Indication method, device, equipment and readable storage medium

Abstract

The present application discloses an indication method, apparatus, device and readable storage medium, the method comprising: sending a first message to a network side, the first message indicating that the terminal stores one or more first reports, the first report being related to a secondary node. In an embodiment of the present application, after receiving the first message, the network side can learn about the situation of the reports related to the secondary node stored inside the terminal, so that the network side can further initiate a message to the terminal requesting to obtain the report, and finally obtain the report on the terminal side, and optimize the communication system parameters by analyzing the information in the report.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to an indication method, device, equipment and readable storage medium. Background Art

[0002] The current mechanism only allows the Master Node (MN) and the terminal to interact with each other, that is, the network side can only obtain reports related to the terminal and the MN, but cannot obtain various reports from any terminal on the SgNB side in the Multi-RAT Dual Connectivity (MR-DC) state. If the network side cannot obtain the terminal's report at the SgNB, it will not be able to optimize the network side based on this information. Summary of the invention

[0003] The purpose of the embodiments of the present application is to provide an indication method, apparatus, device and readable storage medium to solve the problem that the network side cannot obtain the report of the terminal at the auxiliary node.

[0004] In a first aspect, an indication method is provided, which is executed by a terminal and includes:

[0005] A first message is sent to a network side, where the first message indicates that the terminal stores one or more first reports, where the first reports are related to the secondary node.

[0006] In a second aspect, an indication method is provided, which is performed by a network side device and includes:

[0007] A first message is received, the first message indicating that the terminal has one or more first reports stored, the first reports being related to a secondary node.

[0008] In a third aspect, an indication device is provided, which is applied to a terminal, and includes:

[0009] The first sending module is used to send a first message to the network side, where the first message indicates that the terminal stores one or more first reports, and the first report is related to the secondary node.

[0010] In a fourth aspect, an indication device is provided, which is applied to a network side device, including:

[0011] The second receiving module is configured to receive a first message, where the first message indicates that the terminal stores one or more first reports, and the first reports are related to the secondary node.

[0012] In a fifth aspect, a terminal is provided, comprising: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method described in the first aspect.

[0013] In a sixth aspect, a network side device is provided, comprising: a processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, the steps of the method described in the second aspect are implemented.

[0014] In a seventh aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect or the second aspect are implemented.

[0015] According to an eighth aspect, a program product is provided. The program product is stored in a non-volatile storage medium and is executed by at least one processor to implement the steps of the processing method as described in the first aspect or the second aspect.

[0016] In a ninth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the processing method described in the first aspect or the second aspect.

[0017] In an embodiment of the present application, after receiving the first message, the network side can learn about the report related to the auxiliary node stored inside the terminal, so that the network side can further initiate a message to the terminal requesting to obtain the report, and finally obtain the report from the terminal side, and optimize the communication system parameters by analyzing the reported information. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 It is a flow chart of an existing terminal sending a report to a network side;

[0019] Figure 2 is a block diagram of a wireless communication system to which the embodiments of the present application can be applied;

[0020] Figure 3 It is one of the flow charts of the indication method of the embodiment of the present application;

[0021] Figure 4 This is the second flowchart of the indication method of the embodiment of the present application;

[0022] Figure 5 is one of the schematic diagrams of the indicating device of the embodiment of the present application;

[0023] Figure 6 This is the second schematic diagram of the indicating device of the embodiment of the present application;

[0024] Figure 7 is a schematic diagram of a terminal according to an embodiment of the present application;

[0025] Figure 8It is a schematic diagram of a network side device of an embodiment of the present application. DETAILED DESCRIPTION

[0026] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0027] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specified order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first" and "second" are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more. In addition, the "and" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0028] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies. However, the following description describes a New Radio (NR) system for illustrative purposes, and the NR terminology is used in most of the following descriptions, although these technologies can also be applied to applications other than NR system applications, such as the 6th generation (6 th Generation, 6G) communication system.

[0029] In order to facilitate understanding of the embodiments of the present application, the following technical points are first introduced below:

[0030] 1. The process of the terminal sending a report to the network side:

[0031] The terminal can perform a series of reported measurements in the idle / inactive state, some of which are shown below:

[0032] (1) Random Access Channel (RACH) report;

[0033] (2) Minimization of drive tests (MDT) logged measurement information (if the network has configured the UE);

[0034] (3) Connection failure report (connEstFailReport);

[0035] (4) Radio Link Failure (RLF) report (rlf-Report);

[0036] (5) Mobility history information report (mobilityHistoryReport).

[0037] When the terminal enters the connected state from the idle state, if there are reports on the terminal side that have not been reported to the network side before, the availability indicator corresponding to each report will be sent to the network side ( Figure 1 Step a); if there is a "connection failure report" and an RLF report on the terminal side, the terminal will send a message to the network side when entering the connected state, and the message carries an indication field indicating the availability of connection establishment failure information (connEstFailInfoAvailable) and RLF information availability (rlf-InfoAvailable).

[0038] After receiving the message, the network side sends a request message to the terminal to obtain the report according to its own needs ( Figure 1 Step b), the message may only request reports from some terminals;

[0039] For example, when the terminal indicates to the network that it has an RLF report and a connection failure report, the network can independently choose whether to obtain the report or which report to obtain, such as only carrying a request for an RLF report (rlf-ReportReq) in the message or not sending the message (i.e., not requesting any report).

[0040] After receiving the request message from the network side, the terminal sends the corresponding report to the network ( Figure 1 Step c).

[0041] 2. About availability indication:

[0042] Currently, the messages that can carry report existence indication include: RRC Setup Complete (RRCSetupComplete) / RRC Recovery Complete (RRCResumeComplete) / RRC Reconfiguration Complete (RRCReconfigurationComplete) / RRC Reestablishment Complete (RRCReestablishmentComplete) (Type A messages) and Terminal Information Response (UEInformationResponse) (Type B messages).

[0043] It should be noted that Class A messages are used to initially indicate the existence of terminal-side reports, while Class B messages (UEInformationResponse) are used after the initial indication to notify the network side whether there are any reports that have not been fully sent. For example, when an RLF report exists, the terminal will send any of the Class A messages to the network side when entering the connected state, and carry rlf-InfoAvailable in the message to inform the network side that the UE has an RLF report. When the network side initiates a request for the RLF report and the terminal fails to send all the contents of the report (for example, the report data volume is too large to be sent at one time), the terminal will carry rlf-InfoAvailable in the UEInformationResponse that sends the RLF report to inform the network that there are still RLF reports that have not been obtained on the terminal side.

