Handling of Mapped 5G System (5GS) Quality of Service (QoS) Information in the Evolved Packet System (EPS)

Abstract

Aspects of the present disclosure provide an apparatus, method, processing system, and computer-readable medium for updating a QoS configuration at a user equipment (UE). Generally speaking, an example method includes: receiving quality of service (QoS) information, a QoS identifier associated with the QoS information, and a bearer context associated with the QoS information from a network entity 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 the QoS configuration with the QoS information based on whether the UE has been 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, the activate default bearer context request message, or the activate dedicated bearer context request message.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims the benefit of priority of U.S. Application No. 17 / 199,816, filed on Mar. 12, 2021, which claims the benefit of priority of U.S. Provisional Patent Application No. 63 / 007,262, entitled "Processed Mapped 5G System Quality of Service (QoS) Information in Evolved Packet System (EPS)", filed on Apr. 8, 2020. Both of the above - mentioned applications are assigned to the assignee of this application, and the entire contents of which are incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate to wireless communication, and more particularly, aspects of the present disclosure relate to techniques for updating quality of service (QoS) parameters in an environment where a device using a first radio access technology co - exists with a device using a second radio access technology. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasting, etc. These wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). By way of example, examples of such multiple access systems include the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) system, the Advanced LTE (LTE - A) system, the Code Division Multiple Access (CDMA) system, the Time Division Multiple Access (TDMA) system, the Frequency Division Multiple Access (FDMA) system, the Orthogonal Frequency Division Multiple Access (OFDMA) system, the Single - Carrier Frequency Division Multiple Access (SC - FDMA) system, and the Time Division Synchronous Code Division Multiple Access (TD - SCDMA) system.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, and even global levels. New Radio (e.g., 5G NR) is an example of an emerging telecommunication standard. NR is an enhanced set of the LTE mobile standard released by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectral efficiency, reducing cost, improving services, utilizing new spectrums, and better integrating with other open standards by using OFDMA with cyclic prefix (CP) on the downlink (DL) and on the uplink (UL). To this end, NR supports beamforming, multiple - input multiple - output (MIMO) antenna technology, and carrier aggregation.

[0006] However, as the demand for mobile broadband access continues to grow, there is a need for further improvements to NR and LTE technologies. Preferably, these improvements should be applicable to other multiple access technologies and the telecommunication standards that employ these technologies.

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

[0008] The systems, methods, and devices of the present disclosure each have several innovative aspects, none of which alone is responsible for the desired attributes.

[0009] One innovative aspect of the subject matter described in the present disclosure may be implemented in a method for wireless communication by a user equipment (UE). Generally speaking, the method includes: receiving 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 from a network entity; and updating a QoS configuration using the QoS information based on whether the UE has been configured with QoS information associated with the QoS identifier for a bearer context different from the bearer context associated with the QoS information.

[0010] Aspects of the present disclosure provide units, devices, processors, and computer-readable media for performing the methods described herein.

[0011] To achieve the foregoing and related purposes, one or more aspects include the features described in detail hereinafter and particularly pointed out in the claims. The following description and the drawings set forth in detail some illustrative features of one or more aspects. However, these features indicate only some of the various ways in which the principles of the various aspects may be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Details of one or more implementations of the subject matter described in the present disclosure are set forth in the drawings and the following description. However, the drawings only show some typical aspects of the present disclosure and should not be considered as limiting its scope. Other features, aspects, and advantages will become apparent from the description, the drawings, and the claims.

[0013] Figure 1FIG. 0 illustrates an example wireless communication network in which some aspects of the present disclosure may be implemented.

[0014] Figure 2 FIG. 4 illustrates a block diagram depicting an example base station (BS) and an example user equipment (UE) in accordance with some aspects of the present disclosure.

[0015] Figure 3 FIG. 8 illustrates an example of a frame format for a telecommunications system in accordance with certain aspects of the present disclosure.

[0016] Figure 4 FIG. 12 illustrates an interworking between a network operating using a first radio access technology and a network operating using a second radio access technology.

[0017] Figure 5 FIG. 16 illustrates an example scenario where mapping between quality of service (QoS) information of a network using a first radio access technology and QoS information of a network using a second radio access technology is used to activate QoS rules for a bearer context.

[0018] Figure 6 FIG. 20 illustrates example operations for wireless communication by a user equipment (UE) in accordance with some aspects of the present disclosure.

[0019] Figure 7 FIG. 24 illustrates a communication device in accordance with aspects of the present disclosure, which may include various components configured to perform operations for the techniques disclosed herein.

[0020] For ease of understanding, where possible, the same reference numerals have been used to designate identical elements common to the figures. It is contemplated that elements disclosed in one aspect may be beneficially utilized in other aspects without specific recitation. DETAILED DESCRIPTION

[0021] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media 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.

[0022] The following description provides examples of updating QoS information in an environment where a device using a first radio access technology coexists with a device using a second radio access technology, and does not limit the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of the elements discussed without departing from the scope of the present disclosure. Various processes or components may be omitted, replaced, or added as appropriate for each example. For example, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Additionally, features described with respect to some examples may be combined into some other examples. For instance, using any number of aspects set forth herein, a device may be implemented or a method may be practiced. Moreover, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functionality, or a combination of structures and functionality different from or in addition to the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure set forth herein may be embodied by one or more elements of the claims.

