System information transmission method and apparatus, electronic device, and storage medium

Abstract

The present application relates to the technical field of mobile communications, and in particular to a system information transmission method and apparatus, an electronic device, and a storage medium, for use in improving the system information transmission efficiency. The method comprises: in a synchronization signal and PBCH block (SSB) transmission period, transmitting SSBs and on-demand system information (OSI) according to at least two sub-periods, wherein in a first time slot of each sub-period, an SSB set corresponding to the sub-period is transmitted; and in a second time slot of the same sub-period, target OSI corresponding to the SSB set is transmitted, the target OSI comprising different types of OSI corresponding to indexes of SSBs in the SSB set.

Description

A method, apparatus, electronic device, and storage medium for transmitting system messages.

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 2024115874064, filed on November 7, 2024, entitled "A method, apparatus, electronic device and storage medium for transmitting system messages", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of mobile communication technology, and in particular to a method, apparatus, electronic device, and storage medium for transmitting system messages. Background Technology

[0004] In modern communication systems, especially 5G (5th-generation) systems, ensuring that user equipment (UE) can quickly obtain network information and maintain efficient communication is of paramount importance. Effective transmission of system messages and scheduling of synchronization signal blocks (SSBs) are core elements for achieving this goal.

[0005] In 5G systems, System Information (SI) is divided into three types: Minimum System Information (MSI), Remaining Minimum System Information (RMSI), and On-demand System Information (OSI). RMSI includes the Master Information Block (MIB) and System Information Block Type 1 (SIB1), representing the most basic information. OSI includes SIB2 to SIB14, with subsequent versions adding SIB15 to SIB21, as well as the location system information posSib.

[0006] In related technologies, scheduling mechanisms typically require that one SI (Indicator Signal) must be completely transmitted before the next SI can be transmitted. Specifically, when the SSB (Segment Subsystem) period is long, the UE may experience a long waiting time and be unable to obtain updated information in a timely manner. This situation is particularly evident in satellite communication systems. For satellite communication systems, the number of coverage spectral positions is large, reaching thousands. According to relevant protocols, the FR1 / FR2 bands support a maximum of 8 or 64 SSB indices respectively. This limitation cannot meet the needs of wide coverage, so the SSB transmission period will extend to several hundred milliseconds. When multiple SI types are scheduled, using the same time-frequency resources, the SI period (SI-Periodicity) will be a time unit on the order of seconds, much larger than the time of the terrestrial system. The UE cannot respond quickly to changes, such as the local ephemeris in SIB19. In addition, in order to transmit OSI (Optical System Signal) as quickly as possible within a period, even when multiple OSI time slots are configured, there is still a limitation that one SI must be completely transmitted before the next SI can be transmitted, resulting in low system message transmission efficiency. Summary of the Invention

[0007] This application provides a method, apparatus, electronic device, and storage medium for transmitting system messages, in order to improve the transmission efficiency of system messages.

[0008] This application provides a method for transmitting system messages, including:

[0009] During the SSB transmission cycle, the SSB and OSI are transmitted in at least two sub-cycles, where:

[0010] In the first time period within the sub-cycle, the SSB group corresponding to the sub-cycle is sent;

[0011] In the second time period within the same sub-cycle, a target OSI corresponding to the SSB group is sent; the target OSI includes OSIs of different types corresponding to the indices of SSBs in the SSB group.

[0012] This application provides a system message transmission device, comprising:

[0013] The transmitting unit is configured to transmit SSB and OSI data in at least two sub-cycles within the SSB transmission cycle, wherein:

[0014] In the first time period within the sub-cycle, the SSB group corresponding to the sub-cycle is sent;

[0015] In the second time period within the same sub-cycle, a target OSI corresponding to the SSB group is sent; the target OSI includes OSIs of different types corresponding to the indices of SSBs in the SSB group.

[0016] Optionally, the scheduling position of the target OSI within the second time period is determined based on the system message queue corresponding to the sub-period; the system message queue is used to indicate the scheduling order of the different types of OSI.

[0017] Optionally, the scheduling location includes a starting time slot and a first starting system frame number. The first starting system frame number is related to the second starting system frame number where the sub-cycle is located, the window offset of the time window where the target OSI is located, and the number of frame time slots. The number of frame time slots is the number of time slots contained in a radio frame.

[0018] Optionally, the transmitting unit is further configured as follows:

[0019] The target OSI is repeatedly transmitted during other second time periods within the same sub-cycle.

[0020] Optionally, at least two of the sub-periods are obtained by dividing the SSB transmission period into integer multiples of the SSB burst set transmission period.

[0021] Optionally, if there is a time window during the second time period during which OSI is not transmitted, the apparatus further includes:

[0022] The indicator unit is configured to indicate that the time window has not sent OSI in at least one of the following ways:

[0023] Define the system message block type of the time window as invalid;

[0024] Set the message broadcast status of the time window to null.

[0025] Configure target parameters for time windows other than the aforementioned time window.

[0026] An electronic device provided in this application includes a processor and a memory, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor performs the steps of any of the above-described system message transmission methods.

[0027] This application provides a computer-readable storage medium including a computer program. When the computer program is run on an electronic device, the computer program is configured to cause the electronic device to perform the steps of any of the above-described system message transmission methods.

[0028] This application provides a computer program product, which includes a computer program stored in a computer-readable storage medium. When a processor of an electronic device reads the computer program from the computer-readable storage medium, the processor executes the computer program, causing the electronic device to perform the steps of any of the above-described system message transmission methods.

[0029] The beneficial effects of this application are as follows:

[0030] This application provides a method, apparatus, electronic device, and storage medium for transmitting system messages. By introducing the concept of sub-cycles, SSBs and OSIs are transmitted according to at least two sub-cycles within an SSB transmission cycle. This method divides the SSB transmission cycle into at least two sub-cycles, allowing for fine-grained management of the transmission timing of SSBs and system messages, thereby improving the orderliness of system message transmission. Furthermore, in the first time period within each sub-cycle, the corresponding SSB group is transmitted. In the second time period within the same sub-cycle, the target OSI corresponding to that SSB group is transmitted. The target OSI includes OSIs of different types corresponding to the indices of the SSBs in that SSB group. This achieves synchronous transmission of the SSB group and the different types of OSI messages corresponding to that SSB group within each sub-cycle, instead of transmitting one type of OSI corresponding to all SSB indices before transmitting the next type of OSI. This avoids the problem of OSI transmission being premature across sub-cycles, leading to delays in OSI acquisition by terminal devices, and further improves the overall efficiency and stability of the communication system.

[0031] Other features and advantages of this application will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the application. The objectives and other advantages of this application may be realized and obtained by means of the structures particularly pointed out in the written description, claims, and drawings. Attached Figure Description

[0032] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0033] Figure 1 is a schematic diagram of an application scenario in an embodiment of this application;

[0034] Figure 2 is a flowchart illustrating the implementation of a system message transmission method according to an embodiment of this application;

[0035] Figure 3 is a schematic diagram of the division of a sub-period of an SSB transmission period in an embodiment of this application;

[0036] Figure 4 is a schematic diagram of the sub-period division of another SSB transmission period in an embodiment of this application;

[0037] Figure 5 is a scheduling flowchart of various target OSIs in an embodiment of this application;

[0038] Figure 6 is a schematic diagram of the transmission of each OSI in a sub-cycle in an embodiment of this application;

[0039] Figure 7 is a schematic diagram of the transmission of each OSI in another sub-cycle in an embodiment of this application;

[0040] Figure 8 is a schematic diagram of a time window without sending OSI configuration in an embodiment of this application;

[0041] Figure 9 is a schematic diagram illustrating the differences between the OSI system transmission method and related OSI technologies in an embodiment of this application.

[0042] Figure 10 is a flowchart illustrating another method for transmitting system messages according to an embodiment of this application.

[0043] Figure 11 is a schematic diagram of a system message transmission device according to an embodiment of this application;

[0044] Figure 12 is a schematic diagram of another system message transmission device structure according to an embodiment of this application;

[0045] Figure 13 is a schematic diagram of the composition structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0046] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings of the embodiments of this application. Obviously, the described embodiments are only some embodiments of the technical solutions of this application, and not all embodiments. Based on the embodiments recorded in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the technical solutions of this application.

[0047] In the embodiments of this application, the terms "information," "signal," "message," "channel," and "singaling" may sometimes be used interchangeably. It should be noted that, without emphasizing their distinction, they all convey the same meaning. Similarly, the terms "of," "corresponding (relevant)," and "corresponding" may sometimes be used interchangeably. It should be noted that, without emphasizing their distinction, they all convey the same meaning.

[0048] The following describes some of the concepts involved in the embodiments of this application.

[0049] SSB: SSB stands for SS / PBCH block. The SS / PBCH block is the primary information demodulated by the terminal equipment during initial access. This SS / PBCH block mainly includes the primary synchronization signal (PSS), secondary synchronization signal (SSS), and physical broadcast channel (PBCH). The terminal equipment can perform cell synchronization and coarse symbol-level timing synchronization by demodulating the PSS and SSS. The PBCH can carry MIB information configured at higher layers. The terminal equipment can perform system frame-level timing synchronization and obtain SIB1 / RMSI / OSI location information by demodulating the MIB information.

