WO2024150287A1 - Wireless communication node and terminal - Google Patents

Abstract

This wireless communication node comprises a control unit that detects any fault occurring between the wireless communication node and a higher-order node, and a transmission unit that transmits fault information to the higher-order node, the fault information including information pertaining to movement of the wireless communication node.

Description

Wireless communication node, terminal

This disclosure relates to wireless communication nodes and terminals.

The 3rd Generation Partnership Project (3GPP) is developing specifications for the 5th generation mobile communication system (5G, also known as New Radio (NR) or Next Generation (NG)) and is also developing specifications for the next generation of mobile communication systems, known as Beyond 5G, 5G Evolution or 6G.

For example, 3GPP Release 17 specifies Integrated Access and Backhaul (IAB), which integrates wireless access to terminals (User Equipment, UE) and wireless backhaul between wireless communication nodes that make up base stations (next generation NodeB, gNB). Wireless communication nodes consist of an IAB-donor connected to the network and an IAB-node that is connected to the IAB-donor via wireless backhaul and performs wireless communication with the UE.

Furthermore, as part of an attempt to expand the IAB-node, 3GPP Release 18 is discussing mobile IAB-nodes, which are equipped with IAB-nodes on moving objects such as automobiles and drones (Non-Patent Document 1).

If a failure such as a radio link failure (RLF) or handover failure (HOF) occurs between an IAB-node and an upper node (IAB-donor or another IAB-node) connected to the IAB-node, the IAB-node or a UE under the IAB-node must report the failure information to the network via the upper node.

However, when the IAB-node is the mobile IAB-node described above, the parameters to be reported become more complex as the IAB-node moves, and there is a risk that recovery from a failure cannot be achieved by simply reporting the conventional failure information. In addition, when the IAB-node performs dual connectivity (DC) with multiple upper nodes, the selection of parameters to be reported and the report destination becomes more complex as the number of cells increases, and a similar problem may occur.

The present disclosure has been made in light of these circumstances, and aims to provide a wireless communication node and terminal that can report fault information to the network without impeding the scalability of the IAB-node, such as improving mobility and supporting DC.

One aspect of the disclosure is a wireless communication node (wireless communication node 150) that includes a control unit (control unit 180) that detects a fault that occurs between the wireless communication node and a higher-level node, and a transmission unit (fault reporting unit 170) that transmits fault information to the higher-level node, the fault information including information related to the movement of the wireless communication node.

One aspect of the disclosure is a wireless communication node (wireless communication node 150) that performs dual connections with multiple upper nodes, and includes a control unit (control unit 180) that detects a fault that occurs between the wireless communication node and the upper node, and a transmission unit (fault reporting unit 170) that transmits fault information to the upper node, and the fault information includes identification information of the cell in which the fault is detected.

One aspect of the disclosure is a terminal (UE200) connected to a wireless communication node, the terminal (UE200) comprising a control unit (control unit 230) that detects a fault occurring between the wireless communication node and a higher-level node, and a transmission unit (fault reporting unit 220) that transmits fault information to the higher-level node, the fault information including information related to the movement of the terminal.

FIG. 1 is a diagram showing the overall configuration of a wireless communication system. FIG. 2 is a functional block diagram of an IAB-donor constituting a base station. FIG. 3 is a functional block diagram of an IAB-node constituting a base station. FIG. 4 is a functional block diagram of the terminal. FIG. 5 is a diagram showing the occurrence of RLF. FIG. 6 is a diagram showing the occurrence of RLF/HOF during handover. FIG. 7 is a diagram showing the occurrence of RLF/HOF during handover. FIG. 8 is a diagram showing the occurrence of RLF/HOF during handover. FIG. 9 is a sequence diagram of reporting an RLF. FIG. 10 shows the occurrence of RLF in DC. FIG. 11 is a sequence diagram for reporting RLF in a secondary cell group (SCG). FIG. 12 is a sequence diagram of reporting RLF in a master cell group (MCG). FIG. 13 is a diagram illustrating an example of a hardware configuration of a wireless communication node and a terminal. FIG. 14 is a diagram illustrating an example of the configuration of a vehicle.

The following describes the embodiments with reference to the drawings. Note that identical or similar symbols are used for identical functions and configurations, and descriptions thereof will be omitted as appropriate.

(1) Overall Schematic Configuration of Wireless Communication System The wireless communication system 10 shown in Fig. 1 is a wireless communication system conforming to a method called 5G. On the other hand, the wireless communication system 10 may be a wireless communication system conforming to a method called Beyond 5G, 5G Evolution, or 6G.

As shown in FIG. 1, the wireless communication system 10 includes a Next Generation-Radio Access Network (NG-RAN) 20, a wireless communication node 100 connected to the NG-RAN 20 via a wired transmission path such as fiber transport, a wireless communication node 150 connected to the wireless communication node 100 via a wireless backhaul, and a terminal (User Equipment, UE) 200 connected to the wireless communication node 150. The NG-RAN 20 is connected to a core network (CN) (not shown). The NG-RAN 20 and the CN may be simply referred to as a "network."

