Terminal, base station, radio communication system, and radio communication method

A-IoT enabled UEs receive resource configuration from base stations to communicate with A-IoT devices in inactive states, addressing the challenge of resource allocation in Ambient IoT.

JP2025157077APending Publication Date: 2025-10-15NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2024194676
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-11-06
Publication Date
2025-10-15

AI Technical Summary

Technical Problem

In Ambient IoT, there is a need to clarify the method for allocating resources for communication with A-IoT devices when they are not connected to a base station, such as in an RRC inactive or idle state.

Method used

A-IoT enabled UEs receive configuration information for resources from a base station when not connected, allowing them to communicate with A-IoT devices using lower layers.

Benefits of technology

Enables appropriate resource allocation for communication with A-IoT devices in inactive states, facilitating efficient communication without a direct connection to the base station.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2025157077000001_ABST
    Figure 2025157077000001_ABST
Patent Text Reader

Abstract

To provide a terminal, a base station, a radio communication system, a radio communication method that appropriately allocate a resource of communication executed with an A-IoT device in a state where a terminal is not connected to the base station.SOLUTION: A terminal comprises: a control section that controls communication with a communication device by using a lower layer; and a receiving section that receives, from a base station, setting information of a resource used in the communication using the lower layer in a state where the terminal is not connected to the base station. The control section executes communication with the communication device on the basis of the setting information in a state where the terminal is not connected to the base station.SELECTED DRAWING: Figure 5
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present disclosure relates to a terminal, a base station, a wireless communication system, and a wireless communication method that support Ambient IoT. [Background technology]

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

