WO2024195282A1 - Core network node, data generation method, program, and communication system - Google Patents

Abstract

The purpose of the present disclosure is to provide a core network node via which a UE can use a service provided in an edge computing environment over a 5G network. A core network node according to the present disclosure is provided with: a reception unit which receives, from an edge node in an edge computing environment, first path information pertaining to a first communication path between an edge application server and the edge node in the edge computing environment; and a data generation unit which generates matching information between the first path information and second path information pertaining to a second communication path between the edge node in the core network and another core network node different from the core network node.

Description

Core network node, data generation method, program, and communication system

The present disclosure relates to a core network node, a data generation method, and a program.

In recent years, the application of a network technology known as edge computing has been considered in comparison with cloud computing, which aggregates all information in the cloud and executes data processing on high-performance servers on the cloud. In edge computing, data processing, data analysis, and other processes are carried out on servers placed in the peripheral areas of devices at the ends of the network, such as Internet of Things (IoT) terminals. The server that has carried out the data processing, etc., sends the processed or analyzed data to the cloud or device. This makes it possible to reduce communication delays and network loads, etc.

Non-Patent Document 1 shows the process flow when a UE (User Equipment) connected to a 5G (5th Generation) network provided by a telecommunications carrier uses a service provided in an edge computing environment. Specifically, it shows the process flow when the telecommunications carrier managing the 5G network is different from the carrier managing the edge computing environment. Non-Patent Document 1 describes that when a core network node arranged in the 5G network receives network information for connecting to the edge computing environment, it translates the received network information into network information to be used by the core network node. The core network node can provide the UE with the services provided in the edge computing environment by using the network information translated so that it can be used in the 5G network.

3GPP TR 23.700-48 V2.0.0 (2022-11)

However, Non-Patent Document 1 does not clearly describe how to identify the translated information from the network information received from the edge computing environment, that is, how the information before and after translation is associated. In other words, the current 3GPP (3rd Generation Partnership Project) (registered trademark) does not specify the specific content of the translation process performed by the core network node. Therefore, each operator may not be able to translate or change the information received from other operators into appropriate information. In this case, there is a problem that the UE may not be able to use the services provided in the edge computing environment.

In view of the above-mentioned problems, the objective of the present disclosure is to provide a core network node, a data generation method, and a program that enable a UE to use services provided in an edge computing environment via a 5G network.

The core network node according to the first aspect of the present disclosure includes a receiving means for receiving, from a first edge node in an edge computing environment, first route information regarding a first communication route between an edge application server in the edge computing environment and the edge node, and a generating means for generating second route information regarding a second communication route between a second edge node in the core network and a first core network node, and information associating the first route information with the second route information.

The data generation method according to the second aspect of the present disclosure receives, from a first edge node in an edge computing environment, first route information regarding a first communication route between an edge application server in the edge computing environment and the edge node, and generates association information between the first route information and second route information regarding a second communication route between a second edge node in a core network and a first core network node.

The program according to the third aspect of the present disclosure causes a computer to receive, from a first edge node in an edge computing environment, first route information regarding a first communication route between an edge application server in the edge computing environment and the edge node, and generate association information between the first route information and second route information regarding a second communication route between a second edge node in a core network and a first core network node.

The present disclosure provides a core network node, a data generation method, and a program that enable a UE to use services provided in an edge computing environment via a 5G network.

FIG. 2 is a configuration diagram of a core network node according to the present disclosure. A diagram showing the flow of data generation processing in a core network node according to the present disclosure. FIG. 1 is a configuration diagram of a communication system according to the present disclosure. This is a configuration diagram of the Local part of DN related to the present disclosure. A diagram showing the flow of the EAS Deployment Information generation process related to the present disclosure. A diagram showing the information elements contained in the EAS profile related to the present disclosure. A diagram showing the information elements included in the EAS Service KPIs disclosed herein. A diagram showing the parameters contained in the EAS Deployment Information disclosed herein. A diagram showing the flow of the EAS Deployment Information update process related to the present disclosure. A diagram showing the parameters contained in the EAS Deployment Information disclosed herein. A diagram showing the parameters contained in the EAS Deployment Information disclosed herein. FIG. 2 is a configuration diagram of a core network node according to the present disclosure.

(Embodiment 1)
Hereinafter, a configuration example of the core network node 10 will be described with reference to Fig. 1. The core network node 10 may be a node arranged in the core network 100. The node may correspond to an entity (device) or a function (function). The core network node 10 may be a computer device operated by a processor executing a program stored in a memory.

