阅读说明：本技术 网络节点 (Network node ) 是由 户枝辉朗 甲斐健次 于 2019-02-14 设计创作，主要内容包括：一种网络节点,具有：接收单元,从终止并分离高层的多个上位网络节点中的第一上位网络节点接收用于请求初始化的信号；以及控制单元,在接收了所述请求初始化的信号的情况下,决定用户装置专用的信息的初始化范围,并执行被决定的所述初始化范围的用户装置专用的信息的初始化。(A network node having: a reception unit that receives a signal for requesting initialization from a first upper network node among a plurality of upper network nodes that terminate and separate upper layers; and a control unit which determines an initialization range of the user device specific information and initializes the user device specific information of the determined initialization range, when receiving the signal requesting initialization.)

1. A network node having:

a reception unit that receives a signal for requesting initialization from a first upper network node among a plurality of upper network nodes that terminate and separate upper layers; and

and a control unit which determines an initialization range of the user device specific information and initializes the user device specific information of the determined initialization range, when receiving the signal requesting initialization.

2. The network node of claim 1,

the control unit determines information specific to the user equipment related to the first upper network node as an initialization range.

3. The network node of claim 1,

the control unit decides all user device-specific information as an initialization range,

the network node further has: a transmission unit that transmits a signal for requesting initialization to a second upper network node among the plurality of upper network nodes.

4. The network node of claim 1,

the control unit selects whether to determine information specific to the user device related to the first upper network node as an initialization range or to determine information specific to all the user devices as the initialization range, based on a signal requesting initialization from the first upper network node.

5. A network node having:

a transmitting unit that transmits a signal for requesting initialization for deciding an initialization range of the user device-specific information to the lower network node,

the signal requesting initialization includes information indicating whether the information specific to the user equipment to which the user equipment is related is an initialization range or all the information specific to the user equipment is an initialization range,

the network node is one of a plurality of upper network nodes that terminate and separate upper layers.

Technical Field

The present invention relates to a network node in a wireless communication system.

Background

Research is being conducted on a technology that satisfies a large-capacity system, a high-speed data transmission rate, low delay, simultaneous connection of a large number of terminals, low cost, power saving, and the like as a request condition in NR (New Radio) (also referred to as "5G") that is a follow-up system of LTE (Long Term Evolution) (for example, non-patent document 1).

In the NR wireless communication system, the following techniques are introduced, as in the case of the dual connection in the LTE wireless communication system: a so-called LTE-NR dual connection, NR-NR dual connection, or Multi-RAT (Multi Radio Access Technology) dual connection (hereinafter, also referred to as "MR-DC") in which data is divided between a base station (eNB) of an LTE wireless communication system and a base station (gNB) of an NR wireless communication system and data is transmitted and received simultaneously by these base stations (for example, non-patent document 2).

In addition, in the NR wireless communication system, HLS (high layer split) is introduced. A higher layer is configured in a gNB-CU (Central Unit) and a lower layer is configured in a gNB-DU (Distributed Unit) in a separate manner (for example, non-patent document 3). In addition, in the LTE wireless communication system, the same CU-DU structure (HLS introduced) can be adopted.

Documents of the prior art

Non-patent document

Non-patent document 1: 3GPP TS 38.300V15.4.0(2018-12)

Non-patent document 2: 3GPP TS 37.340V15.4.0(2018-12)

Non-patent document 3: 3GPP TS 38.401V15.4.0(2018-12)

Disclosure of Invention

Problems to be solved by the invention

Research is being conducted on connecting a plurality of HLS interfaces for a single DU in the wireless communication system of NR and LTE. In the case where a single DU has multiple HLS interfaces, there is a case where UE-specific information that the CU and the DU each have does not match due to the initialization operation.

The present invention has been made in view of the above problems, and an object of the present invention is to perform initialization of matching between network nodes in a wireless communication system.

Means for solving the problems

According to the technique of the present disclosure, there is provided a network node having: a reception unit that receives a signal for requesting initialization from a first upper network node among a plurality of upper network nodes that terminate and separate upper layers; and a control unit which determines an initialization range of the user device specific information and initializes the user device specific information of the determined initialization range, when receiving the signal requesting initialization.

Effects of the invention

According to the technology of the present disclosure, matched initialization can be performed between network nodes in a wireless communication system.

Drawings

Fig. 1 is a diagram showing a configuration example of a network architecture in the embodiment of the present invention.

Fig. 2 is a diagram showing a configuration example (1) of a wireless communication system according to an embodiment of the present invention.

Fig. 3 is a diagram showing a configuration example (2) of a wireless communication system according to an embodiment of the present invention.

Fig. 4 is a diagram for explaining an example (1) of signal transmission in the embodiment of the present invention.

Fig. 5 is a diagram for explaining an example (2) of signal transmission in the embodiment of the present invention.

Fig. 6 is a flowchart for explaining operation example (1) in the embodiment of the present invention.

Fig. 7 is a flowchart for explaining operation example (2) in the embodiment of the present invention.

Fig. 8 is a flowchart for explaining operation example (3) in the embodiment of the present invention.

Fig. 9 is a flowchart for explaining operation example (4) in the embodiment of the present invention.

Fig. 10 is a flowchart for explaining operation example (5) in the embodiment of the present invention.

Fig. 11 is a diagram for explaining example (1) of initialization in the embodiment of the present invention.

Fig. 12 is a diagram for explaining an example (2) of initialization in the embodiment of the present invention.

Fig. 13A is a diagram for explaining an example (1) of the version notification operation.

Fig. 13B is a diagram for explaining an example (2) of the version notification operation.

Fig. 13C is a diagram for explaining an example (3) of the version notification operation.

Fig. 14 is a diagram for explaining an example (1) of the version notification operation in the embodiment of the present invention.

Fig. 15 is a diagram for explaining an example (2) of the version notification operation in the embodiment of the present invention.

Fig. 16 is a diagram for explaining an example (3) of the version notification operation in the embodiment of the present invention.

Fig. 17 is a diagram for explaining an example (4) of the version notification operation in the embodiment of the present invention.

Fig. 18 is a diagram showing an example of a functional configuration of the base station apparatus 10 according to the embodiment of the present invention.

Fig. 19 is a diagram showing an example of a functional configuration of the user apparatus 20 according to the embodiment of the present invention.

Fig. 20 is a diagram showing an example of a hardware configuration of the base station apparatus 10 or the user apparatus 20 according to the embodiment of the present invention.

Detailed Description