The configuration of the wireless communication system 10 in which the wireless access to the UE 200 and the wireless backhaul between the wireless communication nodes 100 and 150 are integrated in this manner is called Integrated Access and Backhaul (IAB). Note that the specific configuration of the wireless communication system 10, for example the number of wireless communication nodes 100, 150 and UEs 200, is not limited to the example shown in FIG. 1 (see FIGS. 6 to 8 and 10).

In IAB, the direction from the wireless communication node 100 to the wireless communication node 150 and UE 200 is the downlink (DL) direction, and the direction from the wireless communication node 150 and UE 200 to the wireless communication node 100 and the network is the uplink (UL) direction.

The wireless communication node 100 may also be called an IAB-donor, and may be called an upper node or a Parent node based on the topology with the wireless communication node 150. The wireless communication node 150 may also be called an IAB-node, and may be called a lower node or a Child node based on the topology with the wireless communication node 100. Such names may also be applied between multiple wireless communication nodes 150. For example, the wireless communication nodes 150A and 150B in the configuration example shown in FIG. 10 may be called an upper node or a Parent node of the wireless communication node 150C. The UE 200 may also be called a lower node or a Child node based on the topology with the wireless communication nodes 100 and 150.

The wireless communication node 100 has a Central Unit (CU), which is a function for connecting to a network, and a Distributed Unit (DU), which is a function for connecting to a lower node. The wireless communication node 150 has a Mobile Terminal (MT), which is a function for connecting to a higher node, and a DU, which is a function for connecting to a lower node. The MT and DU of the wireless communication node 150 are also called IAB-MT and IAB-DU, respectively.

The wireless communication node 150 may be a mobile IAB-node (see FIG. 5). In other words, it may be an IAB-node that is movable and mounted on a moving object such as an automobile or a drone. Such a wireless communication node 150 can flexibly set the communication range (coverage) of the UE 200.

The wireless communication node 150 (150C) may perform dual connectivity (DC) with multiple upper nodes ( wireless communication nodes 150A, 150B) (see FIG. 10). Such a wireless communication node 150 (150C) is not only capable of high-speed communication, but can also connect to the network via the MCG even if a failure occurs in the SCG, for example.

(2) Functional Block Configuration of Wireless Communication System (2.1) Functional Block Configuration of Wireless Communication Node (IAB-donor) As shown in FIG. 2, the wireless communication node 100 (100A, 100B) comprises a transceiver unit 110, a NW IF unit 120, a fault reporting unit 130, and a control unit 140.

The transmitting/receiving unit 110 transmits and receives wireless signals to and from the lower node. The transmitting/receiving unit 110 may be configured as a transmitting unit that transmits wireless signals to the lower node and a receiving unit that receives wireless signals from the lower node.

The NW IF unit 120 provides a communication interface that realizes a connection to a network. The communication interface is, for example, an X2, Xn, N2, or N3 interface.

The fault reporting unit 130 reports fault information received from fault reporting units 170 and 220 of lower nodes, which will be described later, to the network. In other words, the fault reporting unit 130 constitutes a transmission unit that transmits fault information to the network.

The control unit 140 controls the transmission and reception of wireless signals by the transceiver unit 110, the provision of a communication interface by the NW IF unit 120, and the reporting of fault information by the fault reporting unit 130. The control unit 140 also cooperates with lower-level nodes to recover from faults that occur between the lower-level nodes.

(2.2) Functional Block Configuration of Wireless Communication Node (IAB-node) As shown in FIG. 3, the wireless communication node 150 (150A, 150B, 150C) includes a transceiver unit 160, a fault reporting unit 170, and a control unit 180.

The transmitting/receiving unit 160 transmits and receives wireless signals between the upper node and the lower node. The transmitting/receiving unit 110 may be configured as a transmitting unit that transmits wireless signals to the upper node and the lower node, and a receiving unit that receives wireless signals from the upper node and the lower node.

The fault reporting unit 170 reports fault information relating to faults detected by the control unit 180 (described later) to the higher-level node. The fault reporting unit 170 also reports fault information received from the fault reporting unit 220 of the lower-level node to the higher-level node. In other words, the fault reporting unit 170 constitutes a transmitting unit that transmits fault information to the higher-level node. The fault information reported (transmitted) to the higher-level node is reported (transmitted) to the network via the higher-level node.

The control unit 180 controls the transmission and reception of wireless signals by the transceiver unit 160, and the reporting of fault information by the fault reporting unit 170. The control unit 180 also cooperates with the higher-level node to recover from faults that occur between the higher-level node and the control unit 180.

The control unit 180 detects a fault that occurs between the upper node and the node. The fault may be, for example, a radio link fault (RLF) or a handover fault (HOF). The control unit 180 generates fault information indicating the content of the detected fault. The fault information is reported to the upper node by the fault reporting unit 170 as described above.

In addition, if the wireless communication node 150 is a mobile IAB-node, the control unit 180 may collect information related to the movement of the wireless communication node 150, such as the position, movement speed, flight status, etc., and include this information in the fault information generated in the event of a fault. Other specific examples of fault information generated by the control unit 180 will be described in detail in the operation example.