[0003] Furthermore, in 3GPP Release-19, in order to support IoT (Internet of Things), technology (Ambient IoT) related to communication devices (hereinafter referred to as A-IoT devices) having a simpler configuration than that of a UE is being considered (for example, Non-Patent Document 1). [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TR38.848 V18.0.0, September 2023 Summary of the Invention

[0005] In Ambient IoT, a topology using a terminal functioning as a reader (hereinafter referred to as Topology 2) is assumed. In Topology 2, a terminal functioning as a reader may be referred to as an A-IoT enabled UE.

[0006] Against this background, the inventors conducted extensive research and discovered that there may be cases in which an A-IoT enabled UE communicates with an A-IoT device when it is not connected to a base station (e.g., in an RRC inactive state or an RRC idle state), and that in such cases, there is a need to clarify the method for allocating resources for communication with an A-IoT device in an inactive state.

[0007] Therefore, the present disclosure has been made to solve the above-mentioned problems, and aims to provide a terminal, base station, wireless communication system, and wireless communication method that can appropriately allocate resources for communication with an A-IoT device when not connected to a base station in Ambient IoT.

[0008] The outline of the disclosure is a terminal comprising: a control unit that controls communication using a communication device and a lower layer; and a receiving unit that receives configuration information for resources to be used in communication using the lower layer from a base station when not connected to the base station, and the control unit communicates with the communication device based on the configuration information when not connected to the base station.

[0009] The outline of the disclosure is a base station comprising: a control unit that controls communication between a communication device and a terminal that performs communication using a lower layer; and a transmission unit that transmits configuration information for resources used in communication using the lower layer to the terminal when the terminal is not connected to the base station.

[0010] The outline of the disclosure is a wireless communication system comprising a terminal and a base station, wherein the terminal comprises a control unit that controls communication using a lower layer with a communication device, and a receiving unit that receives from the base station configuration information for resources to be used in communication using the lower layer when not connected to the base station, and the control unit executes communication with the communication device based on the configuration information when not connected to the base station.

[0011] The outline of the disclosure is a wireless communication method comprising the steps of: controlling communication using a lower layer with a communication device; receiving configuration information for resources to be used in communication using the lower layer from a base station when not connected to the base station; and performing communication with the communication device based on the configuration information when not connected to the base station. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram showing the overall schematic configuration of a wireless communication system 10. As shown in FIG. [Figure 2] FIG. 2 shows a diagram illustrating frequency ranges used in cellular networks. [Figure 3] FIG. 3 is a diagram showing an example of the configuration of a radio frame, a subframe, and a slot used in a cellular network. [Figure 4] FIG. 4 is a functional block diagram of the UE 200. [Figure 5] FIG. 5 is a functional block diagram of the network device 50. As shown in FIG. [Figure 6] Figure 6 is a functional block diagram of gNB100. [Figure 7] FIG. 7 is a diagram for explaining Ambient IoT. [Figure 8] FIG. 8 is a diagram for explaining Ambient IoT. [Figure 9] FIG. 9 is a diagram for explaining Ambient IoT. [Figure 10] FIG. 10 is a diagram for explaining the first operation example. [Figure 11] FIG. 11 is a diagram for explaining the first operation example. [Figure 12] FIG. 12 is a diagram illustrating the second operation example. [Figure 13] FIG. 13 is a diagram illustrating the third operation example. [Figure 14]FIG. 14 is a diagram illustrating the third operation example. [Figure 15] FIG. 15 is a diagram illustrating the third operation example. [Figure 16] FIG. 16 is a diagram illustrating an example of the hardware configuration of the network device 50 and the UE 200. As shown in FIG. [Figure 17] FIG. 17 is a diagram showing an example of the configuration of a vehicle 2001. DETAILED DESCRIPTION OF THE INVENTION

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

[0014] (1) Overall configuration of wireless communication system 1 is a diagram showing an overall schematic configuration of a wireless communication system 10 according to an embodiment. The wireless communication system 10 includes a terminal 200 (hereinafter referred to as UE (User Equipment) 200), a first network 10A, and a second network 10B.

[0015] The first network 10A has a radio access network 20A and a core network 30A. The radio access network 20A includes a base station 100A that performs radio communication with the UE 200. Note that the first network 10A may not have the radio access network 20A but may have the base station 100A. The first network 10A may not have the core network 30A. The base station 100A may be configured by a DU (Distributed Unit) and a CU (Central Unit). The DU may perform processing of layers below the MAC layer. The CU may perform processing above the PDCP layer.

[0016] The first network 10A may be a network conforming to a new technology (6G). 6G may be referred to as Beyond 5G or 5G Evolution. The first network 10A may be a network conforming to an existing technology (5G). 5G may be referred to as 5G New Radio (NR).

[0017] The second network 10B has a radio access network 20B and a core network 30B. The radio access network 20B includes a base station 100B that performs radio communication with the UE 200. Note that the second network 10B may not have the radio access network 20B but may have the base station 100B. The second network 10B may not have the core network 30B. The base station 100B may be configured by a DU and a CU.

[0018] The second network 10B may be a network conforming to existing technology (5G). 5G may be referred to as 5G New Radio (NR). The second network 10B may be a network conforming to new technology (6G). 6G may be referred to as Beyond 5G or 5G Evolution.

[0019] Here, the first network 10A and the second network 10B may have different radio access schemes. For example, the radio access scheme may be a cellular network radio access scheme called 5G, Beyond 5G, 5G Evolution, 6G, or the like.

[0020] Hereinafter, the base station 100A and the base station 100B may be collectively referred to as the base station 100 or the gNB 100. The core network 30A and the core network 30B may be collectively referred to as the core network 30.

[0021] First, the cellular network may support multiple frequency ranges (FR) as shown in Figure 2. For example, as shown in Figure 2, the cellular network supports FR1, FR2-1, and FR2-2. The frequency bands of each FR are as follows:

[0022] FR1: 410 MHz to 7.125 GHz FR2-1: 24.25 GHz to 52.6 GHz ·FR2-2: More than 52.6GHz~71GHz FR1 may use a Sub-Carrier Spacing (SCS) of 15, 30, or 60 kHz, and may use 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 may use a bandwidth (BW) of 50 to 400 MHz.

[0023] Note that SCS may be interpreted as numerology, which is defined in 3GPP TS38.300 and corresponds to one subcarrier spacing in the frequency domain.

[0024] Furthermore, cellular networks may also support higher frequency bands than the FR2 frequency band, specifically, frequency bands above 52.6 GHz up to 71 GHz or 114.25 GHz.

[0025] Second, the cellular network may correspond to the radio frames, subframes and slots shown in FIG.

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

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

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

[0029] (2) Functional block configuration of wireless communication system The functional block configuration of the wireless communication system 10 will be described below.

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

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

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

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

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

[0035] The control signal / reference signal processor 240 performs 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 .

[0036] Specifically, the control signal / reference signal processor 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. The control signal / reference signal processor 240 also transmits various control signals to the gNB 100 via a predetermined control channel.

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

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

[0039] 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 position information.

[0040] 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), Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI), and a Physical Broadcast Channel (PBCH).

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

[0042] 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, Frequency Domain Resource Assignment (FDRA), Time Domain Resource Assignment (TDRA), Modulation and Coding Scheme (MCS), HARQ Process Number (HPN), New Data Indicator (NDI), Redundancy Version (RV), etc.

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

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

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

[0046] 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 HARQ (Hybrid Automatic Repeat Request).

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

[0048] In the embodiment, it may be assumed that UE 200 is a communication device (hereinafter referred to as an A-IoT device) having a simpler configuration than a general UE. The A-IoT device has lower layers such as a PHY layer and a MAC layer, and may not have upper layers such as an RLC layer, a PDCP layer, or an RRC layer.

