TWI815789B - Ran re-architecture for network slicing - Google Patents

Abstract

Embodiments provide a radio access network (RAN) control entity apparatus operable in a wireless communication network, the apparatus comprising radio frequency (RF) circuitry to receive at least one communication originating from a wireless network device or transmit at least one communication to a wireless network device, wherein the RAN control entity is coupled to a baseband unit (BBU) and remote radio head (RRH), and circuitry to partition a physical RAN infrastructure or C-RAN into one or more network slices, and partition the BBU and/or RRH according to a deployment scenario of the one or more network slices.

Description

Radio Access Network (RAN) re-architecture technology for network slicing

Embodiments described herein relate generally to the field of wireless communication systems, and more particularly to the management of radio access networks of a wireless communication system.

Implementation aspects of the present invention may generally relate to the field of wireless communications.

According to an embodiment of the present invention, a device for a radio access network (RAN) control entity operable in a wireless communication network is specifically proposed. The RAN control entity is coupled to a base frequency unit (BBU) and a remote From the radio head (RRH), the equipment includes: radio frequency (RF) circuitry that receives at least one communication from or transmits at least one communication to a wireless network device; and circuitry, It: divides a physical RAN infrastructure or cloud radio access network (C-RAN) into one or more network slices; and divides the BBU and/or RRH according to one of the deployment scenarios of the one or more network slices .

The following detailed description refers to the accompanying drawings. The same reference numbers may be used in the different drawings to identify the same or similar elements. In the following description, for the purpose of explanation rather than limitation, specific details such as specific structures, architectures, interfaces, technologies, etc. are provided so that various aspects of the present disclosure can be thoroughly understood. However, one of ordinary skill in the art having the benefit of this disclosure will understand that various aspects of the claimed scope may be practiced in other instances that depart from these specific details. In some instances, descriptions of well-known devices, circuits, and methods are omitted to avoid obscuring the disclosure with unnecessary detail.

The following detailed description refers to the accompanying drawings. The same reference numbers may be used in the different drawings to identify the same or similar elements. In the following description, for the purpose of explanation rather than limitation, specific details such as specific structures, architectures, interfaces, technologies, etc. are provided so that various aspects of the present disclosure can be thoroughly understood. However, one of ordinary skill in the art having the benefit of this disclosure will understand that various aspects of the claimed scope may be practiced in other instances that depart from these specific details. In some instances, descriptions of well-known devices, circuits, and methods are omitted to avoid obscuring the disclosure with unnecessary detail.

In the fourth generation long-term evolution technology (4G-LTE) and advanced LTE/professional wireless communication networks, heterogeneity in network architecture and applications has become a trend. Examples of these trends are the development of small cell and relay networks, device-to-device (D2D) communication networks (also known as proximity services), and machine type communications (MTC). A sub-cell may be considered any cell form smaller than a traditional macro eNB/BS (e.g. micro/pico/femto cell). After entering the fifth generation (5G) wireless communication network, this heterogeneous trend may become more significant, and improved methods and equipment suitable for controlling wireless resources are expected. For example, because 5G wireless communication networks are expected to serve a wide variety of applications (with various traffic types and requirements), network and user equipment (with various communication and computing capabilities), and be different from more traditional Commercial markets (i.e. use cases) for voice services (e.g. Voice over LTE (VoLTE)) and mobile broadband (MBB) and therefore the desire to control each of these use cases so that it is possible to optimize, or at least improve, the use of these wireless resources .

Embodiments of the present disclosure generally relate to slicing of a radio access network (RAN) architecture of a wireless communication network. The RAN may be part of the wireless communications network implementing one or more radio access technologies (RATs) and may be considered resident between a user device (UE) such as a mobile phone, smartphone, connected laptop, etc. A location between a laptop, or any remotely controlled (or simply accessible) machine, and provides a connection to the Core Network (CN) that serves the wireless communications network. The RAN may be implemented using silicon chip(s), resident on the UEs and/or base stations, such as enhanced Node Bs (eNBs), base stations, or the like, forming a cellular-based wireless communication network. /system. Examples of RAN include, but are not limited to: GRAN (a GSM radio access network); GERAN (essentially an EDGE-enabled GRAN); UTRAN (a UMTS radio access network); and E-UTRAN (an LTE or advanced LTE/professional high-speed and low-latency radio access network).

The embodiments described herein discuss a general network slicing architecture in a radio access network of a wireless communication network, such as, but not limited to, a 5G wireless communication network. In particular, embodiments may include the concepts of horizontal and vertical network slicing. Vertical slicing can include slicing the radio access network according to vertical markets, from many existing and new types of communications (which can be implemented through future wireless communication networks, including especially radio access networks), one of which A vertical market may encompass a single/specific type of communication (i.e., it may be defined as a single or specific use case for the communication involved). A commercial market that can be deployed in a wireless communication network can also be called a vertical market. These existing types include mobile broadband (MBB) and voice (VoLTE), while new communication types can include new types of connectivity services and use cases, such as machine type communication (MTC), personal area network, dedicated health Networking, machine-to-machine (M2M), enhanced MBB (eMBB), time-critical communications, vehicle-to-everything (V2X) (including workshop-to-vehicle (V2V) and vehicle-to-infrastructure (V2I)), and the like. The definition of a vertical market is not limiting and will include any existing or future logical division (i.e., segregation, segmentation, or the like) of a physical radio access network dedicated to a particular purpose, or type of communication by wireless communications . In some examples, there may be multiple physical radio access networks used, each divided into logically separated radio access networks.

The proposed network slicing can be planable, highly scalable and flexible, taking into account the availability, latency and power requirements of the wireless communication network required for each specific use case and the impact on battery life, reliability and capacity. , safety and speed.

Network slicing is regarded as one of the key technologies used to meet the diverse requirements and diverse services and applications expected to be supported in 5G communication networks. This is because in wireless communications technology, the challenge of further improving spectral efficiency at the radio link level is increasing, so new ways have been discovered to build future wireless networks and devices served by those wireless networks , to meet increasing capacity requirements. To achieve these goals, 5G and future generations of wireless networks, and especially the wireless devices that serve or are served by those wireless networks, are continuing to evolve to combine computing and communications and deploy end-to-end end solution. This is a paradigm shift from previous generations, where technology development focused solely on single-layer communications.

If the capacity of a wireless network is to be increased, it can be achieved by slicing it. This may involve slicing (i.e., logically dividing/partitioning) traditional large, single, mobile broadband networks into multiple virtual networks to serve vertical industries and applications in a more cost- and resource-efficient manner. Each network slice can have a different network architecture, as well as different application, control, packet and signal processing capabilities and capacities to achieve the best return on investment. Vertical slicing (i.e., industry or type of service) can be added to an existing scalable wireless network at any time, rather than deploying a new dedicated wireless network for that vertical market. Vertical network slicing thus provides a practical means of isolating traffic from a vertical application perspective from the rest of the general mobile broadband service, thereby effectively avoiding or significantly simplifying traditional QoS engineering issues. Wireless network slicing can include slicing in both the core network and the radio access network (ie, an end-to-end solution).

In wireless networks of 5G and above, the capacity expansion and contraction of a network is no longer so uniform compared to previous generations. For example, the scaling factor may be higher when the wireless network is closer to a user and lower as we move deeper into the wireless network's infrastructure. This non-uniform scaling may result from an enhanced user experience, enabled by significantly increased sensing capabilities (and/or processing resources) available at wireless devices utilizing wireless networks. Unlike previous generations of wireless networks where a network served primarily as a data conduit, which scaled evenly (but singularly) end-to-end as the air interface improved, 5G and future generations of wireless networks can at least Partially relies on information networks, including the diverse (heterogeneous and/or homogeneous) computing, network connectivity and storage capabilities of such wireless networks and the wireless devices that serve/receive services.

For example, the overall wireless network will continue to expand rapidly, but the computing and network connections at the edge of the network will grow even faster, so that user data traffic can be processed at the edge of the wireless network (so-called edge cloud applications). User devices can no longer be simply "terminals" terminating a communications link. Instead, it can become a new generation of mobile or fixed network nodes for a new generation of consumer devices, machines, and tools. For example, a laptop, a smartphone, a home gateway, or any other wireless network device (or the component devices that form such a wireless network device, or are sold as part thereof to consumers) may become A network cluster of many devices or tools deployed around a computing and networking device. For example, it may form a Personal Area Network (PAN). Many of these mobile or fixed wireless network devices can form what can be called an underlay network, a new type of network in 5G and beyond technologies, with devices capable of communicating directly with each other or with fixed networks, and with There are computations that can be offloaded to larger form factor platforms or edge cloud base stations (i.e., entities in the wireless network with larger processing resources, either entirely or simply available at that moment). This can be accomplished through a virtualization platform that includes the edge cloud across many devices for optimal mobile computing and communications.

The scaling of this new category of wireless networks can be driven by several factors. For example, since device sensing is typically local, processing of sensed data can be local, and decisions and actions based on sensed data become local. This trend can be further amplified by the growth of wearable devices and the Internet of Things. For example, when machines begin to play a larger role in communications than human users, overall communications link speeds can be increased.

As the number of communication links increases in proximity to users and user devices, the definition of end-to-end must be discussed again. Therefore, it is proposed to provide a cloud architecture framework that can be integrated into data centers and edge clouds to provide local intelligence and services closer to end users or devices. This could be, for example, because as wireless networks and systems are deployed in businesses, homes, offices, factories and cars, edge cloud servers become more important for performance and information privacy and security. These latter factors may be driven by growing user (and government) concerns about privacy and security. In addition, data centers embedded in these fixed networks will continue to grow rapidly as many existing services can leverage centralized architectures, leverage new generations of portable and wearable devices, drones, industrial machines, autonomous vehicles, and Similar services can be served more appropriately at the edge of the network and around users, promoting faster growth in communication and computing capabilities.

This newly introduced network slicing concept, specifically one that provides a wireless network system architecture with end-to-end (E2E) vertical and horizontal network slicing, can be used for air interfaces, radio access networks (RAN) and core network (CN) to bring about changes to implement a wireless network system with E2E network slicing.

In short, horizontal slicing works by sharing computing resources among devices serving or being served on (i.e., within or above) the wireless network, based on the processing needs of those devices over time and space/location. to enhance device capabilities.

Horizontal network slicing is designed to adapt to new traffic scaling trends and enable edge cloud computing and computing offloading: computing resources in base stations and portable devices can be sliced horizontally, and these can be integrated with wearable devices Slicing to form a virtual computing platform through a new wireless air interface design as described in this article to significantly expand the computing capabilities of future portable and wearable devices. Horizontal slicing expands device capabilities and enhances user experience.

In the most general terms, network slicing can be thought of as a method that uses virtualization technology to structure, divide and organize the computing and communication resources of a physical wireless network infrastructure into one or more logically partitioned The radio access network can flexibly support the implementation of various use cases. For example, with runtime network slicing, a physical wireless network can be divided into multiple logical radio access networks, each structured and optimized to meet a specific requirement and/or a specific application/service ( i.e. use cases). Therefore, a network slice can be defined as self-contained in terms of operations and traffic, and can have its own network architecture, engineering mechanisms, and network deployment. Network slicing, as proposed in this article, can simplify the creation and operation of network slicing and allow functional reuse and resource sharing (i.e., provide efficiency) of the physical wireless network infrastructure while still being served by the wireless network. Wireless devices provide sufficient wireless network resources (communication and processing resources).

Vertical slicing is designed to support diverse services and applications (ie, use cases/types of communications). Examples include, but are not limited to: wireless/mobile broadband (MBB) communications; extreme mobile broadband (E-MBB) communications; real-time use cases such as industrial control communications, machine-to-machine communications (MTC/MTC1); such as the Internet of Things (IoT) ) Sensor communication, or non-real-time use cases of large-scale machine-to-machine communication (M-MTC/MTC2); ultra-reliable machine-to-machine communication (U-MTC); mobile edge cloud such as cache and communication; workshop (V2V) ) communication; communication between vehicles and infrastructure (V2I); communication between vehicles and anything (V2X). That is, the present disclosure relates to providing network slicing based on any easily definable/differentiable communication type that can be implemented over a wireless network. Vertical network slicing enables resource sharing among services and applications and can avoid or simplify traditional QoS engineering issues.