(2.3) Functional Block Configuration of Terminal As shown in Fig. 4, the UE 200 includes a transceiver unit 210, a fault reporting unit 220, and a control unit 230. As described above, the UE 200 is connected to the wireless communication node 150 and performs wireless communication with the wireless communication node 150, but is not limited to this. The UE 200 may be connected to the wireless communication node 100 and perform wireless communication with the wireless communication node 100, and the following description may be interpreted accordingly.

The transmitting/receiving unit 210 transmits and receives wireless signals to and from the upper node. The transmitting/receiving unit 210 may be configured as a transmitting unit that transmits wireless signals to the upper node, and a receiving unit that receives wireless signals from the upper node.

The fault reporting unit 220 reports fault information relating to faults detected by the control unit 230 (described later) to the upper node. In other words, the fault reporting unit 220 constitutes a transmission unit that transmits fault information to the upper node. The fault information reported (transmitted) to the upper node is reported (transmitted) to the network via the upper node.

The control unit 230 controls the transmission and reception of wireless signals by the transceiver unit 210, and the reporting of fault information by the fault reporting unit 220. The control unit 230 also cooperates with the higher-level node to recover from faults that occur between the higher-level node and the control unit 230.

The control unit 230 detects a fault that occurs between the upper node and the node. The fault may be, for example, a radio link fault (RLF) or a handover fault (HOF). The control unit 230 generates fault information indicating the content of the detected fault. The fault information is reported to the upper node by the fault reporting unit 220 as described above.

In addition, if the connected wireless communication node 150 is a mobile IAB-node, the control unit 230 may collect information related to its own movement, such as position (which may or may not include altitude), altitude, movement speed (horizontal speed, vertical speed), flight status, etc., and include this information in the fault information generated in the event of a fault. Other specific examples of fault information generated by the control unit 230 will be described in detail in the operation example.

In the embodiment, the fault occurring with the upper node is not a fault occurring between the upper node (wireless communication node 150) and the UE 200, but a fault occurring between the wireless communication nodes 100 and 150, as shown by the cross in FIG. 5. Meanwhile, the control unit 230 recognizes that a fault has occurred with the upper node (wireless communication node 150) when the connection with the network is lost. The control unit 230 generates fault information based on this recognition, so that, for example, if the fault information includes cell identification information, the cell identification information indicates the cell formed by the wireless communication node 150 (mobile IAB cell), not the cell formed by the wireless communication node 100 (IAB cell). In addition, if the fault information generated by the control unit 180 described above includes cell identification information, the cell identification information indicates the cell formed by the wireless communication node 100 (IAB cell).

(3) Operation of wireless communication system (3.1) Issues (3.1.1) Issue 1
When a failure such as a radio link failure (RLF) or a handover failure (HOF) occurs between an IAB-node and an upper node (IAB-donor or another IAB-node) connected to the IAB-node, the IAB-node or a UE under the IAB-node needs to report failure information to a network via the upper node. However, when the IAB-node is a mobile IAB-node configured to be movable, parameters to be reported become complicated as the IAB-node moves, so there is a risk that recovery from the failure cannot be achieved by simply reporting the failure information as in the past.

(3.1.2) Issue 2
In addition, when an IAB-node performs dual connectivity (DC) with multiple upper nodes, the selection of parameters to be reported and the reporting destination becomes complicated as the number of cells increases, and there is a risk that recovery from a failure cannot be achieved by simply reporting conventional failure information.

(3.2) Operational Examples (3.2.1) Operational Example 1
An operation example 1 for reporting fault information when an RLF occurs will be described with reference to Fig. 5 to Fig. 9. As shown in Fig. 5, the wireless communication node 150 is a mobile IAB-node.

Here, as indicated by the cross in FIG. 5, it is assumed that an RLF has occurred between the wireless communication node 150 and the upper node, the wireless communication node 100 (IAB-donor). Note that RLF may be interpreted as a concept that includes HOF. The failure (cross) may mean RLF detection or HOF, or may mean the idle state of the RRC connection. Crosses in other figures may be interpreted in the same way.

When the wireless communication node 150 or UE 200 detects an RLF, it generates fault information (RLF report) to report to the network based on the contents of the RLF. The fault information includes, for example, the following:

・source/previous cell ID, target cell ID, failed cell ID
・Reception quality of source/previous cell, reception quality of target cell, reception quality of failed cell ・Reception quality of neighboring cells ・Whether the cell that detected RLF is a mobile IAB cell or a normal (non-mobile) IAB cell Indication of whether
If the IAB-node is a mobile IAB-node, the location (which may or may not include altitude) of the mobile IAB-node or its cell, its altitude, and its moving speed (horizontal speed, vertical speed); Flying or not status
Area where RLF occurred (e.g., Tracking Area Code (TAC) of Tracking Area, RAN area code of RAN Tracking Area), previous TAC, previous RAN area code (Note that previous TAC and previous RAN area code are also used in "RLF occurred" (It may be interpreted as being included in the "area").
・Failure cause (for example, mobile IAB BH RLF, mobile IAB BH RLF recovery failure, IAB BH RLF, IAB BH RLF recovery failure, BH RLF, BH RLF recovery failure, mobile IAB migration failure, mobile IAB full migration failure, IAB migration failure) , IAB full migration failure)
- Time required from RLF detection to failure recovery (e.g., timeUntilBH-RLFRecovery (※BH-RLF: BackHaul-RadioLinkFailure))

