Network node, terminal, and communication method

Abstract

Provided is a network node comprising: a control unit which determines that a terminal is to use a second service, in addition to a first service used by the terminal; a transmission unit which transmits, to a specific network node, a message requesting the detection of an application server that provides the second service; and a reception unit which receives, from the specific network node, a message containing information regarding the application server.

Description

Network node, terminal, and communication method

[0001] The present invention relates to a network node, a terminal, and a communication method.

[0002] 3GPP (registered trademark) (3rd Generation Partnership Project) has introduced a wireless communication system called 5G or NR (New Radio) (hereinafter, the wireless communication system will be referred to as "5G" or "NR") in order to achieve a larger system capacity, a higher data transmission speed, and a lower latency in wireless sections. 5G introduces various wireless technologies to meet the requirement of achieving a throughput of 10 Gbps or more while reducing latency in wireless sections to 1 ms or less. Furthermore, 6G, a future communication system, is also being studied.

[0003] Edge computing, which provides operator and third-party services at locations close to the access point of a UE (terminal), reduces end-to-end latency and reduces the load on the transport network, enabling efficient services, is also being considered. For example, for applications requiring low latency, a system has been proposed in which edge computing functional units are configured in terminals and servers, and communication is enabled using a server located close to the terminal (e.g., Non-Patent Document 1).

[0004] To support service continuity, a procedure has been introduced to transfer application client information from a source server to a target server when a terminal moves, etc. This procedure is called ACR (Application Context Relocation).Federation refers to a situation in which a terminal cooperates with and uses multiple services provided by multiple different ECSPs (Edge Computing Service Providers).

[0005] 3GPP TS 23.558 V18.5.0 (2023-12)

[0006] Regarding the above-mentioned federation, the conventional technology disclosed in Non-Patent Document 1 defines a procedure for federation triggered by a terminal. However, it does not define a procedure for federation triggered by a network node. This poses a problem, for example, in that the opportunities for terminals to use federation are limited.

[0007] The present invention has been made in view of the above points, and has an object to provide a technique for realizing federation triggered by a network node.

[0008] According to the disclosed technology, a network node is provided that includes: a control unit that determines to have a terminal use a second service in addition to a first service that the terminal is using; a transmitting unit that transmits a message to a specific network node requesting discovery of an application server that provides the second service; and a receiving unit that receives a message including information about the application server from the specific network node.

[0009] The disclosed technology provides a technology for realizing federation triggered by a network node.

[0010] FIG. 1 is a diagram for explaining an example of a communication system. FIG. 2 is a diagram for explaining an example of a communication system in a roaming environment. FIG. 3 is a diagram for explaining an example of edge computing. FIG. 4 is a diagram showing a procedure of an EEC trigger. FIG. 5 is a sequence chart of a first embodiment. FIG. 6 is a sequence chart of a second embodiment. FIG. 7 is a diagram showing an example of the functional configuration of a network node 100 in an embodiment of the present invention. FIG. 8 is a diagram showing an example of the functional configuration of a terminal 20 in an embodiment of the present invention. FIG. 9 is a diagram showing an example of the hardware configuration of a terminal 20 and a network node 100 in an embodiment of the present invention. FIG. 10 is a diagram showing an example of the configuration of a vehicle 2001 in an embodiment of the present invention.

[0011] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0012] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies are used as appropriate. However, the existing technologies include, but are not limited to, the existing LTE or the existing NR.

[0013] Furthermore, in the embodiments of the present invention, "configuring" radio parameters and the like may mean that predetermined values ​​are pre-configured, or that radio parameters notified from the network node or the terminal 20 are set. Hereinafter, first, an example of the configuration of a core network that is also used in communication in edge computing will be described, and then the configuration and operation related to edge computing will be described.

