Patent Description:
Currently, Third Generation Partnership Project (3GPP) Technical Specification (TS) <NUM> defines system procedures and services related to Home Subscriber Server/Home Location Register (HSS/HLR) and Unified Data Management (UDM) interworking in User Data Interworking Coexistence and Migration (UDICoM) for Mobile Terminated Short Message Service (MT SMS) delivery support.

However, system procedures to provide MT SMS delivery support are still lacking.

<NPL>) proposes interaction between UDM and HSS for registration notification. A reference point Nxx is proposed between UDM and HSS within combined HSS/UDM. The interface is proposed to be based on SBI principles.

3GPP TS <NUM> V16. <NUM> specifies capabilities and enhancements needed to support SMS over a generic IP Connectivity Access Network using IMS capabilities. These include enhancements to the HSS, communication between the SMS-GMSC / SMS-IWMSC and the HSS, transfer of UE Terminated SMS, UE Originated SMS, Delivery reports, etc..

The claimed subject-matter is defined by methods according to claims <NUM>, <NUM> and <NUM>, a node according to claim <NUM>, and a system according to claim <NUM>.

Some embodiments advantageously provide methods and apparatuses for SMS delivery, such as support of SMS over Internet Protocol (SMSoIP) in Third Generation Partnership Project (3GPP) <NUM>th Generation (<NUM>, also called New Radio or NR)-only deployments.

As described above, 3GPP TS <NUM> currently defines system procedures and services related to HSS/HLR and UDM interworking in UDICoM for MT SMS delivery support.

The scenarios considered assume that there is an HSS/HLR receiving requests from the Short Message Service-Gateway Mobile Switching Center (SMS-GMSC) over Mobile Application Part C (MAP C) and/or Diameter S6c reference points. These MAP C and Diameter S6c reference points with the SMS-GMSC are exposed by the HSS/HLR functionality supporting the Second Generation/Third Generation/Fourth Generation (<NUM>/<NUM>/<NUM>) accesses as defined in, for example, 3GPP TS <NUM>.

However, in the context of 3GPP Release <NUM> (Rel-<NUM>) UDICoM, for MT SMS delivery over Fifth Generation (<NUM>, also called New Radio/NR) Non-Access-Stratum (NAS) in deployment scenarios where <NUM>/<NUM>/<NUM> accesses are not supported, the MAP C and Diameter S6c reference points with the SMS-GMSC are exposed by the UDM instead, since there may be no deployment of the HLR/HSS functionality supporting the legacy accesses and their corresponding reference points in the first place.

In these scenarios (e.g., MT SMS delivery over <NUM> NAS in deployment scenarios where <NUM>/<NUM>/<NUM> accesses are not supported), if support for SMSoIP is also expected, an HSS supporting Internet Protocol (IP) Multimedia Subsystem (IMS) functionality may be used including the support for the registration/de-registration of the IP-Short Message-Gateway (IP-SM-GW) address in the HSS over e.g., the Sh reference point as defined in, for example, 3GPP TS <NUM>.

However, the HSS functionality supporting IMS does not expose the MAP C or Diameter S6c reference points with SMS-GMSC and neither the MAP J or Diameter S6c reference points with the IP-SM-GW. In the context of 3GPP Rel-<NUM> UDICoM, in these cases, the MAP C/J and/or Diameter S6c reference points are exposed by the UDM instead. An example of these scenarios is depicted in an example system <NUM> in <FIG>.

The system <NUM> includes an IP-SM-GW <NUM>, SMS-GMSC <NUM>, UDM <NUM>, HSS <NUM>, Proxy-Call Session Control Function (P-CSCF) <NUM>, UE <NUM> and Serving-Call Session Control Function (S-CSCF) <NUM>.

In some embodiments, the IP-SM-GW may be considered to provide an IMS application server which handles session initiation protocol (SIP) based messaging services for IMS subscribers. In addition, the IP-SM-GW may interact with the legacy short message service center (SMSC) using MAP signalling in order to allow IMS to SMS conversion and distribution. In some embodiments, the IP-SM-GW may be considered to implement transport layer interworking for SMS over IP.

