Frequency hopping for Physical Uplink Shared Channel (PUSCH) communications

Abstract

Some embodiments include an apparatus, method, and computer program product that facilitate frequency hopping for physical uplink shared channel (PUSCH) communications in a 5G wireless communication system. When inter-slot and / or inter-repetition frequency hopping is used, a user equipment (UE) may transmit a first portion of a symbol using a first transmission frequency indicated by a frequency domain resource allocation in a first time slot. The UE may transmit a second portion of a symbol using a second offset frequency in a second time slot. When intra-repetition frequency hopping is used and the symbol is segmented, the UE may disable the intra-repetition frequency hopping and transmit a segmented portion of the symbol using a specific transmission frequency indicated by the frequency domain resource allocation. When intra-repetition frequency hopping is used and the symbol is non-segmented, the UE may apply frequency hopping to divide portions of the symbol for transmission within the repetition.

Description

Background Art

[0001] Various embodiments may generally relate to the field of wireless communications. Summary of the Invention

[0002] Some embodiments of the present disclosure include apparatus and methods that facilitate frequency hopping for Physical Uplink Shared Channel (PUSCH) communications.

[0003] In some embodiments, a method for facilitating intra-repeat frequency hopping for PUSCH communications may include receiving a frequency domain resource allocation indicating a transmission frequency and an offset frequency. The method may include identifying a data set having symbols using a physical uplink shared channel (PUSCH) transmission scheme, and identifying that the PUSCH transmission scheme indicates use of intra-repeat frequency hopping. The method may include determining that the symbol is non-segmented. In response to the determination, the method may include partitioning the symbol into a first partition and a second partition for intra-repeat frequency hopping. The method may include transmitting the first partition of the symbol using the transmission frequency in the transmission repetition, and transmitting the second partition of the symbol using the offset frequency in the transmission repetition.

[0004] In some embodiments, the method may further include identifying a second data set using an intra-repetition hopping PUSCH transmission scheme; determining that the second data set includes segmented symbols; disabling the intra-repetition hopping; and transmitting the second data set using the transmission frequency indicated by the frequency domain resource allocation.

[0005] In some embodiments, the method may further include identifying a second data set having a first portion of symbols and a second portion of symbols using an inter-slot hopping PUSCH transmission scheme, and determining that the first portion and the second portion are segmented. The method may further include transmitting the first portion using the transmission frequency in a first transmission slot and transmitting the second portion using the offset frequency in a second transmission slot.

[0006] In some embodiments, the method may further include identifying a second data set having a first portion of symbols and a second portion of symbols using an inter-slot hopping PUSCH transmission scheme; determining that the first portion and the second portion are non-segmented; transmitting the first portion using the transmission frequency in a first transmission slot; and transmitting the second portion using the offset frequency in a second transmission slot.

[0007] In some embodiments, transmitting using the offset frequency may also include modifying the transmission frequency by converting the transmission frequency using the offset frequency.

[0008] In some embodiments, the method may further include indicating, by the frequency domain resource allocation, a first frequency range corresponding to the transmission frequency and a second frequency range corresponding to the offset frequency.

[0009] In some embodiments, the method may further include alternating between the transmission frequency and the offset frequency to transmit additional PUSCH data.

[0010] In some embodiments, a wireless communication system can facilitate frequency hopping of PUSCH transmissions. The wireless communication system may include a transceiver and at least one processor coupled to the transceiver. The at least one processor may be configured to receive a frequency domain resource allocation indicating a transmission frequency and an offset frequency. The at least one processor may use a physical uplink shared channel (PUSCH) transmission scheme to identify a data set having symbols, and identify the use of inter-repetition frequency hopping indicated by the PUSCH transmission scheme. In response to the determination, the at least one processor may divide the symbol into a first partition and a second partition for inter-repetition frequency hopping. The at least one processor may transmit the first partition of the symbol using the transmission frequency in a first transmission repetition via the transceiver, and transmit the second partition of the symbol using the offset frequency in a second transmission repetition via the transceiver.

[0011] In some embodiments, the symbol may be segmented.

[0012] In some embodiments, the symbol may be non-segmented.

[0013] In some embodiments, the at least one processor may be further configured to identify a second data set using an intra-repeat hopping PUSCH transmission scheme and determine that the second data set includes non-segmented symbols. In response to this determination, the at least one processor may partition the symbols of the second data set into a first partition and a second partition for intra-repeat hopping. The at least one processor may be further configured to transmit the first partition using the transmission frequency in a third transmission repetition and transmit the second partition of symbols using the offset frequency in the third transmission repetition.

[0014] In some embodiments, the at least one processor may be further configured to identify the second data set using an intra-repetition hopping PUSCH transmission scheme. The at least one processor may be configured to determine that the second data set includes segmented symbols and disable the intra-repetition hopping. The at least one processor may be further configured to transmit the second data set using the transmission frequency indicated by the frequency-domain resource allocation.

[0015] In some embodiments, the frequency domain resource allocation indicates a first frequency range corresponding to the transmission frequency and a second frequency range corresponding to the offset frequency.

[0016] In some embodiments, the at least one processor may be further configured to alternate between the transmission frequency and the offset frequency to transmit additional PUSCH data.

[0017] In some embodiments, a method for facilitating frequency hopping of PUSCH transmissions may include receiving a frequency domain resource allocation indicating a transmission frequency and an offset frequency. The method may also include identifying a data set having symbols using a physical uplink shared channel (PUSCH) transmission scheme, and identifying that the PUSCH transmission scheme indicates the use of frequency hopping. In response to the determination, the method may also include dividing the symbols into a first partition and a second partition for frequency hopping. The method may also include transmitting the first partition using the transmission frequency and transmitting the second partition of the symbol using the offset frequency.

[0018] In some embodiments, the frequency hopping is a PUSCH transmission scheme with frequency hopping within a repetition, and the method may further include determining that the length of the symbol meets a symbol length threshold. The method may further include transmitting the first partition of the symbol using the transmission frequency in the transmission repetition, and transmitting the second partition of the symbol using the offset frequency in the transmission repetition.

[0019] In some embodiments, the method may further include receiving a second data set and determining that symbols of the second data set are segmented. The method may further include disabling the intra-repetition frequency hopping PUSCH transmission scheme and transmitting the second data set using the transmission frequency indicated by the frequency domain resource allocation.

[0020] In some embodiments, the frequency hopping is an inter-repetition hopping PUSCH transmission scheme, and the method may further include transmitting the first partitioned portion of the symbol using the transmission frequency in a first transmission repetition, and transmitting the second partitioned portion of the symbol using the offset frequency in a second transmission repetition.

[0021] In some embodiments, the frequency domain resource allocation indicates a first frequency range corresponding to the transmission frequency and a second frequency range corresponding to the offset frequency.

[0022] In some embodiments, the method may further include alternating between the transmission frequency and the offset frequency to transmit additional PUSCH data. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 An example system implementing frequency hopping for Physical Uplink Shared Channel (PUSCH) communications is shown in accordance with some embodiments.

[0024] Figure 2A block diagram illustrating an example wireless system of electronic devices implementing frequency hopping for PUSCH communications according to some embodiments of the present disclosure is shown.

[0025] Figure 3A A block diagram illustrating inter-slot frequency hopping according to some embodiments is shown.

[0026] Figure 3B A block diagram illustrating intra-slot frequency hopping according to some embodiments is shown.

[0027] Figure 4 A block diagram illustrating PUSCH transmission with segmentation according to some embodiments is shown.

[0028] Figure 5 A block diagram illustrating symbol segmentation according to some embodiments is shown.

[0029] Figure 6A A block diagram illustrating inter-slot and / or inter-repetition frequency hopping for Physical Uplink Shared Channel (PUSCH) communications according to some embodiments is shown.

[0030] Figure 6B A block diagram is shown for inter-slot and / or inter-repetition frequency hopping for Physical Uplink Shared Channel (PUSCH) communications with segmentation, according to some embodiments.

[0031] Figure 7 A block diagram of a physical uplink shared channel (PUSCH) data set with segmentation is shown in accordance with some embodiments.

[0032] Figure 8A A block diagram illustrating intra-repetition frequency hopping for Physical Uplink Shared Channel (PUSCH) communications with segmentation is shown in accordance with some embodiments.

[0033] Figure 8B A block diagram illustrating intra-repetition frequency hopping for length-based Physical Uplink Shared Channel (PUSCH) communications, according to some embodiments.

[0034] Figure 9A A flow chart for PUSCH frequency hopping communications according to some embodiments is shown.

[0035] Figure 9B A flow diagram is shown for intra-repetition frequency hopping for Physical Uplink Shared Channel (PUSCH) communications with segmentation, according to some embodiments.

[0036] Figure 10 An exemplary computer system for implementing various embodiments is depicted.

[0037] Features and advantages of the embodiments will become more apparent from the detailed description set forth below when taken in conjunction with the accompanying drawings, in which like reference numerals identify corresponding elements throughout. In the drawings, like reference numerals generally indicate identical, functionally similar, and / or structurally similar elements. The drawing in which an element first appears is indicated by the leftmost digit(s) in the corresponding reference numeral. DETAILED DESCRIPTION

[0038] The following detailed description refers to the accompanying drawings. The same reference numerals may be used to identify the same or similar elements in different drawings. In the following description, specific details, such as specific structures, architectures, interfaces, technologies, etc., are set forth for the purpose of illustration and not limitation, so as to provide a thorough understanding of the various aspects of the various embodiments. However, it will be apparent to those skilled in the art who benefit from this disclosure that the various aspects of the various embodiments can be practiced in other examples that deviate from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the various embodiments due to unnecessary details. For the purposes of this document, the phrase "A or B" refers to (A), (B), or (A and B).

[0039] This disclosure relates to user equipment (UE) communications using the 5G wireless communication protocol. As part of the 5G standard development, the 3rd Generation Partnership Project (3GPP) has released several documents detailing meeting minutes and developments. Two such documents are referred to as Release 15 (Rel-15) and Release 16 (Rel-16).

[0040] With Rel-15 and Rel-16, Physical Uplink Shared Channel (PUSCH) transmissions are supported for 5G communications from a UE to a node or base station. For example, the node may be a gNB or ng-eNB. The UE may use the PUSCH as a communication channel for transmitting data, information, and / or control information. While the UE may use the PUSCH, several issues related to interference may continue to hinder successful communication. For example, channel fading and / or interference may cause issues related to specific communication frequencies.

[0041] One strategy to address these interference issues is to use frequency hopping. Frequency hopping divides data into different segments, which are transmitted on different frequencies. This way, if interference degrades communication on a particular frequency, frequency hopping can still deliver data using a different frequency. Frequency hopping can provide channel diversity to combat interference.

[0042] However, the use of frequency hopping may introduce other issues that may not be desirable. For example, when communication symbols are segmented, frequency hopping may result in resource fragmentation. This fragmentation may make it difficult to reconstruct the message when it is received. In addition, frequency hopping may be sensitive to dynamic events, which may limit flexible downlink and / or uplink adjustments. In this way, introducing frequency hopping for PUSCH communication may require balancing different factors to provide frequency hopping functionality without disrupting other elements of 5G communication.

