Information receiving apparatus and information sending apparatus

Abstract

The present application provides an information receiving apparatus and an information sending apparatus. The information receiving apparatus comprises: a receiver, which receives in a first cell first related information of at least one second cell, and acquires in the first cell at least one piece of first information, the first information comprising system information block type 1 (SIB1) of the at least one second cell.

Description

Information receiving apparatus and information transmitting apparatus TECHNICAL FIELD

[0001] Embodiments of the present application relate to the technical field of wireless communication. BACKGROUND

[0002] In the 5th Generation Mobile Communication Technology (5G) network standardized by the 3rd Generation Partnership Project (3GPP), a large number of NR (New Radio) base stations are deployed. The NR base station needs to work in a large bandwidth (such as 100MHz), needs to use a large number of ports (64T / 64R) and a shorter TTI (1ms), and the energy consumption of the NR base station in baseband processing, digital front-end and other functions is significantly higher than that of the LTE base station.

[0003] According to the data statistics of the operator, the average energy consumption of an NR base station is more than three times that of an LTE base station, and nearly 50% of the cost of deploying a 5G network by the operator is the electricity cost. More importantly, even in the time period without service, the energy consumption of the NR base station is still large, because even when there is no service, the NR base station still needs to send public signals such as Synchroniztion Singnal Block (SSB), System Information Block (SIB, such as SIB1), System Information (SI) and Paging, etc., thereby greatly reducing the energy use efficiency of the NR base station. NR network energy saving is a problem to be solved. In addition, in the future network (such as 6G or later network), the problem of network energy saving also needs to be solved.

[0004] It should be noted that the above introduction to the technical background is only for the convenience of clearly and completely describing the technical solutions of the present application, and facilitating the understanding of those skilled in the art. The above technical solutions cannot be considered as known to those skilled in the art only because they are described in the background section of the present application.

[0005] SUMMARY

[0006] 3GPP Release 19 studies procedures and signaling methods to support on-demand System Information Block Type One (SIB1) for terminal devices in idle or inactive mode, thus, there are cells (e.g. NES cells) that support or use on-demand SIB1 different from the traditional cells. Secondary cells of a NES cell can be used to assist the on-demand SIB1 procedure of the NES cell. For example, a terminal device can receive the on-demand SIB1 of a NES cell from a secondary cell. The inventors found that in the case where one secondary cell can provide the on-demand SIB1 of multiple NES cells, the terminal device cannot identify which NES cell’s on-demand SIB1 is included in the information sent by the secondary cell, and thus cannot determine whether the information sent by the secondary cell contains the on-demand SIB1 of the NES cell it requested.

[0007] To address the above problems or other similar problems, an embodiment of the present application provides an information receiving apparatus and an information sending apparatus.

[0008] According to an aspect of an embodiment of the present application, an information receiving apparatus is provided, which is applied / configured to a terminal device, and the apparatus comprises:

[0009] a receiver configured to receive first related information of at least one second cell in a first cell; and

[0010] obtain at least one first information in the first cell, the first information comprising System Information Block Type One (SIB1) of the at least one second cell.

[0011] According to another aspect of an embodiment of the present application, an information sending apparatus is provided, which is applied / configured to a first network device, and the apparatus comprises:

[0012] a transmitter configured to send at least one first information in a first cell, the first information comprising System Information Block Type One (SIB1) of at least one second cell.

[0013] The beneficial effects of embodiments of the present application include:

[0014] A terminal device can receive first related information of at least one second cell in a first cell, and obtain at least one first information in the first cell, the first information comprising System Information Block Type One (SIB1) of the at least one second cell. Thus, according to the first related information, the terminal device can determine which SIB1 of the second cell is included in the first information, to obtain the SIB1 of the second cell it requested.

[0015] The particular implementations of the application described in detail below are illustrative only and are not intended to limit the scope of the application. Numerous variations, either to details of the implementations or to the general principles described herein, can be made by those skilled in the art without departing from the scope of the application. Reference should be made to the appended claims for an indication of the scope of the application.

[0016] Features described and / or illustrated with respect to one implementation can be used in one or more other implementations in the same or similar manner, in combination with or in place of features in other implementations, or in some cases, in place of some features of the other implementations.

[0017] It should be emphasized that the term "comprises / comprising" when used in this specification is taken to mean the presence of stated features, integers, steps or components but does not preclude the presence or addition of one or more other features, integers, steps, components or groups thereof. BRIEF DESCRIPTION OF DRAWINGS

[0018] Elements and features of one or more embodiments described in the specification and / or one or more figures can be combined with elements and features of one or more other embodiments or figures, or with other current or developing technologies, to produce yet further embodiments.

[0019] The accompanying drawings are included to provide a further understanding of embodiments of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the principles of the application. It is to be understood that the drawings are for purposes of illustration only and that the figures are not necessarily drawn to scale, with the understanding that:

[0020] FIG. 1 is a schematic diagram of a communication system according to an embodiment of the application;

[0021] FIG. 2 is a deployment scenario of a NES cell according to an embodiment of the application;

[0022] FIG. 3 is a scenario for on-demand SIB1 according to an embodiment of the application;

[0023] FIG. 4 is another scenario for on-demand SIB1 according to an embodiment of the application;

[0024] FIG. 5 is a schematic diagram of a method for receiving information according to an embodiment of the application;

[0025] FIG. 6 is a schematic diagram of a process for acquiring Msg1-based on-demand SIB1 according to an embodiment of the application;

[0026] FIG. 7 is a schematic diagram of a process of acquiring Msg3-based on-demand SIB1 according to an embodiment of the present application;

[0027] FIG. 8 is a schematic diagram of a process of acquiring Msg1-based on-demand SIB1 in combination with acquiring Msg3-based on-demand SIB1 according to an embodiment of the present application;

[0028] FIG. 9 is a schematic diagram of a method of transmitting information according to an embodiment of the present application;

[0029] FIG. 10 is a schematic diagram of a method of transmitting information according to an embodiment of the present application;

[0030] FIG. 11 is a schematic diagram of an information receiving apparatus according to an embodiment of the present application;

[0031] FIG. 12 is a schematic diagram of an information transmitting apparatus according to an embodiment of the present application;

[0032] FIG. 13 is a schematic diagram of an information transmitting apparatus according to an embodiment of the present application;

[0033] FIG. 14 is a schematic diagram of a configuration of a communication system according to an embodiment of the present application;

[0034] FIG. 15 is a schematic diagram of a configuration of a terminal device according to an embodiment of the present application;

[0035] FIG. 16 is a schematic diagram of a configuration of a network device according to an embodiment of the present application;

[0036] FIG. 17 is a schematic diagram of a method of transmitting information according to an embodiment of the present application;

[0037] FIG. 18 is a schematic diagram of a method of transmitting information according to an embodiment of the present application. DETAILED DESCRIPTION

[0038] The foregoing and other features of the present application will become more apparent from the following description of the application, when taken in conjunction with the accompanying drawings. In the drawings, specific embodiments of the application are illustrated, which show, by way of example only, the principles of the application. As will be realized by those skilled in the art, the application is not limited to the embodiments described herein, which are presented as examples of the principles of the application. The application includes all modifications, variations, and equivalents that fall within the scope of the appended claims. Various embodiments of the present application will now be described with reference to the accompanying drawings. These embodiments are presented by way of example only, and are not intended to limit the scope of the application.

[0039] In the embodiments of the present application, the terms "first", "second" and the like are used to distinguish different elements from each other, but do not indicate spatial arrangement or time sequence of the elements, and the elements should not be limited by these terms. The term "and / or" includes any one and all combinations of the associated listed terms. The terms "comprise", "include", "have" and the like mean the presence of the stated features, elements, elements or components, but do not exclude the presence or addition of one or more other features, elements, elements or components.

[0040] In the embodiments of the present application, the singular form "a", "an" and the like includes the plural form, should be broadly understood as "one" or "a kind of", and not limited to the meaning of "one"; in addition, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. In addition, the term "according to" should be understood as "at least partially according to", and the term "based on" should be understood as "at least partially based on", unless the context clearly indicates otherwise.

[0041] In the embodiments of the present application, the term "communication network" or "wireless communication network" can refer to a network that complies with any communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), and the like.

[0042] In addition, the communication between devices in the communication system can be carried out according to any stage communication protocol, which can include but is not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), 6G and future communication, and the like, and / or other currently known or future to be developed communication protocols.

[0043] In the embodiments of the present application, the term "network device" refers to, for example, a device that accesses a terminal device to a communication network and provides services for the terminal device in a communication system. The network device can include, but is not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), and the like.

[0044] Wherein, the base station can include, but is not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), 5G base station (gNB), 6G base station, and future base station, etc., and can also include remote radio head (RRH), remote radio unit (RRU), relay, or low-power node (such as femto, pico, etc.). And the term "base station" can include some or all functions of them, and each base station can provide communication coverage for a specific geographic area. The term "cell" can refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0045] In the embodiments of the present application, the term "user equipment" (UE) or "terminal equipment" (TE) refers to, for example, a device that accesses a communication network through a network device and receives network services. The user equipment can be fixed or mobile, and can also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT) station, etc.

