Method and apparatus for UP enhancement

By acquiring and utilizing CG/SPS configuration information and combining carrier aggregation technology, data transmission is optimized in 5G wireless communication system, which solves the problem of insufficient user plane data transmission performance and realizes low latency, high speed and high reliability data transmission , suitable for high-demand services such as XR.

CN119095178APending Publication Date: 2024-12-06APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411416277.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2021-09-03
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

In 5G wireless communication systems, the prior art is difficult to effectively improve the low latency, high data rate, high reliability and flexible periodicity of user plane (UP) data transmission, especially for low frame error rates and frame-level integrated data traffic, especially for low frame error rates and frame-level integrated data traffic , such as extended reality (XR) traffic, insufficient transmission performance.

Method used

By obtaining configuration information, including information for determining authorization (CG)/semi-persistent scheduling (SPS) configuration, data transmission and reception are performed on multiple serving cells using carrier aggregation (CA), and based on transmission delay, success rate and Channel quality dynamically adjusts scheduling strategies to optimize data transmission timing and priorities.

Benefits of technology

It improves the efficiency and reliability of data transmission, supports low-latency and high data rate services, meets high requirements such as XR, and reduces frame error rates and delays through dynamic scheduling and optimization of transmission strategies, and improves user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119095178A_ABST
    Figure CN119095178A_ABST
Patent Text Reader

Abstract

The invention relates to a method and apparatus for UP enhancement. There is provided a method for a user equipment (UE), the method comprising: acquiring configuration information including first configuration information for determining a configured grant (CG) / semi-persistent scheduling (SPS) configuration, the first configuration information being included in a radio resource control (RRC) message; and performing data transmission / reception via the CG / SPS configuration determined by the configuration information.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the invention patent application with application date of September 3, 2021, application number 202180014500.9, and invention name “Method and device for UP enhancement”. Technical Field

[0002] The present application relates generally to wireless communication systems, and more particularly to methods and apparatus for User Plane (UP) enhancement. Background Art

[0003] Wireless mobile communication technologies use various standards and protocols to transmit data between base stations and wireless mobile devices. Wireless communication system standards and protocols may include, but are not limited to, 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE); Fifth Generation (5G) 3GPP New Radio (NR) standards; and technologies beyond 5G. In a fifth generation (5G) wireless radio access network (RAN), a base station may include a RAN node such as a 5G node, a New Radio (NR) node, or a gNode B (gNB), which communicates with a wireless communication device (also known as a user equipment (UE)).

[0004] In UP configuration, configured grant (CG) / semi-persistent scheduling (SPS) is usually applied to the scheduling of low-latency services and is designed for services with small packet sizes. In addition, a CG / SPS configuration with a fixed periodicity is configured for each cell, and CG / SPS activation / deactivation is based on the CG / SPS configuration, and each bandwidth part (BWP) corresponds to a packet size. Summary of the invention

[0005] According to aspects of the present disclosure, a method for a user equipment (UE) is provided, the method comprising: obtaining configuration information, the configuration information comprising first configuration information for determining a configured grant (CG) / semi-persistent scheduling (SPS) configuration, wherein the first configuration information is included in a radio resource control (RRC) message; and performing data transmission / reception via the CG / SPS configuration determined by the configuration information.

[0006] According to aspects of the present disclosure, a method for a user equipment (UE) is provided, the method comprising: obtaining, by an access layer (AS), packet association information from an upper layer above the AS layer, wherein the packet association information indicates packets associated together to correspond to the same frame and key packets among the packets; and performing data transmission via dedicated scheduling for the key packets.

[0007] According to an aspect of the present disclosure, there is provided an apparatus for a user equipment (UE), the apparatus comprising one or more processors configured to perform the steps of the method as described above.

[0008] According to an aspect of the present disclosure, there is provided a computer readable medium having a computer program stored thereon, which, when executed by one or more processors, causes an apparatus to perform the steps of the method as described above.

[0009] According to an aspect of the present disclosure, an apparatus for a communication device is provided, the apparatus comprising means for executing the steps of the method described above.

[0010] According to an aspect of the present disclosure, a computer program product comprises a computer program, which, when executed by one or more processors, causes an apparatus to perform the steps of the method described above. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Features and advantages of the present disclosure will be apparent from the following detailed description taken in conjunction with the accompanying drawings, which together illustrate, by way of example, features of the present disclosure.

[0012] Figure 1 is a block diagram of a system including a base station and a user equipment (UE) according to some embodiments.

[0013] Figure 2 A flowchart of an exemplary method for a UE according to some embodiments is shown.

[0014] Figure 3 A schematic diagram of an exemplary method for a UE according to some embodiments is shown.

[0015] FIG. 4A to FIG. 4B A schematic diagram of an exemplary method for a UE according to some embodiments is shown.

[0016] Figure 5 A schematic diagram of an exemplary method for a UE according to some embodiments is shown.

[0017] Figure 6 A schematic diagram of an exemplary method for a UE according to some embodiments is shown.

[0018] Figure 7 A flowchart of an exemplary method for a UE according to some embodiments is shown.

[0019] Figure 8 A flowchart of an exemplary method for a UE according to some embodiments is shown.

[0020] Fig. 9 A schematic diagram of an exemplary method for a UE according to some embodiments is shown.

[0021] Fig.10 A schematic diagram of an exemplary method for a UE according to some embodiments is shown.

[0022] FIG. 11A to FIG. 11C A schematic diagram of an exemplary method for a UE according to some embodiments is shown.

[0023] Fig.12 A flowchart of an exemplary method for a UE according to some embodiments is shown.

[0024] Fig.13 A communication device (eg, UE or base station) according to some embodiments is shown.

[0025] Fig.14 An exemplary interface of a baseband circuit according to some embodiments is shown.

[0026] Fig.15 Components according to some embodiments are shown.

[0027] Fig.16 The architecture of a wireless network according to some embodiments is shown. DETAILED DESCRIPTION

[0028] In the present disclosure, a "base station" may include a RAN node such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as an evolved Node B, an enhanced Node B, an eNodeB, or an eNB) and / or a Radio Network Controller (RNC) and / or a 5G node, a New Radio (NR) node, or a gNodeB (gNB), which communicates with a wireless communication device also referred to as a user equipment (UE). Although some examples may be described with reference to any of an E-UTRAN Node B, an eNB, an RNC, and / or a gNB, such a device may be replaced with any type of base station.

[0029] In the related field, data traffic that requires low latency, high data rate, high reliability, flexible periodicity, low frame error rate, and frame-level integration has attracted widespread attention. An example of such data traffic may be extended reality (XR) traffic. An efficient data transmission / reception mechanism is needed to improve the performance of such data traffic.

[0030] To achieve this goal, the present disclosure provides a method and apparatus for user plane (UP) enhancement. Various aspects of the present disclosure will be described below in conjunction with the accompanying drawings.

[0031] Figure 1 is a block diagram of a system including a base station and a user equipment (UE) according to some embodiments. Figure 1 A wireless network 100 is shown according to some embodiments. The wireless network 100 includes a UE 101 and a base station 150 connected via an air interface 190.

[0032] UE 101 and any other UE in the system may be, for example, a laptop computer, a smart phone, a tablet computer, a printer, a machine type device, such as a smart meter or a dedicated device for healthcare monitoring, remote safety monitoring, an intelligent transportation system, or any other wireless device with or without a user interface. Base station 150 provides network connectivity to a wider network (not shown) to UE 101 via an air interface 190 in a base station service area provided by base station 150. In some embodiments, such a wider network may be a wide area network operated by a cellular network provider, or may be the Internet. Each base station service area associated with base station 150 is supported by an antenna integrated with base station 150. The service area is divided into a plurality of sectors associated with certain antennas. Such sectors may be physically associated with fixed antennas, or may be assigned to a physical area with a tunable antenna or antenna setting, which may be adjusted in a beamforming process for directing signals to a particular sector. For example, one embodiment of the base station 150 includes three sectors, each sector covering a 120 degree area, with antenna arrays pointed toward each sector to provide 360 ​​degree coverage around the base station 150 .