The core network node 10 has a receiving unit 11 and a data generating unit 12. The receiving unit 11 and the data generating unit 12 may be software or a module in which processing is performed by a processor executing a program stored in a memory. Alternatively, the receiving unit 11 and the data generating unit 12 may be hardware such as a circuit or a chip. The receiving unit 11 is used as a means for receiving information. The data generating unit 12 is used as a means for generating information.

The receiver 11 receives route information (hereinafter referred to as first route information) regarding a communication path (hereinafter referred to as a first communication path) between an edge application server in the edge computing 200 environment and the edge node 20 from the edge node 20 arranged in the edge computing environment 200. Furthermore, the receiver 11 may receive network information regarding a relay network 300 that connects the core network 100 and the edge computing environment 200.

At least one edge node 20 is arranged in the edge computing environment 200. The edge node 20 provides an edge computing service to a communication terminal or the like connected to the core network 100. The edge computing service may be referred to as an edge application service or an application service. The edge computing environment 200 may also be referred to as a data network connected to the core network 100.

The core network 100 and the edge computing environment 200 may be managed by different operators and may have different management policies. The core network 100 may be, for example, a network managed or operated by a telecommunications carrier and designed in accordance with specifications defined in 3GPP (3rd Generation Partnership Project). The core network 100 may specifically be a 5G core network (5GC: 5G Core network). The edge computing environment 200 may be, for example, a network managed or operated by a service provider and designed in accordance with policies defined independently by the service provider. However, the edge computing environment 200 may be designed in accordance with specifications defined by a telecommunications carrier or 3GPP in order to interconnect with the core network 100.

The relay network 300 may be a network that enables the core network 100 and the edge computing environment 200 to be connected in a secure state. The secure state is a state in which data confidentiality, integrity, availability, etc. are maintained, and may be a state in which specified standards regarding data confidentiality, integrity, and availability are satisfied. The relay network 300 may be, for example, a closed environment network rather than an open network such as the Internet. The closed environment network may be, for example, a network using dedicated lines, or a DC (Data Center) network provided by a specific operator. Alternatively, the relay network 300 may be a VPN (Virtual Private Network) built on a general IP network.

The network information regarding the relay network 300 may be, for example, information for identifying the relay network 300 (e.g., the name of the relay network 300), information for identifying a service provided on the relay network 300 (e.g., the name of a service provided on the relay network 300), information for accessing the relay network 300, etc. Furthermore, the network information may be information regarding a connection between an application server in the edge computing environment 200 and the relay network 300.

The receiving unit 11 may receive network information via another network through which control data is transferred, separate from the relay network 300 through which user data is transferred.

The data generating unit 12 generates information associating the first route information with route information (hereinafter referred to as second route information) regarding a communication route (hereinafter referred to as second communication route) between an edge node in the core network 100 and another core network node different from the core network node 10. The second route information may be rephrased as route information (hereinafter also referred to as communication route information) that identifies a route to the relay network 300 in the core network 100. Furthermore, the data generating unit 12 may associate (or associate) the first route information, the second route information, and the network information. In other words, the data generating unit 12 may generate association information of the first route information, the second route information, and the network information. In this way, the data generating unit 12 generates information associating the route information with the network information. The route information may be, for example, information indicating a device to be passed through, information indicating a line for connecting to the relay network 300, or information regarding a gateway device disposed at an edge of the relay network 300 on the core network 100 side. The gateway device may be an edge node in the core network 100. Also, the gateway device disposed at the edge of the relay network 300 on the edge computing environment 200 side may be an edge node in the edge computing environment 200.

Associating route information with network information may include storing information associating the route information with the network information in a memory or the like.

Next, the flow of the data generation process in the core network node 10 will be described with reference to FIG. 2. First, the receiver 11 receives route information (hereinafter referred to as first route information) regarding a communication route (hereinafter referred to as first communication route) between an edge application server in the edge computing environment 200 and the edge node 20 from the edge node 20 arranged in the edge computing environment 200 (S11). Next, the data generator 12 generates association information between the route information (hereinafter referred to as second route information) regarding a communication route (hereinafter referred to as second communication route) between an edge node in the core network 100 and another core network node different from the core network node 10 and the first route information (S12).

As described above, the core network node 10 associates the route information in the edge computing environment 200 with the route information in the core network 100. The core network node 10 or another core network node uses the association information to enable data transfer between the communication terminal and the edge computing environment 200.