As can be seen in <FIG>, for MT SMS delivery, the UDM <NUM> may attempt to involve the IP-SM-GW <NUM>, but the IP-SM-GW address is not kept at the UDM <NUM> but at the HSS (IMS) <NUM> instead. The IP-SM-GW <NUM> will register in the HSS (IMS) while the SMS-GMSC <NUM> and IP-SM-GW <NUM> will interact with the UDM <NUM>.

In the context of 3GPP Rel-<NUM> UDICoM, for MT SMS delivery over <NUM> NAS in deployment scenarios where <NUM>/<NUM>/<NUM> accesses are not supported and where support for SMS over IP is also expected, interactions between the UDM <NUM> and the HSS (IMS) <NUM> should be specified for e.g., the transfer of the IP-SM-GW address. Handling of the IP-SM-GW address in the interactions with Fifth Generation System UDR (5GS-UDR) via e.g., an Nudr interface should also be considered.

Some embodiments of the present disclosure provide for one or more new procedures to make the IP-SM-GW address available to the UDM in deployment scenarios where, for example, <NUM>/<NUM>/<NUM> accesses are not supported and support of SMS over IP is expected.

Some embodiments of the present disclosure may allow the UDM to identify and/or locate the IP-SM-GW that is serving a user for SMS. Some embodiments may provide proper support of MT SMS delivery procedures in <NUM> Core (5GC) only deployments where SMSoIP is required.

Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to short message service (SMS) delivery. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

The UE herein can be any type of wireless device capable of communicating with a network node or another UE over radio signals. In some embodiments, the UE may be an autonomous machine configured to communicate via IMS. The UE herein can by any type of communication device capable of communicating with another UE, an application server, a network node, a server, an IMS NF or other IMS network node, via a wired connection and/or a wireless connection. The UE may also be a radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), low-cost and/or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (IoT) device, or a Narrowband IoT (NB-IOT) device etc..

In some embodiments, the term "node" is used herein and can be any kind of network node, such as, a subscriber server node (e.g., HSS) and/or a data management node (e.g., UDM). In some embodiments, the node may be, for example, a core network node, such as a <NUM> and/or NR network node, an IMS node, a Network Function (NF) node, such as, for example, a P-CSCF node, an S-CSCF node, an I-CSCF node, etc..

A node may include physical components, such as processors, allocated processing elements, or other computing hardware, computer memory, communication interfaces, and other supporting computing hardware. The node may use dedicated physical components, or the node may be allocated use of the physical components of another device, such as a computing device or resources of a datacenter, in which case the node is said to be virtualized. A node may be associated with multiple physical components that may be located either in one location, or may be distributed across multiple locations.

In some embodiments, the terms "gateway" and "IP-SM-GW" may be used interchangeably. In some embodiments, the terms "data management node" may be used interchangeably with "UDM node". In some embodiments, the terms "subscriber node" and "HSS node" may be used interchangeably. In some embodiments, the terms "data repository node" and "UDR node" may be used interchangeably.

In some embodiments, the "address" herein may be considered an IP address or any other type of address or location identifier that may be used to identify and/or locate the IP-SM-GW for the user.

In some embodiments, the term "legacy access" may mean an HSS and/or HLR functionality supporting Evolved Packet Core (EPC) and/or circuit switched/packet switched (CS/PS) access technologies, respectively. Any two or more embodiments described in this disclosure may be combined in any way with each other.

Note also that some embodiments of the present disclosure may be supported by standard documents disclosed in Third Generation Partnership Project (3GPP) technical specifications. That is, some embodiments of the description can be supported by the above documents. In addition, all the terms disclosed in the present document may be described by the above standard documents.

Note that although terminology from one particular wireless system, such as, for example, <NUM>rd Generation Partnership Project (3GPP), Long Term Evolution (LTE), <NUM>th Generation (<NUM>) (also known as New Radio (NR)), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system.

Note further, that functions described herein as being performed by a UE or a UDM node or an HSS node or any network node may be distributed over a plurality of UEs or a plurality of UDM nodes or a plurality of HSS nodes or a plurality of network nodes. In other words, it is contemplated that the functions of the UE, UDM node, HSS node or network node described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in <FIG> a schematic diagram of a communication system <NUM>, according to an embodiment, constructed in accordance with the principles of the present disclosure. The communication system <NUM> in <FIG> is a non-limiting example and other embodiments of the present disclosure may be implemented by one or more other systems and/or networks. Referring to <FIG>, the system <NUM> includes a UDM <NUM> and HSS <NUM> that may be configured according to one or more of the embodiments of the present disclosure. In addition, the system <NUM> includes the IP-SM-GW <NUM>, SMS-GMSC <NUM>, UE <NUM> and an IMS core including a P-CSCF <NUM> and a S-CSCF <NUM>.

