Network node and communication method

Abstract

This network node comprises: a reception unit that receives, from a central unit or a distributed unit of each of a plurality of base stations, 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, on the basis of a table in which a plurality of spectrum sensing reports are integrated, determines an instruction for frequency allocation for each of the plurality of base stations in a frequency band shared by a plurality of wireless systems; and a transmission unit that transmits the determined instruction for frequency allocation to the central unit or the distributed unit of each of the plurality of base stations.

Description

Network Node and Communication Method

[0001] The present invention relates to a network node 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 requirements, 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] Further, in the O-RAN (Open Radio Access Network) Alliance, managed spectrum sharing (Managed Spectrum Sharing (MSS)) for spectrum bands used in a plurality of existing wireless communication systems (such as aviation, maritime, and satellite) is being studied. Also, with the latest wireless technologies such as 5G and 6G, real-time spectrum sharing between different systems becomes possible, and the importance of orchestration based on the O-RAN architecture is increasing further.

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

[0005] The radio spectrum is an indispensable resource for various wireless communication services. However, the conventional spectrum allocation does not necessarily achieve the optimal utilization of the spectrum. Also, an orchestration mechanism for the entire network regarding the sharing of spectrum bands is not defined.

[0006] The present invention has been made in view of the above points, and an object thereof is to provide an orchestration mechanism for sharing spectrum bands used in a plurality of wireless communication systems.

[0007] According to the disclosed technology, a network node is provided having a receiving unit that receives spectrum sensing reports including information elements for frequency utilization reports and information elements for interference reports from a central or distributed unit of a plurality of base stations; a control unit that determines instructions for frequency allocation for each of the plurality of base stations in a frequency band shared by a plurality of wireless systems based on a table integrating the plurality of spectrum sensing reports; and a transmitting unit that transmits the determined frequency allocation instructions to the central or distributed unit of the plurality of base stations.

[0008] The disclosed technology can provide an orchestration mechanism for sharing spectrum bands used in multiple wireless communication systems.

[0009] 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 section type X in an embodiment of the present invention. This figure shows an example of section type Y 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 section extension B in an embodiment of the present invention. This figure shows the configuration of a base station in scenario 1 in an embodiment of the present invention. This figure shows an example of a sequence diagram for scenario 1 in an embodiment of the present invention. This figure illustrates integrated analysis in an embodiment of the present invention. This figure shows an example of the configuration of a base station in scenarios 2 and 3 in an embodiment of the present invention. This figure shows an example of a sequence diagram for scenario 2 in an embodiment of the present invention. This figure shows an example of a sequence diagram for scenario 3 in an embodiment of the present invention. This figure shows an example of SpectrumSensingData in an embodiment of the present invention. This figure shows an example of an InterferenceReport in an embodiment of the present invention. This figure shows the configuration of a base station in an embodiment of the present invention. This figure shows an example of a sequence diagram for scenario 4-1 in an embodiment of the present invention. This figure shows an example of an SSR integrated table in an embodiment of the present invention. This figure illustrates the operation of guard band and adjacent band management in an embodiment of the present invention. This figure shows an example of a SpectrumAssignmentPolicy in an embodiment of the present invention. This figure shows an example of a sequence diagram for scenario 4-2 in an embodiment of the present invention. This figure shows an example of the functional configuration of the base station 10 and network node 30 in an embodiment of the present invention. This figure shows an example of the functional configuration of the terminal 20 in an embodiment of the present invention. This figure shows an example of the hardware configuration of the base station 10 and terminal 20 in an embodiment of the present invention. This figure shows an example of the configuration of the vehicle 2001 in an embodiment of the present invention.

[0010] 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.

[0011] 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 be, for example, existing LTE or existing NR, but are not limited to existing LTE or NR.

[0012] 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-".

[0013] 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).

[0014] 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.

[0015] 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.

[0016] 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.

[0017] 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.

[0018] 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.

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

[0020] 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.

[0021] 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.

[0022] 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.

[0023] 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.

[0024] 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.

[0025] 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.

[0026] 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.

[0027] 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.

[0028] (Example 1) This example describes a method for sharing and using spectrum bands used by multiple wireless communication systems. This example extends the open fronthaul specification of O-RAN and enables managed spectrum sharing (MSS). It also enables efficient sharing of frequency bands between different radio frequency (RF) systems, which is expected to lead to effective use of limited frequency resources. Furthermore, through MSS, it is possible to integrate and coordinate multiple types of network access technologies, including licensed and unlicensed spectra, achieve efficient spectrum utilization, seamless connectivity, and improve the user experience.

[0029] The existing O-RAN open fronthaul specification does not adequately consider the exchange of information regarding spectrum sharing in communication between O-DU and O-RU. To address this, for example, the O-RU can detect radio waves from other systems and report the detection results to the O-DU. The O-DU then analyzes the detection results and issues frequency usage instructions to the O-RU. Note that O-CU, RIC, SMO, etc., may be used instead of the O-DU.

[0030] Furthermore, the following new section types may be defined as message formats used between the fronthaul interface between the O-DU and O-RU to exchange spectrum sensing information / spectrum utilization instructions, etc.: • Section Type X: Used to transmit a Spectrum Sensing Report (SSR) from the O-RU to the O-DU. Figure 5 shows an example of Section Type X in an embodiment of the present invention. • Section Type Y: Used to transmit a Spectrum Utilization Assignment (SUA) from the O-DU to the O-RU. Figure 6 shows an example of Section Type Y in an embodiment of the present invention.

[0031] In addition, section extensions may be defined to transmit detailed information in conjunction with the above-mentioned section types X and Y. • Section extension type A: Used to provide detailed information on spectrum sensing. Figure 7 shows an example of section extension A in an embodiment of the present invention. • Section extension type B: Used to provide additional control information regarding spectrum utilization instructions. Figure 8 shows an example of section extension B in an embodiment of the present invention.

[0032] (Example of specification change) This section describes an example of a specification change for an existing O-RAN fronthaul interface.

[0033] Newly defined section types (X, Y) / section extensions (A, B) may be added to the existing O-RAN fronthaul control plane (C-Plane) protocol.

[0034] A new message type format may be defined, and the data type and encoding scheme for each field may be defined.

[0035] In the management plane (M-Plane), new parameters (for example, a flag to enable the MSS function) may be configurable.

[0036] (Example 1-1) Spectrum Sharing in an O-RAN System Example 1-1 describes a method for extending the O-RAN Open Fronthaul specification and introducing new section types and section extensions for exchanging information on spectrum sharing between O-DUs (O-RAN Distributed Units) and O-RUs (O-RAN Radio Units).

[0037] (Method 1) Defining new section types: Define section type X (Spectrum Sensing Report (SSR)) for the O-RU to sense the surrounding spectrum environment and report the detection results to the O-DU, and section type Y (Spectrum Utilization Assignment (SUA)) for the O-DU to instruct the O-RU on how to utilize the spectrum.