[0033] UE 101 includes a control circuit 105 coupled to a transmission circuit 110 and a receiving circuit 115. The transmission circuit 110 and the receiving circuit 115 may each be coupled to one or more antennas. The control circuit 105 may be adapted to perform operations associated with MTC. In some embodiments, the control circuit 105 of UE 101 may perform calculations or may initiate measurements associated with the air interface 190 to determine the channel quality of the available connection to the base station 150. These calculations may be performed in conjunction with the control circuit 155 of the base station 150. The transmission circuit 110 and the receiving circuit 115 may be adapted to transmit and receive data, respectively. The control circuit 105 may be adapted or configured to perform various operations, such as various operations related to the UE described elsewhere in this disclosure. The transmission circuit 110 may transmit multiple multiplexed uplink physical channels. The multiple uplink physical channels may be multiplexed according to time division multiplexing (TDM) or frequency division multiplexing (FDM). The transmission circuit 110 may be configured to receive block data from the control circuit 105 for transmission across the air interface 190. Similarly, the receiving circuit 115 can receive multiple multiplexed downlink physical channels from the air interface 190 and relay these physical channels to the control circuit 105. The uplink and downlink physical channels can be multiplexed according to TDM or FDM. The transmitting circuit 110 and the receiving circuit 115 can transmit and receive control data and content data (e.g., messages, images, videos, etc.) structured within data blocks carried by the physical channels.

[0034] Figure 1Also shown is a base station 150 according to various embodiments. The base station 150 circuitry may include a control circuit 155 coupled to a transmission circuit 160 and a reception circuit 165. The transmission circuit 160 and the reception circuit 165 may each be coupled to one or more antennas that may be used to enable communication via an air interface 190.

[0035] The control circuit 155 may be adapted to perform operations associated with MTC. The transmission circuit 160 and the reception circuit 165 may be adapted to transmit and receive data, respectively, within a narrow system bandwidth that is narrower than a standard bandwidth for personal communications. In some embodiments, for example, the transmission bandwidth may be set to or close to 1.4 MHz. In other embodiments, other bandwidths may be used. The control circuit 155 may perform various operations, such as base station-related operations described elsewhere in this disclosure.

[0036] Within the narrow system bandwidth, the transmission circuit 160 can transmit multiple multiplexed downlink physical channels. The multiple downlink physical channels can be multiplexed according to TDM or FDM. The transmission circuit 160 can transmit the multiple multiplexed downlink physical channels in a downlink superframe composed of multiple downlink subframes.

[0037] In a narrow system bandwidth, the receiving circuit 165 can receive multiple multiplexed uplink physical channels. The multiple uplink physical channels can be multiplexed according to TDM or FDM. The receiving circuit 165 can receive the multiple multiplexed uplink physical channels in an uplink superframe composed of multiple uplink subframes.

[0038] As further described below, control circuits 105 and 155 may be involved in measuring channel quality of air interface 190. Channel quality may be based, for example, on physical obstacles between UE 101 and base station 150, electromagnetic signal interference from other sources, reflections, or indirect paths between UE 101 and base station 150, or other such signal noise sources. Based on the channel quality, multiple retransmissions of a data block may be scheduled so that transmission circuit 110 may transmit copies of the same data multiple times, and reception circuit 115 may receive multiple copies of the same data multiple times.

[0039] Figure 2 A flowchart of an exemplary method for a UE according to some embodiments is shown.

[0040] like Figure 2As shown, the method for UE may include the following steps: S202, obtaining configuration information, the configuration information including first configuration information for determining a configured grant (CG) / semi-persistent scheduling (SPS) configuration; and S204, performing data transmission / reception via the CG / SPS configuration determined by the configuration information. The first configuration information may be included in a radio resource control (RRC) message. For example, the network (NW) side may configure and activate the CG / SPS via RRC signaling.

[0041] In some embodiments, the configuration information may also include second configuration information for determining the CG / SPS configuration. The second configuration information may be included in downlink control information (DCI).

[0042] In some embodiments, at the first time, the second configuration information may be provided via an RRC message together with the first configuration information. For example, the second configuration may be provided via an RRC message together with the first configuration from the gNB.

[0043] In some embodiments, the UE may be Figure 1 The UE 101 described in the embodiment of the present invention may obtain configuration information from the network side (eg, from a primary serving cell, ie, PCell), where the configuration information includes first configuration information and second configuration information.

[0044] Data transmission / reception via CG / SPS configuration can be performed at a given time, which means that the UE can deliver uplink (UL) transmission or monitor to receive downlink (DL) via CG configuration and SPS configuration, respectively, at that time.

[0045] In some embodiments, one CG / SPS configuration may be applied to multiple serving cells, such as a PCell and at least one secondary serving cell, i.e., an SCell. Data transmission / reception may be performed on multiple serving cells via carrier aggregation (CA). The active serving cell for the CG / SPS configuration may be indicated from the network side (e.g., a PCell). Figure 3 and FIG. 4A to FIG. 4B Describe in more detail.

[0046] In some embodiments, CG / SPS configuration may be performed in a repetitive manner, where a set of occasions is configured on a specific serving cell indicated in the configuration information. Figure 5 Describe in more detail.

[0047] In some embodiments, a timing window including multiple optional timings may be indicated by configuration information. Data transmission / reception may be performed at a timing within the timing window. Figure 6 Describe in more detail.

[0048] In some embodiments, when triggering factors (such as transmission delay, transmission success rate, and radio quality satisfying preset conditions) are met, the UE may initiate acquisition of configuration information (e.g., Figure 2 S202 in ), so the subsequent data transmission / reception can be performed as described above. Figure 7 Describe in more detail.

[0049] In the following, for the purpose of illustration, the embodiment in which the second configuration information is also provided and included in the DCI will be described. Figures 3 to 6 .

[0050] Figure 3 A schematic diagram of an exemplary method for a UE according to some embodiments is shown.

[0051] like Figure 3 As shown, the UE may obtain first configuration information 301, which indicates a parameter of a CG / SPS configuration index having a predetermined value. The UE may also obtain second configuration information 302, which indicates the timing of the CG / SPS configuration and the multiple serving cells on which the CG / SPS configuration is applied. In addition, the UE may perform data transmission / reception on the multiple serving cells via CA at the timing of the CG / SPS configuration. For illustration purposes, Figure 3 Three data transmissions 303-1 to 303-3 are shown. However, fewer or more data transmissions are possible based on actual applications. In addition, the situation of data reception is similar to that of data transmission.

[0052] The first configuration information via the RRC message may be represented by CGConfigurationIndex=1, which indicates the CG configuration. Similarly, the first configuration information via the RRC message may include SPSConfigurationIndex=1, which indicates the SPS configuration.

[0053] In addition, the second configuration information via the DCI may include a layer 1 (L1) CG activation command, such as CG#1activation. The CG authorization may be applied as a CG opportunity based on the L1 CG activation command. The second configuration information may include a parameter indicating the serving cell to which the CG authorization is applied. For example, the parameter Activated Cell=PCell,SCell#1 indicates that the same CG authorization is applied on PCell and SCell#1. Figure 3 SCell #1 is shown for illustration purposes, but more SCells may be possible based on actual implementation.

[0054] Using such first configuration information and second configuration information, the UE can start data transmission via CA on PCell and SCell#1.

[0055] Similarly, the second configuration information via DCI may include an L1 SPS activation command. The SPS grant may be applied as an SPS opportunity based on the L1 SPS activation command. The second configuration information may include a parameter indicating the serving cell to which the SPS grant is applied. For example, the parameter Activated Cell=PCell,SCell#1 indicates that the same SPS grant is applied on PCell and SCell#1.

[0056] Using such first configuration information and second configuration information, the UE can start data reception via CA on PCell and SCell#1.

[0057] like Figure 3 As shown, there may be multiple opportunities for performing data transmission / reception on multiple serving cells via CA, for example, 303-1 to 303-3. Figure 3 shown.

[0058] According to the present disclosure, data transmission / reception is performed simultaneously via CA using multiple serving cells. Therefore, the total data transmission / reception rate can be increased by using more serving cells involved, which can support transmission with high data rates for scheduling low-latency services.

[0059] FIG. 4A to FIG. 4B A schematic diagram of an exemplary method for a UE according to some embodiments is shown.