[0014] Fig. 1 is a diagram illustrating an example of a communication system corresponding to a core network. As shown in Fig. 1, this communication system is composed of a UE (terminal 20) and multiple network nodes. Hereinafter, it is assumed that one network node corresponds to each function, but multiple functions may be realized by one network node, or multiple network nodes may realize one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0015] The RAN (Radio Access Network) is a network node having a radio access function, which 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 having functions such as terminating the RAN interface, terminating the NAS (Non-Access Stratum), registration management, connection management, reachability management, and mobility management. The UPF is a network node having functions such as a PDU (Protocol Data Unit) session point to the outside that interconnects with the DN (Data Network), packet routing and forwarding, and user plane QoS (Quality of Service) handling. The UPF and the DN constitute a network slice.

[0016] The AMF is connected to the 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). The AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes interconnected via interfaces based on their respective services: Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

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

[0018] 2 is a diagram for explaining an example of a communication system in a roaming environment. As shown in Fig. 2, the network is made up of a UE, which is a terminal 20, and a plurality of network nodes.

[0019] The SEPP is a non-transparent proxy that filters control plane messages between PLMNs (Public Land Mobile Networks). The vSEPP shown in Figure 2 is a SEPP in a visited network, and the hSEPP is a SEPP in a home network.

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

[0021] (Edge Computing) An overview of edge computing related to the technology according to the present embodiment will be described. As described above, edge computing is being considered, which enables efficient services by providing operator and third-party services at locations close to the access point of a UE, thereby reducing end-to-end delays and reducing the load on a transport network.

[0022] For example, for applications that require low latency, an operation is being considered in which a functional unit for edge computing is configured in the terminal and server, and communication is enabled using a server located close to the terminal (for example, Non-Patent Document 1).

[0023] FIG. 3 is a diagram illustrating an example of edge computing. FIG. 3 is also a configuration diagram of a communication system according to this embodiment. As shown in FIG. 3, application communication is performed between an edge application server 40 (EAS) that provides an application service (which may also be called a service) to a terminal 20 and an application client 22 (AC) in the terminal 20 (which may also be called a UE 20). An edge enabler server 30 (EES) and an edge enabler client 21 (EEC) in the terminal 20 perform operations for connecting to an edge data network (EDN). The EAS may also be called a "server."

[0024] 3, the UE 20 is connected to an edge data network and an edge configuration server (ECS) 50 via a core network. The ECS 50 is a server that provides support functions necessary for the EEC 21 to connect to the EES 30. Specifically, the ECS 50 provides EDN configuration information to the UE 20.

[0025] The EAS 40, the EES 30, and the ECS 50 are all examples of network nodes. Furthermore, the EAS 40, the EES 30, and the ECS 50 may all be implemented as a physical device (computer), a container, a POD, or some other method.

[0026] The reference point EDGE-n in the architecture enabling edge applications shown in FIG. 3 is as follows (see Non-Patent Document 1):

[0027] EDGE-1: Enables interoperability between the EES 30 and the EEC 21. Registers and deregisters the EEC 21 to the EES 30. Also searches and acquires configuration information for the EAS 40. Also discovers available EASs 40 in the EDN. Executes service continuity procedures, such as initiating ACR (Application Context Relocation).

[0028] EDGE-2: Enables interoperability between the EES 30 and APIs to retrieve core network functions and network capability information. Supports access via the Service Capability Exposure Function (SCEF) and NEF APIs, or direct access to core network functions from the EES 30 located within the Mobile Network Operator (MNO) trust domain.

[0029] EDGE-3: Enables interoperability between the EES 30 and the EAS 40. Supports registration of the EAS 40 with availability information, such as time constraints and location constraints. Also, deregisters the EAS 40 from the EES 30. Also, discovers the target EAS 40 to support Application Context Transfer (ACT). Also, provides access to network capability information, such as location information. Also, requests the establishment of a data session between the AC 22 and the EAS 40, to which a specific QoS applies, and obtains QoS information. Also, supports service continuity procedures, such as ACR status.

[0030] EDGE-4: Enables interoperability between the ECS 50 and the EEC 21. Provides edge configuration information to the EEC 21.

