WO2023001032A1

WO2023001032A1 - Method and apparatus for reporting system information report, and terminal and storage medium

Info

Publication number: WO2023001032A1
Application number: PCT/CN2022/105383
Authority: WO
Inventors: 潘翔; 文鸣; 布巴卡·金巴·迪·阿达姆
Original assignee: 维沃移动通信有限公司
Priority date: 2021-07-19
Filing date: 2022-07-13
Publication date: 2023-01-26
Also published as: CN115643590A

Abstract

The present application belongs to the technical field of communications. Disclosed are a method and apparatus for reporting a system information report, and a terminal and a storage medium. The method for reporting a system information report in the embodiments of the present application comprises: a terminal determining acquisition condition information of a requested first target system information block on the basis of configuration information of a first on-demand system information report; and the terminal sending, to a network side device, a list of on-demand system information reports, wherein the list of on-demand system information reports comprises a second on-demand system information report, and the second on-demand system information report comprises the first on-demand system information report and/or a third on-demand system information report, the third on-demand system information report being generated after the first on-demand system information report is generated, and the first on-demand system information report being generated on the basis of the acquisition condition information of the first target system information block.

Description

System message report reporting method, device, terminal and storage medium

Cross References to Related Applications

This application claims the priority of the Chinese patent application with the application number 202110815788.1 filed on July 19, 2021, and the title of the invention is "Method, device, terminal and storage medium for reporting system information report", which is fully incorporated by reference this application.

technical field

The present application belongs to the technical field of communication, and in particular relates to a reporting method, device, terminal and storage medium of a system message report.

Background technique

The on-demand SI report is used to record and feed back the information about the request result of the system information block (intended SIB) requested to be allocated, so as to optimize the resource allocation of the system information requested to be allocated.

Currently, it has been confirmed that system information reports for request allocation are reported at the granularity of System Information Block (SIB), but the specific reporting method is not clear.

Contents of the invention

Embodiments of the present application provide a method, device, terminal, and storage medium for reporting system information reports, which can solve the problem of unclear reporting of on-demand SI.

In the first aspect, a method for reporting a system message report is provided, and the method includes:

The terminal determines the acquisition situation information of the requested first target system information block based on the configuration information of the system information report allocated by the first request;

The terminal sends a system message report list requesting allocation to the network side device, where the system message report list requesting allocation includes a second system information report requesting allocation, and the second system information report requesting allocation includes the first allocation requesting list and/or a third system message report requesting distribution, where the third requesting distribution system message report is generated after the first requesting distribution system message report is generated; the first requesting distribution of the system message report is generated The system message report is generated based on the acquisition situation information of the first target system message block.

In a second aspect, a device for reporting a system message report is provided, and the device includes:

The first determining module is configured to determine the acquisition situation information of the requested first target system information block based on the configuration information of the system information report assigned by the first request;

The first sending module is configured to send a system message report list requesting distribution to the network side device, the system message report list requesting distribution including a second system message report requesting distribution, the second system message report requesting distribution including The first system message report requesting allocation and/or the third system message report requesting allocation, where the third system message report requesting allocation is generated after the first system message report requesting allocation is generated; The system message report for the first request allocation is generated based on the acquisition situation information of the first target system message block.

In a third aspect, a terminal is provided. The terminal includes a processor, a memory, and a program or instruction stored in the memory and operable on the processor. When the program or instruction is executed by the processor The steps of the method described in the first aspect are realized.

In a fourth aspect, a terminal is provided, including a processor and a communication interface, wherein the processor is configured to: determine the acquisition status of the requested first target system message block based on the configuration information of the system message report assigned by the first request Information; the communication interface is used to: send a system message report list requesting distribution to the network side device, the system message report list requesting distribution includes a second system message report requesting distribution, the second system message requesting distribution The report includes the first system message report requesting allocation and/or the third system message report requesting allocation, and the third system message report requesting allocation is generated after the first system message report requesting allocation is generated ; The system message report for the first allocation request is generated based on the acquisition situation information of the first target system message block.

In a fifth aspect, a readable storage medium is provided, on which a program or an instruction is stored, and when the program or instruction is executed by a processor, the steps of the method as described in the first aspect are implemented.

A sixth aspect provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, the processor is used to run programs or instructions, and implement the method as described in the first aspect .

In a seventh aspect, a computer program/program product is provided, the computer program/program product is stored in a non-transitory storage medium, and the program/program product is executed by at least one processor to implement the program described in the first aspect Steps in the reporting method of the system message report.

In the embodiment of the present application, after determining the acquisition status information of the requested target system information block based on the configuration information of the system information report assigned by the first request, the terminal reports the system information report to the network side device, thereby clarifying the system information report The reporting method ensures that the network side can obtain the acquisition situation of the system information block requested for allocation, and can optimize the resource allocation of the configured broadcast system information block based on the analysis of the acquisition situation.

Description of drawings

FIG. 1 shows a structural diagram of a wireless communication system to which an embodiment of the present application is applicable;

FIG. 2 is a schematic flowchart of a method for reporting a system message report provided by an embodiment of the present application;

FIG. 3 is a schematic structural diagram of a reporting device for a system message report provided by an embodiment of the present application;

FIG. 4 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of a hardware structure of a terminal implementing an embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application will be clearly described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, but not all of them. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments in this application belong to the protection scope of this application.

The terms "first", "second" and the like in the description and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or described herein and that "first" and "second" distinguish objects. It is usually one category, and the number of objects is not limited. For example, there may be one or more first objects. In addition, "and/or" in the description and claims means at least one of the connected objects, and the character "/" generally means that the related objects are an "or" relationship.

It is worth noting that the technology described in the embodiment of this application is not limited to the Long Term Evolution (Long Term Evolution, LTE)/LTE-Advanced (LTE-Advanced, LTE-A) system, and can also be used in other wireless communication systems, such as code 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 (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 above-mentioned system and radio technology, and can also be used for other systems and radio technologies. The following description describes the New Radio (NR) system for illustrative purposes, and uses NR terminology in most of the following descriptions, but these techniques can also be applied to applications other than NR system applications, such as the 6th generation (6 ^th Generation, 6G) communication system.

FIG. 1 shows a structural diagram of a wireless communication system to which this embodiment of the present application is applicable. The wireless communication system includes a terminal 11 and a network side device 12 . Wherein, the terminal 11 can also be called a terminal device or a user terminal or a user equipment (User Equipment, UE), and the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer , personal digital assistant (Personal Digital Assistant, PDA), handheld computer, netbook, ultra-mobile personal computer (ultra-mobile personal computer, UMPC), mobile Internet device (Mobile Internet Device, MID), augmented reality (augmented reality, AR) /Virtual reality (virtual reality, VR) equipment, robots, wearable devices (Wearable Device), vehicle-mounted equipment (VUE), pedestrian terminal (PUE), smart home (home equipment with wireless communication functions, such as refrigerators, TVs, washing machine or furniture, etc.), wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart feet Chains, etc.), smart wristbands, smart clothing, game consoles, etc. It should be noted that, the embodiment of the present application does not limit the specific type of the terminal 11 . The network side device 12 may be a base station or a core network, where a base station may be called 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 Basic Service Set (BSS), Extended Service Set (ESS), Node B, Evolved Node B (eNB), Home Node B, Home Evolved Node B, WLAN access point, WiFi node, transmission 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 specific technical terms. It should be noted that in the embodiment of this 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.

The method, device, terminal, and storage medium for reporting system message reports provided by the embodiments of the present application will be described in detail below through some embodiments and application scenarios with reference to the accompanying drawings.

For Other SI except SIB1, including normal system information block (normal SIB) and positioning system information block (pos SIB) for positioning, its transmission methods can be divided into two types: periodic broadcast and based on UE request (on-demand ) broadcast.

Periodic broadcast: In the SI window corresponding to the calculated SI, the network side sends the SI according to the period si-Periodicity;

On-demand request broadcast: If there is no UE request, the network side will not send the SI; if the UE sends a request to the network side, the network side will send the SI within a period of time in the SI window corresponding to the calculated SI.

The broadcast SI of the On-demand request may include two optional implementations (Msg1-based and Msg3-based), and the network side may select one of them for configuration according to the implementation.

Based on Msg1: The network side provides the system information request configuration field SI-requestConfig or posSI-RequestConfig in the SIB1 scheduling information sent, which carries information such as preamble values for different SIs, dedicated RACH resources used, and masks. If the UE receives this field, it requests SI using the method based on Msg1.

Based on Msg3: The network side does not provide the system information request configuration field SI-requestConfig or posSI-RequestConfig in the scheduling information of SIB1 sent by the network side, then use the method based on Msg3 to request SI.

No matter what kind of on-demand SI request is used, the SI is used as the minimum request granularity, and the system message request at the SIB granularity is not supported. That is, multiple SIBs can be mapped in the same SI message, even if only one of the SIBs is needed, the entire SI message needs to be obtained.

For a connected UE, the SI can be obtained by reading broadcast or receiving dedicated signaling.

Read broadcast mode: If the active BWP of the UE has a common search space for receiving system information, the UE can obtain the SI on the active BWP after sending the request message DedicatedSIBRequest.

Dedicated signaling mode: If the active BWP of the UE does not have a common search space for receiving system information, the UE can obtain the SI through the RRC reconfiguration message after sending the request message DedicatedSIBRequest.

Fig. 2 is a schematic flowchart of a method for reporting a system message report provided by an embodiment of the present application. As shown in Fig. 2, the method includes the following steps:

Step 200, based on the configuration information of the system information report of the first request allocation, the terminal determines the acquisition status information of the requested first target system information block;

Step 210, the terminal sends a list of system message reports requesting distribution to the network side device, the list of system message reports requesting distribution includes a second system message report requesting distribution, and the second system message report requesting distribution includes the first A system message report requesting allocation and/or a third system message report requesting allocation, wherein the third system message report requesting allocation is generated after generating the first system message report requesting allocation; the first The system message report requesting allocation is generated based on the acquisition situation information of the first target system message block.

Optionally, the first on-demand SI report for allocation, the second system information report for allocation, and the third system information report for allocation can be used for at least one of the following:

a) Determine whether a certain SIB fails to request due to unreasonable random access (Random Access Channel, RACH) resource allocation;

b) Judging whether a certain SIB is frequently requested but not periodically broadcast;

c) Judging that certain SIBs are frequently requested by the same UE but placed in different SI messages.

Optionally, the terminal may include a UE capable of generating an on-demand SI report;

Optionally, in order to ensure that the network side device can obtain the acquisition status of the system information block normal SIB or pos SIB that is requested to be allocated and can optimize the configuration of the configured broadcast system information block resource configuration based on the analysis of the acquisition status, it is possible to generate an on-demand The UE capable of SI report may determine the acquisition situation information of the requested first target system information block based on the configuration information of the system information report assigned by the first request; and then may generate the second target system information block based on the acquisition situation information of the first target system information block A distribution-requesting system information report, and sending the distribution-requesting system information report list in which the first distribution-requesting system information report is located to the network side device.

Optionally, after the system information report for the first allocation request is generated, it may be determined to request the acquisition situation information of the second target system information block, and based on the acquisition situation information of the second target system information block, determine to generate the third request for allocation A system message report, or, judging whether to generate a system message report for the distribution of the third request;

Optionally, the configuration information adopted by the third system message report requesting distribution may include the configuration information of the first system message report requesting distribution;

Optionally, the configuration information reported by the system message for the first allocation request may be protocol-defined or preset or indicated by the network side device;

Optionally, after the configuration information of the first system message report requesting distribution is determined based on the protocol definition or preset or the network side device instruction, this configuration information may be used in subsequent generation of the third system message report requesting distribution.

Optionally, when the configuration information is used for the system message report allocated by the third request, the configuration of the system message report allocated by the first request can be adaptively configured for the system message report allocated by the third request.

Optionally, when reporting the system information report of the first request allocation, after the UE capable of generating an on-demand SI report requests the network to broadcast the on-demand SI, it can record the acquisition of the first target intended SIB according to the on-demand SI configuration In this case, generate the system message report (the first on-demand SI report) for the first request allocation, and cache the report in the UE; after receiving the on-demand SI report request from the network, the UE passes the radio resource control (Radio Resource Control, RRC) message to report the on-demand SI report list to the network.

Optionally, the system message report of the first request allocation includes at least one of the following:

a cell identifier of a cell corresponding to the first target system information block;

an identification of the first target system message block;

Timestamp when the target system information block was requested;

Situation information of each random access during the request process of the first target system information block;

The request mode of the first target system message block;

The request result of the first target system message block;

The reason why the first target sysmessage block request failed.

Optionally, the first system message report requesting distribution may be located in the first information field of the system message report list requesting distribution;

Optionally, the first information domain includes at least any one or any combination of the following information:

an identification of the first target system message block;

Timestamp when the target system information block was requested;

The request mode of the first target system message block;

The request result of the first target system message block;

The reason why the first target sysmessage block request failed.

Optionally, in this embodiment of the present application, the first information domain "on-Demand-SI-Report" is designed so that the network side device can perform network optimization according to the report.

Optionally, the identifier of the first target system message block includes at least one of the following:

the identification of the general system message block;

Identifier of the positioning system information block used for positioning.

Optionally, the identifier of the first target system message block may be located in the second information field of the system message report list requesting distribution;

Optionally, for the second information field, it may be an identifier of a common system information block, that is, a normal SIB identifier, or an identifier of a positioning system information block used for positioning, that is, a pos SIB identifier.

Optionally, the normal SIB identifier may be the type of the SIB.

For example, the second information field may include a pos SIB identifier, which may be used to indicate the type of the pos SIB, encryption (encrypted or not), GNSS type, SBAS type; GNSSSBAS wherein the second information field may include the pos SIB type and additional Information, this additional information is used to uniquely map out a certain pos SIB. In addition to the pos SIB type, the additional information requires 6 bits, including 1 bit of encrypted information, 3 bits of GNSS type information, and 2 bits of SBAS type information;