[0044] Currently, this indication can only be used to indicate terminal-side reports on a master node (MN), and there is no mechanism to indicate reports on a secondary node (SN).

[0045] 3. About the terminal information request (UEInformationRequest) message:

[0046] This message is used by the network side to request the terminal to obtain corresponding information, such as requesting the terminal to send idle mode measurement (idle mode measurement), recorded measurement report (logged measurement report), connection establishment failure report (connection establishment failure report), RACH report, etc.

[0047] 4. About the terminal information response (UEInformationResponse) message:

[0048] This message is used by the terminal to send relevant information previously requested by the network to the network. For example, when ra-ReportReq-r16 in UEInformationRequest is set to 'true', the terminal will include ra-ReportList-r16 in the UEInformationResponse message and send it to the network.

[0049] This message can only be used to deliver MN related reports. It can be sent using signalling radio bearers (SRB) 1 and SRB2. SRB2 is used when logged measurement information is included in this message.

[0050] Figure 2A block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 21, a network side device 22 and a network side device 23. Among them, the terminal 21 can also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 21 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), a wearable device (WearableDevice) or a vehicle-mounted device (VUE), a pedestrian terminal (PUE) and other terminal side devices, and the wearable device includes: a bracelet, a headset, glasses, etc. It should be noted that the specific type of the terminal 21 is not limited in the embodiment of the present application. The network side device 22 and the network side device 23 can be a base station or a core network, wherein the base station can be referred to as a node B, an evolved node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a B node, an evolved B node (eNB), a home B node, a home evolved B node, a WLAN access point, a WiFi node, a transmitting and receiving point (Transmitting Receiving Point, TRP) or some other suitable term in the field. As long as the same technical effect is achieved, the base station is not limited to the specified technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is taken as an example, but the specific type of the base station is not limited.

[0051] The following, in conjunction with the accompanying drawings, describes in detail the indication method, device and readable storage medium provided in the embodiments of the present application through specific embodiments and their application scenarios.

[0052] See also Figure 3 , an embodiment of the present application provides an indication method, which is executed by a terminal, specifically step 301.

[0053] Step 301: Send a first message (eg, an RRC message) to the network side, wherein the first message indicates that the terminal stores one or more first reports, and the first report is related to the secondary node (SgNB).

[0054] In the embodiments of the present application, Figure 3 The method shown also includes: receiving a message sent by the network side requesting to obtain a report; and sending one or more of the first reports to the network side according to the message requesting to obtain a report.

[0055] For example, the terminal can report at least part of one or more stored reports to the network side according to the message requesting the report. For example, the terminal reports multiple first reports at the same time, including: RACH report, RLF report, LoggedMDT report, etc., but of course not limited to this.

[0056] In this embodiment of the present application, the first message carries an availability indicator corresponding to the first report.

[0057] In this embodiment of the present application, when the primary node to which the terminal is connected is a base station in a new radio (NR) system, that is, the MN to which the terminal is connected is a gNB, the first message is at least one of the following:

[0058] (1) Radio resource control setup completion message (e.g., RRCSetupComplete);

[0059] (2) Radio resource control recovery complete message (e.g., RRCResumeComplete);

[0060] (3) Radio resource control reconfiguration complete message (e.g., RRCReconfigurationComplete);

[0061] (4) Radio resource control reestablishment completion message (e.g., RRCReestablishmentComplete);

[0062] (5) Terminal information response message (e.g., UEInformationResponse).

[0063] In the embodiment of the present application, when the primary node to which the terminal is connected is a base station in a Long Term Evolution (LTE) system, that is, the MN to which the terminal is connected is an eNB, the first message is at least one of the following:

[0064] (1) Radio resource control connection setup complete message (e.g., RRCConnectionSetupComplete);

[0065] (2) Radio resource control connection resumption complete message (e.g., RRCConnectionResumeComplete);

[0066] (3) Radio resource control connection reconfiguration complete message (e.g., RRCConnectionReconfigurationComplete);

[0067] (4) Radio resource control connection reestablishment completion message (e.g., RRCConnectionReestablishmentComplete).

[0068] (5) Terminal information response message (e.g., UEInformationResponse).

[0069] In this embodiment of the present application, the presence indication includes at least one of the following:

[0070] (1) There is an identifier of a random access report for accessing a secondary cell group (e.g., rach-InfoAvailableSCG), indicating that there is a random access report (RACH report) as a SN node in the MR-DC state, including at least one of the following: two-step (2-step) and four-step (4-step) RACH reports; or two separate indicators are used to indicate 2-step and 4-step RACH respectively, such as 2steprach-InfoAvailableSCG and 4steprach-InfoAvailableSCG;

[0071] (2) The presence of a secondary cell group minimization of drive test log measurement report indicator (e.g., logMeasAvailableSCG): indicates the presence of MDT logged measurement information of the SN node in the MR-DC state;

[0072] (3) The existence of a Bluetooth measurement report for minimization of drive test records of a secondary cell group (e.g., logMeasAvailableBTSCG): indicates the existence of MDT logged Bluetooth measurement information of the SN node in the MR-DC state;

[0073] (4) The presence of a secondary cell group minimization of drive test log WLAN measurement report flag (e.g., logMeasAvailableWLANSCG): indicates the presence of MDT logged WLAN measurement information of the SN node in the MR-DC state;

[0074] (5) An identifier indicating the existence of a secondary cell group connection establishment failure report (e.g., connEstFailInfoAvailableSCG): indicating the existence of a connection failure report as an SN node in the MR-DC state;

[0075] (6) An identifier indicating the existence of a radio link failure report of a secondary cell group (e.g., rlf-InfoAvailableSCG): indicating the existence of a radio link failure (RLF) report of the SN node in the MR-DC state;

[0076] (7) An identifier indicating the existence of a mobility history information report of a secondary cell group (eg, mobilityHistoryReportAvailableSCG): indicates the existence of a mobility history information report of the SN node in the MR-DC state.

[0077] In the embodiment of the present application, the existence indication is obtained by reusing the existing reporting indication mechanism between the terminal and the master node.

[0078] In this embodiment of the present application, if the terminal establishes a connection with the secondary node, the first message is at least one of the following:

[0079] (1) Radio resource control establishment complete message;

[0080] (2) Radio resource control recovery complete message;

[0081] (3) Radio resource control reconfiguration complete message;

[0082] (4) Radio resource control re-establishment complete message;

[0083] (5) Radio resource control connection establishment completion message;

[0084] (6) Radio resource control connection recovery complete message;

