A method, device and storage medium for receiving and sending system messages

By determining the PDCCH listening timing and confirming the beam-related fields of the system message in the NTN system, the problem of beam-level system message indication in the satellite network is solved, and the effective transmission of system messages and beam-related parameters is realized and the coverage area adaptation is achieved. , improves communication efficiency.

CN114389774BActive Publication Date: 2024-11-08CHINA MOBILE COMM LTD RES INST +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202011136913.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-10-22
Publication Date
2024-11-08
Estimated Expiration
2040-10-22

AI Technical Summary

Technical Problem

The prior art cannot effectively support beam-level system message indications in satellite networks, resulting in the inability to adapt beam-related parameters in NTN scenarios, affecting communication coverage and efficiency.

Method used

By determining the PDCCH listening timing and confirming that the system message is related to the beam and/or SSB based on the fields in SIB-TypeInfo and SIB, a system message reception and transmission method is provided, system message indication is supported at the beam level, and similar messages are merged to optimize information transfer.

Benefits of technology

The effective transmission of system messages and beam-related parameters broadcast by the base station in the NTN system is realized, the adaptability of the beam coverage area and information transmission efficiency are improved, and the overhead of system messages is reduced.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114389774B_ABST
    Figure CN114389774B_ABST
Patent Text Reader

Abstract

The present invention discloses a method, device and storage medium for receiving and sending system messages, including: determining a PDCCH listening time; receiving a system message according to the determined PDCCH listening time. The base station determines the system message that needs to be sent to the terminal; and sends the system message on the PDCCH. The present invention solves the problem that when the base station needs to broadcast many beam-related parameters, it can only support the cell-level system message indication method and cannot support the parameter indication under the NTN. The information carried in the SI has better adaptability to the coverage area of ​​the beam; the system message overhead is small.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of wireless communication technology, and in particular to a method, device and storage medium for receiving and sending system messages. Background Art

[0002] In order to meet the demand for ubiquitous wireless coverage, the 5G system needs to support the integration of terrestrial networks and satellite networks. To this end, 3GPP is conducting NTN (non-terrestrial network) research, hoping to provide cost-effective coverage for unserved areas (e.g., ocean, aircraft, underwater) in 5G deployment through satellite networks;

[0003] Strengthen the reliability of 5G networks: improve the continuity of high-speed M2M (Machine to Machine) / IoT (Internet of Things) services, provide communications in extreme environments, and provide emergency communications guarantees;

[0004] Ensure 5G network scalability and provide effective multicast / broadcast resources for the network edge.

[0005] Figure 1 This is a schematic diagram of a satellite network architecture. As shown in the figure, existing satellite systems usually use a point beam coverage method, that is, the satellite generates multiple spaced beams to form a relatively ideal cellular structure.

[0006] The current discussion requires support for the following two working modes:

[0007] Mode 1: Each satellite generates only one cell, and each cell includes multiple spot beams;

[0008] Mode 2: Each satellite generates multiple cells, and each cell includes only one spot beam.

[0009] The base station needs to broadcast many beam-related parameters. However, the deficiency of the existing technology is that the existing system message indication method that only supports the cell level cannot well adapt to the indication requirements of beam-related parameters under NTN. Summary of the invention

[0010] The present invention provides a system message receiving and sending method, device and storage medium, which are used to support a beam-level system message indication mode.

[0011] The present invention provides the following technical solutions:

[0012] A method for receiving a system message, comprising:

[0013] Determine the PDCCH listening opportunity;

[0014] Receive system messages according to the determined PDCCH listening opportunity.

[0015] In implementation, the system message is related to a beam and / or SSB.

[0016] In implementation, the UE does not expect the same values ​​corresponding to the same fields in system messages related to different beams and / or SSBs in the same cell to be the same.

[0017] In implementation, it is determined that the system message is related to the beam and / or SSB by one of the following methods or a combination thereof:

[0018] According to a pre-agreed agreement, confirm that the system message is related to the beam and / or SSB;

[0019] Confirming, according to a first field in SIB-TypeInfo, that the system message is related to a beam and / or an SSB, wherein the first field indicates that the system message is related to a beam and / or an SSB;

[0020] Confirming, according to a second field in the SIB, that the system message is related to the beam and / or the SSB, wherein the second field indicates that the system message is related to the beam and / or the SSB;

[0021] According to the third field in the SIB, it is confirmed that the system message is related to the beam and / or SSB, wherein the third field indicates the beam indication or SSB indication corresponding to the system message.

[0022] In implementation, the first field and areaScope in the SIB-TypeInfo cannot simultaneously take the value of true.

[0023] In an implementation, the system message is associated with the first spatial relationship.

[0024] In implementation, the UE does not expect that the values ​​corresponding to the same field in the system messages related to different first spatial relationships in the same cell are the same.

[0025] In implementation, determining that the system message is related to the first spatial relationship is done by one of the following methods or a combination thereof:

[0026] According to the fourth field in the SIB, confirm that the system message is related to the first spatial relationship, wherein the fourth field includes at least one of the following indications or a combination thereof:

[0027] SSB instructions;

[0028] a first reference signal indication;

[0029] TCI indication;

[0030] The first reference signal includes at least one of the following reference signals:

[0031] CSI-RS, TRS, SRS.

[0032] In implementation, the system message includes a fifth field, wherein:

[0033] The fifth field is related to the beam;

[0034] And / or, the fifth field is related to SSB;

[0035] And / or, the fifth field is related to the first spatial relationship.

[0036] During implementation, the UE does not expect that the value corresponding to the fifth field in the system message related to different beams, SSBs, or first spatial relationships in the same cell is the same.

[0037] In an implementation, the fifth field is used to indicate at least one of the following parameters:

[0038] General timing advance, timing offset, RAR listening offset.

[0039] During implementation, when the system message includes a beam indication, when the beam indications corresponding to the system messages received N times are the same, the system messages received N times are merged; and / or, if the beam indications corresponding to the system messages received N times are different, the system messages received N times are not merged; wherein N is greater than or equal to 2.

[0040] During implementation, it further includes:

[0041] When N received system messages correspond to the same SSB number,

[0042] If the SSB is not updated, merging the system messages received N times;

[0043] and / or, if the SSB is updated, the system messages received N times are not merged;

[0044] Wherein, N is greater than or equal to 2.

[0045] In implementation, the system message further includes one or a combination of the following parameters:

[0046] General timing advance, timing offset, RAR listening offset.

[0047] During implementation, determining the PDCCH listening opportunity includes:

[0048] Determine that the PDCCH listening opportunity is associated with a beam, an SSB and / or a first spatial relationship.

[0049] In implementation, the terminal assumes that the system message is sent only in a PDCCH listening opportunity associated with the beam, the SSB and / or the first spatial relationship;

[0050] And / or, the terminal assumes that the system message is not sent in a PDCCH listening occasion other than a PDCCH listening occasion associated with the beam, the SSB and / or the first spatial relationship.

[0051] A method for sending SI, comprising:

[0052] The base station determines the system message that needs to be sent to the terminal;

[0053] System messages are sent on PDCCH.

[0054] In implementation, the system message is related to a beam and / or SSB.

[0055] In implementation, the UE does not expect the same values ​​corresponding to the same fields in system messages related to different beams and / or SSBs in the same cell to be the same.

[0056] In implementation, it is determined that the system message is related to the beam and / or SSB by one of the following methods or a combination thereof:

[0057] According to a pre-agreed agreement, confirm that the system message is related to the beam and / or SSB;

[0058] Confirming, according to a first field in SIB-TypeInfo, that the system message is related to a beam and / or an SSB, wherein the first field indicates that the system message is related to a beam and / or an SSB;

[0059] According to the second field in the SIB, it is confirmed that the system message is related to the beam and / or SSB, wherein the second field indicates that the system message is related to the beam and / or SSB.

[0060] According to the third field in the SIB, it is confirmed that the system message is related to the beam and / or SSB, wherein the third field indicates the beam indication or SSB indication corresponding to the system message.

[0061] In implementation, the first field and areaScope in the SIB-TypeInfo cannot simultaneously take the value of true.

[0062] In an implementation, the system message is associated with the first spatial relationship.

[0063] In implementation, the UE does not expect that the values ​​corresponding to the same field in the system messages related to different first spatial relationships in the same cell are the same.

[0064] In implementation, determining that the system message is related to the first spatial relationship is done by one of the following methods or a combination thereof:

[0065] According to the fourth field in the SIB, confirm that the system message is related to the first spatial relationship, wherein the fourth field includes at least one of the following indications or a combination thereof:

[0066] SSB instructions;

[0067] a first reference signal indication;

[0068] TCI indication;

[0069] The first reference signal includes at least one of the following reference signals:

[0070] CSI-RS, TRS, SRS.

[0071] In implementation, the system message includes a fifth field, wherein the fifth field is related to the beam;

[0072] And / or, the fifth field is related to SSB;

[0073] And / or, the fifth field is related to the first spatial relationship.

[0074] During implementation, the UE does not expect that the value corresponding to the fifth field in the system message related to different beams, SSBs, or first spatial relationships in the same cell is the same.

[0075] In an implementation, the fifth field is used to indicate at least one of the following parameters:

[0076] General timing advance, timing offset, RAR listening offset.

[0077] In implementation, the system message further includes one or a combination of the following parameters:

[0078] General timing advance, timing offset, RAR listening offset.

[0079] In implementation, the PDCCH for sending SI includes:

[0080] The PDCCH is associated with a beam, an SSB and / or a first spatial relationship.

[0081] A terminal, comprising:

[0082] The processor reads the program in the memory and performs the following processes:

[0083] Determine the PDCCH listening opportunity;

[0084] Receive system messages according to the determined PDCCH listening opportunity;

[0085] A transceiver is used to receive and send data under the control of the processor.

[0086] In implementation, the system message is related to a beam and / or SSB.

[0087] In implementation, the UE does not expect the same values ​​corresponding to the same fields in system messages related to different beams and / or SSBs in the same cell to be the same.

