Communication methods and products

Abstract

The application provides a communication method and product, and belongs to the technical field of communication. The method comprises the following steps: setting a common window, the period of the common window is the greatest common divisor of the periods of multiple SI messages, and one or more SI messages with a multiple relationship are sent in the same common window. At this time, different SI messages do not need to be sent in different SI windows, the time length for a terminal device to acquire SI messages can be shortened, the terminal device can acquire the required SI messages more quickly, the energy consumption of the terminal device can be reduced when the terminal device acquires multiple SI messages through one common window, and in addition, the type of the SI message sent in the common window is matched with the period of the SI message, the SI message can be reasonably sent in different common windows according to the occurrence frequency, and the SI message is sent in an orderly manner.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to a communication method, device, chip system, computer-readable storage medium, and computer program product. Background Technology

[0002] System information (SI) is a set of key network-side parameters that are periodically broadcast or provided on demand by network devices (such as base stations) for terminal devices to perform cell search, access, camp, reselection, and normal communication. System information includes: Master Information Block (MIB), System Information Block (SIB) 1, and other system information (SIBs). Other system information refers to all SIBs other than MIB and SIB1, such as SIB2, SIB3, SIB4, etc.

[0003] SI scheduling is a mechanism used by the network side to allocate and instruct transmission resources for information from other systems. Currently, SI scheduling uses a mechanism based on SI messages and SI windows. However, this design leads to increased latency for terminal devices to obtain SI information. Summary of the Invention

[0004] In view of this, this application provides a communication method, apparatus, chip system, computer-readable storage medium, and computer program product to shorten the time for a terminal device to obtain SI messages, enabling the terminal device to obtain the required SI messages more quickly.

[0005] In a first aspect, embodiments of this application provide a communication method. This method can be executed by a terminal device, or by a component (such as a circuit, chip, or chip system) configured in the terminal device, or by a logic module or software capable of implementing all or part of the functions of the terminal device. This application does not limit this. The following description uses a terminal device as an example.

[0006] The method includes: when it is determined that at least one SI message associated with a target common window contains a target SI message, receiving a target SI message from a network device in the target common window, and obtaining a target SIB based on the target SI message; wherein, a first duration is an integer multiple of the period of each SI message in the at least one SI message, the first duration is the product of the number of windows and the period of the common window, the number of windows is the number of common windows passed from a preset start time point to the start time point of the target common window, the period of the common window is the greatest common divisor of the periods of multiple SI messages, and the at least one SI message is some or all of the multiple SI messages.

[0007] Currently, SI scheduling follows these principles: only SIBs with the same period can be mapped to the same SI message; SI windows for different SI messages do not overlap. That is, different SI messages are sent in different SI windows, and different SI messages are not sent simultaneously. This may increase the latency for terminal devices to acquire SI messages. To address this issue, this application embodiment sets up a common window (as described above, the target common window). The period of this common window is the greatest common divisor of the periods of multiple SI messages. One or more SI messages with periods that are multiples of each other are sent in the same common window. This eliminates the need to send different SI messages in different SI windows, thereby shortening the time it takes for terminal devices to acquire SI messages. This allows terminal devices to acquire the required SI messages faster and reduces power consumption when acquiring multiple desired SI messages through a single common window. Furthermore, based on the characteristic of multiples between SI message periods, by matching the type of SI message sent in the common window with the SI message period, SI messages can be sent rationally in different common windows according to their frequency of occurrence, enabling orderly and conflict-free periodic transmission of SI messages.

[0008] In one possible implementation, the at least one SI message is determined based on the sequence number of the target common window, the period of each SI message among the multiple SI messages, and the period of the common window. The sequence number of the target common window is a value obtained by dividing a second duration by the period of the common window and rounding down. The second duration is the difference between the current time and a preset start time. The current time is the time when the network device determines the sequence number of the target common window. SI messages whose sequence number of the target common window divided by a first value leaves a remainder of zero belong to the at least one SI message; or, SI messages whose sequence number of the target common window divided by the first value leaves a remainder of zero and which need to be broadcast belong to at least one SI message. The first value is a multiple of the period of each SI message among the multiple SI messages and the period of the common window. In this way, the network device can quickly and accurately calculate the one or more SI messages that need to be sent for the target common window. Furthermore, this method eliminates the need for network devices to store large scheduling tables (such as a list of all SI messages to be sent in each public window in chronological order), thus saving network device memory. It also facilitates the dynamic addition and removal of SI messages. For example, when adding a new SI message, it is only necessary to judge the SI message in the above manner, and the wireless system will regenerate the scheduling table without affecting the sending timing of existing SI messages.

[0009] In one possible implementation, before receiving the target SI message from the network device within the target common window, the method of the first aspect further includes: receiving a first message within the target common window, the first message indicating at least one SI message associated with the target common window; and determining the target SI message associated with the target common window based on the first message. Thus, the terminal device does not need to calculate the common window where different SI messages appear, thereby reducing the computational overhead of the terminal device.

[0010] In one possible implementation, the first message is a downlink control information (DCI). Sending at least one SI message within the target common window using existing message instructions can improve resource utilization and reduce transmission latency.

[0011] In one possible implementation, the first message carries a bit string used to indicate at least one SI message. Before receiving the first message in the target common window, the method in the first aspect further includes: receiving first information from the network device, the first information used to indicate the mapping relationship between each bit in the bit string and each SI message in the plurality of SI messages; the determination of the target common window associated with the target SI message based on the first message includes: determining the target common window associated with the target SI message based on the bit string and the first information. Since the situation corresponding to each SI message only occupies 1 bit in the bit string, that is, only N bits are needed to indicate N SI messages, where N is a positive integer, thereby reducing the amount of data transmitted and reducing the communication overhead of the network device. Moreover, the terminal device only needs to determine which SI messages the target common window is associated with based on the bit string sent by the network device, without having to try to receive and parse each SI message, thereby saving the power consumption of the terminal device.

[0012] In one possible implementation, the first information is carried in the System Information Block (SIB1). Sending the first information through the existing SIB1 can improve resource utilization and reduce transmission latency.

[0013] In one possible implementation, before receiving the target SI message from the network device in the target common window, the method of the first aspect further includes: receiving a second message in the target common window, the second message indicating transmission configuration parameters for transmitting at least one SI message; the aforementioned receiving the target SI message from the network device in the target common window includes: receiving the target SI message in the target common window based on the transmission configuration parameters. The transmission configuration parameters may include time-frequency resources for transmitting at least one SI message. The transmission configuration parameters may also include a modulation and coding strategy. The network device may broadcast the second message in the target common window. After receiving the second message, the terminal device may obtain the target SI message based on the transmission configuration parameters, such as receiving the target SI message or at least one SI message containing the target SI message on the time-frequency resources in the transmission configuration parameters, or demodulating the received symbols based on the MCS, and performing channel decoding on the demodulated bits, etc. In this way, it can be ensured that the terminal device successfully obtains the target SI message.

[0014] In one possible implementation, the second message is a DCI. By using existing message indication to transmit at least one SI message's transmission configuration parameters, resource utilization can be improved and transmission latency reduced.

[0015] In one possible implementation, before receiving the target SI message from the network device within the target common window, the method of the first aspect further includes: receiving second information from the network device, the second information including a common window period and a window start reference point, or the second information including a common window length, or the second information including a common window period, a window start reference point, and a common window length; wherein the common window period is used to indicate the period of the common window, the window start reference point is used to indicate the offset of the start time point of the common window relative to the start time point of the window period to which the common window belongs, and the common window length is used to indicate the duration of the common window; receiving the target SI message from the network device within the target common window includes: receiving the target SI message within the target common window according to the second information. Thus, when the second information includes the common window period and the window start reference point, the terminal device can calculate the start time of each common window based on the common window period and the window start reference point. That is, the network device does not need to send the start time of each common window to the terminal device, thereby saving communication resources and reducing the communication overhead of the network device. Furthermore, when the second information includes the common window length, when the terminal device receives the target SI message in the target common window, it can listen to the target common window based on the common window length, so that the terminal device can turn off the receiver or enter a sleep state in time when the target common window ends, thereby avoiding unnecessary power consumption of the terminal device.

[0016] In one possible implementation, before receiving the target SI message from the network device in the target common window, the method of the first aspect further includes: receiving third information from the network device, the third information including at least one of the following: association information and period multiple information, wherein the association information is used to indicate the SIB associated with each SI message in the plurality of SI messages, and the period multiple information is used to indicate the multiple relationship between the period of each SI message in the plurality of SI messages and the period of the common window; the above-mentioned receiving the target SI message in the target common window according to the second information includes: receiving the target SI message in the target common window according to the second information and the third information. Thus, when the third information includes association information, the terminal device can accurately and quickly determine the target SI message based on the association information; when the third information includes period multiple information, the terminal device can calculate the period of each SI message based on the period multiple information and the period of the common window. Compared to the network device sending the period of each SI message, the network device sending the period multiple information can reduce the communication overhead of the network device.

[0017] In one possible implementation, the second and third information are carried in SIB1. Sending the second and third information via the existing SIB1 improves resource utilization and reduces transmission latency. Furthermore, this method allows the terminal device to obtain both the second and third information with a single message reception, thus avoiding the need for the radio frequency and baseband sections of the terminal device to frequently power on to receive multiple messages, thereby reducing the power consumption of the terminal device.

[0018] In one possible implementation, when there are multiple SI messages, each SI message is distinguished by a different logical channel identifier in the Media Access Control (MAC) subheading. This allows network devices to send multiple SI messages using the same time-frequency resources, thereby improving resource utilization and reducing signaling overhead. Furthermore, distinguishing different SI messages using different logical channel identifiers enables terminal devices to quickly and accurately differentiate between multiple SI messages received, ensuring that the terminal device obtains the target SI message.

[0019] In one possible implementation, the method described in the first aspect further includes: entering a sleep state when it is determined that the target common window is not sending a target SI message. That is, the terminal device enters a sleep state when it determines that the target common window cannot obtain a target SI message. This reduces the power consumption of the terminal device.

[0020] In one possible implementation, at least one SI message does not include an on-demand requested SI message. Before receiving the target SI message from the network device within the target common window, the method of the first aspect further includes: if it is determined that the target SI message is an on-demand requested SI message and that the target SI message can be transmitted within the target common window, sending a third message to the network device, the third message being used to request the network device to send the target SI message; and receiving the target SI message from the network device. When the target SI message is an on-demand requested SI message, the network device does not broadcast the target SI message. In this case, the terminal device can request the network device to send the target SI message, thereby obtaining the target SI message it needs.

[0021] Secondly, embodiments of this application provide a communication method. This method can be executed by a network device, or by a component (such as a circuit, chip, or chip system) configured in the network device, or by a logic module or software capable of implementing all or part of the functions of the network device. This application does not limit this. The following description uses a network device as an example.

[0022] The method includes: acquiring at least one SI message and sending the at least one SI message in a target common window; wherein, a first duration is an integer multiple of the period of each SI message in the at least one SI message, the first duration is the product of the number of windows and the period of the common window, the number of windows is the number of common windows passed from a preset start time point to the start time point of the target common window, the period of the common window is the greatest common divisor of the periods of multiple SI messages, and the at least one SI message is some or all of the multiple SI messages.

[0023] In one possible implementation, obtaining at least one SI message includes: obtaining the sequence number of a target public window based on a second duration and the period of a public window, wherein the sequence number of the target public window is a value obtained by dividing the second duration by the period of the public window and rounding down, the second duration being the difference between the current time point and a preset start time point, and the current time point being the time point at which the network device determines the sequence number of the target public window; determining at least one SI message based on the sequence number of the target public window, the period of each SI message in the plurality of SI messages, and the period of the public window; SI messages whose sequence number of the target public window divided by a first value leaves a remainder of zero belong to the at least one SI message, or SI messages whose sequence number of the target public window divided by a first value leaves a remainder of zero and which need to be broadcast belong to at least one SI message; the first value is a multiple of the period of each SI message in the plurality of SI messages and the period of the public window.

[0024] In one possible implementation, before sending at least one SI message in the target public window, the method of the second aspect further includes: sending a first message in the target public window, the first message indicating at least one SI message to be associated with the target public window.

[0025] In one possible implementation, the first message is DCI.

[0026] In one possible implementation, the first message carries a bit string used to indicate at least one SI message; before sending the first message in the target common window, the method of the second aspect further includes: sending first information used to indicate the mapping relationship between each bit in the bit string and each SI message in the plurality of SI messages.

[0027] In one possible implementation, the first information is carried in SIB1.

[0028] In one possible implementation, before sending at least one SI message in the target common window, the method of the second aspect further includes: sending a second message in the target common window, the second message indicating transmission configuration parameters for transmitting at least one SI message.

[0029] In one possible implementation, the second message is DCI.

[0030] In one possible implementation, before sending at least one SI message in the target common window, the method of the second aspect further includes: sending second information, the second information including a common window period and a window start reference point, or the second information including a common window length, or the second information including a common window period, a window start reference point, and a common window length; wherein the common window period is used to indicate the window period of the target common window, the window start reference point is used to indicate the offset of the start time point of the common window relative to the start time point of the window period to which the common window belongs, and the common window length is used to indicate the duration of the common window.

