Network node and communication method

Abstract

This network node comprises: a control unit that creates a second database for storing data in a first database, and disposes the second database in the same environment as a specific network node; and a transmission unit that transmits destination information of the second database so that the specific network node can access the second database. The network node functions as the first database.

Description

Network node and communication method

[0001] The present invention relates to a network node in a communication system 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] Furthermore, in 5G networks, a Unified Data Repository (UDR) is used to store and retrieve subscriber data. The UDR is an example of a subscriber database (DB).

[0004] 3GPP TS 29.504 V18.4.0 (2023-12)3GPP TS 23.502 V18.4.0 (2023-12)3GPP TS 23.288 V18.4.0 (2023-12)3GPP TS 23.501 V18.4.0 (2023-12)

[0005] DBs such as UDR may take a long time to access if the access scale becomes large. In addition, the long access time may cause processing delays, which may affect the response time of the entire 5G network.

[0006] Furthermore, recent innovations in AI technology are likely to lead to an increase in information references for creating AI models, which is expected to further increase the load on database access.

[0007] The present invention has been made in view of the above-mentioned points, and has as its object to provide a technique for reducing the access load to a database used on a network.

[0008] According to the disclosed technology, there is provided a network node that functions as the first database, comprising: a control unit that creates a second database that stores data in the first database and places the second database in the same environment as a specific network node; and a transmission unit that transmits destination information of the second database so that the specific network node can access the second database.

[0009] The disclosed technology provides a technology for reducing the access load to a database used in a network.

[0010] 1 is a diagram for explaining an example of a communication system. FIG. 1 is a diagram for explaining an example of a communication system in a roaming environment. FIG. 2 is a diagram for explaining a connection configuration of a UDR. FIG. 3 is a diagram for explaining a status of access to a DB. FIG. 2 is a diagram for explaining an overall outline of an embodiment of the present invention. FIG. 3 is a diagram for explaining a first embodiment. FIG. 4 is a sequence chart of the first embodiment. FIG. 4 is a diagram for explaining a second embodiment. FIG. 5 is a diagram for explaining a third embodiment. FIG. 5 is a sequence chart of the third embodiment. FIG. 6 is a sequence chart of the third embodiment. FIG. 7 is a diagram for explaining an example of load information (Input data). FIG. 8 is a diagram for explaining an example of load information (Output data). FIG. 9 is a diagram for explaining a fourth embodiment. FIG. 10 is a sequence chart of the fourth embodiment. FIG. 11 is a diagram for explaining a fifth embodiment. FIG. 12 is a sequence chart of the fifth embodiment. FIG. 13 is a sequence chart of the fifth embodiment. FIG. 14 is a diagram for explaining an example of the functional configuration of a network node 100 in an embodiment of the present invention. FIG. 15 is a diagram for explaining an example of the functional configuration of a terminal 20 in an embodiment of the present invention. FIG. 16 is a diagram for explaining an example of the hardware configuration of a terminal 20 and a network node 100 in an embodiment of the present invention. FIG. 17 is a diagram for explaining 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 terminal 20 are set. Hereinafter, first, a configuration example of a 5G core network, which is an example of a network to which the technology according to the present invention is applied, will be described, and then the configuration and operation according to the embodiments of the present invention 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) 50, NRF (Network Repository Function) 60, UDM (Unified Data Management) 30, AUSF (Authentication Server Function), PCF (Policy Control Function) 40, AF (Application Function), and UDR (User Data Repository) 70. The AMF, SMF, NSSF, NEF 50, NRF 60, UDM 30, AUSF, PCF 40, AF, and UDR 70 are network nodes connected to each other via interfaces based on their respective services, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, Naf, and Nudr.

[0017] The SMF is a network node having 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 50 is a network node having a function of notifying other NFs (Network Functions) of capabilities and events. The NSSF is a network node having functions such as selecting a network slice to which a UE connects, determining an allowed NSSAI (Network Slice Selection Assistance Information), determining an NSSAI to be set, and determining an AMF set to which a UE connects. The PCF 40 is a network node having a function of controlling network policies. The AF is a network node having a function of controlling application servers. The NRF 60 is a network node having a function of discovering NF instances that provide services. The UDM 30 is a network node that manages subscriber data and authentication data. The UDM 30 is connected to the UDR 70 that holds 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] (About UDR) As described in Non-Patent Document 1 (3GPP TS29.504), UDR (Unified Data Repository) is a network element of 5GC, and supports functions such as "storing and retrieving subscription data," "storing and retrieving policy data," "storing and retrieving public structure data," and "subscribing to notifications and notifying changes to subscribed data."