[0050] SSB Transmission Period: This refers to the time interval at which the base station periodically transmits SSBs. The SSB transmission period determines the repetition frequency of the synchronization signal block on the time axis. Within this period, the base station transmits SSB burst sets according to a preset time plan, ensuring that the terminal device can receive the synchronization signal at the appropriate time and complete the initial synchronization and access with the base station. The length of the SSB transmission period depends on the network configuration and application scenario. In high-speed mobile or high-density scenarios, a shorter SSB transmission period may be required to ensure that the terminal device can synchronize quickly; while in more stable scenarios, the period can be extended to save network resources.

[0051] SSB Burst Set: This refers to a set of SSBs continuously transmitted by network devices (such as 5G NR base stations) within a specific time window. SSB burst sets are primarily used to provide synchronization signals (PSS, SSS) and Physical Broadcast Channel (PBCH) information to terminal devices (such as mobile phones or IoT devices), enabling them to complete cell synchronization, obtain basic system information, and access the network.

[0052] SSB Burst Period: This refers to the time interval at which network devices periodically send SSB burst sets. This period determines the frequency at which SSB groups repeat on the timeline. The base station sends SSB burst sets according to a preset periodic plan to ensure that terminal devices can receive the required synchronization signals within this period, thereby completing synchronization and initial access with the base station.

[0053] A sub-period is a smaller time unit divided based on integer multiples of the SSB burst set period. The sub-period is a further subdivision of the SSB transmission period according to the SSB burst set period, allowing the transmission of one or more SSB groups within a single sub-period, while simultaneously synchronizing with the corresponding OSI scheduler. Within an SSB sub-period, the network device first transmits the SSB group, and then schedules other OSI messages associated with that SSB group according to the system message queue.

[0054] A cell is a basic data structure or unit of information used to describe and define specific parameters, fields, or message types in a communication protocol. Cells are usually explicitly represented in the protocol specification, defining their data type, value range, possible options, and format so that both communicating parties can parse and process this information according to the same rules.

[0055] The preferred embodiments of this application are described below with reference to the accompanying drawings. It should be understood that the preferred embodiments described herein are for illustration and explanation only and are not intended to limit this application. Furthermore, the embodiments and features in the embodiments of this application can be combined with each other without conflict.

[0056] Figure 1 illustrates an application scenario of an embodiment of this application. The application scenario includes one or more network devices and one or more terminal devices connected to the network devices. For ease of description, only one network device and two terminal devices are shown in Figure 1.

[0057] In Figure 1, the terminal device can be located within the beam / cell coverage area of ​​the network device. The terminal device can communicate with the network device over the air via either the uplink (UL) or downlink (DL). For example, in the UL direction, the terminal device can send uplink data to the network device via the physical uplink shared channel (PUSCH); in the DL direction, the network device can send downlink data to the terminal device via the physical downlink shared channel (PDSCH).

[0058] The terminal device in Figure 1 can be a terminal device that supports the new air interface, which can access the communication system through the air interface and initiate services such as making calls and accessing the Internet. The terminal device can be an entity on the user side used to receive or transmit signals, and can have channel prediction and channel coefficient feedback functions.

[0059] Terminal equipment can also be called user equipment (UE), mobile station (MS), or mobile terminal (MT), etc. Specifically, the terminal equipment in Figure 1 can be a mobile phone, tablet computer, or computer with wireless transceiver capabilities. It can also be a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in autonomous driving, a wireless terminal in telemedicine, a wireless terminal in a smart grid, a wireless terminal in a smart city, a wireless terminal in a smart home, an in-vehicle terminal, a vehicle with vehicle-to-vehicle (V2V) communication capabilities, an intelligent connected vehicle, a drone with drone-to-drone (U2U) communication capabilities, etc., without limitation.

[0060] In Figure 1, the network device can be any device with wireless transceiver capabilities. Its main functions include wireless physical control, resource scheduling and wireless resource management, wireless access control, and mobility management, providing reliable wireless transmission protocols and data encryption protocols. The network device can be an entity on the network side configured to transmit or receive signals and may possess channel prediction capabilities.

[0061] Specifically, the network device can be either a wired access device or a wireless access device. For example, the network device can be an access network (AN) / radio access network (RAN) device, composed of multiple 5G-AN / 5G-RAN nodes. These 5G-AN / 5G-RAN nodes can be: access points (APs), base stations (nodeBs, NBs), enhanced nodeBs (eNBs), next-generation nodeBs (gNBs), transmission reception points (TRPs), transmission points (TPs), or other types of access nodes.

[0062] In one alternative implementation, the terminal device 110 and the network device 120 can communicate via a communication network.

[0063] In one alternative implementation, the communication network is a wired network or a wireless network.

[0064] It should be noted that Figure 1 is only an example, and in reality, the number of terminal devices and network devices is not limited, and no specific limitation is made in this embodiment.

[0065] Furthermore, the embodiments of this application can be applied to various communication system scenarios, such as: satellite communication systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication systems, 5th generation (5G) communication systems, new radio (NR) systems, and other future communication systems such as 6G. Optionally, the technical solutions provided in this application can also be applied to Internet of Things (IoT) systems, narrowband Internet of Things (NB-IoT) systems, etc.

[0066] The following describes the system message transmission method provided by the exemplary embodiments of this application in conjunction with the application scenarios described above and with reference to the accompanying drawings. It should be noted that the above application scenarios are only shown to facilitate understanding of the spirit and principles of this application, and the embodiments of this application are not limited in any way in this respect.

[0067] Referring to Figure 2, which is a flowchart of a system message transmission method provided in this application embodiment, taking a network device as the execution subject, the specific implementation process of the method is as follows:

[0068] S21: During the SSB transmission cycle, transmit the SSB and OSI in at least two sub-cycles.

[0069] The SSB transmission period refers to the time interval at which the base station periodically transmits SSBs. The SSB transmission period determines the repetition frequency of the synchronization signal block on the time axis. Within this period, the base station transmits SSB burst sets according to a preset time plan to ensure that the terminal device can receive the synchronization signal at the appropriate time and complete the initial synchronization and access with the base station.

[0070] The OSI principle of sending SSB and other system messages in at least two sub-cycles refers to dividing the SSB transmission cycle into at least two sub-cycles.

[0071] In this embodiment of the application, in order to map all corresponding OSIs within the current SSB transmission period, the specified SSB transmission period is divided into units of integer multiples of the SSB burst set period.

[0072] Among them, the SSB burst set is a group of SSBs sent within a specific time window; based on this division unit, the SSB transmission period can be divided into at least two sub-periods.

[0073] In this context, an integer multiple of the SSB burst set period refers to any integer multiple related to the burst set transmission period. For example, if an SSB burst set period is T, the division unit can be T, 2T, 3T, etc.

[0074] In one optional embodiment, when the integer multiple of the SSB burst set period is set to 1, a group of SSBs can be sent in the first time period within each transmission sub-period. Meanwhile, to address the problem mentioned in the background art where the long SSB period leads to excessive waiting time for terminal devices and untimely information acquisition, the second time period within this transmission sub-period also needs to send various OSI messages corresponding to the SSB group. This is only briefly introduced here; please refer to the following for details, which will not be repeated here.

[0075] See Figure 3, which is a schematic diagram of the division of an SSB sub-period in an embodiment of this application.

[0076] In this system, the SSB sub-period is 80ms. SSBs are concentrated and sent within the first 5ms of each 20ms period. These concentrated SSBs form an SSB burst set. The idle time between two SSB burst sets can be used to send corresponding OSI messages, thus making full use of time resources and improving message transmission efficiency. Specifically, in Figure 3, the SSB burst set period is 20ms. When an SSB transmission period contains multiple SSB burst sets, the division unit is an integer multiple of the SSB burst set period. In Figure 3, a sub-period is one time the duration of an SSB burst set, i.e., the sub-period is 20ms. Therefore, an SSB transmission period can be divided into four sub-periods.

[0077] In another optional embodiment, when the integer multiple of the SSB burst set period is set to 2, two SSBs can be sent within each sub-period. Simultaneously, to address the issue mentioned in the background art where the long SSB period leads to excessive UE waiting time and untimely information acquisition, various OSI messages corresponding to these two SSB groups also need to be sent within this sub-period.

[0078] See Figure 4, which is a schematic diagram of the division of another SSB transmission sub-cycle in an embodiment of this application.

[0079] The SSB transmission sub-cycle remains 80ms, and the SSB burst set cycle remains 20ms. By using twice the SSB burst set cycle as the division unit, the SSB transmission cycle can be divided into two transmission sub-cycles.

[0080] It should be noted here that when using a division unit of at least 2 times the SSB burst, the SSB period must be an integer multiple of that division unit.

[0081] In an alternative implementation, a new information cell SSB-SubPeriodicity is added:

[0082] SSB-SubPeriodicity ENUMERATED{s10, s20, s40, s80, s160}.

[0083] The SSB-SubPeriodicity field is used to define the SSB subperiod. Its value range is set according to the SSB burst set period, and is usually an integer multiple of the burst set period to ensure the synchronization and efficiency of SSB transmission. SSB subperiods include, but are not limited to: s10, s20, s40, s80, and s160. These values ​​represent the length of the subperiod. For example, s10 means 10 time slots as a subperiod, s20 means 20 time slots, and so on.

