EP4007337A1 - Endgerät und kommunikationsknoten - Google Patents

Endgerät und kommunikationsknoten Download PDF

Info

Publication number
EP4007337A1
EP4007337A1 EP19939423.0A EP19939423A EP4007337A1 EP 4007337 A1 EP4007337 A1 EP 4007337A1 EP 19939423 A EP19939423 A EP 19939423A EP 4007337 A1 EP4007337 A1 EP 4007337A1
Authority
EP
European Patent Office
Prior art keywords
failure
communication
communication node
terminal
information
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.)
Pending
Application number
EP19939423.0A
Other languages
English (en)
French (fr)
Other versions
EP4007337A4 (de
Inventor
Hideaki Takahashi
Tianyang Min
Kenji Kai
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.)
NTT Docomo Inc
Original Assignee
NTT Docomo Inc
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 NTT Docomo Inc filed Critical NTT Docomo Inc
Publication of EP4007337A1 publication Critical patent/EP4007337A1/de
Publication of EP4007337A4 publication Critical patent/EP4007337A4/de
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment

Definitions

  • the present invention relates to terminals and communication nodes that perform a trace for RLF reporting.
  • LTE Long Term Evolution
  • LTE-Advanced LTE-Advanced
  • 5G New Radio
  • NR New Radio
  • NG Next Generation
  • LTE has employed Minimization of Drive Test (MDT) for collecting radio quality and positioning information from terminals as a substitute of driving tests.
  • MDT specifies Trace for RLF reporting, according to which a terminal reports a radio link failure (RLF) when it is detected (see Non-patent document 1) .
  • RLF radio link failure
  • a base station When a base station receives Trace Session Activation in which RLF reporting only is specified in the Job type from a management apparatus (element manager: EM), it starts a trace for the RLF reporting.
  • EM Management apparatus
  • RRC Radio Resource Control
  • the RLF report is transmitted from the terminal to the base station through UE Information Request/Response communicated between the base station and the terminal.
  • the base station stores the RLF report in a trace record and transmits the trace record to a trace collection entity (TCE) .
  • TCE trace collection entity
  • Non-patent document 1 TS32.422 V15.2.0 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Subscriber and equipment trace; Trace control and configuration management (Release 15), 3GPP, 2019-06
  • NR specifies dual connectivity (DC) for a terminal to communicate multiple communication nodes simultaneously.
  • the present invention has been made in light of the above situation, and an objective thereof is to provide a method of performing a trace for RLF reporting that is suitable for the DC configuration with which a terminal communicates with multiple communication nodes simultaneously.
  • a terminal (200) includes: a communication unit (210, 220) that communicates simultaneously with a first communication node (100a) and a second communication node (100b); a detection unit (230) that detects a failure in communication with the second communication node (100b); and a transmitting unit (220) that transmits failure information to the first communication node, the failure information concerning a failure in communication with the second communication node.
  • a communication node (100a) includes: a communication unit (110, 120) that, together with a second communication node (100b), communicates with a terminal (200) ; a control unit (130) that performs a trace to collect failure information from the terminal (200); a receiving unit (110) that receives failure information from the second communication node (100b), the failure information concerning a failure in communication between the terminal (200) and the communication node (100a) itself; and a transmitting unit (120) that transmits the failure information to a trace collection entity (400) when the communication node (100a) is performing a trace.
  • a communication node (100b) includes: a communication unit (110, 120) that, together with a second communication node, communicates with a terminal (200); a receiving unit (110) that receives failure information from the terminal, the failure information concerning a failure in communication between the terminal and the second communication node; and a transmitting unit (120) that transmits the failure information to the second communication node.
  • a radio communication system 10 includes a next generation-radio access network 20 (hereinafter referred to as an NG-RAN 20) and a terminal 200.
  • the terminal is also called user equipment (UE).
  • UE user equipment
  • the NG-RAN 20 includes communication nodes 100a and 100b.
  • the concrete configuration of the radio communication system 10 including the number of the communication nodes and terminals is not limited to the example illustrated in Fig. 1 .
  • the NG-RAN 20 actually includes multiple NG-RAN Nodes, specifically, gNBs (or ng-eNBs), and is connected to a 5G core network (5GC) conforming to NR.
  • Fig. 1 illustrates an EM 300 and a TCE 400 included in the core network. Note that the NG-RAN 20 and 5GC may be simply expressed as a "network".
  • the communication nodes 100a and 100b are gNBs or ng-eNBs.
  • the communication nodes 100a and 100b perform radio communication conforming to NR with the terminal 200.
  • the communication nodes 100a and 100b and the terminal 200 are capable of supporting massive MIMO for generating more directional beams by controlling the radio signals transmitted from multiple antenna elements, carrier aggregation (CA) for using multiple component carriers (CC), dual connectivity (DC) for simultaneous communication between multiple NG-RAN Nodes and a terminal, and the like.
  • CA carrier aggregation
  • CC component carriers
  • DC dual connectivity
  • the radio communication system 10 may include an evolved universal terrestrial radio access network (E-UTRAN) instead of the NG-RAN 20.
  • E-UTRAN includes multiple E-UTRAN Nodes, specifically, eNBs (or en-gNBs), and is connected to a core network (EPC) conforming to LTE.
  • the communication nodes 100a and 100b are eNBs or en-gNBs.
  • serving cells are classified as follows. Note that the serving cell means a cell a radio link between which and a terminal has been established.
  • a group of serving cells associated with a communication node (master node, MN) that provides a control plane connected to the core network is called a master cell group (MCG) .
  • the MCG includes a primary cell (hereinafter, a PCell) and one or more secondary cells (hereinafter, SCells).
  • the PCell is used when a terminal starts an initial connection with the MN.
  • the MCG may be constituted of only a PCell.
  • the PCell is also called a special cell (SpCell) in the MCG.
  • a group of serving cells associated with a communication node (secondary node, SN) that does not provide a control plane connected to the core network but provides additional resources to terminals is called a secondary cell group (SCG).
  • the SCG includes a primary SCell (hereinafter, PSCell) and one or more SCells.
  • PSCell primary SCell
  • the PSCell is used when a terminal starts an initial connection with the SN.
  • the SCG may be constituted of only a PSCell.
  • the PSCell is also called an SpCell in the SCG.
  • the communication node 100a is assumed to be an MN.
  • the communication node 100a forms a PCell.
  • the communication node 100b is assumed to be an SN.
  • the communication node 100b forms a PSCell.
  • the communication node 100a may be an SN, and the communication node 100b may be an MN.
  • the communication nodes 100a and 100b start a trace for RLF reporting based on an instruction from the EM 300. Specifically, when the communication nodes 100a and 100b receive Trace Session Activation indicating RLF reporting only from the EM 300, they start a trace session. In Trace Session Activation, RLF reporting only is written in the Job type. SCG failure and MCG failure may be included under RLF in the Job type. For example, RLF reporting only (RLF, SCG failure, MCG failure) is written in the Job type.
  • the Trace Session Activation may include the IP address of the TCE 400.
  • the terminal 200 When the terminal 200, the connection between which and the communication nodes 100a and 100b is active, detects an abnormality in the MCG or SCG, the terminal 200 transmits information on the detected abnormality to the communication nodes 100a and 100b.
  • the communication nodes 100a and 100b which are performing the trace, store the information received from the terminal 200 in a trace record and transmits the trace record to the TCE 400.
  • the configurations of the communication nodes 100a and 100b and the terminal 200 according to the present embodiment will be described.
  • the following describes only parts related to the features of the present embodiment.
  • the communication nodes 100a and 100b and the terminal 200 naturally include other functional blocks not related to the features of the present embodiment.
  • the configuration of the communication node 100a will be described with reference to Fig. 2 .
  • the communication node 100a and the communication node 100b have the same configuration, and hence, description of the communication node 100b is omitted.
  • the communication node 100a illustrated in Fig. 2 includes a receiving unit 110, a transmitting unit 120, a control unit 130, and a memory unit 140.
  • the receiving unit 110 receives uplink data from the terminal 200.
  • the transmitting unit 120 together with the communication node 100b, transmits downlink data to the terminal 200.
  • the receiving unit 110 and the transmitting unit 120 constitute a communication unit that, together with the communication node 100b, communicates with the terminal 200.
  • the receiving unit 110 receives an instruction to start a trace for RLF reporting, from the EM 300.
  • the receiving unit 110 receives information on a failure detected by the terminal 200.
  • Information on a failure is, for example, an SCG failure or an MCG failure.
  • the receiving unit 110 may receive information on a failure from the terminal 200 and also may receive information on a failure from the other communication node 100b.
  • the transmitting unit 120 transmits a trace record including information on a failure detected by the terminal 200 to the TCE 400.
  • the transmitting unit 120 transmits information on a failure received from the terminal 200 to the other communication node 100b.
  • the control unit 130 starts a trace when the receiving unit 110 receives an instruction to start a trace.
  • the control unit 130 stores information on a failure received by the receiving unit 110 into a trace record.
  • the information on a failure stored in a trace record may be called an RLF report, SCG failure report, or MCG failure report.
  • the control unit 130 makes the transmitting unit 120 transmit the trace record at a specified time.
  • the memory unit 140 stores trace records.
  • the configuration of the terminal 200 will be described with reference to Fig. 3 .
  • the terminal 200 illustrated in Fig. 3 includes a receiving unit 210, a transmitting unit 220, and a detection unit 230.
  • the receiving unit 210 receives downlink data from each of the communication nodes 100a and 100b.
  • the transmitting unit 220 transmits uplink data to each of the communication nodes 100a and 100b.
  • the receiving unit 210 and the transmitting unit 220 constitute a communication unit that communicates each of the communication nodes 100a and 100b simultaneously.
  • the transmitting unit 220 When the detection unit 230 detects a failure, the transmitting unit 220 notifies the communication nodes 100a and 100b of information on the detected failure. At this time, the transmitting unit 220 reports the information on the detected failure to a communication node of the communication nodes 100a and 100b that is not involved in the detected failure. For example, when a failure is detected in communication between the terminal 200 and the communication node 100a, the transmitting unit 220 notifies the communication node 100b that a failure has been detected in communication with the communication node 100a. When a failure is detected in communication between the terminal 200 and the communication node 100b, the transmitting unit 220 notifies the communication node 100a that a failure has been detected in communication with the communication node 100b.
  • the detection unit 230 is configured to detect a failure in communication with each of the communication nodes 100a and 100b. In other words, the detection unit 230 separately detects a failure in each of the MCG and the SCG.
  • the detection unit 230 may judge that an MCG failure has happened when one of the following events happened in the MCG: when a timer T310 that started after a notification of a radio communication problem from the physical layer is over, when a random access procedure failed, or when it was detected that the number of retransmissions exceeded its maximum number in the radio link control (RLC).
  • RLC radio link control
  • the detection unit 230 may judge that an SCG failure has happened when one of the following events happened in the SCG: when the timer T310 that started after a notification of a radio communication problem from the physical layer is over, when a random access procedure failed, when it was detected that the number of retransmissions exceeded its maximum number in the radio link control (RLC), when an SCG reconfiguration with sync failed, when an SCG reconfiguration failed, or when an integrity check failure in SRB3 was notified from an SCG lower layer.
  • RLC radio link control
  • the communication node 100a is referred to as MN, the communication node 100b as SN, and the terminal 200 as UE.
  • MN the communication node 100a
  • SN the communication node 100b
  • UE the terminal 200
  • the following describes four cases: a case where an MCG failure happens when the MN is performing a trace, a case where an MCG failure happens when the SN is performing a trace, a case where an SCG failure happens when the MN is performing a trace, and a case where an SCG failure happens when the SN is performing a trace.
  • the UE are communicating with both the MN and the SN simultaneously.
  • the EM transmits Trace Session Activation to the MN.
  • the MN starts a trace session.
  • the UE the connection between which and the MN and the SN is active, detects an MCG failure.
  • the UE transmits the MCG failure information to the SN.
  • the UE may transmit MCGFailureInformation as illustrated in Fig. 5 to the SN via SRB3.
  • the SRB3 is a bearer for control messages between the terminal 200 and the SN.
  • the UE may include information related to the MCG failure in the MCGFailureInformation. For example, in the case where the timer T310 is over, the UE sets t310-Expiry in the failureType. In the case where the UE has detected a random-access procedure failure in the MAC layer of the MCG, the UE sets randomAccessProblem in the failureType. In the case where the UE has detected that the number of retransmissions exceeded its maximum number in the RLC layer of the MCG, the UE sets rlc-MaxNumRetx in the failureType.
  • the UE may include radio quality for each MeasObject set in the MCG, in the MCGFailureInformation.
  • the MeasObject is information for setting the radio access technology (RAT) and frequency to be measured.
  • RAT radio access technology
  • the UE may include, in the MCGFailureInformation, positional information indicating the position of the UE itself at the time when the UE detected an MCG failure such as the positional information obtained by using a global navigation satellite system (GNSS) or failedPCellID.
  • GNSS global navigation satellite system
  • the UE may include LocationInfo illustrated in Fig. 6 in the MCGFailureInformation.
  • the UE may notify the SN of the positional information on the position of the UE itself at the time when the UE detected an MCG failure, in response to an inquiry from the SN.
  • the UE may perform the process in step S104 before performing an RRC reconnection procedure for connection with the MN or may perform the process in step S104 after completing the RRC reconnection procedure for connection with the MN.
  • the SN notifies the MN of the occurrence of the MCG failure.
  • the SN may transmit a CG-Config message including the MCG failure information to the MN.
  • the MN and the SN are communicably connected with an X2 interface.
  • the MN stores the MCG failure report in a trace record.
  • the MN transmits the trace record to the TCE.
  • the EM transmits Trace Session Activation to the SN.
  • the SN starts a trace session.
  • the UE the connection between which and the MN and the SN is active, detects an MCG failure.
  • the UE transmits the MCG failure information to the SN.
  • the method of notifying the SN of the MCG failure information is the same as or a similar to the process at step S104 in (3-1).
  • the SN stores the MCG failure report in a trace record.
  • the SN transmits the trace record to the TCE.
  • the EM transmits Trace Session Activation to the MN.
  • the MN starts a trace session.
  • the UE the connection between which and the MN and the SN is active, detects an SCG failure.
  • the UE transmits the SCG failure information to the MN.
  • the UE may transmit SCGFailureInformation as illustrated in Fig. 9 to the MN.
  • the UE may include information related to the SCG failure in the SCGFailureInformation. For example, in the case where the timer T310 is over, the UE sets t310-Expiry in the failureType. When SCG reconfiguration with sync failed, the UE sets synchReconfigFailure-SCG in the failureType. In the case where the UE has detected a random-access procedure failure in the MAC layer of the SCG, the UE sets randomAccessProblem in the failureType. In the case where the UE has detected that the number of retransmissions exceeded its maximum number in the RLC layer of the SCG, the UE sets rlc-MaxNumRetx in the failureType.
  • the UE When an integrity check failure concerning SRB3 is reported from an SCG lower layer, the UE sets srb3-IntegratyFailure in the failureType. In the case where SCG reconfiguration failed, the UE sets scg-reconfigFailure in the failureType.
  • the UE may include radio quality for each MeasObject set in the SCG, in the SCGFailureInformation.
  • the UE may include, in the SCGFailureInformation, positional information indicating the position of the UE itself at the time when the UE detected an SCG failure such as the positional information obtained by using a global navigation satellite system (GNSS) or failedPSCellID.
  • GNSS global navigation satellite system
  • the UE may include LocationInfo illustrated in Fig. 6 in the SCGFailureInformation.
  • the UE may notify the MN of the positional information on the position of the UE itself at the time when the UE detected an SCG failure, in response to an inquiry from the MN.
  • the MN stores the SCG failure report in a trace record.
  • the MN transmits the trace record to the TCE.
  • the EM transmits Trace Session Activation to the SN.
  • the SN starts a trace session.
  • the UE the connection between which and the MN and the SN is active, detects an SCG failure.
  • the UE transmits the SCG failure information to the MN.
  • the method of notifying the MN of the SCG failure information is the same as or a similar to the case where the MN performs a trace.
  • the MN notifies the SN of the SCG failure.
  • the MN may transmit a CG-ConfigInfo message including the SCG failure information to the SN.
  • the SN stores the SCG failure report in a trace record.
  • the SN transmits the trace record to the TCE.
  • the terminal 200 in the foregoing embodiment which communicates with both the MN and the SN simultaneously, detects a failure in the MCG or the SCG.
  • the terminal 200 detects an MCG failure, it transmits the MCG failure information to the SN, and when the terminal 200 detected an SCG failure, it transmits the SCG failure information to the MN.
  • the foregoing embodiment can provide a method of performing a trace for RLF reporting, suitable for a DC configuration.
  • the communication nodes 100a and 100b receive MCG failure information or SCG failure information from the terminal 200, if the MN is performing a trace, the SN transmits the MCG failure information to the MN, and if the SN is performing a trace, the MN transmits the SCG failure information to the SN.
  • the MCG failure information and the SCG failure information is transmitted to the MN or SN that is performing a trace, the terminal 200 only needs to report that a failure has happened, to the MN or SN that is not involved in the failure.
  • the core network can obtain the positional information at the time of the occurrence of the MCG failure or the SCG failure, and thus, the core network can geographically identify the area having a problem in area quality.
  • each functional block may be implemented by using one apparatus into which the constituents are physically or logically combined or by using two or more apparatuses that are physically or logically separated but directly or indirectly connected to one another (for example, using wires, radio communication, or the like).
  • the functional blocks may be implemented by using a combination of the above one or multiple apparatuses and software.
  • the functions include judging, deciding, determining, calculating, computing, processing, deriving, investigating, searching, checking, receiving, transmitting, outputting, accessing, resolving, choosing, selecting, establishing, comparing, supposing, expecting, assuming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating or mapping, and assigning, but the functions are not limited to theses.
  • a functional block (component) that has a function of transmission is called a transmitting unit or a transmitter. In either case, the implementation method is not limited to any specific ones, as mentioned above.
  • Fig. 11 is a diagram illustrating an example of the hardware configuration of the communication node and the terminal.
  • the communication node and the terminal may be configured as a computer apparatus including a processor 1001, memory 1002, storage 1003, communication apparatus 1004, input apparatus 1005, output apparatus 1006, bus 1007, and others.
  • apparatus may be interpreted as a circuit, device, unit, or the like.
  • the hardware configuration of the apparatus may include one or more apparatuses illustrated in the figure or may be a configuration without some of the apparatuses.
  • Each functional block of the apparatus is implemented by using a hardware component of the computer apparatus or a combination of some of the hardware components.
  • Each function of the apparatus is implemented by loading specified software (program) into hardware such as the processor 1001 or the memory 1002.
  • the processor 1001 performs computing according to the software to control the communication performed by the communication apparatus 1004 and control either reading or writing or both reading and writing of data in the memory 1002 and storage 1003.
  • the processor 1001 for example, runs an operating system to control the entire computer.
  • the processor 1001 may be constituted of a central processing unit (CPU) including an interface with peripheral apparatuses, a control apparatus, a computation apparatus, and a register.
  • CPU central processing unit
  • the processor 1001 loads a program (program codes), software modules, data, and the like from at least one of the storage 1003 and the communication apparatus 1004 into the memory 1002, and performs various processes according to these.
  • the program used here is a program that causes a computer to perform at least part of the operation described in the foregoing embodiment.
  • the foregoing various processes may be performed by one processor 1001 or may be performed by two or more processors 1001 simultaneously or sequentially.
  • the processor 1001 may be constituted of one or more chips. Note that the program may be transmitted from a network via an electrical communication line.
  • the memory 1002 is a computer readable recording medium and may be constituted of, for example, at least one of media including read only memory (ROM), erasable programmable ROM (EPROM) electrically erasable programmable ROM (EEPROM), and random access memory (RAM).
  • the memory 1002 may be called a register, a cache, main memory (a main storage apparatus) , or the like.
  • the memory 1002 can store a program (program codes), software modules, or the like with which the method according to an embodiment of the present disclosure can be performed.
  • the storage 1003 is a computer readable recording medium and may be constituted of, for example, at least one of media including an optical disk such as Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (for example, a Compact Disc, a Digital Versatile Disc, a Blu-Ray (registered trademark) Disc), a smart card, flash memory (for example, a card, a stick, or a key drive), a floppy (registered trademark) disk, and a magnetic strip.
  • the storage 1003 may be called an auxiliary storage apparatus.
  • the foregoing recording medium may be, for example, a database, a server, or other suitable media including at least one of the memory 1002 and the storage 1003.
  • the communication apparatus 1004 is hardware (a transmission/reception device) for performing communication between computers via at least one of a wired network and a radio network.
  • the communication apparatus 1004 is called, for example, a network device, network controller, network card, communication module, or the like.
  • the communication apparatus 1004 may include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, and the like to implement at least one of techniques: frequency division duplex (FDD) and time division duplex (TDD).
  • FDD frequency division duplex
  • TDD time division duplex
  • the input apparatus 1005 is an input device for receiving input from the outside (for example, a keyboard, mouth, microphone, switch, button, sensor, and the like).
  • the output apparatus 1006 is an output device for performing output to the outside (for example, a display, speaker, LED lamp, or the like). Note that the input apparatus 1005 and the output apparatus 1006 may be integrally formed as one unitary structure (for example, a touch panel).
  • the apparatuses such as the processor 1001, the memory 1002, and others are connected to one another via the bus 1007 for communicating information.
  • the bus 1007 may be constituted of one type of bus or may be constituted to have a different bus for each apparatus.
  • the apparatus may include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), and the like, and some or all of the functional blocks may be implemented by the hardware.
  • the processor 1001 may be implemented, for example, by using at least one of these pieces of hardware.
  • Notification of information is not limited to an aspect/embodiment described in the present disclosure, but other methods may be used for it.
  • notification of information may be performed by physical layer signaling (for example, downlink control information (DCI), uplink control information (UCI)), upper layer signaling (for example, radio resource control (RRC) signaling, medium access control (MAC) signaling, broadcasting information (a master information block (MIB), a system information block (SIB)), or other signaling, or using a combination of these.
  • RRC signaling may be called an RRC message and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.
  • Each aspect/embodiment described in the present disclosure may be applied to at least one of a system using LTE, LTE-A, SUPER 3G, IMT-Advanced, the 4th generation mobile communication system (4G), 5G future radio access (FRA), NR, W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, ultra-wideband (UWB), Bluetooth (registered trademark), or another suitable system ; and a next generation system extended based on these systems.
  • Each aspect/embodiment may be applied to a combination of multiple systems (for example, a combination of 5G and at least one of LTE and LTE-A, or the like).
  • Certain operations that have been assumed to be performed by a base station in the present disclosure are performed by the upper node in some cases. It is apparent that various operations performed, to communicate with terminals, in a network constituted of one or more network nodes having a base station can be performed by at least one of the base station and other network nodes other than the base station (for example, MME, S-GW, and the like are conceivable, but the present disclosure is not limited to these) . Although the above description is for an example in which the number of network nodes other than the base station is one, multiple other network nodes may be combined (for example, MME and S-GW).
  • Information and signals can be outputted from an upper layer (or a lower layer) to a lower layer (or an upper layer).
  • Information and the like may be inputted and outputted via multiple network nodes.
  • Inputted or outputted information and the like may be stored in a specific location (for example, memory) or may be managed by using a management table. Information and the like that are inputted and outputted may be overwritten or updated, or other information may be added to it. Outputted information and the like may be deleted. Inputted information and the like may be transmitted to other apparatuses.
  • Determination may be performed by using a value expressed in one bit (0 or 1), by using a Boolean value (true or false), or by comparison of numerical values (for example, comparison with a specified value).
  • notification of specified information is not limited to that performed explicitly but may be performed implicitly (for example, by not performing notification of the specified information).
  • software whether it is called software, firmware, middleware, microcode, a hardware description language, or other names, means instructions, instruction sets, codes, code segments, program codes, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, or functions.
  • Software, instructions, information, and the like may be communicated via a transmission medium.
  • a transmission medium For example, in the case where software is transmitted from a website, a server, or other remote sources through at least one of a wired technology (coaxial cable, optical fiber cable, twisted pair cable, digital subscriber line (DSL), or the like) and a wireless technology (infrared rays, microwaves, or the like), the at least one of these wired technology and wireless technology is included within the definition of a transmission medium.
  • a wired technology coaxial cable, optical fiber cable, twisted pair cable, digital subscriber line (DSL), or the like
  • DSL digital subscriber line
  • the at least one of these wired technology and wireless technology is included within the definition of a transmission medium.
  • Information, signals, or the like described in the present disclosure may be expressed by using one of various different technologies.
  • data, instructions, commands, information, signals, bits, symbols, chips, and the like that can be referred to in the above entire description may be expressed by using voltage, electric current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or combinations of any of these.
  • channel and symbol may be signal (signaling) .
  • a signal may be a message.
  • a component carrier may be called a carrier frequency, cell, frequency carrier, or the like.
  • system and “network” used in the present disclosure are used interchangeably.
  • a radio resource may be indicated by an index.
  • base station BS
  • radio base station fixed station
  • NodeB NodeB
  • eNodeB eNodeB
  • gNodeB gNodeB
  • a base station may also be called a macro cell, small cell, femto-cell, pico-cell, or the like.
  • a base station can accommodate one or more (for example, three) cells.
  • the overall coverage area of the base station can be divided into multiple smaller areas, and a communication service for each smaller area may be provided by a base station subsystem (for example, a small indoor base station (remote radio head: RRH).
  • a base station subsystem for example, a small indoor base station (remote radio head: RRH).
  • cell refers to part or all of the coverage area of at least one of a base station and a base station subsystem that provides a communication service in this coverage.
  • a mobile station may be called, by those skilled in the art, a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terms.
  • At least one of a base station and a mobile station may be called a transmission apparatus, reception apparatus, communication apparatus, or the like.
  • a base station and a mobile station may be a device mounted on a mobile object, a mobile object itself, or the like.
  • the mobile object may be transportation (for example, a car, an airplane, or the like), an uncrewed mobile object (for example, a drone, an automated driving vehicle, or the like), or a robot (crewed or uncrewed) .
  • at least one of a base station and a mobile station includes an apparatus that does not necessarily move while performing communication.
  • at least one of a base station and a mobile station may be an Internet of things (IoT) unit such as a sensor.
  • IoT Internet of things
  • a communication node in the present disclosure may be interpreted as a terminal.
  • Each aspect/embodiment in the present disclosure may be applied to, for example, a configuration in which communication between a communication node and a terminal is replaced with communication between multiple terminals (which may be called, for example, device-to-device (D2D), vehicle-to-everything (V2X), or the like).
  • a terminal may have functions that a foregoing communication node has.
  • Wording such as "uplink” and "downlink” may be interpreted as wording corresponding to communication between terminals (for example, "side”).
  • an uplink channel, a downlink channel, and the like may be interpreted as a side channel.
  • a terminal in the present disclosure may be interpreted as a communication node.
  • a communication node may have functions that the foregoing terminal has.
  • connection means various types of direct or indirect connection or combination between two or more elements and hence include cases in which one or more intermediate elements are present between two elements connected or combined to each other.
  • Combination or connection between elements may be a physical one, a logical one, or a combination of these.
  • connection may be interpreted as "access”.
  • connection such as one or more electric wires, cables, and printed electrical connections or by using, as some non-limiting and non-exhaustive examples, electromagnetic energy having wavelengths in a radio frequency region, a microwave region, or an optical (both visible and invisible) region, or the like.
  • any reference to elements using designations such as “first”, “second”, and the like in the present disclosure does not generally limit the quantity or order of those elements. These designations can be used in the present disclosure as a convenient method for distinguishing between two or more elements. Hence, reference to the first and the second elements does not mean that only two elements can be employed or that the first element has to precede the second element in a respect.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
EP19939423.0A 2019-07-31 2019-07-31 Endgerät und kommunikationsknoten Pending EP4007337A4 (de)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2019/030074 WO2021019742A1 (ja) 2019-07-31 2019-07-31 端末および通信ノード

Publications (2)

Publication Number Publication Date
EP4007337A1 true EP4007337A1 (de) 2022-06-01
EP4007337A4 EP4007337A4 (de) 2023-03-22

Family

ID=74229468

Family Applications (1)

Application Number Title Priority Date Filing Date
EP19939423.0A Pending EP4007337A4 (de) 2019-07-31 2019-07-31 Endgerät und kommunikationsknoten

Country Status (4)

Country Link
US (1) US20220272554A1 (de)
EP (1) EP4007337A4 (de)
CN (1) CN114175709A (de)
WO (1) WO2021019742A1 (de)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220141907A1 (en) * 2020-11-03 2022-05-05 At&T Intellectual Property I, L.P. Endpoint device radio link failure information reporting

Family Cites Families (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7715837B2 (en) * 2000-02-18 2010-05-11 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for releasing connections in an access network
US9271204B2 (en) * 2008-11-17 2016-02-23 Qualcomm Incorporated Mobility management based on radio link failure reporting
CN109905893A (zh) * 2012-01-19 2019-06-18 日本电气株式会社 无线通信系统、无线站、无线终端、无线通信方法、以及程序
KR102036061B1 (ko) * 2013-04-08 2019-11-26 삼성전자 주식회사 무선 통신 시스템에서 단말기가 mbms 관련 측정 정보를 기록하고 보고하는 방법 및 장치
CN106332114A (zh) * 2015-06-19 2017-01-11 北京信威通信技术股份有限公司 一种网络移动性优化的方法
WO2018027018A1 (en) * 2016-08-03 2018-02-08 Intel Corporation Remote debugging and management
EP3566539B1 (de) * 2017-01-06 2021-03-17 Telefonaktiebolaget LM Ericsson (PUBL) Funknetzwerkknoten, drahtlose vorrichtung und darin ausgeführte verfahren zur handhabung von verbindungen in einem drahtloskommunikationsnetzwerk
WO2018203108A1 (en) * 2017-05-04 2018-11-08 Telefonaktiebolaget Lm Ericsson (Publ) Efficient troubleshooting in openflow switches
EP4236590A3 (de) * 2017-05-04 2023-10-18 Samsung Electronics Co., Ltd. Verfahren zur meldung des ausfalls eines sekundären knoten in netzwerken mit dualer konnektivität, benutzergerät und basisstation
WO2018228560A1 (en) * 2017-06-16 2018-12-20 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for measurement report
EP3701687A4 (de) * 2017-10-27 2021-02-17 Telefonaktiebolaget LM Ericsson (publ) Optimierte datenpfadfehlerbehebung mit verfolgungsrichtlinienmotor
WO2019099550A1 (en) * 2017-11-14 2019-05-23 Idac Holdings, Inc. Operating dual connectivity in an inactive state
WO2019097476A1 (en) * 2017-11-17 2019-05-23 Telefonaktiebolaget Lm Ericsson (Publ) Management of resource allocation and notification control over ran interfaces
CN109818770B (zh) * 2017-11-22 2020-11-13 维沃移动通信有限公司 一种最小化路测异常配置处理方法和装置
JP7145611B2 (ja) * 2017-12-28 2022-10-03 シャープ株式会社 端末装置、方法、および、集積回路
US11895695B2 (en) * 2018-02-15 2024-02-06 Qualcomm Incorporated System and method for beam failure recovery request by user equipment
EP3738338A4 (de) * 2018-04-02 2021-03-10 LG Electronics Inc. Verfahren zur erstellung eines eintrags einer protokollierten messung und vorrichtung zur unterstützung davon
WO2019193553A1 (en) * 2018-04-06 2019-10-10 Telefonaktiebolaget Lm Ericsson (Publ) Qos flow management over e1
WO2019211860A1 (en) * 2018-05-02 2019-11-07 Telefonaktiebolaget Lm Ericsson (Publ) First network node, second network node, and methods performed thereby for tracing a packet in a pipeline
KR20190131411A (ko) * 2018-05-16 2019-11-26 삼성전자주식회사 차세대 이동통신 시스템에서 셀 측정 정보를 수집 및 보고하는 방법 및 장치
EP3797544A1 (de) * 2018-05-21 2021-03-31 Telefonaktiebolaget LM Ericsson (publ) Messkonfiguration für nichtlizenzierte operationen
US11729782B2 (en) * 2018-06-11 2023-08-15 Apple Inc. Enhanced uplink beam management
US11956822B2 (en) * 2018-06-19 2024-04-09 Interdigital Patent Holdings, Inc. Radio link monitoring in shared spectrum
US11503516B2 (en) * 2018-06-22 2022-11-15 Lg Electronics Inc. Method and apparatus for providing beam related information for connection failure detection in wireless communication system
CN110708766B (zh) * 2018-07-10 2023-11-28 夏普株式会社 用户设备的控制方法以及用户设备
US11770870B2 (en) * 2018-07-18 2023-09-26 Qualcomm Incorporated Methods and apparatus related to beam recovery in the secondary cell
CN113016233B (zh) * 2018-11-14 2024-02-06 上海诺基亚贝尔股份有限公司 跟踪管理
US11882202B2 (en) * 2018-11-16 2024-01-23 Cisco Technology, Inc. Intent based network data path tracing and instant diagnostics
US11979754B2 (en) * 2018-12-22 2024-05-07 Nokia Solutions And Networks Oy Connection behavior identification for wireless networks
SG11202107924UA (en) * 2019-01-25 2021-08-30 Zte Corp Method and apparatus for reporting master cell group failure
WO2020164714A1 (en) * 2019-02-14 2020-08-20 Nokia Technologies Oy Control mechanism for supporting connection establishment procedure
MX2021014442A (es) * 2019-06-07 2021-12-15 Ntt Docomo Inc Terminal y estacion de base.
WO2021180156A1 (en) * 2020-03-12 2021-09-16 Shanghai Langbo Communication Technology Company Limited Methods and devices for mobility enhancement and optimisation in wireless communication
CN116233894A (zh) * 2020-03-26 2023-06-06 上海朗帛通信技术有限公司 一种被用于无线通信的通信节点中的方法和装置
EP4124159A4 (de) * 2020-04-22 2023-09-27 Shanghai Langbo Communication Technology Company Limited Verfahren und vorrichtung zur verwendung in einem kommunikationsknoten zur drahtlosen kommunikation
US11825542B2 (en) * 2020-08-13 2023-11-21 Shanghai Langbo Communication Technology Company Limited Method and device used in communication node for wireless communication
WO2024033820A1 (en) * 2022-08-08 2024-02-15 Telefonaktiebolaget Lm Ericsson (Publ) Radio link failure signaling to a secondary node

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220141907A1 (en) * 2020-11-03 2022-05-05 At&T Intellectual Property I, L.P. Endpoint device radio link failure information reporting
US11672042B2 (en) * 2020-11-03 2023-06-06 At&T Intellectual Property I, L.P. Endpoint device radio link failure information reporting

Also Published As

Publication number Publication date
EP4007337A4 (de) 2023-03-22
US20220272554A1 (en) 2022-08-25
JPWO2021019742A1 (de) 2021-02-04
WO2021019742A1 (ja) 2021-02-04
CN114175709A (zh) 2022-03-11

Similar Documents

Publication Publication Date Title
US11330496B2 (en) User equipment and base station apparatus
US10999827B2 (en) User equipment
US11477729B2 (en) Cell selection or access method, a user terminal, a maintenance method, and a base station
US11770697B2 (en) Terminal, transmission method, and radio communication system
EP3989632A1 (de) Endgerät
EP3836739A1 (de) Drahtloses zugangssystem und kommunikationsvorrichtung
US20230299839A1 (en) Terminal and radio communication method
CN115989693A (zh) 终端及无线通信系统
EP4007337A1 (de) Endgerät und kommunikationsknoten
EP3927048A1 (de) Benutzervorrichtung und basisstationsvorrichtung
JP2023052488A (ja) ユーザ装置
EP4007338A1 (de) Endgerät und kommunikationsknoten
WO2023077322A1 (en) Determination of concurrent beam failure
WO2022205282A1 (en) Methods, devices and computer storage media for communication
JP7312240B2 (ja) ユーザ装置
US20240031884A1 (en) Terminal and radio communication system
WO2019180849A1 (ja) 基地局
WO2020255420A1 (ja) 端末
WO2020084745A1 (ja) ユーザ装置

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20220126

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Free format text: PREVIOUS MAIN CLASS: H04W0016180000

Ipc: H04W0024080000

A4 Supplementary search report drawn up and despatched

Effective date: 20230217

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 76/15 20180101ALN20230213BHEP

Ipc: H04W 76/19 20180101ALI20230213BHEP

Ipc: H04W 24/08 20090101AFI20230213BHEP

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230509