Network node, cloud system, and communication method

Abstract

This network node comprises: a reception unit that receives, from a base station, a spectrum sensing report including an information element relating to a report of frequency usage status and an information element relating to a report of interference; a control unit that determines traffic demand of the base station and satellite interference on the basis of the spectrum sensing report, and sets an information element for requesting resource reservation relating to frequency allocation for interference avoidance; and a transmission unit that transmits the information element for requesting the resource reservation to a cloud system that manages virtual resources.

Description

Network Node, Cloud System, and Communication Method

[0001] The present invention relates to a network node, a cloud system, and a communication method in a communication system.

[0002] In a wireless communication system NR (New Radio) (also referred to as "5G") and a successor system of NR (for example, "6G") based on the 3GPP (registered trademark) standard, as a requirement, technologies that satisfy a large-capacity system, high data transmission speed, low latency, simultaneous connection of a large number of terminals, low cost, power saving, etc. are being studied (for example, Non-Patent Document 1).

[0003] Also, in the O-RAN (Open Radio Access Network) Alliance, managed spectrum sharing (Managed Spectrum Sharing (MSS), which may also be referred to as integrated spectrum sharing) for spectrum bands used in a plurality of existing wireless communication systems (such as aviation, maritime, and satellite) is being studied.

[0004] 3GPP TS 38.300 V18.3.0 (2024-09)

[0005] Wireless spectrum is an essential resource for various wireless communication services. However, conventional spectrum allocation does not necessarily achieve the optimal utilization of the spectrum. In the O-RAN architecture, service management and orchestration (Service Management and Orchestration (SMO)) are responsible for the management of the entire network, and each network element is connected through interfaces such as O1, O2, A1, and E2. In particular, the O2 interface is used to connect between SMO and O-Cloud in the management and control of virtualized network resources.

[0006] However, in the existing specifications of O-RAN, the information exchange and control functions necessary for the realization of MSS (Managed Spectrum Sharing) via the O2 interface are not defined.

[0007] The present invention has been made in view of the above points, and aims to realize information exchange and control functions for resource management in the sharing of spectrum bands used in multiple wireless communication systems via the O2 interface of O-RAN.

[0008] According to the disclosed technology, a network node is provided which includes a receiving unit that receives a spectrum sensing report from a base station, which includes an information element for reporting frequency usage and an information element for reporting interference; a control unit that determines the traffic demand and satellite interference at the base station based on the spectrum sensing report and sets an information element for requesting resource allocation for frequency allocation to avoid interference; and a transmitting unit that transmits the information element for requesting resource allocation to a cloud system that manages virtual resources.

[0009] According to the disclosed technology, information exchange and control functions for resource management in the sharing of spectrum bandwidth used in multiple wireless communication systems can be realized via the O2 interface of O-RAN.

[0010] This figure shows an example configuration of a wireless communication system in an embodiment of the present invention (1). This figure shows an example configuration of a wireless communication system in an embodiment of the present invention (2). This figure shows an example of a logical architecture in O-RAN. This figure illustrates Managed Spectrum Sharing (MSS) being considered in O-RAN. This figure shows an example of SpectrumResourceInformation in an embodiment of the present invention. This figure shows an example of SpectrumAllocationRequest in an embodiment of the present invention. This figure shows an example of a sequence diagram in an embodiment of the present invention. This figure illustrates requestedFrequencyBands in an embodiment of the present invention. This figure shows an example of section type X in an embodiment of the present invention. This figure shows an example of section extension A in an embodiment of the present invention. This figure shows an example of the functional configuration of a base station 10 and a network node 30 in an embodiment of the present invention. This figure shows an example of the functional configuration of a terminal 20 in an embodiment of the present invention. This figure shows an example of the hardware configuration of a base station 10 and a terminal 20 in an embodiment of the present invention. This figure shows an example of the configuration of a vehicle 2001 in an embodiment of the present invention.

[0011] Embodiments of the present invention will be described below with reference to the drawings. Note that the embodiments described below are examples, and the embodiments to which the present invention is applied are not limited to those described below.

[0012] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies may be used as appropriate. However, such existing technologies may include, for example, existing LTE or existing NR, but are not limited to existing LTE or NR.

[0013] Furthermore, in the embodiments of the present invention described below, terms such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel), which are used in existing LTE systems, will be used. This is for convenience of description, and similar signals, functions, etc., may be called by other names. Also, the above terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even if a signal is used in NR, it is not necessarily explicitly stated as "NR-".

