WO2020159490A1 - Optimisation de la distribution de messages sms en temps opportun - Google Patents

Optimisation de la distribution de messages sms en temps opportun Download PDF

Info

Publication number
WO2020159490A1
WO2020159490A1 PCT/US2019/015850 US2019015850W WO2020159490A1 WO 2020159490 A1 WO2020159490 A1 WO 2020159490A1 US 2019015850 W US2019015850 W US 2019015850W WO 2020159490 A1 WO2020159490 A1 WO 2020159490A1
Authority
WO
WIPO (PCT)
Prior art keywords
reset
subscriber
message
network element
identification
Prior art date
Application number
PCT/US2019/015850
Other languages
English (en)
Inventor
Saurabh Khare
Devaki Chandramouli
Ulrich Wiehe
Original Assignee
Nokia Technologies Oy
Nokia Usa Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy, Nokia Usa Inc. filed Critical Nokia Technologies Oy
Priority to PCT/US2019/015850 priority Critical patent/WO2020159490A1/fr
Publication of WO2020159490A1 publication Critical patent/WO2020159490A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/30—Network data restoration; Network data reliability; Network data fault tolerance
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data

Definitions

  • 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.
  • LTE Long Term Evolution
  • 5G fifth generation
  • NR new radio
  • 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.
  • SMS short message service
  • HSS home subscriber server
  • HLR home location register
  • UDM unified data management
  • 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.
  • UMTS Universal Mobile Telecommunications System
  • UTRAN Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • E- UTRAN Evolved UTRAN
  • LTE-A LTE-Advanced
  • MulteFire LTE-A Pro
  • LTE-A Pro new radio
  • 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.
  • 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).
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable low-latency- communication
  • mMTC massive machine type communication
  • NR is expected to deliver extreme broadband and ultra-robust, low latency connectivity and massive networking to support the Internet of Things (IoT).
  • IoT Internet of Things
  • M2M machine-to-machine
  • the nodes that can provide radio access functionality to a user equipment may be named gNB when built on NR radio and may be named NG-eNB when built on E-UTRA radio.
  • 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.
  • the reset message may include the reset-identification.
  • 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 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.
  • the reset message may include the reset-identification.
  • 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.
  • 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.
  • the reset message may include the reset-identification.
  • 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.
  • 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.
  • the reset message may include the reset- identification.
  • 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.
  • 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.
  • the reset message may include the reset-identification.
  • 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.
  • 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.
  • the reset message may include the reset-identification.
  • 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.
  • 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.
  • the method may include in response to the reset message, reattempting to deliver the message to the subscriber according to the reset-identification.
  • 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.
  • 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.
  • 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.
  • the method may, in response to the reset message, reattempt to deliver the message to the subscriber according to the reset-identification.
  • 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.
  • the method may, in response to the reset message, reattempt to deliver the message to the subscriber according to the reset-identification.
  • 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.
  • 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.
  • FIG. 1 illustrates an example signal flow, according to an example embodiment.
  • FIG. 2 illustrates another example signal flow, according to an example embodiment.
  • FIG. 3 illustrates an example flow diagram of a method, according to an embodiment.
  • FIG. 4 illustrates an example flow diagram of another method, according to an example embodiment.
  • FIG. 5a illustrates a block diagram of an apparatus according to an example embodiment
  • FIG. 5b illustrates a block diagram of another apparatus according to an example embodiment.
  • Short message service has been described in 3GPP 23040, and may be applicable for 2G, 3G, 4G, and 5G.
  • HSS home subscriber server
  • HLR home location register
  • UDM unified data management
  • MNRF mobile not readable flags
  • SMSC short message service center
  • MNRF mobile not readable flags
  • MSC short message service center
  • SMSC short message service center
  • front-ends (HLR/HSS/UDM) may be data-less/bght weighted.
  • the backend DB 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.
  • SMSC 5G core network
  • MAP mobile application part
  • S6c short message broker
  • 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.
  • FIG. 1 illustrates an example signal flow, according to an example embodiment.
  • 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.
  • AMF access management function
  • SMSF short message service function
  • the UE may lose radio connectivity.
  • another user of another UE may send an SMS to UE1.
  • the SMS from the other UE may be stored in the SMSC.
  • the SMSC may try to deliver the SMS to UE1.
  • the SMSC may query the HLR/HSS for UEl’s location, and the SMSF1 address may be returned to the SMSC.
  • the SMSC may try to deliver the SMS to the SMSFl/AMFl, but fails at doing so.
  • the SMSC may send a“Report-SM-Delivery-Status” to the HLR/HSS which stores the SMSF-MNRF flags and SMSC address (MWD data).
  • 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.
  • the HLR/HSS/UDM may be restarted.
  • 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.
  • the HLR/HSS/UDM When the HLR/HSS/UDM is restarted, it loses the MNRF flags and SMSC address data that were previously stored.
  • the user of UE1 makes himself available and registers in the network.
  • 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.
  • the SMSC deletes the SMS without reattempting to deliver the SMS message.
  • Certain example embodiments therefore may resolve the challenges and complications described above.
  • 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.
  • the SMSC may store the reset-ID along with the SMS data.
  • HLR/HSS restart or DB restore
  • HLR/HSS may send a RESET message (along with reset-ID) or similar message to the SMSC.
  • 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.
  • FIG. 2 illustrates another example signal flow, according to an example embodiment.
  • steps 1-5 are similar to steps 1-5 illustrated in FIG. 1.
  • the HLR/HSS may add a reset-ID in a response to the report sent to the SMSC.
  • the failure report may be sent via the MAP/S2c interface, and may include a report SM delivery status.
  • the SMSC may store the reset-ID along with any SMS data.
  • the reset-ID may be assigned based on DB organization.
  • the reset-ID may be assigned so that when one BEDSA fails, only those subscribers may be identified and may be restored.
  • LDAP lightweight directory access protocol
  • BEDSA back end directory service agent
  • the HLR/HSS/UDM may be restarted.
  • 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.
  • the HLR/HSS/UDM may lose the previously stored dynamic data.
  • 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.
  • 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.
  • the SMSC address may be statically configured at the HSS/HLR, or it may be provided by the operator.
  • the reset message may have HLR/HSS ID and reset-ID to indicate which subscribers are impacted.
  • 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).
  • PLMN public land mobile network
  • the new reset message 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.
  • MSISDN mobile station international subscriber directory number
  • the SMSC may handle the reset message and mark all subscribers pending to be restored according to the reset-ID.
  • 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.”
  • MNP mobile number portability
  • 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.
  • ENUM electronic number mapping system
  • 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.
  • 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
  • the SMSC may trigger a defined number of SRI_SM/S6c-SRR in batches so that the network may not be overloaded.
  • the SMSC may perform the same reattempt before deleting the SMS.
  • the HLR/HSS may return the SMSF (i.e., SMSF1) address, and the SMS delivery may fail again.
  • 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.
  • FIG. 3 illustrates an example flow diagram of a method according to an example embodiment.
  • 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.
  • 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.
  • the response may include a reset-identification which identifies the subscriber.
  • 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.
  • 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.
  • the reset message may include the reset-identification.
  • 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 method may include, at 305, registering an access management function and a short message service function at a network element.
  • the method may include receiving a query from the core network element for location information of the subscriber.
  • the reset-identification may be assigned based on DB organization.
  • FIG. 4 illustrates an example flow diagram of another method according to an example embodiment.
  • the flow diagram of FIG. 4 may be performed by a core network element in a 3GPP system, such as LTE or 5G NR.
  • the method of FIG. 4 may be performed by an SMSC or SMS router.
  • 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.
  • the method may include receiving a response to the failure report, wherein the response may include a reset-identification identifying the subscriber.
  • the method may include receiving a reset message from the network element indicating that stored data corresponding to the subscriber has been lost.
  • the reset message may also include the reset- identification.
  • the store data may include at least MNRF flags and/or SMSC addresses, and the reset-identification may be assigned based on DB organization.
  • 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.
  • the method may include, at 405, querying the network element for location information of the subscriber.
  • the method may include marking the subscriber to be restored according to the reset-identification.
  • 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.
  • the method may include sending a mobile application part for all marked messages for the network element.
  • the method may include triggering a defined number of SRI_SM/S6c-SRR in batches so that the network will not be overloaded.
  • the method may include reattempting to deliver the message upon expiration of a timer for the message.
  • FIG. 5a illustrates an example of an apparatus 10 according to an example embodiment.
  • apparatus 10 may be a node, host, core network element, or server in a communication network or serving such a network.
  • apparatus 10 may be an SMSC or SMS router associated with a radio access network (RAN), such as an LTE network, 5G or NR.
  • RAN radio access network
  • 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.
  • 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.
  • 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.
  • 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.
  • processor 12 may represent a multiprocessor
  • the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).
  • 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.
  • 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.
  • 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.
  • 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.
  • an external computer readable storage medium such as an optical disc, USB drive, flash drive, or any other storage medium.
  • the external computer readable storage medium may store a computer program or software for execution by processor 12 and/or apparatus 10.
  • 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).
  • filters for example, digital-to-analog converters and the like
  • mappers for example, mappers
  • FFT Fast Fourier Transform
  • 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.
  • transceiver 18 may be capable of transmitting and receiving signals or data directly.
  • apparatus 10 may include an input and/or output device (I/O device).
  • 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.
  • processor 12 and memory 14 may be included in or may form a part of processing circuitry or control circuitry.
  • transceiver 18 may be included in or may form a part of transceiving circuitry.
  • 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.
  • hardware-only circuitry implementations e.g., analog and/or digital circuitry
  • combinations of hardware circuits and software e.g., combinations of analog and/or digital hardware circuits with software/firmware
  • any portions of hardware processor(s) with software including digital signal processors
  • 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.
  • circuitry may also cover, for example, a baseband integrated circuit in a server, cellular network node or device, or other computing or network device.
  • 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.
  • apparatus 10 may be configured to perform an optimization procedure for SMS delivery, for example.
  • 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.
  • 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.
  • the store data may include at least MNRF flags and/or SMSC addresses, and the reset-identification may be assigned based on DB organization.
  • the apparatus 10 may also be controlled by memory 14 and processor 12 to query the network element for location information of the subscriber.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 5b illustrates an example of an apparatus 20 according to another 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.
  • RAN radio access network
  • 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.
  • apparatus 10 may include components or features not 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.
  • 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.
  • 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.
  • processor 22 may represent a multiprocessor
  • the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).
  • 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.
  • 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.
  • 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.
  • 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.
  • an external computer readable storage medium such as an optical disc, USB drive, flash drive, or any other storage medium.
  • the external computer readable storage medium may store a computer program or software for execution by processor 22 and/or apparatus 20.
  • 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.
  • filters for example, digital-to-analog converters and the like
  • symbol demappers for example, digital-to-analog converters and the like
  • signal shaping components for example, an Inverse Fast Fourier Transform (IFFT) module, and the like
  • IFFT Inverse Fast Fourier Transform
  • 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.
  • transceiver 28 may be capable of transmitting and receiving signals or data directly.
  • apparatus 10 may include an input and/or output device (I/O device).
  • apparatus 20 may further include a user interface, such as a graphical user interface or touchscreen.
  • 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.
  • 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.
  • processor 22 and memory 24 may be included in or may form a part of processing circuitry or control circuitry.
  • transceiver 28 may be included in or may form a part of transceiving circuitry.
  • apparatus 20 may be controlled by memory 24 and processor 22 to perform the functions associated with example embodiments described herein.
  • 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.
  • apparatus 20 may be configured perform an optimization procedure for SMS delivery, for instance.
  • 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.
  • the response may include a reset-identification which identifies the subscriber.
  • 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.
  • 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.
  • the reset message may include the reset-identification.
  • 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.
  • 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.
  • the reset-identification may be assigned based on DB organization.
  • 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.
  • the UE in certain example embodiments may be a mobile equipment (ME), mobile station, mobile device, stationary device, IoT device, or other device.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • carrier may include a record medium, computer memory, read only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and software distribution package, for example.
  • 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.
  • 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.
  • ASIC application specific integrated circuit
  • PGA programmable gate array
  • FPGA field programmable gate array
  • 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.
  • 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.
  • eNB Enhanced Node B LTE base station
  • SMSC Short Message Service Center

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé de réduction du surdébit, des appareils et un produit programme d'ordinateur associés. Un procédé peut comprendre la réception d'un rapport de défaillance provenant d'un élément de réseau central. Le procédé peut également comprendre l'envoi d'une réponse au rapport de défaillance, la réponse comprenant une identification de réinitialisation identifiant l'abonné. De plus, le procédé peut comprendre la réalisation d'un redémarrage de l'élément de réseau ou d'un redémarrage pour diverses raisons dans le rapport de défaillance, et l'envoi d'un message de réinitialisation à l'élément de réseau central. En outre, la réception du message de réinitialisation peut déclencher sur l'élément de réseau central une tentative de délivrance du message à l'abonné.
PCT/US2019/015850 2019-01-30 2019-01-30 Optimisation de la distribution de messages sms en temps opportun WO2020159490A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2019/015850 WO2020159490A1 (fr) 2019-01-30 2019-01-30 Optimisation de la distribution de messages sms en temps opportun

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2019/015850 WO2020159490A1 (fr) 2019-01-30 2019-01-30 Optimisation de la distribution de messages sms en temps opportun