[0038] (Method 2) Defining new section extensions Define section extension type A for providing detailed information on spectrum sensing (e.g., sensed frequency band, signal strength, interference level, etc.) and section extension type B for providing additional control information regarding spectrum usage instructions (e.g., specified frequency band, allowable output level, usage period, etc.).

[0039] (Method 3) Operation Procedure Step 1: Spectrum Sensing The O-RU may sense the ambient spectrum conditions in real time and generate a Spectrum Sensing Report (SSR).

[0040] Step 2: Sending the SSR The O-RU may send the SSR to the O-DU using section type X and section extension type A.

[0041] Step 3: Analysis and Decision-Making The O-DU may analyze the received SSR and create a Spectrum Use Instruction (SUA). Alternatively, an external node such as SMO / RIC / O-CU may perform this task on behalf of the O-DU.

[0042] Step 4: Sending the SUA The O-DU may send the SUA to the O-RU using section type Y and section extension type B.

[0043] Step 5: Operation Adjustment The O-RU may adjust its operating parameters, such as frequency bandwidth / transmit power, according to the received SUA.

[0044] (Example regarding SSR reception and SUA determination) (SSR reception) The O-RU (radio unit for cellular systems) may transmit an SSR (section type X and section extension A) to the O-DU, which contains the following information obtained by real-time spectrum sensing: • Frequency band: Strong interference detected around 3.660 GHz • Interference source: Estimated to be from a satellite system (matches known satellite uplink / downlink frequency bands) • Interference intensity: Approximately 10 dB • RB range in use (example): Corresponds to around RB#200 to RB#210 (Analysis in the O-DU) Based on the information obtained from the SSR, the O-DU may create an SUA, taking into account the following information. - Guidelines for coexistence with satellite systems (pre-configured policies or information obtained from SMO / RIC / O-CU) - Frequency bands used by satellites that need to be avoided (3.650 GHz to 3.680 GHz band) - Unoccupied frequency bands (e.g., no interference reports around 3.600 to 3.620 GHz) - Priority / quality of service (e.g., allocate stable bandwidth to emergency communications and high-priority services) - Geographical / time restrictions (e.g., consider the relevant region / time zone) (SUA creation) The O-DU may decide the following information to include in the SUA (Section Type Y and Section Extension B):・AllowedFrequencyBands: Regions with less satellite interference (e.g., 3.600 - 3.620 GHz) ・AllowedRBs: RB range corresponding to the applicable frequency band (AllowedFrequencyBands) (e.g., RB#220 - RB#230) ・PowerLimitations: Maximum transmission power (e.g., 15 dBm) ・PriorityLevel: Priority (e.g., high priority (level 1, when there is important communication in the cellular system)) ・FrequencyHoppingPattern: Frequency hopping pattern (e.g., hopping between 3.600 GHz and 3.6005 GHz every 20 ms to ensure stable operation) ・InterferenceTolerance: Interference tolerance (e.g., 5 dB, re-evaluation by SSR if it exceeds 5 dB) ・TimeRestrictions: Available time ・GeographicalRestrictions: Available area (SUA transmission) The O-DU may transmit the created SUA to the O-RU. The O-RU provides stable cellular communication using frequencies sufficiently separated from the satellite interference band according to the SUA.

[0045] (Example 1 - 2) Cooperative spectrum sharing among multiple nodes In Example 1 - 2, a method is described in which multiple O-RUs transmit SSRs to the O-DUs they are connected to and optimize spectrum sharing cooperatively via O-DUs or external nodes such as O-CU, SMO, and RIC. Also, in Example 2, for the realization of MSS (Managed Spectrum Sharing), in addition to the aforementioned section types X / Y and section extensions A / B, a newly defined section extension G including identification information / management information required for cooperation may be used.

[0046] Next, Scenario 1 regarding cooperation via one O-DU, Scenario 2 regarding cooperation among multiple O-DUs, and Scenario 3 regarding cooperation via O-CU will be described using sequence diagrams. Each scenario may be executed in combination.

[0047] (Scenario 1) Cooperative Diagram via One O-DU FIG. 9 is a diagram showing an example of the configuration of a base station in Scenario 1 in an embodiment of the present invention. In the base station of Scenario 1, for example, as shown in FIG. 9, an O-DU 10B is deployed under an O-CU 10A, and an O-RU 10C and an O-RU 10C2 are deployed under the O-DU 10B.

[0048] FIG. 10 is a diagram showing an example of a sequence diagram of Scenario 1 in an embodiment of the present invention. Hereinafter, the processing of each step will be described.

[0049] S101: The O-RU 10C2 collects information on the spectrum utilization status in its own device in real time.

[0050] S102: The O-RU 10C2 receives radio waves transmitted from another system 40 such as a satellite communication system / broadcast system, and collects information on the surrounding environment (for example, received signal strength, interference level).

[0051] S103: Based on the information collected in S101 and S102, the O-RU 10C2 creates a spectrum sensing report (Spectrum Sensing Report (SSR)) including section type X / section extension type {A / G}. Further, the O-RU 10C2 transmits the created SSR to the O-DU 10B.

[0052] S104: The O-RU 10C collects information on the spectrum utilization status in its own device in real time.

[0053] S105: The O-RU 10C receives radio waves transmitted from another system 40 such as a satellite communication system / broadcast system, and collects information on the surrounding environment (for example, received signal strength, interference level).

[0054] S106: Based on the information collected in S104 and S105, the O-RU 10C creates a spectrum sensing report (Spectrum Sensing Report (SSR)) including section type X and section extension type A / G. Further, the O-RU 10C transmits the created SSR to the O-DU 10B.

[0055] S107: O-DU10B integrates and analyzes the spectrum sensing reports (SSRs) received in S103 and S106. O-DU10B may, for example, determine scheduling instructions for O-RU10C and O-RU10C2 based on the analysis results. Here, an example of integrated analysis will be explained using Figure 11. Figure 11 is a diagram illustrating integrated analysis in an embodiment of the present invention.

[0056] As a prerequisite, assume that the satellite gateway is occupying the 3.650 to 3.680 GHz band within the 3.6 to 3.7 GHz frequency band, which is available for shared use by multiple wireless systems.

[0057] The O-RU10C detects 30 dB interference (very strong) around 3.660 GHz, while the O-RU10C2 detects 10 dB interference (somewhat mild) around 3.660 GHz.

[0058] O-DU10B performs the following integrated analysis based on the SUR from O-RU10C and O-RU10C2.

[0059] For O-RU10C, due to strong interference, the frequency will be shifted significantly further down than the satellite band (3.600–3.620 GHz) to secure a 30 MHz guard band from the satellite GW band. At this time, the transmit power will be limited to about 10 dBm, and the Interference Tolerance will be set to a strict value of 5 dB so that it can be immediately reassigned if re-interference occurs.

[0060] For O-RU10C2, since the interference is minor, a small shift to 3.620-3.640 GHz is sufficient, and a 10 MHz guard band will be secured from the satellite GW band. The transmit power will be set at 15 dBm and the interference tolerance at approximately 10 dB, with the policy being to tolerate minor interference.

