Inter-system mobility management method and device for RedCap multi-mode terminal

Abstract

The invention discloses an inter-system mobility management method of a RedCap multi-mode terminal. If the RedCap multi-mode terminal detects that the 5G cell satisfies the current inter-system measurement event and the historical information does not record whether the 5G cell supports RedCap, the RedCap multi-mode terminal determines that the 5G cell satisfies the current inter-system measurement event; if yes, the RedCap multimode terminal attempts to perform advanced downlink synchronization on the 5G cell in a measurement gap configured in a current 4G network or in a time slice resource of a discontinuous reception period, or in a specific time slice resource expanded and spliced by the configured time slice resource, or in a user-defined gap of the terminal, and pre-reads the SIB1 of the 5G cell. According to the invention, the RedCap multi-mode terminal residing in the 4G cell fully utilizes, expands or defines various time slice resources to try to perform downlink synchronization on the target 5G NR cell, and pre-reads the SIB1 after downlink synchronization, so that the RedCap multi-mode terminal can judge whether the target 5G NR cell supports RedCap or not in advance.

Description

Technical Field

[0001] The present application relates to a mobile terminal inter-system mobility management method. Background Art

[0002] In the R15 and R16 versions of the 3GPP 5G communication protocol, three application scenarios are defined: eMBB (Enhanced Mobile Broadband), URLLC (Ultra-Reliable and Low Latency Communications), and mMTC (Massive Machine Type Communication). eMBB is mainly used in 5G mobile phones, focusing on indicators such as network speed, bandwidth capacity, and spectrum efficiency; URLLC focuses on reliability and low latency; and mMTC focuses on the number of connections and energy consumption. The latter two mainly focus on industry Internet, including vertical industry fields such as industrial manufacturing and Internet of Vehicles.

[0003] In the R17 version of the 3GPP 5G communication protocol, a lightweight RedCap (Reduced Capability) terminal was introduced. Compared with traditional 5G terminals, RedCap terminals reduce bandwidth, reduce the number of MIMO (multi-input multi-output) layers, adjust modulation methods, introduce half-duplex mode, and remove DC (Dual Connectivity) and CA (Carrier Aggregation) features to reduce terminal costs and power consumption, extend service life, and better adapt to IoT deployment scenarios with medium and low rate requirements such as industrial sensors, video surveillance, and wearable devices.

[0004] When a mobile terminal (UE, user equipment) accesses a 5G cell, the mobile terminal and the 5G cell are required to respectively identify whether the other party supports RedCap capabilities.

[0005] The mobile terminal mainly determines whether the 5G cell supports RedCap capabilities through the relevant parameters and rules in the 38.300, 38.304 and 38.331 communication protocols of the 3GPP organization. After the RedCap terminal reads the system message broadcast by the 5G cell, it determines whether the current cell supports RedCap according to the intraFreqReselectionRedCap indication in SIB1 (System Information Block Type 1). If this indication is not carried in SIB1, it means that the 5G cell prohibits RedCap terminals from accessing, so the RedCap terminal can directly BAR (access prohibition) the 5G cell.

[0006] The 5G cell determines whether the mobile terminal supports RedCap capabilities mainly through the following three strategies.

[0007] First, during the random access process of the mobile terminal, if the preamble of the PRACH (Physical Random Access Channel) dedicated to the RedCap terminal is configured in the SIB1 broadcast by the 5G cell, if the 5G cell detects that the message 1 (MSG1) or message A (MSGA) sent by the mobile terminal uses the preamble of the PRACH dedicated to the RedCap terminal, it can identify that the mobile terminal supports RedCap. If the PRACH occasion dedicated to the RedCap terminal is also configured in the SIB1 broadcast by the 5G cell, if the 5G cell detects that the message 1 or message A sent by the mobile terminal is at the PRACH occasion dedicated to the RedCap terminal, it can also identify that the mobile terminal supports RedCap.

[0008] Second, during the random access process, if the mobile terminal is a RedCap terminal, when sending message 3 (MSG3) or message A, it will use a dedicated LCID (Logical Channel ID) to identify CCCH (Common Control Channel) or CCCH1. The 5G cell identifies whether the mobile terminal supports RedCap by whether the mobile terminal uses the LCID dedicated to the RedCap terminal.

[0009] Third, when the mobile terminal resides in the 5G network, the 5G cell that supports R17 or higher versions of the 3GPP 5G communication protocol obtains information about whether the mobile terminal supports RedCap through terminal capability query. If the mobile terminal supports RedCap, the mobile terminal informs the network side through RedCap related capability indications such as the R17 capability parameter supportOfRedCap.

[0010] When a mobile terminal resides in a 5G network, a 5G cell that only supports R16 or lower versions of the 3GPP 5G communication protocol cannot correctly determine whether the mobile terminal supports RedCap even if it receives the R17 capability reported by the RedCap terminal because the network side cannot parse the R17 capability parameter supportOfRedCap and other RedCap-related capability indications.

[0011] When the mobile terminal resides in the 4G network, even if the 4G cell receives the R17 capability reported by the RedCap terminal, it cannot correctly determine whether the mobile terminal supports RedCap because the network side cannot parse the R17 capability parameter supportOfRedCap and other RedCap-related capability indications.

[0012] RedCap multimode terminal refers to a mobile terminal that supports both RedCap cells of 5G network and 4G network. When a RedCap multimode terminal resides in a 4G network, if there is a 5G neighboring cell, the 4G network usually configures 5G inter-RAT measurement (also known as inter-system measurement) for mobility management of mobile terminals. The reporting criteria for inter-system measurement mainly include B1 event (Event B1) and B2 event (Event B2). B1 event indicates that the signal quality of the neighboring cell of the heterogeneous system is higher than the absolute threshold, and B2 event indicates that the signal quality of the current serving cell is lower than the absolute threshold and the signal quality of the neighboring cell of the heterogeneous system is higher than the absolute threshold. During the relative movement of the RedCap multimode terminal with the network, when the RedCap multimode terminal detects that the current heterogeneous system measurement meets the B1 event or the B2 event, the RedCap multimode terminal sends a measurement report message to the network. When the network receives the measurement report message reported by the RedCap multimode terminal, it usually notifies the RedCap multimode terminal to switch or redirect to the heterogeneous system cell of the target standard through the air interface signaling MobilityFromEUTRACommand and RRCConnectionRelease messages. If the target cell is a 5G cell that only supports R16 or lower versions of the 3GPP 5G communication protocol, the RedCap multi-mode terminal may be switched or redirected to a non-RedCap cell (a 5G cell that does not support RedCap). Since the RedCap multi-mode terminal cannot access the 5G network of the non-RedCap cell, it will inevitably lead to a switching failure or redirection failure, affecting the normal continuation or initiation of the service, and ultimately affecting the user experience. Summary of the invention

