Cloud native core network system, MME, and method

Abstract

This cloud native core network system includes: a mobility management entity (MME) that is a containerized network function; and an HSS + UDM that is connected to the MME via a service-based interface (SBI), is a containerized network function, and has a home subscriber server (HSS) function and a unified data management (UDM) function.

Description

Cloud native core network system, MME, and method

[0001] The present disclosure relates to a cloud native core network system, an MME, and a method.

[0002] A wireless communication system compatible with both 4G (4th Generation) and 5G (5th Generation) is being studied (see, for example, Patent Document 1 and Non-Patent Document 1). For example, a 4G EPC (Evolved Packet Core) MME (Mobility Management Entity) is connected to a 5GC HSS (Home Subscriber Server) + UDM (Unified Data Management). The HSS (Home Subscriber Server) + UDM (Unified Data Management) is a core network node having the functions of the HSS and the UDM.

[0003] In addition, the construction of cloud native architecture is underway for the 5th Generation Core network (5GC).

[0004] International Publication No. 2022 / 195851

[0005] 3GPP TS 23.501 V18.2.2 (2023-07) “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 18)”, July 2023

[0006] The present inventor has found that, as 5G becomes increasingly widespread, EPC convergence is expected, and that cloud-native EPC is expected to progress as a preliminary step. The present inventor then noted that messages conforming to the Diameter Protocol are exchanged between the MME and the HSS+UDM, i.e., the MME and the HSS+UDM are connected via an interface conforming to the Diameter Protocol. The present inventor then noted that, with an interface conforming to the Diameter Protocol, communication is bound to the IP addresses of the MME and the HSS+UDM. The present inventor then found that an interface conforming to the Diameter Protocol may impair the flexibility of the cloud-native architecture (e.g., ease of configuration expansion, ease of building a redundant configuration). In other words, the present inventor found that simply converting the MME to cloud-native may impair the benefits of the cloud-native architecture.

[0007] An object of the present disclosure is to provide a cloud native core network system, an MME, and a method that can connect an MME and a UDM while maintaining the advantages of a cloud native architecture.

[0008] In one aspect, a cloud native core network system includes: a Mobility Management Entity (MME) that is a containerized network function; and a core network node that is connected to the MME via a Service Based Interface (SBI), that is a containerized network function, and that has a Home Subscriber Server (HSS) function and a Unified Data Management (UDM) function.

[0009] In another aspect, a cloud native core network system includes: a Mobility Management Entity (MME) that is a containerized network function; and a Unified Data Management (UDM) that is a containerized network function connected to the MME via a Service Based Interface (SBI).

[0010] In another aspect, a method performed by a cloud native core network system includes: the cloud native core network system includes: an MME (Mobility Management Entity) that is a containerized network function (CNF); and a core network node that is connected to the MME via a Service Based Interface (SBI), is a containerized network function, and has a Home Subscriber Server (HSS) function and a Unified Data Management (UDM) function, wherein the MME includes a plurality of MME processing units corresponding to any of a plurality of MME services of the MME; and the core network node includes a plurality of HSS processing units corresponding to any of a plurality of HSS services of the core network node; and the method includes: one MME processing unit among the plurality of MME processing units obtaining, from a Domain Name System (DNS), an IP address of a target HSS processing unit corresponding to the one HSS service, based on a Fully Qualified Domain Name (FQDN) corresponding to the one HSS service.

[0011] In another aspect, a method performed by a cloud native core network system includes: the cloud native core network system includes: a Mobility Management Entity (MME) that is a containerized network function; and a Unified Data Management (UDM) that is connected to the MME via a Service Based Interface (SBI) and is a containerized network function; the MME includes a plurality of MME processing units corresponding to any of a plurality of MME services of the MME and a plurality of conversion processing units corresponding to the plurality of MME processing units, respectively; and the UDM includes a plurality of UDM processing units corresponding to any of a plurality of UDM services of the UDM; and the method includes: a conversion processing unit corresponding to one MME processing unit among the plurality of MME processing units obtaining an IP address of a target UDM processing unit corresponding to the one UDM service from a Domain Name System (DNS) based on a Fully Qualified Domain Name (FQDN) corresponding to the one UDM service.

[0012] In another aspect, a method executed by a cloud native core network system, the cloud native core network system includes: an MME (Mobility Management Entity) that is a containerized network function (CNF); a UDM (Unified Data Management) that is connected to the MME via a service based interface (SBI) and is a containerized network function; and a converter that is connected to the MME by a diameter protocol interface and to the UDM by the service based interface (SBI), converting a hypertext transfer protocol (HTTP) compliant message received from the UDM into a diameter protocol compliant message and outputting the diameter protocol compliant message to the MME, wherein the MME includes a plurality of MME processors corresponding to any of a plurality of MME services of the MME, the UDM includes a plurality of UDM processors corresponding to any of a plurality of UDM services of the UDM, and the method further includes: the converter converting a fully qualified domain name (FQDN) corresponding to one UDM service into a diameter protocol compliant message; The method includes obtaining an IP address of a target UDM processing unit corresponding to the one UDM service from a DNS (Domain Name System) based on the IP address of the target UDM processing unit.

[0013] In another aspect, the Mobility Management Entity (MME) is a containerized network function and is connected to a core network node that is a containerized network function and has Home Subscriber Server (HSS) functionality and Unified Data Management (UDM) functionality via a Service Based Interface (SBI).

[0014] In another aspect, a Mobility Management Entity (MME) is a containerized network function and is connected to a Unified Data Management (UDM) containerized network function via a Service Based Interface (SBI).

[0015] In another aspect, a method performed by a Mobility Management Entity (MME), wherein the MME is a containerized network function and is connected to a core network node that is a containerized network function and has a Home Subscriber Server (HSS) function and a Unified Data Management (UDM) function via a Service Based Interface (SBI), the core network node comprising a plurality of HSS Processing Units corresponding to any of a plurality of HSS services of the core network node, and the MME comprises a plurality of MME Processing Units corresponding to any of a plurality of MME services of the MME, the method including one of the plurality of MME Processing Units obtaining, from a Domain Name System (DNS), an IP address of a target HSS Processing Unit corresponding to the one HSS service based on a Fully Qualified Domain Name (FQDN) corresponding to the one HSS service.

