Information transmission method, and apparatus

Abstract

Disclosed in the present application are an information transmission method and an apparatus. The method comprises: receiving configuration information on a first cell, the configuration information being configuration information of OSI of each cell among a plurality of cells, and the configuration information of the OSI of the plurality of cells being the same; and, on the basis of the configuration information, acquiring, on a second cell, OSI of the second cell, the second cell being one of the plurality of cells. Because the plurality of cells have the same OSI configuration information, by just acquiring the OSI configuration information once, a terminal device can acquire OSI of any cell on the basis of the configuration information, such that the terminal device can still directly acquire the OSI from the second cell even without receiving any SSB and SIB1 of the second cell, thereby improving the efficiency of acquiring the OSI by the terminal device. In addition, a network device does not need to deliver an SSB and an SIB1 in the second cell, thereby saving power consumption of the network device.

Description

An information transmission method and apparatus

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411448605.7, filed on October 16, 2024, entitled "An Information Transmission Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of mobile communications, and more particularly to an information transmission method and apparatus. Background Technology

[0004] Currently, when a terminal device obtains other system information (OSI) from a cell, it first needs to receive the cell's synchronization signal block (SSB) and system information block (SIB) 1. After obtaining downlink synchronization based on the SSB, the terminal device obtains the OSI time-frequency resource configuration from SIB1, thereby receiving OSI on the OSI time-frequency resources.

[0005] SSB (Secondary Subsystem for Buses) in a cell is typically triggered periodically. When a new terminal device moves into the cell, it needs to wait for the SSB transmission cycle to arrive before it can receive the SSB. If the SSB cycle is long, it will cause the terminal device to spend a long time acquiring the OSI (Optical System Identity). SIB1 (Secondary Subsystem for Buses) in a cell can be triggered periodically or on demand. If SIB1 is triggered periodically and the SIB1 cycle is long, it will also cause the terminal device to spend a long time acquiring the OSI. If SIB1 is triggered on demand, when many new terminal devices enter the cell one after another, it will continuously trigger the network device to send SIB1 in the cell, resulting in increased power consumption of the network device.

[0006] How to balance improving the efficiency of terminal devices in acquiring OSI and reducing the power consumption of network devices is a technical problem that urgently needs to be solved. Summary of the Invention

[0007] This application provides an information transmission method and apparatus that can simultaneously improve the efficiency of terminal devices in acquiring OSI and reduce the power consumption of network devices.

[0008] Firstly, an information transmission method is provided. This method can be executed by a terminal device. Unless otherwise specified, "terminal device" in this application can refer to the terminal device itself, a component within the terminal device (e.g., a processor, chip, or chip system), or a logical module or software capable of implementing all or part of the terminal device's functions. The method includes: receiving configuration information on a first cell, the configuration information being the OSI configuration information of various cells in a plurality of cells, wherein the OSI configuration information of the plurality of cells is identical; and obtaining the OSI of a second cell based on the configuration information. The second cell is one of a plurality of cells, and the second cell can be the same as or different from the first cell, without limitation.

[0009] In this embodiment, multiple cells share the same OSI configuration information. Therefore, once a terminal device obtains the OSI configuration information (e.g., from the first cell), it can obtain the OSI of any cell (e.g., the second cell). This allows the terminal device to directly obtain the OSI from the second cell even without receiving the SSB and SIB1 from the second cell, improving the efficiency of OSI acquisition. Furthermore, this method eliminates the need for network devices to distribute SSB and SIB1 from the second cell, thus saving network device power consumption.

[0010] In one possible design, the configuration information can be carried in the SSB (hereinafter referred to as the first SSB) of the first cell. Accordingly, receiving the configuration information in the first cell includes receiving the first SSB, where the first SSB contains the configuration information. In another possible design, the configuration information can be carried in the SIB1 (hereinafter referred to as the first SIB1) of the first cell. Accordingly, receiving the configuration information in the first cell includes receiving the first SIB1, where the first SIB1 contains the configuration information.

[0011] It is understandable that in practical applications, only one of the first SSB and the first SIB1 can carry configuration information, or both can carry configuration information, without any restriction.

[0012] In one possible design, obtaining the OSI of the second cell based on configuration information may include: sending a request message on the second cell based on the configuration information, the request message being used to request the network device to send the OSI of the second cell on the second cell; and receiving the OSI of the second cell on the second cell.

[0013] In this design, the network device sends the OSI of the second cell only after the terminal device triggers the network device to send the OSI of the second cell. This enables the OSI of the second cell to be sent on demand, which can save the power consumption of the network device.

[0014] In one possible design, the configuration information may include first information, which indicates that the OSI of the second cell is to be transmitted on demand.

[0015] Thus, the terminal device can determine that the OSI of the second cell is to be sent on demand based on the first information, and then send a request message to trigger the network device to send the OSI on the second cell.

[0016] In one possible design, before receiving the OSI of the second cell on the second cell, a downlink synchronization signal can also be received on the second cell, which includes the identifier of the second cell.

[0017] In this design, after the terminal device triggers the network device to send the OSI of the second cell, the terminal device can receive the downlink synchronization signal sent by the network device, thereby completing synchronization with the second cell and providing support for the terminal device to receive the OSI on the second cell. The terminal device does not need to wait for the SSB of the second cell to achieve synchronization with it, which can further improve the efficiency of the terminal device in obtaining the OSI.

[0018] In one possible design, the time interval between the downlink synchronization signal and the OSI of the second cell is a preset value; or, the configuration information may also include second information, which is used to indicate the time interval between the downlink synchronization signal and the OSI of the second cell.

[0019] In this way, the terminal device can determine the time interval between the downlink synchronization signal and the OSI of the second cell, and thus receive the downlink synchronization signal and the OSI of the second cell according to the time interval.

[0020] In one possible design, the configuration information may further include third information, which is used to indicate the time-frequency resources of the request message; correspondingly, sending the request message on the second cell according to the configuration information includes: sending the request message on the time-frequency resources indicated by the third information.

[0021] In this way, the terminal device can determine the time and frequency resources used to send the request message, thus improving the reliability of the solution.

[0022] In one possible design, before receiving the OSI of the second cell on the second cell, the SIB1 of the second cell (hereinafter referred to as the second SIB1) can also be received on the second cell, wherein the reception window of the second SIB1 is associated with the reception window of the OSI of the second cell.

[0023] In this design, after the terminal device sends a request message to request the OSI (Optical System Identification) information, it can first receive the SIB1 (System Information Base) of the second cell from the network device. The terminal device can then receive the OSI information of the second cell based on the SIB1. Thus, the configuration information received by the terminal device in the first cell can be used only for obtaining partial OSI configuration information from the second cell; the remaining configuration information is carried in the second SIB1 and sent to the terminal device, improving the flexibility of the solution. Furthermore, when the OSI configuration information is updated, the terminal device can promptly obtain the latest OSI configuration information from the SIB1 of the second cell, improving the reliability of the solution.

[0024] Secondly, an information transmission method is provided. This method can be executed by a network device. Unless otherwise specified, "network device" in this application can refer to the network device itself, a component within the network device (e.g., a processor, chip, or chip system), or a logical module or software capable of implementing all or part of the functions of the network device. The method includes: transmitting configuration information on a first cell, wherein the configuration information is the OSI configuration information of each of multiple cells, and the OSI configuration information of the multiple cells is the same; and transmitting the OSI of a second cell on a second cell. The second cell is one of multiple cells, and the second cell can be the same as or different from the first cell, without limitation.

[0025] In one possible design, a first SSB containing configuration information can be transmitted on the first cell; and / or a first SIB1 containing configuration information can be transmitted on the first cell.

[0026] In one possible design, after receiving the request message on the second cell, the OSI of the second cell can be sent on the second cell. The request message is used to request the network device to send the OSI of the second cell on the second cell.

[0027] In one possible design, the configuration information may also include first information, which is used to indicate that the OSI of the second cell is to transmit on demand.

[0028] In one possible design, before transmitting the OSI of the second cell on the second cell, a downlink synchronization signal can also be transmitted on the second cell, which includes the identifier of the second cell.

[0029] In one possible design, the time interval between the downlink synchronization signal and the OSI of the second cell is a preset value; or, the configuration information may also include second information, which is used to indicate the time interval between the downlink synchronization signal and the OSI of the second cell.

[0030] In one possible design, the configuration information may further include third information, which is used to indicate the time-frequency resources of the request message; correspondingly, receiving the request message on the second cell may include receiving the request message on the time-frequency resources indicated by the third information.

[0031] In one possible design, before transmitting the OSI of the second cell on the second cell, a second SIB1 of the second cell can also be transmitted on the second cell, wherein the receive window of the second SIB1 is associated with the receive window of the OSI of the second cell.

[0032] The beneficial effects of each design in the second aspect above can be referred to the description of the beneficial effects of the corresponding design in the first aspect above, and will not be repeated here.

[0033] Thirdly, an information transmission method is provided, which can be executed by a terminal device. Unless otherwise specified, "terminal device" in this application can refer to the terminal device itself, a component within the terminal device (e.g., a processor, chip, or chip system), or a logical module or software capable of implementing all or part of the terminal device's functions. The method includes: sending a first request message on a second cell, the first request message requesting a network device to send a second SIB1 of the second cell on the second cell; receiving a downlink synchronization signal on the second cell, the downlink synchronization signal including an identifier of the second cell; receiving the second SIB1 on the second cell, the second SIB1 containing OSI configuration information of the second cell; sending a second request message on the second cell according to the configuration information, the second request message requesting the network device to send the OSI of the second cell on the second cell; and receiving the OSI of the second cell on the second cell.

[0034] In this embodiment, after the terminal device triggers the network device to send SIB1 in the second cell, it can receive the downlink synchronization signal sent by the network device in the second cell. This allows the terminal device to complete synchronization with the second cell. Furthermore, after receiving the SIB1 from the second cell, the terminal device also obtains the OSI of the second cell based on the OSI configuration information in the SIB1. This enables the terminal device to directly obtain the SIB1 and OSI of the second cell even without receiving the SSB from the second cell, improving the efficiency of OSI acquisition. Moreover, this method eliminates the need for the network device to send the SSB in the second cell, thus saving network device power consumption.

