WO2020159490A1

WO2020159490A1 - Optimization in timely short message service delivery

Info

Publication number: WO2020159490A1
Application number: PCT/US2019/015850
Authority: WO
Inventors: Saurabh Khare; Devaki Chandramouli; Ulrich Wiehe
Original assignee: Nokia Technologies Oy; Nokia USA Inc
Current assignee: Nokia Technologies Oy; Nokia USA Inc
Priority date: 2019-01-30
Filing date: 2019-01-30
Publication date: 2020-08-06
Anticipated expiration: 2021-07-30

Abstract

Method, apparatuses, and computer program product for overhead reduction are provided. One method may include receiving a failure report from a core network element. The method may also include sending a response to the failure report, the response including a reset-identification identifying the subscriber. In addition, the method may include performing a network element restart or a restart due to various reasons in the failure report, and sending a reset message to the core network element. Further, receipt of the reset message may trigger the core network element to reattempt delivery of the message to the subscriber.

Description

TITLE:

OPTIMIZATION IN TIMELY SHORT MESSAGE SERVICE DELIVERY

FIELD:

[0001] Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) radio access technology or new radio (NR) access technology, or other communications systems. For example, certain embodiments may relate to apparatuses, systems, and/or methods for optimizing timely short message service (SMS) delivery after a home subscriber server (HSS), home location register (HLR, or unified data management (UDM) restart.

BACKGROUND:

[0002] Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E- UTRAN), LTE-Advanced (LTE-A), MulteFire, LTE-A Pro, and/or fifth generation (5G) radio access technology or new radio (NR) access technology. Fifth generation (5G) wireless systems refer to the next generation (NG) of radio systems and network architecture. 5G is mostly built on a new radio (NR), but the 5G (or NG) network can also build on E-UTRA radio. It is estimated that NR will provide bitrates on the order of 10-20 Gbit/s or higher, and will support at least enhanced mobile broadband (eMBB) and ultra-reliable low-latency- communication (URLLC) as well as massive machine type communication (mMTC). NR is expected to deliver extreme broadband and ultra-robust, low latency connectivity and massive networking to support the Internet of Things (IoT). With IoT and machine-to-machine (M2M) communication becoming more widespread, there will be a growing need for networks that meet the needs of lower power, low data rate, and long battery life. It is noted that, in 5G, the nodes that can provide radio access functionality to a user equipment (i.e., similar to Node B in UTRAN or eNB in LTE) may be named gNB when built on NR radio and may be named NG-eNB when built on E-UTRA radio.

SUMMARY

[0003] One embodiment may be directed to a method. The method may include receiving a failure report from a core network element indicating that delivery of a message to a subscriber has failed. The method may also include sending a response to the failure report to the core network element, the response including a reset-identification identifying the subscriber. The method may further include performing a network element restart or a restart due to various reasons in the failure report, and sending a reset message to the core network element indicating that stored data corresponding to the subscriber has been lost. In an example embodiment, the reset message may include the reset-identification. In another example embodiment, receipt of the reset message may trigger the core network element to reattempt delivery of the message to the subscriber according to the reset-identification.

[0004] Another example embodiment may be directed to an apparatus. The apparatus may include means for receiving a failure report from a core network element indicating that delivery of a message to a subscriber has failed. The apparatus may also include means for sending a response to the failure report to the core network element, the response including a reset-identification identifying the subscriber. The apparatus may further include means for performing a network element restart or a restart due to various reasons in the failure report, and sending a reset message to the core network element indicating that stored data corresponding to the subscriber has been lost. In an example embodiment, the reset message may include the reset-identification. In another example embodiment, receipt of the reset message may trigger the core network element to reattempt delivery of the message to the subscriber according to the reset-identification.

[0005] Another example embodiment may be directed to an apparatus which may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus at least to receive a failure report from a core network element indicating that delivery of a message to a subscriber has failed. The at least one memory and the computer program code may further be configured to, with the at least one processor, cause the apparatus at least to send a response to the failure report to the core network element, the response including a reset-identification identifying the subscriber. The at least one memory and the computer program code may further be configured to, with the at least one processor, cause the apparatus at least to perform a network element restart or a restart due to various reasons in the failure report, and sending a reset message to the core network element indicating that stored data corresponding to the subscriber has been lost. In an example embodiment, the reset message may include the reset-identification. In another example embodiment, receipt of the reset message may trigger the core network element to reattempt delivery of the message to the subscriber according to the reset- identification.

[0006] In accordance with some example embodiments, a non-transitory computer readable medium can be encoded with instructions that may, when executed in hardware, perform a method. The method may receive a failure report from a core network element indicating that delivery of a message to a subscriber has failed. The method may also send a response to the failure report to the core network element, the response including a reset-identification identifying the subscriber. The method may further perform a network element restart or a restart due to various reasons in the failure report, and send a reset message to the core network element indicating that stored data corresponding to the subscriber has been lost. In an example embodiment, the reset message may include the reset- identification. In another example embodiment, receipt of the reset message may trigger the core network element to reattempt delivery of the message to the subscriber according to the reset-identification.