[0031] EDGE-5: Allows interoperability between the AC 22 and the EEC 21.

[0032] EDGE-6: Enables interoperability between the ECS 50 and the EES 30. Registers EES information to the ECS 50. Also, deregisters EES information from the ECS 50. Also, retrieves target EES information from the ECS 50.

[0033] EDGE-7: Enables interoperability between EAS 40 and APIs to retrieve core network functions and network capability information. Access via SCEF and NEF APIs or direct access to core network functions from EAS 40 located within the MNO trust domain is supported.

[0034] EDGE-8: Enables interoperability between the ECS 50 and APIs to retrieve core network functions and network capability information. Access via SCEF and NEF APIs or direct access to core network functions from the ECS 50 located within the MNO trust domain is supported.

[0035] EDGE-9 enables interoperability between EESs 30. Two EESs 30 connected by EDGE-9 may be included in different EDNs or the same EDN. To support ACR, it discovers target EAS information. It also supports EEC context relocation procedures. It also transparently transfers application context in ACR managed by the EEL (Edge Enabler layer).

[0036] (Regarding ACR and Federation) Non-Patent Document 1 defines a procedure called ACR (Application Context Relocation) as a procedure for supporting service continuity. In ACR, when a terminal 20 moves, for example, information about an application client is transferred from a source EAS to which the terminal 20 is connected before the move to a target EAS to which the terminal 20 is connected after the move.

[0037] Furthermore, the cooperative use of multiple services provided by multiple different ECSPs (Edge Computing Service Providers) by a terminal is called a federation. The cooperative use of multiple services provided by multiple different ECSPs (Edge Computing Service Providers) may also be called ENS (Edge Node Sharing). In this specification, "federation" may be replaced with "ENS."

[0038] (Regarding the Issues) There are only two federation patterns defined in the Edge Application of 3GPP_SA6: the EEC trigger pattern and the EES trigger pattern. Non-Patent Document 1 describes the procedure for only the EEC trigger pattern, but does not describe the procedure for the EES trigger pattern or the EAS trigger pattern, and these are not supported. Note that the trigger conditions are determined by, for example, application service logic.

[0039] As a use case of federation assumed in this embodiment, for example, when terminal 20 is using service B, if the network side (ECSP side) decides to allow terminal 20 to use the functions of service A, the network side proposes federation to terminal 20. However, conventional technology cannot realize such a use case.

[0040] In this embodiment, it is assumed that AI (Artificial Intelligence) or the like provides federation in accordance with the usage status of the service.

[0041] (Outline of the embodiment) This embodiment proposes a new pattern and procedure for federation. Specifically, the EES 30 or the EAS 40 checks the service usage status of the terminal 20 (user) and, after determining that the conditions for executing federation are met, executes the procedure for implementing federation.

[0042] In the following, first, the procedure of the EEC trigger federation (ENS) will be described, then the procedure of the EES trigger will be described as a first embodiment, and the procedure of the EAS trigger will be described as a second embodiment.

[0043] In the following explanations of each sequence (FIGS. 4 to 6), ECSP-A is an ECSP partner of ECSP-B, and ECSP-B is the leading ECSP that provides services to the user (terminal 20). In other words, ECSP-B provides a service that is different from the service provided by ECSP-A. In addition, the user is currently using the service of ECSP-B. Through federation, terminal 20 can use the service of ECSP-A in addition to the service of ECSP-B that it is currently using.

[0044] (Federation Procedure of EEC Trigger) The federation procedure of EEC trigger will be described with reference to FIG.

[0045] In S1 (step 1), the EEC 21 sends an EAS discovery request to the EES 30B (ECSP-B).

[0046] In S2, if the EAS discovery request includes EES information of a partner ECSP (ECSP-A) or if the requested EAS is not available to EES 30B, EES 30B can decide to use the ENS. If the EAS discovery request includes EES information of a partner ECSP, EES 30B can use the EES information after verifying it.