[0022] Figure 3 shows the details of the connection configuration related to UDR (Non-Patent Document 1). As shown in Figure 3, NFs such as UDM, PCF, and NEF access UDR data using the Nudr interface. The Nudr interface can also be used for the HSS (Home Subscriber Server), which is an LTE subscriber DB.

[0023] (Regarding the Problem) FIG. 4 shows a situation in which the UDM 30, the PCF 40, and the NEF 50 each access a DB (database) such as a UDR.

[0024] DBs such as UDR may take a long time to access if the access scale becomes large. In addition, the long access time may cause processing delays, which may affect the response time of the entire 5G network.

[0025] Furthermore, recent innovations in AI technology are likely to lead to an increase in information references for creating AI models, which is expected to further increase the load on database access.

[0026] Hereinafter, a technique for reducing the access load to a DB will be described as a technique according to this embodiment.

[0027] (Outline of the Embodiments) In this specification, first to fifth embodiments will be described. An outline of each embodiment will be described with reference to FIG. 5. Note that the "subscriber DB 75" in the following description is, for example, a UDR or an HSS. Hereinafter, the "subscriber DB 75" is assumed to be a UDR, but is not limited to a UDR.

[0028] In the first to third embodiments, the subscriber DB 75 creates one or more read replicas (reference DBs) that are dedicated to reading data that is updated infrequently, and performs scale out (distributed placement). After distributing the read replicas, the UDM 30, PCF 40, and NEF 50 are notified of information on the access destination for data acquisition. FIG. 5 shows read replicas 76 to 78 created from the subscriber DB 75 as distributed read replicas. The subscriber DB 75 is referred to as an update DB because information updates are performed on the subscriber DB 75. The Query (Get) shown in FIG. 5 indicates access for acquiring (reading) information.

[0029] In the fourth embodiment, a Coordinator NF 80 is provided as a network node for primary data storage for updating data in read replicas. That is, in the fourth embodiment, when data that is updated infrequently is updated, the data is stored in the Coordinator NF 80 in order to update the data in the read replicas. When there is no access to the read replicas, the data stored in the Coordinator NF 80 is used to update the data in each read replica.

[0030] The fifth embodiment introduces an SCP (Service Communication Proxy) 90. This solves the problem in the first to third embodiments that it is necessary to add access destinations to the UDM 30, PCF 40, and NEF 50. The SCP (Service Communication Proxy) 90 determines the destination of a message from the request content of the received message.

[0031] In this specification, it is assumed that the first to fifth embodiments are implemented in combination, but it is not necessary to implement all of the first to fifth embodiments in combination. For example, the technology according to the invention in each embodiment may be implemented independently. Each embodiment will be described in detail below.

[0032] First Embodiment First, a description will be given of a first embodiment. In the first embodiment, read replicas (reference DBs) of the subscriber DB 75 are statically distributed.

[0033] In the first embodiment, the UDM 30, the PCF 40, and the NEF 50 each register a subscription with the NRF 60, and when a read replica is created, they receive notification of change information from the NRF 60. Note that this communication may be indirect communication via an SCP.

[0034] An outline of the processing according to the first embodiment will be described with reference to Fig. 6. In Fig. 6, it is assumed that the UDM 30, the PCF 40, and the NEF 50 are each connected to the subscriber DB 75.

[0035] In S1, the subscriber DB 75 creates read replicas (76 to 78 in FIG. 6) for data that is updated infrequently, and distributes the created read replicas to the same environment as the subscriber DB 70. Placing a read replica in the same environment as the subscriber DB 70 means, for example, placing the read replica in the same data center as the data center where the subscriber DB 70 is located. The read replica only accepts queries from the UDM 30 / PCF 40 / NEF 50. In other words, only data is read from the UDM 30 / PCF 40 / NEF 50.

[0036] Note that "the subscriber DB 75 creating and arranging a reference DB that will be a read replica" may mean, for example, starting a server or container that functions as the reference DB and storing data. Also, "the subscriber DB 75 creating and arranging a reference DB that will be a read replica" may mean that the subscriber DB 75 instructs another device to create and arrange a reference DB that will be a read replica.

