WO2025209843A1

WO2025209843A1 - Indication of pending mobile terminating services

Info

Publication number: WO2025209843A1
Application number: PCT/EP2025/057629
Authority: WO
Inventors: Srinivas GARIKIPATI; Saurabh Khare; Bighnaraj PANIGRAHI
Original assignee: Nokia Technologies Oy
Current assignee: Nokia Technologies Oy
Priority date: 2024-04-05
Filing date: 2025-03-20
Publication date: 2025-10-09
Anticipated expiration: 2026-10-05

Abstract

Embodiments of the present disclosure relate to an indication of a pending mobile terminating service. In an aspect, a terminal device receives an indication from a first network node that a pending mobile terminating service is initiated for a user subscription of the terminal device. A user identity associated with the user subscription is registered via the terminal device and the user subscription is de-registered via the terminal device. The terminal device further provides the indication to an application layer of the terminal device based on the pending mobile terminating service. By implementing the embodiments of the present disclosure, the user subscription which is de-registered can be notified when there is a mobile terminating service that is being attempted by the network when the user identity is registered.

Description

INDICATION OF PENDING MOBILE TERMINATING SERVICES

FIELD

[0001] Various example embodiments generally relate to the field of communication, and in particular, to a terminal device, network nodes, methods, apparatuses and a computer readable storage medium for providing an indication of a pending mobile terminating service.

BACKGROUND

[0002] A communication network can be seen as a facility that enables communications between two or more communication devices, or provides communication devices access to a data network. A mobile or wireless communication network is one example of a communication network.

[0003] Such communication networks operate in accordance with standards, such as those promulgated by the third generation partnership project (3 GPP) or European telecommunications standards institute (ETSI). Examples of such standards include the so- called 5th generation (5G) standard or other standards promulgated by 3GPP.

SUMMARY

[0004] In general, example embodiments of the present disclosure provide a solution related to an indication of a pending mobile terminating service. For example, the solution can notify the user subscription which is de-registered when there is a mobile terminating service that is being attempted by the network when the user identity is registered.

[0005] In a first aspect, there is provided a terminal device. The terminal device comprises at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device at least to: receive, from a first network node, an indication that a pending mobile terminating service is initiated for a user subscription of the terminal device, wherein a user identity associated with the user subscription is registered via the terminal device; and provide the indication to an application layer of the terminal device based on the pending mobile terminating service.

[0006] In a second aspect, there is provided a first network node. The first network node may comprise at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the first network node at least to: receive, from a second network node, an indication that a pending mobile terminating service is initiated for a user subscription of a terminal device, wherein a user identity associated with the user subscription is registered via the terminal device and the user subscription is de-registered; and transmit, to the terminal device, the indication that the pending mobile terminating service is initiated for the user subscription of the terminal device.

[0007] In a third aspect, there is provided a second network node. The second network node may comprise at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the second network node at least to: receive a message of a pending mobile terminating service terminating for a user subscription of a terminal device, wherein a user identity associated with the user subscription of the terminal device is registered via the terminal device and the user subscription is de-registered; and in response to the message, transmit, to the terminal device via a first network node, an indication that the pending mobile terminating service is initiated for the user subscription of the terminal device.

[0008] In a fourth aspect, there is provided a method. The method comprises: receiving, at a terminal device from a first network node, an indication that a pending mobile terminating service is initiated for a user subscription of the terminal device, wherein a user identity associated with the user subscription is registered via the terminal device; and providing the indication to an application layer of the terminal device based on the pending mobile terminating service.

[0009] In a fifth aspect, there is provided a method. The method comprises: receiving, at a first network node from a second network node, an indication that a pending mobile terminating service is initiated for a user subscription of a terminal device, wherein a user identity associated with the user subscription is registered via the terminal device and the user subscription is de-registered; and transmitting, to the terminal device, the indication that the pending mobile terminating service is initiated for the user subscription of the terminal device.

[0010] In a sixth aspect, there is provided a method. The method comprises: receiving, at a second network node, a message of a pending mobile terminating service terminating for a user subscription of a terminal device, wherein a user identity associated with the user subscription of the terminal device is registered via the terminal device and the user subscription is de-registered; and in response to the message, transmitting, to the terminal device via a first network node, an indication that the pending mobile terminating service is initiated for the user subscription of the terminal device.

[0011] In a seventh aspect, there is provided an apparatus. The apparatus comprises: means for receiving, at a terminal device from a first network node, an indication that a pending mobile terminating service is initiated for a user subscription of the terminal device, wherein a user identity associated with the user subscription is registered via the terminal device; and means for providing the indication to an application layer of the terminal device based on the pending mobile terminating service.

[0012] In an eighth aspect, there is provided an apparatus. The apparatus comprises: means for receiving, at a first network node from a second network node, an indication that a pending mobile terminating service is initiated for a user subscription of a terminal device, wherein a user identity associated with the user subscription is registered via the terminal device and the user subscription is de-registered; and means for transmitting, to the terminal device, the indication that the pending mobile terminating service is initiated for the user subscription of the terminal device.

[0013] In a ninth aspect, there is provided an apparatus. The apparatus comprises: means for receiving, at a second network node, a message of a pending mobile terminating service terminating for a user subscription of a terminal device, wherein a user identity associated with the user subscription of the terminal device is registered via the terminal device and the user subscription is de-registered; and means for in response to the message, transmitting, to the terminal device via a first network node, an indication that the pending mobile terminating service is initiated for the user subscription of the terminal device.

[0014] In a tenth aspect, there is provided a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method according to any of the fourth to the sixth aspect.

[0015] In an eleventh aspect, there is provided a computer program comprising instructions, which, when executed by an apparatus, cause the apparatus at least to: receive, from a first network node, an indication that a pending mobile terminating service is initiated for a user subscription of the terminal device, wherein a user identity associated with the user subscription is registered via the terminal device; and provide the indication to an application layer of the terminal device based on the pending mobile terminating service. [0016] In a twelfth aspect, there is provided a computer program comprising instructions, which, when executed by an apparatus, cause the apparatus at least to: receive, from a second network node, an indication that a pending mobile terminating service is initiated for a user subscription of a terminal device, wherein a user identity associated with the user subscription is registered via the terminal device and the user subscription is de-registered; and transmit, to the terminal device, the indication that the pending mobile terminating service is initiated for the user subscription of the terminal device.

[0017] In a thirteenth aspect, there is provided a computer program comprising instructions, which, when executed by an apparatus, cause the apparatus at least to: receive a message of a pending mobile terminating service terminating for a user subscription of a terminal device, wherein a user identity associated with the user subscription of the terminal device is registered via the terminal device and the user subscription is de-registered; and in response to the message, transmit, to the terminal device via a first network node, an indication that the pending mobile terminating service is initiated for the user subscription of the terminal device.

[0018] In a fourteenth aspect, there is provided a terminal device. The terminal device comprises receiving circuitry configured to receive, from a first network node, an indication that a pending mobile terminating service is initiated for a user subscription of the terminal device, wherein a user identity associated with the user subscription is registered via the terminal device; and providing circuitry configured to provide the indication to an application layer of the terminal device based on the pending mobile terminating service.

[0019] In a fifteenth aspect, there is provided a first network node. The first network node comprises receiving circuitry configured to receive, from a second network node, an indication that a pending mobile terminating service is initiated for a user subscription of a terminal device, wherein a user identity associated with the user subscription is registered via the terminal device and the user subscription is de-registered; and transmitting circuitry configured to transmit, to the terminal device, the indication that the pending mobile terminating service is initiated for the user subscription of the terminal device.

[0020] In a sixteenth aspect, there is provided a second network node. The second network node comprises receiving circuitry configured to receive a message of a pending mobile terminating service terminating for a user subscription of a terminal device, wherein a user identity associated with the user subscription of the terminal device is registered via the terminal device and the user subscription is de-registered; and transmitting circuitry configured to in response to the message, transmit, to the terminal device via a first network node, an indication that the pending mobile terminating service is initiated for the user subscription of the terminal device.

[0021] It is to be understood that the summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.

BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Some example embodiments will now be described with reference to the accompanying drawings, in which:

[0023] FIG. 1 illustrates an example network environment in which example embodiments of the present disclosure may be implemented;

[0024] FIG. 2 illustrates an example signaling process of an indication of a pending mobile terminating service in accordance with some example embodiments of the present disclosure;

[0025] FIG. 3 illustrates an example signaling process of an indication of a pending internet protocol (IP) multimedia subsystem (IMS) service in accordance with some example embodiments of the present disclosure;

[0026] FIG. 4 illustrates an example signaling process of an indication of a pending short message service (SMS) in accordance with some example embodiments of the present disclosure;

[0027] FIG. 5 illustrates an example signaling process of an indication of a pending nonIP data delivery (NIDD) service in accordance with some example embodiments of the present disclosure;

[0028] FIG. 6 illustrates an example flowchart of a process of an indication of a pending mobile terminating service implemented at a terminal device in accordance with some example embodiments of the present disclosure;

[0029] FIG. 7 illustrates an example flowchart of a process of an indication of a pending mobile terminating service implemented at a first network node in accordance with some example embodiments of the present disclosure; [0030] FIG. 8 illustrates an example flowchart of a process of an indication of a pending mobile terminating service implemented at a second network node in accordance with some example embodiments of the present disclosure;

[0031] FIG. 9 illustrates an example simplified block diagram of a device that is suitable for implementing embodiments of the present disclosure; and

[0032] FIG. 10 illustrates an example block diagram of an example computer readable medium in accordance with some example embodiments of the present disclosure.

[0033] Throughout the drawings, the same or similar reference numerals represent the same or similar element.

DETAILED DESCRIPTION

[0034] Principles of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. The disclosure described herein may be implemented in various manners other than the ones described below.

[0035] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which the present disclosure belongs.

[0036] References in the present disclosure to “one embodiment,” “an embodiment,” “an example embodiment,” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0037] It may be understood that although the terms “first” and “second” etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the listed terms.

[0038] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. 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”, “has”, “having”, “includes” and/or “including”, when used herein, specify the presence of stated features, elements, and/or components etc., but do not preclude the presence or addition of one or more other features, elements, components and/ or combinations thereof. As used herein, “at least one of the following: <a list of two or more elements>” and “at least one of <a list of two or more elements>” and similar wording, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0039] As used in this application, the term “circuitry” may refer to one or more or all of the following:

(a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) and

(b) combinations of hardware circuits and software, such as (as applicable):

(i) a combination of analog and/or digital hardware circuit(s) with software/firmware and

(ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and

(c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor s) that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

[0040] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0041] As used herein, the term “communication network” refers to a network following any suitable communication standards, such as long term evolution (LTE), LTE-advanced (LTE-A), wideband code division multiple access (WCDMA), high-speed packet access (HSPA), narrow band Internet of things (NB-IoT) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the third generation (3G), the fourth generation (4G), 4.5G, the fifth generation (5G) communication protocols, and/or beyond. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.

[0042] As used herein, the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP), for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a NR NB (also referred to as a gNB), a remote radio unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, a low power node such as a femto, a pico, and so forth, depending on the applied terminology and technology.

[0043] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE), a subscriber station (SS), a portable subscriber station, a mobile station (MS), or an access terminal (AT). The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, wireless customer-premises equipment (CPE), an Internet of things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial, a relay node, an integrated access and backhaul (IAB) node, and/or industrial wireless networks, and the like. In the following description, the terms “terminal device”, “communication device”, “terminal”, “user equipment” and “UE” may be used interchangeably.

