SIB1 request configuration information update method and communication device

Abstract

Disclosed are an SIB1 request configuration information update method and a communication device. The method comprises: receiving a first message, wherein the first message comprises first indication information and first configuration information, the first indication information indicating the update of SIB1 request configuration information, and the first configuration information being used for configuring the SIB1 request configuration information; and on the basis of the first indication information, updating, to the first configuration information, configuration information for configuring an SIB1 request. The use of the method facilitates correctly requesting an SIB1 and increases the probability of successfully requesting the SIB1.

Description

SIB1 Request Configuration Information Update Method and Communication Equipment

[0001] This application claims priority to Chinese Patent Application No. 202411950019.2, filed on December 25, 2024, entitled "SIB1 Method and Communication Device for Requesting Configuration Information Update", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a method and communication device for requesting configuration information updates using SIB1. Background Technology

[0003] Network energy efficiency is crucial for environmental sustainability, reducing environmental impact (greenhouse gas emissions), and saving operating costs. With the widespread adoption of 5G across various industries and geographic regions, processing more advanced services and applications requires extremely high data rates. Networks are becoming denser, using more antennas, greater bandwidth, and more frequency bands, leading to increased energy consumption for current 5G communication systems and future 6G and further evolved communication systems. Therefore, new solutions are needed to improve network energy efficiency.

[0004] When network devices continuously broadcast synchronization signals, physical broadcast channel blocks (SSBs), and system message blocks (SIB1) when the terminal devices they serve have no access, measurement, or service transmission needs, it leads to energy waste. Under low to medium load conditions, transmitting SIB1 on demand can significantly improve the energy consumption of network devices.

[0005] The so-called on-demand SIB1 transmission refers to a terminal device initiating an SIB1 request when it has an SIB1 need. Upon receiving the SIB1 request, the network device sends the SIB1 itself; that is, SIB1 transmission changes from periodic broadcasting to on-demand requests. This on-demand request mode requires designing a request signal and providing the configuration information needed for request signal transmission and / or SIB1 transmission. Typically, network device A sends the SIB1 request configuration information to the terminal device, which then sends the SIB1 request to the corresponding network device B (a cell supporting on-demand SIB1 transmission) based on this configuration information. Upon receiving the SIB1 request, network device B sends the SIB1 to the terminal device. After receiving the SIB1, the terminal device completes subsequent operations based on the SIB1 message, such as random access.

[0006] However, if the terminal device does not obtain the updated SIB1 request configuration information in a timely manner when the SIB1 request configuration information is updated, the inconsistency between the SIB1 request configuration between the network device and the terminal device will prevent the on-demand transmission of SIBs from being triggered. As a result, the terminal device cannot correctly request SIB1, causing the SIB1 request to fail. Summary of the Invention

[0007] This application provides a method and communication device for requesting SIB1 configuration information updates, which is beneficial for correctly requesting SIB1 and increases the probability of successful SIB1 requests.

[0008] Firstly, some embodiments of this application provide a method for updating SIB1 request configuration information. This method can be executed by a terminal device, by a module applied to the terminal device (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the terminal device's functions. The SIB1 request configuration information update method includes: receiving a first message, the first message including first indication information and first configuration information, the first indication information indicating that SIB1 request configuration information should be updated, and the first configuration information being used to configure the SIB1 request configuration information; and updating the configuration information used to configure the SIB1 request to the first configuration information based on the first indication information.

[0009] Based on the method described in the first aspect, the SIB1 request configuration information in the terminal device is updated by the first indication information and the first configuration information in the first message, so that the SIB1 request configuration information of the network device and the terminal device are consistent, which is conducive to correctly requesting SIB1 and increasing the probability of successful SIB1 request.

[0010] In one possible embodiment, the first message is the first SIB.

[0011] In one possible embodiment, the first SIB is SIB1.

[0012] In one possible embodiment, the control information candidate resource of the first SIB is indicated by information in the SSB.

[0013] In one possible embodiment, the first SIB is an SIB other than SIB1.

[0014] In one possible embodiment, the first configuration information includes the SIB1 request configuration information of the current cell, or it includes the SIB1 request configuration information of neighboring cells.

[0015] Secondly, this application provides a method for updating SIB1 request configuration information. This method can be executed by a network device, by a module applied to the network device (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the functions of the network device. The SIB1 request configuration information update method includes: sending a first message, the first message including first indication information and first configuration information, the first indication information indicating that SIB1 request configuration information should be updated, and the first configuration information being used to configure the SIB1 request configuration information.

[0016] In one possible embodiment, the first message is the first SIB.

[0017] In one possible embodiment, the first SIB is SIB1.

[0018] In one possible embodiment, the control information candidate resource of the first SIB is indicated by information in the SSB.

[0019] In one possible embodiment, the first configuration information includes the SIB1 request configuration information of the current cell, or it includes the SIB1 request configuration information of neighboring cells.

[0020] Thirdly, some embodiments of this application provide a method for updating SIB1 request configuration information. This method can be executed by a terminal device, by a module applied to the terminal device (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the terminal device's functions. The SIB1 request configuration information update method includes: sending a second message, the second message being used to request second configuration information, the second configuration information being used to configure the SIB1 request configuration information; and receiving the second configuration information.

[0021] Based on the method described in the third aspect, the terminal device autonomously requests SIB1 configuration information from the network device, thereby ensuring that the SIB1 configuration information of the network device and the terminal device is consistent, which is conducive to correctly requesting SIB1 and increasing the probability of successful SIB1 request.

[0022] In one possible embodiment, the second message is a preamble sequence or Msg1.

[0023] In one possible embodiment, the transmission resources of the second configuration information are indicated by a third message, or the second configuration information is carried in a third message; wherein the third message is a random access response (RAR), Msg2, or a second SIB.

[0024] In one possible embodiment, the third message is a second SIB, and the transmission information of the second SIB is obtained through the SSB.

[0025] In one possible embodiment, the SSB is the first SSB opportunity after the fourth message and the SSB transmitted thereafter, or the SSB is the SSB transmitted within the first full SSB cycle after the fourth message and thereafter, or the SSB is the first SSB opportunity after the window corresponding to the fourth message and the SSB transmitted thereafter, or the SSB is the SSB transmitted within the first full SSB cycle after the window corresponding to the fourth message and thereafter.

[0026] In one possible embodiment, the fourth message is a random access response (RAR) or Msg2.

[0027] Fourthly, this application provides a SIB1 request configuration information update method. This method can be executed by a network device, by a module applied to the network device (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the network device's functions. The SIB1 request configuration information update method includes: receiving a second message, the second message being used to request second configuration information, the second configuration information being used to configure the SIB1 request configuration information; and sending the second configuration information.

[0028] In one possible embodiment, the second message is a preamble sequence or Msg1.

[0029] In one possible embodiment, the transmission resources of the second configuration information are indicated by a third message, or the second configuration information is carried in a third message; wherein the third message is a random access response (RAR), Msg2, or a second SIB.

[0030] In one possible embodiment, the third message is a second SIB, and the transmission information of the second SIB is obtained through the SSB.

[0031] In one possible embodiment, the SSB is the first SSB opportunity after the fourth message and the SSB transmitted thereafter, or the SSB is the SSB transmitted within the first full SSB cycle after the fourth message and thereafter, or the SSB is the first SSB opportunity after the window corresponding to the fourth message and the SSB transmitted thereafter, or the SSB is the SSB transmitted within the first full SSB cycle after the window corresponding to the fourth message and thereafter.

[0032] In one possible embodiment, the fourth message is a random access response (RAR) or Msg2.

[0033] Fifthly, this application provides a communication device, which may be a terminal device or a module applied to a terminal device, such as a processor, chip, or chip system, or may be a logic node, logic module, or software capable of implementing all or part of the functions of the terminal device. The communication device includes modules / units for executing any method of the first aspect / third aspect and its possible implementations.

[0034] Sixthly, this application provides a communication device, which may be a network device or a module applied to a network device, such as a processor, chip, or chip system, or may be a logical node, logical module, or software capable of implementing all or part of the functions of a network device. The communication device includes modules / units for performing any of the methods of the second / fourth aspect and their possible implementations.

[0035] In a seventh aspect, this application provides a chip including a processor and an interface, the processor and the interface being coupled; the interface is used to receive or output signals, and the processor is used to execute code instructions, causing the chip to perform the methods described in the first, second, third, or fourth aspects above.

[0036] Eighthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when invoked, cause the method described in the first aspect to be executed, or cause the method described in the second, third, or fourth aspect to be executed.

[0037] Ninthly, this application provides a computer program product comprising: computer program code, which, when executed, causes the method described in the first aspect to be executed, or causes the method described in the second, third, or fourth aspect to be executed.

[0038] In a tenth aspect, this application provides a communication system comprising a communication device (e.g., a terminal device) for performing the method described in the first aspect, a communication device (e.g., a network device) for performing the method described in the second aspect, a communication device (e.g., a terminal device) for performing the method described in the third aspect, and a communication device (e.g., a network device) for performing the method described in the fourth aspect. Attached Figure Description

[0039] Figure 1 is a schematic diagram of an on-demand SIB request scenario provided by an embodiment of this application;

[0040] Figure 2 is a schematic diagram of a system architecture provided in this application;

[0041] Figure 3 is a flowchart illustrating a SIB1 request configuration information update method provided in this application;

[0042] Figure 4A is a flowchart illustrating another SIB1 request configuration information update method provided in this application;

[0043] Figure 4B is a flowchart illustrating another SIB1 request configuration information update method provided in this application;

[0044] Figure 5 is a flowchart illustrating another SIB1 request configuration information update method provided in this application;

[0045] Figure 6 is a flowchart illustrating another SIB1 request configuration information update method provided in this application;

[0046] Figure 7 is a schematic diagram of the structure of a communication device provided in this application;

[0047] Figure 8 is a schematic diagram of another communication device provided in this application. Detailed Implementation

[0048] The specific embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0049] The terms "first" and "second," etc., used in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0050] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0051] In this application, "at least one (item)" means one or more, "more than one" means two or more, "at least two (items)" means two or three or more, and "and / or" is used to describe the relationship between related objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0052] In this application, "sending information" can be understood as one device sending information to another device, or it can also be understood as one logical module within a device sending information to another logical module. For example, "access network device sending information" can be understood as the access network device sending information to another device (such as a terminal), or it can be understood as logical module 1 in the access network device sending information to logical module 2 in the access network device.

