Information acquisition method, information indication method, information acquisition device, information indication device and communication equipment

Abstract

The invention discloses an information obtaining method, an information indicating method, an information indicating device and communication equipment, and belongs to the technical field of communication. The information obtaining method of the embodiment of the invention comprises the following steps that: a terminal obtains a broadcast state of a system information block 1SIB1 of a service cell of the terminal according to the broadcast state of the system information block 1SIB1 of the service cell of the terminal; acquiring other system information OSI required by the terminal through a first mode or a second mode; wherein the broadcast state of the SIB1 is used for indicating whether the SIB1 is being broadcasted; the first mode comprises the following steps: acquiring an SIB1 of the serving cell, and acquiring an OSI required by the terminal according to the acquired SIB1; and the second mode is that the OSI required by the terminal is requested from network side equipment.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to an information acquisition method, an information indication method, an apparatus, and a communication device. Background Technology

[0002] The primary function of System Information Block 1 (SIB1) is to provide key information required for a terminal to access a cell, including random access parameters. In addition, SIB1 includes scheduling information for Other System Information (OSI), which helps the terminal effectively acquire and manage system information. For example, SIB1 can indicate the broadcast status of OSI, allowing the terminal to obtain the OSI based on the broadcast status indicated in SIB1.

[0003] In SIB1, if the OSI broadcast state is set to broadcast, this state must be maintained for one system information modification cycle; that is, it can only be changed to non-broadcast in the next system information modification cycle. However, if the OSI broadcast state is set to non-broadcast during this cycle, it can be changed to broadcast in the current system information modification cycle. Furthermore, in existing related technologies, changes to the OSI broadcast state in SIB1 do not send short messages to notify the terminal.

[0004] Furthermore, in network energy saving (i.e., on-demand SIB1 transmission) scenarios, NES cells transmit SIB1 on demand. When a connected terminal needs to obtain an OSI, it first requests SIB1. After obtaining the requested SIB1, it may learn from the SIB1 configuration that the OSI of interest is non-broadcast (if SIB1 is requested on demand, OSI is more likely to be requested on demand as well). Therefore, the terminal needs to send two requests to obtain the OSI of interest, increasing the latency and power consumption of the terminal requesting the OSI. This problem also exists for terminals in RRC IDLE / INACTIVE states.

[0005] Therefore, it can be seen that when a terminal obtains the required OSI, it may need to request SIB1 first, which increases the latency and power consumption of obtaining OSI. Summary of the Invention

[0006] This application provides an information acquisition method, information indication method, apparatus, and communication device, which can solve the problems of long latency and high power consumption in terminal acquisition of OSI in existing related technologies.

[0007] Firstly, an information acquisition method is provided, the method comprising:

[0008] The terminal obtains other system information (OSI) required by the terminal through a first method or a second method, based on the broadcast status of the system information block 1SIB1 of the serving cell of the terminal.

[0009] The broadcast status of SIB1 is used to indicate whether SIB1 is being broadcast;

[0010] The first method is to obtain the SIB1 of the serving cell and obtain the OSI required by the terminal based on the obtained SIB1; the second method is to request the OSI required by the terminal from the network-side device.

[0011] Secondly, an information indication method is provided, the method comprising:

[0012] The network-side device uses the second information to indicate the broadcast status of the system information block 1SIB1 of the serving cell of the terminal;

[0013] The second information includes at least one of the main information block (MIB) of the serving cell and the load of the physical broadcast channel (PBCH), and the broadcast status of SIB1 is used to indicate whether SIB1 is being broadcast.

[0014] Thirdly, an information acquisition device is provided for use in a terminal, the device comprising:

[0015] The acquisition module is used to acquire other system information (OSI) required by the terminal according to the broadcast status of the system information block 1SIB1 of the serving cell of the terminal, through a first method or a second method.

[0016] The broadcast status of SIB1 is used to indicate whether SIB1 is being broadcast;

[0017] The first method is to obtain the SIB1 of the serving cell and obtain the OSI required by the terminal based on the obtained SIB1; the second method is to request the OSI required by the terminal from the network-side device.

[0018] Fourthly, an information indication device is provided, applied to network-side equipment, the device comprising:

[0019] The indication module is used to indicate the broadcast status of the system information block 1SIB1 of the serving cell of the terminal through the second information;

[0020] The second information includes at least one of the main information block (MIB) of the serving cell and the load of the physical broadcast channel (PBCH), and the broadcast status of SIB1 is used to indicate whether SIB1 is being broadcast.

[0021] Fifthly, a communication device is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the information acquisition method as described in the first aspect, or implementing the steps of the information indication method as described in the second aspect.

[0022] Sixthly, a terminal is provided, including a processor and a communication interface, wherein the processor is used for:

[0023] Based on the broadcast status of the system information block 1SIB1 of the serving cell of the terminal, other system information OSI required by the terminal is obtained through the first method or the second method;

[0024] The broadcast status of SIB1 is used to indicate whether SIB1 is being broadcast;

[0025] The first method is to obtain the SIB1 of the serving cell and obtain the OSI required by the terminal based on the obtained SIB1; the second method is to request the OSI required by the terminal from the network-side device.

[0026] In a seventh aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used for:

[0027] The broadcast status of the system information block 1SIB1 of the serving cell of the second information indicator terminal is used;

[0028] The second information includes at least one of the main information block (MIB) of the serving cell and the load of the physical broadcast channel (PBCH), and the broadcast status of SIB1 is used to indicate whether SIB1 is being broadcast.

[0029] Eighthly, 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 information acquisition method as described in the first aspect, or the steps of the information indication method as described in the second aspect.

[0030] A ninth aspect provides a wireless communication system, comprising: a terminal and a network-side device, wherein the terminal is configured to perform the steps of the information acquisition method as described in the first aspect, and the network-side device is configured to perform the steps of the information indication method as described in the second aspect.

[0031] In a tenth aspect, 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 information acquisition method as described in the first aspect, or to implement the information indication method as described in the second aspect.

[0032] In an eleventh aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the information acquisition method as described in the first aspect, or the information indication method as described in the second aspect.

[0033] In this embodiment of the application, the terminal can obtain other system information (OSI) required by the terminal through a first method or a second method according to the broadcast status of the 1SIB1 of the serving cell of the terminal; wherein, the first method is: to obtain the SIB1 of the serving cell and obtain the OSI required by the terminal according to the obtained SIB1; the second method is: to request the OSI required by the terminal from the network side device, wherein the broadcast status of the SIB1 is used to indicate whether the SIB1 is being broadcast.

[0034] As can be seen, in this embodiment of the application, the terminal can select a method that matches the broadcast state of SIB1 from the first method and the second method to obtain the required OSI; that is, in this embodiment of the application, the method by which the terminal obtains the required OSI matches the broadcast state of SIB1 of the terminal's serving cell.

[0035] It should be noted that SIB1 can be sent periodically (i.e., in broadcast form) or on demand (i.e., in non-broadcast form under network energy-saving scenarios). Furthermore, the broadcast state of SIB1 is mostly related to the broadcast state of OSI; that is, when the broadcast state of SIB1 is non-broadcast, the broadcast state of OSI is often also non-broadcast. Therefore, the statement that "the method by which the terminal obtains the required OSI matches the broadcast state of SIB1 of the terminal's serving cell" can also be understood as: the method by which the terminal obtains the required OSI matches the broadcast state of OSI. Therefore, in this embodiment, when the terminal needs to obtain OSI, it can obtain the broadcast state of SIB1 (equivalent to determining the broadcast state of OSI based on the broadcast state of SIB1) instead of determining the OSI broadcast state by obtaining SIB1, and then select an appropriate method to obtain OSI based on this. This avoids having to obtain SIB1 first when obtaining the required OSI, thereby reducing the latency and power consumption of obtaining OSI. Attached Figure Description

[0036] Figure 1 This is a block diagram of a wireless communication system applicable to embodiments of this application;

[0037] Figure 2 This is a flowchart of an information acquisition method according to an embodiment of this application;

[0038] Figure 3This is a flowchart of another information indication method in the embodiments of this application;

[0039] Figure 4 This is a structural block diagram of an information acquisition device according to an embodiment of this application;

[0040] Figure 5 This is a structural block diagram of another information indication device in the embodiments of this application;

[0041] Figure 6 This is a structural block diagram of a communication device according to an embodiment of this application;

[0042] Figure 7 This is a structural block diagram of a terminal according to an embodiment of this application;

[0043] Figure 8 This is a structural block diagram of a network-side device in an embodiment of this application. Detailed Implementation

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

[0045] The terms "first," "second," etc., used in 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, without limiting the number of objects; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, "A or B" covers three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0046] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0047] 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), or 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 systems other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0048] 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 be a mobile phone, tablet computer, laptop computer, notebook 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, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart earphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in the embodiments of this application.

