Network node and control method

The network node ensures seamless edge computing services by identifying available EAS compositions, addressing service continuity issues in 5G networks when devices move, thereby maintaining low-latency services.

JP2026102997APending Publication Date: 2026-06-24NTT DOCOMO INC

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
NTT DOCOMO INC
Filing Date
2023-04-24
Publication Date
2026-06-24

AI Technical Summary

Technical Problem

In 5G networks, when a device moves, changing connections to a new Edge Application Server (EAS) may disrupt the continuity of edge computing services due to the new EAS not being connected to the same constituent EAS as the original, leading to a potential decrease in service quality.

Method used

A network node that includes a receiving unit for profile information and a control unit to determine a candidate destination program provider based on the profile information and a discovery request, ensuring seamless service continuity by identifying available EAS compositions.

Benefits of technology

Maintains edge computing services with low latency even when devices are in motion by verifying service continuity and ensuring continuous service provision.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026102997000001_ABST
    Figure 2026102997000001_ABST
Patent Text Reader

Abstract

Maintaining services provided by edge computing when the device is in motion. [Solution] The network node includes a receiving unit that receives profile information from a program provider that includes information on whether a program provider composition is available, and a receiving unit that receives a program provider discovery request from a source function execution unit that includes an identifier that identifies the program provider composition, a control unit that determines a candidate destination program provider based on the profile information and the program provider discovery request, and a transmitting unit that transmits a program provider discovery response including the determined candidate destination program provider to the source function execution unit.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a network node and a control method in a communication system.

Background Art

[0002] In 3GPP (Registered Trademark) (3rd Generation Partnership Project), in order to achieve further increase in system capacity, further increase in data transmission speed, further reduction in latency in the radio section, etc., a radio communication method called 5G or NR (New Radio) (hereinafter, this radio communication method is referred to as "5G" or "NR") is being studied. In 5G, various radio technologies are being studied in order to meet the requirement of achieving a throughput of 10 Gbps or more and reducing the latency in the radio section to 1 ms or less.

[0003] In NR, a network architecture including a 5GC (5G Core Network) corresponding to the EPC (Evolved Packet Core) which is the core network in the network architecture of LTE (Long Term Evolution) and an NG-RAN (Next Generation - Radio Access Network) corresponding to the E-UTRAN (Evolved Universal Terrestrial Radio Access Network) which is the RAN (Radio Access Network) in the network architecture of LTE is being studied (for example, Non-Patent Document 1).

[0004] Furthermore, edge computing is being considered to enable efficient services by reducing latency between endpoints and lowering the load on the transport network by providing operator and third-party services closer to the UE's access point. For example, for applications requiring low latency, an operation is being considered in which edge computing functions are configured in the terminal and server, and communication is enabled using a server located close to the terminal (see, for example, Non-Patent Document 2). [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] 3GPP TS 23.501 V17.6.0(2022-09) [Non-Patent Document 2] 3GPP TS 23.558 V18.1.0(2022-12) [Non-Patent Document 3] 3GPP TR 23.700-98 V18.0.0(2022-12) [Overview of the project] [Problems that the invention aims to solve]

[0006] This scenario assumes that an application client on a terminal connects to an EAS (Edge Application Server) (which may be called a Connecting EAS), and that this EAS cooperates with other EASs (which may be called Component EASs) to provide services to the user (EAS composition, e.g., Non-Patent Document 3).

[0007] In this case, when a device moves, the system may change its connection to an EAS located near the device's new location in order to provide the service with the lowest possible latency. However, if the EAS after the connection change is not connected to the same constituent EAS as the original EAS, it may become impossible to continue providing the same level of service as before the connection change.

[0008] This invention has been made in view of the above points, and aims to maintain the services provided by edge computing when the terminal is in motion. [Means for solving the problem]

[0009] According to the disclosed technology, a network node is provided that includes: a receiving unit that receives profile information from a program provider including information on whether a program provider composition is available, and a receiving unit that receives a program provider discovery request from a source function execution unit including an identifier that identifies the program provider composition; a control unit that determines a candidate destination program provider based on the profile information and the program provider discovery request; and a transmitting unit that transmits a program provider discovery response including the determined candidate destination program provider to the source function execution unit. [Effects of the Invention]

