Adaptive throughput and bandwidth for an improved category of mobile devices

Abstract

Method for performing wireless communication between a user equipment device (UE) (106) and a wireless communication network (100), the method comprising: through the UE (106): Communicate (702) to the wireless communication network (100) of a device category of the UE (106), wherein the device category specifies different parameters for devices that implement each of a multitude of application classes; Establishing (704) a communication channel with the wireless communication network (100), wherein the communication channel has parameters that are determined at least partially based on the device category of the UE (106), wherein the parameters include a fixed bandwidth; to the wireless communication network (100) after the establishment (704) of the communication channel, indicate (708) that the UE (106) implements a specific application, wherein the specific application belongs to a first class of the plurality of application classes; and Receiving (710) an indication from the wireless communication network (100) that the communication channel parameters have changed, wherein the received indication is in response to the indication (708) that the UE (106) is implementing the specific application, wherein changed parameters include an increased bandwidth.

Description

AREA OF INVENTION

[0001] The present application relates to wireless communication and in particular to a new and / or improved category of devices in 3GPP wireless communication. DESCRIPTION OF RELATED TECHNOLOGY

[0002] The use of wireless communication systems is increasing rapidly. In recent years, wireless devices such as smartphones and tablet computers have become increasingly complex. In addition to supporting telephone calls, many mobile devices (i.e., user equipment devices or UEs) now provide access to the internet, email, text messaging, and navigation using the Global Positioning System (GPS), and are capable of running complex applications that utilize these functionalities. Furthermore, there are numerous different technologies and standards for wireless communication. Some examples of wireless communication standards include GSM, UMTS (WCDMA, TDS-CDMA), LTE, LTE Advanced (LTE-A), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), IEEE 802.11 (WLAN or Wi-Fi), IEEE 802.16 (WiMAX), Bluetooth™, and others.

[0003] Several wireless communication standards, such as LTE, use packet-switched networks. The LTE specification defines a number of user equipment (UE) categories, with each LTE category defining the overall performance and capabilities of a UE. These LTE categories define the standards by which a particular handset, dongle, or other equipment operates within the communication system. The LTE categories, or UE classes, are used to ensure that the base station (e.g., enhanced NodeB, eNodeB, or eNB) can communicate correctly with the user equipment. The UE relays the LTE UE category information to the base station, enabling the base station to determine the UE's performance characteristics and communicate with it accordingly. This allows the base station to communicate using capabilities it knows the UE possesses.While users may not be particularly aware of their UE's category, the UE's performance corresponds to its category and allows the base station to communicate effectively with all connected UEs. Therefore, LTE UE category information can be important for UE performance.

[0004] It is less likely that the base station will communicate beyond the power level specified by the UE category. Therefore, it may be desirable to introduce one or more new UE categories to provide operational flexibility. Improvements in this area are thus desirable.

[0005] Publication US 2010 / 0057 485 A1 reveals methods and devices for machine-to-machine-based communication service classes. SUMMARY OF THE INVENTION

[0006] The invention is defined in the independent claims. Advantageous embodiments are defined in the dependent claims. Embodiments are presented herein, inter alia, for methods for wireless communication devices that communicate, for example, with mobile communication base stations according to a new device category, and for devices implementing the methods. Embodiments are further presented herein for wireless communication systems comprising user equipment devices (UE devices) and base stations that communicate with each other within the wireless communication systems.

[0007] In various embodiments, a user equipment device (UE device) can communicate according to the new device category, meeting specified QoS (quality of service) requirements while also fulfilling specified power transfer balance requirements and additional optimization requirements. The new device category can identify the UE device as a body-worn device. According to some embodiments, LTE Category M can be extended to support non-MTC operations performed by body-worn devices. For example, the new device category can support UE mobility and prohibit access control.

[0008] Additional extensions can be implemented in response to a notification from the UE indicating that it is implementing a specific application, such as VoLTE, or a near-real-time application, such as audio streaming. In some scenarios, the notification may include the UE displaying a specific QCI value. In other scenarios, the notification may include the UE being connected to a specific APN.

[0009] A method for conducting wireless communication between a user equipment device (UE) and a wireless communication network is disclosed. The method may include the UE communicating a device category of the UE to the wireless communication network, wherein the device category identifies the UE as a body-worn device. The UE may establish a communication channel with the wireless communication network, wherein the communication channel has parameters that are determined at least partially based on the device category of the UE. The parameters may include a fixed bandwidth. After establishing the communication channel, the UE may indicate to the wireless communication network that the UE is implementing a specific application.For example, indicating that the UE is implementing the specific application may include setting a QCI value and / or requesting a connection to a specific APN. In response to the UE indicating that it is implementing a specific application, the UE may receive a notification from the wireless communication network that the communication channel parameters have changed. For example, receiving the notification that the communication channel parameters have changed may include establishing a dedicated carrier for the specific application. The changed parameters may include increased bandwidth and may include dynamic bandwidth determined by the wireless communication network. In some embodiments, the changed parameters may also include changed Quality of Service (QoS) parameters.

[0010] In some embodiments, the specific application may include a Voice over Internet Protocol (VoIP) application. The UE may use a physical MTC (machine-type communication) downlink control channel (M-PDCCH) to schedule bundled VoIP audio packets.

[0011] A user equipment device (UE) is disclosed, which may include at least one memory and at least one processor coupled to the at least one memory. The at least one processor may be configured to cause the UE to establish a communication channel with a wireless communication network, wherein the communication channel has initial parameters corresponding to a device category of the UE, such as a wearable device category. For example, the initial parameters may include a fixed bandwidth. The at least one processor may further be configured to cause the UE, after establishing the communication channel, to send an initial indication to the wireless communication network, indicating that the UE implements a specific application.For example, indicating that the UE is implementing the specific application may include setting a QCI value. The at least one processor may further be configured to cause the UE to receive a second indication from the wireless communication network, responding to the first indication that the communication channel parameters have changed. For example, the changed parameters may include increased bandwidth and dynamic bandwidth determined by the wireless communication network.

[0012] In some embodiments, the initial parameters may also correspond to a device of the UE device category that implements delay-tolerant applications, and the modified parameters may correspond to a device of the UE device category that implements a Voice-over-Internet Protocol (VoIP) application.

[0013] In some embodiments, the specific application may include a VoIP application, and the at least one processor may further be configured to cause the UE to use an M-PDCCH to schedule bundled VoIP audio packets.

[0014] A non-volatile, computer-readable medium is disclosed that stores program instructions executable by at least one processor of a user equipment device (UE). The program instructions can cause the UE to communicate with a wireless communication network over a communication channel having initial parameters defined by a category for a body-worn device implementing a delay-tolerant application. For example, the initial parameters can include a fixed bandwidth. The program instructions can further cause the UE to initiate the implementation of a Voice-over-Internet Protocol (VoIP) application and send an initial indication to the wireless communication network, over the communication channel with the initial parameters, that the UE is implementing the VoIP application.The program instructions can further instruct the UE to receive a second indication from the wireless communication network, responding to the first indication that the communication channel has changed to include second parameters. For example, the second parameters can include increased bandwidth and can include dynamic bandwidth determined by the wireless communication network. The program instructions can also be executable to instruct the UE to reconfigure its operating settings to communicate with the wireless communication network according to the second parameters in response to receiving the second indication.

