System information block validity checking method, apparatus, terminal and storage medium
By using the cell identifier from a list of public or non-public network identifier information to determine the validity of the SIB, the problem of terminals misjudging the validity of the SIB under certain circumstances is solved, and correct SIB checking is achieved.
Patent Information
- Application Number
- CN202110214460.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-02-25
- Publication Date
- 2026-01-30
- Estimated Expiration
- 2041-07-28
AI Technical Summary
In certain situations, a terminal may mistakenly consider an invalid System Information Block (SIB) to be valid, thus continuing to use the invalid SIB and being unable to obtain a new valid SIB.
The validity of the system information block stored in the terminal is determined by the cell identifier corresponding to the first public land mobile network identifier in the public land mobile network identifier information list or the first non-public network identifier in the non-public network identifier information list, thus avoiding misjudgment.
Ensure that the terminal can correctly determine the validity of the SIB when roaming in different networks, reselecting cells, or returning to the network from a non-coverage area, and avoid using invalid SIBs.
Smart Images

Figure CN114980151B_ABST
Abstract
Description
Technical Field
[0001] This application belongs to the field of communication technology, and specifically relates to a method, apparatus, terminal and storage medium for validating system information blocks. Background Technology
[0002] After receiving the System Information Block 1 (SIB1) message, when the terminal requests other System Information Blocks (SIBs), it can check the validity of other SIBs stored by the UE according to the SIB validity check step. If the stored other SIBs are valid, the UE uses the stored other SIBs; otherwise, the UE obtains the SI message(s) according to whether the other SIBs are broadcast.
[0003] According to the existing SIB validity check method, under certain specific circumstances (such as when the terminal is roaming in another network, performing cell reselection, or returning to the network from a non-coverage area), the terminal may recognize an invalid SIB as valid, which will cause the terminal to continue using the invalid SIB instead of obtaining a new corresponding SIB. Summary of the Invention
[0004] This application provides a method, apparatus, terminal, and storage medium for validating system information blocks (SIBs), enabling the terminal to correctly perform SIB validity checks and avoiding the problem that the terminal might mistake an invalid SIB for a valid one under certain circumstances.
[0005] Firstly, a method for validating system information blocks is provided, the method comprising:
[0006] The terminal determines the validity of the System Information Block (SIB) stored in the terminal based on the cell identifier corresponding to the first Public Land Mobile Network (PLN) identifier in the Public Land Mobile Network (PLN) identifier information list; or,
[0007] The terminal determines the validity of the System Information Block (SIB) stored in the terminal based on the cell identifier corresponding to the first non-public network identifier in the non-public network identifier information list.
[0008] Secondly, a system information block validity checking device is provided, comprising:
[0009] The validity check unit is used by the terminal to determine the validity of the System Information Block (SIB) stored in the terminal based on the cell identifier corresponding to the first Public Land Mobile Network (PLN) identifier in the Public Land Mobile Network (PLN) identifier information list; or,
[0010] The terminal determines the validity of the System Information Block (SIB) stored in the terminal based on the cell identifier corresponding to the first non-public network identifier in the non-public network identifier information list.
[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 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.
[0013] Fifthly, a chip is provided, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the method as described in the first aspect.
[0014] In this embodiment, the validity of the System Information Block (SIB) stored in the terminal is determined based on the cell identifier corresponding to the first public land mobile network identifier in the public land mobile network identifier information list or the cell identifier corresponding to the first non-public network identifier in the non-public network identifier information list. This enables the terminal to correctly perform SIB validity checks and avoids the terminal from considering invalid SIBs as valid under certain specific circumstances. Attached Figure Description
[0015] Figure 1 This is a block diagram of a wireless communication system applicable to embodiments of this application;
[0016] Figure 2 One of the flowcharts illustrating the validity check method for system information blocks provided in this application embodiment;
[0017] Figure 3 This diagram illustrates the information used for SIB validity checks in existing technologies when a terminal moves between small areas.
[0018] Figure 4 A schematic diagram illustrating the information used for SIB validity checking when the terminal moves between cells, as provided in this application embodiment.
[0019] Figure 5 A second schematic flowchart illustrating the validity check method for system information blocks provided in this application embodiment;
[0020] Figure 6 The third flowchart illustrates the validity check method for system information blocks provided in this application embodiment;
[0021] Figure 7 A schematic diagram of the structure of the system information block validity checking device provided in the embodiments of this application;
[0022] Figure 8 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;
[0023] Figure 9 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application. Detailed Implementation
[0024] 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.
[0025] 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 use of data can be interchanged 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.
[0026] 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. However, the following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description, but these technologies can also be applied to applications other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.
[0027] Figure 1This diagram illustrates a block 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 or user equipment (UE). The 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), wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), etc. Wearable devices include wristbands, headphones, glasses, etc. It should be noted that this application does not limit the specific type of terminal 11. 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 embodiment of the application, only the base station in the NR system is used as an example, but the specific type of base station is not limited.
[0028] The validity check method for system information blocks provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.
[0029] Figure 2 This is one of the flowcharts illustrating the validity check method for system information blocks provided in the embodiments of this application, such as... Figure 2 As shown, the method includes:
[0030] Step 200: The terminal determines the validity of the System Information Block (SIB) stored in the terminal based on the cell identifier corresponding to the first Public Land Mobile Network (PLN) identifier in the Public Land Mobile Network (PLN) identifier information list; or,
[0031] The terminal determines the validity of the System Information Block (SIB) stored in the terminal based on the cell identifier corresponding to the first non-public network identifier in the non-public network identifier information list.
[0032] It should be noted that the equivalent description of the cell identifier (cellIdentity) corresponding to the first public land mobile network identifier (PLMN-identity) in the public land mobile network identifier information list (PLMN-IdentityInfoList) is the first cell identifier in the public land mobile network identifier information list, i.e., the first cellIdentity in the PLMN-IdentityInfoList.
[0033] The equivalent description of the cell identity corresponding to the first non-public network identity (NPN identity) in the NPN-IdentityInfoList is the first cell identity in the NPN-IdentityInfoList.
[0034] In the prior art, after receiving the SIB1 message, the terminal checks whether its cell access related information cellAccessRelatedInfo contains the public land mobile network identifier (PLMN-Identity) of the public land mobile network (PLMN) selected by the terminal. If it does, the terminal uses the public land mobile network identifier list (PLMN-IdentityList) corresponding to the PLMN-IdentityInfo containing the PLMN-Identity information selected by the UE, the tracking area code (trackingAreaCode), and the cell identifier (cellIdentity).
[0035] After the terminal obtains the master information block (MIB), SIB1, or system information (SI) message in the serving cell, if the terminal wants to store the obtained SIB, it will also store the associated information indicated by the system information scheduling information si-SchedulingInfo. The associated information includes at least one of the following: areaScope (if it appears), the first PLMN-Identity in PLMN-IdentityInfoList or the first NPN Identity in NPN-IdentityInfoList, cellIdentity, systemInformationAreaID (if it appears), and valueTag (if it appears).
[0036] The first NPN Identity in the NPN-IdentityInfoList:
[0037] In the case of a standalone NPN (SNPN) network, it is the SNPN identity; or,
[0038] In the case of a non-standalone NPN network (Public network integrated NPN, PNI-NPN), it is a PNI-NPN identity.
[0039] In the case of a cell-specific SIB, according to the existing protocol, after the terminal completes the SI acquisition step, for UEs with NPN capability and serving cells that only support non-public network NPN-only cells, it is necessary to check whether the first NPN identity, cellIdentity and valueTag in the NPN-IdentityInfoList of the received SIB are exactly the same as those stored by the UE. If they are the same, it is considered that the SIB stored by the UE is valid for the current area.
[0040] For UEs that do not have NPN capability and whose cell is a non-NPN-only cell that only supports non-public network cells, it is necessary to check whether the first PLMN-identity, cellIdentity and valueTag in the PLMN-IdentityInfoList in the received SIB are exactly the same as those stored by the UE. If they are the same, it is considered that the SIB stored by the UE is valid for the current area.
[0041] However, based on the existing SIB validity check procedures, there may be situations where the terminal incorrectly believes that the currently stored SIB is valid, thus causing other problems.
[0042] For example, the SIB validity check issue in roaming situations is as follows:
[0043] Figure 3 This diagram illustrates the information used for SIB validity checks in existing technologies when terminals move between small areas. For example... Figure 3 As shown, assuming a UE's home public land mobile network (HPLMN) has a PLMN-identity of 46006, meaning the UE is a China Unicom user and is currently in a shared radio access network (RAN) cell, Cell 1, the public land mobile network identification information list PLMN-IdentityInfoList received by the UE from this serving cell in SIB1 may contain two public land mobile network identification information PLMN-IdentityInfos. The first PLMN-IdentityInfo contains information related to the mobile operator, including two PLMN-identities, 46000 and 46002, and a corresponding 36-bit cellIdentity, denoted as A. The second PLMN-IdentityInfo contains information related to the China Unicom operator, including one PLMN-identity, 46006, and a corresponding 36-bit cellIdentity, denoted as B.
[0044] After the UE obtains the MIB, SIB1, and other SIBs in Cell 1, if the UE stores other SIBs, the first PLMN-identity in the PLMN-IdentityInfoList is used during the validity check. In this example, the UE stores the mobile operator's PLMN-identity = 46000, and stores the cellIdentity corresponding to the selected / accessed PLMN (i.e., HPLMN, whose PLMN-identity = 46006). Figure 3 When PLMN-identity = 46006, the corresponding cellIdentity is B, that is, the cellIdentity stored by the UE is B.
[0045] When a UE moves to another cell, assuming that the new cell Cell 2 does not have a China Unicom base station, but both China Unicom and China Mobile agree that the UE can roam in Cell 2 across different networks, the UE can reselect and normally camp on the new cell Cell 2. The following situations may occur:
[0046] The UE had never been stationed in Cell 2 before; and,
[0047] The PLMN-identity of the Cell 2 mobile operator's PLMN is the same as the first PLMN-identity in the PLMN-IdentityInfoList in Cell 1; and,
[0048] The cellIdentity corresponding to the PLMN of the mobile operator in Cell 2 is exactly the same as the cellIdentity corresponding to the PLMN of the China Unicom operator selected by the UE in the original Cell 1 cell, both being B; and...
[0049] One or more SIBs stored in the UE have the same valueTag as the corresponding SIB in SIB1 received in Cell 2;
[0050] At this point, the UE will consider the stored valueTag to be the same as the valueTag indicated by SIB1 in Cell 2 as valid, but in reality it is not valid. According to the existing protocol, this will cause the UE not to obtain a new corresponding SIB and to continue using the invalid SIB.
[0051] Similarly, when a UE performs cell reselection or returns to the network from an uncovered area and accesses an acceptable cell, there may be situations where the UE has never camped on that cell before, but the first PLMN-identity and cellIdentity in the PLMN-IdentityInfoList of that cell's SIB1 are the same as the first PLMN-identity and cellIdentity in the UE's stored PLMN-IdentityInfoList, and one or more SIBs in the UE's stored SIBs have the same valueTag as the corresponding SIB in the SIB1 received in that cell. As a result, the UE will not obtain a new corresponding SIB and will continue to use the invalid SIB.
[0052] To address the aforementioned issues, this application proposes determining the validity of the System Information Block (SIB) stored in the terminal based on the cell identifier corresponding to the first Public Land Mobile Network identifier in the Public Land Mobile Network Identifier Information List or the cell identifier corresponding to the first Non-Public Network Identifier in the Non-Public Network Identifier Information List.
[0053] The difference between the embodiments of this application and the prior art is that, in the prior art, when checking the validity of an SIB, the cell identifier stored and received by the terminal is the cellIdentity corresponding to the (home) PLMN / NPN selected / accessed by the terminal; while in the embodiments of this application, the cell identifier stored and received by the terminal is the cell identifier corresponding to the first public land mobile network identifier in the public land mobile network identifier information list or the cell identifier corresponding to the first non-public network identifier in the non-public network identifier information list. Because the cellIdentities of different cells are necessarily different under the same PLMN-identity, if the PLMN-identity stored by the terminal is the same as the PLMN-identity of the SIB received by the terminal, since the cellIdentities are necessarily different, the SIB stored by the terminal will not be judged as valid. This solves the problem of the terminal mistakenly judging an invalid SIB as valid when moving between different cells due to certain specific situations (such as roaming between different networks, performing cell reselection, or returning to the network from a non-coverage area).
[0054] The following specific example illustrates how the system information block validity check method provided in this application solves the SIB validity check problem.
[0055] Figure 4 This is a schematic diagram illustrating the information used by the terminal to check the validity of SIB when it moves between small areas, as provided in the embodiments of this application.
[0056] like Figure 4As shown, assuming a UE's home public land mobile network (HPLMN) has a PLMN-identity of 46006, meaning the UE is a China Unicom user and is currently in a shared radio access network (RAN) cell, Cell 1, the public land mobile network identification information list PLMN-IdentityInfoList received by the UE from this serving cell in SIB1 may contain two public land mobile network identification information PLMN-IdentityInfos. The first PLMN-IdentityInfo contains information related to the mobile operator, including two PLMN-identities, 46000 and 46002, and a corresponding 36-bit cellIdentity, denoted as A. The second PLMN-IdentityInfo contains information related to the China Unicom operator, including one PLMN-identity, 46006, and a corresponding 36-bit cellIdentity, denoted as B. After the UE obtains the MIB, SIB1, and other SIBs in Cell 1, it stores the other SIBs. During validity checks, it uses the first PLMN-identity in the PLMN-IdentityInfoList associated with the SIB. In this example, the UE stores the mobile operator's PLMN-identity = 46000 and the cellIdentity corresponding to the first PLMN-identity in the PLMN-IdentityInfoList. Figure 4 When PLMN-identity = 46000, the corresponding cellIdentity is A, that is, the cellIdentity stored by the UE is A.
[0057] When a UE moves to another cell, assuming that the new cell Cell 2 does not have a China Unicom base station, but both China Unicom and China Mobile agree to allow the UE to roam in Cell 2, the UE can reselect and normally camp on the new cell Cell 2. Figure 4 As shown, the first PLMN-identity in the PLMN-IdentityInfoList received by the UE is PLMN-identity=46000. The cellIdentity corresponding to PLMN-identity=46000 is B, which is inconsistent with the cellIdentity stored by the UE. Therefore, it is determined that the SIB stored by the UE is invalid.
[0058] In this embodiment, the validity of the System Information Block (SIB) stored in the terminal is determined based on the cell identifier corresponding to the first public land mobile network identifier in the public land mobile network identifier information list or the cell identifier corresponding to the first non-public network identifier in the non-public network identifier information list. This enables the terminal to correctly perform SIB validity checks and avoids the terminal from considering invalid SIBs as valid under certain specific circumstances.
[0059] Optionally, the terminal determines the validity of the System Information Block (SIB) stored in the terminal based on the cell identifier corresponding to the first Public Land Mobile Network (PLN) identifier in the Public Land Mobile Network (PLN) Identifier Information List, including:
[0060] If the terminal meets the first preset condition, the terminal determines the validity of the System Information Block (SIB) stored in the terminal based on the cell identifier corresponding to the first Public Land Mobile Network identifier in the Public Land Mobile Network Identifier Information List.
[0061] The first preset condition includes:
[0062] The serving cell is either a non-NPN-only cell or the terminal does not have non-public network NPN capability; and,
[0063] The SIBs stored in the terminal and the SIBs received by the terminal from the serving cell are cell-specific.
[0064] For a given SIB, if the areaScope corresponding to that SIB is set to true, it is area-specific; if the areaScope corresponding to that SIB does not appear, it is cell-specific.
[0065] It is understandable that the situations that satisfy the above first preset condition include:
[0066] The terminal is roaming in a different network and is reselected to a second cell that is different from the public land mobile network (PLMN) of the original first cell, the second cell is a non-NPN-only cell, or the terminal does not have NPN capability, and the SIB stored by the terminal and the SIB received by the terminal from the serving cell are cell-specific.
[0067] or,
[0068] The terminal returns to the network from a non-coverage area and accesses an acceptable cell, wherein the acceptable cell is a non-NPN-only cell or the terminal does not have NPN capability, and the SIB stored by the terminal and the SIB received by the terminal from the serving cell are cell-specific.
[0069] or,
[0070] The terminal performs cell reselection and reselects to an acceptable cell. The acceptable cell is a non-NPN-only cell or the terminal does not have NPN capability, and the SIB stored by the terminal is cell-specific.
[0071] An acceptable cell is a cell where a UE can camp, but only receive limited services (initiating emergency calls and receiving Earthquake and Tsunami Warning System (ETWS) / Commercial Mobile Alert Service (CMAS) notifications). An acceptable cell should meet the minimum set of requirements for implementing emergency calls and receiving ETWS and CMAS notifications in the NR network, primarily including the following requirements: the cell is not prohibited; and it meets cell selection criteria.
[0072] Among them, NPN-only cells are cells that can only be used for normal service by NPN-signed users. UEs with NPN capabilities determine that a cell is an NPN-only cell by detecting that cellReservedForOtherUse IE is set to true, and also by the presence of npn-IdentityInfoList IE in cellAccessRelatedInfo.
[0073] A non-NPN-only cell refers to a cell that does not meet the above NPN-only criteria, i.e., the cellAccessRelatedInfo does not contain a cellReservedForOtherUse IE. Furthermore, a terminal lacking NPN capability means that the terminal does not support access to non-public networks.
[0074] In this embodiment of the application, when the terminal meets the first preset condition, the validity of the system information block (SIB) stored by the terminal is determined based on the cell identifier corresponding to the first public land mobile network identifier in the public land mobile network identifier information list. This enables the terminal to correctly perform SIB validity checks and avoids the terminal from recognizing invalid SIBs as valid in certain specific situations.
[0075] Optionally, the terminal determines the validity of the System Information Block (SIB) stored in the terminal based on the cell identifier corresponding to the first Public Land Mobile Network (PLN) identifier in the Public Land Mobile Network (PLN) Identifier Information List, including:
[0076] After receiving the System Information Block 1 SIB1 message sent by the serving cell, the terminal obtains the first Public Land Mobile Network Identifier (PLMN-identity), the first Cell Identifier (cellIdentity), and the first Value Tag.
[0077] If the first PLMN-identity matches the second PLMN-identity stored in the terminal, the first cellIdentity matches the second cellIdentity stored in the terminal, and the first valueTag matches the second valueTag stored in the terminal, then the SIB stored in the terminal is determined to be valid.
[0078] Wherein, the first PLMN-identity is the first PLMN-identity in the Public Land Mobile Network Identifier Information list of the SIB1 message;
[0079] Among them, the Public Land Mobile Network Identification Information List refers to PLMN-IdentityInfoList;
[0080] The first cellIdentity is the cell identifier corresponding to the first PLMN-identity;
[0081] An equivalent description is that the first cellIdentity is the first cell identifier in the public terrestrial mobile network identifier information list.
[0082] The first valueTag is the value tag corresponding to the SIB in the system information scheduling information si-SchedulingInfo of the SIB1 message.
[0083] It is understood that the value tag in the system information scheduling information si-SchedulingInfo of the SIB1 message can correspond to one or more SIBs. Accordingly, the first valueTag represents the value tag corresponding to one or more SIBs.
[0084] Optionally, if the terminal satisfies the following conditions: the serving cell is not a non-NPN-only cell or the terminal does not have non-public network NPN capability; and the SIB stored by the terminal is cell-specific compared to the SIB received by the terminal from the serving cell, after receiving the System Information Block 1 SIB1 message sent by the serving cell, the terminal obtains the first Public Land Mobile Network Identifier (PLMN-identity), the first Cell Identifier (cellIdentity), and the first Value Tag (valueTag). If the first PLMN-identity matches the second PLMN-identity stored by the terminal, the first cellIdentity matches the second cellIdentity stored by the terminal, and the first valueTag matches the second valueTag stored by the terminal, then the SIB stored by the terminal is determined to be valid.
[0085] Optionally, before determining the validity of the SIB stored by the terminal based on the cell identifier corresponding to the first public land mobile network identifier in the public land mobile network identifier information list, the method further includes:
[0086] After the terminal obtains the system information message (SI message) sent by the serving cell, when storing the SIB contained in the SI message, it stores the second PLMN-identity, the second cellIdentity, and the second valueTag.
[0087] Figure 5 A second flowchart illustrating the validity check method for system information blocks provided in this application embodiment includes:
[0088] Step 500: After the terminal obtains the system information message (SI message) sent by the serving cell, when storing the SIB contained in the SI message, it stores the second PLMN-identity, the second cellIdentity, and the second valueTag.
[0089] Step 501: After receiving the System Information Block 1 (SIB1) message sent by the serving cell, the terminal obtains the first Public Land Mobile Network Identifier (PLMN-identity), the first Cell Identifier (cellIdentity), and the first Value Tag.
[0090] Step 502: If the first PLMN-identity is consistent with the second PLMN-identity stored in the terminal, the first cellIdentity is consistent with the second cellIdentity stored in the terminal, and the first valueTag is consistent with the second valueTag stored in the terminal, then the SIB stored in the terminal is determined to be valid.
[0091] like Figure 5 As shown, before performing a validity check on an SIB, the terminal needs to store the associated information of the SIB. That is, after obtaining the system information message (SI message) sent by the serving cell, when storing the SIB contained in the SI message, the terminal needs to store the second PLMN-identity, the second cellIdentity, and the second valueTag.
[0092] Wherein, the second PLMN-identity is the first PLMN-identity in the list of SIB-associated Public Land Mobile Network Identifiers contained in the SI message;
[0093] It should be noted that the SIB contained in the SI message is the SIB stored in the terminal.
[0094] The second cellIdentity is the cell identifier corresponding to the second PLMN-identity;
[0095] An equivalent description is that the second cellIdentity is the first cell identifier in the list of public land mobile network identifier information associated with the SIB contained in the SI message.
[0096] The second valueTag is the value tag corresponding to the SIB contained in the SI message.
[0097] In this embodiment of the application, the validity of the System Information Block (SIB) stored by the terminal is determined based on the cell identifier corresponding to the first Public Land Mobile Network identifier in the Public Land Mobile Network Identifier Information List. This enables the terminal to correctly perform SIB validity checks and avoids the terminal from considering invalid SIBs as valid under certain specific circumstances.
[0098] In other embodiments of this application, the terminal determines the validity of the System Information Block (SIB) stored in the terminal based on the cell identifier corresponding to the first non-public network identifier in the non-public network identifier information list, including:
[0099] If the terminal meets the second preset condition, the terminal determines the validity of the system information block (SIB) stored in the terminal based on the cell identifier corresponding to the first non-public network identifier in the non-public network identifier information list.
[0100] The second preset condition is:
[0101] The terminal has non-public network NPN capability and serves a cell that only supports non-public network NPN; and...
[0102] The SIBs stored in the terminal and the SIBs received by the terminal from the serving cell are cell-specific.
[0103] It is understandable that the situations that satisfy the above second preset condition include:
[0104] The terminal is roaming in a different network and is reselected to a fourth cell that is different from the public land mobile network (PLMN) of the original third cell. The fourth cell is an NPN-only cell and the terminal has NPN capability. The SIB stored in the terminal and the SIB received by the terminal from the serving cell are cell-specific.
[0105] or,
[0106] The terminal returns to the network from a non-coverage area and accesses an acceptable cell, wherein the acceptable cell is an NPN-only cell and the terminal has NPN capability, and the SIB stored by the terminal and the SIB received by the terminal from the serving cell are cell-specific.
[0107] or,
[0108] The terminal performs cell reselection and reselects to an acceptable cell, wherein the acceptable cell is an NPN-only cell and the terminal has NPN capability, and the SIB stored by the terminal is cell-specific.
[0109] In this context, an NPN-only cell refers to a cell that only supports non-public networks and can only be used for normal services by NPN-signed users. A UE with NPN capability determines that the cell is an NPN-only cell by detecting that `cellReservedForOtherUse IE` is set to true, and also by the presence of `npn-IdentityInfoListIE` in `cellAccessRelatedInfo`. For a terminal to have NPN capability means that the terminal supports access to non-public networks.
[0110] In this embodiment of the application, when the terminal meets the second preset condition, the validity of the system information block (SIB) stored by the terminal is determined based on the cell identifier corresponding to the first non-public network identifier in the non-public network identifier information list. This enables the terminal to correctly perform SIB validity checks and avoids the terminal from recognizing invalid SIBs as valid in certain specific situations.
[0111] Optionally, determining the validity of the System Information Block (SIB) stored in the terminal based on the cell identifier corresponding to the first non-public network identifier in the non-public network identifier information list includes:
[0112] After receiving the SIB1 message sent by the serving cell, the terminal obtains the first non-public network identifier NPNidentity, the third cellIdentity, and the third valueTag;
[0113] If the first NPN identity matches the second NPN identity stored in the terminal, the third cellIdentity matches the fourth cellIdentity stored in the terminal, and the third valueTag matches the fourth valueTag stored in the terminal, then the SIB stored in the terminal is determined to be valid.
[0114] Wherein, the first NPN identity is the first NPN identity in the non-public network identifier information list of the SIB1 message;
[0115] The non-public network identifier information list refers to NPN-IdentityInfoList;
[0116] The third cellIdentity is the cell identifier corresponding to the first NPN identity;
[0117] An equivalent description is that the third cellIdentity is the first cell identifier in the list of non-public network identifier information.
[0118] The first NPN-Identity in NPN-IdentityInfoList can be specifically:
[0119] In the case of a standalone NPN (SNPN) network, it is the SNPN identity; or,
[0120] In the case of a non-standalone NPN network (Public network integrated NPN, PNI-NPN), it is a PNI-NPN identity.
[0121] The third valueTag is the value tag corresponding to the SIB in the system information scheduling information si-SchedulingInfo of the SIB1 message.
[0122] It is understood that the value tag in the system information scheduling information si-SchedulingInfo of the SIB1 message can correspond to one or more SIBs, and correspondingly, the third valueTag represents the value tag corresponding to one or more SIBs.
[0123] Optionally, if the terminal satisfies the following conditions: the terminal has non-public network NPN capability and the serving cell is a cell that only supports non-public network NPN, and the SIB stored by the terminal and the SIB received by the terminal from the serving cell are cell-specific, after receiving the SIB1 message sent by the serving cell, the terminal obtains the first non-public network identifier (NPN identity), the third cellIdentity, and the third valueTag. If the first NPN identity is consistent with the second NPN identity stored by the terminal, the third cellIdentity is consistent with the fourth cellIdentity stored by the terminal, and the third valueTag is consistent with the fourth valueTag stored by the terminal, then the SIB stored by the terminal is determined to be valid.
[0124] Optionally, before determining the validity of the System Information Block (SIB) stored in the terminal based on the cell identifier corresponding to the first non-public network identifier in the non-public network identifier information list, the method further includes:
[0125] After the terminal obtains the system information message (SI message) sent by the serving cell, when storing the SIB contained in the SI message, it stores the second NPN identity, the fourth cellIdentity, and the fourth valueTag.
[0126] Figure 6 The third flowchart illustrates the method for validating system information blocks provided in this application embodiment. This method includes the following steps:
[0127] Step 600: After the terminal obtains the system information message (SI message) sent by the serving cell, when storing the SIB contained in the SI message, it stores the second NPN identity, the fourth cellIdentity, and the fourth valueTag.
[0128] Step 601: After receiving the SIB1 message sent by the serving cell, the terminal obtains the first non-public network identifier NPNidentity, the third cellIdentity, and the third valueTag;
[0129] Step 602: If the first NPN identity is consistent with the second NPN identity stored in the terminal, the third cellIdentity is consistent with the fourth cellIdentity stored in the terminal, and the third valueTag is consistent with the fourth valueTag stored in the terminal, then the SIB stored in the terminal is determined to be valid.
[0130] like Figure 6 As shown, before performing a validity check on an SIB, the terminal needs to store the associated information of the SIB. That is, after obtaining the system information message (SI message) sent by the serving cell, when obtaining and storing the SIB contained in the SI message, the terminal needs to store the second NPN identity, the fourth cellIdentity, and the fourth valueTag.
[0131] Wherein, the second NPN identity is the first NPN identity in the list of non-public network identifier information associated with the SIB contained in the SI message;
[0132] The fourth cellIdentity is the cell identifier corresponding to the second NPN dentity;
[0133] An equivalent description is that the fourth cellIdentity is the first cell identifier in the list of public land mobile network identifier information associated with the SIB contained in the SI message.
[0134] The fourth valueTag is the value tag corresponding to the SIB contained in the SI message.
[0135] In this embodiment of the application, the validity of the System Information Block (SIB) stored by the terminal is determined based on the cell identifier corresponding to the first non-public network identifier in the non-public network identifier information list. This enables the terminal to correctly perform SIB validity checks and avoids the terminal from considering invalid SIBs as valid under certain specific circumstances.
[0136] It should be noted that the system information block validity checking method provided in this application embodiment can be executed by a system information block validity checking device, or by a control module within the system information block validity checking device for executing the system information block validity checking method. This application embodiment uses the execution of the system information block validity checking method by a system information block validity checking device as an example to illustrate the system information block validity checking device provided in this application embodiment.
[0137] Figure 7 This is a schematic diagram of the structure of the system information block validity checking device provided in the embodiments of this application, as shown below. Figure 7 As shown, the device includes: a validity checking unit 710, used for:
[0138] The terminal determines the validity of its stored System Information Block (SIB) based on the cell identifier corresponding to the first Public Land Mobile Network (PLN) identifier in the Public Land Mobile Network (PLN) Identifier Information List; or,
[0139] The terminal determines the validity of the System Information Block (SIB) stored in the terminal based on the cell identifier corresponding to the first non-public network identifier in the non-public network identifier information list.
[0140] In this embodiment, the validity of the System Information Block (SIB) stored in the terminal is determined based on the cell identifier corresponding to the first public land mobile network identifier in the public land mobile network identifier information list or the cell identifier corresponding to the first non-public network identifier in the non-public network identifier information list. This enables the terminal to correctly perform SIB validity checks and avoids the terminal from considering invalid SIBs as valid under certain specific circumstances.
[0141] Optionally, the validity check unit is used for:
[0142] If the terminal meets the first preset condition, the terminal determines the validity of the System Information Block (SIB) stored in the terminal based on the cell identifier corresponding to the first Public Land Mobile Network identifier in the Public Land Mobile Network Identifier Information List.
[0143] The first preset condition includes:
[0144] The serving cell is either a non-NPN-only cell or the terminal does not have non-public network NPN capability; and,
[0145] The SIBs stored in the terminal and the SIBs received by the terminal from the serving cell are cell-specific.
[0146] Optionally, the validity check unit is used for:
[0147] After receiving the System Information Block 1 SIB1 message sent by the serving cell, the terminal obtains the first Public Land Mobile Network Identifier (PLMN-identity), the first Cell Identifier (cellIdentity), and the first Value Tag.
[0148] If the first PLMN-identity is consistent with the second PLMN-identity stored in the terminal, the first cellIdentity is consistent with the second cellIdentity stored in the terminal, and the first valueTag is consistent with the second valueTag stored in the terminal, then the SIB stored in the terminal is determined to be valid.
[0149] Wherein, the first PLMN-identity is the first PLMN-identity in the Public Land Mobile Network Identifier Information list of the SIB1 message;
[0150] The first cellIdentity is the cell identifier corresponding to the first PLMN-identity;
[0151] The first valueTag is the value tag corresponding to the SIB in the system information scheduling information si-SchedulingInfo of the SIB1 message.
[0152] Optionally, it also includes a first storage unit for:
[0153] After the terminal obtains the system information message (SI message) sent by the serving cell, when storing the SIB contained in the SI message, it stores the second PLMN-identity, the second cellIdentity, and the second valueTag.
[0154] Wherein, the second PLMN-identity is the first PLMN-identity in the list of SIB-associated Public Land Mobile Network Identifiers contained in the SI message;
[0155] The second cellIdentity is the cell identifier corresponding to the second PLMN-identity;
[0156] The second valueTag is the value tag corresponding to the SIB contained in the SI message.
[0157] Optionally, the validity check unit is used for:
[0158] If the terminal meets the second preset condition, the terminal determines the validity of the system information block (SIB) stored in the terminal based on the cell identifier corresponding to the first non-public network identifier in the non-public network identifier information list.
[0159] The second preset condition is:
[0160] The terminal has non-public network NPN capability and serves a cell that only supports non-public network NPN; and...
[0161] The SIBs stored in the terminal and the SIBs received by the terminal from the serving cell are cell-specific.
[0162] Optionally, the validity check unit is used for:
[0163] After receiving the SIB1 message sent by the serving cell, the terminal obtains the first non-public network identifier NPNidentity, the third cellIdentity, and the third valueTag;
[0164] If the first NPN identity matches the second NPN identity stored in the terminal, the third cellIdentity matches the fourth cellIdentity stored in the terminal, and the third valueTag matches the fourth valueTag stored in the terminal, then the SIB stored in the terminal is determined to be valid.
[0165] Wherein, the first NPN identity is the first NPN identity in the non-public network identifier information list of the SIB1 message;
[0166] The third cellIdentity is the cell identifier corresponding to the first NPN identity;
[0167] The third valueTag is the value tag corresponding to the SIB in the system information scheduling information si-SchedulingInfo of the SIB1 message.
[0168] Optionally, a second storage unit is also included for:
[0169] After the terminal obtains the system information message (SI message) sent by the serving cell, when storing the SIB contained in the SI message, it stores the second NPN identity, the fourth cellIdentity, and the fourth valueTag.
[0170] Wherein, the second NPN identity is the first NPN identity in the list of non-public network identifier information associated with the SIB contained in the SI message;
[0171] The fourth cellIdentity is the cell identifier corresponding to the second NPN dentity;
[0172] The fourth valueTag is the value tag corresponding to the SIB contained in the SI message.
[0173] The validity check device for system information blocks in this application embodiment can be a device or electronic device with an operating system, or it can be a component, integrated circuit, or chip in a terminal. The electronic device can be a mobile electronic device or a non-mobile electronic device. For example, mobile electronic devices can include, but are not limited to, the types of terminals 11 listed above, and non-mobile electronic devices can be servers, network attached storage (NAS), personal computers (PCs), televisions (TVs), ATMs, or self-service machines, etc. This application embodiment does not make specific limitations.
[0174] The system information block validity checking device provided in this application embodiment can achieve Figure 2 , Figures 4 to 6 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.
[0175] Optional, such as Figure 8 As shown, this application embodiment also provides a communication device 800, including a processor 801, a memory 802, and a program or instruction stored in the memory 802 that can be run on the processor 801. For example, when the communication device 800 is a terminal, when the program or instruction is executed by the processor 801, it implements the various processes of the above-mentioned system information block validity check method embodiment and can achieve the same technical effect. To avoid repetition, it will not be described again here.
[0176] Figure 9 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.
[0177] The terminal 900 includes, but is not limited to, at least some of the following components: radio frequency unit 901, network module 902, audio output unit 903, input unit 904, sensor 905, display unit 906, user input unit 907, interface unit 908, memory 909, and processor 910.
[0178] Those skilled in the art will understand that the terminal 900 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 910 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 9 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.
[0179] It should be understood that, in this embodiment, the input unit 904 may include a graphics processing unit (GPU) 9041 and a microphone 9042. The GPU 9041 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 906 may include a display panel 9061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 907 includes a touch panel 9071 and other input devices 9072. The touch panel 9071 is also called a touch screen. The touch panel 9071 may include a touch detection device and a touch controller. Other input devices 9072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.
[0180] In this embodiment, the radio frequency unit 901 receives downlink data from the network-side device and processes it for the processor 910; additionally, it sends uplink data to the network-side device. Typically, the radio frequency unit 901 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.
[0181] The memory 909 can be used to store software programs or instructions and various data. The memory 909 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 909 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.
[0182] Processor 910 may include one or more processing units; optionally, processor 910 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 910.
[0183] Wherein, the processor 910 is used by the terminal to determine the validity of the System Information Block (SIB) stored in the terminal based on the cell identifier corresponding to the first Public Land Mobile Network (PLN) identifier in the Public Land Mobile Network (PLN) identifier information list; or,
[0184] The terminal determines the validity of the System Information Block (SIB) stored in the terminal based on the cell identifier corresponding to the first non-public network identifier in the non-public network identifier information list.
[0185] In this embodiment, the validity of the System Information Block (SIB) stored in the terminal is determined based on the cell identifier corresponding to the first public land mobile network identifier in the public land mobile network identifier information list or the cell identifier corresponding to the first non-public network identifier in the non-public network identifier information list. This enables the terminal to correctly perform SIB validity checks and avoids the terminal from considering invalid SIBs as valid under certain specific circumstances.
[0186] Optionally, the terminal determines the validity of the System Information Block (SIB) stored in the terminal based on the cell identifier corresponding to the first Public Land Mobile Network (PLN) identifier in the Public Land Mobile Network (PLN) Identifier Information List, including:
[0187] If the terminal meets the first preset condition, the terminal determines the validity of the System Information Block (SIB) stored in the terminal based on the cell identifier corresponding to the first Public Land Mobile Network identifier in the Public Land Mobile Network Identifier Information List.
[0188] The first preset condition includes:
[0189] The serving cell is either a non-NPN-only cell or the terminal does not have non-public network NPN capability; and,
[0190] The SIBs stored in the terminal and the SIBs received by the terminal from the serving cell are cell-specific.
[0191] Optionally, the processor 910 is also used for:
[0192] After receiving the System Information Block 1 SIB1 message sent by the serving cell, the terminal obtains the first Public Land Mobile Network Identifier (PLMN-identity), the first Cell Identifier (cellIdentity), and the first Value Tag.
[0193] If the first PLMN-identity is consistent with the second PLMN-identity stored in the terminal, the first cellIdentity is consistent with the second cellIdentity stored in the terminal, and the first valueTag is consistent with the second valueTag stored in the terminal, then the SIB stored in the terminal is determined to be valid.
[0194] Wherein, the first PLMN-identity is the first PLMN-identity in the Public Land Mobile Network Identifier Information list of the SIB1 message;
[0195] The first cellIdentity is the cell identifier corresponding to the first PLMN-identity;
[0196] The first valueTag is the value tag corresponding to the SIB in the system information scheduling information si-SchedulingInfo of the SIB1 message.
[0197] Optionally, the processor 910 is also used for:
[0198] After the terminal obtains the system information message (SI message) sent by the serving cell, when storing the SIB contained in the SI message, it stores the second PLMN-identity, the second cellIdentity, and the second valueTag.
[0199] Wherein, the second PLMN-identity is the first PLMN-identity in the list of SIB-associated Public Land Mobile Network Identifiers contained in the SI message;
[0200] The second cellIdentity is the cell identifier corresponding to the second PLMN-identity;
[0201] The second valueTag is the value tag corresponding to the SIB contained in the SI message.
[0202] Optionally, the terminal determines the validity of the System Information Block (SIB) stored in the terminal based on the cell identifier corresponding to the first non-public network identifier in the non-public network identifier information list, including:
[0203] If the terminal meets the second preset condition, the terminal determines the validity of the system information block (SIB) stored in the terminal based on the cell identifier corresponding to the first non-public network identifier in the non-public network identifier information list.
[0204] The second preset condition is:
[0205] The terminal has non-public network NPN capability and serves a cell that only supports non-public network NPN; and...
[0206] The SIBs stored in the terminal and the SIBs received by the terminal from the serving cell are cell-specific.
[0207] Optionally, the processor 910 is also used for:
[0208] After receiving the SIB1 message sent by the serving cell, the terminal obtains the first non-public network identifier NPNidentity, the third cellIdentity, and the third valueTag;
[0209] If the first NPN identity matches the second NPN identity stored in the terminal, the third cellIdentity matches the fourth cellIdentity stored in the terminal, and the third valueTag matches the fourth valueTag stored in the terminal, then the SIB stored in the terminal is determined to be valid.
[0210] Wherein, the first NPN identity is the first NPN identity in the non-public network identifier information list of the SIB1 message;
[0211] The third cellIdentity is the cell identifier corresponding to the first NPN identity;
[0212] The third valueTag is the value tag corresponding to the SIB in the system information scheduling information si-SchedulingInfo of the SIB1 message.
[0213] Optionally, the processor 910 is also used for:
[0214] After the terminal obtains the system information message (SI message) sent by the serving cell, when storing the SIB contained in the SI message, it stores the second NPN identity, the fourth cellIdentity, and the fourth valueTag.
[0215] Wherein, the second NPN identity is the first NPN identity in the list of non-public network identifier information associated with the SIB contained in the SI message;
[0216] The fourth cellIdentity is the cell identifier corresponding to the second NPN dentity;
[0217] The fourth valueTag is the value tag corresponding to the SIB contained in the SI message.
[0218] The terminal embodiment in this application is a product embodiment corresponding to the above method embodiment. All implementation methods in the above method embodiment are applicable to this terminal embodiment and can achieve the same or similar technical effects, so they will not be described again here.
[0219] 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 information block validity check method embodiment and achieve the same technical effect. To avoid repetition, they will not be described again here.
[0220] 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.
[0221] 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 information block validity check method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.
[0222] 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.
[0223] 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 additional 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 reverse order, 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.
[0224] 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 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.
[0225] 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 validity check of a system information block, characterized in that, Comprising: The terminal determines validity of system information block (SIB) stored by the terminal based on cell identity corresponding to the first public land mobile network (PLMN) identity in the list of PLMN identity information; Or, The terminal determines validity of system information block (SIB) stored by the terminal based on cell identity corresponding to the first non-public network (NPN) identity in the list of NPN identity information; Wherein, the cell identity is the first cell identity in the list of PLMN identity information or the cell identity is the first cell identity in the list of NPN identity information; The terminal determines validity of system information block (SIB) stored by the terminal based on cell identity corresponding to the first public land mobile network (PLMN) identity in the list of PLMN identity information, comprising: In a case that the terminal meets a first preset condition, the terminal determines validity of system information block (SIB) stored by the terminal based on cell identity corresponding to the first PLMN identity in the list of PLMN identity information; Wherein, the first preset condition comprises: The serving cell is a non-PLMN-only cell or the terminal is not NPN capable; and The SIB stored by the terminal and the SIB received by the terminal from the serving cell are cell-specific. The terminal determines validity of system information block (SIB) stored by the terminal based on cell identity corresponding to the first non-public network (NPN) identity in the list of NPN identity information, comprising: In a case that the terminal meets a second preset condition, the terminal determines validity of system information block (SIB) stored by the terminal based on cell identity corresponding to the first NPN identity in the list of NPN identity information; Wherein, the second preset condition comprises: The terminal is NPN capable and the serving cell is a NPN-only cell; and The SIB stored by the terminal and the SIB received by the terminal from the serving cell are cell-specific.
2. The method of validity check of system information block according to claim 1, characterized in that, The terminal determines validity of system information block (SIB) stored by the terminal based on cell identity corresponding to the first public land mobile network (PLMN) identity in the list of PLMN identity information, comprising: After the terminal receives a system information block 1 (SIB1) message sent by a serving cell, a first public land mobile network (PLMN) identity is acquired PLMN-identity , a first cell identity cellIdentity , and a first value tag valueTag ; In the first PLMN-identity agreement with the second PLMN-identity stored by the terminal, the first cellIdentity agreement with the second cellIdentity stored by the terminal, and the first valueTag agreement with the second valueTag stored by the terminal, it is determined that the SIB stored by the terminal is valid. The first PLMN-identity is the first one in the public land mobile network identification information list of the SIB1 message PLMN-identity ; the first cellIdentity for the first PLMN-identity a corresponding cell identity; The first valueTag Value tag corresponding to the SIB in the system information scheduling information si-SchedulingInfo of the SIB1 message.
3. The method of validity check of a system information block according to any of claims 1 to 2, characterized in that, Before the terminal determines validity of SIB stored by the terminal based on cell identity corresponding to the first PLMN identity in the list of PLMN identity information, further comprising: When the terminal stores SIBs contained in a system information message (SI message) transmitted by a serving cell after acquiring the SI message, the second PLMN-identity , the second cellIdentity , and the second valueTag ; Among them, the second PLMN-identity The first one in the list of public land mobile network identification information associated with the SIB contained in the SI message PLMN-identity ; the second cellIdentity for the second PLMN-identity a corresponding cell identity; The second valueTag Value tag corresponding to the SIB included in the SI message.
4. The method of validity check of system information block according to claim 1, characterized in that, determine validity of a system information block (SIB) stored by the terminal based on a cell identity corresponding to a first non-public network (NPN) identity in a NPN identity information list, comprises: After the terminal receives the SIB1 message sent by the serving cell, the first non-public network identity NPN identity, the third cellIdentity and the third valueTag ; In case the first NPN identity is identical to a second NPN identity stored by the terminal, the third cellIdentity is identical to a fourth cellIdentity identity stored by the terminal, and the third valueTag is identical to a fourth valueTag identity stored by the terminal, it is determined that the SIB stored by the terminal is valid. wherein the first NPN identity is a first NPN identity in a NPN identity information list of the SIB1 message; The third cellIdentity A cell identity corresponding to the first NPN identity; The third valueTag is a value tag corresponding to the SIB in the system information scheduling information si-SchedulingInfo of the SIB1 message.
5. The method of validity check of system information block according to claim 1 or 4, characterized in that, before determining the validity of the SIB stored by the terminal based on the cell identity corresponding to the first NPN identity in the NPN identity information list, further comprises: When the terminal stores the SIB contained in the system information message SI message sent by the serving cell after acquiring the SI message, the second NPN identity, the fourth cellIdentity and the fourth valueTag ; wherein the second NPN identity is a first NPN identity in a NPN identity information list associated with a SIB contained in the SI message; the fourth cellIdentity a cell identity corresponding to the second NPN identity; The fourth valueTag Value tag corresponding to the SIB contained in the SI message.
6. An apparatus for validity check of a system information block, characterized by comprises: an validity checking unit, configured to determine validity of a system information block (SIB) stored by the terminal based on a cell identity corresponding to a first public land mobile network (PLMN) identity in a PLMN identity information list; or, determine validity of a system information block (SIB) stored by the terminal based on a cell identity corresponding to a first non-public network (NPN) identity in a NPN identity information list; wherein the cell identity is a first cell identity in the PLMN identity information list or the cell identity is a first cell identity in the NPN identity information list; the validity checking unit is configured to: in a case where the terminal meets a first preset condition, determine validity of a system information block (SIB) stored by the terminal based on a cell identity corresponding to a first public land mobile network (PLMN) identity in a PLMN identity information list; wherein the first preset condition comprises: a serving cell is a non-non-public network (NPN)-only cell or the terminal does not have NPN capability; and the SIB stored by the terminal and a SIB received by the terminal from the serving cell is cell-specific; in a case where the terminal meets a second preset condition, determine validity of a system information block (SIB) stored by the terminal based on a cell identity corresponding to a first non-public network (NPN) identity in a NPN identity information list; wherein the second preset condition comprises: the terminal has NPN capability and the serving cell is an NPN-only cell; and The SIB stored by the terminal and the SIB received by the terminal from the serving cell are cell-specific.
7. The system information block validity checking apparatus according to claim 6, wherein, The validity checking unit is configured to: After the terminal receives a system information block 1 (SIB1) message sent by a serving cell, a first public land mobile network (PLMN) identity is acquired PLMN-identity , a first cell identity cellIdentity , and a first value tag valueTag In the first PLMN-identity agreement with the second PLMN-identity stored by the terminal, the first cellIdentity agreement with the second cellIdentity stored by the terminal, and the first valueTag agreement with the second valueTag stored by the terminal, it is determined that the SIB stored by the terminal is valid. The first PLMN-identity is the first one in the public land mobile network identification information list of the SIB1 message PLMN-identity ; the first cellIdentity for the first PLMN-identity a corresponding cell identity; The first valueTag Value tag corresponding to the SIB in the system information scheduling information si-SchedulingInfo of the SIB1 message.
8. The system information block validity checking apparatus of any of claims 6 to 7, wherein, Further comprising a first storage unit configured to: When the terminal stores SIBs contained in a system information message (SI message) transmitted by a serving cell after acquiring the SI message, the second PLMN-identity , the second cellIdentity , and the second valueTag ; Among them, the second PLMN-identity The first one in the list of public land mobile network identification information associated with the SIB contained in the SI message PLMN-identity ; the second cellIdentity for the second PLMN-identity a corresponding cell identity; The second valueTag Value tag corresponding to the SIB included in the SI message.
9. The system information block validity checking apparatus according to claim 6, wherein, The validity checking unit is configured to: After the terminal receives the SIB1 message sent by the serving cell, the first non-public network identity NPN identity, the third cellIdentity and the third valueTag ; In case the first NPN identity is identical to a second NPN identity stored by the terminal, the third cellIdentity is identical to a fourth cellIdentity identity stored by the terminal, and the third valueTag is identical to a fourth valueTag identity stored by the terminal, it is determined that the SIB stored by the terminal is valid. The first NPN identity is the first NPN identity in a list of non-public network identity information of the SIB1 message. The third cellIdentity A cell identity corresponding to the first NPN identity; The third valueTag is a value tag corresponding to the SIB in the system information scheduling information si-SchedulingInfo of the SIB1 message.
10. The system information block validity checking apparatus according to claim 6 or 9, characterized by, Further comprising a second storage unit configured to: When the terminal stores the SIB contained in the system information message SI message sent by the serving cell after acquiring the SI message, the second NPN identity, the fourth cellIdentity and the fourth valueTag ; The second NPN identity is the first NPN identity in a list of non-public network identity information associated with the SIB contained in the SI message. the fourth cellIdentity a cell identity corresponding to the second NPN identity; The fourth valueTag Value tag corresponding to the SIB included in the SI message.
11. A terminal, characterized by comprising: A processor, a memory, and a program or instructions stored on the memory and executable on the processor, the program or instructions being executed by the processor to implement the steps of the system information block validity checking method according to any one of claims 1 to 5.
12. A readable storage medium, characterized by, A readable storage medium storing a program or instructions, the program or instructions being executed by a processor to implement the steps of the system information block validity checking method according to any one of claims 1 to 5.