Hereinafter, embodiments of the present invention will be described with reference to the drawings. The embodiments described below are examples, and the embodiments to which the present invention is applied are not limited to the following embodiments.

In the operation of the wireless communication system of the embodiment of the present invention, the related art is suitably used. The prior art is, for example, but not limited to, existing LTE. The term "LTE" used in the present specification broadly includes LTE-Advanced and LTE-Advanced modes (e.g., NR) unless otherwise specified.

In the embodiments of the present invention described below, terms such as SS (Synchronization signal), PSS (primary SS), SSs (secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), and the like, which are used in conventional LTE, are used. This is merely for convenience of explanation, and the same signals, functions, and the like as those described above may be referred to by other names. Further, the above terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even a signal used for NR is not necessarily referred to as "NR-".

In the embodiment of the present invention, the Duplex (Duplex) system may be a TDD (Time Division Duplex) system, an FDD (Frequency Division Duplex) system, or another (e.g., a Flexible Duplex (flexile Duplex) system).

In the embodiment of the present invention, the "configured (configuration)" of the radio parameters or the like may be a specific value set in advance (Pre-configuration), or may be a radio parameter set notified from the base station apparatus 10 or the user apparatus 20.

Fig. 1 is a diagram showing a configuration example of a network architecture in the embodiment of the present invention. As shown in fig. 1, the wireless network architecture in the embodiment of the present invention includes, on the LTE-Advanced side, 4G-CU (Central Unit), 4G-DU (Distributed Unit), EPC (Evolved Packet Core), and the like. The wireless network architecture in the embodiment of the invention comprises 5G-CU, 5G-DU, 5GC (5G Core network) and the like at the 5G side.

As shown in fig. 1, on the 4G side, the 4G-CU includes an RRC (Radio Resource Control) layer and a PDCP (Packet Data Convergence Protocol) layer. The 4G-DU includes an RLC (Radio Link Control) layer, a MAC (Medium Access Control) layer, and L1 (layer 1, PHY layer, or physical layer), and is connected to the UE via RF. The network node containing the 4G-CU and the 4G-DU is called eNB. The 4G-CU connects to the 4G-DU via a FH (Fronthaul) interface. Furthermore, the 4G-CU is connected to the EPC via an IP border gateway.

On the other hand, on the 5G side, as shown in fig. 1, the 5G-CU includes an RRC layer and a PDCP layer. The 4G-DU includes an RLC layer, a MAC layer, and L1, and is connected with the UE via RF. The 5G-CU contains the RRC layer and is connected to the 5G-DU via the FH interface and to the 5GC via the NG interface. Furthermore, the 5G-CU is connected to the 4G-CU via an X2 interface. The PDCP layer in the 4G-CU is a junction or a separation point when performing 4G-5G DC (Dual Connectivity), that is, EN-DC (E-UTRA-NR Dual Connectivity). The network node containing the 5G-CU and the 5G-DU is referred to as the gNB. Furthermore, the 5G-CU may also be referred to as gNB-CU, and the 5G-DU may also be referred to as gNB-DU. In the following description, the base station apparatus 10 may be a gNB-CU as a network node or a gNB-DU as a network node. In the LTE wireless communication system, the above-described gbb-CU and gbb-DU on the premise of 5G may also be referred to as eNB-CU and eNB-DU.

Further, as shown in FIG. 1, DC is performed between 4G-DU and 5G-DU. Further, although not shown, a UE (User Equipment) is connected wirelessly via RF of a 4G-DU or a 5G-DU, and transmits and receives packets.

In addition, fig. 1 shows a wireless network architecture at DC of LTE-NR, i.e., EN-DC (E-UTRA-NR Dual Connectivity). However, the same wireless network architecture can also be used in case the NR is operated independently.

Furthermore, a plurality of 5G-DUs may be connected to the 5G-CU. Further, NR-DC (NR-NR Dual Connectivity) may be performed by connecting UEs to a plurality of 5G-CUs, or NR-DC may be performed by connecting UEs to a plurality of 5G-DUs and a single 5G-CU.

Furthermore, a plurality of 5G-CUs may be connected to the 5G-DU. In the following description, a configuration is assumed in which a plurality of 5G-CUs are connected to a 5G-DU. The following description may also be applied to a CU-DU structure in an LTE wireless communication system.

Fig. 2 is a diagram showing a configuration example (1) of a wireless communication system according to an embodiment of the present invention. As shown in fig. 2, CU10B, CU10C, and CU10D are arranged in each PLMN (Public Land Mobile Network) as RAN (Radio Access Network) sharing, and are connected to a single DU 10A. That is, DU10A has multiple HLS interfaces. The HLS interface is, for example, an interface in which the PDCP layer or the RRC layer is separated.

Fig. 3 is a diagram showing a configuration example (2) of a wireless communication system according to an embodiment of the present invention. As shown in fig. 3, the HLS interface is split over E-UTRAN and NG-RAN and CU10B connected to EPC and CU10C connected to 5GC are connected to DU 10A. That is, DU10A has multiple HLS interfaces. In addition, in the example of fig. 3, the CU is split on each HLS interface, but a case is also envisaged where the CU is single and split only on the HLS interface.

Here, signals in a radio communication system are roughly classified into signals specific to a UE (User Equipment) and signals common to cells. UE-specific signals are terminated on either CU. Thus, for example, in the visited network per PLMN ID, per E-UTRAN or NG-RAN, a mechanism for allocating UE-specific signals to CUs is needed. In the absence of this mechanism, an appropriate CU cannot be selected for transmission and reception of a UE-specific signal. On the other hand, a mechanism is needed for making the cell-common signals not contradictory between HLS interfaces in notifications from multiple CUs. In the absence of this mechanism, the DU cannot determine which CU's indication should be followed.

Fig. 4 is a diagram for explaining an example (1) of signal transmission in the embodiment of the present invention. Using fig. 4, an example of a signal transmitted when DU10A is connected to CU10B and CU10C is shown. As shown in fig. 4, for the UE-specific signals, UE-specific 1 signals are transmitted from CU10B to DU10A, and UE-specific 2 signals are transmitted from CU10C to DU 10A. That is, UE-specific signals are transmitted from CU10, respectively.

On the other hand, as shown in fig. 4, a cell-common signal is transmitted only from CU10B to DU 10A. With the structure in which a signal set to be cell-common is transmitted from the predetermined CU10, DU10A can correctly transmit a cell-common signal to UE 20.