[0061] O-RU10C and O-RU10C2 receive instructions (scheduling) regarding frequency allocation without frequency overlap from a single O-DU (O-DU10B) using SUA. Here, the SUA includes, for example, the following information: ・SUA for O-RU10C: AllowedFrequencyBands=3.600–3.620 GHz, Power=10 dBm, InterferenceTolerance=5 dB ・SUA for O-RU10C2: AllowedFrequencyBands=3.620–3.640 GHz, Power=15 dBm, InterferenceTolerance=10 dB Let's return to Figure 10 for further explanation.

[0062] S108: O-DU10B creates a Spectrum Use Instruction (SUA) to send to O-RU10C and O-RU10C2 based on the results of the analysis performed in S106. The SUA may include section type Y / section extension B.

[0063] S109: O-DU10B transmits the spectrum usage instruction (SUA) created in S108 to O-RU10C.

[0064] S110: O-RU10C may adjust operating parameters such as frequency band and transmit power based on the SUA received in S109.

[0065] S111: O-DU10B transmits the spectrum usage instruction (SUA) created in S108 to O-RU10C2.

[0066] S112: O-RU10C2 may adjust operating parameters such as frequency bandwidth and transmit power based on the SUA received in S111.

[0067] Following the procedure described above, an O-RU can consider spectrum sensing reports (SSRs) received from multiple O-RUs and issue a spectrum usage instruction (SUA) to each O-RU.

[0068] (Scenario 2) Coordination between multiple O-DUs Diagram 12 shows an example of the base station configurations for scenarios 2 and 3 in embodiments of the present invention. The base station in scenario 2 has, for example, a first configuration in which O-DU10B is deployed under O-CU10A (O-CU is the O-RAN central unit) and O-RU10C is deployed under O-DU10B, and a second configuration in which O-DU10B2 is deployed under O-CU10A2 and O-RU10C2 is deployed under O-DU10B2. Furthermore, O-CU10A and O-CU10A2 are connected by an Xn interface, and O-DU10B and O-DU10B2 are connected by a D2 interface. The first and second configurations may be different base stations or the same base station.

[0069] Figure 13 shows an example of a sequence diagram for Scenario 2 in an embodiment of the present invention. The processing of each step will be described below.

[0070] S201: O-RU10C2 collects information on spectrum utilization status within its own device in real time.

[0071] S202: O-RU10C2 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).

[0072] S203: Based on the information collected in S201 and S202, O-RU10C2 creates a Spectrum Sensing Report (SSR) including section type X / section extension type {A / G}. Furthermore, O-RU10C2 transmits the created SSR to O-DU10B2.

[0073] S204: The O-RU10C collects information on the spectrum utilization status of its own device in real time.

[0074] S205: O-RU10C 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).

[0075] S206: Based on the information collected in S204 and S205, O-RU10C creates a Spectrum Sensing Report (SSR) including section type X and section extension types A / G. Furthermore, O-RU10C transmits the created SSR to O-DU10B.

[0076] S207: O-DU10B and O-DU10B2 share a Spectrum Sensing Report (SSR). For example, O-DU10B2 transmits an SSR it holds to O-DU10B, and O-DU10B transmits an SSR it holds to O-DU10B2, thereby sharing the SSR.

[0077] S208: O-DU10B and O-DU10B2 cooperate to create a Spectrum Utilization Instruction (SUA) based on the SSR shared in S207. For example, O-DU10B analyzes the SSR shared in S207 to create a SUA for O-RU10C, and O-DU10B2 analyzes the SSR shared in S207 to create a SUA for O-RU10C2. The SUA may include section type Y / section extension B.

[0078] In coordinating between O-DUs, adjustments will be made to ensure that the frequency bands used by O-RU10C and O-RU10C2 do not interfere with each other, or that the time spent using the same frequency band does not overlap.

[0079] For example, if the usable frequency band (50 MHz bandwidth) is the same for O-RU10C and O-RU10C2, and the cells of O-RU10C and O-RU10C2 are close together, and the degree of interference from other systems is stronger for O-RU10C than for O-RU10C2, then to avoid interference with the frequencies of other systems, a 10 MHz bandwidth gap may be set from the frequency band of other systems. O-RU10C would use the first 20 MHz bandwidth, which is farther from the frequencies of other systems, while O-RU10C2 would use the latter 20 MHz bandwidth, which is closer to the frequencies of other systems. Alternatively, if the degree of interference from other systems is similar for both O-RU10C2 and O-RU10C, a 40 MHz bandwidth, 10 MHz away from the frequencies of other systems, could be scheduled to be used equally by O-RU10C and O-RU10C2 through time-division multiplexing.

[0080] S209: O-DU10B transmits the spectrum usage instruction (SUA) created in S208 to O-RU10C.

[0081] S210: O-RU10C may adjust operating parameters such as frequency bandwidth and transmit power based on the SUA received in S209.

[0082] S211: O-DU10B2 transmits the Spectrum Usage Instruction (SUA) created in S208 to O-RU10C2.

[0083] S212: O-RU10C2 may adjust operating parameters such as frequency bandwidth and transmit power based on the SUA received in S211.

[0084] The procedure described above allows multiple O-DUs to share spectrum sensing reports (SSRs) received from their subordinate O-RUs with other O-DUs and then issue spectrum usage instructions (SUAs) to each O-RU.

[0085] (Scenario 3) In coordinating scenario 3 via O-CU, the base station configuration shown in Figure 12 is used, similar to scenario 2. Figure 14 is a diagram showing an example of a sequence diagram for scenario 3 in an embodiment of the present invention. The processing of each step will be described below.

[0086] S301: O-RU10C collects information on spectrum utilization status within its own device in real time.

[0087] S302: O-RU10C 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).

[0088] S303: Based on the information collected in S301 and S302, O-RU10C creates a Spectrum Sensing Report (SSR) including section type X / section extension type {A / G}. Furthermore, O-RU10C transmits the created SSR to O-DU10B.

[0089] S304: O-DU10B transmits the spectrum sensing report (SSR) received in S303 to O-CU10A.

[0090] S305: O-CU10A and O-CU10A2 share a Spectrum Sensing Report (SSR). Here, it is assumed that O-CU10A2 receives SSRs from its subordinate O-DU10B2 using the same procedure as in S301 to S304. For example, O-CU10A shares SSRs by sending an SSR held by its own device to O-CU10A2, and O-CU10A2 sends an SSR held by its own device to O-CU10A.

[0091] S307: O-CU10A2 creates a Spectrum Utilization Instruction (SUA) in cooperation with other O-CUs based on the SSR shared in S305. This creation may be the same as the process in S208 of Scenario 2.

[0092] S308: O-CU10A creates a Spectrum Utilization Instruction (SUA) in cooperation with other O-CUs based on the SSR shared in S305. This creation may be the same as the process in S208 of Scenario 2.