[0023] In general, any number of wireless networks may be deployed in a given geographical area. Each wireless network may support a specific radio access technology (RAT) and may operate on one or more frequencies. The RAT may also be referred to as a radio technology, air interface, etc. The frequency may also be referred to as a carrier, sub - carrier, frequency channel, tone, sub - band, etc. Each frequency may support a single RAT in a given geographical area to avoid interference between wireless networks with different RATs. In some cases, a 5G NR RAT network may be deployed.

[0024] Figure 1 An example wireless communication network 100 is shown in which aspects of the present disclosure may be performed. For example, as Figure 1 shown, UE 120a may include a Quality of Service (QoS) parameter update module 122, and the QoS parameter update module 122 may be configured to perform (or cause UE 120a to perform) Figure 4 operation 400. Similarly, base station 110a may include a QoS parameter configuration module 112, and the QoS parameter configuration module 112 may be configured to perform (or cause base station 110a to perform) an operation of sending QoS configuration information to the UE.

[0025] NR access (e.g., 5G NR) can support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting broadband widths (e.g., 80 MHz or higher), millimeter wave (mmWave) targeting high carrier frequencies (e.g., 25 GHz or higher), massive machine type communication MTC (mMTC) targeting non-backward compatible MTC technologies, or mission-critical services targeting ultra-reliable low-latency communication (URLLC). These services can include latency and reliability requirements. These services can also have different transmission time intervals (TTIs) to meet the corresponding quality of service (QoS) requirements. Additionally, these services can coexist in the same time domain resources (e.g., time slots or subframes) or frequency domain resources (e.g., component carriers).

[0026] As Figure 1 shown, the wireless communication network 100 can include multiple base stations (BSs) 110a-z (each BS is also individually referred to herein as BS 110 or collectively as BS 110) and other network entities. The BS 110 can provide communication coverage for a specific geographical area (sometimes referred to as a “cell”), which can be fixed or can move according to the location of the mobile BS 110. In some examples, the BSs 110 can be interconnected with each other or with one or more other BSs or network nodes (not shown) in the wireless communication network 100 through various types of backhaul interfaces (e.g., direct physical connections, wireless connections, virtual networks, etc.) using any suitable transmission network. In Figure 1 the example shown, BSs 110a, 110b, and 110c can be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS 110x can be a pico BS for pico cell 102x. BSs 110y and 110z can be femto BSs for femto cells 102y and 102z, respectively. A BS can support one or more cells. The BS 110 communicates with user equipment (UEs) 120a-y (each UE is also individually referred to herein as UE 120 or collectively as UEs 120) in the wireless communication network 100. The UEs 120 (e.g., 120x, 120y, etc.) can be dispersed throughout the wireless communication network 100, and each UE 120 can be fixed or mobile.

[0027] The wireless communication network 100 can also include relay stations (e.g., relay station 110r) (which are also referred to as repeaters, etc.), which receive transmissions of data and / or other information from an upstream station (e.g., BS 110a or UE 120r) and send transmissions of data or other information to a downstream station (e.g., UE 120 or BS 110), or relay transmissions between UEs 120 to facilitate communication between devices.

[0028] The network controller 130 can be coupled to a set of BSs 110 and provide coordination and control for these BSs 110. The network controller 130 can communicate with the BSs 110 via the backhaul. The BSs 110 can also communicate with each other (e.g., directly or indirectly) via a wireless or wired backhaul.

[0029] Figure 2 A block diagram of an example base station (BS) and an example user equipment (UE) in accordance with some aspects of the present disclosure is shown.

[0030] At the BS 110, the transmit processor 220 can receive data from the data source 212 and control information from the controller / processor 240. The control information can be used 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 can be used for the physical downlink shared channel (PDSCH), etc. The processor 220 can process (e.g., encode and symbol map) the data and control information respectively to obtain data symbols and control symbols. The transmit processor 220 can also generate reference symbols such as for the primary synchronization signal (PSS), secondary synchronization signal (SSS), and cell-specific reference signal (CRS). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on the data symbols, control symbols, or reference symbols (if applicable) and provide an output symbol stream to the modulators (MOD) 232a - 232t. Each modulator 232 can process the corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signals from the modulators 232a - 232t can be transmitted via the antennas 234a - 234t respectively.

[0031] At the UE 120, antennas 252a - 252r can receive downlink signals from the BS 110 and can provide the received signals to the demodulators (DEMOD) in transceivers 254a - 254r, respectively. Each demodulator 254 can condition (e.g., filter, amplify, down - convert, and digitize) the respective received signal to obtain input samples. Each demodulator can further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. The MIMO detector 256 can obtain the received symbols from all demodulators 254a - 254r, perform MIMO detection on the received symbols (if applicable), and provide the detected symbols. The receive processor 258 can process (e.g., demodulate, de - interleave, and decode) the detected symbols, provide the decoded data for the UE 120 to the data sink 260, and provide the decoded control information to the controller / processor 280.

[0032] On the uplink, at the UE 120, the transmit processor 264 can receive and process data from the data source 262 (e.g., for the physical uplink shared channel (PUSCH)) and control information from the controller / processor 280 (e.g., for the physical uplink control channel (PUCCH)). The transmit processor 264 can also generate reference symbols for reference signals (e.g., for sounding reference signals (SRS)). The symbols from the transmit processor 264 can be precoded by the TX MIMO processor 266 (if applicable), further processed by the demodulators in transceivers 254a - 254r (e.g., for SC - FDM, etc.), and sent to the BS 110. At the BS 110, the uplink signal from the UE 120 can be received by the antenna 234, processed by the modulator 232, detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain the decoded data and control information sent by the UE 120. The receive processor 238 can provide the decoded data to the data sink 239 and provide the decoded control information to the controller / processor 240.

[0033] Memories 242 and 282 can store data and program codes for the BS 110 and the UE 120, respectively. The scheduler 244 can schedule the UE for data transmission on the downlink or uplink.

[0034] The controller / processor 280 or other processors and modules at the UE 120 can execute or direct the execution of the processes of the techniques described herein. As Figure 2 shown, the controller / processor 280 of the UE 120 has a QoS parameter update module 122, which can be configured to execute Figure 4Operation 400, as discussed further below in detail. The controller / processor 240 of the base station 110 includes a QoS parameter configuration module that can be configured to send a QoS configuration message to the UE for processing. Although shown at the controller / processor, other components of the UE or BS can be used to perform the operations described herein.

[0035] Figure 3 FIG. is a diagram illustrating an example of a frame format 300 for NR. The transmission timeline for each of the downlink and uplink can be divided into units of radio frames. Each radio frame can have a predetermined duration (e.g., 10 ms) and can be divided into 10 subframes with indices 0 to 9, each subframe being 1 ms. Each subframe can include a variable number of time slots, depending on the subcarrier spacing. Each time slot can include a variable number of symbol periods (e.g., 7 or 14 symbols), depending on the subcarrier spacing. Indices can be assigned to the symbol periods within each time slot. A mini-slot (which can be referred to as a sub-slot structure) refers to a transmission time interval having a duration less than that of a time slot (e.g., 2, 3, or 4 symbols).

[0036] Each symbol in a time slot can indicate the link direction of data transmission (e.g., DL, UL, or flexible), and the link direction of each subframe can be switched dynamically. The link direction can be based on the time slot format. Each time slot can include DL / UL data as well as DL / UL control information.