[0043] This disclosure describes a process for introducing PUSCH transmissions with inter-slot hopping, inter-repeat hopping, and intra-repeat hopping. This process can help legacy and / or modern UEs provide PUSCH communications while employing frequency hopping. Furthermore, the embodiments described herein can limit resource fragmentation to provide more reliable communications and can allow time-frequency resources to be shared between different UEs. Some UEs can use the Rel-15 PUSCH frequency hopping scheme, while other UEs can use the Rel-16 PUSCH frequency hopping scheme.

[0044] As will be further explained below, the UE can receive frequency domain resource allocation from the network node. For example, the frequency domain resource allocation can indicate a specific frequency group around the starting frequency and a second frequency group around the offset frequency, wherein one / multiple frequencies are associated with physical resource blocks (one / multiple PRBs). The starting or transmission frequency and the offset frequency can be used for frequency hopping. In some embodiments, the UE can support inter-slot frequency hopping, inter-repetition frequency hopping, or intra-repetition frequency hopping. In some embodiments, the index of the frequency hopping offset can be indicated by downlink control information (DCI) format 0_2 / 0_1 / 0_0.

[0045] Based on the configuration of the data, the settings of the UE and / or the commands received from the communication node, the UE can be configured to transmit a data set including data symbols using a physical uplink shared channel (PUSCH) transmission scheme. The UE can then determine whether to perform the transmission using inter-slot hopping, inter-repetition hopping or intra-repetition hopping. The UE can receive one or more signalings from the communication node to determine whether to apply frequency hopping to the PUSCH. When frequency hopping is applied, the one or more signalings may indicate which hopping scheme to use among inter-slot hopping, inter-repetition hopping or intra-repetition hopping. In NR Rel-16, the so-called PUSCH repetition type B is introduced. The time domain resources of PUSCH repetition type B are characterized by a triplet (S, L, K). The time domain resources consist of K PUSCH nominal repetitions; each PUSCH nominal repetition consists of L OFDM symbols; and S is the starting symbol index in the time slot where the first symbol in the first PUSCH nominal repetition appears. Because the nominal repetition portion is contained in two time slots and / or one or more symbols in the nominal repetition are not available for this PUSCH repetition type B transmission, and there are fewer than L symbols in the resulting actual repetition, the PUSCH nominal repetition can be segmented into one or more actual repetitions. In some cases, there may be a single actual repetition generated from the nominal repetition, and the number of symbols in the actual repetition is less than L. If all symbols under the nominal repetition are available for this PUSCH repetition type B transmission and the nominal repetition is completely contained in one time slot, the nominal repetition generates one actual repetition with L symbols. Inter-slot hopping, inter-repetition hopping, or intra-repetition hopping maps the actual repetition from the nominal repetition to one or more frequency locations. For inter-slot hopping and inter-repetition hopping, the frequency locations of the symbols in the actual repetition are the same; for intra-repetition hopping, the frequency locations of some symbols may be different from the frequency locations of some other symbols within some actual repetitions.

[0046] In some embodiments utilizing inter-slot frequency hopping, all symbols in an actual repetition start from the same frequency position, and further, all symbols in all actual repetitions within the same time slot start from the same frequency position. In some embodiments, all actual repetitions within the same time slot start from the same frequency position.

[0047] In some embodiments, for inter-repetition frequency hopping, all symbols in the actual repetition start from the same frequency position. In addition, all symbols in all actual repetitions within the same nominal repetition start from the same frequency position.

[0048] In some embodiments utilizing intra-repeat frequency hopping, when a nominal repetition is mapped to one or more actual repetitions, the number of symbols in the actual repetition is compared to a threshold value, X. If the number of symbols in the actual repetition is not less than X, the actual repetition is divided into two parts, with the first part containing a lower bound (X / 2) symbols and the second part containing an upper bound (X / 2) symbols. The first part begins at the starting RB, and the second part begins at the starting RB modified by an offset. If the number of symbols in the actual repetition is less than X, all symbols in the actual repetition begin at the same frequency position, which can be the starting RB or the starting RB modified by an offset. The threshold value, X, can depend on L. In some embodiments, X can be the same as L.

[0049] In some embodiments utilizing intra-repeat frequency hopping, when a nominal repetition is mapped to one or more actual repetitions, the number of symbols in the actual repetition is compared to a threshold value X. If the number of symbols in the actual repetition is not less than X, the actual repetition is divided into two parts, with the first part containing lower-bound (X / 2) symbols and the second part containing upper-bound (X / 2) symbols. The first part begins at the starting RB, and the second part begins at the starting RB modified by an offset. In some embodiments, when the number of symbols in the actual repetition is less than X, or when a nominal repetition generates two or more actual repetitions, all symbols in the actual repetition begin at the same frequency location. To determine the frequency location at which all symbols in the actual repetition begin, symbols in the nominal repetition are represented by symbols with indices {1, 2, ..., L}. The indices are divided into two sets, e.g., {1, ..., lower-bound (L / 2)} and {lower-bound (L / 2)+1, ..., L}. If the actual repetition contains symbols with symbol indices belonging to the first set, all symbols in the actual repetition begin at a single frequency location (e.g., the starting RB). If the actual repetition does not have a symbol with an index belonging to the first set, the actual repetition starts at another frequency position (e.g., a starting RB modified by an offset). Alternatively, the test can be performed using the second set. If the actual repetition contains a symbol with a symbol index belonging to the second set, all symbols in the actual repetition start at one frequency position (e.g., a starting RB modified by an offset). If the actual repetition does not have a symbol with an index belonging to the second set, the actual repetition starts at another frequency position (e.g., a starting RB).

[0050] The triplet transmission parameters and other transmission parameters for PUSCH repetition type B may be provided in one or more signaling messages from the gNB, including RRC signaling from the network and dynamic signaling from DCI. In some embodiments, the UE may be a legacy device that can be upgraded to communicate using the Rel-16 protocol. In this case, the embodiments described herein may be used to configure communications to conform to Rel-16 and / or other 5G protocols.

[0051] For inter-slot hopping and / or inter-repetition hopping, the UE may transmit a PUSCH transmission for the first portion of a symbol within a first slot using the starting RB transmission frequency. This transmission may occur when repetitions are identified and / or when the symbols are segmented. That is, if the PUSCH nominal repetitions of the symbol are segmented, the starting RB transmission frequency may be used to transmit the actual repetitions in the first slot. Under this inter-slot and / or inter-repetition hopping scheme, the actual repetitions in the second slot are transmitted using a transmission frequency modified by an offset frequency. For example, the offset frequency may indicate a specific difference from the starting RB transmission frequency. The actual repetitions contained in the same slot are transmitted from the same frequency position, such as from the starting RB transmission frequency or the starting RB transmission frequency modified by the offset frequency. When the transmission jumps between the starting transmission frequency and the offset frequency, the formatting may be repeated for additional symbols of the data set to provide inter-slot and / or inter-repetition hopping for PUSCH transmission.

[0052] For intra-repeat frequency hopping, unsegmented symbols within a time slot can be transmitted by dividing the symbol into different partitions. The first partition can be transmitted using a first starting RB transmission frequency, while the second partition can be transmitted using a second offset frequency. This partitioning can occur within a time slot and / or provide intra-repeat frequency hopping.

[0053] If a group of symbols is determined to be segmented for intra-repeat hopping, the UE can disable intra-repeat hopping for that PUSCH repetition. In this case, the UE can use the starting RB transmission frequency to transmit the segmented symbols. In this way, disabling intra-repeat hopping can help reduce resource fragmentation. The UE can still use frequency hopping for other time slots and / or repetitions to provide channel diversity. In this way, the embodiments described herein can balance the different considerations for providing frequency hopping for PUSCH transmission.

[0054] Various implementations of these features will now be discussed with respect to the corresponding figures.

[0055] Figure 1 An example system 100 is shown that implements frequency hopping for Physical Uplink Shared Channel (PUSCH) communications in accordance with some embodiments. Figure 1An exemplary system architecture 100 of a network according to various embodiments is shown. The following description is provided for an exemplary system 100 operating in conjunction with LTE system standards and 5G or NR system standards provided by 3GPP technical specifications. However, the exemplary embodiments are not limited in this regard and may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G) systems), IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), and the like.

[0056] like Figure 1 As shown, system 100 includes UE 110A and UE 110B (collectively referred to as "UE 110" or "UE 101"). In this example, multiple UEs 110 are shown as smartphones (e.g., handheld touchscreen mobile computing devices that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing devices, such as consumer electronic devices, mobile phones, smartphones, feature phones, tablets, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, instrument clusters (ICs), heads-up display (HUD) devices, on-board diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), electronic engine management systems (EEMS), electronic / engine control units (ECUs), electronic / engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), connected or "smart" appliances, MTC devices, M2M, IoT devices, etc.

[0057] The UE 110 may be configured to connect to, e.g., be communicatively coupled to, a radio access network (RAN) including RAN nodes 120A, 120B. In an embodiment, the RAN may be an NG RAN or 5G RAN, an E-UTRAN, or a legacy RAN such as a UTRAN or GERAN. As used herein, the term "NG RAN" or the like may refer to a RAN operating in an NR or 5G system 100, while the term "E-UTRAN" or the like may refer to a RAN operating in an LTE or 4G system 100. The UE 110 may utilize connections (or channels), each of which includes a physical communication interface or layer (discussed in further detail below).

[0058] In this example, the connection is shown as an air interface to achieve communication coupling and can be consistent with a cellular communication protocol, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, and / or any other communication protocol discussed herein. In an embodiment, the UE 110 can directly exchange communication data via the ProSe interface. The ProSe interface can alternatively be referred to as a SL interface 105 and can include one or more logical channels, including but not limited to PSCCH, PSSCH, PSDCH, and PSBCH.

[0059] UE 110B may be configured as an access point (AP) (also referred to as a "WLAN node," "WLAN," "WLAN terminal," "WT," etc.). Connections may include local wireless connections, such as connections consistent with any IEEE 802.11 protocol, where the AP will include Wireless Fidelity. Router. In this example, the AP is shown connected to the Internet without being connected to the core network of the wireless system (described in further detail below). In various embodiments, the UE 110B, the RAN, and the AP may be configured to utilize LWA operation and / or LWIP operation. LWA operation may involve the RAN nodes 120A, 120B configuring the UE 110B in the RRC_CONNECTED state to utilize radio resources of LTE and WLAN. LWIP operation may involve the UE 110B using WLAN radio resources via IPsec protocol tunneling to authenticate and encrypt packets (e.g., IP packets) sent over the connection. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0060] The RAN may include one or more AN nodes or RAN nodes 120A and 120B (collectively referred to as "multiple RAN nodes 120" or "RAN nodes 120"). As used herein, the terms "access node," "access point," etc. may describe equipment that provides radio baseband functionality for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BSs, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs, or TRPs, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN node" etc. may refer to a RAN node 120 (e.g., a gNB) operating in an NR or 5G system 100, while the terms "E-UTRAN node" etc. may refer to a RAN node 120 (e.g., an eNB) operating in an LTE or 4G system 100. According to various embodiments, the RAN node 120 may be implemented as one or more of a dedicated physical device such as a macrocell base station and / or a low power (LP) base station for providing a femtocell, picocell, or other similar cell having a smaller coverage area, smaller user capacity, or higher bandwidth than a macrocell.