[0010] According to the disclosed technology, edge computing can maintain services even when the device is in motion. [Brief explanation of the drawing]

[0011] [Figure 1] This is a diagram illustrating an example of a communication system. [Figure 2] This diagram illustrates an example of a communication system in a roaming environment. [Figure 3] This is a diagram illustrating an example of edge computing (1). [Figure 4]This is a diagram illustrating an example of edge computing (2). [Figure 5] This figure illustrates an example (1) of edge computing in an embodiment of the present invention. [Figure 6] This figure illustrates an example (2) of edge computing in an embodiment of the present invention. [Figure 7] This is a sequence diagram illustrating an example of edge computing in an embodiment of the present invention. [Figure 8] This figure shows an example of an EAS Profile in an embodiment of the present invention. [Figure 9] This figure shows an example of the functional configuration of a base station 10 and a network node 30 in an embodiment of the present invention. [Figure 10] This figure shows an example of the functional configuration of terminal 20 in an embodiment of the present invention. [Figure 11] This figure shows an example of the hardware configuration of a base station 10, a terminal 20, and a network node 30 in an embodiment of the present invention. [Figure 12] This figure shows an example of the configuration of a vehicle 2001 in an embodiment of the present invention. [Modes for carrying out the invention]

[0012] Embodiments of the present invention will be described below with reference to the drawings. Note that the embodiments described below are examples, and the embodiments to which the present invention is applied are not limited to those described below.

[0013] In the operation of the wireless communication system according to the embodiments of the present invention, existing technologies may be used as appropriate. However, such existing technologies include, for example, existing LTE, but are not limited to existing LTE. Furthermore, the term "LTE" as used herein has a broad meaning that includes LTE-Advanced and LTE-Advanced and later methods (e.g., NR), or wireless LAN (Local Area Network), unless otherwise specified.

[0014] Also, in the embodiments of the present invention, when wireless parameters or the like are "configured", it may mean that predetermined values are pre-configured, or it may mean that wireless parameters notified from the network node 30 or the terminal 20 are configured.

[0015] FIG. 1 is a diagram for explaining an example of a communication system. As shown in FIG. 1, the communication system is composed of a UE which is a terminal 20 and a plurality of network nodes 30. Hereinafter, it is assumed that one network node 30 corresponds to each function, but one network node 30 may implement a plurality of functions, or a plurality of network nodes 30 may implement one function. Also, the "connection" described below may be a logical connection or a physical connection.

[0016] The RAN (Radio Access Network) is a network node 30 having a radio access function, and may include a base station 10, and is connected to a UE, an AMF (Access and Mobility Management Function), and a UPF (User plane function). The AMF is a network node 30 having functions such as the termination of the RAN interface, the termination of the NAS (Non-Access Stratum), registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 having functions such as a PDU (Protocol Data Unit) session point for interconnecting with the DN (Data Network) externally, packet routing and forwarding, and QoS (Quality of Service) handling of the user plane. The UPF and the DN constitute a network slice. In the wireless communication network in the embodiments of the present invention, a plurality of network slices are constructed.

[0017] AMF is connected to UE, RAN, SMF (Session Management function), NSSF (Network Slice Selection Function), NEF (Network Exposure Function), NRF (Network Repository Function), UDM (Unified Data Management), AUSF (Authentication Server Function), PCF (Policy Control Function), and AF (Application Function). AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are interconnected via interfaces based on their respective services: Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0018] SMF is a network node 30 that has functions such as session management, IP (Internet Protocol) address allocation and management for UEs, DHCP (Dynamic Host Configuration Protocol) functionality, ARP (Address Resolution Protocol) proxy, and roaming functionality. NEF is a network node 30 that has the function of notifying other NFs (Network Functions) of capabilities and events. NSSF is a network node 30 that has functions such as selecting the network slice to which the UE connects, determining the allowed NSSAI (Network Slice Selection Assistance Information), determining the NSSAI to be set, and determining the AMF set to which the UE connects. PCF is a network node 30 that has the function of controlling network policy. AF is a network node 30 that has the function of controlling application servers. NRF is a network node 30 that has the function of discovering NF instances that provide services. UDM is a network node 30 that manages subscriber data and authentication data. UDM is connected to UDR (User Data Repository) which holds the said data.

