Network node and communication method

Abstract

This network node has: a transmission unit that registers a terminal to a user data repository (UDR); a reception unit that receives information from the UDR as a response to the registration of the terminal, said information identifying the UDR; and a control unit that associates and stores the terminal and the information identifying the UDR, wherein if the reception unit receives a fault notification regarding the UDR, the control unit causes the terminal which is stored in association with the UDR to perform a re-registration action.

Description

[Technical field]

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

[0002] 3GPP (3rd Generation Partnership Project) is currently studying a wireless communication system called 5G or NR (New Radio) (hereinafter, the wireless communication system is referred to as "5G" or "NR") in order to realize a larger system capacity, a higher data transmission speed, and a lower latency in wireless sections. In 5G, various wireless technologies are being studied to meet the requirements of achieving a throughput of 10 Gbps or more while keeping the latency in wireless sections to 1 ms or less.

[0003] In NR, a network architecture is being considered that includes 5GC (5G Core Network), which corresponds to EPC (Evolved Packet Core), which is a core network in the network architecture of LTE (Long Term Evolution), and NG-RAN (Next Generation - Radio Access Network), which corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network), which is a RAN (Radio Access Network) in the network architecture of LTE (for example, Non-Patent Document 1). [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 23.501 V15.9.0(2020-03) Summary of the Invention [Problem to be solved by the invention]

[0005] In the 5G core network, when a subscriber's profile information becomes inconsistent, the function for correcting the inconsistent profile information has not been standardized. As a result, when a subscriber's profile information does not match, services based on the latest contract information or location information may not be provided.

[0006] The present invention has been made in view of the above-mentioned points, and has an object to match profile information of subscribers in a network. [Means for solving the problem]

[0007] According to the disclosed technology, a network node is provided which has a transmitting unit which registers a terminal in a UDR (User Data Repository), a receiving unit which receives information identifying the UDR from the UDR in response to the registration of the terminal, and a control unit which associates and retains the terminal and the information identifying the UDR, and when the receiving unit receives a fault notification of the UDR, the control unit causes the terminal which is associated with the UDR and retained to perform a registration operation again. Effect of the Invention

[0008] The disclosed technique allows for matching of subscriber profile information in a network. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating an example of a communication system. [Diagram 2] FIG. 1 is a diagram illustrating an example of a communication system in a roaming environment. [Diagram 3] FIG. 11 is a diagram for explaining an example (1) of a mismatch in profile information. [Figure 4] FIG. 13 is a diagram for explaining an example (2) of a mismatch in profile information. [Diagram 5]FIG. 11 is a diagram for explaining an example (3) of a mismatch in profile information. [Figure 6] FIG. 1 is a diagram for explaining an example (1) of a communication system according to an embodiment of the present invention. [Figure 7] FIG. 2 is a diagram for explaining an example (2) of a communication system according to an embodiment of the present invention. [Figure 8] FIG. 11 is a sequence diagram illustrating an example of updating profile information according to an embodiment of the present invention. [Figure 9] 2 is a diagram illustrating an example of a functional configuration of a base station 10 according to an embodiment of the present invention. [Figure 10] 2 is a diagram illustrating an example of a functional configuration of a terminal 20 according to an embodiment of the present invention. [Figure 11] 2 is a diagram illustrating an example of a hardware configuration of a base station 10 and a terminal 20 according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0011] 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 are, for example, existing LTE, but are not limited to existing LTE. In addition, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and systems after LTE-Advanced (e.g., NR), or wireless LAN (Local Area Network), unless otherwise specified.

[0012] Furthermore, in an embodiment of the present invention, when radio parameters, etc. are "configured," this may mean that predetermined values ​​are pre-configured, or that radio parameters notified from the network node 30 or the terminal 20 are configured.

[0013] Fig. 1 is a diagram for explaining an example of a communication system. As shown in Fig. 1, the communication system is composed of a UE, which is a terminal 20, and a plurality of network nodes 30. In the following, it is assumed that one network node 30 corresponds to each function, but a single network node 30 may realize a plurality of functions, or a single function may be realized by a plurality of network nodes 30. In addition, the "connection" described below may be a logical connection or a physical connection.