[0061] In some embodiments, all or part of the RAN nodes 120 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement a RAN functional split, such as a PDCP split, where the RRC and PDCP layers are operated by the CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes 120; a MAC / PHY split, where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes 120; or a "lower PHY" split, where the RRC, PDCP, RLC, MAC layers, and upper portions of the PHY layers are operated by the CRAN / vBBUP, while the lower portions of the PHY layers are operated by individual RAN nodes 120. This virtualization framework allows idle processor cores of the RAN nodes 120 to execute other virtualized applications. In some implementations, individual RAN nodes 120 may represent a plurality of RAN nodes 120 connected to the RAN via respective F1 interfaces ( Figure 11 ) are connected to the gNB-CU. In these implementations, the gNB-DUs may include one or more remote radio heads or RFEMs, and the gNB-CU may be operated by a server (not shown) located in the RAN or by a pool of servers in a manner similar to CRAN / vBBUP. Additionally or alternatively, one or more of the RAN nodes 120 may be next-generation eNBs (ng-eNBs), which are RAN nodes that provide E-UTRA user plane and control plane protocol terminations to the UE 110 and are connected to the 5GC via an NG interface (discussed below).

[0062] In a V2X scenario, one or more of the multiple RAN nodes 120 may be or function as an RSU. The term "roadside unit" or "RSU" may refer to any traffic infrastructure entity used for V2X communication. The RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, where an RSU implemented in or by a UE may be referred to as a "UE-type RSU," an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU," an RSU implemented in or by a gNB may be referred to as a "gNB-type RSU," and so on. In one example, an RSU is a computing device coupled to RF circuitry located on the roadside that provides connectivity support to passing vehicle UEs 110 (vUEs 110). The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicular and pedestrian traffic. The RSU may operate on the 5.9 GHz Direct Short Range Communication (DSRC) band to provide extremely low latency communications required for high-speed events, such as collision avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low latency communications as well as other cellular communication services. Additionally or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and / or provide connectivity to one or more cellular networks to provide uplink and downlink communications. Some or all of the computing device and the RSU's RF circuitry may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller and / or backhaul network.

[0063] Any of the RAN nodes 120 may serve as the endpoint for the air interface protocol and may be the first point of contact for the UE 110. In some embodiments, any of the RAN nodes 120 may perform various logical functions of the RAN, including but not limited to radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0064] In an embodiment, UE 110 may be configured to communicate with each other or with any of RAN nodes 120 using OFDM communication signals over a multi-carrier communication channel according to various communication techniques, such as, but not limited to, OFDMA communication techniques (e.g., for downlink communication) or SC-FDMA communication techniques (e.g., for uplink and ProSe or sidelink communication), although the scope of the embodiment is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0065] In some embodiments, a downlink resource grid may be used for downlink transmissions from any of the RAN nodes 120 to the UE 110, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, which represents the physical resources in the downlink in each time slot. This type of time-frequency plane representation is common for OFDM systems, making radio resource allocation intuitive. Each column and row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes multiple resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a collection of resource elements; in the frequency domain, this can represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0066] According to various embodiments, UE 110 and RAN node 120 communicate data (e.g., transmit data and receive data) over a licensed medium (also referred to as a "licensed spectrum" and / or a "licensed frequency band") and an unlicensed shared medium (also referred to as an "unlicensed spectrum" and / or an "unlicensed frequency band"). The licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, while the unlicensed spectrum may include a 5 GHz frequency band.

[0067] To operate in the unlicensed spectrum, the UE 110 and the RAN node 120 may operate using LAA, eLAA, and / or feLAA mechanisms. In these implementations, the UE 110 and the RAN node 120 may perform one or more known medium sensing operations and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmitting in the unlicensed spectrum. The medium / carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.

[0068] LBT is a mechanism by which equipment (e.g., multiple UEs 110, multiple RAN nodes 120, etc.) senses the medium (e.g., a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a particular channel in the medium is sensed to be unoccupied). The medium sensing operation may include CCA, which utilizes at least ED to determine whether other signals are present on the channel in order to determine whether the channel is occupied or idle. The LBT mechanism allows cellular / LAA networks to coexist with existing systems in unlicensed spectrum and with other LAA networks. ED may include sensing RF energy over a period of time on an intended transmission band and comparing the sensed RF energy to a predefined or configured threshold.

[0069] Typically, existing systems in the 5 GHz band are WLANs based on IEEE 802.11 technology. WLANs employ a contention-based channel access mechanism known as CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 110, an AP, etc.) intends to transmit, the WLAN node may first perform CCA before transmitting. In addition, in the event that more than one WLAN node senses the channel as idle and transmits simultaneously, a backoff mechanism is used to avoid collisions. The backoff mechanism may be a counter randomly introduced within the CWS that increases exponentially when a collision occurs and is reset to a minimum value when the transmission is successful. The LBT mechanism designed for LAA is somewhat similar to CSMA / CA for WLAN. In some implementations, the LBT process for a DL or UL transmission burst (including PDSCH or PUSCH transmission) may have an LAA contention window of variable length between X and Y ECCA slots, where X and Y are the minimum and maximum values ​​of the CWS for LAA. In one example, the minimum CWS for LAA transmissions may be 9 microseconds (μs); however, the size of the CWS and MCOT (eg, transmission burst) may be based on government regulatory requirements.

[0070] The LAA mechanism is built on the Carrier Adaptation (CA) technology of the LTE-Advanced system. In CA, each aggregated carrier is called a CC. A CC can have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and up to five CCs can be aggregated, resulting in a maximum aggregate bandwidth of 100 MHz. In an FDD system, the number of aggregated carriers can be different for DL ​​and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, each CC can have a different bandwidth than other CCs. In a TDD system, the number of CCs and the bandwidth of each CC are generally the same for DL ​​and UL.

[0071] CA also includes individual serving cells to provide individual CCs. The coverage of the serving cells may be different, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell or PCell may provide the PCC for both UL and DL and may handle activities related to RRC and NAS. The other serving cells are called SCells, and each SCell may provide individual SCCs for both UL and DL. SCCs may be added and removed as needed, and changing the PCC may require the UE 101 to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells may operate in unlicensed spectrum (referred to as "LAA SCells"), and the LAA SCells are assisted by the PCells operating in the licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells indicating different PUSCH starting positions within the same subframe.

[0072] The PDSCH carries user data and higher layer signaling to multiple UEs 110. The PDCCH carries, among other information, information about the transport format and resource allocation associated with the PDSCH channel. It may also inform multiple UEs 110 about the transport format, resource allocation, and HARQ information associated with the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to UEs 110B within a cell) may be performed on any of the multiple RAN nodes 120 based on channel quality information fed back from any of the multiple UEs 110. Downlink resource allocation information may be sent on the PDCCH for (e.g., allocated to) each of the UEs 110.

[0073] PDCCH uses CCE to transmit control information. Before being mapped to resource elements, the PDCCH complex-valued symbols can first be organized into quadruples, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to nine sets of four physical resource elements, respectively, called REGs. Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the DCI and the channel conditions, one or more CCEs can be used to transmit the PDCCH. There may be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8).

[0074] Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some embodiments may utilize EPDCCH that uses PDSCH resources for control information transmission. One or more ECCEs may be used to transmit EPDCCH. Similar to the above, each ECCE may correspond to a set of nine physical resource elements, called EREGs, including four physical resource elements. In some cases, an ECCE may have other numbers of EREGs.

[0075] The RAN nodes 120 may be configured to communicate with each other via an interface. In an embodiment where the system 100 is an LTE system (e.g., when the core network (CN) 140 is an EPC), the interface may be an X2 interface. The X2 interface may be defined between two or more RAN nodes 120 (e.g., two or more eNBs, etc.) connected to the EPC, and / or between two eNBs connected to the EPC. In some implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide a flow control mechanism for user packets transmitted over the X2 interface and may be used to convey information regarding the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information regarding user data transmitted from the MeNB to the SeNB; information regarding successful in-sequence delivery of PDCP PDUs for user data from the SeNB to the UE 110; information regarding PDCP PDUs that were not delivered to the UE 110; information regarding the current minimum expected buffer size at the SeNB for transmitting user data to the UE; and the like. X2-C provides intra-LTE access mobility functions, including context transfer from the source eNB to the target eNB, user plane transmission control, load management functions, and inter-cell interference coordination functions.

[0076] In an embodiment where the system 100 is a 5G or NR system (e.g., when the CN 140 is a 5GC), the interface may be an Xn interface. The Xn interface is defined between two or more RAN nodes 120 (e.g., two or more gNBs, etc.) connected to a 5GC, between a RAN node 120 (e.g., a gNB) and an eNB connected to a 5GC, and / or between two eNBs connected to a 5GC. In some implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and flow control functions. The Xn-C may provide management and error handling functions for managing the functionality of the Xn-C interface; mobility support for the UE 110 in connected mode (e.g., CM-CONNECTED) includes functions for managing UE mobility in connected mode between one or more RAN nodes 120. This mobility support may include context transfer from the old (source) serving RAN node 120 to the new (target) serving RAN node 120; and control of the user plane tunnel between the old (source) serving RAN node 120 and the new (target) serving RAN node 120. The Xn-U protocol stack may include a transport network layer built on the Internet Protocol (IP) transport layer, and a GTP-U layer built on top of the UDP and / or IP layers for carrying user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP)) and a transport network layer built on SCTP. SCTP may be built on top of the IP layer and may provide guaranteed delivery of application layer messages. Within the transport IP layer, signaling PDUs are delivered using point-to-point transport. In other implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same as or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0077] The RAN is shown as being communicatively coupled to a core network—in this embodiment, to a core network (CN) 120. The CN 140 may include a plurality of network elements 130 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 110) connected to the CN 140 via the RAN. Components of the CN 140 may be implemented in one physical node or separate physical nodes, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, NFV may be used to virtualize any or all of the aforementioned network node functions (described in further detail below) via executable instructions stored in one or more computer-readable storage media. A logical instance of the CN 140 may be referred to as a network slice, and a logical instance of a portion of the CN 140 may be referred to as a network sub-slice. The NFV architecture and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (alternatively, performed by proprietary hardware). In other words, the NFV system can be used to perform virtual or reconfigurable implementations of one or more EPC components / functions.

[0078] Generally speaking, the application server 150 may be an element that provides applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data services, etc.). The application server 150 may also be configured to support one or more communication services for the UE 110 via the CN 140 (e.g., VoIP sessions, PTT sessions, group communication sessions, social network services, etc.).

[0079] In an embodiment, CN 140 may be a 5GC, and RAN may be connected to CN 140 via an NG interface. In an embodiment, the NG interface may be divided into two parts: an NG user plane (NG-U) interface, which carries traffic data between RAN node 120 and UPF; and an S1 control plane (NG-C) interface, which is a signaling interface between RAN node 120 and AMF.

[0080] Figure 2A block diagram of an exemplary wireless system 200 of an electronic device implementing frequency hopping for PUSCH communication according to some embodiments of the present disclosure is shown. System 200 can be any of the UE electronic devices 110 of system 100. System 200 includes a processor 210, a transceiver 220, buffers 230a and 230b, a communication infrastructure 240, a memory 250, an operating system 252, an application 254, and an antenna 260. The illustrated system is provided as an exemplary portion of wireless system 200, and system 200 may include other circuits and subsystems. In addition, although the systems of wireless system 200 are shown as separate components, embodiments of the present disclosure may include any combination of these components, fewer components, or more components.

