Base station, terminal, and communication method

Abstract

This base station comprises: a transmission unit that transmits, in a first cell, a synchronization signal and system information of the first cell; and a control unit that causes the transmission unit to transmit, in the first cell, system information of a second cell.

Description

Base Station, Terminal, and Communication Method

[0001] The present disclosure relates to a base station, a terminal, and a communication method for providing a cell of a network to which energy reduction is applied.

[0002] The 3rd Generation Partnership Project (3GPP (registered trademark)) is standardizing the 5th generation mobile communication system (also called 5G, New Radio (NR), or Next Generation (NG)), and is also proceeding with the standardization of the next-generation mobile communication system called Beyond 5G, 5G Evolution, or 6G.

[0003] The 5G base station periodically transmits the SS (Synchronization Signal) and system information (SIB: System Information Block) in each cell. The terminal (also called UE: User Equipment) performs cell search using the SS, acquires SIB1 information included in the system information notified in the searched cell, executes cell selection, and accesses ( camps on) the cell. (Non-Patent Document 1)

[0004] 3GPP TS 36.331 V18.3.1, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (Release 18), 3GPP, September 2024

[0005] In 6G, for example, in order to support high-speed and high-capacity services, there is a possibility of using a high-frequency band with high power consumption, so it may be designed on the premise of network energy saving (NES: Network Energy Saving) in order to suppress power consumption.

[0006] From an NES perspective, it is conceivable to introduce a new cell (or carrier) concept called a non-anchor cell (or non-anchor carrier), separate from the anchor cell (or anchor carrier), and reduce the amount of information transmitted by the non-anchor cell (or non-anchor carrier) to suppress power consumption for the entire network.

[0007] If the transmission of information necessary to access a cell is reduced in a non-anchor cell (or non-anchor carrier), there is a challenge in how to enable terminals to access non-anchor cells (or non-anchor carriers). Note that the term "access" may be interpreted interchangeably with the terms "cell selection" or "cell re-selection."

[0008] Therefore, this disclosure is made in view of these circumstances and aims to provide a base station, terminal, and communication method that enable terminals to reliably access cells in a network to which NES is applied.

[0009] One aspect of the present disclosure is a base station (100) comprising a transmitting unit (110) that transmits a synchronization signal and system information of the first cell in the first cell, and a control unit (120) that causes the transmitting unit to transmit system information of the second cell in the first cell.

[0010] One aspect of the present disclosure is a communication method comprising a transmission step of transmitting a synchronization signal and system information of a first cell in a first cell, and a step of transmitting system information of a second cell in a first cell.

[0011] One aspect of the present disclosure is a terminal (200) comprising, in a first cell, a receiving unit (210) that receives synchronization signals and system information of the first cell and system information of a second cell, and a control unit (220) that accesses the second cell based on the system information of the second cell received in the first cell.

[0012] One aspect of the present disclosure is a base station (100) comprising: a control unit (130) that provides the system information of the second cell to other base stations forming the first cell, which transmit the synchronization signal and system information of the first cell and the system information of the second cell in the first cell; and a transmission unit (110) that transmits the synchronization signal of the second cell in the second cell.

[0013] Figure 1 is a schematic diagram of the overall configuration of a wireless communication system. Figure 2 is a diagram showing the frequency range used in the wireless communication system. Figure 3 is a diagram showing an example of the configuration of wireless frames, subframes, slots, and symbols used in the wireless communication system. Figure 4 is a diagram showing an example of carrier types in 6G. Figure 5 is a functional block diagram of a base station. Figure 6 is a functional block diagram of a terminal. Figure 7 is a diagram showing the first embodiment. Figure 8 is a diagram showing the sequence in the first embodiment. Figure 9 is a diagram showing the first sequence related to information acquisition of non-anchor cells in the first embodiment. Figure 10 is a diagram showing the second sequence related to information acquisition of non-anchor cells in the first embodiment. Figure 11 is a diagram showing the second embodiment. Figure 12 is a diagram showing the first sequence related to information acquisition of non-anchor cells in the second embodiment. Figure 13 is a diagram showing the second sequence related to information acquisition of non-anchor cells in the second embodiment. Figure 14 is a diagram showing the third embodiment. Figure 15 is a diagram showing the first sequence related to inter-device information exchange in the third embodiment. Figure 16 is a diagram showing the second sequence related to inter-device information exchange in the third embodiment. Figure 17 is a diagram showing an example of the hardware configuration of a base station and a terminal. Figure 18 shows an example of a vehicle configuration.

[0014] The embodiments will be described below with reference to the drawings. Note that identical or similar reference numerals are used to denote the same functions and components, and their descriptions will be omitted as appropriate.

[0015] (1) Overall schematic diagram 1 of the wireless communication system is an overall schematic diagram of the wireless communication system 10 according to the embodiment. The wireless communication system 10 is a wireless communication system in accordance with 6G and includes UE200, base station 100, and network 20.

[0016] The wireless communication system 10 may be a wireless communication system conforming to a method called Beyond 5G or 5G Evolution, or it may partially include a wireless communication system conforming to a method called Long Term Evolution (LTE) or 4G, or 5G New Radio (NR). Furthermore, the wireless communication system 10 may be configured to include other radio access technologies (RATs) in addition to 6G, such as 4G / LTE and 5G. The specific configuration of the wireless system 10 is not limited to the example shown in Figure 1.

[0017] Network 20 includes multiple base stations 100. Base stations 100 are, for example, gNBs, and may also include eNBs, etc. Network 20 is connected to a 6G-compliant core network (6GC, not shown).

[0018] Base station 100 is a 6G-compliant wireless base station and performs 6G-compliant wireless communication with UE200. Base station 100 can support carrier aggregation (CA), which uses multiple component carriers (CCs) bundled together, and dual connectivity (DC), which enables simultaneous communication between base stations, by using Massive Multiple-Input Multiple-Output (Massive MIMO), which generates a more directional beam by controlling the wireless signals transmitted from multiple antenna elements.