[0014] The RAN (Radio Access Network) is a network node 30 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 30 having functions such as a RAN interface termination, a NAS (Non-Access Stratum) termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 having functions such as a PDU (Protocol Data Unit) session point to the outside that interconnects with a 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 according to the embodiment of the present invention, a plurality of network slices are constructed.

[0015] 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 30 that are mutually connected via interfaces, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf, based on their respective services.

[0016] The SMF is a network node 30 having functions such as session management, IP (Internet Protocol) address allocation and management of UE, DHCP (Dynamic Host Configuration Protocol) function, ARP (Address Resolution Protocol) proxy, and roaming function. The NEF is a network node 30 having a function of notifying other NFs (Network Functions) of capabilities and events. The NSSF is a network node 30 having functions such as selecting a network slice to which the UE connects, determining permitted NSSAI (Network Slice Selection Assistance Information), determining an NSSAI to be set, and determining an AMF set to which the UE connects. The PCF is a network node 30 having a function of performing network policy control. The AF is a network node 30 having a function of controlling an application server. The NRF is a network node 30 having a function of discovering an NF instance that provides a service. The UDM is a network node 30 that manages subscriber data and authentication data. The UDM is connected to a UDR (User Data Repository) that holds the data.

[0017] 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 a plurality of network nodes 30. In the following, it is assumed that one network node 30 corresponds to each function, but a single network node 30 may realize a plurality of functions, or a plurality of network nodes 30 may realize a single function. In addition, the "connection" described below may be a logical connection or a physical connection.

[0018] The RAN is a network node 30 having a radio access function, and is connected to the UE, the AMF, and the UPF. The AMF is a network node 30 having functions such as RAN interface termination, NAS termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 having functions such as a PDU session point for 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 according to the embodiment of the present invention, a plurality of network slices are constructed.

[0019] 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 30 that are mutually connected via interfaces, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf, based on their respective services.

[0020] The SMF is a network node 30 having functions such as session management, IP address allocation and management for UE, DHCP function, ARP proxy, and roaming function. The NEF is a network node 30 having a function of notifying other NFs of capabilities and events. The NSSF is a network node 30 having functions such as selecting a network slice to which the UE connects, determining an allowed NSSAI, determining an NSSAI to be configured, and determining an AMF set to which the UE connects. The PCF is a network node 30 having a function of performing network policy control. The AF is a network node 30 having a function of controlling an application server. The NRF is a network node 30 having a function of discovering an NF instance that provides a service. 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.

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

[0022] In the case of a mismatch in subscriber profile information, the 5G core network does not have a standardized function for correcting the mismatched information, whereas the 4G core network had a standardized reset function.

[0023] On the other hand, the UDR (User Data Repository) in the 5G core network is designed to prevent stateful data from being lost due to its DLA (Data Layered Architecture) configuration, so a network design that guarantees data related to subscriber profile information in the UDR is being considered. However, it cannot be said that there is absolutely no possibility of mismatches in subscriber profile information.

[0024] If the subscriber's profile information does not match, it may be impossible to provide services based on the latest contract information or location information, which is a problem. In order to solve this problem, if the subscriber's profile information does not match between the UDR and the AMF, SMF, and SMSF (Short Message Service Function), a process to make them match is required.

[0025] FIG. 3 is a diagram for explaining an example (1) of mismatch of profile information. As shown in FIG. 3, when UDM receives SO (Service order), it transmits information related to SO to AMF. Here, since the profile held by UDR is in the area #A whose area information is old due to a failure or the like, UDM notifies AMF#A of information related to SO. Since the actual terminal has moved from 5G_Pool#A managed by AMF#A to 5GPool#B managed by AMF#B, and the information of the corresponding subscriber does not exist in AMF#A, an error response is made. UDM should originally notify AMF#B of information related to SO. As a result, the SO is not reflected immediately, and the terminal cannot receive the service based on the latest contract. Note that information related to SO is also transmitted to SMF in the same way. If the registration information of SMF held by UDR is incorrect, the SO is not reflected immediately in SMF either.

