Enhancement of service-based interface-based short message service

Abstract

According to one aspect, a method for providing routing information associated with a short message service (SMS) message and a user equipment (UE) is described. The method includes determining that the second network node is to be used for routing the SMS message based on a request for the routing information, the request being received from the third network node and transmitting to the second network node a 3GPP access registration information for SMS and a non-3GPP access registration information for SMS. The 3GPP access registration information for SMS includes a first identifier identifies a first SMS function (SMSF) instance serving the UE in the 3GPP access, and the non-3GPP access registration information for SMS comprising a second identifier identifies a second SMSF instance serving the UE in the non-3GPP access.

Description

[0001] ENHANCEMENT OF SERVICE-BASED INTERFACE-BASED SHORT

[0002] MESSAGE SERVICE

[0003] TECHNICAL FIELD

[0004] The present disclosure relates to wireless communications, and in particular, to processes and / or routing information associated with service-based interface (SBI)-based short message service (SMS).

[0005] BACKGROUND

[0006] The Third Generation Partnership Project (3 GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile user equipments (UE), as well as communication between network nodes and between WDs. The 3 GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

[0007] As described in 3GPP Technical Specification (TS) 23.540 V18.2.0, the following different approaches may be used to deliver mobile terminated (MT) short message for the service-based interface (SBI)-based short message service (SMS):

[0008] Successful MT short message transfer without SMS Router / Internet Protocol (IP) short message gateway (IP-SM-GW) in chapter 5.1.2 of 3GPP TS 23.540 V18.2.0;

[0009] Successful MT short message transfer via SMS Router in chapter 5.1.3 of 3GPP TS 23.540 V18.2.0; and

[0010] Successful MT short message transfer via IP-SM-GW in chapter 5.1.4 of 3GPP TS 23.540 V18.2.0.

[0011] The latter two mechanisms may include the unified data management (UDM) creating the routing information for the UE by sending Nipsmgw_SMService_RoutingInfo, or Nrouter_SMService_RoutingInfo, e.g., Step 4 of FIG. 1. FIG. 1 may include one or more steps S1-S17 which may correspond to steps 1-17 shown in chapter 5.1.4 of 3GPP TS 23.540 V18.2.0. When the IP-SM-GW or SMS-Router receives the MT message, the IP-SM-GW or SMS-Router may find the SMS function (SMSF) instance, and forward the message to the SMSF instance, and finally to the UE. Further, the following information of Table 1 (e.g., as described in 3GPP TS 29.577 V18.2.0, section 6.1.6.2.2 -Type: CreateRoutingData) may be included in the request from the UDM to the IP-SM-GW, or SMS-Router.

[0012] Table 1: Definition of type CreateRoutingData

[0013] In addition, based on the description in the chapter 5.16.2.2 - SMS over non-access stratum (NAS) transport in 3GPP TS 23.501 V18.4.0, “5G System supports SMS over NAS via both 3GPP access and non-3GPP access.” The description of the bullet 1-3 of the chapter 4.13.3.6 of 3GPP TS 23.502 V18.4.0 further described that “if there are two AMFs serving the UE, one is for 3GPP access and another is for non-3GPP access, there are two SMSF addresses stored in UDM / UDR. The UDM may return both SMSF addresses.” The term AMF may refer to Access and Mobility Management Function.

[0014] When the UE has 3GPP access, and non-3GPP access from the different public land mobile networks (PLMNs), and with SMS Over NAS feature activated, multiple SMSFs may register into the UDM as shown in FIG. 2. More specifically, FIG. 2 shows a local breakout (LBO) roaming architecture for a 5G Core Network with untrusted non- 3GPP access - N3IWF in a different PLMN from 3GPP access. FIG. 2 may correspond to FIG. 4.2.8.2.2-2 of 3GPP TS 23.501 V18.4.0.

[0015] The SMS over NAS also supports the roaming scenario. FIG. 3 shows a roaming architecture for SMS over NAS in reference point representation, e.g., as shown in FIG. 4.4.2.1-4 of 3GPP TS 23.501 V18.4.0. In the roaming scenario, the UDM, IP-SM-GW and SMS-Router may be in the home PLMN (HPLMN) of the UE acting as SMS Receiver, and SMS gateway mobile switching center (SMS-GMSC) may be in the HPLMN of the UE acting as SMS Sender. FIG. 4 shows an HPLMN of an SMS Sender (first UE) and an HPLMN of an SMS Receiver (second UE), where the HPLMNs may be one PLMN. Steps S18-S25 are shown.

[0016] When the SBLbased SMS is deployed, the MT short message is delivered via the IP-SM-GW or SMS-Router from the SMS-GMSC to the SMSF, and finally to the UE. There are two problems with the current specification:

[0017] It does not support the UE acting as SMS Receiver roaming to other PLMN. When the UE is roaming to another PLMN, i.e. VPLMN, the SMSF instance serving this UE is located in the VPLMN, and the IP-SM-GW or SMS-Router may be in the HPLMN of the UE, so it may require the target PLMN information of SMSF besides the SMF instance identifier (ID) when the IP- SM-GW or SMS-Router wants to have a Inter PLMN Discovery for the SMSF via the network repository functions (NRFs) (e.g. visited NRF (vNRF) and home NRF (hNRF)) to forward the MT short message. However, in the current 3GPP specifications, only SMSF instance ID is provided by the UDM to the IP-SM-GW or SMS-Router in step S4 of FIG. 1 in the CreateRoutingData element or message. When the SMS Receiver is roamed to another PLMN, then it will not be possible to forward the MT short message by the IP-SM-GW or SMS-Router to the SMSF. FIG. 5 shows steps S27-S34 of an example interaction between network functions (NFs). SMS Sender and SMS Receiver are the subscribers of HPLMN, but the SMS Receiver is roamed to VPLMN. When the UE acting as SMS Receiver is served by two SMSF instances for the 3GPP access and non-3GPP access in the different PLMNs, the UDM only provides one SMSF instance ID to the IP-SM-GW and SMS-Router in step S30 of the diagram above. If the IP-SM-GW or SMS-Router cannot reach the SMS instance provided by the UDM for the MT Short message, then it will not be possible to deliver the MT short message to another SMSF instance in another access.

[0018] SUMMARY

[0019] Some embodiments advantageously provide methods, systems, and apparatuses for performing processes and / or providing routing information associated with servicebased interface (SBI)-based short message service (SMS).

[0020] One or more embodiments address the problems of existing technologies and may provide one or both of: the PLMN information of SMSF may be provided or included (e.g., in a message, indication, etc.) so the IP-SM-GW or SMS-Router can find the corresponding SMSF instance when it is located in another PLMN, e.g., with the Inter PLMN discovery described in the chapter 4.17.5 NF / NF corresponding to service discovery across PLMNs in the case of discovery made by NF service consumer, e.g., as described in 3GPP TS 23.502 V18.4.0; and both SMSF information for 3GPP access and non-3GPP access may be provided or included (e.g., in a message, indication, etc.) so the IP-SM-GW or SMS-Router can forward the MT short message to the second SMSF instance if the first SMS instance cannot be used to deliver the message.

[0021] In some cases, such as for MT SMS without SMS router / IP-SM GW, the UDM provides the routing information to the SMS-GMSC with SMF instance for 3GPP and non-3GPP access as well as the PLMN ID if roaming (e.g., as in 3GPP TS 23.540 V18.2.0, 5.1.2). In some embodiments, if UDM determines that an SMS router / IP-SM- GW should be used for routing the SMS message, the UDM receives a request for routing information (e.g., in an Nudm_UECM_SendRoutingInfoForSM message, indication, etc.) from SMS-GMSC and the UDM determines SMS router / IP-SM- GW should be used, the UDM sends the routing information (e.g., in a Nrouter / ipsmgw_SMService_RoutingInfo message, indication, etc.) to either router / IP-SM- GW (comprising the SMSF instances for 3 GPP and non-3GPP and PLMN ID for roaming).

[0022] In one or more embodiments, the SBLbased SMS may be completely working as the non-SBI based SMS. That is, besides the original short message functionality, a UE such as an SMS Receiver roaming to another PLMN is supported. In addition, successful delivery of MT short message may be provided when there are multiple SMSF instances serving the UE.

[0023] According to one aspect, a method for providing routing information associated with a short message service (SMS) message, a first user equipment (UE), and a second UE is described. The SMS message is to be provided 3rd Generation Partnership Project (3GPP) access and non-3GPP access. The method is implemented in a first network node, which is a unified data management (UDM) network node and is configured to communicate with a second network node and a third network node. The second network node is an internet protocol (IP) short message gateway (IP-SM-GW) network node or an SMS router network node. The method includes determining that the second network node is to be used for routing the SMS message based on a request for the routing information, where the request is received from the third network node, and transmitting the routing information to the second network node. The routing information includes one or more SMS function (SMSF) instances for the 3GPP access and the non-3GPP access, and a public land mobile network identifier (PLMN ID) for roaming.

[0024] In some embodiments, the third network node is a SMS gateway mobile switching center (SMS-GMSC) network node.

[0025] In some other embodiments, transmitting the routing information includes transmitting, to the second network node, PLMN information associated with the one or more SMSF instances. The PLMN information is usable by the second network node to find a corresponding SMSF instance located in another PLMN with inter-PLMN discovery.

[0026] In some embodiments, transmitting the routing information includes transmitting, to the second network node, information associated with the one or more SMSF instances for the 3GPP access and the non-3GPP access. The information associated with the SMSF instances for the 3GPP access and the non-3GPP access is usable by the second network node to forward the SMS message to a second SMSF instance if a first SMS instance cannot be used to deliver the SMS message.

[0027] In some other embodiments, the first UE is an SMS sender of the SMS message, and the second UE is an SMS receiver of the SMS message.

[0028] In some embodiments, the 3GPP access is provided via a first PLMN and the non- 3GPP access is provided via a second PLMN.

[0029] According to another aspect, a first network node configured to provide routing information associated with a short message service (SMS) message, a first user equipment (UE) and a second UE is described. The SMS message is to be provided 3rd Generation Partnership Project (3 GPP) access and non-3GPP access. The first network node is a unified data management (UDM) network node and is configured to communicate with a second network node and a third network node. The second network node is an internet protocol (IP) short message gateway (IP-SM-GW) network node or an SMS router network node. The first network node is configured to determine that the second network node is to be used for routing the SMS message based on a request for the routing information, where the request is received from the third network node and transmit the routing information to the second network node. The routing information includes one or more SMS function (SMSF) instances for the 3GPP access and the non- 3GPP access, and a public land mobile network identifier (PLMN ID) for roaming.

[0030] In some embodiments, the third network node is a SMS gateway mobile switching center (SMS-GMSC) network node.

[0031] In some other embodiments, transmitting the routing information includes transmitting, to the second network node, PLMN information associated with the one or more SMSF instances. The PLMN information is usable by the second network node to find a corresponding SMSF instance located in another PLMN with inter-PLMN discovery.

[0032] In some embodiments, transmitting the routing information includes transmitting, to the second network node, information associated with the one or more SMSF instances for the 3GPP access and the non-3GPP access. The information associated with the SMSF instances for the 3GPP access and the non-3GPP access is usable by the second network node to forward the SMS message to a second SMSF instance if a first SMS instance cannot be used to deliver the SMS message.

[0033] In some other embodiments, the first UE is an SMS sender of the SMS message, and the second UE is an SMS receiver of the SMS message.

[0034] In some embodiments, the 3GPP access is provided via a first PLMN and the non- 3GPP access is provided via a second PLMN.

[0035] According to one aspect, a method for providing routing information associated with a short message service (SMS) message and a user equipment (UE) is described. The SMS message is to be provided over 3rd Generation Partnership Project (3GPP) access and non-3GPP access. The method is implemented in a first network node. The first network node is a unified data management (UDM) network node and is configured to communicate with a second network node and a third network node. The second network node is an internet protocol (IP) short message gateway (IP-SM-GW) network node or an SMS router network node. The method includes determining that the second network node is to be used for routing the SMS message based on a request for the routing information, where the request is received from the third network node, and transmitting to the second network node a 3GPP access registration information for SMS and a non-3GPP access registration information for SMS. The 3GPP access registration information for SMS includes a first identifier that identifies a first SMS function (SMSF) instance serving the UE in the 3GPP access, and the non-3GPP access registration information for SMS comprising a second identifier identifies a second SMSF instance serving the UE in the non-3GPP access.

[0036] In some embodiments, the first identifier and the second identifier are the same and identify the same SMSF instance.

[0037] In some other embodiments, the third network node is an SMS gateway mobile switching center (SMS-GMSC) network node.

[0038] In some embodiments, the 3GPP access registration information for SMS further comprises a 3GPP access type, and the non-3GPP access registration information for SMS further comprises a non-3GPP access type.

[0039] In some other embodiments, the 3GPP access registration information for SMS and the non-3GPP access registration information for SMS is usable by the second network node to forward the SMS message to the second SMSF instance if the first SMSF instance cannot be used to deliver the SMS message.

[0040] In some embodiments, the 3GPP access registration information for SMS further comprises a first public land mobile network identifier (PEMN ID) for a first PLMN serving the UE in the 3GPP access, and the non-3GPP access registration information for SMS further comprises a second PLMN ID for a second PLMN serving the UE in the non 3 GPP access.

[0041] In some other embodiments, the first PLMN and the second PLMN are the same PLMN.

[0042] In some embodiments, one or both of the first identifier identifying the first SMSF instance and the second identifier identifying the second SMSF instance are kept by the first network node for backwards-compatibility and are included in the corresponding SMSF registration information parameters.

[0043] According to another aspect, a first network node configured for providing routing information associated with a short message service (SMS) message and a user equipment (UE) is described. The SMS message is to be provided over 3rd Generation Partnership Project (3GPP) access and non-3GPP access. The method is implemented in a first network node. The first network node is a unified data management (UDM) network node and is configured to communicate with a second network node and a third network node. The second network node is an internet protocol (IP) short message gateway (IP-SM-GW) network node or an SMS router network node. The first network node is configured to perform one or more steps corresponding to one or more of the method embodiments implemented in the first network node and / or one or more features associated with the first network node are similar to or the same as the features described in the method embodiments implemented in the first network node.

[0044] According to one aspect, a method for routing a short message service (SMS) message that is to be delivered to a user equipment (UE) is described. The SMS message is to be provided over a 3rd Generation Partnership Project (3GPP) access and a non- 3 GPP access. The method is implemented in a second network node configured to communicate with a first network node. The first network node is a unified data management (UDM) network node. The second network node is an internet protocol (IP) short message gateway (IP-SM-GW) network node or an SMS router network node. The method includes obtaining a 3GPP access registration information for SMS and a non- 3GPP access registration information for SMS. The 3GPP access registration information for SMS comprises a first identifier identifying a first SMS function (SMSF) instance serving the UE in the 3GPP access and a first public land mobile network identifier (PLMN ID) for a first PLMN serving the UE in the 3GPP access. The non-3GPP access registration information for SMS comprises a second identifier identifying a second SMSF instance serving the UE in the non-3GPP and a second PLMN ID for a second PLMN serving the UE in the non 3GPP access. The method also includes receiving the SMS message to be delivered to the UE, selecting, based on a local policy, the first SMSF instance or the second SMSF instance to deliver the SMS message to the UE, and if the first SMSF instance or the second SMSF instance that is selected fails to deliver the SMS to the UE, selecting the other second or first SMSF instance to deliver the SMS message to the UE.

[0045] In some embodiments, the first identifier and the second identifier are the same and identify the same SMSF instance. In some other embodiments, the 3GPP access registration information for SMS further comprises a 3GPP access type, and the non-3GPP access registration information for SMS further comprises a non-3GPP access type.

[0046] In some embodiments, the first PLMN and the second PLMN are the same PLMN.

[0047] In some other embodiments, the method further includes causing the first SMSF instance or the second SMSF instance that is selected to deliver SMS message to the UE.

[0048] According to another aspect, a second network node configured for routing a short message service (SMS) message that is to be delivered to a user equipment (UE) is described. The SMS message is to be provided over a 3rd Generation Partnership Project (3GPP) access and a non-3GPP access. The method is implemented in a second network node configured to communicate with a first network node. The first network node is a unified data management (UDM) network node. The second network node is an internet protocol (IP) short message gateway (IP-SM-GW) network node or an SMS router network node. The second network node is configured to perform one or more steps corresponding to one or more of the method embodiments implemented in the second network node and / or one or more features associated with the first network node are similar to or the same as the features described in the method embodiments implemented in the second network node.

[0049] BRIEF DESCRIPTION OF THE DRAWINGS

[0050] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0051] FIG. 1 shows an example process associated with routing information;

