Patent Description:
The short message service (SMS) service is supported in the <NUM>rd Generation Partnership Project (3GPP) <NUM>th Generation System (5GS) and documented in, for example, 3GPP Technical Specification (TS) <NUM>/<NUM>.

The <FIG> flow diagram shows an example of UE registration for SMS in an example system <NUM> that includes a user equipment (UE) <NUM>, a unified data management (UDM) <NUM>, an access and mobility management function (AMF) <NUM> and a short message service function (SMSF) <NUM>. In step <NUM>, when a UE <NUM> registers to an AMF <NUM>, the AMF <NUM> can register to a SMSF <NUM> for short message service (SMS) over a non-access stratum (NAS) service authorization, as shown in steps <NUM>-<NUM>. Then, the SMSF <NUM> may in turn register to a UDM <NUM>, as shown in <FIG>. In step <NUM>, the AMF <NUM> sends a registration accept message to the UE <NUM>. References to figures in <FIG>, refer to the figures in 3GPP TS <NUM>.

Document "<NPL>, discloses a proposal to consider the Access Type over which the SMS is deactivated. This document proposes the following changes. Consider the Access Type over which the SMS is deactivated. According to the clause <NUM>. <NUM> of 3GPP TS <NUM> V15. <NUM>, the SMS deactivation is triggered by Deregistration or Registration with UE's capability change for SMS over NAS. The general Registration or Deregistration is associated with Access Type (i.e., 3GPP Access or non-3GPP Access). But current SMS deactivation in clause <NUM>. <NUM> didn't differ different accesses. Hence once UE deregister from one access type, the SMS will be deactivated from all access types, which results in that the SMS is no longer allowed to be used by the UE via another available access type. Some editorial changes to correct the Nudr_DM_Unsubscribe service operation.

Document <CIT> (and its post-published patent family member <CIT>) discloses a short message service (SMS) ability updating method, device and apparatus. The method comprises: a mobility management function receives a triggering condition of an SMS function/a user data management function, and/or, the mobility management function determines that SMS over NAS ability update needs to be triggered; the mobility management function updates the SMS over NAS ability of a UE. By using the present application, when a mobility management function receives a triggering condition of an SMS function/a user data management function, and/or, the mobility management function determines that SMS over NAS ability update needs to be triggered, the mobility management function updates the SMS over NAS ability of the UE. The SMS over NAS ability update can be triggered by means of a network side, thereby preventing the UE from making an erroneous SMS transmission attempt.

Some embodiments advantageously provide methods and apparatuses for an update service operation for SMS service.

According to the present disclosure, there are provided methods, an AMF node, an SMSF node and computer-readable media according to the independent claims. Developments are set forth in the dependent claims.

According to a first aspect of the present disclosure, there is provided a method implemented in an access and mobility management, AMF, node. The method comprises performing an update service operation with a short message service function, SMSF, node to add a first user equipment, UE, context information associated to a first access type, the update service operation indicating to the SMSF node the first access type to add when the UE registers in the first access type, or delete the first user equipment, UE, context information associated to the first access type, the update service operation indicating to the SMSF node the first access type to remove when the UE deregisters from the first access type.

According to a second aspect of the present disclosure, there is provided a method implemented in a short message service function, SMSF, node. The method comprises performing a service operation with an access and mobility management, AMF, node to add or remove a first user equipment, UE, context information associated to a first access type, the service operation indicating to the SMSF node the first access type to add or remove; and add or delete the first user equipment, UE, context information associated to the first access type without deleting an existing second UE context information associated with a second access type.

According to a third aspect of the present disclosure, there is provided an access and mobility management, AMF, node comprising processing circuitry, the processing circuitry configured to cause the AMF node to perform any one or more of the methods of the first aspect.

According to a fourth aspect of the present disclosure, there is provided a short message service function, SMSF, node comprising processing circuitry, the processing circuitry configured to cause the SMSF node to perform any one or more of the methods of the second aspect.

According to a fifth aspect of the present disclosure, there is provided a computer-readable medium comprising computer instructions executable by a processor of an access and mobility management, AMF, node to perform any one or more of the methods of the first aspect.

According to a sixth aspect of the present disclosure, there is provided a computer-readable medium comprising computer instructions executable by a processor of a short message service function, SMSF, node to perform any one or more of the methods of the second aspect.

Hereinabove and in the following, "examples" pertain to principles underlying the claimed subject-matter and/or being useful for understanding the claimed subject-matter, while "embodiments" pertain to the claimed subject-matter within the claim scope.

