TW201715910A - Slice-based operation in wireless networks with end-to-end network slicing - Google Patents

Abstract

Embodiments provide a BS apparatus operable in a wireless communication for a 5G system, the apparatus comprising RF circuitry to receive at least one communication originating from a network virtualization component and/or software defined network, and baseband circuitry to identify based on information from the communication a first association of a first local component of a RAN and a second remote component of the RAN, the first association corresponding to a network slice, and identify based on information of the same or a different communication of the at least one communication a second association of the first local component of the RAN and a third component of the RAN that is different than the second component of the RAN, the second association corresponding to the network slice, wherein the second association is based on at least one of traffic type, traffic load, or a QoS requirement.

Description

Split-based operation in a wireless network segmented by end-to-end network

The embodiments described herein relate generally to the field of wireless communication systems, and in particular to the management of radio access networks for wireless communication systems.

Implementations of the invention may be generally related to the field of wireless communications.

According to an embodiment of the present invention, a device for wireless communication of a fifth generation (5G) system is specifically proposed, the device comprising: identifying a first end of a radio access network (RAN) a first associated component of the component with a second remote component of the RAN, the first association corresponding to a network segmentation; and the first local component for identifying the RAN and the RAN a second associated component of the third component, the third component being different from the second component of the RAN, the second association corresponding to the network segmentation; wherein the second relationship is based on a traffic type, a traffic At least one of a load or a quality of service (QoS) requirement.

According to another embodiment of the present invention, an apparatus for wireless communication of a fifth generation (5G) system is provided, the apparatus comprising: identifying a radio access network at a user equipment (UE) (RAN) a first associated component of the first local component and a second remote component of the RAN, the first association corresponding to a network segmentation; and for identifying the RAN at a UE a second associated component of the first local component and a third component of the RAN, the third component being different from the second component of the RAN, the second association corresponding to the network segmentation; The second relationship is based on at least one of a traffic type, a traffic load, or a quality of service (QoS) requirement.

In accordance with yet another embodiment of the present invention, an apparatus for operating a base station (BS) in one of a fifth generation (5G) system for wireless communication is provided, the apparatus comprising: a radio frequency (RF) circuit, The RF circuit is configured to receive at least one communication originating from a network virtualization component and/or a software-defined network; and a baseband circuit configured to: identify a radio access based on information from the communication a first association between a first local component of the network (RAN) and a second remote component of the RAN, the first association corresponding to a network segmentation; and the same or one based on the at least one communication Different communication information identifies a second association between the first local component of the RAN and a third component of the RAN, the third component being different from the second component of the RAN, the second association corresponding to the second component The network segmentation; wherein the second relationship is based on at least one of a traffic type, a traffic load, or a quality of service (QoS) requirement.

The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of illustration and description It will be apparent, however, to those skilled in the art that the invention may be In other instances, descriptions of well-known devices, circuits, and methods are omitted to avoid obscuring the description of the invention with unnecessary detail.

In the fourth generation of long-term evolution (4G-LTE) and LTE advanced/Pro wireless communication networks, there has been a heterogeneity trend in network architecture and applications. Examples of such trends are the development of small cell and relay networks, device-to-device (D2D) communication networks (also known as proximity services), and machine type communication (MTC). A small cell can be considered to be smaller than any form of cell of a conventional jumbo eNB/base station, such as a micro/mini/pico cell. Regarding the fifth generation (5G) wireless communication network, the heterogeneity trend can be more prominent, and suitable improved methods and devices for controlling wireless resources are desirable. For example, because in addition to more traditional voice services (eg, LTE-based voice, VoLTE) and mobile broadband (MBB), 5G wireless communication networks can expect to serve different ranges of applications (with various types of traffic and Demand), network and user equipment (with various communication and computing capabilities) and commercial market (ie usage), so it is desirable to provide control over each of these usage conditions to optimize or at least improve wireless Resource usage is possible.

Embodiments of the present invention generally relate to the segmentation of a Radio Access Network (RAN) architecture of a wireless communication network. The RAN may be part of a wireless communication network implementing one or more radio access technologies (RATs) and may be considered to reside on a location such as a mobile phone, a smart phone, a connected laptop or any The remote control (or simple access) is located at a location between the user devices (UEs) of the machine and provides a connection to a core network (CN) serving the wireless communication network. The RAN may be implemented using a silicon chip residing in a UE and/or a base station, such as an enhanced Node B (eNB), a base station, or a similar one that forms a cellular-based wireless communication network/system. Examples of RANs include, but are not limited to: GRAN (GSM Radio Access Network); GERAN (essentially EDGE allows GRAN); UTRAN (UMTS Radio Access Network); and E-UTRAN (LTE or LTE Advanced/ Pro, high speed and low latency radio access network).

The embodiments described herein discuss the general architecture of network segmentation 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 concept of horizontal and vertical network segmentation. Vertical segmentation can include segmentation of radio access networks based on vertical markets, where the vertical market can include a number of existing communications and a single type of new type of communication that can be made via future wireless communication networks, including specifically radio access networks. /Special type of communication (ie, can be defined as a single or specific use case for the communication involved). Commercial markets that can be deployed via wireless communication networks can also be referred to as vertical markets. Existing types include Mobile Broadband (MBB) and Voice (VoLTE), while new types of communications can include new types of connectivity services and usage, such as Machine Type Communication (MTC), Personal Area Network, Dedicated Health Network, Machine Pairs Machine to machine (M2M), enhanced MBB (eMBB), time critical communication, vehicle communication (V2X) (including vehicle to vehicle (V2V) and vehicle to infrastructure (V2I)) And similar. The definition of a vertical market is not limited and will cover any existing or future logical separation (ie, separation, segmentation, or the like) of a physical communication access network dedicated to wireless communication for a particular use or type of communication. In some instances, there may be multiple physical radio access networks in use, each of which is divided into logically separated radio access networks.

The proposed network segmentation can be planned and highly scalable and flexible to take into account the availability, latency and power requirements of the wireless communication network required by each particular use condition and for battery life, reliability, load, and security. And the impact of speed.

Network segmentation is considered to be one of the key technologies for meeting the different needs and services and applications of the 5G communication network. This is becoming more and more challenging as the spectral efficiency at the radio link level is further improved in wireless communication technologies, and it has been found that future wireless networks and devices powered by their wireless networks are being built to meet the increasing number of devices. A new way of loading demand. In order to achieve these goals, 5G and future generation wireless networks, and in particular the servos of their wireless networks or wireless devices powered by their wireless networks, evolved into a combination of computing and communication and end-to-end solutions. build. This is a paradigm shift since the technology development focused on the previous generation of a single level of communication.

To provide an increased load on the wireless network, the wireless network can be split. This may involve segmenting (ie, logically splitting/separating) a traditional larger single-action broadband network into multiple virtual networks to serve vertical industries and applications in a more cost effective and resource efficient manner. Each network segmentation can have different network architectures and different application, control, packet and signal processing capabilities and loads to achieve the best return on investment. New vertical cuts (ie, industry or service types) can be added to existing splittable wireless networks at any time, rather than deploying new private wireless networks for vertical markets. Thus, vertical network segmentation provides a practical means of separating traffic from the remaining general-purpose broadband services from a vertical application stand, thereby virtually avoiding or significantly simplifying traditional QoS engineering issues. Wireless network segmentation can include segmentation in both the core network and the radio access network (ie, an end-to-end solution).

In a 5G wireless network and beyond, the load adjustment of the network is no longer as uniform as in the previous generation. For example, the scale factor can be higher when the wireless network is closer to the user and lower when we move deeper into the infrastructure of the wireless network. This non-uniform adjustment can be the result of an enhanced user experience achieved by significantly increased sensing capabilities (and/or processing resources) available at the wireless device utilizing the wireless network. Unlike the network, which acts primarily as a data tube, 5G and future generation wireless networks can rely, at least in part, on wireless networks and wireless, as the airborne intermediaries improve end-to-end uniform (but singly) adjustments to previous generation wireless networks. Network servo/servo The information network for different (heterogeneous and/or homogeneous) computing, network connectivity and storage capabilities of wireless devices over wireless networks.

For example, the entire wireless network can continue to grow rapidly, but the computing and network connections at the edge of the network can grow even faster, thus enabling the processing of user data traffic at the edge of the wireless network (so-called Edge cloud application). The user device can no longer simply terminate the "terminal" of the communication link. Alternatively, it can become a next generation mobile or fixed network connection node for a new generation of consumer devices, machines and things. For example, a laptop, tablet, smart phone, home gateway, or any other wireless network device (or forming a component device such as a wireless network device sold to a consumer or forming part of a wireless network device) The component device) can become a computing and network connection center for a network cluster with many devices or things deployed around it. For example, it can form a Personal Area Network (PAN). Many of these actions or fixed wireless network clusters can form a network that can be called the underlying network—a new type of 5G network and a network other than 5G that can communicate with each other or directly with a fixed network. The device has a calculation that can be shared to a larger form factor platform or an edge cloud base station (ie, an entity with larger processing resources available in the wireless network at all times or only at that time). This can be done to achieve optimal action computing and communication on a virtualized platform across many devices, including the edge cloud.

This new type of wireless network adjustment can be driven by several factors. For example, since the device sensing is usually the local end, the processing of the sensed data may be the local end, and the decision and action on the sensed data become the local end. This trend can be further amplified by the proliferation of wearable devices and the Internet of Things. For example, as machines begin to play a greater role in communications than human users, the overall communication link speed can increase.

The definition of end-to-end is to be revisited due to the increasing number of communication links in the vicinity of the user and the user device. Therefore, it is proposed to provide a cloud architecture framework that can be incorporated into a data center and provide an edge cloud that is closer to the end user's or device's local intelligence and services. This is because, for example, as wireless networks and systems are deployed in enterprises, homes, offices, factories, and automobiles, edge-edge servers become more important for performance and information privacy and security. These latter factors can be driven by the increasing interest of users (and governments) in privacy and security. In addition, the data center deep in the fixed network can continue to grow rapidly, because many existing services can be better servoed by a centralized architecture, including a new generation of portable and wearable devices, remote control aircraft, industrial machines, and self-driving cars. And similar people bring even faster communication and computing power growth around the edge of the network and around local users.

The newly introduced network segmentation concept, in particular, provides a concept of a wireless network system architecture with end-to-end (E2E) vertical and horizontal network segmentation, which can be an empty intermediary plane, radio access. The network (RAN) and core network (CN) introduce changes to implement a wireless network system with E2E network segmentation.

In short, horizontal slicing requires shared computing by allowing devices across the servo wireless network or by wireless network servos (ie, in or on the network) to be processed according to their time and space/location. Resources increase the capacity of the device.

The horizontal network segmentation is designed to accommodate the new trend of traffic adjustment and to achieve edge cloud computing and computational sharing: computing resources in base stations and portable devices can be split horizontally, and such segments can be combined with wearable devices. The new wireless air interface design as described herein is integrated to form a virtual computing platform to significantly enhance the computing power of future portable and wearable devices. Horizontal segmentation enhances device capabilities and enhances the user experience.

In general, network segmentation can be viewed as enabling the use of virtualization technology to fabricate, partition, and organize the computing and communication resources of a physical wireless network infrastructure into one or more logically separated radio access networks to enable Flexible support for different usage scenarios. For example, in the case of network segmentation operations, a physical wireless network can be split into multiple logical radio access networks, each architected and optimized for specific needs and/or specific applications/services. (ie usage status). Therefore, network segmentation can be defined as independent in terms of operation and traffic flow, and can have its own network architecture, engineering mechanisms, and network deployment. Network segmentation as proposed herein simplifies the establishment and operation of network segmentation and allows for functional reuse and resource sharing (ie, provision of 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).

The goal of vertical segmentation is to support different services and applications (ie usage/communication type). Examples include (but are not limited to): Wireless/Mobile Broadband (MBB) communications; Extreme Mobile Broadband (E-MBB) communications; such as industry-controlled communications, machine-to-machine communications (MTC/MTC1), instant use; non-instant use conditions , such as Internet of Things (IoT) sensor communication or large-scale machine-to-machine communication (M-MTC/MTC2); ultra-reliable machine-to-machine communication (U-MTC); action edge cloud, for example fast Communication; vehicle-to-vehicle (V2V) communication; vehicle-to-infrastructure (V2I) communication; vehicle-to-anything communication (V2X). That is, the present invention is directed to providing network segmentation based on any easily definable/differentiated type of communication that can be performed over a wireless network. Vertical network segmentation enables resource sharing in services and applications, and avoids or simplifies traditional QoS engineering issues.

At the same time, the goal of horizontal network segmentation is to extend the capabilities of the devices in the wireless network, specifically to the mobile devices that are available to the local resources, and to enhance the user experience. The horizontal network splits across and beyond the physical boundaries of the hardware platform. Horizontal network segmentation enables resource sharing among network nodes and devices, ie, highly supported network nodes/devices can then share their resources (eg, computing, communication, storage) to enhance less support network nodes/devices ability. A simple example would be to supplement the processing and communication capabilities of the wearable device with a network base station and/or a smart phone mobile device. The end result of horizontal network segmentation can be to provide a next-generation (eg, mobile) infrastructure network cluster in which the mobile terminal becomes a mobile network connection node. Horizontal slicing provides air resource sharing across wireless network nodes. The wireless network air interface used in the wireless network can be a horizontally split integration part and an enabler.

Vertical network segmentation and horizontal network segmentation can form independent segments. The end-to-end traffic flow in the vertical segmentation can be transferred between the core network and the terminal device. The end-to-end traffic flow in the horizontal segmentation can be localized and transferred between the client and the host of the mobile edge computing service.

In vertical slicing, each of the network nodes can perform similar functions in separate slicing. The dynamic aspect of vertical segmentation can be mainly based on resource segmentation. However, in horizontal slicing, new functions can be established at the network node when segmentation is supported. For example, portable devices may use different functions to support different types of wearable devices. The dynamic aspect of horizontal segmentation can therefore lie in network functions and resource segmentation.