[0019] The base station 100 may consist of a CU (Central Unit) and a DU (Distributed Unit), the DU being located separately from the CU at a geographically different location. One or more DUs may be connected to the CU. For example, the base station 100 may employ a fronthaul (FH) interface as defined by the O-RAN (Open Radio Access Network Alliance) and may include an O-DU (O-RAN Distributed Unit) and an O-RU (O-RAN Radio Unit).

[0020] The base stations 100 may be connected by an Xn interface. If the base stations 100 have a configuration of CUs and DUs, the CUs and DUs may be connected by an F1 interface, different CUs (for example, between CU1 and CU2) may be connected by an Xn-U interface, and different DUs (for example, between DU1 and DU2) may be connected by an Xn-C interface.

[0021] The base station 100 and UE200 can support CA (carrier aggregation), which uses multiple CCs (cable controllers) in combination, and DC (dual-cable communication), which communicates simultaneously between the UE and multiple base stations, by controlling the radio signals transmitted from multiple antenna elements.

[0022] The UE200 is a terminal capable of performing wireless communication in accordance with 6G, and may also perform wireless communication in accordance with communication methods called Beyond 5G or 5G Evolution. It may also have the capability to perform wireless communication in accordance with LTE / 4G or NR / 5G.

[0023] The UE200 may perform measurement reporting periodically. The UE200 may also perform measurement reporting for each event.

[0024] Furthermore, the wireless communication system 10 may support multiple frequency ranges (FRs). That is, as shown in Figure 2, it may support the following FRs: • FR1: 410 MHz to 7.125 GHz • FR2-1: 24.25 GHz to 52.6 GHz • FR2-2: Over 52.6 GHz to 71 GHz

[0025] In FR1, a subcarrier spacing (SCS) of 15, 30, or 60 kHz and a bandwidth (BW) of 5 to 100 MHz may be used. In FR2-1, an SCS of 60 or 120 kHz (or 240 kHz) and a BW of 50 to 400 MHz may be used.

[0026] In FR2-2, to avoid an increase in phase noise, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) or Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing (DFT-S-OFDM) with a larger SCS may be applied.

[0027] Furthermore, as shown in Figure 3, one slot in the wireless communication system 10 consists of 14 symbols. If this configuration is maintained, the larger (wider) the SCS becomes, the shorter the symbol period (and slot period). Note that the SCS is not limited to the frequencies shown in Figure 3, and may be other frequencies such as 480 kHz or 960 kHz.

[0028] Furthermore, the number of symbols constituting one slot does not necessarily have to be 14; for example, it could be 28 or 56 symbols. In addition, the number of slots per subframe may vary depending on the SCS.

[0029] (2) Carrier configuration diagram 4 is a diagram showing an example of carrier types in 6G. The network 20 in Figure 1 may support the carrier types shown in Figure 4. Specifically, the base station 100 may support all or some of the carrier types: anchor carrier, data carrier, and perch carrier. A cell composed of an anchor carrier is called an anchor cell, a cell composed of a data carrier is called a data cell, and a cell composed of a perch carrier is called a perch cell. In this embodiment, "carrier," "cell," "frequency," "frequency band," and "band" may be interchangeable.

[0030] Figure 4 shows an example where the anchor carrier is located in two frequency bands (Band A and Band B), and the data carrier is located in a higher frequency band (Band C) than the anchor carrier. The perch carrier is shown by a dashed line, and when a perch carrier is newly introduced in 6G, it may be set to a lower frequency than the anchor carrier, or it may be set to a part of the same frequency band as the anchor carrier.

[0031] Anchor carriers may also be called anchor cells or anchor bands, and perch carriers may also be called perch cells or perch bands.

[0032] i) Without the introduction of a perch carrier: If a perch carrier is not introduced, there is no perch carrier in Figure 4. Carriers other than the anchor carrier may be called non-anchor carriers. The anchor carrier may be responsible for sending all or part of the synchronization signals (SS), sync raster, system information (MIB, SIB, other SIBs), and control signaling (PDCCH, DCI) of the non-anchor carrier (e.g., data carrier).

[0033] The synchronization signal (SS) may include, for example, a PSS (Primary Synchronization Signal) and / or an SSS (Secondary Synchronization Signal). System information may include, for example, a MIB (Master Information Block) transmitted on a broadcast channel (e.g., a PBCH (Physical Broadcast Channel)) and / or an SIB (e.g., SIB1) transmitted on a downlink shared channel (e.g., a PDSCH (Physical Downlink Shared Channel)). Since system information is broadcast on the broadcast channel and / or downlink shared channel, it may also be referred to as broadcast information. Furthermore, the block including the synchronization signal and broadcast channel may be called an SSB or SS / PBCH (synchronization signal / physical broadcast channel block), etc.

[0034] An anchor cell composed of an anchor carrier in the embodiment may be understood as a first cell, and a non-anchor cell composed of a non-anchor carrier may be understood as a second cell.

[0035] ii) When a perch carrier is introduced, a perch carrier is present in Figure 4. Carriers other than the perch carrier may be called non-perch carriers. The perch carrier may have the role of transmitting all or part of the synchronization signals (SS), sync raster, system information (MIB, SIB, other SIBs), and control signaling (PDCCH, DCI) of non-perch carriers (e.g., anchor carrier, data carrier).

[0036] It should be noted that perch carriers may be understood as being included in anchor carriers in a broad sense. In this case, perch carriers may also be broadly referred to as anchor carriers. Anchor carriers, including perch carriers, may have the role of transmitting all or part of the synchronization signals (SS), sync raster, system information (MIB, SIB, other SIBs), and control signaling (PDCCH, DCI) of non-anchor carriers (e.g., data carriers).

[0037] A parch cell composed of a parch carrier in the embodiment may be understood as a first cell, and a non-parch cell composed of a non-parch carrier may be understood as a second cell.

[0038] In the embodiment, at least the synchronization signal (SS) of the non-anchor carrier (or non-perch carrier) and system information (MIB, SIB1, other SIBs) may be transmitted on the non-anchor carrier (or non-perch carrier). Furthermore, all or part of the signals or information other than the synchronization signal (SS), i.e., the system information (MIB, SIB1, other SIBs), may not be transmitted on the non-anchor carrier (or non-perch carrier) from the perspective of NES. Also, in the embodiment, the signals or information of the non-anchor carrier (or non-perch carrier) that are not transmitted on the non-anchor carrier (or non-perch carrier) may be transmitted on the anchor carrier (or perch carrier).

