Communication device and communication method

Abstract

A communication device according to the present invention comprises: a control unit that controls wireless communication with a terminal in an environment controlled by a network; and a transmission unit that transmits information about at least one of the communication device and a peripheral device in the periphery of the communication device to the network.

Description

Communication device and communication method

[0001] The present disclosure relates to a communication device and a communication method capable of performing wireless communication with a terminal (UE: User Equipment).

[0002] The 3rd Generation Partnership Project (3GPP: registered trademark) 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, known as Beyond 5G, 5G Evolution, or 6G.

[0003] For example, a white paper on 6G discusses more flexible network function placement and other aspects of network architecture (for example, Non-Patent Document 1).

[0004] NTT Docomo, "Docomo 6G White Paper 5.0 Edition," [online], January 2023, Internet <URL:https: / / www.docomo.ne.jp / binary / pdf / corporate / technology / whitepaper_6g / DOCOMO_6G_White_PaperJP_20221116.pdf>

[0005] As part of the mobile communications network architecture, 6G plans to introduce Network Controlled Access Points (NCAPs), which are access points (communications devices) that can be installed under the mobile communications network and controlled independently by the network operator.

[0006] Incidentally, when a network operator controls an NCAP, it is necessary to consider the status of the NCAP and its peripheral devices, and it is also necessary to update the status of the NCAP and its peripheral devices.

[0007] Therefore, the present disclosure has been made to solve the above-mentioned problems, and aims to provide a communication device and a communication method that allow a network operator to appropriately control NCAP.

[0008] One aspect of the disclosure is a communication device comprising: a control unit that controls wireless communication with a terminal in an environment controlled by a network; and a transmission unit that transmits information regarding the communication device and at least one of peripheral devices located in the vicinity of the communication device to the network.

[0009] One aspect of the disclosure is a communication method comprising the steps of: a communication device controlling wireless communication with a terminal in an environment controlled by a network; and transmitting information regarding at least one of the communication device and peripheral devices located in the vicinity of the communication device to the network.

[0010] FIG. 1 is a diagram illustrating an overall schematic configuration of a wireless communication system 10. FIG. 2 is a diagram illustrating a frequency range used in the wireless communication system 10. FIG. 3 is a diagram illustrating an example configuration of a wireless frame, a subframe, and a slot used in the wireless communication system 10. FIG. 4 is a functional block configuration diagram of a UE 200. FIG. 5 is a functional block configuration diagram of an NCAP 100. FIG. 6 is a functional block configuration diagram of a gNB 50. FIG. 7 is a diagram illustrating operation example 1. FIG. 8 is a diagram illustrating operation example 1. FIG. 9 is a diagram illustrating operation example 3. FIG. 10 is a diagram illustrating operation example 3. FIG. 11 is a diagram illustrating operation example 4. FIG. 12 is a diagram illustrating operation example 4. FIG. 13 is a diagram illustrating an example of the hardware configuration of a gNB 50, an NCAP 100, and a UE 200. FIG. 14 is a diagram illustrating an example configuration of a vehicle 2001.

[0011] Hereinafter, embodiments will be described with reference to the drawings. Note that the same or similar reference numerals are used to designate the same functions or configurations, and descriptions thereof will be omitted as appropriate.

[0012] (1) Overall Schematic Configuration of Wireless Communication System Fig. 1 is a diagram showing the overall schematic configuration of a wireless communication system 10 according to this embodiment. The wireless communication system 10 is a wireless communication system conforming to a standard called Beyond 5G, 5G Evolution, or 6G (hereinafter referred to as 6G), and includes a wireless base station 50 (hereinafter referred to as gNB 50), an NCAP (Network Controlled Access Point) 100, and a terminal 200. Hereinafter, the terminal 200 will be referred to as UE (User Equipment) 200. Note that the wireless communication system 10 may be a wireless communication system conforming to a specification other than 6G, such as 5G New Radio (NR).

[0013] The gNB50 is a 6G-compliant radio base station that performs 6G-compliant radio communication with the UE 200. The NCAP 100 and UE 200 are capable of supporting Massive MIMO (Multiple-Input Multiple-Output), which generates more directional antenna beams by controlling radio signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which aggregates multiple component carriers (CCs), and Dual Connectivity (DC), which simultaneously communicates between the UE and two or more RAN nodes.

[0014] The NCAP 100 is a type of communication device called an access point (AP). The NCAP 100 has a function of controlling and executing wireless communication with the UE 200 in an environment controlled by a network. The NCAP 100 may also have a function of executing wireless communication with the gNB 50.

[0015] The NCAP 100 may be referred to as an NCAP UE. The NCAP 100 may be treated as part of the gNB 50 or as part of the UE 200. The NCAP 100 may be treated as one of the device categories.

[0016] The network may include base station equipment such as a gNB or eNB, and may also include a Session Management Function (SMF), a Mobility Management Entity (MME), or equivalent core network equipment.

[0017] The NCAP 100 may be installed by an operator (which may be called a network operator or a mobile operator) of the wireless communication system 10 (mobile communication system), or may be installed freely by a subscriber of a communication service provided by the wireless communication system 10. A subscriber may be called a user.

[0018] At least one of the frequency bands (which may include band combinations, etc.), the number of antenna beams, the number of MIMO layers, and the transmission power supported by the NCAP 100 may be more limited than that of the gNB 50. The NCAP 100 can provide substantially the same functions as the gNB 50, and therefore can form a cell C1 and accommodate the UE 200.

[0019] UE 200 is typically a mobile terminal such as a smartphone, but may also be a device for the Industrial Internet of Things (IIoT) or Ultra-Reliable and Low Latency Communications (URLLC).

[0020] The wireless communication system 10 may be configured by a radio access network (RAN) configured by multiple RAN nodes such as gNBs 50 using 6G radio access technology (RAT), and a core network conforming to 6G. The RAN and the core network may be simply referred to as a "network."

[0021] The core network (CN) may be connected to the RAN and is a network configured by a switch, a subscriber information management device, etc. The UE 200 can communicate with the core network via the RAN.

[0022] In the wireless communication system 10, a control plane (C-plane) function and a user plane (U-plane) function (UPF: User Plane Function) are defined.

[0023] The C-plane may refer to a series of control processes mainly exchanged to establish communication, etc. The U-plane may refer to the process of transmitting and receiving user data.

[0024] In the core network (and some RANs), the concept of CUPS (Control and User Plane Separation) may be introduced, in which the functions of the C-plane and U-plane are clearly separated.

[0025] The C-plane function of the core network may include an Access and Mobility Management Function (AMF) that provides a management function for access and mobility of the UE 200, a Session Management Function (SMF) that provides a management function for sessions, etc. Note that the AMF and the SMF may be called by different names.

[0026] The NCAP 100 may be connected to the RAN and various controls may be performed from the network operator side via the C-plane function. At least a part of such connection and / or control may be realized using a Self-Organizing Networks (SON) framework. SON may be interpreted as a self-optimization function of a mobile communication network, including automatic configuration at the time of installation of a gNB 50 and automatic parameter optimization.