[0049] Second, a functional block configuration of the network device 50 will be described. The network device 50 is a reader device in Ambient IoT, which will be described later, that directly communicates with a communication device (A-IoT device) having a simpler configuration than that of a general UE. For example, in Ambient IoT Topology 1, the network device 50 may be a base station (gNB100), in Ambient IoT Topology 2, the network device 50 may be an intermediate node, in Ambient IoT Topology 3, the network device 50 may be an assisting node, and in Ambient IoT Topology 4, the network device 50 may be a UE 200 (general UE). The network device 50 may be referred to as a reader device or a reader.

[0050] As shown in FIG. 5, the network device 50 includes a receiving unit 51, a transmitting unit 52, and a control unit 53.

[0051] The receiver 51 receives various signals from the A-IoT device. For example, the receiver 51 may receive an uplink signal from the A-IoT device. The uplink signal may include an uplink control signal or an uplink data signal. The uplink signal may be received via a PDRCH (Physical Device Reader Channel). A message that the reader receives from the A-IoT device may be referred to as a D2R message.

[0052] The receiver 51 may receive various signals from the gNB 100 or the core network 30.

[0053] The transmitter 52 transmits various signals to the A-IoT device. For example, the transmitter 52 may transmit a downlink signal to the A-IoT device. The downlink signal may include a downlink control signal or a downlink data signal. The downlink signal may be transmitted via a PRDCH (Physical Reader Device Channel). A message transmitted by the reader to the A-IoT device may be referred to as an R2D message.

[0054] The transmitter 52 may transmit various signals to the gNB 100 or the core network 30.

[0055] The control unit 53 controls each block that constitutes the network device 50 .

[0056] In the embodiment, a case will be mainly described in which the network device 50 is an A-IoT enabled UE that functions as an intermediate node (reader) in Topology 2, which will be described later. Therefore, the network device 50 may be read as the UE 200.

[0057] In this way, when the network device 50 (UE 200) is an A-IoT enabled UE, the control unit 53 may constitute a control unit that controls communication using a communication device (A-IoT device) and a lower layer. The receiving unit 51 may constitute a receiving unit that receives, from a base station, configuration information for resources used in communication using a lower layer (Ambient IoT) when not connected to the gNB 100 (for example, in an RRC inactive state or an RRC idle state).

[0058] Thirdly, a functional block configuration diagram of the gNB 100. As shown in Fig. 6, the gNB 100 has a receiving unit 110, a transmitting unit 120, and a control unit 130.

[0059] The receiving unit 110 receives various signals from the UE 200. The receiving unit 110 may receive an UL signal via a PUCCH or a PUSCH.

[0060] The transmitter 120 transmits various signals to the UE 200. The transmitter 120 may transmit the DL signal via the PDCCH or the PDSCH.

[0061] The control unit 130 controls each block that constitutes the gNB 100.

[0062] In the embodiment, we will mainly describe the case where gNB100 is an A-IoT enabled gNB that communicates with the Reader and functions as a BS in Topology 2 described below.

[0063] In this way, when the gNB100 is an A-IoT enabled gNB, the control unit 130 may constitute a control unit that controls communication between a communication device (A-IoT device) and a terminal (A-IoT enabled UE) that performs communication using a lower layer. The transmission unit 120 may constitute a transmission unit that transmits configuration information of resources used in communication using a lower layer (Ambient IoT) to the UE200 when not connected to the gNB100 (for example, in an RRC inactive state or an RRC idle state).

[0064] (3) Ambient IoT First, A-IoT devices may be classified into types such as Device A, Device B, and Device C.

[0065] Device A may be a device that does not have a storage for accumulating energy (for example, power) and performs backscattering transmission without performing its own signal generation / amplification or the like.

[0066] Device B may have a storage device that accumulates energy (e.g., power) and performs backscattering transmission without generating its own signal, etc. For example, the energy accumulated in the storage device may be used to amplify the reflected signal.

[0067] Device C may be a device that does not have a storage for accumulating energy (for example, power) and generates its own signal.

[0068] The A-IoT device may be a device defined in 3GPP TR38.848 V18.0.0. The A-IoT device has a simpler configuration than a typical UE. The characteristics of the A-IoT device may be defined by the following elements:

[0069] The output and complexity of A-IoT devices are simpler than those of general UEs. A-IoT device coverage will be introduced that can be achieved with a simpler configuration than general UE. Regarding the data rate of A-IoT devices, a data rate that is realized by a simpler protocol stack than that of general UE will be introduced. Regarding the maximum message size for A-IoT devices, a maximum message size that is realized by a protocol stack that is simpler than that of general UE will be introduced. The delay of A-IoT devices is set to meet the target delay using different access methods and signaling procedures than general UEs. The positioning method for the A-IoT device must be applicable to the topology described below in order to meet the required accuracy.

[0070] Regarding the connection density of A-IoT devices, multiple efficient access methods that differ from those used with general UE will be introduced. Regarding the moving speed of A-IoT devices, a different physical layer configuration will be introduced than that of general UE. Second, the topology of the A-IoT device may be as shown in Figure 7.

[0071] In Topology 1, the A-IoT device may perform UL transmission and DL reception with a base station (BS in Figure 7).

[0072] In Topology 2, an A-IoT device may perform UL transmission and DL reception with a base station (BS in Figure 7) via an intermediate node. The intermediate node may be an IAB (Integrated Access and Backhaul) node or a general UE. The intermediate node may also be a DU. A general UE may be a UE defined separately from an A-IoT device. A general UE may have a more complex configuration than an A-IoT device. In Topology 2, the BS may be referred to as an A-IoT enabled gNB, and the general UE (Intermediate node) may be referred to as an A-IoT enabled UE.

[0073] In Topology 3, the A-IoT device may perform DL reception with a base station (BS in Figure 7) and UL transmission with the base station (BS in Figure 7) via an assisting node. The intermediate node may be an IAB node or a general UE. The intermediate node may also be a DU.

[0074] In Topology 4, UL transmission and DL reception may be performed with a general UE. In Topology 4, D2D communication between a general UE and an A-IoT device may be assumed.

[0075] Note that a general UE is a term used to distinguish it from an A-IoT device, and may also be referred to as an existing UE or a normal UE.

[0076] Third, we explain the interface and protocol stack.

[0077] As shown in Figure 8, Topology 1 may include nodes such as an A-IoT device, an A-IoT RAN, and an A-IoT CN. The A-IoT RAN may be considered to be the BS shown in Figure 7, and the A-IoT CN may be considered to be an upper node of the BS shown in Figure 7. The A-IoT RAN may have a function to read information from the A-IoT device (Common reader function) and a function to communicate with the A-IoT CN (A-IoT RAN node function).

[0078] The interface between the A-IoT device and the A-IoT RAN may be referred to as the A-IoT radio interface, and the interface between the A-IoT RAN and the A-IoT CN may be referred to as the XX interface.

[0079] The A-IoT device and Common reader function may have an A-IoT Radio Protocol layer. The A-IoT Radio Protocol layer is an example of a lower layer and may be considered to be a layer equivalent to the PHY layer and MAC layer. The A-IoT RAN node function and A-IoT CN may have layers such as L1, L2, IP, SCTP (Stream Control Transmission Protocol), and XXAP (XX Application).

[0080] As shown in Figure 9, Topology 2 may include nodes such as an A-IoT device, an A-IoT enabled UE, an A-IoT enabled gNB, and an A-IoT CN. The A-IoT enabled UE may be considered to be the intermediate node shown in Figure 7, the A-IoT enabled gNB may be considered to be the BS shown in Figure 7, and the A-IoT CN may be considered to be an upper node of the BS shown in Figure 7. The A-IoT enabled UE may have the function of reading information from the A-IoT device (Common reader function), and the A-IoT enabled gNB may have the function of communicating with the A-IoT CN (A-IoT RAN node function).

[0081] The interface between the A-IoT device and the A-IoT enabled UE may be referred to as the A-IoT radio interface. The interface between the A-IoT enabled UE and the A-IoT enabled gNB may reuse the NR Uu interface, as with the interface between the UE 200 and the gNB 100. The interface between the A-IoT enabled gNB and the A-IoT CN may be referred to as the XX interface.

[0082] The protocol stacks of the A-IoT device, A-IoT enabled UE, and A-IoT enabled gNB are the same as the protocol stacks of the A-IoT device, Common reader function, and A-IoT RAN node function described in Topology 1.

[0083] (4) Issues In Ambient IoT, Topology 2 is assumed, which uses A-IoT enabled UEs that function as readers.

[0084] Against this background, the inventors conducted extensive research and discovered that there may be cases in which an A-IoT enabled UE communicates with an A-IoT device when it is not connected to an A-IoT enabled gNB (e.g., in an RRC inactive state or an RRC idle state), and that in such cases, there is a need to clarify the method for allocating resources for communication with an A-IoT device when it is not connected to an A-IoT enabled gNB.

[0085] (5) Example of operation To solve the above-mentioned problem, the A-IoT enabled UE receives configuration information for resources used in Ambient IoT when the A-IoT enabled UE is not connected to an A-IoT enabled gNB. Based on the configuration information, the A-IoT enabled UE communicates with an A-IoT device when the A-IoT enabled UE is not connected to an A-IoT enabled gNB. The following operation examples are possible.

[0086] (5.1) Example 1 In operation example 1, the gNB 100 transmits a terminal-specific message including configuration information to the UE 200 (A-IoT enabled UE). The terminal-specific message may be an RRC message, a MAC CE, or a PDCCH. For example, the terminal-specific message may be a message RRCRelease with suspend indication that instructs the release of a connection accompanied by the suspension of the connection.

[0087] The configuration information may include a configuration of UL transmission resources (D2R resources) for the A-IoT device to access the A-IoT enabled UE (Reader) in the RRC inactive state, and may include a configuration of DL transmission resources (R2D resources) for the A-IoT enabled UE (Reader) to access the A-IoT device in the RRC inactive state. The D2R resources and R2D resources may include RACH resources. For example, the RACH resources may include RACH occasions. The configuration information may be referred to as an A-IoT radio resource config.

[0088] Operation example 1 will be described below with reference to Fig. 10. In Fig. 10, the initial state of the A-IoT enabled UE may be the RRC connected state.

[0089] As shown in Figure 10, in step S10, the A-IoT enabled gNB sends an RRC Release with suspend indication to the A-IoT enabled UE. The RRC Release with suspend indication includes an A-IoT radio resource configuration. The A-IoT enabled UE releases the connection and transitions from the RRC connected state to the RRC inactive state.

[0090] In step S11, the A-IoT enabled UE sends a paging message to the A-IoT device. The paging message includes the A-IoT radio resource configuration notified in step S10. The paging message may be referred to as Msg0. The A-IoT enabled UE may perform repeated transmission of the paging message.

[0091] In step S12, the A-IoT device accesses the A-IoT enabled UE based on the A-IoT radio resource configuration notified in step S11 (step S10). Such a procedure may include 3-step (or 4-step) CBRA (Contention-Based Random Access), 2-step CBRA, or CFRA (Contention-Free Random Access). The A-IoT enabled UE may receive data from the A-IoT device.

[0092] In step S20, the A-IoT enabled UE determines whether the amount of data received from the A-IoT device (New data volume in FIG. 10) is below a threshold. In FIG. 10, the explanation continues for the case where the New data volume is below the threshold. Note that the threshold may be predefined in the wireless communication system 10 or may be included in the A-IoT radio resource config.

[0093] In step S21, the A-IoT enabled UE sends Msg1 (Random Access Preamble) to the A-IoT enabled gNB.

[0094] In step S22, the A-IoT enabled gNB sends Msg2 (Random Access Response) to the A-IoT enabled UE.

[0095] In step S23, the A-IoT enabled UE sends Msg3 (e.g., RRC Resume Request) to the A-IoT enabled gNB. The RRC Resume Request may include information requesting an A-IoT radio resource configuration. Msg3 may include data received from the A-IoT device.

[0096] In step S24, the A-IoT enabled gNB sends Msg4 (RRCRelease with suspend indication) to the A-IoT enabled UE. The RRCRelease with suspend indication includes the A-IoT radio resource config.

[0097] Although the A-IoT enabled UE executes the procedure of steps S21 to S24 (Random Access procedure), it transitions to the RRC inactive state in accordance with the RRCRelease with suspend indication.

[0098] In step S31, the A-IoT enabled UE sends a paging message to the A-IoT device. The paging message includes the A-IoT radio resource configuration notified in step S24. The paging message may be referred to as Msg0. The A-IoT enabled UE may perform repeated transmission of the paging message.

[0099] In step S32, the A-IoT device accesses the A-IoT enabled UE. Such a procedure may include 3-step (or 4-step) Contention-Based Random Access (CBRA), 2-step CBRA, or Contention-Free Random Access (CFRA). The A-IoT enabled UE may receive data from the A-IoT device.

[0100] It should be noted in Figure 10 that the A-IoT enabled UE remains in RRC inactive state from step S10 onwards.

[0101] In operation example 1, in step S20, if the new data volume exceeds a threshold, the A-IoT enabled UE may perform a transition (RRC Resume) from the RRC inactive state to the RRC connected state.

[0102] In Operation Example 1, as shown in Figure 11, the A-IoT radio resource config included in the RRCRelease may be set for each group to which the A-IoT device belongs (hereinafter referred to as A-IoT device group). For example, A-IoT resource #1-1 to #1-4 may be set for A-IoT device group #1, and A-IoT resource #2-1 to #2-4 may be set for A-IoT device group #2. The following options may be assumed for the A-IoT device group:

[0103] In Option 1-1, the A-IoT device group may be a group identified by a Group ID assigned to the A-IoT device. The Group ID is information that identifies a group of A-IoT devices. The group identified by the Group ID may be generated based on information registered in the procedure for registering the A-IoT device. The information registered in the procedure for registering the A-IoT device may include the type of A-IoT device (such as Device A, Device B, or Device C described above). In other words, the group identified by the Group ID may be generated based on the type of A-IoT device. The information registered in the procedure for registering the A-IoT device may include the purpose of the A-IoT device (e.g., inventory management, sensor data collection, tracking, actuator control, etc.). In other words, the group identified by the Group ID may be generated based on the purpose of the A-IoT device.

[0104] In Option 1-2, the A-IoT device group may be a group identified by an A-IoT enabled UE or an A-IoT enabled UE ID assigned to the A-IoT enabled UE. The A-IoT enabled UE ID is information that identifies the A-IoT enabled UE in the CN or gNB. In other words, A-IoT devices under the A-IoT enabled UE may be treated as belonging to one A-IoT device group.

[0105] (5.2) Example 2 Operation example 2 describes a modification of operation example 1. In operation example 1, a request for A-IoT radio resource config is executed in the Random Access procedure as shown in steps S21 to S24 of Fig. 10. In contrast, in operation example 2, a request for A-IoT radio resource config is executed using a Configured Grant (CG).

[0106] The following mainly describes differences from Operation Example 1. Specifically, Operation Example 2 will be described with reference to Fig. 12. In Fig. 12, the initial state of the A-IoT enabled UE may be the RRC connected state.

[0107] In Fig. 12, the same step numbers are assigned to steps that are the same as those in Fig. 10. Specifically, Fig. 12 is the same as Fig. 10 except that step S10A is executed instead of step S10 in Fig. 10, and steps S23A to S24A are executed instead of steps S21 to S24 in Fig. 10.

[0108] As shown in Figure 12, in step S10A, the A-IoT enabled gNB sends an RRCRelease with suspend indication to the A-IoT enabled UE. The RRCRelease with suspend indication includes the CG config in addition to the A-IoT radio resource config. The A-IoT enabled UE releases the connection and transitions from the RRC connected state to the RRC inactive state.

[0109] In step S23A, the A-IoT enabled UE sends an RRC Resume Request to the A-IoT enabled gNB using the CG configuration. The RRC Resume Request may include information requesting an A-IoT radio resource configuration. The A-IoT enabled UE may send data received from the A-IoT device to the A-IoT enabled gNB using the CG configuration.

[0110] In step S24A, the A-IoT enabled gNB sends an RRCRelease with suspend indication to the A-IoT enabled UE. The RRCRelease with suspend indication includes an A-IoT radio resource config.

[0111] (5.3) Example 3 Operation example 3 describes a modification of operation example 1. In operation example 1, the RRC inactive state was mainly described as a state in which the A-IoT enabled UE is not connected to the A-IoT enabled gNB. In contrast, operation example 3 also considers the RRC idle state as a state in which the A-IoT enabled UE is not connected to the A-IoT enabled gNB.

[0112] The following mainly describes differences from Operation Example 1. Specifically, Operation Example 3 will be described with reference to Fig. 13. In Fig. 13, the initial state of the A-IoT enabled UE may be the RRC idle state or the RRC inactive state.

[0113] In Fig. 13, the same steps as in Fig. 10 are assigned the same step numbers. Specifically, Fig. 13 is the same as Fig. 10 except that steps S10B to S12B are executed instead of steps S10 to S12 in Fig. 10, and step S40 is executed after step S24.

[0114] As shown in Figure 13, in step S10B, the A-IoT enabled gNB sends an SIB including an A-IoT radio resource config to the A-IoT enabled UE.

[0115] In step S11B, the A-IoT enabled UE sends a paging message to the A-IoT device. The paging message includes the A-IoT radio resource configuration notified in step S10B. The paging message may be referred to as Msg0. The A-IoT enabled UE may perform repeated transmission of the paging message.

[0116] In step S12B, the A-IoT device accesses the A-IoT enabled UE based on the A-IoT radio resource configuration notified in step S11B (step S10B). Such a procedure may include 3-step (or 4-step) Contention-Based Random Access (CBRA), 2-step CBRA, or Contention-Free Random Access (CFRA). The A-IoT enabled UE may receive data from the A-IoT device.

[0117] In step S40, the A-IoT enabled UE executes the procedure of steps S21 to S24 (Random Access procedure), but transitions to the RRC inactive state in accordance with the RRCRelease with suspend indication.