[0093] S309: O-CU10A transmits the spectrum usage instruction (SUA) created in S308 to O-DU10B.

[0094] S310: O-DU10B transmits the spectrum usage instruction (SUA) received in S309 to O-RU10C.

[0095] S311: O-RU10C may adjust operating parameters such as frequency bandwidth and transmit power based on the SUA received in S310.

[0096] Furthermore, the same processing as in S309 to S311 may be performed in O-CU10A2, O-DU10B2, and O-RU10C2.

[0097] Following the procedure described above, an O-CU above an O-DU can share the Spectrum Sensing Report (SSR) received from its subordinate O-RU with other O-CUs and then issue a Spectrum Use Instruction (SUA) to each O-RU.

[0098] (Example 2) Coordination of SMO / RIC and O-CU / O-DU / O-RU This example describes orchestration for sharing spectrum bands used in multiple wireless communication systems.

[0099] (Summary 1: Optimization of frequency utilization at the SMO level) The SMO, which manages the entire network, decides on frequency usage permission / allocation changes based on the Spectrum Sensing Report (SSR) received from the O-DU.

[0100] (Comparison of interference between multiple O-DUs / O-RUs) The SMO receives SSRs from multiple O-DUs, not just a single O-DU, to comprehensively understand the frequency utilization situation across a wide area (degree of interference / band congestion in each cell), and to centrally determine the frequencies to be reallocated to each O-RU.

[0101] (Priority and Quality of Service) The SMO sets standards that allocate more protected bandwidth to emergency communications (such as PS-LTE) and high-priority services, while tolerating a certain degree of interference for best-effort communications. In addition, the SMO determines the optimal frequency allocation while guaranteeing QoS for the entire network by combining the contents of the SSR (such as interference level) with the service priority of each terminal.

[0102] (Guard Band and Adjacent Band Management) In shared bandwidths with multiple other systems, such as satellite systems, it may be necessary to secure a guard band. However, since areas with little interference and unused portions can be reused, the SMO analyzes the SSR received from multiple O-DU / O-RU and reallocates a portion of the guard band / unused bandwidth between O-RUs.

[0103] (Temporal element) SMO accumulates SSR timestamps / past history in response to interference and utilization rates that fluctuate depending on the time of day, and uses artificial intelligence / machine learning models to learn and predict in advance the time periods when congestion is expected, and changes the frequency allocation accordingly.

[0104] (Overview 2: SSR Analysis Criteria in SMO) (SSR Integration Function) The SMO has the function of integrating SSRs received from multiple O-DUs chronologically and geographically and storing them in an SSR integration table. The SSR integration table may include O-RU identifiers, frequency bands, interference levels, RB usage, and priority requests. The SMO may trigger frequency reallocation and send reallocation instructions to the O-DUs when interference exceeds a certain threshold or when there is more than a certain amount of unused bandwidth.

[0105] (Priority and Policy Templates) The SMO may evaluate the SSR based on pre-configured criteria / policies (priority, protected band (Guard Band (GB)), reallocation criteria, etc.) and dynamically change frequency allocation as needed.

[0106] (Time axis and location information) The SMO may create a map of regional congestion (traffic volume, number of connected terminals, etc.) across the entire network / area based on the timestamps / O-RU locations included in the SSR. Furthermore, the SMO may perform local optimizations based on this map, such as shifting frequency bands (i.e., reallocating resources) only in specific regions. For example, the SMO may perform different controls on region A, region B, and region C based on this map.

[0107] (Frequency usage permission based on orchestration of the entire network) The following describes the decision flow performed by the SMO.

[0108] Step 1 (SSR Reception): The SMO receives the SSR from the O-DU via the O1 interface.

[0109] Step 2 (SSR Integrated Evaluation): The SMO stores the SSRs received in Step 1 into an SSR integrated table and comprehensively evaluates them, including priority, interference level, and the number of Resource Blocks (RBs) in use.

[0110] Step 3 (Determining whether frequency reallocation is necessary): SMO considers avoiding frequency bands with high interference, and if an available frequency band is found, it considers reallocating it.

[0111] Step 4 (Application of Priority Rules): If high-priority services are using congested bandwidth, the SMO may reduce the allocation to low-priority services to free up high-priority bandwidth. Conversely, if there is excess bandwidth for low-priority services, the SMO may release some of the excess bandwidth and allocate it to other O-RUs.

[0112] Step 5 (Creating Frequency Utilization Permission Message): The SMO creates a new frequency utilization instruction (e.g., a Spectrum Utilization Assignment (SUA)) and sends it to the O-RU via Non-RT RIC / O-DU.

[0113] Step 6 (Frequency Change Application): The SMO may generate a policy via the Non-RT RIC and send the policy to the Near-RT RIC / O-DU, which may then apply the frequency change in real time based on the policy. Alternatively, the SMO may instruct the O-DU to change the frequency via the O1 interface, and the O-DU may then send a Spectrum Use Instruction (SUA) to the O-RU.

[0114] (Summary 3: Frequency reallocation based on SMO criteria) In conventional MSS, interference detection and frequency reallocation were completed at the O-DU level. In this embodiment, SMO takes an overview of information across the entire network and performs reallocation using service priority / guard band. By using SSR to evaluate unused / congested bands over a wide area and performing dynamic frequency reallocation, frequency utilization efficiency can be improved.

[0115] (Example 2-1) Extension of the O1 Interface In Example 2-1, newly defined information elements (SpectrumSensingData and InterferenceReport) are added to the O1 interface. The existing O1 interface is mainly intended for basic information exchange in OAM (Operations and Management) and does not have detailed spectrum utilization data and interference reporting models to realize MSS (Managed Spectrum Sharing).

[0116] In this embodiment, the following information elements are newly defined: ・SpectrumSensingData This is an information element for reporting frequency utilization, and includes information (parameters) such as frequencyRange, signalStrength, occupiedChannels, interferenceLevel, and timestamp. Figure 15 shows an example of SpectrumSensingData in an embodiment of the present invention. Figure 15 shows examples of parameter names, parameter definitions, and setting values ​​included in SpectrumSensingData. ・InterferenceReport This is an information element for identifying interference sources and reporting interference damage, and may include, for example, interferingSource, affectedFrequencyBands, severityLevel, and timestamp. Figure 16 shows an example of SpectrumSensingData in an embodiment of the present invention. Figure 16 shows examples of parameter names, parameter definitions, and setting values ​​included in InterferenceReport.

[0117] (Detailed Procedure Using Sequence Diagrams) The detailed procedure for this embodiment will be described below using sequence diagrams. In this procedure, the base station configuration shown in Figure 17 is used. As shown in Figure 17, there is a first configuration in which O-DU10B is deployed under O-CU10A and O-RU10C is deployed under O-DU10B, and a second configuration in which O-DU10B2 is deployed under O-CU10A2 and O-RU10C2 is deployed under O-DU10B2. The SMO30 is connected to O-CU10A, O-CU10A2, O-DU10B, and O-DU10B2 via the O1 interface. Furthermore, O-CU10A and O-CU10A2 are connected via the Xn interface, and O-DU10B and O-DU10B2 are connected via the D2 interface. Here, the first and second configurations may be different base stations. Furthermore, this configuration is just one example, and the SMO30 may be configured to connect to three or more base stations, including O-CU / O-DU / O-RU.

