Network node and control method

Abstract

A network node according to the present invention is provided with: a reception unit that receives information indicating a priority level relating to a network function virtualization component (VNFC), and a transmission unit that transmits the priority level information to a network function virtualization component (VNFC), and that transmits the priority level information to the network function virtualization component (VNFC), the reception unit being configured so as to transmit the priority level information to the network function virtualization component (VNFC); and a control unit that determines a VNFC that can be stopped on the basis of the priority level, and that terminates the VNFC that can be stopped and repairs a certain VNFC when a failure has occurred in the certain VNFC.

Description

Technical Field

[0001] This invention relates to network nodes and control methods in communication systems. Background Technology

[0002] Within the 3GPP (3rd Generation Partnership Project), research was conducted on a wireless communication method known as 5G or NR (New Radio) to further increase system capacity, accelerate data transmission speeds, and reduce latency in the radio space. In 5G, various wireless technologies were researched to meet the requirements of achieving throughput of over 10Gbps and achieving latency of less than 1ms in the radio space.

[0003] In NR, research is underway on network architectures that include 5GC (5G Core Network), corresponding to the core network EPC (Evolved Packet Core) in the LTE (Long Term Evolution) network architecture, and NG-RAN (Next Generation-Radio Access Network), corresponding to the RAN (Radio Access Network) E-UTRAN (Evolved Universal Terrestrial Radio Access Network) in the LTE network architecture (e.g., Non-Patent Literature 1 and Non-Patent Literature 2).

[0004] Existing technical documents

[0005] Non-patent literature

[0006] Non-patent literature 1: 3GPP TS 23.501 V18.0.0 (2022-12)

[0007] Non-patent literature 2: 3GPP TS 23.502 V18.0.0 (2022-12) Summary of the Invention

[0008] The problem that the invention aims to solve

[0009] When Network Function Virtualization (NFV) is applied to virtualized Radio Access Networks (vRAN), a component becomes a Single Point of Failure (SPoF). If this component fails, service may become completely inactive.

[0010] The present invention was made in view of the above-mentioned problems, and its purpose is to improve the fault tolerance of applying Network Function Virtualization (NFV) to virtualized Radio Access Network (vRAN).

[0011] Methods for solving problems

[0012] According to the disclosed technology, a network node is provided, comprising: a receiving unit that receives information indicating a priority related to a VNFC (Network Function Virtualization Component); and a control unit that determines which VNFCs can be stopped based on the priority, wherein the control unit terminates the stopable VNFC and repairs the VNFC in the event of a failure of the VNFC.

[0013] Invention Effects

[0014] According to the publicly available technology, it is possible to improve the fault tolerance when applying Network Function Virtualization (NFV) to Virtualized Radio Access Network (vRAN). Attached Figure Description

[0015] Figure 1 This is a diagram used to illustrate an example of a communication system.

[0016] Figure 2 This is a diagram used to illustrate an example of a communication system in a roaming environment.

[0017] Figure 3 This is a diagram used to illustrate an example of NFV.

[0018] Figure 4 This is a diagram used to illustrate an example of vRAN.

[0019] Figure 5This is a flowchart illustrating an example of LCM in vRAN in an embodiment of the present invention.

[0020] Figure 6 This is a diagram illustrating an example of the LCM in the vRAN in an embodiment of the present invention.

[0021] Figure 7 This is a flowchart illustrating an example of VNFC configuration in vRAN in an embodiment of the present invention.

[0022] Figure 8 This is a diagram illustrating an example of VNFC configuration in a vRAN according to an embodiment of the present invention.

[0023] Figure 9 This is a diagram illustrating an example of the functional structure of a base station 10 in an embodiment of the present invention.

[0024] Figure 10 A diagram illustrating an example of the functional structure of terminal 20 in an embodiment of the present invention.

[0025] Figure 11 This is a diagram illustrating an example of the hardware structure of the base station 10 and the terminal 20 in an embodiment of the present invention.

[0026] Figure 12 This is a diagram illustrating an example of the structure of a vehicle 2001 according to an embodiment of the present invention. Detailed Implementation

[0027] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. Furthermore, the embodiments described below are merely examples, and the application of the present invention is not limited to the embodiments described below.

[0028] In the operation of the wireless communication system according to embodiments of the present invention, existing technologies are appropriately used. These existing technologies include, for example, existing LTE, but are not limited to, existing LTE. Furthermore, unless otherwise stated, the term "LTE" as used herein has a broad meaning that includes LTE-Advanced and subsequent modes (e.g., NR) or wireless LAN (Local Area Network).

[0029] Furthermore, in embodiments of the present invention, the "configuration" of wireless parameters, etc., can be a predetermined value that has been pre-configured, or it can be wireless parameters that have been set and notified from network node 30 or terminal 20.

[0030] Figure 1 This is a diagram used to illustrate an example of a communication system. For example... Figure 1As shown, the communication system consists of a UE (User Equipment) as terminal 20 and multiple network nodes 30. Hereinafter, it is assumed that there is one network node 30 corresponding to each function; however, multiple functions can be implemented by one network node 30, or one function can be implemented by multiple network nodes 30. Furthermore, the term "connection" as used below can refer to either a logical connection or a physical connection.

[0031] The RAN (Radio Access Network) is a network node 30 with radio access capabilities, which may include a base station 10 and connect to the UE, AMF (Access and Mobility Management Function), and UPF (User Plane Function). The AMF is a network node 30 with functions such as RAN interface termination, NAS (Non-Access Stratum) termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 with functions such as PDU (Protocol Data Unit) session points interconnected with the DN (Data Network), packet routing and forwarding, and QoS (Quality of Service) processing for the user plane. The UPF and DN constitute a network slice. In the wireless communication network of this embodiment, multiple network slices can also be constructed.

[0032] The AMF connects with the UE, RAN, SMF (Session Management function), NSSF (Network Slice Selection Function), NEF (Network Exposure Function), NRF (Network Repository Function), UDM (Unified Data Management), ASF (Authentication Server Function), PCF (Policy Control Function), and AF (Application Function). AMF, SMF, NSSF, NEF, NRF, UDM, ASF, PCF, and AF are interconnected network nodes 30 via their respective service-based interfaces Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0033] The SMF (Service Provider Function) is a network node 30 with functions such as session management, UE IP (Internet Protocol) address allocation and management, DHCP (Dynamic Host Configuration Protocol) functionality, ARP (Address Resolution Protocol) proxy, and roaming capabilities. The NEF (Network Function Provider Function) is a network node 30 with the ability to notify other NFs (Network Functions) and handle events. The NSSF (Network Slice Selection Assistance Information) is a network node 30 with functions such as selecting the network slice to which the UE connects, determining the allowed NSSAI (Network Slice Selection Assistance Information), determining the configured NSSAI, and determining the set of AMFs to which the UE connects. The PCF (Public Network Function Provider Function) is a network node 30 with the function of controlling network policies. The AF (Application Provider Function) is a network node 30 with the function of controlling application servers. The NRF (Network Provider Function) is a network node 30 with the function of discovering NF instances that provide services. The UDM (User Data Repository) is a network node 30 that manages subscriber data and authentication data. The UDM is connected to the UDR (User Data Repository) that maintains this data.

[0034] Figure 2 This is a diagram illustrating an example of a communication system in a roaming environment. For example... Figure 2 As shown, the network consists of a UE (User Equipment) as terminal 20 and multiple network nodes 30. Hereinafter, it is assumed that there is one network node 30 corresponding to each function; however, multiple functions can be implemented by one network node 30, or one function can be implemented by multiple network nodes 30. Furthermore, the term "connection" as used below can refer to either a logical connection or a physical connection.

[0035] The RAN is a network node 30 with wireless access capabilities, connected to the UE, AMF, and UPF. The AMF is a network node 30 with functions such as RAN interface termination, NAS termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 interconnected with the DN, with functions such as external PDU session points, packet routing and forwarding, and user plane QoS processing. The UPF and DN constitute a network slice. In the wireless communication network of this embodiment, multiple network slices are constructed.

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

[0037] The SMF (Service Provider Function) is a network node 30 with functions such as session management, UE IP address allocation and management, DHCP, ARP proxy, and roaming. The NEF (Network Provider Function) is a network node 30 with the ability to notify other NFs and handle events. The NSSF (Network Provider Function) is a network node 30 with functions such as selecting the network slice the UE connects to, determining the allowed NSSAI (Network Service Access Point), determining the configured NSSAI, and determining the set of AMFs the UE connects to. The PCF (Network Service Function) is a network node 30 with the function of performing network policy control. The AF (Application Provider Function) is a network node 30 with the function of controlling application servers. The NRF (Network Provider Function) is a network node 30 with the function of discovering NF instances that provide services. The SEPP (Secure Provider Proxy) is a non-transparent proxy used to filter control plane messages between PLMNs (Public Land Mobile Networks). Figure 2 The vSEPP shown is the SEPP in the visited network, and the hSEPP is the SEPP in the home network.

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

[0039] Here, when applying NFV (Network Function Virtualization) to vRAN (virtualized Radio Access Network), the methods for utilizing resources are being studied. Figure 3 This is a diagram used to illustrate an example of NFV.

[0040] In NFV, operations such as healing and scaling are defined. Figure 3 As shown, this operation assumes that the resource pool and virtual resources are the same. Figure 3 In the example shown, we envision a VNF (Virtual Network Function) with the same SLA (Service Level Agreement) and a uniform NFVI (NFV Infrastructure). Figure 3 In the example shown, the NFVI consists of a network (NW) and a PC server, and the VNF contains VNFCs (VNF Components) in either an active (Act) state or a standby (Sby) state.

[0041] like Figure 3 As shown, when a fault occurs in VNFC-Sby#1, it is possible to perform a repair based on VNFC-Sby#1 contained in other VNFs.

[0042] On the other hand, in vRAN, there is no redundant structure, or there is an SPoF (Single Point of Failure) where services are completely inactive when certain resources are not functioning, such as processing related to the anchor band or paging channel.

