First core network node, second core network node, method, and program

Abstract

The purpose of the present disclosure is to provide a first core network node capable of accurately recognizing the state of a function enabled by an NF when providing a communication service. A first core network node according to the present disclosure comprises a control unit that enables or disables at least one function to be supported, and a communication unit that transmits, to a second core network node, state information indicating whether the at least one function is enabled or disabled.

Description

First core network node, second core network node, method and program

[0001] The present disclosure relates to a first core network node, a second core network node, a method, and a program.

[0002] The 3GPP (3rd Generation Partnership Project) (registered trademark), which develops communication standards for mobile networks, is considering wireless communication standards for 5G (5th Generation) and communication standards for 5GC (5G Core network) that support 5G.

[0003] 5GC uses a Service Based Architecture (SBA). In SBA, each Network Function (NF) communicates via an API. Each NF provides APIs related to multiple NF services. Each NF uses the NF services via the provided APIs. NFs include nodes that control the Control Plane (C-Plane), such as the Access and Mobility Management Function (AMF) and the Session Management Function (SMF), and nodes that control the User Plane (U-Plane), such as the User Plane Function (UPF). Here, integrating a UPF, which is a node that controls the U-Plane, into an SBA related to the C-Plane is being considered. Furthermore, a UPF selection method (UPF selection) in which an SMF selects a UPF integrated into an SBA is also being considered.

[0004] In UPF selection, the SMF selects a UPF that provides a function or a group of functions (hereinafter simply referred to as "functions") required by the SMF. Non-Patent Document 1 discloses a list of functions provided by UPFs. Examples of functions provided by UPFs include NAT (Network Address Translation) and packet inspection. The SMF extracts a UPF that has the required functions via an NRF (Network Repository Function), which is a node that provides information on functions provided by UPFs. The NRF is assumed to manage an NF Profile that indicates the functions of the NF, including the UPF.

[0005] 3GPP TS 23.501 V18.4.0 (2023-12)

[0006] The NF Profile lists the functions supported by each NF. The UPF can enable or disable each supported function. Therefore, if an SMF selects a UPF that supports a required function but disables the function, the SMF cannot use the required function, resulting in a problem in which the desired communication service cannot be provided.

[0007] In view of the above-mentioned problems, the object of the present disclosure is to provide a first core network node, a second core network node, a method, and a program that can accurately recognize the status of functions that an NF has set to enabled or disabled when providing communication services.

[0008] A first core network node according to the present disclosure comprises a control unit that enables or disables at least one function that it supports, and a communication unit that transmits status information indicating whether the at least one function is enabled or disabled to a second core network node.

[0009] The second core network node of the present disclosure includes a communication unit that requests status information from the first core network node indicating whether at least one function supported by the first core network node is enabled or disabled, and the communication unit receives the status information in response to the request.

[0010] The method of the present disclosure is performed in a first core network node that manages state information indicating whether at least one feature that it supports is enabled or disabled, and transmits the state information to a second core network node.

[0011] The program of the present disclosure causes a computer to manage status information indicating whether at least one supported function is enabled or disabled, and to transmit the status information to a second core network node.

[0012] The present disclosure provides a first core network node, a second core network node, a method, and a program that can accurately recognize the status of functions enabled by an NF when providing a communication service.

[0013] FIG. 1 shows an example of the configuration of a core network node. FIG. 2 shows an example of the configuration of a core network node. FIG. 3 shows a diagram illustrating the flow of communication processing executed in a core network node. FIG. 4 shows a diagram illustrating the flow of communication processing executed in a core network node. FIG. 5 shows an example of the configuration of a communication system in 5GC. FIG. 6 shows a diagram illustrating the flow of processing related to the Nnrf_NFManagement service. FIG. 7 shows a diagram illustrating the flow of communication processing executed in a UPF. FIG. 8 shows a diagram illustrating the flow of processing related to the Nnrf_NFDiscovery service. FIG. 9 shows the flow of processing related to the Nupf_RunningFunctionalities service. FIG. 10 shows a diagram illustrating the flow of status information update processing executed in a UPF. FIG. 11 shows a diagram illustrating the flow of status information reception processing executed in an SMF. FIG. 12 shows a diagram illustrating the flow of a PDU session establishment procedure. FIG. 13 is a block diagram illustrating example configurations of a core network node, an edge node, a UPF, and an SMF.