[0081] Memory 250 may include random access memory (RAM) and / or cache memory, and may include control logic components (e.g., computer software) and / or data. Memory 250 may include other storage devices or memories, such as, but not limited to, a hard drive and / or a removable storage device / unit. According to some examples, an operating system 252 may be stored in memory 250. The operating system 252 may manage the transfer of data from memory 250 and / or one or more application programs 254 to processor 210 and / or transceiver 220. In some examples, the operating system 252 maintains one or more network protocol stacks (e.g., an Internet protocol stack, a cellular protocol stack, etc.) that may include multiple logical layers. At the corresponding layer of the protocol stack, the operating system 252 includes control mechanisms and data structures to perform the functions associated with that layer.

[0082] According to some examples, applications 254 may be stored in memory 250. Applications 254 may include applications used by wireless system 200 and / or a user of wireless system 200 (e.g., user applications). Applications in applications 254 may include applications such as, but not limited to, Siri, TM , FaceTime TM , radio streaming, video streaming, remote control and / or other user applications.

[0083] As an alternative or in addition to the operating system, system 200 may include a communication infrastructure 240. Communication infrastructure 240 provides, for example, communication between processor 210, transceiver 220, and memory 250. In some implementations, communication infrastructure 240 may be a bus. Processor 210, together with instructions stored in memory 250, executes operations that enable the wireless system 200 of system 100 to implement frequency hopping for PUSCH communications as described herein. Additionally or alternatively, transceiver 220 executes operations that enable the wireless system 200, as a UE 110 of system 100, to implement frequency hopping for PUSCH communications as described herein.

[0084] According to some embodiments, the transceiver 220 transmits and receives communication signals that support frequency hopping for PUSCH communications and can be coupled to the antenna 260. The antenna 260 may include one or more antennas that may be of the same or different types. The transceiver 220 allows the system 200 to communicate with other devices, which may be wired and / or wireless. The transceiver 220 may include a processor, a controller, radio components, sockets, plugs, buffers, and similar circuits / devices for connecting to a network and communicating on a network. According to some examples, the transceiver 220 may include one or more circuits for connecting to a wired network and / or a wireless network and communicating on a wired network and / or a wireless network. The transceiver 220 may include a cellular subsystem, a WLAN subsystem, and / or a Bluetooth subsystem. TM subsystems, each of which includes its own radio transceiver and protocol, as will be understood by those skilled in the art based on the discussion provided herein. In some implementations, transceiver 220 can include more or fewer systems for communicating with other devices.

[0085] The cellular subsystem (not shown) may include one or more circuits (including a cellular transceiver) for connecting to and communicating on a cellular network. Cellular networks may include, but are not limited to, 3G / 4G / 5G networks such as Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), etc. Bluetooth TM Subsystems (not shown) may include a system for implementing Bluetooth-based TM Protocol, Bluetooth TM Low Energy Protocol or Bluetooth TM One or more circuits for connection and communication with low-power long-range protocols (including Bluetooth TMThe WLAN subsystem (not shown) may include one or more circuits (including a WLAN transceiver) to enable connection and communication over a WLAN network, such as, but not limited to, a network based on the standards described in IEEE 802.11 (such as, but not limited to, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11bc, IEEE 802.11bd, IEEE 802.11be, etc.).

[0086] According to some embodiments, processor 210, alone or in combination with memory 250 and / or transceiver 220, implements frequency hopping for PUSCH communications. For example, system 200 is configured to generate and transmit frequency hopping for PUSCH communications associated with a buffer (e.g., buffer 230a and / or buffer 230b) of transceiver 220.

[0087] According to some examples, processor 210, alone or in combination with transceiver 220 and / or memory 205, can receive rules and / or parameters associated with frequency hopping for PUSCH communications from, for example, RAN node 120. For example, RAN node 120 can transmit control information related to frequency domain resource allocation and / or resource block (RB) allocation. In some embodiments, RAN node 120 can indicate the type of frequency hopping to be performed, such as inter-slot hopping, inter-repeat hopping, or intra-repeat hopping. Processor 210, alone or in combination with transceiver 220 and / or memory 205, can determine, generate, and transmit PUSCH communications using frequency hopping based on the received rules and / or parameters.

[0088] Furthermore, the processor 210 , alone or in combination with the transceiver 220 and / or the memory 205 , may receive a UL MU transmission schedule from, for example, the RAN node 120 and transmit the buffered data based on the received UL MU transmission schedule.

[0089] Figure 3A A block diagram 300A illustrates inter-slot frequency hopping according to some embodiments. The block diagram 300A may illustrate a Figure 1 300A. UE 110 and / or wireless system 200 may transmit data using the inter-slot hopping scheme depicted in block diagram 300A. This inter-slot hopping may correspond to Rel-15 frequency hopping. In some embodiments, block diagram 300A may be a timing diagram. UE 110 may transmit physical uplink shared channel (PUSCH) data using the inter-slot hopping scheme depicted in block diagram 300A.

[0090] Diagram 300A may include two axes. Axis 310 may indicate a frequency scale, while axis 320 may indicate a time scale. Diagram 300A may depict a communication frame and / or may be divided into different time slots 330. In some embodiments, time slots 330 may be subframes of a frame. UE 110 may transmit communication data by transmitting data in time slots 330. For example, the UE may transmit PUSCH data and / or transmit data to RAN node 120. Although Figure 3A Four time slots 330 are depicted in FIG, but more or fewer time slots may be used to transmit PUSCH data.

[0091] For wireless communications, including 5G communications, PUSCH data may be transmitted in a spread spectrum manner. For example, a frequency domain resource allocation and / or resource block (RB) allocation may be specified for UE 110 to use for transmitting information. In some embodiments, RAN node 120 may provide command information to UE 110 indicating the resource blocks to be utilized by UE 110 when transmitting PUSCH data. The frequency domain resource allocation may specify a frequency range and / or a subcarrier frequency range for transmission. Such a frequency range may be centered around a specific transmission frequency.

[0092] To illustrate an exemplary embodiment, block 340 may represent the transmission of data and / or symbols within time slot 330A. UE 110 may transmit block 340 using a frequency range indicated by a frequency domain resource allocation. Such a frequency range may be identified by the height of block 340, as depicted in block diagram 300A. The frequency range may be identified using axis 310 indicating a frequency scale. As previously described, the frequency domain resource allocation may indicate a center frequency and / or indicate the width of the frequency range used for PUSCH transmission.

[0093] For inter-slot frequency hopping, UE 110 may alternate the frequency range used to transmit data (such as a PUSCH transmission). For example, in a first time slot 330A, UE 110 may transmit block 340 using a first center transmission frequency and / or a first frequency range. The frequency range may be indicated by a frequency domain resource allocation. However, for a second time slot 330B, UE 110 may "hop" frequency and transmit block 350 using a second offset transmission frequency and / or a second frequency range. The second time slot 330B may be a different time instance and / or subframe than the first time slot 330A. The second time slot 330B may use an offset transmission frequency, which may be an offset from the transmission frequency used in time slot 330A. In some embodiments, the offset frequency may be applied to each subcarrier to switch the frequency range used for transmission.

[0094] Using offset frequencies may allow UE 110 to transmit data using a different range of carrier frequencies. Such transmission may provide channel diversity to combat the harmful effects of interference and / or channel fading.

[0095] As UE 110 continues to communicate, UE 110 may continue to alternate frequency ranges between the two ranges. For example, time slot 330C may use a first transmission frequency and / or a first frequency range transmission block 360, while time slot 330D may use a second offset frequency and / or a second frequency range transmission block 370.

[0096] In some embodiments, different frequencies may be used. For example, multiple offset frequencies may be used to generate different transmission patterns. However, for inter-slot frequency hopping, the range of transmission frequencies may be consistent within a particular time slot 330.

[0097] Figure 3B A block diagram 300B illustrates frequency hopping within a time slot according to some embodiments. The block diagram 300B may illustrate a signal from a UE such as Figure 1 300B). UE 110 may transmit data using the intra-slot frequency hopping scheme depicted in block diagram 300B.

[0098] Diagram 300B may include two axes. Axis 310 may indicate a frequency scale, while axis 320 may indicate a time scale. Diagram 300 may depict a communication frame and / or may be divided into different time slots 330. In some embodiments, time slots 330 may be subframes of a frame. UE 110 may communicate data by transmitting data in time slots 330. For example, the UE may transmit PUSCH data and / or transmit data to RAN node 120. Although four time slots 330 are depicted in FIG3 , more or fewer time slots may be used to transmit PUSCH data.

[0099] Similar to inter-slot frequency hopping, for wireless communications, including 5G communications, PUSCH data may be transmitted in a spread spectrum manner. For example, a frequency domain resource allocation may be specified for UE 110 to use for transmitting information. RAN node 120 may provide command information to UE 110 indicating the resource blocks to be utilized by UE 110 when transmitting PUSCH data. The frequency domain resource allocation may specify a frequency range and / or a subcarrier frequency range to be used for transmission. This frequency range may be centered around a specific transmission frequency.

[0100] Similar to inter-slot frequency hopping, intra-slot frequency hopping can achieve channel diversity by alternating the frequency range used to transmit data (such as PUSCH transmissions). Unlike inter-slot frequency hopping, intra-slot frequency hopping can alternate the center frequency and / or frequency range within a particular time slot 330.

[0101] To illustrate an exemplary embodiment, in time slot 330A, UE 110 may transmit data and / or symbols using blocks 345A and 345B. Within time slot 330A, UE 110 may transmit block 345A using a first center transmission frequency and / or a first frequency range. This frequency range may be indicated by a frequency domain resource allocation. UE 110 may transmit block 345B using a second offset transmission frequency and / or a second frequency range. Transmission of blocks 345A and 345B may occur within time slot 330A. In some embodiments, this type of intra-slot frequency hopping may partition a data set, a portion of data, and / or a data symbol into partitions for transmission using different frequency ranges within a particular time slot 330. Using intra-slot frequency hopping may provide additional frequency variation for PUSCH transmissions.

[0102] Similarly, for other time slots 330B, 330C, and 330D, the use of intra-time slot frequency hopping may result in the use of different frequencies for symbol division and transmission of data within a particular time slot 330. For example, in time slot 330B, block 355A may be transmitted using a first center transmission frequency and / or a first frequency range, while block 355B may be transmitted using a second offset frequency and / or a second frequency range. In some embodiments, these frequencies may be the same as those from time slot 330A. In time slot 330C, the UE may transmit blocks 365A and 365B, while in time slot 330D, the UE may transmit blocks 375A and 375B.

[0103] Figure 4 A block diagram 400 illustrates a PUSCH transmission with segmentation according to some embodiments. The segmentation depicted in block diagram 400 may illustrate segmentation due to symbols that may cross time slot boundaries. In some embodiments, block diagram 400 may illustrate different PUSCH transmission modes 420, 430, 440. These transmission modes 420, 430, 440 may indicate time domain transmission. In some embodiments, this PUSCH transmission structure may be used in Rel-16. Furthermore, for each transmission mode 420, 430, 440, a different time slot 410A, 410B, 410C may be used to transmit PUSCH data.