[0060] like Figure 4A As shown, the UE may obtain first configuration information 401, which indicates CGConfigurationIndex = 1. The UE may also obtain second configuration information 402, which indicates CG#1activation and Activated Cell = PCell, SCell#1. In addition, the UE may perform CG data transmission 403-1 to 403-3 based on the first configuration information and the second configuration information.

[0061] In some embodiments, the UE may determine whether any of the plurality of serving cells is sufficient for data transmission based on the amount of data. For example, if both serving cells PCell and SCell#1 are insufficient for data transmission, the UE may perform CG data transmissions 403-1 and 403-3 on both PCell and SCell#1. Alternatively, if the UE determines that the amount of data in the second data transmission 403-2 is small, such that one of the active serving cells is sufficient for data transmission, the UE may perform CG data transmissions 403-1 and 403-3 on the one serving cell (e.g., Figure 4A Data is transmitted on the PCell in the network.

[0062] The serving cell selection scheme may be configured by the network side (eg, PCell) or based on UE specific implementation.

[0063] According to the present disclosure, the serving cell selection scheme can avoid unnecessary transmission and potential resource waste on other serving cells via CA.

[0064] like Figure 4B As shown, the UE may obtain first configuration information 411, which indicates SPSConfigurationIndex=1. The UE may also obtain second configuration information 412, which indicates SPS#1activation and Activated Cell=PCell, SCell#1. In addition, based on the configuration information, the timing for data reception may be determined. The UE may perform SPS data reception 413-1 to 413-3 based on the first configuration information and the second configuration information.

[0065] In some embodiments, in response to detecting a second data transmission on SCell#1 (ie, Figure 4B 413-2), the UE may consider that the corresponding secondary serving cell (i.e., SCell#1) does not transmit data at this time, and skips data reception on SCell#1, and performs data reception only on the selected active cell (e.g., PCell as shown in FIG4 ). The selection of the serving cell for data reception may be based on the UE's capabilities or UE specific implementation. Therefore, in addition to the primary cell, any active cell may be selected.

[0066] Figure 5 A schematic diagram of an exemplary method for a UE according to some embodiments is shown.

[0067] like Figure 5As shown, the UE may obtain first configuration information 501, which indicates CGConfigurationIndex = 1. The UE may also obtain second configuration information 502, which indicates CG#1activation and Duplicate Tx = PCell, SCell#1. In addition, the UE may perform, for example, CG authorized repeated transmission 503-1 to 503-3 on PCell and SCell#1 via a set of opportunities.