[0014] (First embodiment) First, a core network node 10 will be described. Fig. 1 shows an example of the configuration of the core network node 10. The core network node 10 may be, for example, a node constituting 5GC defined in 3GPP. The node may correspond to an entity (device) or a function. The core network node 10 may be a computer device that operates by a processor executing a program stored in a memory.

[0015] The core network node 10 has a control unit 11 and a communication unit 12. The control unit 11 and the communication unit 12 may be software or modules that perform processing by a processor executing a program stored in a memory. Alternatively, the control unit 11 and the communication unit 12 may be hardware such as a circuit or a chip. The control unit 11 may be used as control means for controlling processing and the like performed in the core network node 10. The communication unit 12 may be used as receiving means for receiving information or data.

[0016] The control unit 11 enables or disables at least one function supported by the core network node 10. The at least one function supported by the core network node 10 may be rephrased as at least one function installed in the core network node 10 or at least one function possessed by the core network node 10.

[0017] A function may be a single function or a function realized by combining multiple functions. A function may also be a function group including multiple functions. In the following description, a function also includes a function group.

[0018] The functions supported by the core network node 10 may be functions related to communication, functions related to data processing, functions related to data management, etc. The communication functions may be, for example, a data forwarding function, specifically, a NAT function, etc. For example, the data processing functions may be a packet analysis function, specifically, a packet inspection function. The data management functions may be, for example, the execution of various network policies and user policies, specifically, a function related to the User Plane part of policy rule enforcement.

[0019] Enabling a function may mean putting the function into an executable state. Enabling a function may also be rephrased as putting the function into an ON state, an active state, a started state, etc. Disabling a function may also be put into an inexecutable state. Disabling a function may also be rephrased as putting the function into an OFF state, an inactive state, a stopped state, a terminated state, etc.

[0020] The control unit 11 may enable a disabled function, or may disable a enabled function. The control unit 11 may enable or disable multiple functions collectively, or may enable or disable functions individually.

[0021] The communication unit 12 transmits state information indicating whether at least one function is enabled or disabled to the core network node 20. The state information may be information indicating whether each function is enabled or disabled. The state information may also be flag information indicating whether each function is enabled or disabled.

[0022] The core network node 20 is a node different from the core network node 10. The core network node 10 and the core network node 20 may be connected via a network. Furthermore, the core network node 10 and the core network node 20 may be NFs constituting an SBA. The core network node 10 and the core network node 20 may be nodes whose specifications are defined in 3GPP, such as AMF, SMF, NRF, and UPF.

[0023] The communication unit 12 may transmit the state information periodically or autonomously at any timing to the core network node 20. Alternatively, the communication unit 12 may transmit the state information to the core network node 20 when requested by the core network node 20 to transmit the state information.

[0024] Next, a description will be given of the core network node 20. Fig. 2 shows an example configuration of the core network node 20. The core network node 20 may be a computer device that operates by a processor executing a program stored in a memory.

[0025] The core network node 20 includes a communication unit 21. The communication unit 21 may be software or a module that performs processing by a processor executing a program stored in a memory. Alternatively, the communication unit 21 may be hardware such as a circuit or a chip. The communication unit 21 may be used as a receiving means for receiving information or data.

[0026] The communication unit 21 requests state information indicating whether at least one function supported by the core network node 10 is enabled or disabled from the core network node 10. The request may be, for example, the communication unit 21 transmitting a request message.

[0027] Furthermore, the communication unit 21 receives the state information as a response to a request for state information from the core network node 10. The communication unit 21 may receive a response message including the state information.

[0028] Next, a description will be given of a communication method executed in the core network node 10. FIG.

[0029] First, the control unit 11 manages status information indicating whether at least one supported function is enabled or disabled (S11). For example, the control unit 11 may manage the status of the function after enabling or disabling the function. Next, the communication unit 12 transmits the status information to the core network node 20 (S12).

[0030] Next, a description will be given of a communication method executed in the core network node 20. FIG.

[0031] First, the communication unit 21 requests the core network node 10 for state information indicating whether at least one function supported by the core network node 10 is enabled or disabled (S21). Next, the communication unit 21 receives the state information as a response to the request (S22).