[0052] FIG. 2 shows an example local breakout (LBO) roaming architecture for a 5G Core Network with untrusted non-3GPP access in a PLMN different from 3GPP access;

[0053] FIG. 3 shows an example roaming architecture for SMS over NAS in reference point representation;

[0054] FIG. 4 shows an example HPLMN of an SMS Sender (first UE) and another example HPLMN of an SMS Receiver (second UE);

[0055] FIG. 5 shows an example interaction between network functions (NFs); FIG. 6 is a schematic diagram of an example network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure;

[0056] FIG. 7 is a block diagram of a host computer communicating via a network node with a user equipment over an at least partially wireless connection according to some embodiments of the present disclosure;

[0057] FIG. 8 is a flowchart of an example process in a network node according to some embodiments of the present disclosure;

[0058] FIG. 9 is a flowchart of another example process in a network node according to some embodiments of the present disclosure;

[0059] FIG. 10 is a flowchart of an example process in a network node according to some embodiments of the present disclosure;

[0060] FIG. 11 shows an example process according to some embodiments of the present disclosure;

[0061] FIG. 12 shows another example process according to some embodiments of the present disclosure; and

[0062] FIG. 13 shows another example process according to some embodiments of the present disclosure.

[0063] DETAILED DESCRIPTION

[0064] Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to performing processes and / or providing routing information associated with service-based interface (SBI)-based short message service (SMS). 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. Like numbers refer to like elements throughout the description.