Optionally, for normal SIBs, each SIB can only be included in one of the SI messages; for pos SIBs, the same pos SIB corresponding to different GNSS/SBAS must be included in different SI messages; for all normal SIBs and pos SIB, the same type can only appear once in one SI message. And the pos SIB can also be encrypted by LMF, but the normal SIB cannot be encrypted.

Optionally, for the received encrypted pos SIB, if the UE does not have a corresponding secret key during its processing, the UE may discard the corresponding pos SIB signaling.

Optionally, the identifier of the positioning system information block is used to indicate at least one of the following:

Encryption information of positioning system information block, type of global navigation satellite system and type of satellite-based augmentation system;

The PosSchedulingInfo to which the positioning system information block belongs is located in the sequence position of posSchedulingInfoList.

Optionally, the scheduling indication information (PosSI-SchedulingInfo and SI-SchedulingInfo) of the pos SIBs (such as posSIB1-1~posSIB6-3) used for positioning and the normal SIBs (such as SIB2~SIB14) are not completely consistent. Compared with SIB, the on-demand SI report of pos SIB can introduce additional indication information.

Optionally, the pos SIB identifier may be used to indicate at least one of the following:

The type of the pos SIB, that is, the encryption status of the pos SIB (such as whether it is encrypted), the GNSS type, and the SBAS type;

The type of the pos SIB and the PosSchedulingInfo to which the pos SIB belongs are located in the sequence position of posSchedulingInfoList.

For example, a pos SIB identifier may be the type of the pos SIB and the PosSchedulingInfo to which the pos SIB belongs is located in the sequence position of the posSchedulingInfoList, wherein, a network side device such as a base station can map out the intended pos SIB according to the timestamp and sequence information; among them, it may include pos SIB type and additional information, the additional information is used to uniquely map a certain pos SIB; wherein, in addition to the pos SIB type, the additional information also requires 5 bits of sequence information;

Optionally, the reason why the first target system message block request fails includes at least one of the following:

no valid key;

Random access failed.

Optionally, the reason for the failure of the first target system message block request may be located in the third information field of the system message report list requesting allocation;

Optionally, for the third information field, at least one of the following reasons may be included:

no valid key;

RACH competition failed.

Optionally, in this embodiment of the present application, the second information field "intendedSIB-TypeInfo" and the third information field "causeOfFailure" are designed to identify and process normal SIBs and pos SIBs differently.

Optionally, the identifier of the first target system information block includes the identifier of the positioning system information block, and the terminal does not store the valid key and discards the acquired encrypted positioning system information block, resulting in a system message requesting allocation If the request fails, the reason why the first target system message block request fails includes the invalid key.

Optionally, when the type of the first target system information block belongs to the pos SIB type, and the on-demand SI request fails because the UE discards the obtained encrypted pos SIB without storing a valid key, the value of the third information field may be " No valid key".

Optionally, in a case where the number of times the terminal fails to obtain the first target system information block by initiating random access exceeds a first threshold, the reason for the failure of the first target system information block request includes that the random access failed to enter the competition.

Optionally, when the number of times the UE fails to acquire the SIB by initiating RACH exceeds the maximum value configured by the network, the value of the third information field may be "RACH competition failure".

Optionally, the method also includes:

Before the step of obtaining situation information of the first target system information block of the determination request, the terminal receives a first request message sent by the network side device, and the first request message is used to request the terminal for the The list of system message reports assigned by the first request.

Optionally, after the UE enters the connected state, it may explicitly or implicitly indicate to the network side device that it has saved the system information report requesting allocation; then the network side device may send a first request message to the UE, requesting the terminal The first system information report list for requesting allocation, after receiving the first request message, the UE may send the system information report for requesting allocation to the network side device.

Optionally, the method also includes:

Before the step of the terminal receiving the first request message sent by the network-side device, the terminal sends a terminal capability to the network-side device, where the terminal capability is used to indicate whether the terminal is capable of reporting a random access report capability and/or whether the terminal has the capability of reporting the system message report of the first allocation request.

Optionally, the UE capable of generating an on-demand SI report may report the UE capability to the network side device after the network requests the UE capability.

Optionally, this capability can be included in other existing capabilities, such as "capability of reporting 2-step RACH report", that is, when the UE reports the capability indication 2steprach-Report-r16, it also indicates that the UE has the ability to report the first Ability to request assigned system message reports.

Optionally, the configuration information reported by the system message for the first allocation request includes at least one of the following:

First information used to indicate whether a system message report of the first request allocation can be generated;

used to record the second information of the area of the system message report allocated by the first request;

The third information used to record the maximum number of system message reports requesting allocation that can be stored by the terminal.

Optionally, when the UE records the acquisition status information of the requested first target system information block according to the configuration information of the system information report assigned by the first request, the configuration information of the system information report assigned by the first request may at least include the following at least one item:

The first information used to indicate whether the system message report assigned by the first request can be generated, that is, the first information is used to indicate whether to enable on-demand SI report;

The second information used to record the area of the system message report allocated by the first request, that is, the second information is used to record the area of the first on-demand SI report;

Used to record the third information of the maximum number of system message reports that the first requests to allocate, that is, the third information may be used to record the third information of the maximum number of system message reports that can be stored by the terminal;

Optionally, in order to reduce the impact of report buffering on UE storage, various reports usually have a storage limit.

Taking RA report as an example, when the UE successfully completes 4step RACH, if the currently stored RA report does not exceed maxRAReport, it can continue to generate a new RA report; otherwise, the UE will not generate a new RA report. For example, maxRAReport can be equal to 8.

For example, the on-demand SI report configuration and reporting process may include the following steps:

Step a1. The network side device can request the UE capability from the UE. After receiving the request, the UE can report the UE capability, including whether it supports the ability to generate an on-demand SI report.

Step a2. After the network side device obtains the UE capability, it can send the configuration information of the system information report of the first request allocation to the UE according to the network optimization requirements and the UE capability, that is, the on-demand SI report configuration, including the enable switch, on- The target area collected by demand SI report (such as cell list or TA list), record the maximum number of on-demand SI report.

Step a3. The UE requests the first target on-demand SI from the network side device and generates the first on-demand SI report according to the request result and configuration.

Step a4. After the UE enters the connected state, the network side device can request the first on-demand SI report to the UE through the UEInformationRequest.

Step a5. The UE sends the on-demand SI report list to the network side device.

Step a6. The network side device sends the first on-demand SI report to the base station corresponding to the cell through an Access And Mobility Indication message according to the cell identifier in the first on-demand SI report.

Step a7. After receiving the first on-demand SI report, the base station corresponding to the cell performs on-demand SI resource configuration optimization according to the report information.

Optionally, the embodiment of the present application introduces an optional first on-demand SI report configuration, including enabling switches and recording areas, so as to generate an on-demand SI report for the target area

Optionally, the method also includes at least one of the following:

In a case where the first information indicates that the first system message report requesting allocation can be generated, the terminal generates the first system message report requesting allocation;

In a case where the first information indicates that the system message report for the first allocation request cannot be generated, the terminal does not generate the system message report for the first allocation request;

If the first information is missing, the terminal does not generate the first system message report requesting allocation.

Optionally, "whether to enable on-demand SI report" is the first information, and the first information may be configured by the network according to optimization requirements and UE capabilities.

Optionally, if the value of the first information is "Yes", it means that the system message report for the first allocation request can be generated, and the UE can record the first on-demand SI report; if the value of the first information is " No", it means that the system message report of the first request allocation cannot be generated, and the UE is not allowed to record the first on-demand SI report; if the first information is missing, the UE is not allowed to record the first on-demand SI report .

Optionally, the method also includes at least one of the following:

If the first information indicates that the system message report requesting distribution cannot be generated, the terminal does not generate the first system message report requesting distribution;

If the first information is missing, the terminal generates a system message report requesting distribution of the first.

Optionally, if the value of the first information is "Yes", it means that the system message report for the first allocation request can be generated, and the UE can record the first on-demand SI report; if the value of the first information is "No ", it means that the system message report requesting allocation cannot be generated, and the UE is not allowed to record the first on-demand SI report; if the first information is missing, the UE is allowed to record the first on-demand SI report.

Optionally, the second information includes at least one of the following:

Tracking area TA list;

District list.

Optionally, the second information of the area where the first on-demand SI report is recorded may be configured by the network side device according to optimization requirements and UE capabilities;

Optionally, the second information may be at least one of a TA list and a cell list.

Optionally, in a case where the second information is missing, the area for recording the system message report of the first allocation request is any area.

Optionally, if the second information is missing, it may indicate that the first on-demand SI report can be recorded in any area.

Optionally, the third information is a fixed value or is determined based on network side device configuration.

Optionally, the third information that records the maximum number of first on-demand SI reports may be a fixed value or configured by the network according to optimization requirements and UE capabilities.

Optionally, the method also includes:

After determining the acquisition situation information of the first target system message block, if the terminal determines that the number of cached system message reports allocated by historical requests is less than the third information, the terminal determines the second target system Information about the acquisition status of the message block;

The terminal generates the system information report of the third request allocation based on the acquisition situation information of the second target system information block.

Optionally, after the UE records the acquisition of the first target intended SIB according to the first on-demand SI configuration, when the number of cached historical on-demand SI reports is less than the maximum number limited by the third information, the UE may record Acquisition of the new second target intended SIB, and generate a new on-demand SI report, that is, the third on-demand SI report.

Optionally, the second target system information block may be the same as or different from the first target system information block, for example, if the request for the first target system information block fails, the request may be made again, and the re-request The second target system information block requested once is the same as the first target system information block; for example, after determining the acquisition situation information of the first target system information block, a second target system information block different from the first target system information block can be requested .

Optionally, the method also includes:

After the determination of the acquisition situation information of the first target system message block, if the terminal determines that the number of system message reports allocated by the cached historical requests is equal to the third information, the terminal determines the second target system Information about the acquisition status of the message block;

The terminal determines whether to generate the third system message report requesting distribution based on the information about the acquisition status of the second target system message block and the historical system message report requesting distribution stored in the terminal.

Optionally, after the UE records the acquisition of the first target intended SIB according to the first on-demand SI configuration, when the number of cached historical on-demand SI reports is equal to the maximum number limited by the third information, the UE records the new The acquisition situation of the second target intended SIB, and according to the acquisition situation of the second target intended SIB and the type of the system message report (historical on-deman SI report) allocated by the currently stored historical request determines whether to generate a new on-demand SI report, namely The third on-demand SI report.

Optionally, based on the acquisition situation information of the second target system information block, the terminal,

And, determining whether to generate the third system message report requesting distribution from the stored historical system message report requested in the terminal, including:

If the second target system information block is successfully obtained, determine not to generate the system information report for the third request allocation;

If the acquisition of the second target system message block fails, and there is no system message report for the request allocation that the request result is successful in the system message report of the historical request allocation, determine not to generate the system for the third request allocation news report;

If the acquisition of the second target system message block fails, and there is a system message report of a request allocation that the request result is successful in the system message report of the historical allocation request, determine to generate the system message of the third allocation request report, deleting any one of the system message reports assigned by the historical request or the earliest system message report assigned by the request with a successful request result.

Optionally, this embodiment of the present application introduces on-demand SI report priority, that is, preferentially stores reports of on-demand SI failures.

Optionally, when determining whether to generate the third on-demand SI report, it may be determined based on at least one of the following:

If the second target intended SIB is obtained successfully, the third on-demand SI report will not be generated;

If the acquisition of the intended SIB of the second target fails, and there is no on-demand SI report whose request result is successful in the system message report assigned by the historical request, the third on-demand SI report will not be generated;

If the acquisition of the intended SIB of the second target fails, and there is an on-demand SI report whose request result is successful in the system message report of historical request allocation, generate a third on-demand SI report, and delete any or the earliest stored request The result is a successful on-demand SI report, save the newly generated third on-demand SI report.

Optionally, the method also includes:

Before sending the list of system message reports requesting distribution to the network-side device, the terminal indicates to the network-side device whether the terminal has cached the first system message report requesting distribution.

Optionally, before sending the first on-demand SI report request to the UE, the network side device may first confirm that the UE has cached the first on-demand SI report.

Optionally, after the UE is connected to the network side device, it may explicitly or implicitly indicate to the network side device that the first on-demand SI report has been cached.

Optionally, the terminal indicates to the network side device whether the terminal has cached the system message report for the first allocation request, including:

The terminal sends a first indication message to the network side device, where the first indication information is used to directly indicate whether the terminal has cached the system message report for the first allocation request;

Wherein, the first indication message includes at least one of the following:

Radio resource control setting completion information;

Radio resource control recovery completion information;

RRC reconfiguration complete information;

RRC reestablishment completion information;

Terminal information response.

Optionally, the manner in which the UE explicitly indicates that the first on-demand SI report has been cached may be to send an RRC message, and the RRC message may be:

Radio resource control setup completion information, such as RRCSetupComplete;

Radio resource control recovery completion information, such as RRCResumeComplete;

Radio resource control reconfiguration complete information, such as RRCReconfigurationComplete;

Radio resource control reestablishment completion information, such as RRCReestablishmentComplete;

Terminal information response, such as UEInformationResponse.

Optionally, the terminal capability is also used to indicate whether the terminal has cached the system message report of the first request for allocation.

Optionally, the UE implicitly indicates that the on-demand SI report has been cached by associating the UE capability. If the UE reports that it has the ability to generate an on-demand SI report or other capabilities, the network considers that the UE has cached the on-demand SI report; Otherwise, the network considers that the UE has not cached the on-demand SI report.

Optionally, other capabilities reported by the UE may be the ability to generate RACH reports.

Optionally, the RRC message of the on-demand SI report request sent by the network side device to the UE may be UEInformationRequest.