[0039] Thus, in 5G, the synchronization signal (SS) and PBCH were treated as a single set SSB, but in this embodiment, the synchronization signal (SS) and PBCH of the non-anchor carrier (or non-perch carrier) may be treated independently and transmitted using separate carriers. This allows for a reduction in the periodic transmission of signals or information, for example, when the non-anchor carrier (or non-perch carrier) is set in a high frequency band, thus enabling the NES effect.

[0040] A perch carrier may be understood as a carrier having at least one of the following features, for example:

[0041] - It is a carrier that all devices can access.

[0042] - The carrier is accessible regardless of the terminal type or usage environment (however, some terminals that meet different conditions than the type or usage environment may be configured to be inaccessible). Terminal types include, for example, enhanced Mobile BroadBand (eMBB) terminals, Reduced Capability (RedCap) terminals, Unmanned Aerial Vehicle (UAV) terminals, XR terminals, NTN terminals, IoT terminals, Industrial IoT terminals, NarrowBand IoT (NB-IoT) terminals, Low-Power Wake-Up Signal (LPWUS) terminals, and Small Data Transmission (SDT) terminals. Terminal usage environments include, for example, access type (e.g., 3GPP, non-3GPP), use case (e.g., Immersive Communication, Ubiquitous Connectivity), and service type (e.g., Ultra-Reliable and Low Latency Communications (URLLC), Vehicle to X (V2X), Multicast and Broadcast Service (MBS), Broadcast Service).

[0043] This refers to a carrier that is accessible regardless of whether data communication is enabled or disabled (a carrier not intended for data communication). Data communication primarily refers to the transmission and reception of user data and traffic data processed by the U-Plane (User-Plane). User data may include voice calls, but does not exclude control data. Hereafter, this will also be simply referred to as "communication."

[0044] ・It is a carrier on which a synchronization signal (SS) and / or system information is transmitted. The synchronization signal may include, for example, PSS and / or SSS. The system information may include, for example, the MIB transmitted on a notification channel (e.g., PBCH), and / or SIB (e.g., SIB1) transmitted on a downlink shared channel (e.g., PDSCH). Note that since the system information is notified on the notification channel and / or the downlink shared channel, it may be referred to as notification information. Also, a block including the synchronization signal and the notification channel may be called SSB or SS / PBCH, etc. Thus, a per-carrier may also be a carrier on which control information (e.g., a signal and / or information for initial access) is transmitted. The system information transmitted and received on a per-carrier may include information about other carriers (data carriers (Band C) and anchor carriers (Bands A and B) in the figure). Information about other carriers is, for example, information for a terminal accessing a per-carrier to select other carriers (perform initial access to other carriers). Also, when other carriers transition to the Network Energy Saving mode (NES mode), the information about other carriers may include information about the NES mode. Information about the NES mode is, for example, Cell DTX config(periodicity), Cell DRX config(periodicity), SSB periodicity.

[0045] The perch carrier may be in a lower frequency band than the data carrier (Band C) that transmits and receives data, or the anchor carrier (Bands A and B) that transmits and receives control information (and data). Due to frequency characteristics, coverage is greater in the lower frequency band, so coverage can be ensured by using a carrier in a lower frequency band than the anchor carrier as the perch carrier. On the other hand, by using a carrier in a higher frequency band than the perch carrier as the anchor carrier, a wider bandwidth can be ensured, thereby improving throughput. In this way, by combining a perch carrier and an anchor carrier, coverage can be ensured and throughput can be improved.

[0046] One use case for perch carriers and anchor carriers is to use a wideband frequency band with higher frequencies as an anchor carrier to support high-speed, high-capacity communication services such as XR (Cross Reality or Extended Reality) terminals. However, because such high frequencies are directional, they are susceptible to reflection, requiring beam sweeping or the application of multiple beams, which increases network power consumption. Therefore, when providing high-speed, high-capacity communication services to terminals, a high-frequency band can be provided (turned on) as the anchor carrier. However, when not providing high-speed, high-capacity communication services to terminals, the high-frequency band can not be provided as the anchor carrier (turned off), and the terminals can be kept on standby with a perch carrier on a lower frequency band. By setting the perch carrier to a lower frequency band, coverage can be easily ensured compared to high frequencies because lower frequencies have the property of bending around, and network power consumption can also be reduced. Thus, perch carriers and anchor carriers are also suitable for the introduction of NES.

[0047] Note that "waiting via a prach carrier (camp on)" may be used in the same sense as waiting in a prach cell or waiting in a prach band. Waiting may be used to mean waiting for a communication service. Also, waiting may be used to mean "camp on". The state of the UE performing the waiting may be understood as a state where the RRC connection is not established or suspended, such as the idle state (e.g., RRC_Idle state) or the inactive state (e.g., RRC_Inactive state).

[0048] The prach carrier may be recognizable by the terminal by default or may be set by the network (base station). For example, the prach carrier may be assigned to a frequency band where it is relatively easy to secure coverage. The prach carrier may be understood as a prach carrier group composed of a plurality of prach carriers.

[0049] The anchor carrier may be a carrier that transmits and receives control information (and data). For example, it may be assigned to Band A or Band B, which is a frequency band higher than the prach carrier (e.g., 2 GHz band, etc.). In contrast, the data carrier may be a carrier that transmits and receives data and may be assigned to Band C, which is a frequency band even higher than the anchor carrier (e.g., 3.7 GHz band, 4.5 GHz band, 28 GHz band, etc.). These carriers may be used appropriately depending on the type of terminal and the use case. For example, when an XR terminal or UE uses an XR service, it is conceivable to transition from the prach carrier to the anchor carrier in Band A or B with a high frequency or the data carrier in Band C to perform RACH and enter the connected state (e.g., RRC_Connected state).

[0050] Note that "waiting via the anchor carrier" may be used in the same sense as waiting in an anchor cell or waiting in an anchor band.