[0043] Figure 4 This is a diagram used to illustrate an example of vRAN. In Figure 4 In this configuration, base station 10A uses VNFC-Act#1 for processing related to the U-Plane frequency band via a switch and a PC server. Base station 10B uses VNFC-Act#1 for processing related to the anchor frequency band via a switch and a PC server.

[0044] In vRAN, such as Figure 4 As shown, the NFVI may have a different structure for each server, and within the VNF, the importance may vary depending on the component. For example, processing related to the U-Plane band may have relatively low importance or priority and may not be an SPoF, while processing related to the anchor band may have relatively high importance or priority and may be an SPoF.

[0045] exist Figure 4 In the example, if a fault occurs in VNFC-Act#4, which handles processes related to the anchor band, it is assumed that it cannot be repaired by VNFC-Act#5 or VNFC-Act#6 in other VNFs. In a vRAN scenario, it is necessary to understand the physical structure and identify the dependencies between components for appropriate priority.

[0046] Therefore, a recovery mechanism based on the structure of NFVI, the structure of each component of VNF, and connection information within vRAN can also be constructed. Furthermore, in the current specification, priority settings only exist at the Ns instance level. Therefore, priority at the component level can also be determined within a limited resource pool, such as vRAN. Additionally, the service impact of SPoF components can be considered, and a mechanism to suppress the number of users accommodated can be introduced.

[0047] It allows for Lifecycle Management (LCM) within a VNF, taking into account NFVI topology and VNFC priorities. It also allows defining which VDU (Virtual Deployment Unit) requires priority and / or which VDU should be prioritized within the VNFD (VNF Descriptor). Furthermore, it extends VNFC information to enable priority storage and modification. Finally, it coordinates with the Element Manager (EM) to confirm which VNFCs can be stopped.

[0048] Figure 5 This is a flowchart illustrating an example of LCM in a vRAN according to an embodiment of the present invention. In step S101, the NFV-MANO (Management and Orchestration) refers to the VNFD that defines the priorities of VDUs. In step S102, the NFV-MANO refers to the extended VNFC information, which allows for priority storage and modification. In step S103, the NFV-MANO confirms with the EM which VNFCs can be stopped through Coordinated Lifecycle Processing (Coordinate LCM). In step S104, in the event of a failure in a high-priority VNFC, the NFV-MANO terminates the stopable VNFC and heals it. Alternatively, the resources of the stopped VNFC can be utilized to heal the high-priority VNFC.

[0049] Figure 6 This is a diagram illustrating an example of the LCM in the vRAN in an embodiment of the present invention. Figure 6 In the vRAN shown, the EM and / or NFMF (Network Function Management Function) can set priorities for NFV-MANO. For example, the EM / NFMF can also set priorities for each VNFC of NFV-MANO as needed.

[0050] like Figure 6As shown, the NFV-MANO can refer to a VNFD containing information indicating the priority of the VDU, or it can refer to a VNFD containing information indicating the priority of the VNFC. The EM and / or NFMF can also set this VNFD for the NFV-MANO.

[0051] As a coordination action related to lifecycle processing, NFV-MANO can also confirm with EM which VNFCs are of low priority or which can be stopped. EM can also determine which VNFCs can be stopped based on priority and notify NFV-MANO. For example, EM can decide to stop a low-priority VNFC, or it can decide to stop a VNFC associated with a low-priority VDU.

[0052] In addition, NFV-MANO can refer to the NFVI topology, or it can use the NFVI topology as a reference to determine which VNF, VNFC, or resource to repair if it becomes an SPoF.

[0053] In addition, NFV-MANO, EM, NFMF, VNF, VNFC, PC server, etc., can also be defined as network node 30. Furthermore, a network node 30 can also contain multiple functions. For example, EM and NFMF can be defined as one network node 30, or EM and NFV-MANO can be defined as one network node 30.

[0054] exist Figure 6 In the example shown, VNFC-Act#3 is an SPoF component. In the event of a failure in VNFC-Act#3, NFV-MANO can terminate the pre-confirmed VNFC-ACT#5 and VNFC-ACT#6, which are stopable VNFCs capable of repairing VNFC-Act#3, and use the resources released by this termination to repair VNFC-Act#3.

[0055] Alternatively, a VNFC configuration that takes into account service impact can be implemented. The service impact in the event of a VNFC failure can also be recorded in the VNFD. NFV-MANO can also determine whether the service impact of a VNFC configured as an SPoF is within a threshold when it is configured; if it is above the threshold, reconfiguration is performed.

[0056] Figure 7This is a flowchart illustrating an example of VNFC configuration in a vRAN according to an embodiment of the present invention. In step S201, NFV-MANO refers to a VNFD that describes the service impact when a VNFC becomes a failure. In step S202, when configuring a VNFC as an SPoF, it is determined whether the service impact of the VNFC is above a threshold. If the service impact is above the threshold (Yes in S202), the process proceeds to step S203; if the service impact is not above the threshold (No in S202), the process ends. If the service impact of a VNFC becoming an SPoF is not above the threshold, the VNFC can be configured. In step S203, NFV-MANO performs reconfiguration of the VNFC that has become an SPoF. For example, the service impact can be distributed by increasing the number of VNFCs that have become SPoFs, or the VNFCs corresponding to VNFCs whose service impact is within the threshold can be reconfigured as VNFCs that have become SPoFs.