The system <NUM> may include UDM <NUM> configured to include messenger <NUM> which is configured to cause UDM <NUM> to receive a registration request from a home subscriber server, HSS, node, the registration request being to register an Internet Protocol-Short Message-Gateway, IP-SM-GW, and the registration request comprising an address of the IP-SM-GW; and optionally, as a result of receiving the registration request comprising the address of the IP-SM-GW from the HSS node, determine message waiting data. The system <NUM> includes HSS <NUM> configured to include addresser <NUM> which is configured to cause HSS <NUM> to receive a registration request; and send, to a unified data management, UDM, node, the registration request, the registration request being to register an Internet Protocol-Short Message-Gateway, IP-SM-GW, and the registration request comprising an address of the IP-SM-GW. The system <NUM> includes querier <NUM> which is configured to query a unified data repository (UDR) node for the address of the IP-SM-GW.

It should be noted that, for simplicity, a single node is shown for the various entities in the system <NUM> depicted in <FIG> (e.g., a single UE <NUM>, a single IP-SM-GW <NUM>, a single IMS core, a single UDM <NUM>, a single HSS <NUM>, etc.). It should be understood that the system <NUM> may include numerous entities/nodes of those shown in <FIG>, as well as, additional entities/nodes not shown in <FIG>. In addition, the system <NUM> may include many more connections/interfaces than those shown in <FIG>.

Example implementations, in accordance with an embodiment, of the UE <NUM>, UDM node <NUM>, HSS node <NUM> and a network node <NUM> (e.g., Unified Data Repository (UDR) or any other node) discussed herein will now be described with reference to <FIG>. It is noted that, the interconnection of the UE <NUM>, UDM node <NUM>, HSS node <NUM> and network node <NUM> are shown in serial, such depiction is for the sake of simplicity and ease of explanation. It is understood that or more of the UE <NUM>, UDM node <NUM>, HSS node <NUM> and the network node <NUM> may communicate via a wired and/or wireless network, i.e., cloud network, and that the UE <NUM>, UDM node <NUM>, HSS node <NUM> and the network node <NUM> are not literally connected to one another. In other words, in <FIG>, the connection between the devices UE <NUM>, UDM node <NUM>, HSS node <NUM> and network node <NUM> (e.g., UDR) is shown without explicit reference to any intermediary devices or connections. However, it should be understood that intermediary devices and/or connections may exist between these devices, although not explicitly shown.

The UE <NUM> includes a communication interface <NUM>, processing circuitry <NUM>, and memory <NUM>. The communication interface <NUM> may be configured to communicate with any other elements/nodes in the system <NUM> according to the techniques in the present disclosure. In some embodiments, the communication interface <NUM> may be formed as or may include, for example, one or more radio frequency (RF) transmitters, one or more RF receivers, and/or one or more RF transceivers, and/or may be considered a radio interface. In some embodiments, the communication interface <NUM> may include a wired interface.

The processing circuitry <NUM> may include one or more processors <NUM> and memory, such as, the memory <NUM>. In particular, in addition to a traditional processor and memory, the processing circuitry <NUM> may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.

Thus, the UE <NUM> may further include software stored internally in, for example, memory <NUM>, or stored in external memory (e.g., database) accessible by the UE <NUM> via an external connection. The software may be executable by the processing circuitry <NUM>. The processing circuitry <NUM> may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by the UE <NUM>. The memory <NUM> is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software may include instructions stored in memory <NUM> that, when executed by the processor <NUM> causes the processing circuitry <NUM> and/or configures the UE <NUM> to perform the processes described herein with respect to the UE <NUM>.

The UDM node <NUM> includes a communication interface <NUM>, processing circuitry <NUM>, and memory <NUM>. The communication interface <NUM> may be configured to communicate with any other elements/nodes in the system <NUM> according to the techniques in the present disclosure. In some embodiments, the communication interface <NUM> may be formed as or may include, for example, one or more radio frequency (RF) transmitters, one or more RF receivers, and/or one or more RF transceivers, and/or may be considered a radio interface. In some embodiments, the communication interface <NUM> may include a wired interface.