[0084] Specifically, by configuring sub-periods of different lengths, the transmission frequency of the SSB can be flexibly adjusted according to the needs of the scenario. For example, shorter sub-periods (such as s10 or s20) are suitable for scenarios that require frequent updates to system information, reducing the waiting time of terminal devices and ensuring that they can quickly obtain updated synchronization signals and OSI messages. Longer sub-periods (such as s80 or s160) are suitable for scenarios with relatively stable network resources, saving resource consumption.

[0085] In this embodiment of the application, by dividing the period into sub-periods, each SSB index and its corresponding OSI can achieve a correspondence within the same sub-period, thereby ensuring that SSB and OSI messages can be synchronously transmitted within the same time window.

[0086] The following will provide a detailed explanation of the transmission of the SSB group and the corresponding different types of OSI within each sub-cycle. For each sub-cycle, the following steps S1101 to S1102 will be performed respectively:

[0087] S211: In the first time period within this sub-cycle, send the SSB group corresponding to this sub-cycle.

[0088] The first time period is used to send the SSB group corresponding to that sub-cycle.

[0089] In this embodiment, multiple SSBs need to be sent within a specified SSB transmission period, which can be denoted as N, where N ≤ Lmax, Lmax is the maximum number of supported SSBs to be sent, and N is the number of SSBs actually sent within one SSB period. Furthermore, each SSB carries its own SSB index, used to uniquely identify the SSB so that the terminal device can distinguish between them. This SSB index can be denoted as i, and the value of i is one of {0, 1, ..., N-1}.

[0090] In the embodiments of this application, SSBs are sent in the form of burst sets. When SSBs are sent in the form of burst sets, multiple SSBs can be a group of SSBs. For example, if 16 SSBs, SSB0 to 15, need to be sent in one SSB sending cycle, and SSBs are sent in the form of burst sets, then SSB0 to 3 are the first group of SSBs, SSB4 to 7 are the second group of SSBs, SSB8 to 11 are the third group of SSBs, and SSB12 to 15 are the fourth group of SSBs.

[0091] In an optional implementation, taking the example of needing to send 16 SSBs (SSB0 to 15) within one SSB transmission cycle, if one SSB transmission cycle is divided into 4 sub-cycles, i.e., the SSB transmission cycle is divided in units of 1 times the SSB burst set, then the corresponding SSB groups sent in the first time period of the first sub-cycle are SSB0 to 3, the corresponding SSB groups sent in the first time period of the second sub-cycle are SSB4 to 7, the corresponding SSB groups sent in the first time period of the third sub-cycle are SSB8 to 11, and the corresponding SSB groups sent in the first time period of the fourth sub-cycle are SSB12 to 15.

[0092] By using the above method, it can be ensured that the SSB group corresponding to the sub-cycle is sent in the first time period of each sub-cycle, thereby realizing the step-by-step transmission of each SSB group according to the sub-cycle within an SSB transmission cycle, and reasonably arranging the transmission order of each SSB group in time, effectively reducing the risk of transmission conflict and optimizing resource utilization.

[0093] The above describes the transmission of SSB groups within a sub-cycle. The following will describe the transmission of different types of OSI corresponding to the SSB groups within the same sub-cycle.

[0094] S212: In the second time period within the same sub-cycle, send the target OSI corresponding to the SSB group; the target OSI includes: OSI of different types corresponding to the index of the SSB in the SSB group.

[0095] The second time period is used to send the target OSI corresponding to the SSB group.

[0096] It should be noted that the first and second time periods do not overlap, and the first time period precedes the second time period.

[0097] This approach ensures that the SSB group is sent first, followed by the corresponding OSI message. This allows the terminal to quickly obtain the associated OSI information after receiving the SSB in the current sub-cycle, avoiding waiting for multiple sub-cycles, reducing OSI reception latency, and improving the real-time performance and effectiveness of transmission.

[0098] OSI (Optical System) is a system where base stations provide terminals with more detailed network resource and service information, helping terminals complete configuration and operation after access.

[0099] The OSI types include basic versions SIB2 to SIB14, and subsequent versions SIB15 to SIB21, as well as positioning system information posSib. In this embodiment, the types of basic versions SIB2 to SIB14 and subsequent versions SIB15 to SIB21 are defined by type1 in the newly added information element SIB-TypeInfo-ext->sib-MappingInfo-ext. This allows OSIs of different SIB types (SIB2 to SIB14 and SIB15 to SIB21) to be scheduled through the same scheduling mechanism. For example, they can be placed in the same SI in the scheduling list. At the same time, the system information posSib is defined by type2 in SIB-TypeInfo-ext->sib-MappingInfo-ext to ensure the scheduling and effective transmission of positioning system information. sib-MappingInfo-ext will be described in detail below. Furthermore, this application does not limit the specific SIB types included in the OSI. More SIB types may be added in the future, and they can all be uniformly defined by type1 in sib-MappingInfo-ext of this application.

[0100] In the embodiments of this application, the OSI includes, but is not limited to, the following categories: SIB2, which provides specific parameters for radio access, such as access control and access channel configuration information; SIB3, which contains additional information about the cell, such as spectrum resource allocation and scheduling policies; SIB4, which provides cell load information to help terminal devices optimize and select resources; SIB5, which relates to the Quality of Service (QoS) parameters of user equipment to ensure that the terminal can obtain the required network performance; SIB6, which contains location service-related information to help terminal devices obtain location information; SIB7, which provides network security-related information, including encryption and authentication parameters; SIB8 to SIB21, these SIB blocks further expand the system information, covering information required for specific functions and application scenarios, such as access permissions, handover policies, etc.; and Positioning System Information (posSib), which is a location service-specific system information block designed to provide the information required to support positioning functions.

[0101] Furthermore, for the different types of OSI corresponding to the index of the SSB in the SSB group, the different types of OSI corresponding to the SSB are not limited to including all types of the above-mentioned OSI types. A certain SSB group can correspond to a combination of several types of the above-mentioned types, or it can be all types. This application does not make a specific limit on the number of different types of OSI corresponding to a specific SSB.

[0102] In this embodiment, each SSB index corresponds to a specific OSI type to be transmitted. This correspondence ensures that the terminal device can accurately obtain the corresponding OSI message by identifying the specific SSB index. For example, when the SSB index is i, all OSI messages corresponding to that SSB will be based on the SSB index. This allows for the differentiation and processing of different SSBs and their carried OSIs through indexing, ensuring that the required information is obtained when accessing the network.

[0103] In an optional implementation, taking the example of needing to send 16 SSBs (SSB0 to 15) within one SSB transmission cycle, each SSB index still retains its corresponding OSI index. For example, SSB0 to 3 correspond to OSI-1 (SSB0 to 3), OSI-2 (SSB0 to 3), ..., OSI-n (SSB0 to 3); SSB4 to 7 correspond to OSI-1 (SSB4 to 7), OSI-2 (SSB4 to 7), ..., OSI-n (SSB4 to 7); SSB8 to 11 correspond to OSI-1 (SSB8 to 11), OSI-2 (SSB8 to 11), ..., OSI-n (SSB8 to 11); and SSB12 to 15 correspond to OSI-1 (SSB12 to 15), OSI-2 (SSB12 to 15), ..., OSI-n (SSB12 to 15).

[0104] In one alternative implementation, each OSI type corresponds to specific system information, but this does not mean that each type must be transmitted in every transmission. If it is necessary to transmit a certain OSI type, it can be marked with the corresponding OSI type.

[0105] For example, in a certain OSI transmission process, if three types of system messages—SIB2, SIB4, and SIB7—need to be sent, then SIB2 can be denoted as OSI-1, SIB4 as OSI-2, and SIB2 as OSI-3. Furthermore, in a certain OSI transmission process, if two types of SIBs are similar in their transmission content or destination, they can be sent together to improve efficiency. For example, in a certain OSI transmission process, if four types of system messages—SIB7, SIB8, SIB9, and SIB10—need to be sent, and SIB7 and SIB8 are similar, they can be sent together. Therefore, SIB7 and SIB8 can be denoted as OSI-1, SIB9 as OSI-2, and SIB10 as OSI-3.

[0106] It should be noted that the above-described implementation methods are merely simple examples, and this application does not specifically limit the types of system messages included in the OSI model that are sent.

[0107] The above section introduced the SSB group to be sent and the corresponding target OSI. The following section will explain the specific transmission process of the target OSI:

[0108] The scheduling position of the target OSI in the second time period is determined based on the system message queue corresponding to that sub-cycle; the system message queue is used to indicate the scheduling order of different types of OSI.

[0109] Among them, the system message queue refers to the scheduling information of various target OSIs, which includes at least the scheduling information corresponding to each OSI. The scheduling information is the key information used to determine the specific time to send OSI messages.

[0110] By configuring the system message queue within a sub-cycle, the sending of SSB and various OSI messages can be made more orderly and efficient, ensuring that all types of OSI corresponding to the same SSB index are scheduled and sent within the same sub-cycle, avoiding cross-cycle sending.

[0111] In the embodiments of this application, one SSB sub-cycle corresponds to one system message queue.

[0112] In one optional implementation, when multiple SSB groups need to be sent within an SSB sub-cycle, i.e., when the division unit is an integer multiple of the burst set sending cycle corresponding to the SSB burst set, in order to achieve the purpose of sending the SSB first and then sending the OSI message corresponding to the SSB for each SSB group, the system message queue of an SSB sub-cycle can be divided into multiple sub-queues according to the SSB group. The SSB group is sent first, and then the OSI message corresponding to the SSB is sent according to the sub-queue of the group; then the next SSB group is sent, and then the OSI message corresponding to the next SSB is sent according to the next sub-queue.