[0007] In accordance with some example embodiments, a computer program product may perform a method. The method may receive a failure report from a core network element indicating that delivery of a message to a subscriber has failed. The method may also send a response to the failure report to the core network element, the response including a reset-identification identifying the subscriber. The method may further perform a network element restart or a restart due to various reasons in the failure report, and send a reset message to the core network element indicating that stored data corresponding to the subscriber has been lost. In an example embodiment, the reset message may include the reset-identification. In another example embodiment, receipt of the reset message may trigger the core network element to reattempt delivery of the message to the subscriber according to the reset-identification.

[0008] In accordance with some example embodiments, an apparatus may include circuitry configured to receive a failure report from a core network element indicating that delivery of a message to a subscriber has failed. The circuitry may also be configured to send a response to the failure report to the core network element, the response including a reset-identification identifying the subscriber. The circuitry may further be configured to perform a network element restart or a restart due to various reasons in the failure report, and send a reset message to the core network element indicating that stored data corresponding to the subscriber has been lost. In an example embodiment, the reset message may include the reset-identification. In another example embodiment, receipt of the reset message may trigger the core network element to reattempt delivery of the message to the subscriber according to the reset-identification.

[0009] In accordance with some example embodiments, a method may include sending a failure report to a network element indicating that delivery of a message to a subscriber has failed. The method may also include receiving a response to the failure report, the response including a reset-identification identifying the subscriber. The method may further include receiving a reset message from the network element indicating that stored data corresponding to the subscriber has been lost, the reset message also including the reset- identification. In addition, the method may include in response to the reset message, reattempting to deliver the message to the subscriber according to the reset-identification.

[00010] In accordance with some example embodiments, an apparatus may include means for sending a failure report to a network element indicating that delivery of a message to a subscriber has failed. The apparatus may also include means for receiving a response to the failure report, the response comprising a reset-identification identifying the subscriber. The apparatus may further include means for receiving a reset message from the network element indicating that stored data corresponding to the subscriber has been lost, the reset message also including the reset-identification. The apparatus may also include means for, in response to the reset message, reattempting to deliver the message to the subscriber according to the reset-identification.

[00011] In accordance with some example embodiments, an apparatus may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus at least to send a failure report to a network element indicating that delivery of a message to a subscriber has failed. The at least one memory and the computer program code may also be configured to, with the at least one processor, cause the apparatus at least to receive a response to the failure report, the response including a reset-identification identifying the subscriber. The at least one memory and the computer program code may also be configured to, with the at least one processor, cause the apparatus at least to receive a reset message from the network element indicating that stored data corresponding to the subscriber has been lost, the reset message also including the reset-identification. The at least one memory and the computer program code may also be configured to, with the at least one processor, cause the apparatus at least to, in response to the reset message, reattempt to deliver the message to the subscriber according to the reset-identification.

[00012] In accordance with some example embodiments, a non-transitory computer readable medium can be encoded with instructions that may, when executed in hardware, perform a method. The method may send a failure report to a network element indicating that delivery of a message to a subscriber has failed. The method may also receive a response to the failure report, the response including a reset-identification identifying the subscriber. The method may further receive a reset message from the network element indicating that stored data corresponding to the subscriber has been lost, the reset message also including the reset-identification. In addition, the method may, in response to the reset message, reattempt to deliver the message to the subscriber according to the reset-identification.

[00013] In accordance with some example embodiments, a computer program product may perform a method. The method may send a failure report to a network element indicating that delivery of a message to a subscriber has failed. The method may also receive a response to the failure report, the response including a reset-identification identifying the subscriber. The method may further receive a reset message from the network element indicating that stored data corresponding to the subscriber has been lost, the reset message also including the reset-identification. In addition, the method may, in response to the reset message, reattempt to deliver the message to the subscriber according to the reset-identification.

[00014] In accordance with some embodiments, an apparatus may include circuitry configured to send a failure report to a network element indicating that delivery of a message to a subscriber has failed. The circuitry may also be configured to receive a response to the failure report, the response including a reset-identification identifying the subscriber. The circuitry may further be configured to receive a reset message from the network element indicating that stored data corresponding to the subscriber has been lost, the reset message also including the reset-identification. In addition, the circuitry may, in response to the reset message, be configured to reattempt to deliver the message to the subscriber according to the reset-identification.

BRIEF DESCRIPTION OF THE DRAWINGS:

[00015] F or proper understanding of the invention, reference should be made to the accompanying drawings, wherein:

[00016] FIG. 1 illustrates an example signal flow, according to an example embodiment.

[00017] FIG. 2 illustrates another example signal flow, according to an example embodiment.

[00018] FIG. 3 illustrates an example flow diagram of a method, according to an embodiment.

[00019] FIG. 4 illustrates an example flow diagram of another method, according to an example embodiment.

[00020] FIG. 5a illustrates a block diagram of an apparatus according to an example embodiment

[00021] FIG. 5b illustrates a block diagram of another apparatus according to an example embodiment.

DETAILED DESCRIPTION

[0022] It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for optimizing timely short message service (SMS) delivery, is not intended to limit the scope of certain embodiments but is representative of selected example embodiments.