[0057] Figure 8 This is a diagram illustrating an example of VNFC configuration in a vRAN according to an embodiment of the present invention. (See diagram for example.) Figure 8 As shown, the policy referenced by NFV-MANO includes a threshold for service impact. For example, this threshold can be set per VNF. Figure 8 In this example, the threshold is 1000 subscribers. Additionally, the VNFD referenced by NFV-MANO can also record the service impact of VNFC failures.

[0058] exist Figure 8 In the example, the VNFD records that VNFC-Act#3, which becomes an SPoF, has a service impact of less than 1000 subscribers during a failure, while the VNFD records that VNFC-Act#4, which becomes an SPoF, has a service impact of more than 1000 subscribers during a failure. Therefore, VNFC-Act#4, which becomes an SPoF, can be reconfigured via NFV-MANO when it is configured.

[0059] According to the above embodiments, VNFCs can be prioritized, increasing the priority of VNFCs that become SPoFs. When a VNFC that has become an SPoF fails, it can be easily repaired. Furthermore, by recording the service impact of a VNFC failure in the VNFD, when configuring a VNFC that has become an SPoF, if the service impact of a failure of that SPoF is too significant, the VNFC can be reconfigured.

[0060] That is, it can improve the fault tolerance when Network Function Virtualization (NFV) is applied to virtualized Radio Access Network (vRAN).

[0061] (Device structure)

[0062] Next, an example of the functional structure of the base station 10, network node 30, and terminal 20 performing the processes and actions described above will be explained. The base station 10, network node 30, and terminal 20 include the functions implemented in the above embodiments. However, the base station 10, network node 30, and terminal 20 may each possess only a portion of the functions described in the embodiments.

[0063] <Base station 10 and network node 30>

[0064] Figure 9 This is a diagram illustrating an example of the functional structure of base station 10. (As shown...) Figure 9 As shown, the base station 10 includes a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. Figure 9 The functional structure shown is merely an example. The functional distinctions and names of the functional units can be arbitrary, as long as the actions of the embodiments of the present invention can be implemented. Network node 30 can have the same functional structure as base station 10. Furthermore, network nodes 30 with multiple different functions in the system architecture can also be composed of multiple network nodes 30 separated by function.

[0065] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 or other network node 30 and transmitting the signal via wired or wireless means. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 or other network node 30 and obtaining, for example, higher-level information from the received signals.

[0066] The setting unit 130 stores preset setting information and various setting information sent to the terminal 20 into a storage device, and reads it from the storage device as needed. The content of the setting information is, for example, the operation-related settings described in the embodiment.

[0067] As described in the embodiment, the control unit 140 performs the operation-related processing described in the embodiment. Additionally, the control unit 140 performs communication-related processing with the terminal 20. Alternatively, the signal transmission-related functions of the control unit 140 may be included in the transmitting unit 110, and the signal reception-related functions of the control unit 140 may be included in the receiving unit 120.

[0068] Terminal 20

[0069] Figure 10 This is a diagram illustrating an example of the functional structure of terminal 20. (As shown...) Figure 10 As shown, the terminal 20 includes a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. Figure 10 The functional structure shown is only one example. The functional distinctions and names of the functional units can be arbitrary, as long as the actions of the embodiments of the present invention can be implemented.

[0070] The transmitting unit 210 generates a transmission signal based on the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 wirelessly receives various signals and obtains higher-layer signals from the received physical layer signals. In addition, the receiving unit 220 has the function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals or reference signals, etc., transmitted from the network node 30.

[0071] The setting unit 230 stores various setting information received by the receiving unit 220 from the network node 30 in a storage device, and reads it from the storage device as needed. Furthermore, the setting unit 230 also stores pre-set setting information. The content of the setting information includes, for example, operation-related settings as described in the embodiment.

[0072] As described in the embodiments, the control unit 240 performs the operation-related processing described in the embodiments. Additionally, the control unit 240 performs processing related to capacity enhancement cells. Alternatively, the signal transmission-related functions of the authentication control unit 240 may be included in the transmitting unit 210, and the signal reception-related functions of the control unit 240 may be included in the receiving unit 220.

[0073] (Hardware structure)