[0037] In NR, a synchronization signal (SS) block is transmitted. The SS block includes PSS, SSS, and a two-symbol PBCH. The SS block can be transmitted in fixed time slot positions (such as symbols 0-3 as shown in Figure 3 . The PSS and SSS can be used by the UE for cell search and capture. The PSS can provide half-frame timing, and the SSS can provide the CP length and frame timing. The PSS and SSS can provide the cell identity. The PBCH carries certain basic system information, such as the downlink system bandwidth, timing information within the radio frame, SS burst set periodicity, system frame number, etc. The SS blocks can be organized into SS bursts to support beam scanning. Additional system information, such as the remaining minimum system information (RMSI), system information block (SIB), other system information (OSI), can be transmitted on the physical downlink shared channel (PDSCH) in certain subframes. For mmW, the SS block can be transmitted up to sixty-four times, e.g., with up to sixty-four different beam directions. Up to sixty-four transmissions of the SS block are referred to as an SS burst set. The SS blocks within an SS burst set are transmitted in the same frequency region, while the SS blocks in different SS burst sets can be transmitted at different frequency positions.

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

[0039] Example method for updating quality of service (QoS) information for operations in a first radio access technology when connected to a network entity using a second radio access technology

[0040] Aspects of the present disclosure provide an apparatus, method, processing system, and computer-readable medium for updating quality of service (QoS) information in an environment where a device using a first radio access technology and a device using a second radio access technology coexist.

[0041] In an LTE network using the evolved packet system (EPS), QoS can 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 a NR network using the 5G system (5GS), QoS can 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, the mapping between EPS and 5G session management parameters can allow sharing of QoS information between different networks. For example, the PDN connection information in EPS QoS information can correspond to the PDU session information in 5GS QoS information; the EPS bearer information in EPS QoS information can correspond to the QoS flow information in 5GS QoS information; the APN information can correspond to the DNN; and the traffic flow template (TFT) for an EPS bearer in EPS QoS information can correspond to one or more QoS rules of a QoS flow in 5GS QoS information.

[0042] Generally, the mapped 5G QoS information can include a QoS flow description and QoS flow rules. The QoS flow description typically includes a QoS flow identifier (QFI), an operation code, and one or more other parameters. The QFI can identify a specific operation to be performed regarding 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 can include a 5G QoS identifier (5QI), a guaranteed flow bit rate for the uplink (GFBR UL), a guaranteed flow bit rate for the downlink (GFBR DL), a maximum flow bit rate for the uplink (MFBR UL), a maximum flow bit rate for the downlink (MFBR DL), an average window, and an EPS bearer identifier (EBI). The QoS flow rules can include a QoS rule identifier, a rule operation code, an indication of whether the QoS rule is a default QoS rule, a packet filter, a QoS rule priority, and a QFI.

[0043] Figure 4An example network for establishing interworking between an LTE and an NR network is shown. When a PDN connection is established in the LTE network and there is an interface connecting the LTE and NR networks (e.g., the N26 interface), the network may send 5GS QoS information mapped for each EPS bearer that is being activated to the UE. By sending the QoS information mapped for each EPS bearer that is being activated, the UE can know which QoS flows are to be created and which QoS parameters are to be applied if the data session is transferred from the LTE to the NR network and when the data session is transferred from the LTE to the NR network. The network may also update the mapped 5GS QoS information during EPS bearer context modification. The activation and modification of the QoS information may be carried in, for example, the protocol configuration option (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 message.

[0044] The mapping between the 5G QoS information and the corresponding EPS bearer may be performed based on including the EBI in the mapped 5G QoS information. To simplify the processing at the UE, the network may include only the mapped 5G QoS information corresponding to the EPS bearer context that is being activated or modified. If the EBI is omitted from 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 5G 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.

[0045] However, in some cases, there may be problems with including the mapped 5G QoS information in the activation or modification message. If the mapped 5G QoS information (1) does not include the EBI or includes the EBI of an active EPS bearer, and (2) includes QoS rules or QoS flow descriptions that have been associated with an EPS bearer context other than the EPS bearer context that is being activated or modified, the processing of such information may cause the UE to apply a specified operation (e.g., QoS rule creation) to the EPS bearer context that is being activated or modified and delete the QoS rules or QoS flow descriptions associated with the EPS bearer context other than the EPS bearer context that is being activated or modified. In doing so, the UE may not report an error to the network. In these cases, the EPS bearer context that is not being activated or modified may be unexpectedly affected.

[0046] Figure 5An example scenario is shown where the mapped 5G QoS information may have an unexpected impact on the QoS configuration associated with other EPS bearer contexts. For example, in the first example, the UE may receive an Activate Dedicated EPS Bearer Context Request message on EPS bearer 6, and the mapped QoS information in this message includes a QFI of 1 and an omitted mapped EBI or an EBI of 6. The UE may apply EPS creation for EPS bearer 6. However, since QFI 1 has already been mapped to EBI 5, the UE may delete the QoS flow of EPS bearer 5 and the UE should not modify EPS bearer 5.

[0047] Figure 6 An example operation that can be performed by a user equipment to update the QoS configuration based on the mapped 5G QoS information is shown. Generally, operation 600 may be performed when the UE performs an operation on the received 5GS mapped QoS information or deletes existing QoS rules and / or QoS flow descriptions, and the existing QoS rules and / or QoS flow descriptions are associated with (e.g., mapped to) the EPS bearer context that is being activated or modified.

[0048] As shown, operation 600 begins at block 602, where the UE receives quality of service (QoS) information, a QoS identifier associated with the QoS information, and a bearer context associated with the QoS information from a network entity. The QoS information, the 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 based on the mapping between the QoS rule identifier or the QoS flow identifier and the EPS bearer context, the QoS rule identifier or the QoS flow identifier may be associated with the EPS bearer context.

[0049] At block 604, the UE updates the QoS configuration using the QoS information based on whether the QoS information associated with the QoS identifier has been configured for a bearer context different from the bearer context associated with the QoS information included in the received message (e.g., Modify Bearer Context Request message, Activate Default Bearer Context Request message, or Activate Dedicated Bearer Context Request message).

[0050] 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.

[0051] In some embodiments, QoS information, a QoS identifier associated with the QoS information, and a bearer context associated with the QoS information are received in a Modify EPS Bearer Context Request message. The rule operation may specify that the UE will 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 the packet filters. If there already exists 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 the network entity. For example, the report may be carried, e.g., in a PCO or ePCO IE, with an indication of a semantic error in the QoS operation. In some embodiments, the PCO or ePCO IE may be sent in a Modify EPS Bearer Context Accept message.

[0052] In some embodiments, the flow description operation may specify that the UE will create a new QoS flow description, modify an existing QoS flow description, or delete an existing QoS flow description. If there already exists an existing QoS flow description with the same QoS flow identifier as the QoS flow identifier 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 the network entity. The error may be carried, e.g., in a PCO or ePCO IE, with an indication of a semantic error in the QoS operation. In some embodiments, the PCO or ePCO IE may be sent in a Modify EPS Bearer Context Accept message.

[0053] In some embodiments, QoS information, a QoS identifier, and a bearer context associated with the QoS information may be included in an Activate Default EPS Bearer Context Request or an Activate Dedicated EPS Bearer Context Request message. The flow description operation may specify that the UE will create a new QoS flow operation. If there is a QoS flow description with the same QoS flow identifier as the QoS flow identifier 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 the network entity. The error may be carried, for example, in a PCO or ePCO IE, with an indication of a semantic error in the QoS operation. In some embodiments, the PCO or ePCO IE may be sent in an Activate Default EPS Bearer Context Accept message or an Activate Dedicated EPS Bearer Context Accept message.

[0054] In some embodiments, a Modify EPS Bearer Context Request message, an Activate Default EPS Bearer Context Request, or an 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 an existing QoS rule associated with the QoS identifier and the QoS identifier is not associated with a bearer context, the UE may discard the received QoS information and generate an error message indicating that the QoS information was discarded. As discussed, the error message may be sent by the UE to the network entity, for example, in a PCO or ePCO IE, with an indication of a semantic error in the QoS operation.

[0055] Figure 7 A communication device 700 is shown, which may include various components (e.g., corresponding to unit plus functional components) configured to perform operations for the techniques disclosed herein, such as Figure 6 the operations shown. The communication device 700 includes a processing system 702 coupled to a transceiver 708. The transceiver 708 is configured to transmit and receive signals for the communication device 700 via an antenna 710, such as the various signals described herein. The processing system 702 may be configured to perform processing functions for the communication device 700, including processing signals received and / or to be transmitted by the communication device 700.

[0056] The processing system 702 includes a processor 704 coupled to a computer-readable medium / memory 712 via a bus 706. In certain aspects, the computer-readable medium / memory 712 is configured to store instructions (e.g., computer-executable code) that, when executed by the processor 704, cause the processor 704 to perform Figure 6The operations shown or other operations for performing the various techniques discussed herein for updating QoS configurations based on mapped 5G QoS information. In some aspects, the computer-readable medium / memory 712 stores: code 714 for receiving quality of service (QoS) information, a QoS identifier associated with the QoS information, and a bearer context associated with the QoS information; and code 716 for updating the QoS configuration using the QoS information. The processor 714 includes: circuitry 718 for receiving quality of service (QoS) information, a QoS identifier associated with the QoS information, and a bearer context associated with the QoS information; and circuitry 720 for updating the QoS configuration using the QoS information.

[0057] Example clause

[0058] Clause 1: A method for wireless communication by a user equipment (UE), comprising: receiving, in one of a modify bearer context request message, an activate default bearer context request message, or an activate dedicated bearer context request message, quality of service (QoS) information, a QoS identifier associated with the QoS information, and a bearer context associated with the QoS information, wherein the QoS information includes parameters mapped from a first radio access technology to corresponding parameters for a second radio access technology; and updating a QoS configuration using the QoS information based on whether the UE has been 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, the activate default bearer context request message, or the activate dedicated bearer context request message.

[0059] Clause 2: The method according to clause 1, wherein the bearer context different from the bearer context associated with the received QoS information and the bearer context associated with the received QoS information belong to the same packet data network (PDN) connection.

[0060] Clause 3: The method according to clause 1 or 2, wherein the QoS identifier includes a QoS rule identifier.

[0061] Clause 4: The method according to clause 3, wherein updating the QoS configuration includes: 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, the activate default bearer context request message, or the activate dedicated bearer context request message; discarding the received QoS information; and generating an error message indicating that the received QoS information has been discarded.

[0062] Clause 5: The method according to Clause 1 or 2, wherein: the modified bearer context request message, the activate default bearer context request message, or the activate dedicated bearer context request message includes an indication for creating a new QoS rule; and updating the QoS configuration includes: determining that an existing QoS rule is associated with the QoS identifier and 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 is discarded.

[0063] Clause 6: The method according to any one of Clauses 1 to 5, wherein the QoS identifier includes a QoS flow identifier.

[0064] Clause 7: The method according to Clause 6, wherein updating the QoS configuration includes: determining that an existing QoS flow description is associated with the QoS identifier and the QoS identifier is associated with a bearer context different from the bearer context associated with the QoS information received in the modified 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 is discarded.

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

[0066] Clause 9: An apparatus, comprising: units for performing the operations of any one of Clauses 1 to 7.

[0067] Clause 10: A computer-readable medium having instructions stored thereon, the instructions when executed by a processor perform the operations of any one of Clauses 1 to 7.

[0068] Additional Considerations

[0069] The techniques described herein can be used in a variety of wireless communication technologies, such as NR (e.g., 5G NR), 3GPP Long Term Evolution (LTE), LTE-Advanced (LTE-A), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), and other networks. The terms "network" and "system" are often used interchangeably. CDMA networks may implement radio technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers the IS-2000, IS-95, and IS-856 standards. TDMA networks may implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA networks may implement radio technologies such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunications System (UMTS). LTE and LTE-A are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). cdma2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). NR is an emerging wireless communication technology in deployment.

