Enhanced authorization configured

Abstract

A method for a network is provided, the method comprising: determining QoS information of a plurality of data streams having different Quality of Service (QoS) attributes; transmitting to a User Equipment (UE) a configuration message generated based on the QoS information, wherein the configuration message includes configuration information of at least one Configured Citation (CG); and receiving uplink data based on the plurality of data streams from the UE based on the at least one CG.

Description

Technical Field

[0001] This application relates generally to wireless communication systems, and more specifically to enhancements for configured licenses. Background Technology

[0002] 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 the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE); the 5th Generation (5G) 3GPP New Radio (NR) standard; the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, commonly referred to by the industry organization as Global Microwave Access Interoperability (WiMAX); and the IEEE 802.11 standard for Wireless Local Area Networks (WLANs), commonly referred to by the industry organization as Wi-Fi. In the 3GPP Radio Access Network (RAN) of an LTE system, a base station may include RAN nodes such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly referred to as an Evolved Node B, Enhanced Node B, eNodeB, or eNB) and / or a Radio Network Controller (RNC) in the E-UTRAN, which communicates with wireless communication equipment called User Equipment (UE). In a fifth-generation (5G) wireless RAN, RAN nodes may include 5G nodes, New Radio (NR) nodes, or g node B (gNB), which communicate with wireless communication equipment (also known as user equipment (UE)). Summary of the Invention

[0003] According to an aspect of this disclosure, a method for a network is provided, the method comprising: determining QoS information of a plurality of data streams having different Quality of Service (QoS) attributes; transmitting to a User Equipment (UE) a configuration message generated based on the QoS information, wherein the configuration message includes configuration information of at least one Configured Citation (CG); and receiving uplink data based on the plurality of data streams from the UE based on the at least one CG.

[0004] According to an aspect of this disclosure, a method for a user equipment is provided, the method comprising receiving a configuration message from a network, wherein the configuration message includes configuration information of at least one configured authorization (CG) and is determined based on QoS information of multiple data streams having different quality of service (QoS) attributes; and generating uplink data based on the multiple data streams for transmission to the network based on at least one CG.

[0005] According to an aspect of this disclosure, an apparatus for a user equipment (UE) is provided, the apparatus comprising: one or more processors configured to perform the steps of the methods mentioned above for the user equipment.

[0006] According to an aspect of this disclosure, an apparatus for a network includes: one or more processors configured to perform the steps of the methods mentioned above for the network.

[0007] According to an aspect of this disclosure, a computer-readable medium having a computer program stored thereon is provided, which, when executed by one or more processors, causes a device to perform the steps of the methods mentioned above.

[0008] According to an aspect of this disclosure, a computer program product includes a computer program that, when executed by one or more processors, causes a device to perform the steps of the methods mentioned above. Attached Figure Description

[0009] The features and advantages of this disclosure will become apparent from the following detailed description taken in conjunction with the accompanying drawings, which illustrate the features of this disclosure by way of example.

[0010] Figure 1 It is a block diagram of a system including base stations and user equipment (UE) according to some implementation schemes.

[0011] Figure 2 A flowchart of an exemplary method for a network according to some implementation schemes is shown.

[0012] Figure 3 A flowchart of an exemplary method for a user device according to some implementation schemes is shown.

[0013] Figure 4 The communication exchange combined with the determination of suggested information is illustrated according to some embodiments of this disclosure.

[0014] Figure 5 Another communication exchange is shown, combining the determination of suggested information with some embodiments of this disclosure.

[0015] Figure 6 This illustrates yet another communication exchange combined with the determination of suggested information according to some embodiments of this disclosure.

[0016] Figure 7 Communication exchange combined with CG-based uplink transmission is illustrated according to some embodiments of this disclosure.

[0017] Figure 8A Another communication exchange combined with CG-based uplink transmission is shown according to some embodiments of this disclosure.

[0018] Figure 8B Exemplary Media Access Control (MAC) – Control Element (CE) according to some embodiments of this disclosure are shown.

[0019] Figure 9 This illustrates another communication exchange combined with CG-based uplink transmission according to some embodiments of this disclosure.

[0020] Figure 10 This illustrates another communication exchange combined with CG-based uplink transmission according to some embodiments of this disclosure.

[0021] Figure 11 This illustrates another communication exchange combined with CG-based uplink transmission according to some embodiments of this disclosure.

[0022] Figure 12 This illustrates another communication exchange combined with CG-based uplink transmission according to some embodiments of this disclosure.

[0023] Figure 13 An exemplary block diagram of an apparatus for a network according to some embodiments is shown.

[0024] Figure 14 An exemplary block diagram of an apparatus for a UE according to some implementation schemes is shown.

[0025] Figure 15 Exemplary components of a device 1500 according to some embodiments are shown.

[0026] Figure 16 An exemplary interface of a baseband circuit according to some implementation schemes is shown.

[0027] Figure 17 The components are shown according to some implementation schemes.

[0028] Figure 18 The architecture of a wireless network according to some implementation schemes is shown. Detailed Implementation

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

[0030] Carrier aggregation is a technique that allows multiple carrier signals operating at different frequencies to be used to carry communications for a single UE, thereby increasing the bandwidth available to a single device. In some aspects, carrier aggregation can be used when one or more component carriers are operating at unlicensed frequencies.

[0031] To increase bandwidth and thus bit rate, user equipment (UE) can connect to more than one serving cell. In New Radio (NR), one serving cell can be designated as the primary cell (PCell), while other cells can be secondary cells (SCells). In some cases, the PCell and SCell for the UE may correspond to the same base station (supported by the same base station). In other cases, the PCell and SCell may correspond to different base stations (supported by different base stations).

[0032] In wireless communication, each frequency band has a primary component carrier called the primary cell (PCell), and the other component carriers are called secondary cells (SCells). SCells can be activated for data transmission if necessary.

[0033] Figure 1 A wireless network 100 according to some embodiments is shown. The wireless network 100 includes a UE 101 and a base station 150 connected via an air interface 190.

[0034] UE 101 and any other UE in the system can be, for example, a laptop computer, smartphone, tablet computer, printer, machine-type device, such as a smart meter or dedicated device for healthcare monitoring, remote security monitoring, intelligent transportation systems, or any other wireless device with or without a user interface. Base station 150 provides UE 101 with network connectivity to a wider network (not shown) via air interface 190 within the base station service area provided by base station 150. In some embodiments, such a wider network can be a wide area network operated by a cellular network provider, or it can 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 multiple sectors associated with certain antennas. Such sectors can be physically associated with fixed antennas, or can be assigned to physical areas with tunable antennas or antenna configurations that can be adjusted during beamforming to direct signals to a particular sector. For example, one implementation of base station 150 includes three sectors, each covering a 120-degree area, wherein the antenna array is pointed at each sector to provide 360-degree coverage around base station 150.

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

[0036] Figure 1 Base station 150 according to various embodiments is also shown. Base station 150 circuitry may include control circuitry 155 coupled to transmission circuitry 160 and receiving circuitry 165. Transmission circuitry 160 and receiving circuitry 165 may each be coupled to one or more antennas, which may be used for communication via air interface 190.

[0037] Control circuitry 155 can be adapted to perform operations associated with the MTC. Transmit circuitry 160 and receive circuitry 165 can be adapted to transmit and receive data respectively within a narrow system bandwidth, which is narrower than the standard bandwidth used for personal communications. In some embodiments, for example, the transmission bandwidth can be set to or close to 1.4 MHz. In other embodiments, other bandwidths can be used. Control circuitry 155 can perform various operations, such as those associated with the base station described elsewhere in this disclosure.

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

[0039] Within a narrow system bandwidth, receiver circuit 165 can receive multiple multiplexed uplink physical channels. These multiple uplink physical channels can be multiplexed according to TDM or FDM. Receiver circuit 165 can receive these multiple multiplexed uplink physical channels in an uplink superframe composed of multiple uplink subframes.

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

[0041] The UE and various base stations (e.g., base stations supporting all types of serving cells including PCells and SCells, or base stations acting as network devices for communicating with the UE) described in the following embodiments can be provided by Figure 1 The UE 101 and base station 150 described herein are implemented.

[0042] The configured grant (CG) can be used to satisfy periodic data transmission or to satisfy services with low latency requirements. Based on the configured grant indicated in the control message received from the network, the UE can send uplink data at each time the CG is configured.

[0043] The data streams to be transmitted can have different QoS attributes. For example, data streams can have different priorities, different transport block (TB) sizes, etc. It would be advantageous if network scheduling could be determined based on the different QoS attributes of different data streams.

[0044] The current configuration method for configured licenses supports the association between a specific logical channel (LCH) and a configured license. For example, a first logical channel (LCH 1) can be configured to transmit based on a first configured license (CG 1), and a second logical channel (LCH 2), different from LCH 1, can be configured to transmit based on a second configured license (CG 2). However, in the configuration of CGs, the network does not consider the different QoS requirements of the data streams to be transmitted.