[0053] In this application, "receiving information" can be understood as one device receiving information from another device, or it can also be understood as a logical module within a device receiving information from another logical module. For example, "access network device receiving information" can be understood as the access network device receiving information from another device (such as a terminal), or it can be understood as logical module 1 in the access network device receiving information from logical module 2 in the access network device.

[0054] In this application, phrases such as "sending information to... (e.g., a terminal)" or related illustrations in the accompanying drawings can be understood as indicating that the destination of the information is a terminal. This can include sending information directly or indirectly to a terminal. Similarly, phrases such as "receiving information from... (e.g., a terminal)," "receiving information from... (e.g., a terminal)," or "receiving information sent by (e.g., a terminal)," or related illustrations in the accompanying drawings, can be understood as indicating that the source of the information is a terminal. This can include receiving information directly or indirectly from a terminal. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly and will not be elaborated further here.

[0055] To facilitate understanding of the solutions provided in the embodiments of this application, the relevant concepts involved in the embodiments of this application are introduced below:

[0056] I. Random Access

[0057] The random access process refers to the process from when the terminal device sends a random access preamble to attempt to access the network device until a basic signaling connection is established with the network device. Terminal devices rely on the preamble to achieve random access. Depending on the preamble selection method, random access is divided into two types: contention-based random access and non-contention-based random access. The following section will further introduce terminal access using contention-based random access as an example:

[0058] Contention-based random access mainly consists of a four-step access process:

[0059] (1) The terminal device sends Msg1 to the network device. Msg1: The terminal device sends a random access preamble, or preamble, on the Physical Random Access Channel (PRACH). This preamble is a preamble that the terminal device randomly selects from the preamble pool to initiate contention-based random access on the PRACH. In this process, Msg1 can be equivalently understood as either the preamble or the PRACH signal.

[0060] (2) The network device sends Msg2 to the terminal device. Msg2: After receiving Msg1, the network device sends a Random Access Response (RAR) to the terminal device. Specifically, after sending the preamble, the terminal device will continuously listen to the Physical Downlink Control Channel (PDCCH) within the Random Access Response (RAR) window to receive the Random Access Response (RAR). If the terminal device does not receive a RAR from the network device within the RAR window, the random access process is considered to have failed. When the terminal device successfully receives a RAR (the preamble ID in the RAR is the same as the preamble ID sent by the terminal device), the terminal device can obtain uplink transmission resources through the RAR and then send uplink data.

[0061] (3) The terminal device sends Msg3 to the network device. Msg3 is transmitted on the Physical Uplink Shared Channel (PUSCH), where the PUSCH time-frequency resources used by the terminal device are indicated by the uplink transmission resources in Msg2 above. After sending Msg3, the terminal device starts a contention resolution timer to continuously listen to the PDCCH.

[0062] (4) The network device randomly selects one Msg3 from many Msg3, encapsulates and scrambles it and sends it out through PDCCH. If the terminal device successfully descrambles the PDCCH and the content therein is consistent with the UE ID it sent, then it is considered that random access has been completed.

[0063] II. Paging Process

[0064] In NR networks, paging is a crucial mechanism for notifying terminal devices of incoming data or control messages. Paging messages are typically contained within System Information Blocks (SIBs), particularly SIB1. The paging process can include the following basic steps:

[0065] Paging message issuance: When data needs to be sent to a specific terminal device, the network device generates a paging message. These paging messages are usually contained in SIB1 and sent through the downlink shared channel DL-SCH.

[0066] Paging message transmission: Paging messages are sent on DL-SCH at a fixed period, such as SIB1, which is usually sent at a period of 160ms and can be repeated variably within 160ms.

[0067] Terminal device response: When the terminal device is in the RRC_Connected state, the terminal device will listen for paging messages. If there is data for the terminal device in the paging message, the terminal device will respond and enter a specific communication process.

[0068] In addition, the paging procedure is also used to notify UEs in the RRC_IDLE and RRC_CONNECTED states that system information has changed. Paging messages can be used to notify whether system information has changed. If the UE receives a paging message notifying it of a system information change (excluding alarm information such as ETWS information), the UE needs to receive the updated system information in the next change cycle.

[0069] III. System Message SIB1

[0070] During the random access process described above, the terminal device first needs to decode the information in SIB1 to understand the cell's access conditions, system information scheduling, and other necessary configuration information. This information is crucial for the terminal device to successfully initiate the random access process. For example, the random access parameters in SIB1 (such as PRACH configuration) directly determine how the terminal device sends the preamble, thereby initiating communication with the base station.

[0071] SIB1, a mandatory system message (initially sent by network devices), is also known as Remaining Minimum System Information (RMSI). SIB1 contains cell-level configuration information, including the configuration information required for random access.

[0072] SIB1 also contains availability and scheduling information about other SIBs. Terminal devices can access other SIBs through the scheduling information in SIB1.

[0073] IV. NES Cell