[0070] The techniques described herein can be used in the wireless networks and radio technologies mentioned above and other wireless networks and radio technologies. For clarity, although terms commonly associated with 3G, 4G, or 5G wireless technologies may be used herein to describe aspects, aspects of the present disclosure can be applied to communication systems based on other generations.

[0071] In 3GPP, the term "cell" can refer to the coverage area of a Node B (NB) or the NB subsystem serving that coverage area, depending on the context in which the term is used. In the NR system, the terms "cell" and BS, Next Generation Node B (gNB or gNodeB), Access Point (AP), Distributed Unit (DU), carrier, or Transmission and Reception Point (TRP) can be used interchangeably. A BS can provide communication coverage for macro cells, pico cells, femto cells, or other types of cells. A macro cell can cover a relatively large geographical area (e.g., with a radius of several kilometers) and can allow unrestricted access by UEs with service subscriptions. A pico cell can cover a relatively small geographical area and can allow unrestricted access by UEs with service subscriptions. A femto cell can cover a relatively small geographical area (e.g., a residence) and can allow restricted access by UEs associated with that femto cell (e.g., UEs in a Closed Subscriber Group (CSG), UEs for users in a residence, etc.). The BS for a macro cell can be referred to as a macro BS. The BS for a pico cell can be referred to as a pico BS. The BS for a femto cell can be referred to as a femto BS or a home BS.