[0046] Wherein, the terminal device can include, but is not limited to, the following devices: cellular phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, machine type communication device, laptop computer, cordless phone, smart phone, smart watch, digital camera, XR device, etc.

[0047] For another example, in scenarios such as Internet of Things (IoT), a user equipment can also be a machine or device performing monitoring or measurement, for example, can include but not limited to: Machine Type Communication (MTC) terminal, vehicle-mounted communication terminal, Device to Device (D2D) terminal, Machine to Machine (M2M) terminal, terminal supporting sidelink communication, terminal supporting XR service, etc.

[0048] In addition, the term "network side" or "network device side" refers to the side of the network, which can be a certain base station, or can include one or more network devices as above. The term "user side" or "terminal side" or "terminal device side" refers to the side of the user or terminal, which can be a certain UE, or can include one or more terminal devices as above. In this article, "device" can refer to network device or terminal device without special indication.

[0049] The terms "uplink control signal" and "uplink control information (UCI)" or "physical uplink control channel (PUCCH)" can be interchangeable without causing confusion, and the terms "uplink data signal" and "uplink data information" or "physical uplink shared channel (PUSCH)" can be interchangeable;

[0050] The terms "downlink control signal" and "downlink control information (DCI)" or "physical downlink control channel (PDCCH)" can be interchangeable, and the terms "downlink data signal" and "downlink data information" or "physical downlink shared channel (PDSCH)" can be interchangeable.

[0051] In addition, the uplink signal can include an uplink data signal and / or an uplink control signal and / or a PRACH and / or an SRS, etc., and can also be referred to as an uplink transmission (UL transmission) or uplink information or an uplink channel. Transmitting / receiving the uplink transmission on the uplink resource can be understood as transmitting / receiving the uplink transmission using the uplink resource. The downlink signal can include a downlink data signal and / or a downlink control signal and / or a synchronization signal (SS, for example, PSS / SSS) and / or a broadcast channel (PBCH) and / or an SSB (SS / PBCH block, including PSS, SSS, and PBCH and its DMRS) and / or a CSI-RS, etc., and can also be referred to as a downlink transmission (DL transmission) or downlink information or a downlink channel. Transmitting / receiving the downlink transmission on the downlink resource can be understood as transmitting / receiving the downlink transmission using the downlink resource. In the embodiments of the present application, the higher layer signaling can be, for example, radio resource control (RRC) signaling; the RRC signaling can include, for example, an RRC message, such as a broadcast / common RRC message / signaling (for example, a Master Indication Block (MIB), system information (SI), a dedicated RRC message / signaling; or an RRC information element (RRC IE); or an information field included in the RRC message or the RRC information element (or an information field included in the information field). The higher layer signaling can also be, for example, medium access control layer (MAC) signaling; or a MAC control element (MAC CE). However, the present application is not limited thereto.

[0052] In the embodiments of the present application, "at least one" and "one or more than one" can be interchangeable, "a plurality of" and "more than one" can be interchangeable, and "a plurality of" means at least two, or two or more than two.

[0053] In the embodiments of the present application, pre-defined means defined by a protocol or determined according to a rule defined by the protocol, without additional configuration. Configuration / indication means direct or indirect configuration / indication by the network device through higher layer signaling and / or physical layer signaling. The configuration / indication can be configured / indicated by introducing a higher layer parameter in the higher layer signaling, and the higher layer parameter means a field and / or an information element / unit / element (IE) in the higher layer signaling. The physical layer signaling can be, for example, control information (DCI) carried by a physical downlink control channel or control information carried by a sequence, but is not limited thereto.

[0054] In embodiments of the present application, network device configuration, for example, includes network device pre-configuration and network device dynamic indication. Network device pre-configuration is pre-configured, for example, through high layer signaling (e.g., RRC signaling); network device dynamic indication is dynamically indicated, for example, through physical layer signaling (e.g., DCI and / or MAC CE).

[0055] In embodiments of the present application, a cell supporting or using on-demand SIB1 can also be referred to as a Network Energy Saving (NES) cell or a power saving cell or a special cell or a cell transmitting simplified signals or a special type of energy saving cell or the like. Similarly, a cell supporting or using on-demand SIB1 can also be referred to as the cell being a NES cell or the cell being a power saving cell or the cell being a special cell or the cell being a cell transmitting simplified signals or the cell being a special type of energy saving cell or the cell entering an energy saving mode (or an energy saving state or the like).

[0056] In embodiments of the present application, a cell not supporting or using on-demand SIB1 can also be referred to as a legacy cell or a normal cell or a non-NES cell or the like. Similarly, a cell not supporting or using on-demand SIB1 can also be referred to as the cell not being a NES cell or the cell not being a power saving cell or the cell not being a special cell or the cell not being a cell transmitting simplified signals or the cell not being a special type of energy saving cell or the cell not entering an energy saving mode (or an energy saving state or the like).

[0057] In embodiments of the present application, a terminal device supporting on-demand SIB1 can also be referred to as a Network Energy Saving (NES) terminal device or a terminal device supporting network energy saving or a terminal device with NES capability or a special terminal device or a terminal device receiving simplified signals or a special type of terminal device or the like.

[0058] In embodiments of the present application, a terminal device not supporting on-demand SIB1 can also be referred to as a legacy terminal device or a normal terminal device or a normal terminal device or a terminal device before Release 19 or a non-NES terminal device or a terminal device without NES capability or the like.

[0059] In embodiments of the present application, camping on a cell can also be expressed as normally camping on the cell or temporarily camping on the cell or cell selection to the cell or cell reselection to the cell or considering the cell as a suitable cell or considering the cell as an acceptable cell or the like.

[0060] In the embodiments of this application, the "Wake Up Signal (WUS)" may also be referred to as "Uplink Wake Up Signal (UL WUS)", "Uplink Request Signal", "Uplink Activation Signal", "UE Wake Up Signal", "Physical Random Access Channel (PRACH)", "Random Access Channel", "Random Access Preamble", "Random Access Message 3 (Msg 3)", "Random Access Message 1 (Msg.1)", "Random Access Message A (MsgA)" and similar names.

[0061] In the embodiments of this application, "sending / receiving on the first cell" can also be understood as "sending / receiving by the network device to which the first cell belongs," or it can be simply referred to as "sending / receiving from the first cell." "Receiving," "acquiring," and "detecting" can be used interchangeably. Furthermore, the phrase "on the first cell..." in this application can also be replaced with "in the first cell...", "from the first cell...", or similar expressions.

[0062] For ease of description, the following description uses a base station as an example of an access network device. In the following description, without causing confusion, "if...", "in the case of...", and "when..." can be used interchangeably.

[0063] The following examples illustrate the scenarios of embodiments of this application, but this application is not limited thereto.

[0064] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application, illustrating the case of a terminal device and a network device as examples. As shown in Figure 1, the communication system 100 may include a network device 101, a terminal device 102, and a terminal device 103. For simplicity, Figure 1 only illustrates the case of two terminal devices and one network device, but the embodiments of this application are not limited to this.

[0065] In this embodiment, network device 101, terminal device 102, and terminal device 103 can transmit existing services or services that may be implemented in the future. For example, these services may include, but are not limited to: enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), ultra-reliable and low-latency communication (URLLC), Internet of Things (IoT) communication, and related communication of terminal devices with reduced capabilities, etc.

[0066] Terminal devices 102 and 103 can communicate with network device 101. For example, taking terminal device 102 as an example, terminal device 102 can send data to network device 101, such as using dynamic authorization or configured authorization transmission methods. Network device 101 can receive data sent by one or more terminal devices 102 and provide feedback or uplink scheduling information to terminal device 102, such as ACK / NACK confirmation information or uplink new transmission or retransmission scheduling information. Based on the feedback or uplink scheduling information, terminal device 102 can confirm the end of the transmission process, or can initiate new data transmission, or can retransmit data. Network device 101 can also send data to terminal device 102, and terminal device 102 can receive data sent by network device 101. In addition, different terminal devices can also communicate with each other; for example, terminal device 102 and terminal device 103 can exchange data.

[0067] It is worth noting that Figure 1 shows that both terminal device 102 and terminal device 103 are within the coverage area of ​​network device 101, but this application is not limited to this. Terminal device 102 and terminal device 103 may both be outside the coverage area of ​​network device 101, or one of terminal device 102 and terminal device 103 may be within the coverage area of ​​network device 101 while the other is outside the coverage area of ​​network device 101.

[0068] Figure 2 illustrates a deployment scenario of an NES cell according to an embodiment of this application. As shown in Figure 2, for example, an NES cell is co-deployed with a coverage-providing cell, which can also be referred to as an anchor cell, Cell A, an auxiliary cell, or a neighboring cell, to assist the on-demand SIB1 process of the NES cell. The NES cell can provide network capacity. As another example, an NES cell is co-deployed with its neighboring cells, and these cells can have completely overlapping, partially overlapping, or non-overlapping coverage areas. In Figure 2, communication can occur between the NES cell and the anchor cell, between the NES cell and its neighboring cells, and between the anchor cell and its neighboring cells, for example, through the X2 interface or the F1 interface.