[0016] In another aspect, a method performed by a Mobility Management Entity (MME), the MME being a containerized network function and connected to a Unified Data Management (UDM) containerized network function via a Service Based Interface (SBI), the UDM comprising a plurality of UDM processing units corresponding to any of a plurality of UDM services of the UDM, the MME comprising a plurality of MME processing units corresponding to any of a plurality of MME services of the MME and a plurality of conversion processing units respectively corresponding to the plurality of MME processing units, the method including one conversion processing unit corresponding to one of the plurality of MME processing units obtaining an IP address of a target UDM processing unit corresponding to the one UDM service from a Domain Name System (DNS) based on a Fully Qualified Domain Name (FQDN) corresponding to the one UDM service.

[0017] The present disclosure makes it possible to provide a cloud native core network system, an MME, and a method that can connect an MME and a UDM while maintaining the benefits of a cloud native architecture.

[0018] Fig. 1 is a diagram illustrating a container technology used to build a cloud native core network system. Fig. 2 is a diagram illustrating an example of a cloud native core network system of the present disclosure. Fig. 3 is a diagram illustrating another example of a cloud native core network system of the present disclosure. Fig. 4 is a diagram illustrating another example of a cloud native core network system of the present disclosure. Fig. 5 is a diagram illustrating another example of a cloud native core network system of the present disclosure.

[0019] Hereinafter, embodiments will be described with reference to the drawings. In this disclosure, the drawings may relate to one or more embodiments. Furthermore, each element in the drawings may apply to one or more embodiments. Furthermore, in the embodiments, identical or equivalent elements are given the same reference numerals, and redundant description will be omitted.

[0020] <Overview of Cloud Native Core Network System> Figure 1 is a diagram illustrating container technology used to build a cloud native core network system. The "server" in Figure 1 includes one or more physical servers. The "server" may have at least one memory (not shown) that stores instructions and at least one processor (not shown) that executes processing in accordance with the instructions.

[0021] As shown in Fig. 1, the container technology is a technology for building a virtualized execution environment called a "container" on a host operating system (OS). A container engine controls the container to be controlled.

[0022] The cloud native core network system of the present disclosure includes multiple network functions (e.g., a Mobility Management Entity (MME), a Home Subscriber Server (HSS) + Unified Data Management (UDM), etc.). Each network function provides one or more services (e.g., data processing). Each service is provided by the above-mentioned container. That is, each container corresponds to one of the services (or processing) of the corresponding network function. In other words, the network function of the present disclosure is containerized.

[0023] In this way, the network function unit of the present disclosure is realized as a cloud-native virtualized network function (CNF) by executing each service of the network function unit using a container.

[0024] First Embodiment Fig. 2 is a diagram illustrating an example of a cloud native core network system according to the present disclosure. In Fig. 2, a cloud native core network system 10 includes an MME 11 and an HSS+UDM 12.

[0025] The MME 11 is a cloud-native virtualized network function (CNF), that is, the MME 11 is a containerized network function.

[0026] The HSS+UDM 12 is a core network node having the functions of a Home Subscriber Server (HSS) and a Unified Data Management (UDM). The HSS+UDM 12 is a cloud-native virtualized network function (CNF). That is, the HSS+UDM 12 is a containerized network function. The HSS+UDM 12 is connected to the MME 11 via a Service-Based Interface (SBI).

[0027] As described above, according to the first embodiment, the MME 11 and the HSS+UDM 12 are each a cloud-native virtualized network function (CNF) in the cloud-native core network system 10. The HSS+UDM 12 is connected to the MME 11 via a service-based interface (SBI).

[0028] This configuration of the cloud native core network system 10 allows the HSS+UDM12 and MME11 to be connected via a service-based interface (SBI), thereby enabling the MME11 and HSS+UDM12 to be connected while maintaining the benefits of the cloud native architecture.

[0029] Second Embodiment FIG. 3 is a diagram illustrating another example of a cloud native core network system according to the present disclosure.

[0030] In FIG. 3 , the cloud native core network system 10 includes an MME 11 and an HSS+UDM 12 .

[0031] The MME 11 has MME processing units 11A-1 to 11A-M (M is an integer equal to or greater than 2). Hereinafter, when the MME processing units 11A-1 to 11A-M are not particularly distinguished from one another, each of the MME processing units 11A-1 to 11A-M, or the MME processing units 11A-1 to 11A-M, may be collectively referred to simply as the MME processing unit 11A. Each MME processing unit 11A corresponds to one of the multiple MME services of the MME 11. For example, the MME processing units 11A-1 to 11A-3 may correspond to one MME service, and the MME processing unit 11A-M may correspond to another MME service. Here, each MME processing unit 11A corresponds to, for example, an MME pod. An MME pod is a unit for managing MME containers and may include one or more MME containers.

[0032] The HSS+UDM 12 includes HSS processing units 12A-1 to 12A-N (N is an integer equal to or greater than 2). Hereinafter, when no distinction is made between the HSS processing units 12A-1 to 12A-N, each of the HSS processing units 12A-1 to 12A-N, or the HSS processing units 12A-1 to 12A-N, may be collectively referred to simply as the HSS processing unit 12A. Each HSS processing unit 12A corresponds to one of a plurality of HSS services of the HSS+UDM 12. For example, the HSS processing units 12A-1 to 12A-3 may correspond to one HSS service, and the HSS processing units 12A-(N-1) and 12A-N may correspond to another HSS service. Here, each HSS processing unit 12A corresponds to, for example, an HSS pod. An HSS pod is a unit for managing HSS containers, and can include one or more HSS containers.

[0033] One of the multiple MME processing units 11A acquires an Internet Protocol (IP) address of a target HSS processing unit 12A corresponding to one HSS service from a Domain Name System (DNS) based on a Fully Qualified Domain Name (FQDN) corresponding to the one HSS service. The MME processing unit 11A then uses the acquired IP address to send a message to the target HSS processing unit 12A. For example, the MME processing unit 11A sends a name resolution request including the FQDN corresponding to the one HSS service and the IP address of the one MME processing unit 11A to a Domain Name System (DNS) (not shown). The MME processing unit 11A then receives a response message including the IP address of the target HSS processing unit 12A corresponding to the one HSS service and the IP address of the one MME processing unit 11A, which is sent from the DNS (not shown) in response to the name resolution request. Then, the one MME processing unit 11A sends a message to the target HSS processing unit 12A using the IP address included in the response message. That is, the one MME processing unit 11A sends a message to the target HSS processing unit 12A, the message including the IP address of the target HSS processing unit 12A as the destination IP address and the IP address of the one MME processing unit 11A as the source address. Note that the DNS (not shown) may be included in the cloud native core network system 10, or may be a system existing outside the cloud native core network system 10.

[0034] For example, the MME 11 holds a first table that associates a plurality of HSS services with FQDNs corresponding to each HSS service. Therefore, the first MME processing unit 11A refers to the first table to identify an FQDN corresponding to an HSS service that the first MME processing unit 11A intends to receive. The first MME processing unit 11A then transmits a name resolution request including the identified FQDN to a DNS (Domain Name System) (not shown).

[0035] The DNS (not shown) holds a second table that associates a plurality of FQDNs corresponding to a plurality of HSS services with one or more IP addresses corresponding to each FQDN (i.e., one or more HSS processing units 12A corresponding to each FQDN). The DNS (not shown) then refers to the second table and selects one of the one or more IP addresses (i.e., one or more HSS processing units 12A) corresponding to the FQDN included in the name resolution request. The DNS (not shown) then transmits a response message including the selected IP address (i.e., the IP address of the target HSS processing unit 12A) to one MME processing unit 11A.

[0036] Furthermore, one of the multiple HSS processing units 12A acquires the IP address of the target MME processing unit 11A corresponding to one MME service from a Domain Name System (DNS) based on the FQDN corresponding to the one MME service. The one HSS processing unit 12A then transmits a message to the target MME processing unit 11A using the acquired IP address. For example, the one HSS processing unit 12A transmits a name resolution request including the FQDN corresponding to the one MME service and the IP address of the one HSS processing unit 12A to the DNS (not shown). The one HSS processing unit 12A then receives a response message including the IP address of the target MME processing unit 11A corresponding to the one MME service and the IP address of the one HSS processing unit 12A, which is transmitted from the DNS (not shown) in response to the name resolution request. Then, the one HSS processing unit 12A transmits a message to the target MME processing unit 11A using the IP address included in the response message. That is, the one HSS processing unit 12A transmits a message to the target MME processing unit 11A, the message including the IP address of the target MME processing unit 11A as the destination IP address and the IP address of the one HSS processing unit 12A as the source address. Note that the DNS (not shown) may be included in the cloud native core network system 10, or may be a system existing outside the cloud native core network system 10.

[0037] For example, the HSS 12 holds a third table that associates a plurality of MME services with FQDNs corresponding to each MME service. Therefore, the first HSS processing unit 12A refers to the first table to identify an FQDN corresponding to an MME service that the first HSS processing unit 12A intends to receive. The first HSS processing unit 12A then transmits a name resolution request including the identified FQDN to a DNS (not shown).

[0038] The DNS (not shown) holds a fourth table that associates a plurality of FQDNs corresponding to a plurality of MME services with one or more IP addresses corresponding to each FQDN (i.e., one or more MME processing units 11A corresponding to each FQDN). The DNS (not shown) then refers to the fourth table and selects one of the one or more IP addresses (i.e., one or more MME processing units 11A) corresponding to the FQDN included in the name resolution request. The DNS (not shown) then transmits a response message including the selected IP address (i.e., the IP address of the target MME processing unit 11A) to one HSS processing unit 12A.

[0039] As described above, according to the second embodiment, in the cloud native core network system 10, one MME processing unit 11A acquires the IP address of the target HSS processing unit 12A corresponding to one HSS service from a DNS (not shown) based on an FQDN corresponding to the one HSS service. Then, the one MME processing unit 11A uses the acquired IP address to send a message to the target HSS processing unit 12A. For example, the one MME processing unit 11A sends a name resolution request including the FQDN corresponding to the one HSS service and the IP address of the one MME processing unit 11A to the DNS (not shown). Then, the one MME processing unit 11A receives a response message including the IP address of the target HSS processing unit 12A corresponding to the one HSS service and the IP address of the one MME processing unit 11A, which is sent from the DNS (not shown) in response to the name resolution request. Then, the one MME processing unit 11A transmits a message to the target HSS processing unit 12A using the IP address included in the response message.

[0040] This configuration of the cloud native core network system 10 allows the MME processing units 11A-1 to 11A-M and the HSS processing units 12A-1 to 12A-N to be connected in a mesh pattern, thereby enabling the cloud native core network system 10 to enjoy the benefits of the flexibility of the cloud native architecture (for example, ease of configuration expansion and ease of building a redundant configuration).

[0041] Third Embodiment Fig. 4 is a diagram illustrating another example of a cloud native core network system according to the present disclosure. In Fig. 4, a cloud native core network system 20 includes an MME 21 and a UDM 22.

[0042] The MME 21 is a cloud-native virtualized network function (CNF).

[0043] The UDM 22 is a cloud-native virtualized network function (CNF) and is connected to the MME 11 via a service-based interface (SBI).

[0044] As described above, according to the third embodiment, the MME 21 and the UDM 22 are each a cloud-native virtualized network function (CNF) in the cloud-native core network system 10. The UDM 22 is connected to the MME 21 via a service-based interface (SBI).

[0045] This configuration of the cloud native core network system 10 allows the UDM 22 and the MME 21 to be connected via a service-based interface (SBI), thereby enabling the MME 21 and the UDM 22 to be connected while maintaining the benefits of the cloud native architecture.

[0046] Fourth Embodiment FIG. 5 is a diagram illustrating another example of a cloud native core network system according to the present disclosure.

[0047] In FIG. 5 , the cloud native core network system 20 includes an MME 21 and a UDM 22 .

[0048] The MME 21 has MME processing units 21A-1 to 21A-M (M is an integer of 2 or greater) and conversion processing units 21B-1 to 21B-M (M is an integer of 2 or greater) corresponding to the MME processing units 21A-1 to 21A-M, respectively. Hereinafter, when the MME processing units 21A-1 to 21A-M are not particularly distinguished from one another, each of the MME processing units 21A-1 to 21A-M, or the MME processing units 21A-1 to 21A-M may be collectively referred to as simply the MME processing unit 21A. Hereinafter, when the conversion processing units 21B-1 to 21B-M are not particularly distinguished from one another, each of the conversion processing units 21B-1 to 21B-M, or the MME processing units 21B-1 to 21B-M may be collectively referred to as simply the conversion processing unit 21B. Each MME processing unit 21A corresponds to one of a plurality of MME services of the MME 21. For example, the MME processing units 21A-1 to 21A-3 may correspond to one MME service, and the MME processing unit 21A-M may correspond to another MME service. Here, each MME processing unit 21A corresponds to, for example, an MME pod. An MME pod is a unit for managing MME containers and may include one or more MME containers.

[0049] The UDM 22 includes UDM processing units 22A-1 to 22A-N (N is an integer equal to or greater than 2). Hereinafter, when the UDM processing units 22A-1 to 22A-N are not particularly distinguished from one another, each of the UDM processing units 22A-1 to 22A-N, or the UDM processing units 22A-1 to 22A-N, may be collectively referred to simply as the UDM processing unit 22A. Each UDM processing unit 22A corresponds to one of the multiple UDM services of the UDM 22. For example, the UDM processing units 22A-1 to 22A-3 may correspond to one UDM service, and the UDM processing units 22A-(N-1) and 22A-N may correspond to another UDM service. Here, each UDM processing unit 22A corresponds to, for example, a UDM pod. A UDM pod is a unit for managing UDM containers and may include one or more UDM containers.

[0050] One of the plurality of MME processing units 21A outputs a Diameter protocol compliant message corresponding to one UDM service to one conversion processing unit 21B corresponding to the one MME processing unit 21A.

[0051] The first conversion processing unit 21B acquires the IP address of the target UDM processing unit 22A corresponding to the first UDM service from the DNS based on the FQDN corresponding to the first UDM service. For example, the first conversion processing unit 21B transmits a name resolution request including the FQDN corresponding to the first UDM service and the IP address of the first conversion processing unit 21B to the DNS (not shown). The first conversion processing unit 21B then receives a response message including the IP address of the target UDM processing unit 22A corresponding to the first UDM service and the IP address of the first conversion processing unit 21B, which is transmitted from the DNS (not shown) in response to the name resolution request. The DNS (not shown) may be included in the cloud native core network system 20 or may be a system located outside the cloud native core network system 20.

[0052] For example, the MME 21 stores a fifth table that associates a plurality of UDM services with FQDNs corresponding to each UDM service. Therefore, the first conversion processing unit 21B refers to the fifth table to identify an FQDN corresponding to a UDM service that the first MME processing unit 21A is to receive. The first conversion processing unit 21B then transmits a name resolution request including the identified FQDN to a DNS (Domain Name System) (not shown).

[0053] The DNS (not shown) maintains a sixth table that associates a plurality of FQDNs corresponding to a plurality of UDM services with one or more IP addresses corresponding to each FQDN (i.e., one or more UDM processing units 22A corresponding to each FQDN). The DNS (not shown) then refers to the sixth table and selects one of the one or more IP addresses (i.e., one or more UDM processing units 22A) corresponding to the FQDN included in the name resolution request. The DNS (not shown) then transmits a response message including the selected IP address (i.e., the IP address of the target UDM processing unit 22A) to one conversion processing unit 21B.

[0054] The first conversion processing unit 21B then converts the Diameter protocol-compliant message received from the first MME processing unit 21A into an HTTP (hypertext transfer protocol)-compliant message. The first conversion processing unit 21B then transmits the HTTP-compliant message to the target UDM processing unit 22A using the IP address included in the response message. That is, the first conversion processing unit 21B transmits an HTTP-compliant message that includes the IP address of the target UDM processing unit 22A as the destination IP address and the IP address of the first conversion processing unit 21B as the source address.

[0055] Furthermore, one of the multiple UDM processing units 22A acquires, from the DNS, the IP address of one conversion processing unit 21B corresponding to the target MME processing unit 21A of one MME service, based on the FQDN corresponding to the one MME service. Then, the one UDM processing unit 22A uses the acquired IP address to send an HTTP-compliant message addressed to the target MME processing unit 21A to the conversion processing unit 21B corresponding to the target MME processing unit 21A. For example, the one UDM processing unit 22A sends a name resolution request including the FQDN corresponding to the one MME service and the IP address of the one UDM processing unit 22A to the DNS (not shown). Then, the one UDM processing unit 22A receives a response message sent from the DNS (not shown) in response to the name resolution request, the response message including the IP address of one conversion processing unit 21B corresponding to the target MME processing unit 21A of the one MME service and the IP address of the one UDM processing unit 22A. Then, the one UDM processing unit 22A uses the IP address included in the response message to transmit an HTTP-compliant message to the conversion processing unit 21B corresponding to the target MME processing unit 21A. That is, the one UDM processing unit 22A transmits an HTTP-compliant message that includes the IP address of the one conversion processing unit 21B corresponding to the target MME processing unit 21A as the destination IP address and the IP address of the one UDM processing unit 22A as the source address to the conversion processing unit 21B corresponding to the target MME processing unit 21A.

[0056] Then, the one conversion processing unit 21B converts the HTTP-compliant message received from the one UDM processing unit 22A into a Diameter Protocol-compliant message. Then, the one conversion processing unit 21B outputs the Diameter Protocol-compliant message to the target MME processing unit 21A. Note that the DNS (not shown) may be included in the cloud native core network system 20, or may be a system existing outside the cloud native core network system 20.

[0057] For example, the UDM 22 holds a seventh table that associates a plurality of MME services with FQDNs corresponding to each MME service. Therefore, one UDM processing unit 22A refers to the seventh table to identify an FQDN corresponding to an MME service that the one UDM processing unit 22A is to receive. Then, the one UDM processing unit 22A transmits a name resolution request including the identified FQDN to a DNS (Domain Name System) (not shown).

[0058] The DNS (not shown) holds an eighth table that associates a plurality of FQDNs corresponding to a plurality of MME services with one or more IP addresses corresponding to each FQDN (i.e., one or more MME processing unit conversion processing units 21B corresponding to each FQDN). The DNS (not shown) then refers to the eighth table and selects one of the one or more IP addresses (i.e., one or more conversion processing units 21B) corresponding to the FQDN included in the name resolution request. The DNS (not shown) then transmits a response message including the selected IP address (i.e., the IP address of the conversion processing unit 21B corresponding to the target MME processing unit 21A) to one UDM processing unit 22A.

[0059] As described above, according to the fourth embodiment, in the cloud native core network system 20, a conversion processing unit 21B corresponding to a MME processing unit 21A converts a Diameter Protocol-compliant message addressed to a target UDM processing unit corresponding to a UDM service into a hypertext transfer protocol (HTTP)-compliant message. Furthermore, the conversion processing unit 21B acquires an IP address of a target UDM processing unit 22A corresponding to the UDM service from a DNS based on an FQDN corresponding to the UDM service. For example, the conversion processing unit 21B transmits a name resolution request including the FQDN corresponding to the UDM service and the IP address of the conversion processing unit 21B to a DNS (not shown). The conversion processing unit 21B then receives a response message transmitted from the DNS (not shown) in response to the name resolution request, the response message including the IP address of the target UDM processing unit 22A corresponding to the UDM service and the IP address of the conversion processing unit 21B. Then, the first conversion processing unit 21B uses the acquired IP address to send the HTTP-compliant message to the target UDM processing unit 22A.

[0060] This configuration of the cloud native core network system 20 allows the MME processing units 21A-1 to 21A-M and the UDM processing units 22A-1 to 22A-N to be connected in a mesh pattern, thereby enabling the cloud native core network system 20 to enjoy the benefits of the flexibility of the cloud native architecture (for example, ease of expanding the configuration and ease of building a redundant configuration).

[0061] 6 is a diagram illustrating another example of a cloud native core network system according to the present disclosure. In FIG. 6, a cloud native core network system 30 includes an MME 31, a UDM 32, and a conversion unit 33.

[0062] The MME 31 has MME processing units 21A-1 to 21A-M (M is an integer of 2 or more).

[0063] The UDM 32 has UDM processing units 22A-1 to 22A-N (N is an integer of 2 or more).

[0064] The conversion unit 33 is connected to the MME 31 via a Diameter protocol interface. The conversion unit 33 is also connected to the UDM 32 via a service-based interface (SBI). The conversion unit 33 converts an HTTP-compliant message received from the UDM 32 into a Diameter protocol-compliant message and outputs the Diameter protocol-compliant message to the MME 31. The conversion unit 33 also converts a Diameter protocol-compliant message received from the MME 31 into an HTTP-compliant message and outputs the HTTP-compliant message to the UDM 32. In other words, the conversion unit 33 has functions equivalent to those of the above-mentioned conversion processing units 21B-1 to 22A-M (M is an integer of 2 or greater).

[0065] Although the present disclosure has been described above with reference to the embodiments, the present disclosure is not limited to the above-described embodiments. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present disclosure within the scope of the present disclosure. Furthermore, each embodiment can be combined with other embodiments as appropriate.