[0044] As used herein, the term “resource”, “transmission resource”, “resource block”, “physical resource block” (PRB), “uplink (UL) resource” or “downlink (DL) resource” may refer to any resource for performing a communication, for example, a communication between a terminal device and a network device, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, a resource in a combination of more than one domain or any other resource enabling a communication, and the like. In the following, a resource in time domain (such as, a subframe) will be used as an example of a transmission resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.

[0045] As discussed in the present disclosure, a user subscription may refer to an owner of a UE, and a user identity may be attached to the user subscription. Herein, a user identity is also called as a user profile. The phrases “user identity” and “user profile” may be used interchangeably throughout the description. As an example, it may be assumed that the user subscription may correspond to a farther who own the UE and the user identity may correspond to his daughter. In such case, for example, between time TO to T100, the UE of the father is used by his daughter, which means the unified data management function (UDM) has an indication the user identity of the daughter is active with the user Subscription of the father. Now at T20, if a bank service (or other priority service) sends an SMS to the father (not the daughter), the UDM may know the UE is used by the user identity of daughter with the user Subscription of the father. The mobile terminating service (such as the SMS from the bank) is rejected to the user Subscription of father as the user Subscription of the father might be in either of de-registered / de-activated state; based on the implementation, the operator may have de-registered state or de-activated (inactive) state In certain deployment operator would completely de-register the user Subsrciption of the father and in some cases change the status to de-activated by maintaining the context for easier management.

[0046] In an embodiment, the user subscription may refer to a user identity or a user profile. In this embodiment, the user identity (of/associated with the user subscription) of the UE may be de-registered/de-activated if/when/after another user identity registers via the UE.

[0047] As can be seen from above, there is a need to alert (maybe without exposing what it is about) the father that a mobile terminating service is attempted by the network (NW). One of the reasons may be that the prime person or the subscription owner is the father, who is entitled to know this when his daughter is using his UE.

[0048] In some embodiments, there may be a concept and need to differentiate whether the UE is used by the user subscription alone or being used by a user identity. If the user identity is using the UE, the mobile terminating services such as SMS, NIDD, IMS terminating call attempting to deliver a message to the UE will fail because UE is not available. However, UE is still used by other user identity. In the present disclosure, the following aspects may be considered: 1) the terminating service as in above should not be delivered to the UE, as the UE is being used by the user identity (For example, a daughter (user identity) is using the UE (of the father)); and 2) it is also required to indicate to the user subscription (of the father as in the above example) in a personalized customized message or indication that one or more important services (such as the IMS terminating call, SMS, NIDD, etc.) are on the way to be delivered.

[0049] Example embodiments of the present disclosure provide methods and apparatuses related to pending mobile terminating services, for example, for handling and notifying for mobile terminating services of a UE when/if/after the UE is being used by a user identity (rather than a user subscription of the UE or a user identity of the user subscription of the UE). According to embodiments of the present disclosure, a terminal device receives an indication from a first network node that a pending mobile terminating service is initiated for a user subscription of the terminal device. A user identity associated with the user subscription is registered via the terminal device. In response to the indication, the terminal device may further provide the indication to an application layer of the terminal device (based on the pending mobile terminating service).

[0050] It is understood that the above procedure steps may work together, in a flow of operations as described in the next section, partly together or independently of each other. By implementing the embodiments of the present disclosure, the user subscription which is de-registered can be notified when there is a mobile terminating service that is being attempted by the network when the user identity is registered.

[0051] For illustrative purposes, principles and example embodiments of the present disclosure of an indication of a pending mobile terminating service will be described below with reference to FIG. 1- FIG. 10. However, it is to be noted that these embodiments are given to enable the skilled in the art to understand inventive concepts of the present disclosure and implement the solution as proposed herein, and not intended to limit scope of the present application in any way.

[0052] Reference is made to FIG. 1, which illustrates an example network environment 100 in which example embodiments of the present disclosure may be implemented. The network environment 100, which may be a part of a communication network, includes a terminal device 102, a first network node 104, and a second network node 106 and an access network device 108.

[0053] As illustrated in FIG. 1, the terminal device 102 may also be referred as a user equipment 102 or a UE 102. The access network device 108 may also be referred as a gNB 108. The terminal device 102 and the access network device 108 can communicate with each other. The first network node 104 and the second network node 106 can communicate with each other. The first network node 104 can communicate with the terminal device 102 via the access network device 108.

[0054] The first network node 104 and the second network node 106 may be core network devices or functions. For example, the first network node 104 may be an access and mobility management function (AMF) 104, and the second network node 106 may be a unified data management function (UDM) 106 or a home subscriber server (HSS) 106.

[0055] In the present disclosure, a network node being/comprising a network function refers to a network device/node performing at least part of functionalities of the network function.

[0056] Some use cases may happen in the example network environment 100. For example, in an SMS use case, the SMS server (SMSC) may ask the UDM/HSS 106 to provide the address of the SMS function (SMSF) currently serving the UE 102 to deliver the mobile terminating SMS. The UDM/HSS 106 may provide the address of the SMSF currently serving the UE 102, or the addresses of two SMSFs serving the UE 102 if the UE 102 is registered for 3GPP access and non 3GPP access and the SMS is enabled via any of these accesses to the SMSC. The SMSC may firstly try to deliver the SMS trying one SMSF, and then the second SMSF, if necessary, based on the priority configured in the SMSC.

[0057] For another example, in an IMS terminating access domain selection (TADS) use case, during an IMS terminating call, the IMS server (service centralization and continuity application, SCC AS) may ask for TADS information from the UDM/HSS 106. The UDM/HSS 106 may provide the TADS information to the IMS so that call can be terminated in the registered domain.