[0065] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0066] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

[0067] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections.

[0068] The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multistandard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment, UDM, IP-SM-GW, SMS-GMSC, SMSF, SC, etc. The term “radio node” used herein may be used to also denote a user equipment (UE) such as a wireless device (WD) or a radio network node.

[0069] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The UE herein can be any type of wireless device capable of communicating with a network node or another UE over radio signals, such as a wireless device (WD). 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 (loT) device, or a Narrowband loT (NB-IOT) device, etc.

[0070] Also, in some embodiments, the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell / multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

[0071] In some embodiments, the term “3GPP access” is used and may refer to one or more 3GPP functions and / or resources to which a device (e.g., UE) or node (e.g., network node) may gain access or that the device or node may be provided with. In some embodiments, the term “non-3GPP access” is used and may refer to one or more non- 3GPP functions and / or resources to which a device (e.g., UE) or node (e.g., network node) may gain access or that the device or node may be provided with. 3GPP functions and / or resources may refer to functions and resources corresponding to one or more 3GPP standards, specifications, etc. Non-3GPP functions and / or resources may refer to functions and resources other than 3GPP functions and / or resources. Resources may refer to network nodes, UEs, signaling resources, etc.

[0072] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or 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. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

[0073] Note further, that functions described herein as being performed by a user equipment or a network node may be distributed over a plurality of user equipments and / or network nodes. In other words, it is contemplated that the functions of the network node and user equipment described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0074] Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 6 a schematic diagram of a communication system 10, according to an embodiment, such as a 3 GPP-type cellular network that may support standards such as LTE and / or NR (5G), which comprises an access network 12, such as a radio access network (RAN) 12, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c and core network 14 may include one or more network nodes 16 such as network node 16d. Network nodes 16a, 16b, 16c, 16d may be referred to collectively as network nodes 16 and may be NBs, eNBs, gNBs or other types of wireless access points. Some of the network nodes 16 such as network nodes 16a, 16b, 16c may define a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 (and / or network node 16d) over a wired or wireless connection 20. A first UE 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second UE 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of UEs 22a, 22b (collectively referred to as UEs 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding network node 16. Note that although only two UEs 22 and three network nodes 16 are shown for convenience, the communication system may include many more UEs 22 and network nodes 16. Core network 14 may include one or more core network nodes (also referred to herein as network nodes 16) having hardware and / or software that generally corresponds to the hardware and / or software in network node 16, but arranged to perform the functions of the particular core network node as opposed to a network node 16 in the access network 12.

[0075] Also, it is contemplated that a UE 22 can be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a UE 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, UE 22 can be in communication with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN or an access node such as may be defined / used in future 3GPP access networks such as 6G RAN and future RAN generations.

[0076] A network node 16 is configured to include a node management unit 24 which is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., network node functions. A UE 22 is configured to include a UE management unit 26 which is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., UE functions.

[0077] Any components of system 10 may be comprised or associated with at least one PLMN 11, e.g., access network 12, core network 14, etc. Further, any of the radio access network 12 (and / or its components such as network nodes 16 and / or UEs 22) and / or core network 14 may be in communication with any other network such as a cloud network. Although not shown, core network 14 may include one or more network nodes 16 (and / or UEs 22).

[0078] Example implementations, in accordance with an embodiment, of the UE 22 and network node 16 discussed in the preceding paragraphs will now be described with reference to FIG. 7.

[0079] The communication system 10 includes a network node 16 provided in a communication system 10. Network node 16 includes hardware 28 enabling it to communicate with the UE 22. The hardware 28 may include a radio interface 30 for setting up and maintaining at least a wireless connection 32 with a UE 22 located in a coverage area 18 served by the network node 16. The radio interface 30 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 30 includes an array of antennas 31 to radiate and receive signal(s) carrying electromagnetic waves. In some embodiments, radio interface 30 may be configured for setting up and maintaining at least a wireless / wired connection with other network nodes 16. In some embodiments, network node 16 may include a communication interface 34 configured to perform functions similar to the radio interface functions, e.g., communicate with other network nodes 16 via wired or wireless links.

[0080] In the embodiment shown, the hardware 28 of the network node 16 further includes processing circuitry 36. The processing circuitry 36 may include a processor 38 and a memory 40. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 36 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. The processor 38 may be configured to access (e.g., write to and / or read from) the memory 40, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0081] Thus, the network node 16 further has software 42 stored internally in, for example, memory 40, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 42 may include application 44 which may include software application configured to provide application functions, such as a functions associated with a service provided to UE 22.