[0113] In one optional implementation, the system message queue is denoted as SI-SchedulingInfo. The scheduling information includes, but is not limited to, the preset window length of the new cell sub-cycle (hereinafter referred to as the preset window length) and the new cell sub-cycle system message queue. The system message queue is used to determine the transmission order of various target OSIs. In addition, it also includes multiple scheduling information related to OSI scheduling, including but not limited to the sub-cycle time window position index, OSI transmission period, and OSI type.

[0114] Specifically, the preset window length can be denoted as si-WindowLen-SubPeriod, which represents the length of the OSI message time window within a sub-period;

[0115] The system message queue can be denoted as schedulingInfoList, the time window position index can be denoted as si-WindowPosition-SubPeriod, the OSI transmission period can be denoted as si-Period-SubPeriod, and the OSI type can be denoted as sib-MappingInfo. The system message queue can then be configured as follows:

[0116] Among them, a sequence structure named SI-SchedulingInfo is defined to store the system message queue; schedulingInfoList: represents the OSI list to be scheduled, SEQUENCE(SIZE(1..maxSI-Message)) specifies that the size of the list is between 1 and maxSI-Message, OFSchedulingInfo indicates that each element in the list belongs to the SchedulerInfo type;

[0117] si-WindowLength: Indicates the length of the time window without sub-periods. If si-WindowLen-SubPeriod and schedulingInfoList-ext are carried in SI-SchedulingInfo, the UE ignores si-WindowLength.

[0118] si-WindowLen-SubPeriod-ext: New information element, indicating the window length of the subperiod. Allowed values ​​are s1 to s160. OPTIONAL indicates that this field is optional and can be excluded.

[0119] `schedulingInfoList-ext` represents an extended list of scheduling information. `SEQUENCE(SIZE(1..maxSI-Message))OF SchedulingInfo-ext` is similar to `schedulingInfoList`, but uses a different `SchedulingInfo-ext` type. `OPTIONAL`: This field is also optional.

[0120] It is important to note that the schedulingInfoList-ext cell is different from the schedulingInfoList cell in the original communication protocol. It is the updated schedulingInfoList cell after adding sub-cycles. Other cells related to SSB sub-cycles have also changed, which will not be elaborated here.

[0121] SchedulingInfo-ext defines a sequence structure for more detailed scheduling information.

[0122] si-WindowPosition-SubPeriod: A new information element representing the window position index of a certain OSI within a sub-period. INTEGER(1..256): Specifies that the value of this position index must be between 1 and 256. Unlike the si-WindowPosition-SubPeriod information element in the original communication protocol, this is the updated window position index si-WindowPosition-SubPeriod information element within the sub-period.

[0123] si-Period-SubPeriod: New information element, representing the value of the OSI transmission period. ENUMERATED{rf1, rf2, rf4, rf8, rf16} is an optional value, representing different transmission periods (such as sending once every rf1, rf2, etc.). OPTIONAL: This field is optional.

[0124] sib-MappingInfo-ext: The newly added information element represents SIB (System Information Block) mapping information. The specific format is defined by SIB-Mapping-ext. SIB-Mapping-ext is used to describe SIB type information. sibType-ext: Represents the SIB type selection field. CHOICE indicates that this field can be one of multiple types. type1: The first selection type, which allows values ​​of multiple different types of SIBs (e.g., SIB2 to SIB21) and some spare values ​​(e.g., spare1, spare2, etc.). The SIB-Mapping of related technologies only includes SIB2 to SIB14. This application adds SIB15 to SIB21 on this basis, so that OSI of different SIB types SIB2 to SIB14 and SIB15 to SIB21 can be scheduled through the same scheduling mechanism, for example, through the same SI scheduling. type2 defines another selection type, which allows values ​​of the posSib type.

[0125] In summary, the SI-SchedulingInfo cell, as the core structure of scheduling information, ensures the orderly and efficient transmission of SSB and OSI messages. It contains key parameters such as preset window length, sub-cycles, and mapping information. By configuring these parameters, cross-cycle transmission can be avoided, thereby improving the efficiency and reliability of data transmission.

[0126] After determining the system message queue in the above manner, the scheduling positions of various target OSIs in the sub-cycle can be determined sequentially, and the corresponding target OSIs can be sent according to the determined scheduling positions in the sub-cycle.

[0127] Specifically, SSBs are sent in the form of SSB burst sets (i.e., SSB groups in this paper). After each SSB group is sent within a sub-cycle, the scheduling position of the target OSI of different types corresponding to that SSB group within the sub-cycle can be determined according to the system message queue. The corresponding OSI messages are then sent in sequence according to the scheduling order, ensuring that different types of OSIs with the same SSB index are sent within the current sub-cycle and do not cross over to other sub-cycles, thereby improving the transmission efficiency and timing accuracy of system messages.

[0128] The following section will detail how to determine the scheduling positions for different types of OSI messages and the specific sending process based on the system message queue:

[0129] Optionally, for a type of target OSI within a sub-cycle, the following operations can be performed sequentially according to the scheduling order, as shown in Figure 5, which is a scheduling flowchart of a different type of target OSI in an embodiment of this application, including the following steps S51 to S54:

[0130] S51: Determine the window offset of the time window where the target OSI is located based on the scheduling information corresponding to the target OSI.

[0131] Among them, target OSI refers to a type of target OSI that is sent within the same time window; scheduling information refers to the specific configuration that affects OSI scheduling within a specific sub-period; window offset refers to the offset distance of OSI relative to the window start position within the time window. This offset can affect the timing and order of OSI transmission to ensure that the corresponding OSI messages are effectively transmitted within the specified time.

[0132] Determining the window offset of the target OSI time window ensures accurate scheduling of OSI messages within sub-cycles, and the window offset locates the OSI transmission time slot, thereby ensuring the orderly transmission of different messages within different time windows.

[0133] The calculation process for the window offset will be explained in detail below:

[0134] First, the preset window length corresponding to the target OSI is obtained through the system message queue. This length is used to indicate the time window range allocated for different types of target OSI within the sub-cycle.

[0135] In this application embodiment, the methods for calculating the window offset include, but are not limited to, the following two:

[0136] In calculation method one, if the scheduling information includes the entry number of the target OSI, the first window offset of the target OSI is determined based on the entry number and the preset window length; the entry number indicates the scheduling order of the target OSI within the sub-cycle.

[0137] Specifically, if the scheduling information includes the entry number of the target OSI, denoted as n, then the first window offset X1 can be calculated using Formula 1 based on the entry number n and the preset window length w: X1=(n-1)×w (Formula 1)

[0138] Assuming that within a sub-cycle, the SSB groups to be transmitted are SSB0 to 3, and the number of OSIs to be scheduled is 3, labeled as OSI-1 (SSB0 to 3), OSI-2 (SSB0 to 3), and OSI-3 (SSB0 to 3), and if the preset window length is 8 slots (w = 2 slots), then according to Formula 1, the first window offset of OSI-1 (SSB0 to 3) is (1-1) × 8 = 0 slots, indicating that OSI-1 (SSB0 to 3) OSI-2 (SSB0~3) will be scheduled for transmission in the 0th time slot of the sub-cycle; the first window offset of OSI-2 (SSB0~3) is (2-1)×8=8 slots, indicating that OSI-2 (SSB0~3) will be scheduled for transmission in the 8th time slot of the sub-cycle; the first window offset of OSI-3 (SSB0~3) is (3-1)×8=16 slots, indicating that OSI-3 (SSB0~3) will be scheduled for transmission in the 16th time slot of the sub-cycle.

[0139] Calculation Method 2: If the scheduling information includes the time window position index of the target OSI, then the second window offset of the target OSI is determined based on the time window position index and the preset window length; the time window position index represents the position of the target OSI within the time window during the sub-period.

[0140] Specifically, if the scheduling information includes the target OSI time window position index, denoted as si-WindowPosition-SubPeriod, then the first window offset X2 can be calculated using Formula 2 based on the time window position index si-WindowPosition-SubPeriod and the preset window length w: X2=(si-WindowPosition-SubPeriod-1)×w (Formula 2)

[0141] Taking the example of SSB groups SSB0 to 3 to be transmitted and OSI numbers to be scheduled as 3 within a sub-cycle, and assuming the time window position index values ​​are: OSI-1 time window position index is 2, OSI-2 time window position index is 3, and OSI-3 index time window position is 4, if the preset window length is still 8 slots (w = 8 slots), then the second window offset of OSI-1 is 16 slots, indicating that OSI-1 will be scheduled for transmission in the 16th slot of the sub-cycle; the second window offset of OSI-2 is 24 slots, indicating that OSI-2 will be scheduled for transmission in the 24th slot of the sub-cycle; and the second window offset of OSI-3 is 32 slots, indicating that OSI-3 will be scheduled for transmission in the 32nd slot of the sub-cycle.

[0142] By accurately calculating the window offset, the order in which OSI messages are sent can be ensured, and time conflicts within the same time window can be avoided, effectively improving the scheduling efficiency of the system.

[0143] Next, based on the window offset, the specific time slot for sending the OSI message and its corresponding system frame number are determined.

[0144] S52: Determine the starting time slot and first starting system frame number of the target OSI based on the window offset;

[0145] The starting time slot indicates the position of the OSI message transmission in the current frame, while the starting system frame number indicates the frame sequence number corresponding to that time slot.

[0146] By specifying the starting time slot and system frame number, OSI messages can be accurately sent to the specific time slot, avoiding conflicts or packet loss caused by unclear timing.

[0147] The calculation process for the starting time slot and the starting system frame number will be described in detail below. In an optional implementation, S52 includes S521 to S523:

[0148] S521: Determine the starting time slot based on the window offset and the number of frame time slots; where the number of frame time slots is the number of time slots in a radio frame.

[0149] Specifically, the initial time slot a can be calculated using Formula 3: a = X mod N (Formula 3)

[0150] Where a represents the starting time slot, X represents the window offset, which can be X1 or X2, N is the number of time slots in a radio frame, and mod operation refers to calculating the remainder obtained after dividing two numbers.

[0151] S522: Determine the first starting system frame number of the target OSI based on the second starting system frame number where the sub-cycle is located, the window offset, and the number of frame slots.

[0152] Specifically, the first starting system frame number (SFN) can be calculated using Formula 4: SFN = StartSFNSSB SSB-subperiodicty +FLOOR(X / N) (Formula 4)

[0153] Wherein, SFN represents the first starting system frame number, which is the starting system frame number when the target OSI needs to be scheduled; StartSFNSSB SSB-SubPeriodicity The second starting system frame number is the second starting system frame number in which the sub-cycle is located; X represents the window offset, which can be either X1 or X2; N is the number of time slots in a radio frame; the FLOOR (round down) operation refers to rounding a value down to the nearest integer, and it returns the largest integer not greater than that value.

[0154] S523: Transmit the target OSI within the sub-cycle according to the starting time slot and the first starting system frame number.

[0155] Calculating the starting time slot and first starting system frame number of the target OSI using the formula above ensures that the OSI message scheduling process is strictly synchronized with system time, avoiding time slot misalignment and improving the timing accuracy of the communication system. Furthermore, by rationally arranging the transmission of different types of target OSI messages within the divided sub-cycles, the orderly transmission and timely delivery of messages within each sub-cycle are ensured, thereby improving the overall communication efficiency and reliability.

[0156] The above describes the initial transmission of different types of target OSI messages within an SSB sub-cycle. If the OSI is transmitted periodically, the target OSI is repeatedly transmitted in other second time periods within the same sub-cycle. In this case, the number of transmissions within the sub-cycle also needs to be considered to ensure effective scheduling and transmission of OSI messages in each cycle. For example, the next transmission time can be set to determine whether to retransmit the corresponding OSI within the current sub-cycle, thus ensuring that periodic transmission does not cause message loss or delay.

[0157] For any target OSI, if the corresponding scheduling information also includes the OSI transmission period, then the starting time slot and the first starting system frame number represent the transmission time of the first transmission of the target OSI within the sub-period.

[0158] In scenarios involving periodic transmissions, it's not only necessary to configure the initial transmission but also to effectively schedule subsequent transmissions. Based on this, the following section will further explain how to ensure accurate transmission of the target OSI within sub-cycles, using scheduling information and the transmission period.

[0159] S53: Based on the OSI transmission period and the latest transmission time corresponding to the target OSI, determine the next transmission time when periodically transmitting the target OSI.

[0160] The latest transmission time is the transmission time of the latest successful transmission of the target OSI, and the next transmission time is the planned transmission time of the next transmission of the OSI. The next transmission time is equal to the latest transmission time plus the OSI transmission period.

[0161] S54: Determine whether to continue transmitting the target OSI within the current sub-cycle based on whether the next transmission time of the target OSI belongs to the current sub-cycle.

[0162] Specifically, in step S54, when sending an OSI signal, it can be divided into the following two cases:

[0163] Case 1: If the next transmission time belongs to the current sub-cycle, then continue to transmit the target OSI within the current sub-cycle.

[0164] Specifically, the next transmission time can be determined to belong to the current sub-period if the sum of the latest OSI transmission time and OSI-Period-SubPeriod is less than SSB-SubPeriodicity.

[0165] The next transmission time is equal to the sum of the latest transmission time and the OSI transmission period, i.e., OSI-Period-SubPeriod. SSB-SubPeriodicity represents the end time of the sub-period. If the obtained next transmission time is less than the end time of the current sub-period, then the next transmission time belongs to the current sub-period, and the target OSI continues to be transmitted within the current sub-period.

[0166] Referring to Figure 6, it is a schematic diagram of the transmission of each OSI in an SSB sub-cycle in an embodiment of this application.

[0167] In one optional embodiment, assuming the SSB sub-period is 40 slots, with 4 SSBs and 2 OSIs transmitted within each sub-period, and assuming that OSIs can be transmitted in each time window, the second starting system frame number of the sub-period is SFN = 20, the number of time slots in a radio frame is N = 20 slots, the preset window length is 4 slots, and the transmission periods of OSI-1 and OSI-2 are the same, both 8 slots, then OSI-1-Period = OSI-2-Period = 8 slots.

[0168] If the scheduling information includes the entry number of the target OSI, the first window offset of OSI-1, X1(OSI-1) = 0 slots, can be calculated using Formula 1. Then, the starting time slot and the starting system frame number can be calculated according to the steps in S52 above. The starting time slot of OSI-1, a(OSI-1) = X1(OSI-1) mod N = 0 mod 20 = 0, can be calculated using Formula 3. The starting system frame number of OSI-1, SFN(OSI-1) = 20 + FLOOR(X1(OSI-1) / N) = 20 + 0 = 20, can be calculated using Formula 4.

[0169] Similarly, we can calculate the first window offset of OSI-2 X1(OSI-2) = 4 slots, the starting time slot of OSI-2 a(OSI-2) = X1(OSI-2) mod N = 4 mod 20 = 4, and the starting system frame number of OSI-2 SFN(OSI-2) = 20 + FLOOR(4 / 20) = 20 + 0 = 20.

[0170] If the scheduling information includes the target OSI time window position index, the window position index of OSI-1 is 1, and the window position index of OSI-2 is 2. The calculated second window offset of OSI-1 is 0 slots, and the resulting starting time slot and starting system frame number of OSI-1 are 0 and 20, respectively. The second window offset of OSI-2 is 4 slots, and the resulting starting time slot and starting system frame number of OSI-1 are 4 and 20, respectively.

[0171] The calculations above yielded the initial transmission scenarios for OSI1 and OSI2. As shown in Figure 6, when both OSI-1 and OSI-2 have the same transmission period of 8 slots, for OSI-1, if the next transmission time falls within the current sub-cycle after the 2nd, 3rd, and 4th transmissions, then the target OSI-1 will be transmitted for the 5th time within the current sub-cycle. Similarly, for OSI-2, if the next transmission time falls within the current sub-cycle after the 2nd, 3rd, and 4th transmissions, then the target OSI-2 will be transmitted for the 5th time within the current sub-cycle.

[0172] In this scenario, the target OSI message will be sent within the current sub-cycle. This means that the system calculates the next time to send a message based on the predetermined OSI sending cycle. If this time overlaps with the current sub-cycle, the system will continue sending the target OSI message. The advantage of this approach is that it ensures all periodic messages are sent at the appropriate time, improving message transmission efficiency and ensuring the timeliness and reliability of information.

[0173] If the next transmission time does not belong to the current sub-cycle after the fifth transmission of OSI-1 and OSI-2 is completed, then the sixth transmission within the current sub-cycle will not continue to transmit the target OSI-1 and OSI-2, which is the second case below.

[0174] Referring to Figure 7, it is a schematic diagram of the transmission of each OSI in another SSB sub-cycle in an embodiment of this application.

[0175] In this sub-cycle, the SSB sub-cycle is still 40 slots, with 4 SSBs and 2 OSIs transmitted within each sub-cycle. At this time, the second starting system frame number of the sub-cycle is SFN=20, the number of time slots in a radio frame is N=20 slots, the preset window length is 4 slots, and the transmission cycles of OSI-1 and OSI-2 are different. The transmission cycle of OSI-1 is 8 slots, and the transmission cycle of OSI-2 is 16 slots.

[0176] At this point, OSI-1 is transmitted in the first time window, OSI-2 is transmitted in the second time window, OSI-1 is transmitted in the third time window, and no OSI is transmitted in the fourth time window. The window offset, starting time slot, and starting system frame number for the first transmission of OSI-1 and OSI-2 are calculated in the same way as in Figure 7 above.

[0177] In Figure 7, if the next transmission time for OSI-1 is within the current sub-cycle when the 2nd, 3rd, and 4th transmissions are completed, then the target OSI-1 will continue to be transmitted for the 5th time within the current sub-cycle.

[0178] However, if the next transmission time for OSI-2 falls within the current sub-cycle after the second transmission is completed, then the target OSI-2 will be transmitted a third time within the current sub-cycle. If the next transmission time does not fall within the current sub-cycle after the third transmission is completed, then the target OSI-2 will not be transmitted a fourth time within the current sub-cycle, which is case two below.

[0179] In one optional embodiment of this application, if the time unit is divided by a burst set of at least twice the number of SSBs, multiple SSB burst sets will be sent within each sub-period, i.e., multiple sets of SSBs will be sent, specifically related to the multiple of the SSB burst set period. Therefore, each sub-period can contain multiple SSB burst set periods, and the transmission time of the OSI to be transmitted corresponding to each SSB burst set must not only fall within that sub-period but also belong to the corresponding SSB burst set period.