[0074] The SIB1 message described above has two transmission modes: periodic transmission of SIB1 and on-demand transmission of SIB1. Ordinary NR cells typically transmit SIB1 periodically, while NES cells support both transmission modes for SIB1. That is, NES cells can transmit SIB1 periodically or switch modes to transmit SIB1 on demand.

[0075] The following section provides a further introduction to the on-demand SIB1 mode. On-demand SIB1 can be divided into four scenarios, which are described below with reference to Figure 1. Specifically:

[0076] Scenario 1: As shown in Figure 1-1, Cell B is an NES cell, and Cell A is a neighboring cell of the NES cell. Cell A can be an NES cell or not. That is, Cell B supports both SIB1 transmission modes, and Cell A can support both SIB1 transmission modes or only support one transmission mode (periodically sending SIB1).

[0077] For ease of description, we will use "cell A" to refer to Cell A in Figure 1 and "cell B" to refer to Cell B in Figure 1.

[0078] In the on-demand SIB1 transmission process shown in scenario 1-1, cell B first needs to send SIB1 request configuration information to the UE. This SIB1 request configuration information is used to configure the SIB1 request. The UE sends an SIB1 request to cell B according to the SIB1 request configuration information, and cell B sends SIB1 to the UE after receiving the SIB1 request. At this time, the UE can be a UE preparing to hand over or reselect to cell B from other cells, or a UE that has not yet joined any cell and is preparing to join cell B. This application does not impose any restrictions on this.

[0079] Scenario 2: As shown in Figure 1-2, in the on-demand SIB1 transmission process of Scenario 2 shown in Figure 1-2, cell A first needs to send SIB1 request configuration information to the UE. This SIB1 request configuration information is used to configure the SIB1 request. The UE sends an SIB1 request to cell B according to the SIB1 request configuration information. After receiving the SIB1 request, cell B sends SIB1 to the UE. The information about cell B in the SIB1 request configuration information can be exchanged through communication via the Xn interface.

[0080] Specifically, cell B sends the SIB1 request configuration information related to cell B to cell A through the Xn interface. Correspondingly, cell A receives the SIB1 request configuration information related to cell B through the Xn interface, and subsequently, cell A sends the SIB1 request configuration information related to cell B to the UE so that the UE can send an SIB1 request to cell B.

[0081] Optionally, in scenario two as shown in Figure 1-2, cell A can be the serving cell of the UE. Specifically, this can be a scenario where the UE requests SIB1 from cell B on demand during the process of switching or reselecting from cell A to cell B. Alternatively, the UE may not be connected to either cell A or cell B, but rather to cell C, or the UE may not be connected to any cell. This application does not restrict the relationship between cell A and the UE.

[0082] Scenario 3: As shown in Figure 1, section 1-3, in the on-demand SIB1 transmission process of Scenario 3, cell A first needs to send SIB1 request configuration information to the UE. This SIB1 request configuration information is used to configure the SIB1 request. The UE sends an SIB1 request to cell A according to the SIB1 request configuration information, and cell A sends SIB1 to the UE after receiving the SIB1 request. The SIB1 sent by cell A is related to cell B. Cell A can communicate with cell B through the Xn interface to obtain the SIB1 related to cell B.

[0083] Optionally, in scenario three as shown in Figure 1-3, cell A can be the serving cell of the UE. Specifically, in the process where the UE wants to switch or reselect from cell A to cell B, it can request SIB1 of cell B on demand. The UE may also not be connected to cell A or cell B, but connected to cell C, or the UE may not be connected to any cell. This application does not restrict the relationship between cell A and the UE.

[0084] Scenario 4: As shown in Figure 1, section 1-4, in the on-demand SIB1 transmission process of Scenario 4, cell A first needs to send the SIB1 request configuration information to the UE. This SIB1 request configuration information is used to configure the SIB1 request. The UE sends the SIB1 request to cell A according to the SIB1 request configuration information. After receiving the SIB1 request, cell A sends the SIB1 to the UE through cell B. Cell A can communicate with cell B through the Xn interface to inform cell B about the UE's information, enabling cell B to send the SIB1 to the UE.

[0085] Optionally, in scenario four shown in Figure 1-4, cell A can be the serving cell of the UE. Specifically, this can be a scenario where the UE requests SIB1 of cell B on demand during the process of switching or reselecting from cell A to cell B. Alternatively, the UE may not be connected to either cell A or cell B, but rather to cell C, or the UE may not be connected to any cell. This application does not restrict the relationship between cell A and the UE.

[0086] In the on-demand SIB1 sending method mentioned above, the terminal device needs to request SIB1 from the relevant network device (cell) based on the SIB1 request configuration information. The SIB1 request configuration information needs to be consistent between the terminal device and the network device in order for the on-demand SIB1 request process to proceed normally.

[0087] However, in practice, the SIB1 request configuration information can be changed, meaning it can be updated. For example, at the first moment, the cells that can provide services to the terminal device are: Cell A, Cell B, and Cell C. All three cells are NES cells, and all three are in on-demand SIB1 sending mode. Therefore, at the first moment, the SIB1 request configuration information sent by the network device to the terminal device includes relevant information about Cell A, Cell B, and Cell C (such as the PCI information of each cell). However, at the second moment, Cell A can no longer provide services to the terminal device, and the SIB1 request configuration information on the network device side no longer includes information about Cell A. If, at the second moment, the terminal device still sends an SIB1 request to Cell A according to the SIB1 request configuration information from the first moment, the SIB1 request will fail.

[0088] To avoid SIB1 request failures, this application provides a method for updating SIB1 request configuration information, which facilitates correct SIB1 requests and increases the probability of successful SIB1 requests. It should be noted that the SIB1 request configuration information update method provided in this application is applicable to the four scenarios described in Figure 1 above, but is not limited to these four scenarios.

[0089] To better understand the embodiments of this application, the system architecture involved in the embodiments of this application will be described first below:

[0090] The technical solution of this application may adopt access technologies that evolve after 5G, such as Long Term Evolution (LTE) access technology, 5th generation mobile communication (5G) access technology, and 6th generation mobile communication (6G) access technology.

[0091] The basic architecture of the communication system provided in this application is described below. The communication system provided in this application may include one or more network devices and one or more terminal devices.

[0092] The following explanation uses the system architecture shown in Figure 2 as an example. In Figure 2, the communication system includes a network device 10 and a terminal device 20 that communicates with the network device 10.

[0093] It should be noted that the number of network devices and terminal devices in Figure 2 is merely illustrative and should not be considered as a specific limitation of this application. The terminal devices and network devices involved in the system architecture will be described in detail below.

[0094] I. Terminal Equipment

[0095] A terminal device is an entity on the user side used to receive signals, or transmit signals, or both. Terminal devices are used to provide users with one or more of the following: voice services and data connectivity services. A terminal device can be a device that includes wireless transceiver capabilities and can cooperate with network equipment to provide communication services to users. Specifically, a terminal device can refer to: user equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, terminal, wireless communication equipment, user agent, user equipment, or roadside unit (RSU). Terminal devices can also be drones, Internet of Things (IoT) devices, stations (STs) in wireless local area networks (WLANs), cellular phones, smartphones, cordless phones, wireless data cards, tablets, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistant (PDA) devices, laptop computers, machine type communication (MTC) terminals, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices (also known as wearable smart devices), virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in remote medical care, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in smart grids, and transportation security devices. Wireless terminals in smart cities, smart homes, etc. The terminal device can also be a terminal in a 5G system or a terminal in a next-generation communication system; this application does not limit this.

[0096] The embodiments of this application do not limit the device form of the terminal device. The device used to implement the function of the terminal device can be the terminal device itself; it can also be a device that supports the terminal device in implementing the function, such as a chip system. The device can be installed in the terminal device or used in conjunction with the terminal device. In the embodiments of this application, the chip system can be composed of chips or can include chips and other discrete components.

