Methods for handling emergency short message services via Internet Protocol (Multimedia Subsystem) in mobile communications

By negotiating capabilities between the UE and the network and determining the access category and RRC establishment reason, the uncertainty of emergency SMS service under the 3GPP specification is resolved, and efficient transmission and resource optimization of emergency SMS are achieved.

CN123125904APending Publication Date: 2026-11-17MEDIATEK SINGAPORE PTE LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202580029169.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-11-15
Filing Date
2025-11-14
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Under the 3GPP specification, the behavior of UEs in providing Emergency Short Message Service (SMS) via IP is undefined, particularly regarding capability negotiation, access class and RRC establishment reasons, and congestion handling.

Method used

A series of solutions were proposed, including capability negotiation between the UE and the network, determining the access category and RRC establishment reason for emergency SMS, and performing congestion handling during the NAS backoff timer operation, and performing emergency SMS through IMS.

Benefits of technology

It resolves the uncertainties in UE emergency SMS processing, ensuring the effective transmission of emergency SMS and the rational utilization of network resources.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123125904A_ABST
    Figure CN123125904A_ABST
Patent Text Reader

Abstract

This paper describes a technique for handling Short Message Service (SMS) via the Internet Protocol (IP) Multimedia Subsystem (IMS) in mobile communications. The user equipment (UE) determines that an emergency SMS needs to be sent via IMS. The UE also determines one or both of the access class and radio resource control (RRC) establishment reason for the emergency SMS sent via IMS. Subsequently, the UE performs operations for the emergency SMS sent via IMS.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-references

[0002] This disclosure claims priority to Indian Patent Application No. 202421088427 (filed on 15 November 2024), the entire contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure generally relates to mobile communications, and more specifically, to processing a Short Message Service (SMS) via the Internet Protocol (IP) Multimedia Subsystem (IMS) in mobile communications. Background Technology

[0004] In wireless communications (such as mobile communications) under the current 3rd Generation Partnership Project (3GPP) specifications, as of the time of this disclosure, the behavior of a UE in providing Short Message Service (SMS) via IP remains undefined in several aspects. For example, regarding capability negotiation, UE behavior is undefined in how to process and / or indicate the capabilities of the UE or network to support emergency SMS functionality via IMS. Furthermore, regarding access categories and classes, when a UE detects or supports an emergency SMS via IMS, UE behavior is undefined in how to determine the access category and radio resource control (RRC) establishment reason for that emergency SMS via IMS. Additionally, regarding congestion handling, UE behavior is undefined when a UE needs to send an emergency SMS via IMS while a backoff timer is running (e.g., T3346, T3447, etc.).

[0005] Therefore, a solution is needed to handle emergency SMS messages via IMS in mobile communications. Summary of the Invention

[0006] The following abstract is for illustrative purposes only and is not intended to be limiting in any way. That is, the following abstract aims to introduce the concepts, key points, benefits, and advantages of the novel and non-obvious techniques described herein. Some embodiments will be further elaborated in the detailed description below. Therefore, the following abstract is not intended to identify the essential features of the claimed subject matter, nor is it intended to define the scope of the claimed subject matter.

[0007] The purpose of this disclosure is to propose solutions or strategies for addressing the problems described herein. More specifically, the various solutions proposed herein are believed to provide solutions for handling Short Message Service (SMS) via the Internet Protocol (IP) Multimedia Subsystem (IMS) in mobile communications. It is believed that implementations of one or more of the solutions proposed herein can solve or alleviate the aforementioned problems.

[0008] In one aspect, a method may involve a UE determining that an emergency SMS needs to be sent via IMS. The method may also involve the UE determining either or both of the access class and RRC establishment reason for the emergency SMS sent via IMS. The method may further involve the UE performing an operation for the emergency SMS sent via IMS.

[0009] In another aspect, one method may involve the UE communicating with the network to negotiate the capability to support emergency SMS via IMS. The method may also involve the UE performing an operation for the emergency SMS via IMS.

[0010] In another aspect, a method may involve the UE determining that either or both of the following are necessary: ​​(i) an emergency SMS needs to be sent via IMS, and (ii) a NAS backoff timer is running. The method may also involve the UE performing congestion handling operations for the emergency SMS sent via IMS in response to the determination.