[0082] The software 42 may be executable by the processing circuitry 36. The processing circuitry 36 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 network node 16. Processor 38 corresponds to one or more processors 38 for performing network node 16 functions described herein. The memory 40 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 42 may include instructions that, when executed by the processor 38 and / or processing circuitry 36, causes the processor 38 and / or processing circuitry 36 to perform the processes described herein with respect to network node 16. For example, processing circuitry 36 of the network node 16 may include a node management unit 24 which is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., network node functions.

[0083] The communication system 10 further includes the UE 22 already referred to. The UE 22 may have hardware 46 that may include a radio interface 48 configured to set up and maintain a wireless connection 32 with a network node 16 serving a coverage area 18 in which the UE 22 is currently located. The radio interface 48 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 48 includes an array of antennas 50 to radiate and receive signal(s) carrying electromagnetic waves. In some embodiments, UE 22 may include a communication interface configured to perform functions similar to radio interface 48, e.g., communicate with other UEs 22 via wired or wireless links.

[0084] The hardware 46 of the UE 22 further includes processing circuitry 52. The processing circuitry 52 may include a processor 54 and memory 56. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 52 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. The processor 54 may be configured to access (e.g., write to and / or read from) memory 56, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0085] Thus, the UE 22 may further comprise software 58, which is stored in, for example, memory 56 at the UE 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the UE 22. The software 58 may be executable by the processing circuitry 52. The software 58 may include an application 60. The application 60 may be operable to provide a service to a human or non-human user via the UE 22 and / or be configured to provide application client functions, e.g., associated with application 44.

[0086] The processing circuitry 52 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 UE 22. The processor 54 corresponds to one or more processors 54 for performing UE 22 functions described herein. The UE 22 includes memory 56 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 58 and / or the application 60 may include instructions that, when executed by the processor 54 and / or processing circuitry 52, causes the processor 54 and / or processing circuitry 52 to perform the processes described herein with respect to UE 22. For example, the processing circuitry 52 of the UE 22 may include UE management unit 26 which is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., UE functions.

[0087] In some embodiments, the inner workings of the network node 16 and UE 22 may be as shown in FIG. 7 and independently, the surrounding network topology may be that of FIG. 6.

[0088] The wireless connection 32 between the UE 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and / or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc. In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.

[0089] Although FIGS. 6 and 7 show various “units” such as node management unit 24 and UE management unit 26 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0090] FIG. 8 is a flowchart of an example process in a network node 16, e.g., a first network node 16a. The first network node 16a is configured to provide routing information associated with a short message service (SMS) message, a first user equipment (UE) 22a and a second UE 22b. The SMS message is to be provided 3rd Generation Partnership Project (3 GPP) access and non-3GPP access. The first network node 16a is a unified data management (UDM) network node (or similar network node, e.g., depending on the type of core network, i.e., 3GPP 5G, 3GPP 6G core network, etc.) and is configured to communicate with a second network node 16b and a third network node 16c. The second network node 16b is an internet protocol (IP) short message gateway (IP-SM-GW) network node or an SMS router network node. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the node management unit 24), processor 38, radio interface 30 and / or communication interface 34. Network node 16 such as via processing circuitry 36 and / or processor 38 and / or radio interface 30 and / or communication interface 34 is configured to determine (Block S100) that the second network node 16b is to be used for routing the SMS message based on a request for the routing information, where the request is received from the third network node 16c, and transmit (Block S102) the routing information to the second network node 16b. The routing information includes one or more SMS function (SMSF) instances for the 3GPP access and the non-3GPP access, and a public land mobile network identifier (PLMN ID) for roaming.

[0091] In some embodiments, the third network node 16c is a SMS gateway mobile switching center (SMS-GMSC) network node.

[0092] In some other embodiments, transmitting the routing information includes transmitting, to the second network node 16b, PLMN information associated with the one or 6more SMSF instances. The PLMN information is usable by the second network node 16b to find a corresponding SMSF instance located in another PLMN with inter- PLMN discovery.

[0093] In some embodiments, transmitting the routing information includes transmitting, to the second network node 16b, information associated with the one or more SMSF instances for instances for the 3GPP access and the non-3GPP access is usable by the second network node 16b to forward the SMS message to a second SMSF instance if a first SMS instance cannot be used to deliver the SMS message.

[0094] In some other embodiments, the first UE 22a is an SMS sender of the SMS message, and the second UE 22b is an SMS receiver of the SMS message.

[0095] In some embodiments, the 3GPP access is provided via a first PLMN 1 la and the non-3GPP access is provided via a second PLMN 11b.

[0096] FIG. 9 is a flowchart of an example process / method in a network node 16, e.g., a first network node 16. The method is for providing routing information associated with a short message service (SMS) message and a user equipment (UE). The SMS message is to be provided over 3rd Generation Partnership Project (3GPP) access and non-3GPP access. The method is implemented in a first network node 16. The first network node 16 is, for example, a unified data management (UDM) network node 16 in 5GS and is configured to communicate with a second network node 16 and a third network node 16. The second network node 16 is an internet protocol (IP) short message gateway (IP-SM-GW) network node 16 or an SMS router network node 16. One or more blocks described herein may be performed by one or more elements of the first network node 16 such as by one or more of processing circuitry 36 (including the node management unit 24), processor 38, radio interface 30 and / or communication interface 34. The first network node 16 such as via processing circuitry 36 and / or processor 38 and / or radio interface 30 and / or communication interface 34 is configured to determine (Block S104) that the second network node 16 is to be used for routing the SMS message based on a request for the routing information, where the request is received from the third network node 16. The network node 16 is also configured to transmit (Block S106) to the second network node 16 a 3GPP access registration information for SMS and a non-3GPP access registration information for SMS. The 3GPP access registration information for SMS includes a first identifier that identifies a first SMS function (SMSF) instance serving the UE 22 in the 3GPP access, and the non-3GPP access registration information for SMS comprising a second identifier identifies a second SMSF instance serving the UE 22 in the non-3GPP access.

[0097] In some embodiments, the first identifier and the second identifier are the same and identify the same SMSF instance.

[0098] In some other embodiments, the third network node 16 is an SMS gateway mobile switching center (SMS-GMSC) network node.

[0099] In some embodiments, the 3GPP access registration information for SMS further comprises a 3GPP access type, and the non-3GPP access registration information for SMS further comprises a non-3GPP access type.

[0100] In some other embodiments, the 3GPP access registration information for SMS and the non-3GPP access registration information for SMS is usable by the second network node 16 to forward the SMS message to the second SMSF instance if the first SMSF instance cannot be used to deliver the SMS message.

[0101] In some embodiments, the 3GPP access registration information for SMS further comprises a first public land mobile network identifier (PEMN ID) for a first PLMN serving the UE 22 in the 3GPP access, and the non-3GPP access registration information for SMS further comprises a second PLMN ID for a second PLMN serving the UE 22 in the non 3 GPP access.

[0102] In some other embodiments, the first PLMN and the second PLMN are the same PLMN.

[0103] In some embodiments, one or both of the first identifier identifying the first SMSF instance and the second identifier identifying the second SMSF instance are kept by the first network node 16 for backwards-compatibility and are included in the corresponding SMSF registration information parameters.