[0097] II. Network Equipment

[0098] A network device is an entity on the network side used to transmit signals, or receive signals, or both. A network device can be a means deployed in a radio access network (RAN) to provide wireless communication capabilities to terminal devices.

[0099] In one possible scenario, network equipment can be devices with base station functions, such as evolved NodeBs (eNodeBs), transmitting and receiving points (TRPs), transmitting points (TPs), next-generation NodeBs (gNBs), next-generation base stations in 6G mobile communication systems, integrated access and backhaul (IAB) nodes, and non-terrestrial network equipment, i.e., equipment that can be deployed on high-altitude platforms or satellites. Network equipment can also be transmitting and receiving points (TRPs), base stations, and various forms of control nodes, such as network controllers and wireless controllers. Specifically, network equipment can be various forms of macro base stations, micro base stations (also known as small cells) in heterogeneous network (HetNet) scenarios, relay stations, access points (APs), radio network controllers (RNCs), node Bs (NBs), base station controllers (BSCs), base transceiver stations (BTSs), home base stations (e.g., home evolved node Bs, or home node Bs (HNBs)), baseband units (BBUs) and remote radio units (RRUs) in distributed base station scenarios, transmitting and receiving points (TRPs), transmitting points (TPs), mobile switching centers, etc., and can also be base station antenna panels. Control nodes can connect to multiple base stations and configure resources for multiple terminals covered by multiple base stations. In systems employing different wireless access technologies, the names of devices with base station functions may differ. For example, it could be a gNB in ​​5G, or a network-side device in a network after 5G, or a network device in a future evolved public land mobile network (PLMN) network, or a device that performs base station functions in device-to-device (D2D) communication, machine-to-machine (M2M) communication, or vehicle-to-everything (V2X) communication, etc. This application does not limit the specific name of the network device.Network equipment can also be open RAN (O-RAN or ORAN), baseband pool (BBU pool) and RRU under cloud radio access network (CRAN), etc.

[0100] In another possible scenario, multiple network devices collaborate to assist terminal devices in achieving wireless access, with each network device performing a portion of the base station's functions. For example, network devices may include a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). CUs and DUs can be separate entities or included in the same network element, such as a baseband unit (BBU). RUs may be included in radio equipment or radio units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs). It is understood that network devices can be CU nodes, DU nodes, or devices comprising both CU and DU nodes. Furthermore, CUs can be classified as network devices in the access network (RAN) or the core network (CN), without limitation.

[0101] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0102] Optionally, the network device in this application can be a network device that supports two transmission modes, that is, the network device in this application can support periodic transmission of SIB1 and on-demand transmission of SIB1. For example, at the first moment, the network device is in periodic transmission of SIB1 mode, and at the second moment, the network device can switch to on-demand transmission of SIB1 mode.

[0103] Optionally, the network device in this application may be a network device that only supports one transmission mode. Specifically, the network device in this application only supports periodic transmission of SIB1 mode.

[0104] In this embodiment, the form of the network device is not limited. The device used to implement the function of the network device can be the network device itself, or it can be a device that supports the network device in implementing the function, such as a chip system. The device can be installed in the network device or used in conjunction with the network device.

[0105] The SIB1 request configuration information update method provided in this application embodiment will be further described below with reference to Figure 3. It is understood that this application uses terminal devices and network devices as examples of the execution subjects in the interaction illustration, but it does not limit the execution subjects of the interaction illustration. For example, the method executed by the network device in this application can also be executed by a module applied to the network device (e.g., a chip, chip system, or processor), or by a logical node, logical module, or software capable of implementing all or part of the network device's functions; similarly, the method executed by the terminal device in this application can also be executed by a module applied to the terminal device (e.g., a chip, chip system, or processor), or by a logical node, logical module, or software capable of implementing all or part of the terminal device's functions. Wherein:

[0106] 301. The network device sends a first message, which includes first indication information and first configuration information. The first indication information indicates that SIB1 has requested an update to its configuration information, and the first configuration information is used to configure the configuration information requested by SIB1. Accordingly, the terminal device receives the first message.

[0107] Optionally, the first message is the first SIB.

[0108] Optionally, the first indication information is an SI change indication associated with the first SIB; specifically, the first indication information is the valueTag associated with the first SIB. This first indication information changes when the configuration information regarding SIB1 carried in the first SIB changes. In other words, a change in the configuration information regarding SIB1 carried in the first SIB will cause a change in the first indication information.

[0109] For example, the configuration information requested by SIB1 is carried in a new SIB. If the configuration information requested by SIB1 changes, the valueTag associated with this new SIB will also change accordingly. As another example, the configuration information requested by SIB1 is carried in SIB2. If the configuration information requested by SIB1 changes, the valueTag associated with this SIB2 will also change accordingly.

[0110] Optionally, the first configuration information is carried in the first SIB, and the first indication information is associated with the SI change indication of the first SIB.

[0111] The first SIB can be SIB1, or it can be any other SIB besides SIB1 (e.g., SIB2, SIB3, SIB4, SIB5, or a new SIB). The following describes the cases where the first SIB is SIB1 and the first SIB is any other SIB:

[0112] Case 1: The first SIB is SIB1.

[0113] Optionally, the control information candidate resources of the first SIB are indicated by information in the SSB.

[0114] Optionally, the information in this SSB includes, but is not limited to, the following: SIB1 control information.

[0115] Optionally, the terminal device can receive SIB1 through SIB1 control information, which refers to the candidate frequency domain resource CORESET and time domain resource search space of the PDCCH corresponding to the PDSCH that transmits SIB1.

[0116] Optionally, the SSB carrying the SIB1 control information indication is a complete SSB, which refers to an SSB containing valid SIB1 control information. Valid SIB1 control information means that SIB1 can be received through this SIB1 control information.

[0117] Optionally, the complete SSB is sent within one SSB transmission window, or the complete SSB is sent over M SSB cycles, where the SSB transmission window is an integer multiple of the SSB cycle, and M is a preset value, or M is related to the configuration information requested by SIB1. Specifically, M can be configured and updated using the configuration information requested by SIB1.

[0118] Optionally, in this case, the network device sends a complete SSB, which carries SIB1 control information. The terminal device can obtain SIB1 at the corresponding resource location through the SIB1 control information. The first configuration information is carried in SIB1, so the terminal device obtains the first configuration information.

[0119] Scenario 2: The first SIB is an SIB other than SIB1.

[0120] Optionally, the other SIB can also be called SIBx. The first configuration information is carried in SIBx. Since SIB1 contains the scheduling information of SIBx, and the method of obtaining SIB1 can refer to the above-described case one, SIB1 can be obtained first, then SIBx can be obtained through SIB1, and finally the first configuration information can be obtained from SIBx.

[0121] In one possible embodiment, the transmission resources of the first SIB are indicated by the first SIB scheduling information, which is carried in SIB1, and the transmission resources of SIB1 are indicated by the SIB1 control information carried in SSB.

[0122] The first SIB scheduling information is the scheduling information about SIBx in SIB1. The terminal device can obtain SIBx through the scheduling information of SIBx in SIB1, and thus obtain the first configuration information carried in SIBx.

[0123] Optionally, the SSB carrying the SIB1 control information indication is a complete SSB, which refers to an SSB containing valid SIB1 control information. Valid SIB1 control information means that SIB1 can be received through this SIB1 control information.

[0124] The complete SSB can be found in the description in Case 1 above, and this application does not impose any restrictions on it.