At the same time, horizontal network slicing aims to extend the capabilities of devices in wireless networks, especially mobile devices that may have limited local resources available to them, and enhance user experience. Horizontal network slicing operates across and beyond the physical boundaries of the hardware platform. Horizontal network slicing enables resource sharing between network nodes and devices, i.e., highly capable network nodes/devices can then share their resources (i.e., computing, communications, storage) to enable less capable network nodes/devices. Road nodes/devices enhance their capabilities. A simple example could be to use a network base station and/or a smartphone mobile device to supplement the processing and communication capabilities of a wearable device. One end result of horizontal network slicing may be to provide a new generation mobile (eg mobile) underlying network cluster, where mobile terminals become mobile network connection nodes. Horizontal slicing provides over-the-air resource sharing between wireless network nodes. The wireless network air interface used may be an integrated part of the horizontal slice and an enabler.

Vertical network slicing and horizontal network slicing can form independent slices. End-to-end traffic in a vertical slice can be moved between the core network and end devices. End-to-end traffic in a horizontal slice can be localized and shifted between clients and hosts in a mobile edge computing service.

In vertical slicing, each network node can implement similar functions in different slices. One dynamic aspect of vertical slicing can primarily fall into resource partitioning. However, in horizontal slicing, new functionality can be built at a network node when all slicing is supported. For example, a portable device may use different functions to support different types of wearable devices. The dynamic aspect of horizontal slicing can therefore fall within the partitioning of network functions and resources.

Figure 1 shows a first view of the broad concept of vertical and horizontal network slicing. A complete wireless network 100 is shown, including multiple vertical slices 110 to 140, each serving a different (or at least segmented) vertical market, or use case. In the example shown, vertical slice #1 110 servo mobile broadband communications, vertical slice #2 120 servo shop floor communications, vertical slice #3 130 servo safety communications, and vertical slice #4 140 servo industrial control communications. These are only illustrative use cases, and there are virtually no limitations to the use cases that can be served by a switchable wireless network in accordance with the present disclosure.

The wireless network 100 includes a core network layer part 150 (for example, having multiple servers/control entities/control parts of eNode-B, etc.), a radio access network layer part 160 (for example, including multiple base stations). station, e-Node B, etc.), a device layer part 170 (including portable devices such as UEs, vehicles, surveillance devices, industrial devices, etc.), and a human/wearable layer part 180 (including, for example, wearable devices, Such as smart watches, health monitors, GoogleTM Glasses/MicrosoftTM Holographic Lens type devices and the like). This wearable segment can only cover some use cases, as shown by vertical slices #1 and #2 in the example of Figure 1 where it is included only.

In this vertical domain, the physical computing/storage/radio processing resources (such as servers and base stations 150/160), and the physical radio resources (in terms of time, frequency and space) in the network infrastructure are determined by use cases ( i.e. communication type) are sliced to form end-to-end vertical slices. In the horizontal domain, physical resources (in terms of computing, storage, radio) in adjacent layers of the network hierarchy are sliced to form horizontal slices. In the example shown, there is a first horizontal network slice 190 operating between the RAN 160 and device 170 layers, and a second horizontal network slice 195 operating between the device 170 and wear 180 layers. Any given device served or to be served by wireless network 100 in its entirety, and RAN 160 (and the layers below) in particular, may operate on multiple network slices, of either (or both) type. For example, a smartphone can operate in a vertical slice on mobile broadband (MBB) services, a vertical slice on health care services, and a horizontal slice on support for wearable devices.

When implementing network slicing in the RAN (including air interfaces used in this RAN), in addition to complying with 5G requirements (e.g., data rate, latency, number of connections, etc.), these RAN/air interfaces are used to implement Further desirable characteristics of network slicing, and 5G in general, may include flexibility (i.e., supporting flexible radio resource allocation among slices); scalability (i.e., being easily expanded with the addition of new slices); and Efficiency (e.g. efficient use of radio and energy resources).

Horizontal slicing may include slicing network layers, such as network connectivity and computing (ie, processing resource) capability layers. This can be done across any number of vertical slices served by network 100, for example, from all vertical markets down to anything within one or more vertical slices. This is shown as two exemplary horizontal slices of different widths in Figure 1 - horizontal slice #1 190 is limited to a single vertical slice, while horizontal slice #2 encompasses two vertical slices. Examples of network layers/layers may include, but are not limited to, a macro network layer, a micro/small cell network layer, an inter-device communication layer, and the like. Other network layers may also be involved.

FIG. 2 shows a second view 200 of a portion of the wireless network 100 of FIG. 1 . In particular, Figure 2 shows an example of a specific sliced RAN architecture, where slices can span multiple layers of a traditional wireless network architecture. For example, the RAN architecture of each slice can be dynamically configured depending on factors such as traffic type, traffic load, QoS requirements, etc. In a first example, slice #1 210 only operates at the macro cell level. Slice #2 220 only operates at the small cell level. Finally, slice #3 230 operates at both macro and small cell levels. In another example, one slice (eg, slice #1 210) may operate on small cells, while another slice (eg, slice #3 230) may end up operating on some of these small cells.

Expanding/activating a slice can be referenced as a network slice opening, while deactivating/deactivating a slice can be referenced as a network slice closing. This specific slicing RAN architecture may require specific slicing control plane/user plane operations, slicing on/off operations, and access control and load balancing slicing processing, which will be discussed in more detail below.

Horizontal slicing, which includes slicing network/device computing and communication resources, can achieve computing offloading. Examples include a base station using a slice of its computing resources to help a user device perform computing, or a user device (such as a smartphone) using a slice of its computing resources to help one (more) associated wearable devices perform computing. .

Embodiments of the present disclosure are not limited to any specific form of slicing along the vertical (market) or horizontal (network hierarchy/tier) direction.

Embodiments of the present disclosure can provide a management entity that can operate across the control plane (C plane) and/or the user plane (U plane), which can provide a management plane entity for coordinating the operation of different slices, which can be horizontal Or vertical (or multiple/combined, or partial, or several thereof) slices. This management entity may use a flat management structure or a hierarchical management structure.

Slicing of the radio access network can be seen as slicing the radio access network according to predetermined vertical markets of the network, or horizontal network layers (or multiple/partial layers). This can be considered a form of logical separation between the radio resources provided by or used by the radio access network. Logical partitioning of such wireless resources may allow them to be defined, managed, and/or provisioned (generally or specifically) separately. This separation allows different slices to have the ability to be unable or not allowed to affect each other. Likewise, in some embodiments, one or more slices may specifically be provided with the ability to manage another slice or slices for operations.

In some embodiments, network functions can be completely offloaded to a network slice, and the slice can operate in a discrete mode, such as a discrete millimeter wave (mmWave) small cell network, and an out-of-range D2D Internet. A mmWave small cell is a cell that uses millimeter-sized radio waves (i.e., high frequencies, such as 60 GHz).

In some embodiments, network function(s) may be partially offloaded to a slice, and the slice may operate in a non-discrete mode, such as in an anchor-backed architecture where an anchor- The support architecture may include an anchor cell that provides a control plane and a mobility anchor for maintaining connectivity. In one embodiment, the anchor cell may be a cell with a wide coverage range, such as a macro cell. The anchor-supported architecture may further include an amplifier cell to provide user plane data offloading. In one embodiment, the amplifier cell may be a small cell and may be deployed within the coverage of an anchor cell. From a device perspective, the control plane can be decoupled from the user plane, that is, the control plane can be maintained at the anchor cell, and the data plane can be maintained at the amplifier cell.

In some exemplary embodiments, these horizontal slices and vertical slices may be viewed as interleaved (i.e., where radio access network functions/resources are shared between the vertical and horizontal slices), as shown in diagram 300 of FIG. 3 . Therefore, FIG. 3 shows how a radio access network (RAN) can be sliced into horizontal and vertical slices according to an embodiment that is an alternative (or additional) to the embodiment shown in FIG. 1 , where this Equal slices are all independent in terms of traffic flow and operation. The diagram 300 of Figure 1 has the network hierarchy 302 along the y-axis (i.e., the network layers involved/used), and the radio resources 304 along the x-axis (i.e., indicating the use of separate radio resources, such as frequencies, time slots, etc. ). In the example of FIG. 1 , the vertical slices shown include four vertical slices 306 . However, any number of different markets/use cases can be addressed. The four vertical markets/use cases shown selected for these vertical slices are Mobile Broadband (MBB) 110, One Vehicle-to-Everything (V2X) 120, One Machine Type 1 (MTC-1) 130, One Second Machine Type Communications (MTC-2) 140, labeled slices Slice#1 to Slice#4. These are just illustrative choices of use cases that can be served.

Horizontal slices are also shown in Figure 3. In this example, there are also four horizontal slices 308. The four horizontal slices shown are macro network layer 210, micro network layer 220, inter-device network layer 230, and personal area network (PAN) (eg, wearable) network layer 240. According to an example, each horizontal slice contains a portion of a plurality of vertical slices. Likewise, each vertical slice contains a portion of each horizontal slice. If these separated parts are divided along both horizontal and vertical directions, they can be called sliced parts. Therefore, in the example of FIG. 1, MBB vertical slice 110 includes four slice parts: macro network layer part 112; micro network layer part 114; D2D network layer part 116; and PAN network layer part 118. Similarly, the V2X vertical slice 120 includes four slice parts: a macro network layer part 122; a micro network layer part 124; a D2D network layer part 126; and a PAN network layer part 128. Meanwhile, MTC-1 vertical slice 130 includes four slice parts: macro network layer part 132; micro network layer part 134; D2D network layer part 136; and PAN network layer part 138, while MTC-2 vertical Slice 140 includes four slice parts: macro network layer part 142; micro network layer part 144; D2D network layer part 146; and PAN network layer part 148.

One example of this architecture is a wearable health sensor in a personal area network, which may belong to a dedicated health network. This personal area network layer may then represent a horizontal network slice. The health network running under the coverage area of this personal area network may belong to a vertical network slice. Within the same token, each horizontal network slice can contain multiple vertical network slices. Each vertical network slice can have multiple horizontal network slices. Another example is a macro cell (ie macro eNB) that serves several different use case communications. Likewise, each vertical slice may, for example, be part of multiple horizontal slices in a V2X network, and may have V2I and V2V layers. In another example, a mobile broadband (MBB) vertical slice includes portions in each of the macro, micro, and inter-device layers, as shown. Therefore, embodiments provide a way to logically partition the radio resources provided and/or used by the radio access network based on both use cases (vertical approach) and network layer (horizontal approach).

Communications and computing have collaborated in pushing the boundaries of information and computing technologies. On the network side, computing has been used to facilitate communications by moving computing and storage to the edge. With edge cloud and edge computing, the communication between source and destination is shortened, thereby improving communication efficiency in the network and reducing the amount of information dissemination. Edge clouds and computing solutions have different optimal deployments. As a general rule, the smaller the capabilities of the end devices and/or the higher the device density, the closer the cloud and computing are to the edge of the network.

As device sides move forward, as devices become smaller in size from portable to wearable, and as users' expectations for computing continue to increase, we expect further communication will help deliver the user experience , for example, the network nodes are carved out of their computing resources to facilitate computing at the portable device, and the portable devices are carved out of their computing resources to facilitate computing at the wearable device. Operation. In this way, the network can be sliced horizontally. These cut-out computing resources and the air interface connecting both ends form an integral part of delivering the required services.

Figure 4 shows a more detailed example of horizontal slicing in a scalable wireless network architecture, according to an embodiment. The left hand side shows the traditional 3G/4G architecture (but only starting from RAN and going down). This includes a base station portion 410, including an upstream/core network-side communications function 412, a base station computing function 414 (i.e., the processing resources available in the base station, or closely coupled entities thereof), and a downstream/wireless/ Device-side communication function 416 (used to communicate with the device served by the base station or peer base station, for example, in fronthaul, etc.). Also shown is a portable portion 420 (such as a user equipment, or a similar device) that contains a similar combination of upstream and downstream communication resources and local processing resources. In this case, the upstream communication link is a typical cellular wireless communication link 422 (eg, OFDM/CDMA/LTE type link) and a 5G Radio Access Technology (RAT) (eg, OFDM/CDMA/ One of the downstream communication links 426 of an LTE type link), one of the next generation communication link(s) such as a 5G PAN RAT (yet to be established), or a current or next generation other PAN wireless communication technology, such as Bluetooth, zigbee or similar. In between are the local computing functions 424, that is, the processing resources local to the portable device. Finally, in this example, there is the wearable portion 430, which typically has only a single upstream communication link 432 and limited local processing resource functionality 434.