[0088] In implementation, it is determined that the system message is related to the beam and / or SSB by one of the following methods or a combination thereof:

[0089] According to a pre-agreed agreement, confirm that the system message is related to the beam and / or SSB;

[0090] Confirming, according to a first field in SIB-TypeInfo, that the system message is related to a beam and / or an SSB, wherein the first field indicates that the system message is related to a beam and / or an SSB;

[0091] Confirming, according to a second field in the SIB, that the system message is related to the beam and / or the SSB, wherein the second field indicates that the system message is related to the beam and / or the SSB;

[0092] According to the third field in the SIB, it is confirmed that the system message is related to the beam and / or SSB, wherein the third field indicates the beam indication or SSB indication corresponding to the system message.

[0093] In implementation, the first field and areaScope in the SIB-TypeInfo cannot simultaneously take the value of true.

[0094] In an implementation, the system message is associated with the first spatial relationship.

[0095] In implementation, the UE does not expect that the values ​​corresponding to the same field in the system messages related to different first spatial relationships in the same cell are the same.

[0096] In implementation, determining that the system message is related to the first spatial relationship is done by one of the following methods or a combination thereof:

[0097] According to the fourth field in the SIB, confirm that the system message is related to the first spatial relationship, wherein the fourth field includes at least one of the following indications or a combination thereof:

[0098] SSB instructions;

[0099] a first reference signal indication;

[0100] TCI indication;

[0101] The first reference signal includes at least one of the following reference signals:

[0102] CSI-RS, TRS, SRS.

[0103] In implementation, the system message includes a fifth field, wherein:

[0104] The fifth field is related to the beam;

[0105] And / or, the fifth field is related to SSB;

[0106] And / or, the fifth field is related to the first spatial relationship.

[0107] During implementation, the UE does not expect that the value corresponding to the fifth field in the system message related to different beams, SSBs, or first spatial relationships in the same cell is the same.

[0108] In an implementation, the fifth field is used to indicate at least one of the following parameters:

[0109] General timing advance, timing offset, RAR listening offset.

[0110] During implementation, when the system message includes a beam indication, when the beam indications corresponding to the system messages received N times are the same, the system messages received N times are merged; and / or, if the beam indications corresponding to the system messages received N times are different, the system messages received N times are not merged; wherein N is greater than or equal to 2.

[0111] During implementation, it further includes:

[0112] When N received system messages correspond to the same SSB number,

[0113] If the SSB is not updated, merging the system messages received N times;

[0114] and / or, if the SSB is updated, the system messages received N times are not merged;

[0115] Wherein, N is greater than or equal to 2.

[0116] In implementation, the system message further includes one or a combination of the following parameters:

[0117] General timing advance, timing offset, RAR listening offset.

[0118] During implementation, determining the PDCCH listening opportunity includes:

[0119] Determine that the PDCCH listening opportunity is associated with a beam, an SSB and / or a first spatial relationship.

[0120] In implementation, it is assumed that the system message is sent only in the PDCCH listening opportunity associated with the beam, SSB and / or the first spatial relationship;

[0121] And / or, the terminal assumes that the system message is not sent in a PDCCH listening occasion other than a PDCCH listening occasion associated with the beam, the SSB and / or the first spatial relationship.

[0122] A terminal, comprising:

[0123] The terminal determination module is used to determine the PDCCH listening opportunity;

[0124] The terminal receiving module is used to receive the system message according to the determined PDCCH listening opportunity.

[0125] In implementation, the system message is related to a beam and / or SSB.

[0126] In implementation, it is not expected that the values ​​corresponding to the same fields in system messages related to different beams and / or SSBs in the same cell are the same.

[0127] In implementation, the terminal determination module is further used to determine that the system message is related to the beam and / or SSB by one of the following methods or a combination thereof:

[0128] According to a pre-agreed agreement, confirm that the system message is related to the beam and / or SSB;

[0129] Confirming, according to a first field in SIB-TypeInfo, that the system message is related to a beam and / or an SSB, wherein the first field indicates that the system message is related to a beam and / or an SSB;

[0130] Confirming, according to a second field in the SIB, that the system message is related to the beam and / or the SSB, wherein the second field indicates that the system message is related to the beam and / or the SSB;

[0131] According to the third field in the SIB, it is confirmed that the system message is related to the beam and / or SSB, wherein the third field indicates the beam indication or SSB indication corresponding to the system message.

[0132] In implementation, the first field and areaScope in the SIB-TypeInfo cannot simultaneously take the value of true.

[0133] In an implementation, the system message is associated with the first spatial relationship.

[0134] In implementation, it is not expected that the values ​​corresponding to the same field in the system messages related to different first spatial relationships in the same cell are the same.

[0135] In implementation, the terminal determination module is further used to determine that the system message is related to the first spatial relationship by one of the following methods or a combination thereof:

[0136] According to the fourth field in the SIB, confirm that the system message is related to the first spatial relationship, wherein the fourth field includes at least one of the following indications or a combination thereof:

[0137] SSB instructions;

[0138] a first reference signal indication;

[0139] TCI indication;

[0140] The first reference signal includes at least one of the following reference signals:

[0141] CSI-RS, TRS, SRS.

[0142] In implementation, the system message includes a fifth field, wherein:

[0143] The fifth field is related to the beam;

[0144] And / or, the fifth field is related to SSB;

[0145] And / or, the fifth field is related to the first spatial relationship.

[0146] In implementation, it is not expected that the value corresponding to the fifth field in the system message related to different beams, SSBs, or first spatial relationships in the same cell is the same.

[0147] In an implementation, the fifth field is used to indicate at least one of the following parameters:

[0148] General timing advance, timing offset, RAR listening offset.

[0149] During implementation, the terminal receiving module is further used to, when the system message includes a beam indication, merge the system messages received N times when the beam indications corresponding to the system messages received N times are the same; and / or, if the beam indications corresponding to the system messages received N times are different, not merge the system messages received N times; wherein N is greater than or equal to 2.

[0150] During implementation, the terminal receiving module is further used to merge the system messages received N times when the system messages received N times correspond to the same SSB number if the SSB is not updated; and / or not merge the system messages received N times if the SSB is updated; wherein N is greater than or equal to 2.

[0151] In implementation, the system message further includes one or a combination of the following parameters:

[0152] General timing advance, timing offset, RAR listening offset.

[0153] In implementation, the terminal determination module is further used to determine the PDCCH listening opportunity, including:

[0154] Determine that the PDCCH listening opportunity is associated with a beam, an SSB and / or a first spatial relationship.

[0155] In implementation, the terminal assumes that the system message is sent only in a PDCCH listening opportunity associated with the beam, the SSB and / or the first spatial relationship;

[0156] And / or, the terminal assumes that the system message is not sent in a PDCCH listening occasion other than a PDCCH listening occasion associated with the beam, the SSB and / or the first spatial relationship.

[0157] A base station, comprising:

[0158] The processor reads the program in the memory and performs the following processes:

[0159] Determine the system messages that need to be sent to the terminal;

[0160] Send system messages on PDCCH;

[0161] A transceiver is used to receive and send data under the control of the processor.

[0162] In implementation, the system message is related to a beam and / or SSB.

[0163] In implementation, the UE does not expect the same values ​​corresponding to the same fields in system messages related to different beams and / or SSBs in the same cell to be the same.

[0164] In implementation, it is determined that the system message is related to the beam and / or SSB by one of the following methods or a combination thereof:

[0165] According to a pre-agreed agreement, confirm that the system message is related to the beam and / or SSB;

[0166] Confirming, according to a first field in SIB-TypeInfo, that the system message is related to a beam and / or an SSB, wherein the first field indicates that the system message is related to a beam and / or an SSB;

[0167] According to the second field in the SIB, it is confirmed that the system message is related to the beam and / or SSB, wherein the second field indicates that the system message is related to the beam and / or SSB.

[0168] According to the third field in the SIB, it is confirmed that the system message is related to the beam and / or SSB, wherein the third field indicates the beam indication or SSB indication corresponding to the system message.

[0169] In implementation, the first field and areaScope in the SIB-TypeInfo cannot simultaneously take the value of true.

[0170] In an implementation, the system message is associated with the first spatial relationship.

[0171] In implementation, the UE does not expect that the values ​​corresponding to the same field in the system messages related to different first spatial relationships in the same cell are the same.

[0172] In implementation, determining that the system message is related to the first spatial relationship is done by one of the following methods or a combination thereof:

[0173] According to the fourth field in the SIB, confirm that the system message is related to the first spatial relationship, wherein the fourth field includes at least one of the following indications or a combination thereof:

[0174] SSB instructions;

[0175] a first reference signal indication;

[0176] TCI indication;

[0177] The first reference signal includes at least one of the following reference signals:

[0178] CSI-RS, TRS, SRS.

[0179] In implementation, the system message includes a fifth field, wherein the fifth field is related to the beam;

[0180] And / or, the fifth field is related to SSB;

[0181] And / or, the fifth field is related to the first spatial relationship.

[0182] During implementation, the UE does not expect that the value corresponding to the fifth field in the system message related to different beams, SSBs, or first spatial relationships in the same cell is the same.

[0183] In an implementation, the fifth field is used to indicate at least one of the following parameters:

[0184] General timing advance, timing offset, RAR listening offset.

[0185] In implementation, the system message further includes one or a combination of the following parameters:

[0186] General timing advance, timing offset, RAR listening offset.

[0187] In implementation, the PDCCH for sending SI includes:

[0188] The PDCCH is associated with a beam, an SSB and / or a first spatial relationship.

[0189] A base station, comprising:

[0190] A base station determination module, used to determine the system message that needs to be sent to the terminal;

[0191] The base station sending module is used to send system messages on the PDCCH.

[0192] In implementation, the system message is related to a beam and / or SSB.

[0193] In implementation, the UE does not expect the same values ​​corresponding to the same fields in system messages related to different beams and / or SSBs in the same cell to be the same.