[0069] It is worth noting that Figure 2 shows one terminal device in an NES cell, but this application is not limited to this; there can be more than one terminal device (UE) in an NES cell. Furthermore, Figure 2 shows the terminal device within the coverage area of ​​the NES cell, but this application is not limited to this; the terminal device can also be outside the coverage area of ​​the NES cell. In addition, in Figure 2, the anchor cell can also be deployed together with one or more NES cells, and one or more anchor cells can provide auxiliary information to an NES cell. An NES cell can have one or more neighboring NES cells, or it can have no neighboring NES cells; this application does not impose any restrictions on this.

[0070] In another deployment scenario of NES cells, the NES cell is deployed independently, and there can be more than one terminal device (UE) in the NES cell. The terminal device can be within or outside the coverage area of ​​the NES cell, but this application is not limited to this.

[0071] One of the working objectives of 3GPP Release 19, as shown in Table 1 below, is to study the process and signaling methods to support on-demand SIB1 for UEs in idle / inactive mode, including: triggering methods for uplink wake-up signals using existing signals / channels; providing the UE with the configuration of the wake-up signal; and exchanging wake-up signal configuration information between gNBs (if necessary).

[0072] Table 1

[0073] Currently, 3GPP RAN2 has agreed on relevant scenarios regarding on-demand SIB1. Figure 3 illustrates one scenario of on-demand SIB1 according to an embodiment of this application, specifically scenario 1a. As shown in Figure 3, in scenario 1a, the terminal device obtains the WUS configuration from the anchor cell, sends the WUS to the NES cell, and receives on-demand SIB1 from the NES cell. The agreed-upon details are shown in Table 2 below:

[0074] Table 2

[0075] In addition, 3GPP RAN1 agreed to continue studying on-demand SIB1 for terminal equipment in idle / inactive mode under the following three cases:

[0076] Case 1: The UE obtains the WUS configuration from the NES cell, sends the WUS to the NES cell, and receives on-demand SIB1 from the NES cell;

[0077] Case 2: The UE obtains the WUS configuration from the anchor cell, sends the WUS to the NES cell, and receives on-demand SIB1 from the NES cell, corresponding to scenario 1a where RAN2 agrees;

[0078] Case 3: The UE obtains WUS configuration information from the anchor cell, sends WUS to the anchor cell, and receives on-demand SIB1 from the NES cell from the anchor cell, corresponding to the scenario in Figure 4.

[0079] In scenario three, where an anchor cell provides WUS configuration information for multiple NES cells, the UE cannot currently identify which NES cell(s)'s on-demand SIB1 is included in the information sent by the anchor cell. Therefore, it cannot determine whether the information sent by the anchor cell contains the on-demand SIB1 of the requested NES cell.

[0080] To address at least one of the above-mentioned problems, embodiments of this application provide an information receiving method, an information sending method, an apparatus, and a communication system.

[0081] First aspect of the embodiments

[0082] This application provides an information receiving method, which will be described from the perspective of a terminal device.

[0083] Figure 5 is a schematic diagram of an information receiving method according to an embodiment of this application. The method is applied to a terminal device. As shown in Figure 5, the method includes:

[0084] 501, The terminal device receives at least one first relevant information from a second cell in the first cell;

[0085] 502, The terminal device obtains at least one first piece of information in the first cell, the first piece of information including System Information Block Type 1 (SIB1) of the at least one second cell.

[0086] According to the above embodiments, the terminal device can receive first related information of at least one second cell in the first cell, and obtain at least one piece of first information in the first cell. The first information may include System Information Block Type 1 (SIB1) of the at least one second cell. Thus, based on the first related information, the terminal device can determine which SIB1(s) of the second cell(s) is included in the first information, and obtain the SIB1(s) of the requested second cell.

[0087] It is worth noting that Figure 5 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 5 above.

[0088] In some embodiments, the terminal device (UE) includes a terminal device in an RRC idle (RRC_IDLE) state or an RRC inactive (RRC_INACTIVE) state.

[0089] In some embodiments, the second cell is a cell that supports or uses on-demand SIB1, and may also be referred to as an NES cell or other similar names. Since the second cell is an NES cell, the System Information Block #1 (SIB1) of the second cell may also be referred to as the on-demand SIB1 of the second cell or other names.

[0090] In some embodiments, the first cell may be referred to as an anchor cell, Cell A, an auxiliary cell, or a neighboring cell, to assist the on-demand SIB1 process of the second cell. The first cell may also be used to provide network coverage.

[0091] In some embodiments, the terminal device is currently camped in a first cell. The UE can measure neighboring cells according to the configuration in the system information of the first cell. The UE detects the synchronization signal block (SSB) of a neighboring third cell and obtains the second relevant information of the third cell based on the PSS (primary synchronization signal) and SSS (secondary synchronization signal) in the SSB. The second relevant information includes the physical cell identity (PCI) and / or frequency information (e.g., the absolute radio channel number (ARFCN) of the SSB). Since the third cell does not broadcast SIB1 or the UE does not obtain the SIB1 of the third cell, and the UE knows that the PCI and frequency information correspond to a third cell, the method may further include (not shown) the terminal device sending a wake-up signal (WUS) to the first cell to request on-demand SIB1 of at least one third cell. The third cell is a cell that supports or uses on-demand SIB1. This third cell can be a cell among at least one of the second cells included in the WUS configuration information sent by the network device (e.g., the first cell), or a cell among at least one of the second cells included in the first information sent by the network device (e.g., the first cell), or a cell different from the second cell included in the first information sent by the network device (e.g., the first cell). The wake-up signal can be Msg.1 (e.g., PRACH preamble), message A (Msg.A, e.g., including Preamble and PUSCH), or an RRC system information request message in Msg.3. This wake-up signal can implicitly or explicitly indicate at least one third cell (second related information), that is, based on this wake-up signal, it can be determined which or which third cells' on-demand SIB1 the terminal device requests. How to implicitly or explicitly indicate at least one third cell, and how to send the wake-up signal, will be explained later in conjunction with Figures 6 to 8.

[0092] In some embodiments, after receiving a wake-up signal, the network device of the first cell determines, based on the wake-up signal, which or more third cells' on-demand SIB1 the terminal device requests. It can then send (broadcast) at least one first message to carry the SIB1 of at least one second cell. The SIB1 of the at least one second cell includes the SIB1 of at least one third cell, and optionally may also include the SIB1 of at least one fourth cell requested by other terminal devices. This fourth cell is a cell that supports or uses on-demand SIB1, or the SIB1 of the at least one second cell does not include the SIB1 of the third cell. The number of first messages obtained by the terminal device in the first cell can be one or more. One first message can indicate one or more System Information Block Type 1 (SIB1) of the second cell. For example, a first message can contain one or more SIB1s of the second cell, and the SIB1 of the second cell can be on-demand System Information Block Type 1 (SIB1).

[0093] In some embodiments, the first information may be a System Information Block (SIB) of the first cell. The SIB may be an existing system information block in the system information, or it may be a system information block that will be added to the system information in the future. For example, the first information may be a system information block (e.g., SIBx, where x can be 2, 3, 26, or greater than 26, etc.). Of course, the embodiments of this application are not limited to this; the first information may also be a Radio Resource Control (RRC) message (e.g., an RRC release message) of the first cell. The following embodiments will be described using an example where the first information is an SIB (SIBx).

[0094] In some embodiments, in order to distinguish which SIB1 of which second cell(s) is carried by at least one first information, the terminal device receives at least one first related information of the second cell in the first cell. The first related information includes physical cell identity (PCI) and / or frequency information. The first related information may be included in the aforementioned first information, or it may be included in second information that is different from the first information, or it may be included in the same message as the first information. These will be described separately below.

[0095] In some embodiments of this example, a first piece of information may include one or more System Information Block Type 1 (SIB1) of a second cell. One or more first-related information of a second cell may be included in a first piece of information. In the first piece of information, the first-related information of a second cell may correspond to, be associated with, or be related to the SIB1 of that second cell. Thus, the first piece of information can indicate the correspondence or association between the first-related information of the second cell and the SIB1 of the second cell. The terminal device can identify, based on the first piece of information, which or which second cells' System Information Block Type 1 (SIB1) specifically the first piece of information belongs to. Therefore, the terminal device can determine whether to obtain the on-demand SIB1 of the NES cell it requested. For example, the first piece of information (SIBx-r19) can be represented using ASN.1 as follows:

[0096] The first information may include SIB1 (SIB1-r19) of 1 to maxNrofNEScell-r19 second cells, and may also include first related information (physCellId-r19) of 1 to maxNrofNEScell-r19 second cells. physCellId-r19 and SIB1-r19 correspond one-to-one and are included in the information element SIB1Info-r19 of the same second cell.

[0097] The following explains how, in the above embodiments, the terminal device determines from which first cell to obtain the on-demand SIB1 of the third cell it requests.

[0098] In some embodiments, a first cell may indicate to a terminal device which second cells it provides on-demand SIB1 for. After detecting the SSB of a third cell, the terminal device wants to obtain the on-demand SIB1 of the third cell. If the third cell is one of the at least one of the second cells indicated above, the terminal device obtains the SIB1 of the third cell from the first cell and distinguishes which cell's SIB1 the SIB1 carried by the first information belongs to based on the first relevant information in the first information. In other words, it determines whether the SIB1 carried by the first information includes the SIB1 of the requested third cell based on the first relevant information in the first information.

