System message reporting method and device, terminal and storage medium

Abstract

The application discloses a system message report reporting method and device, a terminal and a storage medium, and belongs to the technical field of communication. The system message report reporting method of the application embodiment comprises the following steps: a terminal determines acquisition condition information of a first target system message block based on configuration information of a first requested system message report; the terminal sends a requested system message report list to a network side device, wherein the requested system message report list comprises a second requested system message report, the second requested system message report comprises the first requested system message report and / or a third requested system message report, the third requested system message report is generated after the first requested system message report is generated, and the first requested system message report is generated based on the acquisition condition information of the first target system message block.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to a system message reporting method, apparatus, terminal, and storage medium. Background Technology

[0002] The on-demand SI report is used to record and report information related to the request results of the intended SIB, thereby optimizing the configuration of the requested SIB resources.

[0003] It has been determined that the system message reports requested for allocation will be reported at the granularity of System Information Block (SIB), but the specific reporting method is unclear. Summary of the Invention

[0004] This application provides a method, apparatus, terminal, and storage medium for reporting system message reports, which can solve the problem of ambiguity in how on-demand SI reports are reported.

[0005] Firstly, a method for reporting system messages is provided, which includes:

[0006] Based on the configuration information of the system message report allocated in the first request, the terminal determines the acquisition status information of the first target system message block of the request;

[0007] The terminal sends a list of requested system message reports to the network-side device. The list of requested system message reports includes a second requested system message report, which includes the first requested system message report and / or a third requested system message report. The third requested system message report is generated after the first requested system message report is generated. The first requested system message report is generated based on the acquisition status information of the first target system message block.

[0008] Secondly, a system message reporting device is provided, the device comprising:

[0009] The first determining module is used to determine the acquisition status information of the first target system message block of the request based on the configuration information of the system message report allocated in the first request;

[0010] The first sending module is used to send a list of requested allocation system message reports to the network-side device. The list of requested allocation system message reports includes a second requested allocation system message report. The second requested allocation system message report includes the first requested allocation system message report and / or a third requested allocation system message report. The third requested allocation system message report is generated after the first requested allocation system message report is generated. The first requested allocation system message report is generated based on the acquisition status information of the first target system message block.

[0011] Thirdly, a terminal is provided, the terminal including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method described in the first aspect.

[0012] Fourthly, a terminal is provided, including a processor and a communication interface, wherein the processor is configured to: determine the acquisition status information of a first target system message block based on the configuration information of a first requested allocation system message report; the communication interface is configured to: send a list of requested allocation system message reports to a network-side device, the list of requested allocation system message reports including a second requested allocation system message report, the second requested allocation system message report including the first requested allocation system message report and / or a third requested allocation system message report, the third requested allocation system message report being generated after the first requested allocation system message report is generated; the first requested allocation system message report is generated based on the acquisition status information of the first target system message block.

[0013] Fifthly, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect.

[0014] In a sixth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being used to run programs or instructions to implement the method as described in the first aspect.

[0015] In a seventh aspect, a computer program / program product is provided, the computer program / program product being stored in a non-transient storage medium, the program / program product being executed by at least one processor to implement the steps of the system message reporting method as described in the first aspect.

[0016] In this embodiment of the application, after determining the acquisition status information of the target system message block requested based on the configuration information of the system message report allocated in the first request, the terminal reports the system message report to the network side device, thereby clarifying the reporting method of the system message report, ensuring that the network side can obtain the acquisition status of the requested system message block, and can optimize the resource configuration of the configured broadcast system message block based on the acquisition status analysis. Attached Figure Description

[0017] Figure 1 This diagram illustrates a structural diagram of a wireless communication system applicable to embodiments of this application;

[0018] Figure 2 This is a flowchart illustrating the system message reporting method provided in this application embodiment;

[0019] Figure 3 This is a schematic diagram of the structure of the system message reporting device provided in the embodiments of this application;

[0020] Figure 4 This is a schematic diagram of the structure of the communication device provided in the embodiments of this application;

[0021] Figure 5 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application. Detailed Implementation

[0022] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0023] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

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

[0025] Figure 1This diagram illustrates a structural diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as a terminal device, user terminal, or user equipment (UE). Terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, game consoles, etc. It should be noted that the specific type of terminal 11 is not limited in this embodiment. Network-side device 12 can be a base station or a core network. The base station can be referred to as a node B, evolved node B, access point, base transceiver station (BTS), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), B node, evolved B node (eNB), home B node, home evolved B node, WLAN access point, WiFi node, transmitting and receiving point (TRP), or any 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 this application embodiment, only the base station in the NR system is used as an example, but the specific type of base station is not limited.

[0026] The following description, in conjunction with the accompanying drawings, details the system message reporting method, apparatus, terminal, and storage medium provided in this application embodiment through some embodiments and application scenarios.

[0027] For Other SIs other than SIB1, including normal system message blocks (normal SIBs) and positioning system information blocks (pos SIBs) used for positioning, their transmission methods can be divided into two types: periodic broadcasts and broadcasts based on UE requests (on-demand).

[0028] Periodic broadcast: Within the calculated SI window, the network side sends the SI according to the period si-Periodicity;

[0029] On-demand request broadcast: If there is no request from the UE, 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 certain period of time in the SI window corresponding to the calculated SI.

[0030] For broadcast SIs of on-demand requests, two optional implementations (based on Msg1 and based on Msg3) can be included, and the network side can choose one of them for configuration according to the implementation.

[0031] Based on Msg1: The network side includes a System Information Request Configuration field SI-requestConfig or posSI-RequestConfig in the SIB1 scheduling information it sends, which carries information such as the preamble value for different SIs, the dedicated RACH resources used, and the mask. If the UE receives this field, it requests the SI using the Msg1-based method.

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

[0033] Regardless of the type of on-demand SI request used, SI is the smallest request granularity; SIB-level system message requests are not supported. This means that multiple SIBs can be mapped to the same SI message, and even if only one SIB is needed, the entire SI message must be retrieved.

[0034] For connected UEs, SI can be obtained by either reading broadcasts or receiving dedicated signaling.

[0035] Reading broadcast method: If the UE's active BWP 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.

[0036] Dedicated signaling method: If the UE's active BWP 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.

[0037] Figure 2 This is a flowchart illustrating the system message reporting method provided in this application embodiment, as shown below. Figure 2 As shown, the method includes the following steps:

[0038] Step 200: Based on the configuration information of the system message report allocated in the first request, the terminal determines the acquisition status information of the first target system message block of the request.

[0039] Step 210: The terminal sends a list of requested system message reports to the network-side device. The list of requested system message reports includes a second requested system message report. The second requested system message report includes the first requested system message report and / or a third requested system message report. The third requested system message report is generated after the first requested system message report is generated. The first requested system message report is generated based on the acquisition status information of the first target system message block.

[0040] Optionally, the first requested allocation system message report (first on-demand SI report), the second requested allocation system message report, and the third requested allocation system message report can all be used for at least one of the following:

[0041] a) Determine whether a request failed due to an unreasonable allocation of Random Access Channel (RACH) resources in a certain SIB;

[0042] b) Determine if a certain SIB is frequently requested but not periodically broadcast;

[0043] c) Determine if several SIBs are frequently requested by the same UE but are placed in different SI messages.

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

[0045] Optionally, in order to ensure that the network-side device can obtain the acquisition status of the requested system message block normal SIB or pos SIB and optimize the configuration of the broadcast system message block resource based on the acquisition status analysis, the UE with the ability to generate an on-demand SI report can determine the acquisition status information of the first target system message block based on the configuration information of the first requested system message report; then, it can generate a first requested system message report based on the acquisition status information of the first target system message block and send the list of requested system message reports containing the first requested system message report to the network-side device.

[0046] Optionally, after generating the first request allocation system message report, the acquisition status information of the second target system message block can be determined, and based on the acquisition status information of the second target system message block, it can be determined whether to generate a third request allocation system message report.

[0047] Optionally, the configuration information used in the third request allocation system message report may include the configuration information of the first request allocation system message report;

[0048] Optionally, the configuration information of the system message report allocated in the first request can be defined by the protocol, pre-set, or indicated by the network-side device;

[0049] Optionally, after determining the configuration information of the first requested allocation system message report based on protocol definition, pre-setting, or network-side device instruction, this configuration information can be used in subsequent generation of the third requested allocation system message report.

[0050] Optionally, when this configuration information is used for the system message report of the third request allocation, the configuration of the system message report of the first request allocation can be adapted to the system message report of the third request allocation.

[0051] Optionally, when reporting the first requested allocation system message report, after a UE capable of generating an on-demand SI report requests an on-demand SI broadcast from the network, it can record the acquisition status of the first target intended SIB according to the on-demand SI configuration, generate the first requested allocation system message report (first on-demand SI report), and cache the report in the UE; after receiving the on-demand SI report request from the network, the UE reports the on-demand SI report list to the network through Radio Resource Control (RRC) messages.

[0052] In this embodiment of the application, after determining the acquisition status information of the target system message block requested based on the configuration information of the system message report allocated in the first request, the terminal reports the system message report to the network side device, thereby clarifying the reporting method of the system message report, ensuring that the network side can obtain the acquisition status of the requested system message block, and can optimize the resource configuration of the configured broadcast system message block based on the acquisition status analysis.

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

[0054] The cell identifier of the cell corresponding to the first target system information block;

[0055] The identifier of the first target system message block;

[0056] The timestamp when the target system information block was requested;

[0057] Information on each random access during the request process of the first target system information block;

[0058] The request method for the first target system message block;

[0059] The request result of the first target system message block;

[0060] The reason why the first target system message block request failed.

[0061] Optionally, the first requested allocation system message report may be located in the first information field of the requested allocation system message report list;

[0062] Optionally, the first information field includes at least one or any combination of the following information:

[0063] The cell identifier of the cell corresponding to the first target system information block;

[0064] The identifier of the first target system message block;

[0065] The timestamp when the target system information block was requested;

[0066] Information on each random access during the request process of the first target system information block;

[0067] The request method for the first target system message block;

[0068] The request result of the first target system message block;

[0069] The reason why the first target system message block request failed.

[0070] Optionally, embodiments of this application design a first information field "on-Demand-SI-Report" to enable network-side devices to perform network optimization based on the report.

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

[0072] Identifier for a regular system message block;

[0073] Identifier of the positioning system information block used for positioning.

[0074] Optionally, the identifier of the first target system message block may be located in the second information field of the requested system message report list;

[0075] Optionally, the second information field can be the identifier of a normal system message block, i.e., the normal SIB identifier, or the identifier of a positioning system information block used for positioning, i.e., the pos SIB identifier.

[0076] Optionally, the normal SIB identifier can be the type of the SIB.

[0077] For example, the second information field may include a pos SIB identifier, which can be used to indicate the type, encryption status (whether encrypted), GNSS type, and SBAS type of the pos SIB; GNSSSBAS. In this second information field, the pos SIB type and additional information can be included. The additional information is used to uniquely map a certain pos SIB. In addition to the pos SIB type, the additional information requires 6 bits, including 1 bit of encryption information, 3 bits of GNSS type information, and 2 bits of SBAS type information.

[0078] Optionally, for normal SIBs, each SIB can only be included in one SI message; for posSIBs, the same pos SIB corresponding to different GNSS / SBAS must be included in different SI messages; for all normal SIBs and pos SIBs, the same type can only appear once in one SI message. Furthermore, pos SIBs can be encrypted using LMF, while normal SIBs cannot.

[0079] Optionally, if the UE does not have the corresponding key during the processing of the received encrypted pos SIB, the UE may discard the corresponding pos SIB signaling.

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

[0081] The encrypted information in the positioning system information block, the type of global navigation satellite system, and the type of satellite-based augmentation system;

[0082] The PosSchedulingInfo to which the location system information block belongs is located in the order of posSchedulingInfoList.

[0083] Optionally, the scheduling indication information (PosSI-SchedulingInfo and SI-SchedulingInfo) of the pos SIB (such as posSIB1-1 to posSIB6-3) used for positioning is not completely consistent with that of the normal SIB (such as SIB2 to SIB14). Therefore, compared with the normal SIB, the on-demand SI report of the pos SIB can introduce additional indication information.

[0084] Optionally, the pos SIB identifier can be used to indicate at least one of the following:

[0085] The type of the pos SIB, i.e., the encryption status of the pos SIB (e.g., whether it is encrypted), GNSS type, and SBAS type;

[0086] The type of the pos SIB and the order of the PosSchedulingInfo to which the pos SIB belongs in the posSchedulingInfoList.

[0087] For example, a pos SIB identifier can be the type of the pos SIB and the sequential position of the pos SchedulingInfo in the posSchedulingInfoList to which the pos SIB belongs. Network-side devices, such as base stations, can map the intended pos SIB based on timestamps and sequence information. This can include the pos SIB type and additional information, which is used to uniquely map a pos SIB. In addition to the pos SIB type, the additional information also requires 5 bits of sequence information.

[0088] Optionally, the reason for the failure of the first target system message block request includes at least one of the following:

[0089] No valid key;

[0090] Random access failed.

[0091] 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 allocated by the request;

[0092] Optionally, the third information field may include at least one of the following reasons:

[0093] No valid key;

[0094] RACH lost the competition.

[0095] Optionally, embodiments of this application distinguish and process normal SIBs and pos SIBs by designing a second information field “intendedSIB-TypeInfo” and a third information field “causeOfFailure”.

[0096] Optionally, if the identifier of the first target system message block includes the identifier of the positioning system information block, and the terminal fails to store the encrypted positioning system information block obtained by discarding the valid key, resulting in the failure of the requested allocation of the system message, the reason for the failure of the first target system message block request includes the absence of a valid key.