[0019] Figure 2 is a diagram illustrating an example of a communication system in a roaming environment. As shown in Figure 2, the network consists of a terminal 20 (UE) and multiple network nodes 30. Hereafter, one network node 30 will be assumed to correspond to each function, however, one network node 30 may implement multiple functions, or multiple network nodes 30 may implement one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0020] The RAN is a network node 30 with wireless access capabilities and is connected to the UE, AMF, and UPF. The AMF is a network node 30 with functions such as RAN interface termination, NAS termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 interconnected with the DN and has functions such as external PDU session point, packet routing and forwarding, and user plane QoS handling. The UPF and DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, multiple network slices are constructed.

[0021] AMF is connected to UE, RAN, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, AF, and SEPP (Security Edge Protection Proxy). AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are interconnected via interfaces based on their respective services: Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0022] SMF is a network node 30 with functions such as session management, UE IP address assignment and management, DHCP functionality, ARP proxy, and roaming functionality. NEF is a network node 30 with the function of notifying other NFs of capabilities and events. NSSF is a network node 30 with functions such as selecting the network slice to which the UE connects, determining the allowed NSSAI, determining the NSSAI to be configured, and determining the AMF set to which the UE connects. PCF is a network node 30 with the function of controlling network policy. AF is a network node 30 with the function of controlling application servers. NRF is a network node 30 with the function of discovering NF instances that provide services. SEPP is an opaque proxy that filters control plane messages between PLMNs (Public Land Mobile Networks). vSEPP shown in Figure 2 is SEPP in the visited network, and hSEPP is SEPP in the home network.

[0023] As shown in Figure 2, the UE is in a roaming environment connected to the RAN and AMF in the VPLMN (Visited PLMN). The VPLMN and HPLMN (Home PLMN) are connected via vSEPP and hSEPP. The UE can communicate with the HPLMN's UDM, for example, via the VPLMN's AMF.

[0024] Furthermore, edge computing is being considered to enable efficient services by reducing latency between endpoints and lowering the load on the transport network by providing operator and third-party services closer to the UE's access point. For example, for applications requiring low latency, an operation is being considered in which edge computing functions are configured in the terminal and server, and communication is enabled using a server located close to the terminal (see, for example, Non-Patent Document 2).

[0025] Figure 3 is a diagram illustrating an example of edge computing (1). As shown in Figure 3, application communication takes place between the Edge Application Server (EAS) and the Application Client (AC), and the Edge Enabler Server (EES) and Edge Enabler Client (EEC) perform the operations to connect to the Edge Data Network (EDN).

[0026] As shown in Figure 3, the UE, the edge data network, and the Edge Configuration Server (ECS) may be connected via the core network.

[0027] The reference point EDGE-n in the architecture that enables edge applications shown in Figure 3 is as follows (see Non-Patent Document 2). EDGE-1: Enables interoperability between EES and EEC. It registers and unregisters EECs with EES. It also searches for and retrieves EAS configuration information. Furthermore, it discovers available EAS instances in the EDN. It executes service continuity procedures, such as initiating ACR (Application Context Relocation). EDGE-2: Enables interaction between EES and APIs for retrieving core network functions and network capability information. Access via SCEF (Service Capability Exposure Function) and NEF APIs, or direct access to core network functions from EES located within an MNO (Mobile Network Operator) trust domain is supported. EDGE-3: Enables interoperability between EES and EAS. Supports registration of EAS with availability-related information. Availability-related information includes, for example, time constraints and location constraints. Also allows unregistering EAS from EES. Furthermore, it performs target EAS discovery to support ACT (Application Context Transfer). It also provides access to network capability information such as location information. It also requests the establishment of data sessions between AC and EAS to which specific QoS is applied and obtains QoS-related information. It also supports service continuity procedures such as ACR status. EDGE-4: Enables interoperability between ECS and EEC. Provides edge configuration information to EEC. EDGE-5: Enables interoperability between AC and EEC. EDGE-6: Enables interoperability between ECS and EES. It registers EES information in ECS, unregisters EES information from ECS, and searches for target EES information from ECS. EDGE-7 enables interoperability between EAS and APIs for retrieving core network functions and network capability information. Access via SCEF and NEF APIs, or direct access to core network functions from EAS located within the MNO trust domain, is supported. EDGE-8 enables interoperability between ECS and APIs for retrieving core network functions and network capability information. Access via SCEF and NEF APIs, or direct access to core network functions from ECS located within an MNO trust domain, is supported. EDGE-9 enables interoperability between EESs. Two EESs connected by EDGE-9 may be located in different EDNs or in the same EDN. To support ACR, it performs discovery of target EAS information. It also supports EEC context relocation procedures. Furthermore, it transparently transfers application contexts in ACR managed by the EEL (Edge Enabler layer).