[0074] The block diagrams used in the description of the above embodiments ( Figure 9 as well as Figure 10 The diagram illustrates blocks organized by function. These functional blocks (components) are implemented through any combination of at least one of hardware and software. Furthermore, there are no particular limitations on the implementation method of each functional block. That is, each functional block can be implemented using a single device that is physically or logically combined, or by directly or indirectly (e.g., using wired, wireless, etc.) connecting two or more physically or logically separate devices. Functional blocks can also be implemented by combining software within the aforementioned single or multiple devices.

[0075] The functions include judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, the functional block (structural part) that performs the sending function is called the transmitting unit or transmitter. In short, as mentioned above, there are no particular limitations on the implementation method.

[0076] For example, in one embodiment of this disclosure, network node 30, terminal 20, etc., can also function as a computer for processing the wireless communication method of this disclosure. Figure 11 This diagram illustrates an example of the hardware structure of a base station 10 and a terminal 20 according to one embodiment of the present disclosure. The network node 30 may have the same hardware structure as the base station 10. The base station 10 and terminal 20 may also be configured as a computer device that physically includes a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007, etc.

[0077] Furthermore, in the following description, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware structure of base station 10 and terminal 20 can be configured to include one or more of the devices shown in the figures, or it can be configured to include no part of the device.

[0078] The functions in base station 10 and terminal 20 are implemented by reading predetermined software (programs) into hardware such as processor 1001 and storage device 1002, so that processor 1001 performs calculations and controls the communication of communication device 1004 or controls at least one of reading and writing data in storage device 1002 and auxiliary storage device 1003.

[0079] The processor 1001 controls the computer as a whole by instructing the operating system to operate. The processor 1001 may also be a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, the control unit 140 and control unit 240 described above can also be implemented using the processor 1001.

[0080] Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage devices 1003 and communication devices 1004, and performs various processes accordingly. As a program, a program is used that causes the computer to perform at least a portion of the actions described in the above embodiments. For example, Figure 9 The control unit 140 of the base station 10 shown can also be implemented by a control program stored in the storage device 1002 and operated in the processor 1001. Alternatively, for example, Figure 10 The control unit 240 of the terminal 20 shown can also be implemented by a control program stored in the storage device 1002 and operated in the processor 1001. Although it has been described that the various processes described above are executed by one processor 1001, the various processes described above can also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 can also be implemented by one or more chips. In addition, the program can also be sent from the network via a telecommunications line.

[0081] Storage device 1002 is a computer-readable recording medium, and may be composed of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory). Storage device 1002 may also be referred to as a register, cache, main memory (main storage device), etc. Storage device 1002 can store programs (program code), software modules, etc., that are executable for implementing the communication method according to one embodiment of this disclosure.

[0082] The auxiliary storage device 1003 is a computer-readable recording medium, such as at least one of the following: CD-ROM (CompactDisc ROM) or other optical discs, hard disks, floppy disks, magneto-optical discs (e.g., compact discs, digital multifunction discs, Blu-ray discs), smart cards, flash memory (e.g., cards, sticks, key drives), floppy disks, magnetic stripes, etc. The aforementioned storage medium may, for example, be a database, server, or other suitable media that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0083] The communication device 1004 is hardware (transceiver) used for communication between computers via at least one of a wired network and a wireless network. It may also be referred to as a network device, network controller, network interface card (NIC), communication module, etc. The communication device 1004 may, for example, be configured to include a high-frequency switch, duplexer, filter, frequency synthesizer, etc., to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, transceiver antennas, amplifiers, transceiver units, transmission path interfaces, etc., can also be implemented using the communication device 1004. The transceiver unit may also be physically or logically separated into a transmitting unit and a receiving unit.

[0084] Input device 1005 is an input device that accepts input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, LED, etc.). Alternatively, input device 1005 and output device 1006 can also be integrated (e.g., a touch panel).

[0085] Furthermore, the processor 1001 and storage device 1002, among other devices, are connected via a bus 1007 for communicating information. The bus 1007 can be configured using a single bus or different buses can be used between each device.

[0086] Furthermore, the base station 10 and the terminal 20 can be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or a FPGA (Field Programmable Gate Array), and can also use this hardware to implement part or all of the functional blocks. For example, the processor 1001 can also be implemented using at least one of these hardware components.

[0087] Figure 12 An example of the structure of vehicle 2001 is shown. For example... Figure 12As shown, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a gearshift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021-2029, an information service unit 2012, and a communication module 2013. The various forms / implementations described in this disclosure can also be applied to communication devices mounted on the vehicle 2001, for example, to the communication module 2013.

[0088] The drive unit 2002 may be composed, for example, an engine, a motor, or a hybrid power system of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a steering wheel) 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.

[0089] The electronic control unit 2010 consists of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (I / O port) 2033. Signals from various sensors 2021 to 2029 of the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 can also be referred to as an ECU (Electronic Control Unit).

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

[0091] The Information Service Unit 2012 consists of various devices such as a car navigation system, audio system, speakers, television, and radio, which provide various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The Information Service Unit 2012 uses information obtained from external devices via communication modules 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001.