[0014] Furthermore, in the embodiments of the present invention, the duplex system may be a TDD (Time Division Duplex) system, an FDD (Frequency Division Duplex) system, or any other system (for example, a Flexible Duplex).

[0015] Furthermore, in embodiments of the present invention, "configuring" wireless parameters means that predetermined values ​​are pre-configured, or that wireless parameters notified from the base station 10 or terminal 20 are configured. Also, in the following description, " / " means "and / or" unless otherwise specified, or unless it is clear from the context that it has a different meaning.

[0016] Figure 1 shows an example configuration (1) of a wireless communication system according to an embodiment of the present invention. The wireless communication system according to an embodiment of the present invention includes a base station 10 and a terminal 20, as shown in Figure 1. Figure 1 shows one base station 10 and one terminal 20, but this is an example, and there may be multiple base stations 10 and terminals 20.

[0017] Base station 10 is a communication device that provides one or more cells and communicates wirelessly with terminal 20. The physical resources of the wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols, and the frequency domain may be defined by the number of subcarriers or resource blocks. Base station 10 transmits synchronization signals and system information to terminal 20. Synchronization signals are, for example, NR-PSS and NR-SSS. System information is transmitted, for example, in NR-PBCH and is also called broadcast information. Synchronization signals and system information may also be called SSB (SS / PBCH block). As shown in Figure 1, base station 10 transmits control signals or data to terminal 20 via DL (Downlink) and receives control signals or data from terminal 20 via UL (Uplink). Both base station 10 and terminal 20 are capable of transmitting and receiving signals using beamforming. Furthermore, both the base station 10 and the terminal 20 can apply MIMO (Multiple Input Multiple Output) communication to DL or UL. Also, both the base station 10 and the terminal 20 may communicate via Carrier Aggregation (CA) through secondary cells (SCell) and primary cells (PCell). Additionally, the terminal 20 may communicate via Dual Connectivity (DC) through the primary cell of base station 10 and the primary secondary cell group cell (PSCell) of another base station 10.

[0018] Terminal 20 is a communication device equipped with wireless communication capabilities, such as a smartphone, mobile phone, tablet, wearable device, or M2M (Machine-to-Machine) communication module. As shown in Figure 1, Terminal 20 receives control signals or data from the base station 10 via DL and transmits control signals or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. Terminal 20 also receives various reference signals transmitted from the base station 10 and performs propagation path quality measurement based on the reception results of said reference signals.

[0019] Furthermore, various requirements are being considered for the next generation of 6G. For example, these requirements may include ultra-broadband communication, mission-critical communication, ultra-massive connection, universal coverage, intelligent connection, and ubiquitous sensing.

[0020] Furthermore, these requirements may include ultra-high-speed communication, large-capacity communication, ultra-wide coverage, ultra-low power consumption, cost reduction, ultra-low latency, ultra-high reliability communication, ultra-high connectivity, and sensing.

[0021] To meet these requirements, the new concept aims for extensibility (e.g., making it more effective for future use), ease of operation, customizability (e.g., making it easier to operate), and sustainability (e.g., cost reduction, a more robust configuration, and resilience). Furthermore, guaranteed communication, ensuring a minimum level of performance at all times, is being considered.

[0022] Figure 2 shows an example configuration (2) of a wireless communication system according to an embodiment of the present invention. Figure 2 shows an example configuration of a wireless communication system when DC (Dual connectivity) is performed. As shown in Figure 2, a base station 10A that will be an MN (Master Node) and a base station 10B that will be an SN (Secondary Node) are provided. Base stations 10A and 10B are each connected to the core network. Terminal 20 can communicate with both base station 10A and base station 10B.

[0023] A cell group provided by base station 10A, which is an MN (Mobile Network), is called an MCG (Master Cell Group), and a cell group provided by base station 10B, which is an SN (Mobile Network), is called an SCG (Secondary Cell Group). In a data center, an MCG consists of one PCell and one or more SCells, and an SCG consists of one PSCell (Primary SCG Cell) and one or more SCells.