[0028] Figure 4 is a diagram illustrating an example of edge computing (2). As shown in Figure 4, we assume a case where an application client on a terminal connects to an EAS (which may be called a Connecting EAS), and this EAS works in cooperation with other EASs (which may be called Component EASs) to provide services to the user (EAS composition, e.g., Non-Patent Document 3). Here, a single EAS may have multiple service-related EASs connected to it as Component EASs. In Figure 4, a total of three Component EASs are connected to the Connecting EAS: two Component EASs related to the game service and one Component EAS related to the video service.

[0029] Furthermore, as shown in Figure 4, when a terminal moves, in order to provide services with the lowest possible latency, the connection may be changed to a connection EAS located near the terminal's destination. However, if the connection EAS after the change is not connected to the component EAS in the same way as the connection EAS that was originally connected, it may become impossible to continue providing the same level of service as before the connection change.

[0030] Therefore, when changing the connected EAS, it is advisable to check the connection status of the target EAS beforehand.

[0031] Figure 5 is a diagram illustrating an example (1) of edge computing in an embodiment of the present invention. As shown in Figure 5, in an EAS composition consisting of a connected EAS and component EAS connected to an AC, multiple component EAS are connected to the connected EAS. The connected EAS notifies the EES of a list indicating availability for each identifier (composite ID) that identifies the EAS composition, in the EAS profile (profile information). Here, the connecting EAS notifies the source EES of the EAS profile, and the connected EAS notifies the target EES of the EAS profile.

[0032] Furthermore, as shown in Figure 5, if the UE moves and it is determined that ACR is required, the source EES queries the target EES for the destination EAS by specifying the composite ID. The target EES refers to the availability of the specified composite ID and considers only EAS corresponding to available EAS compositions as destination candidates. Here, availability may be expressed as a binary value: available or non-available. Alternatively, the number of component EAS in the destination EAS composition may be indicated as an integer value; for example, if the number of component EAS is greater than or equal to a predetermined required number, it is considered available.

[0033] In the example in Figure 5, since composite ID=0001 is available for the connected EAS before the move, the target EES notifies the source EES of the EAS with composite ID=0001 available as a candidate for the target EAS after the move in response to the target EAS discovery. In other words, the target EES notifies the source EES of the EAS in response to the target EAS discovery that the component EAS is the same as the component EAS before the move as a candidate for the EAS after the move. There may be multiple candidate target EAS.

[0034] Figure 6 is a diagram illustrating an example (2) of edge computing in an embodiment of the present invention. In the example in Figure 6, if the connection between the connecting EAS and one component EAS is interrupted at the destination due to a failure, the connecting EAS at the destination notifies the target EAS of an EAS profile with a status of not available. The target EAS does not select the EAS notified with a status of not available as a candidate for the target EAS. That is, the target EAS does not include the EAS with a status of not available as a candidate for the target EAS after migration, and notifies the source EES of its response to target EAS discovery.

[0035] Figure 7 is a sequence diagram illustrating an example of edge computing in an embodiment of the present invention. In step S101a, the source EAS notifies the source EES of its EAS profile. Similarly, in step S101b, the target EAS notifies the target EES of its EAS profile, where the EAS profile includes a list indicating availability for each composite ID.

[0036] Figure 8 shows an example of an EAS profile in an embodiment of the present invention. As shown in Figure 8, the EAS profile has an Information Element, which is a List of availability per composite ID. This list indicates whether or not the services provided by the EAS composition, which consists of connected EAS and component EAS, are available. The composite ID is an identifier (ID) that identifies the EAS composition. Let's return to Figure 7 for further explanation.

