WO2021235499A1 - 通信制御方法 - Google Patents

通信制御方法 Download PDF

Info

Publication number
WO2021235499A1
WO2021235499A1 PCT/JP2021/019068 JP2021019068W WO2021235499A1 WO 2021235499 A1 WO2021235499 A1 WO 2021235499A1 JP 2021019068 W JP2021019068 W JP 2021019068W WO 2021235499 A1 WO2021235499 A1 WO 2021235499A1
Authority
WO
WIPO (PCT)
Prior art keywords
iab
node
relay node
notification
failure
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2021/019068
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
真人 藤代
ヘンリー チャン
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Kyocera Corp
Original Assignee
Kyocera Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Kyocera Corp filed Critical Kyocera Corp
Priority to JP2022524521A priority Critical patent/JP7495491B2/ja
Publication of WO2021235499A1 publication Critical patent/WO2021235499A1/ja
Priority to US18/057,033 priority patent/US12495348B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0064—Transmission or use of information for re-establishing the radio link of control information between different access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/36—Reselection control by user or terminal equipment
    • H04W36/362—Conditional handover
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H04W36/305—Handover due to radio link failure

Definitions

  • the present disclosure relates to a communication control method used in a cellular communication system.
  • IAB Integrated Access and Backhaul
  • One or more relay nodes intervene in the communication between the base station and the user device, and relay the communication.
  • the communication control method is a method used in a cellular communication system.
  • the communication device receives a failure occurrence notification indicating the occurrence of a failure of the backhaul link between the relay node and the parent node of the relay node from the relay node, and the communication device is described by the communication device.
  • the timer for determining the recovery waiting time from the failure is started.
  • the communication control method is a method used in a cellular communication system.
  • the first relay node having the conditional handover setting is from the second relay node, which is the parent node of the first relay node, to the second relay node and the parent node of the second relay node. It has the function of receiving a notification based on the failure of the backhaul link between the two, and the process for forcibly triggering the conditional handover by the first relay node based on the notification. ..
  • the communication control method is a method used in a cellular communication system.
  • the first relay node having the conditional handover setting is from the second relay node, which is the parent node of the first relay node, to the second relay node and the parent node of the second relay node.
  • FIG. 1 is a diagram showing a configuration of a cellular communication system 1 according to an embodiment.
  • Cellular communication system 1 is a 5th generation (5G) cellular communication system based on the 3GPP standard. Specifically, the wireless access system in the cellular communication system 1 is NR (New Radio), which is a 5G wireless access system. However, LTE (Long Term Evolution) may be applied to the cellular communication system 1 at least partially.
  • 5G 5th generation
  • NR New Radio
  • LTE Long Term Evolution
  • the cellular communication system 1 has a 5G core network (5GC) 10, a user device (UE: User Equipment) 100, a base station (called gNB) 200, and an IAB node 300.
  • the IAB node 300 is an example of a relay node.
  • the base station is an NR base station
  • the base station may be an LTE base station (that is, eNB).
  • the 5GC10 has an AMF (Access and Mobility Management Function) 11 and an UPF (User Plane Function) 12.
  • the AMF 11 is a device that performs various mobility controls and the like for the UE 100.
  • the AMF 11 manages information on the area in which the UE 100 is located by communicating with the UE 100 using NAS (Non-Access Stratum) signaling.
  • the UPF 12 is a device that controls the transfer of user data and the like.
  • Each gNB 200 is a fixed wireless communication node and manages one or a plurality of cells.
  • Cell is used as a term to indicate the smallest unit of wireless communication area.
  • Cell may be used as a term to indicate a function or resource for wireless communication with the UE 100.
  • One cell belongs to one carrier frequency.
  • Each gNB200 is interconnected with the 5GC10 via an interface called an NG interface.
  • FIG. 1 illustrates two gNB200-1 and gNB200-2 connected to 5GC10.
  • Each gNB200 is interconnected with other gNB200s in an adjacent relationship via an inter-base station interface called an Xn interface.
  • FIG. 1 shows an example in which gNB200-1 is connected to gNB200-2.
  • Each gNB 200 may be divided into an aggregate unit (CU: Central Unit) and a distributed unit (DU: Distributed Unit).
  • the CU and DU are connected to each other via an interface called an F1 interface.
  • the F1 protocol is a communication protocol between the CU and the DU, and includes the F1-C protocol, which is a control plane protocol, and the F1-U protocol, which is a user plane protocol.
  • the Cellular communication system 1 supports IAB that enables wireless relay of NR access by using NR for the backhaul.
  • the donor gNB200-1 is a terminal node of the NR backhaul on the network side, and is a gNB200 having an additional function of supporting IAB.
  • the backhaul can be multi-hop through multiple hops (ie, multiple IAB nodes 300).
  • FIG. 1 an example in which the IAB node 300-1 wirelessly connects to the donor gNB200-1, the IAB node 300-2 wirelessly connects to the IAB node 300-1, and the F1 protocol is transmitted in two backhaul hops. Is shown.
  • the UE 100 is a mobile wireless communication device that performs wireless communication with a cell.
  • the UE 100 may be any device as long as it is a device that performs wireless communication with the gNB 200 or the IAB node 300.
  • the UE 100 is a mobile phone terminal, a tablet terminal, a notebook PC, a sensor or a device provided in the sensor, and / or a vehicle or a device provided in the vehicle.
  • the UE 100 wirelessly connects to the IAB node 300 or gNB 200 via an access link.
  • FIG. 1 shows an example in which the UE 100 is wirelessly connected to the IAB node 300-2.
  • the UE 100 indirectly communicates with the donor gNB200-1 via the IAB node 300-2 and the IAB node 300-1.
  • FIG. 2 is a diagram showing the relationship between the IAB node 300, the parent node (Parent nodes), and the child node (Child nodes).
  • each IAB node 300 has an IAB-DU corresponding to a base station functional unit and an IAB-MT (Mobile Termination) corresponding to a user equipment functional unit.
  • IAB-DU corresponding to a base station functional unit
  • IAB-MT Mobile Termination
  • the adjacent node (that is, the upper node) on the NR Uu radio interface of the IAB-MT is called the parent node.
  • the parent node is the parent IAB node or the DU of the donor gNB200.
  • the radio link between the IAB-MT and the parent node is called a backhaul link.
  • FIG. 2 shows an example in which the parent nodes of the IAB node 300 are the IAB nodes 300P1 and 300P2. The direction toward the parent node is called upstream.
  • the adjacent node (that is, the lower node) on the NR access interface of the IAB-DU is called a child node.
  • the IAB-DU manages the cell in the same manner as the gNB200.
  • the IAB-DU terminates the NR Uu radio interface to the UE 100 and lower IAB nodes.
  • the IAB-DU supports the F1 protocol to the CU of donor gNB200-1.
  • FIG. 2 shows an example in which the child nodes of the IAB node 300 are the IAB nodes 300C1 to 300C3. The direction toward the child node is called downstream.
  • FIG. 3 is a diagram showing the configuration of gNB 200.
  • the gNB 200 has a wireless communication unit 210, a network communication unit 220, and a control unit 230.
  • the wireless communication unit 210 performs wireless communication with the UE 100 and wireless communication with the IAB node 300.
  • the wireless communication unit 210 has a reception unit 211 and a transmission unit 212.
  • the receiving unit 211 performs various receptions under the control of the control unit 230.
  • the receiving unit 211 includes an antenna, converts the radio signal received by the antenna into a baseband signal (received signal), and outputs the radio signal to the control unit 230.
  • the transmission unit 212 performs various transmissions under the control of the control unit 230.
  • the transmission unit 212 includes an antenna, converts a baseband signal (transmission signal) output by the control unit 230 into a radio signal, and transmits the baseband signal (transmission signal) from the antenna.
  • the network communication unit 220 performs wired communication (or wireless communication) with 5GC10 and wired communication (or wireless communication) with other adjacent gNB200.
  • the network communication unit 220 has a reception unit 221 and a transmission unit 222.
  • the receiving unit 221 performs various types of reception under the control of the control unit 230.
  • the receiving unit 221 receives a signal from the outside and outputs the received signal to the control unit 230.
  • the transmission unit 222 performs various transmissions under the control of the control unit 230.
  • the transmission unit 222 transmits the transmission signal output by the control unit 230 to the outside.
  • the control unit 230 performs various controls on the gNB 200.
  • the control unit 230 includes at least one memory and at least one processor electrically connected to the memory.
  • the memory stores a program executed by the processor and information used for processing by the processor.
  • the processor may include a baseband processor and a CPU (Central Processing Unit).
  • the baseband processor modulates / demodulates and encodes / decodes the baseband signal.
  • the CPU executes a program stored in the memory to perform various processes.
  • the processor performs processing of each layer described later.
  • FIG. 4 is a diagram showing the configuration of the IAB node 300.
  • the IAB node 300 has a wireless communication unit 310 and a control unit 320.
  • the IAB node 300 may have a plurality of wireless communication units 310.
  • the wireless communication unit 310 performs wireless communication (BH link) with the gNB 200 and wireless communication (access link) with the UE 100.
  • the wireless communication unit 310 for BH link communication and the wireless communication unit 310 for access link communication may be provided separately.
  • the wireless communication unit 310 has a receiving unit 311 and a transmitting unit 312.
  • the receiving unit 311 performs various receptions under the control of the control unit 320.
  • the receiving unit 311 includes an antenna, converts the radio signal received by the antenna into a baseband signal (received signal), and outputs the radio signal to the control unit 320.
  • the transmission unit 312 performs various transmissions under the control of the control unit 320.
  • the transmission unit 312 includes an antenna, converts a baseband signal (transmission signal) output by the control unit 320 into a radio signal, and transmits the baseband signal (transmission signal) from the antenna.
  • the control unit 320 performs various controls on the IAB node 300.
  • the control unit 320 includes at least one memory and at least one processor electrically connected to the memory.
  • the memory stores a program executed by the processor and information used for processing by the processor.
  • the processor may include a baseband processor and a CPU.
  • the baseband processor modulates / demodulates and encodes / decodes the baseband signal.
  • the CPU executes a program stored in the memory to perform various processes.
  • the processor performs processing of each layer described later.
  • FIG. 5 is a diagram showing the configuration of the UE 100. As shown in FIG. 5, the UE 100 has a wireless communication unit 110 and a control unit 120.
  • the wireless communication unit 110 performs wireless communication on the access link, that is, wireless communication with the gNB 200 and wireless communication with the IAB node 300. Further, the wireless communication unit 110 may perform wireless communication on the side link, that is, wireless communication with another UE 100.
  • the wireless communication unit 110 has a reception unit 111 and a transmission unit 112.
  • the receiving unit 111 performs various receptions under the control of the control unit 120.
  • the receiving unit 111 includes an antenna, converts the radio signal received by the antenna into a baseband signal (received signal), and outputs the radio signal to the control unit 120.
  • the transmission unit 112 performs various transmissions under the control of the control unit 120.
  • the transmission unit 112 includes an antenna, converts a baseband signal (transmission signal) output by the control unit 120 into a radio signal, and transmits the baseband signal (transmission signal) from the antenna.
  • the control unit 120 performs various controls on the UE 100.
  • the control unit 120 includes at least one memory and at least one processor electrically connected to the memory.
  • the memory stores a program executed by the processor and information used for processing by the processor.
  • the processor may include a baseband processor and a CPU.
  • the baseband processor modulates / demodulates and encodes / decodes the baseband signal.
  • the CPU executes a program stored in the memory to perform various processes.
  • the processor performs processing of each layer described later.
  • FIG. 6 is a diagram showing a protocol stack for RRC connection and NAS connection of IAB-MT.
  • the IAB-MT of the IAB node 300-2 includes a physical (PHY) layer, a MAC (Medium Access Control) layer, an RLC (Radio Link Control) layer, and a PDCP (Packet Data Control Protocol). It has a layer, an RRC (Radio PHY Control) layer, and a NAS (Non-Access Stratum) layer.
  • PHY physical
  • MAC Medium Access Control
  • RLC Radio Link Control
  • PDCP Packet Data Control Protocol
  • It has a layer, an RRC (Radio PHY Control) layer, and a NAS (Non-Access Stratum) layer.
  • the PHY layer performs coding / decoding, modulation / demodulation, antenna mapping / demapping, and resource mapping / demapping.
  • Data and control information are transmitted between the PHY layer of the IAB-MT of the IAB node 300-2 and the PHY layer of the IAB-DU of the IAB node 300-1 via a physical channel.
  • the MAC layer performs data priority control, retransmission processing by hybrid ARQ (HARQ), random access procedure, and the like. Data and control information are transmitted between the MAC layer of the IAB-MT of the IAB node 300-2 and the MAC layer of the IAB-DU of the IAB node 300-1 via the transport channel.
  • the MAC layer of the IAB-DU includes a scheduler. The scheduler determines the transport format (transport block size, modulation / coding method (MCS)) of the upper and lower links and the allocated resource block.
  • MCS modulation / coding method
  • the RLC layer transmits data to the receiving RLC layer by using the functions of the MAC layer and the PHY layer. Data and control information are transmitted between the RLC layer of the IAB-MT of the IAB node 300-2 and the RLC layer of the IAB-DU of the IAB node 300-1 via a logical channel.
  • the PDCP layer performs header compression / decompression and encryption / decryption. Data and control information are transmitted via the radio bearer between the PDCP layer of the IAB-MT of the IAB node 300-2 and the PDCP layer of the donor gNB200-1.
  • the RRC layer controls logical channels, transport channels, and physical channels according to the establishment, re-establishment, and release of radio bearers.
  • RRC signaling for various settings is transmitted between the RRC layer of the IAB-MT of the IAB node 300-2 and the RRC layer of the donor gNB200-1. If there is an RRC connection with the donor gNB200-1, the IAB-MT is in the RRC connected state. If there is no RRC connection with the donor gNB200-1, the IAB-MT is in the RRC idle state.
  • the NAS layer located above the RRC layer performs session management, mobility management, etc.
  • NAS signaling is transmitted between the NAS layer of the IAB-MT of the IAB node 300-2 and the AMF11.
  • FIG. 7 is a diagram showing a protocol stack related to the F1-U protocol.
  • FIG. 8 is a diagram showing a protocol stack for the F1-C protocol.
  • the donor gNB200-1 is divided into CU and DU.
  • each of the IAB-MT of the IAB node 300-2, the IAB-DU of the IAB node 300-1, the IAB-MT of the IAB node 300-1, and the DU of the donor gNB200-1 is an RLC layer. It has a BAP (Backhaul Adjustment Protocol) layer as an upper layer of the above.
  • the BAP layer is a layer that performs routing processing and bearer mapping / demapping processing. In the backhaul, the IP layer is transmitted via the BAP layer, which enables routing in multiple hops.
  • the PDU (Protocol Data Unit) of the BAP layer is transmitted by the backhaul RLC channel (BH NR RLC channel).
  • the backhaul RLC channel BH NR RLC channel.
  • the protocol stack of the F1-C protocol has an F1AP layer and a SCTP layer in place of the GTP-U layer and the UDP layer shown in FIG. 7.
  • FIG. 9 is a diagram for explaining an operation related to a failure-related notification according to an embodiment.
  • the node 500 is a parent node of the IAB node 300T and is a gNB 200 (donor node) or an IAB node 300 (parent IAB node).
  • the IAB-MT of the IAB node 300T has established a backhaul link (BH link) # 1 with the node 500.
  • the IAB-MT of the IAB node 300T is in the RRC connected state.
  • the IAB node 300C is a child node (child IAB node) of the IAB node 300T.
  • the IAB-MT of the IAB node 300C has established a BH link # 2 with the IAB node 300T.
  • the IAB-MT of the IAB node 300C is in the RRC connected state.
  • the IAB-MT of the IAB node 300C may be in the RRC idle state without establishing the BH link # 2 with the IAB node 300T.
  • the UE 100 has established an access link with the IAB node 300T.
  • the UE 100 is in the RRC connected state.
  • the UE 100 may be in the RRC idle state without establishing an access link with the IAB node 300T.
  • the IAB-MT of the IAB node 300T detects the radio link failure (BH RLF) of the BH link # 1.
  • the IAB-MT of the IAB node 300T detects the BH RLF as follows, and performs a recovery trial for recovery from the BH RLF.
  • the IAB-MT of the IAB node 300T detects an out-of-sync state (out-of-sync) N310 times in a row, it detects a radio problem (radio problem) and starts the timer T310 (start). do. After starting the timer T310, the IAB-MT of the IAB node 300T stops the timer T310 when the synchronization state (in-sync) is continuously detected N311 times.
  • the IAB-MT of the IAB node 300T detects the RLF and starts the timer T311 (that is, starts the RRC reestablishment process) when the timer T310 expires without stopping the timer T310, and the BH link. Perform cell selection processing to recover.
  • the IAB-MT of the IAB node 300T selects an appropriate cell by the cell selection process, and stops the timer T311 when the BH link is restored for the selected cell.
  • a suitable cell is one that meets at least the minimum radio quality standards.
  • the IAB-MT of the IAB node 300T transitions to the RRC idle state when the timer T311 expires without succeeding in recovering the BH link.
  • failure to recover from BH RLF after detecting BH RLF (that is, timer T311 has expired) may be referred to as failure of BH link recovery.
  • the IAB node 300T transmits a failure occurrence notification indicating the occurrence of BH RLF between the IAB node 300T and the node 500 to the downstream communication device.
  • the downstream communication device is at least one of the IAB node 300C and the UE 100.
  • the failure occurrence notification may be a notification indicating that BH RLF has been detected.
  • a failure occurrence notification is referred to as Type 1 Notification (RLF detected).
  • the failure occurrence notification may be a notification indicating that recovery from BH RLF is being attempted.
  • a failure occurrence notification will be referred to as Type 2 Notification (Trying to recover).
  • Type1 Notification and Type2 Notification are not distinguished, they are called Type1 / 2 Notification.
  • Type1 / 2 Notification may be included in a message of the BAP layer, for example, a BAP Control PDU (Protocol Data Unit).
  • the IAB node 300C connected to the IAB node 300T can receive the Type1 / 2 Notification included in the message of the BAP layer from the IAB node 300T.
  • the UE 100 since the UE 100 does not have the BAP layer, it cannot receive the Type1 / 2 Notification included in the message of the BAP layer.
  • the IAB-DU of the IAB node 300T includes Type1 / 2 Notification in the system information block type 1 (SIB1) and transmits it.
  • SIB1 system information block type 1
  • SIB1 is an example of system information (system information block). SIB1 defines the scheduling of other system information blocks and contains the information required for initial access. SIB1 is periodically broadcast by DL-SCH (downlink shared channel).
  • DL-SCH downlink shared channel
  • Each of the IAB-MT and UE100 of the IAB node 300C starts a timer (hereinafter referred to as "recovery failure determination timer") that determines the recovery waiting time from the BH RLF in response to the reception of the Type 1/2 Notification.
  • recovery failure determination timer a timer that determines the recovery waiting time from the BH RLF in response to the reception of the Type 1/2 Notification.
  • IAB-MT and UE100 can be unified to the same behavior by notifying Type1 / 2 Notification in SIB1 and determining BH RLF recovery failure of the parent node (IAB node 300T) by the recovery failure determination timer. ..
  • Each of the IAB-MT and the UE 100 of the IAB node 300C starts an operation for switching from the IAB node 300T to another node when the recovery failure determination timer expires.
  • FIG. 10 is a diagram showing the operation of the IAB-MT and the UE 100 of the IAB node 300C regarding the failure-related notification according to the embodiment.
  • the IAB-MT of the IAB node 300C and the UE 100 are simply referred to as a "communication device”.
  • the communication device receives SIB1 including Type1 / 2 Notification from the IAB-DU of the IAB node 300T.
  • the IAB-DU of the IAB node 300T includes Type1 / 2 Notification in the SIB1 that is periodically transmitted when the IAB-MT of the IAB node 300T detects the BH RLF or starts the recovery operation.
  • the BAP layer of the IAB node 300T transmits a BAP Control PDU (or MAC Control Element) including Type1 / 2 Notification when the IAB-MT of the IAB node 300T detects the BH RLF or starts the recovery operation. May be good.
  • the communication device starts the recovery failure determination timer in response to the reception of Type1 / 2 Notification.
  • the timer value of the recovery failure determination timer may be a predetermined fixed value, a variable value set by SIB or the like from the IAB node 300T to the communication device, or communication from the donor node. It may be a variable value set by unicast signaling (RRC Configuration message, etc.) for the device.
  • the recovery failure determination timer value may be equal to or less than the total value of the timer T311 (timer for cell selection) and the timer T301 (timer for RRC reestablishment) of the IAB-MT of the IAB node 300T.
  • the communication device may continue to monitor Type1 / 2 Notification (SIB1) while the recovery failure determination timer is operating.
  • the communication device may stop the uplink transmission while the recovery failure determination timer is operating.
  • step S13 the communication device determines whether or not the predetermined condition for stopping the recovery failure determination timer is satisfied.
  • the predetermined condition is one of the following conditions 1 to 5, or a combination of two or more of the following conditions 1 to 5.
  • Condition 1 Repeated transmission of SIB1 including Type1 / 2 Notification has stopped. That is, condition 1 is a condition that the communication device has not received SIB1 including Type1 / 2 Notification for a certain period of time. When the communication device detects that the repeated reception of SIB1 including Type1 / 2 Notification is stopped, it is determined that condition 1 is satisfied.
  • Type 3 Notification (RLF recovered) was received from the IAB node 300T.
  • Type3 Notification is a recovery notification indicating that the IAB node 300T has recovered from BH RLF.
  • the Type 3 Notification may be transmitted from the IAB node 300T by the BAP Control PDU, or may be transmitted from the IAB node 300T by the SIB1.
  • the IAB node 300C can receive the Type 3 Notification, but the UE 100 cannot receive the Type 3 Notification.
  • the IAB node 300C can quickly grasp that the IAB node 300T has recovered from the BH RLF by receiving the BAP Control PDU including the Type 3 Notification.
  • the IAB node 300C which is a kind of network node, can be handled more advantageously than the UE 100.
  • Type 4 Notification (Recovery fiber) was received from the IAB node 300T.
  • Type4 Notification is a recovery failure notification indicating that the IAB node 300T has failed to recover from the BH RLF.
  • the Type 4 Notification may be transmitted from the IAB node 300T by the BAP Control PDU, or may be transmitted from the IAB node 300T by the SIB1.
  • the communication device that has received the Type 4 Notification stops the recovery failure determination timer, considers that an RLF has occurred, and starts the RRC reestablishment process for recovering from the RLF.
  • the IAB node 300C can receive the Type 4 Notification, but the UE 100 cannot receive the Type 4 Notification.
  • the IAB node 300C can quickly grasp that the IAB node 300T has failed to recover from the BH RLF.
  • the IAB node 300C which is a kind of network node, can be handled more advantageously than the UE 100.
  • Condition 4 The communication device has performed cell reselection (RRC idle state) or handover (RRC connected state). That is, the condition 4 is a condition that the communication device has switched from the cell of the IAB node 300T that has detected the BH RLF to another cell.
  • the handover may include a conditional handover described later.
  • Condition 5 The communication device has detected RLF.
  • Condition 5 is a condition that a failure has occurred in the link of the communication device (BH link # 2 or access link shown in FIG. 9). In this case, the communication device starts the RRC reestablishment process for recovering from the RLF.
  • step S14 the communication device stops the recovery failure determination timer.
  • step S15 the communication device determines whether or not the recovery failure determination timer has expired. If it is determined that the recovery failure determination timer has not expired (step S15: NO), the process returns to step S13.
  • step S16 the communication device starts a predetermined operation for switching from the IAB node 300T to another node.
  • the predetermined operation is one of the following operations 1 to 4, or a combination of two or more of the following operations 1 to 4.
  • Operation 1 It is considered that RLF has occurred (when the communication device is in the RRC connected state). Specifically, in the communication device in the RRC connected state, the IAB node 300T is BH RLF even though the link (BH link # 2 or access link) between the own device and the IAB node 300T is normal. It is determined that the recovery from the above has failed, and it is considered that RLF has occurred in the own device.
  • Operation 2 Trigger RRC re-establishment (when the communication device is in the RRC connected state). The operation 2 may be performed after the operation 1.
  • Operation 3 Trigger cell reselection (when the communication device is in the RRC idle state). That is, when the recovery failure determination timer expires, the communication device in the RRC idle state reselects the cell from the cell (serving cell) of the IAB node 300T to another cell.
  • Operation 4 Trigger a conditional handover (when the communication device is in the RRC connected state). The details of the conditional handover will be described later.
  • the communication device in the RRC connected state performs cell selection processing for selecting the cell of the RRC reestablishment destination.
  • the communication device in the RRC idle state performs cell reselection processing.
  • the communication device In the cell selection process and the cell reselection process, the communication device generally selects a cell having a good wireless state (for example, a cell having a large measured reference signal reception power).
  • the communication device may exclude the cell of the IAB node 300T, which is the original serving cell, from the selection candidates.
  • the communication device may exclude the cell of the IAB node 300T from the selection candidates for a certain period of time (for example, 300 seconds or the like).
  • the communication device may exclude the cell of the IAB node 300T from the selection candidates only in the first cell selection process or cell reselection process after the recovery failure determination timer expires.
  • the communication device does not select the cell of the IAB node 300T, so that the offset of minus infinity or a sufficiently large minus offset (-200 dB) with respect to the measured value of the radio state of the cell of the cell of the IAB node 300T (for example, the reference signal reception power). Etc.) may be given.
  • the conditional handover setting includes a candidate cell for the handover and a trigger condition for the handover.
  • the conditional handover setting may include a plurality of combinations of candidate cells and trigger conditions.
  • the conditional handover settings further include the RRC settings corresponding to the candidate cells.
  • the UE 100 reports the measured value of the radio state of the serving cell and / or the adjacent cell to the gNB 200, and based on this report, the gNB 200 determines the handover to the adjacent cell and transmits the handover instruction to the UE 100. .. Therefore, when the radio state of the serving cell is suddenly deteriorated, in general handover, communication may be interrupted before the handover is executed.
  • the conditional handover when the preset trigger condition is satisfied, the handover to the candidate cell corresponding to the trigger condition can be autonomously executed. Therefore, a problem in general handover can be solved.
  • Event A3 is an event in which the radio state of the adjacent cell is better than the radio state of the serving cell by a predetermined amount (predetermined offset) or more.
  • Event A5 is an event in which the radio state of the serving cell is deteriorated from the first threshold value and the radio state of the adjacent cell is better than the second threshold value.
  • the IAB node 300C having the conditional handover setting receives a notification from the parent node IAB node 300T based on the BH RLF on the BH link # 1 between the IAB node 300T and the node 500. ..
  • the notification based on BH RLF may be the above-mentioned Type1 / 2 Notification or Type4 Notification.
  • the IAB node 300C performs a process for forcibly triggering a conditional handover based on the notification. As a result, under the situation where the IAB node 300T detects the BH RLF, the handover to the candidate cell of the conditional handover can be started more reliably, so that the possibility of communication interruption and the interruption time can be reduced.
  • FIG. 11 is a diagram showing an operation pattern 1 of the IAB node 300C regarding the conditional handover according to one embodiment.
  • step S21 the IAB-MT (or BAP layer) of the IAB node 300C receives Type1 / 2 Notification or Type4 Notification from the IAB node 300T.
  • the recovery failure determination timer described above is started. Here, the description will proceed on the assumption that the recovery failure determination timer has expired.
  • step S22 the IAB-MT of the IAB node 300C indicates that RLF (BH RLF) has occurred in the IAB node 300C in response to the expiration of the recovery failure determination timer or the reception of Type 4 Notification from the IAB node 300T. I reckon.
  • RLF BH RLF
  • step S23 the IAB-MT of the IAB node 300C performs a process for forcibly triggering the set conditional handover.
  • a process for forcibly triggering the set conditional handover is one of the following first process and second process.
  • the IAB-MT of the IAB node 300C controls at least one of the measured value of the radio state and the offset value given to the measured value so that the trigger condition in the conditional handover is satisfied. Then, the IAB-MT of the IAB node 300C performs such control and then evaluates the trigger condition in the conditional handover.
  • the IAB-MT of the IAB node 300C is minus infinite with respect to the measured value of the radio state (for example, the reference signal reception power) of the serving cell (cell of the IAB node 300T) so as to be zero.
  • An offset or a sufficiently large negative offset (-200 dB, etc.) may be added.
  • Such processing may be applied only in the case of the above-mentioned event A5.
  • the evaluation may be performed after considering that the radio state of the serving cell has deteriorated from the first threshold value.
  • a positive offset is given to the measured value of the radio state of the candidate cell so that the measured value of the radio state of the candidate cell is relatively higher than the measured value of the radio state of the serving cell.
  • a negative offset may be added to the measured value of the radio state of the serving cell.
  • the IAB-MT of the IAB node 300C selects one from the plurality of candidate cells and selects one of the selected candidate cells. Execute the handover (step S24).
  • the offset value may be a predetermined fixed value, may be a variable value set by SIB or the like from the IAB node 300T to the IAB node 300C, or may be a donor. It may be a variable value set by unicast signaling (RRC Configuration message, etc.) from the node to the IAB node 300C.
  • the IAB-MT of the IAB node 300C omits the evaluation of the trigger condition in the conditional handover, and considers that the trigger condition is satisfied by the candidate cell. For example, the IAB-MT of the IAB node 300C skips the evaluation of the trigger condition and forcibly triggers the conditional handover, and considers that all the set candidate cells satisfy the trigger condition.
  • the IAB-MT of the IAB node 300C may consider that the trigger condition is satisfied only for the cells satisfying the minimum required radio quality standard (S-criterion) among all the set candidate cells. good.
  • the IAB-MT of the IAB node 300C may consider that the trigger condition is satisfied only for the candidate cell to which the event A3 is specified or only the candidate cell to which the event A5 is specified among all the candidate cells set. ..
  • the IAB-MT of the IAB node 300C selects one from the plurality of candidate cells and selects one of the selected candidate cells. Execute the handover (step S24).
  • the IAB node 300C having the conditional handover setting is a Type 1/2 Notification (failure occurrence notification) indicating the occurrence of BH RLF of the backhaul link # 1 of the IAB node 300T from the parent node IAB node 300T. ) Is received.
  • the trigger of the conditional handover is based on the Type 1/2 Notification. Evaluate the conditions. As a result, the conditional handover can be triggered at an earlier stage, and the possibility of communication interruption and the interruption time can be reduced.
  • FIG. 12 is a diagram showing an operation pattern 2 of the IAB node 300C regarding the conditional handover according to one embodiment.
  • step S31 the IAB-MT (or BAP layer) of the IAB node 300C receives the Type 1/2 Notification from the IAB node 300T.
  • step S32 the IAB-MT of the IAB node 300C evaluates the trigger condition of the conditional handover.
  • the IAB-MT of the IAB node 300C may evaluate the trigger condition of the conditional handover without considering that the BH RLF has occurred because the float of FIG. 11 is different.
  • the trigger condition may include the condition that Type1 / 2 Notification is received from the IAB node 300T a predetermined number of times or more within a predetermined time. For example, when the Type 1/2 Notification is transmitted in the periodically broadcast SIB1, the IAB-MT of the IAB node 300C receives the Type 1/2 Notification more than a certain number of times within a predetermined time, and the trigger condition is Is evaluated as being satisfied. The IAB-MT of the IAB node 300C may evaluate that the trigger condition is satisfied when the Type 1/2 Notification is simply received once.
  • the IAB node 300T may include the measured value of the radio state (BH radio quality) in the BH link # 1 in the Type 1/2 Notification and transmit it.
  • the IAB-MT of the IAB node 300C may evaluate the trigger condition using the measured value included in Type1 / 2 Notification.
  • This trigger condition may be a condition that the BH radio quality of the IAB node 300T is below the threshold value.
  • the BH radio quality may be at least one of the reference signal reception power (RSRP), the reference signal reception quality (RSRQ), and the signal-to-interference noise ratio (SINR), and these values are quantized. (For example, Good / Normal / Bad, etc.).
  • the trigger condition may include the above-mentioned event A3 and / or event A5.
  • the same method as the first process of the operation pattern 1 can be applied.
  • the IAB-MT of the IAB node 300C may use the radio state (BH radio quality) at BH link # 1 as described above instead of the radio quality of the serving cell in the evaluation of event A3 and / or event A5.
  • Event A3 and / or event A5 may be evaluated.
  • step S34 the IAB-MT of the IAB node 300C executes the handover to the candidate cell that satisfies the trigger condition. do.
  • the IAB-MT of the IAB node 300C selects one from the plurality of candidate cells and performs handover to the selected candidate cells.
  • FIGS. 11 to 12 may be implemented in combination with each other. For example, some steps in each flow of FIGS. 11-12 may be applied to other flows.
  • the base station in the cellular communication system 1 may be an eNB which is an LTE base station.
  • the core network in the cellular communication system 1 may be an EPC (Evolved Packet Core).
  • the gNB may be connected to the EPC
  • the eNB may be connected to the 5GC
  • the gNB and the eNB may be connected via an inter-base station interface (Xn interface, X2 interface).
  • a program for causing a computer to execute each process according to the above-described embodiment and modification may be provided.
  • the program may also be recorded on a computer-readable medium.
  • Computer-readable media can be used to install programs on a computer.
  • the computer-readable medium on which the program is recorded may be a non-transient recording medium.
  • the non-transient recording medium is not particularly limited, but may be, for example, a recording medium such as a CD-ROM or a DVD-ROM.
  • a chipset composed of a memory for storing a program for executing each process performed by the UE 100, gNB 200, or the IAB node 300 and a processor for executing the program stored in the memory may be provided.
  • IAB integrated Access AND Backhaul
  • BH RLF backhaul radio link failure
  • RAN2 actually had some discussions at the research stage and the work stage. For example, in TR38.874 statement 9.7.15, RAN2 "prepares an alternative backhaul link and route in advance (ie, before RLF occurs) for efficient BH RLF recovery. I identified that. This mechanism is therefore considered a CHO. Therefore, the CHO may be set on each IAB node for a stable BH connection. In addition, RAN2 also discussed various ways to use CHO in the email discussion, but the Stage 2 specification finally removed the CHO aspect from its statement 9.2.7.
  • Radio Link Failure (Discussion) (Wireless link failure scenario in IAB)
  • the UE declares a radio link failure (RLF) if any of the following criteria are met: -Expiration of the radio problem timer initiated after the indication of the radio problem from the physical layer (the UE will stop the timer if the radio problem recovers before the timer expires).
  • IAB-MT will declare an RLF when it receives a BH RLF notification, ie a "recovery failure" of the parent BH link, even if its own BH link is still good. be.
  • Findings 1 When IAB-MT receives a BH RLF notification, it declares an RLF even if its own BH link is still good.
  • the radio condition of the BH link deteriorates before the RLF declaration. If the trigger condition (CHO event A3 / A5 related to CHO setting) is satisfied, CHO may be triggered. This is a normal scenario that triggers CHO, and IAB-MT is also free to use CHO.
  • Finding 2 If there is a problem with the own BH link, as in the current specifications, the IAB-MT was satisfied with the CHO event A3 / A5 due to the poor radio condition of the own BH link before the RLF declaration. If so, CHO can be triggered.
  • the UE After the RLF is declared, that is, if the CHO has not yet been triggered for some reason, the UE will perform cell selection, and if the selected cell is a CHO candidate, it will try to execute CHO. Therefore, IAB-MT can use this mechanism without extension.
  • the UE In the case of CHO, after the RLF is declared in the source cell, the UE does the following: -Stay on the RRC connection-If you select the appropriate cell, the selected cell is a CHO candidate, and the network configures the UE to try the CHO after the RLF, the UE will try to execute the CHO once. Otherwise, re-establishment is performed. -If a suitable cell is not found within a certain period of time after the RLF is declared, it enters the RRC idle.
  • IAB-MT can attempt CHO execution after the RLF declaration.
  • RAN2 has already agreed that "fast MCG link recovery is supported by NRDC and ENDC” and a new failure type "bh-RLF" will be introduced in both MCG failure information and SCG failure information. Also, as discussed in Findings 2 and 3 above, CHO can be used in the IAB. Therefore, statements that may cause unnecessary confusion, such as limiting RLF recovery, should be removed from TS38.300.
  • Proposal 1 RAN2 should agree to remove "use of RRC reestablishment procedure" from statement 9.2.7 of TS38.300 to avoid unnecessary misunderstanding of RLF recovery in IAB. ..
  • Finding 4 If there is a problem with the parent's BH link, IAB-MT cannot trigger CHO because its own BH link is still / always good.
  • IAB-MT may not select CHO candidate cells, which means that CHO may not be executed.
  • IAB-MT may select the (previous) parent node that sent the BH RLF notification.
  • the IAB node may not execute CHO because it depends on cell selection.
  • IAB-MT should "trigger" CHO when it receives a BH RLF notification ("recovery failure").
  • Proposal 2 RAN2 should agree that IAB-MT "triggers" the CHO upon receipt of the BH RLF notification if the CHO is set.
  • Table 1 shows CHO-related operations from the perspective of IAB-MT (when CHO is set).
  • Proposal 2 can be agreed, the question is how to trigger the CHO upon receipt of the BH RLF notification (“recovery failure”).
  • the following options for CHO evaluation can be considered.
  • IAB-MT considers the RSRP of the source cell to be minus infinity [dBm].
  • IAB-MT considers that all the set CHO execution conditions are satisfied.
  • Proposal 3 RAN2 meets all set CHO trigger conditions if IAB-MT considers the RSRP of the source cell to be minus infinity (option 1) or if it is set when the BH RLF notification is received. It should be considered whether it is considered to be done (option 2).
  • FIGS. 15 and 16 Examples of specification changes for Option 1 and Option 2 when Proposal 3 can be agreed are shown in FIGS. 15 and 16, respectively.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/JP2021/019068 2020-05-20 2021-05-19 通信制御方法 Ceased WO2021235499A1 (ja)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2022524521A JP7495491B2 (ja) 2020-05-20 2021-05-19 通信制御方法及び通信装置
US18/057,033 US12495348B2 (en) 2020-05-20 2022-11-18 Communication control method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063027634P 2020-05-20 2020-05-20
US63/027,634 2020-05-20

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/057,033 Continuation US12495348B2 (en) 2020-05-20 2022-11-18 Communication control method

Publications (1)

Publication Number Publication Date
WO2021235499A1 true WO2021235499A1 (ja) 2021-11-25

Family

ID=78707902

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2021/019068 Ceased WO2021235499A1 (ja) 2020-05-20 2021-05-19 通信制御方法

Country Status (3)

Country Link
US (1) US12495348B2 (https=)
JP (1) JP7495491B2 (https=)
WO (1) WO2021235499A1 (https=)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020175876A1 (en) * 2019-02-26 2020-09-03 Lg Electronics Inc. Relaxation of mobility condition based on serving cell quality
KR20220017863A (ko) * 2020-08-05 2022-02-14 삼성전자주식회사 무선 통신 시스템에서 결합 액세스 및 백홀 시스템을 위한 개선된 셀 선택 및 실패 처리 방법 및 장치
EP4197242A1 (en) * 2020-08-11 2023-06-21 Telefonaktiebolaget LM Ericsson (publ) Adapting integrated access and backhaul node cell coverage
US20240049326A1 (en) * 2022-08-05 2024-02-08 Shanghai Langbo Communication Technology Company Limited Method and device used for wireless communication
WO2025206991A1 (en) * 2024-03-27 2025-10-02 Telefonaktiebolaget Lm Ericsson (Publ) First network node, second network node, third network node and methods performed thereby, for handling a failure

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020032528A1 (ko) * 2018-08-07 2020-02-13 엘지전자 주식회사 무선 통신 시스템에서 노드의 동작 방법 및 상기 방법을 이용하는 장치
CN112740744B (zh) * 2018-09-20 2024-06-11 夏普株式会社 用于处理无线中继网络中的无线电链路失败的系统、设备和方法
WO2020061569A1 (en) * 2018-09-21 2020-03-26 Perk-Up, Inc. D/B/A Kari-Out Co. Leak-resistant paper clamshell containers
WO2020067517A1 (en) * 2018-09-27 2020-04-02 Sharp Kabushiki Kaisha Systems, Devices, and Methods for Handling Radio Link Monitoring and Radio Link Failures in Wireless Relay Networks
EP3841830A4 (en) * 2018-09-27 2022-05-25 Samsung Electronics Co., Ltd. METHOD OF PROCESSING NODE FAULTS IN AN INTEGRATED ACCESS AND BACKHAUL SYSTEM, AND METHOD OF TRANSMITTING ROUTING INFORMATION THEREIN
WO2020066943A1 (en) * 2018-09-27 2020-04-02 Sharp Kabushiki Kaisha Systems, Devices, and Methods for Handling Radio Link Failures in Wireless Relay Networks
WO2020069158A1 (en) * 2018-09-28 2020-04-02 Intel Corporation Route adaptation in multi-hop relay networks
WO2020090988A1 (en) * 2018-10-31 2020-05-07 Sharp Kabushiki Kaisha Methods and apparatus for using conditional handovers for wireless backhaul
WO2020090987A1 (en) * 2018-10-31 2020-05-07 Sharp Kabushiki Kaisha Methods and apparatus for using redundant links in wireless backhaul
WO2020167036A1 (en) * 2019-02-14 2020-08-20 Lg Electronics Inc. Method and apparatus for failure notification on backhaul link in wireless communication system
US11166335B2 (en) * 2019-02-14 2021-11-02 Lg Electronics Inc. Method and apparatus for handling backhaul link failure in wireless communication system
KR20210122799A (ko) * 2019-02-14 2021-10-12 샤프 가부시키가이샤 무선 릴레이 네트워크들에서 무선 링크 실패의 통지
US11963024B2 (en) * 2019-02-15 2024-04-16 Lg Electronics Inc. Method and apparatus for backhaul status reporting in wireless communication system
WO2020171750A1 (en) * 2019-02-22 2020-08-27 Telefonaktiebolaget Lm Ericsson (Publ) Radio network nodes, wireless device and methods performed therein
WO2020222308A1 (en) * 2019-05-02 2020-11-05 Sharp Kabushiki Kaisha Conditional handovers for wireless relay networks
US12058540B2 (en) * 2019-05-02 2024-08-06 Sony Group Corporation Methods, infrastructure equipment and wireless communications networks for handling beam failures
US12289652B2 (en) * 2019-05-02 2025-04-29 Sharp Kabushiki Kaisha Failure information for wireless relay networks
US20230089657A1 (en) * 2020-02-12 2023-03-23 Sharp Kabushiki Kaisha Rrc update procedures in iab networks
WO2021161866A1 (en) * 2020-02-12 2021-08-19 Sharp Kabushiki Kaisha Updating radio resource control connections in iab network
BR112022020228A2 (pt) * 2020-04-09 2022-11-22 Ericsson Telefon Ab L M Métodos para realizar transferência para uma célula alvo e para suportar transferência de um equipamento de usuário para uma célula alvo, equipamento de usuário, meio legível por computador não transitório, e, nó de rede sem fio
US20230164658A1 (en) * 2020-05-01 2023-05-25 Sharp Kabushiki Kaisha Enhanced conditional handover procedures in iab networks

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Backhaul RLF Recovery", 3GPP DRAFT; R2-1906070 BACKHAUL RLF RECOVERY, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Reno, USA; 20190513 - 20190517, 3 May 2019 (2019-05-03), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051710397 *
KYOCERA: "Further discussion on Backhaul RLF handling", 3GPP DRAFT; R2-1909635_IAB_BH-RLF-NOTIFICATION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Prague, Czech Republic; 20190826 - 20190830, 16 August 2019 (2019-08-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051767430 *
KYOCERA: "Possible issues on Backhaul RLF handling", 3GPP DRAFT; R2-2003314, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Online; 20200420 - 20200430, 10 April 2020 (2020-04-10), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051871286 *
ZTE, SANECHIPS: "Discussion on IAB BH RLF handling", 3GPP DRAFT; R2-1906575 DISCUSSION ON IAB BH RLF HANDLING, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Reno, USA; 20190513 - 20190517, 3 May 2019 (2019-05-03), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051710886 *

Also Published As

Publication number Publication date
US20230080014A1 (en) 2023-03-16
JP7495491B2 (ja) 2024-06-04
JPWO2021235499A1 (https=) 2021-11-25
US12495348B2 (en) 2025-12-09

Similar Documents

Publication Publication Date Title
JP7212199B2 (ja) 通信制御方法
JP7322230B2 (ja) 通信制御方法
JP7422916B2 (ja) 通信制御方法、無線中継装置及びプロセッサ
JP7495491B2 (ja) 通信制御方法及び通信装置
JP7522797B2 (ja) 通信制御方法
JP7520164B2 (ja) 通信制御方法、遠隔ユーザ装置、プロセッサ、システム及びプログラム
CN103179597B (zh) 一种无线保真技术的处理方法和用户设备
JP2023536001A (ja) サイドリンクリレーシステムにおける障害処理手順のための方法および装置
WO2021192918A1 (ja) 通信制御方法
JP7658003B2 (ja) 通信制御方法
WO2021024821A1 (ja) 通信制御方法
JPWO2020145000A1 (ja) 通信制御方法
JP7410167B2 (ja) 通信制御方法及び無線中継装置
JP7696471B2 (ja) 通信制御方法、セルラ通信システム、ユーザ装置、プログラム及びチップセット
US12426116B2 (en) Communication control method
JP2026001071A (ja) 通信制御方法
WO2022210546A1 (ja) 通信制御方法
WO2021066161A1 (ja) 通信制御方法及びユーザ装置
JP7426383B2 (ja) 通信制御方法

Legal Events

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

Ref document number: 21807992

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022524521

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21807992

Country of ref document: EP

Kind code of ref document: A1