Specifically, by using the correspondence information, the core network node 10 or other core network nodes can identify to which relay network the data transmitted from the communication terminal should be output. Furthermore, the core network node 10 or other core network nodes can identify the route via which the data should be forwarded to the relay network 300. The data output to the relay network 300 is transmitted to the edge computing environment 200 via the relay network 300.

Furthermore, the core network node 10 or another core network node can determine the route through which data received from the edge computing environment 200 via the relay network 300 should be transmitted to the communication terminal. This allows the core network node 10 to provide the services provided in the edge computing environment 200 to the communication terminal via the core network 100.

(Embodiment 2)
Next, a configuration example of a communication system will be described with reference to Fig. 3. The communication system of Fig. 3 includes a UE 30 and an AN (Access Network) 32. Furthermore, the communication system includes a UPF (User Plane Function) 34 that mainly processes User Plane (UP) data. The UPF 34 is connected to a local part of a DN (Data Network) 50. Furthermore, the communication system includes an AMF (Access and Mobility Management Function) 40, an SMF (Session Management Function) 42, an NEF (Network Exposure Function) 44, a UDR (User Data Repository) 46, and a PCF (Policy Control Function) 48 that mainly processes Control Plane (CP) data.

Each component of the communication system in FIG. 3 may be a node. A node may correspond to a physical entity or a logical function.

The core network node 10 in FIG. 1 corresponds to, for example, NEF 44. Also, the edge computing environment 200 in FIG. 1 is constructed in the local part of DN 50, and the edge node 20 is located in the local part of DN 170.

The UPF 34, AMF 40, SMF 42, NEF 44, UDR 46, and PCF 48 constitute the 5G (5th Generation) core network. The 5G core network corresponds to the core network 100 in FIG. 1. A service-based architecture is applied to the AMF 40, SMF 42, NEF 44, UDR 46, and PCF 48, and they are connected to each other via a service-based interface. For example, HTTP (HyperText Transfer Protocol) may be used in the service-based interface. For example, Namf, Nsmf, Nnef, Nudr, and Npcf are defined as the service interfaces.

Reference points are defined between the nodes that make up the communication system. Specifically, N1 is defined between UE 30 and AMF 40. N2 is defined between AN 32 and AMF 40. N3 is defined between AN 32 and UPF 34. N4 is defined between UPF 34 and SMF 42. N6 is defined between UPF 34 and Local part of DN 50. N9 is defined between UPF 34.

AN32 includes at least one of an NG (Next Generation)-RAN (Radio Access Network) and a non-3GPP AN, and is connected to a 5G core network. AN32 may be referred to as a 5G access network. AN32, which provides a wireless communication line to UE30, may be referred to as an (R)AN (Radio AN). UE30 is a general term for a communication terminal in 3GPP. A network including a 5G core network and a 5G access network may be referred to as a 5G network or a 5G system.

As an anchor point in the 5G system, the UPF 34 terminates PDU (Protocol Data Unit) sessions and interconnects with external networks. Among the UPFs, the UPF that specifically terminates PDU sessions and connects to the DN (Data Network) is referred to as a PSA (PDU Session Anchor)-UPF. Furthermore, among the PSA-UPFs, the UPF that connects to the Central DN may be referred to as a Central-PSA or C-PSA, and the UPF 34 that connects to the Local part of DN 50 may be referred to as a Local-PSA or L-PSA.

AMF40 manages terminal access and terminal mobility. SMF42 manages PDU sessions. In addition, SMF42 has a DHCP (Dynamic Host Configuration Protocol) function and assigns IP addresses to connected UEs.

The NEF 44 provides 3GPP network services that can be exposed to the external environment. The UDR 46 provides services for storing and reading structured data to the NEF 44 and the PCF 48. The PCF 48 generates and provides policy rules.

The local part of DN50 is an external network connected to the 5G network. Here, an example configuration of the local part of DN50 will be described with reference to FIG. 4. An EHE (Edge Hosting Environment) 60 is deployed in the local part of DN50 to realize edge computing. The EHE 60 corresponds to the edge computing environment 200 in FIG. 1. The EHE 60 has an EES (Edge Enabler Server) 62 and an EAS (Edge Application Server) 64. A service-based architecture may be applied to the EES 62 and the EAS 64, and each may be connected via a service-based interface. In the service-based interface, for example, HTTP (HyperText Transfer Protocol) may be used.

The EES 62 may be included in an AF (Application Function) and is deployed in the EHE 60. The EES 62 also supports the registration, update, and re-registration functions of the EAS 64. The EES 62 also directly or indirectly communicates with NFs (Network Functions) deployed in the core network 100 (5G core network). The NFs may be nodes that constitute the 5G core network. Direct communication may be performed, for example, via the PCF 48, and indirect communication may be performed, for example, via the NEF 44.