[0011] It is worth noting that although the content described herein may be within the context of certain wireless access technologies, networks, and network topologies, such as 5G New Radio (NR) / Beyond Fifth-Generation (B5G) / 6G mobile communications, the proposed concepts, schemes, and any variations / derivatives thereof can be implemented, used, and implemented by other types of wireless access technologies, networks, and network topologies, such as, but not limited to, 4G / Long-Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, Internet of Things (IoT), Narrow Band Internet of Things (NB-IoT), Industrial Internet of Things (IIoT), Vehicle-to-Everything (V2X), and non-terrestrial network (NTN) communications. Therefore, the scope of this disclosure is not limited to the examples described herein. Attached Figure Description

[0012] The accompanying drawings are included in this disclosure to provide a further understanding of the disclosure and form part of it. The drawings illustrate embodiments of the disclosure and, together with the description, serve to explain the principles of the disclosure. It will be understood that the drawings are not necessarily drawn to scale, as some components may be shown out of proportion to their actual dimensions in order to clearly illustrate the concepts of the disclosure.

[0013] Figure 1 This is a schematic diagram of an example network environment in which various solutions and schemes according to this disclosure can be implemented.

[0014] Figure 2 Here is a block diagram of an example communication system based on the scheme proposed in this disclosure.

[0015] Figure 3 This is a flowchart of a second example process under the scheme proposed in this disclosure.

[0016] Figure 4 This is a flowchart of a second example process under the scheme proposed in this disclosure.

[0017] Figure 5 This is a flowchart of a second example process under the scheme proposed in this disclosure. Detailed Implementation

[0018] Detailed embodiments and implementations of the claimed subject matter are disclosed herein. However, it should be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matter, which may be implemented in various forms. This disclosure may take many different forms and should not be construed as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided to make the description of this disclosure exhaustive and complete, and to fully communicate the scope of this disclosure to those skilled in the art. In the following description, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

[0019] Overview

[0020] According to embodiments of this disclosure, various technologies, methods, schemes, and / or solutions relate to processing Short Message Service (SMS) via the Internet Protocol (IP) Multimedia Subsystem (IMS) in mobile communications. According to this disclosure, multiple possible solutions can be implemented individually or in combination. That is, although these possible solutions are described individually below, two or more of them can be implemented in some combination.

[0021] Figure 1 An example of a network environment 100 is provided, in which various solutions and schemes according to this disclosure can be implemented. Figures 2-5 Examples of implementing various proposed schemes in network environment 100 according to this disclosure are provided. The following description of the various proposed schemes is in conjunction with... Figures 1-5 It was carried out.

[0022] See Figure 1Network environment 100 involves UE 110 wirelessly communicating with wireless network 120 (e.g., a mobile network comprising non-terrestrial network (NTN) and terrestrial network (TN)) via terrestrial network node 125 (e.g., an evolved Node-B (eNB), a Next Generation Node-B (gNB), or a transmission / reception point (TRP)) and / or non-terrestrial network node 128 (e.g., a satellite) through terrestrial network node 125 and / or non-terrestrial network node 128. For example, terrestrial network node 125 and / or non-terrestrial network node 128 may form an NTN serving cell for wireless communication with UE 110. In some implementations, UE 110 may be an IoT device, such as an NB-IoT UE or an enhanced machine-type communication (eMTC) UE (e.g., a bandwidth-reduced low complexity (BL) UE or a coverage enhancement (CE) UE). In this communication environment, UE 110, network 120, terrestrial network node 125 and non-terrestrial network node 128 can implement various schemes related to handling emergency SMS via IMS, as described below.

[0023] It is worth noting that although various proposed solutions may be described separately or individually below, in actual implementation, some or all of the proposed solutions may be used in combination or implemented in combination in other ways. Of course, each proposed solution may also be used or implemented individually or separately. In addition, as used herein, "lower layer" may refer to layers below the radio resource control (RRC) layer in the 5GMM protocol stack, such as the packet data convergence protocol (PDCP) layer, radio link control (RLC) layer, medium access control (MAC) layer, physical (PHY) layer, etc.