[0026] FIG. 4 is a diagram for explaining an example (2) of a mismatch in profile information. As shown in FIG. 4, when an SMS (Short message service) is received, an SMS-GMSC (SMS Gateway Mobile Switching Center) inquires of the UDM about the location of the receiving subscriber. Here, since the profile held by the UDR is in the old location #A due to a failure or the like, the UDM responds with an incorrect SMSF address, and the SMS-GMSC notifies SMSF#A. Since the actual terminal has moved from 5G_Pool#A corresponding to SMSF#A to 5GPool#B corresponding to SMSF#B, and SMSF#A does not have information on the relevant subscriber, an error response is returned. The UDM should have notified SMSF#B of information related to the SMS reception. This results in an error in the SMS reception.

[0027] Fig. 5 is a diagram for explaining an example (3) of a mismatch in profile information. When a call is received, a terminating access domain selection (T-ADS) is performed to identify the RAT in which the receiving terminal is located. As shown in Fig. 5, if the location information held in the UDR is old, an inquiry is made to an SGSN (Serving General packet radio service Support Node), MME (Mobility Management Entity), or AMF that is not located in the area, resulting in an error.

[0028] Therefore, the inconsistency in the subscriber's profile information is resolved by the operation described below. Fig. 6 is a diagram for explaining an example (1) of a communication system in an embodiment of the present invention. As shown in Fig. 6, in step 1, the UDR#R registers its own NF profile including the setting value of the UDR#R in the NRF. Next, when the user is registered, the UDR#R notifies the AMF#A of the UDR number (UDR#R), and the AMF#A associates the user with the UDR number and holds it (step 2). For example, the user may be identified and held by an International Mobile Subscriber Identity (IMSI), which is one form of a Subscription Permanent Identifier (SUPI).

[0029] 6, user B and UDR#R, user D and UDR#R, user Z and another UDR#Y are associated and stored in AMF#A. In addition, the user presence information in UDR#R indicates that user B is present in AMF#A, user D is present in AMF#A, and user E is present in AMF#B.

[0030] Fig. 7 is a diagram for explaining an example (2) of a communication system in an embodiment of the present invention. Here, as shown in Fig. 7, it is assumed that a failure occurs in UDR#R. Since UDR#R has broken down, it is switched to UDR#r. In step 3, UDR#r registers with the NRF that a failure has occurred in UDR#R, the pre-switching master. Next, the NRF notifies AMF#A that a failure has occurred in UDR#R (step 4).

[0031] In the following step 5, AMF#A executes an operation equivalent to LICH (Location information confirmed in HSS) = NC (Not Confirmed) for the user (terminal) associated with UDR#R, and quickly restores the location registration information stored in the UDR. The operation equivalent to LICH = NC may be an operation of performing location registration in the UDM when a location registration is triggered from the user side, and an operation of prompting re-location registration when making or receiving a call. For example, in the example shown in FIG. 7, since user B and user D are stored in association with UDR#R, AMF#A may prompt user B and user D to re-register their locations in the UDM.

[0032] For example, instead of step 1 shown in FIG. 6, UDR#R may notify the NRF of its own NF profile including the UDR number and the setting value of the SUPI range. Next, AMF#A may obtain the NF profile of the UDR from the NRF. As a result, AMF#A can grasp the user held in UDR#R, so that UDR#R does not need to notify AMF#A of the UDR number (UDR#R) in step 2 shown in FIG. 6. Note that SUPI is an identifier that identifies a subscriber in a 5G system, and IMSI is one form of it, and may be held in the UDR. For example, instead of steps 3 and 4 in FIG. 7, AMF may request an update notification of the NF profile of the UDR to the NRF in advance, and the completion of the failure occurrence resumption may be conveyed from the UDR to the AMF via the NRF as an update notification of the NF profile of the UDR.

[0033] Also, for example, as a method of eliminating the delay in SO reflection in the SMF or the error operation when an SMS is received as shown in Figure 4, following step 5 shown in Figure 7, AMF#A may notify the SMF and SMSF of a request to re-register the terminal in the UDR.