[0023] The features, structures, or characteristics of example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, the usage of the phrases “certain embodiments,”“an example embodiment,”“some embodiments,” or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment. Thus, appearances of the phrases“in certain embodiments,”“an example embodiment,”“in some embodiments,”“in other embodiments,” or other similar language, throughout this specification do not necessarily all refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments.

[0024] Additionally, if desired, the different functions or steps discussed below may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the described functions or steps may be optional or may be combined. As such, the following description should be considered as merely illustrative of the principles and teachings of certain example embodiments, and not in limitation thereof.

[0025] Short message service has been described in 3GPP 23040, and may be applicable for 2G, 3G, 4G, and 5G. Whenever a home subscriber server (HSS), home location register (HLR), or unified data management (UDM) function is restarted while mobile not readable flags (MNRF) and short message service center (SMSC) addresses (also known as message waiting data (MWD data)) are stored in DB, the HSS/HLR/UDM may lose the MNRF flags and/or SMSC addresses. Due to this, when a subscriber becomes reachable, the HSS/HLR/UDM may not inform the SMSC that the subscriber is reachable again. Therefore the SMSC may not reattempt SMS delivery for the non- reachable subscriber.

[0026] A similar problem exists for cloud-based solutions. For example, in cloud-based solutions, front-ends (HLR/HSS/UDM) may be data-less/bght weighted. When the backend DB is restarted, it uses the last stored backup, which might be 15-30 minutes older in certain example embodiments. Because of this, dynamically stored information including, for example, MWD data, in the last 15-30 minutes may be lost. Thus, a similar problem exists in cloud-based solution as with the subscriber described above.

[0027] In 5G core network (5GCN), there is no definition of a new interface between SMSC and UDM. Rather, existing interfaces, such as mobile application part (MAP)/S6c interface, are enhanced to support 5G SMS delivery. Further, for normal (i.e., non-priority) SMS, the SMSC may not retry for an absent subscriber. If the above scenarios happen, then SMS delivery may not be reattempted, and the SMS may be discarded in the SMSC upon a timer expiration.

[0028] FIG. 1 illustrates an example signal flow, according to an example embodiment. As illustrated in FIG. 1, at step 1, user equipment (UE) 1 may register in a 5G network, and access management function (AMF) 1 and short message service function (SMSF) 1 may be registered in UDM. At step 2, after some time has passed, the UE may lose radio connectivity. At step 3, another user of another UE may send an SMS to UE1. In doing so, the SMS from the other UE may be stored in the SMSC. At step 4, the SMSC may try to deliver the SMS to UE1. At this point, the SMSC may query the HLR/HSS for UEl’s location, and the SMSF1 address may be returned to the SMSC.

[0029] As further illustrated in FIG. 1, at step 5, the SMSC may try to deliver the SMS to the SMSFl/AMFl, but fails at doing so. In light of the failure, at step 6, the SMSC may send a“Report-SM-Delivery-Status” to the HLR/HSS which stores the SMSF-MNRF flags and SMSC address (MWD data). By storing this information, the HLR/HSS may inform the SMSC (MAP alert service center message (Alrt-SC) for S6c protocol, S6c-ALR message) when the HLR/HSS detects (receiving Ready for SM or Update Location) that the subscriber has become available.

[0030] At step 7, the HLR/HSS/UDM may be restarted. In certain example embodiments, the restart may happen due to various failure scenarios including, but not limited to, for example, power failure, some critical maintenance activity which causes system restart, or other issues. When the HLR/HSS/UDM is restarted, it loses the MNRF flags and SMSC address data that were previously stored. At step 8, the user of UE1 makes himself available and registers in the network. Thus, the UDM/HSS/HLR is updated with location (AMF2/SMSf2) information of UE1. Since the HLR/HSS has lost the dynamic data (MNRF flags and SMSC address), it cannot alert the SMSCs. As a result, at step 9, as the context timer expires in the SMSC, the SMSC deletes the SMS without reattempting to deliver the SMS message.

[0031] Certain example embodiments therefore may resolve the challenges and complications described above. For instance, in an example embodiment, when the SMS failure report (MAP/S 6c - Report SM delivery status) is received at the HLR/HSS from the SMSC, the HLR/HSS may store the MNRF flags and the SMSC address in DB, and add a reset-ID in the response to the failure report. Thus, based on the failure report response with the reset-ID, the SMSC may store the reset-ID along with the SMS data. Whenever HLR/HSS restart (or DB restore) occurs where HLR/HSS lost the dynamic data, HLR/HSS may send a RESET message (along with reset-ID) or similar message to the SMSC. Upon receiving the reset message, the SMSC may reattempt SMS delivery for all the SMSs that have the received reset-ID stored, either upon timer expiration instead of deleting the SMS without delivery reattempt, or even earlier (based on SMSC internal schedule). For example, the reset message may tell the SMSC that it cannot expect to receive an Alert-SC message, and should therefore retry SMS delivery independently.