[0058] As a further example, in a location services (LCS) use case, the network exposure function (NEF) may ask the UDM/HSS 106 and the UDM/HSS 106 may get the location of the UE 102 (at best at cell level) via the AMF’s location application programming interface (API). Alternatively, the NEF may also ask the user location from the gateway mobile location center (GMLC). Then GMLC may contact the UDM/HSS 106 to determine the AMF 104 currently serving the UE 102 and ask location (i.e., at a granularity smaller than cell level) from the location management function (LMF) via the AMF 104.

[0059] Reference is made to FIG. 2, which illustrates an example signaling process 200 of an indication of a pending mobile terminating service in accordance with some example embodiments of the present disclosure. FIG. 2 will be described with reference to FIG. 1.

[0060] As shown in FIG. 2, the second network node 106 receives (202) a message of a pending mobile terminating service terminating for a user subscription of the terminal device 102. A user identity associated with a user subscription of the terminal device 102 is registered via the terminal device 102 and the user subscription is de-registered.

[0061] In some example embodiments, as part of the registration process, the UE 102 may indicate that it supports receiving of the indication of alerting the UE 102. This indication may be stored in the UE context and this indication may be referred if to or if not to initiate the indication to the UE 102. For example, the terminal device 102 may transmit an indication that the terminal device 102 supports receiving the notification of the pending mobile terminating service. For an another example, the second network node 106 may take a decision if to or if not to initiate the notification on its own based on the indication.

[0062] Then, the second network node 106, in response to the message, transmits (204) an indication 208 of the pending mobile terminating service to the first network node 104. The first network node 104 receives (206) the indication 208 of the pending mobile terminating service from the second network node 106. The first network node 104 transmits (210) the indication 208 of the pending mobile terminating service to the terminal device 102. Thus, it can be seen that the second network node 106 transmits the indication 208 to the terminal device 102 via the first network node 104.

[0063] The terminal device 102 receives (212) the indication 208 of the pending mobile terminating service from first network node 104. The terminal device 102 provides (214) the indication 208 to an application layer of the terminal device 102 based on the pending mobile terminating service.

[0064] In some example embodiments, the pending mobile terminating service may be indicated by a non-access stratum (NAS) based indication with a flag, and the flag may indicate a mobile terminating service. For example, an NAS-based indication to UE 102 which may be delivered from the AMF 104 to the UE 102. This NAS-based indication may be added in the existing NAS message (configuration update procedure) or a new NAS message. For example, a new short message (SM) information element (IE). It can simply be a flag.

[0065] In some example embodiments, the terminal device 102 may transmit the indication 208 from a layer which receives the indication to the application layer, and generate a notification associated with the pending mobile terminating service based on the flag. For example, the NAS-based indication may be delivered to the UE 102 over NAS layer. NASbased indication values (flags) may indicate the mobile terminating service. For example, NASTerminationIndication= value 1 is used for SMS, value 2 is used for IMS terminating service. Similarly, any other existing/future mobile terminating services can also be indicated.

[0066] When the UE 102 of the user subscription receives this NAS-based indication, based on the value, it delivers the indication to the right application layer (such as SMS application or call application). Application layer may display an indication to user or add blink on the screen that a mobile terminating service is pending. The user identity may take some action (e.g., initiate log out so that the UE 102 can get logged in again to receive the message).

[0067] In some example embodiments, a service priority of a plurality of mobile terminating services may be configured in the second network node. Only a mobile terminating service marked in the service priority may be notified to the terminal device 102. The second network node 106 may determine whether the pending mobile terminating service is marked in the service priority, and transmit the indication 208 of the pending mobile terminating service based on determining that the pending mobile terminating service is being initiated for the user subscription.

[0068] In some example embodiments, the terminal device 102 may know that the user subscription has something to be checked out or looked at. The terminal device 102 may create a blink alert, for example, colored 3 to 5 blinks. The user subscription may want to take up the control of the terminal device 102. The user identity may be asked to wait because the priority is for the user subscription.

[0069] In some example embodiments, the terminal device 102 may pop up as an action if it wants to continue as the user identity or may want the user subscription to start registration. If user action is made (e.g., clicking on the pop up button), the user identity is de-registered and the user subscription is registered back.

[0070] By implementing the embodiments of FIG. 2, a solution for alerting the UE of a user subscription that there is a pending mobile terminating service which is being attempted by the network is proposed. The user subscription either through operations, administration, and maintenance (0AM) or application function (AF) provisioning, may configure or select the priority service (such as an SMS or IMS call) that it may want to receive when a mobile terminating service is attempted. That is, a service priority is configured in the UDM per subscriber. Hence, the user subscription which is de-registered can be notified when there is a mobile terminating service that is being attempted by the network when the user identity is registered.

[0071] Reference is made to FIG. 3, which illustrates an example signaling process 300 of an indication of a pending IMS service in accordance with some example embodiments of the present disclosure. FIG. 3 shows the scenario with the example of IMS TADS.

[0072] As shown in FIG. 3, in general, when an Sh-UDR TADS query message comes to the UDM/HSS 306 for terminating IMS call for the UE 302, and UE 302 is in de-activated / deregistered state, the UDM/HSS 306 may return a message of error to the IMS AS 308. However, UDM/HSS 306 may check if the IMS terminating service is marked as a priority service for the user. If yes, the UDM/HSS 306 may send a notification to the AMF 304 indicating that NASTerminationIndication= value 2 (which means the mobile terminating service is IMS in this example) to be deliver to it. The AMF 304 may deliver the NASTerminationIndication= value 2 to the UE 302 over the NAS. [0073] At 312, the UE 302 may register some priority services on the UDM/HSS 306. For example, the IMS service is one of the priority services. At 316, the user profile- 1 (310) may be registered in via the UE 302. At 314, an IMS terminating call invitation may be received. At 318, when user profile-1 registers, the UE 302 will be de-registered. The UDM 306 knows this switch and will hence mark it.