[0180] Taking Figure 4 as an example, the sub-period is 20ms, and the SSB burst set period is 10ms. Assuming two SSB burst sets (SSB0-3 and SSB4-7) are sent within one sub-period, then for SSB0-3, the OSI transmission time should be within the first 10ms; for SSB4-7, the OSI transmission time should be within the last 10ms. This ensures that each OSI to be sent is transmitted within the valid time period associated with its corresponding SSB burst set, avoiding message scheduling misalignment. In this way, it ensures that the OSI to be sent is transmitted promptly and accurately within the valid time period of the current SSB burst set.

[0181] Meanwhile, when sending multiple SSB groups within a sub-cycle, taking the transmission of two SSB groups as an example, such as sending SSB0~3 and their corresponding OSI-1 (SSB0~3) and OSI-2 (SSB0~3), or sending SSB4~7 and their corresponding OSI-1 (SSB4~7) and OSI-2 (SSB4~7), each SSB and OSI group has a first time period and a second time period. To distinguish them, the transmission of the second group SSB4~7 can also be referred to as the third time period, and the fourth time period is used to transmit OSI-1 (SSB0~3). For SSBs 4-7 and OSI-2 (SSB4-7), the third and fourth time periods do not overlap, and the second time period precedes the third time period, while the third time period precedes the fourth time period. Of course, if three SSB groups are sent within a cycle, the transmission time periods of the third SSB group and its corresponding OSI can also be called the fifth and sixth time periods. The fifth and sixth time periods do not overlap, and the fourth time period precedes the fifth time period, while the fifth time period precedes the sixth time period. And so on, ensuring that each SSB group and its OSI are transmitted in sequence within the corresponding time period.

[0182] In one optional implementation, when multiple sets of SSBs need to be transmitted within a sub-cycle, if there are still time slots with spare time windows after transmitting the target OSI corresponding to one set of SSBs, the following strategies can be adopted, including but not limited to:

[0183] Strategy 1: Send invalid messages to fill the time slots of the time window.

[0184] If there is no other data to be sent at this time, invalid messages can be sent to fill the empty time window. For example, invalid messages can be sent in the remaining time slots after SSB0~3 and OSI-1 (SSB0~3) and OSI-2 (SSB0~3) are sent in the first 10ms to occupy resources.

[0185] Strategy 2: Send other valid messages.

[0186] Periodic or repetitive messages can be sent using spare time slots. For example, if there are spare time slots after sending SSB0-3 and OSI-1 (SSB0-3) and OSI-2 (SSB0-3) within 10ms, the previous OSI-1 (SSB0-3) and OSI-2 (SSB0-3) messages can be sent repeatedly to ensure that the terminal device receives the relevant messages in a timely manner.

[0187] Strategy 3: Directly send the OSI corresponding to the next SSB group, but resend the OSI corresponding to the group after the next SSB group is sent.

[0188] For example, if there is a spare time slot after sending SSB0~3 and OSI-1 (SSB0~3) and OSI-2 (SSB0~3) within 10ms, the corresponding OSI-1 (SSB4~7) can be sent for SSB4~7. However, after the next group of SSB4~7 is sent, the corresponding OSI-1 (SSB4~7) and OSI-2 (SSB4~7) are resent to ensure that the corresponding OSI-1 (SSB4~7) and OSI-2 (SSB4~7) can be received immediately after SSB4~7 is sent.

[0189] This flexible approach not only improves the utilization efficiency of time slots or windows, but also allows messages to be repeated or adjusted as needed, further optimizing the scheduling and transmission performance of the OSI model.

[0190] Scenario 2: If the next transmission time does not belong to the current sub-cycle, then the target OSI will not be transmitted within the current sub-cycle.

[0191] In scenario two, as illustrated in scenario one above, it is detected that the next transmission time falls within the next sub-cycle, rather than the current sub-cycle. Since the current sub-cycle has reached its end, the target OSI will no longer be transmitted within this sub-cycle. This decision avoids sending information at the wrong time, thereby reducing potential signal interference and resource waste. This mechanism ensures the orderly transmission of messages, avoids message loss or delay due to timing errors, and improves the overall stability and effectiveness of the communication system.

[0192] In summary, this scheduling mechanism ensures that periodically sent OSI messages are delivered accurately within the specified time window, improving communication reliability and efficiency. Simultaneously, it avoids duplicate or delayed message transmission, thereby effectively reducing network load and optimizing system resource utilization.

[0193] Furthermore, during the aforementioned scheduling process, there may be a time window during which OSI data is not transmitted. In such cases, network devices need a certain indication mechanism to inform terminal devices that OSI data transmission has not been performed, so that terminal devices can correctly understand this state and avoid unnecessary waiting or retransmission operations, thereby ensuring the accuracy of message transmission and the efficient use of resources.

[0194] The following section will detail the indication mechanism used to show that the window has not sent an OSI signal:

[0195] If there is a time window in any sub-cycle where OSI is not transmitted, in this embodiment of the application, the time window also needs to transmit other downlink information, including but not limited to SSB, paging, RA (Random Access). Some windows cannot be used to transmit OSI, and the terminal device needs to be explicitly informed of these windows where OSI cannot be transmitted. The time window where OSI is not transmitted can be indicated in at least one of the following ways:

[0196] Instruction Method 1: Define the system message block type of the time window as invalid.

[0197] If the system message queue also includes System Message Block (SIB) types, then the time window's SIB type is defined as invalid to indicate that the time window has not sent OSI.

[0198] In an alternative implementation, a spare value can be modified to the invalid system message Invalidsib in the System Information Block Type Information (SIB-TypeInfo). This can be achieved as follows:

[0199] SIB-TypeInfo::=SEQUENCE{

[0200] type ENUMERATED{sibType2,sibType3,...,Invalidsib,spare2,spare1}

[0201] }

[0202] By defining the SIB type as invalid to indicate that the OSI was not sent in the time window, when the terminal device receives this type of SIB, it will assume that the corresponding time window did not send the OSI, thus ensuring the accuracy of the scheduling information.

[0203] Instruction Method 2: Set the message broadcast status of the time window to null.

[0204] If the system message queue also includes a message broadcast status, then the message broadcast status of the time window is set to null to indicate that no OSI was sent during the time window.

[0205] In an alternative implementation, the message broadcast status information element si-BroadcastStatus-ext can be added to the scheduling information list SchedulingInfo-ext, with a new null value (NULL) added to its value. This configuration corresponds to windows that do not send OSI messages. This can be achieved as follows:

[0206] SchedulingInfo-ext::=SEQUENCE{

[0207] si-BroadcastStatus-ext ENUMERATED{broadcasting, notBroadcasting, NULL, spare}

[0208] sib-MappingInfo SIB-Mapping

[0209] }

[0210] The SIB type sib-MappingInfo can be configured with any one of them; this application does not impose any specific restrictions here.

[0211] By setting the message broadcast status of the time window to null, the terminal device receives a message with the null value and the corresponding time window does not send an OSI message by default.

[0212] Instruction Method 3: Configure target parameters for time windows other than this one.

[0213] If the system message queue also includes target parameters, then by configuring target parameters for other time windows besides this time window, and not configuring target parameters for this time window, it is indicated that OSI has not been sent in this time window; wherein, the target parameters include the time window position index and the OSI sending period.

[0214] In one optional implementation, assume the SSB sub-cycle is 40 slots, with 4 SSBs transmitted within this sub-cycle. There are 3 OSIs: OSI-1 (SIB2 / SIB3), OSI-2 (SIB4 / SIB5), and OSI-3 (SIB19). Each OSI has the same OSI cycle of 8 slots, and the preset window length is 4 slots. The 3 OSIs are transmitted in the 3rd to 5th time windows, where target parameters are configured. In other time windows where no target parameters are configured, no OSIs are transmitted.

[0215] See Figure 8, which is a schematic diagram of a time window without sending OSI configuration in an embodiment of this application.

[0216] In one optional implementation, according to Method 1, the OSI scheduling types in the scheduling information list in Figure 8 are, in order: OSI-1 (Invalidsib), OSI-2 (Invalidsib), OSI-3 (SIB2 / SIB3), OSI-4 (SIB4 / SIB5), OSI-5 (SIB19), OSI-6 (Invalidsib)...OSI-10 (Invalidsib). According to Method 2, the OSI broadcast states of schedulingInfoList in Figure 8 are, in order: NULL, NULL, broadcasting, broadcasting, broadcasting, NULL...NULL. According to Method 3, the si-WindowPosition-SubPeriod of each SI in schedulingInfoList that actually sends OSI content are 3, 4, and 5, respectively.

[0217] By defining the time windows where OSI signals are not transmitted as described above, potential signal interference and resource waste can be effectively reduced, ensuring orderly message transmission and improving communication stability and effectiveness. Furthermore, by explicitly identifying the windows where OSI signals are not transmitted, terminal devices can optimize their resource management strategies, thereby further improving overall communication efficiency.

[0218] Referring to Figure 9, it is a schematic diagram illustrating the differences between the OSI system transmission method and related OSI transmission technologies in an embodiment of this application.

[0219] In this embodiment, the SSB transmission period is divided into multiple SSB sub-periods according to integer multiples of the SSB burst set period. Within each sub-period, the network device maps the SSB to the corresponding OSI.

[0220] Specifically, Figure 9 illustrates this mapping process, where the SSB group within each SSB sub-cycle will send the corresponding multiple OSI types.