Whenever an "embodiment" is made reference to in the present description, reference is to be made to the above-stated figure list to determine whether an "embodiment" or an "example" is meant.

As an initial matter, it is noted that references to 3GPP TS <NUM> and 3GPP TS <NUM> herein refer to version <NUM>. <NUM> of these TSs. The current context management for SMS service between the AMF <NUM> and the SMSF <NUM> is per UE level, while the context management for SMS service between SMSF <NUM> and UDM <NUM> is per UE per access type (3GPP access, non-3GPP access).

Thus, it may be useful for the AMF <NUM> to report the SMS over NAS capability over 3GPP access and non-3GPP access to the SMSF (e.g., the adding or removal of one access type). Otherwise, the SMSF <NUM> may not be able to perform proper per access type based registration towards the UDM <NUM>.

Some embodiments have considered to introduce the per access type based information reporting (removal or adding of the access type) from AMF <NUM> to SMSF <NUM>. It has been considered to use the current "Deactivate" service operation which is currently specified at the UE level context management (i.e., using the Deactivate service operation means that the UE is totally removed in the SMSF service for the entire UE).

As shown in the information below from 3GPP TS <NUM> and 3GPP TS <NUM> and <FIG>, the existing deactivate and activate service operations are performed at the UE level. Thus, currently, when the NF-service consumer (e.g., AMF <NUM>) sends a new Activate service operation, the previous UE context is overridden totally in the SMSF <NUM>. When the NF-service consumer (e.g., AMF <NUM>) sends a Deactivate service operation message, currently, the entire UE context is deleted.

The Activate service operation is to be used by the NF Service Consumer (e.g. AMF) to activate SMS service for a given service user, which results in creating or updating an individual UE Context for SMS in the SMSF, in the following procedures:.

There is to be only one individual UE Context for SMS per service user. See for example, <FIG>.

The Deactivate service operation is to be used by the NF Service Consumer (e.g. AMF <NUM>) to deactivate SMS service for a given service user, which results in deleting an individual UE Context for SMS in the SMSF, in the following procedures:.

The NF Service Consumer (e.g. AMF <NUM>) is to deactivate SMS service for a given service user by using the HTTP DELETE method as shown in <FIG>.

Thus, currently, using the Deactivation service operation means the entire UE context is removed totally. Some embodiments consider changing the Activation/Deactivation service operation to per access type Activate/Deactivate between AMF/SMF. Although, it may have an impact for UE registration and create issues between 3GPP Release <NUM> (rel-<NUM>) and 3GPP Release <NUM> (rel-<NUM>), which is undesirable, it may still be useful.

Some embodiments of the present disclosure define a new service operation for SMS service. In some embodiments, such service operation may be used by the AMF <NUM> to send new UE related information to the SMSF <NUM> when the UE is already registered/activated in the SMSF <NUM>.

Some embodiments of the present disclosure propose a service operation that "updates" the existing UE context with access type information. Some embodiments propose to update the Deactivate/Activate service operation to be able to provide per access type updates (e.g., delete/add UE context for a specific access type, rather than all UE contexts). Some embodiments propose a separate service operation to update UE context per access type and that the Deactivate service operation is only to be used when the UE context needs to be removed totally (in other words, no SMS at all at both 3GPP and N3GPP).

Some embodiments of the present disclosure may advantageously provide a solution to update UE related information from the AMF to the SMSF.

Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to an update service operation for short message service (SMS) service. 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 base station or a core network node, such as a <NUM> and/or NR network node, an AMF node, a SMSF node, a UDM 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 more general term "access type" is used and may indicate a radio access technology (RAT) type. Thus, the terms "access type" and "RAT type" may be interchangeable in this disclosure. The RAT may be considered the underlying physical connection method for a radio based communication network. Although two different access types are discussed, 3GPP access type and N3GPP access type, the proposed service update operation may be used to add and/or remove yet other access types.

In some embodiments, the term "update/updating" is used and may include adding and/or removing the information indicated in the proposed update service operation, per UE and per access type and/or not merely per UE level.

In some embodiments, the phrase "for the first access type" is used and may mean for the first access type only, and not any other access type that is not indicated in the proposed update service operation.