[0097] Optionally, when the type of the first target system message block is a pos SIB type, and the on-demand SI request fails because the UE discards the acquired encrypted pos SIB due to the lack of a valid key, the value of the third information field can be "no valid key".

[0098] Optionally, if the number of times the terminal fails to obtain the first target system message block by initiating random access exceeds a first threshold, the reason for the failure of the first target system message block request includes the failure of the random access contention.

[0099] 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 can be "RACH contention failed".

[0100] Optionally, the method further includes:

[0101] Before the step of determining the acquisition status information of the first target system message block of the request, the terminal receives a first request message sent by the network-side device. The first request message is used to request the system message report list allocated by the first request from the terminal.

[0102] Optionally, after the UE enters the connected state, it can explicitly or implicitly indicate to the network-side device that it has saved the requested system message reports; then the network-side device can send a first request message to the UE to request the first requested system message report list from the terminal. After receiving the first request message, the UE can send the requested system message reports to the network-side device.

[0103] Optionally, the method further includes:

[0104] Before the terminal receives the first request message sent by the network-side device, the terminal sends a terminal capability to the network-side device. The terminal capability is used to indicate whether the terminal has the ability to report a random access report and / or whether the terminal has the ability to report a system message report allocated by the first request.

[0105] Optionally, a UE capable of generating an on-demand SI report can report the UE capability to the network-side device after the network requests the UE capability.

[0106] Optionally, this capability can be included in other existing capabilities, such as the "capability to report 2-step RACH reports," which means that when the UE reports the capability indication 2steprach-Report-r16, it indicates that the UE has the capability to report the system message reports allocated in the first request.

[0107] Optionally, the configuration information of the system message report allocated in the first request includes at least one of the following:

[0108] First information used to indicate whether a system message report allocated by the first request can be generated;

[0109] Second information for the area used to record the system message report allocated by the first request;

[0110] Third information used to record the maximum number of system message reports for request allocation that the terminal can store.

[0111] Optionally, when the UE records the acquisition status information of the requested first target system message block according to the configuration information of the system message report allocated in the first request, the configuration information of the system message report allocated in the first request may include at least one of the following:

[0112] The first information is used to indicate whether the system message report allocated by the first request can be generated, that is, the first information is used to indicate whether the on-demand SI report is enabled;

[0113] The second information is 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;

[0114] The third information is used to record the maximum number of system message reports allocated in the first request, that is, the third information can be used to record the maximum number of system message reports allocated in the request that the terminal can store;

[0115] Optionally, to reduce the impact of report caching on UE storage, there are usually storage limits for various reports.

[0116] Taking the RA report as an example, when the UE successfully completes the 4-step RACH, if the number of currently stored RA reports does not exceed maxRAReport, a new RA report can be generated; otherwise, the UE will not generate a new RA report. For example, maxRAReport can be equal to 8.

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

[0118] Step a1. The network-side device can request UE capabilities from the UE. After receiving the request, the UE can report its capabilities, including whether it supports the ability to generate on-demand SI reports.

[0119] Step a2. After the network-side device obtains the UE's capabilities, it can send the configuration information of the first requested system message report, namely the on-demand SI report configuration, to the UE according to the network optimization requirements and the UE's capabilities. This includes the enable switch, the target area for on-demand SI report collection (such as cell list or TA list), and the maximum number of on-demand SI reports.

[0120] Step a3. The UE requests the first target on-demand SI from the network-side device and generates the first on-demand SI report based on the request result and configuration.

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

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

[0123] Step a6. The network-side device sends the first on-demand SI report to the base station corresponding to the cell via an AccessAnd Mobility Indication message, based on the cell identifier in the first on-demand SI report.

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

[0125] Optionally, embodiments of this application introduce an optional first on-demand SI report configuration, including an enable switch and a recording area, thereby generating an on-demand SI report for a target area.

[0126] Optionally, the method further includes at least one of the following:

[0127] When the first information indicates that a system message report for the first requested allocation can be generated, the terminal generates the system message report for the first requested allocation;

[0128] If the first information indicates that the system message report requested by the first request cannot be generated, the terminal will not generate the system message report requested by the first request.

[0129] If the first information is missing, the terminal does not generate the system message report requested in the first request.

[0130] Optionally, "whether to enable on-demand SI report" is the first piece of information, which can be configured by the network according to optimization requirements and UE capabilities.

[0131] Optionally, if the first information value is "yes", indicating that the system message report requested by the first request can be generated, then the UE can record the first on-demand SI report; if the first information value is "no", indicating that the system message report requested by the first request cannot be generated, then the UE is not allowed to record the first on-demand SI report; if the first information is missing, then the UE is not allowed to record the first on-demand SI report.

[0132] Optionally, the method further includes at least one of the following:

[0133] When the first information indicates that a system message report for the first requested allocation can be generated, the terminal generates the system message report for the first requested allocation;

[0134] If the first information indicates that the requested system message report cannot be generated, the terminal will not generate the requested system message report.

[0135] In the event that the first information is missing, the terminal generates a system message report for the first requested allocation.

[0136] Optionally, if the first information value is "yes", it indicates that the system message report requested by the first request can be generated, and the UE can record the first on-demand SI report; if the first information value is "no", it indicates that the system message report requested by the first request cannot be generated, and the UE does not allow the recording of the first on-demand SI report; if the first information is missing, the UE allows the recording of the first on-demand SI report.

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

[0138] Tracking area TA list;

[0139] List of residential communities.

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

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

[0142] Optionally, if the second information is missing, the area for recording the system message report of the first request allocation can be any area.

[0143] Alternatively, if this second information is missing, it can be indicated that the first on-demandSI report can be recorded in any region.

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

[0145] Optionally, the maximum number of third pieces of information recorded in the first on-demand SI report can be a fixed value or configured by the network according to optimization requirements and UE capabilities.

[0146] Optionally, the method further includes:

[0147] After determining the acquisition status information of the first target system message block, if the terminal determines that the number of cached historical request allocation system message reports is less than the third information, the terminal determines the acquisition status information of the second target system message block.

[0148] The terminal generates the third request allocation system message report based on the acquisition status information of the second target system message block.

[0149] Optionally, after the UE records the acquisition status of the first target intended SIB according to the first on-demand SI configuration, if the number of cached historical on-demand SI reports is less than the maximum number limited by the third information, the UE can record the acquisition status of the new second target intended SIB and generate a new on-demand SI report, i.e., the third on-demand SI report.

[0150] Optionally, the second target system message block may be the same as or different from the first target system message block. For example, if the request for the first target system message block fails, a second request may be made, in which case the second target system message block requested is the same as the first target system message block; or, after determining the acquisition status information of the first target system message block, a second target system message block different from the first target system message block may be requested.

[0151] Optionally, the method further includes:

[0152] After determining the acquisition status information of the first target system message block, if the terminal determines that the number of cached historical request allocation system message reports is equal to the third information, the terminal determines the acquisition status information of the second target system message block.

[0153] Based on the acquisition information of the second target system message block and the historical request allocation system message reports stored in the terminal, the terminal determines whether to generate the third request allocation system message report.

[0154] Optionally, after the UE records the acquisition status of the first target intended SIB according to the first on-demand SI configuration, it may record the acquisition status of the second target intended SIB when the number of cached historical on-demand SI reports is equal to the maximum number limited by the third information. The UE may then determine whether to generate a new on-demand SI report, i.e., a third on-demand SI report, based on the acquisition status of the second target intended SIB and the type of the currently stored historical request allocation system message report (historical on-demand SI report).

[0155] Optionally, the terminal determines whether to generate the third request allocation system message report based on the acquisition status information of the second target system message block and the historical request allocation system message reports stored in the terminal, including:

[0156] If the second target system message block is successfully acquired, it is determined that the system message report allocated by the third request will not be generated;

[0157] If the acquisition of the second target system message block fails and there is no system message report in the historical request allocation system message report indicating a successful request result, it is determined that the third request allocation system message report will not be generated.

[0158] If the acquisition of the second target system message block fails, and there is a system message report in the historical request allocation system message report with a successful request result, then the third request allocation system message report is generated, and any one or the earliest system message report in the historical request allocation system message report with a successful request result is deleted.

[0159] Optionally, embodiments of this application introduce on-demand SI report priority, that is, priority is given to storing reports of on-demand SI failures.

[0160] Optionally, when determining whether to generate a third on-demand SI report, it can be based on at least one of the following:

[0161] If the second target intended SIB is successfully acquired, a third on-demand SI report will not be generated.

[0162] If the second target intended SIB fails to be acquired, and there is no on-demand SI report with a successful request result in the system message report of the historical request allocation, then the third on-demand SI report will not be generated.

[0163] If the second target intended SIB fails to be acquired, and there is an on-demand SI report with a successful request result in the system message report of the historical request allocation, then a third on-demand SI report is generated, and any one or the earliest stored on-demand SI report with a successful request result is deleted, while the newly generated third on-demand SI report is saved.

[0164] Optionally, the method further includes:

[0165] Before sending the list of requested system message reports to the network-side device, the terminal indicates to the network-side device whether it has cached the first requested system message report.

[0166] 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.

[0167] Optionally, after the UE connects to the network-side device, it can explicitly or implicitly indicate to the network-side device that the first on-demand SI report has been cached.

[0168] Optionally, the terminal instructs the network-side device whether it has cached the system message report requested in the first request, including:

[0169] The terminal sends a first indication message to the network-side device. The first indication message is used to directly indicate whether the terminal has cached the system message report allocated by the first request.

[0170] The first indication message includes at least one of the following:

[0171] Wireless resource control settings complete;

[0172] Wireless resource control restoration complete;

[0173] Wireless resource control reconfiguration complete;

[0174] Wireless resource control reconstruction completed;

[0175] Terminal information response.

[0176] Optionally, the UE may explicitly indicate that the first on-demand SI report has been cached by sending an RRC message, which may be:

[0177] Wireless resource control setup completion information, such as RRCSetupComplete;

[0178] Radio resource control recovery completion information, such as RRCResumeComplete;

[0179] Radio resource control reconfiguration completion information, such as RRCReconfigurationComplete;

[0180] Radio Resource Control (RRC) reconstruction completion information, such as RRCReestablishmentComplete;

[0181] Terminal information response, such as UEInformationResponse.

[0182] Optionally, the terminal capability is also used to indicate whether the terminal has cached the system message report allocated by the first request.

[0183] Optionally, the UE implicitly indicates that it has cached the on-demand SI report by associating it with its capabilities. If the UE reports that it has the ability to generate on-demand SI reports 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.

[0184] Optionally, other capabilities reported by the UE may include the ability to generate RACH reports.

[0185] Optionally, the RRC message sent by the network-side device to the UE for an on-demand SI report request can be a UEInformationRequest.

[0186] Optionally, the UE can report the on-demand SI report to the network-side device via an RRC message, where the RRC message can be a UEInformationResponse, and the reporting result contains an on-demand SI report list (one or more reports).

[0187] Optionally, the following is a flowchart example of the system message reporting method:

[0188] Step b1. The network-side device requests UE capabilities from the UE. After receiving the request, the UE reports its capabilities, including whether it supports the ability to generate on-demand SI reports.

[0189] Step b2. After the network-side device obtains the UE's capabilities, it can optionally issue the first on-demand SI report configuration to the UE based on the network-side device's optimization requirements and the UE's capabilities. This configuration includes an enable switch and the target area for the first on-demand SI report (such as a cell list or TA list). The terminal can record the maximum number of on-demand SI reports.

[0190] Step b3. The UE requests the first target on-demand SI from the network-side device and generates the first on-demand SI report based on the request result and configuration.

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

[0192] Step b5. The network-side device can request the first on-demand SI report from the UE via UEInformationRequest.

[0193] Step b6. The UE sends an on-demand SI report list to the network-side device.

[0194] The method for reporting on-demand SI reports provided in this application introduces on-demand SI report configuration and reporting, defines on-demand SI reports, and differentiates normal SIBs and pos SIBs in the report; enabling the network side to optimize the resource configuration of on-demand SIBs and pos SIBs based on the on-demand SI reports reported by the UE.

[0195] In this embodiment of the application, after determining the acquisition status information of the target system message block requested based on the configuration information of the system message report allocated in the first request, the terminal reports the system message report to the network side device, thereby clarifying the reporting method of the system message report, ensuring that the network side can obtain the acquisition status of the requested system message block, and can optimize the resource configuration of the configured broadcast system message block based on the acquisition status analysis.

[0196] It should be noted that the system message reporting method provided in this application embodiment can be executed by a system message reporting device, or by a control module within the system message reporting device for executing the system message reporting method. This application embodiment uses the execution of the system message reporting method by a system message reporting device as an example to illustrate the system message reporting device provided in this application embodiment.

[0197] Figure 3 This is a schematic diagram of the structure of the system message reporting device provided in the embodiments of this application, as shown below. Figure 3 As shown, the device includes: a first determining module 310 and a first transmitting module 320; wherein:

[0198] The first determining module 310 is used to determine the acquisition status information of the first target system message block of the request based on the configuration information of the system message report allocated by the first request;

[0199] The first sending module 320 is used to send a list of requested allocation system message reports to the network-side device. The list of requested allocation system message reports includes a second requested allocation system message report. The second requested allocation system message report includes the first requested allocation system message report and / or a third requested allocation system message report. The third requested allocation system message report is generated after the first requested allocation system message report is generated. The first requested allocation system message report is generated based on the acquisition status information of the first target system message block.