[0027] In this way, the NCAP 100 can connect to the gNB 50 via the C-plane function. The connection between the gNB 50 and the NCAP 100 may be via a RAN (RAT) or a wired network. The NCAP 100 can also provide the UE 200 with a communication path to broadband Internet and servers for MEC (Multiaccess Edge Computing) via a local area network (LAN). MEC is a mechanism for deploying servers, storage, and the like closer to users (subscribers) in a mobile communication network. Various cloud services may also be accessible via broadband Internet.

[0028] Here, the wireless communication system 10 may have the following features.

[0029] First, the wireless communication system 10 may support multiple frequency ranges (FRs) as shown in Figure 2. For example, as shown in Figure 2, the cellular network may support FR1 and FR2. The frequency bands of each FR are as follows:

[0030] ・FR1: 410 MHz to 7.125 GHz ・FR2-1: 24.25 GHz to 52.6 GHz ・FR2-2: Over 52.6 GHz to 71 GHz FR1 may use a sub-carrier spacing (SCS) of 15, 30, or 60 kHz and a bandwidth (BW) of 5 to 100 MHz. FR2 is a higher frequency than FR1 and may use an SCS of 60 kHz or 120 kHz (including 240 kHz) and a bandwidth (BW) of 50 to 400 MHz.

[0031] Furthermore, the wireless communication system 10 may also be compatible with frequency bands higher than the FR2 frequency band. Specifically, the wireless communication system 10 may be compatible with frequency bands exceeding 52.6 GHz up to 71 GHz or 114.25 GHz.

[0032] Second, the wireless communication system 10 may support the radio frames, subframes, and slots shown in FIG.

[0033] As shown in Figure 3, one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). In addition to 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz, the SCS may also use 480 kHz, 960 kHz, etc.

[0034] Furthermore, the number of symbols constituting one slot does not necessarily have to be 14 (for example, 28 symbols or 56 symbols). Furthermore, the number of slots per subframe may differ depending on the SCS.

[0035] The time direction (t) shown in Fig. 3 may be called a time domain, a symbol period, a symbol time, etc. The frequency direction may be called a frequency domain, a resource block, a subcarrier, a bandwidth part (BWP), etc.

[0036] (2) Functional Block Configuration of Wireless Communication System The functional block configuration of the wireless communication system 10 will be described below.

[0037] First, the functional block configuration of the UE 200 will be described.

[0038] Fig. 4 is a functional block diagram of UE 200. As shown in Fig. 4, UE 200 includes radio signal transmitting / receiving unit 210, amplifier unit 220, modem unit 230, control signal / reference signal processing unit 240, encoding / decoding unit 250, data transmitting / receiving unit 260, and control unit 270.

[0039] The radio signal transmitting / receiving unit 210 transmits and receives radio signals conforming to 5G or 6G. The radio signal transmitting / receiving unit 210 supports Massive MIMO, CA that uses a bundle of multiple CCs, and DC that simultaneously communicates between a UE and two NG-RAN nodes.

[0040] The amplifier unit 220 is configured by a PA (Power Amplifier) / LNA (Low Noise Amplifier), etc. The amplifier unit 220 amplifies the signal output from the modulation / demodulation unit 230 to a predetermined power level. The amplifier unit 220 also amplifies the RF signal output from the radio signal transmission / reception unit 210.

[0041] The modem unit 230 performs data modulation / demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (gNB 100 or another gNB). The modem unit 230 may apply Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM). Furthermore, DFT-S-OFDM may be used not only for the uplink (UL) but also for the downlink (DL).

[0042] The control signal and reference signal processor 240 executes processing related to various control signals transmitted and received by the UE 200 and processing related to various reference signals transmitted and received by the UE 200 .

[0043] Specifically, the control signal / reference signal processing unit 240 receives various control signals, for example, control signals of a radio resource control layer (RRC), transmitted via a predetermined control channel from the gNB 100. In addition, the control signal / reference signal processing unit 240 transmits various control signals to the gNB 100 via a predetermined control channel.

[0044] The control signal / reference signal processing unit 240 performs processing using reference signals (RS) such as a Demodulation Reference Signal (DM-RS) and a Phase Tracking Reference Signal (PT-RS).

[0045] DM-RS is a terminal-specific reference signal (pilot signal) known between the base station and the terminal to estimate the fading channel used for data demodulation. PT-RS is a terminal-specific reference signal intended to estimate phase noise, which is an issue in high frequency bands.

[0046] In addition to DM-RS and PT-RS, the reference signals may also include a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for location information.

[0047] The channels include control channels and data channels, such as a PDCCH (Physical Downlink Control Channel), a PUCCH (Physical Uplink Control Channel), a RACH (Random Access Channel), a Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI), and a Physical Broadcast Channel (PBCH).

[0048] Furthermore, the data channel includes a PDSCH (Physical Downlink Shared Channel) and a PUSCH (Physical Uplink Shared Channel). Data refers to data transmitted via the data channel. The data channel may be interpreted as a shared channel.

[0049] Here, the control signal and reference signal processor 240 may receive downlink control information (DCI). The DCI includes existing fields for storing DCI Formats, Carrier indicator (CI), BWP indicator, FDRA (Frequency Domain Resource Assignment), TDRA (Time Domain Resource Assignment), MCS (Modulation and Coding Scheme), HPN (HARQ Process Number), NDI (New Data Indicator), RV (Redundancy Version), and the like.

[0050] The value stored in the DCI Format field is an information element that specifies the format of the DCI. The value stored in the CI field is an information element that specifies the CC to which the DCI applies. The value stored in the BWP indicator field is an information element that specifies the BWP to which the DCI applies. The BWP that can be specified by the BWP indicator is set by an information element (BandwidthPart-Config) included in the RRC message. The value stored in the FDRA field is an information element that specifies the frequency domain resource to which the DCI applies. The frequency domain resource is identified by the value stored in the FDRA field and an information element (RA Type) included in the RRC message. The value stored in the TDRA field is an information element that specifies the time domain resource to which the DCI applies. The time domain resource is identified by the value stored in the TDRA field and information elements (pdsch-TimeDomainAllocationList, pusch-TimeDomainAllocationList) included in the RRC message. The time domain resource may be identified by the value stored in the TDRA field and a default table. The value stored in the MCS field is an information element that specifies the MCS to which the DCI applies. The MCS is identified by the value stored in the MCS and an MCS table. The MCS table may be specified by an RRC message or may be determined by RNTI scrambling. The value stored in the HPN field is an information element that specifies the HARQ process to which the DCI is applied. The value stored in the NDI field is an information element for specifying whether the data to which the DCI is applied is initial transmission data. The value stored in the RV field is an information element that specifies the redundancy of the data to which the DCI is applied.

[0051] The encoding / decoding unit 250 performs data division / concatenation and channel coding / decoding for each predetermined communication destination (gNB100 or another gNB).

[0052] Specifically, the encoding / decoding unit 250 divides the data output from the data transmitting / receiving unit 260 into pieces of a predetermined size, performs channel coding on the divided data, decodes the data output from the modem unit 230, and concatenates the decoded data.