The EAS 64 may be included in the AF and is deployed in the EHE 60. The EAS 64 executes the Edge Application Service.

The EES 62 and the EAS 64 may be connected via a common service interface, for example, via a control plane network in the local part of DN 50. The EES 62 and the NEF 44 may also be connected via a common service interface. For example, the EES 62 and the NEF 44 may be connected via a network that interconnects the control plane network in the local part of DN 50 and the control plane network in the 5G core network. The EAS 64 may also be connected to the relay network 300 via a user plane network. More specifically, the EAS 64 may be connected to the relay network 300 via a gateway device 301 arranged between the EHE 60 and the relay network 300. The UPF 34 may also be connected to the relay network 300 via a gateway device 302 arranged between the 5G core network and the relay network 300.

The operator that manages the 5G core network may be referred to as a Customer that uses edge computing services, and the operator that manages the EHE 60 may be referred to as a Provider that provides edge computing services.

Next, the flow of the EAS Deployment Information generation process will be explained using Figure 5. First, the EAS 64 uses the Create EAS Profile service of the EES 62 (S21). The Create EAS Profile includes an EAS Profile. Alternatively, the EAS 64 may send an EAS registration request message including an EAS Profile to the EES 62. The EAS registration request message is sent when the EAS 64 requests registration to the EES 62. The EAS registration request message may include information indicating the validity period of the registration of the EAS 64 in the EES 62.

The EAS profile is information about the EAS. Figure 6 shows examples of information elements included in the EAS profile. For example, the EAS profile includes EASID, EAS Endpoint, EAS Geographical Service Area, EAS Topological Service Area, EAS Service KPIs (Key Performance Indicators), List of EAS DNAI(s) (Data Network Access Identifier), List of N6 Traffic Routing requirements, etc.

EASID is identification information of EAS64. EAS Endpoint is endpoint information used for communication with EAS64. The endpoint information may be, for example, a Uniform Resource Identifier (URI), a Fully Qualified Domain Name (FQDN), an IP address, etc. EAS Geographical Service Area may be geographical information related to the service area in which EAS64 provides services. EAS Topological Service Area may be information indicating an area including cells in which UEs provided by EAS64 are located. EAS Service KPIs is information indicating characteristics or features related to the services provided by EAS64.

Figure 7 shows examples of information elements included in the EAS Service KPIs. For example, the EAS Service KPIs include Connection Bandwidth, which indicates the bandwidth for each DNAI or the total bandwidth of all DNAIs associated with the EAS 64. The List of EAS DNAI(s) is list information indicating at least one DNAI associated with the EAS 64. The DNAI is identification information for identifying user plane access to at least one Data Network. The DNAI may be used as identification information for identifying a communication path. For example, the DNAI associated with the EAS 64 may be information identifying a session or path between the EAS 64 and the relay network 300 for accessing the EAS 64. The List of N6 Traffic Routing requirements may be information indicating conditions for routing to the Local part of DN 50 including the EHE 60.

Returning to FIG. 5, EES 62 sends a Response message to EAS 64 (S22). The Response message is sent to EAS 64 as a response message to the request to use the Create EAS Profile service. Alternatively, if an EAS registration request message was sent from EAS 64 to EES 62 in step S21, an EAS registration response message may be sent as the response message.

Next, EES62 uses the Read Connectivity Service of OAM (Operation Administration and Maintenance)_A (S23). OAM is a management device that maintains and operates the Local part of DN50, and the "_A" attached to OAM is the identification information of the OAM. In this disclosure, consider a situation in which Operator A manages OAM_A and Operator B manages OAM_B in Figure 9. OAM_A holds information about devices located in the Local part of DN50 and information about the network configuration. EES62 uses the Read Connectivity Service to obtain information held by OAM_A about the Connectivity Service used by EAS64.

The Connectivity Service is a service provided to enable the EHE 60 and the core network 100 to be connected while ensuring the security of the relay network 300. For example, the Connectivity Service may be a VPN service or a DC service.

The VPN service may be, for example, the L3VPN service described in IETF RFC8299 or the L2VPN service described in IETF RFC8466. The DC service may be, for example, a service that provides a connection to a network established in a station or the like managed by a business operator providing the DC service. The network established in the station or the like may be in a state in which security is ensured as a closed environment network.