[0045] Figure 2 A flowchart of an exemplary method for a network according to some implementation schemes is shown. Figure 2 The method 200 shown can be derived from Figure 1 Implemented using UE 101 as described in the document.

[0046] At step 202, the network can determine QoS information for multiple data streams with different Quality of Service (QoS) attributes.

[0047] Multiple data streams may include user data generated by an application server or received from an external data network (e.g., the Internet). Multiple data streams may have different QoS attributes. QoS information can be any information indicating the QoS attributes of a data stream. In some examples, QoS information may indicate mapping information for QoS streams. For example, mapping information may indicate a mapping between a QoS stream and an LCH (or Data Radio Bearer (DRB)). As another example, mapping information may indicate a mapping between an IP stream and a QoS stream.

[0048] In some implementations, multiple data streams can be mapped to different Internet Protocol (IP) streams in the Non-Access Stratum (NAS) layer. Therefore, different IP streams can have different QoS attributes. IP stream identifiers (IDs) or priority IDs can be assigned to different IP streams to indicate QoS attributes.

[0049] QoS information may include the IP flow identifier (ID) for each packet in the QoS flow. In some implementations, IP flows may be mapped to the same QoS flow. When mapping IP flows to QoS flows, the IP flow ID or priority ID of each packet may be indicated to identify the IP flow to which the corresponding packet belongs in the NAS layer.

[0050] QoS information may include the QoS Flow ID (QFI) / 5G QoS Identifier (5QI) and / or QoS profile of the QoS flow. In some other implementations, IP flows may be mapped to different QoS flows. Different QoS attributes of a data flow may be indicated by the QoS Flow ID (QFI) / 5G QoS Identifier (5QI) and / or QoS profile of the QoS flow.

[0051] QoS information may include LCH IDs. In other specific implementations, different QoS flows may be mapped to different LCHs. Therefore, different LCH IDs can indicate different QoS attributes.

[0052] At step 204, the network may transmit a configuration message generated based on QoS information to the user equipment (UE), wherein the configuration message includes configuration information of at least one configured authorization (CG).

[0053] In some implementations, configuration messages may be transmitted via Radio Resource Control (RRC) messages or physical layer signaling. Configuration messages may include configuration information for at least one CG.

[0054] The network can send RRC messages to the UE to configure uplink grants, and the uplink grants can be stored as CGs. A configured CG can be activated or deactivated based on signaling from the network. The CG configuration information can include the periodicity of the CG, and uplink data can be transmitted at each point in time based on the configured periodicity of the CG.

[0055] Configuration messages can be generated based on the QoS information of the data stream.

[0056] In some implementations, configuration information can be generated based on the mapping information of QoS flows in the AS layer.

[0057] In some implementations, when multiple data flows with different QoS attributes are mapped to different LCHs, the configuration information in the configuration message may indicate that different LCHs are allowed to be transmitted based on different CGs (or different times within the same CG). In some other implementations, when multiple data flows with different QoS attributes are mapped to different QoS flows, the configuration information in the configuration message may indicate that different QoS flows are allowed to be transmitted based on different CGs (or different times within the same CG). In still other implementations, when multiple data flows with different QoS attributes are mapped to different IP flows but the same QoS flow, the configuration information in the configuration message may indicate that packets in the QoS flow are allowed to be transmitted based on different CGs (or different times within the same CG) based on each packet's information (e.g., IP flow ID).

[0058] In some implementations, configuration information can be generated based on the TB size of the QoS stream.

[0059] In some implementations, the CG can be configured to support the same TB size at every point in the CG. In other implementations, the CG can be configured to support different TB sizes at different points in the CG.

[0060] At step 206, the network may receive uplink (UL) data based on multiple data streams from the UE based on at least one CG.

[0061] At each time point of at least one CG configured by the configuration message, the network may receive uplink data from the UE. The uplink data is compiled based on data from QoS streams mapped to multiple data streams.

[0062] Figure 3 A flowchart of an exemplary method for a user device according to some implementation schemes is shown. Figure 3 The method 300 shown can be derived from Figure 1 Implemented using UE 101 as described in [the document].

[0063] At step S302, the UE may receive a configuration message from the network, wherein the configuration message includes configuration information of at least one configured authorization (CG) and is determined based on QoS information of multiple data streams with different quality of service (QoS) attributes.

[0064] In some implementations, configuration messages may be transmitted via Radio Resource Control (RRC) messages or physical layer signaling. Configuration messages may include configuration information for at least one CG.

[0065] The UE can receive configuration messages and store at least one CG. If the stored CG is activated, the UE can send UL data to the network at each time the CG is activated.

[0066] At step S304, the UE may generate uplink data based on multiple data streams based on at least one CG for transmission to the network.

[0067] According to the method for configuring a CG provided in this disclosure, the CG is configured to provide scheduling for data streams with different QoS attributes. In other words, this disclosure provides a way to configure the transmission of data with different QoS requirements for different scheduling.

[0068] In some implementations, step S202 may include the network determining QoS information for multiple data streams based on recommendation information reported by the UE. The network may receive recommendation information regarding QoS information from the UE and determine the QoS information based on the recommendation to the UE. In some examples, the recommendation information may be received directly by the base station. In other examples, the recommendation information may be received by the core network (CN) and forwarded to the base station via the CN.

[0069] In some other implementations, step S202 may include the network determining QoS information itself. The CN may determine the QoS information via an application server and notify the base station of the determined QoS information.

[0070] Depending on the UE side, method 300 may further include the UE generating recommendation information regarding QoS information for multiple data streams for transmission to the network. The recommendation information may be transmitted to the core network (CN) or a base station.

[0071] The recommendation information may indicate preferences for the mapping between QoS flows (QFIs) and LCHs. In some examples, the recommendation information may include a suggested traffic pattern for each mapping between QFIs and LCHs. In other examples, the recommendation information may include suggested traffic patterns for the set of QFIs associated with the same LCH. The recommendation information may be a complete set of preferred traffic patterns for each mapping, or preferred changes based on the current configuration.

[0072] Figure 4 The communication exchange combined with the determination of suggested information is illustrated according to some embodiments of this disclosure.

[0073] like Figure 4 As shown, at operation 403, UE 401 may send suggestion information to base station 402. The suggestion information may include suggested traffic patterns for QoS flows or LCH.

[0074] At operation 404, base station 402 may generate at least one CG configuration based on the recommendation information. Based on the recommended traffic pattern in the recommendation information, base station 402 may determine at least one transmission mode for CG-based transmission.

[0075] At operation 405, base station 402 may transmit at least one CG configuration message to UE.

[0076] At operation 406, UE 401 may perform uplink transmission based on the CG configured by the configuration message received at operation 405.

[0077] Figure 5 Another communication exchange is shown, combining the determination of suggested information with some embodiments of this disclosure.

[0078] like Figure 5 As shown, at operation 504, UE 501 can send suggestion information to CN 503. The suggestion information may include suggested traffic patterns for QoS flows or LCH.

[0079] At operation 505, CN 503 can forward the suggestion information to base station 502 and notify base station 502 of the suggestion information.

[0080] At operation 506, base station 502 may generate at least one CG configuration based on the recommendation information. Based on the recommended traffic pattern in the recommendation information, base station 502 may determine at least one transmission mode for CG-based transmission.

[0081] At operation 507, base station 502 may transmit at least one CG configuration message to UE.

[0082] At operation 508, UE 501 may perform uplink transmission based on the CG configured by the configuration message received at operation 507.

[0083] Figure 6 This illustrates yet another communication exchange combined with the determination of suggested information according to some embodiments of this disclosure.

[0084] like Figure 6 As shown, at operation 604, CN 603 may determine the recommendation information, for example, via an application server.

[0085] At operation 605, CN 603 may notify base station 602 of recommended information. The recommended information may include recommended traffic patterns for QoS flows or LCH.

[0086] At operation 606, base station 602 may generate at least one CG configuration based on the recommendation information. Based on the recommended traffic pattern in the recommendation information, base station 602 may determine at least one transmission mode for CG-based transmission.

[0087] At operation 607, base station 602 may transmit at least one CG configuration message to UE.

[0088] At operation 608, UE 601 may perform uplink transmission based on the CG configured by the configuration message received at operation 607.

[0089] In some implementations, multiple data streams may include a first data stream and a second data stream. The first data stream and the second data stream are configured with different QoS attributes. At least one CG configured by a configuration message may include a first CG and a second CG. The second CG is different from the first CG.

[0090] In some implementations, a first data stream is mapped to a first LCH (LCH 1), and a second data stream is mapped to a second LCH (LCH 2) that is different from the first LCH. For example, the network can determine QoS information indicating the mapping between the first data stream and LCH 1, and the mapping between the second data stream and LCH 1. Therefore, the network can configure different QoS streams corresponding to the first data stream and second data streams to be mapped to different LCHs. The network's base stations (e.g., gNBs) can provide scheduling to meet LCH / DRB level QoS requirements.