[0051] Furthermore, anchor carriers can be considered carriers that act as PCCs (Primary Component Carriers) or PCells (Primary Cells), while data carriers can be considered carriers that act as SCCs (Secondary Component Carriers).

[0052] (3) Functional block configuration of the wireless communication system (3.1) Functional block configuration of the base station As shown in Figure 5, the base station 100 includes a wireless communication unit 110, a broadcast information provision unit 120, an inter-device information provision unit 130, and a control unit 140.

[0053] The wireless communication unit 110 transmits and receives wireless signals to and from the UE200. The wireless signals include a channel and a reference signal.

[0054] The wireless communication unit 110 transmits and receives wireless signals via control channels or data channels. Control channels include the physical uplink control channel (PUCCH), physical downlink control channel (PDCCH), physical random access channel (PRACH), and physical broadcast channel (PBCH). Data channels include the physical uplink sharing channel (PUSCH) and physical downlink sharing channel (PDSCH). Data may refer to data transmitted via the data channel. Reference signals include the Demodulation Reference Signal (DMRS), Phase Tracking Reference Signal (PTRS), Channel State Information-Reference Signal (CSI-RS), Sounding Reference Signal (SRS), and Positioning Reference Signal (PRS).

[0055] The wireless communication unit 110 can transmit one or more notification information. The notification information may be a master information block (MIB) or a system information block (SIB).

[0056] In this embodiment, the wireless communication unit 110 transmits the anchor cell synchronization signal (SS), PBCH (MIB), and SIB in the anchor cell. The wireless communication unit 110 may also transmit all or part of the non-anchor cell information, specifically PBCH (MIB, DMRS), SIB1, and other SIB information, in the anchor cell's PBCH (MIB) and SIB. In this embodiment, the wireless communication unit 110 may transmit the non-anchor cell synchronization signal (SS) in the non-anchor cell, and may not transmit all or part of the non-anchor cell information, specifically PBCH (MIB, DMRS), SIB1, and other SIB information.

[0057] Furthermore, when a perch carrier is introduced, in this embodiment, the wireless communication unit 110 transmits the perch cell synchronization signal (SS), PBCH (MIB), and SIB in the perch cell. The wireless communication unit 110 may also transmit all or part of the non-perch cell information, specifically PBCH (MIB, DMRS), SIB1, and other SIB information, in the PBCH (MIB), SIB, and SIB of the perch cell. The wireless communication unit 110 may also transmit the non-perch cell synchronization signal (SS) in the non-perch cell, and may not transmit all or part of the non-perch cell information, specifically PBCH (MIB, DMRS), SIB1, and other SIB information.

[0058] Furthermore, the wireless communication unit 110 can transmit RRC messages to the UE200.

[0059] In this embodiment, the wireless communication unit 110 may transmit an RRC message (e.g., an RRCReconfiguration message) to the UE200 in the anchor cell that includes all or part of the non-anchor cell information, specifically PBCH (MIB, DMRS), SIB1, and other SIB information. The non-anchor cell information included in this RRC message may be information that is not transmitted in the non-anchor cell from the perspective of NES.

[0060] Furthermore, if a perch carrier is introduced, in this embodiment, the wireless communication unit 110 may transmit an RRC message (e.g., an RRCReconfiguration message) to the UE200 in the perch cell that includes all or part of the non-perch cell information, specifically PBCH (MIB, DMRS), SIB1, and other SIB information. The non-perch cell information included in this RRC message may be information that is not transmitted in the non-perch cell from the perspective of NES.

[0061] The wireless communication unit 110 sends a paging message to the UE200. The wireless communication unit 110 receives an initial access request from the UE200 and sends a response to the UE200 containing the necessary initial access procedure. The initial access may be a random access procedure.

[0062] In this embodiment, the wireless communication unit 110 may be configured as a transmitting unit in the first cell to transmit the synchronization signal and system information of the first cell. In addition, the wireless communication unit 110 may be configured as a transmitting unit in the second cell to transmit the synchronization signal of the second cell.

[0063] The wireless communication unit 110 can receive information transmitted by the wireless communication unit 210, which will be described later. Furthermore, the wireless communication unit 110 can transmit information received by the wireless communication unit 210, which will also be described later.

[0064] The information provision unit 120 provides non-anchor cell (or non-parch cell) system information to the UE200.

[0065] In the embodiment, the system information of a non-anchor cell (or non-part cell) may specifically be all or part of PBCH (MIB, DMRS), SIB1, and other SIB information. All or part of this system information may be understood as information necessary to access the non-anchor cell (or non-part cell). In the embodiment, from the perspective of NES, the broadcast information provision unit 120 does not have to provide all or part of the system information of a non-anchor cell (or non-part cell) to the UE200. In the embodiment, the broadcast information provision unit 120 may provide all or part of the system information of a non-anchor cell (or non-part cell) that is not transmitted in the non-anchor cell (or non-part cell) to the UE200.

[0066] Specifically, the notification information provision unit 120 may provide the system information of the non-anchor cells (or non-partic cells) listed below to the UE200 in the PBCH (MIB) and SIB of the anchor cell (or partic cell), or it may provide it to the UE200 by including it in an RRC message (for example, an RRCReconfiguration message). Note that the RRC message is not limited to existing messages, but may also be a newly defined message.

[0067] Option 1, shown below, is an example of information elements for system information of non-anchor cells (or non-parch cells) separated by PCI (Physical Cell ID), and Option 2 is an example of information elements for system information of non-anchor cells (or non-parch cells) separated by beam index. Option 1) Anchor carrier or Perch carrier MIB / SIB PBCH(MIB, DMRS) for PCI=1 systemFrameNumber subCarrierSpacingCommon dmrs-TypeA-Position pdcch-ConfigSIB1 cellBarrired intraFreqReselection PBCH(MIB, DMRS) for PCI=2 systemFrameNumber subCarrierSpacingCommon dmrs-TypeA-Position pdcch-ConfigSIB1 cellBarrired intraFreqReselection PBCH(MIB, DMRS) for PCI=3 systemFrameNumber subCarrierSpacingCommon dmrs-TypeA-Position pdcch-ConfigSIB1 cellBarrired intraFreqReselection Option 2) Anchor carrier or Perch carrier MIB / SIB PBCH(MIB,DMRS) for beam index=1 systemFrameNumber subCarrierSpacingCommon dmrs-TypeA-Position pdcch-ConfigSIB1 cellBarrired intraFreqReselection PBCH(MIB, DMRS) for beam index=2 systemFrameNumber subCarrierSpacingCommon dmrs-TypeA-Position pdcch-ConfigSIB1 cellBarrired intraFreqReselection PBCH(MIB, DMRS) for beam index=3 systemFrameNumber subCarrierSpacingCommon dmrs-TypeA-Position pdcch-ConfigSIB1 cellBarrired intraFreqReselection,