The right-hand side of Figure 4 shows one of the newly proposed concepts of horizontal network slicing, specifically how the processing resources of entities higher and lower in the network can be "combined" using the communication and processing resource capabilities of the participating entities. , that is, shared with each other. The basic functions are similar and are therefore designated as items 410' to 434' respectively, and act in a similar manner. However, there is now the concept of horizontal slices, in this case horizontal slices #1 190 and #2 195 of Figure 1 are shown in more detail. In this basic example, the wearable device 430' can utilize the processing resources 424' of the portable device 420' by sharing processing data (e.g., data to be processed and integrated processing data) using communication functions. Similarly, portable device 420' can use base station 410' processing resources 414'.

Next, based on this disclosure, part of the network slicing concept will be explained in more detail. In some examples, these functions may be provided as new network functions (NFs), which may be virtualized in some cases, such as by using network functions virtualization (NFV). These NFs and NFVs can be slice specific, or operate on multiple/all slices. The proposed wireless network is both as a whole (e.g., including the core network), but in particular, the RAN will now be slice-aware by leveraging the newly implemented slice awareness.

Among traditional RAN infrastructures, a centralized processing cloud-based RAN (Cloud (C)-RAN) infrastructure has been proposed. In C-RAN, unlike traditional cellular systems, a central pool of baseband processing units (BBUs) performs most of the baseband processing, while the remote radio heads (RRHs) perform the transmission and reception of radio signals. . This C-RAN architecture can improve energy efficiency by merging energy-consuming hardware devices into a BBU/BBU pool. This C-RAN architecture can also reduce both the CAPEX and OPEX of a network by making centralized network management and network upgrades easier to complete. In addition, this C-RAN architecture can be used to implement advanced coordinated multipoint (CoMP) communication and interference management solutions, such as advanced inter-cell interference coordination (eICIC).

Figure 5 illustrates a typical C-RAN architecture 500. RRHs 502, 504, and 506 may send and receive wireless signals from wireless-capable devices, such as user equipment (UE). The RRHs 502, 504 and 506 may communicate with a BBU/BBU pool 514 via fronthaul links 516, 518 and 520 respectively. Fronthaul is the connection between a new network architecture of centralized baseband controllers and long-distance discrete radio heads at cell sites. A common public radio interface (CPRI) may be the type of interface used to connect RRHs 502, 504 and 506 to the BBU/BBU pool 514 via fronthaul links 516, 518 and 520. BBU/BBU pool 514 can communicate with a core network 522. In one example, a communication from core network 522 to one of the wireless devices 524 in one of the coverage devices of RRH 502 (or RRH 504 or RRH 506) may be sent from core network 522 to BBU/BBU pool 514. BBU/BBU pool 514 may then send this communication to RRH 502 (or RRH 504 or RRH 506) via fronthaul link 516 (or via fronthaul link 518 or fronthaul link 520, respectively). This communication may then be sent from RRH 502 (or RRH 504 or RRH 506) to wireless device 524 via a radio signal. This is typically called downlink communication.

In another example, a communication from wireless device 524 to the core network, referred to as an uplink communication, may be transmitted from wireless device 524 and received at RRH 502 (or RRH 504 or RRH 506) via a radio signal. RRH 502 (or RRH 504 or RRH 506) may send this communication to BBU/BBU pool 514 via fronthaul link 516 (or via fronthaul link 518 or fronthaul link 520, respectively). The BBU/BBU pool 514 can then send the communication to the core network 522, where the communication can be directed to its intended destination.

Figure 6 illustrates an example of a CPRI-based C-RAN architecture 600, in which a BBU/BBU pool 602 is connected to an RRH 604 through a fronthaul link 606. RRH 604 may include an analog front end (AFE) 608, a digital to analog converter (DAC) 610, and an analog to digital converter (ADC) 612. AFE 608 may be operatively connected to a plurality of antennas 628. Additionally, as shown in option 614, RRH 604 may include at least two modules for CPRI processing: a compression and framing module 616 and a decompression and framing module 618. The BBU/BBU pool 602 may include a processing module 620 that handles a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Media Access Control (MAC) layer, and an entity ( PHY) layer processing. As shown in selection 622, the BBU/BBU pool 602 may also include at least two modules for CPRI processing: a compression and framing module 624 and a decompression and framing module 626.

In one example, during downlink communication, a signal may be sent from the layer processing module 620 of the BBU/BBU pool 602 to the compression and framing module 624 of the BBU/BBU pool 602. The compression and framing module 624 can perform time domain compression and framing operations on the signal, and send the signal to the decompression and framing module 618 of the RRH 604 via the fronthaul link 606 using the CPRI protocol. The decompression and framing module 618 can perform decompression and framing operations on the signal and send the signal to the DAC 610 . The DAC converts this signal to an analog signal and sends the analog signal to the AFE 608. The AFE can transmit the analog signal to a plurality of antennas 628. A plurality of antennas 628 can wirelessly transmit such analog signals to a destination device (eg, a UE).

In another example, during an uplink communication, the plurality of antennas 628 may receive a radio signal and transmit the signal to the AFE 608 . AFE 608 can send this signal to ADC 612. ADC 612 may digitize this signal using phase (I) and quadrature (Q) sampling and send the digitized signal to compression and framing module 616. The compression and framing module 616 can perform time domain compression and framing operations on this signal, and forward this signal to the decompression and framing module of the BBU/BBU pool 602 via the fronthaul link 606 using the CPRI protocol. 626. The decompression and framing module 626 can perform decompression and framing operations on the signal and send the signal to the layer processing module 620 . The layer processing module 620 can perform higher-layer fundamental frequency processing on this signal.

Although this C-RAN paradigm alleviates many of the problems associated with the traditional RAN paradigm, existing C-RAN architectures also introduce some new challenges. In particular, since the existing C-RAN paradigm requires the use of a CPRI interface to connect an RRH to a BBU/BBU pool, there will still be issues with the transfer rate requirements for the fronthaul links used in the C-RAN architecture because of the The expected transfer rate (i.e. the fronthaul rate) will be significantly higher than the data transfer rate through this radio interface.

For example, consider a Long Term Evolution (LTE) uplink (UL) system with a 10 megahertz (MHz) bandwidth, two receive antennas at an RRH, and a 15.36 MHz sampling frequency. If a 15-bit representation of I/Q phase bit samples is used, the I/Q data rate is 921.6 million bits per second (Mbps). If one considers the CPRI basic frame overhead of one header byte per 15 bytes of data and a line encoding rate of 10/8, the physical line rate becomes 1.2288 gigabits per second (Gbps). In addition, the overall CPRI physical line rate increases linearly with the number of antennas, while the system bandwidth quickly exceeds 10 Gbps when using carrier aggregation. These factors will therefore lead to rather high fronthaul rate requirements for practical deployment.

Other issues also affect the existing C-RAN architecture. For example, CPRI's sampling rate is the same as that of LTE and is independent of user load or user activity within a cell; as a result, there is no statistical average gain. Additionally, CPRI data rate requirements are largely driven by I/Q user plane data samples. An LTE signal is inherently redundant due to the use of guardbands. For example, in a 10 MHz LTE system, only 600 of the 1,024 available subcarriers are used for data; the other subcarriers are zeroed out and used as guard bands. However, although the time-domain I/Q samples have a redundant signal structure, a complex nonlinear scheme is still required to exploit this redundancy in order to achieve a higher compression factor. In addition, forward-pass compression schemes operating on time-domain I/Q samples cannot take advantage of the signal quantization-to-noise ratio (SQNR) of different modulation and coding schemes, or user scheduling side information (e.g., user activity, subcarriers occupancy) because once a signal is split in the time domain, this information is largely lost. For at least these reasons, compression performance in existing C-RAN architectures is relatively poor.

Systems and methods in accordance with the present disclosure present an alternative flexible C-RAN architectural framework that can operate in a radio access network implementing network slicing.

Radio Access Network (RAN) re-architecture has been discussed for Cloud Radio Access Network (CRAN) and 3rd Generation Partnership Project (3GPP) fourth generation (4G) Long Term Evolution (LTE) technology. The main motivation for radio access network re-architecture is to reduce fronthaul rate requirements while maintaining efficiency based on CRAN technical premises. Various radio access network re-architecture options have been proposed, including a pure split physical layer (PHY) option (only the fast Fourier transform (FFT) function is moved to the front end), multiple input multiple output (MIMO) processing is moved to one of the front ends Advanced split PHY option (suitable for massive MIMO applications where the number of antenna elements is much greater than the number of data streams), and a remote PHY option (where the overall PHY functionality is moved to the front end). Other proposals include compression techniques based on PHY segmentation options to further reduce fronthaul rates.

The aforementioned proposal is a symmetrical option, where the same functional split applies to both the downlink (DL) and the uplink (UL). An asymmetric option is based on Coordinated Multipoint (CoMP) observation, where joint reception in UL brings more benefits than joint transmission in DL. This asymmetric re-architecture enables joint reception in the UL, but only technologies such as coordinated scheduling/coordinated beamforming (CS/CB) in the DL provide suitable joint reception in the DL.

In the fifth generation (5G) LTE era, there are new requirements for radio access network re-architecture. New network slicing technology applied to the basic new 5G radio access technology (RAT), or several different RATs, can be used to support a variety of applications and very different requirements. These can be the vertical markets that drive the (vertical) network slicing concept mentioned above. For example, enhanced mobile broadband (eMBB) can provide high bandwidth and a high date rate, which can benefit from advanced MIMO transmission, such as beamforming and cell-free operation. On the other hand, mission-critical Internet of Things (IoT) applications can benefit from extremely low latency, which can be provided by a low-latency frame structure. An example of a low-latency frame structure is a self-contained subframe structure that allows for near-immediate acknowledgment/negative (ACK/NACK) feedback, fast hybrid automatic repeat request (HARQ) retransmission, and natural expansion Transmission to bands that do not require licensing or sharing. However, the different applications and different technologies mentioned above create conflicting requirements for radio access network re-architecture (and its options) using C-RAN.

Mission-critical services are continuously being developed for use on LTE and future wireless networks. For example, the 3rd Generation Partnership Project (3GPP) has one of the standards groups (SA6 - Mission-Critical) set up to develop these service types. application). A mission-critical service may include a mission-critical push-to-talk (MCPTT) service, and an example of a mission-critical IoT service may be vehicle-to-vehicle (V2V) communication, or vehicle-to-infrastructure (V2I) communication, for example, May permit or enable autonomous vehicles, automated emergency response services, and the like. Mission critical, by its very nature, is a service that is subject to priority processing compared to normal telecommunications services, such as supporting the police or fire brigade. This includes the handling of priority messages and/or calls for emergencies and immediate threats (e.g. MCPTT calls), delivering real-time telemetry or control messages that enable automated control (particularly related to fast-moving vehicles), and the like. Exemplary MCPTT services may be used in public safety applications, and also in general commercial applications, such as utility companies and railroads. Other mission-critical services may include emergency services, uninterruptible enterprise services, etc. Services that are mission-critical can also be large-scale (ie, a very large number of such users are, or are to be, served by the wireless network), such as V2V or V2I. A "very large amount" can range from hundreds to millions or more, and can also be defined in terms of the number of base stations per base station or the like. Alternatively or additionally, a very large amount may comprise a high percentage of the available (processing/computing, or wireless) resources in the wireless network where a serving or controlling entity is located or available. Non-mission-critical services can also be large-scale (such as smart meters, which are a form of machine-type communication). The terms "mission critical" and "large scale" can typically be defined by users, system designers, and/or standards (such as 3GPP), and their definitions can change over time. This disclosure is intended to cover all current and future definitions of these terms as found in relevant current or new standards (eg, 3GPP standards).

Exemplary embodiments provide a flexible radio access network re-architecture framework for network slicing/services. Exemplary embodiments may be based on a software-defined RAN (soft RAN) concept, where various RAN functions may be virtualized. For example, in a soft RAN architecture, each network service used or available by the wireless network can be designated as a software application running on a more general hardware platform (for example, Figure 9 or 12 shown in and explained below). This common hardware platform may be provided using commodity hardware, such as data servers, network switches, common radio frequency (RF) circuitry, and the like. Therefore, in a soft RAN, the wireless network operator/owner can simply specify a suitable data plane and control plane processing mechanism to facilitate any (new) service it wishes to deploy a wireless network. This can even be done using high-level languages. This approach reduces time to market and deployment costs, for example, by reducing hardware replacement and/or setup costs. This reduction in time and cost further enhances the ability of the soft RAN-based wireless network disclosed in this article to implement evolving and revolutionary new technologies under development and to be developed. This so-called agile development process can be used to maximize return on investment for network operators.