[0092] The Driver Assistance System 2030 comprises various devices used to prevent accidents or reduce driver workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning devices (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyroscope systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. Furthermore, the Driver Assistance System 2030 transmits and receives various information via the communication module 2013 to achieve driver assistance or autonomous driving functions.

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

[0094] The communication module 2013, controlled by the microprocessor 2031 of the electronic control unit 2010, is a communication device capable of communicating with external devices. For example, it can transmit and receive various types of information with external devices via wireless communication. The communication module 2013 can be located inside or outside the electronic control unit 2010. External devices can be, for example, base stations, mobile stations, etc.

[0095] The communication module 2013 transmits the current signal from the current sensor input to the electronic control unit 2010 to an external device via wireless communication. Additionally, the communication module 2013 also transmits the following signals input to the electronic control unit 2010 via wireless communication to external devices: the front and rear wheel speed signals obtained by the speed sensor 2022; the front and rear wheel air pressure signals obtained by the air pressure sensor 2023; the vehicle speed signal obtained by the vehicle speed sensor 2024; the acceleration signal obtained by the acceleration sensor 2025; the accelerator pedal depressor signal obtained by the accelerator pedal sensor 2029; the brake pedal depressor signal obtained by the brake pedal sensor 2026; the gear shift lever operation signal obtained by the gear shift lever sensor 2027; and the detection signals for detecting obstacles, vehicles, pedestrians, etc., obtained by the object detection sensor 2028.

[0096] The communication module 2013 receives various information (traffic information, signal information, vehicle-to-vehicle information, etc.) sent from external devices and displays it on the information service unit 2012 of the vehicle 2001. Furthermore, the communication module 2013 stores the various information received from external devices in a memory 2032 available to the microprocessor 2031. The microprocessor 2031 can also control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, gearshift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, and sensors 2021-2029 of the vehicle 2001 based on the information stored in the memory 2032.

[0097] (Summary of implementation methods)

[0098] As described above, according to an embodiment of the present invention, a network node is provided, comprising: a receiving unit that receives information indicating a priority related to a VNFC (Network Function Virtualization Component); and a control unit that determines which VNFCs can be stopped based on the priority, wherein the control unit terminates the stopable VNFC and repairs the VNFC in the event that a VNFC has failed.

[0099] Based on the above structure, VNFCs can be prioritized, increasing the priority of VNFCs that become SPoFs. When a VNFC that has become an SPoF fails, it can be easily repaired. That is, it improves fault tolerance when Network Function Virtualization (NFV) is applied to virtualized Radio Access Networks (vRAN).

[0100] In the event of a VNFC failure, the control unit uses resources released by the VNFC that can be stopped after the common lifecycle processing ends to repair that VNFC. According to this structure, VNFCs can be prioritized, increasing the priority of VNFCs that become SPoFs. Repair can be easily performed when a VNFC that has become an SPoF fails.

[0101] The control unit can determine which VNFCs can be stopped based on the priority set for each VDU (Virtual Deployment Unit). According to this structure, VNFCs can be prioritized, increasing the priority of VNFCs that become SPoFs. In the event of a failure in a VNFC that has become an SPoF, repair can be easily performed.

[0102] The control unit determines whether to configure or reconfigure a VNFC based on the service impact of a failure occurring in that VNFC. According to this structure, by recording the service impact of a VNFC failure in the VNFD, when a VNFC configured as an SPoF experiences a significant service impact from a failure, it is possible to reconfigure the VNFC.

[0103] If the service impact of a VNFC failure exceeds a certain threshold, the control unit performs a reconfiguration of that VNFC. According to this structure, by recording the service impact of a VNFC failure in the VNFD, when a VNFC configured as an SPoF experiences a failure, it is possible to reconfigure the VNFC if the service impact of such a failure is too significant.

[0104] In addition, according to an embodiment of the present invention, a control method is provided in which a network node performs the following steps: receiving information indicating a priority related to a VNFC (Network Function Virtualization Component); determining which VNFCs can be stopped based on the priority; and, in the event that a VNFC has failed, terminating the stopable VNFC and repairing the VNFC.

[0105] Based on the above structure, VNFCs can be prioritized, increasing the priority of VNFCs that become SPoFs. When a VNFC that has become an SPoF fails, it can be easily repaired. That is, it improves fault tolerance when Network Function Virtualization (NFV) is applied to virtualized Radio Access Networks (vRAN).

[0106] (Supplement to the implementation method)

[0107] The embodiments of the present invention have been described above, but the disclosed invention is not limited to such embodiments. Those skilled in the art should understand various modifications, alterations, substitutions, and replacements. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these values ​​are merely examples, and any appropriate values ​​may be used. The distinctions between items in the above description are not essential to the present invention. Items described in two or more items may be combined as needed, and items described in one item may be applied to items 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 components. Multiple functional units may be operated by a single physical component, or a single functional unit may be operated by multiple physical components. Regarding the processing described in the embodiments, the order of processing may be interchanged unless there is a contradiction. For ease of explanation, a functional block diagram is used to illustrate the network node 30 and the terminal 20, but such a device may also be implemented by hardware, software, or a combination thereof. According to embodiments of the present invention, software operating through a processor of a network node 30 and software operating through a processor of a terminal 20 can be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server, and other suitable storage media.

[0108] Furthermore, the notification of information is not limited to the forms / implementations described in this disclosure, and other methods may also be used. For example, information notification may be implemented through physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or combinations thereof. In addition, RRC signaling may also be referred to as an RRC message, for example, an RRC connection setup message, an RRC connection reconfiguration message, etc.

[0109] The various forms / implementations described in this disclosure can also be applied to at least one of 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), other suitable systems, and next-generation systems extended therefrom. Furthermore, multiple systems can be combined (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.) for application.