[0068] In this embodiment, the notification information provision unit 120 may be configured in the first cell as a control unit that causes the second cell to transmit system information to the transmission unit.

[0069] The inter-device information exchange unit 130 acquires and exchanges necessary information between base stations 100. If the base station 100 has a configuration of CUs and DUs, information exchange may take place between different CUs (for example, between CU1 and CU2) or between different DUs (for example, between DU1 and DU2). Information exchange may include sending information in response to a request from the other party, sending information unilaterally to the other party, and receiving information from the other party and sending a confirmation of receipt back to the other party.

[0070] In this embodiment, the inter-device information exchange unit 130 obtains information on non-anchor cells (or non-perch cells), specifically PBCH (MIB, DMRS), SIB1, and all or part of other SIB information from other base stations. This non-anchor cell (or non-perch cell) information may be categorized by PCI or by beam index.

[0071] In addition, in the embodiment, the inter-device information exchange unit 130 exchanges with other base stations all or part of the frequency list of anchor cells (or perch cells) and DownlinkConfigCommon, the frequency list of non-anchor cells (or non-perch cells) and DownlinkConfigCommon, and the linking relationships between anchor cells (or perch cells) and non-anchor cells (or non-perch cells).

[0072] In this embodiment, the messages exchanged between the device information exchange unit 130 and other base stations may specifically be an Xn setup request message, an Xn setup response message, or an Xn configuration update message, or an Xn configuration update ACK message. Note that the messages used for information exchange are not limited to existing messages, but may also be newly defined messages.

[0073] The device information exchange unit 130 in the embodiment may be configured as a control unit that transmits the synchronization signal and system information of the first cell and the system information of the second cell to other base stations forming the first cell, and provides the system information of the second cell.

[0074] The control unit 140 controls each functional block that constitutes the base station 100. For example, the control unit 140 controls the transmission and reception of wireless signals by the wireless communication unit 110, the provision of non-anchor cell system information by the notification information provision unit 120, and the acquisition and exchange of information by the inter-device information exchange unit 130.

[0075] The control unit 140 receives an initial access request from the UE200 and executes the initial access procedure. The control unit 140 performs scheduling for the UE200. The control unit 140 also performs processing related to control signals, such as radio resource control (RRC) signaling.

[0076] (3.2) As shown in the terminal's functional block diagram 6, the UE200 includes a wireless communication unit 210, a cell selection / re-selection execution unit 220, and a control unit 230.

[0077] The wireless communication unit 210 transmits and receives wireless signals to and from the base station 100.

[0078] The wireless communication unit 210 can receive one or more broadcast information from the base station 100. The broadcast information may be MIB / SIB. In this embodiment, the system information received in the anchor cell (or parch cell) may include system information from the non-anchor cell (or non-parch cell), as described above. The broadcast information may also include an information element indicating the resource for the initial access that the UE 200 makes with the base station 100. The resource for the initial access may mean a RACH resource.

[0079] The wireless communication unit 210 can receive RRC messages from the base station 100. In this embodiment, the RRC messages received in the anchor cell (or parch cell) (for example, RRCReconfiguration messages) may include information from non-anchor cells (or non-parch cells), as described above.

[0080] In this embodiment, the wireless communication unit 210 may be configured as a receiving unit in the first cell that receives the synchronization signal and system information of the first cell, as well as the system information of the second cell.

[0081] The wireless communication unit 210 can receive paging messages from the base station 100. The wireless signal transmission / reception unit 210 also receives downlink control information for scheduling.

[0082] Furthermore, the wireless communication unit 210 can receive information transmitted by the wireless communication unit 110. Also, the wireless communication unit 210 can transmit information received by the wireless communication unit 110.

[0083] The cell selection / re-selection execution unit 220 performs cell selection and cell re-selection. The targets of cell selection / re-selection may include anchor cells, parchment cells, non-anchor cells, and non-parchment cells. In the embodiment, the cell selection / re-selection execution unit 220 can perform cell selection of non-anchor cells (or non-parchment cells) based on information of non-anchor cells (or non-parchment cells) received in the anchor cell (or parchment cell), specifically PBCH (MIB, DMRS), SIB1, and other SIB information, in whole or in part.

[0084] The cell selection / re-selection execution unit 220 of the embodiment may be configured as a control unit that accesses the second cell based on the system information of the second cell received by the first cell.

[0085] The control unit 230 controls each functional block that makes up the UE200. For example, the control unit 230 controls the transmission and reception of wireless signals by the wireless communication unit 210 and the selection and reselection of cells by the cell selection / reselection execution unit 220.

[0086] (4) Operation of wireless communication systems (4.1) Challenges In 6G, for example, in order to support high-speed, high-capacity services, it may be necessary to use high-frequency bands that consume a lot of power, so in order to suppress power consumption, the system may be designed with NES in mind.

[0087] From an NES perspective, it is conceivable to introduce a new cell (or carrier) concept called a non-anchor cell (or non-anchor carrier), separate from the anchor cell (or anchor carrier), and reduce the amount of information transmitted by the non-anchor cell (or non-anchor carrier) to suppress power consumption for the entire network.

[0088] If the transmission of information necessary to access cells is reduced in non-anchor cells (or non-anchor carriers), the challenge remains of how to enable terminals to access non-anchor cells (or non-anchor carriers).

[0089] The technical challenges that this disclosure seeks to address are not limited to those mentioned above, and other technical challenges not mentioned herein will be clearly understood by a person with ordinary skill in the art to which this disclosure pertains, based on the description herein.

