US20130203399A1 - Handling dual priority applications in a wireless communication network - Google Patents

Handling dual priority applications in a wireless communication network Download PDF

Info

Publication number
US20130203399A1
US20130203399A1 US13/526,307 US201213526307A US2013203399A1 US 20130203399 A1 US20130203399 A1 US 20130203399A1 US 201213526307 A US201213526307 A US 201213526307A US 2013203399 A1 US2013203399 A1 US 2013203399A1
Authority
US
United States
Prior art keywords
priority level
communication
associated
priority
configuration
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US13/526,307
Inventor
Vivek Gupta
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel Corp
Original Assignee
Intel Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US201261595576P priority Critical
Application filed by Intel Corp filed Critical Intel Corp
Priority to US13/526,307 priority patent/US20130203399A1/en
Assigned to INTEL CORPORATION reassignment INTEL CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: GUPTA, VIVEK
Priority claimed from US13/623,779 external-priority patent/US20130201870A1/en
Publication of US20130203399A1 publication Critical patent/US20130203399A1/en
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/10Flow control or congestion control
    • H04L47/12Congestion avoidance or recovery
    • H04L47/122Diverting traffic away from congested spots
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B7/00Radio transmission systems, i.e. using radiation field
    • H04B7/02Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/022Site diversity; Macro-diversity
    • H04B7/024Co-operative use of antennas of several sites, e.g. in co-ordinated multipoint or co-operative multiple-input multiple-output [MIMO] systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/0001Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0026Transmission of channel quality indication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/10Flow control or congestion control
    • H04L47/26Explicit feedback to the source, e.g. choke packet
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/10Scheduling measurement reports ; Arrangements for measurement reports
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic or resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/0289Congestion control
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic or resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/08Load balancing or load distribution
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic or resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/10Flow control between communication endpoints
    • H04W28/12Flow control between communication endpoints using signalling between network elements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/02Access restriction performed under specific conditions
    • H04W48/06Access restriction performed under specific conditions based on traffic conditions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/18Management of setup rejection or failure
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/02Arrangements for detecting or preventing errors in the information received by diversity reception
    • H04L1/06Arrangements for detecting or preventing errors in the information received by diversity reception using space diversity
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L2001/0092Error control systems characterised by the topology of the transmission link
    • H04L2001/0093Point-to-multipoint
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L25/00Baseband systems
    • H04L25/02Details ; Arrangements for supplying electrical power along data transmission lines
    • H04L25/0202Channel estimation
    • H04L25/0204Channel estimation of multiple channels
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L25/00Baseband systems
    • H04L25/02Details ; Arrangements for supplying electrical power along data transmission lines
    • H04L25/0202Channel estimation
    • H04L25/0224Channel estimation using sounding signals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/10Flow control or congestion control
    • H04L47/14Flow control or congestion control in wireless networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/10Flow control or congestion control
    • H04L47/28Flow control or congestion control using time considerations
    • H04L47/283Network and process delay, e.g. jitter or round trip time [RTT]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic or resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/0215Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic or resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/0231Traffic management, e.g. flow control or congestion control based on communication conditions
    • H04W28/0236Traffic management, e.g. flow control or congestion control based on communication conditions radio quality, e.g. interference, losses or delay
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/30Connection release
    • H04W76/34Selective release of ongoing connections
    • H04W76/36Selective release of ongoing connections for reassigning the resources associated with the released connections

Abstract

Embodiments of the present disclosure describe techniques for handling dual priority for a machine-to-machine device in a wireless communication network. The device may include computer-readable media having instructions and one or more processors coupled with the computer-readable media and configured to execute the instructions to configure, as a default configuration, the device with a first priority level for machine-type communications, receive a notification from an application associated with the device, the notification indicating that the application generated a communication to a network controller, the communication being associated with a second priority level that is higher than the first priority level, and in response to the notification, configure, as an override configuration, the device with the second priority level for machine-type communications. If a backoff timer is running for low priority application, and a current communication is not for a low priority, the communication is allowed to proceed.