[0024] According to the proposed scheme of this disclosure, in terms of capability negotiation, the UE (e.g., UE 110) and the network (e.g., wireless network 120) can negotiate and / or indicate support for emergency SMS functionality via IMS using one or more of the following mechanisms. In the first mechanism, the UE can send new / existing bits in existing information elements (IEs) of Mobility Management (MM) (e.g., 6th Generation Mobility Management (6GMM), 5GMM, Evolved Packet System (EPS) Mobility Management (EMM), etc.) or new IEs in existing / new messages to the network (e.g., via registration request, service request, attach request, etc.). In the second mechanism, if the network supports emergency SMS via IMS, the network can indicate support for the UE in existing / new bits / new IEs (e.g., network function support IEs), or in existing / new messages (e.g., via registration acceptance, service acceptance, configuration update command, attach acceptance, etc.). In the third mechanism, the UE can be configured to support emergency SMS via IMS, and / or if the UE is configured / instructed (e.g., by the network) to enable support for this function through a Management Object (MO) configuration mechanism or by information stored in the Universal Subscriber Identity Module (USIM) associated with the UE, then the UE can support the emergency SMS via IMS function. If this function is enabled through MO configuration or USIM or security packets, the UE can use emergency SMS via IMS. Furthermore, support for emergency SMS via IMS can be passed to the UE through USIM configuration, a Management Object (e.g., a non-access stratum (NAS) MO), or security packets (e.g., SMS). In the fourth mechanism, the network can send support indications using access stratum (AS) messages (e.g., existing or new system information blocks (SIBs) or master information blocks (MIBs) from the camped cell).

[0025] According to the proposed scheme of this disclosure, regarding access category and class, when a UE (e.g., UE 110) determines that it needs to send an emergency SMS via IMS (e.g., by receiving a request from an upper layer regarding an emergency SMS via IMS and / or the UE attempting to send an emergency SMS via IMS), the UE may perform one or more of the following operations. Under the proposed scheme, the type of access attempt can be "emergency" or a newly introduced access attempt for an emergency SMS via IMS. Alternatively, the access category can be 2 (=emergency) or a newly introduced access category for an emergency SMS via IMS. Alternatively, the RRC establishment reason can be emergency or a newly introduced RRC establishment reason for an emergency SMS via IMS. Alternatively, the emergency SMS service via IMS can be handled / considered in a manner similar to emergency service. Alternatively, if the access category can be 2 (=emergency) or the newly introduced access category for an emergency SMS via IMS is determined to be unblocked, or the blockage is mitigated or lifted, the UE is allowed to initiate the procedure for SMS via IMS. Under the proposed scheme, when the 5GMM receives a request from the upper layer to send an emergency SMS via IMS, the UE can consider the emergency service procedure to have been initiated. Furthermore, when the emergency SMS procedure via IMS ends, resources are released, the signaling connection established for the emergency SMS via IMS is released, or the UE enters idle mode, the UE can consider the emergency service procedure to have stopped.

[0026] According to the proposed scheme of this disclosure, regarding congestion handling, when a UE (e.g., UE 110) receives a request from an upper layer for an emergency SMS via IMS and / or the UE attempts to send an emergency SMS via IMS and / or a NAS backoff timer (e.g., T3346, T3447, etc.) is running, the UE may perform one or more of the following operations for the emergency SMS via IMS. For example, allowing the UE to establish a (NAS) signaling connection. Alternatively, the UE may also be allowed to send xMM (e.g., 6GMM, 5GMM, or EMM) messages to the network (e.g., wireless network 120). In this case, the xMM message may be, for example, an uplink (UL) NAS transport message, a registration request message, a service request message, an attach request message, etc. Alternatively, the UE can notify the upper layer of the process failure so that the upper layer can try to send an SMS through other domains, such as the circuit-switching (CS) domain or the IP core access network (IP-CAN) (e.g., WiFi).

[0027] Example Implementation