[0035] In one possible design, the configuration information includes first information, which is used to indicate that the OSI of the second cell is on-demand transmission.

[0036] Thus, the terminal device can determine to send a second request message based on the first information, thereby triggering the network device to send OSI on the second cell.

[0037] In one possible design, the configuration information also includes third information, which is used to indicate the time-frequency resources of the second request message; accordingly, sending the second request message on the second cell according to the configuration information includes: sending the second request message on the time-frequency resources indicated by the third information.

[0038] In this way, the terminal device can clearly specify the time and frequency resources for sending the second request message, thus improving the reliability of the solution.

[0039] Fourthly, an information transmission method is provided, which can be executed by a network device. Unless otherwise specified, "network device" in this application can refer to the network device itself, a component within the network device (e.g., a processor, chip, or chip system), or a logical module or software capable of implementing all or part of the functions of the network device. The method includes: receiving a first request message on a second cell, the first request message requesting the network device to transmit a second SIB1 of the second cell on the second cell; transmitting a downlink synchronization signal on the second cell, the downlink synchronization signal including an identifier of the second cell; transmitting the second SIB1 on the second cell, the second SIB1 containing OSI configuration information of the second cell; receiving a second request message on the second cell, the second request message requesting the network device to transmit the OSI of the second cell on the second cell; and transmitting the OSI of the second cell on the second cell.

[0040] In one possible design, the configuration information includes first information, which is used to indicate that the OSI of the second cell is on-demand transmission.

[0041] In one possible design, the configuration information also includes third information, which is used to indicate the time-frequency resources of the second request message; correspondingly, receiving the second request message on the second cell includes: receiving the second request message on the time-frequency resources indicated by the third information.

[0042] The beneficial effects of each design in the fourth aspect above can be referred to the description of the beneficial effects of the corresponding design in the third aspect above, and will not be repeated here.

[0043] Fifthly, a communication device is provided, the device comprising modules, units, or technical means for implementing the method described in the first aspect or any possible design of the first aspect.

[0044] For example, the apparatus may include:

[0045] The transceiver module is used to receive configuration information on the first cell, which is the OSI configuration information of each of the multiple cells, and the OSI configuration information of the multiple cells is the same; and to obtain the OSI of the second cell on the second cell according to the configuration information, wherein the second cell is one of the multiple cells.

[0046] In a sixth aspect, a communication device is provided, the device comprising modules, units, or technical means for implementing the method described in the second aspect or any possible design of the second aspect.

[0047] For example, the apparatus may include:

[0048] The transceiver module is used to send configuration information on the first cell, which is the OSI configuration information of each of the multiple cells, and the OSI configuration information of the multiple cells is the same; and to send the OSI of the second cell on the second cell, where the second cell is one of the multiple cells.

[0049] In a seventh aspect, a communication device is provided, the device comprising modules, units, or technical means for implementing the method described in the third aspect or any possible design of the third aspect.

[0050] For example, the apparatus may include:

[0051] The transceiver module is configured to: send a first request message on the second cell, the first request message requesting the network device to send the second SIB1 of the second cell on the second cell; receive a downlink synchronization signal on the second cell, the downlink synchronization signal including the identifier of the second cell; receive the second SIB1 on the second cell, the second SIB1 containing the OSI configuration information of the second cell; send a second request message on the second cell according to the configuration information, the second request message requesting the network device to send the OSI of the second cell on the second cell; and receive the OSI of the second cell on the second cell.

[0052] Eighthly, a communication device is provided, the device comprising modules, units, or technical means for implementing the method described in the fourth aspect or any possible design of the fourth aspect.

[0053] For example, the apparatus may include:

[0054] The transceiver module is configured to receive a first request message on the second cell, the first request message being used to request the network device to send the second SIB1 of the second cell on the second cell; send a downlink synchronization signal on the second cell, the downlink synchronization signal including the identifier of the second cell; send the second SIB1 on the second cell, the second SIB1 containing the OSI configuration information of the second cell; receive a second request message on the second cell, the second request message being used to request the network device to send the OSI of the second cell on the second cell; and send the OSI of the second cell on the second cell.

[0055] A ninth aspect provides a communication device comprising a processor and an interface circuit electrically coupled to the processor, wherein the processor, through logic circuitry or execution code instructions, causes the method described in the first aspect or any possible design of the first aspect to be executed, or causes the method described in the second aspect or any possible design of the second aspect to be executed, or causes the method described in the third aspect or any possible design of the third aspect to be executed, or causes the method described in the fourth aspect or any possible design of the fourth aspect to be executed.

[0056] A tenth aspect provides a communication device, comprising: at least one processor; and a communication interface communicatively connected to the at least one processor; wherein the at least one processor, by executing instructions stored in a memory, causes the communication device to perform, via the communication interface, the method described in the first aspect or any possible design of the first aspect, or the method described in the second aspect or any possible design of the second aspect, or the method described in the third aspect or any possible design of the third aspect, or the method described in the fourth aspect or any possible design of the fourth aspect.

[0057] Eleventhly, a computer-readable storage medium is provided, the storage medium storing a computer program or instructions that, when the computer program or instructions are executed, cause the method described in the first aspect or any possible design of the first aspect to be executed, or cause the method described in the second aspect or any possible design of the second aspect to be executed, or cause the method described in the third aspect or any possible design of the third aspect to be executed, or cause the method described in the fourth aspect or any possible design of the fourth aspect to be executed.

[0058] In a twelfth aspect, a computer program product is provided, including instructions that, when executed on a computer, cause the method described in the first aspect or any possible design of the first aspect to be executed, or cause the method described in the second aspect or any possible design of the second aspect to be executed, or cause the method described in the third aspect or any possible design of the third aspect to be executed, or cause the method described in the fourth aspect or any possible design of the fourth aspect to be executed.

[0059] In a thirteenth aspect, a communication system is provided, comprising a terminal device and a network device, wherein the terminal device is configured to perform the method as described in the first aspect or any possible design of the first aspect, and the network device is configured to perform the method as described in the second aspect or any possible design of the second aspect; or, the terminal device is configured to perform the method as described in the third aspect or any possible design of the third aspect, and the network device is configured to perform the method as described in the fourth aspect or any possible design of the fourth aspect.

[0060] For the specific designs and beneficial effects of aspects five through thirteen mentioned above, please refer to the corresponding designs and beneficial effects in aspects one through four. Attached Figure Description

[0061] Figure 1 is a schematic diagram of the architecture of a communication system applicable to an embodiment of this application;

[0062] Figure 2 is a schematic diagram of the network device architecture;

[0063] Figures 3A and 3B are schematic diagrams of the network device architecture;

[0064] Figure 4 shows an example of base station power consumption.

[0065] Figure 5 is an example diagram of the random access procedure;

[0066] Figure 6 is a flowchart of an information transmission method provided in an embodiment of this application;

[0067] Figures 7A to 7C are example diagrams of terminal devices obtaining OSI;

[0068] Figure 8 is a flowchart of another information transmission method provided in an embodiment of this application;

[0069] Figure 9 shows an example diagram of a terminal device obtaining the OSI model.

[0070] Figure 10 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0071] Figure 11 is a schematic diagram of another communication device provided in an embodiment of this application;

[0072] Figure 12 is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0073] First, the application scenarios of the embodiments of this application will be introduced.

[0074] The technical solutions of the embodiments of this application can be applied to various communication systems, such as: 5th generation (5G) communication systems, future communication systems, or other wireless communication systems that adopt wireless access technologies, etc., and the technical solutions of the embodiments of this application can be adopted.

[0075] Referring to Figure 1, this is a schematic diagram of the architecture of a communication system applicable to an embodiment of this application. The communication system 1000 includes an access network (AN) 100. Optionally, the communication system may also include a core network (CN) 200 and an Internet 300. The access network 100 may include at least one network device (or network equipment, or network-side equipment), as shown in Figure 1 (110a and 110b). 110a is a base station, and 110b is a micro-station. The communication system 1000 may also include at least one terminal device (or terminal equipment), as shown in Figure 1 (120a to 120j). 120a, 120e, 120f, and 120j are mobile phones, 120b is a car, 120c is a fuel dispenser, 120d is a home access point (HAP) deployed indoors or outdoors, 120g is a laptop computer, 120h is a printer, and 120i is a drone. The same terminal device or the same network device can provide different functions in different application scenarios. For example, the mobile phones in Figure 1 are 120a, 120e, 120f and 120j. Mobile phone 120a can access base station 110a, connect to car 120b, communicate directly with mobile phone 120e and access HAP. Car 120b can access HAP and communicate directly with mobile phone 120a. Mobile phone 120f can access micro-station 110b, connect to laptop 120g and printer 120h. Mobile phone 120j can control drone 120i.

[0076] A network device is a network-side device with wireless transceiver capabilities. A network device can be a device, equipment, or module located on the network side of a communication system and possessing corresponding communication functions. A network device typically contains communication modules, circuits, or chips that perform the corresponding communication functions. The network device also contains program instructions for performing the corresponding communication functions, as well as corresponding program instructions. A network device can include core network devices and / or access network devices. An access network device can be a device in a radio access network (RAN) that provides wireless communication functions for terminal devices; it can be referred to as RAN equipment. The RAN can be an access network in the 3rd Generation Partnership Project (3GPP), such as 4G, 5G, or future-oriented communication networks. The RAN can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), or a communication network combining two or more of the above.

[0077] RAN equipment can also be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system, etc.

[0078] RAN equipment can also be a module or unit that performs some of the functions of a base station. For example, it can be a central unit / control unit (CU), a distributed unit (DU), or a radio unit (RU). The CU and DU can be set up separately or included in the same network element, such as in a baseband unit (BBU). The RU can be included in radio frequency equipment or radio frequency units, such as in a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH). The embodiments of this application do not limit the specific technology or equipment form used in the network device.

[0079] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an open (O)-RAN system, CU can also be called an O-RAN central unit (O-CU), DU can also be called an O-RAN distributed unit (O-DU), CU-CP can also be called an O-RAN central unit control plane (O-CU-CP), CU-UP can also be called an O-RAN Central Unit User Plane (O-CU-UP), and RU can also be called an O-RU. Any of the units CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. RA equipment can be a macro base station, a micro base station, an indoor station, a relay node, or a donor node, etc.