[0072] A UE can also be referred to as a mobile station, terminal, access terminal, user unit, station, Customer Premises Equipment (CPE), cellular phone, smart phone, Personal Digital Assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, Wireless Local Loop (WLL) station, tablet computer, camera, gaming device, netbook, smartbook, ultrabook, appliance, medical device or apparatus, biometric sensor / device, wearable device (such as a smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.)), entertainment device (e.g., music device, video device, satellite radio unit, etc.), vehicle component or sensor, smart meter / sensor, industrial manufacturing device, Global Positioning System device, or any other suitable device configured to communicate via wireless or wired media. Some UEs can be considered Machine Type Communication (MTC) devices or Evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with a BS, another device (e.g., a remote device), or some other entity. A wireless node can provide a connection to or for a network (e.g., a Wide Area Network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs can be considered Internet of Things (IoT) devices, which can be Narrowband IoT (NB-IoT) devices.

[0073] Some wireless networks (e.g., LTE) utilize Orthogonal Frequency Division Multiplexing (OFDM) on the downlink and Single Carrier Frequency Division Multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are often also referred to as tones, frequency bands, etc. Each subcarrier can be modulated with data. Generally, OFDM is utilized in the frequency domain and SC-FDM is utilized in the time domain to transmit modulation symbols. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing can be 15 kHz and the minimum resource allocation (referred to as a "resource block" (RB)) can be 12 subcarriers (or 180 kHz). Thus, for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal Fast Fourier Transform (FFT) size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into subbands. For example, a subband can cover 1.08 MHz (e.g., 6 RBs), and for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, there can be 1, 2, 4, 8, or 16 subbands, respectively. In LTE, the basic Transmission Time Interval (TTI) or packet duration is a 1 ms subframe.

[0074] NR can utilize OFDM with CP on both the uplink and downlink and includes support for half-duplex operation using TDD. In NR, the subframe is still 1 ms, but the basic TTI is referred to as a slot. The subframe contains a variable number of slots (e.g., 1, 2, 4, 8, 16... slots), which depends on the subcarrier spacing. The NR RB is 12 consecutive frequency subcarriers. NR can support a basic subcarrier spacing of 15 kHz, and other subcarrier spacings can be defined relative to the basic subcarrier spacing, e.g., 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 can be supported and the beam direction can be configured dynamically. MIMO transmission with precoding can also be supported. In some examples, the MIMO configuration in the DL can support up to 8 transmit antennas, where multi-layer DL transmission is up to 8 streams and up to 2 streams per UE. In some examples, multi-layer transmission with up to 2 streams per UE can be supported. Aggregation of multiple cells with up to 8 serving cells can be supported.

[0075] In some examples, access to the air interface can be scheduled. A scheduling entity (e.g., a BS) allocates resources for communication among some or all of the devices and apparatuses within its serving area or cell. The scheduling entity can be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for the scheduled communication, the subordinate entity utilizes the resources allocated by the scheduling entity. A base station is not the only entity that can be used as a scheduling entity. In some examples, a UE can be used as a scheduling entity and can schedule resources for one or more subordinate entities (e.g., one or more other UEs), and other UEs can utilize the resources scheduled by the UE for wireless communication. In some examples, a UE can be used as a scheduling entity in a peer-to-peer (P2P) network or in a mesh network. In a mesh network example, in addition to communicating with the scheduling entity, UEs can communicate directly with each other.

[0076] As used herein, the term "determine" can include one or more of a variety of actions. For example, "determine" can include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, database, or another data structure), assuming, etc. Additionally, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc. Additionally, "determine" can include parsing, selecting, choosing, establishing, etc.

[0077] As used herein, unless otherwise expressly stated, the use of "or" is intended to be construed in an inclusive sense. For example, "a or b" can include only a, only b, or a combination of a and b. As used herein, a phrase referring to "at least one" or "one or more" of a list of items refers to any combination of those items, including a single member. For example, "at least one of the following: a, b, or c" is intended to cover the possibilities of only a, only b, only c, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of a, b, and c.