Furthermore, with reference to Figures 6 to 8, the fault information, particularly the cell identification information (cell ID), reported when RLF/HOF occurs during handover will be explained in more detail. Specifically, the cell identification information reported by the wireless communication node 150 and the UE 200 differs at each stage of handover. Note that RLF means a radio link failure (or its detection) and HOF means a handover failure, but RLF/HOF may also mean a failure that occurs before or after handover. In other words, RLF/HOF may be a radio link failure that is not caused by handover, or a failure that is caused by a handover failure.

In Figures 6 to 8, the source IAB-donor of the transition source is the wireless communication node 100A, and the target IAB-donor of the transition destination is the wireless communication node 100B. The CU and DU of the wireless communication node 100A are CU1 and DU1, and the CU and DU of the wireless communication node 100B are CU2 and DU2. Furthermore, the wireless communication node 150 has two IAB-DU functions, which are IAB-DU1 and IAB-DU2. IAB-DU1 is connected to DU1 except during handover, and IAB-DU2 is connected to DU2 except during handover.

First, as shown in FIG. 6, the state before the start of handover will be described. Here, the wireless communication node 150 is connected to the wireless communication node 100A. Note that the UE 200 is connected to the wireless communication node 150, but it can also be said that the UE 200 is connected to the wireless communication node 100A via the wireless communication node 150. At this time, from the viewpoint of the F1 interface, the CU1 and DU1 of the wireless communication node 100A, and the IAB-MT and IAB-DU1 of the wireless communication node 150 are connected.

Therefore, when an RLF/HOF occurs between the wireless communication node 150 and the wireless communication node 100A, the cell in which the RLF/HOF occurs as recognized by the wireless communication node 150 is the cell formed by the DU1 of the wireless communication node 100A. Also, the cell in which the RLF/HOF occurs as recognized by the UE 200 is the cell formed by the IAB-DU1 of the wireless communication node 150. Note that the recognition of the wireless communication node 150 and the UE 200 may be interpreted as recognition of which cell they are connected to in terms of the F1 interface.

As a result of the above, if an RLF/HOF occurs before the start of handover, the wireless communication node 150 reports the cell identification information of the cell formed by the DU1 of the wireless communication node 100A in the fault information, and the UE 200 reports the cell identification information of the cell formed by the IAB-DU1 of the wireless communication node 150 in the fault information.

Next, the state during handover will be described as shown in FIG. 7. Here, the wireless communication node 150 is connected to the wireless communication node 100B by MT mitigation. Note that the UE 200 is connected to the wireless communication node 150, but it can also be said that it is connected to the wireless communication node 100B via the wireless communication node 150. On the other hand, from the viewpoint of the F1 interface, the handover is not complete, and the CU1 of the wireless communication node 100A, the DU2 of the wireless communication node 100B, the IAB-MT of the wireless communication node 150, and the IAB-DU1 are connected.

Therefore, when an RLF/HOF occurs between the wireless communication node 150 and the wireless communication node 100B and the handover of the F1 interface is not completed, the cell in which the RLF/HOF occurs as recognized by the wireless communication node 150 is the cell formed by the DU2 of the wireless communication node 100B. On the other hand, the cell in which the RLF/HOF occurs as recognized by the UE 200 is the cell formed by the IAB-DU1 of the wireless communication node 150. Note that the recognition of the wireless communication node 150 and the UE 200 may be interpreted as recognition of which cell they are connected to in terms of the F1 interface.

As a result of the above, if an RLF/HOF occurs before the start of handover, the wireless communication node 150 reports the cell identification information of the cell formed by DU2 of the wireless communication node 100B in the fault information, and the UE 200 reports the cell identification information of the cell formed by IAB-DU1 of the wireless communication node 150 in the fault information.

Finally, as shown in FIG. 8, the state after the handover is completed will be described. Here, the wireless communication node 150 is connected to the wireless communication node 100B. Note that the UE 200 is connected to the wireless communication node 150, but it can also be said that the UE 200 is connected to the wireless communication node 100B via the wireless communication node 150. At this time, from the viewpoint of the F1 interface, the CU2 and DU2 of the wireless communication node 100B, and the IAB-MT and IAB-DU2 of the wireless communication node 150 are connected.

Therefore, when an RLF/HOF occurs between the wireless communication node 150 and the wireless communication node 100B and handover of the F1 interface is completed, the cell in which the RLF/HOF occurs as recognized by the wireless communication node 150 is the cell formed by the DU2 of the wireless communication node 100B. Also, the cell in which the RLF/HOF occurs as recognized by the UE 200 is the cell formed by the IAB-DU2 of the wireless communication node 150. Note that the recognition of the wireless communication node 150 and the UE 200 may be interpreted as recognition of which cell they are connected to in terms of the F1 interface.

