System information sending method and communication device

Abstract

The embodiment of the invention provides a system information sending method and a communication device. The method comprises the following steps that: network equipment determines a first sending period and a time domain resource corresponding to the first sending period according to a repeated transmission period of the RMSI, and sends the RMSI to terminal equipment according to the first sending period and the time domain resource corresponding to the first sending period. Wherein the repeated transmission period is a repeated transmission period for transmitting the RMSI through each beam in the plurality of beams. The time domain resource corresponding to the first sending period comprises the time domain resource which is used for transmitting a first beam group in the plurality of beams and not transmitting other beams except the first beam group in the plurality of beams in the time domain resource corresponding to the repeated transmission period, that is, the RMSI does not need to be sent through each beam in one repeated transmission period, and the RMSI does not need to be sent through each beam in the repeated transmission period. And thus, the time domain resource overhead proportion for transmitting the RMSI is reduced. Furthermore, the first beam group is repeatedly transmitted in the first sending period, so that the degree of damage to the RMSI merging gain can be reduced.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to a system information sending method and a communication device. Background Art

[0002] The synchronization signal / physical broadcast channel block (SSB) includes a master information block (MIB), which includes the configuration parameters required to obtain the remaining minimum system information (RMSI). Among them, RMSI includes the system information (SI) required for the terminal device to complete the initial access. Among them, in order for the terminal device receiving the SSB to receive the RMSI, the coverage range between the beam sending the SSB and the beam sending the RMSI of the network device needs to be the same, and then the network device needs to traverse each RMSI beam in multiple RMSI beams with different coverage ranges within a transmission repetition period (transmission repetition periodicity) to send RMSI.

[0003] However, when the above-mentioned repeated transmission period is small, the time domain resource overhead of transmitting RMSI will account for a large proportion in the time domain resources corresponding to the repeated transmission period. Therefore, how to reduce the proportion of time domain resource overhead of transmitting RMSI is an urgent problem to be solved. Summary of the invention

[0004] The system information sending method and communication device provided in the embodiments of the present application can reduce the proportion of time domain resource overhead for transmitting RMSI.

[0005] To achieve the above objectives, the embodiments of the present application adopt the following technical solutions:

[0006] In the first aspect, a communication method is provided, which can be executed by a network device, or by a component of the network device, such as a processor, chip, or chip system of the network device, or by a logic module or software that can realize all or part of the functions of the network device. The following is an example of the method being executed by a network device. The method includes: the network device determines the first transmission period and the time domain resources corresponding to the first transmission period according to the repeated transmission period of RMSI, and sends RMSI to the terminal device according to the first transmission period and the time domain resources corresponding to the first transmission period. Among them, the repeated transmission period is a repeated transmission period for transmitting RMSI through each beam in a plurality of beams. The time domain resources corresponding to the first transmission period include: within the time domain resources corresponding to the repeated transmission period, the time domain resources for transmitting the first beam group in a plurality of beams, and not transmitting the time domain resources of other beams in the plurality of beams except the first beam group, and the first beam group is repeatedly transmitted in the first transmission period.

[0007] Since in the embodiment of the present application, the network device sends RMSI through the time domain resources corresponding to the first sending period, and thus the network device can send RMSI only through the first beam group within the time domain resources corresponding to the repeated transmission period, without sending RMSI through each beam, thereby reducing the proportion of time domain resource overhead for transmitting RMSI within the time domain resources corresponding to the repeated transmission period. Furthermore, the first beam group is repeatedly transmitted within the first sending period, thereby reducing the degree of damage to the RMSI combining gain. Therefore, based on the system information sending method provided in the embodiment of the present application, the degree of damage to the RMSI combining gain can be reduced while reducing the proportion of time domain resource overhead for transmitting RMSI.

[0008] In one possible implementation, each beam in the multiple beams corresponds to an SSB. For example, each beam in the multiple beams may be an SSB beam corresponding to each SSB in the multiple SSBs, and the multiple SSBs may be multiple SSBs in an SSB burst set. For example, 4 SSBs are transmitted in an SSB burst set, and the number of the multiple beams is 4. For another example, 64 beams are transmitted in an SSB burst set, and the number of the multiple beams is 64. Furthermore, each beam in the multiple beams may also be a beam having a coverage range close to that of the SSB beam corresponding thereto, and the embodiments of the present application do not specifically limit this.

[0009] In one possible implementation, the time domain resources used to transmit each of the multiple beams are determined based on the SSB corresponding to each of the multiple beams.

[0010] In a possible implementation, the repetition transmission period may refer to: the repetition transmission period of the RMSI transmitted by each of the multiple beams within the transmission period of the RMSI. The repetition transmission period may be a multiple of 20ms, such as 20ms, 40ms, 60ms, 80ms, or 160ms. It should be understood that the repetition transmission period may not be a multiple of 20ms, and the embodiments of the present application do not specifically limit this.

[0011] In a possible implementation, the first transmission period may be an integer multiple of the repetitive transmission period. For example, the first transmission period may be 2 times, 3 times, 4 times, or more times of the repetitive transmission period. Further, the first transmission period may be 160 ms, or the first transmission period may be greater than 160 ms, which is not specifically limited in the embodiments of the present application.