[0099] As some implementations, the first cell can provide WUS configuration information (which may include the PCI and / or frequency information of the at least one second cell) to at least one second cell. The terminal device considers that the first cell providing the WUS configuration information provides on-demand SIB1 for these second cells, or the terminal device obtains the on-demand SIB1 of the at least one second cell from the first cell that provided the WUS configuration information. For example, if the terminal device is within the coverage of the first cell and receives WUS configuration information provided for at least one second cell from the first cell, and the terminal device wants to obtain the on-demand SIB1 of the third cell after detecting the SSB of the third cell, if the third cell is one of the at least one second cell, the terminal device obtains the SIB1 of the third cell from the first cell.

[0100] As some implementations, the first cell may indicate the PCI and / or frequency information of at least one second cell in its system information (e.g., SIB1, SIB3, SIB4, or other SIBs, system information different from the first information). When the terminal device is located within the coverage of the first cell and receives the above indication from the first cell, after detecting the SSB of the third cell, the terminal device wants to obtain the on-demand SIB1 of the third cell. If the third cell is one of the at least one second cell, the terminal device obtains the SIB1 of the third cell from the first cell.

[0101] In other embodiments of this example, the terminal device may also obtain second information from the first cell. The first related information is included in the second information. The second information may include scheduling information for one or more pieces of first information, which is carried by the SIB1 of the first cell. The scheduling information may include at least one of the following: time window length, broadcast status of the first information, period for transmitting the first information, and mapping information. The position of the transmission time window of the first information can be determined based on the scheduling information. A piece of first information (SI / SIBx) may contain a System Information Block Type 1 (SIB1) of a second cell.

[0102] In some examples, the first information within the time window indicated by different scheduling information corresponds to the SIB1 of different second cells. The first related information of a second cell corresponds (is related to or associated with) the scheduling information carrying the first information of the SIB1 of that second cell. For example, the first related information PCI m of a second cell is indicated in the Xth scheduling information, and the first related information PCI n of the next second cell is indicated in the X+1th scheduling information. For example, this second information (SI-SchedulingInfo-r19) can be represented using ASN.1 as Example 1:

[0103] The second information may include 1 to maxSI-Message scheduling information SchedulerInfo3-r19 and a time window length SI-WindowLength. That is, for the 1 to maxSI-Message scheduling information SchedulerInfo3-r19, the same time window length SI-WindowLength is configured. Each scheduling information SchedulerInfo3-r19 includes at least one of the broadcast status (si-BroadcastStatus-r19), the period for sending the first information (si-Periodicity-r19), and mapping information (sib-MappingInfo-r19) of the first information, as well as the first related information of the second cell (physCellId-r19). physCellId-r19 and SchedulerInfo3-r19 correspond one-to-one. Different SchedulerInfo3-r19 may correspond to different time window positions of system information. Therefore, the first information obtained in the time window determined by ScheduleInfo3-r19 and SI-WindowLength corresponds to the first information of physCellId-r19 in ScheduleInfo3-r19.

[0104] In other specific examples, different types of first information correspond to different SIB1s of second cells. The first related information of a second cell corresponds (is related to or associated with) the type information of the first information carrying the SIB1 of that second cell. For example, the scheduling information includes system information block type information (SIB-TypeInfo), which can indicate in the sib-MappingInfo IE corresponding to SIBx that the physical cell identifier corresponding to or related to system information block x (SIBx) is m. It can indicate in the sib-MappingInfo IE corresponding to SIBx+1 that the physical cell identifier corresponding to or related to system information block x+1 (SIBx+1) is n. For example, this second information (SI-SchedulingInfo-r19) can be represented using ASN.1 as Example 2:

[0105] The second information may include 1 to maxSI-Message scheduling information SchedulerInfo3-r19 and a time window length SI-WindowLength. That is, for the above 1 to maxSI-Message scheduling information SchedulerInfo3-r19, the same time window length SI-WindowLength is configured. Each scheduling information SchedulerInfo3-r19 includes at least one of the following: the broadcast status of the first information (si-BroadcastStatus-r19), the period for sending the first information (si-Periodicity-r19), and mapping information (sib-MappingInfo-r19). The mapping information includes system information block type information (SIB-TypeInfo). The system information block type information also includes the first related information of the second cell (physCellId-r19). physCellId-r19 and SIB-TypeInfo are one-to-one correspondences. Different SIB-TypeInfos correspond to different first related information of the second cell. Therefore, the first information of type SIB-TypeInfo obtained in the time window determined by ScheduleInfo3-r19 and SI-WindowLength is the first information of physCellId-r19 in that SIB-TypeInfo.

[0106] The following explains how, in the above implementation (Example 1 or Example 2), the terminal device determines from which first cell to obtain the on-demand SIB1 of the requested third cell.

[0107] In some embodiments, since the second information includes first related information of at least one second cell, the terminal device obtains the first related information from the first cell. The first related information can determine which second cells the first cell provides on-demand SIB1 for, or in other words, it is used to determine from which first cell to obtain the on-demand SIB1 of the requested third cell. After detecting the SSB of the third cell, the terminal device wants to obtain the on-demand SIB1 of the third cell. If the third cell is one of the at least two second cells indicated by the first related information, the terminal device obtains the SIB1 of the third cell from the first cell that provides the first related information, and distinguishes which cell's SIB1 the subsequently obtained first information carries according to the first related information, or in other words, determines whether the SIB1 the subsequently obtained first information carries includes the SIB1 of the requested third cell according to the first related information.

[0108] In some embodiments, in addition to the first relevant information, the first cell may also indicate to the terminal device in other system information (e.g., SIB3 or SIB4 or other SIBs) or in WUS configuration information which second cells the first cell provides on-demand SIB1 for. For example, when the terminal device is within the coverage of the first cell and receives WUS configuration information or SIB3 or SIB4 provided for at least one second cell from the first cell, after detecting the SSB of the third cell, the terminal device wants to obtain the on-demand SIB1 of the third cell. If the third cell is one of the at least one second cell mentioned above, the terminal device obtains the SIB1 of the third cell from the first cell that provides the WUS configuration information or SIB3 or SIB4.

[0109] In some embodiments, the on-demand SIB1 acquisition process of the second cell can be a Msg1-based on-demand SIB1 acquisition process, a Msg3-based on-demand SIB1 acquisition process, or a combination of Msg1-based and Msg3-based on-demand SIB1 acquisition processes. These will be described separately below.

[0110] (I) Msg1-based on-demand SIB1 acquisition process

[0111] Figure 6 is a schematic diagram of the acquisition process of Msg1-based on-demand SIB1 according to an embodiment of this application. As shown in Figure 6, the acquisition process of Msg1-based on-demand SIB1 includes:

[0112] 601, The terminal device obtains the SIB1 of the first cell in the first cell.

[0113] The SIB1 of the first cell indicates the scheduling information (i.e., the second information) of other system information (SIBx). This scheduling information includes, for example, si-RequestConfig or si-RequestConfigSUL, which configures the PRACH preamble and / or PRACH resources corresponding to the SI message where the system information block (SIBx) is located. The PRACH preamble and / or PRACH resources can also be regarded as WUS configuration information, used to indicate the PRACH preamble and / or PRACH resources for sending WUS (Msg.1). The broadcast status (si-BroadcastStatus) related to the system information block (SIBx) is set to, for example, not broadcasting.

[0114] Regarding how to determine which System Information Blocks (SIBx) include the on-demand SIB1 of the second cell:

[0115] When the first relevant information is carried by the first information, the network device of the first cell can determine which SIB(SIBx) to use to send at least one SIB1 of the second cell according to a predefined or preconfigured configuration. For example, predefined SIB2 or SIB2 and SIB3 can carry at least one SIB1 of the second cell. Alternatively, the network device of the first cell can add indication information to the SIB1 to indicate which SIB(SIBx) to send at least one SIB1 of the second cell or to indicate the correspondence between SIBx and the second cell.

[0116] When the first relevant information is carried by the second information, that is, when the scheduling information in 601 also includes the first relevant information, the system information block (SIBx) scheduled by the scheduling information containing the first relevant information includes the on-demand SIB1 of the second cell.

[0117] In addition, the first cell can instruct the terminal device which second cells it provides on-demand SIB1 for.

[0118] 602, The terminal device sends a random access message (Msg.1) to the first cell to request SIB1 of at least one third cell.

[0119] The terminal device can measure neighboring cells based on the configuration of the system information of the first cell. The terminal device can detect the SSB of the neighboring third cell. If the terminal device detects the SSB but does not obtain the SIB1 of the third cell, in order to determine whether the third cell is allowed to camp, the terminal device can initiate an on-demand SIB1 request procedure to request the on-demand SIB1 of the third cell.