Thus, the UDM node <NUM> may further include software stored internally in, for example, memory <NUM>, or stored in external memory (e.g., database) accessible by the UDM node <NUM> via an external connection. The software may be executable by the processing circuitry <NUM>. The processing circuitry <NUM> may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by the UDM node <NUM>. The memory <NUM> is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software may include instructions stored in memory <NUM> that, when executed by the processor <NUM> and/or messenger <NUM>, causes the processing circuitry <NUM> and/or configures the UDM node <NUM> to perform the processes described herein with respect to the UDM node <NUM> (e.g., processes described with reference to <FIG> and/or any of the other flowcharts).

The HSS node <NUM> includes a communication interface <NUM>, processing circuitry <NUM>, and memory <NUM>. The communication interface <NUM> may be configured to communicate with any other elements/nodes in the system <NUM> according to the techniques in the present disclosure. In some embodiments, the communication interface <NUM> may be formed as or may include, for example, one or more radio frequency (RF) transmitters, one or more RF receivers, and/or one or more RF transceivers, and/or may be considered a radio interface. In some embodiments, the communication interface <NUM> may include a wired interface.

Thus, the HSS node <NUM> may further include software stored internally in, for example, memory <NUM>, or stored in external memory (e.g., database) accessible by the HSS node <NUM> via an external connection. The software may be executable by the processing circuitry <NUM>. The processing circuitry <NUM> may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by the HSS node <NUM>. The memory <NUM> is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software may include instructions stored in memory <NUM> that, when executed by the processor <NUM> and/or addresser <NUM>, causes the processing circuitry <NUM> and/or configures the HSS node <NUM> to perform the processes described herein with respect to the HSS node <NUM> (e.g., processes described with reference to <FIG> and/or any of the other flowcharts).

The network node <NUM> (e.g., UDR node, IP-SM-GW, etc.) includes a communication interface <NUM>, processing circuitry <NUM>, and memory <NUM>. The communication interface <NUM> may be configured to communicate with any other elements/nodes in the system <NUM> according to the techniques in the present disclosure. In some embodiments, the communication interface <NUM> may be formed as or may include, for example, one or more radio frequency (RF) transmitters, one or more RF receivers, and/or one or more RF transceivers, and/or may be considered a radio interface. In some embodiments, the communication interface <NUM> may include a wired interface.

Thus, the network node <NUM> may further include software stored internally in, for example, memory <NUM>, or stored in external memory (e.g., database) accessible by the network node <NUM> via an external connection. The software may be executable by the processing circuitry <NUM>. The processing circuitry <NUM> may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by the network node <NUM>. The memory <NUM> is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software may include instructions stored in memory <NUM> that, when executed by the processor <NUM> and/or querier <NUM>, causes the processing circuitry <NUM> and/or configures the network node <NUM> to perform the processes described herein with respect to the network node <NUM> (e.g., 5GS-UDR node, IP-SM-GW, etc.) such as the processes described with reference to <FIG> as well as other figures.

Although <FIG> shows messenger <NUM>, addresser <NUM>, querier <NUM> as being within a respective processor, it is contemplated that these elements may be implemented such that a portion of the elements is stored in a corresponding memory within the processing circuitry. In other words, the elements may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

<FIG> is a flowchart of an exemplary process in a UDM node <NUM> for supporting delivery of an SMS message to the UE <NUM> according to one or more of the techniques in the present disclosure. One or more Blocks and/or functions and/or methods performed by the UDM node <NUM> may be performed by one or more elements of UDM node <NUM> such as by messenger <NUM> in processing circuitry <NUM>, memory <NUM>, processor <NUM>, communication interface <NUM>, etc. according to the example process/method. The example process includes receiving (Block S100), such as via messenger <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, from a home subscriber server (HSS) node <NUM>, an address of an Internet Protocol-Short Message-Gateway (IP-SM-GW) <NUM>, the IP-SM-GW <NUM> serving a user for a Short Message Service (SMS).