[0090] (4.2) Examples of Operation The following explanation will use anchor cells and non-anchor cells, but anchor cells can be understood as being replaced with parch cells and non-anchor cells as non-parch cells. Example of operation 1 shows an example in which an anchor cell transmits all or part of the non-anchor cell information, specifically PBCH (MIB, DMRS), SIB1, and other SIB information. All or part of the non-anchor cell information transmitted by the anchor cell does not need to be transmitted by the non-anchor cell. Example of operation 2 shows an example in which an anchor cell obtains all or part of the non-anchor cell information, specifically PBCH (MIB, DMRS), SIB1, and other SIB information, transmitted by the anchor cell from another base station. Example of operation 3 shows an example in which an anchor cell and a non-anchor cell are linked by exchanging frequency lists of the anchor cell and non-anchor cell with another base station.

[0091] (4.2.1) Operation Example 1 Figure 7 shows a first embodiment. Base station 100A provides an anchor cell composed of an anchor carrier in the 800 MHz frequency band, for example. In contrast, base station 100B provides a non-anchor cell composed of a non-anchor carrier in the 3.7 GHz frequency band, for example. The area covered by the frequency of base station 100A is shown by a solid line, and the area covered by the frequency of base station 100B is shown by a dashed line.

[0092] In Figure 7, base station 100B transmits the synchronization signal (SS) for non-anchor cells, but does not need to transmit all or part of the system information from an NES perspective. In contrast, base station 100A may transmit all or part of the system information for non-anchor cells that base station 100B does not transmit, in anchor cells.

[0093] Figure 8 shows the sequence in the first embodiment. In Figure 8, base station 100B transmits a non-anchor cell synchronization signal (SS) in a non-anchor cell. However, from an NES perspective, base station 100B does not transmit all or part of the non-anchor cell information, specifically PBCH (MIB, DMRS), SIB1, and other SIB information.

[0094] Base station 100A transmits the anchor cell synchronization signal (SS), PBCH (MIB, DMRS), SIB1, and other SIB information in the anchor cell. Base station 100A may also transmit all or part of the non-anchor cell information, specifically the PBCH (MIB, DMRS), SIB1, and other SIB information, in the anchor cell's PBCH (MIB) and SIB. Base station 100A may also transmit an RRC message to UE200 in the anchor cell that includes all or part of the non-anchor cell information, specifically the PBCH (MIB, DMRS), SIB1, and other SIB information.

[0095] The UE200 can access non-anchor cells provided by base station 100B using non-anchor cell system information received in the anchor cell.

[0096] Thus, from an NES perspective, even if all or part of the information necessary to access non-anchor cells is not transmitted in a non-anchor cell, the UE200 can acquire that information in the anchor cell and reliably access the non-anchor cell.

[0097] (4.2.2) Operation Example 2 The following describes how to acquire system information of non-anchor cells transmitted by an anchor cell. Option 1) The following description is based on the first embodiment shown in Figure 7. Figure 9 shows the first sequence for acquiring non-anchor cell information in the first embodiment, and Figure 10 shows the second sequence for acquiring non-anchor cell information in the first embodiment. Note that in Figures 9 and 10, if base stations 100A and 100B are composed of CUs and DUs, information acquisition may be performed between CU1 and CU2, or between DU1 and DU2.

[0098] In Figure 9, base station 100A queries base station 100B for non-anchor cell information using an Xn setup request message (or Xn configuration update message). Upon receiving the Xn setup request message (or Xn configuration update message), base station 100B sends an Xn setup response message (or Xn configuration update ACK message) to base station 100A, for example, for each PCI, which includes all or part of the non-anchor cell information, specifically PBCH (MIB, DMRS), SIB1, and other SIB information.

[0099] Figure 10 differs from Figure 9 in that for each beam index, an Xn setup response message (or Xn configuration update ACK message) is received that includes all or part of the non-anchor cell information, specifically PBCH (MIB, DMRS), SIB1, and other SIB information.

[0100] As a result, base station 100A can obtain information about the non-anchor cell of base station 100B, and can transmit all or part of the non-anchor cell information, specifically PBCH (MIB, DMRS), SIB1, and other SIB information, to UE200 in the anchor cell.

[0101] Option 2) Figure 11 shows a second embodiment. Both base stations 100A and 100B provide an anchor cell and a non-anchor cell. Base station 100A provides an anchor cell consisting of, for example, an anchor carrier in the 2GHz frequency band and a non-anchor cell consisting of, for example, a non-anchor carrier in the 4.5GHz frequency band. In contrast, base station 100B provides an anchor cell consisting of, for example, an anchor carrier in the 800MHz frequency band and a non-anchor cell consisting of, for example, a non-anchor carrier in the 3.7GHz frequency band. The areas covered by each frequency of base station 100A are shown by solid lines, and the areas covered by each frequency of base station 100B are shown by dashed lines.

[0102] In Figure 11, each base station 100A and 100B transmits the non-anchor cell synchronization signal (SS) in the non-anchor cell, but does not need to transmit all or part of the system information from an NES perspective. Conversely, base stations 100A and 100B may transmit all or part of the system information that is not transmitted in the non-anchor cell in the anchor cell.

[0103] Figure 12 shows the first sequence for acquiring information on a non-anchor cell in the second embodiment, and Figure 13 shows the second sequence for acquiring information on a non-anchor cell in the second embodiment. In Figures 12 and 13, if base stations 100A and 100B are composed of CUs and DUs, information acquisition may be performed between CU1 and CU2, or between DU1 and DU2.

[0104] In Figure 12, base station 100A sends an Xn setup request message (or Xn configuration update message) to base station 100B that includes system information for the 4.5GHz frequency band non-anchor cell provided by base station 100A. Specifically, this system information may include all or part of the PBCH (MIB, DMRS), SIB1, and other SIB information, and may consist of system information for each PCI. In response, when base station 100B receives the Xn setup request message (or Xn configuration update message), it sends an Xn setup response message (or Xn configuration update ACK message) to base station 100A that includes system information for the 3.7GHz frequency band non-anchor cell provided by base station 100B. This system information may also include all or part of the PBCH (MIB, DMRS), SIB1, and other SIB information, and may consist of system information for each PCI.