As a result of the above, if an RLF/HOF occurs before the start of a handover, the wireless communication node 150 reports the cell identification information of the cell formed by the DU2 of the wireless communication node 100B in the fault information, and the UE 200 reports the cell identification information of the cell formed by the IAB-DU2 of the wireless communication node 150 in the fault information.

With reference to FIG. 9, the sequence from RLF detection to fault information reporting will be described. First, when the wireless communication node 150 or UE 200 (UE/IAB-MT in the figure) detects RLF, it transmits an RRCRestablishmentRequest to the wireless communication node 100 (gNB/IAB-donor in the figure), which is the upper node. In response, the wireless communication node 100 transmits an RRCRestablishment to the wireless communication node 150 or UE 200.

Next, the wireless communication node 150 or the UE 200 transmits RRCRestablishmentComplete (RLF-available) to the wireless communication node 100. Note that RLF-available may be transmitted using RRCSetupComplete/RRCReconfigurationComplete/RRCResumeComplete instead of RRCRestablishmentRequest.

Finally, the wireless communication node 100 transmits a UE information request to the wireless communication node 150 or the UE 200. In response, the wireless communication node 150 or the UE 200 transmits (reports) a UE information response (RLF report, i.e., fault information) to the wireless communication node 100.

(3.2.2) Operation example 2
10 to 12, an operation example 2 for reporting fault information when RLF occurs in DC will be described. As shown in FIG. 10, the wireless communication node 150C is a mobile IAB-node, and is connected to multiple upper nodes, wireless communication nodes 150A and 150B, via DC. Furthermore, the wireless communication nodes 150A and 150B are normal (non-mobile) IAB-nodes, and are connected to the upper node, wireless communication node 100 (IAB-donor). Moreover, the wireless communication node 150A forms an MCG, and the wireless communication node 150B forms an SCG.

Here, it is assumed that an RLF occurs between wireless communication node 150C and wireless communication node 100B, which is one of multiple upper nodes, i.e., in the SCG. However, this is not limited to the above, and the following can also be applied when an RLF occurs between wireless communication node 150C and wireless communication node 100A, i.e., in the MCG (see FIG. 12). Note that RLF may be understood as a concept that includes HOF.

When the wireless communication node 150C or UE 200 detects an RLF, it generates failure information (SCG failure info, MCG failure info) to report to the network based on the contents of the RLF. The failure information includes, for example, the following:

・Previous cell ID, failed cell ID
- Reception quality of previous cell, reception quality of failed cell - Reception quality of neighboring cells - Indication of whether the cell where RLF was detected is a mobile IAB cell or a normal (non-mobile) IAB cell
If the IAB-node is a mobile IAB-node, the location (which may or may not include altitude) of the mobile IAB-node or its cell, its altitude, and its moving speed (horizontal speed, vertical speed); Flying or not status
Failure cause (e.g. mobile IAB BH RLF, IAB BH RLF, BH RLF)

With reference to Figure 11, the sequence from RLF detection in the SCG to reporting failure information will be described. First, when wireless communication node 150C or UE 200 (UE/IAB-MT in the figure) detects an RLF in the SCG, it transmits (reports) SCG failure info, i.e., failure information, to wireless communication node 150A (MN in the figure), which is the upper node.

With reference to Figure 12, the sequence from RLF detection in the MCG to reporting of failure information will be described. First, when wireless communication node 150C or UE 200 (UE/IAB-MT in the figure) detects RLF in the MCG, it transmits (reports) MCG failure info, i.e., failure information, to wireless communication node 150B (SN in the figure), which is the upper node.

(4) Actions and Effects The wireless communication node 150 and the UE 200 in the above-described embodiment report, as fault information, information related to the movement of the wireless communication node 150 to the network. As a result, even if the wireless communication node 150 is a mobile IAB-node, the fault information can be reported to the network and used for fault recovery.

The wireless communication node 150C and UE 200 in the above-described embodiment report, as fault information, the identification information of the cell in which the fault was detected to the network. As a result, even if the wireless communication node 150C is connected to multiple upper nodes, the wireless communication nodes 150A and 150B, via DC, it is possible to report fault information to the network and use the information to recover from the fault.

The fault information in the above-described embodiment may include at least one of the position, movement speed, and flight state of the wireless communication node or the cell formed by the wireless communication node. This can further enhance the content of the fault information reported to the network.

The fault information in the above-described embodiment may include the area in which the fault occurred. This makes it possible to identify areas in which the network is prone to faults.

The fault information in the above-described embodiment may include the time taken from detection of the fault to recovery from the fault. This makes it possible to know the time it will take for the network to recover from the fault.

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

In the above disclosure, the term wireless communication node is used, but it may also be called a communication node or a communication device. Also, a wireless communication node may be read as a base station.