Fig. 5 is a diagram for explaining an example (2) of signal transmission in the embodiment of the present invention. Using fig. 5, an example of a signal transmitted when DU10A is connected to CU10B and CU10C is shown. As with fig. 4, for UE-specific signals, UE-specific 1 signals are transmitted from CU10B to DU10A, and UE-specific 2 signals are transmitted from CU10C to DU 10A. That is, UE-specific signals are transmitted from CU10, respectively.

On the other hand, as shown in fig. 5, the cell-common signal is coordinated between CU10B and CU10C, and then transmitted from CU10B or CU10C to DU 10A. With the configuration in which a cell-common signal is transmitted from any CU10 after being coordinated among CUs 10, DU10A can correctly transmit a cell-common signal to UE 20.

Fig. 6 is a flowchart for explaining operation example (1) in the embodiment of the present invention. An example of an operation in which DU10 that has received an RRC message from UE20 determines which CU10 to send the RRC message will be described with reference to fig. 6.

In step S11, DU10 receives an RRC message from UE 20. Since the RRC layer does not terminate on DU10, in general, DU10 does not decode RRC messages. Therefore, DU10 decodes only a portion of the RRC message that is necessary for determining CU10 as the destination, and determines CU10 as the destination (S12). Next, DU10 transmits an RRC message to CU10 of the decided destination (S13). As described above, DU10, which received the RRC message from UE20, can decide which CU10 to send to.

Fig. 7 is a flowchart for explaining operation example (2) in the embodiment of the present invention. An example of an operation in which DU10 that has received an RRC message from UE20 determines which CU10 to transmit to will be described with reference to fig. 7.

In step S21, DU10 attempts to connect to the connected CUs 10. DU10 may receive a response indicating whether or not connection is possible from CU10 (S22), or may receive a response only from CU10 that is capable of connection. In step S23, DU10 is connected only to connectable CU 10. As described above, DU10, which received the RRC message from UE20, can decide which CU10 to send to.

Fig. 8 is a flowchart for explaining operation example (3) in the embodiment of the present invention. An example of an operation in which DU10 that has received an RRC message from UE20 determines which CU10 to transmit to will be described with reference to fig. 8.

In step S31, a priority interface between CU-DUs is set. Next, the DU10 decides CU10 to be connected based on the instruction from the CU10 to which the priority interface is set (S32). Subsequently, DU10 is connected to the determined CU10 (S33). Here, DU10 may be newly connected to CU10 as a connection target, or may transmit a UE context (UE context) to CU10 as a connection target to CU10 to which a priority interface is set. As described above, DU10, which received the RRC message from UE20, can decide which CU10 to send to.

Fig. 9 is a flowchart for explaining operation example (4) in the embodiment of the present invention. An example of an operation in which information is notified from CU10 to DU10 will be described with reference to fig. 9.

In step S41, an interface defining CU-DU exchange of specific information is specified. CU10 notifies DU10 only through the determined interface (S42). CU10 may also notify other CUs 10 of the determined interface (S43). The notification in step S43 may be sent directly from CU10 to other CU10, or may be sent from CU10 to other CU10 via DU 10. In the case where the notification is sent from CU10 to other CUs 10 via DU10, the notification may not be sent on an interface that does not exchange the specific information. Note that CU10 may be different depending on the specific information. When specific information is received from a plurality of CUs 10, DU10 combines the plurality of specific information.

The specific information is, for example, the gNB-DU system information. The gNB-DU System Information refers to an SIB (System Information Block) encoded in DU10, and corresponds to an MIB (Master Information Block) and an SIB 1. CU10 needs to coordinate among CUs 10 at notification time in order to notify a part of the gNB-DU system information, e.g. parameters related to forbidden cells, UAC (Unified access control).

The specific information is, for example, the gNB-CU system information. The gNB-CU System Information refers to an SIB (System Information Block) encoded by CU10, and corresponds to an SIB other than MIB and SIB 1. CU10 needs to coordinate CU10 in notification of the gNB-CU system information.

The specific information is, for example, a message related to RESOURCE setting of the DU (e.g., gNB-DU RESOURCE COORDINATION), that is, information related to cell management. The information related to cell management is, for example, information indicating activation, deactivation, addition, deletion, or cell state of a cell. CU10 decides on activation or deactivation of a cell and therefore coordination needs to be done between CUs 10 when notified. Furthermore, CU10 needs to know the state of the cell. When information related to cell management is notified from DU10 to CU10, cell addition, deletion, or Status (Status) may be notified on an interface that does not exchange the specific information.

The specific information is, for example, information related to distribution of emergency information (e.g., WRITE-REPLACE WARNING). Since the information related to the distribution of the emergency information is a parameter that the CU10 can update, coordination among the CUs 10 is required. For example, the following coordination needs to be performed: information related to distribution of emergency information is managed by which CU10, or which CU10 is responsible for which cell in the case where distribution of emergency information is shared by each cell.

Fig. 10 is a flowchart for explaining operation example (5) in the embodiment of the present invention. An example of an operation in which information is notified from CU10 to DU10 will be described with reference to fig. 10.

In step S51, which signal containing specific information is notified to DU10 is coordinated in advance among all CUs 10. That is, information indicating which signal is notified from which CU10 to DU10 is shared by communication between CUs 10. Subsequently, each CU10 signals DU10 according to the coordination result (S52). The specific information is the same as the specific information described in fig. 9. Since specific information coordinated in advance between CUs 10 is notified, no contradiction occurs between the notifications. Therefore, a single CU10 may notify DU10 of specific information, or a plurality of CUs 10 may notify DU10 of specific information.

Fig. 11 is a diagram for explaining example (1) of initialization in the embodiment of the present invention. In the related art, since a plurality of HLS interfaces are not assumed, only initialization for a specific UE (for example, Part of F1 Interface) or initialization for All UEs (for example, Reset All) is specified for initialization of UE-specific information (UE context). However, when setting a plurality of HLS interfaces, it is necessary to match the ranges initialized on the CU10 side and the DU10 side. In the case where the DU10 instructs the CU10 to initialize the UE context of the CU10, there is no problem, but in the case where the CU10 instructs the DU10 to initialize, it is necessary to recognize whether or not the UE context associated with the other CU10 in the DU10 is initialized.

Therefore, initialization may be performed only for a portion associated with the corresponding HLS interface. As shown in fig. 11, if CU10B sends a Reset signal to DU10A, DU10A initializes the UE context associated with the interface between CU10B and DU10A as an initialization range. That is, the UE context associated with the interface between CU10C-DU10A is not included in the initialization scope and will not be initialized.

