Method, terminal device and base station for random access process

Abstract

A method, a terminal device and a base station for a random access procedure are disclosed. According to one embodiment, the terminal device determines a frequency hopping configuration for sending one or more physical uplink shared channels (PUSCHs) in a request message for random access. The terminal device sends the one or more PUSCHs in the request message based on the frequency hopping configuration. The request message includes at least a physical random access channel (PRACH) preamble and the one or more PUSCHs.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to wireless communications, and more particularly to methods, terminal devices, and base stations for random access procedures. Background Art

[0002] This section introduces aspects that may facilitate a better understanding of the present disclosure. Therefore, the statements in this section should be read in this sense, and should not be understood as an admission of what is or is not prior art.

[0003] In New Radio (NR) systems, such as Figure 1 The four-step method shown can be used for the random access procedure. In this method, the user equipment (UE) detects the synchronization signal (SS), decodes the broadcast system information (which can be distributed on multiple physical channels (e.g., physical broadcast channel (PBCH) and physical downlink shared channel (PDSCH))) to obtain random access transmission parameters, and then sends a physical random access channel (PRACH) preamble (message 1, referred to as msg1) on the uplink. The next generation Node B (gNB) detects message 1 and responds with a random access response (RAR, message 2, referred to as msg2). The UE then sends a UE identity (message 3, referred to as msg3) on the physical uplink shared channel (PUSCH). The gNB then sends a contention resolution message (CRM, message 4, referred to as msg4) to the UE to resolve the conflict caused when multiple UEs send the same PRACH preamble. Summary of the invention

[0004] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0005] One of the objectives of the present disclosure is to provide another solution for the random access procedure.

[0006] According to a first aspect of the present disclosure, a method performed by a terminal device is provided. The method includes determining a frequency hopping configuration for sending one or more physical uplink shared channels (PUSCHs) in a request message for random access. The method also includes sending the one or more PUSCHs in the request message based on the frequency hopping configuration. The request message includes at least a physical random access channel (PRACH) preamble and the one or more PUSCHs.

[0007] In an embodiment of the present disclosure, the frequency hopping configuration may include one or more parameters indicating: enabling and / or disabling of frequency hopping; a starting physical resource block (PRB) for frequency hopping; a frequency offset for frequency hopping; a frequency hopping type, which is one of intra-slot hopping, inter-slot hopping, intra-PUSCH opportunity (PO, PUSCH occasion) hopping, and inter-PO hopping; the number of time slots spanned by the one or more PUSCHs; and a redundancy version (RV) for more than one PUSCH.

[0008] In an embodiment of the present disclosure, the frequency hopping configuration may be determined based on radio resource control (RRC) signaling. In this way, the PUSCH of the request message for random access can be sent using an appropriate frequency hopping configuration.

[0009] In an embodiment of the present disclosure, the RRC signaling may be cell-specific RRC signaling, or RRC signaling specific to the terminal device.

[0010] In an embodiment of the present disclosure, when the frequency offset is not configured in the RRC signaling, the terminal device may determine to disable frequency hopping.

[0011] In an embodiment of the present disclosure, when the frequency offset is set to zero in the RRC signaling, the terminal device may determine to disable frequency hopping.

[0012] In an embodiment of the present disclosure, the one or more parameters in the frequency hopping configuration may be determined as a predetermined value. In this way, the PUSCH of the request message for random access can be sent using an appropriate frequency hopping configuration.

[0013] In an embodiment of the present disclosure, the one or more parameters in the frequency hopping configuration may be determined based on the PRACH configuration used for the PRACH preamble. In this way, the PUSCH for the request message for random access can be sent using an appropriate frequency hopping configuration.

[0014] In an embodiment of the present disclosure, the PRACH configuration for the PRACH preamble code may include one or more of the following: an extended PRACH configuration table, one or more parameters in the frequency hopping configuration can be retrieved from the extended PRACH configuration table according to a PRACH configuration index; the number of PRACH opportunities; the starting PRB of the PRACH preamble code; and whether to perform random access as contention-based random access (CBRA) or random access as contention-free random access (CFRA).

[0015] In an embodiment of the present disclosure, when the number of PRACH opportunities adopts a predetermined value, the terminal device may determine to enable frequency hopping.

[0016] In an embodiment of the present disclosure, the frequency offset used for frequency hopping may be determined as a function of the number of PRACH opportunities.

[0017] In an embodiment of the present disclosure, the starting PRB for frequency hopping may be determined as a function of the number of the PRACH opportunities and / or the starting PRB of the PRACH preamble.

[0018] In an embodiment of the present disclosure, the one or more parameters in the frequency hopping configuration may be determined based on the PUSCH configuration used for the request message. In this way, the PUSCH of the request message for random access can be sent using an appropriate frequency hopping configuration.

[0019] In an embodiment of the present disclosure, the PUSCH configuration used for the request message may include one or more parameters indicating: enabling and / or disabling of transform precoding; the number of PRBs spanned by one or more POs of one or more sizes; the location of the PO to be used; the size of the PO set to be used; the location of the PO set to be used; the starting PRB of the PO for the first hop; and the starting PRB of the PO set to be used.

[0020] In an embodiment of the present disclosure, the frequency offset used for frequency hopping may be determined as a function of at least one of: the number of PRBs spanned by the one or more POs having one or more sizes; and the location of the PO to be used.

[0021] In an embodiment of the present disclosure, the frequency offset may be determined as a scaling factor multiplied by the number of PRBs spanned by the one or more POs having one or more sizes.

[0022] In an embodiment of the present disclosure, the starting PRB for frequency hopping can be determined as a function of at least one of: the number of PRBs spanned by the one or more POs having one or more sizes; the starting PRB of the PO used for the first hop; and the starting PRB of the PO set to be used.

[0023] In an embodiment of the present disclosure, the one or more parameters in the frequency hopping configuration may be determined based on one or more of the following: whether the cell serving the terminal device uses frequency division duplex (FDD) or time division duplex (TDD); the different frequency bands in which the terminal device operates; whether a conventional uplink carrier or a supplementary uplink carrier will be used for the random access; whether the random access will be performed in an initial active uplink bandwidth part (BWP); and the size of the active BWP. In this way, the PUSCH for the request message for random access can be sent using an appropriate frequency hopping configuration.

[0024] In an embodiment of the present disclosure, the frequency offset used for frequency hopping may be determined based on the size of the active BWP.

[0025] In an embodiment of the present disclosure, the method may further include providing user data, and forwarding the user data to the host via transmission to the base station.

[0026] According to a second aspect of the present disclosure, a method performed by a base station is provided. The method includes determining a frequency hopping configuration to be used by a terminal device to send one or more PUSCHs in a request message for random access. The method also includes receiving the one or more PUSCHs in a request message for random access based on the frequency hopping configuration.

[0027] In an embodiment of the present disclosure, the frequency hopping configuration may include one or more parameters indicating: enabling and / or disabling of frequency hopping; the starting PRB for frequency hopping; the frequency offset for frequency hopping; the frequency hopping type, which is one of intra-slot hopping, inter-slot hopping, intra-PO hopping, and inter-PO hopping; the number of time slots spanned by the one or more PUSCHs; and the RV for more than one PUSCH.

[0028] According to a third aspect of the present disclosure, a terminal device is provided. The terminal device includes at least one processor and at least one memory. The at least one memory contains instructions executable by the at least one processor, whereby the terminal device is operable to determine a frequency hopping configuration for sending one or more PUSCHs in a request message for random access. The terminal device is also operable to send the one or more PUSCHs in the request message based on the frequency hopping configuration. The request message includes at least a PRACH preamble and the one or more PUSCHs.

[0029] In an embodiment of the present disclosure, the terminal device may be operable to execute the method according to the first aspect above.

[0030] According to a fourth aspect of the present disclosure, a base station is provided. The base station comprises at least one processor and at least one memory. The at least one memory contains instructions executable by the at least one processor, whereby the base station is operable to determine a frequency hopping configuration to be used by a terminal device to send one or more PUSCHs in a request message for random access. The base station is also operable to receive the one or more PUSCHs in a request message for random access based on the frequency hopping configuration.

[0031] In an embodiment of the present disclosure, the base station may be operable to execute the method according to the second aspect above.

[0032] According to a fifth aspect of the present disclosure, a computer program product is provided, wherein the computer program product comprises instructions, and when the instructions are executed by at least one processor, the at least one processor executes the method according to any one of the first and second aspects.

[0033] According to a sixth aspect of the present disclosure, a computer-readable storage medium is provided, wherein the computer-readable storage medium contains instructions, and when the instructions are executed by at least one processor, the at least one processor executes the method according to any one of the first and second aspects.

[0034] According to a seventh aspect of the present disclosure, a terminal device is provided. The terminal device includes a determination module, configured to determine a frequency hopping configuration for sending one or more PUSCHs in a request message for random access. The terminal device includes a sending module, configured to send the one or more PUSCHs in the request message based on the frequency hopping configuration. The request message includes at least a PRACH preamble and the one or more PUSCHs.

[0035] According to an eighth aspect of the present disclosure, a base station is provided. The base station includes a determination module for determining a frequency hopping configuration to be used by a terminal device to send one or more PUSCHs in a request message for random access. The base station also includes a receiving module for receiving the one or more PUSCHs in a request message for random access based on the frequency hopping configuration.

[0036] According to the ninth aspect of the present disclosure, a method implemented in a communication system is provided. The method comprises: at a base station, determining a frequency hopping configuration to be used by a terminal device to send one or more PUSCHs in a request message for random access. The method also comprises: at the terminal device, determining the frequency hopping configuration for sending one or more PUSCHs in a request message for random access. The method also comprises: at the terminal device, based on the frequency hopping configuration, sending the one or more PUSCHs in the request message. The request message comprises at least a PRACH preamble and the one or more PUSCHs. The method also comprises: at the base station, based on the frequency hopping configuration, receiving the one or more PUSCHs in the request message for random access.

[0037] According to the tenth aspect of the present disclosure, a communication system is provided. The communication system includes a base station, which is configured to: determine a frequency hopping configuration to be used by a terminal device to send one or more PUSCHs in a request message for random access; and based on the frequency hopping configuration, receive the one or more PUSCHs in the request message for random access. The communication system also includes the terminal device, which is configured to: determine the frequency hopping configuration for sending one or more PUSCHs in the request message for random access; and based on the frequency hopping configuration, send the one or more PUSCHs in the request message. The request message includes at least a PRACH preamble and the one or more PUSCHs. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] These and other objects, features and advantages of the present disclosure will become apparent from the following detailed description of illustrative embodiments of the present disclosure, which is to be read in connection with the accompanying drawings.

[0039] Figure 1 is a diagram illustrating a four-step random access procedure in NR;

[0040] Figure 2 is a diagram illustrating a two-step random access procedure in NR;

[0041] Figure 3 is a diagram showing a PUSCH set for msgA;

[0042] Figure 4 is a diagram showing a PRACH configuration in NR;

[0043] Figure 5 is a flowchart illustrating a method implemented at a terminal device according to an embodiment of the present disclosure;

[0044] Figure 6 is a flow chart showing a method implemented at a base station according to an embodiment of the present disclosure;

[0045] Figure 7 is a block diagram illustrating an apparatus suitable for use in practicing some embodiments of the present disclosure;

[0046] Figure 8 is a block diagram showing a terminal device according to an embodiment of the present disclosure;

[0047] Fig. 9 is a block diagram illustrating a base station according to an embodiment of the present disclosure;

[0048] Fig.10 is a diagram illustrating a telecommunications network connected to a host via an intermediate network according to some embodiments;

[0049] Fig.11is a diagram illustrating a host communicating with a user equipment via a base station according to some embodiments;

[0050] Fig.12 is a flow chart illustrating a method implemented in a communication system according to some embodiments;

[0051] Fig.13 is a flow chart illustrating a method implemented in a communication system according to some embodiments;

[0052] Fig.14 is a flow chart illustrating a method implemented in a communication system according to some embodiments; and

[0053] Fig.15 is a flow chart illustrating a method implemented in a communication system according to some embodiments. DETAILED DESCRIPTION

[0054] For purposes of explanation, certain details are set forth in the following description in order to provide a thorough understanding of the disclosed embodiments. However, it is apparent to one skilled in the art that the embodiments may be practiced without these specific details or with an equivalent configuration.

[0055] In the four-step random access procedure, the UE sends a PUSCH (message 3) after receiving the timing advance command in the RAR and after adjusting the timing of the PUSCH transmission, allowing the PUSCH to be received at the gNB with a timing accuracy within the cyclic prefix (CP). Without this timing advance functionality, a very large CP would be required to be able to demodulate and detect the PUSCH unless the system is applied in a cell with a very small distance between the UE and the gNB. Since NR will also support larger cells, there is a need to provide timing advance to the UE and therefore the random access procedure requires a four-step approach.

[0056] Figure 2 The 2-step random access process is shown in FIG. Figure 2 As shown, in the 2-step random access process, the steps of detecting synchronization signal (SS) / PBCH blocks and system information are the same as those in the 4-step method, but the initial access is completed in only two steps to minimize the number of channel accesses. At the first step, the UE sends a request message for random access (which can be represented as message A, abbreviated as msgA), which includes, for example, a random access preamble and higher layer data (such as RRC connection request) and may have some additional payload on PUSCH. At the second step, the gNB sends a response message (which can be represented as message B, abbreviated as msgB), which includes, for example, UE identifier allocation, timing advance information, and contention resolution information.

[0057] In NR Release 15 (Rel-15), msg3 frequency hopping is enabled or disabled by a frequency hopping flag indicated in a RAR message for initial msg3 transmission, as shown in the following Table 1 (see Table 8.2-1) copied from the 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 38.213 V15.5.0, and msg3 frequency hopping is indicated in a downlink control information (DCI) format for retransmission of msg3, the DCI format having a cyclic redundancy check (CRC) scrambled by a temporary cell radio network temporary identifier (TC-RNTI).

[0058] RAR Authorization Field Number of bits <![CDATA[ Frequency Hopping Flag ]]> 1 PUSCH frequency resource allocation 14 PUSCH time resource allocation 4 MCS 4 TPC commands for PUSCH 3 CSI Request 1

[0059] Table 1: Random access response grant content field size

[0060] Specifically, the "frequency hopping flag" indicated in the DCI format 0_0 with the CRC scrambled by the TC-RNTI is a frequency hopping flag occupying 1 bit according to Table 7.3.1.1.1-3 defined in subclause 6.3 of TS38.214 V15.5.0.

[0061] For msg3 PUSCH transmission, frequency hopping is not allowed for PUSCH transmission with resource allocation type 0, which cannot be used when transform precoding is enabled or when PUSCH is scheduled by DCI format 0_0 or RAR. In addition, there are two types of PUSCH frequency hopping, namely intra-slot frequency hopping or inter-slot frequency hopping. Inter-slot frequency hopping is only applied to multi-slot PUSCH transmission.

[0062] msgAPUSCH can be sent on time / frequency (T / F) resources called PUSCH opportunities (PO, PUSCH occasion). A resource set containing multiple PUSCH opportunities can be defined. For example, it can be called a "msgA PUSCH set". A PUSCH resource unit (PUSCH RU) can be defined as a PUSCH opportunity (PO) for msgA payload transmission and a demodulation reference signal (DMRS) port / DMRS sequence. PUSCH RU allows multi-user multiple input multiple output (MU-MIMO) reception. Each PUSCH RU occupies a set of consecutive subcarriers and symbols. The msgA PUSCH set appears periodically and has a known symbol length and frequency position. The msgA PUSCH set may contain multiple POs that are consecutive in frequency and time (including guard bands or periods, if defined).

[0063] A PUSCH RU has "K" PRBs. K may vary, and a given PRB may contain PUSCH RUs of different sizes. K is identified by the preamble used. If a PRB contains PUSCH RUs of different sizes K, the DMRS identifier (ID) may be a function of that size. That is, Total #DMRS = (#PO size) x (PUSCH RUs per PO). The UE may randomly select a PUSCH RU index "n" from the configured set.

