Resource determining method and apparatus for prach used for carrying system information request

Abstract

Embodiments of the present application provide a resource determining method and apparatus for a PRACH used for carrying a system information request. The method comprises: a terminal device determines a system information request period, wherein the system information request period comprises a first number (X1) of associated periods or a second number (X2) of associated pattern periods; and determining, in the system information request period, a third number of ROs used for repeatedly transmitting a PRACH preamble.

Description

Method and device for determining PRACH resources for carrying system information request Technical Field

[0001] The embodiments of the present application relate to the field of communication technologies. Background Art

[0002] To enhance the uplink coverage of network equipment (such as base stations), NR Rel-18 studies enhancing the power of Physical Random Access Channel (PRACH) transmitted by terminal equipment (UE) through multiple PRACH transmissions, thereby enabling network equipment to receive PRACHs sent by terminal equipment in areas with weaker coverage, thereby improving the coverage of the initial access channel and ensuring that terminal equipment at the cell edge can access the cell, thereby improving the coverage capability of the system.

[0003] It should be noted that the above introduction to the technical background is merely intended to provide a clear and complete description of the technical solutions of this application and facilitate understanding by those skilled in the art. Simply because these solutions are described in the background technology section of this application, it should not be assumed that the above technical solutions are well known to those skilled in the art.

[0004] Summary of the Invention

[0005] The inventors discovered that multi-PRACH can be applied to PRACH triggered by a system information request (SI request). However, the existing system information request period may not be sufficient to indicate the duration of the multi-PRACH. It may also incorrectly indicate the valid PRACH opportunity (RO), causing ambiguity in the terminal device. Furthermore, it may not clearly indicate the RO location of the multi-PRACH.

[0006] To address at least one of the above problems, embodiments of the present application provide a method and apparatus for determining resources of a PRACH for carrying a system information request.

[0007] According to one aspect of an embodiment of the present application, a method for determining resources of a PRACH for carrying a system information request is provided, including:

[0008] The terminal device determines a system information request (SI request) period, wherein the system information request period includes a first number (X1) of associated periods or a second number (X2) of associated pattern periods; and

[0009] The terminal device determines a third number for repeatedly sending a PRACH preamble in the system information request (SI request) period PRACH opportunity (RO).

[0010] According to another aspect of an embodiment of the present application, a device for determining resources of a PRACH for carrying a system information request is provided, which is configured in a terminal device, and includes:

[0011] A processing unit, which determines a system information request (SI request) period, wherein the system information request period includes a first number (X1) of associated periods or a second number (X2) of associated pattern periods; and determines a third number for repeatedly transmitting a PRACH preamble (preamble) in the system information request (SI request) period. PRACH opportunity (RO).

[0012] According to another aspect of an embodiment of the present application, a method for determining resources of a PRACH for carrying a system information request is provided, including:

[0013] The network device sends configuration information of the PRACH used to carry the system information request to the terminal device;

[0014] The network device receives the PRACH preamble repeatedly sent by the terminal device on a third number of ROs;

[0015] The terminal device determines a system information request (SI request) period, wherein the system information request period includes a first number (X1) of associated periods or a second number (X2) of associated pattern periods; and determines a third number for repeatedly transmitting a PRACH preamble in the system information request (SI request) period. PRACH opportunity (RO).

[0016] According to another aspect of an embodiment of the present application, a device for determining resources of a PRACH for carrying a system information request is provided, which is configured on a network device, and includes:

[0017] A sending unit, configured to send configuration information of a PRACH for carrying a system information request to a terminal device;

[0018] a receiving unit configured to receive a PRACH preamble repeatedly sent by the terminal device on a third number of ROs;

[0019] The terminal device determines a system information request (SI request) period, wherein the system information request period includes a first number (X1) of associated periods or a second number (X2) of associated pattern periods; and determines a third number for repeatedly transmitting a PRACH preamble in the system information request (SI request) period. PRACH opportunity (RO).

[0020] According to another aspect of an embodiment of the present application, a communication system is provided, including:

[0021] A network device that sends configuration information of a PRACH for carrying a system information request to a terminal device;

[0022] A terminal device, which determines a system information request (SI request) period, wherein the system information request period includes a first number (X1) of associated periods or a second number (X2) of associated pattern periods; and determines a third number for repeatedly transmitting a PRACH preamble (preamble) in the system information request (SI request) period. PRACH opportunity (RO).

[0023] One of the beneficial effects of the embodiments of the present application is that the system information request period can cover the time length of multiple PRACHs, can correctly indicate valid PRACH opportunities (ROs) and avoid ambiguity in terminal devices, and can also clearly indicate the RO positions of multiple PRACHs.

[0024] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.

[0025] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0026] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0028] FIG1 is a schematic diagram of a communication system according to an embodiment of the present application;

[0029] FIG2 is an example diagram of an indication within an SI request cycle;

[0030] FIG3 is a schematic diagram of a method for determining resources of a PRACH for carrying a system information request according to an embodiment of the present application;

[0031] FIG4 is another schematic diagram of a method for determining resources of a PRACH for carrying a system information request according to an embodiment of the present application;

[0032] FIG5 is an example diagram of determining a system information request (SI request) period according to an embodiment of the present application;

[0033] FIG6 is an example diagram of an RO according to an embodiment of the present application;

[0034] FIG7 is another example diagram of an RO according to an embodiment of the present application;

[0035] FIG8 is another example diagram of an RO according to an embodiment of the present application;

[0036] FIG9 is another example diagram of an RO according to an embodiment of the present application;

[0037] FIG10 is another example diagram of an RO according to an embodiment of the present application;

[0038] FIG11 is another example diagram of an RO according to an embodiment of the present application;

[0039] FIG12 is another example diagram of an RO according to an embodiment of the present application;

[0040] FIG13 is another example diagram of an RO according to an embodiment of the present application;

[0041] FIG14 is another schematic diagram of a method for determining resources of a PRACH for carrying a system information request according to an embodiment of the present application;

[0042] FIG15 is another schematic diagram of a method for determining resources of a PRACH for carrying a system information request according to an embodiment of the present application;

[0043] FIG16 is an example diagram of determining a system information request (SI request) period according to an embodiment of the present application;

[0044] FIG17 is another schematic diagram of a method for determining resources of a PRACH for carrying a system information request according to an embodiment of the present application;

[0045] FIG18 is another schematic diagram of a method for determining resources of a PRACH for carrying a system information request according to an embodiment of the present application;

[0046] FIG19 is another schematic diagram of a method for determining resources of a PRACH for carrying a system information request according to an embodiment of the present application;

[0047] FIG20 is another example diagram of an RO according to an embodiment of the present application;

[0048] FIG21 is another schematic diagram of a method for determining resources of a PRACH for carrying a system information request according to an embodiment of the present application;

[0049] FIG22 is another schematic diagram of an apparatus for determining resources of a PRACH for carrying a system information request according to an embodiment of the present application;

[0050] FIG23 is another schematic diagram of an apparatus for determining resources of a PRACH for carrying a system information request according to an embodiment of the present application;

[0051] FIG24 is a schematic diagram of a network device according to an embodiment of the present application;

[0052] Figure 25 is a schematic diagram of a terminal device according to an embodiment of the present application. DETAILED DESCRIPTION

[0053] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.

[0054] In the embodiments of the present application, the terms "first," "second," etc. are used to distinguish different elements in terms of title, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising," "including," "having," etc. refer to the presence of the stated features, elements, components, or components, but do not exclude the presence or addition of one or more other features, elements, components, or components.

[0055] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0056] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0057] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), future 6G, etc., and / or other communication protocols currently known or to be developed in the future.

[0058] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to the communication network and provides services to the terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0059] Among them, base stations may include but are not limited to: NodeB (NodeB or NB), evolved NodeB (eNodeB or eNB) and 5G base station (gNB), IAB host, etc., and may also include remote radio head (RRH, Remote Radio Head), remote radio unit (RRU, Remote Radio Unit), relay (relay) or low-power node (such as femeto, pico, etc.). The term "base station" can include some or all of their functions. Each base station can provide communication coverage for a specific geographical area. The term "cell" can refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0060] In the embodiments of the present application, the term "user equipment" (UE) or "terminal equipment" (TE) refers to, for example, a device that accesses a communication network through a network device and receives network services. A terminal device can be fixed or mobile and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, and so on.

[0061] Among them, terminal devices may include but are not limited to the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, etc.

[0062] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measurement, including but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device-to-device (D2D) terminal, machine-to-machine (M2M) terminal, and so on.

[0063] In addition, the term "network side" or "network device side" refers to one side of the network, which can be a base station or one or more network devices as described above. The term "user side" or "terminal side" or "terminal device side" refers to the user or terminal side, which can be a UE or one or more terminal devices as described above. Unless otherwise specified herein, "device" can refer to either network equipment or terminal equipment.

[0064] The following describes the scenarios of the embodiments of the present application through examples, but the present application is not limited thereto.

[0065] FIG1 is a schematic diagram of a communication system according to an embodiment of the present application, schematically illustrating a situation using a terminal device and a network device as an example. As shown in FIG1 , a communication system 100 may include a network device 101 and terminal devices 102 and 103. For simplicity, FIG1 illustrates only two terminal devices and one network device as an example, but the embodiments of the present application are not limited thereto.

[0066] In the embodiment of the present application, existing services or future services can be transmitted between the network device 101 and the terminal devices 102 and 103. For example, these services may include but are not limited to: enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.

[0067] It is worth noting that FIG1 shows that both terminal devices 102 and 103 are within the coverage range of network device 101, but the present application is not limited thereto. Both terminal devices 102 and 103 may not be within the coverage range of network device 101, or one terminal device 102 may be within the coverage range of network device 101 while the other terminal device 103 is outside the coverage range of network device 101.

[0068] In the embodiments of the present application, the high-layer signaling may be, for example, radio resource control (RRC) signaling; for example, an RRC message, including, for example, an MIB, system information, or a dedicated RRC message; or an RRC information element (RRC IE). The high-layer signaling may also be, for example, MAC (Medium Access Control) signaling; or a MAC control element (MAC CE). However, the present application is not limited thereto.

[0069] For PRACH transmission, to facilitate the terminal device to quickly obtain the time domain resources for PRACH transmission, the time domain pattern of SSB-RO mapping for PRACH transmission can be predetermined and repeated in the time domain. Based on the configuration of RO (PRACH occasion), the PRACH configuration period for PARCH transmission can be obtained.

[0070] However, due to conflicts with SSBs or downlink channels, a PRACH configuration period may drop some RO resources and may not be able to map all SSBs. Therefore, an SSB-to-RO association period is defined for single PRACH transmission to ensure that all SSB indices are mapped at least once. However, the SSB-to-RO mapping pattern formed by the SSB-to-RO association period is not guaranteed to be repeatable in the time domain, so an SSB-to-RO association pattern period is defined.

[0071] The above schematically illustrates the correlation period and the correlation pattern period. Please also refer to Table 1.

[0072] Table 1

[0073] Multiple PRACH transmission can also be referred to as a transmission with a third number PRACH transmission with repeated preamble preamble repetitions) or preamble repetition transmissions, i.e., in the third number The PRACH preamble is repeatedly sent on the PRACH opportunity (RO). The PRACH opportunity (RO) can be called RO group or MSG1 repetition. (also called repetition number) is configured by high-level parameters and can be set to {2, 4, 8}. Preamble repetitions: All valid ROs (valid PRACH occasions) are continuous in the time domain, use the same frequency domain resources, and are associated with the same SSB index, and use (associated with) the same preamble set for the SSB index.

[0074] For multiple PRACH transmissions (i.e., MSG1 repetitions), a time period is defined as the association pattern period of the minimum number of multiple PRACH transmissions associated with each SSB index for a configured repetition number, which can determine at least one RO group for each repetition number of multiple PRACH transmissions.

[0075] RO group is a multiple PRACH transmission The starting RO (or first RO) and other ROs in the RO group can be determined according to the description in Table 2 below.

[0076] Table 2

[0077] On the other hand, in a PRACH scenario initiated by an SI request, the terminal device sends a preamble on a suitable RO according to instructions within the SI request period. For example, the SI-RequestConfig information element (IE) and corresponding fields may be used for instructions.

[0078] Figure 2 shows an example of indications within an SI request cycle. As shown in Figure 2, rach-OccasionsSI configures the RO resources for the RACH triggered by the SI request; si-RequestPeriod configures the SI request cycle value and indicates the number of association periods. Within Si-RequestResources, ra-AssociationPeriodIndex indicates the association period index within the SI request cycle for the PARCH occasions in which the terminal device sends the preamble; and ra-ssb-OccasionMaskIndex indicates the time-domain RO index associated with the SSB index selected by the terminal device within that association period.

[0079] Currently, the RO resource of PRACH is determined within the SSB-to-RO association pattern period and is repeated at a later time. The SSB-to-RO association pattern period includes one or more SSB-to-RO association periods, where the SSB-to-RO association period is determined by the mapping between SSB and RO. The RO without SSB mapping in the SSB-to-RO association period cannot be used to transmit PRACH. When the terminal device determines the RACH resource, it first measures the DL RSRP and selects the SSB index associated with the sending resource based on the measured RSRP, and then selects the resource for sending the preamble from the resources associated with the SSB index.

[0080] The inventors found that: for the PRACH transmission with SI request scenario Preamble repetitions (or MSG1 repetitions, hereinafter referred to as MSG1 repetition), because MSG1 repetition is in The frequency domain resources are associated with the same SSB on continuous ROs in the time domain. Therefore, the PRACH occasions of MSG1 repetition have a longer span in the time domain than single PRACH transmission. Even the preamble of MSG1 repetition is sent on ROs in multiple association periods.

[0081] For PRACH transmission with SI request scenario Preamble repetitions, using the existing SI request period indication may not reach the ROs time span of MSG1 repetition, and is not sufficient to indicate the duration of MSG1 repetition.

[0082] In addition, when the value indicated by the existing SI request period is less than the time span of the RO of MSG1 repetition, it may incorrectly indicate the valid RO where the MSG1 repetition transmission is located. For example, because the existing SI request period configuration may be less than the time span of the MSG1 repetition transmission, The time length spanned by each RO. If the existing SI request period configuration is used, the terminal device may determine that the PRACH occasions sent by the SI request are the ROs in the same MSG1 repetition as the previously determined ROs, causing ambiguity for the terminal device. The terminal device will think that it is a new RACH attempt rather than a RACH attempt in the same MSG1 repetition.

[0083] In addition, the existing SI request indicates the RO position for sending preamble in the association period, but only indicates the position of one RO, and does not indicate the positions of multiple ROs for sending preamble in MSG1 repetition. Therefore, it is not clear whether MSG1 repetition is sending preamble. A preamble RO.

[0084] The following describes a solution to at least one of the above problems. In the following description, to avoid confusion, the terms "PRACH" and "physical random access channel" or "random access information" are interchangeable, the terms "PDCCH" and "physical downlink control channel" or "downlink control information" are interchangeable, and the terms "PDSCH" and "physical downlink data channel" or "downlink data" are interchangeable.

[0085] In addition, transmitting or receiving PRACH can be understood as transmitting or receiving random access information carried by PRACH; transmitting or receiving PDCCH can be understood as transmitting or receiving downlink control information carried by PDCCH; transmitting or receiving PDSCH can be understood as transmitting or receiving downlink data carried by PDSCH. The preamble can be called a random access preamble or a PRACH preamble.

[0086] Embodiments of the first aspect

[0087] The embodiment of the present application provides a method for determining resources of a PRACH for carrying a system information request, which is described from the perspective of a terminal device. FIG3 is a schematic diagram of a method for determining resources of a PRACH for carrying a system information request according to an embodiment of the present application. As shown in FIG3 , the method includes:

[0088] 301, the terminal device determines a system information request (SI request) period, wherein the system information request period includes a first number (X1) of associated periods or a second number (X2) of associated pattern periods; and

[0089] 302, the terminal device determines a third number for repeatedly sending a PRACH preamble in the system information request (SI request) period PRACH opportunity (RO).

[0090] It is worth noting that FIG3 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG3 above.

[0091] The PRACH transmission targeted by the embodiments of the present application may be referred to as multiple PRACH transmissions, but is not limited thereto. For example, other terms may be used, such as MSG1 repetition transmission, PRACH repetition transmission, multiple MSG1 transmissions, preamble repetition transmission, etc., and may also be simply referred to as MSG1 repetition, PRACH repetition, preamble repetition, etc. In addition, the repetition number may also be referred to as the number of multiple PRACH transmissions.

[0092] In the embodiment of the present application, the RO for sending preamble repetition is a valid RO (valid ROs), which can follow the definition of valid RO in the 38.213 protocol, for example, ROs that do not conflict with the SSB and whose time interval with the SSB is not less than a threshold, and ROs that do not conflict / overlap with the downlink time domain unit in the TDD configuration; the present application is not limited thereto.

[0093] In some embodiments, a system information request period (SI request period) is, for example, in milliseconds (ms). The system information request period includes a first number X1 of association periods or a second number (X2) of association pattern periods, where the first number X1 or the second number X2 is an integer greater than or equal to 1. The association period may refer to the aforementioned SSB-to-RO association period, and the association pattern period may refer to the aforementioned SSB-to-RO association pattern period.

[0094] In some embodiments, the third number The repetition number of PRACH transmissions is N, a positive integer greater than 1. The terminal device repeatedly transmits the preamble on N ROs, i.e., the same preamble is transmitted on N ROs. For example, N ROs transmitting the same preamble can be called an RO group, i.e., an RO group includes N ROs, where N is the repetition number of the PRACH transmissions.

[0095] In some embodiments, a PRACH opportunity group (RO group) maps at least a fourth number of synchronization signal block (SSB) indices, wherein the fourth number is a value configured and / or indicated by a network device, and the fourth number is an integer greater than or equal to 1.

[0096] For example, the fourth quantity is It can be obtained through ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon. This application is not limited to this and can also be obtained from other parameters. For specific content, please refer to related technologies.

[0097] Table 3 exemplifies an expression of an embodiment of the present application, but the present application is not limited thereto.

[0098] Table 3

[0099] The following first describes the case where the system information request period includes a first number (X1) of association periods. FIG4 is another schematic diagram of a method for determining resources of a PRACH for carrying a system information request according to an embodiment of the present application. As shown in FIG4 , the method includes:

[0100] 401. The terminal device determines a system information request (SI request) period, where the system information request period includes a first number (X1) of associated periods.

[0101] In some embodiments, the first number may be a value configured and / or indicated by a network device, and may be configured through RRC.

[0102] For example, X1 may be directly configured and / or indicated by the network device through RRC signaling, or X1 may be a value in a candidate value set configured by the network device through RRC signaling. For example, the candidate value set may be an RRC preconfigured set, such as {1, 2, 4, 8, 12, 16, 20, 24, 32}. For another example, a value in the candidate value set may be N times the SI request period of a single PRACH, where N is the repetition number of the MSG1 repetition.

[0103] For example, for MSG1 repetitions with different repetition numbers, the SI request period candidate value set is configured separately. For example, for an SI request period with a repetition number of 2, the candidate value set is {1, 2, 4, 8, 12, 16, 20, 24, 32}; for an SI request period with a repetition number of 4, the candidate value set is {2, 4, 8, 16, 24, 32, 40, 48, 64}; and for an SI request period with a repetition number of 8, the candidate value set is {4, 8, 16, 32, 48, 64, 80, 96, 128}.

[0104] For another example, for MSG1 repetitions with different repetition numbers, the SI request period candidate value set is configured together (either jointly or collectively). The corresponding SI request period values ​​for different repetition numbers are determined by the gNB implementation. For example, for MSG1 repetitions with repetition numbers of 2, 4, or 8, the common set is {1, 2, 4, 8, 12, 16, 20, 24, 32, 40, 48, 64, 80, 96, 128}.

[0105] For another example, the values ​​in the candidate value set are determined by the parameter si-RequestPeriod configuration and the repetition number of the MSG1 repetition, wherein the candidate value set configured by the si-RequestPeriod parameter is the same as the candidate value set of the single PRACH.

[0106] For example, if the RRC configures the candidate value set {1, 2, 4, 6, 8, 10, 12, 16} and the RRC configures the SI request resource for the MSG1 repetition with a repetition number of N, e.g., 2, then the candidate value set for the SI request period of the MSG1 repetition is the product of the candidate value set {1, 2, 4, 6, 8, 10, 12, 16} and the repetition number of the MSG1 repetition, i.e., {2, 4, 8, 12, 16, 20, 24, 32}. The SI request period of the MSG1 repetition can be obtained using the above method (i.e., the gNB does not configure the candidate value set), or the SI request period of the MSG1 repetition can be configured by the gNB but according to the above method, or a combination of the above methods can be used. One of the values ​​in the gNB-configured candidate value set is the number of association periods in the SI request period.

[0107] Table 4 is an example of an embodiment of the present application, which exemplarily shows the situation of configuring a candidate value set.

[0108] Table 4

[0109] In some embodiments, the first number is the minimum number of associated periods of the third number of preamble repetition transmissions so that the fourth number of SSB indices are at least mapped to the third number of ROs, wherein the preamble repetition transmission is a PRACH transmission that repeatedly transmits a PRACH preamble on the third number of PRACH opportunities (ROs).

[0110] Figure 5 is an example diagram of determining the system information request (SI request) period in an embodiment of the present application. For example, the terminal device determines that the associated SSB index is SSB#0 based on the DL RSRP, and the number of repetitions of MSG1 repetition is 4. The invalid RO is the RO position that conflicts with the downlink time slot or symbol configured semi-statically or dynamically by the SSB burst. The unused RO is the RO that is not used for preamble transmission because an SSB-to-RO mapping cycle cannot be formed. As shown in Figure 5, the minimum number of association periods that can satisfy the preamble transmission of 4 associations to SSB#0 is 4, and the SI request period length is determined to be 4 association periods.