[0049] Network-side equipment 12 may include access network equipment or core network equipment. Access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (AS), or Wireless Fidelity (WiFi) nodes, etc. The term "base station" can be referred to as NodeB (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay BaseStation (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmission Reception Point (TRP), or any other suitable term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to any specific technical terminology. It should be noted that this application embodiment only uses a base station in an NR system as an example for description and does not limit the specific type of base station.

[0050] To facilitate understanding of the information acquisition method and information indication method in the embodiments of this application, the following related content will be introduced first:

[0051] It should be noted that the OSI required in this article can also be understood as the OSI of interest; the posOSI required can also be understood as the posOSI of interest.

[0052] OSI includes at least one System Information Block (SIB) in the system information, excluding MIB and SIB1. For example, the OSI required by a terminal in RRC connected state may include at least one of the following: SIB12, SIB13, SIB14, SIB20, SIB21, and the Position System Information Block (posSIB). The OSI required by a terminal in RRC idle / inactive state may include at least some of the OSIs in existing related technologies (such as SIB2 to SIB20).

[0053] In this article, "non-broadcast" can also be understood as on-demand transmission, and "broadcast" can be understood as periodic transmission. On-demand transmission includes at least one of the following: transmission requested by the terminal (e.g., the terminal meets the request conditions), and transmission triggered by the network side (e.g., system information changes).

[0054] NES cell refers to: On-demand SIB1 cell.

[0055] Cell A refers to the cell that provides the NES cell wake-up signal (WUS) configuration. It is generally understood as a cell that periodically broadcasts SIB1, but it is also possible that Cell A may enter the state of requesting SIB1 on demand.

[0056] WUS is used to request the NES cell to send SIB1.

[0057] I. Mechanism for RRC-connected terminals to obtain SIB

[0058] 1. For terminals in RRC connected state, if any one of the following conditions A-1 to A-2 is met, a DedicatedSIBRequest message will be transmitted, and T350 (i.e., the timer for disabling OSI requests in connected state) will be started:

[0059] Item A-1: ​​The terminal's active bandwidth part (BWP) is not configured for the OSI Common Search Spaces (CSS) (i.e., searchSpaceOtherSystemInformation is not configured), and the terminal has not saved a valid version of the required OSI. The terminal determines the System Information (SI) message of its serving cell based on the System Information Scheduling Information (si-SchedulingInfo) or the Location System Information Scheduling Information (posSI-SchedulingInfo) in its saved SIB1. The message includes at least one required OSI, and the network-side device allows the connected terminal to send an OSI request (i.e., a request for on-demand SIBs is configured), and the T350 is not in operation.

[0060] Item A-2: The terminal is a UE communicating with the network side through a relay UE (L2 U2N Remote UE), and the terminal has not yet saved a valid version of the required OSI. The terminal determines that the SI message of the terminal's serving cell includes at least one required OSI based on the si-SchedulingInfo or posSI-SchedulingInfo in its saved SIB1. The network-side equipment allows the connected terminal to send OSI requests (i.e., it is configured with onDemandSIB-Request), and the T350 is not in operation.

[0061] 2. For terminals in RRC connected state, where the terminal's active BWP is configured with a CSS for OSI, and the terminal has not yet saved a valid version of the required OSI / posOSI:

[0062] If the terminal determines, based on the si-SchedulingInfo stored in its SIB1, that the SI message of the terminal's serving cell includes at least one required OSI, and the SI broadcast status (si-BroadcastStatus) in SIB1 is broadcasting, then the terminal obtains the required OSI through broadcasting.

[0063] If the terminal determines, based on the si-SchedulingInfo stored in its SIB1, that the SI message of its serving cell includes at least one required OSI, and the SIB1 indicates that the si-BroadcastStatus is not broadcasting, and the network-side device allows the connected terminal to send an OSI request (i.e., it is configured with onDemandSIB-Request), and the T350 (i.e., the timer that disables connected OSI requests) is not running, then the terminal initiates the transmission of the DedicatedSIBRequest message, starts the T350, and obtains the required OSI through broadcast;

[0064] If the terminal determines, based on the posSI-SchedulingInfo stored in its SIB1, that the SI message of the terminal's serving cell includes at least one required posOSI, and the SIB1 indicates that posSI-BroadcastStatus is broadcasting, then the terminal obtains the required posOSI by broadcasting.

[0065] If the terminal determines, based on the posSI-SchedulingInfo stored in its SIB1, that the SI message of its serving cell includes at least one required posOS, and the posSI-BroadcastStatus in SIB1 is notBroadcasting, and the network-side device allows the connected terminal to send OSI requests (i.e., it is configured with onDemandSIB-Request), and the T350 (i.e., the timer for disabling connected OSI requests) is not running, then the terminal initiates the transmission of the DedicatedSIBRequest message, starts the T350, and obtains the required posOSI through broadcast.

[0066] II. Regarding the Broadcast Status Change of OSI in SIB1

[0067] For a terminal in RRC connected state with its active BWP configured for the OSI common search space, when the terminal needs to obtain the OSI of interest, if the terminal does not know the current OSI broadcast state, then the terminal needs to obtain SIB1 first. Specifically, if the terminal has not read SIB1 within the current system information modification period, or if the terminal has obtained SIB1 within the current system information modification period and the OSI broadcast state in SIB1 is set to non-broadcast, the terminal cannot determine the current OSI broadcast state in SIB1.

[0068] III. OD-SIB1 for Network Energy Saving Scenarios

[0069] Network energy efficiency is crucial for environmental sustainability, reducing environmental impacts (such as greenhouse gas emissions), and saving operating costs. With the widespread adoption of 5G across various industries and geographic regions, network communications need to handle services and applications with very high data rates (such as extended reality (XR) services), as well as more advanced services and applications. This leads to denser networks, using more antennas, larger bandwidths, and more frequency bands, consuming more network resources and thus having a greater environmental impact. Therefore, the environmental impact of 5G needs to be controlled, and new solutions need to be developed to improve network energy efficiency. To this end, the 3rd Generation Partnership Project (3GPP) initiated network energy efficiency projects in Release 16 and Release 19 of the protocol, and formulated several energy efficiency directions, one of which is OD-SIB1, where NR cells do not periodically send SIB1, but rather terminals in the RRC idle / inactive state request SIB1 from the network side on demand.

[0070] Currently, the UE can obtain the WUS configuration of the NES cell (i.e., the cell that transmits SIB1 on demand, also known as OD-SIB1 Cell) in SIB1 of Cell A (e.g., a cell that periodically transmits SIB1 normally) or OSI of Cell A. The WUS configuration is used by the terminal to request the NES cell to transmit SIB1, and the request signal is the Physical Random Access Channel (PRACH).

[0071] In addition, the parameters that may be included in the WUS configuration are shown in Table 1.

[0072] Table 1 WUS Configuration Examples

[0073]

[0074]

[0075] The information acquisition method provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0076] See Figure 2 The embodiments of this application provide an information acquisition method, which may include the following step 201:

[0077] Step 201: The terminal obtains other system information (OSI) required by the terminal through a first method or a second method based on the broadcast status of the system information block 1SIB1 of the serving cell of the terminal.

[0078] The broadcast status of SIB1 is used to indicate whether SIB1 is being broadcast (i.e., the broadcast status of SIB1 is broadcast or not broadcast); the first method is to obtain the SIB1 of the serving cell and obtain the OSI required by the terminal based on the obtained SIB1; the second method is to request the OSI required by the terminal from the network-side device, that is, the second method can be understood as: the terminal skips the step of obtaining the SIB1 of the serving cell and directly requests the OSI required by the terminal from the network-side device.

[0079] In addition, the serving cell includes at least one of the following:

[0080] The cell where the IDLE / INACTIVE state terminal resides;

[0081] The primary cell (PCell) of the RRC connected terminal.

[0082] Therefore, in the embodiments of this application, the terminal can select the method of obtaining the OSI required by the terminal in the first method or the second method according to the broadcast status of SIB1 of the serving cell, thereby obtaining the OSI required by the terminal through the selected method.

[0083] It should be noted that whether SIB1 is a broadcast can be understood as at least one of the following:

[0084] Is SIB1 being broadcast?

[0085] Is SIB1 being broadcast for some time?

[0086] In one implementation, whether SIB1 is being broadcast can be understood as whether SIB1 is being broadcast for a period of time.

[0087] As can be seen from step 201 above, in this embodiment of the application, the terminal can obtain other system information (OSI) required by the terminal through a first method or a second method according to the broadcast status of the 1SIB1 of the serving cell of the terminal; wherein, the first method is: to obtain the SIB1 of the serving cell and obtain the OSI required by the terminal according to the obtained SIB1; the second method is: to request the OSI required by the terminal from the network side device, wherein the broadcast status of the SIB1 is used to indicate whether the SIB1 is being broadcast.

[0088] As can be seen, in this embodiment of the application, the terminal can select a method that matches the broadcast state of SIB1 from the first method and the second method to obtain the required OSI; that is, in this embodiment of the application, the method by which the terminal obtains the required OSI matches the broadcast state of SIB1 of the terminal's serving cell.

[0089] It should be noted that SIB1 can be sent periodically (i.e., in broadcast form) or on demand (i.e., in non-broadcast form under network energy-saving scenarios). Furthermore, the broadcast state of SIB1 is mostly related to the broadcast state of OSI; that is, when the broadcast state of SIB1 is non-broadcast, the broadcast state of OSI is often also non-broadcast. Therefore, the statement that "the method by which the terminal obtains the required OSI matches the broadcast state of SIB1 of the terminal's serving cell" can also be understood as: the method by which the terminal obtains the required OSI matches the broadcast state of OSI. Therefore, in this embodiment, when the terminal needs to obtain OSI, it can obtain the broadcast state of SIB1 (equivalent to determining the broadcast state of OSI based on the broadcast state of SIB1) instead of determining the OSI broadcast state by obtaining SIB1, and then select an appropriate method to obtain OSI based on this. This avoids having to obtain SIB1 first when obtaining the required OSI, thereby reducing the latency and power consumption of obtaining OSI.

[0090] Optionally, in step 201 above, the terminal obtains other system information (OSI) required by the terminal according to the broadcast status of the system information block 1SIB1 of the serving cell of the terminal through a first method or a second method, including:

[0091] If the terminal meets the first condition, the terminal obtains the required OSI according to the broadcast state of SIB1 of the serving cell through the first method or the second method.

[0092] The first condition includes at least one of the following B-1 to B-3:

[0093] Item B-1: The active bandwidth portion (BWP) of the terminal is configured for the OSI common search space;

[0094] It should be noted that if the terminal's active BWP is configured with the Common Search Space (CSS) for OSI, it means that the terminal needs to obtain the required OSI via broadcast.

[0095] Item B-2: The terminal does not store a valid version of the OSI required by the terminal;

[0096] It should be noted that if the terminal currently needs to obtain the required OSI, but the terminal does not currently have a valid version of the required OSI saved, then it is determined that the terminal currently needs to obtain the required OSI.

[0097] Item B-3: The terminal determines, based on the first information, that the system information (SI) message of the serving cell includes at least one OSI required by the terminal, wherein the first information includes SI scheduling information stored in SIB1 by the terminal;

[0098] It should be noted that if the terminal determines, based on the SI scheduling information currently stored in SIB1, that the SI message of the serving cell of the terminal includes at least one OSI required by the terminal, it means that the serving cell can provide the OSI required by the terminal, and only then does the terminal need to obtain the OSI it is interested in.

[0099] As can be seen from items B-1 to B-3 above, if the terminal satisfies at least one of B-1 to B-3 above, the terminal needs to obtain its required OSI, and thus can obtain the required OSI of the terminal through the first method or the second method according to the broadcast state of 1SIB1 of the terminal's serving cell.

[0100] Item B-4: The broadcast status of the OSI required by the terminal is unknown.

[0101] For item B-4, the terminal does not know the broadcast state of the OSI required by the terminal in at least one of the following situations:

[0102] The terminal did not read SIB1 within a system information modification cycle;

[0103] If the terminal has obtained SIB1 within a system information modification cycle and the broadcast status of OSI in SIB1 is set to non-broadcast, the broadcast status of the OSI required by the terminal is unknown.

[0104] For example, during the Nth system information modification cycle, the terminal received a system information change notification; during the N+1th system information modification cycle, the terminal received the new SIB1:

[0105] If the new SIB1 indication OSI broadcast status received by the terminal during the N+1th system information modification period is broadcast, then the terminal needs to obtain OSI during the N+1th system information modification period. The terminal can determine that the broadcast status of the OSI it is interested in has always been broadcast, that is, the broadcast status of the OSI it needs is known.

[0106] or,

[0107] If the terminal receives a new SIB1 indicating that the OSI broadcast state is broadcast during the (N+1)th system information modification period, and the network-side device changes the OSI broadcast state to non-broadcast during the (N+2)th system information modification period and sends a new SIB1, but this change from broadcast to non-broadcast does not notify the terminal, then the terminal does not obtain the new SIB1 during the (N+2)th system information modification period. Therefore, when the terminal needs to obtain the OSI during the (N+2)th modification period, the broadcast state of the required OSI is unknown.

[0108] or,

[0109] If the terminal receives a new SIB1 indicating that the OSI broadcast status is non-broadcast during the N+1th system information modification period, and the network-side device changes the OSI broadcast status to broadcast during the N+1th system information modification period and sends a new SIB1, the change of OSI from non-broadcast to broadcast is not notified to the terminal. Therefore, when the terminal needs to obtain the OSI at some time during the N+1th modification period, the broadcast status of the required OSI is unknown at that time.

[0110] As described above, if the terminal does not know the broadcast state of the OSI it needs, it means the terminal needs to acquire SIB1. When acquiring SIB1 is required, the terminal then determines whether to acquire SIB1 based on the broadcast state of SIB1 of the serving cell. Conversely, in some cases, the terminal knows the broadcast state of the OSI it needs. In this case, the terminal can directly determine how to acquire the OSI based on the known broadcast state. The terminal itself does not need to acquire SIB1, and therefore does not need to confirm the broadcast state of SIB1 and acquire the OSI based on it.

[0111] Furthermore, the content of the first condition mentioned above may vary depending on the state of the terminal, as illustrated in Examples 1 and 2 below:

[0112] Example 1: When the terminal is in Radio Resource Control (RRC) connected state, the first condition includes at least one of B-1 to B-4 above; that is, when the terminal is in RRC connected state and satisfies at least one of B-1 to B-4 above, the terminal can obtain the OSI required by the terminal through the first method or the second method according to the broadcast state of SIB1 of the terminal's serving cell.

[0113] For example, in one embodiment, if the terminal is in RRC connected state and satisfies items B-1 to B-4 above, the terminal can obtain the required OSI through the first method or the second method according to the broadcast state of SIB1 of the terminal's serving cell.

[0114] Example 2: When the terminal is in the RRC IDLE state or the RRC INACTIVE state, the first condition includes at least one of B-2 to B-4 above; that is, when the terminal is in the RRC IDLE state or the RRC INACTIVE state and satisfies at least one of B-2 to B-4 above, the terminal can obtain the OSI required by the terminal through the first method or the second method according to the broadcast state of SIB1 of the terminal's serving cell.

[0115] For example, in one embodiment, if the terminal is in RRC IDLE state or RRC INACTIVE state and satisfies items B-2 to B-4 above, the terminal can obtain the OSI required by the terminal through the first method or the second method according to the broadcast state of SIB1 of the terminal's serving cell.

[0116] Furthermore, if the terminal does not meet at least one of B-1 to B-3 above, it means that the terminal does not need to obtain its required OSI. This can also be understood as: if the terminal does not need OSI, then the terminal does not obtain OSI through the first method or the second method according to the broadcast state of SIB1 of the serving cell.

[0117] For example, if the terminal does not meet the above B-1 condition, that is, if the terminal's active BWP is not configured with a CSS for OSI, the network side can send OSI to the terminal through dedicated signaling, without the terminal needing to request OSI from the network side device. Therefore, in this case, the terminal does not need to perform the above step 201.

[0118] For example, if the terminal does not meet the above B-2 condition, it means that the terminal does not have an OSI that is of interest. Therefore, in this case, the terminal does not need to execute step 201.

[0119] For example, if the terminal does not meet the above B-3 conditions, that is, if the OSI is not included in the System Information (SI) message of the serving cell as determined by the first information, it means that the serving cell does not send or support the OSI required by the terminal. Therefore, in this case, the terminal does not need to execute step 201.

[0120] Optionally, in step 201 above, the terminal obtains other system information (OSI) required by the terminal through a first method or a second method based on the broadcast status of the system information block 1SIB1 of the serving cell of the terminal, including the following items C-1 or C-2:

[0121] Item C-1: When the terminal is in the Radio Resource Control (RRC) connected state and the broadcast status of SIB1 of the serving cell indicates that SIB1 is not broadcast (i.e., the broadcast status of SIB1 is non-broadcast), the terminal obtains the OSI required by the terminal through the second method;

[0122] SIB1 includes indication information used to indicate the OSI broadcast status.

[0123] As shown in item C-1, when the terminal is in RRC connected state, if the terminal determines that it needs to obtain the required OSI, then the terminal can obtain the broadcast status of SIB1 of the serving cell. If the broadcast status of SIB1 is non-broadcast, the terminal can request the required OSI from the network-side device. For example, the terminal can directly send a DedicatedSIBRequest to the network-side device to request the OSI required by the terminal.

[0124] It should be noted that when the broadcast status of SIB1 of the serving cell of the terminal is non-broadcast, the OSI is also likely to be non-broadcast (especially in network energy-saving scenarios). In this case, if the terminal obtains SIB1 first and then obtains the required OSI based on SIB1, the SIB1 requested by the terminal may indicate that the OSI is non-broadcast. If the SIB1 indicates that the OSI is non-broadcast, it can be changed to broadcast during the current system information modification cycle. Moreover, the change of OSI broadcast status does not notify the terminal, which makes the terminal need to obtain SIB1 first, thereby increasing the latency and power consumption of the terminal requesting the OSI.

[0125] In this embodiment of the application, when the terminal is in RRC connected state and the broadcast state of SIB1 of the serving cell is non-broadcast, the terminal can directly request the required OSI from the network-side device, skipping the request for SIB1, thereby reducing the latency and power consumption of the terminal in obtaining OSI, and also benefiting network energy saving.

[0126] As can be seen, in this embodiment of the application, when the terminal is in the RRC connected state, if the broadcast state of SIB1 of the serving cell of the terminal is non-broadcast, the terminal can determine that the broadcast state of OSI is also non-broadcast; that is, the terminal can determine the broadcast state of OSI through the broadcast state of SIB1 of the serving cell, and thus can send a DedicatedSIBRequest to request the OSI required by the terminal.

[0127] Item C-2: When the terminal is in RRC connected state and the broadcast status of SIB1 of the serving cell indicates that SIB1 is being broadcast (i.e., the broadcast status of SIB1 is broadcast), the terminal obtains the OSI required by the terminal through the first method.

[0128] As shown in item C-2, when the terminal is in the RRC connected state, if the terminal determines that it needs to obtain the required OSI, then the terminal can obtain the broadcast status of the serving cell's SIB1. If the broadcast status of SIB1 is broadcast, the terminal can first obtain SIB1, and then obtain the required OSI based on the obtained SIB1.

[0129] In one embodiment, the method further includes: the terminal receiving second indication information, wherein the second indication information is used to indicate whether SIB1 is being broadcast.

[0130] In one embodiment, the terminal receiving second indication information includes: the terminal receiving second indication information from the MIB.

[0131] In one alternative implementation, when the terminal is in RRC connection state and the second indication information indicates that SIB1 is being broadcast (i.e., the broadcast state of SIB1 is broadcast), the terminal obtains the OSI required by the terminal through the first method.

[0132] In one optional implementation, when the terminal is in the Radio Resource Control (RRC) connected state and the second indication information indicates that the SIB is not being broadcast (i.e., the broadcast state of SIB1 is non-broadcast), the terminal obtains the OSI required by the terminal through the second method.

[0133] Optionally, the terminal obtains the OSI required by the terminal through the second method, including:

[0134] If the second condition is met, the terminal requests the OSI required by the network-side device;

[0135] The second condition includes at least one of the following:

[0136] The network-side device allows connected terminals to request the OSI required by the terminal from the network-side device;

[0137] The OSI-requested timer is not running.

[0138] Optionally, the method further includes:

[0139] After the terminal requests the OSI required by the network-side device, the terminal starts a timer to disable the OSI request.

[0140] In this context, the network-side device allows connected terminals to request the OSI required by the terminal from the network-side device. This can also be understood as the terminal being configured to send SIB requests on demand (onDemandSIB-Request).

[0141] Therefore, if the terminal is in RRC connected state and the broadcast state of SIB1 of the terminal's serving cell is non-broadcast, the terminal can obtain the required OSI through the second method described above. However, in this case, if the terminal meets the second condition described above, it can obtain the required OSI through the second method described above.

[0142] Additionally, an OSI request disable timer is used to disable requests for the corresponding OSI. In one implementation, the OSI request disable timer is configured per OSI (i.e., one disable timer can be configured for each OSI). In this case, for example, when a terminal requests OSI 12, the disable timer corresponding to OSI 12 is started. During the execution of the disable timer corresponding to OSI 12, the terminal is prohibited from requesting OSI 12 again.

[0143] or,

[0144] Optionally, multiple OSIs can be configured with a single prohibition timer, i.e., a T350. In this case, if a terminal requests the same OSI, it needs to wait for the prohibition timer to expire; if it does not request the same OSI, it does not need to wait for the timer to expire. For example, when a terminal requests OSI 12, T350 is started. During the prohibition timer's operation, the terminal is prohibited from requesting OSI 12 again, but the terminal can request OSI 13.

[0145] Optionally, the terminal obtains other system information (OSI) required by the terminal according to the broadcast state of the system information block 1SIB1 of the serving cell of the terminal through a first method or a second method, including:

[0146] When the terminal is in RRC idle state or RRC inactive state, the terminal obtains the required OSI according to the broadcast state of SIB1 of the serving cell and the validity of the OSI request configuration information through the first method or the second method.

[0147] It should be noted that the validity of the OSI request configuration information used to request OSI differs depending on the terminal's RRC state (e.g., RRC connected, RRC idle, RRC inactive). For example, when the terminal is in the RRC connected state, the OSI request configuration information used for OSI requests is always valid. In this case, the terminal does not need to determine the validity of the OSI request configuration information; it can choose between the first and second methods to obtain the required OSI based on the broadcast state of the serving cell's SIB1. However, when the terminal is in the RRC idle or RRC inactive state, the OSI request configuration information stored by the terminal may not always be valid. Therefore, in this case, the terminal needs to combine the validity of the OSI request configuration information with the broadcast state of the serving cell's SIB1 to determine which method to use to obtain the required OSI.

[0148] Optionally, the terminal obtains the required OSI based on the broadcast status of the serving cell's SIB1 and the validity of the OSI request configuration information, using either the first or second method, including one of the following D-1 to D-3:

[0149] Item D-1: If the broadcast status of SIB1 in the serving cell indicates that SIB1 is not broadcast (i.e., the broadcast status of SIB1 is non-broadcast), and the OSI request configuration information is valid, the terminal obtains the OSI required by the terminal through the second method.

[0150] Referring to the relevant content in section C-1 above, when the broadcast state of SIB1 of the serving cell is non-broadcast, the terminal can obtain the required OSI through the second method. However, when the terminal is in the RRC idle state or RRC inactive state, it is also necessary to meet the condition that the OSI request configuration information is valid. In this way, the terminal can obtain the required OSI through the second method by using valid OSI request configuration information, thereby reducing the latency and power consumption of the terminal in obtaining the OSI.

[0151] Optionally, the OSI request configuration information includes at least one of the following:

[0152] Information indicating the OSI request method;

[0153] Information indicating the requested resource in OSI.

[0154] The OSI request methods include the method based on RRC System Info Request (RRCSystemInfoRequest) (i.e., msg 3based) and the method based on random access preamble request (i.e., msg 1-based). When the OSI request method is msg 1-based, the OSI request resources include msg 1-based request resources, such as available preamble resources, available RO configurations, etc.

[0155] For example, if the OSI request method is msg 1-based, the terminal requests the required OSI by sending msg 1 to the network-side device; or, if the OSI request method is msg 3-based, the terminal requests the required OSI by sending an RRC system information request message to the network-side device.

[0156] It should be noted that if the OSI request method is msg 3-based, the terminal can use public random access resources when sending msg 3. Therefore, in this case, it is not necessary to configure OSI request resources for the terminal. However, if the OSI request method is msg 1-based, the network-side device needs to configure resources such as the preamble used when the terminal sends msg 1.

[0157] Item D-2: When the broadcast status of SIB1 in the serving cell indicates that SIB1 is being broadcast (i.e., the broadcast status of SIB1 is broadcast), the terminal obtains the OSI required by the terminal through the first method;

[0158] Referring to the relevant content in section C-2 above, when the broadcast state of SIB1 of the serving cell is broadcast, the terminal can obtain the OSI required by the terminal through the first method, that is, the terminal rereads SIB1 to obtain the latest OSI request configuration information.

[0159] Item D-3: If the OSI request configuration information is invalid, the terminal obtains the OSI required by the terminal through the first method.

[0160] If the OSI request configuration information is invalid, it means that the terminal cannot directly request the OSI from the network-side device, that is, it cannot obtain the OSI required by the terminal through the second method. In this case, the terminal can obtain the required OSI through the first method.

[0161] Optionally, the method further includes:

[0162] The terminal determines the validity of the saved OSI request configuration information based on whether it receives the first indication information sent by the network-side device.

[0163] The first indication information includes one of the following:

[0164] System information change notification; a notification message specifically used to indicate changes to OSI request configuration information.

[0165] Therefore, when OSI request configuration information changes, the network-side device can send a system information change notification to the terminal, or send a dedicated instruction message to the terminal indicating that OSI request configuration information has changed.

[0166] The indication information specifically used to indicate changes in OSI request configuration information can be carried through paging messages or short messages. For example, a separate bit can be used in a short message to indicate changes in OSI request configuration information.

[0167] In one embodiment, when the OSI request method changes, the network-side device sends a first indication message; when the OSI request resource changes, the network-side device does not send a first indication message.

[0168] In one embodiment, when the OSI request method changes, the network-side device does not send the first indication information; when the OSI request resource changes, the network-side device sends the first indication information.

[0169] In one embodiment, when at least one of the OSI request method change and OSI request resource change occurs, the network-side device sends a first indication message.

[0170] In one embodiment, when the OSI request method changes, the network-side device sends a first indication message, and the first indication message is indicated by the Xth bit in the short message or paging message (e.g., the bit is 1). When the OSI request resource changes, the network-side device sends a first indication message, and the first indication message is indicated by the Yth bit in the short message or paging message (e.g., the bit is 1).

[0171] According to the above embodiments, when the terminal receives at least one first indication message, it can accurately know whether it is an OSI request method change or an OSI request resource change.

[0172] To facilitate understanding of the OSI request method and the OSI request resource change instruction, the following examples illustrate the first and second aspects: First aspect: Notifying of changes to the OSI request method can be done using either notification method-1 or notification method-2:

[0173] Notification Method 1: Use a separate bit in the short message to indicate a change in the OSI request method;

[0174] Notification Method 2: Indicate the change of OSI request method through existing system information change notifications.

[0175] For notification method-1 above, for example, if the OSI request method configured in the terminal's SIB1 is msg3based, and the terminal has not received a notification of a change in the OSI request method, then the terminal determines that the msg 3based OSI request method is valid. Alternatively, for example, if the OSI request method configured in the terminal's SIB1 is msg 1based, and the terminal receives a notification of a change in the OSI request method (i.e., changed to msg 3based), then the terminal determines that the msg 3based OSI request method is valid.

[0176] Regarding the above notification method-2, when the OSI request method changes, the network-side device can notify the terminal of the system information change. In this case, the terminal learns that the system information has changed, but is unsure which parts of the system information have changed. After receiving the system information change notification, the terminal can obtain the new SIB1, and then obtain the changed OSI request method from the new SIB1 and save the changed OSI request method. In this way, the terminal always saves a valid OSI request method.

[0177] Alternatively, for notification method-2 above, when the OSI request method changes, the network-side device can notify the terminal system of the information change. In this case, the terminal can obtain the new SIB1 or not. If the terminal obtains the new SIB1, then the terminal has saved a valid OSI request method; if the terminal does not obtain the new SIB1, then the OSI request method saved by the terminal can be considered invalid.

[0178] It should be noted that the OSI request method can be changed between msg 3based and msg 1based.

[0179] Secondly, the terminal determines the validity of the requested resources in the stored OSI model in the following example 3 or example 4:

[0180] Example 3: The protocol stipulates that the terminal system must be notified of the change in OSI requested resources. Specifically, when the terminal receives a short message indicating a system message change, the terminal immediately acquires the new SIB1, thus ensuring that the terminal always retains a valid OSI requested resource.

[0181] Example 4: The protocol stipulates that in the event of a change in the requested OSI resource, the terminal must be notified, and this indication must be sent via a separate bit in the short message. Specifically, when the terminal receives a short message indicating a change in the requested OSI resource, it can determine that the requested OSI resource in the stored SIB1 is invalid; if no change notification is received, the terminal considers the requested OSI resource in the stored SIB1 to be valid. Optionally, when the terminal receives a short message indicating a change in the requested OSI resource, it may choose to obtain the new SIB1 or not.

[0182] Optionally, the method further includes:

[0183] The terminal determines the broadcast status of SIB1 of the serving cell based on the second information;

[0184] The second information includes at least one of the serving cell's Master Information Block (MIB) and the load of the Physical Broadcast Channel (PBCH).

[0185] Optionally, before the terminal determines the broadcast status of SIB1 of the serving cell based on the second information, the method further includes:

[0186] The terminal receives the second information.

[0187] It should be noted that the broadcast status of the serving cell's SIB1 can be determined based on the second information mentioned above, regardless of whether the terminal is in the RRC connected state, RRC idle state, or RRC inactive state.

[0188] Optionally, determining the broadcast status of the serving cell's SIB1 based on the second information includes the following E-1 or E-2 items:

[0189] E-1: The terminal determines the broadcast status of SIB1 of the serving cell based on the second indication information in the MIB of the serving cell, wherein the second indication information is used to indicate whether SIB1 is being broadcast; for example, the broadcast status of SIB1 can be determined by the reserved bits in the MIB; for example, a reserved bit value of 0 in the MIB indicates that SIB1 is broadcasting, and a value of 1 indicates that SIB1 is not broadcasting.

[0190] E-2: The terminal determines the value of Kssb based on the payload of the serving cell's MIB and PBCH, and determines the broadcast state of the serving cell's SIB1 based on the value of Kssb, wherein Kssb represents the offset between the starting position of the first resource block in the Common Resource Block (CRB) that overlaps with the synchronization signal block and the starting position of the synchronization signal block.

[0191] It should be noted that in existing related technologies, for FR1, when the value of Kssb is in the range of 0 to 23, it indicates that the cell will periodically broadcast SIB1. At this time, the terminal can receive SIB1 according to the configuration indicated by the Physical Downlink Control Channel SIB1 Configuration (pdcch-ConfigSIB1) in the MIB. When the value of Kssb is in the range of 24 to 29, in standards prior to R19, it indicates that the cell does not send SIB1. The terminal can use pdcch-ConfigSIB1 and Kssb in the MIB to jointly indicate a cell that sends SIB1. When Kssb = 30, the terminal does not perform any operation (i.e., 30 is a reserved value). When Kssb = 31, pdcch-ConfigSIB1 indicates that no cell in a certain frequency range sends SIB1. For FR2, when Kssb is in the range of 0-11, it indicates that the cell will periodically broadcast SIB1. In this case, the terminal can receive SIB1 according to the configuration indicated by the Physical Downlink Control Channel SIB1 configuration (pdcch-ConfigSIB1) in the MIB. When Kssb is 12 or 13, in standards prior to R19, it indicates that the cell does not send SIB1. The terminal can use pdcch-ConfigSIB1 and Kssb in the MIB to jointly indicate a cell that sends SIB1. When Kssb = 14, the terminal does not perform any operation (i.e., 14 is a reserved value). Here, FR1 and FR2 represent two frequency band ranges of 5G.

[0192] The embodiments of this application can improve the above-mentioned technology by setting the broadcast status of the serving cell's SIB1 based on the value of Kssb determined by the MIB and PBCH payload. For example, in the FR1 case, when the value of Kssb is 30, it is determined that the serving cell's SIB1 is broadcasting (furthermore, the terminal can receive the broadcast SIB1 according to pdcch-ConfigSIB1 in the MIB); when the value of Kssb is some value between 24 and 29 or is 31, it is determined that the serving cell's SIB1 is not broadcasting. It should be noted that when a cell is in the state of sending SIB1 on demand, its Kssb value is a value between 24 and 29 or 31. When a UE sends a WUS request for SIB1 from that cell, the network responds by sending SIB1. In this case, to prevent other UEs from sending WUS when they also need to obtain SIB1, the network can change the Kssb value to 30. This way, when other UEs need to obtain SIB1, they can first obtain Kssb, and determine the method of obtaining SIB1 based on the Kssb value. For example, in the FR2 case, when the Kssb value is 14, it is determined that the serving cell's SIB1 is being broadcast (furthermore, the terminal can receive the broadcast SIB1 according to pdcch-ConfigSIB1 in the MIB); when the Kssb value is 12, 13, or 15, it is determined that the serving cell's SIB1 is not being broadcast, and the serving cell is determined to be a cell sending SIB1 on demand. Optionally, the method further includes:

[0193] If the first and third conditions are met, the terminal acquires the second information;

[0194] The first condition includes at least one of the following:

[0195] The terminal's activated BWP is configured with a common search space for OSI.

[0196] The terminal does not have a valid OSI version required by the terminal;

[0197] The terminal determines, based on the first information, that the SI message of the serving cell includes at least one OSI required by the terminal, and the first information includes SI scheduling information stored in SIB1 by the terminal.

[0198] The broadcast status of the OSI required by the terminal is unknown;

[0199] The third condition includes at least one of the following:

[0200] The terminal is not notified of any broadcast status change in SIB1 of the serving cell.

[0201] The broadcast state change of SIB1 in the serving cell does not need to follow the system information modification cycle, or the behavior of changing the broadcast state of SIB1 in the serving cell from non-broadcast to broadcast does not need to follow the system information modification cycle and the MIB obtained by the terminal within a system information modification cycle (e.g., the current system information modification cycle) indicates that SIB1 is not broadcast (i.e., if the MIB obtained by the terminal within a system information modification cycle indicates that SIB1 is being broadcast, then the terminal can assume that the broadcast state of SIB1 has been broadcast throughout this cycle, and the terminal does not need to reread the MIB to obtain the broadcast state of SIB1).

[0202] It should be noted that the broadcast state change of the serving cell's SIB1 does not need to follow the system information modification cycle. In other words, the broadcast state change of the serving cell's SIB1 can occur at any MIB transmission time, for example, it can be modified once every 80ms.

[0203] Similarly, the change of the broadcast status of SIB1 of the serving cell from non-broadcast to broadcast does not need to follow the system information modification cycle. It can also be understood that the change of the broadcast status of SIB1 of the serving cell from non-broadcast to broadcast can occur at any MIB transmission time, for example, it can be modified once every 80ms.

[0204] As described above, if the terminal meets the first condition, it can obtain the required OSI based on the broadcast state of the serving cell's SIB1 using either the first or second method. However, if the third condition is also met, the terminal can immediately obtain the second information to determine the broadcast state of the serving cell's SIB1. Conversely, if the third condition is not met, it means the terminal does not need to re-obtain the second information to determine the broadcast state of the serving cell's SIB1, which can be interpreted as the currently known broadcast state of the serving cell's SIB1 being correct.

[0205] Optionally, the method further includes:

[0206] In at least one of the following F-1 to F-2 conditions, the terminal determines that the serving cell allows the terminal to determine the broadcast state of the serving cell's SIB1 based on the second information:

[0207] Item F-1: The terminal receives third indication information from the network-side device, wherein the third indication information is used to indicate that the terminal is allowed to determine the broadcast status of the SIB1 of the serving cell based on the second information; for example, the network-side device can indicate to the terminal through dedicated signaling (such as RRC reconfiguration message) or SIB1 or WUS configuration that the serving cell allows the terminal to determine the broadcast status of the SIB1 of the serving cell based on at least one of MIB and PBCH payload.

[0208] Item F-2: The terminal has obtained the wake-up signal configuration of the serving cell. That is, if the terminal has already obtained the WUS configuration of its serving cell, then the terminal can determine, based on the obtained WUS configuration, whether the serving cell allows the terminal to determine the broadcast state of the serving cell's SIB1 according to at least one of the MIB and PBCH payloads. In other words, if the terminal's serving cell has a WUS configuration, then by default, that cell supports determining the broadcast state of the serving cell's SIB1 according to at least one of the MIB and PBCH payloads.

[0209] Among them, WUS configuration refers to the configuration information used by the terminal to request SIB1 of the serving cell. The contents that WUS configuration may include are shown in Table 1 above, and will not be repeated here.

[0210] It should be noted that the serving cell allows the terminal to determine the broadcast status of the serving cell's SIB1 based on the second information, which can also be understood as: the network-side equipment supports the terminal in determining the broadcast status of the serving cell's SIB1 based on the second information.

[0211] In one embodiment, if a terminal in RRC connected state triggers a handover due to mobility (e.g., receiving a handover command), according to existing related technologies, the terminal needs to hand over to the target cell and obtain the SIB1 of the target cell. The terminal can obtain the SIB1 of the target cell in the following ways:

[0212] Method 1: The protocol stipulates that if the target cell is a cell that sends SIB1 on demand, or if the Kssb value of the target cell in FR1 is not in the range of 0 to 23 (or the Kssb value of the target cell in FR2 is not in the range of 0 to 11), then the handover command must carry the SIB1 of the target cell.

[0213] Method 2: If the handover command does not carry the target cell's SIB1, but carries the WUS configuration for requesting SIB1, the terminal sends a WUS to the target cell to request SIB1. If the handover command does not carry either the target cell's SIB1 or the WUS configuration for requesting SIB1, the terminal can assume that the target cell is broadcasting SIB1, and the terminal can receive the broadcast SIB1. Specifically, the terminal can receive the broadcast SIB1 based on the SIB1 reception configuration carried in the handover command or the SIB1 reception configuration in the target cell's MIB.

[0214] Method 3: If the target cell is a cell that transmits SIB1 on demand and has not broadcast SIB1 within a given time period, then the handover command must carry the SIB1 of the target cell. The start time of the given time period can be protocol-defined, such as the moment the terminal receives (or finishes receiving) the handover command, or the moment the terminal completes random access in the target cell. The duration can be protocol-defined, such as within 20ms. The duration can also be a protocol-defined requirement, such as a maximum duration of 50ms. The failure to broadcast SIB1 within the given time period can be indicated by a specific value (e.g., 1) in the first field of the MIB (e.g., the spare field), or by a specific value (e.g., Kssb is 30for in the case of FR1, or 14 in the case of FR2) determined by at least one of the MIB and PBCH of the second cell. It should be noted that when the Kssb value of the FR1 target cell is a value within the range of 24-29 or 31 (or the Kssb value of the FR2 target cell is 12, 13, or 15), the terminal cannot receive the SIB1 broadcast by the target cell based on pdcch-ConfigSIB1 in the MIB, because pdcch-ConfigSIB1 is used to instruct traditional terminals (terminals that do not support on-demand SIB1 requests) how to find the cell sending the SIB1. When the Kssb value of the FR1 target cell is 30, or the Kssb value of the FR2 target cell is 14, the terminal can receive the SIB1 broadcast by the target cell based on pdcch-ConfigSIB1 in the MIB. Therefore, in Method 1, it can be further determined that if the Kssb value of the FR1 target cell is a value within the range of 24-29 or 31 (or the Kssb value of the FR2 target cell is 12, 13, or 15), then the handover command must carry the SIB1 of the target cell. Method 2 may further include the following: if the handover command does not carry the SIB1 of the target cell, and the Kssb value of the FR1 target cell is a value in the range of 24 to 29 and 31 (or the Kssb value of the FR2 target cell is 12, 13 or 15), then the handover command must carry the reception configuration of the SIB1 of the target cell.

[0215] See Figure 3 As shown, embodiments of this application also provide an information indication method, which may include the following step 301:

[0216] Step 301: The network-side device uses the second information to indicate the broadcast status of the system information block 1SIB1 of the serving cell of the terminal.

[0217] The second information includes at least one of the serving cell's Master Information Block (MIB) and the load of the Physical Broadcast Channel (PBCH); the broadcast status of SIB1 is used to indicate whether SIB1 is being broadcast.

[0218] Therefore, the terminal can determine the broadcast state of the serving cell's SIB1 based on at least one of the loads of the serving cell's MIB and PBCH, enabling the terminal to obtain the required OSI through either a first method or a second method based on the broadcast state of SIB1. The first method involves obtaining the serving cell's SIB1 and then obtaining the required OSI based on the obtained SIB1; the second method involves requesting the required OSI from the network-side equipment.

[0219] Optionally, the second indication information in the MIB of the serving cell is used to indicate whether SIB1 is being broadcast;

[0220] or,

[0221] The Kssb value corresponding to the load of the MIB and PBCH of the serving cell is used to indicate the broadcast status of SIB1 of the serving cell.

[0222] Wherein, Kssb represents the offset between the starting position of the first resource block where the common resource block and the synchronization signal block overlap and the starting position of the synchronization signal block.

[0223] It is understood that the two methods by which the terminal determines the broadcast status of the serving cell's SIB1 based on at least one of the loads of the serving cell's MIB and PBCH can be described in detail above and will not be repeated here.

[0224] Optionally, the method further includes:

[0225] The network-side device sends a third instruction message to the terminal;

[0226] The third indication information is used to instruct the serving cell of the terminal to allow the terminal to determine the broadcast status of SIB1 of the serving cell based on the second information.

[0227] In addition, when the terminal receives the third indication information, it indicates that the serving cell of the terminal allows the terminal to determine the broadcast status of SIB1 of the serving cell based on the second information.

[0228] Optionally, the network-side device may instruct the terminal via dedicated signaling (such as an RRC reconfiguration message) or SIB1 or WUS configuration that the serving cell allows the terminal to determine the broadcast status of the serving cell's SIB1 based on at least one of the MIB and PBCH payloads.

[0229] Optionally, the method further includes:

[0230] In the event of changes to other system information OSI request configuration information, the network-side device sends a first indication message to the terminal;

[0231] The first indication information includes one of the following:

[0232] System information change notification; a notification message specifically used to indicate changes to OSI request configuration information.

[0233] It is understandable that the relevant information regarding the OSI request for configuration information change can be found in the previous text and will not be repeated here.

[0234] Optionally, the OSI request configuration information includes at least one of the following:

[0235] Information indicating the OSI request method;

[0236] Information indicating the requested resource in OSI.

[0237] Optionally, the method further includes:

[0238] In the event of a change in the broadcast status of SIB1 in the serving cell, the network-side device does not notify the terminal.

[0239] If the terminal needs to obtain the required OSI based on the broadcast state of the serving cell's SIB1 through the first or second method, but the network-side equipment does not notify the terminal if the broadcast state of the serving cell's SIB1 changes, then the terminal can obtain at least one of the serving cell's MIB and PBCH loads, and thus determine the broadcast state of the serving cell's SIB1 based on at least one of the MIB and PBCH loads.

[0240] To facilitate understanding of the information acquisition and information indication methods described above, the following two specific implementation methods are introduced.

[0241] Implementation method 1: When the terminal is in RRC connection state and the terminal meets the first condition, the terminal obtains the required OSI through method-1 or method-2 according to the broadcast state of SIB1 of the serving cell;

[0242] Among them, Method-1 is: the terminal first obtains the SIB1 of the serving cell, and then obtains the OSI required by the terminal based on the obtained SIB1; Method-2 is: the terminal directly sends a DedicatedSIBRequest to the network-side device to request the OSI required by the terminal.

[0243] In addition, the first condition includes:

[0244] The terminal's active BWP is configured with CSS for OSI;

[0245] The terminal does not have the required valid OSI version saved.

[0246] The terminal determines, based on the si-SchedulingInfo stored in its SIB1, that the SI message of the terminal's serving cell includes at least one OSI required by the terminal.

[0247] 1.1 Optionally, the terminal obtains the required OSI according to the broadcast state of SIB1 of the serving cell via mode-1 or mode-2, including:

[0248] If the broadcast state of SIB1 of the serving cell is non-broadcast, the terminal obtains the required OSI through method-2;

[0249] If the broadcast status of SIB1 of the serving cell is broadcast, the terminal obtains the OSI required by the terminal through mode-1.

[0250] 1.2 Optionally, the first condition further includes: the terminal's broadcast status for its required OSI is unknown.

[0251] Specifically, if the terminal has not read SIB1 during the current system information modification period, or if the terminal has obtained SIB1 during the current system information modification period and the broadcast status of OSI in SIB1 is set to non-broadcast, the broadcast status of the OSI required by the terminal is unknown.

[0252] 1.3 Optionally, the terminal obtains the broadcast status of SIB1 of the serving cell based on at least one of the MIB and PBCH payload of the serving cell.

[0253] For example, the broadcast status of SIB1 can be determined by the reserved bits in the MIB; for instance, a reserved bit value of 0 in the MIB indicates that SIB1 is broadcasting, and a value of 1 indicates that SIB1 is not broadcasting.

[0254] or,

[0255] For example, the broadcast status of SIB1 of the serving cell can be determined based on the value of Kssb determined by the MIB and PBCH payload. For instance, when the value of Kssb is 30, it is determined that SIB1 of the serving cell is broadcasting (furthermore, the terminal can receive the broadcast SIB1 according to pdcch-ConfigSIB1 in the MIB); when the value of Kssb is some value between 24 and 29 or is 31, it is determined that SIB1 of the serving cell is not broadcasting.

[0256] 1.4 Optionally, when the terminal satisfies the first condition above and the third condition below, the broadcast status of the serving cell's SIB1 of the terminal is immediately determined based on at least one of the MIB and PBCH payload.

[0257] The second condition includes:

[0258] The broadcast status change of SIB1 in the serving cell does not notify the terminal;

[0259] The broadcast state change of SIB1 in the serving cell (here, the change can be from non-broadcast to broadcast, or from broadcast to non-broadcast) can occur at any MIB transmission time (i.e., it does not need to follow the system information modification cycle). Alternatively, the change of the broadcast state of SIB1 in the serving cell from non-broadcast to broadcast can occur at any MIB transmission time (i.e., it does not need to follow the system information modification cycle), and the MIB obtained by the terminal within a system information modification cycle indicates that the broadcast state of SIB1 is non-broadcast (that is, if the MIB obtained by the terminal within a system information modification cycle indicates that the broadcast state of SIB1 is broadcast, the terminal can assume that the broadcast state of SIB1 has always been broadcast within this system information modification cycle. In this case, the terminal does not need to reread the MIB).

[0260] 1.5 Optionally, if the serving cell of the terminal allows the terminal to obtain the broadcast status of SIB1 of the serving cell based on at least one of the MIB and PBCH payloads of the serving cell, the terminal obtains the broadcast status of SIB1 of the serving cell based on at least one of the MIB and PBCH payloads of the serving cell.

[0261] For example, the terminal can receive third indication information sent by the network-side device. This third indication information instructs the serving cell to allow the terminal to determine the broadcast state of the serving cell's SIB1 based on at least one of the MIB and PBCH payloads. Specifically, the network-side device can instruct the connected terminal to allow the serving cell to determine the broadcast state of the serving cell's SIB1 based on at least one of the MIB and PBCH payloads via dedicated signaling (such as an RRC reconfiguration message), SIB1, or WUS configuration.

[0262] Alternatively, for example, if the terminal has already obtained the WUS configuration of its serving cell, then the terminal can determine, based on the obtained WUS configuration, whether the serving cell allows the terminal to determine the broadcast state of the serving cell's SIB1 according to at least one of the MIB and PBCH payloads. In other words, if the terminal's serving cell has a WUS configuration, then by default, that cell supports determining the broadcast state of the serving cell's SIB1 according to at least one of the MIB and PBCH payloads.

[0263] 1.6 Optionally, the terminal obtains the required OSI through method-2, including:

[0264] If the second condition is met, the terminal sends a DedicatedSIBRequest to request the OS required by the terminal.

[0265] The second condition includes:

[0266] The network-side device allows terminals in RRC connected state to send OSI requests (i.e., are configured with onDemandSIB-Request);

[0267] The OSI-requested disable timer (T350) is not running.

[0268] Additionally, the T350 timer can be started after the terminal sends the DedicatedSIBRequest.

[0269] Optionally, each OSI can be configured with a T350. In this case, for example, when a terminal requests OSI 12, the corresponding OSI 12 disable timer is started. During the operation of the disable timer, the terminal is prohibited from requesting OSI 12 again.

[0270] Optionally, multiple OSIs can be configured with a single T350. In this case, if the same OSI is requested, the timer must be allowed to expire; if the same OSI is not requested, the timer does not need to expire. For example, when a terminal requests OSI 12, the T350 is activated. During the timer's execution, the terminal is prohibited from requesting OSI 12 again, but it can request OSI 13.

[0271] As can be seen from the above, for a terminal in the RRC connected state and whose active BWP is configured for the common search space of OSI, when the terminal needs to obtain the required OSI, if the current cell's SIB1 is in the on-demand request state (i.e., the broadcast state of SIB1 is non-broadcast), the terminal can directly send a DedicatedSIBRequest to request the required OSI, skipping the request for SIB1; and after the request, the terminal can receive the required OSI through broadcast, thereby reducing the latency and power consumption of the terminal in obtaining the OSI, and also benefiting network energy saving.

[0272] Implementation Method 2: When the terminal is in RRC IDLE or INACTIVE state and the terminal meets the first condition, the terminal obtains the required OSI through Method-3 or Method-4 based on at least one of the broadcast state of the serving cell's SIB1 and the validity of the OSI request configuration information;

[0273] Among them, Method-3 is: the terminal first obtains the SIB1 of the serving cell, and then obtains the OSI required by the terminal based on the obtained SIB1; Method-4 is: the terminal directly requests the OSI required by the terminal from the network side equipment.

[0274] In addition, the first condition includes:

[0275] The terminal does not have the required valid OSI version saved.

[0276] The terminal determines, based on the si-SchedulingInfo stored in its SIB1, that the SI message of the terminal's serving cell includes at least one OSI required by the terminal.

[0277] In addition, the OSI request configuration information includes at least one of the following: information indicating the OSI request method and information indicating the OSI request resource.

[0278] Optionally, the terminal obtains the required OSI through method-3 or method-4 based on at least one of the broadcast state of the serving cell's SIB1 and the validity of the OSI request configuration information, including:

[0279] If the broadcast status of SIB1 of the serving cell is non-broadcast and the OSI request configuration information saved by the terminal is valid, the terminal obtains the required OSI through method -4.

[0280] If the broadcast status of SIB1 of the serving cell is broadcast, or the OSI request configuration information stored by the terminal is invalid, the terminal obtains the required OSI through method -3.

[0281] Optionally, the method by which the terminal determines the validity of the saved OSI request method is as follows:

[0282] The protocol stipulates that the terminal needs to be notified if the OSI request method changes. The terminal can then determine whether the OSI request method it has saved is valid based on whether it has received the notification of the OSI request method change.

[0283] Optionally, the notification of changes to the OSI request method can be made using either notification method-1 or notification method-2:

[0284] Notification Method 1: Use a separate bit in the short message to indicate a change in the OSI request method;

[0285] Notification Method 2: Indicate the change of OSI request method through existing system information change notifications.

[0286] For notification method-1 above, for example, if the OSI request method configured in the terminal's SIB1 is msg3based, and the terminal has not received a notification of a change in the OSI request method, then the terminal determines that the msg 3based OSI request method is valid. Alternatively, for example, if the OSI request method configured in the terminal's SIB1 is msg 1based, and the terminal receives a notification of a change in the OSI request method (i.e., changed to msg 3based), then the terminal determines that the msg 3based OSI request method is valid.

[0287] Regarding the above notification method-2, when the OSI request method changes, the network-side device can notify the terminal of the system information change. In this case, the terminal learns that the system information has changed, but is unsure which parts of the system information have changed. After receiving the system information change notification, the terminal can obtain the new SIB1, and then obtain the changed OSI request method from the new SIB1 and save the changed OSI request method. In this way, the terminal always saves a valid OSI request method.

[0288] Alternatively, for notification method-2 above, when the OSI request method changes, the network-side device can notify the terminal system of the information change. In this case, the terminal can obtain the new SIB1 or not. If the terminal obtains the new SIB1, then the terminal has saved a valid OSI request method; if the terminal does not obtain the new SIB1, then the OSI request method saved by the terminal can be considered invalid.

[0289] It should be noted that the OSI request method can be changed between msg 3based and msg 1based.

[0290] 2.3 Optionally, the terminal determines the validity of the stored OSI requested resources in the manner described in Example 3 or Example 4:

[0291] Example 3: The protocol stipulates that the terminal system must be notified of the change in OSI requested resources. Specifically, when the terminal receives a short message indicating a system message change, the terminal immediately acquires the new SIB1, thus ensuring that the terminal always retains a valid OSI requested resource.

[0292] Example 4: The protocol stipulates that in the event of a change in the requested OSI resource, the terminal must be notified, and this indication must be sent via a separate bit in the short message. Specifically, when the terminal receives a short message indicating a change in the requested OSI resource, it can determine that the requested OSI resource in the stored SIB1 is invalid; if no change notification is received, the terminal considers the requested OSI resource in the stored SIB1 to be valid. Optionally, when the terminal receives a short message indicating a change in the requested OSI resource, it may choose to obtain the new SIB1 or not.

[0293] It should be noted that 1.2 to 1.5 in the above-described implementation method one also apply to implementation method two, and will not be repeated here.

[0294] It should also be noted that in existing related technologies, for terminals in RRC connected state with their active BWP configured for the OSI common search space, when the terminal needs to obtain the required OSI, if the terminal does not know the current OSI broadcast state, then the terminal needs to obtain SIB1 first. However, in the network energy-saving OD-SIB1 scenario, SIB1 is sent on demand (i.e., non-broadcast), so there is a high probability that the OSI is also sent on demand. Thus, the SIB1 obtained by the terminal may indicate that the OSI is non-broadcast; and if the SIB1 indicates that the OSI is non-broadcast, it can be changed to broadcast in the current modification cycle, and the OSI broadcast state change is not notified to the terminal, thus requiring the terminal to obtain SIB1 again, thereby increasing the latency and power consumption of the terminal requesting the OSI. This problem also exists for terminals in RRC IDLE / INACTIVE state.

[0295] The above-described embodiments one and two of this application can select an appropriate method for obtaining OSI based on the broadcast state of SIB1, thereby reducing the latency and power consumption of terminal requesting OSI, and also facilitating network energy saving.

[0296] The information acquisition method provided in this application can be executed by an information acquisition device. This application uses an information acquisition device executing the information acquisition method as an example to illustrate the information acquisition device provided in this application.

[0297] See Figure 4 The embodiments of this application provide an information acquisition device applied to a terminal. The information acquisition device 40 may include the following modules:

[0298] The acquisition module 401 is used to acquire other system information (OSI) required by the terminal according to the broadcast status of the system information block 1SIB1 of the serving cell of the terminal through a first method or a second method.

[0299] The broadcast status of SIB1 is used to indicate whether SIB1 is being broadcast;

[0300] The first method is to obtain the SIB1 of the serving cell and obtain the OSI required by the terminal based on the obtained SIB1; the second method is to request the OSI required by the terminal from the network-side device.

[0301] Optionally, the acquisition module 401 is specifically used for:

[0302] If the terminal meets the first condition, the OSI required by the terminal is obtained through the first method or the second method according to the broadcast state of SIB1 of the serving cell;

[0303] The first condition includes at least one of the following:

[0304] The active bandwidth portion (BWP) of the terminal is configured for the OSI common search space.

[0305] The terminal does not have a valid OSI version required by the terminal;

[0306] The terminal determines, based on the first information, that the system information (SI) message of the serving cell includes at least one OSI required by the terminal, wherein the first information includes SI scheduling information stored in SIB1 by the terminal.

[0307] The broadcast status of the OSI required by the terminal is unknown.

[0308] Optionally, the acquisition module 401 is specifically used for:

[0309] When the terminal is in the Radio Resource Control (RRC) connected state and the broadcast status of SIB1 of the serving cell indicates that SIB1 is not being broadcast, the OSI required by the terminal is obtained through the second method.

[0310] or,

[0311] When the terminal is in RRC connection state and the broadcast status of SIB1 of the serving cell indicates that SIB1 is being broadcast, the OSI required by the terminal is obtained through the first method.

[0312] Optionally, the acquisition module 401 acquires the OSI required by the terminal through the second method, including:

[0313] If the second condition is met, the terminal requests the OSI required by the network-side device;

[0314] The second condition includes at least one of the following:

[0315] The network-side device allows terminals in RRC connection state to request the OSI required by the terminal from the network-side device;

[0316] The OSI-requested timer is not running.

[0317] Optionally, the device further includes a first processing module, configured to start an OSI request disable timer after the acquisition module 401 requests the OSI required by the terminal from the network-side device.

[0318] Optionally, the acquisition module 401 acquires other system information (OSI) required by the terminal according to the broadcast status of the system information block 1SIB1 of the serving cell of the terminal, through a first method or a second method, including:

[0319] When the terminal is in RRC idle state or RRC inactive state, the OSI required by the terminal is obtained through the first method or the second method according to the broadcast state of SIB1 of the serving cell and the validity of the OSI request configuration information.

[0320] Optionally, the acquisition module 401 acquires the OSI required by the terminal through the first method or the second method based on the broadcast status of the SIB1 of the serving cell and the validity of the OSI request configuration information, including:

[0321] If the broadcast status of SIB1 in the serving cell indicates that SIB1 is not broadcast, and the OSI request configuration information is valid, the OSI required by the terminal is obtained through the second method.

[0322] or,

[0323] When the broadcast status of SIB1 in the serving cell indicates that SIB1 is being broadcast, the OSI required by the terminal is obtained through the first method;

[0324] or,

[0325] If the OSI request configuration information is invalid, the OSI required by the terminal is obtained through the first method.

[0326] Optionally, the apparatus further includes a determining module, configured to: determine the validity of the saved OSI request configuration information based on whether a first indication information sent by the network-side device is received;

[0327] The first indication information includes one of the following:

[0328] System information change notification; a notification message specifically used to indicate changes to OSI request configuration information.

[0329] Optionally, the OSI request configuration information includes at least one of the following:

[0330] Information indicating the OSI request method;

[0331] Information indicating the requested resource in OSI.

[0332] Optionally, the device further includes:

[0333] The determining module is used to determine the broadcast status of SIB1 of the serving cell based on the second information;

[0334] The second information includes at least one of the serving cell's Master Information Block (MIB) and the load of the Physical Broadcast Channel (PBCH).

[0335] Optionally, the determining module determines the broadcast status of SIB1 of the serving cell based on the second information, including:

[0336] The broadcast status of SIB1 of the serving cell is determined based on the second indication information in the MIB of the serving cell, wherein the second indication information is used to indicate whether SIB1 is being broadcast;

[0337] or,

[0338] The value of Kssb is determined based on the load of the MIB and PBCH of the serving cell, and the broadcast status of SIB1 of the serving cell is determined based on the value of Kssb.

[0339] Wherein, Kssb represents the offset between the starting position of the first resource block where the common resource block and the synchronization signal block overlap and the starting position of the synchronization signal block.

[0340] Optionally, the acquisition module 401 is further configured to:

[0341] If the first and third conditions are met, the second information is obtained;

[0342] The first condition includes at least one of the following:

[0343] The terminal's activated BWP is configured with a common search space for OSI.

[0344] The terminal does not have a valid OSI version required by the terminal;

[0345] The terminal determines, based on the first information, that the SI message of the serving cell includes at least one OSI required by the terminal, and the first information includes SI scheduling information stored in SIB1 by the terminal.

[0346] The broadcast status of the OSI required by the terminal is unknown;

[0347] The third condition includes at least one of the following:

[0348] The terminal is not notified of any broadcast status change in SIB1 of the serving cell.

[0349] The broadcast status change of SIB1 of the serving cell does not need to follow the system information modification cycle, or the behavior of changing the broadcast status of SIB1 of the serving cell from non-broadcast to broadcast does not need to follow the system information modification cycle and the MIB indication obtained by the terminal within a system information modification cycle indicates that SIB1 has not been broadcast.

[0350] Optionally, the apparatus further includes: a determining module, configured to:

[0351] The serving cell is determined to allow the terminal to determine the broadcast state of SIB1 of the serving cell based on the second information under at least one of the following conditions:

[0352] The terminal receives a third indication message from the network-side device, wherein the third indication message is used to indicate that the terminal is allowed to determine the broadcast status of SIB1 of the serving cell based on the second information;

[0353] The wake-up signal configuration of the serving cell has been obtained.

[0354] The information acquisition device in this application embodiment can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal; for example, the terminal can include, but is not limited to, the types of terminal 11 listed above, and this application embodiment does not specifically limit it.

[0355] The information acquisition 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.

[0356] The information indication method provided in this application can be executed by an information indication device. This application uses an information indication device executing the information indication method as an example to illustrate the information indication device provided in this application.

[0357] See Figure 5 The embodiments of this application provide an information indication device applied to a network-side device. The information indication device 50 may include the following modules:

[0358] Indication module 501 is used to indicate the broadcast status of system information block 1SIB1 of the serving cell of the terminal through second information;

[0359] The second information includes at least one of the main information block (MIB) of the serving cell and the load of the physical broadcast channel (PBCH), and the broadcast status of SIB1 is used to indicate whether SIB1 is being broadcast.

[0360] Optionally, the second indication information in the MIB of the serving cell is used to indicate whether SIB1 is being broadcast;

[0361] or,

[0362] The Kssb value corresponding to the load of the MIB and PBCH of the serving cell is used to indicate the broadcast status of SIB1 of the serving cell.

[0363] Wherein, Kssb represents the offset between the starting position of the first resource block where the common resource block CRB overlaps with the synchronization signal block and the starting position of the synchronization signal block.

[0364] Optionally, the device further includes:

[0365] The sending module is used to send third indication information to the terminal;

[0366] The third indication information is used to instruct the serving cell of the terminal to allow the terminal to determine the broadcast status of SIB1 of the serving cell based on the second information.

[0367] Optionally, the device further includes:

[0368] The sending module is used to send first indication information to the terminal when other system information OSI request configuration information changes;

[0369] The first indication information includes one of the following:

[0370] System information change notification; a notification message specifically used to indicate changes to OSI request configuration information.

[0371] Optionally, the OSI request configuration information includes at least one of the following:

[0372] Information indicating the OSI request method;

[0373] Information indicating the requested resource in OSI.

[0374] Optionally, the device further includes a second processing module for: not notifying the terminal in the event of a change in the broadcast status of SIB1 of the serving cell.

[0375] The information indicating device in this application embodiment can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a network-side device; for example, the terminal can be of the type of network-side device 12 listed above, and this application embodiment does not specifically limit it.

[0376] The information indicating device provided in this application embodiment can realize Figure 3 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0377] like Figure 6 As shown in the illustration, this application also provides a communication device 600, including a processor 601 and a memory 602. The memory 602 stores programs or instructions that can run on the processor 601. For example, when the communication device 600 is a terminal, the program or instructions executed by the processor 601 implement the various steps of the above-described information acquisition method embodiment and achieve the same technical effect. When the communication device 600 is a network-side device, the program or instructions executed by the processor 601 implement the various steps of the above-described information indication method embodiment and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0378] This application embodiment also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement, for example... Figure 2 The steps in the method embodiment shown are illustrated. This terminal embodiment corresponds to the above-described terminal-side method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and achieve the same technical effect. Specifically, Figure 7 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0379] The terminal 700 includes, but is not limited to, at least some of the following components: radio frequency unit 701, network module 702, audio output unit 703, input unit 704, sensor 705, display unit 706, user input unit 707, interface unit 708, memory 709, and processor 710.