In some embodiments, receiving the address of the IP-SM-GW from the HSS node includes receiving, such as via messenger <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, a registration request to register the IP-SM-GW in a unified data management (UDM) node, the registration request including the address of the IP-SM-GW associated with the user.

In some embodiments, the method further includes at least one of: receiving, such as via messenger <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, a de-registration request to de-register the IP-SM-GW, the de-registration request including the address of the IP-SM-GW; and confirming, such as via messenger <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, one of the registration and the de-registration of the IP-SM-GW in a response message.

In some embodiments, the method includes one or more of, such as via messenger <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>: storing the address in a unified data repository (UDR) node as part of the registration of the IP-SM-GW; removing the address in the UDR node as part of the registration of the IP-SM-GW; determining whether message waiting data are stored for the user associated with the IP-SM-GW; and/or using the address to communicate with the IP-SM-GW to provide a mobile terminated short message service (MT SMS) to a user equipment (UE) associated with the user.

In some embodiments, receiving the address of the IP-SM-GW from the HSS node includes determining, such as via messenger <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, whether the address is available in a home subscriber server (HSS) node by sending a request to the HSS node; and as a result of the request, receiving, such as via messenger <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, a response from the HSS node, the response including the address of the IP-SM-GW associated with the user.

In some embodiments, receiving the address of the IP-SM-GW from the HSS node includes querying, such as via messenger <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, a unified data repository (UDR) node for the address of the IP-SM-GW; and responsive to the query, receiving, such as via messenger <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, the address from the UDR node.

<FIG> is a flowchart of an exemplary process in an HSS node <NUM> for supporting delivery of an SMS message to the UE <NUM> according to one or more of the techniques in the present disclosure. One or more Blocks and/or functions and/or methods performed by the HSS node <NUM> may be performed by one or more elements of HSS node <NUM> such as via addresser <NUM> in processing circuitry <NUM>, memory <NUM>, processor <NUM>, communication interface <NUM>, etc. according to the example process/method. The example process includes sending (Block S102), such as via addresser <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, to one of a unified data repository (UDR) node and a unified data management (UDM) node, an address of an Internet Protocol-Short Message-Gateway (IP-SM-GW), the IP-SM-GW serving a user for a Short Message Service (SMS).

In some embodiments, sending, to the UDM node, the address of the IP-SM-GW includes sending, such as via addresser <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, a registration request to register the IP-SM-GW, the registration request including the address of the IP-SM-GW associated with the user. In some embodiments, the method further includes at least one of: sending, such as via addresser <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, a de-registration request to de-register the IP-SM-GW, the de-registration request including the address of the IP-SM-GW; and receiving, such as via addresser <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, a confirmation of one of the registration and the de-registration of the IP-SM-GW in a response message.

In some embodiments, sending, to the UDM node, the address of the IP-SM-GW is responsive to the HSS node <NUM>: receiving, such as via addresser <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, a request for the address from the UDM node; and responsive to the request, sending, such as via addresser <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, a response to the UDM node, the response including the address of the IP-SM-GW associated with the user. In some embodiments, sending the address of the IP-SM-GW includes sending the address of the IP-SM-GW to the UDR node.

<FIG> is a flowchart of an exemplary process in a network node <NUM> (e.g., UDR node) for supporting delivery of an SMS message to the UE <NUM> according to one or more of the techniques in the present disclosure. One or more Blocks and/or functions and/or methods performed by the network node <NUM> may be performed by one or more elements of network node <NUM> such as via querier <NUM> in processing circuitry <NUM>, memory <NUM>, processor <NUM>, communication interface <NUM>, etc. according to the example process/method. The example process includes receiving (Block S104), such as via querier <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, from a home subscriber server (HSS) node, an address of an Internet Protocol-Short Message-Gateway (IP-SM-GW), the IP-SM-GW serving a user for a Short Message Service (SMS). The process includes as a result of receiving a query from a unified data management (UDM) node for the address of the IP-SM-GW, sending (Block S106), such as via querier <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, the address of the IP-SM-GW to the UDM node. In some embodiments, the network node <NUM> is a unified data repository (UDR) node.