[0085] (7) Radio resource control connection reconfiguration complete message;

[0086] (8) Radio resource control connection re-establishment completion message;

[0087] (9) Terminal information response message.

[0088] Further, optionally, in step 301, the terminal sends a first message carrying an existence indication corresponding to the first report to the secondary node through the primary node. For example, the first message can be carried in an uplink information transmission (for example, UL information transfer for MR-DC) message for dual connection, that is, the terminal can carry the RRC message sent to the SN in the UL information transfer for MR-DC and send it to the MN; after receiving it, the MN forwards the RRC message to be sent to the SN to the SN.

[0089] Further, optionally, the presence indication includes at least one of the following:

[0090] (1) The presence of a random access report indicator (e.g., rach-InfoAvailable): indicates the presence of a RACH report as a SN node in the MR-DC state, including at least one of the following: 2-step, 4-step RACH reports; or using two separate indicators to indicate 2-step and 4-step RACH respectively, such as 2steprach-InfoAvailableSCG and 4steprach-InfoAvailableSCG;

[0091] (2) The presence of a minimized drive test log measurement report flag (e.g., logMeasAvailable): indicates the presence of MDT logged measurement information of the SN node in the MR-DC state;

[0092] (3) The existence of a Bluetooth measurement report for minimized drive test logging (e.g., logMeasAvailableBT): indicates the existence of MDT logged Bluetooth measurement information of the SN node in the MR-DC state;

[0093] (4) The presence of a minimized drive test log wireless LAN measurement report flag (e.g., logMeasAvailableWLAN): indicates the presence of MDT logged WLAN measurement information as a SN node in the MR-DC state;

[0094] (5) An identifier indicating the existence of a connection establishment failure report (e.g., connEstFailInfoAvailable): indicating the existence of a connection failure report as an SN node in the MR-DC state;

[0095] (6) An indication of the existence of a radio link failure report (e.g., rlf-InfoAvailable): indicating the existence of an RLF report of the SN node in the MR-DC state;

[0096] (7) An indicator indicating the presence of a mobility history information report (eg, mobilityHistoryReportAvailable): indicates the presence of a mobility history information report of the SN node in the MR-DC state.

[0097] In an embodiment of the present application, after receiving the first message, the network side can learn about the report related to the auxiliary node stored inside the terminal, so that the network side can further initiate a message to the terminal requesting to obtain the report, and finally obtain the report from the terminal side, and optimize the communication system parameters by analyzing the reported information.

[0098] See also Figure 4 , an embodiment of the present application provides an indication method, which is executed by a network side device, and the specific steps include: step 401.

[0099] Step 401: Receive a first message, where the first message indicates that a terminal stores one or more first reports, where the first reports are related to a secondary node.

[0100] In the embodiments of the present application, Figure 4 The method shown also includes: sending a message requesting to obtain a report according to the first message; and receiving one or more first reports sent by the terminal.

[0101] For example, the multiple first reports reported by the receiving terminal at the same time include: RACH report, RLF report, Logged MDT report, etc., of course, not limited to this.

[0102] In this embodiment of the present application, the first message carries an existence indication corresponding to the first report.

[0103] In this embodiment of the present application, when the primary node to which the terminal is connected is a base station in a new radio (NR) system, that is, the MN to which the terminal is connected is a gNB, the first message is at least one of the following:

[0104] (1) Radio resource control setup completion message (e.g., RRCSetupComplete);

[0105] (2) Radio resource control recovery complete message (e.g., RRCResumeComplete);

[0106] (3) Radio resource control reconfiguration complete message (e.g., RRCReconfigurationComplete);

[0107] (4) Radio resource control reestablishment completion message (e.g., RRCReestablishmentComplete);

[0108] (5) Terminal information response message (e.g., UEInformationResponse).

[0109] In the embodiment of the present application, when the primary node to which the terminal is connected is a base station in the LTE system, that is, the MN to which the terminal is connected is an eNB, the first message is at least one of the following:

[0110] (1) Radio resource control connection setup complete message (e.g., RRCConnectionSetupComplete);

[0111] (2) Radio resource control connection resumption complete message (e.g., RRCConnectionResumeComplete);

[0112] (3) Radio resource control connection reconfiguration complete message (e.g., RRCConnectionReconfigurationComplete);

[0113] (4) Radio resource control connection reestablishment completion message (e.g., RRCConnectionReestablishmentComplete).

[0114] (5) Terminal information response message (e.g., UEInformationResponse).

[0115] In this embodiment of the present application, the presence indication includes at least one of the following:

[0116] (1) There is an identifier of a random access report for accessing a secondary cell group (e.g., rach-InfoAvailableSCG), indicating that there is a random access report (RACH report) as a SN node in the MR-DC state, including at least one of the following: two-step (2-step) and four-step (4-step) RACH reports; or two separate indicators are used to indicate 2-step and 4-step RACH respectively, such as 2steprach-InfoAvailableSCG and 4steprach-InfoAvailableSCG;

[0117] (2) The presence of a secondary cell group minimization of drive test log measurement report indicator (e.g., logMeasAvailableSCG): indicates the presence of MDT logged measurement information of the SN node in the MR-DC state;

[0118] (3) The existence of a Bluetooth measurement report for minimization of drive test records of a secondary cell group (e.g., logMeasAvailableBTSCG): indicates the existence of MDT logged Bluetooth measurement information of the SN node in the MR-DC state;

[0119] (4) The presence of a secondary cell group minimization of drive test log WLAN measurement report flag (e.g., logMeasAvailableWLANSCG): indicates the presence of MDT logged WLAN measurement information of the SN node in the MR-DC state;

[0120] (5) An identifier indicating the existence of a secondary cell group connection establishment failure report (e.g., connEstFailInfoAvailableSCG): indicating the existence of a connection failure report as an SN node in the MR-DC state;

[0121] (6) An identifier indicating the existence of a radio link failure report of a secondary cell group (e.g., rlf-InfoAvailableSCG): indicating the existence of a radio link failure (RLF) report of the SN node in the MR-DC state;

[0122] (7) An identifier indicating the existence of a mobility history information report of a secondary cell group (eg, mobilityHistoryReportAvailableSCG): indicates the existence of a mobility history information report of the SN node in the MR-DC state.

[0123] In the embodiment of the present application, the existence indication is obtained by reusing the existing reporting indication mechanism between the terminal and the master node.

[0124] In this embodiment of the present application, if the terminal establishes a connection with the secondary node, the first message is at least one of the following:

[0125] (1) Radio resource control establishment complete message;

[0126] (2) Radio resource control recovery complete message;

[0127] (3) Radio resource control reconfiguration complete message;

[0128] (4) Radio resource control re-establishment complete message;

[0129] (5) Radio resource control connection establishment completion message;

[0130] (6) Radio resource control connection recovery complete message;

[0131] (7) Radio resource control connection reconfiguration complete message;

[0132] (8) Radio resource control connection re-establishment completion message;

[0133] (9) Terminal information response message.

[0134] Further, optionally, in step 401, the secondary node receives, through the primary node, a first message carrying an existence indication corresponding to the first report, for example, the first message is carried in an uplink information transmission (eg, UL information transfer for MR-DC) message for dual connectivity.

[0135] Further, optionally, the presence indication includes at least one of the following:

[0136] (1) The presence of a random access report indicator (e.g., rach-InfoAvailable): indicates the presence of a RACH report as a SN node in the MR-DC state, including at least one of the following: 2-step, 4-step RACH reports; or using two separate indicators to indicate 2-step and 4-step RACH respectively, such as 2steprach-InfoAvailableSCG and 4steprach-InfoAvailableSCG;

[0137] (2) The presence of a minimized drive test log measurement report flag (e.g., logMeasAvailable): indicates the presence of MDT logged measurement information of the SN node in the MR-DC state;

[0138] (3) The existence of a Bluetooth measurement report for minimized drive test logging (e.g., logMeasAvailableBT): indicates the existence of MDT logged Bluetooth measurement information of the SN node in the MR-DC state;

[0139] (4) The presence of a minimized drive test log wireless LAN measurement report flag (e.g., logMeasAvailableWLAN): indicates the presence of MDT logged WLAN measurement information as a SN node in the MR-DC state;

[0140] (5) An identifier indicating the existence of a connection establishment failure report (e.g., connEstFailInfoAvailable): indicating the existence of a connection failure report as an SN node in the MR-DC state;

[0141] (6) An indication of the existence of a radio link failure report (e.g., rlf-InfoAvailable): indicating the existence of an RLF report of the SN node in the MR-DC state;

[0142] (7) An indicator indicating the presence of a mobility history information report (eg, mobilityHistoryReportAvailable): indicates the presence of a mobility history information report of the SN node in the MR-DC state.

[0143] In an embodiment of the present application, after receiving the first message, the network side can learn about the report related to the auxiliary node stored inside the terminal, so that the network side can further initiate a message to the terminal requesting to obtain the report, and finally obtain the report from the terminal side, and optimize the communication system parameters by analyzing the reported information.

[0144] The implementation of the present application is described below in conjunction with Example 1 and Example 2.

[0145] Embodiment 1: Acquisition of SN logged MDT measurement report (reported before UE restores MR-DC).

[0146] Step 1: The UE receives the logged measurement configuration configured for the UE by the MN (or the first network node) and the SN (or the second network node) respectively in MR-DC (connected state);