[0221] In related technologies, OSI transmission is not closely coordinated with the SSB burst set period, but may span multiple SSB burst set periods.

[0222] For example, in related technologies, after all OSI types corresponding to SSB indices have been sent, the next OSI type is sent, as shown in Figure 9. The SSB indices are SSB0 to 15. After the OSI-1 types corresponding to SSB0 to 15 (including SSB0 to 3, SSB4 to 7, SSB8 to 11, and SSB12 to 15) have been sent, namely OSI-1(SSB0 to 3), OSI-1(SSB4 to 7), OSI-1(SSB8 to 11), and OSI-1(SSB12 to 15), the next OSI type is sent, i.e., OSI- In cases like 2(SSB0~3), OSI-2(SSB4~7), OSI-2(SSB8~11), and OSI-2(SSB12~15), after SSB0~3 is sent, some OSI messages (such as OSI-1(SSB0~3)) may be sent within the same cycle, but other OSI messages (such as OSI-2(SSB0~3) and OSI-3(SSB0~3)) need to wait for the next SSB burst cycle before they can be sent. This may increase the latency of OSI transmission, as multiple SSB transmission cycles are required. Simultaneously, the OSI-1 (SSB4~7) corresponding to SSB4~7 will be sent before SSB4~7, leading to inconsistent latency between different SSB cycles. This forces the terminal device to process multiple OSI messages from different time periods, increasing processing complexity.

[0223] In one optional embodiment of this application, the SSB transmission period is 80ms. By using multiples of the SSB burst set period as the division unit, a complete SSB transmission period can be divided into multiple SSB sub-periods. In the figure, the SSB sub-period is 20ms. Within each sub-cycle, one SSB group (e.g., SSB0-3, SSB4-7, etc.) is sent, and each SSB group corresponds to multiple OSI messages. For example, in the first sub-cycle, SSB0-3 corresponds to OSI-1 (SSB0-3) and OSI-2 (SSB0-3). After sending SSB0-3 in the first time period of the first sub-cycle, the corresponding OSI messages (OSI-1 (SSB0-3) and OSI-2 (SSB0-3)) are sent immediately in the second time period of the first sub-cycle. In the second sub-cycle, SSB4-7 corresponds to OSI-1 (SSB4-7) and OSI-2 (SSB4-7). After sending SSB4-7 in the first time period of the second sub-cycle, the corresponding OSI messages (OSI-1 (SSB4-7) and OSI-2 (SSB4-7)) are sent immediately in the second time period of the second sub-cycle. In this way, each SSB sub-cycle ensures that the SSB and its corresponding different types of OSI messages can be sent within the same sub-cycle.

[0224] In summary, the technical solution of this application ensures close coordination between OSI and SSB transmission, avoiding scheduling mismatches between OSI and SSB and improving OSI transmission efficiency. In the embodiments of this application, the network device configures a system message queue to ensure that all OSI messages corresponding to all SSB groups within a sub-cycle are transmitted before initiating the transmission of SSB groups and their corresponding OSI messages in the next sub-cycle. This means that within a sub-cycle, SSBs are scheduled one-to-one with all OSI messages within that sub-cycle, ensuring that all OSI messages are transmitted in a timely manner before the end of each sub-cycle.

[0225] Based on the same inventive concept, and referring to Figure 10, this application embodiment also provides another method for transmitting system messages applied to a terminal device, the specific steps of which are as follows:

[0226] S101: During the SSB reception period, receive SSB and OSI in at least two sub-cycles.

[0227] The SSB reception period refers to the time period during which the terminal device receives SSB and OSI within the network device's SSB transmission period. OSI is received in a time-division manner within this reception period. The SSB reception period and the network device's SSB transmission period are kept in the same time sequence (allowing for a certain delay) to ensure the integrity and orderliness of system messages.

[0228] The receiving mechanism on the terminal device side is essentially the same as the message scheduling mechanism of the network device: the terminal device receives relevant SSB and OSI messages step by step according to the system message queue sent by the network device and the divided sub-cycles to achieve the synchronization and timeliness of message transmission.

[0229] Specifically, the terminal device will first acquire sub-cycles to ensure that it can keep pace with the network device’s reception rhythm and accurately locate the required reception time window.

[0230] S1011: In the first time period within a sub-cycle, receive the SSB group corresponding to the sub-cycle;

[0231] S1012: In the second time period within the same sub-cycle, receive the target OSI corresponding to the SSB group; the target OSI includes: OSI of different types corresponding to the index of the SSB in the SSB group.

[0232] Optionally, the first time period and the second time period do not overlap, and the first time period is located before the second time period.

[0233] Optionally, the scheduling position of the target OSI in the second time period is determined based on the system message queue corresponding to the sub-cycle; the system message queue is used to indicate the scheduling order of different types of OSI.

[0234] Optionally, the scheduling location includes the starting time slot and the first starting system frame number;

[0235] The first starting system frame number is related to the second starting system frame number of the sub-cycle, the window offset of the time window where the target OSI is located, and the number of frame slots. The number of frame slots is the number of slots contained in a radio frame.

[0236] The terminal device determines the specific time point within a sub-cycle to receive OSI messages by using the window offset, starting timeslot, and system frame number from the network scheduling information. Based on this scheduling information, the terminal device receives the scheduled OSI messages within the corresponding timeslot and frame number. In this way, the terminal device can receive system messages from the network in an orderly and efficient manner within each sub-cycle, and further adjust its communication strategy based on the received OSI messages, ensuring the rational utilization of network resources and communication stability.

[0237] Optionally, the method also includes:

[0238] In other second time periods within the same sub-cycle, the target OSI is repeatedly received.

[0239] In the subsequent second time period within the same sub-cycle, the terminal device can repeatedly receive the target OSI to ensure that the terminal device can successfully obtain the necessary system information.

[0240] On the terminal device side, if a sub-cycle contains multiple SSBs (e.g., SSB0-3 and SSB4-7), the terminal device will receive each SSB and its corresponding OSI message in the corresponding time period sequence. Specifically, the terminal device will first receive the first SSB (e.g., SSB0-3) in the first time period of the sub-cycle and the corresponding OSI message of SSB0-3 in the second time period. Then, it will receive the second SSB (e.g., SSB47) in the third time period and the corresponding OSI message of SSB4-7 in the fourth time period. In this way, within a sub-cycle, the terminal device can sequentially complete the reception process of multiple SSBs and their OSI messages.

[0241] Optionally, at least two sub-periods are obtained by dividing the SSB transmission period into units that are integer multiples of the SSB burst set transmission period.

[0242] Optionally, the time window during the second time period when the network device does not send OSI data can be determined by at least one of the following methods:

[0243] The system message block type for the time window is invalid;

[0244] The message broadcast status of the time window is null.

[0245] Other time windows besides the main time window are configured with target parameters.

[0246] In some situations, network devices may choose not to send OSI messages within a certain time window due to resource constraints, network congestion, or scheduling optimization strategies. In this case, terminal devices will also be unable to receive OSI messages within that time window. If the network side provides this instruction through one of the methods mentioned above, the terminal device will determine whether OSI messages have been sent within that time window based on the scheduling information in the system message queue (including but not limited to the system message block (SIB) type, message broadcast status, or target parameter configuration). If the SIB type of the time window is set to invalid, the message broadcast status is empty, or the window is not configured with target parameters, the terminal device can determine that the lack of received OSI messages within that time window is due to the network side not sending them rather than a reception failure, thereby ensuring that the terminal device's message reception strategy is more accurate and efficient.

[0247] For terminal devices, upon receiving an SSB, they can quickly acquire frequency offset and latency information and immediately begin receiving all OSIs corresponding to that SSB group, without having to wait for multiple SSB cycles. This not only reduces the latency of the terminal receiving OSIs but also improves the overall user experience.

[0248] Based on the same inventive concept, this application also provides a system message transmission device 1100, applied to a network device, as shown in FIG11, which is a schematic diagram of the structure of a system message transmission device according to an embodiment of this application, and may include:

[0249] The sending unit 1101 is configured to send SSB and other system message OSIs according to at least two sub-cycles within the SSB transmission period, wherein: in the first time period within the sub-cycle, the SSB group corresponding to the sub-cycle is sent; in the second time period within the same sub-cycle, the target OSI corresponding to the SSB group is sent; the target OSI includes: an OSI of a different type corresponding to the index of the SSB in the SSB group.

[0250] Optionally, the scheduling position of the target OSI within the second time period is determined based on the system message queue corresponding to the sub-period; the system message queue is used to indicate the scheduling order of the different types of OSI.

[0251] Optionally, the scheduling position of the target OSI within the second time period is determined based on the system message queue corresponding to the sub-period; the system message queue is used to indicate the scheduling order of the different types of OSI.

[0252] Optionally, the scheduling location includes a starting time slot and a first starting system frame number. The first starting system frame number is related to the second starting system frame number where the sub-cycle is located, the window offset of the time window where the target OSI is located, and the number of frame time slots. The number of frame time slots is the number of time slots contained in a radio frame.

[0253] Optionally, the transmitting unit 1101 is further configured as follows:

[0254] The target OSI is repeatedly transmitted during other second time periods within the same sub-cycle.

[0255] Optionally, at least two of the sub-periods are obtained by dividing the SSB transmission period into integer multiples of the SSB burst set transmission period.