[0091] The network can further configure different LCHs for the first data stream and second data streams to be mapped to different CGs. For example, configuration information transmitted from the network to the UE can indicate that the first LCH is configured to be transmitted based on the first CG and the second LCH is configured to be transmitted based on the second CG.

[0092] Figure 7 Communication exchange combined with CG-based uplink transmission is illustrated according to some embodiments of this disclosure.

[0093] like Figure 7 As shown, at operation 703, base station 702 can send CG configuration messages of the first CG (CG 1) and the second CG (CG 2) to UE 701.

[0094] When CG 1 is activated, UE 701 can perform uplink transmission of LCH 1 based on CG 1. For example, in each timing of CG 1, the Packet Data Convergence Protocol (PDCP) can assemble Protocol Data Units (PDUs) based on LCH to CG, and user data in LCH 1 can be transmitted in the uplink transmission. At operations 704 and 706, the UE can transmit LCH 1 data in the first timing of CG 1 and the second timing of CG 1, respectively.

[0095] Similarly, UE 701 can perform uplink transmission of LCH 2 based on CG 2. For example, user data in LCH 2 can be transmitted in the uplink transmission during each timing of CG 2. At operations 705 and 707, the UE can transmit LCH 2 data during a first timing of CG 2 and a second timing of CG 2, respectively.

[0096] According to the embodiments of this disclosure, the network can know the QoS requirements for data streams and configure data streams with different QoS attributes to be mapped to different LCHs. Therefore, by configuring different LCHs to be mapped to different CGs, data with different QoS attributes can be scheduled in different modes to meet different QoS requirements.

[0097] The current mechanism supports scheduling to meet LCH / DRB level QoS requirements, which map different LCHs to different CGs. However, if the AS layer only provides LCH-based scheduling, different QoS flows mapped to the same LCH will be scheduled in the same pattern. To provide QoS flow level QoS requirements, a mapping between QoS flows (QFI / 5QI) and CGs is introduced.

[0098] In some other implementations, a first data stream may be mapped to a first QoS stream, and a second data stream may be mapped to a second QoS stream. The second QoS stream may differ from the first QoS stream. For example, the QoS parameters and QoS characteristics of the second QoS stream may differ from those of the first QoS stream. In some examples, the first QoS stream and the second QoS stream may be mapped to the same LCH (e.g., the first LCH) or to different LCHs (e.g., the first QoS stream mapped to the first LCH and the second QoS stream mapped to the second LCH).

[0099] Figure 8A Another communication exchange combined with CG-based uplink transmission is shown according to some embodiments of this disclosure.

[0100] like Figure 8AAs shown, at operation 803, base station 802 may send CG configuration messages for a first CG (CG1) and a second CG (CG2) to UE 801. The configuration information in the CG configuration message may indicate that the first QoS stream (QoS stream 1) is configured to be transmitted based on CG 1, and the second QoS stream (QoS stream 2) may be configured to be transmitted based on CG 2.

[0101] When CG 1 is activated, UE 801 can perform uplink transmissions for QoS Flow 1 based on CG 1. For example, in each timing of CG 1, the Packet Data Convergence Protocol (PDCP) can map Protocol Data Units (PDUs) to CG based on the QoS Flow, and user data in QoS Flow 1 and QoS Flow 2 can be transmitted in the uplink transmission. At operations 804 and 806, the UE can transmit data for QoS Flow 1 in a first timing of CG 1 and a second timing of CG 1, respectively.

[0102] Similarly, UE 801 can perform uplink transmission for QoS flow 2 based on CG 2. For example, user data in QoS flow 2 can be transmitted in the uplink transmission during each timing of CG 2. At operations 805 and 807, the UE can transmit data for QoS flow 2 during a first timing of CG 2 and a second timing of CG 2, respectively.

[0103] Figure 8B Exemplary Media Access Control (MAC) – Control Element (CE) according to some embodiments of this disclosure are shown.

[0104] like Figure 8B As shown, when a UE reports a Buffer Status Report (BSR) for uplink transmission to the network, the BSR via MAC-CE may include buffer sizes for different QoS flows. For example, the BSR may include a first buffer size (buffer size 1) for the first QoS flow (flow ID 1) and a second buffer size (buffer size 2) for the second QoS flow (flow ID 2).

[0105] According to the network side, the network can receive BSR from the UE, wherein the BSR includes the first buffer size of the first QoS stream and the second buffer size of the second QoS stream.

[0106] According to the UE side, the UE can generate a buffer status report (BSR) for transmission to the network, wherein the BSR includes the first buffer size of the first QoS flow and the second buffer size of the second QoS flow.

[0107] By providing different buffer sizes for different QoS flows in the BSR, the UE can report more detailed information about different QoS flows, thus enabling scheduling based on different QoS flows.

[0108] exist Figure 8A In the example shown, each CG is configured for a single QoS stream. In other examples, CGs may be configured for two or more QoS streams. Multiple data streams may also include a third data stream, distinct from the first and second data streams. QoS information for the third data stream may indicate that the third data stream is mapped to a third QoS stream distinct from the first QoS stream. The third QoS stream may also be configured to be transmitted along with the first QoS stream based on the first CG.

[0109] Figure 9 This illustrates another communication exchange combined with CG-based uplink transmission according to some embodiments of this disclosure.

[0110] like Figure 9 As shown, at operation 903, base station 902 may send CG configuration messages for a first CG (CG 1) and a second CG (CG 2) to UE 901. The configuration information in the CG configuration messages may indicate that the first QoS stream (QoS stream 1) and the third QoS stream (QoS stream 3) are configured to be transmitted based on CG 1, and the second QoS stream (QoS stream 2) may be configured to be transmitted based on CG 2. In some examples, QoS stream 1, QoS stream 2, and QoS stream 3 may be mapped to the same LCH (e.g., the first LCH) or mapped to different LCHs respectively.

[0111] When CG 1 is activated, UE 901 can perform uplink transmissions for QoS flow 1 and QoS flow 2 based on CG 1. At operations 904 and 906, the UE can transmit data for QoS flow 1 and QoS flow 3 during a first timing of CG 1 and a second timing of CG 1, respectively.

[0112] Similarly, UE 901 can perform uplink transmission for QoS flow 2 based on CG 2. At operations 905 and 907, the UE can transmit QoS flow 2 data at a first timing of CG 2 and a second timing of CG 2, respectively.

[0113] exist Figure 9 In the example shown, QoS stream 3 can be transmitted simultaneously with QoS stream 1.

[0114] Although two QoS streams (QoS stream 1 and QoS stream 3) are configured for transmission based on CG 1, according to the principles of this disclosure, more QoS streams can be configured for transmission based on a single CG. Furthermore, a single CG can also be configured for more than one CG. For example, QoS stream 1 can be configured for both CG 1 and CG 2. As an example, CG 1 can be configured for transmission of both QoS stream 1 and QoS stream 3, and CG 2 can be configured for transmission of QoS stream 1. Those skilled in the art can determine the number of QoS streams to be transmitted based on the same CG according to the actual QoS requirements.

[0115] According to embodiments of this disclosure, a network (e.g., a gNB) can provide a mapping between the QFI of a QoS flow and the CG in a configuration message. The mapping between QFI and CG can be one-to-one or many-to-one. For example, a CG can be configured to allow the transmission of multiple QoS flows with different QFIs, or QoS flows with the same QFI can be configured to be transmitted based on multiple different CGs. Therefore, by configuring different QoS flows to be mapped to different CGs, different QoS flows can be scheduled in different modes to meet different QoS requirements, even when the QoS flows are mapped to the same LCH.

[0116] In other specific implementations, a first data stream may be mapped to a first IP stream, and a second data stream may be mapped to a second IP stream different from the first IP stream. Configuration information may indicate that the first IP stream is configured to be transmitted based on a first CG, and the second IP stream is configured to be transmitted based on a second CG. The first IP stream and the second IP stream may be mapped to the same QoS stream or different QoS streams in the AS layer.

[0117] If the first IP flow and the IP flow map to different QoS flows in the AS layer, the network can provide scheduling for different QoS flows, such as combining... Figure 8A and Figure 9 As described. However, if the first IP flow and the second IP flow map to the same QoS flow in the AS layer, the AS layer can provide LCH-based or QoS-based scheduling regardless of which IP flow is internally mapped, because the mapping between IP flows and QoS flows is not visible to the AS level. Therefore, this disclosure provides packet-based scheduling for different IP flows mapped to the same QoS flow. It should also be acknowledged that even when different IP flows map to different QoS flows, a combination of... Figure 10 The described group-based scheduling.

[0118] Figure 10 This illustrates another communication exchange combined with CG-based uplink transmission according to some embodiments of this disclosure.