Figure 1 shows a first view of the broad concept of vertical and horizontal network segmentation. A complete wireless network 100 is shown that includes a plurality of vertical segments 110 to 140 of different vertical (or at least separate) vertical markets (i.e., usage conditions). In the example shown, vertical segmentation #1 110 servo action broadband communication, vertical segmentation #2 120 servo vehicle to vehicle communication, vertical segmentation #3 130 servo security communication, and vertical segmentation #4 140 servo industry Control communication. These are merely exemplary use cases and may be virtually unrestricted by the condition of use of the severable wireless network servo in accordance with the present invention.

Wireless network 100 includes a core network layer portion 150 (e.g., a plurality of server/control entities/control portions having eNode-B or the like), a radio access network layer portion 160 (e.g., including a plurality of base stations, e -Node B, etc., device layer portion 170 (including, for example, a portable device such as a UE, a vehicle, a monitoring device, an industrial device, etc.) and a personal/wearable layer portion 180 (including, for example, a wearable device such as wisdom type wristwatch, health monitor, Google ^TM glasses / Microsoft ^TM type holographic lens means and the like). The wearable portion may be only involved in some use cases, as shown by the vertical cuts #1 and #2 included in the example of FIG.

In the vertical domain, the physical computing/storage/radio processing resources (as represented by the server and base station 150/160) and the physical radio resources (as time) in the network infrastructure are segmented by usage status (ie, communication type) , frequency and space) to form end-to-end vertical segmentation. In the horizontal domain, the physical resources (in terms of computation, storage, radio) in the neighboring layers of the network hierarchy are segmented to form a horizontal slice. In the illustrated example, there is a first horizontal network segmentation 190 operating between the RAN 160 and device 170 layers, and a second horizontal network segmentation 195 operating between the device 170 and the wearable 180 layer. The servo or any given device to be servoed by the wireless network 100 as a whole and in particular the RAN 160 (and lower layers) can operate on multiple network segments of either (or both) types. For example, a smart phone can operate in a vertical segmentation of a mobile broadband (MBB) service, a vertical segmentation of a health care service, and a horizontal segmentation of a wearable device.

When the network segmentation in the RAN (including the null mediation used in the RAN) is enabled, in addition to satisfying the 5G requirements (for example, data rate, latency, number of connections, etc.), it is used to enable network segmentation and general 5G. Further desirable features of the RAN/space intermediaries used therein may include flexibility (ie, support for flexible radio resource allocation among segments); adjustability (ie, easy to scale up the addition of new segments); and efficiency (eg, , efficient use of radio and energy resources).

Horizontal slicing can include layers that categorize network layers, such as network connectivity and computing (ie, processing resources) capabilities. This can be done across any number of vertical slicings that are servoed by the network 100, such as falling from any vertical market to one or more vertical cuts. This display is the different widths of the two exemplary horizontal cuts in Figure 1 - horizontal cut #1 190 is limited to a single vertical cut, while horizontal cut #2 covers two vertical cuts. Examples of network layers/layers may include, but are not limited to, a giant network layer, a micro/small cell network layer, a device-to-device communication layer, and the like. Other network layers can also be involved.

2 shows a second view 200 of a portion of the wireless network 100 of FIG. In particular, Figure 2 shows an example of segmenting a particular RAN architecture, where the sharding can span multiple levels of a traditional wireless network architecture. For example, the RAN architecture for each of the segments can be dynamically grouped depending on factors such as traffic type, traffic load, and QoS requirements. In the first example, the segmentation #1 210 may operate only at the giant cell level. However, the segmentation #2 220 operates only at the small cell level. Finally, the segmentation #3 230 can operate on both the giant and small cell levels. In another example, the segmentation (eg, segmentation #1 210) may open the operation on the small cell and the other segmentation (eg, segmentation #3 230) may close the operation on some of the small cells.

The open operation/start split can be referred to as network split enable, and the close/destart split can be referred to as network split disconnect. Segmentation of a particular RAN architecture may require segmentation of specific control plane/user plane operations, split/off operations, and segmentation based access control processing and load balancing processing, as will be discussed in greater detail below.

Computational sharing can be achieved by including horizontal segmentation of the segmentation network/device computing and communication resources. Examples include the base station using its computing resources to facilitate the calculation of the user device, or the user device (eg, a smart phone) using its computing resource segmentation to facilitate the calculation of the associated wearable device. .

Embodiments of the invention are not limited to the segmentation in the vertical (market) or horizontal (network level/layer) direction of any particular form.

Embodiments of the present invention may provide a management entity operable across a control plane (C-plane) and/or a user plane (U-plane) that may be provided to coordinate different horizontal or vertical splits (or multiple/combinations, A management plane entity that operates on or in part, one. The management entity can use a flat management architecture or a hierarchical management architecture.

The segmentation of the radio access network can be considered as a compartmentalization of the radio access network according to a predetermined vertical market or horizontal network layer (or multiple/partial layers) of the network. This can be viewed as a logically separated form between radio resources provided by or used by the radio access network. The logical separation of wireless resources may allow them to be separately defined, managed, and/or (substantially or specifically) resourced. This separation can provide the ability for different segments to be unable or not to be allowed to affect each other. Also, in some embodiments, one or more segments may specifically have the ability to manage one or more segments for operational reasons.

In some embodiments, the network function can be fully shared to the network segmentation, and the segmentation can operate in a standalone mode, such as a small millimeter wave (mmWave) small cell network and an out of range D2D network. The mmWave small cell is a cell that uses millimeter-sized radio waves (i.e., higher frequencies, such as 60 GHz).

In some embodiments, the network functions may be partially shared to the split, and the splitting may operate in a non-independent mode, such as operating in an anchor enhancer architecture, where the anchor enhancer architecture may include an anchor cell to provide a control plane and for An operational anchor that maintains connectivity. In an embodiment, the anchor cell may be a cell with a wide coverage, such as a giant cell. The anchor enhancer architecture may further include an enhancer cell to provide user plane data sharing. In an embodiment, the booster cell may be a small cell and may be deployed under the coverage of the anchor cell. From the perspective of the device, the control plane and the user plane can be decoupled, ie the control plane can be maintained at the anchor cell and the data plane can be maintained at the booster cell.

In some example embodiments, horizontal slicing and vertical slicing may be considered interlaced (ie, radio access network functions/resources are commonly used in some of vertical and horizontal slicing), as shown in FIG. Illustrated in 300. Thus, Figure 3 shows how the Radio Access Network (RAN) can be split into horizontal and vertical splits according to an alternative (or additional) embodiment of the embodiment shown in Figure 1, where the traffic flow and operation are cut Points are completely independent. The graph 300 of Figure 1 has a network hierarchy 302 along the y-axis (i.e., involved/is in use of the network layer) and radio resources 304 along the x-axis (i.e., indicating the use of separate radio resources such as frequency, time slot, etc.) . In the example of FIG. 1, the vertical cut is shown to include four vertical cuts 306. However, any number of different markets/use cases can be involved. The four vertical markets/usages selected for vertical segmentation are Mobile Broadband (MBB) 110, Vehicle Type Communication (V2X) 120, First Machine Type Communication (MTC-1) 130, and Second Machine Type Communication ( MTC-2) 140, which is a segmentation segmentation #1 to a segmentation #4, respectively. These are merely illustrative choices for servo-available conditions.

Horizontal cuts are also shown in Figure 3, which in this example also includes four horizontal cuts 308. The four levels shown are divided into a mega network layer 210, a micro network layer 220, a device-to-device network layer 230, and a personal area network (PAN) (e.g., wearable) network layer 240. According to an example, each horizontal slice contains one of a plurality of vertical segments. Similarly, each vertical cut contains one portion of each horizontal cut. A separate portion as separated in both the horizontal and vertical directions may be referred to as a dicing portion. Thus, in the example of FIG. 1, MBB vertical slice 110 includes four sliced portions: mega network layer portion 112; micro network layer portion 114; D2D network layer portion 116; and PAN network layer portion 118. Similarly, V2X vertical slice 120 includes four sliced portions: giant network layer portion 122; micro network layer portion 124; D2D network layer portion 126; and PAN network layer portion 128. Meanwhile, the MTC-1 vertical slice 130 includes four sliced portions: a giant network layer portion 132; a micro network layer portion 134; a D2D network layer portion 136; and a PAN network layer portion 138, and the MTC-2 is vertical. The segment 140 includes four segmentation portions: a giant network layer portion 142; a micro network layer portion 144; a D2D network layer portion 146; and a PAN network layer portion 148.

In a personal area network, an example of this architecture is a wearable health sensor that can belong to a dedicated health network. The personal area network layer can then represent a horizontal network segmentation. Health sensors that operate under the coverage of a personal area network can be classified as vertical network segments. By the same token, each horizontal network segmentation can include multiple vertical network segments. Each vertical network segmentation can have multiple horizontal network segments. Another example is a mega cell (ie, a giant eNB) that is servant for several different usage conditions communications. Similarly, each vertical slice can contain portions of multiple horizontal slices, for example, in a V2X network, there can be a V2I layer and a V2V layer. In another example, the Mobile Broadband (MBB) vertical segmentation includes portions of each of the giant, micro, and device-to-device layers, as shown. Thus, embodiments provide a way to logically divide the radio resources provided by the radio access network and/or used by the radio access network based on both the usage conditions (vertically) and the network layer (horizontally).

Communication and computing are helping each other to drive the boundaries of information and computing technology. At the network side, calculations have been used to facilitate communication by moving calculations and storage to the edge. In the case of edge cloud and edge computing, the communication link between source and destination becomes shorter, thereby improving communication efficiency and reducing the amount of information transmitted in the network. The optimal deployment of edge clouds and computing solutions will change. The general rule is that the less support and/or the higher the density of the final device, the closer the cloud and computing are to the edge of the network.

At the side of the steering device, where the device self-portable device is further downsized to the wearable device and the user's expectations for computing continue to increase, we anticipate that future communications will help convey the user experience, such as the network node cutting out its Portions of the computing resources are used to facilitate calculations at the portable device, while portable devices cut out portions of their computing resources to facilitate calculations at the wearable device. In this way, the network is split horizontally. The computing resources and the empty intermediaries at both ends of the connection are cut out to form an integrated part of the services required for transportation.

4 shows a more detailed example of a horizontal segmentation in a severable wireless network architecture, in accordance with an embodiment. The traditional 3G/4G architecture is shown on the left (but only from the RAN down). This includes a base station portion 410 that includes an upstream/core network side communication function 412, a base station computing function 414 (ie, processing resources available in the base station or its tightly coupled entities), and downstream/wireless/device side communication functions 416 (with Communication by the base station servo or other peer base station (for example, under the pre-transmission status). A portable portion 420 (e.g., user device or similar device) is also shown that includes similar combinations 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, an OFDM/CDMA/LTE type link) and the downstream communication link 426 is such as a 5G radio access technology (RAT) (eg, OFDM) /CDMA/LTE type link), next generation communication link such as 5G PAN RAT (to be established) or current or next generation other PAN wireless communication technologies, such as Bluetooth, Zigbee or the like. In the meantime, the local computing function 424 is the processing resource of the local end of the portable device. Finally, in this example, there is a wearable portion 430 that typically only has a single upstream communication link 432 and a restricted local processing resource function 434.

The right side of Figure 4 shows one of the new proposed horizontal network segmentation concepts, specifically how to use the entity to capture part of the communication and processing resource capabilities "combination" (that is, sharing among themselves) in the network Processing resources for the upper and lower entities. The basic functions are similar and are therefore represented as items 410' to 434', respectively, and function in a similar manner. However, there is now a concept of horizontal segmentation, in which case the horizontal slices #1 190 and #2 195 of Figure 1 are shown in greater detail. In this basic example, the wearable device 430' can utilize the processing resource 424' of the portable device 420' by sharing the processing data (eg, the processed data and the synthesized processed data) using the communication function. Similarly, the portable device 420' can use the processing resource 414' of the base station 410'.

A more detailed description of one part of the network segmentation concept will now be made in accordance with the present invention. In some instances, such functionality may be provided as a new network function (NF), which may be virtualized, for example, by using Network Function Virtualization (NFV). These NFs and NFVs may be singularly specific or manipulated on multiple/all cleavage points. The proposed wireless network as a whole (e.g., including the core network) and the specific RAN are now aware of the segmentation by utilizing the newly implemented segmentation identification.

In accordance with the present invention, network segmentation is designed to establish a specific end-to-end communication solution and to implement an adjustable 5G radio access network (RAN) and core with heterogeneous deployment, heterogeneous traffic and services, and heterogeneous requirements. Network (CN). Network segmentation is considered one of the key technologies for 5G.

The criteria and granularity for network segmentation are implementation specific. However, as discussed above, in general, network segmentation can include two dimensions: vertical segmentation and horizontal segmentation and can be performed to achieve user-centric services.

Each segmentation can be independent, operating on assigned logical resources, such as a logically separated radio access network (RAN) and a corresponding (ie, servo) core network (CN). In an example, this may involve segmentation specific processing in the CN and RAN. In the CN, Network Function Virtualization (NFV) and Software Defined Network (SDN) can be the technology enabler for network segmentation. For example, NFV and SDN can be used to virtualize network components and functions, which in turn enables easy to assemble/reuse network components and functions in each segmentation (or for each segmentation) to satisfy everything. Divided into its own operational needs. In the RAN, sharding can be established on logical resources abstracted from physical radio resources (eg, transmission points, spectrum, time, etc.). Each segmentation can have its own empty mediation plane and RAN architecture.