[0194] In implementation, the base station determination module is further used to determine that the system message is related to the beam and / or SSB by one of the following methods or a combination thereof:

[0195] According to a pre-agreed agreement, confirm that the system message is related to the beam and / or SSB;

[0196] Confirming, according to a first field in SIB-TypeInfo, that the system message is related to a beam and / or an SSB, wherein the first field indicates that the system message is related to a beam and / or an SSB;

[0197] According to the second field in the SIB, it is confirmed that the system message is related to the beam and / or SSB, wherein the second field indicates that the system message is related to the beam and / or SSB.

[0198] According to the third field in the SIB, it is confirmed that the system message is related to the beam and / or SSB, wherein the third field indicates the beam indication or SSB indication corresponding to the system message.

[0199] In implementation, the first field and areaScope in the SIB-TypeInfo cannot simultaneously take the value of true.

[0200] In an implementation, the system message is associated with the first spatial relationship.

[0201] In implementation, the UE does not expect that the values ​​corresponding to the same field in the system messages related to different first spatial relationships in the same cell are the same.

[0202] In implementation, the base station determination module is further used to determine that the system message is related to the first spatial relationship by one of the following methods or a combination thereof:

[0203] According to the fourth field in the SIB, confirm that the system message is related to the first spatial relationship, wherein the fourth field includes at least one of the following indications or a combination thereof:

[0204] SSB instructions;

[0205] a first reference signal indication;

[0206] TCI indication;

[0207] The first reference signal includes at least one of the following reference signals:

[0208] CSI-RS, TRS, SRS.

[0209] In implementation, the system message includes a fifth field, wherein the fifth field is related to the beam;

[0210] And / or, the fifth field is related to SSB;

[0211] And / or, the fifth field is related to the first spatial relationship.

[0212] During implementation, the UE does not expect that the value corresponding to the fifth field in the system message related to different beams, SSBs, or first spatial relationships in the same cell is the same.

[0213] In an implementation, the fifth field is used to indicate at least one of the following parameters:

[0214] General timing advance, timing offset, RAR listening offset.

[0215] In implementation, the system message further includes one or a combination of the following parameters:

[0216] General timing advance, timing offset, RAR listening offset.

[0217] In implementation, the base station sending module is further used to send the PDCCH of SI, including:

[0218] The PDCCH is associated with a beam, an SSB and / or a first spatial relationship.

[0219] A computer-readable storage medium stores a computer program for executing the above-mentioned SI receiving method and / or SI sending method.

[0220] The beneficial effects of the present invention are as follows:

[0221] In the technical solution provided by the embodiment of the present invention, the base station in the NTN system broadcasts SI, and the SI carries parameters related to the beam and / or SSB. Since the base station broadcasts the parameters related to the beam and / or SSB through the system message, that is, different beams in a cell broadcast the same type of SI (such as SIB x), and the values ​​of the same-name fields carried in the system messages (such as SIB x) corresponding to different beams are different, the parameter values ​​are associated with the corresponding beam and / or SSB. It not only solves the problem that when the base station needs to broadcast many beam-related parameters, it can only support the cell-level system message indication method and cannot support the parameter indication under NTN. Furthermore, since the parameters related to the beam and / or SSB are broadcast, the information carried in the SI is better adapted to the coverage area of ​​the beam; the system message overhead is small.

[0222] Furthermore, a system message indication scheme is provided, used to indicate to the terminal that the message carries parameters related to the beam and / or SSB; a receiving scheme is provided, used to enable the UE to know where to receive the system message carrying parameters related to the beam and / or SSB; and a system message merging scheme is provided, used to enable the UE to know which system messages can be merged, etc. BRIEF DESCRIPTION OF THE DRAWINGS

[0223] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0224] Figure 1 A schematic diagram of a satellite network architecture in the background technology;

[0225] Figure 2 is a schematic diagram of a common TA in an embodiment of the present invention;

[0226] Figure 3 Schematic diagram of the timing relationship from UL grant to PUSCH in an embodiment of the present invention;

[0227] Figure 4 Schematic diagram of the implementation flow of the SI receiving method on the terminal side in an embodiment of the present invention;

[0228] Figure 5 Schematic diagram of the implementation flow of the SI sending method on the base station side in an embodiment of the present invention;

[0229] Figure 6 This is a schematic diagram of spot beam coverage in an embodiment of the present invention;

[0230] Figure 7 This is a schematic diagram of the structure of a base station in an embodiment of the present invention;

[0231] Figure 8 Schematic diagram of the terminal structure in an embodiment of the present invention. DETAILED DESCRIPTION

[0232] The inventors noticed during the invention process that:

[0233] The base station needs to broadcast many beam-related parameters, such as common TA (TA: Time Advance), initial K offset (initial K offset), RAR monitoring offset (RAR: Random Access Response), etc. These parameters may have a certain functional relationship, that is, based on one parameter, another parameter may be derived.

[0234] Figure 2 It is a schematic diagram of common TA. As shown in the figure, in the scheme shown in (a), common TA represents the RTD (round trip delay) from the reference point to the satellite; in the scheme shown in (b), common TA represents the sum of the RTD from the reference point to the satellite and the RTD from the satellite to the ground gateway, where the reference point represents a certain location within the coverage range of the beam.

[0235] In some other schemes, common TA may have other definitions, such as (-1)*RTD from the reference point to the satellite.

[0236] No matter how common TA is defined, this parameter is related to the reference point within the coverage of the beam and is therefore a property of the beam, i.e. common TA is a beam-specific parameter.

[0237] K offset represents the timing offset.

[0238] In the existing solutions provided for terrestrial networks, some timing relationships are explicitly indicated in the DCI (Downlink Control Information) field, including:

[0239] K1: The time slot offset between PDSCH (Physical downlink shared channel) and HARQ-ACK (HARQ confirmation; HARQ: Hybrid automatic repeat request) feedback. The value range of K1 is 0,…,15;

[0240] K2: The time slot offset between UL grant DCI (uplink authorization DCI) and the scheduled PUSCH (Physical Uplink Shared Channel). The value range of K2 is 0,…,32.

[0241] In the NTN scenario, considering the large delay between the satellite and the ground, the value ranges of many timing parameters (such as K1 and K2) in the current solution are no longer sufficient.

[0242] For example, K1 is used to indicate the time slot offset between PDSCH and HARQ feedback. Assume that the base station schedules PDSCH in time slot n through DCI. The ground UE (User Equipment) is in time slot n+τ delay The PDSCH sent by the base station can be received at delay Represents the propagation delay between the satellite and the ground. For GEO (Geosynchronous Earth Orbit), τ delay ≥120ms. Without considering the decoding delay and TA processing on the UE side, assume that the UE sends HARQ-ACK feedback immediately after receiving the PDSCH. The HARQ-ACK also needs to propagate τ delay This means that it takes at least 2τ from the time the base station sends the PDSCH to the time the base station receives the HARQ-ACK feedback from the UE. delay For GEO, the time interval is at least 240ms. Considering a 30kHz subcarrier spacing, each slot lasts 0.5ms, so a 240ms time interval corresponds to 480 slots. Obviously, 480 is far beyond the parameter value range of K1 in the existing solution.

[0243] To solve the above problems, NTN's solution is: instead of modifying the existing value range of K1 or K2 in the existing solution, a new parameter is introduced: the timing offset K offset . At this time:

[0244] The time slot offset between PDSCH and HARQ-ACK feedback = K offset +K1;

[0245] The time slot offset between UL grant DCI and scheduled PUSCH = K offset +K2.

[0246] Figure 3 This is a schematic diagram of the timing relationship from UL grant to PUSCH. As shown in the figure, K offset, should be greater than or equal to RTD (i.e., 2 times the propagation delay, or TA).

[0247] If K offset < RTD and K2 = 0, then the UE receives a UL grant at time t1 (absolute time), indicating that it should send a PUSCH at t1 + K offset + K2 - TA < t1 + K2 (note K2 = 0) = t1. Obviously, this is physically impossible to achieve.

[0248] If K offset = RTD, then the UE receives a UL grant at time t1 (absolute time), indicating that it should send a PUSCH at t1 + K offset + K2 - TA = t1 + K2. That is, the same scheduling flexibility as the terrestrial network is obtained. Therefore, K offset = RTD is the optimal case.

[0249] If K offset > RTD, then the UE receives a UL grant at time t1 (absolute time), indicating that it should send a PUSCH at t1 + K offset + K2 - TA > t1 + K2. The larger the difference between K offset – RTD, the greater the uplink transmission delay of the UE. Therefore, the scheduling timeliness (timeliness) of the UE will be reduced, and the throughput of the UE will also be reduced.

[0250] The inventors noticed that in the 4-step random access process, Msg 2 (RAR) schedules Msg 3 (carried in the PUSCH). Similar to the UL grant, K offset is also required in the scheduling timing from Msg 2 to Msg 3 to adapt to the extremely large RTD in the NTN network.

[0251] There is a solution in NTN that studies the UE with GNSS (Global Navigation Satellite System) positioning or timing capabilities, which can calculate and compensate for TA by itself when sending Msg 1. That is, the UE autonomously calculates TA and sends a PRACH (Physical Random Access Channel). In this scenario, when the UE sends Msg 1, it knows what the RTD from itself to the satellite is. However, when the satellite (or base station) receives the PRACH sent by the UE, it cannot know the RTD from this UE to itself.

[0252] Since the base station side lacks the RTD information of the UE when sending Msg 2, it is impossible to accurately determine K offsetParameters. Note that the above analysis shows that K offset To ensure that the NTN system can work, there is a proposal that the base station broadcasts initial K through system messages. offset value, and initial K offset Greater than the RTD of all UEs within the coverage area.

[0253] The inventors noticed that the larger the coverage area, the greater the difference in RTD of each UE, resulting in the K determined based on the maximum RTD. offset The greater the difference from the actual RTD of each UE.