Here, we will explain the procedure for setting up a VPN service when a VPN service is used as the Connectivity Service. OAM_A generates VPN service profile information to be set in the gateway device 301. The VPN service profile information may include DNAI_A that identifies the path between the gateway device 301 and the EAS 64. "_A" is identification information that identifies the DNAI. DNAI_A may be determined by OAM_A or in the EAS 64. Alternatively, the VPN service profile information may be associated with DNAI_A. OAM_A sets the VPN service profile information in the gateway device 301.

OAM_B generates VPN service profile information to be set in the gateway device 302. OAM_B is a management device that maintains and operates the 5G core network, and the "_B" added to OAM is OAM identification information. OAM_B holds information about devices placed in the 5G core network and information about the network configuration. The VPN service profile information may include DNAI_B that identifies the path between the gateway device 302 and the UPF 34. Alternatively, the VPN service profile information may be associated with DNAI_B. DNAI_B may be determined in a core network node in the 5G core network. OAM_B sets the VPN service profile information in the gateway device 302.

Here, instead of OAM_B generating the VPN service profile information, OAM_A may generate the VPN service profile information to be set in the gateway device 302 and transmit it to the gateway device 302. OAM_A and OAM_B may share the VPN service profile information and DNAI that they each hold.

Returning to FIG. 5, next, OAM_A sends a Response message including information about the Connectivity Service being used by EAS 64 to EES 62 (S24). The information about the Connectivity Service includes, for example, information indicating whether it is a VPN service or a DC service, and if it is a VPN service, information indicating whether it is an L2VPN service or an L3VPN service. Furthermore, the information about the Connectivity Service includes DNAI identification information that identifies the route between EAS 64 and relay network 300.

Next, EES 62 generates EAS Deployment Information (S25). EAS Deployment Information is information related to EAS that is notified to the core network 100. Specifically, EAS Deployment Information is information that indicates details of the services provided by EAS 64. EES 62 generates EAS Deployment Information by combining the EAS Profile obtained from EAS 64 and information related to Connectivity Service obtained from OAM_A.

Here, using Figure 8, we will explain an example of parameters included in EAS Deployment Information. Items from AF ID to EAS IP address range information included in Figure 8 may be set based on information included in the EAS Profile. Connectivity Service may be set based on information about Connectivity Service obtained from OAM_A.

Here, the parameters included in ConnectivityService are explained. providerIdentifier is, for example, the identifier of the operator managing EHE60. connectivityServiceID is the identifier of the operator providing the Connectivity Service. site is a list of information elements describing the environment connected to or using the Connectivity Service, and may indicate, for example, Provider or Customer. siteIdentifier is an identifier of the Connectivity Service, and may be indicated, for example, as L3VPN-SM (L3VPN-Service Model) or L2VPN-SM. L3VPN-SM and L2VPN-SM indicate the type of VPN service. dnai is an identifier that identifies user plane access from EAS64 to the relay network 300. For example, assume that DNAI_A is set as dnai. "_A" is the identification information of DNAI. routeInfo is route information leading to the gateway device 301 providing the Connectivity Service. The routeProfID is an identifier for the setting information (configuration information) for using the Connectivity Service, and may be indicated as, for example, L3VPN-NM (L3VPN-Network Model) or L2VPN-NM.

Next, the flow of the EAS Deployment Information update process will be explained using Figure 9. First, the EES 62 uses the Nnef_EASDeployment_Create service provided by the NEF 44 (S31). When using the Nnef_EASDeployment_Create service provided by the NEF 44, the EES 62 specifies the EAS Deployment Information generated in the EES 62.

Next, if NEF 44 determines that EES 62 is permitted to send a request message, it uses the Read DNAI service of OAM_B to obtain DNAI from OAM_B (S32). NEF 44 uses the Read DNAI service to obtain information about user plane access to the Connectivity Service for accessing EAS 64, which is held by OAM_B. When using the Read DNAI service, for example, the connectivityServiceID included in the EAS Deployment Information may be specified as information identifying the Connectivity Service for accessing EAS 64.

Next, OAM_B sends a Response message including a DNAI that identifies user plane access to the Connectivity Service for accessing the EAS 64 to the NEF 44 (S33). The Response message includes a DNAI_B that identifies the path to the Connectivity Service for accessing the EAS 64.

Next, NEF44 uses the Read routeProfID service of OAM_B to obtain configuration information for using the Connectivity Service from OAM_B (S34). When using the Read routeProfID service, for example, the connectivityServiceID included in the EAS Deployment Information may be specified.