[0037] In the first embodiment, the read replica is not limited to being placed in the same environment as the subscriber DB 70. The read replica may be placed in an environment that can be accessed by the UDM 30 / PCF 40 / NEF 50. Furthermore, "UDM 30 / PCF 40 / NEF 50" means "UDM 30, PCF 40, and NEF 50, respectively."

[0038] After the read replica is deployed, in S2, the subscriber DB 75 notifies the NRF 60 of the change information about itself and updates the information. In Figure 6, "UDR instance (Read-only)" means that the read replica is deployed as read-only. The notification also includes destination information for the read replica.

[0039] In S3, the NRF 60 notifies the UDM 30 / PCF 40 / NEF 50 of the update information (specifically, an instruction to add a destination to the read replica).

[0040] In S4, the UDM 30 / PCF 40 / NEF 50 uses the update information to start communication with the read replica.

[0041] <First Embodiment: Processing Sequence> Next, an example of a processing sequence in the first embodiment will be described with reference to Fig. 7. Note that each message shown in Fig. 7 is basically a message described in Non-Patent Document 2 (TS23.502). However, in order to realize operations related to read replicas, the messages contain new information such as "connection destination information."

[0042] In S101, the UDM 30 / PCF 40 / NEF 50 transmits an Nnrf_NFManagement_NFStatusSubscribe Request to the NRF 60. In S102, the NRF 60 returns an Nnrf_NFManagement_NFStatusSubscribe Response to the UDM 30 / PCF 40 / NEF 50.

[0043] In S103, the subscriber DB 75 sends an Nnrf_NFManagement_NFUpdate Request to the NRF 60. This message includes "NF feature, connection destination information" as input data.

[0044] In S104, based on the message of S103, the NRF 60 updates the NF profile in the subscriber DB 75. In S105, the NRF 60 returns Nnrf_NFManagement_NFUpdate_response (Output data) to the subscriber DB 70.

[0045] In S106, the NRF 60 sends an Nnrf_NFManagement_NFStatusNotify message to the UDM 30 / PCF 40 / NEF 50. This message notifies the UDM 30 / PCF 40 / NEF 50 of connection destination information for the read replica 76. In S107, communication between the read replica 76 and the UDM 30 / PCF 40 / NEF 50 begins.

[0046] <Regarding Information Elements of Input Data> In the Nnrf_NFManagement_NFUpdate service operation (5.2.7.2.3 of Non-Patent Document 2) in S103 to S105 of Fig. 7, the Input data of the conventional technology includes an NF instance ID as Required data, and an updated NF profile as Optional, as described in "If replacing the full NF profile, the full NF profile shall be provided. If updating parts of the NF profile, the NF profile elements that need to be updated shall be provided."

[0047] On the other hand, in this embodiment, in addition to the above information, "NF feature: Read-only" and "Connection destination information: FQDN or IP address of read-only NF(NOTE)" are included in the Input data as "Inputs, Optional:". Note that the above Note indicates that when there is a plurality of connection destination information, they are notified in a list.

[0048] <Effects of First Embodiment> The technology according to the first embodiment allows for the placement of a read-only read replica, thereby reducing the access load to the subscriber DB 75 .

[0049] Second Embodiment Next, a second embodiment will be described. In the second embodiment, read replicas (reference DBs) of the subscriber DB 75 are distributed to each NF. Except for the method of arranging the read replicas, the second embodiment is the same as the first embodiment. Specifically, it is as follows.

[0050] The processing according to the second embodiment will be described with reference to Fig. 8. In Fig. 8, it is assumed that the UDM 30, the PCF 40, and the NEF 50 are each connected to the subscriber DB 75.

[0051] In S1, the subscriber DB 75 creates read replicas (76-78) for data that is updated infrequently, and distributes the created read replicas to the same environment as each NF. Placing a read replica in the same environment as an NF means, for example, placing the read replica in the same data center as the NF. Placing a read replica in the same environment as an NF may also mean placing the read replica on the same server as the server that contains the NF.

