CN116097719A

CN116097719A - Method for reporting recorded measurement report, terminal equipment and network equipment

Info

Publication number: CN116097719A
Application number: CN202080105104.2A
Authority: CN
Inventors: 刘洋; 林雪; 石聪
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-11-27
Filing date: 2020-11-27
Publication date: 2023-05-09
Also published as: WO2022110070A1

Abstract

A method, terminal device and network device for reporting recorded measurement report, the method includes: the method comprises the steps that terminal equipment receives a first message sent by network equipment, wherein the first message is used for indicating the terminal equipment to report a recorded measurement report to the network equipment; the terminal device reports a recorded measurement report to the network device, wherein the recorded measurement report comprises at least one set of measurement quantities and first information.

Description

Method for reporting recorded measurement report, terminal equipment and network equipment

Technical Field

The embodiment of the application relates to the field of communication, in particular to a method for reporting a recorded measurement report, terminal equipment and network equipment.

Background

In a New Radio (NR) system, an idle terminal device may perform cell measurement based on an idle mode measurement configuration (idleModeMeasurement configuration), or may perform cell measurement based on a measurement configuration for cell reselection, and further may record measurement amounts in a recorded measurement report (logged measurement report), so it is a problem for a network device how to distinguish whether the measurement amounts reported by the terminal device are measurement amounts obtained based on the measurement configuration for cell reselection or measurement amounts obtained based on the idle mode measurement configuration. And, if the recorded measurement report reported by the terminal device does not include the measurement quantity based on the idle mode measurement configuration, how the network device determines the reason why the terminal device stops recording the idle mode measurement quantity is also an urgent problem to be solved

Disclosure of Invention

The terminal device can determine the reason that the terminal device stops recording the idle mode measurement quantity by including duration time information or a flag bit for stopping executing idle mode measurement in the recorded measurement report, or include indication information of the type of the flag measurement quantity in the recorded measurement report so that the network device can determine whether the measurement quantity reported by the terminal device is the idle mode measurement quantity according to the indication information.

In a first aspect, a method for reporting a recorded measurement report is provided, including: the method comprises the steps that terminal equipment receives a first message sent by network equipment, wherein the first message is used for indicating the terminal equipment to report a recorded measurement report to the network equipment; the terminal device reports a recorded measurement report to the network device, wherein the recorded measurement report comprises at least one set of measurement quantities and first information.

In a second aspect, a method for reporting a recorded measurement report is provided, including: the network equipment sends a first message to the terminal equipment, wherein the first message is used for indicating the terminal equipment to report a recorded measurement report to the network equipment;

The network equipment receives a recorded measurement report reported by the terminal equipment, wherein the recorded measurement comprises at least one group of measurement quantity and first information;

and the network equipment determines whether the measurement quantity is an idle mode measurement quantity according to the first information, and/or the reason that the terminal equipment stops recording the idle mode measurement quantity, wherein the idle mode measurement quantity is obtained based on idle mode measurement configuration measurement.

In a third aspect, a terminal device is provided for performing the method in the first aspect or each implementation manner thereof.

Specifically, the terminal device comprises functional modules for performing the method of the first aspect or its implementation manner.

In a fourth aspect, a network device is provided for performing the method of the second aspect or implementations thereof.

In particular, the network device comprises functional modules for performing the method of the second aspect or implementations thereof described above.

In a fifth aspect, a terminal device is provided comprising a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory and executing the method in the first aspect or various implementation manners thereof.

In a sixth aspect, a network device is provided that includes a processor and a memory. The memory is for storing a computer program and the processor is for calling and running the computer program stored in the memory for performing the method of the second aspect or implementations thereof described above.

A seventh aspect provides a chip for implementing the method of any one of the first to second aspects or each implementation thereof.

Specifically, the chip includes: a processor for calling and running a computer program from a memory, causing a device in which the apparatus is installed to perform the method as in any one of the first to second aspects or implementations thereof described above.

In an eighth aspect, a computer-readable storage medium is provided for storing a computer program that causes a computer to perform the method of any one of the above-described first to second aspects or implementations thereof.

A ninth aspect provides a computer program product comprising computer program instructions for causing a computer to perform the method of any one of the first to second aspects or implementations thereof.

In a tenth aspect, there is provided a computer program which, when run on a computer, causes the computer to perform the method of any one of the first to second aspects or implementations thereof.

According to the technical scheme, the network equipment can determine the reason that the terminal equipment stops recording the idle mode measurement quantity according to the preset duration time when the terminal equipment executes the idle mode measurement by including the preset duration time in the reported recorded measurement report. Alternatively, by including the first flag bit in the recorded measurement report, the network device can determine when the terminal device stops performing idle mode measurements, thereby being able to determine the reason why the terminal device stops recording idle mode measurement amounts.

In addition, the terminal device includes indication information for marking the measurement quantity type in the reported recorded measurement report, so that the terminal device can distinguish whether the measurement quantity is an idle mode measurement quantity or a cell reselection measurement quantity according to the indication information.

Drawings

Fig. 1 is a schematic diagram of a communication system architecture provided in an embodiment of the present application.

Fig. 2 is a schematic interaction diagram of a terminal device performing MDT measurements and reporting measurement quantities.

Fig. 3 is a schematic interaction diagram of a dual connection establishment procedure.

Fig. 4 is a schematic interaction diagram of a method of reporting a recorded measurement report according to an embodiment of the present application.

Fig. 5 is an example diagram of reporting a recorded measurement report according to an embodiment of the present application.

Fig. 6 is a schematic block diagram of a terminal device according to an embodiment of the present application.

Fig. 7 is a schematic block diagram of a network device provided according to an embodiment of the present application.