[0080] In various embodiments of this application, the functions of the network device can be implemented by the network device itself, by modules (such as chips) within the network device, or by logic modules or software capable of implementing all or part of the functions. Alternatively, they can be implemented by a control subsystem that includes network device functions. This control subsystem, including network device functions, can be a control center in the aforementioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities.

[0081] A terminal device is a user-side device with wireless transceiver capabilities. Terminal devices can also be called terminal equipment, terminals, user interfaces (UEs), mobile stations, mobile terminals, etc. Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, intelligent transportation, and smart cities. Terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, mobile stations (MS), subscriber units, cellular phones, smartphones, wireless data cards, personal digital assistant (PDA) computers, tablet computers, wireless modems, handsets, laptop computers, or machine-type communication (MTC) terminals, etc. Terminal devices typically contain communication modules, circuits, or chips that perform the corresponding communication functions. They may also be configured with program instructions for performing these functions.

[0082] In various embodiments of this application, the means for implementing the functions of the terminal device may be implemented by the terminal device itself, or by a module (such as a chip or modem) in the terminal device, or by a logic module or software that can implement all or part of the functions.

[0083] Network devices and terminal devices can be fixed in location or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of the network devices and terminal devices.

[0084] The roles of network devices and terminal devices can be relative. For example, the helicopter or drone 120i in Figure 1 can be configured as a mobile network device. For terminal devices 120j that access the wireless access network 100 via 120i, terminal device 120i is a network device; however, for network device 110a, 120i is a terminal device. That is, 110a and 120i communicate via a wireless air interface protocol. Of course, 110a and 120i can also communicate via a network device-to-network device interface protocol. In this case, relative to 110a, 120i is also a network device. Therefore, both network devices and terminal devices can be collectively referred to as communication devices. 110a and 110b in Figure 1 can be called communication devices with network device functions, and 120a-120j in Figure 1 can be called communication devices with terminal device functions.

[0085] Communication between base stations and terminal devices, between base stations, and between terminal devices can be conducted using licensed spectrum, unlicensed spectrum, or both simultaneously. Communication can be conducted using spectrum below 6 GHz, spectrum above 6 GHz, or both simultaneously. The embodiments of this application do not limit the spectrum resources used for wireless communication.

[0086] Figure 2 illustrates the architecture of a network device. This network device is, for example, any of the network devices shown in Figure 1. As shown in Figure 2, this network device includes a BBU and RRU / AAU / RRH.

[0087] The Baseband Buffer Unit (BBU) can be viewed as a control network element, supporting functions above the interface based on the Enhanced Common Public Radio Interface (eCPRI) protocol (e.g., functions above the Physical Payer-High (PHY-High) layer, specifically including radio resource control (RRC), packet data convergence protocol (PDCP), radio link control (RLC), media access control address (MAC), and PHY-High layer functions). Specifically, the BBU can implement functions such as coding, rate matching, scrambling, modulation, and layer mapping, as well as decoding, descrambling, inverse discrete fourier transform (IDFT), and channel estimation / equalization. Optionally, the processing unit within the BBU used to implement baseband functions can be called a baseband high (BBH) unit.

[0088] RRU / AAU / RRH can be considered as execution network elements, which can support functions below the interface based on the CPRI protocol (e.g., functions below radio frequency functions). The processing unit in RRU / AAU / RRH used to implement baseband functions is called the baseband low (BBL) unit.

[0089] The RRU / AAU / RRH and BBU can communicate via an intermediate network element, which can possess various functions of the low physical layer (PHY-Low) (e.g., precoding, resource element (RE) mapping, RE inverse mapping, etc.). The intermediate network element is not specifically illustrated in Figure 2. Optionally, the intermediate network element can also be included in the network device; that is, both the BBU and the intermediate network element in Figure 2 belong to the network device. The high physical layer and the low physical layer can be collectively referred to as the physical layer (PHY).

[0090] Taking the PHY function as an example, the access network device includes one or more of the following functions: coding, rate matching, scrambling, modulation, layer mapping, precoding, resource element (RE) mapping, digital beamforming (BF), inverse fast Fourier transformation (IFFT) / adding cyclic prefix (CP), decoding, rate matching de-matching, descrambling, demodulation, inverse discrete Fourier transformation (IDFT), channel equalization (or channel estimation), RE de-mapping, digital BF, fast Fourier transform (FFT) / CP removal, digital to analog (DA) conversion, analog BF, analog to digital (AD) conversion, or analog BF.

[0091] The above-mentioned one or more functional modules can be implemented through software, hardware, or a combination of software and hardware. Physically, they can be discrete or integrated. It is understood that the functional modules mentioned above are merely examples, and the access network device may include more other modules (e.g., scheduling module, power control module, hybrid automatic repeat request (HARQ) module, flow control module, mobility management module, or artificial intelligence (AI) module, etc.) depending on the design, or may not include a certain functional module shown in Figure 2 (e.g., excluding the digital BF module).

[0092] Optionally, the BBU may include a CU and / or a DU. The RRU / AAU / RRH includes a radio unit (RU), which may further include a radio frequency (RF) unit and an antenna. The DU and RU can communicate via a fronthaul (FH) interface. Fronthaul interfaces include, but are not limited to, the common public radio interface (CPRI) and / or eCPRI. The interface between the BBU and the RRU / AAU / RRH can also be called a fronthaul interface. To implement the fronthaul interface, the BBU and RRU / AAU / RRH can be connected via a fronthaul network, or the DU and RU can be connected via a fronthaul network. For example, fronthaul networks include, but are not limited to, direct fiber optic connections and wavelength division multiplexing (WDM) networks.

[0093] Network devices can support one or more types of fronthaul interfaces. Different fronthaul interfaces correspond to DUs and RUs with different functions. As shown in Figure 2, if the fronthaul interface between the DU and RU is a CPRI, the DU is configured to implement one or more baseband functions, and the RU is configured to implement one or more radio frequency functions. If the fronthaul interface between the DU and RU is an eCPRI, compared to the CPRI, some baseband functions of the downlink (UL) and / or uplink (DL) are moved from the DU to the RU. Different splitting methods between the DU and RU correspond to different types (Category, Cat) of eCPRI. Figure 2 shows six examples of eCPRI, represented by Cat A, Cat B, Cat C, Cat D, Cat E, and Cat F. These six types can also be represented as Options A to F, or Options 1 to 6, or other methods, without limitation. In addition, there may be other splitting methods between the DU and RU, that is, there may be other types of eCPRI.

[0094] Taking eCPRI Cat A as an example, for downlink transmission, layer mapping is used as the dividing line. DU is configured to implement one or more functions preceding layer mapping (i.e., coding, rate matching, scrambling, modulation, and layer mapping), while other functions following layer mapping (e.g., RE mapping, digital BF, or IFFT / CP addition) are implemented in RU. For uplink transmission, de-RE mapping is used as the dividing line. DU is configured to implement one or more functions preceding de-mapping (i.e., decoding, rate matching de-matching, descrambling, demodulation, IDFT, channel equalization, and de-RE mapping), while other functions following de-mapping (e.g., digital BF or FFT / CP removal) are implemented in RU.

[0095] Similarly, for eCPRI Cat B, Cat C, Cat D, Cat E, and Cat F, different DU and RU segmentation methods are used. The DU handles the segmentation point and the functions before it, while the RU handles the functions after it. The segmentation points for each type of eCPRI are shown in Figure 2 and will not be detailed further. For example, for eCPRI Cat B, RE mapping is used for downlink transmission segmentation, and de-RE mapping is used for uplink transmission segmentation. For uplink transmission, RE mapping and the functions before it are handled by the DU, while the functions after RE mapping and RF functions are handled by the RU. For downlink transmission, de-RE mapping and the functions before it are handled by the DU, while the functions after de-RE mapping and RF functions are handled by the RU.

[0096] The eCPRI segmentation method can be symmetrical for uplink and downlink, as shown in Figure 2 with eCPRI Cat B and Cat C; or, the eCPRI segmentation method can be asymmetrical for uplink and downlink, as shown in Figure 2 with eCPRI Cat A, Cat D, Cat E, and Cat F, without restriction. Optionally, different segmentation methods can be configured for different channels or different channel groups for uplink and / or downlink, i.e., different types of eCPRI can be configured. A channel group can include one or more channels.

[0097] Figure 3A illustrates the chip architecture of a network device. Logically, the network device is divided into CU, DU, and RU. The CU is a platform that performs upper-layer L2 and L3 functions. The backhaul interface carries traffic between the CU and the core network. The DU performs L1 and some L2 functions. The midhaul interface carries traffic between the CU and DU. The RU performs L1 computation and RF digital functions; the fronthaul interface carries traffic between the RU and DU. An integrated DU includes the functions of both the DU and RU.

[0098] The hardware of a CU / DU includes a chassis platform, motherboard, peripherals, and cooling system. The motherboard contains processing units, memory, internal I / O interfaces, and external connection ports. The processing unit is, for example, a central processing unit (CPU), such as an x86 or RAM-based CPU. The CU / DU hardware also includes hardware accelerators, which are designed with interfaces. Hardware functional components include: storage for software, hardware, and system debugging interfaces, and a single-board management controller.

[0099] DU systems are typically implemented using multi-core processors and one or more hardware accelerators. Parts of the DU protocol stack can be implemented in software running on the multi-core processor, while computationally intensive L1 and L2 functions can be offloaded to the hardware accelerator. The hardware accelerator can be a field-programmable gate array (FPGA) / graphics processing unit (GPU); alternatively, all L1 functions can be offloaded to the hardware accelerator, while other protocol stack components are implemented in software running on the processor; or the entire protocol stack can be implemented in software running on the processor. The hardware accelerator supports interconnection with x86 or non-x86 processors. Similarly, the accelerator has a multi-channel PCIe interface pointing to the CPU and external connections via GbE.

[0100] The RU consists of three parts: the open-RAN processing unit (OPU), the data processing unit (DPU), and the radio frequency processing unit (RF processing unit).