[0012] In a possible implementation, within the time domain resources corresponding to the first transmission cycle, the time domain resources used to transmit each of the multiple beams belong to the time domain resources corresponding to each of the multiple beams within the repeated transmission cycle. For example, taking the first transmission cycle as twice the repeated transmission cycle, and 16 beams (i.e., beam #1 to beam #16) are transmitted within the repeated transmission cycle, the time domain resources corresponding to the first transmission cycle include the time domain resource #1 corresponding to the first repeated transmission cycle, and the time domain resource #2 corresponding to the second repeated transmission cycle. Among them, within the first transmission cycle, the time slot used to transmit beam #1 can be the time slot for transmitting beam #1 within time domain resource #1, and the time slot used to transmit beam #16 can be the time slot for transmitting beam #1 within time domain resource #16. That is to say, within the time domain resources corresponding to the first transmission cycle, the time domain resources corresponding to each of the multiple beams within the repeated transmission cycle can be reused.

[0013] Furthermore, the time domain resources corresponding to the first transmission period may include time domain resources for transmitting only the first beam, that is, time domain resources for transmitting the first beam group among multiple beams, and not transmitting other beams among multiple beams except the first beam group, within the time domain resources corresponding to the repeated transmission period. In other words, within the time domain resources corresponding to the repeated transmission period, the proportion of time domain resource overhead for transmitting RMSI can be reduced by not transmitting other beams except the first beam group.

[0014] In a possible implementation, the first beam group may include any Y beams from the multiple beams. Taking the multiple beams as M beams as an example, the value range of Y is: [1, M). When Y is greater than 1, the Y beams may be adjacent to each other, or spaced apart, and the embodiment of the present application does not specifically limit this. Furthermore, the first beam group is repeatedly transmitted within the first transmission cycle. The number of repeated transmissions of the first beam group may be 1, 2, 3, or more times, and the embodiment of the present application does not specifically limit this. That is to say, for terminal devices within the coverage of the first beam group, due to the repeated transmission of the first beam group, the terminal device can receive RMSI multiple times within the first transmission cycle, thereby obtaining a combined gain of RMSI.

[0015] It can be understood that for the terminal device to perform RMSI merging, the terminal device can receive 3 to 5 RMSIs within a given time to perform RMSI merging, and the obtained RMSI merging gain can meet the coverage requirement.

[0016] Furthermore, in a possible implementation, the time interval for repeated transmission of the first beam group can be equal to the above-mentioned repeated transmission period. That is to say, since the period of repeated transmission of the first beam remains unchanged, the terminal device within the coverage of the first beam group can receive at least two RMSIs for RMSI merging within a given time, thereby reducing the degree of damage to the RMSI merging gain. It can be understood that when the number of repeated transmissions of the first beam group is greater than or equal to 2 times, and the time interval for repeated transmission of the first beam group can be equal to the above-mentioned repeated transmission period, the terminal device within the coverage of the first beam group can receive at least 3 RMSIs within a given time, that is, the RMSI merging gain will not be damaged.

[0017] In a possible implementation, in the time domain resources corresponding to the repeated transmission period, the time domain resources used to transmit the first beam group among the multiple beams, and not to transmit the time domain resources of the other beams except the first beam group among the multiple beams, include: in the time domain resources corresponding to each repeated transmission period among the time domain resources corresponding to N1 repeated transmission periods, the time domain resources used to transmit the first beam, and not to transmit the other beams except the first beam group among the multiple beams, where N1 is an integer greater than 1. It can be understood that by using multiple time domain resources that only transmit the first beam group, the proportion of time domain resource overhead for transmitting RMSI in the time domain resources corresponding to the first transmission period can be reduced as a whole.

[0018] In a possible implementation, the time domain resources corresponding to each of the time domain resources corresponding to N1 repetition transmission periods are spaced apart from each other. The interval may be, for example, 1 repetition transmission period, 2 repetition transmission periods, or more repetition transmission periods. Furthermore, the interval between the time domain resources corresponding to two different repetition transmission periods may be variable. For example, taking N1 as 3 as an example, the interval between the time domain resources corresponding to the first repetition transmission period and the time domain resources corresponding to the second repetition transmission period may be 1 repetition transmission period. The interval between the time domain resources corresponding to the second repetition transmission period and the time domain resources corresponding to the third repetition transmission may be 2 repetition transmission periods.

[0019] In a possible implementation, the time domain resources corresponding to each of the time domain resources corresponding to the N1 repeated transmission periods are adjacent to each other. It can be understood that, compared with the case where the time domain resources corresponding to the above-mentioned N1 repeated transmission periods are spaced from each other, the time domain resources corresponding to the N1 repeated transmission periods are adjacent to each other, which can reduce the transmission time required for transmitting the N1 first beam groups only, and further reduce the proportion of time domain resource overhead for transmitting RMSI.

[0020] In a possible implementation, when N1 is greater than 2, time domain resources corresponding to at least two of the time domain resources corresponding to the N1 repeated transmission periods are adjacent to each other. It can be understood that the time domain resources corresponding to at least two repeated transmission periods are adjacent to each other, which can reduce the proportion of time domain resource overhead for transmitting RMSI in the time domain resources corresponding to adjacent repeated transmission periods.

[0021] In a possible implementation, the transmission time required for the first beam group in the first transmission cycle is the time corresponding to N1 repeated transmission cycles. That is, in the first transmission cycle, the first beam group is transmitted through the time domain resource that only transmits the first beam group, and is not repeatedly transmitted on other time domain resources, which can further reduce the time domain resource overhead of transmitting RMSI. Furthermore, the first beam group transmitted by adjacent repetitions can also reduce the degree of damage to the RMSI combining gain.

[0022] In a possible implementation, the time domain resources corresponding to the first transmission period also include: within the time domain resources corresponding to the repeated transmission period, time domain resources for transmitting the second beam group among the multiple beams, and not transmitting other beams among the multiple beams except the second beam group, and the beams included in the second beam group are different from the beams included in the first beam group. In other words, on the basis of only sending the first beam group, the proportion of time domain resource overhead for transmitting RMSI can be further reduced by not sending other beams except the second beam group.

[0023] It should be understood that, for the sake of convenience, the above-mentioned "within the time domain resources corresponding to the repeated transmission period, the time domain resources for transmitting the second beam group among the multiple beams, and not transmitting other beams among the multiple beams except the second beam group" is replaced by "only the time domain resources for sending the second beam group".

[0024] In a possible implementation, the number of beams included in the second beam group may be K. Taking the case where the multiple beams are M beams and the number of beams included in the first beam group is Y as an example, the value range of K is: [1, MY]. Furthermore, when K is greater than 1, the K beams are adjacent to each other or spaced apart, and the embodiment of the present application does not specifically limit this. It can be understood that the above K may be the same as or different from Y. Taking M=16 as an example, Y may be equal to 4, and K may be equal to any value from 1 to 12. For example, taking the case where M beams include SSB beam #1 to SSB beam #16, and the first beam group is: SSB beam #1, SSB beam #2, and SSB beams #14 to #16 as an example, the second beam group may be: any 1, 2, 3, or 12 of SSB beam #3 to SSB beam #13, etc. Furthermore, taking the second beam group including SSB beam #3 to SSB beam #13 as an example, within the time domain resources corresponding to the first sending cycle, within one repeated transmission cycle of 20ms, the time domain resource overhead for transmitting RMSI is reduced from the original 16 time slots to 11 time slots, thereby reducing the proportion of time domain resource overhead for transmitting RMSI.

[0025] In a possible implementation, in the time domain resources corresponding to the repeated transmission period, the time domain resources for transmitting the second beam group among the multiple beams, and not transmitting the time domain resources of other beams except the second beam group among the multiple beams, include: in the time domain resources corresponding to each repeated transmission period among the time domain resources corresponding to N2 repeated transmission periods, the time domain resources for transmitting the second beam, and not transmitting the time domain resources of other beams except the second beam group among the multiple beams, where N2 is an integer greater than 1. That is to say, in the time domain resources corresponding to the first transmission period, the second beam group may also be repeatedly transmitted, thereby reducing the degree of damage to the RMSI combining gain for the terminal devices within the coverage of the second beam group.

[0026] It can be understood that the time domain resources for sending only the second beam group are similar to the time domain resources for sending only the first beam group. For example, the number of time domain resources for sending only the second beam group may be N2; for another example, the time domain resources corresponding to the N2 repeated transmission periods may be located at any time domain position within the first transmission period; for another example, the time domain resources corresponding to each of the N2 repeated transmission periods may be intermittent, adjacent, or partially adjacent.

[0027] In a possible implementation, N1 and N2 may be different. The time domain resources for sending only the first beam group and the time domain resources for sending only the second beam group may be arranged alternately first or alternately later. For example, taking N1=3 and N2=5 as an example, 3 time domain resources for sending only the first beam group and 3 time domain resources for sending only the second beam group may be arranged alternately first, and then the remaining 2 time domain resources for sending only the second beam group may be arranged. It can be understood that the time domain resources for sending only the first beam group and the time domain resources for sending only the second beam group may also be arranged in other ways.

[0028] In one possible implementation, the first beam group is periodically transmitted in the first transmission cycle. The transmission period of the first beam group in the first transmission cycle may be a repeated transmission period. That is to say, for the terminal equipment within the coverage of the first beam group, it can continuously receive N1 RMSIs for RMSI merging, thereby reducing the degree of damage to the RMSI merging gain. It can be understood that the second beam group may also be periodically transmitted in the first transmission cycle, and the transmission period of the second beam group in the first transmission cycle may also be a repeated transmission period, so that for the terminal equipment within the coverage of the second beam group, the degree of damage to the RMSI merging gain can be reduced.

[0029] It can be understood that when the number of beams between the first beam group and the second beam group is less than the number of multiple beams that need to be traversed, the network device can also send a third beam group, or a third beam group and a fourth beam group, etc. Among them, the third beam group may include other beams in the multiple beams except the first beam group and the second beam group. The fourth beam group may include other beams in the multiple beams except the first beam group to the third beam group. Furthermore, the number of transmissions of each beam group in the first beam group to the fourth beam group in the first transmission cycle may be the same or different.

[0030] In a second aspect, a communication device is provided for implementing the above-mentioned various methods. The communication device may be a network device in the above-mentioned first aspect or any implementation thereof, or a device including the above-mentioned network device, or a device included in the above-mentioned network device, such as a core. The communication device includes a module, unit, or means corresponding to the above-mentioned method, and the module, unit, or means may be implemented by hardware, software, or by executing the corresponding software implementation by hardware. The hardware or software includes one or more modules or units corresponding to the above-mentioned functions.

[0031] In some possible designs, the communication device may include a processing module and a transceiver module. The transceiver module, which may also be referred to as a transceiver unit, is used to implement the sending and / or receiving functions in the first aspect and any possible implementation thereof. The transceiver module may be composed of a transceiver circuit, a transceiver, a transceiver or a communication interface. The processing module may be used to implement the processing functions in the first aspect and any possible implementation thereof.

[0032] In some possible designs, the transceiver module includes a sending module and a receiving module, which are respectively used to implement the sending and receiving functions in the above-mentioned first aspect and any possible implementation methods thereof.

[0033] In a third aspect, a communication device is provided, comprising: a processor and a memory; the memory is used to store computer instructions, and when the processor executes the instructions, the communication device executes the method described in the first aspect. The communication device can be the network device in the first aspect or any implementation thereof, or a device including the network device, or a device included in the network device, such as a chip.

[0034] In a fourth aspect, a communication device is provided, comprising: a processor and a communication interface; the communication interface is used to communicate with a module outside the communication device; the processor is used to execute a computer program or instruction so that the communication device executes the method described in the first aspect. The communication device can be the network device in the first aspect or any implementation thereof, or a device including the network device, or a device included in the network device, such as a chip.

[0035] In a fifth aspect, a communication device is provided, comprising: at least one processor; the processor is used to execute a computer program or instruction stored in a memory, so that the communication device performs the method described in the first aspect above. The memory may be coupled to the processor, or may be independent of the processor. The communication device may be a network device in the first aspect or any implementation thereof, or a device including the network device, or a device included in the network device, such as a chip.

[0036] In a sixth aspect, a computer-readable storage medium is provided, in which a computer program or instruction is stored. When the computer-readable storage medium is run on a communication device, the communication device can execute the method described in the first aspect or any one of its implementation methods.

[0037] In a seventh aspect, a computer program product comprising instructions is provided, which, when executed on a communication device, enables the communication device to execute the method described in the first aspect or any one of its implementations.

[0038] In an eighth aspect, a communication device (for example, the communication device may be a chip or a chip system) is provided, wherein the communication device includes a processor for implementing the functions involved in the above-mentioned first aspect or any implementation method thereof.

[0039] In some possible designs, the communication device includes a memory for storing necessary program instructions and data.

[0040] In some possible designs, when the device is a chip system, it can be composed of a chip or include a chip and other discrete devices.

[0041] It can be understood that when the communication device provided in any one of the second aspect to the eighth aspect is a chip, the above-mentioned sending action / function can be understood as output, and the above-mentioned receiving action / function can be understood as input.

[0042] Among them, the technical effects brought about by any design method in the second to eighth aspects can refer to the technical effects brought about by different design methods in the above-mentioned first aspect, and will not be repeated here.

[0043] In a ninth aspect, a communication system is provided, which includes the network device described in the above aspects.

[0044] In some possible designs, the communication system also includes the terminal device described in the above aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] Figure 1 This is a schematic diagram of RMSI transmission provided in an embodiment of the present application;

[0046] Figure 2 It is a structural diagram of a communication system provided in an embodiment of the present application;

[0047] Figure 3 is a structural diagram of a communication device provided in an embodiment of the present application;

[0048] Figure 4 This is a flowchart of a method for sending system information provided by an embodiment of the present application;

[0049] Figure 5 It is a schematic diagram of an RMSI transmitted through 16 SSB beams within 160ms provided by an embodiment of the present application;

[0050] Figure 6 is a schematic diagram of another RMSI transmitted through 16 SSB beams within 160ms provided by an embodiment of the present application;

[0051] Figure 7 It is a structural diagram of a network device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0052] To facilitate understanding of the technical solutions provided by the embodiments of the present application, a brief introduction to the relevant technologies of the embodiments of the present application is first given. The brief introduction is as follows:

[0053] First, the time and frequency resources of the new radio (NR) system:

[0054] Time-frequency resources include time domain resources and frequency domain resources. Among them, the time domain resources and frequency domain resources of the NR system are related to the transmission scheme of the NR system. The uplink (UL) transmission scheme and the downlink (DL) transmission scheme of the NR system can use orthogonal frequency division multiplexing (OFDM) technology. The principle of OFDM is: divide multiple subchannels in the frequency domain, convert the data to be transmitted into serial and parallel, and obtain multiple groups of data for parallel transmission, and then modulate each group of data to the subcarrier corresponding to each subchannel for transmission, that is, the data to be transmitted can be transmitted through multiple subcarriers superimposed in space. In other words, the minimum frequency domain resource in the NR system is 1 subcarrier, and the minimum time domain resource is 1 OFDM symbol.

[0055] It can be understood that the specific configuration of OFDM is related to the subcarrier spacing (SCS) configuration. Table 1 shows the SCS supported by the NR system. In Table 1, the first column is the SCS configuration μ, and the second column Δf represents the SCS.

[0056] Table 1

[0057]

[0058]

[0059] The following introduces the time domain resources and frequency domain resources in the NR system in combination with SCS.

[0060] 1.1. Time domain resources:

[0061] In the time domain, the NR system can be transmitted in units of radio frames. The duration of each radio frame is T f = 10ms. Each wireless frame can be composed of 10 frames with a duration of T sf=1ms subframe. The 10 subframes in a wireless frame can be arranged in sequence. For example, the 10 subframes in a wireless frame can be arranged in ascending order in chronological order as: subframe #0 to subframe #9. For another example, the 10 subframes can be arranged in descending order in chronological order, that is, subframe #9 to subframe #0. The embodiment of the present application does not specifically limit the subframe sorting method.

[0062] It can be understood that a wireless frame can also be divided into two half-frames of the same size, namely half-frame #0 and half-frame #1. Each half-frame includes five sub-frames. For example, half-frame #0 can be composed of sub-frames #0 to sub-frame #4, and half-frame #1 can be composed of sub-frames #5 to sub-frame #9.

[0063] It should be understood that the above numbering and sequence of half frames and subframes are only exemplary. For example, the starting number may also be #1. For example, 10 subframes in a wireless frame may be represented as: subframe #1 to subframe #10.

[0064] Furthermore, in the NR system, a subframe may include several time slots. For the subcarrier spacing configuration μ, the time slots may be numbered in ascending order within a subframe. Arrangement, and can be numbered in ascending order within a wireless frame In a time slot there are consecutive OFDM symbols, It is related to the cyclic prefix (CP) used by OFDM symbols. CP can be divided into normal CP and extended CP. Normal CP corresponds to See Table 2 for the extended CP corresponding Please refer to Table 3.

[0065] It should be understood that the time slot in a subframe The time domain starting position of the OFDM symbol in the same subframe For example, when a time slot includes 14 OFDM symbols, the OFDM symbols can be arranged in chronological order as: OFDM symbol #0 to OFDM symbol #13, wherein the time domain starting position of OFDM symbol #0 is the same as the time domain starting position of the time slot.

[0066] Table 2

[0067]

[0068] Table 3

[0069]

[0070] Furthermore, since the transmission of the NR system can be divided into uplink transmission and downlink transmission, a time slot may be used for uplink transmission or downlink transmission. Among them, the network can be configured in a downlink-uplink transmission periodicity (DL-ULtransmission periodicity) to determine the ratio between the uplink time slot used for uplink transmission and the downlink time slot used for downlink transmission. For example, the downlink-uplink transmission periodicity may be 0.5ms, 0.625ms, 1.25ms, or 2.5ms, etc., and the ratio between the uplink time slot and the downlink time slot may be 1:4, 3:7, or 1:3, etc., which is not specifically limited in the embodiments of the present application.

[0071] For example, for SCS configuration μ=3, that is, SCS=120kHz, as shown in Table 2, one subframe (1ms) may include 8 time slots, and one radio frame (10ms) may include 80 time slots. Among them, taking the ratio between uplink time slots and downlink time slots as 1:4 as an example, 80 time slots in one radio frame may be divided into 16 uplink time slots and 64 downlink time slots.

[0072] It should be understood that the downlink-uplink transmission period, and the ratio between the uplink time slot and the downlink time slot, can be specifically referred to in TS 38.213, and will not be repeated here.

[0073] 1.2. Frequency domain resources:

[0074] In the NR system, a subcarrier in the frequency domain and an OFDM symbol in the time domain can be defined as a resource element (RE), where RE is the smallest granularity resource in the physical layer.

[0075] Furthermore, in the frequency domain, regardless of the subcarrier spacing, the NR system can define 12 consecutive subcarriers as a resource block (RB).

[0076] Second, SSB:

[0077] SSB may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS) and a physical broadcast channel (PBCH). Among them, the terminal device must first detect the PSS and SSS to obtain downlink time-frequency synchronization, as well as the physical cell identifier (PCID), and then decode the PBCH. The PBCH includes the MIB and other information related to the SSB transmission time. The MIB contains the configuration parameters required to obtain the RMSI. The terminal device can blindly detect the physical downlink control channel (PDCCH) according to the configuration parameters, and then obtain the downlink control information (DCI). The DCI can be used to indicate the time-frequency resources of the physical downlink shared channel (PDSCH) carrying the RMSI, so that the terminal device can receive the RMSI according to the time-frequency resources and complete the initial access according to the RMSI. The specific process of the above-mentioned terminal device obtaining the RMSI can be found in the relevant description of TS 38.213, which will not be repeated here.

[0078] Furthermore, due to the large propagation loss of high-frequency carriers, beamforming is required to increase the coverage distance of wireless signals. Among them, since each beam has a limited coverage angle, that is, the beam width is narrow, terminal devices outside the beam coverage range cannot reliably receive wireless signals from network devices. However, SSB is a broadcast signal (or broadcast channel), which requires that all terminal devices in the cell can receive it. A beam with a limited coverage angle cannot actually meet the needs of full coverage of the cell, and network devices are required to transmit SSB through beam scanning.

[0079] Furthermore, transmitting SSB by beam scanning may mean transmitting SSB in beams in different directions at different times to cover the entire cell. Among them, the beam transmitting SSB may be called an SSB beam, and different SSB beams have different directions, that is, different SSB beams have different coverage ranges. The multiple SSBs required to complete a beam scan constitute an SSB burst set, and the maximum number of SSBs contained in an SSB burst set may be 4, 8, 16, or 64. Among them, the SSB burst set needs to complete the transmission within 5ms of a half frame, and the transmission period of the SSB burst set may be {5, 10, 20, 40, 80, 160} ms.

[0080] Third, RMSI:

[0081] RMSI may also be referred to as system information block type 1 (SIB1). RMSI may include a public land mobile network (PLMN) ID, a cell global ID, a cell barring status, a cell selection parameter, or other system information, etc. For details, please refer to the relevant description of TS 38.331, which will not be repeated here.

[0082] It can be understood that, as described in the aforementioned “Second, SSB”, different SSB beams have different coverage and transmission times, and the terminal device needs to determine the time and frequency resources for receiving RMSI based on the received SSB. In order to enable terminal devices located at different locations in the cell to receive RMSI, the network device needs to send RMSI through each SSB beam in multiple SSB beams, so that the terminal device can access the network device.

[0083] Furthermore, the transmission period of RMSI can be 160ms, and the same information can be repeatedly transmitted within 160ms, that is, RMSI is periodically transmitted through each beam in multiple SSB beams within 160ms. Among them, the network device can send RMSI after sending the SSB burst set, or the network device can reuse the time-frequency resources corresponding to each SSB in the SSB burst set to send RMSI. For details, please refer to the relevant description in TS 38.213, which will not be repeated here.

[0084] It should be understood that the default repetition transmission period for transmitting RMSI through each SSB beam in multiple SSB beams is 20ms, but the actual repetition transmission period can be set by the network, for example, by the network equipment, or by the core network (CN).

[0085] Furthermore, within the above-mentioned repeated transmission period, the time domain resources in each SSB beam used to transmit multiple SSB beams are determined according to the SSB corresponding to the SSB beam. For example, the time domain resources used to transmit an SSB beam are different from the time domain resources for transmitting the SSB corresponding to the SSB beam, and the time interval between the two can be determined according to the MIB in the SSB corresponding to the SSB beam. For another example, the time domain resources used to transmit an SSB beam can reuse the time domain resources for transmitting the SSB corresponding to the SSB beam. It can be understood that the above-mentioned time domain resources used to transmit an SSB beam can refer to the relevant description of TS 38.213 for details, which will not be repeated here.

[0086] Combine the following Figure 1 The transmission of RMSI is illustrated by way of example.

[0087] Figure 1 FIG. 1 is a schematic diagram of RMSI transmission provided in an embodiment of the present application. Figure 1 As shown, the transmission period of the SSB burst set is 20ms, and the SSB burst set completes the transmission within one half frame of 5ms. 16 SSBs are transmitted in the SSB burst set, namely SSB#1 to SSB#16, and the SSB beams of the 16 SSBs are SSB beam#1 to SSB beam#16 (i.e., the SSB beam of SSB#1 is SSB beam#1, the SSB beam of SSB#2 is SSB beam#2, ..., the SSB beam of SSB#16 is SSB beam#16), and thus RMSI needs to be transmitted through each SSB beam in SSB beam#1 to SSB beam#16, i.e., RMSI is transmitted through SSB beam#1, RMSI is transmitted through SSB beam#2, ..., RMSI is transmitted through SSB beam#16.

[0088] Furthermore, the transmission period of RMSI is 160ms, and the RMSI transmitted through SSB beam #1 to SSB beam #16 can be repeatedly transmitted within 160ms. Figure 1 As shown, the repetitive transmission period is 20ms, that is, within the RMSI transmission period (160ms), the RMSI transmitted through SSB beam #1 to SSB beam #16 can be transmitted a total of 8 times.

[0089] Further, in the repeated transmission period, the time domain resource for transmitting RMSI may be after the time domain resource for transmitting the SSB burst set. Among the time domain resources for transmitting RMSI, the time domain resource for transmitting each SSB beam in SSB beam #1 to SSB beam #16 may be 1 time slot.

[0090] However, when there are many SSB beams for transmitting RMSI, the time domain resource overhead for transmitting RMSI accounts for a large proportion in the time domain resources corresponding to the repeated transmission period. For example, taking the 80 time slots in a radio frame in the aforementioned "1.1, time domain resources" as an example, including 64 downlink time slots, the time domain resources corresponding to the 20ms repeated transmission period include 128 downlink time slots. Figure 1 In the example, the time domain resource overhead for transmitting RMSI through 16 SSB beams requires 16 time slots, and the time domain resource overhead for transmitting RMSI accounts for 12.5%. Therefore, the time domain resource overhead for transmitting RMSI accounts for a large proportion.

[0091] It is understandable that the time domain resources for transmitting RMSI are difficult to use for downlink data transmission. For example, in the frequency range (FR) 2 (such as the millimeter wave band) scenario, in order to compensate for the transmission loss of high-frequency signals, it is necessary to concentrate the limited energy in a narrower beam width, that is, the SSB beam used in the time domain resources for transmitting RMSI can only cover a limited number of terminal devices, and cannot be used for downlink data scheduling of other terminal devices outside the coverage range of the SSB beam, which will limit downlink data transmission. Furthermore, according to Chapter 5 of TS 38.214 (h20 version), regarding the relevant instructions on PDSCH scheduling restrictions, for the same cell operating in FR2, in the process of obtaining system information triggered by paging-radio network temporary identifier (P-RNTI), if there is a PDSCH that partially or completely overlaps in time with the PDSCH scheduled using the system information-radio network temporary identifier (SI-RNTI), the terminal device does not expect to simultaneously decode the PDSCH scheduled using the cell-radio network temporary identifier (cell RNTI, C-RNTI), modulation and coding scheme-cell-radio network temporary identifier (modulation and coding scheme-cell-RNTI, MCS-RNTI), or configured scheduling-radio network temporary identifier (configured scheduling RNTI, CS-RNTI), that is, in the FR2 scenario, in the same cell, the terminal device does not expect to demodulate RMSI and downlink data at the same time.