[0104] FIG. 10 is a flowchart of an example process / method in a network node 16, e.g., a second network node 16. The method is for routing a short message service (SMS) message that is to be delivered to a user equipment (UE). The SMS message is to be provided over a 3rd Generation Partnership Project (3GPP) access and a non-3GPP access. The method is implemented in a second network node 16 configured to communicate with a first network node 16. The first network node 16 is a unified data management (UDM) network node. The second network node 16 is an internet protocol (IP) short message gateway (IP-SM-GW) network node or an SMS router network node. One or more blocks described herein may be performed by one or more elements of the second network node 16 such as by one or more of processing circuitry 36 (including the node management unit 24), processor 38, radio interface 30 and / or communication interface 34. The second network node 16 such as via processing circuitry 36 and / or processor 38 and / or radio interface 30 and / or communication interface 34 is configured to obtain (Block S108) a 3GPP access registration information for SMS and a non-3GPP access registration information for SMS. The 3GPP access registration information for SMS comprises a first identifier identifying a first SMS function (SMSF) instance serving the UE 22 in the 3GPP access and a first public land mobile network identifier (PLMN ID) for a first PLMN serving the UE 22 in the 3GPP access. The non-3GPP access registration information for SMS comprises a second identifier identifying a second SMSF instance serving the UE 22 in the non-3GPP and a second PLMN ID for a second PLMN serving the UE 22 in the non 3GPP access. The second network node 16 is also configured to receive (Block SI 10) the SMS message to be delivered to the UE 22, select (Block S 112), based on a local policy, the first SMSF instance or the second SMSF instance to deliver the SMS message to the UE 22, and if the first SMSF instance or the second SMSF instance that is selected fails to deliver the SMS to the UE 22, select (Block S 114) the other second or first SMSF instance to deliver the SMS message to the UE 22.

[0105] In some embodiments, the first identifier and the second identifier are the same and identify the same SMSF instance.

[0106] In some other embodiments, the 3GPP access registration information for SMS further comprises a 3GPP access type, and the non-3GPP access registration information for SMS further comprises a non-3GPP access type.

[0107] In some embodiments, the first PLMN and the second PLMN are the same PLMN.

[0108] In some other embodiments, the method further includes causing the first SMSF instance or the second SMSF instance that is selected to deliver SMS message to the UE 22.

[0109] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for performing processes and / or providing routing information associated with service-based interface (SBI)-based short message service (SMS).

[0110] One or more UE 22 functions described below may be performed by one or more of processing circuitry 52, processor 54, UE management unit 26, radio interface 48, etc. One or more network node 16 functions described below may be performed by one or more of processing circuitry 36, processor 38, node management unit 24, radio interface 30, etc.

[0111] In some embodiments, routing data or information may be determined and / or provided to one or more components of system 10. The routing data or information may be part of a configuration usable by one or more components of system 10 to determine associated attributes and may include attribute name, data type, cardinality, description, applicability, etc. One or more embodiments provide a method that enables the network node 16 to create routing data in a second network node 16 (e.g., IP SM GW, SMS router). The created router data may also be referred to as SMSF routing data. One or more embodiments provide routing data attributes that may be created / updated, as included in for example CreateRoutingData according to the different implementation alternatives. In one alternative as shown in Table 2, additional SMS Instance Id and PLMN information (e.g., plmnld, additionalSmsfld, additionalPLmnld) are included individually, as illustrated in Table 2.

[0112] Modifications reflecting additional information to include in the create routing data sent from the first network node 16 (e.g., UDM) to second network node 16 (e.g., IP SM GW / SMS router), are shown herein using bold fonts.

[0113] Table 2: Type: CreateRoutingData (Corresponding to Table 6.1.6.2.2-1 of 3GPP

[0114] TS 29.577 V18.2.0)

[0115] Alternatively, the routing data information is included in one or more SmsfRegistrations for different access information as registered to the UDM by the SMSF (e.g.., smsf3Gpp, smsfNon3gpp). The UDM provides that information instead when creating or updating the second node with the routing data. Therefore an alternative Table 2 describing the attribute of a modified CreateRoutingData (of 3GPP TS 29.577

[0116] V18.2.0 - 6.1.6.2.2) is provided below in Table 3:

[0117] FIG. 11 shows an example process according to one or more embodiments. A UE 22a, HPLMN 1 la, a VPLMN 1 lb, and a UE 22b in the VPLMN 1 lb are shown. HPLMN I la may also include a UDM network node 16a, IP-SM-GW network node 16b, SM- GMSC network node 16c, a first SMF network node 16d, and a service center network node 16e. VPLMN 11b may include a second SMF network node 16f. The example process includes one or more of the following steps:

[0118] SMSF Registration Information (as described in clause 6.2.6.2.6 of 3GPP TS 29.503 V19.1.0)

[0119] Modifications to the procedure specified in the standard are shown herein using bold fonts.

[0120] S200. UE 22a (SMS Receiver) registers to 5GC, and with SMS over NAS functionality activated from both the 3GPP and Non-3GPP Access, and the UE 22a is served by the multiple SMSF instances, and this information may be registered in the UDM network node 16a as well. At the same time, the UE 22b (SMS Sender) registers to 5GS as well. More specifically, step S200 may include steps S200a, S200b, and S200c as shown, at step S200a, UE 22a (SMS receiver) registers to 5GC from the 3GPP access in HPLMN Ila with the SMS over NAS functionality on SMS network node 16d (e.g., SMSF 1). At step S200b, UE 22a (SMS receiver) registers to 5GC from the non-3GPP access in VPLMN 11b with the SMS over NAS functionality on SMS network node 16f (e.g., SMSF 2). At step S200c, UE 22b (SMS sender) registers to 5GC with the SMS over NAS functionality.

[0121] S202. The UE 22b (SMS Sender) sends a short message to another UE 22 (SMS Receiver) such as UE 22a (SMS Receiver) in another PLMN 11, e.g., by following steps 1-4 of Figure 5.2.2-1 in 3GPP TS 23.540 V18.2.0.

[0122] S204. The SC delivers the MT short message to SMS-GMSC network node 16c, e.g., as described in the Steps 1-2 of Figure 5.1.4-1 in 3GPP TS 23.540 V18.2.0. SMS- GMSC network node 16c invokes the Nnrf_NFDiscovery to discover and select the UDM instance(s) (or UDM network nodes 16a), supporting SMS SBI interfaces, and managing the user subscriptions of the generic public subscription identifier (GPSI).

[0123] S206. The SMS-GMSC invokes Nudm_UECM_SendRoutingInfoForSM (e.g., GPSI) to the UDM network node 16a to get the serving node information for all access types for UE 22.

[0124] S208. The UDM network node 16a shall or may invoke the Nipsmgw_SMService_RoutingInfo to provide the SMSF(s) information to the IP-SM-GW network node 16b. There may be one or more alternatives for signaling the SMSF(s) information. The SMSF(s) information may be provided as one or more attribute identifying the SMSFs such as the PLMN ID, additional SMSF instance ID and additional PLMN ID besides the original SMSF Instance ID, where the original SMSF instance ID is the SMSF instance that initially registered to UDM (used by UE over a first access) and additional SMSF instance ID represents the additional SMSF instance ID used for the additional access type. Alternatively, the UDM 16a provides to the IP-SM-GW 16b or (SMS Router ) the smsfRegistration for 3GPP access, and smsfRegistration for non-3GPP access (if one exists). The smsfRegistration for 3GPP access and the smsfRegistration for non 3GPP access attributes each include the full SMSF addressing information (i.e., SMSF access type, PLMN IDs, Diameter and MAP addresses...) and are described in 3GPP TS 29.503. The details attributes for the two alternatives are illustrated in table 2 and 3 further below.