[0032] As described above, the core network node 10 can transmit, to the core network node 20, status information indicating whether at least one function supported by the core network node 10 is enabled or disabled. That is, the core network node 10 can expose status information of at least one function supported by the core network node 10 to the core network 20. Furthermore, this allows the core network node 20 to recognize not only that the core network node 10 supports a certain function, but also whether the function is enabled or disabled.

[0033] As a result, the core network node 20 can provide the desired communication service using the core network node 10 in which the requested function is enabled.

[0034] (Embodiment 2) Figure 5 shows an example of the configuration of a communication system in 5GC. The communication system in Figure 5 has a UPF 30, an SMF 40, and an NRF 50. The UPF 30, the SMF 40, and the NRF 50 each correspond to a node. Furthermore, the UPF 30, the SMF 40, and the NRF 50 correspond to NFs constituting 5GC. The UPF 30 corresponds to the core network node 10 in Figure 1. The SMF 40 corresponds to the core network node 20 in Figure 2.

[0035] The UPF 30, the SMF 40, and the NRF 50 are configured with an SBA and are connected to each other via a Service Based Interface (SBI). For example, the HyperText Transfer Protocol (HTTP) may be used in the SBI. For example, Nupf, Nsmf, and Nnrf are defined in the SBI.

[0036] The communication system shown in Figure 5 also shows that the UPF 30 is integrated into the SBA. That is, in the communication system shown in Figure 5, NFs such as the SMF 40 and NRF 50 can access or acquire information managed by the UPF 30 via Nupf. That is, NFs such as the SMF 40 and NRF 50 can use services provided by the UPF 30 via Nupf. Furthermore, the UPF 30 can use services provided by the SMF 40 or NRF 50 via Nsmf or Nnrf.

[0037] The UPF 30 serves as an anchor point in the 5G system, terminating a PDU (Protocol Data Unit) session and interconnecting with an external network. The UPF 30 transfers user plane data.

[0038] The SMF 40 manages PDU sessions. Furthermore, the SMF 40 selects a UPF when establishing or configuring a PDU session. When selecting a UPF, the SMF 40 may select a UPF based on the functions supported by the UPF and whether or not the functions are enabled. For example, the SMF 40 may select a UPF that has the functions required to establish a PDU session and has the functions enabled from among at least one UPF. To select a UPF, the SMF 40 needs to recognize, for example, the functions supported by the UPF and whether or not the functions supported by the UPF are enabled.

[0039] The NRF 50 provides a function for the NFs in the 5GC to discover services. The services may be services provided by each NF via an API. The NRF 50 manages the functions supported by each NF and the services provided by each NF. The NRF 50 may be used as a database that holds the functions supported by each NF and the services provided by each NF. Holding may be rephrased as storing, memorizing, or recording.

[0040] Next, a process of registering functions supported by an NF in the NRF 50 will be described. Fig. 6 shows a process flow related to the Nnrf_NFManagement service. The Nnrf_NFManagement service may be a service that enables an NF to have the NRF 50 manage an NF profile. An NF having the NRF 50 manage an NF profile may mean registering an NF profile in the NRF 50, updating an NF profile registered in the NRF 50, or deleting an NF profile registered in the NRF 50.

[0041] Furthermore, the Nnrf_NFManagement service may be a service that notifies the changed NF profile when a change occurs in the NF profile. Fig. 6 shows an example in which the UPF 30 registers the NF profile of the UPF 30 in the NRF 50.

[0042] First, the UPF 30 notifies the NRF 50 of the NF Profile in the UPF 30 by using the Nnrf_NFManagement service (S31). Specifically, the UPF 30 may notify the NRF 50 of the NF Profile by using the Nnrf_NFManagement_NFRegister Request service. The NRF 50 holds the NF Profile in the UPF 30.

[0043] The NF profile may include, for example, an NF type, an NF instance ID, an FQDN (Fully Qualified Domain Name) or IP address of the NF, and names of functions supported by the NF. Furthermore, the NF profile may include information indicating that the NF supports a service for notifying other NFs of status information indicating whether the functions supported by the NF are enabled or disabled. The information indicating that the NF supports a service for notifying other NFs of status information may be capability information indicating that the NF is capable of notifying other NFs of status information.

[0044] The NF type may be information that specifies the type of node. The NF type may be information that indicates, for example, UPF, SMF, NRF, etc. The information used for the NF type may be a method of indicating any one of a plurality of nodes that are managed in advance in a list. The NF type may be information that indicates a network function or a network entity included in 5GC. The NF type may be, for example, string type information. For example, the information that indicates a network function or a network entity included in 5GC set in the NF type may be "NRF", "UDM", "AMF", "SMF", "AUSF", "NEF", "PCF", "SMSF", "NSSF", "UDR", "LMF", "GMLC", "5G_EIR", "SEPP", "UPF", "N3IWF", "AF", "UDSF", "BSF", "CHF", "NWDAF", "PCSCF", "CBCF", "UCMF", "HSS", "SOR_AF", "SPAF", "MME", "SCSAS", "SCEF", Examples of NF instance IDs include "SCP", "NSSAAF", "ICSCF", "SCSCF", "DRA", "IMS_AS", "AANF", "5G_DDNMF", "NSACF", "MFAF", "EASDF", "DCCF", "MB_SMF", "TSCTSF", "ADRF", "GBA_BSF", "CEF", "MB_UPF", "NSWOF", "PKMF", "MNPF", "SMS_GMSC", "SMS_IWMSC", "MBSF", "MBSTF", "PANF", "DCSF", "MRF", "MRFP", "MF", and "SLPKMF". The NF instance ID may be identification information of a node. For example, if the NF is a UPF, the name of the function supported by the NF may be the name of a function such as NAT or packet inspection. The name of the function supported by the NF may be the name of at least one of a plurality of function names managed in a list in advance.The NF UPF has many functions other than NAT and packet inspection, and the names of the functions supported by the NF UPF that are included in the NF Profile are not limited to NAT and packet inspection.

[0045] The status information may be treated as information different from the names of the functions supported by the NF, or may be treated as information included in the names of the functions supported by the NF. The information included in the names of the functions supported by the NF may, for example, be associated with information indicating whether each function supported by the NF is enabled or disabled. The information indicating whether a function is enabled or disabled may, for example, be either a flag indicating enabled or disabled.

[0046] Alternatively, the status information may be information indicating a list of functions that are in an enabled state or a list of functions that are in an disabled state, as information different from the names of functions supported by the NF. Alternatively, the status information may be information indicating a list of functions that are in an enabled state and a list of functions that are in an disabled state, as information different from the names of functions supported by the NF.

[0047] 7 is a diagram showing the flow of communication processing executed in the UPF 30. First, the control unit 11 manages information indicating whether at least one supported function is enabled or disabled (S41). Next, the communication unit 12 notifies the NRF 50 that it has a service that notifies status information (S42). The NRF 50 manages information that the UPF 30 has a service that notifies status information.

[0048] Next, a process in which the SMF 40 acquires information about a UPF will be described. Fig. 8 shows a process flow related to the Nnrf_NFDiscovery service. The Nnrf_NFDiscovery service may be a process in which an NF discovers at least one other NF that supports a specific function or a specific service. "Discover" may also be referred to as "searching," "extracting," etc. Fig. 8 shows an example in which the SMF 40 discovers at least one UPF that supports a specific function.

[0049] First, the SMF 40 uses the Nnrf_NFDiscovery Request service to request the NRF 50 to discover at least one UPF that supports a service that notifies status information (S51). In the Nnrf_NFDiscovery Request service, the SMF 40 may set or specify, for example, the NF type, the name of the target function, and support for the service that notifies status information. Here, the SMF 40 sets UPF as the NF type. The SMF 40 may also set at least one of NAT and packet inspection as the name of the target function. Alternatively, the SMF 40 may set both NAT and packet inspection as the name of the target function. Furthermore, in addition to NAT and / or packet inspection, the SMF 40 may also set one or more functions other than NAT and packet inspection as the name of the target function. Furthermore, the SMF 40 may also set one or more functions other than NAT and packet inspection as the name of the target function.

[0050] Next, the NRF 50 performs a process of discovering a UPF that matches the conditions requested by the SMF 40 (S52). The discovery process may be referred to as a search process or an extraction process. Specifically, the NRF 50 identifies at least one UPF that supports a service that notifies status information among multiple UPFs that support the function targeted by the SMF 40. Alternatively, the NRF 50 identifies whether or not a UPF that supports a service that notifies status information exists among multiple UPFs that support the function targeted by the SMF 40.