[0074] In some embodiments, the user subscription is de-registred if/when the user identity (e.g., the user identity different from the user subscription or from the user identity of the user subscription) is registered via the terminal device. The deregistation process of the user subscription may be triggered by terminal device or network. That is, in some embodiments, the UE may perform certain actions of/for deregistering the user subscription if the user identity is registered via the terminal device. In some embodiments, if the the user identity is registered via the terminal device, the UE does not need to act for deregistering the user subscription and the network (e.g., base station and/or core network function(s)) acknowledges/determines that the the user subscription is deregistered.

[0075] In some example embodiments, the de-regi strati on may be initiated by the UE and/ or network. User Identities may be considered to use the UE (of UE Subscription), and it may be considered that only amongst UE Subscription or User Profile could use actively. When/If/ After a User Identity A is registered via the UE in the network and then a User Identity B (Same is the handling when the UE Subscription is currently registered and a User Identity is getting registered) may be registered via the UE into the network. Under such conditions, the User Identity A is de-registered.

[0076] In an embodiment, the user identity/user subcription/UE is de-registered may refer to that the user identity/user subcription of the UE or previously registered via the UE is de- regi stered/de-activated or in a de-regi stered/de-activated state.

[0077] In some example embodiments, as part of the de-regi strati on of the current registration, the following procedures may happen: changing the status of the User Identity A to INACTIVE (run a timer for maintaining the context), and/or either Suspending or Releasing the corresponding PDU Sessions that were earlier established. AMF, PCF, SMF, UPF, UDM may be involved in the process of de-regi stering the User Identity A.

[0078] At 320, the sh-UDR TADS query message is transmitted from the IMS AS 308 to the UDM/HSS 306. This means that an SRI SM message comes to the UDM/HSS 306 for terminating SMSF address determination for the UE 302. Because at this time, the user profile-1 is registered in via the UE 302, and the user subscription is de-registered, at 322, the UDM/HSS 306 may return a message indicating an error to the IMS AS 308.

[0079] At 324, the UDM/HSS 306 may understand/determine/acknowledge that there is a mobile terminating service initiated for the UE 302. Because the UDM/HSS 306 knows that the UE 302 is de-registered now and User Profile 1 is registered/logged in, the UDM/HSS 306 may send an indication towards the UE 302 via the AMF 304.

[0080] At 326, the UDM/HSS 306 may send a notification (Term_indication=2) to the AMF 304. At 328, the AMF 304 may send a NAS message (Term_indication=2) to the UE 302. At 330, the UE 302 may display the notification. For example, the application layer of the UE 302 may display/generate an indication to user or add blink on the screen that the IMS terminating call is pending.

[0081] Reference is made to FIG. 4, which illustrates an example signaling process 400 of an indication of a pending SMS in accordance with some example embodiments of the present disclosure. FIG. 4 shows the scenario with the example of SMS.

[0082] As shown in FIG. 4, in general, when a MAP send routing information for short (SRI SM) message or similar diameter message comes to UDM/HSS 406 for terminating SMSF address determination for the UE 402, and UE 402 is in deactivated state, the UDM/HSS 406 returns a message of error to the SMS-GMSC 408. However, UDM/HSS 406 may check if SMS service is marked as priority service for the user. If yes, the UDM/HSS 406 may send the notification to AMF 404 indicating that NASTerminationIndication= value 1 (which means the mobile terminating service is SMS in this example) is to be delivered to it. The AMF 404 may deliver the NASTerminationIndication= value 1 to the UE 402 over the NAS.

[0083] At 412, the UE 402 may register some priority services on the UDM/HSS 406. For example, the SMS is one of the priority services. At 416, the user profile- 1 (410) may be registered in via the UE 402. At 414, an SMS message is transferred from the service center (SC) 409 to the SMS-GMSC 408. At 418, when user profile-1 registers, the UE 402 will be de-registered. The UDM 406 knows this switch and will hence mark it.

[0084] At 420, an Nudm UECM SendRountinglnfoForSM message is transmitted from the SMS-GMSC 408 to the UDM/HSS 406. This means that a SRI SM message or similar diameter message comes to UDM/HSS 406 for terminating SMSF address determination for the UE 402. Because at this time, the user profile-1 is registered in via the UE 402, and the user subscription is de-registered, at 422, thus the UDM/HSS 406 may return a message indicating an error to the SMS-GMSC 408.

[0085] At 424, the UDM/HSS 406 may understand that there is an SMS initiated for the UE 402. Because the UDM/HSS 406 knows that the UE 402 is de-registered/de-activated now and user profile 1 is registered/logged in, the UDM/HSS 406 may send an indication towards the UE 402 via the AMF 404.

[0086] At 426, the UDM/HSS 406 may send a notification (Term_indication=l) to the AMF 404. At 428, the AMF 404 may send a NAS message (Term_indication=l) to the UE 402. At 430, the UE 402 may display the notification.

[0087] Reference is made to FIG. 5, which illustrates an example signaling process 500 of an indication of a pending NIDD service in accordance with some example embodiments of the present disclosure. FIG. 5 shows the scenario with the example of NIDD.

[0088] As shown in FIG. 5, in general, a configuration create request may be sent by an AF to the NEF 508. The NEF 508 may send the authorization request and receive an error response for the UE 502’s generic public subscription identifier (GPSI) and the UE 502 may be used by the user. The UDM/HSS 506 may check if the NIDD terminating service is marked as a priority service for the user. If yes, the UDM/HSS 506 may send a notification to the AMF 504 indicating that NASTerminationIndication= value 3 (which means the mobile terminating service is NIDD in this example) is to be delivered to the AMF 504. The AMF 504 may deliver the NASTerminationIndication= value 3 to the UE 502 over the NAS.