[0125] S210. The IP-SM-GW network node 16b stores the routing information for a given UE 22 and sends Nipsmgw_SMService_RoutingInfo response to the UDM network node 16a.

[0126] S212. The UDM network node 15a responds to the SMS-GMSC network node 16c by sending Nudm_UECM_SendRoutingInfoForSM response, including the address of IP-SM-GW network node 16b or SMS Router.

[0127] S214. The SMS-GMSC network node 16c forwards the SMS message to the IP- SM-GW network node 16b or SMS Router.

[0128] S216. The IP-SM-GW network node 16b (or SMS Router) has more than one SMSF network node 16 (e.g. SMSF 1, and SMSF 2) address to use for SMS transport towards the UE 22, the IP-SM-GW network node 16b first chooses the address of the first SMSF network node 16d to use based on operator local policy to forward the SMS message to the UE. If the first SMSF network node 16d cannot deliver the short message to the UE 22, e.g., due to its own issue or other issues, the IP-SM-GW network node 16b (or SMS Router) can select another SMSF network node 16 (i.e. network node 16f (SMSF 2)) in the corresponding PLMN 11 (e.g., VPLMN 11b) to re-deliver the MT short message.

[0129] NOTE: It may be possible to only have one SMSF (or SMSF network node 16), which is in another PLMN 11, just as SMSF 2 (the second SMSF network node 16f).

[0130] S218. The MT Short message is delivered to the UE 22a (SMS Receiver), and the UE 22a (SMS Receiver) delivers the delivery report back to the SC network node 16e.

[0131] S220. SC network node 16c forwards the delivery report to the UE 22b (SMS Sender). S222. Additional steps may be performed, such as per 3GPP TS 23.540 V18.2.0.

[0132] In some embodiments, e.g., related to FIG. 11, the term “serving node information” is used and may refer to data requested from a third network node 16 (e.g., at step S206). Further, “routing information” or “routing data” is used and may refer to data sent from a first network node 16 (e.g., UDM) to the third network node 16 (e.g., IP SM GW / SMS router).

[0133] The SMSF ID that the UDM sends to the IP-SM-GW or SMS Router can be located in a different network (in roaming scenarios), so the UDM must add the PLMN- ID. Also, there might or may be an SMSF allocated for 3GPP access, and a different one for non-3GPP access.

[0134] In addition, if the IP-SM-GW and SMS Router are SBI-capable, their addressing information should not consist on IP-addressing (e.g. IP address, FQDN, ...) since this does not allow the consumer to invoke SBI services (critical information is missing, such as HTTP scheme, API version, API prefix, etc...). Instead, the NF Instance ID should be included, so the consumer can discover all these data, and also make use of SBI capabilities (such as discovering the NF Set of equivalent instances, for reliability).

[0135] The UDM includes the IP-SM-GW or SMS Router NF Instance ID is included along with the existing IP-based addressing information to the SMS-GMSC (third node). The following describes some modifications to the APIs described in TS 29.577 to support the embodiments herein:

[0136] 5.2.2.2.1 General

[0137] One or more embodiments provide backwards-compatible new features, with impacts on the following APIs:

[0138] - TS29577_ Nipsmgw_SMService.yaml

[0139] - TS29577_ Nrouter_SMService.yaml

[0140] The Routinginfo service operation shall or may be used to provide the SMSF Instance Id to the IP-SM-GW. It is used in the following procedures:

[0141] - Successful Mobile Terminated short message transfer via IP-SM-GW (e.g., clause 5.1.4 of 3GPP TS 23.540 V18.2.0).

[0142] - Unsuccessful Mobile Terminated short message transfer via IP-SM-GW (e.g., clause 5.1.6 of 3GPP TS 23.540 V18.2.0).

[0143] The NF Service Consumer (e.g., UDM, UDM network node 16a, etc.) may provide the SMSF Instance Id to the IP-SM-GW (e.g., IP-SM-GW network node 16b) by using the HTTP PUT method as shown in FIG. 12 (which corresponds to Figure 5.2.2.2.1-1 in TS 29.577 V18.2.0), which shows an example process of routing information creation, including one or more of the following steps:

[0144] S300. (corresponding to step S208 above) The NF Service Consumer (e.g. UDM or UDM network node 16a) shall or may send a PUT request to the resource representing the UE's Mobile Terminated Short Message Information resource (i.e. ... / mt- sms / {gpsi}) of the IP-SM-GW (e.g., IP-SM-GW network node 16b) to update or create the routing information for a given UE (CreateRouting Data). The pay load body of the PUT request shall or may include:

[0145] - SMSF Instance Id

[0146] - SMSF Registration information (for each access type)

[0147] NOTE: SMSF Instance Id is kept for backwards-compatibility reasons, but its content is included in the SMSF Registration information parameters.

[0148] The details of CreateRoutingData are proposed in Table 2 or alternatively Table 3).

[0149] S302a. (corresponding to step S210 above) If the resource does not exist (there is no previous routing information stored in IP-SM-GW for that user), IP-SM-GW (e.g., IP- SM-GW network node 16b) stores the received routing data and returns a "201 Created" response with the "Location" header containing the URI of the created resource. The PUT response body include CreatedRoutingData that can comprise (details illustrated in Table 4 or 5) :

[0150] - the IP address of the IP-SM-GW (e.g., IP-SM-GW network node 16b) (to be sent by the UDM to the SMS-GMSC); and / or

[0151] - the FQDN of the IP-SM-GW (e.g., IP-SM-GW network node 16b) (to be sent by the UDM to the SMS-GMSC); and / or

[0152] - the NF Instance ID of the IP-SM-GW (e.g., IP-SM-GW network node 16b).

[0153] S302b. If the resource exists (there is previous routing information stored in IP- SM-GW for that user), the IP-SM-GW (e.g., IP-SM-GW network node 16b) updates the routing data by replacing it with the received information and responds with "200 OK" or "204 No Content".

[0154] S302c. On failure, or redirection, one of the HTTP status codes (e.g., listed in Table 6.1.3.3.3.1-3 of 3GPP TS 23.577 V19.0.0) is returned.

[0155] Steps S300-S302c correspond to steps l-2c of Figure 5.2.2.2.1-1 (Routing Information creation) of 3GPP TS 29.577 V18.2.0. 5.3.2.2.1 General

[0156] The Routinginfo service operation shall or may be used to provide the SMSF

[0157] Instance Id to the SMS Router. It is or may be used in the following procedures:

[0158] - Successful Mobile Terminated short message transfer via SMS Router (see clause 5.1.3 of 3GPP TS 23.540 V18.2.0).

[0159] - Unsuccessful Mobile Terminated short message transfer via SMS Router (see clause 5.1.9 of 3GPP TS 23.540 V18.2.0).

[0160] The NF Service Consumer (e.g., UDM or UDM network node 16a) shall or may provide the SMSF Instance Id to the SMS Router (e.g., SMS Router network node 16b) by using the HTTP PUT method as shown in FIG. 13 (which corresponds to Figure 5.3.2.2.1 1).