[0024] Figure 3 shows an example of the logical architecture in O-RAN. As shown in Figure 3, at base station 10, distributed units (O-DUs) and radio units (O-RUs) are connected via an open fronthaul interface. This interface also transmits and receives control signals, user data, and synchronization signals in the open fronthaul control / user / synchronization plane (Open FH CUS-Plane), and management signals in the open fronthaul management plane (Open FH M-Plane). Furthermore, the Service Management and Orchestration (SMO), which manages and integrates services, communicates with the O-RUs via the Open FH M-Plane, with the O-DUs via the O1 interface, and with the O-Cloud via the O2 interface. Furthermore, the Non-Real Time RIC (RAN Intelligent Controller) in the SMO communicates with the Near-Real Time RIC via the A1 interface. The control plane (O-CU-CP) and user plane (O-CU-UP) of the Central Unit (O-CU) communicate with the O-DU via the F1-c and F1-u interfaces, respectively. The Near-Real Time RIC communicates with the O-DU and O-CU-CP, etc., via the E2 interface. Additionally, the rApp, an application running in the Non-Real Time RIC, performs processing related to network operation and management, while the xApp, running in the Near-Real Time RIC, performs processing related to network optimization.

[0025] O-DU, O-CU, O-RU, SMO, and RIC may be deployed on the same base station, on different base stations, or in different locations other than base stations (nearby, remote, etc.). They may be treated as base station equipment or as network nodes. Furthermore, O-DU and O-CU may be deployed on a virtualization infrastructure and may be denoted as vDU (virtual DU) and vCU (virtual CU), for example.

[0026] The radio spectrum is an essential resource for various wireless communication services. However, traditional spectrum allocations, made by national regulatory authorities based on prevailing market demand, do not always ensure optimal spectrum utilization. Spectrum bands are typically allocated for specific applications, and existing licensed systems with specific technical requirements (e.g., timing, modulation scheme, power level) are deployed within those bands.

[0027] Many existing systems do not achieve optimal spectrum utilization, and opportunities for efficiency improvements exist to share some or all of the bandwidth depending on time, frequency, or geographical conditions. Studies by regulatory authorities in several countries have revealed that there is significant underutilization of the spectrum both in time and space across all licensed network services and all bandwidths of interest.

[0028] Advances in wireless technology have made it possible to sense the wireless environment quickly and precisely, and to respond to changing conditions more rapidly than ever before. This has created an opportunity for multiple systems with different applications and technical requirements to share the same bandwidth based on a Managed Spectrum Sharing (MSS) approach. Figure 4 illustrates Managed Spectrum Sharing (MSS) as being considered in O-RAN. For example, MSS can be applied to manage spectrum usage between existing systems such as maritime, aviation, and satellite systems and cellular systems. Existing systems continue to operate as primary users of their bandwidth, while the latest 5G / 6G (new entrant) systems can improve overall spectrum utilization efficiency and potentially reduce costs compared to conventionally licensed bandwidth.

[0029] (Example) This example describes a method for realizing information exchange and control functions in the sharing of spectrum bandwidth used in multiple wireless communication systems via the O2 interface of O-RAN.

[0030] The existing O2 interface is designed for general resource management on O-Cloud (cloud infrastructure / cloud system) that manages virtual resources, and does not support frequency band information and virtual resource allocation requests that take MSS (Managed Spectrum Sharing) into consideration. This embodiment describes a method that introduces a new data model and enables the exchange of frequency allocation requests and resource utilization status for MSS support via the O2 interface.

[0031] In this embodiment, two new information elements are defined: SpectrumResourceInformation and SpectrumAllocationRequest.

[0032] (New Information Element) SpectrumResourceInformation This is an information element for reporting the frequency band and resource utilization status associated with virtualization resources within O-Cloud. Figure 5 shows an example of SpectrumResourceInformation in an embodiment of the present invention. Figure 5 shows examples of parameter names, definitions, and set values ​​related to the information included in SpectrumResourceInformation.

[0033] allocatedFrequencyBands (List of allocated frequency bands) This shows a list of frequency bands that O-Cloud currently reserves and operates. It shows the reserved frequency bands / bandwidth for frequency bands for which resource allocation has been requested. For example, {3.45–3.46 GHz, 3.48–3.50 GHz} may be set as the configuration value.

[0034] timeConstrains specify the start date and time, end date and time, and validity period (the period reserved for the request) for resource usage. For example, the settings could be: Start date and time: 2025 / 01 / 10 17:30, End date and time: 2025 / 01 / 10 18:30.

[0035] Resource Usage: This section displays information indicating the usage (availability) of virtual resources across O-Cloud, including CPU, memory, storage, and network bandwidth. Settings can include, for example, CPU usage (e.g., 60%), memory usage (e.g., 70%) / amount used (e.g., 8GB), and traffic volume (e.g., 500Mbps).