[0013] The technical problem to be solved by this application is: how to enable the RedCap multi-mode terminal residing in the 4G cell to determine in advance whether the 5G cell supports RedCap, thereby avoiding the RedCap multi-mode terminal from being switched or redirected to the 5G non-RedCap cell.

[0014] In order to solve the above technical problems, the present application proposes a method for managing inter-system mobility of RedCap multi-mode terminals, comprising the following steps. Step S1: The RedCap multi-mode terminal records the frequency, subcarrier spacing, and physical cell identifier of the 5G cell that has been successfully resided or searched; if the RedCap multi-mode terminal successfully reads the SIB1 of the 5G cell that has been successfully resided or searched, it further records the PLMN of the 5G cell, whether the 5G cell supports RedCap, and whether other accessible 5G neighboring cells can be searched in the same frequency band; this information is saved in the RedCap multi-mode terminal as historical information. Step S2: When the RedCap multi-mode terminal enters the connection state of the 4G network, the 4G network configures 5G inter-system measurement information; the RedCap multi-mode terminal measures the 5G cell, and when a certain 5G cell is measured, the RedCap multi-mode terminal first queries the historical information. If the historical information records that the 5G cell supports RedCap, or the historical information does not record whether the 5G cell supports RedCap, the 5G cell continues to participate in the measurement and evaluation, and proceeds to step S3. If the historical information records that the 5G cell does not support RedCap, the 5G non-RedCap cell will no longer participate in the measurement and evaluation. Step S3: The RedCap multimode terminal measures and evaluates the 5G cell. If it is measured that the 5G cell does not meet any current heterosystem measurement event, the RedCap multimode terminal does not trigger a measurement report. If it is measured that the 5G cell meets a current heterosystem measurement event, and the historical information records that the 5G cell supports RedCap, the RedCap multimode terminal sends a heterosystem measurement report to the 4G network. If it is measured that the 5G cell meets a current heterosystem measurement event, and the historical information does not record whether the 5G cell supports RedCap, proceed to step S4. Step S4: The RedCap multimode terminal attempts to synchronize the 5G cell in advance in the measurement gap or discontinuous reception cycle time slice resources configured by the current 4G network, or in the specific time slice resources spliced ​​by the configured time slice resources, or in the terminal-defined gap, and pre-reads the SIB1 of the 5G cell. If the RedCap multimode terminal succeeds in downlink synchronization of the 5G cell and pre-reading of SIB1 of the 5G cell, proceed to step S5. If the RedCap multimode terminal fails in downlink synchronization of the 5G cell, or succeeds in downlink synchronization but fails to pre-read SIB1 of the 5G cell, proceed to step S6. Step S5: The RedCap multimode terminal determines whether the 5G NR cell supports RedCap based on the SIB1 information of the 5G cell. If the 5G cell supports RedCap, proceed to step S3 to continue measuring and evaluating the 5G cell. If the 5G cell does not support RedCap, the 5G non-RedCap cell no longer participates in the measurement and evaluation.Step S6: The RedCap multimode terminal compares the signal quality of the 4G LTE service cell at this time with the preset threshold of the RedCap multimode terminal. If the signal quality of the 4G LTE service cell at this time is less than the preset threshold of the RedCap multimode terminal, the RedCap multimode terminal sends the measurement report normally. If the signal quality of the 4G LTE service cell at this time is greater than or equal to the preset threshold of the RedCap multimode terminal, the RedCap multimode terminal does not send this measurement report.

[0015] Furthermore, after the step S2 is executed, no matter which case, the RedCap multi-mode terminal will add the measured information of the 5G cell to the historical information or update the original record in the historical information.

[0016] Furthermore, after the step S5 is executed, no matter which case, the RedCap multi-mode terminal adds the information of the 5G cell to the historical information or updates the original record in the historical information.

[0017] Furthermore, in step S4, successful downlink synchronization is a prerequisite for pre-reading SIB1.

[0018] Furthermore, the step S4 further includes the following sub-steps. Step S41: The RedCap multimode terminal checks the time slice resources of the measurement gap and discontinuous reception cycle configured in the current 4G network. If the effective duration of the time slice resources configured in the current 4G network meets the minimum duration for the RedCap multimode terminal to complete the downlink synchronization of the 5G cell, or pre-read SIB1, the RedCap multimode terminal attempts the downlink synchronization of the 5G cell within the configured time slice resources, or attempts to pre-read SIB1 of the 5G cell. If the effective duration of the time slice resources configured in the current 4G network does not meet the minimum duration for the RedCap multimode terminal to complete the downlink synchronization of the 5G cell, or pre-read SIB1, proceed to step S42. Step S42: The RedCap multimode terminal, based on the configured time slice resource, extends outward for a period of time at the front and / or rear of a certain cycle of the configured time slice resource to piece together a continuous specific time slice resource, the duration of which satisfies the minimum duration for the RedCap multimode terminal to complete the downlink synchronization of the 5G cell or pre-read SIB1; then the RedCap multimode terminal attempts the downlink synchronization of the 5G cell within the specific time slice resource, and attempts to pre-read the SIB1 of the 5G cell. If it is not possible to piece together a specific time slice resource that meets the conditions by expanding the configured time slice resource, proceed to step S43. Step S43: The RedCap multimode terminal selects a complete terminal-defined gap, the duration of which satisfies the minimum duration for the RedCap multimode terminal to complete the downlink synchronization of the 5G cell or pre-read SIB1; the RedCap multimode terminal attempts the downlink synchronization of the 5G cell within the terminal-defined gap, and attempts to pre-read the SIB1 of the 5G cell.

[0019] Further, in step S41, the RedCap multimode terminal attempts the downlink synchronization of the 5G cell within the configured complete time slice resource, and attempts to pre-read the SIB1 of the 5G cell after the downlink synchronization is successful. Alternatively, the RedCap multimode terminal attempts the downlink synchronization of the 5G cell within the configured time slice resource, and the RedCap multimode terminal attempts to pre-read the SIB1 of the 5G cell within another configured time slice resource; these two time slice resources are different periods of the measurement gap, or the idle period of different periods of the discontinuous reception period, or any combination of the measurement gap and the idle period of the discontinuous reception period.