[0053] The data transmitter / receiver 260 transmits and receives Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmitter / receiver 260 assembles and disassembles PDUs / SDUs in multiple layers (such as a Medium Access Control layer (MAC), a Radio Link Control layer (RLC), and a Packet Data Convergence Protocol layer (PDCP)). The data transmitter / receiver 260 also performs data error correction and retransmission control based on Hybrid Automatic Repeat Request (HARQ).

[0054] The control unit 270 controls each functional block that configures the UE 200 .

[0055] Secondly, a description will be given of the functional block configuration of the NCAP 100. The NCAP 100 may have some of the functions of the UE 200 described above, or may have some of the functions of the gNB 50 described later.

[0056] Fig. 5 is a functional block diagram of the NCAP 100. As shown in Fig. 5, the NCAP 100 includes a transmitting unit 110, a receiving unit 120, and a control unit 130. In the embodiment, the NCAP 100 is an example of a communication device.

[0057] The transmitter 110 may transmit various signals to the UE 200. For example, the transmitter 110 may transmit signals to the UE 200 via the PDCCH and the PDSCH in the same wireless communication as the wireless communication between the gNB 50 and the UE 200.

[0058] The transmitter 110 may transmit various types of information to a network (for example, the gNB 50). The transmitter 110 may transmit the information wirelessly or via a wire.

[0059] The receiving unit 120 may receive various signals from the UE 200. For example, the receiving unit 120 may receive signals from the UE 200 via the PUCCH and the PUSCH in the same wireless communication as the wireless communication between the gNB 50 and the UE 200.

[0060] The receiving unit 120 may receive various types of information from a network (for example, the gNB 50). The receiving unit 120 may receive the information wirelessly or via a wired connection.

[0061] In the embodiment, the transmitter 110 and the receiver 120 may configure a communication unit that performs wireless communication with the UE 200 in an environment controlled by a network. For example, the transmitter 110 and the receiver 120 may perform the following operations.

[0062] As will be explained in detail in Operation Example 1 below, the transmitter 110 may constitute a transmitter that transmits information regarding the NCAP 100 and at least one of the peripheral devices located around the NCAP 100 (e.g., gNB 50 or another NCAP 100) to the network.

[0063] Although details will be explained in the second operation example below, the receiving unit 120 may constitute a receiving unit that receives information related to the settings of the NCAP 100 from the network.

[0064] As will be explained in detail in operation example 3 below, the receiver 120 may constitute a receiver that receives information from the network instructing measurements regarding peripheral devices (e.g., gNB50 or other NCAP100) located in the vicinity of the NCAP100.

[0065] The control unit 130 controls each functional block that constitutes the NCAP 100.

[0066] In the embodiment, the control unit 130 may constitute a control unit that controls wireless communication with the UE 200 in an environment controlled by a network.

[0067] Third, we will explain the functional block configuration of gNB50.

[0068] Fig. 6 is a functional block diagram of the gNB 50. As shown in Fig. 6, the gNB 50 includes a transmitter 51, a receiver 52, and a controller 53. In the embodiment, the gNB 50 is an example of a communication device.

[0069] The transmitter 51 may transmit various signals to the UE 200. For example, the transmitter 51 may transmit signals to the UE 200 via a PDCCH and a PDSCH.

[0070] The transmission unit 51 may transmit various types of information to a network (for example, the NCAP 100). The transmission unit 51 may transmit information wirelessly or via a wire.

[0071] The receiver 52 may receive various signals from the UE 200. For example, the receiver 52 may receive signals from the UE 200 via the PUCCH and the PUSCH.

[0072] The receiving unit 52 may receive various types of information from a network (for example, the NCAP 100). The receiving unit 52 may receive information wirelessly or via a wired connection.

[0073] As will be explained in detail in Operation Example 1 below, the receiver 52 may receive information from the NCAP 100 regarding at least one of the gNB 50 and peripheral devices located around the gNB 50 (e.g., the gNB 50 or another gNB 50, etc.).

[0074] As will be explained in detail in operation example 2 below, the transmitter 51 may transmit information regarding the configuration of the gNB 50 to the NCAP 100.

[0075] As will be explained in detail in operation example 3 below, the transmitter 51 may transmit information to the NCAP 100 instructing measurements regarding peripheral devices (e.g., the gNB 50 or other gNBs 50) located in the vicinity of the gNB 50.

[0076] The control unit 53 controls each functional block constituting the gNB 50. The control unit 53 may be responsible for at least a part of the function of controlling communication between the NCAP 100 and the UE 200.

[0077] (3) Issues When assuming the use of the NCAP 100 described above, when a network operator controls the NCAP, it is necessary to take into account the status of the NCAP and its peripheral devices, and it is also necessary to update the status of the NCAP and its peripheral devices.

[0078] Under such a background, the inventors have conducted extensive research and found that it is preferable for a network operator to perform the following operations in order to appropriately control NCAP.

[0079] (4) Operational Examples (4.1) Operational Example 1 In Operational Example 1, the NCAP 100 transmits information about the NCAP 100 and at least one of peripheral devices located around the NCAP 100 to the network. Here, the peripheral devices may include a gNB 50 or another NCAP 100. The network may include base station equipment such as the gNB 50, and may include core network equipment such as an SMF and an MME.

[0080] The information about the NCAP 100 may include at least one of location information of the NCAP 100, information about the radio wave sector of the NCAP 100, information about the radio wave tilt of the NCAP 100, and identification information (e.g., PCI; Physical Cell ID) of the NCAP 100. The information about the NCAP 100 is not limited to these pieces of information, and may include information necessary for the base station operation of the NCAP 100 controlled from the network. The PCI may be associated with a cell frequency, or may be read as the cell frequency.

[0081] The information about the peripheral device may include at least one of information about the quality of a signal received from the peripheral device (e.g., RSRP; Reference Signal Received Power) and identification information about the peripheral device (e.g., PCI). The information about the peripheral device is not limited to these pieces of information, and may include information necessary for the NCAP 100 to perform base station operations controlled from the network. The PCI may be associated with a cell frequency or may be read as the cell frequency.

[0082] In Operational Example 1, the following options may be considered:

[0083] Option 1-1 explains how to send (report) information to the network.

[0084] In option 1-1-1, reporting may be performed via a wired line. The wired line may be a general broadband line (e.g., Broadband Internet as shown in FIG. 1). The wired line may include various interfaces for connecting to a network (e.g., X2 link, S1 link, Xn link, NG link).

[0085] In option 1-1-2, reporting may be performed wirelessly. For example, information may be reported using a PUCCH, a PUSCH, a PRACH (Physical Random Access Channel), an SRS, a DM-RS, a TRS (Tracking Reference Signal), an UCI (Uplink Control Information), etc. That is, the NCAP 100 may receive information about its configuration using the same method as wireless communication between the gNB 50 and the UE 200.

[0086] In option 1-1-2, bits included in the report may be associated with report content (meaning). For example, as shown in Fig. 7, a table associating bits with report content (meaning) is defined, and the NCAP 100 issues a report to the network including bits associated with the report content (meaning). The table (or the association between bits and report content) may be predefined in the wireless communication system 10, or may be set or instructed by the network via RRC, MAC-CE, or DCI.