[0032] FIG. 2 illustrates another example signal flow, according to an example embodiment. As illustrated in FIG. 2, steps 1-5 are similar to steps 1-5 illustrated in FIG. 1. At step 6 of FIG. 2, when a failure report is received at the HLR/HSS, the HLR/HSS may add a reset-ID in a response to the report sent to the SMSC. In an example embodiment, the failure report may be sent via the MAP/S2c interface, and may include a report SM delivery status. Upon receipt of the response from the HLR/HSS, the SMSC may store the reset-ID along with any SMS data. According to an example embodiment, the reset-ID may be assigned based on DB organization. Thus, in case of failure in a part of DB (e.g., in case of lightweight directory access protocol (LDAP), back end directory service agent (BEDSA) based), the reset-ID may be assigned so that when one BEDSA fails, only those subscribers may be identified and may be restored.

[0033] At step 7, due to various scenarios, the HLR/HSS/UDM may be restarted. In certain example embodiments, the restart may happen due to various failure scenarios including, but not limited to, for example, power failure, some critical maintenance activity which causes system restart, or other issues. After restart, the HLR/HSS/UDM may lose the previously stored dynamic data. As one example, the DB restoration may have already happened, and the last 30 minutes of the backup was used which causes the last 30 minute dynamic data to be lost. At step 8, after the UDM/HSS/HLR has been restarted, the HSS/HLR may send a new reset message (S6c/MAP) to the SMSC to inform that the HSS/HLR has lost the MWD data, which may include the MNRF flags and SMSC addresses. According to an example embodiment, the SMSC address may be statically configured at the HSS/HLR, or it may be provided by the operator. In addition, the reset message may have HLR/HSS ID and reset-ID to indicate which subscribers are impacted. In an example embodiment, an operator may configure at least all the SMSC address belongs to the same operator, or an operator may make an agreement with other operators and configure all the SMSC addresses belonging to different operators in the same public land mobile network (PLMN). According to another example embodiment, the new reset message (S6c/MAP) may be implemented as a special Alert-SC message that includes the reset-ID (identifying the impacted UEs), but does not include a mobile station international subscriber directory number (MSISDN) that identifies a single UE.

[0034] At step 9, the SMSC may handle the reset message and mark all subscribers pending to be restored according to the reset-ID. According to an example embodiment, if the reset-ID is not available, the SMSC may mark subscribers as“pending to be restored” based on several factors. For example, the SMSC may map from the HLR global title (GT) to an MSISDN for a MAP (global title) based address. Another option may be that the operator knows their MSISDN range, in which the SMSC may be configured with an MSISDN range that belongs to the home operator. In this regard, many SMSC vendors may support a mobile number portability (MNP) query as well. Based on the MNP query, the SMSC may know that the MSISDN belongs to the home operator, and mark the subscriber accordingly as“pending to be restored.”

[0035] In a further example embodiment, for SMSC that has a diameter address (S6c implementation), the SMSC may perform an electronic number mapping system (ENUM) query (MSISDN mapped to HSS diameter address). This HSS diameter address may be compared with the HSS diameter address received in the reset message.

[0036] At step 10, the SMSc may send MAP SRI_SM/S6c-SRR (MAP send routing information for short message/S 6c-send routing-info-for-SM-request, where S6c is a diameter protocol between SMSC and HSS) request for all of the marked SMS for that particular HLR/HSS. Alternatively, in an example embodiment, to control the sudden traffic, the SMSC may trigger a defined number of SRI_SM/S6c-SRR in batches so that the network may not be overloaded. Moreover, according to another example embodiment, upon timer expiration for the SMS, the SMSC may perform the same reattempt before deleting the SMS.

[0037] At steps 11 and 12, the HLR/HSS may return the SMSF (i.e., SMSF1) address, and the SMS delivery may fail again. At step 13, as the SMS delivery fails, the HSS/HLR may add the MWD data again (SC address and/or SMSF- MNRF flag) based on the failure report. If during that time, the user will be available, then the SMS delivery will be successful. According to such methods, the SMS will not be discarded in the SMSC. Instead, SMS delivery will be reattempted.

[0038] FIG. 3 illustrates an example flow diagram of a method according to an example embodiment. In certain example embodiments, the flow diagram of FIG. 3 may be performed by a network element, which may include, for example a UDM, HSS or HLR, or a combination of the UDM, HSS, and HLR. According to one embodiment, the method of FIG. 3 may include initially, at 300, receiving a failure report from a core network element indicating that delivery of a message to a subscriber has failed. The method may also include, at 315, sending a response to the failure report to the core network element. In an example embodiment, the response may include a reset-identification which identifies the subscriber. At 320, the method may include performing a network element restart or a restart due to various reasons in the failure report. According to example embodiment, when the restart is performed, dynamic data of the subscriber including at least MNRF flags and/or SMSC addresses are lost.

[0039] The method may further include, at 325, sending a reset message to the core network element indicating that stored data corresponding to the subscriber has been lost. In an example embodiment, the reset message may include the reset-identification. In another example embodiment, the receipt of the reset message may trigger the core network element to reattempt delivery of the message to the subscriber according to the reset-identification. According to another example embodiment, the method may include, at 305, registering an access management function and a short message service function at a network element. In addition, at 310, the method may include receiving a query from the core network element for location information of the subscriber. According to certain example embodiments, the reset-identification may be assigned based on DB organization.