[0028] Figure 2 An example communication system 200 according to an embodiment of the present disclosure is shown, having at least one example device 210 and one example device 220. Each of devices 210 and 220 can perform various functions to implement the schemes, techniques, processes, and methods described herein, relating to handling emergency SMS via IMS in mobile communications, including the various schemes described above regarding various proposed designs, concepts, schemes, systems, and methods, including network environment 100, and the processes described below.

[0029] Each of devices 210 and 220 can be part of an electronic device, which can be a network device or UE (e.g., UE 110), such as a portable or mobile device, wearable device, in-vehicle device or vehicle, wireless communication device, or computing device. For example, each of devices 210 and 220 can be implemented in a smartphone, smartwatch, personal digital assistant, electronic control unit (ECU) in a vehicle, digital camera, or computing device such as a tablet, laptop, or notebook computer. Each of devices 210 and 220 can also be part of a machine-type device, which can be an IoT device, such as a non-mobile or fixed device, home appliance, roadside unit (RSU), wired communication device, or computing device. For example, each of devices 210 and 220 can be implemented in a smart thermostat, smart refrigerator, smart door lock, wireless speaker, or home control center. When implemented as network devices, device 210 and / or device 220 may be implemented in an eNB in ​​an LTE, LTE-Advanced, or LTE-Advanced Pro network, or in a gNB or TRP in a 5G, NR, or IoT network.

[0030] In some implementations, each of devices 210 and 220 may be implemented as one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more complex instruction-set computing (CISC) processors, or one or more reduced instruction-set computing (RISC) processors. In the various embodiments described above, each of devices 210 and 220 may be implemented as a network device or a UE. Each of devices 210 and 220 may include... Figure 2 At least some components are shown, such as processor 212 and processor 222. Each of devices 210 and 220 may also include one or more other components unrelated to the proposed solutions of this disclosure (e.g., internal power supply, display device, and / or user interface device); therefore, for the sake of brevity, Figure 2 Such components of devices 210 and 220 are not shown and are not described below.

[0031] In one aspect, each of processors 212 and 222 may be implemented as one or more single-core processors, one or more multi-core processors, or one or more CISC or RISC processors. That is, although the singular term "processor" is used herein to refer to processors 212 and 222, in some embodiments of this disclosure, each of processors 212 and 222 may include multiple processors, and in other embodiments may include a single processor. In another aspect, each of processors 212 and 222 may be implemented in hardware (and optionally firmware) having electronic components, including but not limited to one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors, and / or one or more varactor diodes, which are configured and arranged according to this disclosure to achieve a particular purpose. In other words, in at least some embodiments, each of processors 212 and 222 is a dedicated machine specifically designed, arranged, and configured to perform a particular task, including handling emergency SMS-related tasks via IMS in mobile communications according to various embodiments of this disclosure.

[0032] In some embodiments, device 210 may further include a transceiver 216 connected to processor 212. Transceiver 216 is capable of wirelessly transmitting and receiving data. In some embodiments, transceiver 216 is capable of wireless communication with different types of wireless networks using different radio access technologies (RATs). In some embodiments, transceiver 216 may be equipped with multiple antenna ports (not shown), such as four antenna ports. That is, transceiver 216 may be equipped with multiple transmit antennas and multiple receive antennas for multiple-input multiple-output (MIMO) wireless communication. In some embodiments, device 220 may further include a transceiver 226 connected to processor 222. Transceiver 226 may include a transceiver capable of wirelessly transmitting and receiving data. In some embodiments, transceiver 226 is capable of wireless communication with different types of UE / wireless networks using different RATs. In some embodiments, transceiver 226 may be equipped with multiple antenna ports (not shown), such as four antenna ports. That is, transceiver 226 may be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communication.

[0033] In some embodiments, device 210 may further include a memory 214 coupled to and accessible by processor 212 for storing data. In some embodiments, device 220 may further include a memory 224 coupled to and accessible by processor 222 for storing data. Each of memory 214 and memory 224 may include a random-access memory (RAM), such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM), and / or zero-capacitor RAM (Z-RAM). Alternatively, or additionally, each of memory 214 and memory 224 may include a read-only memory (ROM), such as a mask ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), and / or electrically erasable programmable ROM (EEPROM). Alternatively, each of memories 214 and 224 may include a non-volatile random-access memory (NVRAM), such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM), and / or phase-change memory.