[0064] In NR Release 15, the time and frequency resources on which the PRACH preamble is sent are defined as PRACH occasions. In the present disclosure, a PRACH occasion may also be referred to as a RACH opportunity, or a random access (RA) opportunity, or simply as a RO. A RO used to send a preamble in a 2-step RA may be referred to as a 2-step RO, and a RO used to send a preamble in a 4-step RA may be referred to as a 4-step RO.

[0065] The time resource and preamble format for PRACH transmission are configured by a PRACH configuration index, which indicates a row in the PRACH configuration table specified in Tables 6.3.3.2-2, 6.3.3.2-3, 6.3.3.2-4 of TS 38.211 (for FR1 paired spectrum, FR1 unpaired spectrum, and FR2 with unpaired spectrum, respectively). FR1 represents a first frequency range, such as a low frequency range. FR2 represents a second frequency range, such as a high frequency range.

[0066] For example, in Table 6.3.3.2-3 for FR1 unpaired spectrum, for PRACH preamble format 0, the value of x indicates the PRACH configuration period expressed in the number of system frames. The value of y indicates the system frame on which the PRACH opportunity is configured within each PRACH configuration period. For example, if y is set to 0, it means PRACH opportunities configured only in the first frame of each PRACH configuration period. The values ​​in the column "Subframe number" tell on which subframes the PRACH opportunity is configured. The values ​​in the column "Starting symbol" are the symbol indexes.

[0067] In the case of TDD, the semi-statically configured downlink (DL) part and / or the synchronization signal block (SSB) actually transmitted can override some time domain PRACH opportunities defined in the PRACH configuration table and make them invalid. More specifically, the PRACH opportunities in the uplink (UL) part are always valid, and the PRACH opportunities in the X part are valid as long as the following conditions are met: the PRACH opportunity is not before or conflicts with the SSB in the RACH time slot, and the PRACH opportunity is at least N symbols after the last symbol of the DL part and the SSB. N is 0 or 2, depending on the PRACH format and the subcarrier spacing.

[0068] In the frequency domain, NR supports multiple frequency-multiplexed PRACH opportunities on the same time domain PRACH opportunity. This is mainly motivated by the fact that analog beam scanning is supported in NR so that the PRACH opportunities associated with one SSB are configured at the same time instant but at different frequency locations. The number of frequency division multiplexed (FDM) PRACH opportunities in one time domain PRACH opportunity can be 1, 2, 4, or 8. Figure 4 An example of PRACH opportunity configuration in NR is given.

[0069] In NR Release 15, for each PRACH opportunity in each cell, there are up to 64 sequences that can be used as random access preambles. The RRC parameter totalNumberOfRA-Preambles determines how many of these 64 sequences are used as random access preambles for each PRACH opportunity in each cell. The 64 sequences are configured by first including all available cyclic shifts of the root Zadoff-Chu sequence, and then in order of increasing root index until 64 preambles have been generated for this PRACH opportunity.

[0070] Unlike msg3 PUSCH, msgA PUSCH is not scheduled by any signaling or message for initial transmission. Therefore, it is desirable to provide a method on how to enable or disable msgA PUSCH frequency hopping, at least for the initial transmission of msgA PUSCH.

[0071] Furthermore, whether inter-slot frequency hopping will be supported or intra-slot frequency hopping will be supported may depend on the msgA PUSCH transmission scheme, such as whether msgA PUSCH repetition is supported for msgA PUSCH.The PUSCH resource allocation type may also need to be considered as it will affect the possibility of frequency hopping.

[0072] The present disclosure proposes an improved solution for a 2-step random access process. The solution can be applied to a wireless communication system including a terminal device and a base station. The terminal device can communicate with the base station via a radio access communication link. The base station can provide a radio access communication link to a terminal device in its communication service cell. The base station can be, for example, a gNB in ​​NR. It should be noted that communication can be performed between the terminal device and the base station according to any suitable communication standard and protocol. The terminal device may also be referred to as, for example, a device, an access terminal, a user equipment (UE), a mobile station, a mobile unit, a user station, etc. The terminal device may refer to any terminal device that can access a wireless communication network and receive services therefrom. By way of example and not limitation, the terminal device may include a portable computer, an image capture terminal device such as a digital camera, a game terminal device, a music storage and playback device, a mobile phone, a cellular phone, a smart phone, a tablet computer, a wearable device, a personal digital assistant (PDA), etc.

[0073] In the Internet of Things (IoT) scenario, a terminal device may refer to a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another terminal device and / or network device. In this case, the terminal device may be a machine-to-machine (M2M) device, which may be referred to as a machine type communication (MTC) device in the context of the 3rd Generation Partnership Project (3GPP). Specific examples of such machines or devices may include sensors, metering devices such as power meters, industrial machinery, bicycles, vehicles, or household or personal appliances (e.g., refrigerators, televisions), personal wearable devices (such as watches), and the like.

[0074] Now, several embodiments will be described to explain the improved solution for the random access procedure. As a first embodiment, msgA PUSCH frequency hopping and / or frequency offset can be configured in an RRC message, which can be a cell-specific message and / or a UE-specific RRC message. When the UE is in RRC connected mode, the UE-specific message can be used.

[0075] As an example, in the PUSCH-ConfigCommon information element (IE), the underlined parameters given below may be configured for cell-specific signaling to control msgA PUSCH frequency hopping.

[0076]

[0077]

[0078]

[0079] As another example, in the PUSCH-Config IE, similar parameters may be configured for UE-specific signaling to control msgA PUSCH frequency hopping.

[0080] As a second embodiment, the frequency offset may be predetermined. As a first option, the frequency offset is equal to where f is the scaling factor and is the total span of PRBs occupied by PUSCH PO. As an example, f may take a predefined value. Possible values ​​may include, but are not limited to, 1, 1 / 2, and 1 / 4. As another example, f may be a value signaled from the network.

[0081] As a second option, the frequency offset can be associated with one or more of the following factors. The first factor is the total number of PRBs spanned by the PUSCH opportunity. For example, the RB offset value should not be less than the maximum total number of PRBs occupied by the msgA PUSCH opportunity of the first hop. The PUSCH opportunity can have one or more sizes. The second factor is the size of the active BWP in which the msgA is sent as part of the random access process. The third factor is the location of the PUSCH opportunity. For example, when an msgA PUSCH in a current opportunity is to be repeated in another opportunity, the other opportunity can be determined by the current opportunity to ensure that they are on different PRBs within the PUSCH opportunity set. The fourth factor is the number of PRBs used for one PUSCH opportunity. The fifth factor is the location and size of the PUSCH opportunity set.

[0082] As a third option, the frequency offset is relative to the starting PRB, which may be the starting PRB for the first hop PUSCH opportunity, the starting PRB of the PUSCH opportunity set, or a function of the starting PRB for the corresponding RACH opportunity for the corresponding msgA preamble transmission. Note that the starting PRB may be signaled in an RRC message, such as in a system information block type 1 (SIB1).

[0083] As a third embodiment, the frequency hopping flag may be implicitly indicated by the configuration offset. As an example, when the frequency offset is not configured, this means that frequency hopping is not enabled. As another example, when the frequency offset is set to 0, there is no frequency hopping.

[0084] As a fourth embodiment, the frequency hopping type for msgA PUSCH may be one or more of the following: intra-slot, inter-slot, intra-PO, and inter-PO. Intra-slot means that frequency hopping is performed within the slot allocated for PUSCH. Inter-slot means that when multi-slot transmission is supported for msgA PUSCH, frequency hopping is applied between slots. Here, multi-slot transmission may be one of the following: 1) msgA PUSCH is repeated in different slots, but on the same orthogonal frequency division multiplexing (OFDM) symbol in each slot; 2) msgA PUSCH is repeated in different slots and also on different OFDM symbols in each slot. Intra-PO means that msgA PUSCH can be repeated within one PO set, but on different PRBs to achieve frequency diversity. In some cases, the span of a PO may be less than one slot, and then its repetition is sent on different frequency allocations within one slot. Inter-PO means that msgA PUSCH can be repeated between different PO sets and on different PRBs to achieve frequency diversity.

[0085] Which type of frequency hopping is used may be RRC-configured, which may be cell-specific signaling (e.g., in SIB1), and / or UE-specific signaling, which may be applied when the UE is in RRC connected mode. As an example, when intra-slot and inter-slot frequency hopping is applied, cell-specific signaling may be included in the PUSCH-ConfigCommon IE to indicate whether inter-slot or intra-slot frequency hopping is used. As shown below, in the PUSCH-ConfigCommon IE, the underlined parameters given below may be configured to control msgA PUSCH frequency hopping.

[0086]

[0087]

[0088] As another example, similar parameters may be placed in the PUSCH-Config IE for UE-specific signaling.

[0089] As a fifth embodiment, in order to support inter-slot frequency hopping, or intra-PO frequency hopping, or inter-PO frequency hopping, the number of repetitions and / or the redundancy version (RV) mode may be signaled in the RRC message or predetermined. For example, some signaling may be included in the PUSCH-ConfigCommon IE to support the repetition of the msgA PUSCH, as shown below.

[0090]

[0091]

[0092] As a sixth embodiment, the msgA PUSCH transmission configuration may be determined by one or more parameters of the msgA preamble, and / or the msgA PUSCH configuration. As a first option, the msgA PUSCH transmission configuration (including its frequency hopping configuration) may be determined by the cell-specific PRACH configuration for the msgA preamble. Specifically, some of the cell-specific PRACH configurations may be provided by, for example, rach-ConfigGeneric (or its equivalent) within the RACH-ConfigCommon IE. Similarly, some of the UE-specific PRACH configurations may be provided by, for example, rach-ConfigGeneric (or its equivalent) within the RACH-Config IE. Within the initial active uplink BWP during initial access, the PRACH frequency resources n are allocated in increasing order starting from the lowest frequency. RA ∈{0,1,…,M-1}, where M is equal to the higher layer parameter msg1-FDM (or equivalent, or msgA-FDM with respect to the number of msgA PRACH opportunities frequency division multiplexed). The value of M can be 1, 2, 4 or 8. For example, the msgA PUSCH frequency hopping configuration can be a function of the M value.

[0093] In one example, msgA PUSCH frequency hopping is possible only when M takes a specific value, such as M=1 or M={1 or 2}. In another example, msgA PUSCH frequency offset (when frequency hopping is enabled) is a function of M. For example, the frequency offset is equal to

[0094] In yet another example, the msgA PUSCH starting RB for frequency hopping (FH) is a function of msg1-FrequencyStart (or equivalent, or msgA-FrequencyStart with respect to the starting PRB of the msgA preamble, or with respect to the starting PRB of the msgA PUSCH opportunity, or the starting PRB of the entire PUSCH opportunity set). As an illustrative example, RB start equal in Indicates the PRB index provided by msg1-FrequencyStart or msgA-FrequencyStart. Here, RB start represents the msgA PUSCH starting RB for FH. As another exemplary example, RB start equal

[0095] As a second option, the msgA PUSCH frequency hopping configuration depends on whether the transform precoder of the msgA PUSCH is enabled. As a third option, the msgA PUSCH frequency hopping configuration depends on whether the 2-step RACH is performed as contention-based random access (CBRA) or contention-free random access (CFRA). When the 2-step RACH is contention-based, the frequency hopping of the msgA PUSCH is particularly useful for combating interference.

[0096] As a seventh embodiment, the msgA PUSCH FH configuration is part of a 2-step RACH configuration table. In this embodiment, the RACH configuration table is extended to include msgA PUSCH frequency hopping parameters. For example, for each RACH configuration index indicating a row in the RACH configuration table, the corresponding msgA PUSCH frequency hopping parameters are added to the row. Therefore, when a higher layer parameter prach-ConfigurationIndex (or equivalent) is used to look up a PRACH configuration in the table, the msgAPUSCH FH parameters are also obtained.

[0097] The FH parameters may include one or more of the following: enabling msgA PUSCH FH or not enabling msgA PUSCH FH; the msgA PUSCH starting RB for FH, i.e., RB start ; msgA PUSCH FH offset; and the number of time slots K spanned by msgA PUSCH. If K>1, inter-time slot hopping of msgA PUSCH can be applied. If K<=1, only intra-time slot hopping of msgAPUSCH can be applied.

[0098] As an eighth embodiment, msgA PUSCH FH configuration considers other system configurations. In one example, msgAPUSCH FH configuration is affected by FDD or TDD of the cell configuration. For example, in the case of FDD, msgA PUSCH has all symbols and slots available for PUSCH transmission, and there is no need to impose restrictions on inter-slot and intra-slot FH due to UL / DL transmission mode.

[0099] On the other hand, in the case of TDD, the UL / DL transmission mode needs to be considered in PUSCH transmission. PUSCH transmission is only valid when the associated symbol is for UL. For example, semi-statically configured DL symbols and / or time slots can override msgA PUSCH transmission, including its intra-slot and inter-slot transmission. Semi-statically configured UL symbols and / or time slots can always be used for msgA PUSCH transmission. Semi-statically configured flexible symbols / time slots can be used for msgA PUSCH transmission unless they conflict with the actual SSB transmission indicated. Here, the semi-static DL / UL allocation is accomplished via cell-specific RRC configuration and / or UE-specific RRC configuration. In RRC connected mode, in 2-step RA, the UE can use cell-specific and UE-specific RRC configurations. In RRC idle / inactive state, in 2-step RA, the UE can use cell-specific RRC configurations.

[0100] In another example, the msgA PUSCH FH configuration takes into account the operating spectrum. For example, depending on whether the spectrum belongs to FR1 (low frequency band 38.101-1) or FR2 (high frequency band 38.101-2), the configuration may be different. Another example is that different FH configurations may be introduced for wideband or narrowband. A certain predetermined number of PRBs may be used as a threshold to determine whether it is a narrowband or a wideband.

[0101] In another example, the msgA PUSCH FH configuration considers whether the uplink carrier in which the 2-step RACH occurs is a regular UL carrier or a supplementary UL carrier. In another example, the msgA PUSCH FH configuration may depend on whether the 2-step RACH is performed in the initial active UL BWP.

[0102] In the following, reference will be made to Figures 5 to 15 Describe the solution further. Figure 5 1 is a flow chart illustrating a method implemented at a terminal device according to an embodiment of the present disclosure. At block 502, the terminal device determines a frequency hopping configuration for sending one or more PUSCHs in a request message for random access. At block 504, the terminal device sends one or more PUSCHs in a request message based on the frequency hopping configuration. The request message includes at least a PRACH preamble and the one or more PUSCHs.

[0103] The random access may be a two-step random access. The frequency hopping configuration may include, but is not limited to, one or more parameters indicating: enabling and / or disabling of frequency hopping; starting PRB for frequency hopping; frequency offset for frequency hopping; frequency hopping type, which is one of intra-slot hopping, inter-slot hopping, intra-PO hopping, and inter-PO hopping; the number of time slots spanned by the one or more PUSCHs; and redundancy versions (RVs) for more than one PUSCH.

[0104] There may be six options for implementing block 502. As a first option, the frequency hopping configuration may be determined based on RRC signaling. Thus, the determination at block 502 may include receiving at least a portion of the frequency hopping configuration from the base station in RRC signaling. At least a portion of the frequency hopping configuration may be explicitly signaled in the RRC signaling, or implicitly indicated in the RRC signaling. The RRC signaling may be cell-specific RRC signaling or RRC signaling specific to the terminal device. As an example, when the frequency offset is not configured in the RRC signaling, the terminal device may determine to disable frequency hopping. As another example, when the frequency offset is set to zero in the RRC signaling, the terminal device may determine to disable frequency hopping.

[0105] As a second option, one or more parameters in the frequency hopping configuration may be determined as predetermined values. As an illustrative example, if the RRC signaling only indicates the activation of frequency hopping but does not indicate a frequency offset, the terminal device may use a predetermined value as the frequency offset. Similarly, any other parameter except the frequency offset may be determined as a predetermined value.

[0106] As a third option, one or more parameters in the frequency hopping configuration may be determined based on the PRACH configuration for the PRACH preamble. The PRACH configuration for the PRACH preamble may include, but is not limited to, one or more of the following: an extended PRACH configuration table from which one or more parameters in the frequency hopping configuration can be retrieved according to a PRACH configuration index; the number of PRACH opportunities; the starting PRB of the PRACH preamble; and whether to perform random access as CBRA or as CFRA.

[0107] As an example, when the number of PRACH opportunities adopts a predetermined value, the terminal device may determine to enable frequency hopping. As another example, the frequency offset for frequency hopping may be determined as a function of the number of PRACH opportunities. As another example, the starting PRB for frequency hopping may be determined as a function of the number of PRACH opportunities and / or the starting PRB of the PRACH preamble.

[0108] As a fourth option, one or more parameters in the frequency hopping configuration may be determined based on the PUSCH configuration used for the request message. The PUSCH configuration used for the request message may include, but is not limited to, one or more parameters indicating: enabling and / or disabling of transform precoding; the number of PRBs spanned by one or more POs of one or more sizes; the location of the PO to be used; the size of the PO set to be used; the location of the PO set to be used; the starting PRB of the PO for the first hop; the starting PRB of the PO set to be used.

[0109] As an example, the frequency offset for frequency hopping can be determined as a function of at least one of: the number of PRBs spanned by one or more POs of one or more sizes; and the location of the PO to be used. For example, the frequency offset can be determined as a scaling factor multiplied by the number of PRBs spanned by one or more POs of one or more sizes.

[0110] As another example, the starting PRB for frequency hopping can be determined as a function of at least one of: the number of PRBs spanned by one or more POs of one or more sizes; the starting PRB of the PO for the first hop; and the starting PRB of the PO set to be used.

[0111] As a fifth option, one or more parameters in the frequency hopping configuration may be determined based on one or more of the following: whether the cell serving the terminal device uses FDD or TDD; the different frequency bands in which the terminal device operates; whether a conventional uplink carrier or a supplementary uplink carrier will be used for random access; whether the random access will be performed in the initial active uplink BWP; and the size of the active BWP. For example, the frequency offset for frequency hopping may be determined based on the size of the active BWP. As a sixth option, a combination of any two or more of the first to fifth options described above may be used. Regardless of which option is used, the PUSCH for the request message for random access may be sent using an appropriate frequency hopping configuration.

[0112] Figure 66 is a flowchart illustrating a method implemented at a base station according to an embodiment of the present disclosure. At box 602, the base station determines a frequency hopping configuration to be used by a terminal device to send one or more PUSCHs in a request message for random access. The random access may be a two-step random access. The frequency hopping configuration may include, but is not limited to, one or more parameters indicating: enabling and / or disabling frequency hopping; the starting PRB for frequency hopping; the frequency offset for frequency hopping; the type of frequency hopping, which may be one of intra-slot hopping, inter-slot hopping, intra-PO hopping, and inter-PO hopping; the number of time slots spanned by the one or more PUSCHs; and a redundancy version (RV) for more than one PUSCH. The above principles for determining the frequency hopping configuration on the terminal device side may be similarly applied to the base station side. At box 604, the base station receives one or more PUSCHs in a request message for random access based on the frequency hopping configuration.

[0113] Optionally, the base station may indicate the frequency hopping configuration to the terminal device in RRC signaling. In this way, the frequency hopping configuration may be provided to the terminal device for use in sending a PUSCH for a request message for random access. The RRC signaling may be cell-specific RRC signaling or RRC signaling specific to the terminal device. The frequency hopping configuration may be explicitly signaled in the RRC signaling or implicitly indicated in the RRC signaling. It should be noted that two consecutively shown blocks in the accompanying drawings may actually be executed substantially in parallel, or they may sometimes be executed in reverse order, depending on the functions involved.

[0114] Based on the above description, at least one aspect of the present disclosure provides a method implemented in a communication system. The method includes: at a base station, determining a frequency hopping configuration to be used by a terminal device to send one or more PUSCHs in a request message for random access. The method also includes: at the terminal device, determining a frequency hopping configuration for sending one or more PUSCHs in a request message for random access. The method also includes: at the terminal device, based on the frequency hopping configuration, sending one or more PUSCHs in a request message. The request message includes at least a PRACH preamble and the one or more PUSCHs. The method also includes: at the base station, based on the frequency hopping configuration, receiving one or more PUSCHs in a request message for random access.

[0115] Figure 7 700 is a block diagram showing an apparatus suitable for use in practicing some embodiments of the present disclosure. For example, any of the terminal device and the base station described above can be implemented by the apparatus 700. As shown in the figure, the apparatus 700 may include a processor 710, a memory 720 storing programs, and an optional communication interface 730 for communicating data with other external devices via wired and / or wireless communications.

[0116] The program includes program instructions that, when executed by the processor 710, enable the device 700 to operate according to embodiments of the present disclosure, as discussed above. That is, embodiments of the present disclosure may be implemented at least in part by computer software executable by the processor 710, or by hardware, or by a combination of software and hardware.

[0117] The memory 720 may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The processor 710 may be of any type suitable for the local technical environment and may include, as non-limiting examples, one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture.

[0118] Figure 8 800 includes a determining module 802 and a sending module 804. The determining module 802 may be configured to determine a frequency hopping configuration for sending one or more PUSCHs in a request message for random access, as described above with respect to block 502. The sending module 804 may be configured to send one or more PUSCHs in a request message based on the frequency hopping configuration, as described above with respect to block 504. The request message includes at least a PRACH preamble and one or more PUSCHs.

[0119] Fig. 9 is a block diagram of a base station according to an embodiment of the present disclosure. As shown in the figure, the base station 900 includes a determination module 902 and a receiving module 904. The determination module 902 may be configured to determine a frequency hopping configuration to be used by a terminal device to send one or more PUSCHs in a request message for random access, as described above with respect to block 602. The receiving module 904 may be configured to receive one or more PUSCHs in a request message for random access based on the frequency hopping configuration, as described above with respect to block 604. The above modules may be implemented by hardware, or software, or a combination of both.

[0120] Based on the above description, at least one aspect of the present disclosure provides a communication system. The communication system includes a base station, which is configured to: determine a frequency hopping configuration to be used by a terminal device to send one or more PUSCHs in a request message for random access; and based on the frequency hopping configuration, receive one or more PUSCHs in a request message for random access. The communication system also includes a terminal device, which is configured to: determine a frequency hopping configuration for sending one or more PUSCHs in a request message for random access; and based on the frequency hopping configuration, send one or more PUSCHs in a request message. The request message includes at least a PRACH preamble and one or more PUSCHs.

[0121] refer to Fig.10 According to an embodiment, a communication system includes a telecommunication network 3210 such as a 3GPP type cellular network, which includes an access network 3211 such as a radio access network and a core network 3214. The access network 3211 includes a plurality of base stations 3212a, 3212b, 3212c (such as NB, eNB, gNB or other types of wireless access points), each defining a corresponding coverage area 3213a, 3213b, 3213c. Each base station 3212a, 3212b, 3212c can be connected to the core network 3214 via a wired or wireless connection 3215. A first UE 3291 located in the coverage area 3213c is configured to be wirelessly connected to the corresponding base station 3212c, or to be paged by the corresponding base station 3212c. A second UE 3292 in the coverage area 3213a can be wirelessly connected to the corresponding base station 3212a. Although multiple UEs 3291, 3292 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is in the coverage area or a single UE is connected to the corresponding base station 3212.