[0047] It should be noted that to verify the information of the partner ECSPs, the EES 30B (ECSP-B) can use the federation agreement between the ECSPs.

[0048] If the EAS discovery request does not include the EES information of the partner ECSP, then in S3, the EES 30B may use an EES acquisition procedure to acquire the EES information of the partner ECSP. The request for EES information acquisition may include an ENS instruction to allow the ECS 50B (ECSP-B) to skip checking the T-EES registered locally at the EES 30B (ECSP-B).

[0049] Once the partner ECSP's EES information is available, in S4, EES 30B (ECSP-B) sends an EAS discovery request to EES 30A (ECSP-A). The EAS discovery request includes information about the MNO providing service to UE 20 (e.g., MNO name, PLMN ID).

[0050] EES 30A (ECSP-A) validates the request and returns an EAS discovery response to EES 30B (ECSP-B) containing one or more discovered candidate EASs based on the serving MNO information received from EES 30B (ECSP-B) and the authorized MNO information registered by the candidate EASs.

[0051] It should be noted that EES 30A (ECSP-A) may use a federation agreement between ECSPs to validate EAS discovery requests.

[0052] In S5, the EES 30B (ECSP-B) provides the discovered information to the EEC 21.

[0053] First Embodiment Next, federation of EES triggers will be described with reference to the sequence chart of Fig. 5. In the following description, the service of ECSP-B is referred to as service B, and the service of ECSP-A is referred to as service A.

[0054] In S101, the EES 30B (ECSP-B) analyzes the service usage status of the user (terminal 20) using AI or the like, and proceeds to S102 if it determines that the service usage pattern of the terminal 20 matches a predetermined pattern. More specifically, when the EES 30B determines that the terminal 20 will use service A in addition to service B through federation, it proceeds to S102.

[0055] For example, the EES 30B holds a machine learning model (e.g., a neural network model) and inputs information indicating the service usage status of the terminal 20 (e.g., traffic and operation information of service A) into the model. If information indicating that "the terminal 20 will be allowed to use service A in addition to service B through federation" is output from the model, the process proceeds to S102.

[0056] To create the above model (or usage pattern), for example, a server (e.g., NWDAF (Network Data Analytics Function)) provided in the core network can be used. For example, the EES 30B acquires information about the communication of the terminal 20 (information indicating the service usage status) from the NWDAF, analyzes the frequency of "using service B after a specific operation while using service A" on the terminal 20, and creates a model (or usage pattern).

[0057] Alternatively, a server (e.g., NWDAF) provided in the core network may hold a model and use the model to determine whether to execute federation, and the EES 30B may acquire the determination result. The EES 30B may then determine whether to execute federation based on the determination result.

[0058] In S102, EES 30B (ECSP-B) requests permission to execute federation by sending a federation request to EEC 21B (terminal 20). The federation request includes, for example, information about service A as a service to be used together with service B.

[0059] In S103, the EEC 21B transmits a federation response to the federation request to the EES 30B (ECSP-B), and the EES 30B (ECSP-B) receives the federation response from the EEC 21B. This federation response includes, for example, permission to execute the federation.

[0060] For example, terminal 20 that receives a federation request displays information requesting permission to use service A through federation, and when the user inputs information indicating permission, a federation response is transmitted from terminal 20. Alternatively, terminal 20 may automatically determine whether to permit or deny the request and transmit the federation response.

[0061] In S104, the EES 30B can obtain the EES information of the partner ECSP using the EES obtainment procedure. The request for obtaining the EES information can include an ENS instruction to allow the ECS 50B (ECSP-B) to skip checking the T-EES registered locally in the EES 30B (ECSP-B).

[0062] In S105, when the EES information of the partner ECSP becomes available, EES 30B (ECSP-B) sends an EAS discovery request to EES 30A (ECSP-A). The EAS discovery request includes information about the MNO that provides services to terminal 20 (e.g., MNO name, PLMN ID).