[0068] In some embodiments, the group of opportunities on different serving cells may be determined by the network side (e.g., Figure 5 In response to activation by the network side, the group of opportunities is used for repeated transmission on multiple serving cells, each serving cell corresponding to one opportunity. Therefore, data transmission / reception can be performed on the primary cell (for example, Figure 5 PCell shown in FIG. 1 and a secondary cell among the multiple serving cells (eg, Figure 5 Executed simultaneously on SCell#1) as shown.

[0069] Similarly, the SPS configuration may be indicated in the first configuration information.The second configuration information may provide an L1 activation command and correspondingly indicate a serving cell for SPS data reception.

[0070] In addition, in the primary serving cell (e.g. Figure 5 PCell shown in FIG. 1 ) and a secondary serving cell (eg, Figure 5 In the case where the same CG grant is applied to both SCell#1 and SCell#2, a predetermined parameter may be used to indicate the transmission method. For example, PCell may be determined for the first transmission with RV index = 0, and SCell#1 may be determined for the retransmission with RV index = 2.

[0071] The retransmission (or repeated transmission) may be a complete copy of the first transmission (or new transmission), ie the retransmission sends exactly the same data as the first transmission.

[0072] According to the present disclosure, repeated transmission of data performed via a plurality of serving cells can ensure high reliability in transmission.

[0073] Figure 6 A schematic diagram of an exemplary method for a UE according to some embodiments is shown.

[0074] like Figure 6As shown, the UE may obtain first configuration information 601, which indicates CGConfigurationIndex=1, CG Window=4 and CG periodicity=20ms. The UE may also obtain second configuration information 602, which indicates CG#1activation. In addition, the UE may obtain the first configuration information 601, which indicates CGConfigurationIndex=1, CG Window=4 and CG periodicity=20ms. The UE may also obtain second configuration information 602, which indicates CG#1activation. Figure 6 CG authorization transmission is performed on the PCell using one of 603-3 or 604-1). Figure 6 The other dashed arrow lines shown (i.e., 603-1, 603-2, 603-4, 604-2, 604-3, and 604-4) refer to other selectable opportunities within opportunity windows 611 and 612. Although the four selectable opportunities within the opportunity window and the two opportunity windows with a periodicity of 20 ms are Figure 6 However, they are not limited to the above examples based on actual specific implementations.

[0075] The timing window for each period of transmission can be applied not only in the CG configuration but also in the SPS configuration. For example, in the CG configuration, the UE can process the UL transmission at a selected timing within the timing window. For another example, in the SPS configuration, the UE can keep monitoring until the physical downlink shared channel (PDSCH) reception starts at a selected timing within the timing window.

[0076] In some embodiments, the first configuration information may include a second parameter (ie, CG window=4) indicating a timing window having a predetermined number of selectable timings. Figure 6 As shown, the opportunity windows 611 and 612 may have selectable opportunities 603-1 to 603-4 and 604-1 to 604-4, respectively. As described above, the number of selectable opportunities is not limited to four, which is merely an example of a specific implementation.

[0077] Since the CG grant is applied as a CG opportunity, the UE may be allowed to transmit once per window. The timing for transmission within the opportunity window may be selected based on UE specific implementation or data status (e.g., when the data arrives for transmission).

[0078] In some embodiments, the first configuration information may also include a third parameter indicating the opportunity window of each cycle (e.g., Figure 6 As shown in , CG periodicity = 20ms). Therefore, the timing window and position within each period can be determined. It should be noted that the period is from the perspective of the timing window. This means that the selected timings in different timing windows can be independent of each other. For example, Figure 6As shown, the selection of timing in timing window 611 may not affect the selection of timing in timing window 612 .

[0079] According to the present disclosure, flexible timing for data transmission / reception can be obtained by applying opportunity windows. Figure 6 As shown, if the data is not ready for transmission at the first opportunity 603-1 within the first opportunity window 611, there may still be remaining opportunities to be used within the first opportunity window. In the absence of this opportunity window, the data must wait until the next opportunity (e.g., Figure 6 The timing 604-1) is shown for transmission, which increases the delay of data transmission.

[0080] Figure 7 A flowchart of an exemplary method for a UE according to some embodiments is shown.

[0081] like Figure 7 As shown, the method for UE may include the following steps: S702, determining whether at least one factor selected from the group of transmission delay, transmission success rate and radio quality satisfies a preset condition; S704, in response to determining that the selected factor satisfies the preset condition, providing preference information for the configuration of the configuration information to be acquired; S706, acquiring configuration information for determining the configured grant (CG) / semi-persistent scheduling (SPS) configuration; and S708, performing data transmission / reception via the CG / SPS configuration determined by the configuration information.

[0082] For example, when the radio quality is lower than a predetermined threshold, repeated transmission may be triggered, and thus a message with a repeated transmission indication (such as Figure 5 Alternatively or in addition, transmission via CA may be triggered to reduce the modulation and coding scheme (MCS) used for the transmission in each cell, so that a CA indication (such as Figure 4A and Figure 4B The configuration information of Activated Cell = PCell, SCell#1) is shown. Radio quality can also be considered by the network side in the cell selection scheme to select the activated cell for transmission.

[0083] In addition, when the transmission delay is greater than a predetermined threshold, the above transmission, repeated transmission and opportunity window via CA can be triggered by obtaining configuration information with corresponding indication from the network side.

[0084] In addition, when the transmission success rate is lower than a predetermined threshold, transmission or repeated transmission via CA can be triggered, so configuration information with corresponding indications from the network side can be obtained. The transmission success rate can also be considered by the network side in the cell selection scheme to select an activated cell for transmission.

[0085] The evaluation of triggering factors (such as transmission delay, transmission success rate and radio quality) is performed on the network side based on network specific implementation. After the evaluation, the network side can configure configuration information including corresponding indications and send it to the UE.

[0086] Alternatively, an evaluation of triggering factors (such as transmission delay, transmission success rate, and radio quality) may be performed at the UE. After the evaluation, the UE may transmit preferences or recommendations generated based on the evaluation via L1 / L2 / L3 signaling to the network side. The network side may configure configuration information including corresponding indications and send it to the UE.

[0087] Figure 8 A flowchart of an exemplary method for a UE according to some embodiments is shown.

[0088] like Figure 8 As shown, the method for UE may include the following steps: S802, obtaining, by an access layer (AS), packet association information from an upper layer above the AS layer; and S804, performing data transmission via dedicated scheduling for the key packet. The packet association information indicates packets that are associated together to correspond to the same frame and key packets among the packets.

[0089] At least one remaining packet corresponding to the same frame with the critical packet can depend on the critical packet. In this case, if the transmission / reception of the critical packet is unsuccessful, the remaining packets are no longer useful.

[0090] According to the present disclosure, frame-level integrated transmission can be implemented so that the quality of service (QoS) mechanism can take into account frame-level parameters, such as frame error rate, frame delay budget, etc. Frame-level integrated transmission for identifying which packets belong to a video frame is also beneficial to meet XR service requirements.

[0091] Fig. 9 A schematic diagram of an exemplary method for a UE according to some embodiments is shown.

[0092] The packet association information may indicate packets that are associated together to correspond to the same frame by marking the packets corresponding to the same frame with the same tag.

[0093] like Fig. 9As shown, packets PACKET#1 to PACKET#4 may have the same tag F#1, which indicates that packets PACKET#1 to PACKET#4 are associated together to frame FRAME#1. In addition, packets PACKET#5 to PACKET#7 may have the same tag F#2, which indicates that packets PACKET#5 to PACKET#7 are associated together to frame FRAME#2.

[0094] The packet association information can also indicate a key packet in the packets by marking a key tag on the key packet. Therefore, the tag C can be marked on, for example, PACKET#1 and PACKET#5, which are key packets in frames FRAME#1 and FRAME#2, respectively.

[0095] Tags can be marked by upper layers for packets and delivered to the AS layer. The AS layer can identify packet association information via these tags and perform data transmission accordingly.

[0096] Fig.10 A schematic diagram of an exemplary method for a UE according to some embodiments is shown. Fig.10 As shown, a scheduling scheme for transmitting high-reliability packets (ie, critical packets) is executed using packet association information 1001 acquired from an upper layer.

[0097] In some embodiments, the UE may provide a dedicated scheduling request (SR) 1002 to the network side (NW) to request dedicated scheduling for the critical packet. The UE may also provide the NW with the data volume of the critical packet in a buffer status report (BSR) of a medium access control (MAC) control element (CE) 1003. In addition, the UE may obtain a configured grant (CG) configuration 1004 from the NW, which indicates a higher priority of the critical packet than the remaining packets in the group. Reference will be made to FIG. 11A to FIG. 11C Describe in more detail.

[0098] FIG. 11A to FIG. 11C A schematic diagram of an exemplary method for a UE according to some embodiments is shown.

[0099] like Fig.11A As shown, packets PACKET#1, PACKET#2, PACKET#3, and PACKET#4 may correspond to frame FRAME#1. When a critical packet arrives, the UE may Fig.11A PACKET#1 shown) provides special SR (e.g., Fig.11AThe C-SR shown in the figure requests reliable scheduling from the NW. In addition, the UE can provide normal SR for the remaining packets PACKET#2, PACKET#3 and PACKET#4. The NW can configure special resources for critical packets and associate them with one or more special logical channels (LCHs). Fig.11A Four groupings are shown in FIG, but fewer or more groupings are possible based on the actual implementation.

[0100] like Fig. 11B As shown, the UE may provide the data amount of the critical packet in the BSR of the MAC CE. A special logical channel group (LCG) (e.g., LCG 1 corresponding to buffer size BUFFER SIZE 1) may be configured by the NW for critical packet transmission based on the buffer information in various LCGs. Then, the UE may first perform the transmission of the critical packet using the special LCG configured by the NW.

[0101] like Fig. 11C As shown, the UE can obtain DCI indicating that the critical packet has a higher priority than the remaining packets in the packet. The DCI can be provided from the NW. Upon receiving the DCI, the corresponding grant is used only for the critical packet (i.e., packet PACKET#1 in FRAME#1) as the priority indicated in the DCI. Therefore, only Fig. 11C Packet PACKET #1 is shown being transmitted by the grant (as shown by the dashed line).

[0102] In other words, NW can configure high L1 priority or critical specific priority for critical packet transmission. UE can first check the LCH associated with the CG / DG. If critical priority is set for the LCH, only the authorization configured by the CG / DG can be allowed to directly deliver the critical packets of those LCHs.

[0103] According to the present disclosure, special resources configured for key packets with higher reliability and priority as well as frame-level performance can also be improved accordingly.

[0104] Fig.12 A flowchart of an exemplary method for a UE according to some embodiments is shown.

[0105] like Fig.12 As shown, the method for UE may include the following steps: S1202, the access layer (AS) obtains packet association information from the upper layer above the AS layer; S1204, performs data transmission via dedicated scheduling for the key packet; and S1206, executes an abandonment scheme.

[0106] In some embodiments, executing the abandonment scheme can determine whether the data transmission for the critical packet is successfully performed. As described above, if the transmission of the critical packet is unsuccessful, at least one remaining packet corresponding to the same frame may no longer be useful. Therefore, in response to determining that the data transmission for the critical packet is not successfully performed, the data transmission for the remaining packets that have not yet been transmitted may become unnecessary and can be discarded.

[0107] In some embodiments, in acknowledgement mode (AM mode), directly discarding packets may result in sequence number (SN) mismatch or other automatic repeat request (ARQ) errors. Therefore, if the remaining packets have been assigned SNs or are being transmitted, the UE may continue to perform data transmission by only indicating the remaining packets in the radio link control (RLC) header without any payload for transmission. The transmission of the packets indicated in the RLC header may keep ARQ running correctly.

[0108] In some embodiments, with respect to data reception (ie, in the DL direction), the UE may receive packets that are associated together to correspond to the same frame. In this case, the associated information may be carried in the packets and obtained by the UE.

[0109] In addition, the UE may determine whether a key packet in the packet is successfully received. In response to determining that the key packet is not successfully received, the UE may abandon the remaining packets at the AS layer without transmitting them to an upper layer.

[0110] In some embodiments, the UE may also provide RLC acknowledgment (ACK) for the remaining packets as feedback of reception while discarding the remaining packets. This feedback may keep ARQ running correctly for AM mode.

[0111] According to the present disclosure, the packet abandonment scheme performed by the UE can reduce unnecessary data transmission / reception after determining that a key packet has not been successfully transmitted / received. In addition, the abandonment scheme can also keep the ACK or error detection mechanism running correctly.

[0112] Fig.13Exemplary components of a device 1300 according to some embodiments are shown. In some embodiments, the device 1300 may include at least an application circuit 1302, a baseband circuit 1304, a radio frequency (RF) circuit (shown as RF circuit 1320), a front-end module (FEM) circuit (shown as FEM 1330), one or more antennas 1332, and a power management circuit (shown as PMC 1334) coupled together as shown. The components of the illustrated device 1300 may be included in a UE or a RAN node. In some embodiments, the device 1300 may include fewer elements (e.g., the RAN node may not utilize the application circuit 1302, but include a processor / controller to process IP data received from the EPC). In some embodiments, the device 1300 may include additional elements, such as, for example, a memory / storage device, a display, a camera, a sensor, or an input / output (I / O) interface. In other embodiments, the components described below may be included in more than one device (e.g., the circuit may be separately included in more than one device for a specific implementation of a cloud-RAN (C-RAN)).

[0113] The application circuit 1302 may include one or more application processors. For example, the application circuit 1302 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The processors may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). These processors may be coupled to or may include memory / storage devices, and may be configured to execute instructions stored in the memory / storage devices to enable various applications or operating systems to run on the device 1300. In some embodiments, the processor of the application circuit 1302 may process IP data packets received from the EPC.

[0114] The baseband circuit 1304 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 1304 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of the RF circuit 1320 and generate baseband signals for the transmit signal path of the RF circuit 1320. The baseband circuit 1304 may interact with the application circuit 1302 to generate and process baseband signals and control the operation of the RF circuit 1320. For example, in some embodiments, the baseband circuit 1304 may include a third generation (3G) baseband processor (3G baseband processor 1306), a fourth generation (4G) baseband processor (4G baseband processor 1308), a fifth generation (5G) baseband processor (5G baseband processor 1310), or other baseband processors 1312 of other existing generations, generations under development, or generations to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuit 1304 (e.g., one or more of the baseband processors) may handle various radio control functions that can communicate with one or more radio networks via the RF circuit 1320. In other embodiments, some or all of the functions of the illustrated baseband processor may be included in a module stored in the memory 1318 and executed via the central processing unit (CPET 1314). The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuit of the baseband circuit 1304 may include a fast Fourier transform (FFT), precoding, or constellation mapping / demapping function. In some embodiments, the encoding / decoding circuit of the baseband circuit 1304 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples, and may include other suitable functions in other embodiments.

[0115] In some embodiments, the baseband circuit 1304 may include a digital signal processor (DSP), such as one or more audio DSPs 1316. The one or more audio DSPs 1316 may include elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments. In some embodiments, the components of the baseband circuit may be appropriately combined in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all of the components of the baseband circuit 1304 and the application circuit 1302 may be implemented together, such as on a system on a chip (SOC).

[0116] In some embodiments, the baseband circuit 1304 may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit 1304 may support communications with an Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other wireless metropolitan area network (WMAN), wireless local area network (WLAN), wireless personal area network (WPAN). Embodiments in which the baseband circuit 1304 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuits.

[0117] RF circuit 1320 may enable communication with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various embodiments, RF circuit 1320 may include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. RF circuit 1320 may include a receive signal path, which may include circuits for down-converting an RF signal received from FEM circuit 1330 and providing a baseband signal to baseband circuit 1304. RF circuit 1320 may also include a transmit signal path, which may include circuits for up-converting a baseband signal provided by baseband circuit 1304 and providing an RF output signal for transmission to FEM circuit 1330. In some embodiments, the receive signal path of RF circuit 1320 may include mixer circuit 1322, amplifier circuit 1324, and filter circuit 1326. In some embodiments, the transmit signal path of RF circuit 1320 may include filter circuit 1326 and mixer circuit 1322. RF circuit 1320 may also include synthesizer circuit 1328 for synthesizing frequencies used by mixer circuit 1322 for receiving signal path and transmitting signal path. In some embodiments, mixer circuit 1322 of receiving signal path may be configured to down-convert RF signal received from FEM circuit 1330 based on synthesized frequency provided by synthesizer circuit 1328. Amplifier circuit 1324 may be configured to amplify down-converted signal, and filter circuit 1326 may be a low pass filter (LPF) or a band pass filter (BPF) configured to remove unwanted signals from down-converted signal to generate output baseband signal. Output baseband signal may be provided to baseband circuit 1304 for further processing. In some embodiments, although this is not required, output baseband signal may be zero frequency baseband signal. In some embodiments, mixer circuit 1322 of receiving signal path may include passive mixer, but the scope of the embodiment is not limited in this respect.

[0118] In some embodiments, mixer circuit 1322 of the transmit signal path may be configured to up-convert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 1328 to generate an RF output signal for FEM circuit 1330. The baseband signal may be provided by baseband circuit 1304 and may be filtered by filter circuit 1326.

[0119] In some embodiments, the mixer circuit 1322 of the receive signal path and the mixer circuit 1322 of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and up-conversion, respectively. In some embodiments, the mixer circuit 1322 of the receive signal path and the mixer circuit 1322 of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuit 1322 of the receive signal path and the mixer circuit 1322 may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 1322 of the receive signal path and the mixer circuit 1322 of the transmit signal path may be configured for superheterodyne operation.

[0120] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, RF circuit 1320 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits, and baseband circuit 1304 may include a digital baseband interface to communicate with RF circuit 1320.

[0121] In some dual-mode embodiments, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0122] In some embodiments, synthesizer circuit 1328 may be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, but the scope of the embodiments is not limited in this regard, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 1328 may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0123] The synthesizer circuit 1328 may be configured to synthesize an output frequency based on the frequency input and the divider control input for use by the mixer circuit 1322 of the RF circuit 1320. In some embodiments, the synthesizer circuit 1328 may be a fractional-N / N+1 synthesizer.

[0124] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not required. The divider control input may be provided by baseband circuitry 1304 or application circuitry 1302 (such as an application processor) according to the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by application circuitry 1302.

[0125] The synthesizer circuit 1328 of the RF circuit 1320 may include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable, delay element, a phase detector, a charge pump, and a D-type flip-flop set. In these embodiments, the delay element may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0126] In some embodiments, the synthesizer circuit 1328 can be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used with a quadrature generator and divider circuit to generate multiple signals with multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency can be the LO frequency (fLO). In some embodiments, the RF circuit 1320 can include an IQ / polarity converter.

[0127] FEM circuitry 1330 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 1332, amplify the received signals, and provide an amplified version of the received signals to RF circuitry 1320 for further processing. FEM circuitry 1330 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by RF circuitry 1320 for transmission by one or more of one or more antennas 1332. In various embodiments, amplification by either the transmit or receive signal path may be accomplished in only RF circuitry 1320, only FEM circuitry 1330, or in both RF circuitry 1320 and FEM circuitry 1330.

[0128] In some embodiments, the FEM circuit 1330 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit 1330 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit 1330 may include an LNA to amplify a received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuit 1320). The transmit signal path of the FEM circuit 1330 may include a power amplifier (PA) to amplify an input RF signal (e.g., provided by the RF circuit 1320), and one or more filters to generate an RF signal for subsequent transmission (e.g., through one or more of the one or more antennas 1332).

[0129] In some embodiments, PMC 1334 can manage the power provided to baseband circuit 1304. Specifically, PMC 1334 can control power selection, voltage scaling, battery charging, or DC-DC conversion. When device 1300 is capable of being powered by a battery, for example, when device 1300 is included in an EGE, PMC 1334 can generally be included. PMC 1334 can improve power conversion efficiency while providing the desired specific implementation size and heat dissipation characteristics.

[0130] Fig.13 PMC 1334 is shown coupled only to baseband circuitry 1304. However, in other embodiments, PMC 1334 may additionally or alternatively be coupled to other components (such as, but not limited to, application circuitry 1302, RF circuitry 1320, or FEM circuitry 1330) and perform similar power management operations for these components.

[0131] In some embodiments, the PMC 1334 may control or otherwise be part of various power saving mechanisms of the device 1300. For example, if the device 1300 is in an RRC connected state, in which the device is still connected to a RAN node because the device expects to receive communications soon, the device may enter a state called discontinuous reception mode (DRX) after a period of inactivity. During this state, the device 1300 may be powered off for short time intervals, thereby saving power.

[0132] If there is no data traffic activity for an extended period of time, the device 1300 may transition to an RRC idle state, in which the device is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The device 1300 enters a very low power state and performs paging, in which the device periodically wakes up again to listen to the network and then powers down again. The device 1300 cannot receive data in this state, and in order to receive data, the device must transition back to an RRC connected state.

[0133] An additional power saving mode can keep a device from using the network for longer than the paging interval (which can range from a few seconds to several hours). During this time, the device is completely unable to connect to the network and can be completely powered down. Any data sent during this time will be significantly delayed, and it is assumed that the delay is acceptable.

[0134] The processor of the application circuit 1302 and the processor of the baseband circuit 1304 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 1304 can be used alone or in combination to perform layer 3, layer 2, or layer 1 functions, while the processor of the application circuit 1302 can utilize data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., transport communication protocol (TCP) and user datagram protocol (UDP) layers). As mentioned herein, layer 3 may include a radio resource control (RRC) layer, which will be described in further detail below. As mentioned herein, layer 2 may include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, layer 1 may include a physical (PHY) layer of a UE / RAN node, which will be described in further detail below.

[0135] Fig.14 An exemplary interface 1400 of a baseband circuit according to some embodiments is shown. As discussed above, Fig.13 The baseband circuit 1304 may include a 3G baseband processor 1306, a 4G baseband processor 1308, a 5G baseband processor 1310, other baseband processors 1312, a CPU 1314, and a memory 1318 used by the processors. As shown, each processor may include a memory interface 1402 for sending / receiving data to / from the memory 1318.

[0136] The baseband circuit 1304 may also include one or more interfaces to communicatively couple to other circuits / devices, such as a memory interface 1404 (e.g., an interface for sending data to or receiving data from a memory external to the baseband circuit 1304), an application circuit interface 1406 (e.g., an interface for sending data to or receiving data from the memory external to the baseband circuit 1304), and an application circuit interface 1407 (e.g., an interface for sending data to or receiving data from the memory external to the baseband circuit 1304). Fig.13 an interface for sending data to or receiving data from the application circuit 1302), an RF circuit interface 1408 (for example, an interface for sending data to or receiving data from the application circuit Fig.13 an interface for sending data to or receiving data from the RF circuit 1320 of the wireless device), a wireless hardware connection interface 1410 (for example, for sending data to a near field communication (NFC) component, Parts (e.g. Low Energy), components and other communication components to send or receive data from these components) and a power management interface 1412 (e.g., an interface for sending or receiving power or control signals to or from the PMC 1334).

