WO2024171988A1 - 通信システム - Google Patents

通信システム Download PDF

Info

Publication number
WO2024171988A1
WO2024171988A1 PCT/JP2024/004618 JP2024004618W WO2024171988A1 WO 2024171988 A1 WO2024171988 A1 WO 2024171988A1 JP 2024004618 W JP2024004618 W JP 2024004618W WO 2024171988 A1 WO2024171988 A1 WO 2024171988A1
Authority
WO
WIPO (PCT)
Prior art keywords
communication
base station
information
unit
signaling
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2024/004618
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
忠宏 下田
満 望月
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Mitsubishi Electric Corp
Original Assignee
Mitsubishi Electric Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Mitsubishi Electric Corp filed Critical Mitsubishi Electric Corp
Priority to EP24756833.0A priority Critical patent/EP4668992A1/en
Priority to JP2025501130A priority patent/JPWO2024171988A1/ja
Priority to CN202480010628.1A priority patent/CN120642546A/zh
Publication of WO2024171988A1 publication Critical patent/WO2024171988A1/ja
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/40—Resource management for direct mode communication, e.g. D2D or sidelink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/18—TPC being performed according to specific parameters
    • H04W52/24—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters
    • H04W52/246—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters where the output power of a terminal is based on a path parameter calculated in said terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/18—TPC being performed according to specific parameters
    • H04W52/24—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters
    • H04W52/247—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters where the output power of a terminal is based on a path parameter sent by another terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/38—TPC being performed in particular situations
    • H04W52/383—TPC being performed in particular situations power control in peer-to-peer links
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • This disclosure relates to wireless communication technology.
  • 5G fifth-generation
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution Advanced
  • NR New Radio Access Technology
  • the NR system is being considered based on the LTE system and the LTE-A system.
  • Non-Patent Document 3 For example, in Europe, an organization called METIS has compiled 5G requirements (see Non-Patent Document 3).
  • the requirements for a 5G wireless access system are that it will have 1,000 times the system capacity, 100 times the data transmission speed, one-fifth (1/5) the data processing delay, and 100 times the number of simultaneous connections of communication terminals compared to an LTE system, while also achieving further reductions in power consumption and lower costs for the equipment (see Non-Patent Document 3).
  • NR's access method will be OFDM (Orthogonal Frequency Division Multiplexing) in the downlink direction, and OFDM and DFT-s-OFDM (Discrete Fourier Transform-spread-OFDM) in the uplink direction. Also, like LTE and LTE-A, the 5G system will not include circuit switching and will only use packet communication methods.
  • OFDM Orthogonal Frequency Division Multiplexing
  • DFT-s-OFDM Discrete Fourier Transform-spread-OFDM
  • NR is capable of using higher frequencies than LTE in order to improve transmission speeds and reduce processing delays.
  • NR which may use higher frequencies than LTE, ensures cell coverage by forming a narrow beam-like transmission and reception range (beamforming) and changing the direction of the beam (beam sweeping).
  • Figure 1 is an explanatory diagram showing the configuration of a radio frame used in an NR communication system.
  • one radio frame is 10 ms.
  • the radio frame is divided into 10 equally sized subframes.
  • one or more numerologies i.e., one or more subcarrier spacings (SCS)
  • SCS subcarrier spacings
  • one subframe is 1 ms regardless of the subcarrier spacing, and one slot is composed of 14 symbols.
  • the number of slots included in one subframe is one when the subcarrier spacing is 15 kHz, and the number of slots at other subcarrier spacings increases in proportion to the subcarrier spacing (see Non-Patent Document 11 (3GPP TS38.211)).
  • Non-Patent Document 2 (Chapter 5) and Non-Patent Document 11.
  • the Physical Broadcast Channel is a channel for downlink transmission from a base station device (hereinafter sometimes simply referred to as a "base station”) to a communication terminal device (hereinafter sometimes referred to as a “communication terminal” or “terminal”) such as a mobile terminal device (hereinafter sometimes simply referred to as a “mobile terminal”).
  • the PBCH is transmitted together with a downlink synchronization signal.
  • Downstream synchronization signals in NR include a primary synchronization signal (P-SS) and a secondary synchronization signal (S-SS).
  • Synchronization signals are transmitted from base stations as synchronization signal bursts (hereinafter sometimes referred to as SS bursts) at a specified cycle and for a specified duration.
  • SS bursts are composed of synchronization signal blocks (hereinafter sometimes referred to as SS blocks) for each beam of the base station.
  • the base station transmits the SS blocks of each beam by changing the beam during the duration of the SS burst.
  • the SS block is composed of P-SS, S-SS, and PBCH.
  • the Physical Downlink Control Channel is a channel for downlink transmission from a base station to a communication terminal.
  • the PDCCH carries downlink control information (DCI).
  • the DCI includes resource allocation information for the Downlink Shared Channel (DL-SCH), which is one of the transport channels described below, resource allocation information for the Paging Channel (PCH), which is one of the transport channels described below, and HARQ (Hybrid Automatic Repeat reQuest) information for the DL-SCH.
  • the DCI may also include an uplink scheduling grant.
  • the DCI may also include an Ack (Acknowledgement)/Nack (Negative Acknowledgement), which is a response signal to the uplink transmission.
  • the DCI may include a slot format indication (SFI).
  • SFI slot format indication
  • the PDCCH or DCI is also called an L1/L2 control signal.
  • a time-frequency region is provided that is a candidate for including PDCCH. This region is called the control resource set (CORESET).
  • the communication terminal monitors the CORESET and acquires the PDCCH.
  • the Physical Downlink Shared Channel is a channel for downlink transmission from a base station to a communication terminal.
  • the PDSCH is mapped to the Downlink Shared Channel (DL-SCH), which is a transport channel, and the PCH, which is a transport channel.
  • DL-SCH Downlink Shared Channel
  • PCH which is a transport channel
  • the Physical Uplink Control Channel is a channel for uplink transmission from a communication terminal to a base station.
  • the PUCCH carries uplink control information (UCI).
  • the UCI includes Ack/Nack, which is a response signal for downlink transmission, CSI (Channel State Information), and Scheduling Request (SR).
  • CSI is composed of RI (Rank Indicator), PMI (Precoding Matrix Indicator), and CQI (Channel Quality Indicator) reports.
  • RI is rank information of the channel matrix in MIMO (Multiple Input Multiple Output).
  • PMI is information of the precoding weight matrix used in MIMO.
  • CQI is quality information that indicates the quality of received data or the quality of the communication path.
  • UCI may be carried by the PUSCH, which will be described later.
  • PUCCH or UCI is also called an L1/L2 control signal.
  • the Physical Uplink Shared Channel (PUSCH) is a channel for uplink transmission from a communication terminal to a base station.
  • the Uplink Shared Channel (UL-SCH) which is one of the transport channels, is mapped to the PUSCH.
  • the Physical Random Access Channel is a channel for uplink transmission from a communication terminal to a base station.
  • the PRACH carries a random access preamble.
  • the downlink reference signal is a known symbol in an NR communication system.
  • the following four types of downlink reference signals are defined: UE-specific reference signals, namely, the Demodulation Reference Signal (DM-RS), the Phase Tracking Reference Signal (PT-RS), the Positioning Reference Signal (PRS), and the Channel State Information Reference Signal (CSI-RS).
  • Measurements of the physical layer of the communication terminal include the Reference Signal Received Power (RSRP) measurement of the reference signal and the Reference Signal Received Quality (RSRQ) measurement of the reference signal.
  • RSRP Reference Signal Received Power
  • RSRQ Reference Signal Received Quality
  • the uplink reference signal is also a known symbol in an NR communication system.
  • Three types of uplink reference signals are defined: Data demodulation reference signal (DM-RS), phase tracking reference signal (PT-RS), and sounding reference signal (SRS).
  • DM-RS Data demodulation reference signal
  • PT-RS phase tracking reference signal
  • SRS sounding reference signal
  • Non-Patent Document 2 The following describes the transport channels described in Non-Patent Document 2 (Chapter 5).
  • the broadcast channel (BCH) is broadcast to the entire coverage of the base station (cell).
  • the BCH is mapped to the physical broadcast channel (PBCH).
  • PBCH physical broadcast channel
  • HARQ retransmission control is applied to the downlink shared channel (DL-SCH).
  • DL-SCH can be notified to the entire coverage of the base station (cell).
  • DL-SCH supports dynamic or semi-static resource allocation. Semi-static resource allocation is also called semi-persistent scheduling.
  • DL-SCH supports discontinuous reception (DRX) of communication terminals to reduce power consumption of communication terminals.
  • DL-SCH is mapped to the physical downlink shared channel (PDSCH).
  • the Paging Channel supports DRX in communication terminals to enable low power consumption in the communication terminals.
  • the PCH is required to notify the entire coverage of the base station (cell).
  • the PCH is dynamically mapped to physical resources such as the Physical Downlink Shared Channel (PDSCH) that can be used for traffic.
  • PDSCH Physical Downlink Shared Channel
  • the uplink shared channel (UL-SCH) is subject to retransmission control using HARQ.
  • the UL-SCH supports dynamic or semi-static resource allocation. Semi-static resource allocation is also called configured grant.
  • the UL-SCH is mapped to the physical uplink shared channel (PUSCH).
  • the Random Access Channel is limited to control information. There is a risk of collisions on the RACH.
  • the RACH is mapped to the Physical Random Access Channel (PRACH).
  • PRACH Physical Random Access Channel
  • HARQ is a technology that improves the communication quality of a transmission path by combining Automatic Repeat reQuest (ARQ) and Forward Error Correction.
  • ARQ Automatic Repeat reQuest
  • HARQ has the advantage that error correction works effectively by retransmission even for transmission paths where the communication quality changes. In particular, it is possible to obtain further quality improvement by combining the reception results of the initial transmission and the retransmission when retransmitting.
  • a CRC error occurs on the receiving side
  • the receiving side requests a retransmission to the transmitting side.
  • the retransmission request is made by toggling the NDI (New Data Indicator).
  • the transmitting side that receives the retransmission request retransmits the data. If no CRC error occurs on the receiving side, no retransmission request is made. If the transmitting side does not receive a retransmission request for a specified period of time, it assumes that no CRC error occurred on the receiving side.
  • the Broadcast Control Channel is a downlink channel for broadcasting system control information.
  • the logical channel BCCH is mapped to the broadcast channel (BCH), which is a transport channel, or the downlink shared channel (DL-SCH).
  • the Paging Control Channel is a downlink channel for transmitting paging information and changes to system information.
  • the PCCH which is a logical channel, is mapped to the Paging Channel (PCH), which is a transport channel.
  • the Common Control Channel is a channel for transmitting control information between a communication terminal and a base station.
  • the CCCH is used when the communication terminal does not have an RRC connection with the network.
  • the CCCH is mapped to the downlink shared channel (DL-SCH), which is a transport channel.
  • the CCCH is mapped to the uplink shared channel (UL-SCH), which is a transport channel.
  • the Dedicated Control Channel is a channel that transmits dedicated control information between a communication terminal and a network on a one-to-one basis.
  • the DCCH is used when the communication terminal has an RRC connection with the network.
  • the DCCH is mapped to the uplink shared channel (UL-SCH) in the uplink and to the downlink shared channel (DL-SCH) in the downlink.
  • the Dedicated Traffic Channel is a one-to-one communication channel to a communication terminal for transmitting user information.
  • DTCH exists for both uplink and downlink.
  • DTCH is mapped to the uplink shared channel (UL-SCH), and in the downlink, it is mapped to the downlink shared channel (DL-SCH).
  • UL-SCH uplink shared channel
  • DL-SCH downlink shared channel
  • the location of a communication terminal is tracked in units of an area consisting of one or more cells. Location tracking is performed in order to track the location of the communication terminal even when it is in standby mode and to enable the communication terminal to be called, in other words, to allow the communication terminal to receive calls.
  • the area for tracking the location of this communication terminal is called a Tracking Area (TA).
  • TA Tracking Area
  • NR supports calling of communication terminals in a range that is smaller than a tracking area. This range is called the RAN Notification Area (RNA). Paging of communication terminals in the RRC_INACTIVE state, as described below, is performed within this range.
  • RNA RAN Notification Area
  • CA carrier aggregation
  • CCs component carriers
  • transmission bandwidths transmission bandwidths
  • a communication terminal UE When CA is configured, a communication terminal UE has only one RRC connection with the network (NW).
  • one serving cell provides NAS (Non-Access Stratum) mobility information and security input.
  • This cell is called a Primary Cell (PCell).
  • a Secondary Cell (SCell) is configured to form a set of serving cells together with the PCell.
  • a set of serving cells consisting of one PCell and one or more SCells is configured for one UE.
  • DC Dual Connectivity
  • the serving cells configured by the master base station may be collectively called the Master Cell Group (MCG), and the serving cells configured by the secondary base station may be collectively called the Secondary Cell Group (SCG).
  • MCG Master Cell Group
  • SCG Secondary Cell Group
  • the primary cell in the MCG or SCG is called a special cell (Special Cell: SpCell or SPCell).
  • the special cell in the MCG is called the PCell, and the special cell in the SCG is called the primary SCG cell (PSCell).
  • the base station pre-configures a portion of the carrier frequency band (hereinafter sometimes referred to as the Bandwidth Part (BWP)) for the UE, and the UE transmits and receives data to and from the base station using that BWP, thereby reducing power consumption in the UE.
  • BWP Bandwidth Part
  • SL communication also called PC5 communication
  • EPS Evolved Packet System
  • 5G core system 5G core system
  • SL communication communication is performed between terminals.
  • Services using SL communication include, for example, V2X (Vehicle-to-everything) service and proximity service.
  • V2X Vehicle-to-everything
  • SL communication not only direct communication between terminals but also communication between UE and NW via a relay has been proposed (see non-patent documents 26 and 28).
  • the physical sidelink broadcast channel (PSBCH) carries information related to the system and synchronization and is transmitted from the UE.
  • the physical sidelink control channel (PSCCH) carries control information from the UE for sidelink and V2X sidelink communications.
  • the physical sidelink shared channel (PSSCH) carries data from the UE for sidelink and V2X sidelink communications.
  • the physical sidelink feedback channel (PSFCH) carries HARQ feedback on the sidelink from a UE that receives a PSSCH transmission to the UE that transmitted the PSSCH.
  • the transport channel used for SL (see Non-Patent Document 1) is explained below.
  • the sidelink broadcast channel (SL-BCH) has a predetermined transport format and is mapped to the PSBCH, which is a physical channel.
  • the sidelink shared channel supports broadcast transmissions.
  • the SL-SCH supports both UE autonomous resource selection and base station scheduled resource allocation. There is a collision risk with UE autonomous resource selection, and there is no collision when the UE is allocated individual resources by the base station.
  • the SL-SCH also supports dynamic link adaptation by changing the transmission power, modulation, and coding.
  • the SL-SCH is mapped to the PSSCH, which is a physical channel.
  • the Sidelink Broadcast Control Channel is a channel for sidelink that is used to broadcast sidelink system information from one UE to other UEs.
  • the SBCCH is mapped to the SL-BCH, which is a transport channel.
  • the Sidelink Traffic Channel is a one-to-many sidelink traffic channel for transmitting user information from one UE to other UEs.
  • STCH is used only by UEs with sidelink communication capability and UEs with V2X sidelink communication capability.
  • One-to-one communication between two sidelink communication capable UEs is also realized by STCH.
  • STCH is mapped to the SL-SCH, which is a transport channel.
  • the Sidelink Control Channel is a sidelink control channel for transmitting control information from one UE to another.
  • the SCCH is mapped to the SL-SCH, which is a transport channel.
  • Unicast and groupcast communication in SL supports HARQ feedback (Ack/Nack), CSI reporting, etc.
  • 3GPP is also considering integrated access and backhaul (IAB), which would wirelessly perform both the access link between UE and base station, and the backhaul link between base stations (see non-patent documents 2, 20, and 29).
  • IAB integrated access and backhaul
  • one of the objectives of this disclosure is to realize a communications system that enables communication with ultra-low power consumption IoT devices.
  • the communication system disclosed herein includes a base station compatible with a fifth-generation wireless access system, a communication terminal connected to the base station, and a device connected to the base station or the communication terminal, and is characterized in that the base station schedules communications between the device and the base station and between the device and the communication terminal, and the device communicates with the base station or the communication terminal in accordance with the scheduling results by the base station.
  • This disclosure makes it possible to realize a communications system that enables communication with ultra-low power consumption IoT devices.
  • FIG. 1 is a block diagram showing the overall configuration of an NR communication system 210 being discussed in 3GPP. This is a configuration diagram of DC by a base station connecting to an NG core.
  • FIG. 3 is a block diagram showing the configuration of a mobile terminal 202 shown in FIG. 2.
  • 3 is a block diagram showing a configuration of a base station 213 shown in FIG. 2.
  • a block diagram showing the configuration of the 5GC unit. 1 is a flowchart showing an outline of the process from cell search to standby operation performed by a communication terminal (UE) in an NR communication system.
  • UE communication terminal
  • FIG. 2 is a connection configuration diagram showing an example of a connection configuration of terminals in SL communication.
  • FIG. 11 is a sequence diagram illustrating an example of a scheduling operation from a base station to a UE regarding communication between the UE and a device according to the first embodiment.
  • FIG. 11 is a sequence diagram illustrating a first alternative example of a scheduling operation from a base station to a UE regarding communication between the UE and a device in accordance with the first embodiment.
  • FIG. 11 is a sequence diagram illustrating a second alternative example of a scheduling operation from a base station to a UE regarding communication between the UE and a device in accordance with the first embodiment.
  • FIG. 13 is a diagram illustrating an example of a protocol stack between a UE and a base station for communication between the UE and a device according to a fifth embodiment.
  • FIG. 11 is a diagram showing another example of a protocol stack between a UE and a base station relating to communication between the UE and a device, for the fifth embodiment.
  • FIG. 2 is a block diagram showing the overall configuration of a NR communication system 210 being discussed in 3GPP.
  • the radio access network is called NG-RAN (Next Generation Radio Access Network) 211.
  • a mobile terminal device hereinafter referred to as “mobile terminal (User Equipment: UE)"
  • UE User Equipment
  • UE base station
  • NG-RAN NodeB gNB
  • the NG-RAN 211 is composed of one or more NR base stations 213.
  • “communication terminal device” includes not only mobile terminal devices such as mobile mobile phone terminal devices, but also stationary devices such as sensors.
  • “communication terminal device” may be simply referred to as “communication terminal.”
  • the AS (Access Stratum) protocol is terminated between UE 202 and NG-RAN 211.
  • AS protocols include RRC (Radio Resource Control), SDAP (Service Data Adaptation Protocol), PDCP (Packet Data Convergence Protocol), RLC (Radio Link Control), MAC (Medium Access Control), and PHY (Physical layer).
  • RRC Radio Resource Control
  • SDAP Service Data Adaptation Protocol
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • PHY Physical layer
  • RRC Radio Resource Control
  • SDAP Service Data Adaptation Protocol
  • SDAP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • PHY Physical layer
  • the control protocol RRC Radio Resource Control
  • RRC Radio Resource Control
  • the states of the NR base station 213 and the UE 202 in RRC include RRC_IDLE, RRC_CONNECTED, and RRC_INACTIVE.
  • RRC_IDLE PLMN (Public Land Mobile Network) selection, system information (SI) notification, paging, cell re-selection, mobility, etc. are performed.
  • RRC_CONNECTED the mobile terminal has an RRC connection and can transmit and receive data with the network.
  • RRC_CONNECTED handover (HO) and neighbor cell measurement are performed.
  • RRC_INACTIVE the connection between the 5G core unit 214 and the NR base station 213 is maintained, and system information (SI) notification, paging, cell re-selection, mobility, etc. are performed.
  • the gNB213 is connected to a 5G core unit (hereinafter sometimes referred to as a "5GC unit") 214 including an access and mobility management function (AMF), a session management function (SMF), or a user plane function (UPF) via an NG interface.
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane function
  • Control information and/or user data is communicated between the gNB213 and the 5GC unit 214.
  • the NG interface is a collective term for the N2 interface between the gNB213 and the AMF220, the N3 interface between the gNB213 and the UPF221, the N11 interface between the AMF220 and the SMF222, and the N4 interface between the UPF221 and the SMF222.
  • Multiple 5GC units 214 may be connected to one gNB213.
  • gNB213 are connected via the Xn interface, and control information and/or user data are communicated between gNB213.
  • the 5GC unit 214 is an upper device, specifically an upper node, and controls the connection between the NR base station 213 and the mobile terminal (UE) 202, distributes paging signals to one or more NR base stations (gNB) 213 and/or LTE base stations (E-UTRAN NodeB: eNB), etc.
  • the 5GC unit 214 also performs mobility control in the idle state.
  • the 5GC unit 214 manages the tracking area list when the mobile terminal 202 is in the idle state, in the inactive state, and in the active state.
  • the 5GC unit 214 initiates the paging protocol by transmitting a paging message to a cell belonging to the tracking area in which the mobile terminal 202 is registered.
  • gNB213 may configure one or more cells. When one gNB213 configures multiple cells, each cell is configured to be capable of communicating with UE202.
  • the gNB 213 may be divided into a central unit (hereinafter sometimes referred to as CU) 215 and a distributed unit (hereinafter sometimes referred to as DU) 216.
  • CU central unit
  • DU distributed unit
  • One CU 215 is configured within the gNB 213.
  • One or more DUs 216 are configured within the gNB 213.
  • One DU 216 configures one or more cells.
  • the CU 215 is connected to the DU 216 via an F1 interface, and control information and/or user data are communicated between the CU 215 and the DU 216.
  • the F1 interface is composed of an F1-C interface and an F1-U interface.
  • the CU 215 is responsible for the functions of the RRC, SDAP, and PDCP protocols, and the DU 216 is responsible for the functions of the RLC, MAC, and PHY protocols.
  • One or more TRPs (Transmission Reception Points) 219 may be connected to the DU 216.
  • the TRPs 219 transmit and receive radio signals to and from the UE.
  • the CU 215 may be divided into a CU for C-plane (CU-C) 217 and a CU for U-plane (CU-U) 218.
  • One CU-C 217 is configured within the CU 215.
  • One or more CU-Us 218 are configured within the CU 215.
  • the CU-C 217 is connected to the CU-U 218 via an E1 interface, and control information is communicated between the CU-C 217 and the CU-U 218.
  • the CU-C 217 is connected to the DU 216 via an F1-C interface, and control information is communicated between the CU-C 217 and the DU 216.
  • the CU-U 218 is connected to the DU 216 via an F1-U interface, and user data is communicated between the CU-U 218 and the DU 216.
  • a 5G communication system may include a Unified Data Management (UDM) function and a Policy Control Function (PCF) described in Non-Patent Document 10 (3GPP TS23.501).
  • the UDM and/or PCF may be included in the 5GC unit 214 in FIG. 2.
  • a location management function described in non-patent document 24 (3GPP TS 38.305) may be provided.
  • the LMF may be connected to the base station via the AMF as disclosed in non-patent document 25 (3GPP TS 23.273).
  • a 5G communication system may include a Non-3GPP Interworking Function (N3IWF) described in Non-Patent Document 10 (3GPP TS23.501).
  • the N3IWF may terminate the Access Network (AN) between the UE and the UE in non-3GPP access between the UE and the N3IWF.
  • AN Access Network
  • Figure 3 shows the configuration of DC (dual connectivity) connected to the NG core.
  • the master base station 240-1 may be a gNB or an eNB.
  • the secondary base station 240-2 may be a gNB or an eNB.
  • NG-EN-DC a DC configuration in which the master base station 240-1 is a gNB and the secondary base station 240-2 is an eNB.
  • FIG. 3 an example is shown in which the U-Plane connection between the 5GC unit 214 and the secondary base station 240-2 is made via the master base station 240-1, but it may also be made directly between the 5GC unit 214 and the secondary base station 240-2. Also, in FIG. 3, instead of the 5GC unit 214, an EPC (Evolved Packet Core), which is a core network connected to the LTE system and the LTE-A system, may be connected to the master base station 240-1. A U-Plane connection may be made directly between the EPC and the secondary base station 240-2.
  • EPC Evolved Packet Core
  • FIG. 4 is a block diagram showing the configuration of the mobile terminal 202 shown in FIG. 2.
  • the transmission process of the mobile terminal 202 shown in FIG. 4 will be described.
  • the control data from the control unit 310 and the user data from the application unit 302 are sent to the protocol processing unit 301. Buffering of the control data and the user data may be performed. Buffers for the control data and the user data may be provided in the control unit 310, the application unit 302, or the protocol processing unit 301.
  • the protocol processing unit 301 performs protocol processing such as SDAP, PDCP, RLC, MAC, etc., for example, determining the destination base station in DC, etc., and adding a header in each protocol.
  • the data that has been subjected to the protocol processing is passed to the encoder unit 304, where it is subjected to encoding processing such as error correction.
  • the data that has been encoded by the encoder unit 304 is modulated by the modulation unit 305. Precoding in MIMO may be performed by the modulation unit 305.
  • the modulated data is converted into a baseband signal, and then output to frequency conversion section 306, where it is converted into a radio transmission frequency. Then, the transmission signal is transmitted from antennas 307-1 to 307-4 to base station 213.
  • FIG. 4 an example in which the number of antennas is four is shown, but the number of antennas is not limited to four.
  • the reception process of the mobile terminal 202 is executed as follows. Radio signals from the base station 213 are received by the antennas 307-1 to 307-4. The received signals are converted from the radio reception frequency to a baseband signal by the frequency conversion unit 306, and demodulation process is performed by the demodulation unit 308. Weight calculation and multiplication process may also be performed by the demodulation unit 308.
  • the demodulated data is passed to the decoder unit 309, where decoding process such as error correction is performed.
  • the decoded data is passed to the protocol processing unit 301, where protocol processing such as MAC, RLC, PDCP, SDAP, etc. is performed, for example, operations such as removing the header in each protocol are performed.
  • protocol processing such as MAC, RLC, PDCP, SDAP, etc. is performed, for example, operations such as removing the header in each protocol are performed.
  • the control data is passed to the control unit 310, and the user data is passed to the application unit 302.
  • control unit 310 The series of processes of the mobile terminal 202 are controlled by the control unit 310. Therefore, although the control unit 310 is omitted in FIG. 4, it is also connected to each of the units 302, 304 to 309.
  • Each part of the mobile terminal 202 is realized by a processing circuit including, for example, a processor and a memory.
  • the control unit 310 is realized by a processor executing a program in which a series of processes of the mobile terminal 202 are described.
  • the program in which a series of processes of the mobile terminal 202 are described is stored in a memory. Examples of memory are non-volatile or volatile semiconductor memories such as RAM (Random Access Memory), ROM (Read Only Memory), and flash memory.
  • Each part of the mobile terminal 202 may be realized by a dedicated processing circuit such as an FPGA (Field Programmable Gate Array), an ASIC (Application Specific Integrated Circuit), or a DSP (Digital Signal Processor).
  • a dedicated processing circuit such as an FPGA (Field Programmable Gate Array), an ASIC (Application Specific Integrated Circuit), or a DSP (Digital Signal Processor).
  • FPGA Field Programmable Gate Array
  • ASIC Application Specific Integrated Circuit
  • DSP Digital Signal Processor
  • FIG. 5 is a block diagram showing the configuration of the base station 213 shown in Figure 2. The transmission process of the base station 213 shown in Figure 5 will be described.
  • the EPC communication unit 401 transmits and receives data between the base station 213 and the EPC.
  • the 5GC communication unit 412 transmits and receives data between the base station 213 and the 5GC (such as the 5GC unit 214).
  • the other base station communication unit 402 transmits and receives data with other base stations.
  • the EPC communication unit 401, the 5GC communication unit 412, and the other base station communication unit 402 each exchange information with the protocol processing unit 403.
  • Control data from the control unit 411, and user data and control data from the EPC communication unit 401, the 5GC communication unit 412, and the other base station communication unit 402 are sent to the protocol processing unit 403. Buffering of the control data and user data may be performed. Buffers for control data and user data may be provided in the control unit 411, in the EPC communication unit 401, in the 5GC communication unit 412, or in the other base station communication unit 402.
  • the protocol processing unit 403 performs protocol processing such as SDAP, PDCP, RLC, MAC, etc., for example, routing of transmission data in DC, etc., and adding headers in each protocol.
  • the data that has been subjected to protocol processing is passed to the encoder unit 405, where encoding processing such as error correction is performed.
  • Data may also be sent from the protocol processing unit 403 to the other base station communication unit 402.
  • DC data sent from the 5GC communication unit 412 or the EPC communication unit 401 may be sent to another base station, for example, a secondary base station, via the other base station communication unit 402.
  • the encoded data is modulated by the modulation unit 406. Precoding in MIMO may be performed by the modulation unit 406.
  • the modulated data is converted into a baseband signal, and then output to the frequency conversion unit 407, where it is converted into a radio transmission frequency. Then, the transmission signal is transmitted from antennas 408-1 to 408-4 to one or more mobile terminals 202.
  • FIG. 5 an example in which the number of antennas is four is shown, but the number of antennas is not limited to four.
  • the reception process of the base station 213 is executed as follows. Radio signals from one or more mobile terminals 202 are received by antennas 408-1 to 408-4. The received signals are converted from a radio reception frequency to a baseband signal by frequency conversion unit 407, and demodulation process is performed by demodulation unit 409. The demodulated data is passed to decoder unit 410, where decoding process such as error correction is performed. The decoded data is passed to protocol processing unit 403, where protocol processing such as MAC, RLC, PDCP, SDAP, etc., for example, operations such as removing the header in each protocol, are performed.
  • protocol processing such as MAC, RLC, PDCP, SDAP, etc.
  • control data is passed to the control unit 411, 5GC communication unit 412, EPC communication unit 401, or other base station communication unit 402 and the user data is passed to the 5GC communication unit 412, EPC communication unit 401, or other base station communication unit 402.
  • Data sent from the other base station communication unit 402 may be sent to the 5GC communication unit 412 or the EPC communication unit 401.
  • the data may be, for example, uplink data sent to the 5GC communication unit 412 or the EPC communication unit 401 via the other base station in the DC.
  • control unit 411 The series of processes in the base station 213 are controlled by the control unit 411. Therefore, although the control unit 411 is omitted in FIG. 5, it is also connected to each of the units 401, 402, 405 to 410, and 412.
  • the various parts of the base station 213, such as the control unit 411, protocol processing unit 403, 5GC communication unit 412, EPC communication unit 401, other base station communication unit 402, encoder unit 405, and decoder unit 410, are implemented by a processing circuit including a processor and memory, or a dedicated processing circuit such as an FPGA, ASIC, or DSP, similar to the mobile terminal 202 described above.
  • a processing circuit including a processor and memory, or a dedicated processing circuit such as an FPGA, ASIC, or DSP, similar to the mobile terminal 202 described above.
  • the number of antennas used by the base station 213 for transmission and the number of antennas used for reception may be the same or different.
  • the DU communication unit is connected to the protocol processing unit 403.
  • the protocol processing unit 403 in the CU 215 performs protocol processing such as PDCP and SDAP.
  • a configuration in which a CU communication unit is provided may be used, excluding the EPC communication unit 401, other base station communication unit 402, and 5GC communication unit 412 shown in FIG. 5.
  • the CU communication unit is connected to a protocol processing unit 403.
  • the protocol processing unit 403 in the DU 216 performs protocol processing such as PHY, MAC, and RLC.
  • FIG. 6 is a block diagram showing the configuration of the 5GC unit.
  • FIG. 6 shows the configuration of the 5GC unit 214 shown in FIG. 2 described above.
  • FIG. 6 shows a case where the 5GC unit 214 shown in FIG. 2 includes an AMF configuration, an SMF configuration, and a UPF configuration.
  • the AMF may have the function of the control plane control unit 525
  • the SMF may have the function of the session management unit 527
  • the UPF may have the function of the user plane communication unit 523 and the Data Network communication unit 521.
  • the Data Network communication unit 521 transmits and receives data between the 5GC unit 214 and the Data Network.
  • the base station communication unit 522 transmits and receives data between the 5GC unit 214 and the base station 213 via the NG interface.
  • User data sent from the Data Network is passed from the Data Network communication unit 521 to the base station communication unit 522 via the user plane communication unit 523, and is then transmitted to one or more base stations 213.
  • User data sent from the base station 213 is passed from the base station communication unit 522 to the Data Network communication unit 521 via the user plane communication unit 523, and is then transmitted to the Data Network.
  • the control data sent from the base station 213 is passed from the base station communication unit 522 to the control plane control unit 525.
  • the control plane control unit 525 may pass the control data to the session management unit 527.
  • the control data may be sent from the Data Network.
  • the control data sent from the Data Network may be sent from the Data Network communication unit 521 to the session management unit 527 via the user plane communication unit 523.
  • the session management unit 527 may send the control data to the control plane control unit 525.
  • the user plane control unit 523 includes a PDU processing unit 523-1, a mobility anchoring unit 523-2, etc., and performs general processing for the user plane (hereinafter sometimes referred to as U-Plane).
  • the PDU processing unit 523-1 processes data packets, for example, sending and receiving packets with the Data Network communication unit 521, and sending and receiving packets with the base station communication unit 522.
  • the mobility anchoring unit 523-2 is responsible for anchoring the data path during UE mobility.
  • the session management unit 527 manages the PDU session established between the UE and the UPF.
  • the session management unit 527 includes a PDU session control unit 527-1 and a UE IP address allocation unit 527-2.
  • the PDU session control unit 527-1 manages the PDU session between the mobile terminal 202 and the 5GC unit 214.
  • the UE IP address allocation unit 527-2 allocates an IP address to the mobile terminal 202.
  • the control plane control unit 525 includes a NAS security unit 525-1, an idle state mobility management unit 525-2, etc., and performs general processing for the control plane (hereinafter sometimes referred to as the C-Plane).
  • the NAS security unit 525-1 performs security for NAS (Non-Access Stratum) messages, etc.
  • the idle state mobility management unit 525-2 performs mobility management for the standby state (idle state: also called RRC_IDLE state or simply idle), generation and control of paging signals in the standby state, addition, deletion, update, search, tracking area list management, etc. for one or more mobile terminals 202 under its umbrella.
  • the series of processes in the 5GC unit 214 are controlled by the control unit 526. Therefore, although the control unit 526 is omitted in FIG. 6, it is connected to each of the units 521 to 523, 525, and 527.
  • Each unit in the 5GC unit 214 is realized, for example, by a processing circuit including a processor and memory, or a dedicated processing circuit such as an FPGA, ASIC, or DSP, similar to the control unit 310 of the mobile terminal 202 described above.
  • FIG. 7 is a flow chart showing an outline of the process from cell search to standby operation performed by a communication terminal (UE) in an NR communication system.
  • the communication terminal starts a cell search, in step ST601, it synchronizes slot timing and frame timing using a first synchronization signal (P-SS) and a second synchronization signal (S-SS) transmitted from a nearby base station.
  • P-SS first synchronization signal
  • S-SS second synchronization signal
  • the Synchronization Signal is assigned a synchronization code that corresponds one-to-one to the PCI (Physical Cell Identifier) assigned to each cell. 1008 different PCIs are being considered. A communication terminal uses these 1008 different PCIs to synchronize and detect (identify) the PCI of the synchronized cell.
  • the communication terminal receives the PBCH for the next synchronized cell.
  • the MIB Master Information Block
  • the MIB is mapped to the BCCH on the PBCH. Therefore, the MIB can be obtained by receiving the PBCH and obtaining the BCCH.
  • MIB information include SFN (System Frame Number), scheduling information for SIB (System Information Block) 1, subcarrier spacing for SIB1, etc., and DM-RS position information.
  • the communication terminal also acquires an SS block identifier from the PBCH. A part of the bit string of the SS block identifier is included in the MIB. The remaining bit string is included in an identifier used to generate a sequence of a DM-RS associated with the PBCH. The communication terminal acquires the SS block identifier using the MIB included in the PBCH and the sequence of a DM-RS associated with the PBCH.
  • step ST603 the communication terminal measures the received power of the SS block.
  • the communication terminal selects the cell with the best reception quality, for example, the cell with the highest reception power, that is, the best cell, from among the one or more cells detected up to step ST603.
  • the communication terminal also selects the beam with the best reception quality, for example, the beam with the highest reception power of the SS block, that is, the best beam.
  • the reception power of the SS block for each SS block identifier is used to select the best beam.
  • step ST605 the communication terminal receives DL-SCH based on the scheduling information of SIB1 included in the MIB, and obtains SIB1 in the broadcast information BCCH.
  • SIB1 includes information on access to the cell, cell configuration information, and scheduling information of other SIBs (SIBk: an integer k ⁇ 2).
  • SIB1 also includes a tracking area code (TAC).
  • TAC tracking area code
  • the communication terminal compares the TAC of SIB1 received in step ST605 with the TAC portion of the tracking area identity (TAI) in the tracking area list already held by the communication terminal.
  • the tracking area list is also called a TAI list.
  • TAI is identification information for identifying a tracking area, and is composed of MCC (Mobile Country Code), MNC (Mobile Network Code), and TAC (Tracking Area Code).
  • MCC Mobile Country Code
  • MNC Mobile Network Code
  • TAC Track Area Code
  • MCC Mobile Country Code
  • MNC Mobile Network Code
  • TAC Track Area Code
  • step ST606 If the comparison result in step ST606 shows that the TAC received in step ST605 is the same as the TAC included in the tracking area list, the communications terminal enters standby mode in the cell. If the comparison shows that the TAC received in step ST605 is not included in the tracking area list, the communications terminal requests a change of tracking area through the cell to the core network (EPC) including the MME, etc., in order to perform a Tracking Area Update (TAU).
  • EPC core network
  • MME Tracking Area Update
  • the devices constituting the core network update the tracking area list based on the identification number (UE-ID, etc.) of the communication terminal sent from the communication terminal together with the TAU request signal.
  • the core network side device transmits the updated tracking area list to the communication terminal.
  • the communication terminal rewrites (updates) the TAC list held by the communication terminal based on the received tracking area list.
  • the communication terminal then enters standby mode in the cell.
  • random access In random access, four-step random access and two-step random access are used. In addition, for each of four-step random access and two-step random access, there is contention-based random access, i.e., random access in which timing collisions with other mobile terminals may occur, and contention-free random access.
  • contention-based random access i.e., random access in which timing collisions with other mobile terminals may occur
  • the mobile terminal transmits a random access preamble to the base station.
  • the random access preamble may be selected by the mobile terminal from within a predetermined range, or may be individually assigned to the mobile terminal and notified by the base station.
  • the base station transmits a random access response to the mobile terminal.
  • the random access response includes uplink scheduling information to be used in the third step, a terminal identifier to be used in the uplink transmission in the third step, etc.
  • the mobile terminal performs an uplink transmission to the base station.
  • the mobile terminal uses the information acquired in the second step.
  • the base station notifies the mobile terminal whether the collision has been resolved. If the mobile terminal is notified that there is no collision, it ends the random access process. If the mobile terminal is notified that there is a collision, it restarts the process from the first step.
  • the collision-free four-step random access method differs from the collision-based four-step random access method in the following ways. That is, prior to the first step, the base station assigns a random access preamble and uplink scheduling to the mobile terminal in advance. Also, in the fourth step, there is no need to notify whether or not the collision has been resolved.
  • the mobile terminal transmits a random access preamble and performs uplink transmission to the base station.
  • the base station notifies the mobile terminal whether there is a collision. If the mobile terminal is notified that there is no collision, it ends the random access process. If the mobile terminal is notified that there is a collision, it restarts the process from the first step.
  • the collision-free two-step random access method differs from the collision-based two-step random access method in the following ways.
  • the base station assigns a random access preamble and uplink scheduling to the mobile terminal in advance.
  • the base station transmits a random access response to the mobile terminal.
  • Figure 8 shows an example of a cell configuration in NR.
  • narrow beams are formed and transmitted in different directions.
  • base station 750 transmits and receives signals to and from a mobile terminal using beam 751-1.
  • base station 750 transmits and receives signals to and from a mobile terminal using beam 751-2.
  • base station 750 transmits and receives signals to and from a mobile terminal using one or more of beams 751-3 to 751-8. In this way, base station 750 forms a wide-range cell 752.
  • the number of beams used by the base station 750 is eight, but the number of beams may be different from eight. Also, in the example shown in FIG. 8, the number of beams used simultaneously by the base station 750 is one, but it may be multiple.
  • the concept of Quasi-CoLocation is used to identify beams (see Non-Patent Document 14 (3GPP TS38.214)). That is, the beam is identified by information indicating which reference signal (e.g., SS block, CSI-RS) the beam can be considered to be the same as.
  • the information may include the type of information on the viewpoint of the beam being considered to be the same, such as Doppler shift, Doppler shift spread, average delay, average delay spread, and spatial Rx parameters (see Non-Patent Document 14 (3GPP TS38.214)).
  • SL Side Link
  • D2D Device to Device
  • V2V Vehicle to Vehicle
  • PC5-S signaling is implemented to establish a link for implementing SL, i.e., PC5 communication.
  • the link is implemented at the V2X layer and is also called a Layer 2 link.
  • RRC signaling in SL communication is also called PC5 RRC signaling.
  • PC5 RRC signaling it has been proposed to notify UE capabilities between UEs performing PC5 communication, and to notify AS layer settings for V2X communication using PC5 communication.
  • Figure 9 shows an example of the connection configuration of a mobile terminal in SL communication.
  • UE805 and UE806 are present within the coverage 803 of base station 801.
  • UL/DL communication 807 is performed between base station 801 and UE805.
  • UL/DL communication 808 is performed between base station 801 and UE806.
  • SL communication 810 is performed between UE805 and UE806.
  • UE811 and UE812 are present outside the coverage 803.
  • SL communication 814 is performed between UE805 and UE811.
  • SL communication 816 is performed between UE811 and UE812.
  • UE 805 shown in FIG. 9 relays communication between UE 811 and base station 801.
  • a configuration similar to that shown in FIG. 4 may be used for the UE that performs relaying.
  • the relaying process in the UE will be described using FIG. 4.
  • the relaying process by UE 805 in communication from UE 811 to base station 801 will be described.
  • Radio signals from UE 811 are received by antennas 307-1 to 307-4.
  • the received signals are converted from a radio reception frequency to a baseband signal by frequency conversion unit 306, and demodulated by demodulation unit 308. Weight calculation and multiplication may also be performed by demodulation unit 308.
  • the demodulated data is passed to decoder unit 309, where decoding such as error correction is performed.
  • the decoded data is passed to protocol processing unit 301, where protocol processing such as MAC and RLC used for communication with UE 811 is performed, such as removing the header in each protocol. Protocol processing such as RLC and MAC used for communication with base station 801 is also performed, such as adding a header in each protocol. In some cases, protocol processing of PDCP and SDAP may be performed in the protocol processing unit 301 of the UE 811.
  • the data that has undergone protocol processing is passed to the encoder unit 304, where encoding processing such as error correction is performed. There may be data that is output directly from the protocol processing unit 301 to the modulation unit 305 without undergoing encoding processing.
  • the data that has undergone encoding processing in the encoder unit 304 is modulated in the modulation unit 305.
  • Precoding in MIMO may be performed in the modulation unit 305.
  • the modulated data is converted into a baseband signal, and then output to the frequency conversion unit 306, where it is converted into a wireless transmission frequency. Thereafter, a transmission signal is transmitted from the antennas 307-1 to 307-4 to the base station 801.
  • a base station that supports IAB (hereinafter, sometimes referred to as an IAB base station) is composed of an IAB donor CU, which is the CU of a base station that operates as an IAB donor providing IAB functions, an IAB donor DU, which is the DU of a base station that operates as an IAB donor, and an IAB node that is connected to the IAB donor DU and to the UE using a radio interface.
  • An F1 interface is provided between the IAB node and the IAB donor CU (see Non-Patent Document 2).
  • IAB donor CU 901 is connected to IAB donor DU 902.
  • IAB node 903 is connected to IAB donor DU 902 using a wireless interface.
  • IAB node 903 is connected to IAB node 904 using a wireless interface. That is, IAB nodes may be connected in multiple stages.
  • UE 905 is connected to IAB node 904 using a wireless interface.
  • UE 906 may be connected to IAB node 903 using a wireless interface, and UE 907 may be connected to IAB donor DU 902 using a wireless interface.
  • Multiple IAB donor DUs 902 may be connected to an IAB donor CU 901, multiple IAB nodes 903 may be connected to an IAB donor DU 902, and multiple IAB nodes 904 may be connected to an IAB node 903.
  • the BAP (Backhaul Adaptation Protocol) layer is provided in the connection between the IAB donor DU and the IAB node and in the connection between the IAB nodes (see Non-Patent Document 29).
  • the BAP layer performs operations such as routing the received data to the IAB donor DU and/or the IAB node, and mapping to the RLC channel (see Non-Patent Document 29).
  • the configuration of the IAB donor DU a configuration similar to that of DU 216 is used.
  • BAP layer processing is performed, such as adding a BAP header to downstream data, routing to an IAB node, and removing the BAP header from upstream data.
  • IAB node configuration a configuration that omits the EPC communication unit 401, other base station communication unit 402, and 5GC communication unit 412 shown in Figure 5 may be used.
  • the transmission and reception processing in the IAB node will be explained using Figures 5 and 10.
  • the transmission and reception processing of the IAB node 903 in the communication between the IAB donor CU 901 and the UE 905 will be explained.
  • a radio signal from the IAB node 904 is received by the antenna 408 (some or all of the antennas 408-1 to 408-4).
  • the received signal is converted from the radio reception frequency to a baseband signal by the frequency conversion unit 407, and demodulation processing is performed by the demodulation unit 409.
  • the demodulated data is passed to the decoder unit 410, where decoding processing such as error correction is performed.
  • the decoded data is passed to the protocol processing unit 403, where protocol processing such as MAC and RLC used for communication with the IAB node 904 is performed, for example, operations such as removing the header in each protocol are performed.
  • protocol processing such as MAC and RLC used for communication with the IAB node 904
  • routing to the IAB donor DU 902 using the BAP header is performed, and protocol processing such as RLC and MAC used for communication with the IAB donor DU 902, for example, operations such as adding a header for each protocol, are performed.
  • the data that has been subjected to protocol processing is passed to the encoder unit 405, where encoding processing such as error correction is performed.
  • the encoded data is modulated by the modulation unit 406.
  • Precoding in MIMO may be performed by the modulation unit 406.
  • the modulated data is converted into a baseband signal, and then output to the frequency conversion unit 407, where it is converted into a radio transmission frequency.
  • a transmission signal is transmitted to the IAB donor DU 902 from the antennas 408-1 to 408-4.
  • the same processing is performed in downlink communication from the IAB donor CU 901 to the UE 905.
  • IAB node 904 In IAB node 904, the same sending and receiving processing as in IAB node 903 is performed. In protocol processing unit 403 of IAB node 903, processing of the BAP layer is performed, such as adding a BAP header in upstream communication and routing to IAB node 904, and removing the BAP header in downstream communication.
  • ultra-low power consumption IoT devices (hereinafter sometimes referred to as devices) into mobile communication systems is being discussed. It has been proposed that ultra-low power consumption IoT devices communicate with UEs or gNBs using a communication method different from the communication method used in the air interface defined by conventional 3GPP (Non-Patent Documents 31, 33, 34). For this reason, a method is required for coexistence of communication on the air interface (Uu) between UEs and gNBs and communication on the air interface between devices and UEs or gNBs.
  • Uu air interface
  • This embodiment discloses a method to solve this problem.
  • the base station schedules communication between the device and the UE or the base station.
  • the scheduling may be dynamic scheduling or semi-persistent scheduling.
  • the base station notifies the UE of information related to the scheduling.
  • the base station may transmit a scheduling grant to the UE.
  • the grant may be a dynamic grant or a configured grant.
  • the above-mentioned configured grant may be, for example, a configured grant of type 1 (see Non-Patent Document 2, Section 10.3). This makes it possible, for example, to reduce the amount of signaling from the base station to the UE.
  • the above-mentioned configured grant may be a configured grant of type 2 (see Non-Patent Document 2, Section 10.3). This makes it possible, for example, to flexibly control the transmission power in communication between the UE and the device.
  • the following (1) to (8) are disclosed as information contained in the scheduling information notified from the base station to the UE.
  • the information (1) above may be, for example, information indicating that the communication is for a device, information indicating that the communication is for a base station, or information indicating that the communication is for another UE.
  • a different DCI may be used for each type of communication partner. For example, a new DCI for communication for devices may be created and used. This allows, for example, a UE to quickly identify the communication partner.
  • a Radio Network Temporary Identifier may be assigned for each type of communication partner.
  • the RNTI used for device-directed communication may be an RNTI for receiving a PDCCH including scheduling information for device-directed communication.
  • the RNTI used for base station-directed communication may be an RNTI for receiving a PDCCH including scheduling information for communication with the base station.
  • the base station may notify the UE of the RNTI in advance.
  • the UE may use the RNTI to determine whether the PDCCH transmitted from the base station includes scheduling information for device-directed communication or includes scheduling information for communication with the base station. This allows the UE to quickly determine the type of communication partner, for example.
  • the information (2-1) above may be, for example, information about the frequency used for transmission from the UE to the device, or information about the frequency used for transmission from the device to the UE, or it may include both of the above.
  • the base station may notify the UE of information about the frequency used for transmission from the device to the UE, allowing the UE to quickly ascertain the reception frequency from the device.
  • the information in (2-1) above may include information about the carrier, for example, information about the CC, information about the BWP, information about the physical resource block (PRB), information about the subcarrier, for example, information about the subcarrier number, or a combination of the above.
  • the information about the subcarrier number may be uniquely assigned within one PRB, uniquely assigned within multiple PRBs, uniquely assigned within a BWP, or uniquely assigned within a CC. For example, by being uniquely assigned within one PRB, it is possible to keep the size of the information about the subcarrier number small.
  • the information (2-1) above may be given as information on the center frequency, or as information on the higher end of the frequency band used for transmission and reception with the device, or as information on the lower end.
  • the information above may include information on the frequency band.
  • the frequency band information may be given, for example, using information on the operating band (see non-patent documents 38, 39, and 40).
  • the information above may include information on the frequency width.
  • the frequency width information may be given in PRB units, in subcarrier units, or in a specified unit (e.g., in kilohertz units), or a combination of multiple of the above may be used. For example, by providing the information in PRB units and/or subcarrier units, it is possible to keep the size of the information small. As another example, by providing the information in the specified unit, it is possible to improve the flexibility of communication between the device and the UE.
  • the information (2-1) above may include information about subcarrier spacing.
  • the information may be information about subcarrier spacing in transmission from a UE to a device, or information about subcarrier spacing in transmission from a device to a UE.
  • the information may be given as an integer multiple and/or an integer fraction of a predetermined frequency, or may be given as information of a power of 2 multiplied by a predetermined frequency, or may be given in a predetermined unit (e.g., kilohertz), or a combination of the above may be used.
  • the information for example, by providing the information as an integer multiple and/or an integer fraction of a predetermined frequency, it becomes possible to flexibly change the subcarrier spacing in transmission and reception between a UE and a device, while reducing the signaling size from a base station to a UE.
  • the information in a predetermined unit, it becomes possible to communicate with devices having various characteristics.
  • the information (2-2) above may include information on the time when the UE transmits to the device, may include information on the time when the device responds to the UE, may include information on the time from the completion of transmission from the UE to the device to the start of the response from the device to the UE, may include information on the time from the start of transmission from the UE to the device to the completion of the response from the device to the UE, or may include information on a combination of multiple of the above.
  • a plurality of the above information may be included. By including a plurality of the above information, for example, the base station can collectively schedule multiple transmissions and responses between the UE and the device, which makes it possible to reduce the amount of signaling between the base station and the UE.
  • the information (2-2) above may be provided on a frame-by-frame basis, a subframe-by-slot basis, a symbol-by-symbol basis, a predetermined unit (e.g., microseconds), or a combination of the above.
  • a predetermined unit e.g., microseconds
  • by providing the information in the above-mentioned predetermined unit it is possible to improve the flexibility of communication between devices and UEs.
  • the configuration of frames, subframes, slots, and/or symbols (hereinafter sometimes referred to as frames, etc.) used in communication between a UE and a base station may be the same as the configuration of frames, etc. used in communication between a UE and a base station (see FIG. 1). This makes it possible, for example, to avoid complexity in the communication system.
  • the configuration of frames, etc. used in communication between a UE and a base station may be different from the configuration of frames, etc. used in communication between a UE and a base station. This makes it possible, for example, to improve flexibility in the communication system.
  • the length of a frame, etc. used in communication between a UE and a base station may be the same as, or an integer multiple of, or an integer fraction of, the length of a frame, etc. used in communication between a UE and a base station. This makes it possible, for example, to avoid complexity in the communication system.
  • the length of a frame, etc. used in communication between a UE and a base station may be different from the length of a frame, etc. used in communication between a UE and a base station.
  • one slot may be composed of a number of symbols other than 7 symbols (e.g., 5 symbols). This makes it possible, for example, to improve flexibility in the communication system.
  • the scheduled timing may be along frame timing, slot timing, and/or symbol timing.
  • the scheduling may be, for example, scheduling for communication between a UE and a device. This may, for example, avoid complexities related to scheduling.
  • the scheduled timing may not be aligned with frame timing, slot timing, and/or symbol timing. This allows for flexibility in scheduling, for example, in communications between a UE and a device.
  • the information in (2-3) above may include information about a beam used to transmit a signal from the UE to the device.
  • a signal for deriving a beam may be provided.
  • the information about the beam may include information about the signal.
  • the signal may be, for example, a reference signal.
  • a new reference signal used for transmission from the UE to the device may be provided.
  • an SRS may be used.
  • an SRS setting may be used to set a beam used to transmit a signal from the UE to the device.
  • the information about the beam may be, for example, information about a beam used for SRS transmission from the UE.
  • the information about the beam used for SRS transmission may include, for example, an SRS identifier.
  • information about a beam used by the UE to receive a signal from a base station may be included.
  • the information about the beam may include, for example, an identifier of a downlink signal (e.g., a CSI-RS identifier, an SS block identifier).
  • the UE may transmit and receive between the device using the beam information included in the above (2-3). This makes it possible, for example, to prevent a UE from transmitting radio waves in unnecessary directions, thereby reducing interference in the communication system.
  • the SRS settings used to set the beam used to transmit signals from the UE to the device may be set separately from the SRS settings transmitted from the UE to the base station. This makes it possible to avoid, for example, complexity in the RRC signaling configuration for the SRS settings.
  • the information (2-3) above may include information regarding the beam that the UE uses to receive a signal from the device.
  • the information regarding the beam used for reception may be, for example, similar to the information regarding the beam used for transmission described above.
  • the information may be used, for example, when the device transmits to the UE using radio waves from another UE or a base station.
  • the UE may use the information to receive a signal from the device. This allows, for example, the UE to quickly receive a signal from the device.
  • the beam used by the UE to receive a signal from the device and the beam used by the UE to transmit a signal to the device may be the same. This can, for example, avoid complexity in the communication system.
  • the beams may be different from each other.
  • the beam used by the UE to receive a signal from the device may have a higher gain than the beam used by the UE to transmit a signal to the device. This can, for example, enable communication between the UE and the device even when the power of the signal from the device is low.
  • the base station may configure the UE with signals for deriving the beam.
  • the configuration may be performed using RRC signaling, e.g., RRC reconfiguration signaling.
  • the configuration may include information about resources (e.g., frequency, time, power) used to transmit the signals.
  • the UE may transmit a signal to the device to derive a beam.
  • the transmission of the signal may be performed together with signaling to the device.
  • the transmission of the signal may be time-multiplexed or frequency-multiplexed with the signaling to the device.
  • the transmission of the signal may be performed separately from the signaling to the device.
  • the information (2-4) above may include information on the transmission power of the UE.
  • the transmission power included in the information may be given using an absolute value. For example, it may be given in dBm units, or it may be given as information in which the absolute value is quantized in a predetermined unit. This makes it possible, for example, to quickly change the transmission power of the UE.
  • the transmission power included in the information may be a relative value. For example, a relative value with respect to a predetermined power may be given, or a relative value with respect to the previous transmission power may be given. This makes it possible, for example, to reduce the amount of signaling from the base station to the UE.
  • the relative values may be given in the same steps as the relative values used in the communication between the UE and the base station. This makes it possible to avoid, for example, complexity in the communication system.
  • the relative values may be given in steps different from the relative values used in the communication between the UE and the base station.
  • the relative values may be given in steps larger than the relative values used in the communication between the UE and the base station. This makes it possible, for example, to quickly control the transmission power in the communication between the UE and the device.
  • the relative values may be given in steps smaller than the relative values used in the communication between the UE and the base station. This makes it possible, for example, to finely control the transmission power in the communication between the UE and the device.
  • the information in (2-4) above may include information about the transmission power from the device to the UE.
  • the UE may notify the device of the information about the transmission power.
  • the device may use the information to transmit to the UE. This allows the UE to quickly measure the path loss between the device and its own UE, for example.
  • the information (3) above may include a UE identifier, for example, a Radio Network Temporary Identifier (RNTI).
  • RNTI Radio Network Temporary Identifier
  • the UE may use this information to transmit to the device. This allows the UE to quickly recognize that the scheduling information is intended for the UE.
  • Different identifiers may be assigned to the same UE for device-directed communication and base station-directed communication.
  • the UE may use the identifier included in (3) above to determine whether the scheduling is for device-directed communication or for base station-directed communication. This allows the UE to quickly determine the communication partner, for example.
  • the information (4) above may include information for identifying the device.
  • the information for identifying the device may include a device identifier. This allows, for example, the UE to quickly identify the device with which it is communicating.
  • the information for identifying the device may include information that is readable by the user. This allows the user to quickly identify the device.
  • the UE may search only for devices that match the aforementioned identifier. This allows the UE to quickly search for devices with that identifier, for example.
  • the information in (4) above may include information indicating that all devices are the target, or may include information regarding an instruction to search for devices.
  • the UE may use this information to search for devices. This allows the UE to search for any device in its vicinity, for example.
  • the information (4) above may include a portion of the device identifier.
  • the portion of the device identifier may be, for example, a predetermined number of digits from the lowest digits of the device identifier, or a predetermined number of digits from the highest digits of the device identifier.
  • the UE may search for only devices that match that portion of the identifier. This makes it possible to prevent detection of an excessive number of devices, for example, when there are many devices in the vicinity of the UE.
  • the information in (4) above may include information about devices that are not subject to search.
  • the information may include a device identifier or a part of the device identifier. It may include information indicating that a device that corresponds to the identifier or part of the identifier is not subject to search.
  • the UE may use the information to exclude the device from the search targets. This makes it possible to prevent multiple UEs from searching for the same device in a case where other UEs can communicate with the device, for example, and as a result, it is possible to improve the efficiency of the communication system, for example, the efficiency of resource utilization.
  • the information (4) above may not be included.
  • the UE may detect all devices from which responses have been returned. This may, for example, reduce the amount of signaling between the base station and the UE.
  • the information (5) above may include information on the reception power of radio waves from the device, information on the signal to interference plus noise ratio (SINR), information on the error rate, or a plurality of the above information.
  • Information on the thresholds of the reception power, SINR, and/or error rate may be included.
  • the error rate may be the bit error rate (BER), the block error rate (BLER), or the frame error rate (FER).
  • the UE may not detect devices with reception quality below the threshold or below the threshold. This makes it possible to prevent, for example, the UE from detecting an excessive number of devices.
  • the UE may notify the base station of information on devices with reception quality below the threshold or below the threshold.
  • the base station may use the information to determine that another UE will communicate with the device. This makes it possible to ensure, for example, communication quality between the UE and the device in a communication system.
  • the information (6) above may include information on the communication capacity, speed, and/or bit rate between the UE and the device, may include information on communication delay, or may include multiple pieces of information as described above. It may include information on a threshold for communication capacity, speed, bit rate, and/or delay.
  • the UE may not communicate with devices with a QoS below the threshold or at or below the threshold.
  • the UE may notify the base station of information on devices with a QoS below the threshold or at or below the threshold.
  • the base station may use the information to decide that another UE will communicate with the device. This makes it possible to ensure QoS in communications between the UE and the device, for example.
  • the information in (7) above may include information regarding an upper limit on the number of devices that the UE can detect.
  • the UE may detect more devices than the number included in (7) above, or may not detect devices equal to or greater than the number included in (7) above. This makes it possible, for example, to prevent the UE from detecting an excessive number of devices, and as a result, it is possible to improve the efficiency of the communication system, for example, the efficiency of resource utilization.
  • the UE communicates with the device using the information (1) to (8) described above.
  • the UE may search for, confirm, and/or detect the device, obtain data held by the device (e.g., read data from the device), make a request to write data to the device, or transmit a radio wave source for communication from the device to the UE.
  • Communication from the device to the UE may be, for example, a response to the search for, confirmation, and/or detection of the device from the UE, a notification of data held by the device, or a response to a request to write data from the UE.
  • Notification of data held by the device may be triggered, for example, by the acquisition of data from the UE to the device, or may be performed without being triggered by such acquisition.
  • the UE may request scheduling from the base station.
  • the request may be for communication between the UE and the device.
  • the scheduling request may include information regarding the communication between the UE and the device.
  • the scheduling request may include information indicating that the scheduling request is for communication between the UE and the device.
  • Different resources may be used for a scheduling request for communication between a UE and a device and a scheduling request for communication between a UE and a base station.
  • the identifiers of the scheduling requests may be different, or the identifiers of the PUCCH resources may be different. This allows, for example, the base station to quickly determine whether the UE's scheduling request is for communication between the UE and a base station or communication between the UE and a device.
  • Different resources may be used between a scheduling request for the UE to transmit information about a device to the base station and a scheduling request for transmitting data generated by the UE to the base station.
  • the method of providing different resources may be the same as described above. This allows the base station to quickly determine, for example, whether uplink data from the UE is data about a device or data generated by the UE.
  • Communication between the UE and the device may include signaling from the UE to the device, data transmitted from the UE to the device (e.g., data written to the device), signaling from the device to the UE, or data transmitted from the device to the UE (e.g., data read from the device).
  • Different resources may be used for the scheduling requests used for each of the above-mentioned transmissions.
  • the different resources may be provided in the same manner as described above. This allows, for example, the base station to quickly grasp the type of transmission and reception between the UE and the device, and as a result, the base station can efficiently schedule the transmission and reception between the UE and the device.
  • a scheduling request for communication between a UE and a device may be provided for each device. This may, for example, improve the flexibility of communication between a UE and a device. As another example, the scheduling request may be common between devices. This may, for example, save resources allocated to the scheduling request. As another example, the scheduling request may be provided for each of a plurality of devices (e.g., a group of devices). This may, for example, improve the flexibility of communication between a UE and a device while saving resources allocated to the scheduling request.
  • the group may be set for each communication service, for example.
  • the communication service may be, for example, eMBB (enhanced Mobile Broadband), URLLC (Ultra-Reliability Low Latency Communication), or mMTC (massive Machine Type Communication).
  • the communication service may be determined by the application, for example, asset tracking, entrance/exit management, or other applications.
  • the same resources may be used for a scheduling request for communication between a UE and a device and a scheduling request for communication between a UE and a base station. This makes it possible to prevent, for example, a shortage of resources that can be allocated to scheduling requests.
  • a Buffer Status Report may be used to request scheduling from a UE to a base station.
  • the scheduling request may be, for example, a scheduling request for communication between a UE and a device, or a scheduling request for communication between a UE and a base station.
  • the UE may be capable of using multiple BSRs.
  • each of the multiple BSRs may be provided with identification information (e.g., an identifier).
  • the UE may include the identification information in transmitting the BSR to the base station.
  • the base station may use the information to identify the BSR.
  • the BSR used in the scheduling request for the UE to transmit information about the device to the base station and the BSR used in the scheduling request for the UE to transmit data generated by the UE to the base station may be different from each other. This makes it possible, for example, to prevent congestion of the LCG (Logical Channel Group) assigned to the UE. As another example, the BSR used in the scheduling request for the UE to transmit information about the device to the base station and the BSR used in the scheduling request for the UE to transmit data generated by the UE to the base station may be the same BSR. This makes it possible, for example, to avoid complexity in the communication system.
  • LCG Logical Channel Group
  • the BSRs used in the scheduling requests for signaling from the UE to the device, data transmitted from the UE to the device, signaling from the device to the UE, and/or data transmitted from the device to the UE may be different from each other. This makes it possible, for example, to prevent the LCG allocated to the UE from becoming congested. As another example, the BSRs used in the scheduling requests mentioned above may be the same. This makes it possible, for example, to avoid complexity in the communication system.
  • the BSR used for the scheduling request for communication between a UE and a device may be provided for each device. This makes it possible, for example, to improve the flexibility of communication between a UE and a device. As another example, the BSR used for the scheduling request may be common between devices. This makes it possible, for example, to avoid the complexity of the communication system. As another example, the BSR used for the scheduling request may be provided for each of a plurality of devices (e.g., a group of devices). This makes it possible, for example, to improve the flexibility of the communication system while avoiding the complexity of the communication system.
  • a new logical channel may be provided.
  • the logical channel may be, for example, a logical channel assigned to communication between the UE and the device, or a logical channel through which the UE transmits information about the device to the base station.
  • a logical channel may be assigned for communication between the UE and the device.
  • the logical channel may be assigned on a per-device basis, the same logical channel may be assigned to multiple devices (e.g., a group of devices), or the same logical channel may be assigned to all devices with which the UE communicates.
  • the same logical channel may be allocated between the transmission of information related to the device from the UE to the base station and the transmission of data generated by the UE to the base station. This makes it possible, for example, to prevent congestion of the logical channel.
  • a different logical channel may be allocated between the transmission of information related to the device from the UE to the base station and the transmission of data generated by the UE to the base station. This makes it possible, for example, to improve flexibility in the communication system.
  • the same logical channel may be assigned to signaling from a UE to a device, data transmitted from a UE to a device, signaling from a device to a UE, and/or data transmitted from a device to a UE. This makes it possible, for example, to prevent logical channel congestion.
  • different logical channels may be assigned to signaling from a UE to a device, data transmitted from a UE to a device, signaling from a device to a UE, and/or data transmitted from a device to a UE. This makes it possible, for example, to improve the flexibility of the communication system.
  • the logical channel may belong to a logical channel group.
  • the logical channel group to which the logical channel belongs may belong to a different logical channel group from the logical channel related to the communication between the UE and the base station. This allows the base station to quickly distinguish between the communication between the UE and the device and the communication between the UE and the base station, for example.
  • the logical channel group may be assigned on a per-device basis, the same logical channel group may be assigned to multiple devices, or the same logical channel group may be assigned to all devices with which the UE communicates.
  • the same logical channel group may be assigned between the transmission of device-related information from the UE to the base station and the transmission of data generated by the UE to the base station. This makes it possible, for example, to prevent logical channel group congestion.
  • different logical channel groups may be assigned between the transmission of device-related information from the UE to the base station and the transmission of data generated by the UE to the base station. This makes it possible, for example, to improve flexibility in the communication system.
  • the same logical channel group may be assigned to signaling from a UE to a device, data transmitted from a UE to a device, signaling from a device to a UE, and/or data transmitted from a device to a UE. This makes it possible, for example, to prevent logical channel groups from becoming congested. As another example, different logical channel groups may be assigned to signaling from a UE to a device, data transmitted from a UE to a device, signaling from a device to a UE, and/or data transmitted from a device to a UE. This makes it possible, for example, to improve the flexibility of the communication system.
  • Communications between a UE and a device may be scheduled for each device. This can, for example, avoid complexity in the communication system.
  • communications between a UE and a device may be scheduled for multiple devices simultaneously. For example, multiple devices assigned to the same logical channel may be scheduled simultaneously. This can, for example, reduce the number of times that a base station schedules a UE, and as a result, can improve efficiency in the communication system, for example, resource utilization efficiency.
  • the UE may notify the base station of information related to the device.
  • the information may include, for example, the results of a device search, information identifying the device, information acquired from the device (e.g., data acquired by a sensor associated with the device), or a combination of the above information.
  • the information may include information related to the location of the UE itself. This allows, for example, the base station to determine the approximate location of the device.
  • the information may include information related to time.
  • the information related to time may be associated, for example, with the results of a device search, with information acquired from the device, or with information related to the UE's location. This makes it possible, for example, in a communication system, to predict information such as data at a specific time with high accuracy.
  • the notification of this information from the UE to the base station may include information about multiple devices. This makes it possible, for example, to reduce the number of times scheduling is performed for the UE.
  • the PUSCH may be used for notifying the base station of information related to the device from the UE. This makes it possible, for example, to avoid complexity in the communication system.
  • RRC signaling may be used for the notification. This makes it possible, for example, for the UE to notify the base station of a large amount of information.
  • MAC signaling may be used for the notification. This makes it possible, for example, for the UE to notify the base station of the information quickly.
  • L1/L2 signaling may be used for the notification. This makes it possible, for example, for the UE to notify the base station of the information even more quickly.
  • the communication between the UE and the device and the notification of the information from the UE to the base station may be scheduled together.
  • both schedulings may be included in the same signaling.
  • both schedulings may be included in the same DCI, or different DCIs may be included in the same signaling. This makes it possible to reduce the number of signalings from the base station to the UE, for example.
  • the UE may notify the core network of the information about the device.
  • the core network device may be, for example, an AMF.
  • AMF Access Management Function
  • NAS signaling may be used for the notification.
  • a new interface may be provided between the UE and the core network, and signaling of the interface may be used. This may reduce the amount of processing by the base station, for example.
  • the core network device may be an SMF, a PCF, a UPF, or an NWDAF (Network Data Analytics Function) (see Non-Patent Document 10). For example, by notifying the NWDAF of the information about the device, the NWDAF may quickly collect and analyze data about the device.
  • NWDAF Network Data Analytics Function
  • the communication between the UE and the device and the notification of the information from the UE to the base station may be scheduled separately.
  • both types of scheduling may be performed using different signaling. This, for example, can avoid complexity in the communication system.
  • a scheduling request from the UE to the base station for communication between the UE and the device, and a scheduling request from the UE to the base station for notifying the base station of the above-mentioned information may be made together. For example, resources indicating that both are scheduling requests may be allocated and used. This makes it possible to reduce the amount of signaling from the UE to the base station, for example.
  • a scheduling request from the UE to the base station for communication between the UE and the device and a scheduling request from the UE to the base station for notifying the base station of the above-mentioned information may be made separately. This makes it possible to avoid, for example, complexity in the communication system.
  • Information necessary for communication between a UE and a device may be determined in advance.
  • the information may be set in advance in the communication system, or may be set for each PLMN, for each NPN (Non-Public Network), for each tracking area, for each RNA, for each cell, for each UE, or for each device.
  • the information may be set for each communication service.
  • the communication service may be, for example, eMBB (enhanced Mobile Broadband), URLLC (Ultra-Reliability Low Latency Communication), or mMTC (massive Machine Type Communication).
  • the communication service may be determined depending on the application, for example, asset tracking, entrance/exit management, or other applications.
  • the information (A) above may include information indicating whether or not the communication system supports communication between the UE and the device.
  • the UE may use this information to decide whether or not to connect to a base station under the communication system. This allows, for example, the UE to quickly ascertain whether or not communication with the device can be performed.
  • the information (B) above may include, for example, information regarding standards for communication between the UE and the device that can be supported in the communication system.
  • standards may include, for example, standards related to the air interface (e.g., ISO/IEC 18000 series).
  • the UE may use the information (B) above to decide whether or not to connect to a base station under the communication system. This allows, for example, the UE to quickly grasp standards that can be used for communication with the device.
  • the information (B) above may include, for example, information regarding the interface standard between the UE and the network that can be supported in the communication system.
  • the standard may include, for example, LLRP (Low Level Reader Protocol) (Non-Patent Document 36), ALE (Application Level Event) (Non-Patent Document 37), or other interface standards.
  • the UE may use the information (B) above to decide whether or not to connect to a base station under the communication system. This allows, for example, the UE to quickly grasp the interface between the UE and the network that can be used in connection with communication with the device.
  • the information (C) above may include, for example, information on a supportable frequency, information on a supportable time resource, or information on a supportable transmission power.
  • the information on a supportable frequency may include, for example, the information (2-1) above.
  • the information on a supportable time resource may include, for example, the information (2-2) above, information on a period, or information on a time interval.
  • the information on the period may include, for example, information on a period of a timing that can be allocated to communication between a UE and a device.
  • the information on the time interval may include, for example, information on a time interval that can be allocated to communication between a UE and a device.
  • the information on the period and/or the information on the time interval may be given on a radio frame basis, a subframe basis, a slot basis, a symbol basis, a predetermined time unit (e.g., microseconds), or a combination of the above.
  • the information on the supportable power consumption may include, for example, the information (2-4) above, or information on the maximum power consumption of the UE that can be supported in the communication system.
  • the maximum power consumption of the UE mentioned above may be the power consumption related to communication between the UE and the device.
  • the information necessary for communication between the UE and the device may be reported or notified from the base station to the UE.
  • the base station may include the information in system information and report or notify the information to the UE.
  • the base station may notify the UE of the information individually.
  • RRC signaling, MAC signaling, or L1/L2 signaling may be used for the notification from the base station to the UE.
  • the information may be notified from the core network to the UE.
  • NAS signaling may be used for the notification.
  • the UE may notify the base station of information necessary for communication between the UE and the device.
  • RRC signaling may be used for the notification from the UE to the base station.
  • RRC setup request RRCSetupRequest
  • RRC recovery request RRC recovery request
  • MAC signaling or L1/L2 signaling may be used for the notification. This allows, for example, the UE to quickly notify the base station of the information.
  • the UE may notify the information by including it in the UE capabilities.
  • the UE may notify the core NW of the information.
  • NAS signaling may be used for this notification.
  • the information notified by the UE may include the information (A) to (D) described above.
  • it may include information indicating which of the information (A) to (D) described above the UE can support.
  • the base station and/or core network may use the information to determine settings related to communication between the UE and the device. This makes it possible, for example, to execute communication between the UE and the device.
  • the information required for communication between the UE and the device may be transmitted and received between the UE and the base station during the UE registration process or during the TAU process. This makes it possible to reduce the amount of signaling in the communication system, for example.
  • the base station may notify the UE of the settings related to the communication between the UE and the device.
  • RRC signaling may be used for the notification.
  • the RRC signaling may be performed using RRC setup (RRCSetup). This allows, for example, the base station to perform settings related to the communication between the UE and the device for a UE in the RRC_IDLE state.
  • RRC signaling may use RRC recovery (RRCResume) signaling. This allows, for example, the base station to perform settings related to the communication between the UE and the device for a UE in the RRC_INACTIVE state.
  • the RRC signaling may use RRC reconfiguration (RRCReconfiguration) signaling.
  • the base station may perform settings related to the communication between the UE and the device for a UE in the RRC_CONNECTED state.
  • the notification may be made using MAC signaling or L1/L2 signaling. This allows, for example, the base station to quickly notify the UE of the setting.
  • the settings notified from the base station to the UE may include information similar to (A) to (D) above.
  • information regarding the standard used for communication between the UE and the device may be included
  • information regarding the resources used for communication between the UE and the device may be included.
  • the settings may include the information from (1) to (8) above.
  • FIG. 11 shows an example of a scheduling operation from a base station to a UE regarding communication between the UE and a device.
  • scheduling from the base station to the UE is performed dynamically.
  • FIG. 11 shows a case where scheduling between the UE and the device and scheduling between the UE and the base station are performed using different signaling.
  • the base station notifies the UE of information necessary for communication between the UE and the device.
  • the notification may be performed, for example, by using system information.
  • the information may include, for example, the above-mentioned information (A) to (D).
  • the information may be multiple pieces of information.
  • the information may include a list of the above-mentioned (A) to (D).
  • the UE notifies the base station of information on settings for communication between the UE and the device that the UE can support.
  • the notification may be performed using RRC signaling, for example, signaling of an RRC setup request (RRCSetupRequest), or signaling of an RRC recovery request (RRCResumeRequest).
  • the information may include, for example, the above-mentioned information (A) to (D).
  • the information may be multiple.
  • the information may include a list of the above-mentioned (A) to (D) that the UE can support.
  • the base station notifies the UE of information on the setting to be used between the UE and the device.
  • the notification may be performed using RRC signaling, for example, RRC setup (RRCSetup) signaling, RRC recovery (RRCResume) signaling, or RRC reconfiguration (RRCReconfiguration) signaling.
  • the information may include, for example, information similar to the above (A) to (D).
  • information on the standard used for communication between the UE and the device may be included
  • information on the resources used for communication between the UE and the device may be included.
  • the setting may include the above information (1) to (8).
  • the UE uses the information notified in step ST1109 to set up communication between its own UE and the device.
  • the UE notifies the base station of the completion of the setting.
  • RRC signaling for example, RRC setup completion (RRCSetupComplete) signaling may be used, RRC recovery completion (RRCResumeComplete) signaling may be used, or RRC reconfiguration completion (RRCReconfigurationComplete) signaling may be used.
  • step ST1121 shown in FIG. 11 the UE makes a scheduling request to the base station.
  • the request is a scheduling request related to communication between the UE and a device.
  • resources different from those in the scheduling request for communication between the UE and the base station may be used.
  • the base station notifies the UE of a scheduling grant.
  • the grant is a scheduling grant related to communication between the UE and the device.
  • the scheduling grant may include the information shown in (1) to (8) above.
  • step ST1125 shown in FIG. 11 the UE transmits a signal to the device.
  • the transmission in step ST1125 may be performed using the scheduling grant notified in step ST1123.
  • the UE transmits a signal to the device to search for the device.
  • step ST1127 shown in FIG. 11 the device transmits the response of step ST1125 to the UE.
  • the response may include information about the identifier of the device itself, or may include information about the services supported by the device itself.
  • the device may be emitting radio waves to the UE.
  • the device may perform the transmission of step ST1127 using radio waves from the UE.
  • the emission of radio waves from the UE to the device and the transmission of a signal from the device to the UE in step ST1127 may be performed using the scheduling grant of step ST1123.
  • the UE obtains device information using step ST1127.
  • the UE may measure the received signal in step ST1127.
  • the measurement may be, for example, a measurement of the received power, a measurement of the SINR, or a measurement of the error rate.
  • step ST1131 shown in FIG. 11 the UE makes a scheduling request to the base station.
  • the request in step ST1131 is a scheduling request related to communication between the UE and the base station.
  • resources different from those in the scheduling request for communication between the UE and the device may be used.
  • step ST1133 shown in FIG. 11 the base station notifies the UE of a scheduling grant.
  • the grant in step ST1133 is a scheduling grant related to uplink transmission from the UE to the base station.
  • the UE transmits an uplink signal to the base station.
  • the uplink signal may include information acquired in step ST1127, such as information regarding the identifier of the searched device, or may include device search results, such as information regarding the number of searched devices, or may include information regarding the measurement results of the received signal.
  • the scheduling request for step ST1125 and the scheduling request for step ST1127 are performed using the same signaling in step ST1121, but they may be performed using different signaling. This makes it possible to flexibly respond to, for example, fluctuations in the radio wave environment in the communication system.
  • Step ST1125 may include information identifying the device from which data is to be read (e.g., an identifier), or may include information related to the data to be read (e.g., the type of data).
  • Step ST1127 may include information identifying the device, data of the own device, or may include information related to the type of data of the own device.
  • Step ST1135 may include information identifying the device, data of the device, information related to the type of data of the device, or may include measurement results of the received signal by the UE. This enables, for example, the communication system to read data from the device.
  • Step ST1125 may include information identifying the device to which data is to be written (e.g., an identifier), or may include information related to the data to be written (e.g., data content, data type).
  • Step ST1127 may include information identifying the device, or may include information related to the result of writing the data (e.g., whether writing was successful or not, content of the written data).
  • Step ST1135 may include information identifying the device, or may include information related to the result of writing the data (e.g., whether writing was successful or not, content of the written data), or may include the result of measurement of the signal received by the UE. This enables, for example, the communication system to write data to the device.
  • Scheduling of communication between the UE and the device and scheduling between the UE and the base station may be performed together. For example, both types of scheduling may be performed using the same scheduling grant.
  • the above scheduling may be used, for example, when the frequency of an uplink signal is used for communication between the UE and the device. This makes it possible, for example, to reduce the amount of signaling between the base station and the UE.
  • FIG. 12 shows a first alternative example of a scheduling operation from a base station to a UE regarding communication between the UE and a device.
  • scheduling from the base station to the UE is performed dynamically.
  • FIG. 12 shows a case where scheduling between the UE and the device and scheduling between the UE and the base station are performed using the same signaling.
  • the same step numbers are used for processing similar to that in FIG. 11, and common explanations are omitted.
  • Steps ST1105 to ST1111 shown in FIG. 12 are the same as those in FIG. 11.
  • the UE makes a scheduling request to the base station.
  • the request is a scheduling request related to communication between the UE and the device and communication between the UE and the base station.
  • the scheduling request in step ST1221 may include information indicating that the scheduling request is for communication between the UE and the base station and information indicating that the scheduling request is for communication between the UE and the device. As another example, none of the above information may be included.
  • the base station notifies the UE of a scheduling grant.
  • the grant is a scheduling grant related to both communication between the UE and the device and communication between the UE and the base station.
  • the scheduling grant may include the information shown in (1) to (8) above.
  • both types of scheduling may be included in the same DCI, or different DCIs may be included in the same signaling.
  • Steps ST1125 to ST1135 shown in FIG. 12 are the same as those in FIG. 11.
  • the transmissions in steps ST1125 to ST1135 may be performed using the scheduling grant in step ST1223.
  • a configured grant may be used for scheduling communication between a UE and a device.
  • FIG. 13 shows a second example of a scheduling operation from a base station to a UE for communication between the UE and a device.
  • FIG. 13 shows an example in which a configured grant of type 2 is used for scheduling from a base station to a UE.
  • both the scheduling between the UE and the device and the scheduling between the UE and the base station are performed using a scheduling grant of type 2.
  • the scheduling between the UE and the device and the scheduling between the UE and the base station are performed using different signaling.
  • the same processes as in FIG. 11 are assigned the same step numbers, and common explanations are omitted.
  • Steps ST1105 and ST1107 shown in FIG. 13 are the same as those in FIG. 11.
  • step ST1309 shown in FIG. 13 the base station notifies the UE of information regarding the settings to be used between the UE and the device.
  • Step ST1309 may include information similar to that of step ST1109 in FIG. 11.
  • Step ST1309 may include information regarding grants already configured for the UE.
  • the information regarding the already configured grants may include, for example, the above-mentioned information (1) to (8).
  • the UE uses the information notified in step ST1309 to configure communications between the UE and the device, and between the UE and the base station.
  • Step ST1111 shown in FIG. 13 is the same as in FIG. 11.
  • step ST1323 shown in FIG. 13 the base station notifies the UE of a scheduling grant.
  • the grant is a configured grant of type 2.
  • the scheduling grant notified in step ST1323 is a scheduling grant related to communication between the UE and the device.
  • the scheduling grant may include the information shown in (1) to (8) above.
  • a scheduling request may not be made from the UE to the base station.
  • Steps ST1125 and ST1127 shown in FIG. 13 are the same as those in FIG. 11.
  • step ST1333 shown in FIG. 13 the base station notifies the UE of a scheduling grant.
  • the grant is a configured grant of type 2.
  • the scheduling grant notified in step ST1333 is a scheduling grant related to communication between the UE and the base station.
  • Step ST1135 shown in FIG. 13 is the same as in FIG. 11.
  • step ST1323 and step ST1333 may be included in step ST1309. This makes it possible to reduce the number of times signaling is performed from the base station to the UE, for example.
  • Communication between the UE and the device may be scheduled at the timing of the on-duration of DRX.
  • the above-mentioned DRX may be, for example, C-DRX (Connected mode-DRX). This makes it possible, for example, to reduce the power consumption of the UE.
  • communication between the UE and the device may be scheduled at the timing of the inactive DRX. This makes it possible, for example, to quickly execute communication between the UE and the device.
  • Retransmission may be performed in communication between a UE and a device.
  • the retransmission may be performed, for example, using a retransmission request from the communication partner, or may be performed using information indicating that the communication partner was unable to correctly process the received signal. This may improve the reliability of communication between a UE and a device, for example.
  • the UE may make a scheduling request to the base station for resources to be used for retransmission. This enables, for example, flexible scheduling in communications between the UE and the device. As another example, the UE may not make a scheduling request to the base station for resources to be used for retransmission.
  • the base station may schedule the UE including resources related to retransmission.
  • the scheduling from the base station to the UE may include information indicating that resources related to retransmission are included.
  • the UE may use the information to perform retransmission in communications with the device. This makes it possible, for example, to reduce the amount of signaling between the UE and the device.
  • HARQ may not be used in the communication between the UE and the device. This can, for example, avoid complexities in the communication between the UE and the device.
  • HARQ may be used for communication between the UE and the device. This can improve the reliability of communication between the UE and the device, for example.
  • Repetition may not be used in the communication between the UE and the device. This can, for example, avoid complexities in the communication between the UE and the device.
  • repetition may be used in communication between a UE and a device. This makes it possible to prevent an increase in power consumption of the UE while improving the reliability of communication between the UE and the device, for example.
  • the UE may notify the base station of information regarding whether retransmission in communication with the device is supported, information regarding whether HARQ is supported, or information regarding whether repetition is supported.
  • the notification from the UE to the base station may be performed, for example, using UE capabilities, or may use RRC signaling, such as signaling of an RRC setup request (RRCSetupRequest) or signaling of an RRC recovery request (RRCResumeRequest). This allows, for example, the base station to quickly determine whether the UE supports HARQ and/or whether the UE supports repetition.
  • the base station may notify the UE of information regarding whether or not retransmission is used in communication with the device, may notify the UE of information regarding whether or not HARQ is used, or may notify the UE of information regarding whether or not repetition is used.
  • the information notified from the base station to the UE may be included in, for example, the settings related to communication between the UE and the device notified to the UE by the base station described above. This allows, for example, the UE to quickly grasp whether or not retransmission is used, whether or not HARQ is used, and/or whether or not repetition is used in communication with the device.
  • the configured grant may be, for example, a configured grant used for scheduling between a UE and a device.
  • the base station may notify the UE of information regarding activation/deactivation of the configured grant.
  • the notification may be made using RRC signaling, MAC signaling, or L1/L2 signaling. This enables, for example, flexible scheduling in a communication system.
  • the device search disclosed in the first embodiment may be device confirmation or device detection.
  • This embodiment 1 enables scheduling of communication between a UE and a device, thereby enabling communication between a UE and a device in a communication system.
  • Embodiment 2 In order to allow communications over the air interface between a device and a UE or a gNB to coexist with communications over the air interface (Uu) between a UE and a gNB and/or communications over the air interface (PC5) between UEs, it is necessary to reduce interference to other UEs and/or base stations from communications between the device and a UE or a gNB.
  • Uu air interface
  • PC5 air interface
  • the UE may control the power in the communication between the UE and the device.
  • the UE may use the power of the signal received from the device to determine the power to be used in the communication between the UE and the device.
  • the UE may increase the transmission power from the UE to the device.
  • the UE may increase the transmission power from the UE to the device. This makes it possible to improve the reliability of communication between the device and the UE, for example.
  • the UE may reduce the transmission power from the UE to the device. For example, if the device uses backscatter communication, the UE may reduce the transmission power from the UE to the device. This makes it possible to reduce the power consumption of the UE, for example.
  • the UE may measure the received power from the device for each transmission beam.
  • the signal for beam derivation disclosed in the first embodiment may be used for the transmission beam. This allows, for example, the UE to determine the optimal beam for communication with the device.
  • a target reception quality for the UE may be set.
  • the target reception quality may be, for example, based on received power or SINR.
  • the setting may be set for each UE, for multiple UEs, for each cell, for multiple cells, for each PLMN, for each NPN, or may be determined uniformly in the communication system.
  • the maximum power of the UE may be set.
  • the maximum power may be the maximum power in communication between the UE and a device, the maximum power in communication between the UE and a base station, the maximum power in communication between the UE and another UE, or the maximum power in the aforementioned multiple communication.
  • the target reception quality and/or maximum power of the UE may be determined by the UE itself, by the base station, by the core network device, or may be predetermined by a standard.
  • the base station may report or notify the UE of the target reception quality and/or maximum power of the UE.
  • the report or notification from the base station to the UE may use system information, RRC signaling, MAC signaling, or L1/L2 signaling.
  • the core network device may notify the UE of the information.
  • NAS signaling may be used to notify the information.
  • the base station and/or core network device may notify the UE of information regarding the desired reception power of the device.
  • the desired reception power may be, for example, the reception power at which the device can operate.
  • the reception power at which the device can operate may be, for example, the reception power at which the device can execute data processing (e.g., reading, writing, calculation) of the device itself, or the reception power at which the device can transmit a signal to the UE.
  • a plurality of desired reception powers may be provided.
  • the desired reception power may include a reception power at which the device can execute data processing (e.g., reading, writing, calculation) of the device itself, and a reception power at which the device can transmit a signal to the UE.
  • the desired reception power may be predetermined by a standard.
  • the UE may use information regarding the desired reception power to determine the transmission power for the device. This makes it possible to ensure, for example, communication quality between the UE and the device.
  • the base station controls the power in communication between the UE and the device.
  • the UE notifies the base station of information related to the received power from the device.
  • the UE may notify the base station of the transmission power of the UE.
  • the transmission power may be, for example, the transmission power used in communication between the UE and the device. This allows, for example, the base station to know the transmission power of the UE, which can reduce interference with other devices in the communication system.
  • the UE may request the base station to increase or decrease the transmission power of the UE. This makes it possible, for example, to reduce the amount of signaling from the UE to the base station.
  • UCI may be used to notify the base station of the information from the UE. This allows, for example, the notification from the UE to the base station to be executed quickly.
  • MAC signaling may be used for the notification. This allows, for example, the reliability of the notification to be improved by HARQ control.
  • RRC signaling may be used for the notification. This allows, for example, the amount of information included in the notification to be increased. The same may be true for the signaling used for the request from the UE to the base station.
  • the base station determines the power for communication between the UE and the device.
  • the base station may use the above-mentioned notification and/or request to determine the power for communication between the UE and the device.
  • the base station notifies the UE of information related to the UE's transmission power.
  • the notification may include information indicating communication between the UE and the device, information indicating communication between the UE and the base station, or information indicating communication between the UE and another UE. This allows, for example, the UE to quickly ascertain the communication partner for which the notified transmission power is to be applied.
  • the notification may be performed, for example, by using the notification of the information (2-4) disclosed in the first embodiment. This makes it possible, for example, to avoid complexity in the communication system.
  • Dedicated signaling may be provided and used to notify the information from the base station to the UE. This makes it possible, for example, to flexibly execute power control.
  • the base station may determine whether or not to perform repetition.
  • the base station may notify the UE of information regarding repetition.
  • the notification may include information regarding the communication in which the repetition is performed (e.g., communication from the UE to the device, communication from the device to the UE), information regarding the presence or absence of repetition, information regarding the number of repetitions, information regarding the power in each repetition, information about the device (e.g., an identifier), or a combination of the above.
  • the notification from the base station to the UE may be performed, for example, using the notification of information (1) to (8) disclosed in the first embodiment. This makes it possible to avoid, for example, complexity in the communication system.
  • Dedicated signaling may be provided and used to notify the information from the base station to the UE. This makes it possible, for example, to flexibly perform repetition control.
  • the UE and/or device may perform repetition using the notification. This makes it possible, for example, to reduce the transmission power of the UE while ensuring the reliability of communications between the UE and the device.
  • the target reception quality of the UE may be set and/or the maximum power of the UE may be set.
  • Setting and/or notifying the target reception quality and/or maximum power of the UE may be similar to the method disclosed in the above-mentioned solution.
  • Transmissions from the UE to the device may include information about the UE's transmit power. This allows the device to measure the path loss between the UE, for example.
  • the transmission of a signal from the device to the UE may include information about the received power of the signal from the UE.
  • the UE may use this information to derive the path loss between the UE and the device. This may, for example, reduce the amount of signaling from the UE to the device.
  • the signal transmitted from the device to the UE may include information regarding the received power of each transmission beam from the UE, or may include information regarding the received power of a beam derived signal transmitted from the UE. This allows, for example, the UE to determine the optimal beam for communication with the device.
  • a signal transmitted from the device to the UE may include information about the path loss derived by the device. This may, for example, reduce the amount of processing in the UE.
  • the initial transmission power of the UE may be set.
  • the initial transmission power may be, for example, the initial transmission power after starting a connection with the base station, the transmission power in the initial communication with the communication partner device, or the communication a predetermined time after the last communication with the device.
  • the initial transmission power of the UE may be set for communication between the UE and the device, for communication between the UE and the base station, for communication between the UE and another UE, or through the multiple communications mentioned above.
  • the initial transmission power may be reported or notified to the UE by the base station in system information, may be determined by the base station and notified to the UE individually, may be preset in the SIM, or may be determined in advance by a standard.
  • the base station may notify the UE by including information regarding the initial transmission power in signaling for transitioning the UE from the RRC_CONNECTED state to the RRC_IDLE state, or the base station may notify the UE by including the information in signaling for transitioning the UE from the RRC_CONNECTED state to the RRC_INACTIVE state.
  • the initial transmission power may be determined by the UE using the received power from the device.
  • the received power from the device may be, for example, the received power of a signal due to backscattering of radio waves from another base station or another UE.
  • the above-mentioned report or notification may include information indicating communication between the UE and a device, may include information indicating communication between the UE and a base station, or may include information indicating communication between the UE and another UE. This allows, for example, the UE to quickly ascertain the communication partner that is the target of the notified transmission power.
  • the base station may prioritize communication between the UE and the device over transmissions from other UEs.
  • the transmissions may be from the other UE to the base station, from the other UE to the device, or from the other UE to yet another UE.
  • the base station may instruct the UE to stop transmission.
  • the instruction may include, for example, information on the reason for the stop.
  • the information on the reason for the stop may include, for example, information on the communication between the UE and the device, or information on the resources (e.g., frequency, time) used for the communication.
  • the instruction may be included, for example, in the DCI to the other UE.
  • the other UE may use the instruction to stop transmission from its own UE.
  • the transmissions stopped by the other UE may be the entire scheduled transmissions, or only the resources that overlap with the communication between the UE and the device. This makes it possible to prevent interference from other UEs to a UE that communicates with a device.
  • a base station may notify other base stations of information regarding resources scheduled by the base station for communication between a UE and a device.
  • the information may include, for example, information regarding communication between a UE and a device, or information regarding the priority of the communication.
  • the other base station may stop transmission and reception with a UE under the control of the base station upon receipt of the notification. This makes it possible to prevent interference from other base stations with a UE communicating with a device, for example.
  • This embodiment 2 enables transmission power control in communication between a UE and a device, and as a result, it becomes possible to suppress interference caused to other UEs and/or base stations by communication between a device and a UE or a gNB.
  • Embodiment 3 In a communication system, communication between a UE and a device may be supported, and sidelink communication may be supported. However, the coexistence of sidelink communication and communication between a UE and a device in the same UE is not disclosed. As a result, there is a risk of malfunction in the UE.
  • sidelink communication may be prioritized over communication with the device.
  • a UE performing sidelink communication may disable communication with the device.
  • a UE capable of performing sidelink communication may disable communication with the device (e.g., does not have the capability, cannot be configured, cannot transmit or receive), and a UE configured for sidelink communication may disable communication with the device (e.g., cannot be configured, cannot transmit or receive). This makes it possible to prevent, for example, excessive power consumption by the UE.
  • a UE performing sidelink communication may be able to communicate with a device.
  • a UE capable of performing sidelink communication may be able to communicate with a device (e.g., has the capability, can be configured), and a UE configured for sidelink communication may be able to communicate with a device (e.g., can be configured, can send and receive). This allows, for example, a UE to search for devices over a wide area.
  • the UE performing sidelink communication may be, for example, a UE that is not involved in relaying. As another example, it may be a UE that is involved in relaying.
  • the UE that is involved in relaying may be, for example, a remote UE (see Non-Patent Document 26, Section 6.3.12) or a relay UE (see Non-Patent Document 26, Section 6.3.12).
  • the aforementioned relay may be, for example, a UE-to-NW relay or a UE-to-UE relay.
  • the scheduling between the device and the UE may be performed by the base station.
  • the scheduling may be performed by a relay UE.
  • the scheduling may be performed by a remote UE.
  • the UE performing sidelink communication may be, for example, a UE that is not involved in relaying.
  • the scheduling may be performed by the UE itself that communicates with the device.
  • communication with a device may be prioritized over sidelink communication.
  • a UE communicating with a device may disable sidelink communication.
  • a UE capable of communicating with a device may disable sidelink communication (e.g., does not have the capability, cannot be configured, cannot transmit or receive), and a UE configured for communication with a device may disable sidelink communication (e.g., cannot be configured, cannot transmit or receive). This makes it possible to prevent, for example, excessive power consumption by the UE.
  • a UE that communicates with a device may enable sidelink communication.
  • a UE that is capable of communicating with a device may enable sidelink communication (e.g., has the capability, can be configured), and a UE that is configured for communication with a device may enable sidelink communication (e.g., can be configured, can send and receive).
  • sidelink communication e.g., can be configured, can send and receive.
  • the setting may be determined for each PLMN, for each NPN, for each tracking area, for each RNA, for each base station, for each cell, or for each UE.
  • the setting may be performed by the core NW device or the base station.
  • the setting may be set in advance in the SIM.
  • the core NW may notify the UE of the setting.
  • the notification may be performed, for example, using NAS signaling.
  • the base station may report or notify the UE of the setting.
  • the notification may be performed, for example, using system information.
  • the notification may be performed using RRC signaling, MAC signaling, or L1/L2 signaling.
  • the setting that was performed first may be prioritized between communication with the device and sidelink communication.
  • a UE that has been configured for communication with the device may disable sidelink communication
  • a UE that has been configured for sidelink communication may disable communication with the device. This makes it possible to avoid, for example, complexity in the communication system.
  • the later setting may be prioritized between communication with the device and sidelink communication.
  • sidelink communication may be performed in a UE configured for communication with a device, and communication with the device may be performed in a UE configured for sidelink communication. This, for example, can improve the flexibility of the communication system.
  • the setting may be determined for each PLMN, for each NPN, for each tracking area, for each RNA, for each base station, for each cell, or for each UE.
  • the setting may be performed by the core NW device or the base station.
  • the setting may be set in the SIM in advance.
  • the core NW may notify the UE of the setting.
  • the notification may be performed, for example, using NAS signaling.
  • the base station may report or notify the UE of the setting.
  • the notification may be performed, for example, using system information.
  • the notification may be performed using RRC signaling, MAC signaling, or L1/L2 signaling.
  • a parameter may be provided regarding whether or not simultaneous communication between the device and sidelink communication is possible.
  • the parameter may be included in the UE capabilities, for example.
  • the UE may notify the base station of the parameter.
  • the resources to be used for communication with the device may be determined in advance.
  • Candidates for resources to be used for communication with the device may be determined in advance.
  • the candidates may be the same as the resource pool in the side link (see Non-Patent Document 2), for example. As another example, the candidates may be different from the resource pool in the side link. There may or may not be an overlap between the candidates and the resource pool in the side link.
  • the candidates may be part of the resource pool in the side link, or the candidates may include the resource pool in the side link.
  • Information regarding the availability of communication with the device may be assigned to each resource constituting the resource pool in the side link.
  • UEs outside the range of a base station may be able to communicate with the device. This allows, for example, communication between the UE and the device to be performed over a wide range.
  • a UE that is out of range of a base station may be unable to communicate with the device. This can, for example, avoid complexities in the communication system.
  • the setting may be included, for example, in a policy or parameter for UE-device communication.
  • the core network device may transmit information about the setting to the base station.
  • the notification from the core network device to the base station may be, for example, a notification of a policy or parameter for UE-device communication.
  • the core network device or base station may transmit information about the setting to the UE.
  • the notification from the core network device or base station to the UE may be, for example, a notification of a policy or parameter for UE-device communication.
  • information about the setting may be transmitted from the AF to the UE via the PCF, AMF, and gNB as a policy or parameter for UE-device communication.
  • a UE that supports communication with a device may be provided with a policy or parameter for UE-device communication from the core network device.
  • a UE that supports communication with a device can obtain information about the setting. It may also be possible to associate a service with the settings, for example.
  • the UE may check the frequency resource usage status of other UEs and/or base stations.
  • the check may be performed, for example, by a receiving operation by the UE on the frequency resource.
  • the frequency resource may be, for example, a frequency resource that the UE intends to use for communication with a device.
  • the check may be performed, for example, on other UEs when the UE is out of range of the base station.
  • the UE may not communicate with a device on a frequency resource used by the other UE and/or base station. This may, for example, reduce interference to other UEs and/or base stations.
  • This embodiment 3 enables the UE to support sidelink communication and communication between the UE and the device, thereby making it possible to prevent malfunctions in the UE.
  • Embodiment 4 When incorporating a device into a mobile communication system, communication is required between the device and a UE and/or a base station. However, details of information transmitted and received in the communication are not disclosed. As a result, a problem occurs in that the device cannot communicate with the UE and/or the base station, and the device cannot be incorporated into the mobile communication system.
  • the UE transmits a signal to the device.
  • the signal may be, for example, a notification regarding a search for the device, a request to write information to the device, or a request to read information from the device.
  • the information contained in the signal is disclosed as follows: (a) to (k).
  • the information in (a) above may be, for example, a notification regarding search, confirmation, and/or detection of the device, a request to write information to the device, or a request to read information from the device.
  • the information (a) above may be, for example, a pilot signal.
  • the pilot signal may be defined, for example, by a standard.
  • the device may use the information to recognize a signal from the UE. This allows, for example, the device to receive a signal from the UE.
  • the information in (b) above may be, for example, information indicating a notification regarding a search, confirmation, and/or detection of a device, information indicating a request to write information to a device, or information indicating a request to read information from a device.
  • the device may use the information to determine the type of signal from the UE.
  • the information (a) above may include the information (b) above.
  • a pilot signal may be provided for each type of communication. This allows, for example, a device to quickly determine the type of signal from a UE.
  • the information (c) above may be, for example, the RNTI of the UE.
  • the identifier may be an identifier assigned as the leader of the device. This allows, for example, the device to quickly recognize the leader UE.
  • the information in (d) above may include the entire device identifier, or may include part of the device identifier. It may include information indicating that the device corresponding to that identifier or part of the identifier is a communication target, or may include information indicating that the device is not a communication target. As another example, the information in (d) above may include information that all devices are targets. The device may use this information to determine whether or not it is a communication target for the signal from the UE. This makes it possible, for example, to prevent responses from devices that are not communication targets.
  • the device may use the information in (e) above to update the information it holds. This makes it possible, for example, to remotely update the information held by the device.
  • the information in (e) above may be encrypted. For example, it may be encrypted using the identifier of the device. In this case, the signal from the UE to the device may not include the information in (d) above. The device may decrypt the information in (e) above using its own device identifier. This makes it possible to improve the security of communications between the UE and the device, for example.
  • the information (f) above may include, for example, information on a device identifier, information on the type of data held by the device (e.g., sensor measurement results), or information on time.
  • the time-related information may be associated with the data held by the device.
  • the device may use the information to determine the information to send to the UE. This, for example, eliminates the need for the device to send all of the information it holds, and as a result, the efficiency of the communication system, for example, the efficiency of resource utilization, may be improved.
  • the information (g) above may be, for example, the time from the start of transmission of the signal from the UE to the device to the start of the response from the device to the UE, or the time from the end of transmission of the signal from the UE to the device to the start of the response from the device to the UE.
  • the device may use this information to respond to the UE. This allows, for example, the device to transmit a response to the UE at an appropriate time.
  • the information (h) above may be, for example, a code for detecting an error in the signal from the UE to the device or for correcting an error.
  • the information (h) above may be, for example, a CRC bit or a parity bit. This allows, for example, the device to quickly determine whether or not there is an error in the signal from the UE.
  • the information in (i) above may include information regarding the transmission power of the signal from the UE to the device.
  • the device may measure the reception power of the signal from the UE to the device. This allows the device to measure, for example, the path loss of the signal from the UE.
  • the information (j) above may include, for example, information (e.g., an identifier) for identifying a service related to the transmission of a signal from the UE to the device, or may include information for identifying a service supported by the UE.
  • the information for identifying a service may be, for example, eMBB (enhanced Mobile Broadband), URLLC (Ultra-Reliability Low Latency Communication), or mMTC (massive Machine Type Communication).
  • the communication service may be determined by the application, for example, asset tracking, entrance/exit management, or other applications.
  • the device may use the information (j) above to determine whether to respond to the UE. For example, the device may not respond to a device search from a UE that does not correspond to a service supported by the device. This allows, for example, the UE to prevent unnecessary device searches and reduce interference with other UEs, etc.
  • the device transmits a signal to the UE.
  • the signal may be, for example, a response to a signal transmitted from the UE to the device.
  • the information (a) above may be, for example, a response to searching, confirming, and/or detecting the device, a response to writing information to the device, or a notification regarding the results of reading information from the device itself.
  • the information (a) above may be, for example, a pilot signal.
  • the pilot signal may be defined, for example, by a standard.
  • the UE may use the information to recognize a signal from the device. This allows, for example, the UE to receive a signal from the device.
  • the information (i) above may be, for example, information indicating that it is a response to a search, confirmation, and/or detection of the device, information indicating that it is a response to writing information to the device, information indicating that it is a transmission of data from the device itself, or information indicating that it is a notification regarding the result of reading information from the device itself.
  • the UE may use this information to determine the type of signal from the device.
  • the information (a) above may include the information (b) above.
  • a pilot signal may be provided for each type of communication. This allows, for example, the UE to quickly determine the type of signal from the device.
  • the information (c) above may be the same as the information (c) above.
  • the UE may use this information to determine that it is a communication target of a signal from a device. This makes it possible to prevent, for example, malfunction of UEs that are not communication targets.
  • the information (e) above may be, for example, the same as the information (d) above.
  • the information may be, for example, the entire identifier of the device. This allows, for example, the UE to quickly recognize the source device.
  • the information (e) above may be, for example, information indicating that a signal from the UE to the device was received correctly, or information indicating that the signal was not received correctly. Whether or not the signal was received correctly may be determined, for example, using the information (h) above.
  • the UE may use this information to retransmit the signal to the device. This may, for example, improve the reliability of communication between the UE and the device.
  • the information (f) above may include information written by the device itself.
  • the UE may use this information to determine whether writing to the device was performed correctly. For example, the UE may make this determination by comparing the information that the UE itself requested to be written with the information notified by the device. This makes it possible to improve the reliability of requests from the UE to write information to a device, for example.
  • the information (f) above may include information indicating whether or not the device has been able to write information to its own device.
  • the UE may use this information to determine whether or not writing of information to the device has been completed. This may, for example, reduce the size of notifications sent from the device to the UE.
  • the information (g) above may include information possessed by the device itself.
  • the information may be, for example, information read by the device itself.
  • the UE may use the information to obtain information possessed by the device.
  • the information (k) above may include information regarding the type of information possessed by the device itself.
  • the information regarding the type may be the same as the information (f) above, for example.
  • the UE may use the information regarding the type to determine whether the information notified from the device is the type of information requested by the UE itself. This may, for example, improve the reliability of reading information from the device.
  • the information (h) above may include information indicating the received power of the signal from the UE to the device.
  • the UE may use this information to ascertain the received power at the device, or to derive the path loss between the UE and the device. This makes it possible, for example, to control the power in communication between the UE and the device.
  • the information (h) above may include information indicating the path loss in communication between the UE and the device itself.
  • the device may calculate the path loss using the information (i) above transmitted from the UE. This makes it possible to reduce the amount of processing involved in the path loss calculation of the UE, for example.
  • the above-mentioned information (K) may be, for example, a code for detecting an error in the signal from the device to the UE or for correcting an error.
  • the above-mentioned information (K) may be, for example, a CRC bit or a parity bit. This allows, for example, the UE to quickly determine whether or not there is an error in the signal from the device.
  • the information (k) above may include, for example, information (e.g., an identifier) that identifies a service related to the transmission of a signal from the device to the UE, or may include information that identifies a service supported by the device.
  • the information that identifies the service may be, for example, similar to the information (j) above.
  • the UE may not notify the base station of information from a device that does not correspond to a service supported by the UE. This may make it possible to reduce the size of signaling between the base station and the UE, for example.
  • This fourth embodiment enables communication between the UE and the device, thereby making it possible to incorporate the device into the mobile communication system.
  • Embodiment 5 In the communication system, communication between a UE and a device may be supported.
  • the UE may act, for example, as a reader and/or writer with the device.
  • the base station may act as a host in the communication between the UE and the device.
  • the core NW device may act as the host.
  • the UE and the base station may each have a communication protocol between the reader/writer and the host (hereinafter, may be referred to as the RH protocol).
  • the protocol may be, for example, LLRP, ALE, or another protocol.
  • the signaling of the protocol may be encapsulated by RRC signaling.
  • Signaling for encapsulating the protocol may be provided in the RRC signaling. This makes it possible to avoid, for example, complexity in the communication system.
  • FIG. 14 is a diagram showing an example of a protocol stack between a UE and a base station (gNB) for communication between the UE and a device.
  • FIG. 14 shows an example in which the UE is the reader/writer and the base station is the host.
  • the PHY, MAC, RLC, PDCP, and RRC protocols terminate between the UE and the base station.
  • the UE and the base station each have an RH protocol, which terminates with each other.
  • the RH protocol (shown as "Reader/Writer-Host" in FIG. 14) is encapsulated by RRC signaling.
  • the RRC signaling may include RH protocol signaling.
  • the RRC signaling may include information included in the RH protocol. This allows, for example, the UE and/or the base station to quickly obtain the information included in the RH protocol.
  • FIG. 15 is a diagram showing another example of a protocol stack between a UE and a base station for communication between the UE and a device.
  • FIG. 15 shows an example in which the UE is a reader/writer and the base station is a host.
  • the PHY, MAC, RLC, PDCP, and RRC protocols terminate between the UE and the base station.
  • the RRC signaling includes information held by the RH protocol.
  • the signaling of the RH protocol may be encapsulated in MAC signaling, or the information included in the RH protocol may be included in MAC signaling.
  • MAC signaling For example, a CLIENT_REQUEST_OP message in the LLRP (see Non-Patent Document 36, Section 12.1.11) may be transmitted using MAC signaling. This allows, for example, quick signaling from the UE to the base station.
  • the signaling of the RH protocol may be encapsulated in L1/L2 signaling, or the information included in the RH protocol may be included in L1/L2 signaling. This allows, for example, even quicker signaling from the UE to the base station.
  • the core network device may act as a host in communication between the UE and the device.
  • the core network device may be, for example, an AMF.
  • the signaling of the RH protocol may be encapsulated by NAS signaling.
  • Signaling for encapsulating the protocol may be provided in the NAS signaling. This makes it possible to avoid, for example, complexity in the communication system.
  • FIG. 16 is a diagram showing an example of a protocol stack between a UE and a core network device for communication between the UE and a device.
  • the core network device is an AMF.
  • FIG. 16 shows an example in which the UE is a reader/writer and the AMF is a host.
  • the PHY, MAC, RLC, PDCP, and RRC protocols terminate between the UE and the base station.
  • the L1, L2, IP, SCTP, and NGAP protocols terminate between the base station and the AMF.
  • the UE and the AMF each have an RH protocol and terminate with each other.
  • the RH protocol is encapsulated by NAS signaling.
  • the NAS signaling may include RH protocol signaling.
  • the NAS signaling may include information included in the RH protocol. This allows, for example, the UE and/or the AMF to quickly obtain the information included in the RH protocol.
  • FIG. 17 is a diagram showing another example of a protocol stack between a UE and a core network device for communication between the UE and a device.
  • the core network device is an AMF.
  • FIG. 17 shows an example in which the UE is a reader/writer and the AMF is a host.
  • the PHY, MAC, RLC, PDCP, and RRC protocols terminate between the UE and the base station.
  • the L1, L2, IP, SCTP, and NGAP protocols terminate between the base station and the AMF.
  • the NAS protocol terminates between the UE and the AMF.
  • the NAS signaling includes information held by the RH protocol.
  • the host core network device is an AMF
  • another core network device may be the host.
  • it may be an SMF, a PCF, a UPF, or an NWDAF.
  • the connection between the core network device and the UE may be via a base station or an AMF, or may be made directly from the base station to the core network device.
  • An interface between the UE and the core network device (hereinafter, sometimes referred to as a UE-core network interface) may be provided.
  • An interface between the base station and the core network device hereinafter, sometimes referred to as a base station-core network interface) may be provided.
  • the AMF may be the core network device.
  • a protocol for the UE-core network interface may be used instead of the NAS protocol possessed by the UE and AMF, and a protocol for the base station-core network interface may be used instead of the NGAP protocol possessed by the base station and AMF. The same may be true for the example shown in FIG. 17.
  • This fifth embodiment makes it possible to support communication between UEs and devices in a communication system.
  • one or more cells are configured in one gNB.
  • it is described as a gNB or a cell, but unless otherwise specified, it may be a gNB or a cell.
  • a gNB may be an MCG or an SCG.
  • a slot is an example of a time unit for communication in a fifth generation communication system.
  • a slot may be a scheduling unit.
  • the processing described as being performed on a slot basis may be performed on a TTI basis, a subframe basis, a subslot basis, or a minislot basis.
  • the methods disclosed in the above-mentioned embodiments and their modified examples may be applied to the IAB. They may be applied to communications between an IAB donor and an IAB node. They may be applied to processing using Uu in the IAB.
  • the methods disclosed in the above-mentioned embodiments and their modified examples may be applied to communication between UEs or between a UE and a NW via a relay using SL communication.
  • the methods disclosed in the above-mentioned embodiments and their modified examples may be applied to services that use SL communication, not limited to V2X (Vehicle-to-everything) services.
  • the methods may be applied to SL communication used in a variety of services, such as proximity-based services, public safety, communication between wearable devices, and communication between devices in factories.
  • (Appendix 1) A base station compatible with a fifth-generation wireless access system; A communication terminal connected to the base station; A device connecting to the base station or the communication terminal; Including, The base station schedules communication between the device and the base station and schedules communication between the device and the communication terminal; The device communicates with the base station or the communication terminal according to a scheduling result by the base station.
  • a communication system comprising: (Appendix 2) the communication terminal controls a transmission power to the device based on a power of a signal received from the device in communication with the device; 2. The communication system according to claim 1 .
  • the communication terminal notifies the base station of at least one of a power of a received signal from the device and a power of a signal transmitted to the device; The base station controls power of a signal transmitted and received between the communication terminal and the device based on the power notified from the communication terminal.
  • the communication system according to claim 1 (Appendix 4) When the communication terminal performs sidelink communication, which is direct communication with another communication terminal, The base station schedules the sidelink communication. 4.
  • the communication system according to claim 1, (Appendix 5) The communication terminal transmits information regarding communication between the device and the communication terminal to the device; the device initiates communication with the communication terminal based on the information received from the communication terminal; 5.
  • a communication system according to claim 1, (Appendix 6) the communication terminal operates as at least one of a reader and a writer of the device; The base station acts as a host in communication between the communication terminal and the device. 6.
  • 202 Communication terminal device (mobile terminal), 210 Communication system, 213, 240-1, 240-2, 750 Base station device (NR base station, base station), 214 5G core unit, 215 Central unit, 216 Distributed unit, 217 Central unit for control plane, 218 Central unit for user plane, 219 TRP, 301, 403 Protocol processing unit, 302 Application unit, 304, 405 Encoder unit, 305, 406 Modulation unit, 306, 407 Frequency conversion unit, 307-1 to 307-4, 408-1 to 408-4 Antenna, 308, 409 Demodulation unit, 309, 410 Decoder unit, 310, 411, 526 control unit, 401 EPC communication unit, 402 other base station communication unit, 412 5GC communication unit, 521 Data Network communication unit, 522 base station communication unit, 523 user plane communication unit, 523-1 PDU processing unit, 523-2 mobility anchoring unit, 525 control plane control unit, 525-1 NAS security unit, 525-2 idle state mobility management unit, 527 session management unit

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/JP2024/004618 2023-02-14 2024-02-09 通信システム Ceased WO2024171988A1 (ja)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP24756833.0A EP4668992A1 (en) 2023-02-14 2024-02-09 Communication system
JP2025501130A JPWO2024171988A1 (https=) 2023-02-14 2024-02-09
CN202480010628.1A CN120642546A (zh) 2023-02-14 2024-02-09 通信系统

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2023-020840 2023-02-14
JP2023020840 2023-02-14

Publications (1)

Publication Number Publication Date
WO2024171988A1 true WO2024171988A1 (ja) 2024-08-22

Family

ID=92421910

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2024/004618 Ceased WO2024171988A1 (ja) 2023-02-14 2024-02-09 通信システム

Country Status (4)

Country Link
EP (1) EP4668992A1 (https=)
JP (1) JPWO2024171988A1 (https=)
CN (1) CN120642546A (https=)
WO (1) WO2024171988A1 (https=)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019031085A1 (ja) * 2017-08-09 2019-02-14 ソニー株式会社 通信装置及び通信方法
WO2019149341A1 (en) * 2018-01-30 2019-08-08 Huawei Technologies Co., Ltd. Techniques for location estimation using rfid tags
WO2021026571A1 (en) * 2019-08-08 2021-02-11 Qualcomm Incorporated Sidelink closed-loop transmit power control command processing
JP2023019054A (ja) * 2021-07-28 2023-02-09 株式会社デンソー リレー端末及び通信方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019031085A1 (ja) * 2017-08-09 2019-02-14 ソニー株式会社 通信装置及び通信方法
WO2019149341A1 (en) * 2018-01-30 2019-08-08 Huawei Technologies Co., Ltd. Techniques for location estimation using rfid tags
WO2021026571A1 (en) * 2019-08-08 2021-02-11 Qualcomm Incorporated Sidelink closed-loop transmit power control command processing
JP2023019054A (ja) * 2021-07-28 2023-02-09 株式会社デンソー リレー端末及び通信方法

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
EPCGLOBAL, LOW LEVEL READER PROTOCOL (LLRP) VERSION 1.1, Retrieved from the Internet <URL:https://gs1go2.azureedge.net/cdn/ff/7aZwEHsz5I8MM-lbIcvFNwjL90FcGGZgBU_hAjJttEE/1416474591/public/docs/epc/llrp_1_1-standard-20101013.pdf>
EPCGLOBAL, THE APPLICATION LEVEL EVENTS (ALE) SPECIFICATION VERSION 1.1.1 PART I: CORE SPECIFICATION, Retrieved from the Internet <URL:https://www.gs1.org/sites/default/files/docs/epc/ale_1_1_1-standard-core-20090313.pdf>
LENOVO: "On NTN NW verified UE location ", 3GPP TSG RAN #98E RP-223364, 5 December 2022 (2022-12-05), XP093201730 *