[0015] In some embodiments, the second parameters may include the use of a physical MTC downlink control channel (M-PDCCH) for scheduling bundled VoIP audio packets.

[0016] In some embodiments, the program instructions can further cause the UE to initiate the implementation of a time-sensitive, periodic application after receiving the second indication, and to send a third indication to the wireless communication network via the communication channel with the second parameters, indicating that the UE is implementing the time-sensitive, periodic application. The program instructions can further cause the UE to send a fourth indication to the wireless communication network via the communication channel with the second parameters, indicating that the UE has stopped implementing the VoIP application, and to receive a fifth indication from the wireless communication network, responding to the fourth indication that the communication channel has changed to include third parameters that differ from the first and second parameters.

[0017] It should be noted that the techniques described herein can be implemented and / or used in a number of different types of devices, including, but not limited to, base stations, access points, mobile phones, portable media playback devices, tablet computers, body-worn devices and a variety of other computing devices.

[0018] This summary is intended to provide a brief overview of some of the items described in this document. Accordingly, it should be noted that the features described above are merely examples and should not be considered in any way limiting the scope or spirit of the item described herein. Further features, aspects, and advantages of the item described herein will become apparent from the following detailed description, figures, and claims. BRIEF DESCRIPTION OF THE DRAWINGS Fig. Figure 1 illustrates an exemplary (and simplified) system for wireless communication according to some embodiments; Fig. Figure 2 illustrates an exemplary base station communicating with an exemplary wireless user equipment device (UE device) according to some embodiments; Fig. Figure 3 illustrates an exemplary block diagram of a UE according to some embodiments; Fig. Figure 4 illustrates an exemplary block diagram of a base station according to some embodiments; Fig. Figure 5 illustrates a call sequence that represents a procedure for requesting a dedicated carrier according to some embodiments; Fig. Figure 6 illustrates a call flow that represents a procedure for connecting to a specific access point name (APN) according to some embodiments; and Fig. Figure 7 is a flowchart that illustrates a method for performing communication with devices of a body-worn category according to some embodiments.

[0019] While the features described herein are open to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and described in detail herein. It should be understood, however, that the drawings and the detailed description thereto are not intended to be limited to the specific disclosed form, but rather that the invention is intended to cover all modifications, equivalents, and alternatives that fall within the spirit and scope of the subject matter as defined by the attached claims. DETAILED DESCRIPTION OF THE EXECUTION FORMS Acronyms

[0020] This application uses various acronyms. Definitions of the most frequently used acronyms that may appear in this application are provided below: • AP: Access Point • APN: Access Point Name • BS: Base station • DL: Downlink (from BS to UE) • DRB: Data Radio Bearer • EPS: Evolved Packet System • GBR: Guaranteed Bitrate • GSM: Global System for Mobile Communication • IP: Internet Protocol • LAN: Local Area Network • LTE: Long Term Evolution • MME: Mobility Management Entity • M-PDCCH: MTC Physical Downlink Control Channel • MTC: Machine Type Communications • PDCCH: Physical Downlink Control Channel • PDN: Packet Data Network • PGW: PDN Gateway • QCI: QoS Class Identifier • QoS: Quality of Service • RAT: Radio Access Technology • RB: Resource Block • SGW: Serving Gateway • SPS: Semi-Persistent Scheduling • UE: User Equipment • UL: Uplink (from UE to BS) • UMTS: Universal Mobile Telecommunication System • VoIP: Voice over IP • Wi-Fi: “Wireless Local Area Network” RAT (WLAN RAT) based on the standards (IEEE) 802.11 of the “Institute of Electrical and Electronics Engineers” • WLAN: Wireless LAN (Wireless LAN) terms