[0092] In summary, the time domain resources for transmitting RMSI are difficult to be used for downlink data transmission. In other words, when the time domain resource overhead for transmitting RMSI accounts for a large proportion, the time domain resources for downlink data transmission account for a small proportion, affecting the downlink data transmission rate.

[0093] Furthermore, when the network device is unloaded or lightly loaded, the time domain resource overhead of transmitting RMSI accounts for a large proportion, which will lead to high power consumption of the network device and is not conducive to energy saving of the network device.

[0094] It should be understood that by lengthening the repetitive transmission period of RMSI, the time domain resource overhead ratio of RMSI transmission can be reduced. However, for a terminal device that receives RMSI multiple times for RMSI merging, lengthening the repetitive transmission period of RMSI will result in a loss of RMSI merging gain. Figure 1In the example, the RMSI repetition transmission period is 20ms, that is, within 160ms, the RMSI transmitted through SSB beam #1 to SSB beam #16 can be transmitted a total of 8 times, and the terminal device can perform RMSI merging through the RMSI received 3 times within 80ms; or, the terminal device can perform RSMI merging through the RMSI received 4 times within 100ms. If the RMSI repetition transmission period is extended to 80ms, then within 160ms, the RMSI transmitted through SSB beam #1 to SSB beam #16 is transmitted twice, and then the terminal device only receives 1 RMSI within 80ms, and RMSI merging cannot be performed; or, the terminal device performs RMSI merging through the 2 RMSI received within 160ms. In other words, by lengthening the RMSI repetition transmission period, the number of RMSIs received by the terminal device within a given time is reduced, which will result in a loss of RMSI merging gain. Furthermore, in scenarios where coverage performance is limited, the RMSI merging gain is impaired, resulting in a decrease in RMSI coverage performance.

[0095] Based on this, an embodiment of the present application provides a system information sending method, which can reduce the proportion of time domain resource overhead for transmitting RMSI.

[0096] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0097] In order to facilitate understanding of the embodiments of the present application, the following points are explained before introducing the embodiments of the present application.

[0098] 1. In the embodiments of the present application, for the convenience of description, when numbering or indexing is involved, the numbering can be started from 1 or from 0, or from any parameter.

[0099] 2. "Pre-definition", "pre-configuration", or "protocol agreement" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (e.g., a network device). The embodiments of this application do not limit the specific implementation methods. Among them, "saving" can mean saving in one or more memories.

[0100] 3. The “protocol” involved in the embodiments of the present application may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, which is not limited in the embodiments of the present application.

[0101] 4. In the embodiments of the present application, descriptions such as “when…”, “in the case of…”, “if” and “if” all mean that under certain objective circumstances, the device (such as the first device or the second device) will make corresponding processing. It does not limit the time, nor does it require the device to have a judgment action when implementing it, nor does it mean that there are other limitations.

[0102] 5. In the embodiments of the present application, “sending information to...(terminal device)” can be understood as the destination of the information being the terminal device, and can include directly or indirectly sending information to the terminal device. “Receiving information from...(network device)” or “receiving information from...(network device)” can be understood as the source of the information being the network device, and can include directly or indirectly receiving information from the network device. The information may be processed as necessary between the source and destination of the information transmission, such as format changes, etc., but the destination can understand the valid information from the source. Similar expressions in the present application can be understood similarly and will not be repeated here.

[0103] 6. In the description of the embodiments of the present application, unless otherwise specified, the "and / or" in the embodiments of the present application indicates that there may be three relationships, for example, A and / or B, which may indicate: A exists alone, A and B exist at the same time, and B exists alone, wherein A and B may be singular or plural. Moreover, "at least one of the following" or similar expressions refers to any combination of these items, including any combination of single items or plural items. In addition, in order to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first", "second" and the like are used to distinguish the same items or similar items with substantially the same functions and effects. Those skilled in the art may understand that the words "first", "second" and the like do not limit the quantity and execution order, and the words "first", "second" and the like do not limit the certain difference. At the same time, in the embodiments of the present application, the words "exemplary" or "for example" are used to indicate examples, illustrations or explanations.

[0104] The embodiments of the present application may be applicable to LTE systems or NR systems (also referred to as fifth generation (5th generation, 5G) systems), systems with hybrid LTE and NR networking, vehicle to everything (V2X) systems, device-to-device (D2D) systems, machine to machine (M2M) communication systems, Internet of Things (IoT) systems (such as narrowband Internet of Things (NB-IoT) systems), 6G systems, and other next generation communication systems. Alternatively, the communication system may also be an open radio access network (O-RAN or ORAN) or a cloud radio access network (cloudRAN, CRAN), without limitation.