[0031] In one possible implementation, before sending at least one SI message in the target common window, the method of the second aspect further includes: sending third information, the third information including at least one of the following: association information and period multiple information; wherein, the association information is used to indicate the SIB associated with each SI message in the plurality of SI messages, and the period multiple information is used to indicate the multiple relationship between the period of each SI message in the plurality of SI messages and the period of the common window.

[0032] In one possible implementation, the second and third information mentioned above are carried in SIB1.

[0033] In one possible implementation, when there are multiple SI messages in at least one SI message, each SI message in the at least one SI message is distinguished by a different logical channel identifier in the MAC subheader.

[0034] The second aspect is the implementation on the network side, which corresponds to the first aspect. The explanations, supplements, and descriptions of the beneficial effects of the first aspect also apply to the second aspect, and will not be repeated here.

[0035] Thirdly, a communication device is provided. The communication device includes: a module for performing the method in any possible implementation of any of the above aspects, such as a communication module and a processing module. For example, the communication module is used to instruct the transmission and reception functions of the communication device, and the processing module is used to perform functions of the communication device other than the transmission and reception functions.

[0036] Optionally, the communication module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device described in the third aspect, and the receiving module implements the receiving function of the communication device described in the third aspect.

[0037] Optionally, the communication device described in the third aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the methods in any of the possible implementations of any of the above aspects.

[0038] It is understood that the communication device described in the third aspect may be a terminal device or a network device, or it may be a chip (system) or other component or assembly that can be disposed in the terminal device or the network device, or it may be a device that includes the terminal device or the network device. This application does not limit it in this regard.

[0039] Furthermore, the technical effects of the communication device described in the third aspect can be referenced from the technical effects of the methods in any possible implementation of any of the above aspects, and will not be repeated here.

[0040] Fourthly, a communication device is provided, including at least one processor. The at least one processor is coupled to a memory storing programs or instructions. The processor executes the programs or instructions in the memory, causing the communication device to perform a method in any possible implementation of any of the above aspects. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, to which the processor is coupled.

[0041] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0042] In another implementation, the communication device is a chip configured in a terminal device or network device. When the communication device is a chip configured in a terminal device or network device, the communication interface can be an input / output interface.

[0043] Fifthly, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute a method in any possible implementation of any aspect.

[0044] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be output to, for example, but not limited to, a transmitter and transmitted by the transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0045] In a sixth aspect, a communication device is provided, including a processor and a memory. The processor is used to read instructions stored in the memory and to receive signals via a receiver and transmit signals via a transmitter to execute the method in any possible implementation of any of the above aspects.

[0046] Optionally, the processor may be one or more, and the memory may be one or more.

[0047] In a seventh aspect, embodiments of this application provide a chip system including one or more processors for calling and executing instructions stored in memory, causing the methods in any of the above aspects or any possible implementations of the above aspects to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0048] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0049] Eighthly, a computer-readable storage medium is provided that stores a computer program or instructions, which, when executed, cause a computer to perform the method in any possible implementation of any of the preceding aspects.

[0050] Ninthly, a computer program product is provided, the computer program product comprising: a computer program or instructions, which, when the computer program is run, causes the method in any possible implementation of any of the preceding aspects to be executed. Attached Figure Description

[0051] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings.

[0052] Figure 1 A schematic diagram of the communication system provided in the embodiments of this application; Figure 2 A schematic diagram of system information SI scheduling provided in the embodiments of this application. Figure 1 ; Figure 3 A schematic diagram of SI scheduling provided in the embodiments of this application. Figure 2 ; Figure 4 A schematic diagram of SI scheduling provided in the embodiments of this application. Figure 3 ; Figure 5 Flowchart of the communication method provided in the embodiments of this application Figure 1 ; Figure 6 This is a schematic diagram illustrating the process of a base station sending various types of information according to an embodiment of this application; Figure 7 A schematic flowchart illustrating the base station scheduling method provided in this application embodiment; Figure 8 A flowchart illustrating a method for a user equipment (UE) to receive SI messages according to an embodiment of this application; Figure 9 Flowchart of the communication method provided in the embodiments of this application Figure 2 ; Figure 10 Schematic diagram of the communication device provided in the embodiments of this application Figure 1 ; Figure 11 Schematic diagram of the communication device provided in the embodiments of this application Figure 2 . Detailed Implementation

[0053] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0054] The technical solutions provided in this application can be applied to various communication systems, such as: Global System for Mobile Communications (GSM) systems, General Packet Radio Service (GPRS), Wireless Local Area Network (WLAN), Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, sidelink communication systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, non-terrestrial network (NTN) communication systems, 5th generation (5G) mobile communication systems, or new radio access technology (NR). Among these, 5G mobile communication systems can include non-standalone (NSA) and / or standalone (SA) networking. The technical solutions provided in this application can also be applied to future communication systems. This application does not limit the scope of these applications.

[0055] Figure 1 This is a schematic diagram of a communication system 100 used in an embodiment of this application. The communication system 100 may include network devices, such as... Figure 1 The network device 110 is shown. The communication system 100 may also include terminal devices, such as... Figure 1 The terminal device 120 shown. The network device 110 and the terminal device 120 can communicate via a wireless link.

[0056] Figure 1 An exemplary network device 110 and a terminal device 120 are shown. Optionally, the communication system 100 may also include multiple network devices and / or multiple terminal devices.

[0057] The network equipment in this application can be network-side equipment such as access network equipment and core network equipment. Access network equipment is sometimes also called access node. Access network equipment has wireless transceiver capabilities and is used to communicate with terminals. Access network equipment includes, but is not limited to, base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs) in the above-mentioned communication systems, next-generation NodeBs (gNBs) in 5G mobile communication systems, access network equipment or modules of access network equipment in open RAN (ORAN) systems, satellites in NTN communication systems, base stations in future mobile communication systems, or access nodes in WiFi systems. Access network equipment can also be modules or units that can implement some of the functions of a base station. Access network equipment can be macro base stations, micro base stations or indoor stations, relay nodes or donor nodes, or wireless controllers in cloud radioaccess network (CRAN) scenarios. Optionally, access network equipment can also be servers, wearable devices, or vehicle-mounted equipment, etc. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). Multiple access network devices in a communication system can be base stations of the same type or different types. Base stations can communicate with terminals directly or via relay stations. Terminals can communicate with multiple base stations using different access technologies. The embodiments of this application do not limit the specific technology or device form used in the access network equipment. In this application, the access network equipment is referred to as a network device.

[0058] In this application, the means for implementing the functions of a network device can be a network device itself, or a means capable of supporting the network device in implementing those functions, such as a processor, circuit, chip, or chip system. This means can be installed in or connected to the network device. In the technical solutions provided in this application, the example of a network device being used to implement the functions of a network device is used to describe the technical solutions provided in this application.

[0059] The terminal device in this application can be a wireless terminal device capable of receiving network device scheduling and instruction information. The wireless terminal device can be a device providing voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. For example, the terminal device can communicate with one or more core networks or the Internet via a radio access network (RAN). The terminal device can also be referred to as a terminal, user equipment (UE), mobile station, mobile terminal, 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), Internet of Things (IoT), ultra-reliable low-latency communication (URLLC), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, or satellite communication, etc. The terminal can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, aircraft (such as drone, helicopter, airplane), hot air balloon, ship, robot, robotic arm, or smart home device, etc. The embodiments of this application do not limit the form of the terminal device.

[0060] In this application, the apparatus for implementing the functions of a terminal device can be the terminal device itself, or any apparatus capable of supporting the terminal device in implementing those functions, such as a processor, circuit, chip, or chip system. This apparatus can be installed in or connected to the terminal device. In the technical solutions provided in this application, the example of a terminal device being used to implement the functions of a terminal device is used to describe the technical solutions provided in this application.

[0061] Access network equipment and / or terminal equipment can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water; or in the air on aircraft, balloons, and satellites. This application does not limit the application scenarios of the access network equipment and terminal equipment. They can be deployed in the same or different scenarios; for example, both can be deployed on land simultaneously; or the access network equipment can be deployed on land while the terminal equipment is deployed on water, etc., and so on.

[0062] In practical applications, multiple network devices can collaborate to assist terminals in achieving wireless access, with different network devices each implementing a portion of the base station's functions. For example, network devices can be central units (CUs), distributed units (DUs), CUs (control planes, CPs), CUs (user planes, UPs), or radio units (RUs), etc. CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

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

[0064] To facilitate understanding of the embodiments of this application, the terminology used in this application will be briefly explained first. Optionally, the explanation of some terms may also refer to the explanations in the 3rd Generation Partnership Project (3GPP) standard protocol.

[0065] 1. SI is a set of key network-side parameters that are periodically broadcast or provided on demand by network devices (such as base stations) and are necessary for terminal devices to perform cell search, access, camp, reselect, and normal communication. This system information includes: MIB, SIB1, and other system information.

[0066] The MIB is broadcast via the physical broadcast channel (PBCH) and carries limited necessary information, such as the system frame number (SFN) and the physical downlink control channel (PDCCH) configuration.

[0067] SIB1 is transmitted via the physical downlink shared channel (PDSCH) and scheduled via the PDCCH (scrambled with the system information radionetwork temporary identifier (SI-RNTI)). It contains access control information and scheduling information for other SIBs. SIB1 can also be called remaining minimum system information (RMSI).

[0068] Other system information refers to all SIBs other than MIB and SIB1, such as SIB2 to SIB11.

[0069] 2. SI scheduling is a mechanism by which the network allocates and instructs transmission resources for information from other systems. In other words, SI scheduling refers to how the network arranges and organizes the transmission of information from other systems (SIBs 2 and above) on the radio channel, such as when to send it and on which frequency resources. In SI scheduling, the scheduling information for other system information is carried by SIB1. For example, SIB1 can indicate which SIBs the cell provides and in which SI message each of these SIBs is arranged.

[0070] Currently, SI scheduling employs a mechanism based on SI messages and SI windows. This means that one or more SIBs are mapped to the same SI message, and that SI message is sent within the corresponding SI window. Under this mechanism, SI scheduling follows these principles: only SIBs with the same period can be mapped to the same SI message; and the SI windows of different SI messages do not overlap. For example, ... Figure 2 As shown, SIB2 and SIB4 are mapped in SI message 1, and SIB5 is mapped to SI message 2. SI message 1 is sent in SI window 1, and SI message 2 is sent in SI window 2.

[0071] In NR, the SI scheduling scheme has been enhanced multiple times in different versions. These will be explained below.