Fig. 12 is a diagram for explaining an example (2) of initialization in the embodiment of the present invention. The initialized ranges on the CU10 side and the DU10 side may be matched by setting the initialized ranges to all UE contexts, notifying the CU10 other than the CU10 that transmitted the initialization instruction that initialization has been performed, and notifying the CU10 that initialization is requested in the same manner as initialization in the DU 10A.

As shown in fig. 12, when CU10B transmits a Reset signal to DU10A, DU10A initializes all UE contexts as an initialization range. Subsequently, if DU10A sends a Reset signal to CU10C, DU10C initializes the UE context.

Note that the use of either the initialization method shown in fig. 11 or the initialization method shown in fig. 12 may be explicitly indicated by a Reset signal transmitted from CU10B shown in fig. 11 to DU 10A.

Fig. 13A is a diagram for explaining an example (1) of the version notification operation. In the prior art, there are parameters (e.g., measgapcfonfig) that are encoded as follows: the DU encodes a part of the RRC container (RRC container), and the CU decodes the RRC container and puts it into a higher (upper) RRC container again. Therefore, the CU needs to be able to decode the RRC container of the DU, and thus the highest RRC version used between CU and DU needs to be consistent. Thus, the DU informs the CUs of the latest RRC versions supported, and likewise, the CUs informs the DU of the latest RRC versions supported and uses the CU and the highest RRC version supported in the DU on the CU-DU interface.

As shown in FIG. 13A, in the case where the RRC version of the CU is Rel-16 and the RRC version of the DU is Rel-15, the DU transmits "F1 setup Req. (Rel-15)" (F1 setup (setup) request) to the CU. Subsequently, the CU sends "F1 setup Resp. (Rel-16)" (F1 set (setup) response) to the DU. Rel-15 is used in the CU-DU interface, since the highest RRC version supported by both parties is Rel-15.

Fig. 13B is a diagram for explaining an example (2) of the version notification operation. As shown in fig. 13B, if the RRC version of the CU is Rel-15 and the RRC version of the DU is Rel-16, the DU transmits "F1 setup Req" (Rel-16) "to the CU. Subsequently, the CU sends "F1 setup Resp. (Rel-15)" to the DU. Since the highest RRC version supported by both parties is Rel-15, Rel-15 is used in the CU-DU interface.

Fig. 13C is a diagram for explaining an example (3) of the version notification operation. As shown in fig. 13C, if the RRC version of the CU is Rel-15 and the RRC version of the DU is Rel-15, the DU transmits "F1 setup Req" (Rel-15) "to the CU. Subsequently, the CU sends "F1 setup Resp. (Rel-15)" to the DU. Rel-15 is used in the CU-DU interface, since the highest RRC version supported by both parties is Rel-15.

Fig. 14 is a diagram for explaining an example (1) of the version notification operation in the embodiment of the present invention. When a plurality of CUs are connected to a DU, the DU cannot determine which RRC version should be used when RRC versions supported by the CUs are different.

Therefore, in the case where multiple CUs 10 are connected with DU10, DU10 uses multiple RRC versions per CU 10. The RRC version may be switched for each CU for a cell-common signal such as system information, or may be determined by DU 10.

As shown in fig. 14, when the RRC version of CU10B is Rel-15, the RRC version of CU10C is Rel-16, and the RRC version of DU10A is Rel-16, Rel-15 may be used for the interface CU10B-DU10A, and Rel-16 may be used for the interface CU10C-DU 10A.

Fig. 15 is a diagram for explaining an example (2) of the version notification operation in the embodiment of the present invention. As shown in fig. 15, when the RRC version of CU10B is Rel-15, the RRC version of CU10C is Rel-16, and the RRC version of DU10A is Rel-16, CU10B and CU10C can determine that the highest version common among CUs, i.e., the lowest version among CUs, is Rel-15 in each CU10 by coordination, and therefore, when "F1 setup Req" (Rel-16) "is transmitted from DU10A to CU10C, CU10C may transmit" F1 setup Resp "(Rel-15)" to DU10A, and use the same RRC version, i.e., Rel-15, as the interface of CU10B-DU10A in the interface of CU10C-DU 10A.

Fig. 16 is a diagram for explaining an example (3) of the version notification operation in the embodiment of the present invention. The RRC version used in the CU-DU interface can also be coordinated between CUs via DU 10. For example, DU10 may also match RRC versions among CUs by re-notifying the RRC version of a CU10 to other CUs 10 that have established HLS interfaces.

As shown in FIG. 16, the RRC version was established for Rel-16 for the interface CU10C-DU 10A. In this state, DU10A sends "F1 setup Req. (Rel-16)" to CU 10B. Subsequently, CU10B sends "F1 setup Resp. (Rel-15)" to DU 10A. Then, since the RRC version of the interface of CU10B is lower than that of CU10C, DU10A sends "gNB-DU config update (gNB-DU configuration update) (Rel-15)" to CU10C, thereby changing the RRC version of the interface of CU10C-CU10A to Rel-15. The message name "gNB-DU config update" of F1 is an example, and may be other names.

Fig. 17 is a diagram for explaining an example (4) of the version notification operation in the embodiment of the present invention.

DU10 may also disconnect the established F1 interface and re-establish the F1 interface through the RRC version used in the other CUs 10.

As shown in FIG. 17, the interface CU10C-DU10A is established with RRC version Rel-16. In this state, DU10A sends "F1 setup Req. (Rel-16)" to CU 10B. Subsequently, CU10B sends "F1 setup Resp. (Rel-15)" to DU 10A. Then, since the RRC version of the interface of CU10B is lower than that of CU10C, DU10A sends "F1 setup Req. (Rel-15)" to CU 10C. Subsequently, CU10C sends "F1 setup Resp" (Rel-15) "to DU10A, changing the RRC version of the interface of CU10C-CU10A to Rel-15.

In the above-described embodiment, in a configuration in which a plurality of CUs and DUs are connected, the CUs and DUs as network nodes can appropriately initialize the user-specific information that each of the CUs and DUs has.

That is, matched initialization can be performed between network nodes in the wireless communication system.

(device construction)

Next, a functional configuration example of the base station apparatus 10 and the user apparatus 20 that execute the processing and operation described above will be described. The base station apparatus 10 and the user apparatus 20 include functions to implement the above-described embodiments. However, the base station apparatus 10 and the user apparatus 20 may have only some of the functions in the embodiments.