[0105] In addition, the communication architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of the communication architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0106] like Figure 2 , which is a schematic diagram of the structure of a communication system 200 provided in an embodiment of the present application. Figure 2 The communication system 200 includes at least one network device (eg Figure 2 210a or 210b), and at least one terminal device (eg Figure 2 It is understood that the network device can be connected to the CN wirelessly or wired, and the CN device and the network device in the CN can be different physical devices, or the same physical device that integrates the CN logical function and the wireless access network logical function. It is understood that Figure 2 The number of network devices and terminal devices is only an example, and can be more or less, and the embodiments of the present application do not specifically limit this.

[0107] In a possible implementation, the network device determines the first transmission period and the time domain resources corresponding to the first transmission period according to the repeated transmission period of the RMSI, and sends the RMSI to the terminal device according to the first transmission period and the time domain resources corresponding to the first transmission period. The repeated transmission period is a repeated transmission period for transmitting the RMSI through each beam in a plurality of beams. The time domain resources corresponding to the first transmission period include: within the time domain resources corresponding to the repeated transmission period, the time domain resources for transmitting the first beam group in a plurality of beams, and not transmitting the other beams in the plurality of beams except the first beam group, and the first beam group is repeatedly transmitted in the first transmission period.

[0108] The specific implementation of the above solution will be described in detail in the following embodiments and will not be repeated here.

[0109] Since in the embodiment of the present application, the network device sends RMSI through the time domain resources corresponding to the first sending period, and thus the network device can send RMSI only through the first beam group within the time domain resources corresponding to the repeated transmission period, without sending RMSI through each beam, thereby reducing the proportion of time domain resource overhead for transmitting RMSI within the time domain resources corresponding to the repeated transmission period. Furthermore, the first beam group is repeatedly transmitted within the first sending period, thereby reducing the degree of damage to the RMSI combining gain. Therefore, based on the system information sending method provided in the embodiment of the present application, the degree of damage to the RMSI combining gain can be reduced while reducing the proportion of time domain resource overhead for transmitting RMSI.

[0110] In a possible implementation, the network device in the embodiment of the present application may be a device that communicates with a terminal device. The network device may also be referred to as an access network (RAN) device, an access node, a RAN entity, or a RAN node. Figure 2 As shown, the multiple network devices in the communication system 200 can be nodes of the same type or nodes of different types. In some scenarios, the roles of network devices and terminal devices are relative, for example Figure 2 The network element 220i in the figure can be a helicopter or a drone, which can be configured as a mobile base station. For the terminal devices 220j that access the communication system 200 through the network element 220i, the network element 220i can be the base station 210a; but for the base station 210a, the network element 220i is a terminal device. Network devices and terminal devices are sometimes referred to as communication devices, for example Figure 2 The network elements 210a and 210b may be understood as communication devices having base station functions, and the network elements 220a-220j may be understood as communication devices having terminal functions.

[0111] In one possible scenario, the network device may be a transmission and reception point (TRP), a base station, a remote radio unit (RRU) or a baseband unit (BBU) (also called a digital unit (DU)) of a split base station, a broadband network gateway (BNG), an aggregation switch, a non-3GPP access device, a relay station or an access point. The network device may be a macro base station (e.g. Figure 2 network element 110a in the network), micro base station or indoor station (such as Figure 2 The network device may be a network element 110b in the V2X system, a relay node or a donor node, or a wireless controller in a CRAN scenario. Optionally, the network device may also be a server, a wearable device, a vehicle or an on-board device, etc. For example, the network device in the V2X system may be a road side unit (RSU). In addition, the network device in the embodiment of the present application may be an eNB or eNodeB (evolutionalNodeB) in LTE, a wireless controller in a CRAN scenario, a base station in a 5G communication system (e.g., a next-generation node B (gNodeB, gNB)), or a base station in a future evolution system (e.g., a 6G communication system), etc., which is not specifically limited here.

[0112] In one possible implementation, in some deployments, the gNB may include a centralized unit (CU), a DU, a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The gNB may also include an active antenna unit (AAU). The CU implements some functions of the gNB, and the DU implements some functions of the gNB, for example, the CU is responsible for processing non-real-time protocols and services, and implementing the functions of the RRC and / or PDCP layers. The DU is responsible for processing physical layer protocols and real-time services, and implementing the functions of the RLC layer, the MAC layer, and the PHY layer. The AAU implements some physical layer processing functions, radio frequency processing, and related functions of active antennas. Since the information of the RRC layer will eventually become the information of the PHY layer, or be converted from the information of the PHY layer, under this architecture, high-level signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or by the DU+AAU. It can be understood that the network device can be a device including one or more of a CU node, a DU node, and an AAU node. In addition, the CU may be divided into a network device in the RAN, or may be divided into a network device in the CN, which is not limited in the embodiments of the present application.

[0113] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called O-CU (open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, the embodiments of the present application are described by taking CU, CU-CP, CU-UP, DU and RU as examples. Any unit of CU (or CU-CP, CU-UP), DU and RU in the embodiments of the present application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0114] In a possible implementation, the terminal device in the embodiment of the present application may be a device for implementing a wireless communication function, such as a terminal or a chip that can be used in a terminal, etc. The terminal may be a user equipment (UE), an access terminal, a terminal unit, a terminal station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a terminal agent or a terminal device, etc. in a 5G network or a future evolved public land mobile network (PLMN). The access terminal may be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a VR terminal device, an AR terminal device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. In a possible implementation, the terminal device may be mobile or fixed.

[0115] In a possible implementation, the network device and terminal device in the embodiment of the present application may also be referred to as a communication device, which may be a general device or a dedicated device, and the embodiment of the present application does not specifically limit this.

[0116] In a possible implementation, the relevant functions of the terminal device or network device in the embodiment of the present application can be implemented by one device, or by multiple devices together, or by one or more functional modules in one device, and the embodiment of the present application does not specifically limit this. It is understandable that the above functions can be network elements in hardware devices, or software functions running on dedicated hardware, or a combination of hardware and software, or virtualization functions instantiated on a platform (e.g., a cloud platform).

[0117] For example, the relevant functions of the network device or terminal device in the embodiment of the present application can be Figure 3 The communication device 300 is used to implement the above. Figure 3FIG. 3 is a schematic diagram of the structure of a communication device 300 provided in an embodiment of the present application. The communication device 300 includes one or more processors 301, a communication line 302, and at least one communication interface ( Figure 3 The communication device 300 is merely illustrative and is described by taking the communication interface 304 and a processor 301 as an example. Optionally, the communication device 300 may further include a memory 303.

[0118] The processor 301 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.

[0119] The communication line 302 may include a path for connecting different components.

[0120] The communication interface 304 may be a transceiver module for communicating with other devices or communication networks, such as Ethernet, RAN, wireless local area networks (WLAN), etc. For example, the transceiver module may be a device such as a transceiver or a transceiver. In a possible implementation, the communication interface 304 may also be a transceiver circuit located in the processor 301 to implement signal input and signal output of the processor.

[0121] The memory 303 may be a device with a storage function. For example, it may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory may exist independently and be connected to the processor via a communication line 302. The memory may also be integrated with the processor.

[0122] The memory 303 is used to store computer-executable instructions for executing the solution of the present application, and the execution is controlled by the processor 301. The processor 301 is used to execute the computer-executable instructions stored in the memory 303, thereby realizing the signal transmission method provided in the embodiment of the present application.

[0123] Alternatively, in an embodiment of the present application, the processor 301 may also perform functions related to the processing of the signal transmission method provided in the following embodiments of the present application, and the communication interface 304 is responsible for communicating with other devices or communication networks, which is not specifically limited in the embodiment of the present application.

[0124] In a possible implementation, the memory 303 in the embodiment of the present application can also be used to store the information or parameters described in the following embodiments, such as RMSI, the repeated transmission period of RMSI, the first sending period, or the time domain resources corresponding to the first sending period.

[0125] The computer-executable instructions in the embodiments of the present application may also be referred to as application program codes, which is not specifically limited in the embodiments of the present application.

[0126] In a specific implementation, as an embodiment, the processor 301 may include one or more CPUs, such as Figure 3 CPU0 and CPU1 in.

[0127] In a specific implementation, as an embodiment, the communication device 300 may include multiple processors, such as Figure 3 301 and processor 307 in the embodiment of the present invention. Each of these processors may be a single-CPU processor or a multi-CPU processor. The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0128] In a specific implementation, as an embodiment, the communication apparatus 300 may further include an output device 305 and an input device 306. The output device 305 communicates with the processor 301 and may display information in a variety of ways.

[0129] The communication device 300 can be a general device or a dedicated device. For example, the communication device 300 can be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, or a computer with Figure 3 The embodiment of the present application does not limit the type of the communication device 300.

[0130] The following will be combined Figure 4, the system information sending method provided in the embodiment of the present application is described in detail.

[0131] It should be understood that the signal names between the various devices or the names of the various parameters in the signals in the following embodiments of the present application are merely examples, and other names may be used in specific implementations, and the embodiments of the present application do not specifically limit this.

[0132] by Figure 2 As an example, the interaction between the network device and the terminal device shown in FIG. Figure 4 As shown, a system information sending method provided in an embodiment of the present application includes the following steps:

[0133] S401. The network device determines the first transmission period and the time domain resources corresponding to the first transmission period according to the repeated transmission period of RMSI. The repeated transmission period is the repeated transmission period for transmitting RMSI through each beam in a plurality of beams. The time domain resources corresponding to the first transmission period include: within the time domain resources corresponding to the repeated transmission period, the time domain resources for transmitting the first beam group in a plurality of beams, and not transmitting the time domain resources of other beams in the plurality of beams except the first beam group. The first beam group is repeatedly transmitted in the first transmission period.

[0134] S402: The network device sends the RMSI to the terminal device according to the first sending period and the time domain resources corresponding to the first sending period. Correspondingly, the terminal device receives the RMSI from the network device.

[0135] The above steps S401 to S402 are described in detail below.

[0136] For step S401:

[0137] In a possible implementation, each beam in the plurality of beams corresponds to an SSB. For example, each beam in the plurality of beams may be an SSB beam corresponding to each SSB in a plurality of SSBs, and the plurality of SSBs may be a plurality of SSBs in an SSB burst set. For details, see Figure 1 SSB beam #1 to SSB beam #16 that transmit RMSI during the repeated transmission period will not be repeated here.

[0138] It can be understood that the number of the multiple beams is related to the number of SSBs transmitted in the SSB burst set. For example, if 4 SSBs are transmitted in the SSB burst set, the number of the multiple beams is 4. For another example, if 64 beams are transmitted in the SSB burst set, the number of the multiple beams is 64.

[0139] Furthermore, each of the multiple beams may also be a beam with a coverage range close to that of its corresponding SSB beam, and the embodiments of the present application do not specifically limit this.

[0140] In one possible implementation, the time domain resource used to transmit each of the multiple beams is determined according to the SSB corresponding to each of the multiple beams.

[0141] Among them, the specific method for determining the time domain resources of each of the above beams can be found in the relevant instructions in the aforementioned "Third, RMSI", which will not be repeated here.

[0142] In a possible implementation, the repetitive transmission period in step S401 may refer to the repetitive transmission period in the aforementioned “RMSI”. For details, please refer to the relevant instructions, which will not be repeated here.

[0143] Further, the repetitive transmission period in the embodiment of the present application may be a multiple of 20ms, such as 20ms, 40ms, 60ms, 80ms, or 160ms, etc. It should be understood that the repetitive transmission period may not be a multiple of 20ms, such as 21ms, 22ms, 30ms, 31ms, 39ms, 41ms, 49ms, or 50ms, etc., and the embodiment of the present application does not specifically limit this.

[0144] The first sending period and the time domain resources corresponding to the first sending period are introduced below.

[0145] It should be understood that the first transmission period may refer to the transmission period in which the network device transmits RMSI. In the first transmission period, each of the above-mentioned multiple beams is transmitted at least once. In other words, some of the multiple beams can be transmitted repeatedly, and then the terminal device within the coverage of the partial beam can receive RMSI multiple times, thereby obtaining RMSI merging gain.

[0146] In a possible implementation, the first transmission period may be an integer multiple of the repetitive transmission period. For example, the first transmission period may be 2 times, 3 times, 4 times, or more times of the repetitive transmission period. Further, the first transmission period may be 160 ms, or the first transmission period may be greater than 160 ms, which is not specifically limited in the embodiments of the present application.

[0147] In a possible implementation, within the time domain resources corresponding to the first transmission cycle, the time domain resources used to transmit each of the multiple beams belong to the time domain resources corresponding to each of the multiple beams within the repeated transmission cycle. For example, taking the first transmission cycle as twice the repeated transmission cycle, and 16 beams (i.e., beam #1 to beam #16) are transmitted within the repeated transmission cycle, the time domain resources corresponding to the first transmission cycle include the time domain resource #1 corresponding to the first repeated transmission cycle, and the time domain resource #2 corresponding to the second repeated transmission cycle. Among them, within the first transmission cycle, the time slot used to transmit beam #1 can be the time slot for transmitting beam #1 within time domain resource #1, and the time slot used to transmit beam #16 can be the time slot for transmitting beam #1 within time domain resource #16.

[0148] That is to say, within the time domain resources corresponding to the first sending period, the time domain resources corresponding to each beam in the multiple beams in the repeated transmission period can be multiplexed.

[0149] Furthermore, the time domain resources corresponding to the first sending period may include time domain resources for sending only the first beam, that is, in step S401: within the time domain resources corresponding to the repeated transmission period, the time domain resources are used to transmit the first beam group among multiple beams, and the time domain resources other than the first beam group among the multiple beams are not transmitted.

[0150] That is to say, within the time domain resources corresponding to the repeated transmission period, the proportion of time domain resource overhead for transmitting RMSI can be reduced by not sending beams other than the first beam group.

[0151] In a possible implementation, the first beam group may include any Y beams from the plurality of beams. Taking the plurality of beams as M beams as an example, the value range of Y is: [1, M). Furthermore, when Y is greater than 1, the Y beams may be adjacent to each other or spaced apart, and this embodiment of the present application does not specifically limit this.

[0152] Further, as described in step 401, the first beam group is repeatedly transmitted in the first transmission period. The number of times the first beam group is repeatedly transmitted may be 1, 2, 3, or more times, which is not specifically limited in the embodiment of the present application.

[0153] That is to say, for the terminal device within the coverage of the first beam group, due to the repeated transmission of the first beam group, the terminal device can receive RMSI multiple times within the first sending period, thereby obtaining the combined gain of RMSI.

[0154] It can be understood that for the terminal device to perform RMSI merging, the terminal device can receive 3 to 5 RMSIs within a given time to perform RMSI merging, and the obtained RMSI merging gain can meet the coverage requirement.

[0155] Furthermore, in a possible implementation, the time interval of repeated transmission of the first beam group may be equal to the repeated transmission period. That is, since the period of repeated transmission of the first beam remains unchanged, within a given time, the terminal device within the coverage of the first beam group can receive at least two RMSIs for RMSI merging, thereby reducing the degree of damage to the RMSI merging gain.

[0156] It can be understood that when the number of repeated transmissions of the first beam group is greater than or equal to 2 times, and the time interval for repeated transmissions of the first beam group can be equal to the above-mentioned repeated transmission period, the terminal device within the coverage of the first beam group can receive RMSI at least 3 times within a given time, that is, the RMSI combining gain will not be impaired.

[0157] Combine the following Figure 4 to Figure 7 , further illustrating the time domain resources corresponding to the above-mentioned first sending cycle.

[0158] For example, the time domain resources corresponding to the first transmission period are described by taking the case where the multiple beams are 16 SSB beams (ie, SSB beam #1 to SSB beam #16), the repetitive transmission period is 20ms, and the first transmission period is 160ms. Figure 5 As shown, Figure 5 (a) is a schematic diagram of a RMSI defined in TS 38.213 that is repeatedly transmitted through 16 SSB beams within 160ms. Figure 5 (b) is a schematic diagram of a time domain resource corresponding to the first transmission period including a time domain resource that only transmits the first beam group. Figure 5 In (b), the first beam group may include: SSB beam #1, SSB beam #2, and SSB beams #14 to #16. On time domain resources other than the time domain resources that only send the first beam group, the network device may send RMSI through each of the multiple beams.

[0159] That is to say, within one repeated transmission cycle of 20ms, the time domain resource overhead for transmitting RMSI is reduced from the original 16 time slots to 5 time slots, and thus the proportion of the time domain resource overhead for transmitting RMSI is reduced from 16 / 128=12.5% ​​in the previous example to 5 / 128=3.9%.

[0160] It is understandable that the above Figure 5 (b) is only an example. The time domain resources for sending only the first beam group may not be within the time domain resources corresponding to the first repeated transmission period within the first sending period, and may also be on other time domain resources except the time domain resources corresponding to the first repeated transmission period. The embodiments of the present application do not make specific limitations on this.

[0161] It should be understood that the number of time domain resources for sending only the first beam group can be multiple, which is described in detail below.

[0162] In a possible implementation, time domain resources corresponding to a repeated transmission period are used to transmit a first beam group among multiple beams, and time domain resources other than the first beam group among the multiple beams are not transmitted, including: time domain resources corresponding to each repeated transmission period among the time domain resources corresponding to N1 repeated transmission periods, are used to transmit the first beam, and time domain resources other than the first beam group among the multiple beams are not transmitted, where N1 is an integer greater than 1.

[0163] It can be understood that by using multiple time domain resources that only send the first beam group, the proportion of time domain resource overhead for transmitting RMSI in the time domain resources corresponding to the first sending period can be reduced as a whole.

[0164] Further, in a possible implementation, the time domain resources corresponding to each of the N1 repetition transmission periods are spaced apart from each other, wherein the interval may be, for example, 1 repetition transmission period, 2 repetition transmission periods, or more repetition transmission periods.

[0165] Furthermore, the interval between the time domain resources corresponding to two different repetition transmission periods may be variable. For example, taking N1 as 3, the interval between the time domain resources corresponding to the first repetition transmission period and the time domain resources corresponding to the second repetition transmission period may be 1 repetition transmission period. The interval between the time domain resources corresponding to the second repetition transmission period and the time domain resources corresponding to the third repetition transmission may be 2 repetition transmission periods.

[0166] Below Figure 5 Taking (c) in FIG. 1 as an example, the proportion of time domain resource overhead for transmitting RMSI is illustrated.

[0167] like Figure 5 As shown in (c), N1 is 2, that is, the first transmission cycle includes two time domain resources that only transmit the first beam group. The time interval between the two time domain resources that only transmit the first beam group is one repeated transmission cycle. In other words, the transmission time required for the two time domain resources that only transmit the first beam group is the time corresponding to three repeated transmission cycles. Then, within the time corresponding to the three repeated transmission cycles, relative to Figure 5 (a) The time domain resource overhead of transmitting RMSI accounts for 12.5%, Figure 5 In (c), the proportion of time domain resource overhead for transmitting RMSI can be reduced to (5+16+5) / (3×128)=6.8%.

[0168] In another possible implementation, the time domain resources corresponding to each of the time domain resources corresponding to the N1 repeated transmission periods are adjacent to each other. It can be understood that, compared with the case where the time domain resources corresponding to the above-mentioned N1 repeated transmission periods are spaced from each other, the time domain resources corresponding to the N1 repeated transmission periods are adjacent to each other, which can reduce the transmission time required for transmitting the N1 first beam groups only, and further reduce the proportion of time domain resource overhead for transmitting RMSI.

[0169] For example, relative to Figure 5 The two time domain resources in (c) that only send the first beam group require three repeated transmission cycles (i.e., 60ms), because Figure 5 The two time domain resources in (d) that only transmit the first beam group are adjacent to each other, so the required transmission time is only 2 repeated transmission cycles (i.e. 40ms). Figure 5 For example, in (d) of FIG. 1 , the proportion of the time domain resource overhead of transmitting RMSI within the required transmission time can be obtained by Figure 5 The 6.8% in (c) is reduced to (5+5) / (2×128)=3.9%.

[0170] It can be understood that within the time domain resources corresponding to the first transmission cycle, within the time resources (40ms) corresponding to the first two repeated transmission cycles, Figure 5 In (c), the time domain resource overhead of transmitting RMSI in the first 40ms accounts for (5+16) / (2×128)=8.2%. Figure 5 In (d), the time domain resource overhead of transmitting RMSI in the first 40 ms accounts for 3.9%.

[0171] That is to say, within a certain time period in the first sending cycle, the time domain resources corresponding to each of the time domain resources corresponding to the N1 repeated transmission periods are adjacent to each other, which can further reduce the proportion of time domain resource overhead for transmitting RMSI within the certain time period.

[0172] It is also understandable that the above Figure 5 (c) and (d) are only examples. The time domain resources for sending only the first beam group can also be at any time domain position within the time domain resources corresponding to the first sending period. The embodiments of the present application do not make specific limitations on this.

[0173] In a possible implementation, when N1 is greater than 2, time domain resources corresponding to at least two of the time domain resources corresponding to the N1 repeated transmission periods are adjacent to each other. It can be understood that the time domain resources corresponding to at least two repeated transmission periods are adjacent to each other, which can reduce the proportion of time domain resource overhead for transmitting RMSI in the time domain resources corresponding to adjacent repeated transmission periods.

[0174] For example, Figure 5 (e) is a schematic diagram of the time domain resources corresponding to the first transmission cycle when N1 is adjusted to 7. Figure 5 As shown in (e), among the time domain resources corresponding to the 7 repeated transmission periods, the time domain resources corresponding to the 6 repeated transmission periods are adjacent to each other. In other words, in the last 120ms of 160ms, the time domain resource overhead of transmitting RMSI accounts for 3.9%.

[0175] It should be understood that the above Figure 5 In (a) to (e), the first beam group is transmitted 8 times in the first transmission cycle, and the time interval between two adjacent transmissions is the repeated transmission cycle, that is, for the terminal equipment within the coverage of the first beam group, the RMSI combining gain will not be impaired.

[0176] In a possible implementation, the transmission time required for the first beam group in the first transmission cycle is the time corresponding to N1 repeated transmission cycles. That is, in the first transmission cycle, the first beam group is transmitted through the time domain resource that only transmits the first beam group, and is not repeatedly transmitted on other time domain resources, which can further reduce the time domain resource overhead of transmitting RMSI. Furthermore, the first beam group transmitted by adjacent repetitions can also reduce the degree of damage to the RMSI combining gain.

[0177] For example, Figure 5 For example, if the first beam group is not sent in the last 120ms of 160ms, the time domain resource overhead of transmitting RMSI in the last 120ms is reduced from 12.5% ​​to 3.9%. Furthermore, the terminal device within the coverage of the first beam group can receive 2 RMSIs for RMSI merging in the first 40ms of 160ms, thereby reducing the degree of damage to the RMSI merging gain.

[0178] It can be understood that, on the basis of not repeatedly sending the first beam group on other time domain resources, other time domain resources can be used to send other beams in multiple beams except the first beam group, such as the second beam group, and then can be used for terminal devices within the coverage of the second beam group to receive RMSI.

[0179] The following introduces the time domain resources used for transmitting the second beam group within the time domain resources corresponding to the first sending period.

[0180] In one possible implementation, the time domain resources corresponding to the first sending period also include: within the time domain resources corresponding to the repeated transmission period, time domain resources are used to transmit the second beam group among the multiple beams, and time domain resources other than the second beam group among the multiple beams are not transmitted, and the beams included in the second beam group are different from the beams included in the first beam group.

[0181] That is to say, on the basis of sending only the first beam group, the proportion of time domain resource overhead for transmitting RMSI can be further reduced by not sending other beams except the second beam group.

[0182] It should be understood that, for the sake of convenience, the above-mentioned "within the time domain resources corresponding to the repeated transmission period, the time domain resources for transmitting the second beam group among the multiple beams, and not transmitting other beams among the multiple beams except the second beam group" is replaced by "only the time domain resources for sending the second beam group".

[0183] In a possible implementation, the number of beams included in the second beam group may be K. Taking the case where the multiple beams are M beams and the number of beams included in the first beam group is Y as an example, the value range of K is: [1, MY]. Furthermore, when K is greater than 1, the K beams are adjacent to each other or spaced apart, and the embodiment of the present application does not specifically limit this.

[0184] It is understood that the above K can be the same as or different from Y. Taking M=16 as an example, Y can be equal to 4, and K can be equal to any value between 1 and 12. For example, Figure 5 The first beam group in (a) to (e) is: SSB beam #1, SSB beam #2, and SSB beam #14 to #16, and the second beam group can be: any one, two, three, or 12 of SSB beam #3 to SSB beam #13. Taking the second beam group including SSB beam #3 to SSB beam #13 as an example, within the time domain resources corresponding to the first transmission period, within one repeated transmission period of 20ms, the time domain resource overhead for transmitting RMSI is reduced from the original 16 time slots to 11 time slots, and thus the proportion of time domain resource overhead for transmitting RMSI is reduced from 12.5% ​​to 8.6%.

[0185] In a possible implementation, the time domain resources corresponding to a repeated transmission period are used to transmit the second beam group among multiple beams, and the time domain resources other than the second beam group among the multiple beams are not transmitted, including: in the time domain resources corresponding to each repeated transmission period among the time domain resources corresponding to N2 repeated transmission periods, the time domain resources are used to transmit the second beam, and the time domain resources other than the second beam group among the multiple beams are not transmitted, where N2 is an integer greater than 1.

[0186] That is to say, within the time domain resources corresponding to the first sending period, the second beam group can also be transmitted repeatedly, thereby reducing the degree of damage to the RMSI combining gain for the terminal devices within the coverage of the second beam group.

[0187] It can be understood that the time domain resources for only sending the second beam group are similar to the time domain resources for only sending the first beam group. For example, the number of time domain resources for only sending the second beam group may be N2; for another example, the time domain resources corresponding to the N2 repeated transmission periods may be located at any time domain position within the first sending period; for another example, the time domain resources corresponding to each of the N2 repeated transmission periods may be intermittent, adjacent, or partially adjacent. For details, please refer to the aforementioned description on "time domain resources for only sending the first beam group", which will not be repeated here.

[0188] The time domain resources corresponding to the first sending period are further explained below in combination with the time domain resources for sending only the first beam group and the time domain resources for sending only the second beam group.

[0189] In a possible implementation, the time domain resources corresponding to each repetition transmission period in the time domain resources corresponding to N1 repetition transmission periods and the time domain resources corresponding to each repetition transmission period in the time domain resources corresponding to N2 repetition transmission periods may be adjacent.

[0190] For example, Figure 6 As shown in (a) in the figure, the first beam group is Figure 5 The first beam group in (a) to (d), the second beam group includes: SSB beam #3 to SSB beam #13. The time domain resources corresponding to the first transmission period can be divided into two categories: time domain resources for only transmitting the first beam group and time domain resources for only transmitting the second beam group. Further, the number of time domain resources for only transmitting the first beam group is N1, and the number of time domain resources for only transmitting the second beam group is N2. The two types of time domain resources can be arranged alternately in the time domain, that is, Figure 6 As shown in (a) in .

[0191] It is understandable that Figure 6 As shown in (a), within the time domain resources corresponding to the first sending cycle, the proportion of time domain resource overhead for transmitting RMSI is reduced from 12.5% ​​to 6.25%.

[0192] In a possible implementation, N1 and N2 may be different. The time domain resources for sending only the first beam group and the time domain resources for sending only the second beam group may be arranged alternately first or later. Figure 6 As shown in (b), N1=3, N2=5, 3 time domain resources that only send the first beam group and 3 time domain resources that only send the second beam group can be arranged alternately first, and then the remaining 2 time domain resources that only send the second beam group can be arranged.

[0193] It can be understood that the time domain resources for sending only the first beam group and the time domain resources for sending only the second beam group can also be arranged in other ways. Figure 6 As shown in (c), within the time domain resources corresponding to the first sending cycle, the time domain resources are arranged in chronological order as follows: time domain resources for only sending the first beam group, two time domain resources for only sending the second beam group, time domain resources for only sending the first beam group, time domain resources for only sending the second beam group, time domain resources for only sending the first beam group, and two time domain resources for only sending the second beam group.

[0194] In a possible implementation, the first beam group is periodically transmitted in a first transmission period, wherein the period of transmission of the first beam group in the first transmission period may be a repeated transmission period.

[0195] That is to say, for the terminal device within the coverage of the first beam group, it can continuously receive N1 RMSIs for RMSI merging, thereby reducing the degree of damage to the RMSI merging gain.

[0196] It can be understood that the second beam group can also be transmitted periodically within the first sending cycle, and the transmission period of the second beam group within the first sending cycle can also be a repeated transmission period. In this way, for the terminal equipment within the coverage range of the second beam group, the degree of damage to the RMSI combining gain can be reduced.

[0197] It should be understood that the network device may transmit the first beam group N1 times and then transmit the second beam group N2 times in the first transmission cycle. Alternatively, the network device may transmit the second beam group N2 times and then transmit the first beam group N1 times.

[0198] For example, Figure 6 As shown in (d), in the first sending cycle, the first beam group can be transmitted 4 times, and then the second beam group can be transmitted 4 times. Therefore, in the time domain resources corresponding to the first sending cycle, the time domain resource overhead of transmitting RMSI in the first 80ms accounts for 3.9%, and the time domain resource overhead of transmitting RMSI in the last 80ms accounts for 11 / 128=8.6%.

[0199] It can be understood that when the number of beams between the first beam group and the second beam group is less than the number of multiple beams that need to be traversed, the network device can also send a third beam group, or the third beam group and the fourth beam group, etc. The third beam group may include other beams in the multiple beams except the first beam group and the second beam group. The fourth beam group may include other beams in the multiple beams except the first beam group to the third beam group.

[0200] For example, Figure 6As shown in (e), the network device can send the first beam group to the fourth beam group. The first beam group includes: SSB beam #1 to SSB beam #4. The second beam group includes: SSB beam #5 to SSB beam #8. The third beam group includes: SSB beam #9 to SSB beam #12. The fourth beam group includes: SSB beam #13 to SSB beam #16.

[0201] Furthermore, the number of times each beam group in the first beam group to the fourth beam group is transmitted in the first sending period may be the same or different, and this embodiment of the present application does not specifically limit this.

[0202] For example, in Figure 6 In the example shown in (e), the number of transmissions of each beam group from the first beam group to the fourth beam group in the first transmission cycle is 2, that is, each beam group can be repeatedly transmitted once. Among them, the transmission time required for each beam group from the first beam group to the fourth beam group in the first transmission cycle is the time corresponding to two repeated transmission cycles, that is, 40ms. In other words, SSB beam #1 to SSB beam #4 can be transmitted twice in the first 40ms of the first transmission cycle, SSB beam #5 to SSB beam #8 can be transmitted twice in the 40ms to 80ms of the first transmission cycle, SSB beam #9 to SSB beam #12 can be transmitted twice in the 80ms to 120ms of the first transmission cycle, and SSB beam #13 to SSB beam #16 can be transmitted twice in the 120ms to 160ms of the first transmission cycle. In this way, in the time domain resources corresponding to the first transmission cycle, the proportion of time domain resource overhead for transmitting RMSI is reduced from 12.5% ​​to 1 / 4 of the original.

[0203] It can also be understood that the transmission time required for each beam group of the first to fourth beam groups in the first transmission cycle may be a multiple of the repeated transmission cycle, such as 20ms, 40ms, 80ms, 160ms, etc. For example, when the transmission time required for each beam group of the first to fourth beam groups in the first transmission cycle is 160ms, the first transmission cycle is 640ms.

[0204] It should be understood that, as described above regarding the first sending cycle, transmitting RMSI through the first sending cycle and the time domain resources corresponding to the first sending cycle can reduce the proportion of time domain resource overhead for transmitting RMSI and reduce the degree of damage to the RMSI combining gain, thereby increasing the proportion of time domain resources used for downlink data transmission and reducing power consumption when the network device is unloaded or underloaded.

[0205] The following exemplarily introduces a scenario in which the network device determines the first sending period and the time domain resources corresponding to the first sending period (ie, step S401) according to the repeated transmission period of the RMSI.

[0206] For example, the network device may perform step S401 when it is unloaded or lightly loaded. When it is unloaded or lightly loaded, fewer terminal devices need to access the network in the cell corresponding to the network device, and the network device may not send RMSI frequently, thereby saving power consumption.

[0207] For another example, the network device may execute step S401 when the downlink data transmission demand is high, and then use the saved time domain resources for transmitting RMSI for PDSCH scheduling of other terminal devices to improve the downlink data transmission rate.

[0208] It is understandable that the network device may also execute step S401 according to the CN instruction, and this embodiment of the present application does not specifically limit this.

[0209] For step S402:

[0210] It can be understood that, as described above regarding "Second, SSB", after the terminal device receives the SSB from the network device, it can obtain the required configuration parameters of the RMSI according to the MIB in the SSB, and blindly detect the PDCCH according to the configuration parameters, and then obtain the DCI indicating the time-frequency resources of the PDSCH carrying the RMSI, so that the terminal device can receive the RMSI from the network device. Among them, the specific process of the above-mentioned terminal device obtaining the RMSI can refer to the relevant description of TS 38.213, which will not be repeated here.

[0211] It can be understood that, for the above-mentioned situation of transmitting only the first beam group, the network device may not send the PDCCH corresponding to other beams in the multiple beam groups except the first beam group.

[0212] It should be understood that in the embodiment of the present application, the network device may be the O-CU, O-DU, or O-RU in the aforementioned ORAN, or a combination of O-CU, O-DU, or O-RU. For example, the O-DU may decide how to broadcast system information based on scheduling parameters, such as the O-DU may determine the first transmission period and the time domain resources corresponding to the first transmission period based on the repeated transmission period of the RMSI. Furthermore, the O-DU may send the RMSI through the O-RU based on the first transmission period and the time domain resources corresponding to the first transmission period.

[0213] For another example, the O-CU may determine the first sending period and the time domain resources corresponding to the first sending period according to the repeated transmission period of the RMSI, and send the RMSI through the O-RU according to the first sending period and the time domain resources corresponding to the first sending period.

[0214] For another example, the O-CU may determine the first transmission period and the time domain resources corresponding to the first transmission period according to the repeated transmission period of the RMSI, and the O-DU may generate the specific content of the RMSI, and then send the RMSI through the O-RU. It can be understood that the O-DU may also determine the first transmission period and the time domain resources corresponding to the first transmission period according to the repeated transmission period of the RMSI, and the O-CU generates the specific content of the RMSI.

[0215] It should be understood that since the O-CU and O-DU are responsible for the functions of the high-level protocol layer, and the high-level information will eventually become the information of the PHY layer, or be converted from the information of the PHY layer, therefore, under the ORAN architecture, the RMSI in the embodiment of the present application can also be considered to be sent by the O-CU and / or O-DU.

[0216] Since in the embodiment of the present application, the network device sends RMSI through the time domain resources corresponding to the first sending period, and thus the network device can send RMSI only through the first beam group within the time domain resources corresponding to the repeated transmission period, without sending RMSI through each beam, thereby reducing the proportion of time domain resource overhead for transmitting RMSI within the time domain resources corresponding to the repeated transmission period. Furthermore, the first beam group is repeatedly transmitted within the first sending period, thereby reducing the degree of damage to the RMSI combining gain. Therefore, based on the system information sending method provided in the embodiment of the present application, the degree of damage to the RMSI combining gain can be reduced while reducing the proportion of time domain resource overhead for transmitting RMSI.

[0217] The actions of the network devices in steps S401 to S402 can be performed by Figure 3 The processor 301 in the communication device 300 shown in the figure calls the application code to instruct the communication device 300 to execute. The actions of the terminal device in the above steps S401 to S402 can be performed by Figure 3 The processor 301 in the communication device 300 shown calls the application code to instruct the communication device 300 to execute, and the embodiment of the present application does not impose any limitation on this.

[0218] The above mainly introduces the scheme provided by the embodiment of the present application from the perspective of interaction between various network elements. Accordingly, the embodiment of the present application also provides a communication device, which is used to implement the above various methods. The communication device can be a network device in the above method embodiment, or a device including the above network device, or a component that can be used for a network device; or, the communication device can be a first terminal device in the above method embodiment, or a device including the above first terminal device, or a component that can be used for a first terminal device. It can be understood that in order to implement the above functions, the communication device includes a hardware structure and / or software module corresponding to each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0219] The embodiment of the present application can divide the functional modules of the communication device according to the above method embodiment. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be understood that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0220] For example, taking the communication device as the network device in the above method embodiment as an example, Figure 7 The schematic diagram of the structure of a network device 700 is shown. The network device 700 includes a transceiver module 701 and a processing module 702. The transceiver module 701, which may also be called a transceiver unit, is used to implement the transceiver function, and may be, for example, a transceiver circuit, a transceiver, a transceiver or a communication interface.

[0221] The processing module 702 is used to implement the processing function corresponding to the network device in the above method embodiment, and the transceiver module 701 is used to implement the transceiver function corresponding to the network device in the above method embodiment.

[0222] For example, the processing module 702 is used to determine the first transmission period and the time domain resources corresponding to the first transmission period according to the repeated transmission period of the RMSI; the transceiver module 701 is used to send the RMSI to the terminal device according to the first transmission period and the time domain resources corresponding to the first transmission period. The repeated transmission period is a repeated transmission period for transmitting the RMSI through each beam in a plurality of beams. The time domain resources corresponding to the first transmission period include: within the time domain resources corresponding to the repeated transmission period, time domain resources for transmitting the first beam group in a plurality of beams, and not transmitting other beams in the plurality of beams except the first beam group, and the first beam group is repeatedly transmitted in the first transmission period.

[0223] In some embodiments, the time domain resource used to transmit each of the plurality of beams is determined based on the SSB corresponding to each of the plurality of beams.

[0224] In some embodiments, within the time domain resources corresponding to a repeated transmission period, time domain resources are used to transmit a first beam group among multiple beams, and time domain resources other than the first beam group among the multiple beams are not transmitted, including: within the time domain resources corresponding to each repeated transmission period among the time domain resources corresponding to N1 repeated transmission periods, time domain resources are used to transmit the first beam, and time domain resources other than the first beam group among the multiple beams are not transmitted, where N1 is an integer greater than 1.

[0225] In some embodiments, the time domain resources corresponding to each repetition transmission period in the time domain resources corresponding to the N1 repetition transmission periods are spaced apart from each other.

[0226] In some embodiments, the time domain resources corresponding to each of the time domain resources corresponding to the N1 repetitive transmission periods are adjacent to each other.

[0227] In some embodiments, when N1 is greater than 2, time domain resources corresponding to at least two of the time domain resources corresponding to the N1 repetition transmission periods are adjacent to each other.

[0228] In some embodiments, the transmission time required for the first beam group in the first transmission cycle is the time corresponding to N1 repeated transmission cycles.

[0229] In some embodiments, the time domain resources corresponding to the first sending period also include: within the time domain resources corresponding to the repeated transmission period, time domain resources are used to transmit the second beam group among the multiple beams, and do not transmit other beams among the multiple beams except the second beam group, and the beams included in the second beam group are different from the beams included in the first beam group.

[0230] In some embodiments, within the time domain resources corresponding to a repeated transmission period, time domain resources are used to transmit the second beam group among multiple beams, and time domain resources other than the second beam group among the multiple beams are not transmitted, including: within the time domain resources corresponding to each repeated transmission period among the time domain resources corresponding to N2 repeated transmission periods, time domain resources are used to transmit the second beam, and time domain resources other than the second beam group among the multiple beams are not transmitted, where N2 is an integer greater than 1.

[0231] Among them, all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, and will not be repeated here.

[0232] In the embodiment of the present application, the network device 700 is presented in the form of dividing various functional modules in an integrated manner. The "module" here can refer to a specific ASIC, circuit, processor and memory that executes one or more software or firmware programs, integrated logic circuit, and / or other devices that can provide the above functions. In a simple embodiment, those skilled in the art can imagine that the network device 700 can be used Figure 3 The form of the communication device 300 is shown.

[0233] for example, Figure 3 The processor 301 in the communication device 300 shown can call a computer to execute instructions, so that the communication device 300 executes the system information sending method in the above method embodiment.

[0234] Specifically, Figure 7 The functions / implementation processes of the transceiver module 701 and the processing module 702 can be Figure 3 The processor 301 in the communication device 300 shown calls a computer to execute instructions to implement. Or, Figure 7 The function / implementation process of the processing module 702 in Figure 3 The processor 301 in the communication device 300 shown calls the computer to execute instructions to implement, Figure 7 The function / implementation process of the transceiver module 701 can be Figure 3 The communication interface 304 in the communication device 300 shown in FIG.

[0235] Since the network device 700 provided in the embodiment of the present application can execute the above-mentioned system information sending method, the technical effects that can be obtained can refer to the above-mentioned method embodiment and will not be repeated here.

[0236] It should be understood that one or more of the above modules or units can be implemented by software, hardware or a combination of the two. When any of the above modules or units are implemented in software, the software exists in the form of computer program instructions. Optionally, the computer program instructions are stored in a memory, and the processor can be used to execute the program instructions and implement the above method flow. The processor can be built into an SoC (system on chip) or an ASIC, or it can be an independent semiconductor chip. In addition to the core used to execute software instructions for calculation or processing in the processor, it can also further include necessary hardware accelerators, such as field programmable gate arrays (FPGA), PLDs (programmable logic devices), or logic circuits that implement special logic operations.

[0237] When the above modules or units are implemented in hardware, the hardware can be any one or any combination of a CPU, a microprocessor, a digital signal processing (DSP) chip, a microcontroller unit (MCU), an artificial intelligence processor, an ASIC, a SoC, an FPGA, a PLD, a dedicated digital circuit, a hardware accelerator or a non-integrated discrete device, which can run the necessary software or not rely on the software to execute the above method flow.

[0238] Optionally, an embodiment of the present application further provides a communication device (for example, the communication device may be a chip or a chip system), which includes a processor for implementing the method in any of the above method embodiments.

[0239] Optionally, the communication device further includes a memory. The memory is used to store necessary program instructions and data, and the processor can call the program code stored in the memory to instruct the communication device to execute the method in any of the above method embodiments. Of course, the memory may not be in the communication device. When the communication device is a chip system, it can be composed of a chip, or it can include a chip and other discrete devices, which is not specifically limited in the embodiments of the present application.

[0240] Optionally, an embodiment of the present application further provides a computer-readable storage medium, which stores a computer program or instruction, and when the computer-readable storage medium is run on a communication device, the communication device can execute the method described in any of the above method embodiments or any of its implementation methods.

[0241] Optionally, an embodiment of the present application further provides a communication system, which includes the network device described in the above method embodiment and the terminal device described in the above method embodiment.

[0242] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using a software program, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loading and executing computer program instructions on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. Computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, data center, etc. that contains one or more servers that can be integrated with a medium. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0243] Although the present application is described herein in conjunction with various embodiments, in the process of implementing the claimed application, those skilled in the art may understand and implement other changes to the disclosed embodiments by viewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "one" or "an" does not exclude multiple situations. A single processor or other unit may implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0244] Although the present application has been described in conjunction with specific features and embodiments thereof, it is obvious that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Accordingly, this specification and the drawings are merely exemplary illustrations of the present application as defined by the appended claims, and are deemed to have covered any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A method for sending system information, characterized in that: The method comprises: The network device determines, according to the repeated transmission period of the remaining minimum system information RMSI, a first transmission period and a time domain resource corresponding to the first transmission period, where the repeated transmission period is a repeated transmission period for transmitting the RMSI through each beam in a plurality of beams, and the time domain resource corresponding to the first transmission period includes: within the time domain resource corresponding to the repeated transmission period, a time domain resource for transmitting a first beam group in the plurality of beams, and not transmitting other beams in the plurality of beams except the first beam group, and the first beam group is repeatedly transmitted in the first transmission period; The network device sends the RMSI to the terminal device according to the first sending period and the time domain resources corresponding to the first sending period.