[0104] Transmission mode 420 may illustrate the transmission of PUSCH data without segmentation. In this case, the symbol data set may include symbol 422 and symbol 424. Although symbol 422 and symbol 424 may be different, based on the timing of the transmission, the UE may transmit the symbols within time slot 410A. In this case, the UE may apply frequency hopping within time slot 410A to divide the symbols and achieve channel diversity.

[0105] However, in transmission modes 430 and 440, a set of symbols may be segmented, which may result in symbols 432, 434, 436, 438, 442, and 444 being divided between two time slots 410A, 410B, respectively. This segmentation may create difficulties in performing frequency hopping because the segmented symbols may become fragmented if separated from adjacent symbols. For example, at a base station and / or node receiving a PUSCH transmission, the expectation may be a nominal repetition of received symbols, but the segmentation of timing may introduce fragmentation issues when frequency hopping is applied. In this way, symbols that cross time slot boundaries may introduce segmentation, which may complicate the frequency hopping process. Another example of such segmentation is Figure 5 shown.

[0106] Figure 5 A block diagram 500 illustrating symbol segmentation according to some embodiments is shown. Figure 5 Segmentation caused by downlink transmissions that may occur during a PUSCH transmission can be depicted. Block diagram 500 demonstrates this segmentation via symbol stream 520. A symbol can be a data set transmitted by a UE using PUSCH. In an exemplary embodiment, the nominal repetition length of a symbol can be four symbols. For example, symbols 520A through 520D designated as "1_1," "1_2," "1_3," and "1_4" can represent nominal repetitions. The nominal repetition can represent an agreed-upon length of symbols exchanged between a UE and a node. In some embodiments, the nominal repetition can represent a symbol slot size, such as four symbols. The term "repetition" can refer to a transport block. The actual data of the symbols between repetitions can be different. In some embodiments, each symbol 520 can represent a length of two or more symbols. This embodiment will be further described below.

[0107] The fragmentation of the data set may occur due to downlink transmissions received by the UE during the attempted transmission of symbol stream 520. In some cases, the downlink may interrupt this transmission. For example, a downlink may occur when attempting to transmit symbols 520G through 520J designated as "2_3," "2_4," "3_1," and "3_2." This group of symbols may be collectively referred to as fragmentation symbols 510. Downlink transmissions received by the UE may occur during those times, which may prevent the UE from transmitting fragmentation symbols 510.

[0108] In this case, even though the nominal length may be four symbols, for the second repetition, only two symbols 520E, 520F may be available to the UE to perform PUSCH transmission. Similarly, for the third nominal repetition, only two symbols 520K, 520L may be used.

[0109] In this way, downlink transmissions can further introduce segmentation into the PUSCH transmission scheme. When considering this segmentation, as well as the potential segmentation caused by symbols crossing slot boundaries, the use of frequency hopping becomes increasingly difficult given these complex scenarios. However, as will be described further below, even with this segmentation in mind, several implementations can be used to apply frequency hopping to PUSCH transmissions.

[0110] Figure 6A Block diagram 600A illustrates inter-slot and / or inter-repetition frequency hopping for physical uplink shared channel (PUSCH) communications, according to some embodiments. In some embodiments, block diagram 600A may depict a PUSCH transmission scheme when symbols are non-segmented. Block diagram 600A may be a timing diagram having two axes. Axis 610 may indicate a frequency scale, while axis 620 may indicate a time scale. Block diagram 600A may depict a communication frame and / or may be divided into different time slots 630. In some embodiments, a time slot 630 may be a subframe of a frame. A UE may transmit communication data by transmitting data in a time slot 630. For example, a UE may transmit PUSCH data and / or transmit data to a RAN node 120. Although two time slots 630 are depicted in FIG6 , more or fewer time slots may be used to transmit PUSCH data.

[0111] Similar to the previously described inter-slot frequency hopping configuration, the inter-slot frequency hopping depicted in FIG6 can use different frequency ranges to transmit PUSCH data based on the frequency domain resource allocation. These frequency ranges can alternate between time slots. For example, a first center transmission frequency and / or a first frequency range can be used to transmit blocks 640A and 640B in time slot 630A. This frequency range can be indicated by the frequency domain resource allocation. A second offset frequency and / or a second frequency range can be used to transmit blocks 640C and 640D in time slot 630B. In some embodiments, the UE can alternate between these frequency ranges to transmit PUSCH data when transmitting other blocks 640.

[0112] In block diagram 600A, blocks 640 may correspond to different symbols. Without symbol segmentation within slot 630, these symbols may be transmitted as blocks 640 using inter-slot frequency hopping. For example, if slot 630 can transmit four symbols, and each block 640 carries two symbols, then slot 630A may transmit four symbols using a first center transmission frequency and / or a first frequency range. Slot 630B may transmit four symbols using a second offset frequency and / or a second frequency range. These eight symbols may be different from the transmitted PUSCH data.

[0113] As mentioned earlier, when symbols may not be segmented, the UE can use this inter-slot hopping to transmit PUSCH data. Figure 6B A transmission scheme using inter-slot frequency hopping when symbols are segmented may be provided.

[0114] Figure 6A Inter-repeat hopping can also be depicted. In this scheme, with inter-repeat hopping, symbols can be transmitted in repetitions 630A and 630B rather than in slots 630A and 630B. These repetitions can represent nominal repetition lengths, as described further below. In this case, repetitions 630A and 630B can be used to perform inter-repeat hopping without using slots.

[0115] Figure 6B A block diagram 600B is shown for inter-slot and / or inter-repetition frequency hopping for physical uplink shared channel (PUSCH) communications with segmentation according to some embodiments. In some embodiments, the block diagram 600B may depict a method for Figure 7 Timing diagram of frequency hopping between time slots of the segments shown.

[0116] Figure 7 A block diagram of a physical uplink shared channel (PUSCH) data set 700 with segmentation is shown according to some embodiments. Figure 6B Previously described Figure 7 .

[0117] Figure 7 A data set 700 is depicted. The data set 700 can be organized into time slots 710, which can correspond to Figure 6B The 6:30 time slot and / or Figure 8A and Figure 8B repetitions 830. In some embodiments, the data set 700 may be organized into repetitions 710. For convenience, the term "time slot 710" will be used, but the term may refer to the time slot 710 and / or the repetition 710. Similar to the description of the time slot above, the UE may use the time slot 710 to transmit PUSCH data. In an embodiment, the time slot 710 may carry six data symbols. For example, symbol time slot 720A may represent two symbols. Time slot 710A may include a spatial allocation of three symbol time slots 720 (such as symbols 720A, 720B, and 720C). Each symbol may have an allocated space for transmitting two symbols. In this way, the length of the nominal repetition may be six symbols. For example, time slots 710A, 710B, 710C, and 710D may utilize a repetition length of six symbols. Reference will be made to Figure 7 、 Figure 6B 、 Figure 8A and Figure 8B This exemplary embodiment is further described.In some embodiments, the symbol length of time slot 710 may be greater or less than the indicated length.

[0118] In some embodiments, segmentation can occur within a particular time slot 710. This segmentation can divide symbols, which may cause them to be discontinuous. For example, within time slots 710A and 710B, segmentation can occur at symbol time slots 720B and 720E. In this way, symbol 720A can be separated from symbol 720C. Symbol 720D can be separated from symbol 720F. As previously described, this segmentation can occur, for example, due to downlink transmissions and / or crossing boundaries.

[0119] Downlink transmissions and / or boundary crossing effects may also occur at symbol slot 720H. However, this situation may not cause segmentation because the symbols in symbol slot 720G may still be contiguous. For example, symbol slot 720G may include four symbols that may be relevant for PUSCH transmission. Symbol slot 720H ​​may experience degradation and may prevent PUSCH transmission, but this prevention may not cause segmentation within slot 710C. Similarly, in slot 710D, segmentation may not occur. In this case, symbol slot 720I may include six symbols that may be relevant. This slot may not prevent PUSCH transmission.

[0120] Return to Figure 6B , block diagram 600B may illustrate a method for transmitting Figure 7 The diagram 600B may include two axes. Axis 610 may indicate a frequency scale, while axis 620 may indicate a time scale. Diagram 600B may depict a communication frame and / or may be divided into different time slots 630. Time slots 630 may correspond to, for example, Figure 7 The time slot 710 is depicted in FIG.

[0121] Similar to reference Figure 6A In a similar manner to the inter-slot frequency hopping described above, the UE may perform frequency hopping on segmented symbols used for PUSCH transmission. For example, the UE may alternate PUSCH transmissions between a first transmission frequency range and a second transmission frequency range. The first range may correspond to a first center transmission frequency, while the second range may correspond to an offset frequency. These ranges may correspond to frequency domain resource allocations.

[0122] To illustrate the transmission of segmented symbols, the UE may transmit segmented symbols in time slots 630A and 630B. For example, the UE may use a first frequency range to transmit symbols 645A and 645C. Due to the segmentation caused at symbol time slot 645B, the UE may not transmit a symbol in that time slot. Similarly, in time slot 630B, the UE may use a second frequency range to transmit symbols 645D and 645F. Due to the segmentation caused at symbol time slot 645E, the UE may not transmit a symbol in that time slot. Based on this configuration, even when symbols become segmented, the UE can still apply inter-slot hopping to PUSCH transmissions. As previously explained, this inter-slot hopping can help provide channel diversity.

[0123] Furthermore, such inter-slot hopping can allow for mixed frequency hopping scenarios, where some slots 630 may include segment symbols while others do not. For example, slots 630C and 630D may include symbols 645 that may not be segment symbols. For example, in slot 630C, the UE may transmit symbols 645G and 645H despite being blocked from transmitting in symbol slot 645I. Similarly, in slot 630D, which may include consecutive symbols 645J, the UE may perform such transmission using inter-slot hopping. In this manner, using this inter-slot hopping scheme, the UE may transmit PUSCH communications for both segment symbols and non-segment symbols.

[0124] Similar to Figure 6A , Figure 6B Inter-repeat hopping can also be depicted. In this scheme, with inter-repeat hopping, symbols can be transmitted as repetitions 630A through 630D, rather than as slots 630A through 630D. These repetitions can represent nominal repeat lengths, as described further below. In this case, repetitions 630A through 630D can be used to perform inter-repeat hopping without using slots. Similarly, when symbols are segmented, repetitions 630A through 630D can be used.

[0125] for Figure 6A and Figure 6B , the following protocol can also be used to further describe inter-slot frequency hopping. For inter-slot frequency hopping, the same frequency offset can be applied to the PUSCH repetitions within a specific time slot. This application can include PUSCH segmentation within that time slot. The frequency offset can alternate between two values: zero and RB 偏移 RB 偏移 It can be a frequency offset value from the starting transmission frequency. This alternation can be applied to the time slots with PUSCH allocation. The starting frequency (i.e., frequency range) of the resource block (RB) can be given by:

[0126]

[0127] In case of inter-repetition PUSCH frequency hopping, the frequency offset value can alternate between two values: zero and RB 偏移 In some embodiments, the value "p" may be a PUSCH repetition index, where 0 ≤ p ≤ P-1. In this case, the value "p" may be configured by a higher communication layer that is dynamically configured and / or signaled. The starting RB position of a PUSCH repetition "p" may be given by:

[0128]

[0129] If the PUSCH repetition is segmented, each segment may follow this formula. In some embodiments, for the segments under one PUSCH repetition, no additional frequency hopping is introduced.

[0130] Figure 8A A block diagram 800A illustrates intra-repetition frequency hopping for physical uplink shared channel (PUSCH) communications with segmentation, according to some embodiments. The block diagram 800A may depict Figure 7 Intra-repeat hopping of the data set 700 depicted in FIG. Unlike inter-repeat hopping, intra-repeat hopping can perform symbol segmentation within a particular repetition 830. Diagram 800A may include two axes. Axis 810 may indicate a frequency scale, while axis 820 may indicate a time scale. Diagram 800A may depict a communication frame and / or may be divided into different repetitions 830. Repetitions 830 may correspond to, for example, Figure 7 Time slot 710 is depicted in FIG.

[0131] Similar to reference Figure 3B Similar to the intra-slot frequency hopping described above, the UE may perform intra-repetition frequency hopping on symbols used for PUSCH transmission. The UE may divide consecutive symbols into different portions and transmit the different portions using different frequency ranges. For example, the UE may alternate PUSCH transmissions within repetition 830 between a first transmission frequency range and a second transmission frequency range. The first range may correspond to a first center transmission frequency and a first partition of symbols, while the second range may correspond to an offset frequency and a second partition of symbols. These ranges may correspond to frequency domain resource allocations.

[0132] However, if a symbol is segmented within a repetition 830, intra-repetition frequency hopping may be disabled for that particular repetition 830. The segmented symbols may be transmitted using the same frequency range within the repetition 830. From a segmentation perspective, this disabling may help prevent resource fragmentation. For example, disabling may reduce the complexity of PUSCH transmission and reception of the symbol.

[0133] To illustrate exemplary embodiments, Figure 7 As shown, the UE can use repetition 830 to transmit data set 700. In repetition 830A, symbols 840A and 840B can be segmented. In this case, the UE can disable intra-repetition frequency hopping. Then, the same transmission frequency and / or the same frequency range can be used to transmit symbols 840A and 840B. Similarly, in repetition 830B, symbols 840C and 840D can be segmented. The same transmission frequency can be used to transmit symbols 840C and 840D. The same transmission frequency can be used to transmit symbols 840A, 840B, 840C, and 840D. In this way, intra-repetition frequency hopping can be used. In some embodiments, intra-repetition frequency hopping can be combined with inter-slot frequency hopping and / or inter-repetition frequency hopping. Different transmission frequencies and / or different frequency ranges can be used to transmit repetitions 830A and 830B.

[0134] In contrast to these segmented symbols, repetitions 830C and 830D depict symbols 840 that may be non-segmented. In these cases, the UE may apply intra-repetition frequency hopping to the symbols to achieve channel diversity. For example, in repetition 830C, symbols 840E and 840F may be transmitted using different frequency ranges. As previously explained, although repetition 830C may include a portion where the UE may not perform a PUSCH transmission, that portion may not segment symbols 840E and 840F. Since symbols 840E and 840F are not segmented, the UE may perform intra-repetition frequency hopping on these symbols.

[0135] Similarly, repetition 830D may include symbols 840G and 840H. These symbols may be non-segmented. In this case, the UE may divide the symbols into different parts and transmit the different parts using different transmission frequencies and / or different frequency ranges. In some embodiments, symbols 840G and 840H may be symbols of different lengths compared to symbols 840E and 840F. For example, symbols 840G and 840H may each be three symbols long, while symbols 840E and 840F may each be two symbols long. As previously explained, this intra-repetition frequency hopping configuration may provide a balance between complexity and possible resource fragmentation while still allowing channel diversity in PUSCH transmissions.

[0136] for Figure 8A , the following protocol can also be used to further describe intra-repeat frequency hopping. In the case of intra-repeat PUSCH repetition, each unsegmented PUSCH repetition can be divided into two hops. The number of symbols in the first hop can be given by the following formula:

[0137]

[0138] The number of symbols in the second jump can be given by:

[0139]

[0140] in is the length of the PUSCH transmission in OFDM symbols in one PUSCH repetition.

[0141] The starting resource block (RB) in each hop can be given by:

[0142]

[0143] For segmented PUSCH repetition, in order to avoid the limitation of convolution hopping scheme, the starting RB can be fixed to RB 起始 and / or

[0144] While intra-repetition PUSCH hopping can be disabled for a segment, in some embodiments, intra-repetition PUSCH hopping can be disabled if the length of the PUSCH segment is less than a threshold. For example, the threshold can be two symbols. To illustrate an example, while a portion of repetition 830C prevents PUSCH transmission, if that portion prevents PUSCH transmission to a state where available symbols are below a threshold, intra-repetition hopping can be disabled for repetition 830C.

[0145] For example, in some implementations utilizing intra-repeat frequency hopping, when a nominal repetition is mapped to one or more actual repetitions, the number of symbols in the actual repetition can be compared to a threshold value, X. If the number of symbols in the actual repetition is not less than X, the actual repetition is divided into two parts, with the first part containing lower bound (X / 2) symbols and the second part containing upper bound (X / 2) symbols. The first part begins at the starting RB, and the second part begins at the starting RB modified by an offset. Symbols 840E, 840F, 840G, and 840H may illustrate this length-based intra-repeat frequency hopping. If the number of symbols in the actual repetition is less than X, all symbols in the actual repetition begin at the same frequency position, which may be the starting RB or the starting RB modified by an offset. Repetitions 830A and 830B illustrate this implementation where symbols 840A, 840B, 840C, and 840D are below the threshold value. Threshold X may depend on L, and X may be the same as L.

[0146] Figure 8B A block diagram 800B illustrates frequency hopping within a repetition for length-based physical uplink shared channel (PUSCH) communications according to some embodiments. The block diagram 800B may depict Figure 7800B may include two axes. Axis 810 may indicate a frequency scale, while axis 820 may indicate a time scale. Diagram 800B may depict a communication frame and / or may be divided into different repetitions 830. Repetitions 830 may correspond to, for example, Figure 7 Time slot 710 is depicted in FIG.

[0147] In some embodiments, block diagram 800B may depict an embodiment in which symbols 845A, 845B, 845C, and / or 845D meet and / or exceed a threshold based on symbol length. For example, in this case, the threshold may be set to two symbols, and symbols 845A, 845B, 845C, and / or 845D may be two symbols long. In this case, symbols 845A, 845B, 845C, and / or 845D may be divided and transmitted using intra-repeat frequency hopping within repetitions 830A and 830B. Similarly, for repetitions 830C and 830D, symbols 845E, 845F, 845G, and / or 845H may meet the threshold. Consequently, since the threshold is met, these symbols may be transmitted using intra-repeat frequency hopping.

[0148] As previously explained, in some embodiments utilizing intra-repetition frequency hopping, when a nominal repetition is mapped to one or more actual repetitions, the number of symbols 845 in the actual repetition is compared to a threshold value X, and if the number of symbols 845 in the actual repetition is not less than X, the actual repetition is divided into two parts, with a lower limit (X / 2) symbols 845 in the first part and an upper limit (X / 2) symbols 845 in the second part. The first part starts from the starting RB and the second part starts from the starting RB modified by the offset. In some embodiments, when the number of symbols 845 in the actual repetition is less than X, or one nominal repetition generates two or more actual repetitions, all symbols 845 in the actual repetition start from the same frequency position. This embodiment Figure 8ADepicted in . In order to determine the frequency position at which all symbols in the actual repetition start, the symbols in the nominal repetition are represented by symbols with indices {1, 2, …, L}. The indices are divided into two sets, for example {1, …, floor(L / 2)} and {floor(L / 2)+1, …, L}. If the actual repetition contains symbols whose symbol indices belong to the first set, all symbols in the actual repetition start from one frequency position (e.g., the starting RB). If the actual repetition does not have symbols whose indices belong to the first set, the actual repetition starts from another frequency position (e.g., the starting RB modified by the offset). Alternatively, the test can be performed using the second set. If the actual repetition contains symbols whose symbol indices belong to the second set, all symbols in the actual repetition start from one frequency position (e.g., the starting RB modified by the offset). If the actual repetition does not have symbols whose indices belong to the second set, the actual repetition starts from another frequency position (e.g., the starting RB).

[0149] Figure 9A Flowchart 900A is shown for PUSCH frequency hopping communication according to some embodiments. In some embodiments, a UE such as UE 110 and / or wireless system 200 may execute flowchart 900A. In some embodiments, UE 110 may use flowchart 900A to transmit PUSCH data to RAN node 120. Flowchart 900A will be described with reference to UE 110; however, flowchart 900A is not limited to this exemplary embodiment. Flowchart 900A may be executed on any computing device, such as, for example, a computing device such as a UE 110 or a wireless system 200. Figure 10 The described computer systems and / or processing logic may include hardware (eg, circuitry, dedicated logic, programmable logic, microcode, etc.), software (eg, instructions executed on a processing device), or a combination thereof.

[0150] It should be understood that not all steps may be required to perform the disclosure provided herein. In addition, as will be appreciated by those skilled in the art, some of these steps may be performed simultaneously or in a manner similar to that described herein. Figure 9A The different orders shown are executed.

[0151] At 905, UE 110 may receive a frequency domain resource allocation indicating a transmission frequency and an offset frequency. For example, UE 110 may receive the frequency domain resource allocation from RAN node 120. The frequency domain resource allocation may indicate a first frequency range centered around the transmission frequency. Similarly, the frequency domain resource allocation may indicate a second frequency range centered around the offset frequency. In some embodiments, the offset frequency may represent a modification of the transmission frequency to convert the first frequency range to the second frequency range.

[0152] At 910, UE 110 may identify a data set having a first portion of symbols and a second portion of symbols using a physical uplink shared channel (PUSCH) transmission scheme. This PUSCH data set may be information and / or control data transmitted by UE 110 to RAN node 120. The data set may be divided into slots and / or repetitions of symbols. In some embodiments, each slot and / or repetition may be a symbol of the same length.

[0153] At 915, UE 110 may identify whether the PUSCH transmission scheme indicates the use of inter-slot hopping or inter-repetition hopping. In some embodiments, UE 110 may be commanded by RAN node 120 to use inter-slot hopping or inter-repetition hopping. In some embodiments, UE 110 and RAN node 120 may exchange control information to specify the use of inter-slot hopping or inter-repetition hopping. This exchange may occur prior to the PUSCH transmission. At 920, UE 110 may determine whether to use inter-slot hopping or inter-repetition hopping to transmit the data set.

[0154] If inter-slot frequency hopping is used, then at 925, UE 110 may transmit a first portion of the symbol in a first time slot using the transmission frequency indicated by the frequency domain resource allocation. At 930, UE 110 may transmit a second portion of the symbol in a second time slot using the transmission frequency modified by the offset frequency. This transmission is previously referred to as Figure 6A and Figure 6B If the symbols are segmented and / or non-segmented, inter-slot frequency hopping may be employed. In some embodiments, the time slots may continue to alternate between a transmission frequency and a transmission frequency modified by an offset frequency to transmit the symbols of the data set.