In the disclosure above, the terms DL and UL are used, but they may also be called forward link, return link, access link, etc.

In the above disclosure, the wireless communication nodes 150 and 150C are described as being mobile IAB-nodes, but they may also be non-mobile IAB-nodes. Similarly, the wireless communication nodes 150A and 150B are described as being non-mobile IAB-nodes, but they may also be mobile IAB-nodes. Note that the wireless communication node 150 may be understood as a concept that encompasses the wireless communication nodes 150A, 150B, and 150C. Similarly, the wireless communication node 100 may be understood as a concept that encompasses the wired communication nodes 100A and 100B.

In the above disclosure, the fault information is reported by the wireless communication node 150 or the UE 200, but it may be reported by the wireless communication node 150 and the UE 200.

The above-mentioned operational examples may be combined and applied in a composite manner, as long as no contradiction occurs. For example, the DC of operational example 2 may be applied to the wireless communication node 150 of operational example 1.

In the above disclosure, configure, activate, update, indicate, enable, specify, and select may be read as interchangeable. Similarly, link, associate, correspond, and map may be read as interchangeable, and allocate, assign, monitor, and map may also be read as interchangeable.

Furthermore, specific, dedicated, UE-specific, and UE-individual may be read as interchangeable. Similarly, common, shared, group-common, UE-common, and UE-shared may be read as interchangeable.

The block diagrams (Figs. 2, 3, and 4) used to explain the above-mentioned embodiments show functional blocks. 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 may be realized using two or more devices that are physically or logically separated and directly or indirectly connected (e.g., using wires, wirelessly, etc.) and these multiple devices. The functional blocks may be realized by combining the one device or the multiple devices with software.

Functions include, but are not limited to, judgement, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, regard, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs the transmission function is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on the method of realization for any of these.

Furthermore, the above-mentioned wireless communication nodes 100, 150 and UE 200 (the devices) may function as a computer that performs processing of the wireless communication method of the present disclosure. FIG. 13 is a diagram showing an example of the hardware configuration of the devices. As shown in FIG. 13, the devices may be configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007.

In the following explanation, the term "apparatus" can be interpreted as a circuit, device, unit, etc. The hardware configuration of the apparatus may be configured to include one or more of the devices shown in the figure, or may be configured to exclude some of the devices.

Each functional block of the device (Figures 2, 3, and 4) is realized by any hardware element of the computer device, or a combination of the hardware elements.

Furthermore, each function of the device is realized by loading a specific software (program) onto hardware such as the processor 1001 and memory 1002, causing the processor 1001 to perform calculations, control communications by the communications device 1004, and control at least one of reading and writing data in the memory 1002 and storage 1003.

The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) that includes an interface with peripheral devices, a control unit, an arithmetic unit, registers, etc.

The processor 1001 also reads out programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to these. The programs used are those that cause a computer to execute at least some of the operations described in the above-mentioned embodiments. Furthermore, the various processes described above may be executed by one processor 1001, or may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

Memory 1002 is a computer-readable recording medium and may be composed of, for example, at least one of Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), Random Access Memory (RAM), etc. Memory 1002 may also be called a register, cache, main memory, etc. Memory 1002 can store a program (program code), software module, etc. capable of executing a method according to one embodiment of the present disclosure.

Storage 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned recording medium may be, for example, a database, a server, or other suitable medium including at least one of memory 1002 and storage 1003.

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 called, for example, a network device, a network controller, a network card, a communication module, etc.

The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., to realize, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).

The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

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

Furthermore, the device may be configured to include hardware such as a microprocessor, a digital signal processor (Digital Signal Processor (DSP), Application Specific Integrated Circuit (ASIC), Programmable Logic Device (PLD), Field Programmable Gate Array (FPGA), etc., and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

Furthermore, the notification of information is not limited to the aspects/embodiments described in the present disclosure and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling), broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination of these. Furthermore, RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc.

Each aspect/embodiment described in this disclosure may be applied to at least one of systems utilizing Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable systems and next generation systems enhanced therefrom. Multiple systems may also be applied in combination (e.g., a combination of at least one of LTE and LTE-A with 5G).

The processing steps, sequences, flow charts, etc. of each aspect/embodiment described in this disclosure may be reordered unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.

In this disclosure, certain operations that are described as being performed by a base station may in some cases be performed by its upper node. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and other network nodes other than the base station (such as, but not limited to, an MME or an S-GW). Although the above example shows a case where there is one other network node other than the base station, it may also be a combination of multiple other network nodes (such as an MME and an S-GW).

Information, signals (information, etc.) can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). They may be input and output via multiple network nodes.

The input and output information may be stored in a specific location (e.g., memory) or may be managed using a management table. The input and output information may be overwritten, updated, or appended. The output information may be deleted. The input information may be sent to another device.

The determination may be based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., a comparison with a predetermined value).

Each aspect/embodiment described in this disclosure may be used alone, in combination, or switched depending on the execution. In addition, notification of specific information (e.g., notification that "X is the case") is not limited to being done explicitly, but may be done implicitly (e.g., not notifying the specific information).

Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

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

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