A soft RAN operating system (OS) can be deployed to manage all the complexities behind implementing and deploying network services(s) across generic/commodity hardware. This general/commodity hardware can be located in the central office and/or at remote cell sites, as implemented in one of the deployment profiles used on any given wireless network for the network slice-aware C-RAN provided by the disclosed soft RAN. Depends.

In situations where some of these RAN functions cannot be virtualized, dedicated hardware accelerator(s) may also or instead be used.

Exemplary embodiments provide a flexible radio access network re-architecture framework for network slicing/services. The framework of these exemplary embodiments may use base station (e.g., an evolved nodeB (eNB)) scheduling information and may be dynamically based on different network slices/services to be supported by the (re-architected/re-architectable) RAN Perform radio access network re-architecture.

Previous radio access network re-architectures using C-RAN discussed above were unaware of network slicing and operated primarily with only fronthaul data rate and latency trade-offs in mind. However, the flexible radio access network re-architecture of the illustrative embodiments has significant impact on fronthaul bandwidth (BW) and latency, network profile of any specific service/slice used, quality of service (QoS), where each node is located. Computing considerations and/or capabilities, and the like, support different 5G services (i.e. use cases/vertical markets, e.g. vertical network slicing), and technologies or architectures (e.g. compute slicing, e.g. horizontal network slicing).

Exemplary embodiments provide a 5G air interface that supports different network services by enabling flexible selection of waveforms (e.g., Orthogonal Frequency Division Multiplexing (OFDM)/Code Division Multiple Access (CDMA)/etc.) and numerology Flexibility and multitasking. For example, massive Internet of Things (IoT) could use a narrower subcarrier spacing, or even code division multiple access (CDMA) waveforms using a time/frequency grid, while mobile broadband services could use band One of the orthogonal frequency division multiplexing (OFDM) waveforms with larger subcarrier spacing. That is to say, when deploying wireless communication services to a first group of devices with one communication parameter type (for example, a large number, with specific latency requirements), a second group of devices with a second communication parameter type (such as (less large, but more data hungry) devices will have very different needs, and this will be difficult to reconcile within a single homogeneous network. Therefore, the present disclosure provides network slicing in C-RAN, for example, thereby providing means to provide different sets of ideas for different communication parameters/performance. For example, according to embodiments, a base station (e.g., eNB) may be aware of different network services or slices (e.g., logically separated radios) used on the same single entity radio access network during scheduling. Access the different resources served by the network.

Different services may also require different 5G technologies, such as radio access technology (RAT). For example, mobile broadband services may require high throughput, so massive MIMO/beam aggregation technology is expected to be very useful in meeting this high throughput requirement. However, for mission-critical services, peak throughput may not necessarily be high, but latency requirements may be very stringent. Likewise, in some implementations, the 5G RAT(s) used (or one of them) may be designed for wide area network (WAN) communications, while in other implementations, the (etc.) ) 5G RAT (or one thereof) is designed for Personal Area Network (PAN) communications. These latter RATs may be replacements (or replacements) for Bluetooth, Zigbee or similar communications.

Therefore, the flexible radio access network re-architecture of these exemplary embodiments can support different 5G services and technologies. Likewise, fronthaul bandwidth (BW) is considered a primary decision point for 4G radio access network re-architecture efforts and can be used to drive key decisions on better radio access network architecture options including network slicing concepts. .

Figure 7 shows an overall process 700 for flexible radio access network re-architecture according to a first example. This procedure can operate at an operating frequency (also considered an operating complexity level) based on a transmission time interval (TTI) period, such as every 1 ms. However, the present disclosure is not limited to any specific operating frequency/rate. Within each time period, frequency resources 710 for different operating (or upcoming operating - for example, when slicing is about to be turned on) network slices are determined. Frequency resources can be time slots or frequencies (please refer to Figure 3), or use numerology or similar. The disclosed process then determines which mode or type of operation can be used in RAN/C-RAN, ie which type of radio access network architecture is used. A radio access network architecture, as used herein, can be thought of as any form of specific technology, technology(s), implementation details, improvements or types of its operation within a wireless network, in particular a RAN. Architectures are typically described, maintained, and updated in standards documents to facilitate the use of individual wireless network technologies.

A first exemplary option may use Joint Transmit (JT) CoMP and/or Joint Receive (JR) CoMP, possibly with beam aggregation 720, to serve wireless device(s) served by network slicing/RAN. This could be used, for example, when providing a high-throughput mobile broadband (MBB) service in a dense environment. At the same time, beam pooling and JT/JR are particularly useful in mmWave bands for high throughput and robust links. In some examples, packetized fronthaul may provide forward packetization using a split physical layer (PHY) arrangement 750, where, for example, the split PHY processing (SPP) architecture is a C-RAN arrangement that splits the wireless Base station (BS) functions between channel encoding/decoding and wireless modulation/demodulation, and the ability to provide CoMP joint transmission and reception solutions.

A second illustrative option may use a large number (ie, many) connections to serve wireless device(s) served by a network slice/RAN, such as may be used in an IoT deployment. This can be used, for example, when devices are used for data collection/reporting on a large scale, such as smart grids/meters, and other (large-scale) machine-to-machine type communications.

In this case, different fronthaul architectures 760 may be provided, for example, depending on the fronthaul data rates applicable (or required) for each particular form of large-scale/IoT deployment being used. Other factors may influence the choice of prequel architecture, such as latency, or the like. Examples of different fronthaul architectures that may be deployed may include any of the following: Common Public Radio Interface (CPRI), or CPRI-like/Advanced architectures (e.g., CPRI compression and Ethernet CPRI), remote PHY, or Layer 2 (L2)/Layer 3 (L3) segmented type architecture, and/or for example, one of the segmented physical layer (PHY)/media access control layer (MAC) in the remote radio head (RRH) .

A third exemplary option may be to use a mission-critical service standard 740 (which may also include a large number of connections, such as for V2X) to serve wireless device(s) served by a network slice/RAN, for example , where these devices are used in time-critical (e.g., V2X), or critical delivery (e.g., emergency services) use cases, or similar.

In this situation, different fronthaul architectures 770 may be provided, for example, depending on the specific needs of the mission-critical type of service type. For example, a Layer 2 (L2)/Layer 3 (L3) split type architecture 770 may be used (such as used above to include PHY/MAC split in the RRH).

The interface and packet format between the baseband unit (BBU) and the remote radio head (RRH) can be proprietary or standardized in 3GPP.

Figure 8 shows a second, more detailed/specific, exemplary overall process 800 for a flexible radio access network re-architecture, particularly within an exemplary packetized arrangement. This example is shown in Figure 7, which is also based on determining frequency resources for network slicing based on the complexity of each TTI period, and has three illustrative options.

A first illustrative option 820 is to use the corresponding resource blocks (RBs) for beamforming, and/or JT/JR CoMP, in which case the process uses the advanced CPRI technology 850 for any of the following Situation (or need): High bandwidth, low latency, or dark fiber fronthaul availability (e.g., if there is some spare fiber capacity for the RRH (currently dark, not light). At least until this point in time, this will may be relevant when wide (but JT/JR is not supported), or this program uses quantization of I/Q samples, for example, depending on the compression scheme used on the RAT, to provide, for example, any of the following One: a certain amount of bandwidth (such as low, medium, high), low latency fronthaul, or similar. Other methods such as fixed uniform quantization, nonlinear quantization, etc. are also possible. This quantization scheme is typically specified by a particular standard being used, for example, to allow multiple vendor implementations.

A second exemplary option 830 may be to use a large number of connections to serve large-scale (ie, many) devices, such as may be used in IoT deployments. In this case, similar to the above, different fronthaul architectures 870 can be provided, but this time, for example, depending on the fronthaul bandwidth and delay parameters. Other factors may influence the choice of prequel architecture, such as latency, or the like. Examples of different fronthaul architectures that may be deployed may include any of the following: Common Public Radio Interface (CPRI), or CPRI-like/advanced type architectures (e.g., CPRI compression and Ethernet CPRI), remote PHY, or Layer 2 (L2)/Layer 3 (L3) split type architecture (example used above to include PHY/MAC split in RRH). Each possible RAN segmentation type has a corresponding data packetization format.

A third exemplary option 840 may be used for extremely delay-sensitive data-based devices, in which case a self-contained subframe format may be used. In this exemplary scenario, a media access control (MAC) protocol data unit (PDU), MAC PDU-based fronthaul architecture 880 may be used. In some instances, this process may include operations with and without cells.

The term "circuitry" as used herein may mean, be part of, or include an application specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or grouped), and/or memory (shared, dedicated, or grouped) that executes one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the functions described. In some embodiments, the circuitry may be implemented in one or more software or firmware modules, or functions associated with the circuitry may be implemented by the one or more software or firmware modules. In some embodiments, circuitry may include logic that may be at least partially operable in hardware. The terms device (served by a RAN or network slice) and UE are used interchangeably in this document.

The embodiments described herein may be implemented as a system using any suitably configured hardware and/or software. Figure 9 shows exemplary components of an electronic device 900 for one embodiment. In embodiments, the electronic device 900 may be, implement, be incorporated into, or otherwise be part of a user equipment (UE), an evolved NodeB (eNB), or another network component (e.g., , corresponding to a network virtualization device and/or a network component of a software-defined network device). In some embodiments, electronic device 900 may include application circuitry 910, baseband circuitry 920, radio frequency (RF) circuitry 930, front-end module (FEM) circuitry 940 and a or multiple antennas 950.

Application circuitry 910 may include one or more application processors. For example, application circuitry 910 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and specialized processors (graphics processors, application processors, etc.). Such processors may be coupled to and/or include memory/storage and may be configured to execute instructions stored in such memory/storage to allow various applications and/or or operating system is running on this system.

Baseband circuitry 920 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. Baseband circuitry 920 may include one or more baseband processors and/or control logic to process baseband signals received from one of the receive signal paths of RF circuitry 930 and for one of the transmit signal paths of RF circuitry 930 Generate fundamental frequency signal. The baseband processing circuitry 920 can be interfaced with the application circuitry 910 for generating and processing the baseband signals, and for controlling the operation of the RF circuitry 930 . For example, in some embodiments, the baseband circuit system 920 may include a second generation (2G) baseband processor 921, a third generation (3G) baseband processor 922, a fourth generation (4G) baseband processor Processor 923, and/or other baseband processor(s) 924 of other existing generations, under development, or in future generations to be developed (such as fifth generation (5G), 6G, etc.). Baseband circuitry 920 (eg, one or more of baseband processors 921 - 924 ) may handle various radio control functions that allow communication with one or more radio networks via RF circuitry 930 . These radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency offset, etc. In some embodiments, the modulation/demodulation circuitry of baseband circuitry 920 may include fast Fourier transform (FFT), precoding, and/or constellation mapping/demapping functions. In some embodiments, the encoding/decoding circuitry of baseband circuitry 920 may include convolutional, tail-code deconvolution, turbo, Viterbi, and/or low density parity check (LDPC) encoders/ Decoder function. Embodiments of modulation/demodulation and encoder/decoder functions are not limited to these examples, and other suitable functions may be included in other embodiments.

In some embodiments, baseband circuitry 920 may include elements of a protocol stack, for example, elements of an Evolved Universal Terrestrial Radio Access Network (EUTRAN) protocol, including, for example, physical (PHY), media storage, etc. Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and/or Radio Resource Control (RRC) elements. The central processing unit (CPU) 925 of the baseband circuitry 920 may be configured to run elements of the protocol stack for PHY, MAC, RLC, PDCP and/or RRC signaling. In some embodiments, the baseband circuitry may include one or more audio digital signal processors (DSPs) 926. The audio DSP(s) 926 may be or include components for compression/decompression and echo cancellation, and may include other suitable processing components in other embodiments.