[0147] Step 2: The UE enters an idle state or an inactive state, and records the measurement values ​​in the areas configured by the first network node and the second network node (NR according to the area configuration (AreaConfiguration) of the measured cell, LTE according to the target multicast / multicast single frequency network area list (targetMBSFN-AreaList) and the configuration in AreaConfiguration for measuring the multicast / multicast single frequency network (Multimedia Broadcast multicast service SingleFrequency Network, MBSFN), and obtains the logged MDT report measured under the configuration of the first network node (called MN logged MDT report) and the logged MDT report measured under the configuration of the second network node (called logged MDT report as an SN node in the MR-DC state);

[0148] Step 3: The UE ends the idle / inactive state and first resumes the connection state with a certain cell (i.e., it is connected to the MN, but the SN connection has not been established at this time), and carries an indication of the existence of the MN / SN Logged MDT report (logMeasAvailableSCG) in any of the following messages:

[0149] (a)RRCSetupComplete;

[0150] (b)RRCResumeComplete;

[0151] (c) RRCReconfigurationComplete;

[0152] (d)RRRCReestablishmentComplete;

[0153] (e)RRCConnectionSetupComplete;

[0154] (f)RRCConnectionResumeComplete;

[0155] (g)RRCConnectionReconfigurationComplete;

[0156] (h)RRCConnectionReestablishmentComplete.

[0157] For example, if the UE is suspended and receives a resume message from the network, the connection is restored using the RRCResumeComplete message (MN is the base station of the NR system).

[0158] Alternatively, the UE receives a reconfiguration message from the network side and successfully restores the connection, then sends an RRCReconfigurationComplete message. (MN is a base station of the NR system).

[0159] It can be understood that the above message can be selected based on whether the MN is a gNB or an eNB, and the process through which the terminal returns to the connected state.

[0160] Step 4: The network side decides whether to obtain the report based on the demand. If necessary, it sends a report request message to the UE (UEInformationRequest), which carries a request identifier, such as logMeasReportReqSCG, to request the UE to report the logged MDT as an SN node in the MR-DC state.

[0161] In step 4, the network side can decide which reports are needed for the SN after the UE restores the MR-DC connection according to the needs; or the MN transfers the existence indication of the SN-side report to the SN through the X2 / Xn interface, and the SN decides.

[0162] Step 5: The UE sends the requested logged MDT report as an SN node in the MR-DC state to the network side through UEInformationResponse; if the logged MDT report as an SN node in the MR-DC state cannot be sent in full in this transmission, the UE will carry logMeasAvailableSCG again in the UEInformationResponse message to indicate that there are still unobtained reports on the terminal side.

[0163] Step 6: The network side decides whether to obtain the report based on demand. If necessary, repeat steps 4 and 5.

[0164] Embodiment 2: Acquisition of SN logged MDT measurement report (reported after UE restores MR-DC)

[0165] Step 1: The UE receives the logged measurement configuration configured for the UE by the MN (or the first network node) and the SN (or the second network node) respectively in MR-DC (connected state);

[0166] Step 2: The UE enters the idle / inactive state, and records the measurement values ​​in the areas configured by the first network node and the second network node (NR according to the AreaConfiguration of the measured cell, LTE according to the configuration in the targetMBSFN-AreaList and AreaConfiguration of the measured MBSFN), and obtains the logged MDT report measured under the configuration of the first network node (called MN logged MDT report) and the logged MDT report measured under the configuration of the second network node (called logged MDT report as an SN node in the MR-DC state);

[0167] Step 3: The UE ends the idle / inactive state and first resumes the connection state with a certain cell (i.e., it is connected to the MN, but the SN connection has not been established at this time). At this time, only the indication information related to the MN in the last MR-DC state is carried; when the UE establishes a connection with the SN, the indication of the existence of the SN Logged MDT report in the last MR-DC state (logMeasAvailable) is carried in any of the following messages:

[0168] (a)RRCSetupComplete;

[0169] (b)RRCResumeComplete;

[0170] (c) RRCReconfigurationComplete;

[0171] (d)RRRCReestablishmentComplete.

[0172] It can be understood that the above message can be selected based on whether the MN is a gNB or an eNB, and the process through which the terminal returns to the connected state.

[0173] The selected first message is transmitted via the uplink information (UL information transfer for MR-DC) message for dual connection, that is, the RRC message sent by the terminal to the SN is carried in the UL information transfer for MR-DC and sent to the MN; after receiving it, the MN forwards the RRC message to be sent to the SN to the SN.

[0174] Step 5: The network side (SN) decides whether to obtain the report based on the demand. If necessary, it sends a report request message to the UE (UEInformationRequest), which carries a request identifier, such as logMeasReportReqSCG, to request the UE to report the last logged MDT as an SN node in the MR-DC state;

[0175] Step 6: The UE sends the requested logged MDT report as an SN node in the MR-DC state to the network side through UEInformationResponse; if the logged MDT report as an SN node in the MR-DC state cannot be sent in full in this transmission, the UE will carry logMeasAvailable again in the UEInformationResponse message to indicate that there are still unobtained reports on the terminal side.

[0176] Step 7: The network side decides whether to obtain the report based on demand. If necessary, repeat steps 4 and 5.

[0177] See also Figure 5 The embodiment of the present application provides an indication device, which is applied to a terminal. The device 500 includes:

[0178] The first sending module 501 is configured to send a first message to a network side, where the first message indicates that the terminal stores one or more first reports, and the first report is related to a secondary node.

[0179] In an embodiment of the present application, the device 500 includes: a first receiving module, used to receive a message sent by the network side requesting to obtain a report; a second sending module, used to send one or more of the first reports to the network side according to the message requesting to obtain the report, that is, at least part of the one or more first reports stored in the terminal can be reported to the network side.

[0180] In this embodiment of the present application, the first message carries an existence indication corresponding to the first report.

[0181] In this embodiment of the present application, when the primary node to which the terminal is connected is a base station in the NR system, that is, the MN to which the terminal is connected is a gNB, the first message is at least one of the following:

[0182] (1) Radio resource control setup completion message (e.g., RRCSetupComplete);

[0183] (2) Radio resource control recovery complete message (e.g., RRCResumeComplete);

[0184] (3) Radio resource control reconfiguration complete message (e.g., RRCReconfigurationComplete);

[0185] (4) Radio resource control reestablishment completion message (e.g., RRCReestablishmentComplete);

[0186] (5) Terminal information response message (e.g., UEInformationResponse).

[0187] In the embodiment of the present application, when the primary node to which the terminal is connected is a base station in the LTE system, that is, the MN to which the terminal is connected is an eNB, the first message is at least one of the following:

[0188] (1) Radio resource control connection setup complete message (e.g., RRCConnectionSetupComplete);

[0189] (2) Radio resource control connection resumption complete message (e.g., RRCConnectionResumeComplete);

[0190] (3) Radio resource control connection reconfiguration complete message (e.g., RRCConnectionReconfigurationComplete);

[0191] (4) Radio resource control connection reestablishment completion message (e.g., RRCConnectionReestablishmentComplete).

[0192] (5) Terminal information response message (e.g., UEInformationResponse).

[0193] In this embodiment of the present application, the presence indication includes at least one of the following:

[0194] (1) There is an identifier of a random access report for accessing a secondary cell group (e.g., rach-InfoAvailableSCG), indicating that there is a random access report (RACH report) as a SN node in the MR-DC state, including at least one of the following: two-step (2-step) and four-step (4-step) RACH reports; or two separate indicators are used to indicate 2-step and 4-step RACH respectively, such as 2steprach-InfoAvailableSCG and 4steprach-InfoAvailableSCG;

[0195] (2) The presence of a secondary cell group minimization of drive test log measurement report indicator (e.g., logMeasAvailableSCG): indicates the presence of MDT logged measurement information of the SN node in the MR-DC state;

[0196] (3) The existence of a Bluetooth measurement report for minimization of drive test records of a secondary cell group (e.g., logMeasAvailableBTSCG): indicates the existence of MDT logged Bluetooth measurement information of the SN node in the MR-DC state;

[0197] (4) The presence of a secondary cell group minimization of drive test log WLAN measurement report flag (e.g., logMeasAvailableWLANSCG): indicates the presence of MDT logged WLAN measurement information of the SN node in the MR-DC state;

[0198] (5) An identifier indicating the existence of a secondary cell group connection establishment failure report (e.g., connEstFailInfoAvailableSCG): indicating the existence of a connection failure report as an SN node in the MR-DC state;

[0199] (6) An identifier indicating the existence of a radio link failure report of a secondary cell group (e.g., rlf-InfoAvailableSCG): indicating the existence of a radio link failure (RLF) report of the SN node in the MR-DC state;

[0200] (7) An identifier indicating the existence of a mobility history information report of a secondary cell group (eg, mobilityHistoryReportAvailableSCG): indicates the existence of a mobility history information report of the SN node in the MR-DC state.

[0201] In the embodiment of the present application, the existence indication is obtained by reusing the existing reporting indication mechanism between the terminal and the master node.

[0202] Further, optionally, the first sending module 501 sends a first message carrying a presence indication corresponding to the first report to the secondary node through the primary node, for example, the first message is a UL information transfer for MR-DC message.

[0203] Further, optionally, the presence indication includes at least one of the following:

[0204] (1) The presence of a random access report indicator (e.g., rach-InfoAvailable): indicates the presence of a RACH report as a SN node in the MR-DC state, including at least one of the following: 2-step, 4-step RACH reports; or using two separate indicators to indicate 2-step and 4-step RACH respectively, such as 2steprach-InfoAvailableSCG and 4steprach-InfoAvailableSCG;

[0205] (2) The presence of a minimized drive test log measurement report flag (e.g., logMeasAvailable): indicates the presence of MDT logged measurement information of the SN node in the MR-DC state;

[0206] (3) The existence of a Bluetooth measurement report for minimized drive test logging (e.g., logMeasAvailableBT): indicates the existence of MDT logged Bluetooth measurement information of the SN node in the MR-DC state;

[0207] (4) The presence of a minimized drive test log wireless LAN measurement report flag (e.g., logMeasAvailableWLAN): indicates the presence of MDT logged WLAN measurement information as a SN node in the MR-DC state;

[0208] (5) An identifier indicating the existence of a connection establishment failure report (e.g., connEstFailInfoAvailable): indicating the existence of a connection failure report as an SN node in the MR-DC state;

[0209] (6) An indication of the existence of a radio link failure report (e.g., rlf-InfoAvailable): indicating the existence of an RLF report of the SN node in the MR-DC state;

[0210] (7) An indicator indicating the presence of a mobility history information report (eg, mobilityHistoryReportAvailable): indicates the presence of a mobility history information report of the SN node in the MR-DC state.

[0211] In this embodiment of the present application, if the terminal establishes a connection with the secondary node, the first message is at least one of the following:

[0212] (1) Radio resource control establishment complete message;

[0213] (2) Radio resource control recovery complete message;

[0214] (3) Radio resource control reconfiguration complete message;

[0215] (4) Radio resource control re-establishment complete message;

[0216] (5) Radio resource control connection establishment completion message;

[0217] (6) Radio resource control connection recovery complete message;

[0218] (7) Radio resource control connection reconfiguration complete message;

[0219] (8) Radio resource control connection re-establishment completion message;

[0220] (9) Terminal information response message.

[0221] The device provided in the embodiment of the present application can achieve Figure 3 The various processes implemented by the method embodiment shown achieve the same technical effect and will not be described again here to avoid repetition.

[0222] See also Figure 6 , the embodiment of the present application provides an indication device, which is applied to a network side device, and the device 600 includes:

[0223] The second receiving module 601 is configured to receive a first message, where the first message indicates that the terminal stores one or more first reports, and the first reports are related to the secondary node.

[0224] In the embodiment of the present application, the device 600 also includes: a third sending module, used to send a message requesting to obtain a report according to the first message; and a third receiving module, used to receive one or more first reports sent by the terminal.

[0225] In this embodiment of the present application, the first message carries an existence indication corresponding to the first report.

[0226] In this embodiment of the present application, when the primary node to which the terminal is connected is a base station in the NR system, that is, the MN to which the terminal is connected is a gNB, the first message is at least one of the following:

[0227] (1) Radio resource control setup completion message (e.g., RRCSetupComplete);

[0228] (2) Radio resource control recovery complete message (e.g., RRCResumeComplete);

[0229] (3) Radio resource control reconfiguration complete message (e.g., RRCReconfigurationComplete);

[0230] (4) Radio resource control reestablishment completion message (e.g., RRCReestablishmentComplete);

[0231] (5) Terminal information response message (e.g., UEInformationResponse).

[0232] In the embodiment of the present application, when the primary node to which the terminal is connected is a base station in the LTE system, that is, the MN to which the terminal is connected is an eNB, the first message is at least one of the following:

[0233] (1) Radio resource control connection setup complete message (e.g., RRCConnectionSetupComplete);

[0234] (2) Radio resource control connection resumption complete message (e.g., RRCConnectionResumeComplete);

[0235] (3) Radio resource control connection reconfiguration complete message (e.g., RRCConnectionReconfigurationComplete);

[0236] (4) Radio resource control connection reestablishment completion message (e.g., RRCConnectionReestablishmentComplete).

[0237] (5) Terminal information response message (e.g., UEInformationResponse).

[0238] In this embodiment of the present application, the presence indication includes at least one of the following:

[0239] (1) There is an identifier of a random access report for accessing a secondary cell group (e.g., rach-InfoAvailableSCG), indicating that there is a random access report (RACH report) as a SN node in the MR-DC state, including at least one of the following: two-step (2-step) and four-step (4-step) RACH reports; or two separate indicators are used to indicate 2-step and 4-step RACH respectively, such as 2steprach-InfoAvailableSCG and 4steprach-InfoAvailableSCG;

[0240] (2) The presence of a secondary cell group minimization of drive test log measurement report indicator (e.g., logMeasAvailableSCG): indicates the presence of MDT logged measurement information of the SN node in the MR-DC state;

[0241] (3) The existence of a Bluetooth measurement report for minimization of drive test records of a secondary cell group (e.g., logMeasAvailableBTSCG): indicates the existence of MDT logged Bluetooth measurement information of the SN node in the MR-DC state;

[0242] (4) The presence of a secondary cell group minimization of drive test log WLAN measurement report flag (e.g., logMeasAvailableWLANSCG): indicates the presence of MDT logged WLAN measurement information of the SN node in the MR-DC state;

[0243] (5) An identifier indicating the existence of a secondary cell group connection establishment failure report (e.g., connEstFailInfoAvailableSCG): indicating the existence of a connection failure report as an SN node in the MR-DC state;

[0244] (6) An identifier indicating the existence of a radio link failure report of a secondary cell group (e.g., rlf-InfoAvailableSCG): indicating the existence of a radio link failure (RLF) report of the SN node in the MR-DC state;

[0245] (7) An identifier indicating the existence of a mobility history information report of a secondary cell group (eg, mobilityHistoryReportAvailableSCG): indicates the existence of a mobility history information report of the SN node in the MR-DC state.

[0246] In the embodiment of the present application, the existence indication is obtained by reusing the existing reporting indication mechanism between the terminal and the master node.

[0247] In this embodiment of the present application, if the terminal establishes a connection with the secondary node, the first message is at least one of the following:

[0248] (1) Radio resource control establishment complete message;

[0249] (2) Radio resource control recovery complete message;

[0250] (3) Radio resource control reconfiguration complete message;

[0251] (4) Radio resource control re-establishment complete message;

[0252] (5) Radio resource control connection establishment completion message;

[0253] (6) Radio resource control connection recovery complete message;

[0254] (7) Radio resource control connection reconfiguration complete message;

[0255] (8) Radio resource control connection re-establishment completion message;

[0256] (9) Terminal information response message.

[0257] Further, optionally, the second receiving module 601 receives a first message carrying a presence indication corresponding to the first report through the master node, for example, the first message is carried in a UL information transfer for MR-DC message.

[0258] Further, optionally, the presence indication includes at least one of the following:

[0259] (1) The presence of a random access report indicator (e.g., rach-InfoAvailable): indicates the presence of a RACH report as a SN node in the MR-DC state, including at least one of the following: 2-step, 4-step RACH reports; or using two separate indicators to indicate 2-step and 4-step RACH respectively, such as 2steprach-InfoAvailableSCG and 4steprach-InfoAvailableSCG;

[0260] (2) The presence of a minimized drive test log measurement report flag (e.g., logMeasAvailable): indicates the presence of MDT logged measurement information of the SN node in the MR-DC state;

[0261] (3) The existence of a Bluetooth measurement report for minimized drive test logging (e.g., logMeasAvailableBT): indicates the existence of MDT logged Bluetooth measurement information of the SN node in the MR-DC state;

[0262] (4) The presence of a minimized drive test log wireless LAN measurement report flag (e.g., logMeasAvailableWLAN): indicates the presence of MDT logged WLAN measurement information as a SN node in the MR-DC state;

[0263] (5) An identifier indicating the existence of a connection establishment failure report (e.g., connEstFailInfoAvailable): indicating the existence of a connection failure report as an SN node in the MR-DC state;

[0264] (6) An indication of the existence of a radio link failure report (e.g., rlf-InfoAvailable): indicating the existence of an RLF report of the SN node in the MR-DC state;

[0265] (7) An indicator indicating the presence of a mobility history information report (eg, mobilityHistoryReportAvailable): indicates the presence of a mobility history information report of the SN node in the MR-DC state.

[0266] The device provided in the embodiment of the present application can achieve Figure 3 The various processes implemented by the method embodiment shown achieve the same technical effect and will not be described again here to avoid repetition.

[0267] Figure 7 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0268] The terminal 700 includes but is not limited to: a radio frequency unit 701, a network module 702, an audio output unit 703, an input unit 704, a sensor 705, a display unit 706, a user input unit 707, an interface unit 708, a memory 709, and a processor 710.