[0256] Optionally, if there is a time window during the second time period during which OSI is not transmitted, the device 1100 further includes:

[0257] Indication unit 1102 indicates that the time window has not sent OSI in at least one of the following ways:

[0258] Define the system message block type of the time window as invalid;

[0259] Set the message broadcast status of the time window to null.

[0260] Configure target parameters for time windows other than the aforementioned time window.

[0261] Based on the same inventive concept, this application also provides a system message transmission device 1200, applied to a terminal, as shown in FIG12, which is a schematic diagram of the structure of a system message transmission device according to an embodiment of this application, and may include:

[0262] The receiving unit 1201 is configured to receive SSB and other system message OSIs according to at least two sub-cycles within the SSB receiving period, wherein: in the first time period within the sub-cycle, the SSB group corresponding to the sub-cycle is received; in the second time period within the same sub-cycle, the target OSI corresponding to the SSB group is received; the target OSI includes: OSI of a different type corresponding to the index of the SSB in the SSB group.

[0263] Optionally, the scheduling position of the target OSI within the second time period is determined based on the system message queue corresponding to the sub-period; the system message queue is used to indicate the scheduling order of the different types of OSI.

[0264] Optionally, the scheduling position of the target OSI within the second time period is determined based on the system message queue corresponding to the sub-period; the system message queue is used to indicate the scheduling order of the different types of OSI.

[0265] Optionally, the scheduling location includes a starting time slot and a first starting system frame number. The first starting system frame number is related to the second starting system frame number where the sub-cycle is located, the window offset of the time window where the target OSI is located, and the number of frame time slots. The number of frame time slots is the number of time slots contained in a radio frame.

[0266] Optionally, the receiving unit 1201 is further configured as follows:

[0267] The target OSI is repeatedly received during other second time periods within the same sub-cycle.

[0268] Optionally, at least two of the sub-periods are obtained by dividing the SSB reception period into integer multiples of the SSB burst set reception period.

[0269] Optionally, the device 1200 further includes:

[0270] The determining unit 1202 determines the time window during the second time period when the network device does not send OSI data through at least one of the following methods:

[0271] The system message block type for the time window is defined as invalid;

[0272] The message broadcast status of the time window is set to null.

[0273] Configure target parameters for time windows other than the time window itself.

[0274] For ease of description, the above sections are divided into modules (or units) according to their functions and described separately. Of course, in implementing this application, the functions of each module (or unit) can be implemented in one or more software or hardware components.

[0275] In this application embodiment, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0276] Having described a method and apparatus for transmitting system messages according to an exemplary embodiment of this application, we will now describe an electronic device according to another exemplary embodiment of this application.

[0277] Those skilled in the art will understand that various aspects of this application can be implemented as a system, method, or program product. Therefore, various aspects of this application can be specifically implemented in the following forms: a completely hardware implementation, a completely software implementation (including firmware, microcode, etc.), or a combination of hardware and software implementations, collectively referred to herein as a "circuit," "module," or "system."

[0278] Based on the same inventive concept as the above-described method embodiments, this application also provides an electronic device. In one embodiment, the electronic device may be a server, such as the network device 130 shown in FIG1. ​​In this embodiment, the structure of the electronic device may be as shown in FIG13, including a memory 1301, a communication module 1303, and one or more processors 1302.

[0279] The memory 1301 is configured to store computer programs executed by the processor 1302. The memory 1301 may mainly include a program storage area and a data storage area. The program storage area may store the operating system and programs required to run instant messaging functions, etc.; the data storage area may store various instant messaging information and operation instruction sets, etc.

[0280] Memory 1301 may be volatile memory, such as random-access memory (RAM); memory 1301 may also be non-volatile memory, such as read-only memory, flash memory, hard disk drive (HDD), or solid-state drive (SSD); or memory 1301 may be any other medium capable of carrying or storing a desired computer program having the form of instructions or data structures and accessible by a computer, but is not limited thereto. Memory 1301 may be a combination of the above-described memories.

[0281] Processor 1302 may include one or more central processing units (CPUs) or digital processing units, etc. Processor 1302 is configured to implement the above-mentioned method of transmitting system messages when calling computer programs stored in memory 1301.

[0282] The communication module 1303 is configured to communicate with terminal devices and other servers.

[0283] This application embodiment does not limit the specific connection medium between the memory 1301, communication module 1303, and processor 1302. In Figure 13, the memory 1301 and processor 1302 are connected via a bus 1304, which is depicted as a thick line. The connection methods between other components are merely illustrative and not intended to be limiting. The bus 1304 can be an address bus, data bus, control bus, etc. For ease of description, only one thick line is used in Figure 13, but this does not imply that there is only one bus or one type of bus.

[0284] The memory 1301 stores a computer storage medium, which in turn stores computer-executable instructions configured to implement a system message transmission method according to an embodiment of this application. The processor 1302 is configured to execute the aforementioned system message transmission method, as shown in FIG2.

[0285] In some alternative implementations, various aspects of the system message transmission method provided in this application can also be implemented in the form of a program product, which includes a computer program. When the program product is run on an electronic device, the computer program is configured to cause the electronic device to perform the steps in the system message transmission method according to various exemplary embodiments of this application described above. For example, the electronic device can perform the steps shown in FIG2 or FIG5.

[0286] The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of readable storage media include: electrical connections having one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0287] The program product of the embodiments of this application may employ a portable compact disc read-only memory (CD-ROM) and include a computer program, and may run on an electronic device. However, the program product of this application is not limited thereto. In this document, the readable storage medium may be any tangible medium that contains or stores a program that may be used by or in conjunction with a command execution system, apparatus, or device.

[0288] A readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying a readable computer program. This propagated data signal may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of sending, propagating, or transmitting a program for use by or in conjunction with a command execution system, apparatus, or device.

[0289] Computer programs contained on readable media may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.

[0290] Computer programs for performing the operations of this application can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The computer program can execute entirely on the user's electronic device, partially on the user's electronic device, as a standalone software package, partially on the user's electronic device and partially on a remote electronic device, or entirely on a remote electronic device or server. In cases involving remote electronic devices, the remote electronic device can be connected to the user's electronic device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external electronic device (e.g., via the Internet using an Internet service provider).

[0291] It should be noted that although several units or sub-units of the device have been mentioned in the detailed description above, this division is merely exemplary and not mandatory. In fact, according to embodiments of this application, the features and functions of two or more units described above can be embodied in one unit. Conversely, the features and functions of one unit described above can be further divided and embodied by multiple units.

[0292] Furthermore, although the operations of the method of this application are described in a specific order in the accompanying drawings, this does not require or imply that these operations must be performed in that specific order, or that all the operations shown must be performed to achieve the desired result. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.

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

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

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

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

[0297] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.

[0298] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method for transmitting system messages, the method comprising: During the SSB (Synchronization Signal Block) transmission cycle, the SSB and other OSI (System Information Structure) messages are transmitted in at least two sub-cycles, including: In the first time period within the sub-cycle, the SSB group corresponding to the sub-cycle is sent; In the second time period within the same sub-cycle, a target OSI corresponding to the SSB group is sent; the target OSI includes OSIs of different types corresponding to the indices of SSBs in the SSB group.

2. The method as described in claim 1, wherein, The first time period and the second time period do not overlap, and the first time period is located before the second time period.

3. The method as described in claim 1, wherein, The scheduling position of the target OSI within the second time period is determined based on the system message queue corresponding to the sub-period; the system message queue is used to indicate the scheduling order of the different types of OSI.

4. The method of claim 3, wherein, The scheduling location includes the starting time slot and the first starting system frame number; The first starting system frame number is related to the second starting system frame number in which the sub-cycle is located, the window offset of the time window in which the target OSI is located, and the number of frame slots, wherein the number of frame slots is the number of slots contained in a radio frame.

5. The method of claim 1, wherein, The method further includes: The target OSI is repeatedly transmitted during other second time periods within the same sub-cycle.

6. The method according to any one of claims 1 to 5, wherein, At least two of the sub-periods are obtained by dividing the SSB transmission period into integer multiples of the SSB burst set transmission period.

7. The method according to any one of claims 1 to 5, wherein, If, within the second time period, there exists a time window during which OSI is not transmitted, the method further includes: The time window was not sent OSI in at least one of the following ways: Define the system message block type of the time window as invalid; Set the message broadcast status of the time window to null. Configure target parameters for time windows other than the aforementioned time window.

8. A system message transmission device, comprising: The transmitting unit is configured to transmit SSB and other system messages OSI according to at least two sub-cycles within the SSB transmission cycle, wherein: In the first time period within the sub-cycle, the SSB group corresponding to the sub-cycle is sent; In the second time period within the same sub-cycle, a target OSI corresponding to the SSB group is sent; the target OSI includes OSIs of different types corresponding to the indices of SSBs in the SSB group.

9. An electronic device comprising a processor and a memory, wherein, The memory stores a computer program that, when executed by the processor, causes the processor to perform the steps of any one of the methods described in claims 1 to 7.

10. A computer-readable storage medium comprising a computer program, which, when executed on an electronic device, is configured to cause the electronic device to perform the steps of any one of the methods of claims 1 to 7.

11. A computer program product comprising a computer program stored in a computer-readable storage medium; wherein when a processor of an electronic device reads the computer program from the computer-readable storage medium, the processor executes the computer program such that the electronic device performs the steps of any one of the methods of claims 1 to 7.

Images