[0034] Each of devices 210 and 220 may be a communication entity capable of communicating with each other in accordance with various proposed schemes of this disclosure. For illustrative purposes only and without limitation, the following description, in the context of example flows 300, 400, and 500, provides the capabilities of device 210 as a UE (e.g., UE 110) and device 220 as a network node (e.g., network node 125) of a network (e.g., wireless network 120 as a 5G / NR mobile network).

[0035] Explanatory process

[0036] Figure 3An example flow 300 according to an embodiment of this disclosure is illustrated. Flow 300 may represent one aspect of implementing the various proposed designs, concepts, schemes, systems, and methods described above. More specifically, flow 300 may represent one aspect of the proposed concepts and schemes of this disclosure regarding handling emergency SMS via IMS in mobile communications. Flow 300 may include one or more operations, actions, or functions, as shown in one or more flow blocks. Although shown as discrete flow blocks, the individual flow blocks of flow 300 may be divided into more flow blocks, merged into fewer flow blocks, or omitted, depending on the desired implementation. Furthermore, the flow blocks / sub-flow blocks of flow 300 may be arranged according to... Figure 3 The process can be executed in the order shown, or in a different order. Furthermore, one or more process blocks / sub-process blocks of process 300 can be executed repeatedly or iteratively. Process 300 can be implemented by devices 210 and 220 and any variations thereof. For illustrative purposes only and without limitation, process 300 is described below in the context of device 210 as a UE (e.g., UE 110) and device 220 as a communication entity (e.g., a network node of a network (e.g., wireless network 120) such as a non-terrestrial network node 128 or a terrestrial network node 125)). Process 300 may begin at process block 310.

[0037] At 310, process 300 may involve the processor 212 of device 210 (as UE 110) determining that an emergency SMS via IMS is required. Process 300 can proceed from 310 to 320.

[0038] At 320, process 300 may involve processor 212 establishing a signaling connection via transceiver 216 for the emergency SMS via IMS. Process 300 can proceed from 320 to 330.

[0039] At 330, process 300 may involve processor 212 determining either or both of the access category and RRC establishment reason for the emergency SMS via IMS. Process 300 may proceed from 330 to 340.

[0040] At 340, process 300 may involve processor 212 performing operations via transceiver 216 with a network (e.g., via device 220 as a non-terrestrial network node 128 or a wireless network 120 of terrestrial network 125) for the emergency SMS via IMS.

[0041] In some implementations, when determining the access category, process 300 may involve processor 212 determining that the type of the access attempt is “emergency” or that the access attempt indicates that the access attempt is for the emergency SMS via IMS.

[0042] In some implementations, when determining the access category, process 300 may involve processor 212 determining that the access category is 2 (indicating emergency), or that the access category indicates that the UE is establishing a signaling connection for the emergency SMS via IMS.

[0043] In some implementations, when determining the RRC establishment reason, process 300 may involve processor 212 setting the RRC establishment reason to an emergency call or setting the RRC establishment reason to indicate that the UE is establishing a signaling connection for the emergency SMS via IMS.

[0044] In some implementations, establishing a signaling connection for the emergency SMS via IMS can be handled in a manner similar to one or more other emergency services.

[0045] In some implementations, when performing the operation, process 300 may involve processor 212 responding to: (a) the access category is 2 (indicating emergency); or (b) a new access category for the emergency SMS via IMS is determined to be unblocked; or (c) the block on the emergency SMS via IMS is lifted, initiating a process for the emergency SMS via IMS.

[0046] Figure 4 An example flow 400 according to an embodiment of this disclosure is illustrated. Flow 400 may represent one aspect of implementing the various proposed designs, concepts, schemes, systems, and methods described above. More specifically, flow 400 may represent one aspect of the proposed concepts and schemes of this disclosure regarding handling emergency SMS via IMS in mobile communications. Flow 400 may include one or more operations, actions, or functions, as shown in one or more flow blocks. Although shown as discrete flow blocks, the individual flow blocks of flow 400 may be divided into more flow blocks, merged into fewer flow blocks, or omitted, depending on the desired implementation. Furthermore, the flow blocks / sub-flow blocks of flow 400 may be arranged according to... Figure 4 The process can be executed in the order shown, or in a different order. Furthermore, one or more process blocks / sub-process blocks of process 400 can be executed repeatedly or iteratively. Process 400 can be implemented by devices 210 and 220 and any variations thereof. For illustrative purposes only and without limitation, process 400 is described below in the context of device 210 as a UE (e.g., UE 110) and device 220 as a communication entity (e.g., a network node of a network (e.g., wireless network 120) such as a non-terrestrial network node 128 or a terrestrial network node 125). Process 400 may begin at process block 410.

