Consumer, network node, and communication method

Abstract

This consumer uses a service of a network node and is provided with: a receiving unit for receiving a notification including information indicating a period in which subscriber data should be double-written onto a first network node and a second network node after migration of the subscriber data from the first network node to the second network node; and a control unit that, when the subscriber data is updated after receipt of the notification, performs a double write of the updated subscriber data onto the first network node and the second network node.

Description

Consumer, network node and communication method

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

[0002] In 5GC under 3GPP (registered trademark), procedures for transferring subscriber databases are specified (for example, Non-Patent Document 1).

[0003] Generally, in database transfer, a double write technique is known in which data is written simultaneously to both the old and new databases in order to maintain data consistency and improve reliability.

[0004] 3GPP TS 23.502 V18.6.0 (2024-06)

[0005] However, the 3GPP standard does not specify a procedure for double-writing when transferring a subscriber database, which may result in a risk that data consistency cannot be maintained or that double-writing procedures cannot be performed appropriately when transferring a subscriber database.

[0006] According to this embodiment, a consumer using the services of a network node comprises a receiving unit that receives a notification including information indicating that after subscriber data is transferred from a first network node to a second network node, it is time to dual-write the subscriber data to the first network node and the second network node, and a control unit that, after receiving the notification, dual-writes the updated subscriber data to the first network node and the second network node when the subscriber data is updated.

[0007] According to this embodiment, double writing can be appropriately performed in the transfer of the subscriber database.

[0008] 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 illustrating an example of a procedure for dual writing in transferring a subscriber database. FIG. 3 is a sequence diagram illustrating an example of a procedure for transferring a subscriber database to which the dual writing method according to Example 1 is applied. FIG. 4 is a sequence diagram illustrating an example of a procedure for transferring a subscriber database to which the dual writing method according to Example 2 is applied. FIG. 5 is a diagram illustrating an example of an operation of NF profile partial update according to this embodiment. FIG. 6 is a diagram illustrating an example of a table illustrating a definition of NFProfile according to this embodiment. FIG. 7 is a diagram illustrating an example of a table illustrating a definition of type UdrInfo included in this embodiment. FIG. 8 is a diagram illustrating an example of an operation related to Notification from an NRF according to this embodiment. FIG. 9 is a diagram illustrating an example of newly defined information included in Notification according to this embodiment. FIG. 10 is a diagram illustrating an example of the functional configuration of a base station and a network node according to this embodiment. FIG. 11 is a diagram illustrating an example of the functional configuration of a terminal according to this embodiment. FIG. 12 is a diagram illustrating an example of the hardware configuration of a base station, a network node, and a terminal according to this embodiment. FIG. 13 is a diagram illustrating an example of the configuration of a vehicle according to this embodiment.

[0009] The present embodiment will be described below 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.

[0010] Existing technologies are used as appropriate in the operation of the wireless communication system of this embodiment. The existing technologies are, for example, communication methods based on the 3GPP standard, such as the existing NR (New Radio) (5G) / 5GC (5G Core network). However, the existing technologies are not limited to NR / 5GC, but also include LTE, LTE-Advanced, and NR (5G) and later systems, or wireless LANs (Local Area Networks).

[0011] In this embodiment, "configuring" radio parameters etc. may mean that predetermined values ​​are pre-configured, or that radio parameters notified from a network node or a terminal are set.

[0012] Fig. 1 is a diagram illustrating an example of a communication system. As shown in Fig. 1, the 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.

[0013] 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. In the wireless communication network of this embodiment, multiple network slices may be constructed.

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

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

[0016] Fig. 2 is a diagram for explaining an example of a communication system in a roaming environment. As shown in Fig. 2, the network is composed of a UE, which is a 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.

[0017] The RAN is a network node having a radio access function and is connected to the UE, the AMF, and the UPF. The AMF is a network node having functions such as RAN interface termination, NAS termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node having functions such as a PDU session point to the outside that interconnects with the DN, packet routing and forwarding, and user plane QoS handling. The UPF and the DN constitute a network slice. In the wireless communication network of this embodiment, multiple network slices are constructed.