[0125] Optionally, in this second scenario, the network device sends a complete SSB, which carries SIB1 control information. The terminal device can obtain SIB1 at the corresponding resource location through this SIB1 control information. Since SIB1 contains SIBx scheduling information, SIBx can be obtained through the SIBx scheduling information contained in SIB1. The first configuration information is carried in SIBx, thereby allowing the terminal device to obtain the first configuration information.

[0126] The above two scenarios describe how terminal devices obtain the first configuration information when it is carried under SIB1 and SIBx, respectively. The network device that sends the first configuration information will now be described with reference to Figure 1.

[0127] In one possible embodiment, the first configuration information includes the SIB1 request configuration information of the current cell, or it includes the SIB1 request configuration information of neighboring cells.

[0128] Optionally, the first configuration information includes the SIB1 request configuration information of this cell. For example, in the scenario corresponding to 1-1 in Figure 1, the cell is Cell B. The first configuration information includes the SIB1 request configuration information of Cell B. Subsequently, the terminal device sends an SIB1 request to Cell B through the SIB1 request configuration information of Cell B.

[0129] Optionally, the first configuration information is the updated SIB1 request configuration information, and the update of the first configuration information includes the update of the SIB1 request configuration information of this cell. For example, in the scenario corresponding to 1-1 in Figure 1, the updated part of the first configuration information includes the part of the updated SIB1 request configuration information of cell B.

[0130] Optionally, the first configuration information includes the SIB1 request configuration information of the neighboring cell. For example, scenarios 1-2, 1-3, and 1-4 in Figure 1. In these scenarios, the local cell is Cell A, and the neighboring cell is Cell B, which is a neighboring cell of Cell A. Since Cell A sends the first configuration information to the terminal device in these scenarios, Cell A is considered the local cell, and Cell B is considered the neighboring cell. This first configuration information includes the SIB1 request configuration information of Cell B; that is, Cell A sends the SIB1 request configuration information of Cell B (the neighboring cell) to the terminal device, and the terminal device subsequently sends an SIB1 request to Cell B using this SIB1 request configuration information.

[0131] Optionally, the first configuration information is the updated SIB1 request configuration information, and the update of the first configuration information includes the update of the SIB1 request configuration information of neighboring cells. For example, in the scenarios corresponding to 1-2, 1-3 and 1-4 in Figure 1, the updated part of the first configuration information includes the part of the SIB1 request configuration information update of cell B (neighboring cell).

[0132] In addition to the two methods mentioned above where terminal devices obtain the first configuration information through a complete SSB, this application also provides another method for obtaining the first configuration information. In one possible embodiment, the terminal device obtains the first SSB through a paging process.

[0133] Optionally, the first SIB can be SIB1. The first configuration information is carried in SIB1. The terminal device obtains the first configuration information by acquiring SIB1 through a paging process.

[0134] Optionally, the first SIB can be an SIBx other than SIB1. The first configuration information is carried in the SIBx. The terminal device obtains the SIBx through a paging process, thereby obtaining the first configuration information. Alternatively, the terminal device obtains SIB1 through a paging process, and then obtains the SIBx through the scheduling information in SIB1, thereby obtaining the first configuration information.

[0135] Optionally, the first configuration information obtained by the terminal device through the paging process is the SIB1 request configuration information of the neighboring cell. As shown in Figure 4A, when the SIB1 request configuration information related to the NES Cell (neighboring cell) changes, the NES Cell informs cell A of the change. Cell A then notifies the terminal device to update the SIB containing the SIB1 request configuration information (first configuration information) through the paging process. The SI change indication in the SIB message updated by this paging process differs from the SI change indication in the previous SIB message.

[0136] The following section, with reference to Figure 4B, further describes the two methods by which the aforementioned terminal devices obtain updated SIB1 request configuration information (obtained through the paging process and obtained through SSB).

[0137] Optionally, a change in the SI change indication will trigger a paging procedure, which can notify UEs that need to update their system messages. If the SIB1 request configuration information changes, the SI change indication associated with the first SIB carrying that SIB1 request configuration information will also change, triggering a paging procedure. After the paging procedure is initiated, the terminal device can obtain the updated system message (first SIB) during the system message change cycle.

[0138] For example, assume the terminal device is camped in NES Cell 1, and its neighboring cells are NES Cell 2 and Cell A. When NES Cell 2 updates its SIB1 request configuration information, it notifies Cell A. NES Cell 2 and Cell A can communicate via the Xn interface; that is, NES Cell 2 notifies Cell A through the Xn interface and sends the updated SIB1 request configuration information to Cell A. This updated SIB1 request configuration information is carried in the SIB message. Cell A updates the SIB message through a paging procedure, and the terminal device thus obtains the updated SIB1 request configuration information.

[0139] Optionally, the SIB1 request configuration information sent via SSB may include only the SIB1 request configuration information of NES Cell 2.

[0140] Optionally, the updated SIB1 request configuration information sent by cell A to the terminal device includes the SIB1 request configuration information of NES Cell 2, as well as the SIB1 request configuration information of other neighboring cells (e.g., NES Cell 3, NES Cell 4, etc.). For example, at the first moment, the SIB1 request configuration information of NES Cell 2 is SIB1 request configuration information A, the SIB1 request configuration information of NES Cell 3 is request configuration information B, and the SIB1 request configuration information of NES Cell 4 is request configuration information C. At the second moment, the SIB1 request configuration information of NES Cell 2 is changed from SIB1 request configuration information A to SIB1 request configuration information D. At the second moment, the SIB message updated by cell A through the paging procedure includes SIB1 request configuration information B, SIB1 request configuration information C, and SIB1 request configuration information D.

[0141] Optionally, assuming that at the first moment, the SI change indication associated with the SIB message containing SIB1 request configuration information is 1, and at the second moment, since the SIB1 request configuration information has changed (SIB1 request configuration information A in the SIB message has changed to SIB1 request configuration information D), then at the second moment, the SI change indication associated with the SIB message containing SIB1 request configuration information changes to 2. The change of the SI change indication will notify the terminal device through the paging process, and the SIB message containing SIB1 request configuration information needs to be updated. The terminal device updates the SIB message and obtains the updated SIB1 request configuration information.

[0142] For example, assume the terminal device is camped in NES Cell 1, and its neighboring cells are NES Cell 2 and Cell A. When NES Cell 2 updates its SIB1 request configuration information, NES Cell 2 informs NES Cell 1 via the Xn interface. NES Cell 1 then sends an SSB to the terminal device to inform it of the updated SIB1 request configuration information. This SIB1 request configuration information can be carried in SIB1 or in SIBx; for details, please refer to the descriptions of Case 1 and Case 2 above, which will not be elaborated upon here.

[0143] Optionally, the SIB1 request configuration information sent via SSB may include the SIB1 request configuration information of NES Cell 2, as well as the SIB1 request configuration information of other neighboring cells (such as NES Cell 3, NES Cell 4, etc.).

[0144] Optionally, the SIB1 request configuration information sent via SSB may include only the SIB1 request configuration information of NES Cell 2.

[0145] Optionally, if the updated SIB1 request configuration information is sent via SSB, the SI change indication in SIB1 or SIBx will also be changed.

[0146] 302. Based on the first instruction information, the terminal device updates the configuration information used to configure the SIB1 request to the first configuration information.

[0147] Optionally, the first indication information can be an SI change indication, specifically a ValueTag.

[0148] In one possible embodiment, the terminal device updates the configuration information used to configure the SIB1 request to the first configuration information based on the first indication information, including: updating the configuration information used to configure the SIB1 request to the first configuration information when the first indication information changes.