In the RAN, each cell site may have multiple shards operating thereon, each shard may have its own RAN architecture, and each mobile device, such as a User Equipment (UE), may subscribe to one or more Segmentation. As with current mobile networks, mobile device (e.g., UE) association, access control, and load balancing schemes can be segmented rather than cell specific. The split/close operation can be enabled at each access point (AP) or base station (BS). The control plane and user plane assembly can be customized to consider the operation based on the division. In a sense, segmenting a particular operation can obscure the concept of a physical cell site (e.g., a base station) and direct network operations to service/traffic/user oriented rather than physical cell steering.

An example of the invention provides a divisional basis in the RAN. Specifically, the following aspects are discussed: 1) segmentation of a specific RAN architecture; 2) control plane and user plane combination in the case of network segmentation; 3) split/close operation; 4) based on segmentation Take control; and / or 5) load balancing based on segmentation. 1. Split the specific RAN architecture

2 shows an example of segmenting a particular RAN architecture depending on factors such as traffic type, traffic load, QoS requirements, and the like, and the RAN architecture for each of the partitions may be dynamically grouped. The proposed severable RAN architecture may include control plane and user plane functions that may provide functionality and other functionality for split/off operations and segmentation based access control processing and load balancing processing. The proposed severable RAN architecture can utilize control plane and user plane operations, where the c-plane portion can be either shared or sliced specific or a combination thereof, as will be explained in the following sections. 2. Control plane and user plane combination in RAN

Depending on how the control plane (C-plane) and the user plane (U-plane) are coupled (decoupled) into the RAN, there are various options for how the C/U plane can be assembled for the severable RAN architecture. In the following, reference to "decoupling" may mean that the individual parts are not co-located or are not on the same logical or physical signal path for signaling messages (ie, if decoupled, for C-plane messages) Does not travel the same path as the message for the u plane). The term coupling may mean the opposite, that is, the individual parts are co-located or on the same logical or physical signal path for signaling messages. Option 1 : Control plane as independent segmentation , decoupling control plane segmentation and user plane segmentation

In this option, the C plane and the U plane of each network segmentation are decoupled. There may be one C-plane segmentation that supports all U-planes. The C-plane segmentation and the U-plane segmentation can operate on different network nodes. For example, the C-plane segmentation can be maintained at the jumbo BS, while the U-plane segmentation can operate on the jumbo BS, on the small cell BS, and/or via device-to-device links. The advantage of this option is that the C-Plane function can always be turned on, providing full coverage for devices that are segmented by the network. A disadvantage can be a handshake exchange between a C-plane shard and a U-plane shard when it is not physically co-located. FIG. 5 shows an example C/U plane implementation 500 with decoupled assembly of network segmentation. In particular, FIG. 5 shows a global commonal c connected to a respective u-plane (eg, u-plane 520 of slice #1, u-plane 530 of slice #2, all down to u-plane 540 of slice #N) Plane 510 (ie used for all network segmentation). That is, the particular number of (segmented) u-plane dicing/the number of shards used is arbitrary for any given instance implementation and the current environment in which it is implemented. Option 2 : Each control plane is coupled to the user plane

In this option, the C-planes of each slice are coupled to the U-plane and are physically co-located. The advantages of this combination may include less control of the transmission delay and transmission of additional load among the transmission points. In some instances, to ensure coverage of the C-plane, the severing may remain open at a transmission point that has only minor traffic with respect to the segmentation. 6 shows a C/U plane coupled tangent packet 600 in which a sliced specific c-plane 610 of slice #1 is coupled to a u-plane 620 of slice #1, and a slice of slice #2 is coupled to a particular c-plane 630. The u-plane 640 of #2, and can continue to fall all the way down to (ie, at most) the segmentation #N, the particular c-plane 650 is coupled to the u-plane 660 of the segmentation #N. Again, the number of segments used is arbitrary for the implementation and implementation of the current environment. Option 3 : Splitting the control plane into a common control plane to slice and segment the specific control plane

In this option, some of the shared control plane functions, such as those in the 'Radio Resource Control Idle' (RRC-Idle) mode (eg, paging, cell reselection, location update), can be classified into a common C-plane portion, Functions in the 'Radio Resource Control Connection' (RRC-Connected) mode (eg, handover, dedicated bearer settings) can be classified into specific control plane functions. In an example, the advantage is to provide coverage and at the same time reduce control signaling exchanges among network nodes. 7 shows a partially decoupled C/U plane assembly 700 in which a common c-plane function 710 is coupled to: a split-specific portion 720 of slice #1 and a split-specific u-plane function 730 of slice #1; The segmentation of the specific portion 740 and the segmentation #2 is divided into a specific u-plane function 750, and can continue to fall until (ie, at most) the segmentation #N of the segmentation specific portion 760 and the segmentation #N segmentation specific u plane function 770. Again, the number of segments used is arbitrary for the implementation and implementation of the current environment. 3. Cut/close procedure

Regardless of the c-plane/u-plane topology, the proposed segmentation-specific RAN architecture essentially recommends the use of a split/close procedure. Some of the contexts of splitting/closing include: opening a segmentation in a small cell under the coverage of a giant cell; opening a segmentation in a cell operating in a different frequency band (eg, a high frequency band, an unlicensed band). The triggering of the splitting at the access point may include: a) the split traffic load exceeds a certain threshold - for example, this information may be obtained from the UE attempting to access the AP on the split and/or Indicated by neighboring APs and/or by a network central controller and/or by an AP in a parent hierarchy (e.g., a giant cell). b) the number of UEs operating in the segmentation exceeds a certain threshold - for example, this information may be obtained by the UE attempting to access the AP on the slice and/or by the neighboring AP and/or by The AP in the parent class (for example, a giant cell) indicates. c) in order to maintain the service continuity of the mobile UE, where the US moves across the base station (eg, the giant BS) and is connected to a specific segmentation (or multiple segments) on one base station, but it will move (and The base station to which it is handed over does not yet have any or all of the individual divisions that operate on it. d) In order to meet certain QoS requirements, such as low latency, ultra-reliability, etc., that is, QoS demand agitation can be best/better servo QoS level by new segmentation.

The splitting at an AP can be triggered by the UE or by the network. Figures 6 through 8 show the split open procedure by different types of triggers. When triggered by the UE, the UE may send an indication of the expected segmentation during random access. The split open procedure may vary depending on the type of UE trigger (ie, due to traffic load or due to QoS requirements). In the traffic load actuated split open, the BS can turn on splitting only when it sees enough traffic incoming. If the BS decides not to enable the split, the UE access request may not always be accepted. In QoS-driven splitting, the BS can turn on the sharding when it has QoS requirements. A UE access request is acceptable in view of the fact that the requested QoS satisfies certain criteria. When triggered by the peer BS/AP, the peer BS/AP may send a trigger message to request the splitting at the target BS to be opened.

8 shows a first example 800 of UE triggered split splitting (ie, split splitting). In the example of FIG. 8, the agitation parameter is that the number of UEs requesting the severing (on) exceeds a certain threshold. In FIG. 8, the instance open procedure begins with random access by an individual UE including an indication (ie, a data element) of the expected segmentation that the UE wishes to use. This includes a message 810 sent from the UE to the base station. The receiving base station can then turn on the requested network segmentation 820 when sufficient UE has requested to use the same network segmentation (i.e., the number of thresholds has been exceeded). Since the splitting is enabled, the message that the splitting is enabled can be sent from (and received to) the base station to (and from) the mobility management entity (MME) or other network control entity that implements the split management procedure, the message is about The division of the information is exchanged. This is shown in Figure 8 as a two-way message arrow 830. The result of the combined message exchange can be a wireless resource (eg, frequency, numerology, etc.) assigned for the segmentation to be turned on. The segmentation information may then include 850 in the system information message (ie, system broadcast information) for preparation for access by all devices served by the respective base stations (and/or network control entities). This allows all devices wishing to access the newly opened segment to have information such as by providing segmentation specific control information such as, but not limited to, Downlink Control Information (DCI), Entity Random Access Channel ( PRACH resources, split random access (RA) allocations, and the like. With this new acquisition information, the individual UEs can then randomly access the newly established network segmentation 870.

9 shows a second instance 900 of UE triggered split splitting, where the agitation parameter is that the type requested by the UE belongs to certain QoS levels. The procedure is very similar to the procedure 800 of Figure 8 (similar items are referenced by the same number). In this case, however, the split 920 is turned on after the device sends a request for a given QoS level (e.g., by having random access with individual request information therein). In some implementations, other levels may be provided. In this example, the base station provides a random access response 930 earlier, which means that the device based on the QoS requirement request segmentation can access the segmentation earlier and is in a simplified manner at 940, since at least a portion of the information has been Provided to the device in message 930.

FIG. 10 shows a first example 1000 of network triggered split splitting. In the example of this figure, there is a triggering base station (ie, a base station that requests to turn on the sharding, for example, it may already have a separate operating division, and will hand over the UE to the target base station), and the target base station ( That is, receiving the base station that opens the request for each split, for example, because the device that uses the splitting is to be handed over). The request is sent from the trigger base station to the target base station 1010. The target base station then begins to turn on the respective split 1020, which instigates the splitting of the combined information 1030 with the MME/Managed Separate Network Control Entity. The MME/network control entity provides packet splitting information to the target base station 1040 (and accordingly sets the splitting accordingly), and the respective split information can then be included in the system information broadcasted to all devices, so that it is desired to access the new The device that turns on the segmentation can operate using the broadcast information.

At the same time, the trigger to disconnect the split at the access point (or base station) may include: a) the split traffic load is below a certain threshold; b) the number of UEs operating in the splitting is low At a certain threshold.

Figure 11 shows an example split disconnect procedure 1100 in a base station (e.g., a source base station). This example is a condition of the number of traffic loads/connections on the UE reporting and segmentation based on neighboring cell conditions, and the BS (source BS) may decide to disconnect the segmentation. In order to prepare for the disconnection, the BS may hand the active UE to be connected to the BS operating on the sever to the neighboring BS (ie, the target base station) on which the operation is severed. The procedure of Figure 11 begins by transmitting a message 1110 including the report of the target base station from the UE currently connected to the source base station to the source base station. Based on the report in message 1110, the source base station may decide to disconnect (ie, turn off) the split because it now satisfies the split disconnect condition, such as a low traffic load. A split device (e.g., UE) can be handed over to a neighboring base station to maintain its service continuity. In this case, the source base station bootstrap (i.e., agitation) handover procedure 1130 can be performed to deliver the device to the corresponding segmentation on the target base station. Information exchange 1140 about the S1 interface (or any other suitable base station to core network interface) can then be performed to exchange information for the re-assembly target and the segmentation status on the source base station, such that the source base station The cut can then be closed at 1150.

As can be seen from the examples described above, the opening and closing of a particular network segmentation can be agitated by any entity that utilizes the function of segmentation or providing segmentation and agitates for a variety of reasons. The illustrated examples are merely illustrative types of segmentation management programs and subroutines that may be utilized in their management programs in accordance with the present invention. 4. Segmentation based access control

Since each RAN architecture can be different, access control can also be singularly specific. Access control applies when the UE attempts to become a Radio Resource Control (RRC) connected mode and/or during handover. For UEs in idle mode, the UE can camp on any base station and remain in idle mode. In this case, the C/U plane assembly options 1 and 2 discussed (Figs. 5 and 6) can be applied.

FIG. 12 shows an example of segmenting a particular random access procedure 1200. The base station system information (i.e., the broadcast system information) can carry information 1210 about the role of the segmentation in the BS. Based on the BS system information, the UE may decide 1220 whether to perform random access with the BS. If the expected segmentation is active in the BS and a good channel condition is given, the UE may access the active segmentation 1230 by performing an RA request that includes information about the segmentation that the UE will access. Even if the expected segmentation is not supported by the BS, the UE may still decide to request access. In this case, the factors that influence the decision may be: link conditions, QoS requirements, traffic load of neighboring cells, and the like. If the UE makes an access request but the split is currently not active in the BS, the BS may have to decide whether to accept the request and turn on the respective split. A handshake exchange between the BS or the BS and the central controller can be used to facilitate BS decisions (e.g., as shown in Figures 8-11). Once the BS decides to accept the access request, the BS can use the procedure discussed in the previous section to turn on the segmentation. In either case, the base station may respond (ie, affirmative or negative) 1240 to the base station requesting the UE RA.

In an example, for UEs that can simultaneously operate on multiple shards and where multiple shards are initiated in different APs or BSs, the UE may have to maintain multiple connections simultaneously. In this case, the C/U plane assembly options as discussed in the previous section become important here. For example, the UE may be anchored in one C-plane and maintain multiple connections on differently sliced U-planes (like C/U plane assembly options 1 - 5), or the UE may have to maintain basic C A common C-plane of the planar operation, with each segmentation specific/dedicated C-plane portion (like C/U plane assembly option 2 - Figure 6) or the UE can have multiple connections for each servo segmentation and Multiple C planes (like C/U plane assembly option 3 - Figure 7).

In an example, a load balancing based on segmentation can be provided. Segmentation-based load balancing enables traffic shaping gain, reduced control signaling extra load, and/or improved overall spectral efficiency. Operation with respect to split-based load balancing may involve coordination across the sever and across the AP/BS. A handshake exchange can be used with respect to the load conditions of each of the segments in the AP/BS. Load balancing based on segmentation may require joint application of split/close programs and segmentation of specific access control procedures.

In an example, a segmentation specific RAN architecture is provided. The RAN architecture of each of the shards can be dynamically grouped depending on factors such as traffic type, traffic load, and QoS requirements.

In an example, a control plane and user plane combination option can be provided to support RAN segmentation. In an example, the C/U plane can be self-cutting and decoupling (eg, the control plane is used as an independent segmentation, and the decoupling control plane is segmented from the user plane). In another example, the C/U plane may not be self-cutting packet decoupling (eg, the control plane in each of the points is coupled to the user plane). In another example, the C/U plane may be partially self-cutting packet decoupling (eg, the control plane splits into a common control plane to slice and slice a particular control plane). In some instances, decoupling may be provided by ensuring that the decoupled portions are not co-located or do not contain the same logical or physical signal path. For example, when the C-plane is decoupled from the U-plane, the C-Plane function does not co-locate with the U-Plane function and/or the C-Plane message transmission does not follow the logical or physical signal path that is the same as the corresponding U-plane message transfer. In some examples, the coupling may be provided by ensuring that the coupling portions co-located or contain the same logical or physical signal path. For example, when the C-plane is coupled to the U-plane, the C-Plane function is co-located with the U-Plane function and/or the C-Plane message transfer follows the same logical or physical signal path as the corresponding U-plane message transfer.