[0120] If a first cell indicates to the terminal device which second cells it provides on-demand SIB1 for (e.g., via WUS configuration information or second information carrying first relevant information or other system information SIB1, SIB3, SIB4, or other SIBs different from the first information), and the second cells include a third cell, the terminal device can send a random access message (Msg.1) or message A (Msg.A) (i.e., a wake-up signal) to the first cell to request first information. The first information can be a system information block (SIBx) of the first cell. By requesting the first information, at least one SIB1 of a third cell can be requested. The terminal device can use the preamble and / or resources corresponding to the requested system information block to send the random access message (Msg.1) or message A (Msg.A). For example, the terminal device can use the PRACH preamble and / or PRACH resources configured in si-RequestConfig or si-RequestConfigSUL for the system information block (SIBx) including the on-demand SIB1 of the second cell to send the random access message (SI request for SIBx). When a terminal device requests SIB1 of one or more third cells, it may send a random access message (Msg.1) or message A (Msg.A) using the preamble and / or resources corresponding to the requested system information block and / or resources corresponding to the third cell, to implicitly indicate the requested at least one third cell. Alternatively, the random access message or message A (wake-up signal) may also include second relevant information about at least one third cell to explicitly indicate the requested at least one third cell.

[0121] In some embodiments, the random access message or message A (wake-up signal) may also include information for indicating the system information (block) requested, such as SIB-TypeInfo.

[0122] When the first relevant information is carried by the first information, the terminal device can determine which SIB(SIBx) to request based on predefined or preconfigured information. For example, if SIB2 or SIB2 and SIB3 are predefined to carry at least one SIB1 of a second cell or a third cell, then SIB2 or SIB2 and SIB3 can be requested. Alternatively, the terminal device can determine which SIB(SIBx) to request based on the indication information added to SIB1.

[0123] When the first relevant information is carried by the second information, that is, when the scheduling information in 601 also includes the first relevant information, the system information block (SIBx) scheduled by the scheduling information containing the first relevant information includes the on-demand SIB1 of the second cell or the third cell. Based on this first relevant information, it is determined which SIB(SIBx)(SIBx) is requested.

[0124] 603, The terminal device receives the acknowledgment message sent by the first cell. For details, please refer to the relevant technologies of Msg1-based on-demand SI, which will not be elaborated here.

[0125] Optionally, the terminal device may also receive the SIB1 of the first cell again. In the SIB1 of the first cell received again, the broadcast status (si-BroadcastStatus) related to the system information block (SIBx) is set to, for example, broadcasting.

[0126] 604, The terminal device receives at least one first message in a first cell, the first message including at least one SIB1 of a second cell, including at least one SIB1 of a requested third cell.

[0127] The first information may be a System Information Block (SIBx) of a first cell. The System Information Block (SIBx) includes at least one on-demand SIB1 of a second cell. The third cell may be a cell among at least one of the second cells included in the WUS configuration information sent by the network device (e.g., the first cell), or a cell among at least one of the second cells included in the first information sent by the network device (e.g., the first cell), or a cell different from the second cell included in the first information sent by the network device (e.g., the first cell). Therefore, the terminal device can obtain the on-demand SIB1 of the requested third cell from the System Information Block (SIBx) of the first cell.

[0128] When the first relevant information is carried by the first information, the terminal device obtains the first information and can obtain the on-demand SIB1 of the third cell in at least one second cell's on-demand SIB1 carried by the first information. The first information includes the System Information Block (SIBx) of the first cell. For example, the terminal device can identify whether the second cell corresponding to the first relevant information is the third cell it requests based on the first relevant information indicated in the System Information Block (SIBx); if so, it can obtain the on-demand SIB1 of the requested third cell. If neither is the case, the terminal device considers the request for the on-demand SIB1 of the third cell to have failed or considers the acquisition of the on-demand SIB1 of the third cell to have failed. In this way, the terminal device can identify which second cell's System Information Block Type 1 (SIB1) in the first information belongs to based on the first information. Thus, the terminal device can determine whether it has obtained the on-demand SIB1 of the third cell it requests.

[0129] When the first relevant information is carried by the second information (corresponding to Example 1), the terminal device can obtain a system information block in the time window corresponding to the third cell based on the second information and the first relevant information, thereby obtaining the on-demand SIB1 of the third cell. For example, the terminal device can obtain a system information block (SIBx) in the SI time window related to the requested third cell based on the scheduling information of the system information (block) related to the first relevant information indicated in the SIB1 of the first cell, thereby obtaining the on-demand SIB1 of the third cell. When the SI time window related to the requested third cell corresponds to more than one system information block, the obtained system information block can be the first, the last, or any one of the more than one system information blocks. For example, when the obtained system information block is the first of the more than one system information blocks, the terminal device can choose not to obtain subsequent SIBs within that time window to save overhead.

[0130] When the first relevant information is carried by the second information (corresponding to Example 2), the terminal device can obtain the system information block corresponding to the third cell within the time window corresponding to the third cell based on the second information and the first relevant information, thereby obtaining the on-demand SIB1 of the third cell. For example, the terminal device can obtain the system information block (SIBx) of the third cell within the SI time window related to the requested third cell based on the scheduling information of the system information (block) related to the first relevant information indicated in the SIB1 of the first cell, thereby obtaining the on-demand SIB1 of the third cell. Therefore, the terminal device can directly obtain the on-demand SIB1 of the requested third cell without needing to obtain the on-demand SIB1 of cells requested by other terminal devices, saving overhead.

[0131] In some embodiments, at 604, first information is received, which includes the SIB1 of at least one second cell but does not include the SIB1 of the third cell requested by the terminal device. In this embodiment, if the terminal device considers that requesting the on-demand SIB1 of the third cell has failed or that acquiring the on-demand SIB1 of the third cell has failed, the third cell may be considered to be in a barred state. Alternatively, the terminal device may resend WUS (e.g., random access message one or message A) to request the on-demand SIB1 of the third cell. For example, if the WUS has been sent a maximum number of times without acquiring the on-demand SIB1 of the third cell, the third cell may be considered to be in a barred state.

[0132] In some embodiments, at 604, if the terminal device attempts to receive but does not receive the first information, the terminal device considers that requesting the on-demand SIB1 of the third cell has failed or that acquiring the on-demand SIB1 of the third cell has failed. The terminal device may consider the third cell to be in a barred state, or the terminal device may resend WUS (e.g., random access message one or message A) to request the on-demand SIB1 of the third cell. For example, if the WUS is sent up to the maximum number of times and the on-demand SIB1 of the third cell is not acquired, the terminal device may consider the third cell to be in a barred state.

[0133] (ii) Msg3-based on-demand SIB1 acquisition process.

[0134] Figure 7 is a schematic diagram of the Msg3-based on-demand SIB1 acquisition process. As shown in Figure 7, the Msg3-based on-demand SIB1 acquisition process includes:

[0135] 701, The terminal device obtains the SIB1 of the first cell in the first cell.

[0136] The terminal device can camp on the first cell. The terminal device can receive SIB1 of the first cell. SIB1 of the first cell indicates second information about system information (blocks) within the first cell. The second information includes scheduling information. In the second information, for system information blocks (SIBx) that include SIB1 of the second cell, the broadcast status (si-BroadcastStatus) associated with the system information block (SIBx) is set to, for example, not broadcasting.

[0137] In addition, the first cell can indicate to the terminal device which second cells it provides on-demand SIB1.702 for, and the terminal device sends a random access message (Msg.1) to the first cell.

[0138] The terminal device can measure neighboring cells based on the configuration of the system information of the first cell. The terminal device can detect the SSB of the neighboring third cell. If the terminal device detects the SSB but does not obtain the SIB1 of the third cell, in order to determine whether the third cell is allowed to camp, the terminal device can initiate an on-demand SIB1 request procedure to request the SIB1 of the third cell. If the first cell indicates to the terminal device which second cells it provides on-demand SIB1 for (e.g., through the first relevant information carried in the WUS configuration information or the second information, or other system information SIB1, SIB3, SIB4, or other SIBs different from the first information), and the second cell includes the third cell, the terminal device can send a random access message (Msg.1) to the first cell.

[0139] 703, The terminal device receives the Random Access Response (RAR) sent by the first cell.

[0140] The network equipment in the first cell can receive Random Access Message 1 (Msg.1) sent by the terminal device and can send a Random Access Response to the terminal device. The terminal device can receive the Random Access Message 1 (Msg.1) and its Random Access Response. For information on 702 and 703, please refer to the relevant Msg3-based on-demand SI technologies; details will not be elaborated here.

[0141] 704. The terminal device sends the RRCSystemInfoRequest message in Random Access Message 3 (Msg.3) to the first cell.

[0142] The RRCSystemInfoRequest message can be viewed as a wake-up signal, where the requested-SI-List indicates the SI or SIB of at least one third cell SIB1 requested by the bearer terminal device.

[0143] When the first relevant information is carried by the first information, the RRCSystemInfoRequest message also includes at least one second relevant information about a third cell, used to explicitly indicate which or which third cells' SIB1 is requested.

[0144] When the first relevant information is carried by the second information (Example 1), the RRCSystemInfoRequest message also includes information indicating the requested system information (SI); when the first relevant information is carried by the second information (Example 2), the RRCSystemInfoRequest message also includes information indicating the requested system information block (SIBx) or information indicating the requested system information (SI); the method by which the terminal device determines which SI / SIB (SIBx) is requested is similar to that described in 602, and will not be repeated here.

[0145] 705, The terminal device receives the acknowledgment message sent in the first cell.

[0146] Optionally, the terminal device can also receive the SIB1 of the first cell again. In the SIB1 of the first cell received again, the broadcast status (si-BroadcastStatus) related to the system information block (SIBx) is set to, for example, broadcasting. For more information on 705, please refer to the Msg3-based on-demand SI related technologies, which will not be elaborated here.