[0052] 8, the UDM 30 and the read replica 76 are placed in the same environment, the PCF 40 and the read replica 77 are placed in the same environment, and the NEF 50 and the read replica 78 are placed in the same environment. The read replicas only accept queries from the UDM 30 / PCF 40 / NEF 50. In other words, only data is read from the UDM 30 / PCF 40 / NEF 50.

[0053] In S2, after the read replica is placed, the subscriber DB 75 notifies the NRF 60 of the change information about itself and updates the information.

[0054] In S3, the NRF 60 notifies the UDM 30 / PCF 40 / NEF 50 of the update information (specifically, the added destinations). In S4, the UDM 30 / PCF 40 / NEF 50 uses the update information to start communication with the read replica.

[0055] The processing sequence of the second embodiment is the same as the processing sequence of the first embodiment shown in FIG.

[0056] <Input data information elements> Here, differences from the first embodiment will be described. In the second embodiment, the "NF feature: Read-only" in the first embodiment becomes "NF feature: tightly coupled read-only." In other words, the fact that the target NF and read replica are "tightly coupled" is added.

[0057] <Effects of Second Embodiment> In addition to the effects of the first embodiment, the technology according to the second embodiment has the effect of reducing delays in communication between the UDM 30 / PCF 40 / NEF 50 and the read replica.

[0058] Third Embodiment Next, a third embodiment will be described. In the third embodiment, read replicas are dynamically distributed and allocated in response to a temporary increase in access. An overview of the third embodiment will be described with reference to FIG. 9 .

[0059] 9 , the third embodiment includes a Consumer 400 and a Network Data Analytics Function (NWDAF) 300. The Consumer 400 may be an independent node, an Operation and Maintenance (OAM) node, or a UDR. The NWDAF 300 is a function (node) that collects and analyzes various data within the network and returns the results.

[0060] In S1, the Consumer 400 notifies (sets) the collected information (UDR information) and thresholds to the NWDAF 300. At the time of this notification, the Consumer 400 also notifies the NWDAF 300 whether the scale out (distributed placement) destination is the same environment as the subscriber DB 75 (the method of the first embodiment) or each NF environment (the method of the second embodiment).

[0061] In S2, the NWDAF 300 collects load information from the subscriber DB 75 via the NRF 60. When the OAM is the Consumer 400, the NWDAF 300 may pass the collected information directly to the Consumer 400 (S2-a).

[0062] In S3, the NWDAF 300 performs data analysis to determine whether the load on the subscriber DB 75 exceeds a threshold. If the load exceeds the threshold, the NWDAF 300 decides to perform scale out (distributed placement). If the OAM is the Consumer 400, the OAM may perform data analysis and decide to perform scale out (distributed placement).

[0063] In S4, the NWDAF 300 instructs the subscriber DB 75 to execute scale out (distributed placement). If the OAM is the Consumer 400, the OAM instructs the subscriber DB 75 to execute scale out. After the scale out (distributed placement), the operation of the first embodiment or the operation of the second embodiment is performed.

[0064] The load information is collected periodically, for example. If the load on the subscriber DB 75 falls below a threshold as a result of the load information analysis by the NWDAF 300 (or the OAM), the subscriber DB 75 may, for example, reduce the number of read replicas. The subscriber DB 75 may also delete all read replicas and return to the state before the read replicas were created.

[0065] Third Embodiment: Processing Sequence Next, an example of a processing sequence in the third embodiment will be described with reference to FIGS.

[0066] 10, the UDM 30 / PCF 40 / NEF 50 transmits an Nnrf_NFManagement_NFStatusSubscribe Request to the NRF 60. In S302, the NRF 60 transmits an Nnrf_NFManagement_NFStatusSubscribe Response to the UDM 30 / PCF 40 / NEF 50. These messages are described in Non-Patent Document 2.

[0067] In S303, the Consumer 400 sends Nnwdaf_AnalyticsSubscription_Subscribe (Analytics ID="NF load information", input data) to the NWDAF 300. Details of the input data in this message will be described later. The procedure related to Nnrf_NFManagement_NFStatus_Subscribe is described in Non-Patent Document 3 (TS23.288), but the message in the third embodiment includes information that is not present in the prior art.

[0068] In S304, the NWDAF 300 subscribes to load information of the subscriber DB 75 from the NRF 60 based on the message received in S303.

[0069] If the OAM is the Consumer 400, the NWDAF 300 transmits an Nnwdaf_AnalyticsSubscription_Notify to the Consumer 400 in S305.