[0137] Fig.15 1 is a block diagram illustrating a component 1500 capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and capable of performing any one or more of the methods discussed herein, according to some example embodiments. Specifically, Fig.15 A schematic diagram of hardware resources 1502 is shown, which includes one or more processors 1512 (or processor cores), one or more memory / storage devices 1518, and one or more communication resources 1520, each of which can be communicatively coupled via a bus 1522. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 1504 can be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 1502.

[0138] Processor 1512 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) (such as a baseband processor), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 1514 and processor 1516.

[0139] The memory / storage device 1518 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1518 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.

[0140] The communication resources 1520 may include interconnect or network interface components or other suitable devices to communicate with one or more peripheral devices 1506 or one or more databases 1508 via the network 1510. For example, the communication resources 1520 may include wired communication components (e.g., for coupling via a universal serial bus (USB)), cellular communication components, NFC components, Parts (e.g. Low power consumption), components and other communication components.

[0141] The instructions 1524 may include software, programs, applications, applet, applications, or other executable code for causing at least any one of the processors 1512 to perform any one or more of the methods discussed herein. The instructions 1524 may reside completely or partially in at least one of the processors 1512 (e.g., in a cache memory of the processor), the memory / storage device 1518, or any suitable combination thereof. In addition, any portion of the instructions 1524 may be transmitted to the hardware resources 1502 from any combination of the peripheral device 1506 or the database 1508. Therefore, the memory of the processor 1512, the memory / storage device 1518, the peripheral device 1506, and the database 1508 are examples of computer-readable and machine-readable media.