[0089] At 512, the UE 502 may register some priority services on the UDM/HSS 506. For example, the NIDD service is one of the priority services. At 516, the user profile-1 (510) may be registered in via the UE 502. At 514, the configuration create request may be sent by to the NEF 508. When user profile-1 registers, the UE 502 will be de-registered. The UDM 506 knows this switch and will hence mark it.

[0090] At 520, an Nudm_NIDD_Authorization_Get_Request message is transmitted from the NEF 508 to the UDM/HSS 506. Because at this time, the user profile- 1 is registered in via the UE 502, and the user subscription is de-registered, at 522, thus the UDM/HSS 506 may return a Nudm NIDD Authorization Error message to the NEF 508.

[0091] At 524, the UDM/HSS 506 may understand that there is a mobile terminating service initiated for the UE 502. Because the UDM/HSS 506 knows that the UE 502 is de- registered/de-activated now and user profile 1 is registered/logged in, the UDM/HSS 506 may send an indication towards the UE 502 via the AMF 504.

[0092] At 526, the UDM/HSS 506 may send a notification (Term_indication=3) to the AMF 504. At 528, the AMF 504 may send a NAS message (Term_indication=3) to the UE 502. At 530, the UE 502 may display the notification.

[0093] Reference is made to FIG. 6, which illustrates an example flowchart of a process 600 of an indication of a pending mobile terminating service implemented at a terminal device in accordance with some example embodiments of the present disclosure. FIG.6 will be described with reference to FIG. 1.

[0094] At 602, the terminal device 102 receives an indication that a pending mobile terminating service is initiated for a user subscription of the terminal device 102 from the first network node 104. A user identity associated with the user subscription is registered via the terminal device 102.

[0095] At 604, the terminal device 102 may provide the indication to an application layer of the terminal device 102 (based on the pending mobile terminating service).