[0020] Furthermore, in step S42, the RedCap multi-mode terminal takes the configured time slice resource as a basis, expands outward for a period of time at the front and / or back of a certain cycle of the configured time slice resource, and pieces together a continuous specific time slice resource, the duration of which satisfies the minimum duration for the RedCap multi-mode terminal to complete the downlink synchronization of the 5G cell and pre-read SIB1; then the RedCap multi-mode terminal attempts the downlink synchronization of the 5G cell within the specific time slice resource, and attempts to pre-read SIB1 of the 5G cell. Alternatively, the RedCap multi-mode terminal takes the configured time slice resource as a basis, expands outward for a period of time from the front and / or back of a certain cycle of the configured time slice resource, and pieces together a first continuous specific time slice resource, and expands outward for a period of time from the front and / or back of another cycle of the configured time slice resource, and pieces together a second continuous specific time slice resource. The duration of these two specific time slice resources meets the minimum duration for the RedCap multi-mode terminal to complete the downlink synchronization of the 5G cell or pre-read SIB1; then the RedCap multi-mode terminal attempts the downlink synchronization of the 5G cell within the first specific time slice resource, and the RedCap multi-mode terminal attempts to pre-read SIB1 of the 5G cell within the second specific time slice resource.

[0021] Further, in step S42, if the configured time slice resource is a measurement gap, the extension operation is to extend the duration of a certain period of the measurement gap forward and / or backward; if the configured time slice resource is a discontinuous reception period, the extension operation is to extend the duration of an idle period in a certain period of the discontinuous reception period forward and / or backward.

[0022] Furthermore, in step S43, the RedCap multimode terminal selects a complete terminal-defined gap, the duration of which satisfies the minimum duration for the RedCap multimode terminal to complete the downlink synchronization of the 5G cell and pre-read SIB1; the RedCap multimode terminal attempts the downlink synchronization of the 5G cell within the terminal-defined gap, and attempts to pre-read SIB1 of the 5G cell. Alternatively, the RedCap multimode terminal selects two complete terminal-defined gaps, the durations of which satisfy the minimum duration for the RedCap multimode terminal to complete the downlink synchronization of the 5G cell or pre-read SIB1; the RedCap multimode terminal attempts the downlink synchronization of the 5G cell within the first terminal-defined gap, and the RedCap multimode terminal attempts to pre-read SIB1 of the 5G cell within the second terminal-defined gap.

[0023] The present application also proposes a RedCap multimode terminal inter-system mobility management device, including a historical information recording unit, a historical information query unit, a measurement evaluation unit, an attempt pre-reading unit, a pre-reading success execution unit, and a pre-reading failure execution unit. The historical information recording unit is used to record the frequency, subcarrier spacing, and physical cell identifier of the 5G cell where the RedCap multimode terminal successfully resides or searches; if the RedCap multimode terminal successfully reads the SIB1 of the 5G cell where it successfully resides or searches, it further records the PLMN of the 5G cell, whether the 5G cell supports RedCap, and whether it can search for other accessible 5G neighboring cells in the same frequency band. The historical information query unit is used to measure the 5G cell when the RedCap multimode terminal measures a certain 5G cell, query the historical information; if the historical information records that the 5G cell supports RedCap, or the historical information does not record whether the 5G cell supports RedCap, it is transferred to the measurement evaluation unit for further processing; if the historical information records that the 5G cell does not support RedCap, the 5G non-RedCap cell will no longer participate in the measurement and evaluation. The measurement and evaluation unit is used by the RedCap multimode terminal to measure and evaluate the 5G cell; if the 5G cell is measured to not satisfy any current heterosystem measurement event, the RedCap multimode terminal does not trigger a measurement report; if the 5G cell is measured to satisfy a current heterosystem measurement event, and the historical information records that the 5G cell supports RedCap, the RedCap multimode terminal sends a heterosystem measurement report to the 4G network; if the 5G cell is measured to satisfy a current heterosystem measurement event, and the historical information does not record whether the 5G cell supports RedCap, it is transferred to the attempt pre-reading unit to continue processing. The attempt pre-reading unit is used by the RedCap multimode terminal to attempt early downlink synchronization of the 5G cell within the time slice resources of the measurement gap or non-continuous reception cycle configured in the current 4G network, or within the specific time slice resources of the configured time slice resources, or within the terminal-defined gap, and pre-read the SIB1 of the 5G cell; if the RedCap multimode terminal succeeds in downlink synchronization of the 5G cell and pre-reading the SIB1 of the 5G cell, it is transferred to the pre-reading success execution unit for further processing; if the RedCap multimode terminal fails in downlink synchronization of the 5G cell, or succeeds in downlink synchronization but fails to pre-read the SIB1 of the 5G cell, it is transferred to the pre-reading failure execution unit for further processing. The pre-reading success execution unit is used by the RedCap multimode terminal to determine whether the 5G NR cell supports RedCap according to the SIB1 information of the 5G cell; if the 5G cell supports RedCap, it is transferred to the measurement evaluation unit to continue measuring and evaluating the 5G cell; if the 5G cell does not support RedCap, the 5G non-RedCap cell no longer participates in measurement and evaluation.The pre-reading failure execution unit is used by the RedCap multi-mode terminal to compare the current 4G LTE service cell signal quality with the preset threshold of the RedCap multi-mode terminal; if the current 4G LTE service cell signal quality is less than the preset threshold of the RedCap multi-mode terminal, the RedCap multi-mode terminal sends the measurement report normally; if the current 4G LTE service cell signal quality is greater than or equal to the preset threshold of the RedCap multi-mode terminal, the RedCap multi-mode terminal does not send this measurement report.

[0024] The technical effect achieved by the present application is: the RedCap multi-mode terminal residing in the 4G cell fully utilizes, expands, or defines various time slice resources to attempt to perform downlink synchronization on the target 5G NR cell, and pre-reads SIB1 after downlink synchronization, so that the RedCap multi-mode terminal can determine in advance whether the target 5G NR cell supports RedCap. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 is a schematic diagram of the measurement gap.

[0026] Figure 2 It is a schematic diagram of the structure of a synchronization signal block (SSB).

[0027] Figure 3 It is a schematic diagram of three time-frequency resource multiplexing styles of SSB and CORESET0.