It should be understood that the service operation discussed in the present disclosure may have any name and should not be limited to the specific names used herein, which are exemplary and/descriptive, such as, "update service operation", or existing service operations such as activate and deactivate, since services and/or messages may, for example, be given another name in a specification, even though the use/function is as disclosed in the present disclosure.

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 an AMF node <NUM> or an SMSF node <NUM> or any network node may be distributed over a plurality of AMF nodes <NUM> or a plurality of SMSF nodes <NUM> or a plurality of network nodes. In other words, it is contemplated that the functions of the UE <NUM>, AMF node <NUM>, SMSF node <NUM> 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 an example communication system <NUM> 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 UE <NUM>, in addition to various support elements for supporting short message service (SMS) delivery to the UE <NUM> such as a radio access network (RAN) <NUM> (e.g., 3GPP <NUM>th Generation (<NUM>) RAN also known as New Radio or NR RAN), which may provide radio access to the UE <NUM>. The system <NUM> includes an Access and Mobility Management Function (AMF) node <NUM>, which may provide a function for access and/or mobility management for the UE <NUM>. The system <NUM> includes the SMSF node <NUM>. In some embodiments, the SMSF node <NUM> may support the transfer of SMS to the UE <NUM> e.g., over non-Access stratum (NAS). In this capacity, the SMSF may conduct subscription checking and perform a relay function between the device and the SMSC (Short Message Service Centre), through interaction with the AMF node <NUM>. The system <NUM> includes a UDM node <NUM>, which stores and manages subscriber information. 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 RAN <NUM>, a single AMF node <NUM>, a single SMSF node <NUM>, a single UDM node <NUM>, etc.); however, 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 than those shown in <FIG>.

The AMF node <NUM> may include an update requester <NUM>, which may be configured to send an update service operation message to a short message service function (SMSF) node to update, for a first access type, user equipment (UE) context information for a short message service (SMS) service.

The SMSF node <NUM> may include an updater <NUM>, which may be configured to receive an update service operation message, the update service response message requesting to update, for a first access type, user equipment (UE) context information for a short message service (SMS) service and/or update (e.g., add/remove) UE context information per the access type indicated in the update service operation message.

Example implementations, in accordance with an embodiment, of the UE <NUM>, AMF node <NUM>, SMSF node <NUM> and a network node <NUM> (e.g., UDM node, RAN node, etc.) discussed in the preceding paragraphs will now be described with reference to <FIG>.

The UE <NUM> includes a communication interface <NUM>, processing circuitry <NUM>, and memory <NUM>. The communication interface <NUM> may be configured to communicate with the RAN <NUM> and/or AMF node <NUM> and/or other elements 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 also 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 AMF node <NUM> includes a communication interface <NUM>, processing circuitry <NUM>, and memory <NUM>. The communication interface <NUM> may be configured to communicate with the SMSF node <NUM> and/or other elements in the system <NUM> according to one or more of 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 also include a wired interface.

Thus, the AMF node <NUM> may further include software stored internally in, for example, memory <NUM>, or stored in external memory (e.g., database) accessible by the AMF 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 AMF 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 update requester <NUM>, causes the processing circuitry <NUM> and/or configures the AMF node <NUM> to perform the processes described herein with respect to the AMF node <NUM> (e.g., processes described with reference to <FIG> and/or any of the other flowcharts).

The SMSF node <NUM> includes a communication interface <NUM>, processing circuitry <NUM>, and memory <NUM>. The communication interface <NUM> may be configured to communicate with the AMF node <NUM> and/or the UDM node <NUM> and/or other elements in the system <NUM> according to one or more of 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 also include a wired interface.

Thus, the SMSF node <NUM> may further include software stored internally in, for example, memory <NUM>, or stored in external memory (e.g., database) accessible by the SMSF 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 SMSF 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 updater <NUM>, causes the processing circuitry <NUM> and/or configures the SMSF node <NUM> to perform the processes described herein with respect to the SMSF node <NUM> (e.g., processes described with reference to <FIG> and/or any of the other flowcharts).

The network node <NUM> (e.g., UDM node <NUM>, RAN node <NUM> etc.) includes a communication interface <NUM>, processing circuitry <NUM>, and memory <NUM>. The communication interface <NUM> may be configured to communicate the elements in the system <NUM> according to one or more of 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 also 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>, 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., UDM node <NUM>, RAN node <NUM>, etc.).

In <FIG>, the connection between the devices UE <NUM>, AMF node <NUM>, SMSF node <NUM> and network node <NUM> 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.