[0070] The NWDAF 300 (or the Consumer 400) performs data analysis in S306 and determines to perform Scale out (distributed placement) in S307. In S308, the NWDAF 300 transmits an Nnwdaf_AnalyticsSubscription_Notify that specifies the "distribution method." Note that this example shows a case where the Consumer 400 is the subscriber DB 75 (UDR).

[0071] Thereafter, as shown in FIG. 11, the same processing sequence as in the first embodiment (and the second embodiment) is executed.

[0072] <Information Elements of Input Data> Fig. 12 shows an example of input data for "Analytics ID: NF load information" in the message of S303. "NF load" and "NF status" are the same as those described in Non-Patent Document 3. "Threshold value(s)" and "distribution method" are new input data. A threshold value required for data analysis is set in "Threshold value(s)." The distribution method (e.g., read-only, tightly coupled read-only) used when distributing read replicas is set in "distribution method."

[0073] <About Information Elements of Output Data> FIG. 13 shows an example of output data for "Analytics ID: NF load information" in the message of S308. Information elements other than "distribution method" are the same as those described in Non-Patent Document 3. "Distribution method" is new output data. In "distribution method," the distribution method (e.g., read-only, tightly coupled read-only) to be used when distributing and placing read replicas is set. Based on this distribution method information, the subscriber DB 75 creates and places read replicas using the method of the first embodiment or the method of the second embodiment.

[0074] <Effects of the Third Embodiment> The technology according to the third embodiment makes it possible to dynamically allocate read replicas depending on the load situation.

[0075] Fourth Embodiment Next, a fourth embodiment will be described. In the fourth embodiment, data is updated in a read replica (reference DB).

[0076] In other words, when data that is infrequently updated and stored in the read replica is updated in the subscriber DB 75, the data must also be updated in the read replica. For this purpose, as shown in Fig. 14, a Coordinator NF 80 is provided. The processing of the fourth embodiment will be described with reference to Fig. 14.

[0077] In S1, the subscriber DB 75 notifies the Coordinator NF 80 of update information. The update information is, for example, information (data) newly written from the UDM 30 / PCF 40 / NEF 50. The Coordinator NF 80 temporarily holds the update information.

[0078] In S2, the Coordinator NF 80 notifies (sends a signal to) each read replica that it has received the update information. In other words, the Coordinator NF 80 requests each read replica to acquire the update information.

[0079] In S3, each read replica acquires update information from the Coordinator NF 80 at a time when there is no access from the UDM 30 / PCF 40 / NEF 50 or the like.

[0080] The Coordinator NF80 may delete the update information it is holding after a predetermined time has elapsed, or may delete the update information after confirming that the update information has been acquired from all read replicas that are expected to acquire the update information.

[0081] <Fourth Embodiment: Processing Sequence> Next, an example of a processing sequence in the fourth embodiment will be described with reference to Fig. 15. In S401, the Coordinator NF 80 sends a Nudr_DataRepository_subscribe request to the subscriber DB 75. In S402, the subscriber DB 75 generates a Subscription, and in S403, returns a Nudr_DataRepository_subscribe response to the Coordinator NF 80.

[0082] In S404, it is assumed that the subscriber DB 75 receives the updated information. In S405, the subscriber DB 75 notifies the Coordinator NF 80 of the updated information.

[0083] In S406, the Coordinator NF 80 sends a Nudr_DataRepository_query request (Input: NF instance ID) to the read replica 76. This message requests the read replica 76 to obtain update information.

[0084] In S407 , the read replica 76 returns a Nudr_DataRepository_query response to the Coordinator NF 80 .

[0085] In S408, the read replica 76 sends a Query Request (Input: NF instance ID) to the Coordinator NF 80. In S409, the Coordinator NF 80 returns a Query Response (Output) including update information to the read replica 76.

[0086] <Regarding New Information Elements> The following describes new information elements (messages) used in the fourth embodiment. Nudr_DataRepository_query is an information element sent from the Coordinator NF 80 to the read replica 76, and includes an NF instance ID as "Inputs, Required:".

[0087] The Query request is an information element sent from the read replica 76 to the Coordinator NF 80, and includes an NF instance ID as "Inputs, Required:".

