End-to-end slicing method, apparatus and computer program product in wireless communication system

Abstract

A method, apparatus, and computer program for providing end-to-end slicing in a wireless communication system. A profile of a plurality of network slices of the wireless communication system is determined. Each network slice of the plurality of network slices has one or more communication components logically isolated from one or more communication components of another network slice of the plurality of network slices. Based on the determined profile and a request received from a user device, a network slice of the plurality of network slices is selected for transmission of data associated with the user device. The data associated with the user device is transmitted using the selected network slice.

Description

Technical Field

[0001] In some implementations, the current topic relates to telecommunications systems, and more specifically to end-to-end slicing in wireless communication systems (e.g., it may include 5G new radios (“NR”) with a lower-layer split architecture). Background Technology

[0002] In today's world, cellular networks provide on-demand communication capabilities to individuals and businesses. Typically, a cellular network is a wireless network that can be distributed across terrestrial areas (called cells). Each such cell is served by at least one transceiver located at a fixed point, called a cell site or base station. Each cell uses a different set of frequencies than its neighboring cells to avoid interference and provide improved service within each cell. When cells are connected together, they provide radio coverage over a wide geographical area, enabling a large number of mobile phones and / or other wireless devices or portable transceivers to communicate with each other and with fixed transceivers and telephones anywhere in the network. This communication is performed through base stations and can be achieved even when a mobile transceiver is moved through more than one cell during transmission. Major wireless communication providers have deployed such cell sites worldwide, allowing mobile phones and mobile computing devices to connect to the public switched telephone network and the public internet.

[0003] A mobile phone is a portable telephone capable of receiving and / or making telephone and / or data calls via a cell site or tower by using radio waves to transmit signals to and from the mobile phone. Given the large number of mobile phone users, current mobile phone networks offer limited and shared resources. In this regard, cell sites and mobile phones can vary frequencies and use low-power transmitters to allow multiple callers to use the network simultaneously with less interference. Cell site coverage can depend on a specific geographic location and / or the number of users who may potentially use the network. For example, in urban areas, a cell site can have a range of up to about 1 / 2 mile; in rural areas, this range can be up to 5 miles; and in some areas, users can receive signals from cell sites 25 miles away.

[0004] The following are some examples of digital cellular technologies used by communication providers: Global System for Mobile Communications (“GSM”), General Packet Radio Service (“GPRS”), cdmaOne, CDMA2000, Evolved Data Optimized (“EV-DO”), Enhanced Data Rate GSM Evolution (“EDGE”), Universal Mobile Telecommunications System (“UMTS”), Digital Enhanced Cordless Telecommunications (“DECT”), Digital AMPS (“IS-136 / TDMA”), and Integrated Digital Enhanced Network (“iDEN”). Long Term Evolution, or 4G LTE, developed by the 3rd Generation Partnership Project (“3GPP”) standards body, is the standard for high-speed data wireless communication for mobile phones and data terminals. The 5G LTE standard is currently under development. LTE is based on GSM / EDGE and UMTS / HSPA digital cellular technologies and allows for increased capacity and speed through the use of different radio interfaces and core network improvements.

[0005] Mobile devices are used to receive and send different types of data, such as voice data (e.g., phone calls), email, text messages, internet browsing, video data (e.g., videos, video calls, augmented / virtual reality, etc.), and audio data (e.g., music streaming). Different types of data may require different transmission bandwidths. For example, reproducing high-definition video on a mobile device with good quality may require higher bandwidth compared to transmitting emails or text messages to the mobile device. 5G NR networks implement network slicing features to accommodate different types of data services and usage. However, end-to-end network slicing and selection are not yet clearly defined. Summary of the Invention

[0006] In some implementations, the present subject relates to a computer-implemented method for providing end-to-end slicing in a wireless communication system. The method may include determining a profile of multiple network slices of the wireless communication system. Each of the multiple network slices may have one or more communication components logically isolated from one or more communication components of another network slice. The method may further include selecting a network slice from the multiple network slices for transmitting data associated with the user equipment based on the determined profile and a request received from a user equipment; and using the selected network slice to transmit the data associated with the user equipment.

[0007] In some implementations, the current topic may include one or more of the following optional features. The method may further include determining at least one communication component for isolation of the network slice based on at least one parameter in the network slice's configuration file. In some implementations, the parameter may include one or more of the following: latency requirements, the number of user devices using the network slice, the number of tracking areas associated with the network slice, the mobility level of the user devices using the network slice, the activity of the network slice, the required isolation level, and any combination thereof.

[0008] In some implementations, the method may further include: using the selected network slice to monitor data transmission; based on the monitoring, selecting another configuration of the network slice for data transmission from among multiple network slice configurations; and using the other selected network slice configuration to transmit data associated with the user device.

[0009] In some implementations, the method may further include virtualizing one or more logically isolated components, and optionally instantiating one or more virtualized logically isolated components based on at least one parameter.

[0010] The aforementioned determination, selection, and transmission operations can be performed by the base station (e.g., gNB in ​​a 5G NR network).

[0011] In some implementations, a base station may include at least one of the following communication components: one or more remote radio units (RU), one or more centralized units (CU), one or more distributed units (DU), one or more control plane portions (CU-CP) of one or more centralized units, one or more user plane portions (CU-UP) of one or more centralized units, one or more access and mobility functions (AMF), one or more user plane functions (UPF), and one or more session management functions (SMF).

[0012] In some implementations, at least one of the following: one or more CU-UPs, one or more AMFs, one or more UPFs, and one or more SMFs of one network slice in a plurality of network slices can be logically isolated from at least one of the following: one or more CU-UPs, one or more AMFs, one or more UPFs, and one or more SMFs of another network slice in the plurality of network slices. However, one or more RUs, one or more DUs, and one or more CU-CPs can be shared by all network slices in the plurality of slices.

[0013] In some implementations, the CU-UP, UPF, and SMF of one of the multiple network slices can be logically isolated from the CU-UP, UPF, and SMF of another network slice. However, RU, DU, CU-CP, and AMF can be shared by all network slices in the multiple slices. In this implementation, transmission may include transmitting data associated with a user equipment using multiple network slices.

[0014] In some implementations, the DU, CU-CP, CU-UP, AMF, UPF, and SMF of one network slice in a plurality of network slices can be logically isolated from the DU, CU-CP, CU-UP, AMF, UPF, and SMF of another network slice in a plurality of network slices. However, the RU can be shared by all network slices in a plurality of network slices.

[0015] In some implementations, the DU, CU-UP, UPF, and SMF of one of the multiple network slices can be logically isolated from the DU, CU-UP, UPF, and SMF of another network slice. However, the RU, CU-CP, and AMF can be shared by all slices. In this case, transmission may include transmitting data associated with a user equipment using multiple network slices.

[0016] In some implementations, the RU, DU, CU-CP, CU-UP, AMF, UPF, and SMF of one network slice in a plurality of network slices can be logically isolated from the RU, DU, CU-CP, CU-UP, AMF, UPF, and SMF of another network slice in a plurality of network slices.