[0018] The AMF is connected to the UE, RAN, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, AF, and SEPP (Security Edge Protection Proxy). The AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes interconnected via respective service-based interfaces, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0019] The SMF is a network node having functions such as session management, UE IP address allocation and management, DHCP function, ARP proxy, and roaming function. The NEF is a network node having a function of notifying other NFs of capabilities and events. The NSSF is a network node having functions such as selecting a network slice to which a UE connects, determining allowed NSSAIs, determining a configured NSSAI, and determining an AMF set to which a UE connects. The PCF 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 is a network node having a function of discovering NF instances that provide services. The SEPP is a non-transparent proxy that filters control plane messages between PLMNs (Public Land Mobile Networks). The vSEPP shown in FIG. 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] While the conventional 3GPP standard specifies procedures for transferring subscriber databases (subscriber data), it does not support a double-write procedure for maintaining data consistency during the transfer of the subscriber database. As a result, there is a risk that data consistency cannot be maintained or downtime cannot be minimized during the transfer of the subscriber database.

[0022] 3 is a diagram showing an example of a procedure for double-writing in the transfer of a subscriber database. In the example of FIG. 3, subscriber data is transferred from an old database contained in UDR1 to a new database contained in UDR2.

[0023] The left diagram of Figure 3 shows an example of a dual-write operation during or after subscriber data transfer and before checking the normality of the new database. In the left diagram of Figure 3, the AMF sends a subscriber data transfer request to a UDM selected by round robin. This request includes identification information (e.g., SUPI (Subscription Permanent Identifier)) of the UE to be transferred. Because the UDM is during or after the subscriber data transfer and before checking the normality of the new database, it performs dual-write of the subscriber data to both the old database (UDR1) and the new database (UDR2) where the subscriber data of the UE corresponding to the SUPI is stored.

[0024] The right diagram of Fig. 3 shows an example of the operation of dual writing after the transfer of subscriber data and after the normality of the new database is confirmed. In the right diagram of Fig. 3, after the normality of the new database is confirmed, dual writing is stopped and the UDM accesses and writes only to the new database (UDR2).

[0025] Conventionally, a UDR consumer (UDM, PCF, NEF) discovers the UDR in which the UE is stored and accesses the discovered UDR, but no method is specified for applying the dual-write method.

[0026] For example, the conventional 3GPP standard does not have a mechanism for determining whether a UDR consumer is in a period (normality confirmation period) during which the normality of a new database (new UDR) after transfer is confirmed, and therefore the UDR consumer cannot determine when dual writing should be performed.

[0027] Next, the conventional 3GPP standard does not provide a mechanism for a UDR consumer to identify which subscriber is the target of dual writing.

[0028] Furthermore, the existing 3GPP standard does not provide a mechanism for a UDR consumer to determine when to stop double-writing.

[0029] According to this embodiment, the procedure for double writing in the transfer of the subscriber database is clarified, the consistency of data in the transfer of the subscriber database is guaranteed, and reliability can be improved.

[0030] The procedure for transferring a subscriber database to which the dual-write method is applied in this embodiment will be described below as examples 1 and 2.

[0031] First Embodiment FIG. 4 is a sequence diagram showing an example of a procedure for transferring a subscriber database to which the dual writing method according to the first embodiment is applied.

[0032] 4 is a consumer (UDM, PCF, NEF) that uses the UDR service for the UDR. The Consumer 60 is an NF (Network Function) Consumer, and may be referred to as a UDR / UDM / NRF Consumer.

[0033] The old UDR 40 may be referred to as a source UDR. The new UDR 50 may be referred to as a target UDR. The UDR in this embodiment is a database that manages at least subscriber data, and may also be a database that manages session information and / or authentication information.

[0034] In step S101, the Consumer 60 transmits a Subscribe to the NRF 30. Subscribe is a message in which the Consumer 60 requests the NRF 30 to notify the NRF 30 of a specific NF type or service.

[0035] Subscribe includes NF Type, NF Service, NF Instance Filter, Notification Uri, and Subscription Duration. NF Type specifies the type of NF to receive notifications for. NF Service specifies the service when receiving notifications for a service provided by a specific NF. NF Instance Filter specifies the conditions for identifying a specific NF instance when receiving only notifications for that instance. Notification Uri specifies the URI to which the NRF sends notifications. Subscription Duration specifies the validity period of the subscription.

[0036] In the Subscribe in step S101, in order to receive an NFM_update notification from the NRF 30, for example, "NRF" may be set in the NF Type and "NFDiscovery service" may be set in the NF Service.

[0037] In step S102, the subscriber data (database) is transferred from the old UDR 40 to the new UDR 50.