[0142] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes and / or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following examples. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the example section below.

[0143] Fig.16 The architecture of a system 1600 of a network according to some embodiments is shown. The following description is provided for an exemplary system 1600 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 the embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G)) systems, etc.

[0144] like Fig.16 As shown, system 1600 includes UE 1601a and UE 1601b (collectively referred to as "UE 1601"). UE 1601a and / or UE 1601b may correspond to the above-mentioned UEs.

[0145] In this example, UE 1601 is shown as a smart phone (e.g., a handheld touch screen mobile computing device that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a consumer electronic device, a mobile phone, a smart phone, a feature phone, a tablet computer, a wearable computer device, a personal digital assistant (PDA), a pager, a wireless handheld device, a desktop computer, a laptop computer, an in-vehicle infotainment (IVI), an in-car entertainment (ICE) device, an instrument panel (IC), a head-up display (HUD) device, an on-board diagnostic (OBD) device, a dashtop mobile equipment (DME), a mobile data terminal (MDT), an electronic engine management system (EEMS), an electronic / engine control unit (ECU), an electronic / engine control module (ECM), an embedded system, a microcontroller, a control module, an engine management system (EMS), a networked or "smart" appliance, an MTC device, an M2M, an IoT device, etc.

[0146] In some embodiments, any of the UEs 1601 may be an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via PLMN, ProSe or D2D communications, sensor networks, or IoT networks. M2M or MTC data exchanges may be machine-initiated data exchanges. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0147] UE 1601 may be configured to connect, e.g., be communicatively coupled, to RAN 1610. In an embodiment, RAN 1610 may be an NG RAN or 5G RAN, an E-UTRAN, or a legacy RAN, such as UTRAN or GERAN. As used herein, the term "NGRAN" or the like may refer to RAN 1610 operating in an NR or 5G system 1600, while the term "E-UTRAN" or the like may refer to RAN 1610 operating in an LTE or 4G system 1600. UE 1601 utilizes connections (or channels) 1603 and 1604, respectively, each connection comprising a physical communication interface or layer (discussed in further detail below).

[0148] In this example, connections 1603 and 1604 are shown as air interfaces 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, UE 1601 can directly exchange communication data via a ProSe interface 1605. The ProSe interface 1605 can alternatively be referred to as a SL interface 1605, and can include one or more logical channels, including but not limited to PSCCH, PSSCH, PSDCH, and PSBCH.

[0149] UE 1601b is shown as being configured to access AP 1606 (also referred to as "WLAN node 1606," "WLAN 1606," "WLAN terminal 1606," or "WT 1606," etc.) via connection 1607. Connection 1607 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein AP 1606 would include wireless fidelity. router. In this example, AP 1606 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, UE 1601b, RAN 1610, and AP 1606 may be configured to utilize LWA operation and / or LWIP operation. LWA operation may involve UE 1601b in RRC CONNECTED being configured by RAN nodes 1611a-b to utilize radio resources of LTE and WLAN. LWIP operation may involve UE 1601b using WLAN radio resources (e.g., connection 1607) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., IP packets) sent through connection 1607. 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.

[0150] The RAN 1610 may include one or more AN nodes or RAN nodes 1611a and 1611b (collectively referred to as "RAN nodes 1611") that enable connections 1603 and 1604. As used herein, the terms "access node", "access point", etc. may describe equipment that provides radio baseband functions for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP or TRP, 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" and the like may refer to RNA nodes 1611 (e.g., gNBs) operating in NR or 5G systems 1600, while the terms "E-UTRAN nodes" and the like may refer to RAN nodes 1611 (e.g., eNBs) operating in LTE or 4G systems 1600. According to various embodiments, the RAN node 1611 may be implemented as one or more of dedicated physical devices 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.

[0151] In some embodiments, all or part of the RAN node 1611 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 RAN functional splitting, such as PDCP splitting, where the RRC and PDCP layers are operated by the CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes 1611; MAC / PHY splitting, where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes 1611; or "lower PHY" splitting, 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 1611. The virtualization framework allows idle processor cores of the RAN node 1611 to execute other virtualized applications. In some specific implementations, separate RAN nodes 1611 may be represented via separate FI interfaces ( Fig.16In some implementations, the gNB-DU 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 1610 or by a server pool in a manner similar to the CRAN / vBBUP. In addition or alternatively, one or more of the RAN nodes 1611 may be a next generation eNB (ng-eNB), which is a RAN node that provides E-UTRA user plane and control plane protocol terminals to the UE 1601 and is connected to the 5G Core (5GC) via an NG interface.

[0152] In a V2X scenario, one or more of the RAN nodes 1611 may be an RSU or act 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, wherein 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, the RSU is a computing device coupled to a radio frequency circuit located on the road side that provides connectivity support to a passing vehicle UE 1601 (vUE1601). 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 vehicle 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, etc. In addition 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. In addition 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 weather-resistant 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.

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

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

[0155] In some embodiments, the downlink resource grid can be used for downlink transmissions from any node in the RAN node 1611 to the UE 1601, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, called a resource grid or a time-frequency resource grid, which is the physical resource in the downlink in each time slot. For OFDM systems, such a time-frequency plane representation is a common practice, which makes radio resource allocation intuitive. Each column and each 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 the 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 set 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.

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

[0157] To operate in the unlicensed spectrum, the UE 1601 and the RAN node 1611 may operate using LAA, eLAA, and / or feLAA mechanisms. In these implementations, the UE 1601 and the RAN node 1611 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.

[0158] LBT is a mechanism by which equipment (e.g., UE 1601, RAN node 1611, etc.) senses a 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 a CCA that utilizes at least an 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 expected transmission band and comparing the sensed RF energy to a predefined or configured threshold.

[0159] Typically, existing systems in the 5 GHz band are WLANs based on IEEE 802.11 technology. WLANs use a contention-based channel access mechanism called CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 1601, AP 1606, etc.) intends to transmit, the WLAN node may first perform CCA before transmission. In addition, in the case where more than one WLAN node senses the channel as idle and transmits at the same time, a backoff mechanism is used to avoid conflicts. The backoff mechanism may be a counter randomly introduced within the CWS that increases exponentially when a conflict occurs and is reset to a minimum value when the transmission is successful. The LBT mechanism designed for LAA is somewhat similar to the CSMA / CA of WLAN. In some specific implementations, the LBT process for a DL or UL transmission burst (including PDSCH or PUSCH transmission) may have a 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 of 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.