The baseband circuit system 920 may further include a memory/storage 927 . Memory/storage 927 may be used to load and store data and/or instructions for operation by the processor of baseband circuitry 920 . Memory/storage for an embodiment may include any combination of dependent memory and/or non-volatile memory as appropriate. Memory/storage 927 may include any combination of various memory/storage levels, including, but not limited to, read-only memory (ROM), random access memory with embedded software instructions (e.g., firmware) (such as dynamic random access memory (DRAM)), cache, buffer, etc. Memory/storage 927 may be shared among the various processors or may be dedicated to a particular processor.

In some embodiments, the components of the baseband circuit system may be appropriately combined into a single chip, a single chip set, or disposed on the same circuit board. In some embodiments, some or all of the constituent components of baseband circuitry 920 and application circuitry 910 may be implemented together, for example, on a system on a chip (SOC).

In some embodiments, baseband circuitry 920 may be used to conduct communications compatible with one or more radio technologies. For example, in some embodiments, baseband circuitry 920 may support communications with an Evolved Universal Terrestrial Radio Access Network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless LAN ( WLAN), a Wireless Personal Area Network (WPAN) for communication. Embodiments in which baseband circuitry 920 is configured to support radio communications with more than one wireless protocol may be referred to as multi-mode baseband circuitry.

RF circuitry 930 may allow communication with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, RF circuitry 930 may include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. RF circuitry 930 may include a receive signal path, which may include circuitry to downconvert the RF signal received from FEM circuitry 940 and provide a baseband signal to baseband circuitry 920 . RF circuitry 930 may also include a transmission signal path, which may include circuitry for upconverting the baseband signal provided by baseband circuitry 920 and providing an RF output signal to FEM circuitry 940 for transmission. .

In some embodiments, RF circuitry 930 may include a receive signal path and a transmit signal path. The receive signal path of the RF circuit system 930 may include a mixer circuit system 931 , an amplifier circuit system 932 and a filter circuit system 933 . The transmission signal path of the RF circuit system 930 may include a filter circuit system 933 and a mixer circuit system 931 . RF circuitry 930 may also include synthesizer circuitry 934 for combining a frequency for use by mixer circuitry 931 of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 931 of the receive signal path may be configured to down-convert the RF signal received from the FEM circuitry 940 based on the synthesized frequency provided by the synthesizer circuitry 934 . Amplifier circuitry 932 may be configured to amplify the down-converted signals, and filter circuitry 933 may be configured to remove unwanted signals from the down-converted signals to generate an output basis. Frequency signal is either a low-pass filter (LPF) or a band-pass filter (BPF). An output baseband signal may be provided to baseband circuitry 920 for further processing. In some embodiments, the output fundamental frequency signal may be a zero-frequency fundamental frequency signal, but this is not a necessary condition. In some embodiments, the receive signal path mixer circuitry 931 may include a passive mixer, although the scope of such embodiments is not limited in this regard.

In some embodiments, the mixer circuitry 931 of the transmission signal path may be configured to upconvert the input baseband signal based on the synthesized frequency provided by the synthesizer circuitry 932 to generate a signal for the FEM circuitry. RF output signal used by 940. These baseband signals may be provided by baseband circuitry 920 and filtered by filter circuitry 933 . Filter circuitry 933 may include a low pass filter (LPF), but the scope of the embodiments is not limited in this regard.

In some embodiments, the mixer circuitry 931 of the receive signal path and the mixer circuitry 931 of the transmit signal path may include two or more mixers and may be arranged for quadrature operation, respectively. Downconversion and/or upconversion. In some embodiments, the mixer circuitry 931 of the receive signal path and the mixer circuitry 931 of the transmit signal path may include two or more mixers and may be arranged for image rejection ( For example, Hartley image rejection). In some embodiments, the mixer circuitry 931 of the receive signal path and the mixer circuitry 931 may be arranged for direct down conversion and/or direct conversion, respectively. In some embodiments, the mixer circuitry 931 of the receive signal path and the mixer circuitry 931 of the transmit signal path may be configured for superheterodyne operation.

In some embodiments, the output fundamental frequency signals and the input fundamental frequency signals may be analog fundamental frequency signals, although the scope of these embodiments is not limited in this regard. In some alternative embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, RF circuitry 930 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and baseband circuitry 920 may include a circuit for communicating with RF circuitry 930 Digital baseband interface.

In some dual-mode embodiments, a separate wireless IC for signal processing may be provided for each spectrum, although the scope of such embodiments is not limited in this regard.

In some embodiments, synthesizer circuitry 934 may be a fractional N synthesizer or a fractional N/N+1 synthesizer, but the scope of such embodiments is not limited in this regard as there may be other suitable types. frequency synthesizer. For example, the synthesizer circuitry 934 may be a sigma delta synthesizer, a frequency doubler, or a synthesizer including a phase locked loop with a frequency divider.

Synthesizer circuitry 934 may be configured to synthesize an output frequency for use by mixer circuitry 931 of RF circuitry 930 based on a frequency input and a divider control input. In some embodiments, synthesizer circuitry 934 may be a fractional N/N+1 synthesizer.

In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), but this is not a requirement. The divider control input may be provided by either the baseband circuitry 920 or the application processor 910, depending on the desired output frequency. In some embodiments, a divider control input (eg, N) may be determined via a lookup table based on a channel indicated by the application processor 910 .

The synthesizer circuitry 934 of the RF circuitry 930 may include a divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the divider may be a dual analog-to-digital divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (eg, based on a carry output) to provide a fractional distribution ratio. In some exemplary embodiments, the DLL may include a set of cascaded, adjustable, delay elements, a phase detector, a charge pump, and a D-type flip-flop. In these embodiments, the delay elements may be configured to divide a VCO cycle into Nd equal phase packets, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback and helps ensure that the total delay through the delay line is one VCO cycle.

In some embodiments, the synthesizer circuitry 934 may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (eg, twice the carrier frequency , four times the carrier frequency), and can be used with a quadrature generator and divider circuit system to generate multiple signals with different phases at the carrier frequency. In some embodiments, the output frequency may be an LO frequency (fLO). In some embodiments, RF circuitry 930 may include an IQ/polarity converter.

FEM circuitry 940 may include a receive signal path, which may include circuits configured to operate on RF signals received from one or more antennas 950 , amplify the received signals, and provide This amplified version of the circuitry that has received the signal for further processing. FEM circuitry 940 may also include a transmission signal path, which may include circuitry configured to amplify transmission signals provided by RF circuitry 930 for transmission by one or more of one or more antennas 950 system.

In some embodiments, FEM circuitry 940 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuit system may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include a low noise amplifier (LNA) for amplifying received RF signals and providing the amplified received RF signals as an output (eg, to RF circuitry 930). The transmission signal path of FEM circuitry 940 may include a power amplifier (PA) for amplifying an input RF signal (eg, provided by RF circuitry 930 ), and one or more RF signals for generating (eg, by A filter for subsequent transmissions by one or more antennas 950.

In various embodiments, network interface controller (NIC) circuitry 960 may include one or more transmit and receive (TX/RX) signal paths that may be connected to one or more Data packet network. In some embodiments, NIC circuitry 960 may be connected to these data packet networks via multiple network interface circuits 965 . NIC circuitry 960 may support one or more data link layer standards, such as Ethernet, Fiber, Token Ring, Asynchronous Transfer Mode (ATM), and/or any other suitable data link layer standard(s) . In some embodiments, the electronic device 900 can be connected to various network elements (such as a base station, a network controller, a radio access network (RAN) device, an S-GW, an SDN switch, an MME, P-GW, and the like) may contain an identical or similar network interface circuitry 965. Furthermore, NIC circuitry 960 may include or be associated with processing circuitry, such as one or more single-core or multi-core processors and/or logic circuitry, to provide processing suitable for use in accordance with the NIC circuitry. One or more data link layer standards implement communication processing technology.

In some embodiments, the electronic device 900 may include additional components, such as memory/storage, a display, a camera, a sensor, and/or an input/output (I/O) interface.

In embodiments in which electronic device 900 is, implements, is incorporated into, or is otherwise part of a radio access network (RAN), NIC circuitry 960 may be used to partition network resources into one or more slices. Each of the one or more slices corresponds to a service to be provided by a radio access network (RAN); and the network interface circuitry 965 can be used to provide the one or more slices according to a corresponding service to be provided. Network resources for all slices.

In embodiments in which electronic device 900 is, implements, is incorporated into, or is otherwise part of an evolved nodeB (eNB), network interface circuitry 965 may be used to receive a network partitioned into one or more slices. A group of resource segments, where each of the one or more slices corresponds to a service to be provided by a radio access network (RAN). The baseband circuit system 920 can be used to allocate network resources of each of the one or more slices according to the network resource segment group.

In some embodiments, the electronic device of Figure 9 may be configured to perform one or more processes, techniques and/or methods, or portions thereof, as described herein. Figure 10 illustrates a first illustrative method of this process. For example, this process may include dividing baseband unit (BBU) and remote radio head (RRH) functions 1010 to implement network slicing according to different deployment scenarios 1020. Figure 11 shows a second example method. For example, this process may include partitioning the network resource 1110 into one or more slices. Each of the one or more slices may correspond to a service to be provided by a radio access network (RAN). This process may include providing 1120 network resources for each of the one or more slices according to a corresponding service to be provided. Both illustrative approaches dynamically (re)configure the RAN architecture used on the RAN or C-RAN based on the needs of the RAN and/or network slicing to operate this RAN at any given point in time.

Figure 12 illustrates a block diagram of components capable of reading instructions from a machine-readable or computer-readable medium (eg, a machine-readable storage medium) and performing the methods discussed herein, in accordance with some exemplary embodiments. any one or more of them. Specifically, FIG. 12 shows a schematic diagram of a hardware resource 1200, which includes one or more processors (or processor cores) 1210, one or more memories/storage communicatively coupled to each other via a bus 1240. Device 1220, and one or more communication resources 1230.

Processor 1210 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), such as a baseband processor For example, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination of the above) may include a processor 1212 and a processor 1214. The memory/storage device 1220 may include main memory, disk storage, or any suitable combination thereof.

Communication resources 1230 may include interconnection and/or network interface components, or other appropriate devices, for communicating with one or more peripheral devices 1204 and/or one or more databases 1206 via a network 1208 . For example, communication resources 1230 may include wired communication components (eg, for coupling via a universal serial bus (USB)), cellular communication components, near field communication (NFC) components, BluetoothR components (eg, BluetoothR low energy ), Wi-FiR components, and other communication components.