[0269] Those skilled in the art will appreciate that the terminal 700 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 710 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Figure 7 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0270] It should be understood that in the embodiment of the present application, the input unit 704 may include a graphics processor (Graphics Processing Unit, GPU) 7041 and a microphone 7042, and the graphics processor 7041 processes the image data of the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the image capture mode. The display unit 706 may include a display panel 7061, and the display panel 7061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 707 includes a touch panel 7071 and other input devices 7072. The touch panel 7071 is also called a touch screen. The touch panel 7071 may include two parts: a touch detection device and a touch controller. Other input devices 7072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0271] In the embodiment of the present application, the radio frequency unit 701 receives downlink data from the network side device and sends it to the processor 710 for processing; in addition, the uplink data is sent to the network side device. Generally, the radio frequency unit 701 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0272] The memory 709 can be used to store software programs or instructions and various data. The memory 709 can mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area can store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 709 can include a high-speed random access memory, and can also include a non-volatile memory, wherein the non-volatile memory can be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or a flash memory. For example, at least one disk storage device, a flash memory device, or other non-volatile solid-state storage devices.

[0273] The processor 710 may include one or more processing units; optionally, the processor 710 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, and application programs or instructions, etc., and the modem processor mainly processes wireless communications, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 710.

[0274] The terminal provided in the embodiment of the present application can achieve Figure 3 The various processes implemented by the method embodiment shown achieve the same technical effect and will not be described again here to avoid repetition.