[0149] For example, suppose that at a first moment, the network device sends a first SIB associated with ValueTag=1 and SIB configuration information A to the terminal device, and the terminal device stores the relevant information of the first SIB. Specifically, it can store ValueTag=1 and SIB configuration information A. At a second moment, the SIB configuration information A changes from SIB configuration information A to SIB configuration information B. At this time, the network device sends the first SIB associated with ValueTag=2 ​​and SIB configuration information B to the terminal device. The change of valueTag will initiate a paging procedure to notify the terminal that the SIB has changed. The UE updates the SIB message and obtains SIB configuration information B in the subsequent system information change cycle.

[0150] In this manner, after the SIB1 request configuration information is updated, the network device proactively sends the updated SIB1 request configuration information to the terminal device. Optionally, in some cases, the terminal device may proactively request the updated SIB1 request configuration information from the network device.

[0151] For example, if a terminal device identifies the current cell as an NES cell and the SIB message containing SIB1 request configuration information stored in the terminal device is invalid, the terminal device proactively requests the updated SIB1 request configuration information from the network device. Alternatively, if the terminal device does not store SIB1 request configuration information (e.g., when the terminal device is first powered on), the terminal device proactively requests the SIB1 request configuration information from the network device. Or, if the SIB1 request configuration information stored in the terminal device does not include the SIB1 request configuration information for the identified NES cell, the terminal device proactively requests the SIB1 request configuration information from the network device. The terminal device's request for SIB1 request configuration information from the network device is not limited to the scenarios exemplified above, and this application does not impose any restrictions on these scenarios.

[0152] The following description, with reference to Figure 5, illustrates the scenario where the terminal device actively requests configuration information from the network device via SIB1. It should be understood that this embodiment uses the terminal device and network device as examples of the entities performing this interaction, but it does not limit the entities that can perform the interaction. Wherein:

[0153] 501. The terminal device sends a second message, which requests second configuration information. The second configuration information is used to configure SIB1. Correspondingly, the network device receives the second message.

[0154] Optionally, the second message is a preamble sequence or Msg1. Preamble and Msg1 can be found in the descriptions above and will not be repeated here.

[0155] Optionally, the second message includes second instruction information, which is used to instruct the network device to send second configuration information to the terminal device.

[0156] Optionally, the second indication information is the index of the preamble, which is either the default index or an index agreed upon by the protocol.

[0157] Optionally, the root sequence and cyclic shift corresponding to the preamble can be the default root sequence and default cyclic shift, or the root sequence and cyclic shift specified by the protocol.

[0158] Optionally, the index of the preamble, the root sequence of the preamble, and the cyclic shift are indicated by the SSB.

[0159] Optionally, the index of the preamble, the root sequence of the preamble, and the cyclic shift are indicated by MIB and / or PBCH loads.

[0160] Optionally, the transport resources of the preamble are indicated by the SSB, specifically by the master information block (MIB) and / or the physical broadcast channel (PBCH) payload.

[0161] For example, the following description, in conjunction with Figure 6, further illustrates this embodiment, which corresponds to scenario 1-2 in Figure 1 above. Specifically: 601. Cell A sends a MIB and / or PBCH to the terminal device to indicate the preamble index, the root sequence of the preamble, and the cycle shift. 602. Based on the preamble index, the root sequence of the preamble, and the cycle shift indicated in step 601, the terminal device sends a preamble to Cell A to request second configuration information. After receiving the preamble, Cell A responds by sending the second configuration information to the terminal device (603. Cell A sends the second configuration information to the terminal device). The second configuration information includes at least the Nes Cell's SIB1 request configuration information. 604. The terminal device sends an SIB1 request to the Nes Cell based on the second configuration information. 605. The Nes Cell sends the SIB1 request to the terminal device.

[0162] Optionally, when the terminal device identifies the current cell as an NES cell and the SIB message containing SIB1 request configuration information stored in the terminal device is invalid, the terminal device sends a preamble or Msg1 to the network device.

[0163] Optionally, if the terminal device does not store SIB1 request configuration information, the terminal device may send a preamble or Msg1 to the network device.

[0164] Optionally, if the SIB1 request configuration information stored in the terminal device does not contain the identified SIB1 request configuration information of the NES cell, the terminal device sends a preamble or Msg1 to the network device.

[0165] 502. The network device sends the second configuration information. Correspondingly, the terminal device receives the second configuration information.

[0166] Optionally, the transmission resources of the second configuration information are indicated by a third message, or the second configuration information is carried in a third message; wherein the third message is a random access response (RAR), Msg2, or a second SIB.

[0167] (1) The transmission resources of the second configuration information are indicated by Msg2.

[0168] Optionally, Msg2 includes the scheduling PDCCH corresponding to the SIB1 request configuration information.

[0169] Optionally, the terminal device receives the PDCCH and receives SIB1 request configuration information based on the PDCCH.

[0170] Optionally, the second configuration information (SIB1 request configuration information) is carried in the first PDCCH, which is indicated by Msg2.

[0171] Optionally, the second configuration information may contain only the SIB1 request configuration information of this cell, or the SIB1 request configuration information of this cell and neighboring cells.

[0172] (2) The second configuration information is carried in Msg2.

[0173] Optionally, Msg2 contains a second configuration information.

[0174] Optionally, the second configuration information may contain only the SIB1 request configuration information of this cell, or the SIB1 request configuration information of this cell and neighboring cells.

[0175] (3) The second configuration information is carried in the second SIB.

[0176] Optionally, the third message is the second SIB, and the transmission information of the second SIB is obtained through the SSB.

[0177] The third message is the second SIB, which can be either SIB1 or SIBx (SIBx is any other SIB message besides SIB1).

[0178] Optionally, the SSB can be the first SSB opportunity after the fourth message and the SSB transmitted thereafter, or the SSB can be the SSB transmitted within the first complete SSB cycle after the fourth message and the SSB transmitted thereafter, or the SSB can be the first SSB opportunity after the window corresponding to the fourth message and the SSB transmitted thereafter, or the SSB can be the SSB transmitted within the first complete SSB cycle after the window corresponding to the fourth message and the SSB transmitted thereafter.

[0179] In one possible embodiment, the second SIB is SIB1, and the control information candidate resource of the second SIB is indicated by information in the SSB.

[0180] Optionally, the terminal device can receive SIB1 through SIB1 control information, which refers to the candidate frequency domain resource CORESET and time domain resource search space of the PDCCH corresponding to the PDSCH that transmits SIB1.

[0181] Optionally, the SSB carrying the SIB1 control information indication is a complete SSB, which refers to an SSB containing valid SIB1 control information. Valid SIB1 control information means that SIB1 can be received through this SIB1 control information.

[0182] In one possible embodiment, the second SIB is SIBx, the transmission information of the second SIB is indicated by the second SIB scheduling information, the second SIB scheduling information is carried in SIB1, and the control information candidate resources of SIB1 are indicated by the information in SSB.

[0183] Optionally, the terminal device obtains the transmission information of SIBx through SIB1, which includes whether it is in broadcast mode and the transmission resources used for transmission.

[0184] Optionally, the SSB can be the first SSB opportunity after the fourth message and the SSB transmitted thereafter, or the SSB can be the SSB transmitted within the first complete SSB cycle after the fourth message and the SSB transmitted thereafter, or the SSB can be the first SSB opportunity after the window corresponding to the fourth message and the SSB transmitted thereafter, or the SSB can be the SSB transmitted within the first complete SSB cycle after the window corresponding to the fourth message and the SSB transmitted thereafter.

[0185] Optionally, the complete SSB refers to an SSB containing valid SIB1 control information, and valid SIB1 control information means that SIB1 can be received through this SIB1 control information.

[0186] Optionally, the fourth message is a random access response (RAR) or Msg2.