[0066] Some or all of the above embodiments may be described as, but are not limited to, the following supplementary notes: (Supplementary Note 1) A cloud native core network system including: an MME (Mobility Management Entity) that is a containerized network function; and a core network node that is connected to the MME via a service-based interface (SBI), is a containerized network function, and has a home subscriber server (HSS) function and a unified data management (UDM) function. (Supplementary Note 2) The cloud native core network system according to Supplementary Note 1, wherein the MME comprises a plurality of MME processing units corresponding to any of a plurality of MME services of the MME, the core network node comprises a plurality of HSS processing units corresponding to any of a plurality of HSS services of the core network node, and one MME processing unit among the plurality of MME processing units acquires an IP address of a target HSS processing unit corresponding to the one HSS service from a Domain Name System (DNS) based on an FQDN (Fully Qualified Domain Name) corresponding to the one HSS service. (Supplementary Note 3) The cloud native core network system according to Supplementary Note 2, wherein the one MME processing unit transmits a name resolution request including the FQDN corresponding to the one HSS service to the DNS, and receives the IP address of the target HSS processing unit corresponding to the one HSS service transmitted from the DNS in response to the name resolution request. (Supplementary Note 4) The cloud native core network system according to Supplementary Note 2 or 3, wherein the one MME processing unit transmits a message to the target HSS processing unit using the acquired IP address. (Supplementary Note 5) The cloud native core network system according to Supplementary Note 2, wherein each MME processing unit corresponds to an MME pod, and each HSS processing unit corresponds to an HSS pod.(Supplementary Note 6) The cloud native core network system according to Supplementary Note 5, wherein the MME pod corresponds to one or more MME containers, and the HSS pod corresponds to one or more HSS containers. (Supplementary Note 7) A cloud native core network system including: an MME (Mobility Management Entity) that is a containerized network function; and a UDM (Unified Data Management) that is a containerized network function connected to the MME via a Service Based Interface (SBI). (Supplementary Note 8) The cloud native core network system according to Supplementary Note 7, wherein the MME comprises a plurality of MME processing units corresponding to any of a plurality of MME services of the MME and a plurality of conversion processing units respectively corresponding to the plurality of MME processing units, the UDM comprises a plurality of UDM processing units corresponding to any of a plurality of UDM services of the UDM, and one conversion processing unit corresponding to one MME processing unit among the plurality of MME processing units acquires an IP address of a target UDM processing unit corresponding to the one UDM service from a Domain Name System (DNS) based on an FQDN (Fully Qualified Domain Name) corresponding to the one UDM service. (Supplementary Note 9) The cloud native core network system according to Supplementary Note 8, wherein the one conversion processing unit transmits a name resolution request including the FQDN corresponding to the one UDM service to the DNS, and receives the IP address of the target UDM processing unit corresponding to the one UDM service transmitted from the DNS in response to the name resolution request. (Supplementary Note 10) The cloud native core network system according to Supplementary Note 8 or 9, wherein the one conversion processing unit converts a Diameter Protocol-compliant message directed to the target UDM processing unit into an HTTP (hypertext transfer protocol)-compliant message, and sends the HTTP-compliant message to the target UDM processing unit using the acquired IP address.(Supplementary Note 11) The cloud native core network system according to Supplementary Note 7, comprising a conversion unit connected to the MME by a Diameter Protocol interface and connected to the UDM by a Service Based Interface (SBI), and converting an HTTP (hypertext transfer protocol) compliant message received from the UDM into a Diameter Protocol compliant message and outputting the Diameter Protocol compliant message to the MME. (Supplementary Note 12) The cloud native core network system according to Supplementary Note 11, wherein the MME comprises a plurality of MME processing units corresponding to any of a plurality of MME services of the MME, the UDM comprises a plurality of UDM processing units corresponding to any of a plurality of UDM services of the UDM, and the conversion unit acquires an IP address of a target UDM processing unit corresponding to one UDM service from a Domain Name System (DNS) based on an FQDN (Fully Qualified Domain Name) corresponding to one UDM service. (Supplementary Note 13) The cloud native core network system according to Supplementary Note 12, wherein the conversion unit transmits a name resolution request including an FQDN corresponding to the one UDM service to the DNS, and receives an IP address of a target UDM processing unit corresponding to the one UDM service transmitted from the DNS in response to the name resolution request. (Supplementary Note 14) The cloud native core network system according to Supplementary Note 12 or 13, wherein the conversion unit converts a Diameter Protocol compliant message directed to the target UDM processing unit into an HTTP compliant message, and transmits the HTTP compliant message to the target UDM processing unit by using the acquired IP address. (Supplementary Note 15) The cloud native core network system according to Supplementary Note 8 or 12, wherein each MME processing unit corresponds to an MME pod, and each UDM processing unit corresponds to a UDM pod. (Supplementary Note 16) The cloud native core network system according to Supplementary Note 15, wherein the MME pod corresponds to one or more MME containers, and the UDM pod corresponds to one or more UDM containers.(Supplementary Note 17) A method executed by a cloud native core network system, the cloud native core network system including: an MME (Mobility Management Entity) which is a containerized network function (CNF); and a core network node which is connected to the MME via a service based interface (SBI), is a containerized network function, and has a home subscriber server (HSS) function and a unified data management (UDM) function; the MME includes a plurality of MME processing units corresponding to any of a plurality of MME services of the MME; and the core network node includes a plurality of HSS processing units corresponding to any of a plurality of HSS services of the core network node; the method includes: one MME processing unit among the plurality of MME processing units acquiring an IP address of a target HSS processing unit corresponding to the one HSS service from a domain name system (DNS), based on a fully qualified domain name (FQDN) corresponding to the one HSS service. (Supplementary Note 18) The method according to Supplementary Note 17, wherein the obtaining includes: the one MME processing unit sending a name resolution request to a DNS, the FQDN including the one HSS service; and the one MME processing unit receiving an IP address of a target HSS processing unit corresponding to the one HSS service, sent from the DNS in response to the name resolution request. (Supplementary Note 19) The method according to Supplementary Note 17 or 18, wherein the one MME processing unit sends a message to the target HSS processing unit using the obtained IP address. (Supplementary Note 20) The method according to Supplementary Note 17, wherein each MME processing unit corresponds to an MME pod, and each HSS processing unit corresponds to an HSS pod. (Supplementary Note 21) The method according to Supplementary Note 20, wherein the MME pod corresponds to one or more MME containers, and the HSS pod corresponds to one or more HSS containers.(Supplementary Note 22) A method executed by a cloud native core network system, the cloud native core network system including: an MME (Mobility Management Entity) that is a containerized network function; and a UDM (Unified Data Management) that is connected to the MME via a Service Based Interface (SBI) and is a containerized network function; the MME includes a plurality of MME processing units corresponding to any of a plurality of MME services of the MME, and a plurality of conversion processing units corresponding to the plurality of MME processing units, respectively; the UDM includes a plurality of UDM processing units corresponding to any of a plurality of UDM services of the UDM; and the method includes: one conversion processing unit corresponding to one MME processing unit among the plurality of MME processing units obtaining an IP address of a target UDM processing unit corresponding to the one UDM service from a DNS (Domain Name System), based on an FQDN (Fully Qualified Domain Name) corresponding to the one UDM service. (Supplementary Note 23) The method according to Supplementary Note 22, wherein the obtaining includes: the one conversion processing unit sending a name resolution request including an FQDN corresponding to the one UDM service to the DNS, and the one conversion processing unit receiving an IP address of a target UDM processing unit corresponding to the one UDM service sent from the DNS in response to the name resolution request. (Supplementary Note 24) The method according to Supplementary Note 22 or 23, further including the one conversion processing unit converting a Diameter Protocol compliant message intended for the target UDM processing unit into an HTTP (hypertext transfer protocol) compliant message and sending the HTTP compliant message to the target UDM processing unit using the obtained IP address.(Supplementary Note 25) A method executed by a cloud native core network system, the cloud native core network system including: an MME (Mobility Management Entity) that is a containerized network function (CNF); a UDM (Unified Data Management) that is connected to the MME via a service based interface (SBI) and is a containerized network function; and a conversion unit that is connected to the MME by a diameter protocol interface and to the UDM by the service based interface (SBI) and that converts a hypertext transfer protocol (HTTP) compliant message received from the UDM into a diameter protocol compliant message and outputs the diameter protocol compliant message to the MME, the MME including a plurality of MME processing units corresponding to any of a plurality of MME services of the MME, the UDM including a plurality of UDM processing units corresponding to any of a plurality of UDM services of the UDM, the method further comprising: the conversion unit converting a fully qualified domain name (FQDN) corresponding to one UDM service into a diameter protocol compliant message; The method according to Supplementary Note 25, further comprising: acquiring an IP address of a target UDM processing unit corresponding to the one UDM service from a Domain Name System (DNS) based on a FQDN corresponding to the one UDM service. (Supplementary Note 26) The method according to Supplementary Note 25, wherein the acquiring comprises: the conversion unit sending a name resolution request including an FQDN corresponding to the one UDM service to the DNS; and the conversion unit receiving the IP address of the target UDM processing unit corresponding to the one UDM service sent from the DNS in response to the name resolution request. (Supplementary Note 27) The method according to Supplementary Note 25 or 26, further comprising: the conversion unit converting a Diameter Protocol compliant message addressed to the target UDM processing unit into an HTTP compliant message, and sending the HTTP compliant message to the target UDM processing unit using the acquired IP address.(Supplementary Note 28) The method of Supplementary Note 22 or 25, wherein each MME processing unit corresponds to an MME pod, and each UDM processing unit corresponds to a UDM pod. (Supplementary Note 29) The method of Supplementary Note 28, wherein the MME pod corresponds to one or more MME containers, and the UDM pod corresponds to one or more UDM containers. (Supplementary Note 30) An MME (Mobility Management Entity), which is a containerized network function, and which is connected to a core network node which is a containerized network function and has a Home Subscriber Server (HSS) function and a Unified Data Management (UDM) function via a Service Based Interface (SBI). (Supplementary Note 31) The MME according to Supplementary Note 30, wherein the core network node comprises a plurality of HSS processing units corresponding to any of a plurality of HSS services of the core network node, the MME comprises a plurality of MME processing units corresponding to any of a plurality of MME services of the MME, and one MME processing unit among the plurality of MME processing units acquires an IP address of a target HSS processing unit corresponding to the one HSS service from a Domain Name System (DNS) based on an FQDN corresponding to the one HSS service. (Supplementary Note 32) The MME according to Supplementary Note 31, wherein the one MME processing unit transmits a name resolution request including the FQDN (Fully Qualified Domain Name) corresponding to the one HSS service to the DNS, and receives the IP address of the target HSS processing unit corresponding to the one HSS service transmitted from the DNS in response to the name resolution request. (Supplementary Note 33) The MME according to Supplementary Note 31 or 32, wherein the one MME processing unit transmits a message to the target HSS processing unit using the acquired IP address. (Supplementary Note 34) The MME according to Supplementary Note 31, wherein each MME processing unit corresponds to an MME pod, and each HSS processing unit corresponds to an HSS pod.(Supplementary Note 35) The MME according to Supplementary Note 34, wherein the MME pod corresponds to one or more MME containers, and the HSS pod corresponds to one or more HSS containers. (Supplementary Note 36) An MME (Mobility Management Entity), which is a containerized network function, and which is connected to a containerized network function, Unified Data Management (UDM), via a Service Based Interface (SBI). (Supplementary Note 37) The MME according to Supplementary Note 36, wherein the UDM comprises a plurality of UDM processing units corresponding to any of a plurality of UDM services of the UDM, the MME comprises a plurality of MME processing units corresponding to any of a plurality of MME services of the MME and a plurality of conversion processing units respectively corresponding to the plurality of MME processing units, and one conversion processing unit corresponding to one MME processing unit among the plurality of MME processing units acquires an IP address of a target UDM processing unit corresponding to the one UDM service from a Domain Name System (DNS) based on an FQDN (Fully Qualified Domain Name) corresponding to the one UDM service. (Supplementary Note 38) The MME according to Supplementary Note 37, wherein the one conversion processing unit transmits a name resolution request including the FQDN corresponding to the one UDM service to the DNS, and receives the IP address of the target UDM processing unit corresponding to the one UDM service transmitted from the DNS in response to the name resolution request. (Supplementary Note 39) The MME according to Supplementary Note 37 or 38, wherein the one conversion processing unit converts a Diameter Protocol compliant message addressed to the target UDM processing unit into an HTTP (hypertext transfer protocol) compliant message, and transmits the HTTP compliant message to the target UDM processing unit using the acquired IP address. (Supplementary Note 40) The MME according to Supplementary Note 37, wherein each MME processing unit corresponds to an MME pod, and each UDM processing unit corresponds to a UDM pod.(Supplementary Note 41) The MME according to Supplementary Note 40, wherein the MME pod corresponds to one or more MME containers, and the UDM pod corresponds to one or more UDM containers. (Supplementary Note 42) A method executed by an MME (Mobility Management Entity), wherein the MME is a containerized network function and is connected to a core network node which is also a containerized network function and has a Home Subscriber Server (HSS) function and a Unified Data Management (UDM) function via a Service Based Interface (SBI), the core network node comprises a plurality of HSS processing units corresponding to any of a plurality of HSS services of the core network node, and the MME comprises a plurality of MME processing units corresponding to any of a plurality of MME services of the MME, the method comprising: one MME processing unit among the plurality of MME processing units obtaining, from a Domain Name System (DNS), an IP address of a target HSS processing unit corresponding to the one HSS service, based on a Fully Qualified Domain Name (FQDN) corresponding to the one HSS service. (Supplementary Note 43) The method according to Supplementary Note 42, wherein the obtaining includes: the one MME processing unit sending to the DNS a name resolution request including an FQDN corresponding to the one HSS service; and the one MME processing unit receiving, by the one MME processing unit, an IP address of a target HSS processing unit corresponding to the one HSS service sent from the DNS in response to the name resolution request. (Supplementary Note 44) The method according to Supplementary Note 42 or 43, further including: the one MME processing unit sending a message to the target HSS processing unit using the obtained IP address. (Supplementary Note 45) The method according to Supplementary Note 42, wherein each MME processing unit corresponds to an MME pod, and each HSS processing unit corresponds to an HSS pod.(Supplementary Note 46) The method of Supplementary Note 45, wherein the MME pod corresponds to one or more MME containers; and the HSS pod corresponds to one or more HSS containers. (Supplementary Note 47) A method executed by an MME (Mobility Management Entity), wherein the MME is a containerized network function and is connected to a UDM (Unified Data Management), which is also a containerized network function, via a Service Based Interface (SBI), the UDM comprises a plurality of UDM processing units corresponding to any of a plurality of UDM services of the UDM, the MME comprises a plurality of MME processing units corresponding to any of a plurality of MME services of the MME, and a plurality of conversion processing units corresponding to the plurality of MME processing units, respectively, the method including one conversion processing unit corresponding to one MME processing unit among the plurality of MME processing units obtaining an IP address of a target UDM processing unit corresponding to the one UDM service from a DNS (Domain Name System) based on an FQDN (Fully Qualified Domain Name) corresponding to the one UDM service. (Supplementary Note 48) The method according to Supplementary Note 47, wherein the obtaining includes: the one conversion processing unit sending a name resolution request including an FQDN corresponding to the one UDM service to a DNS (Domain Name System), and the one conversion processing unit receiving an IP address of a target UDM processing unit corresponding to the one UDM service sent from the DNS in response to the name resolution request. (Supplementary Note 49) The method according to Supplementary Note 47 or 48, further including the one conversion processing unit converting a Diameter Protocol compliant message intended for the target UDM processing unit into an HTTP (hypertext transfer protocol) compliant message and sending the HTTP compliant message to the target UDM processing unit using the obtained IP address.(Supplementary Note 50) The method of Supplementary Note 47, wherein each MME processing unit corresponds to an MME pod, and each UDM processing unit corresponds to a UDM pod. (Supplementary Note 51) The method of Supplementary Note 50, wherein the MME pod corresponds to one or more MME containers, and the UDM pod corresponds to one or more UDM containers.

[0067] REFERENCE SIGNS LIST 10 Cloud native core network system 11 MME 11A MME processing unit 12A HSS+UDM processing unit 20 Cloud native core network system 21 MME 21A Processing unit 21B Conversion processing unit 22 UDM 22A UDM processing unit 30 Cloud native core network system 31 MME 32 UDM 33 Conversion unit

Claims

1. A cloud native core network system including: an MME (Mobility Management Entity), which is a containerized network function; and a core network node, which is connected to the MME via a service-based interface (SBI), is a containerized network function, and has a Home Subscriber Server (HSS) function and a Unified Data Management (UDM) function.

2. The cloud native core network system according to claim 1, wherein the MME comprises a plurality of MME processing units corresponding to any of a plurality of MME services of the MME, the core network node comprises a plurality of HSS processing units corresponding to any of a plurality of HSS services of the core network node, and one of the plurality of MME processing units obtains an IP address of a target HSS processing unit corresponding to the one HSS service from a DNS (Domain Name System) based on a FQDN (Fully Qualified Domain Name) corresponding to the one HSS service.

3. The cloud native core network system according to claim 2, wherein the one MME processing unit sends a name resolution request including an FQDN corresponding to the one HSS service to the DNS, and receives an IP address of a target HSS processing unit corresponding to the one HSS service sent from the DNS in response to the name resolution request.

4. The cloud native core network system according to claim 2 or 3, wherein the one MME processing unit transmits a message to the target HSS processing unit by using the acquired IP address.

5. The cloud native core network system according to claim 2, wherein each MME processing unit corresponds to an MME pod, and each HSS processing unit corresponds to an HSS pod.

6. The cloud native core network system according to claim 5, wherein the MME pod corresponds to one or more MME containers, and the HSS pod corresponds to one or more HSS containers.

7. A cloud native core network system including: an MME (Mobility Management Entity), which is a containerized network function; and a UDM (Unified Data Management), which is a containerized network function connected to the MME via a service-based interface (SBI).