[0037] In step S102, the source EAS sends an EAS discovery request to the source EES. In the following step S103, the source EES decides whether or not to perform an ACR. If an ACR is performed, in the following step S104, the source EES retrieves information about the target EES from the ECS.

[0038] In the following step S105, the source EES sends an EAS discovery request containing the composite ID to the target EES. In the following step S106, the target EES selects target EAS candidates by comparing the availability of the composite IDs of the EAS. Alternatively, the target EES selects as target EAS candidates any EAS (EAS composition) that is specified by the composite ID included in the EAS discovery request and is available (e.g., status is available). Alternatively, if the status in the EAS profile indicates the number of component EAS in the connected EAS composition, the target EES selects as candidates any EAS (EAS composition) whose status indicates a number greater than or equal to a predetermined number.

[0039] In the subsequent step S107, the target EES sends an EAS discovery response to the source EES, which includes a candidate target EAS determined based on the notified composite ID.

[0040] In the subsequent step S108, the source EES sends an EAS discovery response to the source EAS, which includes a candidate target EAS.

[0041] The above-described embodiment allows for a simple verification of whether service continuity is ensured in the environment at the destination of the UE, even in complex edge computing use cases using multiple EAS, and enables the continuous provision of low-latency services.

[0042] In other words, edge computing can maintain the services it provides even when the device is in motion.

[0043] Furthermore, EAS may be referred to by names such as program delivery device, and EES may be referred to by names such as function execution device. Also, the point before the terminal moves is called the source, and the point after the terminal moves is called the target. Network nodes, devices, and servers connected to the terminal may be referred to, for example, as the source EES function execution device and the target EAS as the destination program delivery device. Additionally, EAS composition may be referred to as program delivery device composition, and EAS discovery request as program delivery device EAS discovery request.

[0044] (Device configuration) Next, an example of the functional configuration of the base station 10, network node 30, and terminal 20 that perform the processes and operations described above will be explained. The base station 10, network node 30, and terminal 20 include the functions to perform the embodiments described above. However, the base station 10, network node 30, and terminal 20 may each have only some of the functions in the embodiments. The network node 30 may support the AC, EEC, EDN, EAS, EES, ECS, and core network described above.

[0045] <Base station 10 and network node 30> Figure 9 shows an example of the functional configuration of a base station 10 and a network node 30. As shown in Figure 9, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Figure 9 is merely an example. The functional classifications and names of the functional units can be anything as long as they can perform the operations according to the embodiment of the present invention. The network node 30 may have the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different functions on the system architecture may be composed of multiple network nodes 30 separated by function.

[0046] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 or other network node 30 and transmitting the signal by wire or wireless. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 or other network node 30 and obtaining information from the received signal, for example, higher layer information. A communication unit including the transmitting unit 110 and the receiving unit 120 may be configured.

[0047] The configuration unit 130 stores pre-configured configuration information and various configuration information to be transmitted to the terminal 20 in a storage device, and reads it from the storage device as needed. The contents of the configuration information include, for example, information related to PDCP and information related to SBI.

[0048] As described in the embodiment, the control unit 140 performs processing related to PDCP in the network. The control unit 140 also performs processing for SBI communication. The control unit 140 also performs processing related to communication with the terminal 20. The signal transmission function of the control unit 140 may be included in the transmission unit 110, and the signal reception function of the control unit 140 may be included in the reception unit 120.

[0049] <Terminal 20> Figure 10 shows an example of the functional configuration of terminal 20. As shown in Figure 10, terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Figure 10 is merely an example. The functional classifications and names of the functional units can be anything as long as they can perform the operations according to the embodiment of the present invention. Furthermore, the communication device that becomes the resource holder 20 may have a functional configuration similar to that of terminal 20.

[0050] The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 wirelessly receives various signals and obtains signals from higher layers from the received physical layer signals. The receiving unit 220 also has the function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals or reference signals transmitted from the network node 30. A communication unit including the transmitting unit 210 and the receiving unit 220 may be configured.

[0051] The configuration unit 230 stores various configuration information received from the network node 30 by the receiving unit 220 in its storage device and reads it from the storage device as needed. The configuration unit 230 also stores pre-configured configuration information. The content of the configuration information includes, for example, information related to PDCP.