[0036] ScalingCapabilities indicates the range within which resources can be scaled up or down (e.g., upper and lower limits for CPU and memory scaling). This is useful information when requesting resources (requiredResources). The settings can include, for example, a range encompassing the upper and lower limits for the number of CPU cores (e.g., 2 to 8), and a range encompassing the upper and lower limits for memory (e.g., 4 to 16 GB).

[0037] InterferenceMetrics displays wireless evaluation metrics such as interference level and signal-to-noise ratio (SNIR). For example, the interference level (e.g., 8dB) and the SNIR (e.g., 15dB) can be set as parameters.

[0038] GeographicLocation indicates the geographic location (latitude and longitude, etc.) of the O-Cloud resources. This is used for interference avoidance and latency optimization decisions. For example, latitude (e.g., 35.68) and longitude (e.g., 139.69) can be set as values.

[0039] Energy Consumption: This section displays environmental impact-related information, such as the amount of electricity consumed by O-Cloud resources. A setting value can be configured, for example, the amount of electricity consumed by the resource (e.g., 500 WH).

[0040] Uptime (continuous operating time) indicates the continuous operating time of the resources (CPU, memory, etc.) that make up O-Cloud. It is used for failure prediction and maintenance planning. As a setting value, for example, the operating time (e.g., 72 hours) can be set.

[0041] securityStatus displays security-related information such as security patches and vulnerability information. Possible settings include, for example, whether the patches are up-to-date (e.g., Yes) and the number of vulnerabilities found (e.g., 0).

[0042] The `virtualizationType` parameter indicates the type of virtualization (VM or container, etc.). It is used to determine the optimal resource allocation and operational strategy. For example, the virtualization type might be set to `container-based`.

[0043] In the above-mentioned SpectrumResourceInformation (spectrum resource information), the information regarding resourceUsage (resource usage status) and scalingCapabilites (scaling performance) may be used as reference information when the SMO determines the resources to be requested from the O-Cloud. Also, the O-Cloud may notify the SMO of the said information in advance before receiving a resource reservation request from the SMO. Further, some of the information elements of the said information (for example, interferenceMetrics, geographicLocation, energyConsumption, uptime, securityStatus, and virtualizationType) may not be essential information and may be optional information selectively set as required.

[0044] (New information element) SpectrumAllocationRequest (spectrum allocation request) It is an information element for the SMO to request the O-Cloud for allocation of a specific frequency band or additional virtual resources. FIG. 6 is a diagram showing an example of SpectrumAllocationRequest in an embodiment of the present invention. In FIG. 6, parameter names, definitions, and example setting values regarding the information included in SpectrumAllocationRequest are described.

[0045] requestedFrequencyBands (requested frequency bands) It indicates candidates (multiple possible) for the frequency band or frequency width requested by the SMO from the O-Cloud. The same information is used in the first request, additional requests, and change requests. As a setting value, for example, a candidate for a frequency band of {3.46 to 3.47 GHz} is set.

[0046] requiredResources (required resources) It indicates the virtual resource specifications (such as CPU, memory, and NW bandwidth) to be requested. As a setting value, for example, a CPU of 4 cores, a memory of 8 GB, and a traffic volume of 1 Gbps are set.

[0047] priorityLevel (Requested Priority) Indicates the priority / importance / urgency of the request. It is used by O-Cloud to process requests with higher priority first during contention. As a setting value, for example, Priority (High) is set.

[0048] timeConstraints (Valid Period) Indicates the start date and time, end date and time, and valid period of the requested resource utilization. This enables dynamic scheduling with time limitations. It is also possible to specify only the start date and time without specifying the end date and time. As a setting value, for example, Start Date and Time (2025 / 01 / 10 17:30) and End Date and Time (2025 / 01 / 10 18:30) are set.

[0049] redundancyRequirements (Redundancy Requirements) Indicates the redundancy requirements requested. This makes it possible to ensure the resources necessary for failover in case of a failure. As a setting value, for example, Redundancy Level 2 (two sets of resources with the same specifications) is set.

[0050] qosTargets (QoS Target Values) Indicates QoS target values such as latency / throughput, which serve as a reference when O-Cloud calculates the required resources. As a setting value, for example, Latency of 10 ms or less and Throughput of 5 Mbps or more are set.

[0051] securityConstraints (Security Requirements) Indicates scaling conditions (thresholds / expansion procedures, etc.) related to traffic fluctuations / usage rates. As a setting value, for example, Encryption Method (e.g., TLS1.3) and Security Policy ID (e.g., SEC-1001) are set.