[0161] S400. (corresponding to step S208 above) The NF Service Consumer (e.g., UDM or UDM network node 16a) shall or may send a PUT request to the resource representing the UE's Mobile Terminated Short Message Information resource (i.e. ... / mt- sms / {gpsi}) of the SMS Router (e.g., SMS Router network node 16b) to update or create the routing information for a given UE (CreateRoutingData). The payload body of the PUT request shall or may contain:

[0162] SMSF Instance Id

[0163] SMSF Registration information (for each access type)

[0164] NOTE: SMSF Instance Id is kept for backwards-compatibility reasons, but its content is included in the SMSF Registration information parameters.

[0165] The details of CreateRoutingData are proposed in Table 2 or alternatively Table 3).S402a. (corresponding to step S210 above) If the resource does not exist (there is no previous routing information stored in SMS Router for that user), SMS Router stores the received routing data and returns a "201 Created" response with the "Location" header containing the URI of the created resource.

[0166] The PUT response body include CreatedRoutingData that can comprise (details illustrated in Table 4 or 5 : the IP address of the SMS Router (e.g., SMS Router network node 16b) (to be sent by the UDM to the SMS-GMSC); and / or the FQDN of the SMS Router (e.g., SMS Router network node 16b) (to be sent by the UDM to the SMS-GMSC); and / or the NF Instance ID of the SMS Router (e.g., SMS Router network node

[0167] 16b). S402b. If the resource exists (there is previous routing information stored in SMS Router for that user), the SMS Router (e.g. SMS Router network node 16b) updates the routing data by replacing it with the received information and responds with "200 OK" or "204 No Content". S402c. On failure, or redirection, one of the HTTP status code (e.g., listed in Table

[0168] 6.2.3.3.3.1-3) shall or may be returned.

[0169] Type: CreatedRoutingData

[0170] Table 4 (or Table 6.1.6.2.3-1): Definition of type CreatedRoutingData

[0171]

[0172] Type:CreatedRoutingData

[0173] Table 5(or Table 6.2.6.2.2- 1): Definition of type CreatedRoutingData

[0174] Nipsmgw SMService API ... text not shown for clarity ...)

[0175] CreateRoutingData: description: Information used for creating or updating the routing information of the user. type: object required:

[0176] - sms fid properties: sms fid:

[0177] $ref: 'TS29571_CommonData.yaml# / components / schemas / NfInstanceId' smsf3Gpp:

[0178] $ref:

[0179] 'TS29503_Nudm_UECM.yaml# / components / schemas / SmsfRegistration' smsfNon3Gpp:

[0180] $ref:

[0181] 'TS29503_Nudm_UECM.yaml# / components / schemas / SmsfRegistration' supi:

[0182] $ref: 'TS2957 l_CommonData.yaml# / components / schemas / Supi' ipSmGwGuidancelnd: type: boolean default: false supportedFeatures :

[0183] $ref:

[0184] 'TS29571_CommonData.yaml# / components / schemas / SupportedFeatures'

[0185] CreatedRoutingData: description: Information used for receiving the MT SMS. type: object properties: ipsmgwlpv4:

[0186] $ref: 'TS2957 l_CommonData.yaml# / components / schemas / Ipv4Addr' ipsmgwlpv6:

[0187] $ref: 'TS2957 l_CommonData.yaml# / components / schemas / Ipv6Addr' ipsmgwFqdn:

[0188] $ref: 'TS2957 l_CommonData.yaml# / components / schemas / Fqdn' ipSmGwNflnstanceld:

[0189] $ref: 'TS29571_CommonData.yaml# / components / schemas / NfInstanceId' correlationld: type: string ipSmGwGuidance:

[0190] $ref:

[0191] TS29503_Nudm_UECM.yaml# / components / schemas / IpSmGwGuidance' supportedFeatures :

[0192] $ref:

[0193] 'TS29571_CommonData.yaml# / components / schemas / SupportedFeatures' ... text not shown for clarity ...)

[0194] Nrouter SMService API ... text not shown for clarity ...)

[0195] CreatedRoutingData: description: Information used for receiving the MT SMS. type: object properties: routerip v4:

[0196] $ref: 'TS2957 l_CommonData.yaml# / components / schemas / Ipv4Addr' routerlpv6:

[0197] $ref: 'TS2957 l_CommonData.yaml# / components / schemas / Ipv6Addr' routerFqdn:

[0198] $ref: 'TS2957 l_CommonData.yaml# / components / schemas / Fqdn' routerNflnstanceld:

[0199] $ref: 'TS29571_CommonData.yaml# / components / schemas / NfInstanceId' supportedFeatures : $ref:

[0200] 'TS29571_CommonData.yaml# / components / schemas / SupportedFeatures'

[0201] In some embodiments, the term “instance” may refer to a network node 16 that is configured to provide one or more functions associated with an instance of a predetermined function. In a nonlimiting example, an SMSF instance may refer to an SMSF network node 16 or a network node 16 configured to perform SMSF functions. However, the embodiments are not limited as such, and other instances (e.g., NF instance) may similarly refer to corresponding network nodes 16 (e.g.., NF network node 16).

[0202] The following is a nonlimiting list of example embodiments.

[0203] 1. A method for providing routing information associated with a short message service (SMS) message, a first user equipment (UE) 22a and a second UE 22b, the SMS message to be provided, for example, over or via 3rd Generation Partnership Project (3GPP) access and non-3GPP access, the method being implemented in a first network node 16a, the first network node 16 being a unified data management (UDM) network node and configured to communicate with a second network node 16b and a third network node 16c, the second network node being an internet protocol (IP) short message gateway (IP-SM-GW) network node 16b or an SMS router network node, the method comprising: determining (S100) that the second network node 16b is to be used for routing the SMS message based on a request for the routing information, the request being received from the third network node 16c; and transmitting (S102) the routing information to the second network node, the routing information comprising one or more SMS function (SMSF) instances for the 3GPP access and the non-3GPP access, and a public land mobile network identifier (PLMN ID) for roaming.

[0204] 2. The method of Embodiment 1, wherein the third network node 16c is a SMS gateway mobile switching center (SMS-GMSC) network node.

[0205] 3. The method of any one of Embodiments 1 and 2, wherein transmitting the routing information includes transmitting, to the second network node 16b, PLMN information associated with the one or more SMSF instances, the PLMN information being usable by the second network node 16b to find a corresponding SMSF instance located in another PLMN with inter-PLMN discovery.

[0206] 4. The method of any one of Embodiments 1-3, wherein transmitting the routing information includes transmitting, to the second network node 16b, information associated with the one or more SMSF instances for the 3GPP access and the non-3GPP access, the information associated with the SMSF instances for the 3GPP access and the non-3GPP access being usable by the second network node 16b to forward the SMS message to a second SMSF instance if a first SMS instance cannot be used to deliver the SMS message.

[0207] 5. The method of any one of Embodiments 1-4, wherein the first UE 22a is an SMS sender of the SMS message, and the second UE 22b is an SMS receiver of the SMS message.

[0208] 6. The method of any one of Embodiments 1-5, wherein the 3GPP access is provided via a first PLMN 1 la and the non-3GPP access is provided via a second PLMN 11b.

[0209] 7. A first network node 16a configured to provide routing information associated with a short message service (SMS) message, a first user equipment (UE) 22a and a second UE 22b, the SMS message to be provided 3rd Generation Partnership Project (3GPP) access and non-3GPP access, the first network node 16a being a unified data management (UDM) network node and configured to communicate with a second network node 16b and a third network node 16c, the second network node being an internet protocol (IP) short message gateway (IP-SM-GW) network node or an SMS router network node, the first network node 16a being configured to: determine that the second network node 16b is to be used for routing the SMS message based on a request for the routing information, the request being received from the third network node 16c; and transmit the routing information to the second network node, the routing information comprising one or more SMS function (SMSF) instances for the 3GPP access and the non-3GPP access, and a public land mobile network identifier (PLMN ID) for roaming.