< base station apparatus 10 >

Fig. 18 is a diagram showing an example of a functional configuration of the base station apparatus 10 according to the embodiment of the present invention. As shown in fig. 18, base station apparatus 10 includes transmission section 110, reception section 120, setting section 130, and control section 140. The functional configuration shown in fig. 18 is merely an example. The functional distinction and the name of the functional unit may be arbitrary as long as the operation according to the embodiment of the present invention can be performed. Further, the base station apparatus 10 may be a separate CU10 or DU 10.

The transmission unit 110 includes a function of generating a signal to be transmitted to the user apparatus 20 side and transmitting the signal wirelessly. Further, the transmitting unit 110 transmits the inter-network node message to other network nodes. The reception unit 120 includes a function of receiving various signals transmitted from the user apparatus 20 and acquiring, for example, higher layer information from the received signals. Further, the transmission unit 110 has a function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL/UL control signals, and the like to the user equipment 20. Further, the receiving unit 120 receives inter-network node messages from other network nodes.

The setting unit 130 stores preset setting information and various kinds of setting information transmitted to the user device 20 in a storage device, and reads the setting information from the storage device as necessary. The content of the setting information is, for example, setting information related to an RRC message, setting information related to communication of the user equipment 20, and the like.

As explained in the embodiment, the control unit 140 controls wireless communication for transmitting and receiving an RRC message. Further, control section 140 controls initialization for setting related to communication of user apparatus 20. Transmission section 110 may include a function section relating to signal transmission in control section 140, and reception section 120 may include a function section relating to signal reception in control section 140.

< user device 20 >

Fig. 19 is a diagram showing an example of a functional configuration of the user apparatus 20 according to the embodiment of the present invention. As shown in fig. 19, the user apparatus 20 includes a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in fig. 19 is merely an example. The functional distinction and the name of the functional unit may be arbitrary as long as the operation according to the embodiment of the present invention can be performed.

Transmission section 210 generates a transmission signal based on the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 wirelessly receives various signals and acquires a signal of a higher layer from the received signal of the physical layer. Furthermore, the reception unit 220 has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL/UL/SL control signals, and the like transmitted from the base station apparatus 10. For example, as D2D communication, the transmitting unit 210 transmits PSCCH (Physical Sidelink Control Channel), PSCCH (Physical Sidelink Shared Channel), PSDCH (Physical Sidelink Discovery Channel), PSBCH (Physical Sidelink Broadcast Channel), and the like to the other user equipment 20, and the receiving unit 120 receives PSCCH, PSDCH, PSBCH, and the like from the other user equipment 20.

Setting section 230 stores various kinds of setting information received from base station apparatus 10 or user apparatus 20 by receiving section 220 in a storage device, and reads the information from the storage device as necessary. The setting unit 230 also stores preset setting information. The content of the setting information is, for example, setting information related to an RRC message.

As explained in the embodiment, the control unit 240 controls wireless communication for transmitting and receiving an RRC message. Further, control section 240 receives information related to radio communication from base station apparatus 10, controls radio communication of user apparatus 20 based on the information, and reports necessary information to base station apparatus 10. It is also possible to make transmitting section 210 include a functional section relating to signal transmission in control section 240 and make receiving section 220 include a functional section relating to signal reception in control section 240.

(hardware construction)

The block diagrams (fig. 18 and 19) used for the description of the above embodiment show blocks of functional units. These functional blocks (constituent units) are realized by an arbitrary combination of at least one of hardware and software. The method of implementing each functional block is not particularly limited. That is, each functional block may be implemented by one apparatus that is physically or logically combined, or may be implemented by a plurality of apparatuses that are directly or indirectly (for example, by using wire or wireless) connected to two or more apparatuses that are physically or logically separated. The functional blocks may also be implemented by combining software in one or more of the above-described apparatuses.

The functions include, but are not limited to, judgment, decision, determination, calculation, processing, derivation, investigation, retrieval, confirmation, reception, transmission, output, access, resolution, selection, establishment, comparison, assumption, expectation, view, broadcast (broadcasting), notification (notification), communication (communicating), forwarding (forwarding), composition (configuration), reconfiguration (reconfiguration), allocation (allocation, mapping), assignment (assigning), and the like. For example, a functional block (a structural unit) that functions transmission is called a transmitting unit (transmitting unit), a transmitter (transmitter), or the like. As described above, any one of the implementation methods is not particularly limited.

For example, the base station apparatus 10, the user apparatus 20, and the like according to one embodiment of the present disclosure may function as a computer that performs processing of the radio communication method of the present disclosure. Fig. 20 is a diagram illustrating an example of the hardware configuration of the base station apparatus 10 and the user apparatus 20 according to the embodiment of the present disclosure. The base station apparatus 10 and the user apparatus 20 may be physically configured as a computer apparatus 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, and the like.

In the following description, the term "device" may be replaced with a circuit, a device, a unit, or the like. The hardware configuration of the base station apparatus 10 and the user apparatus 20 may be configured to include one or more of the illustrated apparatuses, or may be configured not to include some of the apparatuses.

Each function of the base station apparatus 10 and the user apparatus 20 is realized by, for example, reading specific software (program) into hardware such as the processor 1001 and the storage device 1002, performing an operation by the processor 1001, and controlling communication via the communication device 1004 or at least one of reading and writing of data in the storage device 1002 and the auxiliary storage device 1003.

The processor 1001 controls the entire computer by operating an operating system, for example. The processor 1001 may be configured by a Central Processing Unit (CPU) including an interface with a peripheral device, a control device, an arithmetic device, a register, and the like. For example, the control unit 140, the control unit 240, and the like described above may be implemented by the processor 1001.

Further, the processor 1001 reads out a program (program code), a software module, data, or the like from at least one of the auxiliary storage device 1003 and the communication device 1004 to the storage device 1002, and executes various processes in accordance with them. As the program, a program that causes a computer to execute at least a part of the operations described in the above-described embodiments is used. For example, the control unit 140 of the base station apparatus 10 shown in fig. 18 may also be realized by a control program stored in the storage device 1002 and operated in the processor 1001. Further, for example, the control unit 240 of the user device 20 shown in fig. 19 may also be realized by a control program stored in the storage device 1002 and operated in the processor 1001. The above various processes have been described as being executed by one processor 1001, but may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may also be mounted by more than one chip. In addition, the program may also be transmitted from a network via an electric communication line.