[0052] scalingPolicy (Scaling Policy) Indicates scaling conditions (thresholds / expansion procedures, etc.) related to traffic fluctuations / usage rates. As a setting value, for example, a condition of adding 1 core when the CPU usage rate exceeds 80% is set.

[0053] Environmental targets indicate environmental constraints / target values ​​such as CO2 emission / electricity usage targets. For example, a CO2 emission target (e.g., 100 g / h or less) is set.

[0054] In the SpectrumAllocationRequest information element described above, either requestedFrequencyBands or requiredResources may be set when making a request to O-Cloud. If only requestedFrequencyBands is set, O-Cloud calculates the virtual resources (computational resources) required to process the requested frequency bands. This calculation may be performed, for example, using a mapping table between frequency bands (bandwidth / location, etc.) and virtual resources. Furthermore, the calculation method / mapping table may be defined for each requirement such as qosTargets (QoS target values) / securityConstraints (security requirements). In addition, some of the information in this information element (for example, redundancyRequirements, qosTargets, securityConstraints, scalingPolicy, and environmentalTargets) may not be mandatory information but optional information that can be selectively set as needed.

[0055] (Detailed Procedure Using Sequence Diagrams) The detailed procedure for this embodiment will be described below using sequence diagrams. Figure 7 is a diagram showing an example of a sequence diagram in an embodiment of the present invention. In this sequence diagram, the base station 10 includes one or more O-CU / O-DU / O-RU. The processing of each step will be described below.

[0056] S101: Base station 10 collects information regarding the spectrum utilization status of its own device in real time.

[0057] S102: The base station 10 receives radio waves transmitted from other systems 40, such as satellite communication systems / broadcasting systems, and collects information about the surrounding environment (e.g., received signal strength, interference level).

[0058] S103: The base station 10 transmits a Spectrum Sensing Report (SSR) created based on the information collected in S101 and S102 to the SMO / Non-RT RIC30A. The SSR may include parameters included in section type X shown in Figure 8 and section extension A shown in Figure 9.

[0059] S104: The SMO / Non-RT RIC30A grasps the traffic demand (cellular demand) and satellite interference at base station 10 and determines the time / period when frequency allocation for interference avoidance is necessary. This determination may be performed using an artificial intelligence / machine learning model. For example, the SMO / Non-RT RIC30A may determine that "interference avoidance is necessary from 8:00 to 20:00" based on cellular demand (2Gbps) and satellite interference (3.660-3.670GHz, 15-20dB).

[0060] S105: Based on the result of the decision in S104, the SMO / Non-RT RIC30A sets information elements related to the spectrum allocation request (SpectrumAllocationRequest) and sends the set information elements to the O-Cloud40B. For example, the SMO / Non-RT RIC30A may set requestedFrequencyBands to {3.600 to 3.660, 3.670 to 3.700} as shown in Figure 10. Alternatively, the SMO / Non-RT RIC30A may set requiredThroughput to 2 Gbps, priorityLevel to priority (high), and timeConstraints to 18:00 to 20:00.

[0061] Furthermore, in order to avoid satellite interference and request the allocation of virtual resources, the SMO / Non-RT RIC30A sends configured information elements (SpectrumAllocationRequest) to the O-Cloud40B via the O2 interface.

[0062] S106: O-Cloud40B calculates and allocates the necessary virtual resources based on the information element (SpectrumAllocationRequest) received in S105. Here, O-Cloud40B may perform this calculation by referring to a mapping table that shows the relationship between the frequency band (width / location of the frequency band, etc.) and the virtual resources.

[0063] S107: O-Cloud40B sets the allocatedFrequencyBands parameter of the information element SpectrumResourceInformation (spectrum resource information) based on the virtual resources calculated and secured in S106, according to the information elements received in S105.

[0064] S108: O-Cloud40B may, if necessary, place the containers of resources in the virtual environment calculated and secured in S106 on network nodes with less satellite interference.

[0065] S109: Based on the virtual resources calculated and secured in S106, O-Cloud40B appropriately sets parameters other than allocatedFrequencyBands in the information element SpectrumResourceInformation, and transmits the set information element to SMO / Non-RT RIC30A.

[0066] S110: O-Cloud40B allocates the virtual resources calculated and secured in S106 to the O-DU / O-RU of base station 10.

[0067] S111: The SMO / Non-RT RIC30A instructs base station 10 to execute communication using the reserved virtual resources.

[0068] S112: O-Cloud40B releases any virtual resources that are not needed. For example, based on the timeConstraints (validity period) 18:00 to 20:00 set in the information element (SpectrumAllocationRequest) received in S105, O-Cloud40B releases the virtual resources allocated in S106 after 20:00 has elapsed.

[0069] S113: Based on the result of releasing the virtual resources in S112, O-Cloud40B updates the settings of the information element (SpectrumResourceInformation) and sends the updated information element to SMO / Non-RT RIC30A.

[0070] S114: Based on the information element (Resource Information) received in S112, the SMO / Non-RT RIC30A decides whether to perform normal operations or operations in preparation for future demand forecasts.

[0071] (Effects) The above-described embodiment effectively realizes Integrated Spectrum Sharing (MSS) in the O-RAN architecture, enabling efficient utilization of frequency resources and cloud resources. Furthermore, the expansion of the O2 interface strengthens cooperation between SMO and O-Cloud, enabling resource management and optimization of the entire network. In addition, it is possible to enhance the flexibility and scalability of the network by applying the embodiment to various scenarios.

[0072] In other words, the above embodiment makes it possible to realize information exchange and control functions for resource management in the sharing of spectrum bandwidth used in multiple wireless communication systems via the O2 interface of O-RAN.

[0073] (Device Configuration) Next, an example of the functional configuration of the base station 10, network node 30, and terminal 20 that perform the processing and operations described above will be explained. The base station 10, network node 30, and terminal 20 include the functions to perform the embodiments described above. However, the base station 10, network node 30, and terminal 20 may each have only some of the functions in the embodiments.

[0074] <Base Station 10 and Network Node 30> Figure 11 shows an example of the functional configuration of a base station 10 and a network node 30. As shown in Figure 11, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Figure 11 is merely an example. The functional classifications and names of the functional units can be anything as long as they can perform the operations according to the embodiment of the present invention. The network node 30 may have the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different functions on the system architecture may be composed of multiple network nodes 30 separated by function.

[0075] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 or other network node 30 and transmitting the signal by wire or wireless. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 or other network node 30 and obtaining information from the received signal, for example, information from a higher layer. A communication unit including the transmitting unit 110 and the receiving unit 120 may be configured.

[0076] The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 20 in a storage device, and reads them from the storage device as needed.

[0077] The control unit 140 performs the processing described in the embodiment. The signal transmission function in the control unit 140 may be included in the transmission unit 110, and the signal reception function in the control unit 140 may be included in the reception unit 120.

[0078] <Terminal 20> Figure 12 is a diagram showing an example of the functional configuration of terminal 20. As shown in Figure 12, terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Figure 12 is merely an example. Any functional classification and functional unit names are acceptable as long as they enable the operation according to the embodiment of the present invention. Furthermore, a communication device that acts as a resource holder may have a functional configuration similar to that of terminal 20.

[0079] The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 wirelessly receives various signals and obtains signals from higher layers from the received physical layer signals. The receiving unit 220 also has the function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals or reference signals transmitted from the network node 30. A communication unit including the transmitting unit 210 and the receiving unit 220 may be configured.

[0080] The setting unit 230 stores various setting information received from the network node 30 by the receiving unit 220 in its storage device and reads it from the storage device as needed. The setting unit 230 also stores pre-configured setting information.

[0081] The control unit 240 performs the processing described in the embodiment. The signal transmission function in the control unit 240 may be included in the transmission unit 210, and the signal reception function in the control unit 240 may be included in the reception unit 220.

[0082] (Hardware Configuration) The block diagrams (Figures 11 and 12) used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may be realized by combining the one device or the multiple devices with software.

[0083] Functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0084] For example, the network node 30, terminal 20, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 13 is a diagram showing an example of the hardware configuration of a base station 10 and terminal 20 according to one embodiment of the present disclosure. The network node 30 may have the same hardware configuration as the base station 10. The base station 10 and terminal 20 described above may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0085] In the following explanation, the term "device" can be read as "circuit," "device," "unit," etc. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

[0086] Each function in the base station 10 and terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and storage device 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of data reading and writing in the storage device 1002 and auxiliary storage device 1003.

[0087] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit 140, control unit 240, etc., described above may be implemented by the processor 1001.

[0088] Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 140 of the base station 10 shown in Figure 11 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Also, for example, the control unit 240 of the terminal 20 shown in Figure 12 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above-described processes have been explained as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from the network via a telecommunications line.

[0089] The storage device 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The storage device 1002 may also be called a register, cache, main memory, etc. The storage device 1002 can store executable programs (program code), software modules, etc., for implementing a communication method according to one embodiment of the present disclosure.