[0101] An OPU can be implemented through a RAN fronthaul (RAN FH) processing unit, a CPU, an FPGA, or an ASIC. For example, an OPU receives eCPRI frames from the O-RAN fronthaul and performs fronthaul interface operations, the lowest level L1 (encoding, scrambling, modulation, layer mapping, precoding), synchronization, beamforming, and resource unit mapping.

[0102] The DPU performs synchronization, digital downconversion (DDC) (e.g., digital downconversion in UL), digital upconversion (DDC) (e.g., digital upconversion in DL), crest factor reduction (CFR), and digital pre-distortion (DPD) to improve power amplifier efficiency by reducing the peak-to-average power ratio (PAPR) / adjacent channel power ratio (ACLR) of the RF front end. The DPU can be implemented using an FPGA or an application-specific integrated circuit (ASIC).

[0103] The RF processing unit includes a transceiver module, up / down converters, power amplifiers (PA), low-noise amplifiers (LNA), and transmit / receive (Tx / Rx) filters. The transceiver module can be used for all conversions between the analog and digital domains (digital-to-analog converters (DACs) and analog-to-digital converters (ADCs), specifically, for example, RF sampling, using RF in up-conversion and down-conversion, frequency conversion by mixing intermediate frequency (IF) and local oscillator (LO), etc. Furthermore, the physical and logical partitions within the RF processing unit may not have specific boundaries.

[0104] In one possible design, the DU can be located in the BBU, and the RU can be located in the RRU / AAU / RRH. The processing unit in the BBU used to implement baseband functions is called the baseband high (BBH) unit, and the processing unit in the RRU / AAU / RRH used to implement baseband functions is called the baseband low (BBL) unit.

[0105] For example, Figure 3B illustrates the interaction between BBL and BBH. The specific steps are as follows:

[0106] 1) During system startup or reconfiguration, the BBL reports the channel processing capabilities and switching rules for the Physical Uplink Shared Channel (PUSCH), Physical Downlink Shared Channel (PDSCH), Physical Downlink Control Channel (PDCCH), and Physical Uplink Control Channel (PUCCH) to the BBH via the eCPRI interface. The eCPRI interface signaling involved is newly added signaling. This signaling defines the channel processing capabilities and switching rules for PUSCH / PDSCH / PDCCH / PUCCH. The advantage of this signaling defining channel switching rules is that it facilitates the interconnection of DUs and RUs from different vendors, and also helps decouple the design of DUs and RUs from products from the same vendor.

[0107] 2) The BBH side calculates the BBL processing capacity margin based on the scheduling results of the PUSCH / PDSCH / PDCCH / PUCCH channels in the current processing cycle, and allocates appropriate PDSCH channel processing for the next cycle according to the processing capacity margin. The processing cycle involved in this step is determined by the design and can be in the millisecond or second range.

[0108] 3) BBH notifies BBL of the PDSCH channel processing tasks allocated in step 2) through the eCPRI interface. The PDSCH channel processing adopts the splitting scheme deployed in BBH by default to obtain the advantages of pooled processing resources and flexible evolution.

[0109] The following describes some of the technical features involved in the embodiments of this application.

[0110] I. Energy saving.

[0111] Compared to fourth-generation (4G) networks, fifth-generation (5G) networks (or new radio (NR) networks) have dramatically increased transmission bandwidth. Simultaneously, the higher peak-to-average power ratio (PAPR) further reduces the efficiency of power amplifiers (PAs), leading to a sharp increase in the power consumption of 5G network equipment (such as base stations). At the same time, the dramatic increase in transmission channels at base stations also results in a sharp increase in the static power consumption of 5G systems. Furthermore, the increased deployment frequency bands and smaller coverage areas of 5G networks, coupled with the increasingly dense deployment of base stations, further increase the overall power consumption of the entire network. The power consumption of a single 5G base station is typically 2 to 3 times that of a typical 4G base station. As shown in Figure 4, the typical power consumption of a single remote radio unit (RRU) in the 4G era was 660W, while in the 5G era, the typical power consumption of a single active antenna unit (AAU) increases to 1400W. Such high energy consumption is detrimental to environmental protection and sustainable social development, and also results in significant electricity costs. Energy costs account for 23% of the overall operating expenses of some operators. Therefore, research on green and energy-saving communication technologies is particularly important for the continuous evolution of communication systems.

[0112] II. Staying in the community.

[0113] In NR technology, if a terminal device receives complete system information (mainly referring to the system information block (SIB1)) of a cell, the terminal device can receive paging messages sent by the cell, or actively initiate random access in the cell. It can be said that the terminal device has successfully camped in the cell.

[0114] The process of a terminal device camping in a cell can be divided into the following two steps:

[0115] 1. The terminal equipment receives the synchronization signal block (SSB):

[0116] For example, the base station (or cell) sends SSB at a period of 20ms. The terminal device needs to receive the SSB to obtain downlink synchronization, and at the same time obtain the time and frequency resources for receiving SIB1 from the SSB.

[0117] 2. The terminal equipment receives SIB1.

[0118] For example, the base station (or cell) sends SIB1 at a period of 160ms. After receiving SIB1, the terminal device can obtain the necessary information for accessing or camping on the cell from SIB1, including paging-related configuration information.

[0119] After completing cell camping, the terminal device can receive paging messages within that cell. Paging-related resource configurations mainly include paging PDCCH configuration and paging PDSCH configuration. The paging PDCCH configuration primarily indicates the time-frequency location at which the terminal device receives paging messages, while the PDSCH is used to carry the paging messages. After obtaining the above configuration information, the terminal device can detect paging messages at the corresponding time-frequency location.

[0120] Furthermore, paging-related resources are configured at the cell level (i.e., per cell), meaning that paging configurations can differ between cells. If a terminal device moves from one cell to another, it needs to re-receive the SSB and SIB1 of the new cell, camp on that new cell, and obtain the paging configuration before it can receive paging messages in that new cell.

[0121] III. Random Access.

[0122] If a terminal device needs to send uplink data or signaling when there are no uplink resources, such as when the terminal device needs to send a radio resource control (RRC) reconstruction request, an RRC establishment request, or an RRC resume request, it needs to trigger a random access procedure. During this procedure, the terminal device can request network resources and use those resources to transmit data, while avoiding resource conflicts with other terminal devices.

[0123] See Figure 5 for an example of a random access procedure, which includes the following four steps:

[0124] 1) The terminal device randomly selects a preamble sequence (or preamble) and sends it on the random access channel (RACH). The message sent can be called message 1 (msg1).

[0125] This process may result in two or more terminal devices selecting the same preamble sequence and sending it at the same time.

[0126] 2) After detecting the transmission of a preamble sequence, the network device sends a random access response (which can be called message 2 (msg2)). The random access response should contain at least the following information:

[0127] A. The number of the received leader sequence;

[0128] B. Adjust information periodically;

[0129] C. Uplink resource location indication information allocated to terminal devices, including temporarily allocated cell radio network temporary identifier (C-RNTI).

[0130] 3) After receiving the random access response, the terminal device sends an uplink message (which can be called message 3 (msg3)) on the uplink resources allocated by the network device.

[0131] During this process, the terminal device can send the required content (such as RRC reconstruction information request, RRC establishment request, or RRC resume request) to the network device using the uplink resources allocated by the network device. Simultaneously, it uses the temporary C-RNTI (TC-RNTI) allocated in step 2) to initiate the detection conflict resolution message.

[0132] 4) The network device (such as eNodeB) receives the uplink message sent by the terminal device and returns a conflict resolution message (which can be called message 4 (msg4)) to the UE that has successfully accessed the network.

[0133] If, in step 1), two UEs choose the same preamble sequence and send data at the same time, then in step 3), both UEs will send msg3 simultaneously, resulting in a conflict. When the network device detects uplink resources, it can only detect uplink data sent by one UE at a time. In the conflict resolution message, the network device will truncate the uplink data sent by the UE, extracting the first X bits (X is a positive integer), and schedule them to the UE via a temporary TC-RNTI. Upon receiving this message, the UE checks if it matches its own sent msg3. If they match, the access is considered successful; otherwise, the access fails.

[0134] IV. Other System Information (OSI):

[0135] In the NR system, after cell search, the UE needs to obtain the cell's system information (or system messages). System information mainly includes the master information block (MIB), system information block (SIB) 1, and other system information (OSI). The UE must receive the MIB and SIB1 to camp on the cell. The main contents of the system information are shown in Table 1 below:

[0136] Table 1

[0137] For single-frequency networks (i.e., the entire network uses one frequency), cell reselection will only use the OSI related to co-frequency neighbor cell reselection, namely SIB2 and SIB3.

[0138] SIB1 specifies the transmission method for the OSI model. For example, SIB1 indicates "broadcasting," meaning the OSI model will always be transmitted, while SIB1 indicates "not broadcasting," meaning the OSI model is transmitted on demand. In on-demand transmission, the terminal device needs to actively trigger the transmission for the network device (such as a base station) to send the OSI model.

[0139] In NR technology, idle terminal devices must obtain OSI (mainly SIB2 and SIB3) for mobility management to perform cell reselection within the same frequency range. As mentioned above, OSI can be configured to be sent as required or as needed. If it's required, the network device's basic power consumption will be relatively high. If it's as needed, OSI (mainly SIB2 and SIB3) will be requested whenever a new terminal device enters the cell. However, before requesting OSI, the terminal device first needs to receive SIB1 to obtain OSI-related time-frequency resource configuration information. If the SSB and SIB1 periods are prolonged, when a terminal device moves to a neighboring cell without receiving SSB and SIB1, it cannot obtain the OSI-related time-frequency resource configuration information, resulting in the inability to perform cell reselection. If SIB1 is sent as needed, as many new terminal devices continuously enter the cell, SIB1 transmission will be constantly triggered, leading to increased network device power consumption.

[0140] In view of this, the technical solution of the embodiments of this application is provided to balance reducing the power consumption of network devices and improving the efficiency of terminal devices in obtaining OSI.

[0141] Referring to Figure 6, which is a flowchart of an information transmission method provided in an embodiment of this application, the method is applied to the system shown in Figure 1 as an example, and includes the following steps S601 to S602.

[0142] S601. The network device sends configuration information on the first cell, and the corresponding terminal device receives the configuration information on the first cell.