[0052] The control unit 240 performs processing related to PDCP in the network, as described in the embodiment. The signal transmission function of the control unit 240 may be included in the transmission unit 210, and the signal reception function of the control unit 240 may be included in the reception unit 220.

[0053] (Hardware configuration) The block diagrams (Figures 9 and 10) used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may be realized by combining the one or more devices with software.

[0054] Functions include, but are not limited to, judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. As mentioned above, the method of implementation is not particularly limited.

[0055] For example, the network node 30, terminal 20, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 11 is a diagram showing an example of the hardware configuration of a base station 10 and terminal 20 according to one embodiment of the present disclosure. The network node 30 may have a hardware configuration similar to that of the base station 10. The base station 10 and terminal 20 described above may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0056] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

[0057] Each function in the base station 10 and terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and storage device 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of the reading and writing of data in the storage device 1002 and auxiliary storage device 1003.

[0058] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit 140, control unit 240, etc., described above may be implemented by the processor 1001.

[0059] Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes accordingly. The program used is one that causes a computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 140 of the base station 10 shown in Figure 9 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Also, for example, the control unit 240 of the terminal 20 shown in Figure 10 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above processes have been described as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may be transmitted from the network via a telecommunications line.

[0060] The storage device 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The storage device 1002 may also be called a register, cache, main memory, etc. The storage device 1002 can store executable programs (program code), software modules, etc., for implementing a communication method according to one embodiment of this disclosure.

[0061] The auxiliary storage device 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disc, a digital multipurpose disc, a Blu-ray® disc), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The above-mentioned storage medium may also be a database, server, or other suitable medium that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0062] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may include high-frequency switches, duplexers, filters, frequency synthesizers, etc., to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmit / receive antenna, amplifier section, transmit / receive section, transmission path interface, etc., may be implemented by the communication device 1004. The transmit / receive section may be implemented with physically or logically separated transmitting and receiving sections.

[0063] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0064] Furthermore, each device, such as the processor 1001 and the storage device 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.

[0065] Furthermore, the base station 10 and terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0066] Figure 12 shows an example of the configuration of vehicle 2001. As shown in Figure 12, vehicle 2001 comprises a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021-2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in this disclosure may be applied to a communication device mounted on vehicle 2001, for example, to the communication module 2013.

[0067] The drive unit 2002 consists of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel, which is operated by the user.

[0068] The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (IO ports) 2033. Signals from various sensors 2021 to 2029 installed in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0069] Signals from various sensors 2021-2029 include current signals from current sensor 2021 which senses motor current, front and rear wheel rotation speed signals obtained by rotation speed sensor 2022, front and rear wheel air pressure signals obtained by air pressure sensor 2023, vehicle speed signals obtained by vehicle speed sensor 2024, acceleration signals obtained by acceleration sensor 2025, accelerator pedal depression signals obtained by accelerator pedal sensor 2029, brake pedal depression signals obtained by brake pedal sensor 2026, shift lever operation signals obtained by shift lever sensor 2027, and detection signals obtained by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0070] The Information Services Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Services Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001. The Information Services Unit 2012 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) and output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

[0071] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also sends and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

[0072] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via its communication port. For example, the communication module 2013 sends and receives data via its communication port 2033 to the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021-29 provided in the vehicle 2001.

[0073] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station or a mobile station.

[0074] The communication module 2013 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 2012. The electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above input.

[0075] The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit, which outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from the external device in memory 2032, which is available to the microprocessor 2031. Based on the information stored in memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc., provided in the vehicle 2001.

[0076] (Summary of the embodiments) As described above, according to an embodiment of the present invention, a network node is provided which includes: a receiving unit that receives profile information from a program providing device including information on whether a program providing device composition is available, and a receiving unit that receives a program providing device discovery request from a source function execution device including an identifier that identifies the program providing device composition; a control unit that determines a candidate destination program providing device based on the profile information and the program providing device discovery request; and a transmitting unit that transmits a program providing device discovery response including the determined candidate destination program providing device to the source function execution device.

[0077] With the above configuration, even in complex edge computing use cases using multiple EAS, it is possible to easily verify whether service continuity is guaranteed in the environment where the UE moves, and to continue providing low-latency services. In other words, the services provided by edge computing can be maintained even when the terminal moves.

[0078] The control unit may determine a program provider that is indicated in the profile information as having an available program provider composition identified by the identifier as a candidate for the destination program provider. This configuration allows for easy verification of whether service continuity is ensured in the environment at the destination of the UE, even in complex edge computing use cases using multiple EAS, and enables the continuous provision of low-latency services.

[0079] The control unit may determine a program provider as a candidate for the destination program provider if the number of component program providers in the program provider composition identified by the identifier in the profile information is equal to or greater than a predetermined number. With this configuration, even in complex edge computing use cases using multiple EAS, it is possible to easily verify whether service continuity is ensured in the environment at the destination of the UE and to continue providing low-latency services.

[0080] Furthermore, according to an embodiment of the present invention, a network node is provided which receives profile information from a program provider that includes information on whether a program provider composition is available, and receives a program provider discovery request from a source function execution device that includes an identifier that identifies the program provider composition, and a control unit that determines whether or not to perform an ACR (Application Context Relocation). If the control unit determines to perform an ACR, the receiving unit further includes a transmitting unit that receives information on a destination function execution device from an ECS (Edge Configuration Server) and transmits a program provider discovery request to the destination function execution device that includes an identifier that identifies the program provider composition, and the receiving unit receives a program provider discovery response from the destination function execution device that includes a candidate destination program provider.

[0081] With the above configuration, even in complex edge computing use cases using multiple EAS, it is possible to easily verify whether service continuity is guaranteed in the environment where the UE moves, and to continue providing low-latency services. In other words, the services provided by edge computing can be maintained even when the terminal moves.

[0082] Furthermore, according to an embodiment of the present invention, a control method is provided that a network node can execute, comprising the steps of: receiving profile information from a program provider including information on whether a program provider composition is available; receiving a program provider discovery request from a source function execution device including an identifier that identifies the program provider composition; determining a candidate destination program provider based on the profile information and the program provider discovery request; and transmitting a program provider discovery response including the determined candidate destination program provider to the source function execution device.

[0083] With the above configuration, even in complex edge computing use cases using multiple EAS, it is possible to easily verify whether service continuity is guaranteed in the environment where the UE moves, and to continue providing low-latency services. In other words, the services provided by edge computing can be maintained even when the terminal moves.

[0084] Furthermore, according to an embodiment of the present invention, the present invention provides a control method to be executed by a network node that receives a program provider discovery request from a source function execution device that includes an identifier that identifies the program provider composition, and a receiving step that receives profile information from a program provider that includes information about whether a program provider composition is available from a program provider, and a receiving step that includes an identifier that identifies the program provider composition from a source function execution device, and a control step that determines whether or not to perform an Application Context Relocation (ACR). If the control step determines that an ACR should be performed, the receiving step further includes a transmitting step that receives information about a destination function execution device from an Edge Configuration Server (ECS), and transmits a program provider discovery request that includes an identifier that identifies the program provider composition to the destination function execution device, and the receiving step provides a control method to be executed by a network node that receives a program provider discovery response including a candidate destination program provider from the destination function execution device.

[0085] With the above configuration, even in complex edge computing use cases using multiple EAS, it is possible to easily verify whether service continuity is guaranteed in the environment where the UE moves, and to continue providing low-latency services. In other words, the services provided by edge computing can be maintained even when the terminal moves.

[0086] (Supplement to the embodiment) While embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. Regarding the processing procedures described in the embodiments, the order of processing may be changed as long as it does not contradict each other. For the convenience of explaining the processing, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be implemented in hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to an embodiment of the present invention and the software operated by the processor of the terminal 20 according to an embodiment of the present invention may be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

[0087] Furthermore, the notification of information is not limited to the embodiments / models described herein and may be carried out by other methods. For example, the notification of information may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or combinations thereof. Also, RRC signaling may be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0088] Each aspect / embodiment described in this disclosure includes LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), and IEEE This may apply to at least one system utilizing 802.20, UWB (Ultra-WideBand), Bluetooth®, or other appropriate systems, and to next-generation systems extended, modified, created, or defined based thereon. It may also apply to a combination of multiple systems (for example, a combination of at least one of LTE and LTE-A with 5G).