[0090] The auxiliary storage device 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital multipurpose disk, a Blu-ray® disk), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The above-mentioned storage medium may also be a database, server, or other suitable medium that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0091] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmitting and receiving antenna, amplifier section, transmitting and receiving section, transmission path interface, etc., may be implemented by the communication device 1004. The transmitting and receiving section may be implemented in a physically or logically separated manner, with a transmitting section and a receiving section.

[0092] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0093] Furthermore, each device, such as the processor 1001 and the storage device 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.

[0094] Furthermore, the base station 10 and terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0095] O-CU may be interpreted as CU, control device, communication device, aggregation device, central device, management device, etc. Each of these devices may be rephrased as a unit, node, etc. For example, O-CU may be interpreted as a central unit, aggregation node, etc.

[0096] O-DU may be interpreted as DU, control device, communication device, distributed device, high-PHY device, etc. Each of these devices may be rephrased as unit, node, etc. For example, O-DU may be interpreted as distributed unit, distributed node, etc.

[0097] O-RU may be interpreted as RU, radio equipment, RF (Radio Frequency) equipment, low PHY equipment, etc. Each piece of equipment may be rephrased as a unit, node, etc. For example, O-RU may be interpreted as a radio unit, radio node, etc.

[0098] SMO may be interpreted as a control device, communication device, or management device. Each of these devices may be rephrased as a unit, node, etc. For example, SMO may be interpreted as a management unit, management node, etc.

[0099] Non-Real Time RIC may be interpreted as RIC, non-real-time control device, control device, or communication device. Each of these devices may be rephrased as a unit, node, etc. For example, Non-Real Time RIC may be interpreted as a control unit, control node, etc.

[0100] Near-Real Time RIC may be interpreted as RIC, quasi-real-time control device, control device, or communication device. Each of these devices may be rephrased as a unit, node, etc. For example, Non-Real Time RIC may be interpreted as a control unit, control node, etc.

[0101] Figure 14 shows an example of the configuration of vehicle 2001. As shown in Figure 14, vehicle 2001 includes an operating unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in this disclosure may be applied to a communication device mounted on vehicle 2001, for example, to the communication module 2013.

[0102] The operating unit 2002 consists of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel, which is operated by the user.

[0103] The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (IO ports) 2033. Signals from various sensors 2021 to 2029 installed in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0104] Signals from various sensors 2021 to 2029 include current signals from current sensor 2021 for sensing motor current, front and rear wheel rotation speed signals acquired by rotation speed sensor 2022, front and rear wheel air pressure signals acquired by air pressure sensor 2023, vehicle speed signals acquired by vehicle speed sensor 2024, acceleration signals acquired by acceleration sensor 2025, accelerator pedal depression signals acquired by accelerator pedal sensor 2029, brake pedal depression signals acquired by brake pedal sensor 2026, shift lever operation signals acquired by shift lever sensor 2027, and detection signals acquired by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0105] The Information Service Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Service Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001. The Information Service Unit 2012 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) and output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

[0106] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

[0107] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via its communication port. For example, the communication module 2013 sends and receives data via the communication port 2033 between the moving parts 2002, steering parts 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021-29 provided in the vehicle 2001.

[0108] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, it can send and receive various types of information with external devices via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station or a mobile station.

[0109] The communication module 2013 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 2012. The electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include the information based on the above input.

[0110] The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit, which outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from the external device in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the operating unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc., provided in the vehicle 2001.

[0111] <Notes> (Note 1) A network node having: a receiving unit that receives from a base station information elements regarding frequency usage status reports, information elements regarding interference reports, and a spectrum sensing report including these; a control unit that determines the traffic demand and satellite interference at the base station based on the spectrum sensing report and sets information elements requesting resource allocation for interference avoidance; and a transmitting unit that transmits the information elements requesting resource allocation to a cloud system that manages virtual resources. (Note 2) The network node according to Note 1, wherein the receiving unit receives information elements regarding the resource allocation report from the cloud system. (Note 3) A cloud system having: a receiving unit that receives from a network node that performs service management and orchestration information elements requesting resource allocation for interference avoidance; a control unit that secures resources based on the information elements requesting resource allocation; and a transmitting unit that transmits information elements regarding the resource allocation report to the network node. (Appendix 4) The cloud system according to Appendix 3, wherein the control unit releases the secured resources after the validity period set in the information element requesting resource allocation has elapsed, and the transmission unit transmits an information element regarding the release. (Appendix 5) A communication method performed by a network node, comprising: receiving a spectrum sensing report from a base station, which includes an information element regarding a frequency usage status report and an information element regarding an interference report; determining the traffic demand and satellite interference at the base station based on the spectrum sensing report, and setting an information element requesting resource allocation for interference avoidance; and transmitting the information element requesting resource allocation to a cloud system that manages virtual resources.

