Processing mapped 5G system (5GS) quality of service (QoS) information in evolved packet system (EPS)

Aspects of the present disclosure provide apparatus, methods, processing systems, and computer readable mediums for updating QoS configurations at a user equipment (UE). An example method generally includes receiving, from a network entity, quality of service (QoS) information, a QoS identifier associated with the QoS information, and a bearer context associated with the QoS information in one of a modify bearer context request message, an activate default bearer context request message, or an activate dedicated bearer context request message; and updating a QoS configuration using the QoS information based on whether the UE is already configured with QoS information associated with the QoS identifier for a bearer context different from the bearer context associated with the QoS information received in the modify bearer context request message, activate default bearer context request message, or activate dedicated bearer context request message.

TECHNICAL FIELD

Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for updating quality of service (QoS) parameters in an environment where devices using a first radio access technology and devices using a second radio access technology coexist.

BACKGROUND

A control resource set (CORESET) for systems, such as an NR and LTE systems, may comprise one or more control resource (e.g., time and frequency resources) sets, configured for conveying PDCCH, within the system bandwidth. Within each CORESET, one or more search spaces (e.g., common search space (CSS), UE-specific search space (USS), etc.) may be defined for a given UE.

SUMMARY

One innovative aspect of the subject matter described in this disclosure can be implemented in a method for wireless communication by a user equipment (UE). The method generally includes receiving, from a network entity, quality of service (QoS) information, a QoS identifier associated with the QoS information, and a bearer context associated with the QoS information in one of a modify bearer context request message, an activate default bearer context request message, or an activate dedicated bearer context request message; and updating a QoS configuration using the QoS information based on whether the UE is already configured with QoS information associated with the QoS identifier for a different bearer context than the bearer context associated with the QoS information.

Aspects of the present disclosure provide means for, apparatus, processors, and computer-readable mediums for performing the methods described herein.

To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the appended drawings set forth in detail some illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.

DETAILED DESCRIPTION

Aspects of the present disclosure provide apparatus, methods, processing systems, and computer readable mediums for updating quality of service (QoS) information in an environment where devices using a first radio access technology and devices using a second radio access technology coexist.

FIG. 1illustrates an example wireless communication network100in which aspects of the present disclosure may be performed. For example, as shown inFIG. 1, UE120amay include a quality of service (QoS) parameter updating module122that may be configured to perform (or cause UE120ato perform) operations400ofFIG. 4. Similarly, a base station110amay include a QoS parameter configuration module112that may be configured to perform (or cause the base station110ato perform) operations to transmit QoS configuration information to the UE.

NR access (for example, 5G NR) may support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (for example, 80 MHz or beyond), millimeter wave (mmWave) targeting high carrier frequency (for example, 25 GHz or beyond), massive machine type communications MTC (mMTC) targeting non-backward compatible MTC techniques, or mission critical services targeting ultra-reliable low-latency communications (URLLC). These services may include latency and reliability requirements. These services may also have different transmission time intervals (TTI) to meet respective quality of service (QoS) requirements. In addition, these services may co-exist in the same time-domain resource (for example, a slot or subframe) or frequency-domain resource (for example, component carrier).

Wireless communication network100may also include relay stations (for example, relay station110r), also referred to as relays or the like, that receive a transmission of data or other information from an upstream station (for example, a BS110aor a UE120r) and sends a transmission of the data or other information to a downstream station (for example, a UE120or a BS110), or that relays transmissions between UEs120, to facilitate communication between devices.

A network controller130may couple to a set of BSs110and provide coordination and control for these BSs110. The network controller130may communicate with the BSs110via a backhaul. The BSs110may also communicate with one another (for example, directly or indirectly) via wireless or wireline backhaul.

FIG. 2shows a block diagram illustrating an example base station (BS) and an example user equipment (UE) in accordance with some aspects of the present disclosure.