Publications (1)

Publication Number Publication Date
WO2020159490A1 true WO2020159490A1 (fr) 2020-08-06

Family

ID=65441085

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2019/015850 WO2020159490A1 (fr) 2019-01-30 2019-01-30 Optimisation de la distribution de messages sms en temps opportun

Country Status (1)

Country Link
WO (1) WO2020159490A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008154955A1 (fr) * 2007-06-19 2008-12-24 Telefonaktiebolaget Lm Ericsson (Publ) Récupération ims après défaillance hss

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008154955A1 (fr) * 2007-06-19 2008-12-24 Telefonaktiebolaget Lm Ericsson (Publ) Récupération ims après défaillance hss

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Mobile Application Part (MAP) specification (Release 15)", 22 December 2018 (2018-12-22), XP051686703, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/3guInternal/3GPP%5Fultimate%5Fversions%5Fto%5Fbe%5Ftransposed/sentToDpc/29002%2Df40%2Ezip> [retrieved on 20181222] *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS); Stage 2 (Release 15)", 17 September 2018 (2018-09-17), XP051535178, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fsa/WG2%5FArch/Latest%5FSA2%5FSpecs/DRAFT%5FINTERIM/23228%2Df30%5FCR%5FImplemented%2Ezip> [retrieved on 20180917] *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2 (Release 15)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 23.204, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V15.0.0, 27 March 2018 (2018-03-27), pages 1 - 59, XP051450514 *