[0047] At 410, process 400 may involve the processor 212 of device 210 (as UE 110) communicating with a network (e.g., via device 220 as a non-terrestrial network node 128 or a terrestrial network 125 wireless network 120) through transceiver 216 to negotiate the capability to support emergency SMS via IMS. Process 400 may proceed from 410 to 420.

[0048] At 420, process 400 may involve processor 212 communicating with the network via transceiver 216 to perform operations for the emergency SMS via IMS.

[0049] In some implementations, when communicating with the network, process 400 may involve processor 212 transmitting to the network an indication of the UE's support for the emergency SMS via IMS, through new or existing bits in an existing IE of the MM, or a new IE in an existing or new message. In some implementations, the MM may include a 6GMM, a 5GMM, or an EMM.

[0050] In some implementations, when communicating with a network, process 400 may involve processor 212 receiving from the network, via existing or new bits or a new IE in an existing or new message, an indication of the network's support for the emergency SMS via IMS. In some implementations, the existing or new message may include a registration acceptance message, a service acceptance message, a configuration update command message, or an attach acceptance message.

[0051] In some implementations, when communicating with the network, process 400 may involve processor 212 receiving from the network an instruction from the network regarding support for the emergency SMS via IMS via an AS message from the camped cell. In some implementations, the AS message may include an SIB or a MIB.

[0052] In some implementations, when performing the operation, process 400 may involve processor 212 using the emergency SMS via IMS in response to the UE being configured, enabled, or instructed to support the emergency SMS via IMS.

[0053] In some implementations, process 400 may also involve processor 212 obtaining functional support for the emergency SMS via IMS from USIM configuration, MO, or security group.

[0054] Figure 5An example flow 500 according to an embodiment of this disclosure is illustrated. Flow 500 may represent one aspect of implementing the various designs, concepts, schemes, systems, and methods proposed above. More specifically, flow 500 may represent one aspect of the concepts and schemes proposed in this disclosure regarding handling emergency SMS via IMS in mobile communications. Flow 500 may include one or more operations, actions, or functions, as shown in one or more flow blocks. Although shown as discrete flow blocks, the individual flow blocks of flow 500 may be divided into more flow blocks, merged into fewer flow blocks, or omitted, depending on the desired implementation. Furthermore, the flow blocks / sub-flow blocks of flow 500 may be arranged in... Figure 5 The process can be executed in the order shown, or in a different order. Furthermore, one or more process blocks / sub-process blocks of process 500 can be executed repeatedly or iteratively. Process 500 can be implemented by or in devices 210 and 220 and any variations thereof. For illustrative purposes only and without limitation, the following process 500 is described in the context of device 210 as a UE (e.g., UE 110) and device 220 as a communication entity (e.g., a network node of a network (e.g., wireless network 120) such as a non-terrestrial network node 128 or a terrestrial network node 125). Process 500 may begin at process block 510.

[0055] At 510, process 500 may involve processor 212 of device 210 (as UE 110) determining either or both of the following: (i) an emergency SMS is required via IMS, and (ii) the NAS backoff timer is running. Process 500 may continue from 510 to 520.

[0056] At 520, process 500 may involve processor 212 responding to a determination operation by performing an operation via transceiver 216 for congestion handling of the emergency SMS via IMS.

[0057] In some implementations, the NAS backoff timer may include at least one of T3346 and T3447.

[0058] In some implementations, during the execution of the operation, process 500 may involve processor 212 establishing a NAS signaling connection.