[0089] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order.

[0090] In this specification, specific operations performed by the base station 10 may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station 10, it is clear that various operations performed for communication with the terminal 20 can be performed by the base station 10 and at least one of the other network nodes (for example, an MME or S-GW, but not limited to these). Although the above example illustrates the case where there is one other network node besides the base station 10, the other network node may be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0091] The information or signals described in this disclosure may be output from a higher layer (or lower layer) to a lower layer (or higher layer). They may also be input and output via multiple network nodes.

[0092] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

[0093] The determination in this disclosure may be made by a value represented by one bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0094] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0095] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0096] The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0097] In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0098] The terms “system” and “network” as used in this disclosure are interchangeable.

[0099] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index.

[0100] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0101] In this disclosure, terms such as "base station (BS)", "wireless base station", "base station equipment", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0102] A base station can house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0103] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform information-based control or operation.

[0104] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0105] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or several other appropriate terms.

[0106] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes the case when the mobile body is stationary. The mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and items mounted on them. The mobile body may also be a mobile body that moves autonomously based on operation commands. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station may include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0107] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the terminals 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel.

[0108] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station may be configured to have the same functions as the user terminal described above.

[0109] As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in a table, database, or other data structure), and ascertaining. “Determining” may also include, for example, receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0110] The terms “connected,” “coupled,” or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0111] The reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applicable standard.

[0112] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0113] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way.

[0114] In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc.

[0115] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0116] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0117] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0118] Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0119] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way. [Explanation of Symbols]

[0120] 10 base station 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 devices 210 Transmitter 220 Receiver 230 Setting section 240 Control Unit 30 network nodes 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device

Claims

1. A receiving unit that receives profile information from a program provider that includes information on whether a program provider composition is available, and receives a program provider discovery request from a source function execution device that includes an identifier that identifies the program provider composition, A control unit that determines a candidate for a destination program provider based on the profile information and the program provider discovery request, A transmission unit that transmits a program provider discovery response, including the determined destination program provider candidate, to the source function execution device, A network node that has

2. The network node according to claim 1, wherein the control unit determines a program provider that is indicated in the profile information as having an available program provider composition identified by the identifier, as a candidate for the destination program provider.

3. The network node according to claim 1, wherein the control unit determines a program provider as a candidate for the destination program provider, in the profile information, a program provider whose number of component program provider devices in the program provider composition identified by the identifier is equal to or greater than a predetermined number.

4. A receiving unit that receives profile information from a program provider that includes information on whether a program provider composition is available, and receives a program provider discovery request from a source function execution device that includes an identifier that identifies the program provider composition, It includes a control unit that determines whether or not to perform ACR (Application Context Relocation), If the control unit determines that it will perform ACR, The receiving unit receives information about the destination function execution device from the ECS (Edge Configuration Server), The system further includes a transmission unit that transmits a program provider discovery request, which includes an identifier that identifies the program provider composition, to the destination function execution device. The receiving unit is a network node that receives a program provider discovery response, including a candidate destination program provider, from the destination function execution device.

5. The steps include receiving profile information from a program provider that includes information on whether a program provider composition is available, and receiving a program provider discovery request from a source function execution device that includes an identifier that identifies the program provider composition, The steps include determining a candidate for a destination program provider based on the profile information and the program provider discovery request, The steps include transmitting a program provider discovery response, including the determined destination program provider candidate, to the source function execution device, A control method performed by a network node having [a certain feature].

6. A receiving step includes receiving profile information from a program provider that includes information on whether a program provider composition is available, and receiving a program provider discovery request from a source function execution device that includes an identifier that identifies the program provider composition, It includes a control step that determines whether or not to perform ACR (Application Context Relocation), If the control step determines that ACR should be executed, The aforementioned receiving step involves receiving information about the destination function execution device from the ECS (Edge Configuration Server), The transmission step further includes transmitting a program provider discovery request, which includes an identifier that identifies the program provider composition, to the destination function execution device. The receiving step is a control method performed by a network node that receives a program provider discovery response, including a candidate destination program provider, from the destination function execution device.