[0118] Figure 18 shows an example of a sequence diagram for Scenario 4-1 in an embodiment of the present invention. In this sequence diagram, O-CU10A2, O-DU10B2, and O-RU10C2 perform the same processing as O-CU10A, O-DU10B, and O-RU10C. The processing of each step will be described below.

[0119] S401: O-RU10C collects information on spectrum utilization status within its own device in real time.

[0120] S402: O-RU10C 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).

[0121] S403: O-RU10C generates a Spectrum Sensing Report (SSR) including Section Type X / Section Extension Type B based on the information collected in S401 and S402.

[0122] Furthermore, the O-RU10C may, for example, monitor a 30MHz bandwidth in the 3.650-3.680GHz range, and based on the monitoring results, set information elements (SpectrumSensingData) and include said information elements (SpectrumSensingData) in the Spectrum Sensing Report (SSR). These information elements (SpectrumSensingData) may also include parameters with the following values: • frequencyRange = 3.650~3.680GHz • signalStrength = -85 dBm • occupiedChannels = {3.650~3.660GHz} (10MHz bandwidth that O-RU10C recognizes as being used by its own device or other systems 40) • interferenceLevel = 12 dB • timestamp = 2025 / 1 / 15 10:05 In addition, O-RU10C may create an information element (InterferenceReport) if it detects interference from, for example, a satellite gateway station (Satellite_GW_01). The information element (InterferenceReport) may also include parameters with the following values ​​set.・interferingSource = "Satellite_GW_01" ・affectedFrequencyBands = {3.650~3.670GHz} ・severityLevel = "High" ・timestamp = 2025 / 1 / 15 10:06 ・PriorityReq (High or Low) O-RU10C may include the information element (SpectrumSensingData) and the information element (InterferenceReport) in the same SSR, or it may create an SSR containing the information element (SpectrumSensingData) and an SSR containing the information element (InterferenceReport).

[0123] Furthermore, O-RU10C sends the created SSR to O-CU10A / O-DU10B.

[0124] S404: O-CU10A / O-DU10B sends a message to SMO30A containing the spectrum sensing report (SSR) or equivalent information elements (SpectrumSensingData / InterferenceReport) received in S403.

[0125] Alternatively, in S403, O-CU10A / O-DU10B may receive an SSR that does not contain information elements (SpectrumSensingData) / information elements (InterferenceReport), and based on the information contained in the SSR, O-CU10A / O-DU10B may create information elements (SpectrumSensingData) / information elements (InterferenceReport) and send a message to SMO30A that corresponds to the SSR containing the created information elements.

[0126] Here, O-CU10A / O-DU10B may send an SSR (or a message equivalent to an SSR) to SMO30A via the O1 interface. Alternatively, O-CU10A / O-DU10B may send an SSR (or a message equivalent to an SSR) to the Near-RT RIC via the E2 interface, and the Near-RT RIC may then send an SSR (or a message equivalent to an SSR) to the Non-RT RIC in SMO30A via the A1 interface.

[0127] Details regarding the correspondence between the Spectrum Sensing Report (SSR) and the information elements (SpectrumSensingData) / Information elements (InterferenceReport) (parameter mapping) will be described later.

[0128] S405: SMO30A may directly receive information from other systems 40 regarding the frequency utilization status of those other systems.

[0129] S406: SMO30A analyzes the SSR (or equivalent message) received in S404 and the frequency utilization status of other systems received in S405, and determines the optimal spectrum allocation for the entire network based on the results of the analysis.

[0130] Furthermore, SMO30A may create / update an SSR integration table based on the SSR (or equivalent message) received in S404 and the frequency utilization status of other systems received in S405, and determine the optimal spectrum allocation for the entire network based on the SSR integration table. Figure 19 shows an example of an SSR integration table in an embodiment of the present invention. As shown in Figure 19, it includes, for example, information on SSRs received from two O-RUs (identifiers ORU_1 and ORU_2).

[0131] Furthermore, as described in Overview 2 above, SMO30A may decide to perform frequency reallocation based on pre-configured conditions (for example, when interference exceeds a threshold, when a certain amount of unused bandwidth is identified, etc.), criteria, policies, congestion maps, etc.

[0132] Furthermore, SMO30A creates a Spectrum Usage Instruction (SUA) to send to each O-RU (O-RU10C, O-RU10C2) based on the determined spectrum assignment. The SUA may include section type Y / section extension B. Alternatively, SMO30A may create a message containing information equivalent to the SUA.

[0133] S407: SMO30A sends a message containing the Spectrum Usage Instruction (SUA) or equivalent information created in S406 to O-CU10A / O-DU10B via the O1 interface. Alternatively, the Non-RT RIC within SMO30A may send an SUA (or an equivalent message) to the Near-RT RIC via the A1 interface, and the Near-RT RIC may send an SUA (or an equivalent message) to O-CU10A / O-DU10B via the E2 interface.

[0134] S408: O-CU10A / O-DU10B sends a message to O-RU10C containing the Spectrum Use Instruction (SUA) or information equivalent to the SUA received in S407. Here, if O-CU10A / O-DU10B receives a message containing information equivalent to the SUA in S406, O-CU10A / O-DU10B may generate an SUA based on the information contained in the received message and send the created SUA to O-RU10C.

[0135] S409: O-RU10C may adjust operating parameters such as frequency bandwidth and transmit power based on the spectrum usage instruction (SUA) or a message containing information equivalent to a SUA received in S408.

[0136] (Correspondence between SSR and information elements (SpectrumSensingData) / information elements (InterferenceReport)) This section explains the parameters in information elements (SpectrumSensingData) / information elements (InterferenceReport) that correspond to the parameters of section type X or section extension A in SSR.

[0137] There is no parameter in SpectrumSensingData / InterferenceReport corresponding to "Message Type = X" (section type X) in the SSR; this parameter may be managed, for example, by the O1 interface or an internal protocol.

[0138] There is no parameter in SpectrumSensingData / InterferenceReport that corresponds to the SSR's "Message ID = MSG_SSR" (section type X); it can correspond to an ID or log ID assigned to the message received by the SMO30A.

[0139] There is no SpectrumSensingData / InterferenceReport parameter corresponding to the SSR "Section ID = 0x01" (Section Type X). When identifying multiple SSRs, it is possible to manage them using, for example, the O1 message ID or the table ID used in SMO.

[0140] The "RB_START, RB_NUM" (section type X) of the SSR can be mapped to a portion of the occupiedChannels in SpectrumSensingData (such as the number of RBs currently in use).

[0141] The "SYMBOL_ID" (section type X) of the SSR does not have a direct corresponding parameter in SpectrumSensingData, but it may be associated with, for example, the time slot information in O-RU.