[0147] 706. The terminal device receives at least one first piece of information in the first cell, the first information including the SIB1 of at least one second cell. The implementation method can be found in 604, and will not be repeated here.

[0148] (III) Combining the acquisition of Msg1-based on-demand SIB1 with the acquisition of Msg3-based on-demand SIB1

[0149] Figure 8 is a schematic diagram illustrating the combined process of acquiring Msg1-based on-demand SIB1 and Msg3-based on-demand SIB1. As shown in Figure 8, the combined process of acquiring Msg1-based on-demand SIB1 and Msg3-based on-demand SIB1 may include:

[0150] 801, the terminal device obtains the SIB1 of the first cell in the first cell. The implementation method can refer to 601, the difference being that a set of PRACH preamble and / or PRACH resources of the SI corresponding to the SIB1 of the second cell are configured in si-RequestConfig or si-RequestConfigSUL.

[0151] 802, the terminal device sends a random access message (Msg.1) to the first cell to request SIB1 of at least one third cell. The implementation can refer to 602. Since the PRACH preamble and / or PRACH resources configured in 801 can correspond to a group of second cells, the network device can determine the range or group of third cells requested by the UE upon receiving Msg.1.

[0152] 803, The terminal device receives the random access response sent by the first cell.

[0153] 804. The terminal device sends the RRCSystemInfoRequest message from Random Access Message 3 (Msg.3) to the first cell. The implementation method can be found in 704, and will not be repeated here.

[0154] 805, The terminal device receives the acknowledgment message sent by the first cell.

[0155] Optionally, the terminal device may also receive the SIB1 of the first cell again. In the SIB1 of the first cell received again, the broadcast status (si-BroadcastStatus) related to the system information block (SIBx) is set to, for example, broadcasting.

[0156] 806. The terminal device receives at least one first piece of information in the first cell, the first information including the SIB1 of at least one second cell. Implementations of 805 and 806 can be found in 705 and 706, and will not be repeated here.

[0157] As can be seen from the above embodiments, based on the first relevant information, the terminal device can determine which of the second cell(s)'s SIB1 is included in the first information, and thus obtain the SIB1 of the requested second cell. Furthermore, the second cell does not need to receive WUS or broadcast SIB1, therefore the second cell can also be more energy-efficient.

[0158] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0159] It is worth noting that the above description only covers the steps relevant to this application, but this application is not limited thereto. The information receiving method of this application may also include other steps, and for details of these steps, please refer to related technologies.

[0160] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0161] Second aspect of the embodiments

[0162] This application provides an information transmission method, which is described from the perspective of a network device.

[0163] Figure 9 is a schematic diagram of an information transmission method according to an embodiment of this application. The method is applied to a first network device, which includes network devices belonging to a first cell. As shown in Figure 9, the method includes:

[0164] 901, at least one first message is sent in the first cell, the first message including at least one System Information Block Type 1 (SIB1) of the second cell.

[0165] In some embodiments, the implementation and terminology of 901 in this embodiment are similar to those of 501 and 502 in the embodiments of the first aspect of this application. The above-mentioned related content is incorporated herein and will not be repeated here.

[0166] In some embodiments, the first network device may send WUS configuration information. The WUS configuration information may include a preamble and / or resource information configured for the wake-up signal corresponding to the system information block; alternatively, the WUS configuration information may include second information. The terminal device may send a wake-up signal (WUS) using the preamble and / or resources based on the received WUS configuration information.

[0167] The first network device can receive a wake-up signal (WUS) sent by a terminal device. The sent WUS is used to request the SIB1 of at least one third cell. The sent WUS requests the SIB1 of the third cell by requesting a system information block of the first cell. The SIB1 of the third cell can be included in the system information block of the first cell. The first network device can broadcast first information based on the WUS. The terminal device can obtain the first information broadcast by the first cell; it can obtain the SIB1 of the third cell contained in the first information.

[0168] In some embodiments, the first network device may also send first related information, which may be carried by first information or by second information.

[0169] Please refer to the embodiments in the first aspect for relevant content. The above relevant content is incorporated here and will not be repeated here.

[0170] In some embodiments, since the on-demand SIB1 of the second cell will be sent in the SIB of the first cell, the second network device needs to send the on-demand SIB1 of the second cell it includes to the first network device. That is, the first network device can also receive third information sent by at least one second network device to which the second cell belongs (see 606 in Figure 6, 708 in Figure 7, and 808 in Figure 8). The third information may include at least one on-demand system information block type one (on-demand SIB1) of the second cell. The third information may also include at least one third related information of the second cell. The third related information is information used to identify the cell. The third related information may include at least one of the following: Physical cell identity (PCI), frequency information (e.g., the frequency ARFCN of the SSB), cell identifier (e.g., Cell id or Cell Global ID, etc.), and cell index.

[0171] For example, a first network device can send a request message to a second network device; it can also receive third information (see 605 in Figure 6, 707 in Figure 7, and 807 in Figure 8) from the second network device in response to the request message. The request message may include at least one fourth piece of information related to a second cell. This fourth piece of information is used to identify the cell. It may include at least one of the following: Physical Cell Identity (PCI), frequency information (e.g., the frequency ARFCN of the SSB), cell identifier, or cell index.

[0172] For example, the first network device can also receive third information periodically sent by the second network device. Or

[0173] For example, a first network device can receive third information about a second cell whose SIB1 has changed, sent by a second network device when at least one second cell's System Information Block Type 1 (SIB1) changes. Or

[0174] For example, the third information can be carried by messages during the Xn setup procedure, the RAN node configuration update procedure, or the cell activation procedure. For instance, the third information can be sent via at least one of the following messages: Xn setup request, Xn setup response, RAN node configuration update, RAN node configuration update acknowledge, cell activation request, and cell activation response.

[0175] Therefore, the first network device is able to send first information containing SIB1 of the second cell.

[0176] According to the above embodiments, the first network device can send first related information in the first cell. Based on the first related information, the terminal device can determine which SIB1(s) of the second cell(s) is included in the first information, and obtain the SIB1(s) of the requested second cell. Furthermore, the second network device does not need to receive WUS (Web Service Provider Information) or broadcast SIB1(s), thus the second cell can be more energy-efficient.

[0177] The implementation and terminology of this embodiment are similar to those of the embodiment of the first aspect of this application. The relevant content above is incorporated herein and will not be repeated here.

[0178] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0179] It is worth noting that the above description only covers the steps relevant to this application, but this application is not limited thereto. The information receiving method of this application may also include other steps, and for details of these steps, please refer to related technologies.

[0180] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0181] Third aspect of the embodiments

[0182] This application provides an information transmission method, which is described from the perspective of a network device.

[0183] Figure 10 is a schematic diagram of an information transmission method according to an embodiment of this application. The method is applied to a second network device, which includes network devices belonging to a second cell. As shown in Figure 10, the method includes:

[0184] 1001, Send third information to a third network device, the third information including at least one System Information Block Type 1 (SIB1) of a second cell.

[0185] In some embodiments, the implementation and terminology of 1001 in this embodiment are similar to those of 501 and 502 in the embodiments of the first aspect of this application. The above related content is incorporated herein and will not be repeated here.

[0186] In some embodiments, the second network device includes at least one network device belonging to a second cell, and the third network device includes a first network device belonging to a first cell.

[0187] Alternatively, the second network device may include a DU and the third network device may include a CU. For example, the second network device may be the DU to which the second cell belongs, and the third network device may be the CU to which the second cell belongs.

[0188] In some embodiments, when the second network device includes at least one network device belonging to a second cell, and the third network device includes a first network device belonging to a first cell, third information can be exchanged through the Xn interface.

[0189] For example, Figure 17 is a schematic diagram of an information transmission method according to an embodiment of this application. As shown in Figure 17, optionally, the method may further include: 1701, a third network device may send a request message (e.g., an SIB1 request message) to a second network device; 1702, after receiving the request message sent by the third network device, the second network device may send third information (e.g., including the SIB1 of at least one second cell and third related information of the at least one second cell). The request message includes fourth related information of at least one second cell. Alternatively, the second network device may send the third information periodically. Alternatively, the second network device may send the third information of the second cell whose SIB1 has changed when the System Information Block Type 1 (SIB1) of at least one second cell changes. The third information may be carried by a message in the Xn setup process, the RAN node configuration update process, or the cell activation process, as detailed in the foregoing embodiments.

[0190] In some embodiments, the second network device includes a distributed unit (DU), and the third network device includes a central unit (CU), which can exchange third information through the F1 interface.

[0191] For example, Figure 18 is a schematic diagram of an information transmission method according to an embodiment of this application. As shown in Figure 18, optionally, the method may further include: 1801, a third network device may send a request message (e.g., SIB1 request information) to a second network device; 1802, after receiving the request information sent by the third network device, the second network device may send third information (e.g., including the SIB1 of at least one second cell and the third related information of the at least one second cell). The request message includes the fourth related information of at least one second cell. Alternatively, the second network device may send the third information periodically. Alternatively, the second network device may send the third information of the second cell whose SIB1 has changed when the System Information Block Type 1 (SIB1) of at least one second cell changes. The third information may be carried by messages in the F1 setup process or the gNB-DU configuration update process. Messages in the F1 setup process or the gNB-DU configuration update process include, but are not limited to: F1 setup request, gNB-DU configuration update, gNB-DU configuration update acknowledge, etc.