[0034] FIG. 8 is a sequence diagram for explaining an example of profile information update in an embodiment of the present invention. In FIG. 8, transmission or reception to a UDR may be via a UDM. In step S11, UDR#R (30C) registers the UDR in NRF (30B). In the following step S12, AMF (30A) transmits a user registration to UDR#R (30C). In the following step S13, UDR#R notifies the AMF of the UDR number (UDR#R). In step S14, the AMF retains the correspondence between the IMSI and the UDR number (UDR#R). Step S14 allows the AMF to know the UDR in which the user is registered.

[0035] In step S21, a failure occurs in the UDR#R. In the following step S22, switching is performed from the UDR#R to the UDR#r (30D). In the following step S23, the UDR#r registers a failure of the UDR#R with the NRF. In the following step S24, the NRF transmits a failure notification of the UDR#R to the AMF. In the following step S25, the AMF performs an operation equivalent to the above-mentioned LICH=NC for the terminal that is the UDR#R.

[0036] According to the above-described embodiment, even if a failure occurs in the UDR, the AMF can perform location registration operation again to update the subscriber's profile information.

[0037] That is, subscriber profile information can be matched across the network.

[0038] (Device configuration) Next, examples of functional configurations of the base station 10, the network node 30, and the terminal 20 that perform the processes and operations described above will be described. The base station 10, the network node 30, and the terminal 20 each include functions for performing the above-mentioned embodiments. However, the base station 10, the network node 30, and the terminal 20 may each include only a part of the functions in the embodiments.

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

[0040] The transmitter 110 includes a function of generating a signal to be transmitted to the terminal 20 or another network node 30, and transmitting the signal by wire or wirelessly. The receiver 120 includes a function of receiving various signals transmitted from the terminal 20 or another network node 30, and acquiring, for example, information of a higher layer from the received signal.

[0041] The setting unit 130 stores in a storage device preset setting information and various setting information to be transmitted to the terminal 20, and reads out from the storage device as necessary. The contents of the setting information are, for example, profile information of subscribers in the network.

[0042] As described in the embodiment, the control unit 140 performs processing related to updating profile information of a subscriber in the network. The control unit 140 also performs processing related to communication with the terminal 20. A functional unit in the control unit 140 related to signal transmission may be included in the transmitting unit 110, and a functional unit in the control unit 140 related to signal reception may be included in the receiving unit 120.

[0043] <Terminal 20> Fig. 10 is a diagram showing an example of the functional configuration of terminal 20. As shown in Fig. 10, terminal 20 has transmitting unit 210, receiving unit 220, setting unit 230, and control unit 240. The functional configuration shown in Fig. 10 is merely an example. The functional divisions and names of the functional units may be any names as long as they can perform the operations related to the embodiment of the present invention.

[0044] The transmitter 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiver 220 wirelessly receives various signals and acquires a higher layer signal from the received physical layer signal. 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 the network node 30.

[0045] The setting unit 230 stores various pieces of setting information received from the network node 30 by the receiving unit 220 in a storage device, and reads them out from the storage device as necessary. The setting unit 230 also stores setting information that is set in advance. The contents of the setting information include, for example, information related to a network to which a connection is permitted.

[0046] The control unit 240 performs processing related to connection control to the network and the network slices as described in the embodiment. A functional unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and a functional unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

[0047] (Hardware configuration) The block diagrams (FIGS. 9 and 10) 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 of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically combined, or may be realized using two or more devices that are physically or logically separated and directly or indirectly connected (e.g., using wires, wirelessly, etc.) and these multiple devices. The functional blocks may be realized by combining the one device or the multiple devices with software.

[0048] Functions include, but are not limited to, judgment, determination, judgment, 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, allocation, mapping, assignment, etc. For example, a functional block (component) that performs the function of transmission is called a transmitting unit or a transmitter. In either case, as described above, there is no particular limitation on the method of realization.

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

[0050] 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 devices shown in the figure, or may be configured to exclude some of the devices.

[0051] Each function in the base station 10 and the terminal 20 is realized by loading a specific software (program) onto hardware such as a processor 1001, a memory device 1002, etc., so that the processor 1001 performs calculations, controls communications by the communication device 1004, and controls at least one of reading and writing of data in the memory device 1002 and the auxiliary memory device 1003.

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

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

