Base station and terminal

Abstract

[Problem] The present embodiment makes it possible to achieve efficient communication in a system in which a terminal acquires system information on demand, and to reduce power consumption of the terminal and a network. [Solution] Provided is a first base station comprising: a reception unit that receives, via a first cell provided by the first base station, a transmission request for system information from a terminal and that receives, from a second base station which provides a second cell for transmitting the system information in response to the request from the terminal, setting information for the terminal to access the second cell; and a transmission unit that transmits the setting information to the terminal.

Description

Base Station and Terminal

[0001] The present invention relates to a base station and a terminal in a wireless communication system.

[0002] In 3GPP (Registered Trademark) (3rd Generation Partnership Project) Rel-19, studies are being advanced towards supporting NES (Network Energy Saving), and procedures and signaling methods for supporting on-demand SIB1 are being discussed.

[0003] On-demand SBI1 is supported by NES cells that do not broadcast system information. In the operation of on-demand SBI1, the terminal transmits WUS (Wake-Up Signal) to the NES cell using a WUS (Wake-Up Signal) config for requesting on-demand SIB1, and makes an on-demand SIB1 request. The WUS config is different setting information for each NES cell.

[0004] 3GPP TS 38.300 V18.2.0(2024-06)3GPP TS 38.401 V18.2.0(2024-06)