Although <FIG> shows update requester <NUM> and updater <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 AMF node <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 AMF node <NUM> may be performed by one or more elements of AMF node <NUM> such as by update requester <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 S100), such as via update requester <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, an update service operation message to a short message service function (SMSF) node to update, for a first access type, user equipment (UE) context information for a short message service (SMS) service.

In some embodiments, sending further comprises, while a user equipment (UE) is registered in the AMF node at the first access type and a second access type for a short message service (SMS) service, sending, such as via update requester <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, the update service operation message to the SMSF node to remove, for the first access type, the UE context information for the SMS service and/or while maintaining the UE context information for the second access type.

In some embodiments, sending the update service operation message to remove, for the first access type, the UE context information is responsive to at least one of: the UE indicating to the AMF node to discontinue use of the SMS service for the first access type; the UE being deregistered on the first access type; receiving a deregistration notification from a unified data management (UDM) node for the first access type. In some embodiments, sending further comprises, while a user equipment (UE) is registered in the AMF node at a second access type for a short message service (SMS) service, sending, such as via update requester <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, the update service operation message to the SMSF node to add, for the first access type, the UE context information for the SMS service and/or while maintaining the UE context information for the second access type.

In some embodiments, the update service operation message includes an indication of the first access type that is to be updated. In some embodiments, the update service operation message further includes at least one of a Time Zone for the UE, the UE's routing indicator and the unified data management (UDM) group identifier for the UE that is to be updated in the UE context information for the first access type.

<FIG> is a flowchart of an exemplary process in an SMSF node <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 SMSF node <NUM> may be performed by one or more elements of SMSF node <NUM> such as updater <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 S <NUM>), such as via updater <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, an update service operation message, the update service response message requesting to update, for a first access type, user equipment (UE) context information for a short message service (SMS) service.

In some embodiments, receiving further comprises receiving, such as via updater <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, an update service operation message, the update service operation message while a user equipment (UE) is registered in the AMF node at the first access type and a second access type for the short message service (SMS) service; and the update service operation message requesting to remove, for the first access type, the UE context information for the SMS service. In some embodiments, the method further comprises, responsive to the update service operation message request to remove, for the first access type, the UE context information for the SMS service, releasing, such as via updater <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, an update service operation message, the UE context for the SMS service for the first access type and/or while maintaining the UE context information for the second access type.

In some embodiments, receiving further comprises, while a user equipment (UE) is registered in the AMF node at a second access type for a short message service (SMS) service, receiving the update service operation message to the SMSF node to add, for the first access type, the UE context information for the SMS service; and responsive to the update service operation message request to add, for the first access type, the UE context information for the SMS service, adding, such as via updater <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, an update service operation message, the UE context information for the SMS service for the first access type and/or while maintaining the UE context information for the SMS service for the second access type.

In some embodiments, the update service operation message includes an indication of the first access type that is to be updated by the SMSF node <NUM>. In some embodiments, the update service operation message further includes at least one of a Time Zone for the UE, the UE's routing indicator and the unified data management (UDM) group identifier for the UE that is to be updated by the SMSF node <NUM> in the UE context information for the first access type.

In some embodiments, the method further includes responsive to the received update service operation message, one of adding and removing the UE context information for the indicated first access type according to UE information included in the message.

<FIG> is a flowchart of an exemplary process in a AMF node <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 AMF node <NUM> may be performed by one or more elements of AMF node <NUM> such as by update requester <NUM> in processing circuitry <NUM>, memory <NUM>, processor <NUM>, communication interface <NUM>, etc. according to the example process/method. The example process includes performing (Block S <NUM>), such as by update requester <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, an update service operation with a short message service function, SMSF, node to add or remove a first user equipment, UE, context information associated to a first access type, the update service operation indicating to the SMSF node the first access type to add or remove.

In some embodiments, the performing the update service operation comprises sending, such as by update requester <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, a short message service, SMS, service message to the SMSF node, the SMS service message comprising an indication of the first access type to add or remove. In some embodiments, sending the SMS service message comprises sending, such as by update requester <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, a short message service, SMS, service activate message to add the first UE context information associated to the first access type; sending, such as by update requester <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, a short message service, SMS, service de-activate message to remove first the UE context information associated to the first access type; and sending, such as by update requester <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, a short message service, SMS, service update message to add or remove first the UE context information associated to the first access type.