Fig. 8 is a schematic block diagram of a communication device provided according to an embodiment of the present application.

Fig. 9 is a schematic block diagram of an apparatus provided in accordance with an embodiment of the present application.

Fig. 10 is a schematic block diagram of a communication system provided according to an embodiment of the present application.

Detailed Description

The following description of the technical solutions in the embodiments of the present application will be made with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden for the embodiments herein, are intended to be within the scope of the present application.

The technical solution of the embodiment of the application can be applied to various communication systems, for example: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA) system, wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, general packet Radio service (General Packet Radio Service, GPRS), long term evolution (Long Term Evolution, LTE) system, advanced long term evolution (Advanced long term evolution, LTE-a) system, new Radio (NR) system, evolved system of NR system, LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum, NR-U) system on unlicensed spectrum, non-terrestrial communication network (Non-Terrestrial Networks, NTN) system, universal mobile communication system (Universal Mobile Telecommunication System, UMTS), wireless local area network (Wireless Local Area Networks, WLAN), wireless fidelity (Wireless Fidelity, wiFi), fifth Generation communication (5 th-Generation, 5G) system, or other communication system, etc.

Generally, the number of connections supported by the conventional communication system is limited and easy to implement, however, with the development of communication technology, the mobile communication system will support not only conventional communication but also, for example, device-to-Device (D2D) communication, machine-to-machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), inter-vehicle (Vehicle to Vehicle, V2V) communication, or internet of vehicles (Vehicle to everything, V2X) communication, etc., and the embodiments of the present application may also be applied to these communication systems.

Optionally, the communication system in the embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, and a Stand Alone (SA) fabric scenario.

Optionally, the communication system in the embodiments of the present application may be applied to unlicensed spectrum, where unlicensed spectrum may also be considered as shared spectrum; alternatively, the communication system in the embodiments of the present application may also be applied to licensed spectrum, where licensed spectrum may also be considered as non-shared spectrum.

Embodiments of the present application describe various embodiments in connection with network devices and terminal devices, where a terminal device may also be referred to as a User Equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, user Equipment, or the like.