[0021] The following is a glossary of terms that may appear in the present application: Storage medium – any of the many different types of working memory devices or data storage devices. The term "storage medium" is intended to include an installation medium, such as a CD-ROM, floppy disk, or tape drive; computer system memory or random-access memory, such as DRAM, DDR-RAM, SRAM, EDO-RAM, Rambus-RAM, etc.; non-volatile memory, such as flash memory; magnetic media, such as a hard disk; or optical data storage; registers or other similar types of memory elements, etc. The storage medium may also include other types of memory or combinations thereof. Furthermore, the storage medium may be located in a primary computer system where the programs are executed, or it may be located in a secondary, separate computer system connected to the primary computer system via a network, such as the internet.In the latter case, the second computer system can provide the first computer system with program instructions for execution. The term "storage medium" can include two or more storage media, which may be located in different places, e.g., in different computer systems connected via a network. Carrier medium - a storage medium as described above, as well as a physical transmission medium, such as a bus, a network and / or another physical transmission medium, that transmits signals, such as electrical, electromagnetic or digital signals. Computer system (or computer) – any of the many types of computing or processing systems, including a personal computer system (PC), mainframe system, workstation, network unit, internet unit, personal digital assistant (PDA), television system, grid computing system, or any other device or combination of devices. In general, the term "computer system" can be broadly defined to include any device (or combination of devices) with at least one processor that executes instructions from a storage medium. User equipment (UE) (or "UE device") – any of the many types of computer system devices that are mobile or portable and that perform wireless communication. UEs may also be referred to herein as wireless communication devices. Examples of UE devices include mobile phones or smartphones (e.g., iPhone™, Android™-based phones) and tablet computers, such as iPad™, Samsung Galaxy™, etc., portable gaming devices (e.g., Nintendo DS™, PlayStation Portable™, Gameboy Advance™, iPod™), laptops, body-worn devices (e.g., Apple Watch™, Google Glass™), PDAs, portable internet devices, music players, data storage devices, or other handheld devices, etc.Various other types of devices would fall into this category if they include cellular and / or Wi-Fi communication capabilities and / or other wireless communication capabilities, for example, via short-range radio access technologies (SRATs), such as BLUETOOTH™, etc. In general, the term "UE" or "UE device" can be broadly defined to include any electronic, computing, and / or telecommunications device (or a combination of devices) that can be easily transported by a user and is capable of wireless communication. Body-worn device – refers to a computer system or component thereof that is designed or intended to be worn by a user, such as clothing or an accessory, and that performs wireless communication. Examples of body-worn devices include smartwatches (e.g., Apple Watch™), smartglasses (e.g., Google Glass™), fitness trackers with wireless communication capabilities, etc. Body-worn devices may sometimes include functionality that depends on physical contact with the user, such as monitoring heart rate or other health metrics. Body-worn devices may also sometimes include functionality that depends on being worn at a specific location on the user's body, such as on the user's wrist or at a fixed location relative to the user's eyes.Mobile phones, smartphones and tablet computers with classic form factors are not considered to be wearable devices, even if they are carried in the user's clothing (e.g. in a pocket). Limited power balance – encompasses the full breadth of its usual meaning and includes at least one characteristic of a wireless device (e.g., a UE) that has limited communication capabilities or limited performance relative to a device that does not have a limited power balance or relative to devices for which a Radio Access Technology (RAT) standard has been developed. A UE with a limited power balance may have relatively limited receive and / or transmit capabilities, which may be due to one or more factors such as device design, device size, battery / accumulator size, antenna size or design, transmit power, receive power, and / or other factors.These devices may be referred to herein as devices with a "limited power transfer balance" (or "restricted power transfer balance"). A device may inherently have a limited power transfer balance due to its size, battery / accumulator power, and / or transmit / receive power. For example, a smartwatch communicating with a base station over LTE or LTE-A may inherently have a limited power transfer balance due to its reduced transmit / receive power and / or reduced antenna. Body-worn devices, such as smartwatches, are generally devices with a limited power transfer balance. Current conditions of the transmission medium may also be a contributing factor.It is noted that the term "limited power transfer balance" includes or encompasses power limitations, so that a power-limited device can be regarded as a device with a limited power transfer balance. Base station (BS) - The term 'base station' encompasses the full breadth of its usual meaning and includes at least one wireless communication station installed in a fixed location and used for communication as part of a wireless telephone system or radio system. Processing element – ​​refers to various elements or combinations of elements capable of performing a function in a device, such as a user equipment device or a mobile network device. Processing elements may include, for example: processors and associated memory, sections or circuits of individual processor cores, entire processor cores, processor arrays, circuits such as an application-specific integrated circuit (ASIC), programmable hardware elements such as a field-programmable gate array (FPGA), and any of the many combinations of the foregoing. Wireless device (or wireless communication device) – any of the many types of computer system devices that performs wireless communication using WLAN communication, SRAT communication, Wi-Fi communication, and the like. As used herein, the term “wireless device” can refer to a UE device, as defined above, or to a stationary device, such as a stationary wireless client or wireless base station. For example, a wireless device can be any type of wireless station in an 802.11 system, such as an access point (AP) or client station (UE), or any type of wireless station in a cellular communication system that communicates according to a cellular access technology (e.g., LTE, CDMA, GSM), such as a base station or a mobile phone. Wi-Fi – The term “Wi-Fi” encompasses the full breadth of its usual meaning and includes at least one wireless communication network or RAT (Radio Access Technology) served by wireless LAN (WLAN) access points, providing connectivity to the internet through these access points. State-of-the-art Wi-Fi networks (or WLAN networks) are based on IEEE 802.11 standards and are marketed under the name “Wi-Fi.” A Wi-Fi network (WLAN network) is distinct from a mobile network. BLUETOOTH™ - The term “BLUETOOTH™” has the full breadth of its usual meaning and includes at least any one of the various implementations of the Bluetooth standard, including Bluetooth Low Energy (BTLE) and Bluetooth Low Energy for Audio (BTLEA), including, but not limited to, future implementations of the Bluetooth standard. Personal Area Network (PAN) – The term "Personal Area Network" encompasses the full breadth of its usual meaning and includes at least one of several types of computer networks used for data transmission between devices such as computers, phones, tablets, and input / output devices. Bluetooth is a specific example of a PAN. A PAN is an example of a short-range wireless communication technology. Automatic – refers to an action or operation performed by a computer system (e.g., software executed by the computer system) or a device (e.g., switching logic, programmable hardware elements, ASICs, etc.) without user input that directly defines the action or operation. Thus, the term "automatic" contrasts with an operation performed or defined manually by the user, where the user provides input to directly execute the operation. An automatic procedure may be initiated by user input, but the subsequent actions performed "automatically" are not defined by the user; that is, they are not performed "manually," with the user specifying each action to be carried out.For example, a user filling out an electronic form by selecting each field and providing input that specifies information (e.g., by typing information, selecting checkboxes, choosing a radio button, etc.) is manually filling out the form, even though the computer system needs to update the form in response to the user's actions. The form can be automatically filled out by the computer system, where the computer system (e.g., software running on the computer system) analyzes the form's fields and completes the form entirely without any user input specifying the answers to the fields. As mentioned above, the user can request automatic form filling but is not involved in the actual process of filling out the form (e.g., the user does not manually specify answers for fields; these are filled in automatically).The following description provides various examples of operations that are performed automatically in response to actions taken by the user. Station (STA) – The term “station” refers to any device capable of wireless communication, for example, by using the 802.11 protocol. A station can be a laptop, desktop PC, PDA, access point, Wi-Fi phone, or any type of device similar to a UE. An STA can be fixed, mobile, portable, or body-worn. In general, in wireless networking terminology, a station (STA) broadly encompasses any device capable of wireless communication, and the terms station (STA), wireless client (UE), and node (BS) are therefore often used interchangeably. Configured to - Various components can be designated as "configured". "Configured to" may be described as performing one or more tasks. In such contexts, "configured to" is a broad term that generally means "possessing a structure that" performs the task or tasks during operation. Therefore, the component may be configured to perform the task even if it is not currently performing that task (e.g., a set of electrical conductors may be configured to electrically connect one module to another, even if the two modules are not connected). In some contexts, "configured to" may be a broad term referring to a structure that generally means "possessing switching logic that" performs the task or tasks during operation. Therefore, the component may be configured to perform the task even if it is not currently powered on.In general, the switching logic that forms the structure "configured to" accordingly can include hardware circuits.

[0022] For convenience, various components may be described as performing a task or tasks. Such descriptions should be interpreted as including the phrase "configured to." The citation of a component that is configured to perform one or more tasks is expressly not intended to imply an interpretation under 35 USC § 112, paragraph six, for that component. Figures 1 and 2 - Exemplary communication system

[0023] Fig. Figure 1 illustrates an exemplary (and simplified) wireless communication system according to some embodiments. It is noted that the system is characterized by Fig. 1 merely represents a specific example of a possible system and embodiments can be implemented in any of the many systems, as desired.

[0024] As shown, the exemplary wireless communication system includes a base station 102 that communicates via a transmission medium with one or more user devices 106-1 to 106-N. Each of these user devices may herein be referred to as a “user equipment” (UE) or UE device. Thus, the user devices 106 are referred to as UEs or UE devices. Several of the UE devices may operate according to a new UE category, as detailed herein.

[0025] Base Station 102 can be a Base Transceiver Station (BTS) or a Cell Tower and may include hardware that enables wireless communication with User Equipment (UEs) 106A to 106N. Base Station 102 may also be equipped to communicate with a Network 100 (e.g., among various possibilities, with a mobile network operator's core network, a telecommunications network such as a Public Switched Telephone Network (PSTN), and / or the Internet). Thus, Base Station 102 can facilitate communication between User Equipment and / or between User Equipment and Network 100. The communication area (or coverage area) of the Base Station may be referred to as a "cell."As also used herein, from the perspective of the UEs, a base station can sometimes be considered to represent the network insofar as uplink and downlink communication of the UE is involved. Thus, a UE communicating with one or more base stations in the network can also be interpreted as the UE communicating with the network.

[0026] The base station 102 and the user devices can be configured to communicate over the transmission medium using any of the many radio access technologies (RATs), also known as wireless communication technologies or telecommunications standards, such as GSM, UMTS (WCDMA), LTE, LTE-Advanced (LTE-A), 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), Wi-Fi, WiMAX, etc. In some embodiments, the base station 102 communicates with at least one user device using improved UL (uplink) and DL (downlink) decoupling, preferably via LTE or a similar RAT standard.

[0027] The UE 106 can be capable of communicating using multiple wireless communication standards. For example, a UE 106 can be configured to communicate using one or both of a 3GPP cellular communication standard (such as LTE) or a 3GPP2 cellular communication standard (such as a cellular communication standard from the CDMA2000 family of cellular communication standards). In some embodiments, the UE 106 can be configured to communicate with the Base Station 102 according to at least one new and improved category designation / definition of the UE 106, as described herein.The Base Station 102 and other similar base stations operating according to the same or a different mobile communication standard can thus be provided as one or more networks of cells capable of providing a continuous or almost continuous, overlapping service to the UE 106 and similar devices over a wide geographical area using one or more mobile communication standards.