[0380] Those skilled in the art will understand that the terminal 700 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 710 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 7 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.

[0381] It should be understood that, in this embodiment, the input unit 704 may include a graphics processing unit (GPU) 7041 and a microphone 7042. The GPU 7041 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 706 may include a display panel 7061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 707 includes at least one of a touch panel 7071 and other input devices 7072. The touch panel 7071 is also called a touch screen. The touch panel 7071 may include a touch detection device and a touch controller. Other input devices 7072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick, which will not be described in detail here.

[0382] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 701 can transmit it to the processor 710 for processing; in addition, the radio frequency unit 701 can send uplink data to the network-side device. Typically, the radio frequency unit 701 includes, but is not limited to, an antenna, amplifier, transceiver, coupler, low-noise amplifier, duplexer, etc.

[0383] The memory 709 can be used to store software programs or instructions, as well as various data. The memory 709 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first 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 709 may include volatile memory or non-volatile memory. The non-volatile memory 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. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 709 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

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

[0385] The processor 710 is configured to obtain other system information (OSI) required by the terminal through a first method or a second method, based on the broadcast status of the system information block 1SIB1 of the serving cell of the terminal.

[0386] The broadcast status of SIB1 is used to indicate whether SIB1 is being broadcast;

[0387] The first method is to obtain the SIB1 of the serving cell and obtain the OSI required by the terminal based on the obtained SIB1; the second method is to request the OSI required by the terminal from the network-side device.