Optionally, the UE may report the on-demand SI report to the network side device through an RRC message, wherein the RRC message may be a UEInformationResponse, and the report result includes an on-demand SI report list (one or more reports).

Optionally, the following is an example flow of the reporting method of the system message report:

Step b1. The network side device requests UE capabilities from the UE, and the UE reports the UE capabilities after receiving the request, including whether it supports the ability to generate on-demand SI reports.

Step b2. After the network side device obtains the UE capability, according to the optimization requirements of the network side device and the UE capability, optionally send the first on-demand SI report configuration to the UE, including enabling the switch and collecting the first on-demand SI report The target area (such as cell list or TA list), the terminal can record the maximum number of on-demand SI report.

Step b3. The UE requests the first target on-demand SI from the network side device and generates the first on-demand SI report according to the request result and configuration.

Step b4. After the UE enters the connected state, it may explicitly or implicitly indicate that it has saved the first on-demand SI report.

Step b5. The network side device can request the first on-demand SI report to the UE through the UEInformationRequest.

Step b6. UE sends on-demand SI report list to the network side device.

The method for reporting on-demand SI report provided by the embodiment of this application introduces on-demand SI report configuration and reporting, introduces on-demand SI report configuration and reporting, defines on-demand SI report, and differentiates normal in the report SIB and pos SIB; so that the network side can optimize the resource configuration of the on-demand SIB and pos SIB based on the on-demand SI report reported by the UE.

It should be noted that, the system message report reporting method provided by the embodiment of the present application may be executed by the system message report reporting device, or the device used to execute the system message report reporting method in the system message report reporting device control module. In the embodiment of the present application, the method for reporting the system message report performed by the device for reporting the system message report is taken as an example to describe the device for reporting the system message report provided in the embodiment of the present application.

Fig. 3 is a schematic structural diagram of a device for reporting a system message report provided by an embodiment of the present application. As shown in Fig. 3 , the device includes: a first determining module 310 and a first sending module 320; wherein:

The first determining module 310 is configured to determine, based on the configuration information of the system message report allocated by the first request, the acquisition situation information of the requested first target system message block;

The first sending module 320 is configured to send a list of system message reports requesting distribution to the network side device, where the list of system message reports requesting distribution includes a second system message report requesting distribution, and the second system message report requesting distribution includes The first system message report requesting allocation and/or the third system message report requesting allocation, where the third system message report requesting allocation is generated after the first system message report requesting allocation is generated; The system message report for the first request allocation is generated based on the acquisition situation information of the first target system message block.

Optionally, the means for reporting the system information report determines the acquisition status information of the requested first target system information block through the first determination module 310 based on the configuration information of the system information report requested for distribution by the first request; 320 Send a system message report list requesting distribution to the network side device; wherein, the system message report list requesting distribution includes a second system message report requesting distribution, and the second system message report requesting distribution includes the first A system message report requesting allocation and/or a third system message report requesting allocation, wherein the third system message report requesting allocation is generated after generating the first system message report requesting allocation; the first The system message report requesting allocation is generated based on the acquisition situation information of the first target system message block.

an identification of the first target system message block;

Timestamp when the target system information block was requested;

The request mode of the first target system message block;

The request result of the first target system message block;

The reason why the first target sysmessage block request failed.

the identification of the general system message block;

Identifier of the positioning system information block used for positioning.

no valid key;

Random access failed.

Optionally, the device also includes:

The first receiving module is configured to, before the step of obtaining situation information of the first target system information block of the determination request, the terminal receives a first request message sent by the network side device, and the first request message is used for requesting the first requested system message report list from the terminal.

Optionally, the device also includes:

The second sending module is configured to send the terminal capability to the network side device before the terminal receives the first request message sent by the network side device, and the terminal capability is used to indicate whether the terminal is capable of reporting random Capability of accessing the report and/or whether the terminal has the capability of reporting the system message report of the first request for distribution.

Optionally, the device also includes at least one of the following:

A first generation module, configured to generate a system message report for the first allocation request when the first information indicates that the system message report for the first allocation request can be generated;

A second generating module, configured to not generate the first system message report requesting distribution when the first information indicates that the system message report requesting distribution cannot be generated;

A third generating module, configured to not generate a system message report for the first allocation request if the first information is missing.

Optionally, the device also includes at least one of the following:

A fourth generating module, configured to generate a system message report for the first allocation request when the first information indicates that the system message report for the first allocation request can be generated;

A fifth generating module, configured to not generate the first system message report requesting distribution when the first information indicates that the system message report requesting distribution cannot be generated;

The sixth generation module is configured to generate a system message report of the first request for distribution if the first information is missing.

Optionally, the second information includes at least one of the following:

Tracking area TA list;

District list.

Optionally, when the second information is missing, the area for recording the system message report of the first allocation request is any area.

Optionally, the device also includes:

The first update module is configured to determine, after the determination of the acquisition situation information of the first target system information block, when the terminal determines that the number of cached system information reports allocated by historical requests is less than the third information. information about the acquisition status of the second target system message block;

A seventh generation module, configured to generate the system information report for the third request allocation based on the acquisition situation information of the second target system information block.

Optionally, the device also includes:

The second update module is configured to determine, after the determination of the acquisition situation information of the first target system information block, when the terminal determines that the number of system information reports allocated by the cached historical requests is equal to the third information. information about the acquisition status of the second target system message block;

A first judging module, configured to judge whether to generate the third system message requesting distribution based on the acquisition status information of the second target system message block and the historical system message report requesting distribution stored in the terminal Report.

Optionally, the first judging module is also used for:

Optionally, the device also includes:

A first indicating module, configured to indicate to the network side device whether the terminal has cached the first system message report requesting distribution before sending the system message report list requesting distribution to the network side device .

Optionally, the first indication module is also used for:

sending a first indication message to the network side device, where the first indication information is used to directly indicate whether the terminal has cached the system message report for the first request allocation;

Wherein, the first indication message includes at least one of the following:

Radio resource control setting completion information;

Radio resource control recovery completion information;

RRC reconfiguration complete information;

RRC reestablishment completion information;

Terminal information response.

The reporting device of the system message report in the embodiment of the present application may be a device, a device with an operating system or an electronic device, or a component, an integrated circuit, or a chip in a terminal. The apparatus or electronic equipment may be a mobile terminal or a non-mobile terminal. Exemplarily, the mobile terminal may include but not limited to the types of terminals 11 listed above, and the non-mobile terminal may be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television ( television, TV), teller machines or self-service machines, etc., are not specifically limited in this embodiment of the present application.

The device for reporting system message reports provided by the embodiment of the present application can implement the various processes implemented by the method embodiment in FIG. 2 and achieve the same technical effect. To avoid repetition, details are not repeated here.

Optionally, FIG. 4 is a schematic structural diagram of a communication device provided by an embodiment of the present application. As shown in FIG. And the program or instruction that can run on the processor 401, for example, when the communication device 400 is a terminal, when the program or instruction is executed by the processor 401, realizes the various processes of the reporting method embodiment of the above-mentioned system message report, and Can achieve the same technical effect. When the communication device 400 is a network-side device, when the program or instruction is executed by the processor 401, each process of the above-mentioned system message report reporting method embodiment can be achieved, and the same technical effect can be achieved. In order to avoid repetition, details are not repeated here. .