[0087] In option 1-1-2, resources used in reporting may be associated with report content (meaning). For example, as shown in Fig. 8, a table associating resources with report content (meaning) is defined, and reporting is performed from the NCAP 100 to the network using resources associated with the report content (meaning). The table (or the association between bits and report content) may be predefined in the wireless communication system 10, or may be set or instructed by the network via RRC, MAC-CE, or DCI.

[0088] Option 1-2 explains the timing of sending (reporting) information to the network.

[0089] In option 1-2-1, the NCAP 100 may execute the report at a timing set by default in the NCAP 100. Such a report is an example of an aperiodic report. Although not particularly limited, option 1-2-1 may be applied in the case where the report is executed by wire (option 1-1-1).

[0090] In option 1-2-2, the NCAP 100 may perform reporting at the timing of the initial access of the NCAP 100. Such reporting is an example of aperiodic reporting. Although not particularly limited, option 1-2-1 may be applied in the case where reporting is performed wirelessly (option 1-1-2).

[0091] In option 1-2-3, the NCAP 100 may perform a report when a change in the status of the peripheral device satisfies a condition. Such a report is an example of an event-triggered report. The status of the peripheral device may be the quality of the signal (RSRP) received from the peripheral device, and the condition may be that a change in the RSRP exceeds a threshold. The status of the peripheral device may be the PCI assigned to the peripheral device, and the condition may be that the PCI is changed. In option 1-2-3, the NCAP 100 may receive information from the network instructing it to periodically measure information about the peripheral device.

[0092] In option 1-2-4, the NCAP 100 may execute a report when the NCAP 100 determines that the information of the NCAP 100 needs to be updated. Such a report is an example of an event-triggered report. The information of the NCAP 100 may include at least one of information about the radio wave sector of the NCAP 100, information about the radio wave tilt of the NCAP 100, and identification information (e.g., PCI) of the NCAP 100. The NCAP 100 may determine that the information of the NCAP 100 needs to be updated when the PCI assigned to the peripheral device is the same as the PCI assigned to the NCAP 100. The NCAP 100 may determine that the information of the NCAP 100 needs to be updated when the RSRP is greater than a threshold value, assuming that the peripheral device is located near the NCAP 100.

[0093] In option 1-2-5, the NCAP 100 may perform reporting at periodic timing. Such reporting is an example of periodic reporting. In option 1-2-5, the reporting period may be predefined in the wireless communication system 10, or may be set or instructed by the network via RRC, MAC-CE, or DCI.

[0094] In addition, the reporting period for NCAP100 may be set or instructed in the same manner (existing method) as the measurement or measurement report period for UE200, or may be set or instructed in a different manner (newly introduced method for NCAP100) from the measurement or measurement report period for UE200.

[0095] In Option 1-2, two or more options selected from Options 1-2-1 to 1-2-5 may be combined.

[0096] (4.2) Operation Example 2 In Operation Example 2, the NCAP 100 receives information about the configuration of the NCAP 100 from the network. The network may include base station equipment such as a gNB 50, and may include core network equipment such as an SMF and an MME.

[0097] The information about the settings of the NCAP 100 may include at least one of information about the radio wave sector of the NCAP 100, information about the radio wave tilt of the NCAP 100, and identification information of the NCAP 100 (for example, PCI; Physical Cell ID). The information about the NCAP 100 is not limited to these pieces of information, and may include information necessary for the execution of base station operations of the NCAP 100 controlled from the network. The PCI may be associated with a cell frequency, or may be read as the cell frequency.

[0098] In operation example 2, the following options may be considered:

[0099] Option 2-1 explains how to receive (set) information from the network.

[0100] In option 2-1-1, the configuration may be performed via a wired connection. The wired connection may be a general broadband line (e.g., Broadband Internet shown in FIG. 1). The wired connection may include various interfaces (e.g., X2 link, S1 link, Xn link, NG link) for connecting to a network.

[0101] In option 2-1-2, the configuration may be performed wirelessly. For example, the information may be reported using a PDCCH, a PDSCH, an SSB, a DM-RS, an RRC, a MAC-CE, a DCI, etc. That is, the NCAP 100 may receive information about the configuration of the NCAP 100 using the same method as the wireless communication between the gNB 50 and the UE 200.

[0102] In Option 2-1-2, similarly to Option 1-1-2, bits included in the information about the configuration may be associated with configuration contents (meanings). For example, a table associating bits with configuration contents (meanings) is defined, and the NCAP 100 performs configuration to the network using information including bits associated with the configuration contents (meanings) (see FIG. 7 ). The table (or the association between bits and report contents) may be predefined in the wireless communication system 10, or may be set or instructed by the network via RRC, MAC-CE, or DCI.

[0103] In Option 2-1-2, similarly to Option 1-1-2, resources used in the configuration may be associated with configuration contents (semantics). For example, a table associating resources with configuration contents (semantics) is defined, and the NCAP 100 performs configuration to the network using resources associated with the configuration contents (semantics) (see FIG. 8 ). The table (or the association between bits and report contents) may be predefined in the wireless communication system 10, or may be set or instructed by the network via RRC, MAC-CE, or DCI.

[0104] Option 2-2 explains the timing of receiving (setting) information from the network.

[0105] In option 2-2-1, the NCAP 100 may be instructed to perform the setting at the timing of initial setup of the NCAP 100. Such setting is an example of aperiodic setting. Although not particularly limited, option 2-2-1 may be applied in a case where the setting is performed over a wired connection (option 2-1-1).

[0106] In option 2-2-2, the NCAP 100 may be instructed to perform the setting at the timing of initial access of the NCAP 100. Such setting is an example of aperiodic setting. Although not particularly limited, option 2-2-1 may be applied in a case where the setting is performed wirelessly (option 2-1-2).

[0107] In option 2-2-3, the NCAP 100 may be instructed to perform the setting when a change in the status of the peripheral device satisfies a condition. Such setting is an example of an event-triggered setting. The status of the peripheral device may be the quality of the signal (RSRP) received from the peripheral device, and the condition may be that a change in the RSRP exceeds a threshold. The status of the peripheral device may be the PCI assigned to the peripheral device, and the condition may be that the PCI is changed. In option 2-2-3, the NCAP 100 may receive information from the network instructing it to periodically measure information about the peripheral device.

[0108] In option 2-2-4, the NCAP 100 may be instructed to perform the setting when the NCAP 100 determines that the information of the NCAP 100 needs to be updated. Such a setting is an example of an event-triggered setting. The information of the NCAP 100 may include at least one of information about the radio wave sector of the NCAP 100, information about the radio wave tilt of the NCAP 100, and identification information (e.g., PCI) of the NCAP 100. The NCAP 100 may determine that the information of the NCAP 100 needs to be updated when the PCI assigned to the peripheral device is the same as the PCI assigned to the NCAP 100. The NCAP 100 may determine that the information of the NCAP 100 needs to be updated when the RSRP is greater than a threshold value, assuming that the peripheral device is located near the NCAP 100.