[0028] The UE 106 can also be configured to communicate using WLAN, BLUETOOTH™, one or more global navigation satellite systems (GNSS, e.g., GPS or GLONASS), one and / or more mobile television radio standards (e.g., ATSC-M / H or DVB-H), etc. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0029] Fig. Figure 2 illustrates an exemplary user equipment 106 (e.g., one of the devices 106-1 to 106-N) communicating with the base station 102 according to some embodiments. The UE 106 may be a device with wireless network connectivity, such as a mobile phone, a handheld device, a computer, or a tablet, or virtually any type of wireless device. The UE 106 may include a processor configured to execute program instructions stored in memory. The UE 106 may perform some or all of the method execution modes described herein by executing such stored instructions.Alternatively or additionally, the UE 106 may include a programmable hardware element, such as a field-programmable gate array (FPGA), configured to perform any of the procedure implementations described herein or any part of any of the procedure implementations described herein. The UE 106 may be configured to communicate using any of several wireless communication protocols. For example, the UE 106 may be configured to communicate using two or more of CDMA2000, LTE, LTE-A, WLAN, or GNSS. Other combinations of wireless communication standards are also possible.

[0030] The UE 106 can include one or more antennas for communicating using one or more wireless communication protocols according to one or more RAT standards. In some embodiments, the UE 106 can share one or more parts of a receive chain and / or transmit chain under multiple wireless communication standards. The shared radio device can include a single antenna or multiple antennas (e.g., for MIMO) for performing wireless communication. Alternatively, the UE 106 can include separate transmit and / or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol with which it is configured to communicate.Alternatively, the UE 106 can include one or more radio devices shared by multiple wireless communication protocols and one or more radio devices used exclusively by a single wireless communication protocol. For example, the UE 106 can include one shared radio device for communicating using either LTE or CDMA2000 1xRTT and separate radio devices for communicating using either Wi-Fi or BLUETOOTH™. Other configurations are also possible. Figure 3 - Block diagram of an example lesson

[0031] Fig. Figure 3 illustrates a block diagram of an exemplary UE 106 according to some embodiments. As shown, the UE 106 can include a system-on-a-chip (SOC) 300, which can include sections for various purposes. As shown, the SOC 300 can, for example, include one or more processors 302, which can execute program instructions for the UE 106, and a display switching logic 304, which can perform graphics processing and provide display signals to the display 360. The one or more processors 302 can also be connected to a memory management unit (MMU) 340, which can be configured to receive addresses from the one or more processors 302 and assign these addresses to memory locations (e.g.,to translate in a memory 306, a read-only memory (ROM) 350, a NAND flash memory 310, and / or be coupled with other circuits or devices, such as the display switching logic 304, a radio device 330, a connector interface 320, and / or a display 360. The MMU 340 can be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 340 can be enclosed as a section of the one or more processors 302.

[0032] As shown, the SOC 300 can be coupled with various other circuits of the UE 106. For example, the UE 106 can include various types of memory (e.g., including the NAND flash 310), a connector interface 320 (e.g., for coupling with the computer system), the display 360, and switching logic for wireless communication, such as radio switching logic 329 and 330 (e.g., for LTE, LTE-A, CDMA2000, BLUETOOTH™, Wi-Fi, GPS, etc.). The UE device 106 can include at least one antenna (e.g., 335a) and possibly multiple antennas (e.g., illustrated by antennas 335a and 335b) for performing wireless communication with base stations and / or other devices. Antennas 335a and 335b are shown as examples, and the UE device 106 can include more antennas. Collectively, the one or more antennas are referred to as antenna 335.For example, the UE device 106 can use the antenna 335 to perform wireless communication using the radio switching logic 329 and 330. As noted above, in some embodiments the UE can be configured to communicate using multiple wireless communication standards.

[0033] As further described herein, the UE 106 (and / or the base station 102) may include hardware and software components for implementing methods for communication between the UE 106 (and / or the base station 102), at least according to a new and improved category designation of the UE 106, as further described herein. The one or more processors 302 of the UE device 106 may be configured to implement some or all of the methods described herein, for example, by executing program instructions stored on a storage medium (e.g., a non-volatile, computer-readable storage medium). In other embodiments, the one or more processors 302 may be configured as a programmable hardware element, such as an FPGA (field-programmable gate array) or an ASIC (application-specific integrated circuit).Furthermore, one or more 302 processors can be combined with other components, as in . Fig. 3 shown, coupled and / or cooperating to implement communication through the UE 106, corresponding to a new, improved category designation of UE 106, wherein this communication includes decoding physical control channels according to various embodiments disclosed herein. The one or more processors 302 may also implement various other applications and / or end-user applications running on the UE 106.

[0034] In some embodiments, the 329 and 330 radio switching logic units can include separate control units dedicated to controlling communication for different respective RAT standards. For example, the 330 radio switching logic unit, as described in Fig. Figure 3 shows a cellular control unit (e.g., an LTE control unit), and the radio switching logic 329 can include a Wi-Fi control unit and a BLUETOOTH™ control unit. In at least some embodiments, one or more or all of these control units can be implemented as respective integrated circuits (ICs or chips for short) that communicate with each other and with the SOC 300 (and more specifically with the one or more processors 302), as further described below. For example, the Wi-Fi control unit can communicate with the cellular control unit via a cell ISM link or a WCI interface, and / or the BLUETOOTH™ control unit can communicate with the cellular control unit via a cell ISM link, etc.While three separate control units are illustrated in the radio switching logic 329 and 330, other embodiments have fewer or more similar control units for various different RATs that may be implemented in the UE device 106. Figure 4 - Block diagram of an example base station

[0035] Fig. Figure 4 illustrates a block diagram of an exemplary mobile communication base station 102 according to some embodiments. It is noted that the base station is Fig. Figure 4 is only one example of a possible base station. As shown, the base station 102 can include one or more processors 404 that can execute program instructions for the base station 102. The one or more processors 404 can also be coupled to a memory management unit (MMU) 440, which can be configured to receive addresses from the one or more processors 404 and translate these addresses into locations in a memory (e.g., in a memory 460 and a read-only memory (ROM) 450), or to other circuits or devices.

[0036] The base station 102 can include at least one network port 470. The network port 470 can be configured to establish a connection to a telephone network and to provide access to the telephone network to a plurality of devices, such as the UE devices 106, as described above in the Fig. 1 and Fig. 2 described. The network port 470 (or an additional network port) can be additionally or alternatively configured to establish a connection to a mobile network, such as a mobile network operator's core network. The core network can provide mobility-related services and / or other services to multiple devices, such as the UE devices 106. In some cases, the network port 470 can establish a connection to the telephone network via the core network, and / or the core network can provide a telephone network (e.g., for use by other UE devices served by the mobile network operator).

[0037] The base station 102 can include at least one antenna 434 and possibly several antennas. The at least one antenna 434 can be configured to operate as a wireless transceiver and can further be configured to communicate with the UE devices 106 via a radio device 430. The antenna 434 communicates with the radio device 430 via a communication chain 432. The communication chain 432 can be a receive chain, a transmit chain, or both. The radio device 430 can be configured to communicate using various wireless telecommunications standards, including, but not limited to, LTE, LTE-A, WCDMA, CDMA2000, etc.The processor 404 of the base station 102 can be configured to implement some or all of the procedures described herein for the base station 102 in order to communicate with a UE device belonging to a new and / or improved category of devices capable of adaptively improving power consumption, power transfer balance management, and performance during wireless communication, for example, by executing program instructions stored on a memory medium (e.g., a non-volatile, computer-readable memory medium). Alternatively, the processor 404 can be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), an ASIC (Application Specific Integrated Circuit), or a combination thereof.In the case of certain RATs, for example Wi-Fi, the base station 102 can be configured as an access point (AP), in which case the network port 470 can be implemented to provide access to a wide area network and / or one or more local area networks. For example, it can include at least one Ethernet port, and the radio device 430 can be configured to communicate in accordance with the Wi-Fi standard. The base station 102 can operate according to the various methods disclosed herein for communicating with mobile devices of a wider range of device categories. Device categories

[0038] There are many different device category definitions for LTE devices. For example, at least categories 1 through 17 are designated for smartphones, and most smartphones operate according to one of categories 2 through 8. In other words, smartphones typically operate as a device belonging to one of categories 2 through 8. Category M (Cat M1) is commonly used for machine-type communication (MTC) devices such as soda machines, smart meters, etc., and is defined by the LTE technical specifications, including 3GPP TS 36.306 V13.1.0 and 3GPP TS 36.133 V13.3.0, both of which are hereby incorporated by reference as if they were fully included herein.According to some embodiments, a new and / or improved category can be developed and tailored to a specific group of devices, for example, wearable devices such as smartwatches or smartglasses.

[0039] In terms of functionality, body-worn devices can represent a trade-off between power transfer balance and quality of service (QoS). For example, a body-worn device may have a small form factor relative to a mobile phone. Furthermore, a body-worn device, as defined above, may have a limited power transfer balance. Therefore, when considering a category within which a body-worn device can operate, it may be advantageous to maintain the power transfer balance improvement and low device complexity associated with Cat-M1, for example, because the form factor of the body-worn device may limit the battery / accumulator size, antenna size, and arrangement, etc.

[0040] However, Cat-M1, as currently defined, may be unsuitable for a body-worn device, for example, because a body-worn device may be configured to perform more advanced communication than an MTC device, such as VoLTE, audio streaming, health application monitoring, SMS / MMS messaging, etc. Thus, a body-worn device can benefit from the bandwidth, QoS, and other parameters of smartphone categories. Furthermore, a network may restrict Cat-M1 devices from accessing the network, for example, at certain times of day. For instance, a typical Cat-M1 device, such as an MTC device, may only transmit non-time-critical data, such as power consumption.For such devices, the network can therefore restrict communication to off-peak hours, such as nighttime hours when there is little other network traffic.

[0041] For these reasons, a body-worn device can use a new and / or improved category that is largely based on the features of Cat-M1 to benefit from its power transfer balance characteristics, but also utilizes certain features of other categories. Specifically, a "body-worn category" can be implemented, which may be configured to support body-worn devices (e.g., be optimized for them). In some scenarios, the body-worn category may be a new and / or improved category that utilizes some of the features of Cat-M1 and additionally provides support for body-worn devices. In other scenarios, Cat-M1 may be updated to support body-worn devices, so that the updated version of Cat-M1 can be considered the body-worn category.

[0042] In any case, certain characteristics may be desirable for the body-worn category. For example, it may be desirable for the body-worn category to: support VoIP functionality, such as VoLTE, with coverage improvements; support increased data rates relative to the 1 Mbps supported by Cat-M1; provide coverage improvements for data rates greater than 1 Mbps; enable longer battery life relative to smartphone categories (e.g., enabling a body-worn device to achieve battery life comparable to that achieved by a smartphone with similar usage, despite a different form factor); support UE mobility; support QoS; and prohibit network access blocking for devices operating in the body-worn category.

[0043] Use cases for the body-worn category can be divided into three general classifications of communication applications: latency-tolerant applications; VoIP-type applications, such as VoLTE, which have strict latency constraints; and other power-sensitive applications, including interactive, near-real-time applications or low-data-rate / periodic applications, such as audio streaming. Each of these classifications can benefit from different characteristics of the body-worn category. Specifically, for a body-worn device operating within the body-worn category, the network can implement certain improvements over Cat-M1 only if the body-worn device implements specific applications or classifications of applications.For example, in some scenarios, increased data rates for the body-worn device may only be allocated if the device indicates that it is implementing a VoIP-type application, an interactive, near-real-time application, or a low-data-rate / periodic application. Additional details regarding the enhancements that apply to each application classification are outlined below. Delay-tolerant applications

[0044] Delay-tolerant applications of a body-worn device, such as email communication, SMS / MMS communication, background data updates, etc., can be similar to the communication performed by MTC devices. For example, they can communicate without urgent time constraints and thus transmit using low bandwidths, such as the 1.4 MHz or 6 resource blocks (RBs) of the fixed bandwidth of Cat-M1. Therefore, if a body-worn device implements delay-tolerant applications, the body-worn category can provide similar performance to Cat-M1, such as a fixed bandwidth of 1.4 MHz, the use of M-PDCCH, the use of a single standard data radio bearer (DRB) or a limited number of DRBs, etc.This can enable the body-worn device to achieve improved battery life compared to using smartphone-type devices.

[0045] Even when implementing latency-tolerant applications, a body-worn device can benefit from certain minor improvements in network support beyond those provided by Cat-M1. The body-worn category can therefore provide such improvements. In some scenarios, the body-worn category can provide at least such minor improvements for all applications implemented by a body-worn device.

[0046] For example, the body-worn category can support the mobility of the body-worn device. For example, the body-worn category can enable re-selection and handover even in very poor radio conditions that require maximum coverage improvement.

[0047] As another example, the wearable category can prohibit network access restrictions for devices operating under the wearable category. In particular, the network may not block a wearable device from accessing the network, for example, during certain times of day.

[0048] In some scenarios, these improvements can be implemented for all UEs that operate according to the wearable-on-the-body category, e.g., without the UE further specifying an application that is implemented.

[0049] Applications that are not latency-tolerant (such as VoIP applications and other power-sensitive applications discussed below) may sometimes be referred to as latency-intolerant applications. VoIP applications

[0050] VoIP-like applications, such as VoLTE, can have significantly higher performance limitations than latency-tolerant applications. For example, VoIP-like applications may have strict latency constraints. Therefore, the body-worn category can provide additional enhancements over Cat-M1 to accommodate such higher performance, for example, in addition to the aforementioned enhancements for latency-tolerant applications, when a body-worn device indicates to the network that it is implementing a VoIP-like application.

[0051] For example, the body-worn device category can provide support for a QoS specification. Currently, Cat-M1 provides support for only a limited number of DRBs. The body-worn device category can provide support for the body-worn device to use one or more dedicated DRBs, such as QoS Class Identifier (QCI) 1 for conversational voice data and QCI 5 for signaling data when VoLTE is implemented. Thus, the body-worn device can indicate to the network that it is implementing VoLTE by displaying QCI 1 and QCI 5. Based on (e.g., in response to) the body-worn device displaying QCI 1 and QCI 5, the base station can determine that the communication is VoLTE and make other performance adjustments, such as to bandwidth, QoS, etc. Alternatively, the body-worn device can indicate to the network that it is implementing VoLTE in another way.

[0052] For UEs operating under the body-worn category, VoIP-like applications, such as VoLTE, can be scheduled based on M-PDCCH rather than PDCCH. This can allow a body-worn device to benefit from an M-PDCCH coverage enhancement (e.g., time replay) to schedule a resource allocation for VoLTE approval.

[0053] One problem when using M-PDCCH with VoLTE is a potential violation of VoLTE's time budget. Audio data packets are sent every 20 ms, so ideally, each audio packet should be scheduled within 20 ms. The resource allocation or approval carried out by the M-PDCCH can be repeated in a timely manner to allow the UE to decode it and to improve the power transmission balance. Thus, this application can exceed the 20 ms window while the UE attempts to decode the resource allocation to decode the audio payload.

[0054] To avoid this, in some scenarios the audio packets can be bundled, and semi-persistent scheduling (SPS) can be used. For example, instead of using an approval for each audio packet, the network can send a single approval for multiple audio packets; e.g., for three or four audio packets. This allows the multiple audio packets to each use the same resource allocation, which can provide a longer window (e.g., 80 ms for a bundle of four audio packets) for the UE to decode the audio packets. Additionally, in some scenarios, the network can change the resource allocations infrequently to avoid having to send an M-PDCCH.

[0055] As another example, the body-worn category can allow increased data rates relative to the 1 Mbit / s supported by Cat-M1. To achieve this, the bandwidth of the body-worn category can be increased relative to the bandwidth of Cat-M1. Cat-M1 has a fixed bandwidth of 1.4 MHz or 6 resource blocks (RBs). In some scenarios, the body-worn category can operate with a higher bandwidth, such as 15 RBs (e.g., to support Cat-1 features) or 25 RBs. In some scenarios, the body-worn category may only exceed 6 RBs if additional bandwidth is appropriate or necessary; for example, if additional bandwidth is available and / or if additional bandwidth would improve the quality of service, such as when the body-worn device is located near the cell edge or requires higher throughput.In some scenarios, the body-worn category can exceed 6 RBs if sufficient resources are available, for example, to provide additional downlink power, thereby improving the power transmission balance for body-worn devices operating according to the body-worn category. For example, in some scenarios, the base station can determine the bandwidth to be allocated to a device operating according to the body-worn category, based on available resources and / or one or more signal quality metrics. Other power-sensitive applications

[0056] Other power-sensitive applications, such as interactive, near-real-time applications or low-data-rate / periodic applications, may include applications like audio streaming or time-sensitive periodic reporting for applications such as health monitoring. Such applications can benefit from the enhancements mentioned above regarding delay-tolerant applications. Furthermore, some near-real-time applications may benefit from additional bandwidth relative to Cat-M1, particularly if the body-worn device is located near the cell edge. For example, supporting audio streaming may require a bandwidth of up to 5 MHz and a throughput of up to 100 kbps. Thus, the body-worn category may allow increased data rates for such near-real-time applications, as described above regarding VoIP-type applications.Alternatively, some low-data-rate / periodic reports for applications such as health monitoring can use low data rates (e.g., 64 kbps) but can also provide periodic communication with certain time constraints. Thus, the wearable-body category can allow a QoS specification for such applications. In some scenarios, the wearable-body category can allow dedicated DRBs, e.g., as described above regarding VoIP-like applications.

[0057] As noted above, in some scenarios the network may only allocate additional bandwidth (e.g., beyond the 6 RBs specified for Cat-M1) to a body-worn device if the device indicates that it is implementing a specific application or an application of a particular classification. Other enhancements over Cat-M1, such as the use of dedicated DRBs, may be similarly restricted to specific applications. Thus, to obtain additional resources, such as bandwidth and / or DRBs, allocated by the network, the body-worn device may indicate that it is implementing an interactive, near-real-time application or a low-data-rate / periodic application. However, these applications may not be subject to the same performance limitations as VoIP-type applications.For example, audio streaming may not require a Guaranteed Bitrate (GBR) resource type, as defined by QCI1. Therefore, it may be unsuitable for a body-worn device to request increased resources for an interactive, near-real-time application or a low-bitrate / periodic application using QCI1 and QCI5, such as VoIP-type applications. Instead, the body-worn category can support additional QCI carriers that are not the QCI1 and QCI5 carriers supported for VoIP-type applications.

[0058] In some scenarios, the body-worn category can support a new QCI carrier, which may be referred to herein as QCI15, and which can indicate that a UE operating according to the body-worn category implements an interactive, near-real-time application or a low-data-rate / periodic application, and which can specify parameters appropriate for such applications. For example, as suggested above, QCI15 can specify a non-GBR resource type. In some scenarios, QCI15 can specify a priority level that prioritizes QCI15 communication over generic transmission control protocol (TCP) traffic, such as email traffic or generic QCI8 or QCI9 traffic. For example, QCI15 can specify a priority level of 7.5. In some scenarios, QCI15 can specify a packet delay budget of 100 ms, for example, to allow continuous audio streaming.In some scenarios, QCI15 can have a packet error loss rate of 10. -3 establish.

[0059] The body-worn device can request a dedicated QCI15 carrier, e.g., using a carrier resource allocation procedure requested by the UE, as described in Fig. 5 shown. Fig. Figure 5 illustrates a call flow showing network elements involved in this process. A UE 502 can be a body-worn device, such as the UE 106. The UE 502 can send a carrier resource allocation request 550 to an eNB 504, which can be a base station, such as the BS 102. The carrier resource allocation request 550 can display a QCI value of 15. The carrier resource allocation request 550 can also include additional information about requested resources, such as a bit rate, etc. The eNB 504 can receive the carrier resource allocation request 550 and forward at least part of it to a mobility management unit (MME) 506. The MME 506 can receive the carrier resource allocation request 550 and, in response, send a carrier resource command 552 to reserve the carrier resources on a serving gateway (SGW) 508.The SGW 508 can receive the carrier resource command 552 and, in response, send another carrier resource command 554 to reserve the carrier resources in a packet data network (PDN) gateway (PGW) 510. The PGW 510 can receive the carrier resource command 554 and, in response, send a credit control request (CC-Request) 556 to a policy and charging rules function (PCRF) 512. The PCRF 512 can receive the CC-Request 556 and, in response, send a credit control response (CC-Response) 558 to the PGW 510. At 560, the various network elements can generate the dedicated carrier according to the parameters specified by QCI15, for example, according to known carrier generation procedures.

[0060] Since the eNB 504 and the MME 506 received the carrier resource allocation request 550, which indicates a QCI value of 15, these elements can recognize that the UE 502 is implementing an interactive, near-real-time application or a low-data-rate / periodic application. Therefore, the eNB 504 and / or the MME 506 can make resource allocation decisions, such as bandwidth allocation, appropriate for such applications.

[0061] Alternatively or additionally, the body-worn device can indicate that it is using an interactive, near-real-time application or a low-data-rate / periodic application by requesting a specific access point name (APN), as described in Fig. 6 illustrates. Fig. Figure 6 illustrates a call flow showing network elements involved in this procedure. A UE 602 can be a body-worn device, such as the UE 106. The UE 602 can send a connection request 650 to an eNB 604, which can be a base station, such as the BS 102. The eNB 604 can receive the connection request 650 and forward at least one portion of it to an MME 606. The connection request 650 can indicate a specific APN to which the UE 602 requests a connection. The specific APN indicated in the connection request 650 can be designated for (or otherwise associated with) body-worn devices that implement a specific application or classification of applications.

[0062] The MME 606 can receive the connectivity request 650 and, in response, send a session request 652 to a PGW 610. The session request 652 can indicate the specific APN to which the UE 602 has requested connectivity. The PGW 610 can receive the session request 652 and, in response, send the updated carrier QoS mapping 654 of the evolved packet system (EPS) to the MME 606. In particular, the PGW 610 can recognize that the displayed specific APN is intended for wearable devices implementing a specific application or classification of applications and can assign a QoS for the session as defined or appropriate for that specific application or classification of applications. As a specific example, the PGW 610 can assign the QoS as defined above for QCI15; for example,Non-GBR resource type, priority level of 7.5, packet delay budget of 100 ms and a packet error loss rate of 10. -3 .

[0063] The MME 606 can receive the updated EPS carrier QoS assignment 654 and, in response, send an initial context setup message 656 to the eNB 604. The initial context setup message 656 can display the EPS carrier QoS assigned by the PGW. Thus, the eNB 604 and the MME 606 can recognize that the UE 602 is implementing an interactive, near-real-time application or a low-data-rate / periodic application, and in some scenarios, they can further identify a specific implemented application. Therefore, the eNB 604 and / or the MME 606 can make resource allocation decisions, such as bandwidth allocation, that are appropriate for such applications. Figure 7 - Implementation of communication using devices of the body-worn category

[0064] Fig. Figure 7 is a flowchart illustrating an exemplary procedure for a European Union (EU) to use a category of body-worn device when communicating with a wireless communication network according to some embodiments. The diagram in Fig. The method shown in Figure 7 can be used in conjunction with any of the computer systems or devices shown in the preceding figures, in addition to other devices. For example, the UE as described above can be implemented with reference to any of UEs 106, 502, or 602. Some of the method elements shown can be performed simultaneously, in a different order than shown, or omitted. Furthermore, additional method elements can be performed as desired.

[0065] At 702, the UE can transmit or otherwise communicate a device category of the UE to the wireless communication network (e.g., to a base station of the wireless communication network, such as one of the base stations 102, 504, or 604). For example, the communicated device category can identify the UE as a body-worn device (e.g., a device that is configured, optimized, etc., to operate according to communication parameters defined for a category of body-worn device).

[0066] In 704, the UE can establish a communication channel with the wireless communication network that corresponds to the device category communicated by the UE. In particular, the communication channel can be established with initial communication parameters that correspond to the parameters defined for the communicated device category (e.g., category of a wearable device). The initial parameters can be determined by the wireless communication network based at least partially on (e.g., in response to) the device category communicated by the UE.

[0067] If the device category identifies the UE as a body-worn device, the initial parameters in some scenarios may include parameters selected for a body-worn device implementing delay-tolerant applications (e.g., for a body-worn device that does not implement delay-intolerant wireless communication applications, such as VoIP applications or other power-sensitive applications, as discussed above). For example, such initial parameters may include fixed bandwidth, mobility support, use of M-PDCCH, and / or other parameters discussed above in relation to delay-tolerant applications. In some embodiments, the wireless communication network may default to parameters selected for delay-tolerant applications, such as...if the UE does not indicate that it implements a specific application that requires (or prefers) additional bandwidth (e.g., VoIP applications or other power-sensitive applications, as discussed above).

[0068] The UE can configure hardware, software, or both to communicate with the wireless communication network according to the initial parameters. In the case of 706, the UE can spend a certain amount of time communicating with the wireless communication network over the established communication channel according to the initial communication parameters.

[0069] With 708, the UE can indicate to the wireless communication network that it is implementing a specific application. For example, the UE can send an indication that it is implementing a VoIP application or another power-sensitive application, as discussed above. This can occur in response to the UE initiating the implementation of a specific application that requires (or prefers) different communication parameters than the current parameters of the communication channel (e.g., different from the initial communication parameters). The UE can indicate that it is implementing a specific application by, for example, setting (e.g., requesting) one or more QCI values, requesting a connection to a specific APN, providing an explicit indication, or by other means. The indication can be sent over the communication channel according to the initial communication parameters.

[0070] With the 710, the UE can receive an indication from the wireless communication network that the communication channel parameters have changed. For example, the wireless communication network may have changed the communication channel parameters in response to the UE indicating the implementation of the specific application, such as to meet requirements or preferences related to using the communication channel to support that specific application. For example, the changed parameters may include increased bandwidth, dynamic bandwidth, different QoS values, and / or other parameters discussed above in relation to VoIP applications and / or other power-sensitive applications. The indication that the communication channel parameters have changed can be received in any of several different forms, such as...An explicit indication or message showing the establishment of a dedicated carrier (e.g., the UE may receive a message indicating that a carrier is being established—that the carrier establishment is complete, initiated, or in progress, such as an RRC Connection Reconfiguration Message indicating the establishment of a specific carrier). The indication that the communication channel parameters have changed may include a description, code, or other information that identifies the specific changes.

[0071] At 712, the UE can communicate on the communication channel according to the changed parameters. For example, the UE can perform communication with the wireless communication network to support the specific application. Communication on the communication channel according to the changed parameters may involve (e.g., require or benefit from) the reconfiguration of hardware, software, or both by the UE to operate according to the changed parameters, in response to receiving the indication at 710 that the communication channel parameters have changed. For example, the UE may reconfigure operational software and / or hardware settings (e.g., within the 330 radio device) for encoding and / or decoding signals sent or received with the changed parameters.

[0072] With 714, the UE can indicate to the wireless communication network that it is no longer implementing the specific application. This indication can be a response to the UE's termination of the specific application or be inherent in the application itself. For example, the UE can indicate that it is no longer implementing a VoLTE application by ending a VoLTE call. Alternatively, the UE can send an explicit indication that it has ceased implementing the specific application.

[0073] At 716, the UE can receive a notification from the wireless communication network that the communication channel parameters have changed again. For example, the wireless communication network might have changed the communication channel parameters in response to the UE indicating that it is no longer implementing the specific application. If, for instance, after the specific application has ceased, the UE only implements delay-tolerant applications (e.g., no delay-intolerant applications), the wireless communication network can revert the communication channel parameters to their initial values.

[0074] In response to receiving the notification at 716 that the communication channel parameters have changed again, the UE may further reconfigure hardware, software, or both to communicate with the wireless communication network according to the changed parameters.

[0075] It should be evident that the UE can indicate to the wireless communication network any status change with respect to the applications currently implemented by the UE in a manner similar to that described in steps 708 and 714. In response, the wireless communication network can determine the communication parameters required (or preferred) for an UE of the identified device category that implements applications of the type currently implemented by the UE (e.g., the applications that the UE has notified to the wireless communication network that the UE is currently implementing), as defined by the identified device category. If necessary (or appropriate), the wireless communication network can suitably modify the communication channel parameters and indicate the change to the UE.

[0076] For example, in some scenarios, according to the procedure of Fig.7. The UE may additionally initiate the implementation of a second specific application, for example, while the UE is communicating with the wireless communication channel in step 712. The UE may indicate this to the wireless communication network in a manner similar to that described in step 708. If necessary (or appropriate), the wireless communication network may further modify the communication parameters to accommodate the second specific application and may indicate the change to the UE, for example, in a manner similar to that described in step 710.

[0077] For example, if in step 708 the UE (User Equipment) of the body-worn device category indicates that it is implementing a Low Data Rate / Periodic Reporting application, then the UE's wireless communication network (received by the UE in step 710) may indicate a change in the QoS parameters (among other possible parameter changes), but may not indicate a change in bandwidth, for example, because the Low Data Rate / Periodic Reporting application may not require (or prefer) a different bandwidth than the bandwidth specified for latency-tolerant applications. If the UE later indicates (e.g., during step 712) that it has initiated a VoIP application, the UE's wireless communication network may indicate a further change in the QoS parameters as well as a change in bandwidth (among other possible parameter changes) to accommodate the VoIP application.The UE can reconfigure suitable hardware and / or software to accommodate these changes and thus enable continuous communication with the wireless communication network.

[0078] As an alternative example, the UE, which falls into the category of a wearable device, might initially indicate (e.g., in step 708) that it is implementing a VoIP application, prompting the wireless communication network to indicate a change in communication parameters to accommodate the VoIP application (e.g., in step 710). If the UE later indicates (e.g., during step 712) that it has initiated a Low Data Rate / Periodic Reporting application, then in some scenarios the wireless communication network may not be permitted to indicate any further changes in communication parameters. For example, the communication parameters selected to accommodate the VoIP application might provide performance beyond that of the communication parameters for the Low Data Rate / Periodic Reporting application.Thus, the communication channel parameters in step 712 may already be sufficient to include the application of low-data-rate / periodic reports. However, the UE may indicate in step 714 that it has stopped implementing the VoIP application. In this scenario, the indication received in step 716 may show that the communication parameters have changed to no longer include the VoIP application, for example, while the application of low-data-rate / periodic reports continues to be implemented. Therefore, in this scenario, the communication parameters must not revert to the initial parameters in step 716.

[0079] It should therefore be evident that the UE can notify the wireless communication network of any number of status changes with respect to the applications currently implemented by the UE, and that the wireless communication network can determine the communication parameters required (or preferred) for an UE of the identified device category implementing applications of the type currently implemented by the UE (e.g., the applications that the UE has notified to the wireless communication network that the UE is currently implementing), as defined by the identified device category. If necessary (or appropriate), the wireless communication network can suitably modify the communication channel parameters and notify the UE of the change. In response, the UE can reconfigure its software and / or hardware to accommodate the modified communication parameters.

[0080] Embodiments of the present invention can be implemented in any number of diverse forms. For example, in some embodiments, the present invention can be implemented as a computer-implemented method, a computer-readable storage medium, or a computer system. In other embodiments, the present invention can be implemented using one or more user-designed hardware devices, such as ASICs. In still other embodiments, the present invention can be implemented using one or more programmable hardware elements, such as FPGAs.

[0081] In some embodiments, a non-volatile, computer-readable storage medium (e.g., a non-volatile memory element) can be configured to store program instructions and / or data, wherein, when executed by a computer system, the program instructions cause the computer system to perform a procedure, e.g., any one of the procedure execution forms described herein, or any combination of the procedure execution forms described herein, or any subset of any one of the procedure execution forms described herein, or any combination of such subsets.

[0082] In some embodiments, a device (e.g., a UE) can be configured to include a processor (or a set of processors) and a storage medium (or storage element), wherein program instructions are stored in the storage medium, the processor being configured to read and execute the program instructions from the storage medium, and the program instructions being executable to implement any of the various method implementations described herein (or any combination of the method implementations described herein, or any subset of any of the method implementations described herein, or any combination of such subsets). The device can be implemented in one of many forms.

[0083] Although the embodiments have been described above in considerable detail, numerous variations and modifications are apparent to the person skilled in the art after a full understanding of the foregoing disclosure. It is intended that the following claims be interpreted to include all such variations and modifications.

Claims

[1] A method for performing wireless communication between a user equipment device (UE) (106) and a wireless communication network (100), the method comprising: by the UE (106): Communicating (702) to the wireless communication network (100) a device category of the UE (106), the device category specifying different parameters for devices implementing each of a plurality of application classes; Establishing (704) a communication channel with the wireless communication network (100), the communication channel having parameters determined at least in part based on the device category of the UE (106), the parameters comprising a fixed bandwidth; indicate (708) to the wireless communication network (100) after establishing (704) the communication channel that the UE (106) implements a specific application, wherein the specific application belongs to a first class of the plurality of application classes; and Receiving (710) an indication from the wireless communication network (100) that the communication channel parameters have changed, the received indication being responsive to the indication (708) that the UE (106) implements the specific application, wherein changed parameters include increased bandwidth. [2] The method of claim 1, wherein indicating (708) that the UE (106) implements the specific application comprises setting a Quality of Service, QoS, Class Identifier, QCI value. [3] The method of claim 1, wherein indicating (708) that the UE (106) implements the specific application comprises requesting a binding to a specific Access Point Name, APN. [4] The method of claim 1, wherein the indication that the communication channel parameters have changed comprises a message indicating establishment of a dedicated bearer for the specific application. [5] The method of claim 1, wherein the increased bandwidth comprises a dynamic bandwidth determined by the wireless communication network (100). [6] The method of claim 1, wherein the changed parameters further comprise changed quality of service (QoS) parameters. [7] The method of claim 1, wherein the specific application comprises a Voice over Internet Protocol (VoIP) application, the method further comprising using a physical MTC (machine-type communication) downlink control channel, M-PDCCH, to schedule bundled VoIP audio packets. [8] A user equipment device (UE) (106) comprising: at least one memory (306); and at least one processor (302) coupled to the at least one memory (306), wherein the at least one processor (302) is configured to cause the UE (106) to: Establishing (704) a communication channel with a wireless communication network (100), the communication channel having initial parameters that match a device category of the UE (106), the device category specifying different parameters for devices implementing each of a plurality of application classes; Sending (708) a first indication to the wireless communication network (100) after establishing the communication channel that the UE (106) implements a specific application, wherein the specific application belongs to a first class of the plurality of application classes; and Receiving (710) a second indication from the wireless communication network (100) responsive to the first indication that the communication channel parameters have changed. [9] The UE (106) of claim 8, wherein the initial parameters further correspond to a device of the device category of the UE (106) implementing delay-tolerant applications, and wherein the changed parameters correspond to a device of the device category of the UE (106) implementing a Voice over Internet Protocol (VoIP) application. [10] The UE (106) of claim 8, wherein the initial parameters comprise a fixed bandwidth, and wherein the changed parameters comprise an increased bandwidth. [11] The UE (106) of claim 10, wherein the increased bandwidth comprises a dynamic bandwidth determined by the wireless communication network (100). [12] The UE (106) of claim 8, wherein the device category of the UE (106) indicates that the UE (106) is a wearable device. [13] The UE (106) of claim 8, wherein the specific application comprises a Voice over Internet Protocol (VoIP) application, and wherein the at least one processor is further configured to cause the UE (106) to use a physical MTC (machine-type communication) downlink control channel, M-PDCCH, for scheduling bundled VoIP audio packets. [14] The UE (106) of claim 8, wherein indicating that the UE (106) implements the specific application comprises setting a Quality of Service, QoS, Class Identifier, QCI value. [15] A non-transitory computer-readable medium storing program instructions executable by at least one processor (302) of a user equipment device (UE) (106) to cause the UE (106) to perform the steps of any one of claims 1 to 7.

Images