In some embodiments, performing the update service operation to remove the first UE context information associated to the first access type comprises: while a user equipment, UE, is registered at the AMF node for a short message service, SMS, service over the first access type and over a second access type, sending, such as by update requester <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, a SMS service message indicating the first access type to request the SMSF node to remove the first UE context information associated to the first access type and the UE, while maintaining at the SMSF node a second UE context information associated to the second access type and the UE. In some embodiments, performing the update service operation to remove, such as by update requester <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, the first UE context information associated to the first access type is as a result of at least one of: the UE indicating to the AMF node to discontinue use of the SMS service over the first access type; the UE being deregistered on the first access type; and receiving a deregistration notification associated with the UE from a unified data management, UDM, node for the first access type.

In some embodiments, performing the update service operation to add the first UE context information associated to the first access type comprises: while a user equipment, UE, is registered at the AMF node for a short message service, SMS, service over a second access type, sending, such as by update requester <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, a SMS service message indicating the first access type to request the SMSF node to add the first UE context information associated to the first access type and the UE, while maintaining at the SMSF node a second UE context information associated to the second access type and the UE.

In some embodiments, the update service operation indicates to the SMSF node further information to add or remove from the first UE context information associated to the first access type. In some embodiments, the further information comprises at least one of a Time Zone, a routing indicator and a unified data management, UDM, group identifier for the UE that is to be added or removed in the first UE context information associated to the first access type.

<FIG> is a flowchart of an exemplary process in an SMSF node <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 SMSF node <NUM> may be performed by one or more elements of SMSF node <NUM> such as updater <NUM> in processing circuitry <NUM>, memory <NUM>, processor <NUM>, communication interface <NUM>, etc. according to the example process/method. The example process includes performing (Block S <NUM>), such as by as updater <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, an update service operation with an access and mobility management, AMF, node to add or remove a first user equipment, UE, context information associated to a first access type, the update service operation indicating to the SMSF node the first access type to add or remove.

In some embodiments, the performing the update service operation comprises receiving, such as by as updater <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, a short message service, SMS, service message from the AMF node, the SMS service message comprising an indication of the first access type to add or remove. In some embodiments, receiving the SMS service message comprises receiving, such as by as updater <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, a short message service, SMS, service activate message requesting the SMFS node to add the first UE context information associated to the first access type; receiving, such as by as updater <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, a short message service, SMS, service de-activate message requesting the SMFS node to remove first the UE context information associated to the first access type; and receiving, such as by as updater <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, a short message service, SMS, service update message requesting the SMFS node to add or remove the first the UE context information associated to the first access type.

In some embodiments, performing the update service operation to remove the first UE context information associated to the first access type comprises: as a result of receipt of a short message service, SMS, service message indicating the first access type, releasing, such as by as updater <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, the first UE context information associated to the first access type and the UE, while maintaining, such as by as updater <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, at the SMSF node a second UE context information associated to the second access type and the UE.

In some embodiments, performing the update service operation to remove the first UE context information associated to the first access type is as a result of at least one of: the UE indicating to the AMF node to discontinue use of the SMS service over the first access type; the UE being deregistered on the first access type; and a deregistration notification associated with the UE from a unified data management, UDM, node for the first access type. In some embodiments, performing the update service operation to add the first UE context information associated to the first access type comprises: as a result of receipt of a short message service, SMS, service message indicating the first access type, adding, such as by as updater <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, the first UE context information associated to the first access type and the UE, while maintaining, such as by as updater <NUM>, processing circuitry <NUM>, memory <NUM>, processor <NUM> and/or communication interface <NUM>, at the SMSF node a second UE context information associated to the second access type and the UE.

In some embodiments, the update service operation requests the SMSF node to add or remove further information from the first UE context information associated to the first access type. In some embodiments, the further information comprises at least one of a Time Zone, a routing indicator and a unified data management, UDM, group identifier for the UE that is to be added or removed in the first UE context information associated to the first access type.

Having generally described arrangements for an update service operation for SMS service, 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>, AMF node <NUM>, SMSF node <NUM> and/or network node <NUM>.

Some embodiments provide arrangements that may be used in at least two main use cases that are specified herein in relation to the proposed embodiments of the present disclosure.

One embodiment of the present disclosure may provide arrangements for adding a new access type for the SMS service.

For example, the UE <NUM> may register (e.g., send a registration request to the AMF node <NUM> to register to the 5GS) in N3GPP access (non-3GPP access) and then the AMF node <NUM> registers the UE <NUM> in the SMSF node <NUM> based on, e.g., clause <NUM>. <NUM> in TS <NUM>. The UE <NUM> may register in N3GPP access via the same AMF node <NUM> (e.g., same AMF as the AMF that the UE used to registered via the 3GPP access). The AMF node <NUM> may then use an update service operation (e.g., existing activate/deactivate or separate service operation) to add the new access type, among other parameters.