[0051] Next, the NRF 50 notifies the SMF 40 of the result of the discovery process or the search result (S53). The result of the discovery process may be, for example, information including identification information of at least one identified UPF. The identification information may be information indicating the name of the UPF, or the FQDN or IP address of the UPF. Assume that the at least one identified UPF includes the UPF 30. The NRF 50 may send an Nnrf_NFDiscovery Response message to the SMF 40 as a response message to the use of the Nnrf_NFDiscovery Request service. Alternatively, the NRF 50 may notify the SMF 40 of the result of the discovery process as output information (output) to the use of the Nnrf_NFDiscovery Request service.

[0052] 9 shows the flow of processing related to the Nupf_RunningFunctionalities service. The Nupf_RunningFunctionalities service may be a service by which the NF notifies status information indicating whether the functions supported in the UPF are enabled or disabled.

[0053] First, the SMF 40 requests notification of status information of functions supported by the UPF 30 by using the Nupf_RunningFunctionalities Subscribe service (S61). For example, the SMF 40 may set or specify, in the Nupf_RunningFunctionalities Subscribe service, identification information of the SMF 40 to which the status information is to be notified or a uniform resource identifier (URI) to which the status information is to be notified. For example, the SMF 40 may determine, in the Nupf_RunningFunctionalities Subscribe service, whether to request (subscribe) or not request (unsubscribe) notification of status information from at least one UPF among multiple UPFs identified by the Nnrf_NFDiscovery service. The multiple UPFs are multiple UPFs that support functions targeted by the SMF 40. At least one UPF among the multiple UPFs is a UPF that supports a service that notifies status information of functions supported by the UPF. The SMF 40 may notify at least one UPF determined to subscribe that it requests notification of status information of functions supported in the UPF. The SMF 40 may notify at least one UPF determined not to request notification of status information of functions supported in the UPF.

[0054] Next, the UPF 30 transmits a Response message to the SMF 40 as a response message to the use of the Nupf_RunningFunctionalities Subscribe service (S62). The Response message may include current status information of the functions supported by the UPF 30. For example, when the UPF 30 receives a notification from the SMF 40 requesting (subscribing) notification of status information of the functions supported by the UPF, the UPF 30 may transmit a Response message including current status information of the functions supported by the UPF 30 to the SMF 40. For example, when the UPF 30 receives a notification from the SMF 40 not requesting (unsubscribe) notification of status information of the functions supported by the UPF, the UPF 30 may not need to transmit a Response message.

[0055] Next, when a change occurs in the state information, the UPF 30 notifies the SMF 40 of the changed state information by using the Nupf_RunningFunctionalities Notify service (S63). A change in the state information may occur when a function supported by the UPF 30 is changed from an enabled state to an disabled state, or when a function is changed from a disabled state to an enabled state. There may be multiple states, for example, state 1 (disabled) ⇔ state 2 (being set) ⇔ state 3 (enabled). For example, when the UPF 30 receives a notification from the SMF 40 requesting (subscribing) notification of state information of functions supported by the UPF, the UPF 30 may notify the SMF 40 of the changed state information when a change occurs in the state information. For example, if UPF 30 receives a notification from SMF 40 indicating that it does not request (unsubscribe from) notification of status information of functions supported by the UPF, when a change occurs in the status information, UPF 30 does not need to notify SMF 40 of the changed status information.

[0056] The SMF 40 receives the Response message in step S62 and further receives a notification indicating update of the status information in step S62, thereby being able to recognize the latest status of the functions supported by the UPF 30.

[0057] 10 is a diagram showing the flow of the state information update process executed in the UPF 30. First, the communication unit 12 receives a request for notification of state information held by the UPF 30 from the SMF 40 using the Nupf_RunningFunctionalities Subscribe service (S71). Next, the communication unit 12 transmits a Response message including current state information of the UPF 30 to the SMF 40 (S72). For example, when the communication unit 12 receives a request (subscribe) for notification of state information held by the UPF 30 using the Nupf_RunningFunctionalities Subscribe service from the SMF 40, the communication unit 12 may transmit a Response message including current state information of the UPF 30 to the SMF 40. For example, when the communication unit 12 receives from the SMF 40 a request (unsubscribe) to notify the status information held by the UPF 30 using the Nupf_RunningFunctionalities Subscribe service, the communication unit 12 does not need to send a Response message including the current status information of the UPF 30 to the SMF 40.