[0111] As shown in FIG4 , the method for determining resources for sending a system information request PRACH may further include:

[0112] 402. The terminal device determines an association period in which the third number of RO groups in which the preamble is repeatedly sent belongs.

[0113] In some embodiments, the terminal device can determine the associated period index in which the preamble is repeatedly sent through RRC configuration.

[0114] In some examples, the terminal device determines the association period index (different from the parameter ra-AssociationPeriodIndex) in which the MSG1 repetition is sent in the SI request period through RRC configuration.

[0115] For example, the candidate value set of the association period index is configured by RRC, for example, the candidate value set of the association period index is {0, 1, 2, ..., X1max-1}, where X1max is the maximum value that X1 can take, and the value of the association period index starts from 0 and corresponds to the ascending order of the association period time domain resources in the SI request period.

[0116] For another example, the gNB determines the association period index for the MSG1 repetition transmission and configures it via RRC (e.g., without a candidate value set). The association period index starts at 0 and corresponds to the ascending order of the association period time domain resources in the SI request period.

[0117] For another example, if the candidate value set of the SI request period is determined to be {2, 4, 8, 16, 24, 32, 40, 48, 64}, then the candidate value set of the association period index configuration is {0, 1, 2, 3, ..., 61, 62, 63,}.

[0118] In other examples, the terminal device determines the association period index through the RRC configuration parameter ra-AssociationPeriodIndex.

[0119] For example, the parameter ra-AssociationPeriodIndex indicates that the association period index is D1 (the value of the parameter ra-AssociationPeriodIndex is the same as the value of legacy), and the association period index of MSG1 repetition is D2. Where N is the repetition number of the MSG1 repetition. D2 is determined by RRC configuration using one of the above formulas, and the value of n is determined by RRC configuration.

[0120] For another example, the parameter configured by RRC is the same as the value configured by the parameter ra-AssociationPeriodIndex. If the set of candidate SI request period values ​​is determined to be {2, 4, 8, 16, 24, 32, 40, 48, 64}, and if there are 8 association periods in the SI request period, the value configured by ra-AssociationPeriodIndex is used for indication, that is, D1 is used to indicate INTEGER (0..15). If for an MSG1 repetition with a repetition number of 2, there are 32 association periods in the SI request period; if the indicated association period index is less than 15, the value configured by ra-AssociationPeriodIndex is used for indication; if the indicated association period index is greater than 15 and is an even number, D2 = D1 × n, n = 2, ..., N is used for indication. For example, if D2 = 20, then D1 = 10, n = 2. If the indicated association period index is greater than 15 and is an odd number, then D2 = D1 × n + 1, n = 2, ..., N. For example, if D2 = 31, then D1 = 15, n = 2.

[0121] Table 5 shows an example of the configuration parameter IE.

[0122] Table 5

[0123] The above IE includes SI-RequestResources, wherein an example of ra-AssociationPeriodIndex is shown in Table 6 below.

[0124] Table 6

[0125] For example, you can directly configure the association period index parameter in the SI-RequestResourcesForMSG1-RepetitionNum parameter in the SI-RequestConfigRepetition. For another example, you can use the SI-RequestResources configuration and define a ra-AssociationPeriodIndex-r18 parameter for MSG1repetition in the SI-RequestResources, or directly use the ra-AssociationPeriodIndex parameter in the SI-RequestResources to indicate it.

[0126] As shown in FIG4 , the method for determining resources for sending a system information request PRACH may further include:

[0127] 403. The terminal device determines, according to the RRC configuration, positions of the third number of ROs (RO groups) to which the preambles are repeatedly sent in the association period.

[0128] In some embodiments, the terminal device determines the position of the starting RO (starting RO or first RO) in the third number of ROs (RO group) associated with the selected or indicated SSB index through RRC indication, and the remaining ROs in the third number of ROs (RO group) are adjacent ROs in the time domain associated with the same SSB index in the same frequency domain.

[0129] In some examples, the terminal device indexes all ROs associated with the selected or indicated SSB index within an SSB to RO mapping cycle; wherein, within each SSB to RO mapping cycle in the determined association period, the ROs associated with the selected or indicated SSB index are indexed in ascending order of frequency resources first and then in ascending order of time domain resources; and the index of the starting RO (starting RO or first RO) in the selected third number of ROs (RO group) is determined by RRC parameter indication.

[0130] For example, to determine the RO index, within each SSB-to-RO mapping cycle in the indicated association period, the ROs associated with the selected SSB index may be numbered in ascending order starting from 1, with the numbering order being first determined based on the ascending order of frequency domain resources, and then determined based on the ascending order of time domain resources in the SSB-to-RO mapping cycle. To indicate the RO index, the RO index corresponding to the starting RO of the selected RO group may be indicated by an RRC parameter.

[0131] The following indication method (indication method 1) can be used: ra-ssb-OccasionMaskIndex is used to indicate the position of the starting RO of the selected RO group. The candidate value set of the ra-ssb-OccasionMaskIndex parameter is the same as the existing parameter. The table corresponding to the ra-ssb-OccasionMaskIndex parameter is shown in Table 7.

[0132] Table 7 (PRACH Mask Index values)

[0133] For example, the RO index indicated by ra-ssb-OccasionMaskIndex is the index of the RO associated with the corresponding SSB index in the first SSB-to-RO mapping cycle in the selected association period. For another example, the RO index indicated by ra-ssb-OccasionMaskIndex is the index of the RO associated with the corresponding SSB index in the Xth SSB-to-RO mapping cycle in the selected association period. The X number is configured by RRC parameters. The association period / mapping cycle contains at least one first RO of an RO group associated with the selected SSB index.

[0134] The following indication method (indication method 2) can be used: the RRC parameter indicates the position of the starting RO of the selected RO group, and the value indicated by the RRC parameter corresponds to the position of the starting RO of the selected RO group. The RO index of the first RO in the preamble. (That is, the RRC parameter is different from the existing ra-ssb-OccasionMaskIndex parameter).

[0135] For example, the RRC parameter corresponds to a table. For another example, the RRC parameter directly indicates the index of the RO associated with the corresponding SSB index in the Xth SSB-to-RO mapping cycle in the selected association period. Where X is configured by the RRC parameter. For another example, the RRC parameter directly indicates the RO index in the association period.

[0136] Figure 6 is an example diagram of an RO in an embodiment of the present application. Figure 6 shows SSB-to-RO mapping, where the SSB index is 0 to 3, there are two ROs for FDM on one time domain resource, and each SSB index is associated with four ROs. For the MSG1 repetition with a repetition number of 2, the RO in association period #0 is indicated as the first RO of the RO group. The terminal device selects the RO associated with SSB #0 to send the preamble based on the DL RSRP, where the ROs associated with SSB 0 in association period 0 are numbered starting from 1. The first RO of the RO group associated with SSB 0 is determined by indicating RO #1 and RO #2.

[0137] In some examples, the terminal device indexes a starting RO (or first RO) in the third number of ROs (RO group) associated with the selected or indicated SSB index in the determined association period;

[0138] In the determined association period, the starting RO (starting RO or first RO) in the third number of ROs (RO group) associated with the selected or indicated SSB index is numbered in ascending order of frequency resources, and then numbered in ascending order of time domain resources in the association period; and the index of the starting RO (starting RO or first RO) in the third number of ROs (RO group) in the association period is determined by RRC parameter indication.

[0139] For example, only the starting RO of the RO group is numbered. For the determination of RO index: in the indicated association period, the first RO of the RO groups associated with the same SSB index are numbered in ascending order starting from 1. The numbering order is to first determine the index of the first ROs of the RO groups from the ascending order of frequency domain resources, and then determine the index of the first ROs of the RO groups from the ascending order of time domain resources in the association period. For the indication of RO index: the RRC parameter indicates the selected association period for sending The index of the first RO of each preamble repetition.

[0140] The following indication method (indication method 1) can be used: RRC parameter direct indication corresponds to sending The index of the first RO of the preamble.

[0141] The following indication method (indication method 2) can also be used: RRC parameter configuration RO group index candidate value set in association period, and indicate a value from the set corresponding to the sending The RO index of the first RO in the preamble. This can be a direct correspondence, where the indicated value is the RO index of the first RO, or an indirect correspondence, where the indicated value corresponds to the RO index of the first RO indicated in a table. For example, this can be indicated by the ra-ssb-OccasionMaskIndex parameter and an existing table, or by a new parameter indication and a new table. The first RO of the RO group associated with the selected SSB index must exist in the association period corresponding to the indicated association period index, as determined by the base station implementation.

[0142] FIG7 is another example diagram of an RO according to an embodiment of the present application. As shown in FIG7 , for example, only the first RO associated with SSB 0 that can be used as an RO group is numbered, and the remaining ROs are not numbered.

[0143] In the case of multiple SSB-to-RO mappings within an association period, for example, the configuration is for the Xth SSB-to-RO mapping cycle within the association period. For example, X can be a default value, such as 1. That is, the RO index indicated by default is the RO index of the first SSB-to-RO mapping cycle in the association period. For another example, X can be determined through configuration, such that the indicated RO index is not the RO within a specific SSB-to-RO mapping cycle, but the RO index of all ROs associated with the SSB index in the association period.

[0144] Figure 8 is another example diagram of an RO in an embodiment of the present application. Figure 8 shows SSB-to-RO mapping, where the SSB index is 0 to 2. There are two ROs for FDM on one time domain resource, and each SSB index is associated with one RO. For the MSG1 repetition with a repetition number of 4, the RO in association period #0 is indicated as the first RO of the RO group. The terminal device selects the RO associated with SSB #0 to send the preamble based on the DL RSRP, where the ROs associated with SSB 0 in association period 0 are numbered starting from 1. The first RO of the RO group associated with SSB 0 is determined by indicating RO #1 and RO #2.

[0145] Figure 9 is another example diagram of an RO according to an embodiment of the present application. As shown in Figure 9, the Xth mapping cycle in an association period can be numbered. Figure 10 is another example diagram of an RO according to an embodiment of the present application. As shown in Figure 10, all ROs associated with a selected SSB index in an association period can be numbered.

[0146] For the indication of RO index, the RRC parameter can directly indicate the sending of MSG1 repetition. The RO index of the first RO of the RO can also be indicated by the RRC parameter value in the candidate value set, corresponding to the sending of MSG1 repetition The RO index of the first RO of the RO.

[0147] For example, it can directly correspond to: for example, the candidate value set of RO index is {0,1,2,3,4,5,6,7}, and the RRC parameter indicates a value in the set. For example, if the RRC parameter configuration RO index is 2, then the RO with RO index 2 is the one that sends MSG1 repetition. The first RO of ROs.