[0118] In operation example 3, as shown in Figure 14, the A-IoT radio resource config included in the SIB may be set for each group (A-IoT device group) to which the A-IoT device belongs. For example, A-IoT resource #1-1 to #1-4 may be set for A-IoT device group #1, and A-IoT resource #2-1 to #2-4 may be set for A-IoT device group #2. The A-IoT device group may be the A-IoT device group of option 1-1 described above, or the A-IoT device group of option 1-2 described above.

[0119] In operation example 3, as shown in Fig. 15, the A-IoT radio resource config included in the SIB may be set for each A-IoT enabled UE. In other words, the A-IoT radio resource config included in the SIB may be set in association with the UE ID (or Reader ID). For example, A-IoT resources #1-1 to #1-4 may be set for UE ID (Reader ID) #1, and A-IoT resources #2-1 to #2-4 may be set for UE ID (Reader ID) #2.

[0120] (6) Action and effect In an embodiment, an A-IoT enabled UE receives configuration information (A-IoT radio resource config) for resources used in Ambient IoT in the RRC inactive state, and communicates with the A-IoT device in the RRC inactive state based on the configuration information (A-IoT radio resource config) (Operation Examples 1 to 3). With this configuration, notification of the configuration information (A-IoT radio resource config) allows appropriate allocation of resources for communication with the A-IoT device in the inactive state.

[0121] In an embodiment, the A-IoT enabled UE receives configuration information (A-IoT radio resource config) for resources used in Ambient IoT in the RRC idle state, and communicates with the A-IoT device in the RRC idle state based on the configuration information (A-IoT radio resource config) (Operation Example 3). With this configuration, notification of the configuration information (A-IoT radio resource config) allows appropriate allocation of resources for communication with the A-IoT device in the Inactive state.

[0122] (7) Other embodiments The present invention has been described above in accordance with the embodiments, but it will be obvious to those skilled in the art that the present invention is not limited to these descriptions and that various modifications and improvements are possible.

[0123] Although not particularly mentioned in the above disclosure, which of Operational Examples 1 to 3 to use (which aspect to use) may be set by a higher layer parameter. Which of each option of Operational Examples 1 to 3 to use may be set by a higher layer parameter. Which aspect to support may be reported from UE 200 as UE capability(ies). Which aspect to use may be defined in advance in wireless communication system 10. Which aspect to use may be set by a higher layer parameter and reported from UE 200 as UE capability(ies).

[0124] Although not specifically mentioned in the above disclosure, the following UE capability(ies) may be defined. UE capability(ies) may be defined for each A-IoT device, for each FR (e.g., FR1, FR2, FR2-1, FR2-2, FR3), for each SCS, for each band, for each Bandwidth Combination (BC), or for each Frequency Combination (FC). UE capability(ies) may be included in a signal reported from the UE 200 to the gNB 100, or may be included in a signal configured by the gNB 100 to the UE 200.

[0125] The block diagrams (FIGS. 4 and 5) used in the description of the above-described embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (for example, by wire, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining the single device or the multiple devices with software.

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

[0127] Furthermore, the above-described network device 50, gNB 100, and UE 200 (the devices) may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 16 is a diagram showing an example of the hardware configuration of the devices. As shown in Fig. 16, 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.

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

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

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

[0131] 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, a register, and the like.

[0132] 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-mentioned embodiments. Furthermore, the various processes described above may be executed by one processor 1001, or may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0133] The memory 1002 is a computer-readable recording medium and may be configured by, for example, at least one of 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 can store a program (program code), a software module, etc., that can execute a method according to an embodiment of the present disclosure.

[0134] 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 appropriate medium including at least one of memory 1002 and storage 1003.

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

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

[0137] The input device 1005 is an input device (for example, 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 (for example, a display, a speaker, an LED lamp, etc.) that performs output to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

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

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

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

[0141] 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), 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 and 5G) may also be applied.

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

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

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

[0145] The input and output information may be stored in a specific location (for example, 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 sent to another device.

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

[0147] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

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

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

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

[0151] Note that terms explained 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.

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

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

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

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

[0156] 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 service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

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

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

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

[0160] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). 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.

[0161] 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 communication between terminals (for example, "side"). For example, terms such as uplink channel and downlink channel may be read as side channel.

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

[0163] A radio frame may be composed of one or more frames in the time domain, each of which may be called a subframe.

[0164] A subframe may further be composed of one or more slots in the time domain, and may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0165] Numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by a transceiver in the frequency domain, and specific windowing operations performed by a transceiver in the time domain.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0182] 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 changed in various ways.

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

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

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

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

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

[0188] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.

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

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

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