[0142] The "FrequencyOffset" (Section Type X) of the SSR allows for the correspondence of a portion of the frequencyRange in SpectrumSensingData, assuming that the offset and band information represent the actual operating frequencies.

[0143] The "OccupiedRBs" (section type X) in SSR correspond to the occupiedChannels in SpectrumSensingData.

[0144] The "SignalStrength" (section type X) in SSR corresponds to the signalStrength in SpectrumSensingData.

[0145] The "InterferenceLevel" (Section Extension A) of SSR corresponds to the interferenceLevel of SpectrumSensingData.

[0146] The "SignalBandwidth" (Section Extension A) of SSR corresponds to a portion of the occupiedChannels and frequencyRange of SpectrumSensingData.

[0147] The "ModulationType," "SignalQuality," and "NoiseFloor" parameters of SSR (Section Extension A) may be extended to include these parameters in SpectrumSensingData as needed.

[0148] (Operations related to guard band and adjacent bandwidth management) In S406 in the sequence diagram of Figure 18, the SMO30A may perform the following operations related to guard band and adjacent bandwidth management to determine the optimal spectrum allocation for the entire network. Figure 20 is a diagram illustrating the operation of guard band and adjacent bandwidth management in an embodiment of the present invention.

[0149] Operation 1 (Interference detection in the shared band) As shown in Figure 20, SMO30A assumes that the satellite system primarily uses 3.650-3.660 GHz and reserves 3.660-3.670 GHz as a normal guard band (GB) in order to detect interference in the shared band (a band that can be shared with other systems 40 (satellite systems)). Here, SMO30A refers to the SSR integrated table to confirm that the degree of interference in the 3.665-3.670 GHz band is low, or that the duration of interference is short (there is a lot of downtime for satellite operation).

[0150] Operation 2 (Reuse of Guard Band) SMO30A analyzes the SSR integrated table and determines that the 3.665–3.670 GHz band can be allocated to the cellular system during periods of low interference risk with satellite systems.

[0151] Furthermore, if interference in O-RU(ORU_1), which has a high priority for interference avoidance requests, is severe, SMO30A will decide to open up and allocate a portion of the frequency band of the guard band.

[0152] Operation 3 (Optimal solution obtained by analyzing SSRs from multiple O-RUs): The SMO30A aggregates the bandwidths not used by other O-RUs (ORU_2, etc.) and other cellular systems, and decides to allocate a portion of the guard band frequency range (e.g., 3.665–3.667 MHz) to O-RU (ORU_1). Furthermore, after reusing the allocated bandwidth, if the SMO30A determines from the received SSRs that interference is limited, it may expand the allocated bandwidth.

[0153] Operation 4 (Frequency Use Permission): The SMO30A generates a SUA (Service Agreement) indicating the plan for reusing the guard band determined in Operation 3 and transmits it to the Non-RT RIC. The Non-RT RIC creates a policy based on the received SUA and transmits the created policy to the Near-RT RIC. The Near-RT RIC transmits frequency allocation instructions to the O-DU / O-RU in real time based on the received policy.

[0154] Furthermore, when applying policies / frequency allocation etc. with a time limit (validityPeriod), SMO30A may set policies / instructions to release resources during periods when satellite systems are constantly operating (high interference levels).

[0155] Operation 5 (Dynamic Optimization): When the interference level / priority status changes, the SMO30A may re-evaluate the SSR and, if necessary, dynamically implement policies such as "returning to a state where the guard band is not used" or "shifting the allocated bandwidth within the guard band to another bandwidth."

[0156] (Example 2-2) Data Processing and Policy Control with Non-RT RIC / Near-RT RIC In Example 2-2, the information elements newly defined in Example 1 are utilized, and dynamic frequency allocation is performed by a spectrum allocation policy generated by analysis based on a machine learning model in Non-RT RIC (rApp). The machine learning model may be artificial intelligence (the same applies hereafter). On the other hand, conventional Non-RT RICs primarily aim at long-term optimization and analysis, and have not used policies for dynamic frequency allocation specifically for MSS (Managed Spectrum Sharing).

[0157] Furthermore, in this embodiment, the Non-RT RIC transmits the spectrum allocation policy it generates to the Near-RT RIC via the A1 interface, and the Near-RT RIC then transmits instructions to the O-CU / O-DU / O-RU via the E2 interface, thereby enabling real-time control of frequency allocation.

[0158] In this embodiment, the following information element is newly defined: ・SpectrumAssignmentPolicy (Spectrum Assignment Policy) This is an information element for defining the assignment policy necessary to realize MSS, and includes information (parameters) such as allowedFrequencyBands (list of permitted frequency bands), transmissionPowerLimits (transmission power limits), priorityLevels (priority settings for services), validityPeriod (policy validity period), and actionType (actions such as new assignment, modification, and cancellation). Figure 21 shows an example of SpectrumAssignmentPolicy in an embodiment of the present invention. Figure 21 shows examples of parameter names, parameter definitions, and setting values ​​included in SpectrumAssignmentPolicy.

[0159] The Non-RT RIC transmits the SpectrumAssignmentPolicy to the Near-RT RIC via the A1 interface. The Near-RT RIC then transmits control messages based on the SpectrumAssignmentPolicy in real time via the E2 interface. This allows the SpectrumAssignmentPolicy generated by the Non-RT RIC to be immediately applied by the Near-RT RIC.

[0160] (Example of SpectrumAssignmentPolicy usage) ・Policy generation For example, in policy generation, Non-RT RIC / SMO may analyze historical data and SSR to predict that "satellite interference (3.660-3.670 GHz) will increase by 15-20 dB between 10:00 and 12:00" as a policy regarding interference and traffic prediction.

[0161] Furthermore, for Non-RT RIC / SMO, parameter settings may include `allowedFrequencyBands=3.700-3.710GHz`, `transmissionPowerLimits=15dBm`, and priority levels such as "high priority" for emergency calls and "medium priority" for video distribution as interference avoidance targets. Additionally, the time period may be limited with `validityPeriod=10:00-12:00`, and the migration from the existing band may be determined with `actionType=Modify`.

[0162] Additionally, Non-RT RIC / SMO may set a fallbackPolicy such as "If interference exceeds the threshold (15dB) even in the 3.700-3.710 GHz range, move to 3.710-3.720 GHz." • Policy Distribution For example, Non-RT RIC may send a policy (SpectrumAssignmentPolicy) including the allowedFrequencyBands, transmissionPowerLimits, and fallbackPolicy configured in the policy generation described above to Near-RT RIC via the A1 interface.

[0163] Alternatively, the SMO may instruct the O-DU via the O1 interface to prepare for the frequency transition based on the generated policy described above. Real-time control: For example, the Near-RT RIC or O-DU may, according to a policy to transition frequencies during a specified time period (10:00 to 12:00), switch the frequency used by the O-RU to 3.700 to 3.710 GHz based on actionType=Modify when the validityPeriod (10:00 to 12:00) arrives.