[0096] In some embodiments, the user subscription is de-registered (via the terminal device 102.

[0097] In some example embodiments, the pending mobile terminating service may be indicated by a NAS based indication with a flag, and the flag may indicate a mobile terminating service. That is, the indication may be a NAS based indication.

[0098] In some example embodiments, the pending mobile terminating service may comprise one or more of an SMS, a location-based service, a location service, an IMS service, and/or an NIDD service.

[0099] In some example embodiments, subscribing to the indication of the pending mobile terminating service may be initiated for the user subscription of the terminal device 102 for at least one prioritized mobile terminating service.

[00100] In some example embodiments, the terminal device may subsribe to the indication of the pending mobile terminating service for one or more terminating services (e.g., SMS).

[00101] In some example embodiments, the user identity may be registered to the second network node 106. [00102] In some example embodiments, the terminal device 102 may transmit the indication from a layer which receives the indication to the application layer and generate a notification associated with the pending mobile terminating service.

[00103] In some example embodiments, the terminal device 102 may transmit an indication that the terminal device 102 supports receiving the notification of the pending mobile terminating service. The indication may be transmitted to the first network node and/or the second network node.

[00104] In some example embodiments, the first network node 104 may comprise an AMF, and the second network node 106 may comprise a UDM or an HSS.

[00105] Reference is made to FIG. 7, which illustrates an example flowchart of a process 700 of an indication of a pending mobile terminating service implemented at a first network node in accordance with some example embodiments of the present disclosure. FIG.7 will be described with reference to FIG. 1.

[00106] At 702, the first network node 104 receives, from the second network node 106, an indication that a pending mobile terminating service is initiated for a user subscription of a terminal device 102. A user identity associated with the user subscription is registered via the terminal device 102 and the user subscription is de-registered.

[00107] At 704, the first network node 104 transmits the indication that the pending mobile terminating service is initiated for the user subscription of the terminal device 102.

[00108] For example, the first network node 104 transmits the indication that the pending mobile terminating service is initiated for the user subscription of the terminal device 102 if/when a user identity associated with the user subscription is registered via the terminal device 102 and the user subscription is de-registered.

[00109] In some example embodiments, the pending mobile terminating service may be indicated by an NAS based indication with a flag, and the flag may indicate a mobile terminating service.

[00110] In some example embodiments, the pending mobile terminating service may comprise one or more of an SMS, a location-based service, a location service, an IMS service, and/or an NIDD service.

[00111] In some example embodiments, the first network node 104 may comprise an AMF, and the second network node 106 may comprise a UDM or an HSS. [00112] Reference is made to FIG. 8, which illustrates an example flowchart of a process 800 of an indication of a pending mobile terminating service implemented at a second network node in accordance with some example embodiments of the present disclosure. FIG. 8 will be described with reference to FIG. 1.

[00113] At 802, the second network node 106 receive a message of a pending mobile terminating service terminating for a user subscription of the terminal device 102. A user identity associated with the user subscription of the terminal device 102 is registered via the terminal device 102 and the user subscription is de-registered.

[00114] At 804, in response to/based on the message, the second network node 106 transmits, to the terminal device 102 via a first network node 104, an indication that the pending mobile terminating service is initiated for the user subscription of the terminal device 102.

[00115] In some embodiment, based on/in response to the message, the second network node 106 transmits, to the terminal device 102 via a first network node 104, the indication that the pending mobile terminating service is initiated for the user subscription of the terminal device 102 if/when the user identity associated with the user subscription of the terminal device 102 is registered via the terminal device 102 and the user subscription is deregistered.

[00116] In some example embodiments, the pending mobile terminating service may be indicated by an NAS based indication with a flag, and the flag may indicate a mobile terminating service.

[00117] In some example embodiments, the pending mobile terminating service may comprise one or more of an SMS, a location-based service, a location service, an IMS service, and/or an NIDD service.

[00118] In some example embodiments, a service priority of a plurality of mobile terminating services may be configured in the second network node 106, and a mobile terminating service marked in the service priority may be to be notified to the terminal device 102.

[00119] In some example embodiments, the second network node 106 may determine whether the pending mobile terminating service is marked in the service priority, and may transmit, to the first network node 104, the indication of the pending mobile terminating service based on determining that the pending mobile terminating service is marked in the service priority.

[00120] In some example embodiments, the second network node 106 may receive an indication that the terminal device 102 supports receiving the notification of the pending mobile terminating service.

[00121] In some example embodiments, the first network node 104 may comprise an AMF, and the second network node 106 may comprise a UDM or an HSS.

[00122] By implementing the embodiments of the processes 600 to 800, the user subscription which is de-registered/de-activated can be notified when there is a mobile terminating service that is being attempted by the network when the user identity is registered.

[00123] In some example embodiments, an apparatus capable of performing the method 600 (for example, the terminal device 102) may comprise means for performing the respective steps of the method 600. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

[00124] In some example embodiments, the apparatus may comprise means for receiving, at a terminal device from a first network node, an indication that a pending mobile terminating service is initiated for a user subscription of the terminal device, wherein a user identity associated with the user subscription is registered via the terminal device; and means for providing the indication to an application layer of the terminal device based on the pending mobile terminating service.

[00125] In some example embodiments, the apparatus may comprise means for transmitting the indication from a layer which receives the indication to the application layer; and means for generating a notification associated with the pending mobile terminating service based on the flag.

[00126] In some example embodiments, the apparatus may further comprise means for transmit an indication that the terminal device supports receiving the notification of the pending mobile terminating service.

[00127] In some example embodiments, the apparatus may further comprise means for performing other steps in some example embodiments of the method 600. In some example embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.

[00128] In some example embodiments, an apparatus capable of performing the method 700 (for example, the first network node 104) may comprise means for performing the respective steps of the method 700. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

[00129] In some example embodiments, the apparatus may comprise means for receiving, at a first network node from a second network node, an indication that a pending mobile terminating service is initiated for a user subscription of a terminal device, wherein a user identity associated with the user subscription is registered via the terminal device and the user subscription is de-registered; and means for transmitting, to the terminal device, the indication that the pending mobile terminating service is initiated for the user subscription of the terminal device.

[00130] In some example embodiments, the apparatus may further comprise means for performing other steps in some example embodiments of the method 700. In some example embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.

[00131] In some example embodiments, an apparatus capable of performing the method 800 (for example, the second network node 106) may comprise means for performing the respective steps of the method 800. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

[00132] In some example embodiments, the apparatus may comprise means for receiving, at a second network node, a message of a pending mobile terminating service terminating for a user subscription of a terminal device, wherein a user identity associated with the user subscription of the terminal device is registered via the terminal device and the user subscription is de-registered; and means for in response to the message, transmitting, to the terminal device via a first network node, an indication that the pending mobile terminating service is initiated for the user subscription of the terminal device.

[00133] In some example embodiments, the apparatus may further comprise means for determining whether the pending mobile terminating service is marked in the service priority; and means for transmitting, to the first network node, the indication of the pending mobile terminating service based on determining that the pending mobile terminating service is marked in the service priority.

[00134] In some example embodiments, the apparatus may further comprise means for receiving an indication that the terminal device supports receiving the notification of the pending mobile terminating service.

[00135] In some example embodiments, the apparatus may further comprise means for performing other steps in some example embodiments of the method 800. In some example embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.

[00136] Reference is made to FIG. 9, which illustrates an example simplified block diagram of a device 900 that is suitable for implementing embodiments of the present disclosure. The device 900 may be provided to implement the communication device, for example the terminal device 102 as shown in FIG. 1. As shown, the device 900 includes one or more processors 910, one or more memories 920 may couple to the processor 910, and one or more communication modules 940 may couple to the processor 910.

[00137] The communication module 940 is for bidirectional communications. The communication module 940 has at least one antenna to facilitate communication. The communication interface may represent any interface that is necessary for communication with other network elements, for example the communication interface may be wireless or wireline to other network elements, or software based interface for communication.

[00138] The processor 910 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 900 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.

[00139] The memory 920 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a read only memory (ROM) 924, an electrically programmable read only memory (EPROM), a flash memory, a hard disk, a compact disc (CD), a digital video disk (DVD), and other magnetic storage and/or optical storage. Examples of the volatile memories include, but are not limited to, a random access memory (RAM) 922 and other volatile memories that will not last in the power-down duration.

[00140] A computer program 930 includes computer executable instructions that are executed by the associated processor 910. The program 930 may be stored in the ROM 924. The processor 910 may perform any suitable actions and processing by loading the program 930 into the RAM 922.

[00141] The embodiments of the present disclosure may be implemented by means of the program so that the device 900 may perform any process of the disclosure as discussed with reference to FIG. 2 to FIG. 8. The embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[00142] In some example embodiments, the program 930 may be tangibly contained in a computer readable medium which may be included in the device 900 (such as in the memory 920) or other storage devices that are accessible by the device 900. The device 900 may load the program 930 from the computer readable medium to the RAM 922 for execution. The computer readable medium may include any types of tangible non-volatile storage, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like. FIG. 10 shows an example of the computer readable medium 1000 in form of CD or DVD. The computer readable medium has the program 930 stored thereon.

[00143] Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

[00144] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the processes 600 to 800 as described above with reference to FIG. 6 to FIG. 8. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

[00145] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

[00146] In the context of the present disclosure, the computer program codes or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.

[00147] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. The term “non-transitory,” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM). [00148] Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination.

[00149] Although the present disclosure has been described in languages specific to structural features and/or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

WHAT IS CLAIMED IS:

1. A terminal device comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device at least to: receive, from a first network node, an indication that a pending mobile terminating service is initiated for a user subscription of the terminal device, wherein a user identity associated with the user subscription is registered via the terminal device; and provide the indication to an application layer of the terminal device based on the pending mobile terminating service.