[0028] Figure 4 It is a schematic diagram of a discontinuous reception cycle.

[0029] Figure 5a and Figure 5b It is a flow chart of the inter-system mobility management method of the RedCap multi-mode terminal proposed in this application.

[0030] Figure 6 yes Figure 5a and Figure 5b Schematic diagram of the process of step S4 in .

[0031] Figure 7 It is a structural diagram of the heterogeneous system mobility management device of the RedCap multi-mode terminal proposed in this application.

[0032] Explanation of the reference numerals in the figure: historical information recording unit 1, historical information query unit 2, measurement and evaluation unit 3, attempt pre-reading unit 4, pre-reading success execution unit 5, pre-reading failure execution unit 6. DETAILED DESCRIPTION

[0033] In order to reduce costs and reduce the problem of inter-frequency interference, multi-mode mobile terminals usually use a single RF module for data transmission and signal measurement. In the connected state, in order to perform inter-frequency or inter-system measurements, the network usually configures some measurement gaps. Figure 1 In the measurement gap, the multi-mode mobile terminal does not send or receive any data in the current service cell (service frequency A), but only performs hetero-frequency or hetero-system measurements (frequency B), and then switches to the current service cell after the measurement gap ends.

[0034] In order to measure the 5G cell, the mobile terminal searches for the SSB (Synchronization Signal Block) according to the synchronization raster in the measurement gap. Figure 2 SSB is composed of three parts: primary synchronization signal (PSS), secondary synchronization signal (SSS), and PBCH (Physical Boardcast Channel). Figure 2 In the figure, the horizontal axis represents time (time domain), and the unit is OFDM symbol; the vertical axis represents frequency (frequency domain), and the unit is subcarrier (SC). OFDM stands for Orthogonal Frequency Division Multiplexing. PSS and SSS signals have fixed positions in time-frequency resources. By detecting PSS and SSS, the mobile terminal can obtain frame synchronization and symbol synchronization with the base station, and obtain information such as Physical Cell Identity (PCI). After successful synchronization, the mobile terminal can use the information provided by PSS and SSS to try to decode PBCH, and obtain MIB (Master Indication Block) and PBCH payload by decoding PBCH. These information contain the key parameters required to decode SIB1.

[0035] The mobile terminal uses the information in the MIB to obtain the search space of the PDCCH (Physical Downlink Control Channel) and finds the control resource set (CORESET0) for SIB1. Figure 3According to the time-frequency resource distribution of SSB and CORESET0, there are three multiplexing patterns of SSB and CORESET0. Pattern 1 is time division multiplexing. In this case, the frequency domain length of CORESET0 is always greater than that of SSB, and the frequency domain range of CORESET0 includes SSB. Patterns 2 and 3 are frequency division multiplexing (CORESET0 is in the same system frame as SSB). The difference between pattern 2 and pattern 3 is that in the time domain, CORESET0 of pattern 2 is ahead of SSB, but not far away (CORESET0 is in the previous time slot of SSB). CORESET0 of pattern 3 is in the same time slot of SSB. In the configured search space, the mobile terminal blindly detects the DCI (Downlink Control Information) format 1_0 that schedules SIB1. The mobile terminal uses the information provided in DCI 1_0 to find the time-frequency resource information of the PDSCH (Physical Downlink Shared Channel) carrying SIB1, and thus reads SIB1 from the PDSCH.

[0036] In the connected state, the mobile terminal does not always have data interaction with the network side. Usually, there is data transmission for a period of time, but no data transmission for a long period of time. When there is no data transmission, the mobile terminal does not need to monitor the PDCCH frame. Under the premise of ensuring that data can be transmitted effectively, the 4G LTE network introduces the discontinuous reception technology (DRX). Please refer to Figure 4 The DRX cycle consists of an on duration and an opportunity for DRX. During the on duration, the mobile terminal is awake and monitors the PDCCH. During the opportunity, the mobile terminal does not receive the PDCCH and enters sleep mode to reduce power consumption, but can receive data from other physical channels such as PDSCH.

[0037] When the RedCap multimode terminal resides in the 4G LTE network, if the RedCap multimode terminal detects a 5G NR cell, the RedCap multimode terminal does not know whether the 5G NR cell supports RedCap. The solution proposed in this application is: the RedCap multimode terminal uses various time slice resources to try to perform downlink synchronization on the target 5G NR cell and pre-read SIB1, so that the RedCap multimode terminal can judge in advance whether the target 5G NR cell supports RedCap, thereby avoiding the RedCap multimode terminal from being repeatedly switched or redirected to a 5G non-RedCap cell. The various time slice resources include: measurement gaps, idle periods in discontinuous reception cycles, extended spliced ​​time slices, a continuous terminal-defined gap (GAP), etc. The duration of the time slice resources must be able to meet the minimum duration for the mobile terminal to successfully complete the downlink synchronization of the target 5G NR cell, or successfully pre-read SIB1.

[0038] See also Figure 5a and Figure 5b The inter-system mobility management method of the RedCap multi-mode terminal proposed in this application includes the following steps.

[0039] Step S1: The RedCap multimode terminal records the frequency, sub-carrier spacing (SCS), physical cell identifier and other parameters of the 5G cell that has been successfully resided or searched. If the RedCap multimode terminal successfully reads the SIB1 of the 5G cell that has been successfully resided or searched, it further records the PLMN (Public land mobile network) of the 5G cell, whether the 5G cell supports RedCap, and whether other accessible 5G neighboring cells can be searched in the same frequency band. This information is stored in the RedCap multimode terminal as historical information.

[0040] Step S2: When the RedCap multimode terminal enters the connection state of the 4G network, the 4G network configures the 5G heterogeneous system measurement information through the RRC Connection Reconfiguration message. The 5G heterogeneous system measurement information includes 5G frequency, measurement gap, test report event, etc. The RedCap multimode terminal measures the 5G cell. When a certain 5G cell is measured, the RedCap multimode terminal first queries the historical information.

[0041] If the historical information records that the 5G cell supports RedCap, or the historical information does not record whether the 5G cell supports RedCap, the 5G cell continues to participate in the measurement and evaluation and proceeds to step S3.

[0042] If the historical information records that the 5G cell does not support RedCap, the 5G non-RedCap cell will no longer participate in the measurement and evaluation.

[0043] Step S3: The RedCap multi-mode terminal measures and evaluates the 5G cell.

[0044] If it is detected that the 5G cell does not meet any current inter-system measurement event (B1 event or B2 event), the RedCap multi-mode terminal maintains the current state (connection state of the 4G network) and does not trigger a measurement report.

[0045] If the 5G cell is detected to meet a certain current inter-system measurement event (B1 event or B2 event), and the historical information records that the 5G cell supports RedCap, the RedCap multimode terminal sends an inter-system measurement report to the 4G network to notify the 4G network that there is a better 5G Redcap target cell at this time. The 4G network usually instructs the RedCap multimode terminal to switch or redirect to the 5G RedCap target cell based on the B1 measurement event or B2 measurement event reported by the RedCap multimode terminal.

[0046] If it is measured that the 5G cell meets a current different system measurement event (B1 event or B2 event), and the historical information does not record whether the 5G cell supports RedCap, then go to step S4.

[0047] This step has three possible situations as mentioned above. In any case, the RedCap multimode terminal adds the information of the measured 5G cell (same as step S1) to the historical information or updates the original record in the historical information, especially recording whether the 5G cell supports RedCap.

[0048] Step S4: The RedCap multi-mode terminal attempts to synchronize downlink to the 5G cell in advance within the measurement gap or discontinuous reception cycle time slice resources configured in the current 4G network, or within the specific time slice resources extended and spliced ​​by the configured time slice resources, or within the terminal custom gap, and pre-reads the SIB1 of the 5G cell.

[0049] If the RedCap multi-mode terminal succeeds in downlink synchronization of the 5G cell and pre-reading SIB1 of the 5G cell, the process proceeds to step S5.

[0050] If the RedCap multimode terminal fails in downlink synchronization in the 5G cell, or succeeds in downlink synchronization but fails to pre-read SIB1 of the 5G cell, the process proceeds to step S6. Successful downlink synchronization is a prerequisite for pre-reading SIB1.

[0051] Step S5: The RedCap multimode terminal determines whether the 5G NR cell supports RedCap based on the SIB1 information of the 5G cell.

[0052] If the 5G cell supports RedCap, go to step S3 to continue measuring and evaluating the 5G cell.

[0053] If the 5G cell does not support RedCap, the 5G non-RedCap cell will no longer participate in the measurement and evaluation.

[0054] There are two possible situations in this step. In either case, the RedCap multimode terminal adds the information of the 5G cell (same as step S1) to the historical information or updates the original record in the historical information, especially recording whether the 5G cell supports RedCap.

[0055] Step S6: the RedCap multimode terminal compares the current 4G LTE serving cell signal quality with a preset threshold of the RedCap multimode terminal.

[0056] If the signal quality of the 4G LTE serving cell is less than the preset threshold of the RedCap multimode terminal at this time, the RedCap multimode terminal sends a measurement report normally. The RedCap multimode terminal sends a different system measurement report to the 4G network according to the existing communication protocol, notifying the 4G network that there is a better 5G Redcap target cell at this time. The 4G network usually instructs the RedCap multimode terminal to switch or redirect to the 5G RedCap target cell based on the B1 measurement event or B2 measurement event reported by the RedCap multimode terminal.

[0057] If the 4G LTE serving cell signal quality is greater than or equal to the preset threshold of the RedCap multimode terminal, the RedCap multimode terminal does not send this measurement report. The RedCap multimode terminal continues to maintain the current 4G LTE cell and continue the service.

[0058] The preset threshold of the RedCap multimode terminal can be determined based on an empirical value, mainly considering that the signal quality of the 4G LTE service cell should not be too low. If the signal quality of the 4G LTE service cell is too low, the RedCap multimode terminal may not be able to stay normally in the current 4G LTE service cell, affecting the continuity of the service of the RedCap multimode terminal.

[0059] See also Figure 6 , the step S4 further includes the following sub-steps.

[0060] Step S41: The RedCap multimode terminal checks the time slice resources of the measurement gap and discontinuous reception period configured in the current 4G network. The measurement gap and discontinuous reception period both appear periodically. Usually, the measurement gap must be configured. Only when the measurement gap is configured can the 5G cell be measured in the measurement phase.

[0061] If the effective duration of the time slice resources configured by the current 4G network (if it is a measurement gap, it is the duration of the measurement gap; if it is a discontinuous reception cycle, it is the duration of the idle period therein) meets the minimum duration for the RedCap multimode terminal to complete the downlink synchronization of the 5G cell or pre-read SIB1, then the RedCap multimode terminal attempts the downlink synchronization of the 5G cell within the configured time slice resources (if it is a measurement gap, it is the measurement gap; if it is a discontinuous reception cycle, it is the idle period therein), or attempts to pre-read the SIB1 of the 5G cell. For example, the RedCap multimode terminal attempts the downlink synchronization of the 5G cell within a complete configured time slice resource, and attempts to pre-read the SIB1 of the 5G cell after the downlink synchronization is successful. For another example, the RedCap multimode terminal attempts the downlink synchronization of the 5G cell within one configured time slice resource, and the RedCap multimode terminal attempts to pre-read the SIB1 of the 5G cell within another configured time slice resource. The two time slice resources may be different periods of the measurement gap, or idle periods of different periods of the discontinuous reception cycle, or any combination of the measurement gap and the idle period of the discontinuous reception cycle.

[0062] If the RedCap multi-mode terminal succeeds in downlink synchronization of the 5G cell and pre-reading SIB1 of the 5G cell, the process proceeds to step S5.

[0063] If the RedCap multi-mode terminal fails in downlink synchronization in the 5G cell, or succeeds in downlink synchronization but fails to pre-read SIB1 of the 5G cell, proceed to step S6.

[0064] If the effective duration of the time slice resources currently configured in the 4G network does not meet the minimum duration for the RedCap multi-mode terminal to complete the downlink synchronization of the 5G cell or pre-read SIB1, proceed to step S42.

[0065] Step S42: The RedCap multimode terminal uses the configured time slice resource (if it is a measurement gap, it is the measurement gap; if it is a discontinuous reception cycle, it is the idle period therein) as the basis, and extends forward for a period of time at the front of a certain cycle of the configured time slice resource, or extends backward for a period of time at the rear of a certain cycle of the configured time slice resource, or extends outward for a period of time at the front and rear of a certain cycle of the configured time slice resource at the same time, and a certain cycle of the configured time slice resource and the extended time period are pieced together to form a continuous specific time slice resource, and the duration of the specific time slice resource satisfies the RedCap multimode terminal to complete the downlink synchronization of the 5G cell and pre-read the minimum duration of SIB1. Then the RedCap multimode terminal attempts the downlink synchronization of the 5G cell within the specific time slice resource, and attempts to pre-read the SIB1 of the 5G cell.

[0066] Alternatively, the RedCap multimode terminal, based on the configured time slice resource, pieces together a first continuous specific time slice resource from a certain period of the configured time slice resource and a time period extending forward and / or backward, and pieces together a second continuous specific time slice resource from another period of the configured time slice resource and a time period extending forward and / or backward, and the duration of these two specific time slice resources satisfies the minimum duration for the RedCap multimode terminal to complete the downlink synchronization of the 5G cell or pre-read SIB1. Then the RedCap multimode terminal attempts the downlink synchronization of the 5G cell within the first specific time slice resource, and the RedCap multimode terminal attempts to pre-read SIB1 of the 5G cell within the second specific time slice resource.

[0067] If the configured time slice resource is a measurement gap, the above extension operation is to extend the duration of a certain period of the measurement gap forward and / or backward. If the configured time slice resource is a discontinuous reception period, the above extension operation is to extend the duration of an idle period in a certain period of the discontinuous reception period forward and / or backward.

[0068] If the RedCap multi-mode terminal succeeds in downlink synchronization of the 5G cell and pre-reading SIB1 of the 5G cell, the process proceeds to step S5.

[0069] If the RedCap multi-mode terminal fails in downlink synchronization in the 5G cell, or succeeds in downlink synchronization but fails to pre-read SIB1 of the 5G cell, proceed to step S6.

[0070] If it is not possible to expand the configured time slice resources to piece together a specific time slice resource that meets the conditions, then go to step S43.

[0071] Step S43: The RedCap multimode terminal selects a complete terminal-defined gap according to its own business load. The RedCap multimode terminal has no data transmission or only a small amount of data transmission in the terminal-defined gap. The duration of the terminal-defined gap satisfies the minimum duration for the RedCap multimode terminal to complete the downlink synchronization of the 5G cell and pre-read SIB1. The RedCap multimode terminal attempts the downlink synchronization of the 5G cell in the terminal-defined gap and attempts to pre-read SIB1 of the 5G cell.

[0072] Alternatively, the RedCap multimode terminal selects two complete terminal-defined gaps according to its own business load. During these two terminal-defined gaps, the RedCap multimode terminal has no data transmission, or only a small amount of data transmission, etc. The duration of these two terminal-defined gaps satisfies the minimum duration for the RedCap multimode terminal to complete the downlink synchronization of the 5G cell, or pre-read SIB1. The RedCap multimode terminal attempts the downlink synchronization of the 5G cell in the first terminal-defined gap, and the RedCap multimode terminal attempts to pre-read SIB1 of the 5G cell in the second terminal-defined gap.

[0073] If the RedCap multi-mode terminal succeeds in downlink synchronization of the 5G cell and pre-reading SIB1 of the 5G cell, the process proceeds to step S5.

[0074] If the RedCap multi-mode terminal fails in downlink synchronization in the 5G cell, or succeeds in downlink synchronization but fails to pre-read SIB1 of the 5G cell, proceed to step S6.

[0075] See also Figure 7 The inter-system mobility management device of the RedCap multi-mode terminal proposed in this application includes a history information recording unit 1, a history information query unit 2, a measurement and evaluation unit 3, an attempt pre-reading unit 4, a pre-reading success execution unit 5, and a pre-reading failure execution unit 6. Figure 7 The device shown corresponds to Figure 5a and Figure 5b The method shown.

[0076] The historical information recording unit 1 is used to record the frequency, subcarrier spacing, physical cell identification and other parameters of the 5G cell where the RedCap multimode terminal successfully resides or searches. If the RedCap multimode terminal successfully reads the SIB1 of the 5G cell where it successfully resides or searches, it further records the PLMN of the 5G cell, whether the 5G cell supports RedCap, and whether it can search for other accessible 5G neighboring cells in the same frequency band.

[0077] The historical information query unit 2 is used to query the historical information when the RedCap multimode terminal measures the 5G cell. If the historical information records that the 5G cell supports RedCap, or the historical information does not record whether the 5G cell supports RedCap, the 5G cell continues to participate in the measurement and evaluation, and transfers to the measurement and evaluation unit 3 for further processing. If the historical information records that the 5G cell does not support RedCap, the 5G non-RedCap cell no longer participates in the measurement and evaluation.

[0078] The measurement and evaluation unit 3 is used by the RedCap multimode terminal to measure and evaluate the 5G cell. If it is detected that the 5G cell does not satisfy any current heterosystem measurement event, the RedCap multimode terminal does not trigger a measurement report. If it is detected that the 5G cell satisfies a current heterosystem measurement event, and the historical information records that the 5G cell supports RedCap, the RedCap multimode terminal sends a heterosystem measurement report to the 4G network. If it is detected that the 5G cell satisfies a current heterosystem measurement event, and the historical information does not record whether the 5G cell supports RedCap, it goes to the attempt pre-reading unit 4 to continue processing.

[0079] The attempted pre-reading unit 4 is used by the RedCap multimode terminal to attempt early downlink synchronization of the 5G cell and pre-read the SIB1 of the 5G cell within the measurement gap or discontinuous reception cycle time slice resources configured in the current 4G network, or within the specific time slice resources extended and spliced ​​by the configured time slice resources, or within the terminal-defined gap. If the RedCap multimode terminal succeeds in downlink synchronization of the 5G cell and pre-reading of SIB1 of the 5G cell, it will proceed to the successful pre-reading execution unit 5 for further processing. If the RedCap multimode terminal fails in downlink synchronization of the 5G cell, or succeeds in downlink synchronization but fails to pre-read SIB1 of the 5G cell, it will proceed to the failed pre-reading execution unit 6 for further processing.

[0080] The pre-reading success execution unit 5 is used by the RedCap multimode terminal to determine whether the 5G NR cell supports RedCap according to the SIB1 information of the 5G cell. If the 5G cell supports RedCap, the measurement evaluation unit 3 is transferred to continue measuring and evaluating the 5G cell. If the 5G cell does not support RedCap, the 5G non-RedCap cell no longer participates in the measurement and evaluation.