[0105] Figure 13 differs from Figure 12 in that for each beam index, an Xn setup response message (or Xn configuration update ACK message) is received that includes all or part of the non-anchor cell information, specifically PBCH (MIB, DMRS), SIB1, and other SIB information.

[0106] This allows base stations 100A and 100B to obtain information about the other's non-anchor cell.

[0107] (4.2.3) Operation Example 3 The following describes a method for exchanging information to link anchor cells and non-anchor cells. Option 1) Figure 14 shows a third embodiment. Base station 100A provides anchor cells in the 800MHz frequency band and the 2GHz frequency band, for example. In contrast, base station 100B provides non-anchor cells in the 3.7GHz frequency band and the 4.5GHz frequency band, for example. The areas covered by each frequency of base station 100A are shown by solid lines, and the areas covered by each frequency of base station 100B are shown by dashed lines.

[0108] In Figure 14, base station 100B transmits non-anchor cell synchronization signals (SS) in non-anchor cells in the 3.7GHz and 4.5GHz frequency bands, but does not transmit all or part of the system information from an NES perspective. In contrast, base station 100A may transmit all or part of the system information that base station 100B does not transmit in non-anchor cells in anchor cells in the 800MHz and 2GHz frequency bands.

[0109] Figure 15 shows the first sequence of information exchange between devices in the third embodiment. In Figure 15, if base stations 100A and 100B are composed of CUs and DUs, information exchange may occur between CU1 and CU2, or between DU1 and DU2.

[0110] In Figure 15, base station 100A sends an Xn setup request message (or Xn configuration update message) to base station 100B that includes a frequency list of anchor cells in the 800MHz and 2GHz frequency bands provided by base station 100A, and the DownlinkConfigCommon. In response, upon receiving the Xn setup request message (or Xn configuration update message), base station 100B sends an Xn setup response message (or Xn configuration update ACK message) to base station 100A that includes a frequency list of non-anchor cells in the 3.7GHz and 4.7GHz frequency bands provided by base station 100B, and the DownlinkConfigCommon for each non-anchor cell.

[0111] This allows base station 100A and base station 100B to exchange information with each other, and base station 100A can link the anchor cells of each frequency band with the non-anchor cells of base station 100B in each frequency band.

[0112] For example, when the 800MHz frequency anchor cell is congested, base station 100A may control the Xn setup request message (or Xn configuration update message) to include only the information for the 2GHz frequency band anchor cell, and not the information for the 800MHz frequency band anchor cell. In this way, base station 100A can associate the non-anchor cells of base station 100B in the 3.7GHz and 4.5GHz frequency bands only with the available 2GHz frequency band anchor cell.

[0113] Option 2) Figure 16 shows a second sequence for inter-device information exchange in the second embodiment shown in Figure 11. Note that in Figure 16, if base stations 100A and 100B are composed of CUs and DUs, information exchange may occur between CU1 and CU2, or between DU1 and DU2.

[0114] In Figure 16, base station 100A sends an Xn setup request message (or Xn configuration update message) to base station 100B that includes the frequency list of anchor cells in the 2GHz frequency band provided by base station 100A, the DownlinkConfigCommon for each non-anchor cell, and the relationship between the anchor cells in the 2GHz frequency band and the non-anchor cells in the 4.5GHz frequency band, both provided by base station 100A. In response, when base station 100B receives the Xn setup request message (or Xn configuration update message), it sends an Xn setup response message (or Xn configuration update ACK message) to base station 100A that includes the frequency list of non-anchor cells in the 3.7GHz frequency band provided by base station 100B, the DownlinkConfigCommon for each non-anchor cell, and the relationship between the anchor cells in the 800MHz frequency band and the non-anchor cells in the 3.7MHz frequency band, both provided by base station 100B. This allows base stations 100A and 100B to exchange information with each other and to know the configuration of anchor cells and non-anchor cells under the base station.

[0115] (5) Effects and Benefits As described above, according to the embodiment, an anchor cell (or parch cell) can transmit all or part of the system information of a non-anchor cell (or non-parch cell). Therefore, from the perspective of NES, even if this information is not transmitted in the non-anchor cell (or non-parch cell), the UE200 can receive the necessary information in the anchor cell (or parch cell). As a result, the base station 100 can reliably access the UE200 even in cells to which NES is applied. In addition, the UE200 can reliably access cells to which NES is applied. Furthermore, since the base station 100 can obtain system information of a non-anchor cell (or non-parch cell) from an adjacent base station, it can transmit this information obtained in the anchor cell (or parch cell).

[0116] (6) Other Embodiments Although the contents of the present invention have been described above in accordance with the embodiments, it will be obvious to those skilled in the art that the present invention is not limited to these descriptions and that various modifications and improvements are possible.

[0117] In the above explanation, it has been assumed that non-anchor cells transmit non-anchor cell synchronization signals (SS), but this is not necessarily the case, and non-anchor cell synchronization signals (SS) do not have to be transmitted. In this case, anchor cells may transmit information about non-anchor cell synchronization signals (SS). To this end, base stations may exchange information about non-anchor cell synchronization signals (SS).

[0118] In this disclosure, multiple options and variations may be combined as a single option / variation.

[0119] The block diagrams 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 also be realized by combining software with the one or more of the above devices.

[0120] Functions include, but are not limited to, judgment, decision, judgment, 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.

[0121] For example, the base station 100 and terminal 200 in one embodiment of the present disclosure may function as computers that process the wireless communication method of the present disclosure. Figure 17 is a diagram showing an example of the hardware configuration of the base station 100 and terminal 200 according to one embodiment of the present disclosure. The above-mentioned base station 100 and terminal 200 may be physically configured as computer devices including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

[0122] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the base station 100 and terminal 200 may include one or more of the devices shown in the figure, or it may be configured to omit some of the devices.

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

[0124] 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 units, arithmetic units, registers, and so on.

[0125] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 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. Furthermore, although it has been explained that the above processes are 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 a network via a telecommunications line.

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

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

[0128] The communication device 1004 is hardware (transceiver / receiver 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).

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