[0254] Considering that for mode 2 (each satellite generates multiple cells, each cell includes only one spot beam), each cell includes multiple beams, so K determined based on the cell coverage radius offset The value will be much larger than K determined based on beam offset value, and the latter is more consistent with the RTD of the UE.

[0255] Based on the above considerations, K offset The parameter value is preferably related to the beam, that is, K offset is a beam-specific parameter. In this case, the beam-dependent K is determined based on the maximum RTD within the coverage radius of each beam. offset Get the value.

[0256] RAR monitoring offset means that after UE sends Msg 1, it waits for RAR monitoring offset time before listening to RAR signal, so as to save unnecessary listening processing overhead and energy consumption. The inventors noticed that RAR monitoring offset is strongly related to RTD, so it is better to be a beam-specific parameter.

[0257] In summary, it is necessary to broadcast beam specific parameters in the NTN system.

[0258] Currently, there are two ways to broadcast beam-specific system messages:

[0259] 1. Cell specific SI based (based on cell-specific SI; SI: System Information) beam specific (beam-specific) information indication:

[0260] All beams in a cell broadcast the same SI, and the SI carries the indication information of all beams.

[0261] This solution has large SI signaling overhead.

[0262] 2. Beam specific SI indication:

[0263] Considering that in the NTN point beam application scenario, each user is served by only one beam and can see 2 to 3 beams at most, and there is natural spatial separation between the beams, it is possible to consider sending dedicated SI information for each beam, and the UE does not need to know the dedicated SI information of other beams.

[0264] That is, different beams in a cell broadcast the same type of SI (such as SIB (System Information Block) x), and the values ​​of the same-name fields carried in the system messages corresponding to different beams (such as SIB x) are different, and their parameter values ​​are associated with the corresponding beams.

[0265] The inventors note that the above system message (SI) may be SIB1, or other system messages (Other SI) except SIB1.

[0266] This solution has low system message overhead, and the information carried in SI is best adapted to the coverage area of ​​beam.

[0267] However, the existing technology currently only supports the cell-level system message indication method. Based on this, an indication scheme supporting beam-specific system messages is proposed in an embodiment of the present invention, which can better adapt to the beam coverage area and reduce SI information carrying overhead.

[0268] The specific implementation of the present invention will be described below in conjunction with the accompanying drawings.

[0269] In the description process, the implementation on the UE and base station sides will be described respectively, and then an example of the coordinated implementation of the two will be given to better understand the implementation of the solution given in the embodiment of the present invention. This description does not mean that the two must be implemented in coordination or must be implemented separately. In fact, when the UE and the base station are implemented separately, they also solve the problems on the UE side and the base station side respectively, and when the two are used in combination, better technical effects will be obtained.

[0270] The scheme used as an example in the embodiment of the present invention is satellite communication. In fact, the application scenario of this scheme is not limited to satellite communication systems. In addition to the field of satellite communication, this scheme may also be applied to scenarios that require wide area coverage, such as HAPS (High Altitude Platform Station), ATG (air to ground), or ground base stations. Satellite communication is used as an example in the implementation because it is relatively typical, so satellite communication is used as an example here; however, as long as the timing parameters have insufficient system message indications at the cell level due to the existence of large delays, it can be used. Satellite communication is only used to teach technicians in this field how to implement the present invention specifically, but it does not mean that it can only be used for satellite communication. During the implementation process, the communication environment required for the application can be determined in combination with practical needs.

[0271] Figure 4 A schematic diagram of a flow chart for implementing a method for receiving SI on the terminal side, as shown in the figure, may include:

[0272] Step 401: Determine a PDCCH listening opportunity;

[0273] Step 402: Receive a system message according to the determined PDCCH listening opportunity.

[0274] Figure 5 The schematic diagram of the implementation flow of the SI sending method on the base station side, as shown in the figure, may include:

[0275] Step 501: The base station determines a system message that needs to be sent to the terminal;

[0276] Step 502: Send a system message on the PDCCH.

[0277] In implementation, the system message is related to the beam and / or synchronization signal block SSB (Synchronization Signal / Physical Broadcast Channel Signal Block (or Synchronization Signal Block), Synchronization Signal and PBCH block).

[0278] That is, the terminal receives the system message SI broadcast by the base station in the NTN system according to the determined PDCCH (Physical downlink control channel) listening opportunity, and the SI is related to the beam and / or synchronization signal block SSB.

[0279] The system message is related to the beam and / or SSB means that the system message carries (or is used to indicate) parameters related to the beam and / or SSB. The parameters related to the beam and / or SSB mean that these parameters are related to a specific spatial range. The spatial range can be characterized by a beam, SSB, or some RS (reference signal), such as CSI-RS (channel state information reference signal) and TRS (tracking reference signal).

[0280] In implementation, the UE does not expect the same values ​​corresponding to the same fields in system messages related to different beams and / or SSBs in the same cell to be the same.

[0281] That is, the UE understands (or the UE assumes) that the values ​​corresponding to the same fields in system messages related to different beams and / or SSBs in the same cell may be the same or different, that is, the same field names in system messages related to different beams and / or SSBs correspond to the same or different parameter values.

[0282] The UE does not consider (or assumes) that the values ​​corresponding to the same fields in system messages related to different beams and / or SSBs in the same cell must be the same.

[0283] In implementation, for the terminal, it can be determined that the system message is related to the beam and / or SSB in one of the following ways or a combination thereof:

[0284] According to a pre-agreed agreement, confirm that the system message is related to the beam and / or SSB;

[0285] Confirming, according to a first field in SIB-TypeInfo, that the system message is related to a beam and / or an SSB, wherein the first field indicates that the system message is related to a beam and / or an SSB;

[0286] Confirming, according to a second field in the SIB, that the system message is related to the beam and / or the SSB, wherein the second field indicates that the system message is related to the beam and / or the SSB;

[0287] According to the third field in the SIB, it is confirmed that the system message is related to the beam and / or SSB, wherein the third field indicates the beam indication or SSB indication corresponding to the system message.

[0288] In implementation, for a base station, it may be determined that the system message is related to a beam and / or SSB in one of the following ways or a combination thereof:

[0289] According to a pre-agreed agreement, confirm that the system message is related to the beam and / or SSB;

[0290] Confirming, according to a first field in SIB-TypeInfo, that the system message is related to a beam and / or an SSB, wherein the first field indicates that the system message is related to a beam and / or an SSB;

[0291] According to the second field in the SIB, it is confirmed that the system message is related to the beam and / or SSB, wherein the second field indicates that the system message is related to the beam and / or SSB.

[0292] According to the third field in the SIB, it is confirmed that the system message is related to the beam and / or SSB, wherein the third field indicates the beam indication or SSB indication corresponding to the system message.

[0293] In a specific implementation, the first field and areaScope in the SIB-TypeInfo cannot simultaneously take the value of true.

[0294] In specific implementation:

[0295] Method 1: According to a pre-agreed agreement, confirm that the system message is related to the beam and / or SSB.

[0296] In the embodiment, the system message is related to the beam and / or SSB. For ease of understanding and explanation, the system message is also referred to as a beam and / or SSB-specific system message in the embodiment.

[0297] For example, a new system message type is agreed upon in the protocol, and this system message type is related to the beam and / or SSB.

[0298] Alternatively, it is agreed in the protocol that existing system messages (such as SIB1, SIB2, ...) are related to beams and / or SSBs in specific scenarios (such as NTN, satellite-to-ground communication, HAPS, ATG or ground base station wide coverage scenarios).

[0299] Method 2: Confirm that the system message is related to the beam and / or SSB, wherein the first field indicates that the system message is related to the beam and / or SSB.

[0300] For example, in the existing protocol, the SI-SchedulingInfo IE (SI scheduling information element; IE: Information Element) contains a SchedulingInfo list (schedulingInfoList), and each SchedulingInfo represents an SI window. The SchedulingInfo IE includes a sib-MappingInfo (SIB mapping information) field. The type of sib-MappingInfo is SIB-Mapping (SIB mapping). SIB-Mapping contains a series of SIB-TypeInfo (SIB type information) types, which are used to represent the SIB information contained in the corresponding SI window. The SIB-TypeInfo type includes a field type for indicating the SIB name, a SIB value flag valueTag, and an area flag areaScope. As shown in the following table:

[0301]

[0302]

[0303]

[0304] In a specific implementation, a new field may be added to the SIB-TypeInfo IE to indicate that the system message is related to the beam and / or SSB.

[0305] As shown in the following table, one implementation may be that the first field is optional, and its value range is the enumeration variable true. When the first field exists, it indicates that the SIB information shown is related to the beam and / or SSB. Otherwise, when the first field does not exist, it indicates that the SIB information shown is not related to the beam and / or SSB.

[0306]

[0307] As shown in the following table, another implementation method may be that the first field always exists, and its value range is an enumeration variable {true, false}. When the value of the first field is true, it indicates that the SIB information shown is related to the beam and / or SSB. Otherwise, when the value of the first field is false, it indicates that the SIB information shown is not related to the beam and / or SSB.

[0308]

[0309] Method 3: Confirm that the system message is related to the beam and / or SSB according to the second field in the SIB field, wherein the second field indicates that the system message is related to the beam and / or SSB.

[0310] A second field is added to the SIB x field to indicate that the system message is related to the beam and / or SSB, where x=1, 2, 3, ... That is, a new field is added to the existing SIB1, SIB2, ..., or to the newly added SIB type to indicate that the system message is related to the beam and / or SSB.

[0311] As shown in the following table, a possible implementation is that the second field is optional, and its value range is the enumeration variable true. When the second field exists, it indicates that the SIB information shown is related to the beam and / or SSB.

[0312] Otherwise, when the second field does not exist, it indicates that the SIB information shown is not related to the beam and / or SSB.

[0313]

[0314] As shown in the following table, another possible implementation is that the second field always exists, and its value range is the enumeration variable {true, false}. When the value of the second field is true, it indicates that the SIB information shown is beam and / or SSB related. Otherwise, when the value of the second field is false, it indicates that the SIB information shown is not beam and / or SSB related.