[0081] The pre-reading failure execution unit 6 is used for the RedCap multimode terminal to compare the 4G LTE service cell signal quality at this time with the preset threshold of the RedCap multimode terminal. If the 4G LTE service cell signal quality at this time is less than the preset threshold of the RedCap multimode terminal, the RedCap multimode terminal sends the measurement report normally. If the 4G LTE service cell signal quality at this time is greater than or equal to the preset threshold of the RedCap multimode terminal, the RedCap multimode terminal does not send this measurement report.

[0082] This application attempts to pre-read the SIB1 information of the 5G cell by making full use of various time slice resources in the 4G LTE network, and predicts in advance whether the 5G cell supports RedCap, so as to reduce the probability of RedCap multi-mode terminals attempting to switch or redirect to 5G non-RedCap cells in 4G LTE.

[0083] The above are only preferred embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should all be included in the protection scope of the present application.

Claims

1. A RedCap multi-mode terminal inter-system mobility management method, characterized in that: The method comprises the following steps: Step S1: The RedCap multimode terminal records the frequency, subcarrier spacing, and physical cell identifier of the 5G cell that has been successfully resided or searched; if the RedCap multimode terminal successfully reads the SIB1 of the 5G cell that has been successfully resided or searched, it further records the PLMN of the 5G cell, whether the 5G cell supports RedCap, and whether other accessible 5G neighboring cells can be searched in the same frequency band; this information is stored in the RedCap multimode terminal as historical information; Step S2: When the RedCap multimode terminal enters the connection state of the 4G network, the 4G network configures 5G inter-system measurement information; the RedCap multimode terminal measures the 5G cell, and when a certain 5G cell is measured, the RedCap multimode terminal first queries historical information; If the historical information records that the 5G cell supports RedCap, or the historical information does not record whether the 5G cell supports RedCap, the 5G cell continues to participate in the measurement and evaluation, and proceeds to step S3; If the historical information records that the 5G cell does not support RedCap, the 5G non-RedCap cell will no longer participate in the measurement and evaluation; Step S3: the RedCap multimode terminal measures and evaluates the 5G cell; If it is detected that the 5G cell does not satisfy any current heterogeneous system measurement event, the RedCap multimode terminal does not trigger a measurement report; If it is detected that the 5G cell meets a current heterogeneous system measurement event, and the historical information records that the 5G cell supports RedCap, the RedCap multimode terminal sends a heterogeneous system measurement report to the 4G network; If it is detected that the 5G cell meets a current heterogeneous system measurement event, and the historical information does not record whether the 5G cell supports RedCap, proceed to step S4; Step S4: The RedCap multimode terminal attempts to synchronize downlink to the 5G cell in advance within the measurement gap or discontinuous reception cycle time slice resources configured in the current 4G network, or within the specific time slice resources spliced ​​by extending the configured time slice resources, or within the terminal-defined gap, and pre-reads the SIB1 of the 5G cell; If the RedCap multi-mode terminal is successfully synchronized with the downlink of the 5G cell and pre-reads the SIB1 of the 5G cell, the process proceeds to step S5; If the RedCap multimode terminal fails in downlink synchronization in the 5G cell, or succeeds in downlink synchronization but fails to pre-read SIB1 of the 5G cell, proceed to step S6; Step S5: The RedCap multimode terminal determines whether the 5G NR cell supports RedCap according to the SIB1 information of the 5G cell; If the 5G cell supports RedCap, proceed to step S3 to continue measuring and evaluating the 5G cell; If the 5G cell does not support RedCap, the 5G non-RedCap cell will no longer participate in the measurement and evaluation; Step S6: the RedCap multimode terminal compares the signal quality of the 4G LTE serving cell at this time with the preset threshold of the RedCap multimode terminal; If the 4G LTE serving cell signal quality is less than the preset threshold of the RedCap multi-mode terminal at this time, the RedCap multi-mode terminal sends the measurement report normally; If the 4G LTE serving cell signal quality is greater than or equal to the preset threshold of the RedCap multi-mode terminal at this time, the RedCap multi-mode terminal does not send this measurement report.

2. The RedCap multi-mode terminal inter-system mobility management method according to claim 1, characterized in that: After step S2 is executed, no matter which situation is, the RedCap multi-mode terminal will add the measured information of the 5G cell to the historical information or update the original record in the historical information.

3. The RedCap multi-mode terminal inter-system mobility management method according to claim 1, characterized in that: After step S5 is executed, no matter which case, the RedCap multi-mode terminal adds the information of the 5G cell to the historical information or updates the original record in the historical information.

4. The RedCap multi-mode terminal inter-system mobility management method according to claim 1, characterized in that: In step S4, successful downlink synchronization is a prerequisite for pre-reading SIB1.

5. The RedCap multi-mode terminal inter-system mobility management method according to claim 1, characterized in that: The step S4 further includes the following sub-steps: Step S41: the RedCap multimode terminal checks the measurement gaps and time slice resources of the discontinuous reception cycle configured in the current 4G network; If the effective duration of the time slice resources configured by the current 4G network meets the minimum duration for the RedCap multimode terminal to complete the downlink synchronization of the 5G cell or pre-read SIB1, the RedCap multimode terminal attempts the downlink synchronization of the 5G cell within the configured time slice resources, or attempts to pre-read SIB1 of the 5G cell; If the effective duration of the time slice resources currently configured by the 4G network does not meet the minimum duration for the RedCap multi-mode terminal to complete the downlink synchronization of the 5G cell or pre-read SIB1, proceed to step S42; Step S42: The RedCap multimode terminal, based on the configured time slice resource, extends outward for a period of time at the front and / or rear of a certain cycle of the configured time slice resource to piece together a continuous specific time slice resource, the duration of which satisfies the minimum duration for the RedCap multimode terminal to complete the downlink synchronization of the 5G cell or pre-read SIB1; then the RedCap multimode terminal attempts the downlink synchronization of the 5G cell within the specific time slice resource, and attempts to pre-read SIB1 of the 5G cell; If it is not possible to expand the configured time slice resources to piece together a specific time slice resource that meets the conditions, then proceed to step S43; Step S43: The RedCap multimode terminal selects a complete terminal-customized gap, the duration of which satisfies the minimum duration for the RedCap multimode terminal to complete the downlink synchronization of the 5G cell or pre-read SIB1; the RedCap multimode terminal attempts the downlink synchronization of the 5G cell within the terminal-customized gap, and attempts to pre-read SIB1 of the 5G cell.

6. The RedCap multi-mode terminal inter-system mobility management method according to claim 5, characterized in that: In the step S41, the RedCap multimode terminal attempts downlink synchronization of the 5G cell within the configured complete time slice resource, and attempts to pre-read SIB1 of the 5G cell after the downlink synchronization is successful; Alternatively, the RedCap multimode terminal attempts the downlink synchronization of the 5G cell within one of the configured time slice resources, and the RedCap multimode terminal attempts to pre-read the SIB1 of the 5G cell within another configured time slice resource; these two time slice resources are different periods of the measurement gap, or idle periods of different periods of the discontinuous reception period, or any combination of the measurement gap and the idle period of the discontinuous reception period.

7. The inter-system mobility management method of RedCap multi-mode terminal according to claim 5, characterized in that: In the step S42, the RedCap multimode terminal, based on the configured time slice resource, extends outward for a period of time at the front and / or rear of a certain cycle of the configured time slice resource to piece together a continuous specific time slice resource, the duration of the specific time slice resource satisfies the minimum duration for the RedCap multimode terminal to complete the downlink synchronization of the 5G cell and pre-read SIB1; then the RedCap multimode terminal attempts the downlink synchronization of the 5G cell within the specific time slice resource, and attempts to pre-read SIB1 of the 5G cell; Alternatively, the RedCap multi-mode terminal takes the configured time slice resource as a basis, expands outward for a period of time from the front and / or back of a certain cycle of the configured time slice resource, and pieces together a first continuous specific time slice resource, and expands outward for a period of time from the front and / or back of another cycle of the configured time slice resource, and pieces together a second continuous specific time slice resource. The duration of these two specific time slice resources meets the minimum duration for the RedCap multi-mode terminal to complete the downlink synchronization of the 5G cell or pre-read SIB1; then the RedCap multi-mode terminal attempts the downlink synchronization of the 5G cell within the first specific time slice resource, and the RedCap multi-mode terminal attempts to pre-read SIB1 of the 5G cell within the second specific time slice resource.

8. The RedCap multi-mode terminal inter-system mobility management method according to claim 5, characterized in that: In step S42, if the configured time slice resource is a measurement gap, the extension operation is to extend the duration of a certain period of the measurement gap forward and / or backward; if the configured time slice resource is a discontinuous reception period, the extension operation is to extend the duration of an idle period in a certain period of the discontinuous reception period forward and / or backward.

9. The RedCap multi-mode terminal inter-system mobility management method according to claim 5, characterized in that: In the step S43, the RedCap multimode terminal selects a complete terminal-defined gap, the duration of which satisfies the minimum duration for the RedCap multimode terminal to complete the downlink synchronization of the 5G cell and pre-read SIB1; the RedCap multimode terminal attempts the downlink synchronization of the 5G cell within the terminal-defined gap, and attempts to pre-read SIB1 of the 5G cell; Alternatively, the RedCap multimode terminal selects two complete terminal-customized gaps, and the duration of these two terminal-customized gaps satisfies the minimum duration for the RedCap multimode terminal to complete the downlink synchronization of the 5G cell or pre-read SIB1; the RedCap multimode terminal attempts the downlink synchronization of the 5G cell in the first terminal-customized gap, and the RedCap multimode terminal attempts to pre-read SIB1 of the 5G cell in the second terminal-customized gap.

10. A RedCap multi-mode terminal inter-system mobility management device, characterized in that: It includes a history information recording unit, a history information query unit, a measurement and evaluation unit, an attempt pre-reading unit, a pre-reading success execution unit, and a pre-reading failure execution unit; The historical information recording unit is used to record the frequency, subcarrier spacing, and physical cell identifier of the 5G cell where the RedCap multimode terminal successfully resides or searches; if the RedCap multimode terminal successfully reads the SIB1 of the 5G cell where it successfully resides or searches, it further records the PLMN of the 5G cell, whether the 5G cell supports RedCap, and whether other accessible 5G neighboring cells can be searched in the same frequency band; The historical information query unit is used to query the historical information when the RedCap multi-mode terminal measures the 5G cell. If the historical information records that the 5G cell supports RedCap, or the historical information does not record whether the 5G cell supports RedCap, the measurement and evaluation unit is transferred to continue processing; if the historical information records that the 5G cell does not support RedCap, the 5G non-RedCap cell will no longer participate in the measurement and evaluation; The measurement and evaluation unit is used for the RedCap multimode terminal to measure and evaluate the 5G cell; if it is measured that the 5G cell does not satisfy any current heterosystem measurement event, the RedCap multimode terminal does not trigger a measurement report; if it is measured that the 5G cell satisfies a current heterosystem measurement event, and the historical information records that the 5G cell supports RedCap, the RedCap multimode terminal sends a heterosystem measurement report to the 4G network; if it is measured that the 5G cell satisfies a current heterosystem measurement event, and the historical information does not record whether the 5G cell supports RedCap, it is transferred to the attempt pre-reading unit to continue processing; The attempted pre-reading unit is used for the RedCap multi-mode terminal to attempt early downlink synchronization of the 5G cell and pre-read the SIB1 of the 5G cell within the measurement gap or discontinuous reception cycle time slice resources configured in the current 4G network, or within the specific time slice resources extended and spliced ​​by the configured time slice resources, or within the terminal-defined gap; if the RedCap multi-mode terminal succeeds in the downlink synchronization of the 5G cell and the pre-reading of the SIB1 of the 5G cell, the processing is transferred to the successful pre-reading execution unit; if the RedCap multi-mode terminal fails in the downlink synchronization of the 5G cell, or succeeds in the downlink synchronization but fails to pre-read the SIB1 of the 5G cell, the processing is transferred to the failed pre-reading execution unit; The pre-reading success execution unit is used by the RedCap multi-mode terminal to determine whether the 5G NR cell supports RedCap according to the SIB1 information of the 5G cell; if the 5G cell supports RedCap, the measurement and evaluation unit is transferred to continue to measure and evaluate the 5G cell; if the 5G cell does not support RedCap, the 5G non-RedCap cell no longer participates in the measurement and evaluation; The pre-reading failure execution unit is used for the RedCap multi-mode terminal to compare the current 4G LTE serving cell signal quality with the preset threshold of the RedCap multi-mode terminal; If the 4G LTE serving cell signal quality is less than the preset threshold of the RedCap multi-mode terminal at this time, the RedCap multi-mode terminal sends the measurement report normally; If the 4G LTE serving cell signal quality is greater than or equal to the preset threshold of the RedCap multi-mode terminal at this time, the RedCap multi-mode terminal does not send this measurement report.

Images