[0192] Fig. 17 shows an example of the configuration of a vehicle 2001. As shown in Fig. 17, 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.

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

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

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

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

[0197] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing various types of information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information obtained 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.

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

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

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

[0201] The communication module 2013 transmits, via wireless communication to an external device, a current signal from the current sensor that is input to the electronic control unit 2010. The communication module 2013 also transmits, via wireless communication to an external device, the rotation speed signals of the front and rear wheels acquired by a rotation speed sensor 2022, the air pressure signals of the front and rear wheels acquired by an air pressure sensor 2023, the vehicle speed signal acquired by a vehicle speed sensor 2024, the acceleration signal acquired by an acceleration sensor 2025, the accelerator pedal depression amount signal acquired by an accelerator pedal sensor 2029, the brake pedal depression amount signal acquired by a brake pedal sensor 2026, the shift lever operation signal acquired by a shift lever sensor 2027, and the detection signals for detecting obstacles, vehicles, pedestrians, etc. acquired by an object detection sensor 2028, all of which are input to the electronic control unit 2010.

[0202] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle. The communication module 2013 also stores the various information received from the external 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 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, sensors 2021 to 2028, and the like provided in the vehicle 2001.

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

[0204] (Addendum) The above disclosure may be expressed as follows:

[0205] A first feature is that the terminal comprises a control unit that controls communication using a lower layer with a communication device, and a receiving unit that receives, from a base station, configuration information for resources to be used in communication using the lower layer when not connected to a base station, and the control unit communicates with the communication device based on the configuration information when not connected to the base station.

[0206] A second feature is the terminal according to the first feature, wherein the setting information is included in a message individual to the terminal.

[0207] A third feature is the terminal according to the first feature, wherein the setting information is included in broadcast information.

[0208] A fourth feature is a base station including: a control unit that controls communication between a communication device and a terminal that performs communication using a lower layer; and a transmission unit that transmits configuration information for resources used in communication using the lower layer to the terminal when the terminal is not connected to the base station.

[0209] A fifth feature is a wireless communication system including a terminal and a base station, wherein the terminal includes a control unit that controls communication using a lower layer with a communication device, and a receiving unit that receives, from the base station, configuration information of resources to be used in communication using the lower layer when not connected to the base station, and the control unit performs communication with the communication device based on the configuration information when not connected to the base station.

[0210] A sixth feature is a wireless communication method including: a step of controlling communication using a lower layer with a communication device; a step of receiving, from a base station, configuration information of resources to be used in communication using the lower layer when not connected to the base station; and a step of performing communication with the communication device based on the configuration information when not connected to the base station. [Explanation of symbols]

[0211] 10. Wireless communication systems 10A Network 1 10B Second Network 20A, 20B Wireless Access Network 30A, 30B Core Network 50 Network Equipment 51 Receiving unit 52 Transmitter 53 Control Unit 100A,100B base station 110 Receiving unit 120 Transmitter 130 Control Unit 200 UE 210 Radio signal transmitter / receiver 220 Amplifier section 230 Modulation and Demodulation Unit 240 Control signal / reference signal processing section 250 Encoding / Decoding Unit 260 Data transmission and reception unit 270 Control Unit 1001 processor 1002 memory 1003 Storage 1004 Communication equipment 1005 Input Device 1006 Output Device 1007 Bus 2001 Vehicle 2002 Drive unit 2003 Steering section 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 Services Department 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 Systems Department 2031 microprocessor 2032 memory (ROM, RAM) 2033 communication port

Claims

1. a control unit that controls communication using the communication device and a lower layer; a receiving unit that receives, from a base station, configuration information of resources to be used in communication using the lower layer when not connected to the base station; The control unit executes communication with the communication device based on the setting information in a state where the terminal is not connected to the base station.

2. The terminal of claim 1 , wherein the configuration information is included in a message specific to the terminal.

3. The terminal according to claim 1 , wherein the setting information is included in broadcast information.

4. a control unit that controls communication between the communication device and a terminal that executes communication using a lower layer; a transmitting unit that transmits, to the terminal, configuration information of resources to be used in communication using the lower layer when the terminal is not connected to the base station.

5. A terminal and a base station, The terminal a control unit that controls communication using the communication device and a lower layer; a receiving unit that receives, from the base station, configuration information of resources to be used in communication using the lower layer in a state where the base station is not connected to the base station, The control unit executes communication with the communication device based on the setting information when not connected to the base station.

6. controlling communication using the communication device and the lower layer; receiving, from a base station, configuration information for resources to be used in communication using the lower layer while not connected to the base station; and executing communication with the communication device based on the setting information while not connected to the base station.