[0130] Furthermore, each device, such as the processor 1001 and memory 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.

[0131] Furthermore, the base station 100 and terminal 200 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA), 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.

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

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

[0134] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be reordered, provided they do not contradict each other. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

[0135] The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal can be performed by the base station and at least one other network node (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, it may also be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0136] Information and signals (such as data) can be output from a higher layer (or lower layer) to a lower layer (or higher layer). Input and output may occur via multiple network nodes.

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

[0138] The determination 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).

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

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

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

[0142] The information, signals, etc. described in this disclosure may be represented using any of the various different technologies. 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.

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

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

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

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

[0147] In this disclosure, terms such as "Base Station (BS)", "wireless base station", "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.

[0148] A base station can house one or more (e.g., three) cells (also called sectors). If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which may 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 providing communication services in that coverage.

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

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

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

[0152] 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 Internet of Things (IoT) device such as a sensor.

[0153] Furthermore, the term "base station" in this disclosure may be interpreted as "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 terminal is replaced with communication between multiple terminals (which may be called, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.). In this case, the terminal 200 may have the functions that the base station 100A or 100B 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.

[0154] Similarly, the term "terminal" in this disclosure may be replaced with "base station." In this case, the functions of the terminal 200 described above may be provided by the base station 100A or 100B.

[0155] Figure 18 shows an example of the configuration of vehicle 2001. As shown in Figure 18, vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right 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.

[0156] The drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor.

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

[0158] 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 2027 installed in the vehicle are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an Electronic Control Unit (ECU).

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

[0160] The Information Services Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including car navigation systems, audio systems, speakers, televisions, and radios, and one or more ECUs that control these devices. The Information Services Unit 2012 uses information acquired from external devices via communication modules 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001.

[0161] The Information Services Unit 2012 may include input devices that accept input from external sources (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) and output devices that output to external sources (e.g., displays, speakers, LED lamps, touch panels, etc.).

[0162] 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, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyro systems (e.g., Inertial Measurement Unit (IMU), Inertial Navigation System (INS)), Artificial Intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also sends and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

[0163] 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 drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2029 provided in the vehicle 2001.

[0164] 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 to and from 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.

[0165] 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 to 2029 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 to 2029, 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 information based on the above input.

[0166] The communication module 2013 receives various information (traffic information, signal information, vehicle-to-vehicle information, etc.) transmitted from external devices and displays it on the information service unit 2012 installed in the vehicle. The information service unit 2012 may also be called an output unit, which outputs information (for example, it 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).

[0167] Furthermore, the communication module 2013 stores various information received from external devices in memory 2032, which is available to the microprocessor 2031. Based on the information stored in memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axles 2009, sensors 2021 to 2029, etc., which are provided in the vehicle 2001.

[0168] 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, “determining” may include resolving, selecting, choosing, establishing, or comparing. In other words, "judgment" and "decision" can include considering that some action has been "judged" or "decided." Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0169] The terms “connected,” “coupled,” and any variations 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.

[0170] The reference signal may also be abbreviated as RS, and may be called Pilot depending on the applicable standard.

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

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

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

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

[0175] A wireless frame may consist of one or more frames in the time domain. Each of these frames in the time domain may be called a subframe. A subframe may further consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0176] Numerology may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerology may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

[0177] A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols or Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols). A slot may also be a time unit based on neurology.

[0178] A slot may include multiple mini-slots. Each mini-slot may consist of one or more symbols in the time domain. Mini-slots may also be called sub-slots. Mini-slots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may be called a PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may be called a PDSCH (or PUSCH) mapping type B.

[0179] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.

[0180] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1 to 13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0181] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each terminal to allocate radio resources (such as the frequency bandwidth and transmission power available to each terminal) in TTI units. However, the definition of TTI is not limited to this.

[0182] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Note that when a TTI is given, the actual time interval (e.g., number of symbols) in which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.

[0183] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.

[0184] A TTI with a time length of 1 ms may also be called a normal TTI (TTI in LTE Rel. 8-12), a long TTI, a normal subframe, a long subframe, or a slot. A TTI shorter than a normal TTI may also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini slot, a subslot, or a slot.

[0185] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

[0186] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.

[0187] Furthermore, the time domain of RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0188] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0189] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0190] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the carrier's common reference point. PRBs may be defined and numbered within a BWP.

[0191] A BWP may include BWPs for UL (UL BWP) and BWPs for DL ​​(DL BWP). One or more BWPs may be configured within a single carrier for a UE.

[0192] At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0193] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

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

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

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

[0197] 10 Wireless communication system 20 Network 100 Base station 110 Wireless communication unit 120 Notification information provision unit 130 Inter-device information exchange unit 140 Control unit 200 Terminal 210 Wireless communication unit 220 Cell selection / re-selection execution unit 230 Control unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Left and right front wheels 2008 Left and right rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 Rotation speed sensor 2023, air pressure sensor 2024, vehicle speed sensor 2025, acceleration sensor 2026, brake pedal sensor 2027, shift lever sensor 2028, object detection sensor 2029, accelerator pedal sensor 2030, driver assistance system unit 2031, microprocessor 2032, memory (ROM, RAM) 2033, communication port (IO port)

Claims

1. A base station comprising: a transmitting unit in a first cell that transmits a synchronization signal and system information for the first cell; and a control unit in the first cell that causes the transmitting unit to transmit system information for a second cell.

2. The base station according to claim 1, wherein the transmission of system information of the second cell is restricted.

3. The base station according to claim 1, further comprising a receiving unit for receiving system information of the second cell from other base stations forming the second cell.

4. A communication method comprising: a transmission step of transmitting a synchronization signal and system information of the first cell in the first cell; and a step of transmitting system information of the second cell in the first cell.

5. A terminal comprising a receiving unit in the first cell that receives the synchronization signal and system information of the first cell and the system information of the second cell, and a control unit that accesses the second cell based on the system information of the second cell received in the first cell.

6. A base station comprising: a control unit that provides the system information of the second cell to other base stations forming the first cell, which transmit the synchronization signal and system information of the first cell and the system information of the second cell in the first cell; and a transmission unit that transmits the synchronization signal of the second cell in the second cell.

Images