Method and apparatus for opening domain information to user equipment of application function

Abstract

The embodiment of the invention provides a method and device for opening UE domain information of an application function. A method performed by a first network node in a communication network includes receiving a first request from a second network node, where the first request includes a user equipment identifier (UE ID) indicating a user equipment (UE), determining UE domain information according to the received UE ID, and sending a first response to the second network node. The first response includes the determined UE domain information. The UE domain information includes a core network type and a subscription domain.

Description

TECHNICAL FIELD

[0001] The non-limiting exemplary embodiments of the present disclosure generally relate to the field of communication technology, and in particular, to methods and apparatuses for opening of UE domain information to application function. BACKGROUND

[0002] This section introduces aspects that can facilitate a better understanding of the present disclosure. Accordingly, the statements of this section are to be read in the light of this fact, and not as admissions of what the prior art is or is not.

[0003] The Third Generation Partnership Project (3GPP) Technical Specification (TS) 23.501 V17.7.0 specifies the system architecture for the Fifth Generation Mobile Communication Technology (5G) System (5GS). Figure 1 A non-roaming architecture for service exposure for Evolved Packet Core (EPC) - Fifth Generation Core (5GC) interworking is shown.

[0004] 3GPP TS 29.503 V17.9.0 specifies unified data management services. In this specification, a Network Exposure Function (NEF) can subscribe to a Core Network (CN) type change to a Unified Data Management (UDM). SUMMARY

[0005] This summary is provided to introduce a selection of concepts that are further described below in the detailed description. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0006] More and more operators deploy 5GC and enable interworking of 5GC and EPC. Fifth Generation Mobile Communication Technology (5G) users have 5G / Fourth Generation Mobile Communication Technology (4G) handover capability when the UE moves between 5GC and EPC. This improves the user experience on the UE side.

[0007] At the same time, operators deploy Service Capability Exposure Function / Network Exposure Function (SCEF / NEF). Through the SCEF / NEF, network capabilities are exposed to Application Functions (AFs) via programmable Application Programming Interfaces (APIs).

[0008] Currently, 3GPP TS 29.503 V17.9.0 specifies unified data management services. In this specification, a NEF can subscribe to a Core Network (CN) type change to a Unified Data Management (UDM). However, the AF is not aware of the core network type for the UE. There is no mechanism and data model between the NEF and the AF to let the AF obtain the core network type for the UE.

[0009] Meanwhile, 3GPP does not define a solution for NEF / SCEF / SCEF+NEF to differentiate the subscription domain to know whether the UE is a 4G subscription or a 5G subscription, and as a result, the SCEF+NEF cannot return valid subscription domain information to the AF. For a combined SCEF+NEF, it does not know whether it needs to interact with 4GC or 5GC.

[0010] The core network type is a kind of network domain information. The core network type and the subscription domain mentioned above belong to the UE domain information.

[0011] To overcome or alleviate at least one of the problems mentioned above or other problems, embodiments of the present disclosure propose a solution for exposing UE domain information to an application function.

[0012] In a first aspect of the present disclosure, a method performed by a first network node in a communication network is provided. The method can include receiving, from a second network node, a first request. In the first request, it can include a user equipment identifier (UE ID) indicating a user equipment (UE). The method can further include determining, according to the received UE ID, UE domain information. The method can further include sending, to the second network node, a first response. The first response can include the determined UE domain information.

[0013] In an embodiment, the UE domain information can include a core network type and a subscription domain.

[0014] In an embodiment, the core network type can include at least one of the following: an evolved packet core (EPC), a fifth generation core network (5GC), a dual EPC and 5GC.

[0015] In an embodiment, the subscription domain can include at least one of the following: a fourth generation mobile communication technology subscription (4G subscription) and a fifth generation mobile communication technology subscription (5G subscription).

[0016] In an embodiment, the first network node can include a network exposure function (NEF), a service capability exposure function (SCEF), or a combination of the NEF and the SCEF.

[0017] In an embodiment, the second network node can include an application function (AF).

[0018] In an embodiment, the third network node can include a network repository function (NRF).

[0019] In an embodiment, the fourth network node can include a unified data management (UDM), or a combination of the UDM and a home subscriber server (HSS).

[0020] In a second aspect of the disclosure, a method performed by a second network node in a communication network is provided. The method can include sending a first request to a first network node. The first request can include a user equipment identifier (UE ID) that indicates a user equipment (UE). The method can also include receiving a first response from the first network node. The first response can include UE domain information according to the UE ID.

[0021] In embodiments, the UE domain information can include a core network type and a subscription domain.

[0022] In embodiments, the core network type can include at least one of: an evolved packet core (EPC), a fifth generation core network (5GC), a dual EPC and 5GC.

[0023] In embodiments, the subscription domain can include at least one of a fourth generation mobile communication technology subscription (4G subscription) and a fifth generation mobile communication technology subscription (5G subscription).

[0024] In embodiments, the first network node can include a network exposure function (NEF), a service capability exposure function (SCEF), or a combination of the NEF and the SCEF.

[0025] In embodiments, the second network node can include an application function (AF).

[0026] In a third aspect of the disclosure, an apparatus that can be implemented as a network entity is provided. The apparatus can include one or more processors and one or more memories including computer program code. The one or more memories and the computer program code can be configured to, with the one or more processors, cause the apparatus at least to perform any of the steps of the method according to the first aspect of the disclosure.

[0027] In a fourth aspect of the disclosure, an apparatus that can be implemented as a network entity is provided. The apparatus can include one or more processors and one or more memories storing computer program code. The one or more memories and the computer program code can be configured to, with the one or more processors, cause the apparatus at least to perform any of the steps of the method according to the second aspect of the disclosure.

[0028] In a fifth aspect of the disclosure, a computer readable medium having computer program code embodied thereon is provided, the computer program code, when executed on a computer, causing the computer to perform any of the steps of the method according to the first aspect or the second aspect of the disclosure.

[0029] The embodiments described herein offer numerous advantages, with a non-exhaustive list of examples provided below. A solution for exposing UE domain information to application functions is proposed. Through the proposed method, the application function (AF) can provide fine-grained services based on the exposure of UE domain information. The embodiments described herein are not limited to the features and advantages mentioned above. Additional features and advantages will be recognized by those skilled in the art after reading the following detailed description. Attached Figure Description

[0030] The above and other aspects, features, and benefits of the various embodiments of this disclosure will become more fully apparent by way of example from the following detailed description with reference to the accompanying drawings, wherein the same reference numerals or letters are used to refer to the same or equivalent elements. The drawings are shown to facilitate a better understanding of the embodiments of this disclosure and are not necessarily drawn to scale, wherein:

[0031] Figure 1 This illustrates the service open architecture for EPC-5GC interoperability;

[0032] Figure 2 A flowchart of a method according to an embodiment of the present disclosure is shown;

[0033] Figure 3 A flowchart of a method according to an embodiment of the present disclosure is shown;

[0034] Figure 4 A flowchart of a method according to an embodiment of the present disclosure is shown;

[0035] Figure 5 A flowchart of a method according to an embodiment of the present disclosure is shown;

[0036] Figure 6 An example of a communication system according to an embodiment of the present disclosure is shown;

[0037] Figure 7 This is a block diagram illustrating an apparatus suitable for practicing some embodiments of the present disclosure;

[0038] Figure 8 This is a block diagram illustrating network functionality according to embodiments of the present disclosure;

[0039] Figure 9 This is a block diagram illustrating network functionality according to embodiments of the present disclosure;

[0040] Figure 10 This is a block diagram of a host according to embodiments of the present disclosure; and

[0041] Figure 11 A communication diagram is shown in which a host communicates with a UE via a network node through a partial wireless connection according to an embodiment of the present disclosure. Detailed Implementation

[0042] Embodiments of this disclosure are described in detail with reference to the accompanying drawings. It should be understood that these embodiments are discussed only to enable those skilled in the art to better understand and thus implement this disclosure, and not to impose any limitation on the scope of this disclosure. References to features, advantages, or similar language throughout this specification do not imply that all features and advantages that can be achieved using this disclosure should be included in or in any single embodiment of this disclosure. Rather, references to features and advantages are understood to mean that a particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of this disclosure. Furthermore, in one or more embodiments, the features, advantages, and characteristics described in this disclosure may be combined in any suitable manner. Those skilled in the art will recognize that this disclosure can be practiced without one or more particular features or advantages of a particular embodiment. In other instances, additional features and advantages that may not be present in all embodiments of this disclosure may be recognized in certain embodiments.

[0043] As used herein, the term "network" refers to any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE Advanced, Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), and other wireless networks. CDMA networks can implement radio technologies such as Universal Terrestrial Radio Access (UTRA). UTRA includes WCDMA and other variations of CDMA. TDMA networks can implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA networks can implement radio technologies such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, ad hoc networks, wireless sensor networks, etc. In the following description, the terms "network" and "system" may be used interchangeably. Furthermore, communication between two devices in the network can be performed according to any suitable communication protocol, including but not limited to those defined by standards organizations such as 3GPP. For example, communication protocols may include first-generation (1G), 2G, 3G, 4G, 4.5G, 5G communication protocols and / or any other currently known or future-developed protocols.

[0044] The term "network device" or "network node" refers to any suitable network function (NF) that can be implemented in the network functions (physical or virtual) of a communication network. For example, a network function can be implemented as a network element on dedicated hardware, a software instance running on dedicated hardware, or a virtualized function instantiated on a suitable platform (e.g., on cloud infrastructure). For instance, a 5G system (5GS) can include multiple NFs such as AMF (Access and Mobility Function), SMF (Session Management Function), AUSF (Authentication Service Function), UDM (Unified Data Management), PCF (Policy Control Function), AF (Application Function), NEF (Network Open Function), UPF (User Plane Function), and NRF (Network Repository Function), RAN (Radio Access Network), SCP (Service Communication Agent), NWDAF (Network Data Analysis Function), NSSF (Network Slice Selection Function), NSWAF (Network Slice Specific Authentication and Authorization Function), etc. For example, a 4G system (such as LTE) may include an MME (Mobility Management Entity), HSS (Home Subscriber Server), Policy and Charging Rules Function (PCRF), Packet Data Network Gateway (PGW), PGW Control Plane (PGW-C), Serving Gateway (SGW), SGW Control Plane (SGW-C), E-UTRAN Node B (eNB), etc. In other embodiments, network nodes may include different types of NFs, depending on the specific network.

[0045] The term "terminal device" or "user equipment (UE)" refers to any terminal device that can access a communication network and receive services from it. By way of example and not limitation, a terminal device refers to a mobile terminal or other suitable device. A UE can be, for example, a subscriber station (SS), a portable subscriber station, a mobile station (MS), or an access terminal (AT). Terminal devices can include, but are not limited to, portable computers, image acquisition terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablet computers, wearable devices, personal digital assistants (PDAs), portable computers, desktop computers, wearable terminal devices, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), Universal Serial Bus (USB) dongles, smart devices, wireless customer premises equipment (CPEs), etc. In the following description, the terms "terminal device," "terminal," "user equipment," and "UE" are used interchangeably. As an example, a terminal device may refer to a UE configured to communicate according to one or more communication standards (such as 3GPP's LTE or NR standards) issued by 3GPP (3rd Generation Partnership Project). As used herein, "User Equipment" or "UE" need not necessarily be a "user" in the sense of a human user who owns and / or operates the associated equipment. In some embodiments, a terminal device may be configured to send and / or receive information without direct human interaction. For example, a terminal device may be designed to send information to the network according to a predetermined schedule when triggered by an internal or external event or in response to a request from the network. Conversely, a UE may refer to a device intended for sale to or operated by a human user, but which may not initially be associated with a particular human user.

[0046] As another example, in the Internet of Things (IoT) scenario, a terminal device may represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another terminal device and / or network device. In this case, the terminal device may be a machine-to-machine (M2M) device, which in the 3GPP context may be referred to as a machine-type communication (MTC) device. As a specific example, a terminal device may be a UE that implements the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (such as power meters), industrial machinery, or household or personal appliances (such as refrigerators, televisions, personal wearable devices (such as watches), etc.). In other scenarios, a terminal device may represent a vehicle or other device capable of monitoring and / or reporting its operational status or other functions associated with its operation.

[0047] References to "an embodiment," "embodiment," and "example embodiment," etc., in the specification indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is considered that, whether explicitly described or not, the influence of other embodiments on such feature, structure, or characteristic is within the knowledge of those skilled in the art.

[0048] It should 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 distinguish one element from another only. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed terms.

[0049] As used herein, the phrase “at least one of A and B” or “at least one of A or B” should be understood to mean “only A, only B, or both A and B”. The phrase “A and / or B” should be understood to mean “only A, only B, or both A and B”.

[0050] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well. It will be further understood that the terms “comprising,” “including,” “having,” “containing,” and / or “including” as used herein specify the presence of a feature, element, and / or component, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0051] The terms Core Network Type, Core Network Type (CN Type), Core Network Type (cnType), and Core Network Type (CnType) are all used to describe the registration type to the core network.

[0052] Note that the terms used in this document are for ease of description and differentiation of nodes, devices, or networks. As technology evolves, other terms with similar / identical meanings may also be used.

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

[0054] More and more operators are deploying 5GC and enabling interoperability between 5GC and EPC. When the UE moves between 5GC and EPC, 5G users have 5G / 4G handover capability. This improves the user experience on the UE side.

[0055] Simultaneously, operators deploy SCEF / NEF (Service Capability Exposure Function, Network Exposure Function). Through NEF / SCEF, network capabilities are exposed to application functions (AFs) via programmable application programming interfaces (APIs). This improves the user experience on the AF side. For example, as defined in Section 4.15.3 "Event Exposure using NEF" of 3GPP TS 23.502 v17.7.0, the AF can monitor the status / events of UE reachability, roaming, PDU session establishment / release, location changes, etc.

[0056] For example, the information currently open to the AF as defined in Section 5.3.2.4.3 "Enumeration: MonitoringType" of 3GPP 29.122 is given in Table 1 below.

[0057] Table 1. Enumeration: MonitoringType

[0058]

[0059] Currently, 3GPP TS29.503 V17.9.0 specifies the Unified Data Management Service. In this specification, NEF can change its subscription core network (CN) type to Unified Data Management (UDM).

[0060] However, the AF is unaware of the core network type used by the UE. There is no mechanism or data model between the NEF and the AF to allow the AF to obtain the core network type used by the UE.

[0061] Meanwhile, 3GPP has not defined a solution for distinguishing subscription domains for SCEF+NEF / NEF / SCEF to determine whether the UE is subscribing to 4G or 5G. As a result, SCEF+NEF / NEF / SCEF cannot return valid subscription domain information to the AF. For combined SCEF+NEF, it does not know whether it needs to interact with 4GC or 5GC.

[0062] The core network type and subscription domain mentioned above belong to UE domain information. The core network type is a type of network domain information.

[0063] UE domain information may include at least one of subscription domain and network domain information (core network type).

[0064] In this disclosure, UE domain information may include at least one of subscription domain and core network type.

[0065] To overcome or mitigate at least one of the problems mentioned above or other issues, embodiments of this disclosure propose a solution for exposing UE domain information to application functions based on the UE ID.

[0066] Figure 1 The architecture for service exposure for EPC-5GC interoperability, as defined in 3GPP TS 23.501 v17.7.0, is shown. If the UE is able to move between EPS and 5GS, the network is expected to associate the UE with the SCEF+NEF node for service capability exposure.

[0067] exist Figure 1 In this context, the EPC interface represents the southbound interface between SCEF and the EPC node, such as the S6t interface between SCEF and HSS, or the T6a interface between SCEF and MME.

[0068] The 5GC interface represents the southbound interface between NEF and the 5GC network function, such as the N29 interface between NEF and SMF, the N30 interface between NEF and PCF, etc.

[0069] Interaction between the SCEF and NEF within the combined SCEF+NEF is required. For example, when SCEF+NEF supports the monitoring API, if the UE moves between EPC and 5GC, the SCEF and NEF need to share context and status information about the monitoring events configured for the UE.

[0070] Northbound APIs, which can be supported by EPC or 5GC networks, are discovered by SCEF+NEF nodes.

[0071] Figure 2 A flowchart of a method according to an embodiment of the present disclosure is shown, which can be performed by means implemented in / being implemented as or communicatively coupled to a first network node. Therefore, the means can provide components for implementing various parts of method 200, as well as components for implementing other processes in conjunction with other components.

[0072] At box 202, the first network node can receive a first request from the second network node. The first request may include a user equipment identifier (UE ID) indicating a user equipment (UE).

[0073] At box 204, the first network node can determine the UE domain information based on the received UE ID.

[0074] At box 206, the first network node may send a first response to the second network node. The first response may include the determined UE domain information.

[0075] The first request can be any suitable message, such as an HTTP POST request, an HTTP GET request, etc.

[0076] The first response can be any suitable message, such as an HTTP POST response, an HTTP GET response, etc.

[0077] The UE ID can be any suitable information that can be used to identify one or more user equipments, such as at least one of the following: UE address (such as IP address or MAC (Media Access Control) address), General Public Subscription Identifier (GPSI), Subscription Permanent Identifier (SUPI), Integrated Services Digital Network for Mobile Stations (MSISDN), and External Identifier (ID).

[0078] The first network node can be a physical entity or a virtualized network function. For example, the first network node can be any suitable network device, node, entity, or function (physical or virtual) that can provide network open functions or service capability open functions.

[0079] In this embodiment, the first network node may provide means for securely exposing services and capabilities offered through a network interface. The first network node may provide means for discovering exposed services and capabilities. The first network node may provide access to network capabilities through a homogeneous network application programming interface (e.g., a network API). The first network node may extract services from underlying network interfaces and protocols.

[0080] In one embodiment, the first network node may be a NEF as described in 3GPP TS 23.501 V17.7.0. In another embodiment, the first network node may be a SCEF. In yet another embodiment, the first network node may include a combination of NEF and SCEF.

[0081] In this embodiment, the second network node can be a physical entity or a virtualized network function. For example, a network node can be any suitable network device, node, entity, or function (physical or virtual) that provides application functionality. The second network node can be an application function (AF) as described in 3GPP TS 23.501 V17.7.0. In another embodiment, the second network node can be a Service Capability Server (SCS) / Application Server (AS) as described in 3GPP TS 23.682 V17.3.0.

[0082] In this embodiment, UE domain information may include at least one of core network type and subscription domain.

[0083] In this disclosure, the terms core network type, core network type (CN type), core network type (cnType), core network type (CnType), etc., are used to describe the registration type to the core network.

[0084] In an embodiment, the core network type (CnType) may include at least one of the following: Evolved Packet Core (EPC), Fifth Generation Core Network (5GC), Dual EPC and 5GC.

[0085] For example, Table 2a shows an enumeration of CnType. CnType can include three different kinds of core network types of the UE: EPC, 5GC, Dual EPC, and 5GC. The three different types of CnType can take any suitable form, such as arrays, indicators, bits, or flags.

[0086] In an embodiment, the core network type (CnType) may include at least one of SINGLE_4G, SINGLE_5G, and DUAL_4G5G. Its enumeration is shown in Table 2b.

[0087] “EPC” corresponds to “SINGLE_4G”, “5GC” corresponds to “SINGLE_5G”, and “Dual EPC and 5GC” corresponds to “DUAL_4G5G”.

[0088] The three different types of core network types can be represented by any suitable name for the three registration types in the core network.

[0089] Table 2a. Enumeration of CnType

[0090]

[0091] Table 2b. Enumeration of CnType

[0092]

[0093] The subscription domains used for UEs may include fourth-generation mobile communication technology subscriptions (4G subscriptions) and fifth-generation mobile communication technology subscriptions (5G subscriptions).

[0094] Table 3 shows examples of enumerated subscription fields. Subscription fields can take any suitable form, such as arrays, indicators, bits, or flags.

[0095] Table 3. Enumeration of "Subscription Domains"

[0096]

[0097] In one embodiment, determining the UE domain information (core network type and / or subscription domain) based on the received UE ID may include: sending a second request to a third network node to discover whether a fourth network node service instance exists for the UE ID, and receiving a second response from the third network node. The second response indicates whether a fourth network node service instance exists for the UE ID.

[0098] In an embodiment, when the second response indicates that there is no fourth network node service instance for UE ID, the method may further include: determining the subscription domain as 4G subscription and determining the first core network type as EPC.

[0099] In an embodiment, when the second response indicates the existence of a fourth network node service instance for the UE ID, the method may further include: sending a third request to the fourth network node to subscribe to a core network type change based on the UE ID.

[0100] In an embodiment, the method may further include: receiving a third response from a fourth network node, wherein the third response indicates that, based on the core network type of the UE ID, the core network type included in the UE domain information is determined as the core network type received based on the UE ID in the third response, and the subscription domain is determined as a 5G subscription.

[0101] In an embodiment, when the UE moves between the EPC and 5GC, the method may further include: receiving a first message from a fourth network node, wherein the first message includes an updated core network type based on the UE ID, determining the core network type included in the UE domain information as the updated core network type received in the first message, and determining the subscription domain as a 5G subscription. The method may further include: sending a second message to a second network node. The second message may include updated UE domain information. The updated UE domain information may include the updated core network type and subscription domain.

[0102] In this embodiment, the first request may be a network open feature event exposure subscription request. For example, the first request is an Nnef_EventExposure_Subscribe request.

[0103] In this embodiment, the first response may be a Network Open Function Event Exposure Subscription response. For example, the first response is an Nnef_EventExposure_Subscribe response.

[0104] In this embodiment, the first message may be a notification message. For example, the first message is a Nudm_EventExposure_Notify message.

[0105] In this embodiment, the second message can be a notification message. For example, the first message is an Nnef_EventExposure notification.

[0106] In an embodiment, the third network node may include a network repository function (NRF).

[0107] In an embodiment, the fourth network node may include a unified data management (UDM) or a combination of a UDM and a home subscriber server (HSS).

[0108] Figure 3 A flowchart of a method according to an embodiment of the present disclosure is shown, which can be performed by means implemented in / being implemented as a first network node or communicatively coupled to a first network node. Therefore, the means can provide components for implementing various parts of method 300, as well as components for implementing other processes in conjunction with other components.

[0109] At box 302, the first network node can receive a first request from the second network node. The first request may include a user equipment identifier (UE ID) indicating a user equipment (UE).

[0110] At box 304, the first network node may send a first response to the second network node. The first response may include the core network type and / or subscription domain for the requested UE ID.

[0111] The first request can be any suitable message, such as an HTTP POST request, an HTTP GET request, etc.

[0112] The first response can be any suitable message, such as an HTTP POST response, an HTTP GET response, etc.

[0113] The UE ID can be any suitable information that can be used to identify one or more user equipments, such as at least one of the following: UE address (such as IP address or MAC (Media Access Control) address), General Public Subscription Identifier (GPSI), Subscription Permanent Identifier (SUPI), Integrated Services Digital Network for Mobile Stations (MSISDN), and External Identifier (ID).

[0114] In an embodiment, the first network node may further include determining the core network type and / or subscription domain based on the received UE ID.

[0115] The first network node can be a physical entity or a virtualized network function. For example, the first network node can be any suitable network device, node, entity, or function (physical or virtual) that can provide network open functions or service capability open functions.

[0116] In this embodiment, the first network node may provide means for securely exposing services and capabilities offered through a network interface. The first network node may provide means for discovering exposed services and capabilities. The first network node may provide access to network capabilities through a homogeneous network application programming interface (e.g., a network API). The first network node may extract services from underlying network interfaces and protocols.

[0117] In one embodiment, the first network node may be a NEF as described in 3GPP TS 23.501 V17.7.0. In another embodiment, the first network node may be a SCEF. In yet another embodiment, the first network node may include a combination of NEF and SCEF.

[0118] In this embodiment, the second network node can be a physical entity or a virtualized network function. For example, a network node can be any suitable network device, node, entity, or function (physical or virtual) that provides application functionality. The second network node can be an application function (AF) as described in 3GPP TS 23.501 V17.7.0. In another embodiment, the second network node can be a Service Capability Server (SCS) / Application Server (AS) as described in 3GPP TS 23.682 V17.3.0.

[0119] In an embodiment, the core network type may include at least one of the following: Evolved Packet Core (EPC), Fifth Generation Core Network (5GC), Dual EPC and 5GC.

[0120] In this disclosure, the terms core network type, core network type (CN type), core network type (cnType), core network type (CnType), etc., are used to describe the registration type to the core network.

[0121] In an embodiment, the core network type may include at least one of the following: Evolved Packet Core (EPC), Fifth Generation Core Network (5GC), Dual EPC and 5GC.

[0122] For example, Table 2a shows an enumeration of CnType. CnType can include three different types of core networks for the UE: EPC, 5GC, Dual EPC, and 5GC. The three different types of CnType can take any suitable form, such as arrays, indicators, bits, or flags.

[0123] In another embodiment, the core network type may include at least one of SINGLE_4G, SINGLE_5G, and DUAL_4G5G. An enumeration of this type is shown in Table 2b.

[0124] “EPC” corresponds to “SINGLE_4G”, “5GC” corresponds to “SINGLE_5G”, and “Dual EPC and 5GC” corresponds to “DUAL_4G5G”.

[0125] The three different types of core network types can be represented by any suitable name for the three registration types in the core network.

[0126] The subscription domains used for UEs may include fourth-generation mobile communication technology subscriptions (4G subscriptions) and fifth-generation mobile communication technology subscriptions (5G subscriptions).

[0127] Table 3 shows examples of enumerated subscription fields. Subscription fields can take any suitable form, such as arrays, indicators, bits, or flags.

[0128] In this embodiment, determining the core network type and subscription domain based on the received UE ID includes: sending a second request to a third network node to discover whether a fourth network node service instance exists for the UE ID, and receiving a second response from the third network node. The second response indicates whether a fourth network node service instance exists for the UE ID.

[0129] In an embodiment, when the second response indicates that there is no fourth network node service instance for the UE ID, the method may further include: determining the subscription domain as a 4G subscription and determining the first core network type as "EPC".

[0130] In an embodiment, when the second response indicates the existence of a fourth network node service instance for the UE ID, the method may further include: sending a third request to the fourth network node to subscribe to the core network type based on the UE ID.

[0131] In an embodiment, the method may further include: receiving a third response from a fourth network node, wherein the third response indicates that the core network type is determined as the core network type received according to the UE ID in the third response based on the core network type of the UE ID, and the subscription domain is determined as 5G subscription.

[0132] In an embodiment, when the UE moves between EPC and 5GC, the method may further include: receiving a first message from a fourth network node. The first message may include the current core network type based on the UE ID. The method further includes: determining the core network type as the updated core network type received in the first message, determining the subscription domain as a 5G subscription, and sending a second message to a second network node. The second message may include the determined core network type and the determined subscription domain.

[0133] In this embodiment, the first request may be a network open feature event exposure subscription request. For example, the first request is an Nnef_EventExposure_Subscribe request.

[0134] In this embodiment, the first response may be a Network Open Function Event Exposure Subscription response. For example, the first response is an Nnef_EventExposure_Subscribe response.

[0135] In this embodiment, the first message may be a notification message. For example, the first message is a Nudm_EventExposure_Notify message.

[0136] In this embodiment, the second message can be a notification message. For example, the first message is an Nnef_EventExposure notification.

[0137] In an embodiment, the third network node may include a network repository function (NRF).

[0138] In an embodiment, the fourth network node may include a unified data management (UDM) or a combination of a UDM and a home subscriber server (HSS).

[0139] Figure 4 A flowchart of a method according to an embodiment of the present disclosure is shown, which can be performed by means implemented in / being implemented as a second network node or communicatively coupled to a second network node. Therefore, the means can provide components for implementing various parts of method 400, as well as components for implementing other processes in conjunction with other components.

[0140] At box 402, the second network node may send a first request to the first network node. The first request may include a User Equipment Identifier (UE ID) indicating a User Equipment (UE).

[0141] At box 404, the second network node can receive a first response from the first network node. The first response may include UE domain information based on the UE ID.

[0142] The first request can be any suitable message, such as an HTTP POST request, an HTTP GET request, etc.

[0143] The first response can be any suitable message, such as an HTTP POST response, an HTTP GET response, etc.

[0144] The UE ID can be any suitable information that can be used to identify one or more user equipments, such as at least one of the following: UE address (such as IP address or MAC (Media Access Control) address), General Public Subscription Identifier (GPSI), Subscription Permanent Identifier (SUPI), Integrated Services Digital Network for Mobile Stations (MSISDN), and External Identifier (ID).

[0145] The second network node can be a physical entity or a virtualized network function. For example, the second network node can be any suitable network device, node, entity, or function (physical or virtual) that can provide network open functions or service capability open functions.

[0146] In this embodiment, the second network node can be a physical entity or a virtualized network function. For example, a network node can be any suitable network device, node, entity, or function (physical or virtual) that provides application functionality. The second network node can be an application function (AF) as described in 3GPP TS 23.501 V17.7.0. In another embodiment, the second network node can be a Service Capability Server (SCS) / Application Server (AS) as described in 3GPP TS 23.682 V17.3.0.

[0147] In an embodiment, the first network node may include Network Open Function (NEF), or Service Capability Open Function (SCEF), or a combination of NEF and SCEF.

[0148] In an embodiment, UE domain information may include at least one of core network type and subscription domain.

[0149] For example, Table 2a shows an enumeration of CnType. CnType can include three different types of core networks for the UE: EPC, 5GC, Dual EPC, and 5GC. The three different types of CnType can take any suitable form, such as arrays, indicators, bits, or flags.

[0150] In another embodiment, the core network type (CnType) may include at least one of SINGLE_4G, SINGLE_5G, and DUAL_4G5G. Its enumeration is shown in Table 2b.

[0151] “EPC” corresponds to “SINGLE_4G”, “5GC” corresponds to “SINGLE_5G”, and “Dual EPC and 5GC” corresponds to “DUAL_4G5G”.

[0152] The three different types of core network types can be represented by any suitable name for the three registration types in the core network.

[0153] In this embodiment, the subscription domain may include at least one of fourth-generation mobile communication technology subscription (4G subscription) and fifth-generation mobile communication technology subscription (5G subscription). An enumeration of subscription domains is shown in Table 3.

[0154] In this embodiment, the first request may be a network open feature event exposure subscription request. For example, the first request is an Nnef_EventExposure_Subscribe request.

[0155] In this embodiment, the first response may be a Network Open Function Event (NNEF) subscription response. For example, the first response is an Nnef_EventExposure_Subscribe message.

[0156] In this embodiment, the second message can be a notification message. For example, the first message is an Nnef_EventExposure notification.

[0157] In an embodiment, when the UE moves between EPC and 5GC, the method may further include receiving a second message from a first network node. The second message may include updated UE domain information and core network type based on the UE ID. The updated UE domain information may include an updated core network type and subscription domain.

[0158] In an embodiment, the first network node may include Network Open Function (NEF), Service Capability Open Function (SCEF), or a combination of NEF and SCEF.

[0159] In an embodiment, the second network node may include application functions (AF).

[0160] Figure 5 An example of a communication system according to an embodiment of this disclosure is shown. Four network nodes are present.

[0161] The first network node can be NEF, SCEF, or a combination of NEF and SCF.

[0162] The second network node can be an application function (AF).

[0163] The third network node can be an NRF.

[0164] The fourth network node can be a UDM or a combination of UDM and HSS.

[0165] In the 5GC architecture, each NF producer registers its own service with the NRF, and other NF consumers discover the registered service via the NRF by inputting specific parameters. This process is described in Section 4.17.4 of 3GPP TS23.502 v17.7.0.

[0166] UDM is dedicated to the management of 5G subscriptions. It registers its services with the NRF. Each UDM instance is responsible for a specific UE segment. UE segments use different UE ID ranges, such as GPSI ranges.

[0167] In step 1, the second network node (AF) may send a subscription request to the first network node (NEF / SCEF / NEF+SCF) to subscribe to the Nnef_APISupportCapability service for the user equipment (UE). The UE ID is used to indicate the UE. This request can be an Nnef_EventExposure Subscribe request, which includes the parameters UE ID, event type (API_Support_Capability), and callback URI. The request can be an Nnef_EventExposureSubscribe(UE ID, event type (API_Support_Capability), callback URI) message.

[0168] In step 2, the first network node can discover the EventExposure service of the fourth network node (UDM / HSS) by sending an Nnrf_NFDiscovery_Request to the third network (NRF). The service discovery process is described in detail in section 4.17.4 of 3GPP TS23.502.

[0169] For example, the first network node sends a request to NRF. The request is GET / nnrf-disc / v1 / nf-instances?target-nf-type=UDM&requester-nf-type=NEF&service-names=nudm-ee&gpsi=gpsi.

[0170] The first network node can determine the subscription domain for the UE based on the UDM discovery response from the NRF.

[0171] If the UDM EventExposure service instance is not found in the discovery response, the first network node can determine that this is a 4G subscription for the UE. It can determine that the UE's subscription domain is "4G" subscription. It can determine that the core network type (CType) is "SINGLE_4G" / "EPC".

[0172] In an embodiment, the core network type may include at least one of the following: Evolved Packet Core (EPC), Fifth Generation Core Network (5GC), Dual EPC and 5GC.

[0173] For example, Table 2a shows an enumeration of CnTypes. CnTypes can include three different types of registration for the UE's core network: EPC, 5GC, Dual EPC, and 5GC. The three different types of CnTypes can take any suitable form, such as arrays, indicators, bits, or flags. The three different types of CnTypes can take any suitable name, such as SINGLE_4G, SINGLE_5G, and DUAL_4G5G, which can also be used to represent the three CnTypes, as shown in Table 2b.

[0174] Table 2a. Enumeration of CnType

[0175]

[0176] Table 2b. Enumeration of CnType

[0177]

[0178] The subscription domains used for UEs may include fourth-generation mobile communication technology subscriptions (4G subscriptions) and fifth-generation mobile communication technology subscriptions (5G subscriptions).

[0179] Table 3 shows examples of enumerated subscription fields. Subscription fields can take any suitable form, such as arrays, indicators, bits, or flags.

[0180] Table 3. Enumeration of "Subscription Domains"

[0181]

[0182] Otherwise, if a UDM EventExposure service instance is present in the discovery response, the first network node can determine that this is a 5G subscription. It can then perform steps 3b to 5b to subscribe to the core network type change event from the UDM, and steps 6b to 7b to obtain the core network type change event notification from the UDM.

[0183] Step 3a, (This is a 4G subscription) Based on the CN type (“SINGLE_4G”) and subscription domain (“4G”), the first network node can determine the availability or expected level of support for the public API for the received UE ID.

[0184] The first network node can determine the UE domain information. In the UE domain information, CnType = “SIGNLE_4G” or “EPC”, and the subscription domain = “4G”.

[0185] The first network node can immediately send a MonitoringEventReport with the CnType parameter and the subscription domain in the Nnef_EventExposure_Subscribe response message. Simultaneously, the availability or expected level of support for the public API is also included in the Nnef_EventExposure_Subscribe response. The first network node can then send a response to the AF.

[0186] Step 3b (This is 5G subscription) The first network node can subscribe to the core network type change event from the UDM by sending a Nudm_EventExposure_Subscribe request (CN type change, report type, UE ID, report duration) message.

[0187] Step 4b (This is for 5G subscription): Based on the received UE ID, the UDM can determine the CnType for the indicated UE based on the registered MME or AMF. The UDM can send a Nudm_EventExposure_Subscribe response to the first network node to notify it of the new CnType for the UE.

[0188] The new CnType can be included in CnTypeChangeReport.

[0189] Table 4 shows the definition of a report as described in 3GPP TS29.503 v17.9.0.

[0190] Table 4 Report

[0191]

[0192] The CnTypeChangeReport is described in detail in 3GPP TS29.503 v17.9.0. Table 5 shows the definition of CnTypeChangeReport.

[0193] Table 5 Definition of type CnTypeChangeReport

[0194]

[0195] Step 5b (This is for 5G subscription): Based on the CnType received from the UDM / HSS and the determined subscription domain. Subscription domain = "5G" subscription. The first network node can determine the availability of supported APIs for the indicated UE.

[0196] The first network node can send an Nnef_EventExposure Subscribe response to the second network node. This response includes the MonitoringEventReport and API support capabilities. The MonitoringEventReport can include the CnType and subscription domain in the report.

[0197] Step 6b: When the fourth network node (UDM or HSS) detects that the indicated UE is switching between EPC and 5GC, the UDM can determine the CnType for the indicated UE. The fourth network node (UDM / HSS) can notify the first network node of the CnType by sending Nudm_EventExposure_Notify (CN type).

[0198] Step 7b: Based on the received CnType (“SINGLE_4G”, “SINGLE_5G”, or “DUAL_4G5G”) and subscription domain (subscription domain = 5G), the first network node can determine the availability of supported APIs for the requested UE ID.

[0199] The first network node can send an Nnef_EventExposure notification to the second network node. This notification includes the MonitoringEventReport and API support capabilities. The MonitoringEventReport may include an updated CnType and subscription domain. The CnType is updated to the received newCnType, i.e., CnType = newCnType. The subscription domain = "5G". Furthermore, the MonitoringEventReport may include API support capabilities. The first network node can also send an Nnef_EventExposure Notify to the second network node.

[0200] To support the above solution, the cnType information element and the subscriptionDomain information element have been added to MonitoringEventReport.

[0201] Table 6: Definition of the type MonitoringEventReport

[0202]

[0203] The subscription domain can be included in the MonitoringEventReport to indicate the subscriber type, such as 4G subscription or 5G subscription.

[0204] If AF requests a one-time report from NEF in step 1 (e.g., maxNumberReport=1), then steps 6b-7b are omitted.

[0205] The embodiments described herein offer numerous advantages, with a non-exhaustive list of examples provided below. A solution for exposing UE domain information to application functions is proposed. Through the proposed method, the application processor (AF) can provide fine-grained services based on the exposure of UE domain information. For example, if the UE has registered with 5GS, the AF provides higher video quality. The embodiments described herein are not limited to the features and advantages mentioned above. Additional features and advantages will be appreciated by those skilled in the art upon reading the following detailed description.

[0206] Figure 6 This is a block diagram illustrating an apparatus suitable for practicing some embodiments of the present disclosure. For example, the first network node described above can be implemented as or through apparatus 600.

[0207] The device 600 includes at least one processor 601 (such as a digital processor (DP)) and at least one memory (MEM) 602 coupled to the processor 601. The device 600 may also include a transmitter TX and a receiver RX 603 coupled to the processor 601. The MEM 602 stores a program (PROG) 604. The PROG 604 may include instructions that, when executed on the associated processor 601, enable the device 600 to operate according to embodiments of the present disclosure. Combinations of at least one processor 601 and at least one MEM 602 can form a processing device 605 suitable for implementing various embodiments of the present disclosure.

[0208] Various embodiments of this disclosure can be implemented by a computer program executable by one or more of a processor 601, software, firmware, hardware, or a combination thereof.

[0209] MEM 602 can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples.

[0210] Processor 601 may be of any type suitable for the local technical environment and may include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture, as a non-limiting example.

[0211] In embodiments where the device is implemented as a network node or at a network node, memory 602 contains instructions executable by processor 601, thereby enabling the network node to operate according to any methods associated with the network node as described above.

[0212] In embodiments where the device is implemented as an application node or at an application node, the memory 602 contains instructions executable by the processor 601, thereby enabling the application node to operate according to any methods associated with the application node as described above.

[0213] Figure 7 This is a block diagram illustrating an apparatus suitable for practicing some embodiments of the present disclosure. For example, the second network node described above can be implemented as or through apparatus 700.

[0214] The device 700 includes at least one processor 701 (such as a digital processor (DP)) and at least one memory (MEM) 702 coupled to the processor 701. The device 700 may also include a transmitter TX and a receiver RX 703 coupled to the processor 701. The MEM 702 stores a program (PROG) 704. The PROG 704 may include instructions that, when executed on the associated processor 701, enable the device 700 to operate according to embodiments of the present disclosure. Combinations of at least one processor 701 and at least one MEM 702 can form a processing device 705 suitable for implementing various embodiments of the present disclosure.

[0215] Various embodiments of this disclosure can be implemented by a computer program executable by one or more of a processor 701, software, firmware, hardware, or a combination thereof.

[0216] MEM 702 can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples.

[0217] Processor 701 may be of any type suitable for the local technical environment and may include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture, as a non-limiting example.

[0218] In embodiments where the device is implemented as a network node or at a network node, memory 702 contains instructions executable by processor 701, thereby enabling the network node to operate according to any methods associated with the network node as described above.

[0219] In embodiments where the device is implemented as an application node or at an application node, memory 702 contains instructions executable by processor 701, thereby enabling the application node to operate according to any methods associated with the application node as described above.

[0220] Figure 8 This is a block diagram illustrating a network node according to an embodiment of the present disclosure.

[0221] As shown in the figure, the first network node 800 may include a first receiving module 801, which is configured to receive a first request from the second network node, wherein the first request includes a user equipment identifier (UE ID) indicating a user equipment (UE).

[0222] In an embodiment, the first network node 800 further includes a first determining module 807, which is configured to determine UE domain information based on the received UE ID.

[0223] In one embodiment, the first network node 800 may further include a first sending module 802, which is configured to send a first response to the second network node. The first response may include the determined UE domain information.

[0224] In an embodiment, the first network node 800 may further include a second sending module 804, which is configured to send a second request to the third network node to discover whether a fourth network node service instance for UE ID exists.

[0225] In an embodiment, the first network node 800 may further include a second receiving module 803 configured to receive a second response from a third network node, wherein the second response indicates whether a fourth network node service instance for UE ID exists.

[0226] In an embodiment, the first network node 800 may further include a third sending module 806, which is configured to send a third request to the fourth network node to subscribe to the core network type change based on the UE ID when the second response indicates the existence of a fourth network node service instance for the UE ID.

[0227] In an embodiment, the first network node 800 may further include a third receiving module 805, which is configured to receive a response or message from a fourth network node.

[0228] Figure 9 This is a block diagram illustrating a network node according to an embodiment of the present disclosure.

[0229] As shown in the figure, the second network node 900 may include a sending module 901 configured to send a first request to the first network node. The first request may include a user equipment identifier (UE ID) indicating a user equipment (UE).

[0230] In an embodiment, the second network node 900 may further include a first receiving module 902, which is configured to receive a first response from the first network node. The first response may include UE domain information based on the UE ID.

[0231] In this embodiment, the second network node 900 may further include a second receiving module 903, which is configured to receive a second message from the first network node. The second message may include updated UE domain information based on the UE ID.

[0232] Figure 10 An example of a communication system QQ1000 according to some embodiments is shown.

[0233] In the example, the communication system QQ1000 includes a telecommunications network QQ1002, which includes an access network QQ1004 (such as a radio access network (RAN)) and a core network QQ1006. The core network QQ1006 includes one or more core network nodes QQ1008. The access network QQ1004 includes one or more access network nodes, such as network nodes QQ1010a and QQ1010b (one or more of which may be generally referred to as network node QQ1010), or any other similar 3GPP access node or non-3GPP access point. Network node QQ1010 facilitates direct or indirect connections of user equipment (UE), such as by connecting UEs QQ1012a, QQ1012b, QQ1012c, and QQ1012d (one or more of which may be generally referred to as UE QQ1012) to the core network QQ1006 via one or more radio connections.

[0234] Examples of wireless communication via wireless connection include sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without the use of wires, cables, or other conductors. Furthermore, in various embodiments, the communication system QQ1000 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals, whether via a wired or wireless connection. The communication system QQ1000 may include and interface with any type of communication, telecommunications, data, cellular, radio network, and / or other similar type of system.

[0235] UE QQ1012 can be any of a variety of communication devices, including wireless devices that are deployed, configured, and / or operable to communicate wirelessly with network node QQ1010 and other communication devices. Similarly, network node QQ1010 is deployed, capable of, configured, and / or operable to communicate directly or indirectly with UE QQ1012 and / or with other network nodes or devices in telecommunication network QQ1002 to enable and / or provide network access (such as wireless network access) and / or perform other functions (such as management in telecommunication network QQ1002).

[0236] In the depicted example, core network QQ1006 connects network node QQ1010 to one or more hosts, such as host QQ1016. These connections can be direct or indirect via one or more intermediate networks or devices. In other examples, network nodes can be directly coupled to hosts. Core network QQ1006 includes one or more core network nodes (e.g., core network node QQ1008) constructed with hardware and software components. The characteristics of these components can be substantially similar to those described with respect to UE, network nodes, and / or hosts, such that the description generally applies to the corresponding components of core network node QQ1008. Example core network nodes include one or more of the following functions: Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier Dehiding Function (SIDF), Unified Data Management (UDM), Security Edge Protection Agent (SEPP), Network Open Function (NEF) and / or User Plane Function (UPF), Control Function (PCF), Unified Data Management (UDM), etc.

[0237] The host QQ1016 may be owned or controlled by a service provider other than the operator or provider of the access network QQ1004 and / or the telecommunications network QQ1002, and may be operated by or on behalf of the service provider. The host QQ1016 may host various applications or application functions (AFs) to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services (such as retrieving and compiling data from various environmental conditions detected by multiple UEs), analytics functions, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by the server.

[0238] As a whole, Figure 10The QQ1000 communication system enables connections between the UE, network nodes, and the host. In this sense, the communication system can be configured to operate according to predefined rules or procedures, such as specific standards including but not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi); and / or any other suitable wireless communication standards, such as Global Microwave Access Interoperability (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any Low Power Wide Area Network (LPWAN) standards, such as LoRa and Sigfox.

[0239] In some examples, the QQ1002 telecommunications network is a cellular network implementing 3GPP standardized features. Therefore, the QQ1002 network can support network slicing to provide different logical networks to different devices connected to the QQ1002 network. For example, the QQ1002 network can provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs while providing enhanced mobile broadband (eMBB) services to other UEs, and / or massive machine-type communication (mMTC) / massive IoT services to yet another UE.

[0240] In some examples, UE QQ1012 is configured to send and / or receive information without direct human interaction. For example, the UE may be designed to send information to access network QQ1004 on a predetermined schedule when triggered by internal or external events or in response to a request from access network QQ1004. Furthermore, the UE may be configured to operate in single RAT, multi-RAT, or multi-standard modes. For example, the UE may operate using any one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., configured for multi-radio dual connectivity (MR-DC), such as e-UTRAN (Evolved UMTS Terrestrial Radio Access Network) New Radio Dual Connectivity (EN-DC).

[0241] In the example, hub QQ1014 communicates with access network QQ1004 to facilitate indirect communication between one or more UEs (e.g., UEQQ1012c and / or QQ1012d) and network nodes (e.g., network node QQ1010b). In some examples, hub QQ1014 may be a controller, router, content source, and analytics, or any other communication device relating to the UE described herein. For example, hub QQ1014 may be a broadband router that enables the UE to access core network QQ1006. As another example, hub QQ1014 may be a controller that sends commands or instructions to one or more actuators in the UE. Commands or instructions may be received from the UE, network node QQ1010, or via executable code, scripts, procedures, or other instructions in hub QQ1014. As another example, hub QQ1014 may be a data collector that acts as temporary storage for UE data, and in some embodiments, data analytics or other processing may be performed. As another example, hub QQ1014 may be a content source. For example, for a UE acting as a VR headset, display, speaker, or other media delivery device, the hub QQ1014 can retrieve VR assets, video, audio, or other media or data related to sensory information via network nodes. The hub QQ1014 then provides this directly to the UE after performing local processing and / or adding additional local content. In yet another example, the hub QQ1014 acts as a proxy server or orchestrator for the UE, particularly when one or more devices in the UE are low-power IoT devices.

[0242] Hub QQ1014 can have a constant / persistent or intermittent connection to network node QQ1010b. Hub QQ1014 can also allow different communication schemes and / or scheduling between hub QQ1014 and UEs (e.g., UE QQ1012c and / or QQ1012d) and between hub QQ1014 and core network QQ1006. In other examples, hub QQ1014 is connected to core network QQ1006 and / or one or more UEs via a wired connection. Furthermore, hub QQ1014 can be configured to connect to an M2M service provider via access network QQ1004 and / or to another UE via a direct connection. In some scenarios, a UE can establish a wireless connection with network node QQ1010 while still being connected via hub QQ1014 via a wired or wireless connection. In some embodiments, hub QQ1014 may be a dedicated hub, meaning its primary function is to route communication from network node QQ1010b to the UE / from the UE to network node QQ1010b. In other embodiments, hub QQ1014 may be a non-dedicated hub, meaning it can operate to route communication between the UE and network node QQ1010b, but additionally can operate as a device for the origin and / or destination of communication on certain data channels.

[0243] Figure 11 Based on the block diagram of the QQ100 host described in this article, the QQ100 host can be... Figure 10 The embodiment of host QQ1016. As used herein, host QQ1100 can be or include various combinations of hardware and / or software, including processing resources in a standalone server, blade server, cloud-implemented server, distributed server, virtual machine, container, or server cluster. Host QQ1100 can provide one or more services to one or more UEs.

[0244] The host QQ1100 includes processing circuitry QQ1102, which is operatively coupled via bus QQ1104 to input / output interface QQ1106, network interface QQ1108, power supply QQ1110, and memory QQ1112.

[0245] The memory QQ1112 may include one or more computer programs, including one or more host applications QQ1114 and data QQ1116. Data QQ1116 may include user data, such as data generated by the UE for the host QQ1100 or data generated by the host QQ1100 for the UE. Embodiments of the host QQ1100 may utilize only a subset or all of the illustrated components. The host application QQ1114 may be implemented in a container-based architecture and may provide support for edge applications, video codecs (e.g., Universal Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9), and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, and G.711), including code translation for multiple different categories, types, or implementations of UEs (e.g., mobile phones, desktop computers, wearable display systems, head-up display systems). The host application QQ1114 may also provide user authentication and license checks and may periodically report health status, routing, and content availability to a central node (such as a device in the core network or at the edge). Therefore, the host QQ1100 can select and / or indicate different hosts for the UE to use for overhead services. The host application QQ1114 can support various protocols, such as HTTP Real-time Streaming (HLS), Real-time Messaging Protocol (RTMP), Real-time Streaming Protocol (RTSP), and HTTP-based Dynamic Adaptive Streaming (MPEG-DASH).