[0200] Optionally, the system message reporting device determines the acquisition status information of the first target system message block requested by the first determining module 310 based on the configuration information of the first requested allocated system message report; subsequently, the system message report request list can be sent to the network-side device through the first sending module 320; wherein, the system message report request list includes a second requested allocated system message report, the second requested allocated system message report includes the first requested allocated system message report and / or a third requested allocated system message report, the third requested allocated system message report being generated after the first requested allocated system message report is generated; the first requested allocated system message report is generated based on the acquisition status information of the first target system message block.

[0201] In this embodiment of the application, after determining the acquisition status information of the target system message block requested based on the configuration information of the system message report allocated in the first request, the terminal reports the system message report to the network side device, thereby clarifying the reporting method of the system message report, ensuring that the network side can obtain the acquisition status of the requested system message block, and can optimize the resource configuration of the configured broadcast system message block based on the acquisition status analysis.

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

[0203] The cell identifier of the cell corresponding to the first target system information block;

[0204] The identifier of the first target system message block;

[0205] The timestamp when the target system information block was requested;

[0206] Information on each random access during the request process of the first target system information block;

[0207] The request method for the first target system message block;

[0208] The request result of the first target system message block;

[0209] The reason why the first target system message block request failed.

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

[0211] Identifier for a regular system message block;

[0212] Identifier of the positioning system information block used for positioning.

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

[0214] The encrypted information in the positioning system information block, the type of global navigation satellite system, and the type of satellite-based augmentation system;

[0215] The PosSchedulingInfo to which the location system information block belongs is located in the order of posSchedulingInfoList.

[0216] Optionally, the reason for the failure of the first target system message block request includes at least one of the following:

[0217] No valid key;

[0218] Random access failed.

[0219] Optionally, if the identifier of the first target system message block includes the identifier of the positioning system information block, and the terminal fails to store the encrypted positioning system information block obtained by discarding the valid key, resulting in the failure of the requested allocation of the system message, the reason for the failure of the first target system message block request includes the absence of a valid key.

[0220] Optionally, if the number of times the terminal fails to obtain the first target system message block by initiating random access exceeds a first threshold, the reason for the failure of the first target system message block request includes the failure of the random access contention.

[0221] Optionally, the device further includes:

[0222] The first receiving module is configured to, before the step of determining the acquisition status information of the first target system message block of the request, have the terminal receive a first request message sent by a network-side device, the first request message being used to request the terminal the system message report list allocated by the first request.

[0223] Optionally, the device further includes:

[0224] The second sending module is configured to send terminal capabilities to the network-side device before the terminal receives the first request message sent by the network-side device. The terminal capabilities are used to indicate whether the terminal has the ability to report random access reports and / or whether the terminal has the ability to report system message reports allocated by the first request.

[0225] Optionally, the configuration information of the system message report allocated in the first request includes at least one of the following:

[0226] First information used to indicate whether a system message report allocated by the first request can be generated;

[0227] Second information for the area used to record the system message report allocated by the first request;

[0228] Third information used to record the maximum number of system message reports for request allocation that the terminal can store.

[0229] Optionally, the device further includes at least one of the following:

[0230] The first generation module is configured to generate the system message report for the first request allocation when the first information indicates that the system message report for the first request allocation can be generated.

[0231] The second generation module is configured to not generate the system message report requested by the first request if the first information indicates that the system message report requested by the first request cannot be generated.

[0232] The third generation module is used to prevent the generation of the system message report allocated by the first request in the event that the first information is missing.

[0233] Optionally, the device further includes at least one of the following:

[0234] The fourth generation module is used to generate the system message report for the first request allocation when the first information indicates that the system message report for the first request allocation can be generated.

[0235] The fifth generation module is configured to not generate the first requested system message report when the first information indicates that the requested system message report cannot be generated.

[0236] The sixth generation module generates a system message report for the first request allocation if the first information is missing.

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

[0238] Tracking area TA list;

[0239] List of residential communities.

[0240] Optionally, if the second information is missing, the region where the system message report for the first request allocation is recorded can be any region.

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

[0242] Optionally, the device further includes:

[0243] The first update module is used to determine the acquisition status information of the second target system message block after the acquisition status information of the first target system message block is determined, and when the terminal determines that the number of cached historical request allocation system message reports is less than the third information.

[0244] The seventh generation module is used to generate the system message report for the third request allocation based on the acquisition status information of the second target system message block.

[0245] Optionally, the device further includes:

[0246] The second update module is used to determine the acquisition status information of the second target system message block after the acquisition status information of the first target system message block is determined, and when the terminal determines that the number of cached historical request allocation system message reports is equal to the third information.

[0247] The first judgment module is used to determine whether to generate the third request allocation system message report based on the acquisition status information of the second target system message block and the historical request allocation system message reports stored in the terminal.

[0248] Optionally, the first determination module is further configured to:

[0249] If the second target system message block is successfully acquired, it is determined that the system message report allocated by the third request will not be generated;

[0250] If the acquisition of the second target system message block fails and there is no system message report in the historical request allocation system message report indicating a successful request result, it is determined that the third request allocation system message report will not be generated.

[0251] If the acquisition of the second target system message block fails, and there is a system message report in the historical request allocation system message report with a successful request result, then the third request allocation system message report is generated, and any one or the earliest system message report in the historical request allocation system message report with a successful request result is deleted.

[0252] Optionally, the device further includes:

[0253] The first indication module is used to indicate to the network-side device whether the terminal has cached the first requested allocation system message report before sending the list of requested allocation system message reports to the network-side device.

[0254] Optionally, the first indication module is further configured to:

[0255] Send a first indication message to the network-side device, wherein the first indication information is used to directly indicate whether the terminal has cached the system message report allocated by the first request;

[0256] The first indication message includes at least one of the following:

[0257] Wireless resource control settings complete;

[0258] Wireless resource control restoration complete;

[0259] Wireless resource control reconfiguration complete;

[0260] Wireless resource control reconstruction completed;

[0261] Terminal information response.

[0262] Optionally, the terminal capability is also used to indicate whether the terminal has cached the system message report allocated by the first request.

[0263] In this embodiment of the application, after determining the acquisition status information of the target system message block requested based on the configuration information of the system message report allocated in the first request, the terminal reports the system message report to the network side device, thereby clarifying the reporting method of the system message report, ensuring that the network side can obtain the acquisition status of the requested system message block, and can optimize the resource configuration of the configured broadcast system message block based on the acquisition status analysis.

[0264] The system message reporting device in this embodiment can be a device, a device with an operating system, or an electronic device, or it can be a component, integrated circuit, or chip in a terminal. This device or electronic device can be a mobile terminal or a non-mobile terminal. For example, a mobile terminal can include, but is not limited to, the types of terminals 11 listed above, while a non-mobile terminal can be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This embodiment does not impose specific limitations.