[0315]

[0316] Method 4: Confirm that the system message is a beam and / or SSB-specific system message according to the third field in the SIB field, wherein the third field indicates the beam number or SSB number corresponding to the system message.

[0317] A third field is added to the SIB x field to indicate the beam and / or SSB number corresponding to the system message, where x = 1, 2, 3, ... That is, a new field is added to the existing SIB1, SIB2, ..., or to the newly added SIB type to indicate the beam and / or SSB number corresponding to the system message.

[0318] The third field may always exist or may be an optional field.

[0319] As shown in the following table, a possible implementation is that the third field type is SSB-index (SSB index).

[0320]

[0321] Another possible implementation is that the third field type is a beam number or a CSI-RS-Index (CSI-RS index; CSI-RS: channel state information reference signal, channel state information reference signal).

[0322] In implementation, the first field and the area scope areaScope in the SIB-TypeInfo cannot simultaneously take the value of true.

[0323] Specifically, according to the first field in SIB-TypeInfo, confirm that the system message is a beam and / or SSB-specific system message, wherein the first field indicates that the system message is a beam and / or SSB-specific system message, and the first field and areaScope cannot simultaneously take the value of true.

[0324] That is, in the above-mentioned method 2, the inventor noticed that the first field indicates that the system message is related to the beam and / or SSB, and the areaScope field indicates that the system message is area specific, that is, multiple cells in an area use the same system message, so the two fields cannot be valid at the same time, that is, both cannot take the true value at the same time.

[0325] In an implementation, the system message is associated with the first spatial relationship.

[0326] That is, the system message is related to a specific spatial range, or the system message carries (or is used to indicate) parameters related to a specific spatial range.

[0327] In a specific implementation, the UE does not expect that the values ​​corresponding to the same field in the system messages related to different first spatial relationships in the same cell are the same.

[0328] That is, the UE understands (or the UE assumes) that the values ​​corresponding to the same field in system messages related to different spatial relationships in the same cell may be the same or different, that is, the same field name in system messages related to different spatial relationships corresponds to the same or different parameter values.

[0329] The UE will not think (or the UE will not assume) that the values ​​corresponding to the same field in the system messages related to different spatial relationships in the same cell must be the same.

[0330] In implementation, for the terminal side, it can be determined that the system message is related to the first spatial relationship in one of the following ways or a combination thereof:

[0331] Confirming, according to a fourth field in a system information block SIB, that the system message is related to the first spatial relationship, wherein the fourth field includes at least one of the following indications or a combination thereof:

[0332] SSB instructions;

[0333] a first reference signal indication;

[0334] Transmission Configuration Indicator (TCI) indication;

[0335] The first reference signal includes at least one of the following reference signals:

[0336] Channel state reference information CSI-RS (Channel-state information reference signal), tracking reference signal TRS (tracking reference signal), sounding reference signal SRS (Sounding reference signal).

[0337] For the base station side, it can be determined that the system message is related to the first spatial relationship in one of the following ways or a combination thereof:

[0338] According to the fourth field in the SIB, confirm that the system message is related to the first spatial relationship, wherein the fourth field includes at least one of the following indications or a combination thereof:

[0339] SSB instructions;

[0340] a first reference signal indication;

[0341] TCI indication;

[0342] The first reference signal includes at least one of the following reference signals:

[0343] CSI-RS, TRS, SRS.

[0344] That is, the first spatial relationship is characterized by a beam, an SSB, a reference signal, and / or a TCI. Specifically, the SIB includes a fourth field, the fourth field is used to indicate the first spatial relationship, and the fourth field includes at least one of the following indications or a combination thereof: an SSB indication, a reference signal indication, a TCI indication, etc. Among them, the reference signal used to indicate the first spatial relationship includes: CSI-RS, TRS, SRS, etc.

[0345] In implementation, the system message includes a fifth field, wherein:

[0346] The fifth field is related to the beam;

[0347] And / or, the fifth field is related to SSB;

[0348] And / or, the fifth field is related to the first spatial relationship.

[0349] That is, the system message includes a fifth field related to the beam and / or SSB. According to the fifth field related to the beam and / or SSB and / or the first spatial relationship included in the system message, it is determined that the system message is related to the beam and / or SSB and / or the first spatial relationship.

[0350] Method 5: According to a pre-agreed agreement, confirm that some fields in the system message are related to the beam and / or SSB and / or the first spatial relationship.

[0351] For example, it can be agreed in the protocol that if some given fields exist in existing system messages (such as SIB1, SIB2, ...) or newly added system messages, these system messages are related to the beam and / or SSB and / or the first spatial relationship.

[0352] For example, if the UE finds that the fifth field exists in SIBx (x=1, 2, . . . ), it determines that the fifth field is related to the beam and / or SSB and / or the first spatial relationship.

[0353] In a possible implementation, the fifth field may include at least one of a common timing advance (common TA), a timing offset (K_offset), and a RAR monitoring offset (RAR monitoring offset).

[0354] That is, according to the pre-agreed agreement, the UE determines that the common timing advance (common TA), the timing offset (K_offset), and the RAR monitoring offset (RAR monitoring offset) are related to the beam and / or SSB and / or the first spatial relationship. When the system message includes at least one of the above parameters, it is determined that the system message is also related to the beam and / or SSB and / or the first spatial relationship. Among them, the fifth field is any one of the above parameters related to the beam and / or SSB and / or the first spatial relationship.

[0355] During implementation, the UE does not expect that the value corresponding to the fifth field in the system message related to different beams, SSBs, or first spatial relationships in the same cell is the same.

[0356] That is, the UE understands (or the UE assumes) that the value corresponding to the fifth field in the system message related to different beams, SSBs, or first spatial relationships in the same cell may be the same or different, that is, the fifth field name in the system message related to different beams, SSBs, or first spatial relationships corresponds to the same or different parameter values.

[0357] The UE will not think (or the UE will not assume) that the value corresponding to the fifth field in the system message related to different beams, SSBs, or first spatial relationships in the same cell must be the same.

[0358] During implementation, when the system message includes a beam indication, when the beam indications corresponding to the system messages received N times are the same, the system messages received N times are merged; and / or, if the beam indications corresponding to the system messages received N times are different, the system messages received N times are not merged; wherein N is greater than or equal to 2.

[0359] Specifically, the following explanation is given by taking the third field in the SIB field as an example to indicate the beam number corresponding to the system message.

[0360] In a specific implementation, when the third field in the SIB field is used to indicate the beam number corresponding to the system message, when the beam numbers corresponding to the system messages received N times are the same, the system messages received N times are merged; and / or, if the beam numbers corresponding to the system messages received N times are different, the system messages received N times are not merged; wherein N is greater than or equal to 2.

[0361] Specifically, the system message carries fields related to the beam and / or SSB. When the third field in the SIB field is used to indicate the beam number corresponding to the system message:

[0362] The UE may merge the system messages received N times only when the beam numbers corresponding to the system messages received N times are the same;

[0363] And / or, if the beam numbers corresponding to the system messages received N times are different, the UE cannot combine the system messages received N times;

[0364] Wherein, N is greater than or equal to 2.

[0365] When the third field in the SIB field is used to indicate the beam number corresponding to the system message, the same beam number corresponding to the system messages received N times is a prerequisite for merging system messages, but not a sufficient condition. That is, at least when the beam numbers corresponding to the system messages received N times are the same, the UE may merge the system messages received N times. Other conditions may also include at least one of the following:

[0366] The cell ID, area ID, and value tag are the same.

[0367] When the beam numbers corresponding to the system messages received N times are different, the system messages received N times are not combined.

[0368] In implementation, when the system messages received N times correspond to the same SSB number,

[0369] If the SSB is not updated, merging the system messages received N times;

[0370] and / or, if the SSB is updated, the system messages received N times are not merged;

[0371] Wherein, N is greater than or equal to 2.

[0372] Specifically, the following is explained by taking the third field in the SIB field as an example to indicate the SSB number corresponding to the system message.

[0373] In a specific implementation, when the third field in the SIB field is used to indicate the SSB number corresponding to the system message, when the system messages received N times correspond to the same SSB number, if the SSB is not updated, the system messages received N times are merged; and / or, if the SSB is updated, the system messages received N times are not merged; wherein N is greater than or equal to 2.

[0374] Figure 6 This is a schematic diagram of spot beam coverage. As shown in the figure, different spot beams of the same satellite may use the same SSB number. Therefore, even if the SSB is the same, if the UE moves to a different spot beam coverage, the beam-related system message values ​​carried in the same system message type are different, so the UE cannot merge.

[0375] Therefore, when the UE's SSB is not updated, it means that the UE is still within the coverage of the same spot beam, and the UE can merge the received system messages; however, when the UE leaves the currently covered spot beam (that is, the SSB changes), even if the SSB number corresponding to the newly received system message is the same as the SSB number corresponding to the previously received system message, the UE cannot merge the multiple received system messages because the beam has changed.

[0376] In addition, as in the above point 1, the fact that the SSB has not changed is only a necessary condition for the system message merging, but not a sufficient condition. Other conditions may also include at least one of the following:

[0377] The cell ID, area ID, and value tag are the same.

[0378] Similarly, if the beams and / or SSBs corresponding to the system messages received N times are updated, the system messages received N times cannot be combined.

[0379] In implementation, the system message further includes one or a combination of the following parameters:

[0380] General timing advance, timing offset, RAR listening offset.

[0381] Specifically, the general timing advance, timing offset, and RAR listening offset are all beam-related parameters, specifically, they are all related to the RTD from the beam center to the satellite, or the sum of the RTD from the beam center to the satellite and the RTD from the satellite to the ground gateway. Therefore, in order to better adapt to the beam space characteristics and reduce the signaling indication overhead, the above beam-related parameters can be indicated through beam-related system messages.

[0382] During implementation, it is determined that the PDCCH listening opportunity is associated with the beam, SSB and / or the first spatial relationship.