[0063] The EES 30A (ECSP-A) verifies the request and returns an EAS discovery response including information on one or more discovered candidate EASs to the EES 30B (ECSP-B) in S106.

[0064] The candidate EAS is discovered based on the serving MNO information received from the EES 30B (ECSP-B) and the authorized MNO information registered by the candidate EAS.

[0065] Thereafter, information (profile, address, etc.) of the EAS that provides service A may be notified from EES 30B to EEC 21B.

[0066] <Effects of First Embodiment> According to the first embodiment, federation can be executed based on a trigger by the EES 30B.

[0067] Second Embodiment Next, federation of EAS triggers will be described with reference to the sequence chart of FIG.

[0068] In S201, the EAS 40B (ECSP-B) analyzes the service usage status of the user (terminal 20) using AI or the like, and if it determines that the service usage pattern of the terminal 20 matches a predetermined pattern, it proceeds to S202. More specifically, if the EAS 40B determines that the terminal 20 will use service A in addition to service B through federation, it proceeds to S202.

[0069] For example, the EAS 40B holds a machine learning model (e.g., a neural network model) and inputs information indicating the service usage status of the terminal 20 (e.g., traffic and operation information of service A) into the model. If the model outputs information indicating that "the terminal 20 will be allowed to use service A in addition to service B through federation," the process proceeds to S202.

[0070] To create the above model (or usage pattern), for example, the NWDAF (Network Data Analytics Function) provided in the core network can be used. For example, the EAS 40B acquires information about the communication of the terminal 20 (information indicating the service usage status) from the NWDAF, analyzes the frequency of "using service B after a specific operation while using service A" in the terminal 20, and creates a model (or usage pattern).

[0071] Alternatively, a server (e.g., NWDAF) provided in the core network may hold the model and use the model to determine whether to execute federation, and the EAS 40B may acquire the determination result. The EAS 40B may then decide to execute federation based on the determination result.

[0072] In S202, EAS 40B (ECSP-B) sends an EAS discovery request to EES 30B (ECSP-B), which includes, for example, a requestor identifier (EASID) along with security credentials and an EAS discovery filter that matches the EAS profile.

[0073] If the target Data Network Access Identifier (DNAI) is available at EAS 40B via a user plane path change event, EAS 40B provides the target DNAI to EES 30B.

[0074] The EAS discovery request may include a bundle ID and a bundle type that indicate the proxy bundle case to which the EAS 40B belongs. The EAS discovery request may also include an expected expiration date.

[0075] EAS 40B may also send an EAS discovery request that includes an EAS ID, an application group ID, and EAS synchronization support, indicating that the EAS discovery request is a request to obtain EAS(s) serving the application group ID with the requested EAS ID in order to perform EAS synchronization.

[0076] In S203, EES 30B (ECSP-B) requests permission to execute federation by sending a federation request to EEC 21B (terminal 20). The federation request includes, for example, information about service A as a service to be used together with service B.

[0077] In S204, the EEC 21B transmits a federation response to the federation request to the EES 30B (ECSP-B), and the EES 30B (ECSP-B) receives the federation response from the EEC 21B. This federation response includes, for example, permission to execute the federation.

[0078] For example, terminal 20 that receives a federation request displays information requesting permission to use service A through federation, and when the user inputs information indicating permission, a federation response is transmitted from terminal 20. Alternatively, terminal 20 may automatically determine whether to permit or deny the request and transmit the federation response.

[0079] In S205, if the EAS discovery request does not include the EES information of the partner ECSP, the EES 30B can use an EES acquisition procedure to acquire the EES information of the partner ECSP. The request for EES information acquisition may include an ENS instruction to allow the ECS 50B (ECSP-B) to skip checking the T-EES registered locally at the EES 30B (ECSP-B).

[0080] In S206, when the EES information of the partner ECSP becomes available, EES 30B (ECSP-B) sends an EAS discovery request to EES 30A (ECSP-A). The EAS discovery request includes information about the MNO that provides services to terminal 20 (e.g., MNO name, PLMN ID).

[0081] The EES 30A (ECSP-A) verifies the request and returns an EAS discovery response including information on one or more discovered candidate EASs to the EES 30B (ECSP-B) in S207.

[0082] The candidate EASs are discovered based on the serving MNO information received from the EES 30B (ECSP-B) and the authorized MNO information registered by the candidate EASs.

[0083] In S208, the EES 30B (ECSP-B) transmits an EAS discovery response to the EAS 40B. The EAS discovery response includes information about the discovered EAS.

[0084] Thereafter, information (profile, address, etc.) of the EAS that provides service A may be notified to EEC 21B from EES 30B or EAS 40B.

[0085] <Effects of the Second Embodiment> According to the second embodiment, federation can be executed based on a trigger by the EAS 40B.

[0086] (Variation of Operation) In the first embodiment ( FIG. 5 ), S102 and S103 (federation request and federation response) may not be performed. For example, if EES 30B holds in advance setting information for terminal 20 indicating that "federation may be automatically performed," S102 and S103 are not performed.

[0087] In the first embodiment (FIG. 5), S102 (federation request) is executed, but S103 (federation response) may not actually be executed. In this case, the federation request serves as a notification that federation will be performed.

[0088] In the second embodiment ( FIG. 6 ), steps S203 and S204 (federation request and federation response) may not be performed. For example, if the EES 30B holds in advance setting information for the terminal 20 indicating that "federation may be automatically performed," steps S203 and S204 are not performed.

[0089] In the second embodiment ( FIG. 6 ), S203 (federation request) is executed, but S204 (federation response) may not actually be executed. In this case, the federation request serves as a notification that federation will be performed.

[0090] (Summary of the embodiments) According to the technologies of the first and second embodiments, the federation EES trigger procedure and EAS trigger procedure are realized. In either case, permission is requested from the EEC (user side) after checking the service usage status by utilizing AI or the like using a server in the ECSP. However, as a variation, a method that does not request permission from the EEC can also be used.

[0091] (Device Configuration) Next, a description will be given of an example of the functional configuration of the EES 30, EAS 40, and terminal 20 that perform the processes and operations described above. Hereinafter, the EES 30 and EAS 40 will be collectively referred to as a network node 100.

[0092] <Network Node 100> Fig. 7 is a diagram showing an example of the functional configuration of the network node 100. As shown in Fig. 7, the network node 100 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 7 is merely an example. The names of the functional divisions and functional units may be any as long as they can perform the operations related to the embodiment of the present invention.

[0093] The transmitter 110 has a function of generating a signal to be transmitted to the terminal 20 or a network node and transmitting the signal via a wired or wireless connection. The receiver 120 has a function of receiving various signals transmitted from the terminal 20 or a network node and acquiring, for example, information of a higher layer from the received signal. A communication unit including the transmitter 110 and the receiver 120 may be configured.

[0094] The setting unit 130 stores pre-set setting information and various setting information to be transmitted to the terminal 20 or the network node in a storage device, and reads out the information from the storage device as needed. The control unit 140 controls the network node 100. The function unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and the function unit related to signal reception in the control unit 140 may be included in the receiving unit 120. The transmitting unit 110 and the receiving unit 120 may be called a transmitter and a receiver, respectively.

[0095] <Terminal 20> Fig. 8 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 8, the 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 Fig. 8 is merely an example. The names of the functional divisions and functional units may be any as long as they can perform the operations related to the embodiment of the present invention.

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

[0097] The setting unit 230 stores various pieces of setting information received from the network node by the receiving unit 220 in a storage device and reads them from the storage device as needed. The setting unit 230 also stores setting information that is set in advance. The content of the setting information is, for example, information related to edge computing.

[0098] The control unit 240 controls the terminal 20. The functional unit in the control unit 240 related to signal transmission may be included in the transmitting unit 210, and the functional unit in the control unit 240 related to signal reception may be included in the receiving unit 220. The transmitting unit 210 and the receiving unit 220 may be called a transmitter and a receiver, respectively.

[0099] (Hardware Configuration) The block diagrams (FIGS. 7 and 8) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or the multiple devices.

[0100] Functions include, but are not limited to, judgment, determination, assessment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0101] For example, the network node 100 and the terminal 20 according to an embodiment of the present disclosure may function as a computer that performs processing of the communication method of the present disclosure. Fig. 9 is a diagram illustrating an example of the hardware configuration of the network node 100 and the terminal 20 according to an embodiment of the present disclosure. The network node 100 and the 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.

[0102] In the following description, the term "apparatus" can be read as a circuit, a device, a unit, etc. The hardware configuration of the network node 100 and the terminal 20 may be configured to include one or more of the apparatuses shown in the figure, or may be configured to exclude some of the apparatuses.

[0103] Each function in the network node 100 and the terminal 20 is realized by loading specified software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication via the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

[0104] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.

[0105] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002 and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the network node 100 shown in FIG. 7 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. For example, the control unit 240 of the terminal 20 shown in FIG. 8 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

[0106] The storage device 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), etc. The storage device 1002 may also be called a register, a cache, a main memory, etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

[0107] The secondary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of the storage device 1002 and the secondary storage device 1003.

[0108] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated.

[0109] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0110] 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 may be configured using different buses between each device.

[0111] Furthermore, the network node 100 and the terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0112] 10 shows an example configuration of a vehicle 2001. As shown in FIG. 10 , the 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 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example. For example, the network node 100 or the terminal 20 may be included in the communication module 2013.

[0113] The drive unit 2002 is configured, for example, by 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 operated by the user.

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

[0115] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

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

[0117] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driving burden on the driver, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), 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. In addition, the driving assistance system unit 2030 transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

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

[0119] 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 an external device. For example, it transmits and receives various information to and from the external device 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, a terminal, a network node, or the like.

[0120] The communication module 2013 may transmit, via wireless communication, to an external device at least one of signals from the various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (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 be referred to as input units that accept input.

[0121] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle-to-vehicle information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker 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 external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the 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 to 2029, etc. provided in the vehicle 2001.

[0122] Furthermore, when the communication module 2013 includes the network node 100 (or the terminal 20), the communication module 2013 can perform the operations of the network node 100 (or the terminal 20) described above.

[0123] This specification discloses at least the configurations described in the appendices below.

[0124] <Additional Notes> (Additional Item 1) A network node comprising: a control unit that determines to have a terminal use a second service in addition to a first service currently being used by the terminal; a transmitter that transmits a message to a specific network node requesting discovery of an application server that provides the second service; and a receiver that receives a message from the specific network node including information about the application server. (Additional Item 2) The network node according to Additional Item 1, wherein the transmitter transmits a federation request to the terminal, and the receiver receives a federation response from the terminal. (Additional Item 3) A network node comprising: a control unit that determines to have the terminal use a second service in addition to a first service provided to the terminal; and a transmitter that transmits a message to the specific network node requesting discovery of a network node that provides the second service. (Additional Item 4) A terminal comprising: a receiver that receives a federation request from a network node that determines to use the second service in addition to use of the first service, and a transmitter that transmits a federation response to the network node. (Supplementary Claim 5) A terminal comprising: a receiver that receives a federation request from a second network node based on a request from a first network node that decides to use a second service in addition to using a first service; and a transmitter that transmits a federation response to the second network node. (Supplementary Claim 6) A communication method executed by a network node, comprising: determining to have the terminal use a second service in addition to a first service that the terminal is using; transmitting a message to a specific network node requesting discovery of an application server that provides the second service; and receiving a message from the specific network node that includes information about the application server.

[0125] Any of Supplementary Items 1 to 6 provides a technique for realizing federation triggered by a network node. Supplementary Item 2 makes it possible to request permission to execute federation from a terminal.

[0126] (Supplementary Notes on the Embodiments) Although the 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, and replacements. While specific numerical examples have been used to facilitate understanding of the invention, 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; matters described in two or more items may be used in combination as needed, and matters described in one item may apply to matters described in another item (as long as there is no contradiction). Boundaries between functional units or processing units in functional block diagrams do not necessarily correspond to boundaries between physical components. The operations of multiple functional units may be performed physically by a single component, or the operations of a single functional unit may be performed physically by multiple components. The order of processing procedures described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the network node 100 and the terminal 20 have been described using functional block diagrams. However, such devices may be realized by hardware, software, or a combination thereof. The software operated by the processor of the network node 100 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each 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.

[0127] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling), broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0128] Each aspect / embodiment described in the present disclosure may be implemented using any of the following standards: LTE (Long Term Evolution), LTE-Advanced (LTE-A), 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 (x is, for example, an integer or a decimal number)), 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)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802.34 ( The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of LTE and / or LTE-A with 5G).