[0078] The various illustrative components, logics, logic blocks, modules, circuits, operations, and algorithmic processes described in connection with the implementations disclosed herein can be implemented as electronic hardware, firmware, software, or any combination of hardware, firmware, or software, including the structures and their structural equivalents disclosed in this specification. The interchangeability of hardware, firmware, and software has been generally described in functional terms and illustrated above in connection with the various illustrative components, blocks, modules, circuits, and processes. Whether such functionality is implemented as hardware, firmware, or software depends upon the particular application and the design constraints imposed on the overall system.

[0079] Various modifications to the implementations described in this disclosure may be apparent to those of ordinary skill in the art, and the general principles defined herein may be applied to other implementations without departing from the spirit or scope of the disclosure. Accordingly, the claims are not intended to be limited to the implementations shown herein but are to be accorded the widest scope consistent with the disclosure, the principles disclosed herein, and the novel features.

[0080] In addition, the various features described in the context of separate implementations in this specification can also be implemented in combination in a single implementation. Conversely, the various features described in the context of a single implementation can also be implemented separately or in any suitable sub-combination in multiple implementations. Moreover, although the features may have been described above as acting in a particular combination and even initially claimed as such, in some cases, one or more features from the claimed combination can be removed from the combination, and the claimed combination can be directed to a sub-combination or a variation of the sub-combination.

[0081] Similarly, although the operations are depicted in the drawings in a particular order, this should not be understood as requiring that the operations be performed in the particular order shown or in a sequential order, or that all of the illustrated operations be performed to achieve the desired result. Additionally, the drawings may schematically depict one or more example processes in the form of a flowchart or process diagram. However, other operations not depicted may be incorporated into the example processes schematically shown. For example, one or more additional operations may be performed before, after, concurrently with, or in between any of the operations shown. In certain cases, multitasking and parallel processing may be advantageous. Moreover, the partitioning of the various system components described in the implementations above should not be understood as requiring such partitioning in all implementations, and it should be understood that the described program components and systems can generally be integrated together in a single software product or encapsulated into multiple software products.

Claims

1. A method for wireless communication by a user equipment UE, comprising: receiving, in a message, quality of service QoS information, a QoS identifier associated with the QoS information, and a bearer context associated with the QoS information, wherein the QoS information includes parameters for a first radio access technology mapped to corresponding parameters for a second radio access technology; and discarding a QoS configuration using the QoS information based on the UE being 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 message, wherein discarding the QoS configuration includes: 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 message; discarding the received QoS information; and generating an error message indicating that the received QoS information is discarded.

2. The method according to claim 1, wherein The message includes one of the following: a modify bearer context request message, an activate default bearer context request message, or an activate dedicated bearer context request message.

3. The method according to claim 1, wherein, A bearer context different from the bearer context associated with the received QoS information and the bearer context associated with the received QoS information belong to the same packet data network PDN connection.

4. The method according to claim 1, wherein The QoS identifier includes a QoS rule identifier.

5. The method according to claim 1, wherein, The message includes an indication to create a new QoS rule; and wherein discarding the QoS configuration further includes: 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 is discarded.

6. The method according to claim 1, wherein, The QoS identifier includes a QoS flow identifier.

7. The method according to claim 6, wherein, The message includes an indication to create a new QoS flow description or modify an existing QoS flow description or delete an existing QoS flow description, and wherein discarding the QoS configuration further includes: 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 message; discarding the received QoS information; and generating an error message indicating that the received QoS information is discarded.

8. An apparatus for wireless communication by a user equipment UE, comprising: a processor configured to cause the UE to: receive, in a message, quality of service QoS information, a QoS identifier associated with the QoS information, and a bearer context associated with the QoS information, wherein the QoS information includes parameters for a first radio access technology mapped to corresponding parameters for a second radio access technology; and Discard the QoS configuration using the QoS information, based on that the UE has been 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 message, wherein the processor is configured to cause the UE to perform the following to discard the QoS configuration: Determine that an existing QoS rule is associated with the QoS identifier, and 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 message; Discard the received QoS information; and Generate an error message indicating that the received QoS information is discarded.

9. The device according to claim 8, wherein, The message includes one of the following: Modify bearer context request message, activate default bearer context request message, or activate dedicated bearer context request message.

10. The device according to claim 8, wherein, The bearer context different from the bearer context associated with the received QoS information and the bearer context associated with the received QoS information belong to the same packet data network PDN connection.

11. The device according to claim 8, wherein, The QoS identifier includes a QoS rule identifier.

12. The apparatus according to claim 8, wherein, The message includes an indication to create a new QoS rule; and wherein the processor is configured to cause the UE to perform the following to discard the QoS configuration: Discard the received QoS information at least based on the determination that an existing QoS rule is associated with the QoS identifier and the QoS identifier is not associated with a bearer context; and Generate an error message indicating that the received QoS information is discarded.

13. The apparatus according to claim 8, wherein The QoS identifier includes a QoS flow identifier.

14. The apparatus according to claim 13, wherein, The message includes an indication to create a new QoS flow description, modify an existing QoS flow description, or delete an existing QoS flow description, and wherein the processor is configured to cause the UE to perform the following to discard the QoS configuration: Discard the received QoS information at least based on the determination that an existing QoS flow description is associated with the QoS identifier and the QoS identifier is associated with a bearer context different from the bearer context associated with the QoS information received in the message; and Generate an error message indicating that the received QoS information is discarded.

