WO2023204186A1 - 通信システム - Google Patents
通信システム Download PDFInfo
- Publication number
- WO2023204186A1 WO2023204186A1 PCT/JP2023/015354 JP2023015354W WO2023204186A1 WO 2023204186 A1 WO2023204186 A1 WO 2023204186A1 JP 2023015354 W JP2023015354 W JP 2023015354W WO 2023204186 A1 WO2023204186 A1 WO 2023204186A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- cell
- repeater
- base station
- pcell
- identifier
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/14—Relay systems
- H04B7/15—Active relay systems
- H04B7/204—Multiple access
- H04B7/208—Frequency-division multiple access [FDMA]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
- H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
- H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
- H04B7/0613—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission
- H04B7/0615—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal
- H04B7/0617—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal for beam forming
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/14—Relay systems
- H04B7/15—Active relay systems
- H04B7/155—Ground-based stations
- H04B7/15528—Control of operation parameters of a relay station to exploit the physical medium
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L27/00—Modulated-carrier systems
- H04L27/26—Systems using multi-frequency codes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
- H04W16/24—Cell structures
- H04W16/28—Cell structures using beam steering
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/14—Relay systems
- H04B7/15—Active relay systems
- H04B7/155—Ground-based stations
- H04B7/15528—Control of operation parameters of a relay station to exploit the physical medium
- H04B7/15542—Selecting at relay station its transmit and receive resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W56/00—Synchronisation arrangements
- H04W56/001—Synchronization between nodes
- H04W56/0015—Synchronization between nodes one node acting as a reference for the others
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
- H04W84/042—Public Land Mobile systems, e.g. cellular systems
- H04W84/047—Public Land Mobile systems, e.g. cellular systems using dedicated repeater stations
Definitions
- the present disclosure relates to wireless communication technology.
- LTE Long Term Evolution
- LTE-A Long Term Evolution Advanced
- NR New Radio Access Technology
- Non-Patent Document 3 For example, in Europe, an organization called METIS has compiled requirements for 5G (see Non-Patent Document 3).
- the 5G wireless access system has 1000 times the system capacity, 100 times the data transmission speed, 1/5th the data processing delay, and 100 times the number of simultaneous connection of communication terminals compared to the LTE system.
- the requirements include realizing further reductions in power consumption and costs of devices (see Non-Patent Document 3).
- OFDM Orthogonal Frequency Division Multiplexing
- DFT-s-OFDM Discrete Fourier Transform-spread-OFDM
- the 5G system does not include circuit switching and only uses a packet communication method.
- NR allows the use of higher frequencies than LTE in order to improve transmission speed and reduce processing delays.
- NR which may use a higher frequency than LTE
- cell coverage is ensured by forming a narrow beam-shaped transmission/reception range (beamforming) and changing the direction of the beam (beam sweeping).
- FIG. 1 is an explanatory diagram showing the structure of a radio frame used in an NR communication system.
- one radio frame is 10 ms.
- a radio frame is divided into 10 equally sized subframes.
- one or more numerologies ie, one or more subcarrier spacings (SCS)
- SCS subcarrier spacings
- one subframe is 1 ms regardless of the subcarrier interval, and one slot is composed of 14 symbols.
- the number of slots included in one subframe is one when the subcarrier interval is 15 kHz, and the number of slots at other subcarrier intervals increases in proportion to the subcarrier interval (Non-patent Document 11 (3GPP TS38 (See .211)).
- Non-Patent Document 2 (Chapter 5) and Non-Patent Document 11.
- a physical broadcast channel is a communication terminal from a base station device (hereinafter sometimes simply referred to as a "base station”) to a mobile terminal device (hereinafter sometimes simply referred to as a “mobile terminal”). This is a channel for downlink transmission to a device (hereinafter sometimes referred to as a “communication terminal” or “terminal”).
- PBCH is transmitted together with a downlink synchronization signal.
- Downlink synchronization signals in NR include a first synchronization signal (P-SS) and a second synchronization signal (S-SS).
- a synchronization signal is transmitted from a base station as a synchronization signal burst (hereinafter sometimes referred to as an SS burst) at a predetermined period and with a predetermined duration.
- the SS burst is composed of a synchronization signal block (hereinafter sometimes referred to as an SS block) for each beam of the base station.
- the base station transmits the SS block of each beam by changing the beam within the duration of the SS burst.
- the SS block is composed of P-SS, S-SS, and PBCH.
- a 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 a Downlink Shared Channel (DL-SCH), which is one of the transport channels described below, and a paging channel (Paging Channel, which is one of the transport channels described later). This includes resource allocation information for PCH, HARQ (Hybrid Automatic Repeat reQuest) information regarding DL-SCH, and the like.
- the DCI may include an uplink scheduling grant.
- DCI may include Ack (Acknowledgement)/Nack (Negative Acknowledgement) which is a response signal to uplink transmission.
- the DCI may include a slot format indication (SFI).
- PDCCH or DCI is also called L1/L2 control signal.
- a time/frequency region is provided as a candidate for PDCCH to be included. This area is called a control resource set (CORESET).
- the communication terminal monitors CORESET and acquires PDCCH.
- a physical downlink shared channel is a channel for downlink transmission from a base station to a communication terminal.
- a downlink shared channel (DL-SCH), which is a transport channel, and a PCH, which is a transport channel, are mapped to the PDSCH.
- a physical uplink control channel is a channel for uplink transmission from a communication terminal to a base station.
- PUCCH carries uplink control information (UCI).
- the UCI includes Ack/Nack, which is a response signal for downlink transmission, CSI (Channel State Information), scheduling request (SR), and the like.
- CSI is composed of RI (Rank Indicator), PMI (Precoding Matrix Indicator), and CQI (Channel Quality Indicator) report.
- RI is rank information of a channel matrix in MIMO (Multiple Input, Multiple Output).
- PMI is information on a precoding weight matrix used in MIMO.
- CQI is quality information indicating the quality of received data or the quality of a communication channel.
- the UCI may be carried by PUSCH, which will be described later.
- PUCCH or UCI is also called L1/L2 control signal.
- a physical uplink shared channel is a channel for uplink transmission from a communication terminal to a base station.
- An uplink shared channel (UL-SCH), which is one of the transport channels, is mapped to the PUSCH.
- a physical random access channel is a channel for uplink transmission from a communication terminal to a base station.
- PRACH carries a random access preamble.
- the downlink reference signal (Reference Signal: RS) is a symbol known as an NR communication system.
- the following four types of downlink reference signals are defined.
- Data demodulation reference signal (DM-RS), phase tracking reference signal (PT-RS), and positioning reference signal, which are UE-specific reference signals (UE-specific Reference Signal) :PRS), Channel State Information Reference Signal (CSI-RS).
- Measurements of the physical layer of a communication terminal include reference signal received power (RSRP) measurement and reference signal received quality (RSRQ) measurement.
- RSRP reference signal received power
- RSRQ reference signal received quality
- the uplink reference signal is a symbol known as an NR communication system.
- the following three types of uplink reference signals are defined. These are a data demodulation reference signal (DM-RS), a phase tracking reference signal (PT-RS), and a sounding reference signal (SRS).
- DM-RS data demodulation reference signal
- PT-RS phase tracking reference signal
- SRS sounding reference signal
- Non-Patent Document 2 (Chapter 5) will be explained.
- a broadcast channel (BCH) is broadcast throughout the coverage of the base station (cell).
- the BCH is mapped to a physical broadcast channel (PBCH).
- PBCH physical broadcast channel
- DL-SCH downlink shared channel
- DL-SCH can be broadcast to the entire coverage of a 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 a physical downlink shared channel (PDSCH).
- PDSCH physical downlink shared channel
- a paging channel supports DRX of a communication terminal to enable low power consumption of the communication terminal.
- PCH is required to be broadcast throughout the coverage of a base station (cell).
- the PCH is dynamically mapped to a physical resource such as a physical downlink shared channel (PDSCH) that is available for traffic.
- PDSCH physical downlink shared channel
- UL-SCH uplink shared channel
- PUSCH physical uplink shared channel
- Random Access Channel is limited to control information. RACH is at risk of collision. RACH is mapped to 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 functions effectively through retransmission even on transmission paths where communication quality changes. In particular, it is possible to further improve the quality by combining the reception results of the first transmission and the retransmission upon retransmission.
- a CRC error occurs on the receiving side
- the receiving side issues a retransmission request to the transmitting side.
- a retransmission request is made by toggling an 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 predetermined period of time, it is assumed that a CRC error has not occurred on the receiving side.
- a broadcast control channel is a downlink channel for broadcasting system control information.
- the BCCH which is a logical channel, is mapped to a broadcast channel (BCH), which is a transport channel, or a downlink shared channel (DL-SCH).
- BCH broadcast channel
- DL-SCH downlink shared channel
- PCCH Paging Control Channel
- PCCH paging channel
- a common control channel is a channel for transmitting control information between a communication terminal and a base station.
- CCCH is used when a communication terminal does not have an RRC connection with a network.
- the CCCH is mapped to a downlink shared channel (DL-SCH), which is a transport channel.
- DL-SCH downlink shared channel
- UL-SCH uplink shared channel
- a dedicated control channel is a channel that transmits dedicated control information between a communication terminal and a network on a one-to-one basis.
- DCCH is used when a communication terminal has an RRC connection with the network.
- the DCCH is mapped to an uplink shared channel (UL-SCH) in uplinks and to a downlink shared channel (DL-SCH) in downlinks.
- UL-SCH uplink shared channel
- DL-SCH downlink shared channel
- the Dedicated Traffic Channel is a channel for one-to-one communication with communication terminals for transmitting user information.
- DTCH exists on both uplink and downlink.
- DTCH is mapped to an uplink shared channel (UL-SCH) in uplinks, and mapped to a downlink shared channel (DL-SCH) in downlinks.
- UL-SCH uplink shared channel
- DL-SCH downlink shared channel
- Location tracking of communication terminals is performed in units of areas consisting of one or more cells. Location tracking is performed to track the location of a communication terminal even when it is in a standby state, and to make a call to the communication terminal, in other words, to enable the communication terminal to receive a call.
- This area for tracking the location of the communication terminal is called a tracking area (TA).
- NR In NR, calling of a communication terminal is supported in an area smaller than the tracking area. This range is called a RAN notification area (RAN Notification Area: RNA). Paging of a communication terminal in the RRC_INACTIVE state, which will be described later, is performed within this range.
- RNA RAN Notification Area
- carrier aggregation is used to aggregate two or more component carriers (CCs) (also referred to as “aggregation”) in order to support wide frequency bandwidths (transmission bandwidths).
- CCs component carriers
- aggregation also referred to as “aggregation”
- CA transmission bandwidths
- the UE When CA is configured, the UE, which is a communication terminal, has only one RRC connection with the network (NW).
- one serving cell provides the NAS mobility information and security input. This cell is called a primary cell (PCell).
- PCell primary cell
- SCell secondary cell
- a serving cell set consisting of one PCell and one or more SCells is configured for one UE.
- DC dual connectivity
- a master base station Master Node: MN
- secondary base station Secondary Node: SN
- Serving cells configured by a master base station may be collectively referred to as a master cell group (Master Cell Group: MCG)
- serving cells configured by a secondary base station may be collectively referred to as a secondary cell group (Secondary Cell Group: SCG).
- a primary cell in an MCG or SCG is called a special cell (SpCell or SPCell).
- a special cell in the MCG is called a PCell
- a special cell in the SCG is called a primary SCG cell (PSCell).
- the base station presets a part of the carrier frequency band (hereinafter sometimes referred to as Bandwidth Part (BWP)) to the UE, and the UE performs transmission and reception with the base station in the BWP. By performing this, it is possible to reduce power consumption in the UE.
- BWP Bandwidth Part
- 3GPP supports services (or applications) using side link (SL) communication (also called PC5 communication) in both the EPS (Evolved Packet System) described below and the 5G core system. are being considered (see Non-Patent Documents 1, 2, 26-28).
- SL communication communication is performed between terminals. Examples of services using SL communication include V2X (vehicle-to-everything) services and proximity services.
- V2X vehicle-to-everything
- the physical channel used for SL (see Non-Patent Documents 2 and 11) will be explained.
- the Physical Sidelink Broadcast Channel (PSBCH) carries system and synchronization related information and is transmitted from the UE.
- a physical sidelink control channel (PSCCH) carries control information from the UE for sidelink communication and V2X sidelink communication.
- a physical sidelink shared channel (PSSCH) carries data from the UE for sidelink and V2X sidelink communications.
- a physical sidelink feedback channel (PSFCH) carries HARQ feedback on the sidelink from the UE that received the PSSCH transmission to the UE that transmitted the PSSCH.
- the transport channel used for SL (see Non-Patent Document 1) will be explained.
- 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 transmission.
- SL-SCH supports both UE autonomous resource selection and base station scheduled resource allocation. There is a collision risk in UE automatic resource selection, and when the UE is allocated individual resources by the base station, there is no collision.
- SL-SCH also supports dynamic link adaptation by changing transmit power, modulation, and coding.
- SL-SCH is mapped to PSSCH, which is a physical channel.
- a sidelink broadcast control channel is a sidelink channel for broadcasting sidelink system information from one UE to another UE.
- SBCCH is mapped to 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 another UE.
- STCH is used only by UEs with sidelink communication capabilities and UEs with V2X sidelink communication capabilities.
- One-to-one communication between UEs with two sidelink communication capabilities is also realized on the STCH.
- STCH is mapped to SL-SCH, which is a transport channel.
- a sidelink control channel is a sidelink control channel for transmitting control information from one UE to another UE.
- SCCH is mapped to SL-SCH, which is a transport channel.
- Non-Patent Document 27 (3GPP TS23.287)
- HARQ feedback In unicast communication and group cast communication in SL, HARQ feedback (Ack/Nack), CSI reporting, etc. are supported.
- IAB Integrated Access and Backhaul
- Non-Patent Document 30 control technology with RRC (sometimes referred to as L3 mobility) has been used for cell-level mobility, in other words, inter-cell mobility, but control technology that reduces delay time etc. during mobility has been used. Therefore, it has been proposed to perform mobility control between cells using mobility control (sometimes referred to as L1/L2 mobility) without RRC.
- L3 mobility control technology with RRC
- L1/L2 mobility mobility control
- one of the objects of the present disclosure is to realize a communication system that can control smart repeaters.
- a communication system includes a base station applied to a fifth generation wireless access system and a beamforming function, and is provided between a base station and a communication terminal, or between a communication terminal connected to the base station and another communication terminal.
- a smart repeater that performs relay processing with communication terminals, the base station transmits information about the beam used in the relay processing to the smart repeater, and the smart repeater A beam is formed based on the information and relay processing is performed.
- FIG. 2 is an explanatory diagram showing the structure of a radio frame used in an NR communication system.
- 1 is a block diagram showing the overall configuration of an NR communication system 210 being discussed in 3GPP. It is a block diagram of DC by the base station connected to NG core.
- 3 is a block diagram showing the configuration of a mobile terminal 202 shown in FIG. 2.
- FIG. 3 is a block diagram showing the configuration of a base station 213 shown in FIG. 2.
- FIG. 5 is a block diagram showing the configuration of a 5GC unit.
- FIG. 2 is a flowchart showing an outline of steps from a cell search to a standby operation performed by a communication terminal (UE) in an NR communication system.
- FIG. 2 is a diagram showing an example of a cell configuration in an NR system.
- FIG. 2 is a connection configuration diagram showing an example of a connection configuration of terminals in SL communication.
- FIG. 2 is a connection configuration diagram showing an example of a connection configuration of base stations that support access/backhaul integration.
- FIG. 7 is a diagram illustrating an example of assignment of SS block identifiers to beams that can be configured by base stations and repeaters in Modification 3 of Embodiment 1.
- FIG. 7 is a diagram illustrating another example of assignment of SS block identifiers to beams that can be configured by base stations and repeaters in Modification 3 of Embodiment 1.
- FIG. 7 is a diagram illustrating another example of assignment of SS block identifiers to beams that can be configured by base stations and repeaters in Modification 3 of Embodiment 1.
- FIG. 7 is a diagram illustrating another example of assignment of SS block identifiers to beams that can be configured by base stations and repeaters in Modification 3 of Embodiment 1.
- FIG. 7 is a diagram illustrating an example of a connection sequence of a repeater to a base station in Embodiment 2.
- FIG. 7 is a diagram illustrating an example of a C-plane protocol stack of a base station (gNB) and a repeater in Embodiment 3; 7 is a diagram illustrating an example of a C-plane protocol stack of an AMF, a base station (gNB), and a repeater in Embodiment 3.
- FIG. FIG. 7 is a diagram illustrating an example of a C-plane protocol stack of a base station (gNB) and a repeater in Embodiment 3;
- FIG. 7 is a diagram illustrating an example of a C-plane protocol stack of a base station (gNB), a repeater, and a UE in Embodiment 3; FIG.
- FIG. 7 is a diagram showing another example of the C-plane protocol stack of a base station (gNB), a repeater, and a UE in Embodiment 3;
- FIG. 7 is a diagram illustrating an example of a U-plane protocol stack of a base station (gNB), a repeater, and a UE in Embodiment 3;
- FIG. 2 is a conceptual diagram of inter-cell L1/L2 mobility.
- FIG. 7 is a diagram showing the first half of a sequence illustrating an example of an inter-cell L1/L2 mobility processing method within a DU in Embodiment 4;
- FIG. 7 is a diagram showing the latter half of a sequence illustrating an example of an inter-cell L1/L2 mobility processing method within a DU in Embodiment 4;
- FIG. 7 is a diagram showing the first half of a sequence illustrating an example of an inter-cell L1/L2 mobility processing method including cell change between different DUs in accordance with Embodiment 4;
- FIG. 7 is a diagram showing the latter half of a sequence illustrating an example of an inter-cell L1/L2 mobility processing method including cell change between different DUs in accordance with the fourth embodiment;
- FIG. 4 is a sequence diagram illustrating an example of an inter-cell L1/L2 mobility processing method between different DUs in accordance with Embodiment 4;
- FIG. 10 is a sequence diagram showing another example of the inter-cell L1/L2 mobility processing method between different DUs in Embodiment 4.
- FIG. 10 is a sequence diagram illustrating an example of a method for notifying a UE identifier in a T-PCell in inter-cell L1/L2 mobility between different DUs in accordance with Embodiment 5;
- FIG. 10 is a sequence diagram showing another example of a method of notifying a UE identifier in a T-PCell in inter-cell L1/L2 mobility between different DUs in Embodiment 5.
- FIG. FIG. 10 is a sequence diagram showing another example of the inter-cell L1/L2 mobility processing method between different DUs in Embodiment 4.
- FIG. 10 is a sequence diagram illustrating an example of a method for notifying a UE identifier in a T-PCell in inter-cell L1/L2 mobility between different DUs in Embodiment 5.
- FIG. 10 is a sequence diagram showing another example of a method of notifying a UE identifier in a T-PCell in inter-cell L1/L2 mobility between different DUs in Embodiment 5.
- FIG. FIG. 9 is a sequence diagram illustrating an example of a data transmission method in inter-cell L1/L2 mobility processing in Embodiment 6;
- FIG. 9 is a sequence diagram showing another example of a data transmission method in inter-cell L1/L2 mobility processing in Embodiment 6;
- FIG. 9 is a sequence diagram showing another example of a data transmission method in inter-cell L1/L2 mobility processing in Embodiment 6;
- FIG. 9 is a sequence diagram showing another example of a data transmission method in inter-cell L1/L2 mobility processing in Embodiment 6;
- FIG. 2 is a block diagram showing the overall configuration of an 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)”) 202, which is a communication terminal device, is capable of wireless communication with a base station device (hereinafter referred to as “NR base station (NG-RAN NodeB: gNB)”) 213. It transmits and receives signals via wireless communication.
- the NG-RAN 211 is configured by one or more NR base stations 213.
- the term “communication terminal device” includes not only mobile terminal devices such as movable mobile phone terminal devices, but also non-mobile devices such as sensors.
- a “communication terminal device” may be simply referred to as a “communication terminal.”
- the AS (Access Stratum) protocol is terminated between the UE 202 and the NG-RAN 211.
- AS protocols include, for example, 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). But used.
- 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
- 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 send and receive data to and from the network. Furthermore, in RRC_CONNECTED, handover (HO), measurement of neighbor cells, and the like are performed.
- RRC_INACTIVE maintains the connection between the 5G core unit 214 and the NR base station 213 while performing system information (SI) broadcasting, paging, cell re-selection, mobility, etc. It will be done.
- gNB213 is a 5G core unit (hereinafter referred to as "5GC") that includes an access and mobility management function (AMF), a session management function (SMF), or a user plane function (UPF). 214 (sometimes referred to as "part") by an NG interface. Control information and/or user data are communicated between the gNB 213 and the 5GC unit 214.
- the NG interface is a general term for the N2 interface between gNB 213 and AMF 220, the N3 interface between gNB 213 and UPF 221, the N11 interface between AMF 220 and SMF 222, and the N4 interface between UPF 221 and SMF 222.
- a plurality of 5GC units 214 may be connected to one gNB 213.
- the gNBs 213 are connected by an Xn interface, and control information and/or user data are communicated between the gNBs 213.
- the 5GC unit 214 is a higher-level device, specifically a higher-level node, and controls the connection between the NR base station 213 and the mobile terminal (UE) 202, and controls the connection between one or more NR base stations (gNB) 213 and/or LTE. It distributes paging signals to base stations (E-UTRAN NodeB: eNB). Further, the 5GC unit 214 performs mobility control in an idle state. The 5GC unit 214 manages a tracking area list when the mobile terminal 202 is in a standby state, an inactive state, and an active state. The 5GC unit 214 initiates a paging protocol by transmitting a paging message to a cell belonging to a tracking area in which the mobile terminal 202 is registered.
- the gNB 213 may constitute one or more cells. When one gNB 213 configures multiple cells, each cell is configured to be able to communicate with the UE 202.
- 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 in the gNB 213.
- One or more DUs 216 are configured in the gNB 213.
- One DU 216 constitutes one or more cells.
- the CU 215 is connected to the DU 216 by an F1 interface, and control information and/or user data are communicated between the CU 215 and the DU 216.
- the F1 interface consists 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 TRP 219 transmits and receives radio signals to and from the UE.
- the CU 215 may be divided into a C-plane CU (CU-C) 217 and a U-plane CU (CU-U) 218.
- One CU-C 217 is configured in the CU 215.
- One or more CU-Us 218 are configured in 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 CU-U 218.
- the CU-C 217 is connected to the DU 216 through 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 by 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 the PCF may be included in the 5GC section 214 in FIG.
- a location management function described in Non-Patent Document 24 (3GPP TS38.305) may be provided.
- the LMF may be connected to the base station via the AMF, as disclosed in Non-Patent Document 25 (3GPP TS23.273).
- a 5G communication system may include a non-3GPP interworking function (N3IWF) described in Non-Patent Document 10 (3GPP TS23.501).
- N3IWF non-3GPP interworking function
- the N3IWF may terminate an access network (AN) between the UE and the UE.
- AN access network
- FIG. 3 is a diagram showing the configuration of a DC (dual connectivity) connected to the NG core.
- DC dual connectivity
- solid lines indicate U-Plane connections
- broken lines indicate C-Plane connections.
- 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 master base station 240-1 is a gNB and secondary base station 240-2 is an eNB may be referred to as NG-EN-DC.
- FIG. 3 shows an example in which the U-Plane connection between the 5GC unit 214 and the secondary base station 240-2 is performed via the master base station 240-1, the 5GC unit 214 and the secondary base station 240-2 It may also be done directly between. Further, 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 between the EPC and the secondary base station 240-2 may be made directly.
- EPC Evolved Packet Core
- FIG. 4 is a block diagram showing the configuration of the mobile terminal 202 shown in FIG. 2.
- the transmission processing of the mobile terminal 202 shown in FIG. 4 will be explained.
- control data from the control section 310 and user data from the application section 302 are sent to the protocol processing section 301 .
- Control data and user data may be buffered. Buffers for control data and 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 operations such as processing protocols such as SDAP, PDCP, RLC, and MAC, determining a destination base station in a DC, etc., and adding headers in each protocol.
- the data that has been subjected to the protocol processing is passed to the encoder section 304, where it is subjected to encoding processing such as error correction.
- encoding processing such as error correction.
- the data encoded by the encoder section 304 is modulated by the modulation section 305.
- the modulation section 305 may perform MIMO precoding.
- the modulated data is converted into a baseband signal and then output to frequency conversion section 306, where it is converted into a wireless transmission frequency. Thereafter, transmission signals are transmitted to the base station 213 from the antennas 307-1 to 307-4.
- FIG. 4 illustrates an example in which the number of antennas is four, the number of antennas is not limited to four.
- the reception process of the mobile terminal 202 is executed as follows. Radio signals from base station 213 are received by antennas 307-1 to 307-4. The received signal is converted from a radio reception frequency to a baseband signal by frequency converter 306, and demodulated by demodulator 308. Demodulation section 308 may perform weight calculation and multiplication processing. The demodulated data is passed to a decoder section 309, where decoding processing such as error correction is performed. The decoded data is passed to the protocol processing unit 301, and protocol processing such as MAC, RLC, PDCP, SDAP, etc., such as header removal in each protocol, is performed. Among the data subjected to protocol processing, control data is passed to the control unit 310, and user data is passed to the application unit 302.
- protocol processing such as MAC, RLC, PDCP, SDAP, etc.
- a series of processing by the mobile terminal 202 is controlled by the control unit 310. Therefore, although not shown in FIG. 4, the control section 310 is also connected to each section 302, 304 to 309.
- Each section 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.
- a program that describes a series of processes for the mobile terminal 202 is stored in memory. Examples of memory are nonvolatile or volatile semiconductor memories such as RAM (Random Access Memory), ROM (Read Only Memory), and flash memory.
- Each part of the mobile terminal 202 for example, a control unit 310, a protocol processing unit 301, an encoder unit 304, and a decoder unit 309, is an FPGA (Field Programmable Gate Array), an ASIC (Application Specific Integrated Circuit), a DSP (Digital Signal Processor), etc. It may also be realized by a dedicated processing circuit.
- the number of antennas used by mobile terminal 202 for transmission and the number of antennas used for reception may be the same or different.
- FIG. 5 is a block diagram showing the configuration of base station 213 shown in FIG. 2. Transmission processing of the base station 213 shown in FIG. 5 will be explained.
- 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 (5GC unit 214, etc.).
- Other base station communication section 402 transmits and receives data to and from other base stations.
- the EPC communication unit 401, 5GC communication unit 412, and 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, 5GC communication unit 412, and other base station communication unit 402 are sent to the protocol processing unit 403.
- Control data and user data may be buffered. 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. may be provided.
- the protocol processing unit 403 performs operations such as processing protocols such as SDAP, PDCP, RLC, and MAC, for example, routing transmission data in a DC, etc., and adding headers in each protocol.
- the data that has been subjected to the protocol processing is passed to the encoder unit 405, where it is subjected to encoding processing such as error correction.
- encoding processing such as error correction.
- 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 subjected to modulation processing in modulation section 406.
- Precoding in MIMO may be performed in modulation section 406.
- the modulated data is converted into a baseband signal, it is output to frequency conversion section 407 and converted into a wireless transmission frequency.
- transmission signals are transmitted to one or more mobile terminals 202 from antennas 408-1 to 408-4.
- FIG. 5 illustrates an example in which the number of antennas is four, the number of antennas is not limited to four.
- the reception processing of the base station 213 is executed as follows. Radio signals from one or more mobile terminals 202 are received by antennas 408-1 through 408-4. The received signal is converted from a radio reception frequency to a baseband signal by a frequency converter 407, and demodulated by a demodulator 409. The demodulated data is passed to a decoder section 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, RLC, PDCP, SDAP, etc., such as header removal in each protocol, is 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
- user data is passed to the 5GC communication unit 412, EPC communication unit 401, or other base station communication unit 402. It is passed to the other base station communication section 402.
- Data sent from the other base station communication section 402 may be sent to the 5GC communication section 412 or the EPC communication section 401.
- the data may be, for example, upstream data sent to the 5GC communication unit 412 or the EPC communication unit 401 via another base station in the DC.
- control section 411 is also connected to each section 401, 402, 405 to 410, 412.
- Each unit of the base station 213, for example, 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, is the same as the mobile terminal 202 described above. It is realized by a processing circuit including a processor and memory, or a dedicated processing circuit such as FPGA, ASIC, or DSP. In FIG. 5, the number of antennas used by base station 213 for transmission and the number of antennas used for reception may be the same or different.
- a device with a The DU communication unit connects to the protocol processing unit 403.
- a 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 except for the EPC communication unit 401, other base station communication unit 402, and 5GC communication unit 412 shown in FIG. 5 may be used.
- the CU communication unit connects to the protocol processing unit 403.
- a 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 section.
- FIG. 6 shows the configuration of the 5GC unit 214 shown in FIG. 2 described above.
- FIG. 6 shows a case where the 5GC section 214 shown in FIG. 2 includes an AMF configuration, an SMF configuration, and a UPF configuration.
- the AMF has the function of the control plane control unit 525
- the SMF has the function of the session management unit 527
- the UPF has the functions of the user plane communication unit 523 and the Data Network communication unit 521. good.
- 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 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 transmitted to the Data Network.
- the control data sent from the base station 213 is passed from the base station communication section 522 to the control plane control section 525.
- the control plane controller 525 may pass control data to the session manager 527.
- 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 section 521 to the session management section 527 via the user plane communication section 523.
- the session management unit 527 may send 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, and the like, and performs overall processing for the user plane (hereinafter sometimes referred to as U-Plane).
- the PDU processing unit 523-1 processes data packets, for example, transmits and receives packets to and from the Data Network communication unit 521 and transmits and receives packets to and from the base station communication unit 522.
- the mobility anchoring unit 523-2 is responsible for anchoring data paths when the UE is mobile.
- 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, a UE IP address assignment unit 527-2, and the like.
- 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 assignment unit 527-2 assigns an IP address to the mobile terminal 202, etc.
- the control plane control unit 525 includes a NAS security unit 525-1, an idle state mobility management unit 525-2, and the like, and performs overall processing for the control plane (hereinafter sometimes referred to as C-Plane).
- the NAS security unit 525-1 performs security for NAS (Non-Access Stratum) messages.
- the idle state mobility management unit 525-2 manages mobility in the standby state (Idle State: RRC_IDLE state, or simply referred to as idle), generates and controls paging signals during the standby state, and performs the following functions: Adding, deleting, updating, searching, tracking area list management, etc. of one or more mobile terminals 202 are performed.
- each part of the 5GC unit 214 is realized, for example, by a processing circuit including a processor and a memory, or a dedicated processing circuit such as an FPGA, an ASIC, or a DSP. Ru.
- FIG. 7 is a flowchart schematically showing steps from cell search to standby operation performed by a communication terminal (UE) in the NR communication system.
- the communication terminal starts cell search, in step ST601, the communication terminal determines the slot timing and frame using the first synchronization signal (P-SS) and the second synchronization signal (S-SS) transmitted from surrounding base stations. Synchronize timing.
- P-SS first synchronization signal
- S-SS second synchronization signal
- P-SS and S-SS are collectively referred to as a synchronization signal (SS).
- a synchronization code that corresponds one-to-one to a PCI (Physical Cell Identifier) assigned to each cell is assigned to the synchronization signal (SS).
- PCI Physical Cell Identifier
- 1008 types of PCI are being considered. The communication terminal synchronizes using these 1008 PCIs and detects (identifies) the PCI of the synchronized cell.
- the communication terminal receives the PBCH from the next synchronized cell in step ST602.
- a MIB Master Information Block
- the MIB information includes, for example, SFN (System Frame Number), SIB (System Information Block) 1 scheduling information, subcarrier intervals such as SIB 1, and DM-RS position information.
- the communication terminal acquires the 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 strings are included in the identifier used to generate the sequence of DM-RS accompanying the PBCH.
- the communication terminal obtains the SS block identifier using the MIB included in the PBCH and the DM-RS sequence accompanying 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, ie, the best cell, from among the one or more cells detected up to step ST603. Further, the communication terminal selects a beam with the best reception quality, for example, a beam with the highest reception power of the SS block, that is, the best beam. For example, the received power of the SS block for each SS block identifier is used to select the best beam.
- SIB1 includes information regarding access to the cell, cell configuration information, and scheduling information of other SIBs (SIBk: an integer of 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 part of the tracking area identifier (Tracking Area Identity: TAI) in the tracking area list already held by the communication terminal.
- the tracking area list is also referred to as 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 is the country code.
- MNC is a network code.
- TAC is the tracking area code number.
- step ST606 if the TAC received in step ST605 is the same as the TAC included in the tracking area list, the communication terminal enters a standby operation in the cell. In comparison, if the TAC received in step ST605 is not included in the tracking area list, the communication terminal transmits TAU (Tracking Area Update) to the core network (EPC) including the MME etc. through the cell. Request a tracking area change in order to do so.
- TAU Tracking Area Update
- core network side devices Devices that make up the core network (hereinafter sometimes referred to as “core network side devices”) perform tracking based on the identification number (UE-ID, etc.) of the communication terminal sent from the communication terminal along with the TAU request signal. Update the area list.
- 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. Thereafter, the communication terminal enters a standby operation in the cell.
- random access 4-step random access and 2-step random access are used.
- contention-based random access that is, random access in which timing collision with other mobile terminals may occur
- collision-free (contention-based) random access, contention-free) random access exists.
- 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 from the base station.
- the base station transmits a random access response to the mobile terminal.
- the random access response includes uplink scheduling information used in the third step, a terminal identifier used in uplink transmission in the third step, and the like.
- the mobile terminal performs uplink transmission to the base station.
- the mobile terminal uses the information acquired in the second step for uplink transmission.
- the base station notifies the mobile terminal whether or not there is a conflict resolution.
- the mobile terminal that is notified that there is no collision ends the random access process.
- the mobile terminal that is notified that there is a collision restarts the process from the first step.
- the collision-free 4-step random access method differs from the collision-based 4-step random access method in the following points. That is, prior to the first step, the base station allocates a random access preamble and uplink scheduling to the mobile terminal in advance. Further, the notification of whether or not the conflict is resolved in the fourth step is not required.
- the mobile terminal transmits a random access preamble and performs uplink transmission to the base station.
- the base station notifies the mobile terminal of the presence or absence of a collision.
- the mobile terminal that is notified that there is no collision ends the random access process.
- the mobile terminal that is notified that there is a collision 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 points. That is, prior to the first step, the base station allocates a random access preamble and uplink scheduling to the mobile terminal in advance. Also, in the second step, the base station transmits a random access response to the mobile terminal.
- FIG. 8 shows an example of a cell configuration in NR.
- a narrow beam is formed and transmitted by changing direction.
- base station 750 performs transmission and reception with a mobile terminal using beam 751-1 at a certain time. At other times, base station 750 transmits to and receives from mobile terminals using beam 751-2. Similarly, the base station 750 uses one or more of the beams 751-3 to 751-8 to perform transmission and reception with the mobile terminal. In this way, the base station 750 configures a wide area cell 752.
- FIG. 8 shows an example in which the number of beams used by the base station 750 is eight, the number of beams may be different from eight. Furthermore, in the example shown in FIG. 8, the number of beams that the base station 750 uses simultaneously is one, but it may be plural.
- the concept of QCL is used for beam identification (see Non-Patent Document 14 (3GPP TS38.214)). That is, the beam is identified by information indicating which reference signal (eg, SS block, CSI-RS) beam can be regarded as the same beam.
- the information may include the type of information regarding viewpoints that can be regarded as the same beam, for example, information regarding Doppler shift, Doppler shift spread, average delay, average delay spread, and spatial Rx parameters (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, ie, PC5 communication.
- the link is implemented at the V2X layer and is also referred to as a layer 2 link.
- RRC signaling in SL communication is also referred to as PC5 RRC signaling.
- PC5 RRC signaling it has been proposed to notify UE capabilities between UEs that perform PC5 communication, and to notify AS layer settings for performing V2X communication using PC5 communication.
- FIG. 9 shows an example of a connection configuration of mobile terminals in SL communication.
- UE 805 and UE 806 exist within coverage 803 of base station 801.
- UL/DL communication 807 is performed between base station 801 and UE 805.
- UL/DL communication 808 is performed between base station 801 and UE 806.
- SL communication 810 is performed between UE 805 and UE 806.
- UE 811 and UE 812 exist outside the coverage 803.
- SL communication 814 is performed between UE 805 and UE 811.
- SL communication 816 is performed between UE 811 and UE 812.
- a UE 805 shown in FIG. 9 relays communication between a UE 811 and a base station 801.
- a configuration similar to that in FIG. 4 may be used for a UE that performs relaying.
- Relay processing in the UE will be explained using FIG. 4.
- Relay processing by the UE 805 in communication from the UE 811 to the base station 801 will be described.
- Radio signals from UE 811 are received by antennas 307-1 to 307-4.
- the received signal is converted from a radio reception frequency to a baseband signal by frequency converter 306, and demodulated by demodulator 308.
- Demodulation section 308 may perform weight calculation and multiplication processing.
- the demodulated data is passed to a decoder section 309, where decoding processing such as error correction is performed.
- the decoded data is passed to the protocol processing unit 301, and protocol processing such as MAC and RLC used for communication with the UE 811, such as header removal in each protocol, is performed. It also performs protocol processing such as RLC and MAC used for communication with the base station 801, such as adding headers in each protocol.
- the protocol processing unit 301 of the UE 811 may perform PDCP and SDAP protocol processing.
- the data that has been subjected to the protocol processing is passed to the encoder section 304, where it is subjected to encoding processing such as error correction. There may be data that is directly output from the protocol processing section 301 to the modulation section 305 without being subjected to encoding processing.
- the data encoded by the encoder section 304 is modulated by the modulation section 305.
- the modulation section 305 may perform MIMO precoding.
- the modulated data is converted into a baseband signal and then output to frequency conversion section 306, where it is converted into a wireless transmission frequency. Thereafter, transmission signals are transmitted to the base station 801 from the antennas 307-1 to 307-4.
- a 5G base station can support integrated access and backhaul (IAB) (see Non-Patent Documents 2 and 20).
- a base station that supports IAB (hereinafter sometimes referred to as an IAB base station) is an IAB donor CU, which is a CU of a base station that operates as an IAB donor that provides IAB functions, and a DU of a base station that operates as an IAB donor. It is composed of an IAB donor DU and an IAB node that is connected to the IAB donor DU and to the UE using a wireless interface. An F1 interface is provided between the IAB node and the IAB donor CU (see Non-Patent Document 2).
- IAB donor CU901 is connected to IAB donor DU902.
- 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.
- the UE 905 is connected to the IAB node 904 using a wireless interface.
- the UE 906 may be connected to the IAB node 903 using a wireless interface, and the UE 907 may be connected to the IAB donor DU 902 using a wireless interface.
- a plurality of IAB donor DUs 902 may be connected to an IAB donor CU 901, a plurality of IAB nodes 903 may be connected to an IAB donor DU 902, and a plurality of IAB nodes 904 may be connected to an IAB node 903. There may be cases where
- a BAP (Backhaul Adaptation Protocol) layer is provided in the connection between the IAB donor DU and the IAB node and the connection between the IAB nodes (see Non-Patent Document 29).
- the BAP layer performs operations such as routing received data to an IAB donor DU and/or IAB node and mapping it to an RLC channel (see Non-Patent Document 29).
- the protocol processing unit of the IAB donor DU performs BAP layer processing, such as adding a BAP header to downlink data, routing to an IAB node, and removing the BAP header from uplink data.
- the configuration shown in FIG. 5 excluding the EPC communication section 401, other base station communication section 402, and 5GC communication section 412 may be used.
- Transmission and reception processing at the IAB node will be explained using FIGS. 5 and 10. Transmission and reception processing of the IAB node 903 in communication between the IAB donor CU 901 and the UE 905 will be described.
- 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 a radio reception frequency to a baseband signal by a frequency converter 407, and demodulated by a demodulator 409.
- the demodulated data is passed to a decoder section 410, where decoding processing such as error correction is performed.
- the decoded data is passed to the protocol processing unit 403, where it performs protocol processing such as MAC and RLC used for communication with the IAB node 904, such as header removal in each protocol. Further, 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 is performed, for example, operations such as adding headers in each protocol are performed.
- the data that has been subjected to the protocol processing is passed to the encoder unit 405, where it is subjected to encoding processing such as error correction. There may also be data that is directly output from protocol processing section 403 to modulation section 406 without being subjected to encoding processing.
- the encoded data is subjected to modulation processing in modulation section 406.
- Precoding in MIMO may be performed in modulation section 406.
- the modulated data is converted into a baseband signal, it is output to frequency conversion section 407 and converted into a wireless transmission frequency.
- transmission signals are transmitted to the IAB donor DU 902 from the antennas 408-1 to 408-4. Similar processing is performed in downlink communication from the IAB donor CU 901 to the UE 905.
- the IAB node 904 also performs the same transmission and reception processing as the IAB node 903.
- the protocol processing unit 403 of the IAB node 903 performs BAP layer processing such as adding a BAP header in uplink communication and routing to the IAB node 904, and removing the BAP header in downlink communication.
- a smart repeater (hereinafter sometimes simply referred to as a "repeater”) is used for communication between a base station and a UE (hereinafter sometimes referred to as an access link (AL) (see Non-Patent Document 31)).
- a repeater may have multiple beams.
- the repeater may receive a signal from a transmission source, amplify it, and transmit the amplified signal to a transmission destination (this operation may be referred to as AL transmission/reception).
- the repeater may use beams for AL transmission and reception.
- the base station may control the repeater.
- the base station may transmit a control signal to the repeater (a link used for transmitting a control signal between the base station and the repeater is sometimes referred to as a fronthaul link (FL) (Non-patent Document 31). reference)).
- FL fronthaul link
- L1/L2 signaling may be used for the control signal.
- Embodiment 1 discloses a method for solving such problems.
- the base station instructs the repeater in advance.
- the instruction from the base station to the repeater may be given prior to AL transmission/reception, for example, downlink transmission from the base station to the UE, uplink transmission from the UE to the base station, or may be given prior to sidelink communication between terminals. It's okay to be hurt.
- the repeater may perform AL transmission/reception using the instruction as a trigger. AL transmission and reception may be performed on U-plane data, control information, or reference signals.
- AL may include communication between UEs, and may include communication between base stations, for example, between an IAB donor DU and/or an IAB node, and an IAB node.
- AL transmission/reception in the repeater may be performed between the above-mentioned AL, for example, a base station and a UE, between UEs, or between base stations, for example, an IAB donor DU. And/or transmission and reception between IAB nodes may be performed.
- AL transmission and reception in the repeater may be performed on the downlink, uplink, or sidelink.
- L1/L2 signaling may be used for the instruction.
- a new DCI may be provided.
- a new DCI may be used for the instruction. This makes it possible to prevent malfunctions caused by, for example, other UEs receiving DCI for repeaters.
- MAC signaling may be used for the instruction. This allows, for example, a large amount of information to be transmitted from the base station to the repeater.
- RRC signaling may be used for the instruction. This allows, for example, more information to be transmitted from the base station to the repeater.
- the information in (1) above may include the UE identifier.
- the identifier of the UE may include, for example, a C-RNTI (Cell Radio Network Temporary Identifier). This allows, for example, the repeater to quickly recognize the UE that is the other party for AL transmission and reception.
- the information may include a base station identifier, a DU identifier, a TRP identifier, or a cell identifier.
- the IAB node identifier may be included. This allows, for example, the repeater to quickly recognize the base station, DU, and/or IAB node with which AL transmission/reception is to be performed.
- the information in (2) above may include, for example, information regarding the PDU session used by the UE.
- the repeater may use this information to recognize the source device and destination device. This makes it possible, for example, to reduce the size of signaling from the base station to the repeater.
- the information in (3) above may include information regarding the time when AL transmission and reception starts, information regarding the duration of AL transmission and reception, and information regarding the time when AL transmission and reception ends. may be included.
- the aforementioned information may include any one or a combination of a radio frame number, subframe number, slot number, and symbol number.
- the information in (3) above may include information regarding the time from the instruction to the start of AL transmission/reception.
- the information may include any one or a combination of a radio frame number, subframe number, slot number, and symbol number.
- the information in (3) above may include information regarding slot length or information regarding subcarrier spacing (SCS).
- SCS subcarrier spacing
- the repeater may perform AL transmission and reception using the time resources included in the information (3) above.
- the repeater may stop AL transmission/reception outside the time resources included in the information (3) above, or may perform default AL transmission/reception. As a result, for example, the repeater can perform AL transmission and reception at appropriate timing, and the power consumption of the repeater can be reduced.
- the information in (4) above may include information regarding the lower end of the frequency resource (eg, subcarrier) on which AL transmission and reception is performed, or may include information regarding the upper end of the frequency resource.
- the aforementioned information may include information regarding frequencies, information regarding subcarrier numbers, and information regarding physical resource blocks (PRBs).
- the information in (4) above may include information regarding the range of the frequency resource.
- the information regarding the range may include information regarding frequency width, information regarding the number of subcarriers, or information regarding the number of PRBs.
- the information in (4) above may include information regarding the frequency band in which the frequency resource is included.
- the information regarding frequency bands may include information regarding carrier bands, and may include information regarding BWP.
- the repeater may use this information to obtain information regarding the frequency used for AL transmission and reception.
- the repeater may perform transmission/reception operations related to AL transmission/reception in the frequency resources included in the information (4) above.
- the repeater may not perform transmission/reception operations related to AL transmission/reception outside of the frequency resources included in the information (4) above.
- the repeater can perform AL transmission and reception within an appropriate frequency range, and the power consumption of the repeater can be reduced.
- the information in (5) above may include information regarding beams used by base stations, DUs, TRPs, and/or IAB nodes (hereinafter, these may be collectively referred to as base stations, etc.). , information regarding beams used by the repeater in transmission/reception with a base station or the like, or information regarding beams used by the repeater in transmission/reception with the UE.
- the above-mentioned information (5) may include information regarding the beam used by the repeater for receiving operation, or may include information regarding the beam used by the repeater for transmitting operation.
- the above-mentioned beam-related information may include an SS block identifier or a CSI-RS identifier.
- the aforementioned identifier may be, for example, an identifier of an SS block and/or CSI-RS included in a beam that is in a QCL relationship with a beam received by the repeater.
- the information in (5) above may include information regarding the RS transmitted by the repeater.
- the information regarding the RS may include, for example, information regarding the configuration of the CSI-RS transmitted by the repeater, or information regarding the configuration of the SS block transmitted by the repeater.
- the repeater may use this information to direct the beam to the device with which it will perform AL transmission and reception. This enables, for example, communication between a base station or the like and a UE via a repeater.
- the information in (5) above may include information regarding the beam width.
- the repeater may use this information to determine the beam width. For example, a narrow beam may be used for transmission from a repeater to a base station, and a wide beam may be used for transmission from a repeater to a frequently moving UE. This enables, for example, reliable communication with low power consumption.
- the information in (6) above may include information regarding the reception angle at the repeater, and may also include information regarding the transmission angle at the repeater.
- the above-mentioned information regarding the angle may include, for example, information regarding the azimuth angle or information regarding the elevation angle.
- the information regarding the aforementioned angle may be given as an angle with respect to a predetermined direction.
- the predetermined direction may be an absolute direction, for example horizontal north direction, or a relative direction, for example a direction from the repeater to the base station.
- the repeater may use the information to perform transmission/reception operations related to AL transmission/reception.
- the repeater may not receive radio waves from angles other than those included in the information (6) above. This makes it possible to improve, for example, the performance (eg, SINR (Signal to Interference Noise Ratio)) in transmission and reception via the repeater.
- SINR Signal to Interference Noise Ratio
- the information in (6) above may include information regarding the reflected wave transmission angle in the repeater. This information may be included, for example, when a reflector is used instead of a repeater, or when a Reconfigurable Intelligent Surface (RIS) is used. This makes it possible, for example, to expand the coverage of base stations while reducing power consumption in the communication system.
- RIS Reconfigurable Intelligent Surface
- the information in (7) above may include information regarding the reception gain at the repeater, information regarding the transmission gain at the repeater, or information regarding the gain from the reception end to the transmission end at the repeater. May be included.
- the repeater may use this information to perform an amplification operation in AL transmission and reception. As a result, for example, the repeater can perform AL transmission and reception using sufficient power necessary for AL transmission and reception between the base station, etc. and the UE, and as a result, the repeater can perform AL transmission and reception between the base station, etc. and/or the UE. can be reduced.
- the information in (7) above may include information regarding the amount of attenuation in the repeater.
- the information regarding the amount of attenuation may include information regarding the amount of attenuation in the receiving section, information regarding the amount of attenuation in the transmitting section, or information regarding the amount of attenuation from the transmitting end to the receiving end.
- You may be By this means, for example, when the power used for AL transmission and reception is large, it is possible to reduce the power, and as a result, it is possible to reduce interference with devices of surrounding communication systems. Furthermore, even when using a relay device that does not perform amplification, such as a reflector or RIS, it is possible to control the power related to AL transmission and reception.
- the repeater may transmit a signal to the base station etc. and/or the UE using the information regarding (8) above. This makes it possible to reduce interference to other base stations and/or the UE, for example, while enabling transmission and reception between the base station and the UE.
- the repeater may start the AL transmission/reception operation or may stop the AL transmission/reception operation using the information in (9) above. This makes it possible to reduce power consumption in the repeater, for example.
- the above information (10) may include, for example, information regarding uplinks, information regarding downlinks, and information regarding sidelinks.
- the repeater may use this information to determine the reception destination and/or transmission destination in AL transmission/reception. This makes it possible to reduce the amount of signaling from the base station to the repeater, for example.
- the information in (11) above may include, for example, information indicating that the signal/channel is transmitted individually to the UE, or information indicating that the signal/channel is commonly transmitted to the UE. may also include information indicating.
- the information in (11) above may include information indicating that it is data (for example, U-plane data), information indicating that it is a control signal, or information indicating that it is a reference signal. It may also include information indicating that it is.
- the information in (11) above may include, for example, information identifying a signal/channel (eg, PDCCH, PUSCH, SS block).
- the repeater may use the information to perform AL transmission/reception operations. This makes it possible, for example, to avoid complications in the control of repeaters.
- the information in (11) above may include information regarding the repetition of the signal/channel.
- the information may include, for example, information regarding the number of repetitions.
- the repeater may use the information to perform AL transmission/reception multiple times. This allows, for example, repetition of signals/channels via repeaters in communication systems.
- the above-mentioned information (12) may include, for example, information regarding the AL transmission/reception operation of the repeater when there is no instruction from the base station.
- the information may be, for example, information indicating that the repeater's AL transmission/reception is to be turned off, information indicating that the repeater performs a receiving operation using a predetermined beam, or information indicating that the repeater is to perform a receiving operation using a predetermined beam.
- the information may also be information indicating that a transmission operation is performed using a predetermined beam.
- the repeater may use the information to perform default AL transmission and reception operations. This makes it possible to reduce the amount of signaling related to AL transmission and reception, for example.
- the information in (13) above may include, for example, information regarding transmittance with respect to incident power, information regarding transmitted power, or information regarding reflectance with respect to incident power.
- information regarding reflected power may be included.
- the information may be used, for example, in the reflector and/or the RIS.
- a device such as a repeater may use the information to control itself, for example. This makes it possible to avoid the complexity of controlling reflected power, for example, even when controlling the amount of attenuation is complicated.
- the information in (1) to (14) above may be provided for each UE or for each signal/channel.
- the beam used for transmitting the SS block and the beam used for transmitting the PDCCH and/or PDSCH may be different. This makes it possible, for example, to improve coverage while ensuring power efficiency in a communication system.
- the repeater may obtain all information necessary for AL transmission and reception using instructions from the base station. This makes it possible to avoid processing complexity in repeaters, for example.
- the repeater may perform AL transmission and reception based on some of its own judgment. For example, the repeater may determine the destination beam or transmit power using information regarding the UE notified from the base station. This makes it possible to reduce the amount of signaling from the base station to the repeater, for example.
- This instruction from the base station to the repeater may be performed sequentially. After the access link transmission/reception related to the instruction is completed, the repeater may stop the AL transmission/reception operation, or may perform the default AL transmission/reception.
- the base station may notify the UE of information regarding the beam.
- Information indicating that the communication is via a repeater may be notified.
- the information about beams may include information about the beams used by the repeater, eg, the beams that the repeater directs towards the UE.
- the information regarding the beam used by the repeater may include TCI (Transmission Configuration Indication)-state information (see Non-Patent Document 14 (3GPP TS38.214)) of the cell covered by the repeater.
- the notification from the base station to the UE may be performed using RRC signaling, for example, RRC reconfiguration, MAC signaling, or L1/L2 signaling. It's okay to be hurt.
- the UE may use the notification to obtain information about the beams used by the repeater. This allows, for example, a UE to communicate with a base station via a repeater.
- FIG. 11 is a diagram illustrating an example of an instruction from a base station to a repeater and an AL transmission/reception operation of the repeater in response to the instruction.
- FIG. 11 shows a case where the base station sequentially controls the repeater for each slot.
- FIG. 11 shows an example in which a repeater is used for communication between the base station and UE #1 and between the base station and UE #2.
- the beams shown in FIG. 11 only show the beams used for transmission and reception with the UE, and the beams used for transmission and reception with the base station are omitted.
- UE #1 is located in beam 1105 and UE #2 is located in beam 1107.
- PDCCH is allocated for three symbols from the beginning of each slot.
- the control signal from the base station to the repeater is assigned to the third symbol from the beginning of the PDCCH. It is assumed that the control signal from the base station to the repeater is reflected in the next slot.
- Control signal 1101 includes information indicating that downlink signal transmission is to be performed using beam 1105.
- the repeater receives PDCCH 1102 and PDSCH 1104 from the base station, and transmits them to UE #1 using beam 1105.
- PDCCH 1102 includes scheduling allocation information regarding PDSCH 1104.
- UE #1 receives PDCCH 1102 and PDSCH 1104 transmitted from the repeater.
- Control signal 1103 is transmitted from the base station to the repeater.
- Control signal 1103 includes information indicating that downlink signal transmission is to be performed using beam 1107.
- the repeater receives PDCCH 1106 from the base station and transmits it to UE #2 using beam 1107.
- PDCCH 1106 includes uplink grant information related to PUSCH 1109 in slot #4.
- UE #2 receives the PDCCH 1106 transmitted from the repeater and acquires uplink grant information.
- slot #2 no control signal is transmitted from the base station to the repeater. Triggered by the fact that no control signal was included in slot #2, the repeater transmits downlink signals to UE #1 and UE #2 in slot #3, and also transmits uplink signals from UE #1 and UE #2. There is no reception either.
- Control signal 1108 is transmitted from the base station to the repeater.
- Control signal 1108 includes information indicating that uplink signal transmission is to be performed using beam 1107.
- the repeater receives PUSCH 1109 from UE #2 using beam 1107 and transmits it to the base station.
- slot #4 no control signal is transmitted from the base station to the repeater. Triggered by the fact that no control signal was included in slot #4, the repeater transmits downlink signals to UE #1 and UE #2 in slot #5, and also transmits uplink signals from UE #1 and UE #2. There is no reception either.
- control signals 1101, 1103, and 1108 from the base station to the repeater may not be transmitted to UE #1 and/or UE #2. This makes it possible to reduce the power consumption of the repeater, for example.
- a control signal 1103 from the base station to the repeater may be transmitted from the repeater using beam 1105. This makes it possible, for example, to avoid complications in the control of repeaters.
- the above method may be applied when multiple beams are used for AL transmission and reception.
- the above method may be used when different beams are used for PDCCH and PDSCH for the same UE, or the above method may be used when different beams are used for PDCCH and PUSCH for the same UE.
- the instructions from the base station to the repeater may include the information (1) to (14) described above corresponding to each of the plurality of beams. This allows, for example, increased flexibility in the communication system.
- Information regarding some of the beams among the plurality of beams may be included in the time/frequency domain of control information (eg, PDCCH) from the base station to the UE.
- the information regarding some beams may be, for example, information regarding the beams used for transmitting and receiving signals/channels related to the control information.
- the repeater may obtain information regarding some of the beams by receiving the time/frequency domain of the control information. This makes it possible, for example, to distribute the resources required for the instruction from the base station to the repeater, and as a result, it becomes possible to improve resource usage efficiency in the communication system.
- the instruction may have continuity.
- the repeater may continue to perform AL transmission and reception using the instruction as a trigger.
- the instruction may include information regarding the cycle. Information regarding offsets associated with the period may also be included.
- the repeater may perform AL transmission and reception for each cycle.
- the instructions may be provided with information regarding the duration.
- the repeater may perform AL transmission and reception during the duration.
- the repeater may not perform AL transmission/reception after the elapse of the duration, or may perform default AL transmission/reception.
- a plurality of instructions with continuity may be provided. This enables, for example, transmission and reception between a base station and a plurality of UEs via a repeater.
- FIG. 12 is a diagram illustrating another example of an instruction from a base station to a repeater and the AL transmission/reception operation of the repeater accompanying the instruction.
- FIG. 12 shows a case where a base station issues a continuity instruction to a repeater.
- FIG. 12 shows an example in which a repeater is used for communication between the base station and UE #1 and between the base station and UE #2.
- the beams shown in FIG. 12 only show the beams used for transmission and reception with the UE, and the beams used for transmission and reception with the base station are omitted.
- UE #1 is located in beam 1205 and UE #2 is located in beam 1209.
- FIG. 12 shows an example in which the control of the repeater from the base station is reflected in the next slot and thereafter.
- PDCCH is allocated for three symbols from the beginning of each slot.
- the control signal from the base station to the repeater is assigned to the third symbol from the beginning of the PDCCH. It is assumed that the control signal from the base station to the repeater is reflected in the next slot.
- Control signal 1201 includes information indicating that downlink signal transmission is to be performed using beam 1205.
- the repeater performs a downlink signal transmission operation using beam 1205 in slot #1 according to the information included in control signal 1201.
- the repeater receives PDCCH 1202 and PDSCH 1204 from the base station, and transmits them to UE #1 using beam 1205.
- PDCCH 1202 includes scheduling allocation information regarding PDSCH 1204.
- UE #1 receives PDCCH 1202 and PDSCH 1204 transmitted from the repeater.
- slot #1 no control signal is transmitted from the base station to the repeater.
- the repeater continues the downlink signal transmission operation using beam 1205 in slot #2, triggered by the fact that no control signal is included in slot #1.
- the base station does not transmit anything, so the repeater does not perform downlink transmission using beam 1205.
- slot #2 no control signal is transmitted from the base station to the repeater.
- the repeater continues the downlink signal transmission operation using beam 1205 in slot #3, triggered by the fact that no control signal is included in slot #2.
- the repeater receives PDCCH 1206 and PDSCH 1207 from the base station, and transmits them to UE #1 using beam 1205.
- PDCCH 1206 includes scheduling allocation information regarding PDSCH 1207.
- UE #1 receives PDCCH 1206 and PDSCH 1207 transmitted from the repeater.
- Control signal 1208 includes information indicating that downlink signal transmission is to be performed using beam 1209.
- the repeater performs a downlink signal transmission operation using beam 1209 in slot #4 according to the information included in control signal 1208.
- the repeater receives PDCCH 1210 and PDSCH 1211 from the base station, and transmits them to UE #2 using beam 1209.
- PDCCH 1210 includes scheduling allocation information regarding PDSCH 1211.
- UE#2 receives PDCCH1210 and PDSCH1211 transmitted from the repeater.
- slot #4 no control signal is transmitted from the base station to the repeater.
- the repeater continues the downlink signal transmission operation using beam 1209 in slot #5, triggered by the fact that no control signal is included in slot #4.
- the base station does not transmit anything, so the repeater does not perform downlink transmission using beam 1209.
- control signals 1201 and 1208 from the base station to the repeater may not be transmitted to UE #1 and/or UE #2. This makes it possible to reduce the power consumption of the repeater, for example.
- control signals 1208 from the base station to the repeater may be transmitted from the repeater using beam 1205. This makes it possible, for example, to avoid complications in the control of repeaters.
- Sequential instructions and continuous instructions may coexist.
- the instruction may include information indicating whether the instruction is sequential or continuous.
- the repeater may use the information to determine whether the instruction is sequential or continuous.
- a priority may be set between the sequential instructions and the continuous instructions.
- sequential instructions may take precedence over continuous instructions, or later instructions may take precedence over earlier instructions. This makes it possible, for example, to avoid complications regarding the control of repeaters.
- the repeater performs AL transmission and reception using control signals transmitted from the base station to the UE.
- a repeater may receive the control signal, eg DCI.
- the repeater may acquire information regarding the UE or information regarding transmission and reception resources from the DCI.
- the DCI may include the information (1) to (14) described above, may include information regarding downlink scheduling allocation, may include information regarding uplink scheduling grant, Information regarding scheduling assignment of side links may be included, information regarding preemption may be included, and other information disclosed in Non-Patent Document 12 (3GPP TS38.212) may be included.
- the repeater may receive the downlink signal transmitted by the base station and transmit it to the UE.
- the downlink signal may include PDCCH, PDSCH, DMRS (Demodulation Reference Signal), PT-RS, or CSI - RS, SS block, or PRS may be included.
- the above-mentioned control signal may be included in the downlink signal.
- the repeater may transmit the downlink signal using the aforementioned DCI. For example, the repeater may transmit the downlink signal using time resource information included in the DCI, or may transmit the downlink signal using UE information (e.g., C-RNTI) included in the DCI.
- the downlink signal may be transmitted to the beam where the UE is located.
- the repeater may receive the uplink signal transmitted by the UE and transmit it to the base station.
- the uplink signal may include PUSCH, PUCCH, DMRS, PT-RS, or SRS. or PRACH may be included.
- the repeater may transmit the uplink signal using the aforementioned DCI.
- the repeater may transmit the uplink signal using time resource information included in the DCI, or may transmit the uplink signal using UE information (e.g., C-RNTI) included in the DCI.
- Uplink signals from the UE may be received using the beam in which the UE is located.
- the repeater may obtain information necessary for the UE to receive control signals from the base station.
- the base station may notify the repeater of this information.
- the information may be, for example, information regarding the UE's CORESET. This allows, for example, the repeater to receive control signals transmitted from the base station to the UE.
- the information may include information regarding the UE's SRB (Signaling Radio Bearer) configuration.
- the repeater may use the information to receive signaling from the base station to the UE, for example RRC signaling. This allows, for example, the repeater to recognize changes in the UE's CORESET.
- the processing time may include, for example, the time required to receive the control signal transmitted from the base station to the UE, or the time required to receive the downlink signal transmitted by the base station and then transmit it to the UE. It may be the time from when the uplink signal transmitted by the UE is received until it is transmitted to the base station, or the plurality of processing times described above may be provided for each of the above-mentioned processing times. .
- the processing time may be statically determined by the standard, or may be notified from the repeater to the base station.
- the notification from the repeater to the base station may be performed using L1/L2 signaling, MAC signaling, RRC signaling, may be notified as.
- the base station may use the information regarding processing time to schedule the UE. For example, the base station may use the information regarding the processing time to determine the offset time from PDCCH to PDSCH, or from the PDCCH to PUSCH.
- the repeater may receive broadcast information transmitted from the base station to the UE.
- the repeater may perform AL transmission and reception using broadcast information.
- the repeater may perform AL transmission/reception related to PRACH transmission from the UE to the base station by acquiring information regarding PRACH transmission timing included in broadcast information. This makes it possible to reduce the amount of signaling from the base station to the repeater, for example.
- the repeater may also perform a cell search.
- the repeater may obtain the transmission timing of the SS block using the cell search as an opportunity.
- the repeater may transmit the SS block from the base station to the UE using the cell search result. This makes it possible to reduce the amount of signaling from the base station to the repeater, for example.
- Embodiment 1 may be used in combination.
- a combination of AL transmission/reception using a prior instruction from the base station to the repeater and AL transmission/reception using a control signal to the UE may be used.
- AL transmission/reception using a prior instruction from the base station to the repeater may be used for signals/channels that are commonly transmitted between UEs, and AL transmission/reception may be used for signals/channels that are transmitted for each UE.
- AL transmission/reception using control signals may be used. This makes it possible, for example, to improve the flexibility of the communication system.
- the repeater becomes possible, and as a result, transmission and reception between the base station and the UE via the repeater becomes possible.
- the repeater may receive a control signal from a base station and perform AL transmission and reception.
- the control signal may be, for example, a DCI to a repeater.
- the control signal may include the instruction information disclosed in the first embodiment.
- an identifier is assigned to the repeater.
- the identifier may be, for example, an RNTI (Radio Network Temporary Identifier, see Non-Patent Document 15 (3GPP TS38.321)).
- An area for identifiers allocated to repeaters may be provided.
- the area may be newly provided in an unused area, or a part of an area already allocated for other purposes may be allocated for repeaters.
- the identifier may be fixedly assigned to each repeater.
- the repeater may have a SIM (Subscriber Identity Module).
- the SIM may include information regarding the identifier.
- Information regarding the identifier may be fixedly assigned to each repeater.
- the base station may assign the identifier to the repeater. Random access processing may be used for the assignment from the base station to the repeater, or RRC signaling may be used.
- the base station may encode the control signal to the repeater using the repeater's identifier.
- the repeater may decode the control signal using its assigned identifier.
- the repeater may use the fact that the decoding result is normal to recognize that the control signal is a control signal for its own repeater.
- Control signals for repeater control may also be provided.
- a new DCI may be provided.
- the new DCI may be used for repeater control.
- the repeater may recognize that the control signal is intended for its own repeater by using the fact that the decoding result of the control signal matches the format of the DCI for repeater control.
- the UE may recognize that the control signal is not intended for the UE by using the fact that the decoding result does not match the format of the control signal for the UE. This makes it unnecessary, for example, to assign identifiers to repeaters, thereby avoiding complexity in the communication system.
- an identifier may be assigned to a repeater, and the new DCI may be used in a control signal for controlling the repeater.
- the same identifier (eg, RNTI) may be allowed to be assigned to the repeater and the UE.
- a repeater may decode the control signal using an identifier assigned to the repeater.
- the repeater may recognize that the decoding result is a control signal for its own repeater by using the fact that it matches the DCI format for repeater control, or the repeater may recognize that the decoding result matches the DCI format for repeater control.
- the fact that the control signal does not match may be used to recognize that the control signal is not intended for the own repeater.
- the UE may decode the control signal using the identifier assigned to the UE.
- the UE may recognize that the decoding result is a control signal intended for the UE by using the fact that it matches the format of the DCI for UE control, or the UE may recognize that the decoding result matches the format of the DCI for UE control. It may be recognized that the control signal is not intended for the own UE by using the fact that the control signal does not match the UE. This makes it possible, for example, to prevent erroneous recognition of control signals between repeaters, and also to prevent erroneous recognition between control signal repeaters and UEs.
- a repeater may be assigned multiple identifiers.
- a repeater may perform AL transmission and reception using different settings (eg, settings included in (1) to (14) above) for each identifier used to decode a control signal for controlling the repeater.
- the above settings for each identifier may be notified from the base station to the repeater in advance. This makes it possible to reduce the size of a control signal for repeater control, for example.
- the same identifier as the identifiers of some or all of the UEs to which it is connected may be assigned to the repeater.
- the repeater may identify the UE that is the target of AL transmission and reception using an identifier used to decode a control signal for controlling the repeater. This makes it possible to reduce the size of a control signal for repeater control, for example.
- a base station may notify another base station (hereinafter sometimes referred to as base station B) of information regarding the identifier of a repeater under its own base station. .
- Base station A may perform the notification using an inter-base station interface, for example, Xn signaling.
- Base station B may use this information to provide identifiers to repeaters under its control.
- base station B may assign an identifier different from the identifier of a repeater under base station A to a repeater under its own base station. This makes it possible, for example, to prevent duplicate identifiers between a repeater under base station A and a repeater under base station B. As a result, for example, a repeater under base station A receives a signal from base station B. It is possible to prevent erroneous reception.
- a repeater can recognize a control signal directed to its own repeater, and as a result, communication between a base station, etc. and a UE via the repeater becomes possible.
- the repeater may receive a control signal from a base station and perform AL transmission and reception.
- the resources eg, frequency, time
- the repeater cannot receive a control signal from the base station, and as a result, a problem arises in that AL transmission and reception cannot be performed via the repeater.
- the repeater acquires information regarding resources (eg, frequency, time) used for transmitting and receiving control signals from the base station.
- resources eg, frequency, time
- a method similar to that of the UE may be used to obtain information regarding the resource at the repeater.
- the base station may individually notify the repeaters of information regarding the resources.
- the information regarding the resource may include, for example, CORESET.
- RRC individual signaling for example, RRC reconfiguration signaling (see Non-Patent Document 19 (3GPP TS38.331)) may be used, or RRC startup ( RRCSetup) signaling (see Non-Patent Document 19 (3GPP TS38.331)) may be used.
- the information may include information regarding signaling radio bearers.
- the repeater may use the notification to obtain information regarding resources related to transmission and reception of control signals.
- a method different from that in the UE may be used to obtain information regarding the resource at the repeater.
- broadcast information may be used.
- System information for repeaters may be newly provided.
- the system information for repeaters may include, for example, CORESET or information regarding SRB.
- the base station may broadcast the broadcast information.
- the repeater may use the broadcast information to obtain information regarding the resource.
- MAC signaling may be used.
- the MAC signaling may include information similar to that described above. This allows, for example, the base station to quickly notify information regarding the resource.
- L1/L2 signaling may be used. This allows, for example, the base station to notify information regarding the resource more quickly.
- Pre-configured resources may be used.
- the resource may be defined in advance in a standard.
- a correspondence relationship may be provided between the repeater identifier and the preset resource disclosed in the first modification of the first embodiment.
- the repeater may notify the base station of information regarding preconfigured resources.
- the notification may use RRC signaling, MAC signaling, L1/L2 signaling, or may include signaling used for random access, for example, included in random access processing.
- Msg3 and/or MsgA may be used.
- the base station may use the notification to obtain information regarding resources configured in the repeater.
- Combinations of the aforementioned may also be used.
- part of the information regarding the resource may be notified or broadcast using RRC signaling, and the remaining information may be notified using MAC signaling and/or L1/L2 signaling.
- possible candidates may be notified using RRC signaling, and information indicating resources actually used may be notified using MAC signaling and/or L1/L2 signaling. This makes it possible, for example, to quickly notify a large amount of information.
- the repeater can secure resources for receiving control signals from the base station, and as a result, AL transmission and reception can be performed via the repeater.
- a UE may connect to a base station via a repeater.
- a method for connecting a UE to a base station via a repeater is not disclosed. Therefore, a problem arises in that the UE cannot connect to the base station via the repeater.
- the repeater transmits the SS block.
- the UE performs a cell search using the SS block.
- Embodiment 1 may be used to transmit the SS block from the repeater.
- a repeater may receive, amplify, and transmit SS blocks transmitted from a base station.
- the base station may notify the repeater in advance of information regarding the SS block that the repeater should transmit.
- the notification may include, for example, information regarding the identifier of the SS block, information regarding the PCI, information included in the PBCH, and information regarding the transmission of each SS block.
- Information regarding timing may be included, and information regarding frequency resources on which the SS block is transmitted may be included.
- the information may include information regarding PRACH transmission available resources (eg, time/frequency resources) from the UE.
- the repeater may transmit the SS block using the information notified from the base station.
- the repeater may receive and transmit the SS block without the instruction from the base station disclosed in the first embodiment.
- the repeater may acquire information regarding the transmission timing of the SS block by itself. For example, the repeater may use cell search to obtain information regarding the timing. This makes it possible to reduce the size of signaling from the base station to the repeater, for example.
- a repeater may itself assign an SS block identifier to a beam that it can configure. The same may apply to the CSI-RS identifier.
- the base station may assign SS block identifiers to beams on which repeaters can be configured. The same may apply to the CSI-RS identifier.
- the base station may notify the repeater of information regarding the assignment. The notification may use RRC signaling, MAC signaling, or L1/L2 signaling.
- the same SS block identifier to all beams configured by the repeater.
- the assignment may be used if the repeater has a beam.
- the allocation may be used when the repeater does not configure a beam, or when the repeater transmits only SS blocks without using a beam, and performs normal communication, such as notification of UE-specific control signals. , U plane data, etc. may be transmitted using a beam. This makes it possible, for example, to avoid complications in the communication system.
- FIG. 13 is a diagram illustrating an example of assignment of SS block identifiers to beams that can be configured by base stations and repeaters.
- FIG. 13 shows an example in which the same SS block identifier is assigned to all beams configured by the repeater 1302.
- SS block identifiers #1 to #8 are assigned to the beams configured by base station 1301, respectively.
- Repeater 1302 belongs to the beam with SS block identifier #4.
- SS block identifier #4 is assigned to each beam configured by repeater 1302.
- Repeater 1302 uses the SS block transmitted from base station 1301 to transmit the SS block with SS block identifier #4 to UE 1303.
- the UE 1303 performs a cell search using the SS block.
- a different SS block identifier may be assigned to each beam configured by the repeater 1302.
- the beam in which the repeater 1302 is located may be assigned the same SS block identifier as the SS block identifier assigned to the repeater 1302.
- a plurality of SS block identifiers may be redundantly assigned to the beam of the base station 1301.
- the base station 1301 may transmit to the repeater 1302 as many SS blocks as the number of beams configured by the repeater 1302.
- the repeater 1302 may transmit the SS block from the base station 1301 using a beam configured by the repeater itself.
- FIG. 14 is a diagram illustrating another example of assignment of SS block identifiers to beams that can be configured by base stations and repeaters.
- FIG. 14 shows an example in which different SS block identifiers are assigned to each beam configured by the repeater 1302.
- SS block identifiers #1 to #15 are assigned to the beams configured by base station 1301, respectively.
- SS block identifiers #4 to #11 are redundantly assigned to the beam in which the repeater 1302 is located.
- SS block identifiers #4 to #11 are assigned to the beams configured by repeater 1302, respectively.
- base station 1301 may transmit the SS block to repeater 1302 eight times.
- the repeater 1302 may transmit the SS blocks received from the base station 1301 using different beams.
- UE 1303 may perform a cell search using the SS block associated with SS block identifier #5 transmitted from repeater 1302.
- One SS block may include information on multiple SS blocks.
- the information may include multiple SS block identifiers or information on multiple MIBs.
- the base station 1301 may transmit an SS block including information on a plurality of SS blocks to the repeater 1302.
- the repeater 1302 may use an SS block that includes information on a plurality of SS blocks to transmit information on each SS block using each beam that the repeater can configure. This makes it possible, for example, to reduce the number of beam transmissions from the base station 1301 to the repeater 1302, and as a result, it becomes possible to improve the efficiency of the communication system.
- the beam in which the repeater 1302 is located may be assigned an SS block identifier different from the SS block identifier assigned to the repeater 1302.
- the base station 1301 may transmit the SS block to the repeater 1302 only once.
- the repeater 1302 may transmit the SS block from the base station 1301 using a beam configured by the repeater itself.
- FIG. 15 is a diagram illustrating another example of assignment of SS block identifiers to beams that can be configured by base stations and repeaters.
- FIG. 15 shows an example in which SS block identifiers are independently assigned to each beam configured by a base station 1301 and a repeater 1302.
- SS block identifiers #1 to #8 are assigned to the beams configured by base station 1301, respectively.
- SS block identifier #4 is assigned to the beam in which repeater 1302 is located.
- SS block identifiers #9 to #16 are assigned to the beams configured by repeater 1302, respectively.
- the base station 1301 may transmit the SS block to the repeater 1302 once.
- the repeater 1302 may transmit the SS block from the base station 1301 using each of the beams that it configures.
- the UE 1303 may perform a cell search using the SS block associated with SS block identifier #10.
- the same SS block identifier as the beam configured by the base station 1301 may be assigned to a part of the beam configured by the repeater 1302.
- SS block identifier #4 may be assigned to a portion of the beam configured by repeater 1302. This makes it possible, for example, to reduce the number of SS blocks allocated in the communication system, and as a result, it becomes possible to prevent the depletion of SS block identifiers.
- the repeater 1302 may obtain system information in advance.
- the repeater 1302 may obtain system information using broadcast information transmitted from the base station 1301.
- the base station 1301 may notify the repeater of system information in advance.
- RRC signaling, MAC signaling, or L1/L2 signaling may be used for the notification.
- the system information acquired by the repeater 1302 may be, for example, data of a logical channel, data of a transport channel, or data of a physical channel, for example, data after channel encoding. .
- the repeater 1302 may notify or broadcast the acquired system information to the UE 1303. This makes it possible to reduce the amount of signaling from the base station 1301 to the repeater 1302, for example.
- the base station may transmit the SS block multiple times to the repeater.
- Each SS block transmitted from the base station to the repeater may include information regarding multiple SS blocks.
- FIG. 16 is a diagram illustrating another example of assignment of SS block identifiers to beams that can be configured by base stations and repeaters.
- FIG. 16 shows an example in which the base station 1301 transmits an SS block including information of a plurality of SS blocks multiple times to the repeater 1302.
- SS block identifiers #1 to #15 are assigned to the beams configured by base station 1301, respectively.
- SS block identifiers #4 to #11 are assigned to the beams in which the repeater 1302 is located.
- SS block identifiers #4 to #11 are assigned to the beams configured by repeater 1302, respectively.
- the base station 1301 may transmit the SS block to the repeater 1302 twice.
- the first SS block transmission from base station 1301 to repeater 1302 includes information held by SS block identifiers #4 to #7.
- the second SS block transmission 1302 from the base station 1301 to the repeater includes information held by SS block identifiers #8 to #11.
- the UE 1303 may perform a cell search using the SS block associated with SS block identifier #5.
- the UE 1303 performs a cell search using the SS block transmitted from the repeater 1302.
- the UE 1303 uses the SS block to obtain system information.
- the UE 1303 may use the SS block to obtain information regarding time/frequency resources on which system information is transmitted.
- the UE 1303 performs random access to the base station 1301 via the repeater 1302.
- the UE 1303 may transmit the PRACH at the PRACH transmission timing corresponding to the SS block identifier transmitted from the repeater 1302.
- Repeater 1302 may obtain information regarding PRACH transmission timing from UE 1303.
- the method disclosed in Embodiment 1 may be used to acquire this information in repeater 1302.
- the base station 1301 may notify the repeater 1302, or the repeater 1302 may obtain the information using broadcast information from the base station 1301.
- a beam configured by a repeater may be provided with multiple identifiers.
- the plurality of identifiers may include, for example, a beam identifier of the base station and/or the repeater used for communication between the base station and the repeater, and a beam identifier used between the repeater and the UE. good.
- a plurality of TCI states may be configured, for example, a TCI state between a base station and a repeater, and a TCI state between a repeater and a UE. This makes it possible, for example, to avoid complications in the communication system.
- Modification 3 has been mainly described with respect to SS blocks, it may also be used with respect to CSI-RS. As a result, for example, the same effect as the SS block can be obtained with respect to CSI-RS beam assignment.
- Modification 3 allows a UE to connect to a base station via a repeater, and as a result, it becomes possible to expand the coverage of the communication system.
- Embodiment 2 The repeater itself needs to connect to the base station.
- a UE may connect to a base station via a repeater.
- the method for connecting the repeater to the base station is not disclosed.
- the repeater receives the SS block from the base station and performs a cell search. Repeaters obtain system information from base stations. The repeater performs random access with the base station.
- the repeater transmits PRACH to the base station.
- the repeater may use system information transmitted from the base station to obtain information regarding time/frequency resources available for PRACH transmission.
- the repeater may use the same RA (Random Access) preamble as the UE. This makes it possible, for example, to avoid complexity in the communication system.
- RA preamble field for repeaters may be provided.
- the repeater may select an RA preamble from the area and use it for PRACH transmission. This makes it possible to avoid, for example, RA preamble collision between the repeater and the UE, and as a result, it becomes possible to quickly complete random access at the repeater and the UE.
- the base station may broadcast information regarding the RA preamble area to be allocated to the repeater.
- the repeater may use this information to select the RA preamble.
- the UE may use this information to select the RA preamble. For example, the UE may not use the information to select the RA preamble included in the repeater RA preamble area. That is, the UE may select an RA preamble from an area other than the repeater RA preamble area. This allows for example to avoid duplicate RA preamble selections between the repeater and the UE.
- the base station transmits a random access response (RAR) to the repeater.
- RAR random access response
- the RAR that a base station transmits to a repeater may include a temporary C-RNTI used by the repeater.
- a repeater may obtain the temporary C-RNTI used by the repeater from the RAR.
- the repeater may transmit Msg3 to the base station.
- the temporary C-RNTI acquired by the repeater may be used, or the RNTI disclosed in Modification 1 of Embodiment 1 may be used.
- An RRC connection may be established between the repeater and the base station.
- Msg3 may include RRC startup request signaling (see Non-Patent Document 19 (3GPP TS38.331)).
- the base station may transmit Msg4 to the repeater.
- the base station may transmit Msg4 in response to Msg3 from the repeater.
- Two-step random access may be used for random access between the base station and the repeater. This makes it possible to quickly execute random access processing between the base station and the repeater, for example.
- a repeater may notify the base station of information regarding its own repeater.
- Msg3 may be used for this notification
- MsgA in 2-step random access may be used, or other signaling such as RRC setup completion (RRCSetupComplete) (Non-patent Document 19) (Refer to 3GPP TS38.331)) may be used.
- RRC setup completion RRCSetupComplete
- Non-patent Document 19 Non-patent Document 19
- the information may be included in a capability (eg, UE capability) and notified.
- the information in (A) above may include information indicating that the user is a repeater.
- the information may include information regarding the type of repeater.
- the information regarding the type of repeater may be, for example, information indicating that it is a smart repeater, information indicating that it is a conventional repeater, or information indicating that it is an RIS. Alternatively, it may be information indicating that it is a conventional reflector.
- the base station may recognize that the communication partner is a repeater using the information in (A) above. This allows, for example, the base station to transmit control signals to the repeater.
- the information in (B) above may include information regarding the number of beams that the own repeater can support.
- the information regarding the number of beams may be the number of beams that transmit SS blocks or the number of beams that transmit CSI-RS.
- the base station may use the information to allocate SS blocks to repeaters and determine which beams to use for communication with the UE. This makes it possible to avoid, for example, the complexity associated with controlling the repeater from the base station.
- the above information (C) may include information regarding the distance over which the own repeater can transmit and receive.
- the transmission/reception distance may be provided for each of the SS block and CSI-RS, for example.
- the base station may use this information to perform power control in transmission and reception with the UE. This makes it possible, for example, to reduce power consumption in the repeater, and to prevent transmission failure from the repeater to the UE due to insufficient power.
- the information in (D) above may include information regarding the transmission power that can be transmitted by the own repeater.
- the base station may use the information to determine the transmit power of the repeater. This makes it possible, for example, to reduce power consumption in the repeater, and to prevent transmission failure from the repeater to the UE due to insufficient power.
- the above information (E) may include information regarding the reception power that can be received by the own repeater.
- the base station may use this information to determine the power to be transmitted from its own base station to the repeater, or may determine the transmission power for the UE. This makes it possible to prevent performance deterioration in transmission and reception between the base station and the UE via the repeater, for example.
- the above-mentioned information (F) may include, for example, the information regarding the processing time disclosed in the first embodiment.
- the base station may perform UE scheduling using the information in (F) above. This allows, for example, the base station to schedule UEs connected via repeaters.
- the base station may also set up a repeater.
- the base station may perform the setting using information regarding the repeater, for example, the information in (A) to (G) described above.
- the base station may notify the repeater of the settings.
- the settings notified from the base station to the repeater may include information related to (1) to (14) above, information regarding the SS block transmitted by the repeater, or information regarding the SS block transmitted by the repeater.
- the notification from the base station to the repeater may use RRC signaling, for example, RRC Reconfiguration signaling, MAC signaling, or L1/L2 signaling. Good too.
- the repeater may use the notification from the base station to determine the beam it uses.
- FIG. 17 is a diagram showing an example of a sequence for connecting a repeater to a base station.
- FIG. 17 shows an operation in which a repeater connects to a base station, and then a UE connects to the base station via the repeater.
- arrows with black circles indicate that signal transmission and reception between the base station and the UE is performed via a repeater.
- step ST1701 shown in FIG. 17 the repeater receives the SS block transmitted by the base station.
- step ST1703 the repeater performs a cell search using the SS block in step ST1701.
- step ST1705 the repeater receives the system information transmitted by the base station.
- step ST1707 the repeater uses the system information in step ST1705 to determine whether connection to the base station is possible. For this determination in the repeater, information regarding PLMN included in the system information may be used, or information regarding NPN (Non-Public Network) may be used. In the example shown in FIG. 17, the repeater determines that it can connect to the base station.
- NPN Non-Public Network
- step ST1709 shown in FIG. 17 the repeater transmits PRACH to the base station.
- the repeater may acquire information regarding time/frequency resources used for PRACH transmission from step ST1705.
- the repeater may perform PRACH transmission in step ST1709 using the acquired information regarding the resource.
- the base station transmits RAR to the repeater.
- Step ST1711 may include information regarding the scheduling grant used for transmitting Msg3, or may include information regarding the identifier (eg, temporary C-RNTI) assigned to the repeater.
- step ST1713 shown in FIG. 17 the repeater transmits Msg3 to the base station.
- Msg3 may include signaling of an RRC startup request.
- Msg3 may include information regarding the repeater, for example, the above-mentioned (A) to (G). The above (A) to (G) may be included in the RRC startup request signaling.
- the base station transmits Msg4 to the repeater.
- the repeater recognizes that the random access to the base station has been successful.
- Step ST1715 may include RRC startup (RRCSetup) signaling.
- the repeater may perform RRC startup using the signaling.
- the repeater notifies the base station of the completion of RRC startup. The notification may be performed using, for example, signaling of RRC setup completion (RRCSetupComplete).
- the base station inquires of the repeater about its capabilities.
- the inquiry may be performed using UE capability inquiry signaling.
- the repeater may notify the base station of its own capabilities. For example, signaling of UE capability information may be used for the notification.
- step ST1723 shown in FIG. 17 the base station determines settings to be made to the repeater.
- step ST1725 the base station instructs the repeater to configure the repeater.
- the instruction may include information regarding the beams configured by the repeater, the information in (1) to (14) above, or information regarding the SS block transmitted by the repeater. It may also include system information sent by the repeater.
- the instruction in step ST1725 may be performed using, for example, RRC reconfiguration signaling.
- the repeater uses the instruction to configure its own repeater settings.
- step ST1731 shown in FIG. 17 the repeater transmits the SS block.
- the transmission may be performed using the information included in step ST1725.
- step ST1733 the UE performs a cell search.
- the UE may perform a cell search upon receiving step ST1731.
- step ST1735 the UE receives the system information transmitted by the repeater.
- step ST1737 the UE uses the system information in step ST1735 to determine whether connection to the base station is possible. For this determination in the UE, information regarding the PLMN included in the system information may be used, or information regarding the NPN may be used. In the example shown in FIG. 17, the UE determines that it can connect to the base station.
- step ST1739 shown in FIG. 17 the UE transmits the PRACH to the base station.
- the transmission in step ST1739 may be performed via a repeater.
- the repeater may perform transmission and reception in step ST1739 using the system information acquired in step ST1725.
- step ST1740 shown in FIG. 17 the base station instructs the repeater to set up a beam.
- the instruction may include information regarding the beam used by the repeater, information indicating that the repeater will transmit and receive downlink signals, and information regarding time/frequency resources for transmitting and receiving the repeater. It's okay.
- the base station transmits RAR to the UE.
- the transmission in step ST1741 may be performed via a repeater.
- the repeater may perform transmission and reception in step ST1741 using the settings acquired in step ST1740.
- step ST1742 shown in FIG. 17 the base station instructs the repeater to set a beam.
- the instruction may include information regarding the beam used by the repeater, information indicating that the repeater will transmit and receive uplink signals, and information regarding time/frequency resources for transmitting and receiving by the repeater. It's okay.
- the UE transmits Msg3 to the base station.
- the transmission in step ST1743 may be performed via a repeater.
- the repeater may perform transmission and reception in step ST1743 using the settings acquired in step ST1742.
- step ST1744 shown in FIG. 17 the base station instructs the repeater to set up a beam.
- the instruction may include information regarding the beam used by the repeater, information indicating that the repeater will transmit and receive downlink signals, and information regarding time/frequency resources for transmitting and receiving the repeater. It's okay.
- step ST1745 the base station transmits Msg4 to the UE.
- the transmission in step ST1745 may be performed via a repeater.
- the repeater may perform transmission and reception in step ST1745 using the settings acquired in step ST1744.
- the repeater transmits information regarding its own repeater to the base station in Msg3, but the information may be transmitted in step ST1717 or in step ST1721. You can also use it as This makes it possible, for example, to quickly perform random access processing between the repeater and the base station.
- the above-mentioned (A) to (G) are included as the information regarding the own repeater transmitted from the repeater to the base station in step ST1713, but the above-mentioned (A) to A part of (G) may be included. Some of the above (A) to (G) may be transmitted in step ST1717, and some of the above (A) to (G) may be transmitted in step ST1721. This allows, for example, increased flexibility in the communication system.
- the example shown in FIG. 17 shows an example in which the base station notifies the repeater of information regarding the SS block in step ST1725
- the information regarding the SS block may not be notified.
- the repeater may receive the SS block and/or system information transmitted from the base station as is, and transmit it to the UE. By this, for example, the amount of signaling related to step ST1725 can be reduced.
- the repeater may not be registered in the core NW. This makes it possible, for example, to quickly connect a repeater to a communication system.
- a NAS connection between a repeater and an AMF may be established.
- a repeater may be registered with the core NW.
- the repeater may obtain information regarding the policy from the core NW device.
- the information regarding the policy may include a policy as a repeater.
- the repeater may perform AL transmission and reception using the policy acquired from the core NW device.
- the core NW device can control the communication system in consideration of the presence of repeaters.
- the base station may instruct the repeater to stop and/or deactivate the repeater.
- RRC signaling For this instruction, RRC signaling, MAC signaling, or L1/L2 signaling may be used.
- RRC signaling RRC reconfiguration (RRCReconfiguration), RRC suspension (RRCSuspend), and RRC release (RRCRelease) may be used.
- the repeater may use the instructions from the base station to stop and/or deactivate AL transmissions and receptions. This makes it possible, for example, to stop a repeater that is not under the UE's control, and as a result, it becomes possible to reduce power consumption in the communication system.
- the base station may instruct the repeater to start and/or activate the repeater.
- RRC signaling For this instruction, RRC signaling, MAC signaling, or L1/L2 signaling may be used.
- RRC signaling RRC reconfiguration (RRCReconfiguration), RRC return (RRCResume), or RRC startup (RRCSetup) may be used.
- the repeater may use the instructions from the base station to initiate and/or activate AL transmissions and receptions.
- Random access may not be performed between the base station and the repeater.
- the repeater may establish downlink synchronization with the base station.
- the repeater may establish downlink synchronization with the base station, for example, using cell search of the base station.
- the repeater may establish uplink synchronization with the base station.
- the repeater may transmit SRS or PUCCH to the base station.
- the resources e.g., time, frequency, code
- the base station may notify the repeater of information regarding the TA.
- the repeater may use this information about the TA to modify the uplink transmission timing.
- MAC signaling or L1/L2 signaling may be used to transmit the information regarding the TA from the base station to the repeater.
- a new DCI may be provided and used.
- the repeater can be connected to the base station, and as a result, transmission and reception between the base station and the UE via the repeater is possible.
- L1/L2 signaling may be used to control the repeater from the base station.
- a repeater may have a protocol for handling L1/L2 signaling.
- the repeater cannot process the signaling disclosed above, and as a result, the repeater cannot connect to the base station, making transmission and reception between the base station and the UE via the repeater impossible. A problem arises.
- Embodiment 3 discloses a method for solving the above-mentioned problems.
- the repeater has a C-plane protocol stack.
- the repeater may not have a U-plane protocol.
- the repeater may have a PHY protocol or a MAC protocol. This allows, for example, control from the base station to the repeater using MAC signaling, and as a result, the base station can transmit a large amount of information to the repeater.
- the repeater may have an RLC protocol, a PDCP protocol, or an RRC protocol. This allows, for example, control from the base station to the repeater using RRC signaling, and as a result, the base station can transmit more information to the repeater.
- a repeater may have an RRC state.
- the RRC state that a repeater has may be one or more of RRC_CONNECTED, RRC_INACTIVE, and RRC_IDLE. This makes it possible, for example, to avoid the complexity of controlling repeaters in communication systems.
- the repeater may have a NAS protocol.
- the repeater's NAS protocol may be used, for example, in connecting the repeater to a communication system. This allows, for example, a repeater to connect to the core NW, and as a result, a core NW device, such as an AMF, can recognize the connection of the repeater, thereby making it possible to avoid complications regarding the management of the communication system.
- a repeater may have a CM state.
- the CM state that the repeater has may be, for example, CM_CONNECTED or CM_IDLE. This makes it possible, for example, to avoid the complexity of controlling repeaters in communication systems.
- a repeater may have an RM state.
- the RM state that the repeater has may be, for example, RM_REGISTERED or RM_DEREGISTERED. This makes it possible, for example, to avoid the complexity of controlling repeaters in communication systems.
- FIG. 18 is a diagram showing an example of a C-plane protocol stack of a base station (gNB) and a repeater.
- the protocol stack shown in FIG. 18 may be used, for example, when connecting a repeater to a base station, or when notifying system information from a base station to a repeater.
- radio In the protocol stack shown in FIG. 18, radio (RF), PHY, MAC, RLC, PDCP, and RRC protocols are terminated between the base station (gNB) and the repeater.
- FIG. 19 is a diagram showing an example of the C-plane protocol stack of the AMF, base station (gNB), and repeater.
- the protocol stack shown in FIG. 19 may be used, for example, when connecting a repeater to a core NW.
- radio In the protocol stack shown in FIG. 19, radio (RF), PHY, MAC, RLC, PDCP, and RRC protocols are terminated between the base station (gNB) and the repeater. Between the base station and AMF, L1/L2, IP, SCTP (Stream Control Transmission Protocol, see Non-Patent Document 32), NG-AP (Next Generation Application Protocol, see Non-Patent Document 21 (3GPP TS38.413)) Each protocol is terminated. The NAS protocol is terminated between the repeater and the AMF. Between the repeater and the base station, NAS protocol signaling (also referred to as NAS signaling) is encapsulated into RRC protocol signaling. Between the base station and the AMF, NAS signaling is encapsulated in NG-AP protocol signaling.
- NAS protocol signaling also referred to as NAS signaling
- FIG. 20 is a diagram showing an example of a C-plane protocol stack of a base station (gNB) and a repeater.
- the protocol stack shown in FIG. 20 may be used, for example, in beam control from a base station to a repeater.
- radio (RF) and PHY protocols are terminated between the base station (gNB) and the repeater.
- Beam control instructions from the base station to the repeater are performed using PHY protocol signaling, for example, L1/L2 signaling.
- FIG. 21 is a diagram showing an example of a C-plane protocol stack of a base station (gNB), a repeater, and a UE.
- the protocol stack shown in FIG. 21 may be used, for example, in system information notification from a base station to a UE.
- radio (RF), PHY, MAC, RLC, PDCP, and RRC protocols are mutually terminated between the base station and the repeater and between the repeater and the UE.
- the repeater may maintain system information sent from the base station to the UE.
- the repeater may transmit the maintained system information to the UE.
- FIG. 22 is a diagram showing another example of the C-plane protocol stack of the base station (gNB), repeater, and UE.
- the protocol stack shown in FIG. 22 may be used, for example, in transmitting and receiving RRC signaling between a base station and a UE.
- radio is mutually terminated between the base station and the repeater and between the repeater and the UE.
- PHY, MAC, RLC, PDCP, and RRC protocols are terminated between the base station and the UE.
- the repeater may receive, amplify, and transmit RRC signaling sent from the base station to the UE.
- a repeater may receive RRC signaling sent from a UE to a base station, amplify it, and transmit it to the base station.
- the repeater may not have a U-plane protocol.
- RRC may be replaced with SDAP.
- the repeater may have a U-plane protocol.
- a repeater may have part of the PHY protocol.
- a portion of the PHY protocol that the repeater has may be a PHY low layer section (PHY-Low) (see Non-Patent Document 33 (“O-RAN Fronthaul Specification Overview”)).
- PHY-Low PHY low layer section
- Some PHY protocols that the repeater has may include precoding, digital beamforming, and Inverse Fast Fourier Transform (IFFT). However, analog conversion, analog beamforming, or fast Fourier transform may be included.
- IFFT Inverse Fast Fourier Transform
- the repeater may perform reception processing using the PHY-Low protocol on signals transmitted from the base station.
- a repeater may perform reception processing using analog beamforming, may perform analog/digital conversion, may perform Fourier transformation, or may perform reception processing using digital beamforming. It's okay.
- the repeater may perform transmission processing using the PHY-Low protocol on the signal that has undergone reception processing using the PHY-Low protocol.
- the repeater may perform precoding, may perform transmission processing using digital beamforming, may perform inverse Fourier transform, may perform digital/analog conversion, Transmission processing using analog beamforming may also be performed.
- the repeater may transmit the signal that has undergone the transmission processing to the UE. The aforementioned operation may be performed in downlink communication.
- the repeater may perform reception processing using the PHY-Low protocol on a signal transmitted from a base station, or may perform reception processing using the PHY-Low protocol on a signal that has undergone reception processing on the PHY-Low protocol. Transmission processing may be performed, or the signal subjected to the transmission processing may be transmitted to the base station.
- Operations similar to those described above may be performed in sidelink communication, that is, in a repeater that relays signals between two UEs performing sidelink communication.
- the repeater may perform reception processing using the PHY-Low protocol on a signal transmitted from the UE, or may perform reception processing using the PHY-Low protocol on a signal that has undergone reception processing on the PHY-Low protocol.
- the processing may be performed, or the signal subjected to the transmission processing may be transmitted to other UEs.
- FIG. 23 is a diagram showing an example of a U-plane protocol stack of a base station (gNB), a repeater, and a UE.
- FIG. 23 may be used, for example, in U-plane data transmission and reception between a base station and a UE.
- the protocol stack shown in FIG. 23 shows an example where the repeater has PHY-Low.
- radio (RF) and PHY-Low protocols are mutually terminated between the base station and the repeater and between the repeater and the UE.
- PHY-High, MAC, RLC, PDCP, and SDAP protocols are terminated between the base station and the UE.
- the repeater performs reception PHY-Low protocol processing on U-plane data received from the base station.
- the repeater performs PHY-Low protocol processing for transmission on the U-plane data that has undergone PHY-Low protocol processing, and transmits it to the UE. Similar processing is performed on U-plane data transmitted from the UE to the base station.
- the base station may notify the repeater of information regarding PHY-Low protocol processing.
- the information may include, for example, information regarding precoding (eg, a precoding matrix) or information regarding beamforming.
- the notification may be performed using the method disclosed in Embodiment 1, for example.
- the information may be notified in the same manner as the information (1) to (14) disclosed in the first embodiment, for example.
- the repeater may use this information to perform PHY-Low protocol processing.
- U-plane communication may be performed between the base station and the repeater.
- the repeater may have a U-plane protocol.
- the U-plane protocol that the repeater has may be, for example, the same U-plane protocol as that of the UE.
- the protocol may include, for example, SDAP or a PDU layer.
- a PDU session may be established between the repeater and UDP.
- U-plane communication between the base station and the repeater may be used, for example, to update data held by the repeater, for example, to update firmware. This makes it possible, for example, to update the firmware of the repeater without compressing the C-plane communication band between the base station and the repeater.
- the repeater can receive control signals from the base station, and as a result, transmission and reception between the base station and the UE via the repeater becomes possible.
- Embodiment 4 In the 5G wireless access system, communication for a wide variety of services is performed. In order to enable such communication, for example, support for high-speed mobile terminals and support for a large number of TRPs (Transmission Reception Points) are also being considered. Such systems require reductions in delay time, overhead, and interruption time in mobility control. In response to such demands, in 3GPP, it has been proposed to perform inter-cell mobility control using a control technology (L1/L2 mobility) that does not involve RRC (Non-Patent Document 30). However, no specific method for performing inter-cell mobility control using L1/L2 mobility is disclosed. For this reason, a problem arises in that inter-cell mobility control cannot be realized by L1/L2 mobility, and delay time etc. during mobility cannot be reduced.
- L1/L2 mobility control technology
- RRC Non-Patent Document 30
- FIG. 24 is a conceptual diagram of inter-cell L1/L2 mobility.
- Inter-cell L1/L2 mobility is inter-cell mobility, ie, cell change, by L1/L2 processing.
- FIG. 24 shows inter-cell L1/L2 mobility within one gNB.
- gNB is composed of one CU and one or more DUs connected to the CU.
- the CU has RRC, SDAP, and PDCP protocols.
- DU has RLC, MAC, and PHY protocols.
- CU and DU are connected by an F1 interface.
- two DUs (DU#1, DU#2) are connected to a CU to configure one gNB.
- a DU connects with one or more TRPs.
- FIG. 24 is a conceptual diagram of inter-cell L1/L2 mobility.
- Inter-cell L1/L2 mobility is inter-cell mobility, ie, cell change, by L1/L2 processing.
- FIG. 24 shows inter-cell L1/L2 mobility within one gNB.
- DU#1 is connected to TRP#11 to TRP#13.
- DU#2 is connected to TRP#21 to TRP#23.
- gNB constitutes one or more cells. For example, in FIG. 24, each TRP is used to configure a cell.
- Cell #n is configured using TRP #n.
- communication with a UE in the cell is performed via the TRP that configures the cell.
- Inter-cell L1/L2 mobility will be explained.
- UE #1 is connected to cell #11. Due to the movement of UE #1, the cell to which UE #1 connects is changed from cell #11 to cell #12. The beam used for communication with UE #1 is also changed.
- the cell change is performed by L1/L2 mobility processing.
- the cell change may be referred to as HO. This cell change is sometimes referred to as mobility.
- Inter-cell L1/L2 mobility including cell changes between different DUs will be described.
- UE #2 is connected to cell #13. Due to the movement of UE #2, the cell to which UE #2 connects is changed from cell #13 to cell #21. The beam used for communication with UE #2 is also changed.
- Cell #13 is configured by DU #1
- cell #21 is configured by DU #2. Therefore, the cell to which UE #2 connects between different DUs is changed. In this way, cell changes including cell changes between different DUs are performed by L1/L2 mobility processing.
- the gNB determines a cell that is a candidate target cell in inter-cell L1/L2 mobility.
- the cell may be referred to as a candidate cell.
- the candidate cell may be a candidate for PCell. It may also be a candidate cell when the PCell is changed due to mobility. It may also be used for changing PCell within MCG.
- the candidate cell may be a PSCell candidate. It may also be a candidate cell when the PSCell is changed due to mobility. It may also be used for changing the PSCell within the SCG.
- Conventional mobility control includes CHO (Conditional HO) (see Non-Patent Document 2 (3GPP TS38.300)).
- Candidate cells are used in CHO.
- CHO cannot be applied to L1/L2 mobility because it is L3 mobility, which is mobility control involving conventional RRC. It is preferable to determine candidate cells for target cells in inter-cell L1/L2 mobility separately from candidate cells for CHO. Unless otherwise specified, a candidate cell for inter-cell L1/L2 mobility will be referred to as a candidate cell.
- candidate cells may be limited to serving cells.
- candidate cells may be determined from cells that have been set as serving cells. By doing so, it is possible to simplify the candidate cell setting process and reduce the amount of signaling and information required for the process.
- the gNB may determine candidate beams for one or more targets. This beam may be referred to as a candidate beam. The gNB may use some or all of the beams of the candidate cell as candidate beams. The gNB may determine candidate antenna ports for one or more targets. The antenna port may be referred to as a candidate AP (Antenna Port). The gNB may use some or all of the antenna ports of the candidate cell as candidate APs. The gNB may determine one or more candidate antenna panels for the target. The antenna panel may be referred to as a candidate panel. The gNB may use some or all of the antenna panels of the candidate cell as candidate panels. Unless otherwise specified hereinafter, candidate cells may include candidate beams, candidate APs, and candidate panels.
- the node that determines candidate cells is gNB.
- a source gNB (S-gNB) that is a HO source in inter-cell L1/L2 mobility may determine a candidate cell or the like.
- the CU of the gNB may determine the candidate cells. By doing so, for example, cells under the CU can be easily set as candidate cells.
- Candidate cells can be determined from a larger number of cells.
- the gNB's DU may determine the candidate cell. By determining candidate cells based on DU, for example, candidate cells can be easily determined using L1 measurement results.
- Candidate cells determined for CU and DU may be different.
- the CU may determine candidate cells, and the DU may determine candidate beams and candidate APs.
- candidate cells may be determined by RRC, and candidate beams and candidate APs may be determined by MAC or PHY.
- the DU may transmit information regarding the determined candidate beams and candidate APs to the CU.
- the DU may transmit information regarding the determined candidate beams and candidate APs to the UE.
- the DU may transmit information regarding candidate beams and candidate APs to the UE in association with the candidate cell determined by the CU. By doing so, it becomes possible to flexibly set candidate cells in each process of CU and DU.
- 3GPP provides a measurement method for measuring reception quality in which measurement results are reported using RRC messages (see Non-Patent Document 2 (3GPP TS38.300)).
- this measurement method will be referred to as L3 measurement.
- the L3 measurement results include cell measurement results and beam measurement results.
- 3GPP provides a measurement method in which the measurement result is included in the UCI and reported as a measurement of reception quality (see Non-Patent Document 12 (3GPP TS38.212)).
- this measurement method will be referred to as L1 measurement.
- the L1 measurement results include CSI-RS measurement results and SSB measurement results.
- L1/L2 mobility is processed in the MAC layer (hereinafter sometimes referred to as MAC) and the PHY layer (hereinafter sometimes referred to as PHY). Since the MAC and PHY are configured for each DU, they are processed for each DU.
- the source DU (S-DU) that constitutes the cell (source cell (S-Cell)) before the inter-cell L1/L2 mobility and the inter-cell L1/L2 mobility is different.
- the S-PCell (source PCell) (which may be an S-DU) decides to change cells
- the T-PCell ( The target PCell (which may be a T-DU) cannot recognize it.
- the T-PCell is no longer able to perform scheduling for the UE, and communication between the UE and the T-PCell is no longer possible.
- Embodiment 4 discloses a method for solving such problems.
- FIGS. 25 and 26 are sequence diagrams illustrating an example of an inter-cell L1/L2 mobility processing method within a DU in accordance with the fourth embodiment.
- FIG. 25 shows the first half of the sequence
- FIG. 26 shows the second half of the sequence.
- the candidate cell is configured in the same DU as the source cell (S-PCell).
- the UE connects to the source cell of DU #1, and data communication is performed between the source cell of DU #1, the CU, and the UPF.
- the CU transmits measurement settings to the UE via the DU. In the example shown in FIG. 25, L3 measurement settings are transmitted.
- step ST2504 the UE performs L3 measurement using the received measurement settings.
- step ST2505 the UE transmits the L3 measurement result to the source cell.
- step ST2506 DU #1 configuring the source cell transmits the L3 measurement result received from the UE to the CU.
- the CU determines candidate cells for inter-cell L1/L2 mobility.
- the CU may use the L3 measurement results received from the UE via DU #1.
- the number of candidate cells to be determined is not limited to one, but may be multiple.
- the candidate cells may include source cells. It is preferable that the CU determines candidate cells, allocates candidate cell identifiers, and configures candidate cells.
- the CU notifies the DU of information instructing the UE to perform inter-cell L1/L2 mobility processing. Information regarding inter-cell L1/L2 mobility may be transmitted.
- the information regarding inter-cell L1/L2 mobility may include, for example, the identifier of the target UE, the candidate cell identifier assigned to the determined candidate cell, the candidate cell settings, and the like.
- Candidate cell settings may be configured using, for example, ServingCellConfig information used in the RRC message. This allows DU #1 to start L1/L2 mobility processing between cells within DU #1 for the UE.
- step ST2509 DU #1 notifies the CU of the response to the inter-cell L1/L2 mobility processing setting instruction.
- the response may notify that inter-cell L1/L2 mobility processing configuration has been completed.
- the response may indicate whether or not inter-cell L1/L2 mobility processing can be set.
- DU #1 may send an acknowledgment if the setting is possible. If the setting is not possible, it is recommended to send a rejection response. Reason information may be included in the rejection response. By doing so, the CU can recognize whether or not a candidate cell has been set in DU #1.
- DU #1 notifies the UE from the source cell of information instructing execution of inter-cell L1/L2 mobility processing.
- Information regarding inter-cell L1/L2 mobility may be transmitted.
- the information regarding inter-cell L1/L2 mobility may include, for example, a candidate cell identifier to be assigned to the determined candidate cell, candidate cell settings, and the like.
- Candidate cell settings may be configured using, for example, ServingCellConfig information used in the RRC message. This allows the UE to start L1/L2 mobility processing between cells within DU #1.
- step ST2511 the UE notifies the source cell of DU #1 of a response to the inter-cell L1/L2 mobility processing setting instruction.
- the response may notify that inter-cell L1/L2 mobility processing configuration has been completed.
- DU #1 can recognize whether a candidate cell has been configured in the UE.
- DU #1 which has received the response to the inter-cell L1/L2 mobility processing setting instruction from the UE in step ST2511, may notify the CU that the UE has completed the inter-cell L1/L2 mobility processing setting. By doing so, the CU can recognize whether the UE has completed the inter-cell L1/L2 mobility processing setting.
- the signaling in step ST2509 may be used for this notification.
- the signaling in step ST2509 may include information as to whether the UE has completed the inter-cell L1/L2 mobility processing settings.
- the signaling in step ST2509 may be performed after step ST2511. The amount of signaling can be reduced.
- step ST2512 the CU transmits the L1 measurement settings for inter-cell L1/L2 mobility of the candidate cell to DU #1.
- CSI-MeasConfig information used in the RRC message may be used.
- the source cell of DU #1 transmits the L1 measurement configuration for inter-cell L1/L2 mobility of the candidate cell to the UE.
- the UE can recognize the L1 measurement configuration for inter-cell L1/L2 mobility of the candidate cell.
- the UE performs L1 measurement settings for the candidate cell received from the source cell of DU #1.
- step ST2514 the UE that has configured the L1 measurement settings for the candidate cell transmits the completion of L1 measurement settings for the candidate cell to the source cell of DU #1. This allows DU #1 to recognize that the UE has completed the L1 measurement settings for the candidate cell.
- Transmission of L1 measurement settings for inter-cell L1/L2 mobility of a candidate cell may be included in the notification of information instructing the UE to perform inter-cell L1/L2 mobility processing.
- Step ST2508 and Step ST2510 may include setting of L1 measurement for inter-cell L1/L2 mobility of the candidate cell. Signaling in step ST2512, step ST2513, and step ST2514 can be reduced. It is possible to reduce the delay time of inter-cell L1/L2 mobility processing.
- DU#1 which has received the response to the L1 measurement settings for the candidate cell from the UE in step ST2514, may notify the CU that the UE has completed the L1 measurement settings for the candidate cell.
- F1 signaling may be used for this notification.
- a UL RRC MESSAGE TRANSFER message may be used. By doing so, the CU can recognize whether the UE has completed the L1 measurement settings for the candidate cell.
- step ST2515 the source cell of DU #1 transmits the act/deact settings of the candidate cell to the UE.
- MAC signaling is used.
- the UE that has received the act/deact settings of the candidate cell performs L1 measurement of the activated candidate cell in step ST2516. By transmitting the act/deact settings of the candidate cell, the power consumption of the UE can be reduced.
- the UE that has received the L1 measurement configuration of the candidate cell from the source cell of DU #1 in step ST2513 may perform L1 measurement of all candidate cells in step ST2516.
- step ST2517 the UE transmits the L1 measurement result of the candidate cell to the source cell.
- step ST2518 DU #1, which has received the L1 measurement result of the candidate cell from the UE, decides to change the cell for the UE. In the example shown in FIG. 26, it is determined to change the PCell.
- DU #1 may notify the CU of the cell change result.
- the notification may include information regarding the cell change. For example, UL MESSAGE TRANSFER may be used for the notification. By doing so, the CU can recognize the change in the cell of the UE.
- DU #1 which has decided to change the cell of the UE in step ST2518, may notify the UE from the source cell that the cell has been changed to the target cell.
- the candidate cell identifier of the target cell may be transmitted in the notification.
- MAC signaling is used for the notification. By using MAC signaling, DU #1 can decide to change cells and transmit information about the decided target cell to the UE.
- step ST2521 DU #1 transmits the candidate cell identifier of the target cell, the TCI-state information of the target cell, and the act/deact information of the TCI-state from the source cell to the UE.
- TCI-state information By transmitting TCI-state information, the UE can learn about the beams used in the target cell.
- MAC signaling is used for the notification.
- DU #1 can decide to change cells and transmit information about the decided target cell and beam information in the target cell to the UE.
- step ST2522 the UE changes the PCell to the target cell.
- step ST2523 DU #1 transmits scheduling information from the target cell using PDCCH.
- the UE receives the PDCCH of the target cell using the TCI-state received in step ST2521. By doing so, the UE can receive the PDCCH of the beam of the target cell. The UE is now able to obtain scheduling information.
- step ST2524 the UE becomes capable of data communication between the target cell of DU #1 (PCell after change), CU, and UPF.
- the L1 measurement by the UE the reporting of the L1 measurement results, the determination of cell change in steps ST2516 to ST2518, the notification of cell change, and the TCI-state information of the target cell in steps ST2520 to ST2523.
- notification, cell change, and PDCCH transmission from the beam of the target cell can be performed between the UE and DU #1.
- This can be implemented using only L1/L2 control. Therefore, inter-cell L1/L2 mobility can be performed at an early stage.
- FIGS. 27 and 28 are sequence diagrams illustrating an example of an inter-cell L1/L2 mobility processing method including cell change between different DUs according to the fourth embodiment.
- FIG. 27 shows the first half of the sequence
- FIG. 28 shows the second half of the sequence. Steps common to those in FIGS. 25 and 26 are given the same step numbers, and common explanations will be omitted.
- the examples in FIGS. 27 and 28 disclose a case where the UE decides to change cells.
- the CU determines candidate cells for inter-cell L1/L2 mobility.
- the CU may determine, as a candidate cell, a cell configured by a DU different from the DU that configures the source cell.
- three cells each constituted by DU #2, DU #3, and DU #4 are determined to be candidate cells (Candidate Cell #1, Candidate Cell #2, Candidate Cell #3).
- the CU transmits information regarding inter-cell L1/L2 mobility to the candidate DUs (DU#2, DU#3, DU#4) constituting the candidate cell.
- the CU may transmit information regarding inter-cell L1/L2 mobility to the source DU (DU #1).
- Each candidate DU that has received information regarding inter-cell L1/L2 mobility performs candidate DU configuration.
- each candidate DU notifies the CU of a response to the inter-cell L1/L2 mobility processing setting instruction.
- the response may notify that inter-cell L1/L2 mobility processing configuration has been completed.
- the response may indicate whether or not inter-cell L1/L2 mobility processing can be set.
- Each candidate DU may send an acknowledgment if the setting is possible. If the setting is not possible, it is recommended to send a rejection response. Reason information may be included in the rejection response. By doing so, the CU can recognize whether a candidate cell has been set in each candidate DU.
- the CU notifies DU #1 of information instructing the UE to execute inter-cell L1/L2 mobility processing including cell change between different DUs.
- Information regarding inter-cell L1/L2 mobility may be transmitted.
- the information regarding inter-cell L1/L2 mobility may include, for example, the identifier of the target UE, the candidate cell identifier assigned to the determined candidate cell, the settings of the candidate cell, the identifiers of the candidate DUs forming the candidate cell, and the like.
- Candidate cell settings may be configured using, for example, ServingCellConfig information used in the RRC message. This allows DU #1 to start inter-cell L1/L2 mobility processing, including cell change between different DUs, for the UE.
- DU #1 notifies the UE from the source cell of information instructing execution of inter-cell L1/L2 mobility processing including cell change between different DUs.
- Information regarding inter-cell L1/L2 mobility may be transmitted.
- the information regarding inter-cell L1/L2 mobility may include, for example, a candidate cell identifier to be assigned to the determined candidate cell, candidate cell settings, and identifiers of candidate DUs forming the candidate cell.
- Candidate cell settings may be configured using, for example, ServingCellConfig information used in the RRC message. This allows the UE to initiate L1/L2 mobility processing between cells, including between different DUs.
- the CU transmits L1 measurement settings for inter-cell L1/L2 mobility of the candidate cell to the candidate DU.
- DU #1 which is a source DU
- step ST2710 may be omitted.
- the L1 measurement settings of the candidate cell may be transmitted to the source DU.
- CSI-MeasConfig information used in the RRC message may be used. It is preferable to use F1 signaling for this notification. For example, a UE CONTEXT MODIFICATION REQUEST message may be used.
- each candidate DU notifies the CU whether or not the L1 measurement configuration for inter-cell L1/L2 mobility of the candidate cell is completed. It is preferable to use F1 signaling for this notification. For example, UE CONTEXT MODIFICATION RESPONSE may be used.
- steps ST2701 to ST2703 and step ST2510 may include setting of L1 measurement for inter-cell L1/L2 mobility of the candidate cell.
- step ST2508 may include the information of step ST2512.
- step ST2510 may include the information of step ST2513. It may be combined with the method of omitting step ST2710 described above. By doing so, the signaling in steps ST2707 to ST2714 and steps ST2511 to ST2514 can be reduced. It is possible to reduce the delay time of inter-cell L1/L2 mobility processing.
- step ST2512 the CU transmits the L1 measurement settings for inter-cell L1/L2 mobility of all candidate cells to DU #1.
- CSI-MeasConfig information used in the RRC message may be used.
- step ST2513 the source cell of DU #1 transmits the L1 measurement settings for inter-cell L1/L2 mobility of all candidate cells to the UE. By doing so, the UE can recognize the L1 measurement configuration for inter-cell L1/L2 mobility of the candidate cell.
- the UE may perform synchronization processing with the candidate cell of the candidate DU.
- RA processing may be executed for synchronization processing. It is preferable to perform uplink synchronization through RA processing and receive TA information from each candidate cell. By doing so, synchronization between the UE and the candidate cell becomes possible.
- the synchronization process between the UE and the candidate cell may be performed after the cell change is determined. Instead of all candidate cells or activated candidate cells, synchronization may be performed only with the target cell. It becomes possible to facilitate the processing of the UE. It becomes possible to reduce the power consumption of the UE.
- step ST2516 the UE performs L1 measurement of the candidate cell of the activated candidate DU.
- the UE uses the L1 measurement results of the candidate cell to determine cell change.
- the UE that has decided to change cells transmits L1 measurement results for inter-cell L1/L2 mobility to the source cell and target cell in steps ST2719 and ST2720.
- the L1 measurement results may include information regarding the cell change decision and the target cell after the cell change.
- the L1 measurement results may include information regarding the source cell.
- Information regarding DU may be included in the L1 measurement result. For example, information regarding DUs that constitute the target cell may be included. For example, information regarding DUs that constitute the source cell may be included.
- the information regarding the DU may be an identifier of the DU. By doing so, the source cell and the target cell can recognize that the cell change to the target cell has been decided.
- the target DU (DU#2) constituting the target cell that has recognized that it has become the target cell due to the cell change notifies the CU that it has decided to change the cell through inter-cell L1/L2 mobility. do.
- the target DU may send information regarding the cell change to the CU. This allows the CU to recognize that the cell change of the target DU to the target cell has been determined. These notifications may be sent to the CU from the source DU (DU #1) that constitutes the source cell.
- the CU notifies each candidate DU that the cell has been changed to the target DU and/or target cell due to inter-cell L1/L2 mobility that includes cell changes between different DUs. It's okay.
- Other candidate DUs that have not been determined as target DUs can recognize the target DU and/or target through inter-cell L1/L2 mobility including cell change between different DUs.
- the notification may include information on canceling the setting of the candidate cell. This allows other candidate DUs to cancel the setting of the candidate DU.
- Other candidate DUs may include source DUs.
- Other candidate DUs may include a target DU.
- the other candidate cells notify the CU of a response to the cell change notification. If the cell change notification includes information on candidate cell configuration cancellation, the response may include information as to whether candidate cell configuration cancellation has been completed. This allows the CU to recognize whether the candidate DU has canceled the candidate cell setting.
- the source DU that has received the cell change of the UE in step ST2719 may notify the UE from the source cell that the cell has been changed to the target cell, in step ST2520.
- a candidate cell identifier of the target cell may be transmitted.
- the identifier of the target DU constituting the target cell may be transmitted.
- step ST2522 the UE changes the target cell.
- the target DU that has received the cell change of the UE in step ST2720 sends the candidate cell identifier of the target cell, the TCI-state information of the target cell, and the act/deact information of the TCI-state from the target cell to the UE in step ST2730. Send. By transmitting TCI-state information, the UE can learn about the beams used in the target cell.
- the target DU transmits scheduling information from the target cell using the PDCCH.
- the UE receives the PDCCH of the target cell using the TCI-state received in step ST2730. By doing so, the UE can receive the PDCCH of the beam of the target cell. The UE is now able to obtain scheduling information.
- step ST2524 the UE becomes capable of data communication between the target cell, CU, and UPF of the target DU.
- step ST2516, step ST2718 to step ST2720 the UE performs L1 measurement for inter-cell L1/L2 mobility, determines cell change, reports L1 measurement results for inter-cell L1/L2 mobility,
- the cell change notification, cell change, target cell TCI-state information notification, and PDCCH transmission from the target cell beam in steps ST2520 to ST2523 including step ST2730 are performed between the UE and the source DU, and between the UE and the target DU. It can be implemented with This can be implemented using only L1/L2 control. Therefore, inter-cell L1/L2 mobility including cell change between different DUs can be performed at an early stage.
- steps ST2721 to ST2729 described above do not need to be performed before cell change in inter-cell L1/L2 mobility. It may also be performed after changing the cell.
- the execution timing of this process may be before or after the notification of TCI-state information to the UE. For example, it may be performed after step ST2730 or step ST2523. By reducing the load on the target DU, cell change processing using inter-cell L1/L2 mobility can be performed earlier.
- the CU may notify the source DU of the release of UE CONTEXT.
- the source DU that has received the release releases the UE CONTEXT.
- the source DU notifies the CU of completion of release of UE CONTEXT. By doing so, it becomes possible to discard the UE context in the source DU. It becomes possible to reduce the storage capacity in the source DU.
- the S-PCell notifies the UE of information regarding the cell after the cell change.
- Information regarding the cell after cell change includes information indicating that the cell has been changed to the target cell, candidate cell identifier of the target cell, TCI-state information of the target cell, act/deact information of TCI-state, and such information.
- the UE notifies the T-PCell of information regarding the cell after the cell change.
- the T-PCell that receives this information recognizes that its own cell is the target cell.
- a method for notifying information regarding a cell from an S-PCell to a UE is disclosed.
- Information regarding the cell may be included in the MAC signaling and transmitted.
- information regarding the cell may be included in the MAC CE and transmitted.
- the S-PCell may include information regarding the cell in the MAC CE and transmit it to the UE using the PDCCH.
- information regarding the cell may be included in the DCI and transmitted.
- the S-PCell may include information regarding the cell in the DCI and transmit it to the UE using the PDCCH.
- Information regarding the cell can be transmitted to the UE at an early stage.
- a method for notifying information regarding a cell from a UE to a T-PCell is disclosed.
- Information regarding the cell may be included in the UCI and transmitted.
- the UE may include information regarding the cell in the UCI and transmit it to the T-PCell on the PUCCH or PUSCH. This information can be transmitted to the T-PCell at an early stage.
- Information regarding the cell may be transmitted together with the SR.
- Information regarding the SR and the cell may be multiplexed and transmitted on the PUCCH or PUSCH. It is possible to notify the T-PCell that a cell change has been made and to request scheduling.
- the CU may determine the configuration of SR and/or PUCCH in each candidate cell to be configured for the UE.
- the settings may be the same for all candidate cells.
- the SR transmission process of the UE can be simplified.
- the settings may be different for each candidate cell. It can be set according to the resource usage status in the candidate cell.
- the determination may be made when the CU determines candidate cells for inter-cell L1/L2 mobility. For example, it may be performed in step ST2507 in FIG.
- the CU may transmit the configuration information to each candidate cell.
- the CU may include the configuration information in the information regarding inter-cell L1/L2 mobility that is transmitted to the candidate DUs constituting the candidate cell.
- the CU may transmit the configuration information of each candidate cell to the candidate DUs forming each candidate cell in steps ST2701 to ST2703 in FIG. 27.
- the candidate DU that has received the configuration information may use the configuration information to receive the SR and PUCCH from the UE, for example, when the constituent candidate cell is a T-PCell.
- the candidate DUs constituting the candidate cell may determine the SR and/or PUCCH settings in each candidate cell to be set for the UE. The decision may be made when information regarding inter-cell L1/L2 mobility is received from the CU. For example, each candidate DU may make the determination upon reception of steps ST2701 to ST2703 in FIG. 27.
- the candidate DU transmits the configuration information in the determined candidate cell to the CU. For example, it may be sent in response to information regarding inter-cell L1/L2 mobility received from the CU. For example, it may be transmitted in steps ST2704 to ST2706 in FIG.
- the CU can recognize the configuration information of the candidate cell determined by the candidate DU.
- the CU transmits the SR and/or PUCCH configuration of the candidate cell to the UE.
- the CU may transmit the SR and/or PUCCH configuration of the candidate cell to the UE via the S-PCell.
- the configuration information may be transmitted before the UE notifies the T-PCell of information regarding the cell.
- the configuration information may be included in information regarding inter-cell L1/L2 mobility.
- the configuration information may be included in the configuration of the candidate cell.
- the CU may include the configuration information in information regarding inter-cell L1/L2 mobility and transmit it to the UE via the S-PCell.
- the CU may transmit the configuration information to the S-PCell in step ST2508 of FIG. 27.
- the S-PCell may transmit the configuration information to the UE in step ST2510 of FIG. 27.
- the UE that has received the configuration information from the S-PCell can recognize the configuration information of the candidate cell.
- the UE becomes able to transmit an SR using the SR configuration information of the candidate cell that has become the T-PCell.
- the UE can multiplex the SR and cell-related information and transmit the SR using the PUCCH configuration information of the candidate cell that has become the T-PCell.
- Information regarding the cell may be transmitted together with CRI (CSI-RS Reference Indicator).
- Information regarding the cell may be transmitted along with the CSI including the CRI and/or SBBRI.
- Information regarding the cell and CRI and/or SBBRI may be multiplexed and transmitted on PUCCH or PUSCH. It becomes possible to notify the T-PCell that a cell change has been made to the T-PCell, and to notify the RS measurement results. The T-PCell can recognize the RS measurement results at the UE.
- Information regarding the cell may be transmitted together with the TCI-state.
- Information regarding the cell and TCI-state may be multiplexed and transmitted on PUCCH or PUSCH. It is possible to notify the T-PCell that a cell change has been made to the T-PCell and to notify the QCL information. It becomes possible to notify the T-PCell which beam to use for transmission.
- RA processing may be used to transmit information regarding the cell.
- information about cells may be associated with the PRACH. It may be associated with the PRACH sequence.
- a PRACH with a predetermined sequence is associated with information about the cell.
- the UE transmits the PRACH with the predetermined sequence to the T-PCell.
- the T-PCell can recognize that its own cell (which may be its own DU) has become the T-PCell.
- the predetermined sequence may be statically determined in advance by a standard or the like. Alternatively, the predetermined sequence may be included in the candidate cell settings and notified to the UE in advance.
- a four-step RA process may be used to transmit information regarding the cell.
- Information regarding the cell may be included in Msg3 of the 4-step RA process.
- Information regarding the cell may be included in Msg3 of RA processing for synchronization processing performed between the UE and the T-PCell.
- the UE performs RA processing with the T-PCell, which is the cell after the cell change, using inter-cell L1/L2 mobility, and transmits Msg3 including information regarding the cell to the T-PCell.
- Msg3 the T-PCell becomes able to receive information regarding the cell. By doing so, it becomes possible to notify information regarding the cell as well as synchronization processing.
- Msg3 that notifies information about the cell does not need to include an RRC message. By doing so, it becomes possible to perform processing without RRC. For example, there is no need for the DU to notify the CU of an RRC message. Therefore, early processing becomes possible.
- a two-step RA process may be used to transmit information regarding the cell.
- Information regarding the cell may be included in MsgA of the two-step RA process.
- Information regarding the cell may be included in MsgA of RA processing for synchronization processing performed between the UE and the T-PCell.
- the UE performs RA processing with the T-PCell, which is the cell after the cell change, using inter-cell L1/L2 mobility, and transmits MsgA including information regarding the cell to the T-PCell.
- MsgA the T-PCell can receive information regarding the cell. By doing so, it becomes possible to notify information regarding the cell as well as synchronization processing.
- MsgA reporting information about the cell may not include an RRC message. By doing so, it becomes possible to perform processing without RRC. For example, there is no need for the DU to notify the CU of an RRC message. Therefore, early processing becomes possible.
- FIG. 29 is a sequence diagram illustrating an example of an inter-cell L1/L2 mobility processing method between different DUs in Embodiment 4. Steps common to those in FIGS. 27 and 28 are given the same step numbers, and common explanations will be omitted.
- the example shown in FIG. 29 shows a method of transmitting cell-related information together with the SR from the UE to the target cell (T-PCell). A case is shown in which candidate cell #1 becomes a T-PCell.
- DU #1 is an S-DU that constitutes the S-PCell.
- DU #2 is a T-DU that constitutes T-PCell.
- step ST2516 the UE performs L1 measurement of the candidate cell using the inter-cell L1/L2 mobility candidate cell settings received from the S-PCell.
- step ST2517 the UE transmits the L1 measurement result of the candidate cell to the S-PCell.
- step ST2901 the S-PCell determines a PCell change using the L1 measurement result of the candidate cell received from the UE, and determines a T-PCell.
- candidate cell #1 becomes the T-PCell.
- step ST2902 the S-PCell transmits information regarding the cell to the UE.
- MAC signaling may be used for the transmission.
- step ST2522 the UE changes the PCell using the information received from the S-PCell.
- the UE transmits information regarding the cell to the T-PCell.
- the information is transmitted together with the SR.
- the T-PCell receives the information.
- the T-PCell recognizes that the UE's PCell has been changed to its own cell.
- the T-PCell can recognize the TCI-state and TCI-state activation/deactivation for the UE.
- the T-PCell can determine which beam to use for the UE.
- the T-PCell can recognize that the PCell has changed and that scheduling has been requested from the UE.
- the T-PCell can be scheduled early for the UE.
- the T-PCell transmits PDSCH scheduling information for data transmission to the UE.
- PDSCH TCI-state information may also be transmitted.
- the T-PCell transmits data to the UE using the PDSCH. At this time, it is preferable to use a beam corresponding to the TCI-state transmitted in step ST2523.
- the T-PCell can be scheduled for the UE, and continuous communication is possible between the UE and the T-PCell.
- FIG. 30 is a sequence diagram showing another example of the inter-cell L1/L2 mobility processing method between different DUs in Embodiment 4. Steps common to those in FIG. 29 are given the same step numbers, and common explanations will be omitted.
- the example shown in FIG. 30 shows a method of transmitting cell-related information from the UE to the T-PCell using two-step RA processing.
- the UE performs RA processing on the T-PCell.
- two-step RA processing is performed.
- the UE transmits information indicating changing the PCell to the T-PCell, TCI-state information in the T-PCell, and TCI-state activation/deactivation information.
- information regarding the cell is included in MsgA and transmitted.
- the T-PCell receives the information sent from the UE. By doing this, the T-PCell recognizes that the UE's PCell has been changed to its own cell. Furthermore, the T-PCell can recognize the TCI-state and TCI-state activation/deactivation for the UE. The T-PCell can determine which beam to use for the UE. Furthermore, by transmitting this information through RA processing, the T-PCell can quickly recognize that it has become a PCell.
- the UE does not need to perform RA processing on the candidate cell, for example, in steps ST2715 to ST2717.
- the UE can synchronize with the T-PCell by performing RA processing on the T-PCell in steps ST3001 and ST3002.
- the UE becomes able to transmit to the T-PCell.
- An interface is provided between DUs.
- a Uu interface between a base station and a UE may be applied as an interface between DUs. It is preferable to configure some or all of the functions of the UE in the DU.
- the S-DU transmits information regarding the cell to the T-DU using an inter-DU interface.
- the T-DU receives information about cells transmitted from the S-DU. By doing so, information regarding cells can be directly transmitted and received between DUs. For example, since there is no need to notify information regarding cells via the CU, this information can be transmitted and received quickly with low delay.
- An interface between IAB nodes may be applied as an interface between DUs. Signaling processing between IAB nodes may also be applied. It is preferable that the DU has some or all of the functions of IAB-DU and some or all of the functions of IAB-MT (IAB-Mobile Termination). RLC, MAC, and PHY may be configured in IAB-DU and IAB-MT, respectively. These protocols and functions may be used for interfacing between DUs. By applying existing standards in this way, it is possible to avoid complicating the process.
- inter-cell L1/L2 mobility can be performed between different DUs. Furthermore, since mobility processing without RRC and mobility processing without CU can be executed, inter-cell L1/L2 mobility between different DUs can be performed quickly with low delay. Communication interruption time and communication delay time can be reduced by inter-cell L1/L2 mobility processing between different DUs.
- Embodiment 5 In conventional L1/L2 mobility, the identifier for each cell for the UE was the same because of mobility within the same cell. However, in inter-cell L1/L2 mobility, cells change, so for example, the per-cell identifier for the UE used in the source cell is no longer available in the target cell, and the UE is unable to communicate with the target cell. The problem arises that it becomes possible.
- Embodiment 5 discloses a method for solving such problems.
- the cell-by-cell identifier for UE used in S-PCell is also used in T-PCell.
- the per-cell identifier for the UE may hereinafter be referred to as a UE identifier.
- a method for using the UE identifier used in S-PCell in T-PCell is disclosed.
- a source DU (S-DU) configuring an S-PCell transmits a UE identifier in the S-PCell to a DU (candidate DU) configuring a candidate cell.
- the UE identifier may be transmitted using the inter-DU interface disclosed above.
- the candidate DU can recognize the UE identifier used in the S-PCell.
- the number of candidate cells may be one or more.
- Candidate cells may include S-PCell.
- the S-PCell When the S-PCell is set as a candidate cell and determined as the target PCell by inter-cell L1/L2 mobility, it becomes L1/L2 mobility within the same cell. For example, a beam change may be performed within the S-PCell for the UE.
- the S-DU may transmit the UE identifier in the S-PCell to the CU.
- the CU transmits the UE identifier in the S-PCell to the candidate DU.
- the F1 interface may be used for transmission from the S-DU to the CU.
- the F1 interface may be used for transmission from the CU to the candidate DU.
- the transmission of the UE identifier from the S-DU to the CU may be included in the UE's inter-cell L1/L2 mobility request.
- the transmission of the UE identifier from the CU to the candidate DU may be included in the inter-cell L1/L2 mobility configuration to the candidate DU.
- the candidate DUs configuring the target T-PCell use the UE identifier in the S-PCell as the UE identifier in the T-PCell.
- the T - The DUs constituting the PCell can acquire the UE identifier in the S-PCell, and can use the UE identifier for communication in the T-PCell.
- a different UE identifier may be set for each cell within the gNB. For example, if the gNB configures k cells and the UE identifier setting range is 0 to N, cell #1 has 0 to M_1-1, cell #2 has M_1-1 to M_2-1, Set M_(k-1) to M_k-1 in cell #k. M_k-1 may be equal to or less than N. By doing this, the UE identifiers in the S-PCell and T-PCell will not collide.
- the candidate DU determines the UE identity in the candidate cell.
- the UE identifier in a candidate cell may be set by a DU that constitutes the candidate cell. For example, it may be set using MAC.
- the candidate DU notifies the S-DU of the UE identifier to be used when the candidate cell becomes a T-PCell.
- the UE identifier may be transmitted using the inter-DU interface disclosed above. By receiving the UE identifier from the candidate DU, the S-DU can recognize the UE identifier to be used when the candidate cell becomes a T-PCell.
- the S-DU may transmit the UE identifier in the S-PCell to the candidate DU.
- the UE identifier in the S-PCell may be transmitted using the inter-DU interface disclosed above.
- the S-DU may send the UE identifier in the S-PCell to the candidate DU via the CU.
- F1 signaling may be used for transmission from the S-DU to the CU. For example, it may be transmitted in step ST2506 in FIG.
- F1 signaling may be used for transmission from the CU to the candidate DU. For example, it may be transmitted in steps ST2701 to ST2703 in FIG.
- the candidate DU receives the UE identifier at the S-PCell.
- a candidate DU may or may not consider the UE identity in the S-PCell when determining the UE identity in the candidate cell.
- the UE identifier in the candidate cell may be the same as the UE identifier in the S-PCell.
- information indicating the same as the S-PCell may be transmitted. There is no need to transmit the UE identifier in the candidate cell to the UE, and the amount of information can be reduced.
- the candidate DU may have a UE identifier in the candidate cell that is different from a UE identifier used for other UEs in the candidate cell. Collision between UE identifiers and other UEs can be avoided.
- the candidate DU may transmit the UE identifier in the candidate cell to the CU.
- the CU sends the UE identity in the candidate cell to the S-DU.
- the F1 interface may be used for transmitting the candidate UE identifier from the DU to the CU and/or from the CU to the S-DU.
- the transmission of the UE identifier from the candidate DU to the CU may be included in the candidate cell configuration for inter-cell L1/L2 mobility.
- the UE identifier may be transmitted from the CU to the S-DU while being included in the inter-cell L1/L2 mobility configuration.
- the S-DU transmits the UE identifier in the candidate cell to the UE.
- the UE identifier in the candidate cell may be transmitted from the S-PCell to the UE.
- the UE identifier may be included in the configuration of candidate cells for inter-cell L1/L2 mobility and transmitted. It is preferable to transmit the information regarding the candidate cell in association with the UE identifier in the candidate cell.
- RRC signaling may be used for the transmission. More information can be sent.
- MAC signaling may be used. It becomes possible to transmit the UE identifier early.
- the UE receives a UE identifier for use in the candidate cell.
- the UE stores the UE identifier used in the candidate cell.
- the UE may use the UE identifier in the candidate cell that has become the T-PCell in communication with the T-PCell after inter-cell L1/L2 mobility.
- candidate DUs forming the T-PCell use the UE identifier in the candidate cell that became the T-PCell as the UE identifier in the T-PCell.
- the UE identifier set by the candidate DU can be used for communication between the UE and the T-PCell.
- the UE may clear the configuration of other candidate cells.
- the settings may be discarded.
- the UE may clear the UE identity in other candidate cells if the communication with the T-PCell after inter-cell L1/L2 mobility is successful.
- the UE identifier may be discarded. By doing so, the storage capacity required by the UE can be reduced.
- a candidate DU does not allocate the UE identifier to another UE until it recognizes that the candidate cell that it constitutes has not become a T-PCell.
- the candidate DU does not allocate the UE identifier to another UE until it recognizes that the candidate cell that it constitutes has become a T-PCell.
- a UE targeted for inter-cell L1/L2 mobility may use this UE identifier until the connection with the T-PCell is released or until another UE identifier is configured by the T-PCell. By doing this, even if there is a period from the setting of a candidate cell until the PCell is changed due to inter-cell L1/L2 mobility, the identifier of the UE targeted for mobility will not collide with the identifier of another UE. can be avoided.
- the UE identifier in the candidate cell may be set by the CU. It may be set by the CU's RRC.
- the CU transmits, to the candidate DU, a UE identifier in a candidate cell configured by the candidate DU.
- the candidate cell and the UE identifier may be associated and transmitted.
- the candidate DU that has received the UE identifier in the candidate cell uses the UE identifier for the UE when the candidate cell becomes a T-PCell.
- the CU sends the UE identifier in the candidate cell to the S-DU.
- the UE identifier in the candidate cell and the candidate cell may be transmitted in association with each other.
- the CU may transmit the S-DU by including the UE identifier in the candidate cell in the configuration of the candidate cell.
- F1 signaling may be used to transmit the UE identifier in the candidate cell from the CU to the S-DU.
- the UE identifier at the candidate cell may be included in the RRC message.
- the RRC message may be encapsulated and transmitted using F1 signaling.
- the S-DU transmits to the UE the candidate cell identifier received from the CU.
- the S-DU transmits the UE identifier in the candidate cell from the S-PCell to the UE.
- the UE identifier in the candidate cell and the candidate cell may be transmitted in association with each other.
- the S-DU may be transmitted to the UE by including the UE identifier in the candidate cell in the configuration of the candidate cell.
- the UE identity in the candidate cell may be included in the RRC message.
- RRC signaling may be used to transmit the UE identifier in the candidate cell from the S-DU to the UE.
- MAC signaling may be used to transmit the UE identifier in the candidate cell from the S-DU to the UE.
- the UE identifier in the candidate cell may be included in the DCI.
- PDCCH may be used to transmit the UE identifier in the candidate cell from the S-DU to the UE.
- the CU can determine the UE identifier in the candidate cell.
- the UE can use the UE identifier of the candidate cell determined by the CU when any candidate cell becomes a T-PCell.
- the S-PCell transmits the UE identifier in the T-PCell to the UE.
- the S-PCell determines the T-PCell after changing the PCell due to inter-cell L1/L2 mobility.
- the S-PCell sends information regarding the change of the PCell to the UE.
- the T-PCell identifier, TCI-state information in the T-PCell, and TCI-state activation/deactivation information are transmitted as information related to PCell changes.
- the S-PCell sends the UE identifier in the T-PCell to the UE together with or included in the information regarding the PCell change. For example, MAC signaling may be used as the transmission method.
- the MAC CE may include the UE identifier in the T-PCell. A part or all of the UE identifier in the T-PCell, the T-PCell identifier, TCI-state information, and TCI-state activation/deactivation information may be combined and included in the MAC CE.
- the UE can receive the UE identifier in the T-PCell along with the PCell change instruction from the S-PCell.
- the S-DU may derive the UE identifier in the T-PCell from the UE identifier in the candidate cell.
- the UE identifier in the candidate cell may be obtained by appropriately applying the method described above.
- the UE can obtain the UE identifier in the T-PCell.
- the UE becomes able to communicate with the T-PCell using the UE identifier in the T-PCell received from the S-PCell.
- the T-DU sets the UE identifier in the T-PCell. After inter-cell L1/L2 mobility, the UE communicates with the T-PCell using the UE identifier in the T-PCell configured by the T-DU.
- the T-DU transmits the UE identifier in the T-PCell to the UE.
- the UE performs RA processing with the T-PCell by changing PCell through inter-cell L1/L2 mobility processing.
- the T-PCell transmits the UE identifier in the T-PCell to the UE.
- a four-step RA process may be performed as the RA process.
- the T-PCell may include the UE identifier in Msg2 and transmit it to the UE.
- a two-step RA process may be performed as the RA process.
- the T-PCell may include the UE identifier in MsgB and transmit it to the UE.
- the UE receives the UE identifier from the T-PCell in the RA process.
- the UE may use the RNTI for RA processing when receiving Msg2 or MsgB.
- the RNTI for RA processing may be statically determined in advance according to a standard or the like. Alternatively, it may be transmitted from the S-PCell to the UE in advance.
- the UE can receive the UE identifier from the T-PCell in the RA process.
- the UE may use the UE identifier set by the T-PCell for communication with the T-PCell.
- the UE becomes able to communicate with the T-PCell.
- the T-PCell uses RA processing to transmit the UE identifier in the T-PCell to the UE.
- This method may be applied as appropriate as a method for the UE to receive the UE identifier in the candidate cell (which may be the UE identifier in the case of becoming a T-PCell) from the candidate cell.
- the candidate cell may use RA processing to transmit the UE identity at the candidate cell to the UE.
- the UE may perform RA processing with the candidate cell before the PCell is changed due to inter-cell L1/L2 mobility. For example, before the PCell is changed, the UE may perform RA processing with the candidate cell in order to perform measurements on the candidate cell or to transmit measurement results of the candidate cell to the candidate cell.
- Each candidate cell transmits a UE identifier in the candidate cell to the UE in the RA process.
- the method disclosed above may be applied as appropriate.
- the candidate cell can transmit the UE identifier of the candidate cell to the UE. Therefore, a candidate cell that becomes a T-PCell due to inter-cell L1/L2 mobility can communicate with a UE by using the UE identifier.
- the T-DU transmits the UE identifier in the T-PCell to the UE.
- the T-PCell transmits the UE identifier in the T-PCell to the UE.
- MAC signaling may be used for the transmission.
- the UE identifier can be notified to the UE at an early stage.
- RRC signaling may be used for the transmission.
- the UE identifier may be included in the RRC reconfiguration message and transmitted. For example, it may be included in the existing message RRCReconfiguration.
- the UE identifier on the T-PCell may be transmitted together with the RRC reconfiguration on the T-PCell.
- L1/L2 signaling may be used for the transmission.
- the UE identifier in the T-PCell may be included in the DCI and transmitted on the PDCCH. The UE identifier can be notified to the UE earlier.
- a method in which a UE acquires a UE identifier used until it receives a UE identifier at the T-PCell from a T-PCell.
- the UE identifier used until the UE identifier is received from the T-PCell to the T-PCell may be statically determined by a standard or the like. For example, a default UE identifier may be provided.
- the S-DU may set the UE identifier, include it in the candidate cell settings, and notify the UE from the S-PCell.
- the T-DU may configure the UE identifier, include it in the candidate cell configuration, and notify the UE via the S-PCell.
- the CU may configure the UE identifier, include it in the candidate cell configuration, and notify the S-DU and T-DU.
- the S-DU may include the UE identifier in the configuration of the candidate cell, and the S-PCell may notify the UE.
- the UE can acquire the UE identifier in the T-PCell after inter-cell L1/L2 mobility, and can communicate with the T-PCell.
- the above method is applicable to both inter-cell L1/L2 mobility within the same DU and inter-cell L1/L2 mobility between different DUs. In either case, similar effects can be obtained.
- FIG. 31 is a sequence diagram illustrating an example of a method for notifying a UE identifier in a T-PCell in inter-cell L1/L2 mobility between different DUs in Embodiment 5. Steps common to those in FIG. 29 are given the same step numbers, and common explanations will be omitted.
- the example shown in FIG. 31 discloses an example of a method for transmitting a UE identifier in a candidate cell from an S-PCell to a UE.
- the candidate DUs determine the UE identifier to be used in the candidate cell configured by the own DU of the UE that is the target of inter-cell L1/L2 mobility. , transmits the UE identifier to the CU.
- the candidate DU may be transmitted by associating the candidate cell with the UE identifier.
- Steps ST3101 to ST3103 may be performed in the process of step ST2750, which is the process described above using FIG. 27. It is preferable that the candidate DU that has received the inter-cell L1/L2 mobility configuration request from the CU transmits the UE identifier. For example, in steps ST2701 to ST2703 shown in FIG.
- the candidate DU that has received the inter-cell L1/L2 mobility setting request from the CU is the candidate cell configured by the own DU of the UE that is the target of inter-cell L1/L2 mobility. Determine the UE identifier to be used.
- the candidate DU may transmit the UE identifier used in the candidate cell to the CU. By doing so, the CU can recognize the UE identifier used in each candidate cell.
- step ST3104 of FIG. 31 the CU transmits the UE identifier used in the candidate cell to the S-DU (DU #1).
- Step ST3104 may be performed in the process of step ST2750.
- the CU may transmit the UE identifier used in the candidate cell to the S-DU.
- the S-DU can recognize the UE identifier used in each candidate cell.
- step ST3105 the S-DU transmits the UE identifier used in the candidate cell from the S-PCell to the UE.
- Step ST3105 may be performed in the process of step ST2750.
- the candidate cell identifier may be transmitted in step ST3105.
- the candidate cell identifier and the UE identifier used in the candidate cell may be transmitted in association with each other.
- the S-DU may transmit the UE identifier used in the candidate cell to the UE. By doing so, the UE can recognize the UE identifier used in each candidate cell.
- the UE uses the UE identifier of the candidate cell that will become the T-PCell for reception from the T-PCell after changing the PCell. From now on, the UE may use the UE identifier for communication with the T-PCell. For receiving the PDCCH from the T-PCell in step ST2523, the UE may use the UE identifier of the candidate cell to become the T-PCell received from the S-PCell in step ST3105.
- the UE can acquire the UE identifier in the T-PCell after inter-cell L1/L2 mobility, and can communicate with the T-PCell.
- FIG. 32 is a sequence diagram illustrating another example of the method of notifying the UE identifier in the T-PCell in inter-cell L1/L2 mobility between different DUs in Embodiment 5. Steps common to those in FIG. 30 are given the same step numbers, and common explanations will be omitted.
- the example shown in FIG. 32 discloses an example of a method in which the T-DU (DU #2) sets a UE identifier in the T-PCell and transmits it to the UE.
- step ST3001 the UE performs two-step RA processing on the T-PCell.
- the T-DU that receives the PCell change included in MsgA from the UE determines the UE identifier to be used in the T-PCell.
- step ST3201 the T-PCell transmits the determined UE identifier to the UE.
- the UE identifier is included in MsgB and transmitted in the RA process, for example.
- the UE may use a preset UE identifier when receiving MsgB from the T-PCell in step ST3201. For example, a UE identifier predetermined by a standard is used. For example, a UE identifier for RA processing (RA-RNTI: Random Access Radio Network Temporary Identifier) may be used. By doing so, the UE can receive MsgB in step ST3201. Thereafter, the UE uses the UE identifier received from the T-PCell for communication with the T-PCell. For receiving the PDCCH from the T-PCell in step ST2523, the UE may use the UE identifier received from the T-PCell in step ST3201.
- RA-RNTI Random Access Radio Network Temporary Identifier
- the UE can acquire the UE identifier in the T-PCell after inter-cell L1/L2 mobility, and can communicate with the T-PCell.
- FIG. 33 is a sequence diagram illustrating another example of a method for notifying a UE identifier in a T-PCell in inter-cell L1/L2 mobility between different DUs in Embodiment 5. Steps common to those in FIG. 29 are given the same step numbers, and common explanations will be omitted.
- the example shown in FIG. 33 discloses an example of a method in which the T-DU (DU #2) transmits the UE identifier in the T-PCell to the UE after changing the PCell due to inter-cell L1/L2 mobility.
- the UE notifies the T-PCell of the PCell change.
- the T-DU that receives the PCell change from the UE determines the UE identifier to be used in the T-PCell.
- the T-PCell transmits scheduling information for transmitting the determined UE identifier to the UE.
- PDSCH TCI-state information may be transmitted together with the scheduling information.
- the UE may use a preset UE identifier for receiving the PDCCH from the T-PCell in step ST3301.
- the UE uses the preset UE identifier until it receives the UE identifier from the T-PCell. By doing so, the UE can communicate with the T-PCell until it receives the UE identifier from the T-PCell.
- the T-PCell transmits the determined UE identifier to the UE. It may also be transmitted using MAC signaling. For example, it may be included in the MAC CE and transmitted.
- the UE receives the UE identifier in step ST3302 using the scheduling information received in step ST3301.
- the UE recognizes the UE identifier used in the T-PCell by receiving the UE identifier in step ST3302.
- the UE uses the UE identifier received from the T-PCell for communication with the T-PCell.
- the UE may use the UE identifier received from the T-PCell for communication with the T-PCell in step ST2524.
- the UE identifier in step ST3302 may be multiplexed with the data from the T-PCell to the UE in step ST2524. For example, it may be multiplexed in the MAC layer. Data communication becomes possible between the UE and the T-PCell at an early stage.
- the UE becomes able to acquire the UE identifier used in the T-PCell after inter-cell L1/L2 mobility, and becomes able to communicate with the T-PCell.
- the UE can acquire the UE identifier used in the T-PCell, and can communicate with the T-PCell using the UE identifier. Communication continuity is possible even when L1/L2 mobility occurs between cells.
- Embodiment 6 Since conventional L1/L2 mobility is mobility within the same cell, that is, there is no cell change, retransmission processing is performed in the cell. However, in inter-cell L1/L2 mobility, cells are changed. For this reason, the problem is how to handle retransmission processing in S-PCell and T-PCell, and if no measures are taken, retransmission processing when changing cells due to inter-cell L1/L2 mobility will not work. In such a case, for example, undelivered data may occur in the S-PCell. Without a method for handling data that is not delivered in the S-PCell, a problem arises in which data transmission and reception between the UE and the RAN becomes discontinuous during inter-cell L1/L2 mobility.
- Embodiment 6 discloses a method for solving such problems.
- the S-PCell notifies the UE of the change in PCell.
- the UE receives a PCell change from the S-PCell, it receives the PDCCH of the T-PCell.
- the PCell change may be sent in MAC signaling.
- the PCell change may be included in the MAC CE and transmitted.
- the S-PCell changes the cell that receives the PDCCH in the MAC CE for the UE.
- retransmission processing is executed in the PCell (S-PCell) before the change. It is preferable to perform retransmission processing according to the PDCCH including the DCI from the cell before change. After changing the PCell, the retransmission process is executed using the changed PCell (T-PCell). It is preferable to perform retransmission processing according to the PDCCH including the DCI from the changed cell.
- the retransmission processing may be, for example, HARQ processing.
- the process number in the HARQ process may be set for each cell. Since the same processing as the conventional HARQ processing can be applied, the processing can be avoided from becoming complicated.
- the initial transmission or retransmission of the PDSCH may be configured using the NDI included in the DCI. Since conventional retransmission processing can be applied, complexity of processing can be avoided.
- the buffer of the HARQ process may be cleared (flushed).
- the HARQ buffer may also be cleared.
- the buffer of the HARQ process used for UL transmission and reception may be cleared.
- the buffer of the HARQ process used for DL transmission and reception may be cleared.
- a TB (Transport Block) soft buffer (sometimes referred to as HARQ soft buffer) may be cleared.
- the UE's HARQ buffer may be cleared.
- the HARQ buffer of the S-PCell may be cleared.
- Disclosed is a method for processing data that has not been completely delivered by S-PCell.
- the DU changes the data not delivered by the S-PCell to the T-PCell and transmits it.
- the data may be TB.
- Data for which HARQ processing has not been completed in the S-PCell can be transmitted from the T-PCell.
- the UE receives data from the T-PCell that it has not delivered from the S-PCell.
- the UE buffers the HARQ process on the T-PCell into a new HARQ buffer.
- the above-described method may be applied to processing data that is not delivered by the S-PCell when changing the PCell in inter-cell L1/L2 mobility within a DU.
- the DU transmits data that could not be delivered by the S-PCell due to PCell change due to inter-cell L1/L2 mobility within the DU from the T-PCell to the UE.
- the UE receives data from the T-PCell that could not be delivered on the S-PCell due to PCell change due to inter-cell L1/L2 mobility within the DU. By doing so, the UE can continuously receive data from the DU. It is possible to avoid discontinuous transmission and reception of data in inter-cell L1/L2 mobility within a DU.
- FIG. 34 is a sequence diagram illustrating an example of a data transmission method in inter-cell L1/L2 mobility processing in Embodiment 6. Steps common to those in FIG. 26 are given the same step numbers, and common explanations will be omitted.
- the example of FIG. 34 shows a method in which DU #1 changes data that is not delivered by S-PCell to T-PCell and transmits the data by changing PCell for inter-cell L1/L2 mobility.
- step ST2901 the S-PCell that has decided to change the PCell for the UE targeted for inter-cell L1/L2 mobility transmits undelivered data information to the T-PCell in step ST3401.
- the transmission may be performed after the transmission of the PCell change from the S-PCell to the UE in step ST2902.
- the UE may clear the HARQ buffer of the S-PCell in step ST3402.
- the UE performs data communication with the T-PCell in steps ST2523 and ST2524.
- step ST2524 the T-PCell transmits undelivered data to the UE via the S-PCell.
- DU #1 may have undelivered data information. It is preferable that DU #1 transmits undelivered data from the S-PCell from the T-PCell.
- the timing of clearing the HARQ buffer of the S-PCell in the UE is not limited to this. Good to have.
- the UE may clear the HARQ buffer of the S-PCell when it starts communicating with the T-PCell after changing the PCell.
- the UE may clear the HARQ buffer of the S-PCell.
- the UE may clear the HARQ buffer of the S-PCell.
- the UE may clear the HARQ buffer of the S-PCell when receiving data from the T-PCell after changing the PCell. For example, the UE may clear the HARQ buffer of the S-PCell when receiving the first data from the T-PCell in step ST2524. For example, the UE may clear the S-PCell's HARQ buffer upon receiving undelivered data from the S-PCell from the T-PCell. By doing so, it is possible to avoid the HARQ buffer from continuing to hold data without being cleared.
- the UE's HARQ buffer may be cleared.
- the S-PCell may clear the HARQ buffer of the UE in the S-PCell when transmitting the PCell change to the UE in step ST2902.
- the timing to clear the HARQ buffer of the UE in the S-PCell is not limited to this, and may be any time after the UE has decided to change the PCell.
- the S-PCell may clear the UE's HARQ buffer when transmitting undelivered data information on the S-PCell to the T-PCell.
- the S-PCell may clear the HARQ buffer of the UE when transmitting undelivered data information from the S-PCell to the T-PCell in step ST3401. By doing so, it is possible to avoid the HARQ buffer from continuing to hold data without being cleared.
- the UE may complete HARQ with the S-PCell and clear the buffer that holds the data that has been received. Clearing the buffer disclosed herein may be performed simultaneously with clearing the HARQ buffer described above. By doing so, after the PCell is changed, the buffer used for data communication between the S-PCell and the UE can be reliably cleared, and the buffer amount of the S-PCell and the UE can be reduced.
- the same data is duplicated and transmitted from the CU to the S-DU and candidate DU. It may also be copied using PDCP.
- a new replication protocol may be provided.
- a replication protocol is provided between PDCP and RLC, and the protocol replicates the PDCP PDU received from PDCP and transmits the replicated data to the RLC of the S-DU and the RLC of the candidate DU. Good too.
- the same data identifier is assigned to the S-DU and candidate DU to the duplicated data.
- the same data identifier may be assigned to the target bearer of the UE for inter-cell L1/L2 mobility in the S-DU and the candidate DU.
- the RLC of the S-DU and the RLC of the candidate DU are set to be the same for a target bearer of a UE targeted for inter-cell L1/L2 mobility.
- the RLC of the S-DU and the RLC of the candidate DU assign the same RLC SN (Radio Link Control Sequence Number) to the PDCP PDU transmitted from the CU. Even when segmented by RLC, the same segment processing is performed on the S-DU and candidate DU, and the same RLC SN is assigned. By doing so, the same data identifier can be assigned to the duplicated data in the S-DU and the candidate DU.
- RLC SN Radio Link Control Sequence Number
- the UE After changing the PCell due to inter-cell L1/L2 mobility, the UE transmits to the T-PCell the data that could not be received from the S-PCell of the S-DU and/or the data identifier of the data that could be received.
- the UE may send data identifiers of the data not delivered on the S-PCell and/or the delivered data to the T-PCell.
- the data identifier may be an RLC SN. It may also be RLC SN status information.
- Information on the data identifier may be transmitted as a bitmap. For example, 0 may be mapped to the data identifier of data that could not be received, and 1 may be mapped to the data identifier of data that could be received.
- the lowest data identifier of the data that could not be received may be transmitted.
- the bitmap may be information from the lowest data identifier of the data that could not be received.
- the information on the data identifier may include information on the number of bits of the bitmap.
- the number of bits in the bitmap may be statically determined by a standard or the like.
- the data identifier may be used as a sequence number, and the difference between the largest data identifier of data that could be received and the smallest data identifier of data that could not be received may be used as the number of bits in the bitmap. By doing so, it becomes possible to indicate data that cannot be received discontinuously.
- a method for transmitting data identifiers of data that could not be received from the S-PCell and/or that could be received from the UE to the T-PCell will be disclosed.
- the data identifier is transmitted by MAC signaling. It may be included in the MAC CE and transmitted. Alternatively, the data identifier may be included in the UCI. It may be included in the UCI and transmitted on the PUCCH or PUSCH. The data identifier can be transmitted earlier. Alternatively, the data identifier may be sent in the RA process. For example, it may be transmitted using PRACH or included in Msg3 or MsgA. For these methods, the UE identifier notification method disclosed in Embodiment 4 may be applied as appropriate. By doing so, the data identifier can be transmitted in the access process to the T-PCell.
- the T-PCell receives data identifiers for these data from the UE. Receive RLC SN as a data identifier.
- the T-DU allows the UE to recognize data that could not be received from the S-PCell.
- the T-DU retransmits data that the UE could not receive from the S-PCell from the T-PCell to the UE.
- the data may preferably be an RLC PDU. It becomes possible for the UE to receive data that could not be received by the S-PCell from the T-PCell.
- Another method for solving the above problems is disclosed.
- the method of duplicating and transmitting the same data from the CU to the S-DU and the candidate DU, and the method of assigning the same data identifier to the duplicated data in the S-DU and the candidate DU are applied as appropriate.
- the MAC of candidate DUs may be set to be the same as the MAC of S-DUs.
- the MAC of the S-DU and the MAC of the candidate DU perform the same MAC processing on the RLC PDU transmitted from the RLC. It is preferable to allocate the same process for HARQ processing. It is preferable to assign the same HARQ process identifier to the S-DU and candidate DU to the duplicated data.
- the UE After the PCell is changed due to inter-cell L1/L2 mobility, the UE transmits to the T-PCell the data that could not be received from the S-PCell of the S-DU and/or the HARQ process identifier of the data that could be received. do.
- the UE may send the HARQ process identifier of the data not delivered on the S-PCell and/or the delivered data to the T-PCell.
- Information on the HARQ process identifier may be transmitted as a bitmap. For example, 0 may be mapped to the HARQ process identifier of data that could not be received, and 1 may be mapped to the HARQ process identifier of data that could be received.
- the HARQ process identifier of the lowest data that could not be received may be sent.
- the bitmap may be information from the HARQ process identifier of the lowest data that could not be received.
- the T-PCell receives these HARQ process identifiers from the UE. By doing so, the T-DU can recognize the HARQ process identifier of data that the UE could not receive from the S-PCell. The T-DU retransmits the HARQ process data that could not be received from the S-PCell from the T-PCell to the UE. It becomes possible for the UE to receive HARQ process data that could not be received by the S-PCell from the T-PCell.
- the CU transmits the identifier of the transmitted duplicate data to the candidate DU.
- the identifier of the duplicate data may be an identifier given to the PDCP PDU.
- the PDCP configured in the CU may transmit the PDCP PDU identifier of the duplicate data to the RLC configured in the candidate DU.
- the identifier may be a PDCP PDU SN.
- the candidate DU receives the identifier given to the duplicate data. By doing so, the candidate DU can recognize the identifier of the duplicate data received from the CU.
- the candidate DU may associate the identifier given to the duplicate data with the identifier assigned to the duplicate data in RLC.
- the candidate DU associates the PDCP PDU SN and RLC SN of the duplicate data.
- the candidate DU may store the association.
- the RLC of the candidate DU may store the association. By doing so, the candidate DU can derive the RLC SN from the PDCP PDU SN, or the PDCP PDU SN from the RLC SN.
- the S-DU can derive the RLC SN from the PDCP PDU SN, or the PDCP PDU SN from the RLC SN.
- the UE After changing the PCell due to inter-cell L1/L2 mobility, the UE transmits to the T-PCell the data that could not be received from the S-PCell of the S-DU and/or the data identifier of the data that could be received.
- the UE may send data identifiers of the data not delivered on the S-PCell and/or the delivered data to the T-PCell.
- the data identifier may be a PDCP PDU SN. It may also be used as status information of PDCP PDU SN.
- the data identifier information may be transmitted as a bitmap. For example, 0 may be mapped to the data identifier of data that could not be received, and 1 may be mapped to the data identifier of data that could be received.
- the lowest data identifier of the data that could not be received may be transmitted.
- the bitmap may be information from the lowest data identifier of the data that could not be received.
- the information on the data identifier may include information on the number of bits of the bitmap.
- the number of bits in the bitmap may be statically determined by a standard or the like.
- the data identifier may be used as a sequence number, and the difference between the largest data identifier of data that could be received and the smallest data identifier of data that could not be received may be used as the number of bits in the bitmap. By doing so, it becomes possible to indicate data that cannot be received discontinuously.
- the method disclosed above may be applied as appropriate.
- the UE may transmit the identifier in an RLC Control PDU to the T-PCell.
- the UE may transmit the identifier to the T-PCell in a PDCP Control PDU.
- the identifier is PDCP PDU SN. Complicated transmission processing of the identifier can be avoided.
- the T-PCell receives the PDCP PDU SN of these data from the UE.
- the T-DU allows the UE to recognize the PDCP PDU SN of data that could not be received from the S-PCell. By doing so, the T-DU can recognize the PDCP PDU of data that the UE could not receive from the S-PCell.
- the T-DU retransmits the PDCP PDU of data that could not be received from the S-PCell from the T-PCell to the UE.
- the T-DU may derive an RLC SN associated with the PDCP PDU SN.
- the T-DU transmits data to which the derived RLC SN is assigned to the UE.
- the T-DU can transmit from the T-PCell the PDCP PDU of data that the UE could not receive from the S-PCell.
- the UE can receive PDCP PDUs of data that could not be received by the S-PCell from the T-PCell.
- the RLC of the S-DU and the RLC of the candidate DU are set to the same, and the data replicated by the PDCP of the CU is Therefore, a method of assigning the same data identifier to the S-DU and the candidate DU may be applied as appropriate.
- the UE After changing the PCell due to inter-cell L1/L2 mobility, the UE transmits the RLC SN of the data that could not be received from the S-PCell of the S-DU to the T-PCell.
- the UE may send the RLC SN of data not delivered on the S-PCell to the T-PCell.
- RLC SN status information may also be transmitted.
- the T-PCell receives the RLC SN of these data from the UE.
- the T-DU can recognize the RLC SN of data that the UE could not receive from the S-PCell.
- the T-DU may derive a PDCP PDU SN associated with the RLC SN.
- the T-DU transmits the derived PDCP PDU SN data to the UE. All RLC PDUs to which the RLC SN associated with the PDCP PDU SN is attached will be transmitted. By doing so, the T-DU can transmit from the T-PCell the PDCP PDU that the UE could not receive from the S-PCell.
- the UE can receive PDCP PDUs that could not be received by the S-PCell from the T-PCell.
- the UE can continuously receive data from different DUs even if inter-cell L1/L2 mobility is performed between different DUs. It is possible to avoid discontinuous transmission and reception of data in inter-cell L1/L2 mobility between different DUs.
- FIG. 35 is a sequence diagram showing another example of a data transmission method in inter-cell L1/L2 mobility processing in Embodiment 6. Steps common to those in FIG. 29 are given the same step numbers, and common explanations will be omitted.
- the example in FIG. 35 shows a case where PCell change is performed between different DUs due to inter-cell L1/L2 mobility.
- step ST3501 the CU copies DL (Downlink) data to the UE. It is recommended to perform replication using PDCP.
- the data identifier of the DL data is also duplicated and given to the DL data. It is preferable that the data identifier is PDCP PDU SN.
- the CU transmits DL data to the S-DU (DU #1) in order to communicate with the UE.
- the S-DU transmits the received DL data from the SPCell to the UE.
- steps ST3503 to ST3505 the CU transmits the copied DL data to the candidate DUs (DU#2, DU#3, DU#4).
- the candidate DU holds received DL data.
- the candidate DU may store received DL data. By doing so, the same data and data identifier as the DL data sent to the S-DU is sent to the candidate DU.
- steps ST3501 to ST3505 is not limited to the timing shown in FIG. 35, but may be performed after inter-cell L1/L2 mobility is configured for the UE in step ST2750.
- step ST2750 see FIG. 27
- the above-described processes of steps ST3501 to ST3505 may be performed in response to the transmission of step ST2508.
- the process may be performed upon reception of step ST2509.
- the transmission of duplicate data to the candidate DU is enabled.
- steps ST3501 to ST3505 may be performed after setting candidate cells.
- step ST2750 see FIG. 27
- the process may be performed in response to the transmission of steps ST2701 to ST2703.
- the processing may be performed in response to the transmission in steps ST2704 to ST2706.
- the UE changes the PCell.
- the UE may clear the HARQ buffer of the S-PCell.
- the UE may perform the process of step T3402 disclosed in FIG. 34.
- the method for clearing the HARQ buffer of the UE or S-PCell disclosed above may be applied as appropriate.
- Another method for clearing the UE's HARQ buffer in the S-PCell is disclosed.
- the S-PCell may clear the UE's HARQ buffer when receiving a notification regarding successful access with the UE from the T-PCell.
- the S-PCell may clear the HARQ buffer of the UE when receiving a UE context modification request from the CU in step ST2725 in step ST2751.
- the S-PCell may clear the UE's HARQ buffer if it receives a notification from the CU about the release of the UE's context.
- the S-PCell may clear the HARQ buffer of the UE when receiving the UE context release from the CU in step ST2731 in step ST2752. By doing so, it is possible to reduce the buffer amount of the UE and S-PCell.
- the UE transmits a PCell change to the T-PCell.
- the UE transmits the data identifier of the data not received by the S-PCell to the T-PCell.
- the data identifier of the data not received by the S-PCell may be transmitted together with the change of the PCell.
- the T-PCell receives the data identifier of the data not received by the S-PCell from the UE. By doing so, the T-PCell can recognize the data identifier of data that the UE has not received at the S-PCell.
- the T-PCell derives the data that could not be delivered to the UE from the replicated data received from the CU in step ST3503, using the data identifier of the data that was received from the UE and was not received by the S-PCell. do.
- the T-PCell transmits duplicate data corresponding to the data that could not be delivered to the UE.
- the CU recognizes that the PCell has been changed to the T-PCell.
- the CU transmits data to the T-DU (DU#2) constituting the T-PCell.
- the T-DU transmits data received from the CU from the T-PCell to the UE.
- the CU may transmit a duplicate data discard request to the candidate DU in steps ST2722 to ST2725 (see FIG. 28) included in step ST2751.
- the candidate DU that has received the request to discard the duplicated data may discard the duplicated data.
- Storage capacity can be reduced.
- the duplicate data discard request may be transmitted together with the release of the candidate cell configuration transmitted from the CU to the candidate DU, or included in the release of the candidate cell configuration.
- the amount of signaling can be reduced.
- the release of the candidate cell settings transmitted from the CU to the candidate DU may be regarded as a request to discard the duplicate data.
- the candidate DU that has received the release of the candidate cell configuration from the CU may discard the duplicate data.
- the UE can receive data that could not be received from the S-PCell from the T-PCell. Even when inter-cell L1/L2 mobility is performed between different DUs, continuous communication is possible without losing data.
- the S-PCell transmits to the UE the data identifiers of data for which delivery confirmation was obtained in the S-PCell and/or data for which delivery confirmation was not obtained.
- the data identifier may be transmitted by MAC signaling. For example, it may be included in the MAC CE and transmitted. The data identifier can be transmitted early. Alternatively, the data identifier may be included in the DCI. It may be included in the DCI and transmitted on the PDCCH.
- the S-PCell may be transmitted to the UE together with the PCell change configuration, or may be included in the PCell change configuration.
- the UE transmits, to the T-PCell, the data identifiers of the data whose delivery was confirmed by the S-PCell and/or the data whose delivery was not confirmed.
- the T-DU receives the data identifier from the UE. This allows the T-DU to recognize data that is not delivered to the UE on the S-PCell.
- the T-DU transmits data that is not delivered on the S-PCell from the T-PCell to the UE.
- the UE will be able to receive data that was not delivered on the S-PCell from the T-PCell.
- the method disclosed above may be applied as appropriate for determining which data identifier to use, the information on the data identifier, and the method for transmitting it.
- the UE can continuously receive data from different DUs even if inter-cell L1/L2 mobility is performed between different DUs. It is possible to avoid discontinuous transmission and reception of data in inter-cell L1/L2 mobility between different DUs.
- FIG. 36 is a sequence diagram illustrating another example of a data transmission method in inter-cell L1/L2 mobility processing in Embodiment 6. Steps common to those in FIG. 35 are given the same step numbers, and common explanations will be omitted.
- the example in FIG. 36 shows a method for notifying the data identifier of undelivered data from the S-PCell via the UE.
- the S-PCell transmits the data identifier of undelivered data in the S-PCell to the UE.
- the S-PCell may transmit to the UE the data identifier of the undelivered data in the S-PCell together with the change in the PCell.
- the UE receives from the S-PCell the data identifier of the undelivered data on the S-PCell. By doing so, the UE can recognize the data identifier of undelivered data in the S-PCell.
- the UE changes the PCell.
- the UE transmits a PCell change to the T-PCell.
- the UE transmits the data identifier of the undelivered data in the S-PCell to the T-PCell.
- the data identifier of undelivered data on the S-PCell may be transmitted together with the PCell change.
- the T-PCell receives the data identifier of undelivered data in the S-PCell from the UE. By doing so, the T-PCell can recognize the data identifier of undelivered data in the S-PCell.
- the T-PCell derives the data that could not be delivered to the UE from the replicated data received from the CU in step ST3503, using the data identifier of the undelivered data in the S-PCell received from the UE.
- the T-PCell transmits duplicate data corresponding to the data that could not be delivered to the UE.
- the CU recognizes that the PCell has been changed to the T-PCell.
- the CU transmits data to the T-DU (DU#2) constituting the T-PCell.
- the T-DU transmits data received from the CU from the T-PCell to the UE.
- the S-PCell can transmit undelivered data to the UE from the T-PCell. Even when inter-cell L1/L2 mobility is performed between different DUs, continuous communication is possible without losing data.
- the UE performs HARQ processing on the data received from the S-PCell before changing the PCell.
- the T-PCell also performs HARQ processing.
- the UE performs HARQ processing on both the S-PCell and T-PCell until the HARQ processing on the S-PCell is completed.
- the UE receives data from both the S-PCell and the T-PCell. By doing so, there is no need to notify the T-DU about data that is not delivered by the S-PCell. Signaling load can be reduced and processing complexity can be avoided.
- S-PCell executes data transmission of the last RLC SN of S-PCell before PCell change.
- the data of the last PDCP PDU SN of the S-PCell before the PCell change is transmitted using the S-PCell.
- HARQ processing of these data is preferably performed by S-PCell.
- the UE receives the data transmitted from the S-PCell before the PCell change.
- data is also received from the T-PCell.
- the UE receives data from both the S-PCell and the T-PCell until the reception of the data from the S-PCell is completed.
- the UE may discard one of the data received redundantly from the S-PCell and the T-PCell.
- the reception of the data may end in failure.
- the maximum number of retransmissions in HARQ processing is exceeded, or the maximum number of retransmissions in RLC is exceeded.
- the transmission method the method disclosed above may be applied as appropriate.
- the UE can continuously receive data from different DUs even if inter-cell L1/L2 mobility is performed between different DUs. It is possible to avoid discontinuous transmission and reception of data in inter-cell L1/L2 mobility between different DUs.
- FIG. 37 is a sequence diagram illustrating another example of a data transmission method in inter-cell L1/L2 mobility processing in Embodiment 6. Steps common to those in FIG. 36 are given the same step numbers, and common explanations will be omitted.
- the example in FIG. 37 shows a method for transmitting data from the S-PCell even after changing the PCell. After changing the PCell, the UE receives data from both the S-PCell and the T-PCell until the data reception from the S-PCell is completed.
- step ST2522 the UE changes the PCell. After changing the PCell, the UE does not stop receiving data from the S-PCell until it receives an S-PCell reception stop request.
- the S-PCell transmits the data received from the CU before the PCell change to the UE.
- the T-PCell transmits the duplicate data received from the CU in step ST3503 to the UE. The UE continues to receive data from the S-PCell and also receives data from the T-PCell.
- the UE discards one of the data received redundantly from the S-PCell and the T-PCell. For example, data received later may be discarded.
- the S-PCell which has transmitted the data received from the CU before the PCell change to the UE, transmits an S-PCell reception stop request to the UE in step ST3702.
- the S-PCell may transmit the data identifier of the data that could not be transmitted to the UE together with the S-PCell reception stop request.
- the UE that receives the S-PCell reception stop request from the S-PCell stops receiving from the S-PCell.
- the UE may transmit, to the T-PCell, the data identifier of the undelivered data to the UE in the S-PCell.
- the T-PCell can recognize data that could not be delivered to the UE from the S-PCell.
- the T-PCell should check whether the data that could not be delivered from the S-PCell to the UE has already been transmitted, and if not, transmit the data. Data that could not be transmitted using S-PCell can be reliably transmitted.
- step ST3704 the UE stops discarding data received redundantly from the S-PCell and the T-PCell.
- the S-PCell reception stop request may be transmitted from the T-PCell to the UE.
- the T-PCell may transmit an S-PCell reception stop request to the UE.
- the UE is able to stop reception from the S-PCell at an early stage. The power consumption of the UE can be reduced.
- the CU that recognizes that the PCell has been changed to the T-PCell may transmit a transmission stop request to the UE for the S-DUs that constitute the S-PCell. .
- the S-DU that receives the request stops transmitting data from the S-PCell to the UE.
- the S-PCell reception stop request may be transmitted from the S-PCell to the UE in step ST2751.
- the CU that recognizes that the PCell has been changed to the T-PCell may transmit a transmission stop request to the UE for the S-DUs forming the S-PCell.
- the S-DU that has received the request transmits a request to stop receiving data from the S-PCell to the UE.
- the S-PCell also stops sending data to the UE. By doing so, it becomes possible to continue transmitting data from the S-PCell to the UE until, for example, data is transmitted from the CU to the T-PCell due to a change in the PCell.
- the UE can receive data more reliably.
- a UL data transmission/reception method during inter-cell L1/L2 mobility is disclosed. Clear the HARQ buffer at the UE.
- the HARQ buffer of the S-PCell may be cleared.
- the UE changes the PCell the UE transmits the identifier of the data for which delivery confirmation cannot be obtained to the T-PCell.
- the data may be undelivered data using PDCP. It is effective for inter-cell L1/L2 mobility within a DU or between DUs.
- the data may be undelivered data using RLC. This is effective for intra-DU inter-cell L1/L2 mobility.
- the data may be data for which HARQ processing has not been completed. This is effective for intra-DU inter-cell L1/L2 mobility.
- the UE may perform HARQ processing with both the S-PCell and the T-PCell.
- the UE performs HARQ processing on the S-PCell until the HARQ processing on the S-PCell ends.
- After changing the PCell perform HARQ processing with the T-PCell.
- the UE transmits data to both the S-PCell and the T-PCell until the HARQ processing of the S-PCell is completed.
- the UE When changing the PCell, the UE transmits data of the last RLC SN of the S-PCell using the S-PCell. After changing the PCell, data is sent to the T-PCell. The UE transmits data to both the S-PCell and the T-PCell until the transmission of data for the last RLC SN in the S-PCell is completed.
- the UE When changing the PCell, the UE transmits data of the last PDCP PDU SN of the S-PCell using the S-PCell. After changing the PCell, data is sent to the T-PCell. The UE transmits data to both the S-PCell and the T-PCell until the transmission of data for the last RLC SN in the S-PCell is completed.
- the CU may discard one of the data received redundantly from the S-DU and the T-DU. For example, discarding data received later. By using the one that was received first, data can be received early.
- the data transmission may end in failure.
- the maximum number of retransmissions in HARQ processing is exceeded, or the maximum number of retransmissions in RLC is exceeded.
- the transmission method the method disclosed above may be applied as appropriate.
- the UE can continuously transmit data from different DUs even if inter-cell L1/L2 mobility is performed between different DUs. It is possible to avoid discontinuous transmission and reception of data in inter-cell L1/L2 mobility between different DUs.
- Embodiment 6 data continuity between the UE and RAN due to inter-cell L1/L2 mobility is maintained. In inter-cell L1/L2 mobility, communication is possible without data loss.
- Embodiment 7 In conventional inter-cell mobility, the configuration of CA (Carrier Aggregation) is released, and CA is configured again after mobility. In inter-cell mobility, settings for packet duplication (see Non-Patent Document 2 (3GPP TS38.300)) are also released, and it is necessary to configure packet duplication again after mobility. Therefore, packet replication is interrupted due to inter-cell mobility, resulting in problems such as decreased communication reliability and increased delay.
- CA Carrier Aggregation
- Embodiment 7 discloses a method for solving such problems.
- CA settings are not released in inter-cell L1/L2 mobility.
- DL and/or UL CA settings are not released.
- the serving cell configuration may not be released.
- inter-cell L1/L2 mobility it may be statically determined in advance by standards etc. that the CA settings will not be released. By doing so, it is not necessary to perform RRC processing for releasing CA settings in inter-cell L1/L2 mobility processing. Enabling inter-cell L1/L2 mobility early.
- the method of not releasing CA configuration in inter-cell L1/L2 mobility may be limited to cases where inter-cell L1/L2 mobility is performed within one or more configured serving cells.
- the CA settings may be released.
- the DL and/or UL CA settings may be released.
- the serving cell configuration may be released.
- release of CA settings may be statically determined in advance by standards or the like.
- the UE releases the CA configuration when inter-cell L1/L2 mobility is configured.
- the gNB configures inter-cell L1/L2 mobility for the UE, it releases the CA configuration for the UE. By doing so, it is not necessary to perform RRC processing when changing PCell due to inter-cell L1/L2 mobility.
- the gNB may decide whether to release the CA settings or not.
- gNB may be a CU.
- the gNB notifies the UE in advance that the CA configuration will be released using inter-cell L1/L2 mobility.
- the gNB notifies the UE of the inter-cell L1/L2 mobility configuration, it notifies the UE that the CA configuration will be released.
- the release of the CA configuration may be sent together with or included in the configuration.
- the UE receives information from the gNB indicating that the CA configuration is to be released, the UE releases the CA configuration.
- the gNB transmits a message to the UE to release the CA configuration, it releases the CA configuration to the UE. By doing so, it is not necessary to perform RRC processing when changing PCell due to inter-cell L1/L2 mobility.
- the gNB may decide whether to release the CA configuration or not.
- gNB may be a CU.
- the gNB notifies the UE in advance whether or not to release the CA configuration in inter-cell L1/L2 mobility.
- the gNB notifies the UE of the inter-cell L1/L2 mobility configuration, it notifies the UE whether or not to release the CA configuration.
- Whether or not to release the CA settings may be transmitted together with or included in the settings.
- the UE receives information from the gNB indicating that the CA configuration is to be released, the UE releases the CA configuration.
- the CA configuration is not released.
- the gNB transmits a message to the UE to release the CA configuration, it releases the CA configuration to the UE.
- the gNB transmits to the UE that it will not release the CA configuration it does not release the CA configuration to the UE. By doing so, it becomes possible to control the CA settings during inter-cell L1/L2 mobility. Furthermore, there is no need to perform RRC processing when changing PCell due to inter-cell L1/L2 mobility.
- Packet duplication settings are not released for inter-cell L1/L2 mobility.
- the configuration of packet replication by the CA may not be released.
- inter-cell L1/L2 mobility it may be statically determined in advance by standards etc. that the packet duplication settings will not be released. By doing so, in the inter-cell L1/L2 mobility processing, it is not necessary to perform RRC processing for releasing the packet duplication settings. Enabling inter-cell L1/L2 mobility early.
- packet duplication settings may be released.
- release of packet duplication settings may be statically determined in advance by standards or the like.
- the UE releases the packet duplication configuration when inter-cell L1/L2 mobility is configured.
- the gNB configures the inter-cell L1/L2 mobility for the UE, it releases the packet duplication configuration to the UE. By doing so, it is not necessary to perform RRC processing when changing PCell due to inter-cell L1/L2 mobility.
- the gNB may decide whether to release the packet duplication configuration or not.
- gNB may be a CU.
- the gNB notifies the UE in advance that it will release the packet duplication configuration in inter-cell L1/L2 mobility. For example, when the gNB notifies the UE of the inter-cell L1/L2 mobility configuration, it notifies the UE that the packet duplication configuration will be released. Releasing the packet duplication configuration may be sent together with or included in the configuration.
- the UE receives information indicating that the packet duplication configuration is to be released from the gNB, the UE releases the packet duplication configuration.
- the gNB releases the packet duplication configuration to the UE when it transmits the release of the packet duplication configuration to the UE. By doing so, it is not necessary to perform RRC processing when changing PCell due to inter-cell L1/L2 mobility.
- the gNB may decide whether to release the packet replication configuration or not.
- gNB may be a CU.
- the gNB notifies the UE in advance whether or not to release the packet duplication configuration in inter-cell L1/L2 mobility.
- the gNB notifies the UE of the inter-cell L1/L2 mobility configuration, it notifies the UE whether or not to release the packet duplication configuration.
- Whether or not to release the packet duplication settings may be transmitted together with or included in the settings.
- the UE receives information indicating that the packet duplication configuration is to be released from the gNB, the UE releases the packet duplication configuration.
- the gNB releases the packet duplication configuration to the UE when it transmits the release of the packet duplication configuration to the UE.
- the gNB transmits to the UE that it will not release the packet duplication configuration, it does not release the packet duplication configuration to the UE.
- inter-cell L1/L2 mobility it may be set whether or not to release the packet duplication settings for each type of bearer. For example, the SRB releases the packet replication settings, and the DRB (Data Radio Bearer) sets the packet replication settings not to be released.
- the SRB releases the packet replication settings
- the DRB Data Radio Bearer
- flexible packet duplication settings can be made for each bearer. For example, when the reliability and delay performance required for each bearer differ in inter-cell L1/L2 mobility, flexible settings can be made to satisfy those performance requirements.
- the packet duplication configuration is not released in inter-cell L1/L2 mobility.
- packet duplication settings are released in inter-cell L1/L2 mobility.
- CA settings are not released in inter-cell L1/L2 mobility.
- CA settings are released in inter-cell L1/L2 mobility.
- packet duplication may be continued. Activation of packet replication may be continued. If the serving cell used for LCH (Logical Channel) transmission for packet duplication is not released, packet duplication may be continued.
- LCH Logical Channel
- packet duplication may be performed using T-PCell. It may be applied when packet replication is performed in S-PCell. If the S-PCell is configured to activate packet replication, the activation of packet replication may continue using the T-PCell when the PCell is changed due to inter-cell L1/L2 mobility. If the S-PCell is configured to activate packet duplication, the S-PCell may be deactivated by changing the PCell due to inter-cell L1/L2 mobility. These methods may be applied to SRB or DRB. It may be applied depending on the type of bearer. Flexible packet duplication becomes possible depending on the type of bearer. By doing so, it becomes possible to continue packet duplication with inter-cell L1/L2 mobility.
- packet replication is not performed in the S-PCell, it is preferable to continue packet replication using the same cell before and after changing the PCell due to inter-cell L1/L2 mobility. If packet replication is not activated on the S-PCell, packet replication may be continued using the same cell before and after changing the PCell due to inter-cell L1/L2 mobility. These methods may be applied to DRB. By doing so, packet duplication becomes possible outside of the PCell. It becomes possible to continue packet duplication with inter-cell L1/L2 mobility.
- Packet duplication may be deactivated during inter-cell L1/L2 mobility. Some or all of the DRBs configured for packet replication may be deactivated. Part or all of the RLC for packet duplication may be deactivated. Deactivation of packet duplication during inter-cell L1/L2 mobility may be statically determined by a standard or the like. Signaling can be made unnecessary.
- the gNB may notify the UE of deactivation of packet duplication during inter-cell L1/L2 mobility.
- the notification may be performed for some or all of the DRBs for which packet replication is configured, or for some or all of the RLCs for packet replication.
- the notification may be performed only for DRBs targeted for inter-cell L1/L2 mobility.
- the gNB that notifies the deactivation of packet duplication during inter-cell L1/L2 mobility may be a CU.
- the CU notifies the UE of the deactivation of packet duplication during inter-cell L1/L2 mobility.
- the gNB that notifies deactivation of packet duplication during inter-cell L1/L2 mobility may be a DU.
- the DU informs the UE of the deactivation of packet duplication during inter-cell L1/L2 mobility.
- RRC messages may be used to notify deactivation of packet duplication during inter-cell L1/L2 mobility.
- the CU may notify the deactivation of packet duplication along with or included in the intercell L1/L2 mobility configuration transmitted to the UE via the S-DU. By doing so, early notification can be made before the PCell change is decided.
- MAC signaling may be used to notify deactivation of packet duplication during inter-cell L1/L2 mobility.
- notification may be made using MAC CE.
- a new MAC CE may be provided for this notification.
- an existing MAC CE may be used.
- notification may be made using the MAC CE for DRB.
- notification may be made using MAC CE for RLC. Only the MAC CE for DRB is sufficient.
- the existing MAC CE processing complexity can be avoided.
- the DU may be notified to the UE together with the PCell change notification or included in the PCell change notification. By doing so, it becomes possible to notify the PCell change as well. For example, it is possible to notify the deactivation of packet duplication in consideration of which PCell is to be changed to.
- the T-PCell may obtain DRB and/or RLC information that has deactivated packet replication before changing the PCell.
- a method for obtaining DRB and/or RLC information for which a T-PCell has deactivated packet replication is disclosed.
- the UE After changing the PCell, the UE notifies the T-PCell of DRB and/or RLC information that has deactivated packet replication.
- An RRC message may be used to notify this information. For example, it may be transmitted during RA processing performed by the UE with the T-PCell.
- MAC signaling may be used to notify the information.
- the UE may send it together with the PCell change notification sent to the T-PCell, or it may be included in the notification.
- the information may be included in the UCI.
- the T-PCell can obtain DRB and/or RLC information for which packet replication has been deactivated before changing the PCell.
- the CU may send this information to the T-DU. It may be applied when the CU determines the DRB and/or RLC to deactivate packet replication. It is preferable to use F1 signaling for this transmission. T-PCell can acquire this information.
- the S-DU transmits this information to the CU.
- the CU sends this information to the T-DU. It may be applied when the DU determines the DRB and/or RLC for deactivating packet replication. It is preferable to use F1 signaling for this transmission.
- T-PCell can acquire this information.
- the S-DU transmits this information to the T-DU. It may be applied when the DU determines the DRB and/or RLC for deactivating packet replication. It is preferable to use the interface between DUs disclosed in Embodiment 4 for this transmission. T-PCell can acquire this information.
- the DRB and/or RLC for deactivating packet duplication may be statically determined in advance by a standard or the like.
- UE, DU, and CU can be recognized.
- the DRBs that deactivate packet replication may be part or all. Some or all of the RLCs may deactivate packet replication.
- the RLC that deactivates packet replication may be an S-RLC. By doing so, it becomes possible to set flexible deactivation of packet duplication during inter-cell L1/L2 mobility.
- the T-DU may use the acquired DRB and/or RLC information that deactivated the packet copy to determine the DRB and/or RLC that activates the packet copy.
- the DRB and/or RLC to be activated before and after changing the PCell may not be the same. By doing so, it becomes possible to set flexible activation and deactivation of packet duplication during inter-cell L1/L2 mobility.
- the T-PCell may notify the UE.
- the T-PCell may notify the UE of packet replication activation.
- An RRC message may be used for this notification from the T-PCell to the UE.
- it may be transmitted during RA processing.
- MAC signaling may be used for this notification from the T-PCell to the UE.
- the notification may be included in the MAC CE. This notification can be sent early.
- the notification from the T-PCell to the UE may be included in the DCI.
- the notification may be included in the DCI and transmitted on the PDCCH. This notification can be sent earlier.
- deactivation and activation of packet duplication can be flexibly set according to the radio wave propagation environment and RAN load during inter-cell L1/L2 mobility. Furthermore, since there is no need to release the packet duplication settings, control processing can be simplified.
- the method of activation and deactivation of packet duplication during inter-cell L1/L2 mobility has been disclosed above. These methods may be applied as appropriate to activation and deactivation of a serving cell during inter-cell L1/L2 mobility. For example, by applying this to CA serving cell activation and deactivation, the UE does not release CA and does not need to process unnecessary serving cells. The power consumption of the UE can be reduced.
- packet duplication may be activated (or may be continued). ) or deactivation.
- packet duplication is deactivated. For example, if packet duplication is to be activated (may be continued) during inter-cell L1/L2 mobility, the serving cell used for LCH transmission for packet duplication is activated (may be continued).
- the serving cell used for LCH transmission for packet duplication may be activated (or may be continued), or may be deactivated. By doing so, it is possible to avoid complicating the activation and deactivation processes of CA and packet duplication. Malfunctions can be reduced.
- the gNB may be MCG or SCG.
- PCell may be replaced with PSCell and applied as appropriate. For example, it may be applied to changing SPCell due to inter-cell L1/L2 mobility in SCG.
- RIS reconfigurable intelligent surface
- a subframe is an example of a time unit of communication in the fifth generation communication system.
- a subframe may be a scheduling unit.
- the processing described in units of subframes may be performed in units of TTI, slots, subslots, or minislots.
- the methods disclosed in each of the above-described embodiments and their modifications may be applied not only to V2X (vehicle-to-everything) services but also to services that use SL communication.
- the present invention may be applied to SL communication used in various services such as proximity-based service, public safety, communication between wearable terminals, and communication between devices in factories.
- a base station applied to a fifth generation wireless access system a smart repeater that has a beamforming function and performs relay processing between the base station and a communication terminal, or between a communication terminal connected to the base station and another communication terminal; including;
- the base station transmits information regarding beams used in the relay processing to the smart repeater,
- the smart repeater forms a beam based on information regarding the beam received from the base station and performs the relay processing.
- a communication system characterized by: (Additional note 2) an identifier is assigned to the smart repeater;
- the smart repeater determines whether the control signal transmitted from the base station is a control signal directed to the smart repeater based on the identifier assigned to the smart repeater.
- the communication system according to supplementary note 1, characterized in that: (Additional note 3)
- the base station transmits resource information, which is information regarding resources for transmitting and receiving the control signal, to the smart repeater,
- the smart repeater receives the control signal using a resource indicated by the resource information received from the base station.
- the communication system according to appendix 2 characterized in that: (Additional note 4) The smart repeater is transmitting a synchronization signal block for the communication terminal to perform a cell search;
- the communication system according to any one of Supplementary Notes 1 to 5, characterized in that: (Appendix 7) A base station applied to a fifth generation wireless access system, a communication terminal connected to the base station; including; When changing the cell to which a communication terminal is connected via any one of the plurality of cells configured by the base station, The base station transmits information regarding a new connection destination cell after the communication terminal changes the connection destination to the communication terminal, The communication terminal transmits the information regarding the new connection destination cell received from the base station to the new connection destination cell.
- a communication system characterized by: (Appendix 8) As the cell-by-cell identifier of the communication terminal used in the new connection destination cell after the connection destination change, a cell-by-cell identifier used by the communication terminal in the cell before the connection destination change is used;
- the base station Before the communication terminal changes the connection destination cell, the base station notifies the communication terminal of an identifier to be used by the communication terminal in the new connection destination cell after the connection destination change.
- the communication system according to any one of appendices 7 to 10 characterized in that:
- 202 Communication terminal device (mobile terminal), 210 Communication system, 213,240-1,240-2,750,801 Base station device (NR base station, base station), 214 5G core section, 215 Central unit, 216 Distributed unit , 217 Central unit for control plane, 218 Central unit for user plane, 219 TRP, 301, 403 Protocol processing section, 302 Application section, 304, 405 Encoder section, 305, 406 Modulation section, 306, 407 Frequency conversion section, 307- 1 to 307-4, 408-1 to 408-4 Antenna, 308, 409 Demodulation section, 309, 410 Decoder section, 310, 411, 526 Control section, 401 EPC communication section, 402 Other base station communication section, 412 5 GC communication Department, 521 Data Network Communication Department, 522 Base Station Communication Department, 523 User Plane Communication Department, 523-1 PDU Processing Department, 523-2 Mobility Anchoring Department, 525 Control Plane Control Department, 525-1 NAS Security Department, 525- 2 Idle state
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Priority Applications (4)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US18/854,706 US20250233653A1 (en) | 2022-04-22 | 2023-04-17 | Communication system |
| EP23791834.7A EP4514013A4 (en) | 2022-04-22 | 2023-04-17 | COMMUNICATION SYSTEM |
| CN202380034765.4A CN119032615A (zh) | 2022-04-22 | 2023-04-17 | 通信系统 |
| JP2024516253A JPWO2023204186A1 (cg-RX-API-DMAC7.html) | 2022-04-22 | 2023-04-17 |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| JP2022070970 | 2022-04-22 | ||
| JP2022-070970 | 2022-04-22 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2023204186A1 true WO2023204186A1 (ja) | 2023-10-26 |
Family
ID=88419839
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/JP2023/015354 Ceased WO2023204186A1 (ja) | 2022-04-22 | 2023-04-17 | 通信システム |
Country Status (5)
| Country | Link |
|---|---|
| US (1) | US20250233653A1 (cg-RX-API-DMAC7.html) |
| EP (1) | EP4514013A4 (cg-RX-API-DMAC7.html) |
| JP (1) | JPWO2023204186A1 (cg-RX-API-DMAC7.html) |
| CN (1) | CN119032615A (cg-RX-API-DMAC7.html) |
| WO (1) | WO2023204186A1 (cg-RX-API-DMAC7.html) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB2627239A (en) * | 2023-02-16 | 2024-08-21 | Samsung Electronics Co Ltd | Releasing connection of repeater node from access node |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US12706707B2 (en) * | 2022-09-14 | 2026-08-11 | Qualcomm Incorporated | Beam control techniques for a transparent repeater |
| JP7649280B2 (ja) * | 2022-09-27 | 2025-03-19 | Kddi株式会社 | 接続先のセルを効率的に変更する端末装置及び制御方法 |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2010028816A (ja) * | 2008-07-22 | 2010-02-04 | Ntt Docomo Inc | ハンドオーバー処理方法、基地局およびネットワーク通信システム |
| JP2011120015A (ja) * | 2009-12-03 | 2011-06-16 | Ntt Docomo Inc | 無線基地局、中継装置、無線通信方法 |
| WO2012035638A1 (ja) * | 2010-09-16 | 2012-03-22 | 富士通株式会社 | 無線通信方法、中継局、基地局及び移動局 |
| JP2016531506A (ja) * | 2013-08-09 | 2016-10-06 | パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカPanasonic Intellectual Property Corporation of America | 移動中の二重接続におけるueの効率的状況報告 |
| JP2017503415A (ja) * | 2014-07-11 | 2017-01-26 | 華為技術有限公司Huawei Technologies Co.,Ltd. | セルハンドオーバ方法、基地局、およびシステム |
| JP2019024211A (ja) * | 2016-01-25 | 2019-02-14 | 京セラ株式会社 | 無線端末及び基地局 |
| KR20190034094A (ko) * | 2017-09-22 | 2019-04-01 | 주식회사 케이티 | 릴레이 노드의 데이터 처리 방법 및 그 장치 |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11611421B2 (en) * | 2019-08-05 | 2023-03-21 | Qualcomm Incorporated | Techniques for in-band repeater control |
| US11711789B2 (en) * | 2020-08-14 | 2023-07-25 | Qualcomm Incorporated | Control signal design for smart repeater devices |
-
2023
- 2023-04-17 JP JP2024516253A patent/JPWO2023204186A1/ja active Pending
- 2023-04-17 US US18/854,706 patent/US20250233653A1/en active Pending
- 2023-04-17 WO PCT/JP2023/015354 patent/WO2023204186A1/ja not_active Ceased
- 2023-04-17 EP EP23791834.7A patent/EP4514013A4/en active Pending
- 2023-04-17 CN CN202380034765.4A patent/CN119032615A/zh active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2010028816A (ja) * | 2008-07-22 | 2010-02-04 | Ntt Docomo Inc | ハンドオーバー処理方法、基地局およびネットワーク通信システム |
| JP2011120015A (ja) * | 2009-12-03 | 2011-06-16 | Ntt Docomo Inc | 無線基地局、中継装置、無線通信方法 |
| WO2012035638A1 (ja) * | 2010-09-16 | 2012-03-22 | 富士通株式会社 | 無線通信方法、中継局、基地局及び移動局 |
| JP2016531506A (ja) * | 2013-08-09 | 2016-10-06 | パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカPanasonic Intellectual Property Corporation of America | 移動中の二重接続におけるueの効率的状況報告 |
| JP2017503415A (ja) * | 2014-07-11 | 2017-01-26 | 華為技術有限公司Huawei Technologies Co.,Ltd. | セルハンドオーバ方法、基地局、およびシステム |
| JP2019024211A (ja) * | 2016-01-25 | 2019-02-14 | 京セラ株式会社 | 無線端末及び基地局 |
| KR20190034094A (ko) * | 2017-09-22 | 2019-04-01 | 주식회사 케이티 | 릴레이 노드의 데이터 처리 방법 및 그 장치 |
Non-Patent Citations (2)
| Title |
|---|
| See also references of EP4514013A4 |
| UMESH ET AL.: "O-RAN Fronthaul Specification Overview", NTT DOCOMO TECHNICAL, vol. 27, no. 1, April 2019 (2019-04-01), pages 43 - 55, XP093134350 |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB2627239A (en) * | 2023-02-16 | 2024-08-21 | Samsung Electronics Co Ltd | Releasing connection of repeater node from access node |
Also Published As
| Publication number | Publication date |
|---|---|
| EP4514013A1 (en) | 2025-02-26 |
| US20250233653A1 (en) | 2025-07-17 |
| CN119032615A (zh) | 2024-11-26 |
| EP4514013A4 (en) | 2026-06-10 |
| JPWO2023204186A1 (cg-RX-API-DMAC7.html) | 2023-10-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7405911B2 (ja) | 無線通信システム、基地局 | |
| JP7686037B2 (ja) | ユーザ装置、基地局および通信システム | |
| JP7570317B2 (ja) | 通信端末装置、基地局装置および通信システム | |
| JP7420732B2 (ja) | ユーザ装置および通信システム | |
| US9843950B2 (en) | Method and apparatus for performing data transmission in wireless communication system | |
| US20250159561A1 (en) | Communication system and base station | |
| JP2025148405A (ja) | 第1の端末装置、第2の端末装置および通信システム | |
| EP4514013A1 (en) | Communication system | |
| KR20230147612A (ko) | 통신 시스템 및 기지국 | |
| WO2022181525A1 (ja) | 通信システムおよび通信端末 | |
| WO2024029423A1 (ja) | 通信システム | |
| WO2024029422A1 (ja) | 通信システム | |
| WO2024143363A1 (ja) | 通信システム | |
| US20250097790A1 (en) | Communication system | |
| EP4568393A1 (en) | Base station and communication system | |
| WO2024029424A1 (ja) | 通信システム | |
| WO2025146774A1 (ja) | 通信システム | |
| WO2024232311A1 (ja) | 通信システム | |
| WO2023054394A1 (ja) | 通信システム | |
| WO2025033207A1 (ja) | 通信システム | |
| WO2025187671A1 (ja) | 通信システム | |
| WO2024185748A1 (ja) | 通信システムおよび基地局 | |
| WO2023153335A1 (ja) | 通信システム | |
| WO2026074878A1 (ja) | 通信システム | |
| KR20210030397A (ko) | 무선 네트워크에서 충돌 처리 |
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: 23791834 Country of ref document: EP Kind code of ref document: A1 |
|
| ENP | Entry into the national phase |
Ref document number: 2024516253 Country of ref document: JP Kind code of ref document: A |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 18854706 Country of ref document: US |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 202447077939 Country of ref document: IN |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 202380034765.4 Country of ref document: CN |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 2023791834 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: 2023791834 Country of ref document: EP Effective date: 20241122 |
|
| WWP | Wipo information: published in national office |
Ref document number: 18854706 Country of ref document: US |