In an example, the triggering factor for the split/close at the AP or the BS may include at least one of the following: the traffic load of the split at the AP/BS exceeds a certain threshold, and operates on the other The number of UEs in the role of segmentation exceeds a certain threshold to maintain service continuity of the mobile UE or to meet certain QoS requirements, such as low latency, super reliability, and the like.

In an example, the splitting at an AP can be triggered by the UE or by the network. When triggered by the UE, the UE may send an indication of the expected segmentation during random access. When triggered by the peer BS/AP, the peer BS/AP may send a trigger message to request the splitting at the target BS to be opened. When the splitting is turned on, the AP/BS and the MME/network control entity can exchange the signaling.

In an example, the split open procedure may be different depending on the type of UE trigger (eg, due to traffic load or due to QoS requirements). In an example, in the traffic load actuated split open, the BS may turn the split only when it sees sufficient traffic incoming. In an example, if the BS decides not to enable the sharding, the UE access request may not be accepted. In another example, in QoS-enabled segmentation opening, the BS may turn on segmentation in response to QoS requirements (eg, accepting UE access requests in view of certain criteria being met for the requested QoS).

In an example, the triggering for breaking the segmentation at the access point can include at least one of: the traffic load of the segmentation is below a certain threshold, or operates on a segmentation The number of UEs in the role is below a certain threshold.

In an example, the BS may determine the disconnection split based on at least one of a UE reporting or splitting traffic load/connection number condition for neighboring cell conditions.

In an example, when the split is broken, the BS hands over the split UE in the handover to the neighbor BS.

In an example, the BS system can carry information about the roles in the BS.

In an example, the UE may decide whether to access the BS based on at least one of an expected split at the BS, a link condition, a QoS requirement, or a traffic load of a neighboring cell.

In an example, a handshake exchange between the BS or the BS and the central controller can be used to assist the BS in determining whether to enable the split.

In an example, for UEs that can operate on multiple shards simultaneously and multiple shards are initiated in different APs or BSs, the UE can maintain multiple connections simultaneously.

In an example, split-based load balancing may require coordination across the shards and across the AP/BS. A handshake exchange can be used with respect to the load conditions of each of the segments in the AP/BS.

As used herein, the term "circuitry" may mean the following, part of or include: special application integrated circuits (ASICs), electronic circuits, processors (shared, dedicated, or group). And/or memory (shared, dedicated or group) of one or more software or firmware programs, combinational logic circuits, and/or other suitable hardware components that provide the described functionality. In some embodiments, the circuitry can be implemented in one or more software or firmware modules, or the functions associated with the circuitry can be implemented by one or more software or firmware modules. In some embodiments, the circuitry can include logic that is at least partially hardware operable. As used herein, the term device (served by RAN or network segmentation) and UE may be interchangeable.

Embodiments described herein can be implemented using any suitably assembled hardware and/or software system. For one embodiment, FIG. 13 shows example components of electronic device 1300. In an embodiment, the electronic device 1300 may be one of the following, implement the following, be incorporated in, or otherwise be part of: a User Equipment (UE), an Evolved NodeB (eNB), or Another network component (e.g., a network component corresponding to a network virtualization device and/or a software-defined network device). In some embodiments, the electronic device 1300 can include at least an application circuit 1310, a baseband circuit 1320, a radio frequency (RF) circuit 1330, a front end module (FEM) circuit 1340, and one or more antennas coupled together as shown. 1350.

Application circuit 1310 can include one or more application processors. For example, application circuit 1310 can include circuitry such as, but not limited to, one or more single core or multi-core processors. A processor can include any combination of general purpose processors and special purpose processors (eg, graphics processors, application processors, etc.). The processor can be coupled to the memory/storage and/or can include a memory/storage and can be configured to execute instructions stored in the memory/storage to cause various applications and/or operating systems to be in the system Run on.

The baseband circuit 1320 can include circuitry such as, but not limited to, one or more single core or multi-core processors. The baseband circuit 1320 can include one or more baseband processors and/or control logic to process the baseband signals received from the receive signal path of the RF circuitry 1330 and generate a baseband signal for the transmit signal path of the RF circuitry 1330. . The baseband processing circuit 1320 can interface with the application circuitry 1310 for generating and processing baseband signals and for controlling the operation of the RF circuitry 1330. For example, in some embodiments, the baseband circuit 1320 can include a second generation (2G) baseband processor 1321, a third generation (3G) baseband processor 1322, and a fourth generation (4G) baseband processor. 1323 and/or other existing baseband processors 1324 that are on behalf of the generation, or are to be developed in the future (eg, fifth generation (5G), 6G, etc.). The baseband circuitry 1320 (eg, one or more of the baseband processors 1321 through 1324) can handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 1330. Radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, and the like. In some embodiments, the modulation/demodulation circuitry of the baseband circuit 1320 can include Fast Fourier Transform (FFT), pre-write code, and/or cluster mapping/demapping functionality. In some embodiments, the encoding/decoding circuitry of the baseband circuitry 1320 can include convolution, tail biting convolution, turbo code, Viterbi, and/or low density parity check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to such examples, and other suitable functionality may be included in other embodiments.

In some embodiments, the baseband circuitry 1320 can include elements of a protocol stack, such as elements of an Evolved Universal Terrestrial Radio Access Network (EUTRAN) protocol including, for example, the following: entity (PHY), media access Control (MAC), Radio Link Control (RLC), Packet Data Aggregation Protocol (PDCP), and/or Radio Resource Control (RRC) elements. A central processing unit (CPU) 1325 of the baseband circuit 1320 can be configured to operate elements of a protocol stack for signaling PHY, MAC, RLC, PDCP, and/or RRC layers. In some embodiments, the baseband circuit can include one or more audio digital signal processors (DSPs) 1326. The audio DSP 1326 can include elements for compression/decompression and echo cancellation, and can include other suitable processing elements in other embodiments.

The baseband circuit 1320 can further include a memory/storage 1327. Memory/storage 1327 can be used to load and store data and/or instructions for operations performed by the processor of baseband circuit 1320. The memory/storage for one embodiment may comprise any combination of suitable electrical memory and/or non-electrical memory. The memory/storage 1327 can include any combination of memory/storage of various levels including, but not limited to, read only memory (ROM) with embedded software instructions (eg, firmware), random access memory Body (for example, dynamic random access memory (DRAM)), cache memory, buffer, and the like. The memory/storage 1327 can be used in a variety of processors or dedicated to a particular processor.

The components of the baseband circuit can be suitably combined in a single wafer, in a single wafer set, or in some embodiments on the same circuit board. In some embodiments, some or all of the constituent components of baseband circuit 1320 and application circuitry 1310 can be implemented together on, for example, a system single chip (SOC).

In some embodiments, baseband circuitry 1320 can provide communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit 1320 can support an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area network (WMAN), wireless local area network (WLAN), Wireless Personal Area Network (WPAN) communication. Embodiments of baseband circuitry 1320 that are configured to support radio communication for more than one wireless protocol may be referred to as multi-mode baseband circuitry.

The RF circuit 1330 can communicate with the wireless network through the non-solid media using modulated electromagnetic radiation. In various embodiments, RF circuitry 1330 can include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. The RF circuit 1330 can include a receive signal path that can include circuitry to downconvert the RF signal received from the FEM circuit 1340 and provide the baseband signal to the baseband circuit 1320. The RF circuit 1330 can also include a transmit signal path that can include circuitry to upconvert the baseband signal provided by the baseband circuit 1320 and provide the RF output signal to the FEM circuit 1340 for transmission.

In some embodiments, RF circuitry 1330 can include a receive signal path and a transmit signal path. The receive signal path of the RF circuit 1330 may include a mixer circuit 1331, an amplifier circuit 1332, and a filter circuit 1333. The transmission signal path of the RF circuit 1330 may include a filter circuit 1333 and a mixer circuit 1331. The RF circuit 1330 can also include a synthesizer circuit 1334 for synthesizing frequencies for use by the mixer circuit 1331 that receives the signal path and the transmission signal path. In some embodiments, the mixer circuit 1331 that receives the signal path can be configured to downconvert the RF signal received from the FEM circuit 1340 based on the synthesized frequency provided by the synthesizer circuit 1334. The amplifier circuit 1332 can be configured to amplify the downconverted signal, and the filter circuit 1333 can be a low pass filter that is configured to remove an undesirable signal from the downconverted signal to produce an output baseband signal. (LPF) or bandpass filter (BPF). The output baseband signal can be provided to the baseband circuit 1320 for further processing. In some embodiments, the output baseband signal can be a zero frequency baseband signal, but this is not a requirement. In some embodiments, the mixer circuit 1331 that receives the signal path may include a passive mixer, although the scope of the embodiments is not limited in this regard.

In some embodiments, the mixer circuit 1331 of the transmit signal path can be configured to generate an RF output signal for the FEM circuit 1340 based on the synthesized frequency upconverted input baseband signal provided by the synthesizer circuit 1332. . The baseband signal can be provided by the baseband circuit 1320 and can be filtered by the filter circuit 1333. The filter circuit 1333 may include a low pass filter (LPF), but the scope of the embodiments is not limited in this regard.

In some embodiments, the mixer circuit 1331 that receives the signal path and the mixer circuit 1331 that transmits the signal path may include two or more than two mixers, and may be configured to be used for four-phase down-conversion, respectively. Conversion and / or up conversion. In some embodiments, the mixer circuit 1331 that receives the signal path and the mixer circuit 1331 that transmits the signal path may include two or more than two mixers, and may be configured for image rejection (eg, Hartley image suppression). In some embodiments, the mixer circuit 1331 and the mixer circuit 1331 that receive the signal path can be configured for direct down conversion and/or direct up conversion, respectively. In some embodiments, the mixer circuit 1331 that receives the signal path and the mixer circuit 1331 that transmits the signal path can be assembled for superheterodyne operation.

In some embodiments, the output baseband signal and the input baseband signal can be analogous to the baseband signal, although the scope of the embodiments is not limited in this regard. In some alternative embodiments, the output baseband signal and the input baseband signal can be digital baseband signals. In these alternative embodiments, the RF circuit 1330 can include an analog to digital converter (ADC) and a digital to analog converter (DAC) circuit, and the baseband circuit 1320 can include a digital baseband interface to communicate with the RF circuit 1330. .

In some dual mode embodiments, separate radio IC circuits may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this regard.

In some embodiments, the synthesizer circuit 1334 can be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect, since other types of frequency synthesizers are available. As appropriate. For example, synthesizer circuit 1334 can be a delta-delta synthesizer, a frequency multiplier, or a synthesizer that includes a phase locked loop with a frequency divider.

Synthesizer circuit 1334 can be configured to synthesize the output frequency for use by mixer circuit 1331 of RF circuit 1330 based on the frequency input and the divider control input. In some embodiments, synthesizer circuit 1334 can be a fractional rate N/N+1 synthesizer.

In some embodiments, the frequency input can be provided by a voltage controlled oscillator (VCO), but this is not a requirement. The divider control input can be provided by the baseband circuit 1320 or the application slave processor 1310 depending on the desired output frequency. In some embodiments, the divider control input (eg, N) can be determined based on a channel self- lookup table indicated by the application processor 1310.

The synthesizer circuit 1334 of the RF circuit 1330 can include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider can be a dual modulus divider (DMD) and the phase accumulator can be a digital phase accumulator (DPA). In some embodiments, the DMD can be configured to divide the input signal by N or N+1 (eg, based on a carry output) to provide a division ratio. In some example embodiments, the DLL may include a set of cascaded tunable delay elements, phase detectors, charge pumps, and D-type flip-flops. In such embodiments, the delay elements can be assembled to divide the VCO period into Nd equal phase packets, where Nd is the number of delay elements in the delay line. In this way, the DLL provides a negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

In some embodiments, synthesizer circuit 1334 can be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency can be a multiple of a carrier frequency (eg, twice the carrier frequency, four times the carrier) The frequency is combined with the quadrature generator and the divider circuit to produce a plurality of signals having a plurality of different phases relative to each other at a carrier frequency. In some embodiments, the output frequency can be the LO frequency (fLO). In some embodiments, RF circuit 1330 can include an IQ/polarity converter.

FEM circuit 1340 can include a receive signal path, which can include being configured to operate on an RF signal received from one or more antennas 1350, amplify the received signal, and provide an amplified version of the received signal to RF circuit 1330 for use in Further processing of the circuit. The FEM circuit 1340 can also include a transmit signal path that can include circuitry that is assembled to amplify the signal provided by the RF circuit 1330 for transmission for transmission by one or more of the one or more antennas 1350.