[0148] Another example can also be indirectly corresponding: for example, the RRC configuration candidate value set is {0,1,2,3,...,15}, and the candidate value set corresponds to the RO index in a row in the table. For example, the table is Table 7. When the RRC configuration RO index parameter indicates 6, the RO with RO index 7 is the one that sends MSG1 repetition. The first RO of ROs.

[0149] In some embodiments, the terminal device determines the position of the third number of ROs (RO groups) associated with the selected or indicated SSB index through RRC indication; wherein in the determined association period, the third number of ROs (RO groups) associated with the selected or indicated SSB index are numbered in ascending order of frequency resources, and then numbered in ascending order of time domain resources in the association period; and the index of the third number of ROs (RO groups) is determined in the association period through RRC parameter indication.

[0150] For example, the positions of the RO groups associated with the selected SSB index are indicated by RRC parameters.

[0151] For the determination of RO group index: in the indicated association period, RO groups associated with the same SSB index are numbered in ascending order starting from 1. The numbering order is to first determine the index of the RO groups from the ascending order of frequency domain resources, and then determine the index of the RO groups from the ascending order of time domain resources in the association period.

[0152] For the indication of RO group index: RRC parameter indication is used to send in the selected association period The index of the RO group of the preamble.

[0153] The following indication method (indication method 1) can be used: RRC parameter direct indication corresponds to sending The index of the RO group of the preamble.

[0154] The following indication method (indication method 2) can also be used: RRC parameter configuration RO group index candidate value set in association period, and indicate a value from the set corresponding to the sending For example, it can directly correspond, that is, the indicated value is the index of the RO group; for another example, it can also indirectly correspond, that is, the indicated value corresponds to the index of the RO group indicated in a table.

[0155] For example, the RO groups can be numbered and the RO set to send the preamble repetition can be determined based on the RO group index. Figure 11 is another example diagram of ROs in an embodiment of the present application. Figure 11 shows SSB-to-RO mapping, where the SSB index is 0 to 3. There are 4 ROs in FDM on one time domain resource, and each SSB index is associated with 2 ROs. For the MSG1 repetition with a repetition number of 2 associated with SSB 0, the RO group index is determined as described above. ROs with the same label are one RO group.

[0156] For another example, the first RO of the RO group can be numbered and the RO set to send the preamble repetition can be determined based on the RO index of the first RO. Figure 12 is another example diagram of RO in an embodiment of the present application. Figure 12 shows SSB-to-RO mapping, where the SSB index is 0 to 3, there are 4 ROs in FDM on one time domain resource, and each SSB index is associated with 2 ROs. For the MSG1repetition with the repetition number 2 associated with SSB 0, the first RO of the RO group is numbered within an SI request cycle, and the index of the RO group is determined as above. ROs with the same label are one RO group.

[0157] Figure 13 is another example diagram of an RO according to an embodiment of the present application. Figure 13 illustrates SSB-to-RO mapping, with SSB indices ranging from 0 to 3. There are four ROs in FDM on a time domain resource, with each SSB index associated with two ROs. For the MSG1 repetition associated with SSB 0 and repetition number 2, the first RO of the RO group is numbered within an SSB-to-RO mapping cycle. The RO group index is determined as described above. ROs with the same index are considered an RO group.

[0158] The above is an exemplary description of the determination of the RO group index. For the indication of the RO group index, reference may be made to the aforementioned content.

[0159] In some embodiments, the terminal device determines the position of any one RO in the third number of ROs (RO group) associated with the selected or indicated SSB index through RRC indication; wherein in each SSB to RO mapping cycle in the determined association period, the RO associated with the selected or indicated SSB index is numbered in ascending order of frequency resources first, and then in ascending order of time domain resources within the SSB to RO mapping cycle; and the index of one RO in the third number of ROs (RO group) within an SSB to RO mapping cycle in the association period is determined through RRC parameter indication.

[0160] For example, the RRC parameter indicates the position of any RO in the RO groups associated with the selected SSB index. For the determination of the RO index: in each SSB-to-RO mapping cycle in the indicated association period, the ROs associated with the same SSB index are numbered in ascending order starting from 1, and the numbering order is to first determine the RO index from the ascending order of the frequency domain resources, and then determine the RO index from the ascending order of the time domain resources in the SSB-to-RO mapping cycle. For the indication of the RO index: the RRC parameter indicates the Xth SSB-to-RO mapping cycle in the selected association period for sending The index of a RO in the preamble repetitions.

[0161] For example, X may default to a certain value, for example, X defaults to 1, ie, the RRC indicates the RO index in the first mapping cycle in the selected association period; for another example, X may be configured by an RRC parameter.

[0162] RO index can be indicated in the following ways (indication method 1): RRC parameter direct indication is used to send The index of a RO in a preamble repetition. The RO group to which the RO index corresponds is the RO group used for RO group sent by preamble repetition.

[0163] RO index can also be indicated in the following manner (indication method 2): RRC parameter configuration RO index candidate value set, and indicate a value from the set corresponding to the sent For example, it can directly correspond to, that is, directly indicate the RO index; the RO group to which the RO corresponding to the indicated RO index belongs is used for For another example, it can also correspond indirectly, that is, the indicated value corresponds to the RO index indicated in a table; the RO group to which the RO corresponding to the indicated RO index belongs is the RO group for For example, the RO group sent by the preamble repetition is indicated by the ra-ssb-OccasionMaskIndex parameter and the existing table, or a new parameter indication and a new table.

[0164] For example, the UE first determines the RO group pattern in an SI request cycle, and uses the aforementioned indication method to indicate an RO index. The RO group corresponding to the RO index is the one that sends the MSG1 repetition. ROs.

[0165] FIG4 and related contents schematically illustrate that the RO is determined through RRC configuration. The RO can also be randomly selected.

[0166] FIG14 is another schematic diagram of a method for determining resources of a PRACH for carrying a system information request according to an embodiment of the present application. As shown in FIG14 , the method includes:

[0167] 1401. The terminal device determines a system information request (SI request) period, where the system information request period includes a first number (X1) of associated periods.

[0168] 1402. The terminal device determines an association period in which a third number of RO groups (RO groups) in which the preamble is repeatedly transmitted belong.

[0169] Regarding the above 1401 and 1402, please refer to the above 401 and 402 and related contents respectively.

[0170] As shown in FIG14 , the method further includes:

[0171] 1403. The terminal device randomly selects the third number of ROs (RO groups) associated with the selected or indicated SSB index during the association period.

[0172] For example, in the association period indicated by the association period index, an RO group associated with the selected SSB index is randomly selected.

[0173] The above schematically illustrates the situation where the system information request period includes the first number (X1) association periods, but the present application is not limited thereto. For example, the contents of Figures 3 and 4 can be combined. For example, when RRC configures the MSG1 repetition of SI request to send When the RO position of the preamble is not configured, the RO resource for sending the preamble is determined according to the RO index of the indicated starting RO, or the RO resource for sending the preamble is determined according to the indicated RO group index. When the RO position is not configured, the UE randomly selects the RO resource.

[0174] In some embodiments, the maximum value of the first number is X1max. X1max can be a fixed value, such as 128; or X1max is the number of association periods when the time period reaches an upper limit; or X1max is a value configured by the network device.

[0175] The following further describes the case where the system information request period includes a second number (X2) of association pattern periods. FIG15 is another schematic diagram of a method for determining resources of a PRACH for carrying a system information request according to an embodiment of the present application. As shown in FIG15 , the method includes:

[0176] 1501. The terminal device determines a system information request (SI request) period, where the system information request period includes a second number (X2) of associated pattern periods.

[0177] In some embodiments, the second number is configured by the network device via RRC.

[0178] For example, the RRC parameter indicates the number of association pattern periods in the SI request period, that is, the SI request period is configured as X2 association pattern periods. X2 may be directly configured by RRC (that is, there is no candidate value set), or X2 may be configured by RRC and be a value in a candidate set, and the candidate value set may be a set configured by RRC, such as {1, 2, 4, 8}.

[0179] In some embodiments, the second number is a value determined by a parameter configured by the network device through RRC.

[0180] For example, X2 is determined by other parameters configured by the base station. For example, the value of X2 is the value of the repetition number corresponding to the MSG1 repetition; for another example, the value of X2 is the same as the number of association pattern periods in the time period.

[0181] In some embodiments, the second number is the minimum number of associated pattern periods for repeated preamble transmission so that the fourth number of SSB indices are at least mapped to the third number of ROs, wherein the repeated preamble transmission is a PRACH transmission that repeatedly transmits a PRACH preamble on the third number of PRACH opportunities (ROs).

[0182] For example, X2 is: for the configured repetition number of MSG1 repetition, the SI request period is a value of the minimum number of association pattern periods for which all SSB indices are mapped to at least one RO group.

[0183] Figure 16 is an example diagram of determining the system information request (SI request) period in an embodiment of the present application. Figure 16 shows SSB-to-RO mapping, where the SSB index is 0 to 2, there are 2 ROs for FDM on one time domain resource, and each SSB index is associated with 1 RO. For the MSG1 repetition with a repetition number of 4, the RO in association period #0 is indicated as the first RO of the RO group. The terminal device selects the RO associated with SSB #0 to send the preamble based on the DL RSRP, where the RO associated with SSB 0 in association period 0 is numbered starting from 1, and the first RO of the RO group associated with SSB 0 is determined by indicating RO #1 and RO #2.

[0184] In Figure 16, the minimum number of association pattern periods required for SSBs 0 to 2 to be mapped to an RO group is 2. The dotted ROs are the RO groups associated with SSB 0, the slashed ROs are the RO groups associated with SSB 1, and the grid ROs are the RO groups associated with SSB 2. The remaining ROs cannot form an RO group and are therefore not used for multiple PRACH transmission.

[0185] As shown in FIG15 , the method for determining resources for sending a system information request PRACH may further include:

[0186] 1502. The terminal device determines an association pattern period in which the third number of RO groups (RO groups) in which the preamble is repeatedly sent belongs.

[0187] In some embodiments, the terminal device determines the associated pattern period index in which the preamble is repeatedly transmitted through RRC configuration.

[0188] For example, RRC configures the association pattern period index where MSG1 repetition is sent in the SI request period, and the candidate value set of the association pattern period index is configured by RRC. The following method 1 (direct configuration of the candidate value set) can be adopted: for example, the candidate value set of the association pattern period index is {0,1,2,…,X2max-1}, where X2max is the maximum value that X2 can take, and the value of the association period index starts from 0 and corresponds to the ascending order of the time domain resources of the association pattern period in the SI request period. The following method 2 (indirect configuration of the candidate value set) can also be adopted: for example, the values ​​in the candidate value set correspond to the values ​​of the association pattern period index in a certain table.

[0189] For another example, the gNB determines the association pattern period index for the MSG1 repetition transmission and configures it via RRC (without a candidate value set). The association pattern period index value starts from 0 and corresponds to the ascending order of the association pattern period time domain resources in the SI request period.

[0190] For another example, the association pattern period index parameter can be directly configured in the SI-RequestResourcesFor MSG1-RepetitionNum parameter in the SI-RequestConfigRepetition.