[0187] For example, the fourth message is Msg2, and the third message is the second SIB. Msg2 contains an acknowledgment message for the received second message. The network device begins sending a complete SSB at the start of the SBB cycle after sending Msg2. This complete SSB contains valid SIB control information. "Valid" means that SIB1 can be received through the SIB1 control information in the SSB. The SIB1 control information refers to the candidate frequency domain resource CORESET and time domain resource search space of the PDCCH corresponding to the PDSCH transmitting SIB1.

[0188] Optionally, the starting position of the complete SSB cycle is the first complete SSB cycle after Msg2 is sent, or the starting position of the complete SSB cycle is the first complete SSB cycle after the RAR window.

[0189] Optionally, the complete SSB can be sent within an SSB window or within M SSB cycles, where the SSB window is an integer multiple of the SSB cycle.

[0190] Optionally, after receiving a complete SSB, the terminal device obtains SIB1 and / or SIBx through the complete SSB, and obtains second configuration information through SIB1 and / or SIBx.

[0191] In one possible embodiment, where the second configuration information is carried in SIB1: the network device sends a complete SSB, which carries SIB1 control information. The terminal device can obtain SIB1 at the corresponding resource location through the SIB1 control information. The second configuration information is carried in SIB1, so the terminal device obtains the second configuration information.

[0192] In one possible embodiment, where the second configuration information is carried in SIBx: the network device sends a complete SSB, which carries SIB1 control information. The terminal device can obtain SIB1 at the corresponding resource location through this SIB1 control information. Since SIB1 contains SIBx scheduling information, SIBx can be obtained through the SIBx scheduling information contained in SIB1. The first configuration information is carried in SIBx, thereby enabling the terminal device to obtain the first configuration information.

[0193] Optionally, the second configuration information may contain only the SIB1 request configuration information of this cell, or the SIB1 request configuration information of this cell and neighboring cells.

[0194] In summary, this application provides two methods for updating SIB1 request configuration information: one is for the network device to proactively update the SIB1 request configuration information for the terminal device, and the other is for the terminal device to autonomously request the SIB1 request configuration information from the network device to update the SIB1 request configuration information. The purpose of both methods is to align the SIB1 request configuration between the network device and the terminal device, thereby enabling the terminal device to correctly request SIB1 and increasing the probability of successful SIB1 requests.

[0195] This application provides a communication device that can be used to implement the functions of the aforementioned terminal device or network device. The communication device can be a terminal device or a network device. The communication device includes modules or units corresponding to the methods / operations / steps / actions performed by the terminal device or network device in the above method embodiments. These units can be hardware circuits, software, or a combination of hardware circuits and software. Please refer to Figure 7, which shows a schematic diagram of the structure of a communication device 700 according to an embodiment of this application. The communication device 700 may include an interface unit 701 and a processing unit 702. The processing unit 702 is used to process signaling and / or data, which may be data received by the interface unit 701, and the processed signaling and / or data may also be sent by the interface unit 701.

[0196] In one embodiment, when the communication device 700 is a terminal device, wherein:

[0197] Interface unit 701 is used to receive a first message, the first message including first indication information and first configuration information, the first indication information indicating that the configuration information requested by SIB1 is updated, and the first configuration information is used to configure the configuration information requested by SIB1.

[0198] The processing unit 702 is configured to update the configuration information used to configure the SIB1 request to the first configuration information based on the first indication information.

[0199] In one possible embodiment, the first message is the first SIB.

[0200] In one possible embodiment, the first SIB is SIB1.

[0201] In one possible embodiment, the control information candidate resource of the first SIB is indicated by information in the SSB.

[0202] In one possible embodiment, the first SIB is an SIB other than SIB1.

[0203] In one possible embodiment, the first configuration information includes the SIB1 request configuration information of the current cell, or it includes the SIB1 request configuration information of neighboring cells.

[0204] In one embodiment, when the communication device 700 is a network device, wherein:

[0205] Interface unit 701 is used to send a first message, the first message including first indication information and first configuration information, the first indication information indicating that the configuration information requested by SIB1 is updated, and the first configuration information is used to configure the configuration information requested by SIB1.

[0206] In one possible embodiment, the first message is the first SIB.

[0207] In one possible embodiment, the first SIB is SIB1.

[0208] In one possible embodiment, the control information candidate resource of the first SIB is indicated by information in the SSB.

[0209] In one possible embodiment, the first configuration information includes the SIB1 request configuration information of the current cell, or it includes the SIB1 request configuration information of neighboring cells.

[0210] In one embodiment, when the communication device 700 is a terminal device, wherein:

[0211] Interface unit 701 is used to send a second message, which is used to request second configuration information, and the second configuration information is used to configure SIB1 request configuration information; and to receive the second configuration information.

[0212] In one possible embodiment, the second message is a preamble sequence or Msg1.

[0213] In one possible embodiment, the transmission resources of the second configuration information are indicated by a third message, or the second configuration information is carried in a third message; wherein the third message is a random access response (RAR), Msg2, or a second SIB.

[0214] In one possible embodiment, the third message is a second SIB, and the transmission information of the second SIB is obtained through the SSB.

[0215] In one possible embodiment, the SSB is the first SSB opportunity after the fourth message and the SSB transmitted thereafter, or the SSB is the SSB transmitted within the first full SSB cycle after the fourth message and thereafter, or the SSB is the first SSB opportunity after the window corresponding to the fourth message and the SSB transmitted thereafter, or the SSB is the SSB transmitted within the first full SSB cycle after the window corresponding to the fourth message and thereafter.

[0216] In one possible embodiment, the fourth message is a random access response (RAR) or Msg2.

[0217] In one embodiment, when the communication device 700 is a terminal device, wherein:

[0218] Interface unit 701 is used to receive a second message, the second message being used to request second configuration information, the second configuration information being used to configure SIB1 request configuration information; and to send the second configuration information.

[0219] In one possible embodiment, the second message is a preamble sequence or Msg1.

[0220] In one possible embodiment, the transmission resources of the second configuration information are indicated by a third message, or the second configuration information is carried in a third message; wherein the third message is a random access response (RAR), Msg2, or a second SIB.

[0221] In one possible embodiment, the third message is a second SIB, and the transmission information of the second SIB is obtained through the SSB.

[0222] In one possible embodiment, the SSB is the first SSB opportunity after the fourth message and the SSB transmitted thereafter, or the SSB is the SSB transmitted within the first full SSB cycle after the fourth message and thereafter, or the SSB is the first SSB opportunity after the window corresponding to the fourth message and the SSB transmitted thereafter, or the SSB is the SSB transmitted within the first full SSB cycle after the window corresponding to the fourth message and thereafter.

[0223] In one possible embodiment, the fourth message is a random access response (RAR) or Msg2.

[0224] Figure 8 illustrates a communication device 800 provided in an embodiment of this application, used to implement the functions of the aforementioned terminal device or network device. This device can be a communication device or a device used within a communication device. The communication device can be a terminal device or a network device. The device used within the communication device can be a chip system or a chip within the communication device. The chip system can be composed of chips, or it can include chips and other discrete components.

[0225] The communication device 800 includes at least one processor 810 for implementing the processing functions of the device (e.g., network device or terminal device) in the method provided in the embodiments of this application.

[0226] Optionally, the communication device 800 may further include a communication interface 820 for implementing the transmit and receive operations of the device (e.g., a network device or a terminal device) in the method provided in this application embodiment. In this application embodiment, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface for communicating with other devices through a transmission medium. For example, the communication interface 820 is used for the device in the communication device 800 to communicate with other devices. The processor 810 uses the communication interface 820 to transmit and receive data and to implement the method described in the above method embodiment. As shown in FIG8, the communication interface 820 may be located inside or outside the communication device 800, and this application embodiment does not limit this.