[0054] The storage device 1002 is a computer-readable recording medium, and may be configured by at least one of, for example, a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), a Random Access Memory (RAM), etc. The storage device 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The storage device 1002 can store a program (program code), software modules, etc. that are executable to implement a communication method according to an embodiment of the present disclosure.

[0055] The auxiliary 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 suitable medium including at least one of the storage device 1002 and the auxiliary storage device 1003.

[0056] The communication device 1004 is hardware (transmission and reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also called, 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., in order to realize at least one of, for example, Frequency Division Duplex (FDD) and Time Division Duplex (TDD). For example, a transmission and reception antenna, an amplifier unit, a transmission and reception unit, a transmission line interface, etc. may be realized by the communication device 1004. The transmission and reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated from each other.

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

[0058] In addition, 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.

[0059] 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), a field programmable gate array (FPGA), etc., 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.

[0060] (Summary of the embodiment) As described above, according to an embodiment of the present invention, a network node is provided which has a transmitting unit which registers a terminal in a UDR (User Data Repository), a receiving unit which receives information identifying the UDR from the UDR in response to the registration of the terminal, and a control unit which associates and retains the terminal and the information identifying the UDR, and when the receiving unit receives a fault notification of the UDR, the control unit causes the terminal which is associated with the UDR and retained to perform a registration operation again.

[0061] With the above configuration, even if a failure occurs in the UDR, the AMF can perform location registration again to update the subscriber's profile information. That is, the subscriber's profile information can be matched in the network.

[0062] The receiving unit may receive a notification of a failure of the UDR from an NRF (Network Repository Function). With this configuration, even if a failure occurs in the UDR, the AMF can perform a location registration operation again to update the subscriber's profile information.

[0063] The notification of the failure of the UDR may be based on information notified to the NRF by a UDR substituting for the UDR. With this configuration, even if a failure occurs in the UDR, the AMF can update the subscriber's profile information by performing a location registration operation again.

[0064] When the receiving unit receives a failure notification of the UDR, the transmitting unit may transmit a request to perform a registration operation again for the terminal associated with the UDR to an SMF (Session Management function) or an SMSF (Short Message Service Function). With this configuration, even if a failure occurs in the UDR, the AMF can request the SMF or SMSF to perform a location registration operation again for the terminal associated with the UDR to update the subscriber's profile information.

[0065] Also, according to an embodiment of the present invention, there is provided a communication method in which a network node executes a transmission procedure for registering a terminal in a UDR (User Data Repository), a reception procedure for receiving information identifying the UDR from the UDR in response to the registration of the terminal, a control procedure for associating and retaining the terminal and the information identifying the UDR, and a procedure for causing the terminal, which is associated with the UDR and retained, to perform a registration operation again when a fault notification of the UDR is received.

[0066] With the above configuration, even if a failure occurs in the UDR, the AMF can perform location registration again to update the subscriber's profile information. That is, the subscriber's profile information can be matched in the network.

[0067] (Supplementary embodiment) Although the embodiment of the present invention has been described above, the disclosed invention is not limited to such an embodiment, and those skilled in the art will understand various modifications, modifications, alternatives, replacements, and the like. Although the description has been given using specific numerical examples to facilitate understanding of the invention, unless otherwise specified, those numerical values ​​are merely examples and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention, and matters described in two or more items may be used in combination as necessary, and matters described in one item may be applied to matters described in another item (as long as there is no contradiction). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operations of multiple functional units may be physically performed by one part, or the operations of one functional unit may be physically performed by multiple parts. The order of the processing procedures described in the embodiment may be changed as long as there is no contradiction. For convenience of the processing description, the network node 30 and the terminal 20 have been described using functional block diagrams, but such devices may be realized by hardware, software, or a combination thereof. The software operated by a processor contained in the network node 30 in accordance with an embodiment of the present invention and the software operated by a processor contained in the terminal 20 in accordance with an embodiment of the present invention may each be stored in a 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.

[0068] 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 of these. Furthermore, the RRC signaling may be called an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0069] Each aspect / embodiment described in the present disclosure may be applied to at least one of systems using LTE (Long Term Evolution), LTE-A (LTE-Advanced), 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-WideBand), Bluetooth (registered trademark), and other suitable systems, and next-generation systems extended based on these. In addition, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A and 5G, etc.) may be applied.

