MASKING

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This patent application claims priority to U. S. Utility patent application with Serial No. 16/141,380, filed September 25, 2018, which is anon-provisional application of, and claims priority to, U.S. Provisional Patent Application Serial No. 62/589,445, filed November 21, 2017. Application Serial No. 16/141,380 and 62/589,445 are fully incorporated herein by reference.

BACKGROUND

[0002] A quality of service (QoS) class identifier (QCI) is a scalar value that is used to prioritize services within a communication network. 3GPP 23.401 defines QCI values from 0 to 255. QCI values 1-9 are standardized, QCI values 10-127 are reserved, and QCI values 128-254 are defined as operator-specific QCIs. The extended QCI values (QCI values 10-254) enable a communication network to define specific priorities within the communication network. For example, a subscriber assigned a QCI value of 150 may be given a higher priority within the communication network than a subscriber assigned a QCI value of 200. While there may be significant value to utilizing extended QCI values within a communication network, many user devices are not configured to support the extended QCI values. For example, many mobile phones only recognize QCI values between 1 and 9. When a communication network attempts to use an extended QCI value when establishing a session with a user device that does not support the extended QCI value, errors may occur or the user device may crash.

BRIEF DESCRIPTION OF THE DRAWINGS

[0003] The detailed description is set forth with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different figures indicates similar or identical items or features.

[0004] FIG. l is a block diagram of an example communication network configured to implement extended quality of service (QoS) class identifier (QCI) masking.

[0005] FIG. 2 is a block diagram of an example communication network system configured to implement extended QCI masking. [0006] FIG. 3 is a flow diagram of an example process for implementing extended

QCI masking across multiple components of an example communication network.

[0007] FIG. 4 is a flow diagram of an example process for implementing extended

QCI masking as performed by a mobility management entity of an example communication network.

DETAILED DESCRIPTION

Introduction

[0008] Systems and methods discussed herein are directed to extended quality of service (QoS) class identifier (QCI) masking.

[0009] A QCI is a scalar value that is used to prioritize services within a communication network. 3GPP 23.401 defines QCI values from 0 to 255. QCI values 1-9 are standardized, QCI values 10-127 are reserved, and QCI values 128-254 are defined as operator-specific QCIs. QCI values 1-9 are referred to herein as “standard QCI values,” while QCI values 10-254 are referred to herein as“extended QCI values.” The extended QCI values enable a communication network to define specific priorities within the communication network. For example, a subscriber assigned a QCI value of 150 may be given a higher priority within the communication network than a subscriber assigned a QCI value of 200. Any number of performance parameters associated with any number of network components may be associated with an extended QCI value. While there may be significant value to utilizing extended QCI values within a communication network, many user devices are not configured to support the extended QCI values. For example, many mobile phones only recognize QCI values between 1 and 9. When a communication network attempts to use an extended QCI value when establishing a session with a user device that does not support the extended QCI value, errors may occur or the user device may crash. By using an extended QCI value within the network system, but masking that value in communications to the device, the network is able to take full advantage of the extended QCI values and provide service priorities in accordance therewith. The user device (e.g., a mobile phone) is provided a standard QCI value, which masks (or hides) the extended QCI value that is being used on the network.

[0010] For example, a communication network provider may offer different service plans having different prices, and corresponding different levels of service. A first subscriber may pay a premium price for a premium service plan in which Internet data is given a higher priority over subscribers to a basic service plan. In this scenario, a mobile phone associated with the basic service plan and a mobile phone associated with the premium service plan may both be provided the same standard QCI value, however, the network associates different extended QCI values with the two sessions (or a standard QCI value with the session associated with the basic service plan and an extended QCI value with the session associated with the premium service plan). In this way, when processing Internet data for the two sessions, the network prioritizes the data for the session associated with the premium service plan over the data for the session associated with the basic service plan. There is no difference in how the mobile phones process the data based on QCI values, so providing both mobile devices with the same standard QCI values does not have a negative impact.

[0011] In the described example implementations, a communication session between a user device and a communication network may be established such that the communication network associates an extended QCI value with the session while communicating a standard QCI value to the user device. By mapping the extended QCI values to standard QCI values, the communication network is able to prioritize service based on the extended QCI value while masking the extended QCI value with a standard QCI value that is communicated to the user device. Communicating the standard QCI value to the user device prevents errors that may occur if the user device does not support extended QCI values.

Example Network Environment