[0388] Optionally, the processor 710 is specifically used for:

[0389] If the terminal meets the first condition, the OSI required by the terminal is obtained through the first method or the second method according to the broadcast state of SIB1 of the serving cell;

[0390] The first condition includes at least one of the following:

[0391] The active bandwidth portion (BWP) of the terminal is configured for the OSI common search space.

[0392] The terminal does not have a valid OSI version required by the terminal;

[0393] The terminal determines, based on the first information, that the system information (SI) message of the serving cell includes at least one OSI required by the terminal, wherein the first information includes SI scheduling information stored in SIB1 by the terminal.

[0394] The broadcast status of the OSI required by the terminal is unknown.

[0395] Optionally, the processor 710 is specifically used for:

[0396] When the terminal is in the Radio Resource Control (RRC) connected state and the broadcast status of SIB1 of the serving cell indicates that SIB1 is not being broadcast, the OSI required by the terminal is obtained through the second method.

[0397] or,

[0398] When the terminal is in RRC connection state and the broadcast status of SIB1 of the serving cell indicates that SIB1 is being broadcast, the OSI required by the terminal is obtained through the first method.

[0399] Optionally, the processor 710 obtains the OSI required by the terminal through the second method, including:

[0400] If the second condition is met, the terminal requests the OSI required by the network-side device;