Description

    CROSS REFERENCE TO RELATED APPLICATIONS
  • The present application claims priority to U.S. Provisional Patent Application No. 61/595,576, filed Feb. 6, 2012, entitled “Advanced Wireless Communication Systems and Techniques,” which is hereby incorporated by reference in its entirety for all purposes.
  • FIELD
  • Embodiments of the present disclosure generally relate to the field of wireless communication systems, and more particularly, to machine-to-machine communications in wireless communication networks.
  • BACKGROUND
  • Machine-to-machine (“M2M”) wireless machines or devices (hereafter referred to as “M2M devices”) may communicate primarily or exclusively with other M2M devices, with little or no human intervention. Examples of M2M devices may include wireless weather sensors, assembly line sensors, meters to track vehicles of a fleet, and so forth. In many cases these M2M devices may connect to a wireless network and communicate, e.g., over a wide area network such as the Internet, with a network server. M2M devices may be used with the IEEE 802.16 standard, IEEE Std. 802.16-2009, published May 29, 2009 (“WiMAX”), as well as in Third Generation Partnership Project (“3GPP”) networks. In parlance of the 3GPP Long Term Evolution (“LTE”) Release 10 (March 2011) (the “LTE Standard”), M2M communications may alternatively be referred to as “machine-type communications” (“MTC”). From a network perspective, M2M communications may be considered to be relatively low-priority communications due to their relatively high latency tolerances and infrequent data transfers. However, most M2M devices that normally communicate on a low priority level may have rare occasions when they need to communicate on a priority level that is higher than a low priority.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • Embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals designate like structural elements. Embodiments are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings.
  • FIG. 1 illustrates an example wireless communication network in accordance with some embodiments.
  • FIGS. 2 and 3 are block diagrams illustrating example communications between user equipment (mobile device) and a wireless communication network in accordance with some embodiments.
  • FIG. 4 is a process flow diagram for communications between a network controller and user equipment in a wireless communication network in accordance with some embodiments.
  • FIG. 5 is a process flow diagram for handling a dual priority by user equipment in a wireless network environment in accordance with some embodiments.
  • FIG. 6 is a process flow diagram for handling a dual priority by user equipment in a congested wireless network environment in accordance with some embodiments.
  • FIG. 7 illustrates an example system that may be used to practice various embodiments described herein.
  • DETAILED DESCRIPTION
  • Embodiments of the present disclosure provide data techniques and configurations for handling dual-priority devices in a wireless communication network. In the following detailed description, reference is made to the accompanying drawings which form a part hereof, wherein like numerals designate like parts throughout, and in which is shown by way of illustration embodiments in which the subject matter of the present disclosure may be practiced. It is to be understood that other embodiments may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure. Therefore, the following detailed description is not to be taken in a limiting sense, and the scope of embodiments is defined by the appended claims and their equivalents.
  • Various operations are described as multiple discrete operations in turn, in a manner that is most helpful in understanding the claimed subject matter. However, the order of description should not be construed as to imply that these operations are necessarily order dependent. In particular, these operations may not be performed in the order of presentation. Operations described may be performed in a different order than the described embodiment. Various additional operations may be performed and/or described operations may be omitted in additional embodiments.
  • The description may use the phrases “in an embodiment,” or “in embodiments,” which may each refer to one or more of the same or different embodiments. Furthermore, the terms “comprising,” “including,” “having,” and the like, as used with respect to embodiments of the present disclosure, are synonymous.
  • As used herein, the term “module” may refer to, be part of, or include an Application-Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality.
  • Example embodiments may be described herein in relation to wireless communication networks including networks such as 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) networks including any amendments, updates, and/or revisions (e.g., LTE Release 10 (also referred to as LTE-Advanced (LTE-A), LTE Release 11, etc.), Worldwide Interoperability for Microwave Access (WiMAX) networks, and the like. The embodiments described herein may operate in relation to a radio access network, e.g., an evolved Universal Terrestrial Radio Access Network (E-UTRAN) having evolved node base stations (eNBs), and a core network, e.g., an evolved packet core having gateways, management entities, etc.
  • In other embodiments, communication schemes described herein may be compatible with additional/alternative communication standards, specifications, and/or protocols. For example, embodiments of the present disclosure may be applied to other types of wireless networks where similar advantages may be obtained. Such networks may include, but are not limited to, wireless local area networks (WLANs), wireless personal area networks (WPANs) and/or wireless wide area networks (WWANs) such as cellular networks and the like.
  • The following embodiments may be used in a variety of applications including transmitters and receivers of a mobile wireless radio system. Radio systems specifically included within the scope of the embodiments include, but are not limited to, network interface cards (NICs), network adaptors, base stations, access points (APs), relay nodes, eNBs, gateways, bridges, hubs and satellite radiotelephones. Further, the radio systems within the scope of embodiments may include satellite systems, personal communication systems (PCS), two-way radio systems, global positioning systems (GPS), two-way pagers, personal computers (PCs) and related peripherals, personal digital assistants (PDAs), personal computing accessories and all existing and future arising systems which may be related in nature and to which the principles of the embodiments could be suitably applied.
  • Techniques described herein provide for enabling user equipment (UE) such as an M2M device to provide at least two priority levels (e.g., dual priority) for communications initiated by the UE in a wireless network environment. In some wireless communication environments, the M2M network overload control work may be simplified by restricting M2M devices to a single priority level for all applications executing on the M2M device. The device may be assigned a priority level of either “low priority” or “normal priority.” In practice, significant number of machine type communications may be categorized as “low priority” and hence the M2M devices may be assigned that setting.
  • However, most M2M devices that normally use “low priority” may also have infrequent, rare occasions when they need to use the “normal” priority setting. For example, electricity meters sending a daily report (e.g., of the per hour usage) may send the report as “low priority.” However, there may be instances in which the electricity meter may want to send an alarm with “normal priority,” for example, if the meter is being tampered with or is being vandalized.
  • In another example, a road temperature sensor may send daily “I′m still working” communications with “low priority” but, if the road temperature falls to sub-zero, may need to immediately send a warning to the control center with “normal priority.”
  • In yet another example, an M2M device may host multiple applications. For example, a room temperature application residing on an M2M device may require data transmission using “low priority,” while a video-streaming application residing on the same device may require data transmission using “normal priority.” The embodiments described herein are not limited to the above examples; the above examples are included for illustration of the techniques described in the present disclosure.
  • If the device may only use either “low priority” or “normal priority” levels for communications, the need for a truly “low priority” device to support rare “normal priority” events may dissuade MTC customers from using the “low priority” setting for their M2M devices. Instead, the MTC customers may be encouraged to configure their devices for “normal priority” level of communications at all times. This may have undesirable consequences with respect to additional network overload.
  • Embodiments of the present invention provide applications that may reside on an M2M device with the ability to override the device's default “low priority” setting in cases when the applications may need to transmit a “normal priority” communication.
  • In one embodiment, the UE and/or communications initiated by the UE (e.g., requests initiated by the applications hosted by the UE) may be assigned a default (e.g., low) priority level. In some cases, for example, in emergency and other situations described below in greater detail, the UE may be configured to override the default priority associated with the initiated request and assign a higher (e.g., “normal”) priority level to the initiated request that may be treated by the network according to the assigned priority level. For example, the network may be congested and may not immediately accept a request or other communication from the UE that is associated with a default priority (or lower level of priority), but may accept and process a request or other communications from the UE that is associated with a higher (normal) level that may be assigned to the communication by the UE. More specifically, if the network is determined to be congested and therefore unable to process a request with a default (low) priority from the UE, the network may provide to the UE a wait time value, during which the UE may refrain from attempting to contact the network with communications with low priority. However, if the UE initiates requests with a higher (normal) priority level, these requests may be allowed to be accepted by the network.
  • In another embodiment, it may be desired for the UE to have a capability to override access control configurations associated with the UE, such as Extended Access Barring configuration. Extended Access Barring (EAB) is a mechanism for the operator(s) to control mobile originating access attempts from UEs that are configured for EAB in order to prevent overload of the access network and/or the core network. In congestion or overload situations, the operator may restrict access from UEs configured for EAB while permitting access from other UEs. UEs configured for EAB are considered more tolerant to access restrictions than other UEs. When an operator determines that it is appropriate to apply EAB, the network broadcasts necessary information to provide EAB control for UEs in a specific area.
  • However, in some instances, the Extended Access Barring configuration may need to be overridden, typically in conjunction with low priority override capability as described above. This may relate to the fact that typically UEs configured for low access priority are also configured for EAB. Accordingly, when it is necessary to override low priority for a communication initiated by a UE, it may also be necessary to override an EAB setting in order to allow the communication to proceed. Operations of UEs configured to provide dual priority for communications initiated by the UEs in different situations are described below in greater detail.
  • FIG. 1 schematically illustrates an example wireless network 100 in accordance with some embodiments. The network 100 may include a RAN 20 and a core network 25. In some embodiments, the network 100 may be an LTE network, the RAN 20 may be a E-UTRAN, and the core network 25 may be an Evolved Packet System (EPS) type core network. A UE 15 may access the core network 25 via a radio link (“link”) with an eNB such as, for example, one of eNBs 40, 42, etc., in the RAN 20. The UE 15 may be, for example, a subscriber station (e.g., an M2M device) that is configured to communicate with the eNBs 40, 42 in conformance with one or more protocols. The following description is provided for an example network 100 that conforms with 3GPP for ease of discussion; however, subject matter of the present disclosure is not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein. In some embodiments, the UE 15 may be configured to communicate using a multiple-input and multiple-output (MIMO) communication scheme. One or more antennas of the UE 15 may be used to concurrently utilize radio resources of multiple respective component carriers (e.g., which may correspond with antennas of eNBs 40, 42) of RAN 20. The UE 15 may be configured to communicate using Orthogonal Frequency Division Multiple Access (OFDMA) in, e.g., downlink communications, and/or Single-Carrier Frequency Division Multiple Access (SC-FDMA) in, e.g., uplink communications in some embodiments.
  • While FIG. 1 generally depicts the UE 15 as a mobile device (e.g., a cellular phone), in various embodiments the UE 15 may be a personal computer (PC), a notebook, ultrabook, netbook, smartphone, an ultra mobile PC (UMPC), a handheld mobile device, an universal integrated circuit card (UICC), a personal digital assistant (PDA), a Customer Premise Equipment (CPE), a tablet, or other consumer electronics such as MP3 players, digital cameras, and the like. As discussed above, the UE 15 may be a Machine-Type Communication (MTC) device, also known as M2M device. In the present disclosure, the terms “UE” and “device” will be used interchangeably for simplicity purposes. The eNBs 40, 42 may include one or more antennas, one or more radio modules to modulate and/or demodulate signals transmitted or received on an air interface, and one or more digital modules to process signals transmitted and received on the air interface.
  • In some embodiments, communication with the UE 15 via RAN 20 may be facilitated via one or more nodes 45 (e.g., Radio Network Controllers). The one or more nodes 45 may act as an interface between the core network 25 and the RAN 20. According to various embodiments, the one or more nodes 45 may include a Mobile Management Entity (MME) that is configured to manage signaling exchanges (e.g., authentication of the UE 15) between the base stations 40, 42 and the core network 25 (e.g., one or more servers 50), a Packet Data Network Gateway (PGW) to provide a gateway router to the Internet 65, and/or a Serving Gateway (SGW) to manage user data tunnels or paths between the eNBs 40, 42 of the RAN 20 and the PGW. Other types of nodes may be used in other embodiments.
  • The core network 25 may include logic (e.g., a module) to provide authentication of the UE 15 or other actions associated with establishment of a communication link to provide a connected state of the UE 15 with the network 100. For example, the core network 25 may include one or more servers 50 that may be communicatively coupled to the base stations 40, 42. In an embodiment, the one or more servers 50 may include a Home Subscriber Server (HSS), which may be used to manage user parameters such as a user's International Mobile Subscriber Identity (IMSI), authentication information, and the like. The core network 25 may include other servers, interfaces, and modules. In some embodiments, logic associated with different functionalities of the one or more servers 50 may be combined to reduce a number of servers, including, for example, being combined in a single machine or module.
  • According to various embodiments, the network 100 may be an Internet Protocol (IP) based network. For example, the core network 25 may be, at least in part, an IP based network, such as a packet switched (PS) network. Interfaces between network nodes (e.g., the one or more nodes 45) may be based on IP, including a backhaul connection to the base stations 40, 42. In some embodiments, the network 100 may be enabled to provide connection with a circuit switched (CS) network (e.g., CS domain). In an embodiment, a UE 15 may communicate with the network 100 according to one or more communication protocols, such as, for example, Radio Resource Control (RRC) protocol adapted for LTE communication environment.
  • An example connection diagram between the UE 15 and the network 100 is illustrated in FIG. 2. As the diagram 200 illustrates, the UE 15 may send an RRC connection request message 204 to a network controller 206. The RRC connection request message 204 may be a request by the UE 15 for allocation of radio resources so that the UE 15 may exchange data with the RAN 20. The network controller 206 may control establishment and/or maintenance of RRC connections between the UE 15 and the RAN 20. The network controller 206 may be disposed in an eNB 40 or 42 with which the UE 15 attempts to establish an RRC connection. In other embodiments, the network controller 206, or components thereof, may be disposed in additional/alternative network entities, e.g., within a node of the one or more nodes 45, a server of the one or more servers 50, etc.
  • If the RAN 20 is congested and is not be able to support an RRC connection associated with the RRC connection request message 204, the network controller 206 may respond with an RRC connection reject message 208 to reject the RRC connection request message 204. In this case an RRC connection between the UE 15 and the RAN 20 may not be established. In one example, an RRC connection request message may relate to a NAS request message, such as attach request, tracking area update request, or extended service request.
  • In some instances, for particular types of devices, such as MTC devices, the network controller 206 may provide, in the connection reject message 208, a wait time (WT) value also known as extended wait time or EWTA timer associated with the device (known as a “backoff timer”) may start running for the duration of the wait time and may keep the device “on hold,” e.g., refraining from sending communications to the network, until the wait time expires and the device may be allowed to resend the request to the network.
  • A wait time value may be provided to the device (UE) in other instances. FIG. 3 is a block diagram 300 illustrating an instance where the UE 15 may initiate a connection request by sending an RRC connection request message 304 to the network controller 206. The network controller 206 in this instance may determine that the RAN 20 may be able to support an RRC connection associated with the RRC connection request message 304. Accordingly, the network controller 206 may respond with a connection setup message 308. A number of other handshake messages (not shown) may be transmitted between the UE 15 and the network controller 206 in accordance with an adapted communication protocol. For example, the UE 15 may respond to the connection setup message 308 with a notification that a connection setup is complete; the network controller 206 may issue a security mode establishment command; the UE 15 may notify the network controller 206 that the security mode has been established. In one embodiment, the network controller 206 may provide an RRC connection release message 310 that may include a wait time value. In summary, when the network is congested or overloaded, the network controller 206 may specify an extended wait time and ask the UE 15 to “back off” for the duration of the wait time. The foregoing describes how a UE 15 configured for dual priority may handle the situations when the network is congested and the UE 15 receives the wait time value from the network in response to a request (e.g., a connection request).
  • FIG. 4 is a process flow diagram illustrating communications between a network controller, e.g., network controller 206, and a UE, e.g., UE 15, in a wireless network environment in accordance with an embodiment. It is assumed that the UE is configured as a dual-priority device. For example, the UE may be configured to provide an ability to override, in some cases, low priority associated with the device or with one or more applications residing on the device. (It should be understood that “dual priority” in the context of this disclosure may mean two or more priorities. The example with two priorities is provided merely for illustrative purposes.)
  • The process 400 begins at block 402, where the UE may send a request (e.g., connection request) to the network controller. As discussed above, there may be different types of communications initiated by the mobile device, such as, for example, an RRC Connection Request. As described above in reference to FIG. 2, if the network is congested above a certain determined level that allows establishing a connection with the device the network controller may respond with a rejection message (e.g., the network controller may send the RRC Connection Reject message described above) along with a wait time value, as illustrated by block 404. At block 408, the received wait time may be used to start a backoff timer that determines the time period within which the device may refrain from sending another request to the network controller. At block 410, a priority value (e.g., default (low) priority or normal priority) associated with the device's request may be stored by the device for future use.
  • FIG. 5 is a process flow diagram for handling dual-priority communications by user equipment, e.g., UE 15, in a wireless network environment in accordance with some embodiments. The process 500 begins at block 502, where a UE may receive a configuration providing an ability to override a default (e.g., low) priority associated with the UE and/or applications residing on the UE. For example, a new configuration parameter may be added to the UE configuration that may override the default priority. More specifically, a new configuration parameter may be added to the non-access stratum (NAS) configuration of the UE that allows for overriding of the NAS low priority indicator setting. In another example, a new configuration parameter may be added to the non-access stratum configuration that allows for overriding an Extended Access Barring configuration, as discussed above. The configuration parameter may be provided by a provider of a wireless communication network in which the UE is operating. As described above, the wireless communication network may comprise UTRAN or E-UTRAN, for example.
  • At block 504, a communication, such as a request message to a network controller, e.g., network controller 206, may be initiated by the UE. For example, an application residing on the UE may indicate a need to send a request to the network controller. As discussed above, a request to the network controller may be any type of request, such as RRC Connection Request. In other examples, a UE may initiate a request to the network controller in connection with an attach procedure (e.g., request to “attach” the UE to the network), tracking area update procedure, location updating procedure, routing area update procedure, service request procedure, and the like. In yet another example, an application may initiate a request (e.g., request to send information to an end user via the network).
  • At decision block 506 it may be determined whether an application initiating a communication is associated with a priority level that is different than a default priority. For example, it may be determined whether an application is associated with a normal priority. If it is determined that the application initiating the communication is not associated with a priority other than a default priority, the process 500 moves to decision block 508. Otherwise, the process 500 moves to block 512.
  • At decision block 508 it may be determined whether a communication from the application requires overriding the default priority. As discussed above, some applications that typically are associated with, and send requests or other communications associated with, default (low) priority, occasionally may need to send communications associated with higher priority. For example, an electricity meter may want to send an alarm with “normal priority,” for example, if the meter is being tampered with or is being vandalized, as opposed to a daily report that is typically sent with a low priority.
  • If it is determined that the communication does not require overriding a default priority, at block 510 the communication is initiated (e.g., sent) to the controller with a default priority indication and is treated by the network controller according to an indicated priority.
  • If it is determined that the communication requires overriding a default (e.g., low) priority, the process 500 moves to block 512, where the low priority is overridden, for example, using the configuration setting as described in reference to block 502. At block 514, a communication is initiated (e.g., sent) to the controller with a different level of priority which is allowed by the dual priority character of the UE configuration (e.g., normal priority).
  • FIG. 6 is a process flow diagram for handling dual-priority communications by user equipment in a congested wireless network environment in accordance with some embodiments. As described above in reference to FIG. 4, in case of a congested network, the network controller may respond to a communication (e.g., request to connect) from UE with a rejection message that may include a wait time value directing the UE to refrain from sending communications to the network until the wait time expires. The UE may start a backoff timer with the received wait time value and store the priority value associated with the UE earlier communication that triggered the rejection from the network.
  • In some situations, the received wait time value may be ignored by the UE. However, for the purpose of an embodiment illustrated in FIG. 6 it is assumed that the UE may not ignore the received wait time value.
  • The process 600 begins at block 602, where the UE may be configured with a configuration providing an ability to override a default (e.g., low) priority associated with the UE and/or applications residing on the UE, similar to the example described above in reference to FIG. 5. At block 604, a communication to a network controller may be initiated by the UE. As described in reference to FIG. 5, a communication may relate to connection (e.g., a PDN connection) or other Mobility Management functions (e.g., attach procedure, tracking area update procedure, location updating procedure, routing area update procedure, service request procedure, and the like). At decision block 606 it may be determined whether a backoff timer associated with UE is running If it is determined that a backoff timer is not running, the process moves to block 614, where the initiated communication may be sent to the network controller.
  • If it is determined that the backoff timer is running, at decision block 608 it may be determined whether the backoff timer was started as a result of a prior communication (e.g., a response to a communication sent by the UE) that is associated with a default (e.g., low) priority. For example, the backoff timer may have been started due to prior Mobility Management functions, for example, NAS request messages such as attach request, tracking area update request, or extended service request. As described in reference to FIG. 4 (block 410), when the backoff timer starts, the priority value (low or normal) associated with the communication that triggers the backoff timer may be stored. Accordingly, a priority level of a communication that triggered the backoff timer may be determined at decision block 608. If it is determined that the backoff timer was started in connection with a communication having a priority level other than default (e.g., normal priority), the process 600 moves to block 616, where the initiated communication may be sent only upon an expiration of the backoff timer.
  • If it is determined that the backoff timer was started in connection with a prior communication having a low priority level (e.g., a prior NAS request message having a low priority level), at decision block 610 it may be determined whether the initiated communication is associated with a priority other than a default priority, e.g., normal priority. Some instances of requests that may be associated with a normal priority are described above in reference to FIG. 5 (block 508). If it is determined that the initiated communication is not associated with a priority other than a default (low) priority, the process 600 moves to block 616, where the initiated communication may be sent only upon an expiration of the backoff timer. If it is determined that the initiated communication is associated with a priority other than a default (low) priority, at block 612 the UE default (low) priority may be overridden. At block 614, the initiated communication may be sent with a priority other than default, e.g., normal priority, which is higher than the default low priority.
  • Embodiments of the present disclosure may be implemented into a system using any suitable hardware and/or software to configure as desired. FIG. 7 schematically illustrates an example system that may be used to practice various embodiments described herein. FIG. 7 illustrates, for one embodiment, an example system 700 having one or more processor(s) 704, system control module 708 coupled to at least one of the processor(s) 704, system memory 712 coupled to system control module 708, non-volatile memory (NVM)/storage 717 coupled to system control module 708, and one or more communications interface(s) 720 coupled to system control module 708.
  • In some embodiments, the system 700 may be capable of functioning as the UE 15 as described herein. In other embodiments, the system 700 may be capable of functioning as the one or more nodes 45 or one or more servers 50 of FIG. 1 or otherwise provide logic/module that performs functions as described for eNB 40, 42 and/or other modules described herein. In some embodiments, the system 700 may include one or more computer-readable media (e.g., system memory or NVM/storage 717) having instructions and one or more processors (e.g., processor(s) 704) coupled with the one or more computer-readable media and configured to execute the instructions to implement a module to perform actions described herein.
  • System control module 708 for one embodiment may include any suitable interface controllers to provide for any suitable interface to at least one of the processor(s) 704 and/or to any suitable device or component in communication with system control module 708.
  • System control module 708 may include memory controller module 710 to provide an interface to system memory 712. The memory controller module 710 may be a hardware module, a software module, and/or a firmware module.
  • System memory 712 may be used to load and store data and/or instructions, for example, for system 700. System memory 712 for one embodiment may include any suitable volatile memory, such as suitable DRAM, for example. In some embodiments, the system memory 712 may include double data rate type four synchronous dynamic random-access memory (DDR4 SDRAM).
  • System control module 708 for one embodiment may include one or more input/output (I/O) controller(s) to provide an interface to NVM/storage 717 and communications interface(s) 720.
  • The NVM/storage 717 may be used to store data and/or instructions, for example. NVM/storage 717 may include any suitable non-volatile memory, such as flash memory, for example, and/or may include any suitable non-volatile storage device(s), such as one or more hard disk drive(s) (HDD(s)), one or more compact disc (CD) drive(s), and/or one or more digital versatile disc (DVD) drive(s), for example.
  • The NVM/storage 717 may include a storage resource physically part of a device on which the system 700 is installed or it may be accessible by, but not necessarily a part of, the device. For example, the NVM/storage 717 may be accessed over a network via the communications interface(s) 720.
  • Communications interface(s) 720 may provide an interface for system 700 to communicate over one or more network(s) and/or with any other suitable device. The system 700 may wirelessly communicate with the one or more components of the wireless network in accordance with any of one or more wireless network standards and/or protocols.
  • For one embodiment, at least one of the processor(s) 704 may be packaged together with logic for one or more controller(s) of system control module 708, e.g., memory controller module 710. For one embodiment, at least one of the processor(s) 704 may be packaged together with logic for one or more controllers of system control module 708 to form a System in Package (SiP). For one embodiment, at least one of the processor(s) 704 may be integrated on the same die with logic for one or more controller(s) of system control module 708. For one embodiment, at least one of the processor(s) 704 may be integrated on the same die with logic for one or more controller(s) of system control module 708 to form a System on Chip (SoC).
  • In various embodiments, the system 700 may be, but is not limited to, a server, a workstation, a desktop computing device, or a mobile computing device (e.g., a laptop computing device, a handheld computing device, a tablet, a netbook, etc.). In various embodiments, the system 700 may have more or less components, and/or different architectures. For example, in some embodiments, the system 700 may include one or more of a camera, a keyboard, liquid crystal display (LCD) screen (including touch screen displays), non-volatile memory port, multiple antennas, graphics chip, application-specific integrated circuit (ASIC), and speakers.
  • According to various embodiments, the present disclosure describes a device, comprising one or more computer-readable media having instructions; and one or more processors coupled with the one or more computer-readable media and configured to execute the instructions to configure, as a default configuration, the device with a first priority level for machine-type communications; receive a notification from an application associated with the device, the notification indicating that the application generated a communication to a network controller, the communication being associated with a second priority level that is higher than the first priority level; and in response to the notification, configure, as an override configuration, the device with the second priority level for machine-type communications.
  • According to various embodiments, the present disclosure describes a system comprising a network controller having a controller processor and a controller memory having instructions stored thereon that, when executed on the controller processor, cause the controller processor to provide a wait time value in response to a first communication to the network controller. The system further includes a device configured with a first priority level for machine-type communications, the device having a device processor and a device memory having instructions stored thereon that, when executed on the device processor, cause the device processor to generate a second communication to the network controller; determine whether a backoff timer associated with the first communication is running; and based on the determination, determine whether to send the second communication to the network controller.
  • According to various embodiments, the present disclosure describes a computer-implemented method comprising enabling a dual priority configuration, the enabling including a default configuration with a first priority level and an ability to override the first priority level and assign a second priority level, the second priority level being higher than the first priority level; receiving an indication of a communication to be sent to a network controller, the communication being associated with the second priority level; and sending the communication with the second priority level to the network controller.
  • According to various embodiments, the present disclosure describes a computer-readable storage medium having instructions stored thereon that, when executed on a computing device, cause the computing device to configure a wireless device with a dual priority configuration, the configuring including assigning a default configuration associated with a first priority level and providing an ability to override the first priority level and assign a second priority level, the second priority level being higher than the first priority level; receive an indication of a communication to be sent to a network controller, the communication being associated with the second priority level; determine whether a backoff timer associated with an earlier communication is running; determine whether the earlier communication is associated with the first priority level; and send the communication when it is determined that the backoff timer is running and the earlier communication is associated with the first priority level.
  • Although certain embodiments have been illustrated and described herein for purposes of description, a wide variety of alternate and/or equivalent embodiments or implementations calculated to achieve the same purposes may be substituted for the embodiments shown and described without departing from the scope of the present disclosure. This application is intended to cover any adaptations or variations of the embodiments discussed herein. Therefore, it is manifestly intended that embodiments described herein be limited only by the claims and the equivalents thereof.

Claims (30)

1.-30. (canceled)
31. One or more computer-readable media having instructions that, when executed, cause a device to:
receive, from upper layers, a request that a user equipment (UE) access a wireless communication network for services associated with a first priority level;
determine a backoff timer is running; and
determine a timing of transmission of a non-access stratum (NAS) request message to a network controller based on a determination of whether the backoff timer was initiated based on another NAS request message communication having the first priority level or a second priority level that is lower than the first priority level.
32. The one or more computer-readable media of claim 31, wherein the instructions, when executed, further cause the device to:
determine that the backoff timer was initiated based on another NAS request message having the first priority level; and
transmit the NAS request message upon expiration of the backoff timer.
33. The one or more computer-readable media of claim 31, wherein the instructions, when executed, further cause the device to:
determine that the backoff timer was initiated based on another NAS request message having the second priority level; and
transmit the NAS request message while the backoff timer is running.
34. The one or more computer-readable media of claim 31, wherein the other NAS request message has an indicator to indicate the first or second priority level.
35. The one or more computer-readable media of claim 34, wherein the other NAS request message is an attach request, a tracking area update request, or an extended service request.
36. The one or more computer-readable media of claim 31, wherein the NAS request message is an attach request, a tracking area update request, or an extended service request.
37. The one or more computer-readable media of claim 31, wherein the instructions, when executed, further cause the device to:
add a configuration parameter associated with a device configuration management object, the configuration parameter to indicate an ability of the device to override a configuration of the device, wherein the configuration is a default configuration associated with the second priority level or an extended access barring (EAB) configuration.
38. The one or more computer-readable media of claim 37, wherein the configuration parameter is provided to the management object by a provider of the wireless communication network.
39. The one or more computer-readable media of claim 31, wherein the UE is a machine-to-machine device.
40. The one or more computer-readable media of claim 31, wherein the instructions, when executed, further cause the device to:
configure the device with a dual-priority configuration by assigning a default configuration associated with the second priority level and providing an ability to override the second priority level and assign the first priority level.
41. An apparatus comprising the one or more computer-readable media of claim 31 and further comprising:
one or more processors coupled with the one or more computer-readable media and configured to execute the instructions.
42. The apparatus of claim 41, wherein the apparatus is a machine-to-machine device.
43. The apparatus of claim 42, wherein the network controller is a machine-type communication (MTC) controller.
44. An apparatus comprising:
logic to configure, as a default configuration, the apparatus with a first priority level for machine-type communications over a wireless communication network;
logic to receive a notification from an application associated with the apparatus, the notification indicating that the application is associated with a second priority level that is higher than the first priority level; and
logic to, in response to the notification, configure, as an override configuration, the apparatus with the second priority level for machine-type communications.
45. The apparatus of claim 44, further comprising:
logic to determine whether a backoff timer associated with an earlier communication is running.
46. The apparatus of claim 45, further comprising:
logic to determine whether the earlier communication is associated with the first priority level; and
logic to initiate a communication to a network controller in an event it is determined that the earlier communication is associated with the first priority level.
47. The apparatus of claim 46, further comprising:
logic to initiate the communication to the network controller after the backoff timer expires in an event it is determined that the earlier communication is not associated with the first priority level, wherein the earlier communication is determined to be associated with the second priority level.
48. The apparatus of claim 46, wherein the communication to the network controller comprises a radio resource control (RRC) attach request, an RRC tracking area update request, an RRC service request, an RRC location request, or an RRC routing area update request.
49. The apparatus of claim 46, wherein the network controller is part of an evolved universal terrestrial radio access network (E-UTRAN).
50. The apparatus of claim 44, further comprising:
logic to add a configuration parameter associated with a device configuration management object, the configuration parameter indicating an ability to override the default configuration associated with the apparatus.
51. The apparatus of claim 50, wherein the configuration parameter is provided to the management object by a provider of the wireless communication network.
52. The apparatus of claim 44, wherein the apparatus is a machine-to-machine device.
53. One or more computer-readable media having instructions that, when executed, cause a network controller to:
configure a machine-to-machine (M2M) device with a dual-priority configuration in which the M2M device is able to override a default, low-priority configuration or an extended access barring configuration; and
receive one or more network requests from the M2M device, wherein individual network requests of the one or more network requests include priority indicators associated with respective network requests.
54. The one or more computer-readable media of claim 53, wherein the instructions, when executed, are to cause the network controller to:
provide, to a device configuration management object of the M2M device, a configuration parameter to indicate the ability of the M2M device to override the default, low-priority configuration or the extended access barring configuration.
55. An apparatus, comprising:
the one or more computer-readable media of claim 53; and
one or more processors coupled with the one or more computer readable media and configured to execute the instructions.
56. The apparatus of claim 55, further comprising the network controller, wherein the network controller is a machine-type communication (MTC) controller.
57. A computer-implemented method comprising:
under control of one or more computing devices configured with executable instructions,
enabling a dual priority non-access stratum (NAS) configuration, the enabling including a default configuration with a first priority level and an ability to override the first priority level and assign a second priority level, the second priority level being higher than the first priority level;
receiving, from upper layers, a request for services associated with the second priority level; and
sending a communication with the second priority level to a network controller.
58. The method of claim 57, wherein the sending the communication with the second priority level to the network controller includes:
determining whether a backoff timer associated with an earlier communication is running;
determining whether the earlier communication is associated with the first priority level; and
sending the communication when it is determined that the backoff timer is running and the earlier communication is associated with the first priority level.
59. The method of claim 57, further comprising:
sending the communication after the backoff timer expires when it is determined that the backoff timer is running and the earlier communication is not associated with the first priority level.
US13/526,307 2012-02-06 2012-06-18 Handling dual priority applications in a wireless communication network Abandoned US20130203399A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US201261595576P true 2012-02-06 2012-02-06
US13/526,307 US20130203399A1 (en) 2012-02-06 2012-06-18 Handling dual priority applications in a wireless communication network

Applications Claiming Priority (21)

Application Number Priority Date Filing Date Title
US13/526,307 US20130203399A1 (en) 2012-02-06 2012-06-18 Handling dual priority applications in a wireless communication network
US13/623,779 US20130201870A1 (en) 2012-02-06 2012-09-20 Handling dual priority applications in a wireless communication network
KR1020147021783A KR101592805B1 (en) 2012-02-06 2013-02-05 Handling dual priority configurations in a wireless communication network
JP2014555838A JP5876166B2 (en) 2012-02-06 2013-02-05 Handling dual priority configurations in wireless communication networks
AU2013217503A AU2013217503B2 (en) 2012-02-06 2013-02-05 Handling dual priority configurations in a wireless communication network
PCT/US2013/024793 WO2013119583A1 (en) 2012-02-06 2013-02-05 Handling dual priority configurations in a wireless communication network
CN201380008335.1A CN104094566B (en) 2012-02-06 2013-02-05 Handle equipment, method and the computer-readable medium of the dual priority configuration in cordless communication network
CA2861483A CA2861483C (en) 2012-02-06 2013-02-05 Handling dual priority configurations in a wireless communication network
CN201711114063.XA CN107613481A (en) 2012-02-06 2013-02-05 Handle the dual priority configuration in cordless communication network
FI20135108A FI20135108A (en) 2012-02-06 2013-02-05 Management of dual priority applications in a wireless communication network
EP13746668.6A EP2813039A4 (en) 2012-02-06 2013-02-05 Handling dual priority configurations in a wireless communication network
TW102104366A TWI635731B (en) 2012-02-06 2013-02-05 Method and apparatuses for handling dual priority configurations in a wireless communication network and computer-readable media thereof
IT000166A ITMI20130166A1 (en) 2012-02-06 2013-02-06 Management of configurations to priority 'double in a wireless communication network
BE201300079A BE1020827A5 (en) 2012-02-06 2013-02-06 Managing dual priority configurations in a wireless communication network.
CN2013101239602A CN103259619A (en) 2012-02-06 2013-02-06 Device of handling dual priority applications in a wireless communication network
NL2010249A NL2010249C2 (en) 2012-02-06 2013-02-06 Handling dual priority configurations in a wireless communication network.
FR1350995A FR2986934A1 (en) 2012-02-06 2013-02-06 Apparatus for handling wait time that is provided to e.g. machine-to-machine device, in congested e.g. network, has processors coupled with computer-readable media and executing instructions to determine whether to start backoff timer
ES201330139A ES2453444B2 (en) 2012-02-06 2013-02-06 Treatment of dual priority configurations in a wireless communications network
US13/971,795 US20130336218A1 (en) 2012-02-06 2013-08-20 Handling dual priority configurations in a wireless communication network
HK14112745.7A HK1199335A1 (en) 2012-02-06 2014-12-19 Handling dual priority configurations in a wireless communication network
HK15101120.4A HK1200990A1 (en) 2012-02-06 2015-02-03 Handling dual priority configurations in a wireless communication network

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/623,779 Continuation-In-Part US20130201870A1 (en) 2012-02-06 2012-09-20 Handling dual priority applications in a wireless communication network

Publications (1)

Publication Number Publication Date
US20130203399A1 true US20130203399A1 (en) 2013-08-08

Family

ID=48047768

Family Applications (6)

Application Number Title Priority Date Filing Date
US13/997,595 Abandoned US20140219115A1 (en) 2012-02-06 2012-06-08 Signaling for configuration of downlink coordinated multipoint communications
US13/526,307 Abandoned US20130203399A1 (en) 2012-02-06 2012-06-18 Handling dual priority applications in a wireless communication network
US13/526,302 Active US9055477B2 (en) 2012-02-06 2012-06-18 Handling wait time in a congested wireless communication network
US13/563,508 Active 2032-11-28 US9071999B2 (en) 2012-02-06 2012-07-31 Handling user plane congestion in a wireless communication network
US13/917,324 Active US9125103B2 (en) 2012-02-06 2013-06-13 Handling wait time in a congested wireless communication network
US14/754,173 Active US9736074B2 (en) 2012-02-06 2015-06-29 Handling user plane congestion in a wireless communication network

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US13/997,595 Abandoned US20140219115A1 (en) 2012-02-06 2012-06-08 Signaling for configuration of downlink coordinated multipoint communications

Family Applications After (4)

Application Number Title Priority Date Filing Date
US13/526,302 Active US9055477B2 (en) 2012-02-06 2012-06-18 Handling wait time in a congested wireless communication network
US13/563,508 Active 2032-11-28 US9071999B2 (en) 2012-02-06 2012-07-31 Handling user plane congestion in a wireless communication network
US13/917,324 Active US9125103B2 (en) 2012-02-06 2013-06-13 Handling wait time in a congested wireless communication network
US14/754,173 Active US9736074B2 (en) 2012-02-06 2015-06-29 Handling user plane congestion in a wireless communication network

Country Status (14)

Country Link
US (6) US20140219115A1 (en)
EP (3) EP2813007A4 (en)
JP (4) JP5893760B2 (en)
KR (4) KR101594942B1 (en)
CN (4) CN104115422B (en)
CA (1) CA2861432C (en)
ES (1) ES2440370B2 (en)
FI (1) FI126448B (en)
FR (1) FR2986933B1 (en)
IT (1) IT1416452B1 (en)
NL (1) NL2010250C2 (en)
SE (2) SE1650715A1 (en)
TW (1) TWI523551B (en)
WO (3) WO2013119267A2 (en)

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130182644A1 (en) * 2012-01-18 2013-07-18 Lg Electronics Inc. Control method and device based on multiple priorities in wireless communication system
US20130235775A1 (en) * 2008-06-13 2013-09-12 Research In Motion Limited Apparatus and method for transmitting messages in mobile telecommunications system user equipment
US20130304956A1 (en) * 2012-05-10 2013-11-14 Alcatel-Lucent Telecom Ltd. Methods and apparatuses for multiple priority access in a wireless network system
US20140029530A1 (en) * 2012-07-26 2014-01-30 Lg Electronics Inc. Method and terminal for applying an extended access barring
US20140064069A1 (en) * 2012-08-29 2014-03-06 Htc Corporation Method of Handling Non-Access Stratum Message and Related Communication Device
US20140153546A1 (en) * 2012-11-07 2014-06-05 Lg Electronics Inc. Method and an apparatus for access network selection in a wireless communication system
US20150085658A1 (en) * 2012-04-04 2015-03-26 Kt Corporation Method and apparatus for controlling access to machine-type communication device having dual priority application
US20150249900A1 (en) * 2012-09-26 2015-09-03 Lg Electronics Inc. Mtc monitoring method
US20150256961A1 (en) * 2012-10-05 2015-09-10 Lg Electronics Inc. Method and device for controlling multipriority in wireless communication system
US20150264550A1 (en) * 2012-12-18 2015-09-17 Jeffrey Douglas Johnson Systems, devices and methods to communicate public safety information
US20170071025A1 (en) * 2013-11-29 2017-03-09 Zte Corporation NAS Connection Establishment Method, System and Radio Access Network Node
US20170171873A1 (en) * 2015-12-15 2017-06-15 At&T Intellectual Property I, L.P. Method, computer-readable storage device and apparatus for processing machine-to-machine communications

Families Citing this family (44)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9264097B2 (en) 2009-06-04 2016-02-16 Qualcomm Incorporated Interference mitigation for downlink in a wireless communication system
MX2013010241A (en) 2011-03-08 2014-04-16 Abengoa Solar Inc Trough solar collector module.
TW201246879A (en) 2011-04-13 2012-11-16 Interdigital Patent Holdings Methods, systems and apparatus for managing and/or enforcing policies for managing internet protocol (''IP'') traffic among multiple accesses of a network
WO2013107025A1 (en) * 2012-01-19 2013-07-25 Panasonic Corporation Method of scrambling reference signals, device and user equipment using the method
US10038534B2 (en) * 2012-01-19 2018-07-31 Sun Patent Trust Method of scrambling reference signals, device and user equipment using the method
US9807644B2 (en) * 2012-02-17 2017-10-31 Interdigital Patent Holdings, Inc. Hierarchical traffic differentiation to handle congestion and/or manage user quality of experience
GB2499674B (en) * 2012-02-27 2014-03-26 Broadcom Corp Method and apparatus for coordinated multi-point operations
WO2013133597A1 (en) * 2012-03-08 2013-09-12 엘지전자 주식회사 Method and apparatus for transmitting information for reporting in wireless communication system
US9276646B2 (en) * 2012-04-27 2016-03-01 Htc Corporation Method of managing cooperating set for coordinated multiple point transmission and reception and related communication device
US20130301448A1 (en) * 2012-05-09 2013-11-14 Samsung Electronics Co., Ltd Csi definitions and feedback modes for coordinated multi-point transmission
US20130336193A1 (en) * 2012-06-19 2013-12-19 Qualcomm Incorporated Network information for assisting user equipment
US9585054B2 (en) 2012-07-19 2017-02-28 Interdigital Patent Holdings, Inc. Method and apparatus for detecting and managing user plane congestion
US20140029458A1 (en) * 2012-07-24 2014-01-30 Acer Incorporated Apparatuses and methods for signaling coordinated multi-point (comp) measurement configuration
JP6016262B2 (en) * 2012-07-31 2016-10-26 日本電気通信システム株式会社 Mobile terminal, control node, packet forwarding node, and method for congestion control
US9456358B2 (en) * 2012-08-13 2016-09-27 Qualcomm Incorporated Method and apparatus for indicating active channel state information reference signal (CSI-RS) configurations
WO2014047927A1 (en) * 2012-09-29 2014-04-03 华为技术有限公司 Control information sending method, receiving method, and apparatus
WO2014047925A1 (en) * 2012-09-29 2014-04-03 华为技术有限公司 Interference measurement method, base station and user equipment
WO2014065898A1 (en) * 2012-10-26 2014-05-01 Intel Corporation Reporting of user plane congestion
CN104854898A (en) * 2013-01-04 2015-08-19 富士通株式会社 Method for channel measurement, configuration method and apparatus for channel measurement
US9973966B2 (en) 2013-01-11 2018-05-15 Interdigital Patent Holdings, Inc. User-plane congestion management
JP5950023B2 (en) * 2013-03-18 2016-07-13 富士通株式会社 Communication path control apparatus, address conversion apparatus, communication system, and communication path setting method
WO2014175919A1 (en) 2013-04-26 2014-10-30 Intel IP Corporation Shared spectrum reassignment in a spectrum sharing context
WO2014198747A1 (en) * 2013-06-12 2014-12-18 Telefonaktiebolaget L M Ericsson (Publ) Method, apparatus, system, computer program and computer program product for mitigating end user congestion in a wireless network
KR20150006316A (en) 2013-07-08 2015-01-16 삼성전자주식회사 Apparatus and method for controlling control overload in wlan systems
EP2835927B1 (en) * 2013-08-07 2016-11-30 Samsung Electronics Co., Ltd Method and apparatus for scheduling resources at relay station (RS) in mobile communication network
JP6178186B2 (en) * 2013-09-24 2017-08-09 Kddi株式会社 Communication control device, radio communication system, communication control method, and computer program
JP6055389B2 (en) * 2013-10-08 2016-12-27 株式会社Nttドコモ Wireless base station
EP3069554A1 (en) 2013-11-13 2016-09-21 Huawei Technologies Co., Ltd. Transmission of machine type communications data using disrupted connectivity
US9681325B2 (en) * 2013-12-19 2017-06-13 Qualcomm Incorporated Channel and interference measurement in LTE/LTE-A networks including unlicensed spectrum
EP3079404B1 (en) * 2013-12-30 2018-02-21 Huawei Technologies Co., Ltd. Fault handling methods, packet data network gateway , mobility management entity and network system
US9591509B2 (en) 2014-04-10 2017-03-07 Qualcomm Incorporated Congestion control scheme
US9807669B1 (en) * 2014-10-24 2017-10-31 Sprint Communications Company L.P. Identifying communication paths based on packet data network gateway status reports
EP3030031B1 (en) * 2014-12-01 2017-09-06 Mitsubishi Electric R&D Centre Europe B.V. Method for allocating transmission resources in a wireless communications network
CN107210801A (en) * 2015-02-05 2017-09-26 Lg 电子株式会社 The method and its device of CSI feedback in wireless communication system
JP6473013B2 (en) * 2015-02-24 2019-02-20 Kddi株式会社 Control device, control method and program
CN106160823A (en) * 2015-04-03 2016-11-23 索尼公司 Device for wireless communications and method
WO2016167506A1 (en) 2015-04-15 2016-10-20 Lg Electronics Inc. Method for generating a mac control element in a carrier aggregation system and a device therefor
US9930517B2 (en) * 2015-10-30 2018-03-27 Acer Incorporated Apparatuses and methods for handling change of user equipment (UE) usage type
CN107294583A (en) * 2016-03-31 2017-10-24 华为技术有限公司 A kind of channel status measuring method and device
WO2018008977A1 (en) * 2016-07-05 2018-01-11 Samsung Electronics Co., Ltd. A method of handling control plane data in a wireless network
JPWO2018084115A1 (en) * 2016-11-01 2019-09-19 株式会社Nttドコモ Wireless terminal apparatus and communication method
WO2018131413A1 (en) * 2017-01-10 2018-07-19 株式会社Nttドコモ Mobile communication system and congestion control method
JP6503038B2 (en) * 2017-10-04 2019-04-17 京セラ株式会社 Control method for wireless communication system, wireless communication system, and base station
WO2019216807A1 (en) * 2018-05-07 2019-11-14 Telefonaktiebolaget Lm Ericsson (Publ) Methods for handling periodic radio access network notification area (rna) update configuration upon reject

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110274040A1 (en) * 2010-02-12 2011-11-10 Interdigital Patent Holdings, Inc. Method and apparatus for optimizing uplink random access channel transmission
US20110287765A1 (en) * 2010-05-04 2011-11-24 Vodafone Ip Licensing Limited Operation of machine-type communication devices
US20120002545A1 (en) * 2010-06-07 2012-01-05 Interdigital Patent Holdings, Inc. Method and apparatus for transmitting service request messages in a congested network
US20120263036A1 (en) * 2011-04-14 2012-10-18 Barclay Deborah L Mechanism for wireless access networks to throttle traffic during congestion
US20140016616A1 (en) * 2011-03-31 2014-01-16 Telefonaktiebolaget L M Ericsson (Publ) Low priority indication in extended service request for enhanced overload handling

Family Cites Families (49)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6400695B1 (en) 1998-05-22 2002-06-04 Lucent Technologies Inc. Methods and apparatus for retransmission based access priority in a communications system
CA2301435C (en) * 1999-04-16 2006-10-10 At&T Corp. Method for reducing congestion in packet-switched networks
US7133422B2 (en) * 2002-01-31 2006-11-07 Texas Instruments Incorporated Implementing enhanced distributed coordinating function (EDCF) with a single hardware backoff counter
US6961570B2 (en) * 2002-07-17 2005-11-01 Asustek Computer Inc. Handling of a wireless device re-entering a service area
KR100728546B1 (en) * 2002-11-04 2007-06-15 리서치 인 모션 리미티드 Method and system for maintaining a wireless data connection
FR2848052B1 (en) * 2002-11-29 2005-03-18 Orange France System and method for selection in a terminal for an architecture dedicated to a communication network
US7796507B2 (en) * 2005-12-29 2010-09-14 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for communication network congestion control
JP2008017409A (en) * 2006-07-10 2008-01-24 Hitachi Ltd QoS CONTROL SYSTEM, QoS CONTROL DEVICE AND SESSION CONTROL DEVICE
GB0619179D0 (en) 2006-09-29 2006-11-08 Ip Access Ltd Telecommunications access control system and method
CN101400099A (en) * 2007-09-27 2009-04-01 华为技术有限公司 Load information providing method, S-GW, control method for service gateway and MME
WO2009054702A1 (en) 2007-10-25 2009-04-30 Lg Electronics Inc. Method of measuring cell in wireless communication system
WO2009090160A1 (en) 2008-01-14 2009-07-23 Telefonaktiebolaget Lm Ericsson (Publ) Method and nodes for congestion notification
US8248941B2 (en) * 2008-02-01 2012-08-21 Nokia Siemens Networks Oy Method, apparatus and computer program for uplink scheduling in a network that employs relay nodes
US8515436B2 (en) 2008-03-27 2013-08-20 Qualcomm Incorporated Management of wireless connections
US8295174B2 (en) * 2008-03-28 2012-10-23 Research In Motion Limited Proactive uplink aggregate maximum bit rate enforcement
CN101459928B (en) * 2008-04-16 2010-12-08 中兴通讯股份有限公司 Overload notification method between network elements
RU2467510C1 (en) 2008-08-08 2012-11-20 Интердиджитал Пэйтент Холдингз, Инк. Method and apparatus for performing serving high speed downlink shared channel change
US8838089B2 (en) * 2008-10-20 2014-09-16 Htc Corporation Method of improving radio resource control connenction establishment in a wireless communication system and related communication device
US8289848B2 (en) 2009-02-02 2012-10-16 Telefonaktiebolaget Lm Ericsson (Publ) Controlling a packet flow from a user equipment
WO2010102127A1 (en) * 2009-03-04 2010-09-10 Cisco Technology, Inc. Detecting overloads in network devices
US8917707B2 (en) * 2009-04-24 2014-12-23 Samsung Electronics Co., Ltd. Techniques for channel state information feedback in wireless communication system
US20100302951A1 (en) * 2009-05-26 2010-12-02 Ou Meng-Hui Method and Apparatus for Handling Radio Link Failure
US9357568B2 (en) 2009-06-16 2016-05-31 Futurewei Technologies, Inc. System and method for adapting an application source rate to a load condition
US8570963B2 (en) * 2009-10-26 2013-10-29 Qualcomm Incorporated Coordinated multi-point (CoMP) network and protocol architecture
CN102118830B (en) * 2010-01-05 2014-08-06 华为技术有限公司 Access control method, device and system.
US8693320B2 (en) 2010-01-11 2014-04-08 Research In Motion Limited Congestion level indication with explicit congestion notification in communication systems
US8599708B2 (en) * 2010-01-14 2013-12-03 Qualcomm Incorporated Channel feedback based on reference signal
US8767584B2 (en) 2010-01-29 2014-07-01 Alcatel Lucent Method and apparatus for analyzing mobile services delivery
EP2360864A1 (en) * 2010-02-12 2011-08-24 Panasonic Corporation Component carrier (de)activation in communication systems using carrier aggregation
US8305987B2 (en) * 2010-02-12 2012-11-06 Research In Motion Limited Reference signal for a coordinated multi-point network implementation
CN104780030B (en) * 2010-03-17 2018-11-09 Lg电子株式会社 Method, base station and the movement station of channel state information-reference signal are sent in the wireless communication system for supporting mutiple antennas
US20110261695A1 (en) * 2010-04-23 2011-10-27 Xiaoming Zhao System and method for network congestion control
WO2011136589A2 (en) * 2010-04-28 2011-11-03 엘지전자 주식회사 Method for controlling congestion of mtc data in a mobile communication system
US20110267948A1 (en) * 2010-05-03 2011-11-03 Koc Ali T Techniques for communicating and managing congestion in a wireless network
WO2011160308A1 (en) * 2010-06-25 2011-12-29 华为技术有限公司 Method for processing network congestion, network device and network system
WO2012006005A2 (en) * 2010-06-29 2012-01-12 Interdigital Patent Holdings, Inc. Demodulation reference signal based channel state information feedback in ofdm-mimo systems
CN101877608B (en) * 2010-06-30 2015-07-22 中兴通讯股份有限公司 Optimized weighted CSI feeding back method and device for cooperative beam forming
CN102421141A (en) * 2010-09-28 2012-04-18 大唐移动通信设备有限公司 Capability notification method as well as method, system and equipment for controlling network congestion
US8554933B2 (en) * 2010-10-05 2013-10-08 Verizon Patent And Licensing Inc. Dynamic selection of packet data network gateways
JP5330477B2 (en) * 2010-10-05 2013-10-30 宏達國際電子股▲ふん▼有限公司 Method for handling congestion control based on access point name and associated communication device
KR101752707B1 (en) * 2011-01-03 2017-07-03 삼성전자 주식회사 Method for controlling congestion in mobile communication system
US20120178449A1 (en) * 2011-01-11 2012-07-12 Liao Ching-Yu Apparatuses and methods for handling mobility management (mm) back-offs
WO2012097875A1 (en) * 2011-01-20 2012-07-26 Telefonaktiebolaget Lm Ericsson (Publ) Gateway allocation in a mobile communication system
CN102098759A (en) * 2011-02-18 2011-06-15 电信科学技术研究院 Method and device for access control
CN102255689B (en) * 2011-07-08 2018-05-04 中兴通讯股份有限公司 A kind of processing method of channel condition information, apparatus and system
US9197387B2 (en) * 2011-08-15 2015-11-24 Google Technology Holdings LLC Method and apparatus for control channel transmission and reception
US20130083681A1 (en) * 2011-09-30 2013-04-04 Research In Motion Limited Methods of Channel State Information Feedback and Transmission in Coordinated Multi-Point Wireless Communications System
US20130166644A1 (en) * 2011-12-23 2013-06-27 Futurewei Technologies, Inc. System and Method for Resource Management in Multiple Communications Point Operation
US8953478B2 (en) * 2012-01-27 2015-02-10 Intel Corporation Evolved node B and method for coherent coordinated multipoint transmission with per CSI-RS feedback

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110274040A1 (en) * 2010-02-12 2011-11-10 Interdigital Patent Holdings, Inc. Method and apparatus for optimizing uplink random access channel transmission
US20110287765A1 (en) * 2010-05-04 2011-11-24 Vodafone Ip Licensing Limited Operation of machine-type communication devices
US20120002545A1 (en) * 2010-06-07 2012-01-05 Interdigital Patent Holdings, Inc. Method and apparatus for transmitting service request messages in a congested network
US20140016616A1 (en) * 2011-03-31 2014-01-16 Telefonaktiebolaget L M Ericsson (Publ) Low priority indication in extended service request for enhanced overload handling
US20120263036A1 (en) * 2011-04-14 2012-10-18 Barclay Deborah L Mechanism for wireless access networks to throttle traffic during congestion

Cited By (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9913221B2 (en) 2008-06-13 2018-03-06 Blackberry Limited Apparatus and method for transmitting messages in mobile telecommunications system user equipment
US20130235775A1 (en) * 2008-06-13 2013-09-12 Research In Motion Limited Apparatus and method for transmitting messages in mobile telecommunications system user equipment
US9432934B2 (en) * 2008-06-13 2016-08-30 Blackberry Limited Apparatus and method for transmitting messages in mobile telecommunications system user equipment
US9743447B2 (en) * 2012-01-18 2017-08-22 Lg Electronics Inc. Control method and device based on multiple priorities in wireless communication system
US20130182644A1 (en) * 2012-01-18 2013-07-18 Lg Electronics Inc. Control method and device based on multiple priorities in wireless communication system
US9386478B2 (en) * 2012-04-04 2016-07-05 Kt Corporation Method and apparatus for controlling access to machine-type communication device having dual priority application
US20150085658A1 (en) * 2012-04-04 2015-03-26 Kt Corporation Method and apparatus for controlling access to machine-type communication device having dual priority application
US9015395B2 (en) * 2012-05-10 2015-04-21 Alcatel Lucent Methods and apparatuses for multiple priority access in a wireless network system
US20130304956A1 (en) * 2012-05-10 2013-11-14 Alcatel-Lucent Telecom Ltd. Methods and apparatuses for multiple priority access in a wireless network system
US9125137B2 (en) * 2012-07-26 2015-09-01 Lg Electronics Inc. Method and terminal for applying an extended access barring
US20140029530A1 (en) * 2012-07-26 2014-01-30 Lg Electronics Inc. Method and terminal for applying an extended access barring
US9426687B2 (en) * 2012-08-29 2016-08-23 Htc Corporation Method of handling non-access stratum message and related communication device
US20140064069A1 (en) * 2012-08-29 2014-03-06 Htc Corporation Method of Handling Non-Access Stratum Message and Related Communication Device
US20150249900A1 (en) * 2012-09-26 2015-09-03 Lg Electronics Inc. Mtc monitoring method
US9628941B2 (en) * 2012-09-26 2017-04-18 Lg Electronics Inc. MTC monitoring method
US20170094443A1 (en) * 2012-10-05 2017-03-30 Lg Electronics Inc. Method and device for controlling multipriority in wireless communication system
US9554233B2 (en) * 2012-10-05 2017-01-24 Lg Electronics Inc. Method and device for controlling multipriority in wireless communication system
US20150256961A1 (en) * 2012-10-05 2015-09-10 Lg Electronics Inc. Method and device for controlling multipriority in wireless communication system
US9894465B2 (en) * 2012-10-05 2018-02-13 Lg Electronics Inc. Method and device for controlling multipriority in wireless communication system
US9900832B2 (en) * 2012-11-07 2018-02-20 Lg Electronics Inc. Method and an apparatus for access network selection in a wireless communication system
US20140153546A1 (en) * 2012-11-07 2014-06-05 Lg Electronics Inc. Method and an apparatus for access network selection in a wireless communication system
US20150264550A1 (en) * 2012-12-18 2015-09-17 Jeffrey Douglas Johnson Systems, devices and methods to communicate public safety information
US9913121B2 (en) * 2012-12-18 2018-03-06 James Petrizzi Systems, devices and methods to communicate public safety information
US9723648B2 (en) * 2013-11-29 2017-08-01 Zte Corporation NAS connection establishment method, system and radio access network node
US20170071025A1 (en) * 2013-11-29 2017-03-09 Zte Corporation NAS Connection Establishment Method, System and Radio Access Network Node
US9860906B2 (en) * 2015-12-15 2018-01-02 At&T Intellectual Property I, L.P. Method, computer-readable storage device and apparatus for processing machine-to-machine communications
US20170171873A1 (en) * 2015-12-15 2017-06-15 At&T Intellectual Property I, L.P. Method, computer-readable storage device and apparatus for processing machine-to-machine communications

Also Published As

Publication number Publication date
WO2013119267A2 (en) 2013-08-15
FR2986933A1 (en) 2013-08-16
CN104115422A (en) 2014-10-22
US9125103B2 (en) 2015-09-01
NL2010250A (en) 2013-08-08
SE1650715A1 (en) 2016-05-24
US20130272124A1 (en) 2013-10-17
JP6238486B2 (en) 2017-11-29
EP2813038A4 (en) 2016-02-17
JP5945775B2 (en) 2016-07-05
FI20135109A (en) 2013-08-07
JP5986228B2 (en) 2016-09-06
KR101762086B1 (en) 2017-07-26
NL2010250C2 (en) 2014-03-24
KR20140115338A (en) 2014-09-30
CN104115422B (en) 2018-09-25
WO2013119267A3 (en) 2013-12-19
KR20140116472A (en) 2014-10-02
JP2015505660A (en) 2015-02-23
JP5893760B2 (en) 2016-03-23
CN103249113B (en) 2016-12-28
US20150381497A1 (en) 2015-12-31
ES2440370R1 (en) 2014-07-11
JP2016226014A (en) 2016-12-28
US20130201823A1 (en) 2013-08-08
CN104094563A (en) 2014-10-08
US9071999B2 (en) 2015-06-30
TWI523551B (en) 2016-02-21
EP2813038A1 (en) 2014-12-17
ITMI20130167A1 (en) 2013-08-07
KR101606484B1 (en) 2016-03-25
FR2986933B1 (en) 2018-05-11
ES2440370A2 (en) 2014-01-28
CN107104755A (en) 2017-08-29
EP2813007A4 (en) 2015-10-28
WO2013119585A1 (en) 2013-08-15
US20130201824A1 (en) 2013-08-08
TW201404195A (en) 2014-01-16
IT1416452B1 (en) 2015-06-19
EP2813007A2 (en) 2014-12-17
JP2015511452A (en) 2015-04-16
WO2013119506A1 (en) 2013-08-15
JP2015506651A (en) 2015-03-02
KR101594942B1 (en) 2016-02-26
SE1300090A1 (en) 2013-09-12
US20140219115A1 (en) 2014-08-07
KR20140114008A (en) 2014-09-25
US9055477B2 (en) 2015-06-09
EP2813124A1 (en) 2014-12-17
CA2861432C (en) 2017-04-18
EP2813124A4 (en) 2015-08-05
CA2861432A1 (en) 2013-08-15
CN103249113A (en) 2013-08-14
US9736074B2 (en) 2017-08-15
ES2440370B2 (en) 2015-04-22
KR20160075868A (en) 2016-06-29
FI126448B (en) 2016-12-15

Similar Documents

Publication Publication Date Title
JP6371361B2 (en) Small data techniques and configuration in wireless communication networks
US9807590B2 (en) Techniques to facilitate dual connectivity
JP6227017B2 (en) Efficient signaling for machine type communication
TWI528772B (en) Techniques and systems for extended discontinuous reception
US9326207B2 (en) Enhanced node B and methods for providing system information updates to user equipment with extended paging cycles
US10206226B2 (en) Coordination techniques for radio resource control state management in dual-connectivity architectures
KR101752625B1 (en) Machine type communication preregistration
TWI498032B (en) Method and apparatus for machine-to-machine communication registration
US9288434B2 (en) Apparatus and method for congestion control in wireless communication networks
US20120040700A1 (en) Group paging for machine-type communications
CN104956721B (en) For configure and using small data radio bearer method and apparatus
JP6228132B2 (en) Multiple Priority Control Method and Apparatus in Wireless Communication System
US20150201342A1 (en) Energy-harvesting devices in wireless networks
US20130148560A1 (en) Component carrier uplink maximum transmission power reporting scheme for carrier aggregation
CN104205667B (en) For triggering the technology of multiple wireless devices and configuration
US9191806B2 (en) Method and apparatus for retransmitting MTC group message in wireless communication system
KR20120098899A (en) Group-based machine to machine communication
US20170019750A1 (en) Overload control and coordination between m2m service layer and 3gpp networks
EP2848075B1 (en) Packet data network connections for multi priority wireless devices
EP2880616B1 (en) Device-to-device advertisement
US20120252518A1 (en) Network initiated triggering of an offline device
JP6422469B2 (en) Apparatus and method for machine type communication
EP3202189B1 (en) Service capability server/epc coordination for power savings mode and paging
CN107104755A (en) Dispose the stand-by period in the cordless communication network of congestion
US9544709B2 (en) Small data transmission techniques in a wireless communication network

Legal Events

Date Code Title Description
AS Assignment

Owner name: INTEL CORPORATION, CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:GUPTA, VIVEK;REEL/FRAME:028396/0590

Effective date: 20120614

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION