US20150078154A1 - Congestion control for short message service in 3rd generation partnership project (3gpp) systems - Google Patents
Congestion control for short message service in 3rd generation partnership project (3gpp) systems Download PDFInfo
- Publication number
- US20150078154A1 US20150078154A1 US14/486,651 US201414486651A US2015078154A1 US 20150078154 A1 US20150078154 A1 US 20150078154A1 US 201414486651 A US201414486651 A US 201414486651A US 2015078154 A1 US2015078154 A1 US 2015078154A1
- Authority
- US
- United States
- Prior art keywords
- sms
- message
- network
- short message
- mme
- 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
Links
Images
Classifications
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
- G01S5/00—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations
- G01S5/02—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations using radio waves
- G01S5/0205—Details
- G01S5/0236—Assistance data, e.g. base station almanac
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/24—Radio transmission systems, i.e. using radiation field for communication between two or more posts
- H04B7/26—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile
- H04B7/2643—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile using time-division multiple access [TDMA]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J13/00—Code division multiplex systems
- H04J13/0007—Code type
- H04J13/004—Orthogonal
- H04J13/0048—Walsh
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J3/00—Time-division multiplex systems
- H04J3/02—Details
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1829—Arrangements specially adapted for the receiver end
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1867—Arrangements specially adapted for the transmitter end
- H04L1/1893—Physical mapping arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L27/00—Modulated-carrier systems
- H04L27/26—Systems using multi-frequency codes
- H04L27/2601—Multicarrier modulation systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
- H04L5/0051—Allocation of pilot signals, i.e. of signals known to the receiver of dedicated pilots, i.e. pilots destined for a single user or terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/14—Two-way operation using the same type of signal, i.e. duplex
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0231—Traffic management, e.g. flow control or congestion control based on communication conditions
- H04W28/0236—Traffic management, e.g. flow control or congestion control based on communication conditions radio quality, e.g. interference, losses or delay
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0231—Traffic management, e.g. flow control or congestion control based on communication conditions
- H04W28/0242—Determining whether packet losses are due to overload or to deterioration of radio communication conditions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0247—Traffic management, e.g. flow control or congestion control based on conditions of the access network or the infrastructure network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/04—Reselecting a cell layer in multi-layered cells
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
- H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
- H04W72/044—Wireless resource allocation based on the type of the allocated resource
- H04W72/0446—Resources in time domain, e.g. slots or frames
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
- H04W72/044—Wireless resource allocation based on the type of the allocated resource
- H04W72/0466—Wireless resource allocation based on the type of the allocated resource the resource being a scrambling code
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/10—Flow control between communication endpoints
- H04W28/12—Flow control between communication endpoints using signalling between network elements
Definitions
- the present disclosure generally relates to management of short message (SM) loads and, more particularly, to management of mobile originated (MO) short message service (SMS) messages, mobile terminated (MT) SMS messages, and other types of SMs including small data transfer and device triggering via a mobility management entity (MME) or serving general packet radio service (GPRS) support node (SGSN).
- MME mobility management entity
- GPRS general packet radio service
- 3GPP network systems provide for transport, subscriber management, and other communication services including various architectural enhancements motivated by, but not restricted to, MTC.
- one such service is control plane device triggering—so-called device triggering, or simply, triggering.
- Device triggering is a technique to send information (e.g., a device trigger, or simply, trigger) to a user equipment device (or simply, UE) to cause it to perform application specific actions including initiating communications with a services capability server (SCS) (in an indirect communication model system) or an application server (AS) (in a direct communication model system).
- SCS services capability server
- AS application server
- device triggering is frequently employed when a network address for a UE is not available or reachable by the SCS/AS.
- a device trigger message may be used to establish communications because the trigger includes information that facilitates routing of messages in a 3GPP network to an appropriate UE application, and facilitates that UE application to route messages to an appropriate SCS/AS application.
- T4 device triggering uses MT-SMS messages for delivering a device trigger to a UE, as defined in 3GPP TS 23.682 for release no. 11 (Rel-11) of the 3GPP standardization.
- a device trigger may include other information, such as user data, conveyed by means of the SMS protocol.
- Rel-11 also includes a feature in which SMs can be delivered to UE via an enhanced MME.
- the enhanced MME is the network entity that supports the so-called SMS in MME feature.
- NAS non-access stratum
- API access point name
- NAS level mobility management congestion control includes two types of control: access point name (APN) based congestion control, and general NAS level mobility management congestion control.
- APN based congestion control is applicable to UEs that are members of a particular APN.
- the network can provide a maximum limit of the number of connections (bearers) or the number of network accesses to the network.
- General NAS level mobility management congestion control is applicable when numerous UEs initiate nearly simultaneous network access attempts, which cause congestion in the serving core network (CN) node, e.g., an MME or serving general packet radio service (GPRS) support node (SGSN).
- CN serving core network
- GPRS general packet radio service
- the 3GPP standardization currently does not provide for an MME/SGSN that assesses NAS level congestion controls to determine whether and when to deliver (or reject) SMs.
- FIG. 1 is a block diagram of network entities forming a portion of a 3GPP system, according to one embodiment.
- FIG. 2 is a message sequence chart showing an MME or SGSN controlling delivery of MT-SMSs or SM device triggers during an overload situation, according to one embodiment.
- FIG. 3 is a block diagram of a UE, according to one embodiment.
- This portion of the disclosure describes MMEs and SGSNs capable of controlling device trigger loads by communicating diameter-based messages over, respectively, SGd and Gdd interfaces (also called reference points) with associated SMS entities.
- MME and SGSN functionality can be implemented on either a single hardware device or as separate network entities (i.e., separate devices).
- MME/SGSN an MME and SGSN are referred to generally as an MME/SGSN, by which the “/” connotes an inclusive disjunction meaning an MME, an SGSN, or a combination of both an MME and an SGSN.
- the “/” notation is used for other network entities, interfaces, and functions that are similar to each other and can therefore be embodied as one or multiple devices.
- the SCS/AS mentioned in the background information of this disclosure is one such example.
- SMS-SC short message service-service center
- the first subsection describes an example of 3GPP network components that are pertinent to congestion control over SGd/Gdd interfaces.
- the second subsection describes examples of MME/SGSN control of MT-SMS loads by communicating with an SMS-SC over SGd/Gdd interfaces.
- the third subsection describes an example message procedure for communicating with an SMS-SC over SGd/Gdd interfaces.
- the fourth subsection describes an example UE in the form of a mobile device embodiment.
- the fifth subsection describes additional embodiments employing the techniques described herein.
- FIG. 1 shows details of a 3GPP network 10 having entities configured to manage delivery of SMs (e.g., MT- and MO-SMS messages, device triggers, or small data transfers) while NAS congestion controls are active.
- SMs e.g., MT- and MO-SMS messages, device triggers, or small data transfers
- an SCS/AS 16 creates an MT-SMS message and communicates it through a Tsp reference point 18 to an MTC interworking function (MTC-IWF) 20 .
- MTC-IWF 20 provides over a T4 reference point 26 information representing the MT-SMS message, including information concerning the message destination and its duration of validity.
- the SMS-SC 30 is generally responsible for the relaying, storing, and forwarding of SMs.
- the SMS-SC entity 30 may include an SMS router, and other SMS-related entities that are generally referred to herein as an SMS-SC entity.
- a gateway mobile-services switching center (MSC) for short message service (SMS-GMSC) corresponds to the functions of an MSC that are capable of receiving an SM, interrogating over an S6c/C interface 32 a home subscriber server (HSS) or home location register (HLR) 34 for routing information and SMS information.
- an interworking MSC for short message service corresponds to the functions of an MSC that are capable of receiving an SM from within a public land mobile network (PLMN) and submitting it to the recipient service center.
- PLMN public land mobile network
- the SMS-SC 30 provides the message to an appropriate interface.
- An SGd interface 44 for example, enables the transfer of SMs between an MME 46 and the SMS-SC 30 , as described in 3GPP TS 23.040.
- a Gdd interface 54 enables the transfer of SMs between an SGSN 56 and the SMS-SC 30 , as described in 3GPP TS 23.040.
- the MME 46 performs packet switching functions for mobile stations located in a geographical area designated as the MME area. Its interface with a radio access network (RAN) 62 is called an S1-MME interface 64 .
- RAN radio access network
- the SGSN 56 performs packet switching functions for mobile stations located in a geographical area designated as the SGSN area. Its interface with the RAN 62 is called an Iu interface 66 .
- a UE 70 sends and receives messages through an air interface 72 .
- UMTS universal mobile telecommunications system
- MS mobile station
- the MME 46 or SGSN 56 can communicate MO-SMS messages over, respectively, the SGd interface 44 and the Gdd interface 54 .
- device triggers can be communicated via the SGd interface 44 and the Gdd interface 54 .
- the various types of messages communicated over these interfaces e.g., MT-SMS messages, MO-SMS messages, device triggers, or small data transfers
- SMs are referred to herein as SMs.
- SMs may be received by the SMS-SC 30 over interfaces other than the Tsp interface 18 .
- FIG. 1 shows a Tsms interface 74 between a short message entity (SME) 76 and the SMS-SC 30 .
- the Tsms interface 74 is an interface that encompasses all the various proprietary SMS-SC-to-SME interface standards, as described in 3GPP technical report (TR) 23.039.
- TR 3GPP technical report
- the Tsms interface 74 can be used to send a trigger to the UE 70 , in which case the trigger is encapsulated in an MT-SMS message.
- This method of triggering provides over-the-top application access to the UE 70 by any network entity (e.g. an SCS) acting as an SME.
- any network entity e.g. an SCS
- FIG. 2 shows an example of a message flow diagram 80 in which the MME/SGSN 46 , 56 control their respective SM loads by providing (with the SGd/Gdd interface 44 , 54 ) messages delivered to the SMS-SC 30 .
- Initial messages and sequences 82 of the example diagram 80 are based on Tsp device triggering. Details of Tsp device triggering are described in 3GPP TS 23.682. Likewise, T4 device triggering 84 is also described in 3GPP TS 23.682.
- an MT-SMS message may include transfer protocol-protocol identification (TP-PID) information identifying an MT message as a device trigger intended for the UE 70 (i.e., an application on the UE 70 ). In other embodiments, an MT message is identified as MT-SMS message intended for a user of the UE 70 .
- TP-PID transfer protocol-protocol identification
- the SMS-SC 30 sends to the MME/SGSN 46 , 56 a diameter-based message called an MT forward short message request 86 , which is described in greater detail in the following subsection.
- Diagram 80 shows an overload situation 88 in which the MME/SGSN 46 , 56 recognizes that it cannot deliver a trigger due to MME/SGSN overload, for example, NAS level congestion 90 .
- the MME/SGSN 46 , 56 (or the HSS/HLR 34 , in other embodiments) may not be able to deliver an SM to the UE 70 .
- the overload situation 88 can happen when the UE 70 is sending or receiving too many NAS messages to the evolved packet system, the UE's SM memory capacity is exceeded, the MT-SMS is barred, or the MME/SGSN 46 , 56 is congested. Other factors such as MME/SGSN processing capability may also cause MME/SGSN congestion.
- MME NAS level congestion control is defined in 3GPP TS 23.401.
- SGSN NAS level congestion control is defined in 3GPP TS 23.060.
- the MME/SGSN 46 , 56 attempt to ensure that no UEs are triggered as long as the particular congestion situation (e.g., NAS level mobility management congestion control) remains. Accordingly, to reflect the amount of SM load that the MME/SGSN 46 , 56 wishes to reduce, the MME/SGSN 46 , 56 can send an MT forward short message answer 92 over the SGd/Gdd interface 44 , 54 .
- the particular congestion situation e.g., NAS level mobility management congestion control
- the answer 92 includes an information element (IE) indicating SGd/Gdd SM overload parameters, such as, for example: overload suppression value (e.g., the percentage of messages to reject or allow), suppression validity duration, overload report, suppression subcategories (e.g., a specific priority type), and/or other parameters.
- overload suppression value e.g., the percentage of messages to reject or allow
- suppression validity duration e.g., the percentage of messages to reject or allow
- overload report e.g., a specific priority type
- suppression subcategories e.g., a specific priority type
- suppression may be refereed as throttling, in which case overload parameters include, for example: throttling value, throttling validity duration, and/or throttling subcategories (e.g., a specific priority type).
- overload parameters include, for example: throttling value, throttling validity duration, and/or throttling subcategories (e.g., a specific priority type).
- the MME 46 when the MME 46 cannot deliver the SM to the UE 70 , the MME 46 returns a failure report to the SMS-SC 30 (e.g., the SMS GMSC/SMS router).
- a failure report may be sent as part of an extended MT forward short message answer.
- the MT forward short message answer 92 (described in the following subsection) can be extended to include a new congestion value for result-code attribute value pair (AVP).
- AVP result-code attribute value pair
- an SM delivery failure cause AVP inside the MT forward short message answer 92 can be extended to include a new value indicating the cause of the congestion.
- the MT forward short message answer 92 can include a back-off timer value AVP indicating for the SMS-SC 30 that the SMS-SC 30 should suppress SMs (e.g., MT-SMS or device trigger messages) until the duration of the back-off timer has lapsed.
- SMs e.g., MT-SMS or device trigger messages
- the MT forward short message answer 92 can include an overload supported feature AVP (e.g. granular or course control of overload) and an overload parameter AVP (e.g. back-off timer value, overload suppression value, overload report, overload validity duration, or other similar overload parameter AVPs).
- AVP overload supported feature
- AVP overload parameter AVP
- the MME/SGSN 46 , 56 can send new diameter message to the SMS-SC 30 indicating the congestion situation and back-off timer value.
- New messages may contain overload parameters (e.g. overload suppression value, overload report, overload validity duration, etc.).
- the SMS-GMSC/SMS router/HSS procedures for handling and responding 94 to the failure report are specified in TS 23.040. Additionally, if the SM failed due to the UE 70 not being reachable, the MME 46 sets the Mobile-Not-Reachable-Flag-in-MME-for-SMS (MNRF-MME) indication in the MME 46 .
- MNRF-MME Mobile-Not-Reachable-Flag-in-MME-for-SMS
- the MME 46 sends a Ready for SM (international mobile subscriber identity (IMSI), UE-Present) message to the HSS 34 and the MME 46 clears the corresponding MNRF-MME indication associated with the UE 70 .
- IMSI international mobile subscriber identity
- UE-Present a message that the MME 46 receives an indication from a serving gateway (S-GW) that the UE 70 has handover to non-3GPP coverage, it will not trigger this activity notification.
- S-GW serving gateway
- the MME 46 sends a Ready for SM (IMSI, UE-Memory-Available) message to the HSS 34 .
- IMSI UE-Memory-Available
- the MME/SGSN 46 , 56 If the MME/SGSN 46 , 56 is congested (e.g. general overload, or the MME/SGSN 46 , 56 is running a NAS level congestion back-off timer, etc.), then the MME/SGSN 46 , 56 returns a failure report using MT forward short message answer to SMS-SC/SMS GMSC/SMS router 30 indicating such congestion.
- the SMS-SC 30 upon receiving a failure report indicating congestion, may start a back-off timer and will not attempt sending SMs to the (serving) MME/SGSN 46 , 56 until the expiry of this timer.
- the SMS-SC 30 can conduct overload control in any of the following manners: (1) perform SM suppression as indicated in the SGd/Gdd overload parameters to stop submitting SMs to the congested network node; (2) report status 96 and/or return 98 the failure report with appropriate cause value to the SCS 16 (i.e., by way of MTC-IWF 20 ) for suppressing a trigger as indicated in the SGd/Gdd suppression parameters; or (3) determine if load control should be performed towards one or more MTC-IWFs.
- the MME/SGSN 46 , 56 provides support for communicating SMs to UEs for high priority SMs.
- the MME/SGSN 46 , 56 can also send a new or updated message over the SGd/Gdd 44 , 54 interface to the SMS-SC 30 .
- the new or updated message thereby indicates new overload parameters for modifying the SM suppression configuration, or resuming handling SMs from the SMS-SC 30 when the suppression duration is expired.
- the MME/SGSN 46 , 56 applies NAS level congestion control to a particular target UE—the UE 70 having a running back-off timer (or the MME/SGSN 46 , 56 is running a timer for the UE 70 )—the MME/SGSN 46 , 56 can decide whether to reject the trigger request in order to avoid MO mobility management (MM) or session management signaling from the (target) UE 70 to the network 10 .
- the MME/SGSN 46 , 56 may reject the trigger request to the UE 70 based on one or more of the following conditions: the priority of the trigger request, if the trigger request is used for device triggering, or if a back-off timer is applied to the (target) UE 70 .
- An appropriate reject cause indicates that the unsuccessful trigger request delivery is for the particular UE 70 (e.g., due to congestion or MM back-off timing).
- the MME/SGSN 46 , 56 may inform the SMS-SC 30 about a back-off timer for dropping the further trigger request to the UE 70 (similar or different value as the MM back-off timer running in the MME/SGSN 46 , 56 ).
- the SMS-SC 30 can compare the validity period and the back-off timer duration, if any, to conduct further handling for the triggering message.
- the SMS-SC 30 can attempt delivery of the triggering message to the target UE 70 at a later time occurring after the expiration of the back-off timer duration but before expiration of the validity period. Otherwise, the SMS-SC 30 can delete the triggering message either immediately or after the expiration of the validity period and report 98 the failure of the trigger delivery (e.g., indicates that the cause of the failure delivery is due to network congestion) to the MTC-IWF 20 over the T4 interface 26 .
- the MME/SGSN 46 , 56 can decide to store the trigger and re-attempt the delivery after the back-off timer expires. In this case, the MME/SGSN 46 , 56 will inform the SMS-SC 30 of the trigger delivery status.
- the MME/SGSN 46 , 56 may differentiate between a device trigger and MT-SMS for purposes of reacting to different congestion situations.
- a device trigger and a more general MT-SMS can be identified based on a TP-PID field in the transfer protocol data unit (TPDU) of SMS message.
- TP-PID is defined in 3GPP TS 23.040.
- the MME/SGSN 46 , 56 may read the TP-PID to determine if it identifies an SMS message or a device triggering short message or any other message.
- the MME/SGSN 46 , 56 may drop device triggers but allow MT-SMSs, or alternatively, it may drop MT-SMS and allow device triggers.
- the aforementioned overload control mechanism for SMs conveyed from the SMS-SC 30 to the MME/SGSN 46 , 56 is not limited to MT messages. In fact, the mechanism has a similar implementation for MO messages.
- the SMS-SC 30 may itself become aware of or it is otherwise informed of an overload at the SMS-SC 30 and thereby sends overload parameters (e.g., overload suppression value, overload report, overload validity duration, back-off timer, etc.) to the MME/SGSN 46 , 56 .
- overload parameters e.g., overload suppression value, overload report, overload validity duration, back-off timer, etc.
- the SMS-SC 30 if the SMS-SC 30 is overloaded, it can send an MO forward short message answer message to the MME/SGSN 46 , 56 .
- such an MO forward short message answer can be extended to include new congestion value for result-code AVP.
- An SM delivery failure cause AVP inside the MO forward short message answer can be extended to include new value indicating the cause of the congestion.
- the MO forward short message answer can include a back-off timer value AVP indicating to the MME/SGSN 46 , 56 to suppress SMs until the duration of back-off timer has lapsed.
- the MO forward short message answer can include an overload supported feature AVP (e.g. granular or course control of overload) and overload parameter AVP (e.g. back-off timer value, overload suppression value, overload report, overload validity duration, etc).
- overload supported feature AVP e.g. granular or course control of overload
- overload parameter AVP e.g. back-off timer value, overload suppression value, overload report, overload validity duration, etc.
- the SMS-SC 30 can send a new diameter message to the MME/SGSN 46 , 56 indicating a congestion situation and a back-off timer value.
- the new message may contain overload parameters (e.g. overload suppression value, overload report, overload validity duration, etc.).
- the SMS-SC 30 If the SMS-SC 30 is congested, then the SMS-SC 30 returns a failure report using MO forward short message answer to MME/SGSN 46 , 56 indicating such congestion.
- the MME/SGSN 46 , 56 upon receiving a failure report indicating congestion, may start a back-off timer and will not attempt sending SMs to the SMS-SC 30 until the expiry of this timer.
- the MME/SGSN 46 , 56 can conduct overload control in any of the following manners: (1) perform SM suppression as indicated in the SGd/Gdd overload parameters to stop submitting SMs to the congested network node; (2) report status (e.g., akin to status 96 , FIG. 2 ) and/or return the failure report (e.g., akin to report 98 , FIG. 2 ) with an appropriate cause value to the UE 70 .
- An example cause value may, for example, indicate the UE 70 should begin applying NAS based congestion control.
- the SMS-SC 30 provides support for communicating SMs to MME/SGSN 46 , 56 for high priority SMs.
- the SMS-SC 30 can also send a new or updated message over the SGd/Gdd 44 , 54 interface to the MME/SGSN 46 , 56 .
- the new or updated message thereby indicates new overload parameters for modifying the SM suppression configuration, or resuming handling SMs from the MME/SGSN 46 , 56 when the suppression duration is expired.
- This subsection provides an example of standardization of a MME/SGSN message procedure for responding to NAS level congestion.
- the message procedure is called an MT forward short message procedure.
- the procedure is typically used between the SMS-SC and the serving MME or SGSN (transiting though an SMS Router, if present) to forward mobile terminated short messages.
- This procedure is used according to the call flows described in 3GPP TS 23.040 section 10 , and the procedure includes an MT forward short message request and an MT forward short message answer.
- These messages are mapped to the commands MT-Forward-Short-Message-Request/Answer (TFR/TFA) in the Diameter-based message formats, including an IE and AVP information, specified in 3GPP TS 29.338.
- TFR/TFA MT-Forward-Short-Message-Request/Answer
- the following tables 1 and 2 specify the involved information elements for the MT forward short message request.
- SM RP DA User-Name* shall contain an (M) IMSI. *(See internet engineering task force (IETF) request for comments (RFC) 3588) SM RP OA SC-Address M This information element shall contain the Service Center address.
- SM RP UI SM-RP-UI M This information element shall contain the short message transfer protocol data unit.
- MME MME-Number- Conditional This information element contains the Number for for-MT-SMS (C) Integrated Services for Digital Network MT SMS (ISDN) number of the MME (see 3GPP TS 23.003) and shall be present when the request is sent to an MME.
- SGSN SGSN-Number C This information element contains the Number ISDN number of the SGSN (see 3GPP TS 23.003) and shall be present when the request is sent to an SGSN. TFR-Flags TFR-Flags C This information element shall contain a bit mask. Bit 0 indicates, when set, if the Service Center has more messages to send. SM Delivery SM-Delivery- Optional This information element, when present, Timer Timer (O) shall indicate the SM Delivery Timer value set in the SMS-GMSC to the IP-SM-GW.
- Start Time Time shall indicate the timestamp (in UTC) at which the SM Delivery Supervision Timer was started in the SMS-GMSC.
- Overload Overload- O If present, this information element shall Supported Supported- contain the list of supported overload Features Feature features.
- Overload Overload- O If present, this information element shall Parameters Parameters contain the list overload parameters (e.g., overload suppression value, a back-off timer, or other parameters) Supported Supported- O If present, this information element shall Features Features* contain the list of features supported by the origin host. *(See 3GPP TS 29.229)
- the following table 2 defines a diameter-based message, which is extends table 1 for 3GPP TS 29.338, and which is formatted according to a command code format (CCF) definition for the diameter base protocol of IETF RFC 3588.
- CCF command code format
- the following table 2 is similar to table 1, but includes example definitions expressed in an Augmented Backus-Naur Form (ABNF) metalanguage syntax.
- Result Result-Code/ M This information element shall contain the result Experimental- of the operation. Result The Result-Code AVP shall be used to indicate success/errors as defined in the Diameter Base Protocol. The Experimental-Result AVP shall be used for SGd/Gdd errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor- Id AVP, and the error code in the Experimental- Result-Code AVP.
- this information element shall contain Supported Supported- the list of supported overload features.
- Features Feature Overload Overload- O If present, this information element shall contain Parameters Parameters the desired overload controls (e.g., overload suppression value, a back-off timer, or other parameters) Supported Supported- O If present, this information element shall contain Features Features* the list of features supported by the origin host. *(See 3GPP TS 29.229)
- the “Supported-Features” AVP in the forgoing tables can be used in addition to or as an alternative to the discrete “Overload-Supported-Feature” or “Overload-Parameters” AVPs.
- the forgoing tables have similar counterparts for MO forward short message procedures that may be used when an SMS-SC is overloaded. For example, if the SMS-SC 30 ( FIG. 1 ) is overloaded upon receipt of an MO forward short message request message from the MME 46 , then the SMS-SC 30 may respond with an MO forward short message answer message that includes “Overload-Supported-Feature,” “Overload-Parameters,” or similar AVPs.
- the MME and the SGSN behave as follows when receiving an MT Forward Short Message Request.
- the MME or the SGSN check if the IMSI is known.
- the MME or the SGSN attempts to deliver the short message to the UE.
- the MME or the SGSN returns a Result-Code set to DIAMETER_SUCCESS.
- the MME sets the MNRF flag and returns an Experimental-Result-Code set to DIAMETER_ERROR_ABSENT_USER.
- the SGSN sets the MNRG flag and returns an Experimental-Result-Code set to DIAMETER_ERROR_ABSENT_USER.
- the MME or the SGSN returns an Experimental-Result-Code set to DIAMETER_ERROR_SM_DELIVERY_FAILURE complemented with an SM Delivery Failure Cause indication.
- the MME or the SGSN If a requested facility is not supported, then the MME or the SGSN returns an Experimental-Result-Code set to DIAMETER_ERROR_FACILITY_NOT_SUPPORTED.
- the mobile terminated short message transfer cannot be completed because: another mobile terminated short message transfer is going on and the delivery node does not support message buffering, another mobile terminated short message transfer is going on and it is not possible to buffer the message for later delivery, or the message was buffered but it is not possible to deliver the message before the expiry of the buffering time defined in 3GPP TS 23.040; then the MME or the SGSN returns an Experimental-Result-Code set to DIAMETER_ERROR_USER_BUSY_FOR_MT_SMS.
- the MME or the SGSN returns an Experimental-Result-Code set to DIAMETER_ERROR_ILLEGAL_USER.
- the MME or the SGSN returns an Experimental-Result-Code set to DIAMETER_ERROR_ILLEGAL_EQUIPMENT.
- the MME or the SGSN If the delivery of the mobile terminated short message failed because of NAS level congestion, then the MME or the SGSN returns an Experimental-Result-Code set to DIAMETER_ERROR_MME_CONGESTION or DIAMETER_ERROR_SGSN_CONGESTION. MME or SGSN may also send back-off timer.
- DIAMETER_ERROR_SN_CONGESTION may also be defined where SN indicates “Serving Node.”
- the SMS-GMSC behaves as follows.
- the SMS-GMSC makes use of this procedure over the SGd interface or over the Gdd interface for the delivery of an MT short message when it has selected the serving node of which it obtained the Diameter Identity from the answer of the Send Routing Info for SM procedure.
- SMS-GMSC is not aware that the MT Forward Short Message Request may be routed to an SMS router.
- SMS-GMSC may start the timer. For an MT SM (or device triggering message) with validity period, the SMS-GMSC can compare the validity period and the back-off timer duration, if any, to conduct further handling for the triggering message. If the validity period is larger than the back-off timer duration, the SMS-GMSC can attempt delivery of the triggering message to the target UE at a later time after the expiration of the back-off timer duration. Otherwise, the SMS-GMSC can delete the triggering message after the expiration of the validity period and report the failure of the trigger delivery (e.g., indicates that the cause of the failure delivery is due to network congestion) to the MTC-IWF.
- the SMS-GMSC can delete the triggering message after the expiration of the validity period and report the failure of the trigger delivery (e.g., indicates that the cause of the failure delivery is due to network congestion) to the MTC-IWF.
- FIG. 3 provides an example illustration of a mobile device, commonly deployed as a UE, and referred to as a mobile station (MS), a mobile wireless device, a mobile communication device, a tablet, a handset, or other type of mobile wireless device.
- the mobile device can include one or more antennas configured to communicate with a transmission station, such as a base station (BS), an eNB, a base band unit (BBU), a remote radio head (RRH), a remote radio equipment (RRE), a relay station (RS), a radio equipment (RE), or other type of wireless wide area network (WWAN) access point.
- the mobile device can be configured to communicate using at least one wireless communication standard including 3GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and WiFi.
- the mobile device can communicate using separate antennas for each wireless communication standard or shared antennas for multiple wireless communication standards.
- the mobile device can communicate in a wireless local area network (WLAN), a wireless personal area network (WPAN), and/or
- FIG. 3 also provides an illustration of a microphone and one or more speakers that can be used for audio input and output from the mobile device.
- the display screen may be a liquid crystal display (LCD) screen, or other type of display screen such as an organic light emitting diode (OLED) display.
- the display screen can be configured as a touch screen.
- the touch screen may use capacitive, resistive, or another type of touch screen technology.
- An application processor and a graphics processor can be coupled to internal memory to provide processing and display capabilities.
- a non-volatile memory port can also be used to provide data input/output options to a user.
- the non-volatile memory port may also be used to expand the memory capabilities of the mobile device.
- a keyboard may be integrated with the mobile device or wirelessly connected to the mobile device to provide additional user input.
- a virtual keyboard may also be provided using the touch screen.
- Examples may include subject matter such as a method, means for performing acts of the method, at least one machine-readable medium including instructions that, when performed by a machine cause the machine to performs acts of the method, or of an apparatus or system for SM load control according to embodiments and examples described herein.
- the following examples are enumerated for added clarity.
- An network entity for use in a 3rd generation partnership project (3GPP) network comprising circuitry configured to: receive from a short message service-service center (SMS-SC) entity a mobile terminated (MT) forward short message request; determine whether the network entity is overloaded such that the network entity is unable to deliver a short message (SM) to a user equipment (UE); and send to the SMS-SC an MT forward short message answer having information indicating that the network entity is overloaded, in which the MT forward short message answer causes the SMS-SC to temporarily suppress sending further SMs, and in which the network entity comprises at least one of a mobility management entity (MME) or a serving general packet radio service support node (SGSN).
- MME mobility management entity
- SGSN serving general packet radio service support node
- the network entity of example 1 in which in response to a non-access stratum (NAS) level congestion control in place for the UE, the network entity is configured to reject a trigger request so as to avoid mobile originated (MO) mobility management (MM) or session management signaling from the UE to the network.
- NAS non-access stratum
- a short message service-service center (SMS-SC) device comprising circuitry configured to: transmit to a network node a short message (SM) by using an interface between the SMS-SC device and the network node, in which the interface is an SGd interface when the network node comprises a mobility management entity (MME), and in which the interface is a Gdd interface when the network node comprises a serving general packet radio service support node (SGSN); receive through the interface a message response indicating that network node is unable to deliver the SM to a target mobile station, the message response including a parameter for suppressing transmission of a subsequent SM to the network node while the network node is unable to deliver the subsequent SM; and determine whether to transmit the subsequent SM to the network node based on the message response.
- SM short message
- MME mobility management entity
- SGSN serving general packet radio service support node
- the SMS-SC device of example 9 in which the SM is a triggering message having a validity period, and the circuitry is further configured to: delete the triggering message after expiration of the validity period; and report a failure of trigger delivery.
- MT-SMS mobile terminated short message service
- TP-PID transfer protocol-protocol identifier
- a method for controlling an amount of mobile terminated (MT) short message service (SMS) (MT-SMS) messages to be delivered to a mobility management entity (MME) or a serving general packet radio service support node (SGSN) in a 3rd generation partnership project network comprising: detecting at the MME/SGSN a congestion event; and transmitting over an SGd/Gdd interface, in response to detecting the congestion event, a diameter-based message including an information element having an attribute value pair indicating that the MME/SGSN is temporarily unable to deliver an MT-SMS message.
- MME mobility management entity
- SGSN serving general packet radio service support node
- the MT-SMS messages comprise device triggering messages over a T4 interface.
- the method of example 16 further comprising: determining a suppression duration in which the MME/SGSN is temporarily unable to deliver an MT-SMS message; and including information in the diameter-based message that indicates the suppression duration.
- the method of example 16 further comprising: determining that the congestion event has subsided; and transmitting over an SGd/Gdd interface, a message indicating the congestion event has subsided.
- the congestion event comprises a non-access stratum (NAS) level congestion control event.
- NAS non-access stratum
- a network node comprising circuitry configured to: transmit to a short message service-service center (SMS-SC) device a mobile originated (MO) short message (SM) by using an interface between the network node and the SMS-SC device, in which the interface is an SGd interface when the network node comprises a mobility management entity (MME), and in which the interface is a Gdd interface when the network node comprises a serving general packet radio service support node (SGSN); receive through the interface a message response indicating that the SMS-SC device is unable to deliver the MO SM to a target destination, the message response including a parameter for suppressing transmission of a subsequent MO SM from the network node while the SMS-SC device is unable to deliver the subsequent MO SM; and determine whether to transmit the subsequent MO SM to the SMS-SC device based on the message response.
- SMS-SC short message service-service center
- MO mobile originated
- a method performed by a network entity for use in a 3rd generation partnership project (3GPP) network comprising: receiving from a short message service-service center (SMS-SC) entity a mobile terminated (MT) forward short message request; determining whether the network entity is overloaded such that the network entity is unable to deliver a short message (SM) to a user equipment (UE); and sending to the SMS-SC an MT forward short message answer having information indicating that the network entity is overloaded, in which the MT forward short message answer causes the SMS-SC to temporarily suppress sending further SMs, and in which the network entity comprises at least one of a mobility management entity (MME) or a serving general packet radio service support node (SGSN).
- MME mobility management entity
- SGSN serving general packet radio service support node
- the information includes a suppression parameter that configures the SMS-SC to delay sending further SMs for a predetermined time.
- example 25 further comprising sending a second message having updated suppression parameters for ceasing trigger suppression in response to the network entity recovering from being overloaded.
- the method of example 25, further comprising sending a second message indicating updated suppression parameters for decreasing an amount of trigger suppression in response to the network entity recovering from being overloaded.
- the network entity in response to a non-access stratum (NAS) level congestion control in place for the UE, the network entity is configured to reject a trigger request so as to avoid mobile originated (MO) mobility management (MM) or session management signaling from the UE to the network.
- NAS non-access stratum
- a method performed by a short message service-service center (SMS-SC) device comprising: transmitting to a network node a short message (SM) by using an interface between the SMS-SC device and the network node, in which the interface is an SGd interface when the network node comprises a mobility management entity (MME), and in which the interface is a Gdd interface when the network node comprises a serving general packet radio service support node (SGSN); receiving through the interface a message response indicating that network node is unable to deliver the SM to a target mobile station, the message response including a parameter for suppressing transmission of a subsequent SM to the network node while the network node is unable to deliver the subsequent SM; and determining whether to transmit the subsequent SM to the network node based on the message response.
- SMS-SC short message service-service center
- the parameter includes a back-off timer indicating a suppression period for suppressing transmission of the subsequent SM to the network node during the suppression period.
- the method of example 33 further comprising: determining whether the subsequent SM is a high priority SM; transmitting the subsequent SM when it is a high priority SM; and suppressing transmission of the subsequent SM when it is not a high priority SM.
- the SM is a triggering message having a validity period
- the method further comprising: deleting the triggering message after expiration of the validity period; and reporting a failure of trigger delivery.
- the method of example 33 further comprising: determining whether the SM is a device trigger or a mobile terminated short message service (MT-SMS) message by reading a transfer protocol-protocol identifier (TP-PID) field of the SM; and allowing delivery of the SM based on whether it is determined to be a device trigger or an MT-SMS message.
- MT-SMS mobile terminated short message service
- TP-PID transfer protocol-protocol identifier
- the method of example 33 further comprising: determining whether the network node is congested based on an operator policy or configuration; and allowing delivery of the SM based on whether it is determined to be a device trigger or a mobile terminated short message service message.
- a computer-readable medium for controlling an amount of short message (SM) load communicated in a 3rd generation partnership project network the computer-readable medium having stored thereon computer-executable instructions executable by a network entity to cause the network entity to: detect a congestion event at the network entity; and transmit over an SGd/Gdd interface, in response to detecting the congestion event, a diameter-based message including an information element having an attribute value pair indicating that the network entity is temporarily unable to deliver a SM message.
- SM short message
- the computer-readable medium of example 40 in which the instructions cause the network entity to: determine a suppression duration in which the network entity is temporarily unable to deliver an SM; and include information in the diameter-based message that indicates the suppression duration.
- the computer-readable medium of example 40 in which the instructions cause the network entity to: determine that the congestion event has subsided; and transmit over an SGd/Gdd interface, a message indicating the congestion event has subsided.
- the computer-readable medium of example 40 in which the congestion event comprises a non-access stratum (NAS) level congestion control event.
- NAS non-access stratum
- SM load includes mobile terminated (MT) short message service (SMS) messages.
- MT mobile terminated
- SMS short message service
- SM load includes mobile ordinated (MO) short message service (SMS) messages.
- MO mobile ordinated
- SMS short message service
- MME mobility management entity
- SGSN serving general packet radio service support node
- SMS-SC short message service-service center
- At least one computer readable storage medium having instructions stored thereon, that when executed on a device perform the method of any of examples 16 through 20, and 25 through 39.
- ASICs application-specific integrated circuits
- PLDs programmable logic devices
- FPGAs field-programmable gate arrays
- Embodiments may be implemented in one or a combination of hardware, firmware, and software. Embodiments may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein.
- a computer-readable storage device may include any non-transitory mechanism for storing information in a form readable by a machine (e.g., a computer).
- a computer-readable storage device may include read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media.
- one or more processors may be configured with instructions stored on a computer-readable storage device.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Radar, Positioning & Navigation (AREA)
- Remote Sensing (AREA)
- Mobile Radio Communication Systems (AREA)
- Position Fixing By Use Of Radio Waves (AREA)
Abstract
A mobility management entity or serving general packet radio service support node controls short message loads by communicating diameter-based messages over, respectively, SGd and Gdd interfaces with associated short message service-service center entities.
Description
- This application claims priority benefit of U.S. provisional patent application No. 61/879,014, filed Sep. 17, 2013 (attorney docket no. P61026Z), which is hereby incorporated herein by reference in its entirety.
- The present disclosure generally relates to management of short message (SM) loads and, more particularly, to management of mobile originated (MO) short message service (SMS) messages, mobile terminated (MT) SMS messages, and other types of SMs including small data transfer and device triggering via a mobility management entity (MME) or serving general packet radio service (GPRS) support node (SGSN).
- 3GPP network systems provide for transport, subscriber management, and other communication services including various architectural enhancements motivated by, but not restricted to, MTC. For example, one such service is control plane device triggering—so-called device triggering, or simply, triggering. Device triggering is a technique to send information (e.g., a device trigger, or simply, trigger) to a user equipment device (or simply, UE) to cause it to perform application specific actions including initiating communications with a services capability server (SCS) (in an indirect communication model system) or an application server (AS) (in a direct communication model system). For example, device triggering is frequently employed when a network address for a UE is not available or reachable by the SCS/AS. In such a case, a device trigger message may be used to establish communications because the trigger includes information that facilitates routing of messages in a 3GPP network to an appropriate UE application, and facilitates that UE application to route messages to an appropriate SCS/AS application.
- There are several types of device triggering schemes. T4 device triggering uses MT-SMS messages for delivering a device trigger to a UE, as defined in 3GPP TS 23.682 for release no. 11 (Rel-11) of the 3GPP standardization. In general, however, a device trigger may include other information, such as user data, conveyed by means of the SMS protocol.
- Rel-11 also includes a feature in which SMs can be delivered to UE via an enhanced MME. Accordingly, the enhanced MME is the network entity that supports the so-called SMS in MME feature.
- Too many UEs simultaneous sending or receiving device triggers or other SMs, including MT- and MO-SMS messages, can sometimes cause congestion (generally referred to as an overload situation) to the network, and thereby compromise the 3GPP network performance. In release no. 10 (Rel-10) of the 3GPP standardization, a congestion control mechanism for networks was extended to include non-access stratum (NAS) level congestion control, which includes two types of control: access point name (APN) based congestion control, and general NAS level mobility management congestion control.
- APN based congestion control is applicable to UEs that are members of a particular APN. Thus, for a particular APN, the network can provide a maximum limit of the number of connections (bearers) or the number of network accesses to the network.
- General NAS level mobility management congestion control is applicable when numerous UEs initiate nearly simultaneous network access attempts, which cause congestion in the serving core network (CN) node, e.g., an MME or serving general packet radio service (GPRS) support node (SGSN).
- The 3GPP standardization currently does not provide for an MME/SGSN that assesses NAS level congestion controls to determine whether and when to deliver (or reject) SMs.
-
FIG. 1 is a block diagram of network entities forming a portion of a 3GPP system, according to one embodiment. -
FIG. 2 is a message sequence chart showing an MME or SGSN controlling delivery of MT-SMSs or SM device triggers during an overload situation, according to one embodiment. -
FIG. 3 is a block diagram of a UE, according to one embodiment. - This portion of the disclosure describes MMEs and SGSNs capable of controlling device trigger loads by communicating diameter-based messages over, respectively, SGd and Gdd interfaces (also called reference points) with associated SMS entities. Before continuing with the description, however, the following two paragraphs clarify the meaning of some shorthand notations used for purposes of conciseness in this disclosure. These two paragraphs are then followed by a third paragraph providing a brief overview of five subsections that impart a description of the drawing figures and embodiments.
- First, skilled persons will recognize that both MME and SGSN functionality can be implemented on either a single hardware device or as separate network entities (i.e., separate devices). For conciseness, therefore, an MME and SGSN are referred to generally as an MME/SGSN, by which the “/” connotes an inclusive disjunction meaning an MME, an SGSN, or a combination of both an MME and an SGSN. Likewise, the “/” notation is used for other network entities, interfaces, and functions that are similar to each other and can therefore be embodied as one or multiple devices. The SCS/AS mentioned in the background information of this disclosure is one such example.
- Second, network entities that provide SMS by relaying, storing, and forwarding SMs are generally referred to herein as a short message service-service center (SMS-SC) entity. This is so because the various entities comprising an SMS-SC—entities that are described in the following subsection—may employ similar interfaces, functions, or hardware platforms. Thus, rather than refer to multiple SMS-SC entities with the aforementioned “I” notation, it is more concise to sometimes refer to them as an SMS-SC entity, or simply an SMS-SC.
- Third, the following detailed description is organized into five subsections. The first subsection describes an example of 3GPP network components that are pertinent to congestion control over SGd/Gdd interfaces. The second subsection describes examples of MME/SGSN control of MT-SMS loads by communicating with an SMS-SC over SGd/Gdd interfaces. The third subsection describes an example message procedure for communicating with an SMS-SC over SGd/Gdd interfaces. The fourth subsection describes an example UE in the form of a mobile device embodiment. The fifth subsection describes additional embodiments employing the techniques described herein.
-
FIG. 1 shows details of a3GPP network 10 having entities configured to manage delivery of SMs (e.g., MT- and MO-SMS messages, device triggers, or small data transfers) while NAS congestion controls are active. For example, an SCS/AS 16 creates an MT-SMS message and communicates it through aTsp reference point 18 to an MTC interworking function (MTC-IWF) 20. The MTC-IWF 20 provides over aT4 reference point 26 information representing the MT-SMS message, including information concerning the message destination and its duration of validity. - The message then arrives at an SMS-
SC entity 30. The SMS-SC 30 is generally responsible for the relaying, storing, and forwarding of SMs. As noted previously, the SMS-SC entity 30 may include an SMS router, and other SMS-related entities that are generally referred to herein as an SMS-SC entity. For example, a gateway mobile-services switching center (MSC) for short message service (SMS-GMSC) corresponds to the functions of an MSC that are capable of receiving an SM, interrogating over an S6c/C interface 32 a home subscriber server (HSS) or home location register (HLR) 34 for routing information and SMS information. Similarly, an interworking MSC for short message service (SMS-IWMSC) corresponds to the functions of an MSC that are capable of receiving an SM from within a public land mobile network (PLMN) and submitting it to the recipient service center. - The SMS-
SC 30 provides the message to an appropriate interface. AnSGd interface 44, for example, enables the transfer of SMs between anMME 46 and the SMS-SC 30, as described in 3GPP TS 23.040. Likewise, aGdd interface 54 enables the transfer of SMs between anSGSN 56 and the SMS-SC 30, as described in 3GPP TS 23.040. - The MME 46 performs packet switching functions for mobile stations located in a geographical area designated as the MME area. Its interface with a radio access network (RAN) 62 is called an S1-
MME interface 64. - The SGSN 56 performs packet switching functions for mobile stations located in a geographical area designated as the SGSN area. Its interface with the RAN 62 is called an
Iu interface 66. - Lastly, a UE 70 sends and receives messages through an
air interface 72. The term UE in universal mobile telecommunications system (UMTS) terminology defined in 3GPP TR 21.905 is synonymous with the term mobile station (MS) that is used in this document and is defined in 3GPP TS 23.040. - In another embodiment, the
MME 46 or SGSN 56 can communicate MO-SMS messages over, respectively, theSGd interface 44 and theGdd interface 54. Also, device triggers can be communicated via theSGd interface 44 and theGdd interface 54. Accordingly, the various types of messages communicated over these interfaces (e.g., MT-SMS messages, MO-SMS messages, device triggers, or small data transfers) are referred to herein as SMs. - In some embodiments, SMs may be received by the SMS-
SC 30 over interfaces other than theTsp interface 18. For example,FIG. 1 shows aTsms interface 74 between a short message entity (SME) 76 and the SMS-SC 30. TheTsms interface 74 is an interface that encompasses all the various proprietary SMS-SC-to-SME interface standards, as described in 3GPP technical report (TR) 23.039. TheTsms interface 74 can be used to send a trigger to theUE 70, in which case the trigger is encapsulated in an MT-SMS message. This method of triggering provides over-the-top application access to theUE 70 by any network entity (e.g. an SCS) acting as an SME. -
FIG. 2 shows an example of a message flow diagram 80 in which the MME/SGSN Gdd interface 44,54) messages delivered to the SMS-SC 30. - Initial messages and
sequences 82 of the example diagram 80 are based on Tsp device triggering. Details of Tsp device triggering are described in 3GPP TS 23.682. Likewise, T4 device triggering 84 is also described in 3GPP TS 23.682. In some embodiments, an MT-SMS message may include transfer protocol-protocol identification (TP-PID) information identifying an MT message as a device trigger intended for the UE 70 (i.e., an application on the UE 70). In other embodiments, an MT message is identified as MT-SMS message intended for a user of theUE 70. - After the initial device trigger setup, the SMS-
SC 30 sends to the MME/SGSN 46,56 a diameter-based message called an MT forwardshort message request 86, which is described in greater detail in the following subsection. - Diagram 80 shows an
overload situation 88 in which the MME/SGSN NAS level congestion 90. Thus, the MME/SGSN 46,56 (or the HSS/HLR 34, in other embodiments) may not be able to deliver an SM to theUE 70. Theoverload situation 88 can happen when theUE 70 is sending or receiving too many NAS messages to the evolved packet system, the UE's SM memory capacity is exceeded, the MT-SMS is barred, or the MME/SGSN - To reduce the likelihood of an occurrence of
network congestion 80 being exacerbated by UEs that respond to triggers, the MME/SGSN SGSN SGSN short message answer 92 over the SGd/Gdd interface answer 92, as described in the following subsection, includes an information element (IE) indicating SGd/Gdd SM overload parameters, such as, for example: overload suppression value (e.g., the percentage of messages to reject or allow), suppression validity duration, overload report, suppression subcategories (e.g., a specific priority type), and/or other parameters. - In certain embodiments, suppression may be refereed as throttling, in which case overload parameters include, for example: throttling value, throttling validity duration, and/or throttling subcategories (e.g., a specific priority type).
- According to one embodiment, when the
MME 46 cannot deliver the SM to theUE 70, theMME 46 returns a failure report to the SMS-SC 30 (e.g., the SMS GMSC/SMS router). A failure report may be sent as part of an extended MT forward short message answer. For example, in some embodiments, the MT forward short message answer 92 (described in the following subsection) can be extended to include a new congestion value for result-code attribute value pair (AVP). Also, an SM delivery failure cause AVP inside the MT forwardshort message answer 92 can be extended to include a new value indicating the cause of the congestion. - In some embodiments, the MT forward
short message answer 92 can include a back-off timer value AVP indicating for the SMS-SC 30 that the SMS-SC 30 should suppress SMs (e.g., MT-SMS or device trigger messages) until the duration of the back-off timer has lapsed. - In some embodiments, the MT forward
short message answer 92 can include an overload supported feature AVP (e.g. granular or course control of overload) and an overload parameter AVP (e.g. back-off timer value, overload suppression value, overload report, overload validity duration, or other similar overload parameter AVPs). - In some embodiments, the MME/
SGSN SC 30 indicating the congestion situation and back-off timer value. New messages may contain overload parameters (e.g. overload suppression value, overload report, overload validity duration, etc.). - The SMS-GMSC/SMS router/HSS procedures for handling and responding 94 to the failure report are specified in TS 23.040. Additionally, if the SM failed due to the
UE 70 not being reachable, theMME 46 sets the Mobile-Not-Reachable-Flag-in-MME-for-SMS (MNRF-MME) indication in theMME 46. - If the
UE 70 subsequently becomes reachable and MNRF-MME indication is set, then theMME 46 sends a Ready for SM (international mobile subscriber identity (IMSI), UE-Present) message to theHSS 34 and theMME 46 clears the corresponding MNRF-MME indication associated with theUE 70. Notably, in the case that theMME 46 receives an indication from a serving gateway (S-GW) that theUE 70 has handover to non-3GPP coverage, it will not trigger this activity notification. - If the
UE 70 subsequently notifies theMME 46 that SMS memory is available, then theMME 46 sends a Ready for SM (IMSI, UE-Memory-Available) message to theHSS 34. - Reception of a Ready for SM message or an Update Location Request message by the
HSS 34 when MNRF is set will trigger the SMS alert procedure as defined in 3GPP TS 23.040. - If the MME/
SGSN SGSN SGSN SMS router 30 indicating such congestion. The SMS-SC 30, upon receiving a failure report indicating congestion, may start a back-off timer and will not attempt sending SMs to the (serving) MME/SGSN SGSN SC 30 can conduct overload control in any of the following manners: (1) perform SM suppression as indicated in the SGd/Gdd overload parameters to stop submitting SMs to the congested network node; (2) report status 96 and/or return 98 the failure report with appropriate cause value to the SCS 16 (i.e., by way of MTC-IWF 20) for suppressing a trigger as indicated in the SGd/Gdd suppression parameters; or (3) determine if load control should be performed towards one or more MTC-IWFs. - In some embodiments, during an overload situation, the MME/
SGSN - When the MME/
SGSN SGSN Gdd SC 30. The new or updated message thereby indicates new overload parameters for modifying the SM suppression configuration, or resuming handling SMs from the SMS-SC 30 when the suppression duration is expired. - If the MME/
SGSN UE 70 having a running back-off timer (or the MME/SGSN SGSN UE 70 to thenetwork 10. The MME/SGSN UE 70 based on one or more of the following conditions: the priority of the trigger request, if the trigger request is used for device triggering, or if a back-off timer is applied to the (target)UE 70. - An appropriate reject cause indicates that the unsuccessful trigger request delivery is for the particular UE 70 (e.g., due to congestion or MM back-off timing). Additionally, the MME/
SGSN SC 30 about a back-off timer for dropping the further trigger request to the UE 70 (similar or different value as the MM back-off timer running in the MME/SGSN 46,56). For an SM having a validity period, the SMS-SC 30 can compare the validity period and the back-off timer duration, if any, to conduct further handling for the triggering message. If the duration of the validity period is longer than that of the back-off timer, the SMS-SC 30 can attempt delivery of the triggering message to thetarget UE 70 at a later time occurring after the expiration of the back-off timer duration but before expiration of the validity period. Otherwise, the SMS-SC 30 can delete the triggering message either immediately or after the expiration of the validity period and report 98 the failure of the trigger delivery (e.g., indicates that the cause of the failure delivery is due to network congestion) to the MTC-IWF 20 over theT4 interface 26. - In another embodiment, if the MME/
SGSN particular target UE 70, then the MME/SGSN SGSN SC 30 of the trigger delivery status. - Although the aforementioned embodiments apply to both device triggering and MT-SMS, in some situations the MME/
SGSN SGSN SGSN SGSN - The aforementioned overload control mechanism for SMs conveyed from the SMS-
SC 30 to the MME/SGSN SC 30 may itself become aware of or it is otherwise informed of an overload at the SMS-SC 30 and thereby sends overload parameters (e.g., overload suppression value, overload report, overload validity duration, back-off timer, etc.) to the MME/SGSN SC 30 is overloaded, it can send an MO forward short message answer message to the MME/SGSN - In some embodiment, the MO forward short message answer can include a back-off timer value AVP indicating to the MME/
SGSN - In some embodiments, the MO forward short message answer can include an overload supported feature AVP (e.g. granular or course control of overload) and overload parameter AVP (e.g. back-off timer value, overload suppression value, overload report, overload validity duration, etc).
- In some embodiments, the SMS-
SC 30 can send a new diameter message to the MME/SGSN - If the SMS-
SC 30 is congested, then the SMS-SC 30 returns a failure report using MO forward short message answer to MME/SGSN SGSN SC 30 until the expiry of this timer. In general, however, when receiving SGd/Gdd overload parameters from the SMS-SC 30, the MME/SGSN FIG. 2 ) and/or return the failure report (e.g., akin to report 98,FIG. 2 ) with an appropriate cause value to theUE 70. An example cause value may, for example, indicate theUE 70 should begin applying NAS based congestion control. - In some embodiments, during an overload situation, the SMS-
SC 30 provides support for communicating SMs to MME/SGSN - When the SMS-
SC 30 is recovering from overload situation or network congestion, the SMS-SC 30 can also send a new or updated message over the SGd/Gdd SGSN SGSN - This subsection provides an example of standardization of a MME/SGSN message procedure for responding to NAS level congestion. The message procedure is called an MT forward short message procedure. The procedure is typically used between the SMS-SC and the serving MME or SGSN (transiting though an SMS Router, if present) to forward mobile terminated short messages. This procedure is used according to the call flows described in 3GPP TS 23.040
section 10, and the procedure includes an MT forward short message request and an MT forward short message answer. These messages are mapped to the commands MT-Forward-Short-Message-Request/Answer (TFR/TFA) in the Diameter-based message formats, including an IE and AVP information, specified in 3GPP TS 29.338. - The following tables 1 and 2 specify the involved information elements for the MT forward short message request.
-
TABLE 1 MT Forward Short Message Request Mapping to IE name Diameter AVP Cat. Description SM RP DA User-Name* Mandatory This information element shall contain an (M) IMSI. *(See internet engineering task force (IETF) request for comments (RFC) 3588) SM RP OA SC-Address M This information element shall contain the Service Center address. SM RP UI SM-RP-UI M This information element shall contain the short message transfer protocol data unit. MME MME-Number- Conditional This information element contains the Number for for-MT-SMS (C) Integrated Services for Digital Network MT SMS (ISDN) number of the MME (see 3GPP TS 23.003) and shall be present when the request is sent to an MME. SGSN SGSN-Number C This information element contains the Number ISDN number of the SGSN (see 3GPP TS 23.003) and shall be present when the request is sent to an SGSN. TFR-Flags TFR-Flags C This information element shall contain a bit mask. Bit 0 indicates, when set, if the Service Center has more messages to send. SM Delivery SM-Delivery- Optional This information element, when present, Timer Timer (O) shall indicate the SM Delivery Timer value set in the SMS-GMSC to the IP-SM-GW. SM Delivery SM-Delivery-Start- O This information element, when present, Start Time Time shall indicate the timestamp (in UTC) at which the SM Delivery Supervision Timer was started in the SMS-GMSC. Overload Overload- O If present, this information element shall Supported Supported- contain the list of supported overload Features Feature features. Overload Overload- O If present, this information element shall Parameters Parameters contain the list overload parameters (e.g., overload suppression value, a back-off timer, or other parameters) Supported Supported- O If present, this information element shall Features Features* contain the list of features supported by the origin host. *(See 3GPP TS 29.229) - The following table 2 defines a diameter-based message, which is extends table 1 for 3GPP TS 29.338, and which is formatted according to a command code format (CCF) definition for the diameter base protocol of IETF RFC 3588. Thus, the following table 2 is similar to table 1, but includes example definitions expressed in an Augmented Backus-Naur Form (ABNF) metalanguage syntax.
-
TABLE 2 Diameter-Based MT Forward Short Message Request Command AVP Fields Command < header >, < fixed >, { required }, Definition and [ optional ] Notes < MT-Forward- < Diameter Header: 8388646, REQ, numeric code Short-Message- PXY, 16777313 > identifying the Request > ::= < Session-Id > message [ Vendor-Specific-Application-Id ] { Auth-Session-State } { Origin-Host } { Origin-Realm } { Destination-Host } { Destination-Realm } { User-Name } [ SMSMI-Correlation-ID ] { SC-Address } { SM-RP-UI } [ MME-Number-for-MT-SMS ] [ SGSN-Number ] [ TFR-Flags ] [ SM-Delivery-Timer ] [ SM-Delivery-Start-Time ] [Overload-Supported-Feature] Indicate overload [Overload-Parameters] control capability at network node (e.g., MME/SGSN) *[ Supported-Features ] *denotes elements *[ AVP ] that may have *[ Proxy-Info ] duplicate instances *[ Route-Record ] - The following tables 3 and 4 specify the involved information elements for MT forward short message the answer.
-
TABLE 3 MT Forward Short Message Answer Mapping to IE name Diameter AVP Cat. Description Result Result-Code/ M This information element shall contain the result Experimental- of the operation. Result The Result-Code AVP shall be used to indicate success/errors as defined in the Diameter Base Protocol. The Experimental-Result AVP shall be used for SGd/Gdd errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor- Id AVP, and the error code in the Experimental- Result-Code AVP. The following errors are applicable: Unknown User; Absent User; User busy for MT SMS; Illegal User; Illegal Equipment; SM Delivery Failure; Congestion (e.g., FAILURE_CONGESTION) Absent Absent-User- O This information element may be present when User Diagnostic- Experimental-Result-Code is set to Diagnostic SM DIAMETER_ERROR_ABSENT_USER and it SM shall contain the reason of the absence of the user given by the MME or the SGSN. SM SM-Delivery- C If Experimental-Result-Code is set to Delivery Failure-Cause DIAMETER_ERROR_SM_DELIVERY_FAILURE, Failure this information element shall be present and Cause indicate one of the following: memory capacity exceeded in the mobile equipment; UE error; mobile equipment not equipped to support the mobile terminated short message service; NAS congestion. It may be completed with a Diagnostic information element having a code set to, for example, DIAMETER_ERROR_MME_CONGESTION SM RP UI SM-RP-UI O If present, this information element shall contain a short message transfer protocol data unit in the message delivery acknowledgement from the MME to the Service Center. Overload Overload- O If present, this information element shall contain Supported Supported- the list of supported overload features. Features Feature Overload Overload- O If present, this information element shall contain Parameters Parameters the desired overload controls (e.g., overload suppression value, a back-off timer, or other parameters) Supported Supported- O If present, this information element shall contain Features Features* the list of features supported by the origin host. *(See 3GPP TS 29.229) -
TABLE 4 Diameter-Based MT Forward Short Message Answer Command AVP Fields Command < header >, < fixed >, { required }, Definition and [ optional ] Notes < MT- < Diameter Header: 8388646, REQ, numeric code Forward- PXY, 16777313 > identifying the message Short- < Session-Id > Message- [ Vendor-Specific-Application-Id ] Answer > ::= [ Result-Code ] e.g., failure (congestion) [ Experimental-Result ] { Auth-Session-State } { Origin-Host } { Origin-Realm } [ Absent-User-Diagnostic-SM ] [ SM-Delivery-Failure-Cause ] e.g., MME is congested [ SM-RP-UI ] [Overload-Supported-Feature] Parameters that control [Overload-Parameters] for overload situation *[ Supported-Features ] *denotes elements that *[ AVP ] may have duplicate *[ Proxy-Info ] instances *[ Route-Record ] - In some embodiments, the “Supported-Features” AVP in the forgoing tables can be used in addition to or as an alternative to the discrete “Overload-Supported-Feature” or “Overload-Parameters” AVPs. Also, the forgoing tables have similar counterparts for MO forward short message procedures that may be used when an SMS-SC is overloaded. For example, if the SMS-SC 30 (
FIG. 1 ) is overloaded upon receipt of an MO forward short message request message from theMME 46, then the SMS-SC 30 may respond with an MO forward short message answer message that includes “Overload-Supported-Feature,” “Overload-Parameters,” or similar AVPs. - With respect to the foregoing tables, the MME and the SGSN behave as follows when receiving an MT Forward Short Message Request.
- The MME or the SGSN check if the IMSI is known.
- If it is not known, an Experimental-Result-Code set to DIAMETER_ERROR_USER_UNKNOWN is returned.
- The MME or the SGSN attempts to deliver the short message to the UE.
- If the delivery of the short message to the UE is successful, then the MME or the SGSN returns a Result-Code set to DIAMETER_SUCCESS.
- If the UE is not reachable via the MME, then the MME sets the MNRF flag and returns an Experimental-Result-Code set to DIAMETER_ERROR_ABSENT_USER.
- If the UE is not reachable via the SGSN, then the SGSN sets the MNRG flag and returns an Experimental-Result-Code set to DIAMETER_ERROR_ABSENT_USER.
- If the delivery of the mobile terminated short message failed because of memory capacity exceeded or UE error or UE not SM equipped, then the MME or the SGSN returns an Experimental-Result-Code set to DIAMETER_ERROR_SM_DELIVERY_FAILURE complemented with an SM Delivery Failure Cause indication.
- If a requested facility is not supported, then the MME or the SGSN returns an Experimental-Result-Code set to DIAMETER_ERROR_FACILITY_NOT_SUPPORTED.
- If the user is busy for MT SMS, i.e., the mobile terminated short message transfer cannot be completed because: another mobile terminated short message transfer is going on and the delivery node does not support message buffering, another mobile terminated short message transfer is going on and it is not possible to buffer the message for later delivery, or the message was buffered but it is not possible to deliver the message before the expiry of the buffering time defined in 3GPP TS 23.040; then the MME or the SGSN returns an Experimental-Result-Code set to DIAMETER_ERROR_USER_BUSY_FOR_MT_SMS.
- If the delivery of the mobile terminated short message failed because the mobile station failed authentication, then the MME or the SGSN returns an Experimental-Result-Code set to DIAMETER_ERROR_ILLEGAL_USER.
- If the delivery of the mobile terminated short message failed because an IMEI check failed, i.e., the IMEI was blacklisted or not white-listed, then the MME or the SGSN returns an Experimental-Result-Code set to DIAMETER_ERROR_ILLEGAL_EQUIPMENT.
- If the delivery of the mobile terminated short message failed because of NAS level congestion, then the MME or the SGSN returns an Experimental-Result-Code set to DIAMETER_ERROR_MME_CONGESTION or DIAMETER_ERROR_SGSN_CONGESTION. MME or SGSN may also send back-off timer.
- A common error cause DIAMETER_ERROR_SN_CONGESTION may also be defined where SN indicates “Serving Node.”
- With respect to the forgoing tables, the SMS-GMSC behaves as follows.
- The SMS-GMSC makes use of this procedure over the SGd interface or over the Gdd interface for the delivery of an MT short message when it has selected the serving node of which it obtained the Diameter Identity from the answer of the Send Routing Info for SM procedure.
- Note that the SMS-GMSC is not aware that the MT Forward Short Message Request may be routed to an SMS router.
- On receiving congestion result code with back-off timer, SMS-GMSC may start the timer. For an MT SM (or device triggering message) with validity period, the SMS-GMSC can compare the validity period and the back-off timer duration, if any, to conduct further handling for the triggering message. If the validity period is larger than the back-off timer duration, the SMS-GMSC can attempt delivery of the triggering message to the target UE at a later time after the expiration of the back-off timer duration. Otherwise, the SMS-GMSC can delete the triggering message after the expiration of the validity period and report the failure of the trigger delivery (e.g., indicates that the cause of the failure delivery is due to network congestion) to the MTC-IWF.
-
FIG. 3 provides an example illustration of a mobile device, commonly deployed as a UE, and referred to as a mobile station (MS), a mobile wireless device, a mobile communication device, a tablet, a handset, or other type of mobile wireless device. The mobile device can include one or more antennas configured to communicate with a transmission station, such as a base station (BS), an eNB, a base band unit (BBU), a remote radio head (RRH), a remote radio equipment (RRE), a relay station (RS), a radio equipment (RE), or other type of wireless wide area network (WWAN) access point. The mobile device can be configured to communicate using at least one wireless communication standard including 3GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and WiFi. The mobile device can communicate using separate antennas for each wireless communication standard or shared antennas for multiple wireless communication standards. The mobile device can communicate in a wireless local area network (WLAN), a wireless personal area network (WPAN), and/or a WWAN. -
FIG. 3 also provides an illustration of a microphone and one or more speakers that can be used for audio input and output from the mobile device. The display screen may be a liquid crystal display (LCD) screen, or other type of display screen such as an organic light emitting diode (OLED) display. The display screen can be configured as a touch screen. The touch screen may use capacitive, resistive, or another type of touch screen technology. An application processor and a graphics processor can be coupled to internal memory to provide processing and display capabilities. A non-volatile memory port can also be used to provide data input/output options to a user. The non-volatile memory port may also be used to expand the memory capabilities of the mobile device. A keyboard may be integrated with the mobile device or wirelessly connected to the mobile device to provide additional user input. A virtual keyboard may also be provided using the touch screen. - Examples may include subject matter such as a method, means for performing acts of the method, at least one machine-readable medium including instructions that, when performed by a machine cause the machine to performs acts of the method, or of an apparatus or system for SM load control according to embodiments and examples described herein. The following examples are enumerated for added clarity.
- An network entity for use in a 3rd generation partnership project (3GPP) network, the network entity comprising circuitry configured to: receive from a short message service-service center (SMS-SC) entity a mobile terminated (MT) forward short message request; determine whether the network entity is overloaded such that the network entity is unable to deliver a short message (SM) to a user equipment (UE); and send to the SMS-SC an MT forward short message answer having information indicating that the network entity is overloaded, in which the MT forward short message answer causes the SMS-SC to temporarily suppress sending further SMs, and in which the network entity comprises at least one of a mobility management entity (MME) or a serving general packet radio service support node (SGSN).
- The network entity of example 1, in which the information includes a suppression parameter that configures the SMS-SC to delay sending further SMs for a predetermined time.
- The network entity of example 1, in which the information includes a suppression parameter that configures the SMS-SC to continue to send high priority SMs to the UE during an overload situation or network congestion.
- The network entity of example 1, in which the circuitry is further configured to send a second message having updated suppression parameters for ceasing trigger suppression in response to the network entity recovering from being overloaded.
- The network entity of example 1, in which the network entity is overloaded due to hardware resource limitations or network congestion.
- The network entity of example 1, in which the circuitry is further configured to send a second message indicating updated suppression parameters for decreasing an amount of trigger suppression in response to the network entity recovering from being overloaded.
- The network entity of example 1, in which the MT forward short message request and the MT forward short message answer are defined by a diameter-based message format that includes an attribute value pair indicating an occurrence of a congestion situation.
- The network entity of example 1, in which in response to a non-access stratum (NAS) level congestion control in place for the UE, the network entity is configured to reject a trigger request so as to avoid mobile originated (MO) mobility management (MM) or session management signaling from the UE to the network.
- A short message service-service center (SMS-SC) device comprising circuitry configured to: transmit to a network node a short message (SM) by using an interface between the SMS-SC device and the network node, in which the interface is an SGd interface when the network node comprises a mobility management entity (MME), and in which the interface is a Gdd interface when the network node comprises a serving general packet radio service support node (SGSN); receive through the interface a message response indicating that network node is unable to deliver the SM to a target mobile station, the message response including a parameter for suppressing transmission of a subsequent SM to the network node while the network node is unable to deliver the subsequent SM; and determine whether to transmit the subsequent SM to the network node based on the message response.
- The SMS-SC device of example 9, in which the parameter includes a back-off timer indicating a suppression period for suppressing transmission of the subsequent SM to the network node during the suppression period.
- The SMS-SC of example 10, in which the subsequent SM includes a validity period, and the circuitry is further configured to: compare the validity period to the suppression period; and transmit the subsequent SM after expiration of the suppression period and prior to expiration of the validity period.
- The SMS-SC device of example 9, in which the circuitry is further configured to: determine whether the subsequent SM is a high priority SM; transmit the subsequent SM when it is a high priority SM; and suppress transmission of the subsequent SM when it is not a high priority SM.
- The SMS-SC device of example 9, in which the SM is a triggering message having a validity period, and the circuitry is further configured to: delete the triggering message after expiration of the validity period; and report a failure of trigger delivery.
- The SMS-SC device of example 9, in which the circuitry is further configured to: determine whether the SM is a device trigger or a mobile terminated short message service (MT-SMS) message by reading a transfer protocol-protocol identifier (TP-PID) field of the SM; and allow delivery of the SM based on whether it is determined to be a device trigger or an MT-SMS message.
- The SMS-SC of example 9, in which the circuitry is further configured to: determine whether the network node is congested based on an operator policy or configuration; and allow delivery of the SM based on whether it is determined to be a device trigger or a mobile terminated short message service message.
- A method for controlling an amount of mobile terminated (MT) short message service (SMS) (MT-SMS) messages to be delivered to a mobility management entity (MME) or a serving general packet radio service support node (SGSN) in a 3rd generation partnership project network, the method comprising: detecting at the MME/SGSN a congestion event; and transmitting over an SGd/Gdd interface, in response to detecting the congestion event, a diameter-based message including an information element having an attribute value pair indicating that the MME/SGSN is temporarily unable to deliver an MT-SMS message.
- The method of example 16, in which the MT-SMS messages comprise device triggering messages over a T4 interface.
- The method of example 16, further comprising: determining a suppression duration in which the MME/SGSN is temporarily unable to deliver an MT-SMS message; and including information in the diameter-based message that indicates the suppression duration.
- The method of example 16, further comprising: determining that the congestion event has subsided; and transmitting over an SGd/Gdd interface, a message indicating the congestion event has subsided.
- The method of example 16, in which the congestion event comprises a non-access stratum (NAS) level congestion control event.
- A network node comprising circuitry configured to: transmit to a short message service-service center (SMS-SC) device a mobile originated (MO) short message (SM) by using an interface between the network node and the SMS-SC device, in which the interface is an SGd interface when the network node comprises a mobility management entity (MME), and in which the interface is a Gdd interface when the network node comprises a serving general packet radio service support node (SGSN); receive through the interface a message response indicating that the SMS-SC device is unable to deliver the MO SM to a target destination, the message response including a parameter for suppressing transmission of a subsequent MO SM from the network node while the SMS-SC device is unable to deliver the subsequent MO SM; and determine whether to transmit the subsequent MO SM to the SMS-SC device based on the message response.
- The network node of example 21, in which the parameter includes a back-off timer indicating a suppression period for suppressing transmission of the subsequent MO SM to the SMS-SC device during the suppression period.
- The network node of example 22, in which the subsequent MO SM includes a validity period, and the circuitry is further configured to: compare the validity period to the suppression period; and transmit the subsequent MO SM after expiration of the suppression period and prior to expiration of the validity period.
- The network node of example 21, in which the circuitry is further configured to: determine whether the subsequent MO SM is a high priority MO SM; transmit the subsequent MO SM when it is a high priority MO SM; and suppress transmission of the subsequent MO SM when it is not a high priority MT SM.
- A method performed by a network entity for use in a 3rd generation partnership project (3GPP) network, the method comprising: receiving from a short message service-service center (SMS-SC) entity a mobile terminated (MT) forward short message request; determining whether the network entity is overloaded such that the network entity is unable to deliver a short message (SM) to a user equipment (UE); and sending to the SMS-SC an MT forward short message answer having information indicating that the network entity is overloaded, in which the MT forward short message answer causes the SMS-SC to temporarily suppress sending further SMs, and in which the network entity comprises at least one of a mobility management entity (MME) or a serving general packet radio service support node (SGSN).
- The method of example 25, in which the information includes a suppression parameter that configures the SMS-SC to delay sending further SMs for a predetermined time.
- The method of example 25, in which the information includes a suppression parameter that configures the SMS-SC to continue to send high priority SMs to the UE during an overload situation or network congestion.
- The method of example 25, further comprising sending a second message having updated suppression parameters for ceasing trigger suppression in response to the network entity recovering from being overloaded.
- The method of example 25, in which the network entity is overloaded due to hardware resource limitations or network congestion.
- The method of example 25, further comprising sending a second message indicating updated suppression parameters for decreasing an amount of trigger suppression in response to the network entity recovering from being overloaded.
- The method of example 25, in which the MT forward short message request and the MT forward short message answer are defined by a diameter-based message format that includes an attribute value pair indicating an occurrence of a congestion situation.
- The method of example 25, in which in response to a non-access stratum (NAS) level congestion control in place for the UE, the network entity is configured to reject a trigger request so as to avoid mobile originated (MO) mobility management (MM) or session management signaling from the UE to the network.
- A method performed by a short message service-service center (SMS-SC) device, the method comprising: transmitting to a network node a short message (SM) by using an interface between the SMS-SC device and the network node, in which the interface is an SGd interface when the network node comprises a mobility management entity (MME), and in which the interface is a Gdd interface when the network node comprises a serving general packet radio service support node (SGSN); receiving through the interface a message response indicating that network node is unable to deliver the SM to a target mobile station, the message response including a parameter for suppressing transmission of a subsequent SM to the network node while the network node is unable to deliver the subsequent SM; and determining whether to transmit the subsequent SM to the network node based on the message response.
- The method of example 33, in which the parameter includes a back-off timer indicating a suppression period for suppressing transmission of the subsequent SM to the network node during the suppression period.
- The method of example 34, in which the subsequent SM includes a validity period, and the method further comprising: comparing the validity period to the suppression period; and transmitting the subsequent SM after expiration of the suppression period and prior to expiration of the validity period.
- The method of example 33, further comprising: determining whether the subsequent SM is a high priority SM; transmitting the subsequent SM when it is a high priority SM; and suppressing transmission of the subsequent SM when it is not a high priority SM.
- The method of example 33, in which the SM is a triggering message having a validity period, and the method further comprising: deleting the triggering message after expiration of the validity period; and reporting a failure of trigger delivery.
- The method of example 33, further comprising: determining whether the SM is a device trigger or a mobile terminated short message service (MT-SMS) message by reading a transfer protocol-protocol identifier (TP-PID) field of the SM; and allowing delivery of the SM based on whether it is determined to be a device trigger or an MT-SMS message.
- The method of example 33, further comprising: determining whether the network node is congested based on an operator policy or configuration; and allowing delivery of the SM based on whether it is determined to be a device trigger or a mobile terminated short message service message.
- A computer-readable medium for controlling an amount of short message (SM) load communicated in a 3rd generation partnership project network, the computer-readable medium having stored thereon computer-executable instructions executable by a network entity to cause the network entity to: detect a congestion event at the network entity; and transmit over an SGd/Gdd interface, in response to detecting the congestion event, a diameter-based message including an information element having an attribute value pair indicating that the network entity is temporarily unable to deliver a SM message.
- The computer-readable medium of example 40, in which the SM load comprises device triggering messages.
- The computer-readable medium of example 40, in which the instructions cause the network entity to: determine a suppression duration in which the network entity is temporarily unable to deliver an SM; and include information in the diameter-based message that indicates the suppression duration.
- The computer-readable medium of example 40, in which the instructions cause the network entity to: determine that the congestion event has subsided; and transmit over an SGd/Gdd interface, a message indicating the congestion event has subsided.
- The computer-readable medium of example 40, in which the congestion event comprises a non-access stratum (NAS) level congestion control event.
- The computer-readable medium of any of examples 40 through 44, in which the SM load includes mobile terminated (MT) short message service (SMS) messages.
- The computer-readable medium of any of examples 40 through 44, in which the SM load includes mobile ordinated (MO) short message service (SMS) messages.
- The computer-readable medium of any of examples 40 through 44, in which the network entity comprises at least one of a mobility management entity (MME) or a serving general packet radio service support node (SGSN).
- The computer-readable medium of any of examples 40 through 44, in which the network entity comprises a short message service-service center (SMS-SC) entity.
- At least one computer readable storage medium, having instructions stored thereon, that when executed on a device perform the method of any of examples 16 through 20, and 25 through 39.
- The techniques introduced above can be implemented by programmable circuitry programmed or configured by software and/or firmware, or they can be implemented entirely by special-purpose hardwired circuitry, or in a combination of such forms. Such special-purpose circuitry (if any) can be in the form of, for example, one or more application-specific integrated circuits (ASICs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), etc.
- Embodiments may be implemented in one or a combination of hardware, firmware, and software. Embodiments may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein. A computer-readable storage device may include any non-transitory mechanism for storing information in a form readable by a machine (e.g., a computer). For example, a computer-readable storage device may include read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media. In some embodiments, one or more processors may be configured with instructions stored on a computer-readable storage device.
- Although the present disclosure includes reference to specific example embodiments, it will be recognized that the claims are not limited to the embodiments described, but can be practiced with modification and alteration within the spirit and scope of the appended claims. Accordingly, the specification and drawings are to be regarded in an illustrative sense rather than a restrictive sense. It will be understood by skilled persons that many changes may be made to the details of the above-described embodiments without departing from the underlying principles of the invention. The scope of the present invention should, therefore, be determined only by the following claims.
Claims (24)
1. A network entity for use in a 3rd generation partnership project (3GPP) network, the network entity comprising circuitry configured to:
receive from a short message service-service center (SMS-SC) entity a mobile terminated (MT) forward short message request;
determine whether the network entity is overloaded such that the network entity is unable to deliver a short message (SM) to a user equipment (UE); and
send to the SMS-SC an MT forward short message answer having information indicating that the network entity is overloaded, in which the MT forward short message answer causes the SMS-SC to temporarily suppress sending further SMs, and in which the network entity comprises at least one of a mobility management entity (MME) or a serving general packet radio service support node (SGSN).
2. The network entity of claim 1 , in which the information includes a suppression parameter that configures the SMS-SC to delay sending further SMs for a predetermined time.
3. The network entity of claim 1 , in which the information includes a suppression parameter that configures the SMS-SC to continue to send high priority SMs to the UE during an overload situation or network congestion.
4. The network entity of claim 1 , in which the circuitry is further configured to send a second message having updated suppression parameters for ceasing trigger suppression in response to the network entity recovering from being overloaded.
5. The network entity of claim 1 , in which the network entity is overloaded due to hardware resource limitations or network congestion.
6. The network entity of claim 1 , in which the circuitry is further configured to send a second message indicating updated suppression parameters for decreasing an amount of trigger suppression in response to the network entity recovering from being overloaded.
7. The network entity of claim 1 , in which the MT forward short message request and the MT forward short message answer are defined by a diameter-based message format that includes an attribute value pair indicating an occurrence of a congestion situation.
8. The network entity of claim 1 , in which in response to a non-access stratum (NAS) level congestion control in place for the UE, the network entity is configured to reject a trigger request so as to avoid mobile originated (MO) mobility management (MM) or session management signaling from the UE to the network.
9. A short message service-service center (SMS-SC) device comprising circuitry configured to:
transmit to a network node a short message (SM) by using an interface between the SMS-SC device and the network node, in which the interface is an SGd interface when the network node comprises a mobility management entity (MME), and in which the interface is a Gdd interface when the network node comprises a serving general packet radio service support node (SGSN);
receive through the interface a message response indicating that network node is unable to deliver the SM to a target mobile station, the message response including a parameter for suppressing transmission of a subsequent SM to the network node while the network node is unable to deliver the subsequent SM; and
determine whether to transmit the subsequent SM to the network node based on the message response.
10. The SMS-SC device of claim 9 , in which the parameter includes a back-off timer indicating a suppression period for suppressing transmission of the subsequent SM to the network node during the suppression period.
11. The SMS-SC of claim 10 , in which the subsequent SM includes a validity period, and the circuitry is further configured to:
compare the validity period to the suppression period; and
transmit the subsequent SM after expiration of the suppression period and prior to expiration of the validity period.
12. The SMS-SC device of claim 9 , in which the circuitry is further configured to:
determine whether the subsequent SM is a high priority SM;
transmit the subsequent SM when it is a high priority SM; and
suppress transmission of the subsequent SM when it is not a high priority SM.
13. The SMS-SC device of claim 9 , in which the SM is a triggering message having a validity period, and the circuitry is further configured to:
delete the triggering message after expiration of the validity period; and
report a failure of trigger delivery.
14. The SMS-SC device of claim 9 , in which the circuitry is further configured to:
determine whether the SM is a device trigger or a mobile terminated short message service (MT-SMS) message by reading a transfer protocol-protocol identifier (TP-PID) field of the SM; and
allow delivery of the SM based on whether it is determined to be a device trigger or an MT-SMS message.
15. The SMS-SC of claim 9 , in which the circuitry is further configured to:
determine whether the network node is congested based on an operator policy or configuration; and
allow delivery of the SM based on whether it is determined to be a device trigger or a mobile terminated short message service message.
16. A method for controlling an amount of mobile terminated (MT) short message service (SMS) (MT-SMS) messages to be delivered to a mobility management entity (MME) or a serving general packet radio service support node (SGSN) in a 3rd generation partnership project network, the method comprising:
detecting at the MME/SGSN a congestion event; and
transmitting over an SGd/Gdd interface, in response to detecting the congestion event, a diameter-based message including an information element having an attribute value pair indicating that the MME/SGSN is temporarily unable to deliver an MT-SMS message.
17. The method of claim 16 , in which the MT-SMS messages comprise device triggering messages over a T4 interface.
18. The method of claim 16 , further comprising:
determining a suppression duration in which the MME/SGSN is temporarily unable to deliver an MT-SMS message; and
including information in the diameter-based message that indicates the suppression duration.
19. The method of claim 16 , further comprising:
determining that the congestion event has subsided; and
transmitting over an SGd/Gdd interface, a message indicating the congestion event has subsided.
20. The method of claim 16 , in which the congestion event comprises a non-access stratum (NAS) level congestion control event.
21. A network node comprising circuitry configured to:
transmit to a short message service-service center (SMS-SC) device a mobile originated (MO) short message (SM) by using an interface between the network node and the SMS-SC device, in which the interface is an SGd interface when the network node comprises a mobility management entity (MME), and in which the interface is a Gdd interface when the network node comprises a serving general packet radio service support node (SGSN);
receive through the interface a message response indicating that the SMS-SC device is unable to deliver the MO SM to a target destination, the message response including a parameter for suppressing transmission of a subsequent MO SM from the network node while the SMS-SC device is unable to deliver the subsequent MO SM; and
determine whether to transmit the subsequent MO SM to the SMS-SC device based on the message response.
22. The network node of claim 21 , in which the parameter includes a back-off timer indicating a suppression period for suppressing transmission of the subsequent MO SM to the SMS-SC device during the suppression period.
23. The network node of claim 22 , in which the subsequent MO SM includes a validity period, and the circuitry is further configured to:
compare the validity period to the suppression period; and
transmit the subsequent MO SM after expiration of the suppression period and prior to expiration of the validity period.
24. The network node of claim 21 , in which the circuitry is further configured to:
determine whether the subsequent MO SM is a high priority MO SM;
transmit the subsequent MO SM when it is a high priority MO SM; and
suppress transmission of the subsequent MO SM when it is not a high priority MT SM.
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/486,651 US20150078154A1 (en) | 2013-09-17 | 2014-09-15 | Congestion control for short message service in 3rd generation partnership project (3gpp) systems |
ES14846265.8T ES2689847T3 (en) | 2013-09-17 | 2014-09-16 | Congestion control for short messaging service in 3rd Generation Association Project (3GPP) systems |
CN201480045706.8A CN105474688B (en) | 2013-09-17 | 2014-09-16 | The congestion control of short message service is directed in third generation cooperative partner program (3GPP) system |
EP14846265.8A EP3047674B1 (en) | 2013-09-17 | 2014-09-16 | Congestion control for short message service in 3rd generation partnership project (3gpp) systems |
PCT/US2014/055939 WO2015042069A1 (en) | 2013-09-17 | 2014-09-16 | Congestion control for short message service in 3rd generation partnership project (3gpp) systems |
HK16110647.8A HK1222757A1 (en) | 2013-09-17 | 2016-09-07 | Congestion control for short message service in 3rd generation partnership project (3gpp) systems (3gpp) |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201361879014P | 2013-09-17 | 2013-09-17 | |
US14/486,651 US20150078154A1 (en) | 2013-09-17 | 2014-09-15 | Congestion control for short message service in 3rd generation partnership project (3gpp) systems |
Publications (1)
Publication Number | Publication Date |
---|---|
US20150078154A1 true US20150078154A1 (en) | 2015-03-19 |
Family
ID=52667889
Family Applications (11)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/314,850 Active 2035-02-11 US9516541B2 (en) | 2013-09-17 | 2014-06-25 | Congestion measurement and reporting for real-time delay-sensitive applications |
US14/316,180 Active US9386476B2 (en) | 2013-09-17 | 2014-06-26 | Transmission of physical broadcast channel (PBCH) contents |
US14/316,188 Active 2034-08-22 US9264933B2 (en) | 2013-09-17 | 2014-06-26 | DRX operation for UL/DL reconfiguration |
US14/912,587 Abandoned US20160205651A1 (en) | 2013-09-17 | 2014-09-12 | Devices and methods for sending or receiving assistance data |
US14/912,588 Abandoned US20160205601A1 (en) | 2013-09-17 | 2014-09-12 | Early ttt termination |
US14/486,651 Abandoned US20150078154A1 (en) | 2013-09-17 | 2014-09-15 | Congestion control for short message service in 3rd generation partnership project (3gpp) systems |
US15/022,484 Active 2034-10-15 US10003994B2 (en) | 2013-09-17 | 2014-09-16 | Techniques for identifying physical hybrid automatic request indicator channel resources |
US14/991,696 Active US9867078B2 (en) | 2013-09-17 | 2016-01-08 | DRX operation for UL/DL reconfiguration |
US15/202,264 Active US10123231B2 (en) | 2013-09-17 | 2016-07-05 | Transmission of physical broadcast channel (PBCH) contents |
US15/659,425 Active US10306509B2 (en) | 2013-09-17 | 2017-07-25 | DRX operation for UL/DL reconfiguration |
US16/153,584 Active US11039334B2 (en) | 2013-09-17 | 2018-10-05 | Transmission of physical broadcast channel (PBCH) contents |
Family Applications Before (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/314,850 Active 2035-02-11 US9516541B2 (en) | 2013-09-17 | 2014-06-25 | Congestion measurement and reporting for real-time delay-sensitive applications |
US14/316,180 Active US9386476B2 (en) | 2013-09-17 | 2014-06-26 | Transmission of physical broadcast channel (PBCH) contents |
US14/316,188 Active 2034-08-22 US9264933B2 (en) | 2013-09-17 | 2014-06-26 | DRX operation for UL/DL reconfiguration |
US14/912,587 Abandoned US20160205651A1 (en) | 2013-09-17 | 2014-09-12 | Devices and methods for sending or receiving assistance data |
US14/912,588 Abandoned US20160205601A1 (en) | 2013-09-17 | 2014-09-12 | Early ttt termination |
Family Applications After (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/022,484 Active 2034-10-15 US10003994B2 (en) | 2013-09-17 | 2014-09-16 | Techniques for identifying physical hybrid automatic request indicator channel resources |
US14/991,696 Active US9867078B2 (en) | 2013-09-17 | 2016-01-08 | DRX operation for UL/DL reconfiguration |
US15/202,264 Active US10123231B2 (en) | 2013-09-17 | 2016-07-05 | Transmission of physical broadcast channel (PBCH) contents |
US15/659,425 Active US10306509B2 (en) | 2013-09-17 | 2017-07-25 | DRX operation for UL/DL reconfiguration |
US16/153,584 Active US11039334B2 (en) | 2013-09-17 | 2018-10-05 | Transmission of physical broadcast channel (PBCH) contents |
Country Status (10)
Country | Link |
---|---|
US (11) | US9516541B2 (en) |
EP (6) | EP3047580B1 (en) |
JP (3) | JP2016530840A (en) |
KR (3) | KR101909798B1 (en) |
CN (5) | CN113015209A (en) |
ES (1) | ES2701336T3 (en) |
HK (4) | HK1222481A1 (en) |
HU (2) | HUE041895T2 (en) |
TW (3) | TWI662856B (en) |
WO (5) | WO2015041754A1 (en) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150119092A1 (en) * | 2013-01-16 | 2015-04-30 | Huawei Device Co., Ltd. | Trigger message sending method, device and system |
CN106686561A (en) * | 2015-11-06 | 2017-05-17 | 阿尔卡特朗讯公司 | Support of mobile-terminated short message delivery for user equipment using power saving mechanism such as extended idle mode DRX |
CN108293273A (en) * | 2015-12-02 | 2018-07-17 | 瑞典爱立信有限公司 | For the enhancing of the MT SM transmission for the mobile terminal for enabling eDRX |
US10326562B2 (en) | 2013-11-13 | 2019-06-18 | Samsung Electronics Co., Ltd. | Method and apparatus for controlling power headroom report and hybrid automatic retransmission in mobile communication system |
US10455453B2 (en) * | 2017-08-16 | 2019-10-22 | T-Mobile Usa, Inc. | Service enablement based on access network |
US11722859B1 (en) * | 2012-07-02 | 2023-08-08 | CSC Holdings, LLC | Service continuity and network preference for SMS services |
Families Citing this family (82)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8488521B2 (en) | 2008-03-14 | 2013-07-16 | Interdigital Patent Holdings, Inc. | Behavior for wireless transmit/receive unit and MAC control elements for LTE DRX operations |
CN104105162B (en) * | 2013-04-05 | 2017-11-17 | 华为技术有限公司 | The method of transmission information, base station, terminal and system between base station and terminal |
JP6239270B2 (en) | 2013-05-29 | 2017-11-29 | 京セラ株式会社 | Base station, user terminal and processor |
WO2015017978A1 (en) * | 2013-08-06 | 2015-02-12 | Mediatek Inc. | Drx operations in adaptive tdd systems |
US9516541B2 (en) * | 2013-09-17 | 2016-12-06 | Intel IP Corporation | Congestion measurement and reporting for real-time delay-sensitive applications |
JP2016536915A (en) * | 2013-09-18 | 2016-11-24 | エヌイーシー(チャイナ)カンパニー, リミテッドNEC(China)Co.,Ltd. | Method and apparatus for improving effective range in wireless communication system |
WO2015054886A1 (en) * | 2013-10-18 | 2015-04-23 | Nokia Siemens Networks Oy | Dynamic uplink/downlink configuration |
CN105594169A (en) * | 2013-11-07 | 2016-05-18 | 华为技术有限公司 | System and method for traffic splitting |
TWI641278B (en) * | 2014-03-11 | 2018-11-11 | Lg電子股份有限公司 | Method for counting a drx (discontinuous reception) timer in a carrier aggregation system and a device therefor |
US9655025B1 (en) * | 2014-03-24 | 2017-05-16 | Sprint Spectrum L.P. | Managing the performance of a wireless device handover |
BR112017003000A2 (en) | 2014-08-15 | 2017-12-12 | Interdigital Patent Holdings Inc | improved coverage for time division duplexing and improved interference mitigation and traffic adaptation in long term evolution systems and wireless transmission / reception unit |
WO2016032218A2 (en) * | 2014-08-27 | 2016-03-03 | 엘지전자 주식회사 | Method for receiving reference signal in wireless communication system and apparatus therefor |
US9622241B2 (en) * | 2014-09-26 | 2017-04-11 | Alcatel Lucent | Method and apparatus for preventing message collision |
EP3207728B1 (en) * | 2014-10-17 | 2021-05-19 | Samsung Electronics Co., Ltd. | Methods and systems for enabling channel measurement of unlicensed carrier in cellular on unlicensed band systems |
US9614766B2 (en) * | 2014-12-16 | 2017-04-04 | Cisco Technology, Inc. | System and method to analyze congestion in low latency network |
WO2016132741A1 (en) * | 2015-02-20 | 2016-08-25 | 日本電気株式会社 | Wireless communication system, base station device, mobile station device, and wireless communication control method |
US10306618B2 (en) * | 2015-03-05 | 2019-05-28 | Lg Electronics Inc. | Method and wireless device for receiving downlink control channel |
CN106161302A (en) * | 2015-04-09 | 2016-11-23 | 电信科学技术研究院 | A kind of method and device of information transmission |
US11025446B2 (en) | 2015-06-15 | 2021-06-01 | Samsung Electronics Co., Ltd. | Method and apparatus for group communication in wireless communication system |
EP4318996A3 (en) * | 2015-07-30 | 2024-02-21 | Apple Inc. | Physical broadcast channel design |
US20170048014A1 (en) * | 2015-08-13 | 2017-02-16 | Spreadtrum Hong Kong Limited | Apparatus and method for generating scrambling codes for repetition transmissions |
GB2544103A (en) * | 2015-11-06 | 2017-05-10 | Nec Corp | Communication system |
US20170201340A1 (en) * | 2016-01-08 | 2017-07-13 | Lg Electronics Inc. | Method for receiving broadcast channel and apparatus therefor |
JP2019080085A (en) * | 2016-03-18 | 2019-05-23 | シャープ株式会社 | Terminal device, base station device, communication method, and integrated circuit |
US10855407B2 (en) * | 2016-05-09 | 2020-12-01 | Apple Inc. | Extended physical broadcast channel design for 5G standalone system |
CN109565896B (en) | 2016-08-11 | 2023-05-12 | 三星电子株式会社 | Low power RRC operation method and apparatus |
CN107733564A (en) * | 2016-08-12 | 2018-02-23 | 中兴通讯股份有限公司 | Determination method and device, base station, the terminal of PHICH resource |
EP4213550A1 (en) * | 2016-08-12 | 2023-07-19 | Sony Group Corporation | Location server, infrastructure equipment, communications device and methods |
US10638394B2 (en) * | 2016-09-07 | 2020-04-28 | Parallel Wireless, Inc. | Multi-stage handover |
KR20180035638A (en) | 2016-09-29 | 2018-04-06 | 삼성전자주식회사 | Method and apparatus of data transfer mode with/without rrc connection |
EP3536049A1 (en) * | 2016-11-02 | 2019-09-11 | IDAC Holdings, Inc. | Devices, systems and methods for power efficient beam management in wireless systems |
EP4220215A1 (en) * | 2016-11-18 | 2023-08-02 | Telefonaktiebolaget LM Ericsson (publ) | Detection of a narrowband positioning reference signal (nprs) location in a radio frame |
US10638444B2 (en) * | 2016-12-01 | 2020-04-28 | Qualcomm Incorporated | Positioning techniques for wireless communications devices using shared radio frequency spectrum |
US10470191B2 (en) | 2016-12-09 | 2019-11-05 | Samsung Electronics Co., Ltd. | Method and apparatus of broadcast signals and channels for system information transmission |
US10778384B2 (en) | 2016-12-20 | 2020-09-15 | Verizon Patent And Licensing Inc. | System and method for improved capacity using channel multiplexing |
US10904729B2 (en) * | 2016-12-20 | 2021-01-26 | Verizon Patent And Licensing Inc. | System and method for improved capacity using channel multiplexing |
EP3566348A1 (en) * | 2017-01-06 | 2019-11-13 | IDAC Holdings, Inc. | Error check-based synchronization and broadcast channel |
CN115314182A (en) | 2017-01-09 | 2022-11-08 | 瑞典爱立信有限公司 | Coordination of duplex directions in NR TDD systems |
KR102379582B1 (en) * | 2017-01-11 | 2022-03-29 | 후아웨이 테크놀러지 컴퍼니 리미티드 | Message transmission method and device |
CN108347293B (en) * | 2017-01-24 | 2023-10-24 | 华为技术有限公司 | Transmission method and device |
CN108347296B (en) | 2017-01-25 | 2020-12-22 | 华为技术有限公司 | Information transmission method and equipment |
CN110192368B (en) * | 2017-01-27 | 2022-04-05 | 高通股份有限公司 | Techniques and apparatus for channel interference reduction |
US10638485B2 (en) * | 2017-01-27 | 2020-04-28 | Qualcomm Incorporated | Techniques and apparatuses for channel interference reduction |
GB2562023A (en) * | 2017-02-03 | 2018-11-07 | Tcl Communication Ltd | Synchronisation in cellular networks |
FI3580977T3 (en) | 2017-02-07 | 2023-02-28 | Method and apparatus for broadcast channel configuration and broadcast channel transmission and reception for communication system | |
US10390218B2 (en) | 2017-02-17 | 2019-08-20 | At&T Intellectual Property I, L.P. | Dynamically requesting mobile devices to report network information |
US10568102B2 (en) | 2017-02-23 | 2020-02-18 | Qualcomm Incorporated | Usage of synchronization signal block index in new radio |
US10454657B2 (en) | 2017-02-28 | 2019-10-22 | Qualcomm Incorporated | Narrowband time-division duplex frame structure for narrowband communications |
ES2867873T3 (en) * | 2017-03-17 | 2021-10-21 | Guangdong Oppo Mobile Telecommunications Corp Ltd | Method for detecting the sync signal block and method, apparatus and system for transmitting the sync signal block |
CN112469127B (en) * | 2017-03-20 | 2024-03-19 | 华为技术有限公司 | Communication method, terminal and network equipment |
EP4090087A1 (en) * | 2017-03-23 | 2022-11-16 | Telefonaktiebolaget LM Ericsson (publ) | Method and device for determining timer configuration |
CN108738137B (en) * | 2017-04-14 | 2021-08-03 | 普天信息技术有限公司 | Processing method and device for sending PBCH |
CN110098908B (en) * | 2017-05-04 | 2020-09-08 | 华为技术有限公司 | PBCH transmission method and device |
CN108809497B (en) * | 2017-05-05 | 2021-11-02 | 展讯通信(上海)有限公司 | Bearing method of time index, detection method and device, storage medium, base station and terminal |
CN109302741B (en) * | 2017-05-05 | 2019-11-19 | 华为技术有限公司 | Communication means and communication device |
CN108811007B (en) * | 2017-05-05 | 2022-04-26 | 中兴通讯股份有限公司 | OTDOA positioning auxiliary data configuration method, device and system |
US10880062B2 (en) * | 2017-06-29 | 2020-12-29 | Qualcomm Incorporated | Providing protection for information delivered in demodulation reference signals (DMRS) |
CN114584260B (en) * | 2017-07-27 | 2024-02-13 | 苹果公司 | Scrambling of Physical Broadcast Channel (PBCH) |
WO2019022577A1 (en) * | 2017-07-28 | 2019-01-31 | 엘지전자 주식회사 | Method for transmitting and receiving broadcast channel and device therefor |
WO2019028793A1 (en) * | 2017-08-10 | 2019-02-14 | 华为技术有限公司 | Random access preamble transmitting method and device |
RU2749181C1 (en) | 2017-09-07 | 2021-06-07 | Гуандун Оппо Мобайл Телекоммьюникейшнс Корп., Лтд. | Method for interrupted reception, network apparatus and terminal apparatus |
US10743257B2 (en) * | 2017-09-15 | 2020-08-11 | Qualcomm Incorporated | Techniques and apparatuses for wakeup signal transmission |
US10082559B1 (en) * | 2017-09-22 | 2018-09-25 | Nokia Technologies Oy | PCI cell restriction and coarse geometry |
US11320511B2 (en) | 2017-09-29 | 2022-05-03 | Futurewei Technologies, Inc. | Observed time difference of arrival (OTDOA) positioning in wireless communication networks |
US11283540B2 (en) * | 2017-10-06 | 2022-03-22 | Qualcomm Incorporated | Cell-specific interleaving, rate-matching, and/or resource element mapping |
US11290957B2 (en) * | 2017-11-17 | 2022-03-29 | Samsung Electronics Co., Ltd. | Sequence design of wake-up signals and resynchronization sequence |
US10349429B1 (en) * | 2017-12-17 | 2019-07-09 | Telefonaktiebolaget Lm Ericsson (Publ) | System and method for frequency redirection in a communication system |
WO2019153126A1 (en) * | 2018-02-06 | 2019-08-15 | 华为技术有限公司 | Feedback information indicating method and device |
WO2019213972A1 (en) * | 2018-05-11 | 2019-11-14 | 华为技术有限公司 | Method and apparatus for transmitting random access preamble |
CN112119600B (en) * | 2018-05-18 | 2022-05-24 | 华为技术有限公司 | Network access node and client device for content type indication |
WO2020013447A1 (en) | 2018-07-09 | 2020-01-16 | 엘지전자 주식회사 | Method for transmitting and receiving physical downlink shared channel in wireless communication system, and apparatus supporting same |
US11329780B2 (en) | 2019-01-16 | 2022-05-10 | Qualcomm Incorporated | Physical layer non-line-of-sight (LOS) path discrimination using multiple frequency carriers |
US11956161B2 (en) * | 2019-07-10 | 2024-04-09 | Telefonaktiebolaget Lm Ericsson (Publ) | Technique for determining a packet delay budget |
US11438272B2 (en) * | 2019-12-31 | 2022-09-06 | Opanga Networks, Inc. | System and method for mobility tracking |
KR20210119839A (en) * | 2020-03-25 | 2021-10-06 | 삼성전자주식회사 | Electornic device for measuring communication signal from outside and method for operating thereof |
KR20230084102A (en) * | 2020-07-01 | 2023-06-12 | 퀄컴 인코포레이티드 | Timing offset signaling between stations for user equipment based positioning |
KR20220009523A (en) | 2020-07-15 | 2022-01-25 | 삼성전자주식회사 | Storage controller, and operation mehtod of storage controller |
CA3189529A1 (en) | 2020-07-21 | 2022-01-27 | Zte Corporation | Systems and methods for beam indication in multi-beam cell |
CN114513740B (en) * | 2020-10-27 | 2024-01-12 | 大唐移动通信设备有限公司 | Positioning method, positioning device, terminal and positioning equipment |
CN115695109A (en) * | 2021-07-31 | 2023-02-03 | 华为技术有限公司 | Scrambling and descrambling method and communication device |
US12047266B2 (en) * | 2022-01-14 | 2024-07-23 | Qualcomm Incorporated | Round-trip time as a latency performance indicator |
WO2024016265A1 (en) * | 2022-07-21 | 2024-01-25 | Qualcomm Incorporated | Artificial intelligence based discontinuous reception configuration |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030003953A1 (en) * | 2001-06-18 | 2003-01-02 | Comverse Network Systems Ltd. | Multi-user chat service in a cellular network |
US20070184856A1 (en) * | 2006-02-06 | 2007-08-09 | Narendranath Kudlu | Choice-based short messaging service in wireless networks and devices therefor |
US20110263278A1 (en) * | 2010-04-21 | 2011-10-27 | Research In Motion Limited | User Interface Methods And Apparatus For Use In Communicating Messages |
US20120257571A1 (en) * | 2011-04-07 | 2012-10-11 | Liao Ching-Yu | Method of Handling Signaling and Data Transmission for Machine-Type Communication |
US20140287752A1 (en) * | 2011-10-03 | 2014-09-25 | Lg Electronics Inc. | Mobility management entity handling sms-related signal |
US20140341041A1 (en) * | 2011-12-13 | 2014-11-20 | Panasonic Corporation | Device triggering and apn-based congestion control |
US20140370923A1 (en) * | 2012-02-01 | 2014-12-18 | Zte Corporation | Method and system for sending short message |
Family Cites Families (123)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US2983418A (en) * | 1958-12-31 | 1961-05-09 | Ernest A Hendrie | Ticker tape carrier |
US8031583B2 (en) * | 2005-03-30 | 2011-10-04 | Motorola Mobility, Inc. | Method and apparatus for reducing round trip latency and overhead within a communication system |
KR101247698B1 (en) * | 2005-08-05 | 2013-03-26 | 삼성디스플레이 주식회사 | Liquid crystal display |
EP2034750B1 (en) * | 2006-06-29 | 2017-05-17 | Fujitsu Limited | Cell selection method, mobile station apparatus, and mobile communication system in hierarchical cell structure |
JP4806665B2 (en) * | 2007-06-19 | 2011-11-02 | 株式会社エヌ・ティ・ティ・ドコモ | Base station apparatus, transmission method, and communication system |
DE102007038099A1 (en) * | 2007-08-13 | 2009-04-16 | T-Mobile International Ag | Method for avoiding ping-pong hand-over in mobile networks |
US8767634B2 (en) * | 2007-08-14 | 2014-07-01 | Lg Electronics Inc. | Method for acquiring resource region information for PHICH and method of receiving PDCCH |
CN101953181A (en) * | 2007-12-17 | 2011-01-19 | 三菱电机株式会社 | Mobile communication system |
US8396068B2 (en) * | 2007-12-20 | 2013-03-12 | Lg Electronics Inc. | Method for transmitting data in wireless communication system |
US8699487B2 (en) | 2008-02-04 | 2014-04-15 | Qualcomm Incorporated | Uplink delay budget feedback |
US7843817B2 (en) * | 2008-03-11 | 2010-11-30 | Cisco Technology, Inc. | Congestion control in wireless mesh networks |
EP2255588B1 (en) * | 2008-03-20 | 2018-05-09 | Telefonaktiebolaget LM Ericsson (publ) | Scheduling of uplink measurement reports |
US8559298B2 (en) * | 2008-06-30 | 2013-10-15 | Qualcomm Incorporated | Method and apparatus for automatic handover optimization |
CN101646239B (en) * | 2008-08-06 | 2012-05-09 | 中兴通讯股份有限公司 | Semi-persistent scheduling method |
KR101215690B1 (en) * | 2008-10-31 | 2012-12-26 | 엘지전자 주식회사 | Method and apparatus for performing harq process in wireless communication system |
CN101730207B (en) * | 2008-11-03 | 2015-04-15 | 电信科学技术研究院 | Method and UE for enhancing power saving performance of UE |
WO2010066063A1 (en) * | 2008-12-10 | 2010-06-17 | Telefonaktiebogalet L M Ericsson (Publ) | Tdd intra frequency handover measurement enhancement |
WO2010078365A1 (en) * | 2008-12-30 | 2010-07-08 | Interdigital Patent Holdings, Inc. | Discontinuous reception for carrier aggregation |
US8982759B2 (en) * | 2009-01-15 | 2015-03-17 | Lg Electronics Inc. | System information transmitting and receiving device |
JP5075859B2 (en) | 2009-03-09 | 2012-11-21 | 株式会社エヌ・ティ・ティ・ドコモ | Wireless base station |
US20100273451A1 (en) * | 2009-04-28 | 2010-10-28 | Bergstroem Joakim | Method and Apparatus for Mobile Terminal Positioning Operations |
US8446868B2 (en) * | 2009-05-07 | 2013-05-21 | Qualcomm Incorporated | Method and apparatus for processing blind decoding results in a wireless communication system |
KR20100127723A (en) * | 2009-05-26 | 2010-12-06 | 엘지전자 주식회사 | Method for obtaining antenna information in a wireless communication system and apparatus thereof |
US9002354B2 (en) * | 2009-06-12 | 2015-04-07 | Google Technology Holdings, LLC | Interference control, SINR optimization and signaling enhancements to improve the performance of OTDOA measurements |
US20120327779A1 (en) * | 2009-06-12 | 2012-12-27 | Cygnus Broadband, Inc. | Systems and methods for congestion detection for use in prioritizing and scheduling packets in a communication network |
PT3419366T (en) * | 2009-06-15 | 2021-02-01 | Guangdong Oppo Mobile Telecommunications Corp Ltd | Method for discontinuous reception operation for long term evolution advanced carrier aggregation |
WO2010147445A2 (en) * | 2009-06-19 | 2010-12-23 | 엘지전자 주식회사 | Cell searching method and apparatus in multi-carrier system |
US9042240B2 (en) * | 2009-07-31 | 2015-05-26 | Qualcomm Incorporated | Systems, apparatus and methods for broadcast channel decoding |
US8838132B2 (en) * | 2009-08-12 | 2014-09-16 | Qualcomm Incorporated | Enhanced positioning assistance data for reduced signaling |
SG178359A1 (en) * | 2009-08-13 | 2012-03-29 | Interdigital Patent Holdings | Method and apparatus for supporting positioning measurements |
US9084171B2 (en) * | 2009-09-10 | 2015-07-14 | At&T Mobility Ii Llc | Predictive hard and soft handover |
CN102036348B (en) * | 2009-09-30 | 2014-01-01 | 中兴通讯股份有限公司 | Discontinuous reception configuration method and system |
US9184899B2 (en) * | 2009-10-14 | 2015-11-10 | Qualcomm Incorporated | Downlink association set for uplink ACK/NACK in time division duplex system |
KR20110055367A (en) | 2009-11-17 | 2011-05-25 | 엘지전자 주식회사 | Method and apparatus of performing harq in multiple antenna system |
US8559958B2 (en) * | 2009-11-30 | 2013-10-15 | Samsung Electronics Co., Ltd | Methods and apparatus for handover between macro base station and home base station |
KR101750371B1 (en) * | 2009-12-24 | 2017-07-03 | 삼성전자 주식회사 | Method and apparatus defining transmission and reception time of physical channels supporting cross carrier scheduling in TDD cellular communication systems |
CN102714877B (en) * | 2010-01-08 | 2016-05-04 | 交互数字专利控股公司 | Carry out for the discontinuous reception of multicarrier/many cell operations and/or the method and apparatus of discontinuous transmission |
US9083494B2 (en) * | 2010-03-23 | 2015-07-14 | Qualcomm Incorporated | Efficient resource utilization in TDD |
WO2011135796A1 (en) * | 2010-04-28 | 2011-11-03 | パナソニック株式会社 | Wireless communication apparatus and wireless communication method |
WO2011139100A2 (en) * | 2010-05-04 | 2011-11-10 | 엘지전자 주식회사 | Method and device for downlink confirmation response data transmission resource allocation in a wireless communication system |
EP2387272B1 (en) * | 2010-05-11 | 2016-11-30 | Telefonaktiebolaget LM Ericsson (publ) | Storing of neighbour cell information for rapid recovery in case of handover failure |
WO2012008816A2 (en) * | 2010-07-16 | 2012-01-19 | 엘지전자 주식회사 | Method and apparatus for transmitting location estimation message in wireless communication system |
KR101191215B1 (en) * | 2010-07-16 | 2012-10-15 | 엘지전자 주식회사 | Method and apparatus of positioning in a wireless communication system |
WO2012023893A1 (en) * | 2010-08-16 | 2012-02-23 | Telefonaktiebolaget L M Ericsson (Publ) | Positioning node, user equipment and methods therein |
WO2012022026A1 (en) * | 2010-08-17 | 2012-02-23 | 富士通株式会社 | Method, system and transmitter for allocating resources |
US8797896B2 (en) * | 2010-08-25 | 2014-08-05 | Futurewei Technologies, Inc. | System and method for assigning backhaul resources |
KR101285398B1 (en) * | 2010-09-08 | 2013-07-10 | 엘지전자 주식회사 | Method and apparutus for transmitting control information |
CN102457854B (en) | 2010-10-14 | 2015-06-03 | 华为技术有限公司 | Method, device and system for solving channel conflict |
US8903415B2 (en) * | 2011-01-19 | 2014-12-02 | Telefonaktiebolaget Lm Ericsson | User equipment, a positioning node and methods therein |
KR20120084533A (en) * | 2011-01-20 | 2012-07-30 | 삼성전자주식회사 | Method and apparatus for supporting handover in heterogeneous network |
CN102075993B (en) * | 2011-01-30 | 2013-06-05 | 大唐移动通信设备有限公司 | Method and equipment for maintaining timer in carrier aggregation system |
WO2012112104A1 (en) * | 2011-02-15 | 2012-08-23 | Telefonaktiebolaget L M Ericsson (Publ) | Methods and systems for enabling user activity-aware positioning |
US8831611B2 (en) * | 2011-02-18 | 2014-09-09 | Blackberry Limited | Method and apparatus for avoiding in-device coexistence interference with keeping time update for handover |
US8665717B2 (en) | 2011-02-18 | 2014-03-04 | Verizon Patent And Licensing Inc. | Data rate aware scheduling in advanced wireless networks |
US9119102B2 (en) * | 2011-04-04 | 2015-08-25 | Telefonaktiebolaget Lm Ericsson (Publ) | Radio network node and method for using positioning gap indication for enhancing positioning performance |
WO2012149319A1 (en) * | 2011-04-29 | 2012-11-01 | Research In Motion Limited | Receiving messages in connection with lte wakeup |
US9282494B2 (en) * | 2011-05-02 | 2016-03-08 | Telefonaktiebolaget L M Ericsson (Publ) | Method in a radio network node for controlling handover decision of a user equipment |
US8797924B2 (en) | 2011-05-06 | 2014-08-05 | Innovative Sonic Corporation | Method and apparatus to improve discontinuous reception (DRX) operation for TDD (time division duplex) and FDD (frequency division duplex) mode in carrier aggregation (CA) |
US9271281B2 (en) | 2011-05-06 | 2016-02-23 | Innovation Sonic Corporation | Method and apparatus to improve inter-band carrier aggregation (CA) in TDD (time division duplex) mode |
US8570971B2 (en) * | 2011-05-06 | 2013-10-29 | Qualcomm Incorporated | Systems and methods for configuring remote radio heads |
WO2013002591A2 (en) * | 2011-06-28 | 2013-01-03 | 엘지전자 주식회사 | Method for user equipment transreceiving signal in wireless communication system |
CN103703734B (en) * | 2011-07-27 | 2019-03-19 | Lg电子株式会社 | The method of uplink reference signals and the terminal using this method are sent in multi-node system |
US20130040692A1 (en) * | 2011-08-11 | 2013-02-14 | Mediatek, Inc. | Method of Heterogeneous Network Mobility |
US11184142B2 (en) * | 2011-08-12 | 2021-11-23 | Nokia Solutions And Networks Oy | Discontinuous reception for carrier aggregation |
US8923274B2 (en) | 2011-08-15 | 2014-12-30 | Blackberry Limited | Notifying a UL/DL configuration in LTE TDD systems |
US8705556B2 (en) | 2011-08-15 | 2014-04-22 | Blackberry Limited | Notifying a UL/DL configuration in LTE TDD systems |
EP2749082B1 (en) * | 2011-08-25 | 2016-04-13 | Telefonaktiebolaget LM Ericsson (publ) | Adapting a triggering threshold for cell re-selection measurements |
CN103051428B (en) * | 2011-10-13 | 2018-08-24 | 中兴通讯股份有限公司 | The only PCI feedback cell determination methods and system of the terminal of configuration dedicated channel |
KR101973466B1 (en) | 2011-11-01 | 2019-04-30 | 엘지전자 주식회사 | Method for transmitting and receiving a signal, and apparatus therefor |
KR101953216B1 (en) | 2011-11-11 | 2019-02-28 | 삼성전자주식회사 | Method and apparatus for transmiting system information in mobile communucation system |
CN103947144B (en) * | 2011-11-23 | 2017-03-08 | Lg电子株式会社 | The method and apparatus sending/obtain control information in a wireless communication system |
US9078253B2 (en) * | 2011-11-28 | 2015-07-07 | Samsung Electronics Co., Ltd. | Apparatus and method for machine-type communications |
CN102523627B (en) * | 2011-12-08 | 2014-04-02 | 电信科学技术研究院 | Data transmission method and apparatus thereof |
US9609675B2 (en) * | 2012-01-16 | 2017-03-28 | Lg Electronics Inc. | Method and apparatus for monitoring control channel |
CN103220811B (en) * | 2012-01-19 | 2018-04-27 | 中兴通讯股份有限公司 | The method of information processing method, MTC UE random access LTE systems |
CN103220104B (en) * | 2012-01-20 | 2018-02-09 | 北京三星通信技术研究有限公司 | A kind of PUSCH transmission method |
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 |
US9344943B2 (en) * | 2012-01-30 | 2016-05-17 | Telefonaktiebolaget Lm Ericsson (Publ) | Inter-frequency and inter-RAT small cell detection in heterogeneous networks |
US9008585B2 (en) * | 2012-01-30 | 2015-04-14 | Futurewei Technologies, Inc. | System and method for wireless communications measurements and CSI feedback |
TWI624184B (en) * | 2012-02-03 | 2018-05-11 | 內數位專利控股公司 | Method and apparatus for coexistence among wireless transmit/receive units (wtrus) operating in the same spectrum |
US9019836B2 (en) * | 2012-02-03 | 2015-04-28 | Qualcomm Incorporated | Downlink data transfer flow control during carrier aggregation |
EP2815603B1 (en) | 2012-02-17 | 2019-09-25 | Interdigital Patent Holdings, Inc. | Hierarchical traffic differentiation to handle congestion and/or manage user quality of experience |
ES2429663B1 (en) | 2012-02-28 | 2015-04-13 | Telefónica, S.A. | METHOD AND SYSTEM FOR PLANNING THE DESCENDING LINK IN LONG-TERM EVOLUTION NETWORKS (LTE) BASED ON QUALITY OF SERVICE (QOS) |
US20150049653A1 (en) * | 2012-03-16 | 2015-02-19 | Samsung Electronics Co., Ltd. | Method and system for handling ue behavior in inter-band carrier aggregation with cell specific tdd configuration |
US9526091B2 (en) | 2012-03-16 | 2016-12-20 | Intel Corporation | Method and apparatus for coordination of self-optimization functions in a wireless network |
US20130250878A1 (en) * | 2012-03-23 | 2013-09-26 | Samsung Electronics Co., Ltd | Apparatus and method for machine-type communications |
US9674855B2 (en) * | 2012-03-29 | 2017-06-06 | Qualcomm Incorporated | H-ARQ timing determination under cross-carrier scheduling in LTE |
WO2013157905A1 (en) * | 2012-04-20 | 2013-10-24 | 엘지전자 주식회사 | Method for transceiving signals, and apparatus therefor |
US9686056B2 (en) * | 2012-05-11 | 2017-06-20 | Blackberry Limited | PHICH transmission in time division duplex systems |
US10154483B2 (en) * | 2012-09-12 | 2018-12-11 | Qualcomm Incorporated | Coverage enhancement techniques for machine type communication devices in a wireless network |
WO2014042423A2 (en) * | 2012-09-16 | 2014-03-20 | 엘지전자 주식회사 | Method by which a terminal receives enhanced downlink control channel in wireless communication system, and apparatus for same |
CN118509125A (en) * | 2012-09-26 | 2024-08-16 | 交互数字专利控股公司 | Dynamic TDD uplink/downlink configuration method |
WO2014054887A1 (en) * | 2012-10-02 | 2014-04-10 | 한양대학교 산학협력단 | Method for transmitting and receiving downlink signal and channel, terminal therefor, and base station therefor |
KR102082971B1 (en) * | 2012-10-05 | 2020-02-28 | 인터디지탈 패튼 홀딩스, 인크 | Method and apparatus for enhancing coverage of machine type communication (mtc) devices |
ES2682251T3 (en) * | 2012-10-12 | 2018-09-19 | Nec Corporation | Communications Node |
US9893853B2 (en) * | 2012-11-01 | 2018-02-13 | Lg Electronics Inc. | Method and apparatus for transceiving reference signal in wireless communication system |
CN103795510A (en) * | 2012-11-02 | 2014-05-14 | 北京三星通信技术研究有限公司 | Method and device for transmitting HARQ instruction information |
US9407302B2 (en) * | 2012-12-03 | 2016-08-02 | Intel Corporation | Communication device, mobile terminal, method for requesting information and method for providing information |
US9516659B2 (en) * | 2012-12-06 | 2016-12-06 | Intel Corporation | Carrier type (NCT) information embedded in synchronization signal |
US9820295B2 (en) * | 2013-01-10 | 2017-11-14 | Telefonaktiebolaget Lm Ericsson (Publ) | Over-the air signaling for coordination of time-division duplexing |
US9485763B2 (en) * | 2013-01-14 | 2016-11-01 | Lg Electronics Inc. | Method and user equipment for receiving downlink signal and method and base station for transmitting downlink signal |
EP3399685B1 (en) * | 2013-01-14 | 2019-12-25 | LG Electronics Inc. | Method and user equipment for receiving downlink signal and method and base station for transmitting downlink signal |
CN105164963B (en) * | 2013-01-18 | 2019-04-23 | 安华高科技股份有限公司 | Method, equipment and the wireless terminal of the repetition transmission of downlink control signal |
KR101729565B1 (en) * | 2013-03-04 | 2017-05-02 | 엘지전자 주식회사 | Method for controlling uplink power in wireless communication system and device therefor |
CN105052216B (en) | 2013-04-03 | 2019-01-04 | 夏普株式会社 | Terminal installation, base station apparatus, integrated circuit and wireless communications method |
US9160515B2 (en) * | 2013-04-04 | 2015-10-13 | Intel IP Corporation | User equipment and methods for handover enhancement using scaled time-to-trigger and time-of-stay |
US9735942B2 (en) * | 2013-04-05 | 2017-08-15 | Qualcomm Incorporated | Physical broadcast channel (PBCH) coverage enhancements for machine type communications (MTC) |
HUE052173T2 (en) * | 2013-04-05 | 2021-04-28 | Ericsson Telefon Ab L M | Broadcast of information for new carrier type |
US9854599B2 (en) * | 2013-04-26 | 2017-12-26 | Sharp Kabushiki Kaisha | Terminal device, integrated circuit, and radio communication method capable of reducing power consumption in radio communication system to which dynamic TDD is applied |
CN110266454B (en) * | 2013-05-12 | 2021-08-06 | Lg电子株式会社 | Apparatus for receiving system information block |
US9974068B2 (en) * | 2013-05-16 | 2018-05-15 | Lg Electronics Inc. | Method for transmitting signal for improving coverage and apparatus for same |
WO2014204285A1 (en) * | 2013-06-21 | 2014-12-24 | Lg Electronics Inc. | A method for enhancing coverage of user equipment and an apparatus using the same |
US9432809B2 (en) * | 2013-07-12 | 2016-08-30 | Qualcomm Incorporated | Providing OTDOA PRS assistance data |
JP2016530781A (en) * | 2013-07-16 | 2016-09-29 | エレクトロニクス アンド テレコミュニケーションズ リサーチ インスチチュートElectronics And Telecommunications Research Institute | Communication method in carrier aggregation-based wireless communication system (COMMUNICATION METHOD IN WIRELESS COMMUNICATION SYSTEM ON BASIS OF CARRIER AGGREGATION) |
US20160295597A1 (en) * | 2013-07-26 | 2016-10-06 | Intel IP Corporation | Signaling interference information for user equipment assistance |
US9374151B2 (en) * | 2013-08-08 | 2016-06-21 | Intel IP Corporation | Coverage extension level for coverage limited device |
CN104349458B (en) * | 2013-08-08 | 2019-05-17 | 中兴通讯股份有限公司 | Transmission method, method for transmission processing, communication node and the terminal of control channel |
WO2015042117A1 (en) | 2013-09-17 | 2015-03-26 | Intel IP Corporation | Congestion measurement and reporting for real-time delay-sensitive applications |
US9516541B2 (en) * | 2013-09-17 | 2016-12-06 | Intel IP Corporation | Congestion measurement and reporting for real-time delay-sensitive applications |
US9667386B2 (en) * | 2013-11-13 | 2017-05-30 | Samsung Electronics Co., Ltd | Transmission of control channel and data channels for coverage enhancements |
EP2887760A1 (en) * | 2013-12-23 | 2015-06-24 | Telefonica S.A. | A method and a system for performing virtualization of a radio access technology over Orthogonal Frequency-Division Multiple Access (OFDMA) wireless networks and computer program products thereof |
CN106716908B (en) * | 2014-09-27 | 2020-04-17 | Lg电子株式会社 | Method for transmitting and receiving signal in wireless communication system and apparatus for performing the same |
WO2016114626A1 (en) * | 2015-01-16 | 2016-07-21 | 엘지전자 주식회사 | Method and device for transmitting and receiving shared control message in wireless access system supporting machine type communication |
-
2014
- 2014-06-25 US US14/314,850 patent/US9516541B2/en active Active
- 2014-06-26 US US14/316,180 patent/US9386476B2/en active Active
- 2014-06-26 US US14/316,188 patent/US9264933B2/en active Active
- 2014-07-30 KR KR1020167011221A patent/KR101909798B1/en active IP Right Grant
- 2014-07-30 JP JP2016541968A patent/JP2016530840A/en active Pending
- 2014-07-30 KR KR1020167001756A patent/KR101737745B1/en active IP Right Grant
- 2014-07-30 EP EP14846269.0A patent/EP3047580B1/en active Active
- 2014-07-30 WO PCT/US2014/048954 patent/WO2015041754A1/en active Application Filing
- 2014-07-30 EP EP16170298.0A patent/EP3101824B1/en active Active
- 2014-07-30 HU HUE16170298A patent/HUE041895T2/en unknown
- 2014-07-30 KR KR1020177033368A patent/KR101922366B1/en active IP Right Grant
- 2014-07-30 ES ES16170298T patent/ES2701336T3/en active Active
- 2014-09-01 TW TW106125580A patent/TWI662856B/en active
- 2014-09-01 TW TW103130108A patent/TWI603646B/en active
- 2014-09-01 TW TW105113832A patent/TWI600337B/en active
- 2014-09-12 WO PCT/US2014/055517 patent/WO2015041960A1/en active Application Filing
- 2014-09-12 CN CN202110253624.4A patent/CN113015209A/en active Pending
- 2014-09-12 EP EP14845419.2A patent/EP3047671B1/en active Active
- 2014-09-12 WO PCT/US2014/055513 patent/WO2015041959A1/en active Application Filing
- 2014-09-12 US US14/912,587 patent/US20160205651A1/en not_active Abandoned
- 2014-09-12 CN CN201480045721.2A patent/CN105580414A/en active Pending
- 2014-09-12 EP EP14846321.9A patent/EP3047692B1/en active Active
- 2014-09-12 US US14/912,588 patent/US20160205601A1/en not_active Abandoned
- 2014-09-12 CN CN201480045560.7A patent/CN105474719A/en active Pending
- 2014-09-15 US US14/486,651 patent/US20150078154A1/en not_active Abandoned
- 2014-09-16 CN CN201480045628.1A patent/CN105612712B/en active Active
- 2014-09-16 CN CN201480045136.2A patent/CN105453456B/en active Active
- 2014-09-16 EP EP14846279.9A patent/EP3047599A4/en not_active Withdrawn
- 2014-09-16 EP EP14846425.8A patent/EP3047581B1/en active Active
- 2014-09-16 US US15/022,484 patent/US10003994B2/en active Active
- 2014-09-16 WO PCT/US2014/055837 patent/WO2015042035A1/en active Application Filing
- 2014-09-16 WO PCT/US2014/055751 patent/WO2015042004A1/en active Application Filing
- 2014-09-17 HU HUE14845454A patent/HUE038890T2/en unknown
-
2016
- 2016-01-08 US US14/991,696 patent/US9867078B2/en active Active
- 2016-04-14 JP JP2016081269A patent/JP6247333B2/en active Active
- 2016-07-05 US US15/202,264 patent/US10123231B2/en active Active
- 2016-09-02 HK HK16110486.2A patent/HK1222481A1/en unknown
- 2016-09-07 HK HK16110645.0A patent/HK1222502A1/en unknown
- 2016-10-03 HK HK16111509.3A patent/HK1223482A1/en unknown
- 2016-10-17 HK HK16111939.3A patent/HK1223755A1/en not_active IP Right Cessation
-
2017
- 2017-07-25 US US15/659,425 patent/US10306509B2/en active Active
- 2017-11-16 JP JP2017221364A patent/JP6471919B2/en active Active
-
2018
- 2018-10-05 US US16/153,584 patent/US11039334B2/en active Active
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030003953A1 (en) * | 2001-06-18 | 2003-01-02 | Comverse Network Systems Ltd. | Multi-user chat service in a cellular network |
US20070184856A1 (en) * | 2006-02-06 | 2007-08-09 | Narendranath Kudlu | Choice-based short messaging service in wireless networks and devices therefor |
US20110263278A1 (en) * | 2010-04-21 | 2011-10-27 | Research In Motion Limited | User Interface Methods And Apparatus For Use In Communicating Messages |
US20120257571A1 (en) * | 2011-04-07 | 2012-10-11 | Liao Ching-Yu | Method of Handling Signaling and Data Transmission for Machine-Type Communication |
US20140287752A1 (en) * | 2011-10-03 | 2014-09-25 | Lg Electronics Inc. | Mobility management entity handling sms-related signal |
US20140341041A1 (en) * | 2011-12-13 | 2014-11-20 | Panasonic Corporation | Device triggering and apn-based congestion control |
US20140370923A1 (en) * | 2012-02-01 | 2014-12-18 | Zte Corporation | Method and system for sending short message |
Non-Patent Citations (1)
Title |
---|
3GPP TS 29.338 v12.1.0 (2013-06), 3rd Generation Partnership Project; Technical Specification Group Core Network and TErminals; Diameter based protocols to support Short Message Service (SMS) capable Mobile Management Entities (MMEs) (Release 12) * |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11722859B1 (en) * | 2012-07-02 | 2023-08-08 | CSC Holdings, LLC | Service continuity and network preference for SMS services |
US20150119092A1 (en) * | 2013-01-16 | 2015-04-30 | Huawei Device Co., Ltd. | Trigger message sending method, device and system |
US9351135B2 (en) * | 2013-01-16 | 2016-05-24 | Huawei Device Co., Ltd. | Trigger message sending method, device and system |
US10326562B2 (en) | 2013-11-13 | 2019-06-18 | Samsung Electronics Co., Ltd. | Method and apparatus for controlling power headroom report and hybrid automatic retransmission in mobile communication system |
US10880052B2 (en) | 2013-11-13 | 2020-12-29 | Samsung Electronics Co., Ltd. | Method and apparatus for controlling power headroom report and hybrid automatic retransmission in mobile communication system |
CN106686561A (en) * | 2015-11-06 | 2017-05-17 | 阿尔卡特朗讯公司 | Support of mobile-terminated short message delivery for user equipment using power saving mechanism such as extended idle mode DRX |
US20170142679A1 (en) * | 2015-11-06 | 2017-05-18 | Bruno Landais | Support of mobile-terminated short message delivery for a user equipment using a power saving mechanism such as extended idle mode drx |
EP3166345B1 (en) * | 2015-11-06 | 2022-03-30 | Alcatel Lucent | Support of mobile-terminated short message delivery for a user equipment in extended idle mode drx |
US10652850B2 (en) * | 2015-11-06 | 2020-05-12 | Nokia Technologies Oy | Support of mobile-terminated short message delivery for a user equipment using a power saving mechanism such as extended idle mode DRX |
US11109198B2 (en) | 2015-12-02 | 2021-08-31 | Telefonaktiebolaget Lm Ericsson (Publ) | Enhancement of MT SM delivery for eDRX enabled mobile terminals |
US11641567B2 (en) | 2015-12-02 | 2023-05-02 | Telefonaktiebolaget Lm Ericsson (Publ) | Enhancement of MT SM delivery for EDRX enabled mobile terminals |
CN108293273A (en) * | 2015-12-02 | 2018-07-17 | 瑞典爱立信有限公司 | For the enhancing of the MT SM transmission for the mobile terminal for enabling eDRX |
US11140580B2 (en) | 2017-08-16 | 2021-10-05 | T-Mobile Usa, Inc. | Service enablement based on access network |
US10455453B2 (en) * | 2017-08-16 | 2019-10-22 | T-Mobile Usa, Inc. | Service enablement based on access network |
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20150078154A1 (en) | Congestion control for short message service in 3rd generation partnership project (3gpp) systems | |
US11863312B2 (en) | System, methods, and apparatuses for managing data rate for control plane optimization | |
US10624004B2 (en) | Serving node relocating method in wireless communication system and device for same | |
US11617072B2 (en) | Reliable data delivery over non-access stratum | |
US10779142B2 (en) | Method and device for controlling multipriority in wireless communication system | |
US9894464B2 (en) | Conveyance of application communication patterns from an external application server to a 3rd generation partnership project system | |
US20200137613A1 (en) | Machine type communication monitoring framework for 3gpp systems | |
US9225399B2 (en) | Method to enable optimization for small data in an evolved packet core (EPC) | |
KR102250738B1 (en) | Smooth ue transfer within an evolved packet core | |
EP3047674B1 (en) | Congestion control for short message service in 3rd generation partnership project (3gpp) systems | |
US9648515B2 (en) | Device triggering and APN-based congestion control | |
KR101830200B1 (en) | Device and method for controlling a device triggering in mobile operator netwokr | |
US9980103B2 (en) | Non-access stratum (NAS) transparent messaging | |
US20170280270A1 (en) | Method for controlling application related to third party server in wireless communication system and device for same | |
US9967905B2 (en) | Method and device for cancelling device trigger in wireless communication system | |
WO2020156460A1 (en) | Methods and nodes for ue-to-ue event monitoring | |
ES2975510T3 (en) | Method and entity to check the port consistency of the NIDD message |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTEL IP CORPORATION, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:JAIN, PUNEET K.;REEL/FRAME:033782/0352 Effective date: 20140912 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |