Data Acquisition of User Equipment in the 5th Generation Core Network

Abstract

A mechanism for UE data acquisition in 5GC is provided. A method is performed by a first NF node. The method includes receiving a request for UE data from a second NF node. The method includes acquiring UE data including an AAA server FQDN. The AAA server FQDN may be acquired from a UDR node. The method includes providing the UE data including the AAA server FQDN to the second NF node.

Description

[Technical field]

[0001] The embodiments presented herein relate to a method, a network function node, a computer program, and a computer program product for data acquisition of a user equipment in a fifth generation core network. [Background technology]

[0002] Generally speaking, the fifth generation (5G) system (5GS) is a telecommunication system that uses the 5G New Radio (NR) air interface or the Evolved Universal Terrestrial Radio Access (E-UTRA) air interface connected to the 5G Core Network (5GC). The 5GC includes functional entities called Network Functions (NFs). The functionality of the system is achieved by a collection of NFs that provide services to other NFs that are authorized to access their services. Each NF provides different functionality, which allows different services to be offered.

[0003] FIG. 1 is a schematic diagram showing a communication network 10. The communications network 10 may be considered a public land mobile network (PLMN) and represents the 5GS reference architecture and includes the following entities: an authentication server function (AUSF) node 50, an access and mobility management function (AMF) node 55, a data network (DN) 80, e.g. operator services, internet access or third party services, a network exposure function (NEF) node 20, a network repository function (NRF) node 25, a network slice selection function (NSSF) node 15, a policy control function (PCF) node 30, a session management function (SMF) node 200, a unified data manager (UDM) node 100, a unified data repository (UDR) node 45, a user plane function (UPF) node 75, an application function (AF) node 35, a user equipment (UE) 85, also referred to as a client node, a (radio) access network ((R)AN) 70, a network data analysis function (NWDAF) node 60, a binding support function (BSF) node 40 and a charging function (CHF) node 65. Service-based interfaces are represented in the format Nxyz (eg, Nnssf, Nnef, etc.), and point-to-point interfaces are represented in the format Nx (eg, N1, N2, etc.).

[0004] Two non-limiting and illustrative examples of how an NF (such as an SMF node) interacts with a UDM to obtain information about a UE will now be disclosed.

[0005] A first example is provided in the sequence diagram of Figure 2. According to this example, an NF (e.g., SMF) makes a request to the UDM for Session Management Subscription Data Retrieval. The NF sends a UDM GET request (SUPI, selected network slice, and / or DNN) to the UDM. The UDM will return the UE's session management subscription data (an array of SessionManagementSubscriptionData objects, one array element per S-NSSAI). SessionManagementSubscriptionData contains SessionManagementSubscriptionData\DnnConfiguration\dnAaaAddress. One definition of DnnConfiguration is given in Table 6.1.6.2.9-1 of 3GPP TS 29.503 version 17.2.0, titled "5G System; Unified Data Management Services; Stage 3".

[0006] S11: The AMF receives a PDU Session Establishment Request from the UE or the (R)AN.

[0007] S12: AMF sends an Nsmf_PDUSession_CreateSMContext request to SMF.

[0008] S13: SMF sends Nsmf_PDUSession_CreateSMContext response to AMF.

[0009] S14: The SMF sends a GET request (SUPI, sm-data) to the UDM to request acquisition of session management subscription data.

[0010] S15: The UDM sends a GET request (SUPI, sm-data) to the UDR to request acquisition of session management subscription data.

[0011] S16: UDR sends a 100 OK message with session management subscription data (DnnConfiguration: AAA server IP address of AAA server-1) to UDM.

[0012] S17: UDM sends a 100 OK message with session management subscription data (DnnConfiguration: AAA server IP address of AAA server-1) to SMF.

[0013] S18: SMF uses the received AAA server IP address to send a Radius Authentication Request to AAA server-1. If any IP address is invalid or AAA server-1 is experiencing operational failure, AAA server-1 will not send any response for that.

[0014] S19: The SMF rejects the PDU session establishment by sending a Namf_Communication_N1N2MessageTransfer with (PDU session establishment rejected).

[0015] A second example is provided in the sequence diagram of Figure 3. According to this example, the NF (e.g., NEF) requests the UDM to provide information available for the UE in 5GS. The CREATE / UPDATE request to the UDM includes 5GVnGroupConfiguration\5gVnGroupData\dnAaaAddress. One definition of 5GVnGroupData is given in Table 6.5.6.2.7-1 of 3GPP TS 29.503 mentioned above.

[0016] S21: The NF (eg, SMF) sends a Nudm_SDM_Subscribe request to the UDM.

[0017] S22: UDM sends a 201 Created message.

[0018] S23: The AF sends a Nnef_ParameterProvision_Create / Update request with the group ID (GroupId) and the IP address of the AAA server-1 (5GVnGroup\AAA Server IP Address) to the NEF.

[0019] S24: The NEF sends a Nnef_ParameterProvision_Create / Update request to the UDM with the group ID and the IP address of the AAA server-1 (5GVnGroup\AAA Server IP Address).

[0020] S25: The UDM executes a Nudr_DM_Query procedure with the UDR for verification.

[0021] S26: The UDM executes a Nudr_DM_Update procedure with the UDR, along with the group ID (GroupId) and the IP address of the AAA server-1 (5GVnGroup\AAA Server IP Address).

[0022] S27: The UDM sends a Nnef_ParameterProvision_Create / Update response to the NEF.

[0023] S28: The NEF transmits a Nnef_ParameterProvision_Create / Update response to the AF.

[0024] S29: UDM sends a Nudm_SDM_Notification notification to SMF with the group ID and the IP address of AAA Server-1 (5GVnGroup\AAA Server IP Address) since SMF subscribed to the change in step S21.

[0025] S30: SMF sends a 204 message to UDM.

[0026] S31: The SMF sends a Radius authentication request to AAA server-1 using the received IP address to be contacted. If any IP address is invalid or AAA server-1 is experiencing operational failure, AAA server-1 will not send any response for that.

[0027] As can be seen in the illustrative examples of both Figures 2 and 3, there could be some scenarios where the information provided from the UDM to the SMF (or more generally from 1NF to 2NF) does not allow for the performance of secondary authentication and authorization of the UE.

[0028] Thus, there is a need for an improved procedure for a second NF to obtain UE information from a first NF. Summary of the Invention

[0029] The objective of the embodiments herein is to allow one NF (such as an SMF) to obtain UE information from another NF (such as an UDM) without causing the AAA server to become unavailable as in the above scenario, or at least in a manner that mitigates or reduces the negative impact of this.

[0030] According to a first aspect, a method for UE data acquisition in 5GC is presented. The method is executed by a first NF node. The method includes receiving a request for data of a UE (85) from a second NF node (200) (S106), acquiring the data of the UE (85) including an AAA server FQDN (S108), and providing the data of the UE (85) including the AAA server FQDN to the second NF node (200) (S110).

[0031] In some embodiments, the AAA server FQDN is obtained from the UDR node (45).

[0032] In some embodiments, the method further includes receiving a first update request from the NEF node (20) including the AAA server FQDN (S102), and providing a second update request to the UDR node (45) together with the AAA server FQDN (S104).

[0033] In some embodiments, the method is performed as part of a PDU session establishment procedure for the UE (85).

[0034] In some embodiments, the request for data is a request to obtain session management subscription data for the UE (85).

[0035] In some embodiments, the request for data is a request for information available in the 5GS (10) about the UE (85).

[0036] In some embodiments, the data for the UE (85) is provided in either a DnnConfiguration object or a 5gVnGroupData object.

[0037] In some embodiments, the AAA server FQDN is provided in the dnAaaAddress attribute of either the DnnConfiguration object or the 5gVnGroupData object.

[0038] In some embodiments, the first NF node (200) is a UDM node and the second NF node (200) is a SMF node.

[0039] According to a second aspect, a first NF node for data acquisition of a UE in 5GC is presented. The first NF node comprises a processing circuit. The processing circuit is configured to cause the first NF node to receive a request for data of the UE from a second NF node. The processing circuit is configured to cause the first NF node to acquire the data of the UE including an AAA server FQDN. The processing circuit is configured to cause the first NF node to provide the data of the UE including the AAA server FQDN to a second NF node.

[0040] According to a third aspect, a first NF node for data acquisition of a UE in 5GC is presented. The first NF node comprises a receiving module configured to receive a request for data of the UE from a second NF node. The first NF node comprises an acquiring module configured to acquire the data of the UE including an AAA server FQDN. The first NF node comprises a providing module configured to provide the data of the UE including the AAA server FQDN to a second NF node.

[0041] According to a fourth aspect, there is provided a computer program for data acquisition of a UE in a 5GC, the computer program including computer program code which, when executed on processing circuitry of a first NF node, causes the first NF node to perform a method according to the first aspect.

[0042] According to a fifth aspect, a method for UE data acquisition in 5GC is presented, the method being performed by a second NF node, the method including providing (S202) to a first NF node (100) a request for data of the UE (85), and receiving (S204) the data of the UE (85) from the first NF node (100), the data including an AAA server FQDN.

[0043] In some embodiments, the method further includes authenticating the data of the UE with an AAA server, the AAA server being determined based on the AAA server FQDN.

[0044] In some embodiments, determining the AAA server includes obtaining a set of AAA server IP addresses from a DNS server by providing the AAA server FQDN to the DNS server (S206).

[0045] In some embodiments, the method further includes storing (S208) a mapping between the AAA server FQDN and each IP address in the set of AAA server IP addresses.

[0046] In some embodiments, the method further includes providing (S210) an authentication request for the UE (85) to the AAA server at one of the IP addresses in the set of AAA server IP addresses.

[0047] In some embodiments, the authentication request is for a secondary authentication and authorization for the UE (85).

[0048] In some embodiments, if the AAA server is not reachable at the one of the IP addresses in the set of AAA server IP addresses, the request is provided to the other one of the IP addresses in the set of AAA server IP addresses.

[0049] In some embodiments, providing the request for data is triggered by a previous failed attempt to contact the AAA server.

[0050] In some embodiments, the method is performed as part of a PDU session establishment procedure for the UE (85).

[0051] In some embodiments, the request for data is a request to obtain session management subscription data for the UE (85).

[0052] In some embodiments, the request for data is a request for information available in the 5GS (10) about the UE (85).

[0053] In some embodiments, the data for the UE (85) is received in either a DnnConfiguration object or a 5gVnGroupData object.

[0054] In some embodiments, the AAA server FQDN is received in the dnAaaAddress attribute of either a DnnConfiguration object or a 5gVnGroupData object.

[0055] In some embodiments, the first NF node (200) is a UDM node and the second NF node (200) is a SMF node.

[0056] According to a sixth aspect, a second NF node for data acquisition for a UE in 5GC is presented. The second NF node comprises a processing circuit. The processing circuit is configured to cause the second NF node to provide a request for the data of the UE to a first NF node. The processing circuit is configured to cause the second NF node to receive the data of the UE from the first NF node, the data including an AAA server FQDN. In some embodiments, the processing circuit is configured to cause the second NF node to obtain a set of AAA server IP addresses from a DNS server by providing the AAA server FQDN to the DNS server.

[0057] According to a seventh aspect, a second NF node for data acquisition for a UE in 5GC is presented. The second NF node comprises a providing module configured to provide a request for data for the UE to a first NF node. The second NF node comprises a receiving module configured to receive the data for the UE from the first NF node, the data including an AAA server FQDN. In some embodiments, the second NF node comprises an obtaining module configured to obtain a set of AAA server IP addresses from a DNS server by providing the AAA server FQDN to the DNS server.

[0058] According to an eighth aspect, there is provided a computer program for data acquisition of a UE in a 5GC, the computer program including computer program code which, when executed on a processing circuit of a second NF node, causes the second NF node to perform a method according to the fifth aspect.

[0059] According to a ninth aspect, there is provided a computer program product including a computer program according to at least one of the fourth and eighth aspects and a computer-readable storage medium having the computer program stored thereon. The computer-readable storage medium may be a non-transitory computer-readable storage medium.

[0060] Advantageously, these aspects may be used in a procedure for a second NF (such as an SMF) to obtain information about a UE from a first NF (such as a UDM) without causing the AAA server to become unavailable as in the above scenario, or at least in a manner that mitigates or reduces the adverse effects thereof.

[0061] Advantageously, these aspects provide node redundancy: if an AAA server fails (or the corresponding IP address is unavailable), requests for an action to be performed by that AAA server can be directed, according to the FQDN, to other AAA servers that have not experienced a failure.

[0062] Advantageously, these aspects provide load balancing among AAA servers: if an AAA server is overloaded, requests for the performance of certain actions by that AAA server can be directed to other AAA servers that are not overloaded, according to the FQDN.

[0063] Other objects, features and advantages of the included embodiments will become apparent from the following detailed disclosure, from the appended dependent claims, as well as from the drawings.

[0064] In general, all terms used in the claims should be interpreted according to their ordinary meaning in the art, unless expressly defined otherwise herein. All references to an element, apparatus, component, means, module, step, etc., should be openly interpreted as a reference to at least one instance of that element, apparatus, component, means, module, step, etc., unless expressly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless expressly stated otherwise. [Brief description of the drawings]

[0065] The inventive concept will now be described by way of example only, with reference to the accompanying drawings in which:

[0066] [Figure 1] FIG. 1 is a schematic diagram illustrating a communication network according to an embodiment. [Diagram 2] FIG. 2 is a sequence diagram of a method according to an example. [Diagram 3] FIG. 2 is a sequence diagram of a method according to an example. [Figure 4] 1 is a flowchart of a method according to an embodiment. [Diagram 5] 1 is a flowchart of a method according to an embodiment. [Figure 6A] FIG. 2 is a sequence diagram of a method according to an embodiment. [Figure 6B] FIG. 2 is a sequence diagram of a method according to an embodiment. [Figure 7] FIG. 2 is a sequence diagram of a method according to an embodiment. [Figure 8] FIG. 1 is a schematic diagram illustrating functional units of a first NF node according to one embodiment. [Figure 9] FIG. 1 is a schematic diagram showing a group of functional modules of a first NF node according to an embodiment. [Figure 10] FIG. 2 is a schematic diagram illustrating functional units of a second NF node according to one embodiment. [Figure 11] FIG. 1 is a schematic diagram showing a group of functional modules of a second NF node according to one embodiment. [Figure 12] 1 illustrates an example of a computer program product including computer readable means according to one embodiment. [Figure 13] FIG. 1 is a schematic diagram illustrating a telecommunications network connected through an intermediate network to a host computer in accordance with some embodiments. [Figure 14] FIG. 1 is a schematic diagram illustrating a host computer communicating with an end device via a base station over a partially wireless connection in accordance with some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0067] The inventive concept will now be more fully described with reference to the accompanying drawings, in which certain embodiments of the inventive concept are depicted. The inventive concept may, however, be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein, but rather, the embodiments are provided by way of example so that this disclosure will be thorough and complete, and will fully convey the scope of the inventive concept to those skilled in the art. Throughout the description, like numbers refer to like elements. Any steps or features indicated with dashed lines should be considered optional.

[0068] As noted above, there is a need for an improved procedure for an NF to obtain information about a UE from another NF. In this regard, dnAaaAddress is defined as a single IP address. In the example of FIG. 2, this is illustrated by the fact that dnAaaAddress in DnnConfiguration is defined as one single IP address. In the example of FIG. 3, this is illustrated by the fact that dnAaaAddress in 5GvnGroupData is defined as one single IP address. Therefore, if the AAA server is not reachable or cannot operate properly due to some failure, secondary authentication and authorization for the UE will fail. In a practical network deployment, multiple AAA servers may be configured to provide load balancing and redundancy. Therefore, if dnAaaAddress is supplemented or combined with FQDN information, DNS resolution can be performed to obtain multiple AAA server IP addresses (i.e., IP addresses for multiple AAA servers), thereby supporting load balancing and providing AAA server redundancy.

[0069] The embodiments disclosed herein thus relate to an arrangement for data acquisition of a UE 85 in a 5GC. To obtain such an arrangement, a computer program product is provided that includes a first NF node 100, a method to be executed by the first NF node 100, and code in the form of a computer program that, when executed on, for example, a processing circuit of the first NF node 100, causes the first NF node 100 to perform the method. To obtain such an arrangement, a computer program product is provided that includes a second NF node 200, a method to be executed by the second NF node 200, and code in the form of a computer program that, when executed on, for example, a processing circuit of the second NF node 200, causes the second NF node 200 to perform the method.

[0070] Referring now to FIG. 4, there is shown a method performed by a first NF node 100 for data acquisition for UE 85 in 5GC according to one embodiment.

[0071] As disclosed further below, the second NF node 200 provides a request for the data of the UE 85 to the first NF node 100. This request is received by the UDM 100. In particular, the first NF node 100 is configured to perform step S106:

[0072] S106: The first NF node 100 receives a request from the second NF node 200 for data of the UE 85.

[0073] The above data is obtained from the UDR 45. In particular, the first NF node 100 is configured to perform step S108:

[0074] S108: The first NF node 100 receives the data of the UE 85 including the AAA server FQDN from the UDR node 45.

[0075] The data is then provided to the NF that requested the data. In particular, the first NF node 100 is configured to perform step S110:

[0076] S110: The first NF node 100 provides the data of the UE 85, including the AAA server FQDN, to the second NF node 200.

[0077] Now, embodiments relating to further details of UE85 data acquisition in 5GC performed by the first NF node 100 will be disclosed.

[0078] There may be various types of first NF nodes 100 and second NF nodes 200. In some embodiments, the first NF node 100 is a UDM node and the second NF node 200 is a SMF node.

[0079] UDR Node 45 There may be various ways for the UDR node 45 to have access to the AAA server FQDN. In some aspects, the AAA server FQDN is provided from the first NF node 100 to the UDR node 45. In particular, in some embodiments, the first NF node 100 is configured to perform steps S102 and S104 (optional):

[0080] S102: The first NF node 100 receives a first update request from the NEF node 20. The update request includes the AAA server FQDN.

[0081] S104: The first NF node 100 provides a second update request to the UDR node 45 along with the AAA server FQDN.

[0082] This will be explained in more detail below with reference to FIG.

[0083] There may be various contexts in which the method disclosed herein may be implemented. In some embodiments, the method is implemented as part of a PDU session establishment procedure for a UE 85. This will be explained in more detail below with reference to Figures 6A and 6B.

[0084] There may be various types of requests for data that are obtained by the first NF node 100 from the second NF node 200 in step S106. In some embodiments, the request for data is 85 5. The request for data is a request for Session Management Subscription Data Retrieval for the UE 85. This will be explained in more detail below with reference to Figures 6A and 6B. In another embodiment, the request for data is a request for information available at the 5GS 10 about the UE 85. This will be explained in more detail below with reference to Figure 7.

[0085] There may be various ways in which the first NF node 100 provides the UE 85 data, including the AAA server FQDN, to the second NF node 200 in step S110. In some embodiments, the UE 85 data is provided in either a DnnConfiguration object or a 5gVnGroupData object. The former will be described in more detail below with reference to Figures 6A and 6B, and the latter will be described in more detail below with reference to Figure 7.

[0086] There may be various ways for the first NF node 100 to provide the AAA server FQDN to the second NF node 200 in step S110. In some embodiments, the AAA server FQDN is provided in the dnAaaAddress attribute of either a DnnConfiguration object or a 5gVnGroupData object. The former will be described in more detail below with reference to Figures 6A and 6B, and the latter will be described in more detail below with reference to Figure 7.

[0087] Referring now to FIG. 5, a method performed by a second NF node 200 for data acquisition for UE85 in 5GC according to one embodiment is shown.

[0088] The second NF node 200 is assumed to request data for the UE 85. In particular, the second NF node 200 is configured to perform step S202:

[0089] S202: The second NF node 200 provides a request for data of the UE 85 to the first NF node 100.

[0090] As mentioned above, the first NF node 100 provides the UE 85 with data including the AAA server FQDN. The second NF node 200 is expected to receive this data. In particular, the second NF node 200 is configured to perform step S204:

[0091] S204: The second NF node 200 receives the data of the UE 85 including the AAA server FQDN from the first NF node 100.

[0092] The AAA server IP address is then obtained from the AAA server FQDN. In particular, the second NF node 200 is configured to perform step S206:

[0093] S206: The second NF node 200 obtains a set of AAA server IP addresses from the DNS server by providing the AAA server FQDN to the DNS server.

[0094] Now, embodiments relating to further details of data acquisition of UE85 in 5GC performed by the second NF node 200 will be disclosed.

[0095] As noted above, there may be various types of first NF nodes 100 and second NF nodes 200. In some embodiments, the first NF node 100 is a UDM node and the second NF node 200 is a SMF node.

[0096] Once the set of AAA server IP addresses is obtained from the DNS server in step S206, there may be various actions performed by the second NF node 200.

[0097] In some aspects, the mapping between the AAA server FQDN and the IP address is stored. In particular, in some embodiments, the second NF node 200 is configured to perform step S208 (optional):

[0098] S208: The second NF node 200 stores a mapping between the AAA server FQDN and each IP address in the set of AAA server IP addresses.

[0099] In some aspects, the second NF node 200 provides the authentication request to an AAA server at at least one of the plurality of IP addresses. In particular, in some embodiments, the second NF node 200 is configured to perform step S210 (optional):

[0100] S210: The second NF node 200 provides an authentication request for the UE 85 to an AAA server at one of the IP addresses in the set of AAA server IP addresses.

[0101] In some embodiments, the authentication request is for secondary authentication and authorization for the UE 85.

[0102] The second NF node 200 may repeat step S210 for different IP addresses in the set of AAA server IP addresses until the AAA server responds to the authentication request. Notably, in some embodiments, if the AAA server is not reachable at one of the IP addresses in the set of AAA server IP addresses, the request is provided to another one of the IP addresses in the set of AAA server IP addresses.

[0103] There may be various triggers for the second NF node 200 to provide a request for the UE 85's data to the first NF node 100 in step S202. In some embodiments, providing the request for data is triggered by a previous failed attempt to contact an AAA server. That is, if the second NF node 200 previously provided an authentication request for the UE 85 to an AAA server at a specific IP address and the AAA server was not reachable at that specific IP address, this may act as a trigger for the second NF node 200 to provide a request for the UE 85's data to the first NF node 100 in step S202.

[0104] As mentioned above, there may be various contexts in which the method disclosed herein may be performed. In some embodiments, the method is performed as part of a PDU session establishment procedure for a UE 85. This will be explained in more detail below with reference to Figures 6A and 6B.

[0105] There may be various types of requests for data that are provided by the second NF node 200 to the second NF node 200 in step S202. In some embodiments, the request for data may be 85 5GS 10。 In another embodiment, the request for data is a request for information available at the 5GS 10 about the UE 85. This will be explained in more detail below with reference to Figure 7.

[0106] There may be various ways for the second NF node 200 to receive the UE 85 data, including the AAA server FQDN, from the first NF node 100 in step S204. In some embodiments, the UE 85 data is received in either a DnnConfiguration object or a 5gVnGroupData object. The former will be described in more detail below with reference to Figures 6A and 6B, and the latter will be described in more detail below with reference to Figure 7. Additionally, in some embodiments, the AAA server FQDN is received in a dnAaaAddress attribute of either a DnnConfiguration object or a 5gVnGroupData object. The former will be described in more detail below with reference to Figures 6A and 6B, and the latter will be described in more detail below with reference to Figure 7.

[0107] Referring again to 3GPP TS 29.503, Table 6.1.6.2.9-1 and / or Table 6.5.6.2.7-1 of 3GPP TS 29.503 could be updated to include entries according to Table 1 or Table 2. In this regard, Table 1 provides an example where the data type of the dnAaaAddress attribute is extended to also include FQDN, while Table 2 provides an example where a new attribute, dnAaaFQDN, is added with a data type of FQDN. This is true regardless of whether the UE 85 data is provided in a DnnConfiguration object or a 5gVnGroupData object.

[0108] [Table 1]

[0109] [Table 2]

[0110] In both of these cases, the FQDN may be represented by a simple data type that has a type name of Fqdn and is a string as shown in Table 3. Table 3 may be an extension to Table 6.1.6.3.2-1 of 3GPP TS 29.503.

[0111] [Table 3]

[0112] A first specific embodiment for data acquisition for UE85 in 5GC based on at least some of the above disclosed embodiments will now be disclosed in detail with reference to the sequence diagrams of Figures 6A and 6B. This embodiment relates to a scenario in which the above method is executed as part of a PDU session establishment procedure for a UE85, the first NF node 100 is a UDM and the second NF is an SMF, the request for data is a request for session management subscription data acquisition for the UE85, the data for the UE85 is provided in either a DnnConfiguration object or a 5gVnGroupData object, and the AAA server FQDN is provided in the dnAaaAddress attribute of the DnnConfiguration object.

[0113] S301: The AMF receives a PDU Session Establishment Request from a UE or an (R)AN.

[0114] S302: AMF sends an Nsmf_PDUSession_CreateSMContext request to SMF.

[0115] S303: SMF sends Nsmf_PDUSession_CreateSMContext response to AMF.

[0116] S304: The SMF sends a GET request (SUPI, sm-data) to the UDM to obtain session management subscription data.

[0117] S305: The UDM sends a GET request (SUPI, sm-data) to the UDR to request acquisition of session management subscription data.

[0118] S306: The UDR sends a 100 OK message with the session management subscription data (DnnConfiguration: AAA server FQDN) to the UDM.

[0119] S307: UDM sends a 100 OK message with session management subscription data (DnnConfiguration: AAA server FQDN) to SMF.

[0120] S308: The SMF sends a DNS Query Request with the AAA server FQDN to the DNS server.

[0121] S309: The DNS server sends a DNS Query Response with the AAA server FQDNs that are mapped to the AAA server-1 IP address, the AAA server-2 IP address, ..., the AAA server-N IP address in reply to the SMF.

[0122] S310.SMF stores the above mappings in the DNS cache: AAA server FQDN is mapped to AAA server-1 IP address, AAA server-2 IP address, ..., AAA server-N IP address.

[0123] S311.SMF selects the AAA server-1 IP address and sends a Radius Authentication Request to the AAA server-1.

[0124] S312. Either the IP address is invalid or AAA server-1 is experiencing operational failure and therefore AAA server-1 does not send any response, therefore, SMF resends the Radius authentication request (or sends a second Radius authentication request) to AAA server-2.

[0125] S313. AAA server-2 sends a Radius authentication response to the SMF.

[0126] S314.SMF continues the PDU session establishment procedure.

[0127] If both the AAA server IP address and the AAA server FQDN are sent in S307, the SMF can decide which one has a higher priority to use. If it is decided that the AAA server IP address should be used first, the SMF can use the AAA server IP address first, and if it fails, the SMF can then use the AAA server FQDN.

[0128] A second specific embodiment for data acquisition for UE 85 in 5GC based on at least some of the above disclosed embodiments will now be disclosed in detail with reference to the sequence diagram of Fig. 7. This embodiment relates to a scenario where the request for data is a request for information available for the UE 85 at the 5GS 10, the first NF node 100 is a UDM and the second NF is a SMF, the data for the UE 85 is provided in a 5gVnGroupData object and the AAA server FQDN is provided in the dnAaaAddress attribute of the 5gVnGroupData object.

[0129] S401: An NF (eg, SMF) sends a Nudm_SDM_Subscribe request to a UDM.

[0130] S402: UDM sends a 201 Created message.

[0131] S403: The AF sends a Nnef_ParameterProvision_Create / Update request with the group ID (GroupId) and 5GVnGroup\AAA Server FQDN to the NEF.

[0132] S404: The NEF sends a Nnef_ParameterProvision_Create / Update request to the UDM along with the group ID (GroupId) and the 5GVnGroup\AAA Server FQDN.

[0133] S405: The UDM executes the Nudr_DM_Query procedure with the UDR to verify data.

[0134] S406: The UDM executes a Nudr_DM_Update procedure with the UDR, including the group ID (GroupId) and the 5GVnGroup\AAA Server FQDN.

[0135] S407: The UDM transmits a Nnef_ParameterProvision_Create / Update response to the NEF.

[0136] S408: The NEF transmits a Nnef_ParameterProvision_Create / Update response to the AF.

[0137] S409: UDM sends a Nudm_SDM_Notification notification with the group ID, 5GVnGroup\AAA Server FQDN to SMF since SMF subscribed to the change in step S401.

[0138] S410: SMF sends a 204 message to UDM.

[0139] S411: The procedure of FIG. 7 may continue from step S310 onwards.

[0140] Figure 8 illustrates in schematic form the components of the first NF node 100 according to one embodiment in terms of several functional units. The processing circuitry 110 is implemented using any combination of one or more suitable central processing units (CPUs), multiprocessors, microcontrollers, digital signal processors (DSPs), etc. capable of executing software instructions stored in a computer program product 1110a (such as in Figure 12) in the form of, for example, a storage medium 130. The processing circuitry 110 may further be implemented as at least one application specific integrated circuit (ASIC) or field programmable gate array (FPGA).

[0141] In particular, processing circuitry 110 is configured to cause the first NF node 100 to perform the set of operations or steps disclosed above. For example, storage medium 130 may store the set of operations, and processing circuitry 110 may be configured to read the set of operations from storage medium 130 and cause the first NF node 100 to perform the set of operations. The set of operations may be provided as a set of executable instructions. Thus, processing circuitry 110 is adapted to thereby perform the method as disclosed herein.

[0142] Storage medium 130 may also include persistent storage, which may be any one or combination of, for example, magnetic memory, optical memory, solid-state memory, or remotely mounted memory.

[0143] The first NF node 100 may further comprise a communications interface 120 for communicating with other entities, functions, nodes, and devices, such as those illustrated in the communications network 10. As such, the communications interface 120 may comprise one or more transmitters and receivers, including analog and digital components.

[0144] Processing circuitry 110 controls the overall operation of the first NF node 100, for example, by sending data and control signals to communications interface 120 and storage medium 130, by receiving data and reports from communications interface 120, and by reading data and instructions from storage medium 130. Other components and associated functionality of the first NF node 100 have been omitted so as not to obscure the concepts presented herein.

[0145] FIG. 9 shows a schematic of components of a first NF node 100 according to one embodiment in terms of several functional modules. The first NF node 100 of FIG. 9 comprises several functional modules, such as a receiving module 110c configured to perform step S106, an acquiring module 110d configured to perform step S108, and a providing module 110e configured to perform step S110. The first NF node 100 of FIG. 9 may further comprise a number of optional functional modules, such as a receiving module 110a configured to perform step S102, and any of a providing module 110b configured to perform step S104. Generally speaking, each of the functional modules 110a:110e may be implemented in hardware or software. Preferably, one or more or all of the functional modules 110a:110e may be implemented by a processing circuit 110, possibly in cooperation with a communication interface 120 and / or a storage medium 130. The processing circuitry 110 may thus be configured to retrieve instructions provided by the functional modules 110a:110e from the storage medium 130 and execute those instructions to perform any steps of the first NF node 100 as disclosed herein.

[0146] Figure 10 shows a schematic of components of the second NF node 200 according to one embodiment in terms of several functional units. The processing circuitry 210 is provided using any combination of one or more suitable central processing units (CPUs), multiprocessors, microcontrollers, digital signal processors (DSPs), etc. capable of executing software instructions stored in a computer program product 1110b (as in Figure 12), for example in the form of a storage medium 230. The processing circuitry 210 may further be provided as at least one application specific integrated circuit (ASIC) or field programmable gate array (FPGA).

[0147] In particular, processing circuitry 210 is configured to cause the second NF node 200 to perform the set of operations or steps disclosed above. For example, storage medium 230 may store the set of operations, and processing circuitry 210 may be configured to read the set of operations from storage medium 230 and cause the second NF node 200 to perform the set of operations. The set of operations may be provided as a set of executable instructions. Thus, processing circuitry 210 is adapted to thereby perform the method as disclosed herein.

[0148] Storage medium 230 may also include persistent storage, which may be any one or combination of, for example, magnetic memory, optical memory, solid-state memory, or remotely mounted memory.

[0149] The second NF node 200 may further comprise a communications interface 220 for communicating with other entities, functions, nodes, and devices, such as those illustrated in the communications network 10. As such, the communications interface 220 may comprise one or more transmitters and receivers, including analog and digital components.

[0150] Processing circuitry 210 controls the overall operation of second NF node 200, for example, by sending data and control signals to communications interface 220 and storage medium 230, by receiving data and reports from communications interface 220, and by reading data and instructions from storage medium 230. Other components and associated functionality of second NF node 200 have been omitted so as not to obscure the concepts presented herein.

[0151] FIG. 11 shows a schematic of components of a second NF node 200 according to one embodiment in terms of several functional modules. The second NF node 200 of FIG. 11 comprises several functional modules, such as a providing module 210a configured to perform step S202, a receiving module 210b configured to perform step S204, and an acquiring module 210c configured to perform step S106. The second NF node 200 of FIG. 11 may further comprise a number of optional functional modules, such as a storage module 210d configured to perform step S208, and any of the providing modules 210e configured to perform step S210. Generally speaking, each of the functional modules 210a:210e may be implemented in hardware or software. Preferably, one or more or all of the functional modules 210a:210e may be implemented by a processing circuit 210, possibly in cooperation with a communication interface 220 and / or a storage medium 230. Processing circuitry 210 may thus be configured to retrieve instructions provided by functional modules 210a:210e from storage medium 230 and execute those instructions to perform any steps of 2NF node 200 as disclosed herein.

[0152] The first NF node 100 and / or the second NF node 200 may be provided as a stand-alone device or as part of at least one further device. For example, the first NF node 100 and / or the second NF node 200 may be provided in a node of a core network. Alternatively, the first NF node 100 and / or the second NF node 200 may be distributed among at least two devices or nodes. Thus, a first portion of the instructions executed by the first NF node 100 and / or the second NF node 200 may be executed in a first device and a second portion of the instructions executed by the first NF node 100 and / or the second NF node 200 may be executed in a second device, and the embodiments disclosed herein are not limited to any specific number of devices on which the instructions executed by the first NF node 100 and / or the second NF node 200 may be executed. Thus, the method according to the embodiments disclosed herein is suitable for execution by the first NF node 100 and / or the second NF node 200 located in a cloud computing environment. Thus, although a single processing circuit 110, 210 is shown in Figures 8 and 10, the processing circuit 110, 210 may be distributed across multiple physical devices or nodes. The same applies to the functional modules 110a:110e, 210a:210e in Figures 9 and 11, and the computer programs 1120a, 1120b in Figure 12.

[0153] 12 shows an example of a computer program product 1110a, 1110b including a computer readable means 1130. The computer readable means 1130 may have stored thereon a computer program 1120a that can cause entities and devices, such as the processing circuitry 110 and the communications interface 120 and storage medium 130 operatively coupled thereto, to perform the method according to embodiments described herein. The computer program 1120a and / or the computer program product 1110a may thus provide the means for performing any steps of the first NF node 100 as disclosed herein. The computer readable means 1130 may have stored thereon a computer program 1120b that can cause entities and devices, such as the processing circuitry 210 and the communications interface 220 and storage medium 230 operatively coupled thereto, to perform the method according to embodiments described herein. Computer program 1120b and / or computer program product 1110b may thus provide means for performing any of the steps of 2NF node 200 as disclosed herein.

[0154] In the example of Fig. 12, the computer program products 1110a, 1110b are shown as optical discs, such as compact discs (CDs), digital versatile discs (DVDs) or Blu-ray discs. The computer program products 1110a, 1110b may also be embodied as a memory, such as random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM) or electrically erasable programmable read-only memory (EEPROM), more particularly as a non-volatile storage medium of the device in an external memory, such as a Universal Serial Bus (USB) memory or a flash memory, such as a Compact Flash memory. Thus, although the computer programs 1120a, 1120b are shown here diagrammatically as tracks on the depicted optical disc, the computer programs 1120a, 1120b can be stored in any manner suitable for the computer program products 1110a, 1110b.

[0155] Figure 13 is a schematic diagram illustrating a telecommunication network connected via an intermediate network 420 to a host computer 430 according to some embodiments. According to one embodiment, a communication system includes a telecommunication network 410, such as a 3GPP-type cellular network, which includes an access network 411, such as an (R)AN in Figure 1, and a core network 414, such as a 5GC in Figure 1. The access network 411 includes multiple radio access network nodes 412a, 412b, 412c, such as NBs, eNBs, gNBs (corresponding to the (R)AN 70 in Figure 1), or other types of wireless access points, each of which defines a corresponding coverage area 413a, 413b, 413c. Each radio access network node 412a, 412b, 412c can be connected to the core network 414 over a wired or wireless connection 415. A first UE 491 located in the coverage area 413c is wirelessly connected to or configured to be paged by the corresponding network node 412c. A second UE 492 in the coverage area 413a can wirelessly connect to the corresponding network node 412a. Although multiple UEs 491, 492 are shown in this example, the disclosed embodiments are equally applicable to a situation where there is a single UE in the coverage area or a single terminal device connects to the corresponding network node 412. The UEs 491, 492 correspond to the UEs 85 of FIG. 1.

[0156] The telecommunications network 410 is itself connected to a host computer 430, which may be embodied in standalone server hardware and / or software, cloud-implemented servers, distributed servers, or as processing resources in a server farm. The host computer 430 may be owned or controlled by a service provider, or may be operated by or for the service provider. The connections 421 and 422 between the telecommunications network 410 and the host computer 430 may extend directly from the core network 414 to the host computer 430, or may be connected via an optional intermediate network 420. The intermediate network 420 may be one or a combination of public, private, or hosted networks, and the intermediate network 420 may be a backbone network or the Internet, if any, and in particular the intermediate network 420 may include two or more sub-networks (not shown).

[0157] The communication system of FIG. 13 generally enables connectivity between connected UEs 491, 492 and a host computer 430. The connectivity may be described as an over-the-top (OTT) connection 450. The host computer 430 and connected UEs 491, 492 are configured to communicate data and / or signaling via the OTT connection 450 using the access network 411, the core network 414, any intermediate networks 420 and possible further infrastructure (not shown) as intermediate steps. The OTT connection 450 may be transparent in the sense that participating communication devices en route through the OTT connection 450 are unaware of the routing of uplink and downlink communications. For example, the network node 412 may not be or need not be informed of past routing of incoming downlink communications with data to be forwarded (e.g., handed over) originating from the host computer 430 to the connected UE 491. Similarly, the network node 412 does not need to be aware of the future routing of outgoing uplink communications originating from the UE 491 towards the host computer 430.

[0158] FIG. 14 is a schematic diagram illustrating a host computer communicating with a UE via a radio access network node over a partially wireless connection according to some embodiments. An exemplary implementation according to one embodiment of the UE, radio access network node and host computer discussed in the previous paragraph will now be described with reference to FIG. 14. In the communication system 500, the host computer 510 comprises hardware 515 including a communication interface 516 configured to set up and maintain a wired or wireless connection with interfaces of different communication devices of the communication system 500. The host computer 510 further comprises a processing circuit 518, which may have storage and / or processing capabilities. In particular, the processing circuit 518 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The host computer 510 further comprises software 511 stored in or accessible by the host computer 510, the software 511 being executable by the processing circuit 518. The software 511 includes a host application 512. The host application 512 may be operable to provide services to a remote user, such as a UE 530, connecting via an OTT connection 550 that terminates at the host computer 510. The UE 530 corresponds to the UE 85 of Figure 1. During the provision of services to the remote user, the host application 512 may provide user data that is transmitted using the OTT connection 550.

[0159] The communication system 500 further includes a radio access network node 520 provided in the telecommunication system, the radio access network node 520 comprising hardware 525 enabling communication with the host computer 510 and the UE 530. The radio access network node 520 corresponds to the (R)AN 70 of FIG. 1. The hardware 525 may include a communication interface 526 for setting up and maintaining wired or wireless connections with interfaces of different communication devices of the communication system 500, as well as a radio interface 527 for setting up and maintaining at least a wireless connection 570 with a UE 530 located within a coverage area (not shown in FIG. 7) served by the radio access network node 520. The communication interface 526 may be configured to facilitate a connection 560 to the host computer 510. The connection 560 may be direct or may pass through a core network (not shown in FIG. 14) of the telecommunication system and / or one or more intermediate networks outside the telecommunication system. In the illustrated embodiment, the hardware 525 of the radio access network node 520 further includes processing circuitry 528, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown), adapted to execute instructions. The radio access network node 520 further includes software 521, either stored internally or accessible via an external connection.

[0160] The communication system 500 further includes the UE 530 already mentioned. Its hardware 535 may include a radio interface 537 configured to set up and maintain a radio connection 570 with a radio access network node serving the coverage area in which the UE 530 is currently located. The hardware 535 of the UE 530 further includes a processing circuit 538 adapted to execute instructions, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown). The UE 530 further includes software 531 stored within or accessible by the UE 530 and executable by the processing circuit 538. The software 531 includes a client application 532. The client application 532, with the support of the host computer 510, may be operable to provide services via the UE 530 to a human or non-human user. In the host computer 510, a host application 512 running may communicate with a client application 532 running via an OTT connection 550 that terminates at the UE 530 and the host computer 510. During the provision of a service to a user, the client application 532 may receive request data from the host application 512 and provide user data in response to the request data. The OTT connection 550 may transport both the request data and the user data. The client application 532 may interact with the user to generate the user data that it provides.

[0161] It should be noted that the host computer 510, the radio access network node 520 and the UE 530 shown in Fig. 14 may be similar to or identical to the host computer 430, one of the radio access network nodes 412a, 412b, 412c and one of the UEs 491, 492 shown in Fig. 13, respectively. That is to say, the internal workings of these entities may be as shown in Fig. 14, and independently, the surrounding network topology may be that of Fig. 13.

[0162] 14, an OTT connection 550 is depicted abstractly to illustrate communication between the host computer 510 and the UE 530 through the network node 520 without explicit reference to any intermediate devices and the exact routing of messages through those devices. The routing may be determined by the network infrastructure, which may be configured to hide the routing from the UE 530 or the service provider operating the host computer 510, or both. While the OTT connection 550 is active, the network infrastructure may further make decisions to dynamically change the routing (e.g., based on load balancing considerations or network reconfiguration).

[0163] The wireless connection 570 between the UE 530 and the radio access network node 520 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 530 by means of the OTT connection 550, of which the wireless connection 570 forms the last segment. More precisely, the teachings of these embodiments may reduce interference by improved classification capabilities of flying UEs that may create significant interference.

[0164] A measurement procedure may be provided for the purpose of monitoring data rates, latency and other factors that are improved by one or more embodiments. There may further be optional network functionality for reconfiguring the OTT connection 550 between the host computer 510 and the UE 530 in response to measurement variations. The measurement procedure and / or the network functionality for reconfiguring the OTT connection 550 may be implemented in the software 511 and hardware 515 of the host computer 510, or in the software 531 and hardware 535 of the UE 530, or both. In some embodiments, sensors (not shown) may be deployed in or associated with the communication device through which the OTT connection 550 passes, and these sensors may participate in the measurement procedure by providing values ​​of the monitored quantities exemplified above or providing values ​​of other physical quantities from which the monitored quantities may be calculated or estimated by the software 511, 531. Reconfiguration of the OTT connection 550 may include message formats, retransmission settings, preferred routing, etc., which may not affect the network node 520 and may be unknown or imperceptible to the radio access network node 520. Such procedures and functionality may be known or practiced in the art. In one embodiment, the measurements may involve proprietary UE signaling that facilitates measurements by the host computer 510 of throughput, propagation time, latency, etc. The measurements may be implemented by the software 511 and 531 sending messages, specifically empty or "dummy" messages, over the OTT connection 550 while monitoring propagation times, errors, etc.

[0165] The inventive concept has been described above primarily with reference to certain embodiments. However, as will be readily appreciated by those skilled in the art, other embodiments than those disclosed above are equally possible within the scope of the inventive concept as defined by the appended claims.

Claims

1. A method for data acquisition for a UE (85) in 5GC, the method being performed by a first NF node (100), the method comprising: receiving (S106) a request for data of the UE (85) from a second NF node (200); Obtaining the data of the UE (85) including an AAA Server FQDN (S108); Providing (S110) the data of the UE (85) including the AAA Server FQDN to the second NF node (200); Including, The method, wherein the second NF node (200) is an SMF node.

2. 2. The method of claim 1, wherein the AAA server FQDN is obtained from a UDR node (45), in particular the method further comprises: Receiving a first update request including the AAA server FQDN from a NEF node (20) (S102); providing (S104) a second update request to the UDR node (45) together with the AAA Server FQDN.

3. 2. The method of claim 1, wherein the method is performed as part of a PDU session establishment procedure for the UE (85).

4. 2. The method of claim 1, wherein the request for data is a request for obtaining session management subscription data for the UE (85).

5. 2. The method of claim 1, wherein the data for the UE (85) is provided in either a DnnConfiguration object or a 5gVnGroupData object.

6. The method of claim 1, wherein the first NF node (100) is a UDM node.

7. A method for data acquisition for a UE (85) in 5GC, the method being performed by a second NF node (200), the method comprising: providing a request for data of the UE (85) to a first NF node (100) (S202); receiving (S204) the data of the UE (85) including an AAA server FQDN from the first NF node (100); Including, The method, wherein the second NF node (200) is an SMF node.

8. The method of claim 7, further comprising: authenticating the data of the UE with an AAA server, the AAA server being determined based on the AAA server FQDN.

9. 9. The method of claim 8, wherein determining the AAA server comprises obtaining a set of AAA server IP addresses from a DNS server by providing the AAA server FQDN to the DNS server (S206).

10. 10. The method of claim 9, further comprising: storing (S208) a mapping between the AAA server FQDN and each IP address in the set of AAA server IP addresses.

11. 10. The method of claim 9, further comprising: providing (S210) an authentication request for the UE (85) to the AAA server at one of the IP addresses in the set of AAA server IP addresses.

12. The method of claim 11, wherein the authentication request is for a secondary authentication and authorization for the UE (85).

13. 13. The method of claim 12, wherein if the AAA server is not reachable at the one of the IP addresses in the set of AAA server IP addresses, then the authentication request is provided to another one of the IP addresses in the set of AAA server IP addresses.

14. 13. The method of claim 12, wherein providing the request for data is triggered by a previous failed attempt to contact the AAA server.

15. 8. The method of claim 7, wherein the method is performed as part of a PDU session establishment procedure for the UE (85).

16. The method of claim 7, wherein the request for data is a request for obtaining session management subscription data for the UE (85).

17. 8. The method of claim 7, wherein the data for the UE (85) is received in either a DnnConfiguration object or a 5gVnGroupData object.

18. The method of claim 7, wherein the first NF node (100) is a UDM node.

19. A first NF node (100) for data acquisition of a UE (85) in 5GC, the first NF node (100) comprising a processing circuit (110), the processing circuit providing to the first NF node (100): receiving a request for data for the UE (85) from a second NF node (200); obtaining said data of said UE (85) including an AAA Server FQDN; providing said data of said UE (85) including said AAA Server FQDN to said second NF node (200); configured to cause The second NF node (200) is a first NF node (100) that is an SMF node.

20. A first NF node (100) according to claim 19, further configured to execute the method according to any one of claims 2 to 6.

21. A second NF node (200) for data acquisition of a UE (85) in 5GC, the second NF node (200) comprising a processing circuit (210), the processing circuit providing to the second NF node (200): providing a request for data of said UE (85) to a first NF node (100); receiving said data of said UE (85) including an AAA Server FQDN from said first NF node (100); configured to cause The second NF node (200), which is an SMF node.

22. A second NF node (200) according to claim 21, further configured to execute the method according to any one of claims 8 to 18.

Images