[0058] Next, the control unit 11 determines whether a change has occurred in the state information (S73). If the control unit 11 determines that a change has occurred in the state information, the communication unit 12 notifies the SMF 40 of the changed state information (S74). Specifically, the communication unit 12 notifies the SMF 40 of the changed state information by using the Nupf_RunningFunctionalities Notify service. The communication unit 12 may notify only the state information related to the function in which a change has occurred, or may notify the state information related to the function in which a change has occurred together with the state information related to the function in which no change has occurred. For example, if the communication unit 12 receives a request (subscribe) from the SMF 40 to be notified of the state information held by the UPF 30 using the Nupf_RunningFunctionalities Subscribe service, and if the control unit 11 determines that a change has occurred in the state information, the communication unit 12 may notify the SMF 40 of the state information related to the function in which a change has occurred. For example, when the communication unit 12 receives from the SMF 40 an instruction (unsubscribe) to not request notification of the status information held by the UPF 30 using the Nupf_RunningFunctionalities Subscribe service, if the control unit 11 determines that a change has occurred in the status information, the communication unit 12 does not need to notify the SMF 40 of the status information regarding the function in which the change has occurred.

[0059] 11 is a diagram showing the flow of a state information reception process executed in the SMF 40. First, the communication unit 21 requests notification of state information held by the UPF 30 using the Nupf_RunningFunctionalities Subscribe service (S81). For example, the communication unit 21 may notify (subscribe) that notification of state information held by the UPF 30 is requested using the Nupf_RunningFunctionalities Subscribe service. For example, the communication unit 12 may notify (unsubscribe) that notification of state information held by the UPF 30 is not requested using the Nupf_RunningFunctionalities Subscribe service.

[0060] Next, the communication unit 21 receives a Response message including current state information of the UPF 30 as a response to the request in step S81 (S82). Next, the communication unit 21 receives notification of state information that has changed in the UPF 30 by using the Nupf_RunningFunctionalities Notify service (S83). For example, when the communication unit 12 notifies (subscribes) to request notification of state information held by the UPF 30 by using the Nupf_RunningFunctionalities Subscribe service, the communication unit 21 may receive a Response message including current state information of the UPF 30. Furthermore, the communication unit 21 may receive notification of state information that has changed in the UPF 30 by using the Nupf_RunningFunctionalities Notify service.

[0061] As described above, the UPF 30 manages whether each function it supports is enabled or disabled. Furthermore, the UPF 30 notifies the SMF 40 of its status information in response to a request from the SMF 40. As a result, for example, when establishing a PDU session, the SMF 40 can select a UPF in which the required function is enabled and establish the PDU session. Specifically, the SMF 40 can determine whether the required function is enabled by obtaining status information through the Nupf_RunningFunctionalities Notify service. Furthermore, the UPF 30 can notify the SMF 40 of status information (enabled, disabled, setting, etc.) of each function supported by the UPF 30 as a UPF Event Exposure Service. Furthermore, the SMF 40 can request (subscribe) or not request (unsubscribe) status information of each function supported by the UPF 30. Furthermore, the UPF 30 using the container technology can support an interface that can automatically transmit the status of the functions supported by the UPF 30 to the SMF 40. By supporting an interface that can automatically transmit the status of the functions supported by the UPF 30 to the SMF 40, the SMF 40 can grasp the status of the UPF 30 and select an appropriate UPF.

[0062] FIG. 12 is a diagram showing the flow of a PDU session establishment procedure when a communication device (User Equipment (UE)) requests the establishment of a new PDU (Packet Data Unit) session.

[0063] First, the communication device transmits a PDU Session Establishment Request message to the AMF (Step 1). For example, the PDU Session Establishment message may include S-NSSAI (Single-Network Slice Selection Assistance Information), UE Requested DNN (Data Network Name), PDU Session ID, Request type, Old PDU Session ID, N1 SM container (PDU Session Establishment Request, [Port Management Information Container]).

[0064] Next, the AMF that receives the PDU session establishment message selects an SMF (Step 2).