[0210] 8. The first network node 16a of Embodiment 7, wherein the third network node 16c is a SMS gateway mobile switching center (SMS-GMSC) network node.

[0211] 9. The first network node 16a of any one of Embodiments 7 and 8, wherein transmitting the routing information includes transmitting, to the second network node 16b, PLMN information associated with the one or more SMSF instances, the PLMN information being usable by the second network node to find a corresponding SMSF instance located in another PLMN with inter-PLMN discovery. 10. The first network node 16a of any one of Embodiments 7-9, wherein transmitting the routing information includes transmitting, to the second network node 16b, information associated with the one or more SMSF instances for the 3GPP access and the non-3GPP access, the information associated with the SMSF instances for the 3GPP access and the non-3GPP access being usable by the second network node to forward the SMS message to a second SMSF instance if a first SMS instance cannot be used to deliver the SMS message.

[0212] 11. The first network node 16a of any one of Embodiments 7-10, wherein the first UE 22a is an SMS sender of the SMS message, and the second UE 22b is an SMS receiver of the SMS message.

[0213] 12. The first network node 16a of any one of Embodiments 7-11, wherein the 3 GPP access is provided via a first PLMN I la and the non-3GPP access is provided via a second PLMN 11b.

[0214] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0215] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0216] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0217] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0218] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0219] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

[0220] Abbreviations that may be used in the preceding description include:

[0221] IP-SM-GW IP-Short-Message-Gateway

[0222] MT Mobile Terminated

[0223] SC Service Centre

[0224] SMS Short Message Service

[0225] SMS GMSC Gateway MSC For Short Message Service

[0226] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings and following claims.

Claims

What is claimed is:

1. A method for providing routing information associated with a short message service, SMS, message and a user equipment, UE, (22) the SMS message to be provided over 3rd Generation Partnership Project, 3GPP, access and non-3GPP access, the method being implemented in a first network node (16), the first network node (16) being a unified data management, UDM, network node (16) and configured to communicate with a second network node (16) and a third network node (16), the second network node (16) being an internet protocol, IP, short message gateway, IP-SM-GW, network node (16) or an SMS router network node (16), the method comprising: determining (S104) that the second network node (16) is to be used for routing the SMS message based on a request for the routing information, the request being received from the third network node (16); and transmitting (S106) to the second network node (16) a 3GPP access registration information for SMS and a non-3GPP access registration information for SMS, the 3GPP access registration information for SMS comprising a first identifier identifying a first SMS function, SMSF, instance serving the UE (22) in the 3GPP access, the non-3GPP access registration information for SMS comprising a second identifier identifying a second SMSF instance serving the UE (22) in the non-3GPP access.

2. The method of Claim 1, wherein the first identifier and the second identifier are the same and identify the same SMSF instance.

3. The method of any one of Claims 1 and 2, wherein the third network node (16) is an SMS gateway mobile switching center, SMS-GMSC, network node (16).

4. The method of any one of Claims 1-3, wherein the 3GPP access registration information for SMS further comprises a 3GPP access type, and the non-3GPP access registration information for SMS further comprises a non-3GPP access type.

5. The method of any one of Claims 1-4, wherein the 3GPP access registration information for SMS and the non-3GPP access registration information for SMS is usable by the second network node (16) to forward the SMS message to thesecond SMSF instance if the first SMSF instance cannot be used to deliver the SMS message.

6. The method of any one of Claims 1-5, wherein the 3GPP access registration information for SMS further comprises a first public land mobile network identifier (PLMN ID) for a first PLMN serving the UE (22) in the 3GPP access, and the non-3GPP access registration information for SMS further comprises a second PLMN ID for a second PLMN serving the UE (22) in the non 3 GPP access.

7. The method of Claim 6, wherein the first PLMN and the second PLMN are the same PLMN.

8. The method of any one of Claims 1-7, wherein one or both of the first identifier identifying the first SMSF instance and the second identifier identifying the second SMSF instance are kept by the first network node (16) for backwards-compatibility and are included in the corresponding SMSF registration information parameters.

9. A first network node (16) configured for providing routing information associated with a short message service, SMS, message and a user equipment, UE, (22) the SMS message to be provided over 3rd Generation Partnership Project, 3GPP, access and non-3GPP access, the first network node (16) being a unified data management, UDM, network node (16) and configured to communicate with a second network node (16) and a third network node (16), the second network node (16) being an internet protocol, IP, short message gateway, IP-SM-GW, network node (16) or an SMS router network node (16), the first network node (16) being configured to perform one or more steps corresponding to one or more of Claims 1-8 and / or one or more features associated with the first network node (16) are similar to or the same as the features recited in Claims 1-8.

10. A method for routing a short message service, SMS, message that is to be delivered to a user equipment, UE, (22) the SMS message to be provided over 3rd Generation Partnership Project, 3GPP, access and non-3GPP access, the method being implemented in a second network node (16) configured to communicate with a first network node (16), the first network node (16) being a unified data management, UDM,network node (16), the second network node (16) being an internet protocol, IP, short message gateway, IP-SM-GW, network node (16) or an SMS router network node (16), the method comprising: obtaining (S108) a 3GPP access registration information for SMS and a non-3GPP access registration information for SMS, the 3GPP access registration information for SMS comprising a first identifier identifying a first SMS function, SMSF, instance serving the UE (22) in the 3 GPP access and a first public land mobile network identifier, PLMN ID, for a first PLMN serving the UE (22) in the 3GPP access, the non-3GPP access registration information for SMS comprising a second identifier identifying a second SMSF instance serving the UE (22) in the non-3GPP and a second PLMN ID for a second PLMN serving the UE (22) in the non 3GPP access; receiving (SI 10) the SMS message to be delivered to the UE (22); selecting (SI 12), based on a local policy, the first SMSF instance or the second SMSF instance to deliver the SMS message to the UE (22); and if the first SMSF instance or the second SMSF instance that is selected fails to deliver the SMS to the UE (22), selecting (SI 14) the other second or first SMSF instance to deliver the SMS message to the UE (22).

11. The method of Claim 10, wherein the first identifier and the second identifier are the same and identify the same SMSF instance.

12. The method of any one of Claims 10 and 11, wherein the 3 GPP access registration information for SMS further comprises a 3GPP access type, and the non-3GPP access registration information for SMS further comprises a non-3GPP access type.

13. The method of any one of Claims 10-12, wherein the first PLMN and the second PLMN are the same PLMN.

14. The method of any one of Claims 10-13, wherein the method further includes: causing the first SMSF instance or the second SMSF instance that is selected to deliver SMS message to the UE (22).

15. A second network node (16) configured for routing a short message service, SMS, message that is to be delivered to a user equipment, UE, (22) the SMS message to be provided over 3rd Generation Partnership Project, 3GPP, access and non- 3GPP access, the method being implemented in a second network node (16) configured to communicate with a first network node (16), the first network node (16) being a unified data management, UDM, network node (16), the second network node (16) being an internet protocol, IP, short message gateway, IP-SM-GW, network node (16) or an SMS router network node (16), the second network node (16) being configured to perform one or more steps corresponding to one or more of Claims 10-14 and / or one or more features associated with the second network node (16) are similar to or the same as the features recited in Claims 10-14.

Images