8. The cloud native core network system of claim 7, wherein the MME comprises a plurality of MME processing units corresponding to any of a plurality of MME services of the MME, and a plurality of conversion processing units each corresponding to the plurality of MME processing units; the UDM comprises a plurality of UDM processing units corresponding to any of a plurality of UDM services of the UDM; and one conversion processing unit corresponding to one MME processing unit among the plurality of MME processing units obtains an IP address of a target UDM processing unit corresponding to the one UDM service from a DNS (Domain Name System) based on an FQDN (Fully Qualified Domain Name) corresponding to the one UDM service.

9. The cloud native core network system according to claim 7, further comprising a conversion unit connected to the MME via a diameter protocol interface and connected to the UDM via a service-based interface (SBI), and configured to convert an HTTP (hypertext transfer protocol) compliant message received from the UDM into a diameter protocol compliant message and output the diameter protocol compliant message to the MME.

10. A method executed by a cloud native core network system, the cloud native core network system including: an MME (Mobility Management Entity) which is a containerized network function (CNF); and a core network node which is connected to the MME via a service based interface (SBI), is a containerized network function, and has a Home Subscriber Server (HSS) function and a Unified Data Management (UDM) function; the MME includes a plurality of MME processing units corresponding to any of a plurality of MME services of the MME; and the core network node includes a plurality of HSS processing units corresponding to any of a plurality of HSS services of the core network node; and the method includes: one MME processing unit among the plurality of MME processing units acquiring an IP address of a target HSS processing unit corresponding to the one HSS service from a Domain Name System (DNS) based on a Fully Qualified Domain Name (FQDN) corresponding to the one HSS service.

11. A method executed by a cloud native core network system, the cloud native core network system including: an MME (Mobility Management Entity) which is a containerized network function; and a UDM (Unified Data Management) which is connected to the MME via a Service Based Interface (SBI) and is a containerized network function; the MME includes a plurality of MME processing units corresponding to any of a plurality of MME services of the MME, and a plurality of conversion processing units respectively corresponding to the plurality of MME processing units; the UDM includes a plurality of UDM processing units corresponding to any of a plurality of UDM services of the UDM; and the method includes a conversion processing unit corresponding to one MME processing unit among the plurality of MME processing units obtaining an IP address of a target UDM processing unit corresponding to the one UDM service from a Domain Name System (DNS) based on a Fully Qualified Domain Name (FQDN) corresponding to the one UDM service.

12. A method executed by a cloud native core network system, the cloud native core network system including: an MME (Mobility Management Entity) which is a containerized network function (CNF); a UDM (Unified Data Management) which is connected to the MME via a service based interface (SBI) and is a containerized network function; and a conversion unit which is connected to the MME by a diameter protocol interface and to the UDM by the service based interface (SBI) and converts a hypertext transfer protocol (HTTP) compliant message received from the UDM into a diameter protocol compliant message and outputs the diameter protocol compliant message to the MME, the MME including a plurality of MME processing units corresponding to any of a plurality of MME services of the MME, the UDM including a plurality of UDM processing units corresponding to any of a plurality of UDM services of the UDM, the method further including: the conversion unit converting a fully qualified domain name (FQDN) corresponding to one UDM service into ... obtaining an IP address of a target UDM processing unit corresponding to the one UDM service from a Domain Name System (DNS) based on a target name of the one UDM service.

13. A Mobility Management Entity (MME), which is a containerized network function, and which is connected to a core network node that is a containerized network function and has a Home Subscriber Server (HSS) function and a Unified Data Management (UDM) function via a Service Based Interface (SBI).

14. The MME according to claim 13, wherein the core network node comprises a plurality of HSS processing units corresponding to any of a plurality of HSS services of the core network node, the MME comprises a plurality of MME processing units corresponding to any of a plurality of MME services of the MME, and one of the plurality of MME processing units obtains an IP address of a target HSS processing unit corresponding to the one HSS service from a DNS (Domain Name System) based on an FQDN corresponding to the one HSS service.

15. A Mobility Management Entity (MME), which is a containerized network function, and which is connected to a Unified Data Management (UDM) containerized network function via a Service Based Interface (SBI).

16. The MME of claim 15, wherein the UDM comprises a plurality of UDM processing units corresponding to any of a plurality of UDM services of the UDM, the MME comprises a plurality of MME processing units corresponding to any of a plurality of MME services of the MME, and a plurality of conversion processing units respectively corresponding to the plurality of MME processing units, and a conversion processing unit corresponding to one of the plurality of MME processing units obtains an IP address of a target UDM processing unit corresponding to the one UDM service from a DNS (Domain Name System) based on an FQDN (Fully Qualified Domain Name) corresponding to the one UDM service.

17. The MME according to claim 16, wherein the one conversion processing unit sends a name resolution request including an FQDN corresponding to the one UDM service to the DNS, and receives an IP address of a target UDM processing unit corresponding to the one UDM service sent from the DNS in response to the name resolution request.

18. The MME according to claim 16 or 17, wherein the one conversion processing unit converts a Diameter protocol compliant message addressed to the target UDM processing unit into an HTTP (hypertext transfer protocol) compliant message, and transmits the HTTP compliant message to the target UDM processing unit using the acquired IP address.

19. A method executed by an MME (Mobility Management Entity), wherein the MME is a containerized network function and is connected to a core network node which is a containerized network function and has a Home Subscriber Server (HSS) function and a Unified Data Management (UDM) function via a Service Based Interface (SBI), wherein the core network node includes a plurality of HSS processing units corresponding to any of a plurality of HSS services of the core network node, and the MME includes a plurality of MME processing units corresponding to any of a plurality of MME services of the MME, the method including one of the plurality of MME processing units obtaining an IP address of a target HSS processing unit corresponding to the one HSS service from a Domain Name System (DNS) based on a Fully Qualified Domain Name (FQDN) corresponding to the one HSS service.

20. A method executed by an MME (Mobility Management Entity), wherein the MME is a containerized network function and is connected to a UDM (Unified Data Management), which is also a containerized network function, via a Service Based Interface (SBI), the UDM includes a plurality of UDM processing units corresponding to any of a plurality of UDM services of the UDM, the MME includes a plurality of MME processing units corresponding to any of a plurality of MME services of the MME, and a plurality of conversion processing units respectively corresponding to the plurality of MME processing units, the method including a conversion processing unit corresponding to one of the plurality of MME processing units obtaining an IP address of a target UDM processing unit corresponding to the one UDM service from a DNS (Domain Name System) based on a FQDN (Fully Qualified Domain Name) corresponding to the one UDM service.

Images