[0059] In some implementations, during operation, process 500 may involve processor 212 transmitting an MM message to the network. In some implementations, the MM message includes a UL NAS transmission message, a registration request message, a service request message, or an attach request message. In some implementations, the MM may include a 6GMM, a 5GMM, or an EMM.

[0060] In some implementations, during operation, process 500 may involve processor 212 notifying upper-layer process failure so that the upper layer may attempt to send SMS via another domain (e.g., CS domain) or IP-CAN (e.g., WiFi).

[0061] Additional notes

[0062] The topics described herein sometimes demonstrate different components contained within or connected to other different components. It should be understood that such architectures are merely examples, and many other architectures can actually be implemented to achieve the same functionality. Conceptually, any arrangement of components to achieve the same functionality is effectively “associated” to achieve the desired function. Therefore, any two components combined in this document to achieve a specific function can be considered “associated with each other” to achieve the desired function, regardless of the architecture or intermediate components. Similarly, any two components so associating can be considered “operably connected” or “operably coupled” to achieve the desired function, and any two components that can be so associating can also be considered “operably coupled” to achieve the desired function. Specific examples of being operablely coupled include, but are not limited to, physically matable and / or physically interactive components and / or wirelessly interactive and / or logically interactive components.

[0063] Furthermore, regarding the use of almost all plural and / or singular terms in this document, those skilled in the art can appropriately convert plural to singular and / or singular to plural depending on the context and / or application. For clarity, various singular / plural permutations are explicitly listed herein.

[0064] Furthermore, those skilled in the art will understand that terms commonly used herein, particularly in appended claims, such as the body portion of appended claims, are generally considered "open-ended" terms. For example, the word "comprising" should be interpreted as "comprising but not limited to," the word "having" should be interpreted as "having at least," and the word "including" should be interpreted as "including but not limited to," etc. Those skilled in the art will also further understand that if a specific quantity is introduced in a claim intentionally, that intention will be explicitly stated in the claim; if no such statement is made, then that intention does not exist. For example, for ease of understanding, the appended claims below may contain the use of the introductory phrases "at least one" and "one or more" to introduce the content of the claim. However, the use of such phrases should not be interpreted as meaning that when the content of a claim is introduced by the indefinite article "a" or "an," any specific claim containing that content is limited to only one embodiment containing that content, even if the same claim contains the introductory phrase "one or more" or "at least one" and indefinite articles such as "a" or "an," for example, "a" and / or "an" should be interpreted as "at least one" or "one or more"; the same applies to the case where the content of a claim is introduced by a definite article. Furthermore, even if a specific quantity is explicitly stated in the claims, those skilled in the art will recognize that such a statement should be interpreted as at least the stated quantity. For example, stating "two items" alone, without further modification, means at least two items, or two or more items. Additionally, when using conventions such as "at least one of A, B, and C," such structures are generally intended for those skilled in the art to understand the meaning of the convention. For example, "a system having at least one of A, B, and C" includes, but is not limited to, systems having only A, only B, only C, both A and B, both A and C, both B and C, and systems having both A, B, and C. When using conventions such as "at least one of A, B, and C," such structures are generally intended for those skilled in the art to understand the meaning of the convention. For example, "a system having at least one of A, B, and C" includes, but is not limited to, systems having only A, only B, only C, both A and B, both A and C, both B and C, and systems having both A, B, and C. Those skilled in the art will further understand that virtually any disjunctive words and / or phrases appearing in the specification, claims, or drawings, when presenting two or more alternative terms, should be understood to include one, any, or both terms. For example, the phrase “A or B” should be understood to include the possibility of “A” or “B” or “A and B”.

[0065] As can be seen from the foregoing, the various embodiments of this disclosure have been described for illustrative purposes, and various modifications can be made without departing from the scope and spirit of this disclosure. Therefore, the various embodiments disclosed herein are not intended to be limiting, and the true scope and spirit are defined by the following claims.

Claims

1. A method comprising: The user equipment's processor determines that an emergency short message service is needed via the Internet Protocol Multimedia Subsystem. The processor establishes a signaling connection for the emergency short message service via the Internet Protocol Multimedia Subsystem; The processor determines either or both of the access category and the reason for establishing Radio Resource Control for the Emergency Short Message Service via the Internet Protocol Multimedia Subsystem; and The processor performs operations for the emergency short message service via the Internet Protocol Multimedia Subsystem.