[0191] As shown in FIG15 , the method for determining resources for sending a system information request PRACH may further include:

[0192] 1503. The terminal device determines, within an association pattern period, an association period in which the third number of ROs repeatedly sent by the preamble is located.

[0193] In some embodiments, the terminal device determines the associated period index in which the preamble is repeatedly transmitted through RRC configuration.

[0194] For example, RRC configures the association period index (i.e., different from the parameter ra-AssociationPeriodIndex) in which the MSG1 repetition sends the preamble in the association pattern period. For example, the candidate value set of the association period index is configured by RRC, such as the candidate value set of the association period index is {0, 1, 2, ..., X3}, where X3max is the maximum value that X3 can take. The value of X3 can be: X3 is a default fixed value, such as 16; X3 can also be determined by the base station implementation; wherein the value of the association period index starts from 0 and corresponds to the ascending order of the association period time domain resources in the association pattern period. For another example, the gNB determines the association period index in which the MSG1 repetition is sent and configures it through RRC (without a candidate value set); wherein the value of the association period index starts from 0 and corresponds to the ascending order of the association period time domain resources in the SI request period.

[0195] For another example, the association period index is determined by the parameter ra-AssociationPeriodIndex configured in RRC. For example, the value of the parameter ra-AssociationPeriodIndex is the same as the existing value.

[0196] For the configuration of candidate value sets for the association period index, refer to the previous embodiments for its configuration parameters. For example, the association period index parameter can be directly configured in the SI-RequestResourcesForMSG1-RepetitionNum parameter in the SI-RequestConfigRepetition. For another example, the SI-RequestResources configuration can be used to define a ra-AssociationPeriodIndex-r18 parameter for MSG1repetition in the SI-RequestResources. Alternatively, the ra-AssociationPeriodIndex parameter in the SI-RequestResources can be directly used to indicate this.

[0197] As shown in FIG15 , the method for determining resources for sending a system information request PRACH may further include:

[0198] 1504. The terminal device determines the third number of ROs (RO groups) in the association period.

[0199] For example, as described in 403 in Figure 4, the terminal device determines the positions of the third number of ROs (RO groups) to which the preamble is repeatedly sent in the association period according to the RRC configuration; or, as described in 1303 in Figure 13, the terminal device randomly selects the third number of ROs (RO groups) associated with the selected or indicated SSB index in the association period.

[0200] FIG17 is another schematic diagram of a method for determining resources of a PRACH for carrying a system information request according to an embodiment of the present application. As shown in FIG17 , the method includes:

[0201] 1701. The terminal device determines a system information request (SI request) period, where the system information request period includes a second number (X2) of associated pattern periods.

[0202] 1702. The terminal device determines an association pattern period in which the third number of ROs (RO groups) repeatedly transmitted by the preamble belong.

[0203] Regarding the above 1701 and 1702, please refer to the above 1501 and 1502 and related contents respectively.

[0204] As shown in FIG17 , the method may further include:

[0205] 1703. The terminal device determines, according to the RRC configuration, positions of the third number of ROs (RO groups) to which the preamble is repeatedly transmitted in the association pattern period.

[0206] In some embodiments, the terminal device determines the position of the starting RO (starting RO or first RO) in the third number of ROs (RO group) associated with the selected or indicated SSB index through RRC indication, and the remaining ROs in the third number of ROs (RO group) are adjacent ROs in the time domain associated with the same SSB index in the same frequency domain.

[0207] In some examples, the terminal device numbers all ROs associated with the selected or indicated SSB index within the SSB to RO mapping loop;

[0208] The SSB to RO mapping cycle where the starting RO (or first RO) of the third number of ROs (RO group) in the associated pattern period is located is determined in ascending order of frequency resources first and then in ascending order of time domain resources within the associated pattern period.

[0209] Within the indicated SSB to RO mapping loop, the ROs associated with the selected or indicated SSB index are numbered in ascending order of frequency resources first and then in ascending order of time domain resources within the SSB to RO mapping loop; and the index of the starting RO (starting RO or first RO) in the third number of ROs (RO group) is determined by RRC parameter indication.

[0210] For example, the ROs with the same SSB index in the SSB-to-RO mapping cycle can be labeled. The order of the SSB-to-RO mapping cycles in which the first RO of the preamble is located. The SSB-to-RO mapping cycle order is determined in ascending order starting from 1, according to the ascending order of frequency domain resources and then according to the ascending order of time domain resources in the association pattern period.

[0211] For determining the RO index, within the SSB-to-RO mapping cycle indicated above, the ROs associated with the selected SSB index are numbered in ascending order starting from 1, and the numbering order is to first determine the RO index from the ascending order of frequency domain resources, and then determine the RO index from the ascending order of time domain resources in the SSB-to-RO mapping cycle.

[0212] For RO index indication: RRC parameter indication is sent For example, the following indication method 1 is adopted: ra-ssb-OccasionMaskIndex indicates the position of the starting RO of the selected RO group, the candidate value set of the ra-ssb-OccasionMaskIndex parameter is the same as the existing parameter, and the table corresponding to the ra-ssb-OccasionMaskIndex parameter is Table 7. For another example, the following indication method 2 is adopted: RRC parameter indicates the position of the starting RO of the selected RO group, and the value indicated by the RRC parameter corresponds to the position of the starting RO of the selected RO group. The RO index of the first RO in the preamble. That is, this RRC parameter is different from the existing ra-ssb-OccasionMaskIndex parameter.

[0213] In some examples, the terminal device numbers all ROs associated with the selected or indicated SSB index within the associated pattern period, wherein within the associated pattern period, the ROs associated with the selected or indicated SSB index are numbered in ascending order of frequency resources first and then in ascending order of time domain resources within the associated pattern period; and the index of the starting RO (starting RO or first RO) in the third number of ROs (RO group) within the associated pattern period is determined by RRC parameter indication.

[0214] For the determination of RO index: within the determined association pattern period, the ROs associated with the selected SSB index are numbered in ascending order starting from 1, and the numbering order is to first determine the RO index from the ascending order of frequency domain resources, and then determine the RO index from the ascending order of time domain resources within the association pattern period.

[0215] For RO index indication: RRC parameter indicates the selected association pattern period, used to send The index of the first RO of the preamble repetitions. For example, the following indication method 1 can be used: RRC parameters directly indicate the corresponding For another example, the following indication method 2 can be used: the RRC parameter configuration association pattern period RO group index candidate value set (larger than the aforementioned candidate value set), and indicate a value from the set corresponding to the sent The RO index of the first RO in the preamble. This can be a direct correspondence, indicating the RO index of the first RO, or an indirect correspondence, indicating the value corresponding to the RO index of the first RO in a table. For example, this can be indicated by the ra-ssb-OccasionMaskIndex parameter and an existing table, or by a new parameter and a new table.

[0216] For a new table, for example, RRC indicates a certain value, the value corresponds to a certain row in the table, and the row in the table corresponds to the RO index.

[0217] In some examples, the terminal device numbers a starting RO (or first RO) in the third number of ROs (RO group) associated with the selected or indicated SSB index in the associated pattern period;

[0218] Wherein, within the associated pattern period, the starting RO (starting RO or first RO) in the third number of ROs (RO group) associated with the selected or indicated SSB index is numbered in ascending order of frequency resources first and then in ascending order of time domain resources within the associated pattern period; and the index of the starting RO (starting RO or first RO) in the third number of ROs (RO group) within the associated pattern period is determined by RRC parameter indication.

[0219] For example, only the starting RO of the RO group can be numbered. Regarding the determination of the RO index: in the indicated association pattern period, the first RO of the RO groups associated with the same SSB index are numbered in ascending order starting from 1. The numbering order is to first determine the index of the first ROs of the RO groups from the ascending order of frequency domain resources, and then determine the index of the first ROs of the RO groups from the ascending order of time domain resources in the association pattern period.

[0220] For RO index indication: RRC parameter indicates the selected association pattern period, used to send The index of the first RO of the preamble repetitions. For example, the following indication method 1 can be used: RRC parameters directly indicate the corresponding For another example, the following indication method 2 can be used: the RRC parameter configuration association pattern period RO group index candidate value set, and indicate a value from the set corresponding to the sent The RO index of the first RO in the preamble. This can be a direct correspondence, where the indicated value is the RO index of the first RO, or an indirect correspondence, where the indicated value corresponds to the RO index of the first RO indicated in a table. For example, this can be indicated by the ra-ssb-OccasionMaskIndex parameter and an existing table, or by a new parameter and a new table. The first RO of the RO group associated with the selected SSB index must exist in the indicated association pattern period, and this is determined by the base station implementation.

[0221] In some embodiments, the terminal device determines the position of the third number of ROs (RO groups) associated with the selected or indicated SSB index through RRC indication; wherein in the associated pattern period, the third number of ROs (RO groups) associated with the selected or indicated SSB index are numbered in ascending order of frequency resources, and then numbered in ascending order of time domain resources in the associated pattern period; and the index of the third number of ROs (RO groups) in the associated pattern period is determined through RRC parameter indication.

[0222] For example, the position of the RO groups associated with the selected SSB index is indicated by an RRC parameter. For determining the RO group index: determining it in the association pattern period, refer to the aforementioned embodiment (e.g., FIG. 4 and related content). For indicating the RO group index, refer to the aforementioned embodiment (e.g., FIG. 4 and related content).

[0223] In some embodiments, the terminal device determines the position of any one RO in the third number of ROs (RO group) associated with the selected or indicated SSB index through RRC indication; wherein in each SSB to RO mapping cycle in the associated pattern period, the RO associated with the selected or indicated SSB index is numbered in ascending order of frequency resources first, and then in ascending order of time domain resources in the SSB to RO mapping cycle; and the index of one RO in the third number of ROs (RO group) in an SSB to RO mapping cycle in the associated pattern period is determined through RRC parameter indication.

[0224] For example, the position of any RO in the RO groups associated with the selected SSB index is indicated by an RRC parameter. Regarding the determination of the RO group index: Determined in the association pattern period, reference may be made to the aforementioned embodiments (e.g., FIG. 4 and related content). Regarding the indication of the RO group index, reference may also be made to the aforementioned embodiments (e.g., FIG. 4 and related content).

[0225] FIG. 17 and related content schematically illustrate that the RO is determined through RRC configuration. The RO can also be randomly selected.

[0226] FIG18 is another schematic diagram of a method for determining resources of a PRACH for carrying a system information request according to an embodiment of the present application. As shown in FIG18 , the method includes:

[0227] 1801. The terminal device determines a system information request (SI request) period, where the system information request period includes a second number (X2) of associated periods.

[0228] 1802. The terminal device determines an association period in which a third number of RO groups (RO groups) in which preambles are repeatedly transmitted.

[0229] Regarding the above 1801 and 1802, please refer to the above 1701 and 1702 and related contents respectively.

[0230] As shown in FIG18 , the method further includes:

[0231] 1803. The terminal device randomly selects the third number of ROs (RO groups) associated with the selected or indicated SSB index in the association pattern period.

[0232] For example, in the association pattern period indicated by the association pattern period index, an RO group associated with the selected SSB index is randomly selected.

[0233] The above schematically illustrates the situation where the system information request period includes the first number (X1) association periods, and the present application is not limited thereto. For example, the contents of Figures 17 and 18 can be combined. For example, when RRC configures the MSG1 repetition of SI request to send When the RO position of the preamble is not configured, the RO resource for sending the preamble is determined according to the RO index of the indicated starting RO, or the RO resource for sending the preamble is determined according to the indicated RO group index. When the RO position is not configured, the UE randomly selects the RO resource.

[0234] In some embodiments, the maximum value of the second number is X2max. X2max can be a fixed value, such as 8; or X2max is the number of association cycles when the time period reaches an upper limit; or X2max is a value configured by the network device.

[0235] FIG19 is another schematic diagram of a method for determining resources of a PRACH for carrying a system information request according to an embodiment of the present application. As shown in FIG19 , the method includes:

[0236] 1901. The terminal device determines a system information request (SI request) period, wherein the system information request period includes a first number (X1) of associated periods or a second number (X2) of associated pattern periods; and

[0237] 1902. The terminal device randomly selects the third number of ROs (RO groups) associated with the selected or indicated SSB index during the system information request period.

[0238] Regarding the above 1901, please refer to the aforementioned 401, 1502, 1701 and 1801 and related content.

[0239] The above schematically illustrates the embodiments of the present application, but the present application is not limited thereto. For example, when determining the RO group, a configuration-based determination method and a random selection method may be combined.

[0240] For example, the method of Figure 4 can be combined with random selection. In the case of RRC configuration association period index and / or RO index, the time to send MSG1 repetition is determined according to the configuration. In the absence of RRC configuration association period index and / or RO index, random selection is used to determine the time to send MSG1 repetition. ROs.

[0241] For another example, the method of Figure 15 can be combined with random selection. In the case of RRC configuration of association period index and / or RO index, the time of sending MSG1 repetition is determined according to the configuration. In the absence of RRC configuration association period index and / or RO index, random selection is used to determine the time to send MSG1 repetition. ROs.

[0242] For another example, the method of FIG17 can be combined with random selection. In the case of RRC configuration association pattern period index and / or RO index, the time of sending MSG1 repetition is determined according to the configuration. In the absence of RRC configuration association pattern period index and / or RO index, random selection is used to determine the time to send MSG1 repetition. ROs.

[0243] The following further explains the mask index.

[0244] In some embodiments, the situation where the PRACH mask index indication is used may be: the RO index indicated by the PRACH mask index is to number the RO associated with each SSB index in each SSB-to-RO mapping cycle, and the consecutive ROs of each SSB index in each mapping cycle will reset the mask index. The terminal device selects the RO indicated by the PRACH mask index in the first available mapping cycle for the indicated (or selected) SSB index. ROs for PRACH transmission with preamble repetitions.

[0245] In some embodiments, the situation where the PRACH mask index indication is used may be: if the terminal device selects the RO indicated by the PRACH mask index for the indicated SSB index to perform PRACH transmission of preamble repetition, the ROs cannot constitute a set of valid ROs for preamble transmissions, the terminal device does not use the set of ROs to perform PRACH transmission of preamble repetition, and the terminal device reselects the RO indicated by the PRACH mask index to perform PRACH transmission of preamble repetition.

[0246] Figure 20 is another example diagram of an RO according to an embodiment of the present application. As shown in Figure 20, with SSB indices ranging from 0 to 3, the ROs multiplex four resources in the frequency domain. For an MSG1 repetition with a repetition number of 4, if the preamble repetition is sent using an RO associated with SSB 0, since the ROs transmitting the preamble repetition share the same frequency domain resources, the ROs marked with dots can form an RO group with a repetition number of 4, while the ROs marked with slashes cannot form an RO group with a repetition number of 4.

[0247] If the terminal device selects the ROs marked with slashes to send preamble repetition according to the mask index indication, it cannot send the preamble repetition four times. Then the terminal device reselects the RO associated with SSB 0 indicated by the PRACH mask index to send the preamble repetition, that is, the terminal device reselects the ROs marked in orange to send the preamble repetition.

[0248] In an embodiment of the present application, the SI request period is determined so that the SI request period can cover the time domain resources sent by the preamble repetition, so that the terminal device can completely send the preamble repetition. And limiting the maximum value of the SI request period can reduce the delay of the terminal device in sending the SI request and improve the efficiency of the terminal device. In addition, by determining the SI request period, the consensus of the network device and the terminal device on the time domain resources of the preamble repetition in the SI request period is unified, avoiding ambiguity on the terminal device side. In addition, for the MSG1 repetition of the SI request, it is determined to send RO, which ensures that the terminal device effectively selects appropriate resources to send the preamble repetition.

[0249] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0250] It can be seen from the above embodiments that the system information request period can cover the time length of multiple PRACHs, can correctly indicate valid PRACH opportunities (ROs) and avoid ambiguity of terminal devices, and can also clearly indicate the RO positions of multiple PRACHs.

[0251] Embodiments of the second aspect

[0252] The embodiment of the present application provides a method for determining resources of a PRACH for carrying a system information request, which is described from the perspective of a network device. The embodiment of the second aspect can be combined with the embodiment of the first aspect, and the same contents as the embodiment of the first aspect will not be repeated.

[0253] FIG21 is a schematic diagram of a method for determining resources of a PRACH for carrying a system information request according to an embodiment of the present application. As shown in FIG21 , the method includes:

[0254] 2101, the network device sends configuration information of a PRACH for carrying a system information request to the terminal device;

[0255] 2102. The network device receives a PRACH preamble repeatedly sent by the terminal device on a third number of ROs.

[0256] The terminal device determines a system information request (SI request) period, wherein the system information request period includes a first number (X1) of associated periods or a second number (X2) of associated pattern periods; and determines a third number for repeatedly transmitting a PRACH preamble in the system information request (SI request) period. PRACH opportunity (RO).

[0257] It is worth noting that FIG21 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be removed. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG21 above.

[0258] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0259] It can be seen from the above embodiments that the system information request period can cover the time length of multiple PRACHs, can correctly indicate valid PRACH opportunities (ROs) and avoid ambiguity of terminal devices, and can also clearly indicate the RO positions of multiple PRACHs.

[0260] Embodiments of the third aspect

[0261] The embodiment of the present application provides a device for determining resources of a PRACH for carrying a system information request. The device may be, for example, a terminal device, or one or more components or assemblies configured in the terminal device, and the same contents as those in the embodiment of the first aspect are not repeated here.

[0262] FIG22 is a schematic diagram of a PRACH resource determination apparatus for carrying a system information request according to an embodiment of the present application. As shown in FIG22 , the PRACH resource determination apparatus 2200 for carrying a system information request includes:

[0263] A processing unit 2201 is configured to determine a system information request (SI request) period, wherein the system information request period includes a first number (X1) of associated periods or a second number (X2) of associated pattern periods; and determine a third number of PRACH preambles for repetitive transmission in the system information request (SI request) period. PRACH opportunity (RO).

[0264] In some embodiments, as shown in FIG22 , the apparatus 2200 for determining resources of a PRACH for carrying a system information request may further include:

[0265] A receiving unit 2202, configured to receive configuration information of a PRACH for carrying a system information request;

[0266] The sending unit 2203 is configured to repeatedly send the PRACH preamble on a third number of ROs.

[0267] In some embodiments, the system information request period includes a first number (X1) of association periods;

[0268] The first number is configured by the network device through RRC,

[0269] Alternatively, the first number is the minimum number of associated periods for repeated preamble transmission so that the fourth number of SSB indices are at least mapped to the third number of ROs, wherein the repeated preamble transmission is a PRACH transmission that repeatedly transmits a PRACH preamble on the third number of PRACH opportunities (ROs).

[0270] In some embodiments, the processing unit is further configured to: determine an association period in which the third number of ROs of the preamble are repeatedly sent.

[0271] In some embodiments, the associated period index during which the preamble is repeatedly transmitted is determined by RRC configuration.

[0272] In some embodiments, the processing unit determines, according to RRC configuration, positions of the third number of ROs (RO groups) to which the preamble is repeatedly transmitted in the association period.

[0273] In some embodiments, the position of the starting RO (starting RO or first RO) in the third number of ROs (RO group) associated with the selected or indicated SSB index is determined by RRC indication, and the remaining ROs in the third number of ROs (RO group) are adjacent ROs in the time domain associated with the same SSB index in the same frequency domain.

[0274] In some embodiments, all ROs associated with the selected or indicated SSB index are indexed within an SSB-to-RO mapping cycle; wherein within each SSB-to-RO mapping cycle in the determined association period, the ROs associated with the selected or indicated SSB index are indexed in ascending order of frequency resources first and then in ascending order of time domain resources; and the index of the starting RO (starting RO or first RO) in the selected third number of ROs (RO group) is determined by RRC parameter indication.

[0275] In some embodiments, the starting RO (starting RO or first RO) in the third number of ROs (RO group) associated with the selected or indicated SSB index is numbered (indexed) in the determined association period; wherein in the determined association period, the starting RO (starting RO or first RO) in the third number of ROs (RO group) associated with the selected or indicated SSB index is numbered in ascending order of frequency resources, and then numbered in ascending order of time domain resources in the association period; and the index of the starting RO (starting RO or first RO) in the third number of ROs (RO group) in the association period is determined by RRC parameter indication.

[0276] In some embodiments, the locations of the third number of ROs (RO groups) associated with the selected or indicated SSB index are determined by RRC indication;

[0277] In the determined association period, a third number of ROs (RO groups) associated with the selected or indicated SSB index are numbered in ascending order of frequency resources, and then numbered in ascending order of time domain resources in the association period; and the index of the third number of ROs (RO groups) in the association period is determined by RRC parameter indication.

[0278] In some embodiments, the position of any one of the third number of ROs (RO group) associated with the selected or indicated SSB index is determined by RRC indication;

[0279] In each SSB to RO mapping cycle in the determined association period, the RO associated with the selected or indicated SSB index is numbered in ascending order of frequency resources, and then in ascending order of time domain resources in the SSB to RO mapping cycle; and the index of an RO in the third number of ROs (RO group) in an SSB to RO mapping cycle in the association period is determined by RRC parameter indication.

[0280] In some embodiments, the processing unit randomly selects the third number of ROs (RO groups) associated with the selected or indicated SSB index during the association period.

[0281] In some embodiments, the maximum value of the first number is X1max; the X1max is a fixed value, or the number of associated periods when the time period reaches an upper limit, or a value configured by RRC.

[0282] In some embodiments, the system information request period includes a second number (X2) of association pattern periods;