[0038] In step S103a, the old UDR 40 transmits a notification (NFM_Update) indicating an update of the UDR 40 storing the subscriber data of the UE (terminal 20) after the subscriber data transfer to the NRF 30. The NFM_Update includes the duplicate writing target subscriber ID as a new attribute. The attribute may also be referred to as information or an information element.

[0039] The dual-write target subscriber ID may be at least one of, for example, a SUPI, a GPSI (Generic Public Subscription Identifier), a range including multiple SUPIs, a range including multiple GPSIs, a group ID identifying a group including one or multiple UEs / subscribers, and any other information identifying a UE / subscriber. The new attribute included in the NFM_Update is, for example, the attribute name "MigrationInfo" and the data type "UdrInfo" shown in FIG. 7, which will be described later. Based on the new attribute including the dual-write target subscriber ID, it is possible to indicate to the consumer 60 which subscriber is the dual-write target.

[0040] In step S103b, the new UDR 50 transmits a notification (NFM_Update) indicating an update of the UDR 50 storing the subscriber data of the UE (terminal 20) after the subscriber data transfer to the NRF 30. The new attribute of the NFM_Update is the same as that in step S103a.

[0041] Although FIG. 4 shows an example in which step S103b is executed after step S103a, step S103a may be executed after step S103b.

[0042] In step S104a, the NRF 30 transmits to the Consumer 60, in response to the NFM_Update received in step S103a, a notification (NFM_Notify) indicating an update of the UDR 40 in which the subscriber data of the UE (terminal 20) after the subscriber data transfer is stored. The NFM_Notify includes the duplicate writing target subscriber ID as a new attribute. The new attribute is, for example, the attribute name "MigrationInfo" and the data type "UdrInfo" shown in FIG. 10 (described later).

[0043] In step S104b, the NRF 30 transmits to the Consumer 60, in response to the NFM_Update received in step S103b, a notification (NFM_Notify) indicating an update of the UDR 50 in which the subscriber data of the UE (terminal 20) after the subscriber data transfer is stored. The NFM_Notify includes the duplicate writing target subscriber ID as a new attribute. While FIG. 4 shows an example in which step S104b is executed after step S104a, step S104a may also be executed after step S104b.

[0044] When the notification from the NRF 30 includes a new attribute (for example, a subscriber ID to be duplicated), the Consumer 60 may determine that it is the period for duplicate writing after the subscriber data transfer.

[0045] In step S105, the Consumer 60 determines that the need to access the UDR has arisen. For example, the need to access the UDR has arisen when an update to subscriber data corresponding to a specific subscriber has occurred.

[0046] In step S106, the Consumer 60 determines whether or not dual writing of the relevant subscriber is necessary. For example, if the subscriber ID corresponding to the subscriber data to be updated (the subscriber ID to be updated) is included in the received dual writing target subscriber IDs, the Consumer 60 may determine that dual writing of the subscriber data of the subscriber ID to be updated is necessary. On the other hand, if the subscriber ID corresponding to the subscriber data to be updated (the subscriber ID to be updated) is not included in the received dual writing target subscriber IDs, the Consumer 60 may determine that dual writing of the subscriber data of the new target subscriber ID is not necessary.

[0047] In step S106, if it is determined that dual writing for the subscriber is necessary (Yes in step S106), dual writing is performed in steps S107a and S107b. In step S107a, the Consumer 60 requests the old UDR 40 to write update data, and in step S107b, the Consumer 60 requests the new UDR 50 to write the same update data.

[0048] In step S108, the O&M 70 determines whether the transfer of subscriber data to the new UDR 50 is normal.

[0049] In this embodiment, the normality of the subscriber data transfer may be referred to as the normality or stability of the UDR (database). The normality of the subscriber data transfer may be determined based on, for example, at least one of a consistency check of the transferred data, a system performance verification, or a system operation check. The consistency check of the transferred data verifies whether the transferred data matches the data before the transfer. The performance verification verifies whether the transferred system is performing as expected. For example, the performance verification verifies whether one or more of resource (CPU, memory) usage, response time (the system's response speed to specific operations or requests), throughput (the number of transactions or amount of data the system can process per unit time), or stability / reliability (the system's stability during operation or under high load over a specified period, and the error rate) meet the required conditions. The system operation check verifies, for example, whether the application functions (data registration, update, deletion, search, etc.) operate without problems or whether there are no problems with specified test items.

[0050] The determination of the normality of the subscriber data transfer may be performed by a user (administrator) of the O&M 70, or may be performed automatically by an NF within the 5GC or an external system / device.