[0129] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be rearranged unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.

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

[0131] The information or signals described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0132] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be transmitted to another device.

[0133] In the present disclosure, the determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0134] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0135] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

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

[0137] Note that terms described 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 a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0138] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0139] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or other corresponding information. For example, a radio resource may be indicated by an index.

[0140] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0141] In the present disclosure, terms such as "base station (BS)," "radio base station," "base station device," "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. A base station may also be referred to by terms such as a macrocell, a small cell, a femtocell, and a picocell.

[0142] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage.

[0143] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

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

[0145] 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 some other suitable terminology.

[0146] Either the network node 100 or the terminal 20 may be referred to as a transmitting device, a receiving device, a communication device, or the like. Note that either the network node 100 or the terminal 20 may be a device mounted on a mobile object, the mobile object itself, or the like. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. Furthermore, the mobile object may be a mobile object that moves autonomously based on an operation command, a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (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 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.

[0147] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present 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, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0148] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station may be configured to have the functions of the user terminal described above.

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

[0150] The terms "connected," "coupled," or any variation thereof, refer to 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" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0151] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

[0152] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0153] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

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

[0155] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0156] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0157] In the present 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 "coupled" may also be interpreted in the same way as "different."

[0158] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0159] Although the present disclosure has been described in detail above, it is 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 spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0160] 10 Base station 20 Terminal 21 EEC 22 AC 30 EES 40 EAS 50 ECS 100 Network node 110 Transmitter 120 Receiver 130 Setting unit 140 Controller 210 Transmitter 220 Receiver 230 Setting unit 240 Controller 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device

Claims

1. A network node comprising: a control unit that determines to have a terminal use a second service in addition to a first service currently used by the terminal; a transmission unit that transmits a message to a specific network node requesting discovery of an application server that provides the second service; and a reception unit that receives a message including information on the application server from the specific network node.

2. The network node according to claim 1, wherein the transmitter transmits a federation request to the terminal, and the receiver receives a federation response from the terminal.

3. A network node comprising: a control unit that determines to allow a terminal to use a second service in addition to a first service provided to the terminal; and a transmission unit that transmits a message to a specific network node requesting that the specific network node discover a network node that provides the second service.

4. A terminal comprising: a receiver that receives a federation request from a network node that determines the use of a second service in addition to the use of a first service; and a transmitter that transmits a federation response to the network node.

5. A terminal comprising: a receiver that receives a federation request from a second network node based on a request from a first network node that determines the use of a second service in addition to the use of a first service; and a transmitter that transmits a federation response to the second network node.

6. A communication method executed by a network node, comprising: determining to have a terminal use a second service in addition to a first service currently used by the terminal; sending a message to a specific network node requesting discovery of an application server that provides the second service; and receiving a message from the specific network node that includes information about the application server.

Images