[0119] like Figure 10As shown, at operation 1003, base station 1002 can send CG configuration messages for a first CG (CG 1) and a second CG (CG 2) to UE 1001. The configuration information in the CG configuration message can indicate that packets from the first IP flow (IP flow 1) can be configured for transmission based on CG 1, and packets from the second IP flow (IP flow 2) can be configured for transmission based on CG 2. Packets can be identified by each packet's information, such as the IP flow ID or a priority ID indicating a packet in a QoS flow. Different IP flow IDs for packets can indicate different QoS requirements for the packets. AS layer / Media Access Control (MAC) can perform packet and CG mapping based on each packet's information.

[0120] When CG 1 is activated, UE 1001 can perform uplink transmissions for packets from IP flow 1 based on CG 1. At operations 1004 and 1006, the UE can transmit packets from IP flow 1 at a first timing of CG 1 and a second timing of CG 1, respectively.

[0121] Similarly, UE 1001 can perform uplink transmissions for packets from IP flow 2 based on CG 2. At operations 1005 and 1007, the UE can transmit data from packets from IP flow 2 at a first timing of CG 2 and a second timing of CG 2, respectively.

[0122] According to embodiments of this disclosure, a network (e.g., a gNB) can provide a mapping between each packet information of the same QoS flow and a CG in a configuration message. The mapping between each packet information and a CG can be a one-to-one mapping or a many-to-one mapping. For example, a CG can be configured to allow the transmission of multiple packets with different IP flow IDs, or packets with the same IP flow ID can be configured to be transmitted based on multiple different CGs. Therefore, by configuring different packets in the same QoS flow to be mapped to different CGs, different packets can be scheduled in different modes to meet different QoS requirements, even when packets are mapped to the same QoS flow.

[0123] In the current configuration of CG, each timing of CG can support the same TB size. To provide a more flexible transmission mode for CG, this disclosure introduces CG configurations in which each timing of CG can support different TB sizes. For example, a first timing of a first CG can be configured to support a first TB size, and a second timing of the first CG can be configured to support a second TB size different from the first TB size.

[0124] Figure 11 This illustrates another communication exchange combined with CG-based uplink transmission according to some embodiments of this disclosure.

[0125] like Figure 11As shown, at operation 1103, base station 1102 may send a CG configuration message for a first CG (CG 1) to UE 1101. The configuration information in the CG configuration message may indicate that a first timing of CG 1 is configured to support a first TB size (TB size 1), and a second timing of CG 1 is configured to support a second TB size (TB size 2) different from the first TB size. For example, odd-numbered timings of CG 1 may be configured to support TB size 1, and even-numbered timings of CG 1 may be configured to support TB size 2.

[0126] When CG 1 is activated, UE 1101 can perform uplink transmissions based on CG 1. At operations 1104 and 1106, the UE can transmit data of size 1 TB during the first and third timings of CG 1, respectively. Similarly, at operations 1105 and 1107, the UE can transmit data of size 2 TB during the second and fourth timings of CG 1, respectively.

[0127] Although CG configuration only supports Figure 11 The example described uses two TB sizes in CG 1, but those skilled in the art can configure a single CG to support larger TB sizes, as well as the mapping between TB sizes and the timing of CGs.

[0128] In some examples, the TB size supported by the CG can be explicitly configured in the configuration information. The configuration information can define different TB sizes and the mapping between TB sizes and CG timings, allowing the UE to perform uplink transmissions based on the configuration information. For example, the configuration information can explicitly indicate TB size 1 for a first timing of the CG and TB size 2 for a second timing of the CG.

[0129] In some other examples, the TB size supported by CG can be configured without explicit mapping.

[0130] Figure 12 This illustrates another communication exchange combined with CG-based uplink transmission according to some embodiments of this disclosure.

[0131] like Figure 12As shown, at operation 1203, base station 1202 may send a CG configuration message for a first CG (CG 1) to UE 1101. The configuration information in the CG configuration message may indicate that each timing of CG 1 supports a set of TB sizes. For example, the configuration information may indicate that a first timing of CG 1 is configured to support a first TB size range (TB size set 1), and a second timing of CG 1 is configured to support a second TB size range different from TB size set 1 (TB size set 2). Alternatively, the configuration information may indicate that a timing of CG 1 is configured to support the same set of TB sizes (e.g., TB size set 1). The TB size set may be indicated using the actual TB size or a TB size index.

[0132] When CG 1 is activated, UE 1201 can perform uplink transmission based on CG 1. Generating uplink data based on multiple data streams may include: generating a transport block that includes the uplink data to be transmitted based on the first CG and uplink control information (UCI) indicating the actual size of the TB, wherein the actual size of the TB is selected from a set of TB sizes indicated in the configuration information.

[0133] At operation 1204, the UE can determine TB size 1 and generate a TB of TB size 1 and uplink control information (UCI) for transmission over the Physical Uplink Shared Channel (PUSCH) in the first timing of CG 1. The TB may include uplink data to be transmitted based on CG1. The UCI may indicate the actual size of the TB transmitted at operation 1204. The actual size of the TB is selected from the set of TB sizes indicated in the configuration information. The network can receive the UCI and TB transmitted in operation 1204, determine the actual TB size based on the UCI, and decode the received TB based on the determined actual TB size. Similarly, at operations 1205 and 1107, the UE can transmit data of TB size 2 in the second timing of CG 1, where TB size 2 is selected from the set of TB sizes configured in the configuration message.

[0134] According to embodiments of this disclosure, a configuration of a CG with variable TB is introduced. For a first service data of a first size to be transmitted every 20ms and a second service data of a second size to be transmitted every 40ms, the CG can be configured to have a periodicity of 20ms, with odd-numbered intervals configured with a first TB size equal to the sum of the first and second sizes, and even-numbered intervals configured with a second TB size equal to the first size. Therefore, when a variable TB size is configured for the CG, different data streams can be transmitted based on the same CG, and the mapping of QoS streams to the CG can be omitted.

[0135] It should also be confirmed that LCH-to-CG mapping, QoS flow-to-CG mapping, mapping of each packet information to CG, and variable TB size configuration within a CG can be applied simultaneously. Those skilled in the art can select one or more configuration methods based on actual QoS requirements.

[0136] Figure 13 An exemplary block diagram of an apparatus for a network according to some embodiments is shown. Figure 13 The device 1300 shown can be used to implement, for example, a combination Figure 2 Method 200 is shown.

[0137] like Figure 13 As shown, the device 1300 includes a QoS information determination unit 1310, a transmission unit 1320, and a receiving unit 1330.

[0138] The QoS information determination unit 1310 can be configured to determine QoS information for multiple data streams with different Quality of Service (QoS) attributes.

[0139] The transmission unit 1320 can be configured to transmit a configuration message generated based on QoS information to a user equipment (UE), wherein the configuration message includes configuration information of at least one configured authorization (CG).

[0140] The receiving unit 1330 can be configured to receive uplink data based on multiple data streams from the UE based on at least one CG.

[0141] Figure 14 An exemplary block diagram of an apparatus for a UE according to some implementation schemes is shown. Figure 14 The device 1400 shown can be used to implement, for example, a combination Figure 3 Method 300 is shown.

[0142] like Figure 14 As shown, the device 1400 includes a receiving unit 1410 and a generating unit 1420.

[0143] The receiving unit 1410 can be configured to receive a configuration message from the network, wherein the configuration message includes configuration information of at least one configured authorization (CG) and is determined based on QoS information of multiple data streams with different quality of service (QoS) attributes.

[0144] The generation unit 1420 can be configured to generate uplink data based on multiple data streams based on at least one CG for transmission to the network.

[0145] Figure 15Exemplary components of device 1500 according to some embodiments are shown. In some embodiments, device 1500 may include at least application circuitry 1502, baseband circuitry 1504, radio frequency (RF) circuitry (shown as RF circuitry 1520), front-end module (FEM) circuitry (shown as FEM circuitry 1530), one or more antennas 1532, and power management circuitry (PMC) (shown as PMC 1534) coupled together as shown. Components of the illustrated device 1500 may be included in a UE or RAN node. In some embodiments, device 1500 may include fewer components (e.g., the RAN node may not utilize application circuitry 1502, but instead include a processor / controller to process IP data received from the EPC). In some embodiments, device 1500 may include additional components such as, for example, memory / storage devices, displays, cameras, sensors, or input / output (I / O) interfaces. In other embodiments, the components described below may be included in more than one device (e.g., the circuitry may be individually included in more than one device for a cloud-RAN (C-RAN) specific implementation).

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