<FIG> is a flowchart of an exemplary process in a UDM node <NUM> for supporting delivery of an SMS message to the UE <NUM> according to one or more of the techniques in the present disclosure. One or more Blocks and/or functions and/or methods performed by the UDM node <NUM> may be performed by one or more elements of UDM node <NUM> such as by messenger <NUM> in processing circuitry <NUM>, memory <NUM>, processor <NUM>, communication interface <NUM>, etc. according to the example process/method. The example process includes receiving (Block S108) by the UDM node, such as by messenger <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, a registration request from a home subscriber server, HSS, node, the registration request being to register an Internet Protocol-Short Message-Gateway, IP-SM-GW, and the registration request comprising an address of the IP-SM-GW. The method includes optionally, as a result of receiving the registration request comprising the address of the IP-SM-GW from the HSS node, determining (Block S110), such as by messenger <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, message waiting data.

In some embodiments, the method includes confirming, such as by messenger <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, the registration of the IP-SM-GW in a response message to the HSS node. In some embodiments, the method includes storing, such as by messenger <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, the received address of the IP-SM-GW in a unified data repository, UDR, node as part of the registration of the IP-SM-GW. In some embodiments, the method includes as a result of the registration of the IP-SM-GW and/or the received registration request comprising the address of the IP-SM-GW, one or more of: determining, such as by messenger <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, whether message waiting data are stored for a user associated with the IP-SM-GW; as a result of determining that the message waiting data are stored for the user, alerting, such as by messenger <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, at least one Short Message Service, SMS, service center, SC, and receiving a request for routing information from the at least one SMS SC; and using, such as by messenger <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, the address to communicate with the IP-SM-GW to provide a mobile terminated short message service, MT SMS, to a user equipment, UE, associated with the user.

In some embodiments, the method includes one or more of: receiving, such as by messenger <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, from the HSS node, a de-registration request to de-register the IP-SM-GW, the de-registration request comprising the address of the IP-SM-GW; and confirming, such as by messenger <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, a de-registration of the IP-SM-GW in a response message to the HSS node. In some embodiments, the method includes removing, such as by messenger <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, the address of the IP-SM-GW from the UDR node as part of the de-registration of the IP-SM-GW. In some embodiments, one or more of: the HSS node comprises HSS functionality supporting Internet Protocol, IP, Multimedia Subsystem, IMS; and the HSS node lacks an HSS and/or Home Location Register, HLR, functionality supporting legacy access.

<FIG> is a flowchart of an exemplary process in an HSS node <NUM> for supporting delivery of an SMS message to the UE <NUM> according to one or more of the techniques in the present disclosure. One or more Blocks and/or functions and/or methods performed by the HSS node <NUM> may be performed by one or more elements of HSS node <NUM> such as via addresser <NUM> in processing circuitry <NUM>, memory <NUM>, processor <NUM>, communication interface <NUM>, etc. according to the example process/method. The example process includes receiving (Block S112), such as via addresser <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, a registration request. The method includes sending (Block S114), such as via addresser <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, to a unified data management, UDM, node, the registration request, the registration request being to register an Internet Protocol-Short Message-Gateway, IP-SM-GW, and the registration request comprising an address of the IP-SM-GW.

In some embodiments, the method further includes receiving, such as via addresser <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, from the UDM node, a confirmation of the registration of the IP-SM-GW in a response message. In some embodiments, the method further includes as a result of receiving a de-registration request, sending, such as via addresser <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, to the UDM node, the de-registration request to de-register the IP-SM-GW, the de-registration request comprising the address of the IP-SM-GW; and receiving, such as via addresser <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, a confirmation of the de-registration of the IP-SM-GW in a response message. In some embodiments, one or more of: the HSS node comprises HSS functionality supporting Internet Protocol, IP, Multimedia Subsystem, IMS; and the HSS node lacks an HSS and/or Home Location Register, HLR, functionality supporting legacy access.

Having generally described arrangements for supporting short message service (SMS) delivery in certain scenarios, a more detailed description of some of the embodiments are provided as follows with reference to <FIG>, and which may be implemented by UE <NUM>, UDM node <NUM>, HSS node <NUM> and/or any network node (e.g., network node <NUM>, UDR node, etc.) discussed herein.

Some embodiments of the present disclosure provide a new procedure to make the IP-SM-GW address available to the UDM node <NUM> in deployment scenarios where <NUM>/<NUM>/<NUM> accesses are not supported and support of SMS over IP is expected to be provided. Some example embodiments and/or alternatives to define the interactions that allow the UDM node <NUM> to obtain the IP-SM-GW address are described below with reference to the call flow diagrams in <FIG>, in which at least some notable steps are bolded below for clarity.