[0192] The first relevant information can be the same as the second relevant information, and the third relevant information can be the same as the fourth relevant information.

[0193] According to the above embodiment, the second network device can send third information to the third network device. The third information includes at least one System Information Block Type 1 (SIB1) of the second cell. This allows the third network device to provide the terminal device with at least one System Information Block Type 1 (SIB1) of the second cell. The second network device can achieve greater energy efficiency.

[0194] The implementation and terminology of this embodiment are similar to those of the embodiment of the first aspect of this application. The relevant content above is incorporated herein and will not be repeated here.

[0195] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0196] It is worth noting that the above description only covers the steps relevant to this application, but this application is not limited thereto. The information receiving method of this application may also include other steps, and for details of these steps, please refer to related technologies.

[0197] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0198] Fourth aspect of the embodiment

[0199] This application provides an information receiving device, applied / configured in a terminal device. This information receiving device and the information receiving method in the first aspect of this application are based on the same inventive concept and have similar problem-solving principles. Therefore, the implementation of the information receiving device is the same as the implementation of the information receiving method in the first aspect of this application, and repeated details will not be described again. As used below, the terms "unit" or "module" can refer to a combination of software and / or hardware that performs a predetermined function. Although the system described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0200] Figure 11 is a schematic diagram of an information receiving device according to an embodiment of this application. As shown in Figure 11, the information receiving device 1100 includes:

[0201] Receiver 1101 receives first related information of at least one second cell in a first cell; and acquires at least one first piece of information in the first cell, the first piece of information including System Information Block Type 1 (SIB1) of the at least one second cell.

[0202] In some embodiments, receiver 1101 also acquires second information from the first cell, wherein the first related information is included in the second information or included in the first information.

[0203] In some embodiments, the apparatus 1100 may further include a transmitter (not shown) that sends a wake-up signal (WUS) in the first cell to request on-demand SIB1 from at least one third cell.

[0204] In some embodiments, the first information is a system information block, and the apparatus 1200 further includes a processor (not shown) that determines the requested system information block based on predefined or instruction information or the first related information.

[0205] In some embodiments, the receiver 1101 also receives WUS configuration information in the first cell, the WUS configuration information including information on the preamble and / or resources configured for the wake-up signal corresponding to the system information block; or, the WUS configuration information includes second information.

[0206] In some embodiments, receiver 1101 obtains the on-demand SIB1 of the third cell in at least one second cell of the first information-bearing on-demand SIB1 based on the first relevant information.

[0207] In some embodiments, receiver 1101 obtains a system information block in the time window corresponding to the third cell based on the second information and the first related information, so as to obtain the on-demand SIB1 of the third cell; when the time window corresponding to the third cell corresponds to multiple system information blocks, the system information block is one of the multiple system information blocks.

[0208] In some embodiments, receiver 1101 obtains the system information block corresponding to the third cell in the time window corresponding to the third cell based on the second information and the first related information, so as to obtain the on-demand SIB1 of the third cell.

[0209] The implementation methods for each piece of information can be referred to the foregoing embodiments, and will not be repeated here.

[0210] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0211] It is worth noting that the above description only covers the steps relevant to this application, but this application is not limited thereto. The information receiving method of this application may also include other steps, and for details of these steps, please refer to related technologies.

[0212] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0213] Fifth aspect of the embodiment

[0214] This application provides an information transmitting device, applied / configured on a first network device. This information transmitting device is based on the same inventive concept as the information receiving method in the first aspect and the information transmitting method in the second aspect of this application, and the principle of solving the problem is similar. Therefore, the implementation of the information transmitting device is the same as the implementation of the information receiving method in the first aspect and the information transmitting method in the second aspect of this application, and repeated details will not be described again. The terms "unit" or "module" used below can refer to a combination of software and / or hardware that implements a predetermined function. Although the system described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0215] Figure 12 is a schematic diagram of an information transmission device according to an embodiment of this application. As shown in Figure 12, the device 1200 includes:

[0216] Transmitter 1201 transmits at least one first message in a first cell, the first message including at least one System Information Block Type 1 (SIB1) of a second cell.

[0217] In some embodiments, the apparatus 1200 may further include a receiver (not shown) that receives third information sent by a second network device to which at least one of the second cells belongs, the third information including System Information Block Type 1 (SIB1) of at least one of the second cells.

[0218] In some embodiments, the third information may further include at least one third-related information of the second cell.

[0219] In some embodiments, the transmitter 1201 may send a request message to a second network device; and the receiver may receive the third information sent by the second network device in response to the request message; or

[0220] The receiver receives the third information periodically sent by the second network device; or

[0221] The receiver receives the third information about the second cell whose SIB1 has changed, sent by the second network device when the System Information Block Type 1 (SIB1) of the at least one second cell changes; or

[0222] The third information is carried by messages during the Xn setup process, the RAN node configuration update process, or the cell activation process.

[0223] In some embodiments, the request message includes at least one fourth relevant information about the second cell.

[0224] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0225] It is worth noting that the above description only covers the steps relevant to this application, but this application is not limited thereto. The information receiving method of this application may also include other steps, and for details of these steps, please refer to related technologies.

[0226] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0227] Implementation of the sixth aspect

[0228] This application provides an information transmitting device, applied / configured on a second network device. This information transmitting device is based on the same inventive concept as the information receiving method in the first aspect and the information transmitting method in the third aspect of this application, and the principle of solving the problem is similar. Therefore, the implementation of the information transmitting device is the same as the implementation of the information receiving method in the first aspect and the information transmitting method in the third aspect of this application, and repeated details will not be described again. The terms "unit" or "module" used below can refer to a combination of software and / or hardware that implements a predetermined function. Although the system described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0229] Figure 13 is a schematic diagram of an information transmission device according to an embodiment of this application. As shown in Figure 13, the device 1300 includes:

[0230] Transmitter 1301 sends third information to a third network device, the third information including at least one System Information Block Type 1 (SIB1) of a second cell.

[0231] In some embodiments, the second network device includes the network device to which the at least one second cell belongs, and the third network device includes the first network device to which the first cell belongs; or, the second network device includes a DU, and the third network device includes a CU.

[0232] In some embodiments, the third information may further include at least one third-related information of the second cell.

[0233] In some embodiments, after receiving the request information sent by the third network device, the transmitter 1301 sends the third information; or

[0234] Transmitter 1301 periodically transmits the third information; or

[0235] When at least one second cell changes its System Information Block Type 1 (SIB1), transmitter 1401 transmits the third information of the second cell whose SIB1 has changed; or

[0236] The third piece of information is carried by messages during the F1 setup process or the gNB-DU configuration update process; or

[0237] The third information is carried by messages during the Xn setup process, RAN node configuration update process, or cell activation process.

[0238] In some embodiments, the request message includes at least one fourth relevant information about the second cell.

[0239] In some embodiments, the third relevant information and / or the fourth relevant information include PCI and / or frequency information or cell identifier or cell index.

[0240] Seventh aspect of the embodiment

[0241] This application provides a communication system, which, as shown in FIG14, includes a terminal device 1401, a first network device 1402, and a second network device 1403.

[0242] In this embodiment of the application, the terminal device 1401 is configured to perform the information receiving method in the first aspect of the application, for example, the terminal device 1401 receives first related information of at least one second cell in the first cell; and obtains at least one first information in the first cell, the first information including System Information Block Type 1 (SIB1) of the at least one second cell.

[0243] In this embodiment of the application, the first network device 1402 is configured to perform the information transmission method in the second aspect of the application. For example, the first network device 1402 transmits at least one first message in a first cell, the first message including at least one System Information Block Type 1 (SIB1) of a second cell.

[0244] In this embodiment of the application, the second network device 1403 is configured to perform the information transmission method in the third aspect of the application, for example, the second network device 1403 sends third information to the third network device, the third information including at least one System Information Block Type 1 (SIB1) of a second cell.

[0245] This application provides a terminal device.

[0246] Figure 15 is a schematic diagram of the configuration of a terminal device according to an embodiment of this application. The terminal device can be a remote terminal device. As shown in Figure 15, the terminal device 1500 may include a processor 1501 and a memory 1502; the memory 1502 stores data and programs and is coupled to the processor 1501. It is worth noting that this figure is exemplary; other types of structures can also be used to supplement or replace this structure to realize telecommunications functions or other functions.

[0247] For example, processor 1501 may be configured to execute a program to implement the information receiving method as described in the first aspect embodiment. For example, processor 1501 may be configured to perform the following operations: receiving first related information of at least one second cell in a first cell; and acquiring at least one piece of first information in the first cell, the first information including System Information Block Type 1 (SIB1) of the at least one second cell.

[0248] As shown in Figure 15, the terminal device 1500 may further include: a communication module 1503, an input unit 1504, a display 1505, and a power supply 1506. The functions of these components are similar to those in the prior art and will not be described in detail here. It is worth noting that the terminal device 1500 does not necessarily include all the components shown in Figure 15; these components are not essential. Furthermore, the terminal device 1500 may also include components not shown in Figure 15, which can be referred to in related technologies.