[0122] The telecommunications network 3210 itself is connected to a host 3230, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. The host 3230 may be under the ownership or control of a service provider, or may be operated by or on behalf of a service provider. The connections 3221 and 3222 between the telecommunications network 3210 and the host 3230 may extend directly from the core network 3214 to the host 3230, or may extend via an optional intermediate network 3220. The intermediate network 3220 may be one of a public network, a private network, or a hosted network, or a combination of more than one; if any, the intermediate network 3220 may be a backbone network or the Internet; in particular, the intermediate network 3220 may include two or more subnetworks (not shown).

[0123] Fig.10 The communication system as a whole implements connectivity between connected UEs 3291, 3292 and a host 3230. The connectivity may be described as an over-the-top (OTT) connection 3250. The host 3230 and the connected UEs 3291, 3292 are configured to use the access network 3211, the core network 3214, any intermediate networks 3220, and possible additional infrastructure (not shown) as intermediaries to pass data and / or signaling via the OTT connection 3250. The participating communication devices traversed by the OTT connection 3250 are not aware of the routing of uplink and downlink communications, and in this sense, the OTT connection 3250 may be transparent. For example, the base station 3212 may not or need not be informed of the past routing of incoming downlink communications with data originating from the host 3230 to be forwarded (e.g., handed over) to the connected UE 3291. Similarly, base station 3212 need not be aware of future routing of uplink communications originating from UE 3291 toward host 3230.

[0124] Now refer to Fig.11 Describe the example implementation of the UE, base station and host discussed in the previous paragraph according to one embodiment. In the communication system 3300, the host 3310 includes hardware 3315, and the hardware 3315 includes a communication interface 3316, which is configured to establish and maintain a wired or wireless connection of an interface with different communication devices of the communication system 3300. The host 3310 also includes a processing circuit 3318, which may have storage and / or processing capabilities. In particular, the processing circuit 3318 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these suitable for executing instructions (not shown). The host 3310 also includes software 3311, which is stored in the host 3310 or can be accessed by the host 3310, and can be executed by the processing circuit 3318. Software 3311 includes a host application 3312. The host application 3312 may be operable to provide services to a remote user, such as a UE 3330 connected via an OTT connection 3350 terminating at the UE 3330 and the host 3310. In providing services to the remote user, the host application 3312 may provide user data transmitted using the OTT connection 3350.