2. The terminal device of claim 1, wherein the terminal device is further caused to: initiate a de-regi strati on of the user subscription.

3. The terminal device of claim 1 or 2, wherein the pending mobile terminating service is indicated by a non-access stratum (NAS) based indication with a flag, and wherein the flag indicates at least one mobile terminating service.

4. The terminal device of any of claims 1-3, wherein the pending mobile terminating service comprises at least one of the following: a short message service (SMS); a location-based service; an Internet protocol (IP) multimedia subsystem (IMS) service; or a non-IP data delivery (NIDD) service.

5. The terminal device of any of claims 1-4, wherein a subscription to the indication of the pending mobile terminating service is initiated for the user subscription of the terminal device for at least one prioritized mobile terminating service.

6. The terminal device of any of claims 1-5, wherein the terminal device is further caused to provide the indication to the application layer by: transmitting the indication from a layer of the terminal device which receives the indication to the application layer of the terminal device; and generating a notification associated with the pending mobile terminating service based on the flag.

7. The terminal device of any of claims 1-6, wherein the terminal device is further caused to: transmit, to the first network node, an indication that the terminal device supports receiving the notification of the pending mobile terminating service.

8. The terminal device of any of claims 1-7, wherein the first network node comprises an access and mobility management function (AMF).

9. A first network node comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first network node at least to: receive, from a second network node, an indication that a pending mobile terminating service is initiated for a user subscription of a terminal device, wherein a user identity associated with the user subscription is registered via the terminal device and the user subscription is de-registered; and transmit, to the terminal device, the indication that the pending mobile terminating service is initiated for the user subscription of the terminal device.

10. The first network node of claim 9, wherein the indication of the pending mobile terminating service being initiated for the user subscription of a terminal device is transmitted to the terminal device by a non-access stratum (NAS) based indication with a flag, and wherein the flag indicates at least one mobile terminating service.

11. The first network node of claim 9 or 10, wherein the pending mobile terminating service comprises at least one of the following: a short message service (SMS); a location-based service; an Internet protocol (IP) multimedia subsystem (IMS) service; or a non-IP data delivery (NIDD) service.

12. The first network node of any of claims 9-11, wherein at least one of the following: the first network node comprises an access and mobility management function

(AMF); or the second network node comprises a unified data management function (UDM) or a home subscriber server (HSS).

13. A second network node comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second network node at least to: receive a message of a pending mobile terminating service terminating for a user subscription of a terminal device, wherein a user identity associated with the user subscription of the terminal device is registered via the terminal device and the user subscription is de-registered; and in response to the message, transmit, to the terminal device via a first network node, an indication that the pending mobile terminating service is initiated for the user subscription of the terminal device.

14. The second network node of claim 13, wherein the indication of the pending mobile terminating service is transmitted to the terminal device by a non-access stratum (NAS) based indication with a flag, and wherein the flag indicates at least one mobile terminating service.

15. The second network node of claim 13 or 14, wherein the pending mobile terminating service comprises at least one of the following: a short message service (SMS); a location-based service; an Internet protocol (IP) multimedia subsystem (IMS) service; or a non-IP data delivery (NIDD) service.

16. The second network node of any of claims 13-15, wherein a subscription to the indication of the pending mobile terminating service is initiated for the user subscription of the terminal device for at least one prioritized mobile terminating service.

17. The second network node of claim 16, wherein the pending mobile terminating service is marked with a service priority.

18. The second network node of any of claims 13-17, wherein the second network node is further caused to: receive, from the terminal device, an indication that the terminal device supports receiving the notification of the pending mobile terminating service.

19. The second network node of any of claims 13-18, wherein at least one of the following: the first network node comprises an access and mobility management function (AMF); or the second network node comprises a unified data management function (UDM) or a home subscriber server (HSS).

20. A method comprising: receiving, at a terminal device from a first network node, an indication that a pending mobile terminating service is initiated for a user subscription of the terminal device, wherein a user identity associated with the user subscription is registered via the terminal device; and providing the indication to an application layer of the terminal device based on the pending mobile terminating service.

21. A method comprising: receiving, at a first network node from a second network node, an indication that a pending mobile terminating service is initiated for a user subscription of a terminal device, wherein a user identity associated with the user subscription is registered via the terminal device and the user subscription is de-registered; and transmitting, to the terminal device, the indication that the pending mobile terminating service is initiated for the user subscription of the terminal device.

22. A method comprising: receiving, at a second network node, a message of a pending mobile terminating service terminating for a user subscription of a terminal device, wherein a user identity associated with the user subscription of the terminal device is registered via the terminal device and the user subscription is de-registered; and in response to the message, transmitting, to the terminal device via a first network node, an indication that the pending mobile terminating service is initiated for the user subscription of the terminal device.

23. An apparatus comprising: means for receiving, at a terminal device from a first network node, an indication that a pending mobile terminating service is initiated for a user subscription of the terminal device, wherein a user identity associated with the user subscription is registered via the terminal device; and means for providing the indication to an application layer of the terminal device based on the pending mobile terminating service.

24. An apparatus comprising: means for receiving, at a first network node from a second network node, an indication that a pending mobile terminating service is initiated for a user subscription of a terminal device, wherein a user identity associated with the user subscription is registered via the terminal device and the user subscription is de-registered; and means for transmitting, to the terminal device, the indication that the pending mobile terminating service is initiated for the user subscription of the terminal device.

25. An apparatus comprising: means for receiving, at a second network node, a message of a pending mobile terminating service terminating for a user subscription of a terminal device, wherein a user identity associated with the user subscription of the terminal device is registered via the terminal device and the user subscription is de-registered; and means for in response to the message, transmitting, to the terminal device via a first network node, an indication that the pending mobile terminating service is initiated for the user subscription of the terminal device.

26. Anon-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method of any of claims 20-22.