[0155] Similarly, if inter-repetition frequency hopping is used, then at 925, the UE 110 may transmit a first portion of the symbol using the transmission frequency indicated by the frequency domain resource allocation in the first transmission repetition. At 930, the UE 110 may transmit a second portion of the symbol using the transmission frequency modified by the offset frequency in the second transmission repetition. This transmission is previously referred to as Figure 6A and Figure 6B If the symbols are segmented and / or non-segmented, inter-repetition frequency hopping may be employed. In some embodiments, the repetitions may continue to alternate between the transmission frequency and the transmission frequency modified by the offset frequency to transmit the symbols of the data set.

[0156] Returning to 920, if inter-slot hopping or inter-repeat hopping is not used, UE 110 may identify whether the PUSCH transmission scheme indicates the use of intra-repeat hopping. In some embodiments, UE 110 may be instructed by RAN node 120 to use intra-repeat hopping. In some embodiments, UE 110 and RAN node 120 may exchange control information to specify users for intra-repeat hopping. This exchange may occur prior to the PUSCH transmission. At 940, UE 110 may determine whether to use intra-repeat hopping to transmit the data set.

[0157] At 950, UE 110 may perform intra-repetition frequency hopping for PUSCH transmission. Figure 9B The use of intra-repetition frequency hopping is further described.If the UE 110 does not perform intra-repetition frequency hopping, then at 945, the UE 110 may transmit the data set without frequency hopping using the PUSCH transmission scheme.

[0158] Figure 9B Flowchart 900B illustrates repetitive intra-frequency hopping for physical uplink shared channel (PUSCH) communications with segmentation, according to some embodiments. In some embodiments, a UE, such as UE 110 and / or wireless system 200, may execute flowchart 900B. In some embodiments, UE 110 may use flowchart 900B to transmit PUSCH data to RAN node 120. Flowchart 900B will be described with reference to UE 110; however, flowchart 900B is not limited to this exemplary embodiment. Flowchart 900B may be executed on any computing device, such as, for example, a computing device described with reference to FIG. Figure 10 The described computer systems and / or processing logic may include hardware (eg, circuitry, dedicated logic, programmable logic, microcode, etc.), software (eg, instructions executed on a processing device), or a combination thereof.

[0159] It should be understood that not all steps may be required to perform the disclosure provided herein. In addition, as will be appreciated by those skilled in the art, some of these steps may be performed simultaneously or in a manner similar to that described herein. Figure 9B The different orders shown are executed.

[0160] UE 110 may execute flowchart 900B as a continuation of flowchart 900A, as described with reference to FIG. Figure 9A The flowchart 900B may show reference Figure 8A and / or Figure 8B At 955, UE 110 may determine whether a portion of a symbol is segmented. For example, the segmentation of a symbol may be similar to that of reference 1. Figure 4 、 Figure 5 、 Figure 7 、 Figure 8A and Figure 8B The segmentation of the symbol may be identified for each slot and / or repetition of the symbol transmitted by UE 110. At 960, UE 110 may determine whether the symbol is segmented.

[0161] At 965, if the symbol is segmented, the UE 110 may disable intra-repeat frequency hopping. In some embodiments, the UE 110 may not apply intra-repeat frequency hopping to symbols in a particular repetition. In some embodiments, the UE 110 may also disable intra-repeat frequency hopping if the number of symbols within the repetition is below a threshold number of symbols. As will be explained further below, the UE 110 may determine at 975 and 980 whether the length of the symbol is below a threshold. In this case, the UE 110 may disable intra-repeat frequency hopping at 965. In either case, the portion of the symbol that may have been segmented cannot be transmitted using intra-repeat frequency hopping.

[0162] At 970, UE 110 may transmit the portion using the transmission frequency indicated by the frequency domain resource allocation. Figure 9A At 950, each portion of the segmented symbol may be evaluated. These portions may correspond to the values ​​previously described with reference to Figure 8A When the symbols are segmented, a specific transmission frequency and / or frequency range can be used within the repetition to transmit the segmented symbols without applying frequency hopping. In some embodiments, inter-repetition frequency hopping can be combined with intra-repetition frequency hopping. In this case, UE 110 can perform 925 and 930 to transmit portions of the data set using different repetitions with inter-repetition frequency hopping.

[0163] Returning to 960, if a portion of the symbols in the repetition is non-segmented and / or continuous, the UE 110 may determine whether the length of the symbol is below a threshold. In some embodiments, even if the symbol is segmented, the UE 110 may also determine whether the length of the symbol is below a threshold as previously described. Figure 8B This determination is performed as explained above. For example, in some embodiments, the length of the symbol may determine whether intra-repeat frequency hopping is applied. In this case, even if the symbol is segmented, intra-repeat frequency hopping may still be applied according to the configuration of UE 110. At 980, if UE 110 determines that the length of the symbol is below the threshold, UE 110 may return to 965 to disable intra-repeat frequency hopping, and at 970, may perform a transmission.

[0164] At 980, if the UE 110 determines that the length of the symbol is not below a threshold (eg, the length meets and / or exceeds the threshold), then at 985, the UE 110 may apply frequency hopping to divide the portions of the symbol. Figure 8A and Figure 8B This intra-repeat division is described. UE 110 may divide the symbol into a first partition and a second partition for transmission within the repetition. In some embodiments, the determination of the segmentation and / or threshold length may be optional elements. For example, the determination of whether to apply intra-repeat frequency hopping may be based on the segmentation and / or length threshold. In this manner, the determination of whether to apply intra-repeat frequency hopping is not limited to applying these two determination mechanisms. In some embodiments, steps 975 and / or 980 may be bypassed. For example, steps 975 and / or 980 may be optional elements of flowchart 900B. In this case, the determination of whether to apply intra-repeat frequency hopping may be based on whether the portion of the symbol is segmented.

[0165] At 990, UE 110 may transmit a first partition of symbols within a repetition using the transmission frequency indicated by the frequency domain resource allocation. At 995, UE 110 may transmit a second partition of symbols within a repetition using the transmission frequency modified by the offset frequency. In this case, UE 110 may perform intra-repetition frequency hopping on these partitions.

[0166] In some embodiments, if additional data from the data set is to be transmitted, the UE 110 may repeat elements of flowcharts 900A and 900B to transmit data using inter-slot hopping, inter-repeat hopping, intra-repeat hopping, and / or one of the three. The RAN node 120 may change the selected frequency hopping scheme. The RAN node 120 may also change the frequency domain resource allocation and change the transmission frequency and / or the offset frequency. In some embodiments, the change may change the frequency range corresponding to the transmission frequency and / or the frequency range corresponding to the offset frequency. Using the inter-slot hopping, inter-repeat hopping, and / or intra-repeat hopping described herein, the UE 110 and / or other communication systems may provide frequency hopping for PUSCH transmissions to provide channel diversity while avoiding potential resource fragmentation.

[0167] As previously explained, elements of flowcharts 900A and / or 900B may be optional and / or may not be performed. For example, if RAN node 120 transmits a command to UE 110 to use a specific transmission scheme (e.g., inter-slot hopping, inter-repeat hopping, and / or intra-repeat hopping), UE 110 may avoid checking elements to determine which hopping scheme to use. UE 110 may bypass elements 915, 920, 935, and / or 940, for example. However, in some embodiments, UE 110 may perform this determination based on an analysis of transmission parameters.

[0168] Figure 10 An exemplary computer system for implementing various embodiments is depicted. Figure 10The computer system 1000 shown may be one or more well-known computer systems for implementing various embodiments. For example, one or more computer systems 1000 may be used to implement any of the embodiments discussed herein, as well as combinations and subcombinations of the embodiments.

[0169] Computer system 1000 may include one or more processors (also referred to as central processing units or CPUs), such as processor 1004. Processor 1004 may be connected to a communication infrastructure or bus 1006.

[0170] The computer system 1000 may also include user input / output devices 1003 , such as a monitor, keyboard, pointing device, etc., that can communicate with the communication infrastructure 1006 through the user input / output interface 1002 .

[0171] One or more of the processors 1004 may be a graphics processing unit (GPU). In an embodiment, a GPU may be a processor that is a specialized electronic circuit designed to process mathematically intensive applications. A GPU may have an efficient parallel architecture for processing large blocks of data in parallel, such as mathematically intensive data commonly found in computer graphics applications, images, videos, and the like.

[0172] The computer system 1000 may also include a main memory or primary storage 1008, such as random access memory (RAM). The main memory 1008 may include one or more levels of cache. The main memory 1008 may store control logic components (i.e., computer software) and / or data therein.

[0173] The computer system 1000 may also include one or more secondary storage devices or memories 1010. The secondary storage 1010 may include, for example, a hard disk drive 1012 and / or a removable storage device or drive 1014. The removable storage drive 1014 may be a floppy disk drive, a tape drive, an optical disk drive, an optical storage device, a tape backup device, and / or any other storage device / drive.

[0174] The removable storage drive 1014 can interact with a removable storage unit 1018. The removable storage unit 1018 may include a computer-usable or readable storage device having computer software (control logic) and / or data stored thereon. The removable storage unit 1018 may be a floppy disk, a magnetic tape, an optical disk, a DVD, an optical storage disk, and / or any other computer data storage device. The removable storage drive 1014 can read from and / or write to the removable storage unit 1018.

[0175] Secondary memory 1010 may include other devices, apparatuses, components, tools, or other means for allowing computer programs and / or other instructions and / or data to be accessed by computer system 1000. Such devices, apparatuses, components, tools, or other means may include, for example, a removable storage unit 1022 and an interface 1020. Examples of removable storage unit 1022 and interface 1020 may include a program cartridge and cartridge interface (such as found in video game devices), a removable memory chip (such as an EPROM or PROM) and associated socket, a memory stick and USB port, a memory card and associated memory card slot, and / or any other removable storage unit and associated interface.

[0176] The computer system 1000 may also include a communication or network interface 1024. The communication interface 1024 may enable the computer system 1000 to communicate and interact with any combination of external devices, external networks, external entities, and the like (individually and collectively referenced by reference numeral 1028). For example, the communication interface 1024 may allow the computer system 1000 to communicate with an external or remote device 1028 via a communication path 1026, which may be wired and / or wireless (a combination of wired and / or wireless) and may include any combination of a LAN, a WAN, the Internet, and the like. Control logic components and / or data may be transferred to and from the computer system 1000 via the communication path 1026.

[0177] The computer system 1000 may also be any of, to name a few non-limiting examples, a personal digital assistant (PDA), a desktop workstation, a laptop or notebook computer, a netbook, a tablet computer, a smartphone, a smartwatch or other wearable device, an appliance, part of the Internet of Things, and / or an embedded system, or any combination thereof.

[0178] Computer system 1000 can be a client or server accessing or hosting any application and / or data through any delivery paradigm, including but not limited to: remote or distributed cloud computing solutions; local or on-premises software ("on-premises" cloud-based solutions); "as a service" models (e.g., Content as a Service (CaaS), Digital Content as a Service (DCaaS), Software as a Service (SaaS), Management Software as a Service (MSaaS), Platform as a Service (PaaS), Desktop as a Service (DaaS), Framework as a Service (FaaS), Backend as a Service (BaaS), Mobile Backend as a Service (MBaaS), Infrastructure as a Service (IaaS), etc.); and / or hybrid models including any combination of the foregoing examples or other services or delivery paradigms.