Instructions 1250 may include software, a program, an application, a mini-application, an app, or other executable code for causing at least any processor 1210 to perform any one or more of the methods discussed herein. Instructions 1250 may reside, in whole or in part, within at least one of: processor 1210 (eg, within the processor's cache), memory/storage 1220, or any appropriate combination thereof. Furthermore, any portion of instructions 1250 may be transferred to hardware resources 1200 from any combination of peripheral devices 1204 and/or database 1206 . Accordingly, the memory of processor 1210, memory/storage 1220, peripheral devices 1204, and database 1206 are examples of computer-readable and machine-readable media. Example

Example 1 may include a method of implementing network slicing to divide functions between baseband units (BBUs) and remote radio heads (RRH) in different deployment scenarios.

Example 2 may include methods like Example 1 or some other examples herein, in which an evolved nodeB (eNB) will use scheduling information for each network slice to partition the BBU and RRH functions. The eNB is just one example of a base station.

Example 3 may include a method as in Example 2 or some other examples herein, wherein the eNB pairs frequencies scheduled for mobile broadband services with advanced multiple-input multiple-output (MIMO) schemes and medium/high bandwidth (BW) fronthaul/ Time resources are used to divide BBU and RRH functions into Class 1 Common Public Radio Interface (CPRI) and/or Advanced CPRI or Physical Layer (PHY) segmentation.

Example 4 may include a method as in Example 2 or some other examples herein, where the eNB will use frequency/time resources scheduled for low-latency services, such as mission-critical Internet of Things (IoT) applications and/or devices , perform functional division of Layer 2 (L2)/Layer 3 (L3) BBU and RRH.

Example 5 may include a method as in Example 2 or some other examples herein, wherein the eNB performs a type of CPRI, PHY partitioning of frequency/time resources scheduled for massive machine type communications (MTC) services or mobile broadband services , remote PHY, or L2/L3 split BBU and RRH functional split.

Example 6 may include a method as in Example 1 or some other examples herein, wherein the eNB uses scheduling information for fronthaul packetization for each network slice.

Example 7 may include a method as in Example 6 or some other examples herein, wherein the eNB pairs the frequency/time scheduled to support advanced MIMO schemes such as coordinated multipoint (CoMP), beam pooling, cellless operation, etc. Resources for forward packetization defined for CPRI-like or PHY segmentation BBU and RRH segmentation.

Example 8 may include a method as in Example 6 or some other example herein, wherein the eNB performs L2 for the frequency/time resources scheduled for extremely delay-sensitive applications such as mission-critical IoT applications or mission-critical IoT devices. /L3 BBU and RRH division define the forward packetization procedure.

Example 9 may include a method as in Example 6 or some other examples herein, wherein the eNB performs, based on fronthaul BW and delay, including CPRI-like, PHY segmentation, remote PHY, L2/L3 segmentation and other forward packetization procedures.

Example 10 may include a method comprising: partitioning network resources into one or more slices, wherein the one or more slices each correspond to a service to be provided by a radio access network (RAN); and providing network resources of each of the one or more slices according to a corresponding service to be provided.

Example 11 may include a method as in Example 10 or some other examples herein, wherein the differentiating includes defining a first slice of the one or more slices to be associated with a large-scale Internet of Things (IoT) application and/or IoT device , and defining a second one of the one or more slices to be associated with a mobile broadband service, and wherein the providing includes allocating a narrow bandwidth to a desired time/frequency grid for the service associated with the first slice. subcarrier spacing or code division multiple access (CDMA) waveforms, and allocating an orthogonal frequency division multiplexing (OFDM) waveform with a larger subcarrier spacing to services associated with the second slice.

Example 12 may include the method of Example 11 or some other examples herein, wherein the providing includes allocating network resources for high throughput requirements to services associated with the second slice, and allocating network resources to services associated with the first slice. Allocate low-latency resources to slice-related services.

Example 13 may include a method as in Example 10 or some other examples herein, which further includes determining frequency resources used by each of the one or more slices for a transmission time interval (TTI); determining the frequency resources associated with the TTI. Whether a service is a service with large-scale connections; and when determining that the service associated with the TTI is a service with large-scale connections and is based on a fronthaul rate, select a radio access network Road (RAN) segmentation. Example 14 may include a method as in Example 10 or some other example herein, wherein the RAN partitioning includes a Common Public Radio Interface (CPRI), PHY partitioning, remote PHY, or L2/L3 partitioning of frequency/time resources, The baseband unit (BBU) and remote radio head (RRH) functions are divided into one of them.

Example 15 may include a method as in Example 13 or some other examples herein, further including determining whether the service associated with the TTI is a service beam aggregation; and when the service associated with the TTI is a usage beam When aggregating services, a split PHY architecture is used to encapsulate the fronthaul packets.

Example 16 may include a method like Example 15 or some other examples herein, which further includes: determining whether the service associated with the TTI is a mission-critical service; and when the service associated with the TTI is a critical When serving tasks, use this L2/L3 split.

Example 17 may include a method as in Example 14 or some other example herein, wherein the selection includes determining that the service associated with the TTI is a service with large-scale connections and is based on a fronthaul bandwidth (BW) and fronthaul delay, the RAN partition is selected, and each RAN partition includes a corresponding data packetization format.

Example 18 may include a method as in Example 17 or some other examples herein, further including: determining whether the service associated with the TTI is a service beam aggregation; using corresponding resource blocks (RBs) for the beam aggregation ; when the fronthaul includes a high BW and low latency, select an advanced CPRI RAN segmentation; and when the fronthaul includes a medium BW and low latency, select an I/Q quantization and/or compression scheme RAN segmentation .

Example 19 may include the method of Example 17 or some other examples herein, further including: determining whether the service associated with the TTI is a delay-sensitive service; and selecting a Media Access Control (MAC) protocol data unit (PDU) prequel.

Example 20 may include an apparatus that includes network interface controller (NIC) circuitry for partitioning network resources into one or more slices, where each of the one or more slices corresponds to a radio to be used. a service provided by the access network (RAN); and network interface circuitry for providing network resources of each of the one or more slices according to a corresponding service to be provided.

Example 21 may include equipment as in Example 20 or some other examples herein, where the NIC circuitry is used to define the NIC circuitry associated with a large-scale Internet of Things (IoT) application and/or IoT device in order to differentiate network resources. or a first slice of one or more slices, and a second slice defining the one or more slices associated with a mobile broadband service, and wherein in order to provide the network resources, the network interface circuitry is used to allocate a narrow subcarrier spacing or Code Division Multiple Access (CDMA) waveform to a desired time/frequency grid for services associated with the first slice, and to allocate a narrow subcarrier spacing or Code Division Multiple Access (CDMA) waveform to services associated with the second slice. A larger subcarrier spacing allocates an orthogonal frequency division multiplexing (OFDM) waveform.

Example 22 may include equipment as in Example 21 or some other example herein, wherein in order to provide the network resources, the network interface circuitry is used to allocate services associated with the second slice for high throughput Network resources are requested, and low-latency resources are allocated to services associated with the first slice.

Example 23 may include equipment as in Example 20 or some other examples herein, wherein the NIC circuitry is used to determine frequency resources for each of the one or more slices for a transmission time interval (TTI); determine and Whether a service associated with the TTI is a service with a large-scale connection; and when it is determined that the service associated with the TTI is a service with a large-scale connection and is based on a fronthaul rate, select a Radio Access Network (RAN) segmentation.

Example 24 may include equipment as in Example 20 or some other example herein, wherein the RAN partitioning includes a Common Public Radio Interface (CPRI), PHY partitioning, remote PHY, or L2/L3 partitioning of frequency/time resources, The baseband unit (BBU) and remote radio head (RRH) functions are divided into one of them.

Example 25 may include equipment like Example 23 or some other examples herein, the NIC circuitry is used to determine whether the service associated with the TTI is a service beam aggregation; and when the service associated with the TTI is When using beam aggregation services, a split PHY architecture is used for packetization of fronthaul packets.

Example 26 may include equipment like Example 25 or some other examples herein, the NIC circuitry is used to determine whether the service associated with the TTI is a mission-critical service; and when the service associated with the TTI is For a mission-critical service, use the L2/L3 split.

Example 27 may include an arrangement like Example 24 or some other example herein, wherein the NIC circuitry is used for selection purposes in determining that the service associated with the TTI is a service with large-scale connectivity and is based on a The RAN partition is selected based on the fronthaul bandwidth (BW) and fronthaul delay, and each RAN partition includes a corresponding data packetization format.

Example 28 may include equipment like Example 27 or some other examples herein, the NIC circuitry is used to determine whether the service associated with the TTI is a service beam aggregation; use the corresponding resource block (RB) for the Beam pooling; selecting an advanced CPRI RAN segmentation when the fronthaul includes a high BW and low latency; and selecting an I/Q quantization and/or compression scheme when the fronthaul includes a medium BW and low latency RAN segmentation.

Example 29 may include equipment such as Example 27 or some other examples herein, the NIC circuitry is used to determine whether the service associated with the TTI is a delay-sensitive service; and select a media access control (MAC) protocol Data unit (PDU) forward transmission.

Example 30 may include equipment as examples 20 to 29 or some other examples herein, wherein the services are provided by the RAN, and the equipment is implemented in an electronic device associated with the RAN, and according to Network resource allocation in Examples 20 to 29 is provided to one or more evolved nodeBs (eNBs) via the network interface circuitry.

Example 31 may include an apparatus that includes network interface circuitry for receiving a group of network resource segments partitioned into one or more slices, where each of the one or more slices corresponds to a radio memory to be used. Obtain a service provided by the network (RAN); and use the baseband circuit system to allocate the network resources of each of the one or more slices according to the network resource segment group.

Example 32 may include equipment as in Example 31 or some other example herein, where the equipment is for implementation in an evolved nodeB (eNB).

Example 33 may include equipment as in Example 31 or some other example herein, where the equipment is for implementation in a device, such as a user equipment (UE), being served by the wireless network.

Example 34 may include a radio access network (RAN) control entity device operable in a wireless communication network, the device including: receiving at least one communication originating from a wireless network device, or transmitting At least one radio frequency (RF) circuitry that communicates to a wireless network device; wherein the RAN control entity is coupled to a baseband unit (BBU) and a remote radio head (RRH); and also includes circuitry to : Divide a physical RAN infrastructure or C-RAN into one or more network slices; and divide the BBU and/or RRH according to one of the deployment scenarios of the one or more network slices.

Example 35 may include equipment as in Example 34 or some other example herein, wherein the circuitry is further configured to use the physical radio access network, or the one or more networks operating or to be operated on the C-RAN. Scheduling information for each of the network slices is used to divide the BBU and/or RRH according to one of the deployment scenarios of the one or more network slices.

Example 36 may include the equipment of Examples 34-36 or some other examples herein, wherein the circuitry is further configured to use any one or more of the following to combine the one or more network slices according to one of the deployment scenarios of the one or more network slices. BBU and/or RRH partitioning: a type of Common Public Radio Interface (CPRI)/Advanced CPRI technology; a physical layer (PHY) partitioning technology across the BBU and RRH.

Example 37 may include equipment as examples 34 to 37 or some other examples herein, wherein the circuitry is used to partition the BBU and/or RRH to partition wireless network resources of the wireless network, wherein the wireless network Resources include frequency/time resources and/or physical resource blocks (PRBs).

Example 38 may include equipment such as Examples 34-37 or some other examples herein, in which the wireless network resources are divided according to a vertical slice or a horizontal slice.

Example 39 may include equipment as in Examples 34-38, or some other examples herein, in which a vertical slice is a mobile broadband service using an advanced multiple-input multiple-output (MIMO) scheme and a medium-to-high bandwidth fronthaul.

Example 40 may include equipment such as Examples 34-39 or some other examples herein, wherein the circuitry is used to partition the BBU and/or RRH according to parameters of the vertical or horizontal network slice.

Example 41 may include equipment as examples 39-40 or some other examples herein, wherein the parameters of the vertical or horizontal network slice include any one or more of the following: a data rate; a data bandwidth; a number of waiting A server device; a latency; a mission criticality; a delay; a quality of service (QoS); or a network profile of a service.

Example 42 may include the apparatus of Examples 39-40 or some other examples herein, wherein the circuitry is further configured to determine or perform fronthaul packetization with scheduling information for or belonging to each network slice.

Example 43 may include equipment as in Example 42 or some other example herein, further configured to determine or perform forward packetization procedures as defined in any of: a Common Public Radio Interface (CPRI)/Advanced CPRI technology; and A physical layer (PHY) segmentation technology across the BBU and RRH.

Example 44 may include the apparatus of Example 43 or some other example herein, wherein the circuitry is further configured to determine or perform a forward packetization process defined by frequency/time resource scheduling supporting an advanced MIMO technology, wherein the Techniques may include any one or more of CoMP, beam pooling or cellless operation.

Example 45 may include equipment as in Example 43 or some other example herein, wherein the circuitry is further configured to determine or perform a forward packetization process as defined by a frequency/time resource schedule or technology that supports any of the following: -Mission criticality, latency or bandwidth.

Example 46 may include equipment like Example 45 or some other example herein where mission criticality applies to a latency sensitive application.

Example 47 may include equipment as in Example 45 or some other example herein, wherein the equipment includes a base station.

Example 48 may include equipment as in Example 47 or some other example herein, wherein the base station includes an enhanced Node B (eNB).

Example 49 may include equipment such as Examples 34-48 or some other examples herein, wherein a vertical network slice includes any one or more of the following: a physical radio access network infrastructure for or dedicated to a single communication type A logical partition of a physical radio access network infrastructure; a logical partition of a physical radio access network infrastructure dedicated to or by communications for a specific communications use case; a logical partition of a physical radio access network infrastructure having Self-contained operations and traffic that are not related to operations and traffic on any other logical partition of the entity's radio access network infrastructure; and one of the horizontal network slices that contains at least one device operating in this RAN A logical partition of computing resources, wherein the at least one device includes a base station, a controller, or a device served by the RAN.

Example 50 may include user equipment for use with a radio access network (RAN) control entity equipment operable in a wireless communication network, the equipment including: for use under the control of the RAN control entity Receive at least one communication from a wireless network device, or transmit at least one communication to radio frequency (RF) circuitry of a wireless network device under the RAN control entity; wherein the RAN control entity includes as in Examples 34 to 49 Or some of the other examples in this article.

Example 51 may include one or more computer-readable media containing instructions that, when executed by one or more processors of an electronic device, cause the electronic device to access a radio access network of a wireless communications network Perform one or more elements of a method in (RAN), the method comprising: dividing a physical RAN infrastructure or C-RAN into one or more network slices; and based on one of the one or more network slices The deployment scenario divides the BBU and/or RRH.

Example 52 may include a method as in Example 51 or some other examples herein, wherein the method further includes using the one or more network slices operating or to be operated on the physical radio access network, or C-RAN. The scheduling information of each partitions the BBU and/or RRH according to one of the deployment scenarios of the one or more network slices.

Example 53 may include a method as in Examples 51 to 52 or some other examples herein, wherein the method further includes using any one or more of the following, according to one of the deployment scenarios of the one or more network slices, combining the BBU and /or RRH division: a type of Common Public Radio Interface (CPRI)/CPRI advanced technology; a physical layer (PHY) division technology across the BBU and RRH.

Example 54 may include a method as in Examples 51 to 53 or some other examples herein, wherein the method further includes allocating the BBU and/or RRH to allocate wireless network resources of the wireless network, wherein the wireless network resources Includes frequency/time resources and/or physical resource blocks (PRB).

Example 55 may include a method as in Examples 51 to 54 or some other examples herein, wherein the wireless network resources are divided according to a vertical slice or a horizontal slice.

Example 56 may include a method as in Examples 51 to 55 or some other examples herein, wherein a vertical slice is a mobile broadband service using an advanced multiple-input multiple-output (MIMO) scheme and a medium-to-high bandwidth fronthaul.

Example 57 may include a method as in Examples 51 to 56 or some other examples herein, and the method may further include dividing the BBU and/or RRH according to parameters of the vertical or horizontal network slice.

Example 58 may include a method as in Examples 51 to 57 or some other examples herein, wherein the parameters of the vertical or horizontal network slice include any one or more of the following: a data rate; a data bandwidth; a number of waiting times. A server device; a latency; a mission criticality; a delay; a quality of service (QoS); or a network profile of a service.

Example 59 may include a method as in Examples 51-58 or some other examples herein, wherein the method further includes determining or performing fronthaul packetization based on scheduling information for or belonging to each network slice.

Example 60 may include a method as in Example 59 or some other example herein, wherein the method further includes determining or performing a fronthaul packetization procedure as defined in any of the following: Common Public Radio Interface (CPRI) Type 1/CPRI-Advanced Technology; and physical layer (PHY) segmentation technology across the BBU and RRH.

Example 61 may include a method as in Example 60 or some other examples herein, wherein the method may further include determining or performing a forward packetization process defined by a frequency/time resource schedule supporting an advanced MIMO technology, wherein the technology may Including any one or more of CoMP, beam pooling or cellless operation.

Example 62 may include a method as in Example 60 or some other examples herein, wherein the method further includes determining or performing the fronthaul packetization process as defined by a frequency/time resource schedule or technology that supports any of the following: - Mission criticality, latency or bandwidth.

Example 63 may include a method as in Example 62 or some other example herein, where mission criticality applies to a delay-sensitive application.

Example 64 may include a method as in Example 62 or some other examples herein, wherein the method, or at least a portion thereof, is performed in a Cloud Radio Access Network (C-RAN), a RAN control entity, a base station, a Executed in a device served by the RAN, a UE, a BBU or an RRH.

Example 65 may include the method of Examples 51-64 or some other examples herein, wherein a vertical network slice includes any one or more of the following: a physical radio access network infrastructure for or dedicated to a single communication type A logical partition of a physical radio access network infrastructure; a logical partition of a physical radio access network infrastructure dedicated to or by communications for a specific communications use case; a logical partition of a physical radio access network infrastructure having Self-contained operations and traffic that are not related to operations and traffic on any other logical partition of the entity's radio access network infrastructure; and one of the horizontal network slices that contains at least one device operating in this RAN A logical partition of computing resources, wherein the at least one device includes a base station, a controller, or a device served by the RAN.

Example 67 may include one or more computer-readable media containing instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform any of Examples 1 to 19 and 51 to 64. or any method described in or in connection therewith, or one or more elements of any other method or process described herein, or according to any one or more of Examples 20 to 50 or 66, or as described herein. Any other device described above provides the functionality of this equipment.

Example 66 may include an apparatus including logic, modules, means, and/or circuitry for performing one of the methods described in or related to any of Examples 1-19, 51-64, or herein. one or more elements of any other method or process described.

Example 67 may include a method, technique, or process as described in or related to any one of Examples 1 to 19, 51 to 64, or portions or components thereof.

Example 68 may include an apparatus comprising: one or more processors and one or more computer-readable media including instructions that, when executed by the one or more processors, cause the or multiple processors to perform methods, techniques, or processes described in or related to any one of Examples 1 to 19, 51 to 64, or portions thereof, or according to any one or more of Examples 20 to 50, or 66 , or any other device described herein that provides the functionality of the equipment or device.

Example 69 may include a method of communicating in a wireless network as shown and described herein. Example 70 may include a system for providing wireless communications as shown and described herein. Example 71 may include an apparatus for providing wireless communications as shown and described herein.

Exemplary use cases/types of communications may include: wireless/mobile broadband (MBB) communications; extreme mobile broadband (E-MBB) communications; real-time use cases such as industrial control communications, machine-to-machine communications (MTC/MTC1); such as Internet of Things (IoT) sensor communication, or non-real-time use cases of massive machine-to-machine communication (M-MTC/MTC2); ultra-reliable machine-to-machine communication (U-MTC); such as cache, mobile edge cloud communication ;Vehicle-to-vehicle (V2V) communication; Vehicle-to-infrastructure (V2I) communication; Vehicle-to-everything communication (V2X). That is, the present disclosure relates to providing network slicing based on any easily definable/differentiable communication type that can be implemented over a wireless network.

In some examples, the radio access network (RAN) control entity is distributed over part of the RAN. In some examples, the portion of the RAN is a base station (e.g., eNB) of the RAN. In other examples, the portion(s) of the RAN may be a UE, or any other component of the wireless network/ Devices served by, or forming part of (or serving) RAN, such as Mobility Management Engine (MME), Baseband Unit (BBU), Remote Radio Head (RRH), etc. In some examples, if the entity distributes the RAN control entity, the RAN control entity may be co-located with the macro BS and only manage the slice portion under the coverage of the macro BS. In some examples, if the RAN control entity is located in a central location, the RAN control entity may manage a slice portion across multiple BSs covered by the RAN control entity. The RAN control entity may contain at least part of the control RAN or device allocation, which may contain resources as required by one of the one or more horizontal or vertical slices, such as being/located in, or available in one of the wireless networks. The computing resources of the device.

As described herein, if an instance or claim explicitly states that RF circuitry is, for example, used to form a larger entity within the wireless network, such as a base station, this is also intended to cover the exclusion of such circuitry. This or an alternative embodiment of RF circuitry, for example, may be used (or provided) in a physically distributed form in accordance with the present disclosure. This may apply, for example, when the entity forms part of a cloud radio access network, where the radio parts (eg RRH) are not common as at least a significant part of the control function (entity, module, etc.) Placed/located within the same entity, such as BBU. Therefore, no embodiments are intended to be limited to having only one RF portion of the wireless network that sends or receives messages to or from the wireless network. For example, some implementations may be partial fronthaul capability, which may be a connection from a centralized or other centralized baseband function (eg, BBU) to the radio front end (eg, RRH).

Any reference to a computer program product or computer-readable medium when used herein may include references to both transitory (such as physical media) and non-transitory (such as signals or data structures thereof).

Various examples disclosed herein may provide a number of advantages, for example, but not limited to: for the device being served, for any given amount of core network and/or RAN resources (e.g., compute, radio, etc.) (more) Complete coverage; less control communication delay and communication overhead between transmission points; provides improved coverage while reducing control communication exchanges between network nodes (including transmission points); a more efficient (overall, or Substantial part) wireless network because, for example, it allows a given (e.g., a single) physical radio access network infrastructure to be used by multiple use cases, thereby resulting in less hardware/infrastructure than would otherwise be the case. method will be used (e.g. twice, or more hardware, for example, to provide separate physical radio access network infrastructure for each use case); for both across the RAN and within each slice of the RAN Maintenance/maintenance of radio access network performance, efficiency, reliability, service and quality of service has generally been improved across all devices operating.

This, or the opening, enabling or logical partitioning of a network slice, or the like, as described herein, may be used interchangeably with each other and the terms are used interchangeably. Similarly, the closure, deactivation or logical termination of a network slice, or the like may all be equivalent to each other, and the terms used interchangeably. A network slice may also be referenced as a logical separation (partition, partition, etc.) of radio network access, or as a logical separation (partition, partition, etc.) of radio network access. One of the devices served by or to be served by this physical radio access network infrastructure, or a network slice, may include a UE, and any and all other device forms that may be served may also be interchanged with reference to a UE herein. A device can be referenced as a wireless network device. However, when a wireless network device is used in this article, it can also refer to a serving entity, such as a base station, MME, BBU, RRH, etc., depending on the usage context. Operationally, according to the network slicing disclosed in this article, an access point and a base station can be considered similar in use or deployment.

Specific examples, such as those described herein, have been used to explain the methods and functions (and functional units that perform those functions) disclosed herein, however, the disclosure is not so limited. For example, embodiments of the present disclosure are not limited to any specific example. For example, if a specific vertical market is disclosed in relation to a diagram, this is only an example, and any vertical market can be used instead; A slice in which a particular part is relevant to a figure may be replaced by any part of the slice; if a RAN has been disclosed as having a certain size, type or number of slices (horizontal or vertical) relevant to a figure , any size, type or number of slices may be used instead; provided that all slices or portions of slices are disclosed to be of a certain size, type or number in relation to a figure (either horizontally or vertically), any size may be used , type or number of slices or sliced parts instead. Likewise, in the foregoing, although the slices have been numbered starting from 1, other numbering schemes may be implemented, for example, the numbers could start from 0 instead, so that slice #1 could be slice #0, and the like. Therefore, these specific numbers are not limiting, unlike showing an illustrative difference between slices (because they are numbered differently), or an illustrative relationship between numbered slice portions (because sub-portions of the same numbered slice are numbered sequentially). ).

The term "circuitry" as used herein may mean, be part of, or include an application specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or grouped), and/or memory (shared, dedicated, or grouped) that executes one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware or software components, including those that provide the Function one or more virtual machines. In some embodiments, the circuitry may be implemented in one or more software or firmware modules, or functions associated with the circuitry may be implemented by the one or more software or firmware modules. In some embodiments, circuitry may include logic that may be at least partially operable in hardware. In some embodiments, this processing/execution may be distributed rather than centralized.