[0143] This configuration information includes the OSI configuration information for each of the multiple cells, and the OSI configuration information for these multiple cells is the same.

[0144] The OSI (Output System) may include cell reselection-related information, such as SIB2 and SIB3. In some embodiments, the OSI in this application may also be described as "SIB2 and SIB3". Of course, the OSI may also include other information, such as one or more of SIB4 to SIB12 in Table 1, without limitation.

[0145] In some embodiments, configuration information can be carried in the SSB. For example, a network device can receive the SSB of a first cell on a first cell, and the SSB of the first cell contains the configuration information. For ease of description, the SSB of the first cell will be referred to as the first SSB below.

[0146] The first SSB contains configuration information, which can be interpreted in three ways:

[0147] Understanding Method 1: The configuration information is located on the time-frequency resource where the first SSB is located, that is, the configuration information is part of the first SSB.

[0148] Understanding Method 2: The configuration information is located on the time-frequency resources used to transmit the first SSB (i.e., the time-frequency resources allocated to the first SSB), and the configuration information and the first SSB occupy the same time domain resources (such as time slots or symbols), and are located on frequency domain resources not occupied by the first SSB (such as resource blocks (RBs)). (i.e., the first SSB and the configuration information are located on different RBs, which are frequency domain resources allocated to the first SSB).

[0149] In method 3, the configuration information is located on the time-frequency resources used to transmit the first SSB (i.e., the time-frequency resources allocated to the first SSB), and the configuration information and the first SSB occupy the same frequency domain resources (such as RB), and are located on the time domain resources (such as time slots) not occupied by the first SSB (i.e., the first SSB and the configuration information occupy different time slots, which are time domain resources allocated to the first SSB).

[0150] For methods 2 and 3 above, the first SSB contains configuration information, which can also be described as: the configuration information is sent together with the first SSB, or the configuration information is sent at the same time as the first SSB, etc.

[0151] In other embodiments, the configuration information may be carried in SIB1. For example, a network device may receive the SIB1 of a first cell on a first cell, and the SIB1 of the first cell contains the configuration information. For ease of description, the SIB1 of the first cell will be referred to as the first SIB1 below.

[0152] Similarly, the first SIB contains configuration information, which can be understood in three ways. For details, please refer to the above explanation of how the first SSB contains configuration information. We will not elaborate further here.

[0153] In practical applications, only one of the first SSB and the first SIB1 may contain configuration information, or both of the first SSB and the first SIB1 may contain configuration information; there are no restrictions.

[0154] As a possible example, configuration information may include one or more of the following:

[0155] 1. Scheduling Information:

[0156] 1) Broadcast status of system information (including OSI): For example, configure SIB2 and SIB3 to not broadcast, i.e., send on demand;

[0157] 2) The cycle of system information (including OSI);

[0158] 3) SIB mapping relationship: For example, the SIB types included in OSI indicate which SIB(s) are sent in the same period;

[0159] 2. System information (including OSI) window length: indicates the time and location at which the terminal device receives system information (including OSI);

[0160] 3. OSI search space;

[0161] 4. System information (including OSI) area identifier (ID): indicates the system information area to which the current cell belongs;

[0162] 5. Configuration for requesting system information (including OSI):

[0163] 1) Random Access (RACH) related configuration: For example, when a terminal device requests system information based on a random access request message, the random access slot (RO) configuration used in the request message must be the same;

[0164] 2) System information request cycle;

[0165] 3) Resources used for system information requests, such as the preamble index used by the request message sent by the terminal device based on the random access request message.

[0166] Of course, the above content is just a few examples of configuration information, and the actual situation is not limited to this.

[0167] S602. The terminal device obtains the OSI of the second cell based on the configuration information.

[0168] The second residential area is one of the aforementioned residential areas. The second residential area can be the first residential area, or it can be different from the first residential area.

[0169] It is understandable that the terminal device moves to the second cell before obtaining the OSI of the second cell based on the configuration information. For example, the terminal device may move from the first cell to the second cell, or it may move from the first cell to one or more other cells before moving to the second cell; there are no restrictions.

[0170] In the above scheme, multiple cells share the same OSI configuration information. Therefore, a terminal device only needs to obtain the OSI configuration information once (e.g., from the first cell) to obtain the OSI of any cell (e.g., the second cell). This allows the terminal device to directly obtain the OSI from the second cell even without receiving the SSB and SIB1 information from the second cell, improving the efficiency of OSI acquisition. Furthermore, this method eliminates the need for network devices to send SSB and SIB1 information from the second cell, thus saving network device power consumption.

[0171] In one possible design, the configuration information may specifically include resource configurations for the terminal device to trigger the network device to distribute the OSI (Optical System Identity). Specifically, the terminal device obtaining the OSI of the second cell based on the configuration information may include: the terminal device sending a request message on the second cell, which requests the network device to distribute the OSI of the second cell; the network device receiving the request message and distributing the OSI of the second cell; and the terminal device receiving the OSI of the second cell.

[0172] For example, the configuration information may include first information indicating that the OSI of the second cell is to be sent on demand, such as "on demand" as exemplified above. In this case, based on the first information, the terminal device can determine that the OSI of the second cell is to be sent on demand, and then send a request message on the second cell to trigger the network device to send the OSI of the second cell.

[0173] For example, the configuration information may include third information that indicates the time-frequency resource for the request message. For instance, the third information might be a request configuration for system information (including OSI) as exemplified above. Accordingly, the terminal device can send the request message on the time-frequency resource indicated by the third information.

[0174] Furthermore, the configuration information may also include resource configurations related to the terminal device receiving the OSI (or the network device transmitting the OSI). Specifically, the terminal device receives the OSI of the second cell on the second cell according to the configuration information.

[0175] For example, the configuration information includes a fourth piece of information, which indicates the time-frequency resources of the OSI of the second cell. For instance, the fourth piece of information includes one or more of the following: the period of the system information (including OSI), the SIB mapping relationship, the window length of the system information (including OSI), the search space of the OSI, and the area identifier (ID) of the system information (including OSI). Based on this information, the terminal device can determine on which specific time-frequency resources the network device transmits the OSI of the second cell, and thus receive the OSI of the second cell on the corresponding time-frequency resources.

[0176] In some embodiments, the request message may carry indication information, instructing the network device to send the OSI of the second cell on the second cell.

[0177] In some embodiments, the request message may be a random access request message, or the request message may be carried within a random access request message. For example, the terminal device may send a dedicated preamble sequence on the second cell as a request message to trigger the network device to issue an OSI. This preamble sequence may be different from the preamble sequence used for random access, for example, corresponding to a different preamble index.

[0178] In some embodiments, the request message may also be referred to as an uplink wake-up signal or other names, and this application does not impose any restrictions.

[0179] In the above design, the network device sends the OSI of the second cell only after the terminal device triggers the network device to send the OSI of the second cell. This enables the OSI of the second cell to be sent on demand, which can save the power consumption of the network device.

[0180] In one possible design, considering that when the terminal device receives the OSI of the second cell, the network device may not have yet transmitted the SSB on the second cell, or the period for transmitting the SSB in the second cell may not have arrived (i.e., the second cell has not transmitted the SSB), the network device can also transmit a downlink synchronization signal on the second cell before transmitting the OSI of the second cell. Correspondingly, before receiving the OSI of the second cell, the terminal device also receives a downlink synchronization signal on the second cell. This downlink synchronization signal includes the identifier of the second cell, such as the second cell's (physic cell ID, PCI).

[0181] In this design, the network device first sends a downlink synchronization signal based on a request message. This signal can be used by the terminal device to synchronize with the second cell, providing support for the terminal device to subsequently receive OSI signals on the second cell. The terminal device can achieve synchronization with the second cell without waiting for the second cell's SSB, further improving the efficiency of the terminal device in acquiring OSI signals.

[0182] In one possible implementation, the time interval between the downlink synchronization signal and the OSI of the second cell is a preset value. For example, the protocol specifies the time interval between the downlink synchronization signal and the OSI of the second cell, or the network equipment and terminal equipment agree on the time interval between the downlink synchronization signal and the OSI of the second cell, or the network configures the time interval between the downlink synchronization signal and the OSI of the second cell, etc.

[0183] In another possible implementation, the configuration information also includes second information, which indicates the time interval between the downlink synchronization signal and the OSI of the second cell.

[0184] Through any of the above implementation methods, the terminal device can determine the time interval between the downlink synchronization signal and the OSI of the second cell, and thus receive the downlink synchronization signal and the OSI of the second cell according to the time interval.

[0185] In one possible design, before the network device transmits the OSI of the second cell on the second cell, it also transmits the SIB1 of the second cell (hereinafter referred to as the second SIB1); correspondingly, before the terminal device receives the OSI of the second cell on the second cell, it also receives the second SIB1 on the second cell.

[0186] In one possible example, the OSI configuration information obtained by the terminal device from the first cell only includes the relevant resource configuration for triggering the network device to send OSI. After the terminal device sends a request message according to the configuration information, the network device first sends the SIB1 of the second cell (i.e., the second SIB1) on the second cell, which carries the relevant resource configuration for the terminal device to receive OSI (or the network device to send OSI). Thus, the terminal device can receive OSI on the second cell according to the second SIB1.

[0187] In another possible example, the receive window of the second SIB1 is associated with the receive window of the OSI of the second cell; for example, the receive window of the second SIB1 and the receive window of the SIB1 of the second cell are spaced at a fixed interval. In this way, the terminal device can receive the OSI of the second cell based on the received second SIB1.

[0188] In this design, after the network device receives the request message for requesting OSI from the terminal device, it first sends the SIB1 of the second cell, and then sends the OSI of the second cell, so that the terminal device can receive the OSI of the second cell according to the SIB1 of the second cell.

[0189] In this scenario, the configuration information obtained in S601 can be part of the configuration information required by the terminal device to obtain OSI (e.g., for the terminal device to trigger the network device to issue relevant resource configurations for SIB1), while other configuration information (e.g., for the terminal device to trigger the network device to issue relevant resource configurations for OSI) can be issued to the terminal device in SIB1 of the second cell, improving the flexibility of the solution. For example, when the configuration information in S601 is carried by the SSB of the first cell, due to the limited resources of the SSB, only part of the configuration information can be carried, and the remaining configuration information can be carried in SIB1 of the second cell.