Next, OAM_B sends a Response message including a routeProfID that identifies configuration information for using the Connectivity Service to the NEF 44 (S35). The Response message may include routeProfID_B as configuration information for using the Connectivity Service to access the EAS 64. The Response message may also include routeInfo_B as route information to a gateway device that provides the Connectivity Service. routeInfo_B is route information to a gateway device that provides the Connectivity Service. The gateway device may be, for example, the gateway device 302 that is located at the edge between the relay network 300 and the UPF 34. routeProfID_B is an identifier of configuration information (configuration information) for using the Connectivity Service, and may be indicated, for example, as L3VPN-NM (L3VPN-Network Model) or L2VPN-NM.

Steps S34 and S35 may be included in the processing of steps S32 and S33. That is, in step S33, NEF44 may receive DNAI_B, routeProfID_B, and routeInfo_B.

Next, NEF44 updates ConnectivityService, which is a parameter included in EAS Deployment Information (S36). Specifically, NEF44 adds information on the 5G core network side to ConnectivityService. Here, the EAS Deployment Information before and after the update will be explained using Figures 10 and 11.

Figure 10 shows the EAS Deployment Information before the update in step S36. The EAS Deployment Information before the update includes a parameter set as site[0] indicating information on the Local part of DN50 side including EHE60 provided by the Provider. Figure 11 shows the EAS Deployment Information after the update in step S36. The EAS Deployment Information after the update includes a parameter set as site[1] indicating information on the Customer side 5G core network side. The information on the Customer side 5G core network side may be, for example, information between the UPF 34 and a gateway device 302 providing a Connectivity Service.

Returning to FIG. 9, next, NEF 44 notifies UDR 46 of the updated EAS Deployment Information using the Nudr_DM_Create service provided by UDR 46 (S37). NEF 44 may notify UDR 46 of the updated EAS Deployment Information by using the Nudr_DM_Create Request service that includes the updated EAS Deployment Information.

Next, UDR46 sends a Nudr_DM_Create Response message to NEF44 as a response message to the use of the Nudr_DM_Create Request service (S38). Next, NEF44 sends a Nnef_EASDeployment_Create Response message to EES62 as a response message to the use of the Nudr_DM_Create Request service in step S31 (S39).

Next, NEF 44 uses the Nnef_EASDeployment_Notify Request service of SMF 42 to notify SMF 42 that the EAS Deployment Information updated in step S36 has been recorded in UDR 46 (S40). Next, SMF 42 sends an Nnef_EASDeployment_Notify Response message to NEF 44 (S41).

After being notified in step S40 that the updated EAS Deployment Information has been recorded in the UDR 46, the SMF 42 may obtain the updated EAS Deployment Information from the UDR 46. When the UE 30 uses the service provided by the EAS 64, the SMF 42 selects a UPF 34 that can connect to the Connectivity Service via DNAI_B and establishes a PDU Session for the UE 30.

As described above, SMF 42 acquires EAS Deployment Information that associates the Connectivity Service connected to EHE 60 with DNAI and route information within the 5G core network. As a result, when UE 30 uses a service provided by EAS 64, SMF 42 selects UPF 34 that can connect to the Connectivity Service via DNAI_B and establishes a PDU Session for UE 30. As a result, UE 30 can connect to EAS 64 via the Connectivity Service, and can use the service provided by EAS 64.

Furthermore, data transfer between the UE 30 and the EAS 64 can be realized without the NEF 44 transmitting information within the core network 100 to the EES 62. In other words, the EAS 64 and the UPF 34 enable data transfer between the UE 30 and the EAS 64 by transferring data to the gateway device 301 and the gateway device 302, respectively. Therefore, the NEF 44 can avoid notifying the EES 62 of network information within the EES 62 core network 100. This makes it possible to prevent the security level in the NEF 44 from being lowered.

FIG. 12 is a block diagram showing an example configuration of a core network node 10 and an edge node 20 (hereinafter referred to as the core network node 10, etc.). Referring to FIG. 12, the core network node 10, etc. includes a network interface 1201, a processor 1202, and a memory 1203. The network interface 1201 may be used to communicate with a network node. The network interface 1201 may include, for example, a network interface card (NIC) that complies with the IEEE 802.3 series. IEEE stands for Institute of Electrical and Electronics Engineers.

The processor 1202 reads out and executes software (computer programs) from the memory 1203 to perform the processing of the core network node 10 and the like described using the flowcharts in the above-mentioned embodiment. The processor 1202 may be, for example, a microprocessor, an MPU, or a CPU. The processor 1202 may include multiple processors.