The terminal device may be a STATION (ST) in a WLAN, may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) STATION, a personal digital assistant (Personal Digital Assistant, PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle mounted device, a wearable device, a terminal device in a next generation communication system such as an NR network, or a terminal device in a future evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.

In embodiments of the present application, the terminal device may be deployed on land, including indoor or outdoor, hand-held, wearable or vehicle-mounted; can also be deployed on the water surface (such as ships, etc.); but may also be deployed in the air (e.g., on aircraft, balloon, satellite, etc.).

In the embodiment of the present application, the terminal device may be a Mobile Phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an augmented Reality (Augmented Reality, AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in unmanned driving (self driving), a wireless terminal device in remote medical (remote medical), a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation security (transportation safety), a wireless terminal device in smart city (smart city), or a wireless terminal device in smart home (smart home), and the like.

By way of example, and not limitation, in embodiments of the present application, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

In this embodiment of the present application, the network device may be a device for communicating with a mobile device, where the network device may be an Access Point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, a relay station or an Access Point, a vehicle device, a wearable device, and a network device (gNB) in an NR network, or a network device in a PLMN network for future evolution, or a network device in an NTN network, etc.

By way of example and not limitation, in embodiments of the present application, a network device may have a mobile nature, e.g., the network device may be a mobile device. Alternatively, the network device may be a satellite, a balloon station. For example, the satellite may be a Low Earth Orbit (LEO) satellite, a medium earth orbit (medium earth orbit, MEO) satellite, a geosynchronous orbit (geostationary earth orbit, GEO) satellite, a high elliptical orbit (High Elliptical Orbit, HEO) satellite, or the like. Alternatively, the network device may be a base station disposed on land, in a water area, or the like.

In this embodiment of the present application, a network device may provide a service for a cell, where a terminal device communicates with the network device through a transmission resource (e.g., a frequency domain resource, or a spectrum resource) used by the cell, where the cell may be a cell corresponding to a network device (e.g., a base station), and the cell may belong to a macro base station, or may belong to a base station corresponding to a Small cell (Small cell), where the Small cell may include: urban cells (Metro cells), micro cells (Micro cells), pico cells (Pico cells), femto cells (Femto cells) and the like, and the small cells have the characteristics of small coverage area and low transmitting power and are suitable for providing high-rate data transmission services.

Exemplary, a communication system 100 to which embodiments of the present application apply is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within the coverage area.

Fig. 1 illustrates one network device and two terminal devices by way of example, and alternatively, the communication system 100 may include a plurality of network devices and may include other numbers of terminal devices within the coverage area of each network device, which is not limited in this embodiment of the present application.

Optionally, the communication system 100 may further include a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should be understood that a device having a communication function in a network/system in an embodiment of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include a network device 110 and a terminal device 120 with communication functions, where the network device 110 and the terminal device 120 may be specific devices described above, and are not described herein again; the communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

It should be understood that, in the embodiments of the present application, the "indication" may be a direct indication, an indirect indication, or an indication having an association relationship. For example, a indicates B, which may mean that a indicates B directly, e.g., B may be obtained by a; it may also indicate that a indicates B indirectly, e.g. a indicates C, B may be obtained by C; it may also be indicated that there is an association between a and B.

In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct correspondence or an indirect correspondence between the two, or may indicate that there is an association between the two, or may indicate a relationship between the two and the indicated, configured, or the like.

In the embodiment of the present application, the "predefining" may be implemented by pre-storing corresponding codes, tables or other manners that may be used to indicate relevant information in devices (including, for example, terminal devices and network devices), and the specific implementation of the present application is not limited. Such as predefined may refer to what is defined in the protocol.

In this embodiment of the present application, the "protocol" may refer to a standard protocol in the communication field, for example, may include an LTE protocol, an NR protocol, and related protocols applied in a future communication system, which is not limited in this application.

In order to understand the performance of a mobile network, a mobile network builder or network operator typically needs to drive a car along a fixed line to collect a series of measurements reflecting the current network performance, such as downstream signal quality/interference. Based on the collected measurement quantity about the network performance, the network optimization team can then adjust the deployment of the mobile network device, the strength of the signal, and the setting of the antenna angle, so as to improve the performance of the mobile network and the satisfaction of the user. However, this method has the disadvantage that as the scale of the mobile network is enlarged, the drive test becomes more time-consuming and labor-consuming, which is not beneficial for the mobile operator to adjust the network deployment in time, and the cost of consumption is greater.

Based on this, mobile networks introduce a signal acquisition method called minimization of drive tests (minimization of Drive test, MDT), whose core idea is to enable numerous user terminals to report their signal acquisition in case of obtaining terminal grants. On the premise that the number of terminals is sufficient, the network can quickly and economically acquire the network performance related information in the area, and this way of collecting the network performance of the terminals in some target areas is called management-based MDT (management-based MDT). In addition, MDT may also be used to assist the network in collecting network performance related data for a specific terminal (e.g., the end user often complains about poor network performance), and this MDT collection is referred to as signal-based MDT (signaling-based MDT).

The target terminal performing the MDT may be in a radio resource control (Radio Resource Control, RRC) connected (connected) mode, an RRC Idle (Idle) mode, or an Inactive (Inactive) mode. But the configuration signaling of the MDT must be sent by the network to the terminal while the terminal is in connected mode. When the network configures an immediate (MDT), the terminal will report in the connected state the measurement quantity that the terminal acquired while in the connected state. Or when the network configures a recorded (logged) MDT, the terminal reports the measurement quantity recorded when the network returns to the idle state to the network when the network is restored to the connected state.

In some embodiments, the MDT configuration may be sent to the terminal through a core network control plane network element or a network management (OAM), and after the terminal completes the measurement quantity acquisition, the MDT report is generated and reported to the base station, and then the base station sends it to an independent MDT data analysis network element, for example, a trace collection entity (Trace Collection Entity, TCE).

Fig. 2 shows a schematic interaction diagram of a terminal device performing MDT measurements and reporting procedures.

In S201, the terminal device receives the recorded MDT configuration transmitted by the network device.

S202, the terminal device performs measurement when backing up to the RRC idle mode (idle mode).

S203, the terminal device indicates to the network device that the recorded measurement quantity is available (logMeasAvailable) after entering the RRC connected mode (connected mode), so that the network device knows that the terminal device has the measurement quantity to upload.

S204, the network device sends a UE information request (UE information Request) to the terminal device requesting to acquire the measurement quantity of the terminal device.

S205, the terminal device sends a UE information response (UE Information Response) to the network device, where the UE information response includes the measurement quantity that needs to be reported.

And S206, the network equipment sends the received measurement quantity equipment reported by the terminal equipment to the TCE.

In a conventional dual-connection establishment procedure, first, the network device needs to send a measurement configuration for the terminal device. And the terminal equipment executes measurement on the frequency point corresponding to the potential primary and secondary cells (PScells) according to the measurement configuration, and reports the measurement result to the network equipment. Finally, the network device (i.e. the primary network (MN)) selects a Secondary Network (SN) with a suitable PSCell according to the measurement result of the terminal device to initiate a dual connection establishment procedure for the terminal device. Fig. 3 shows a schematic interaction diagram of a dual connection establishment procedure.

S21, MN sends an SN adding Request (addition Request) to SN, which is used for requesting to add SN as SN of terminal equipment.

S22, the SN sends an SN addition request acknowledgement to the MN (addition Request Acknowledge).

S22a, the MN sends an Xn-U address indication to the SN for establishing a connection between the two.

S23, the MN sends an RRC reconfiguration message to the UE.

S24, the UE sends RRC reconfiguration complete information to the MN.

S25, the MN sends an SN reconfiguration completion message to the SN.

S26, the UE initiates a random access process to the SN to access the SN.

S27, the MN sends an SN state switching (Status Transfer) command to the SN.

S28, the UPF sends data to the SN through the MN.

S29, the MN sends a protocol data unit (Protocol Data Unit, PDU) session modification indication to the AMF.

S210, the AMF sends a bearer modification command to the UPF.

S211, the UPF sends End Marker Packet to the SN through the MN.

S212, the AMF sends a PDU session modification acknowledgement to the MN.

As can be seen from the above interaction flow, before the MN initiates SN addition Request to the appropriate target SN, it needs to go through the process that the network device sends the measurement configuration to the terminal device, the terminal device performs measurement, and the terminal device reports the measurement result, which is very time-consuming. In order to reduce the time overhead of connection establishment, a mechanism of advanced measurement (early measurement) is introduced in order to quickly add a secondary node to the terminal device to improve throughput.

When the terminal device applies early measurement, the network device may transmit measurement frequency point information to the terminal device, which is needed to prepare for adding SN in idle mode, through an RRC release (RRCRelease) message or a system information block (System Information Block, SIB) broadcast. The terminal device may make measurements according to an idle mode measurement configuration (idleModeMeasurement configuration) while in idle mode.

For the terminal equipment in the idle state, the network equipment can also configure measurement configuration for cell reselection to the terminal equipment, and the terminal equipment can execute cell measurement based on the measurement configuration so as to carry out measurement reporting, so that for the network equipment, how to distinguish whether the measurement quantity reported by the terminal equipment is the measurement quantity obtained based on the measurement configuration of cell reselection or the measurement quantity obtained based on the measurement configuration of the idle mode is a problem. And, if the measurement quantity based on the idle mode measurement configuration is not included in the recorded measurement report reported by the terminal device, how the network device determines the reason why the terminal device stops recording the idle mode measurement quantity is also an urgent problem to be solved.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The following related technologies may be optionally combined with the technical solutions of the embodiments of the present application, which all belong to the protection scope of the embodiments of the present application. Embodiments of the present application include at least some of the following.

Fig. 4 is a schematic interaction diagram of a method of reporting a recorded measurement report according to an embodiment of the present application, as shown in fig. 4, the method 300 may include:

s301, a terminal device receives a first message sent by a network device, wherein the first message is used for indicating the terminal device to report a recorded measurement report to the network device;

s302, the terminal equipment reports a recorded measurement report to the network equipment, wherein the recorded measurement report comprises at least one group of measurement quantity and first information;

s303, the network equipment determines whether the measurement quantity is an idle mode measurement quantity according to the first information, and/or the reason that the terminal equipment stops recording the idle mode measurement quantity.

Alternatively, the first message may be any downlink message, such as an RRC message, and as an example, the first message may be UE information Request described above.

In some embodiments, each set of measurement quantities may be contained in an information element (Information Element, IE), such as recorded measurement information IE (logMeasInfo IE), and may also correspond to a piece of time information that may be contained in the IE. Alternatively, the time information may be a relative time, and the relative time may be a reference time with respect to a time when the terminal device enters the idle mode.

Alternatively, the time information may be the time at which the measurement quantity is recorded, or may also be the time at which the measurement is performed.

In the embodiment of the present application, the idle mode measurement is measured based on an idle mode measurement configuration (idleModeMeasurement configuration), and in a case where the measurement is not an idle mode measurement, the measurement may be measured based on a measurement configuration for cell reselection, for example, and in this case, the measurement obtained may be referred to as a cell reselection measurement.

Optionally, in some embodiments, the first information includes a preset duration for which the terminal device performs idle mode measurement, and/or a time for which the terminal device enters idle mode.

Alternatively, the preset duration for the terminal device to perform idle mode measurement may be configured by the network device, or may be predefined, for example, the network device may configure the duration in idleModeMeasurement configuration, and report the duration at the same time when the recorded measurement report is reported, so that the network device may determine, based on the duration and time information corresponding to the at least one set of measurement amounts, a reason for the terminal device to stop recording the idle mode measurement amounts.

As an example, if the offset of the time information for recording the at least one set of measurement amounts with respect to the time when the terminal device enters the idle mode is smaller than the preset duration, that is, the duration for which the terminal device performs measurement does not reach the preset duration, the network device may determine that the reason for the terminal device to stop recording the idle mode measurement amounts is that the signal quality of the terminal device entering the cell that does not belong to the area covered by the frequency point in the idle mode measurement configuration or the frequency point in the idle mode measurement configuration is poor, for example, the signal strength of the downlink signal corresponding to the frequency point configured in the idle mode measurement configuration is lower than a specific threshold.

As another example, if the offset of the time information for recording the at least one set of measurement amounts with respect to the time when the terminal device enters the idle mode is greater than or equal to the preset duration, the network device may determine that the reason for the terminal device stopping recording the idle mode measurement amounts is that the measurement duration reaches the preset duration.

Optionally, in some embodiments, the first information includes a first flag bit, where the first flag bit is used to determine time information when the terminal device stops performing idle mode measurements.

In some embodiments, at least one IE corresponding to the at least one set of measurement quantities includes a first IE and a second IE, where the first IE corresponds to a first time and the second IE corresponds to a second time, the first time and the second time are adjacent, and if after the first time, the terminal device stops performing idle mode measurement, the terminal device may include the first flag bit in the second IE, where the first flag bit is used to indicate that the terminal device does not perform idle mode measurement for a part or all of a time between the first time and the second time.

Alternatively, part or all of the time between the first time and the second time may refer to a direct part or all of the measurement time point between the first time and the second time.

It should be understood that, in the embodiment of the present application, the measurement time point may refer to a time point when the terminal device performs measurement, and the time point when the terminal device performs measurement may be discrete or continuous, which is not limited in the present application.

Optionally, in some embodiments, the first time and the second time are recorded times of a measured quantity.

For example, the terminal device records a set of measurement values at a first time, generates IE1, records another set of measurement values at a second time, and marks IE2, and after the first time, the terminal device stops performing idle mode measurement, and may include a first flag bit at IE 2.

Optionally, in other embodiments, each IE for recording the measurement quantity includes a start flag bit and a stop flag bit, where the start flag bit is used to flag whether the time corresponding to the IE is the time when the terminal device starts to perform idle mode measurement, and the stop flag bit is used to flag whether the time corresponding to the IE is the time when the terminal device stops performing idle mode measurement, for example, a value of 1 indicates yes and a value of 0 indicates no.

For example, the terminal device records a set of measurement values at a first time, generates IE1, records another set of measurement values at a second time, records another set of measurement values at a third time, records another set of measurement values at an IE3, records another set of measurement values at a fourth time, records another set of measurement values at an IE4, wherein after the first time, the terminal device starts to perform idle mode measurement, stops performing idle mode measurement at the second time, starts to perform idle mode measurement again after the third time, and stops performing idle mode measurement at the fourth time. The start and stop flags in IE1 are 1 and 0, respectively, the start and stop flags in IE2 are 0 and 1, respectively, the start and stop flags in IE3 are 1 and 0, respectively, and the start and stop flags in IE4 are 0 and 1, respectively.

Optionally, in some embodiments, the at least one set of measurement values includes measurement values corresponding to at least one frequency point respectively, and the first information includes information indicating whether the measurement value corresponding to each frequency point is an idle mode measurement value.

As one implementation manner, the first information includes a first bit map, where the first bit map includes a plurality of bits, each bit corresponds to a frequency point, and a value of each bit is used to indicate whether a measurement quantity of the corresponding frequency point is an idle mode measurement quantity.

For example, assuming that the terminal device reports 8 sets of measurement amounts corresponding to 8 frequency points, the first bit bitmap may be 8 bits, where each bit corresponds to one frequency point, and different values of each bit are used to indicate whether the measurement amounts of the corresponding frequency points are idle mode measurement amounts. For example, a bit value of 1 indicates no, and a bit value of 0 indicates no, and if the first bit map is 11000001, the first frequency point may be determined, and the measurement amounts corresponding to the seventh frequency point and the eighth frequency point are obtained according to the idle mode measurement configuration.

In some embodiments, all the measurement values may be included in the measresultneigcellistnr/EUTRA, including the measurement value corresponding to each frequency point, and the measresultneigcellistnr/EUTRA is included in the measresultneigcells-r 16, and then a bit map (bitmaplogmodeMeas) may be added to the measresultneigcells-r 16 to indicate whether the measurement values corresponding to different frequency points in the measresultneigcellistnr/EUTRA are obtained according to the idle mode measurement configuration.

As one example, the syntax format of measResultNeighColls-r 16 is as follows:

SEQUENCE{

measResultNeighCellListNR MeasResultListLogging2NR-r16 OPTIONAL

bitmaplogmodeMeas[0000,111,000]……

measResultNeighCellListEUTRA MeasResultListLogging2EUTRA-r16 OPTIONAL

}

as another implementation manner, the indication information of whether the measurement quantity corresponding to each frequency point is the idle mode measurement quantity is a flag bit, where the flag bit is included in an IE for carrying the measurement quantity corresponding to each frequency point.

In some embodiments, the measurement value corresponding to each frequency point is carried in an IE, for example, measresultlogginr-r 16, and a flag bit, for example, isidleMeas, may be included in the IE to indicate whether the measurement value corresponding to the frequency point is an idle mode measurement value.

As one example, the syntax format of the MeasResultLoggingNR-r16 is as follows:

MeasResultLoggingNR-r16::＝SEQUENCE{

physCellId-r16 physCellId,

resultsSSB-Cell-r16 MeasQuantityResults,

numberofGoodSSB-r16 INTEGER(1..maxNrofSSBs-r16 OPTIONAL

isidleMeas Enumerated{True}

}

as yet another implementation, the recorded measurement report includes a dedicated IE for carrying idle mode measurements.

I.e. idle mode measurements may be recorded in a dedicated IE, so that the recording location of the network device may determine which type of measurement is.

For example, the dedicated IE may be denoted as measResultledModeContels-r 17, and the measResultledleModeContels-r 17 may include measResultNeighcelListNR/EUTRA for recording all idle mode measurements.

As an example, the syntax format of measresultablemodeells-r 17 is as follows:

measResultidleModeCells-r17 SEQUENCE{

measResultNeighCellListNR MeasResultListLogging2NR-r16 OPTIONAL

measResultNeighCellListEUTRA MeasResultListLogging2EUTRA-r16 OPTIONAL

}

optionally, in some embodiments, in case an idle mode measurement is included in the recorded measurement report, the recorded measurement report further includes first indication information for indicating that an idle mode measurement is included in the recorded measurement report. In this way, the network device may determine the type of measurement quantity or the expiration time for performing idle mode measurement, etc. in the case that the first indication information is included in the recorded measurement report, again in the manner described above.

A specific implementation procedure for reporting a recorded measurement report according to an embodiment of the present application is described with reference to fig. 5.

First, the terminal device in the connected mode receives a recorded measurement configuration of the network device, and based on the recorded measurement configuration, the terminal device determines that the measurement quantity recorded when the terminal device falls back into the idle mode is reported to the network device when entering the connected mode. The logged measurement configuration may include a logged duration (logged duration), among other things.

The terminal device then receives an RRC release message of the network device, which RRC release message comprises an idle mode measurement configuration 1, which idle mode measurement configuration 1 may comprise a duration1 (denoted measidleDuration 1), i.e. the duration for which the terminal device performs idle mode measurements.

The terminal equipment rolls back to an idle mode, starts a timer T331, the duration of the timer is measIdleDuration1, starts a timer T330, the duration of the timer is loggingDuration, and performs cell measurement based on the idle mode measurement configuration 1.

Further, the terminal device enters the connected mode and receives an RRC release message of the network device, where the RRC release message includes an idle mode measurement configuration 2, and the idle mode measurement configuration 2 may include a duration2 (denoted as measIdleDuration 2).

The terminal equipment rolls back to the idle mode, starts a timer T331, the duration of the timer is measIdleDurate 2, and performs cell measurement based on the idle mode measurement configuration 2.

If the terminal device does not report the logged-in measurement report after entering the connection mode for the second time, the terminal device needs to record the measurement quantities of the two idle modes, and the logged-in measurement report includes the measurement quantities of the two idle modes and also includes the durations corresponding to the two idle modes, namely measIdleDuration1 and measIdleDuration2.

Optionally, the logged measurement report may further comprise time information for the terminal device to enter an idle mode.

Therefore, in the embodiment of the present application, the terminal device performs the idle mode measurement by including the preset duration of time for the terminal device to perform the idle mode measurement in the reported recorded measurement report, so that the network device can determine the reason for the terminal device to stop recording the idle mode measurement according to the preset duration of time. Alternatively, by including the first flag bit in the recorded measurement report, the network device can determine when the terminal device stops performing idle mode measurements, thereby being able to determine the reason why the terminal device stops recording idle mode measurement amounts.

The method embodiments of the present application are described in detail above with reference to fig. 4 to 5, and the apparatus embodiments of the present application are described in detail below with reference to fig. 6 to 10, it being understood that the apparatus embodiments and the method embodiments correspond to each other, and similar descriptions may refer to the method embodiments.

Fig. 6 shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application. As shown in fig. 6, the terminal device 400 includes:

A communication unit 410, configured to receive a first message sent by a network device, where the first message is used to instruct the terminal device to report a recorded measurement report to the network device;

reporting a recorded measurement report to the network device, wherein the recorded measurement report comprises at least one set of measurement quantities and first information.

Optionally, in some embodiments, the first information is used by the network device to determine whether the measurement quantity is an idle mode measurement quantity, and/or a reason for the terminal device to stop recording the idle mode measurement quantity, where the idle mode measurement quantity is measured based on an idle mode measurement configuration.

Optionally, in some embodiments, the first information includes a preset duration for which the terminal device performs idle mode measurement and/or a time when the terminal device enters idle mode.

Optionally, in some embodiments, the preset duration and/or the time the terminal device enters idle mode is used for the network device to determine a reason for the terminal device to stop recording idle mode measurements.

Optionally, in some embodiments, the recorded measurement report further includes time information for recording the at least one set of measurements, wherein,

The offset of the time information of the at least one group of measurement quantities relative to the time of the terminal equipment entering the idle mode is smaller than the preset duration time, and the reason for indicating the terminal equipment to stop recording the idle mode measurement quantities is that the signal strength of a downlink signal corresponding to a frequency point in the idle mode measurement configuration or a frequency point in the idle mode measurement configuration is lower than a specific threshold value; or alternatively

The offset of the time information of the at least one group of measurement quantities relative to the time of the terminal equipment entering the idle mode is larger than or equal to the preset duration, and the reason for indicating the terminal equipment to stop recording the idle mode measurement quantities is that the measurement duration reaches the preset duration.

Optionally, in some embodiments, the first flag bit is used to indicate that the terminal device does not perform idle mode measurement for part or all of the time between the first time and the second time.

Optionally, in some embodiments, the first flag bit is included in an information element IE corresponding to the second time for recording the measurement quantity.

Optionally, in some embodiments, the first time and the second time are relative times with a time of the terminal device entering idle mode as a reference time.

Optionally, in some embodiments, the at least one set of measurement values includes measurement values corresponding to at least one frequency point respectively, and the first information includes information indicating whether the measurement value corresponding to the at least one frequency point is an idle mode measurement value.

Optionally, in some embodiments, the first information includes a first bit map, where the first bit map includes a plurality of bits, each bit corresponds to a frequency point, and a value of each bit is used to indicate whether a measurement quantity of the corresponding frequency point is an idle mode measurement quantity.

Optionally, in some embodiments, the indication information of whether the measurement quantity corresponding to each frequency point is an idle mode measurement quantity includes a flag bit, where the flag bit is included in an IE for carrying the measurement quantity corresponding to each frequency point.

Optionally, in some embodiments, the logged measurement report includes a dedicated IE for carrying idle mode measurement amounts.

Optionally, in some embodiments, in case an idle mode measurement is included in the recorded measurement report, the recorded measurement report further includes second indication information for indicating that an idle mode measurement is included in the recorded measurement report.

Alternatively, in some embodiments, the communication unit may be a communication interface or transceiver, or an input/output interface of a communication chip or a system on a chip

It should be understood that the terminal device 400 according to the embodiment of the present application may correspond to the terminal device in the embodiment of the method of the present application, and the foregoing and other operations and/or functions of each unit in the terminal device 400 are respectively for implementing the corresponding flow of the terminal device in the method 300 shown in fig. 4, and are not further described herein for brevity.

Fig. 7 is a schematic block diagram of a network device according to an embodiment of the present application. The network device 500 of fig. 7 includes:

a communication unit 510, configured to send a first message to a terminal device, where the first message is used to instruct the terminal device to report a recorded measurement report to the network device, and receive the recorded measurement report reported by the terminal device, where the recorded measurement includes at least one set of measurement quantity and first information;

A processing unit 520, configured to determine, according to the first information, whether the measurement quantity is an idle mode measurement quantity, and/or a reason why the terminal device stops recording the idle mode measurement quantity, where the idle mode measurement quantity is obtained based on an idle mode measurement configuration measurement.

Optionally, in some embodiments, the recorded measurement report further comprises time information recording the at least one set of measurement quantities, wherein the processing unit is specifically configured to:

if the offset of the time information for recording the at least one set of measurement quantities relative to the time of the terminal equipment entering the idle mode is smaller than the preset duration, determining that the reason for stopping recording the idle mode measurement quantities by the terminal equipment is that the signal strength of a downlink signal corresponding to a frequency point in the idle mode measurement configuration or a frequency point in the idle mode measurement configuration is lower than a specific threshold value; or alternatively

If the offset of the time information of the at least one set of measurement quantities relative to the time of the terminal equipment entering the idle mode is greater than or equal to the preset duration, determining that the reason why the terminal equipment stops recording the measurement quantities of the idle mode is that the measurement duration reaches the preset duration.

Optionally, in some embodiments, the at least one set of measurement values includes a set of measurement values corresponding to at least one frequency point respectively, and the first information includes information indicating whether the set of measurement values corresponding to each frequency point is an idle mode measurement value.

Optionally, in some embodiments, the processing unit 520 is further configured to:

in the case that the recorded measurement report includes first indication information, determining whether the measurement quantity is an idle mode measurement quantity according to the first information, wherein the first indication information is used for indicating that the recorded measurement report includes the idle mode measurement quantity.

Alternatively, in some embodiments, the communication unit may be a communication interface or transceiver, or an input/output interface of a communication chip or a system on a chip. The processing unit may be one or more processors.

It should be understood that the network device 500 according to the embodiment of the present application may correspond to the network device in the embodiment of the method of the present application, and the foregoing and other operations and/or functions of each unit in the network device 500 are respectively for implementing the corresponding flow of the network device in the method 300 shown in fig. 4, and are not further described herein for brevity.

Fig. 8 is a schematic structural diagram of a communication device 600 provided in an embodiment of the present application. The communication device 600 shown in fig. 8 comprises a processor 610, from which the processor 610 may call and run a computer program to implement the method in the embodiments of the present application.

Optionally, as shown in fig. 8, the communication device 600 may further comprise a memory 620. Wherein the processor 610 may call and run a computer program from the memory 620 to implement the methods in embodiments of the present application.

The memory 620 may be a separate device from the processor 610 or may be integrated into the processor 610.

Optionally, as shown in fig. 8, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, and in particular, may send information or data to other devices, or receive information or data sent by other devices.

The transceiver 630 may include a transmitter and a receiver, among others. Transceiver 630 may further include antennas, the number of which may be one or more.

Optionally, the communication device 600 may be specifically a network device in the embodiment of the present application, and the communication device 600 may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the communication device 600 may be specifically a mobile terminal/terminal device in the embodiment of the present application, and the communication device 600 may implement corresponding processes implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which are not described herein for brevity.

Fig. 9 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 700 shown in fig. 9 includes a processor 710, and the processor 710 may call and run a computer program from a memory to implement the methods in the embodiments of the present application.

Optionally, as shown in fig. 9, chip 700 may also include memory 720. Wherein the processor 710 may call and run a computer program from the memory 720 to implement the methods in embodiments of the present application.

Wherein the memory 720 may be a separate device from the processor 710 or may be integrated into the processor 710.

Optionally, the chip 700 may also include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and in particular, may obtain information or data sent by other devices or chips.

Optionally, the chip 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.

Optionally, the chip may be applied to a network device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the chip may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

Fig. 10 is a schematic block diagram of a communication system 900 provided in an embodiment of the present application. As shown in fig. 10, the communication system 900 includes a terminal device 910 and a network device 920.

The terminal device 910 may be configured to implement the corresponding functions implemented by the terminal device in the above method, and the network device 920 may be configured to implement the corresponding functions implemented by the network device in the above method, which are not described herein for brevity.

It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memory is exemplary but not limiting, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

Embodiments of the present application also provide a computer-readable storage medium for storing a computer program.

Optionally, the computer readable storage medium may be applied to a network device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the computer readable storage medium may be applied to a mobile terminal/terminal device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding procedure implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, which is not described herein for brevity.

Embodiments of the present application also provide a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to a network device in the embodiments of the present application, and the computer program instructions cause the computer to execute corresponding flows implemented by the network device in the methods in the embodiments of the present application, which are not described herein for brevity.

Optionally, the computer program product may be applied to a mobile terminal/terminal device in the embodiments of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiments of the present application, which are not described herein for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to a network device in the embodiments of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the computer program may be applied to a mobile terminal/terminal device in the embodiments of the present application, where the computer program when run on a computer causes the computer to execute corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiments of the present application, and for brevity, will not be described herein.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A method of reporting a recorded measurement report, comprising:

the method comprises the steps that terminal equipment receives a first message sent by network equipment, wherein the first message is used for indicating the terminal equipment to report a recorded measurement report to the network equipment;

the terminal device reports a recorded measurement report to the network device, wherein the recorded measurement report comprises at least one set of measurement quantities and first information.
The method according to claim 1, wherein the first information is used by a network device to determine whether the measurement quantity is an idle mode measurement quantity, and/or a reason for the terminal device to stop recording an idle mode measurement quantity, wherein the idle mode measurement quantity is measured based on an idle mode measurement configuration.
Method according to claim 1 or 2, characterized in that the first information comprises a preset duration for which the terminal device performs idle mode measurements and/or a time when the terminal device enters idle mode.
A method according to claim 3, characterized in that the preset duration and/or the time the terminal device enters idle mode is used by the network device to determine the reason why the terminal device stops recording idle mode measurements.
The method of claim 3 or 4, wherein the recorded measurement report further comprises time information recording the at least one set of measurements, wherein,

the offset of the time information of the at least one group of measurement quantities relative to the time of the terminal equipment entering the idle mode is smaller than the preset duration time, and the reason for indicating the terminal equipment to stop recording the idle mode measurement quantities is that the signal strength of a downlink signal corresponding to a frequency point in the idle mode measurement configuration or a frequency point in the idle mode measurement configuration is lower than a specific threshold value; or alternatively

The offset of the time information of the at least one group of measurement quantities relative to the time of the terminal equipment entering the idle mode is larger than or equal to the preset duration, and the reason for indicating the terminal equipment to stop recording the idle mode measurement quantities is that the measurement duration reaches the preset duration.
The method according to any of claims 1-5, wherein the first information comprises a first flag bit for determining time information when the terminal device stops performing idle mode measurements.
The method of claim 6, wherein the first flag bit is used to indicate that the terminal device is not performing idle mode measurements for some or all of the time between the first time and the second time.
The method of claim 7, wherein the first flag bit is included in an information element IE corresponding to the second time for recording the measurement quantity.
The method according to claim 7 or 8, wherein the first time and the second time are relative times with reference to the time when the terminal device enters idle mode.
The method according to any one of claims 7-9, wherein the first time and the second time are recording times of a measured quantity.
The method according to any of claims 1-10, wherein the at least one set of measurement values comprises measurement values corresponding to at least one frequency point, respectively, and the first information comprises information indicating whether the measurement value corresponding to the at least one frequency point is an idle mode measurement value.
The method of claim 11, wherein the first information comprises a first bit map, the first bit map comprising a plurality of bits, each bit corresponding to a frequency point, and wherein a value of each bit is used to indicate whether a measurement of the corresponding frequency point is an idle mode measurement.
The method of claim 11 wherein the indication of whether the measurement corresponding to each frequency point is an idle mode measurement includes a flag bit, where the flag bit is included in an IE for carrying the measurement corresponding to each frequency point.
The method according to any of claims 1-10, wherein the recorded measurement report comprises a dedicated IE for carrying idle mode measurements.
The method according to any of claims 1-14, wherein in case an idle mode measurement is included in the recorded measurement report, the recorded measurement report further comprises second indication information indicating that an idle mode measurement is included in the recorded measurement report.
A method of reporting a recorded measurement report, comprising:

The network equipment sends a first message to the terminal equipment, wherein the first message is used for indicating the terminal equipment to report a recorded measurement report to the network equipment;

the network equipment receives a recorded measurement report reported by the terminal equipment, wherein the recorded measurement comprises at least one group of measurement quantity and first information;

and the network equipment determines whether the measurement quantity is an idle mode measurement quantity according to the first information, and/or the reason that the terminal equipment stops recording the idle mode measurement quantity, wherein the idle mode measurement quantity is obtained based on idle mode measurement configuration measurement.
The method according to claim 16, wherein the first information comprises a preset duration for which the terminal device performs idle mode measurements and/or a time at which the terminal device enters idle mode.
The method according to claim 17, wherein the recorded measurement report further comprises time information recording the at least one set of measurement quantities, wherein the network device determining whether the measurement quantity is an idle mode measurement quantity based on the first information, and/or a reason for the terminal device to stop recording idle mode measurement quantities, comprises:

If the offset of the time information for recording the at least one set of measurement quantities relative to the time of the terminal equipment entering the idle mode is smaller than the preset duration, determining that the reason for stopping recording the idle mode measurement quantities by the terminal equipment is that the signal strength of a downlink signal corresponding to a frequency point in the idle mode measurement configuration or a frequency point in the idle mode measurement configuration is lower than a specific threshold value; or alternatively

If the offset of the time information of the at least one set of measurement quantities relative to the time of the terminal equipment entering the idle mode is greater than or equal to the preset duration, determining that the reason why the terminal equipment stops recording the measurement quantities of the idle mode is that the measurement duration reaches the preset duration.
The method according to any of claims 16-18, wherein the first information comprises a first flag bit for determining time information when the terminal device stops performing idle mode measurements.
The method of claim 19, wherein the first flag bit is used to indicate that the terminal device is not performing idle mode measurements for some or all of the time between the first time and the second time.
The method of claim 20, wherein the first flag bit is included in an information element IE corresponding to the second time for recording the measurement quantity.
The method according to claim 20 or 21, wherein the first time and the second time are relative times with reference to the time when the terminal device enters idle mode.
The method according to any one of claims 20-22, wherein the first time and the second time are recording times of a measured quantity.
The method according to any of claims 16-23, wherein the at least one set of measurements comprises a set of measurements corresponding to at least one frequency point, respectively, and the first information comprises information indicating whether the set of measurements corresponding to each frequency point is an idle mode measurement.
The method of claim 24, wherein the first information comprises a first bit map, the first bit map comprising a plurality of bits, each bit corresponding to a frequency point, and wherein a value of each bit is used to indicate whether a measurement of the corresponding frequency point is an idle mode measurement.
The method of claim 24, wherein the indication information of whether the measurement corresponding to each frequency point is an idle mode measurement includes a flag bit, where the flag bit is included in an IE for carrying the measurement corresponding to each frequency point.
The method according to any of claims 16-23, wherein the recorded measurement report comprises a dedicated IE for carrying idle mode measurements.
The method according to any one of claims 16-27, further comprising:

in the case that the recorded measurement report includes first indication information, determining whether the measurement quantity is an idle mode measurement quantity according to the first information, wherein the first indication information is used for indicating that the recorded measurement report includes the idle mode measurement quantity.
A terminal device, comprising:

the communication unit is used for receiving a first message sent by the network equipment, and the first message is used for indicating the terminal equipment to report a recorded measurement report to the network equipment;

reporting a recorded measurement report to the network device, wherein the recorded measurement report comprises at least one set of measurement quantities and first information.
A network device, comprising:

a communication unit, configured to send a first message to a terminal device, where the first message is configured to instruct the terminal device to report a recorded measurement report to the network device, and receive the recorded measurement report reported by the terminal device, where the recorded measurement includes at least one set of measurement quantity and first information;

And the processing unit is used for determining whether the measurement quantity is an idle mode measurement quantity according to the first information and/or stopping recording the reason of the idle mode measurement quantity by the terminal equipment, wherein the idle mode measurement quantity is obtained based on idle mode measurement configuration measurement.
A terminal device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory, to perform the method of any of claims 1 to 15.
A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 15.
A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 15.
A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 15.
A computer program, characterized in that the computer program causes a computer to perform the method according to any one of claims 1 to 15.
A network device, comprising: a processor and a memory for storing a computer program, the processor being for invoking and running the computer program stored in the memory, performing the method of any of claims 16 to 28.
A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any of claims 16 to 28.
A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 16 to 28.
A computer program product comprising computer program instructions which cause a computer to perform the method of any of claims 16 to 28.
A computer program, characterized in that the computer program causes a computer to perform the method of any one of claims 16 to 28.