[0065] Next, the SMF selects a UPF (Step 8). The SMF may select a UPF based on the status information of functions supported in the UPF obtained by using the Nupf_RunningFunctionalities Subscribe service. For example, the SMF may select a UPF for which the status information of functions supported in the UPF is valid. For example, the SMF may select a UPF by taking into account the S-NSSAI and the UE Requested DNN as well as whether the status information of functions supported in the UPF is valid. Finally, the SMF sends a PDU Session Establishment Accept message to the communication terminal via the AMF (Steps 11-13).

[0066] Fig. 13 is a block diagram showing an example configuration of a core network node 10, an edge node 20, a UPF 30, and an SMF 40 (hereinafter referred to as core network nodes 10, etc.). Referring to Fig. 13, 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 network nodes. The network interface 1201 may include, for example, a network interface card (NIC) compliant with the IEEE 802.3 series. IEEE stands for Institute of Electrical and Electronics Engineers.

[0067] The processor 1202 reads 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. The processor 1202 may be, for example, a microprocessor, an MPU, or a CPU. The processor 1202 may include multiple processors.

[0068] The memory 1203 is configured by a combination of volatile memory and non-volatile memory. The memory 1203 may include storage located remotely from the processor 1202. In this case, the processor 1202 may access the memory 1203 via an I / O (Input / Output) interface (not shown).

[0069] 13, the memory 1203 is used to store software modules. The processor 1202 reads and executes these software modules from the memory 1203, thereby performing processing of the core network node 10, etc.

[0070] As described with reference to the figures, each of the processors included in the core network node 10, etc. executes one or more programs containing instructions for causing a computer to perform the algorithms described with reference to the figures.

[0071] 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 a tangible storage medium. By way of example and not limitation, computer-readable medium or tangible storage medium includes 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 disc or other optical disk storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage device. The program may also 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 includes electrical, optical, acoustic, or other forms of propagated signals.

[0072] 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.

[0073] Each drawing is merely an example for describing one or more embodiments. Each drawing may not relate to only one particular embodiment, but may also relate to one or more other embodiments. As will be understood by those skilled in the art, various features or steps described with reference to any one drawing can be combined with features or steps shown in one or more other drawings to create, for example, an embodiment not explicitly shown or described. Not all features or steps shown in any one drawing are necessary 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.

[0074] Some or all of the above embodiments can be described as, but are not limited to, the following supplementary notes. (Supplementary Note 1) A first core network node comprising: a control unit that enables or disables at least one function that it supports; and a communication unit that transmits state information indicating whether the at least one function is enabled or disabled to a second core network node. (Supplementary Note 2) The first core network node according to Supplementary Note 1, wherein the communication unit transmits the state information to the second core network node when the second core network node requests the state information. (Supplementary Note 3) The first core network node according to Supplementary Note 2, wherein the communication unit notifies the second core network node that a state of the at least one function has changed from an enabled state to an disabled state, or from an disabled state to an enabled state. (Supplementary Note 4) The first core network node according to any one of Supplements 1 to 3, wherein the communication unit registers capability information indicating that the state information can be transmitted to an information providing device that provides information to the second core network node. (Supplementary Note 5) The first core network node according to Supplementary Note 4, wherein the at least one function is information included in an NF profile managed by an NRF, which is the information providing device. (Supplementary Note 6) The first core network node according to Supplementary Note 5, wherein the at least one function is a function supported by a UPF. (Supplementary Note 7) The first core network node according to Supplementary Note 5 or 6, wherein the at least one function includes at least one of NAT and Packet Inspection. (Supplementary Note 8) A second core network node comprising a communication unit that requests, from the first core network node, state information indicating whether at least one function supported by the first core network node is enabled or disabled, wherein the communication unit receives the state information in a response to the request. (Supplementary Note 9) The second core network node according to Supplementary Note 8, wherein the communication unit receives information indicating that a state of the at least one function has changed from an enabled state to an disabled state or from an disabled state to an enabled state.(Supplementary Note 10) The second core network node according to Supplementary Note 8 or 9, wherein the communication unit receives, from an information providing device, information indicating at least one of the first core network nodes to which the state information can be transmitted. (Supplementary Note 11) The second core network node according to Supplementary Note 10, wherein the at least one function is information included in an NF profile managed by an NRF that is the information providing device. (Supplementary Note 12) The second core network node according to Supplementary Note 11, wherein the at least one function is a function supported by a UPF. (Supplementary Note 13) The second core network node according to Supplementary Note 11 or 12, wherein the at least one function includes at least one of NAT and Packet Inspection. (Supplementary Note 14) A method executed in a first core network node, managing state information indicating whether at least one supported function is enabled or disabled, and transmitting the state information to a second core network node. (Supplementary Note 15) A method executed in a second core network node, requesting state information indicating whether at least one function supported by a first core network node is enabled or disabled from the first core network node, and receiving the state information in response to the request. (Supplementary Note 16) The method of Supplementary Note 15, selecting the first core network node in which a required function is enabled when establishing a PDU (Protocol Data Unit) session after receiving the state information. (Supplementary Note 17) A program causing a computer to manage state information indicating whether at least one function supported is enabled or disabled, and transmitting the state information to a second core network node. (Supplementary Note 18) A program causing a computer to request state information indicating whether at least one function supported by the first core network node is enabled or disabled from the first core network node, and receiving the state information in response to the request.(Supplementary Note 19) The program according to Supplementary Note 17, wherein after receiving the state information, the first core network node in which a required function is enabled is selected when establishing a PDU (Protocol Data Unit) session.