[0088] The Query response is an information element transmitted from the Coordinator NF 80 to the Read Replica 76, and includes a Result indication as "Outputs, Required:". The Result indication includes, for example, update information linked to the NF instance ID of the subscriber DB 75 (UDR).

[0089] In the fourth embodiment, by providing the Coordinator NF 80, the subscriber DB 75 can unilaterally send update information without having to synchronize with the update timing of the read replica, thereby reducing the processing load, such as multiple retransmissions due to update errors.

[0090] Fifth Embodiment Next, a fifth embodiment will be described. In the first to third embodiments described above, it is necessary to add (notify) the read replica destination to the UDM 30 / PCF 40 / NEF 50 via the NRF 60, which may affect existing settings. Therefore, in the fifth embodiment, an SCP 90 that supports indirect communication is introduced, as shown in FIG. 16 . Based on the request information (update or query) received from the UDM 30 / PCF 40 / NEF 50, the SCP 90 determines the transfer destination of the received request information.

[0091] That is, after distributing the subscriber DB 75 by creating a read replica, destination change setting (routing setting) is performed between the SCP 90 and the subscriber DB 75 .

[0092] This setting allows the SCP 90 to route update information to the subscriber DB 75 and route query requests (information read requests) to the read replica, as shown in FIG.

[0093] Fifth Embodiment: Processing Sequence Next, an example of a processing sequence in the fifth embodiment will be described with reference to FIGS.

[0094] 17, it is assumed that the SCP 90 and the NRF 60 are linked. In S502, the NF service registration procedure is performed (4.17.1, TS23.502 (Non-Patent Document 2)). In this procedure, a Routing Binding indication is also sent (Table 6.3.1.0-1, TS23.501 (Non-Patent Document 4)). In addition, in this procedure, the instance ID of the UDR is set in this NF instance.

[0095] In S503, the NF service registration procedure is executed (4.17.1, TS23.502 (Non-Patent Document 2)).

[0096] In S504, the subscriber DB 75 sends an Nnrf_NFManagement_NFUpdate_request (Input data: NF feature, connection destination information) to the NRF 60. This message has the same content as the message in S103 in the first embodiment. In S505, the NRF 60 updates the NF profile, and in S506, returns an Nnrf_NFManagement_NFUpdate_response (Output data) to the subscriber DB 75. Through these procedures, the NRF 60 stores the destination information (connection destination information) of the read replica 76 as updated profile information in the subscriber DB 75.

[0097] 18, the SCP 90 acquires update information from the NRF 60. The update information is information indicating that a read replica (=UDR (Read-only)) has been added as an NF instance, and includes destination information of the read replica.

[0098] In S508, the SCP 90 executes settings for changing the routing from the contents of the service request based on the update information acquired in S507. Fig. 19 shows the operation after the settings.

[0099] Steps S511 to S514 show the procedure for updating information in the subscriber DB 75. In step S511, the UDM 30 / PCF 40 / NEF 50 sends a service request (update) to the SCP 90. In step S512, the SCP 90 transfers the service request (update) to the subscriber DB 75. The subscriber DB 75 updates the information and returns a service response to the SCP 90 in step S513. In step S514, the SCP 90 transfers the service response to the UDM 30 / PCF 40 / NEF 50.

[0100] Steps S521 to S525 show the query procedure for acquiring information from the read replica 76.

[0101] In S521, the UDM 30 / PCF 40 / NEF 50 sends a service request (Query (Get)) indicating an information acquisition request to the SCP 90. In S522, when the SCP 90 detects that the service request indicates an information acquisition request, it changes the routing so that the service request is forwarded to the read replica.

[0102] In S523, the SCP 90 transfers the service request to the read replica 76. In S524, the read replica 76 returns a service response including the read information to the SCP 90. In S525, the SCP 90 transfers the service response to the UDM 30 / PCF 40 / NEF 50.

[0103] <Effects of the fifth embodiment> In the fifth embodiment, by introducing SCP 90, even when read replicas are distributed, no changes are required on the UDM30 / PCF40 / NEF50 side, and UDM30 / PCF40 / NEF50 can use normal requests as they are when no read replicas are used.

[0104] (Effects of the First to Fifth Embodiments) The technologies according to the first to fifth embodiments can shorten the access time for retrieving data from a database, thereby reducing the impact on the response time of the entire 5G network. In addition, the access load to the subscriber DB for information reference for creating an AI model can be reduced.