[0249] This application provides a network device, such as a base station, but this application is not limited to this and may also include other network devices.

[0250] Figure 16 is a schematic diagram of the network device configuration according to an embodiment of this application. As shown in Figure 16, the network device 1600 may include: a processor 1610 (e.g., a central processing unit CPU) and a memory 1620; the memory 1620 is coupled to the processor 1610. The memory 1620 can store various types of data; in addition, it also stores an information processing program 1630, and executes the program 1630 under the control of the processor 1610.

[0251] For example, processor 1610 can be configured to execute a program to implement the information transmission method as described in the second aspect embodiment or the third aspect embodiment. For example, processor 1610 can be configured to control the transmission of at least one first message in a first cell, the first message including at least one System Information Block Type 1 (SIB1) of a second cell. As another example, processor 1610 can also be configured to control the transmission of third information to a third network device, the third information including at least one System Information Block Type 1 (SIB1) of a second cell.

[0252] In addition, as shown in Figure 16, network device 1600 may also include: transceiver 1640 and antenna 1650, etc.; the functions of the above components are similar to those in the prior art, and will not be described in detail here. It is worth noting that network device 1600 does not necessarily have to include all the components shown in Figure 16; in addition, network device 1600 may also include components not shown in Figure 16, which can be referred to in the prior art.

[0253] This application also provides a computer-readable program, wherein when the program is executed in a terminal device, the program causes the computer to perform the information receiving method described in the first aspect of this application in the terminal device.

[0254] This application also provides a storage medium storing a computer-readable program, wherein the computer-readable program causes a computer to execute the information receiving method described in the first aspect of this application in a terminal device.

[0255] This application also provides a computer-readable program, wherein when the program is executed in a network device, the program causes the computer to perform the information sending method described in the second or third aspect of this application in the network device.

[0256] This application also provides a storage medium storing a computer-readable program, wherein the computer-readable program causes a computer to execute the information transmission method described in the second or third aspect of this application in a network device.

[0257] The apparatus and methods described above in this application can be implemented in hardware or in combination with software. This application relates to a computer-readable program that, when executed by a logic component, enables the logic component to implement the apparatus or components described above, or to implement the various methods or steps described above. This application also relates to storage media for storing the above programs, such as hard disks, magnetic disks, optical disks, DVDs, flash memory, etc.

[0258] The methods / apparatus described in conjunction with the embodiments of this application can be directly embodied in hardware, software modules executed by a processor, or a combination of both. For example, one or more and / or combinations of one or more functional block diagrams shown in the figures can correspond to various software modules in a computer program flow, or to various hardware modules. These software modules can correspond to the various steps shown in the figures, respectively. These hardware modules can be implemented, for example, using a field-programmable gate array (FPGA) to embed these software modules.

[0259] The software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. A storage medium can be coupled to the processor, enabling the processor to read information from and write information to the storage medium; or the storage medium can be an integral part of the processor. The processor and storage medium can reside in an ASIC. The software module can be stored in the memory of a mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a high-capacity MEGA-SIM card or a high-capacity flash memory device, the software module can be stored in the MEGA-SIM card or the high-capacity flash memory device.

[0260] One or more and / or one or more combinations of functional blocks described in the accompanying drawings can be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any suitable combination thereof for performing the functions described herein. One or more and / or one or more combinations of functional blocks described in the accompanying drawings can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0261] The present application has been described above with reference to specific embodiments. However, those skilled in the art should understand that these descriptions are exemplary and not intended to limit the scope of protection of the present application. Those skilled in the art can make various modifications and variations to the present application based on its spirit and principles, and these modifications and variations are also within the scope of the present application.

[0262] Regarding the implementation methods including the above embodiments, the following notes are also disclosed:

[0263] 1. An information transmission method, applied to a second network device, the method comprising:

[0264] Send third information to a third network device, the third information including at least one System Information Block Type 1 (SIB1) of a second cell.

[0265] 2. The method according to Appendix 1, wherein the second network device includes the network device to which the at least one second cell belongs, and the third network device includes the first network device to which the first cell belongs; or, the second network device includes DU, and the third network device includes CU.

[0266] 3. The method according to Appendix 1, wherein the third information further includes third related information of the at least one second cell.

[0267] 4. The method according to Appendix 1, wherein sending the third information to the third network device includes:

[0268] After receiving the request information sent by the third network device, send the third information; or

[0269] Periodically send the third information; or

[0270] When the System Information Block Type 1 (SIB1) of at least one second cell changes, the third information of the second cell whose SIB1 has changed is sent; or

[0271] The third information is carried by messages during the F1 setup process or the gNB-DU configuration update process; or

[0272] The third information is carried by messages during the Xn setup process, the RAN node configuration update process, or the cell activation process.

[0273] 5. The method according to Appendix 4, wherein the request message includes at least one fourth relevant information of a second cell.

[0274] 6. The method according to any one of Appendices 1 to 5, wherein the third relevant information and / or the fourth relevant information includes PCI and / or frequency information or cell identifier or cell index.

[0275] 7. An information transmission method, applied to a first network device, the method comprising:

[0276] The first network device receives third information sent by at least one second network device to which the second cell belongs, the third information including at least one System Information Block Type 1 (SIB1) of the second cell.

Claims

1. An information receiving apparatus applied to a terminal device, the apparatus comprising: a receiver configured to receive, in a first cell, first related information of at least one second cell; and obtain, in the first cell, at least one first information, the first information comprising system information block type one (SIB1) of the at least one second cell.

2. The apparatus of claim 1, wherein, the first related information of the at least one second cell is contained in the first information.

3. The apparatus of claim 2, wherein, the first related information of one second cell corresponds to the SIB1 of the one second cell.

4. The apparatus of claim 1, wherein, the receiver is further configured to obtain, in the first cell, second information, the first related information being contained in the second information.

5. The apparatus of claim 4, wherein, the second information comprises scheduling information of the first information.

6. The apparatus of claim 5, wherein, the first information comprises SIB1 of one second cell.

7. The apparatus of claim 6, wherein, SIB1 of different second cells corresponds to first information in different scheduling information indicated time windows.

8. The apparatus of claim 6, wherein, SIB1 of different second cells corresponds to different types of first information.

9. The apparatus of claim 1, wherein, the apparatus further comprises: a transmitter configured to transmit, in the first cell, a wake-up signal (WUS) to request on-demand SIB1 of at least one third cell.

10. The apparatus of claim 9, wherein, the receiver is further configured to receive, in the first cell, WUS configuration information, the WUS configuration information comprising information of a preamble and / or resource configured for a wake-up signal corresponding to a system information block; or the WUS configuration information comprises second information.

11. The apparatus of claim 9, wherein, the receiver is configured to obtain, according to the first related information, on-demand SIB1 of the third cell in on-demand SIB1 of at least one second cell carried by the first information.

12. The apparatus of claim 9, wherein, the receiver is configured to obtain, according to second information and the first related information, one system information block in a time window corresponding to the third cell to obtain on-demand SIB1 of the third cell; when a plurality of system information blocks correspond to the time window corresponding to the third cell, the one system information block is one of the plurality of system information blocks.

13. The apparatus of claim 9, wherein, the receiver is configured to obtain, according to second information and the first related information, a system information block corresponding to the third cell in a time window corresponding to the third cell to obtain on-demand SIB1 of the third cell.

14. The apparatus of claim 2, wherein, the first related information comprises physical cell identity (PCI) and / or frequency information.

15. The apparatus of claim 1, wherein, the first information is a system information block or a radio resource control message, and the SIB1 of the second cell is an on-demand SIB1. 16.An information transmitting apparatus applied to a first network device, the apparatus comprising: a transmitter configured to transmit, in a first cell, at least one first information, the first information comprising system information block type one (SIB1) of at least one second cell.

17. The apparatus of claim 16, wherein, the apparatus further comprises: a receiver configured to receive, from a second network device to which the at least one second cell belongs, third information comprising SIB1 of the at least one second cell.

18. The apparatus of claim 17, wherein, The third information further comprises third related information of the at least one second cell. 19.The apparatus of claim 17, wherein, the transmitter transmits a request message to the second network device; and the receiver receives the third information transmitted by the second network device in response to the request message; or the receiver receives the third information periodically transmitted by the second network device; or the receiver receives the third information of the second cell whose system information block type one (SIB1) is changed transmitted by the second network device when the SIB1 is changed; or the third information is carried by a message in an Xn setup procedure or a RAN node configuration update procedure or a cell activation procedure.

20. The apparatus of claim 19, wherein, the request message comprises fourth related information of the at least one second cell. the third information further comprises third related information of the at least one second cell. 19.The apparatus of claim 17, wherein, the transmitter transmits a request message to the second network device; and the receiver receives the third information transmitted by the second network device in response to the request message; or the receiver receives the third information periodically transmitted by the second network device; or the receiver receives the third information of the second cell whose system information block type one (SIB1) is changed transmitted by the second network device when the SIB1 is changed; or the third information is carried by a message in an Xn setup procedure or a RAN node configuration update procedure or a cell activation procedure. the request message comprises fourth related information of the at least one second cell.

Images