Method and associated device for HARQ process configurable for uplink grant
By introducing HARQ process ID offset and periodic determination of HARQ process, the limitations of HARQ process configuration supported by multiple TSN service flows in the telecommunications system are solved, and flexible management and efficiency improvement of NR base stations are achieved.
Patent Information
- Application Number
- CN202080024611.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-03-28
- Filing Date
- 2020-03-23
- Publication Date
- 2024-11-01
- Estimated Expiration
- 2040-03-23
AI Technical Summary
In telecommunications systems, the current HARQ process ID determination method cannot be directly applied to multiple configured license configurations, resulting in significant restrictions on the configuration of NR base stations and the failure to clearly define when to start or not start uplink licenses and fail to clearly define when to start or not start uplink licenses Related HARQ processes and their license timers.
Introduced configurable HARQ process identifiers (HARQ process IDs) for multiple uplink licenses, HARQ processes related to uplink licenses are determined through HARQ process ID offset and periodicity, and selectively started or restarted. The configured license timer.
It realizes flexible scheduling and retransmission management of multiple TSN service flows, avoids configuration restrictions, and improves network flexibility and efficiency.
Smart Images

Figure CN113647041B_ABST
Abstract
Description
[0001] Related applications
[0002] This application claims the benefit of provisional patent application serial number 62 / 825,526, filed on March 28, 2019, the entire disclosure of which is incorporated herein by reference. Technical Field
[0003] The present disclosure relates to configuration of a Hybrid Automatic Repeat Request (HARQ) process in a telecommunication system. Background Art
[0004] Support for time-sensitive networking (TSN) traffic flows in telecommunication systems has been studied. For example, the 3rd Generation Partnership Project (3GPP) commissioned research project RP-182090, Revision SID: Study on New Radio (NR) Industrial Internet of Things (IoT). In addition, the study ended with Technical Report 38.825. The report specifically mentions that in TSN use cases (for example, in future factory environments), user equipment (UE) needs to deploy multiple periodic flows with critical priorities, each of which can have a different period. For example, multiple TSN flows can originate from different applications. Therefore, solutions for serving multiple TSN traffic flows in a single UE may be required.
[0005] Under 3GPP standards such as NR, configured uplink grants are provided to support TSN traffic flows. A configured uplink grant (as opposed to a dynamic uplink grant) is a persistent uplink grant that supports the latency, reliability, or other requirements of a TSN traffic flow. In order to serve multiple TSN flows simultaneously, it is beneficial to support multiple configured grant configurations and multiple semi-persistent scheduling (SPS) configurations in a single UE for a given bandwidth part (BWP) of a serving cell.
[0006] In 3GPP follow-up work items RP-190726 and RP-190728, detailed goals include:
[0007] Specification of enhanced uplink (UL) configuration grant transmission [RAN1, RAN2]
[0008] o Multiple active configurations for a given BWP for a serving cell allow for Type 1 and Type 2 configurations
[0009] Note: Vehicle-to-everything (V2X) use cases are also considered
[0010] The configured uplink grant may be supported by one of multiple hybrid automatic repeat request (HARQ) processes, each HARQ process identified by a separate HARQ process identifier (ID). The current NR Rel-15 specification calculates the HARQ process ID for each configured uplink grant as follows (see clause 5.4.1 in 3GPP Technical Specification (TS) 38.321):
[0011] For a configured uplink grant, the HARQ process ID associated with the first symbol of a UL transmission can be derived from the following equation:
[0012] HARQ Process ID=[floor(CURRENT_symbol / periodicity)]modulo nrofHARQ-Processes
[0013] However, the above-mentioned HARQ process ID decision method cannot be directly applied to the configured grants from multiple configured grant configurations because it leads to significant restrictions on the NR base station (gNB) configuration.
[0014] In NRrel-15, the Configured Grant Timer was introduced. The ConfiguredGrantTimer is used to prevent new configured grant transmissions for the same HARQ process. If a timer for a configured uplink grant is configured, this timer applies only to the HARQ process. This is to allow the network to have enough time to process the previous transmission and (in case of erroneous decoding at the gNB) send a retransmission dynamic UL grant. The way it is specified in the MAC specification is that a configured grant can be delivered to the HARQ entity for further processing only if the corresponding ConfiguredGrantTimer is not running (see clause 5.4.1 in 3GPP TS 38.321).
[0015] There are some challenges currently. With the introduction of support for multiple TSN service flows, the HARQ process associated with a configured uplink grant is unclear. In addition, there is a need to have correct operation of when a configured grant timer should be started or not started, and therefore a need to define the HARQ process for a configured uplink grant. Summary of the invention
[0016] A hybrid automatic repeat request (HARQ) process configurable for multiple uplink grants for a cell is provided. In the case of using multiple configured grant configurations, new rules defining HARQ process identifiers (IDs) for the configured grants are introduced. Based on this, the configured grant timers are selectively started / restarted.
[0017] Various embodiments are proposed herein to solve one or more of the problems disclosed herein. In some embodiments, a method for a HARQ process in a cell that can be configured for multiple configured uplink grants, performed by a wireless device, is provided, the method comprising: receiving an uplink grant, the uplink grant comprising a HARQ process ID; determining, based on a HARQ process ID offset, that a HARQ process associated with the HARQ process ID is configured for the configured uplink grant; and starting or restarting a configured grant timer for the HARQ process.
[0018] In some embodiments, the HARQ process ID is associated with a grant configuration of a configured uplink grant.
[0019] In some embodiments, determining that the HARQ process is configured for the configured uplink grant is further based on the HARQ process ID and the number of HARQ processes for each configured grant. In some embodiments, determining that the HARQ process is configured for the configured uplink grant includes: determining that the HARQ process ID is greater than or equal to the HARQ process ID offset and less than the sum of the HARQ process ID offset and the number of HARQ processes for the configured grant.
[0020] In some embodiments, the HARQ process ID for the configured uplink grant is determined according to:
[0021] HARQ Process ID=[floor(CURRENT_symbol / periodicity)]modulo nrofHARQ-Processes+harq-procID-offset,
[0022] Wherein, CURRENT_symbol is the symbol index of the data transmission for the uplink grant, periodicity is the period of the uplink grant, nrofHARQ-Processes is the number of HARQ processes for the configured grant, and harq-procID-offset is the HARQ process ID offset.
[0023] In some embodiments, the method further comprises: sending uplink data according to the uplink grant.In some embodiments, the uplink data comprises a HARQ process ID offset.
[0024] In some embodiments, the uplink grant is received via an RRC message.
[0025] In some embodiments, the uplink grant is received via a DCI message.
[0026] In some embodiments, the method further includes: receiving another uplink grant associated with another HARQ process ID different from the HARQ process ID; and determining whether another HARQ process associated with the HARQ process ID is configured for another configured uplink grant based on another HARQ process ID offset. In some embodiments, the method further includes: if another HARQ process is configured for another configured uplink grant, starting or restarting another configured grant timer for another HARQ process.
[0027] In some embodiments, a method for sending uplink data using a HARQ process performed by a wireless device is provided, the method comprising: receiving a first uplink grant associated with a first HARQ process ID; determining, based on the first HARQ process ID offset, that the first HARQ process is configured for a first configured uplink grant; and setting a first configured grant timer for the first uplink grant according to the first HARQ process.
[0028] In some embodiments, the first HARQ process is identified by a first HARQ process ID; and the first HARQ process ID is determined according to:
[0029] HARQ Process ID=[floor(CURRENT_symbol / periodicity)]modulo nrofHARQ-Processes+harq-procID-offset,
[0030] Wherein, CURRENT_symbol is the symbol index of the data transmission for the uplink grant, periodicity is the period of the uplink grant, nrofHARQ-Processes is the number of HARQ processes for the configured grant, and harq-procID-offset is the HARQ process ID offset.
[0031] In some embodiments, the method further comprises: receiving a second uplink grant associated with a second HARQ process ID; determining, based on the second HARQ process ID offset, that the second HARQ process associated with the second HARQ process ID is configured for a second configured uplink grant; and setting a second configured grant timer for the second uplink grant according to the second HARQ process. In some embodiments, the second configured grant timer is set with the same parameters as the first configured grant timer. In some embodiments, the second configured grant timer is set with at least one parameter different from the first configured grant timer.
[0032] In some embodiments, the method further comprises: sending first uplink data using the first uplink grant, and starting or restarting a first configured grant timer.
[0033] In some embodiments, a method for allocating uplink licenses for multiple license configurations, performed by a base station, is provided, the method comprising: configuring a first uplink license for a first service flow; configuring a second uplink license for a second service flow; setting a first HARQ process ID offset for the first uplink license, the first HARQ process ID offset corresponding to the first HARQ process ID; setting a second HARQ process ID offset for the second uplink license; and providing the first HARQ process ID offset to a first user equipment UE associated with the first service flow.
[0034] In some embodiments, the method further comprises: providing a second HARQ process ID offset to the first UE. In some embodiments, the method further comprises: providing a second HARQ process ID offset to a second UE associated with the second traffic flow.
[0035] In some embodiments, the method further comprises: determining a number of HARQ processes configured for the configured grant; and providing the number of HARQ processes configured for the configured grant to the first UE.
[0036] In some embodiments, the method further comprises: deactivating the second uplink grant; in response to deactivating the second uplink grant, resetting the first HARQ process ID offset. In some embodiments, the method further comprises: in response to deactivating the second uplink grant, updating the number of HARQ processes configured for the configured grant.
[0037] In some embodiments, the first HARQ process ID offset is provided via an RRC message.
[0038] In some embodiments, the first HARQ process ID offset is provided via a DCI message.
[0039] In some embodiments, a wireless device is provided for configuring a hybrid automatic repeat request HARQ process configurable for multiple uplink grants in a cell, and the wireless device is suitable for executing the method described in any one of the above embodiments.
[0040] In some embodiments, the wireless device comprises a processing circuit adapted to perform the method described in any one of the above embodiments.
[0041] In some embodiments, a base station is provided for allocating uplink grants for multiple grant configurations. The base station is suitable for executing the method described in any one of the above embodiments.
[0042] Certain embodiments may provide one or more of the following technical advantages: Selectively starting a configured grant timer based on whether the identified HARQ process belongs to one of a plurality of configured grant configurations, enabling the gNB to flexibly schedule retransmissions (when the configured grant timer is started) or not schedule retransmissions (in which case new data may be sent directly on the configured grant). BRIEF DESCRIPTION OF THE DRAWINGS
[0043] The accompanying drawings incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.
[0044] Figure 1 An example of a cellular communication network 100 is shown according to some embodiments of the present disclosure.
[0045] Figure 2A is a flow chart illustrating a method implemented in a user equipment (UE) according to certain embodiments.
[0046] Figure 2B It is shown Figure 2A A flow chart of an alternative embodiment of a method of.
[0047] Figure 3A is a flow chart illustrating a method implemented in a UE according to certain embodiments.
[0048] Figure 3B It is shown Figure 3A A flow chart of an alternative embodiment of a method of.
[0049] Figure 4A is a flow chart illustrating a method implemented in a base station according to certain embodiments.
[0050] Figure 4B It is shown Figure 4A A flow chart of an alternative embodiment of a method of.
[0051] Figure 5 is a schematic block diagram of a radio access node 500 according to some embodiments of the present disclosure.
[0052] Figure 6 is a schematic block diagram illustrating a virtualized embodiment of a radio access node according to some embodiments of the present disclosure.
[0053] Figure 7 is a schematic block diagram of a radio access node according to some other embodiments of the present disclosure.
[0054] Figure 8 is a schematic block diagram of a UE according to some embodiments of the present disclosure.
[0055] Fig. 9 is a schematic block diagram of a UE according to some other embodiments of the present disclosure.
[0056] Fig.10 An example communication system is shown in which embodiments of the present disclosure may be implemented.
[0057] Fig.11 Show Fig.10 Example implementations of a UE, a base station, and a host computer.
[0058] Fig.12 is a flow chart illustrating a method implemented in a communication system according to one embodiment.
[0059] Fig.13 is a flow chart illustrating a method implemented in a communication system according to one embodiment.
[0060] Fig.14 is a flow chart illustrating a method implemented in a communication system according to one embodiment.
[0061] Fig.15 is a flow chart illustrating a method implemented in a communication system according to one embodiment. DETAILED DESCRIPTION
[0062] The embodiments set forth below represent information that enables those skilled in the art to practice the embodiments, and illustrate the best mode for practicing the embodiments. When reading the following description according to the accompanying drawings, those skilled in the art will understand the concepts of the present disclosure, and will recognize the application of these concepts that are not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the present disclosure.
[0063] Radio node: As used herein, a "radio node" is a radio access node or a wireless device.
[0064] Radio access node: As used herein, a "radio access node" or "radio network node" is any node operating in a radio access network of a cellular communication network for wirelessly sending and / or receiving signals. Some examples of radio access nodes include, but are not limited to, base stations (e.g., new radio (NR) base stations (gNBs) in third generation partnership project (3GPP) fifth generation (5G) NR networks or enhanced or evolved node Bs (eNBs) in 3GPP long term evolution (LTE) networks), high power or macro base stations, low power base stations (e.g., micro base stations, pico base stations, home eNBs, etc.), and relay nodes.
[0065] Core network node: As used herein, a "core network node" is any type of node in a core network. Some examples of core network nodes include, for example, a mobility management entity (MME), a packet data network gateway (P-GW), a service capability exposure function (SCEF), etc.
[0066] Wireless Device: As used herein, a "wireless device" is any type of device that accesses (i.e., is served by) a cellular communication network by wirelessly sending and / or receiving signals to and / or from a radio access node. Some examples of wireless devices include, but are not limited to, user equipment (UE) and machine type communication (MTC) devices in 3GPP networks.
[0067] Network node: As used herein, a "network node" is any node that is part of the radio access network or the core network of a cellular communication network / system.
[0068] Note that the description given herein focuses on 3GPP cellular communication systems, and therefore, 3GPP terminology or terminology similar to 3GPP terminology is often used. However, the concepts disclosed herein are not limited to 3GPP systems.
[0069] Note that in the description of this document, reference may be made to the term "cell"; however, particularly with respect to 5G NR concepts, "beam" may be used instead of "cell", and therefore, it is important to note that the concepts described in this document apply equally to cells and beams.
[0070] Figure 1An example of a cellular communication network 100 according to some embodiments of the present disclosure is shown. In the embodiments described herein, the cellular communication network 100 is a 5G NR network. In this example, the cellular communication network 100 includes base stations 102-1 and 102-2, which are referred to as eNBs in LTE and gNBs in 5G NR, for controlling corresponding macro cells 104-1 and 104-2. The base stations 102-1 and 102-2 are collectively referred to as base stations 102 herein, and are also individually referred to as base stations 102. Similarly, the macro cells 104-1 and 104-2 are collectively referred to as macro cells 104 herein, and are also individually referred to as macro cells 104. The cellular communication network 100 may also include a plurality of low power nodes 106-1 to 106-4 that control corresponding small cells 108-1 to 108-4. The low power nodes 106-1 to 106-4 may be small base stations (such as pico or femto base stations) or remote radio heads (RRHs), etc. Note that, although not shown, one or more of the small cells 108-1 to 108-4 may alternatively be provided by the base station 102. The low power nodes 106-1 to 106-4 are collectively referred to herein as low power nodes 106, and are also individually referred to as low power nodes 106. Similarly, the small cells 108-1 to 108-4 are generally collectively referred to herein as small cells 108, and are also individually referred to as small cells 108. The base station 102 (and optionally the low power nodes 106) are connected to the core network 110.
[0071] Base station 102 and low power node 106 provide services to wireless devices 112-1 through 112-5 in corresponding cells 104 and 108. Wireless devices 112-1 through 112-5 are collectively referred to herein as wireless devices 112 and also individually as wireless devices 112. Wireless devices 112 are also sometimes referred to herein as UEs.
[0072] In an exemplary aspect, the cellular communication network 100 facilitates service of multiple time-sensitive network (TSN) traffic flows simultaneously. Therefore, for a given bandwidth part (BWP) of a serving cell (e.g., macro cell 104 or small cell 108), it is beneficial for the cellular communication network 100 to support multiple configured grant configurations and multiple semi-persistent scheduling (SPS) configurations in a single UE (e.g., wireless device 112).
[0073] A configured uplink grant to a UE (e.g., wireless device 112) may be supported by one of a plurality of hybrid automatic repeat request (HARQ) processes, each HARQ process being identified by a separate HARQ process identifier (ID). As described above, with the introduction of support for multiple TSN service flows, the HARQ process associated with a configured uplink grant becomes unclear.
[0074] In this regard, the current HARQ process ID decision method cannot be directly applied to the configured grants from multiple configured grant configurations because it results in significant restrictions on the configuration of the base station 112 (e.g., NR gNB). However, it is beneficial to separate the HARQ process identifier (PID) pools from the perspective of the grant configurations. One solution is to configure an offset associated with each configuration. This solution is logical because it separates the HARQ process pools between different grant configurations, and therefore, the grant configurations will have independent operation.
[0075] This configurable offset should be reflected in the medium access control (MAC) HARQ PID decision equation, as well as in the radio resource control (RRC) ConfiguredGrantConfig element. It can be described as:
[0076] HARQ Process ID=[floor(CURRENT_symbol / periodicity)]modulo nrofHARQ-Processes+harq-procID-offset
[0077] In addition, it is necessary to have correct operation of when the configured grant timer should be started or not started, and therefore the HARQ process for the configured uplink grant needs to be defined. For example, it appears several times in the MAC 3GPP specification (clause 5.4.2.1):
[0078] 4> If the uplink grant is for a C-RNTI and the identified HARQ process is configured for the configured uplink grant:
[0079] 5> Start or restart configuredGrantTimer (if configured) for the corresponding HARQ process when performing transmission.
[0080] To address this, a note in the MAC specification states the definition of the HARQ process for the configured grants:
[0081] NOTE 2: If the configured uplink grant is activated and the associated HARQ process ID is less than nrofHARQ-Processes, the HARQ process is configured for the configured uplink grant.
[0082] According to the above specification, when the gNB issues a dynamic uplink grant to the UE and the HARQ process identified by this grant is less than the nrofHARQprocesses configured for the configured grant, the configured grant timer is (re)started; otherwise, it is not (re)started.
[0083] According to the following embodiments, depending on whether the identified HARQ process belongs to a certain HARQ process group (e.g., a HARQ process group configured for a certain (or more) configured grant configuration in a plurality of configured grant configurations, or a HARQ process group valid for a certain (or more) configured grant configuration in a plurality of configured grant configurations). When the HARQ process is configured for a configured uplink grant, the configured grant timer is started / restarted. The following embodiments give details of this definition:
[0084] In a first exemplary aspect, a HARQ process is configured for a configured uplink grant if the configured uplink grant is activated and the associated HARQ process ID belongs to the following set:
[0085] HARQ-proc-Offset_i,HARQ-proc-Offset_i+1,...,HARQ-proc-Offset_i+nrofHARQ-Processes_i-1
[0086] Among them, HARQ-proc-Offset_i represents the HARQ process offset for the licensed configuration i, and nrofHARQ-Processes_i represents the number of HARQ processes for the configured licensed configuration i in RRC.
[0087] In addition, if the HARQ process belongs to a configured permitted operation or is configured for a configured permitted operation, the HARQ process is considered to be configured for the configured permitted operation; for example, according to the above-mentioned first exemplary aspect, the HARQ process is valid for any one of multiple configured permitted configurations.
[0088] In a second exemplary aspect, a HARQ process is configured for a configured uplink grant if the configured uplink grant is activated and the associated HARQ process ID is less than:
[0089] nrofHARQ-Processes_i*+HARQ-Proc-Offset_i*
[0090] Wherein, i* is the configuration index having the maximum value of HARQ-Proc-Offset.
[0091] In some embodiments, the gNB allocates consecutive HARQ process IDs starting from zero for different configurations.
[0092] Assume that some flows are stopped (and the associated configuration group (CG) is deactivated) and additional flows arrive at the UE. In this case, the gNB needs to configure new nrofHARQ-Processes_i and HARQ-Proc-Offset_i. The gNB may need to quickly allocate such parameters using a downlink control information (DCI) message instead of RRC. Therefore, in some embodiments, the gNB may use a DCI message to allocate such parameters.
[0093] In some cases, the gNB may allocate multiple CG configurations to overcome data arrival misalignment. Therefore, the gNB allocates the same nrofHARQ-Processes_i and HARQ-Proc-Offset_i per multiple configurations, as they will accommodate the same services. In this case, the configured grant timer should be started / restarted according to the same content as above. Figures 2A-4B These embodiments are further described.
[0094] Figure 2A 2 is a flow chart illustrating a method according to a particular embodiment. The method may be performed by a UE. The method begins at step 200, where an uplink grant including a HARQ process ID is received. The method also includes step 202, where a HARQ process associated with the HARQ process ID is determined to be configured for the configured uplink grant based on the HARQ process ID offset. In some examples, the HARQ process ID for the configured uplink grant is determined according to:
[0095] HARQ Process ID=[floor(CURRENT_symbol / periodicity)]modulo nrofHARQ-Processes+harq-procID-offset
[0096] Wherein CURRENT_symbol is the symbol index of the data transmission for the uplink grant, periodicity is the period of the uplink grant, nrofHARQ-Processes is the number of HARQ processes for the configured grant, and harq-procID-offset is the HARQ process ID offset. The method also includes step 204, wherein the configured grant timer for the HARQ process is started or restarted. Optionally, the method may include sending uplink data according to the uplink grant (e.g., by including the HARQ process ID offset).
[0097] Figure 2B It is shown Figure 2A2 is a flow chart of an alternative embodiment of a method for transmitting a first uplink grant to a UE, which may also be performed by a UE. The method begins at step 208, where a first uplink grant associated with a first HARQ process ID is received. The method also includes step 210, where it is determined whether the first HARQ process ID is less than or equal to a threshold HARQ process offset. The method also includes step 212, where if the first HARQ process ID is less than or equal to the threshold HARQ process offset, a first configured grant timer for the first uplink grant is set.
[0098] Figure 3A is a flow chart illustrating a method according to a specific embodiment. The method may be performed by a UE. The method begins at step 300, wherein a first uplink grant associated with a first HARQ process ID is received. The method further comprises step 302, wherein it is determined based on the first HARQ process ID offset that the first HARQ process is configured for a first configured uplink grant. The method further comprises step 304, wherein a first configured grant timer for the first uplink grant is set according to the first HARQ process. Optionally, the method may comprise step 306, wherein first uplink data is sent using the first uplink grant, and the first configured grant timer is started or restarted.
[0099] Figure 3B It is shown Figure 3A 308, wherein a first uplink grant associated with a first HARQ process ID is received. The method further comprises step 310, wherein a determination is made as to whether the first HARQ process ID belongs to a first grant configuration. The method further comprises step 312, wherein if the first HARQ process ID belongs to the first grant configuration, a first configured grant timer is set for the first grant configuration.
[0100] Figure 4A is a flow chart illustrating a method according to a particular embodiment. The method may be performed by a base station. The method begins at step 400, where a first uplink grant is configured for a first service flow (e.g., one of a plurality of TSN service flows). The method also includes step 402, where a second uplink grant is configured for a second service flow. The method also includes step 404, where a first HARQ process ID offset is set for the first uplink grant, the first HARQ process offset corresponding to the first HARQ process ID. The method also includes step 406, where a second HARQ process ID offset is set for the second uplink grant. The second HARQ process ID offset may be different from the first HARQ process ID offset (e.g., due to different periodicity or other parameters, as described above with respect to Figure 1The method further includes step 408, wherein a first HARQ process offset is provided to a first UE associated with a first service flow.
[0101] Figure 4B It is shown Figure 4A 4. The method of claim 4, which is a flow chart of an alternative embodiment of a method of claim 4, which may also be performed by a base station. The method begins at step 410, where a first uplink grant is allocated for a first HARQ process associated with a first HARQ process ID. The method also includes step 412, where a second uplink grant is allocated for a second HARQ process associated with a second HARQ process ID. The method also includes step 414, where a first HARQ process ID offset is set for the first HARQ process. The method also includes step 416, where a second HARQ process ID offset is set for the second HARQ process. The second HARQ process ID offset may be different from the first HARQ process ID offset (e.g., due to different periodicity or other parameters, as described above with respect to Figure 1 The method further comprises step 418, wherein a first configured grant timer is set for the first grant configuration. The method further comprises step 420, wherein a second configured grant timer is set for the second grant configuration.
[0102] Figure 5 5 is a schematic block diagram of a radio access node 500 according to some embodiments of the present disclosure. The radio access node 500 may be, for example, a base station 102 or 106. As shown, the radio access node 500 includes a control system 502, which includes one or more processors 504 (e.g., a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc.), a memory 506, and a network interface 508. The one or more processors 504 are also referred to as processing circuits herein. In addition, the radio access node 500 includes one or more radio units 510, each of which includes one or more transmitters 512 and one or more receivers 514 coupled to one or more antennas 516. The radio unit 510 may be referred to as a radio interface circuit or a part of a radio interface circuit. In some embodiments, the radio unit 510 is external to the control system 502 and is connected to the control system 502 via, for example, a wired connection (e.g., an optical cable). However, in some other embodiments, the radio unit 510 and possible antennas 516 are integrated with the control system 502. The one or more processors 804 operate to provide one or more functions of the radio access node 500 as described herein. In some embodiments, the functions are implemented in software stored in, for example, the memory 506 and executed by the one or more processors 504.
[0103] Figure 6 5 is a schematic block diagram illustrating a virtualized embodiment of a radio access node 500 according to some embodiments of the present disclosure. This discussion is equally applicable to other types of network nodes. In addition, other types of network nodes may have similar virtualized architectures.
[0104] As used herein, a "virtualized" radio access node is an implementation of a radio access node 500 in which at least a portion of the functionality of the radio access node 500 is implemented as a virtual component (e.g., via a virtual machine executed on a physical processing node in a network). As shown, in this example, the radio access node 500 includes a control system 502 and one or more radio units 510, the control system 502 including one or more processors 504 (e.g., CPU, ASIC, FPGA, etc.), a memory 506, and a network interface 508, each radio unit including one or more transmitters 512 and one or more receivers 514 coupled to one or more antennas 516, as described above. The control system 502 is connected to the radio unit 510 via, for example, an optical cable. The control system 502 is connected to one or more processing nodes 600 via a network interface 508, the one or more processing nodes 600 being coupled to a network 602 or being included as part of the network 602. Each processing node 600 includes one or more processors 604 (e.g., CPU, ASIC, FPGA, etc.), a memory 606, and a network interface 608.
[0105] In this example, the functionality 610 of the radio access node 500 described herein is implemented at one or more processing nodes 600, or distributed between the control system 502 and one or more processing nodes 600 in any desired manner. In some specific embodiments, some or all of the functionality 610 of the radio access node 500 described herein is implemented as a virtual component executed by one or more virtual machines implemented in a virtual environment hosted by the processing node 600. As will be appreciated by one of ordinary skill in the art, additional signaling or communication is used between the processing node 600 and the control system 502 in order to perform at least some of the desired functionality 610. Note that in some embodiments, the control system 502 may not be included, in which case the radio unit 510 communicates directly with the processing node 600 via a suitable network interface.
[0106] In some embodiments, a computer program comprising instructions is provided, which, when executed by at least one processor, causes the at least one processor to perform the functions of a radio access node 500 according to any embodiment described herein or a node (e.g., processing node 600) that implements one or more functions 610 of the radio access node 500 in a virtual environment. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of the following: an electrical signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).
[0107] Figure 7 700 is a schematic block diagram of a radio access node 500 according to some other embodiments of the present disclosure. The radio access node 500 includes one or more modules 700, each of which is implemented in software. The modules 700 provide the functionality of the radio access node 500 described herein. This discussion also applies to Figure 6 , wherein module 700 may be implemented at one of processing nodes 600 or distributed among multiple processing nodes 600 and / or distributed between processing node 600 and control system 502 .
[0108] Figure 8 is a schematic block diagram of a UE 800 according to some embodiments of the present disclosure. As shown, the UE 800 includes one or more processors 802 (e.g., CPU, ASIC, FPGA, etc.), a memory 804, and one or more transceivers 806, each transceiver 806 including one or more transmitters 808 and one or more receivers 810 coupled to one or more antennas 812. The transceiver 806 includes a radio front-end circuit connected to the antenna 812, and the radio front-end circuit is configured to condition the signal transmitted between the antenna 812 and the processor 802, as will be understood by a person of ordinary skill in the art. The processor 802 is also referred to herein as a processing circuit. The transceiver 806 is also referred to herein as a radio circuit. In some embodiments, the functionality of the UE 800 as described above may be implemented in whole or in part in software stored in, for example, the memory 804 and executed by the processor 802. Note that the UE 800 may include Figure 8 Additional components not shown in the figure, such as, for example, one or more user interface components (e.g., input / output interfaces (including displays, buttons, touch screens, microphones, speakers, etc.), and / or any other components for allowing information to be input into the UE 800 and / or allowing information to be output from the UE 800), a power source (e.g., a battery and associated power circuitry), etc.
[0109] In some embodiments, a computer program including instructions is provided, which, when executed by at least one processor, causes the at least one processor to perform the functions of the UE 800 according to any of the embodiments described herein. In some embodiments, a carrier including the aforementioned computer program product is provided. The carrier is one of the following: an electric signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).
[0110] Fig. 9 800 according to some other embodiments of the present disclosure. The UE 800 includes one or more modules 900, each of which is implemented in software. The modules 900 provide the functions of the UE 800 described herein.
[0111] refer to Fig.10 According to an embodiment, the communication system includes a telecommunication network 1300 such as a 3GPP type cellular network, which includes an access network 1002 such as a RAN, and a core network 1004. The access network 1002 includes a plurality of base stations 1006A, 1006B, 1306C such as NB, eNB, gNB, or other types of wireless access points (APs), each of which defines a corresponding coverage area 1008A, 1008B, 1008C. Each base station 1006A, 1006B, 1006C can be connected to the core network 1004 via a wired or wireless connection 1010. A first UE 1012 located in the coverage area 1008C is configured to be wirelessly connected to the corresponding base station 1006C or to be paged by the corresponding base station 1006C. A second UE 1014 in the coverage area 1008A can be wirelessly connected to the corresponding base station 1006A. Although multiple UEs 1012 , 1014 are shown in this example, the disclosed embodiments are equally applicable to scenarios where a single UE is in the coverage area or where a single UE is connecting to the corresponding base station 1006 .
[0112] The telecommunications network 1000 itself is connected to a host computer 1016, which may be embodied in the hardware and / or software of a stand-alone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 1016 may be under the ownership or control of a service provider, or may be operated by or on behalf of a service provider. Connections 1018 and 1020 between the telecommunications network 1000 and the host computer 1016 may extend directly from the core network 1004 to the host computer 1316, or may be connected via an optional intermediate network 1022. The intermediate network 1022 may be one of a public network, a private network, or a managed network, or a combination of more than one thereof; the intermediate network 1022 (if any) may be a backbone network or the Internet; in particular, the intermediate network 1022 may include two or more sub-networks (not shown).
[0113] Fig.10 The communication system as a whole implements a connection between the connected UE 1012, 1014 and the host computer 1016. The connection can be described as an over-the-top (OTT) connection 1024. The host computer 1016 and the connected UE 1012, 1014 are configured to use the access network 1002, the core network 1004, any intermediate network 1022, and possibly other infrastructure (not shown) as intermediaries to transmit data and / or signaling via the OTT connection 1024. The OTT connection 1024 can be transparent in the sense that the participating communication devices through which the OTT connection 1024 passes are unaware of the routes of the uplink and downlink communications. For example, the base station 1006 may not or need not be informed of the past route of the incoming downlink communication, wherein the incoming downlink communication has data that originates from the host computer 1016 to be forwarded (e.g., handed over) to the connected UE 1012. Similarly, the base station 1006 need not be aware of the future routing of outgoing uplink communications originating from the UE 1012 to the host computer 1016 .
[0114] Now refer to Fig.11To describe the exemplary implementation of the UE, base station, and host computer discussed in the previous paragraphs according to the embodiment. In the communication system 1100, the host computer 1102 includes hardware 1104, which includes a communication interface 1106 configured to establish and maintain a wired or wireless connection with different communication devices in the communication system 1100. The host computer 1102 also includes a processing circuit 1108, which may have storage and / or processing capabilities. In particular, the processing circuit 1108 may include one or more programmable processors, ASICs, FPGAs, or a combination of components (not shown) that are suitable for executing instructions. The host computer 1102 also includes software 1110, which is stored in or accessible to the host computer 1102 and can be executed by the processing circuit 1108. The software 1110 includes a host application 1112. The host application 1112 may be operable to provide services to a remote user, such as a UE 1114 connected via an OTT connection 1116 terminating at the UE 1114 and the host computer 1102. In providing services to the remote user, the host application 1112 may provide user data, which is sent using the OTT connection 1116.
[0115] The communication system 1100 also includes a base station 1118, which is provided in the telecommunication system and includes hardware 1120 that enables it to communicate with the host computer 1102 and the UE 1114. The hardware 1120 may include a communication interface 1122 for establishing and maintaining a wired or wireless connection with different communication devices in the communication system 1100, and a communication interface 1122 for establishing and maintaining a connection with at least a network located in a coverage area (not in a coverage area) served by the base station 1118. Fig.11 1102). The communication interface 1122 may be configured to facilitate a connection 1128 to the host computer 1102. The connection 1128 may be direct, or it may pass through a core network (not shown in FIG. 1103 ) in the telecommunications system. Fig.11 11) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 1120 of the base station 1118 also includes processing circuitry 1130, which may include one or more programmable processors, ASICs, FPGAs, or a combination of components (not shown) suitable for executing instructions. The base station 1118 also has software 1132 stored internally or accessible via an external connection.
[0116] The communication system 1100 also includes the UE 1114 already mentioned. The hardware 1134 of the UE 1114 may include a radio interface 1136, which is configured to establish and maintain a wireless connection 1126 with a base station serving the coverage area in which the UE 1114 is currently located. The hardware 1134 of the UE 1114 also includes a processing circuit 1138, which may include one or more programmable processors, ASICs, FPGAs, or a combination of components (not shown) suitable for executing instructions. The UE 1114 also includes software 1140, which is stored in the UE 1114 or can be accessed by the UE 1114 and can be executed by the processing circuit 1138. The software 1140 includes a client application 1142. With the support of the host computer 1102, the client application 1142 can be operable to provide services to human or non-human users via the UE 1114. In the host computer 1102, the executing host application 1112 can communicate with the executing client application 1142 via the OTT connection 1116 that terminates at the UE 1114 and the host computer 1102. When providing services to users, the client application 1142 can receive request data from the host application 1112 and provide user data in response to the request data. The OTT connection 1116 can transmit both the request data and the user data. The client application 1142 can interact with the user to generate the user data it provides.
[0117] Note that Fig.11 The host computer 1102, base station 1118, and UE 1114 shown in FIG. Fig.10 The host computer 1016 in the example embodiment, one of the base stations 1006A, 1006B, 1006C, and one of the UEs 1012, 1014 may be similar or identical. That is, the internal workings of these entities may be similar to Fig.11 As shown in , and independently, the surrounding network topology can be Fig.10 Those in .
[0118] exist Fig.11 11, the OTT connection 1116 has been abstractly drawn to illustrate the communication between the host computer 1102 and the UE 1114 via the base station 1118, without explicitly mentioning any intermediate devices and the precise message routing via these devices. The network infrastructure can determine the routing, which can be configured to be hidden from the UE 1114 or the service provider operating the host computer 1102, or both. When the OTT connection 1116 is active, the network infrastructure can further make decisions by which it dynamically changes the routing (e.g., based on load balancing considerations or reconfiguration of the network).
[0119] The wireless connection 1126 between the UE 1114 and the base station 1118 is in accordance with the teachings of the embodiments described in the present disclosure. One or more of the various embodiments may improve the performance of OTT services provided to the UE 1114 using the OTT connection 1126, where the wireless connection 1126 constitutes the last leg. More precisely, the teachings of these embodiments may provide the base station 1118 with flexibility for scheduling transmissions and retransmissions, which may improve the data rate and latency of the OTT connection 1116.
[0120] A measurement process may be provided for the purpose of monitoring data rates, delays, and other factors that one or more embodiments improve. There may also be an optional network function for reconfiguring the OTT connection 1116 between the host computer 1102 and the UE 1114 in response to changes in the measurement results. The measurement process and / or network function for reconfiguring the OTT connection 1116 may be implemented in the software 1110 and hardware 1104 of the host computer 1102 or the software 1140 and hardware 1134 of the UE 1114, or both. In some embodiments, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 1116 passes; the sensor may participate in the measurement process by providing the value of the monitoring quantity exemplified above, or providing the value of other physical quantities (the software 1110, 1140 may calculate or estimate these monitoring quantities based on these other physical quantities). The reconfiguration of the OTT connection 1116 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not need to affect the base station 1118, and it may be unknown or imperceptible to the base station 1118. Such processes and functions may be known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation time, latency, etc. by the host computer 1102. These measurements may be implemented in the software 1110 and 1140 when causing messages (particularly empty messages or "dummy" messages) to be sent using the OTT connection 1116 to monitor propagation time, errors, etc.
[0121] Fig.12 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station, and a UE, which can be reference Fig.10 and Fig.11 For the sake of simplicity of this disclosure, only the entities described in Fig.12. In step 1200, the host computer provides user data. In sub-step 1202 of step 1200 (which may be optional), the host computer provides the user data by executing a host application. In step 1204, the host computer initiates a transmission that carries the user data to the UE. In step 1206 (which may be optional), in accordance with the teachings of the embodiments described in the present disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In step 1208 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.
[0122] Fig.13 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station, and a UE, which can be reference Fig.10 and Fig.11 For the sake of simplicity of this disclosure, only the entities described in Fig.13 . In step 1300 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 1302, the host computer initiates a transmission that carries the user data to the UE. According to the teachings of the embodiments described in the present disclosure, the transmission may pass through a base station. In step 1304 (which may be optional), the UE receives the user data carried in the transmission.
[0123] Fig.14 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station, and a UE, which can be reference Fig.10 and Fig.11 For the sake of simplicity of this disclosure, only the entities described in Fig.14. In step 1400 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1402, the UE provides user data. In sub-step 1404 (which may be optional) of step 1400, the UE provides user data by executing a client application. In sub-step 1406 (which may be optional) of step 1402, the UE executes a client application, which provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may further consider user input received from the user. Regardless of the specific manner of providing user data, in sub-step 1408 (which may be optional), the UE initiates transmission of user data to the host computer. In step 1410 of the method, according to the teachings of the embodiments described in the present disclosure, the host computer receives user data sent from the UE.
[0124] Fig.15 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station, and a UE, which can be reference Fig.10 and Fig.11 For the sake of simplicity of this disclosure, only the entities described in Fig.15 In step 1500 (which may be optional), according to the teachings of the embodiments described in the present disclosure, the base station receives user data from the UE. In step 1502 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 1504 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.
[0125] Any suitable steps, methods, features, functions or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include a plurality of these functional units. These functional units may be implemented via processing circuits and other digital hardware, wherein the processing circuits may include one or more microprocessors or microcontrollers, and other digital hardware may include digital signal processors (DSPs), dedicated digital logic, etc. The processing circuit may be configured to execute program codes stored in a memory, and the memory may include one or more types of memory, such as a read-only memory (ROM), a random access memory (RAM), a buffer memory, a flash memory device, an optical memory, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols, and instructions for executing one or more techniques described herein. In some implementations, according to one or more embodiments of the present disclosure, a processing circuit may be used to cause a corresponding functional unit to perform a corresponding function.
[0126] Although the processes in the accompanying figures may show a specific order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform operations in a different order, combine certain operations, overlap certain operations, etc.).
[0127] Group A Embodiment
[0128] Embodiment 1: A method for sending uplink data through multiple configured license configurations performed by a wireless device, the method comprising: receiving a first uplink license associated with a first HARQ process ID; determining whether the first HARQ process ID belongs to the first license configuration; and if the first HARQ process ID belongs to the first license configuration, setting a first configured license timer for the first license configuration.
[0129] Embodiment 2: The method according to Embodiment 1 further includes: if the first HARQ process ID does not belong to the first permitted configuration, determining whether the first HARQ process ID belongs to the second permitted configuration; and if the first HARQ process ID belongs to the second permitted configuration, setting the second configured permitted timer for the second permitted configuration.
[0130] Embodiment 3: The method according to any one of embodiments 1 to 2, wherein if the HARQ process ID includes an offset associated with the first grant configuration, the first HARQ process ID belongs to the first grant configuration.
[0131] Embodiment 4: The method according to any one of Embodiments 1 to 3, wherein the first uplink grant is received via an RRC message.
[0132] Embodiment 5: The method according to any one of Embodiments 1 to 4, wherein the first uplink grant is received via a DCI message.
[0133] Embodiment 6: A method for sending uplink data through multiple configured grant configurations performed by a wireless device, the method comprising: receiving a first uplink grant associated with a first HARQ process ID; determining whether the first HARQ process ID is less than or equal to a threshold HARQ process offset; and if the first HARQ process ID is less than or equal to the threshold HARQ process offset, setting a first configured grant timer for the first uplink grant.
[0134] Embodiment 7: The method according to embodiment 6, wherein the threshold HARQ process offset comprises a maximum HARQ process offset for a group of HARQ processes.
[0135] Embodiment 8: The method according to any one of Embodiments 6 to 7, wherein the first uplink grant is received via an RRC message.
[0136] Embodiment 9: The method according to any one of Embodiments 6 to 8, wherein the first uplink grant is received via a DCI message.
[0137] Embodiment 10: The method according to any of the preceding embodiments further comprises: providing user data; and forwarding the user data to a host computer via a transmission to a base station.
[0138] Group B Embodiment
[0139] Embodiment 11: A method for allocating uplink licenses for multiple license configurations performed by a base station, the method comprising: allocating a first uplink license for a first HARQ process associated with a first HARQ process ID; allocating a second uplink license for a second HARQ process associated with a second HARQ process ID; setting a first HARQ process ID offset for the first HARQ process; setting a second HARQ process ID offset different from the first HARQ process ID offset for the second HARQ process; setting a first configured license timer for the first license configuration; and setting a second configured license timer for the second license configuration.
[0140] Embodiment 12: The method according to embodiment 11 further includes: deactivating a third uplink grant; and in response to deactivating the third uplink grant, resetting the first HARQ process ID offset.
[0141] Embodiment 13: The method according to any one of embodiments 11 to 12, wherein allocating the first uplink grant includes sending an RRC message.
[0142] Embodiment 14: The method according to any one of embodiments 11 to 13, wherein allocating the first uplink grant includes sending a DCI message.
[0143] Embodiment 15: The method according to any one of the preceding embodiments further comprises: obtaining user data; and forwarding the user data to a host computer or a wireless device.
[0144] Group C Embodiment
[0145] Embodiment 16: A wireless device for sending uplink data through multiple configured permission configurations, the wireless device comprising: a processing circuit configured to perform any step of any one of the embodiments of Group A; and a power supply circuit configured to supply power to the wireless device.
[0146] Embodiment 17: A base station for allocating uplink licenses for multiple license configurations, the base station comprising: a processing circuit configured to perform any step of any one of the embodiments of Group B; and a power supply circuit configured to supply power to the base station.
[0147] Embodiment 18: A user equipment UE, for sending uplink data through multiple configured permitted configurations, the UE comprising: an antenna, which is configured to send and receive wireless signals; a radio front-end circuit, connected to the antenna and the processing circuit and configured to adjust the signal transmitted between the antenna and the processing circuit; a processing circuit, which is configured to perform any step described in any one of the embodiments of Group A; an input interface, connected to the processing circuit and configured to allow information to be input into the UE for processing by the processing circuit; an output interface, connected to the processing circuit and configured to output information that has been processed by the processing circuit from the UE; and a battery, connected to the processing circuit and configured to supply power to the UE.
[0148] Embodiment 19: A communication system comprising a host computer, the host computer comprising: a processing circuit configured to provide user data; a communication interface configured to forward the user data to a cellular network for transmission to a user equipment UE; wherein the cellular network comprises a base station having a radio interface and a processing circuit, the processing circuit of the base station being configured to perform any of the steps described in any one of the embodiments of Group B.
[0149] Embodiment 20: The communication system according to the previous embodiment further includes a base station.
[0150] Embodiment 21: The communication system according to the first two embodiments further includes a UE, wherein the UE is configured to communicate with a base station.
[0151] Embodiment 22: A communication system according to the first three embodiments, wherein: a processing circuit of a host computer is configured to execute a host application to provide user data; and the UE includes a processing circuit configured to execute a client application associated with the host application.
[0152] Embodiment 23: A method implemented in a communication system including a host computer, a base station and a user equipment UE, the method comprising: providing user data at the host computer; and initiating, at the host computer, a transmission carrying the user data to the UE via a cellular network including the base station, wherein the base station performs any step described in any one of the embodiments of Group B.
[0153] Embodiment 24: The method according to the previous embodiment further includes: sending user data at the base station.
[0154] Embodiment 25: The method according to the first two embodiments, wherein the user data is provided by executing a host application at a host computer, and the method further comprises: executing a client application associated with the host application at a UE.
[0155] Embodiment 26: A user equipment UE is configured to communicate with a base station, the UE comprising a radio interface and a processing circuit configured to execute the methods described in the first three embodiments.
[0156] Embodiment 27: A communication system comprising a host computer, the host computer comprising: a processing circuit configured to provide user data; a communication interface configured to forward the user data to a cellular network for transmission to a user equipment UE; wherein the UE comprises a radio interface and a processing circuit, and the components of the UE are configured to perform any step described in any one of the embodiments of Group A.
[0157] Embodiment 28: According to the communication system described in the previous embodiment, the cellular network also includes a base station configured to communicate with the UE.
[0158] Embodiment 29: A communication system according to the first two embodiments, wherein: the processing circuit of the host computer is configured to execute a host application to provide user data; and the processing circuit of the UE is configured to execute a client application associated with the host application.
[0159] Embodiment 30: A method implemented in a communication system including a host computer, a base station and a user equipment UE, the method comprising: providing user data at the host computer; and initiating, at the host computer, a transmission carrying the user data to the UE via a cellular network including a base station, wherein the UE performs any step described in any one of the embodiments of group A.
[0160] Embodiment 31: The method according to the previous embodiment further includes: at the UE, receiving user data from the base station.
[0161] Embodiment 32: A communication system comprising a host computer, the host computer comprising: a communication interface configured to receive user data originating from a transmission from a user equipment UE to a base station; wherein the UE comprises a radio interface and a processing circuit, the processing circuit of the UE being configured to perform any step described in any one of the embodiments of Group A.
[0162] Embodiment 33: The communication system according to the previous embodiment further includes a UE.
[0163] Embodiment 34: The communication system according to the first two embodiments further comprises a base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward user data carried by transmissions from the UE to the base station to a host computer.
[0164] Embodiment 35: A communication system according to the first three embodiments, wherein: the processing circuit of the host computer is configured to execute a host application; and the processing circuit of the UE is configured to execute a client application associated with the host application, thereby providing user data.
[0165] Embodiment 36: A communication system according to the first four embodiments, wherein: the processing circuit of the host computer is configured to execute a host application to provide request data; and the processing circuit of the UE is configured to execute a client application associated with the host application in response to the request data to provide user data.
[0166] Embodiment 37: A method implemented in a communication system including a host computer, a base station and a user equipment UE, the method comprising: at the host computer, receiving user data sent from the UE to the base station, wherein the UE executes any step of any one of the embodiments in Group A.
[0167] Embodiment 38: The method according to the previous embodiment further includes providing user data to the base station at the UE.
[0168] Embodiment 39: The method according to the first two embodiments further includes: executing a client application at the UE to provide user data to be sent; and executing a host application associated with the client application at the host computer.
[0169] Embodiment 40: The method according to the first three embodiments further includes: executing a client application at the UE; receiving input data for the client application at the UE, the input data being provided at the host computer by executing a host application associated with the client application; wherein the user data to be sent is provided by the client application in response to the input data.
[0170] Embodiment 41: A communication system comprising a host computer, the host computer comprising a communication interface, which is configured to receive user data originating from a transmission from a user equipment UE to a base station, wherein the base station comprises a radio interface and a processing circuit, and the processing circuit of the base station is configured to perform any step described in any one of the embodiments of Group B.
[0171] Embodiment 42: The communication system according to the previous embodiment further includes a base station.
[0172] Embodiment 43: The communication system according to the first two embodiments further includes a UE, wherein the UE is configured to communicate with a base station.
[0173] Embodiment 44: A communication system according to the first two embodiments, wherein: the processing circuit of the host computer is configured to execute a host application; and the UE is configured to execute a client application associated with the host application, thereby providing user data to be received by the host computer.
[0174] Embodiment 45: A method implemented in a communication system including a host computer, a base station and a user equipment UE, the method comprising: at the host computer, receiving from the base station user data originating from a transmission that the base station has received from the UE, wherein the UE performs any step described in any one of the embodiments of Group A.
[0175] Embodiment 46: The method according to the previous embodiment further includes: receiving user data from the UE at the base station.
[0176] Embodiment 47: The method according to the previous two embodiments further includes: at the base station, initiating transmission of the received user data to a host computer.
[0177] At least some of the following abbreviations may be used in the present disclosure. If there is an inconsistency between these abbreviations, priority should be given to how the abbreviation is used above. If listed multiple times below, the first listing should take precedence over any subsequent listing.
[0178] 3GPP Third Generation Partnership Project
[0179] 5G fifth generation
[0180] AP Access Point
[0181] ASIC Application-Specific Integrated Circuit
[0182] BSC Base Station Controller
[0183] BTS Base Transceiver Station
[0184] CD
[0185] ·COTS Commercial Off-the-Shelf
[0186] CPE
[0187] CPU Central Processing Unit
[0188] D2D Device to Device
[0189] DAS Distributed Antenna System
[0190] DSP Digital Signal Processor
[0191] DVD Digital Video Disc
[0192] eNB Enhanced or evolved Node B
[0193] E-SMLC Evolved Service Mobile Location Center
[0194] FPGA Field Programmable Gate Array
[0195] GHz Gigahertz
[0196] gNB New Radio Base Station
[0197] gNB-CU New Radio Base Station Central Unit gNB-DU New Radio Base Station Distributed Unit GSM Global System for Mobile Communications
[0198] IoT
[0199] IP Internet Protocol
[0200] ·LEE Laptop Embedded Device
[0201] LME Laptop Mounted Device
[0202] LTE Long Term Evolution
[0203] M2M Machine to Machine
[0204] MANO management and orchestration
[0205] MCE Multi-cell / multicast coordination entity
[0206] MDT Minimized Drive Test
[0207] MIMO Multiple Input Multiple Output
[0208] MME Mobility Management Entity
[0209] MSC Mobile Switching Center
[0210] MSR Multi-Standard Radio
[0211] MTC Machine Type Communication
[0212] NB-IoT Narrowband Internet of Things
[0213] NFV Network Function Virtualization
[0214] NIC Network Interface Controller
[0215] NR New Radio
[0216] NRF Network Function Repository function
[0217] O&M Operation and Maintenance
[0218] OSS Operation Support System
[0219] OTT Over the Top
[0220] PC Personal Computer
[0221] PDA Personal Digital Assistant
[0222] P-GW Packet Data Network Gateway
[0223] RAM Random Access Memory
[0224] RAN Radio Access Network
[0225] RAT Radio Access Technology
[0226] RF
[0227] RNC Radio Network Controller
[0228] ROM Read Only Memory
[0229] RRH Remote Radio Head
[0230] RRU Remote Radio Unit
[0231] SCEF service capability exposure function
[0232] ·SOC System on Chip
[0233] SON self-organizing network
[0234] UE User Equipment
[0235] USB Universal Serial Bus
[0236] V2I Vehicle to Infrastructure
[0237] V2V Vehicle to Vehicle
[0238] V2X Vehicle to Everything
[0239] VMM Virtual Machine Monitor
[0240] VNE Virtual Network Element
[0241] VNF Virtual Network Function
[0242] ·VoIP Voice over Internet Protocol
[0243] ·WCDMA Wideband Code Division Multiple Access
[0244] WiMax Worldwide Interoperability for Microwave Access
[0245] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered to be within the scope of the concepts disclosed herein.
Claims
1. A method, performed by a user equipment (UE), for a hybrid automatic repeat request (HARQ) process in a cell configurable for a plurality of configured uplink grants, the method comprising: receiving an uplink grant, wherein the uplink grant includes a HARQ process identifier ID; determining, based on the HARQ process ID offset, that a HARQ process associated with the HARQ process ID is configured for the configured uplink grant; as well as A configured grant timer for the HARQ process is started or restarted based on whether the HARQ process belongs to a configured set of HARQ processes and whether the HARQ process is configured for a configured uplink grant.
2. The method according to claim 1, wherein A HARQ process is configured for a configured uplink grant if the configured uplink grant is activated and the associated HARQ process ID belongs to the following set: HARQ-proc-Offset_i,HARQ-proc-Offset_i+1,...,HARQ-proc-Offset_i+nrofHARQ-Processes_i-1, Wherein, HARQ-proc-Offset_i represents the HARQ process offset for the permitted configuration i, and nrofHARQ-Processes_i represents the number of HARQ processes for the configured permitted configuration i.
3. The method according to claim 1, wherein A HARQ process is configured for a configured uplink grant if it is activated and the associated HARQ process ID is less than: nrofHARQ-Processes_i*+HARQ-Proc-Offset_i*, Where i* is the configuration index with the maximum value of HARQ-Proc-Offset, HARQ-Proc-Offset_i* represents the HARQ process offset for the allowed configuration i*, and nrofHARQ-Processes_i* represents the number of HARQ processes for the configured allowed configuration i*.
4. The method according to claim 1, wherein The HARQ process ID is associated with a grant configuration of the configured uplink grant.
5. The method according to claim 1, wherein Determining that the HARQ process is configured for the configured uplink grant is further based on the HARQ process ID and the number of HARQ processes per configured grant.
6. The method according to claim 5, wherein: Determining that the HARQ process is configured for the configured uplink grant includes determining that the HARQ process ID is greater than or equal to the HARQ process ID offset and less than a sum of the HARQ process ID offset and a number of HARQ processes for the configured grant.
7. The method according to any one of claims 1 to 6, wherein The HARQ process ID for the configured uplink grant is determined according to: HARQ Process ID=[floor(CURRENT_symbol / periodicity)]modulo nrofHARQ-Processes+harq-procID-offset, Wherein, CURRENT_symbol is the symbol index of the data transmission for the uplink grant, periodicity is the period of the uplink grant, nrofHARQ-Processes is the number of HARQ processes for the configured grant, and harq-procID-offset is the HARQ process ID offset.
8. The method according to claim 7, wherein: The harq-procID-offset and the nrofHARQ-Processes for the uplink grant are received through one or more radio resource control RRC messages, one or more downlink control information DCI messages, or a combination of one or more RRC messages and one or more DCI messages.
9. The method according to any one of claims 1 to 6, further comprising: Uplink data is transmitted according to the uplink grant.
10. The method according to claim 9, wherein: The uplink data includes the HARQ process ID offset.
11. The method according to any one of claims 1 to 6, wherein The uplink grant is received through a radio resource control (RRC) message.
12. The method according to any one of claims 1 to 6, wherein The uplink grant is received through a downlink control information (DCI) message.
13. The method according to any one of claims 1 to 6, further comprising: receiving another uplink grant associated with another HARQ process ID different from the HARQ process ID; as well as Based on another HARQ process ID offset, it is determined whether another HARQ process associated with the HARQ process ID is configured for another configured uplink grant.
14. The method according to claim 13, further comprising: If the another HARQ process is configured for the another configured uplink grant, starting or restarting the another configured grant timer for the another HARQ process.
15. A user equipment (UE) for configuring a hybrid automatic repeat request (HARQ) process in a cell configurable for multiple uplink grants, the UE comprising a processing circuit configured to perform the method according to any one of claims 1 to 14.
Citation Information
Patent Citations
(H)ARQ method, base station and user equipment for semi-persistent scheduling
CN104158640A
Method and apparatus for selecting uplink cell
CN105359603A
Periodic uplink grant alignment in a cellular network
CN106664714A
Method For Performing An Ack / Nack Indication Based On The Uplink Grants Over Multiple Subframes In A Wireless Communication System And A Device Therefor
CN107683620A
Base station device and terminal device
JP2019036777A