[0105] (Device Configuration) Next, a description will be given of an example of the functional configuration of the network node 100 (subscriber DB 75, Coordinator NF 80, SCP 90, NWDAF 300, Consumer 400, etc.) and the terminal 20 that perform the processes and operations described above.

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

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

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

[0109] <Terminal 20> Fig. 21 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 20, 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. 20 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.

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

[0111] The setting unit 230 stores various setting information received from the network node by the receiving unit 220 in a storage device, and reads it out from the storage device as needed. The setting unit 230 also stores setting information that is set in advance.

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

[0113] (Hardware Configuration) The block diagrams (FIGS. 20 and 21) 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 be realized by combining software with the single device or the multiple devices.

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

[0115] 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. 22 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.

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

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

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

[0119] Furthermore, the processor 1001 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. 20 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 21 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.

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

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

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

[0123] 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).

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

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

[0126] Fig. 23 shows a configuration example of a vehicle 2001. As shown in Fig. 23, 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.

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

[0128] 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).

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

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

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

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

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

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

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

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

[0137] This specification discloses at least the configurations described in Supplementary Notes 1 to 5 below.

[0138] <Supplementary Note 1: Corresponding to the first embodiment> (Supplementary Item 1) A network node functioning as the first database, comprising: a control unit that creates a second database that stores data in a first database, and arranges the second database in an environment accessible to a specific network node; and a transmitter that transmits destination information of the second database toward the specific network node. (Supplementary Item 2) The network node according to Supplementary Item 1, wherein the destination information is transmitted to the specific network node via NRF. (Supplementary Item 3) The network node according to Supplementary Item 1, wherein the second database is created as a read-only database. (Supplementary Item 4) A communication method executed by the network node functioning as the first database, comprising: creating a second database that stores data in the first database, and arranging the second database in an environment accessible to a specific network node; and transmitting the destination information of the second database toward the specific network node.

[0139] Any of Supplementary Items 1 to 4 provides a technique for reducing the access load to a database used in a network. Supplementary Item 2 enables destination information to be reliably transmitted to a specific network node. Supplementary Item 3 enables the second database to be used as a read-only database for load balancing.

[0140] <Supplementary Note 2: Corresponding to Second Embodiment> (Supplementary Note 1) A network node functioning as the first database, comprising: a control unit that creates a second database that stores data in the first database, and places the second database in the same environment as a specific network node; and a transmitter that transmits destination information of the second database so that the specific network node can access the second database. (Supplementary Note 2) The network node according to Supplementary Note 1, wherein the destination information is transmitted to the specific network node via NRF. (Supplementary Note 3) The network node according to Supplementary Note 1, wherein the second database is created as a read-only database. (Supplementary Note 4) A communication method executed by the network node functioning as the first database, comprising: creating a second database that stores data in the first database, and placing the second database in the same environment as a specific network node; and transmitting the destination information of the second database so that the specific network node can access the second database.

[0141] Any of Supplementary Items 1 to 4 provides a technique for reducing the access load to a database used in a network. Supplementary Item 2 enables destination information to be reliably transmitted to a specific network node. Supplementary Item 3 enables the second database to be used as a read-only database for load balancing.

[0142] <Supplementary Note 3: Corresponding to the third embodiment> (Supplementary Note 1) A network node comprising: a receiving unit that collects load information of a first database; a control unit that decides, based on the load information, to allocate a second database that stores data of the first database; and a transmitting unit that transmits a message to the first database instructing the allocation of the second database. (Supplementary Note 2) The network node according to Supplementary Note 1, wherein the control unit decides to allocate the second database when detecting that the load indicated by the load information exceeds a threshold. (Supplementary Note 3) The network node according to Supplementary Note 1, wherein the message includes information indicating a distribution method of the second database, and the distribution method is a method of allocating the second database in the same environment as the first database, or a method of allocating the second database in the same environment as a specific network node that accesses the second database. (Supplementary Note 4) A communication method executed by a network node, comprising: collecting load information of a first database; deciding, based on the load information, to allocate a second database that stores data of the first database; and transmitting a message to the first database instructing the allocation of the second database.

[0143] Any of Supplementary Items 1 to 4 provides a technique for reducing the access load to a database used in a network. Furthermore, the second database can be dynamically allocated. Supplementary Item 2 clarifies the criteria for allocating the second database. Supplementary Item 3 allows the method for allocating the second database to be specified.

[0144] <Supplementary Note 4: Corresponding to the fourth embodiment> (Supplementary Note 1) A network node comprising: a receiving unit that receives update information from a first database when information is updated in the first database; and a transmitting unit that transmits a message requesting acquisition of the update information to a second database that stores data in the first database. (Supplementary Note 2) The network node according to Supplementary Note 1, wherein the second database is a database that receives read-only access from a specific network node that updates information in the first database. (Supplementary Note 3) The network node according to Supplementary Note 1, wherein the second database is a database that is located in the same environment as the first database, or a database that is located in the same environment as a specific network node that updates information in the first database. (Supplementary Note 4) A communication method executed by a network node, comprising: when information is updated in the first database, receiving update information from the first database; and transmitting a message requesting acquisition of the update information to a second database that stores data in the first database.

[0145] Any of Supplementary Items 1 to 4 provides a technique for reducing the access load to a database used in a network. Furthermore, the second database can be updated appropriately. According to Supplementary Item 2, updates to a read-only second database can be performed appropriately. According to Supplementary Item 3, updates to a second database that can be arranged in a variety of forms can be performed appropriately.

[0146] <Supplementary Note 5: Corresponding to Fifth Embodiment> (Supplementary Note 1) A network node comprising: a receiving unit that receives a message from a specific network node; a control unit that determines, based on the content of the message, a first database or a second database that stores data in the first database as a transfer destination of the message; and a transmitting unit that transfers the message to the transfer destination determined by the control unit. (Supplementary Note 2) The network node according to Supplementary Note 1, wherein the control unit determines the first database as the transfer destination when the message is a message instructing an information update, and determines the second database as the transfer destination when the message is a message instructing an information acquisition. (Supplementary Note 3) The network node according to Supplementary Note 1, wherein, after the second database has been allocated by the first database, the control unit performs settings for determining the transfer destination based on a change notification transmitted from the first database. (Supplementary clause 4) A communication method executed by a network node, comprising: a step of receiving a message from a specific network node; a step of determining, based on the content of the message, a first database or a second database that stores data in the first database as a forwarding destination of the message; and a step of forwarding the message to the determined forwarding destination.

[0147] Any of Supplementary Items 1 to 4 provides a technique for reducing the access load to a database used in a network. Also, a specific network node can access the second database without adding a destination to the specific network node. Supplementary Item 2 allows the forwarding destination of a message to be appropriately determined. Supplementary Item 3 allows the settings for determining the forwarding destination to be appropriately performed.

[0148] (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.

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

[0150] 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).

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

[0152] 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).

[0153] The information, signals, etc. 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.

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

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

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

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

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

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

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

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

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

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

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

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

[0166] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," and the like 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 some other suitable terminology.

[0168] 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, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that travels autonomously based on an operational command. Furthermore, the mobile object may be 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). Note that at least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

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

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

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

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

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

[0174] 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."

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

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

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

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

[0179] 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."

[0180] 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).

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

[0182] 10 Base Station 20 Terminal 30 UDM 40 PCF 50 NEF 60 NRF 70 UDR 75 Subscriber DB 76-78 Read Replica 80 Coordinator NF 90 SCP 100 Network Node 110 Transmitter 120 Receiver 130 Setting Unit 140 Controller 210 Transmitter 220 Receiver 230 Setting Unit 240 Controller 300 NWDAF 400 Consumer 1001 Processor 1002 Storage Device 1003 Auxiliary Storage Device 1004 Communication Device 1005 Input Device 1006 Output Device

Claims

1. A network node that functions as the first database, comprising: a control unit that creates a second database for storing data in the first database and arranges the second database in the same environment as a specific network node; and a transmission unit that transmits destination information of the second database so that the specific network node can access the second database.

2. The network node according to claim 1, wherein the destination information is transmitted to the specific network node via an NRF.

3. The network node according to claim 1, wherein the second database is created as a read-only database.

4. A communication method executed by a network node that functions as the first database, comprising: creating a second database for storing data in the first database and arranging the second database in the same environment as a specific network node; and transmitting destination information of the second database so that the specific network node can access the second database.

Images