<FIG> shows an example call flow diagram for the registration of the IP-SM-GW address in the UDM node <NUM> and subsequent SMS routing information retrieval, as shown in the following call flow diagram steps:.

After successful registration of the IP-SM-GW's <NUM> address, the UDM node <NUM> determines whether message waiting data are stored and alerts all Service Centres using procedures described in, for example, 3GPP TS <NUM> if applicable.

The UDM node <NUM> receives a request for routing information from the SMS-GMSC <NUM> via MAP or Diameter. If the 5GS-UDR is used, the UDM node <NUM> queries the 5GS-UDR to read the registered Short Message Service Function (SMSF) and/or IP-SM-GW <NUM>, if any. Routing information is provided to SMS-GMSC <NUM> from IP-SM-GW <NUM> or UDM node <NUM>.

The options 5a-5f, i.e., steps S124-S136 shown in <FIG> are based on the options for MT SMS procedure described in section <NUM> of 3GPP TS <NUM>, considering a 5GC only deployment where the UDM node <NUM> is present and HLR/HSS serving <NUM>/<NUM>/<NUM> accesses are not deployed. Steps 5a-5c correspond to 3a-3c; step 5d corresponds to 3d; and steps 5e-5f correspond to 3e-3f, respectively, as shown in figure <NUM> of 3GPP TS <NUM>.

<FIG> shows an example call flow diagram for the deregistration of the IP-SM-GW <NUM> address in the UDM node <NUM>, as shown in the following call flow diagram steps:.

In addition, or alternatively, in some embodiments, when the UDM node <NUM> receives a request for routing information from the SMS-GMSC <NUM> via MAP or Diameter, the UDM node <NUM> may determine in the HSS node <NUM> (IMS) if there is an IP-SM-GW <NUM> address.

<FIG> shows an example call flow diagram for the retrieval of the IP-SM-GW <NUM> address from the HSS node <NUM> (IMS) by the UDM node <NUM> upon reception of an SMS routing information request, as shown in the following call flow diagram steps:.

Additionally, and/or alternatively, the registration and deregistration of the IP-SM-GW <NUM> address in the UDM node <NUM> may be performed by direct interaction from the HSS node <NUM> (IMS) to 5GS-UDR (e.g., network node 36b).

<FIG> shows an example call flow diagram for the registration (or deregistration) of the IP-SM-GW <NUM> address in the 5GS-UDR (e.g., network node 36b) and subsequent SMS routing information retrieval, as shown in the following call flow diagram steps:.

It should be understood that although the example embodiments discussed herein may use one or another type of message or one or another network node arrangement or context, the techniques disclosed herein may be used with other types of messages or other types of network architecture arrangements or other contexts, to support SMS delivery according to the techniques provided in this disclosure.

Some embodiments of the present disclosure provide for one or more new procedures to allow the IP-SM-GW address to become available to the UDM in deployment scenarios where, for example, <NUM>/<NUM>/<NUM> accesses are not supported and/or support of SMS over IP is to be provided.

Claim 1:
A method implemented in a unified data management, UDM, node (<NUM>), the method comprising:
receiving (S118), by the UDM node (<NUM>), a registration request from a home subscriber server, HSS, node (<NUM>), the registration request being to register an Internet Protocol-Short Message-Gateway, IP-SM-GW (<NUM>), and the registration request comprising an address of the IP-SM-GW (<NUM>); and
as a result of the registration of the IP-SM-GW (<NUM>) and/or the received registration request comprising the address of the IP-SM-GW (<NUM>):
determining whether message waiting data are stored for a user served by the IP-SM-GW (<NUM>);
as a result of determining that the message waiting data are stored for the user, alerting at least one Short Message Service, SMS, service center, SC; and
in response to receiving (S134) a request for routing information from a Short Message Service-Gateway Mobile Switching Center, SMS-GMSC (<NUM>),
providing (S136) the address to the SMS-GSMC (<NUM>) to enable communication between the SMS-GMSC (<NUM>) with the IP-SM-GW (<NUM>) to provide a mobile terminated short message service, MT SMS, to a user equipment, UE, associated with the user.