[0227] Optionally, the communication device 800 may further include at least one memory 830 for storing program instructions and / or data. The memory 830 is coupled to the processor 810. The coupling in this embodiment is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, for information exchange between devices, units, or modules. The processor 810 may operate in conjunction with the memory 830. The processor 810 may execute program instructions stored in the memory 830. At least one of the at least one memory may be included in the processor 810. Alternatively, the at least one memory may be located within the communication device 800 and outside the processor 810. Alternatively, the at least one memory may be located outside the communication device 800; this embodiment does not limit the scope of the application.

[0228] This embodiment does not limit the specific connection medium between the communication interface 820, processor 810, and memory 830. In Figure 8, the memory 830, processor 810, and communication interface 820 are connected via a bus, indicated by a thick line. The connection methods between other components are merely illustrative and not intended to be limiting. The bus can be categorized as an address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 8, but this does not imply that there is only one bus or one type of bus.

[0229] When the communication device 800 is specifically a device for use with equipment (such as network equipment or terminal equipment), for example, when the communication device 800 is specifically a chip or chip system, the communication interface 820 may output or receive baseband signals. When the communication device 800 is specifically a device (such as network equipment or terminal equipment), the communication interface 820 may output or receive radio frequency signals. In the embodiments of this application, the processor may be a general-purpose processor, digital signal processor, application-specific integrated circuit, field-programmable gate array or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, which can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly reflected as being executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.

[0230] It should be noted that the aforementioned communication interface 820 can be used to perform the functions of the aforementioned interface unit 701, and the aforementioned processor 810 can be used to perform the functions of the aforementioned processing unit 702, which will not be elaborated further here.

[0231] When the aforementioned communication device is a chip applied to a terminal device, the terminal device chip implements the functions of the terminal device in the above method embodiments, and the terminal device chip receives information from other network elements; or, the terminal device chip sends information to other network elements.

[0232] When the aforementioned communication device is a chip used in a network device, the network device chip implements the functions of the network device in the above method embodiments. The network device chip receives information from other network elements; or, the network device chip sends information to other network elements.

[0233] It is understood that the processor in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor or any conventional processor.

[0234] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Additionally, the ASIC can reside in a network device or a terminal device. Alternatively, the processor and storage medium can exist as discrete components in the terminal device or network device.

[0235] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer program or instructions can be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a DVD; or it can be a semiconductor medium, such as a solid-state disk (SSD).

[0236] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0237] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

[0238] This application also provides a computer-readable storage medium storing computer-executable instructions. When the computer-executable instructions are executed, the method executed by the terminal device or network device in the above method embodiments is implemented.

[0239] This application also provides a computer program product, which includes a computer program that, when executed, causes the method executed by the terminal device or network device in the above method embodiments to be implemented.

[0240] This application also provides a communication system, which includes a terminal device or a network device. The terminal device is used to execute the method described in the above method embodiments. The network device is used to execute the method described in the above method embodiments.

[0241] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0242] The descriptions of the various embodiments provided in this application can be referenced mutually. Each embodiment has its own emphasis, and parts not described in detail in a certain embodiment can be referred to the relevant descriptions of other embodiments. For the sake of convenience and brevity, for example, the functions and execution steps of the various devices and equipment provided in the embodiments of this application can be referred to the relevant descriptions of the method embodiments of this application. The method embodiments and the device embodiments can also be referenced, combined or cited from each other.

[0243] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A method for updating configuration information in an SIB1 request, characterized in that, The method includes: Receive a first message, the first message including first indication information and first configuration information, the first indication information instructing SIB1 to request configuration information update, the first configuration information being used to configure SIB1 to request configuration information; Based on the first indication information, the configuration information used to configure the SIB1 request is updated to the first configuration information.

2. The method according to claim 1, characterized in that, The first message is the first SIB.

3. The method according to claim 2, characterized in that, The first SIB is SIB1.

4. The method according to claim 3, characterized in that, The control information candidate resources of the first SIB are indicated by information in the SSB.

5. The method according to any one of claims 1-4, characterized in that, The first configuration information includes the SIB1 request configuration information of this cell, or it includes the SIB1 request configuration information of neighboring cells.

6. A method for updating configuration information in an SIB1 request, characterized in that, The method includes: Send a first message, which includes first indication information and first configuration information. The first indication information indicates that SIB1 requests configuration information updates, and the first configuration information is used to configure SIB1 to request configuration information.

7. The method according to claim 6, characterized in that, The first message is the first SIB.

8. The method according to claim 7, characterized in that, The first SIB is SIB1.

9. The method according to claim 8, characterized in that, The control information candidate resources of the first SIB are indicated by information in the SSB.

10. The method according to any one of claims 6-9, characterized in that, The first configuration information includes the SIB1 request configuration information of this cell, or it includes the SIB1 request configuration information of neighboring cells.

11. A method for updating configuration information in an SIB1 request, characterized in that, The method includes: Send a second message, the second message being used to request second configuration information, the second configuration information being used to configure SIB1 request configuration information; Receive the second configuration information.

12. The method according to claim 11, characterized in that, The second message is either a preamble sequence or Msg1.

13. The method according to claim 11 or 12, characterized in that, The transmission resources of the second configuration information are indicated by a third message, or the second configuration information is carried in the third message; The third message is either a random access response (RAR), Msg2, or a second SIB.

14. The method according to claim 13, characterized in that, The third message is the second SIB, and the transmission information of the second SIB is obtained through the SSB.

15. The method according to claim 14, characterized in that, The SSB can be the first SSB opportunity after the fourth message and the SSB transmitted thereafter, or the SSB can be the SSB transmitted within the first complete SSB cycle after the fourth message and the SSB transmitted thereafter, or the SSB can be the first SSB opportunity after the window corresponding to the fourth message and the SSB transmitted thereafter, or the SSB can be the SSB transmitted within the first complete SSB cycle after the window corresponding to the fourth message and the SSB transmitted thereafter.

16. The method according to claim 15, characterized in that, The fourth message is a random access response (RAR) or Msg2.

17. A method for updating configuration information in an SIB1 request, characterized in that, The method includes: Receive a second message, the second message being used to request second configuration information, the second configuration information being used to configure SIB1 request configuration information; Send the second configuration information.

18. The method according to claim 17, characterized in that, The first message is either a preamble sequence or Msg1.

19. The method according to claim 17 or 18, characterized in that, The transmission resources of the second configuration information are indicated by a third message, or the second configuration information is carried in the third message; The third message is either a random access response (RAR), Msg2, or a second SIB.

20. The method according to claim 19, characterized in that, The third message is the second SIB, and the transmission information of the second SIB is obtained through the SSB.

21. The method according to claim 20, characterized in that, The SSB can be the first SSB opportunity after the fourth message and the SSB transmitted thereafter, or the SSB can be the SSB transmitted within the first complete SSB cycle after the fourth message and the SSB transmitted thereafter, or the SSB can be the first SSB opportunity after the window corresponding to the fourth message and the SSB transmitted thereafter, or the SSB can be the SSB transmitted within the first complete SSB cycle after the window corresponding to the fourth message and the SSB transmitted thereafter.

22. The method according to claim 21, characterized in that, The fourth message is a random access response (RAR) or Msg2.

23. A communication device, characterized in that, Includes units for performing the method as described in any one of claims 1 to 22.

24. A communication device, characterized in that, It includes a processor and a memory, the processor and the memory being coupled, the processor being used to implement the method as described in any one of claims 1 to 22.

25. A chip, characterized in that, The device includes a processor and an interface, wherein the processor and the interface are coupled; the interface is used to receive or output signals, and the processor is used to execute code instructions to cause the method of any one of claims 1 to 22 to be performed.

26. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when invoked, cause the computer to perform the method described in any one of claims 1 to 22.

Images