[0265] The system message reporting device provided in this application embodiment can achieve... Figure 2 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0266] Optional, Figure 4 This is a schematic diagram of the structure of the communication device provided in the embodiments of this application, such as... Figure 4As shown, this application embodiment also provides a communication device 400, including a processor 401, a memory 402, and a program or instructions stored in the memory 402 and executable on the processor 401. For example, when the communication device 400 is a terminal, the program or instructions executed by the processor 401 implement the various processes of the above-described system message reporting method embodiment, and achieve the same technical effect. When the communication device 400 is a network-side device, the program or instructions executed by the processor 401 implement the various processes of the above-described system message reporting method embodiment, and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0267] This application embodiment also provides a terminal, including a processor and a communication interface. The processor is used to: determine the acquisition status information of a first target system message block based on the configuration information of a first requested allocation system message report; the communication interface is used to: send a list of requested allocation system message reports to a network-side device, the list of requested allocation system message reports including a second requested allocation system message report, the second requested allocation system message report including the first requested allocation system message report and / or a third requested allocation system message report, the third requested allocation system message report being generated after the first requested allocation system message report is generated; the first requested allocation system message report is generated based on the acquisition status information of the first target system message block. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and all implementation processes and methods of the above method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, Figure 5 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

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

[0269] Those skilled in the art will understand that the terminal 500 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 510 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 5 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0270] It should be understood that, in this embodiment, the input unit 504 may include a graphics processing unit (GPU) 5041 and a microphone 5042. The GPU 5041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 506 may include a display panel 5061, which 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 a touch detection device and a touch controller. Other input devices 5072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick, which will not be described in detail here.

[0271] In this embodiment, the radio frequency unit 501 receives downlink data from the network-side device and processes it for the processor 510; additionally, it sends uplink data to the network-side device. Typically, 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, etc.

[0272] The memory 509 can be used to store software programs or instructions and various data. The memory 509 may primarily include a program or instruction storage area and a data storage area. The program or instruction storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 509 may include high-speed random access memory and non-volatile memory, which may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. For example, at least one disk storage device, flash memory device, or other non-volatile solid-state storage device.

[0273] Processor 510 may include one or more processing units; optionally, processor 510 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications or instructions, and the modem processor mainly handles wireless communication, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 510.

[0274] The processor 510 is used for:

[0275] Based on the configuration information of the system message report allocated in the first request, determine the acquisition status information of the first target system message block of the request;

[0276] A list of requested allocation system message reports is sent to the network-side device. The list of requested allocation system message reports includes a second requested allocation system message report. The second requested allocation system message report includes the first requested allocation system message report and / or a third requested allocation system message report. The third requested allocation system message report is generated after the first requested allocation system message report is generated. The first requested allocation system message report is generated based on the acquisition status information of the first target system message block.

[0277] In this embodiment of the application, after determining the acquisition status information of the target system message block requested based on the configuration information of the system message report allocated in the first request, the terminal reports the system message report to the network side device, thereby clarifying the reporting method of the system message report, ensuring that the network side can obtain the acquisition status of the requested system message block, and can optimize the resource configuration of the configured broadcast system message block based on the acquisition status analysis.

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

[0279] The cell identifier of the cell corresponding to the first target system information block;

[0280] The identifier of the first target system message block;

[0281] The timestamp when the target system information block was requested;

[0282] Information on each random access during the request process of the first target system information block;

[0283] The request method for the first target system message block;

[0284] The request result of the first target system message block;

[0285] The reason why the first target system message block request failed.

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

[0287] Identifier for a regular system message block;

[0288] Identifier of the positioning system information block used for positioning.

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

[0290] The encrypted information in the positioning system information block, the type of global navigation satellite system, and the type of satellite-based augmentation system;

[0291] The PosSchedulingInfo to which the location system information block belongs is located in the order of posSchedulingInfoList.

[0292] Optionally, the reason for the failure of the first target system message block request includes at least one of the following:

[0293] No valid key;

[0294] Random access failed.

[0295] Optionally, if the identifier of the first target system message block includes the identifier of the positioning system information block, and the terminal fails to store the encrypted positioning system information block obtained by discarding the valid key, resulting in the failure of the requested allocation of the system message, the reason for the failure of the first target system message block request includes the absence of a valid key.

[0296] Optionally, if the number of times the terminal fails to obtain the first target system message block by initiating random access exceeds a first threshold, the reason for the failure of the first target system message block request includes the failure of the random access contention.

[0297] Optionally, the processor 510 is also used for:

[0298] Before the step of determining the acquisition status information of the first target system message block of the request, a first request message sent by a network-side device is received. The first request message is used to request the system message report list allocated by the first request from the terminal.

[0299] Optionally, the processor 510 is also used for:

[0300] Before the terminal receives the first request message sent by the network-side device, the terminal capability is sent to the network-side device. The terminal capability is used to indicate whether the terminal has the ability to report a random access report and / or whether the terminal has the ability to report a system message report allocated by the first request.

[0301] Optionally, the configuration information of the system message report allocated in the first request includes at least one of the following:

[0302] First information used to indicate whether a system message report allocated by the first request can be generated;

[0303] Second information for the area used to record the system message report allocated by the first request;

[0304] Third information used to record the maximum number of system message reports for request allocation that the terminal can store.

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

[0306] If the first information indicates that a system message report for the first request allocation can be generated, then the system message report for the first request allocation is generated.

[0307] If the first information indicates that the system message report requested by the first request cannot be generated, the system message report requested by the first request will not be generated.

[0308] If the first information is missing, the system message report allocated by the first request will not be generated.

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

[0310] If the first information indicates that a system message report for the first request allocation can be generated, then the system message report for the first request allocation is generated.

[0311] If the first information indicates that the requested system message report cannot be generated, the requested system message report will not be generated.

[0312] If the first information is missing, generate a system message report for the first request allocation.

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

[0314] Tracking area TA list;

[0315] List of residential communities.

[0316] Optionally, if the second information is missing, the region where the system message report for the first request allocation is recorded can be any region.

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

[0318] Optionally, the processor 510 is also used for:

[0319] After determining the acquisition status information of the first target system message block, if the terminal determines that the number of cached historical request allocation system message reports is less than the third information, the acquisition status information of the second target system message block is determined.

[0320] Based on the acquisition information of the second target system message block, a system message report for the third request allocation is generated.

[0321] Optionally, the processor 510 is also used for:

[0322] After determining the acquisition status information of the first target system message block, if the terminal determines that the number of cached historical request allocation system message reports is equal to the third information, the acquisition status information of the second target system message block is determined.

[0323] Based on the acquisition information of the second target system message block and the historical request allocation system message reports stored in the terminal, the terminal determines whether to generate the third request allocation system message report.

[0324] Optionally, the processor 510 is also used for:

[0325] If the second target system message block is successfully acquired, it is determined that the system message report allocated by the third request will not be generated;

[0326] If the acquisition of the second target system message block fails and there is no system message report in the historical request allocation system message report indicating a successful request result, it is determined that the third request allocation system message report will not be generated.