2. The method of claim 1, wherein determining the access category includes determining that the type of the access attempt is "emergency" or that the access attempt indicates that the access attempt is for the emergency short message service via Internet Protocol (Internet Protocol Multimedia Subsystem).

3. The method of claim 1, wherein determining the access category includes determining the access category as 2 (indicating emergency), or the access category indicating that the user equipment is establishing the signaling connection for the emergency short message service via the Internet Protocol Multimedia Subsystem.

4. The method of claim 1, wherein determining the cause of establishment of the radio resource control includes setting the cause of establishment of the radio resource control as an emergency call or setting the cause of establishment of the radio resource control to indicate that the user equipment is establishing the signaling connection for the emergency short message service via the Internet Protocol Multimedia Subsystem.

5. The method of claim 1, wherein the signaling connection for the emergency short message service of the Internet Protocol Multimedia Subsystem is established to be processed in a manner similar to one or more other emergency services.

6. The method of claim 1, wherein performing the operation includes initiating a process for the emergency short message service via the Internet Protocol Multimedia Subsystem in response to: The access category is 2 (indicating emergency); or The new access category for this emergency short message service via the Internet Protocol Multimedia Subsystem has been determined to be unblocked; or The block on this emergency short message service via the Internet Protocol Multimedia Subsystem has been lifted.

7. A method comprising: The user equipment's processor communicates with the network to negotiate the capability to support emergency short message service via the Internet Protocol Multimedia Subsystem; as well as The processor performs operations for the emergency short message service via the Internet Protocol Multimedia Subsystem.

8. The method of claim 7, wherein communication with the network comprises transmitting to the network an indication of the user equipment's support for the emergency short message service via the Internet Protocol Multimedia Subsystem through new or existing bits in existing information elements of mobility management, or new information elements in existing or new messages.

9. The method of claim 8, wherein the mobility management includes sixth-generation mobility management, fifth-generation mobility management, or evolved packet system mobility management.

10. The method of claim 7, wherein communication with the network includes receiving from the network an indication of the network's support for the emergency short message service via the Internet Protocol Multimedia Subsystem, either via existing or new bits or new information elements in existing or new messages.

11. The method of claim 10, wherein the existing or new message includes a registration acceptance message, a service acceptance message, a configuration update command message, or an attach acceptance message.

12. The method of claim 7, wherein communication with the network includes receiving from the network an indication of the network's support for the emergency short message service via the Internet Protocol Multimedia Subsystem via an access layer message from the stationary cell.

13. The method of claim 12, wherein the access layer message includes a system information block or a master information block.

14. The method of claim 7, wherein performing the operation includes using the Emergency Short Message Service via Internet Protocol Multimedia Subsystem in response to the user equipment being configured, enabled, or instructed to support the Emergency Short Message Service via Internet Protocol Multimedia Subsystem.

15. The method of claim 14, further comprising: The processor obtains functional support for the emergency short message service via the Internet Protocol Multimedia Subsystem from the configuration, management objects, or security groups of the general user identity module.

16. A method comprising: The processor of the user equipment determines one or both of the following: Emergency SMS service is required via the Internet Protocol Multimedia Subsystem (IPS). The non-access stratum backoff timer is running; as well as The processor, in response to a determination operation, performs an operation to handle congestion in the emergency short message service via the Internet Protocol Multimedia Subsystem.

17. The method of claim 16, wherein the non-access stratum backoff timer comprises at least one of T3346 and T3447.

18. The method of claim 16, wherein performing the operation includes establishing a non-access stratum signaling connection.

19. The method of claim 16, wherein performing the operation includes transmitting a mobility management message to the network, wherein the mobility management message includes an uplink non-access stratum transmission message, a registration request message, a service request message, or an attach request message, and the mobility management includes sixth-generation mobility management, fifth-generation mobility management, or evolved packet system mobility management.

20. The method of claim 16, wherein performing the operation includes notifying the upper-layer process of failure so that the upper layer may attempt to access the short message service through another domain or Internet Protocol Core access network.