[0072] In Release (Rel)-15, SI messages carrying SIBs are configured in the scheduling InfoList. The SI window for SI messages is determined according to the order of the SI message entries configured in the scheduling InfoList. In Rel-15, some idle windows exist that cannot be utilized. For example... Figure 3 As shown, the SI window with index number 1 ( Figure 1 SI windows from index SI-1 to index 7 ( Figure 1 SI-7 windows are respectively configured in subframes n+1 to n+7, and the SI windows do not overlap; and Figure 3 There are some unused SI windows that cannot be used.

[0073] In Rel-16, 5G introduces enhanced support for positioning capabilities. To this end, the network needs to broadcast a set of Positioning System Information Blocks (posSIBs) to provide positioning assistance data to the terminal (UE), such as reference signal configuration and base station location information. The SI messages carrying posSIBs are configured in posSchedulingInfoList to support posSIB transmission. For positioning SI messages, the protocol introduces a new parameter, offsetToSI-Used. When this parameter is configured, the positioning SI window calculation rule changes: posSchedulingInfoList is appended to the end of the SI message list configured by schedulingInfoList with a period of 8 radio frames. Then, the SI windows of all positioning SI messages generated by posSchedulingInfoList are shifted backward by 80ms, creating an idle window between SFN8 and SFN16 specifically for transmitting positioning reference signals and other positioning-related signals. Figure 4 As shown, there are idle windows in SFN8 to SFN16, which can be used to transmit positioning reference signals and other positioning-related signals.

[0074] In Rel-17, SI messages carrying SIBs or posSIBs (System Information Blocks introduced in Rel-17) are configured in schedulingInfoList2. The SI window for SI messages is directly indicated by the gNB. This enhancement allows any free window to be utilized.

[0075] Due to the limitations of the aforementioned principles, SI messages from different periods can only be mapped to different SI windows, and these SI windows are ordered sequentially in the time domain. This design increases the latency for the terminal device to acquire SI messages and also increases the power consumption of the terminal device. For example, when multiple SI messages exist, after receiving MIB and SIB1, the terminal device needs to wait for multiple (e.g., 8) independent SI windows before it can receive the required SI message, resulting in a longer waiting time for the terminal device to acquire the required SI message.

[0076] To address the aforementioned issues, this application proposes setting up a common window whose period is the greatest common divisor of the periods of all SI messages. One or more SI messages with periods that are multiples of each other are sent within the same common window. This eliminates the need to send different SI messages in separate SI windows, allowing network devices to send multiple SI messages within a single common window. This shortens the time it takes for terminal devices to acquire SI messages, enabling them to obtain the required SI messages more quickly and reducing their energy consumption. Furthermore, based on the characteristic of the multiples of SI message periods, by matching the types of SI messages sent in the common window with their periods, SI messages can be sent in different common windows according to their frequency of occurrence, ensuring orderly transmission of SI messages.

[0077] The solution provided in this application will be described in detail below with reference to the corresponding flowcharts. It is understood that the illustrative flowcharts provided in this application primarily use different devices (e.g., terminal devices, network devices) as examples of the execution subjects of this interactive illustration to illustrate the method, but this application does not limit the execution subjects of the interactive illustrations. For example, the devices (e.g., terminal devices, network devices) in the illustrative flowcharts can also be chips, chip systems, or processors that support the implementation of this method on the device, or logic modules or software that can implement all or part of the functions of the device.

[0078] As a general statement, the message or signaling interactions involved in the interaction process of this application embodiment can be standard messages or signaling or newly introduced messages or signaling. This application embodiment does not make specific limitations on this.

[0079] Figure 5 This is a schematic diagram illustrating a communication method according to an embodiment of this application. It can be understood that... Figure 5 The terminal device in the middle can be Figure 1 Any terminal device in the network can be a component (such as a processor, chip, or chip system). Network devices can be... Figure 1 Any access network device, or a component within an access network device (such as a processor, chip, or chip system). For example... Figure 5 As shown, the above communication method includes the following steps: S501, the network device receives at least one SI message.

[0080] SI messages can be used to carry one or more SIBs with the same (scheduling) period. In the embodiments of this application, the network device can group SIBs with the same period into the same group and map the SIBs in that group to the same SI message. In other words, the SIBs in the SI message have the same period. It is understood that the specific principle of SI messages can also refer to the prior art, and will not be elaborated here.

[0081] At least one SI message is associated with a target common window (described below), or in other words, at least one SI message is mapped to a target common window. This at least one SI message can be understood as one or more SI messages actively sent or actively broadcast by the network device in the target common window, that is, the at least one SI message is sent without being requested by other devices from the network device.

[0082] At least one SI message belongs to multiple SI messages (denoted as the SI message set), or in other words, the at least one SI message is a part or all of the SI messages in the SI message set. This SI message set can be understood as all SI messages in the communication network, such as all SI messages in 5G NR, such as SI message 1, SI message 2, SI message 3, etc. It is understandable that as communication technology continues to evolve, future communication networks may add new SI messages or reduce existing SI messages, and this SI message set can be adaptively adjusted according to changes in communication requirements.

[0083] The period of each SI message in at least one SI message is divisible by the first duration, or in other words, the first duration is an integer multiple of the period of each SI message in at least one SI message.

[0084] The period of each SI message in at least one SI message refers to the period during which the SI message is sent, or in other words, the time interval between the repeated occurrences of the SI message. The periods of the SI messages in at least one SI message can be the same or different. For example, at least one SI message includes SI message 1, SI message 2, and SI message 4; where SI message 1 has a period of rf8, where rf8 refers to 8 radio frames, and the duration of one radio frame is 10 milliseconds (ms), i.e., rf8 is 80ms; SI message 2 has a period of 16 rf, i.e., 160ms; and SI message 4 has a period of 8 rf, i.e., 80ms. It can be understood that the periods of different SI messages in 5G NR are multiples of each other.

[0085] The first duration is the product of the number of windows and the period of the common window.

[0086] The number of windows is the number of public windows that pass through from the preset start time point to the start time point of the target public window.

[0087] The preset start time point can be understood as the initial time of the pre-set system time, or, in other words, as the absolute starting reference point on the entire system timeline. This preset time point can be the starting time point of the period to which the first common window (denoted as the first common window) belongs. Furthermore, the preset start time point can be determined by the radio frame and subframe numbers. For example, if time is divided into radio frames of 10ms length, each frame has a number (SFN), with SFNs ranging from 0 to 1023 and cycling through them; and the preset start time point is SFN=0, subframe=0, then the starting position of the first common window can be the 0th subframe of the 0th radio frame.

[0088] The target common window can be understood as the window that will send at least one of the aforementioned SI messages. This target common window can be any of the periodically appearing common windows. In this embodiment, the common window appears periodically, and it can be used to transmit one or more SI messages associated with it. For example, the period of the common window is rf16, meaning the period is 160ms, and the common window appears once every 160ms. The target common window can be the third appearing common window. The start time of the target common window can be understood as the moment when the target common window begins.

[0089] The number of windows can be calculated by dividing the difference between the preset start time and the start time of the target common window by the period of the common window (described below) and rounding down. For example, if the preset start time is SFN=0, the period of the target common window is rf8 (80ms), and the start time of the target common window is SFN=26, the difference between the preset start time and the start time of the target common window is 260ms. Dividing 260 by 80 and rounding down gives a value of 3, meaning that 3 common windows have passed before the target common window, and the number of windows is 3. In other words, the target common window is the 4th common window to appear.

[0090] A common window can be understood as a window that transmits one or more SI messages. The target common window and the first common window mentioned above belong to the common window category. The period of a common window can be understood as the basic unit of transmission time for all SIBs except SIB1, or in other words, the period of a common window can be understood as the basic unit of transmission time for all SI messages in the SI message set. The period of a common window is the greatest common divisor of the periods of the SI message set (all SI messages in it). For example, if the periods of the SI messages in the SI message set are rf8, rf16, rf24, and rf32, then the period of the common window (such as the target common window and the first common window) is rf8, which is 80ms.

[0091] For example, the SI set includes SI messages #A1, #A2, #A3, and #A4, with periods of rf8 (80ms), rf16 (160ms), rf24 (240ms), and rf32 (320ms) respectively. The period of the common window is rf8 (80ms). The preset start time is SFN=0. If the start time of the target common window is SFN=34, then the number of windows is 4, the first duration is 320ms, and at least one SI message is SI message #A1, SI message #A3, or SI message #A4. In this case, the first duration divided by the periods of SI message #A1, SI message #A3, and SI message #A4 respectively yields an integer value. Alternatively, if the starting time of the target public window is SFN=2, then the number of windows is 0, the first duration is 0, and at least one SI message is all SI messages in the SI message set. In this case, the result of dividing the first duration by the period of each SI message in the SI message set is 0.

[0092] Furthermore, the first duration can also be expressed as the difference between the start time of the period to which the target common window belongs and the preset start time. Continuing the example above, if the start time of the target common window is SFN=34, then the period to which the target common window belongs starts at SFN=32 and ends at SFN=40, meaning the start time of the period to which the target common window belongs is SFN=32. In this case, the first duration is the duration between SFN=32 and SFN=0, i.e., rf32 (320ms). Alternatively, if the start time of the target common window is SFN=2, then the period to which the target common window belongs starts at SFN=0 and ends at SFN=8, meaning the start time of the period to which the target common window belongs is SFN=0, and the first duration is 0.

[0093] When the start time of the period to which the first common window belongs is a preset start time, the first duration can also be expressed as the difference between the start time of the target common window and the start time of the first common window. Continuing the example above, the start time of the period to which the first common window belongs is SFN=0, and the start time of the first common window is SFN=2. If the start time of the target common window is SFN=34, then the difference between the start time of the target common window and the start time of the first common window is rf32, that is, the first duration is rf32 (320ms). Alternatively, if the start time of the target common window is SFN=2, then the difference between the start time of the target common window and the start time of the first common window is 0, that is, the target common window is the first common window, and the first duration is 0.

[0094] In this embodiment, SFN can be used as a reference time, such as using SFN = 0 as a preset starting time point. The value range of SFN can be fixed. For example, the value of SFN can be from 0 to 1023, that is, when SFN counts to 1023, the SFN of the next radio frame will automatically reset to zero and start counting again from 0, forming a cycle with a period of 1024 radio frames (i.e., 10.24 seconds (s)). For the common window, the starting time point of the common window can be the moment when SFN = 0 in each cycle. For example, during the current SFN counting process, the starting time point of the common window is the moment when SFN = 0 during the SFN counting process; after the current SFN counts to 1023, the SFN of the next radio frame will automatically reset to zero, that is, SFN = 0, and the moment when SFN = 0 is the starting time point of the common window.

[0095] By setting the period of the common window to the greatest common divisor of the periods of all SI messages in the SI message set, the duration between the start time of any common window's period and the preset start time is an integer multiple of the periods of at least some of the SI messages in this SI message set. This ensures that SI messages are sent periodically without conflict at fixed window numbers.

[0096] The above content introduced the relationship between the public window and SI messages. The following describes how to obtain at least one of the aforementioned SI messages.

[0097] In a first possible implementation, the network device acquiring at least one SI message may specifically include: the network device acquiring the sequence number of a target common window based on a second duration and the period of a common window, and determining at least one SI message based on the sequence number of the target common window, the period of each SI message in the aforementioned SI message set, and the period of the common window. Specifically, the sequence number of the target common window is the value obtained by dividing the second duration by the period of the common window and rounding down, where the second duration is the difference between the current time point and a preset start time point, and the current time point is the time point at which the network device determines the sequence number of the target common window; SI messages whose sequence number of the target common window has a remainder of zero when divided by a first value belong to at least one SI message, where the first value is a multiple of the period of each SI message in the SI message set and the period of the common window. That is, the at least one SI message is determined based on the sequence number of the target common window, the period of each SI message in the aforementioned SI message set, and the period of the aforementioned common window.

[0098] The sequence number of the target common window can also be called its index, number, or other possible names. The sequence number of the target common window can be used to uniquely identify its sequential position on the timeline. For example, if the sequence number of the common window starts from 0, then the sequence number s can represent the (s+1)th appearing common window; or, if the sequence number of the common window starts from 1, then the sequence number s can represent the sth appearing common window, where s is a positive integer. For instance, if the sequence number of the common window starts from 0 and the sequence number of the target common window is 2, then the target common window is the 3rd appearing common window.

[0099] The second duration can represent the time interval between the current time and the preset start time. The current time can be understood as the current system time when the network device obtains the sequence number of the target window, such as SFN=34. The time when the network device obtains the sequence number of the target common window can be the start time of the target common window or any time within the target common window. That is, the current time can be the start time of the target common window or any time within the target common window.

[0100] Network devices can calculate the serial number of the target public window according to the following formula (1).

[0101] wid = floor(t1 / co_period); (1) Where wid is the sequence number of the target common window, t1 is the second duration mentioned above, co_period is the period of the common window, and floor is the floor function. When the preset start time is SFN=0, the second duration can be expressed as the current system time, i.e., SFN×10 + slot_offset. SFN×10 can represent the total duration of the complete radio frame since the preset start time, and slot_offset can represent the offset in milliseconds from the frame header to the current time slot within the current radio frame. That is, the current system time is the total number of milliseconds from the absolute starting point (such as the start time of the radio frame with SFN=0) to the current time.

[0102] It is understood that the above describes how a network device calculates the sequence number of a target common window when or after the target common window arrives. In this embodiment, the network device can also calculate the sequence number of the target common window in advance before it arrives. In this case, the network device can determine the current time point as the start time point, end time point, or any time within the target common window to perform the above calculation and obtain the sequence number of the target common window. That is, the network device does not use the current system time when obtaining the sequence number of the target window as the current system time for the above calculation.

[0103] The network device can perform the following formula (2) on each SI message in the above SI message set to determine whether the SI message needs to be sent in the target common window.

[0104] Y = wid mod (SIm_period / co_period); (2) Where SIm_period is the period of the m-th SI message in the SI message set, m is an integer greater than 1, and mod is the modulo operator. When the network device performs the above formula (2) on each SI message in the SI message set, if Y is 0, it means that the SI message is transmitted in the target common window, that is, the network device sends the SI message in the target common window at this time; if Y is not 0, it means that the SI message is not transmitted in the target common window, that is, the network device does not send the SI message in the target common window at this time.

[0105] For example, the SI message set includes SI message #a1, SI message #a2, SI message #a3 and SI message #a4, and the periods of these four SI messages are rf8 (80ms), rf16 (160ms), rf24 (240ms) and rf8 (80ms), respectively; the period of the common window is the greatest common divisor of the periods of these four SI messages, that is, the period of the common window is rf8; t1 is rf32 (320ms). In this case, the target common window sequence number wid = floor(rf32 / rf8) = 4; for SI messages #a1 and #a4, Y = 4 mod(rf8 / rf8) = 0, meaning SI messages #a1 and #a4 are sent within the target common window; for SI message #a2, Y = 4 mod (rf16 / rf8) = 0, meaning SI message #a2 is sent within the target common window; for SI message #a3, Y = 4 mod(rf24 / rf8) = 1, meaning Y is not equal to 0, and therefore SI message #a3 is not sent within the target common window. Through the above calculations, the network device can determine that SI messages #a1, #a2, and #a4 are sent within the target common window.

[0106] Furthermore, in the first possible implementation, the target common window number is a natural number, i.e., wid is a natural number. When wid is 0, i.e., when the target common window is the first common window, the network device performs the above formula (2) operation on each SI message in the SI message set, and the result is Y=0. At this time, each SI message in the above SI message set needs to be sent in the first common window. In this case, if the length of the first common window is sufficient to send all SI messages, i.e., the length of the first common window is sufficient to send all SI messages, then the network device can send all SI messages. If the length of the first common window is insufficient to cover the duration of sending all SI messages (i.e., all SI messages in the SI message set), the network device can truncate some or all of the SI messages in the SI message set before sending them. For example, it can truncate each SI message at the halfway point and send the first half of the content of each SI message in the SI message set. In subsequent common windows, when the network device determines at least one SI message that needs to be sent in the current common window, it can first determine whether there is any SI message that has not been completely sent before. If so, the remaining content of the SI message can be sent in the current common window. This process continues until all SI messages are sent completely.

[0107] In this embodiment, the network device can quickly and accurately calculate one or more SI messages that need to be sent in the current public window (the target public window) based on the period of the public window and the period of each SI message in the SI message set, using the above formulas (1) and (2). Furthermore, this method eliminates the need for the network device to store a large scheduling table (such as a list of all SI messages to be sent in each public window in chronological order), thus saving network device memory. It also facilitates the dynamic addition and removal of SI messages; for example, when adding a new SI message, only the SI message needs to be judged using the above formula, and the scheduling table is wirelessly regenerated without affecting the sending timing of existing SI messages.

[0108] In the second possible implementation, the network device acquiring at least one SI message may specifically include: the network device acquiring the sequence number of a target public window based on a second duration and the period of a public window, and determining at least one SI message based on the sequence number of the target public window, the period of each SI message in the aforementioned SI message set, and the period of the public window. Specifically, the sequence number of the target public window is the value obtained by dividing the second duration by the period of the public window and rounding down, where the second duration is the difference between the current time point and a preset start time point, and the current time point is the time point at which the network device determines the sequence number of the target public window; the remainder of the sequence number of the target public window divided by a first value is zero, and the SI message to be broadcast belongs to at least one SI message; the first value is a multiple of the period of each SI message in the SI message set and the period of the public window. That is, the at least one SI message is determined based on the sequence number of the target public window, the period of each SI message in the aforementioned SI message set, and the period of the aforementioned public window.

[0109] The sequence number of the target public window, the method for calculating the sequence number of the target public window (formula (1) above), and the method for sending SI messages by the target public window (formula (2) above) can be referred to the relevant introduction in the first possible implementation above, and will not be repeated here.

[0110] A broadcast SI message can be understood as an SI message that does not require on-demand request. An on-demand SI message can be understood as an SI message that the network device does not broadcast periodically, but only sends after the terminal device explicitly requests it. Furthermore, on-demand SI messages can be predefined by the protocol, or pre-configured in both the network device and the terminal device, or pre-configured in the network device and sent by the network device to the terminal device.

[0111] After obtaining one or more SI messages (denoted as SI message #1) that can be sent in the target public window according to the above formula (2), the network device can further determine whether each SI message in SI message #1 is a SI message that needs to be broadcast, or in other words, it can further determine whether each SI message in SI message #1 is an SI message that is requested on demand.

[0112] If all SI messages in SI message #1 are SI messages that need to be broadcast, that is, there are no SI messages that are requested on demand in SI message #1, then at least one SI message associated with the target common window is SI message #1. In this case, the network device can send or broadcast SI message #1 in the target common window.

[0113] If SI message #1 contains SI messages that do not need to be broadcast, i.e., if SI message #1 contains on-demand requested SI messages, the network device can filter or remove these on-demand requested SI messages from SI message #1, resulting in one or more SI messages after the on-demand requested SI messages have been filtered out (denoted as SI message #2, i.e., at least one SI message). At this point, at least one SI message associated with the target common window is SI message #2, and the network device sends or broadcasts SI message #2 within the target common window. This avoids the network device broadcasting on-demand requested SI messages, thereby saving radio resources, reducing signaling overhead, and lowering the network device's power consumption.

[0114] The first and second possible implementations described above illustrate the specific methods by which a network device acquires at least one SI message associated with a target common window. The network device can acquire the SI message to be sent in the target common window at the start of the target common window (the start time of the target common window); or it can acquire the SI message to be associated with the target common window before the start of the target common window, such as within a preset time period before the start of the target common window, or at a certain time point after the previous common window and before the target common window. The timing of the network device acquiring the above at least one SI message can be flexibly set according to the actual situation and is not limited.

[0115] S502, the network device sends at least one SI message in the target common window. Correspondingly, if the terminal device determines that at least one SI message associated with the target common window contains the target SI message, it receives the target SI message from the network device in the target common window.

[0116] The at least one SI message can be referred to the relevant description in S501 above, and will not be repeated here. After obtaining at least one SI message, the network device can send or broadcast the SI messages sequentially in the target common window according to the priority of each SI message in descending order of priority. The method for determining the priority of SI messages can refer to the prior art, and will not be repeated here.

[0117] The target SI message is the SI message that the terminal device wants to acquire or receive; and the network device is not concerned with the target SI message that the terminal device wants to acquire or receive. The target SI message can be one or more SI messages. When at least one SI message is multiple SI messages, the target SI message can be one or more SI messages; when at least one SI message is a single SI message, the target SI message is a single SI message.

[0118] The target SI message includes the target SIB that the terminal device wants to obtain; the terminal device can determine the target SI message based on the target SIB it wants to obtain. For example, the terminal device can obtain different mapping relationships between SI messages and SIBs (such as association information, described below); when the terminal device needs to obtain the target SIB, the terminal device can determine the SI message containing the target SIB based on the target SIB and the mapping relationship, and this SI message is the target SI message.

[0119] There are several ways for a terminal device to determine whether at least one SI message associated with a target common window contains a target SI message. For example, a network device can send a first message to indicate the at least one SI message. In this case, the terminal device can determine whether the at least one SI message contains the target SI message based on the first message. Alternatively, the terminal device can determine whether the target common window is a common window associated with the target SI message based on the period of the target SI message and the period of the common window. These will be described in detail below.

[0120] In a first possible implementation, before the network device sends at least one SI message in the target common window, or before the terminal device receives the target SI message from the network device in the target common window, the method may further include: the network device sending a first message in the target common window, and correspondingly, the terminal device receiving the first message in the target common window, wherein the first message is used to indicate at least one SI message associated with the target common window; the terminal device determines the target SI message associated with the target common window based on the first message.

[0121] The first message can be downlink control information (DCI). By instructing at least one SI message to be sent within the target common window using existing messages, resource utilization can be improved and transmission latency reduced. Of course, the first message can also be other types of messages; the specific settings can be flexibly configured according to actual needs without limitation.

[0122] The association of target SI messages with the target common window can be understood as: the network device actively sends or broadcasts target SI messages within the target common window. That is, the terminal device does not need to request the network device to send target SI messages.

[0123] A network device can send the first message at the start time of the target common window. For example, if the network device obtains at least one SI message that needs to be sent in the target common window before it starts, then the network device can send the first message at the start time of the target common window. Alternatively, the network device can send the first message after the target common window starts but before sending at least one SI message. For example, the network device can obtain at least one SI message at the start of the target common window and send the first message upon obtaining that at least one SI message.

[0124] In this embodiment, the network device can broadcast a first message. After receiving the first message, the terminal device can determine, based on the first message, at least one SI message to be sent within the target common window. Thus, the terminal device does not need to calculate the common window where different SI messages appear, thereby reducing its computational overhead.

[0125] Furthermore, the first message may carry the identifier (ID) of each SI message in the aforementioned at least one SI message, so as to indicate at least one SI message to be sent in the target common window through the ID of the SI message. In the embodiments of this application, the ID of the SI message may be the order of the SI messages in the scheduling information list of SI messages in SIB1 (such as the aforementioned schedulingInfoList), such as the ID of the first SI message in the list being "0", the ID of the second SI message being "2", and so on. The ID of the SI message may also be the ID assigned by the network device to each SI message in the aforementioned SI message set.

[0126] Alternatively, the first message may carry a bit string to indicate at least one of the aforementioned SI messages, thereby indicating at least one SI message to be sent in the target public window.

[0127] For example, the first message carries a bit string used to indicate at least one SI message. Before the network device sends the first message in the target common window, or before the terminal device receives the first message in the target common window, the method may further include: the network device sending first information, and correspondingly, the terminal device receiving first information from the network device, wherein the first information is used to indicate the mapping relationship between each bit in the bit string and each SI message in the SI message set; the terminal device determining the target common window associated with the target SI message based on the first message may specifically include: the terminal device determining the target common window associated with the target SI message based on the bit string and the first information.

[0128] The first message can be carried in SIB1. Sending the first message through the existing SIB1 can improve resource utilization and reduce transmission latency. Of course, the first message can also be sent through other existing messages (such as MIB) or newly defined messages. The specific settings can be flexibly configured according to the actual situation without any restrictions.

[0129] The first piece of information can include the length of the bit string and the bit mapping. The length of the bit string can be the number of bits it contains, such as 5 bits, 6 bits, or 10 bits. The bit mapping can be understood as the rules for mapping each bit in the bit string to each SI message in the SI message set. For example, the (q-1)th bit in the bit string is mapped to the SI message with index q, such as the SIq message, where q is a positive integer.

[0130] Furthermore, a bit value of 0 or 1 can indicate whether the SI message corresponding to that bit is associated with the target common window, or in other words, whether the SI message corresponding to that bit is actively sent by the network device within the target common window. For example, a bit value of 0 in the bit string indicates that the SI message associated with that bit is not associated with the target common window, meaning the SI message is not actively sent by the network device within the target common window. A bit value of 1 in the bit string indicates that the SI message associated with that bit is associated with the target common window, meaning the SI message is actively sent by the network device within the target common window. Alternatively, a bit value of 1 in the bit string indicates that the SI message associated with that bit is not associated with the target common window, while a bit value of 0 in the bit string indicates that the SI message associated with that bit is associated with the target common window. This rule can be predefined by the protocol, pre-set in network devices and terminal devices, or sent by the network device to the terminal device via information. It can be flexibly set according to the actual situation without restriction.

[0131] After receiving the first information, the terminal device can store or remember the association between each bit in the bit string sent by the network device and the SI message, based on the first information. After receiving the bit string from the network device, the terminal device can determine the transmission status of each SI message in the target common window based on its stored association.

[0132] For example, the SI message set includes four SI messages: SI message #b1, SI message #b2, SI message #b3, and SI message #b4. The first piece of information includes the length of the bit string and a bit mapping. The length is 4 bits, and the bit mapping is as follows: the 0th bit in the bit string is mapped to SI message #b1, the 1st bit to SI message #b2, the 2nd bit to SI message #b3, and the 3rd bit to SI message #b4. Furthermore, the protocol predefines that when a bit in the bit string is 0, it indicates that the SI message associated with that bit is not actively sent by the network device within the target common window; when a bit in the bit string is 1, it indicates that the SI message associated with that bit is actively sent by the network device within the target common window.

[0133] After receiving the first information, the terminal device can store the association between each bit in the bit string indicated by the bit mapping and the SI message. The network device broadcasts bit string #b in the target common window, where bit string #b is 1011. After receiving bit string #b, the terminal can determine, based on the mapping relationship, that SI messages #b1, #b2, and #b4 will be sent in the target common window.

[0134] In this embodiment, the network device broadcasts first information, enabling the terminal device to determine at least one SI message associated with the target common window based on the bit string subsequently sent by the network device. Since the information corresponding to each SI message occupies only 1 bit in the bit string, meaning N SI messages only require N bits for indication (N is a positive integer), this reduces the amount of data transmitted and lowers the communication overhead of the network device. Furthermore, the terminal device only needs to determine which SI messages are associated with the target common window based on the bit string sent by the network device, without needing to attempt to receive and parse each SI message, thus saving energy consumption.

[0135] Furthermore, in this embodiment, the network device can also add bits to the bit string to indicate warning information. For example, when a sudden event requires warning in a target public window, the network device can indicate that warning information will be sent in the target public window through the corresponding bits in the bit string. In this case, the first information can also indicate the mapping relationship between the newly added bits in the bit string and the warning information. After the network device sends the bit string in the public window, the terminal device can determine whether the public window will broadcast warning information based on the bit string, thereby receiving the warning information in a timely manner.

[0136] In the second possible implementation, the terminal device can calculate the common window (denoted as common window #1) associated with the target SI message based on the period of the target SI message, and determine whether the target common window is common window #1. If the target common window is common window #1, the terminal device determines that the target common window is associated with the target SI message.

[0137] For example, if the period of the target SI message is rf16, then the target SI message will appear in the common window #1 corresponding to the start times of rf16, rf32, rf48, etc. (i.e., start times that are multiples of rf16). When the terminal device wakes up the target common window, it can determine whether the target common window is common window #1. If the target common window is #1, the terminal device determines that the target common window is associated with the target SI message.

[0138] In this way, the terminal device can determine the common window in which the target SI message appears on its own, without the network device having to indicate the SI message associated with the common window through a message in each common window, thereby reducing the communication overhead of the network device.

[0139] The above describes how a terminal device determines whether a target common window should send a target SI message. When there are multiple SI messages, the terminal device can first receive multiple SI messages on a single time-frequency resource, and then parse these multiple SI messages to obtain the target SI message; alternatively, the terminal device can receive the target SI message on the time-frequency resource corresponding to the target SI message (described below). The specific configuration can be adjusted according to the actual situation and is not restricted.

[0140] S503, the terminal device obtains the target SIB based on the target SI message.

[0141] After obtaining the target SI message, the terminal device can decode the target SI message to obtain the target SIB. The specific implementation of the terminal device obtaining the SIB from the SI message can be found in existing technologies and will not be elaborated here.

[0142] In summary, in this embodiment, by setting a common window whose period is the greatest common divisor of the periods of all SI messages in the SI message set, one or more SI messages with periods that are multiples of each other can be sent in the same common window (i.e., different SI messages do not need to be sent in different SI windows). This shortens the time it takes for the terminal device to obtain SI messages, allowing the terminal device to obtain the required SI messages more quickly. Furthermore, it reduces the power consumption of the terminal device when it obtains multiple desired SI messages through a single common window. Moreover, based on the characteristic that the periods of SI messages are multiples of each other, by matching the type of SI message sent in the common window with the period of the SI message, SI messages can be sent reasonably in different common windows according to their frequency of occurrence, enabling the orderly and conflict-free periodic transmission of SI messages.

[0143] Optionally, in conjunction with the above embodiments, before the network device sends at least one SI message in the target common window, or before the terminal device receives the target SI message from the network device in the target common window, the above method may further include: the network device sending a second message in the target common window, and correspondingly, the terminal device receiving the second message in the target common window, wherein the second message indicates transmission configuration parameters for transmitting at least one SI message; the terminal device receiving the target SI message from the network device in the target common window may specifically include: the terminal device receiving the target SI message in the target common window based on the transmission configuration parameters.

[0144] The second message can be a DCI. Using existing message instructions to transmit at least one SI message's transmission configuration parameters can improve resource utilization and reduce transmission latency. Of course, the second message can also be other types of messages; the specific settings can be flexibly configured according to actual needs without limitation.

[0145] The transmission configuration parameters may include time and frequency resources for transmitting at least one SI message.

[0146] When there are multiple SI messages, the time-frequency resource can be a time-frequency resource used by at least one SI message. In this case, the at least one SI message can be sent on the time-frequency resource through a message (that is, multiple SI messages are encapsulated into the same transport block), and the terminal device can first receive the at least one SI message on the time-frequency resource, and then parse the target SI message from the received at least one SI message.

[0147] Alternatively, when there are multiple SI messages, the time-frequency resources can be multiple time-frequency resources corresponding to at least one SI message. For example, these multiple time-frequency resources can be time-frequency resources corresponding to each SI message in the at least one SI message. In this case, different SI messages in the at least one SI message are transmitted on different time-frequency resources, and the terminal device can receive the target SI message on the time-frequency resource corresponding to the target SI message. As another example, each of the multiple time-frequency resources can correspond to at least some of the SI messages in the at least one SI message. For instance, when there are 5 SI messages in the at least one SI message, the network device transmits 3 SI messages through time-frequency resource #a1 and the remaining 2 SI messages through time-frequency resource #a2. In this case, the time-frequency resources used to transmit the at least one SI message are time-frequency resource #a1 and time-frequency resource #a2.

[0148] Furthermore, in this scenario, different time-frequency resources can be associated with each SI message in at least one SI message to clearly indicate the time-frequency resources on which each SI message in at least one SI message is transmitted. That is, the transmission configuration parameters can then include the time-frequency resources and the IDs of the SI messages transmitted on those resources.

[0149] Transmission configuration parameters may also include a modulation and coding scheme (MCS). This MCS can be understood as a parameter table entry that maps modulation schemes (such as quadrature phase shift keying (QPSK), quadrature amplitude modulation (QAM), 64QAM) to channel coding rates (such as 1 / 3, 1 / 2, 3 / 4) as index values. It can be used to control the balance between the rate and reliability of wireless data transmission. The specific principle of the MCS can be found in existing technologies. In this embodiment, the network device can determine the MCS carried in the second message based on the current channel state (such as the latest channel quality indicator (CQI) reported by the terminal device, the block error rate in the previous common window of the target common window, etc.). Furthermore, if the terminal device does not receive the MCS in the target common window, it can use the most recently received MCS, such as the MCS received in the previous common window of the target common window.

[0150] The second message can be sent after the first message. For example, the network device can send the second message immediately after sending the first message; or, the network device can send the second message after a preset interval (e.g., 1ms or 2ms) after sending the first message. In this way, the terminal device can first determine whether the target common window will send the desired target SI message based on the first message. Once it determines that the target common window is associated with the target SI message, it continuously listens to receive the second message and, based on the second message, determines how to obtain the target SI message.

[0151] Furthermore, when transmitting at least one SI message using multiple time-frequency resources, the network device can determine the order of the SI messages within the at least one SI message after prioritizing them. Following this order, before transmitting a portion of the SI messages (denoted as SI message #B1), the network device can transmit a second message to indicate the transmission configuration parameters corresponding to SI message #B1, such as the time-frequency resources used for transmitting SI message #B1, the ID of SI message #B1, and the MCS. After transmitting SI message #B1 and before transmitting the other SI messages within the at least one SI message (denoted as SI message #B2), the network device can transmit a second message to indicate the transmission configuration parameters corresponding to SI message #B2, such as the time-frequency resources used for transmitting SI message #B2, the ID of SI message #B2, and the MCS. The network device continues according to the above rules until all at least one SI message has been transmitted.

[0152] In this embodiment, the network device can broadcast a second message within the target common window. After receiving the second message, the terminal device can obtain the target SI message based on transmission configuration parameters. This could involve receiving the target SI message or at least one SI message containing the target SI message on the time-frequency resources specified in the transmission configuration parameters, or demodulating the received symbols based on the MCS (Multi-Signal System) and performing channel decoding on the demodulated bits. This ensures that the terminal device successfully obtains the target SI message.

[0153] Optionally, in conjunction with the above embodiments, before the network device sends at least one SI message in the target common window, or before the terminal device receives the target SI message from the network device in the target common window, the above method may further include: the network device sending second information, and correspondingly, the terminal device receiving the second information from the network device, wherein the second information includes a common window period and a window start reference point, or the second information includes a common window length, or the second information includes a common window period, a window start reference point, and a common window length; the terminal device receiving the target SI message from the network device in the target common window may specifically include: the terminal device receiving the target SI message in the target common window according to the second information.

[0154] The second information can be sent to the terminal device before the network device sends the SI message, that is, before the network device sends the SI message for the first time in the first common window. For example, the second information can be carried in system information, such as in SIB1. Sending the second information through the existing SIB1 can improve resource utilization and reduce transmission latency. Of course, the first information can also be sent through other existing messages (such as MIBs) or newly defined messages; the specific settings can be flexibly configured according to the actual situation without limitation.

[0155] The public window cycle is used to indicate the cycle of the public window. For details, please refer to the relevant introduction above, which will not be repeated here.

[0156] The window start reference point indicates the offset of the start time of a common window relative to the start time of the window cycle to which it belongs. This offset is less than the length of the common window. For example, if the cycle of the common window is rf16, the preset start time is SFN=0, and the window start reference point is 10ms, then in a cycle starting at SFN=0, the start time of the common window in that cycle needs to be increased by 10ms from the start time of that cycle, i.e., the start time of the common window is SFN=1; in a cycle starting at SFN=16, the start time of the common window in that cycle needs to be increased by 10ms from the start time of that cycle, i.e., the start time of the common window is SFN=17.

[0157] The common window length indicates the duration of the common window. The duration of the common window can be understood as the length of time the common window lasts, and this duration can be less than the common window's period. For example, if the common window's period is rf16 (160ms), the common window's length is 40ms.

[0158] In this embodiment, the network device can broadcast second information. After receiving the common window period and the window start reference point, the terminal device can calculate the start time of each common window based on these two pieces of information. Continuing the example above, with the preset start time point SFN=0, the window start reference point 0, and the common window period rf16, the start times of each common window in chronological order are rf16, rf32, rf48, rf64, etc. In this way, the terminal device can determine whether the target SI message it wants is sent in the common window at the start time of each common window, that is, whether the terminal device is listening to the common window. For example, the terminal device can determine whether the target SI message it wants is sent in the target common window by receiving the first message sent within the target common window, and listen to the target common window when the target SI message is sent.

[0159] After receiving the common window length, the terminal device can listen to the target common window based on the common window length when it determines that it will receive the target SI message in the target common window.

[0160] By sending second information to the terminal device, when the second information includes the common window period and the window start reference point, the terminal device can calculate the start time of each common window based on the common window period and the window start reference point. This means the network device does not need to send the start time of each common window to the terminal device, thus saving communication resources and reducing the communication overhead of the network device. Furthermore, when the second information includes the common window length, when the terminal device receives the target SI message within the target common window, it can monitor the target common window based on the common window length. This allows the terminal device to promptly shut down the receiver or enter sleep mode when the target common window ends, thereby avoiding unnecessary power consumption by the terminal device.

[0161] In addition, the aforementioned public window period, public window length, and window start reference point can be sent together with the second information, or they can be sent through different information or messages. The specific settings can be flexibly configured according to the actual situation without any restrictions.

[0162] Furthermore, before the network device sends at least one SI message in the target common window, or before the terminal device receives the target SI message from the network device in the target common window, the above method may further include: the network device sending third information, and correspondingly, the terminal device receiving the third information from the network device, wherein the third information includes at least one of the following: association information, period multiple information; the terminal device receiving the target SI message in the target common window based on the second information may specifically include: the terminal device receiving the target SI message in the target common window based on the second information and the third information.

[0163] The third information can be sent to the terminal device before the network device sends the SI message, that is, before the network device sends the SI message for the first time. For example, the third information can be carried in system information, such as in SIB1. Sending the third information through the existing SIB1 can improve resource utilization and reduce transmission latency. Of course, the third information can also be sent through other existing messages (such as MIBs) or newly defined messages; the specific settings can be flexibly configured according to the actual situation without limitation.

[0164] The third and second information can be carried in SIB1. Sending the third and second information through the existing SIB1 can further improve resource utilization and reduce transmission latency. In addition, this method allows the terminal device to obtain the second and third information with a single message, thereby avoiding the need for the radio frequency and baseband sections of the terminal device to frequently power on to receive multiple messages, thus reducing the power consumption of the terminal device.

[0165] Association information is used to indicate the SIBs associated with each SI message in the SI message set. In other words, association information indicates the association relationship between each SI message and an SIB (all SIBs except SIB1) in the SI message set. An associated SIB can be understood as one or more SIBs included (or carried) in the SI message. Different SI messages are associated with different SIBs. For example, an SI message set includes SI messages #c1, #c2, #c3, and #c4. SI message #c1 is associated with SIB2, SI message #c2 is associated with SIB3 and SIB4, SI message #c3 is associated with SIB5, and SI message #c4 is associated with SIB5 and SIB6 (denoted as example #c).

[0166] The period multiple information is used to indicate the ratio between the period of each SI message in the SI message set and the period of the common window. The period multiple information can be multiple values ​​k, each k corresponding to the quotient obtained by dividing the period of each SI message in the SI message set by the period of the common window. For example, if the SI message set includes SI messages #d1, #d2, and #d3, with periods of rf8, rf16, and rf48 respectively, and the period of the common window is rf8, then k for SI message #d1 is 1, k for SI message #d2 is 2, and k for SI message #d3 is 6. That is, the period multiple information can be 1, 2, and 6 (denoted as example #d). It can be understood that in this embodiment, the period of the common window is the greatest common divisor of the periods of all SI messages in the SI message set, thus ensuring the ratio between the period of each SI message in the SI message set and the period of the common window.

[0167] In this embodiment, the network device can broadcast third information. After receiving the association information, the terminal device can determine the SI message containing the target SIB it wants to obtain, i.e., the target SI message, based on the association information. Furthermore, after determining the target SI message to be obtained, the terminal device can establish a list of SI messages it is interested in. After determining that at least one SI message is associated with the target public window, the terminal device can compare the list of SI messages with the at least one SI message to determine whether the target public window is associated with the target SI message. For example, after receiving the first message mentioned above, the terminal device can compare the list of SI messages with at least one SI message (such as a bit string) indicated by the first message to determine whether the target public window is associated with the target SI message. Continuing with example #c, if the terminal device wants to obtain SIB2 and SIB3, it can determine, based on the association information, that SIB2 is associated with SI message #c1 and SIB3 is associated with SI #c2. That is, the terminal device needs to obtain SI messages #c1 and #c2, and the terminal device can establish a list of SI messages it is interested in, i.e., SI-table{SI message #c2, SI message #c3}.

[0168] After receiving the period multiple information, the terminal device can determine the start time of the common window for sending the target SI message based on the period multiple information and the period of the common window. Continuing with the previous example #d, the target SI message is SI message #d2, the k value corresponding to SI message #d2 is 2, and the period of the common window is rf8. Then the period of SI message #d2 is rf16, and the start time of the common window for sending the target SI message is: rf16, rf32, rf48, etc. In this embodiment, the terminal device can determine the start time of the common window for sending the target SI message based on the period multiple information and the period of the common window after determining the target SI message. Alternatively, after receiving the period multiple information, the terminal device can also calculate the period of each SI message in the SI set based on the period multiple information, and calculate at least one SI message associated with each common window based on the period, such as calculating at least one SI message associated with each common window at the beginning (or before) of each common window. The specific implementation of the terminal device calculating at least one SI message associated with each common window (denoted as implementation #1) is similar to the specific implementation of the network device calculating at least one SI message associated with each common window (denoted as implementation #2). The difference is that implementation #1 is calculated by the terminal device, while implementation #2 is calculated by the network device. The similarities can be understood by referring to the aforementioned related introductions, and will not be repeated here. Furthermore, when calculating the sequence number of a common window, the terminal device can calculate it based on the duration between the start time point of the common window and a preset start time point.

[0169] By sending third information to the terminal device, when the third information includes associated information, the terminal device can accurately and quickly determine the target SI message based on the associated information. The terminal device can calculate the period of each SI message based on the period multiple information and the period of the common window. Compared with the period of each SI message sent by the network device, the network device can reduce the communication overhead of the network device by sending the period multiple information.

[0170] In addition, the aforementioned related information and period multiple information can be sent together through a third-party message, or they can be sent through different messages or information. The specific settings can be flexibly configured according to the actual situation, without any restrictions.

[0171] The above content describes the various types of information that network devices send or broadcast before sending SI messages, such as first information, second information, and third information. For ease of understanding, the following section will combine... Figure 6 This section uses a specific example to illustrate the process of a base station (i.e., the network device mentioned above) sending various types of information in SIB1.

[0172] like Figure 6 As shown, the process of a base station sending various types of information is as follows: S601, Base station defines common SI window basic parameters.

[0173] The basic parameters of the common SI window include: common SI window period, common SI window length, and window start reference point.

[0174] It can be understood that the basic parameters of the SI window correspond to the second information mentioned above, the common SI window period corresponds to the common window period mentioned above, and the common SI window length corresponds to the common window length mentioned above.

[0175] S602, the base station groups SIBs with the same period into a group and puts the group of SIBs into the same SI message.

[0176] The specific implementation of S602 can be found in existing technologies, and will not be elaborated here.

[0177] S603, the base station assigns an ID and a transmission cycle multiple k to each SI message in all SI messages.

[0178] All SI messages correspond to the above set of SI messages.

[0179] k is the multiple of the SI message period relative to the common SI window period. k can be found in the relevant introduction in the period multiple information above, and will not be repeated here.

[0180] S604, Base station configuration for the format of BitString scheduling indication.

[0181] The format of the BitString scheduling instruction includes: the length of the bit string, and the bit mapping.

[0182] It is understandable that the format of the BitString scheduling instruction can also be called the BitString scheduling instruction configuration, or other possible names. The format of the BitString scheduling instruction corresponds to the first piece of information mentioned above, and the length of the bit string and the bit mapping can be found in the relevant introduction in the first piece of information, which will not be repeated here.

[0183] S605, base station configuration SIB1.

[0184] The aforementioned SIB1 includes: basic parameters of the common SI window, schedulingInfoList, and the format of the BitString scheduling instruction. The basic parameters of the common SI window can be found in the relevant description in S601, and will not be repeated here. The schedulingInfoList includes: the SIB information contained in each SI message among all the aforementioned SI messages, and the transmission period multiple of the SI messages. The schedulingInfoList may also include other information from the prior art schedulingInfoList, which does not include the period of the SI messages.

[0185] Based on the above information, the base station can construct SIB1 at the radio resource control (RRC) layer.

[0186] It can be understood that schedulingInfoList corresponds to the third information mentioned above, the SIB information contained in each SI message corresponds to the related information mentioned above, and the transmission cycle multiple of the SI message corresponds to the cycle multiple information mentioned above.

[0187] S606, the base station sends the encoded SIB1 transport block to the medium access control (MAC) layer for scheduling, and then transmits it at the physical (PHY) layer.

[0188] In other words, after constructing SIB1, the RRC layer of the base station can encode and channel-code SIB1 to obtain a transport block (i.e., the SIB1 transport block), and then hand the encoded transport block over to the MAC layer. Upon receiving the transport block, the MAC layer determines the transmission time and physical resources (such as time slots and resource blocks) and sends the organized data (plus a MAC header, etc.) to the PHY layer. The PHY layer is responsible for the final signal processing, such as scrambling, modulation, layer mapping, precoding, and resource mapping, generating an orthogonal frequency division multiplexing (OFDM) signal, which is then transmitted through the antenna.

[0189] For specific implementation details of S606, please refer to existing technologies; they will not be elaborated here.

[0190] It is understood that the specific implementations of S601 to S606 can be understood by referring to the aforementioned content, and will not be repeated here.

[0191] Optionally, in conjunction with the above embodiments, when there are multiple SI messages in the at least one SI message, each SI message in the at least one SI message is distinguished by a different logical channel (LC) identifier (ID) in the MAC subheader.

[0192] The above-mentioned number of SI messages can be understood as: at least one SI message is multiple SI messages.

[0193] The MAC header is the header information of a MAC sub-protocol data unit (SUB PDU). The MAC header is typically located at the very beginning of the MAC SUB PDU and is used to describe and identify the data portion.

[0194] A MAC Sub-Bundle is the basic unit that constitutes a MAC protocol data unit (PDU). A MAC Sub-Bundle can consist of a MAC header and a data portion. The MAC header includes the LCID.

[0195] The data portion can be a MAC service data unit (SDU), a MAC control element (CE), or padding bits.

[0196] It is understandable that the specific principles of MAC SUBPDU, MAC PDU, MAC subheader, and LCID can be found in existing technologies, and will not be elaborated here.

[0197] After a network device receives at least one SI message, if there are multiple SI messages and these SI messages reuse the same MAC PDU, the network device can encapsulate each SI message into a MAC SUBPDU and fill in the corresponding LCID value in the MAC subheader of each SI message according to the logical channel associated with the different SI messages. The LCID values ​​are different for different SI messages.

[0198] After receiving at least one SI message, the terminal device can parse different MACSUBPDUs through the MAC layer. At this point, the terminal device can determine the SI message corresponding to the MAC SUBPDU based on the association between the LCID and different SI messages, as well as the LCID in the parsed different MACSUBPDUs. The association between the LCID and different SI messages can be predefined by the protocol, pre-set in the network device and terminal device, or sent from the network device to the terminal device. The specific configuration can be flexibly set according to the actual situation and is not limited.

[0199] The above method enables network devices to send multiple SI messages using the same time-frequency resource, thereby improving resource utilization and reducing signaling overhead. Furthermore, by distinguishing different SI messages using different LCID values, terminal devices can quickly and accurately differentiate between multiple SI messages received, ensuring that the terminal device obtains the target SI message.

[0200] Optionally, in conjunction with the above embodiments, the at least one SI message does not include an on-demand requested SI message. Before the terminal device receives the target SI message from the network device in the target common window, the method may further include: if the target SI message is an on-demand requested SI message and the terminal device determines that the target SI message can be transmitted in the target common window, the terminal device sends a third message to the network device, and the network device receives the third message from the terminal device accordingly, wherein the third message is used to request the network device to send the target SI message; in response to the third message, the network device sends the target SI message to the terminal device, and the terminal device receives the target SI message from the network device accordingly.

[0201] The on-demand SI message can be referred to the foregoing description, and will not be repeated here. In the embodiments of this application, the network device can send information to the terminal device to indicate the on-demand SI message. The terminal device can determine whether the target SI message is an on-demand SI message based on the information; or, the on-demand SI message can be predefined by protocol, and the terminal can determine whether the target SI message is an on-demand SI message according to the predefined content of the protocol.

[0202] The transmission of a target SI message within a target common window can be understood as follows: the target SI message should be sent within the target common window, calculated based on the period of the target SI message and the period of the common window; or, in other words, the first duration is an integer multiple of the period of the target SI message.

[0203] The target SI message being an on-demand requested SI message can mean that the network device does not broadcast (or actively send) the target SI message in the target common window, that is, the terminal device needs to request the network device to send the target SI message.

[0204] In this embodiment, when a terminal device determines that it needs to obtain a target SI message, it can determine whether the target SI message is an on-demand requested SI message. If the target SI message is an on-demand requested SI message, the terminal device can determine a common window that can send the target SI message. When the target common window is a common window that can send the target SI message, the terminal device requests the network device to send the target SI message through a third message. After receiving the third message, the network device can send the target SI message to the terminal device based on the third message. In this way, it can be ensured that the terminal device obtains the target SI message it needs.

[0205] Furthermore, network devices can broadcast target SI messages when the number of requests received from the network device to send a target SI message exceeds a certain threshold. This eliminates the need for the network device to send target SI messages separately to different terminal devices multiple times, thus saving communication resources and reducing the network device's energy consumption.

[0206] Optionally, in conjunction with the above embodiments, the method may further include: the terminal device entering a sleep state when it is determined that the target public window will not send a target SI message.

[0207] The terminal device can determine whether to send a target SI message in the target public window based on the period of the target SI message and the period of the public window. For details, please refer to the above-mentioned introduction.

[0208] Alternatively, the terminal device can determine that the target public window will not send the target SI message based on a fourth message sent or broadcast by the network device in the target public window. For example, before the terminal device enters a sleep state, the above method may further include: the network device sending a fourth message in the target public window, and correspondingly, the terminal device receiving the fourth message in the target public window, wherein the fourth message is used to indicate at least one SI message associated with the target public window; the terminal device determining that the target SI message will not be sent in the target public window based on the fourth message (i.e., the at least one SI message), such as by determining that the target SI message is not included in the at least one SI message.

[0209] The fourth message is similar to the first message mentioned above, except that the fourth message indicates that at least one SI message does not include the target SI message, while the first message indicates that at least one SI message includes the target SI message. The similarities can be understood by referring to the relevant description in the first message mentioned above, and will not be repeated here.

[0210] In this embodiment of the application, when the terminal device determines that the target common window does not send the target SI message, that is, when the terminal device determines that the target SI message cannot be obtained in the target common window, it enters a sleep state, which can save the power consumption of the terminal device.

[0211] In the embodiments of this application, different SI messages can be expressed in different ways. For example, the first SI message in the SI message set can be represented as SI message 1, SI-1, SI1, or other possible representations. This application does not limit this.

[0212] The above content provides an overview of communication methods. For ease of understanding, the following section will combine... Figure 7 and Figure 8This section details the specific operation procedures of the base station (the aforementioned network equipment) and the UE (the aforementioned terminal equipment) in the above communication method.

[0213] like Figure 7 As shown, the base station scheduling method includes the following steps: S701, when the system time reaches the start time of the predetermined common window (denoted as common window #A1), the base station scheduler marks the common window #A1 as active.

[0214] Public window #A1 corresponds to the aforementioned Figure 5 The target public window in the illustrated embodiment.

[0215] The scheduler can be understood as a software module in the base station. When the base station scheduler marks a window as active, it means that the current public window needs to be processed, such as determining the SI message to be sent in the public window, the BitString corresponding to the SI message, etc. For details, please refer to S702 to S713 below.

[0216] In addition, the base station can execute S701 after executing the aforementioned S606.

[0217] S702, the serial number of the base station's common window #A1.

[0218] The sequence number wid of public window #A1 is calculated as follows: wid = floor( (SFN×10 + slot_offset) / co_period ); where (SFN×10 + slot_offset) is the current system time, corresponding to the current time point mentioned above. The calculation method for the sequence number of public window #A1 can be found in the previous section. Figure 5 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0219] S703, perform the following operation on the SIm message: Y = wid mod (SIm_period / co_period).

[0220] A SIm message can be understood as each SI message in the SI message set, or in other words, each SI message in the entire SI message set, where m is an integer greater than 1. This SI message set can be referenced above. Figure 5 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0221] The above formula can be referred to the previous one. Figure 5 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0222] S704, the base station determines whether the Y corresponding to the SIM message is 0.

[0223] If the Y corresponding to the SIm message is 0, then execute S705; if the Y corresponding to the SIm message is not 0, then execute S707.

[0224] S705, the base station determines whether the SIM message is an on-demand requested SI message.

[0225] If the SIm message is not an on-demand SI message, then execute S706; if the SIm message is an on-demand SI message, then execute S707.

[0226] S706, the base station sets the value of the (m-1)th bit of the constructed BitString scheduling instruction to 1.

[0227] BitString scheduling instruction corresponds to the aforementioned Figure 5 The bit string in the illustrated embodiment. Setting the (m-1)th bit of the BitString scheduling indicator to 1 indicates that the SIm message is actively sent by the base station in the common window #A1.

[0228] S707, the base station sets the value of the (m-1)th bit of the constructed BitString scheduling instruction to 0.

[0229] Setting the (m-1)th bit of the BitString scheduling indicator to 0 indicates that the base station does not actively send SIm messages in the public window #A1.

[0230] S708, the base station executes S703 until all SI messages have been processed.

[0231] All SI messages correspond to the aforementioned SI message set.

[0232] S709, the base station puts the generated BitString scheduling instruction into DCI#1 and sends DCI#1 on the PDCCH.

[0233] The above S709 can be understood as the dynamic scheduling of messages within the public window #A1.

[0234] S710, the base station arranges the scheduling order of SI messages according to the priority of the SI messages transmitted in the common window #A1.

[0235] The SI message transmitted in public window #A1 can be understood as: the SI message whose value at the corresponding position of the BitString scheduling indication is 1, that is, the SI message transmitted in public window #A1 is the SI message that the base station will actively send or broadcast.

[0236] The total number of SI messages transmitted in public window #A1 is N, where N is a positive integer.

[0237] S711, the base station allocates time and frequency resources for the i-th transmission SI message within the common window #A1, where i ranges from 1 to N and is a positive integer.

[0238] In other words, the base station allocates time-frequency resources for transmitting each SI message within the SI messages transmitted in the common window #A1. For example, when the SI message transmitted in the common window #A1 is a single SI message, the base station allocates time-frequency resources for this single SI message. As another example, when the SI message transmitted in the common window #A1 is multiple SI messages, the base station allocates corresponding time-frequency resources sequentially for each of these multiple SI messages, as detailed above. Figure 5 The relevant descriptions in the illustrated embodiments are for reference only and will not be repeated here.

[0239] S712, the base station constructs DCI#2 and sends DCI#2.

[0240] DCI#2 includes: the time-frequency resource, MCS and SI message ID corresponding to the i-th transmitted SI message, where i ranges from 1 to N and is a positive integer.

[0241] S713, the base station transmits the i-th SI message on the time-frequency resources allocated for the i-th transmitted SI message; the base station repeats the above S711 to S713 in the order of taking 1 to N in sequence according to i, and the scheduler stops scheduling when the window predetermined time of the common window #A1 ends.

[0242] The base station repeatedly executing S711 to S713 in the order of taking numbers from 1 to N in sequence can be understood as follows: Before sending the i-th SI message, the base station allocates time-frequency resources for transmitting each SI message, and constructs and sends a DCI#2 based on the time-frequency resources to indicate the transmission configuration parameters of the SI message. That is, in this case, the base station may send multiple different DCI#2s.

[0243] Furthermore, in this embodiment, if N SI messages can be transmitted using the same time-frequency resource, the base station can allocate a time-frequency resource for these N SI messages and, based on that time-frequency resource, construct and transmit a DCI indicating the transmission configuration parameters of the N SI messages. That is, the base station can transmit a DCI#2 at this time.

[0244] The end of the scheduled time for public window #A1 can be understood as the current time (system time) reaching the end time of public window #A1.

[0245] When the scheduled time for public window #A1 ends, the base station stops transmitting messages.

[0246] It is understood that the specific implementations of S701 to S713 mentioned above can refer to the foregoing. Figure 5 The relevant descriptions of the embodiments shown will not be repeated here.

[0247] like Figure 8 As shown, the method for a UE to receive an SI message includes the following steps: S801, the UE obtains SIB1 on the PDCCH and reads the format of the common SI window basic parameters, schedulingInfoList, and BitString scheduling instruction based on SIB1.

[0248] The formats of basic parameters for the common SI window, schedulingInfoList, and BitString scheduling instructions can be found in the preceding text. Figure 6 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0249] In S802, the UE determines which SI messages contain its required SIBs through the schedulingInfoList and establishes a list of SI messages it is interested in.

[0250] The UE can determine which SI messages contain the specific implementations of its required SIBs, and the list of SI messages the UE is interested in (SI-table) can be found in the aforementioned documentation. Figure 5 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0251] S803, the UE wakes up precisely at the start of each common window and receives DCI#1 sent by the base station.

[0252] The method by which the UE determines the start time of each common window can be referred to the above. Figure 5 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0253] For DCI#1, please refer to the aforementioned references. Figure 7 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0254] S804, the UE receives DCI#1, decodes DCI#1, and obtains the BitString scheduling instruction.

[0255] For DCI#2 and BitString scheduling instructions, please refer to the aforementioned [reference needed]. Figure 7 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0256] The UE can search for the DCI scrambled with a specific RNTI (such as SI-Indication-RNTI), i.e., DCI#2, at a predefined location. After successfully decoding DCI#2, the UE obtains a BitString scheduling indication.

[0257] S805, the UE compares the BitString scheduling instruction with its list of SI messages it is interested in.

[0258] S806, the UE determines whether the required SI message exists in the BitString scheduling instruction.

[0259] If the required SI message is not present in the BitString scheduling instruction, then execute S807. If the required SI message is present in the BitString scheduling instruction, then execute S808.

[0260] S807, the UE enters sleep mode.

[0261] S808, when the ID of the required SI message exists in the DCI#2 received by the UE, the UE reads the time-frequency resource #1 and MCS of DCI#2.

[0262] For DCI#2, please refer to the aforementioned references. Figure 7 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0263] The UE can determine the time-frequency resource #1 corresponding to the ID of the required SI message based on DCI#2.

[0264] S809, the UE receives the SI message on time and frequency resources #1 and obtains the required SIB information based on the SI message.

[0265] It is understood that the specific implementations of S801 to S809 mentioned above can refer to the foregoing. Figures 5 to 7 The relevant descriptions of the embodiments shown will not be repeated here.

[0266] It's also understandable that the above content describes the specific operation procedures of the base station and UE in the aforementioned communication method. For ease of understanding, the following will combine... Figure 9 Let's take a specific example to illustrate the above communication method.

[0267] The base station (the aforementioned network equipment) configures the periods of SI1, SI2, SI3, and SI4, as well as the SIBs contained in these four SI messages. Specifically, the period of SI1 is: SI1_period = rf32 (320ms), and SI1 includes SIB2 and SIB3, i.e., SI1:[SIB2,SIB3]. The period of SI2 is: SI2_period = rf64 (640ms), and SI2 includes SIB4 and SIB5, i.e., SI2:[SIB4,SIB5]. The period of SI3 is: SI3_period = rf128 (1280ms), and SI3 includes SIB6, i.e., SI3:[SIB6]. The period of SI4 is: SI4_period = rf64 (640ms), and SI4 includes SIB8 and SIB9, i.e., SI4:[SIB8,SIB9].

[0268] The base station uses the greatest common divisor of the periods of these four SI messages as the common window period co_period, i.e., co_period=32rf (i.e. 320ms); and the base station defines the length of the common window as 40ms, the window start reference point as 40ms, and the preset start time point as SFN=0, subframe=0.

[0269] The base station is configured with SIB1, which contains the following: 1) Common window configuration: Common SI window period: co_period=320ms=32rf; Common SI window length: 40ms; Common window start position: SFN=0, subframe=0.