[0012] FIG. 1 illustrates an example network environment 100 in which extended QCI masking may be implemented. Example network environment 100 includes a user device 102 and a communication network 104. Communication network 104 includes any number of access points (evolved Node B (eNB)) 106(1), 106(2), 106(3), ... , 106(N), a mobility management entity (MME) 108, a home subscriber server (HSS) 110, a policy and charging rules function (PCRF) 112, and one or more gateways 114. In the illustrated example, each component of the communication network 104 may be configured to support extended QCI values, and thus may be configured to prioritize service among active sessions based on extended QCI values associated with the active sessions. For example, each network component that supports extended QCI values may maintain priority data that defines, for each extended QCI value, one or more prioritization parameters, which are applied to a communication session having the particular extended QCI value.

[0013] Each eNB 106 is configured to enable communication between the user device 102 and the communication network 104. When a user device is powered on, the user device sends, and an eNB receives, a request to attach and activate a session with the communication network 104.

[0014] MME 108 is configured to perform authentication and authorization when a user device requests a new session with the communication network 104 and to perform session management. In the illustrated example, the MME 108 also maintains extended QCI mapping 116, which maps extended QCI values to standard QCI values. In the example described herein, extended QCI values may include values between 10 and 255, each of which may be mapped to a standard QCI value between 6 and 9. Standard QCI values 1-5 are standardized for specific types of data, while QCI values 6-9 provide more flexibility. Accordingly, in the example implementation described herein, each extended QCI value is mapped to a standard QCI value between 6 and 9.

[0015] HSS 110 is configured to maintain subscriber account information, which may include, for example, subscriber profile data, billing data, subscription data, and so on. In the illustrated example, subscriber profile data is maintained in a subscriber profile data repository 118 within the HSS 110. The subscriber profile data repository 118 may also include a subscriber extended QCI value 120, which is an extended QCI value that is associated with the subscriber account. Any number of business policies may be used to assign extended QCI values to subscriber accounts. As one example, a communication network 104 may offer a standard membership, a premium membership, and an economy membership, with the economy membership being less expensive and having a lower quality of service guarantee as compared to the standard membership, and the premium membership being more expensive and having a higher quality of service guarantee as compared to the standard membership. In this example, subscribers who subscribe to the standard membership may be assigned an extended QCI value of 200, subscribers who subscribe to the premium membership may be assigned an extended QCI value of 150, and subscribers who subscribe to the economy membership may be assigned an extended QCI value of 250. [0016] Policy and charging rules function (PCRF) 112 is configured to apply and enforce various policies and rules with regard to each subscriber active on the communication network 104 at any given time.

[0017] Gateways 114 is representative of any number of serving gateways (SGW) and/or packet data network (PDN) gateways. Gateways 114 are configured to support transmission and receipt of various types of data associated with any number of active subscriber sessions within the communication network 104.

[0018] FIG. 2 illustrates select components of a communication network system 104 configured to implement extended QCI masking as described herein. Example communication network system 104 includes one or more processors 202, any number of communication interfaces 204, any number of gateways 114, and memory 206 communicatively coupled to the one or more processors 202. Memory 206 may include, for example, subscriber profile data repository 118, MME 108, and PCRF 112. Subscriber profile data repository 118 includes subscriber extended QCI value 120. MME 108 includes extended QCI mapping 116. In an alternate example implementation, the extended QCI mapping 116 may be maintained in the subscriber profile data repository 118, such that, for example, the subscriber profile data repository 118 maintains, for an individual subscriber, both an extended QCI value and a standard QCI value.

[0019] Communication interfaces 204 enable communication between components of the communication network system 104 and communication between the communication network system 104 and other devices (e.g., user devices).

[0020] Subscriber profile data repository 118 maintains user profile data for user devices associated with the communication network system 104. User profile data may include, for example, user name, phone number, user device ID, billing data, and so on. In addition, subscriber profile data repository includes subscriber extended QCI value 120, which specifies an extended QCI value associated with the user account.

[0021] MME 108 is configured to provide authentication and authorization, and to provide session management. In the illustrated example, the MME 108 also maintains the extended QCI mapping 116, which maps extended QCI values, which are associated with subscriber accounts, to standard QCI values, which are supported by user devices.

[0022] PCRF 112 is configured to apply and enforce various policies and rules with regard to each subscriber active on the communication network 104 at any given time. Example Processes

[0023] FIG. 3 is a flow diagram illustrating an example series of communications between components of the example environment illustrated in FIG. 1 to perform extended QCI masking.

[0024] When user device 102 is initially powered on, the user device 102 sends an attach request 302 to an eNB 106, as indicated by arrow 304. As indicated by arrow 306, the eNB 106 forwards the attach request 302 to the MME 108.