[0040] FIG. 4 illustrates an example flow diagram of another method according to an example embodiment. In certain example embodiments, the flow diagram of FIG. 4 may be performed by a core network element in a 3GPP system, such as LTE or 5G NR. For instance, in some example embodiments, the method of FIG. 4 may be performed by an SMSC or SMS router.

[0041] According to one example embodiment, the method of FIG. 4 may include initially, at 400, sending a failure report to a network element indicating that delivery of a message to a subscriber has failed. At 410, the method may include receiving a response to the failure report, wherein the response may include a reset-identification identifying the subscriber. Further, at 415, the method may include receiving a reset message from the network element indicating that stored data corresponding to the subscriber has been lost. In an example embodiment, the reset message may also include the reset- identification. In another example embodiment, the store data may include at least MNRF flags and/or SMSC addresses, and the reset-identification may be assigned based on DB organization. At 420, the method may include reattempting to deliver the message to the subscriber according to the reset- identification. In an example embodiment, the reattempt may be performed in response to the reset message.

[0042] According to another example embodiment, the method may include, at 405, querying the network element for location information of the subscriber. In addition, at 425, the method may include marking the subscriber to be restored according to the reset-identification. In an example embodiment, if the reset- identification is not available, the subscriber may be marked based on a mapping from a home location register global title to a destination mobile station international subscriber delivery number. Further, at 430, the method may include sending a mobile application part for all marked messages for the network element. Alternatively, in an example embodiment, the method may include triggering a defined number of SRI_SM/S6c-SRR in batches so that the network will not be overloaded. In another example embodiment, the method may include reattempting to deliver the message upon expiration of a timer for the message.

[0043] FIG. 5a illustrates an example of an apparatus 10 according to an example embodiment. In an example embodiment, apparatus 10 may be a node, host, core network element, or server in a communication network or serving such a network. For example, apparatus 10 may be an SMSC or SMS router associated with a radio access network (RAN), such as an LTE network, 5G or NR.

[0044] It should be understood that, in some example embodiments, apparatus 10 may be comprised of an edge cloud server as a distributed computing system where the server and the radio node may be stand-alone apparatuses communicating with each other via a radio path or via a wired connection, or they may be located in a same entity communicating via a wired connection. It should be noted that one of ordinary skill in the art would understand that apparatus 10 may include components or features not shown in FIG. 5a.

[0045] As illustrated in the example of FIG. 5a, apparatus 10 may include a processor 12 for processing information and executing instructions or operations. Processor 12 may be any type of general or specific purpose processor. For example, processor 12 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 12 is shown in FIG. 5a, multiple processors may be utilized according to other embodiments. For example, it should be understood that, in certain embodiments, apparatus 10 may include two or more processors that may form a multiprocessor system (e.g., in this case processor 12 may represent a multiprocessor) that may support multiprocessing. In certain embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0046] According to certain example embodiments, processor 12 may perform functions associated with the operation of apparatus 10, which may include, for example, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 10, including processes related to management of communication resources.

[0047] Apparatus 10 may further include or be coupled to a memory 14 (internal or external), which may be coupled to processor 12, for storing information and instructions that may be executed by processor 12. Memory 14 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and/or removable memory. For example, memory 14 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non-transitory machine or computer readable media. The instructions stored in memory 14 may include program instructions or computer program code that, when executed by processor 12, enable the apparatus 10 to perform tasks as described herein.

[0048] In an embodiment, apparatus 10 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processor 12 and/or apparatus 10.

[0049] In certain example embodiments, apparatus 10 may also include or be coupled to one or more antennas 15 for transmitting and receiving signals and/or data to and from apparatus 10. Apparatus 10 may further include or be coupled to a transceiver 18 configured to transmit and receive information. The transceiver 18 may include, for example, a plurality of radio interfaces that may be coupled to the antenna(s) 15. The radio interfaces may correspond to a plurality of radio access technologies including one or more of GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, radio frequency identifier (RFID), ultrawideband (UWB), MulteFire, and the like. The radio interface may include components, such as filters, converters (for example, digital-to-analog converters and the like), mappers, a Fast Fourier Transform (FFT) module, and the like, to generate symbols for a transmission via one or more downlinks and to receive symbols (for example, via an uplink).

[0050] As such, transceiver 18 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 15 and demodulate information received via the antenna(s) 15 for further processing by other elements of apparatus 10. In other embodiments, transceiver 18 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some embodiments, apparatus 10 may include an input and/or output device (I/O device).

[0051] In an embodiment, memory 14 may store software modules that provide functionality when executed by processor 12. The modules may include, for example, an operating system that provides operating system functionality for apparatus 10. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 10. The components of apparatus 10 may be implemented in hardware, or as any suitable combination of hardware and software. [0052] According to some embodiments, processor 12 and memory 14 may be included in or may form a part of processing circuitry or control circuitry. In addition, in some embodiments, transceiver 18 may be included in or may form a part of transceiving circuitry.