[0109] In option 2-2-5, the NCAP 100 may be instructed to perform the configuration at periodic timing. Such configuration is an example of periodic configuration. In option 2-2-5, the configuration period may be predefined in the wireless communication system 10, or may be set or instructed by the network via RRC, MAC-CE, or DCI.

[0110] In addition, the setting period for NCAP100 may be set or instructed in the same manner (existing method) as the measurement or measurement setting period for UE200, or may be set or instructed in a different manner (a method newly introduced for NCAP100) from the measurement or measurement setting period for UE200.

[0111] In Option 2-2, two or more options selected from Options 2-2-1 to 2-2-5 may be combined.

[0112] In option 2-2, the NCAP 100 may request the network to configure the NCAP 100. The timing for requesting the configuration of the NCAP 100 may include the timing of one or more options selected from the above-described options 2-2-1 to 2-2-5.

[0113] In option 2-2, the NCAP 100 may assume that configuration of the NCAP 100 is performed following the report described in operation example 1 (transmission of information about the NCAP 100 and at least one of the peripheral devices located around the NCAP 100). The timing of the report described in operation example 1 may include the timing of one or more options selected from options 1-2-1 to 1-2-5 described in operation example 1. The report described in operation example 1 may be read as a request for configuration of the NCAP 100, or may include a request for configuration of the NCAP 100.

[0114] (4.3) Operation Example 3 In Operation Example 3, the NCAP 100 receives information from the network instructing measurements on peripheral devices located around the NCAP 100. Here, the peripheral devices may include a gNB 50 or other NCAPs 100. The network may include base station equipment such as the gNB 50, and may include core network equipment such as an SMF and an MME.

[0115] The measurements related to the peripheral device may include measurements of the quality of the signal received from the peripheral device (e.g., RSRP). The measurements related to the peripheral device are not limited to quality measurements and may include measurements of information necessary for the NCAP 100 to perform base station operations controlled from the network.

[0116] Option 3-1 explains how to receive information from the network (measurement instructions).

[0117] In option 3-1-1, the measurement instruction may be performed via a wired line. The wired line may be a general broadband line (e.g., Broadband Internet shown in FIG. 1). The wired line may include various interfaces (e.g., X2 link, S1 link, Xn link, NG link) for connecting to a network.

[0118] In option 3-1-2, the measurement instruction may be performed wirelessly. For example, the information may be reported using PDCCH, PDSCH, SSB, DM-RS, RRC, MAC-CE, DCI, etc. That is, NCAP100 may receive information about its configuration using the same method as wireless communication between gNB50 and UE200.

[0119] Option 3-2 explains the timing of receiving information (measurement instructions) from the network.

[0120] In option 3-2-1, the NCAP 100 may be instructed to perform measurement at the timing of the initial setting of the NCAP 100. Such a setting is an example of an aperiodic setting. Although not particularly limited, option 3-2-1 may be applied in a case where the setting is performed by wire (option 3-1-1).

[0121] In option 3-2-2, the NCAP 100 may be instructed to perform measurement at the timing of initial access of the NCAP 100. Such a setting is an example of aperiodic setting. Although not particularly limited, option 3-2-1 may be applied in the case where setting is performed wirelessly (option 3-1-2).

[0122] In option 3-2-3, the NCAP 100 may be instructed to perform measurement when a change in the status of the peripheral device satisfies a condition. Such a setting is an example of an event trigger setting. The status of the peripheral device may be the quality of the signal (RSRP) received from the peripheral device, and the condition may be that a change in the RSRP exceeds a threshold. The status of the peripheral device may be the PCI assigned to the peripheral device, and the condition may be that the PCI is changed. In option 3-2-3, the NCAP 100 may receive information from the network instructing it to periodically measure information about the peripheral device.

[0123] In option 3-2-4, the NCAP 100 may be instructed to perform measurement when the NCAP 100 determines that the information of the NCAP 100 needs to be updated. Such a setting is an example of an event trigger setting. The information of the NCAP 100 may include at least one of information about the radio wave sector of the NCAP 100, information about the radio wave tilt of the NCAP 100, and identification information (e.g., PCI) of the NCAP 100. The NCAP 100 may determine that the information of the NCAP 100 needs to be updated when the PCI assigned to the peripheral device is the same as the PCI assigned to the NCAP 100. The NCAP 100 may determine that the information of the NCAP 100 needs to be updated when the RSRP is greater than a threshold value, assuming that the peripheral device is located near the NCAP 100.

[0124] In option 3-2-5, the NCAP 100 may be instructed to perform measurements at periodic timing. Such a setting is an example of periodic setting. In option 3-2-5, the setting period may be predefined in the wireless communication system 10, or may be set or instructed by the network via RRC, MAC-CE, or DCI.

[0125] In addition, the setting period for NCAP100 may be set or instructed in the same manner (existing method) as the measurement or measurement setting period for UE200, or may be set or instructed in a different manner (a method newly introduced for NCAP100) from the measurement or measurement setting period for UE200.

[0126] In Option 3-2, two or more options selected from Options 3-2-1 to 3-2-5 may be combined.

[0127] In Option 3-3, the relationship between a measurement instruction to the existing UE 200 and a measurement instruction to the NCAP 100 will be described. For example, a measurement instruction to the existing UE 200 is set by the information elements shown in Figs. 9 and 10. The information elements may be set by the RRC. The information elements may include information elements specified in 3GPP TS38.331. Under this premise, Option 3-3 may include the following options.

[0128] In option 3-3-1, the measurement instruction to the NCAP 100 may be set together with the measurement instruction to the existing UE 200. In such a case, the information element shown in Fig. 9 may be reused in the measurement instruction to the NCAP 100. The reuse may mean that the NCAP 100 interprets the information element shown in Fig. 9 to reinterpret the measurement instruction to the existing UE 200 as the measurement instruction to the NCAP 100.

[0129] In option 3-3-2, the measurement instruction to the NCAP 100 may be set separately from the existing measurement instruction to the UE 200. In such a case, the information element regarding the measurement instruction to the NCAP 100 may be defined separately from the information element regarding the existing measurement instruction to the UE 200 (see FIGS. 9 and 10). The information element regarding the measurement instruction to the NCAP 100 may be considered to be a newly introduced information element. The newly introduced information element may include an information element corresponding to MeasConfig / MeasIdleConfig, and such an information element may be referred to as MeasConfigNCAP. The newly introduced information element may include an information element indicating the measurement target of the NCAP 100 in MeasConfig / MeasIdleConfig (see FIG. 9), or may include an information element indicating the measurement target of the NCAP 100 in MeasObjectToAddModList (see FIG. 10). Such an information element may be referred to as measObjectPCI.

[0130] In option 3-4, the NCAP 100 may send information to the network requesting measurements about the peripheral device (hereinafter referred to as a measurement request). The network receiving such a measurement request may act in the following options:

[0131] In option 3-4-1, the measurement request is information requesting that the network perform measurements on the peripheral device. The network may perform measurements on the peripheral device in response to the measurement request and transmit the results of the measurements on the peripheral device to the NCAP 100. In other words, the measurement request may be interpreted as a request to notify the results of the measurements on the peripheral device (a measurement result notification request).