Referring to the flow chart in <FIG>, example steps for adding a new access type for the SMS service may include one or more of the following (in some embodiments, it may be assumed that the UE <NUM> is already registered via 3GPP access as in TS <NUM> clause <NUM>. <NUM>):
Initially, in Step S108, the UE <NUM> is registered in the AMF node <NUM> via one access type (e.g., 3GPP access) and the SMS service is activated for the UE <NUM>.

UE <NUM> registers towards the same AMF node <NUM> via another access type (e.g., non-3GPP access). Note: this may mean that the UE <NUM> selected 3GPP and non-3GPP access in the same public land mobile network (PLMN).

Step S112 of <FIG> may be the same as steps <NUM>-<NUM> of figure <NUM>. <NUM> in TS <NUM>.

AMF node <NUM> selects the existing SMSF node <NUM> and informs the SMSF node <NUM> of the new access type (in some embodiments, along with other parameters), by invoking the Nsmf_SMService_Update/Activate service operation (e.g., sending a service update operation request message to the SMSF node <NUM> to update the indicated UE's <NUM> SMS service information including the access type).

Step S114 of <FIG> may be the same as steps <NUM>-<NUM> of figure <NUM>. <NUM> in TS <NUM>.

The SMSF node <NUM> responds back to the AMF node <NUM> with a Nsmsf_SMService_Update/Activate service operation response message.

The AMF node <NUM> includes the "SMS allowed" indication to the UE <NUM> in the Registration Accept message, as in step <NUM> of figure <NUM>. <NUM> in TS <NUM>.

One embodiment of the present disclosure may provide arrangements for removing a new access type for the SMS service, e.g., in particular the removing of one access type for a UE <NUM> that has SMS service for <NUM> access types.

For example, the AMF node <NUM> may also use an update service operation to remove one access type, such as e.g., a separate update service operation or existing activate/deactivate service operation that has been changed to allow per access type updates. In some embodiments, the AMF node <NUM> requests from the SMSF node <NUM> removal of one access type (out of two more access types) for the indicated UE <NUM> by invoking e.g., the Nsmf_SMService_Update/Deactivate service operation (e.g., sending a service operation request message to the SMSF node <NUM> to update by removing the indicated accept type (e.g., 3GPP access type or N3GPP access type) from the UE's <NUM> SMS service information).

One example definition for the service update service operation is shown below:.

In one example, Section <NUM>. <NUM> (SMSF Services) of 3GPP TS <NUM> may be changed to the following:.

The following table illustrates the SMSF Services.

Similarly, 3GPP TS <NUM> may be updated to add Section <NUM>. x to reflect the example update service operation provided above.

In addition to the access type input parameter, Time Zone, UE's routing indicator, or UDM group identifier is shown and may be included as part of the update operation. For example, by defining a Time Zone input parameter to the proposed update service operation, the Time Zone in the UE's <NUM> SMS context may be updated accordingly for the UE <NUM>. These parameters may be used by the network, e.g., by the AMF node <NUM> and SMSF node <NUM> to create a UE context per access type for the UE <NUM>. In other embodiments, the service operation e.g., "Nsmsf_SMSService_Update/Deactivate" may be defined in other ways and/or may include more or less than the parameters shown in the example definition above.

There is no way in the current 3GPP specifications to update the UE context from the AMF to the SMSF e.g., per access type in a currently defined service operation. Some embodiments of the present disclosure propose a service operation to update UE related information from AMF to SMSF (e.g., without the previous UE context being overridden totally in the SMSF, such as may occur using an activate service operation and/or without the entire UE context being deleted, as may occur using a deactivate service operation), such as a new separate update service operation or a modification to existing activate/deactivate service operations according to the techniques described herein.

Claim 1:
A method implemented in an access and mobility management, AMF, node (<NUM>), the method comprising:
performing (S104) an update service operation with a short message service function, SMSF, node (<NUM>) to:
- add a first user equipment, UE, context information associated to a first access type, the update service operation indicating to the SMSF node (<NUM>) the first access type to add when the UE registers in the first access type, or
- delete the first user equipment, UE, context information associated to the first access type, the update service operation indicating to the SMSF node (<NUM>) the first access type to remove when the UE deregisters from the first access type.