[0401] The second condition includes at least one of the following:

[0402] The network-side device allows terminals in RRC connection state to request the OSI required by the terminal from the network-side device;

[0403] The OSI-requested timer is not running.

[0404] Optionally, the processor 710 is further configured to: after requesting the OSI required by the terminal from the network-side device, start a timer to disable the OSI request.

[0405] Optionally, the processor 710 obtains other system information (OSI) required by the terminal according to the broadcast status of the system information block 1SIB1 of the serving cell of the terminal, through a first method or a second method, including:

[0406] When the terminal is in RRC idle state or RRC inactive state, the OSI required by the terminal is obtained through the first method or the second method according to the broadcast state of SIB1 of the serving cell and the validity of the OSI request configuration information.

[0407] Optionally, the processor 710 obtains the OSI required by the terminal through the first method or the second method based on the broadcast status of the serving cell's SIB1 and the validity of the OSI request configuration information, including:

[0408] If the broadcast status of SIB1 in the serving cell indicates that SIB1 is not broadcast, and the OSI request configuration information is valid, the OSI required by the terminal is obtained through the second method.

[0409] or,

[0410] When the broadcast status of SIB1 in the serving cell indicates that SIB1 is being broadcast, the OSI required by the terminal is obtained through the first method;

[0411] or,

