Network node and communication method

Abstract

The present invention pertains to a network node comprising: a reception unit for receiving a discovery request for a computational resource that is set for a subscriber, the request being received from a computational resource that is set for another subscriber or from another network node; and a transmission unit that transmits, to the other computational resource or the other network node, information indicating an attribute of the computational resource.

Description

【Technical Field】 【0001】 The present invention relates to a network node and a communication method in a wireless communication system. 【Background Art】 【0002】 In NR (New Radio), which is a successor system to LTE (Long Term Evolution) (also referred to as "5G"), a network architecture including a 5GC (5G Core Network) corresponding to the EPC (Evolved Packet Core), which is the core network in the LTE network architecture, 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 LTE network architecture, is being considered (for example, Non-Patent Document 1 and Non-Patent Document 2). 【Prior Art Documents】 【Non-Patent Documents】 [[ID=z20]] 【0003】 【Non-Patent Document 1】 3GPP TS 23.501 V17.2.0 (2021-09) 【Non-Patent Document 2】 3GPP TS 23.502 V17.2.1 (2021-09) 【Summary of the Invention】 【Problems to be Solved by the Invention】 【0004】 It is envisioned that telecommunications carriers will provide a service that leases computing resources within the network to subscribers. Subscribers can use these computing resources as the endpoint for sending and receiving communications related to them. Subscribers may also have application programs equipped with AI or other technologies that act on their behalf reside on these computing resources. These applications may search for opposing applications residing on other computing resources and autonomously communicate with the discovered applications. However, with existing technologies, it has been difficult to discover these other computing resources, which are necessary prior to the aforementioned application search. 【0005】 This invention has been made in view of the above points, and aims to enable computing resources on a network to discover other computing resources. [Means for solving the problem] 【0006】 According to the disclosed technology, a network node is provided that includes a receiving unit that receives a request to discover computing resources set up by a subscriber from computing resources set up by other subscribers or from other network nodes, and a transmitting unit that transmits information indicating the attributes of the computing resources to the other computing resources or the other network nodes. [Effects of the Invention] 【0007】 The disclosed technology provides a mechanism that enables computing resources on a network to discover other computing resources. [Brief explanation of the drawing] 【0008】 [Figure 1] This figure illustrates a wireless communication system according to an embodiment of the present invention. [Figure 2] This figure shows an example of the configuration of a core network according to an embodiment of the present invention. [Figure 3] This sequence diagram shows an example of the procedure for establishing a CRMF session according to an embodiment of the present invention. [Figure 4]This sequence diagram shows an example of the procedure for changing a CRMF session according to an embodiment of the present invention. [Figure 5] This sequence diagram shows an example of the flow of a service request procedure according to an embodiment of the present invention. [Figure 6] This sequence diagram shows an example of the procedure for releasing a CRMF session according to an embodiment of the present invention. [Figure 7] This sequence diagram shows an example of the flow of the CRMF registration procedure according to an embodiment of the present invention. [Figure 8] This sequence diagram shows an example of the procedure for establishing a PDU session according to an embodiment of the present invention. [Figure 9] This sequence diagram shows an example of the flow of the incoming packet forwarding determination procedure according to an embodiment of the present invention. [Figure 10] This sequence diagram shows an example of the flow of an incoming packet forwarding procedure according to an embodiment of the present invention. [Figure 11] This sequence diagram shows an example of the flow of a container registration procedure according to an embodiment of the present invention. [Figure 12] This sequence diagram shows an example of the flow of a container-to-container communication procedure according to an embodiment of the present invention. [Figure 13] This sequence diagram shows an example of the flow of a container movement procedure related to container movement mode 2 of an embodiment of the present invention. [Figure 14] This sequence diagram shows an example of the flow of a container movement procedure related to container movement mode 3 of an embodiment of the present invention. [Figure 15] This figure shows an example of the functional configuration of a base station according to an embodiment of the present invention. [Figure 16] This figure shows an example of the functional configuration of a terminal according to an embodiment of the present invention. [Figure 17] This figure shows an example of the hardware configuration of a base station or terminal according to an embodiment of the present invention. [Figure 18] This figure shows an example of the configuration of a vehicle according to an embodiment of the present invention. 【Mode for Carrying Out the Invention】 【0009】 Hereinafter, embodiments of the present invention will be described with reference to the drawings. Note that the embodiments described below are merely examples, and the embodiments to which the present invention is applied are not limited to the following embodiments. 【0010】 In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies may be used as appropriate. The existing technologies are, for example, existing NR or LTE, but are not limited to existing NR or LTE. Further, the term "LTE" used in this specification shall have a broad meaning including LTE-Advanced and subsequent systems (e.g., NR) unless otherwise specified. 【0011】 Also, in the embodiments of the present invention described below, terms such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), PUSCH (Physical Uplink Shared Channel), etc. used in existing LTE are used. This is for convenience of description, and signals, functions, etc. similar to these may be called by other names. Also, the above terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even for signals used in NR, the "NR-" is not necessarily specified. 【0012】 In addition, in the embodiments of the present invention, the duplex mode may be a TDD (Time Division Duplex) mode, an FDD (Frequency Division Duplex) mode, or other modes (e.g., Flexible Duplex, etc.). 【0013】 In addition, in the embodiments of the present invention, the phrase "configured" for radio parameters, etc. may mean that predetermined values are pre-configured, or that radio parameters notified from a base station or a terminal are configured. 【0014】 (System Configuration) FIG. 1 is a diagram for explaining a wireless communication system according to an embodiment of the present invention. As shown in FIG. 1, the wireless communication system according to an embodiment of the present invention includes a base station 10 and a terminal 20. Although one base station 10 and one terminal 20 are shown in FIG. 1, this is an example, and there may be a plurality of each. 【0015】 The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. The physical resources of the wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols, and the frequency domain may be defined by the number of sub-carriers or the number of resource blocks. Also, the TTI (Transmission Time Interval) in the time domain may be a slot or a sub-frame. 【0016】 The base station 10 transmits synchronization signals and system information to the terminal 20. The synchronization signals are, for example, NR-PSS and NR-SSS. The system information is transmitted, for example, via NR-PBCH and is also called broadcast information. The synchronization signals and system information may also be called SSB (SS / PBCH block). As shown in Figure 1, the base station 10 transmits control signals or data to the terminal 20 via DL (Downlink) and receives control signals or data from the terminal 20 via UL (Uplink). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals using beamforming. Furthermore, both the base station 10 and the terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to DL or UL. In addition, both the base station 10 and the terminal 20 may communicate via secondary cells (SCell) and primary cells (PCell) using CA (Carrier Aggregation). Furthermore, terminal 20 may communicate via the primary cell of base station 10 and the primary secondary cell group cell (PSCell: Primary SCG Cell) of other base stations 10 using DC (Dual Connectivity). 【0017】 Terminal 20 is a communication device equipped with wireless communication capabilities, such as a smartphone, mobile phone, tablet, wearable device, or M2M (Machine-to-Machine) communication module. As shown in Figure 1, Terminal 20 receives control signals or data from the base station 10 via DL and transmits control signals or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. Terminal 20 also receives various reference signals transmitted from the base station 10 and performs propagation path quality measurements based on the reception results of these reference signals. Terminal 20 may also be referred to as UE and base station 10 as gNB. 【0018】 Figure 2 shows an example of the configuration of a core network according to an embodiment of the present invention. The wireless communication system comprises a RAN (Radio Access Network) 10, a terminal 20, a core network 30, and a DN (Data Network) 40. 【0019】 The core network 30 is a network equipped with exchanges, subscriber information management devices, etc. The core network 30 comprises network nodes that implement U-Plane functionality and a group of network nodes that implement C-Plane functionality. 【0020】 The U-Plane function is a function that performs the processing of sending and receiving user data. A network node that implements the U-Plane function is, for example, the UPF (User plane function) 380. The UPF 380 is a network node that has functions such as an external PDU (Protocol Data Unit) session point for interconnecting with the DN 40, packet routing and forwarding, and user plane QoS (Quality of Service) handling. The UPF 380 controls the sending and receiving of data between the DN 40 and the terminal 20. The UPF 380 and DN 40 may consist of one or more network slices. 【0021】 The C-Plane function group is a set of functions that execute a series of control processes for establishing communication and other purposes. The network node group that implements the C-Plane function group includes, for example, AMF (Access and Mobility Management Function) 310, UDM (Unified Data Management) 320, NEF (Network Exposure Function) 330, NRF (Network Repository Function) 340, AUSF (Authentication Server Function) 350, PCF (Policy Control Function) 360, SMF (Session Management Function) 370, and AF (Application Function) 390. 【0022】 RAN10 is a network node that is communicatively connected to the core network 30 and the terminal 20, and includes a base station, a line control device, etc. RAN10 is communicatively connected to AMF310 and UPF380. In the following, base station 10 will also be referred to as RAN10. 【0023】 The AMF310 is a network node with functions such as RAN interface termination, NAS (Non-Access Stratum) termination, registration management, connection management, reachability management, and mobility management. The NRF340 is a network node with the function of discovering NF (Network Function) instances that provide services. The UDM320 is a network node that manages subscriber data and authentication data. The UDM320 includes a UDR (User Data Repository)321 that holds the said data and a FE (Front End)322. The FE322 processes subscriber information. 【0024】 The SMF370 is a network node with functions such as session management, IP (Internet Protocol) address assignment and management for terminal 20, DHCP (Dynamic Host Configuration Protocol) functionality, ARP (Address Resolution Protocol) proxy, and roaming functionality. The NEF330 is a network node with the function of notifying other NFs (Network Functions) of their capabilities and events. The PCF360 is a network node with the function of controlling network policies. 【0025】 The AF (Application Function) 390 is a network node that has the function of controlling application servers. 【0026】 Terminal 20 and AMF310 are connected as an N1 link. AMF310 and RAN10 are connected as an N2 link. UPF380 and RAN10 are connected as an N3 link. UPF380 and SMF370 are connected as an N4 link. UPF380 and DN40 are connected as an N6 link. 【0027】 Furthermore, the core network 30 according to this embodiment further includes a CRMF (Computing Resource Management Function) 371 and a UCRF (User Computing Resource Function) 381 in addition to the conventional configuration described above. 【0028】 UCRF381 is a function that provides computing resources available to users (subscribers) (hereinafter also referred to as the user computing resource function). Computing resources are also referred to as containers below. Note that computing resources may include execution environments for running various applications installed on those computing resources. In other words, UCRF381 has one or more containers 382. UCRF381 is included in the U-Plane function and is communicated with UPF380 as a Ny link. In addition, UCRF381 and DN40 are communicated with each other as an N6 link. 【0029】 CRMF371 is a function for managing computing resources (hereinafter also referred to as the computing resource management function). CRMF371 is included in the C-Plane function group and is connected to other network nodes included in the C-Plane function group so that they can communicate with each other. 【0030】 CRMF371 and UCRF381 are connected in a way that allows them to communicate as an Nx link. Note that the names Nx link and Ny link are just examples and other names may be used. 【0031】 Figure 3 is a sequence diagram showing an example of the procedure for establishing a CRMF session according to an embodiment of the present invention. In step S101, terminal 20 sends a CRMF session establishment request to AMF 310. Terminal 20 may set the CRMF session ID for the termination in AMF and the requested resource capacity indicating the capacity of the requested computing resources in the CRMF session establishment request. Note that the "capacity of computing resources" described below may include not only the capacity of computing resources but also the execution environment, capabilities, etc. 【0032】 In the subsequent step S102, AMF310 sends a CRMF session establishment request to CRMF371. AMF310 includes the CRMF session ID set by terminal 20 in the CRMF session establishment request. AMF310 may also include the requested resource capacity set by terminal 20 in the CRMF session establishment request. 【0033】 In the following step S103, CRMF371 sends a subscriber information confirmation to UDM320 to obtain subscriber information. In the following step S104, UDM320 sends a subscriber information response to CRMF371. Based on the obtained subscriber information, CRMF371 determines whether the CRMF session establishment request from terminal 20 is permissible. If the determination indicates that the CRMF session establishment request from terminal 20 is permissible, the process may proceed to step S105. On the other hand, if the determination indicates that the CRMF session establishment request from terminal 20 is not permissible, CRMF371 may send a response to AMF310 indicating that the CRMF session establishment request has been rejected. AMF310 may send this response to terminal 20. 【0034】 In the following step S105, CRMF371 transmits the requested resource capacity obtained by the CRMF session establishment request to PCF360. In the following step S106, PCF360 determines the capacity of computing resources to be provided to terminal 20 based on the information contained in the obtained requested resource capacity and the telecommunications carrier's policy, and transmits information including the determined capacity to CRMF371 as a requested resource capacity response. 【0035】 For example, PCF360 may decide to provide terminal 20 with computing resources of the same capacity as the requested resource capacity, or it may decide to provide terminal 20 with computing resources of a capacity less than the requested resource capacity, or it may decide to provide terminal 20 with computing resources of a capacity greater than the requested resource capacity. 【0036】 In the following step S107, CRMF371 selects a UCRF381. For example, CRMF371 may select a UCRF381 that is close to terminal 20 based on the location information of terminal 20. In the following step S108, CRMF371 sends a UCRF session establishment request to UCRF381. CRMF371 sets a computing resource generation request in the UCRF session establishment request. The computing resource generation request may be set based on the requested resource capacity, or it may include information indicating the capacity of computing resources based on the requested resource capacity response obtained from PCF360. 【0037】 In the following step S109, UCRF381 configures a container. This container may be configured based on the capacity of computing resources obtained from CRMF371. In the following step S110, UCRF381 sends a UCRF session establishment response to CRMF371. 【0038】 In the following step S111, CRMF371 sends a CRMF session establishment response to AMF310. In the following step S112, AMF310 sends a CRMF session establishment response to terminal 20. 【0039】 Furthermore, in step S113, the UCRF381 may obtain an external communication IP address from, for example, the interface with the DN. Also, in step S114, the UCRF381 may start an application within the container. This application may be a communication application that uses the obtained external communication IP address. 【0040】 Furthermore, from step S114 onward, terminal 20 may use the container configured in UCRF381 to receive services from a telecommunications carrier. 【0041】 Figure 4 is a sequence diagram showing an example of the procedure for changing a CRMF session according to an embodiment of the present invention. In step S200, the CRMF session is assumed to be in an established state. 【0042】 In step S201, terminal 20 sends a CRMF session change request to AMF310, specifying the CRMF session ID. Terminal 20 may also set the change resource capacity and capacity, which are information requesting changes to the capacity, capabilities, and execution environment of the computing resources of the container to be changed, in the CRMF session change request. 【0043】 In the subsequent step S202, AMF310 sends a CRMF session change request to CRMF371. AMF310 includes the CRMF session ID set by terminal 20 in the CRMF session change request. AMF310 may also include the change resource capacity set by terminal 20 in the CRMF session change request. 【0044】 In the following step S203, the CRMF371 determines whether the CRMF session change request from terminal 20 is permissible based on the subscriber information already obtained at its own node. If the CRMF session change request from terminal 20 is permissible based on this determination, the process may proceed to step S204. 【0045】 In the following step S204, CRMF371 transmits the modified resource capacity obtained by the CRMF session change request to PCF360. In the following step S205, PCF360 determines the capacity of computing resources to be provided to terminal 20 based on the information contained in the acquired modified resource capacity and the telecommunications carrier's policy, and transmits information including the determined capacity to CRMF371 as a modified resource capacity response. 【0046】 For example, PCF360 may decide to provide terminal 20 with computing resources of the same capacity as the changed resource capacity, or it may decide to provide terminal 20 with computing resources of a capacity less than the changed resource capacity, or it may decide to provide terminal 20 with computing resources of a capacity greater than the changed resource capacity. 【0047】 In the subsequent step S206, CRMF371 sends a UCRF session change request to UCRF381. CRMF371 sets a computing resource change request in the UCRF session change request. The computing resource change request may be set based on the capacity of the resources to be changed, or it may include information indicating the capacity of the computing resources based on the capacity of the resources to be changed obtained from PCF360. 【0048】 In the following step S207, UCRF381 modifies the container based on the UCRF session change request. The container may be modified based on the capacity of the computing resources obtained from CRMF371. In the following step S208, UCRF381 sends a UCRF session change response to CRMF371. 【0049】 In the following step S209, CRMF371 sends a CRMF session change response to AMF310. In the following step S210, AMF310 sends a CRMF session change response to terminal 20. 【0050】 Figure 5 is a sequence diagram showing an example of the flow of a service request procedure according to an embodiment of the present invention. In step S300, the CRMF session is assumed to be established. 【0051】 In step S301, the UCRF381 detects that the container is not in use. In the subsequent step S302, the UCRF381 deactivates the container. The UCRF381 may deactivate the container based on the carrier's policy if the container has not been used for a certain period of time. 【0052】 In step S303, terminal 20 sends a service request to AMF310, specifying the CRMF session ID in the container list requiring activation. In the following step S304, AMF310 sends a context update request to CRMF371, which includes an information element (IE) indicating the container status set to "Activated". The value of the information element indicating the container status may be set to "Activated", "Activated", or "Deactivated". 【0053】 In the subsequent step S305, CRMF371 sends a UCRF session change request to UCRF381. CRMF371 sets a computing resource change request in the UCRF session change request. CRMF371 may also set an information element in the computing resource change request that indicates the container state obtained from the context update request. 【0054】 In the following step S306, UCRF381 activates the container based on the UCRF session change request. In the following step S307, UCRF381 sends a UCRF session change response to CRMF371. 【0055】 In the following step S308, CRMF371 sends a context update response to AMF310. In the following step S309, AMF310 sends a service response to terminal 20. 【0056】 Figure 6 is a sequence diagram showing an example of the procedure for releasing a CRMF session according to an embodiment of the present invention. In step S400, the CRMF session is assumed to be in an established state. 【0057】 In step S401, terminal 20 sends a CRMF session release request to AMF310, specifying the CRMF session ID. In the following step S402, AMF310 sends a CRMF session release request to CRMF371. AMF310 includes the CRMF session ID set by terminal 20 in the CRMF session release request. 【0058】 In the following step S403, CRMF371 sends a UCRF session release request to UCRF381 to release the UCRF session corresponding to the CRMF session specified by the received CRMF session release request. In the following step S404, UCRF381 releases the corresponding container based on the received UCRF session release request. In the following step S405, UCRF381 sends a UCRF session release response to CRMF371. 【0059】 In the following step S406, CRMF371 sends a CRMF session release response to AMF310. In the following step S407, AMF310 sends a CRMF session release response to terminal 20. 【0060】 (Forwarding incoming packets to the container) Next, we will describe the procedure for forwarding incoming calls to terminal 20 to container 382. 【0061】 Figure 7 is a sequence diagram showing an example of the flow of a CRMF registration procedure according to an embodiment of the present invention. The CRMF registration procedure is a procedure for registering CRMF371 with UDM320. As a prerequisite, the "Ncrmf_CRMFSession" service, which controls the CRMF session context contained in CRMF371, is installed in the C-Plane function group. 【0062】 After container 382 is created, CRMF371 sends a "Nudm_UECM_Registration" request to UDM320 (step S451). The "Nudm_UECM_Registration" request may include the NF instance ID of CRMF371, the CRMF session ID assigned by terminal 20 at the time of the container creation request, the terminal's SUPI (Subscription Permanent Identifier), etc. The "Nudm_UECM_Registration" request is an example of a registration request from CRMF371 to UDM320. 【0063】 UDM320 sends a "Nudm_UECM_Registration" response to CRFM371 (step S452). 【0064】 This allows the SMF370 to access the UDM320 and find the CRMF371 that manages the destination container and the destination UCRF381. 【0065】 Figure 8 is a sequence diagram showing an example of the flow of the PDU session establishment procedure according to an embodiment of the present invention. The PDU session establishment procedure is a procedure for establishing a PDU session and follows the same flow as in the conventional method. The differences from the conventional method will be explained below. 【0066】 Terminal 20 sends a PDU session establishment request to AMF310 (step S501). Here, the PDU session establishment request may include an information element that requests a "no response container transfer" in addition to the conventional one. A "no response container transfer" means transferring to the container without responding. 【0067】 AMF310 sends a PDU session establishment request to SMF370 (step S502). SMF370 sends a PDU session response policy request to PCF360 (step S503). PCF360 sends a PDU session response policy response to SMF370 (step S504). 【0068】 SMF370 sends a PDU session establishment response to AMF310 (step S505). AMF310 notifies terminal 20 of the PDU session establishment response (step S506). 【0069】 Here, the PDU session-aware policy may include an information element requesting "unresponsive container transfer" in addition to the conventional one. Subscribers can set or change the PDU session-aware policy held by the PCF360 via the NEF330. When the SMF370 receives a "unresponsive container transfer" request from terminal 20 or the PCF360, it may store the information element requesting "unresponsive container transfer" as the context of the PDU session. 【0070】 An established PDU session enters a preserved state. The forwarding procedure when a packet arrives at such a PDU session is described below. 【0071】 Figure 9 is a sequence diagram showing an example of the flow of the incoming packet forwarding determination procedure according to an embodiment of the present invention. The incoming packet forwarding determination procedure is a procedure for determining whether or not to forward an incoming packet to container 382. 【0072】 UPF380 receives a packet from the originating terminal 20A (step S601). Note that the originating terminal 20A is an example of an incoming source. The incoming source may be an external terminal or an external application (such as a network node that executes processing defined in an application program). UPF380 buffers (stores) the packet. Note that UPF380 is an example of a first network node that stores packets to be forwarded to computing resources configured for each subscriber. Next, UPF380 notifies SMF370 of the packet arrival (step S602). 【0073】 The SMF370 determines whether the PDU session context includes "unresponsive container forwarding" (step S603). If the SMF370 determines that the PDU session context includes "unresponsive container forwarding", it decides that the incoming packet should be forwarded to the container (step S604). 【0074】 Furthermore, if SMF370 determines that the PDU session context does not contain "unresponsive container forwarding", it sends a terminal call request to AMF310 (step S605). AMF310 sends the terminal call to the incoming terminal 20B (step S606). The incoming terminal 20B sends a service request to AMF310 (step S607). 【0075】 AMF310 determines whether the service request contains "container forwarding" (step S608). If AMF310 determines that the service request contains "container forwarding", it sends an "Nsmf_PDUSession_UpdateSMContext" request to SMF370 that contains an information element requesting that the incoming packet be forwarded to the container (step S609). Therefore, SMF370 determines that the incoming packet should be forwarded to container 382 (step S610). 【0076】 Furthermore, if AMF310 determines that the service request does not include "container forwarding," it sends an "Nsmf_PDUSession_UpdateSMContext" request to SMF370 that does not contain any information elements requesting the container to forward the incoming packet (step S611). Therefore, SMF370 determines that it should not forward the incoming packet to container 382 (step S612). 【0077】 Figure 10 is a sequence diagram showing an example of the flow of an incoming packet forwarding procedure according to an embodiment of the present invention. The incoming packet forwarding procedure is the procedure for forwarding an incoming packet when the SMF370 determines in the incoming packet forwarding determination procedure shown in Figure 9 that the incoming packet should be forwarded to container 382. 【0078】 SMF370 sends a "Nudm_UECM_Get" request to UDM320 (step S701). The "Nudm_UECM_Get" request is set to NF type=CRMF371, SUPI=SUPI of incoming terminal 20B. 【0079】 UDM320 sends a "Nudm_UECM_Get" response to SMF370 (step S702). The "Nudm_UECM_Get" response includes the CRMF-NF instance ID and the CRMF session ID. 【0080】 Next, SMF370 sends an "Ncrmf_CRMFSession_UpdateCRMContext" request to CRMF371 (step S703). The "Ncrmf_CRMFSession_UpdateCRMContext" request includes the CRMF session ID and the termination information of UPF380. SMF370 is an example of a third network node that sends a notification to CRMF371 that UPF380 has stored packets to forward to container 382. 【0081】 CRMF371 sets the termination point of UPF380 to UCRF381 (and container 382) corresponding to the CRMF session ID (step S704). The termination point of UPF380 is the termination point that receives packets transmitted from UCRF381 (and container 382). CRMF371 is an example of a second network node that notifies UCRF381 (and container 382) of configuration information for forwarding packets. UCRF381 sends termination point information for UCRF381 (and container 382) that receives packets transmitted from UPF380 to CRMF371 (step S705). 【0082】 CRMF371 sends an "Ncrmf_CRMFSession_UpdateCRMContext" response to SMF370 (step S706). SMF370 sets the termination point for UCRF381 (and container 382) to UPF380 (step S707). The termination point for UCRF381 (and container 382) is the termination point that receives packets sent from UPF380. 【0083】 Then, UPF380 forwards the incoming packet to container 382 (step S708). This incoming packet is the packet that UPF380 received from the originating terminal 20A and buffered in step S601 of the incoming packet forwarding determination procedure shown in Figure 9. 【0084】 The core network 30 can forward incoming packets to container 382 using the incoming packet forwarding determination procedure shown in Figure 9 and the incoming packet forwarding procedure shown in Figure 10. 【0085】 (Inter-container communication) Next, we will explain an example where a container discovers and communicates with other containers. For example, we envision a container searching for other containers through the execution of an application program equipped with AI, and autonomously communicating with other containers that it discovers. 【0086】 Hereafter, we will position the container as a UF (User Function) similar to an NF (Network Function). As a prerequisite, we define "Nnrf_UFManagement" as a new service similar to the existing service "Nnrf_NFManagement" and "Nnrf_UFDiscovery" as a new service similar to the existing service "Nnrf_NFDiscovery" in NRF340. In addition, we define "UFProfile" as a new information element similar to the existing information element "NFProfile". 【0087】 Figure 11 is a sequence diagram showing an example of the flow of a container registration procedure according to an embodiment of the present invention. As a prerequisite, when container 382 (or CRMF371) is created, the internal communication IP address and external communication IP address of container 382 are obtained. 【0088】 CRMF371 creates a "UFProfile" for container 382 (step S801). The "UFProfile" includes the UF instance ID, SUPI, internal communication IP address, external communication IP address, CRMF-NF instance ID, etc. 【0089】 CRMF371 sends a "Nnrf_UFManagement_UFRegister" request to NRF340 (step S802). NRF340 is an example of a network management node that manages the network to discover NF instances that provide services. 【0090】 Container 382 may also create its own "UFProfile". In this case, container 382 creates its own "UFProfile" and sends an "Nnrf_UFManagement_UFRegister" request to NRF340. 【0091】 Figure 12 is a sequence diagram showing an example of the flow of an inter-container communication procedure according to an embodiment of the present invention. The source container 382-1 sends "Nnrf_UFDiscovery_Request" to NRF340 (step S901). "Nnrf_UFDiscovery_Request" has the destination SUPI etc. set as the search key. 【0092】 NRF340 sends "Nnrf_UFDiscovery_Response" to source container 382-1 (step S902). "Nnrf_UFDiscovery_Response" contains the "UFProfile" of destination container 382-2. 【0093】 Next, the source container 382-1 initiates communication with the destination container 382-2 (step S903). 【0094】 Through the container registration procedure and inter-container communication procedure, the originating container can discover and communicate with the destination container. 【0095】 (Container movement) Next, we will explain an example of moving a container due to subscriber changes, etc. 【0096】 The core network 30 (CRMF371) may perform one of the following three operating modes when moving containers. 【0097】 In container movement mode 1, the CRMF371 does not move the container. Container movement mode 1 is intended for use when a network is adopted in which UCRFs are aggregated and deployed. 【0098】 In container relocation mode 2, the CRMF371 stops and deletes the currently used container, and then sets up a new container at the destination. 【0099】 In container migration mode 3, CRMF371 keeps the currently used container running while setting up a new container at the destination. Then, after the application within the container has moved its context, CRMF371 stops and deletes the currently used container. 【0100】 Container movement modes 2 and 3 are expected to be used when a network is adopted that distributes the UCRF. 【0101】 Furthermore, CRMF371 may decide whether to move a container or select a container movement mode based on the judgment of PCF360. PCF360 or CRMF371 may receive information such as terminal location (e.g., information obtained from the AMF terminal location disclosure service) and subscriber preferences regarding container movement (e.g., information notified by the terminal when the target container was created, subscriber information), and based on the received information, determine whether to move a container or select a container movement mode. 【0102】 Figure 13 is a sequence diagram showing an example of the flow of a container movement procedure related to container movement mode 2 of an embodiment of the present invention. 【0103】 CRMF371 decides to move the container (step S1001). Next, CRMF371 requests the "UFProfile" of the source container from NRF340 (step S1002). NRF340 responds to CRMF371 with the "UFProfile" of the source container (step S1003). 【0104】 Next, CRMF371 stops and deletes the source container (step S1004). Subsequently, CRMF371 configures the destination container (step S1005). These specific steps may be the same as steps S108 to S110 of the CRMF session establishment procedure shown in Figure 3. 【0105】 The destination container may also be a container that has the same "UFProfile" as the source container. In this case, CRMF371 may assign the destination container the same CRMF session ID as the source container and add a CRMF session ID child number. The destination container obtains an IP address for internal communication and an IP address for external communication. 【0106】 CRMF371 sends a "Nnrf_UFManagement_UFUpdate" request to NRF340 (step S1006). NRF340 registers a "UFProfile" corresponding to the destination container as an override of the "UFProfile" of the source container. 【0107】 Figure 14 is a sequence diagram showing an example of the flow of a container movement procedure related to container movement mode 3 of an embodiment of the present invention. 【0108】 CRMF371 decides to move the container (step S1101). Next, CRMF371 requests the "UFProfile" of the source container 382-3 from NRF340 (step S1102). NRF340 responds to CRMF371 with the "UFProfile" of the source container 382-3 (step S1103). 【0109】 Next, CRMF371 configures the destination container 382-4 (step S1104). The specific procedure may be the same as steps S108 to S110 of the CRMF session establishment procedure shown in Figure 3. 【0110】 Note that the destination container 382-4 may be a container having the same "UFProfile" as the source container 382-3. In this case, CRMF371 may assign the same CRMF session ID to the destination container 382-4 as the source container 382-3 and add a CRMF session ID child number. The CRMF session ID child number may be a sequential number starting from 1, for example. The destination container 382-4 obtains an IP address for internal communication and an IP address for external communication. 【0111】 Next, CRMF371 notifies the destination container 382-4 of the IP address used for internal communication of the source container 382-3 (step S1105). Then, CRMF371 notifies the source container 382-3 of the IP address used for internal communication of the destination container 382-4 (step S1106). 【0112】 The source container 382-3 moves the context to the destination container 382-4 (step S1107). The context may be, for example, various data, application programs, configuration information, etc. 【0113】 Next, CRMF371 stops and deletes the source container 382-3 when the timer expires or for other triggers (step S1108). Then, CRMF371 sends a "Nnrf_UFManagement_UFUpdate" request to NRF340 (step S1109). NRF340 registers a "UFProfile" corresponding to the destination container 382-4 as an overwrite of the "UFProfile" of the source container 382-3. 【0114】 The container relocation procedure shown in Figure 13 or Figure 14 allows the core network 30 to relocate containers in response to subscriber migration or other changes. 【0115】 (Device configuration) Next, we will describe an example of the functional configuration of the base station 10, terminal 20, and various network nodes that perform the processes and operations described above. The base station 10, terminal 20, and various network nodes include the functions to implement the embodiments described above. However, the base station 10, terminal 20, and various network nodes may each have only some of the functions in the embodiments. 【0116】 <Base station 10 and network node> Figure 15 shows an example of the functional configuration of a base station 10. As shown in Figure 15, 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 15 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. Network nodes may have the same functional configuration as the base station 10. Furthermore, network nodes having multiple different functions on the system architecture may be composed of multiple network nodes separated by function. 【0117】 The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 or other network nodes 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 nodes and obtaining information from the received signals, for example, information from a higher layer. 【0118】 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, settings related to communication using NTN. 【0119】 As described in the embodiment, the control unit 140 performs processing related to communication using NTN. The control unit 140 also performs processing related to communication with the terminal 20. Furthermore, the control unit 140 performs processing related to verifying the geographical location of the terminal 20. The signal transmission function in the control unit 140 may be included in the transmission unit 110, and the signal reception function in the control unit 140 may be included in the reception unit 120. 【0120】 <Terminal 20> Figure 16 is a diagram showing an example of the functional configuration of terminal 20. As shown in Figure 16, 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 16 is merely an example. The names of the functional categories and functional units can be anything as long as they can perform the operations according to the embodiment of the present invention. The USIM inserted into terminal 20 may also have a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240, similar to terminal 20. 【0121】 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 acquires 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 network nodes. 【0122】 The configuration unit 230 stores various configuration information received from network nodes 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. 【0123】 The network nodes in this embodiment may be configured as network nodes as described in the following sections. Furthermore, the following communication methods may be implemented. 【0124】 <Configuration of this embodiment> (Section 1) A receiving unit that receives requests for discovery of computing resources set up by a subscriber from computing resources set up by other subscribers or from other network nodes, The system includes a transmission unit that transmits information indicating the attributes of the computing resource to other computing resources or other network nodes. Network node. (Section 2) The information indicating the attributes of the computing resource includes information indicating the address of the communication destination of the computing resource. The network node described in paragraph 1. (Section 3) The receiving unit receives a request to register information indicating the attributes of the computing resource, The system further includes a control unit that controls the storage of information indicating the attributes of the computing resource. A network node as described in paragraph 1 or 2. (Section 4) The steps include receiving a request to discover computing resources set up for a subscriber from computing resources set up for other subscribers or from other network nodes, The process includes the step of transmitting information indicating the attributes of the computing resource to the other computing resource or the other network node. The communication method used by network nodes. 【0125】 In any of the above configurations, a technology is provided that enables computing resources on a network to discover other computing resources. According to paragraph 2, information indicating the address of the communication destination of a computing resource can be transmitted to other computing resources or other network nodes. According to paragraph 3, information indicating the attributes of a computing resource can be stored in response to a request to register information indicating the attributes of the computing resource. 【0126】 (Hardware configuration) The block diagrams (Figures 15 and 16) 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. 【0127】 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. 【0128】 For example, the network node, 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 17 is a diagram showing an example of the hardware configuration of a base station 10 and a terminal 20 according to one embodiment of the present disclosure. The network node may have the same hardware configuration as the base station 10. The USIM may have the same hardware configuration as the terminal 20. 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. 【0129】 In the following explanation, the term "device" can be read as "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. 【0130】 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. 【0131】 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. 【0132】 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 15 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 16 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. 【0133】 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. 【0134】 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. 【0135】 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. 【0136】 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). 【0137】 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. 【0138】 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. 【0139】 Figure 18 shows an example of the configuration of vehicle 2001. As shown in Figure 18, vehicle 2001 includes 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. 【0140】 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. 【0141】 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). 【0142】 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. 【0143】 The Information Services Unit 2012 consists of various devices for providing 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. 【0144】 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. 【0145】 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. 【0146】 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. 【0147】 The communication module 2013 transmits current signals from current sensors input to the electronic control unit 2010 to an external device via wireless communication. The communication module 2013 also transmits, via wireless communication, other signals input to the electronic control unit 2010, including front and rear wheel rotation speed signals obtained by the rotation speed sensor 2022, front and rear wheel air pressure signals obtained by the air pressure sensor 2023, vehicle speed signals obtained by the vehicle speed sensor 2024, acceleration signals obtained by the acceleration sensor 2025, accelerator pedal depression signals obtained by the accelerator pedal sensor 2029, brake pedal depression signals obtained by the brake pedal sensor 2026, shift lever operation signals obtained by the shift lever sensor 2027, and detection signals obtained by the object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc. 【0148】 The communication module 2013 receives various information (traffic information, signal information, distance information, etc.) transmitted from an external device and displays it on the information service unit 2012 installed in the vehicle 2001. 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., installed in the vehicle 2001. 【0149】 (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. 【0150】 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. 【0151】 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). 【0152】 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. 【0153】 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). 【0154】 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. 【0155】 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. 【0156】 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). 【0157】 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. 【0158】 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. 【0159】 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. 【0160】 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. 【0161】 The terms “system” and “network” as used in this disclosure are interchangeable. 【0162】 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. 【0163】 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. 【0164】 In this disclosure, terms such as "Base Station (BS)", "wireless base station", "base station", "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. 【0165】 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. 【0166】 In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably. 【0167】 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. 【0168】 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 be a device mounted on a mobile body, the mobile body itself, etc. The mobile body 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). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operation. 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. 【0169】 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. 【0170】 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. 【0171】 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." 【0172】 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. 【0173】 The reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applicable standard. 【0174】 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." 【0175】 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. 【0176】 In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc. 【0177】 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. 【0178】 A wireless frame may consist of one or more frames in the time domain. Each of these frames in the time domain may be called a subframe. A subframe may further consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology. 【0179】 Numerical logic may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerical logic may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain. 【0180】 A slot may consist of one or more symbols in the time domain (such as OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.). A slot may also be a time unit based on neurology. 【0181】 A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. Minislots may also be called subslots. Minislots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B. 【0182】 Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms. 【0183】 For example, one subframe may be called a Transmission Time Interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one mini-slot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, mini-slot, etc., instead of a subframe. 【0184】 Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each terminal 20 to allocate wireless resources (such as the frequency bandwidth and transmission power available to each terminal 20) in TTI units. However, the definition of TTI is not limited to this. 【0185】 TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI. 【0186】 Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled. 【0187】 A TTI with a time length of 1ms may also be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may also be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc. 【0188】 Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more. 【0189】 A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology. 【0190】 Furthermore, the time domain of RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks. 【0191】 One or more RBs may also be called a Physical RB (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc. 【0192】 Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol. 【0193】 A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a particular neurology system in a given carrier. These common RBs may be identified by an index of the RBs relative to a common reference point of the carrier. A Bandwidth Part (PRB) may be defined and numbered within a given BWP. 【0194】 A BWP may include a BWP for UL (Ultraviolet Link) and a BWP for DL ​​(Download Link). One or more BWPs may be set for a terminal 20 within a single carrier. 【0195】 At least one of the configured BWPs may be active, and terminal 20 does not need to be expected to send or receive a predetermined signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP". 【0196】 The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways. 【0197】 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. 【0198】 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." 【0199】 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). 【0200】 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] 【0201】 10 Base station (RAN) 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 devices 30 Core Network 40 DN 210 Transmitter 220 Receiver 230 Setting section 240 Control Unit 310 AMF 320 UDM 330 NEF 340 NRF 350 AUSF 360 PCF 370 SMF 371 CRMF 380 UPF 381 UCRF 382 containers 390 AF 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive Unit 2003 Steering Department 2004 Accelerator pedal 2005 Brake pedal 2006 Shift Lever 2007 Front Wheel 2008 Rear wheel 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 2013 Communication Module 2021 Current Sensor 2022 Rotation speed sensor 2023 Pneumatic Sensor 2024 Vehicle Speed ​​Sensor 2025 Accelerometer 2026 Brake Pedal Sensor 2027 Shift lever sensor 2028 Object Detection Sensor 2029 Accelerator pedal sensor 2030 Driver Support Systems Department 2031 Microprocessor 2032 memory (ROM, RAM) 2033 Communication port (I / O port)