[0190] Furthermore, when the OSI configuration information is updated, the network device can carry the updated OSI configuration information in the SIB1 of the second cell, so that the terminal device can obtain the latest OSI configuration information from the SIB1 of the second cell in a timely manner, thereby improving the reliability of the solution.

[0191] It is understood that the above-described embodiments can be implemented individually or in combination with each other, without limitation. Several examples of combined implementations are given below:

[0192] Example 1: SIB1 includes OSI configuration information. Terminal devices directly request the OSI, and network devices distribute the OSI. For example, as shown in Figure 7A:

[0193] 1. The terminal device camps in cell 1 and receives SSB and SIB1 sent by the network device in cell 1. SIB1 includes OSI configuration information, and this configuration information is the same in all cells in an area.

[0194] 2. The terminal device moves to cell 2 and sends a request message to the network device in cell 2 (this request message differs from the one that triggered the network device to send in cell 1, for example, by using a different preamble sequence or indication information), to trigger the network device to send the OSI (Optical System Indicator) in cell 2. The request message can use a dedicated preamble sequence or indication information to request the OSI.

[0195] 3. The network device sends a downlink synchronization signal to the terminal device on cell 2, and the downlink synchronization signal carries the PCI of cell 2. The terminal device receives the downlink synchronization signal and completes synchronization with cell 2.

[0196] 4. The network device sends the OSI signal to the terminal device on cell 2 for the terminal device to perform cell reselection. The terminal device receives the OSI signal on cell 2. The OSI signal and the downlink synchronization signal in step 3 can have a constraint relationship in the time domain, for example, the downlink synchronization signal is one or two time slots before the OSI signal.

[0197] In this example, SIB1 of cell 1 carries OSI configuration information, and this configuration information is the same in all cells in an area. This ensures that the terminal device can directly trigger OSI transmission in any cell without receiving SIB1.

[0198] Example 2: The SSB includes OSI configuration information. Terminal devices directly request the OSI, and network devices distribute the OSI. For example, as shown in Figure 7B:

[0199] 1. The terminal device camps in cell 1 and receives the SSB sent by the network device in cell 1. The SSB includes OSI configuration information, and this configuration information is the same in all cells in an area.

[0200] 2. The terminal device moves to cell 2 and sends a request message to the network device in cell 2 (this request message differs from the one that triggered the network device to send in cell 1, for example, by using a different preamble sequence or indication information), to trigger the network device to send the OSI (Optical System Indicator) in cell 2. The request message can use a dedicated preamble sequence or indication information to request the OSI.

[0201] 3. The network device sends a downlink synchronization signal to the terminal device on cell 2, and the downlink synchronization signal carries the PCI of cell 2. The terminal device receives the downlink synchronization signal and completes synchronization with cell 2.

[0202] 4. The network device sends the OSI signal to the terminal device on cell 2 for cell reselection. The terminal device receives the OSI signal on cell 2. The OSI signal and the downlink synchronization signal in step 3 have a time-domain constraint relationship. For example, the downlink synchronization signal is one or two time slots before the OSI signal.

[0203] In this example, the SSB of cell 1 carries OSI configuration information, and this configuration information is the same in all cells in an area. This ensures that the terminal device can directly trigger the OSI transmission of any cell without receiving SIB1.

[0204] Example 3: The SSB includes OSI configuration information. The terminal device directly requests the OSI, while the network device first sends SIB1 and then sends the OSI. See Figure 7C for example:

[0205] 1. The terminal device camps in cell 1 and receives the SSB sent by the network device in cell 1. The SSB includes OSI configuration information, and this configuration information is the same in all cells in an area.

[0206] 2. The terminal device moves to cell 2 and sends a request message to the network device in cell 2 (this request message differs from the one that triggered the network device to send in cell 1, for example, by using a different preamble sequence or indication information), to trigger the network device to send the OSI (Optical System Indicator) in cell 2. The request message can use a dedicated preamble sequence or indication information to request the OSI.

[0207] 3. The network device sends a downlink synchronization signal to the terminal device on cell 2, and the downlink synchronization signal carries the PCI of cell 2. The terminal device receives the downlink synchronization signal and completes synchronization with cell 2.

[0208] 4. The network device sends SIB1 and OSI to the terminal device on cell 2 for the terminal device to perform cell reselection. The terminal device receives OSI on cell 2. The SI windows of SIB1 and OSI are associated, meaning that the terminal device receives OSI immediately after receiving SIB1.

[0209] In this example, the SSB of cell 1 carries OSI configuration information, and this configuration information is the same in all cells in an area. This ensures that the terminal device can trigger the transmission of SIB1 and OSI in any cell without receiving SIB1.

[0210] Referring to Figure 8, which is a flowchart of an information transmission method provided in an embodiment of this application, the method is applied to the system shown in Figure 1 as an example, and includes the following steps S801 to S805.

[0211] S801. The terminal device sends a first request message on the second cell, and the network device receives the first request message on the second cell accordingly.

[0212] The first request message is used to request the network device to send the SIB1 of the second cell (hereinafter referred to as the second SIB1) on the second cell.

[0213] As you can understand, the second cell here refers to the cell where the terminal device is located. Specifically, it can be the cell where the terminal device first accesses the network, or it can be the cell that the terminal device enters after moving from another cell; there are no restrictions.

[0214] The configuration information used by the terminal device to send the first request message can be configuration information specified by the protocol. For example, the protocol specifies that the terminal device can trigger the network device to issue SIB1 by sending a preamble. The configuration information used by the terminal device to send the first request message can also be configuration information issued by the network, such as configuration information previously received by the terminal device in other cells, such as the first cell. Specifically, this could be the configuration information carried in the SSB and / or SIB1 received by the terminal device in the first cell. This application embodiment does not impose specific restrictions on how the terminal device sends the first request message.

[0215] It is understandable that the terminal device can send a first request message on the second cell even if it has not received the SSB of the second cell. Alternatively, the terminal device can also send a first request message on the second cell even if it has received the SSB of the second cell.

[0216] S802. The network device sends a downlink synchronization signal on the second cell, and the terminal device receives the downlink synchronization signal on the second cell accordingly.

[0217] The downlink synchronization signal includes the identifier of the second cell, which indicates that the downlink synchronization signal is the downlink synchronization signal of the second cell.

[0218] Correspondingly, after receiving the downlink synchronization signal, the terminal device can complete the synchronization with the second cell to enable the reception of other information.

[0219] S803, the network device sends the second SIB1 on the second cell, and the terminal device receives the second SIB1 on the second cell accordingly.

[0220] The second SIB1 contains the OSI configuration information of the second cell.

[0221] For details regarding the specific implementation of the OSI configuration information contained in the second SIB1, please refer to the specific implementation of the OSI configuration information contained in the first SIB1 in the embodiment shown in Figure 6 above, which will not be elaborated further here.

[0222] In one possible implementation, the time interval between the downlink synchronization signal and the second SIB1 is a preset value. For example, the protocol may specify the time interval between the downlink synchronization signal and the second SIB1, or the network device and the terminal device may agree on the time interval, or the network may configure the time interval between the downlink synchronization signal and the second SIB1, etc., without limitation. In another possible implementation, the configuration information also includes second information, which is used to indicate the time interval between the downlink synchronization signal and the second SIB1. Through any of the above implementations, the terminal device can determine the time interval between the downlink synchronization signal and the second SIB1, and thus receive the downlink synchronization signal and the second SIB1 according to that time interval.

[0223] S804. The terminal device sends a second request message on the second cell according to the OSI configuration information, and the network device receives the second request message on the second cell accordingly.

[0224] The second request message is used to request the network device to send the OSI of the second cell on the second cell.

[0225] The specific implementation of the terminal device sending the second request message on the second cell based on the OSI configuration information can be found in the embodiment shown in Figure 6 above, and will not be elaborated further.

[0226] S805: The network device transmits the OSI of the second cell on the second cell, and correspondingly, the terminal device receives the OSI of the second cell on the second cell.

[0227] In the above scheme, the terminal device can directly send a first request message to the second cell to request the second cell's SIB1 even if it has not received the second cell's SSB. After receiving the first request message, the network device first sends a downlink synchronization signal on the second cell to enable the terminal device to synchronize with the second cell. Then, it sends the second cell's SIB1 on the second cell, allowing the terminal device to obtain the second cell's OSI configuration information based on the SIB1. In this scheme, the terminal device can achieve synchronization with the second cell without waiting for the second cell's SSB, improving the efficiency of the terminal device in obtaining the OSI. The network device does not need to periodically broadcast the SSB and SIB1 in the second cell, saving network device power consumption.

[0228] Similarly, the OSI configuration information can also include first information, which indicates that the OSI of the second cell is to be sent on demand. Thus, the terminal device can determine to send a second request message based on the first information, thereby triggering the network device to send the OSI on the second cell.

[0229] Similarly, the configuration information may also include third information, which indicates the time-frequency resources for the second request message; correspondingly, sending the second request message on the second cell according to the configuration information includes sending the second request message on the time-frequency resources indicated by the third information. In this way, the terminal device can explicitly specify the time-frequency resources for sending the second request message, improving the reliability of the solution.

[0230] It is understood that the embodiments shown in Figure 6 and Figure 8 can be implemented separately or in combination to achieve different technical effects.

[0231] For example, Example 4 below provides one possible implementation example.

[0232] Example 4: SIB1 includes OSI configuration information. The terminal device requests SIB1 first, then requests OSI. See Figure 9 for example:

[0233] 1. The terminal device camps in cell 1 and receives SSB and SIB1 sent by the network device in cell 1. SIB1 includes OSI configuration information, and this configuration information is the same in all cells in an area.

[0234] 2. The terminal device moves to cell 2 and sends request message 1 to the network device in cell 2 to trigger the network device to send SIB1 in cell 2. Request message 1 can use a dedicated preamble sequence or indication information to request SIB1.

[0235] 3. The network device sends a downlink synchronization signal to the terminal device on cell 2, and the downlink synchronization signal carries the PCI of cell 2. The terminal device receives the downlink synchronization signal and completes synchronization with cell 2.