[0051] If the normality of the subscriber data transfer is confirmed, in step S109, the O&M 70 issues a command to stop double writing.

[0052] In step S110, the old UDR 40 sends a notification of subscriber data transfer (NFM_Update) to the NRF 30. The NFM_Update includes the ID of the duplicated-write target subscriber to be deleted as a new attribute. The new attribute is an attribute (e.g., "MigrationInfo") included in the NFProfile that indicates transfer information. The data type corresponding to "MigrationInfo" is UDR information (e.g., "UdrInfo"). The fact that "MigrationInfo" is not set in the NFProfile indicates that the duplicated-write period has ended.

[0053] In step S111, the new UDR 50 sends a write request response to the NFR 30.

[0054] In step S112, the NFR 30 sends a subscriber data transfer notification (NFM_Update) to the Consumer 60. The NFM_Update includes the ID of the subscriber to be deleted as a new attribute. The subscriber data transfer notification in step S112 includes the information indicated in the subscriber data transfer notification in step S110.

[0055] In this way, if the notification from the NFR 30 to the Consumer 60 does not include the predetermined information ("MigrationInfo"), the Consumer 60 can determine that the dual-write period has ended based on the notification.

[0056] Second Embodiment FIG. 5 is a sequence diagram showing an example of a procedure for transferring a subscriber database to which the dual writing method according to a second embodiment is applied.

[0057] Steps S201-203b and S205-212 in Fig. 5 correspond to steps S101-103b and S105-112 in Fig. 4, respectively, and therefore a description of the operations of these steps will be omitted.

[0058] According to the second embodiment, after step S203b, in step S213, the NRF 30 aggregates information included in the NFM_Update from the old UDR 40 and the NFM_Update from the new UDR 50. In step S204, the NRF 30 transmits to the Consumer 60, based on the information aggregated in step S213, a notification (NFM_Notify) indicating the update of the old UDR 40 and the new UDR 50 in which the subscriber data of the UE (terminal 20) after the subscriber data transfer is stored. The NFM_Notify includes the duplicate writing target subscriber ID as a new attribute. The operations from step S205 onwards are executed.

[0059] Inter-NF messages and new parameters applied in this embodiment including Examples 1 and 2 will be described below.

[0060] FIG. 6 is a diagram showing an example of the operation of the NF profile partial update in this embodiment. The NF profile partial update is an operation for updating only a part of the NF profile in 5GC. The procedure of the NF profile partial update is specified, for example, in 3GPP TS 29.510 Section 5.2.2.3.1B. According to this embodiment, as shown in FIG. 6, a new attribute is added to the NFProfile of the Nnrf_NFManagement NFProfile Partial Update transmitted from the NRF to the NF Service Consumer. The NRF in FIG. 6 may be replaced with the UDR 40 / UDR 50, and the NF Service Consumer may be replaced with the NRF 30. The Nnrf_NFManagement NFProfile Partial Update is, for example, "NFM_Update" in steps S103a and S103b in FIG. 4 (steps S203a and S203b in FIG. 5).

[0061] As shown in Fig. 7, NFProfile includes new attributes with an attribute name of "MigrationInfo" and a data type of "UdrInfo." "UdrInfo" indicates the range of the added or removed SUPI (specific data for the UDR (ranges of added or removed SUPI, group ID, ...)). If "UdrInfo" is not set, it indicates that the dual-write period has ended. The table shown in Fig. 7 is, for example, a table in which the new attribute has been added to Table 6.1.6.2.2-1: Definition of type NFProfile shown in 3GPP TS 29.510, Section 6.1.6.2.2 "Type: NFProfile."

[0062] FIG. 8 shows attributes included in "UdrInfo." In this embodiment, new attributes included in "UdrInfo" include, for example, "addedSupiRanges" (SUPI ranges added due to subscriber data transfer), "addedGpsiRanged" (GPSI ranges added due to subscriber data transfer), "addedExternalGroupIdentifiersRanges" (Group ID ranges added due to subscriber data transfer), "removedSupiRanges" (SUPI ranges moved due to subscriber data transfer), "removedGpsiRanged" (GPSI ranges moved due to subscriber data transfer), and "removedExternalGroupIdentifiersRanges" (Group ID ranges moved due to subscriber data transfer). The table shown in FIG. 8 is, for example, a table in which new attributes are added to 3GPP TS 29.510 Section 6.1.6.2.6 "Type: UdrInfo Table 6.1.6.2.6-1: Definition of type UdrInfo."