Also Published As

Publication number Publication date
JPWO2024171988A1 (https=) 2024-08-22
EP4668992A1 (en) 2025-12-24
CN120642546A (zh) 2025-09-12

Similar Documents

Publication Publication Date Title
JP7507825B2 (ja) 通信システム、基地局装置および通信端末装置
US20200127883A1 (en) Method and apparatus for beam failure recovery
KR20190017675A (ko) 하향링크 제어 채널의 송수신 방법 및 이를 이용하는 장치
EP4478784A1 (en) Communication system and base station
CN118612818A (zh) 通信系统、通信终端及基站
JP2025098084A (ja) 端末装置および通信システム
EP4195866A1 (en) Communication system and communication terminal
US20240340795A1 (en) Method and apparatus for supporting network energy saving function in communication network
CN116868623A (zh) 通信系统及基站
WO2024029423A1 (ja) 通信システム
WO2024143363A1 (ja) 通信システム
WO2024029422A1 (ja) 通信システム
WO2023013513A1 (ja) 通信システム
WO2024171988A1 (ja) 通信システム
EP4478800A1 (en) Communication system
EP4568336A1 (en) Communication system
WO2024185748A1 (ja) 通信システムおよび基地局
EP4568393A1 (en) Base station and communication system
EP4668993A1 (en) Communication system
WO2024232311A1 (ja) 通信システム
WO2025146774A1 (ja) 通信システム
WO2025033207A1 (ja) 通信システム
WO2024209973A1 (ja) 基地局および通信システム
WO2025187671A1 (ja) 通信システム
WO2025094903A1 (ja) 通信システム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24756833

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2025501130

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 202517068263

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 202480010628.1

Country of ref document: CN

WWP Wipo information: published in national office

Ref document number: 202517068263

Country of ref document: IN

WWP Wipo information: published in national office

Ref document number: 202480010628.1

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2024756833

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2024756833

Country of ref document: EP

Effective date: 20250915

WWP Wipo information: published in national office

Ref document number: 2024756833

Country of ref document: EP