[0160] The LAA mechanism is built on the CA technology of the LTE-Advanced system. In CA, each aggregated carrier is called a CC. A CC may have a bandwidth of 1.4MHz, 3MHz, 5MHz, 10MHz, 15MHz, or 20MHz, and up to five CCs may be aggregated, so the maximum aggregated bandwidth is 100MHz. In an FDD system, the number of aggregated carriers may 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 may have a different bandwidth from other CCs. In a TDD system, the number of CCs and the bandwidth of each CC are typically the same for DL ​​and UL.

[0161] 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. 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 PCCs may require UE 1601 to undergo switching. In LAA, eLAA, and feLAA, some or all of the SCells may operate in an 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 start positions within the same subframe.

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

[0163] PDCCH uses control channel elements (CCE) to transmit control information. Before being mapped to resource elements, the PDCCH complex-valued symbols can first be organized into quadruplets, which can then be arranged using a sub-block interleaver for rate matching. Each PDCCH can be transmitted using one or more of these CCEs, where each CCE can correspond to six resource element groups (REGs). Each REG includes a resource block in an OFDM symbol. Depending on the size of the downlink control information (DCI) and channel conditions, one or more CCEs can be used to transmit the PDCCH. Different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, 8, or 16) can be used for the transmission of PDCCH.

[0164] 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 nine sets of four physical resource elements, referred to as EREG. In some cases, ECCE may have other numbers of EREGs.

[0165] The RAN nodes 1611 may be configured to communicate with each other via an interface 1612. In an embodiment where the system 1600 is an LTE system (e.g., when the CN 1620 is an EPC), the interface 1612 may be an X2 interface 1612. The X2 interface may be defined between two or more RAN nodes 1611 (e.g., two or more eNBs, etc.) connected to the EPC 1620, and / or between two eNBs connected to the EPC 1620. 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 transmit information about the delivery of user data between eNBs. For example, X2-U may provide specific sequence number information about user data transmitted from MeNB to SeNB; information about successful in-sequence delivery of PDCP PDUs from SeNB to UE 1601 for user data; information about PDCP PDUs not delivered to UE 1601; information about the current minimum expected buffer size at SeNB for transmitting user data to UE; and the like. X2-C may provide intra-LTE access mobility functions, including context transfer from source eNB to target eNB, user plane transmission control, etc.; load management functions; and inter-cell interference coordination functions. In an embodiment where system 1600 is a 5G or NR system (e.g., when CN 1620 is a 5GC), interface 1612 may be an Xn interface 1612. The Xn interface is defined between two or more RAN nodes 1611 (e.g., two or more gNBs, etc.) connected to 5GC 1620, between a RAN node 1611 (e.g., gNB) connected to 5GC 1620 and an eNB, and / or between two eNBs connected to 5GC 1620. In some specific 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 functions of the Xn-C interface; mobility support for UE 1601 in connected mode (e.g., CM connection) includes functions for managing UE mobility in connected mode between one or more RAN nodes 1611. Mobility support may include context transfer from the old (source) serving RAN node 1611 to the new (target) serving RAN node 1611; and control of the user plane tunnel between the old (source) serving RAN node 1611 and the new (target) serving RAN node 1611. The protocol stack of the Xn-U may include a transport network layer built on an Internet Protocol (IP) transport layer, and a GTP-U layer on top of a UDP and / or IP layer 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 on top of the IP layer and may provide guaranteed delivery of application layer messages. In the transport IP layer, signaling PDUs are delivered using point-to-point transport. In other specific implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0166] RAN 1610 is shown as being communicatively coupled to a core network—in this embodiment, a core network (CN) 1620. The CN 1620 may include a plurality of network elements 1622 configured to provide various data and telecommunication services to customers / users (e.g., users of UE 1601) connected to CN 1620 via RAN 1610. The components of CN 1620 may be implemented in one physical node or in 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 above network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 1620 may be referred to as a network slice, and a logical instance of a portion of CN 1620 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 may be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.

[0167] Generally speaking, the application server 1630 may be an element that provides applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data service, etc.). The application server 1630 may also be configured to support one or more communication services for the UE 1601 via the EPC 1620 (e.g., VoIP session, PTT session, group communication session, social network service, etc.).

[0168] In an embodiment, CN 1620 may be a 5GC (referred to as "5GC 1620" or the like), and RAN 1610 may be connected to CN 1620 via an NG interface 1613. In an embodiment, NG interface 1613 may be divided into two parts: an NG user plane (NG-U) interface 1614, which carries traffic data between RAN node 1611 and UPF; and an S1 control plane (NG-C) interface 1615, which is a signaling interface between RAN node 1611 and AMF.

[0169] In an embodiment, CN 1620 may be a 5G CN (referred to as "5GC 1620", etc.), while in other embodiments, CN 1620 may be an EPC. In the case where CN 1620 is an EPC (referred to as "EPC 1620", etc.), RAN 1610 may be connected to CN 1620 via an S1 interface 1613. In an embodiment, the S1 interface 1613 may be divided into two parts: an S1 user plane (SI-U) interface 1614, which carries traffic data between the RAN node 1611 and the S-GW; and an S1-MME interface 1615, which is a signaling interface between the RAN node 1611 and the MME.

[0170] Additional Embodiments

[0171] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes and / or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following examples. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the example section below.

[0172] The following examples relate to additional embodiments.

[0173] Embodiment 1 is a method for a user equipment (UE), the method comprising: obtaining configuration information, the configuration information comprising first configuration information for determining a configured grant (CG) / semi-persistent scheduling (SPS) configuration, wherein the first configuration information is included in a radio resource control (RRC) message; and performing data transmission / reception via the CG / SPS configuration determined by the configuration information.

[0174] Embodiment 2 is a method according to embodiment 1, wherein the configuration information also includes second configuration information for determining the CG / SPS configuration, wherein the second configuration information is included in downlink control information (DCI).

[0175] Embodiment 3 is a method according to embodiment 1, wherein the configuration information also includes second configuration information for determining the CG / SPS configuration, wherein the second configuration information is provided together with the first configuration information via the RRC message.

[0176] Embodiment 4 is a method according to Embodiment 2 or 3, wherein the first configuration information indicates a parameter of a CG / SPS configuration index having a predetermined value, and the second configuration information indicates the timing of the CG / SPS configuration and a plurality of service cells on which the CG / SPS configuration is applied, and wherein performing the data transmission / reception includes: performing the data transmission / reception on the plurality of service cells via carrier aggregation (CA) at the timing of the CG / SPS configuration.

[0177] Embodiment 5 is a method according to embodiment 4, wherein performing the data transmission on the multiple service cells includes: determining whether any service cell among the multiple service cells is sufficient for the data transmission based on the amount of data; and in response to determining that the one service cell is sufficient for the data transmission, selecting the service cell for the data transmission.

[0178] Embodiment 6 is a method according to embodiment 4, wherein performing the data reception on the multiple service cells includes: detecting whether discontinuous transmission (DTX) occurs on any secondary cell among the multiple service cells at the timing of the SPS configuration; and in response to determining that the DTX is detected, skipping the data reception on the secondary cell and performing the data reception on a selected active cell among the multiple service cells based on the capability of the UE.