[0383] In implementation, the terminal assumes that the system message is sent only in a PDCCH listening opportunity associated with the beam, the SSB and / or the first spatial relationship;

[0384] And / or, the terminal assumes that the system message is not sent in a PDCCH listening occasion other than a PDCCH listening occasion associated with the beam, the SSB and / or the first spatial relationship.

[0385] That is, the UE determines that the system message is only sent in the PDCCH listening opportunity associated with the beam, SSB and / or the first spatial relationship.

[0386] Specifically, the UE determines the PDCCH listening occasions associated with the beam and / or SSB and / or the first spatial relationship, and listens to the system messages related to the beam and / or SSB and / or the first spatial relationship only in these determined PDCCH listening occasions.

[0387] Specifically, the terminal determines the PDCCH listening opportunity by sending the beam and / or SSB-specific system message only in the PDCCH listening opportunity associated with the beam and / or SSB;

[0388] And / or, the terminal determines the PDCCH listening timing according to the fact that the beam and / or SSB-specific system message is not sent in a PDCCH listening timing other than the PDCCH listening timing associated with the beam and / or SSB.

[0389] Specifically, determining the PDCCH listening opportunity may further include:

[0390] The terminal assumes that the beam and / or SSB-specific system message is only sent in a PDCCH listening opportunity associated with the beam and / or SSB;

[0391] And / or, the terminal assumes that the beam and / or SSB-specific system message is not sent in a PDCCH listening occasion other than a PDCCH listening occasion associated with the beam and / or SSB.

[0392] Specifically, system messages related to beams and / or SSBs and / or the first spatial relationship may be carried by SIB1, or by other system messages (Other SI) other than SIB1.

[0393] In a specific implementation, if the beam specific SI is carried by SIB1, the PDCCH monitoring timing of SIB1 and the terminal monitoring behavior thereof are determined according to the prior art.

[0394] If the beam specific SI is carried by other system messages (Other SI) other than SIB1, the beam specific SI reception mode is determined according to the following method:

[0395] In a specific implementation, the UE may determine all possible PDCCH listening opportunities according to the prior art, including:

[0396] 1. Determine SI windows according to the prior art;

[0397] 2. Search space according to existing technology (searchSpace);

[0398] 3. Determine all PDCCH listening opportunities according to the prior art:

[0399] For SI message acquisition PDCCH monitoring occasion(s)are determinedaccording to searchSpaceOtherSystemInformation.If searchSpaceOtherSystemInformation is set to zero,PDCCH monitoring occasions for SI message reception inSI-window are same as PDCCH monitoring occasions for SIB1 where the mappingbetween PDCCH monitoring occasions and SSBs is specified in TS 38.213

[13] .If searchSpaceOtherSystemInformation is not set to zero,PDCCH monitoringoccasions for SI message are determined based on search space indicated by searchSpaceOtherSystemInformation.PDCCH monitoring occasions for SI messagewhich are not overlapping with UL symbols(determined according to tdd-UL-DL-ConfigurationCommon)are sequentially numbered from one in the SI window. (For SI message acquisition, the PDCCH listening opportunity is determined according to the searchSpaceOtherSystemInformation field. If searchSpaceOtherSystemInformation is set to zero, the PDCCH listening opportunity for receiving SI messages in the SI window is the same as the PDCCH listening opportunity for SIB1, where the mapping between PDCCH monitoring opportunities and SSBs is specified in TS 38.213.If searchSpaceOtherSystemInformation is not zero, the PDCCH listening timing of the SI message is determined according to the search space indicated by searchSpaceOtherSystemInformation. The PDCCH listening timing of the SI message that does not overlap with the UL symbol (determined jointly according to the TDD UL DL configuration) is numbered sequentially in the SI window. ).

[0400] 1. Determine the PDCCH monitoring occasion associated with SSB according to the prior art:

[0401] The [x×N+K]th PDCCH monitoring occasion(s) for SI message in SI-window corresponds to the Kth transmitted SSB, where x=0,1,...X-1,K=1,2,…N,N is the number of actual transmitted SSBs determined according to ssb-PositionsInBurst in SIB1 and X is equal to CEIL(number of PDCCH monitoringoccasions in SI-window / N).(The [x×N+K]th PDCCH monitoring occasion(s) for SI message in SI-window corresponds to the Kth transmitted SSB, where x=0,1,...x-1,K=1,2,…N,N is the number of actual transmitted SSBs determined according to ssb-PositionsInBurst in SIB1, and x is equal to CEIL(number of PDCCH monitoringoccasions in SI-window / N).)

[0402] 2. Adjust the UE behavior so that the UE only listens to the beamspecific SI in the PDCCH monitoring occasion associated with the SSB.

[0403] Add the following description to the agreement:

[0404] The UE assumes that, in the SI window, PDCCH for an beam specific SI message is transmitted in at least one PDCCH monitoring occasion corresponding to each transmitted SSB, and it is not transmitted in a PDCCH monitoring occasion corresponding to SSBs other than the transmitted one. (The UE assumes that, in the SI window, the PDCCH corresponding to the beam-related SI message is transmitted in at least one PDCCH monitoring occasion corresponding to each transmitted SSB, and the SI message is not transmitted in the PDCCH monitoring occasion corresponding to other transmitted SSBs.)

[0405] In the above embodiments, the prior art can at least implement the above solution according to the technology specified in 3GPP Release 16 and its previous protocol versions.

[0406] In implementation, the UE receives system messages only in a PDCCH monitoring occasion associated with a transmitted beam or SSB, and it is assumed that the terminal assumes that the beam and / or SSB-specific system messages are only sent in a PDCCH monitoring occasion associated with the beam and / or SSB; and / or the terminal assumes that the beam and / or SSB-specific system messages are not sent in a PDCCH monitoring occasion other than the PDCCH monitoring occasion associated with the beam and / or SSB.

[0407] Based on the same inventive concept, an embodiment of the present invention also provides a base station, a terminal, and a computer-readable storage medium long-term evolution multi-carrier upgrade system. Since the principles of solving the problems by these devices are similar to those of the SI receiving method and the SI sending method, the implementation of these devices can refer to the implementation of the method, and the repeated parts will not be repeated.

[0408] When implementing the technical solution provided by the embodiment of the present invention, it can be implemented as follows.

[0409] Figure 7 The following is a schematic diagram of the base station structure. As shown in the figure, the base station includes:

[0410] The processor 700 is used to read the program in the memory 720 and execute the following process:

[0411] Determine the system messages that need to be sent to the terminal;

[0412] Send system messages on PDCCH;

[0413] The transceiver 710 is configured to receive and send data under the control of the processor 700 .

[0414] In implementation, the system message is related to a beam and / or SSB.

[0415] In implementation, the UE does not expect the same values ​​corresponding to the same fields in system messages related to different beams and / or SSBs in the same cell to be the same.

[0416] In implementation, it is determined that the system message is related to the beam and / or SSB by one of the following methods or a combination thereof:

[0417] According to a pre-agreed agreement, confirm that the system message is related to the beam and / or SSB;

[0418] Confirming, according to a first field in SIB-TypeInfo, that the system message is related to a beam and / or an SSB, wherein the first field indicates that the system message is related to a beam and / or an SSB;

[0419] According to the second field in the SIB, it is confirmed that the system message is related to the beam and / or SSB, wherein the second field indicates that the system message is related to the beam and / or SSB.

[0420] According to the third field in the SIB, it is confirmed that the system message is related to the beam and / or SSB, wherein the third field indicates the beam indication or SSB indication corresponding to the system message.

[0421] In implementation, the first field and areaScope in the SIB-TypeInfo cannot simultaneously take the value of true.

[0422] In an implementation, the system message is associated with the first spatial relationship.

[0423] In implementation, the UE does not expect that the values ​​corresponding to the same field in the system messages related to different first spatial relationships in the same cell are the same.

[0424] In implementation, determining that the system message is related to the first spatial relationship is done by one of the following methods or a combination thereof:

[0425] According to the fourth field in the SIB, confirm that the system message is related to the first spatial relationship, wherein the fourth field includes at least one of the following indications or a combination thereof:

[0426] SSB instructions;

[0427] a first reference signal indication;

[0428] TCI indication;

[0429] The first reference signal includes at least one of the following reference signals:

[0430] CSI-RS, TRS, SRS.

[0431] In implementation, the system message includes a fifth field, wherein the fifth field is related to the beam;

[0432] And / or, the fifth field is related to SSB;

[0433] And / or, the fifth field is related to the first spatial relationship.

[0434] During implementation, the UE does not expect that the value corresponding to the fifth field in the system message related to different beams, SSBs, or first spatial relationships in the same cell is the same.

[0435] In an implementation, the fifth field is used to indicate at least one of the following parameters:

[0436] General timing advance, timing offset, RAR listening offset.

[0437] In implementation, the system message further includes one or a combination of the following parameters:

[0438] General timing advance, timing offset, RAR listening offset.

[0439] In implementation, the PDCCH for sending SI includes:

[0440] The PDCCH is associated with a beam, an SSB and / or a first spatial relationship.

[0441] Among them, Figure 7 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 700 and memory represented by memory 720. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 710 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium. The processor 700 is responsible for managing the bus architecture and general processing, and the memory 720 may store data used by the processor 700 when performing operations.

[0442] An embodiment of the present invention further provides a base station, including:

[0443] A base station determination module, used to determine the system message that needs to be sent to the terminal;

[0444] The base station sending module is used to send system messages on the PDCCH.

[0445] In implementation, the system message is related to a beam and / or SSB.

[0446] In implementation, the UE does not expect the same values ​​corresponding to the same fields in system messages related to different beams and / or SSBs in the same cell to be the same.

[0447] In implementation, the base station determination module is further used to determine that the system message is related to the beam and / or SSB by one of the following methods or a combination thereof:

[0448] According to a pre-agreed agreement, confirm that the system message is related to the beam and / or SSB;