[0179] Any suitable data structures, file formats, and schemas in computer system 400 may be derived from standards including, but not limited to, JavaScript Object Notation (JSON), Extensible Markup Language (XML), another markup language (YAML), Extensible Hypertext Markup Language (XHTML), Wireless Markup Language (WML), MessagePack, XML User Interface Language (XUL), or any other functionally similar representation, alone or in combination. Alternatively, proprietary data structures, formats, or schemas may be used alone or in combination with known or open standards.

[0180] In some embodiments, a tangible, non-transitory device or article of manufacture includes a tangible, non-transitory computer-usable or readable medium having control logic (software) stored thereon, which may also be referred to herein as a computer program product or program storage device. This includes, but is not limited to, computer system 1000, main memory 1008, secondary memory 1010, and removable storage units 1018 and 1022, as well as tangible articles of manufacture embodying any combination of the foregoing. Such control logic, when executed by one or more data processing devices (such as computer system 1000), may cause such data processing devices to operate as described herein.

[0181] Based on the teachings contained in this disclosure, it will be apparent to those skilled in the relevant art how to use Figure 10 The embodiments of the present disclosure may be made and used with data processing devices, computer systems, and / or computer architectures other than those shown. In particular, the embodiments may operate with software, hardware, and / or operating system implementations other than those described herein.

[0182] It should be understood that the detailed description section, and not any other sections, is intended to be used to interpret the claims. The other sections may set forth one or more, but not all, exemplary embodiments contemplated by the inventors, and thus are not intended to limit the present disclosure or the appended claims in any way.

[0183] Although the present disclosure describes exemplary embodiments for exemplary fields and applications, it should be understood that the present disclosure is not limited thereto. Other embodiments and modifications are possible and are within the scope and spirit of the present disclosure. For example, and without limiting the generality of this paragraph, the embodiments are not limited to the software, hardware, firmware, and / or entities shown in the figures and / or described herein. In addition, the embodiments (whether or not explicitly described herein) have significant utility for fields and applications beyond the examples described herein.

[0184] Embodiments have been described herein with the aid of functional building blocks illustrating the implementation of specific functions and relationships thereof. For ease of description, the boundaries of these functional building blocks have been arbitrarily defined herein. Alternative boundaries may be defined so long as the specified functions and relationships (or their equivalents) are appropriately performed. Additionally, alternative embodiments may perform functional blocks, steps, operations, methods, etc., in an order different from that described herein.

[0185] References herein to "one embodiment," "embodiment," "exemplary embodiment," or similar phrases indicate that the described embodiment may include specific characteristic structures, structures, or characteristics, but each embodiment may not necessarily include specific characteristic structures, structures, or characteristics. In addition, such wording does not necessarily refer to the same embodiment. In addition, when specific characteristic structures, structures, or characteristics are described in conjunction with an embodiment, it is within the knowledge of those skilled in the art to incorporate these characteristic structures, structures, or characteristics into other embodiments, regardless of whether they are explicitly mentioned or described herein. In addition, some embodiments may be described using the expressions "coupled" and "connected" and their derivatives. These terms are not necessarily intended to be synonyms for each other. For example, some embodiments may be described using the terms "connected" and / or "coupled" to indicate that two or more elements are in direct physical contact and / or electrical contact with each other. However, the term "coupled" may also refer to two or more elements that are not in direct contact with each other, but still collaborate and / or interact with each other.

[0186] The breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.

[0187] As described above, various aspects of the present technology may include collecting and using data available from various sources to, for example, improve or enhance functionality. The present disclosure contemplates that, in some instances, these collected data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, Twitter IDs, home addresses, data or records related to the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying information or personal information. The present disclosure recognizes that the use of such personal information data in the present technology can be used to benefit users.

[0188] This disclosure contemplates that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information will adhere to established privacy policies and / or practices. Specifically, such entities should implement and adhere to privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining the privacy and security of personal information. Such policies should be easily accessible to users and updated as the collection and / or use of data changes. Personal information collected from users should be used for the entity's legitimate and reasonable purposes and not shared or sold beyond those legitimate uses. Furthermore, such collection / sharing should only be done with the user's informed consent. Furthermore, such entities should consider taking any necessary steps to safeguard and secure access to such personal information and ensure that others with access to the personal information adhere to their privacy policies and procedures. Furthermore, such entities may subject themselves to third-party assessments to demonstrate compliance with widely accepted privacy policies and practices. Furthermore, policies and practices should be tailored to the specific type of personal information collected and / or accessed, and to applicable laws and standards, including jurisdictional considerations. For example, in the United States, the collection or access of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be maintained for different types of personal data in each country.

[0189] Regardless of the foregoing, the present disclosure also contemplates implementation schemes in which users selectively block the use or access of personal information data. That is, the present disclosure contemplates providing hardware components and / or software components to prevent or block access to such personal information data. For example, the present technology can be configured to allow users to selectively “opt in” or “opt out” of collecting personal information data at any time, for example, during or after registration for a service. In addition to providing “opt in” and “opt out” options, the present disclosure contemplates providing notifications related to access or use of personal information. For example, a user may be notified that their personal information data will be accessed when downloading an application, and then reminded again just before the personal information data is accessed by the application.

[0190] Furthermore, it is an object of the present disclosure that personal information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use. Risk can be minimized by limiting data collection and deleting data once it is no longer needed. In addition, and when applicable, including in certain health-related applications, data de-identification can be used to protect the privacy of users. De-identification can be facilitated by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than the address level), controlling how data is stored (e.g., aggregating data across users), and / or other methods, where appropriate.

[0191] Thus, while the present disclosure broadly encompasses the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that various embodiments may be implemented without requiring access to such personal information data. That is, various embodiments of the present technology will not be unable to function properly due to the lack of all or a portion of such personal information data.

Claims

1. A method for wireless communication, comprising: receiving a frequency domain resource allocation indicating a transmission frequency and an offset frequency; Identifying a data set having symbols using a physical uplink shared channel (PUSCH) transmission scheme; Identifying the use of frequency hopping within a repetition indication in the PUSCH transmission scheme; determining whether the symbol is non-segmented; disabling the intra-repetition frequency hopping in response to determining that the symbol is segmented; In response to determining that the symbol is non-segmented, determining whether a length of the symbol meets a symbol length threshold; In response to determining that the length of the symbol meets the symbol length threshold, dividing the symbol into a first partition and a second partition for intra-repetition frequency hopping; transmitting said first partition of symbols using said transmission frequency in a transmission repetition; as well as The second partition of the offset frequency symbols is transmitted in the transmission repetitions.

2. The method according to claim 1, further comprising: identifying the second data set using an intra-repetition frequency hopping PUSCH transmission scheme; determining that the second data set includes segment symbols; disabling intra-repetition frequency hopping; as well as The second data set is transmitted using the transmission frequency indicated by the frequency domain resource allocation.

3. The method according to claim 1, further comprising: identifying a second data set having a first portion of symbols and a second portion of symbols using an inter-slot hopping PUSCH transmission scheme; determining that the first portion and the second portion are segmented; transmitting the first portion using the transmission frequency in a first transmission time slot; as well as The second part is transmitted using the offset frequency in a second transmission time slot.

4. The method according to claim 1, further comprising: identifying a second data set having a first portion of symbols and a second portion of symbols using an inter-slot hopping PUSCH transmission scheme; determining that the first portion and the second portion are non-segmented; transmitting the first portion using the transmission frequency in a first transmission time slot; as well as The second part is transmitted using the offset frequency in a second transmission time slot.

5. The method of claim 1 , wherein transmitting using the offset frequency further comprises: The transmission frequency is modified by converting the transmission frequency using the offset frequency. The method according to claim 1 , wherein the frequency domain resource allocation indicates a first frequency range corresponding to the transmission frequency and a second frequency range corresponding to the offset frequency.

7. The method according to claim 1, further comprising: Alternating between the transmission frequency and the offset frequency to transmit additional PUSCH data.

8. A wireless communication system comprising: transceiver; and at least one processor coupled to the transceiver, wherein the at least one processor is configured to: receiving a frequency domain resource allocation indicating a transmission frequency and an offset frequency; Identifying a data set having symbols using a physical uplink shared channel (PUSCH) transmission scheme; Identifying the use of frequency hopping within a repetition indication in the PUSCH transmission scheme; determining whether the symbol is non-segmented; disabling the intra-repetition frequency hopping in response to determining that the symbol is segmented; In response to determining that the symbol is non-segmented, determining whether a length of the symbol meets a symbol length threshold; In response to determining that the length of the symbol meets the symbol length threshold, dividing the symbol into a first partition and a second partition for intra-repetition frequency hopping; transmitting, via the transceiver, the first partition of symbols using the transmission frequency in a first transmission repetition; as well as The second partition of symbols is transmitted using the offset frequency in the first transmission repetition via the transceiver.

9. The wireless communication system of claim 8, wherein the at least one processor is further configured to: identifying the second data set using an inter-repetition hopping PUSCH transmission scheme; dividing the symbols of the second data set into a first partition and a second partition for inter-repetition frequency hopping; transmitting the first partitioned portion of symbols of the second data set using the transmission frequency in a second transmission repetition; as well as The second partitioned portion of symbols of the second data set is transmitted using the offset frequency in a third transmission repetition.

10. The wireless communication system of claim 9, wherein the symbols of the second data set are segmented.

11. The wireless communication system of claim 9, wherein the symbols of the second data set are non-segmented.

12. The wireless communication system of claim 8, wherein the at least one processor is further configured to: identifying the second data set using an intra-repetition frequency hopping PUSCH transmission scheme; determining that the second data set includes segment symbols; disabling intra-repetition frequency hopping; and The second data set is transmitted using the transmission frequency indicated by the frequency domain resource allocation. 13 . The wireless communication system according to claim 8 , wherein the frequency domain resource allocation indicates a first frequency range corresponding to the transmission frequency and a second frequency range corresponding to the offset frequency.

14. The wireless communication system of claim 8, wherein the at least one processor is further configured to: Alternating between the transmission frequency and the offset frequency to transmit additional PUSCH data.

15. A method for wireless communication, comprising: transmitting, from a base station to a user equipment (UE), a frequency domain resource allocation indicating a transmission frequency and an offset frequency corresponding to a physical uplink shared channel (PUSCH) transmission scheme, wherein when symbols of a data set are non-segmented, and when it is determined that a length of the symbol meets a symbol length threshold in response to the symbols being non-segmented, the PUSCH transmission scheme divides the data set having the symbols into a plurality of parts for intra-repetition frequency hopping; receiving, at the base station and from the UE, a first partitioned portion of symbols from a transmitted data set using the transmission frequency; as well as A second partition of symbols is received at the base station and from the UE using the offset frequency. 16 . The method according to claim 15 , wherein the frequency domain resource allocation indicates a first frequency range corresponding to the transmission frequency and a second frequency range corresponding to the offset frequency.

17. The method according to claim 15, further comprising: Additional PUSCH data is received at the base station and from the UE, the additional PUSCH data being transmitted alternately using the transmission frequency and the offset frequency.

Images