[0236] 4. The network device sends SIB1 to the terminal device in cell 2. SIB1 includes OSI configuration information, and this configuration information is the same in all cells in an area.

[0237] It is understandable that if the OSI configuration information is not updated, the OSI configuration information received in step 4 will be consistent with the OSI configuration information received in step 1. If the OSI configuration information is updated, the OSI configuration information received in step 4 will be different from the OSI configuration information received in step 1.

[0238] 5. The terminal device sends request message 2 to the network device on cell 2 based on the latest OSI configuration information, which triggers the network device to send SIB1 on cell 2. Request message 2 can use a dedicated preamble sequence or indication information to request OSI.

[0239] 6. The network device sends the OSI to the terminal device on cell 2 for the terminal device to perform cell reselection, and the terminal device receives the OSI on cell 2.

[0240] In this example, SIB1 of cell 1 carries OSI configuration information, and this configuration information is the same in all cells in an area. After the terminal device moves to a new cell (such as cell 2), it first triggers the new cell to send SIB1, thereby ensuring that the terminal device can obtain the latest OSI configuration information, and triggers the new cell to send OSI according to the latest OSI configuration information.

[0241] It is understood that Figure 9 is only one possible example and is not limited to this.

[0242] The methods provided by the embodiments of this application have been described above with reference to the accompanying drawings. The apparatus provided by the embodiments of this application will be described below with reference to the accompanying drawings.

[0243] This application provides a communication device, which includes modules, units, or means that perform the method steps in the above method embodiments. The functions, units, or means can be implemented by software, hardware, or hardware executing corresponding software.

[0244] For example, referring to FIG10, the device may include a processing module 201 and a transceiver module 202. The transceiver module 202 may include only a sending module, only a receiving module, or both a sending module and a receiving module, without limitation.

[0245] When the device is located at the terminal equipment:

[0246] The transceiver module 202 is used to receive configuration information on the first cell, which is the OSI configuration information of each of multiple cells, and the OSI configuration information of these multiple cells is the same; and to obtain the OSI of the second cell on the second cell based on the configuration information, wherein the second cell is one of the multiple cells. It can be understood that the second cell and the first cell can be the same or different. Optionally, the processing module 201 is used to process the configuration information.

[0247] Because multiple cells share the same OSI configuration information, this device only needs to obtain the OSI configuration information once (e.g., from the first cell) to obtain the OSI of any cell (e.g., the second cell). This allows it to directly obtain the OSI from the second cell even without receiving the SSB and SIB1 information, thus improving the efficiency of OSI acquisition. Furthermore, this method eliminates the need for network devices to distribute SSB and SIB1 information from the second cell, thereby saving network device power consumption.

[0248] In one possible design, the transceiver module 202 is configured to: receive a first SSB on a first cell, the first SSB containing configuration information; and / or receive a first SIB1 on the first cell, the first SIB1 containing configuration information.

[0249] It is understandable that in practical applications, only one of the first SSB and the first SIB1 can carry configuration information, or both can carry configuration information, without any restriction.

[0250] In one possible design, the transceiver module 202 is used to: send a request message on the second cell according to configuration information, the request message being used to request the network device to send the OSI of the second cell on the second cell; and receive the OSI of the second cell on the second cell. In this way, the OSI of the second cell can be sent on demand, saving power consumption of the network device.

[0251] In one possible design, the configuration information also includes first information indicating that the OSI of the second cell is to be transmitted on demand. Thus, the device can determine that the OSI of the second cell is to be transmitted on demand based on the first information, and then send a request message to trigger the network device to transmit the OSI on the second cell.

[0252] In one possible design, the transceiver module 202 is also used to: receive a downlink synchronization signal on the second cell before receiving the OSI of the second cell on the second cell, the downlink synchronization signal including the identifier of the second cell.

[0253] In this way, the device completes synchronization with the second cell, providing support for subsequent OSI reception on the second cell. Furthermore, synchronization with the second cell can be achieved without waiting for the second cell's SSB, further improving the efficiency of OSI acquisition.

[0254] In one possible design, the time interval between the downlink synchronization signal and the OSI of the second cell is a preset value; or, the configuration information may also include second information, which is used to indicate the time interval between the downlink synchronization signal and the OSI of the second cell.

[0255] In this way, the device can receive the downlink synchronization signal and the OSI of the second cell according to the time interval.

[0256] In one possible design, the configuration information also includes third information, which is used to indicate the time-frequency resources of the request message; when the transceiver module 202 sends the request message on the second cell according to the configuration information, it is specifically used to: send the request message on the time-frequency resources indicated by the third information.

[0257] In this way, the device can determine the time and frequency resources used to send the request message, thus improving the reliability of the solution.

[0258] In one possible design, the transceiver module 202 is further configured to: receive the second SIB1 of the second cell on the second cell before receiving the OSI of the second cell on the second cell, wherein the receiving window of the second SIB1 is associated with the receiving window of the OSI of the second cell.

[0259] In this way, the OSI configuration information can include only the resource configurations used to trigger network devices to issue OSI information, improving the flexibility of the solution. Furthermore, when the OSI configuration information is updated, the latest OSI configuration information can be obtained promptly from the SIB1 of the second cell, improving the reliability of the solution.

[0260] When the device is located on a network device:

[0261] The transceiver module 202 is used to send configuration information on the first cell, which is the OSI configuration information of each of the multiple cells, and the OSI configuration information of the multiple cells is the same; and to send the OSI of the second cell on the second cell, where the second cell is one of the multiple cells. It can be understood that the second cell can be the same as the first cell or different from the first cell, without restriction. Optionally, the processing module 201 is used to generate the configuration information and OSI.

[0262] The device sends configuration information on the first cell. This configuration information includes the OSI configuration information for each of the multiple cells. Because multiple cells share the same OSI configuration information, the device only needs to send the OSI configuration information at least once (e.g., on the first cell). Subsequent terminal devices can then obtain the OSI of any cell (e.g., the second cell) based on this configuration information. This allows the device to directly obtain the OSI from the second cell even without receiving the SSB and SIB1 information, thus improving the efficiency of OSI acquisition. Furthermore, this method eliminates the need for the device to send the SSB and SIB1 information on the second cell, thereby saving device power consumption.

[0263] In one possible design, the transceiver module 202 is configured to: transmit a first SSB on the first cell, the first SSB containing configuration information; and / or transmit a first SIB1 on the first cell, the first SIB1 containing configuration information. It is understood that either the first SSB or the first SIB1 may carry configuration information, or both may carry configuration information; there is no restriction.

[0264] In one possible design, the transceiver module 202 is further configured to: after receiving a request message on the second cell, transmit the OSI of the second cell on the second cell. The request message is used to request the network device to transmit the OSI of the second cell on the second cell. In this way, the OSI can be transmitted to the terminal device on the second cell based on the request message, achieving an on-demand triggering effect.

[0265] In one possible design, the configuration information may further include first information indicating that the OSI of the second cell is to be transmitted on demand. This allows the terminal device to clearly identify that the OSI is triggered on demand, thus enabling it to send a request message to trigger OSI transmission when needed.

[0266] In one possible design, the transceiver module 202 is further configured to: before transmitting the OSI of the second cell on the second cell, transmit a downlink synchronization signal on the second cell, the downlink synchronization signal including the identifier of the second cell. This allows the terminal device to complete synchronization with the second cell in advance, further improving the efficiency of the terminal device in acquiring the OSI.

[0267] In one possible design, the time interval between the downlink synchronization signal and the OSI of the second cell is a preset value; alternatively, the configuration information may include second information indicating the time interval between the downlink synchronization signal and the OSI of the second cell. This allows the terminal device to receive the downlink synchronization signal and the OSI of the second cell based on this time interval.

[0268] In one possible design, the configuration information may further include third information, which indicates the time-frequency resources of the request message; correspondingly, the transceiver module 202 is used to receive the request message on the time-frequency resources indicated by the third information. This allows the sender and receiver of the request message to determine the time-frequency resources used by the request message, improving the reliability of the solution.

[0269] In one possible design, the transceiver module 202 is further configured to: before transmitting the OSI of the second cell on the second cell, transmit the second SIB1 of the second cell, wherein the receive window of the second SIB1 is associated with the receive window of the OSI of the second cell. In this way, the OSI configuration information can include only the resource configurations relevant to triggering the network device to issue the OSI, improving the flexibility of the solution. Furthermore, when the OSI configuration information is updated, the latest OSI configuration information can be promptly transmitted to the SIB1 of the second cell, improving the reliability of the solution.

[0270] When the device is located at the terminal equipment:

[0271] The transceiver module 202 is configured to: send a first request message on the second cell, the first request message requesting the network device to send the second SIB1 of the second cell; receive a downlink synchronization signal on the second cell, the downlink synchronization signal including the identifier of the second cell; receive the second SIB1 on the second cell, the second SIB1 containing the OSI configuration information of the second cell; send a second request message on the second cell according to the configuration information, the second request message requesting the network device to send the OSI of the second cell; and receive the OSI of the second cell on the second cell. Optionally, a processing module 201 is configured to process the second SIB1, configuration information, OSI, etc.

[0272] After triggering the network device to send SIB1 in the second cell, this device can receive the downlink synchronization signal sent by the network device in the second cell, thus enabling the terminal device to synchronize with the second cell. Upon receiving the SIB1 from the second cell, it also obtains the OSI of the second cell based on the OSI configuration information in the SIB1. This allows the terminal device to directly obtain the SIB1 and OSI of the second cell even without receiving the SSB from the second cell, improving the efficiency of OSI acquisition. Furthermore, this device eliminates the need for the network device to send the SSB in the second cell, thereby saving network device power consumption.

[0273] When the device is located on a network device:

[0274] The transceiver module 202 is configured to receive a first request message on the second cell, the first request message requesting the network device to transmit the second SIB1 of the second cell on the second cell; transmit a downlink synchronization signal on the second cell, the downlink synchronization signal including the identifier of the second cell; transmit the second SIB1 on the second cell, the second SIB1 containing the OSI configuration information of the second cell; receive a second request message on the second cell, the second request message requesting the network device to transmit the OSI of the second cell on the second cell; and transmit the OSI of the second cell on the second cell. Optionally, the processing module 201 is configured to process and generate the downlink synchronization signal, the second SIB1, the OSI, etc.