[0147] Baseband circuit 1504 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. Baseband circuit 1504 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of RF circuit 1520 and generate baseband signals for the transmit signal path of RF circuit 1520. Baseband circuit 1504 may interact with application circuitry 1502 to generate and process baseband signals and control the operation of RF circuit 1520. For example, in some embodiments, baseband circuit 1504 may include a third-generation (3G) baseband processor (3G baseband processor 1506), a fourth-generation (4G) baseband processor (4G baseband processor 1508), a fifth-generation (5G) baseband processor (5G baseband processor 1510), or other existing, under development, or future generations of baseband processors 1512 (e.g., second-generation (2G), sixth-generation (6G), etc.). Baseband circuitry 1504 (e.g., one or more baseband processors in a baseband processor suite) can handle various radio control functions capable of communicating with one or more radio networks via RF circuitry 1520. In other embodiments, some or all of the functions of the illustrated baseband processor may be included in a module stored in memory 1518 and executed via a central processing unit ETnit (CPET 1514). Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, RF shifting, etc. In some embodiments, the modulation / demodulation circuitry of baseband circuitry 1504 may include Fast Fourier Transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of baseband circuitry 1504 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity-check (LDPC) encoder / decoder functions. Implementations of modulation / demodulation and encoder / decoder functions are not limited to these examples, and other suitable functions may be included in other embodiments.

[0148] In some embodiments, the baseband circuitry 1504 may include a digital signal processor (DSP), such as one or more audio DSPs 1516. The one or more audio DSPs 1516 may include elements for compression / decompression and echo cancellation, and in other embodiments may include other suitable processing elements. In some embodiments, components of the baseband circuitry may be suitably 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 circuitry 1504 and the application circuitry 1502 may be implemented together, for example, on a system-on-a-chip (SoC).

[0149] In some implementations, baseband circuit 1504 can provide communication compatible with one or more radio technologies. For example, in some implementations, baseband circuit 1504 can support communication with the Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other Wireless Metropolitan Area Networks (WMAN), Wireless Local Area Networks (WLAN), or Wireless Personal Area Networks (WPAN). Implementations in which baseband circuit 1504 is configured to support radio communication with more than one radio protocol may be referred to as multimode baseband circuits.

[0150] RF circuit 1520 enables communication with a wireless network via a non-solid medium using modulated electromagnetic radiation. In various embodiments, RF circuit 1520 may include switches, filters, amplifiers, etc., to facilitate communication with the wireless network. RF circuit 1520 may include a receive signal path that includes circuitry for down-converting the RF signal received from FEM circuit 1530 and providing a baseband signal to baseband circuit 1504. RF circuit 1520 may also include a transmit signal path that includes circuitry for up-converting the baseband signal provided by baseband circuit 1504 and providing an RF output signal for transmission to FEM circuit 1530.

[0151] In some embodiments, the receive signal path of RF circuit 1520 may include mixer circuit 1522, amplifier circuit 1524, and filter circuit 1526. In some embodiments, the transmit signal path of RF circuit 1520 may include filter circuit 1526 and mixer circuit 1522. RF circuit 1520 may also include synthesizer circuit 1528 for synthesizing frequencies used by mixer circuit 1522 for both the receive and transmit signal paths. In some embodiments, mixer circuit 1522 for the receive signal path may be configured to down-convert the RF signal received from FEM circuit 1530 based on the synthesized frequency provided by synthesizer circuit 1528. Amplifier circuit 1524 may be configured to amplify the down-converted signal, and filter circuit 1526 may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuit 1504 for further processing. In some implementations, although not required, the output baseband signal may be a zero-frequency baseband signal. In some implementations, the mixer circuit 1522 for the received signal path may include a passive mixer, but the scope of the implementations is not limited in this respect.

[0152] In some implementations, the mixer circuit 1522 of the transmission signal path can be configured to up-convert the input baseband signal based on the synthesized frequency provided by the synthesizer circuit 1528 to generate an RF output signal for the FEM circuit 1530. The baseband signal can be provided by the baseband circuit 1504 and can be filtered by the filter circuit 1526.

[0153] In some embodiments, the mixer circuit 1522 for the receive signal path and the mixer circuit 1522 for the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuit 1522 for the receive signal path and the mixer circuit 1522 for 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 1522 for the receive signal path and the mixer circuit 1522 may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuit 1522 for the receive signal path and the mixer circuit 1522 for the transmit signal path may be configured for superheterodyne operation.

[0154] 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, the RF circuit 1520 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and the baseband circuit 1504 may include a digital baseband interface for communicating with the RF circuit 1520.

[0155] In some dual-mode implementations, separate radio IC circuits can be provided to process signals for each spectrum, but the scope of the implementation is not limited in this respect.

[0156] In some implementations, synthesizer circuit 1528 may be a fractional N synthesizer or a fractional N / N+1 synthesizer, but the scope of implementations is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 1528 may be a Δ-Σ synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0157] Synthesizer circuit 1528 can be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 1522 of RF circuit 1520. In some embodiments, synthesizer circuit 1528 can be a fractional N / N+1 synthesizer.

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

[0159] The synthesizer circuit 1528 of the RF circuit 1520 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 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 set of D-type flip-flops. In these embodiments, the delay elements 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. Thus, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

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

[0161] FEM circuit 1530 may include a receive signal path, which may include circuitry configured to operate on RF signals received from one or more antennas 1532, amplify the received signals, and provide an amplified version of the received signals to RF circuit 1520 for further processing. FEM circuit 1530 may also include a transmit signal path, which may include circuitry configured to amplify transmit signals provided by RF circuit 1520 for transmission by one or more of the one or more antennas 1532. In various embodiments, amplification via the transmit signal path or the receive signal path may be performed only in RF circuit 1520, only in FEM circuit 1530, or in both RF circuit 1520 and FEM circuit 1530.

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

[0163] In some implementations, the PMC 1534 manages the power supplied to the baseband circuitry 1504. Specifically, the PMC 1534 controls power selection, voltage scaling, battery charging, or DC-DC conversion. The PMC 1534 is typically included when the device 1500 is capable of being battery powered, for example, when the device 1500 is included in an EGE. The PMC 1534 can improve power conversion efficiency while providing the desired implementation size and thermal characteristics.

[0164] Figure 15 A PMC 1534 is shown that is coupled only to the baseband circuit 1504. However, in other embodiments, the PMC 1534 may additionally or alternatively be coupled to other components (such as, but not limited to, the application circuit 1502, the RF circuit 1520, or the FEM circuit 1530) and perform similar power management operations for these components.

[0165] In some implementations, the PMC 1534 may control various power-saving mechanisms of the device 1500 or otherwise become part of such power-saving mechanisms. For example, if the device 1500 is in an RRC connected state, where it remains connected to the RAN node because it expects to receive communication soon, the device may enter a state called Discontinuous Receive Mode (DRX) after an inactive period. During this state, the device 1500 may be powered down for short intervals, thereby saving power.

[0166] If there is no data traffic activity during the extended period, device 1500 may transition to an RRC idle state, in which the device disconnects from the network and does not perform operations such as channel quality feedback or handover. Device 1500 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 off again. Device 1500 cannot receive data in this state, and in order to receive data, the device transitions back to the RRC connected state.

[0167] An additional power-saving mode allows the device to be unavailable from the network for periods exceeding the paging interval (ranging from seconds to hours). During this time, the device is completely unconnected to the network and can be completely powered off. Any data sent during this period will incur significant latency, which is assumed to be acceptable.

[0168] The processors of application circuit 1502 and baseband circuit 1504 are elements that can be used to execute one or more instances of the protocol stack. For example, the processor of baseband circuit 1504 can be used alone or in combination to execute layer 3, layer 2, or layer 1 functions, while the processor of application circuit 1502 can utilize data received from these layers (e.g., packet data) and further execute layer 4 functions (e.g., Transport Communication Protocol (TCP) and User Datagram Protocol (UDP) layers). As mentioned herein, layer 3 may include the Radio Resource Control (RRC) layer, which will be described in further detail below. As mentioned herein, layer 2 may include the Media Access Control (MAC) layer, the Radio Link Control (RLC) layer, and the Packet Data Convergence Protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, layer 1 may include the physical (PHY) layer of the UE / RAN node, which will be described in further detail below.

[0169] Figure 16 An exemplary interface 1600 of a baseband circuit according to some embodiments is shown. As discussed above, Figure 15 The baseband circuit 1504 may include a 3G baseband processor 1506, a 4G baseband processor 1508, a 5G baseband processor 1510, other baseband processors 1512, a CPU 1514, and a memory 1518 used by the processors. As shown, each processor may include a corresponding memory interface 1602 for sending / receiving data to / from the memory 1518.

[0170] Baseband circuit 1504 may further include: one or more interfaces for communicatively coupling to other circuits / devices, such as memory interface 1604 (e.g., an interface for sending / receiving data to / from a memory external to baseband circuit 1504); application circuit interface 1606 (e.g., for sending / receiving data to / from a memory external to baseband circuit 1504); and application circuit interface 1606 (e.g., for sending / receiving data to / from a memory external to baseband circuit 1504). Figure 15 Application circuit 1502 (interface for sending / receiving data); RF circuit interface 1608 (e.g., for sending / receiving data to / from...). Figure 15 The RF circuit 1320 is an interface for transmitting / receiving data; the wireless hardware connection interface 1610 (e.g., for transmitting / receiving data to / from near field communication (NFC) components, Components (e.g.) LowEnergy) Interfaces for sending / receiving data to / from components and other communication components; and power management interface 1612 (e.g., an interface for sending / receiving power or control signals to / from PMC 1534).