[0005] However, when reselection from the NES cell first selected by the terminal (for example, NES cell #1) to another NES cell (for example, NES cell #2) is performed, the terminal needs to obtain a WUS config for communicating with NES cell #2 from cell A in order to trigger the transmission of on-demand SIB1 to the candidate NES cell #2 for reselection. Thus, it is not efficient for the terminal to always camp on cell A and communicate with cell A in order to obtain the WUS config, which may cause more power consumption in both the network and the terminal.

[0006] The first base station in this embodiment includes a receiving unit that receives a request to transmit system information from a terminal via a first cell provided by the first base station, and receives setting information for the terminal to access the second cell from a second base station that provides a second cell that transmits system information in response to the request from the terminal, and a transmitting unit that transmits the setting information to the terminal.

[0007] According to this embodiment, efficient communication is achieved in a system where the terminal acquires system information on demand, and power consumption in the terminal and network can be reduced.

[0008] This is a diagram illustrating the wireless communication system in this embodiment. This is a diagram illustrating an example of operation when the on-demand SIB1 method is applied. This is a diagram illustrating an example of operation when the on-demand SIB1 method is applied. This is a diagram illustrating an example of operation when the on-demand SIB1 method is applied. This is a diagram illustrating an example of operation when the on-demand SIB1 method is applied. This is a sequence diagram showing an example of operation of the wireless communication system in Example 1 of this embodiment. This is a sequence diagram showing an example of operation of the wireless communication system in Example 1 of this embodiment. This is a sequence diagram showing an example of operation of the wireless communication system in Example 2 of this embodiment. This is a sequence diagram showing an example of operation of the wireless communication system in Example 2 of this embodiment. This is a sequence diagram showing an example of operation of the wireless communication system in Example 3 of this embodiment. This is a sequence diagram showing an example of operation of the wireless communication system in Example 3 of this embodiment. This is a diagram illustrating an example of operation of the wireless communication system in this embodiment. This is a diagram illustrating an example of operation of the wireless communication system in this embodiment. This is a diagram illustrating an example of the functional configuration of a base station in this embodiment. This is a diagram illustrating an example of the functional configuration of a terminal in this embodiment. This is a diagram illustrating an example of the hardware configuration of a base station or terminal in this embodiment. This is a diagram illustrating an example of the configuration of a vehicle in this embodiment.

[0009] This embodiment 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 applies are not limited to those described below.

[0010] The wireless communication system of this embodiment operates using existing technology. Existing technology is, for example, wireless communication technology based on communication standards such as the 3GPP standard. Existing technology is, for example, NR (New Radio), but is not limited to existing NR. As used herein, the term "NR" has a broad meaning that includes NR (5G) and later systems (e.g., 6G), unless otherwise specified.

[0011] In the embodiments 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. In NR, the above terms will be referred to as SS, PSS, SSS, PBCH, PRACH, etc., without any particular distinction from LTE.

[0012] In this embodiment, the duplex method may be a TDD (Time Division Duplex) method, an FDD (Frequency Division Duplex) method, or any other method (for example, a Flexible Duplex).

[0013] In this embodiment, "configuring" wireless parameters means either pre-configuring predetermined values, or configuring wireless parameters notified by the base station 10 or terminal 20.

[0014] Figure 1 shows an example of the configuration of a wireless communication system in this embodiment. The wireless communication system in this embodiment includes a base station 10 and a terminal 20, as shown in Figure 1. Although Figure 1 shows one base station 10 and one terminal 20, this is an example, and there may be multiple base stations 10 and terminals 20.

[0015] 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, PSS and SSS. System information is transmitted, for example, via 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 base station 10 and terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to DL or UL. Furthermore, both the base station 10 and the terminal 20 may communicate via secondary cells (SCell) and primary cells (PCell) using Carrier Aggregation (CA). In addition, the terminal 20 may communicate via the primary cell of base station 10 and the primary secondary cell group cell (PSCell) of another base station 10 using Dual Connectivity (DC).

[0016] Base station 10 may also be referred to as a RAN (Radio Access Network) node. Base station 10 is, for example, a gNodeB (gNB) in NR.

[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 measurements based on the reception results of these reference signals.

[0018] In the following explanation, " / " means "and / or" unless otherwise specified, or unless the context makes it clear that it has a different meaning.

[0019] In 3GPP Rel-19, discussions are underway regarding support for NES (Network Energy Saving), and procedures and signaling methods for supporting on-demand SIB1 are being discussed. For example, methods for triggering using UL WUS with existing signals / channels, methods for providing WUS configuration information to UEs, and information exchange between gNBs are being considered.

[0020] 3GPP is considering on-demand SIB1 methods for UEs in the RRC_INACTIVE / RRC_IDLE state, focusing on the following cases 1-3.

[0021] Case 1: Option 1 + A + X Case 2: Option 1 + B + X Case 3: Option 2 + B + Y Here, options 1 / 2 / A / B / X / Y are defined as follows:

[0022] (Regarding the target cell for UL WUS transmission) Option 1: The UE sends UL WUS to the NES cell.

[0023] Option 2: UE sends UL WUS to cell A.

[0024] "Cell A" is defined as a cell that periodically transmits SIB1, at least within its own cell. "NES cell" is defined as a cell that may transmit SIB1 in response to UL WUS from the UE. In other words, SIB1 is not broadcast in NES cells, and NES cells support on-demand SIB1.

[0025] (Regarding the provision of UL WUS transmission configuration information) Option A: The UE obtains UL WUS configuration information from the NES cell.

[0026] Option B: UE retrieves UL WUS configuration information from cell A.

[0027] (Regarding SIB1 reception) Option X: The UE receives on-demand SIB1 from the NES cell.

[0028] Option Y: UE receives on-demand SIB1 from cell A.

[0029] Figure 2-4 shows the operation of the on-demand SIB1 method in each of the cases 1-3.

[0030] In Figure 2, which illustrates the operation of Case 1, in step S1, the terminal receives an UL (Uplink) WUS (Wake-Up Signal) config from the RAN node (NES cell). The UL WUS config contains the information necessary for the UE to request an on-demand SIB1. Based on the information contained in the WUS config, the UE decides when, on what frequency, and how to transmit the WUS. The WUS config also includes RACH (Random Access Channel) configuration information for requesting the SIB1.

[0031] In step S2, the terminal sends an on-demand SIB1 request to the RAN node. For example, if the terminal requires an on-demand SIB1, it sends a WUS based on the UL WUS config. The WUS is sent as a RACH preamble.

[0032] For example, a RAN node sends a RAR (Random Access Response) to a UE that has received a WUS. The RAR contains information about sending SIB1. The RAN node sends SIB1 to the UE according to the schedule specified in the RAR.

[0033] In step S3, the terminal receives an on-demand SIB1 from the RAN node. The terminal obtains the information necessary to access the cell from the received on-demand SIB1.

[0034] In Figure 3, which shows an example of operation in Case 2, in step S1, the terminal receives the WUS config from the RAN node (cell A) via an SIB or RRC release message. In step S2, the terminal sends an on-demand SIB1 request to the RAN node (NES cell). In step S3, the terminal receives the on-demand SIB1 from the RAN node (NES cell).

[0035] In Figure 4, which shows an example of operation in Case 3, in step S1, the terminal receives the WUS config from the RAN node (cell A) via an SIB or RRC release message. In step S2, the terminal sends an on-demand SIB1 request to the RAN node (NES cell). In step S3, the terminal receives the on-demand SIB1 from the RAN node (NES cell).

[0036] The following has been agreed upon within 3GPP regarding on-demand SIB1:

[0037] - Assume the UE reuses the RACH procedure to request an on-demand SIB1.

[0038] - UL WUS configuration includes at least RACH configuration.

[0039] - The UE needs to know the UL WUS configuration to know which cell's SIB1 to request.

[0040] Here, as shown in FIG. 5, in a wireless communication system, there are a plurality of NES cells that can be selected by a terminal, and it is assumed that reselection from a certain NES cell (for example, NES cell #1) to another NES cell (for example, NES cell #2) may occur.

[0041] In such a case, based on the current agreements in 3GPP, the terminal needs to camp on cell A on which it was previously camped or another cell A to trigger the transmission of on-demand SIB1 to the candidate NES cell #2 for reselection, and obtain the UL WUS config for accessing NES cell #2 from cell A. Thus, it is not efficient for the terminal to always camp on cell A and communicate with cell A to obtain the UL WUS config, which may cause more power consumption in both the network and the terminal.

[0042] According to this embodiment, efficient communication in the method (on-demand SIB1) in which the terminal obtains system information on demand can be realized, and power consumption in the terminal and the network can be reduced. Hereinafter, each example in this embodiment will be described.

[0043] The examples in this embodiment may be executed independently of each other, or any combination of a plurality of examples may be executed.

[0044] In the following description, the RAN node 10-1 that provides (or manages) NES cell #1 is represented as RAN node (NES cell #1) 10-1. The RAN node 10-2 that provides NES cell #2 is represented as RAN node (NES cell #2) 10-2. The RAN node 10-3 that provides cell A is represented as RAN node (cell A) 10-3.

[0045] The WUS config is an example of the configuration information used to access the NES cell. The WUS config may be the UL WUS config.

[0046] SIB1 is an example of the system information. The on-demand SIB1 is an example of the on-demand system information.

[0047] In the NES cell, SIB1 is not broadcast. The NES cell supports on-demand SIB1.

[0048] Cell A is a cell that periodically transmits SIB1 at least in its own cell.

[0049] (Example 1) The RAN node that provides the NES cell notifies other RAN nodes of the configuration information for accessing the NES via the Xn interface.

[0050] As shown in FIG. 6, in step S101, the RAN node (NES cell #2) 10-2 transmits the WUS config for accessing the NES cell #2 to the RAN node (NES cell #1) 10-1 via the Xn interface.

[0051] In step S102, the RAN node (NES cell #1) 10-1 transmits the WUS config for accessing the NES cell #1 to the RAN node (NES cell #2) 10-2 via the Xn interface.

[0052] In FIG. 6, after step S102, step S101 may be executed.

[0053] When the RAN node 10 transmits and receives at least one of the Xn setup request message, Xn setup message, RAN node configuration update message, or RAN node configuration update Ack message to / from another RAN node, it may transmit the WUS config. The WUS config may be included in at least one of, for example, the Xn setup request message, Xn setup message, RAN node configuration update message, or RAN node configuration update Ack message, or may be transmitted simultaneously with these messages.

[0054] An architecture in which the functions of RAN node 10 are divided into CU (Central Unit) and DU (Distributed Unit) is called a split RAN node. A split RAN node is, for example, a split gNB. This embodiment may also be applied to a split RAN node. In addition to the WUS config, RAN node 10 may notify other RAN nodes 10 of the SIB1.

[0055] In the example in Figure 7, for instance, NES cell #1 is the cell initially selected by terminal 20, and NES cell #2 is the cell re-selected by NES cell #1.

[0056] As shown in Figure 7, in step S201, RAN node-DU (NES cell #2) 10-2-DU sends the WUS config and SIB1 for accessing NES cell #2 to RAN node-CU (NES cell #2) 10-2-CU via the F1 interface.

[0057] In step S202, RAN node-CU (NES cell #2) 10-2-CU sends the WUS config and SIB1 for accessing NES cell #2 to RAN node-CU (NES cell #1) 10-1-CU.

[0058] In step S203, RAN node-CU (NES cell #1) 10-1-CU sends the WUS config and SIB1 for accessing NES cell #2 to RAN node-DU (NES cell #1) 10-1-DU via the F1 interface.

[0059] In step S204, RAN node-DU (NES cell #1) 10-1-DU sends the WUS config and SIB1 for accessing NES cell #2 to terminal 20 using a system information message or RRC message (e.g., an RRC release message).

[0060] In this way, terminal 20 can obtain the WUS config and SIB1 to access other NES cells that are not camp-on. Using this information, terminal 20 can perform on-demand SIB1 operations on other NES cells.

[0061] In the example in Figure 8, for example, NES cell #2 is the cell initially selected by terminal 20, and NES cell #1 is the cell re-selected by NES cell #2.

[0062] As shown in Figure 8, in step S301, RAN node-DU (NES cell #1) 10-1-DU sends the WUS config and SIB1 for accessing NES cell #1 to RAN node-CU (NES cell #1) 10-1-CU via the F1 interface.

[0063] In step S302, RAN node-CU (NES cell #1) 10-1-CU sends the WUS config and SIB1 for accessing NES cell #1 to RAN node-CU (NES cell #2) 10-2-CU.

[0064] In step S303, RAN node-CU (NES cell #2) 10-2-CU sends the WUS config and SIB1 for accessing NES cell #1 to RAN node-DU (NES cell #2) 10-2-DU via the F1 interface.

[0065] In step S304, RAN node-DU (NES cell #2) 10-2-DU sends the WUS config and SIB1 to terminal 20 to access NES cell #1.

[0066] In the examples in Figures 7 and 8, WUS config and SIB1 may be transmitted when at least one of the following is sent or received: Xn setup request message, Xn setup message, RAN node configuration update message, RAN node configuration update Ack message, F1 setup request message, F1 setup response message, GNB-DU configuration update, GNB-DU configuration update ACKNOWLEDGE, GNB-CU configuration update, or GNB-CU configuration update ACKNOWLEDGE; they may be included in these messages; or they may be transmitted simultaneously with these messages.

[0067] (Example 2) According to Example 2, the WUS config may be transmitted from one NES cell to another NES cell via the RAN node 10 that provides cell A.

[0068] As shown in Figure 9, in step S401, RAN node (NES cell #2) 10-2 sends a WUS config for accessing NES cell #2 to RAN node (cell A) 10-3 via the Xn interface.

[0069] In step S402, RAN node (NES cell #1) 10-1 sends a WUS config for accessing NES cell #1 to RAN node (cell A) 10-3 via the Xn interface.

[0070] In step S403, RAN node (cell A) 10-3 sends a WUS config for accessing NES cell #1 to RAN node (NES cell #2) 10-2 via the Xn interface.

[0071] In step S404, RAN node (cell A) 10-3 sends the WUS config and SIB1 for accessing NES cell #2 to RAN node (NES cell #1) 10-1 via the Xn interface.

[0072] In the example shown in Figure 9, RAN node 10 may send a WUS config when it has sent or received at least one of the following messages to or from other RAN nodes: an Xn setup request message, an Xn setup message, a RAN node configuration update message, or a RAN node configuration update Ack message. The WUS config may be included in, for example, at least one of the following messages: an Xn setup request message, an Xn setup message, a RAN node configuration update message, or a RAN node configuration update Ack message, or it may be sent simultaneously with these messages.

[0073] Example 2 may also be applied to a split RAN node architecture.

[0074] As shown in Figure 10, in step S501, RAN node-CU (NES cell #2) 10-2-CU sends a WUS config for accessing NES cell #2 to RAN node (cell A) 10-3 via the Xn interface.

[0075] In step S502, RAN node-CU (NES cell #1) 10-1-CU sends a WUS config for accessing NES cell #1 to RAN node (cell A) 10-3 via the Xn interface.

[0076] In step S503, RAN node (cell A) 10-3 sends a WUS config for accessing NES cell #1 to RAN node-CU (NES cell #2) 10-2-CU via the Xn interface.

[0077] In step S504, RAN node (cell A) 10-3 sends a WUS config for accessing NES cell #2 to RAN node-CU (NES cell #1) 10-1-CU via the Xn interface.

[0078] In step S505, RAN node-CU (NES cell #2) 10-2-CU sends the WUS config for accessing NES cell #1 to RAN node-DU (NES cell #2) 10-2-DU via the F1 interface.

[0079] In step S506, RAN node-CU (NES cell #1) 10-1-CU sends a WUS config for accessing NES cell #2 to RAN node-DU (NES cell #1) 10-1-DU via the F1 interface.

[0080] In the example shown in Figure 10, WUS config and SIB1 may be transmitted when at least one of the following is sent or received: Xn setup request message, Xn setup message, RAN node configuration update message, RAN node configuration update Ack message, F1 setup request message, F1 setup response message, GNB-DU configuration update, GNB-DU configuration update ACKNOWLEDGE, GNB-CU configuration update, or GNB-CU configuration update ACKNOWLEDGE; they may be included in these messages; or they may be transmitted simultaneously with these messages.

[0081] (Example 3) According to Example 3, the WUS config may be sent from one RAN node-DU to another RAN node-DU via the D2 interface, as shown in Figure 11.

[0082] In step S601 of Figure 11, RAN node-DU (NES cell #2) 10-2-DU sends a WUS config for accessing NES cell #2 to RAN node-DU (NES cell #1) 10-1-DU via the D2 interface.

[0083] In step S602, RAN node-DU (NES cell #1) 10-1-DU sends the WUS config for accessing NES cell #1 to RAN node-DU (NES cell #2) 10-2-DU via the D2 interface.

[0084] For example, as shown in Figure 12, the RAN node-DU providing cell A and the multiple RAN node DUs providing NES cells may each send and receive WUS config via the D2 interface.

[0085] In step S701 of Figure 12, RAN node-DU (NES cell #2) 10-2-DU sends a WUS config for accessing NES cell #2 to RAN node-DU (cell A) 10-3-DU.

[0086] In step S702, RAN node-DU (NES cell #1) 10-1-DU sends a WUS config for accessing NES cell #1 to RAN node-DU (cell A) 10-3-DU.

[0087] In step S703, RAN node-DU (cell A) 10-3-DU sends a WUS config for accessing NES cell #2 to RAN node-DU (NES cell #1) 10-1-DU.

[0088] In step S704, RAN node-DU (cell A) 10-3-DU sends a WUS config for accessing NES cell #1 to RAN node-DU (NES cell #2) 10-2-DU.

[0089] In the examples shown in Figures 11 and 12, the WUS config may be sent when, for example, at least one of the following is sent: a D2 setup request message, a D2 setup response, a RAN node configuration update message, or a RAN node configuration update Ack message; it may be included in these messages; or it may be sent simultaneously with these messages.

[0090] Figure 13 shows an example of the operation of the wireless communication system in this embodiment.

[0091] In step S11 of Figure 13, terminal 20 receives the WUS config from RAN node (cell A) 10-3 via an SIB or RRC release message.

[0092] In step S12, terminal 20 sends an on-demand SIB1 request to RAN node (NES cell #1) 10-1.

[0093] For example, RAN node (NES cell #1) 10-1 has already obtained the WUS config of NES cell #2 by following one of the procedures shown in Figure 6-12.

[0094] In step S13, terminal 20 receives an on-demand SIB1 from RAN node (NES cell #1) 10-1, which contains a WUS config for accessing NES cell #2. This allows terminal 20 to communicate with NES cell #2 using the received WUS config for accessing NES cell #2.

[0095] Figure 14 shows an example of the operation of the wireless communication system in this embodiment.

[0096] In step S21 of Figure 14, terminal 20 receives the WUS config from RAN node (cell A) 10-3 via an SIB or RRC release message.

[0097] In step S22, terminal 20 sends an on-demand SIB1 request to RAN node (NES cell #1) 10-1.

[0098] For example, RAN node (NES cell #1) 10-1 has already obtained the WUS config and SIB1 of NES cell #2 by following one of the procedures shown in Figure 6-12.

[0099] In step S23, terminal 20 receives an on-demand SIB1 from RAN node (NES cell #1) 10-1, which includes a WUS config for accessing NES cell #2. This allows terminal 20 to communicate with NES cell #2 using the received WUS config and SIB1 for accessing NES cell #2.

[0100] Traditionally, when a terminal switched cells from its initially selected NES cell (e.g., NES cell #1) to another NES cell (e.g., NES cell #2), the terminal had to communicate with cell A, obtain a WUS config from cell A to access NES cell #2, and then use this obtained WUS config to retrieve SIB1 from NES cell #2.

[0101] According to this embodiment, since multiple NES cells can exchange WUS config or WUS config in addition to SIB1 with each other, even if a terminal re-selects NES cell #1 to NES cell #2, the terminal can obtain the SIB1 of NES cell #2 without accessing cell A.

[0102] For example, according to this embodiment, the terminal can obtain a WUS config for directly accessing NES cell #2 from NES cell #1, use the obtained WUS config to send a WUS to NES cell #2, and obtain an SIB1 from NES cell #2.

[0103] For example, according to this embodiment, the terminal can obtain the WUS config and the SIB1 of NES cell #2 for direct access to NES cell #2 from NES cell #1.

[0104] Thus, according to this embodiment, the procedure for the terminal to communicate with cell A can be omitted, resulting in more efficient communication and further reduction of power consumption.

[0105] (Device Configuration) Next, an example of the functional configuration of the base station 10 and terminal 20 that perform the processes and operations described above will be explained. The base station 10 and terminal 20 include the functions to carry out the embodiments described above. However, the base station 10 and terminal 20 may each be equipped with only some of the functions in the embodiments.

[0106] <Base Station> Figure 15 is a diagram showing an example of the functional configuration of the base station 10 in this embodiment. As shown in Figure 15, 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 15 is merely an example. Any functional classification and functional unit names are acceptable as long as they can perform the operations according to this embodiment.

[0107] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 and transmitting the signal wirelessly. The transmitting unit 110 also transmits setting information, instructions, and notifications related to the low-power wake-up signal to the terminal 20. The transmitting unit 110 also transmits notifications to the terminal regarding the switching of monitoring operations. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 and obtaining information from the received signals, for example, information from a higher layer. The transmitting unit 110 also has the function of transmitting PSS, SSS, PBCH, DL / UL control signals, etc. to the terminal 20. The receiving unit 120 also receives inter-network node messages from other network nodes.

[0108] The setting unit 130 stores pre-set setting information and various setting information to be transmitted to the terminal 20. The content of the setting information includes, for example, information related to measurements in low-power signals.

[0109] As described in the embodiment, the control unit 140 performs control related to setting, instructing, and notifying about low-power wake-up signals and the like. The signal transmission function unit of the control unit 140 may be included in the transmission unit 110, and the signal reception function unit of the control unit 140 may be included in the reception unit 120.

[0110] <Terminal> Figure 16 is a diagram showing an example of the functional configuration of terminal 20 in this embodiment. As shown in Figure 16, 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 16 is merely an example. Any functional classification and name of functional unit is acceptable as long as it can perform the operations according to this embodiment. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as the communication unit.

[0111] The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The transmitting unit 210 also transmits capability information related to the low-power wake-up signal to the base station 10. The receiving unit 220 wirelessly receives various signals and acquires signals from higher layers from the received physical layer signals. The receiving unit 220 also has the function of receiving PSS, SSS, PBCH, DL / UL / SL control signals, etc. transmitted from the base station 10. The receiving unit 220 also receives paging notification information, setting information, instructions, and notifications related to the low-power wake-up signal from the base station 10. For example, the receiving unit 220 receives the low-power wake-up signal from the base station 10. The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. The setting unit 230 also stores pre-set setting information. The content of the setting information is, for example, information related to measurements in low-power signals.

[0112] As described in the embodiment, the control unit 240 performs control related to setting, instructing, and notifying of low-power wake-up signals. The signal transmission function unit of the control unit 240 may be included in the transmission unit 210, and the signal reception function unit of the control unit 240 may be included in the reception unit 220.

[0113] (Hardware Configuration) The block diagrams (Figures 15 and 16) 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.

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

[0115] For example, the base station 10, 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 17 is a diagram showing an example of the hardware configuration of the base station 10 and terminal 20 according to one embodiment of the present disclosure. The above-mentioned base station 10 and terminal 20 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.

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

[0117] 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 the reading and writing of data in the storage device 1002 and auxiliary storage device 1003.

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

[0119] 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 15 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 16 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.

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

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

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

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

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

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

[0126] 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, 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.

[0127] The drive 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.

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

[0129] Signals from various sensors 2021 to 2029 include current signals from current sensor 2021 for sensing motor current, front or rear wheel rotation speed signals acquired by rotation speed sensor 2022, front or 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.

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

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

[0132] 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, 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.

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

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

[0135] 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 drive 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.

[0136] (Configuration relating to this embodiment) (Note 1) A first base station comprising: a receiving unit that receives a request to transmit system information from a terminal via a first cell provided by the first base station, and receives setting information for the terminal to access the second cell from a second base station that provides a second cell that transmits system information in response to a request from the terminal; and a transmitting unit that transmits the setting information to the terminal.

[0137] (Note 2) The receiving unit is the first base station as described in Note 1, which receives system information of the second cell in addition to the setting information for accessing the second cell from the second base station.

[0138] (Note 3) The receiving unit is the first base station as described in Note 1, which receives the setting information for accessing the second cell from a third base station that provides a third cell that periodically transmits system information.

[0139] (Appendix 4) The first base station as described in Appendix 1, wherein the CU (Central Unit) of the first base station receives the configuration information and system information of the second cell for accessing the second cell from the CU of the second base station, and the CU of the first base station transmits the configuration information and system information of the second cell for accessing the second cell to the DU (Distributed Unit) of the first base station.

[0140] (Note 5) The first base station described in Note 1, wherein the DU of the first base station receives the configuration information for accessing the second cell from the DU of the second base station.

[0141] (Appendix 6) A terminal comprising: a transmitting unit that transmits a request to transmit system information to the first base station via a first cell provided by the first base station; and a receiving unit that receives from the first base station configuration information for accessing a second cell provided by a second base station that transmits system information in response to a request from the terminal.

[0142] In any of the above configurations, efficient communication is achieved in a system where the terminal acquires system information on demand, and power consumption in the terminal and network can be reduced.

[0143] (Supplement to Embodiments) Although these embodiments have been described above, the disclosed invention is not limited to these 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 this embodiment and the software operated by the processor of the terminal 20 according to this embodiment 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.

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

[0145] Each aspect / embodiment described in this disclosure may be applied to at least one of systems utilizing LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (new Radio), W-CDMA®, GSM®, CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, and other appropriate systems, as well as next-generation systems extended 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0174] Numerical logic may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerical logic 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.

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

[0176] A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. Minislots may also be called subslots. Minislots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called a PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called a PDSCH (or PUSCH) mapping type B.

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

[0178] 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 in existing LTE (1 ms), a period shorter than 1 ms (e.g., 1-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.

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

[0180] 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. 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 TTI.

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

[0182] A TTI with a time length of 1 ms may be called a normal TTI, a long TTI, a normal subframe, a long subframe, a slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini slot, a sub slot, a slot, etc.

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

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

[0185] Furthermore, the time domain of the 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.

[0186] One or more RBs may also be called a Physical RB (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

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

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

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

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

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

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

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

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

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

[0196] This patent application claims priority based on Japanese Patent Application No. 2024-194682, filed on November 6, 2024, and the entire contents of Japanese Patent Application No. 2024-194682 are incorporated herein by reference.

[0197] 10 Base station 110 Transmitting unit 120 Receiving unit 130 Setting unit 140 Control unit 20 Terminal 210 Transmitting unit 220 Receiving unit 230 Setting unit 240 Control unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheel 2008 Rear wheel 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 (I / O port)

Claims

1. A first base station comprising: a receiving unit that receives a request to transmit system information from a terminal via a first cell provided by the first base station, and receives setting information for the terminal to access the second cell from a second base station that provides a second cell that transmits system information in response to the request from the terminal; and a transmitting unit that transmits the setting information to the terminal.

2. The first base station according to claim 1, wherein the receiving unit receives system information of the second cell from the second base station, in addition to the setting information for accessing the second cell.

3. The first base station according to claim 1, wherein the receiving unit receives the configuration information for accessing the second cell from a third base station that provides a third cell that periodically transmits system information.

4. The first base station according to claim 1, wherein the CU (Central Unit) of the first base station receives the configuration information and system information of the second cell for accessing the second cell from the CU of the second base station, and the CU of the first base station transmits the configuration information and system information of the second cell for accessing the second cell to the DU (Distributed Unit) of the first base station.

5. The first base station according to claim 1, wherein the DU of the first base station receives the configuration information for accessing the second cell from the DU of the second base station.

6. A terminal comprising: a transmitting unit that transmits a request to transmit system information to the first base station via a first cell provided by the first base station; and a receiving unit that receives from the first base station configuration information for accessing a second cell provided by a second base station that transmits system information in response to a request from the terminal.

Images