[0412] If the OSI request configuration information is invalid, the OSI required by the terminal is obtained through the first method.

[0413] Optionally, the processor 710 is further configured to: determine the validity of the saved OSI request configuration information based on whether it receives the first indication information sent by the network-side device;

[0414] The first indication information includes one of the following:

[0415] System information change notification; a notification message specifically used to indicate changes to OSI request configuration information.

[0416] Optionally, the OSI request configuration information includes at least one of the following:

[0417] Information indicating the OSI request method;

[0418] Information indicating the requested resource in OSI.

[0419] Optionally, the processor 710 is further configured to: determine the broadcast status of SIB1 of the serving cell based on the second information;

[0420] The second information includes at least one of the serving cell's Master Information Block (MIB) and the load of the Physical Broadcast Channel (PBCH).

[0421] Optionally, the processor 710 determines the broadcast status of the serving cell's SIB1 based on the second information, including:

[0422] The broadcast status of SIB1 of the serving cell is determined based on the second indication information in the MIB of the serving cell, wherein the second indication information is used to indicate whether SIB1 is being broadcast;

[0423] or,

[0424] The value of Kssb is determined based on the load of the MIB and PBCH of the serving cell, and the broadcast status of SIB1 of the serving cell is determined based on the value of Kssb.

[0425] Wherein, Kssb represents the offset between the starting position of the first resource block where the common resource block (CRB) and the synchronization signal block overlap and the starting position of the synchronization signal block.