[0283] The second number is configured by the network device through RRC, or the second number is a value determined based on a parameter configured by the network device through RRC, or the second number is the minimum number of associated pattern periods for repeated preamble transmission so that the fourth number of SSB indexes are at least mapped to the third number of ROs, wherein the repeated preamble transmission is a PRACH transmission that repeatedly transmits a PRACH preamble on the third number of PRACH opportunities (ROs).

[0284] In some embodiments, the processing unit is further configured to: determine an association pattern period in which the third number of ROs during the repeated transmission of the preamble occurs.

[0285] In some embodiments, the associated pattern period index in which the preamble is repeatedly transmitted is determined through RRC configuration.

[0286] In some embodiments, the processing unit is further configured to: determine, within an association pattern period, an association period in which the third number of ROs are repeatedly sent by the preamble.

[0287] In some embodiments, the associated period index during which the preamble is repeatedly transmitted is determined by RRC configuration.

[0288] In some embodiments, the processing unit is further configured to: determine, according to an RRC configuration, positions of the third number of ROs (RO groups) to which the preamble is repeatedly transmitted in the association period;

[0289] Alternatively, in the association period, the third number of ROs (RO groups) associated with the selected or indicated SSB index are randomly selected.

[0290] In some embodiments, the processing unit is further configured to: determine, according to RRC configuration, positions of the third number of ROs (RO groups) to which the preamble is repeatedly transmitted in the association pattern period.

[0291] In some embodiments, the position of the starting RO (starting RO or first RO) in the third number of ROs (RO group) associated with the selected or indicated SSB index is determined by RRC indication, and the remaining ROs in the third number of ROs (RO group) are adjacent ROs in the time domain associated with the same SSB index in the same frequency domain.

[0292] In some embodiments, all ROs associated with the selected or indicated SSB index are numbered within the SSB to RO mapping loop;

[0293] The SSB to RO mapping cycle where the starting RO (or first RO) of the third number of ROs (RO group) in the associated pattern period is located is determined in ascending order of frequency resources first and then in ascending order of time domain resources within the associated pattern period.

[0294] Within the indicated SSB to RO mapping loop, the ROs associated with the selected or indicated SSB index are numbered in ascending order of frequency resources first and then in ascending order of time domain resources within the SSB to RO mapping loop; and the index of the starting RO (starting RO or first RO) in the third number of ROs (RO group) is determined by RRC parameter indication.

[0295] In some embodiments, all ROs associated with the selected or indicated SSB index are numbered within the indicated associated pattern period.

[0296] In which, within the determined associated pattern period, the ROs associated with the selected or indicated SSB index are numbered in ascending order of frequency resources first and then in ascending order of time domain resources within the associated pattern period; and the index of the starting RO (starting RO or first RO) in the third number of ROs (RO group) within the associated pattern period is determined by RRC parameter indication.

[0297] In some embodiments, a starting RO (or first RO) of the third number of ROs (RO group) associated with the selected or indicated SSB index is numbered in the determined associated pattern period;

[0298] In which, within the determined associated pattern period, the starting RO (starting RO or first RO) in the third number of ROs (RO group) associated with the selected or indicated SSB index is numbered in ascending order of frequency resources first and then in ascending order of time domain resources within the associated pattern period; and the index of the starting RO (starting RO or first RO) in the third number of ROs (RO group) within the associated pattern period is determined by RRC parameter indication.

[0299] In some embodiments, the position of the third number of ROs (RO groups) associated with the selected or indicated SSB index is determined by RRC indication; wherein in the associated pattern period, the third number of ROs (RO groups) associated with the selected or indicated SSB index are numbered in ascending order of frequency resources, and then numbered in ascending order of time domain resources in the associated pattern period; and the index of the third number of ROs (RO groups) in the associated pattern period is determined by RRC parameter indication.

[0300] In some embodiments, the position of any one RO in the third number of ROs (RO group) associated with the selected or indicated SSB index is determined by RRC indication; wherein in each SSB to RO mapping cycle in the associated pattern period, the RO associated with the selected or indicated SSB index is numbered in ascending order of frequency resources first, and then in ascending order of time domain resources in the SSB to RO mapping cycle; and the index of one RO in the third number of ROs (RO group) in an SSB to RO mapping cycle in the associated pattern period is determined by RRC parameter indication.

[0301] In some embodiments, the processing unit is further configured to: randomly select the third number of ROs (RO groups) associated with the selected or indicated SSB index in the associated pattern period.

[0302] In some embodiments, the maximum value of the second number is X2max; X2max is a fixed value, or the number of associated pattern periods when the time period reaches an upper limit, or a value configured by RRC.

[0303] In some embodiments, the processing unit randomly selects the third number of ROs (RO groups) associated with the selected or indicated SSB index during the system information request period.

[0304] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The apparatus 2200 for determining transmission resources of a PRACH for carrying a system information request may also include other components or modules. For the specific contents of these components or modules, reference may be made to related technologies.

[0305] In addition, for the sake of simplicity, FIG22 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0306] Through the embodiments of the present application, the system information request period can cover the time length of multiple PRACHs, can correctly indicate the valid PRACH opportunities (RO) and avoid ambiguity of terminal devices, and can also clearly indicate the RO positions of multiple PRACHs.

[0307] Embodiments of the fourth aspect

[0308] The embodiment of the present application provides a device for determining resources of a PRACH for carrying a system information request. The device may be, for example, a network device, or one or more components or assemblies configured on the network device. The contents that are the same as those in the first and second aspects of the embodiment are not repeated here.

[0309] FIG23 is a schematic diagram of a PRACH resource determination apparatus for carrying a system information request according to an embodiment of the present application. As shown in FIG23 , the PRACH resource determination apparatus 2300 for carrying a system information request includes:

[0310] A sending unit 2301 sends configuration information of a PRACH for carrying a system information request to a terminal device;

[0311] a receiving unit 2302 configured to receive a PRACH preamble repeatedly sent by a terminal device on a third number of ROs;

[0312] The terminal device determines a system information request (SI request) period, wherein the system information request period includes a first number (X1) of associated periods or a second number (X2) of associated pattern periods; and determines a third number for repeatedly transmitting a PRACH preamble in the system information request (SI request) period. PRACH opportunity (RO).

[0313] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The PRACH resource determination device 2300 for carrying system information requests may also include other components or modules. For the specific contents of these components or modules, reference may be made to related technologies.

[0314] In addition, for the sake of simplicity, FIG23 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0315] Through the embodiments of the present application, the system information request period can cover the time length of multiple PRACHs, can correctly indicate the valid PRACH opportunities (RO) and avoid ambiguity of terminal devices, and can also clearly indicate the RO positions of multiple PRACHs.

[0316] Embodiments of the fifth aspect

[0317] An embodiment of the present application also provides a communication system, and reference may be made to FIG1 . The contents that are the same as those in the first to fourth aspects of the embodiments will not be repeated.

[0318] In some embodiments, the communication system 100 may include at least:

[0319] A network device that sends configuration information of a PRACH for carrying a system information request to a terminal device;

[0320] A terminal device, which determines a system information request (SI request) period, wherein the system information request period includes a first number (X1) of associated periods or a second number (X2) of associated pattern periods; and determines a third number for repeatedly transmitting a PRACH preamble (preamble) in the system information request (SI request) period. PRACH opportunity (RO).

[0321] An embodiment of the present application further provides a network device, which may be, for example, a base station, but the present application is not limited thereto and may also be other network devices.

[0322] Figure 24 is a schematic diagram of the structure of a network device according to an embodiment of the present application. As shown in Figure 24, network device 2400 may include a processor 2410 (e.g., a central processing unit (CPU)) and a memory 2420; the memory 2420 is coupled to the processor 2410. The memory 2420 may store various data and may also store an information processing program 2430, which is executed under the control of the processor 2410.

[0323] For example, the processor 2410 may be configured to execute a program to implement the method for determining resources of a PRACH for carrying a system information request as described in the embodiment of the second aspect. For example, the processor 2410 may be configured to perform the following control: sending configuration information of a PRACH for carrying a system information request to a terminal device; receiving a PRACH preamble repeatedly sent by the terminal device on a third number of ROs;

[0324] The terminal device determines a system information request (SI request) period, wherein the system information request period includes a first number (X1) of associated periods or a second number (X2) of associated pattern periods; and determines a third number for repeatedly transmitting a PRACH preamble in the system information request (SI request) period. PRACH opportunity (RO).

[0325] In addition, as shown in Figure 24, network device 2400 may further include: a transceiver 2440 and an antenna 2450; wherein, the functions of the above components are similar to those in the prior art and are not further described here. It is worth noting that network device 2400 does not necessarily include all the components shown in Figure 24; in addition, network device 2400 may also include components not shown in Figure 24, and reference may be made to the prior art.

[0326] The embodiment of the present application also provides a terminal device, but the present application is not limited thereto and may also be other devices.

[0327] Figure 25 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in Figure 25 , terminal device 2500 may include a processor 2510 and a memory 2520. Memory 2520 stores data and programs and is coupled to processor 2510. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication or other functions.

[0328] For example, the processor 2510 may be configured to execute a program to implement the resource determination method for a PRACH carrying a system information request as described in the embodiment of the first aspect. For example, the processor 2510 may be configured to perform the following control: determining a system information request (SI request) period, wherein the system information request period includes a first number (X1) of associated periods or a second number (X2) of associated pattern periods; and determining a third number of times for repeatedly transmitting a PRACH preamble (preamble) in the system information request (SI request) period. PRACH opportunity (RO).

[0329] As shown in Figure 25 , the terminal device 2500 may further include: a communication module 2530, an input unit 2540, a display 2550, and a power supply 2560. The functions of these components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 2500 does not necessarily include all of the components shown in Figure 25 , and these components are not essential. Furthermore, the terminal device 2500 may also include components not shown in Figure 25 , for which reference may be made to the prior art.

[0330] An embodiment of the present application also provides a computer program, wherein when the program is executed in a terminal device, the program enables the terminal device to execute the resource determination method for the PRACH used to carry the system information request described in the embodiment of the first aspect.

[0331] An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the resource determination method for a PRACH for carrying a system information request as described in the embodiment of the first aspect.

[0332] An embodiment of the present application also provides a computer program, wherein when the program is executed in a network device, the program enables the network device to execute the resource determination method for the PRACH used to carry the system information request described in the embodiment of the second aspect.

[0333] An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables a network device to execute the resource determination method for a PRACH for carrying a system information request as described in an embodiment of the second aspect.

[0334] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0335] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0336] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0337] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0338] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0339] Regarding the implementation methods including the above embodiments, the following additional notes are also disclosed:

[0340] 1. A method for determining transmission resources of a PRACH for carrying a system information request, comprising:

[0341] The terminal device determines a system information request (SI request) period, wherein the system information request period includes a first number (X1) of associated periods or a second number (X2) of associated pattern periods; and

[0342] The terminal device determines a third number for repeatedly sending a PRACH preamble in the system information request (SI request) period PRACH opportunity (RO).

[0343] 2. The method according to the supplementary note, wherein the system information request period includes a first number (X1) of association periods;