[0075] Some or all of the elements (e.g., configurations and functions) described in Supplementary Notes 2 to 7 that are dependent on Supplementary Note 1 may also be dependent on Supplementary Notes 14 and 17 in the same dependency relationship as Supplementary Notes 2 to 7. Some or all of the elements (e.g., configurations and functions) described in Supplementary Notes 9 to 13 that are dependent on Supplementary Note 8 may also be dependent on Supplementary Notes 15 and 18 in the same dependency relationship as Supplementary Notes 9 to 13. Some or all of the elements described in any Supplementary Note may be applicable to various hardware, software, recording means for recording software, systems, and methods.

[0076] This application claims priority based on Japanese Patent Application No. 2024-021121, filed February 15, 2024, the disclosure of which is incorporated herein in its entirety by reference.

[0077] REFERENCE SIGNS LIST 10 Core network node 11 Control unit 12 Communication unit 20 Core network node 21 Communication unit 30 UPF 40 SMF 50 NRF

Claims

1. A first core network node comprising: a control means for enabling or disabling at least one function that it supports; and a communication means for transmitting status information indicating whether the at least one function is enabled or disabled to a second core network node.

2. The first core network node according to claim 1, wherein the communication means transmits the status information to the second core network node when the second core network node requests the status information.

3. The first core network node according to claim 2, wherein the communication means notifies the second core network node that the state of the at least one function has changed from an enabled state to an disabled state or from an disabled state to an enabled state.

4. A first core network node according to any one of claims 1 to 3, wherein the communication means registers capability information indicating that the status information can be transmitted to an information providing device that provides information to the second core network node.

5. The first core network node according to claim 4, wherein the at least one function is information included in an NF profile managed by an NRF that is the information providing device.

6. The first core network node according to claim 5, wherein the at least one function is a function supported by a UPF.

7. The first core network node according to any one of claims 1 to 3, wherein the at least one function includes at least one of NAT and packet inspection.

8. A second core network node comprising a communication means for requesting status information from the first core network node indicating whether at least one function supported by the first core network node is enabled or disabled, the communication means receiving the status information in response to the request.

9. The second core network node according to claim 8, wherein after receiving the status information, the second core network node selects the first core network node in which a required function is enabled when establishing a PDU (Protocol Data Unit) session.

10. A second core network node according to claim 8 or 9, wherein the communication means receives information indicating at least one of the first core network nodes to which the status information can be transmitted from an information providing device.

11. The second core network node according to claim 10, wherein the at least one function is information included in an NF profile managed by an NRF that is the information providing device.

12. The second core network node according to claim 11, wherein the at least one function is a function supported by a UPF.

13. The second core network node according to claim 11 or 12, wherein the at least one function includes at least one of NAT and packet inspection.

14. A method performed in a first core network node, the method comprising: managing state information indicating whether at least one feature that it supports is enabled or disabled; and transmitting the state information to a second core network node.

15. A program that causes a computer to manage status information indicating whether at least one supported function is enabled or disabled, and transmit the status information to a second core network node.

Images