15. An apparatus for wireless communication by a user equipment UE, comprising: A unit for receiving, from a network entity in a message, quality of service QoS information, a QoS identifier associated with the QoS information, and a bearer context associated with the QoS information, wherein the QoS information includes parameters mapped from a first radio access technology to corresponding parameters for a second radio access technology; and A unit for discarding the QoS configuration using the QoS information, based on that the UE has been 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 message, wherein the unit for discarding the QoS configuration includes: A unit for 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 message; A unit for discarding the received QoS information; and A unit for generating an error message indicating that the received QoS information is discarded.

16. The device according to claim 15, wherein, The message includes one of the following: a modify bearer context request message, an activate default bearer context request message, or an activate dedicated bearer context request message.

17. The apparatus according to claim 15, wherein The bearer context different from the bearer context associated with the received QoS information and the bearer context associated with the received QoS information belong to the same packet data network (PDN) connection.

18. The device according to claim 15, wherein, The QoS identifier includes a QoS rule identifier.

19. The apparatus according to claim 15, wherein The message includes an indication to create a new QoS rule, and wherein the unit for discarding the QoS configuration includes: A unit for determining to discard the received QoS information based at least on the determination that an existing QoS rule is associated with the QoS identifier and the QoS identifier is not associated with a bearer context; and A unit for generating an error message indicating that the received QoS information is discarded.

20. The apparatus according to claim 15, wherein The QoS identifier includes a QoS flow identifier.

21. The device according to claim 20, wherein The message includes an indication to create a new QoS flow description, modify an existing QoS flow description, or delete an existing QoS flow description, and wherein the unit for discarding the QoS configuration includes: A unit for determining to discard the received QoS information based at least on the determination that an existing QoS flow description is associated with the QoS identifier and the QoS identifier is associated with a bearer context different from the bearer context associated with the QoS information received in the message; and A unit for generating an error message indicating that the received QoS information is discarded.

22. An apparatus for wireless communication used by a user equipment (UE), comprising: A processor configured to cause the UE to: Receive quality of service (QoS) information, a QoS identifier associated with the QoS information, and a bearer context associated with the QoS information from a network entity 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 includes parameters mapped from a first radio access technology to corresponding parameters for a second radio access technology, and wherein the QoS identifier includes a QoS flow identifier; and Update a QoS configuration using the QoS information based on whether the UE has been 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, the activate default bearer context request message, or the activate dedicated bearer context request message, wherein the processor is configured to cause the UE to perform the following to update the QoS configuration: Determine that an existing QoS rule is associated with the QoS identifier, and 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 message; Discard the received QoS information; and Generate an error message indicating that the received QoS information is discarded.

23. The apparatus according to claim 22, wherein, The bearer context different from the bearer context associated with the received QoS information and the bearer context associated with the received QoS information belong to the same packet data network (PDN) connection.

24. The apparatus according to claim 22, wherein, The QoS identifier includes a QoS rule identifier.

25. The apparatus according to claim 24, wherein, The processor is configured to cause the UE to perform the following to update the QoS configuration: Determine that an existing QoS rule is associated with the QoS identifier and 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; Discard the received QoS information; And Generate an error message indicating that the received QoS information is discarded.

26. The apparatus according to claim 22, 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 Wherein, the processor is configured to cause the UE to perform the following to update the QoS configuration: Determine that an existing QoS rule is associated with the QoS identifier and the QoS identifier is not associated with a bearer context; Discard the received QoS information; and Generate an error message indicating that the received QoS information is discarded.

27. A method for wireless communication by a user equipment UE, comprising: Receiving, in one of a modify bearer context request message, an activate default bearer context request message, or an activate dedicated bearer context request message, quality of service (QoS) information, a QoS identifier associated with the QoS information, and a bearer context associated with the QoS information, wherein the QoS information includes parameters mapped from a first radio access technology to corresponding parameters for a second radio access technology, and wherein the QoS identifier includes a QoS flow identifier; and Updating the QoS configuration using the QoS information based on whether the UE has been 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, wherein updating the QoS configuration includes: Determine that an existing QoS rule is associated with the QoS identifier, and 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 message; Discard the received QoS information; and Generate an error message indicating that the received QoS information is discarded.

28. The method according to claim 27, wherein, The bearer context different from the bearer context associated with the received QoS information and the bearer context associated with the received QoS information belong to the same packet data network (PDN) connection.

29. The method according to claim 27, wherein, The QoS identifier includes a QoS flow identifier.

30. The method according to claim 29, wherein, Updating the QoS configuration includes: Determine that an existing QoS flow description is associated with the QoS identifier and the QoS identifier is 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, and is associated with the stored QoS flow description of the bearer context; Discard the received QoS information; and Generate an error message indicating that the received QoS information is discarded.

31. The method according to claim 27, 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 of creating a new QoS rule; And Updating the QoS configuration includes: Determine that an existing QoS rule is associated with the QoS identifier and the QoS identifier is not associated with a bearer context; Discard the received QoS information; and Generate an error message indicating that the received QoS information is discarded.

Images