[0270] 2) The scheduling information list (schedulingInfoList) is as follows: Entry 1: { SI1, sib-MappingInfo: [SIB2, SIB3], k: 1}; Entry 2: { SI2,sib-MappingInfo: [SIB4, SIB5], k: 2}; Entry 3: { SI3, sib-MappingInfo: [SIB6], k: 4}; Entry 4: { SI4,sib-MappingInfo: [SIB8, SIB9], k: 2}.

[0271] Where k is the ratio of the SI message period to the common window period, as detailed above. Figure 5 The relevant descriptions of the period multiple information in the illustrated embodiment will not be repeated here.

[0272] 3) Format of BitString dispatch instruction: The length of the BitString scheduling indicator is 4 bits.

[0273] The bit mapping of BitString is: [bit0→SI1, bit1→SI2, bit2→SI3, bit3→SI4].

[0274] The base station hands over the encoded SIB1 transport block to the MAC layer for scheduling, and then transmits it at the physical layer.

[0275] like Figure 9 As shown, when the system time reaches the predetermined common window start time of 680ms, the base station scheduler marks the window (680ms - 720ms) as active. The base station calculates the current common window number: wid = floor((SFN×10 + slot_offset) / co_period ) = floor(680 / 320)= 2, that is, the current common window number is 2.