[0025] In response to receiving the attach request 302, the MME authorizes and authenticates the user device 102 by sending an update location request (ULR) 308 to the HSS 110, as indicated by arrow 310.

[0026] In response to receiving the ULR 308, the HSS 110 determines the extended QCI associated with the subscriber account indicated in the ULR 308. For example, the HSS 110 looks up the extended QCI value in the subscriber profile data repository 118. As indicated by arrow 312, the HSS 110 then returns to the MME 108 an update location answer (ULA) 314 that includes the subscriber’s extended QCI value.

[0027] The MME 108 then sends a create session request (CSR) 316, with the subscriber’s extended QCI value to the SPGW 114, as indicated by arrow 318.

[0028] In response to receiving the CSR 316, the SPGW 114 then sends a credit control request (CCR) 320 with the subscriber’s extended QCI value to the PCRF 112, as indicated by arrow 322. In some examples, the PCRF 112 may then overwrite the extended QCI value, for example, if the extended QCI value assigned to the subscriber account has changed since it was last retrieved by the HSS 110.

[0029] The PCRF 112 then sends a CCR 324 to the SPGW 114, as indicated by arrow 326. CCR 324 includes the extended QCI value, which may have been updated by the PCRF 112.

[0030] The SPGW 114 then sends a create session response 328 that includes the extended QCI to the MME 108, as indicated by arrow 330.

[0031] In response to receiving the create session response 328, the MME 108 determines the standard QCI value to which the extended QCI value is mapped. For example, the MME 108 queries the extended QCI mapping 116 to determine a standard QCI value to which the extended QCI value is mapped. The MME 108 then sends an initial context setup message (ICSM) 332 to the Enb 106, as indicated by arrow 334, and sends a non-access stratum (NAS) message 336 (inside the initial context setup message) to the user device 102 with the mapped standard QCI value, as indicated by arrow 338.

[0032] FIG. 4 is a flow chart of an example process 400 for implementing extended QCI masking.

[0033] At block 402, a request to attach to a communication network is received. For example MME 108 receives an attach request from a user device 102 via an eNB 106.

[0034] At block 404, an extended QCI value associated with the subscriber account is determined. For example, the MME 108 sends a ULR to the HSS 110, and the HSS 110 returns a ULA that includes the extended QCI associated with the subscriber account, as stored in the subscriber profile repository 118.

[0035] At block 406, a session is established within the communication network using the extended QCI value. For example, the MME 108 communicates the extended QCI value to the PCRF 112 and the gateways 114 to establish the session. The MME also sends the extended QCI value to the eNB 106.

[0036] At block 408, a mapped standard QCI value is determined. For example, the MME 108 identifies the extended QCI value in the extended QCI mapping 116 to determine the standard QCI value to which the extended QCI value is mapped.

[0037] At block 410, the session is established with the user device using the mapped standard QCI value. For example, the MME 108 sends to the user device 102, an NAS message that includes the standard QCI value.

[0038] Some or all operations of the processes described above can be performed by execution of computer-readable instructions stored on a computer storage medium, as defined below. The term“computer-readable instructions” as used in the description and claims, include routines, applications, application modules, program modules, programs, components, data structures, algorithms, and the like. Computer-readable instructions can be implemented on various system configurations, including single processor or multiprocessor systems, minicomputers, mainframe computers, personal computers, hand-held computing devices, microprocessor-based, programmable consumer electronics, combinations thereof, and the like. Memory 206 is an example of computer storage media. [0039] The computer storage media may include volatile memory (such as random access memory (RAM)) and/or non-volatile memory (such as read-only memory (ROM), flash memory, etc.)· The computer storage media may also include additional removable storage and/or non-removable storage including, but not limited to, flash memory, magnetic storage, optical storage, and/or tape storage that may provide non volatile storage of computer-readable instructions, data structures, program modules, and the like.

[0040] A non-transient computer storage medium is an example of computer- readable media. Computer-readable media includes at least two types of computer- readable media, namely computer storage media and communications media. Computer storage media includes volatile and non-volatile, removable and non removable media implemented in any process or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, phase change memory (PRAM), static random-access memory (SRAM), dynamic random-access memory (DRAM), other types of random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information for access by a computing device. In contrast, communication media may embody computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transmission mechanism. As defined herein, computer storage media do not include communication media.

[0041] The computer-readable instructions stored on one or more non-transitory computer storage media that, when executed by one or more processors, may perform operations described above with reference to FIGs. 1-4. Generally, computer-readable instructions include routines, programs, objects, components, data structures, and the like that perform particular functions or implement particular abstract data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement the processes. CONCLUSION

[0042] Although the subject maher has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject maher defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claims.