[0449] Confirming, according to a first field in SIB-TypeInfo, that the system message is related to a beam and / or an SSB, wherein the first field indicates that the system message is related to a beam and / or an SSB;

[0450] According to the second field in the SIB, it is confirmed that the system message is related to the beam and / or SSB, wherein the second field indicates that the system message is related to the beam and / or SSB.

[0451] According to the third field in the SIB, it is confirmed that the system message is related to the beam and / or SSB, wherein the third field indicates the beam indication or SSB indication corresponding to the system message.

[0452] In implementation, the first field and areaScope in the SIB-TypeInfo cannot simultaneously take the value of true.

[0453] In an implementation, the system message is associated with the first spatial relationship.

[0454] In implementation, the UE does not expect that the values ​​corresponding to the same field in the system messages related to different first spatial relationships in the same cell are the same.

[0455] In implementation, the base station determination module is further used to determine that the system message is related to the first spatial relationship by one of the following methods or a combination thereof:

[0456] According to the fourth field in the SIB, confirm that the system message is related to the first spatial relationship, wherein the fourth field includes at least one of the following indications or a combination thereof:

[0457] SSB instructions;

[0458] a first reference signal indication;

[0459] TCI indication;

[0460] The first reference signal includes at least one of the following reference signals:

[0461] CSI-RS, TRS, SRS.

[0462] In implementation, the system message includes a fifth field, wherein the fifth field is related to the beam;

[0463] And / or, the fifth field is related to SSB;

[0464] And / or, the fifth field is related to the first spatial relationship.

[0465] During implementation, the UE does not expect that the value corresponding to the fifth field in the system message related to different beams, SSBs, or first spatial relationships in the same cell is the same.

[0466] In an implementation, the fifth field is used to indicate at least one of the following parameters:

[0467] General timing advance, timing offset, RAR listening offset.

[0468] In implementation, the system message further includes one or a combination of the following parameters:

[0469] General timing advance, timing offset, RAR listening offset.

[0470] In implementation, the base station sending module is further used to send the PDCCH of SI, including:

[0471] The PDCCH is associated with a beam, an SSB and / or a first spatial relationship.

[0472] For the convenience of description, the various parts of the above-mentioned device are divided into various modules or units according to their functions and described separately. Of course, when implementing the present invention, the functions of each module or unit can be implemented in the same or multiple software or hardware.

[0473] Figure 8 The terminal structure diagram is shown in the figure. As shown in the figure, the terminal includes:

[0474] The processor 800 is used to read the program in the memory 820 and execute the following process:

[0475] Determine the PDCCH listening opportunity;

[0476] Receive system messages according to the determined PDCCH listening opportunity;

[0477] The transceiver 810 is configured to receive and send data under the control of the processor 800 .

[0478] In implementation, the system message is related to a beam and / or SSB.

[0479] In implementation, the UE does not expect the same values ​​corresponding to the same fields in system messages related to different beams and / or SSBs in the same cell to be the same.

[0480] In implementation, it is determined that the system message is related to the beam and / or SSB by one of the following methods or a combination thereof:

[0481] According to a pre-agreed agreement, confirm that the system message is related to the beam and / or SSB;

[0482] Confirming, according to a first field in SIB-TypeInfo, that the system message is related to a beam and / or an SSB, wherein the first field indicates that the system message is related to a beam and / or an SSB;

[0483] Confirming, according to a second field in the SIB, that the system message is related to the beam and / or the SSB, wherein the second field indicates that the system message is related to the beam and / or the SSB;

[0484] According to the third field in the SIB, it is confirmed that the system message is related to the beam and / or SSB, wherein the third field indicates the beam indication or SSB indication corresponding to the system message.

[0485] In implementation, the first field and areaScope in the SIB-TypeInfo cannot simultaneously take the value of true.

[0486] In an implementation, the system message is associated with the first spatial relationship.

[0487] In implementation, the UE does not expect that the values ​​corresponding to the same field in the system messages related to different first spatial relationships in the same cell are the same.

[0488] In implementation, determining that the system message is related to the first spatial relationship is done by one of the following methods or a combination thereof:

[0489] According to the fourth field in the SIB, confirm that the system message is related to the first spatial relationship, wherein the fourth field includes at least one of the following indications or a combination thereof:

[0490] SSB instructions;

[0491] a first reference signal indication;

[0492] TCI indication;

[0493] The first reference signal includes at least one of the following reference signals:

[0494] CSI-RS, TRS, SRS.

[0495] In implementation, the system message includes a fifth field, wherein:

[0496] The fifth field is related to the beam;

[0497] And / or, the fifth field is related to SSB;

[0498] And / or, the fifth field is related to the first spatial relationship.

[0499] During implementation, the UE does not expect that the value corresponding to the fifth field in the system message related to different beams, SSBs, or first spatial relationships in the same cell is the same.

[0500] In an implementation, the fifth field is used to indicate at least one of the following parameters:

[0501] General timing advance, timing offset, RAR listening offset.

[0502] During implementation, when the system message includes a beam indication, when the beam indications corresponding to the system messages received N times are the same, the system messages received N times are merged; and / or, if the beam indications corresponding to the system messages received N times are different, the system messages received N times are not merged; wherein N is greater than or equal to 2.

[0503] During implementation, it further includes:

[0504] When N received system messages correspond to the same SSB number,

[0505] If the SSB is not updated, merging the system messages received N times;

[0506] and / or, if the SSB is updated, the system messages received N times are not merged;

[0507] Wherein, N is greater than or equal to 2.

[0508] In implementation, the system message further includes one or a combination of the following parameters:

[0509] General timing advance, timing offset, RAR listening offset.

[0510] During implementation, determining the PDCCH listening opportunity includes:

[0511] Determine that the PDCCH listening opportunity is associated with a beam, an SSB and / or a first spatial relationship.

[0512] In implementation, it is assumed that the system message is sent only in the PDCCH listening opportunity associated with the beam, SSB and / or the first spatial relationship;

[0513] And / or, the terminal assumes that the system message is not sent in a PDCCH listening occasion other than a PDCCH listening occasion associated with the beam, the SSB and / or the first spatial relationship.

[0514] Among them, Figure 8 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 800 and various circuits of memory represented by memory 820 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 810 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium. For different user devices, the user interface 830 may also be an interface capable of externally and internally connecting required devices, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

[0515] The processor 800 is responsible for managing the bus architecture and general processing, and the memory 820 can store data used by the processor 800 when performing operations.

[0516] An embodiment of the present invention further provides a terminal, including:

[0517] The terminal determination module is used to determine the PDCCH listening opportunity;

[0518] The terminal receiving module is used to receive the system message according to the determined PDCCH listening opportunity.

[0519] In implementation, the system message is related to a beam and / or SSB.

[0520] In implementation, it is not expected that the values ​​corresponding to the same fields in system messages related to different beams and / or SSBs in the same cell are the same.

[0521] In implementation, the terminal determination module is further used to determine that the system message is related to the beam and / or SSB by one of the following methods or a combination thereof:

[0522] According to a pre-agreed agreement, confirm that the system message is related to the beam and / or SSB;

[0523] Confirming, according to a first field in SIB-TypeInfo, that the system message is related to a beam and / or an SSB, wherein the first field indicates that the system message is related to a beam and / or an SSB;

[0524] Confirming, according to a second field in the SIB, that the system message is related to the beam and / or the SSB, wherein the second field indicates that the system message is related to the beam and / or the SSB;

[0525] According to the third field in the SIB, it is confirmed that the system message is related to the beam and / or SSB, wherein the third field indicates the beam indication or SSB indication corresponding to the system message.

[0526] In implementation, the first field and areaScope in the SIB-TypeInfo cannot simultaneously take the value of true.

[0527] In an implementation, the system message is associated with the first spatial relationship.

[0528] In implementation, it is not expected that the values ​​corresponding to the same field in the system messages related to different first spatial relationships in the same cell are the same.

[0529] In implementation, the terminal determination module is further used to determine that the system message is related to the first spatial relationship by one of the following methods or a combination thereof:

[0530] According to the fourth field in the SIB, confirm that the system message is related to the first spatial relationship, wherein the fourth field includes at least one of the following indications or a combination thereof:

[0531] SSB instructions;

[0532] a first reference signal indication;

[0533] TCI indication;

[0534] The first reference signal includes at least one of the following reference signals:

[0535] CSI-RS, TRS, SRS.

[0536] In implementation, the system message includes a fifth field, wherein:

[0537] The fifth field is related to the beam;

[0538] And / or, the fifth field is related to SSB;

[0539] And / or, the fifth field is related to the first spatial relationship.

[0540] In implementation, it is not expected that the value corresponding to the fifth field in the system message related to different beams, SSBs, or first spatial relationships in the same cell is the same.

[0541] In an implementation, the fifth field is used to indicate at least one of the following parameters:

[0542] General timing advance, timing offset, RAR listening offset.

[0543] During implementation, the terminal receiving module is further used to, when the system message includes a beam indication, merge the system messages received N times when the beam indications corresponding to the system messages received N times are the same; and / or, if the beam indications corresponding to the system messages received N times are different, not merge the system messages received N times; wherein N is greater than or equal to 2.

[0544] During implementation, the terminal receiving module is further used to merge the system messages received N times when the system messages received N times correspond to the same SSB number if the SSB is not updated; and / or not merge the system messages received N times if the SSB is updated; wherein N is greater than or equal to 2.

[0545] In implementation, the system message further includes one or a combination of the following parameters:

[0546] General timing advance, timing offset, RAR listening offset.

[0547] In implementation, the terminal determination module is further used to determine the PDCCH listening opportunity, including:

[0548] Determine that the PDCCH listening opportunity is associated with a beam, an SSB and / or a first spatial relationship.

[0549] In implementation, the terminal assumes that the system message is sent only in a PDCCH listening opportunity associated with the beam, the SSB and / or the first spatial relationship;

[0550] And / or, the terminal assumes that the system message is not sent in a PDCCH listening occasion other than a PDCCH listening occasion associated with the beam, the SSB and / or the first spatial relationship.