[0276] The base station confirms whether each SI message is transmitted within the window. The specific formula is: Y = wid mod (SIm_period / co_period), where m takes values ​​from 1 to 4 and is a positive integer.

[0277] Specifically, SI1: 2 mod (320 / 320) = 0, meaning SI1 is transmitted in window 2 (i.e., the public window with window number 2).

[0278] SI2: 2 mod (640 / 320) = 0, meaning SI2 is transmitted in window 2; SI3: 2 mod (1280 / 320) = 2, meaning SI3 is not transmitted in window 2; SI4: 2 mod (640 / 320) = 0, meaning SI4 is transmitted in window 2; Based on the structure for determining whether an SI message is to be transmitted within the window for each SI message, the base station generates a BitString scheduling indication, namely 1011.

[0279] The base station puts the generated BitString scheduling instruction into DCI#1, and then sends DCI#1 on the PDCCH.

[0280] The base station arranges the scheduling order of SI messages according to the priority of the SI messages transmitted in the window (SI messages whose corresponding bit value of the BitString scheduling indicator is 1, i.e., SI1 message, SI2 message, and SI4 message), such as SI1 message, SI2 message, and SI4 message.

[0281] The base station allocates time-frequency resources for the SI1 message transmitted within the window, constructs DCI#2, and transmits the constructed DCI#2. DCI#2 includes: time-frequency resource #11 allocated for the SI1 message, MCS, and the ID of the SI1 message. After sending DCI#2, the base station transmits the SI1 message on the allocated time-frequency resource #11.