In some embodiments, FEM circuit 1340 can include a TX/RX switch to switch between a transmission mode and a receive mode operation. The FEM circuit can include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit can include a low noise amplifier (LNA) to amplify the received RF signal and provide an amplified received RF signal as an output (eg, to RF circuit 1330). The transmit signal path of FEM circuit 1340 can include a power amplifier (PA) to amplify the input RF signal (eg, provided by RF circuitry 1330), and one or more filters to generate for subsequent transmission (eg, by one or more RF signal of one or more of antennas 1350.

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

In some embodiments where the electronic device 1300 is a base station such as an eNB, an implementation base station, incorporated into a base station, or otherwise implemented in a base station, the baseband circuit 1320 can be used to identify the radio access network based on information from the communication. The first association of the first local component of the road with the second remote component of the RAN. The first association may correspond to a network segmentation. The baseband circuit 1320 can be configured to identify a second association of the first local component of the RAN with a third component of the RAN of the second component different from the RAN based on information of the same or different communications of the at least one communication, the second association corresponding to Network segmentation. The second association may be based on at least one of a traffic type, a traffic load, or a quality of service (QoS) requirement. The RF circuit 1330 can be used to receive at least one communication from a network virtualization component and/or a software defined network.

In some embodiments in which the electronic device 1300 is a UE, implements a UE, is incorporated into a UE, or otherwise implements a UE, the RF circuit 1330 can be configured to receive at least one of a network virtualization component and/or a software defined network. communication. The baseband circuit 1320 can be configured to identify a first association of the first local component of the radio access network with the second remote component of the RAN based on information from the communication. The first association may correspond to a network segmentation. The baseband circuit 1320 can be configured to identify a second association of the first local component of the RAN with a third component of the RAN that is different from the second component of the RAN based on information from the communication. The second association may correspond to a network segmentation. The second association may be based on at least one of a traffic type, a traffic load, or a quality of service (QoS) requirement.

As described herein, the terms mobile network, wireless network, and wireless communication network discuss and describe the same network type.

In some embodiments, the electronic device of Figure 13 can be used to perform one or more of the procedures, techniques, and/or methods, or portions thereof, as described herein. One such procedure is depicted in Figure 14, for example, for a split-based operation in a 5G network segmented by an end-to-end network. For example, the program can include identifying a first association of a first local component of the radio access network with a second remote component of the RAN, the first association corresponding to network segmentation. The program can further include identifying a second association of the first local component of the RAN with a third component of the RAN that is different from the second component of the RAN, the second association corresponding to network segmentation. In an example, the second association can be based on at least one of a traffic type, a traffic load, or a quality of service (QoS) requirement. Another such procedure is depicted in FIG. 15, for example, a method of operating a UE for a split-based operation in a 5G network segmented by a peer-to-peer network.

For example, the program can include identifying, at the UE, a first association of a first local component of the radio access network with a second remote component of the RAN, the first association corresponding to network segmentation. The program can further include identifying, at the UE, a second association of the first local component of the RAN with a third component of the RAN that is different from the second component of the RAN, the second association corresponding to network segmentation. In an example, the second association can be based on at least one of a traffic type, a traffic load, or a quality of service (QoS) requirement.

15 shows a second example method 1500 for wireless communication of a fifth generation (5G) system, such as a wireless network. The method includes identifying, at a UE, a first association of a first local component of a radio access network with a second remote component of a RAN, the first association corresponding to a network segmentation 1510, and the identifying the RAN at the UE A second association of a local component with a third component of the RAN that is different from the second component of the RAN, the second association corresponding to the network segmentation 1520. The second association may be based on at least one of a traffic type, a traffic load, or a quality of service (QoS) requirement.

16 is a block diagram illustrating components capable of reading instructions from a machine readable or computer readable medium (eg, a machine readable storage medium) and performing any one or more of the methods discussed herein, in accordance with some example embodiments. Figure. In particular, FIG. 16 shows one or more processors (or processor cores) 1610, one or more memory/storage devices 1620, and one or more communication resources 1630 (each of which is via busbar 1640). A graphical representation of a hardware resource 1600 coupled in communication.

A processor 1610 (eg, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor such as a baseband processor (DSP), Special Application Integrated Circuit (ASIC), Radio Frequency Integrated Circuit (RFIC), another processor, or any suitable combination thereof, may include, for example, processor 1612 and processor 1614. The memory/storage device 1620 can include a main memory, a disk storage, or any suitable combination thereof.

Communication resource 1630 can include an interconnection and/or network interface component or other suitable device to communicate with one or more peripheral devices 1604 and/or one or more databases 1606 via network 1608. For example, communication resource 1630 can include wired communication components (eg, for coupling via a universal serial bus (USB)), cellular communication components, near field communication (NFC) components, Bluetooth® components (eg, Bluetooth®) Low energy), Wi-Fi® components and other communication components.

The instructions 1650 can include software, programs, applications, applets, applications, or other means for causing at least one of the processors 1610 to perform any one or more of the methods discussed herein. Executable code. The instructions 1650 may reside wholly or partially within at least one of the processor 1610 (eg, the processor's cache memory), the memory/storage device 1620, or any suitable combination thereof. In addition, any portion of the instructions 1650 can be transferred from the peripheral device 1604 and/or any combination of the databases 1606 to the hardware resource 1600. Thus, the memory, memory/storage 1620, peripheral device 1604, and database 1606 of the processor 1610 are examples of computer readable and machine readable media.

Other methods of wireless communication are also disclosed, for example, as discussed above with reference to Figures 8-12.

Embodiments may be implemented in accordance with any of the following examples that are common and employed in any and all permutations:

14 shows a first example method 1400 for wireless communication of a fifth generation (5G) system, such as a wireless network. Example 1 can include a method for wireless communication of a fifth generation (5G) system, such as a wireless network, comprising: identifying a first local component of a radio access network (RAN) and a second far of the RAN a first association of the end component, the first association corresponding to the network segmentation 1420; and a second association identifying the first local component of the RAN with a third component of the RAN different from the second component of the RAN, the second association corresponding to The network is segmented; wherein the second relationship is based on at least one of a traffic type, a traffic load, or a quality of service (QoS) requirement.

Example 2 can include the example of Example 1 or some other examples herein, further comprising: identifying an association of control plane shards for network segmentation; and identifying user plane severities in multiple user plane shards Control plane splitting association.

Example 3 can include the example of Example 1 or some other example herein, further comprising: identifying an association of control plane shards of network segmentation; and identifying an association of a single user plane shard to a control plane shard.

Example 4 can include the example of Example 1 or some other example herein, further comprising: identifying an association of a common control plane segmentation of the network segmentation; and identifying user plane segments in the plurality of user plane segments Association with the common control plane; and identifying the association between the plurality of segments in a particular control plane and the division of the particular control plane to the common control plane.

Example 5 can include the example of Example 1 or some other example herein, further comprising: determining whether to change a power state of the first component or the second component based on at least one of: associated with network segmentation The traffic load exceeds or falls below the threshold, and the number of UEs operating in the network segmentation exceeds or decreases below the threshold to maintain service continuity of the mobile UE or to meet specific QoS. Requirements (eg, low latency, super reliability, or the like or a combination thereof).

Example 6 can include the instance of Example 5 or some other example herein, further comprising: determining whether to change a power state of the first component or the second component based on the received control signal; wherein the control signal is derived from the UE (and included in the random At least one of an indication of the expected segmentation during the access or a peer base station/access point (BS/AP) (and including a trigger message requesting a change in the split power state at the target BS).

Example 7 can include the instance of Example 5 or some other example herein, further comprising: transmitting a signal to the remote AP/BS or the mobility management entity in response to determining to change the power state of the first component or the second component At least one of the (MME)/network control entities exchanges signals.

Example 8 can include the instance of Example 6 or some other example herein, wherein the control signal is received via the UE interface (eg, the control signal originates from the UE), and the method further includes: in response to receiving the control signal, based on the message The monitoring determines whether to maintain the power state of the first component or the second component.

Example 9 can include the instance of Example 6 or some other example herein, wherein the control signal is received via a UE interface, and the method further comprises: determining whether to maintain the first component or the second based on the QoS criteria in response to receiving the control signal The power state of the component.

Example 10 can include the instance of Example 1 or some other example herein, further comprising: determining whether to change a power state of the first component or the second component based on at least one of: UEs regarding neighbor cell conditions The condition of the traffic load/connection number on the report or network segmentation.

Example 11 can include the instance of Example 5 or 10 or some other example herein, further comprising: in response to determining to change a power state of the first component or the second component, handing over the split-active UE to the phase Neighbor BS.

Example 12 can include the instance of Example 5 or 10 or some other example herein, further comprising: transmitting or receiving system information carrying information about the active segmentation in the BS.

Example 13 may include the example of Example 1 or some other examples herein, further comprising: determining whether to change the first component based on a handshake between BSs of the plurality of central controllers of the plurality of BSs or the plurality of BSs The power state of the second component.

Example 14 can include the example of example 13 or some other example herein, further comprising transmitting or receiving a signaling to or indicating a load condition for each of a plurality of network segments including network segmentation From AP or BS.

15 shows an example 15 of a method 1500 for wireless communication of a fifth generation (5G) system, such as a wireless network. Example 15 can include a method for wireless communication of a fifth generation (5G) system, comprising: identifying, at a UE, a first association of a first local component of a radio access network with a second remote component of a RAN The first association corresponds to the network segmentation 1510; and the second association of the first local component of the RAN with the third component of the RAN different from the second component of the RAN is identified at the UE, the second association corresponding to the network The second contact is based on at least one of the traffic type, traffic load, or quality of service (QoS) requirements 1520.

Example 16 can include the instance of Example 15 or some other example herein, further comprising: determining whether to access the BS based on at least one of: a power state, a link condition, a QoS requirement of the BS that is expected to be segmented Or the traffic load of the neighboring cell.

Example 17 can include the example of Example 15 or some other example herein, further comprising: maintaining a connection to another network segmentation of a different AP or BS that is different from the network segmentation.

Example 18 can include a device (e.g., an electronic device of any network device, including but not limited to an eNB) operable in wireless communication of a fifth generation (5G) system, such as a wireless network, the device The method includes: a radio frequency (RF) circuit for receiving at least one communication originating from a network virtualization component and/or a software-defined network; and a baseband circuit for: identifying radio access based on information from the communication a first association between a first local component of the network (RAN) and a second remote component of the RAN, the first association corresponding to network segmentation; and the identification of the RAN based on information of the same or different communications of the at least one communication a second association of the first local component with a third component of the RAN different from the second component of the RAN, the second association corresponding to network segmentation; wherein the second association is based on traffic type, traffic load or quality of service At least one of (QoS) requirements.

Example 19 can include the example of Example 18 or some other example herein, wherein the baseband circuit is configured to: identify an association of control plane shards of network segmentation; and identify user planes in a plurality of user plane shards The association between the segmentation and the control plane segmentation.

Example 20 may include the example of Example 18 or some other examples herein, wherein the baseband circuit is configured to: identify associations of control plane shards of network segmentation; and identify single user plane shards and control plane severities The association.

Example 21 can include the example of Example 18 or some other example herein, wherein the baseband circuit is configured to: identify an association of a common control plane segmentation of the network segmentation; and identify users in the plurality of user plane segments The association between the plane segmentation and the common control plane segmentation; and the identification of the segmentation of a plurality of segments in a particular control plane is associated with a common control plane segmentation.

Example 22 can include the instance of Example 18 or some other example herein, wherein the baseband circuit is configured to: determine whether to change a power state of the first component or the second component based on at least one of: The associated traffic load exceeds or falls below the threshold, and the number of UEs operating in the network segmentation exceeds or decreases below the threshold to maintain service continuity of the mobile UE or Meet specific QoS requirements (eg, low latency, super reliability, or the like or a combination thereof).

Example 23 can include the example of example 22 or some other example herein, wherein the baseband circuit is configured to: determine whether to change a power state of the first component or the second component based on a control signal received by the RF circuit; wherein the control signal is derived At least one of the UE (and including an indication of the expected segmentation during random access) or a peer BS/AP (and including a trigger message requesting a change in the split power state at the target BS).

Example 24 can include the example of example 22 or some other example herein, wherein the baseband circuit is operative to transmit a signal to the remote AP/BS or MME in response to determining to change the power state of the first component or the second component / at least one of the network control entities exchanges the message.

Example 25 may include the example of example 23 or some other examples herein, wherein the control signal is received via the UE interface, and wherein the baseband circuit is configured to: determine whether to maintain the first component based on the traffic monitoring in response to receiving the control signal Or the power state of the second component.

Example 26 may include the example of example 23 or some other examples herein, wherein the control signal is received via a UE interface, and wherein the baseband circuit is responsive to receiving the control signal, determining whether to maintain the first component or based on QoS criteria The power state of the second component.

Example 27 can include the instance of Example 18 or some other example herein, wherein the baseband circuit is configured to: determine whether to change a power state of the first component or the second component based on at least one of: about a neighboring cell The condition of the UE report or the number of traffic load/connections on the network segmentation.

The example 28 may include the example of the example 22 or 27 or some other examples herein, wherein the baseband circuit is configured to: in response to determining to change the power state of the first component or the second component, to split the active UE Delivered to the neighboring BS.

Example 29 may include the example of Example 22 or 27 or some other example herein, wherein the baseband circuit causes the RF circuit to transmit system information or RF circuitry carrying information about the active segmentation in the BS. System information of the information split in the role.

The example 30 may include the example of the embodiment 18 or some other examples herein, wherein the baseband circuit is configured to: determine whether to change the number based on a handshake between the BSs of the plurality of central controllers of the plurality of BSs or the plurality of BSs The power state of a component or a second component.

Example 31 can include an instance of instance 30 or some other example herein, wherein the baseband circuit causes the RF circuit to transmit a signal indicating a load condition for each of a plurality of network segments including network segmentation to Or receiving a signal from the AP or BS, or the RF circuit, indicating that the load condition for each of the plurality of network segments including the network segmentation is to or from the AP or BS.

Example 32 can include a device (eg, an electronic device operable in a user device in a wireless communication of a fifth generation (5G) system), the device comprising: a radio frequency (RF) circuit for self-originating the network At least one communication receiving component of the virtualization component and/or the software-defined network; and a baseband circuit for: identifying the first local component of the radio access network (RAN) and the RAN based on the information from the communication a first association of the two remote components, the first association corresponding to the network segmentation; and based on the information from the communication, identifying the first local component of the RAN and the third component of the RAN different from the second component of the RAN The second association, the second association corresponds to network segmentation; wherein the second association is based on at least one of a traffic type, a traffic load, or a quality of service (QoS) requirement.

Example 33 may include the instance of Example 32 or some other example herein, wherein the baseband circuit is configured to: determine whether to access the BS based on at least one of: a power state, a link condition of the BS that is expected to be segmented , QoS requirements or traffic load of neighboring cells.

Example 34 may include an instance of Example 32 or some other example herein, wherein the baseband circuit is configured to simultaneously maintain network segmentation and another network segmentation of different APs or BSs different from network segmentation connection.

Example 35 can include an instance of any of Examples 1 to 34, or some other example herein, wherein the network segmentation includes any one or more of: an entity for or dedicated to a single type of communication Logical partitioning of the radio access network infrastructure; logical partitioning of the physical radio access network infrastructure for or dedicated to communications for specific usage communications; any other logic independent of the physical radio access network infrastructure The operation of the partition and the independent operation of the traffic flow and the logical partitioning of the physical radio access network infrastructure of the traffic flow. An advantage of this example and other examples described herein is that a more efficient wireless network is because, for example, it allows a given amount of (eg, a single) physical radio access network infrastructure to be used by multiple usage conditions, This results in less hardware/base than what would otherwise be used (eg, twice or more hardware (for example) to provide a separate physical radio access network infrastructure for each use case) structure.

Example 36 can include an instance of any of Examples 1 through 35 or some other example herein, wherein the network is split into end-to-end network segments, where the peer-to-peer is included for use in providing network segmentation The logical separation of both the physical radio access network infrastructure and the physical core network infrastructure.

Example 37 can include an instance of any of Examples 1 to 36 or some other example herein, wherein communication of a particular use condition includes any easily definable/differentiated type of communication that can be made via a wireless network.

Example 38 may include an instance of any of Examples 1 to 37 or some other example herein, wherein the network segmentation comprises a logically separated radio access network carried on a shared physical radio access network (RAN) .

Example 39 can include an instance of any of Examples 1 to 38 or some other example herein, wherein the network segmentation comprises vertical segmentation according to usage status and/or segmentation according to a level of shared resources, wherein the shared resource A resource shared between a shared layer of a radio access network or a selected one of entities in different layers of the wireless network.

Example 40 can include a Radio Access Network (RAN) control entity that includes circuitry to logically separate a physical infrastructure of a radio access network into two or more than two logically separated a virtual radio access network, wherein the logically separated virtual radio access network comprises a radio access network optimized for a predefined communication type, and wherein the logically separated virtual access network comprises independent Independent operation and traffic flow of any other logically separated virtual access network operations and traffic flows; each of two or more logically separated virtual access networks is based on At least one parameter associated with a predefined communication type for each of two or more logically separated virtual access networks is dynamically assembled; wherein at least one of the predefined communication types is associated One parameter is at least one of the following: a traffic type of a predefined communication type, a traffic load of a predefined communication type, and a service quality requirement of a predefined communication type.

Example 41 may include an instance of instance 40 or some other example herein in which the physical infrastructure of the radio access network is logically separated into two or more than two logically separated virtual radio access networks including on Or start a logically separate virtual access network.

Example 42 may include an instance of instance 40 or 41 or some other example herein, wherein turning on or initiating a logically separate virtual access network includes any one or more of the following: when served by a wireless network When the device is triggered, the device transmits an indication of the expected logically separated virtual access network to be used in the initial random access (RA); when triggered by the peer access point (AP) or the base station (BS), the peer An access point (AP) or a base station (BS) transmits a trigger message to a target access point (AP) or a base station (BS), the trigger message including a request to enable or start a virtual access network designated to be logically separated; A handshake exchange between an access point (AP) or a base station (BS) and a mobility management entity (MME) or a network control entity associated with the physical radio access network to determine whether to use, enable or initiate The logically separated virtual access network's composition parameters.

Example 43 may include the examples of Examples 40-42 or some other examples herein, wherein the traffic load of the predefined communication type includes any one or more of the following: an access point (AP) or a base station ( Predefined traffic threshold level at BS); exceeds the number of predefined active devices operating on the existing logically separated virtual access network

Example 44 may include the examples of Examples 40-43 or some other examples herein, wherein the quality of service requirements for the predefined communication types include or are based on any one or more of: maintaining the servo network by the radio access network Service continuity of the mobile device, and wherein the device is in use with a predefined communication type; providing a predetermined maximum latency for a predefined communication type; providing a predetermined minimum communication reliability for a predefined communication type; providing a predefined communication type The minimum data rate is predetermined.

Example 45 can include the examples of Examples 40-44 or some other examples herein, wherein the circuitry is further for: disconnecting or logically separating logically separated virtualities based on at least one other parameter associated with the predefined communication type Accessing the network, wherein at least one other parameter is based on at least one of: an access point (AP) or a base station (BS) at which the traffic level falls below a predefined threshold; The number of active devices on the existing logically separated virtual access network falls below a predefined threshold; data reports on logically separated virtual access networks or neighboring cells, base stations or access points The conditions.

Example 46 can include an instance of example 45 or some other example herein, wherein the data report includes a system information block or portion thereof.

Example 47 can include the examples of Examples 45-46 or some other examples herein, wherein the data report includes a system information block or portion thereof that carries information about the logically separated virtual access networks.

Example 48 can include the examples of Examples 40-47 or some other examples herein, wherein when the logically separated virtual access network is detached or disconnected, the circuitry is further configured to: logically separate the virtual access network Any remaining devices on the way are handed over to a different logically separate virtual access network operating on the same base station or access point; or any device remaining on the logically separated virtual access network is handed over to Another base station or access point that maintains the operation of the same logically separated virtual access network to be disconnected.

Example 49 can include the examples of Examples 40-48 or some other examples herein, wherein the device to be served by the radio access network includes a User Equipment (UE).

Example 50 can include the examples of Examples 40-49 or some other examples herein, wherein the device or UE to be queried determines whether and how to access the logically separated virtual access network based on any one or more of the following: Road: an indication that the selected logically separated virtual access network currently acts on a serving access point (AP) or base station (BS) of the current serving UE; a Serving Access Point (AP) of the UE and the current Serving UE Or the link condition of the radio link between the base stations (BS); the QoS requirement for providing wireless communication to the UE; or the access point of the adjacent access point (AP) or base station (BS) to the current serving UE The traffic load between (AP) or base station (BS).

Example 51 may include the examples of Examples 40 through 50 or some other examples herein in which signaling between a Servo Access Point (AP) or a Base Station (BS) via a servo device or servo device is operable to assist in storing One of the point (AP) or base station (BS) determines whether to agile the logically separated virtual access network open procedure or the logically separated virtual access network disconnect procedure.

Example 52 may include the examples of Examples 40 through 51 or some other examples herein, wherein the signaling includes logically separating each of the roles between the access points (APs) or base stations (BSs) of the server device. Load conditions on the virtual access network to provide separate logically separate virtual access networks.

Example 53 can include the examples of Examples 40-52 or some other examples herein, wherein the device served by the radio access network is operable to maintain a plurality of logically separate virtual access networks and/or to a service device Multiple access points (APs) or base stations (BSs) are connected to provide a logically separate virtual access network.

Example 54 may include the examples of Examples 40-53 or some other examples herein in which the physical infrastructure of the radio access network is logically separated into two or more logically separate virtual access networks including Providing two or more network segmentation, and wherein the control entity provides a control plane and a user plane combination for two or more network segmentation, wherein the control plane and the user plane are combined Included in any of the following: a network for each operating network segmentation splits a particular user plane and a single shared control plane that is used by all operating networks, where the particular network is segmented The control plane and the user plane functions are decoupled from each other; or the network for each operating network segmentation divides a specific user plane and the network divides the specific control plane, wherein the control plane of the specific network segmentation and The user plane functions are coupled to each other; or the network for each operating network segmentation splits the specific control plane and includes the first shared control plane portion; and the second network divides the specific control plane portion for each Network switching control operation of the sub-plane; wherein the specific network control plane and tangential per user plane function from the portion coupled to each other and partially decoupled from each other.

Example 55 can include configured machine executable instructions that, when executed by one or more processors, implement a method in a wireless communication network, the method comprising: logically separating a physical infrastructure of a radio access network Two or more logically separated virtual radio access networks, wherein the logically separated virtual radio access network includes a radio access network optimized for a predefined communication type, and wherein the logic A separate virtual access network includes independent operations and traffic flows independent of any other logically separated virtual access network operations and traffic flows; depending on whether it is to be used for two or more logical places At least one parameter associated with a predefined communication type of each of the separate virtual access networks, dynamically arranging each of two or more logically separate virtual access networks; The at least one parameter associated with the predefined communication type is at least one of: a traffic type of a predefined communication type, a traffic load of a predefined communication type, a predefined News type of quality of service requirements.

Example 56 may include an instance of instance 55 or some other example herein in which the physical infrastructure of the radio access network is logically separated into two or more than two logically separated virtual radio access networks including on A logically separated virtual access network.

Example 57 can include an instance of instance 55 or 56 or some other example herein, wherein opening a logically separate virtual access network includes any one or more of the following: when triggered by a wireless network servo device Transmitting, in initial random access (RA), an indication of an expected logically separated virtual access network to be used; when triggered by a peer access point (AP) or a base station (BS), a message is triggered A peer access point (AP) or a base station (BS) transmits to a target access point (AP) or a base station (BS), the trigger message includes a request to open a virtual access network designated to be logically separated; an access point (AP) or base station (BS) exchanges credits with an active management entity (MME) or a network control entity associated with an entity radio access network to determine logical separation of to-be-used, enabled, or initiated The configuration parameters of the virtual access network.

Example 58 may include the examples of Examples 55-57 or some other examples herein, wherein the traffic load of the predefined communication type includes any one or more of the following: an access point (AP) or a base station ( The predefined traffic threshold level at BS); the number of predefined active devices operating on a virtual access network that is already logically separated.

Example 59 can include the examples of Examples 55-58 or some other examples herein, wherein the quality of service requirements for the predefined communication types include or are based on any one or more of: maintaining the servo network access by the radio Service continuity of the mobile device, and wherein the device is in use with a predefined communication type; providing a predetermined maximum latency for a predefined communication type; providing a predetermined minimum communication reliability for a predefined communication type; providing a predefined communication type The minimum data rate is predetermined.

Example 60 can include the examples of Examples 55-59 or some other examples herein, further comprising: disconnecting or logically separating logically separate virtual access networks based on at least one other parameter associated with a predefined communication type The at least one other parameter is based on at least one of: the access level (AP) or the base station (BS) at which the traffic level falls below a predefined threshold; operating in the existing logic The number of active devices on the geographically separated virtual access network is reduced below a predefined threshold; the data report for the logically separated virtual access network or the condition of the neighboring cell, base station or access point.

Example 61 can include an instance of instance 60 or some other example herein, wherein the data report includes a system information block or portion thereof.

The instance 62 can include an instance of the instance 60 or 61 or some other example herein, wherein the data report includes a system information block or portion thereof that carries information about the virtual access network that is logically separated.

Example 63 can include the examples of Examples 55-62 or some other examples herein, wherein when the logically separated virtual access network is detached or disconnected, the method further includes: logically separating the virtual access network Any remaining devices on the road are handed over to a different logically separate virtual access network operating on the same or different base stations or access points; or any device remaining on the logically separated virtual access network Another base station or access point that is operated to maintain the operation of the same logically separated virtual access network that is to be disconnected at the current base station.

Example 64 can include the examples of Examples 55-63 or some other examples herein, wherein the device to be served by the radio access network includes a User Equipment (UE).

Example 65 can include the examples of Examples 55-64 or some other examples herein, further comprising the device or UE to be queried to determine whether and how to access the logically separated virtual reality based on any one or more of the following: Access network: the selected logically separated virtual access network currently acts on the servo access point (AP) or base station (BS) of the current serving UE; the servo access of the UE and the current serving UE Link conditions of the wireless link between the point (AP) or the base station (BS); QoS requirements for providing wireless communication to the UE; or neighboring access point (AP) or base station (BS) to the current serving UE The traffic load between the access point (AP) or the base station (BS).

Example 66 can include the examples of Examples 55-65 or some other examples herein in which a signaling between a Servo Access Point (AP) or a Base Station (BS) of a servo device or servo device is operable to assist in storing One of the point (AP) or base station (BS) determines whether to agile the logically separated virtual access network open procedure or the logically separated virtual access network disconnect procedure.

Example 67 can include the examples of Examples 55-66 or some other examples herein, wherein the signaling includes logically separating each of the functions between the access points (APs) or base stations (BSs) of the server device. Load conditions on the virtual access network to provide separate logically separate virtual access networks.

Example 68 can include the examples of Examples 55-67 or some other examples herein, further comprising maintaining a plurality of logically separated virtual access networks and/or to a plurality of servo devices by means of a radio access network servo Connected by an access point (AP) or a base station (BS) to provide a logically separate virtual access network.

Example 69 can include the examples of Examples 55-68 or some other examples herein, wherein the physical infrastructure of the radio access network is logically separated into two or more logically separate virtual access networks including Providing two or more network segmentation, and the method further comprises providing a control plane and a user plane combination for two or more network segmentation, wherein the control plane and the user plane group The configuration includes any one of the following: a network for each operating network segmentation splits a specific user plane and a single shared control plane that is used by all operating networks, where the specific network is segmented The control plane and the user plane function are decoupled from each other; or the network for each operating network segmentation divides the specific user plane and the network divides the specific control plane, wherein the control plane of the specific network segmentation And the user plane functions are coupled to each other; or the network for each operating network segmentation splits the specific control plane and includes the first shared control plane portion; and the second network splits the specific control plane portion for A network operation control sliced plane; wherein the specific network control plane and tangential per user plane function from the portion coupled to each other and partially decoupled from each other.

Example 70 can include a means for triggering network segmentation in a radio access network, comprising: circuitry for triggering the opening or disconnection of a network segmentation based on any one or more of: radio The traffic load of the network-switched traffic load or the radio access network is split across the threshold traffic load, where the threshold traffic load is in the radio access network (RAN). The traffic load at the access point (AP) or base station (BS); and/or the active user equipment (UE) operating on the radio access network or on the network segmentation of the radio access network The number of thresholds that exceed the number of thresholds for active UEs; the service continuity requirements of mobile UEs based on maintaining network segmentation for use on a radio access network or for use on a radio access network; Quality of Service (QoS) requirements for devices on the radio access network or on the network segmentation of the radio access network, where QoS requirements include, but are not limited to, radio access networks or network segmentation The amount of latency of the wireless connection, Or the level of reliability of a wireless access network or network segmented wireless connection.

Advantages of example 70 or other examples described herein may include improved radio access network performance, efficiency, reliability, service and quality of service for all devices operating across the RAN and operating within every RAN of the RAN maintain.

Example 71 can include an instance of instance 70 or some other example herein in which network segmentation is enabled at an access point (AP) or base station (BS), and wherein the triggering for enabling network segmentation includes: Receiving a UE trigger signal from the UE, the UE trigger signal including an indication for an expected network segmentation used by the UE, where the UE trigger signal is included in the random access of the UE, or by a target access point (AP) Or the target base station (BS) receives a trigger signal from a peer access point (AP) or a peer base station (BS), the trigger signal includes enabling network segmentation at a target access point (AP) or a base station (BS) Request.

Example 72 may include an instance of instance 70 or 71 or some other example herein, wherein turning on network segmentation is included at an access point (AP) or base station (BS) with an mobility management entity (MME) or network control Exchange messages between entities to enable network segmentation.

Example 73 may include the examples of examples 70-72 or some other examples herein in which the access point (AP) or base station (BS) receives sufficient amount in the traffic load actuated network splitting turn-on. When the traffic is made to make the network segmentation open, the access point (AP) or the base station (BS) starts the network segmentation, wherein a sufficient amount of traffic is a predetermined value.

Example 74 may include instances of instances 70-73 or some other examples herein, wherein if the amount of traffic is insufficient, the access point (AP) or base station (BS) rejects random access (RA) requests from the requesting entity. .

Example 75 may include instances of instances 70-74 or some other examples herein in which, in QoS-enabled network segmentation turn-on, only when an access point (AP) or base station (BS) receives meets predefined criteria When the QoS service requests, the access point (AP) or the base station (BS) starts network segmentation.

Example 76 can include a base station (BS) device operable in a wireless communication network, the device comprising: radio frequency (RF) circuitry for receiving at least one communication originating from a wireless network device or transmitting at least one communication to a wireless network device; and a radio access network control entity according to any of the examples 40 to 54; or a device for performing a component or module of any of the examples 55 to 69; or an instance 70 A device to any of 75; or some other example herein.

Example 77 can include a user equipment (UE) device operable in a wireless communication network, the device comprising: radio frequency (RF) circuitry for receiving or transmitting at least one communication to another device in the wireless communication network; And a radio access network control entity according to any of the examples 40 to 54; or a device comprising the means or module for performing any of the examples 55 to 69; or any of the examples 70 to 75 One device; or some other example herein.

Example 78 can include an apparatus comprising one of the methods described or associated with any one of Examples 1 to 17, 35 to 39, 55 to 69, or any other method or program described herein or A component of multiple features.

Example 79 can include one or more non-transitory computer readable media containing instructions that, when executed by one or more processors of an electronic device, cause the electronic device to: perform or be described in relation to Examples 1 through 17, 35 One or more elements of the method of any one of 39, 55 to 69, or any other method or procedure described herein, or a device as claimed in any one of claims 18 to 54 or 70 to 75 Or the functionality of the device.

Example 80 can include an apparatus comprising one or both of the methods described or associated with any of Examples 1 to 17, 35 to 39, 55 to 69, or any other method or program described herein. The logic, modules, components, and/or circuits of multiple elements.

Example 81 can include an apparatus comprising: one or more processors and one or more computer readable media containing instructions that, when executed by one or more processors, cause one or more processors to execute A method, technique or program as described or associated with any one of Examples 1 to 17, 35 to 39, 55 to 69, or any other method or program described herein.

Example 82 can include a method of communicating in a wireless network as shown and described herein.

Example 83 can include a system for providing wireless communication as shown and described herein.

Example 84 can include an apparatus for providing wireless communication as shown and described herein.

Example 85 can include a device that implements network segmentation in a radio access network, including any combination of the devices, entities, or methods described herein or portions of the devices, entities, or methods described herein.

Example 86 can include a radio access network that includes any combination of the devices, entities, or methods described herein or portions of the devices, entities, or methods described herein.

Example 87 can include a device for use in a radio access network, including any combination of the devices, entities, or methods described herein or portions of the devices, entities, or methods described herein.

Examples of usage/types of communications may include: Wireless/Mobile Broadband (MBB) communications; Extreme Mobile Broadband (E-MBB) communications; such as industry-controlled communications, machine-to-machine communications (MTC/MTC1), instant use; Usage status, such as Internet of Things (IoT) sensor communication or large-scale machine-to-machine communication (M-MTC/MTC2); ultra-reliable machine-to-machine communication (U-MTC); mobile edge cloud, such as cache communication; vehicle For vehicle (V2V) communication; vehicle-to-infrastructure (V2I) communication; vehicle-to-anything communication (V2X). That is, the present invention is directed to providing network segmentation based on any easily definable/differentiated type of communication that can be performed over a wireless network.

In some examples, the RAN control entity is distributed across portions of the RAN. In some examples, a portion of the RAN is a base station (eg, an eNB) of the RAN, and in other examples, a portion of the RAN may be a UE, or a Servo Wireless Network/RAN or any other device that is served by the wireless network/RAN. , or (or servo) the formation of a wireless network/RAN, such as an Actor Management Engine (MME), a Baseband Unit (BBU), a Remote Radio Head (RRH), or the like. In some examples, if the RAN control entity is physically distributed, the RAN control entity may co-locate with the jumbo BS and manage only the segmentation portion under the coverage of the jumbo BS. In some examples, if the RAN Control Entity is in a central location, the RAN Control Entity may manage the segmentation portion across a plurality of BSs under the coverage of the RAN Control Entity. The RAN Control Entity may include controlling at least a portion of the RAN's allocation or devices, resources, such as computing resources at/in the device in the wireless network or available to the device, in accordance with one or more horizontal or vertical segmentation needs.

As described herein, where an example or claim recites, for example, an RF circuit to form a larger entity (e.g., a base station) within a wireless network, this is also intended to be encompassed and not included (for example) for ( Or provide an embodiment or alternative embodiment of an RF circuit of a distributed form entity in accordance with the present invention. This may be applicable, for example, when an entity forms part of a cloud RAN, where the radio portion (eg, RRH) does not have the same entity as at least a substantial portion of the control functions (entities, modules, etc.) (eg, BBUs) Co-located / within the entity. Thus, no embodiment is intended to be limited to only those embodiments that have the RF portion to transmit or receive messages to or from the wireless network. For example, some implementations may be part of a forward transmission capability, which may be a connection from a centralized or more centralized baseband function (eg, a BBU) to a radio front end (eg, RRH).

As used herein, any reference to a computer program product or computer readable medium may include reference to both temporary (eg, physical media) and non-transitory forms (eg, signals or their data structures).

The various examples disclosed herein may provide a number of advantages, such as, but not limited to, providing a full set of servo devices for any given amount of core network and/or RAN resources (eg, computing, radio, etc.) Full coverage; less control of transmission delays and transmission of additional load among transmission points; provision of improved coverage and simultaneous reduction of control signaling exchanges in network nodes (company transmission points); more effective (overall or Most of it) wireless networks, because, for example, they allow a given amount of (eg, a single) physical radio access network infrastructure to be used by multiple usage conditions, thereby compared to what would otherwise be used (eg, , twice or more hardware (for example, to provide a separate physical radio access network infrastructure for each use case) brings less hardware/infrastructure; for every traversal operation across the RAN and RAN All of the devices are generally maintained/maintained with improved radio access network performance, efficiency, reliability, service and service quality.

As described herein, the opening, starting or logical separation of network segments, or the like, may be equivalent to each other, and the terms are used interchangeably. Similarly, disconnection, deactivation, or logical de-separation of network segments, or the like, may be equivalent to each other, and the terms are used interchangeably. Network segmentation may also refer to logically separated (separated, segmented, etc.) radio network access or reference logically separated (separated, partitioned, etc.) radio network access portions. A device that services a physical radio access network infrastructure or network segmentation or that is segmented by the infrastructure or network may include a UE, although any and all other forms of devices that may be servoed may also be used herein. The reference of the UE is interchanged. The device can be referred to as a wireless network device. However, depending on the context of use, a wireless network device as used herein may also reference a servo entity, such as a base station, MME, BBU, RRH, and the like. Operationally, in terms of the network segmentation revealed, the access point and base station can be considered similar in use or deployment.

Specific examples have been used to explain the disclosed methods and functions (and functional units for performing their functions) as described herein, although the invention is not limited thereto. For example, embodiments of the invention are not limited to any particular example, such as: in the case of a particular vertical market relative to the figures, this is merely an example and may alternatively use any vertical market; the particularity of the segmentation is disclosed relative to the figure In some cases, any part of the segmentation may alternatively be used; in the case where the RAN has been revealed to have a certain size, type or number of cuts (horizontal or vertical) relative to the figure, any size, type or cut may alternatively be used Sub-number; in the case where the segmentation or segmentation has been revealed as having a certain size, type or number (in horizontal or vertical) relative to the figure, any size, type or number of segments or segments may alternatively be used. section. Moreover, in the foregoing, although the numbering scheme of the segmentation has been applied starting from 1, other numbering schemes may be implemented, for example, the numbering may alternatively start from 0, so that the segmentation #1 may be the segmentation #0 and its Similar. Thus, a particular number is not limited, except by an exemplary relationship between the illustrated distinctions (by different numbers) or by numbered segments (by consecutively numbering the same numbered segmentation) Outside the subsection).

As used herein, the term "circuitry" may mean the following, part of or include: special application integrated circuits (ASICs), electronic circuits, processors (shared, dedicated, or group). And/or executing one or more software or firmware files (shared, dedicated or group), combinational logic circuits and/or other suitable hardware or software components, including one or more of the described functionality Virtual machines. In some embodiments, the circuitry can be implemented in one or more software or firmware modules, or the functions associated with the circuitry can be implemented by one or more software or firmware modules. In some embodiments, the circuitry can include logic that is at least partially hardware operable. In some embodiments, the processing/execution may be distributed rather than centralized processing/execution.

As used herein, any reference to a (RAN) architecture may include specific procedures, techniques, technologies, implementation details, wireless networks (or similar network connections) that may be defined or considered to be in any form. Anything in the system entity) that is an improvement or type of operation (specifically in the RAN). The architecture can typically be introduced, maintained, and updated in standard documents that use separate wireless networking technologies, such as the Third Generation Partnership Project (3GPP) standards and the like.

It will be appreciated that any of the disclosed methods (or corresponding devices, programs, data carriers, etc.) can be performed by a host or client depending on the particular implementation (ie, the disclosed method/device is in the form of a communication, and thus can be "Viewing angles" are carried out, that is, in a manner corresponding to each other). In addition, it will be understood that the terms "receiving" and "transmission" encompass "input" and "output" and are not limited to the RF context for transmitting and receiving radio waves. Thus, for example, a wafer or other device or component for implementing an embodiment can produce material for output to another wafer, device or component, or have input data from another wafer, device or component, and This output or input may be referred to as "transmit" and "receive", including gerund form, ie "transmission" and "receiving" and this "transmission" within the RF context. (transmitting) and "receiving".

As used in this manual, any statement in the form of "at least one of A, B or C" and the phrase "at least one of A, B and C" are used in conjunction with the conjunction "or" and "reverse". The terms "and" such that they include any and all combinations and combinations of A, B, and C, that is, A, B, C, A and B in any order, and A in any order. C, B and C in any order and A, B, C in any order. There may be more or less than three features in such an illustration.

In the scope of the patent application, any reference mark placed between parentheses shall not be considered as limiting the scope of the patent application. The word "comprising" does not exclude the presence of other elements or steps that are different from the elements or steps recited in the claims. Moreover, as used herein, the terms "a" or "an" are defined as one or more than one. In addition, the use of an introductory phrase such as "at least one" and "one or more" in the scope of the patent application should not be construed as implying that the indefinite article "a" or "an" A claim component limits any particular claim containing the claimed component to an invention containing only one such component, even if the same claim includes the introductory phrase "one or more" or "at least one" and such as "a" (a) or "an" indefinite article. The same is true for the use of definite articles. Terms such as "first" and "second" are used to arbitrarily distinguish the elements described by the term unless otherwise stated. Therefore, such terms are not necessarily intended to indicate the time or other prioritization of such elements. The mere fact that certain measures are recited in the scope of the various claims are not intended to be

The features of the foregoing embodiments and examples and the scope of the following claims may be combined in any suitable configuration, unless otherwise explicitly stated as incompatible or physical or otherwise in the scope of the embodiments, examples, or claims. Especially in the case where there is a beneficial effect. This is not limited to any given benefit, and may alternatively result from "after the fact" benefits. That is, the combination of features is not limited to the form described, the form (eg, numbering) of the specific examples, embodiments, or sub-claims. In addition, the phrase "in one embodiment", "in accordance with the embodiments" and the like, is merely in the form of the wording and should not be construed as limiting the following features to all of the same or similar wording. A separate embodiment of the situation. That is, references to "a", "an" or "an" embodiment may be a reference to any one or more and/or all embodiments or combinations thereof. Also, similarly, references to the "this" embodiment are not limited to the immediately preceding embodiments.

In the foregoing, references to "layers" may be references to predefined (or definable) portions of the infrastructure, whereas references to "layers" may refer to operating networks on/in the network infrastructure. Reference to the agreement layer or part thereof. As used herein, vertical slicing can be referenced to or related to vertical market segments. As used herein, any machine-executable instructions may perform the disclosed methods and may thus be used synonymously with the terminology.

The above description of one or more embodiments provides a description and description, and is not intended to limit the scope of the invention. Modifications and variations are possible in the course of the teachings of the invention.

100‧‧‧Wireless network
110‧‧‧Vertical Segmentation #1/Mobile Broadband (MBB)
112, 122, 132, 142‧‧‧ Mega network layer
114, 124, 134, 144‧‧‧ micro network layer
116, 126, 136, 146‧‧‧D2D network layer part
118, 128, 138, 148‧‧‧PAN network layer
120‧‧‧Vertical cut score #2/Vehicle type communication (V2X)
130‧‧‧Vertical cut score #3/First machine type communication (MTC-1)
140‧‧‧Vertical cut-off #4/Second machine type communication (MTC-2)
150‧‧‧ core network layer part
160‧‧‧ Radio Access Network (RAN) layer section
170‧‧‧Device layer
180‧‧‧Personal/wearable layer
190‧‧‧First level network segmentation
195‧‧‧Second level network segmentation
200‧‧‧ second view
210‧‧‧Split #1/mega network layer
220‧‧‧Split #2/micro network layer
230‧‧‧Split #3/Device-to-Device (D2D) network layer
240‧‧‧Personal Area Network (PAN) network layer
300‧‧‧ graphics
302‧‧‧Network class
304‧‧‧ Radio resources
306‧‧‧Vertical cut
308‧‧‧ horizontal cut
410‧‧‧Base station section
410'‧‧‧Base Station
412‧‧‧Upstream/core network side communication function
412'~434'‧‧‧Project
414‧‧‧Base station computing function
414', 424' ‧ ‧ processing resources
416‧‧‧Downstream/wireless/device side communication function
420‧‧‧ portable part
420'‧‧‧ portable device
422‧‧‧Hive wireless communication link
424‧‧‧ Local computing function
426‧‧‧ downstream communication link
430‧‧‧ wearable part
430'‧‧‧ wearable device
432‧‧‧Single upstream communication link
434‧‧‧Restricted local processing resource function
500‧‧‧C/U plane implementation
510‧‧‧All-in-one shared c-plane
520, 620‧‧‧ cut the u plane of #1
530, 640‧‧‧ cut the u plane of #2
540, 660‧‧‧ cut into the u plane of #N
600‧‧‧C/U plane coupling and cutting
610‧‧‧Split #1 is divided into specific c-planes
630‧‧‧Split #2 is divided into specific c-planes
650‧‧‧Split #N is divided into specific c-planes
700‧‧‧Partial decoupling C/U plane assembly
710‧‧‧Shared c-plane function
720‧‧‧Split #1 is divided into specific parts
730‧‧‧Split #1 splits the specific u-plane function
740‧‧‧Split #2 is divided into specific parts
750‧‧‧Split #2 splits the specific u-plane function
760‧‧‧Split #N split into specific parts
770‧‧‧Split #N splits the specific u-plane function
800‧‧‧First instance/project
810, 1110‧‧‧ messages
830‧‧‧Two-way message arrow
900‧‧‧Second instance
930‧‧‧ Random Access Response/Message
1000‧‧‧First instance
1100‧‧‧Split disconnection procedure
1130‧‧‧Handover procedure
1140‧‧·Information exchange
1200‧‧‧Division of specific random access procedures
1300‧‧‧Electronic devices
1310‧‧‧Application Circuit
1320‧‧‧Base frequency circuit
1321‧‧‧second generation (2G) baseband processor
1322‧‧‧3rd generation (3G) baseband processor
1323‧‧‧ fourth generation (4G) baseband processor
1324‧‧‧Other baseband processors
1325‧‧‧Central Processing Unit (CPU)
1326‧‧‧Audio digital signal processor (DSP)
1327‧‧‧Memory/storage
1330‧‧‧ Radio Frequency (RF) Circuit
1331‧‧‧Mixer circuit
1332‧‧‧Amplifier circuit
1333‧‧‧Filter circuit
1334‧‧‧Synthesizer circuit
1340‧‧‧ Front End Module (FEM) Circuit
1350‧‧‧Antenna
1400‧‧‧ first example method
1500‧‧‧Second example method
1600‧‧‧ hardware resources
1604‧‧‧ peripheral devices
1606‧‧‧Database
1608‧‧‧Network
1610, 1612, 1614‧‧ ‧ processors
1620‧‧‧Memory/storage
1630‧‧‧Communication resources
1640‧‧ ‧ busbar
1650‧‧ directive

The aspects, features, and advantages of the embodiments of the present invention will be apparent from the description of the accompanying drawings, in which A first view of a broad concept; FIG. 2 shows a second view of a portion of the wireless network of FIG. 1; FIG. 3 shows how a Radio Access Network (RAN) can be replaced in accordance with the embodiment shown in FIG. The (or additional) embodiment is divided into horizontal and vertical segments; Figure 4 shows a more detailed example of a horizontal segmentation in a wireless network architecture according to an example; Figure 5 shows a decoupled group with network segmentation A first example C/U plane implementation is shown; Figure 6 shows a second example C/U plane implementation with network segmentation coupling; Figure 7 shows a partial decoupling, partial coupling combination with network segmentation Example C/U plane implementation; Figure 8 shows a first instance split open procedure by the UE based on the threshold; Figure 9 shows a second instance split open procedure by the UE based on the quality of service level; Figure 10 shows by Base station An example split opens the program; Figure 11 shows a first instance split close procedure by a base station; Figure 12 shows a first instance random access procedure; Figure 13 shows an electronic device (e.g., UE or base station) in accordance with an embodiment Example implementation; Figure 14 shows a first example method of wireless communication of a fifth generation (5G) system in accordance with an embodiment; Figure 15 shows a second example method of wireless communication of a fifth generation (5G) system in accordance with an embodiment; Figure 16 shows a graphical representation of a hardware resource in accordance with an embodiment.

500‧‧‧C/U plane implementation

510‧‧‧All-in-one shared c-plane

520‧‧‧Split #1 u plane

530‧‧‧Split #2 u plane

540‧‧‧Split #N u plane

Claims (30)

An apparatus for wireless communication of a fifth generation (5G) system, the apparatus comprising: a first local component for identifying a radio access network (RAN) and a second remote component of the RAN a first associated component, the first association corresponding to a network segmentation; and a component for identifying a second association between the first local component of the RAN and a third component of the RAN, The third component is different from the second component of the RAN, where the second association corresponds to the network segmentation; wherein the second association is based on a traffic type, a traffic load, or a quality of service (QoS) requirement At least one. The device of claim 1, the device further comprising: an associated component for identifying a control plane segmentation of the network segmentation; and a user plane slice for identifying a plurality of user plane segments An associated component that is segmented from the control plane. The device of claim 1, the device further comprising: an associated component for identifying a control plane segmentation of the network segmentation; and for identifying a single user plane segmentation and the control plane segmentation An associated component. The device of claim 1, the device further comprising: an associated component for identifying a common control plane segmentation of the network segmentation; and a user plane slice for identifying a plurality of user plane segments An associated component that is segmented from the common control plane; and means for identifying a plurality of components in a particular control plane that are segmented into a particular control plane and that are associated with the common control plane. The device of claim 1, the device further comprising: means for determining whether to change a power state of the first component or the second component based on at least one of: for maintaining a mobile use Service continuity of a device (UE), or a service associated with the network segmentation to meet a particular QoS requirement (eg, low latency, super-reliability, or the like, or a combination thereof) If the load exceeds a threshold or decreases below a threshold and the number of user equipments (UEs) operating on the network segment exceeds a threshold or decreases below a threshold . The device of claim 5, the device further comprising: means for determining whether to change a power state of the first component or the second component based on a received control signal; wherein the control signal is derived from the following At least one of: one UE (and including an indication of an expected segmentation during a random access) or a peer base station/access point (BS/AP) (and including for requesting the target) A trigger message for the change of the power state at the BS). The device of claim 5, the device further comprising: transmitting a signal to a remote AP/BS or an mobility management entity in response to determining that the power state of the first component or the second component is to be changed ( At least one of the MME)/network control entities to exchange the components of the message. The device of claim 6, wherein the control signal is received through a UE interface (eg, the control signal originates from the UE), and the device further includes: responsive to receiving the control signal to be based on the service A component that determines whether to maintain a power state of the first component or the second component is monitored. The device of claim 6, wherein the control signal is received via a UE interface, and the device further comprises: responsive to receiving the control signal to determine whether to maintain the first component or based on a QoS criterion A component of a power state of the second component. The device of claim 1, the device further comprising: means for determining whether to change a power state of the first component or the second component based on at least one of: for neighbor cell conditions One UE reports or the number of traffic load/connections that are split for the network. The device of claim 5, the device further comprising: responsive to determining that the power state of the first component or the second component is to be changed, and handing over an active UE on the slice to an adjacent The components of the BS. The device of claim 5, the device further comprising: means for transmitting or receiving system information, the system information carrying information about the segmentation in the role of a base station (BS). The device of claim 1, the device further comprising: for base station (BS) based on one of the plurality of central controllers in the plurality of base stations (BS) or in the plurality of BSs An inter-signal exchange determines whether a component of a power state of the first component or the second component is to be changed. The device of claim 13, the device further comprising means for transmitting the message to an access point (AP) or a base station (BS) or receiving a message from the AP or the BS, the signaling indication A load condition for each of a plurality of network segments including the network segmentation. A device for wireless communication of a fifth generation (5G) system, the device comprising: a first local component for identifying a radio access network (RAN) at a user equipment (UE) a first associated component of the second remote component of the RAN, the first association corresponding to a network segmentation; and a first local component and the RAN for identifying the RAN at a UE a second associated component of the third component, the third component being different from the second component of the RAN, the second association corresponding to the network segmentation; wherein the second relationship is based on a traffic type, At least one of a workload or a quality of service (QoS) requirement. The device of claim 15, the device further comprising: means for determining whether to access a base station (BS) based on at least one of: a power state of one of the expected BSs, Link conditions, QoS requirements, or traffic load of neighboring cells. The device of claim 15, the device further comprising: a different access point (AP) or base station for maintaining a split to the network and another network segmentation different from the network segmentation ( BS) One of the connected components. A device operable in a base station (BS) for wireless communication in one of a fifth generation (5G) system, the device comprising: a radio frequency (RF) circuit for receiving a source network Virtualization component and/or software defining at least one communication of the network; and a baseband circuit for: identifying a first end of a radio access network (RAN) based on information from the communication a first association of the component with a second remote component of the RAN, the first association corresponding to a network segmentation; and identifying the RAN based on the same or a different communication of the at least one communication a second component associated with a third component of the RAN, the third component being different from the second component of the RAN, the second association corresponding to the network segmentation; wherein the second The contact is based on at least one of a traffic type, a traffic load, or a quality of service (QoS) requirement. The device of claim 18, wherein the baseband circuit is configured to: identify an association of one of the network segmentation control planes; and identify one of the plurality of user plane segments An association with the control plane. The device of claim 18, wherein the baseband circuit is configured to: identify an association of a control plane segmentation of the network segmentation; and identify a single user plane segmentation segmentation with the control plane An association. The device of claim 18, wherein the baseband circuit is configured to: identify an association of one of the network segments and share a control plane segmentation; and identify one of the plurality of user plane segments into a user plane segmentation An association with the common control plane segmentation; and identifying an association between all of the plurality of specific control planes and the division of the common control plane. The device of claim 18, wherein the baseband circuit is configured to: determine whether to change a power state of the first component or the second component based on at least one of: maintaining a mobile User equipment (UE) service continuity, or one of the services associated with the network slice to satisfy a particular QoS requirement (eg, low latency, super reliability, or the like, or a combination thereof) If the load exceeds a threshold or falls below a threshold, the number of user equipments (UEs) in the operation of the network slice exceeds a threshold or decreases below a threshold. The device of claim 22, wherein the baseband circuit is configured to: determine whether to change a power state of the first component or the second component based on a control signal received by the RF circuit; wherein the control signal From at least one of: a UE (and including an indication of an expected segmentation during a random access) or a peer base station/access point (BS/AP) (and including requesting the target) A trigger message for the change of the split power state at the BS). The device of claim 22, wherein the baseband circuit is configured to: transmit a signal to a remote AP/BS or in response to determining that the power state of the first component or the second component is to be changed At least one of an Mobility Management Entity (MME)/Network Control Entity exchanges a message. The device of claim 23, wherein the control signal is received through a UE interface, and wherein the baseband circuit is configured to: determine, in response to receiving the control signal, whether to maintain the first based on traffic monitoring A power state of the component or the second component. The device of claim 23, wherein the control signal is received through a UE interface, and wherein the baseband circuit is configured to: determine, in response to receiving the control signal, whether to maintain the first A power state of a component or the second component. The device of claim 18, wherein the baseband circuit is configured to: determine whether to change a power state of the first component or the second component based on: a UE report for neighbor cell conditions or At least one of the traffic load/connection number conditions for the network segmentation; or a handshake between the plurality of BSs or among the plurality of central controllers BS of the plurality of BSs. The device of claim 22, wherein the baseband circuit is configured to: in response to determining that the power state of the first component or the second component is to be changed, handing over an active UE on the segmentation to An adjacent BS. The device of claim 22, wherein the baseband circuit is operative to cause the RF circuit to transmit system information carrying information about an active segmentation in a BS, or to cause the RF circuit to receive a carry System information of the information split in the role of a BS. The device of claim 27, wherein the baseband circuit is configured to cause the RF circuit to: transmit the message to an AP or a BS, the signaling indicating a plurality of networks including the network segmentation The load condition of each of the segments; or receiving a message from an AP or a BS indicating a load condition for each of a plurality of network segments including the network segmentation.