2. The method according to claim 1, characterized in that The time domain resources corresponding to the repeated transmission period are used to transmit the first beam group among the multiple beams, and the time domain resources other than the first beam group among the multiple beams are not transmitted, including: the time domain resources corresponding to each repeated transmission period among N1 time domain resources corresponding to the repeated transmission periods are used to transmit the first beam, and the time domain resources other than the first beam group among the multiple beams are not transmitted, and N1 is an integer greater than 1.

3. The method according to claim 2, characterized in that When N1 is greater than 2, time domain resources corresponding to at least two of the time domain resources corresponding to the N1 repeated transmission periods are adjacent to each other.

4. The method according to claim 2 or 3, characterized in that: The time domain resources corresponding to each repetitive transmission period in the N1 time domain resources corresponding to the repetitive transmission periods are adjacent to each other.

5. The method according to claim 2, characterized in that: The time domain resources corresponding to each repetitive transmission period in the N1 time domain resources corresponding to the repetitive transmission periods are spaced apart from each other.

6. The method according to any one of claims 2 to 5, characterized in that: The transmission time required for the first beam group in the first sending cycle is the time corresponding to N1 repeated transmission cycles.

7. The method according to any one of claims 1 to 6, characterized in that The time domain resources corresponding to the first sending period also include: within the time domain resources corresponding to the repeated transmission period, time domain resources are used to transmit the second beam group among the multiple beams, and do not transmit other beams among the multiple beams except the second beam group, and the beams included in the second beam group are different from the beams included in the first beam group.

8. The method according to claim 7, characterized in that The time domain resources corresponding to the repeated transmission period are used to transmit the second beam group among the multiple beams, and the time domain resources other than the second beam group among the multiple beams are not transmitted, including: the time domain resources corresponding to each repeated transmission period among N2 time domain resources corresponding to the repeated transmission periods are used to transmit the second beam, and the time domain resources other than the second beam group among the multiple beams are not transmitted, and N2 is an integer greater than 1.

9. The method according to any one of claims 1 to 8, characterized in that The time domain resources used for transmitting each of the multiple beams are determined according to a synchronization signal / physical broadcast channel block SSB corresponding to each of the multiple beams.

10. A communication device, characterized in that: The communication device is used to execute the system information sending method according to any one of claims 1 to 9.

11. A communication device, characterized in that: The communication device includes a processor and a storage medium, wherein the storage medium stores instructions, and when the instructions are executed by the processor, the system information sending method according to any one of claims 1 to 9 is implemented.

12. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes instructions, and when the instructions are executed by a processor, the system information sending method according to any one of claims 1 to 9 is implemented.

13. A computer program product, characterized in that The computer program product comprises instructions, and when the instructions are executed by a processor, the system information sending method according to any one of claims 1 to 9 is implemented.

Images