Technology in secondary cell group fault measurement report
By including SCS information of the reference signal in the SCG fault report, the problem that the fault measurement report in 5G NR communication cannot identify the fault cell or beam is solved, which improves the utilization efficiency of network resources and the accuracy of access configuration.
Patent Information
- Application Number
- CN201980062349.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2018-09-26
- Filing Date
- 2019-09-24
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2039-09-24
AI Technical Summary
In 5G NR communication, existing fault measurement reports cannot provide sufficient information to identify fault measurement objects in frequency and subcarrier interval (SCS), making it difficult for the network to identify faulty cells or beams, affecting the access configuration of the UE.
By including SCS information of the reference signal in the SCG fault report, the access node (AN) can identify the reference signal at the fault cell or beam level, determine the corresponding operation, reduce ambiguity and utilize network resources more efficiently.
The ability to identify faulty cells or beams in a 5G NR network is realized, access configuration errors caused by ambiguity are avoided, and network resource utilization efficiency is improved.
Smart Images

Figure CN112753241B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This patent application claims priority to U.S. Provisional Patent Application No. 62 / 736,926, filed on September 26, 2018, entitled “Encoding of Secondary Cell Group Failure Measurement Report,” the disclosure of which is incorporated herein by reference in its entirety. Technical Field
[0003] Embodiments of the present invention generally relate to the field of wireless communication technology. Background Art
[0004] The background description generally presents the context of the present disclosure. The work of the inventors disclosed herein, to the extent described in this background section, and in all aspects of the description that may not qualify as prior art at the time of filing, is not explicitly or implicitly admitted as prior art to the present disclosure. Unless otherwise indicated herein, the methods described in this section are not prior art to the claims of the present disclosure and are not admitted as prior art by inclusion in this section.
[0005] Various communications and / or networks involving fifth generation (5G) new radio (NR) have been developed over a wide frequency range, such as sub-6 GHz and millimeter wave (mmWave). Therefore, more than one subcarrier spacing (SCS) is used in communications involving NR. Existing measurement reports from user equipment (UE), especially faulty measurement reports, may not provide sufficient information to identify a faulty measurement object (MO) in terms of frequency, SCS, etc. Therefore, the network may not be able to identify the MO based on the existing faulty measurement reports. In this regard, a new solution is needed. BRIEF DESCRIPTION OF THE DRAWINGS
[0006] The embodiment will be more easily understood by the following specific implementation in conjunction with the accompanying drawings. In order to facilitate this description, similar reference numerals represent similar structural elements. In each figure of the accompanying drawings, the embodiment is shown by way of example and not limitation.
[0007] Figure 1 An example of a network including a user equipment (UE) and an access node (AN) in a wireless network according to various embodiments is schematically illustrated.
[0008] Figure 2 Example components of an apparatus according to various embodiments are shown.
[0009] Figure 3AAn exemplary radio frequency front end (RFFE) combining a millimeter wave (mmWave) RFFE and one or more sub-millimeter wave radio frequency integrated circuits (RFICs) according to some embodiments is shown. Figure 3B Alternative RFFEs according to various embodiments are shown.
[0010] Figure 4 An exemplary network involving 5G NR communications according to various embodiments is shown.
[0011] Figure 5A An operational flow / algorithm structure for facilitating a process for reporting a Secondary Cell Group (SCG) failure relative to reference signal measurements by a UE in a network involving NR according to various embodiments is shown. Figure 5B An operational flow / algorithm structure for facilitating a process for reporting SCG failures relative to reference signal measurements by the AN 110 in a network involving NRs according to various embodiments is shown.
[0012] Figure 6 An exemplary interface of a baseband circuit according to some embodiments is shown.
[0013] Figure 7 Hardware resources according to some embodiments are shown. DETAILED DESCRIPTION
[0014] In the following specific embodiments, reference is made to the accompanying drawings forming a part of the present invention, wherein like numbers represent like parts throughout the accompanying drawings, and wherein practicable embodiments are shown by way of example. It should be understood that other embodiments may be used and structural or logical changes may be made without departing from the scope of the present disclosure. Therefore, the following specific embodiments will not have a limiting meaning.
[0015] Various operations can be described in sequence as multiple discrete actions or operations in a manner that is most helpful for understanding the claimed subject matter. However, the order of description should not be understood to imply that these operations must rely on the order. Specifically, these operations cannot be performed in the order presented. The operations can be performed in a different order from the described embodiment. In additional embodiments, various additional operations can be performed and / or the described operations can be omitted.
[0016] For purposes of this disclosure, the phrases "A or B" and "A and / or B" mean (A), (B), or (A and B). For purposes of this disclosure, the phrases "A, B or C" and "A, B and / or C" mean (A), (B), (C), (A and B), (A and C), (B and C), or (A, B and C).
[0017] The description may use the phrases "in one embodiment" or "in multiple embodiments," which may each refer to one or more of the same or different embodiments. In addition, the terms "comprising," "including," "having," etc. used with the embodiments of the present disclosure are synonymous.
[0018] As used herein, the term "circuit" may refer to an integrated circuit (e.g., a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), etc.), a discrete circuit, a combinational logic circuit, a system on a chip (SOC), a portion of a packaged system (SiP), or any combination thereof that provides the described functionality. In some embodiments, the circuit may execute one or more software or firmware modules to provide the described functionality. In some embodiments, the circuit may include a logic component that is capable of operating at least partially in hardware.
[0019] Various frequency bands below 6 GHz exist in 4G LTE networks. In NR, Frequency Range 1 (FR1) overlaps and extends 4G LTE frequencies, including various bands from 450 MHz to 6,000 MHz, which are often referred to as NR sub-6 GHz. NR also includes Frequency Range 2 (FR2) covering from 24,250 MHz to 52,600 MHz, which is often referred to as millimeter wave, even though strictly speaking millimeter wave frequencies may start at 30 GHz. In this article, FR1 / FR2 and sub-6 GHz (below 6 GHz) / mmWave pairs are used interchangeably.
[0020] Multi-Radio Access Technology (RAT) Dual Connectivity (MR-DC) may involve multiple receive (Rx) / transmit (Tx) UEs that may be configured to utilize radio resources provided by two different schedulers in two different nodes connected via a non-ideal backhaul, one scheduler providing Evolved Universal Terrestrial Radio Access (E-UTRA) access and the other scheduler providing NR access. One scheduler is located in a master node (MN) and the other scheduler is located in a secondary node (SN). The MN and SN are connected via a network interface, and at least the MN is connected to a core network.
[0021] MR-DC may include, but is not limited to, E-UTRA-NR dual connectivity (EN-DC), NG-RAN-E-UTRA-NR dual connectivity (NGEN-DC), and NR-E-UTRA dual connectivity (NE-DC). In an EN-DC network or communication, a UE may be connected to an evolved Node B (eNB) or ng-eNB acting as a MN and a next generation Node B (gNB) acting as a SN. The ng-eNB may be an enhanced eNodeB that is connected to the 5G core network via a next generation (NG) interface, but still uses the LTE air interface to communicate with the 5G UE. Therefore, both the basic gNB and the ng-eNB use the new NG interface for the 5G core, but use different radio interfaces for the UE. Note that in some embodiments herein, "eNB" may be used to indicate an eNB and / or ng-eNB. The eNB or ng-eNB is connected to the evolved packet core (EPC), and the gNB is connected to the eNB. The gNB may be a node that provides the UE with new radio (NR) user plane and control plane protocol terminations and acts as a SN in EN-DC. In contrast, in an EN-DC network or communication, the UE may be connected to one gNB acting as a MN and one eNB or ng-eNB acting as a SN. The gNB is connected to the 5G Core (5GC), and the eNB or ng-eNB is connected to the gNB via an Xn interface. In some embodiments, an NR standalone (SA) network may include NR-NR dual connectivity, where the gNB is connected to the 5GC, and the eNB (or other LTE node) is not involved in NR-NRDC communications.
[0022] In EN-DC, NR-NRDC and / or similar networks involving MN and SN, the UE may perform cell and / or beam measurements relative to one or more cells of the SCG. If the UE determines one or more measurement failures based on specific criteria, the UE may provide an SCG failure report to the MN. Existing SCG failure reports may not include SCS information for reference signals measured by the UE. However, due to the NR parameter set, there are several available SCSs. Therefore, the reference signal measurement may fail in one or more specific SCSs of reference signals with a specific frequency, but not in all of these cases. Without identifying the SCS, it may cause ambiguity to the MN, so that the MN may not be able to determine or derive sufficient information about the failed cell-level and / or beam-level reference signal measurements based on the existing SCG failure report. This may adversely affect the network's configuration of the UE to not access via those cells or beams, or to avoid access via those cells or beams. This may also adversely affect the network's configuration of the UE to access via those cells or beams with respect to the best cell-level and / or beam-level reference signal measurements. More details will be referred to below. Figure 4 discuss.
[0023] The embodiments described herein may include, for example, an apparatus, method, and storage medium for generating an SCG fault report having sufficient information of reference signals in a network involving NR, so that the MN or SN can identify the faulty cell / beam level reference signal and determine the corresponding operation to or for the SCG. It should be noted that the MN or SN can identify the best cell / beam level reference signal instead of the faulty cell / beam level reference signal, so that the MN or SN can determine the corresponding operation accordingly. The reference signal measurements herein may include, but are not limited to, cell-level and beam-level measurements relative to a cell. This implementation can reduce or avoid ambiguity in identifying one or more faulty reference signal measurements of the MN and / or the network, so that network resources can be utilized more efficiently.
[0024] Figure 1 An exemplary wireless network 100 (hereinafter referred to as "network 100") according to various embodiments of the present invention is schematically illustrated. Network 100 may include UE 105 in wireless communication with AN 110. In some embodiments, network 100 may be an NR SA network. UE 105 may be configured to connect to AN 110, for example, to be communicatively coupled. In this example, connection 112 is shown as an air interface to achieve communicatively coupling, and may be consistent with a cellular communication protocol, such as a 5GNR protocol operating at millimeter wave and sub-6GHz, a global system for mobile communications (GSM) protocol, a code division multiple access (CDMA) network protocol, a push-to-talk (PTT) protocol, etc.
[0025] UE 105 is shown as a smart phone (e.g., a handheld touch screen mobile computing device that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a personal data assistant (PDA), a pager, a laptop computer, a desktop computer, a wireless handheld terminal, a customer premises equipment (CPE), a fixed wireless access (FWA) device, a vehicle-mounted UE, or any computing device that includes a wireless communication interface. In some embodiments, UE 105 may include an Internet of Things (IoT) UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may exchange data with an MTC server or device via a public land mobile network (PLMN), proximity-based services (ProSe) or device-to-device (D2D) communications, a sensor network, or an IoT network using technologies such as narrowband IoT (NB-IoT), machine-to-machine (M2M), or machine type communications (MTC). The M2M or MTC data exchange may be a machine-initiated data exchange. The NB-IoT / MTC network describes interconnected NB-IoT / MTC UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with ephemeral connections. NB-IoT / MTC UEs may execute background applications (e.g., keep-alive messages, status updates, location-related services, etc.).
[0026] AN 110 may initiate or terminate connection 112. AN 110 may be referred to as a base station (BS), NodeB, evolved NodeB (eNB), next generation NodeB (gNB or ng-gNB), NG-RAN node, cell, serving cell, neighbor cell, etc., and may include a ground station (e.g., a terrestrial access point) or a satellite station that provides coverage in a geographic area.
[0027] AN 110 may be the first point of contact for UE 105. In some embodiments, AN 110 may fulfill various logical functions including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management, data packet scheduling, and mobility management.
[0028] In some embodiments, a downlink resource grid may be used for downlink transmissions from AN 110 to UE 105, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, which is a physical resource in the downlink in each time slot. For orthogonal frequency division multiplexing (OFDM) systems, such a time-frequency plane representation is a common practice, which makes wireless resource allocation intuitive. Each column and each row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes a plurality of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a set of resource elements; in the frequency domain, this may represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit several different physical downlink channels.
[0029] The physical downlink shared channel (PDSCH) may carry user data and higher layer signaling to the UE 105. The physical downlink control channel (PDCCH) may carry information about the transport format and resource allocation related to the PDSCH channel, among other things. It may also inform the UE 105 about the transport format, resource allocation, and hybrid automatic repeat request (HARQ) information related to the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to the UE 105 within the cell) may be performed at the AN 110 based on channel quality information fed back from any of the UEs 105. Downlink resource allocation information may be sent on the PDCCH for (e.g., allocated to) the UE 105.
[0030] PDCCH can use control channel elements (CCE) to transmit control information. Before being mapped to resource elements, PDCCH complex-valued symbols can first be organized into four tuples, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to four sets of nine physical resource elements, called resource element groups (REGs). Four orthogonal phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the downlink control information (DCI) and channel conditions, one or more CCEs can be used to transmit the PDCCH.
[0031] Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some embodiments may utilize an enhanced physical downlink control channel (ePDCCH) that uses PDSCH resources for control information transmission. One or more enhanced control channel elements (ECCEs) may be used to transmit ePDCCH. Similar to the above, each ECCE may correspond to four sets of nine physical resource elements, referred to as enhanced resource element groups (EREGs). In some cases, ECCEs may have other numbers of EREGs.
[0032] like Figure 1 As shown, UE 105 may include millimeter wave communication circuits grouped according to functions. The circuits shown here are for illustrative purposes, and UE 105 may include other circuits shown in Figure 3. UE 105 may include protocol processing circuits 115, which may implement one or more layer operations related to medium access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), radio resource control (RRC), and non-access stratum (NAS).
[0033] The protocol processing circuitry 115 may include one or more processing cores (not shown) for executing instructions and one or more memory structures (not shown) for storing program and data information.
[0034] The UE 105 may also include digital baseband circuitry 125, which may implement physical layer (PHY) functions, including one or more of the following: HARQ functions, scrambling and / or descrambling, encoding and / or decoding, layer mapping and / or demapping, modulation symbol mapping, received symbol and / or bit metric determination, multi-antenna port precoding and / or decoding, which may include space-time, space-frequency or space coding, reference signal generation and / or detection, preamble sequence generation and / or decoding, synchronization sequence generation and / or detection, control channel signal blind decoding, and one or more of other related functions.
[0035] UE 105 may also include transmit circuitry 135 , receive circuitry 145 , radio frequency (RF) circuitry 155 , and an RF front end (RFFE) 165 , which may include or be connected to one or more antenna panels 175 .
[0036] In some embodiments, the RF circuit 155 may include multiple parallel RF chains or branches for one or more of transmit or receive functions; each chain or branch may be coupled to an antenna panel 175 .
[0037] In some embodiments, the protocol processing circuit 115 may include one or more instances of control circuits (not shown) to provide control functions for the digital baseband circuit 125 (or simply referred to as "baseband circuit 125"), the transmit circuit 135, the receive circuit 145, the RF circuit 155, the RFFE 165, and one or more antenna panels 175.
[0038] UE reception may be established by and via one or more antenna panels 175, RFFE 165, RF circuitry 155, receive circuitry 145, digital baseband circuitry 125, and protocol processing circuitry 115. One or more antenna panels 175 may receive transmissions from AN 110 via receive beamforming signals received by multiple antennas / antenna elements of one or more antenna panels 175. More details on the UE 105 architecture are provided in Figure 2 , Figure 3 and Figure 6 . The transmission from AN 110 may be transmit beamformed by the antenna of AN 110. In some embodiments, baseband circuit 125 may include both transmit circuit 135 and receive circuit 145. In other embodiments, baseband circuit 125 may be implemented in separate chips (e.g., one chip including transmit circuit 135 and another chip including receive circuit 145) or modules.
[0039] Similar to UE 105, AN 110 may include millimeter wave / sub-millimeter wave communication circuits grouped according to functions. AN 110 may include protocol processing circuits 120, digital baseband circuits 130 (or simply referred to as "baseband circuits 130"), transmission circuits 140, reception circuits 150, RF circuits 160, RFFE 170, and one or more antenna panels 180.
[0040] Cell transmission can be established by and via the protocol processing circuit 120, the digital baseband circuit 130, the transmission circuit 140, the RF circuit 160, the RFFE 170, and one or more antenna panels 180. The one or more antenna panels 180 can transmit signals by forming a transmit beam. FIG. 3 also shows details about the RFFE 170 and the antenna panel 180.
[0041] Figure 2 2 shows example components of an apparatus 200 according to some embodiments. Figure 1 compared to, Figure 2 Exemplary components of UE 105 or AN 110 are shown from the perspective of receiving and / or transmitting functions, and may not include Figure 1All components described in . In some embodiments, at least as shown in the figure, the device 200 may include an application circuit 202, a baseband circuit 204, an RF circuit 206, an RFFE circuit 208, and multiple antennas 210 at the same time. In some embodiments, the baseband circuit 204 may be similar to the baseband circuit 125 and substantially interchangeable. Multiple antennas 210 may constitute one or more antenna panels for beamforming. The components of the illustrated device 200 may be included in a UE or an AN. In some embodiments, the device 200 may include fewer elements (for example, the cell may not utilize the application circuit 202, but include a processor / controller to process IP data received from the EPC). In some embodiments, the device 200 may include additional elements, such as a memory / storage device, a display, a camera, a sensor, or an input / output (I / O) interface. In other embodiments, the components described below may be included in more than one device (for example, the circuit may be included separately in more than one device for a cloud-RAN (C-RAN) specific implementation).
[0042] The application circuit 202 may include one or more application processors. For example, the application circuit 202 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The processors may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). These processors may be coupled to or may include memory / storage devices, and may be configured to execute instructions stored in the memory / storage devices to enable various applications or operating systems to run on the device 200. In some embodiments, the processors of the application circuit 202 may process IP data packets received from the EPC.
[0043] The baseband circuit 204 may include circuits such as, but not limited to, one or more single-core or multi-core processors. In some embodiments, the baseband circuit 204 may be similar to and substantially interchangeable with the baseband circuit 125 and the baseband circuit 130. The baseband circuit 204 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of the RF circuit 206 and generate baseband signals for the transmit signal path of the RF circuit 206. The baseband circuit 204 may interact with the application circuit 202 to generate and process baseband signals and control the operation of the RF circuit 206. For example, in some embodiments, the baseband circuit 204 may include a third generation (3G) baseband processor 204A, a fourth generation (4G) baseband processor 204B, a fifth generation (5G) baseband processor 204C, or other baseband processors 204D of other existing generations, generations under development, or generations to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuit 204 (e.g., one or more of the baseband processors 204A-D) may handle various radio control functions that can communicate with one or more radio networks via the RF circuit 206. In other embodiments, some or all of the functions of the baseband processors 204A-204D may be included in a module stored in the memory 204G and executed via the central processing unit (CPU) 204E. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuit of the baseband circuit 204 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuit of the baseband circuit 204 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples, and may include other suitable functions in other embodiments.
[0044] In some embodiments, the baseband circuit 204 may include one or more audio digital signal processors (DSPs) 204F. The audio DSP 204F may include elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments. In some embodiments, the components of the baseband circuit may be appropriately combined in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all of the components of the baseband circuit 204 and the application circuit 202 may be implemented together, such as, for example, on a SOC.
[0045] In some embodiments, baseband circuitry 204 may provide communications compatible with one or more radio technologies. For example, in some embodiments, baseband circuitry 204 may support communications with an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) or other wireless metropolitan area network (WMAN), wireless local area network (WLAN), wireless personal area network (WPAN). Embodiments in which baseband circuitry 204 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.
[0046] RF circuitry 206 may communicate with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various embodiments, RF circuitry 206 may include one or more switches, filters, amplifiers, etc. to facilitate communication with a wireless network. RF circuitry 206 may include receiver circuitry 206A, which may include circuitry for down-converting RF signals received from RFFE circuitry 208 and providing baseband signals to baseband circuitry 204. RF circuitry 206 may also include transmitter circuitry 206B, which may include circuitry for up-converting baseband signals provided by baseband circuitry 204 and providing RF output signals for transmission to RFFE circuitry 208.
[0047] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, RF circuit 206 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits, and baseband circuit 204 may include a digital baseband interface to communicate with RF circuit 206.
[0048] In some dual-mode embodiments, separate radio integrated circuit (IC) circuits may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this respect.
[0049] The RFFE circuitry 208 may include a receive signal path that may include circuitry configured to operate on RF beams received from one or more antennas 210. The RF beams may be transmit beams formed and transmitted by the AN 110 when operating in the millimeter wave or sub-millimeter wave frequency range. The RFFE circuitry 208 coupled to the one or more antennas 210 may receive the transmit beams and forward them to the RF circuitry 206 for further processing. The RFFE circuitry 208 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 206 for transmission by the one or more antennas 210 with or without beamforming. In various embodiments, amplification through the transmit or receive signal path may be accomplished only in the RF circuitry 206, only in the RFFE circuitry 208, or in both the RF circuitry 206 and the RFFE circuitry 208.
[0050] In some embodiments, the RFFE circuit 208 may include a TX / RX switch to switch between transmit mode and receive mode operation. The RFFE circuit 208 may include a receive signal path and a transmit signal path. The receive signal path of the RFFE circuit 208 may include a low noise amplifier (LNA) to amplify the received RF beam and provide the amplified received RF signal as an output (e.g., to the RF circuit 206). The transmit signal path of the RFFE circuit 208 may include a power amplifier (PA) to amplify the input RF signal (e.g., provided by the RF circuit 206), and one or more filters to generate an RF signal for beamforming and subsequent transmission (e.g., through one or more of the one or more antennas 210).
[0051] The processor of the application circuit 202 and the processor of the baseband circuit 204 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 204 can be used alone or in combination to perform layer 3, layer 2, or layer 1 functions, while the processor of the application circuit 202 can utilize data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., transport communication protocol (TCP) and user datagram protocol (UDP) layers). As mentioned herein, layer 3 may include a radio resource control (RRC) layer, which will be described in further detail below. As mentioned herein, layer 2 may include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, layer 1 may include a physical (PHY) layer of the UE / AN, which will be described in further detail below.
[0052] Figure 3AAn embodiment of a RF front end 300 incorporating a millimeter wave RFFE 305 and one or more sub-6 GHz radio frequency integrated circuits (RFICs) 310 is shown. In some embodiments, the millimeter wave RFFE 305 may be similar to and substantially interchangeable with the RFFE 165, RFFE 170, and / or RFFE circuitry 208. The millimeter wave RFFE 305 may be used for the UE 105 when operating in FR2 or millimeter wave; the RFIC 310 may be used for the UE 105 when operating in FR1, sub-6 GHz, or LTE bands. In this embodiment, the one or more RFICs 310 may be physically separated from the millimeter wave RFFE 305. The RFIC 310 may include connections to one or more antennas 320. The RFFE 305 may be coupled to a plurality of antennas 315, which may constitute one or more antenna panels.
[0053] Figure 3B An alternative embodiment of RFFE 325 is shown. In this aspect, both mmWave and sub-6 GHz radio functionality may be implemented in the same physical RFFE 330. RFFE 330 may incorporate both mmWave antenna 335 and sub-6 GHz antenna 340. In some embodiments, RFFE 330 may be similar to and substantially interchangeable with RFFE 165, RFFE 170, and / or RFFE circuitry 208.
[0054] Figure 3A and 3B Various RFFE architecture implementations of the UE 105 or AN 110 are shown.
[0055] Figure 4 An exemplary network 400 involving 5G NR communications according to various embodiments is shown. The network 400 may be an EN-DC network. The network 400 may include multiple ANs and / or Node Bs, such as eNB 405 and gNB 410. The eNB 405 and gNB 410 may communicate with Figure 1 4. The eNB 405 may be the same as or substantially similar to the AN 110 in the embodiment. The eNB 405 may be referred to as the MN 405, and the gNB 410 may be referred to as the SN 410. The eNB 405 may provide or be associated with a primary serving cell (PCell) 415 for the UE 105. The eNB 405 may also provide or be associated with one or more secondary cells (SCells) (e.g., 420 and 425). The PCell 415 and the SCells 420 / 425 may be part of a primary cell group (MCG) 430 for the UE 105.
[0056] In some embodiments, the gNB 410 may provide or be associated with a primary secondary serving cell (PSCell) 435 for the UE 105. The gNB 410 may also provide one or more SCells, such as 440 and 445. The PSCell 435 and SCells 440 / 445 may be part of an SCG 450 for the UE 105. Note that “AN of a PCell,” “AN in a PCell,” and “PCell” are used interchangeably throughout the disclosure herein and with respect to PSCell, SCell, etc.
[0057] In addition to the EN-DC mode, the various embodiments discussed herein are applicable to the NR-DC mode, as well as other DC operation modes involving NR operation in the SCG 450. For simplicity of description herein, only the EN-DC mode is described as an example.
[0058] In a network in which UE 105 operates in EN-DC mode, UE 105 may receive an LTE signal, also referred to as an E-UTRA (Evolved Universal Terrestrial Radio Access) signal, from eNB 405. The LTE signal may include multiple LTE frames, which may also include multiple LTE subframes. Those LTE subframes may be referred to as MCG service cell subframes or LTE subframes of MCG service cells. Cells 415 / 420 / 425 may be referred to as LTE service cells. At the same time, UE 105 may receive an NR signal from gNB 410. The NR signal may include multiple NR frames, which may also include multiple NR subframes. Those NR subframes may be referred to as SCG service cell subframes or NR subframes of SCG service cells. Cells 435 / 440 / 445 may be referred to as NR service cells. In addition, the NR subframe may include multiple NR time slots. In some embodiments, the NR time slot may be used to indicate the start of the MG. Note that an NR subframe can always be 1 millisecond (ms), and an NR slot can be 1 ms or have different lengths in the time domain due to various subcarrier spacings (SCs).
[0059] In addition to the MCG / SCG serving cells, there may be multiple neighboring cells in the network 400. Those neighboring cells associated with the eNB 405 may be referred to as MCG non-serving cells, and those neighboring cells associated with the gNB 410 may be referred to as SCG non-serving cells. The UE 105 may monitor one or more non-serving cells by performing reference signal measurements. The reference signal may operate at a serving frequency or a non-serving frequency. A serving frequency is a frequency at which one or more serving cells operate. A non-serving frequency is a frequency other than all serving frequencies at a certain moment.
[0060] UE 105 may measure one or more reference signals associated with one or more cells of SCG 450 based on configuration from the network. The configuration may come from MN 405 or SN 410. The configuration may indicate one or more measurement objects (MOs) including information of reference signal frequency, SC, and other information.
[0061] Reference signals may include, but are not limited to, synchronization signal (SS) blocks, channel state information-reference signals (CSI-RS). If, based on certain measurement criteria, one or more of the reference signal measurements associated with the SCG 450 fails or is considered to have failed, the SCG 450 may be determined to be a failed or failed SCG. If the UE 105 determines an SCG failure based on the corresponding criteria, the UE 105 may generate an SCG failure report to the MN 405 to report details about the SCG failure corresponding to the reference signal measurement. The criteria may include, but are not limited to, radio link failure (RLF) on the PSCell and PSCell change failure. As an example, such a report may include a MeasResultSCG-Failure information element (IE). The MeasResultSCG-Failure IE may include the information listed below. Note that the MeasResultSCG-Failure IE does not provide SCS information about the failed reference signal.
[0062] MeasResultSCG-Failure information element
[0063]
[0064] In NR communications, the NR parameter set allows multiple SCs, such as 15kHz, 30kHz, 120kHz, 240kHz, etc. Therefore, for any given reference signal frequency, one SCS among the multiple SCs may be used together with the reference signal frequency to characterize the reference signal. Therefore, if the UE 105 does not include the SCS information of the failure or detected reference signal measurement in the SCG failure report, the MN 405 and / or SN 410 may not be able to confirm the exact failure or detected reference signal measurement associated with a specific SCS. This may cause ambiguity to the MN 405 / SN 410, and the MN 405 / SN 410 may not be able to schedule or configure the corresponding data communication within the network or configure the appropriate cell and / or beam for the UE 105 based on the SCG failure report. The SCG failure report may not be sufficient to serve its purpose.
[0065] In one example, the UE 105 may be configured with more than one MO for the SSB frequency, and each of those configured MOs may have the same reference signal frequency but a different SC, which may be used to measure one or more neighboring cells. Example configurations are listed below:
[0066]
[0067] In this example, if the fault report does not include information that may indicate the SCS of the faulty or detected SS, the MN 405 may not be able to determine the SCS of the faulty or detected SSB. Similarly, in CSI-RS measurement, the UE 105 may be configured with more than one MO, and each of these configured MOs may have the same reference frequency but different CSI-RS resources, which may have the same or different SCs. Exemplary configurations are listed below:
[0068]
[0069] In the scenario of measuring SS blocks (SSBs), the SSB frequency and PCI information may be sufficient to indicate a faulty SS. The UE 105 may measure the SSB according to one or more MOs and determine one (or more) SSBs with a specific frequency and cannot measure the SCS. In the corresponding SCG fault report, the UE 105 may report the SSB frequency and the physical cell ID (PCI) associated with the SSB to the MN 405, which is still able to determine the accurate SSB due to the lack of corresponding SCS information. In some network scenarios where the serving cell and / or neighboring cells operate at the serving frequency, the UE may be configured to measure one or more SSBs in one or more bandwidth parts (BWPs). Since the SSB frequencies may be different from each other between BWPs, the SCG fault report may be sufficient to provide faulty or detected reference signal information and / or measurements without causing ambiguity to the MN 405 / SN 410. For neighboring cells at the serving frequency, the corresponding PCI information may be sufficient to indicate a faulty or detected reference signal measurement.
[0070] In the scenario where CSI-RS is measured, the CSI-RS frequency, the corresponding PCI, and the CSI-RS index may be included in the SCG report. If the cell is a serving cell, the UE 105 may be configured to measure the same CSI-RS frequency and PCI, but with a different SCS. For example, the UE 105 may measure at different BWPs in the same cell. If cell measurements of different SCSs for the same PCI and CSI-RS frequency are to be reported, this may cause ambiguity in which SCS the reference signal measurements in the SCG failure report refer to without the SCS reported for measurement. Similar situations may occur for neighboring cell measurements in both serving and non-serving frequencies.
[0071] Note that the CSI-RS index may be optional and its use may depend on the configuration used for reporting. For example, in beam measurement, the CSI-RS index of the CSI-RS resource may be used to indicate a specific beam among all beams associated with the same CSI-RS frequency and PCI. However, the CSI-RS index may not be available because it depends on the configuration used for reporting. For example, if the report is based on cell-level measurement, the CSI-RS index may not be available.
[0072] In an embodiment, the SCS information may be included in the SCG failure report, so that the MN 405 and / or SN 410 can identify the failure and / or other detected reference signals. An exemplary report in the MeasResultSCG-Failure IE is listed below. In this example, the SCS information is shown in bold.
[0073] MeasResultSCG-Failure information element
[0074]
[0075] In an embodiment, alternatively or in addition, a measurement identification (ID) may be used. Since the measurement ID may include or indicate SCS information of the reference signal, etc. If the measurement ID is included in the SCG failure report, the MN and / or SN 410 may be able to determine the SCS of the reference signal. For example, if the SN 410 configures the measurement ID, it may be able to know the measurement information (e.g., frequency and SCS) being reported. In addition, if the measurement ID allocation is coordinated between the MN 405 and the SN 410, the MN 405 may be aware of the measurement. An exemplary report in the MeasResultSCG-Failure IE is listed below. In this example, the measurement ID information (measid) is represented in bold.
[0076] MeasResultSCG-Failure information element
[0077]
[0078]
[0079] In an embodiment, MN 405 and / or 410 may not be able to decode SCS information and / or measurement ID without an indication that such information is included in the IE. This indication of a non-critical extension may be used in the MeasResultSCG-Failure IE or in a separate IE to indicate that such information is included in the SCG failure report. This configurable parameter may provide backward compatibility for previous versions. An exemplary indication in the MeasResultSCG-Failure IE is listed below. In this example, the non-critical extension (measResuitPerMOListExt) is shown in bold.
[0080] MeasResultSCG-Failure information element
[0081]
[0082] In an embodiment, a network including MN 405 and / or SN 410 may configure reference signal measurements so that address ambiguity may not occur. This may require further coordination between MN 405 and SN 410 and other control of the network.
[0083] Figure 5A An operational flow / algorithm structure 500 is shown for facilitating a process for reporting SCG failures relative to reference signal measurements by a UE 105 in a NR-involved network according to various embodiments. Note that Figure 5A Describes and is relative to Figure 4 The various embodiments described above with respect to SCG fault reporting may be the same or substantially similar to the SCG fault reporting. The operation flow / algorithm structure 500 may be executed by the UE 105 or circuitry thereof.
[0084] The operational flow / algorithm structure 500 may include generating an IE indicating a measurement ID of an SCS or measurement of a reference signal based on a failed measurement of a reference signal of the SCG at 510. The IE may be the same or substantially similar to the MeasResultSCG-Failure IE described above. The MeasResultSCG-Failure IE is also described in 3GPP Technical Specification (TS) 38.331, v15.2.1 (June 21, 2018). The reference signal may be an SSB, CSI-RS, or other similar reference signal. More details about the IE may be found in the 3GPP Technical Specification (TS) 38.331, v15.2.1 (June 21, 2018). Figure 4 in the description.
[0085] The operation flow / algorithm structure 500 may also include transmitting a message including the IE to the AN at 520. The AN may be the same as or substantially similar to the AN 110 in the present disclosure. The transmission of the message may be performed via RRC or other adapted signaling.
[0086] In some embodiments, the IE may also include bit information to indicate that the IE includes information of the SCS of the reference signal or the measurement ID of the measurement. Such bit parameters may be non-critical extensions and are represented as measResultPerMOListExt in the MeasResultSCG-Failure IE. In addition or alternatively, this parameter may be indicated elsewhere and transmitted to the AN in the same or different format.
[0087] In an implementation scheme, the UE may receive a measurement configuration from the AN to perform reference signal measurements relative to the SCG according to the corresponding MO. Once the UE measures the reference signals, the UE may determine that one or more reference signals have failed the measurement based on various criteria. The UE may generate an SCG failure report accordingly.
[0088] Figure 5B An operational flow / algorithm structure 505 is shown for facilitating a process for reporting SCG failures measured relative to reference signals by the AN 110 in a network involving NRs according to various embodiments. The operational flow / algorithm structure 505 may be performed by the AN 110 or circuitry thereof.
[0089] At 515, the operational flow / algorithm structure 505 may include decoding an IE indicating a measurement ID of a reference signal of an SCS or SCG of a reference signal upon receiving a message including an IE generated by a UE. A failure measurement may be determined based on the measurement of the reference signal.
[0090] The operation flow / algorithm structure 505 may also include determining the SCS of the reference signal to identify the faulty measurement of the reference signal of the SCG at 525. Once the faulty SCG is identified using sufficient reference signal information, the AN may determine one or more actions with respect to the SCG. These actions may include, but are not limited to, releasing the SCG, maintaining the SCG, changing the PSCell of the SCG, and changing other cells of the SCG.
[0091] In some embodiments, AN 110 may first decode an indication indicating a received SCG fault report that includes additional information, such as the SCS of the reference signal, a measurement ID, or other information.
[0092] Figure 6 An exemplary interface of a baseband circuit according to some embodiments is shown. As discussed above, Figure 2The baseband circuit 204 may include processors 204A-204E and a memory 204G used by the processors. Figure 5A and Figure 5B In various embodiments, the processors 204A-204E of the UE 105 may execute some or all of the operational flow / algorithm structure 500. Figure 5A and Figure 5B In various embodiments, the processors 204A-204E of the AN 110 may execute some or all of the operation flow / algorithm structure 505. Each of the processors 204A-204E may include a memory interface 604A-604E for sending / receiving data to / from the memory 204G, respectively. The processors 204A-204E of the UE 105 may be used to process SFTD measurements; the processors 204A-204E of the AN 110 may be used to generate SFTD measurement configurations.
[0093] The baseband circuit 204 may also include: one or more interfaces to communicatively couple to other circuits / devices, such as a memory interface 612 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 204); an application circuit interface 614 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 204); Figure 2 RF circuit interface 616 (for example, for sending / receiving data to / from the application circuit 202); Figure 2 an interface for sending / receiving data to / from a RF circuit 206); a wireless hardware connection interface 618 (e.g., for sending / receiving data to / from a near field communication (NFC) component, Parts (e.g. Low power consumption), components and other communication components to send / receive data); and a power management interface 620 (for example, an interface for sending / receiving power or control signals).
[0094] Figure 7 8 is a block diagram illustrating components capable of reading instructions from a machine-readable medium or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein, according to some example embodiments. Specifically, FIG8 illustrates a schematic diagram of a hardware resource 700, including one or more processors (or processor cores) 710, one or more memory / storage devices 720, and one or more communication resources 730, each of which can be communicatively coupled via a bus 840. For embodiments in which node virtualization (e.g., network function virtualization (NFV)) is utilized, a hypervisor 702 can be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resource 700.
[0095] Processor 710 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) (such as a baseband processor), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 712 and processor 714.
[0096] The memory / storage device 720 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 720 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.
[0097] The communication resources 730 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 704 or one or more databases 706 via the network 708. For example, the communication resources 730 may include a wired communication component (e.g., for coupling via a universal serial bus (USB)), a cellular communication component, an NFC component, Parts (e.g. Low power consumption), components and other communication components.
[0098] The instructions 750 may include software, programs, applications, applet, applications, or other executable codes for causing at least any one of the processors 710 to perform any one or more of the methodologies discussed herein (e.g., operation flows 500 and 505). For example, in an embodiment in which the hardware resource 700 is implemented in the UE 105, the instructions 750 may cause the UE to perform some or all of the operation flow / algorithm structure 500. In other embodiments, the hardware resource 700 may be implemented in the AN 110. The instructions 750 may cause the AN 110 to perform some or all of the operation flow / algorithm structure 505. The instructions 750 may reside in whole or in part in at least one of the processor 710 (e.g., in a cache memory of the processor), the memory / storage device 720, or any suitable combination thereof. In addition, any portion of the instructions 750 may be transmitted to the hardware resource 700 from any combination of the peripheral device 704 or the database 706. Thus, the memory of processor 710, memory / storage device 720, peripheral device 704, and database 706 are examples of computer-readable and machine-readable media.
[0099] Some non-limiting examples of various embodiments are provided below.
[0100] Embodiment 1 may include a method comprising: generating or causing generation of an IE indicating information relative to the SCG failure based on a measurement of an SCG failure corresponding to a reference signal; and transmitting or causing transmission of the message to an access node (AN).
[0101] Embodiment 1.5 may include a method comprising: generating or causing generation of an IE indicating information relative to a SCG failure based on a failure measurement of a reference signal; and transmitting or causing transmission of the message to an access node (AN).
[0102] Embodiment 2 may include the method of embodiment 1 / 1.5 and / or some other embodiments herein, wherein the IE is used to indicate the SCS of the reference signal.
[0103] Embodiment 3 may include the method of embodiment 1 / 1.5 and / or some other embodiments herein, wherein the IE is used to indicate a measurement ID of the measurement.
[0104] Embodiment 4 may include the method of Embodiment 3 and / or some other embodiments herein, wherein the measurement ID is used to indicate the frequency of the reference signal and the SCS of the reference signal, etc.
[0105] Embodiment 5 may include the method of embodiment 1 and / or some other embodiments herein, wherein the IE is used to report SCG failure.
[0106] Embodiment 6 may include the methods of Embodiments 1 to 5 and / or some other embodiments herein, wherein the IE is a MeasResultSCG-Failure IE.
[0107] Embodiment 7 may include the method of embodiments 1 to 6 and / or some other embodiments herein, wherein the reference signal includes a synchronization signal block (SSB) or a channel state information-reference signal (CSI-RS).
[0108] Embodiment 8 may include the method of embodiments 1 to 7 and / or some other embodiments herein, wherein the IE includes a bit indicating that the IE includes information of the SCS or measurement ID of the measurement of the reference signal.
[0109] Embodiment 9 may include the method of embodiments 1 to 7 and / or some other embodiments herein, wherein the IE is the first IE, and when executed, the instructions further cause the UE to
[0110] The second IE is generated to indicate that the first IE includes information of the SCS of the reference signal or the measurement ID of the measurement.
[0111] Embodiment 10 may include the method of embodiments 1 to 9 and / or some other embodiments herein, the method further comprising measuring or causing measurement of a reference signal of a cell relative to the SCG or a beam of a cell of the SCG; and determining or causing determination of an SCG failure based on one or more measurement results from the measurement of the reference signal of the cell relative to the SCG.
[0112] Embodiment 11 may include the method of embodiment 10 and / or some other embodiments herein, wherein the cell is a service cell or a neighboring cell of the SCG.
[0113] Embodiment 12 may include the method of embodiment 10 and / or some other embodiments herein, wherein the reference signal is used to operate at a serving frequency of a serving cell or a neighboring cell, or to operate at a non-serving frequency of a serving cell or a neighboring cell.
[0114] Embodiment 13 may include the methods of embodiments 1 to 12 and / or some other embodiments herein, wherein the AN is a master node (MN) in an EN-DC network, an NR-DC network, or a network with NR operation in an SCG.
[0115] Embodiment 14 may include the method of embodiments 1 to 13 and / or some other embodiments herein, wherein the method is performed by a UE or a part thereof.
[0116] Embodiment 15 may include a method comprising: upon receiving a message including an IE generated by a UE, decoding or causing decoding of an IE indicating information relative to a faulty SCG determined by the UE based on measurements of a reference signal; and determining or causing determination of the SCS of the reference signal, etc., to identify the faulty SCG.
[0117] Embodiment 16 may include the method of embodiment 15 and / or some other embodiments herein, wherein the IE is used to indicate the SCS of the reference signal.
[0118] Embodiment 17 may include the method of embodiment 15 and / or some other embodiments herein, wherein the IE is used to indicate a measurement ID of the measurement.
[0119] Embodiment 18 may include the method of embodiment 15 and / or some other embodiments herein, wherein the measurement ID is used to indicate the frequency of the reference signal and the SCS of the reference signal, etc.
[0120] Embodiment 19 may include the methods of Embodiments 15 to 18 and / or some other embodiments herein, wherein the IE is used to report an SCG failure and is a MeasResultSCG-Failure IE.
[0121] Embodiment 20 may include the method of embodiments 15 to 19 and / or some other embodiments herein, wherein the IE includes a bit indicating that the IE includes information of the SCS or measurement ID of the measurement of the reference signal.
[0122] Embodiment 21 may include the method of embodiments 15 to 20 and / or some other embodiments of the present invention, wherein the IE is a first IE, and when executed, the instruction also causes the AN to decode a second IE to indicate that the first IE includes information of the SCS of the reference signal or the measurement ID of the measurement.
[0123] Embodiment 22 may include the method of embodiments 15 to 20 and / or some other embodiments herein, further comprising releasing or causing release of a faulty SCG based on decoding.
[0124] Embodiment 23 may include the method of Embodiments 15 to 20 and / or some other embodiments herein, further comprising changing or causing a change to a faulty SCG.
[0125] Embodiment 24 may include the method of embodiment 23 and / or some other embodiments herein, wherein changing the faulty SCG is changing one or more operating frequencies and / or associated SCSs relative to one or more cells of the faulty SCG.
[0126] Embodiment 25 may include the methods of embodiments 15 to 24 and / or some other embodiments herein, wherein the AN is a master node (MN) in an EN-DC network, an NR-DC network, or a network with NR operation in an SCG.
[0127] Embodiment 26 may include the method of Embodiments 15 to 25 and / or some other embodiments herein, wherein the method is performed by the AN or a portion thereof.
[0128] Embodiment 27 may include an apparatus comprising means for performing one or more elements of the method described in or related to any of Embodiments 1 to 26, or any other method or process described herein.
[0129] Embodiment 28 may include one or more non-transitory computer-readable media, which include instructions that, when one or more processors of an electronic device execute the instructions, cause the electronic device to perform one or more elements of a method described in or related to any one of Embodiments 1 to 26 or any other method or process described herein.
[0130] Embodiment 29 may include a device comprising logic components, modules and / or circuits for performing one or more elements of the method described in or related to any of Embodiments 1 to 26 or any other method or process described herein.
[0131] Embodiment 30 may include methods, techniques or processes described in or related to any one of Embodiments 1 to 26, or parts or components thereof.
[0132] Embodiment 31 may include a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or a portion thereof, described in or related to any one of Embodiments 1 to 26.
[0133] The present disclosure is described with reference to the flowcharts or block diagrams of the methods, devices (systems) and computer program products according to the embodiments of the present disclosure. It should be understood that each block of the flowchart illustration or block diagram, as well as the combination of blocks in the flowchart illustration or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device create a device for implementing the function / action specified in one or more blocks of the flowchart or block diagram.
[0134] These computer program instructions may also be stored in a computer-readable medium, which can direct a computer or other programmable data processing device to function in a specific manner, so that the instructions stored in the computer-readable medium produce a manufactured article including instruction devices, which implement the functions / actions specified in one or more blocks of the flowchart or block diagram.
[0135] Computer program instructions may also be loaded onto a computer or other programmable data processing apparatus so that a series of operational steps are performed on the computer or other programmable apparatus to produce a computer-implemented process, so that the instructions executed on the computer or other programmable apparatus provide a process for implementing the functions / actions specified in one or more blocks of the flowchart or block diagram.
[0136] The descriptions of the implementations shown herein, including the implementations described in the Abstract, are not intended to be exhaustive or to limit the disclosure to the precise forms disclosed. Although specific implementations and examples are described herein for illustrative purposes, as will be appreciated by those skilled in the relevant art, various calculations may be performed to achieve alternative or equivalent embodiments or implementations for the same purpose, based on the above detailed description, without departing from the scope of the disclosure.
Claims
1. One or more computer readable media (CRMs), the one or more CRMs comprising instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to: generating an information element (IE) indicating a subcarrier spacing (SCS) of a reference signal of a secondary cell group (SCG) based on a failure measurement of the reference signal; and A message including the IE is transmitted to an access node (AN).
2. One or more CRMs according to claim 1, wherein the IE is used to report the failure measurement of the reference signal of the SCG and is MeasResultSCG-FailureIE.
3. The one or more CRMs of claim 1, wherein the reference signal comprises a synchronization signal block (SSB) or a channel state information-reference signal (CSI-RS).
4. The one or more CRMs of claim 1, wherein the IE includes a bit indicating that the IE includes information of the SCS of the reference signal.
5. The one or more CRMs according to claim 1, wherein the IE is a first IE, and when executed, the instructions further cause the UE to generate a second IE to indicate that the first IE includes information of the SCS of the reference signal.
6. One or more CRMs according to any one of claims 1 to 5, wherein when executed, the instructions further cause the UE to: measuring the reference signal relative to a cell of the SCG or a beam of the cell of the SCG; and The measurement is determined to be a faulty measurement based on one or more measurement results from the measurement of the reference signal relative to the cell of the SCG or the beam of the cell of the SCG.
7. One or more CRMs according to claim 6, wherein the cell is a serving cell or a neighboring cell relative to the SCG.
8. The one or more CRMs of claim 6, wherein the reference signal is used to operate at a serving frequency of a serving cell or a neighboring cell, or to operate at a non-serving frequency of the neighboring cell.
9. The one or more CRMs of claim 8, wherein the serving frequency and the non-serving frequency are New Radio (NR) frequencies.
10. The one or more CRMs according to any one of claims 1 to 5, wherein the AN is a master node (MN) in an Evolved Universal Terrestrial Radio Access-New Radio Dual Connectivity (EN-DC) network or a New Radio Dual Connectivity (NR-DC) network.
11. One or more computer readable media (CRMs), the one or more CRMs comprising instructions that, when executed by one or more processors of an access node (AN), cause the AN to: upon receiving a message including an information element (IE) generated by a user equipment (UE), decoding an IE indicating a subcarrier spacing (SCS) of a reference signal of a secondary cell group (SCG); and The SCS of the reference signal is determined to identify a faulty measurement of the reference signal of the SCG.
12. One or more CRMs according to claim 11, wherein the IE is used to report the failure measurement of the reference signal of the SCG and is a MeasResultSCG-Failure IE.
13. The one or more CRMs of claim 11, wherein the IE includes a bit indicating that the IE includes information of the SCS of the reference signal.
14. The one or more CRMs of claim 11, wherein the IE is a first IE, and when executed, the instructions further cause the AN to decode a second IE to indicate that the first IE includes information of the SCS of the reference signal.
15. One or more CRMs according to any one of claims 11 to 14, wherein when executed, the instructions further cause the AN to release or change the SCG based at least on the determined SCS of the reference signal.
16. One or more CRMs according to any one of claims 11 to 14, wherein the AN is a master node (MN) in an Evolved Universal Terrestrial Radio Access-New Radio Dual Connectivity (EN-DC) network or a New Radio Dual Connectivity (NR-DC) network.
17. A device of a user equipment (UE), include: A processing circuit, the processing circuit being configured to: generating an information element (IE) indicating a secondary cell group (SCG) failure based on measurement of a reference signal of the SCG, wherein the IE is used to indicate a subcarrier spacing (SCS) of the reference signal; and An interface circuit is coupled to the processing circuit, the interface being configured to transmit the IE to an access node (AN) to report the SCG failure.
18. The apparatus of claim 17, wherein the interface circuit is further configured to measure the reference signal corresponding to the SCS and a carrier frequency of a cell relative to the SCG.
19. The apparatus of claim 18, wherein the processing circuit is further configured to determine the SCG fault based on one or more measurements from the measurements of the reference signal.
20. The apparatus of claim 17, wherein the IE comprises a bit indicating that the IE comprises information of the SCS of the reference signal.
21. An access node (AN) device, include: means for decoding an information element (IE) indicating a secondary cell group (SCG) failure based on a measurement of a reference signal upon receiving the IE transmitted by a user equipment (UE), wherein the IE is used to indicate a subcarrier spacing (SCS) of the reference signal; and Means for determining the SCS of the reference signal to identify a failure of the SCG.
22. The apparatus of claim 21, wherein the IE comprises a bit for indicating that the IE comprises information of the SCS of the reference signal.
23. The device according to claim 21, further comprising: include: means for generating a message indicating the determined SCS of the reference signal; as well as Means for transmitting the message to a Secondary Node (SN) operating in New Radio (NR) communications.
24. The apparatus according to any one of claims 21 to 23, wherein the AN is a master node (MN) in a dual connectivity (DC) network, and the SCG operates with NR-E-UTRA (NE) communications.