[0282] The base station allocates time-frequency resources for the SI2 message transmitted within the window, constructs DCI#2, and transmits the constructed DCI#2. DCI#2 includes: time-frequency resource #12 allocated for the SI2 message, MCS, and the ID of the SI2 message. After sending DCI#2, the base station transmits the SI2 message on the allocated time-frequency resource #12.

[0283] The base station allocates time-frequency resources for the SI3 message transmitted within the window, constructs DCI#2, and transmits the constructed DCI#2. DCI#2 contains: time-frequency resource #13 allocated for the SI3 message, MCS, and the ID of the SI3 message. After sending DCI#2, the base station transmits the SI3 message on the allocated time-frequency resource #13.

[0284] The above describes the specific implementation of a base station sending different SI messages using different time-frequency resources. In this embodiment, the base station can also allocate the same time-frequency resource for SI1, SI2, and SI4 messages transmitted within a window, construct DCI#2, and transmit the constructed DCI#2. DCI#2 includes: time-frequency resource #14 allocated for SI1, SI2, and SI4 messages, MCS, and the IDs of SI1, SI2, and SI4 messages. After sending DCI#2, the base station transmits SI1, SI2, and SI4 messages on the allocated time-frequency resource #14.

[0285] After obtaining SIB1, the UE can determine which SI messages contain its SIB through the schedulingInfoList in SIB1 and establish a list of SI messages it is interested in, SI-table{SI1, SI3}. The UE wakes up precisely at the start of window 2 (the common window with sequence number 2), receives DCI#1 sent by the base station, and obtains a BitString scheduling indication (1011). The UE compares the BitString scheduling indication with SI-table{SI1, SI3} to determine which SI1 it is interested in is transmitted within that window. When the ID of the required SI1 message exists in the DCI#2 received by the UE, the UE reads the time-frequency resource and MCS corresponding to the SI1 message in DCI#2, receives and decodes data on that time-frequency resource, and obtains its required SIB.