[0063] Fig. 9 is a diagram showing an example of an operation related to a notification from the NRF in this embodiment. The NRF in Fig. 9 may be replaced with the NRF 30, and the NF Service Consumer may be replaced with the Consumer 60. The notification is, for example, "NFM_Notify" in steps S104a and S104b in Fig. 4 (step S204 in Fig. 5). The operation related to a notification from the NRF shown in Fig. 9 is specified, for example, in 3GPP TS 29.510 section 5.2.2.6.2 "Notification from NRF in the same PLMN".

[0064] The notification includes an NFProfile that includes a new attribute, as shown in Fig. 10. The NFProfile includes the newly added attribute name "MigrationInfo" and data type "UdrInfo". Furthermore, "UdrInfo" includes the new attribute shown in Fig. 8.

[0065] The names of messages and attributes (information elements) between NFs shown in Figures 4-10 above are examples, and other names may be used.

[0066] According to the embodiments including the above-described Example 1 and Example 2, it is possible to indicate to the consumer 60 when to perform dual writing after the transfer of subscriber data, which subscribers are subject to dual writing, and when to stop dual writing. This allows the consumer 60 to appropriately control whether to perform or stop dual writing for each subscriber after the transfer of subscriber data.

[0067] (Device Configuration) Next, a description will be given of an example of the functional configuration of the base station 10, network node, and terminal 20 that perform the processes and operations described above. The network nodes are the NRF 30, the UDR 40, the UDR 50, and the Consumer 60. The base station 10, the network node, and the terminal 20 include functions for performing the above-described embodiments. However, the base station 10, the network node, and the terminal 20 may each include only a part of the functions of the embodiments.

[0068] <Base Station and Network Node> Fig. 11 is a diagram showing an example of the functional configuration of a base station 10 and a network node. As shown in Fig. 11, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 11 is merely an example. As long as the operation according to this embodiment can be performed, the names of the functional divisions and functional units may be any. Note that the network node may have the same functional configuration as the base station 10. Furthermore, a network node having multiple different functions in the system architecture may be composed of multiple network nodes separated by function.

[0069] The transmitter 110 has a function of generating a signal to be transmitted to the terminal 20 or another 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 another 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.

[0070] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20 in a storage device, and reads out the information from the storage device as needed.

[0071] The control unit 140 performs the processes described in the embodiments. 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.

[0072] <Terminal> Fig. 12 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 12, 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. 12 is merely an example. As long as the operation according to this embodiment can be performed, the names of the functional divisions and functional units may be any. In addition, the communication device that becomes the resource holder may have the same functional configuration as the terminal 20.

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

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

[0075] The control unit 240 performs the processes described in the embodiments. The function unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the function unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

[0076] (Hardware Configuration) The block diagrams (FIGS. 11 and 12) 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.

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

[0078] For example, the network node, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 13 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The network node may have the same hardware configuration as the base station 10. The above-described base station 10 and the terminal 20 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.

[0079] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0080] Each function in the base station 10 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 by 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.

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

[0082] 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 base station 10 shown in FIG. 11 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. 12 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.

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

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

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

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

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

[0088] Furthermore, the base station 10 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.

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

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

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

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

[0093] 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 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 provides various types of multimedia information and multimedia services to the occupants of the vehicle 2001 by using information acquired from external devices via the communication module 2013, etc.

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

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

[0096] 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 mobile station, or the like.

[0097] The communication module 2013 transmits, via wireless communication to an external device, a current signal from the current sensor that is input to the electronic control unit 2010. The communication module 2013 also transmits, via wireless communication to an external device, the rotation speed signals of the front and rear wheels acquired by a rotation speed sensor 2022, the air pressure signals of the front and rear wheels acquired by an air pressure sensor 2023, the vehicle speed signal acquired by a vehicle speed sensor 2024, the acceleration signal acquired by an acceleration sensor 2025, the accelerator pedal depression amount signal acquired by an accelerator pedal sensor 2029, the brake pedal depression amount signal acquired by a brake pedal sensor 2026, the shift lever operation signal acquired by a shift lever sensor 2027, and detection signals for detecting obstacles, vehicles, pedestrians, etc. acquired by an object detection sensor 2028, all of which are input to the electronic control unit 2010.

[0098] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on the information service unit 2012 provided in the vehicle 2001. The communication module 2013 also stores the various information received from the 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.