[0164] Additionally, if the number of users exceeds maximumUserCountPerBand=100, the Near-RT RIC or O-DU may migrate the frequency of lower-priority users (e.g., IoT) to 3.720–3.730 GHz.

[0165] Additionally, the Near-RT RIC or O-DU may apply a fallback policy and, if interference (exceeding 15 dB) occurs, send an instruction via the E2 interface to "re-migrate to 3.710-3.720 GHz," allowing high-priority emergency calls to be moved to the safe band first.

[0166] Furthermore, Near-RT RICs or O-DUs may, in accordance with policies regarding priority / QoS requirements, immediately reassign if an emergency call falls below the minimum SINR, or maintain the 3.700-3.710 GHz allocation if there is availability for video distribution (medium priority) / IoT (low priority) users. • Policy termination and updates: For example, Non-RT RICs / SMOs may release the policy or transition to the next policy (such as reassigning to the original 3.660-3.670 GHz band once interference subsides) when the policy's validity period expires (e.g., 12:00).

[0167] Additionally, Non-RT RIC / SMO may recollect interference fluctuation / emergency call quality maintenance success rates to reflect log / learning data and adjust parameters for subsequent use.

[0168] (Detailed Procedure Using Sequence Diagrams) The detailed procedure for this embodiment will be described below using sequence diagrams. In this procedure, the base station configuration shown in Figure 17 will be used, similar to that in Embodiment 4-1.

[0169] Figure 22 shows an example of a sequence diagram for Scenario 4-2 in an embodiment of the present invention. In this sequence diagram, O-CU10A2, O-DU10B2, and O-RU10C2 perform the same processing as O-CU10A, O-DU10B, and O-RU10C. The processing of each step will be described below.

[0170] The processes from S501 to S505 are the same as those described in Example 1, specifically from S401 to S405 in Figure 18.

[0171] S506: The Non-RT RIC within SMO30A periodically retrieves the SSR integration table from SMO30A.

[0172] S507: The Non-RT RIC within SMO30A uses the SSR integration table and machine learning models acquired in S506 to analyze and learn the operating patterns of other systems 40. For example, the Non-RT RIC within SMO30A learns the operating patterns of satellite gateway stations to acquire trends such as "interference frequently occurs between 10 and 11 o'clock." Alternatively, for example, the Non-RT RIC within SMO30A can use the learned machine learning models to predict time periods when congestion is expected in the future, thereby enabling it to proactively issue instructions for bandwidth shifting (frequency reallocation).

[0173] S508: SMO30A transmits instructions to O-CU10A / O-DU10B regarding adjustments to frequency band / transmit power, etc., based on the results of the analysis and learning performed in S507. These instructions may be a Spectrum Utilization Instruction (SUA) or a message containing information equivalent to a SUA.

[0174] S509: The Non-RT RIC within SMO30A creates a SpectrumAssignmentPolicy based on the results of the analysis and learning performed in S507, including, for example, "allowedFrequencyBands = 3.700-3.710GHz", "transmissionPowerLimits = 15dBm", and "priorityLevels = High".

[0175] S510: The Non-RT RIC within SMO30A transmits the SpectrumAssignmentPolicy created in S509 to the Near-RT RIC30B via the A1 interface. Here, since the Non-RT RIC is the control device (RAN Intelligent Controller (RIC)) within SMO30A, it can also be said that SMO30A transmits it.

[0176] S511: The Near-RT RIC30B receives and monitors real-time interference level / resource usage information from the O-RU10C / O-DU10B via the E2 interface.

[0177] S512: Based on the SpectrumAssignmentPolicy received in S509 and the monitoring results performed in S511, Near-RT RIC30B sends instructions to O-RU10C / O-DU10B regarding adjustments to the frequency band / transmission power, etc. For example, if the interference level exceeds a predetermined threshold (e.g., 10dB), Near-RT RIC30B may implement additional measures (e.g., fallbackPolicy set in SpectrumAssignmentPolicy) / instructions. Alternatively, for example, based on the policy "If interference with the satellite GW is strong, it is possible to switch from 3.650-3.670GHz to 3.700-3.710GHz," Near-RT RIC30B may send instructions to O-RU10C via the E2 interface to switch frequencies and to set the transmissionPowerLimits to 15dBm to avoid collisions.

[0178] Here, the instruction may include a Spectrum Usage Instruction (SUA) / Information Element (SpectrumAssignmentPolicy). Details regarding the correspondence between Spectrum Usage Instructions (SUAs) and Information Element (SpectrumAssignmentPolicy) (parameter mapping) will be described later.

[0179] S513: Based on the instructions received in S512, the O-RU10C adjusts operating parameters such as frequency band and transmit power.

[0180] S514: After performing adjustments based on the instructions received in S513, O-RU10C transmits feedback information to Near-RT RIC30B, including information regarding reception quality / interference level, etc. Near-RT RIC30B reviews the feedback information received from O-RU10C and may decide to maintain the current settings if, for example, interference has been reduced after O-RU10C moves to a different frequency. Alternatively, Near-RT RIC30B may issue an instruction to return the frequency band to its original frequency band (3.650-3.670 GHz) after interference has been resolved, based on a policy (e.g., validityPeriod).

[0181] S515: The Near-RT RIC30B transmits the control results performed in real time from S511 to S514 to the SMO30A / Non-RT RIC within the SMO30A, and the SMO30A / Non-RT RIC within the SMO30A may update the SSR integration table / machine learning model / policy, etc., based on the received control results. This makes it possible to synchronize information regarding frequency allocation control, etc., between the Non-RT RIC within the SMO30A / Non-RT RIC and the Near-RT RIC30B.

[0182] (Correspondence between Spectrum Usage Instructions (SUA) and Information Elements (SpectrumAssignmentPolicy)) This section describes the parameters in the Information Elements (SpectrumAssignmentPolicy) that correspond to the parameters of Section Type Y or Section Extension B in the SUA.

[0183] There is no SpectrumAssignmentPolicy parameter corresponding to SUA's "Message Type = Y" (section type Y), and this parameter may be managed, for example, as "policy message type".

[0184] There is no SpectrumAssignmentPolicy parameter corresponding to "Message ID = MSG_SUA" (section type Y) in SUA; this parameter may be managed, for example, by a policy ID generated by Non-RT RIC or SMO.

[0185] There is no SpectrumAssignmentPolicy parameter corresponding to "Section ID = 0x02" (section type Y) in SUA; this parameter may be uniquely managed, for example, by SMO or RIC.

[0186] SUA's "AllowedRBs" (section type Y) can be used to convert RB units to frequency band units, allowing it to correspond to SpectrumAssignmentPolicy's allowedFrequencyBands or maxUserCount, etc.

[0187] The SUA's "SYMBOLS" (section type Y) may be extended to include the relevant parameters in the SpectrumAssignmentPolicy as needed.