The storage device 1002 is a computer-readable recording medium, and may be configured with at least one of a ROM (Read Only Memory), an EPROM (Erasable Programmable ROM), an EEPROM (electrically Erasable Programmable ROM), a RAM (Random Access Memory), and the like, for example. The storage 1002 may also be referred to as a register, cache, main memory (primary storage), or the like. The storage device 1002 can store a program (program code), a software module, and the like that are executable to implement the communication method according to the embodiment of the present disclosure.

The auxiliary storage device 1003 is a computer-readable recording medium, and may be configured with at least one of an optical disk such as a CD-ROM (compact Disc ROM), a hard disk drive, a flexible disk, an optical disk (for example, a compact Disc, a digital versatile Disc, a Blu-ray (registered trademark) disk), a smart card, a flash memory (for example, a card, a stick, or a key drive), a Floppy (registered trademark) disk, and a magnetic stripe. The storage medium may be, for example, another suitable medium such as a database or a server including at least one of the storage device 1002 and the auxiliary storage device 1003.

The communication device 1004 is hardware (transmission/reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, a network controller, a network card, a communication module, or the like, for example. The communication device 1004 may include a high-Frequency switch, a duplexer, a filter, a Frequency synthesizer, and the like, for example, in order to realize at least one of Frequency Division Duplexing (FDD) and Time Division Duplexing (TDD). For example, a transmission/reception antenna, an amplifier unit, a transmission/reception unit, a transmission line interface, and the like can be realized by the communication device 1004. The transmitting and receiving unit may be physically or logically separated from the transmitting unit and the receiving unit.

The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, and the like) that receives an input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, or the like) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated (for example, a touch panel).

Further, the processor 1001 and the storage device 1002 are connected to each other via a bus 1007 for communicating information. The bus 1007 may be formed using a single bus, or may be formed using different buses for each device.

The base station apparatus 10 and the user apparatus 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), an FPGA (Field Programmable Gate Array), or the like, and a part or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may also be installed using at least one of these hardware.

(summary of the embodiment)

As described above, according to an embodiment of the present invention, there is provided a network node including: a reception unit that receives a signal for requesting initialization from a first upper network node among a plurality of upper network nodes that terminate and separate upper layers; and a control unit which determines an initialization range of the user device specific information and initializes the user device specific information of the determined initialization range, when receiving the signal requesting initialization.

With the above configuration, in a configuration in which a plurality of CUs and DUs are connected, the CUs and DUs as network nodes can appropriately initialize the user-specific information that each of the CUs and DUs has. That is, the initialization to be matched can be performed between network nodes in the wireless communication system.

The control unit may determine information specific to the user equipment related to the first higher-level network node as an initialization range. With this configuration, the DU can initialize the user device-specific information on the CU that transmits the signal for requesting initialization.

The control unit further has: and a transmitting unit configured to determine information specific to all user devices as an initialization range, and to transmit a signal for requesting initialization to a second upper network node among the plurality of upper network nodes. With this configuration, the DU can match the initialization range between CUs-DU by requesting initialization to CUs other than the CU that transmits the signal for requesting initialization.

The control unit may select whether to determine information specific to the user device related to the first upper network node as the initialization range or to determine all information specific to the user device as the initialization range, based on a signal requesting initialization from the first upper network node. With this configuration, the DU can control the initialization range based on the signal requesting initialization.

Further, according to an embodiment of the present invention, there is provided a network node having: and a transmitting unit configured to transmit, to a lower network node which is one of a plurality of upper network nodes terminating and separating higher layers, a signal requesting initialization for determining an initialization range of information specific to a user device, the signal requesting initialization including information indicating whether information specific to the user device to which the device is related is the initialization range or information indicating whether all information specific to the user device is the initialization range.

With the above configuration, in a configuration in which a plurality of CUs and DUs are connected, the CUs and DUs as network nodes can appropriately initialize the user-specific information that each of the CUs and DUs has. That is, the initialization to be matched can be performed between network nodes in the wireless communication system.

(supplement to embodiment)

While the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and various modifications, alternatives, and substitutions will be apparent to those skilled in the art. Although specific numerical examples are used to facilitate understanding of the present invention, these numerical values are merely examples and any appropriate values may be used unless otherwise specified. The distinction of items in the above description is not essential to the present invention, and items described in two or more items may be used in combination as necessary, or items described in one item may be applied to items described in other items (as long as there is no contradiction). Boundaries of functional units or processing units in the functional block diagrams do not necessarily correspond to boundaries of physical components. Operations of a plurality of functional units may be physically performed by one component, or operations of one functional unit may be physically performed by a plurality of components. As for the processing procedure described in the embodiment, the order of processing may be changed without contradiction. For convenience of explanation of the processing, the base station apparatus 10 and the user apparatus 20 have been explained using functional block diagrams, but such apparatuses may also be realized by hardware, software, or a combination thereof. Software that is operated by a processor provided in the base station apparatus 10 according to the embodiment of the present invention and software that is operated by a processor provided in the user apparatus 20 according to the embodiment of the present invention may be stored in a Random Access Memory (RAM), a flash memory, a Read Only Memory (ROM), an EPROM, an EEPROM, a register, a hard disk (HDD), a removable disk, a CD-ROM, a database, a server, and any other suitable storage medium, respectively.

Further, the notification of information is not limited to the form/embodiment described in the present disclosure, and may be performed using other methods. For example, the notification of the Information may be implemented by physical layer signaling (e.g., DCI (Downlink Control Information)), UCI (Uplink Control Information)), higher 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 a combination thereof).

The aspects/embodiments described in the present disclosure may be applied to LTE (Long Term Evolution), LTE-a (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (fourth generation mobile communication system (4th generation mobile communication system)), 5G (fifth generation mobile communication system (5th generation mobile communication system)), FRA (Future Radio Access), NR (new Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA 2000, UMB (Ultra mobile Broadband), IEEE 802.11(Wi-Fi (registered trademark)), IEEE 802.16(WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-wide band)), Bluetooth (registered trademark), systems using other appropriate systems, and next generation systems extended accordingly. In addition, a plurality of systems may be applied in combination (for example, a combination of 5G and at least one of LTE and LTE-a). .

The processing procedures, sequences, flowcharts, and the like of the respective modes/embodiments described in the present specification may be changed in order as long as they are not contradictory. For example, elements of the various steps are presented in the order shown in the method described in the present disclosure, and are not limited to the specific order presented.

In the present specification, it is assumed that the specific operation performed by the base station apparatus 10 is sometimes performed by an upper node (upper node) thereof, depending on the case. It is apparent that, in a network including one or more network nodes (network nodes) having the base station apparatus 10, various operations performed for communication with the user apparatus 20 can be performed by at least one of the base station apparatus 10 and a network node other than the base station apparatus 10 (for example, MME, S-GW, or the like is considered, but not limited thereto). In the above description, the case where there is one network node other than the base station apparatus 10 is exemplified, but the other network node may be a combination of a plurality of other network nodes (e.g., MME and S-GW).

Information, signals, and the like described in the present disclosure can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). Or may be input or output via a plurality of network nodes.