[0110] The various forms / implementations described in this disclosure can also be applied to systems utilizing LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE The system may include at least one of 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), other suitable systems, and next-generation systems based on, modified, created, or defined by these systems. Furthermore, multiple systems may be combined (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.).

[0111] The processing procedures, timing, and flow of the various forms / implementations described in this specification may be rearranged in order, provided there is no contradiction. For example, the elements of various steps are indicated using an illustrative order for the methods described in this disclosure, but are not limited to the specific order indicated.

[0112] In this specification, specific actions performed by network node 30 may sometimes also be performed by its upper node, depending on the circumstances. In a network consisting of one or more network nodes having network node 30, various actions performed for communication with terminal 20 can obviously be performed by at least one of network node 30 and other network nodes besides network node 30 (e.g., consider MME or S-GW, but not limited to these). The above example illustrates the case where there is only one other network node besides network node 30, but other network nodes can also be a combination of multiple other network nodes (e.g., MME and S-GW).

[0113] The information or signals described in this disclosure can be output from a higher (or lower) layer to a lower (or higher) layer. They can also be input or output via multiple network nodes.

[0114] Input or output information can be stored in a specific location (e.g., memory) or managed using a management table. Input or output information can be overwritten, updated, or appended. Output information can also be deleted. Input information can also be sent to other devices.

[0115] The determination in this disclosure can be made by a value represented by 1 bit (0 or 1), by a Boolean value (Boolean: true or false), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value).

[0116] Software, whether called software, firmware, middleware, microcode, hardware description language, or by other names, should be broadly interpreted as referring to commands, command sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

[0117] In addition, software, commands, information, etc., can be sent and received via a transmission medium. For example, when software is sent from a webpage, server, or other remote source using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) etc.) and wireless technologies (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of a transmission medium.

[0118] The information, signals, etc., described in this disclosure can also be represented using any of a variety of different technologies. For example, the data, commands, instructions, information, signals, bits, symbols, chips, etc., that may be involved in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination of these.

[0119] Furthermore, the terms used in this disclosure and those necessary for understanding this disclosure may be replaced with terms that have the same or similar meanings. For example, at least one of the channel and symbol may also be a signal (signaling). Additionally, a signal may also be a message. Furthermore, a component carrier (CC) may also be referred to as carrier frequency, cell, frequency carrier, etc.

[0120] The terms “system” and “network” as used in this disclosure are used interchangeably.

[0121] Furthermore, the information, parameters, etc., described in this disclosure can be represented using absolute values, relative values ​​to predetermined values, or other corresponding information. For example, wireless resources can be indicated using indexes.

[0122] The names used for the above parameters are non-limiting in any respect. Furthermore, the formulas, etc., using these parameters sometimes differ from those explicitly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by all appropriate names, therefore the various names assigned to these channels and information elements are non-limiting in any respect.

[0123] In this disclosure, the terms "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," and "component carrier" are used interchangeably. Sometimes, terms such as macro cell, small cell, femtocell, and picocell are also used to refer to base stations.

[0124] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, its coverage area can be divided into several smaller areas, each of which can provide communication services through a base station subsystem (e.g., a small indoor base station RRH: Remote Radio Head). Terms such as "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base station and base station subsystem providing communication services within that coverage area.

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

[0126] For mobile stations, those skilled in the art sometimes also use the following terms: 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, handheld device, user agent, mobile client, client, or some other appropriate terms.

[0127] At least one of the base station and mobile station can also be referred to as a transmitting device, receiving device, communication device, etc. Furthermore, at least one of the base station and mobile station can also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body can be a vehicle (e.g., a car, an airplane, etc.), a mobile body moving in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanized or unmanned). In addition, at least one of the base station and mobile station also includes devices that do not necessarily move during communication. For example, at least one of the base station and mobile station can be an IoT (Internet of Things) device such as a sensor.

[0128] Furthermore, the base station in this disclosure can also be replaced by a user terminal. For example, replacing the communication between the base station and the user terminal with communication between multiple terminals 20 (e.g., also referred to as D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.) can also apply various forms / implementations of this disclosure. In this case, the terminal 20 can also be configured to have the functions of the network node 30 described above. In addition, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "side"). For example, uplink channel, downlink channel, etc. can also be replaced with side channel.

[0129] Similarly, the user terminal in this disclosure can also be replaced by a base station. In this case, the base station can also be configured to have the functions of the aforementioned user terminal.

[0130] The terms "determining" and "determining" as used in this disclosure sometimes encompass a variety of actions. For example, "determining" or "determining" may include actions such as judging, calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, database, or other data structure), and ascertaining, which are considered as actions of "determining" or "determining." Furthermore, "determining" or "determining" may include actions such as receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, and accessing (e.g., accessing data in memory), which are considered as actions of "determining" or "determining." Moreover, "determining" or "determining" may include actions such as resolving, selecting, choosing, establishing, and comparing, which are considered as actions of "determining" or "determining." That is, "judgment" and "decision" can include situations where certain actions are regarded as having been "judged" or "decided". In addition, "judgment (decision)" can also be replaced by "assuming", "expecting", "considering", etc.