[0188] SUA's "AllowedFrequencyBands" (section type Y) corresponds to the allowedFrequencyBands in SpectrumAssignmentPolicy.

[0189] SUA's "PowerLimitations" (section type Y) corresponds to the transmissionPowerLimits in SpectrumAssignmentPolicy.

[0190] SUA's "PriorityLevel" (Section Type B) corresponds to the priorityLevels in SpectrumAssignmentPolicy (equivalent to overall service priority setting).

[0191] The SUA's "FrequencyHoppingPattern" (Section Type B) corresponds to the FrequencyHoppingPattern or fallbackPolicy of the SpectrumAssignmentPolicy.

[0192] SUA's "InterferenceTolerance" (Section Type B) corresponds to a part of the InterferenceTolerance or fallbackPolicy in SpectrumAssignmentPolicy.

[0193] SUA's "TimeRestrictions" (Section Type B) corresponds to the validityPeriod of SpectrumAssignmentPolicy (restricting frequency usage by start / end time).

[0194] SUA's "GeographicalRestrictions" (section type B) corresponds to the geographicRestrictions in SpectrumAssignmentPolicy.

[0195] (Effects) The above embodiment enables the effective implementation of Integrated Spectrum Sharing (MSS) in the O-RAN architecture, contributing to the efficient use of frequency resources and improved network performance. Furthermore, by extending the O1 interface used by the SMO and strengthening the cooperation between Non-RT RIC and Near-RT RIC, it becomes possible to optimize and control the entire network resource in real time.

[0196] In other words, the above-described embodiment makes it possible to provide an orchestration mechanism for sharing spectrum bands used in multiple wireless communication systems.

[0197] (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.

[0198] <Base Station 10 and Network Node 30> Figure 23 is a diagram showing an example of the functional configuration of a base station 10 and a network node 30. As shown in Figure 23, 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 23 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.

[0199] 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.

[0200] 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.

[0201] 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.

[0202] <Terminal 20> Figure 24 is a diagram showing an example of the functional configuration of terminal 20. As shown in Figure 24, 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 24 is merely an example. Any functional classification and name of functional unit is acceptable as long as it can perform the operations 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.

[0203] 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.

[0204] 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.

[0205] 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.

[0206] (Hardware Configuration) The block diagrams (Figures 23 and 24) 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 above one device or the above multiple devices with software.

[0207] 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.

[0208] 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 25 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.

[0209] 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.

[0210] 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.

[0211] 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.

[0212] 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 23 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 24 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.

[0213] 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.

[0214] 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.

[0215] 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.

[0216] 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).

[0217] 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.

[0218] 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.

[0219] 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.

[0220] 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.

[0221] 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.

[0222] 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.

[0223] 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.

[0224] 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.

[0225] Figure 26 shows an example of the configuration of vehicle 2001. As shown in Figure 26, 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.

[0226] 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.

[0227] 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).

[0228] 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.

[0229] 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.).

[0230] 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.

[0231] 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.

[0232] 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.

[0233] 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.

[0234] 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.

[0235] <Notes> (Note 1) A network node having: a receiving unit that receives spectrum sensing reports including information elements for frequency utilization reports and information elements for interference reports from a central unit or distributed unit of a plurality of base stations; a control unit that determines instructions for frequency allocation for each of the plurality of base stations in a frequency band shared by a plurality of wireless systems based on a table that integrates the plurality of spectrum sensing reports; and a transmitting unit that transmits the determined frequency allocation instructions to the central unit or distributed unit of the plurality of base stations. (Note 2) The network node according to Note 1, wherein the information elements for frequency utilization reports include information on frequency range, signal strength, occupied channel, and interference level, and the information elements for interference reports include information on interference source identifier, affected frequency band, and interference severity. (Note 3) The network node according to Note 1, wherein the control unit uses a map showing the degree of congestion for each region when determining the instructions for frequency allocation. (Appendix 4) The network node according to Appendix 1, wherein the control unit determines a policy relating to the frequency allocation, and the transmission unit transmits the policy to a quasi-real-time control device. (Appendix 5) The network node according to Appendix 4, wherein the policy includes information relating to a list of permitted frequency bands, a maximum transmit power value, service priority settings, and the validity period of the policy. (Appendix 6) A communication method performed by a network node, comprising the steps of: receiving a spectrum sensing report from a central or distributed unit of a plurality of base stations, including information elements relating to frequency utilization reports and information elements relating to interference reports; determining instructions for frequency allocation for each of the plurality of base stations in a frequency band shared by a plurality of wireless systems, based on a table integrating the plurality of spectrum sensing reports; and transmitting the determined instructions for frequency allocation to the central or distributed unit of the plurality of base stations.

[0236] Any of the appendices 1 to 6 can provide an orchestration mechanism for sharing spectrum bands used in multiple wireless communication systems.

[0237] (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.

[0238] Furthermore, notification of information is not limited to the embodiments / models 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.

[0239] 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).

[0240] 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.

[0241] 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).

[0242] 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.

[0243] 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.

[0244] 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).

[0245] 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.

[0246] 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.

[0247] 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.

[0248] 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.

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

[0250] 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.

[0251] 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.

[0252] 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.

[0253] 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.

[0254] 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.

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

[0256] 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.

[0257] 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.

[0258] 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.

[0259] 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.

[0260] 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."

[0261] 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.

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

[0263] 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."

[0264] 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.

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

[0266] 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.

[0267] 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.

[0268] 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."

[0269] 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).

[0270] 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.

[0271] 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 having: a receiving unit that receives spectrum sensing reports including information elements for frequency usage reports and information elements for interference reports from a central unit or distributed unit of a plurality of base stations; a control unit that determines instructions for frequency allocation for each of the plurality of base stations in a frequency band shared by a plurality of wireless systems based on a table integrating the plurality of spectrum sensing reports; and a transmitting unit that transmits the determined frequency allocation instructions to the central unit or distributed unit of the plurality of base stations.

2. The network node according to claim 1, wherein the information elements for reporting frequency usage include information on frequency range, signal strength, occupied channel, and interference level, and the information elements for reporting interference include information on interference source identifier, affected frequency band, and interference severity.

3. The network node according to claim 1, wherein the control unit uses a map showing the degree of congestion for each region when determining the instruction for frequency allocation.

4. The network node according to claim 1, wherein the control unit determines a policy regarding the frequency allocation, and the transmission unit transmits the policy to a quasi-real-time control device.

5. The network node according to claim 4, wherein the policy includes information regarding a list of permitted frequency bands, a maximum transmit power limit, service priority settings, and the validity period of the policy.

6. A communication method performed by a network node, comprising the steps of: receiving a spectrum sensing report from a central or distributed unit of a plurality of base stations, which includes information elements regarding frequency usage and information elements regarding interference; determining a frequency allocation instruction for each of the plurality of base stations in a frequency band shared by a plurality of wireless systems, based on a table integrating the plurality of spectrum sensing reports; and transmitting the determined frequency allocation instruction to the central or distributed unit of the plurality of base stations.

Images