Claims

[Claim 1] A receiving unit that receives requests for discovery of computing resources set for a subscriber from other computing resources set for other subscribers, or from other network nodes, The system includes a transmission unit that transmits information indicating the attributes of the computing resource to other computing resources or other network nodes, The receiving unit receives a request to register information indicating the attributes of the computing resource, The system further includes a control unit that controls the storage of information indicating the attributes of the computing resource. Network node. [Claim 2] The information indicating the attributes of the computing resource is generated by a function that manages the computing resource, The receiving unit receives a request from the function that manages the computing resource to register information indicating the attributes of the computing resource. The network node according to claim 1. [Claim 3] Information indicating the attributes of the computing resource is generated by the computing resource, The receiving unit receives a request from the computing resource to register information indicating the attributes of the computing resource. The network node according to claim 1. [Claim 4] The information indicating the attributes of the computing resource includes information indicating the address of the communication destination of the computing resource. The network node according to claim 1. [Claim 5] The steps include receiving a request to discover computing resources set up for a subscriber from other computing resources set up for other subscribers, or from other network nodes, The process includes the step of transmitting information indicating the attributes of the computing resource to the other computing resource or the other network node. The steps include receiving a request to register information indicating the attributes of the computing resource, The further step includes controlling the storage of information indicating the attributes of the computing resource. The communication method used by network nodes.

Images