The information to be input and output may be stored in a specific location (for example, a memory) or may be managed using a management table. It can also be managed using a management table. Information and the like to be input and output can be overwritten, updated, or written. The output information and the like may be deleted. The inputted information and the like may be transmitted to other devices.

The determination in the present disclosure may be made by a value (0 or 1) represented by 1 bit, may be made by a Boolean value (Boolean: true or false), and may be made by comparison of numerical values (for example, comparison with a specific value).

Software shall be construed broadly to mean instructions, instruction sets, code segments, program code, programs, subroutines, software modules, applications, software packages, routines, subroutines, objects (objects), executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or by other names.

In addition, software, instructions, information, and the like may also be transmitted or received via a transmission medium. For example, where the software is transmitted from a website, server, or other remote source using at least one of wired technology (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.) and wireless technology (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of transmission medium.

Information, signals, and the like described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, and the like that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or photons, or any combination thereof.

In addition, terms described in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and the symbol may be a signal (signaling). Further, the signal may also be a message. Further, a Component Carrier (CC) may also be referred to as a Carrier frequency, a cell, a frequency Carrier, and the like.

The terms "system" and "network" as used in this disclosure are used interchangeably.

The information, parameters, and the like described in the present disclosure may be expressed in absolute values, relative values to specific values, or other corresponding information. For example, the radio resource may also be indicated by an index.

The names used for the above parameters are not limiting names in all aspects. Further, the mathematical expressions and the like using these parameters are sometimes different from those explicitly disclosed in the present disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable names, and thus the various names assigned to these various channels and information elements are not limiting names in all respects.

In the present disclosure, terms such as "Base Station (BS)", "radio Base Station", "Base Station apparatus", "fixed Station (fixed Station)", "NodeB", "enodeb (enb)", "gbnodeb (gnb)", "access point (access point)", "transmission point)", "reception point (reception point)", "transmission/reception point", "cell", "sector", "cell group", "carrier", "component carrier" may be used interchangeably. A base station is sometimes also referred to by terms such as macrocell, smallcell, femtocell, picocell, and the like.

A base station can accommodate one or more (e.g., 3) cells. In the case where a base station accommodates a plurality of cells, the entire coverage area of the base station can be divided into a plurality of smaller areas, and each of the smaller areas can also provide communication services through a base station subsystem (e.g., a Remote Radio Head (RRH)). The term "cell" or "sector" refers to a portion or the entirety of the coverage area of a base station and base station subsystem that is in communication service within the coverage area.

In the present disclosure, terms such as "Mobile Station (MS)", "User terminal (User terminal)", "User Equipment (UE)", "terminal" and the like may be used interchangeably.

A mobile station is also sometimes referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset (hand set), user agent, mobile client, or several other suitable terms.

At least one of the base station and the mobile station may also be referred to as a transmitting apparatus, a receiving apparatus, a communication apparatus, or the like. At least one of the base station and the mobile station may be a device mounted on the mobile body, the mobile body itself, or the like. The moving body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving body (e.g., an unmanned aerial vehicle, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station further includes a device that does not necessarily move during a communication operation. 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.

Further, the base station in the present disclosure may be replaced by a user terminal. For example, the embodiments and implementation modes of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between a plurality of user terminals 20 (e.g., may also be referred to as D2D (Device-to-Device), V2X (Vehicle-to-event), and the like). In this case, the user apparatus 20 may have the function of the base station apparatus 10 described above. Also, words such as "upstream", "downstream", etc. may be replaced with words corresponding to inter-terminal communication (e.g., "side"). For example, the uplink channel, the downlink channel, and the like may be replaced with the side channel.

Likewise, the user terminal in the present disclosure may also be replaced with a base station. In this case, the base station may have a configuration having the functions of the user terminal.

The terms "determining" and "deciding" used in the present disclosure sometimes include various operations. "determining" and "decision" may include, for example, determining "and" deciding "or the like, such as by determining", "calculating", "processing", "deriving", "investigating", "analyzing", "searching", and "inquiring" (e.g., searching in a table, database, or other data structure). The "determination" and "decision" may include a case where reception (e.g., reception information), transmission (e.g., transmission information), input (input), output (output), access (access) (e.g., access to data in a memory), and the like are regarded as "determination" and "decision". Further, "judgment" and "decision" may include cases in which solution (resolving), selection (selecting), selection (smoothening), establishment (evaluating), comparison (comparing), and the like are regarded as "judgment" and "decision". That is, the terms "determine" and "decide" may include a case where a certain operation is regarded as being "determined" and "decided". The "determination (decision)" may be replaced with "assumption", "expectation", "assumption".

The terms "connected", "coupled", or any variation thereof, mean all of the direct or indirect connections or couplings between two or more elements, and can include the presence of one or more intervening elements between two elements that are "connected" or "coupled" to each other. The combination or connection between the elements may be physical, logical, or a combination thereof. For example, "connected" may also be replaced with "access". As used in this disclosure, two elements can be considered to be "connected" or "coupled" to each other using at least one of one or more wires, cables, printed electrical connections, and the like, and using electromagnetic energy having wavelengths in the radio frequency domain, the microwave domain, and the optical (both visible and invisible) domain, as a few non-limiting and non-exhaustive examples.

The reference signal can also be referred to as rs (reference signal) for short, and also as Pilot (Pilot) depending on the applied standard.

As used in this disclosure, a recitation of "based on" does not mean "based only on" unless explicitly stated otherwise. In other words, the expression "based on" means both "based only on" and "based at least on".

Any reference to the use of "first," "second," etc. elements in this disclosure is not intended to limit the number or order of such elements in a comprehensive manner. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, reference to first and second elements does not mean that only two elements may be employed or that the first element must precede the second element in some fashion.

The "unit" in the configuration of each device described above may be replaced with a "section", "circuit", "device", or the like.

Where the terms "including", "comprising" and variations thereof are used in this disclosure, these terms are intended to be inclusive in the same way as the term "comprising". Further, the term "or" as used in this disclosure means not a logical exclusive or.

A radio frame may also be made up of one or more frames in the time domain. In the time domain, one or more individual frames may also be referred to as subframes. The subframe may be further configured by one or more slots in the time domain. The subframe may also be a fixed time length (e.g., 1ms) independent of a parameter set (numerology).

A parameter set (numerology) may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel. The parameter set (numerology) may also represent, for example, at least one of a SubCarrier Spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a Transmission Time Interval (TTI), the number of symbols per TTI, a radio frame structure, a specific filtering process performed by the transceiver in the frequency domain, a specific windowing process performed by the transceiver in the Time domain, and the like.

The slot may be formed of one or more symbols in the time domain (OFDM (Orthogonal Frequency Division Multiplexing) symbol, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbol, or the like). Further, the time slot may also be a time unit based on a parameter set.

A timeslot may also contain multiple mini-slots. Each mini-slot may also be made up of one or more symbols in the time domain. In addition, a mini-slot may also be referred to as a sub-slot. A mini-slot may also be made up of fewer symbols than a slot. PDSCH (or PUSCH) transmitted in a time unit larger than a mini slot is also referred to as PDSCH (PUSCH) mapping type a. PDSCH (or PUSCH) transmitted using mini-slots is also referred to as PDSCH (PUSCH) mapping type B.

The radio frame, subframe, slot, mini-slot, and symbol all represent a unit of time when a signal is transmitted. The radio frame, subframe, slot, mini-slot, and symbol may be referred to by their names.

For example, one subframe may also be referred to as a Transmission Time Interval (TTI), a plurality of consecutive subframes may also be referred to as TTIs, and one slot or one mini-slot may also be referred to as a TTI. That is, at least one of the subframe and TTI may be a subframe (1ms) in the conventional LTE, may be a period shorter than 1ms (for example, 1 to 13 symbols), or may be a period longer than 1 ms. The unit of displaying TTI may be referred to as a slot, a mini-slot, or the like, and is not referred to as a subframe.

Here, the TTI refers to, for example, the minimum time unit of scheduling in wireless communication. For example, in the LTE system, the base station performs scheduling for allocating radio resources (frequency bandwidth, transmission power, and the like that can be used by each user equipment 20) to each user equipment 20 in TTI units. In addition, the definition of TTI is not limited thereto.

The TTI may be a transmission time unit of a data packet (transport block), a code block, or a code word after channel coding, or may be a processing unit such as scheduling or link adaptation. In addition, when a TTI is provided, a time interval (e.g., the number of symbols) to which a transport block, a code block, and a codeword are actually mapped may also be shorter than the TTI.

In addition, when one slot or one mini-slot is referred to as a TTI, one or more TTIs (i.e., one or more slots or one or more mini-slots) may be the minimum time unit for scheduling. Further, the number of slots (the number of mini-slots) constituting the minimum time unit of the schedule may also be controlled.

A TTI having a time length of 1ms may be referred to as a normal TTI (TTI in LTE rel.8-12), a standard TTI, a long TTI, a normal subframe, a standard subframe, a long subframe, a slot, etc. A TTI shorter than a normal TTI may be referred to as a shortened TTI, a short TTI, a partial TTI, a shortened subframe, a short subframe, a mini-slot, a sub-slot, a slot, etc.

In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be replaced with a TTI having a time length exceeding 1ms, and a short TTI (e.g., a shortened TTI, etc.) may be replaced with a TTI having a TTI length that is less than the TTI length of the long TTI and is 1ms or more.

A Resource Block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more continuous subcarriers (subcarriers) in the frequency domain. The number of subcarriers included in an RB may be the same regardless of the parameter set, and may be 12, for example. The number of subcarriers included in the RB may also be decided based on the parameter set.

In addition, the time domain of the RB may include one or more symbols, and may also have a length of one slot, one mini-slot, one subframe, or one TTI. One TTI, one subframe, and the like may be respectively composed of one or more resource blocks.

In addition, one or more RBs may also be referred to as Physical Resource Blocks (PRBs), Sub-Carrier groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB peers, and so on.

In addition, a Resource block may also be composed of one or more Resource Elements (REs). For example, one RE may also be a radio resource region of one subcarrier and one symbol.

The Bandwidth Part (BWP: Bandwidth Part) (which may also be referred to as a partial Bandwidth) may also indicate a subset of consecutive common RBs (common resource blocks) for a certain parameter set in a certain carrier. Here, the common RB may be determined from an index of an RB with reference to a common reference point of the carrier. The PRB is defined by a certain BWP, and may be numbered additionally within the BWP.

The BWP may include UL BWP (UL BWP) and DL BWP (DL BWP). One or more BWPs may also be set for the UE within one carrier.

At least one of the provisioned BWPs may be active or the UE may not be supposed to transmit or receive a specific signal/channel outside the active BWP. In addition, "cell", "carrier", and the like in the present disclosure may also be replaced with "BWP".

The above structures of radio frame, subframe, slot, mini-slot, and symbol are only examples. The above structures of radio frame, subframe, slot, mini-slot, and symbol are only examples. For example, the structure of the number of subframes included in the radio frame, the number of slots per subframe or radio frame, the number of mini-slots included in a slot, the number of symbols and RBs included in a slot or mini-slot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the Cyclic Prefix (CP) length, and the like can be variously changed.

In the present disclosure, where articles such as a, an, and the in english are added by translation, the present disclosure includes cases where nouns after these articles are plural.

In the present disclosure, the term "a is different from B" may also mean "a is different from B". In addition, the term may also mean "A and B are each different from C". The terms "separate", "combine", and the like are also to be construed as similar to "different".

The aspects and embodiments described in the present disclosure may be used alone, or in combination, or may be switched with execution. Note that the notification of the specific information (for example, the notification of "X") is not limited to be explicitly performed, and may be performed implicitly (for example, the notification of the specific information is not performed).

In the present disclosure, CU10 is an example of a higher-level network node. DU10 is an example of a lower network node. The RRC message is an example of a higher layer message.

While the present disclosure has been described in detail, it will be apparent to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented as modifications and variations without departing from the spirit and scope of the present disclosure defined by the claims. Accordingly, the description of the disclosure is for the purpose of illustration and is not intended to be in any way limiting of the disclosure.

Description of the reference symbols

10 base station device

110 sending unit

120 receiving unit

130 setting unit

140 control unit

20 user device

210 sending 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