[0551] For the convenience of description, the various parts of the above-mentioned device are divided into various modules or units according to their functions and described separately. Of course, when implementing the present invention, the functions of each module or unit can be implemented in the same or multiple software or hardware.

[0552] A computer-readable storage medium is also provided in an embodiment of the present invention, wherein the computer-readable storage medium stores a computer program for executing the above-mentioned SI receiving method and / or SI sending method.

[0553] For specific implementation, please refer to the implementation of the SI receiving method on the terminal side and / or the SI sending method on the base station side.

[0554] In summary, a satellite coverage area of ​​the NTN system may include multiple spot beams. In a typical deployment, each satellite generates only one cell (i.e., only one cell ID), and each cell includes multiple spot beams. A satellite has one cell ID.

[0555] The base station needs to broadcast many parameters related to the UE propagation delay, such as common TA, initial Koffset, RAR monitoring offset, etc. In typical applications, the parameters broadcast by the system message need to be the maximum value of the parameters determined according to the propagation delay of all users in its coverage area, for example, initial K offset = the maximum RTD of all users in the coverage area. Obviously, the larger the coverage radius of the system message, the greater the difference between its value and the value required by a single user (the maximum deviation is the maximum RTD of all users in the coverage area - the minimum RTD of all users).

[0556] Based on this, in the technical solution provided by the embodiment of the present invention, the base station broadcasts beam specific parameters through beam specific system messages, that is, different beams in a cell broadcast the same type of SI (such as SIB x), and the values ​​of the same-name fields carried in the system messages (such as SIB x) corresponding to different beams are different, and their parameter values ​​are associated with the corresponding beams. In this solution, the information carried in the SI is better adapted to the coverage area of ​​the beam; the system message overhead is small.

[0557] This solution further provides a beam specific system message indication solution, used to indicate to the terminal that the message is a beam specific system message, a reception solution, used to enable the UE to know where to receive the beam specific system message, and a system message merging solution, used to enable the UE to know which system messages can be merged, etc.

[0558] It can be seen that this solution is suitable for use in multi-beam coverage scenarios such as NTN.

[0559] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) containing computer-usable program code.

[0560] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0561] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0562] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0563] Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims

1. A method for receiving a system message SI, characterized in that: include: Determine the physical downlink control channel PDCCH listening time; Receive system messages according to the determined PDCCH listening opportunity; The system message is related to a beam and / or a synchronization signal block SSB; wherein the user equipment UE does not expect the same value corresponding to the same field in the system messages related to different beams and / or SSBs in the same cell; and / or, The system message is related to the first spatial relationship; wherein the UE does not expect the same value corresponding to the same field in the system messages related to different first spatial relationships in the same cell to be the same.

2. The method according to claim 1, characterized in that Determine that the system message is related to the beam and / or SSB by one of the following methods or a combination thereof: According to a pre-agreed agreement, confirm that the system message is related to the beam and / or SSB; Confirming, according to a first field in the system information block type information SIB-TypeInfo, that the system message is related to the beam and / or the SSB, wherein the first field indicates that the system message is related to the beam and / or the SSB; Confirming, according to a second field in the SIB, that the system message is related to the beam and / or the SSB, wherein the second field indicates that the system message is related to the beam and / or the SSB; According to the third field in the SIB, it is confirmed that the system message is related to the beam and / or SSB, wherein the third field indicates the beam indication or SSB indication corresponding to the system message.

3. The method according to claim 2, characterized in that The first field and the area scope areaScope in the SIB-TypeInfo cannot simultaneously take the value of true.

4. The method according to claim 1, characterized in that Determine that the system message is related to the first spatial relationship by one of the following methods or a combination thereof: Confirming, according to a fourth field in a system information block SIB, that the system message is related to the first spatial relationship, wherein the fourth field includes at least one of the following indications or a combination thereof: SSB instructions; a first reference signal indication; Transmission Configuration Indication TCI indication; The first reference signal includes at least one of the following reference signals: Channel state reference information CSI-RS, tracking reference signal TRS, and sounding reference signal SRS.

5. The method according to claim 1, characterized in that The system message includes a fifth field, wherein: The fifth field is related to the beam; And / or, the fifth field is related to SSB; And / or, the fifth field is related to the first spatial relationship.

6. The method according to claim 5, characterized in that The UE does not expect that the value corresponding to the fifth field in the system message related to different beams, SSBs, or first spatial relationships in the same cell is the same.

7. The method according to any one of claims 1 or 5, characterized in that: When the system message includes a beam indication, when the beam indications corresponding to the system messages received N times are the same, the system messages received N times are merged; and / or, if the beam indications corresponding to the system messages received N times are different, the system messages received N times are not merged; wherein N is greater than or equal to 2.

8. The method according to any one of claims 1 or 5, characterized in that: Further including: When N received system messages correspond to the same SSB number, If the SSB is not updated, merging the system messages received N times; and / or, if the SSB is updated, the system messages received N times are not merged; Wherein, N is greater than or equal to 2.

9. The method according to claim 1, characterized in that The system message also includes one or a combination of the following parameters: General timing advance, timing offset, random access response RAR listening offset.

10. The method according to claim 1, characterized in that Determine the PDCCH listening opportunity, including: Determine that the PDCCH listening opportunity is associated with a beam, an SSB and / or a first spatial relationship.

11. The method according to claim 1, characterized in that The terminal assumes that the system message is only sent in the PDCCH listening opportunity associated with the beam, SSB and / or the first spatial relationship.

12. A method for sending SI, characterized in that: include: The base station determines the system message that needs to be sent to the terminal; Send system messages on PDCCH; The system message is related to the beam and / or SSB; wherein the UE does not expect the same value corresponding to the same field in the system messages related to different beams and / or SSBs in the same cell; and / or, The system message is related to the first spatial relationship; wherein the UE does not expect the same value corresponding to the same field in the system messages related to different first spatial relationships in the same cell to be the same.

13. The method according to claim 12, characterized in that Determine that the system message is related to the beam and / or SSB by one of the following methods or a combination thereof: According to a pre-agreed agreement, confirm that the system message is related to the beam and / or SSB; Confirming, according to a first field in SIB-TypeInfo, that the system message is related to a beam and / or an SSB, wherein the first field indicates that the system message is related to a beam and / or an SSB; Confirming, according to a second field in the SIB, that the system message is related to the beam and / or the SSB, wherein the second field indicates that the system message is related to the beam and / or the SSB; According to the third field in the SIB, it is confirmed that the system message is related to the beam and / or SSB, wherein the third field indicates the beam indication or SSB indication corresponding to the system message.

14. The method according to claim 13, characterized in that The first field and areaScope in the SIB-TypeInfo cannot simultaneously take the value of true.

15. The method according to claim 12, characterized in that Determine that the system message is related to the first spatial relationship by one of the following methods or a combination thereof: According to the fourth field in the SIB, confirm that the system message is related to the first spatial relationship, wherein the fourth field includes at least one of the following indications or a combination thereof: SSB instructions; a first reference signal indication; TCI indication; The first reference signal includes at least one of the following reference signals: CSI-RS, TRS, SRS.

16. The method according to claim 12, characterized in that The system message includes a fifth field, wherein the fifth field is related to the beam; And / or, the fifth field is related to SSB; And / or, the fifth field is related to the first spatial relationship.

17. The method according to claim 16, characterized in that The UE does not expect that the value corresponding to the fifth field in the system message related to different beams, SSBs, or first spatial relationships in the same cell is the same.

18. The method according to claim 12, characterized in that The system message also includes one or a combination of the following parameters: General timing advance, timing offset, RAR listening offset.

19. The method of claim 12, wherein: The PDCCH that sends SI includes: The PDCCH is associated with a beam, an SSB and / or a first spatial relationship.

20. A terminal, characterized in that: include: The processor reads the program in the memory and performs the following processes: Determine the PDCCH listening opportunity; Receive system messages according to the determined PDCCH listening opportunity; a transceiver for receiving and transmitting data under the control of the processor; The system message is related to a beam and / or a synchronization signal block SSB; wherein the user equipment UE does not expect the same value corresponding to the same field in the system messages related to different beams and / or SSBs in the same cell; and / or, The system message is related to the first spatial relationship; wherein the UE does not expect the same value corresponding to the same field in the system messages related to different first spatial relationships in the same cell to be the same.

21. A terminal, characterized in that: include: A terminal determination module, used to determine a PDCCH listening opportunity; The terminal receiving module is used to receive the system message according to the determined PDCCH listening opportunity; The system message is related to a beam and / or a synchronization signal block SSB; wherein the user equipment UE does not expect the same value corresponding to the same field in the system messages related to different beams and / or SSBs in the same cell; and / or, The system message is related to the first spatial relationship; wherein the UE does not expect the same value corresponding to the same field in the system messages related to different first spatial relationships in the same cell to be the same.

22. A base station, characterized in that: include: The processor reads the program in the memory and performs the following processes: Determine the system messages that need to be sent to the terminal; Send system messages on PDCCH; a transceiver for receiving and transmitting data under the control of the processor; The system message is related to the beam and / or SSB; wherein the UE does not expect the same value corresponding to the same field in the system messages related to different beams and / or SSBs in the same cell; and / or, The system message is related to the first spatial relationship; wherein the UE does not expect the same value corresponding to the same field in the system messages related to different first spatial relationships in the same cell to be the same.

23. A base station, characterized in that: include: A base station determination module, used to determine the system message that needs to be sent to the terminal; A base station sending module, used for sending system messages on PDCCH; The system message is related to the beam and / or SSB; wherein the UE does not expect the same value corresponding to the same field in the system messages related to different beams and / or SSBs in the same cell; and / or, The system message is related to the first spatial relationship; wherein the UE does not expect the same value corresponding to the same field in the system messages related to different first spatial relationships in the same cell to be the same.

24. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program for executing the method according to any one of claims 1 to 19.