[0112] By any of the provisions of Appendix 1 to Appendix 5, it is possible to realize information exchange and control functions for resource management in the sharing of spectrum bandwidth used in multiple wireless communication systems via the O2 interface of O-RAN.

[0113] (Supplement to Embodiments) Embodiments of the present invention have been described above, but the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. The processing procedures described in the embodiments may be rearranged as long as they do not contradict each other. For the convenience of explaining the processing, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized in hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to an embodiment of the present invention and the software operated by the processor of the terminal 20 according to an embodiment of the present invention may be stored in any suitable storage medium such as random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or other appropriate storage medium.

[0114] Furthermore, notification of information is not limited to the embodiments described herein and may be carried out by other means. For example, notification of information may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or combinations thereof. Also, RRC signaling may be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0115] Each aspect / embodiment described in this disclosure refers to LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20 may apply to at least one system utilizing UWB (Ultra-WideBand), Bluetooth®, or other appropriate systems, and to next-generation systems extended, modified, created, or defined based thereon. Alternatively, multiple systems may be applied in combination (e.g., a combination of at least one of LTE and LTE-A with 5G).

[0116] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order.

[0117] In this specification, specific operations performed by the base station 10 may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station 10, it is clear that various operations performed for communication with the terminal 20 can be performed by the base station 10 and at least one of the other network nodes (for example, an MME or S-GW, but not limited to these). Although the above example illustrates the case where there is one other network node besides the base station 10, the other network node may be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0118] The information or signals described in this disclosure may be output from a higher layer (or lower layer) to a lower layer (or higher layer). They may also be input and output via multiple network nodes.

[0119] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

[0120] The determination in this disclosure may be made by a value represented by one bit (0 or 1), by a Boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0121] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0122] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0123] The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0124] In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0125] The terms “system” and “network” as used in this disclosure are interchangeable.

[0126] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index.

[0127] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0128] In this disclosure, terms such as "Base Station (BS)", "wireless base station", "base station equipment", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0129] A base station can accommodate one or more (e.g., three) cells. If a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0130] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform control or operation based on the information.

[0131] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0132] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or several other appropriate terms.

[0133] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes the case when the mobile body is stationary. The mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and items mounted on them. The mobile body may also be a mobile body that moves autonomously based on operation commands. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station may include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0134] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the terminals 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel.

[0135] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station may be configured to have the same functions as the user terminal described above.

[0136] As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching in a table, database, or other data structure), or ascertaining. “Determining” may also include receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, or accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0137] The terms “connected,” “coupled,” or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0138] The reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applicable standard.

[0139] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0140] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way.

[0141] In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc.

[0142] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0143] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0144] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0145] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0146] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

[0147] 10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 230 Setting unit 240 Control unit 30 Network node 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device

Claims

1. A network node comprising: a receiving unit that receives a spectrum sensing report from a base station, which includes information elements related to frequency usage reports and information elements related to interference reports; a control unit that determines the traffic demand and satellite interference at the base station based on the spectrum sensing report and sets information elements requesting resource allocation for interference avoidance; and a transmitting unit that transmits the information elements requesting resource allocation to a cloud system that manages virtual resources.

2. The network node according to claim 1, wherein the receiving unit receives information elements related to the resource allocation report from the cloud system.

3. A cloud system comprising: a receiving unit that receives information elements requesting resource allocation for interference avoidance from network nodes that perform service management and orchestration; a control unit that secures resources based on the information elements requesting resource allocation; and a transmitting unit that transmits information elements related to the reporting of resource allocation to the network nodes.

4. The cloud system according to claim 3, wherein the control unit releases the secured resources after the validity period set in the information element requesting resource allocation has elapsed, and the transmission unit transmits an information element reporting the release.

5. A communication method performed by a network node, comprising: receiving a spectrum sensing report from a base station, which includes an information element for reporting frequency usage and an information element for reporting interference; determining the traffic demand and satellite interference at the base station based on the spectrum sensing report, and setting an information element for requesting resource allocation for frequency allocation to avoid interference; and transmitting the information element for requesting resource allocation to a cloud system that manages virtual resources.

Images