Memory 1203 is composed of a combination of volatile memory and non-volatile memory. Memory 1203 may include storage located away from processor 1202. In this case, processor 1202 may access memory 1203 via an I/O (Input/Output) interface (not shown).

In the example of FIG. 12, the memory 1203 is used to store a group of software modules. The processor 1202 can read and execute these software modules from the memory 1203 to perform the processing of the core network node 10 and the like described in the above embodiment.

As explained using FIG. 12, each of the processors in the core network nodes 10, etc. in the above-mentioned embodiments executes one or more programs that include a set of instructions for causing a computer to execute the algorithm explained using the drawings.

In the above examples, the program includes instructions (or software code) that, when loaded into a computer, cause the computer to perform one or more functions described in the embodiments. The program may be stored on a non-transitory computer-readable medium or tangible storage medium. By way of example and not limitation, computer-readable medium or tangible storage medium may include random-access memory (RAM), read-only memory (ROM), flash memory, solid-state drive (SSD) or other memory technology, CD-ROM, digital versatile disc (DVD), Blu-ray® disk or other optical disk storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage device. The program may be transmitted on a transitory computer-readable medium or communication medium. By way of example and not limitation, transitory computer-readable medium or communication medium may include electrical, optical, acoustic, or other forms of propagated signals.

The present disclosure has been described above with reference to the embodiments, but the present disclosure is not limited to the above-mentioned 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.

The drawings are merely examples for describing one or more embodiments. Each drawing may relate not only to one particular embodiment, but also to one or more other embodiments. As will be appreciated by those skilled in the art, various features or steps described with reference to any one drawing may be combined with features or steps shown in one or more other figures to create, for example, an embodiment not explicitly shown or described. Not all features or steps shown in any one drawing are necessarily required to describe an exemplary embodiment, and some features or steps may be omitted. The order of steps described in any drawing may be changed as appropriate.

Some or all of the above embodiments can be described as follows, but are not limited to the following:

(Appendix 1)
receiving means for receiving, from a first edge node in an edge computing environment, first path information regarding a first communication path between an edge application server in the edge computing environment and the edge node;
A generating means for generating second route information relating to a second communication route between a second edge node in a core network and a first core network node, and information associating the second route information with the first route information;
A core network node comprising:
(Appendix 2)
The first route information is a Data Network Access Identifier (DNAI) used in the edge computing environment,
The second route information is a Data Network Access Identifier (DNAI) used in the core network.
2. A core network node as described in Supplementary Note 1.
(Appendix 3)
The receiving means further receives identification information of a connection service provided in a relay network between the core network and the edge computing environment.
3. A core network node according to claim 1 or 2.
(Appendix 4)
4. The core network node of claim 3, wherein the connection service is a Virtual Private Network (VPN) service.
(Appendix 5)
The core network node according to claim 3, wherein the connection service is a Data Center (DC) service.
(Appendix 6)
6. The core network node according to any one of claims 1 to 5, further comprising a transmitting means for transmitting the association information to a data management node in the core network.
(Appendix 7)
The generating means includes:
7. A core network node according to any one of claims 1 to 6, further comprising: a network management node in the core network for acquiring the first route information associated with the association information from the network management node in the core network.
(Appendix 8)
receiving, from a first edge node in an edge computing environment, first path information regarding a first communication path between an edge application server in the edge computing environment and the edge node;
A data generation method for generating information associating second route information regarding a second communication route between a second edge node in a core network and a first core network node with the first route information.
(Appendix 9)
The first route information is a Data Network Access Identifier (DNAI) used in the edge computing environment,
The second route information is a Data Network Access Identifier (DNAI) used in the core network.
9. The data generation method according to claim 8.
(Appendix 10)
and upon receiving the first path, further receiving an identification of a connectivity service provided in a relay network between the core network and the edge computing environment.
10. The data generation method according to claim 8 or 9.
(Appendix 11)
The data generation method according to claim 9, wherein the connection service is a Virtual Private Network (VPN) service.
(Appendix 12)
The data generation method according to claim 9, wherein the connection service is a DC (Data Center) service.
(Appendix 13)
13. The data generation method according to any one of claims 8 to 12, further comprising transmitting the association information to a data management node in the core network.
(Appendix 14)
The data generation method according to any one of Supplementary claims 8 to 13, wherein, when generating the association information, the first route information is obtained from a network management node in the core network.
(Appendix 15)
receiving, from a first edge node in an edge computing environment, first path information regarding a first communication path between an edge application server in the edge computing environment and the edge node;
A program that causes a computer to execute the following: generating second route information regarding a second communication route between a second edge node in a core network and a first core network node, and association information between the first route information.
(Appendix 16)
an edge node in an edge computing environment;
a core network node in a core network;
A communication system comprising:
The edge node:
Sending to the core network node first route information regarding a first communication route between an edge application server in the edge computing environment and the edge node;
The core network node:
receiving the first route information;
generating association information between second route information regarding a second communication route between a first edge node in the core network and a first core network node and the first route information;
Communication systems.