[0017] Non-transitory computer program products (i.e., physically implemented computer program products) that store instructions, when executed by one or more data processors of one or more computing systems, cause at least one data processor to perform the operations described herein. Similarly, computer systems that may include one or more data processors and memory coupled to said one or more data processors are also described. The memory may temporarily or permanently store instructions that cause at least one processor to perform one or more of the operations described herein. Furthermore, the methods may be implemented by one or more data processors within a single computing system or distributed across two or more computing systems. Such computing systems may be connected and exchange data and / or commands or other instructions via one or more connections (including but not limited to connections via networks (e.g., the Internet, wireless wide area networks, local area networks, wide area networks, wired networks, etc.), direct connections between one or more of the multiple computing systems, etc.

[0018] Details of one or more variations of the subject matter described herein are set forth in the accompanying drawings and the following description. Further features and advantages of the subject matter described herein will be apparent from the specification, drawings, and claims. Attached Figure Description

[0019] The accompanying drawings, which are incorporated in and form part of this specification, illustrate certain aspects of the subject matter disclosed herein and, together with the specification, help to explain some principles associated with the disclosed implementations. In the drawings:

[0020] Figure 1a An exemplary conventional Long Term Evolution (“LTE”) communication system is illustrated;

[0021] Figure 1b It shows Figure 1a Further details of the exemplary LTE system shown;

[0022] Figure 1c It shows Figure 1a Additional details of the Evolution Packet Core of the exemplary LTE system shown;

[0023] Figure 1d It shows Figure 1a The exemplary evolution node B of the exemplary LTE system shown;

[0024] Figure 2 It shows Figures 1a to 1d Further details of the evolution node B shown;

[0025] Figure 3 An exemplary virtual radio access network is shown, based on some implementations of the current topic;

[0026] Figure 4 An exemplary 3GPP decoupling architecture is shown to provide its users with access to higher frequency bands;

[0027] Figure 5 An exemplary network slicing architecture is shown;

[0028] Figure 6 An example S-NSSAI identifier is shown;

[0029] Figure 7 An exemplary 5G wireless communication system is shown;

[0030] Figure 8a An exemplary communication system for performing network slicing separation at the user plane portion of a centralized unit is shown, according to some implementations of the present topic;

[0031] Figure 8bAn exemplary communication system with a user device that can use one or more network slices is shown, according to some implementations of the present topic;

[0032] Figure 9a An exemplary communication system for performing network slicing separation at the distributed unit (DU) portion is shown, according to some implementations of the present topic;

[0033] Figure 9b An exemplary communication system with a user device that can use one or more network slices is shown, according to some implementations of the present topic;

[0034] Figure 10 An exemplary communication system for performing network slicing separation at the remote radio unit (RU) section is shown, according to some implementations of the present topic;

[0035] Figure 11 This illustrates some implementations, based on the current topic, for mapping one or more network slices to a map relative to... Figures 8a-10 Exemplary methods for specific deployment options discussed;

[0036] Figure 12 An exemplary process for updating a slice configuration file to an implementation mapping is shown, based on some implementations of the current topic;

[0037] Figure 13 Exemplary systems based on some implementations of the current topic are shown; and

[0038] Figure 14 Exemplary methods are shown based on some implementations of the current topic. Detailed Implementation

[0039] The current topic can provide systems and methods that can be implemented in a lower-layer decoupled architecture for wireless communication systems. Such systems can include a variety of wireless communication systems, including 5G new radio communication systems, LTE communication systems, etc.

[0040] One or more aspects of the current topic can be incorporated into the transmitter and / or receiver components of base stations (e.g., gNodeB, eNodeB, etc.) in such communication systems. The following is a general discussion of Long Term Evolution (LTE) communication systems and 5G new radio communication systems.

[0041] I. Long Term Evolution (LTE) Communications System

[0042] Figures 1a to 1c and Figure 2An exemplary conventional Long Term Evolution (“LTE”) communication system 100 and its various components are illustrated. As is commercially known, LTE systems, or 4G LTE, are governed by standards for high-speed data wireless communication used in mobile phones and data terminals. These standards are based on GSM / EDGE (“Global System for Mobile Communications” / “Enhanced Data Rate GSM Evolution”) and UMTS / HSPA (“Universal Mobile Telecommunications System” / “High Speed ​​Packet Access”) network technologies. These standards were developed by 3GPP (“3rd Generation Partnership Project”).

[0043] like Figure 1a As shown, system 100 may include an evolved universal terrestrial radio access network (“EUTRAN”) 102, an evolved packet core (“EPC”) 108, and a packet data network (“PDN”) 101, wherein EUTRAN 102 and EPC 108 provide communication between user equipment 104 and PDN 101. EUTRAN 102 may include multiple evolved Node Bs (“eNodeB” or “ENODEB” or “enodeb” or “eNB”) or base stations 106 (a, b, c) that provide communication capabilities to multiple user equipment 104 (a, b, c) (e.g., EUTRAN 102). Figure 1b (As shown in the diagram). User equipment 104 can be a mobile phone, smartphone, tablet, personal computer, personal digital assistant (“PDA”), server, data terminal, and / or any other type of user equipment, and / or any combination thereof. User equipment 104 can connect to EPC 108 via any eNodeB 106 and ultimately to PDN 101. Typically, in terms of distance, user equipment 104 can connect to the nearest eNodeB 106. In LTE system 100, EUTRAN 102 and EPC 108 work together to provide connectivity, mobility, and services to user equipment 104.

[0044] Figure 1b It shows Figure 1a Further details of network 100 shown are provided below. As mentioned above, EUTRAN 102 includes multiple eNodeBs 106, also known as cell sites. The eNodeBs 106 provide radio functions and perform key control functions, including scheduling of air link resources or radio resource management, active-mode mobility or handover, and service admission control. The eNodeBs 106 are responsible for selecting which Mobility Management Entities (MMEs, such as…)… Figure 1c (As shown) will serve user equipment 104 and be responsible for protocol features such as header compression and encryption. The eNodeBs 106 that make up EUTRAN 102 cooperate with each other for radio resource management and handover.

[0045] Communication between user equipment 104 and eNodeB 106 occurs via air interface 122 (also known as the "LTE-Uu" interface). Figure 1b As shown, air interface 122 provides communication between user equipment 104b and eNodeB 106a. Air interface 122 uses Orthogonal Frequency Division Multiple Access (“OFDMA”) and Single Carrier Frequency Division Multiple Access (“SC-FDMA”) (a variant of OFDMA) on the downlink and uplink, respectively. OFDMA allows the use of multiple known antenna techniques, such as Multiple-Input Multiple-Output (“MIMO”).

[0046] Air interface 122 uses various protocols, including Radio Resource Control (“RRC”) for signaling between user equipment 104 and eNodeB 106 and Non-Access Stratum (“NAS”) for signaling between user equipment 104 and MME (such as…). Figure 1c (As shown in the diagram). In addition to signaling, user services are transmitted between user equipment 104 and eNodeB 106. Both signaling and services in system 100 are carried by physical layer (“PHY”) channels.

[0047] Multiple eNodeB 106s can interconnect with each other using X2 interfaces 130 (a, b, c). For example... Figure 1a As shown, X2 interface 130a provides interconnection between eNodeB 106a and eNodeB 106b; X2 interface 130b provides interconnection between eNodeB 106a and eNodeB 106c; and X2 interface 130c provides interconnection between eNodeB 106b and eNodeB 106c. X2 interfaces can be established between two eNodeBs to provide signal exchange, which may include information related to load or interference and information related to handover. eNodeB 106 communicates with the Evolved Packet Core 108 via S1 interface 124 (a, b, c). S1 interface 124 can be split into two interfaces: one interface for the control plane (in... Figure 1c The diagram shows the control plane interface (S1-MME interface) 128), and another interface is used for the user plane (in... Figure 1c The image shows the user plane interface (S1-U interface) 125.

[0048] EPC 108 establishes and enforces Quality of Service (“QoS”) for user services and allows user equipment 104 to maintain a consistent Internet Protocol (“IP”) address while mobile. It should be noted that each node in network 100 has its own IP address. EPC 108 is designed to interact with traditional wireless networks. EPC 108 is also designed to separate the control plane (i.e., signaling) and user plane (i.e., services) in the core network architecture, allowing for greater flexibility in implementation and independent scalability of control and user data functions.

[0049] The EPC 108 architecture is specifically designed for packetized data and Figure 1c This is illustrated in more detail below. EPC 108 includes a Serving Gateway (S-GW) 110, a PDN Gateway (P-GW) 112, a Mobility Management Entity (“MME”) 114, a Home Subscriber Server (“HSS”) 116 (the user database of EPC 108), and a Policy Control and Charging Rules Function (“PCRF”) 118. Some of these (such as S-GW, P-GW, MME, and HSS) are often combined into nodes depending on the manufacturer's implementation.

[0050] S-GW 110 acts as an IP packet data router and serves as the bearer path anchor for user equipment (UE) within EPC 108. Therefore, when a UE moves from one eNodeB 106 to another during mobility operations, S-GW 110 remains unchanged, and the bearer path towards EUTRAN 102 is switched to communicate with the new eNodeB 106 serving UE 104. If UE 104 moves to another S-GW 110's domain, MME 114 will transfer all of the UE's bearer paths to the new S-GW. S-GW 110 establishes bearer paths for the UE to one or more P-GWs 112. If downlink data is received for an idle UE, S-GW 110 buffers downlink packets and requests MME 114 to locate and re-establish the bearer path to and through EUTRAN 102.

[0051] P-GW 112 is EPC 108 (as well as User Equipment 104 and EUTRAN 102) and PDN 101 ( Figure 1aThe gateway between user equipment (as shown in the diagram) and P-GW 112. P-GW 112 acts as a router for user services and performs functions on behalf of user equipment. These functions include IP address allocation for user equipment, packet filtering of downlink user services to ensure they are placed on appropriate bearer paths, and enforcement of downlink QoS (including data rate). Depending on the service the user is using, there may be multiple user data bearer paths between user equipment 104 and P-GW 112. Users may use services on PDNs served by different P-GWs, in which case the user equipment has at least one bearer path established to each P-GW 112. During a handover of a user equipment from one eNodeB to another, if S-GW 110 is also changing, the bearer path originating from P-GW 112 is switched to the new S-GW.

[0052] MME 114 manages user equipment 104 within EPC 108, including managing user authentication, maintaining the background of authenticated user equipment 104, establishing data bearer paths for user services in the network, and maintaining location tracking for idle mobile devices not decoupled from the network. For idle user equipment 104 that needs to reconnect to the access network to receive downlink data, MME 114 initiates paging to locate the user equipment and re-establishes a bearer path to EUTRAN 102 and through EUTRAN 102. The MME 114 for a specific user equipment 104 is selected by eNodeB 106, where user equipment 104 initiates system access from eNodeB 106. For load balancing and redundancy purposes, the MME is typically part of the set of MMEs in EPC 108. In establishing the user's data bearer path, MME 114 is responsible for selecting P-GW 112 and S-GW 110, which will form the endpoints of the data path through EPC 108.

[0053] PCRF 118 is responsible for policy control decision-making and for controlling the flow-based billing functionality within the Policy Control Enforcement Function (“PCEF”), which is retained in P-GW 110. PCRF 118 provides QoS authorization (QoS Class Identifier (“QCI”) and bit rate), which determines how a data flow will be processed in the PCEF and ensures that this conforms to the user’s subscription profile.

[0054] As mentioned above, IP service 119 is provided by PDN 101 (e.g. Figure 1a (as shown in the image).

[0055] Figure 1dAn exemplary structure of eNodeB 106 is shown. eNodeB 106 may include at least one radio remote head (“RRH”) 132 (typically, there may be three RRH 132) and a baseband unit (“BBU”) 134. The RRH 132 may be connected to an antenna 136. The RRH 132 and BBU 134 may be connected using an optical interface consistent with the Common Public Radio Interface (“CPRI”) 142 standard specification. The operation of eNodeB 106 can be characterized using the following standard parameters (and specifications): radio frequency bands (Band4, Band9, Band17), bandwidth (5, 10, 15, 20MHz), access scheme (downlink: OFDMA; uplink: SC-OFDMA), antenna technology (downlink: 2x2 MIMO; uplink: 1x2 single-input multiple-output (“SIMO”)), number of sectors (maximum 6), maximum transmission power (60W), maximum transmission rate (downlink: 150Mb / s; uplink: 50Mb / s), S1 / X2 interface (1000Base-SX, 1000Base-T), and mobile environment (up to 350km / h). BBU 134 can handle digital baseband signal processing, S1 line termination, X2 line termination, call processing, and monitoring and control processing. From EPC 108 ( Figure 1d IP packets received (not shown) can be modulated into digital baseband signals and transmitted to RRH 132. Conversely, digital baseband signals received from RRH 132 can be demodulated into IP packets for transmission to EPC 108.

[0056] The RRH 132 can transmit and receive wireless signals using antenna 136. The RRH 132 can (using converter (“CONV”) 140) convert digital baseband signals from BBU 134 into radio frequency (“RF”) signals and (using amplifier (“AMP”) 138) amplify them for transmission to user equipment 104. Figure 1d (Not shown in the image). Instead, the RF signal received from user equipment 104 (using AMP 138) is amplified and (using CONV 140) converted into a digital baseband signal for transmission to BBU 134.

[0057] Figure 2Additional details of an exemplary eNodeB 106 are shown. The eNodeB 106 comprises multiple layers: LTE layer 1202, LTE layer 2204, and LTE layer 3206. LTE layer 1 includes the physical layer (“PHY”). LTE layer 2 includes medium access control (“MAC”), radio link control (“RLC”), and packet data convergence protocol (“PDCP”). LTE layer 3 includes various functions and protocols, including radio resource control (“RRC”), dynamic resource allocation, eNodeB measurement configuration and provisioning, radio admission control, connection mobility control, and radio resource management (“RRM”). The RLC protocol is an Automatic Repeat Request (“ARQ”) fragmentation protocol used on the cellular air interface. The RRC protocol handles LTE layer 3 control plane signaling between the user equipment and the EUTRAN. RRC includes functions for connection establishment and release, broadcasting system information, radio bearer establishment / reconfiguration and release, RRC connection mobility procedures, paging notification and release, and outer loop power control. PDCP performs IP header compression and decompression, user data transmission, and maintenance of radio bearer sequence numbers. Figure 1d The BBU 134 shown may include LTE layers L1-L3.

[0058] One of the primary functions of eNodeB 106 is radio resource management, which includes scheduling of uplink and downlink air interface resources for user equipment 104, control of bearer resources, and admission control. As an agent of EPC 108, eNodeB 106 is responsible for transmitting paging messages used to locate mobile devices when they are idle. eNodeB 106 also handles over-the-air transmission of common control channel information, header compression, encryption and decryption of user data transmitted over the air, and the establishment of handover reporting and triggering standards. As mentioned above, eNodeB 106 can cooperate with other eNodeB 106s via the X2 interface for handover and interference management purposes. eNodeB 106 communicates with the EPC's MME via the S1-MME interface and with the S-GW via the S1-U interface. Furthermore, eNodeB 106 exchanges user data with the S-GW via the S1-U interface. eNodeB 106 and EPC 108 have a many-to-many relationship to support load sharing and redundancy between the MME and S-GW. The eNodeB 106 selects an MME from a group of MMEs, so multiple MMEs can share the load to avoid congestion.

[0059] III.5G NR Wireless Communication Network

[0060] In some implementations, the current topic involves 5G New Radio (“NR”) communication systems. 5G NR is the next telecommunications standard, surpassing 4G / IMT-Advanced standards. 5G networks offer significantly higher capacity than current 4G, allowing for a greater number of mobile broadband users per area unit and enabling higher and / or unlimited data consumption in gigabytes per month and per user. This allows users to stream high-definition media on their mobile devices for many hours daily, even when not using Wi-Fi. 5G networks offer improved support for device-to-device communication, lower costs, lower latency than 4G devices, and lower battery consumption. Such networks offer data rates of tens of megabits per second for large numbers of users, 100 Mbps for urban areas, and 1 Gbps for users in restricted areas (e.g., office floors), massive simultaneous connections for wireless sensor networks, enhanced spectral efficiency, improved coverage, enhanced signaling efficiency, 1–10 ms latency, and reduced latency compared to existing systems.

[0061] Figure 3 An exemplary virtual radio access network 300 is illustrated. Network 300 can provide communication between various components, including a base station (e.g., eNodeB, gNodeB) 301, a radio device 307, a centralized unit 302, a distributed unit 304, and a radio frequency component 306. Components in system 300 can be communicatively coupled to a core using a backhaul link 305. The centralized unit (“CU”) 302 can be communicatively coupled to the distributed unit (“DU”) 304 using an intermediate connection 308. The radio frequency component (“RU”) 306 can be communicatively coupled to the DU 304 using a fronthaul connection 310.

[0062] In some implementations, CU 302 can provide intelligent communication capabilities to one or more DU units 308. Units 302 and 304 may include one or more base stations, macro base stations, micro base stations, radio remote heads, and / or any combination thereof.

[0063] In a lower-layer discrete architecture environment, the CPRI bandwidth requirement for NR can be 100Gb / s. CPRI compression can be implemented in DU and RU (e.g., Figure 3 (As shown). In 5G communication systems, compressed CPRI on Ethernet frames is referred to as eCPRI and is the recommended forward backhaul interface. This architecture allows for standardization of forward backhaul / intermediate transport, which can include higher-layer separation (e.g., Option 2 or Option 3-1 (upper / lower RLC separation architecture)) and forward backhaul with L1 separation architecture (Option 7).

[0064] In some implementations, the lower-layer separation architecture (e.g., option 7) may include receivers in the uplink, joint processing among multiple transmission points (TPs) for both DL and UL, and transmission bandwidth and latency requirements for ease of deployment. Further, the lower-layer separation architecture of the present topic may include separation between cell-level and user-level processing, which may include cell-level processing in remote units (“RUs”) and user-level processing in DUs. Furthermore, using the lower-layer separation architecture of the present topic, frequency domain samples can be transmitted via Ethernet forward backhaul, wherein frequency domain samples can be compressed to reduce forward backhaul bandwidth.

[0065] Figure 4 An exemplary communication system 400 is shown that can implement 5G technology and provide its users with access to higher frequency bands (e.g., greater than 10 GHz). System 400 may include macro cells 402 and small cells 404 and 406.

[0066] Mobile device 408 can be configured to communicate with one or more small cells 404 and 406. System 400 can allow separation of the control plane (C-plane) and user plane (U-plane) between macro cell 402 and small cells 404 and 406, where the C-plane and U-plane utilize different frequency bands. Specifically, small cells 402 and 404 can be configured to utilize higher frequency bands when communicating with mobile device 408. Macro cell 402 can utilize existing cellular frequency bands for C-plane communication. Mobile device 408 can be communicatively coupled via U-plane 412, where small cells (e.g., small cell 406) can provide higher data rates and more flexible / cost / energy-efficient operation. Macro cell 402 can maintain good connectivity and mobility via C-plane 410. Furthermore, in some cases, LTE PUCCH and NR PUCCH can be transmitted on the same frequency.

[0067] IV. Network Slicing

[0068] 5G network slicing refers to a network architecture that allows multiplexing of virtual and independent logical networks on the same physical network infrastructure. Each network slice is an isolated end-to-end network configured to serve different requirements that a specific application might request. Several network functions can exist in the control plane, which can be shared by more than one network slice. Network slicing technology implements the concepts of Software-Defined Networking (SDN) and Network Functions Virtualization (NFV), thereby allowing flexible and scalable network slicing on top of public network infrastructure. Each network slice can be managed by the same or different Mobile Virtual Network Operators (MVNOs), allowing MVNOs to autonomously deploy multiple network slices tailored to various applications.

[0069] Figure 5 An exemplary network slicing architecture 500 is illustrated. Architecture 500 may include a network slice controller 502, a service layer 504, a network function layer 506, and an infrastructure layer 508. The network slice controller 502 connects to various functional interfaces performed by layers 504-508 to manage requests for each slice. The controller 502 coordinates communication between layers 504-508 to provide end-to-end service management (i.e., mapping individual service instances (SLA requirements) to network functions that satisfy service constraints), virtual resource definition (i.e., virtualizing physical network resources to manage resources used for allocating network functions), and slice lifecycle management (i.e., monitoring slice performance across all three layers 504-508 for dynamic reconfiguration of each slice to adapt to changes in SLA requirements).

[0070] Service layer 504 interfaces with one or more Mobile Virtual Network Operators (MVNOs) 505 and one or more Service Providers 507. MVNOs and providers 507 may share a physical network, where each service is represented as a service instance including all network characteristics required as a Service Level Agreement (SLA). Network Functions layer 506 creates each network slice based on service instance requests from layer 504. A network slice includes individual network functions that can be placed on the virtual network infrastructure and coupled together to create an end-to-end network slice instance based on the network characteristics of the service request. Infrastructure layer 508 is the actual physical network topology multiplexed on each network slice and provides physical network resources to host the network functions of each slice.

[0071] While network slicing is a core feature of 5G communication networks, and the selection of network functions and the routing of data via isolated networks are based on slice IDs, end-to-end slicing aspects of the radio access network and resource isolation for each slice are not yet defined and depend on the specific implementation. Furthermore, current standards define core network selection and routing to the core network based on network slicing; however, resource isolation and management of radio-grade resources are not defined in existing systems. This topic provides solutions to these problems by offering various deployment methods and system aspects for implementing resource isolation in the RAN.

[0072] Network slice instances can be allocated / deallocated by network operators according to various 3GPP standards, which also specify slice profiles (i.e., SliceProfiles) and characteristics for each slice. Some characteristics may include performance requirements for slice (perfReq) attributes, which can be categorized based on whether the slice / service type (SST) is enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), etc. The following data model, as specified in the 3GPP standards, can be used to define slice requirements:

[0073]

[0074]

[0075]

[0076] Additional characteristics may include the maximum number of user equipment (UEs) expected to use a particular slice, the coverage area (or tracking area) available for the slice, the slice's latency characteristics, UE mobility class (e.g., whether the UEs using the slice are expected to be stationary, nomadic, have limited mobility, move quickly, etc.), resource sharing class (e.g., as defined by 3GPP standards as shared / non-shared), resource isolation class (which can indicate the level within the RAN where resources may need to be isolated), and the expected reliability for a particular slice. When the operator provides a slice template (as defined by the code shown above), this template should be mapped to specific characteristics within the RAN and core network.

[0077] The aforementioned network slicing architecture 500 can be based on the identifier S-NSSAI (Specific Network Slice Selection Auxiliary Information). Figure 6An exemplary S-NSSAI identifier 600 is shown. Identifier 600 includes an 8-bit Standard Slice / Service Type (SST) value 602 (which indicates the expected network slice behavior in terms of characteristics and services) and a 24-bit Slice Differentiator (SD) value 604 (which indicates optional information supplementing the slice / service type to distinguish between different network slices of the same slice / service type). The S-NSSAI 600 is used by the User Equipment (UE) when accessing a network in the Public Land Mobile Network (PLMN) associated with the S-NSSAI. Specifically, when registering to the network, the UE provides a “requested NSSAI” to the RAN in its RRC signaling, where the NSSAI is a set of S-NSSAIs 600. The RAN uses the requested NSSAI to select the Access and Mobility Management Function (AMF) in the 5G core network. The AMF is a common element of all slices that the UE can access. After the registration procedure is completed, the UE activates one or more slices by initiating a Packet Data Unit (PDU) session activation procedure. Each PDU session belongs to one slice. The following activation scenarios are possible: a UE accessing multiple network slices (i.e., a UE accessing multiple PDU sessions, where each PDU session uses a different S-NSSAI), and a UE accessing only one network slice. However, the network may already have multiple network slices deployed, with different UEs using different network slices.

[0078] Figure 7 An exemplary 5G wireless communication system 700 is illustrated according to some implementations of the present topic. System 700 can be configured to have a lower-layer decoupled architecture according to option 7-2. System 700 may include a core network 702 (e.g., a 5G core) and one or more gNodeBs (or gNBs), wherein the gNB may have a centralized unit gNB-CU. The gNB-CU may be logically separated into a control plane portion gNB-CU-CP 704 and one or more user plane portions gNB-CU-UP 706. The control plane portion 704 and the user plane portion 706 can be configured to be communicatively coupled using an E1 communication interface 714 (as specified in the 3GPP standard). The control plane portion 704 can be configured to be responsible for the execution of the RRC and PDCP protocols of the radio stack.

[0079] The control plane and user plane portions 704, 706 of the gNB's centralized unit can be configured to be communicatively coupled to one or more distributed units (DUs) 708, 710 according to a lower-layer discrete architecture. Distributed units 708, 710 can be configured to execute the upper layers of the radio stack's RLC, MAC, and PHY layer protocols. Control plane portion 704 can be configured to be communicatively coupled to distributed units 708, 710 using an F1-C communication interface 716, and user plane portion 706 can be configured to be communicatively coupled to distributed units 708, 710 using an F1-U communication interface 718. Distributed units 708, 710 can be coupled to one or more remote radio units (RUs) 712 via a forward backhaul interface 720, which in turn connects to one or more user equipment units (U). Figure 7 (Not shown in the image) Communication. The remote radio unit 712 can be configured to execute the lower part of the PHY layer protocol and provide antenna capability to the remote unit for communication with user equipment (similar to the above combination). Figures 1a-2 (Discussion).

[0080] V. End-to-end network slicing

[0081] In some implementations, such as Figure 7 As shown, to provide end-to-end slicing capability, a base station may be configured with one or more executable procedures (e.g., an end-to-end solution) for performing slice separation at various points within the communication system 700. The determination of where slice separation should occur may depend on individual network parameters, communication session requirements, and / or any other factors. The solution may include: (a) slice separation occurring in the user plane portion of a centralized unit, (b) in a distributed unit, and (c) slice separation occurring at a remote unit. One or more of these solutions may be implemented within system 700 and are discussed below.

[0082] A. Slicing separation at the user plane portion of the centralized unit.

[0083] Figure 8a An exemplary communication system 800 for performing network slicing separation at the user plane portion of a centralized unit is shown, according to some implementations of the present topic. System 800 is similar to Figure 7 The system 700 shown is for ease of explanation and discussion. Figure 8a Only the relevant parts are shown in the image.

[0084] System 800 may include one or more user devices 802 (a, b, c), remote units 803, distributed units 805, and a control plane portion 807 of a centralized unit. In this implementation, units 803-807 can be for all network slices (in... Figure 8aThe three slices shown are shared. This means that all user equipment 802 can access the same units 803-807 before network slice separation occurs at the user plane portion of the centralized unit.

[0085] like Figure 8a As shown, isolation between network slices can be provided forward from the gNB-CU-UP. Specifically, a separate gNB-CU-UP instance 808 (a, b, c) can be created by the radio access network for each slice, which can be configured to serve or allow access by the corresponding user equipment 802 (a, b, c). Furthermore, due to the slice separation, separate corresponding instances of Access and Mobility Functions (AMF) 810 (a, b, c), User Plane Functions (UPF1-3) 812 (a, b, c), and Session Management Functions (SMF1-3) 814 (a, b, c) can also be created. (Apart from any common parts) Each network slice can be identified by the label a, b, or c.

[0086] In 5G networks, the Access and Mobility Management Function (AMF) (which replaces the MME entity in 4G networks) receives connection and session-related information from the user equipment and is responsible for handling connection and mobility management tasks. Session management-related messages can be forwarded to the Session Management Function (SMF). The SMF is responsible for interacting with the decoupled data plane, creating, updating, and removing Protocol Data Unit (PDU) sessions, and managing session context using User Plane Functions (UPFs). The UPF provides interconnection between the mobile infrastructure and the data network (DN) for encapsulation and decapsulation of the GPRS tunneling protocol for the user plane (GTP-U). The SMF also performs packet routing and forwarding, including directing flows to specific data networks based on traffic matching filters, and acting as an intermediate UPF (I-UPF) for up to one PDU session. The UPF also performs application detection using Service Data Flow (SDF) traffic filter templates or 3-tuple packet flow descriptions (i.e., protocol, server-side IP address, and port number) received from the SMF. UPF also performs per-flow QoS processing, which includes transport-level packet labeling for uplink (UL) and downlink (DL), rate limiting on DL, and reflection QoS labeling. In addition, UPF reports traffic usage for purposes such as billing and lawful interception.

[0087] See back Figure 8aIn some implementations, the selection of a specific slice set can be based on the NSSAI parameter requested by user equipment 802 during the registration procedure, and the selection of a specific slice can be based on the S-NSSAI parameter requested by each user equipment 802 during the PDU session establishment procedure. Specifically, using the NSSAI parameter (which may include one or more S-NSSAI parameters), a suitable AMF 810 can be selected during the registration procedure. During the PDU session establishment procedure, using the S-NSSAI parameter, AMF 810 can select a suitable SMF 814. Since the NSSAI parameter requested from each user equipment 802 can be different, different corresponding AMFs 810 can be assigned to different user equipment 802s. Similarly, the corresponding UPF 812 and SMF 814 can be selected based on the S-NSSAI requested by user equipment 802 during the PDU session establishment procedure. Furthermore, because the S-NSSAI requested from each user equipment can be different, different UPF 812 and SMF 814 can be assigned to different user equipment 802. For example, user equipment 802a can be assigned CU-UP 808a, UPF1810a, AMF1812a, and SMF1814a, where each of these functions is configured to be dedicated to a specific network slice.

[0088] In some implementations, a user equipment can be configured to use more than one network slice. Figure 8b An exemplary communication system 820, having a user device 822 that can use one or more network slices, is shown according to some implementations of the present topic. System 820 may be similar to Figure 8a The system 800 shown is an example. However, instead of... Figure 8a The multiple AMF components shown, RU 803, DU 805, CU-CP 807, and a single AMF 819, can be shared by all network slices. The remainder of system 820 is similar. Figure 8a The system 800 shown is described. In operation, depending on the S-NSSAI requested by the user equipment 822 for each PDU session, a different user plane portion (i.e., CU-UP) 808 can be assigned to the user equipment 802.

[0089] B. Slicing separation at the distributed unit section

[0090] Figure 9a An exemplary communication system 900 for performing network slicing separation at the distributed unit (DU) portion is shown, according to some implementations of the present topic. System 900 is similar to Figure 7 The system 700 shown is illustrated, and again, for ease of explanation and discussion, Figure 9aOnly the relevant parts are shown in the image.

[0091] System 900 may include one or more user equipment 902 (a, b, c), a common remote unit 903, one or more distributed units DU1-3905 (a, b, c), and one or more corresponding control plane portions CU-CP1-3907 (a, b, c) of a centralized unit. In this implementation, (similar to...) Figure 8a -Figure b) Only cell 903 can be used for all network slices (in Figure b) Figure 9a (As shown in the diagram, three slices are shared.) This means that all user equipment 902 can access the same remote unit 903 before network slice separation occurs at distributed unit 905.

[0092] like Figure 9a As shown and as described above, isolation between network slices can be provided forward from the DU. Specifically, in addition to the individual DU1-3905, the radio access network can create a control portion CU-CP1-3907 and individual CU-UP instances 908 (a, b, c) for each slice that can be configured to serve or allow access by the corresponding user equipment 902 (a, b, c). Similarly, separate corresponding instances of Access and Mobility Functions (AMF) 910 (a, b, c), User Plane Functions (UPF1-3) 912 (a, b, c), and Session Management Functions (SMF1-3) 914 (a, b, c) can also be created.

[0093] The selection of a specific slice in System 900 can be similar to the above description. Figure 8a Figure b discusses the selection procedure. Specifically, different corresponding AMF 910, UPF 912, and SMF 914 can be assigned to different user equipment 902. For example, user equipment 902a can be assigned DU 905a, CU-CP 907a, CU-UP 908a, UPF1910a, AMF1912a, and SMF1914a, where each of these functions is configured to be dedicated to a specific network slice. Each network slice can be identified by labels a, b, or c (besides any common parts).

[0094] In some implementations, because the DU 905 controls the radio bandwidth, each network slice can be allocated a specific bandwidth portion (BWP) within the carrier's bandwidth. 5G NR communication networks allow the carrier bandwidth to be divided into multiple bandwidth portions (as defined in the 3GPP standard). Each DU 905 can be configured to control one such bandwidth portion. Within the carrier bandwidth, different BWPs can be assigned different Physical Resource Blocks (PRBs). For example, if the carrier bandwidth (CBW) is 100MHz with a subcarrier spacing of 30kHz, it will have a total of 273 PRBs. If the CBW is divided into four BWPs, one of which can be 40MHz, the other three can each be 20MHz. Each BWP can allocate its own PRB share from the total 273 PRBs. Furthermore, different user equipment 902 using different slices can be configured with the specific BWP of the corresponding slice during the PDU session establishment procedure (i.e., during the RRC reconfiguration for dedicated radio bearer (DRB) setup).

[0095] The RU 903 can be configured to support multiple BWPs within the carrier bandwidth. Depending on the BWP receiving uplink messages on it, the RU 903 can route messages to the correct DU 905 via the forward backhaul interface, where, as described above, each DU 905 can connect to its slice-specific CU-CP 907, and also to its slice-specific CU-UP 908 and AMF 910. In this way, apart from the RU 903, the remainder of radio processing and core network processing can be completely isolated for each network slice.

[0096] In some implementations, it is similar to combining Figure 8b The discussion suggests that a user device can be configured to use more than one network slice. Figure 9b An exemplary communication system 920 with a user device 922 that can use one or more network slices is shown according to some implementations of the present topic.

[0097] System 920 can be similar to Figure 9a The system 900 shown is an example. However, instead of... Figure 9a The multiple AMF components shown, RU 903, CU-CP 917, and AMF 919, can be shared by all network slices. The remainder of System 920 can be similar. Figure 9aThe system 900 is shown in the figure. In operation, instead of using BWP-based control RU 903 to separate services, the separation can be based on different component carriers. User equipment 922 can be configured via RRC to use two component carriers in two different cell groups (e.g., dual connectivity scenarios). For example, when user equipment 922 is using one slice (e.g., represented by components 905a, 908a, 912a, 914a), it can use one component carrier (CC1), and when user equipment 922 is using another slice (e.g., represented by components 905b, 908b, 912b, 914b), it can use another component carrier (CC2), and so on.

[0098] In an alternative implementation, services can be allocated from the RU to different DUs based on the PRB range. This PRB range can be assigned to different slices within the same BWP and / or the same component carrier. For example, assuming a scenario where no 100MHz carrier bandwidth is allocated to a BWP, in addition to the 273 PRBs, PRB ranges 1-100 can be used for slice 1, and PRB ranges 101-200 can be used for another slice. The RU can use the aforementioned PRB separation (i.e., based on the PRB of the received uplink service) to allocate the uplink service to the corresponding DU.

[0099] C. Slicing separation at the remote radio unit section

[0100] Figure 10 An exemplary communication system 1000 for performing network slicing separation at a remote radio unit (RU) portion is shown, according to some implementations of the present topic. System 1000 is similar to Figure 7 The system 700 shown is illustrated, and again, for ease of explanation and discussion, in Figure 10 Only the relevant parts are shown in the image.

[0101] System 1000 may include one or more user equipment 1002 (a, b, c), one or more remote radio units RU1-31003 (a, b, c), one or more distributed units DU1-31005 (a, b, c), one or more control plane portions CU-CP1-31007 (a, b, c) of a centralized unit, one or more user plane portions CU-UP1-31008 (a, b, c), one or more UPF1-31012 (a, b, c), one or more SMF1-31014 (a, b, c), and one or more AMF1-31010 (a, b, c). Each network slice can be identified by the label a, b, or c. In this implementation, none of the three network slices share a unit. This means that all user equipment 1002 can access their own designated network slice a, b, or c, because each network slice can be mapped to a different component carrier. Furthermore, different RUs can be placed in each cell site, with one RU radiating one component carrier. Depending on the S-NSSAI being used by the specific user equipment 1002, it can be configured to use the corresponding component carrier.

[0102] like Figures 8a-10 As shown, one or more remote radio units can be connected to one or more distributed units (where the connection can be defined by various standards). Specifically, a remote unit can be controlled by one or more distributed units using one or more I / Q data samples transmitted and / or received (showing changes in amplitude (or oscillation) and phase) to indicate which distributed unit is processing which component carrier or which PRB set within the carrier bandwidth. The DU port ID parameter of the distributed unit can be used to distinguish the processing unit at the distributed unit. The DU port ID parameter can be included in the segment type control message eCPRI header along with the carrier component ID (CCID) and the remote unit port ID (RU port ID). Each distributed unit can be configured with at least one of different component carriers, frequency band sectors, subframes, time slots, etc., in the remote unit. Furthermore, each distributed unit can be configured with a different user equipment identifier for the remote unit. Finally, depending on the time slot / subframe in which the I / Q sample has been received, the remote unit can send the sample to the correct distributed unit.

[0103] See back Figures 8a-10The systems illustrated in these figures provide different ways to flexibly configure base stations (e.g., gNBs) to accommodate varying desired isolation levels for different network slices. An isolation level (e.g., first isolation level) can occur forward in the processing pipeline from the user plane portion of the centralized unit-up (CU-UP), where remote and distributed units (RUs and DUs) can be shared. Within the DU, all physical (PHY) layer, MAC, and RLC configurations, as well as resources, can be shared with other slices. This is achieved by… Figure 8a The system 800 shown in Figure b is illustrated.

[0104] Another level of isolation (e.g., a second level of isolation) can occur forward from the CU-UP in a processing pipeline with shared RUs and DUs, but within the DU, each network slice can have a specific physical layer, MAC, RLC, and PDCP configuration (as identified by the S-NSSAI parameters discussed above). For example, the S-NSSAI parameters for each request can be mapped to a specific cell or a specific BWP within the DU that defines a specific component carrier and / or a synchronization signal block (SSB) within the same component carrier. This level of isolation can be similar to... Figure 8a - The system shown in Figure b, but with multiple component carriers / cells that define SSB / BWP configurations within the same DU.

[0105] In some implementations, another isolation level (e.g., a third isolation level) can occur forward from the distributed unit, where each slice maps to a different distributed unit (e.g., ...). Figure 9a As shown). When a particular user device uses more than one slice (e.g., as shown). Figure 9b As shown), a user equipment can connect to two or more DUs simultaneously and can be configured with separate MAC entities for the primary cell group (MCG) and secondary cell group (SCG) distributed units. In some implementations, each slice can be hosted at different locations based on its latency and / or other SLA requirements (i.e., such as...). Figure 9a The distributed units of slices a, b, and c shown.

[0106] In some implementations, an additional isolation level (e.g., fourth isolation level) may include forward isolation at the RU in the processing pipeline. In this case, complete end-to-end isolation of user plane traffic can exist. Each remote unit can support a separate component carrier. Figure 10 As shown, user equipment can be configured to use separate MAC entities, such as MCG and SCG, for each distributed unit.

[0107] Figure 11 This illustrates some implementations, based on the current topic, for mapping one or more network slices to information about... Figures 8a-10An exemplary method 1100 for the specific deployment options discussed. At 1102, a network slice profile (as discussed above) can be determined. Once the network slice profile is determined, the isolation level can be determined at 1104. At 1106, the combination of the network slice profile and the isolation level can be used to determine which solution can be selected (i.e., combining...). Figures 8a-10 The deployment options discussed.

[0108] In some implementations, different combinations of slice profile information and isolation levels can determine which solution can be used in a particular setting. As a non-limiting example, given the above discussion, there are nine possible combinations of slice profile-isolation level scenarios. It will be understood that the current topic is not limited to these combinations, and other factors may be used to select the specific solution discussed above or any other solution.

[0109] In some implementations, parameters characterizing the slice profile may include at least one of the following: latency, number of UEs in the slice, number of tracking areas, UE mobility level, isolation level, activity factor, and / or any other parameter. In a first exemplary combination (i.e., Figure 11 In operations 1102 and 1104 shown, the slice profile can be characterized by the following: medium to high latency, a high number (e.g., millions) of UEs in the slice, a large number (e.g., greater than or equal to 1500, meaning approximately 700 UEs per TA or per cell) supporting the slice, a tracking area (which loads the maximum number of UEs per cell or sector in the RAN), nomadic or restricted UE mobility, a first isolation level (as described above), and a high activity factor (meaning the network slice is always active). Based on this combination, the following can be selected: Figure 8a The implementation shown is used to process data going to / from user equipment. In this combination, due to the medium to high latency requirements, the CU-CP and CU-UP can be located in a regional data center, and therefore far from the DU.

[0110] In the second exemplary combination, the delay parameter can be lower, while the remaining parameters are similar to those in the first exemplary combination. Again, here one can choose... Figure 8a The implementation shown is used to process data to / from user equipment. Due to low latency requirements, CU-CP and / or CU-UP can be placed close to the DU. The placement of the CU-CP closer to the DU can be determined based on whether the slice requires low control plane latency. The placement of the CU-UP closer to the DU can also be determined based on whether the slice requires low user plane latency.

[0111] In the third exemplary combination, the slice profile parameters can be similar to the first exemplary combination, except that the isolation level is changed to the second isolation level. In this case, the option can be selected again. Figure 8a The implementation shown can be used for each slice by defining a separate component carrier / cell for the SSB / BWP.

[0112] In the fourth exemplary combination, aside from changing the isolation level to the second isolation level, the slice profile parameters can be similar to the second exemplary combination (i.e., low latency). Again, it is possible to choose... Figure 8a The implementation shown can be used for each slice by defining a separate component carrier / cell for the SSB / BWP.

[0113] In the fifth exemplary combination, the slice profile parameters can be similar to the first exemplary combination, except that the isolation level is changed to the third isolation level. In this case, you can choose... Figure 9a The implementation shown is as follows. Here, similar to the first exemplary combination, the CU-CP and CU-UP can be placed in a regional data center, and thus far from the DU.

[0114] In the sixth exemplary combination, aside from changing the isolation level to the third isolation level, the slice profile parameters can be similar to the second exemplary combination (i.e., low latency). In this case, again, the option can be selected... Figure 9a The implementation shown is similar to that discussed in the second exemplary combination. CU-CP and / or CU-UP can be placed close to DU, wherein the placement of the CU-CP closer to DU can be determined based on whether the slice requires low control plane latency, and the placement of the CU-UP closer to DU can also be determined based on whether the slice requires low user plane latency.

[0115] In the seventh exemplary combination, the slice configuration file parameters can be similar to those in the first exemplary combination, except that the isolation level is changed to the fourth isolation level. Here, you can choose... Figure 10 The implementation shown can be such that CU-CP and CU-UP are placed away from DU.

[0116] In the eighth exemplary combination, aside from changing the isolation level to the fourth isolation level, the slice profile parameters can be similar to the second exemplary combination (i.e., low latency). In this case, again, you can choose... Figure 10 The implementation shown can be used to determine the placement of CU-CP and / or CU-UP closer to the DU based on whether the slice requires low control plane latency and / or low user plane latency, respectively.

[0117] In the ninth exemplary combination, the slicing parameters can be similar to the fifth and / or seventh exemplary combinations where the activity factor and number of UEs are low. In this case, it is possible to select... Figure 8a The implementation shown in the diagram, because it does not require providing isolated RAN resources for the network slice, whose activity is sporadic and has few UEs (since it would unnecessarily waste spectrum), can therefore be used in... Figure 8a The implementation shown here is characterized by forward isolation from CU-UP, while DU is shared with other slices.

[0118] In some implementations, tracking regions, mobility levels, etc., may not affect the selection of slice separation options. These parameters can be used to determine multiple locations where DU, CU-CP, and / or CU-UP instances may need to be instantiated, and / or which functions in DU and / or CU may need to be activated (e.g., slices that can be used for fixed user equipment, mobility profiles, Xn interfaces that may not need to be configured in CU-CP instances).

[0119] In some implementations, Figure 11 The process 1100 shown can be provided by OAM in gNB (e.g., as a static table). The mapping of each slice profile to a specific solution and the corresponding placement logic for CU-CP and CU-UP can be configured accordingly.

[0120] In some implementations, the current topic can also perform slice SLA monitoring by viewing one or more Key Point Indicators (KPIs) that can be reported for each slice. For example, for a slice marked with a high activity factor (with level 4 isolation) (e.g., Figure 10 For a specific slice (as shown in the implementation), receiving reports indicating a reduction in data traffic (e.g., suggesting a low activity factor), OAM can map the slice profile from, for example... Figure 10 The implementation shown becomes Figure 8a The implementation method shown.

[0121] Figure 12 An exemplary procedure 1200 for updating configuration file slices to an implementation mapping is shown, based on some implementations of the current topic. Procedure 1200 can be... Figure 7 The system 700 shown may be executed by one or more components and / or any component of the 5G architecture. At 1202, the control portion of one or more distributed and / or centralized units may provide a configuration consistent with a particular current implementation (e.g., as...). Figures 8a-10This refers to status indicators or key performance indicators (KPIs) related to various aspects (e.g., latency, number of UEs, activity factors, etc., as discussed above). KPIs can be provided to the Operations, Administration, and Maintenance (OAM) of the 5G network. The KPIs can then be provided to the Operations Support System / Business Support System (OSS / BSS) of the 5G network. At 1204, the OSS / BSS can determine if a change to the current implementation is required. If so, then at 1206, the slice profile can be determined to a specific implementation (e.g., as shown). Figures 8a-10 The new mapping (as shown in the diagram). Based on this determination, at 1208, (according to...) Figures 8a-10 The appropriate implementation shown here (new virtual network function instantiation / deinstantiation rules for managing virtualized instances of DU, CU-UP, etc.) can be determined using the new mapping. KPI monitoring and reporting can continue if no changes are required.

[0122] In some implementations, the current theme can be configured to be implemented in System 1300, such as... Figure 13 As shown. System 1300 may include one or more of a processor 1310, a memory 1320, a storage device 1330, and an input / output device 1340. Each of components 1310, 1320, 1330, and 1340 may be interconnected using a system bus 1350. Processor 1310 may be configured to process instructions for execution within system 600. In some implementations, processor 1310 may be a single-threaded processor. In alternative implementations, processor 1310 may be a multi-threaded processor. Processor 1310 may be further configured to process instructions stored in memory 1320 or on storage device 1330, including receiving or transmitting information via input / output device 1340. Memory 1320 may store information within system 1300. In some implementations, memory 1320 may be a computer-readable medium. In alternative implementations, memory 1320 may be a volatile memory cell. In still other implementations, memory 1320 may be a non-volatile memory cell. Storage device 1330 provides large-capacity storage for system 1300. In some implementations, storage device 1330 may be a computer-readable medium. In alternative implementations, storage device 1330 may be a floppy disk device, hard disk device, optical disk device, magnetic tape device, non-volatile solid-state memory, or any other type of storage device. Input / output device 1340 may be configured to provide input / output operations to system 1300. In some implementations, input / output device 1340 may include a keyboard and / or pointing device. In alternative implementations, input / output device 1340 may include a display unit for displaying a graphical user interface.

[0123] Figure 14 An exemplary method 1400 is shown, based on some implementations of the current topic. At 1402, configuration files for multiple network slices of the wireless communication system can be determined. (e.g., as...) Figures 8a-10 Each of the multiple network slices (as shown) may have one or more communication components (e.g., RU, DU, CU-CP, CU-UP, AMF, UPF, SMF, etc.) that are logically isolated from one or more communication components of another network slice. At 1404, based on the determined profile and a request received from the user equipment (e.g., NSSAI), a network slice among the multiple network slices can be selected for the transmission of data associated with the user equipment. At 1406, using the selected network slice, the data associated with the user equipment can be transmitted.

[0124] In some implementations, the current topic may include one or more of the following optional features. The method may further include determining at least one communication component of the network slice for isolation based on at least one parameter in the network slice's configuration file. In some embodiments, the parameter may include one or more of the following: latency requirements, the number of user devices using the network slice, the number of tracking areas associated with the network slice, the mobility level of the user devices using the network slice, the activity of the network slice, the required isolation level, and any combination thereof.

[0125] In some implementations, the method may further include: monitoring data transmission using the selected network slice; selecting another configuration of a network slice for data transmission among multiple network slice configurations based on the monitoring; and transmitting data associated with the user device using the other selected network slice configuration.

[0126] In some implementations, the method may include selecting one or more distributed units for transmitting data based on at least one of the following: one or more component carriers, one or more bandwidth portions, one or more physical resource block ranges, and any combination thereof.

[0127] In some implementations, the method may further include virtualizing the one or more logically isolated components, and optionally instantiating the one or more virtualized logically isolated components based on at least one parameter.

[0128] The above determination, selection, and transmission operations can be performed by the base station (e.g., gNB in ​​a 5G NR network).

[0129] In some implementations, a base station may include at least one of the following communication components: one or more remote radio units (RU), one or more centralized units (CU), one or more distributed units (DU), one or more control plane portions (CU-CP) of one or more centralized units, one or more user plane portions (CU-UP) of one or more centralized units, one or more access and mobility functions (AMF), one or more user plane functions (UPF), and one or more session management functions (SMF).

[0130] In some implementations, at least one of the following: one or more CU-UPs, one or more AMFs, one or more UPFs, and one or more SMFs in one of a plurality of network slices can be logically isolated from at least one of the following: one or more CU-UPs, one or more AMFs, one or more UPFs, and one or more SMFs in another of the plurality of network slices. However, one or more RUs, one or more DUs, and one or more CU-CPs can be shared by all network slices in the plurality of slices. This is in Figure 8a As shown in the image.

[0131] In some implementations, the CU-UP, UPF, and SMF of one network slice in a plurality of network slices can be logically isolated from the CU-UP, UPF, and SMF of another network slice in the plurality of network slices. However, RU, DU, CU-CP, and AMF can be shared by all network slices in the plurality of network slices. This is in Figure 8b As shown in the diagram. In this implementation, transmission may include transmitting data associated with the user device using multiple network slices.

[0132] In some implementations, the DU, CU-CP, CU-UP, AMF, UPF, and SMF of one network slice in a plurality of network slices can be logically isolated from the DU, CU-CP, CU-UP, AMF, UPF, and SMF of another network slice in the plurality of network slices. However, the RU can be shared by all network slices in the plurality of network slices. This is in Figure 9a As shown in the image.

[0133] In some implementations, the DU, CU-UP, UPF, and SMF of one network slice in a plurality of network slices can be logically isolated from the DU, CU-UP, UPF, and SMF of another network slice in the plurality of network slices. However, RU, CU-CP, and AMF can be shared by all slices. This is in Figure 9b As shown in the diagram. In this case, the transmission may include transmitting data associated with the user device using multiple network slices.

[0134] In some implementations, the RU, DU, CU-CP, CU-UP, AMF, UPF, and SMF of one network slice in a plurality of network slices can be logically isolated from the RU, DU, CU-CP, CU-UP, AMF, UPF, and SMF of another network slice in a plurality of network slices.

[0135] The systems and methods disclosed herein can be embodied in various forms, including, for example, data processors (such as computers that also include databases, digital electronic circuits, firmware, software, or combinations thereof). Furthermore, the aforementioned features and other aspects and principles of the implementations of this disclosure can be implemented in different environments. Such environments and related applications can be specifically constructed to perform different processes and operations according to the disclosed implementations, or they may include general-purpose computers or computing platforms that are selectively activated or reconfigured by code to provide necessary functionality. The processes disclosed herein do not inherently involve any particular computer, network, architecture, environment, or other apparatus, and can be implemented by suitable combinations of hardware, software, and / or firmware. For example, various general-purpose machines can be used with programs written according to the teachings of the disclosed implementations, or specialized apparatuses or systems can be more readily constructed to perform the desired methods and techniques.

[0136] The systems and methods disclosed herein can be implemented as computer program products, i.e., computer programs tangibly embodied in an information carrier (e.g., in a machine-readable storage device or in a propagating signal) for performing operations on or controlling the operations of data processing devices (e.g., a programmable processor, a computer, or multiple computers). The computer program can be written in any programming language (including compiled or interpreted languages) and can be deployed in any form (including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment). The computer program can be deployed to execute on one or more computers at a site or distributed across multiple sites interconnected via a communication network.

[0137] As used herein, the term “user” can refer to any entity, including a person or a computer.

[0138] Although ordinal numbers (such as first, second, etc.) can imply order in some cases, as used in this document, ordinal numbers do not necessarily imply order. For example, ordinal numbers may simply be used to distinguish one item from another. For example, to distinguish between the first event and the second event, but without implying any chronological order or fixed reference system (so that the first event in one paragraph of the specification may be different from the first event in another paragraph of the specification).

[0139] The foregoing description is intended to illustrate, and not limit, the scope of the invention as defined by the appended claims. Other implementations are within the scope of the following claims.

[0140] These computer programs, also referred to as programs, software, software applications, applications, components, or code, include machine instructions for a programmable processor and can be implemented using high-level programming languages ​​and / or object-oriented programming languages ​​and / or assembly / machine language. As used herein, the term "machine-readable medium" means any computer program product, apparatus, and / or device (such as a disk, optical disk, memory, and programmable logic device (PLD)) used to provide machine instructions and / or data to a programmable processor, including machine-readable media that receive machine instructions as machine-readable signals. The term "machine-readable signal" means any signal used to provide machine instructions and / or data to a programmable processor. Machine-readable media may store such machine instructions non-transitory, such as non-transitory solid-state memory or magnetic hard disk drives or any equivalent storage medium. Machine-readable media may alternatively or additionally store such machine instructions in a transient manner, such as a processor cache or other random access memory associated with one or more physical processor cores.

[0141] To provide interaction with the user, the subject matter described herein can be implemented on a computer having a display device (e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor) for displaying information to the user, and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user. For example, feedback provided to the user can be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; input from the user can be received in any form (including but not limited to sound, speech, or tactile input).

[0142] The subjects described herein can be implemented in a computing system that includes back-end components (e.g., one or more data servers), or includes middleware components (e.g., one or more application servers), or includes front-end components (e.g., one or more client computers with a graphical user interface or web browser through which users can interact with the implementation of the subjects described herein), or any combination of such back-end, middleware, or front-end components. These components of the system can be interconnected via any form of digital data communication medium (e.g., a communication network). Examples of communication networks include, but are not limited to, local area networks (“LANs”), wide area networks (“WANs”), and the Internet.

[0143] A computing system may include clients and servers. Clients and servers are typically, but not exclusively, geographically separated and usually interact through a communication network. The relationship between clients and servers occurs through computer programs running on the respective computers and having a client-server relationship with each other.

[0144] The implementations described above do not represent all implementations consistent with the subject matter described herein. Rather, they are merely examples consistent with aspects related to the described subject matter. While several variations have been described in detail above, other modifications or additions are possible. In particular, other features and / or variations may be provided in addition to those features and / or variations set forth herein. For example, the implementations described above may involve different combinations and sub-combinations of the described features and / or combinations and sub-combinations of several other features described above. Furthermore, the logical flows depicted in the accompanying drawings and / or described herein do not necessarily require the specific order or sequence shown to achieve the desired result. Other implementations may be within the scope of the following claims.

Claims

1. A computer-implemented method comprising: determining a profile of a plurality of network slices of a wireless communication system, each network slice of the plurality of network slices having one or more communication components logically isolated from one or more communication components of another network slice of the plurality of network slices; selecting, based on the determined profile and a request received from a user device, a network slice of the plurality of network slices for transmission of data associated with the user device; transmitting, using the selected network slice, the data associated with the user device; and determining, based on at least one parameter in the profile of the network slice of the plurality of network slices, at least one communication component of the network slice for isolation; wherein the at least one parameter comprises at least one of: a latency requirement, a number of user devices using the network slice, a number of tracking areas associated with the network slice, a mobility level of user devices using the network slice, an activity of the network slice, a required level of isolation, and any combination thereof.

2. The method of claim 1, further comprising: monitoring, using the selected network slice, transmission of data; selecting, based on the monitoring, another configuration of the network slice for transmission of data in a plurality of network slice configurations; and transmitting, using the other selected network slice configuration, the data associated with the user device.

3. The method of claim 2, further comprising selecting one or more distributed units for transmission of data based on at least one of: one or more component carriers, one or more bandwidth parts, one or more physical resource block ranges, and any combination thereof.

4. The method of claim 1, further comprising: virtualizing one or more logically isolated components; and instantiating, based on the at least one parameter, one or more of the virtualized logically isolated components. At least one of the determining, the selecting, and the transmitting is performed by a base station. The base station comprises at least one of the following communication components: one or more remote radio units, one or more centralized units, one or more distributed units, one or more control plane portions of the one or more centralized units, one or more user plane portions of the one or more centralized units, one or more access and mobility functions, one or more user plane functions, and one or more session management functions.

7. The method of claim 6, wherein, 5. The method of claim 4, wherein, ​ 6. The method of claim 5, wherein, ​ ​ at least one of the one or more user plane portions, the one or more access and mobility functions, the one or more user plane functions, and the one or more session management functions of the one or more centralized units of one of the plurality of network slices are logically isolated from at least one of one or more user plane portions, one or more access and mobility functions, one or more user plane functions, and one or more session management functions of the one or more centralized units of another of the plurality of network slices; one or more remote radio units, one or more distributed units, and one or more control plane portions of the one or more centralized units are common to all network slices in the plurality of slices.

8. The method of claim 6, wherein at least one of the one or more user plane portions, the one or more user plane functions, and the one or more session management functions of the one or more centralized units of one of the plurality of network slices are logically isolated from at least one of one or more user plane portions, one or more user plane functions, and one or more session management functions of the one or more centralized units of another of the plurality of network slices; one or more remote radio units, one or more distributed units, one or more control plane portions of the one or more centralized units, and one or more access and mobility functions are common to all network slices in the plurality of slices.

9. The method of claim 8, wherein, the transmission further comprises: transmitting data associated with the user equipment using the plurality of network slices.

10. The method of claim 6, wherein at least one of the one or more distributed units, one or more control plane portions of the one or more centralized units, the one or more user plane portions of the one or more centralized units, the one or more access and mobility functions, the one or more user plane functions, and the one or more session management functions of one of the plurality of network slices are logically isolated from at least one of one or more distributed units, one or more control plane portions of the one or more centralized units, one or more user plane portions of the one or more centralized units, one or more access and mobility functions, one or more user plane functions, and one or more session management functions of another of the plurality of network slices; one or more remote radio units are common to all network slices in the plurality of slices.

11. The method of claim 6, wherein at least one of the one or more distributed units, the one or more user plane portions of the one or more centralized units, the one or more user plane functions, and the one or more session management functions of one network slice of the plurality of network slices is logically isolated from at least one of one or more distributed units, one or more user plane portions of the one or more centralized units, one or more user plane functions, and one or more session management functions of another network slice of the plurality of network slices; the one or more remote radio units, the one or more control plane portions of the one or more centralized units, and the one or more access and mobility functions are common to all network slices of the plurality of slices.

12. The method of claim 11, wherein, the transmission further comprises: transmitting data associated with the user device using the plurality of network slices.

13. The method of claim 6, wherein at least one of the one or more remote radio units, the one or more distributed units, the one or more control plane portions of the one or more centralized units, the one or more user plane portions of the one or more centralized units, the one or more access and mobility functions, the one or more user plane functions, and the one or more session management functions of one network slice of the plurality of network slices is logically isolated from at least one of one or more remote radio units, one or more distributed units, one or more control plane portions of the one or more centralized units, one or more user plane portions of the one or more centralized units, one or more access and mobility functions, one or more user plane functions, and one or more session management functions of another network slice of the plurality of network slices.

14. A network slice apparatus comprising: at least one programmable processor; and a non-transitory machine-readable medium storing instructions that, when executed by the at least one programmable processor, cause the at least one programmable processor to perform operations comprising: determining a profile of a plurality of network slices of a wireless communication system, each network slice of the plurality of network slices having one or more communication components logically isolated from one or more communication components of another network slice of the plurality of network slices; selecting a network slice of the plurality of network slices for transmitting data associated with a user device based on the determined profile and a request received from the user device; transmitting data associated with the user device using the selected network slice; and determining, based on at least one parameter in a profile of the network slice of the plurality of network slices, at least one communication component of the network slice for isolation; wherein the at least one parameter comprises at least one of: a latency requirement, a number of user devices using the network slice, a number of tracking areas associated with the network slice, a mobility level of user devices using the network slice, an activity of the network slice, a required level of isolation, and any combination thereof.

15. The apparatus of claim 14, wherein, The operations further comprise: monitoring transmission of data using the selected network slice; selecting, based on the monitoring, another configuration of the network slice for transmission of data in a plurality of network slice configurations; and transmitting data associated with the user device using the other selected network slice configuration.

16. The apparatus of claim 15, wherein, The operations further comprise selecting one or more distributed units for transmission of data based on at least one of: one or more component carriers, one or more bandwidth parts, one or more physical resource block ranges, and any combination thereof.

17. The apparatus of claim 14, wherein, The operations further comprise: virtualizing one or more logically isolated components; and instantiating, based on the at least one parameter, one or more of the virtualized logically isolated components.

18. The apparatus of claim 17, wherein, At least one of the determining, the selecting, and the transmitting is performed by a base station.

19. The apparatus of claim 18, wherein, The base station comprises at least one of the following communication components: one or more remote radio units, one or more centralized units, one or more distributed units, one or more control plane portions of the one or more centralized units, one or more user plane portions of the one or more centralized units, one or more access and mobility functions, one or more user plane functions, and one or more session management functions.

20. The apparatus of claim 19, wherein, at least one of the one or more user plane portions of the one or more centralized units, the one or more access and mobility functions, the one or more user plane functions, and the one or more session management functions of one network slice of the plurality of network slices is logically isolated from at least one of one or more user plane portions of the one or more centralized units, one or more access and mobility functions, one or more user plane functions, and one or more session management functions of another network slice of the plurality of network slices; one or more remote radio units, one or more distributed units, and one or more control plane portions of the one or more centralized units are common to all network slices of the plurality of slices.

21. The apparatus of claim 19, wherein at least one of the one or more distributed units of one of the plurality of network slices, one or more control plane portions of the one or more centralized units, the one or more user plane portions of the one or more centralized units, the one or more access and mobility functions, the one or more user plane functions, and the one or more session management functions are logically isolated from at least one of one or more distributed units, one or more control plane portions of the one or more centralized units, one or more user plane portions of the one or more centralized units, one or more access and mobility functions, one or more user plane functions, and one or more session management functions of another of the plurality of network slices; one or more remote radio units, one or more distributed units, one or more control plane portions of the one or more centralized units, and one or more access and mobility functions are common to all network slices in the plurality of slices.

22. The apparatus of claim 21, wherein, the transmission further comprises: transmitting data associated with the user equipment using the plurality of network slices.

23. The apparatus of claim 19, wherein at least one of the one or more distributed units of one of the plurality of network slices, one or more control plane portions of the one or more centralized units, the one or more user plane portions of the one or more centralized units, the one or more access and mobility functions, the one or more user plane functions, and the one or more session management functions are logically isolated from at least one of one or more distributed units, one or more control plane portions of the one or more centralized units, one or more user plane portions of the one or more centralized units, one or more access and mobility functions, one or more user plane functions, and one or more session management functions of another of the plurality of network slices; one or more remote radio units are common to all network slices in the plurality of slices.

24. The apparatus of claim 19, wherein at least one of the one or more distributed units of one of the plurality of network slices, one or more control plane portions of the one or more centralized units, the one or more user plane portions of the one or more centralized units, the one or more access and mobility functions, the one or more user plane functions, and the one or more session management functions are logically isolated from at least one of one or more distributed units, one or more control plane portions of the one or more centralized units, one or more user plane portions of the one or more centralized units, one or more access and mobility functions, one or more user plane functions, and one or more session management functions of another of the plurality of network slices; one or more remote radio units, one or more control plane portions of the one or more centralized units, and one or more access and mobility functions are common to all network slices in the plurality of slices.

25. The apparatus of claim 24, wherein, the transmission further comprises: transmitting data associated with the user equipment using the plurality of network slices.

26. The apparatus of claim 19, wherein At least one of the one or more remote radio units, the one or more distributed units, one or more control plane portions of the one or more centralized units, the one or more user plane portions of the one or more centralized units, the one or more access and mobility functions, the one or more user plane functions, and the one or more session management functions of one network slice of the plurality of network slices is logically isolated from at least one of one or more remote radio units, one or more distributed units, one or more control plane portions of the one or more centralized units, one or more user plane portions of the one or more centralized units, one or more access and mobility functions, one or more user plane functions, and one or more session management functions of another network slice of the plurality of network slices.

27. A computer program product comprising a non-transitory machine-readable medium storing instructions that, when executed by at least one programmable processor, cause the at least one programmable processor to perform operations comprising: determining a profile of a plurality of network slices of a wireless communication system, each network slice of the plurality of network slices having one or more communication components logically isolated from one or more communication components of another network slice of the plurality of network slices; selecting, based on the determined profile and a request received from a user device, a network slice of the plurality of network slices for transmission of data associated with the user device; transmitting the data associated with the user device using the selected network slice; and determining, based on at least one parameter in the profile of the network slice of the plurality of network slices, at least one communication component of the network slice for isolation; wherein the at least one parameter comprises at least one of: a latency requirement, a number of user devices using the network slice, a number of tracking areas associated with the network slice, a mobility level of user devices using the network slice, an activity of the network slice, a required level of isolation, and any combination thereof.

28. The computer program product of claim 27, wherein, The operations further comprise: monitoring transmission of data using the selected network slice; selecting, based on the monitoring, another configuration of the network slice for transmission of data in a plurality of network slice configurations; and transmitting the data associated with the user device using the other selected network slice configuration.

29. The computer program product of claim 27, wherein, The operations further comprise selecting one or more distributed units for transmission of data based on at least one of: one or more component carriers, one or more bandwidth parts, one or more physical resource block ranges, and any combination thereof.

30. The computer program product of claim 27, wherein, The operations further comprise: virtualizing one or more logically isolated components; and instantiating the one or more virtualized logically isolated components based on the at least one parameter.

31. The computer program product of claim 30, wherein, At least one of the determining, the selecting, and the transmitting is performed by a base station.

32. The computer program product of claim 31, wherein, The base station comprises at least one of the following communication components: one or more remote radio units, one or more centralized units, one or more distributed units, one or more control plane portions of the one or more centralized units, one or more user plane portions of the one or more centralized units, one or more access and mobility functions, one or more user plane functions, and one or more session management functions.

33. The computer program product of claim 32, wherein at least one of the one or more user plane portions of the one or more centralized units, the one or more access and mobility functions, the one or more user plane functions, and the one or more session management functions of one network slice of the plurality of network slices is logically isolated from at least one of one or more user plane portions of the one or more centralized units, one or more access and mobility functions, one or more user plane functions, and one or more session management functions of another network slice of the plurality of network slices; one or more remote radio units, one or more distributed units, and one or more control plane portions of the one or more centralized units are common to all network slices of the plurality of slices.

34. The computer program product of claim 32, wherein at least one of the one or more user plane portions of the one or more centralized units, the one or more user plane functions, and the one or more session management functions of one network slice of the plurality of network slices is logically isolated from at least one of one or more user plane portions of the one or more centralized units, one or more user plane functions, and one or more session management functions of another network slice of the plurality of network slices; one or more remote radio units, one or more distributed units, one or more control plane portions of the one or more centralized units, and one or more access and mobility functions are common to all network slices of the plurality of slices.

35. The computer program product of claim 34, wherein, The transmission further comprises: transmitting data associated with the user device using the plurality of network slices.

36. The computer program product of claim 32, wherein at least one of the one or more distributed units, the one or more control plane portions of the one or more centralized units, the one or more user plane portions of the one or more centralized units, the one or more access and mobility functions, the one or more user plane functions, and the one or more session management functions of one of the plurality of network slices are logically isolated from at least one of the one or more distributed units, the one or more control plane portions of the one or more centralized units, the one or more user plane portions of the one or more centralized units, one or more access and mobility functions, one or more user plane functions, and one or more session management functions of another of the plurality of network slices; the one or more remote radio units are common to all network slices in the plurality of slices.

37. The computer program product of claim 32, wherein at least one of the one or more distributed units, the one or more user plane portions of the one or more centralized units, the one or more user plane functions, and the one or more session management functions of one of the plurality of network slices are logically isolated from at least one of the one or more distributed units, the one or more user plane portions of the one or more centralized units, one or more user plane functions, and one or more session management functions of another of the plurality of network slices; the one or more remote radio units, the one or more control plane portions of the one or more centralized units, and the one or more access and mobility functions are common to all network slices in the plurality of slices.

38. The computer program product of claim 37, wherein, the transmission further comprises: transmitting data associated with the user equipment using the plurality of network slices.

39. The computer program product of claim 32, wherein at least one of the one or more remote radio units, the one or more distributed units, the one or more control plane portions of the one or more centralized units, the one or more user plane portions of the one or more centralized units, the one or more access and mobility functions, the one or more user plane functions, and the one or more session management functions of one of the plurality of network slices are logically isolated from at least one of the one or more remote radio units, the one or more distributed units, the one or more control plane portions of the one or more centralized units, the one or more user plane portions of the one or more centralized units, one or more access and mobility functions, one or more user plane functions, and one or more session management functions of another of the plurality of network slices.

Images