[0286] In this embodiment of the application, the base station can send SI messages within a certain period of time within each common window. For example, in Figure 9 In this diagram, each square represents a common window, and the central area within the square represents the time period during which the base station sends the SI message corresponding to that common window. The area before the central area within each square can be used to send the BitString scheduling indication corresponding to that common window (as in DCI#1 above), and can also be used to send information such as time-frequency resources and MCS indicating the SI message to be sent in that common window (as in DCI#2 above). The area after the central area within each square can be used for operations such as retransmission of messages within that common window. Alternatively, the base station can send SI messages within each common window, meaning that in this case, the base station does not need to send SI messages within a specific time period within each common window.

[0287] Understandable. Figure 9 The example shown can be referred to the foregoing. Figures 5 to 8 The embodiments shown are for reference only and will not be described in detail here.

[0288] It should be understood that Figures 5 to 9 The flowcharts or scene diagrams shown are for illustrative purposes only and are not intended to limit the embodiments of this application to the examples illustrated. In fact, those skilled in the art can interpret the embodiments based on... Figures 5 to 9 The examples in the document can be transformed into equivalent ways to obtain more implementations.

[0289] The above text combined Figures 5 to 9 This document describes in detail the communication method provided in the embodiments of this application. The following will combine... Figures 10 to 11 The device embodiments of this application are described in detail below. It should be understood that the communication device of this application embodiment can execute the various communication methods of the foregoing embodiments of this application, that is, the specific working processes of the various products below can be referred to the corresponding processes in the foregoing method embodiments.

[0290] In the embodiments described above, the terminal device may execute some or all of the steps in each embodiment; the network device may execute some or all of the steps in each embodiment. These steps or operations are merely examples, and the embodiments of this application may also perform other operations or variations thereof. Furthermore, the steps may be executed in different orders as presented in the embodiments, and it is not necessary to execute all the operations in the embodiments of this application. Moreover, the sequence number of each step does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0291] Figure 10 This is a schematic block diagram of a communication device provided in an embodiment of this application. Figure 10 As shown, the communication device 1000 may include a communication module 1020. The communication module 1020 can implement corresponding communication functions, which can be internal communication functions of the communication device 1000 or communication functions between the communication device 1000 and other devices. Optionally, the communication module 1020 may also be referred to as a communication interface or transceiver module. Optionally, the communication device 1000 further includes a processing module 1010. The processing module 1010 can implement corresponding processing functions.