Note that the terms explained in this disclosure and the 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 the symbol may be a signal (signaling). Also, the signal may be a message. Also, the component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

As used in this disclosure, the terms "system" and "network" are used interchangeably.

In addition, the information, parameters, etc. described in this disclosure may be represented using absolute values, may be represented using relative values from a predetermined value, or may be represented using other corresponding information. For example, a radio resource may be indicated by an index.

The names used for the above-mentioned parameters are not limiting in any respect. Furthermore, the formulas etc. using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not limiting in any respect.

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

A base station can accommodate one or more (e.g., three) cells (also called sectors). If a base station accommodates multiple cells, the overall coverage area of the base station can be divided into multiple smaller areas, and each smaller area can also provide communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

The term "cell" or "sector" refers to part or the entire coverage area of a base station and/or a base station subsystem that provides communication services within that coverage.

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

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 some other suitable terminology.

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 be a device mounted on a moving object, or the moving object itself, etc. The moving object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may include a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

Furthermore, the base station in the present disclosure may be interpreted as a mobile station (user terminal, the same applies below). For example, each aspect/embodiment of the present disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between multiple mobile stations (which may be called, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.). In this case, the mobile station may be configured to have the functions of a base station. Furthermore, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to communication between terminals (for example, "side"). For example, the uplink channel, downlink channel, etc. may be interpreted as a side channel.

Similarly, the mobile station in this disclosure may be interpreted as a base station. In this case, the base station may be configured to have the functions of the mobile station.

A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe.

A subframe may further be composed 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.

Numerology may be a communication parameter that applies to at least one of the transmission and reception of a signal or channel. Numerology may indicate, 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 structure, a particular filtering operation performed by the transceiver in the frequency domain, a particular windowing operation performed by the transceiver in the time domain, etc.

A slot may consist of one or more symbols in the time domain (e.g., Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.). A slot may be a numerology-based unit of time.

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

Radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals. Radio frame, subframe, slot, minislot, and symbol may each be referred to by a different name that corresponds to the radio frame, subframe, slot, minislot, and symbol.

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 the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit expressing the TTI may be called a slot, minislot, etc., instead of a subframe.

Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station schedules each user terminal by allocating radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) in TTI units. Note that the definition of TTI is not limited to this.

The TTI may be a transmission time unit for a channel-coded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) in which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

In addition, when one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit of scheduling. In addition, the number of slots (minislots) that constitute the minimum time unit of scheduling may be controlled.

A TTI having a time length of 1 ms may be referred to as a normal TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may be referred to as a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

Note that a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length of 1 ms or more but less than the TTI length of a long TTI.

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

Furthermore, the time domain of an RB may include one or more symbols and may be one slot, one minislot, one subframe, or one TTI in length. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

In addition, one or more RBs may also be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

Furthermore, a resource block may be composed of one or more resource elements (RE). For example, one RE may be a radio resource area of one subcarrier and one symbol.

A Bandwidth Part (BWP), which may also be referred to as a partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by an index of the RB relative to a common reference point of the carrier. PRBs may be defined in a BWP and numbered within that BWP.

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

At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal/channel outside the active BWP. Note that "cell," "carrier," etc. in this disclosure may be read as "BWP."

The above-mentioned structures of radio frames, subframes, slots, minislots, and symbols are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio 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, as well as the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, and other configurations can be changed in various ways.

The terms "connected," "coupled," or any variation thereof, refer to 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" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using at least one of one or more wires, cables, and printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

The reference signal may also be abbreviated as Reference Signal (RS) or referred to as a pilot depending on the applicable standard.

As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

Any reference to an element using a designation such as "first," "second," etc., 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 method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some way.

When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Additionally, the term "or," as used in this disclosure, is not intended to be an exclusive or.

In this disclosure, where articles have been added through translation, such as a, an, and the in English, this disclosure may include that the noun following these articles is in the plural form.

As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., searching in a table, database, or other data structure), ascertaining something that is deemed to be a "judging" or "determining," and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Additionally, "judgment" and "decision" can include considering resolving, selecting, choosing, establishing, comparing, etc., to have been "judged" or "decided." In other words, "judgment" and "decision" can include considering some action to have been "judged" or "decided." Additionally, "judgment" can be interpreted as "assuming," "expecting," "considering," etc.

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 "combined" may also be interpreted in the same way as "different."

FIG. 14 shows an example of the configuration of a vehicle 2001. As shown in FIG. 14, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021-2029, an information service unit 2012, and a communication module 2013.

The drive unit 2002 is composed 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 operated by the user.

The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2027 provided in the vehicle. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

Signals from the various sensors 2021 to 2028 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels acquired by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels acquired by an air pressure sensor 2023, a vehicle speed signal acquired by a vehicle speed sensor 2024, an acceleration signal acquired by an acceleration sensor 2025, an accelerator pedal depression amount signal acquired by an accelerator pedal sensor 2029, a brake pedal depression amount signal acquired by a brake pedal sensor 2026, a shift lever operation signal acquired by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. acquired by an object detection sensor 2028.