[0132] In option 3-4-2, the measurement request is information requesting that the network perform measurements on the peripheral device. The network may perform measurements on the peripheral device in response to the measurement request, and perform the configuration described in operation example 2 based on the results of the measurements on the peripheral device. In other words, the measurement request may be interpreted as a request for the configuration of the NCAP 100 described in operation example 2.

[0133] In option 3-4-3, the measurement request is information requesting that the NCAP 100 perform measurements on the peripheral device. The network notifies the NCAP 100 of information indicating whether or not to permit the measurement in response to the measurement request. That is, the measurement request may be interpreted as a measurement permission request requesting permission to perform the measurement. In such a case, if the NCAP 100 is not permitted by the network even after a certain period of time has elapsed since sending the measurement permission request, the NCAP 100 may perform measurements on the peripheral device without permission from the network.

[0134] In option 3-5, the NCAP 100 may receive information from the network indicating the timing for reporting the measurement results for the peripheral device. The timing for reporting may include the timing for one or more options selected from option 1-2-1 to option 1-2-5 described in operation example 1. The transmission of information about the peripheral device may be interpreted as a measurement result report. The timing for reporting may be set together with the measurement instruction or may be set separately from the measurement instruction.

[0135] (4.4) Operation Example 4 In Operation Example 4, a procedure will be described that is premised on at least one of the above-mentioned Operation Examples 1 to 3. The following options are possible as the procedure.

[0136] Option 4-1 describes the RA (Random Access) procedure, which may be considered as an example of initial access to the NCAP 100.

[0137] 11, in step S10, the NCAP 100 transmits Msg.1 to the NW. Msg.1 may be transmitted via a PRACH (Physical Random Access Channel). Msg.1 may also be referred to as a PRACH preamble.

[0138] In step S11, the NCAP 100 receives Msg.2 from the NW. Msg.2 may be transmitted via a PDSCH. Msg.2 may be referred to as a Random Access Response (RAR).

[0139] In step S12, the NCAP 100 transmits Msg. 3 to the NW. Msg 3 may be referred to as an RRC Connection Request.

[0140] In step S13, the NCAP 100 receives Msg. 4 from the NW. Msg. 4 may be referred to as RRC Connection Setup.

[0141] Under these assumptions, the following options are possible:

[0142] In option 4-1-1, the NCAP 100 may use Msg.1 to perform the report described in Operation Example 1. In such a case, the NCAP 100 may use Msg.2 or Msg.4 to instruct the setting described in Operation Example 2.

[0143] In option 4-1-2, the NCAP 100 may use Msg. 3 to perform the report described in Operation Example 1. In such a case, the NCAP 100 may use Msg. 4 to instruct the setting described in Operation Example 2.

[0144] In option 4-1-3, NCAP 100 may use Msg. 1 to report information about peripheral devices (part of the report described in operation example 1). In such a case, NCAP 100 may set information about NCAP 100 based on the information about peripheral devices reported in Msg. 1, and may use Msg. 3 to report information about NCAP 100 (part of the report described in operation example 1).

[0145] In option 4-1-4, the NCAP 100 may use Mgs.1 to explicitly or implicitly send a measurement request to the NW (the measurement request described in option 3-4 of operation example 3). In such a case, the NCAP 100 may use Mg.2 to receive information about peripheral devices. The NCAP 100 may set information about the NCAP 100 based on the information about the peripheral devices received in Mg.2, and may use Mg.3 to report information about the NCAP 100 (part of the report described in operation example 1).

[0146] In option 4-1-5, options 4-1-3 and 4-1-4 may be combined. That is, the NCAP 100 may set information about itself based on the information about the peripheral device reported in Msg.1 and the information about the peripheral device received in Msg.2, and may also use Msg.3 to report information about the NCAP 100 (part of the report described in operation example 1).

[0147] In option 4-1-6, the NCAP 100 may use Msg.1 to report information about peripheral devices (part of the report described in Operation Example 1). Based on the information about peripheral devices reported in Msg.1, information about the NCAP 100 may be determined, and the NCAP 100 may use Msg.3 to report information about the NCAP 100 (part of the report described in Operation Example 1). Subsequently, the NCAP 100 may use Msg.4 to instruct the settings described in Operation Example 2.

[0148] In option 4-1-7, the NCAP 100 may explicitly or implicitly send a measurement request to the NW using Mgs.1 (the measurement request described in option 3-4 of operation example 3). In such a case, the NCAP 100 may receive information about peripheral devices using Msg.2. The NCAP 100 may determine information about itself based on the information about the peripheral devices received in Msg.2, and may report information about the NCAP 100 using Msg.3 (part of the report described in operation example 1). Subsequently, the NCAP 100 may be instructed to perform the settings described in operation example 2 using Msg.4.

[0149] In option 4-1-8, options 4-1-6 and 4-1-7 may be combined. That is, the NCAP 100 may determine information about itself based on the information about the peripheral device reported in Msg.1 and the information about the peripheral device received in Msg.2, and may report the information about the NCAP 100 using Msg.3 (part of the report described in operation example 1). Subsequently, the NCAP 100 may be instructed to perform the setting described in operation example 2 using Msg.4.

[0150] Although Option 4-1 illustrates a 4-step RA procedure, Option 4-1 may also be applied to a 2-step RA procedure. For example, NCAP 100 may use Msg. A to execute the report described in Operation Example 1. In such a case, NCAP 100 may use Msg. B to instruct the setting described in Operation Example 2.

[0151] In option 4-1, assuming the configuration of NCAP100 described in operation example 2 using Msg.2, Msg.4 or Msg.B, if the configuration of NCAP100 is not performed by the network, the information of NCAP100 may be set as shown below.

[0152] In Alt.1, the NCAP 100 may determine that it is not necessary to consider the status of the peripheral devices, and may set the information of the NCAP 100 itself. The following methods are conceivable for setting the information of the NCAP 100.

[0153] In Alt.1-1, the information of the NCAP 100 (such as the sector, tilt, and PCI) may be predefined in the wireless communication system 10. For example, default values ​​may be defined as the information of the NCAP 100.

[0154] In Alternative 1-2, a table or a derivation formula for deriving information for the NCAP 100 may be predefined in the wireless communication system 10. The table or the derivation formula may be a table or a derivation formula for deriving information for the NCAP 100 based on parameters. The parameters may include information measurable by the NCAP 100 (e.g., the quality of a signal received from a peripheral device (RSRP)).

[0155] In Alt.1-3, the NCAP 100 may set the information of the NCAP 100 according to the implementation conditions of the NCAP 100. The implementation conditions may be determined by the manufacturer of the NCAP 100 or the like.

[0156] In Alt.2, in order to suppress interference with peripheral devices, the NCAP 100 may not transmit a signal from the NCAP 100. In such a case, the NCAP 100 may perform the following operations.

[0157] In Alt.2-1, the NCAP 100 may again request the setting of information about the NCAP 100. The setting request may include information about the NCAP 100, or may not include information about the NCAP 100. The setting request may include information about peripheral devices, or may not include information about peripheral devices. The setting request may be a setting request for the NCAP 100 described in Operation Example 2, or may be a measurement request described in Operation Example 3. The setting request may be a retransmission of Msg.1, Msg.3, or Msg.A.