Some or all of the elements (e.g., configurations and functions) described in Supplementary Notes 9 to 14 that are dependent on Supplementary Note 8 may also be dependent on Supplementary Note 15 in a similar dependent relationship to Supplementary Notes 9 to 14. Some or all of the elements described in any of the supplementary notes may be applied to various hardware, software, recording means for recording software, systems, and methods.

This application claims priority based on Japanese Patent Application No. 2023-46511, filed March 23, 2023, the entire disclosure of which is incorporated herein by reference.

10 Core network node 11 Receiver 12 Data generator 20 Edge node 30 UE
32 AN
34 UPF
40 AMF
42 SMF
44 NEF
46 UDR
48 PCF
50 Local part of DN
60 EHE
62 EES
64 EAS
100 Core network 200 Edge computing environment 300 Relay network 301 Gateway device 302 Gateway device

Claims (20)

receiving means for receiving, from a first edge node in an edge computing environment, first path information regarding a first communication path between an edge application server in the edge computing environment and the edge node;
A generating means for generating second route information relating to a second communication route between a second edge node in a core network and a first core network node, and information associating the second route information with the first route information;
A core network node comprising: The first route information is a Data Network Access Identifier (DNAI) used in the edge computing environment,
The second route information is a Data Network Access Identifier (DNAI) used in the core network.
A core network node as claimed in claim 1. The receiving means further receives identification information of a connection service provided in a relay network between the core network and the edge computing environment.
A core network node according to claim 1 or 2. The core network node of claim 3, wherein the connection service is a VPN (Virtual Private Network) service. The core network node according to claim 3, wherein the connection service is a DC (Data Center) service. The core network node according to claim 1 or 2, further comprising a transmission means for transmitting the association information to a data management node in the core network. The generating means includes:
The core network node according to claim 1 , further comprising: a network management node in the core network, configured to acquire the first route information associated with the association information from the network management node in the core network. receiving, from a first edge node in an edge computing environment, first path information regarding a first communication path between an edge application server in the edge computing environment and the edge node;
A data generation method for generating information associating second route information regarding a second communication route between a second edge node in a core network and a first core network node with the first route information. The first route information is a Data Network Access Identifier (DNAI) used in the edge computing environment,
The second route information is a Data Network Access Identifier (DNAI) used in the core network.
The data generating method according to claim 8. When receiving the first route information, further receiving an identification of a connectivity service provided in a relay network between the core network and the edge computing environment.
The data generating method according to claim 8 or 9. The data generation method according to claim 10, wherein the connection service is a VPN (Virtual Private Network) service. The data generation method according to claim 10, wherein the connection service is a DC (Data Center) service. The data generation method according to any one of claims 8 to 12, wherein the association information is transmitted to a data management node in the core network. The data generation method according to any one of claims 8 to 13, wherein when generating the association information, the first route information is obtained from a network management node in the core network. receiving, from a first edge node in an edge computing environment, first path information regarding a first communication path between an edge application server in the edge computing environment and the edge node;
A program that causes a computer to execute the following: generating second route information regarding a second communication route between a second edge node in a core network and a first core network node, and association information between the first route information. The first route information is a Data Network Access Identifier (DNAI) used in the edge computing environment,
The second route information is a Data Network Access Identifier (DNAI) used in the core network.
The program according to claim 15. When receiving the first route information, further receiving an identification of a connectivity service provided in a relay network between the core network and the edge computing environment.
17. The program according to claim 15 or 16. The program according to claim 17, wherein the connection service is a VPN (Virtual Private Network) service. The program according to claim 17, wherein the connection service is a DC (Data Center) service. an edge node in an edge computing environment;
a core network node in a core network;
A communication system comprising:
The edge node:
Sending to the core network node first route information regarding a first communication route between an edge application server in the edge computing environment and the edge node;
The core network node:
receiving the first route information;
generating association information between second route information regarding a second communication route between a first edge node in the core network and a first core network node and the first route information;
Communication systems.

Images