[0327] If the acquisition of the second target system message block fails, and there is a system message report in the historical request allocation system message report with a successful request result, then the third request allocation system message report is generated, and any one or the earliest system message report in the historical request allocation system message report with a successful request result is deleted.

[0328] Optionally, the processor 510 is also used for:

[0329] Before sending the list of requested system message reports to the network-side device, the terminal is instructed to the network-side device whether it has cached the first requested system message report.

[0330] Optionally, the processor 510 is also used for:

[0331] Send a first indication message to the network-side device, wherein the first indication information is used to directly indicate whether the terminal has cached the system message report allocated by the first request;

[0332] The first indication message includes at least one of the following:

[0333] Wireless resource control settings complete;

[0334] Wireless resource control restoration complete;

[0335] Wireless resource control reconfiguration complete;

[0336] Wireless resource control reconstruction completed;

[0337] Terminal information response.

[0338] Optionally, the terminal capability is also used to indicate whether the terminal has cached the system message report allocated by the first request.

[0339] In this embodiment of the application, after determining the acquisition status information of the target system message block requested based on the configuration information of the system message report allocated in the first request, the terminal reports the system message report to the network side device, thereby clarifying the reporting method of the system message report, ensuring that the network side can obtain the acquisition status of the requested system message block, and can optimize the resource configuration of the configured broadcast system message block based on the acquisition status analysis.

[0340] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described system message reporting method embodiment and achieve the same technical effect. To avoid repetition, they will not be described again here.

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

[0342] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described system message reporting method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0343] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0344] This application also provides a computer program / program product, which is stored in a non-transient storage medium. The program / program product is executed by at least one processor to implement the various processes of the above-described system message reporting method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0345] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0346] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0347] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for reporting system messages, characterized in that, include: Based on the configuration information of the system message report allocated in the first request, the terminal determines the acquisition status information of the first target system message block of the request; The terminal sends a list of requested system message reports to the network-side device. The list of requested system message reports includes a second requested system message report. The second requested system message report includes the first requested system message report and / or a third requested system message report. The third requested system message report is generated after the first requested system message report is generated. The first requested system message report is generated based on the acquisition status information of the first target system message block. The system message report for the first request allocation includes at least one of the following: The identifier of the first target system message block; The reason why the first target system message block request failed; The identifier of the first target system message block includes at least one of the following: Identifier for a regular system message block; Identifier of the positioning system information block used for positioning; The identifier of the positioning system information block is used to indicate at least one of the following: The encrypted information in the positioning system information block, the type of global navigation satellite system, and the type of satellite-based augmentation system; The PosSchedulingInfo to which the location system information block belongs is located in the order of posSchedulingInfoList; 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.

2. The system message reporting method according to claim 1, characterized in that, The system message report for the first request allocation includes at least one of the following: The cell identifier of the cell corresponding to the first target system message block; The timestamp when the target system message block was requested; Information on each random access during the request process of the first target system message block; The request method for the first target system message block; The request result of the first target system message block.

3. The system message reporting method according to claim 1, characterized in that, If the identifier of the first target system message block includes the identifier of the location system information block, and the terminal fails to store the encrypted location system information block obtained by discarding the valid key, resulting in the failure of the requested allocation of the system message, the reason for the failure of the first target system message block request includes the absence of a valid key.

4. The system message reporting method according to claim 3, characterized in that, If the number of times the terminal fails to obtain the first target system message block by initiating random access exceeds a first threshold, the reasons for the failure of the first target system message block request include the failure of the random access contention.

5. The system message reporting method according to any one of claims 1-4, characterized in that, The method further includes: Before the step of determining the acquisition status information of the first target system message block of the request, the terminal receives a first request message sent by the network-side device. The first request message is used to request the system message report list allocated by the first request from the terminal.

6. The system message reporting method according to claim 5, characterized in that, The method further includes: Before the terminal receives the first request message sent by the network-side device, the terminal sends a terminal capability to the network-side device. The terminal capability is used to indicate whether the terminal has the ability to report a random access report and / or whether the terminal has the ability to report a system message report allocated by the first request.

7. The system message reporting method according to any one of claims 1-4, characterized in that, The configuration information for the system message report allocated in the first request includes at least one of the following: First information used to indicate whether a system message report allocated by the first request can be generated; Second information for the area used to record the system message report of the first requested allocation; Third information used to record the maximum number of system message reports for request allocation that the terminal can store.

8. The system message reporting method according to claim 7, characterized in that, The method further includes at least one of the following: When the first information indicates that a system message report for the first requested allocation can be generated, the terminal generates the system message report for the first requested allocation; If the first information indicates that the system message report requested by the first request cannot be generated, the terminal will not generate the system message report requested by the first request. If the first information is missing, the terminal does not generate the system message report requested in the first request.

9. The system message reporting method according to claim 7, characterized in that, The method further includes at least one of the following: When the first information indicates that a system message report for the first requested allocation can be generated, the terminal generates the system message report for the first requested allocation; If the first information indicates that the requested system message report cannot be generated, the terminal will not generate the requested system message report. In the event that the first information is missing, the terminal generates a system message report for the first requested allocation.

10. The system message reporting method according to claim 7, characterized in that, The second information includes at least one of the following: Tracking area TA list; List of residential communities.

11. The system message reporting method according to claim 7, characterized in that, In the absence of the second information, the region for recording the system message report of the first request allocation can be any region.

12. The system message reporting method according to claim 7, characterized in that, The third piece of information is a fixed value or determined based on the network-side device configuration.

13. The system message reporting method according to claim 7, characterized in that, The method further includes: After determining the acquisition status information of the first target system message block, if the terminal determines that the number of cached historical request allocation system message reports is less than the third information, the terminal determines the acquisition status information of the second target system message block. The terminal generates the third request allocation system message report based on the acquisition status information of the second target system message block.

14. The system message reporting method according to claim 7, characterized in that, The method further includes: After determining the acquisition status information of the first target system message block, if the terminal determines that the number of cached historical request allocation system message reports is equal to the third information, the terminal determines the acquisition status information of the second target system message block. Based on the acquisition information of the second target system message block and the historical request allocation system message reports stored in the terminal, the terminal determines whether to generate the third request allocation system message report.

15. The system message reporting method according to claim 14, characterized in that, Based on the acquisition information of the second target system message block and the historical request allocation system message reports stored in the terminal, the terminal determines whether to generate the third request allocation system message report, including: If the second target system message block is successfully acquired, it is determined that the system message report allocated by the third request will not be generated; If the acquisition of the second target system message block fails and there is no system message report in the historical request allocation system message report indicating a successful request result, it is determined that the third request allocation system message report will not be generated. If the acquisition of the second target system message block fails, and there is a system message report in the historical request allocation system message report with a successful request result, then the third request allocation system message report is generated, and any one or the earliest system message report in the historical request allocation system message report with a successful request result is deleted.