At the BS110, a transmit processor220may receive data from a data source212and control information from a controller/processor240. The control information may be for the physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical hybrid ARQ indicator channel (PHICH), physical downlink control channel (PDCCH), group common PDCCH (GC PDCCH), etc. The data may be for the physical downlink shared channel (PDSCH), etc. The processor220may process (for example, encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The transmit processor220may also generate reference symbols, such as for the primary synchronization signal (PSS), secondary synchronization signal (SSS), and cell-specific reference signal (CRS). A transmit (TX) multiple-input multiple-output (MIMO) processor230may perform spatial processing (for example, precoding) on the data symbols, the control symbols, or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs)232a-232t. Each modulator232may process a respective output symbol stream (for example, for OFDM, etc.) to obtain an output sample stream. Each modulator may further process (for example, convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from modulators232a-232tmay be transmitted via the antennas234a-234t, respectively.

The memories242and282may store data and program codes for BS110and UE120, respectively. A scheduler244may schedule UEs for data transmission on the downlink or uplink.

The controller/processor280or other processors and modules at the UE120may perform or direct the execution of processes for the techniques described herein. As shown inFIG. 2, the controller/processor280of the UE120has a QoS parameter updating module122that may be configured to perform operations400ofFIG. 4, as discussed in further detail below. The controller/processor240of the base station110includes a QoS parameter configuration module that may be configured to transmit QoS configuration messages to a UE for processing. Although shown at the Controller/Processor, other components of the UE or BS may be used to perform the operations described herein.

FIG. 3is a diagram showing an example of a frame format300for NR. The transmission timeline for each of the downlink and uplink may be partitioned into units of radio frames. Each radio frame may have a predetermined duration (e.g., 10 ms) and may be partitioned into 10 subframes, each of 1 ms, with indices of 0 through 9. Each subframe may include a variable number of slots depending on the subcarrier spacing. Each slot may include a variable number of symbol periods (e.g., 7 or 14 symbols) depending on the subcarrier spacing. The symbol periods in each slot may be assigned indices. A mini-slot, which may be referred to as a sub-slot structure, refers to a transmit time interval having a duration less than a slot (e.g., 2, 3, or 4 symbols).

In NR, a synchronization signal (SS) block is transmitted. The SS block includes a PSS, a SSS, and a two symbol PBCH. The SS block can be transmitted in a fixed slot location, such as the symbols 0-3 as shown inFIG. 3. The PSS and SSS may be used by UEs for cell search and acquisition. The PSS may provide half-frame timing, the SS may provide the CP length and frame timing. The PSS and SSS may provide the cell identity. The PBCH carries some basic system information, such as downlink system bandwidth, timing information within radio frame, SS burst set periodicity, system frame number, etc. The SS blocks may be organized into SS bursts to support beam sweeping. Further system information such as, remaining minimum system information (RMSI), system information blocks (SIBs), other system information (OSI) can be transmitted on a physical downlink shared channel (PDSCH) in certain subframes. The SS block can be transmitted up to sixty-four times, for example, with up to sixty-four different beam directions for mmW. The up to sixty-four transmissions of the SS block are referred to as the SS burst set. SS blocks in an SS burst set are transmitted in the same frequency region, while SS blocks in different SS bursts sets can be transmitted at different frequency locations.

A control resource set (CORESET) for systems, such as an NR and LTE systems, may comprise one or more control resource (e.g., time and frequency resources) sets, configured for conveying PDCCH, within the system bandwidth. Within each CORESET, one or more search spaces (e.g., common search space (CSS), UE-specific search space (USS), etc.) may be defined for a given UE. According to aspects of the present disclosure, a CORESET is a set of time and frequency domain resources, defined in units of resource element groups (REGs). Each REG may comprise a fixed number (e.g., twelve) tones in one symbol period (e.g., a symbol period of a slot), where one tone in one symbol period is referred to as a resource element (RE). A fixed number of REGs may be included in a control channel element (CCE). Sets of CCEs may be used to transmit new radio PDCCHs (NR-PDCCHs), with different numbers of CCEs in the sets used to transmit NR-PDCCHs using differing aggregation levels. Multiple sets of CCEs may be defined as search spaces for UEs, and thus a NodeB or other base station may transmit an NR-PDCCH to a UE by transmitting the NR-PDCCH in a set of CCEs that is defined as a decoding candidate within a search space for the UE, and the UE may receive the NR-PDCCH by searching in search spaces for the UE and decoding the NR-PDCCH transmitted by the NodeB.

Example Methods for Updating Quality of Service (QoS) Information for Operations in a First Radio Access Technology while Connected to a Network Entity Using a Second Radio Access Technology

Aspects of the present disclosure provide apparatus, methods, processing systems, and computer readable mediums for updating quality of service (QoS) information in an environment where devices using a first radio access technology and devices using a second radio access technology coexist.

In LTE networks using the Evolved Packet System (EPS), QoS may be achieved by applying different parameters to different EPS bearer contexts within a packet data network (PDN) connection to a network entity identified by an access point name (APN). Similarly, in NR networks using the 5G System (5GS), QoS may be achieved by applying different parameters to QoS flows within a packet data unit (PDU) session with a network entity identified by a data network name (DNN). In an environment where a network using a first radio access technology (e.g., LTE) and a network using a second radio access technology (e.g., NR) coexist and a UE can operate on either network, mappings between EPS and 5GS session management parameters may allow for QoS information to be shared across different networks. For example, PDN connection information in EPS QoS information may correspond to PDU session information in 5GS QoS information; EPS bearer information in EPS QoS information may correspond to QoS flow information in 5GS QoS information; APN information may correspond to a DNN; and a traffic flow template (TFT) for an EPS bearer in EPS QoS information may correspond to one or more QoS rules for a QoS flow in 5GS QoS information.

Generally, mapped 5GS QoS information may include QoS flow descriptions and QoS flow rules. A QoS flow description generally includes a QoS Flow Identifier (QFI), an operation code, and one or more other parameters. The QFI may identify a specific operation to be performed in respect of the QoS information, such as creating a new QoS flow description, deleting an existing QoS flow description, or modifying a QoS flow description. The one or more other parameters may include a 5G QoS Identifier (5QI), guaranteed flow bit rate for the uplink (GFBR UL), guaranteed flow bit rate for the downlink (GFBR DL), maximum flow bit rate for the uplink (MFBR UL), maximum flow bit rate for the downlink (MFBR DL), an averaging window, and an EPS bearer identity (EBI). The QoS flow rules may include a QoS rule identifier, a rule operation code, an indication of whether the QoS rule is the default QoS rule, packet filters, a QoS rule precedence, and a QFI.

FIG. 4illustrates an example network in which interworking is established between an LTE and an NR network. When a PDN connection is established in the LTE network and an interface connecting the LTE and NR networks is present (e.g., the N26 interface), the network may transmit, to a UE, mapped 5GS QoS information for each EPS bearer being activated. By transmitting the mapped QoS information for each EPS bearer being activated, a UE may know which QoS flows to create and which QoS parameters to apply if and when the data session is transferred from an LTE to an NR network. The network may also update the mapped 5GS QoS information during EPS bearer context modification. The activation and modification of QoS information may be carried, for example, in a Protocol Configuration Options (PCO) or enhanced PCO (ePCO) information element in various messages, such as the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST, ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST, or MODIFY EPS BEARER CONTEXT REQUEST messages.

The mapping between 5GS QoS information and the corresponding EPS bearer may be performed based on the inclusion of the EBI in the mapped 5G QoS information. To simplify processing at a UE, the network may only include mapped 5GS QoS information corresponding to the EPS bearer context that is being activated or modified. If the EBI is omitted in the mapped 5G QoS information, the UE may assume that the mapped 5GS QoS information is associated with the EPS bearer context that is being activated or modified. Otherwise, if the EBI is included in the mapped 5GS QoS information and the included EBI is not the EBI of the mapped bearer context that is being activated or modified, the UE may discard the mapped 5G QoS information and report an error to the network.

In some cases, however, problems may arise with the inclusion of mapped 5GS QoS information in an activation or modification message. If the mapped 5GS QoS information (1) does not include an EBI or includes the EBI of the active EPS bearer, and (2) includes QoS rules or QoS flow descriptions already associated with an EPS bearer context other than the EPS bearer context being activated or modified, the processing of such information may cause the UE to apply the specified operation (e.g., QoS rule creation) to the EPS bearer context being activated or modified and to delete the QoS rule or QoS flow description associated with the EPS bearer context other than the EPS bearer context being activated or modified. In doing so, the UE may not report an error to the network. In these cases, EPS bearer contexts not being activated or modified may be impacted unintendedly.

FIG. 5illustrates example scenarios in which mapped 5GS QoS information may cause an unintended impact to QoS configurations associated with other EPS bearer contexts. For example, in a first example, the UE may receive an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message on EPS bearer 6, and the mapped QoS information in the message includes a QFI of 1 and an omitted mapped EBI or an EBI of 6. The UE may apply the EPS creation for EPS bearer 6. However, because QFI 1 has been mapped to EBI 5, the UE may delete the QoS flow for EPS bearer 5, which the UE is not supposed to modify.

FIG. 6illustrates example operations that may be performed by a user equipment to update a QoS configuration based on mapped 5GS QoS information. Generally, operations600may be performed when the UE executes an operation on the received 5GS mapped QoS information or deletes an existing QoS rule and/or QoS flow description, and the existing QoS rule and/or QoS flow description is associated with (e.g., mapped to) the EPS bearer context being activated or modified.

As illustrated, operations600begin at block602, where the UE receives, from a network entity, quality of service (QoS) information, a QoS identifier associated with the QoS information, and a bearer context associated with the QoS information. The QoS information, QoS identifier, and the bearer context associated with the QoS information may be received in one of a modify bearer context request message, an activate default bearer context request message, or an activate dedicated bearer context request message. Generally, the QoS information may be associated with a QoS rule identifier or a QoS flow identifier, and the QoS rule identifier or QoS flow identifier may be associated with an EPS bearer context based on a mapping between the QoS rule identifier or QoS flow identifier and the EPS bearer context.

At block604, the UE updates a QoS configuration using the QoS information based on whether QoS information associated with the QoS identifier is already configured for a bearer context different from the bearer context associated with the QoS information included in the received message (e.g., the modify bearer context request message, the activate default bearer context request message, or the an activate dedicated bearer context request message).

In some embodiments, the QoS information and the received QoS information may be associated with different bearer contexts. The QoS information and the received QoS information may belong to the same or different PDN connections.

In some embodiments, the QoS information, the QoS identifier associated with the QoS information, and the bearer context associated with the QoS information is received in a MODIFY EPS BEARER CONTEXT REQUEST message. The rule operation may specify that the UE is to create a new QoS rule, modify an existing QoS rule and add packet filters, modify an existing QoS rule and replace all packet filters, or modify an existing QoS rule without modifying packet filters. If there is already an existing QoS rule with the same QoS rule identifier, and the QoS rule identifier is associated with a QoS flow description stored for an EPS bearer context other than the EPS bearer context identified in the message, the UE may not perform the rule operation and may discard the QoS rule information. The UE may report an error to a network entity. The report may be carried, for example, in a PCO or ePCO IE with an indication that a semantic error exists in the QoS operation. In some embodiments, the PCO or ePCO IE may be transmitted in a MODIFY EPS BEARER CONTEXT ACCEPT message.

In some embodiments, a flow description operation may specify that a UE is to create a new QoS flow description, modify an existing QoS flow description, or delete an existing QoS flow description. If there is already an existing QoS flow description with the same QoS flow identifier as that included in the request and the QoS flow identifier is stored for an EPS bearer context different from the EPS bearer context identified in the message (i.e., the EPS bearer context being modified), the UE may not perform the flow description operation and may discard the flow description information. The UE may report an error to a network entity. The error may be carried, for example, in a PCO or ePCO IE with an indication that a semantic error exists in the QoS operation. In some embodiments, the PCO or ePCO IE may be transmitted in a MODIFY EPS BEARER CONTEXT ACCEPT message.

In some embodiments, the QoS information, the QoS identifier, and the bearer context associated with the QoS information may be included in an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST or ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message. The flow description operation may specify that the UE is to create a new QoS flow operation. If a QoS flow description exists with the same QoS flow identifier as that included in the message and the QoS flow identifier is stored for an EPS bearer context different from the EPS bearer context identified in the message (i.e., the EPS bearer context being activated), the UE may not perform the flow description operation and may discard the flow description operation. The UE may report an error to a network entity. The error may be carried, for example, in a PCO or ePCO IE with an indication that a semantic error exists in the QoS operation. In some embodiments, the PCO or ePCO IE may be transmitted in an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message or an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message.

In some embodiments, the MODIFY EPS BEARER CONTEXT REQUEST message, the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST, or the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message may be used to generate a new QoS rule associated with a given QoS identifier. If there is already an existing QoS rule associated with the QoS identifier and that the QoS identifier is not associated with a bearer context, the UE can discard the received QoS information and generate an error message indicating that the QoS information was discarded. As discussed, the error message may be transmitted by the UE to a network entity, for example, in a PCO or ePCO IE with an indication that a semantic error exists in the QoS operation.

FIG. 7illustrates a communications device700that may include various components (e.g., corresponding to means-plus-function components) configured to perform operations for the techniques disclosed herein, such as the operations illustrated inFIG. 6. The communications device700includes a processing system702coupled to a transceiver708. The transceiver708is configured to transmit and receive signals for the communications device700via an antenna710, such as the various signals as described herein. The processing system702may be configured to perform processing functions for the communications device700, including processing signals received and/or to be transmitted by the communications device700.

The processing system702includes a processor704coupled to a computer-readable medium/memory712via a bus706. In certain aspects, the computer-readable medium/memory712is configured to store instructions (e.g., computer-executable code) that when executed by the processor704, cause the processor704to perform the operations illustrated inFIG. 6, or other operations for performing the various techniques discussed herein to update a QoS configuration based on mapped 5GS QoS information. In certain aspects, computer-readable medium/memory712stores code714for receiving quality of service (QoS) information, a QoS identifier associated with the QoS information, and a bearer context associated with the QoS information; and code716for updating a QoS configuration using the QoS information. The processor714includes circuitry718for receiving quality of service (QoS) information, a QoS identifier associated with the QoS information, and a bearer context associated with the QoS information; and circuitry720for updating a QoS configuration using the QoS information.

Example Clauses

Clause 1: A method for wireless communications by a user equipment (UE), comprising: receiving, from a network entity, quality of service (QoS) information, a QoS identifier associated with the QoS information, and a bearer context associated with the QoS information in one of a modify bearer context request message, an activate default bearer context request message, or an activate dedicated bearer context request message, wherein the QoS information comprises parameters for a first radio access technology mapped to corresponding parameters for a second radio access technology; and updating a QoS configuration using the QoS information based on whether the UE is already configured with QoS information associated with the QoS identifier for a bearer context different from the bearer context associated with the QoS information received in the modify bearer context request message, activate default bearer context request message, or activate dedicated bearer context request message.

Clause 2: The method of Clause 1, wherein the bearer context different from the bearer context associated with the received QoS information belongs to a same packet data network (PDN) connection as the bearer context associated with the received QoS information.

Clause 3: The method of Clauses 1 or 2, wherein the QoS identifier comprises a QoS rule identifier.

Clause 4: The method of Clause 3, wherein updating the QoS configuration comprises: determining that an existing QoS rule is associated with the QoS identifier and that the QoS identifier is associated with a QoS flow description stored for a bearer context different from the bearer context associated with the QoS information received in the modify bearer context request message, activate default bearer context request message, or activate dedicated bearer context request message; discarding the received QoS information; and generating an error message indicating that the received QoS information was discarded.

Clause 5: The method of Clauses 1 or 2, wherein: the modify bearer context request message, the activate default bearer context request message, or the activate dedicated bearer context request message includes an indication to create a new QoS rule; and updating the QoS configuration comprises: determining that an existing QoS rule is associated with the QoS identifier and that the QoS identifier is not associated with a bearer context; discarding the received QoS information; and generating an error message indicating that the received QoS information was discarded.

Clause 6: The method of any of Clauses 1 through 5, wherein the QoS identifier comprises a QoS flow identifier.

Clause 7: The method of Clause 6, wherein updating the QoS configuration comprises: determining that an existing QoS flow description is associated with the QoS identifier and that the QoS identifier is associated with a bearer context different from the bearer context associated with the QoS information received in the modify bearer context request message, activate default bearer context request message, or activate dedicated bearer context request message; discarding the received QoS information; and generating an error message indicating that the received QoS information was discarded.

Clause 8: An apparatus, comprising: a memory; and a processor configured to perform the operations of any of Clauses 1 through 7.

Clause 9: An apparatus, comprising: means for performing the operations of any of Clauses 1 through 7.

Clause 10: A computer-readable medium having instructions stored thereon which, when executed by a processor, performs the operations of any of Clauses 1 through 7.

Additional Considerations

The techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, while aspects may be described herein using terminology commonly associated with 3G, 4G, or 5G wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems.

NR may utilize OFDM with a CP on the uplink and downlink and include support for half-duplex operation using TDD. In NR, a subframe is still 1 ms, but the basic TTI is referred to as a slot. A subframe contains a variable number of slots (for example, 1, 2, 4, 8, 16, . . . slots) depending on the subcarrier spacing. The NR RB is 12 consecutive frequency subcarriers. NR may support a base subcarrier spacing of 15 KHz and other subcarrier spacing may be defined with respect to the base subcarrier spacing, for example, 30 kHz, 60 kHz, 120 kHz, 240 kHz, etc. The symbol and slot lengths scale with the subcarrier spacing. The CP length also depends on the subcarrier spacing. Beamforming may be supported and beam direction may be dynamically configured. MIMO transmissions with precoding may also be supported. In some examples, MIMO configurations in the DL may support up to 8 transmit antennas with multi-layer DL transmissions up to 8 streams and up to 2 streams per UE. In some examples, multi-layer transmissions with up to 2 streams per UE may be supported. Aggregation of multiple cells may be supported with up to 8 serving cells.

As used herein, the term “determining” may encompass one or more of a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, investigating, looking up (for example, looking up in a table, a database or another data structure), assuming and the like. Also, “determining” may include receiving (for example, receiving information), accessing (for example, accessing data in a memory) and the like. Also, “determining” may include resolving, selecting, choosing, establishing and the like.

As used herein, “or” is used intended to be interpreted in the inclusive sense, unless otherwise explicitly indicated. For example, “a or b” may include a only, b only, or a combination of a and b. As used herein, a phrase referring to “at least one of” or “one or more of” a list of items refers to any combination of those items, including single members. For example, “at least one of: a, b, or c” is intended to cover the possibilities of: a only, b only, c only, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of a and b and c.