The embodiment of the present application also provides a terminal, including a processor and a communication interface, the processor is configured to: determine the acquisition status information of the requested first target system message block based on the configuration information of the system message report assigned by the first request; The communication interface is configured to: send a system message report list requesting distribution to the network side device, the system message report list requesting distribution includes a second system message report requesting distribution, and the second system message report requesting distribution includes The first system message report requesting allocation and/or the third system message report requesting allocation, where the third system message report requesting allocation is generated after the first system message report requesting allocation is generated; The system message report for the first request allocation is generated based on the acquisition situation information of the first target system message block. This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment, and each implementation process and implementation mode of the above-mentioned method embodiment can be applied to this terminal embodiment, and can achieve the same technical effect. Specifically, FIG. 5 is a schematic diagram of a hardware structure of a terminal implementing an embodiment of the present application.

The terminal 500 includes, but is not limited to: a radio frequency unit 501, a network module 502, an audio output unit 503, an input unit 504, a sensor 505, a display unit 506, a user input unit 507, an interface unit 508, a memory 509, and a processor 510, etc. at least some of the components.

Those skilled in the art can understand that the terminal 500 can also include a power supply (such as a battery) for supplying power to various components, and the power supply can be logically connected to the processor 510 through the power management system, so as to manage charging, discharging, and power consumption through the power management system. Management and other functions. The terminal structure shown in FIG. 5 does not constitute a limitation on the terminal, and the terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange different components, which will not be repeated here.

It should be understood that, in the embodiment of the present application, the input unit 504 may include a graphics processor (Graphics Processing Unit, GPU) 5041 and a microphone 5042, and the graphics processor 5041 is used for the image capture device ( Such as the image data of the still picture or video obtained by the camera) for processing. The display unit 506 may include a display panel 5061, and the display panel 5061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 507 includes a touch panel 5071 and other input devices 5072 . The touch panel 5071 is also called a touch screen. The touch panel 5071 may include two parts, a touch detection device and a touch controller. Other input devices 5072 may include, but are not limited to, physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be repeated here.

In the embodiment of the present application, the radio frequency unit 501 receives the downlink data from the network side device, and processes it to the processor 510; in addition, sends the uplink data to the network side device. Generally, the radio frequency unit 501 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

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

The processor 510 may include one or more processing units; optionally, the processor 510 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, application programs or instructions, etc., Modem processors mainly handle wireless communications, such as baseband processors. It can be understood that the foregoing modem processor may not be integrated into the processor 510 .

Wherein, the processor 510 is used for:

Based on the configuration information of the system information report assigned by the first request, determine the acquisition situation information of the requested first target system information block;

sending a system message report list requesting allocation to the network side device, the system message report list requesting allocation including a second system information report requesting allocation, the second requesting allocation system information report including the first requesting allocation A system message report and/or a third system message report requesting distribution, the third system message report requesting distribution is generated after the first system message report requesting distribution is generated; the system message report requesting distribution of the first The message report is generated based on the acquisition status information of the first target system message block.

an identification of the first target system message block;

Timestamp when the target system information block was requested;

The request mode of the first target system message block;

The request result of the first target system message block;

The reason why the first target sysmessage block request failed.

the identification of the general system message block;

Identifier of the positioning system information block used for positioning.

no valid key;

Random access failed.

Optionally, the processor 510 is also used for:

Before the step of obtaining situation information of the first target system message block of the determination request, receiving a first request message sent by the network side device, the first request message is used to request the terminal for the first request List of assigned system message reports.

Optionally, the processor 510 is also used for:

Before the step of the terminal receiving the first request message sent by the network-side device, sending the terminal capability to the network-side device, where the terminal capability is used to indicate whether the terminal has the capability of reporting a random access report and/or Or whether the terminal is capable of reporting the system message report of the first allocation request.

Optionally, the processor 510 is also used for at least one of the following:

If the first information indicates that a system message report for the first allocation request can be generated, generate a system message report for the first allocation request;

When the first information indicates that the system message report for the first allocation request cannot be generated, the system message report for the first allocation request is not generated;

If the first information is missing, the first system message report requesting allocation is not generated.

Optionally, the processor 510 is also used for at least one of the following:

If the first information indicates that the system message report requesting distribution cannot be generated, not generating the first system message report requesting distribution;

In case the first information is missing, a system message report of the first request allocation is generated.

Optionally, the second information includes at least one of the following:

Tracking area TA list;

District list.

Optionally, the processor 510 is also used for:

After determining the acquisition situation information of the first target system information block, when the terminal determines that the number of cached system information reports allocated by historical requests is less than the third information, determine the information of the second target system information block obtain situational information;

Based on the acquisition situation information of the second target system information block, generate the system information report of the third request allocation.

Optionally, the processor 510 is also used for:

After determining the acquisition situation information of the first target system information block, when the terminal determines that the number of cached system information reports allocated by historical requests is equal to the third information, determine the information of the second target system information block obtain situational information;

Optionally, the processor 510 is also used for:

Before sending the list of system message reports requesting distribution to the network side device, indicating to the network side device whether the terminal has cached the first system message report requesting distribution.

Optionally, the processor 510 is also used for:

Wherein, the first indication message includes at least one of the following:

Radio resource control setting completion information;

Radio resource control recovery completion information;

RRC reconfiguration complete information;

RRC reestablishment completion information;

Terminal information response.

Optionally, the terminal capability is also used to indicate whether the terminal has cached the system message report of the first request for distribution.

The embodiment of the present application also provides a readable storage medium, the readable storage medium stores a program or an instruction, and when the program or instruction is executed by the processor, each process of the above-mentioned system message report reporting method embodiment is implemented, and The same technical effect can be achieved, so in order to avoid repetition, details will not be repeated here.

Wherein, the processor is the processor in the terminal described in the foregoing embodiments. The readable storage medium includes computer readable storage medium, such as computer read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk, etc.

The embodiment of the present application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the reporting method of the above-mentioned system message report The various processes of the embodiment can achieve the same technical effect, so in order to avoid repetition, details are not repeated here.

It should be understood that the chip mentioned in the embodiment of the present application may also be called a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip.

The embodiment of the present application also provides a computer program/program product, the computer program/program product is stored in a non-transitory storage medium, and the program/program product is executed by at least one processor to implement the above-mentioned system message Each process of the reporting method embodiment of the report can achieve the same technical effect, so in order to avoid repetition, details are not repeated here.

It should be noted that, in this document, the term "comprising", "comprising" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or apparatus comprising a set of elements includes not only those elements, It also includes other elements not expressly listed, or elements inherent in the process, method, article, or device. Without further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of additional identical elements in the process, method, article, or apparatus comprising that 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. Functions are performed, for example, the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