[0275] After receiving the second request message, before the second cell sends SIB1, the device also sends a downlink synchronization signal on the second cell. This enables the terminal device to synchronize with the second cell, facilitating its subsequent reception of SIB1 and acquisition of the second cell's OSI configuration information based on the SIB1. This allows the terminal device to directly obtain the second cell's SIB1 and OSI even without receiving the second cell's SSB, improving the efficiency of OSI acquisition. Furthermore, the device can avoid sending SSB on the second cell, thus saving network equipment power consumption.

[0276] It should be understood that all relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0277] Based on the same technical concept, referring to Figure 11, this application embodiment also provides a communication device, including:

[0278] At least one processor 301; and a communication interface 303 communicatively connected to the at least one processor 301; the at least one processor 301 executes instructions stored in the memory 302, causing the device to perform the method steps in the above method embodiments through the communication interface 303. The communication interface 303 can be used to perform the functions of the transceiver module 202, and the processor 301 can be used to perform the functions of the processing module 201.

[0279] Optionally, the memory 302 is located outside the device.

[0280] Optionally, the device includes the memory 302, which is connected to the at least one processor 301 and stores instructions executable by the at least one processor 301. Figure 11 shows, with dashed lines, that the memory 302 is optional for the device.

[0281] The processor 301 and the memory 302 can be coupled through an interface circuit or integrated together; no restriction is imposed here.

[0282] This application embodiment does not limit the specific connection medium between the processor 301, memory 302, and communication interface 303. In this application embodiment, the processor 301, memory 302, and communication interface 303 are connected via a bus 304 in Figure 11. The bus is represented by a thick line in Figure 11. The connection methods between other components are only for illustrative purposes and are not intended to be limiting. The bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 11, but this does not mean that there is only one bus or one type of bus.

[0283] This application embodiment does not limit the specific connection medium between the processor 301, memory 302, and communication interface 303. In this application embodiment, the processor 301, memory 302, and communication interface 303 are connected via a bus 304 in Figure 11. The bus is represented by a thick line in Figure 11. The connection methods between other components are only for illustrative purposes and are not intended to be limiting. The bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 11, but this does not mean that there is only one bus or one type of bus.

[0284] Based on the same technical concept, this application also provides a communication device. Referring to FIG12, the communication device includes a processor 401 and an interface circuit 402. The interface circuit 402 is electrically coupled to the processor 401. The processor 401 executes the method steps in the above method embodiments through logic circuits or executable code instructions. Optionally, the communication device further includes a memory. The interface circuit 402 can be used to execute the functions of the transceiver module 202, and the processor 401 can be used to execute the functions of the processing module 201.

[0285] It should be understood that the processor mentioned in the embodiments of this application can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor, implemented by reading software code stored in memory.

[0286] For example, the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0287] It should be understood that the memory mentioned in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate Synchronous DRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0288] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) can be integrated into the processor.

[0289] It should be noted that the memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.

[0290] Based on the same technical concept, embodiments of this application also provide a computer-readable storage medium, including a program or instructions, which, when run on a computer, cause the methods in the above method embodiments to be executed.

[0291] Based on the same technical concept, embodiments of this application also provide a computer program product, including instructions that, when run on a computer, cause the methods in the above method embodiments to be executed.

[0292] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0293] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0294] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0295] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

Claims

1. A method of information transmission, characterized in that, include: The configuration information is received on the first cell. The configuration information is the OSI configuration information of each cell in the multiple cells, and the OSI configuration information of the multiple cells is the same. The OSI of the second cell is obtained on the second cell according to the configuration information, wherein the second cell is one of the plurality of cells.

2. The method of claim 1, wherein, The second cell is different from the first cell.

3. The method of claim 1 or 2, wherein, Receiving configuration information on the first cell includes: Receive a first synchronization information block (SSB) on the first cell, the first SSB containing the configuration information; and / or The first system information block SIB1 is received on the first cell, and the first SIB1 contains the configuration information.

4. The method of claim 3, wherein, Based on the configuration information, the OSI of the second cell is obtained on the second cell, including: According to the configuration information, a request message is sent on the second cell, the request message being used to request the network device to send the OSI of the second cell on the second cell; Receive the OSI of the second cell on the second cell.

5. The method of claim 4, wherein, The configuration information also includes first information, which is used to indicate that the OSI of the second cell is to be sent on demand.

6. The method of claim 4 or 5, wherein, Before receiving the OSI of the second cell on the second cell, the following is also included: A downlink synchronization signal is received on the second cell, the downlink synchronization signal including the identifier of the second cell.

7. The method of claim 6, wherein, The time interval between the downlink synchronization signal and the OSI of the second cell is a preset value; or, The configuration information also includes second information, which indicates the time interval between the downlink synchronization signal and the OSI of the second cell.

8. The method according to any one of claims 4 to 7, wherein, The configuration information also includes third information, which is used to indicate the time-frequency resources of the request message; Sending a request message on the second cell according to the configuration information includes: The request message is sent on the time-frequency resource indicated by the third information.

9. The method according to any one of claims 4 to 8, wherein, Before receiving the OSI of the second cell on the second cell, the following is also included: The second SIB1 of the second cell is received on the second cell, wherein the reception window of the second SIB1 is associated with the reception window of the OSI of the second cell.

10. An information transmission method characterized by comprising: include: Configuration information is sent on the first cell, which is the OSI configuration information of each cell in the multiple cells, and the OSI configuration information of the multiple cells is the same; The OSI of the second cell is transmitted on the second cell, wherein the second cell is one of the plurality of cells.

11. The method of claim 10, wherein, The second cell is different from the first cell.

12. The method of claim 10 or 11, wherein, Sending configuration information on the first cell includes: Send a first synchronization information block (SSB) on the first cell, the first SSB containing the configuration information; and / or A first system information block (SIB1) is transmitted on the first cell, and the first SIB1 contains the configuration information.

13. The method of claim 12, wherein, Transmit the OSI of the second cell on the second cell, including: After receiving the request message on the second cell, the OSI of the second cell is sent on the second cell. The request message is used to request the network device to send the OSI of the second cell on the second cell.

14. The method of claim 13, wherein, The configuration information also includes first information, which is used to indicate that the OSI of the second cell is to be sent on demand.

15. The method of claim 13 or 14, wherein, Before transmitting the OSI of the second cell on the second cell, the following is also included: A downlink synchronization signal is transmitted on the second cell, the downlink synchronization signal including the identifier of the second cell.

16. The method of claim 15, wherein, The time interval between the downlink synchronization signal and the OSI of the second cell is a preset value; or, The configuration information also includes second information, which indicates the time interval between the downlink synchronization signal and the OSI of the second cell.

17. The method of any one of claims 13-16, wherein, The configuration information also includes third information, which is used to indicate the time-frequency resources of the request message; Receive the request message on the second cell, including: The request message is received on the time-frequency resource indicated by the third information.

18. The method of any one of claims 13-17, wherein, Before transmitting the OSI of the second cell on the second cell, the following is also included: The second SIB1 of the second cell is transmitted on the second cell, wherein the receive window of the second SIB1 is associated with the receive window of the OSI of the second cell.

19. An information transmission method characterized by comprising: include: Send a first request message on the second cell, the first request message being used to request the network device to send the second SIB1 of the second cell on the second cell; A downlink synchronization signal is received on the second cell, the downlink synchronization signal including the identifier of the second cell; The second SIB1 is received on the second cell, and the second SIB1 contains the OSI configuration information of the second cell; According to the configuration information, a second request message is sent on the second cell, the second request message being used to request the network device to send the OSI of the second cell on the second cell; Receive the OSI of the second cell on the second cell.

20. The method of claim 19, wherein, The configuration information includes first information, which is used to indicate that the OSI of the second cell is to be sent on demand.

21. The method of claim 19 or 20, wherein, The configuration information also includes third information, which is used to indicate the time-frequency resources of the second request message; Sending the second request message on the second cell according to the configuration information includes: The second request message is sent on the time-frequency resource indicated by the third information.

22. An information transmission method, characterized by, include: A first request message is received on the second cell, the first request message being used to request the network device to send the second SIB1 of the second cell on the second cell; A downlink synchronization signal is transmitted on the second cell, the downlink synchronization signal including the identifier of the second cell; The second SIB1 is transmitted on the second cell, and the second SIB1 contains the OSI configuration information of the second cell; A second request message is received on the second cell, the second request message being used to request the network device to send the OSI of the second cell on the second cell; Transmit the OSI of the second cell on the second cell.

23. The method of claim 22, wherein, The configuration information includes first information, which is used to indicate that the OSI of the second cell is to be sent on demand.

24. The method of claim 22 or 23, wherein, The configuration information also includes third information, which is used to indicate the time-frequency resources of the second request message; Receiving the second request message on the second cell includes: The second request message is received on the time-frequency resource indicated by the third information.

25. A communications device, characterized by It includes modules for performing the method as described in any one of claims 1-9, or modules for performing the method as described in any one of claims 10-18, or modules for performing the method as described in any one of claims 19-21, or modules for performing the method as described in any one of claims 22-24.

26. A communications device, characterized by The method includes at least one processor; and a communication interface communicatively connected to the at least one processor; wherein the at least one processor executes instructions stored in memory to cause the method as described in any one of claims 1-9 to be executed, or to cause the method as described in any one of claims 10-18 to be executed, or to cause the method as described in any one of claims 19-21 to be executed, or to cause the method as described in any one of claims 22-24 to be executed.

27. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions that, when executed, cause the method described in any one of claims 1-9 to be implemented, or cause the method described in any one of claims 10-18 to be implemented, or cause the method described in any one of claims 19-21 to be implemented, or cause the method described in any one of claims 22-24 to be implemented.

28. A computer program product, characterised in that, Includes instructions that, when executed on a computer, cause the method of any one of claims 1-9 to be implemented, or the method of any one of claims 10-18 to be implemented, or the method of any one of claims 19-21 to be implemented, or the method of any one of claims 22-24 to be implemented.

Images