Any reference to a (RAN) architecture when used herein may include any form of specific process(s), technology, technology(s) that may be defined or considered as a wireless network (or similar network connectivity system entity) , implementation details, operational improvements or anything of the type, especially in this RAN. Architectural examples may be introduced, maintained, and updated in standards documents to facilitate the use of various wireless network technologies, such as the 3rd Generation Partnership Project (3GPP) standards, and the like.

It will be understood that any of the methods (or corresponding devices, programs, data carriers, etc.) disclosed herein may be implemented by a host or client, depending on the particular implementation (i.e., herein The method/equipment of revelation is a form of communication and, as such, can be carried out from any "point of view", i.e., corresponding to each other). Furthermore, it will be understood that the terms "receive" and "transmit" include "input" and "output" and are not limited to the RF context of transmitting and receiving radio waves. Thus, for example, a chip or other device or component used to implement embodiments may generate data for output to, or have an input from, another chip, device, or component data, and this output or input may be meant to include "transmitting" and "receiving" in gerund form, that is, "transmitting" and "receiving", and this "transmitting" in an RF context and "receiving".

Any statement used in the form of "at least one of A, B or C", and the statement "at least one of A, B and C" is used in this specification, use an antinomial connective "or" and a The negative connective "and" makes those statements include any and all combinations and several permutations of A, B, C, that is, A alone, B alone, C alone, A and B in any order, A in any order and C, B and C in any order, and A, B, C in any order. More or less than three characteristics may be used in such statements.