[0070] The steps, sequences, flow charts, etc. of each aspect / embodiment described herein may be reordered unless inconsistent. 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.

[0071] In this specification, a specific operation performed by the network node 30 may be performed by its upper node in some cases. In a network consisting of one or more network nodes including the network node 30, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the network node 30 and other network nodes other than the network node 30 (e.g., MME or 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 30, the other network node may be a combination of multiple other network nodes (e.g., MME and S-GW).

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

[0073] The input and output information may be stored in a specific location (e.g., memory) or may be managed using a management table. The input and output information may be overwritten, updated, or added to. The output information may be deleted. The input information may be transmitted to another device.

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

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

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

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

[0078] In addition, the terms described in this disclosure and the 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). Also, a signal may be a message. Also, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

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

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

[0081] The names used for the above-mentioned parameters are not limiting in any way. Moreover, the formulas 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 limiting in any way.

[0082] In the present disclosure, terms such as "base station (BS)", "wireless 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", "component carrier", etc. may be used interchangeably. A base station may also be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, etc.

[0083] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided 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 term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or a base station subsystem that provides communication services in this coverage.

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

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

[0086] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a moving body, the moving body itself, etc. The moving body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving 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 include a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0087] Furthermore, the base station in the present disclosure may be read as a user terminal. For example, each aspect / embodiment 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 a plurality of terminals 20 (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the terminal 20 may be configured to have the functions of the above-mentioned network node 30. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, an uplink channel, a downlink channel, etc. may be read as a side channel.

[0088] Similarly, a user terminal in the present disclosure may be read as a base station. In this case, the base station may be configured to have the functions of the above-mentioned user terminal.

[0089] 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, search, inquiry (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 a memory), and the like. In addition, "judgment" and "decision" can include considering resolving, selecting, choosing, establishing, comparing, etc., to be a "judgment" or "decision." In other words, "judgment" and "decision" can include considering some action to be a "judgment" or "decision." In addition, "judgment" can be interpreted as "assuming," "expecting," "considering," etc.

[0090] 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 at least one of one or more wires, cables, and 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.

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

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

[0093] Any reference to an element using a designation such as "first," "second," etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient 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 precede the second element in some way.

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

[0095] 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." Further, when used in this disclosure, the term "or" is not intended to be an exclusive or.

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

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

[0098] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched according to execution. In addition, notification of specific information (e.g., notification that "X is the case") is not limited to being done explicitly, but may be done implicitly (e.g., not notifying the specific information).

[0099] Note that the AMF in this disclosure is an example of a network node.

[0100] 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 in the present disclosure. 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. [Explanation of symbols]

[0101] 10 base station 110 Transmitter 120 Receiving unit 130 Setting section 140 Control section 20 Terminals 210 Transmitter 220 Receiving unit 230 Setting section 240 Control Unit 30 Network Nodes 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication equipment 1005 Input Device 1006 Output device

Claims

1. A transmitter for registering a terminal in a User Data Repository (UDR); a receiving unit that receives information for identifying the UDR from the UDR as a response to the registration of the terminal; a control unit that associates and holds information for identifying the terminal and the UDR; A network node, wherein when the receiving unit receives a failure notification of the UDR, the control unit causes the terminal held in association with the UDR to perform a registration operation again.

2. The network node according to claim 1 , wherein the receiving unit receives the failure notification of the UDR from a Network Repository Function (NRF).

3. 3. The network node according to claim 2, wherein the notification of the failure of the UDR is based on information notified to the NRF by a UDR substituting for the UDR.

4. 2. The network node according to claim 1, wherein when the receiving unit receives a failure notification of the UDR, the transmitting unit transmits a request to an SMF (Session Management function) or an SMSF (Short Message Service Function) to perform a registration operation again for a terminal associated with the UDR.

5. A sending procedure for registering the terminal in the UDR (User Data Repository); a receiving step of receiving information identifying the UDR from the UDR as a response to the registration of the terminal; a control procedure for storing information for identifying the terminal and the UDR in association with each other; and when a failure notification of the UDR is received, the network node executes a procedure of causing the terminal held in association with the UDR to perform a registration operation again.

Images