[0053] As used herein, the term“circuitry” may refer to hardware-only circuitry implementations (e.g., analog and/or digital circuitry), combinations of hardware circuits and software, combinations of analog and/or digital hardware circuits with software/firmware, any portions of hardware processor(s) with software (including digital signal processors) that work together to case an apparatus (e.g., apparatus 10) to perform various functions, and/or hardware circuit(s) and/or processor(s), or portions thereof, that use software for operation but where the software may not be present when it is not needed for operation. As a further example, as used herein, the term“circuitry” may also cover an implementation of merely a hardware circuit or processor (or multiple processors), or portion of a hardware circuit or processor, and its accompanying software and/or firmware. The term circuitry may also cover, for example, a baseband integrated circuit in a server, cellular network node or device, or other computing or network device.

[0054] According to certain embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to perform the functions associated with any of the embodiments described herein, such as the flow or signaling diagrams illustrated in FIGs. 1-4. In some embodiments, apparatus 10 may be configured to perform an optimization procedure for SMS delivery, for example.

[0055] For instance, in one embodiment, apparatus 10 may be controlled by memory 14 and processor 12 to send a failure report to a network element indicating that delivery of a message to a subscriber has failed. Apparatus 10 may further be controlled by memory 14 and processor 12 to receive a response to the failure report, the response including a reset identification identifying the subscriber. Apparatus 10 may further be controlled by memory 14 and processor 12 to receive a reset message from the network element indicating that stored data corresponding to the subscriber has been lost. In an example embodiment, the reset message may also include the reset-identification. Apparatus 10 may also be controlled by memory 14 and processor 12 to, in response to the reset message, reattempt to deliver the message to the subscriber according to the reset-identification. In another example embodiment, the store data may include at least MNRF flags and/or SMSC addresses, and the reset-identification may be assigned based on DB organization.

[0056] In another example embodiment, the apparatus 10 may also be controlled by memory 14 and processor 12 to query the network element for location information of the subscriber. According to another example embodiment, the apparatus 10 may also be controlled by memory 14 and processor 12 to mark the subscriber to be restored according to the reset-identification. In an example embodiment, if the reset-identification is not available, the subscriber may be marked based on a mapping from a home location register global title to a destination mobile station international subscriber directory number. In a further example embodiment, the apparatus 10 may be controlled by memory 14 and processor 12 to send a mobile application part for all marked messages for the network element. Alternatively, in an example embodiment, the apparatus 10 may be controlled by memory 14 and processor 12 to trigger a defined number of SRI_SM/S6c-SRR in batches so that the network will not be overloaded. In another example embodiment, the apparatus 10 may be controlled by memory 14 and processor 12 to reattempt to deliver the message upon expiration of a timer for the message.

[0057] FIG. 5b illustrates an example of an apparatus 20 according to another embodiment. In an embodiment, apparatus 20 may be a node or element in a communications network or associated with such a network, such as a UDM, HSS or HLR, or a combination of the UDM, HSS, and HLR associated with a radio access network (RAN), such as an LTE network, 5G or NR. [0058] It should be understood that, in some example embodiments, apparatus 20 may be comprised of an edge cloud server as a distributed computing system where the server and the radio node may be stand-alone apparatuses communicating with each other via a radio path or via a wired connection, or they may be located in a same entity communicating via a wired connection. It should be noted that one of ordinary skill in the art would understand that apparatus 10 may include components or features not FIG. 5b.

[0059] As illustrated in the example of FIG. 5b, apparatus 20 may include or be coupled to a processor 22 for processing information and executing instructions or operations. Processor 22 may be any type of general or specific purpose processor. In fact, processor 22 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application- specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 22 is shown in FIG. 5b, multiple processors may be utilized according to other embodiments. For example, it should be understood that, in certain example embodiments, apparatus 20 may include two or more processors that may form a multiprocessor system (e.g., in this case processor 22 may represent a multiprocessor) that may support multiprocessing. According to certain example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0060] Processor 22 may perform functions associated with the operation of apparatus 20 including, as some examples, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 20, including processes related to management of communication resources.

[0061] Apparatus 20 may further include or be coupled to a memory 24 (internal or external), which may be coupled to processor 22, for storing information and instructions that may be executed by processor 22. Memory 24 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and/or removable memory. For example, memory 24 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non-transitory machine or computer readable media. The instructions stored in memory 24 may include program instructions or computer program code that, when executed by processor 22, enable the apparatus 20 to perform tasks as described herein.

[0062] In an embodiment, apparatus 20 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processor 22 and/or apparatus 20.

[0063] In some embodiments, apparatus 20 may also include or be coupled to one or more antennas 25 for receiving a downlink signal and for transmitting via an uplink from apparatus 20. Apparatus 20 may further include a transceiver 28 configured to transmit and receive information. The transceiver 28 may also include a radio interface (e.g., a modem) coupled to the antenna 25. The radio interface may correspond to a plurality of radio access technologies including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT- LE, NFC, RFID, UWB, and the like. The radio interface may include other components, such as filters, converters (for example, digital-to-analog converters and the like), symbol demappers, signal shaping components, an Inverse Fast Fourier Transform (IFFT) module, and the like, to process symbols, such as OFDMA symbols, carried by a downlink or an uplink.

[0064] For instance, transceiver 28 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 25 and demodulate information received via the antenna(s) 25 for further processing by other elements of apparatus 20. In other embodiments, transceiver 28 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some embodiments, apparatus 10 may include an input and/or output device (I/O device). In certain embodiments, apparatus 20 may further include a user interface, such as a graphical user interface or touchscreen.