[0275] The present application embodiment also provides a network side device. Figure 8 As shown, the network side device 800 includes: an antenna 801, a radio frequency device 802, and a baseband device 803. The antenna 801 is connected to the radio frequency device 802. In the uplink direction, the radio frequency device 802 receives information through the antenna 801 and sends the received information to the baseband device 803 for processing. In the downlink direction, the baseband device 803 processes the information to be sent and sends it to the radio frequency device 802. The radio frequency device 802 processes the received information and sends it out through the antenna 801.

[0276] The frequency band processing device may be located in the baseband device 803 . The method performed by the network-side device in the above embodiment may be implemented in the baseband device 803 . The baseband device 803 includes a processor 804 and a memory 805 .

[0277] The baseband device 803 may include, for example, at least one baseband board on which a plurality of chips are arranged. Figure 8 As shown, one of the chips is, for example, a processor 804, which is connected to a memory 805 to call a program in the memory 805 to execute the network device operations shown in the above method embodiment.

[0278] The baseband device 803 may further include a network interface 806 for exchanging information with the radio frequency device 802 , and the interface may be, for example, a common public radio interface (CPRI for short).

[0279] Specifically, the network side device of the embodiment of the present application further includes: instructions or programs stored in the memory 805 and executable on the processor 804, and the processor 804 calls the instructions or programs in the memory 805 to execute. Figure 6 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.

[0280] The embodiment of the present application also provides a program product, which is stored in a non-volatile storage medium and is executed by at least one processor to implement the following Figure 2 or Figure 3 The steps of the processing method.

[0281] The embodiment of the present application also provides a readable storage medium on which a program or instruction is stored. When the program or instruction is executed by a processor, the above Figure 2 or Figure 3The various processes of the method embodiment shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0282] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0283] The present application also provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a network side device program or instruction to implement the above Figure 2 The various processes of the method embodiment shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0284] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0285] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0286] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0287] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A method for indicating, executed by a terminal, characterized in that: include: Sending a first message to a network side device, where the first message indicates that the terminal stores one or more first reports, where the first report is related to a secondary node, and where the first message carries an existence indication corresponding to the first report, where the existence indication includes at least one of the following: an identifier of a Bluetooth measurement report of a secondary cell group minimizing drive test records, and an identifier of a wireless local area network measurement report of a secondary cell group minimizing drive test records; the first report is obtained by measuring the terminal in an idle state or an inactive state; The method further comprises: Receiving a message requesting to obtain a report sent by the network side device; According to the message requesting to obtain the report, one or more of the first reports are sent to the network side device, where the network side device is a secondary node.

2. The method according to claim 1, characterized in that The presence indication also includes at least one of the following: An identification of the presence of a random access report for accessing a secondary cell group; An indication of the presence of a measurement report of minimization of drive test records for a secondary cell group; An identification of a report of failure to establish a connection to a secondary cell group exists; An indication of the presence of a secondary cell group radio link failure report; There is an indicator for reporting the mobility history information of the secondary cell group.

3. The method according to claim 1, characterized in that When the primary node to which the terminal is connected is a base station in a new air interface system, the first message is at least one of the following: Radio resource control setup complete message; Radio resource control recovery complete message; Radio resource control reconfiguration complete message; Radio resource control re-establishment complete message; Terminal information response message.

4. The method according to claim 1, characterized in that: When the primary node to which the terminal is connected is a base station in a long term evolution system, the first message is at least one of the following: Radio resource control connection establishment complete message; Radio resource control connection recovery complete message; Radio resource control connection reconfiguration complete message; Radio resource control connection re-establishment complete message; Terminal information response message.