[0099] <Additional Notes> (Additional Note 1) A consumer (e.g., consumer 60) that uses the services of a network node, comprising: a receiving unit that receives a notification including information indicating that after subscriber data is transferred from a first network node (e.g., old UDR 40) to a second network node (e.g., new UDR 50), it is a period in which the subscriber data should be dual-written to the first network node and the second network node; and a control unit that, after receiving the notification, when the subscriber data is updated, dual-writes the updated subscriber data to the first network node and the second network node.

[0100] (Supplementary Item 2) The consumer according to Supplementary Item 1, wherein the notification includes identification information of the subscriber who is the subject of the double writing.

[0101] (Supplementary Item 3) A consumer as described in Supplementary Item 2, wherein the control unit dual-writes the updated subscriber data to the first network node and the second network node when the subscriber corresponding to the updated subscriber data is the subscriber to be dual-written.

[0102] (Supplementary Item 4) The consumer according to Supplementary Item 1, wherein the receiving unit receives a notification that does not include the information, and the control unit stops the dual writing based on the notification that does not include the information.

[0103] (Supplementary clause 5) A third network node (e.g., NRF 30) comprising: a transmitter that transmits a notification to a consumer including information indicating that it is a period during which subscriber data should be dual-written to the first network node and the second network node after subscriber data has been transferred from a first network node to a second network node; a receiver that receives a request from the consumer to dual-write the updated subscriber data when the subscriber data is updated after the notification has been sent; and a controller that dual-writes the updated subscriber data to the first network node and the second network node based on the request.

[0104] (Supplementary clause 6) A communication method executed by a consumer using a service of a network node, comprising: a step of receiving a notification including information indicating that after subscriber data is transferred from a first network node to a second network node, it is a period in which the subscriber data should be dual-written to the first network node and the second network node; and a step of dual-writing the updated subscriber data to the first network node and the second network node when the subscriber data is updated after receiving the notification.

[0105] According to Supplementary Items 1-6, it is possible to properly perform double writing during the transfer of subscriber data. According to Supplementary Items 1, 5, and 6, it is possible to indicate to the consumer when double writing should be performed after the transfer of subscriber data. According to Supplementary Items 2 and 3, it is possible to indicate to the consumer which subscribers are subject to double writing after the transfer of subscriber data. According to Supplementary Item 4, it is possible to indicate to the consumer when double writing should be performed.

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

[0107] Each aspect / embodiment described in the present disclosure may be applied to at least one of systems using LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (New Radio), 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.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems enhanced based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.) may also be applied.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0122] 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 remote radio head (RRH)). The terms "cell" or "sector" refer to part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

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

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

[0125] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may 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.

[0126] 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 above-mentioned network node. 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.

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

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

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

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

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

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

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

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

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

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

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

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

[0139] 10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 230 Setting unit 240 Control unit 30 NRF 40 UDR 50 UDR 60 Consumer 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheels 2008 Rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 RPM sensor 2023 Air pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. A consumer that uses the services of a network node, comprising: a receiving unit that receives a notification including information indicating that after subscriber data is transferred from a first network node to a second network node, it is time to dual-write the subscriber data to the first network node and the second network node; and a control unit that, when the subscriber data is updated after receiving the notification, dual-writes the updated subscriber data to the first network node and the second network node.

2. The consumer of claim 1, wherein the notification includes identification information of the subscriber to whom the dual write is to be performed.

3. A consumer as described in claim 2, wherein the control unit dual-writes the updated subscriber data to the first network node and the second network node when the subscriber corresponding to the updated subscriber data is the subscriber to be dual-written.

4. The consumer according to claim 1, wherein the receiving unit receives a notification that does not include the information, and the control unit stops the dual writing based on the notification that does not include the information.

5. A third network node comprising: a transmitter that transmits a notification to a consumer including information indicating that, after subscriber data is transferred from a first network node to a second network node, it is time to duplicate the subscriber data in the first network node and the second network node; a receiver that receives a request from the consumer to duplicate the updated subscriber data when the subscriber data is updated after the notification is sent; and a control unit that duplicates the updated subscriber data in the first network node and the second network node based on the request.

6. A communication method executed by a consumer using a service of a network node, comprising: a step of receiving a notification including information indicating that, after transfer of subscriber data from a first network node to a second network node, it is a period in which the subscriber data should be duplicated to the first network node and the second network node; and a step of, after receiving the notification, when the subscriber data is updated, duplicate-writing the updated subscriber data to the first network node and the second network node.

Images