[0065] In an embodiment, memory 24 stores software modules that provide functionality when executed by processor 22. The modules may include, for example, an operating system that provides operating system functionality for apparatus 20. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 20. The components of apparatus 20 may be implemented in hardware, or as any suitable combination of hardware and software. According to an example embodiment, apparatus 20 may optionally be configured to communicate with apparatus 10 via a wireless or wired communications link 70 according to any radio access technology, such as NR.

[0066] According to certain example embodiments, processor 22 and memory 24 may be included in or may form a part of processing circuitry or control circuitry. In addition, in some embodiments, transceiver 28 may be included in or may form a part of transceiving circuitry.

[0067] According to certain embodiments, apparatus 20 may be controlled by memory 24 and processor 22 to perform the functions associated with example embodiments described herein. For example, in some embodiments, apparatus 20 may be configured to perform one or more of the processes depicted in any of the flow charts or signaling diagrams described herein, such as the flow diagrams illustrated in FIGs. 1-4. For example, in certain embodiments, apparatus 20 may be configured perform an optimization procedure for SMS delivery, for instance.

[0068] For instance, in one embodiment, apparatus 20 may be controlled by memory 14 and processor 12 to receive a failure report from a core network element indicating that delivery of a message to a subscriber has failed. The apparatus 20 may also be controlled by memory 14 and processor 12 to send a response to the failure report to the core network element. In an example embodiment, the response may include a reset-identification which identifies the subscriber. In addition, apparatus 20 may be controlled by memory 14 and processor 12 to perform a network element restart or a restart due to various reasons in the failure report. According to example embodiment, when the restart is performed, dynamic data of the subscriber including at least MNRF flags and/or SMSC addresses are lost.

[0069] The apparatus 20 may also be controlled by memory 14 and processor 12 to send a reset message to the core network element indicating that stored data corresponding to the subscriber has been lost. In an example embodiment, the reset message may include the reset-identification. In another example embodiment, the receipt of the reset message may trigger the core network element to reattempt delivery of the message to the subscriber according to the reset-identification. The apparatus 20 may also be controlled by memory 14 and processor 12 to register an access management function and a short message service function at a network element. In addition, the apparatus 20 may be controlled by memory 14 and processor 12 to receive a query from the core network element for location information of the subscriber. According to certain example embodiments, the reset-identification may be assigned based on DB organization.

[0070] According to certain example embodiments, any one of additional network elements including, for example, UEs, AMFl, SMSF1, AMF, and SMSF illustrated in FIGS. 1 and 2 may include similar hardware elements and functionalities as those of apparatuses 10 and 20 illustrated in FIGs. 5a and 5b, and as described above. Further, the UE in certain example embodiments may be a mobile equipment (ME), mobile station, mobile device, stationary device, IoT device, or other device. As described herein, UE may alternatively be referred to as, for example, a mobile station, mobile equipment, mobile unit, mobile device, user device, subscriber station, wireless terminal, tablet, smart phone, IoT device, sensor or NB-IoT device, or the like.

[0071] Certain example embodiments described herein provide several technical improvements, enhancements, and/or advantages. For example, certain example embodiments provide the ability for the home subscriber MWD data to be restored even after UDM/HSS/HLR restart. Certain example embodiments may also ensure SMS delivery. That is, according to certain example embodiments, it is possible that the SMS will not be discarded in the SMSC after a failed delivery. Rather, according to certain example embodiments, it is possible for the SMSC to reattempt delivery of the SMS to the destined UE.

[0072] In some example embodiments, the functionality of any of the methods, processes, signaling diagrams, algorithms or flow charts described herein may be implemented by software and/or computer program code or portions of code stored in memory or other computer readable or tangible media, and executed by a processor.

[0073] In some example embodiments, an apparatus may be included or be associated with at least one software application, module, unit or entity configured as arithmetic operation(s), or as a program or portions of it (including an added or updated software routine), executed by at least one operation processor. Programs, also called program products or computer programs, including software routines, applets and macros, may be stored in any apparatus- readable data storage medium and include program instructions to perform particular tasks. [0074] A computer program product may comprise one or more computer- executable components which, when the program is run, are configured to carry out some example embodiments. The one or more computer-executable components may be at least one software code or portions of it. Modifications and configurations required for implementing functionality of an example embodiment may be performed as routine(s), which may be implemented as added or updated software routine(s). Software routine(s) may be downloaded into the apparatus.

[0075] As an example, software or a computer program code or portions of it may be in a source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers may include a record medium, computer memory, read only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers. The computer readable medium or computer readable storage medium may be a non-transitory medium.

[0076] In other example embodiments, the functionality may be performed by hardware or circuitry included in an apparatus (e.g., apparatus 10 or apparatus 20), for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another example embodiment, the functionality may be implemented as a signal, a non tangible means that can be carried by an electromagnetic signal downloaded from the Internet or other network.