[0426] Optionally, the processor 710 is further configured to:

[0427] If the first and third conditions are met, the second information is obtained;

[0428] The first condition includes at least one of the following:

[0429] The terminal's activated BWP is configured with a common search space for OSI.

[0430] The terminal does not have a valid OSI version required by the terminal;

[0431] The terminal determines, based on the first information, that the SI message of the serving cell includes at least one OSI required by the terminal, and the first information includes SI scheduling information stored in SIB1 by the terminal.

[0432] The broadcast status of the OSI required by the terminal is unknown;

[0433] The third condition includes at least one of the following:

[0434] The terminal is not notified of any broadcast status change in SIB1 of the serving cell.

[0435] The broadcast status change of SIB1 of the serving cell does not need to follow the system information modification cycle, or the behavior of changing the broadcast status of SIB1 of the serving cell from non-broadcast to broadcast does not need to follow the system information modification cycle and the MIB indication obtained by the terminal within a system information modification cycle indicates that SIB1 has not been broadcast.

[0436] Optionally, the processor 710 is also used for:

[0437] The serving cell is determined to allow the terminal to determine the broadcast state of SIB1 of the serving cell based on the second information under at least one of the following conditions:

[0438] The terminal receives a third indication message from the network-side device, wherein the third indication message is used to indicate that the terminal is allowed to determine the broadcast status of SIB1 of the serving cell based on the second information;

[0439] The wake-up signal configuration of the serving cell has been obtained.

[0440] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effect. To avoid repetition, it will not be described again here.

[0441] This application embodiment also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement, for example... Figure 3 The information indicated indicates the steps of the method embodiment. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0442] Specifically, embodiments of this application also provide a network-side device. For example... Figure 8 As shown, the network-side device 800 includes: an antenna 81, a radio frequency (RF) device 82, a baseband device 83, a processor 84, and a memory 85. The antenna 81 is connected to the RF device 82. In the uplink direction, the RF device 82 receives information through the antenna 81 and transmits the received information to the baseband device 83 for processing. In the downlink direction, the baseband device 83 processes the information to be transmitted and sends it to the RF device 82. The RF device 82 processes the received information and transmits it through the antenna 81.

[0443] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 83, which includes a baseband processor.

[0444] Baseband device 83 may include, for example, at least one baseband board on which multiple chips are disposed, such as... Figure 8 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 85 via a bus interface to call the program in the memory 85 and execute the network device operation shown in the above method embodiment.

[0445] The network-side device may also include a network interface 86, such as a Common Public Radio Interface (CPRI).

[0446] Specifically, the network-side device 800 of this embodiment further includes: instructions or programs stored in a memory 85 and executable on a processor 84, wherein the processor 84 calls the instructions or programs in the memory 85 to execute. Figure 5 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0447] 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 information acquisition method or information indication method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0448] 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. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0449] 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 information acquisition method or information indication method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

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

[0451] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described information acquisition method or information indication method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0452] This application also provides a wireless communication system, including: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the information acquisition method described above, and the network-side device can be used to perform the steps of the information indication method described above.

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

[0454] From 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 computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0455] 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 implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. An information acquisition method, characterized in that, The method includes: The terminal obtains other system information (OSI) required by the terminal through a first method or a second method, based on the broadcast status of the system information block 1SIB1 of the serving cell of the terminal. The broadcast status of SIB1 is used to indicate whether SIB1 is being broadcast; The first method is to obtain the SIB1 of the serving cell and obtain the OSI required by the terminal based on the obtained SIB1; the second method is to request the OSI required by the terminal from the network-side device.

2. The method according to claim 1, characterized in that, The terminal obtains other system information (OSI) required by the terminal through a first method or a second method, based on the broadcast status of the system information block 1SIB1 of the serving cell of the terminal, including: If the terminal meets the first condition, the terminal obtains the required OSI according to the broadcast state of SIB1 of the serving cell through the first method or the second method. The first condition includes at least one of the following: The active bandwidth portion (BWP) of the terminal is configured for the OSI common search space. The terminal does not have a valid OSI version required by the terminal; The terminal determines, based on the first information, that the system information (SI) message of the serving cell includes at least one OSI required by the terminal, wherein the first information includes SI scheduling information stored in SIB1 by the terminal. The broadcast status of the OSI required by the terminal is unknown.

3. The method according to claim 1 or 2, characterized in that, The terminal obtains other system information (OSI) required by the terminal through a first method or a second method, based on the broadcast status of the system information block 1SIB1 of the serving cell of the terminal, including: When the terminal is in the Radio Resource Control (RRC) connected state and the broadcast status of SIB1 of the serving cell indicates that SIB1 is not being broadcast, the terminal obtains the OSI required by the terminal through the second method. or, When the terminal is in RRC connected state and the broadcast status of SIB1 of the serving cell indicates that SIB1 is being broadcast, the terminal obtains the OSI required by the terminal through the first method.

4. The method according to claim 3, characterized in that, The terminal obtains the OSI required by the second method, including: If the second condition is met, the terminal requests the OSI required by the network-side device; The second condition includes at least one of the following: The network-side device allows terminals in RRC connection state to request the OSI required by the terminal from the network-side device; The OSI-requested timer is not running.

5. The method according to claim 4, characterized in that, The method further includes: After the terminal requests the OSI required by the network-side device, the terminal starts a timer to disable the OSI request.

6. The method according to claim 1 or 2, characterized in that, The terminal obtains other system information (OSI) required by the terminal through a first method or a second method, based on the broadcast status of the system information block 1SIB1 of the serving cell of the terminal, including: When the terminal is in RRC idle state or RRC inactive state, the terminal obtains the required OSI according to the broadcast state of SIB1 of the serving cell and the validity of the OSI request configuration information through the first method or the second method.