The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing various types of information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information acquired from external devices via the communication module 2013, etc., to provide various types of multimedia information and multimedia services to the occupants of the vehicle 1.

The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driving burden on the driver, such as a millimeter wave radar, LiDAR (Light Detection and Ranging), a camera, a positioning locator (e.g., GNSS, etc.), map information (e.g., high definition (HD) map, autonomous vehicle (AV) map, etc.), a gyro system (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chip, and an AI processor, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driving assistance functions or autonomous driving functions.

The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 1 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 between the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in electronic control unit 2010, and sensors 2021 to 2028, which are provided on the vehicle 2001.

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 an external device. For example, it transmits and receives various information to and from the external device 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, a mobile station, etc.

The communication module 2013 transmits a current signal from the current sensor input to the electronic control unit 2010 to an external device via wireless communication. The communication module 2013 also transmits to an external device via wireless communication the following signals input to the electronic control unit 2010: a front wheel or rear wheel rotation speed signal acquired by a rotation speed sensor 2022, a front wheel or rear wheel air pressure signal acquired by an air pressure sensor 2023, a vehicle speed signal acquired by a vehicle speed sensor 2024, an acceleration signal acquired by an acceleration sensor 2025, an accelerator pedal depression amount signal acquired by an accelerator pedal sensor 2029, a brake pedal depression amount signal acquired by a brake pedal sensor 2026, a shift lever operation signal acquired by a shift lever sensor 2027, and a detection signal for detecting an obstacle, a vehicle, a pedestrian, etc. acquired by an object detection sensor 2028.

The communication module 2013 receives various information (traffic information, signal information, vehicle distance information, etc.) transmitted from an external device, and displays it on an information service unit 2012 provided in the vehicle. 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, left and right front wheels 2007, left and right rear wheels 2008, axles 2009, sensors 2021-2028, and the like provided in the vehicle 2001.

　Although the present disclosure has been described in detail above, it is 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 spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended as an illustrative example and does not have any limiting meaning with respect to the present disclosure.

(Additional Note)
The above disclosure may be expressed as follows:

The first feature is a wireless communication node that includes a control unit that detects a fault that occurs between the wireless communication node and a higher-level node, and a transmission unit that transmits fault information to the higher-level node, and the fault information includes information related to the movement of the wireless communication node.

The second feature is a wireless communication node that performs dual connections with multiple upper nodes, and includes a control unit that detects a fault that occurs between the wireless communication node and the upper node, and a transmission unit that transmits fault information to the upper node, and the fault information includes identification information of the cell in which the fault is detected.

The third feature is a wireless communication node in the first or second feature, in which the fault information includes at least one of the position, movement speed, and flight state of the wireless communication node or the cell formed by the wireless communication node.

The fourth feature is that in the first feature, the fault information is a wireless communication node that includes the area where the fault occurred.

The fifth feature is a wireless communication node according to the first feature, in which the fault information includes the time required from detection of the fault to recovery from the fault.

The sixth feature is a terminal connected to a wireless communication node, the terminal comprising a control unit that detects a fault occurring between the wireless communication node and a higher-level node, and a transmission unit that transmits fault information to the higher-level node, the fault information including information related to the movement of the terminal.

10 Wireless Communication Systems 20 NG-RAN
100, 100A, 100B wireless communication node 110 transceiver unit 120 NW IF unit 130 fault reporting unit 140 control unit 150, 150A, 150B, 150C wireless communication node 160 transceiver unit 170 fault reporting unit 180 control unit 200 UE
210 Transmitting/receiving unit 220 Fault reporting unit 230 Control unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Left and right front wheels 2008 Left and right rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 Rotational 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 Driving assistance system section 2031 Microprocessor 2032 Memory (ROM, RAM)
2033 communication port

Claims (6)

1. 1. A wireless communication node, comprising:
   a control unit for detecting a fault occurring between the wireless communication node and a host node;
   A transmitter for transmitting fault information to the upper node;
   Equipped with
   the fault information includes information related to movement of the wireless communication node;
   Wireless communication node.
2. A wireless communication node that performs dual connectivity with a plurality of upper nodes,
   a control unit for detecting a fault occurring between the wireless communication node and a host node;
   A transmitter for transmitting fault information to the upper node;
   Equipped with
   The fault information includes identification information of a cell in which the fault is detected.
   Wireless communication node.
3. The fault information includes at least one of a position, a moving speed, and a flight state of the wireless communication node or a cell formed by the wireless communication node.
   2. The wireless communication node according to claim 1.
4. The fault information includes an area where the fault occurred.
   2. The wireless communication node according to claim 1.
5. The fault information includes a time required from detection of the fault to recovery from the fault.
   2. The wireless communication node according to claim 1.
6. A terminal connected to a wireless communication node,
   a control unit for detecting a fault occurring between the wireless communication node and a host node;
   A transmitter for transmitting fault information to the upper node;
   Equipped with
   The fault information includes information related to movement of the terminal.
   Terminal.

Images