[0131] The terms “connected,” “coupled,” or any variations thereof are intended to indicate any direct or indirect connection or combination between two or more elements, including cases where there is one or more intermediate elements between the two elements that are “connected” or “coupled.” The combination or connection between elements can be physical, logical, or a combination of these. For example, “access” can be used instead of “connected.” In the context of this disclosure, it can be understood that two elements are “connected” or “coupled” to each other using at least one of one or more wires, cables, and printed electrical connections, and, as some non-limiting and non-inclusive examples, using electromagnetic energy with wavelengths in the wireless frequency domain, microwave region, and light (including both visible and invisible regions) to “connect” or “couple” to each other.

[0132] The reference signal can be simply called RS (Reference Signal), or, depending on the standard applied, pilot.

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

[0134] Any reference to elements using the designations "first," "second," etc., as used in this disclosure does not necessarily limit the number or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, references to the first and second elements do not imply that only two elements can be taken, or that in any form the first element must precede the second element.

[0135] Alternatively, the "unit" in the structure of the above devices can be replaced with "section", "circuit", "equipment", etc.

[0136] When the terms "include," "including," and their variations are used in this disclosure, these terms, like the term "comprising," imply inclusion. Furthermore, the term "or" as used in this disclosure does not refer to XOR.

[0137] In this disclosure, for example, in cases where articles are added through translation, such as in English (e.g., a, an, and the), this disclosure may also include cases where the noun following these articles is in a plural form.

[0138] In this disclosure, the phrase "A and B are different" can mean "A and B are not the same." Furthermore, this phrase can also mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."

[0139] The various forms / implementations described in this disclosure can be used individually or in combination, and can be switched depending on the execution. Furthermore, the notification of predetermined information (e.g., a "It is X" notification) is not limited to being explicit, but can also be implicit (e.g., not being notified of the predetermined information).

[0140] The present disclosure has been described in detail above, but it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented as modifications and variations without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the present disclosure is for illustrative purposes only and is not intended to be limiting.

[0141] Label Explanation

[0142] 10 base stations

[0143] 110 Dispatch Department

[0144] 120 Receiving Department

[0145] 130 Setting Department

[0146] 140 Control Department

[0147] 20 terminals

[0148] 210 Sending Department

[0149] 220 Receiving Department

[0150] 230 Setting Department

[0151] 240 Control Department

[0152] 30 network nodes

[0153] 1001 processor

[0154] 1002 Storage device

[0155] 1003 Auxiliary storage device

[0156] 1004 Communication devices

[0157] 1005 Input Device

[0158] 1006 Output Device

[0159] Vehicle 2001

[0160] 2002 Drive Unit

[0161] 2003 Steering Unit

[0162] 2004 Accelerator Pedal

[0163] 2005 Brake Pedal

[0164] 2006 gearshift lever

[0165] 2007 front wheel

[0166] 2008 rear wheel

[0167] 2009 axle

[0168] 2010 Electronic Control Department

[0169] 2012 Information Service Department

[0170] 2013 Communication Module

[0171] 2021 Current Sensor

[0172] 2022 Speed ​​Sensor

[0173] 2023 Barometric Pressure Sensor

[0174] 2024 vehicle speed sensor

[0175] 2025 Accelerometer

[0176] 2026 Brake Pedal Sensor

[0177] 2027 Gearshift sensor

[0178] 2028 Object Detection Sensor

[0179] 2029 Accelerator Pedal Sensor

[0180] 2030 Driver Assistance Systems Department

[0181] 2031 microprocessor

[0182] 2032 Memory (ROM, RAM)

[0183] 2033 Communication Port (IO Port)

Claims

1. A network node having: The receiving unit receives information indicating the priority of the network function virtualization component, namely VNFC; and The control unit, based on the aforementioned priority, determines which VNFCs can be stopped. If a VNFC malfunctions, the control unit terminates the stopable VNFC and repairs the VNFC.

2. The network node according to claim 1, wherein, In the event of a failure in a VNFC, the control unit uses the resources released by the VNFC that can be stopped after the common lifecycle processing ends to repair the VNFC.

3. The network node according to claim 1, wherein, The control unit determines which VNFCs can be stopped based on the priority set for each virtual deployment unit (VDU).

4. The network node according to claim 1, wherein, The control unit determines whether to configure or reconfigure a particular VNFC based on the service impact of a failure occurring in that VNFC.

5. The network node according to claim 1, wherein, If the service impact of a VNFC failure exceeds a threshold, the control unit performs a reconfiguration of that VNFC.

6. A control method in which a network node performs the following steps: Receive information indicating the priority associated with the Network Functions Virtualization Component (VNFC); Based on the aforementioned priorities, determine which VNFCs can be stopped; and In the event of a VNFC failure, the stopable VNFC is terminated, and the VNFC is repaired.

Images