Similar Documents

Publication Publication Date Title
US11509728B2 (en) Methods and apparatuses for discovering a network function acting as network function service consumer
EP3987715A1 (fr) Notification de souscription à un événement
US11729046B2 (en) Failure indication of master cell group with fallback to radio resource control re-establishment
US20240015044A1 (en) Separate session start request indication
US11503437B2 (en) Methods and apparatuses for multicast-broadcast service (MBS) activation and deactivation
US11510105B2 (en) User plane function (UPF) control with coexistence of policy control and packet filters dynamically generated at the session management function (SMF)
EP3979680A1 (fr) Services de localisation améliorés en 5g
EP4274195A1 (fr) Attribution de serveur d&#39;application périphérique pour des groupes ad hoc d&#39;équipement utilisateur
WO2020183330A1 (fr) Distribution d&#39;informations de référence temporelle efficace pour de multiples domaines d&#39;horloge
EP4316046A1 (fr) Enregistrement simultané sur de multiples réseaux
US20220322214A1 (en) Filtered authorization list for private networks
WO2020159490A1 (fr) Optimisation de la distribution de messages sms en temps opportun
US20220279621A1 (en) Emergency operations slice exchange between entities in mobile networks
US20230269016A1 (en) Working clock determination for a mobile user equipment
US11943812B2 (en) Determining random access channel (RACH) resources or parameters based on network slice-based resource allocation classes (RACs)
US20230068412A1 (en) Ad hoc group based services to support 5g system (5gs) scenarios
US20230269795A1 (en) Methods and apparatuses for user plane function control for multicast transport
US20230254929A1 (en) Restoration of multicast/broadcast service upon multicast/broadcast user plane function failure without restart
US20230254172A1 (en) Broadcast service restoration for multicast/broadcast service upon radio access node failure or restart
WO2021140372A1 (fr) Indications sélectives en direction d&#39;un équipement utilisateur
WO2023285224A1 (fr) Procédés et appareils destinés à permettre à un équipement utilisateur de s&#39;enregistrer auprès de multiples réseaux mobiles terrestres publics et réseaux non publics à l&#39;aide du même type d&#39;accès

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19705640

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19705640

Country of ref document: EP

Kind code of ref document: A1