Through the description of the above embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is better implementation. Based on such an understanding, the technical solution of the present application can be embodied in the form of computer software products, which are stored in a storage medium (such as ROM/RAM, magnetic disk, etc.) , optical disc), including several instructions to enable a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in various embodiments of the present application.

The embodiments of the present application have been described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementations. The above-mentioned specific implementations are only illustrative and not restrictive. Those of ordinary skill in the art will Under the inspiration of this application, without departing from the purpose of this application and the scope of protection of the claims, many forms can also be made, all of which belong to the protection of this application.

Claims

A reporting method for a system message report, comprising:

The terminal determines the acquisition situation information of the requested first target system information block based on the configuration information of the system information report allocated by the first request;

The terminal sends a system message report list requesting allocation to the network side device, where the system message report list requesting allocation includes a second system information report requesting allocation, and the second system information report requesting allocation includes the first allocation requesting list and/or a third system message report requesting distribution, where the third requesting distribution system message report is generated after the first requesting distribution system message report is generated; the first requesting distribution of the system message report is generated The system message report is generated based on the acquisition situation information of the first target system message block.
The method for reporting a system message report according to claim 1, wherein the system message report for the first request allocation includes at least one of the following:

a cell identifier of a cell corresponding to the first target system information block;

an identification of the first target system message block;

Timestamp when the target system information block was requested;

Situation information of each random access during the request process of the first target system information block;

The request mode of the first target system message block;

The request result of the first target system message block;

The reason why the first target sysmessage block request failed.
The method for reporting a system message report according to claim 2, wherein the identifier of the first target system message block includes at least one of the following:

the identification of the general system message block;

Identifier of the positioning system information block used for positioning.
The method for reporting a system message report according to claim 3, wherein the identifier of the positioning system information block is used to indicate at least one of the following:

Encryption information of positioning system information block, GNSS type and SBAS type;

The PosSchedulingInfo to which the positioning system information block belongs is located in the sequence position of posSchedulingInfoList.
The method for reporting a system message report according to claim 3, wherein the reasons for the failure of the first target system message block request include at least one of the following:

no valid key;

Random access failed.
The method for reporting a system information report according to claim 5, wherein the identification of the first target system information block includes the identification of the positioning system information block, and the terminal does not store the effective key and discards the acquisition In the case that the encrypted location system information block results in a system information request requesting allocation failure, the reason for the failure of the first target system information block request includes the lack of a valid key.
The method for reporting a system message report according to claim 5, wherein when the number of times the terminal fails to obtain the system message block of the first target by initiating random access exceeds a first threshold, the first target The reason for the failure of the system information block request includes the failure of the random access competition.
The method for reporting a system message report according to any one of claims 1-7, wherein the method further comprises:

Before the step of obtaining situation information of the first target system information block of the determination request, the terminal receives a first request message sent by the network side device, and the first request message is used to request the terminal for the The list of system message reports assigned by the first request.
The method for reporting a system message report according to claim 8, wherein the method further comprises:

Before the step of the terminal receiving the first request message sent by the network-side device, the terminal sends a terminal capability to the network-side device, where the terminal capability is used to indicate whether the terminal is capable of reporting a random access report capability and/or whether the terminal has the capability of reporting the system message report of the first allocation request.
The method for reporting a system message report according to any one of claims 1-7, wherein the configuration information of the system message report for the first request allocation includes at least one of the following:

First information used to indicate whether a system message report of the first request allocation can be generated;

used to record the second information of the area of the system message report allocated by the first request;

The third information used to record the maximum number of system message reports requesting allocation that can be stored by the terminal.
The method for reporting a system message report according to claim 10, wherein the method further comprises at least one of the following:

In a case where the first information indicates that the first system message report requesting allocation can be generated, the terminal generates the first system message report requesting allocation;

In a case where the first information indicates that the system message report for the first allocation request cannot be generated, the terminal does not generate the system message report for the first allocation request;

If the first information is missing, the terminal does not generate the first system message report requesting allocation.
The method for reporting a system message report according to claim 10, wherein the method further comprises at least one of the following:

In a case where the first information indicates that the first system message report requesting allocation can be generated, the terminal generates the first system message report requesting allocation;

If the first information indicates that the system message report requesting distribution cannot be generated, the terminal does not generate the first system message report requesting distribution;

If the first information is missing, the terminal generates a system message report requesting distribution of the first.
The method for reporting a system message report according to claim 10, wherein the second information includes at least one of the following:

Tracking area TA list;

District list.
The method for reporting a system message report according to claim 10, wherein, in the case that the second information is missing, the area for recording the system message report for the first allocation request is any area.
The method for reporting a system message report according to claim 10, wherein the third information is a fixed value or is determined based on configuration of a network side device.
The method for reporting a system message report according to any one of claims 1-7, wherein the method further comprises:

After determining the acquisition situation information of the first target system information block, if the terminal determines that the number of cached system information reports allocated by historical requests is less than the third information, the terminal determines the second target system information block access to information;

The terminal generates the system information report of the third request allocation based on the acquisition situation information of the second target system information block.
The method for reporting a system message report according to any one of claims 1-7, wherein the method further comprises:

After the determination of the acquisition situation information of the first target system information block, when the terminal determines that the number of system information reports allocated by the cached historical requests is equal to the third information, the terminal determines the second target system information block access to information;

The terminal determines whether to generate the third system message report requesting distribution based on the information about the acquisition status of the second target system message block and the historical system message report requesting distribution stored in the terminal.
The method for reporting a system message report according to claim 17, wherein the terminal is based on the acquisition situation information of the second target system message block, and the system message report allocated by the historical request stored in the terminal, Judging whether to generate the system message report for the third request allocation includes:

If the second target system information block is successfully obtained, determine not to generate the system information report for the third request allocation;

If the acquisition of the second target system message block fails, and there is no system message report for the request allocation that the request result is successful in the system message report of the historical request allocation, determine not to generate the system for the third request allocation news report;

If the acquisition of the second target system message block fails, and there is a system message report of a request allocation that the request result is successful in the system message report of the historical allocation request, determine to generate the system message of the third allocation request report, deleting any one of the system message reports assigned by the historical request or the earliest system message report assigned by the request with a successful request result.
The method for reporting a system message report according to any one of claims 1-8, wherein the method further comprises:

Before sending the list of system message reports requesting distribution to the network-side device, the terminal indicates to the network-side device whether the terminal has cached the first system message report requesting distribution.
The method for reporting a system message report according to claim 19, wherein the terminal indicates to the network side device whether the terminal has cached the system message report of the first request for allocation, comprising:

The terminal sends a first indication message to the network side device, where the first indication information is used to directly indicate whether the terminal has cached the system message report for the first allocation request;

Wherein, the first indication message includes at least one of the following:

Radio resource control setting completion information;

Radio resource control recovery completion information;

RRC reconfiguration complete information;

RRC reestablishment completion information;

Terminal information response.
The method for reporting a system message report according to claim 9, wherein the terminal capability is further used to indicate whether the terminal has cached the system message report that the first request is allocated.
A reporting device for a system message report, the device comprising:

A first determining module, configured to determine the acquisition situation information of the requested first target system information block based on the configuration information of the system information report assigned by the first request;

The first sending module is configured to send a system message report list requesting distribution to the network side device, the system message report list requesting distribution including a second system message report requesting distribution, the second system message report requesting distribution including The first system message report requesting allocation and/or the third system message report requesting allocation, where the third system message report requesting allocation is generated after the first system message report requesting allocation is generated; The system message report for the first request allocation is generated based on the acquisition status information of the first target system message block.
The reporting device for a system message report according to claim 22, wherein the system message report for the first request allocation includes at least one of the following:

a cell identifier of a cell corresponding to the first target system information block;

an identification of the first target system message block;

Timestamp when the target system information block was requested;

Situation information of each random access during the request process of the first target system information block;

The request mode of the first target system message block;

The request result of the first target system message block;

The reason why the first target sysmessage block request failed.
The device for reporting system information reports according to claim 23, wherein the identifier of the first target system information block includes at least one of the following:

the identification of the general system message block;

Identifier of the positioning system information block used for positioning.
The device for reporting system information reports according to claim 24, wherein the identifier of the positioning system information block is used to indicate at least one of the following:

Encryption information of positioning system information block, type of global navigation satellite system and type of satellite-based augmentation system;

The PosSchedulingInfo to which the positioning system information block belongs is located in the sequence position of posSchedulingInfoList.
The device for reporting system information reports according to claim 24, wherein the reasons for the failure of the first target system information block request include at least one of the following:

no valid key;

Random access failed.
The device for reporting system information reports according to claim 26, wherein the identification of the first target system information block includes the identification of the positioning system information block, and the terminal does not store the valid key and discards the obtained encryption In the case where the locating system information block results in a failure of a system information request requesting distribution, the reason for the failure of the first target system information block request includes the lack of a valid key.
The device for reporting a system message report according to claim 26, wherein when the number of times the terminal fails to obtain the first target system message block by initiating random access exceeds a first threshold, the first target system message The reason for the block request failure includes the random access contention failure.
The device for reporting a system message report according to any one of claims 22-28, wherein the device further comprises:

The first receiving module is configured to receive the first request message sent by the network side device before the step of determining the requested first target system information block to obtain the situation information, and the first request message is used to request the terminal The system message report list allocated by the first request.
The device for reporting a system message report according to claim 29, wherein the device further comprises:

The second sending module is configured to send the terminal capability to the network side device before the terminal receives the first request message sent by the network side device, and the terminal capability is used to indicate whether the terminal is capable of reporting random Capability of accessing the report and/or whether the terminal has the capability of reporting the system message report of the first request for distribution.
The device for reporting a system message report according to any one of claims 22-28, wherein the configuration information of the system message report for the first request for allocation includes at least one of the following:

First information used to indicate whether a system message report of the first request allocation can be generated;

used to record the second information of the area of the system message report allocated by the first request;

The third information used to record the maximum number of system message reports requesting allocation that can be stored by the terminal.
The device for reporting system message reports according to claim 31, wherein the device further comprises at least one of the following:

A first generation module, configured to generate a system message report for the first allocation request when the first information indicates that the system message report for the first allocation request can be generated;

A second generating module, configured to not generate the first system message report requesting distribution when the first information indicates that the system message report requesting distribution cannot be generated;

A third generating module, configured to not generate a system message report for the first allocation request if the first information is missing.
The device for reporting system message reports according to claim 31, wherein the device further comprises at least one of the following:

A fourth generating module, configured to generate a system message report for the first allocation request when the first information indicates that the system message report for the first allocation request can be generated;

A fifth generating module, configured to not generate the first system message report requesting distribution when the first information indicates that the system message report requesting distribution cannot be generated;

The sixth generation module is configured to generate a system message report of the first request for distribution if the first information is missing.
The device for reporting system message reports according to claim 31, wherein the second information includes at least one of the following:

Tracking area TA list;

District list.
The device for reporting a system message report according to claim 31, wherein in the case where the second information is missing, the area for recording the system message report for the first allocation request is any area.
The device for reporting system information reports according to claim 31, wherein the third information is a fixed value or determined based on configuration of network side equipment.
The device for reporting a system message report according to any one of claims 22-28, wherein the device further comprises:

The first update module is configured to determine the second target system when the terminal determines that the number of cached system message reports allocated by historical requests is less than the third information after the determination of the acquisition situation information of the first target system message block Information about the acquisition status of the message block;

A seventh generation module, configured to generate the system information report for the third request allocation based on the acquisition situation information of the second target system information block.
The device for reporting a system message report according to any one of claims 22-28, wherein the device further comprises:

The second update module is configured to determine the second target system when the terminal determines that the number of system message reports allocated by the cached historical request is equal to the third information after the determination of the acquisition situation information of the first target system message block Information about the acquisition status of the message block;

A first judging module, configured to judge whether to generate the third system message requesting distribution based on the acquisition situation information of the second target system message block and the historical system message report requesting distribution stored in the terminal Report.
The device for reporting system message reports according to claim 38, wherein the first judging module is further configured to:

If the second target system information block is successfully obtained, determine not to generate the system information report for the third request allocation;

If the acquisition of the second target system message block fails, and there is no system message report for the request allocation that the request result is successful in the system message report of the historical request allocation, determine not to generate the system for the third request allocation news report;

If the acquisition of the second target system message block fails, and there is a system message report of a request allocation that the request result is successful in the system message report of the historical allocation request, determine to generate the system message of the third allocation request report, deleting any one of the system message reports assigned by the historical request or the earliest system message report assigned by the request with a successful request result.
The device for reporting a system message report according to any one of claims 22-28, wherein the device further comprises:

The first indicating module is configured to indicate to the network side device whether the terminal has cached the first system message report requesting distribution before sending the distribution requesting system message report list to the network side device.
The device for reporting system message reports according to claim 40, wherein the first indication module is further used for:

sending a first indication message to the network side device, where the first indication information is used to directly indicate whether the terminal has cached the system message report for the first request allocation;

Wherein, the first indication message includes at least one of the following:

Radio resource control setting completion information;

Radio resource control recovery completion information;

RRC reconfiguration complete information;

RRC reestablishment completion information;

Terminal information response.
The device for reporting a system message report according to claim 30, wherein the terminal capability is further used to indicate whether the terminal has cached the system message report for the first request for distribution.
A terminal, comprising a processor, a memory, and a program or instruction stored in the memory and operable on the processor, when the program or instruction is executed by the processor, any of claims 1 to 21 can be realized. A step in the method for reporting a system message report.
A readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, the steps of the method for reporting a system message report according to any one of claims 1 to 21 are realized .
A chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to implement the system according to any one of claims 1 to 21 when executing programs or instructions The steps of the reporting method of the message report.
A computer program product, the computer program product is stored in a non-transitory storage medium, and the program product is executed by at least one processor to implement the system message report according to any one of claims 1 to 21 Steps in the escalation method.