[0125] The communication system 3300 also includes a base station 3320, which is provided in the telecommunication system and includes hardware 3325 that enables it to communicate with the host 3310 and the UE 3330. The hardware 3325 may include a communication interface 3326 for establishing and maintaining a wired or wireless connection with different communication devices of the communication system 3300, and a communication interface 3326 for establishing and maintaining a connection with a network located in the coverage area ( Fig.11 3327 of at least a wireless connection 3370 of a UE 3330 in the example embodiment (not shown). The communication interface 3326 may be configured to facilitate a connection 3360 to the host 3310. The connection 3360 may be direct, or the connection 3360 may pass through a core network ( Fig.11 3320) and / or traverse one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 3325 of the base station 3320 also includes processing circuitry 3328, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these suitable for executing instructions (not shown). The base station 3320 also has software 3321 stored internally or accessible via an external connection.

[0126] The communication system 3300 also includes the UE 3330 already mentioned. Its hardware 3335 may include a radio interface 3337, which is configured to establish and maintain a wireless connection 3370 with a base station serving the coverage area where the UE 3330 is currently located. The hardware 3335 of the UE 3330 also includes a processing circuit 3338, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these suitable for executing instructions (not shown). The UE 3330 also includes software 3331, which is stored in the UE 3330 or can be accessed by the UE 3330 and can be executed by the processing circuit 3338. The software 3331 includes a client application 3332. The client application 3332 may be operable to provide services to human or non-human users via the UE 3330 under the support of the host 3310. In the host 3310, the executed host application 3312 can communicate with the executed client application 3332 via the OTT connection 3350 terminated at the UE 3330 and the host 3310. In the process of providing services to the user, the client application 3332 can receive request data from the host application 3312 and provide user data in response to the request data. The OTT connection 3350 can transmit both the request data and the user data. The client application 3332 can interact with the user to generate the user data it provides.

[0127] It should be noted that Fig.11 The host 3310, base station 3320 and UE 3330 shown in Fig.10 The host 3230, one of the base stations 3212a, 3212b, 3212c, and one of the UEs 3291, 3292 are similar or identical. That is, the internal workings of these entities can be similar to Fig.11 As shown, and independently, the surrounding network topology can be Fig.10 The surrounding network topology.

[0128] exist Fig.11 In the figure, the OTT connection 3350 has been abstractly drawn to show the communication between the host 3310 and the UE 3330 via the base station 3320, without explicit reference to any intermediate devices and the precise routing of messages via these devices. The network infrastructure can determine the route, and the network infrastructure can be configured to hide the route from the UE 3330, or hide the route from the service provider operating the host 3310, or hide the route from both. When the OTT connection 3350 is active, the network infrastructure can also make decisions by which the network infrastructure dynamically changes the route (for example, based on load balancing considerations or reconfiguration of the network).

[0129] The wireless connection 3370 between the UE 3330 and the base station 3320 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE 3330 using the OTT connection 3350, in which the wireless connection 3370 forms the last leg. More precisely, the teachings of these embodiments can improve latency and thereby provide benefits such as reduced user waiting time.

[0130] The measurement process may be provided for the purpose of monitoring data rate, latency, and other factors improved by one or more embodiments. There may also be an optional network function for reconfiguring the OTT connection 3350 between the host 3310 and the UE 3330 in response to changes in the measurement results. The measurement process and / or network function for reconfiguring the OTT connection 3350 may be implemented in the software 3311 and hardware 3315 of the host 3310, or in the software 3331 and hardware 3335 of the UE 3330, or in both. In some embodiments, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 3350 passes; the sensor may participate in the measurement process by supplying the values ​​of the monitored quantities exemplified above, or supplying the values ​​of other physical quantities from which the software 3311, 3331 can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 3350 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not need to affect the base station 3320, and the reconfiguration may be unknown or imperceptible to the base station 3320. Such processes and functions may be known and practiced in the art. In certain embodiments, the measurements may involve proprietary UE signaling that facilitates measurement of throughput, propagation time, latency, etc., of the host 3310. The measurements may be implemented because the software 3311 and 3331 causes messages (particularly, empty messages or 'dummy' messages) to be transmitted using the OTT connection 3350 while the software 3311 and 3331 monitors propagation time, errors, etc.

[0131] Fig.12 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host, a base station and a UE, which can be reference Fig.10 and 11 For the sake of brevity of this disclosure, only the Fig.12 Reference to the accompanying drawings of . In step 3410, the host provides user data. In sub-step 3411 of step 3410 (which may be optional), the host provides user data by executing a host application. In step 3420, the host initiates a transmission carrying the user data to the UE. In step 3430 (which may be optional), in accordance with the teachings of the embodiments described in the full text of this disclosure, the base station sends the user data carried in the transmission initiated by the host to the UE. In step 3440 (which may be optional), the UE executes a client application associated with the host application executed by the host.

[0132] Fig.13 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host, a base station and a UE, which can be reference Fig.10 and 11 For the sake of brevity of this disclosure, only the Fig.13 Reference to the accompanying drawings of the method. In step 3510 of the method, the host provides user data. In an optional sub-step (not shown), the host provides the user data by executing a host application. In step 3520, the host initiates a transmission carrying the user data to the UE. According to the teachings of the embodiments described in the full text of this disclosure, the transmission can be performed via a base station. In step 3530 (which may be optional), the UE receives the user data carried in the transmission.

[0133] Fig.14 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host, a base station and a UE, which can be reference Fig.10 and 11 For the sake of brevity of this disclosure, only the Fig.14Reference to the accompanying drawings. In step 3610 (which may be optional), the UE receives input data provided by the host. Additionally or alternatively, in step 3620, the UE provides user data. In sub-step 3621 of step 3620 (which may be optional), the UE provides user data by executing a client application. In sub-step 3611 of step 3610 (which may be optional), the UE executes a client application that provides user data as a reaction to the received input data provided by the host. In the process of providing user data, the executed client application may also consider user input received from the user. Regardless of the specific manner of providing user data, in sub-step 3630 (which may be optional), the UE initiates transmission of user data to the host. In step 3640 of the method, in accordance with the teachings of the embodiments described in the entire disclosure, the host receives user data sent from the UE.

[0134] Fig.15 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host, a base station and a UE, which can be reference Fig.10 and 11 For the sake of brevity of this disclosure, only the Fig.15 In step 3710 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 3720 (which may be optional), the base station initiates a transmission of the received user data to the host. In step 3730 (which may be optional), the host receives the user data carried in the transmission initiated by the base station.

[0135] According to one aspect of the present disclosure, a method implemented in a communication system including a host, a base station and a terminal device is provided. The method includes: receiving user data sent from a terminal device to a base station at the host. The terminal device determines a frequency hopping configuration for sending one or more PUSCHs in a request message for random access. The terminal device sends one or more PUSCHs in a request message based on the frequency hopping configuration. The request message includes at least a PRACH preamble and one or more PUSCHs.

[0136] In an embodiment of the present disclosure, the method may further include: providing user data to the base station at the terminal device.

[0137] In an embodiment of the present disclosure, the method may further include: executing a client application at the terminal device to provide user data to be sent. The method may further include: executing a host application associated with the client application at the host.

[0138] In an embodiment of the present disclosure, the method may further include: executing a client application at a terminal device. The method may further include: receiving input data to the client application at the terminal device. The input data may be provided at the host by executing a host application associated with the client application. The user data to be sent may be provided by the client application in response to the input data.

[0139] According to another aspect of the present disclosure, a communication system including a host is provided. The host includes a communication interface configured to receive user data originating from a transmission from a terminal device to a base station. The terminal device includes a radio interface and a processing circuit. The processing circuit of the terminal device is configured to determine a frequency hopping configuration for sending one or more PUSCHs in a request message for random access. The processing circuit of the terminal device is also configured to send one or more PUSCHs in a request message based on the frequency hopping configuration. The request message includes at least a PRACH preamble and one or more PUSCHs.

[0140] In an embodiment of the present disclosure, the communication system may further include a terminal device.

[0141] In an embodiment of the present disclosure, the communication system may further include a base station. The base station may include a radio interface configured to communicate with a terminal device, and a communication interface configured to forward user data carried by a transmission from the terminal device to the base station to a host.

[0142] In an embodiment of the present disclosure, the processing circuit of the host may be configured to execute a host application. The processing circuit of the terminal device may be configured to execute a client application associated with the host application, thereby providing user data.

[0143] In an embodiment of the present disclosure, the processing circuit of the host may be configured to execute a host application to provide request data, and the processing circuit of the terminal device may be configured to execute a client application associated with the host application to provide user data in response to the request data.

[0144] According to another aspect of the present disclosure, a method implemented in a communication system including a host, a base station and a terminal device is provided. The method includes: receiving, at the host, from the base station, user data originating from a transmission that the base station has received from the terminal device. The base station determines a frequency hopping configuration to be used by the terminal device to send one or more PUSCHs in a request message for random access. The base station receives one or more PUSCHs in a request message for random access based on the frequency hopping configuration.

[0145] In an embodiment of the present disclosure, the method may further include: receiving user data from a terminal device at a base station.

[0146] In an embodiment of the present disclosure, the method may further include: initiating, at the base station, transmission of the received user data to the host.

[0147] According to another aspect of the present disclosure, a communication system including a host is provided. The host includes a communication interface configured to receive user data originating from a transmission from a terminal device to a base station. The base station includes a radio interface and a processing circuit. The processing circuit of the base station is configured to determine a frequency hopping configuration to be used by the terminal device to send one or more PUSCHs in a request message for random access. The processing circuit of the base station is also configured to receive one or more PUSCHs in a request message for random access based on the frequency hopping configuration.

[0148] In an embodiment of the present disclosure, the communication system may further include a base station.

[0149] In an embodiment of the present disclosure, the communication system may further include a terminal device. The terminal device may be configured to communicate with the base station.

[0150] In an embodiment of the present disclosure, the processing circuit of the host may be configured to execute a host application. The terminal device may be configured to execute a client application associated with the host application, thereby providing user data to be received by the host.

[0151] In general, various exemplary embodiments may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, although the present disclosure is not limited thereto. Although various aspects of the exemplary embodiments of the present disclosure may be shown and described as block diagrams, flow charts, or using some other graphical representations, it should be well understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or controllers, or other computing devices, or some combination thereof.

[0152] Thus, it should be understood that at least some aspects of the exemplary embodiments of the present disclosure may be practiced in various components such as integrated circuit chips and modules. Thus, it should be understood that the exemplary embodiments of the present disclosure may be implemented in a device embodied as an integrated circuit, wherein the integrated circuit may include circuits (and possibly firmware) for embodying at least one or more of a data processor, a digital signal processor, a baseband circuit, and a radio frequency circuit that may be configured to operate according to the exemplary embodiments of the present disclosure.

[0153] It should be understood that at least some aspects of the exemplary embodiments of the present disclosure may be embodied in computer executable instructions executed by one or more computers or other devices, such as embodied in one or more program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., which perform specific tasks or implement specific abstract data types when executed by a processor in a computer or other device. Computer executable instructions may be stored on a computer readable medium, such as a hard disk, an optical disk, a removable storage medium, a solid-state memory, a RAM, etc. It will be appreciated by those skilled in the art that the functions of the program modules may be combined or distributed as needed in various embodiments. In addition, the functions may be embodied in firmware or hardware equivalents (such as integrated circuits, field programmable gate arrays (FPGAs), etc.) in whole or in part.

[0154] References in this disclosure to "one embodiment," "an embodiment," etc., indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment must include the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. In addition, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it is within the knowledge of those skilled in the art to implement such feature, structure, or characteristic in conjunction with other embodiments, whether or not explicitly described.

[0155] It should be understood that, although the terms "first", "second", etc. can be used in this article to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, the first element can be referred to as the second element, and similarly, the second element can be referred to as the first element without departing from the scope of this disclosure. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed terms.

[0156] The terms used herein are only used to describe the purpose of specific embodiments, and are not intended to limit the present disclosure. As used herein, the singular "a, an" and "the" are intended to also include plural forms, unless the context clearly indicates otherwise. It will also be understood that the terms "include", "have" and / or "comprise" when used herein refer to the existence of stated features, elements and / or components, and do not exclude the existence or addition of one or more other features, elements, components and / or their combinations. The term "connection" used herein covers the direct and / or indirect connection between two elements.

[0157] The present disclosure includes any novel feature or feature combination disclosed herein, either explicitly or in any generalized form thereof. When read in conjunction with the accompanying drawings, various modifications and adaptations to the above exemplary embodiments of the present disclosure will become apparent to those skilled in the relevant art in view of the above description. However, any and all modifications will still fall within the scope of the non-limiting and exemplary embodiments of the present disclosure.

Claims

1. A method performed by a terminal device, comprising: Determining a frequency hopping configuration for sending one or more physical uplink shared channels PUSCH in a random access request message; as well as Based on the frequency hopping configuration, sending the one or more PUSCHs in the request message, the request message including at least a physical random access channel PRACH preamble and the one or more PUSCHs; The frequency hopping configuration includes one or more parameters indicating: enabling and / or disabling of frequency hopping; The starting physical resource block PRB for frequency hopping; Frequency offset for frequency hopping; A frequency hopping type, which is one of intra-slot frequency hopping, inter-slot frequency hopping, intra-PUSCH opportunity PO frequency hopping, and inter-PO frequency hopping; The number of time slots spanned by the one or more PUSCHs; and Redundancy version RV for more than one PUSCH; The one or more parameters in the frequency hopping configuration are determined based on a PRACH configuration for the PRACH preamble.

2. The method according to claim 1, wherein: The frequency hopping configuration is determined based on radio resource control RRC signaling.

3. The method according to claim 2, wherein: The RRC signaling is cell-specific RRC signaling, or RRC signaling specific to the terminal device.

4. The method according to claim 3, wherein: When the frequency offset is not configured in the RRC signaling, the terminal device determines to disable frequency hopping.

5. The method according to claim 3, wherein: When the frequency offset is set to zero in the RRC signaling, the terminal device determines to disable frequency hopping.

6. The method according to claim 1, wherein: The one or more parameters in the frequency hopping configuration are determined to be predetermined values.

7. The method according to claim 1, wherein: The PRACH configuration for the PRACH preamble includes one or more of the following: an extended PRACH configuration table, from which one or more parameters in the frequency hopping configuration can be retrieved according to a PRACH configuration index; The number of PRACH opportunities; The starting PRB of the PRACH preamble; as well as Whether random access is performed as contention-based random access (CBRA) or random access is performed as contention-free random access (CFRA).

8. The method according to claim 7, wherein: When the number of PRACH opportunities adopts a predetermined value, the terminal device determines to enable frequency hopping.

9. The method according to claim 7, wherein: The frequency offset used for frequency hopping is determined as a function of the number of PRACH opportunities.

10. The method according to any one of claims 7 to 9, wherein: The starting PRB for frequency hopping is determined as a function of the number of the PRACH opportunities and / or the starting PRB of the PRACH preamble.

11. The method according to claim 1, wherein: The one or more parameters in the frequency hopping configuration are determined based on a PUSCH configuration used for the request message.

12. The method according to claim 11, wherein: The PUSCH configuration for the request message includes one or more parameters indicating: Enable and / or disable transform precoding; The number of PRBs spanned by one or more POs of one or more sizes; The location of the PO to be used; The size of the PO set to be used; The location of the PO set to be used; The starting PRB for the PO of the first hop; The starting PRB of the PO set to be used.

13. The method according to claim 12, wherein: The frequency offset used for frequency hopping is determined as a function of at least one of: The number of PRBs spanned by the one or more POs having one or more sizes; and the location of the POs to be used.

14. The method according to claim 13, wherein: The frequency offset is determined as a scaling factor multiplied by the number of PRBs spanned by the one or more POs having one or more sizes.

15. The method according to any one of claims 12 to 14, wherein: The starting PRB for frequency hopping is determined as a function of at least one of: The number of PRBs spanned by the one or more POs having one or more sizes; the starting PRB of the PO for the first hop; and the starting PRB of the PO set to be used.

16. The method according to claim 1, wherein: The one or more parameters in the frequency hopping configuration are determined based on one or more of the following: Whether the cell serving the terminal device uses frequency division duplex FDD or time division duplex TDD; different frequency bands in which the terminal devices operate; whether a normal uplink carrier or a supplementary uplink carrier is to be used for the random access; whether the random access is to be performed in an initial active uplink bandwidth part BWP; as well as The size of the active BWP.

17. The method according to claim 16, wherein: The frequency offset used for frequency hopping is determined based on the size of the active BWP.

18. A method performed by a base station, comprising: determining a frequency hopping configuration to be used by a terminal device to send one or more physical uplink shared channels, PUSCH, in a request message for random access; as well as receiving, based on the frequency hopping configuration, the one or more PUSCHs in a request message for random access; The frequency hopping configuration includes one or more parameters indicating: enabling and / or disabling of frequency hopping; The starting physical resource block PRB for frequency hopping; Frequency offset for frequency hopping; A frequency hopping type, which is one of intra-slot frequency hopping, inter-slot frequency hopping, intra-PUSCH opportunity PO frequency hopping, and inter-PO frequency hopping; The number of time slots spanned by the one or more PUSCHs; and Redundancy version RV for more than one PUSCH; The one or more parameters in the frequency hopping configuration are determined based on a PRACH configuration for a physical random access channel PRACH preamble.

19. A terminal device, comprising: at least one processor; as well as at least one memory containing instructions executable by the at least one processor, whereby the terminal device is operable to: Determining a frequency hopping configuration for sending one or more physical uplink shared channels PUSCH in a random access request message; and Based on the frequency hopping configuration, the one or more PUSCHs are sent in the request message, the request message at least including a physical random access channel PRACH preamble and the one or more PUSCHs; wherein the frequency hopping configuration includes one or more parameters indicating: enabling and / or disabling of frequency hopping; The starting physical resource block PRB for frequency hopping; Frequency offset for frequency hopping; A frequency hopping type, which is one of intra-slot frequency hopping, inter-slot frequency hopping, intra-PUSCH opportunity PO frequency hopping, and inter-PO frequency hopping; The number of time slots spanned by the one or more PUSCHs; and Redundancy version RV for more than one PUSCH; The one or more parameters in the frequency hopping configuration are determined based on a PRACH configuration for the PRACH preamble.

20. The terminal device according to claim 19, wherein: The terminal device is operable to perform a method according to any one of claims 2 to 17.

21. A base station, comprising: at least one processor; as well as at least one memory containing instructions executable by the at least one processor, whereby the base station is operable to: determining a frequency hopping configuration to be used by a terminal device to send one or more physical uplink shared channels, PUSCH, in a request message for random access; and receiving, based on the frequency hopping configuration, the one or more PUSCHs in a request message for random access; The frequency hopping configuration includes one or more parameters indicating: enabling and / or disabling of frequency hopping; The starting physical resource block PRB for frequency hopping; Frequency offset for frequency hopping; A frequency hopping type, which is one of intra-slot frequency hopping, inter-slot frequency hopping, intra-PUSCH opportunity PO frequency hopping, and inter-PO frequency hopping; The number of time slots spanned by the one or more PUSCHs; and Redundancy version RV for more than one PUSCH; The one or more parameters in the frequency hopping configuration are determined based on a PRACH configuration for a physical random access channel PRACH preamble code.

22. A method implemented in a communication system, comprising: At a base station, determining a frequency hopping configuration to be used by a terminal device to send one or more physical uplink shared channels (PUSCH) in a request message for random access; At the terminal device, determining the frequency hopping configuration for sending one or more PUSCHs in a random access request message; At the terminal device, based on the frequency hopping configuration, sending the one or more PUSCHs in the request message, the request message including at least a physical random access channel PRACH preamble and the one or more PUSCHs; as well as At the base station, based on the frequency hopping configuration, receiving the one or more PUSCHs in a request message for random access; wherein the frequency hopping configuration includes one or more parameters indicating: enabling and / or disabling of frequency hopping; The starting physical resource block PRB for frequency hopping; Frequency offset for frequency hopping; A frequency hopping type, which is one of intra-slot frequency hopping, inter-slot frequency hopping, intra-PUSCH opportunity PO frequency hopping, and inter-PO frequency hopping; The number of time slots spanned by the one or more PUSCHs; and Redundancy version RV for more than one PUSCH; The one or more parameters in the frequency hopping configuration are determined based on a PRACH configuration for the PRACH preamble.

23. A communication system comprising: A base station configured to: determine a frequency hopping configuration to be used by a terminal device to send one or more physical uplink shared channels (PUSCH) in a request message for random access; and based on the frequency hopping configuration, receive the one or more PUSCHs in the request message for random access; and The terminal device is configured to: determine the frequency hopping configuration for sending one or more PUSCHs in a random access request message; and send the one or more PUSCHs in the request message based on the frequency hopping configuration, wherein the request message includes at least a physical random access channel PRACH preamble and the one or more PUSCHs; The frequency hopping configuration includes one or more parameters indicating: enabling and / or disabling of frequency hopping; The starting physical resource block PRB for frequency hopping; Frequency offset for frequency hopping; A frequency hopping type, which is one of intra-slot frequency hopping, inter-slot frequency hopping, intra-PUSCH opportunity PO frequency hopping, and inter-PO frequency hopping; The number of time slots spanned by the one or more PUSCHs; and Redundancy version RV for more than one PUSCH; The one or more parameters in the frequency hopping configuration are determined based on a PRACH configuration for the PRACH preamble.

24. A computer-readable storage medium comprising instructions which, when executed by at least one processor, cause the at least one processor to perform the method of any one of claims 1 to 18.

Images