In a request, any reference symbols placed between parentheses shall not be deemed to limit the request. The word "comprising" does not exclude the presence of elements or steps other than those listed in a claim. Furthermore, when the terms "a" or its variations are used in this article, they define one or more than one. Likewise, the use of prepositions such as "at least one" and "one or more" should not be taken to imply that the introduction of another claim element preceded by the indefinite article "a" would make any specific claim element containing the introduced claim element The claim is limited to an invention containing only one such element, even when the same claim includes prepositions such as "one or more" or "at least one", and indefinite articles such as "a" or its variations. . Unless stated otherwise, terms such as "first" and "second" are used to arbitrarily distinguish the elements described in such terms from each other. Therefore, these terms are not necessarily intended to indicate a temporal relationship or other prioritization of such elements. The mere fact that certain measurements are stated in mutually distinct claims does not indicate that a combination of these measurements cannot be used to produce a benefit.

Unless otherwise expressly stated to be incompatible, or the physical aspects of such embodiments, examples or claims otherwise prevent such combination, the features of the foregoing embodiments and examples, as well as the following claims, may be configured in any suitable arrangement. Structural integration, especially for features that would have beneficial effects in doing so. This is not limited to just any specific benefit, but can result from an "ex post" benefit. That is to say, the combination of features is not limited to the stated form, in particular the form(s) of the example(s), the form (eg numbering) of the embodiment(s), or the dependency of the claim(s). Furthermore, this also applies to terms such as "in one embodiment," "according to an embodiment," and the like, which are merely stylistic forms of a word and should not be used for all other instances of the same or similar word. The features that follow are considered to be limited to another embodiment. That is, a reference to "a," "an," or "some" embodiments may be a reference to any one or more, and/or all disclosed embodiments, or combinations thereof. Likewise, reference to "the" embodiment may not be limited to the embodiment immediately preceding it.

In the foregoing, a reference to a "layer" may be a reference to a predefined (or definable) part of the infrastructure, and a reference to a "layer" may be a reference to the network infrastructure, or a part thereof. A reference to a network protocol layer operating in /. A vertical slice, when used herein, may be referenced as or in relation to a vertical market segment. As used herein, any machine-executable instructions, or computationally readable medium, that can perform a disclosed method, and thus may be used synonymously with the term method or each other.

The foregoing description of one or more implementation aspects provides illustration and description, but is not intended to be exhaustive or to limit the scope of the invention to the precise forms disclosed. Modifications and variations are possible in light of the above teachings, or may be acquired from practicing various implementation aspects of the invention.

100‧‧‧Wireless Internet 110~140, 306‧‧‧vertical slice 112, 122, 132, 142‧‧‧Macro network layer part 114, 124, 134, 144‧‧‧Micro network layer part 116, 126, 136, 146‧‧‧D2D network layer part 118, 128, 138, 148‧‧‧PAN network layer part 150‧‧‧Core network layer part 160‧‧‧Radio access network layer part 170‧‧‧Device layer part 180‧‧‧Personal/wearing layer part 190‧‧‧First horizontal network slicing 195‧‧‧Second horizontal network slicing 200‧‧‧Second view 210‧‧‧Slice #1 211‧‧‧Slice #2 220‧‧‧Micro network layer 230‧‧‧Slice #3 240‧‧‧Personal Area Network Network Layer 300‧‧‧Illustration 302‧‧‧Network Class 304‧‧‧Radio Resources 410‧‧‧Base station part 410'‧‧‧Base Station 412‧‧‧Upstream/core network side communication function 414‧‧‧Base station computing function 414', 424'‧‧‧Processing resources 416‧‧‧Downstream/wireless/device-side communication functions 420‧‧‧Portable part 420'‧‧‧Portable device 422‧‧‧Typical cellular wireless communication link 424‧‧‧Local operation function 426‧‧‧Downstream communication link 430‧‧‧Wearable part 430'‧‧‧Wearable device 432‧‧‧Upstream communication link 434‧‧‧Limited local processing resource function 434'‧‧‧Project 500‧‧‧C-RAN Architecture 502~506, 604‧‧‧RRH 514‧‧‧BBU/BBU Pool 516~520‧‧‧Fronthaul link 522‧‧‧Core Network 524‧‧‧Wireless Device 600‧‧‧CPRI-based C-RAN architecture 602‧‧‧BBU/BBU Pool 606‧‧‧Fronthaul link 608‧‧‧Analog front-end 610‧‧‧Digital to Analog Converter 612‧‧‧Analog-to-digital converter 614, 622‧‧‧Choose 616, 624‧‧‧Compression and framing modules 618, 626‧‧‧Decompression and framing modules 620‧‧‧Layer Processing Module 628, 950‧‧‧antenna 700, 800‧‧‧Procedure 710~770, 850~870, 1010~1020, 1110~1120‧‧‧Steps 820~840‧‧‧Illustrative options 900‧‧‧Electronic Devices 910‧‧‧Application circuit system 920‧‧‧Basic frequency circuit system 921‧‧‧Radio frequency (RF) circuit system 922‧‧‧Third generation (3G) baseband processor 923‧‧‧Fourth generation (4G) baseband processor 924‧‧‧baseband processor 925‧‧‧Central Processing Unit 926‧‧‧Audio Digital Signal Processor 927‧‧‧Memory/Storage 930‧‧‧RF Circuit System 931‧‧‧Mixer circuit system 932‧‧‧Amplifier circuit system 933‧‧‧Filter circuit system 934‧‧‧synthesizer circuit system 940‧‧‧Front-end module (FEM) circuit system 960‧‧‧Network Interface Controller (NIC) Circuit System 965‧‧‧Network interface circuit system 1200‧‧‧Hardware resources 1204‧‧‧Peripheral devices 1206‧‧‧Database 1208‧‧‧Network 1210‧‧‧Processor 1212‧‧‧Processor 1214‧‧‧Processor 1220‧‧‧Memory/storage device 1230‧‧‧Communication Resources 1240‧‧‧Bus 1250‧‧‧Instruction

Aspects, features and advantages of embodiments of the present disclosure will become apparent upon reading the description of the embodiments with reference to the accompanying drawings, in which like symbols represent similar elements, in which: Figure 1 illustrates the broad concepts of vertical and horizontal network slicing. a first view; Figure 2 shows a second view of a part of the wireless network of Figure 1; Figure 3 shows what kind of The method slices a radio access network (RAN) into horizontal and vertical slices; Figure 4 shows a more detailed example of horizontal slicing in a scalable wireless network architecture based on an example; Figure 5 shows a first example based on an example Flexible cloud radio access network (C-RAN) architecture; Figure 6 shows a second exemplary C-RAN architecture according to an example; Figure 7 shows a first exemplary C-RAN architecture for flexible radio access network according to an example An exemplary process; Figure 8 shows a second exemplary process for flexible radio access network re-architecture according to an example; Figure 9 shows an exemplary process of an electronic device (such as a UE or a base station) according to an example Implementation aspect; Figure 10 shows a first illustrative method of radio access network re-architecture according to an example; Figure 11 shows a second illustrative method of radio access network re-architecture according to an example; Figure 12 according to an embodiment A schematic diagram showing one of the hardware resources.

700‧‧‧Procedure

Steps 710~770‧‧‧

Claims (20)

An equipment that can operate as a radio access network (RAN) control entity in a wireless communication network. The RAN control entity is coupled to a baseband unit (BBU) and a remote radio head (RRH). The equipment includes : Radio frequency (RF) circuitry that receives at least one communication from or transmits at least one communication to a wireless network device; and circuitry that: connects a physical RAN infrastructure or cloud radio The access network (C-RAN) is divided into one or more network slices; and the BBU and/or RRH are divided according to one of the deployment scenarios of the one or more network slices, and the wireless network resources are based on a vertical A vertical network slice consists of any one or more of the following: a logical partition of a physical radio access network infrastructure used for or dedicated to a single communication type; a logical partition of a physical radio access network infrastructure used for or dedicated to a single communication type; A logical partition of a physical radio access network infrastructure that is specific to a communications use case; a logical partition of a physical radio access network infrastructure that has the same features as in the physical radio access network infrastructure self-contained operations and traffic that are unrelated to operations and traffic on any other logical partition; and one of the horizontal network slices includes a logical partition of the computing resources of at least one device operating in the RAN, where the At least one device includes a base station, a controller, or a device served by the RAN. The equipment of claim 1, wherein the circuitry is further used to use a schedule for each of the one or more network slices operating or to be operated on the physical radio access network, or C-RAN Information, divide the BBU and/or RRH according to one of the deployment scenarios of the one or more network slices. The equipment of claim 1, wherein the circuit system is further used to divide the BBU and/or RRH according to one of the deployment scenarios of the one or more network slices using any one or more of the following: a type of universal public radio interface (CPRI)/Advanced CPRI technology; and a physical layer (PHY) segmentation technology across the BBU and RRH. Such as requesting the equipment of item 1, wherein the circuit system is used to divide the BBU and/or RRH to divide wireless network resources of the wireless network, wherein the wireless network resources include frequency/time resources and/or physical resources block (PRB). As claimed in claim 1, one of the vertical slices is a mobile broadband service using an advanced multiple-input multiple-output (MIMO) solution and a medium-to-high bandwidth fronthaul. The equipment of claim 1, wherein the circuit system is used to divide the BBU and/or RRH according to the parameters of the vertical or horizontal network slicing. For example, the equipment of claim item 6, wherein the parameters of the vertical or horizontal network slice include any one or more of the following: a data rate; a data bandwidth; a number of devices to be served; a latency; a mission criticality; a latency; a quality of service (QoS); or a network profile of a service. The apparatus of claim 1, wherein the circuitry further uses scheduling information for or belonging to each network slice to determine or perform fronthaul packetization. The equipment of claim 8, wherein the circuitry is further used to determine or perform forward packetization procedures as defined in any of the following: a common public radio interface (CPRI)/Advanced CPRI technology; and a link between the BBU and RRH's physical layer (PHY) segmentation technology. The apparatus of claim 9, wherein the circuitry is further configured to determine or perform a forward packetization process defined by a frequency/time resource schedule supporting an advanced MIMO technology, wherein the technology may include Coordinated Multipoint (CoMP) ), beam convergence or cellless operation any one or more of these. Such as the equipment of claim 9, wherein the circuit system is further used to determine or perform forward packetization procedures defined by a frequency/time resource schedule or technology that supports any of the following: mission criticality, latency, or bandwidth. Such as the equipment of claim 11, wherein the mission criticality applies to a delay-sensitive application. Such as the equipment of claim 11, wherein the equipment includes a base station. The equipment of claim 13, wherein the base station includes an enhanced Node B (eNB). An equipment for functional division of baseband unit (BBU) and remote radio head (RRH), including means to implement network slicing in different deployment scenarios, in which an evolved nodeB (eNB) will use the schedule of each network slice information to perform the BBU and RRH functional partitioning, where the eNB uses the scheduling information of each network slice for fronthaul packetization, and where the eNB will use frequency/time resources scheduled for low-latency services, such as For mission-critical Internet of Things (IoT) applications and/or devices, layer 2 (L2)/layer 3 (L3) BBU and RRH functions are divided. Such as the equipment of claim 15, wherein the eNB performs a type of common public radio interface ( CPRI) and/or advanced CPRI or physical layer (PHY) segmentation BBU and RRH functional division. Such as requesting the equipment of item 15, wherein the eNB performs Type 1 CPRI, PHY split, remote PHY, or L2/L3 on frequency/time resources scheduled for massive machine type communications (MTC) services or mobile broadband services Split the BBU and RRH functions. Such as the equipment of claim 15, wherein the eNB performs CPRI-like or PHY partitioning of the frequency/time resources scheduled to support advanced MIMO schemes such as coordinated multi-point (CoMP), beam pooling, cell-less operation, etc. The forward packetization procedure is defined by BBU and RRH partitioning. Such as requesting the equipment of item 15, wherein the eNB is configured to use the frequency/time resources scheduled for extremely delay-sensitive applications such as mission-critical IoT applications or mission-critical IoT devices. source, performs the forward packetization process defined for L2/L3BBU and RRH partitioning. Such as requesting the equipment of item 15, wherein the eNB performs CPRI-like, PHY segmentation, remote PHY, or L2 based on fronthaul BW and delay on the frequency/time resources scheduled for large-scale IoT and mobile broadband services /L3 splitting, etc. before transmitting the packetization program.