16. The method for reporting system messages according to any one of claims 1-5, characterized in that, The method further includes: Before sending the list of requested system message reports to the network-side device, the terminal indicates to the network-side device whether it has cached the first requested system message report.

17. The system message reporting method according to claim 16, characterized in that, The terminal instructs the network-side device whether it has cached the system message report allocated in the first request, including: The terminal sends a first indication message to the network-side device, the first indication message being used to directly indicate whether the terminal has cached the system message report allocated by the first request; The first indication message includes at least one of the following: Wireless resource control settings complete; Wireless resource control restoration complete; Wireless resource control reconfiguration complete; Wireless resource control reconstruction completed; Terminal information response.

18. The system message reporting method according to claim 6, characterized in that, The terminal capability is also used to indicate whether the terminal has cached the system message report allocated by the first request.

19. A system message reporting device, characterized in that, Applied to a terminal, the device includes: The first determining module is used to determine the acquisition status information of the first target system message block of the request based on the configuration information of the system message report allocated in the first request; The first sending module is configured to send a list of requested allocation system message reports to the network-side device. The list of requested allocation system message reports includes a second requested allocation system message report. The second requested allocation system message report includes the first requested allocation system message report and / or a third requested allocation system message report. The third requested allocation system message report is generated after the first requested allocation system message report is generated. The first requested allocation system message report is generated based on the acquisition status information of the first target system message block. The system message report for the first request allocation includes at least one of the following: The identifier of the first target system message block; The reason why the first target system message block request failed; The identifier of the first target system message block includes at least one of the following: Identifier for a regular system message block; Identifier of the positioning system information block used for positioning; The identifier of the positioning system information block is used to indicate at least one of the following: The encrypted information in the positioning system information block, the type of global navigation satellite system, and the type of satellite-based augmentation system; The PosSchedulingInfo to which the location system information block belongs is located in the order of posSchedulingInfoList; 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.

20. The system message reporting device according to claim 19, characterized in that, The system message report for the first request allocation includes at least one of the following: The cell identifier of the cell corresponding to the first target system message block; The timestamp when the target system message block was requested; Information on each random access during the request process of the first target system message block; The request method for the first target system message block; The request result of the first target system message block.

21. The system message reporting device according to claim 19, characterized in that, If the identifier of the first target system message block includes the identifier of the location system information block, and the terminal fails to store the encrypted location system information block obtained by discarding the valid key, resulting in the failure of the requested allocation of the system message, the reason for the failure of the first target system message block request includes the absence of a valid key.

22. The system message reporting device according to claim 19, characterized in that, If the number of times the terminal fails to obtain the first target system message block by initiating random access exceeds a first threshold, the reasons for the failure of the first target system message block request include the failure of the random access contention.

23. The system message reporting device according to any one of claims 19-22, characterized in that, The device further includes: The first receiving module is configured to receive a first request message sent by a network-side device before the step of determining the acquisition status information of the first target system message block of the request. The first request message is used to request the system message report list allocated by the first request from the terminal.

24. The system message reporting device according to claim 23, characterized in that, The device further includes: The second sending module is configured to send terminal capabilities to the network-side device before the terminal receives the first request message sent by the network-side device. The terminal capabilities are used to indicate whether the terminal has the ability to report random access reports and / or whether the terminal has the ability to report system message reports allocated by the first request.

25. The system message reporting device according to any one of claims 19-22, characterized in that, The configuration information for the system message report allocated in the first request includes at least one of the following: First information used to indicate whether a system message report allocated by the first request can be generated; Second information for the area used to record the system message report of the first requested allocation; Third information used to record the maximum number of system message reports for request allocation that the terminal can store.

26. The system message reporting device according to claim 25, characterized in that, The device further includes at least one of the following: The first generation module is configured to generate the system message report for the first request allocation when the first information indicates that the system message report for the first request allocation can be generated. The second generation module is configured to not generate the system message report requested by the first request if the first information indicates that the system message report requested by the first request cannot be generated. The third generation module is used to prevent the generation of the system message report allocated by the first request in the event that the first information is missing.

27. The system message reporting device according to claim 25, characterized in that, The device further includes at least one of the following: The fourth generation module is used to generate the system message report for the first request allocation when the first information indicates that the system message report for the first request allocation can be generated. The fifth generation module is configured to not generate the first requested system message report when the first information indicates that the requested system message report cannot be generated. The sixth generation module generates a system message report for the first request allocation if the first information is missing.

28. The system message reporting device according to claim 25, characterized in that, The second information includes at least one of the following: Tracking area TA list; List of residential communities.

29. The system message reporting device according to claim 25, characterized in that, In the absence of the second information, the region for recording the system message report of the first request allocation can be any region.

30. The system message reporting device according to claim 25, characterized in that, The third piece of information is a fixed value or determined based on the network-side device configuration.

31. The system message reporting device according to claim 25, characterized in that, The device further includes: The first update module is used to determine the acquisition status information of the second target system message block after the acquisition status information of the first target system message block is determined, and when the terminal determines that the number of cached historical request allocation system message reports is less than the third information. The seventh generation module is used to generate the system message report for the third request allocation based on the acquisition status information of the second target system message block.

32. The system message reporting device according to claim 25, characterized in that, The device further includes: The second update module is used to determine the acquisition status information of the second target system message block after the acquisition status information of the first target system message block is determined, and when the terminal determines that the number of cached historical request allocation system message reports is equal to the third information. The first judgment module is used to determine whether to generate the third request allocation system message report based on the acquisition status information of the second target system message block and the historical request allocation system message reports stored in the terminal.

33. The system message reporting device according to claim 32, characterized in that, The first judgment module is also used for: If the second target system message block is successfully acquired, it is determined that the system message report allocated by the third request will not be generated; If the acquisition of the second target system message block fails and there is no system message report in the historical request allocation system message report indicating a successful request result, it is determined that the third request allocation system message report will not be generated. If the acquisition of the second target system message block fails, and there is a system message report in the historical request allocation system message report with a successful request result, then the third request allocation system message report is generated, and any one or the earliest system message report in the historical request allocation system message report with a successful request result is deleted.

34. The system message reporting device according to any one of claims 19-22, characterized in that, The device further includes: The first indication module is used to indicate to the network-side device whether the terminal has cached the first requested system message report before sending the list of requested system message reports to the network-side device.

35. The system message reporting device according to claim 34, characterized in that, The first indication module is also used for: Send a first indication message to the network-side device. The first indication message is used to directly indicate whether the terminal has cached the system message report allocated by the first request. The first indication message includes at least one of the following: Wireless resource control settings complete; Wireless resource control restoration complete; Wireless resource control reconfiguration complete; Wireless resource control reconstruction completed; Terminal information response.

36. The system message reporting device according to claim 24, characterized in that, The terminal capability is also used to indicate whether the terminal has cached the system message report allocated by the first request.

37. A terminal, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the system message reporting method as described in any one of claims 1 to 18.

38. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the system message reporting method as described in any one of claims 1 to 18.

Images