[0158] In Alt.2-2, the NCAP 100 may request the setting of Alt.2-1 at a cycle of X. X may be expressed in units of ms, symbols, sub-slots, or slots. The value of X may be predefined in the wireless communication system 10 or may be broadcast from the network.

[0159] In Alt.2-3, the NCAP 100 may repeat the request for setting Alt.2-2 N times, where N may be an integer equal to or greater than 1. The value of N may be predefined in the wireless communication system 10 or may be broadcast from the network.

[0160] In Alt.2-4, the NCAP 100 may perform the operation of Alt.1 if the configuration of the NCAP 100 is not performed by the network even after performing the configuration request of Alt.2-2 or ALT.2-3.

[0161] Option 4-2 describes the Measurement report procedure, which may be event-triggered or periodic.

[0162] 12, in step S20, the NCAP 100 receives a measurement instruction from the NW. Step S20 may be considered as an example of the above-mentioned operation example 3.

[0163] In step S21, the NCAP 100 transmits a measurement result report to the NW. Step S21 may be considered as an example of the above-mentioned operation example 1.

[0164] In step S22, the NCAP 100 receives a setting instruction from the NW. Step S22 may be considered as an example of the above-mentioned second operation example.

[0165] In option 4-2, when the configuration of the NCAP 100 is not performed by the network, the information of the NCAP 100 may be configured as shown below.

[0166] In Alt.1, the NCAP 100 may determine that it is not necessary to consider the status of the peripheral devices, and may set the information of the NCAP 100 itself. The following methods are conceivable for setting the information of the NCAP 100.

[0167] In Alt.1-1, the information of the NCAP 100 (such as the sector, tilt, and PCI) may be predefined in the wireless communication system 10. For example, default values ​​may be defined as the information of the NCAP 100.

[0168] In Alternative 1-2, a table or a derivation formula for deriving information for the NCAP 100 may be predefined in the wireless communication system 10. The table or the derivation formula may be a table or a derivation formula for deriving information for the NCAP 100 based on parameters. The parameters may include information measurable by the NCAP 100 (e.g., the quality of a signal received from a peripheral device (RSRP)).

[0169] In Alt.1-3, the NCAP 100 may set the information of the NCAP 100 according to the implementation conditions of the NCAP 100. The implementation conditions may be determined by the manufacturer of the NCAP 100 or the like.

[0170] In Alt.2, in order to suppress interference with peripheral devices, the NCAP 100 may not transmit a signal from the NCAP 100. In such a case, the NCAP 100 may perform the following operations.

[0171] In Alt.2-1, the NCAP 100 may again request the setting of the information of the NCAP 100. The setting request may include the measurement result report of step S21, or may not include the measurement result report of step S21. The setting request may also be a retransmission of the measurement result report of step S21.

[0172] In Alt.2-2, the NCAP 100 may request the setting of Alt.2-1 at a cycle of X. X may be expressed in units of ms, symbols, sub-slots, or slots. The value of X may be predefined in the wireless communication system 10 or may be broadcast from the network.

[0173] In Alt.2-3, the NCAP 100 may repeat the request for setting Alt.2-2 N times, where N may be an integer equal to or greater than 1. The value of N may be predefined in the wireless communication system 10 or may be broadcast from the network.

[0174] In Alt.2-4, the NCAP 100 may perform the operation of Alt.1 if the configuration of the NCAP 100 is not performed by the network even after performing the configuration request of Alt.2-2 or ALT.2-3.

[0175] (4.5) Operation Example 5 In operation example 5, the initial access of the NCAP 100 may be defined separately from the initial access of the UE 200 .

[0176] For example, the initial access of NCAP100 may include transmission and reception of information elements different from those in the initial access of UE200, or may include transmission and reception of messages different from those in the initial access of UE200. The initial access of NCAP100 may include procedures for performing at least some of the operations described in Operation Example 1. The initial access of NCAP100 may include procedures for performing at least some of the operations described in Operation Example 2. The initial access of NCAP100 may include procedures for performing at least some of the operations described in Operation Example 3.

[0177] For example, the SSB (PSS; Primary Synchronization Signal, SSS; Secondary Synchronization Signal) used for the initial access of the NCAP 100 may be transmitted at a frequency and / or time position different from the SSB used for the initial access of the UE 200.

[0178] (5) Actions and Effects In an embodiment, the NCAP 100 may transmit information about at least one of the gNB 50 and peripheral devices located around the gNB 50 (e.g., the gNB 50 or another gNB 50, etc.) to the network (see Operation Example 1, etc.). Such a configuration allows the network to grasp the status of the NCAP 100 and the peripheral devices of the NCAP 100, allowing the network operator to appropriately control the NCAP.

[0179] In an embodiment, the NCAP 100 may receive information about the settings of the NCAP 100 from the network (see Operation Example 2, etc.). Such a configuration can suppress arbitrary settings by the NCAP 100, allowing the network operator to appropriately control the NCAP.

[0180] In an embodiment, the NCAP 100 may receive information from the network instructing measurement of peripheral devices (e.g., gNB 50 or other NCAP 100) located around the NCAP 100 (see Operation Example 3, etc.). According to such a configuration, since it is assumed that measurement results will be obtained in response to a measurement instruction, the network can grasp the status of the NCAP 100 and the peripheral devices of the NCAP 100, and the network operator can appropriately control the NCAP.

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

[0182] In the above disclosure, SRS may be read as SRS for MIMO, Positioning, Codebook, Non-codebook, Beam management, Antenna switching, etc.

[0183] In the above disclosure, the network (NW) may be read as gNB, TRP, LMF, etc.

[0184] In the above disclosure, "configured or instructed by the network (NW)" may be read as "configured / activated / indicated by the network (NW) via RRC / MAC CE / DCI."

[0185] Although not specifically mentioned in the above disclosure, the UE 200 connected to the network configured by the NCAP 100 may or may not be separately connected to a radio base station on the network operator side. The operation of the NCAP 100 and / or the UE 200 may differ depending on whether or not the connection is established. Note that the network configured by the NCAP 100 may use a licensed band or an unlicensed band.

[0186] Furthermore, the block diagrams (FIGS. 4 to 6) used to explain the above-described embodiments show functional blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (e.g., wired, wireless, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or multiple devices.

[0187] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how each is implemented.

[0188] Furthermore, the above-described gNB 50, NCAP 100, and UE 200 (hereinafter, 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 including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0189] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the apparatus may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0190] Each functional block of the device (see FIGS. 4 to 6) is realized by any hardware element of the computer device or a combination of the hardware elements.

[0191] In addition, each function of the device is realized by loading specified software (programs) onto hardware such as processor 1001 and memory 1002, causing processor 1001 to perform calculations, control communication via communication device 1004, and control at least one of reading and writing data in memory 1002 and storage 1003.

[0192] The processor 1001 controls the entire computer by running, for example, an operating system, and may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, and registers.

[0193] The processor 1001 also reads 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 in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described 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.