7. The method according to claim 6, characterized in that, The terminal obtains the required OSI based on the broadcast status of the serving cell's SIB1 and the validity of the OSI request configuration information, using either the first method or the second method, including: If the broadcast status of SIB1 in the serving cell indicates that SIB1 is not broadcast, and the OSI request configuration information is valid, the terminal obtains the OSI required by the terminal through the second method. or, When the broadcast status of SIB1 in the serving cell indicates that SIB1 is being broadcast, the terminal obtains the OSI required by the terminal through the first method; or, If the OSI request configuration information is invalid, the terminal obtains the required OSI through the first method.

8. The method according to claim 6 or 7, characterized in that, The method further includes: The terminal determines the validity of the saved OSI request configuration information based on whether it receives the first indication information sent by the network-side device. The first indication information includes one of the following: System information change notification; a notification message specifically used to indicate changes to OSI request configuration information.

9. The method according to any one of claims 6 to 8, characterized in that, The OSI request configuration information includes at least one of the following: Information indicating the OSI request method; Information indicating the requested resource in OSI.

10. The method according to any one of claims 1 to 9, characterized in that, The method further includes: The terminal determines the broadcast status of SIB1 of the serving cell based on the second information; The second information includes at least one of the serving cell's Master Information Block (MIB) and the load of the Physical Broadcast Channel (PBCH).

11. The method according to claim 10, characterized in that, The terminal determines the broadcast status of SIB1 of the serving cell based on the second information, including: The terminal determines the broadcast status of SIB1 of the serving cell based on the second indication information in the MIB of the serving cell, wherein the second indication information is used to indicate whether SIB1 is being broadcast; or, The terminal determines the value of Kssb based on the load of the MIB and PBCH of the serving cell, and determines the broadcast status of SIB1 of the serving cell based on the value of Kssb. Wherein, Kssb represents the offset between the starting position of the first resource block in the common resource block (CRB) that overlaps with the synchronization signal block and the starting position of the synchronization signal block.

12. The method according to claim 10 or 11, characterized in that, The method further includes: If the first and third conditions are met, the terminal acquires the second information; The first condition includes at least one of the following: The terminal's activated BWP is configured with a common search space for OSI. The terminal does not have a valid OSI version required by the terminal; The terminal determines, based on the first information, that the SI message of the serving cell includes at least one OSI required by the terminal, and the first information includes SI scheduling information stored in SIB1 by the terminal. The broadcast status of the OSI required by the terminal is unknown; The third condition includes at least one of the following: The terminal is not notified of any broadcast status change in SIB1 of the serving cell. The broadcast status change of SIB1 of the serving cell does not need to follow the system information modification cycle, or the behavior of changing the broadcast status of SIB1 of the serving cell from non-broadcast to broadcast does not need to follow the system information modification cycle and the MIB indication obtained by the terminal within a system information modification cycle indicates that SIB1 has not been broadcast.

13. The method according to any one of claims 10 to 12, characterized in that, The method further includes: The terminal determines that the serving cell allows the terminal to determine the broadcast state of the serving cell's SIB1 based on the second information under at least one of the following conditions: The terminal receives third indication information from the network-side device, wherein the third indication information is used to indicate that the terminal is allowed to determine the broadcast status of SIB1 of the serving cell based on the second information; The terminal has obtained the wake-up signal configuration of the serving cell.

14. An information indication method, characterized in that, The method includes: The network-side device uses the second information to indicate the broadcast status of the system information block 1SIB1 of the serving cell of the terminal; The second information includes at least one of the serving cell's Master Information Block (MIB) and the load of the Physical Broadcast Channel (PBCH); the broadcast status of SIB1 is used to indicate whether SIB1 is being broadcast.

15. The method according to claim 14, characterized in that, The second indication information in the MIB of the serving cell is used to indicate whether SIB1 is being broadcast; or, The Kssb value corresponding to the load of the MIB and PBCH of the serving cell is used to indicate the broadcast status of SIB1 of the serving cell. Wherein, Kssb represents the offset between the starting position of the first resource block in the common resource block (CRB) that overlaps with the synchronization signal block and the starting position of the synchronization signal block.

16. The method according to claim 14 or 15, characterized in that, The method further includes: The network-side device sends a third instruction message to the terminal; The third indication information is used to instruct the serving cell of the terminal to allow the terminal to determine the broadcast status of SIB1 of the serving cell based on the second information.

17. The method according to any one of claims 14 to 16, characterized in that, The method further includes: In the event of changes to other system information OSI request configuration information, the network-side device sends a first indication message to the terminal; The first indication information includes one of the following: System information change notification; a notification message specifically used to indicate changes to OSI request configuration information.

18. The method according to claim 17, characterized in that, The OSI request configuration information includes at least one of the following: Information indicating the OSI request method; Information indicating the requested resource in OSI.

19. The method according to any one of claims 14 to 18, characterized in that, The method further includes: In the event of a change in the broadcast status of SIB1 in the serving cell, the network-side device does not notify the terminal.

20. An information acquisition device, characterized in that, Applied to a terminal, the device includes: The acquisition module is used to acquire other system information (OSI) required by the terminal according to the broadcast status of the system information block 1SIB1 of the serving cell of the terminal, through a first method or a second method. The broadcast status of SIB1 is used to indicate whether SIB1 is being broadcast; The first method is to obtain the SIB1 of the serving cell and obtain the OSI required by the terminal based on the obtained SIB1; the second method is to request the OSI required by the terminal from the network-side device.

21. The apparatus according to claim 20, characterized in that, The acquisition module is specifically used for: If the terminal meets the first condition, the OSI required by the terminal is obtained through the first method or the second method according to the broadcast state of SIB1 of the serving cell; The first condition includes at least one of the following: The active bandwidth portion (BWP) of the terminal is configured for the OSI common search space. The terminal does not have a valid OSI version required by the terminal; The terminal determines, based on the first information, that the system information (SI) message of the serving cell includes at least one OSI required by the terminal, wherein the first information includes SI scheduling information stored in SIB1 by the terminal. The broadcast status of the OSI required by the terminal is unknown.

22. The apparatus according to claim 20 or 21, characterized in that, The acquisition module is specifically used for: When the terminal is in the Radio Resource Control (RRC) connected state and the broadcast status of SIB1 of the serving cell indicates that SIB1 is not being broadcast, the OSI required by the terminal is obtained through the second method. or, When the terminal is in RRC connection state and the broadcast status of SIB1 of the serving cell indicates that SIB1 is being broadcast, the OSI required by the terminal is obtained through the first method.

23. The apparatus according to claim 22, characterized in that, The acquisition module acquires the OSI required by the terminal through the second method, including: If the second condition is met, the terminal requests the OSI required by the network-side device; The second condition includes at least one of the following: The network-side device allows terminals in RRC connection state to request the OSI required by the terminal from the network-side device; The OSI-requested timer is not running.

24. The apparatus according to claim 20 or 21, characterized in that, The acquisition module obtains other system information (OSI) required by the terminal according to the broadcast status of the system information block 1SIB1 of the serving cell of the terminal, through a first method or a second method, including: When the terminal is in RRC idle state or RRC inactive state, the OSI required by the terminal is obtained through the first method or the second method according to the broadcast state of SIB1 of the serving cell and the validity of the OSI request configuration information.

25. The apparatus according to claim 24, characterized in that, The acquisition module obtains the OSI required by the terminal through the first method or the second method based on the broadcast status of the serving cell's SIB1 and the validity of the OSI request configuration information, including: If the broadcast status of SIB1 in the serving cell indicates that SIB1 is not broadcast, and the OSI request configuration information is valid, the OSI required by the terminal is obtained through the second method. or, When the broadcast status of SIB1 in the serving cell indicates that SIB1 is being broadcast, the OSI required by the terminal is obtained through the first method; or, If the OSI request configuration information is invalid, the OSI required by the terminal is obtained through the first method.

26. The apparatus according to claim 24 or 25, characterized in that, The device further includes a determining module, configured to: determine the validity of the saved OSI request configuration information based on whether the first indication information sent by the network-side device is received; The first indication information includes one of the following: System information change notification; a notification message specifically used to indicate changes to OSI request configuration information.

27. The apparatus according to any one of claims 20 to 26, characterized in that, The device further includes: The determining module is used to determine the broadcast status of SIB1 of the serving cell based on the second information; The second information includes at least one of the serving cell's Master Information Block (MIB) and the load of the Physical Broadcast Channel (PBCH).

28. The apparatus according to claim 27, characterized in that, The determining module determines the broadcast status of the serving cell's SIB1 based on the second information, including: The broadcast status of SIB1 of the serving cell is determined based on the second indication information in the MIB of the serving cell, wherein the second indication information is used to indicate whether SIB1 is being broadcast; or, The value of Kssb is determined based on the load of the MIB and PBCH of the serving cell, and the broadcast status of SIB1 of the serving cell is determined based on the value of Kssb. Wherein, Kssb represents the offset between the starting position of the first resource block in the common resource block (CRB) that overlaps with the synchronization signal block and the starting position of the synchronization signal block.

29. The apparatus according to claim 27 or 28, characterized in that, The acquisition module is also used for: If the first and third conditions are met, the second information is obtained; The first condition includes at least one of the following: The terminal's activated BWP is configured with a common search space for OSI. The terminal does not have a valid OSI version required by the terminal; The terminal determines, based on the first information, that the SI message of the serving cell includes at least one OSI required by the terminal, and the first information includes SI scheduling information stored in SIB1 by the terminal. The broadcast status of the OSI required by the terminal is unknown; The third condition includes at least one of the following: The terminal is not notified of any broadcast status change in SIB1 of the serving cell. The broadcast status change of SIB1 of the serving cell does not need to follow the system information modification cycle, or the behavior of changing the broadcast status of SIB1 of the serving cell from non-broadcast to broadcast does not need to follow the system information modification cycle and the MIB indication obtained by the terminal within a system information modification cycle indicates that SIB1 has not been broadcast.

30. The apparatus according to any one of claims 27 to 29, characterized in that, The device further includes: a determining module, configured to: The serving cell is determined to allow the terminal to determine the broadcast state of SIB1 of the serving cell based on the second information under at least one of the following conditions: The terminal receives a third indication message from the network-side device, wherein the third indication message is used to indicate that the terminal is allowed to determine the broadcast status of SIB1 of the serving cell based on the second information; The wake-up signal configuration of the serving cell has been obtained.

31. An information indicating device, characterized in that, Applied to network-side devices, the device includes: The indication module is used to indicate the broadcast status of the system information block 1SIB1 of the serving cell of the terminal through the second information; The second information includes at least one of the main information block (MIB) of the serving cell and the load of the physical broadcast channel (PBCH), and the broadcast status of SIB1 is used to indicate whether SIB1 is being broadcast.

32. The apparatus according to claim 31, characterized in that, The second indication information in the MIB of the serving cell is used to indicate whether SIB1 is being broadcast; or, The Kssb value corresponding to the load of the MIB and PBCH of the serving cell is used to indicate the broadcast status of SIB1 of the serving cell. Wherein, Kssb represents the offset between the starting position of the first resource block in the common resource block (CRB) that overlaps with the synchronization signal block and the starting position of the synchronization signal block.

33. The apparatus according to claim 31 or 32, characterized in that, The device further includes: The sending module is used to send third indication information to the terminal; The third indication information is used to instruct the serving cell of the terminal to allow the terminal to determine the broadcast status of SIB1 of the serving cell based on the second information.

34. The apparatus according to any one of claims 31 to 33, characterized in that, The device further includes: The sending module is used to send first indication information to the terminal when other system information OSI request configuration information changes; The first indication information includes one of the following: System information change notification; a notification message specifically used to indicate changes to OSI request configuration information.

35. The apparatus according to any one of claims 31 to 34, characterized in that, The device further includes a second processing module, configured to: not notify the terminal in the event of a change in the broadcast status of SIB1 of the serving cell.

36. A communication device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the information acquisition method as described in any one of claims 1 to 13, or to implement the steps of the information indication method as described in any one of claims 14 to 19.

37. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the information acquisition method as described in any one of claims 1-13, or the information indication method as described in any one of claims 14-19.

Images