Carrier configuration and monitoring of communication devices in a shared communication environment

Abstract

Methods, systems and computer program products are provided for carrier configuration and monitoring of communication devices in a shared communication environment. In some implementations, carrier configuration may be performed in a radio access network-enabled radio unit (RU), and one or more distributed units (DUs) may be associated with different carriers and / or different network operators. Additionally, monitoring of each such DU and / or its management connections may be performed, such that the remote radio units can be configured to determine individual carrier status in the presence of a particular failure of the DU.

Description

【Technical Field】 【0001】 In some implementation examples, the subject matter of this protection relates to a telecommunication system, and in particular, to a communication device in a shared communication environment capable of communicatively connecting one or more distributed units to one or more remote radio units, for example, carrier configuration and monitoring of a distributed unit. 【Background Art】 【0002】 In today's world, cellular networks provide on-demand communication capabilities to individuals and enterprises. Generally, a cellular network is a wireless network that can be distributed over a terrestrial area called a cell. Each such cell is served by at least one fixed-position transceiver called a cell site or base station. Each cell can use a different set of frequencies from its neighboring cells to avoid interference and provide improved service within each cell. When cells are joined together, they provide wireless coverage over a wide geographical area, thereby enabling a large number of mobile phones, and / or other wireless devices or portable transceivers to communicate with each other, as well as with some fixed transceiver and phone in the network. Such communication is performed via the base station and is achieved even when the mobile transceiver is moving through two or more cells during transmission. Major wireless communication providers have deployed such cell sites around the world, thereby enabling communication mobile phones and mobile computing devices to connect to the public switched telephone network and the public Internet. 【0003】 A mobile phone is a cell phone that can receive and / or transmit phone and / or data communications via a cell site or transmission tower by using radio waves to transfer signals to and from other mobile phones. Given the large number of mobile phone users, the current mobile phone network provides limited shared resources. In this regard, cell sites and handsets can change frequencies and use low-power transmitters to enable simultaneous use of the network by many callers with less interference. Cell site coverage can depend on a particular geographical location and / or the number of users who can potentially use the network. For example, in urban areas, a cell site may have a range of up to about half a mile, while in suburban areas, the range may be as much as 5 miles, and in some areas, users can receive signals from cell sites 25 miles away. 【0004】 The following are some examples of digital cellular technologies used by telecommunications providers, namely, Global System for Mobile Communications ("GSM"), General Packet Radio Service ("GPRS"), cdmaOne, CDMA2000, Evolutionary Data Optimization ("EV-DO"), Enhanced Data Rates for GSM Evolution ("EDGE"), Universal Mobile Telecommunications System ("UMTS"), Digital Enhanced Cordless Telecommunications ("DECT"), Digital AMPS ("IS-136 / TDMA"), and Integrated Digital Enhanced Network ("iDEN"). 4G LTE, developed by the Long-Term Evolution, or Third Generation Partnership Project ("3GPP" (registered trademark)) standards body, is a high-speed data wireless communication standard for mobile phones and data terminals. Currently, 5G standards are being developed and deployed. 3GPP cellular technologies such as LTE and 5G NR are evolutions of earlier 3GPP technologies such as GSM / EDGE and UMTS / HSPA digital cellular technologies, enabling increased capacity and speed through improvements to the core network and the use of different radio interfaces. 【0005】 A cellular network can be divided into a radio access network and a core network. The radio access network (RAN) may include network functions capable of handling radio layer communication processing. The core network may include network functions capable of handling higher layer communications, such as Internet Protocol (IP), the transport layer, and the application layer. In some cases, the RAN functions may be divided into baseband unit functions and radio unit functions. For example, a radio unit connected to a baseband unit via a fronthaul network may be responsible for lower layer processing of the radio physical layer, while the baseband unit may be responsible for higher layer radio protocols, such as MAC and RLC. 【0006】 To ensure uninterrupted communication in wireless communication systems, it is sometimes necessary to properly configure various devices and / or monitor for communication session failures among these devices. However, currently implemented protocols cannot provide effective management of such device configurations (including any shared device configurations) or monitor and respond to communication session failures. [Overview of the Initiative] [Means for solving the problem] 【0007】 In some implementations, the protection subject is a method implemented by a computer. This method may include grouping a plurality of first communication devices into a plurality of groups, associating each of the plurality of groups with a second communication device of a wireless communication system, configuring the second communication device to communicate with one or more groups of the first communication devices, and transmitting one or more pieces of communication information in the wireless communication system using the configured second communication device. 【0008】 In some implementations, the protected object may include one or more of the following optionally selectable features. In some implementations, each of the multiple first communication devices may be a distributed unit. Furthermore, the second communication device may be a wireless unit. 【0009】 In some implementations, one or more of the multiple first communication devices may be host first communication devices, and one or more of the multiple first communication devices may be shared resource operator first communication devices. Furthermore, each host first communication device of the one or more first communication devices may be grouped into one or more host groups of a plurality of groups, and each shared resource operator first communication device of the other one or more first communication devices may be grouped into one or more shared resource operator groups of a plurality of groups. Furthermore, the method may also include detecting a failure in the host first communication device, and the method may also include terminating communication with the faulty host first communication device, the communication of which may be related to a default carrier controlled by the faulty host first communication device. Furthermore, configuring a second communication device may include reconfiguring it to communicate with another one or more groups of first communication devices based on the detection of a failure in the host first communication device. Furthermore, the reconfiguration may be performed using the service management orchestration function of the wireless communication system, the reconfiguration may be performed on the management plane, and / or the method may also include sending a call home command to one or more other groups of the first communication devices, and receiving one or more carrier settings from one or more other groups of the first communication devices in response to the call home command, wherein one or more carrier settings are set by one or more other groups of the first communication devices. Furthermore, one or more carrier settings may include at least one of one or more transmit array carrier settings and one or more receive array carrier settings, and / or transmitting one or more communication information in the wireless communication system may include transmitting one or more communication information using one or more carrier settings. 【0010】 In some implementations, at least one of grouping, configuration, and transmission may be performed by at least one base station of the wireless communication system. Furthermore, the base station may include at least one of a base station, an eNodeB base station, a gNodeB base station, a radio base station, and any combination thereof. Furthermore, the base station may be a base station operating in at least one of a Long-Term Evolution communication system, a New Radio communication system, a wireless communication system, and any combination thereof. 【0011】 Also described are non-temporary computer program products (i.e., physically implemented computer program products) that store instructions causing at least one data processor to perform the operations described herein when executed by one or more data processors of one or more computing systems. Similarly, computer systems that may include one or more data processors and memory coupled to one or more data processors are also described. The memory can temporarily or permanently store instructions causing at least one processor to perform one or more of the operations described herein. Furthermore, the methods may be implemented by one or more data processors in a single computing system or distributed across two or more computing systems. Such computing systems may be connected via one or more connections that can exchange data and / or commands or other instructions, etc., and these connections include, but are not limited to, connections via networks (e.g., the Internet, wireless wide area networks, local area networks, wide area networks, wired networks, etc.) via direct connections between one or more of the computing systems. 【0012】 Details of one or more modifications of the protected subject matter described herein are given in the accompanying drawings and the following description. Other features and advantages of the protected subject matter described herein will be evident from the description and drawings, and from the claims. [Brief explanation of the drawing] 【0013】 The accompanying drawings incorporated herein and constituting part of this specification illustrate specific embodiments of the protected subject matter disclosed herein and, together with the description, help to illustrate some of the principles relating to the disclosed implementations. 【0014】 [Figure 1a] This diagram illustrates an exemplary conventional Long Term Evolution (LTE) communication system. [Figure 1b] This figure shows further details of the exemplary LTE system shown in Figure 1a. [Figure 1c] Figure 1a shows further details of the evolved packet core of the exemplary LTE system. [Figure 1d] This figure shows an exemplary evolved Node B of the exemplary LTE system shown in Figure 1a. [Figure 2] Figures 1a to 1d show further details of the evolved Node B. [Figure 3] This figure shows an exemplary virtual wireless access network based on several implementation examples of the protected area. [Figure 4] This figure shows an exemplary 3GPP partition architecture for providing its users with access to higher frequency bands. [Figure 5a] This is a diagram illustrating an exemplary 5G wireless communication system. [Figure 5b] This figure shows an exemplary layer architecture for a partitioned gNB and / or partitioned ng-eNB (for example, a next-generation eNB that can be connected to a 5GC). [Figure 5c] Figures 5a and 5b show an example of functional partitioning in the gNB architecture. [Figure 6] This document illustrates an exemplary system for performing carrier access configuration and monitoring in a wireless communication system, relating to several implementations of the protections described herein. [Figure 7]An exemplary method for performing a carrier access control setting procedure according to some implementation examples of the present protection object is shown. [Figure 8] An exemplary method for performing monitoring of monitoring failures according to some implementation examples of the present protection object is shown. [Figure 9] An exemplary system according to some implementation examples of the present protection object is shown. [Figure 10] An exemplary method according to some implementation examples of the present protection object is shown. 【Mode for Carrying Out the Invention】 【0015】 The present protection object can provide a system and method that can be implemented in a wireless communication system. Such a system can include various wireless communication systems, including a 5G new radio communication system, a long-term evolution communication system, and the like. 【0016】 In some implementation examples, the present protection object relates to the execution of carrier setting in a radio unit (RU) corresponding to a radio access network, and one or more distributed units (DUs) may be associated with various carriers and / or various network operators. Further, the present protection object may be configured to perform monitoring of each of such DUs and / or its management connection, whereby the remote radio unit can be configured to determine the individual carrier state when there is a specific failure in the DU. 【0017】 To execute the above-described setting process and / or monitoring process, the protected object may be configured to group a plurality of first communication devices (e.g., distributed units) into a plurality of groups. Each group of such distributed units may be associated with a second communication device (e.g., remote radio unit). One or more distributed units may be communicatively connected in a wireless communication system, e.g., a Long-Term Evolution communication system, a New Radio communication system, and / or any other communication system. It is also possible to configure a remote radio unit to communicate with one or more groups of distributed units. One or more communication information may be transmitted in such a wireless communication system using the configured one or more distributed units. 【0018】 In some embodiments, one or more distributed units may function as a host distributed unit, and another distributed unit may be a distributed unit of a shared resource operator. Each host distributed unit of the one or more distributed units may be grouped into one or more host groups. Each distributed unit of the shared resource operator may be grouped into one or more shared resource operator groups. 【0019】 In some embodiments, the protected object may be further configured to detect a malfunction of a host distributed unit and, as a result, terminate communication with the malfunctioning host distributed unit. Communication may be associated with a default carrier controlled by the malfunctioning host distributed unit. Further, configuring the radio unit may include reconfiguring the radio unit to communicate with another one or more groups of distributed units based on the detection of the malfunction of the host distributed unit. The reconfiguration may be performed using a service management orchestration function of the wireless communication system. Instead of or in addition to the above, the reconfiguration may be performed in a management plane. 【0020】 In some implementations, the protected object may be configured to send a call home command to one or more other groups of the distributed unit and to receive one or more carrier settings from one or more other groups of the distributed unit in response to the call home command. The carrier settings may be set by one or more other groups of the distributed unit. For example, the carrier settings may include at least one of one or more transmit array carrier settings and / or one or more receive array carrier settings. In some implementations, the transmission of one or more communication information in the wireless communication system may include one or more transmissions of one or more communication information using such carrier settings. 【0021】 In some implementations, one or more of the above processes may be performed by at least one base station of the wireless communication system. The base station may include at least one of a base station, an eNodeB base station, a gNodeB base station, a radio base station, and any combination thereof. Furthermore, the base station may be a base station operating in at least one of a long-term evolution communication system, a new radio communication system, a wireless communication system, and any combination thereof. 【0022】 One or more aspects of the protections described herein may be incorporated into the transmitter and / or receiver components of base stations (e.g., gNodeB, eNodeB, etc.) in such communication systems. The following is a general discussion of long-term evolution communication systems and 5G new radio communication systems. 【0023】 I. Long-Term Evolution Communication Systems Figures 1a-1c and 2 illustrate an exemplary conventional Long-Term Evolution (LTE) communication system 100 with its various components. The LTE system, or 4G LTE, is governed by a standard for high-speed data wireless communication for mobile phones and data terminals, as is commercially known. This standard is an evolution of GSM / EDGE ("Global System for Mobile Communications" / "GSM Evolutionary High-Speed ​​Data Rate") and UMTS / HSPA ("Universal Mobile Communications System" / "High-Speed ​​Packet Access") network technologies. This standard was developed by 3GPP ("Third Generation Partnership Project"). 【0024】 As shown in Figure 1a, the system 100 may include an evolved universal terrestrial radio access network ("EUTRAN") 102, an evolved packet core ("EPC") 108, and an evolved packet data network ("PDN") 101, where EUTRAN 102 and EPC 108 provide communication between user terminals 104 and PDN 101. EUTRAN 102 may include multiple evolved nodes B ("eNodeB", "ENODEB", "enodeb", or "eNB") or base stations 106 (a,b,c) (as shown in Figure 1b) that provide communication capabilities to multiple user terminals 104 (a,b,c). The user terminal 104 may be a mobile phone, smartphone, tablet, personal computer, personal digital assistant ("PDA"), server, data terminal, and / or any other type of user terminal, and / or any combination thereof. The user terminal 104 can connect to the EPC 108 and ultimately to the PDN 101 via any eNodeB 106. Typically, the user terminal 104 can connect to the eNodeB 106 closest in terms of distance. In the LTE system 100, the EUTRAN 102 and EPC 108 work together to provide connectivity, mobility, and services for the user terminal 104. 【0025】 Figure 1b shows further details of the network 100 shown in Figure 1a. As mentioned above, EUTRAN 102 includes multiple eNodeB 106, also known as cell sites. The eNodeB 106 provides radio functionality and performs important control functions, including scheduling or radio resource management of airlink resources, active mode mobility or handover, and admission control for services. The eNodeB 106 is responsible for selecting which mobility management entity (MME (mobility management entity) as shown in Figure 1c) will serve the user terminal 104, and for protocol features such as header compression and encryption. The eNodeB 106 constituting EUTRAN 102 cooperate with each other for radio resource management and handover. 【0026】 Communication between the user terminal 104 and the eNodeB 106 takes place via the air interface 122 (also known as the “LTE-Uu” interface). As shown in Figure 1b, the air interface 122 provides communication between the user terminal 104b and the eNodeB 106a. The air interface 122 uses orthogonal frequency division multiple access (“OFDMA”) and single-carrier frequency division multiple access (“SC-FDMA”), as well as OFDMA variants, on the downlink and uplink, respectively. OFDMA enables the use of several known antenna techniques, including multiple input multiple output (“MIMO”). 【0027】 The air interface 122 uses various protocols, including radio resource control ("RRC") for signaling between the user terminal 104 and the eNodeB 106, and a non-access stratum ("NAS") for signaling between the user terminal 104 and the MME (as shown in Figure 1c). In addition to signaling, user traffic is forwarded between the user terminal 104 and the eNodeB 106. Both signaling and traffic in system 100 are carried by physical layer ("PHY") channels. 【0028】 Multiple eNodeB106s can be interconnected using X2 interfaces 130(a,b,c). As shown in Figure 1a, X2 interface 130a provides interconnection between eNodeB106a and eNodeB106b, X2 interface 130b provides interconnection between eNodeB106a and eNodeB106c, and X2 interface 130c provides interconnection between eNodeB106b and eNodeB106c. The X2 interface can be established between two eNodeBs to provide signal exchange, which may include information related to load or interference, as well as information related to handover. The eNodeB106s communicate with the evolved packet core 108 via S1 interfaces 124(a,b,c). The S1 interface 124 can be divided into two interfaces: one for the control plane (shown as the control plane interface (S1-MME interface) 128 in Figure 1c) and the other for the user plane (shown as the user plane interface (S1-U interface) 125 in Figure 1c). 【0029】 EPC108 establishes and implements Quality of Service (QoS) for user services, enabling user terminals 104 to maintain a consistent Internet Protocol (IP) address while in transit. Note that each node in network 100 has its own IP address. EPC108 is designed to interact with legacy wireless networks. EPC108 is also designed to separate the control plane (i.e., signaling) and the user plane (i.e., traffic) in the core network architecture, which allows for greater flexibility in implementations, as well as independent scalability of control and user data functions. 【0030】 The EPC108 architecture is dedicated to packet data and is illustrated in detail in Figure 1c. The EPC108 includes a Serving Gateway (S-GW) 110, a PDN Gateway (P-GW) 112, a Mobility Management Entity ("MME") 114, a Home Subscriber Server ("HSS (home subscriber server)") 116 (a subscriber database for the EPC108), and a Policy Control and Billing Rule Function ("PCRF (home subscriber server)") 118. Some of these (such as the S-GW, P-GW, MME, and HSS) are often combined into a node according to the manufacturer's implementation. 【0031】 S-GW110 functions as an IP packet data router and is the bearer route anchor for user terminals within EPC108. Therefore, when a user terminal moves from one eNodeB106 to another during mobility operation, S-GW110 remains the same, and the bearer route toward EUTRAN102 is switched to communicate with the new eNodeB106 serving user terminal 104. If user terminal 104 moves to the domain of another S-GW110, MME114 will forward all of the user terminal's bearer routes to the new S-GW. S-GW110 establishes bearer routes for user terminals to one or more P-GW112s. When downstream data is received for an idle user terminal, S-GW110 buffers the downstream packets and requests MME114 to identify and re-establish the bearer routes to and through EUTRAN102. 【0032】 P-GW112 is the gateway between EPC108 (and user terminals 104 and EUTRAN102) and PDN101 (shown in Figure 1a). P-GW112 functions as a router for user traffic and performs functions on behalf of the user terminals. These include assigning IP addresses to user terminals, packet filtering of downstream user traffic to ensure that downstream user traffic is placed on the appropriate bearer route, and implementing downstream QoS, including data rates. Depending on the services used by the subscriber, there may be multiple user data bearer routes between user terminal 104 and P-GW112. A subscriber may use services on a PDN served by different P-GWs, in which case the user terminal has at least one bearer route established to each P-GW112. If the S-GW110 also changes during a handover of a user terminal from one eNodeB to another, the bearer route from P-GW112 is switched to the new S-GW. 【0033】 MME114 manages user terminals 104 within EPC108, including managing subscriber authentication, maintaining context for authenticated user terminals 104, establishing data bearer routes within the network for user traffic, and tracking the location of idle mobiles that have not detached from the network. For idle user terminals 104 that need to be reconnected to the access network to receive downstream data, MME114 initiates paging to locate the user terminal and re-establishes the bearer route to and through EUTRAN102. The MME114 for a particular user terminal 104 is selected by the eNodeB106 from which the user terminal 104 initiates system access. MMEs are typically part of a collection of MMEs within EPC108 for load sharing and redundancy purposes. In establishing user data bearer routes, MME114 is responsible for selecting P-GW112 and S-GW110, which constitute the endpoints of the data route through EPC108. 【0034】 PCRF118 is responsible for policy control decision-making and controlling the flow-based billing functionality within the policy control enforcement function (PCEF) residing in P-GW110. PCRF118 provides QoS authorization (QoS class identifier (QCI) and bitrate), which determines how a given data flow is handled within the PCEF and ensures that this conforms to the user's subscription profile. 【0035】 As described above, IP service 119 is provided by PDN 101 (as shown in Figure 1a). 【0036】 Figure 1d shows an exemplary structure of eNodeB106. eNodeB106 may include at least one remote radio head ("RRH") 132 (typically, there may be three RRHs) and a baseband unit ("BBU") 134. The RRH 132 may be connected to an antenna 136. The RRH 132 and BBU 134 may be connected using an optical interface compliant with the Common Public Radio Interface ("CPRI") / Enhanced CPRI ("eCPRI") 142 standard, either using a custom control and user plane framing method specific to the RRH or using an O-RAN Alliance compliant control and user plane framing method. The operation of eNodeB106 can be characterized using the following standard parameters (and specifications), namely, radio frequency bands (band 4, band 9, band 17, etc.), bandwidth (5, 10, 15, 20 MHz), access method (downlink: OFDMA, uplink: SC-OFDMA), antenna technology (single-user and multi-user MIMO, uplink: single-user and multi-user MIMO), number of sectors (maximum 6), maximum transmission speed (downlink: 150 Mb / s, uplink: 50 Mb / s), S1 / X2 interface (1000Base-SX, 1000Base-T), and mobile environment (maximum 350 km / h). BBU134 can handle digital baseband signal processing, S1 line termination, X2 line termination, call processing, and monitoring and control processing. IP packets received from EPC108 (not shown in Figure 1d) can be modulated into digital baseband signals and transmitted to RRH132. Conversely, the digital baseband signal received from the RRH132 can be demodulated into IP packets for transmission to the EPC108. 【0037】 The RRH132 can transmit and receive radio signals using the antenna 136. The RRH132 can convert digital baseband signals from the BBU134 into radio frequency (RF) signals (using a converter ("CONV (converter)") 140) and power amplified them (using an amplifier ("AMP (amplifier)") 138 for transmission to the user terminal 104 (not shown in Figure 1d). Conversely, RF signals received from the user terminal 104 are amplified (using the AMP 138) and converted into digital baseband signals (using the CONV 140) for transmission to the BBU134. 【0038】 Figure 2 shows additional details of an exemplary eNodeB106. The eNodeB106 includes multiple layers, namely LTE Layer 1 202, LTE Layer 2 204, and LTE Layer 3 206. LTE Layer 1 includes the physical layer ("PHY (physical layer)"). LTE Layer 2 includes medium access control ("MAC (medium access control)"), radio link control ("RLC (radio link control)"), and packet data convergence protocol ("PDCP (packet data convergence protocol)"). LTE Layer 3 includes various functions and protocols, including radio resource control ("RRC (radio resource control)"), dynamic resource allocation, eNodeB measurement configuration and provisioning, radio admission control, connectivity mobility control, and radio resource management ("RRM (radio resource management)"). The RLC protocol is an automatic repeat request ("ARQ (automatic repeat request)") fragmentation protocol used over the cellular air interface. The RRC protocol handles LTE Layer 3 control plane signaling between the user terminal and EUTRAN. RRC includes functions for connection establishment and release, broadcasting system information, establishing / reconfiguring and releasing radio bearers, RRC connection mobility procedures, paging notifications and releases, and outer loop power control. PDCP performs IP header compression and decompression, user data transfer, and maintaining the radio bearer sequence number. BBU134, shown in Figure 1d, may include LTE Layers L1-L3. 【0039】 One of the main functions of eNodeB106 is radio resource management, which includes scheduling of both uplink and downlink air interface resources for user terminal 104, as well as bearer resource control and admission control. As an agent for EPC108, eNodeB106 is responsible for forwarding paging messages used to locate mobile devices when they are idle. eNodeB106 also communicates common control channel information wirelessly, communicates header compression, encryption and decryption of wirelessly transmitted user data, and establishes handover reporting and trigger criteria. As described above, eNodeB106 can cooperate with other eNodeB106s via the X2 interface for handover and interference management purposes. eNodeB106 communicates with the EPC's MME via the S1-MME interface and with the S-GW using the S1-U interface. Furthermore, eNodeB106 exchanges user data with the S-GW via the S1-U interface. eNodeB106 and EPC108 have a many-to-many relationship to support load sharing and redundancy between MMEs and S-GWs. eNodeB106 selects an MME from a group of MMEs so that the load can be shared by multiple MMEs to avoid congestion. 【0040】 II.5G NR Wireless Communication Network In some implementations, this protection concerns 5G New Radio ("NR" or new radio) communication systems. 5G NR is the next telecommunications standard beyond the 4G / IMT-Advanced standard. 5G networks offer greater capabilities than current 4G, enabling a greater number of mobile broadband users per unit area and allowing for more and / or unlimited data consumption in gigabytes per month and per user. This could allow users to stream high-definition media for hours per day using their mobile devices, even if this is not possible on Wi-Fi networks. 5G networks also offer improved support for device-to-device communication, lower costs, lower latency than 4G equipment, and lower battery consumption. Compared to existing systems, such networks offer data rates of tens of megabits per second for a large number of users, 100 Mb / s for metropolitan areas, 1 Gb / s simultaneous to users within a limited area (e.g., an office floor), numerous simultaneous connections for wireless sensor networks, enhanced spectral efficiency, improved coverage, increased signaling efficiency, latency of 1-10 ms, and reduced latency. 【0041】 Figure 3 shows an exemplary virtual radio access network 300. The network 300 can provide communication between various components, including base stations (e.g., eNodeB, gNodeB) 301, radio equipment 307, aggregation units 302, digital units 304, and radio units 306. Components in the system 300 can be communicatively coupled to the core using backhaul links 305. The aggregation unit ("CU (centralized unit)") 302 can be communicatively coupled to the distributed unit ("DU (distributed unit)") 304 using midhaul connections 308. The radio frequency ("RU (radio frequency)") component 306 can be communicatively coupled to the DU 304 using fronthaul connections 310. 【0042】 In some implementations, CU302 can provide intelligent communication capabilities to one or more DU units 308. Units 302, 304 may include one or more base stations, macro base stations, micro base stations, remote radio heads, and / or any combination thereof. 【0043】 In lower-layer partitioned architecture environments, the CPRI bandwidth requirement for NR can be several hundred Gb / s. CPRI compression can be performed at the DU and RU (as shown in Figure 3). In 5G communication systems, compressed CPRI on Ethernet frames is referred to as eCPRI and is the recommended fronthaul network. This architecture can enable fronthaul / midhaul standardization, which may include upper-layer partitioning (e.g., Option 2 or Option 3-1 (upper / lower RLC partitioned architecture)) and fronthaul using an L1 partitioned architecture (Option 7). 【0044】 In some implementations, the lower layer partitioning architecture (e.g., Option 7) may include a receiver at the uplink, joint processing across multiple transmission points (TPs) for both DL / UL, and transport bandwidth and latency requirements to facilitate deployment. Furthermore, the protected lower layer partitioning architecture may include partitioning between cell-level processing and user-level processing, which may include cell-level processing at remote units ("RUs") and user-level processing at DUs. Additionally, using the protected lower layer partitioning architecture, frequency-domain samples may be transported over Ethernet fronthauls, and the frequency-domain samples may be compressed for reduced fronthaul bandwidth. 【0045】 Figure 4 shows an exemplary communication system 400 that can implement 5G technology and give its users the use of higher frequency bands (for example, greater than 10 GHz). System 400 may include a macrocell 402 and small cells 404 and 406. 【0046】 The mobile device 408 may be configured to communicate with one or more of the small cells 404, 406. The system 400 can enable the division of the control plane (C-plane) and user plane (U-plane) between the macrocell 402 and the small cells 404, 406, with the C-plane and U-plane utilizing different frequency bands. Specifically, the small cells 402, 404 may be configured to utilize a higher frequency band when communicating with the mobile device 408. The macrocell 402 can utilize the existing cellular band for C-plane communication. The mobile device 408 may be communicatively coupled via the U-plane 412, where the small cell (e.g., small cell 406) can provide higher data rates and more flexible / cost / energy-efficient operation. The macrocell 402 can maintain good connectivity and mobility via the C-plane 410. Furthermore, in some cases, LTE and NR may be transmitted on the same frequency. 【0047】 Figure 5a shows an exemplary 5G wireless communication system 500, based on several implementations of the protected subject. System 500 may be configured to have a lower-layer partitioning architecture according to option 7-2. System 500 may include a core network 502 (e.g., a 5G core) and one or more gNodeBs (or gNBs), where the gNB may have an aggregation unit gNB-CU. The gNB-CU may be logically divided into a control plane portion gNB-CU-CP 504 and one or more user plane portions gNB-CU-UP 506. The control plane portion 504 and the user plane portion 506 may be configured to be communicatively coupled using an E1 communication interface 514 (as defined in the 3GPP standard). The control plane portion 504 may be configured to be responsible for executing the RRC and PDCP protocols of the radio stack. 【0048】 The control plane portion 504 and user plane portion 506 of the gNB aggregation unit may be configured to communicate with one or more distributed units (DUs) 508, 510 according to the upper layer partitioning architecture. The distributed units 508, 510 may be configured to execute the upper parts of the RLC, MAC, and PHY layer protocols of the radio stack. The control plane portion 504 may be configured to communicate with the distributed units 508, 510 using an F1-C communication interface 516, and the user plane portion 506 may be configured to communicate with the distributed units 508, 510 using an F1-U communication interface 518. The distributed units 508, 510 may be connected to one or more remote radio units (RUs) 512 via a fronthaul network 520 (which may include one or more switches, links, etc.), which communicate with one or more user terminals (not shown in Figure 5a). The remote wireless unit 512 may be configured to execute the lower part of the PHY layer protocol and to provide antenna capabilities to the remote unit for communication with the user terminal (similar to the above description relating to Figures 1a-2). 【0049】 Figure 5b shows an exemplary layer architecture 530 of a segmented gNB. Architecture 530 can be implemented within the communication system 500 shown in Figure 5a, which can be configured as a virtualized, non-aggregated radio access network (RAN) architecture, thereby allowing layers L1, L2, L3 and radio processing to be virtualized and non-aggregated within aggregated units, distributed units, and radio units. As shown in Figure 5b, the gNB-DU 508 can be communicatively coupled to the gNB-CU-CP control plane portion 504 (also shown in Figure 5a) and the gNB-CU-UP user plane portion 506. Each of components 504, 506, and 508 may be configured to include one or more layers. 【0050】 The gNB-DU508 may include RLC, MAC, and PHY layers, as well as various communication sublayers. These may include the F1 Application Protocol (F1-AP) sublayer, the GPRS Tunneling Protocol (GTPU) sublayer, the Stream Controlled Transmission Protocol (SCTP) sublayer, the User Datagram Protocol (UDP) sublayer, and the Internet Protocol (IP) sublayer. As described above, the distributed unit 508 may also be communicatively coupled to the control plane portion 504 of the aggregated unit, which may also include the F1-AP, SCTP, and IP sublayers, as well as the Radio Resource Control and PDCP Control (PDCP-C) sublayers. Furthermore, the distributed unit 508 may also be communicatively coupled to the user plane portion 506 of the aggregated unit of the gNB. The user plane portion 506 may include the Service Data Adaptation Protocol (SDAP), PDCP User (PDCP-U), GTPU, UDP, and IP sublayers. 【0051】 Figure 5c shows an exemplary functional partition in the gNB architecture shown in Figures 5a and 5b. As shown in Figure 5c, gNB-DU508 can be communicatively coupled to gNB-CU-CP504 and GNB-CU-UP506 using the F1-C communication interface. gNB-CU-CP504 and GNB-CU-UP506 can be communicatively coupled using the E1 communication interface. The upper part of the PHY layer (or Layer 1) may be performed by gNB-DU508, and the lower part of the PHY layer may be performed by RU (not shown in Figure 5c). As shown in Figure 5c, the RRC and PDCP-C parts may be performed by the control plane part 504, and the SDAP and PDCP-U parts may be performed by the user plane part 506. 【0052】 Some of the functions of the PHY layer in a 5G communication network may include error detection on the transport channel and indication to higher layers, FEC coding / decoding of the transport channel, hybrid ARQ soft synthesis, rate matching of coded transport channels to physical channels, mapping of coded transport channels to physical channels, power weighting of physical channels, modulation and demodulation of physical channels, frequency and time synchronization, radio characteristics measurement and indication to higher layers, MIMO antenna processing, digital and analog beamforming, RF processing, and other functions. 【0053】 The Layer 2 MAC sublayer can perform beam management, random access procedures, mapping between logical channels and transport channels, concatenation of multiple MAC service data units (SDUs) belonging to a single logical channel into a transport block (TB), multiplexing / demultiplexing of SDUs belonging to a logical channel to / from a TB delivered to the physical layer on the transport channel, scheduling information reporting, error correction by HARQ, priority processing between logical channels of a single UE, priority processing between UEs by dynamic scheduling, transport format selection, and other functions. The functions of the RLC sublayer may include forwarding upper-layer packet data units (PDUs), error correction by ARQ, sorting, duplication, and protocol error detection of data PDUs, and re-establishment. The PDCP sublayer can be responsible for forwarding user data, various functions during re-establishment procedures, retransmission of SDUs, discarding SDUs on the uplink, and forwarding control plane data. 【0054】 The Layer 3 RRC sublayer can perform functions such as broadcasting system information to NAS and AS, establishing, maintaining, and releasing RRC connections, securing, establishing, configuring, maintaining, and releasing point-to-point radio bearers, mobility functions, reporting, and other functions. 【0055】 III. Carrier Configuration and Distributed Unit Monitoring In some implementations, the protected object may relate to the execution of carrier configuration in a radio access network-enabled radio unit (RU), where one or more distributed units (DUs) may be associated with various carriers and / or various network operators. Furthermore, the protected object may be configured to monitor each of such DUs and / or their management connections, thereby enabling the remote radio unit to determine the individual carrier status when a specific failure occurs in a DU. 【0056】 Existing wireless communication systems (the system and, in particular, its management plane components) do not allow carriers associated with a radio unit to be individually configured and / or occupied by two or more distributed units. Furthermore, such systems do not support determining one or more carrier radio frequency (RF) states individually based on monitoring of each radio unit. In particular, existing systems configure a carrier in a remote unit located away from a distributed unit, and then determine one or more carrier RF states based on monitoring (different from performing monitoring on a carrier-by-carrier basis) of a remote unit controller session that directly controls the entire remote unit. 【0057】 Furthermore, existing wireless communication systems do not support the sharing of a single radio unit by multiple distributed units when each distributed unit is associated with and / or may belong to a different public land mobile network (PLMN) operator. On the other hand, sharing of radio units across different PLMN operators may be necessary for radio access network (RAN) sharing, spectrum sharing, and / or network slicing processes. 【0058】 Conventional wireless units receive carrier configuration via the NETCONF (network configuration) management protocol from a wireless unit controller (which can be, for example, a distributed unit and / or a service management and orchestration (SMO) function unit). Typically, the entity that generates the carrier configuration in a wireless unit is a distributed unit acting as a NETCONF client. Furthermore, existing wireless units use a monitoring timer to monitor NETCONF connectivity to NETCONF clients (e.g., one or more distributed units, an SMO, etc.). In this event, the monitoring timer fails, and the wireless unit performs one of the following hypothetical actions. In the first hypothetical action, even after entering monitoring failure handling mode, there remains at least one running, active NETCONF session between the wireless unit and a NETCONF client that has subscribed to receive monitoring notifications. The wireless unit also remains operational and performs one or more periodic call-home procedures to a known wireless unit controller. In another scenario, after entering monitoring failure handling, the wireless unit voluntarily performs a reset because there are no running NETCONF sessions between the wireless unit and any NETCONF clients that have subscribed to receive monitoring notifications. In either scenario, when one monitoring timer (first scenario) or all monitoring timers (second scenario) fail, the existing communication system does not provide the structure or operational framework for the processes that distributed units would need to execute next for the continued operation of such a system. 【0059】 In some implementations, to overcome the above challenges, the protected object can implement one or more configuration methods for configuring one or more radio units to communicate with one or more distributed units, where some carriers may be associated with one distributed unit while others are associated with different distributed units. Furthermore, the protected object can be configured to implement enhanced access control in the radio units so that one distributed unit can perform configuration and control only for the carriers associated with that distributed unit. In addition, the radio units can be configured to perform one or more procedures to ensure continuity of communication when a monitoring timer associated with one of the distributed units fails. 【0060】 Figure 6 shows an exemplary system 600 that performs carrier access configuration and monitoring in a wireless communication system, relating to several implementations of the protected subject. System 600 may be a wireless access network operating in a wireless communication environment (e.g., 4G, LTE, 5G, etc.). System 600 may include one or more distributed units (DU1, DU2, ..., DUn) 602 (a, b, ..., n), a service management orchestration (SMO) component 604, and a wireless unit (RU) 606. 【0061】 DU602 may communicate with SMO component 604 and RU606. SMO component 604 may communicate with DU602 and RU606. Two or more DU602s may also communicate with each other, and one of the DU602s (e.g., DU602a) may act and / or function as a host distributed unit and / or primary distributed unit, while one or more other DU602s (e.g., DU602b, ... 602n) may act and / or function as tenant distributed units and / or secondary distributed units and / or shared resource operator distributed units. For the purpose of configuring carrier access control in RU606 (e.g., which carriers in RU606 are managed by which NETCONF client (i.e., DU602)), in some exemplary implementations, one or more DU602s may be grouped into one or more groups (e.g., host DU, tenant DU, user-specific DU, etc.). After the distributed units have been grouped, a carrier access control configuration procedure may be performed. 【0062】 Figure 7 shows an exemplary method 700 for performing a carrier access control configuration procedure for several implementations of the protected object. Process 700 may be performed using the system 600 shown in Figure 6. In particular, process 700 may be performed using RU606, SMO component 604, host DU602a, and two tenants DU602b and 602c. 【0063】 In 702, physical network function (PNF) procedures may be performed by RU606 and SMO component 604. In particular, SMO component 604 may perform configuration of RU606 using access management capabilities (for example, using ietf-netconf-acm.yang), thereby creating configuration mappings. One or more NETCONF access control model (NACM) containers may be used to generate the configuration mappings. NACM containers may be used to configure host DU602a and tenants DU602b, 602c, etc. 【0064】 For the configuration of the host DU602a, one or more NACM containers may include indications for one or more rule lists. The rule lists may specify that the DU602a is the host DU. Furthermore, rules may specify (as done in 704) write access paths to one or more data nodes (for example, specified using the XPath data model) that can point to one or more transmit array carriers (e.g., tx array carriers) and / or receive array carriers (e.g., rx array carriers) of the carrier controlled by the host DU602a. 【0065】 Similarly, for the configuration of each tenant DU602b, 602c, etc., one or more NACM containers may include indications of one or more rule lists that can specify that a particular DU602b, 602c, etc. is a tenant DU (for example, each tenant DU may be associated with a specific container and its own set of rules). Similarly, rules may specify (as done in 704) write access paths to one or more data nodes (for example, specified using an XPath data model) that can point to one or more transmit array carriers (for example, tx array carriers) and / or receive array carriers (for example, rx array carriers) of the carriers controlled by each tenant DU602b, 602c, etc. 【0066】 The SMO component 704 may also send a "NETCONF edit-config client info" message to configure the RU606 using the configured client (e.g., DU602) information. This information may include various details, such as the management plane Internet Protocol (IP) address and / or fully qualified domain name (FQDN) of each DU602 to which the RU606 needs to connect. 【0067】 After RU606 receives this information, RU606 may send a NETCONF CALLHOME message to each of DU602a, 602b, and 602c (and / or any other DU602 that may already be configured). In response, each DU602(a,b,c) may configure its respective transmit and receive array carriers and send a carrier configuration message to RU606. 【0068】 Once the carrier settings for each DU602 are configured in RU606, the NETCONF connectivity monitoring procedure can be enabled for each DU602. Figure 8 shows an exemplary method 800 for performing monitoring failure monitoring in several implementations of the protected object. Process 800 may be executed by the system 600 shown in Figure 6, and may be executed after the configuration procedure described above shown in Figure 7. 【0069】 In 802, each DU602 may subscribe to monitoring notifications in order to enable the monitoring procedure. After the monitoring notifications have been subscribed to, in 804, RU606 may activate and / or operate one or more timers (e.g., notification timer, monitoring timer, etc.) for each DU602. 【0070】 A timer may be used to support bidirectional monitoring of NETCONF connectivity. The notification timer may be set to a value that corresponds to the monitoring notification period (for example, a period with a default value of 60 seconds). To use the notification timer, the RU606 may send one or more monitoring notifications to the NETCONF client (e.g., DU602) that has subscribed to receive such notifications. The RU606 may send such monitoring notifications when the notification period has elapsed. By receiving the monitoring notifications, the controller (e.g., processor) component of the RU606 may confirm that the NETCONF connectivity to the RU606 is functional. 【0071】 The monitoring timer may use a value that corresponds to the sum of the monitoring notification period (for example, a period with a default value of 60 seconds) and the protection timer overdue period (for example, a period with a default value of 10 seconds). In this case, RU606 may identify one or more monitoring failure behaviors when the sum of the periods has elapsed. To avoid the monitoring timer expiring, a NETCONF client (for example, DU602) that has subscribed to receive monitoring notifications may repeatedly reset the monitoring timer. Such resets of the monitoring timer can be considered by RU606 as confirmation that the NETCONF connectivity to the RU606's controller components is in a functional state. 【0072】 In some implementations, the protected object may be configured to extend the monitoring failure handling process and the monitoring termination handling process. For example, such an extension process may be implemented if the sharing of RU606 by multiple DU602s is not supported by RU606, and / or if a NETCONF session failure occurs for a group of NETCONF clients (e.g., DU602) other than host DU602a and / or any tenant DU602b, 602c. 【0073】 If RU606 detects a monitoring failure at 806, RU606 may immediately disable one or more of the above timer operations for the corresponding NETCONF session at 808. RU606 may then assume that the NETCONF session relating to the faulty monitoring is no longer valid. At 810, RU606 may terminate the invalid NETCONF session by closing one or more Secure Shell Protocol (SSH) and / or Transport Layer Security (TLS) connections used as the basis for the session. RU606 may also initiate a call-home procedure for the NETCONF client (e.g., DU602), using the re-call-home-no-ssh-timer to repeatedly attempt to call home. The call-home procedure may be repeated by RU606 until a new NETCONF session is established by the original NETCONF client (e.g., DU602), and / or the original NETCONF client (e.g., DU602) no longer corresponds to a known controller of RU606. This may be done when re-running the Dynamic Host Configuration Protocol (DHCP) configuration if the controller identity of the RU606 corresponding to the NETCONF client (e.g., DU602) is no longer signaled by the DHCP server, and / or if the NETCONF client (e.g., DU602) was previously configured using the configured-client-info container and this configuration has been removed. 【0074】 Furthermore, even after entering monitoring failure handling mode, there may still be at least one running and / or valid NETCONF session between RU606 and a NETCONF client (e.g., DU602) (which may have already subscribed to receive monitoring notifications). In this case, RU606 may remain operational and perform periodic call-home operations to known controllers. Alternatively, or in addition to the above, after entering monitoring failure handling mode, there may be no running NETCONF sessions between RU606 and any NETCONF client (e.g., DU602) (which may have already subscribed to receive monitoring notifications). In this case, RU606 may voluntarily perform a reset by ceasing all radio transmissions. 【0075】 In some implementations, the RU606 supports sharing a RU606 by multiple DU602s, and if a faulty NETCONF session is associated with host DU602a and / or tenant DU602b, 602c, etc., after entering fault monitoring, at 812, the RU606 may stop one or more radio transmissions of transmit array carriers and / or receive array carriers (e.g., tx array carrier, rx array carrier) that can be controlled by the faulty DU602 (e.g., host DU602a, tenant DU602b, 602c). 【0076】 Subsequently, RU606 may notify 814 of a NETCONF session in which the SMO component 604 is faulty. For example, the notification may be sent using an alarm and / or any other trigger, alert, etc., which may include one or more faulty identifiers (e.g., fault-id). 【0077】 At 816, the SMO component 604 may re-provision RU606 using the information of DU602 contained in the configured client (e.g., DU602) information. After RU606 receives the reconfigured configured client information, at 818, RU606 may perform the NETCONF callhome procedure by sending a NETCONF callhome message to DU602. Subsequently, at 820, DU602 may reconfigure the transmit array carrier and / or receive array carrier (e.g., the tx array carrier and the rx array carrier) that can be controlled by DU602 using the information in the received message. Subsequently, at 822, RU606 may begin RF transmission on those carriers. 【0078】 In some implementations, the protected object can be configured to be implemented in system 900, as shown in Figure 9. System 900 may include one or more of the following: a processor 910, memory 920, storage device 930, and input / output device 940. Each of the components 910, 920, 930, and 940 can be interconnected using the system bus 950. The processor 910 can be configured to process instructions to be executed within system 600. In some implementations, the processor 910 can be a single-threaded processor. In other implementations, the processor 910 can be a multi-threaded processor. The processor 910 can be further configured to process instructions stored in memory 920 or storage device 930 (including receiving and sending information through the input / output device 940). Memory 920 can store information within system 900. In some implementations, memory 920 can be a computer-readable medium. In other implementations, memory 920 can be a volatile memory unit. In yet another set of implementations, memory 920 can be a non-volatile memory unit. The storage device 930 may have the capability to provide large-capacity storage to the system 900. In some implementations, the storage device 930 may be a computer-readable medium. In other implementations, the storage device 930 may be a floppy disk device, a hard disk device, an optical disk device, a tape device, non-volatile solid-state memory, or any other type of storage device. The input / output device 940 may be configured to provide input / output operation to the system 900. In some implementations, the input / output device 940 may include a keyboard and / or a pointing device. In other implementations, the input / output device 940 may include a display device for displaying a graphical user interface. 【0079】 Figure 10 shows an exemplary method 1000 for configuring and / or monitoring one or more communication devices (e.g., wireless units, distributed units) of a wireless communication system, relating to several implementations of the protected subject. Method 1000 may be performed using one or more components of the systems shown in Figures 6-7, which perform one or more functions shown in Figure 8. 【0080】 In 1002, a plurality of first communication devices (for example, DU602 shown in Figure 6) may be grouped into a plurality of groups (for example, host DU602a, tenant DU602b...602n, etc.). Each of the plurality of groups may be associated with a second communication device of the wireless communication system (for example, RU606 shown in Figure 6). In 1004, the second communication device (for example, RU606) may be configured to communicate with one or more groups of the first communication devices (for example, host DU602a, tenant DU602b...602n, etc.) (it may be configured as described above with respect to Figure 7). In 1006, one or more pieces of communication information may be transmitted in the wireless communication system using the configured second communication device. 【0081】 In some implementations, the protected object may include one or more of the following optionally selectable features: Each of the multiple first communication devices may be a distributed unit; the second communication device may be a wireless unit. 【0082】 In some implementations, one or more of the multiple first communication devices may include a host first communication device, and one or more of the multiple first communication devices may be the first communication device of a shared resource operator. Each host first communication device of one or more first communication devices may be grouped into one or more host groups of multiple groups. Each first communication device of a shared resource operator of another one or more first communication devices may be grouped into one or more shared resource operator groups of multiple groups. 【0083】 In some implementations, method 1000 may further include detecting a failure in a first communication device that is a host, and terminating communication with the faulty first communication device that is a host. This communication may be related to a default carrier controlled by the faulty first communication device that is a host. In some implementations, configuring a second communication device may include reconfiguring it to communicate with one or more other groups of the first communication device based on the detection of a failure in the first communication device that is a host. This reconfiguration may be performed using the service management orchestration function of the wireless communication system. Furthermore, this reconfiguration may be performed on the management plane. 【0084】 In some implementations, method 1000 may also include sending a call home command to one or more other groups of the first communication devices and receiving one or more carrier settings from one or more other groups of the first communication devices in response to the call home command. The carrier settings may be set by one or more other groups of the first communication devices. One or more carrier settings may include at least one of one or more transmit array carrier settings and one or more receive array carrier settings. The transmission of one or more communication information in a wireless communication system may include transmitting one or more communication information using one or more carrier settings. 【0085】 In some implementations, at least one of grouping, configuration, and transmission may be performed by at least one base station of the wireless communication system. The base station may include at least one of a base station, an eNodeB base station, a gNodeB base station, a radio base station, and any combination thereof. The base station may also be a base station operating in at least one of a Long-Term Evolution communication system, a New Radio communication system, a wireless communication system, and any combination thereof. 【0086】 The systems and methods disclosed herein can be implemented in various forms, including, for example, data processors such as computers, which may also include databases, digital electronic circuits, firmware, software, or combinations thereof. Furthermore, the above-described features and other aspects and principles of the implementations of this disclosure may be implemented in various environments. Such environments and associated applications may be specifically constructed to perform the various processes and operations of the disclosed implementations, or they may include general-purpose computers or computing platforms that are selectively activated or reconfigured by code to provide the necessary functionality. The processes disclosed herein are essentially independent of any particular computer, network, architecture, environment, or other device and can be implemented by a preferred combination of hardware, software, and / or firmware. For example, various general-purpose machines may be used with programs written in accordance with the teachings of the disclosed implementations, or it may be more convenient to construct dedicated devices or systems to perform the required methods and techniques. 【0087】 The systems and methods disclosed herein can be implemented as computer program products, i.e., computer programs tangibly implemented in information carriers, such as machine-readable storage devices or propagating signals, for execution by or control of the operation of data processing devices, such as programmable processors, computers, or multiple computers. Computer programs can be written in any form of programming language, including compiled or interpreted languages, and can be deployed as standalone programs or in any form, including modules, components, subroutines, or other units suitable for use in a computing environment. Computer programs can be deployed to run on a single computer, or on multiple computers distributed across multiple sites and interconnected by a communication network. 【0088】 As used herein, the term "user" may refer to any entity, including a person or a computer. 【0089】 Ordinal numbers such as "1st," "2nd," etc., may be related to order in some contexts, but as used in this document, ordinal numbers do not necessarily imply order. For example, ordinal numbers can be used simply to distinguish one item from another. For instance, distinguishing the first event from the second event does not imply any arbitrary chronological order or fixed reference system (such as the first event in one paragraph of the description being different from the first event in another paragraph of the description). 【0090】 The foregoing description is intended to illustrate, and not to limit, the scope of the invention as defined by the attached claims. Other examples are within the following claims. 【0091】 These computer programs, which may also be referred to as programs, software, software applications, applications, components, or code, contain machine instructions for a programmable processor and may be implemented in high-level procedural and / or object-oriented programming languages, and / or in assembly / machine language. As used herein, the term “machine-readable medium” means any computer program product, apparatus, and / or device, such as magnetic disks, optical disks, memory, and programmable logic devices (PLDs), used to provide machine instructions and / or data to a programmable processor, including machine-readable medium that receives machine instructions as machine-readable signals. The term “machine-readable signals” means any signals used to provide machine instructions and / or data to a programmable processor. Machine-readable medium may store such machine instructions non-temporarily, for example, non-temporarily stored solid-state memory or magnetic hard drives or any equivalent storage medium. Alternatively or additionally, machine-readable medium may store such machine instructions temporarily, for example, a processor cache or other random-access memory associated with one or more physical processor cores. 【0092】 To provide user interaction, the protected object described herein can be implemented on a computer having a display device for displaying information to the user, such as a cathode ray tube (CRT) or liquid crystal display (LCD) monitor, and a keyboard and pointing device, such as a mouse or trackball, to which the user can provide input to the computer. User interaction can also be provided using other types of devices. For example, the feedback provided to the user may be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback, and user input may be received in any form, including, but not limited to, acoustic, verbal, or tactile input. 【0093】 The protected objects described herein may be implemented in a computing system including, for example, one or more backend components such as data servers, or one or more middleware components such as application servers, or one or more frontend components such as one or more client computers having a graphical user interface or a web browser on which a user can interact with an implementation of the protected object described herein, or in any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication, such as a communication network. Examples of communication networks include, but are not limited to, local area networks ("LANs"), wide area networks ("WANs"), and the Internet. 【0094】 A computing system may include clients and servers. Clients and servers are generally, but not exclusively, separate from one another and typically interact via a communication network. The client-server relationship arises from computer programs running on each computer that have a client-server relationship with one another. 【0095】 The examples described above do not necessarily represent all examples that correspond to the subject matter of protection described herein. Rather, they represent only some examples that correspond to embodiments relating to the subject matter of protection described herein. Some modifications have been described in detail above, but other modifications or additions are possible. In particular, further features and / or variations can be provided in addition to those described herein. For example, the examples described above may cover various combinations and partial combinations of the disclosed features, and / or combinations and partial combinations of some of the further features disclosed above. In addition, the logical flows shown in the accompanying drawings and / or described herein do not necessarily require a specific order or sequence shown to achieve the desired result. Other examples may be within the scope of the following claims.

Claims

[Claim 1] This involves grouping multiple first communication devices into multiple groups, and associating each of the multiple groups with a second communication device of a wireless communication system. The aforementioned wireless communication system is a wireless access network, One or more of the plurality of first communication devices is a host first communication device, and one or more of the plurality of first communication devices is a shared resource operator first communication device. Each of the one or more first communication devices that is a host is grouped into one or more host groups from the plurality of groups, and each of the other one or more first communication devices that is a shared resource operator is grouped into one or more shared resource operator groups from the plurality of groups, Configuring the second communication device to communicate with one or more groups of the first communication device, Using the configured second communication device, transmit one or more pieces of communication information in the wireless communication system. To detect a malfunction in the first communication device which is the host, Terminating communication with the malfunctioning host first communication device, wherein the communication is related to a default carrier controlled by the malfunctioning host first communication device. Equipped with, Configuring the second communication device includes reconfiguring it to communicate with one or more other groups of the first communication device based on the detection of the malfunction of the first communication device, which is the host. A method performed by computer. [Claim 2] The method according to claim 1, wherein each of the plurality of first communication devices is a distributed unit. [Claim 3] The method according to claim 2, wherein the second communication device is a wireless unit. [Claim 4] The method according to claim 1, wherein the resetting is performed using the service management orchestration function of the wireless communication system. [Claim 5] The method according to claim 1, wherein the aforementioned resetting is performed on the management plane. [Claim 6] Sending a call home command to one or more other groups of the first communication device, In response to the call home command, the first communication device receives one or more carrier settings from one or more other groups of the first communication device, wherein the one or more carrier settings are set by one or more other groups of the first communication device. The method according to claim 1, further comprising: [Claim 7] The method according to claim 6, wherein the one or more carrier settings include at least one of one or more transmit array carrier settings and one or more receive array carrier settings. [Claim 8] The method according to claim 6, wherein transmitting the one or more pieces of communication information in the wireless communication system includes transmitting the one or more pieces of communication information using the one or more carrier settings. [Claim 9] The method according to claim 1, wherein at least one of the grouping, setting, and transmitting is performed by at least one base station of the wireless communication system. [Claim 10] The method according to claim 9, wherein the base station includes at least one of a base station, an eNodeB base station, a gNodeB base station, a wireless base station, and any combination thereof. [Claim 11] The method according to claim 10, wherein the base station is a base station operating with at least one of a long-term evolution communication system, a new radio communication system, a wireless communication system, and any combination thereof. [Claim 12] At least one processor, When executed by the at least one processor, at least one non-temporary storage medium that stores instructions causing the at least one processor to perform the operation described in any one of claims 1 to 11, and A device equipped with the following features. [Claim 13] At least one non-temporary storage medium that stores instructions causing the at least one processor to perform the operation described in any one of claims 1 to 11, when executed by the at least one processor.

Images