[0246] Figure 12 illustrates a communication diagram of host QQ1202 communicating with UE QQ1206 via network node QQ1204 through a partial wireless connection according to some embodiments. The UEs (such as...) discussed in the preceding paragraphs according to various embodiments will now be described with reference to Figure 12. Figure 10 UE QQ1012a), network nodes (such as Figure 10 Network node QQ1010a) and host (such as Figure 10 The host QQ1016 and / or Figure 11 Example implementation of the host QQ1100.

[0247] Similar to host QQ1100, embodiments of host QQ1202 include hardware such as a communication interface, processing circuitry, and memory. Host QQ1202 also includes software stored in or accessible by host QQ1202 and executable by the processing circuitry. This software includes a host application operable to provide services to remote users, such as UE QQ1206 connected via an over-the-top (OTT) connection QQ1250 extending between UE QQ1206 and host QQ1202. When providing services to remote users, the host application can provide user data transmitted using the OTT connection QQ1250.

[0248] Network node QQ1204 includes hardware enabling it to communicate with host QQ1202 and UE QQ1206. Connection to QQ1260 can be direct or via a core network (e.g., Figure 10 The core network (QQ1006) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network could be a backbone network or the Internet.

[0249] UE QQ1206 includes hardware and software, the software being stored in or accessible by UE QQ1206 and executable by the UE's processing circuitry. The software includes client applications, such as web browsers or carrier-specific "apps," operable to provide services to human or non-human users via UE QQ1206 with the support of host QQ1202. In host QQ1202, the executing host application can communicate with the executing client application via OTT connection QQ1250, which terminates at both UE QQ1206 and host QQ1202. When providing services to users, the UE's client application can receive request data from the host application at the host and, in response, provide user data. OTT connection QQ1250 can transmit both request data and user data. The UE's client application can interact with users to generate user data provided to the host application via OTT connection QQ1250.

[0250] The OTT connection QQ1250 can be extended via connection QQ1260 between host QQ1202 and network node QQ1204, and via wireless connection QQ1270 between network node QQ1204 and UE QQ1206, to provide connectivity between host QQ1202 and UE QQ1206. Connection QQ1260 and wireless connection QQ1270, which provide OTT connection QQ1250, are abstractly drawn to illustrate communication between host QQ1202 and UE QQ1206 via network node QQ1204, without explicitly referencing any intermediate devices and the precise routing of messages via those devices.

[0251] As an example of sending data via OTT connection QQ1250, in step QQ1208, host QQ1202 provides user data, which can be performed by executing a host application. In some embodiments, the user data is associated with a specific human user interacting with UE QQ1206. In other embodiments, the user data is associated with UE QQ1206, which shares data with host QQ1202 without explicit human interaction. In step QQ1210, host QQ1202 initiates a transmission carrying user data to UE QQ1206. Host QQ1202 may initiate the transmission in response to a request sent by UE QQ1206. This request may be caused by human interaction with UE QQ1206 or by the operation of a client application executed on UE QQ1206. Based on the teachings of the embodiments described throughout this disclosure, the transmission may be carried out via network node QQ1204. Therefore, in step QQ1212, in accordance with the teachings of the embodiments described throughout this disclosure, network node QQ1204 sends user data carried in a transmission initiated by host QQ1202 to UE QQ1206. In step QQ1214, UE QQ1206 receives the user data carried in the transmission, which may be performed by a client application executing on UE QQ1206, associated with a host application executed by host QQ1202.

[0252] In some examples, UE QQ1206 executes a client application that provides user data to host QQ1202. The user data can be provided as a reaction or response to data received from host QQ1202. Therefore, in step QQ1216, UE QQ1206 can provide user data, which can be done by executing the client application. When providing user data, the client application may also consider user input received from a user via the input / output interface of UE QQ1206. Regardless of the specific method of providing user data, in step QQ1218, UE QQ1206 initiates a transmission of user data to host QQ1202 via network node QQ1204. In step QQ1220, in accordance with the teachings of the embodiments described throughout this disclosure, network node QQ1204 receives user data from UE QQ1206 and initiates a transmission of the received user data to host QQ1202. In step QQ1222, host QQ1202 receives the user data carried in the transmission initiated by UE QQ1206.

[0253] One or more improvements in various embodiments enhance the performance of OTT services provided to UE QQ1206 by forming the final segmented OTT connection QQ1250 using the wireless connection QQ1270. More precisely, the teachings of these embodiments in this document can optimize current solutions. Some embodiments in this document can be considered in two development scenarios. In some embodiments of this document, a method for distributing application function keys is proposed in AKMA roaming scenarios, whether the VPLMN supports or does not support AKMA services. In some embodiments of this document, the application function key is bound to the SN ID, which resists key leakage attacks. In some embodiments of this document, when the UE moves to another network, the key KAF used in the VPLMN can be deleted from both the UE and the VPLMN and cannot be reused in the HPLMN, which resists key leakage attacks.

[0254] In the example scenario, factory status information can be collected and analyzed by the host QQ1202. As another example, the host QQ1202 can process audio and video data that may have been retrieved from the UE for map creation. As another example, the host QQ1202 can collect and analyze real-time data to help control vehicle congestion (e.g., control traffic lights). As another example, the host QQ1202 can store surveillance video uploaded by the UE. As another example, the host QQ1202 can store or control access to media content such as video, audio, VR, or AR, which can be broadcast, multicast, or unicast to the UE. As other examples, the host QQ1202 can be used for energy pricing, remote control of non-time-critical power loads to balance generation demand, location services, demonstration services (such as compiling charts based on data collected from remote devices), or any other function that collects, retrieves, stores, analyzes, and / or transmits data.

[0255] In some examples, the measurement process may be provided for the purpose of monitoring data rates, latency, and other factors improved in one or more embodiments. Optional network functions may also exist for reconfiguring the OTT connection QQ1250 between host QQ1202 and UE QQ1206 in response to changes in measurement results. The measurement process and / or the network functions for reconfiguring the OTT connection can be implemented in the software and hardware of host QQ1202 and / or UE QQ 1206. In some embodiments, sensors (not shown) may be deployed in or associated with other communication devices through which the OTT connection QQ1250 passes; the sensors may participate in the measurement process by supplying values ​​of the monitored quantities illustrated above or by supplying values ​​of other physical quantities from which the software can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection QQ1250 may include message formatting, retransmission settings, preferred routing, etc.; reconfiguration does not require direct changes to the operation of network node QQ1204. Such processes and functions are known and practiced in the art. In some embodiments, the measurement results may involve proprietary UE signaling that facilitates measurements of throughput, propagation time, latency, etc., by the host QQ1202. Measurements can be achieved because the software enables the use of an OTT connection with QQ1250 to send messages, particularly empty or “pseudo” messages, while simultaneously monitoring propagation time, errors, etc.

[0256] Example 1. A host configured to operate in a communication system to provide over-the-top (OTT) services, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate the transmission of user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform wireless device-related operations as described above to send user data from the host to the UE.

[0257] Example 2. A host according to the foregoing embodiments, wherein the host's processing circuitry is configured to execute a host application that provides user data; and the UE includes processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.

[0258] Example 3. A method implemented in a host configured to operate in a communication system, the communication system further comprising a network node and a user equipment (UE), the method comprising: providing user data to the UE; and initiating a transmission carrying the user data to the UE via a cellular network including the network node, wherein the network node performs the operations described above in relation to a wireless device to send the user data from the host to the UE.

[0259] Example 4. The method according to the foregoing embodiments further includes: at the network node, transmitting user data provided by the host to the UE.

[0260] Example 5. The method according to any one of the preceding two examples, wherein user data is provided at the host by executing a host application that interacts with a client application executed on the UE, the client application being associated with the host application.

[0261] Example 6. A communication system configured to provide over-the-top service, the communication system comprising: a host including: processing circuitry configured to provide user data to a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate the transmission of user data to a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform the operations described above in relation to a wireless device to send user data from the host to the UE.

[0262] Example 7. The communication system according to the foregoing embodiments further includes: a network node; and / or a user equipment.

[0263] Example 8. A communication system according to the foregoing two examples, wherein the host's processing circuitry is configured to execute a host application to provide user data; and the host application is configured to interact with a client application executed on the UE, the client application being associated with the host application.

[0264] Example 9. A host configured to operate in a communication system to provide over-the-top (OTT) services, the host comprising: processing circuitry configured to initiate the reception of user data; and a network interface configured to receive user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform wireless device-related operations as described above to receive user data for the host from a UE.

[0265] Example 10. A host according to the two embodiments described above, wherein the host's processing circuitry is configured to execute a host application to provide user data; and the host application is configured to interact with a client application executed on the UE, the client application being associated with the host application.

[0266] Example 11. A host according to any one of the foregoing two examples, wherein initiating the reception of user data includes requesting user data.

[0267] Example 12. A method implemented by a host configured to operate in a communication system, the communication system further comprising a network node and a user equipment (UE), the method comprising: at the host, initiating the reception of user data from the UE, the user data originating from a transmission already received from the UE by the network node, wherein the network node performs the operations described above in relation to a wireless device to receive user data from the UE for the host.

[0268] Example 13. The method according to the foregoing embodiments further includes: at the network node, sending the received user data to the host.

[0269] Example 14. A host configured to operate in a communication system to provide over-the-top (OTT) services, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate the transmission of user data to a cellular network for transmission to a user equipment (UE), wherein the UE includes a communication interface and processing circuitry configured to perform wireless device-related operations as described above to receive user data from the host.

[0270] Example 15. The host according to the foregoing embodiments, wherein the cellular network further includes a network node configured to communicate with the UE to send user data from the host to the UE.

[0271] Example 16. A host according to the foregoing two examples, wherein the host's processing circuitry is configured to execute a host application to provide user data; and the host application is configured to interact with a client application executed on the UE, the client application being associated with the host application.

[0272] Example 17. A method implemented by a host operating in a communication system, the communication system further comprising a network node and a user equipment (UE), the method comprising: providing user data to the UE; and initiating a transmission carrying the user data to the UE via a cellular network including the network node, wherein the UE performs the operations described above in relation to a wireless device to receive the user data from the host.

[0273] Example 18. The method according to the foregoing embodiments further includes: at the host, executing a host application associated with a client application executed on the UE to receive user data from the UE.

[0274] Example 19. The method according to the foregoing embodiments further includes: at the host, sending input data to a client application executed on the UE, the input data being provided by executing the host application, wherein user data is provided by the client application in response to input data from the host application.

[0275] Example 20. A host configured to operate in a communication system to provide over-the-top (OTT) services, the host comprising: processing circuitry configured to utilize user data; and a network interface configured to initiate the transmission of user data to a cellular network for transmission to a user equipment (UE), wherein the UE includes a communication interface and processing circuitry, the UE's communication interface and processing circuitry being configured to perform the operations described above in relation to a wireless device to send user data to the host.

[0276] Example 21. The host according to the foregoing embodiments, wherein the cellular network further includes a network node configured to communicate with the UE to send user data from the UE to the host.

[0277] Example 22. A host according to the two embodiments described above, wherein the host's processing circuitry is configured to execute a host application to provide user data; and the host application is configured to interact with a client application executed on the UE, the client application being associated with the host application.

[0278] Example 23. A method implemented by a host configured to operate in a communication system, the communication system further comprising a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted by the UE to the host via the network node, wherein the UE performs the operations described above in relation to a wireless device to transmit the user data to the host.

[0279] Example 24. The method according to the foregoing embodiments further includes: at the host, executing a host application associated with a client application executed on the UE to receive user data from the UE.

[0280] Example 25. The method according to the foregoing embodiments further includes: at the host, sending input data to a client application executed on the UE, the input data being provided by executing the host application, wherein user data is provided by the client application in response to input data from the host application.

[0281] Additionally, this disclosure may also provide a carrier containing the computer program mentioned above, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium. The computer-readable storage medium may be, for example, an optical disc or an electronic storage device, such as RAM (random access memory), ROM (read-only memory), flash memory, magnetic tape, CD-ROM, DVD, Blu-ray disc, etc.

[0282] The techniques described herein can be implemented in various ways such that the means for implementing one or more functions of the corresponding apparatus described with the embodiments includes not only prior art means, but also means for implementing one or more functions of the corresponding apparatus described with the embodiments, and it can include separate means for each individual function or means that can be configured to perform two or more functions. For example, these techniques can be implemented in hardware (one or more means), firmware (one or more means), software (one or more modules), or a combination thereof. For firmware or software, implementation can be achieved by modules (e.g., processes, functions, etc.) that perform the functions described herein.

[0283] Exemplary embodiments described herein have been described above with reference to block diagrams and flowcharts of methods and apparatus. It should be understood that each block illustrated in the block diagrams and flowcharts, as well as combinations of blocks illustrated in the block diagrams and flowcharts, can be implemented, respectively, by various means including computer program instructions. These computer program instructions can be loaded onto a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that the instructions, which execute on the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more flowchart blocks.

[0284] Furthermore, although the operations are depicted in a specific order, this should not be construed as requiring such operations to be performed in the specific order shown or sequentially, or to perform all the illustrated operations to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the foregoing discussion, these details should not be construed as limiting the scope of the subject matter described herein, but rather as descriptions of features that may be specific to particular embodiments. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0285] While this specification contains numerous specific implementation details, these details should not be construed as limiting the scope of any implementation or potentially claimed content, but rather as descriptions of features specific to particular embodiments of a particular implementation. Certain features described in the context of individual embodiments in this specification may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. Moreover, although features may be described above as acting in certain combinations and even so claimed, in some cases, one or more features of a claimed combination may be removed from the combination, and the claimed combination may involve sub-combinations or variations thereof.

[0286] As will be apparent to those skilled in the art, the inventive concept can be implemented in various ways as technology advances. The embodiments described above are given for illustrative purposes and not for limiting the scope of this disclosure, and it should be understood that modifications and variations can be made without departing from the spirit and scope of this disclosure, as will be readily apparent to those skilled in the art. Such modifications and variations are considered to be within the scope of this disclosure and the appended claims. The scope of protection of this disclosure is defined by the appended claims.

Claims

1. A method (200) performed by a first network node in a communication network, comprising: Receive (202) a first request from the second network node, wherein the first request includes a user equipment identifier (UE ID) indicating a user equipment UE; Based on the received UE ID, determine the (204) UE domain information; and Send a first response (206) to the second network node, wherein the first response includes the determined UE domain information; wherein the UE domain information includes the core network type and the subscription domain.

2. The method according to claim 1, wherein, The core network type includes at least one of the following: Evolution Group Core EPC The fifth-generation core network 5GC, and Dual EPC and 5GC.

3. The method according to claim 1, wherein, The subscription domain includes at least one of the following: Fourth-generation mobile communication technology subscription, namely 4G subscription, and Subscription to fifth-generation mobile communication technology, also known as 5G subscription.

4. The method according to any one of claims 1 to 3, wherein, Based on the received UE ID, the UE domain information is determined to include: Send a second request to the third network node to discover whether a fourth network node service instance exists for the UE ID; and A second response is received from the third network node, wherein the second response indicates whether a fourth network node service instance exists for the UE ID.

5. The method according to claim 4, further comprising: when the second response indicates that a fourth network node service instance for the UE ID does not exist; The subscription domain is determined to be 4G subscription, and the core network type is determined to be EPC.

6. The method of claim 4, wherein when the second response indicates the existence of a fourth network node service instance for the UE ID, the method further comprises: Send a third request to the fourth network node to subscribe to the core network type change based on the UE ID.

7. The method according to claim 6, further comprising: A third response is received from the fourth network node, wherein the third response indicates the core network type based on the UE ID; and The core network type included in the UE domain information is determined as the core network type received according to the UEID in the third response, and the subscription domain is determined as 5G subscription.

8. The method according to claim 7, further comprising, when the UE moves between EPC and 5GC: Receive a first message from the fourth network node, wherein the first message includes an updated core network type based on the UE ID; The core network type included in the UE domain information is determined as the updated core network type received in the first message, and the subscription domain is determined as a 5G subscription; and Send a second message to the second network node, wherein the second message includes updated UE domain information, and The updated UE domain information includes the updated core network type and subscription domain.

9. The method according to claim 1, wherein, The first request is a network open function event open subscription request, and The first response is the network open function event open subscription response.

10. The method according to any one of claims 1 to 9, wherein, The first network node includes Network Open Function (NEF), or Service Capability Open Function (SCEF), or a combination of NEF and SCEF; and / or The second network node includes application function AF; and / or The third network node includes a Network Repository Function (NRF); and / or The fourth network node includes a unified data management unit (UDM) or a combination of a UDM and a home subscriber server (HSS).

11. A method (400) performed by a second network node in a communication network, comprising: Send a (402) first request to the first network node, wherein the first request includes a User Equipment Identifier (UE ID) indicating the User Equipment (UE); and Receive (404) a first response from the first network node, wherein the first response includes UE domain information based on the UE ID; wherein the UE domain information includes a core network type and a subscription domain.

12. The method according to claim 11, wherein, The core network type includes at least one of the following: Evolution Group Core EPC The fifth-generation core network 5GC, and Dual EPC and 5GC.

13. The method according to claim 12, wherein, The subscription domain includes at least one of the following: Subscription to fourth-generation mobile communication technology, i.e., 4G subscription; Subscription to fifth-generation mobile communication technology, also known as 5G subscription.

14. The method according to claim 11, wherein, The first request is a network open function event open subscription request, and The first response is the network open function event open subscription response.

15. The method according to any one of claims 11 to 14, further comprising, when the UE moves between EPC and 5GC: Receive a second message from the first network node, wherein the second message includes updated UE domain information based on the UE ID; The updated UE domain information includes the updated core network type and subscription domain.

16. The method according to any one of claims 11 to 14, wherein, The first network node includes Network Open Function (NEF), or Service Capability Open Function (SCEF), or a combination of NEF and SCEF; and / or The second network node includes the application function AF.

17. A first network node (600), comprising: Processor (601); as well as A memory (602), coupled to the processor (601), contains instructions executable by the processor (601), thereby enabling the first network node (600) to: Receive a first request from a second network node, wherein the first request includes a User Equipment Identifier (UE ID) indicating a User Equipment (UE); Based on the received UE ID, determine the UE domain information; and Send a first response to the second network node, wherein the first response includes the determined UE domain information; wherein the UE domain information includes the core network type and the subscription domain.

18. The second network node according to claim 17, wherein, The first network node is also operable to perform the method according to any one of claims 2 to 10.

19. A second network node (700), comprising: Processor (701); as well as A memory (702), coupled to the processor (701), contains instructions executable by the processor (701), thereby enabling the second network node (700) to: Send a first request to a first network node, wherein the first request includes a User Equipment Identifier (UE ID) indicating a User Equipment (UE); and A first response is received from the first network node, wherein the first response includes UE domain information based on the UE ID; wherein the UE domain information includes a core network type and a subscription domain.

20. The second network node according to claim 19, wherein, The second network node may also be operable to perform the method according to any one of claims 12 to 16.

21. A computer-readable storage medium storing instructions, which, when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 1 to 16.

Images