[0171] Figure 17 This is a block diagram illustrating component 1700, according to some exemplary embodiments, capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any or more methods discussed herein. Specifically, Figure 17 A schematic diagram of hardware resource 1702 is shown, which includes one or more processors 1712 (or processor cores), one or more memory / storage devices 1718, and one or more communication resources 1720, each of which is communicatively coupled via bus 1722. In an implementation utilizing node virtualization (e.g., NFV), an executable hypervisor 1704 provides an execution environment for one or more network slices / subslices to utilize hardware resource 1702.

[0172] Processor 1712 (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 1714 and processor 1716.

[0173] The memory / storage device 1718 may include main memory, disk storage devices, or any suitable combination thereof. The memory / storage device 1718 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 devices, etc.

[0174] Communication resource 1720 may include interconnect or network interface components or other suitable devices for communicating with one or more peripheral devices 1706 or one or more databases 1708 via network 1712. For example, communication resource 1720 may include wired communication components (e.g., for coupling via Universal Serial Bus (USB), cellular communication components, NFC components, etc. Components (e.g.) (low power consumption) Components and other communication components.

[0175] Instruction 1724 may include software, a program, application, app, application, or other executable code for causing at least one processor in processor 1712 to perform one or more of the methods discussed herein. Instruction 1724 may reside wholly or partially within processor 1712 (e.g., within the processor's cache memory), at least one of memory / storage device 1718, or any suitable combination thereof. Furthermore, any portion of instruction 1724 may be transferred to hardware resource 1702 from any combination of peripheral device 1706 or database 1708. Therefore, the memory of processor 1712, memory / storage device 1718, peripheral device 1706, and database 1708 are examples of computer-readable and machine-readable media.

[0176] 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 as described in the Examples section below. For example, the baseband circuitry 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 below. As another example, circuitry 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 Examples section below.

[0177] Figure 18 The architecture of a system 1800 of a network according to some embodiments is shown. System 1800 includes one or more user equipment (UEs), shown in this example as UE 1802 and UE 1804. UE 1802 and UE 1804 are shown as smartphones (e.g., handheld touchscreen mobile computing devices that can connect to one or more cellular networks), but it may also include any mobile or non-mobile computing device, such as a personal data assistant (PDA), pager, laptop computer, desktop computer, wireless handheld terminal, or any computing device that includes a wireless communication interface.

[0178] In some implementations, either UE 1802 or UE 1804 may include an Internet of Things (IoT) UE, which may include a network access layer designed to utilize low-power IoT applications with short-lived UE connections. The IoT UE may exchange data with an MTC server or device via technologies such as machine-to-machine (M2M) or machine-type communication (MTC), through a Public Land Mobile Network (PLMN), Proximity-Based Service (ProSe) or Device-to-Device (D2D) communication, sensor networks, or an IoT network. M2M or MTC data exchange may be machine-initiated data exchange. An 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., keeping track of activity messages, status updates, etc.) to facilitate connectivity within the IoT network.

[0179] UE 1802 and UE 1804 can be configured to connect (e.g., communicatively coupled) to a radio access network (RAN) (shown as RAN 1806). RAN 1806 can be, for example, an Evolved Universal Mobile Telecommunications System (ETMTS) Terrestrial Radio Access Network (E-UTRAN), a Next Generation RAN (NG RAN), or some other type of RAN. UE 1802 and UE 1804 utilize connection 1808 and connection 1810, respectively, each of which includes a physical communication interface or layer (discussed in further detail below); in this example, connection 1808 and connection 1810 are shown as air interfaces for communicative coupling and are compatible with cellular communication protocols such as Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA) network protocols, Push-to-Talk (PTT) protocols, Cellular PTT protocols (POC), Universal Mobile Telecommunications System (UMTS) protocols, 3GPP Long Term Evolution (LTE) protocols, 5G protocols, New Radio (NR) protocols, etc.

[0180] In this implementation, UE 1802 and UE 1804 can also directly exchange communication data via ProSe interface 1812. ProSe interface 1812 may alternatively be referred to as a sidelink interface including one or more logical channels, including but not limited to the Physical Sidelink Control Channel (PSCCH), Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Discovery Channel (PSDCH), and Physical Sidelink Broadcast Channel (PSBCH).

[0181] UE 1804 is shown configured to access an access point (AP) (shown as AP 1814) via connection 1816. Connection 1816 can include local wireless connectivity, such as a connection consistent with any IEEE 802.11 protocol, while AP 1814 will include Wireless Fidelity. Router. In this example, AP 1814 can connect to the Internet without connecting to the core network of the wireless system (described in further detail below).

[0182] RAN 1806 can include one or more access nodes that enable connections 1808 and 1810. These access nodes (ANs) can be referred to as base stations (BS), node Bs, evolved Node Bs (eNBs), next-generation Node Bs (gNBs), RAN nodes, etc., and can include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). RAN 1806 can include one or more RAN nodes for providing macro cells, such as macro RAN node 1818, and one or more RAN nodes for providing femtocells or picocells (e.g., cells with smaller coverage area, smaller user capacity, or higher bandwidth compared to macro cells), such as low-power (LP) RAN nodes (e.g., LP RAN node 1820).

[0183] Either macro RAN node 1818 or LP RAN node 1820 can terminate the air interface protocol and can be the first point of contact for UE 1802 and UE 1804. In some implementations, either macro RAN node 1818 or LP RAN node 1820 can fulfill various logical functions of RAN 1806, including but not limited to the functions of the Radio Network Controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management, data packet scheduling, and mobility management.

[0184] According to some implementations, EGE 1802 and EGE 1804 can be configured to communicate with each other or with either macro RAN node 1818 or LP RAN node 1820 on a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals, based on various communication technologies, such as, but not limited to, orthogonal frequency division multiple access (OFDMA) communication technology (e.g., for downlink communication) or single-carrier frequency division multiple access (SC-FDMA) communication technology (e.g., for uplink and ProSe or sidelink communication), but the scope of the implementation is not limited in this respect. OFDM signals may include multiple orthogonal subcarriers.

[0185] In some implementations, the downlink resource grid can be used for downlink transmissions from either macro RAN node 1818 or LP RAN node 1820 to UE 1802 and UE 1804, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, which represents the physical resources in the downlink within each time slot. This time-frequency plane representation is common practice for OFDM systems, making radio resource allocation intuitive. Each column and row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid comprises multiple resource blocks that describe the mapping of certain physical channels to resource elements. Each resource block comprises a set of resource elements; in the frequency domain, this can represent the minimum amount of resources currently available for allocation. Such resource blocks are used to transmit several different physical downlink channels.

[0186] The Physical Downlink Shared Channel (PDSCH) carries user data and higher-layer signaling to UE 1802 and UE 1804. The Physical Downlink Control Channel (PDCCH) carries information such as transmission format and resource allocation related to the PDSCH channel. It also notifies UE 1802 and UE 1804 of transmission format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (allocating control and shared channel resource blocks to UE 1804 within the cell) can be performed at either macro RAN node 1818 or LP RAN node 1820 based on channel quality information fed back from either UE 1802 or UE 1804. Downlink resource allocation information can be transmitted on the PDCCH used (e.g., allocated to) each of UE 1802 and UE 1804.

[0187] PDCCH can use Control Channel Elements (CCEs) to transmit control information. Before being mapped to resource elements, the complex-valued symbols of the PDCCH are first organized into quadruplets, which are then arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to a set of four physical resource elements (REGs) of nine. Four Quadrature Phase Shift Keying (QPSK) symbols can be mapped to each REG. Depending on the size of the Downlink Control Information (DCI) and channel conditions, one or more CCEs can be used to transmit the PDCCH. In LTE, four or more different PDCCH formats with different numbers of CCEs (e.g., aggregation levels, L = 1, 2, 4, or 8) can exist.

[0188] Some implementations may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some implementations may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission. EPDCCH may be transmitted using one or more enhanced control channel elements (ECCEs). Similarly, each ECCE may correspond to a set of nine physical resource elements, referred to as an enhanced resource element group (EREG). In some cases, an ECCE may have a different number of EREGs.

[0189] RAN 1806 is communicatively coupled to the core network (CN) (shown as CN 1828) via S1 interface 1822. In this implementation, CN 1828 can be an evolved packet core (EPC) network, a next-generation packet core (NPC) network, or some other type of CN. In this implementation, S1 interface 1822 is divided into two parts: S1-U interface 1824, which carries traffic data between macro RAN node 1818 and LP RAN node 1820 and the serving gateway (S-GW) (shown as S-GW 1832); and S1-Mobility Management Entity (MME) interface (shown as S1-MME interface 1826), which is the signaling interface between macro RAN node 1818 and LP RAN node 1820 and MME 1830.