[0344] The first number is configured by the network device through RRC,

[0345] Alternatively, the first number is the minimum number of associated periods for repeated preamble transmission so that the fourth number of SSB indices are at least mapped to the third number of ROs, wherein the repeated preamble transmission is a PRACH transmission that repeatedly transmits a PRACH preamble on the third number of PRACH opportunities (ROs).

[0346] 3. The method according to Note 1, wherein the system information request period includes a second number (X2) of association pattern periods;

[0347] The second number is configured by the network device through RRC, or the second number is a value determined based on a parameter configured by the network device through RRC, or the second number is the minimum number of associated pattern periods for repeated preamble transmission so that the fourth number of SSB indexes are at least mapped to the third number of ROs, wherein the repeated preamble transmission is a PRACH transmission that repeatedly transmits a PRACH preamble on the third number of PRACH opportunities (ROs).

[0348] 4. The method according to Supplementary Note 3, wherein the method further comprises:

[0349] The terminal device determines an association pattern period in which the third number of ROs in the preamble are repeatedly sent.

[0350] 5. The method according to Note 4, wherein the terminal device determines the positions of the third number of ROs (RO groups) to which the preamble is repeatedly transmitted in the association pattern period according to RRC configuration.

[0351] 6. The method according to Note 5, wherein the position of the starting RO (starting RO or first RO) in the third number of ROs (RO group) associated with the selected or indicated SSB index is determined by RRC indication, and the remaining ROs in the third number of ROs (RO group) are adjacent ROs in the time domain associated with the same SSB index in the same frequency domain.

[0352] 7. The method according to note 6, wherein all ROs associated with the selected or indicated SSB index are numbered within the SSB to RO mapping loop;

[0353] The SSB to RO mapping cycle where the starting RO (or first RO) of the third number of ROs (RO group) in the associated pattern period is located is determined in ascending order of frequency resources first and then in ascending order of time domain resources within the associated pattern period.

[0354] In the SSB to RO mapping loop, the ROs associated with the selected or indicated SSB index are numbered in ascending order of frequency resources first and then in ascending order of time domain resources in the SSB to RO mapping loop; and the index of the starting RO (starting RO or first RO) in the third number of ROs (RO group) is determined by RRC parameter indication.

[0355] 8. The method according to Note 6, wherein all ROs associated with the selected or indicated SSB index are numbered within the determined associated pattern period.

[0356] Wherein, within the associated pattern period, the ROs associated with the selected or indicated SSB index are numbered in ascending order of frequency resources first and then in ascending order of time domain resources within the associated pattern period; and the index of the starting RO (starting RO or first RO) in the third number of ROs (RO group) within the associated pattern period is determined by RRC parameter indication.

[0357] 9. The method according to supplementary note 6, wherein a starting RO (or first RO) in the third number of ROs (RO group) associated with the selected or indicated SSB index is numbered in the determined associated pattern period;

[0358] Wherein, within the associated pattern period, the starting RO (starting RO or first RO) in the third number of ROs (RO group) associated with the selected or indicated SSB index is numbered in ascending order of frequency resources first and then in ascending order of time domain resources within the associated pattern period; and the index of the starting RO (starting RO or first RO) in the third number of ROs (RO group) within the associated pattern period is determined by RRC parameter indication.

[0359] 10. The method according to Supplementary Note 1, wherein the method further comprises:

[0360] The terminal device randomly selects the third number of ROs (RO groups) associated with the selected or indicated SSB index during the system information request period.

Claims

1. A resource determination device for a PRACH carrying a system information request, configured in a terminal device, the device comprising: a processing unit, configured to determine a system information request period, wherein the system information request period includes a first number of associated periods or a second number of associated pattern periods; And determining a third number of PRACH opportunities for repeatedly sending the PRACH preamble in the system information request period.

2. The device according to claim 1, wherein: The system information request period includes a first number of association periods; The first number is configured by the network device through radio resource control, Alternatively, the first number is the minimum number of associated periods for repeated transmission of the preamble so that the fourth number of SSB indices are at least mapped to the third number of PRACH opportunities, wherein the repeated transmission of the preamble is a PRACH transmission that repeatedly transmits the PRACH preamble on the third number of PRACH opportunities.

3. The device according to claim 2, wherein: The processing unit is further configured to: determine an associated period in which the third number of PRACH opportunities in which the preamble is repeatedly transmitted; The associated period index where the preamble is repeatedly sent is determined through radio resource control configuration.

4. The device according to claim 3, wherein: The processing unit determines, according to a radio resource control configuration, positions of the third number of PRACH opportunities at which the preamble is repeatedly transmitted in the association period.

5. The device according to claim 4, wherein: The position of the starting PRACH opportunity among the third number of PRACH opportunities associated with the selected or indicated SSB index is determined through a wireless resource control indication, and the remaining PRACH opportunities among the third number of PRACH opportunities are adjacent PRACH opportunities in the time domain associated with the same SSB index in the same frequency domain.

6. The device according to claim 5, wherein: All PRACH opportunities associated with the selected or indicated SSB index are numbered in an SSB to RO mapping cycle; wherein in each SSB to RO mapping cycle in the determined association period, the PRACH opportunities associated with the selected or indicated SSB index are numbered in the order of first frequency resources in ascending order and then time domain resources in ascending order; and the index of the starting PRACH opportunity in the selected third number of PRACH opportunities is determined by a radio resource control parameter indication; or, The third number of associated SSBs with the selected or indicated SSB index in the determined association period The starting PRACH opportunity in the PRACH opportunities of the determined association period is numbered; wherein in the determined association period, the starting PRACH opportunity in the third number of PRACH opportunities associated with the selected or indicated SSB index is numbered in ascending order of frequency resources, and then numbered in ascending order of time domain resources in the association period; and the index of the starting PRACH opportunity in the third number of PRACH opportunities in the association period is determined by indicating the wireless resource control parameter.

7. The device according to claim 4, wherein: determining, by radio resource control indication, positions of the third number of PRACH opportunities associated with the selected or indicated SSB index; In which, in the determined association period, a third number of PRACH opportunities associated with the selected or indicated SSB index are numbered in ascending order of frequency resources, and then numbered in ascending order of time domain resources in the association period; and the index of the third number of PRACH opportunities is determined in the association period through the wireless resource control parameter indication.

8. The device according to claim 4, wherein: Determining, by radio resource control indication, a position of any one of the third number of PRACH opportunities associated with the selected or indicated SSB index; In which, in each SSB to RO mapping cycle in the determined association period, the PRACH opportunities associated with the selected or indicated SSB index are numbered in ascending order of frequency resources first, and then in ascending order of time domain resources in the SSB to RO mapping cycle; and the index of one of the third number of PRACH opportunities in a SSB to RO mapping cycle in the association period is determined by indicating a wireless resource control parameter.

9. The device according to claim 3, wherein: The terminal device randomly selects the third number of PRACH opportunities associated with the selected or indicated SSB index during the association period.

10. The device according to claim 2, wherein: The maximum value of the first number is X1max; the X1max is a fixed value, or the number of associated periods when the time period reaches an upper limit, or a value configured by radio resource control.

11. The device according to claim 1, wherein: The system information request period includes a second number of associated pattern periods; The second number is configured by the network device through radio resource control, or the second number is a value determined based on a parameter configured by the network device through radio resource control, or the second number is an association pattern that the preamble repeatedly sends so that the fourth number of SSB indexes are mapped to at least the third number of PRACH opportunities The minimum number of cycles, wherein the repeated transmission of the preamble is a PRACH transmission of the PRACH preamble repeatedly transmitted on the third number of PRACH opportunities.

12. The device according to claim 11, wherein The processing unit is further configured to: determine an associated pattern period in which the third number of PRACH opportunities in which the preamble is repeatedly transmitted are located; The associated pattern period index where the preamble is repeatedly sent is determined through radio resource control configuration.

13. The device according to claim 12, wherein: The processing unit is further configured to: determine, in an association pattern period, an association period in which the third number of PRACH opportunities in which the preamble is repeatedly sent is located; The associated period index where the preamble is repeatedly sent is determined through radio resource control configuration.

14. The device according to claim 13, wherein: The processing unit is further configured to: determine, according to a radio resource control configuration, positions of the third number of PRACH opportunities at which the preamble is repeatedly transmitted in the association period; Alternatively, in the association period, the third number of PRACH opportunities associated with the selected or indicated SSB index are randomly selected.

15. The device according to claim 12, wherein: The processing unit is further configured to: determine, according to a radio resource control configuration, positions of the third number of PRACH opportunities at which the preamble is repeatedly transmitted in the association pattern period.

16. The device according to claim 15, wherein: Determine, by radio resource control indication, a position of a starting PRACH opportunity in the third number of PRACH opportunities associated with the selected or indicated SSB index, the remaining PRACH opportunities in the third number of PRACH opportunities being adjacent PRACH opportunities in the time domain associated with the same SSB index in the same frequency domain; or, Determining the position of the third number of PRACH opportunities associated with the selected or indicated SSB index through a radio resource control indication; wherein in the associated pattern period, the third number of PRACH opportunities associated with the selected or indicated SSB index are numbered in ascending order of frequency resources, and then numbered in ascending order of time domain resources in the associated pattern period; and determining the index of the third number of PRACH opportunities in the associated pattern period through a radio resource control parameter indication; or, Determine the position of any one of the third number of PRACH opportunities associated with the selected or indicated SSB index through a radio resource control indication; wherein each of the associated pattern periods In a SSB to RO mapping cycle, the PRACH opportunities associated with the selected or indicated SSB index are numbered in ascending order of frequency resources first, and then in ascending order of time domain resources in the SSB to RO mapping cycle; and the index of one PRACH opportunity in the third number of PRACH opportunities in a SSB to RO mapping cycle in the associated pattern period is determined by a wireless resource control parameter indication.

17. The device according to claim 12, wherein: The processing unit is further configured to randomly select the third number of PRACH opportunities associated with the selected or indicated SSB index in the associated pattern period.

18. The device according to claim 11, wherein The maximum value of the second number is X2max; the X2max is a fixed value, or the number of associated pattern periods when the time period reaches an upper limit, or a value configured by radio resource control.

19. A resource determination device for a PRACH carrying a system information request, configured in a network device, the device comprising: A sending unit, which sends configuration information of a PRACH for carrying a system information request to a terminal device; A receiving unit, which receives the PRACH preamble repeatedly sent by the terminal device on a third number of PRACH opportunities; wherein the terminal device determines a system information request period, the system information request period includes a first number of associated periods or a second number of associated pattern periods; and determines a third number of PRACH opportunities for repeatedly sending the PRACH preamble in the system information request period.

20. A communication system comprising: A network device, which sends configuration information of a PRACH for carrying a system information request to a terminal device; A terminal device determines a system information request period, wherein the system information request period includes a first number of associated periods or a second number of associated pattern periods; and determines a third number of PRACH opportunities for repeatedly sending a PRACH preamble in the system information request period.

Images