[0179] Embodiment 7 is a method according to Embodiment 2 or 3, wherein the first configuration information indicates a parameter of a CG / SPS configuration index having a predetermined value, and the second configuration information indicates a set of timings corresponding to multiple service cells of the CG / SPS configuration, and wherein the performing of the data transmission / reception includes: performing the data transmission / reception in a repeated manner via the set of timings of the CG / SPS configuration on a corresponding service cell among the multiple service cells.

[0180] Embodiment 8 is a method according to embodiment 7, wherein performing the data transmission / reception in the repeated manner on the corresponding service cell among the multiple service cells includes: simultaneously performing the data transmission / reception on a primary cell among the multiple service cells and a secondary cell among the multiple service cells.

[0181] Embodiment 9 is a method according to embodiment 2 or 3, wherein the first configuration information includes a first parameter of a CG / SPS configuration index having a predetermined value, and a second parameter indicating a timing window having a predetermined number of optional timings; and the second configuration information indicates activation of the CG / SPS configuration, and wherein the performing of the data transmission / reception includes: performing the data transmission / reception at a selected timing within the timing window, wherein the selected timing is based on the capability of the UE or the time when the data for transmission arrives / is detected to the time when the data for reception arrives.

[0182] Embodiment 10 is a method according to embodiment 9, wherein the first configuration information further includes a third parameter indicating a timing window of each cycle, and wherein corresponding selected timings of two adjacent timing windows are independent of each other.

[0183] Embodiment 11 is a method according to any one of Embodiments 1 to 10, further comprising: determining whether at least one factor selected from the group of transmission delay, transmission success rate and radio quality satisfies a preset condition; and in response to determining that the selected factor satisfies the preset condition, providing preference information for the configuration of the configuration information to be obtained.

[0184] Embodiment 12 is a method for a user equipment (UE), the method comprising: obtaining, by an access layer (AS), packet association information from an upper layer above the AS layer, wherein the packet association information indicates packets that are associated together to correspond to the same frame and key packets in the packets; and performing data transmission via dedicated scheduling for the key packets.

[0185] Embodiment 13 is a method according to embodiment 12, further comprising: obtaining the dedicated scheduling for the critical group, comprising: providing a dedicated scheduling request (SR) requesting the dedicated scheduling for the critical group; providing the data amount of the critical group in a buffer status report (BSR) of a medium access control (MAC) control element (CE); and obtaining a configured grant (CG) configuration, the CG configuration indicating that the critical group has a higher priority than the remaining packets in the group.

[0186] Embodiment 14 is a method according to embodiment 13, wherein obtaining the CG configuration includes: obtaining downlink control information (DCI) indicating that the critical packet has a higher priority than the remaining packets, and wherein performing the data transmission via dedicated scheduling for the critical packet includes: when the DCI is received, performing the data transmission only for the critical packet.

[0187] Embodiment 15 is a method according to any one of Embodiments 12 to 14, further comprising: determining whether the data transmission for the key group is successfully performed; in response to determining that the data transmission for the key group is not successfully performed, discarding the data transmission for the remaining groups that have not yet been transmitted.

[0188] Embodiment 16 is a method according to any one of Embodiments 12 to 14, further comprising: determining whether the data transmission for the key packet is successfully performed; in response to determining that the data transmission for the key packet is not successfully performed, performing the data transmission for the remaining packets that have been assigned sequence numbers (SN) for transmission or are being transmitted in the following manner: so that the remaining packets are indicated only in a radio link control (RLC) header without any payload for transmission.

[0189] Embodiment 17 is a method according to any one of Embodiments 12 to 14, further comprising: receiving the packets associated together to correspond to the same frame; determining whether the key packets in the packets are successfully received; and in response to determining that the key packets are not successfully received, abandoning the remaining packets in the packets in the AS layer so that the remaining packets are not delivered to the upper layer.

[0190] Embodiment 18 is a method according to embodiment 17, further comprising: providing RLC acknowledgment (ACK) for the remaining packets as feedback of the reception while discarding the remaining packets.

[0191] Embodiment 19 is a device for a user equipment (UE), the device comprising: one or more processors, the one or more processors being configured to execute the steps of the method according to any one of Embodiments 1 to 18.

[0192] Embodiment 20 is a computer-readable medium having a computer program stored thereon, which, when executed by one or more processors, causes an apparatus to perform the steps of the method according to any one of embodiments 1 to 18.

[0193] Embodiment 21 is an apparatus for a communication device, the apparatus comprising a module for executing the steps of the method according to any one of Embodiments 1 to 18.

[0194] Embodiment 22 is a computer program product, which includes a computer program, which, when executed by one or more processors, causes an apparatus to perform the steps of the method according to any one of embodiments 1 to 18.

[0195] Unless explicitly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in view of the above teachings or may be obtained from the practice of the various embodiments.

[0196] It should be appreciated that the systems described herein include descriptions of specific embodiments. These embodiments may be combined into a single system, partially incorporated into other systems, separated into multiple systems, or otherwise divided or combined. In addition, it is contemplated that parameters / attributes / aspects, etc. of one embodiment may be used in another embodiment. For clarity, these parameters / attributes / aspects, etc. are described only in one or more embodiments, and it should be appreciated that unless otherwise stated herein, these parameters / attributes / aspects, etc. may be combined with or substituted for parameters / attributes, etc. of another embodiment.

[0197] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0198] Although the foregoing has been described in considerable detail for the sake of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways to implement both the processes and the apparatus described herein. Therefore, the embodiments of the present invention are to be regarded as illustrative rather than restrictive, and the specification is not limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

1. A method comprising: determining that a plurality of groups are associated with each other; determining that an attempt to transmit a first packet of the plurality of packets was unsuccessful; as well as One or more packets of the plurality of packets are discarded based on a determination that the attempt to transmit the first packet was unsuccessful.

2. The method according to claim 1, further comprising: The one or more packets are discarded based further on determining that the first packet is a critical packet.

3. The method according to claim 1, further comprising: It is determined that the plurality of groups are associated with each other based on the group association information.

4. The method according to claim 3, further comprising: The packet association information is obtained from a layer above the access layer at the access layer.

5. The method according to claim 3, further comprising: The group association information is acquired from a group among the plurality of groups. The method of claim 1 , wherein the plurality of packets correspond to the same frame.

7. The method of claim 1 , wherein the one or more packets include a first packet having a radio link control (RLC) header and a payload, and the method further comprises: A second packet associated with the first packet is output for transmission, wherein the second packet includes the RLC header but does not include the payload.

8. An apparatus comprising a processing circuit, the processing circuit being configured to: determining that a plurality of groups are associated with each other; determining that an attempt to transmit a first packet of the plurality of packets was unsuccessful; and One or more packets of the plurality of packets are discarded based on a determination that the attempt to transmit the first packet was unsuccessful.

9. The apparatus of claim 8, wherein the processing circuit is further configured to: The one or more packets are discarded based further on determining that the first packet is a critical packet.

10. The apparatus of claim 8, wherein the processing circuit is further configured to: It is determined that the plurality of groups are associated with each other based on the group association information.

11. The apparatus of claim 10, wherein the processing circuit is further configured to: The packet association information is obtained from a layer above the access layer at the access layer.

12. The apparatus of claim 10, wherein the processing circuit is further configured to: The group association information is acquired from a group among the plurality of groups.

13. The apparatus of claim 8, wherein the plurality of packets correspond to the same frame.

14. The apparatus of claim 8, wherein the one or more packets include a first packet having a radio link control (RLC) header and a payload, and the processing circuit is further configured to: A second packet associated with the first packet is output for transmission, wherein the second packet includes the RLC header but does not include the payload.

15. A method comprising: determining that a plurality of groups are associated with each other; determining that an attempt to receive a first packet of the plurality of packets was unsuccessful; as well as One or more packets of the plurality of packets are discarded based on a determination that the attempt to receive the first packet was unsuccessful.

16. The method according to claim 15, further comprising: The one or more packets are discarded based further on determining that the first packet is a critical packet.

17. The method according to claim 15, further comprising: It is determined that the plurality of groups are associated with each other based on the group association information.

18. The method according to claim 17, further comprising: The packet association information is obtained from a layer above the access layer at the access layer.

19. The method according to claim 17, further comprising: The group association information is acquired from a group among the plurality of groups.

20. The method of claim 15, wherein the plurality of packets correspond to the same frame.