[0190] In this implementation, CN 1828 includes an MME 1830, an S-GW 1832, a Packet Data Network (PDN) Gateway (P-GW) (shown as P-GW 1834), and a Home Subscriber Server (HSS) (shown as HSS 1836). The MME 1830 may functionally resemble the control plane of a legacy General Packet Radio Service (GPRS) Support Node (SGSN). The MME 1830 manages access-related mobility aspects such as gateway selection and tracking area list management. The HSS 1836 may include a database for network users, containing subscription-related information for supporting the handling of communication sessions for network entities. Depending on the number of mobile subscribers, equipment capacity, network organization, etc., CN 1828 may include one or more HSS 1836s. For example, the HSS 1836 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location correlation, etc.

[0191] The S-GW 1832 can terminate the S1 interface 322 toward RAN 1806 and route data packets between RAN 1806 and CN 1828. Furthermore, the S-GW 1832 can serve as a local mobility anchor for inter-RAN node handover and can also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, billing, and enforcement of certain policies.

[0192] The P-GW 1834 can terminate the SGi interface toward the PDN. The P-GW 1834 can route data packets between the CN 1828 (e.g., an EPC network) and external networks, such as a network including an application server 1842 (alternatively referred to as an application function (AF)), via an Internet Protocol (IP) interface (shown as IP communication interface 1838). Generally, the application server 1842 can be an element that provides IP bearer resources for applications using the core network (e.g., ETMTS Packet Service (PS) domain, LTE PS data service, etc.). In this embodiment, the P-GW 1834 is shown communicatively coupled to the application server 1842 via the IP communication interface 1838. The application server 1842 can also be configured to support one or more communication services (e.g., Voice over Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for UE 1802 and UE 1804 via the CN 1828.

[0193] The P-GW 1834 can also serve as a node for policy enforcement and charging data collection. The Policy and Charging Enforcement Function (PCRF) (represented as PCRF 1840) is a policy and charging control element of CN 1828. In non-roaming scenarios, a single PCRF may exist within the domestic public land mobile network (HPLMN) associated with the ETE's Internet Protocol Connectivity Access Network (IP-CAN) session. In roaming scenarios with local traffic breaches, two PCRFs may exist associated with the UE's IP-CAN session: a domestic PCRF within the HPLMN (H-PCRF) and a visited PCRF within the visited public land mobile network (VPLMN) (V-PCRF). PCRF 1840 can be communicatively coupled to the application server 1842 via the P-GW 1834. The application server 1842 can signal PCRF 1840 to indicate new service flows and select appropriate Quality of Service (QoS) and charging parameters. PCRF 1840 can provide the rule as a policy and charging enforcement function (PCEF) (not shown) with an appropriate communication flow template (TFT) and QoS category identifier (QCI), which begins with QoS and charging specified by application server 1842.

[0194] Additional Examples

[0195] 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 as described in the Examples section below. For example, the baseband circuitry 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 below. As another example, circuitry 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 Examples section below.

[0196] The following examples relate to other implementation schemes.

[0197] Example 1 is a method for a network, the method comprising: determining QoS information of multiple data streams having different Quality of Service (QoS) attributes; transmitting a configuration message generated based on the QoS information to a user equipment (UE), wherein the configuration message includes configuration information of at least one configured authorization (CG); and receiving uplink data based on the multiple data streams from the UE based on the at least one CG.

[0198] Example 2 is the method according to Example 1, wherein multiple data streams include a first data stream and a second data stream, and QoS information indicates that the first data stream is mapped to a first logical channel (LCH), and the second data stream is mapped to a second LCH different from the first LCH, and wherein at least one CG includes a first CG and a second CG different from the first CG, and configuration information indicates that the first LCH is configured to transmit based on the first CG, and the second LCH is configured to transmit based on the second CG.

[0199] Example 3 is the method according to Example 1, wherein multiple data streams include a first data stream and a second data stream, and QoS information indicates that the first data stream is mapped to a first QoS stream and the second data stream is mapped to a second QoS stream, and wherein at least one CG includes a first CG and a second CG different from the first CG, and configuration information indicates that the first QoS stream is configured to be transmitted based on the first CG and the second QoS stream is configured to be transmitted based on the second CG.

[0200] Example 4 is the method according to Example 3, wherein the plurality of data streams further includes a third data stream, and QoS information indicates that the third data stream is mapped to a third QoS stream different from the first QoS stream, and wherein the third QoS stream is configured to be transmitted based on the first CG.

[0201] Example 5 is the method according to Example 3 or 4, wherein QoS information indicates that the first QoS stream and the second QoS stream are mapped to the same logical channel (LCH).

[0202] Example 6 is a method according to any one of Examples 3-5, the method further comprising: receiving a buffer status report (BSR) from the UE, wherein the BSR includes a first buffer size for a first QoS stream and a second buffer size for a second QoS stream.

[0203] Example 7 is the method according to Example 1, wherein a plurality of data streams include a first data stream and a second data stream, and QoS information indicates that the first data stream is mapped to a first Internet Protocol (IP) stream, and the second data stream is mapped to a second IP stream different from the first IP stream, and wherein at least one CG includes a first CG and a second CG different from the first CG, and configuration information indicates that the first IP stream is configured to be transmitted based on the first CG, and the second IP stream is configured to be transmitted based on the second CG.

[0204] Example 8 is the method according to Example 7, wherein the QoS information further indicates that the first IP flow and the second IP flow are mapped to the same QoS flow.

[0205] Example 9 is a method according to any one of Examples 1-8, wherein a first timing of the first CG is configured to support a first transport block (TB) size, and a second timing of the first CG is configured to support a second TB size different from the first TB size.

[0206] Example 10 is the method according to Example 9, wherein the configuration information explicitly indicates the first TB size at a first time and the second TB size at a second time.

[0207] Example 11 is the method according to Example 9, wherein the configuration information indicates that each timing of the first CG supports a TB-sized set.

[0208] Example 12 is the method according to Example 11, wherein receiving uplink data based on multiple data streams from a UE based on at least one CG includes: receiving a TB transmitted from the UE based on a first CG, the TB including uplink data and uplink control information (UCI) indicating the actual size of the TB, wherein the actual size of the TB is selected from a set of TBs indicated in configuration information; determining the actual size of the TB based on the UCI; and decoding the TB based on the actual size.

[0209] Example 13 is a method according to any one of Examples 1-12, wherein determining the QoS information of multiple data streams with different Quality of Service (QoS) attributes includes: receiving suggestion information about the QoS information of the multiple data streams from the UE; and determining the QoS information of the multiple data streams based on the suggestion information.

[0210] Example 14 is the method according to Example 13, wherein the suggestion information is received by the core network (CN) or a base station.

[0211] Example 15 is a method according to any one of Examples 1-12, wherein determining QoS information for multiple data streams with different Quality of Service (QoS) attributes includes: the core network (CN) determining suggested information about the QoS information of the multiple data streams via an application server; and notifying the base station about the suggested information.

[0212] Example 16 is a method for a user equipment (UE) comprising: receiving a configuration message from a network, wherein the configuration message includes configuration information of at least one configured authorization (CG) and is determined based on QoS information of multiple data streams having different quality of service (QoS) attributes; and generating uplink data based on the multiple data streams for transmission to the network based on at least one CG.

[0213] Example 17 is the method according to Example 16, wherein a plurality of data streams include a first data stream and a second data stream, and QoS information indicates that the first data stream is mapped to a first logical channel (LCH), and the second data stream is mapped to a second LCH different from the first LCH, and wherein at least one CG includes a first CG and a second CG different from the first CG, and configuration information indicates that the first LCH is configured to transmit based on the first CG, and the second LCH is configured to transmit based on the second CG.

[0214] Example 18 is the method according to Example 16, wherein a plurality of data streams include a first data stream and a second data stream, and QoS information indicates that the first data stream is mapped to a first QoS stream and the second data stream is mapped to a second QoS stream, and wherein at least one CG includes a first CG and a second CG different from the first CG, and configuration information indicates that the first QoS stream is configured to be transmitted based on the first CG and the second QoS stream is configured to be transmitted based on the second CG.

[0215] Example 19 is the method according to Example 18, wherein the plurality of data streams further includes a third data stream, and QoS information indicates that the third data stream is mapped to a third QoS stream different from the first QoS stream, and wherein the third QoS stream is configured to be transmitted based on the first CG.

[0216] Example 20 is the method according to Example 18 or 19, wherein QoS information indicates that the first QoS stream and the second QoS stream are mapped to the same logical channel (LCH).

[0217] Example 21 is a method according to any one of Examples 16-20, the method further comprising: generating a buffer status report (BSR) for transmission to the network, wherein the BSR includes a first buffer size for a first QoS flow and a second buffer size for a second QoS flow.

[0218] Example 22 is the method according to Example 16, wherein a plurality of data streams include a first data stream and a second data stream, and QoS information indicates that the first data stream is mapped to a first Internet Protocol (IP) stream, and the second data stream is mapped to a second IP stream different from the first IP stream, and wherein at least one CG includes a first CG and a second CG different from the first CG, and configuration information indicates that the first IP stream is configured to be transmitted based on the first CG, and the second IP stream is configured to be transmitted based on the second CG.

[0219] Example 23 is the method according to Example 22, wherein the QoS information further indicates that the first IP flow and the second IP flow are mapped to the same QoS flow.

[0220] Example 24 is a method according to any one of Examples 16-23, wherein a first timing of the first CG is configured to support a first transport block (TB) size, and a second timing of the first CG is configured to support a second TB size different from the first TB size.

[0221] Example 25 is the method according to Example 24, wherein the configuration information explicitly indicates the first TB size at a first time and the second TB size at a second time.

[0222] Example 26 is the method according to Example 24, wherein the configuration information indicates that each timing of the first CG supports a TB-sized set.

[0223] Example 27 is the method according to Example 26, wherein generating uplink data based on multiple data streams for transmission to the network based on at least one CG includes: generating uplink data to be transmitted based on a first CG and a TB of uplink control information (UCI) indicating the actual size of the transport block, wherein the actual size of the TB is selected from a set of TB sizes indicated in the configuration information.

[0224] Example 28 is a method according to any one of Examples 16-27, the method further comprising: generating suggestion information about QoS information of multiple data streams for transmission to the network.

[0225] Example 29 is the method according to Example 28, wherein the recommendation information is transmitted to the core network (CN) or base station.

[0226] Example 30 is an apparatus for a network, the apparatus comprising: one or more processors configured to perform the steps of the method according to any one of Examples 1-15.

[0227] Example 31 is an apparatus for a user equipment (UE) comprising: one or more processors configured to perform the steps of the method according to any one of Examples 16-29.

[0228] Example 32 is a computer-readable medium having stored thereon computer programs that, when executed by one or more processors of the device, cause the device to perform the steps of the method according to any one of Examples 1-29.

[0229] Example 33 is a computer program product comprising a computer program that, when executed by one or more processors of a device, causes the device to perform the steps of the method according to any one of Examples 1-29.

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

[0231] It should be recognized that the systems described herein include descriptions of specific implementations. These implementations may be combined into a single system, partially integrated into other systems, divided into multiple systems, or otherwise partitioned or combined. Furthermore, it is conceivable to use parameters / attributes / aspects, etc., of one implementation in another implementation. For clarity, these parameters / attributes / aspects, etc., are described only in one or more implementations, and it should be recognized that unless specifically stated herein, these parameters / attributes / aspects, etc., may be combined with or replace parameters / attributes, etc., of another implementation.

[0232] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting 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 authorized use should be clearly explained to users.

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

Claims

1. A method for communication, comprising: Determine the QoS information of multiple data streams with different QoS attributes; Processing suggestion information received from a user equipment (UE), the suggestion information includes a first suggested traffic pattern mapped to a first QoS flow identifier to a logical channel, i.e., QFI to LCH, and a second suggested traffic pattern mapped to a second QFI to LCH. A configuration message is generated based on the QoS information, wherein the configuration message is sent to the UE and includes configuration information for at least one configured authorized CG; as well as Process uplink data received from the UE based on the at least one CG.

2. The method according to claim 1, wherein: The plurality of data streams includes a first data stream and a second data stream, and the QoS information indicates that the first data stream is mapped to a first logical channel (LCH), and the second data stream is mapped to a second LCH different from the first LCH; and The at least one CG includes a first CG and a second CG different from the first CG, and the configuration information indicates that the first LCH is configured to transmit based on the first CG, and the second LCH is configured to transmit based on the second CG.

3. The method according to claim 1, wherein: The plurality of data streams includes a first data stream and a second data stream, and the QoS information indicates that the first data stream is mapped to a first QoS stream, and the second data stream is mapped to a second QoS stream; The at least one CG includes a first CG and a second CG different from the first CG, and the configuration information indicates that the first QoS flow is configured to be transmitted based on the first CG, and the second QoS flow is configured to be transmitted based on the second CG; and The QoS information indicates that the first QoS stream and the second QoS stream are mapped to the same logical channel (LCH).

4. The method according to claim 3, wherein: The plurality of data streams also includes a third data stream, and the QoS information indicates that the third data stream is mapped to a third QoS stream different from the first QoS stream; and The third QoS stream is configured to be transmitted based on the first CG.

5. The method according to claim 3, further comprising: Process the buffer status report (BSR) received from the UE, wherein the BSR includes a first buffer size for the first QoS stream and a second buffer size for the second QoS stream.

6. The method according to claim 1, wherein: The plurality of data streams includes a first data stream and a second data stream, and the QoS information indicates that the first data stream is mapped to a first Internet Protocol (IP) stream, and the second data stream is mapped to a second IP stream different from the first IP stream; and The at least one CG includes a first CG and a second CG different from the first CG, and the configuration information indicates that the first IP stream is configured to be transmitted based on the first CG, and the second IP stream is configured to be transmitted based on the second CG.

7. The method according to any one of claims 1-6, wherein: The first timing of the first CG is configured to support a first transport block size (TB), and the second timing of the first CG is configured to support a second TB size different from the first TB size; and The configuration information explicitly indicates the first TB size for the first time period and the second TB size for the second time period.

8. The method according to any one of claims 1-6, wherein: The first timing of the first CG is configured to support a first transport block (TB) size, and the second timing of the first CG is configured to support a second TB size different from the first TB size; The configuration information indicates that each timing of the first CG supports a TB-sized set; and The processing based on the uplink data received from the UE by the at least one CG includes: Processing TB received from the UE, including the uplink data and uplink control information UCI indicating the actual size of the TB based on the first CG, wherein the actual size of the TB is selected from the set of TB sizes indicated in the configuration information; The actual size of the TB is determined based on the UCI; and The TB is decoded based on the actual size.

9. The method according to any one of claims 1-6, further comprising: The QoS information of the plurality of data streams is determined based on the suggested information.

10. One or more computer-readable media having instructions that, when executed, cause a user-equipped UE to perform the following operations: Send suggestion information to the network, the suggestion information including a first suggested traffic pattern for mapping a first Quality of Service (QoS) flow identifier to a logical channel, i.e., QFI to LCH, and a second suggested traffic pattern for mapping a second QFI to LCH. Process a configuration message received from the network, wherein the configuration message includes configuration information for at least one configured authorized CG, and the configuration message is determined based on QoS information of multiple data streams with different Quality of Service (QoS) attributes; and Uplink data is generated for the plurality of data streams for transmission to the network based on the at least one CG.

11. One or more computer-readable media according to claim 10, wherein: The plurality of data streams includes a first data stream and a second data stream, and the QoS information indicates that the first data stream is mapped to a first logical channel (LCH), and the second data stream is mapped to a second LCH different from the first LCH; and The at least one CG includes a first CG and a second CG different from the first CG, and the configuration information indicates that the first LCH is configured to transmit based on the first CG, and the second LCH is configured to transmit based on the second CG.

12. One or more computer-readable media according to claim 10, wherein: The plurality of data streams includes a first data stream and a second data stream, and the QoS information indicates that the first data stream is mapped to a first QoS stream, and the second data stream is mapped to a second QoS stream; and The at least one CG includes a first CG and a second CG different from the first CG, and the configuration information indicates that the first QoS stream is configured to be transmitted based on the first CG, and the second QoS stream is configured to be transmitted based on the second CG.

13. One or more computer-readable media according to claim 12, wherein: The plurality of data streams also includes a third data stream, and the QoS information indicates that the third data stream is mapped to a third QoS stream different from the first QoS stream; and The third QoS stream is configured to be transmitted based on the first CG.

14. One or more computer-readable media according to claim 12, wherein the QoS information indicates that the first QoS stream and the second QoS stream are mapped to the same logical channel LCH.

15. One or more computer-readable media according to claim 12, wherein the instructions, when executed, further cause the UE to perform the following operations: A buffer status report (BSR) is generated for transmission to the network, wherein the BSR includes a first buffer size for the first QoS flow and a second buffer size for the second QoS flow.

16. One or more computer-readable media according to claim 10, wherein: The plurality of data streams includes a first data stream and a second data stream, and the QoS information indicates that the first data stream is mapped to a first Internet Protocol (IP) stream, and the second data stream is mapped to a second IP stream different from the first IP stream; The at least one CG includes a first CG and a second CG different from the first CG, and the configuration information indicates that the first IP stream is configured to be transmitted based on the first CG, and the second IP stream is configured to be transmitted based on the second CG; and The QoS information further indicates that the first IP flow and the second IP flow are mapped to the same QoS flow.

17. One or more computer-readable media according to any one of claims 10-16, wherein a first timing of the first CG is configured to support a first transport block (TB) size, and a second timing of the first CG is configured to support a second TB size different from the first TB size.

18. One or more computer-readable media of claim 17, wherein the configuration information explicitly indicates the first TB size for the first time period and the second TB size for the second time period.

Images