[0077] According to an example embodiment, an apparatus, such as a node, device, or a corresponding component, may be configured as circuitry, a computer or a microprocessor, such as single-chip computer element, or as a chipset, including at least a memory for providing storage capacity used for arithmetic operation and an operation processor for executing the arithmetic operation.

[0078] One having ordinary skill in the art will readily understand that the invention as discussed above may be practiced with steps in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although the invention has been described based upon these preferred embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of the invention. Although the above embodiments refer to 5G NR and LTE technology, the above embodiments may also apply to any other present or future 3 GPP technology, such as LTE-advanced, and/or fourth generation (4G) technology.

[0079] Partial Glossary

[0080] eNB Enhanced Node B (LTE base station)

[0081] gNB 5G or NR Base Station

[0082] HLR Home Location Register

[0083] HSS Home Subscriber Server

[0084] LTE Long Term Evolution

[0085] MNRF Mobile Not Readable Flag

[0086] NR New Radio

[0087] SMS Short Message Service

[0088] SMSC Short Message Service Center

[0089] SMSF Short Message Service function

[0090] UDM Unified Data Management

[0091] UE User Equipment

Claims

WE CLAIM:

1. A method, comprising:

receiving a failure report from a core network element indicating that delivery of a message to a subscriber has failed;

sending a response to the failure report to the core network element, the response comprising a reset-identification identifying the subscriber;

performing a network element restart or a restart due to various reasons mentioned in the failure report; and

sending a reset message to the core network element indicating that stored data corresponding to the subscriber has been lost, the reset message also comprising the reset-identification,

wherein receipt of the reset message triggers the core network element to reattempt delivery of the message to the subscriber according to the reset- identification.

2. The method according to claim 1 , further comprising registering an access management function and a short message service function.

3. The method according to claims 1 or 2, further comprising, receiving a query from the core network element for location information of the subscriber.

4. The method according to any one of claims 1-3, wherein the reset- identification is assigned based on DB organization.

5. The method according to any one of claims 1-4, wherein the failure report comprises at least mobile not readable flags and message waiting data related to the subscriber.

6. A method, comprising:

sending a failure report to a network element indicating that delivery of a message to a subscriber has failed;

receiving a response to the failure report, the response comprising a reset- identification identifying the subscriber;

receiving a reset message from the network element indicating that stored data corresponding to the subscriber has been lost, the reset message also comprising the reset-identification; and

in response to the reset message, reattempting to deliver the message to the subscriber according to the reset-identification.

7. The method according to claim 6, further comprising querying the network element for location information of the subscriber.

8. The method according to claims 6 or 7, further comprising marking the subscriber to be restored according to the reset-identification,

wherein if the reset-identification is not available, the subscriber is marked based on a mapping from a home location register global title to a destination mobile station international subscriber directory number.

9. The method according to any one of claims 6-8, further comprising sending a mobile application part for all marked messages for the network element.

10. The method according to any one of claims 6-9, wherein the reset- identification is assigned based on DB organization.

11. The method according to any one of claims 6-10, wherein the failure report comprises at least mobile not readable flags and message waiting data related to the subscriber.

12. An apparatus, comprising:

at least one processor; and

at least one memory comprising computer program code,

the at least one memory and the computer program code are configured, with the at least one processor to cause the apparatus at least to

receive a failure report from a core network element indicating that delivery of a message to a subscriber has failed;

send a response to the failure report to the core network element, the response comprising a reset-identification identifying the subscriber;

perform a network element restart or a restart due to various reasons in the failure report; and

send a reset message to the core network element indicating that stored data corresponding to the subscriber has been lost, the reset message also comprising the reset-identification,

13. The apparatus according to claim 12, further comprising registering an access management function and a short message service function.

14. The apparatus according to claims 12 or 13, further comprising, receiving a query from the core network element for location information of the subscriber.

15. The apparatus according to any one of claims 12-14, wherein the reset- identification is assigned based on DB organization.

16. The apparatus according to any one of claims 12-15, wherein the failure report comprises at least mobile not readable flags and message waiting data related to the subscriber.

17. An apparatus, comprising :

at least one processor; and

at least one memory comprising computer program code,

send a failure report to a network element indicating that delivery of a message to a subscriber has failed;

receive a response to the failure report, the response comprising a reset- identification identifying the subscriber;

receive a reset message from the network element indicating that stored data corresponding to the subscriber has been lost, the reset message also comprising the reset-identification; and

in response to the reset message, reattempt to deliver the message to the subscriber according to the reset-identification.

18. The apparatus according to claim 17, further comprising querying the network element for location information of the subscriber.

19. The apparatus according to claims 17 or 18, further comprising marking the subscriber to be restored according to the reset-identification,

20. The apparatus according to any one of claims 17-19, further comprising sending a mobile application part for all marked messages for the network element.

21. The apparatus according to any one of claims 17-20, wherein the reset- identification is assigned based on DB organization.

22. The apparatus according to any one of claims 17-21, wherein the failure report comprises at least mobile not readable flags and message waiting data related to the subscriber.

23. An apparatus comprising means for performing a process according to any of claims 1-22.

24. An apparatus comprising circuitry configured to cause the apparatus to perform a process according to any of claims 1-22.

25. A computer program product encoded with instructions for performing a process according to any of claims 1-22.