5. The method according to claim 1, characterized in that The existence indication is obtained by reusing the existing reporting indication mechanism between the terminal and the master node.

6. The method according to claim 1, characterized in that Sending a first message to a network side device includes: A first message is sent to the secondary node through the primary node.

7. The method according to claim 1, characterized in that If the terminal has established a connection with the secondary node, the first message is at least one of the following: Radio resource control setup complete message; Radio resource control recovery complete message; Radio resource control reconfiguration complete message; Radio resource control re-establishment complete message; Radio resource control connection establishment complete message; Radio resource control connection recovery complete message; Radio resource control connection reconfiguration complete message; Radio resource control connection re-establishment complete message; Terminal information response message.

8. The method according to claim 7, characterized in that The first message is carried in an uplink information transmission message for dual connectivity.

9. A method for indicating, executed by a network side device, characterized in that: include: receiving a first message, where the first message indicates that the terminal stores one or more first reports, where the first reports are related to a secondary node, where the first message carries an existence indication corresponding to the first report, where the existence indication includes at least one of the following: an identifier of a Bluetooth measurement report of a secondary cell group minimizing drive test records, and an identifier of a wireless local area network measurement report of a secondary cell group minimizing drive test records; and the first report is obtained by the terminal in an idle state or an inactive state; The method further comprises: According to the first message, sending a message requesting to obtain a report; One or more first reports sent by the terminal are received, and the network side device is a secondary node.

10. The method according to claim 9, characterized in that The presence indication also includes at least one of the following: An identification of the presence of a random access report for accessing a secondary cell group; An indication of the presence of a measurement report of minimization of drive test records for a secondary cell group; An identification of a report of failure to establish a connection to a secondary cell group exists; An indication of the presence of a secondary cell group radio link failure report; There is an indicator for reporting the mobility history information of the secondary cell group.

11. The method according to claim 9, characterized in that The primary node to which the terminal is connected is a base station in a new air interface system, and the first message is at least one of the following: Radio resource control setup complete message; Radio resource control recovery complete message; Radio resource control reconfiguration complete message; Radio resource control re-establishment complete message; Terminal information response message.

12. The method according to claim 9, characterized in that When the primary node to which the terminal is connected is a base station in a long term evolution system, the first message is at least one of the following: Radio resource control connection establishment complete message; Radio resource control connection recovery complete message; Radio resource control connection reconfiguration complete message; Radio resource control connection re-establishment complete message; Terminal information response message.

13. The method according to claim 9, characterized in that The existence indication is obtained by reusing the existing reporting indication mechanism between the terminal and the master node.

14. The method according to claim 9, characterized in that Receiving a first message, including: A first message is received by the master node.

15. The method according to claim 9, characterized in that If the terminal has established a connection with the secondary node, the first message is at least one of the following: Radio resource control setup complete message; Radio resource control recovery complete message; Radio resource control reconfiguration complete message; Radio resource control re-establishment complete message; Radio resource control connection establishment complete message; Radio resource control connection recovery complete message; Radio resource control connection reconfiguration complete message; Radio resource control connection re-establishment complete message; Terminal information response message.

16. The method according to claim 15, characterized in that The first message is carried in an uplink information transmission message for dual connectivity.

17. The method according to claim 14, characterized in that The receiving the first message through the master node includes: The first message forwarded by the master node is received through the X2 or Xn interface.

18. An indication device, applied to a terminal, characterized in that: include: A first sending module is configured to send a first message to a network side device, wherein the first message indicates that the terminal stores one or more first reports, the first report is related to a secondary node, the first message carries an existence indication corresponding to the first report, and the existence indication includes at least one of the following: an identifier of a Bluetooth measurement report of a secondary cell group minimizing drive test records, and an identifier of a wireless local area network measurement report of a secondary cell group minimizing drive test records; the first report is obtained by the terminal in an idle state or an inactive state; and the device further includes: A first receiving module, configured to receive a message for requesting a report sent by the network side device; The second sending module is used to send one or more of the first reports to the network side device according to the message requesting to obtain the report, and the network side device is a secondary node.

19. The device according to claim 18, characterized in that The presence indication also includes at least one of the following: An identification of the presence of a random access report for accessing a secondary cell group; An indication of the presence of a measurement report of minimization of drive test records for a secondary cell group; An identification of a report of failure to establish a connection to a secondary cell group exists; An indication of the presence of a secondary cell group radio link failure report; There is an indicator for reporting the mobility history information of the secondary cell group.

20. The device according to claim 18, characterized in that When the primary node to which the terminal is connected is a base station in a new air interface system, the first message is at least one of the following: Radio resource control setup complete message; Radio resource control recovery complete message; Radio resource control reconfiguration complete message; Radio resource control re-establishment complete message; Terminal information response message.

21. The device according to claim 18, characterized in that When the primary node to which the terminal is connected is a base station in a long term evolution system, the first message is at least one of the following: Radio resource control connection establishment complete message; Radio resource control connection recovery complete message; Radio resource control connection reconfiguration complete message; Radio resource control connection re-establishment complete message; Terminal information response message.

22. The device according to claim 18, characterized in that The existence indication is obtained by reusing the existing reporting indication mechanism between the terminal and the master node.

23. The device according to claim 18, characterized in that The first sending module further sends a first message carrying an existence indication corresponding to the first report to the secondary node through the primary node.

24. The device according to claim 22, characterized in that The first message is an uplink information transmission message for dual connectivity.

25. An indication device, applied to a network side device, characterized in that: include: A second receiving module is configured to receive a first message, wherein the first message indicates that the terminal stores one or more first reports, the first report is related to the secondary node, the first message carries an existence indication corresponding to the first report, and the existence indication includes at least one of the following: an identifier of a Bluetooth measurement report of minimizing drive test records of a secondary cell group, and an identifier of a wireless local area network measurement report of minimizing drive test records of a secondary cell group; the first report is obtained by the terminal in an idle state or an inactive state; The device also includes: A third sending module, configured to send a message requesting to obtain a report according to the first message; The third receiving module is used to receive one or more first reports sent by the terminal, and the network side device is a secondary node.

26. A terminal, characterized in that: include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein the program implements the steps of the method according to any one of claims 1 to 8 when executed by the processor.

27. A network side device, characterized in that: include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, the steps of the method according to any one of claims 9 to 17 are implemented.

28. A readable storage medium, characterized in that: The readable storage medium stores a program or an instruction, and when the program or the instruction is executed by a processor, the steps of the method according to any one of claims 1 to 17 are implemented.

Images