[0194] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 may store a program (program code), a software module, etc., capable of executing a method according to an embodiment of the present disclosure.

[0195] 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 disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy 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.

[0196] The communication device 1004 is hardware (transmission / reception 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, or a communication module.

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

[0198] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives 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).

[0199] Furthermore, each device such as the processor 1001 and the memory 1002 is connected to 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.

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

[0201] 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 thereof. Furthermore, the 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, or the like.

[0202] Each aspect / embodiment described in the present disclosure may be applied to at least one of a system using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, a 4th generation mobile communication system (4G), a 5th generation mobile communication system (5G), a 6th generation mobile communication system (6G), an xth generation mobile communication system (xG) (where x is, for example, an integer or a decimal), 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 system, and a next-generation system extended based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G) may also be applied.

[0203] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. 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.

[0204] In the present disclosure, a specific operation described as being performed by a base station may, in some cases, be performed by its upper node. It is clear that in a network consisting of one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by at least one of the base station and another network node other than the base station (such as, but not limited to, an MME or an S-GW). While the above example illustrates a case in which there is one other network node other than the base station, a combination of multiple other network nodes (such as an MME and an S-GW) may also be used.

[0205] Information, signals (information, etc.) may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0206] The input and output information may be stored in a specific location (for example, a memory) or may be managed using a management table. The input and output information may be overwritten, updated, or added. The output information may be deleted. The input information may be transmitted to another device.

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

[0208] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

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

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

[0211] The information, signals, etc. 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, 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.

[0212] Note that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

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

[0214] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0215] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions 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 intended to be limiting in any way.

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

[0217] A base station can accommodate one or more (e.g., three) cells (also called sectors). When 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 be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0218] The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

[0219] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

[0220] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

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

[0222] At least one of the base station and the mobile station may be referred to as 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 mobile object, the mobile object itself, etc. The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile 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 also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0223] Furthermore, a base station in the present disclosure may be read as a mobile station (user terminal, the same applies hereinafter). For example, the aspects / embodiments 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) or Vehicle-to-Everything (V2X)). 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 read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel (or sidelink).

[0224] Similarly, a mobile station in the present disclosure may be interpreted as a base station, in which case the base station may have the functions of a mobile station.

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

[0226] Numerology may be a communication parameter applied to the transmission and / or reception of a signal or channel, and may indicate, for example, at least one of a subcarrier spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI), a number of symbols per TTI, a radio frame structure, a particular filtering operation performed by a transceiver in the frequency domain, a particular windowing operation performed by a transceiver in the time domain, etc.

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

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

[0229] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0230] 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. That is, 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 representing the TTI may be called a slot, minislot, etc., instead of a subframe.

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

[0232] The TTI may be a transmission time unit for a channel-encoded 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) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0233] 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 for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

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

[0235] In addition, 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 shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0236] A resource block (RB) is a resource allocation unit in the time domain and the 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 numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.

[0237] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0238] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0239] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0240] A Bandwidth Part (BWP) (which may also be referred to as a fractional 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 their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

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

[0242] 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 the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0243] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. 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, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be variously changed.

[0244] 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 one or more wires, cables, and / or 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.

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

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

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

[0248] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. 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.

[0249] 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." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0250] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0251] 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, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining something that constitutes a "determination," 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. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0252] In the present 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 "coupled" may also be interpreted in the same way as "different."

[0253] 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 to be illustrative and does not have any limiting meaning on the present disclosure.

[0254] 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 to 2029, an information service unit 2012, and a communication module 2013.

[0255] 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, memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals from various sensors 2021 to 2027 provided in the vehicle are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0256] The 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 obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

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

[0258] The information service unit 2012 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0259] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, 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.

[0260] 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 to and from a driving 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, a microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2028, which are provided in the vehicle 2001.

[0261] 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, or the like.

[0262] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021 to 2028 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021 to 2028, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.

[0263] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle-to-vehicle information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle. The information service unit 2012 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from external devices 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 to 2028, and the like provided in the vehicle 2001.

[0264] (Note) A first feature is a communication device comprising: a control unit that controls wireless communication with a terminal in an environment controlled by a network; and a transmission unit that transmits information about the communication device and at least one of peripheral devices located around the communication device to the network.

[0265] A second feature is a communication device according to the first feature, wherein the information about the communication device includes at least one of location information of the communication device, information about a sector of radio waves of the communication device, information about a tilt of radio waves of the communication device, and identification information of the communication device.

[0266] A third feature is a communication device according to the first or second feature, wherein the information about the peripheral device includes at least one of information about the quality of a signal received from the peripheral device and identification information of the peripheral device.

[0267] A fourth feature is a communication device in which, in at least one of the first to third features, the transmitting unit transmits information regarding at least one of the communication device and the peripheral device using the same method as wireless communication between the network and the terminal.

[0268] A fifth feature is a communication device in which, in at least one of the first to fourth features, the transmission unit transmits information about the communication device and at least one of the peripheral devices at at least one of the timing of initial configuration of the communication device, the timing of initial access of the communication device, the timing when a change in the status of the peripheral device satisfies a condition, the timing when the communication device determines that information about the communication device needs to be updated, and periodic timing.

[0269] A sixth feature is a communication method comprising: a step of a communication device controlling wireless communication with a terminal in an environment controlled by a network; and a step of transmitting information regarding at least one of the communication device and peripheral devices located in the vicinity of the communication device to the network.

[0270] 10 Wireless communication system 50 gNB 51 Transmitter 52 Receiver 53 Controller 100 NCAP 110 Transmitter 120 Receiver 130 Controller 200 UE 210 Wireless signal transmitter / receiver 220 Amplifier 230 Modulator / demodulator 240 Control signal / reference signal processor 250 Encoder / decoder 260 Data transmitter / receiver 270 Controller C1 Cell 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 RPM 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 unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port

Claims

1. A communication device comprising: a control unit that controls wireless communication with a terminal in an environment controlled by a network; and a transmission unit that transmits information regarding at least one of the communication device and peripheral devices located in the vicinity of the communication device to the network.

2. The communication device of claim 1, wherein the information about the communication device includes at least one of location information of the communication device, information about the radio wave sector of the communication device, information about the tilt of the radio wave of the communication device, and identification information of the communication device.

3. The communication device according to claim 1, wherein the information relating to the peripheral device includes at least one of information relating to the quality of a signal received from the peripheral device and identification information of the peripheral device.

4. The communication device according to claim 1, wherein the transmitting unit transmits information relating to at least one of the communication device and the peripheral device using the same method as the wireless communication between the network and the terminal.

5. The communication device according to claim 1, wherein the transmitting unit transmits information about at least one of the communication device and the peripheral device at at least one of the timings of initial setting of the communication device, timing of initial access of the communication device, timing when a change in the status of the peripheral device satisfies a condition, timing when the communication device determines that information about the communication device needs to be updated, and periodic timing.

6. A communication method comprising the steps of: a communication device controlling wireless communication with a terminal in an environment controlled by a network; and transmitting information regarding at least one of the communication device and peripheral devices located in the vicinity of the communication device to the network.

Images