[0292] Optionally, the communication device 1000 further includes a storage module, which can be used to store instructions and / or data; the processing module 1010 can read the instructions and / or data in the storage module so that the communication device 1000 can implement the aforementioned method embodiments.

[0293] In one possible design, the communication device 1000 may correspond to the terminal device in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the terminal device. The communication device 1000 may be used to execute the steps or processes performed by the terminal device in any of the above method embodiments.

[0294] For example, the communication module 1020 is configured to receive a target SI message from a network device in a target common window when it is determined that at least one SI message associated with a target common window contains a target SI message; wherein, the first duration is an integer multiple of the period of each SI message in the at least one SI message, the first duration is the product of the number of windows and the period of the common window, the number of windows is the number of common windows passed from a preset start time point to the start time point of the target common window, the period of the common window is the greatest common divisor of the periods of the multiple SI messages, and the at least one SI message is some or all of the multiple SI messages.

[0295] The processing module 1010 is used to obtain the target SIB based on the target SI message.

[0296] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0297] In one possible design, the communication device 1000 may correspond to the network device in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the network device. The communication device 1000 may be used to perform the steps or processes performed by the network device in any of the above method embodiments.

[0298] For example, the processing module 1010 is used to acquire at least one system information SI message; wherein, the first duration is an integer multiple of the period of each SI message in the at least one SI message, the first duration is the product of the number of windows and the period of the common window, the number of windows is the number of common windows passed from the preset start time point to the start time point of the target common window, the period of the common window is the greatest common divisor of the periods of multiple SI messages, and the at least one SI message is some SI messages or all SI messages in the multiple SI messages.

[0299] The communication module 1020 is used to send at least one of the aforementioned SI messages in the target common window.

[0300] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0301] Figure 11 This is another schematic block diagram of the communication device 1100 provided in the embodiments of this application. The communication device 1100 may be a chip, chip system, or processor, etc., used by a terminal device or network device to implement the above-described methods. The communication device 1100 can be used to implement the methods described in the above-described method embodiments; for details, please refer to the descriptions in the above-described method embodiments.

[0302] like Figure 11 As shown, the communication device 1100 may include one or more processors 1110, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 1110 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device 1100 (e.g., a base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

[0303] In an alternative design, the processor 1110 may also store instructions and / or data that can be executed by the processor 1110 to cause the communication device 1100 to perform the methods described in the above method embodiments.

[0304] In another alternative design, the communication device 1100 may include a communication interface 1120 for implementing receiving and transmitting functions. For example, the communication interface 1120 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0305] Optionally, the communication device 1100 may include one or more memories 1130, which may store instructions that can be executed on the processor 1110, causing the communication device 1100 to perform the methods described in the above method embodiments. Optionally, the memories 1130 may also store data. Optionally, the processor 1110 may also store instructions and / or data. The processor 1110 and the memories 1130 may be provided separately or integrated together.

[0306] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the methods disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0307] In one implementation, the communication device 1100 may correspond to the terminal device in the above method embodiments, and may be used to execute the various steps and / or processes executed by the terminal device in the above method embodiments. The processor 1110 may be used to execute instructions stored in the memory 1130, and when the processor 1110 executes the instructions stored in the memory, the processor 1110 is used to execute the various steps and / or processes of the above method embodiments corresponding to the terminal device.

[0308] In another implementation, the communication device 1100 may correspond to the network device in the above method embodiments and may be used to execute the various steps and / or processes executed by the network device in the above method embodiments. The processor 1110 may be used to execute instructions stored in the memory 1130, and when the processor 1110 executes the instructions stored in the memory, the processor 1110 is used to execute the various steps and / or processes of the above method embodiments corresponding to the network device.

[0309] It should be understood that the aforementioned processing device can be one or more chips. For example, the processing device can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0310] It is understood that the memory 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 random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0311] According to the method provided in the embodiments of this application, this application also provides a chip system, which includes one or more processors for calling and executing instructions stored in memory, thereby causing the method described in the embodiments of this application to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0312] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0313] According to the method provided in the embodiments of this application, this application also provides a communication system, which includes the aforementioned network device and terminal device.

[0314] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes a computer program or instructions that, when the computer program is run (or executed), cause the method described in the embodiments of this application to be executed.

[0315] According to the method provided in the embodiments of this application, this application also provides a computer-readable storage medium storing a program or instructions, which, when executed, cause the method described in the embodiments of this application to be performed.

[0316] The computer-readable storage medium may be the aforementioned volatile memory or non-volatile memory, or it may include both volatile memory and non-volatile memory.

[0317] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0318] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When these computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated.

[0319] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0320] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0321] In summary, the above description is merely a preferred embodiment of the technical solution of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A communication method, characterized in that, Applied to a terminal device, the method includes: If it is determined that at least one system information SI message associated with the target public window contains the target SI message, the target SI message is received from the network device in the target public window; Based on the target SI message, obtain the target system information block SIB; Wherein, the first duration is an integer multiple of the period of each SI message in the at least one SI message, the first duration is the product of the number of windows and the period of the common window, the number of windows is the number of common windows passed from the preset start time point to the start time point of the target common window, the period of the common window is the greatest common divisor of the periods of multiple SI messages, and the at least one SI message is some or all of the multiple SI messages.

2. The method according to claim 1, characterized in that, The at least one SI message is determined based on the sequence number of the target common window, the period of each SI message among the plurality of SI messages, and the period of the common window; Wherein, the sequence number of the target public window is the value obtained by dividing the second duration by the period of the public window and rounding down; the second duration is the difference between the current time point and the preset start time point; the current time point is the time point at which the network device determines the sequence number of the target public window; SI messages whose sequence number of the target public window divided by the first value has a remainder of zero belong to the at least one SI message, or, SI messages whose sequence number of the target public window divided by the first value has a remainder of zero and need to be broadcast belong to at least one SI message; the first value is a multiple of the period of each SI message among the multiple SI messages and the period of the public window.

3. The method according to claim 1, characterized in that, Before receiving the target SI message from the network device in the target common window, the method further includes: A first message is received in the target public window, the first message being used to indicate the at least one SI message associated with the target public window; Based on the first message, it is determined that the target public window is associated with the target SI message.

4. The method according to claim 3, characterized in that, The first message is Downlink Control Information (DCI).

5. The method according to claim 3, characterized in that, The first message carries a bit string that indicates the at least one SI message; Before receiving the first message in the target public window, the method further includes: Receive first information from the network device, the first information being used to indicate the mapping relationship between each bit in the bit string and each SI message in the plurality of SI messages; Based on the first message, determining the target SI message associated with the target public window includes: Based on the bit string and the first information, the target public window is associated with the target SI message.

6. The method according to claim 5, characterized in that, The first information is carried in SIB1.

7. The method according to claim 1, characterized in that, Before receiving the target SI message from the network device in the target common window, the method further includes: A second message is received in the target public window, the second message indicating transmission configuration parameters for transmitting the at least one SI message; Receiving the target SI message from the network device in the target common window includes: Based on the transmission configuration parameters, the target SI message is received in the target common window.

8. The method according to claim 7, characterized in that, The second message is DCI.

9. The method according to claim 1, characterized in that, Before receiving the target SI message from the network device in the target common window, the method further includes: The system receives second information from the network device, the second information including: a common window period and a window start reference point; or, the second information including a common window length; or, the second information including a common window period, a window start reference point, and a common window length; wherein, the common window period is used to indicate the period of the common window, the window start reference point is used to indicate the offset of the start time point of the common window relative to the start time point of the window period to which the common window belongs, and the common window length is used to indicate the duration of the common window; Receiving the target SI message from the network device in the target common window includes: Based on the second information, the target SI message is received in the target public window.

10. The method according to claim 9, characterized in that, Before receiving the target SI message from the network device in the target common window, the method further includes: Receive third information from the network device, the third information including at least one of the following: association information and period multiple information, the association information being used to indicate the SIB associated with each SI message in the plurality of SI messages, and the period multiple information being used to indicate the multiple relationship between the period of each SI message in the plurality of SI messages and the period of the common window; Receiving the target SI message in the target public window based on the second information includes: Based on the second information and the third information, the target SI message is received in the target public window.

11. The method according to claim 10, characterized in that, The second and third information are carried in SIB1.

12. The method according to any one of claims 1-11, characterized in that, When there are multiple SI messages in the at least one SI message, each SI message in the at least one SI message is distinguished by a different logical channel identifier in the Media Access Control (MAC) subheader.

13. The method according to any one of claims 1-11, characterized in that, The method further includes: If it is determined that the target public window will not send the target SI message, it enters a sleep state.

14. A communication method, characterized in that, Applied to network devices, the method includes: Obtain at least one System Information (SI) message; Send at least one SI message in the target public window; Wherein, the first duration is an integer multiple of the period of each SI message in the at least one SI message, the first duration is the product of the number of windows and the period of the common window, the number of windows is the number of common windows passed from the preset start time point to the start time point of the target common window, the period of the common window is the greatest common divisor of the periods of multiple SI messages, and the at least one SI message is some or all of the multiple SI messages.

15. The method according to claim 14, characterized in that, The acquisition of at least one SI message includes: Based on the second duration and the period of the public window, the sequence number of the target public window is obtained. The sequence number of the target public window is the value obtained by dividing the second duration by the period of the public window and rounding down. The second duration is the difference between the current time point and the preset start time point. The current time point is the time point at which the network device determines the sequence number of the target public window. The at least one SI message is determined based on the sequence number of the target public window, the period of each SI message in the plurality of SI messages, and the period of the public window; the SI message whose remainder is zero when the sequence number of the target public window is divided by a first value belongs to the at least one SI message, or the SI message whose remainder is zero when the sequence number of the target public window is divided by the first value and needs to be broadcast belongs to the at least one SI message; the first value is a multiple of the period of each SI message in the plurality of SI messages and the period of the public window.

16. The method according to claim 14, characterized in that, Before sending the at least one SI message in the target public window, the method further includes: A first message is sent in the target public window, the first message being used to indicate the at least one SI message associated with the target public window.

17. The method according to claim 16, characterized in that, The first message carries a bit string that indicates the at least one SI message; Before sending the first message in the target public window, the method further includes: Send a first message, which is used to indicate the mapping relationship between each bit in the bit string and each SI message in the plurality of SI messages.

18. The method according to claim 14, characterized in that, Before sending the at least one SI message in the target public window, the method further includes: A second message is sent in the target public window, the second message indicating the transmission configuration parameters for transmitting the at least one SI message.

19. The method according to claim 14, characterized in that, Before sending the at least one SI message in the target public window, the method further includes: Send second information, the second information including: a common window period and a window start reference point, or the second information including a common window length, or the second information including a common window period, a window start reference point and a common window length; wherein, the common window period is used to indicate the window period of the target common window, the window start reference point is used to indicate the offset of the start time point of the common window relative to the start time point of the window period to which the common window belongs, and the common window length is used to indicate the duration of the common window.

20. The method according to claim 19, characterized in that, Before sending the at least one SI message in the target public window, the method further includes: Send a third message, which includes at least one of the following: association information and period multiple information. The association information is used to indicate the SIB associated with each SI message in the plurality of SI messages, and the period multiple information is used to indicate the multiple relationship between the period of each SI message in the plurality of SI messages and the period of the common window.

21. The method according to any one of claims 14-20, characterized in that, When there are multiple SI messages in the at least one SI message, each SI message in the at least one SI message is distinguished by a different logical channel identifier in the Media Access Control (MAC) subheader.

22. A communication device, characterized in that, The apparatus includes a module for performing the method as described in any one of claims 1 to 21.

23. A communication device, characterized in that, The device includes at least one processor coupled to a memory storing a program or instructions, the processor executing the program or instructions to cause the device to perform the method as described in any one of claims 1 to 21.

24. A chip system, characterized in that, The chip system includes one or more processors, which are configured to retrieve and execute instructions stored in memory, such that the method as described in any one of claims 1 to 21 is performed.

25. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed, they cause the computer to perform the method as described in any one of claims 1 to 21.

26. A computer program product, characterized in that, The computer program product includes a computer program or instructions that, when executed by a communication device, cause the method of any one of claims 1 to 21 to be performed.

Images