WO2018090386A1 - 一种nf组件异常的处理方法、设备及*** - Google Patents

一种nf组件异常的处理方法、设备及*** Download PDF

Info

Publication number
WO2018090386A1
WO2018090386A1 PCT/CN2016/106685 CN2016106685W WO2018090386A1 WO 2018090386 A1 WO2018090386 A1 WO 2018090386A1 CN 2016106685 W CN2016106685 W CN 2016106685W WO 2018090386 A1 WO2018090386 A1 WO 2018090386A1
Authority
WO
WIPO (PCT)
Prior art keywords
component
management function
warehouse management
identifier
group
Prior art date
Application number
PCT/CN2016/106685
Other languages
English (en)
French (fr)
Inventor
马景旺
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2016/106685 priority Critical patent/WO2018090386A1/zh
Priority to PCT/CN2017/096262 priority patent/WO2018090677A1/zh
Priority to KR1020197018051A priority patent/KR20190088060A/ko
Priority to JP2019527222A priority patent/JP6900481B2/ja
Priority to BR112019010207A priority patent/BR112019010207A2/pt
Priority to EP17872745.9A priority patent/EP3544232B1/en
Priority to KR1020217012526A priority patent/KR102392120B1/ko
Priority to CN201780072067.8A priority patent/CN109983736B/zh
Publication of WO2018090386A1 publication Critical patent/WO2018090386A1/zh
Priority to US16/418,029 priority patent/US11178000B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5077—Logical partitioning of resources; Management or configuration of virtualized resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0677—Localisation of faults
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/085—Retrieval of network configuration; Tracking network configuration history
    • H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5058—Service discovery by the service manager
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/74—Admission control; Resource allocation measures in reaction to resource unavailability
    • H04L47/746—Reaction triggered by a failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/78—Architectures of resource allocation
    • H04L47/783—Distributed allocation of resources, e.g. bandwidth brokers
    • H04L47/787—Bandwidth trade among domains

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a network function (English: Network Function, NF) component abnormality processing method, device and system.
  • NF Network Function
  • the network services implemented by the Evolved Packet Core (EPC) network pass through the network element (English: Network Element, NE) in the EPC network.
  • the service characteristics of the firmware and the processing logic, and the process message interaction between the NEs are implemented.
  • the user access service requires a mobility management entity (English: Mobility Management Entity, MME) and a service gateway in the EPC network. :Serving Gateway, S-GW) and Packet Data Network Gateway (P-GW), Policy and Charging Rules Function (PCRF), and Home Subscriber Server ( English: Home Subscriber Server (HSS) works together and is standardized through standardized business process logic.
  • MME Mobility Management Entity
  • P-GW Packet Data Network Gateway
  • PCRF Policy and Charging Rules Function
  • HSS Home Subscriber Server
  • the business needs of users have also changed, requiring more service models and better service features, such as the demand for ultra-low latency communication and high reliability communication.
  • Demand, etc. changes in the user's business needs bring the demand for multiple network services of the network.
  • the network services provided by the EPC network are solidified and dispersed in each NE.
  • the EPC network needs to redefine and design the processing logic and process interaction of the NE.
  • such a redesign means that the equipment manufacturer has a long development cycle and high cost, which means that the operator cannot timely distribute new network services.
  • the existing technicians usually split the NEs in the core network part into different NF components according to the function category, such as splitting the MME into authentication and security functions, session management functions, NF components such as mobility management functions and access control functions.
  • These functional decoupling and independent NF components perform process message interaction through their supported service interfaces and other NF components to complete the network services provided by the core network.
  • one of the NF components is abnormal (such as overload or failure), it will affect the process message interaction between the NF components, thereby reducing the entire network. The quality of network services.
  • the present invention provides a method, a device, and a system for processing an NF component abnormality, so as to solve the problem that an existing NF component is abnormal, affecting process message interaction between NF components, and causing a decrease in network network service quality.
  • the present application provides a method for processing a network function NF component exception.
  • the method may be applied to a network including a user equipment, a first NF component, and a second NF component, where the user equipment passes the first NF component and the second NF component.
  • the component communicates, and the network further includes: an NF warehouse management function component, the method comprising:
  • the NF warehouse management function component receives an NF discovery request message for requesting the NF warehouse management function component to query whether there is an alternative NF component in the network where the second NF component is located, and the NF warehouse management function component determines that the network has an alternate third NF.
  • the component the NF warehouse management function component sends a first message to the first NF component, the first message includes an identifier of the third NF component, and the first message is used to notify the first NF component to send the received signaling sent by the user equipment to The third NF component.
  • the alternative NF component may refer to an NF component that has the same function as the second NF component and is in the same component group.
  • the second NF component fails (such as overload or fault)
  • the processing is performed to ensure that the normal process message interaction can still be performed between the NF components when the second NF component fails, thereby ensuring the network service quality of the network.
  • the NF warehouse management function component may determine an optional third NF component according to the group identifier to which the second NF component belongs, specifically, the NF warehouse management The function component may pre-store at least one NF component group; the NF discovery request message may include a group identifier to which the second NF component belongs;
  • the NF warehouse management function component After the NF warehouse management function component receives the NF discovery request message that includes the group identifier to which the second NF component belongs, querying at least one NF component group, if at least one NF component group exists in the first NF component group, the first The NF component group is the same as the group identity to which the second NF component belongs, and the first NF component group includes other NF components except the second NF component, and then any of the other NF components is determined as the standby The third NF component selected.
  • the candidate NF component can be queried from the pre-stored at least one component group to receive the signaling sent by the user equipment, and the alternative NF component implements the process message interaction.
  • the NF warehouse management function component may pre-store at least one NF component group by:
  • the NF warehouse management function component receives an NF registration request message including an identifier of each NF component in the network where the second NF component is located, an NF type corresponding to each NF component, and a group identifier to which each NF component belongs, according to the NF registration request Message, generating at least one NF component group, each NF component group including an NF component, and an NF component
  • the identifier of the NF component included in the same NF component group is the same as the group identifier, and after the component group is generated, an NF registration response message is sent to each NF component.
  • the information about each NF component in the network may be stored in the NF warehouse management function component in advance, so that the NF warehouse management work component receives the NF discovery request. After the message, the candidate NF component is queried.
  • the second NF component itself may detect that the second NF component is faulty (eg, overload);
  • the NF warehouse management function component may receive the NF discovery request message sent by the second NF component, and receive the NF discovery request message and query the preparation in the NF warehouse management function component. After the selected third NF component, the first message is sent to the first NF component through the second NF component.
  • the NF warehouse management function component can learn that the second NF component is faulty through the message sent by the second NF component, and notify the first NF component by the second NF component that the NF component that the second NF component works can replace the NF component.
  • the first NF component may detect that the second NF component is faulty (eg, downtime);
  • the NF warehouse management function component can directly receive the NF discovery request message sent by the first NF component, and receive the NF discovery request message and query the preparation in the NF warehouse management function component. After the selected third NF component, the first message is sent directly to the first NF component.
  • the NF warehouse management function component can learn that the second NF component is faulty through the message sent by the first NF component, and directly notify the candidate NF component after determining the candidate NF component.
  • the first NF component can replace which NF component the NF component working on the second NF component is.
  • the present application further provides a method for processing a network function NF component exception, which may be applied to a network including a user equipment, a first NF component, and a second NF component, and the user equipment passes the first NF component and the first
  • the NF component communicates, and the network further includes: an NF warehouse management function component, the method may include:
  • the first NF component receives the first message sent by the NF warehouse management function component and includes the identifier of the third NF component, the third NF component and the second NF component belong to the same NF component group, and the NF component in the same NF component group The function is the same.
  • the first NF component receives the signaling sent by the user equipment, and sends signaling to the third NF component according to the identifier of the third NF component.
  • the third component that is the same function as the second NF component determined by the NF warehouse management function component can be sent to the second component to ensure that the second component is guaranteed to be in the second.
  • normal process message interaction can still be performed between the NF components to ensure the network service quality of the network.
  • the first NF component may detect that the second NF component is faulty ( For example: downtime), and send NF discovery to the NF warehouse management function component to request the NF warehouse management function component to query whether there is a request message for the optional NF component in the network.
  • the NF warehouse management function component can learn that the second NF component is faulty through the message sent by the first NF component, so that the NF warehouse management function component determines the candidate NF component after receiving the message.
  • the second NF component itself may detect that the second NF component is faulty (eg, overload), and when the second NF component detects the second NF component by itself.
  • the NF warehouse management function component receives the first The second NF component sends an NF discovery request message, and the first NF component can receive the first message sent by the NF warehouse management function component through the second NF component.
  • the NF warehouse management function component can learn that the second NF component is faulty through the message sent by the second NF component, and the first NF component knows which NF component the NF component that can replace the second NF component works by the second NF component.
  • the signaling sent by the user equipment includes the identifier of the user equipment, and the method may further include:
  • the first NF component stores a context of the second NF component including: an identifier of the second NF component, and an identifier of the at least one user device in communication with the second NF component, when the first NF component receives the third NF component
  • the context of the second NF component may be updated according to the identifier of the third NF component, and the context of the third NF component is established.
  • the NF component stored by the user may be queried.
  • Context querying the NF component corresponding to the identifier of the user equipment, and sending the signaling to the NF component, for example, if the identifier of the user equipment is included in the context of the third NF component, according to the identifier of the user equipment, The context of the third NF component is queried, and signaling is sent to the third NF component.
  • the correspondence between the user equipment and the NF component that receives the signaling of the user equipment may be stored in the first NF component in advance.
  • the receiving and receiving the information according to the corresponding relationship may be queried.
  • the NF component of the command improves the signaling forwarding speed.
  • the present application further provides a method for processing a network function NF component exception, which may be applied to a network including a user equipment, a first NF component, and a second NF component, and the user equipment passes the first NF component and the first
  • the NF component communicates, and the network further includes: an NF warehouse management function component, the method may include:
  • the second NF component sends an NF discovery request message to the NF warehouse management function component for requesting the NF warehouse management function component to query whether there is an optional NF component in the network, and receives the NF discovery response message sent by the NF warehouse management function component;
  • the discovery response message includes an identifier of the third NF component, and sends a first message to the first NF component to notify the first NF component to send the received signaling of the user equipment to the third NF component, where the first message may be Contains: the identifier of the third NF component.
  • the second NF component may send a message to the NF warehouse management function component for determining the candidate NF component, and the NF warehouse management function component determines the provisioning.
  • the first NF component is notified to replace the NF component of the NF component working by the second NF component, so that the first NF component forwards the received signaling sent by the user equipment to the NF component, thereby ensuring that When the second NF component fails, the normal flow message interaction between the NF components can still be performed to improve the network service quality of the network.
  • the method may further include: the second NF component detects the self overload.
  • an embodiment of the present invention provides an NF warehouse management function component, where the NF warehouse management function component can include:
  • a receiving unit configured to receive an NF discovery request message for requesting the NF warehouse management function component to query whether there is an alternative NF component in the network where the second NF component is located;
  • a determining unit configured to determine that an optional third NF component exists in a network where the NF warehouse management function component is located;
  • a sending unit configured to send, to the first NF component, an identifier that includes the third NF component, and is used to notify the first NF component to send the received signaling sent by the user equipment to the first NF component.
  • the specific implementation manner of the fourth aspect may refer to the first aspect or the first aspect.
  • the behavior of the NF repository management function component in the NF component exception handling method provided by the achievable manner is not repeated here. Therefore, the NF warehouse management function component provided by the fourth aspect can achieve the same beneficial effects as the first aspect.
  • an embodiment of the present invention provides an NF warehouse management function component, where the NF warehouse management function component may include:
  • a communication interface configured to receive an NF discovery request message for requesting the NF warehouse management function component to query whether there is an alternative NF component in the network where the second NF component is located;
  • a processor configured to determine an optional third NF component in a network where the NF warehouse management function component is located;
  • a communication interface configured to send, to the first NF component, an identifier that includes the third NF component, and is used to notify the first NF component to send the received signaling sent by the user equipment to the first message of the third NF component.
  • the specific implementation manner of the fifth aspect may refer to the behavior function of the NF warehouse management function component in the processing method of the NF component exception provided by the implementation of the first aspect or the first aspect, and details are not repeatedly described herein. Therefore, the NF warehouse management function component provided by the fifth aspect can achieve the same beneficial effects as the first aspect. Additionally, the apparatus can also include a memory for coupling with the processor that retains the program instructions and data necessary for the apparatus.
  • an embodiment of the present invention provides a non-transitory computer readable storage medium storing one or more programs, the one or more programs including instructions, when included in the fourth aspect or the fifth aspect or the above
  • the NF Warehouse Management Function component described in any of the implementable modes is executed, the NF Warehouse Management Function component performs the following events:
  • An NF component sends an identifier containing the third NF component and is used to notify the first NF component that the user will receive The signaling sent by the device is sent to the first message of the third NF component.
  • an embodiment of the present invention provides a first NF component, where the first NF component may include:
  • a receiving unit configured to receive a first message that is sent by the NF warehouse management function component and includes an identifier of the third NF component, where the third NF component and the second NF component belong to the same NF component group, and the NF component in the same NF component group
  • the functions are the same, and the second NF component is configured to receive signaling sent by the user equipment;
  • the receiving unit is further configured to receive signaling sent by the user equipment
  • a sending unit configured to send signaling to the third NF component according to the identifier of the third NF component.
  • the specific implementation manner of the seventh aspect may refer to the behavior function of the first NF component in the processing method of the NF component exception provided by the implementation manner of the second aspect or the second aspect, and details are not repeatedly described herein. Therefore, the first NF component provided by the seventh aspect can achieve the same advantageous effects as the second aspect.
  • an embodiment of the present invention provides a first NF component, where the first NF component may include:
  • a communication interface configured to receive a first message that is sent by the NF warehouse management function component and includes an identifier of the third NF component, the third NF component and the second NF component belong to the same NF component group, and the NF component in the same NF component group
  • the functions are the same, and the second NF component is configured to receive signaling sent by the user equipment;
  • a processor configured to send signaling to the third NF component through the communication interface according to the identifier of the third NF component.
  • the specific implementation manner of the eighth aspect may refer to the behavior function of the first NF component in the processing method of the NF component exception provided by the implementation manner of the second aspect or the second aspect, and details are not repeatedly described herein. Therefore, the first NF component provided by the eighth aspect can achieve the same advantageous effects as the second aspect. Additionally, the apparatus can also include a memory for coupling with the processor that retains the program instructions and data necessary for the apparatus.
  • an embodiment of the present invention provides a non-transitory computer readable storage medium storing one or more programs, the one or more programs including instructions, when included in the seventh aspect or the ninth aspect or the above
  • the first NF component is executed, the first NF component is caused to perform the following events:
  • the first message including the identifier of the third NF component, the third NF component and the second NF component belong to the same NF component group, and the NF component in the same NF component group has the same function
  • the second The NF component is configured to receive signaling sent by the user equipment, and receive signaling sent by the user equipment, and send signaling to the third NF component by using the communication interface according to the identifier of the third NF component.
  • the specific implementation manner of the ninth aspect may refer to the behavior function of the first NF component in the processing method of the NF component exception provided by the implementation manner of the second aspect or the second aspect, and details are not repeatedly described herein. Therefore, the first NF component provided by the ninth aspect can achieve the same advantageous effects as the second aspect.
  • an embodiment of the present invention provides a second NF component, where the second NF component may include:
  • a sending unit configured to send, to the NF warehouse management function component, an NF discovery request message for requesting the NF warehouse management function component to query whether there is an optional NF component in a network where the second NF component is located;
  • a receiving unit configured to receive an NF discovery response message that is sent by the NF warehouse management function component and includes an identifier of the third NF component;
  • the sending unit is further configured to send, to the first NF component, an identifier of the third NF component, and configured to notify the first NF component to send the received signaling sent by the user equipment to the The first message of the third NF component.
  • the specific implementation manner of the tenth aspect may refer to the behavior function of the second NF component in the processing method of the NF component exception provided by the implementation manner of the third aspect or the third aspect, and details are not repeatedly described herein. Therefore, the second NF component provided by the tenth aspect can achieve the same advantageous effects as the third aspect.
  • an embodiment of the present invention provides a second NF component, where the second NF component may include:
  • a communication interface configured to send, to the NF warehouse management function component, an NF discovery request message for requesting the NF warehouse management function component to query whether there is an alternative NF component in the network where the second NF component is located;
  • an NF discovery response message that includes an identifier of the third NF component, and the identifier sent to the first NF component includes: the identifier of the third NF component, and is used to notify the An NF component sends the received signaling sent by the user equipment to the first message of the third NF component.
  • the specific implementation manner of the eleventh aspect may refer to the behavior function of the second NF component in the processing method of the NF component exception provided by the implementation manner of the third aspect or the third aspect, and details are not repeatedly described herein. Therefore, the second NF component provided in the eleventh aspect can achieve the same advantageous effects as the third aspect. Additionally, the apparatus can also include a memory for coupling with the processor that retains the program instructions and data necessary for the apparatus.
  • an embodiment of the present invention provides a non-transitory computer readable storage medium storing one or more programs, the one or more programs including instructions, when included in the eighth aspect or the ninth aspect or When the second NF component is executed, the second NF component performs the following events:
  • the NF discovery response message including the identifier of the third NF component, the identifier sent to the first NF component includes: the identifier of the third NF component, and is used to notify the user equipment that the first NF component will receive
  • the sent signaling is sent to the first message of the third NF component.
  • the specific implementation manner of the twelfth aspect may refer to the behavior function of the second NF component in the processing method of the NF component exception provided by the implementation manner of the third aspect or the third aspect, and details are not repeatedly described herein. Therefore, the second NF component provided in the twelfth aspect can achieve the same advantageous effects as the third aspect.
  • the embodiment of the present invention provides a processing system for an NF component abnormality, comprising the NF warehouse management function component according to the fourth aspect or the sixth aspect or the sixth aspect or any one of the foregoing aspects, such as the seventh aspect Or the first NF component of the eighth aspect or the ninth aspect, or the second NF component according to any one of the tenth or eleventh or twelfth aspect or any of the above.
  • the processing system for the NF component abnormality provided by the thirteenth aspect can implement the above-described processing method of the NF component abnormality, and therefore, the same advantageous effects as the above-described NF component abnormality processing method can be achieved.
  • FIG. 1 is a schematic diagram of a network architecture according to an embodiment of the present invention
  • FIG. 1a is a schematic diagram of still another network architecture according to an embodiment of the present invention.
  • FIG. 2 is a schematic diagram of still another network architecture according to an embodiment of the present disclosure.
  • FIG. 3 is a flowchart of a method for processing an NF component exception according to an embodiment of the present invention
  • FIG. 3a is a diagram of a NF warehouse management function component saving NF group according to an embodiment of the present invention. Flow chart of related information;
  • FIG. 4 is a flowchart of still another method for processing an NF component abnormality according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of still another method for processing an NF component exception according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of an NF warehouse management function component 10 according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a first NF component 20 according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a second NF group 30 according to an embodiment of the present invention.
  • FIG. 9 is a structural diagram of a processing system for an NF component abnormality according to an embodiment of the present invention.
  • the main principle of the present invention is to add an NF Repository Function component to the core network, and to use multiple NF components of the same type (for example, components having the same NF type, or components sharing the same user context). , or a component that shares the same network configuration.
  • the NF component does some or all of the work of the NF component that has an exception, ensuring the normal interaction of process messages between the NF components.
  • NF component A component that splits the network functions in the core network according to the functional category. Each NF component corresponds to one or more NF types, or a new NF component introduced to implement a certain NF; the NF component can be used. An application that implements the NF corresponding to the NF component, and the application can be deployed on an application platform or a server, and is invoked by a server or the like to execute the NF corresponding to the NF component, or the NF component can be separately deployed in the core network.
  • the functional modules are not limited in this embodiment of the present invention.
  • the NF component is only used as a functional module deployed in the core network.
  • the NF component can be named differently according to its corresponding network function, so as to distinguish the NF component, for example, the NF component with session management function (English: Session Management, SM) can be called SM component, and will have mobility.
  • the NF component of the management function (English: Mobily Management, MM) is called the MM component, and the NF component with the small data (English: Small Data, SD) function is called the SD component.
  • the SM component is responsible for managing the PDU session connection of the user equipment, including the establishment, update, and deletion of the PDU session connection; the MM component transmits the message about the PDU session between the SM component and the user and the access network; the MM component is responsible for Network access management of user equipment, location management of user equipment, and reachability management of user equipment.
  • NF component anomaly NF component failure or overload.
  • the NF component can be down, causing the NF component to fail, such as: unable to send and receive messages with other NF components.
  • NF component overload can refer to the load on the NF component (such as: received messages) large
  • the CPU is equal to the preset threshold, or the central processing unit (CPU) load on the NF component is greater than or equal to a preset threshold, or the memory consumption of the NF group is greater than or equal to a preset threshold, where the preset threshold can be as needed.
  • the setting is not limited in this embodiment of the present invention.
  • the method for processing an NF component abnormality may be applied to the network system shown in FIG. 1.
  • the network may include: user equipment (English: User Equipment, UE), and access network ( English: Access Network, AN), User Plane (UP) network element, data network (English: Data Network, DN), multiple NF components (such as: the first NF component, the second NF component), The NF warehouse management function component; wherein, the plurality of NF components and the NF warehouse management function component are located in a core network part of the network.
  • the user equipment accesses the data network through the local access network; the access network may be an enhanced long term evolution (eLTE) network, or may be a next generation network access network (English NextGen RAN).
  • the 3rd Generation Partnership Project (3GPP) access network can also be an access network such as Wireless Local Area Networks (WLAN) or fixed access; the user plane network element is mainly responsible for users. Forwarding of business data; NF components are mainly responsible for connection management, security authentication, mobility management, and location management of user equipment. Different NF components can implement certain network functions of the core network by interacting with process messages.
  • NF Warehouse Management Function Components It is mainly used to save information about each NF component in the core network (such as the address of the NF component, the identity of the group where the NF component is located, and the type of the NF component).
  • FIG. 1 is only a schematic diagram, and the NF component shown in FIG. 1 is only an example, and the number thereof is not limited to the solution described in this application, and the number is not limited to the one shown in FIG. Multiple NF components different from those shown in Figure 1 can be deployed within the network.
  • the core network shown in FIG. 1 may also include other control plane network elements, which will not be further described herein.
  • the first NF component 100 in FIG. 1 may include: a communication interface 1011, a processor 1012, a memory 1013, and At least one communication bus 1014 for implementing connection and mutual communication between the devices;
  • the second NF component 200 may include: a communication interface 2011, a processor 2012, a memory 2013, and at least one communication bus 2014, the communication bus 2014 For implementing the connection and mutual communication between these devices;
  • the NF warehouse management function component 300 can include: a communication interface 3011, a processor 3012, a memory 3013, and at least one communication bus 3014 for implementing between the devices Connect and communicate with each other.
  • the communication interface 1011 is a transceiver unit of the first NF component 100, and is mainly used for signaling or message interaction with an external network element.
  • the communication interface 1011 of the first NF component 100 can receive a control signal sent by the user equipment. Or, the control signaling is forwarded to the second NF component 100.
  • the communication interface 2011 is a transceiver unit of the second NF component 200, and is mainly used for signaling or message interaction with an external network element.
  • the communication interface 2011 can receive control signaling sent by the communication interface 2011 of the first NF component 100. Or send a request message to the NF warehouse management function component 300.
  • the communication interface 3011 is a transceiver unit of the NF warehouse management function component 300, and is mainly used for message interaction with an external network element.
  • the communication interface 3011 can receive the communication interface 1011 of the first NF component 100 or the second NF component 200.
  • the request message sent by the communication interface 2011 or the response message is sent to the first NF component 100 or the second NF component 200.
  • the processor 1012, the processor 2012, and the processor 3012 may be a central processing unit (CPU), or may be an application specific integrated circuit (ASIC), or configured to implement the present invention.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • One or more integrated circuits of an embodiment of the invention such as one or more microprocessors (English: Digital Signal Processor, DSP), or one or more Field Programmable Gate Arrays (FPGAs).
  • the memory 1013, the memory 2013, and the memory 3013 may be volatile memory (English: volatile memory), such as: random access memory (RAM); or non-volatile memory (English: non- Volatile memory, such as: read-only memory (English: Read-Only Memory, ROM), flash memory (English: flash memory), hard disk (English: Hard Disk Drive, HDD); can also be a solid state drive (English: Solid -State Drive, SSD), or a combination of the above types of memory.
  • the memory 1013, the memory 2013, and the memory 3013 may be used to store data, code, such that the processor 1012 implements each of the first NF components 100 by running or executing program code stored in the memory 1013 and invoking data stored in the memory 1013.
  • the processor 2012 implements various functions of the second NF component 200 by running or executing program code stored in the memory 2013 and calling data stored in the memory 2013; the processor 3012 is stored in the memory 3013 by running or executing.
  • the internal program code, as well as the data stored in the memory 3013, implement various functions of the NF Warehouse Management Function Component 300.
  • the communication bus 1014, the communication bus 2014, and the communication bus 3014 can be divided into an address bus, a data bus, a control bus, etc., and can be an industry standard architecture (Industry Standard Architecture, ISA) bus, and an external device interconnection (English: Peripheral Component) , PCI) bus or extended industry standard architecture (English: Extended Industry Standard Architecture, EISA) bus.
  • Industry Standard Architecture ISA
  • PCI Peripheral Component
  • EISA Extended Industry Standard Architecture
  • the processor 2012 of the second NF component 200 determines that an abnormality (such as an overload) occurs, and determines that Generate NF discovery after load balancing
  • the request message is sent to the communication interface 3011 of the NF warehouse management function component 300 through the communication interface 2011.
  • the processor 3012 in the NF warehouse management function component 300 receives the NF discovery request message according to the communication interface 3011, and queries The other NF components of the same function of the NF component: the third NF component, the other NF components that determine the same function as the second NF component share the load on the second NF component 200, and return NF to the second NF component 200 through the communication interface 3011.
  • the communication interface 2011 sends the update request message to the communication interface 1011 of the first NF component 100 after receiving the NF discovery response message, and the processor 1012 in the first NF component 100 receives the update request according to the communication interface 1011.
  • the message forwards part of the signaling sent by the received user equipment to other NF components: the third NF component performs processing;
  • the processor 1012 of the first NF component 100 generates an NF discovery request message through the communication interface 1011 to the NF when determining that the second NF component 200 is abnormal (such as downtime) and is inoperable.
  • the communication interface 3011 of the warehouse management function component 300 transmits the NF discovery request message, and the processor 3012 in the NF warehouse management function component 300 receives the NF discovery request message according to the communication interface 3011, and queries other NF components having the same function as the second NF component.
  • the other available NF components that have the same function as the second NF component are determined to complete the work of the second NF component 200, and the NF discovery response message is returned to the first NF component 200 via the communication interface 3011, and the communication interface 1011 receives the NF discovery response message. Then, the processor 1012 forwards all the signaling sent by the user equipment to the other second NF components for processing according to the NF discovery response message received by the communication interface 1011.
  • the NF component in the case that the NF component is abnormal, some or all of the signaling sent by the user equipment may be processed by other NF components having the same function as the NF component, so that the normal interaction of signaling messages between the NF components is implemented, which is well ensured.
  • the quality of network services on the network in the case that the NF component is abnormal, some or all of the signaling sent by the user equipment may be processed by other NF components having the same function as the NF component, so that the normal interaction of signaling messages between the NF components is implemented, which is well ensured.
  • the quality of network services on the network is well ensured.
  • the first NF component described in FIG. 1 and FIG. 1a may be: an SM component or an SD component.
  • the network system may include: a user equipment, an access network, a user plane network element, a data network, an MM component, The SM component and the SD component; wherein the user equipment, the MM component, and the SM component can exchange messages or signaling with each other to complete protocol data unit (PDU) session processing of the user equipment, and If the SM component is abnormal during the session, the solution provided by the embodiment of the present invention may be used to ensure message or signaling interaction between the MM component and other available SM components to ensure normal PDU session; SD component, MM The component and the user equipment can also exchange messages or signaling with each other to provide a small data service for the user equipment.
  • PDU protocol data unit
  • the solution provided by the embodiment of the present invention can also be used to ensure that the MM component and other available. Message or signaling interaction between SD components, so that other SDs continue to provide small data services for user equipment, avoid service interruption, and improve network network. Quality of service.
  • the second NF component can also be other NF components (not shown in FIG. 2), such as: Multimedia Broadcast and Multicast Service (MBMS) component, Policy component.
  • MBMS Multimedia Broadcast and Multicast Service
  • the user data (English: Subscriber Data) component when the second NF component is an NF component other than the SM component or the SD component, the solution provided by the embodiment of the present invention may also be used to solve the problem that occurs when the component is abnormal.
  • the following embodiment shows the first NF component shown in FIG. 2 as an MM component, and the second NF component is an SM component or an SD component as an example, and the steps provided by the embodiment of the present invention are illustrated and described in detail.
  • the process of NF component exceptions, wherein the illustrated steps can also be performed in a set of computer systems that execute instructions.
  • logical sequences are shown in the figures, in some cases the steps shown or described may be performed in a different order than the ones described herein.
  • FIG. 3 is a flowchart of a method for processing an NF component exception according to an embodiment of the present invention. The method is performed by the device in the network shown in FIG. 2, and is used to solve the problem that the SM component is overloaded during the session between the user equipment and the SM component. As shown in FIG. 3, the method may include the following steps:
  • Step 101 Establish a PDU session between the at least one user equipment and the SM component 1.
  • Each user equipment can establish a PDU session with the SM component 1 through the AN and the MM component. This process is an existing process, and details are not described herein again. It should be noted that, in FIG. 3, for convenience of description, only a process of establishing a PDU session between the user equipment and the SM component 1 and performing the scheme shown in FIG. 3 is illustrated, and the number of user equipments is not applicable to the solution described in this application. The configuration shown in FIG. 3 can be performed for each user equipment, and details are not described herein again.
  • Step 102 The SM component 1 sends a PDU session registration request message to the MM component.
  • the PDU session registration request message may include: an identifier of the user equipment that establishes a PDU session connection with the SM component 1, an identifier of the PDU session connection, an identifier of the SM component 1, and a group identifier to which the SM component 1 belongs.
  • Step 103 The MM component receives the PDU session registration request message, establishes and saves the context of the PDU session connection, and returns a PDU session registration response message to the SM component 1.
  • the context of the PDU session connection records the session identifier of the PDU session connection, the identifier of the user equipment, and the correspondence between the identifiers of the SM component 1.
  • the PDU session registration response message is used to notify the SM component 1 to complete registration of the secondary PDU session.
  • the session identifier of the PDU session is used to identify the PDU session; the identifier of the user equipment is used to uniquely identify the user equipment, and the identifier may be an International Mobile Subscriber Identity (IMSI); the identifier of the SM component 1 is used for Uniquely identifies the SM component 1.
  • IMSI International Mobile Subscriber Identity
  • Step 104 The SM component 1 detects its own overload.
  • the SM component 1 can detect whether the number of the messages received by the device is greater than or equal to a preset threshold, and if the threshold is greater than or equal to the preset threshold, determine that the overload is self-loaded, and load balancing is required.
  • the memory consumption (such as the memory occupancy rate) is greater than or equal to a preset threshold. If the threshold is greater than or equal to the preset threshold, it is determined that the load is overloaded, and load balancing is required.
  • the preset threshold may be set as needed, which is not limited in this embodiment of the present invention.
  • Step 105 The SM component 1 sends an NF discovery request message to the NF warehouse management function component.
  • the NF discovery request message is used to request the NF warehouse management function component to query whether there is an alternative SM component in the network where the SM component is located.
  • the alternative SM component may be an SM component that has the same function as the SM component 1 and is in the same SM component group.
  • the NF Discovery Request message may include the group identity to which the SM component 1 belongs, or may include the identity of the SM component 1.
  • the NF warehouse management function component pre-stores at least one SM component group, each SM component group includes at least one SM component, one SM component corresponds to one identifier, and the SM components in the same SM component group have the same Internet function.
  • the NF warehouse management function component may store at least one SM component group in the form of a list, and may also be stored in other forms, which is not limited in the embodiment of the present invention.
  • At least one SM component group may be stored by using the solution shown in FIG. 3a.
  • the network management function server deploys and manages each SM component in the network, and determines related information of each SM component, such as: an identifier of the SM component, an NF type corresponding to the SM component, and a group to which the SM component belongs.
  • the group identifiers, and send an NF registration request message to the NF warehouse management function component, where the NF registration request message includes related information of each SM component; after receiving the registration request message, the NF warehouse management function component will have the same NF type and the same group.
  • the SM component of the group identifier and the identifier of each SM component are correspondingly recorded in a group, the group is identified by the group identifier to which the SM component belongs, and the NF registration response message is sent to the network management function server, and the NF warehouse management is performed.
  • the function completes the storage of the SM component group information.
  • the identifier of the SM component is used to uniquely identify the location of the SM component in the network.
  • the identifier of the SM component may be the network address of the SM component.
  • the NF type corresponding to the SM component is used to identify the network function corresponding to the SM.
  • the group identifier to which the SM component belongs is used to identify the group to which the SM component belongs.
  • the identifier of the SM component 1 is the Internet Protocol (IP) address 1
  • the NF type corresponding to the SM component 1 is type 1
  • the group identifier to which the SM component 1 belongs is A
  • the identifier of the SM component 2 is IP address 2
  • the NF type corresponding to the SM component 2 is type 1
  • the group ID of the SM component 2 belongs to A
  • the identifier of the SM component 3 is the IP address 3
  • the NF type corresponding to the SM component 3 is the type 2, SM.
  • the group ID of component 3 belongs to B; the identifier of SM component 4 is IP address 4, the NF type corresponding to SM component 4 is type 2, and the group identifier of SM component 4 belongs to B, and the NF warehouse management function component receives Information about these SM components can be stored in the form of a list (as shown in Table 1 below):
  • the information about the SM component includes, but is not limited to, the identifier of the SM component, the NF type corresponding to the SM component, and the group identifier to which the SM component belongs, and may also include: other NF components accessible by the SM component.
  • the related information and the like are not limited in this embodiment of the present invention.
  • Step 106 The NF warehouse management function component receives the NF discovery request message, queries the stored at least one SM component group, determines that there is an alternative SM component 2, and sends an NF discovery response message to the SM component 1.
  • the NF discovery response message may include: an identifier of the SM component 2, where the NF discovery response message is used to notify the SM component 1 that the SM component 2 having the same function as the SM1 component in the core network can share the load on the SM component 1.
  • the NF warehouse management function component may search for the SM component group corresponding to the identifier according to the identifier of the SM component 1, that is, the SM component group in which the SM component is located, if the SM component group in the query is excluding the SM component For other SM components other than component 1, an SM component is selected as the SM component 2 from other SM components, and the identifier of the SM component 2 is included in the NF discovery response message and sent to the SM component 1.
  • the NF warehouse management function component may query the at least one SM component group to find the SM component group identified by the group identifier to which the SM component 1 belongs in the NF discovery request message, if the SM component group in the queried SM component exists For other SM components other than component 1, an SM component is selected as the SM component 2 from other SM components, and the identifier of the SM component 2 is included in the NF discovery response message and sent to the SM component 1.
  • the NF warehouse management function component After receiving the NF discovery request message, queries the above table 1, and determines that the group ID of the group A also includes the SM component 2, and The identifier of the SM component 2 is: IP address 2, and the IP address 2 is included in the NF discovery response message and sent to the SM component 1.
  • Step 107 The SM component 1 sends an NF update request message to the MM component.
  • the NF update request message may include: an identifier of the SM component 2; and may further include an identifier of the SM component 2 and a load balancing policy.
  • the load balancing policy may be determined by the SM component 1 according to the load of the SM component.
  • the load balancing policy is used to determine the load assumed by each SM component during load balancing, such as the load of the SM component 1 and the SM component 2, To achieve load balancing.
  • the load balancing policy may be: assigning, by the SM component 2, the plurality of user equipments corresponding to the continuous IMSI segment to the SM component 2 of the at least one user equipment that establishes the PDU session with the SM component 1
  • the PDU session, the SM component 1 assumes the PDU session of the remaining user equipment in the at least one user equipment, or the plurality of user equipments corresponding to the continuous IMSI segment are allocated to the SM component 1, and the SM component 1 assumes the PDU session of the user equipment.
  • the SM component 1 assumes a PDU session of the remaining user equipment in at least one user equipment; wherein the continuous IMSI segment may be a part of the continuous IMSI in the IMSI corresponding to the at least one user equipment, instead of all.
  • the SM component 1 can formulate a load balancing policy according to its own load, for example, it can be from 60 to 60.
  • the 40 user equipments corresponding to the IMSI segment of 100 are allocated to the SM component 2, and the PDU session of the 40 devices is completed by the SM component 2, and the PDU sessions of the remaining 160 user devices are still completed by the SM component 1.
  • the load balancing policy can also be: IMSI hashing rules, such as: will be with the SM component 1
  • the IMSI corresponding to the at least one user equipment that establishes the PDU session is divided into an even IMSI group and an odd IMSI group, and the even IMSI group includes: all even IMSIs in the IMSI corresponding to at least one user equipment, and the odd IMSI group includes: at least All the odd IMSIs in the IMSI corresponding to one user equipment, the SM component 1 completes the PDU session of the user equipment corresponding to the even IMSI, the SM component 2 completes the PDU session of the user equipment corresponding to the odd IMSI, or the SM component 2 completes the even IMSI Corresponding PDU session of the user equipment, the SM component 1 completes the PDU session of the user equipment corresponding to the odd IMSI,
  • the IMSIs corresponding to the user equipments are from 1 to 200.
  • the user equipment corresponding to the even IMSIs of the 200 IMSIs may be allocated to the SM component 2
  • the PDU session of the 100 devices is completed by the SM component 2
  • the PDU sessions of the remaining 100 user devices are still completed by the SM component 1.
  • Step 108 The MM component receives the NF update request message, updates the context of the SM component 1 according to the load balancing policy, and establishes the context of the SM component 2.
  • the MM component may autonomously decide which user equipments to perform the PDU session with the SM component 1 to allocate to the SM component 2;
  • the MM component determines, according to the load balancing policy, which user equipments that perform the PDU session with the SM component 1 are allocated to the SM component 2, and queries the stored by itself.
  • the context of the SM component 1 deletes the identity of the user equipment assigned to the SM component 2 in the context of the SM component 1, the identity of the user equipment assigned to the SM component 2, the session identifier of the PDU session, and the identity of the SM component 2
  • the correspondence is recorded as the context of the SM2 component.
  • Step 109 The MM component receives the SM signaling sent by the user equipment, and queries the existing information.
  • the context of the stored SM component forwards the SM signaling to the SM component (such as SM component 2) according to the identity of the SM component in the context of the queried SM component.
  • the SM signaling may include: an identifier of the user equipment and a session identifier of the PDU session.
  • the MM component queries, according to the identifier of the user equipment carried in the SM signaling and the session identifier of the PDU session, the identifier that includes the user equipment from the context of the SM component that is stored by the MM component. And the context of the SM component of the identity of the PDU session, and the SM component is sent to the SM component according to the identifier of the SM component in the context of the queried SM component.
  • the SM signaling is sent to the SM component 1, if the identifier of the user equipment and the identifier of the PDU session are included in the context of the SM component 2. And sending the SM signaling to the SM component 2.
  • FIG. 4 it is another A flowchart of a method for processing an NF component exception is performed by a device in the network shown in FIG. 2, and the method may include the following steps:
  • Steps 201-203 wherein the step 201 is the same as the step 101 shown in FIG. 3, the step 202 is the same as the step 102 shown in FIG. 3, and the step 203 is the same as the step 103 shown in FIG.
  • Step 204 The MM component detects that the SM component 1 is down.
  • the MM component can detect the SM component 1 by using the prior art, which is not described in detail in this embodiment of the present invention.
  • Step 205 The MM component sends an NF discovery request message to the NF warehouse management function component.
  • the NF discovery request message is used to request the NF warehouse management function component to query whether there is an alternative SM component in the network where the SM component is located.
  • the NF discovery request message may include the identifier of the SM component 1, or may include the SM component 1 Group ID; an alternate SM component is an SM component that has the same function as SM component 1 and is in the same SM component group.
  • the NF warehouse management function component pre-stores at least one SM component group, each SM component group includes at least one SM component, one SM component corresponds to one identifier, and the SM components in the same SM component group have the same network function. .
  • the NF warehouse management function component may store at least one SM component group in the form of a list, and may also be stored in other forms, which is not limited in the embodiment of the present invention.
  • the process of pre-storing at least one SM component group in the NF warehouse management function component is as shown in FIG. 3a, and details are not described herein again.
  • Step 206 The NF warehouse management function component receives the NF discovery request message, queries the stored at least one SM component group, determines that there is an alternative SM component 2, and sends an NF discovery response message to the MM component.
  • the NF discovery response message may include: an identifier of the SM component 2, where the NF discovery response message is used to notify the SM component 2 that has the same function as the SM1 component in the network where the SM component 1 is located, and can share the load on the SM component 1.
  • Step 207 The MM component receives the NF discovery response message, deletes the context of the SM component 1 according to the NF discovery response message, and establishes the context of the SM component 2.
  • the MM component determines, according to the identifier of the SM component 2 in the response message, that all the services on the SM component 1 are allocated to the SM component 2 for processing, and querying the SM component 1 stored by the MM component.
  • Context the context of the SM component 1 is deleted, and the identifier of the user equipment in the SM component 1, the session identifier of the PDU session, and the correspondence between the identifiers of the SM component 2 are recorded as the context of the SM2 component.
  • Step 208 The MM component receives the SM signaling sent by the user equipment, queries the context of the SM component stored by itself, and forwards the SM signaling to the SM component 2 according to the identifier of the SM component in the queried SM context.
  • the SM signaling may include: an identifier of the user equipment and a session identifier of the PDU session.
  • the MM component queries, according to the identifier of the user equipment carried in the SM signaling and the session identifier of the PDU session, the identifier that includes the user equipment from the context of the SM component that is stored by the MM component. And the context of the SM component of the identity of the PDU session, and the SM component is sent to the SM component according to the identifier of the SM component in the context of the queried SM component.
  • the problem that the SD component is down (not working) during the small data transmission between the user equipment and the SD component may also be solved.
  • FIG. 5 a flowchart of another method for processing an NF component abnormality is performed by a device in the network shown in FIG. 2, and the method may include the following steps:
  • Step 301 The MM component detects that the SD component 1 is down.
  • the MM component can detect the SD component 1 through the prior art, which is not described in detail in this embodiment of the present invention.
  • Step 302 The MM component sends an NF discovery request message to the NF warehouse management function component.
  • the NF discovery request message is used to request the NF warehouse management function component to query whether there is an alternative SD component in the network where the SD component is located, and the NF discovery request message may include the group identifier to which the SD component 1 belongs, or may include the SD The identification of component 1; the alternative SD component may be an SD component that is functionally the same as SD component 1 and that is in the same SD component group.
  • the NF warehouse management function component pre-stores at least one SD component group, each SD component group includes at least one SD component, one SD component corresponds to one identifier, and the SD components in the same SD component group have the same network function. .
  • the NF warehouse management function component may store at least one SD component group in the form of a list, and may also be stored in other forms, which is not limited by the embodiment of the present invention.
  • the process of pre-storing at least one group of SD components in the NF warehouse management function component is as shown in FIG. 3a, and details are not described herein again.
  • Step 303 The NF warehouse management function component receives the NF discovery request message, queries the stored at least one SD component group, determines that there is an alternative SD component 2, and sends an NF discovery response message to the MM.
  • the NF discovery response message may include: an identifier of the SD component 2, and the NF discovery response message is used to notify the SD component 1 that the SD component 2 having the same function as the SD1 component in the EPC network can share the load on the SD component 1.
  • step 106 The process of determining that there is an alternative SD component 2 is the same as step 106 above, and details are not described herein again.
  • Step 304 The MM component receives the NF discovery response message, deletes the context of the SD component 1 according to the NF discovery response message, and establishes the context of the SD component 2.
  • the MM component determines, according to the identifier of the SD component 2 in the response message, that all the services on the SD component 1 are allocated to the SD component 2 for processing, and querying the SD component 1 stored by the MM component.
  • Context the context of the SD component 1 is deleted, and the correspondence between the identity of the user equipment in the SD component 1, the session identifier of the PDU session, and the identity of the SD component 2 is recorded as the context of the SD2 component.
  • Step 305 The MM component receives the SD signaling sent by the user equipment, queries the context of the SD component stored by itself, and forwards the SD signaling to the SD component 2 according to the identifier of the SD component in the queried SD context.
  • the SD signaling may include: an identifier of the user equipment and a session identifier of the PDU session.
  • the MM component queries, according to the identifier of the user equipment carried in the SD signaling and the session identifier of the PDU session, the identifier that includes the user equipment from the context of the SD component that is stored by itself. And the context of the SD component of the identity of the PDU session, sending SD signaling to the SD component based on the identity of the SD component in the context of the queried SD component.
  • the method for processing an NF component exception provided by the embodiment of the present invention is mainly introduced from the perspective of the interaction between the NF warehouse management function component, the first NF component, and the second NF component.
  • the above-mentioned nodes or network elements include corresponding hardware structures and/or software modules for performing respective functions.
  • the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
  • the embodiment of the present invention may divide the function modules of the NF warehouse management function component, the first NF component, and the second NF component according to the foregoing method examples and with reference to FIGS. 6-8, for example, each function module may be divided according to each function. It is also possible to integrate two or more functions into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 6 is a schematic diagram of a possible structure of the NF warehouse management function component 10 involved in the embodiment of the present invention.
  • the NF warehouse management function component 10 is shown in FIG.
  • the NF warehouse management function component 10 can include a receiving unit 101, a determining unit 102, and a sending unit 103.
  • the receiving unit 101 is configured to support the NF warehouse management function.
  • the method can be used to implement the method performed by the NF warehouse management function component.
  • the component performs step 105, step 205 and step 302 in FIGS. 3 to 4;
  • the determining unit 102 is configured to support the NF warehouse management function component to perform step 106, step 206 and step 303 in FIGS. 3 to 5; further, as shown in FIG.
  • the NF warehouse management function component 10 can also include a generating unit 104, which The generating unit 104 is configured to support the NF warehouse management function component to generate at least one NF component group.
  • the receiving unit 101 and the transmitting unit 103 shown in FIG. 6 may be integrated in the communication interface 3011 of the NF warehouse management function component 300 shown in FIG. 1a, and the receiving unit 101 and the communication interface 3011 are executed.
  • the function of the sending unit 103; the determining unit 102 and the generating unit 104 shown in FIG. 6 may be integrated in the processor 3012 of the NF warehouse management function component 300 shown in FIG. 1a, and the determining unit 102 and the generating unit 104 are executed by the processor 3012.
  • the NF warehouse management function component 10 may further include a storage module for storing program code and data of the NF warehouse management function component 10, wherein the processing module may be the NF warehouse management function component 300 shown in FIG. 1a. Memory 3013 in the physical structure.
  • FIG. 7 is a schematic diagram of a possible structure of the first NF component 20 involved in the embodiment of the present invention.
  • the first NF component 20 can be used.
  • the first NF component 20 may include: a receiving unit 201 and a sending unit 202.
  • the receiving unit 201 is configured to support the first NF component 20 to perform the foregoing FIG. 3 to FIG. Step 102, step 107, step 202, step 206, and step 303;
  • the sending unit 202 is configured to support the first NF component 20 to perform the steps 103, 109, 203, and 205 described in the foregoing FIG. 3 to FIG. Step 208, step 302, and step 305.
  • the first NF component 20 may further include: an establishing unit 203 and a detecting unit 204, where the establishing unit 203 is configured to support the first NF component 20 to perform the operations described in the foregoing FIGS. Steps 103, 203, 207, and 307; .
  • the receiving unit 201 and the transmitting unit 202 shown in FIG. 7 can be integrated in the communication interface 1011 of the first NF component 100 shown in FIG. 1a.
  • the function of the receiving unit 201 and the transmitting unit 202 is performed by the communication interface 1011; the establishing unit 203 and the detecting unit 204 shown in FIG. 7 can be integrated in the processor 1012 of the first NF component 100 shown in FIG. 1a, by processing
  • the device 1012 performs the functions of the establishing unit 203 and the detecting unit 204.
  • the first NF component 20 may further include a storage module for storing program code and data of the first NF component 20, wherein the processing module may be in the physical structure of the first NF component 100 shown in FIG. 1a. Memory 1013.
  • FIG. 8 is a schematic diagram of a possible structure of the second NF component 30 involved in the embodiment of the present invention.
  • the second NF component 30 can be used.
  • the second NF 30 may include: a sending unit 301 and a receiving unit 302.
  • the sending unit 301 is configured to support the second NF component 30 to perform the steps shown in FIG. 3 to FIG. 102, step 105, step 107, step 202;
  • the receiving unit 302 is configured to support the second NF component 30 to perform step 103, step 106 and step 203 shown in FIGS. 3 to 5; further, as shown in FIG.
  • the NF component 30 may further include a detecting unit 303 for supporting the second NF component 30 to perform the step 104 shown in FIGS.
  • the transmitting unit 301 and the receiving unit 302 shown in FIG. 8 may be integrated in the communication interface 2011 of the second NF component 200 shown in FIG. 1a, and the transmitting unit 301 is configured to receive and receive by the communication interface 2011.
  • the function of the unit 302; the detecting unit 303 shown in FIG. 8 can be integrated in the processor 2012 of the second NF unit 200 shown in FIG. 1a, and the function of the detecting unit 303 is performed by the processor 2012.
  • the second NF component 20 may further include a storage module for storing program code and data of the second NF component 20, wherein the processing module may be in the physical structure of the second NF component 200 shown in FIG. 1a. Memory 2013.
  • the embodiment of the present invention further provides a processing system for an NF component abnormality.
  • the processing system may include: a user equipment, an NF warehouse management function component 10, a first NF component 20, and a second NF. Component 30.
  • the NF warehouse management function component 10, the first NF component 20, and the second NF component 30 are the same as the above-mentioned devices, and details are not described herein again.
  • the processing system for the NF component abnormality provided by the embodiment of the present invention implements the processing method of the NF component abnormality shown in the foregoing FIG. 3 to FIG. 5, and therefore, the same beneficial effects as the foregoing service transmission method can be achieved, and are not repeated here. Narration.
  • the disclosed system, apparatus, and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical or otherwise.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network devices. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each functional unit may exist independently, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.
  • the above-described integrated unit implemented in the form of a software functional unit can be stored in a computer readable storage medium.
  • the software functional units described above are stored in a storage medium and include instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform portions of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: Universal Serial Bus (USB) flash drive (English: USB flash drive), mobile hard disk, read-only memory (English: read-only memory, ROM), random access

Abstract

本申请提供一种NF组件异常的处理方法、设备及***，涉及通信技术领域，以解决现有NF组件出现异常，影响NF组件间流程消息交互，导致EPC网络的网络服务质量降低的问题。该方法应用于包含用户设备、第一NF组件、第二NF组件以及NF仓库管理功能组件的网络，包括：NF仓库管理功能组件接收包含第二NF组件所属的群组标识的NF发现请求消息，NF仓库管理功能组件根据第二NF组件所属的群组标识，确定网络内存在与第二NF组件相同功能的第三NF组件，NF仓库管理功能组件向第一NF组件发送包含第三NF组件的标识的第一消息，以便第一NF组件将接收到的用户设备发送的信令发往第三NF组件。

Description

一种NF组件异常的处理方法、设备及*** 技术领域
本发明涉及通信技术领域，尤其涉及一种网络功能(英文：Network Function，NF)组件异常的处理方法、设备及***。
背景技术
目前，演进分组核心(英文：Evolved Packet Core，EPC)网络实现的网络业务(如：移动性管理、承载管理和位置网管等功能)是通过EPC网络中网元(英文：Network Element，NE)内固化的服务特性和处理逻辑、以及NE之间的流程消息交互来实现的，如：用户的接入服务需要EPC网络中的移动性管理实体(英文：Mobility Management Entity，MME)、服务网关(英文：Serving Gateway，S-GW)及分组数据网络网关(英文：Packet Data Network Gateway，P-GW)、策略与计费规则功能单元(英文：Policy and Charging Rules Function，PCRF)、以及归属用户服务器(英文：Home Subscriber Server，HSS)共同协作并且通过标准化定义的业务流程逻辑来完成的。
随着商业模式的不断拓展以及技术的不断发展，用户的业务需求也随之发生变化，需求更多服务模式和更优的服务特性，如：超低时延通信的需求以及高可靠性通信的需求等，用户的业务需求的变化带来对网络的多种网络业务的需求。然而，EPC网络所提供的网络服务是固化并分散在各个NE中，此时，如果需要引入新的网络功能来支持用户的业务需求，则EPC网络需要重新定义和设计NE的处理逻辑和流程交互，但这样的重新设计对于设备制造商来说意味着开发周期长和成本高，对于运营商来说意味着不能及时分布新的网络服务。
为解决该问题和满足未来网络的需求，现有技术人员通常将核心网部分内的NE按照功能类别拆分为不同的NF组件，如：将MME拆分为认证和安全功能、会话管理功能、移动管理功能及接入控制功能等NF组件，这些功能解耦和独立的NF组件通过其支持的服务接口和其他NF组件进行流程消息交互完成核心网提供的网络服务。但是，将原有NE拆分为不同NF组件之后，若这些NF组件中其中一NF组件出现异常(如：负载过重或者故障)，则会影响NF组件间的流程消息交互，进而降低整个网络的网络服务质量。
发明内容
本申请提供一种NF组件异常的处理方法、设备及***，以解决现有NF组件出现异常，影响NF组件间流程消息交互，导致网络的网络服务质量降低的问题。
为达到上述目的，本申请采用如下技术方案：
第一方面，本申请提供一种网络功能NF组件异常的处理方法，方法可以应用于包含用户设备、第一NF组件、以及第二NF组件的网络，用户设备通过第一NF组件与第二NF组件进行通信，其特征在于，网络还包括：NF仓库管理功能组件，该方法包括：
NF仓库管理功能组件接收用于请求NF仓库管理功能组件查询第二NF组件所在网络内是否存在备选的NF组件的NF发现请求消息，NF仓库管理功能组件确定网络内存在备选的第三NF组件，NF仓库管理功能组件向第一NF组件发送第一消息，第一消息包含第三NF组件的标识，第一消息用于通知第一NF组件将接收到的用户设备发送的信令发往第三NF组件。
其中，备选的NF组件可以指：与第二NF组件具有相同功能、且在同一组件群组中的NF组件。
如此，在第二NF组件出现故障(如：过载或故障)时，可以 通过NF仓库管理功能组件确定出与该第二NF组件功能相同的第三组件，并通知第一NF组件将原来转发给第二NF组件的信令转发给第三NF组件，由第三NF组件进行处理，以保证在第二NF组件故障时NF组件间仍能进行正常的流程消息交互，保证网络的网络服务质量。
在第一方面的一种可实现方式中，结合第一方面，NF仓库管理功能组件可以根据第二NF组件所属的群组标识来确定出备选的第三NF组件，具体的，NF仓库管理功能组件可以预先存储至少一个NF组件群组；NF发现请求消息可以包含第二NF组件所属的群组标识；
当NF仓库管理功能组件接收到包含第二NF组件所属的群组标识的NF发现请求消息后，查询至少一个NF组件群组，若至少一个NF组件群组存在第一NF组件群组，第一NF组件群组与第二NF组件所属的群组标识相同，且第一NF组件群组包含除第二NF组件之外的其他NF组件，则将其他NF组件中的任一NF组件确定为备选的第三NF组件。
如此，可以从预先存储的至少一个组件群组中查询到备选的NF组件来接收用户设备发送的信令，由备选的NF组件来实现流程消息交互。
在第一方面的再一种可实现方式中，结合第一方面的上一可实现方式，NF仓库管理功能组件可以通过下述方式预先存储至少一个NF组件群组：
NF仓库管理功能组件接收包含第二NF组件所在网络中每个NF组件的标识、每个NF组件所对应的NF类型、每个NF组件所属的群组标识的NF注册请求消息，根据NF注册请求消息，生成至少一个NF组件群组，每个NF组件群组包含NF组件、以及NF组件 的标识，同一NF组件群组包含的NF组件的类型和群组标识相同，并在组件群组生成完成后，向每个NF组件发送NF注册响应消息。
如此，可以预先将网络中每个NF组件的相关信息(如：组件的标识、组件所属的群组标识等等)存储在NF仓库管理功能组件中，以便NF仓库管理工作组件接收到NF发现请求消息后，查询出备选的NF组件。
在第一方面的又一种可实现方式，结合第一方面或第一方面的任一可实现方式，可以由第二NF组件自身检测出第二NF组件出现故障(如：过载)；
当第二NF组件自身检测出第二NF组件故障时，NF仓库管理功能组件可以接收第二NF组件发送的NF发现请求消息，并且在NF仓库管理功能组件接收到NF发现请求消息且查询到备选的第三NF组件后，通过第二NF组件向第一NF组件发送第一消息。
如此，NF仓库管理功能组件可以通过第二NF组件发送的消息获知第二NF组件出现故障，且通过第二NF组件通知第一NF组件可以替代第二NF组件工作的NF组件为哪个NF组件。
在第一方面的又一种可实现方式，结合第一方面或第一方面的任一可实现方式，可以由第一NF组件检测出第二NF组件出现故障(如：宕机)；
当第一NF组件检测出第二NF组件故障时，NF仓库管理功能组件可以直接接收第一NF组件发送的NF发现请求消息，并在NF仓库管理功能组件接收到NF发现请求消息且查询到备选的第三NF组件后，直接向第一NF组件发送第一消息。
如此，NF仓库管理功能组件可以通过第一NF组件发送的消息获知第二NF组件出现故障，且在确定出备选NF组件后，直接通知 第一NF组件可以替代第二NF组件工作的NF组件为哪个NF组件。
第二方面，本申请还提供一种网络功能NF组件异常的处理方法，该方法可以应用于包含用户设备、第一NF组件、以及第二NF组件的网络，用户设备通过第一NF组件与第二NF组件进行通信，其特征在于，网络还包括：NF仓库管理功能组件，该方法可以包括：
第一NF组件接收NF仓库管理功能组件发送的包含第三NF组件的标识的第一消息，第三NF组件与第二NF组件属于同一NF组件群组，同一NF组件群组中的NF组件的功能相同，第一NF组件接收用户设备发送的信令，根据第三NF组件的标识，向第三NF组件发送信令。
如此，在第二NF组件出现故障(如：过载或故障)时，可以通过向NF仓库管理功能组件确定出的与该第二NF组件功能相同的第三组件发送信令，来保证在第二NF组件故障时NF组件间仍能进行正常的流程消息交互，保证网络的网络服务质量。
在第二方面的一种可实现方式中，结合第二方面，在第一NF组件接收NF仓库管理功能组件发送的第一消息之前，可以由第一NF组件检测出第二NF组件出现故障(如：宕机)，并向NF仓库管理功能组件发送NF发现用于请求NF仓库管理功能组件查询网络内是否存在备选的NF组件的请求消息。
如此，NF仓库管理功能组件可以通过第一NF组件发送的消息获知第二NF组件出现故障，以便NF仓库管理功能组件接收到该消息后确定备选NF组件。
在第二方面的一种可实现方式中，结合第二方面，可以由第二NF组件自身检测出第二NF组件出现故障(如：过载)，当第二NF组件自身检测出第二NF组件故障时，NF仓库管理功能组件接收第 二NF组件发送NF发现请求消息，而第一NF组件可以通过第二NF组件接收NF仓库管理功能组件发送的第一消息。
如此，NF仓库管理功能组件可以通过第二NF组件发送的消息获知第二NF组件出现故障，且第一NF组件通过第二NF组件获知可以替代第二NF组件工作的NF组件为哪个NF组件。
在第二方面的再一种可实现方式中，结合第二方面或者第二方面的任一种可实现方式，用户设备发送的信令中包含用户设备的标识，所述方法还可以包括：
第一NF组件中存储有包含：第二NF组件的标识、与第二NF组件通信的至少一个用户设备的标识的第二NF组件的上下文，当第一NF组件接收到包含第三NF组件的标识的第一消息后，可以根据第三NF组件的标识，更新第二NF组件的上下文，建立第三NF组件的上下文，当接收到用户设备的信令后，可以查询自身存储的NF组件的上下文，查询到与用户设备的标识相对应的NF组件，将该信令发送至该NF组件，如：若用户设备的标识包含在第三NF组件的上下文中，则可以根据用户设备的标识、查询第三NF组件的上下文，向第三NF组件发送信令。
如此，可以预先将用户设备与接收该用户设备的信令的NF组件间的对应关系存储在第一NF组件中，当接收到用户设备发送的信令时，根据该对应关系查询出接收该信令的NF组件，提高了信令转发速度。
第三方面，本申请还提供一种网络功能NF组件异常的处理方法，该方法可以应用于包含用户设备、第一NF组件、以及第二NF组件的网络，用户设备通过第一NF组件与第二NF组件进行通信，其特征在于，网络还包括：NF仓库管理功能组件，该方法可以包括：
第二NF组件向NF仓库管理功能组件发送用于请求NF仓库管理功能组件查询网络内存在是否存在备选的NF组件的NF发现请求消息，接收NF仓库管理功能组件发送的NF发现响应消息；NF发现响应消息包含第三NF组件的标识，向第一NF组件发送用于通知第一NF组件将接收到的用户设备发送的信令发往第三NF组件的第一消息，该第一消息可以包含：第三NF组件的标识。
如此，在第二NF组件出现故障(如：过载或故障)时，可以由第二NF组件向NF仓库管理功能组件发送用于确定备选NF组件的消息，待NF仓库管理功能组件确定出备选NF组件后，通知第一NF组件可以替代第二NF组件工作的NF组件为哪个NF组件，以便第一NF组件将接收到的用户设备发送的信令转发至该NF组件，以此保证在第二NF组件故障时NF组件间仍能进行正常的流程消息交互，提高网络的网络服务质量。
在第三方面的一种可实现方式中，结合第三方面，在第二NF组件向NF仓库管理功能组件发送NF发现请求消息之前，该方法还可以包括：第二NF组件检测到自身过载。
第四方面，本发明实施例提供一种NF仓库管理功能组件，该NF仓库管理功能组件可以包括：
接收单元，用于接收用于请求NF仓库管理功能组件查询第二NF组件所在网络内是否存在备选的NF组件的NF发现请求消息；
确定单元，用于确定NF仓库管理功能组件所在网络内存在备选的第三NF组件；
发送单元，用于向第一NF组件发送包含第三NF组件的标识、且用于通知第一NF组件将接收到的用户设备发送的信令发往第三NF组件的第一消息。
其中，第四方面的具体实现方式可以参考第一方面或第一方面 的可实现方式提供的NF组件异常的处理方法中NF仓库管理功能组件的行为功能，在此不再重复赘述。因此，第四方面提供的NF仓库管理功能组件可以达到与第一方面相同的有益效果。
第五方面，本发明实施例提供一种NF仓库管理功能组件，该NF仓库管理功能组件可以包括：
通信接口，用于接收用于请求NF仓库管理功能组件查询第二NF组件所在网络内是否存在备选的NF组件的NF发现请求消息；
处理器，用于确定NF仓库管理功能组件所在网络内存在备选的第三NF组件；
通信接口，用于向第一NF组件发送包含第三NF组件的标识、且用于通知第一NF组件将接收到的用户设备发送的信令发往第三NF组件的第一消息。
其中，第五方面的具体实现方式可以参考第一方面或第一方面的可实现方式提供的NF组件异常的处理方法中NF仓库管理功能组件的行为功能，在此不再重复赘述。因此，第五方面提供的NF仓库管理功能组件可以达到与第一方面相同的有益效果。此外，该装置还可以包括存储器，该存储器用于与处理器耦合，其保存该装置必要的程序指令和数据。
第六方面，本发明实施例提供一种存储一个或多个程序的非易失性计算机可读存储介质，该一个或多个程序包括指令，指令当被包括第四方面或第五方面或上述任一种可实现方式所述的NF仓库管理功能组件执行时，使NF仓库管理功能组件执行以下事件：
接收用于请求NF仓库管理功能组件查询第二NF组件所在网络内是否存在备选的NF组件的NF发现请求消息，确定NF仓库管理功能组件所在网络内存在备选的第三NF组件，向第一NF组件发送包含第三NF组件的标识、且用于通知第一NF组件将接收到的用户 设备发送的信令发往第三NF组件的第一消息。
其中，第六方面的具体实现方式可以参考第一方面或第一方面的可实现方式提供的NF组件异常的处理方法中NF仓库管理功能组件的行为功能，在此不再重复赘述。
第七方面，本发明实施例提供一种第一NF组件，该第一NF组件可以包括：
接收单元，用于接收NF仓库管理功能组件发送的包含第三NF组件的标识的第一消息第三NF组件与第二NF组件属于同一NF组件群组，同一NF组件群组中的NF组件的功能相同，第二NF组件用于接收用户设备发送的信令；
接收单元，还用于接收用户设备发送的信令；
发送单元，用于根据第三NF组件的标识，向第三NF组件发送信令。
其中，第七方面的具体实现方式可以参考第二方面或第二方面的可实现方式提供的NF组件异常的处理方法中第一NF组件的行为功能，在此不再重复赘述。因此，第七方面提供的第一NF组件可以达到与第二方面相同的有益效果。
第八方面，本发明实施例提供一种第一NF组件，该第一NF组件可以包括：
通信接口，用于接收NF仓库管理功能组件发送的包含第三NF组件的标识的第一消息第三NF组件与第二NF组件属于同一NF组件群组，同一NF组件群组中的NF组件的功能相同，第二NF组件用于接收用户设备发送的信令；
以及，接收用户设备发送的信令；
处理器，用于根据第三NF组件的标识，通过通信接口向第三NF组件发送信令。
其中，第八方面的具体实现方式可以参考第二方面或第二方面的可实现方式提供的NF组件异常的处理方法中第一NF组件的行为功能，在此不再重复赘述。因此，第八方面提供的第一NF组件可以达到与第二方面相同的有益效果。此外，该装置还可以包括存储器，该存储器用于与处理器耦合，其保存该装置必要的程序指令和数据。
第九方面，本发明实施例提供一种存储一个或多个程序的非易失性计算机可读存储介质，该一个或多个程序包括指令，指令当被包括第七方面或第九方面或上述任一种可能的实现方式中第一NF组件执行时，使第一NF组件执行以下事件：
接收NF仓库管理功能组件发送的包含第三NF组件的标识的第一消息第三NF组件与第二NF组件属于同一NF组件群组，同一NF组件群组中的NF组件的功能相同，第二NF组件用于接收用户设备发送的信令，以及，接收用户设备发送的信令，根据第三NF组件的标识，通过通信接口向第三NF组件发送信令。
其中，第九方面的具体实现方式可以参考第二方面或第二方面的可实现方式提供的NF组件异常的处理方法中第一NF组件的行为功能，在此不再重复赘述。因此，第九方面提供的第一NF组件可以达到与第二方面相同的有益效果。
第十方面，本发明实施例提供一种第二NF组件，该第二NF组件可以包括：
发送单元，用于向NF仓库管理功能组件发送用于请求所述NF仓库管理功能组件查询所述第二NF组件所在网络内存在是否存在备选的NF组件的NF发现请求消息；
接收单元，用于接收所述NF仓库管理功能组件发送的包含第三NF组件的标识的NF发现响应消息；
发送单元，还用于向第一NF组件发送的包含：所述第三NF组件的标识、且用于通知所述第一NF组件将接收到的所述用户设备发送的信令发往所述第三NF组件的第一消息。
其中，第十方面的具体实现方式可以参考第三方面或第三方面的可实现方式提供的NF组件异常的处理方法中第二NF组件的行为功能，在此不再重复赘述。因此，第十方面提供的第二NF组件可以达到与第三方面相同的有益效果。
第十一方面，本发明实施例提供一种第二NF组件，该第二NF组件可以包括：
通信接口，用于向NF仓库管理功能组件发送用于请求所述NF仓库管理功能组件查询所述第二NF组件所在网络内存在是否存在备选的NF组件的NF发现请求消息；
以及，接收所述NF仓库管理功能组件发送的包含第三NF组件的标识的NF发现响应消息，向第一NF组件发送的包含：所述第三NF组件的标识、且用于通知所述第一NF组件将接收到的所述用户设备发送的信令发往所述第三NF组件的第一消息。
其中，第十一方面的具体实现方式可以参考第三方面或第三方面的可实现方式提供的NF组件异常的处理方法中第二NF组件的行为功能，在此不再重复赘述。因此，第十一方面提供的第二NF组件可以达到与第三方面相同的有益效果。此外，该装置还可以包括存储器，该存储器用于与处理器耦合，其保存该装置必要的程序指令和数据。
第十二方面，本发明实施例提供一种存储一个或多个程序的非易失性计算机可读存储介质，该一个或多个程序包括指令，指令当被包括第八方面或第九方面或上述任一种可实现方式所述第二NF组件执行时，使第二NF组件执行以下事件：
向NF仓库管理功能组件发送用于请求所述NF仓库管理功能组件查询所述第二NF组件所在网络内存在是否存在备选的NF组件的NF发现请求消息，接收所述NF仓库管理功能组件发送的包含第三NF组件的标识的NF发现响应消息，向第一NF组件发送的包含：所述第三NF组件的标识、且用于通知所述第一NF组件将接收到的所述用户设备发送的信令发往所述第三NF组件的第一消息。
其中，第十二方面的具体实现方式可以参考第三方面或第三方面的可实现方式提供的NF组件异常的处理方法中第二NF组件的行为功能，在此不再重复赘述。因此，第十二方面提供的第二NF组件可以达到与第三方面相同的有益效果。
第十三方面，本发明实施例提供一种NF组件异常的处理***，包括如第四方面或第六方面或第六方面或上述任一方式所述的NF仓库管理功能组件、如第七方面或第八方面或第九方面或上述任一方式所述的第一NF组件、如第十方面或第十一方面或第十二方面或上述任一方式所述的第二NF组件。
其中，第十三方面提供的NF组件异常的处理***，可以实现上述所示的NF组件异常的处理方法，因此，可以达到与上述NF组件异常的处理方法相同的有益效果。
附图说明
图1为本发明实施例提供一种网络架构示意图；
图1a为本发明实施例提供的又一种网络架构示意图；
图2为本发明实施例提供的又一种网络架构示意图；
图3为本发明实施例提供的一种NF组件异常的处理方法流程图；
图3a为本发明实施例提供的NF仓库管理功能组件保存NF组 件相关信息的流程图；
图4为本发明实施例提供的又一种NF组件异常的处理方法流程图；
图5为本发明实施例提供的再一种NF组件异常的处理方法流程图；
图6为本发明实施例提供的一种NF仓库管理功能组件10的结构示意图；
图7为本发明实施例提供的一种第一NF组件20的结构示意图；
图8为本发明实施例提供的一种第二NF组30件的结构示意图；
图9为本发明实施例提供的一种NF组件异常的处理***结构图。
具体实施方式
本发明的主要原理是：在核心网中增加NF仓库管理功能(英文：NF Repository Function)组件，将同类型的多个NF组件(如：具有相同NF类型的组件，或者共享同一用户上下文的组件，或者共享同一网络配置的组件)作为一个群组(Cluster)预先保存在NF仓库管理功能组件中，当NF组件出现异常时，从NF仓库管理功能组件中该NF组件所在的群组内选取新的NF组件来完成出现异常的NF组件的部分或者全部工作，保证NF组件间的流程消息的正常交互。
下面结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，在本发明实施例的描述中，需要理解的是，术语“第一”、“第二”、“另一”等指示的***或元件为基于实施例描述的具有一定功能的***或元件，仅是为了便于描述本发明和简化描述，而不是指示或暗示所指的***或元件必须有此命名， 因此不能理解为对本发明的限制。
详细描述本方案之前，为了便于理解本发明所述的技术方案，对本发明中的一些重要名词进行详细解释，需要理解的是，下述名词仅是本发明技术人员为了描述方便进行的命名，并不代表或暗示所指的***或元件必须有此命名，因此不能理解为对本发明的限制：
NF组件：将核心网中的网络功能按照功能类别拆分出来的组件，每个NF组件对应一个或多个NF类型，或者为实现某种NF引入的新的NF组件；NF组件可以是一个用于实现该NF组件对应的NF的应用程序，且该应用程序可以部署在一应用平台或服务器上，供服务器等设备调用以执行NF组件对应的NF，或者NF组件可以为单独部署在核心网中的功能模块，本发明实施例对此不进行限定，本发明实施例仅以NF组件为部署在核心网中的功能模块为例进行说明。其中，NF组件可以按照其对应的网络功能进行不同的命名，以此区分NF组件，如：可以将具有会话管理功能(英文：Session Management，SM)的NF组件称为SM组件，将具有移动性管理功能(英文：Mobily Management，MM)的NF组件称为MM组件、将具有小数据(英文：Small Data，SD)功能的NF组件称为SD组件等等。其中，SM组件负责对用户设备的PDU会话连接进行管理，包括PDU会话连接的建立、更新和删除等；MM组件传递SM组件和用户及接入网之间的PDU会话的有关消息；MM组件负责用户设备的网络接入管理、用户设备的位置管理、用户设备的可达性管理等。
NF组件异常：NF组件故障或者过载。
NF组件故障：可以为NF组件宕机，导致NF组件不能工作，如：不能收发与其他NF组件间交互的消息。
NF组件过载：可以指NF组件上的负载(如：接收的消息)大 于等于预设阈值，或者NF组件上的中央处理器(英文：Central Processing Unit，CPU)负荷大于等于预设阈值，或者NF组的内存消耗大于等于预设阈值，其中，预设阈值可以根据需要进行设置，本发明实施例对此不进行限定。
本发明实施例所述的NF组件异常的处理方法可以应用于图1所示的网络***，如图1所示，该网络可以包括：用户设备(英文：User Equipment，UE)、接入网(英文：Access Network，AN)、用户面(英文：User Plane，UP)网元、数据网络(英文：Data Network，DN)，多个NF组件(如：第一NF组件、第二NF组件)、NF仓库管理功能组件；其中，多个NF组件、NF仓库管理功能组件位于网络的核心网部分。用户设备通过本地的接入网接入数据网络；接入网可以为增强的长期演进(英文：evolved Long Term Evolution，eLTE)网络，也可以为下一代网络接入网(英文NextGen RAN)的第三代合作伙伴计划(英文：3rd Generation Partnership Project，3GPP)接入网，还可以为无线局域网(英文：Wireless Local Area Networks，WLAN)或者固定接入等接入网；用户面网元主要负责用户业务数据的转发；NF组件主要负责用户设备的连接管理、安全认证、移动性管理和位置管理等，不同NF组件间可以通过交互流程消息以实现核心网的某种网络功能，NF仓库管理功能组件主要用于保存核心网中每个NF组件的相关信息(如该NF组件的地址、NF组件所在的群组的标识以及NF组件的类型)。
需要说明的是，图1仅为示意图，图1所示NF组件只是示例，其个数对本申请所述方案不构成限制，其个数不局限于图3所示的几个，在实际部署时网络内可以部署不同于图1所示的多个NF组件。尽管未示出，但是图1所示的核心网还可以包括其他一些控制面网元，在此不再一一赘述。
下面结合图1a对执行本发明实施例提供的方案的主要网元进行详细介绍，如图1a所示，图1中的第一NF组件100可以包括：通信接口1011、处理器1012、存储器1013以及至少一个通信总线1014，通信总线1014用于实现这些装置之间的连接和相互通信；第二NF组件200可以包括：通信接口2011、处理器2012、存储器2013以及至少一个通信总线2014，通信总线2014用于实现这些装置之间的连接和相互通信；NF仓库管理功能组件300可以包括：通信接口3011、处理器3012、存储器3013以及至少一个通信总线3014，通信总线3014用于实现这些装置之间的连接和相互通信。
其中，通信接口1011为第一NF组件100的收发单元，主要用于与外部网元之间进行信令或消息交互，如：第一NF组件100的通信接口1011可接收用户设备发送的控制信令，或者向第二NF组件100转发控制信令。
通信接口2011为第二NF组件200的收发单元，主要用于与外部网元之间进行信令或消息交互，如：通信接口2011可接收第一NF组件100的通信接口2011发送的控制信令，或者向NF仓库管理功能组件300发送请求消息。
通信接口3011为NF仓库管理功能组件300的收发单元，主要用于与外部网元之间进行消息交互，如：通信接口3011可接收第一NF组件100的通信接口1011或者第二NF组件200的通信接口2011发送的请求消息，或者向第一NF组件100或第二NF组件200发送响应消息。
处理器1012、处理器2012、处理器3012可能是中央处理器(英文：Central Processing Unit，CPU)，也可以是特定集成电路(英文：Application Specific Integrated Circuit，ASIC)，或者是被配置成实施本发明实施例的一个或多个集成电路，例如：一个或多个微处理 器(英文：Digital Signal Processor，DSP)，或，一个或者多个现场可编程门阵列(英文：Field Programmable Gate Array，FPGA)。
存储器1013、存储器2013、存储器3013可以是易失性存储器(英文：volatile memory)，如：随机存取存储器(英文：Random-Access Memory，RAM)；也可以是非易失性存储器(英文：non-volatile memory)，如：只读存储器(英文：Read-Only Memory，ROM)、快闪存储器(英文：flash memory)，硬盘(英文：Hard Disk Drive，HDD)；还可以是固态硬盘(英文：Solid-State Drive，SSD)，或者上述种类的存储器的组合。存储器1013、存储器2013、存储器3013可以用于存储数据、代码，以便处理器1012通过运行或执行存储在存储器1013内的程序代码、以及调用存储在存储器1013内的数据实现第一NF组件100的各种功能；处理器2012通过运行或执行存储在存储器2013内的程序代码、以及调用存储在存储器2013内的数据实现第二NF组件200的各种功能；处理器3012通过运行或执行存储在存储器3013内的程序代码、以及调用存储在存储器3013内的数据实现NF仓库管理功能组件300的各种功能。
通信总线1014、通信总线2014、通信总线3014可以分为地址总线、数据总线、控制总线等，可以是工业标准体系结构(英文：Industry Standard Architecture，ISA)总线、外部设备互连(英文：Peripheral Component，PCI)总线或扩展工业标准体系结构(英文：Extended Industry Standard Architecture，EISA)总线等。为便于表示，图1a中仅用一条粗线表示各个通信总线，但并不表示仅有一根总线或一种类型的总线。
具体的，在实现本发明实施例提供的NF组件异常的处理过程中，如图1a中1.1～1.5所示，第二NF组件200的处理器2012在确定自身出现异常(如过载)，确定要进行负载均衡后，生成NF发现 请求消息，通过通信接口2011向NF仓库管理功能组件300的通信接口3011发送该NF发现请求消息，NF仓库管理功能组件300中的处理器3012根据通信接口3011接收到NF发现请求消息，查询与第二NF组件相同功能的其他NF组件：第三NF组件，确定与第二NF组件相同功能的其他NF组件分担第二NF组件200上的负载，并通过通信接口3011向第二NF组件200返回NF发现响应消息，通信接口2011接收到NF发现响应消息后，向第一NF组件100的通信接口1011发送该更新请求消息，第一NF组件100中的处理器1012根据通信接口1011接收到的更新请求消息，将接收到的用户设备发送的部分信令转发给其他NF组件：第三NF组件进行处理；
或者，如图1a中虚线所示，第一NF组件100的处理器1012在确定第二NF组件200出现异常(如宕机)，不能工作时，生成NF发现请求消息，通过通信接口1011向NF仓库管理功能组件300的通信接口3011发送该NF发现请求消息，NF仓库管理功能组件300中的处理器3012根据通信接口3011接收到NF发现请求消息，查询与第二NF组件相同功能的其他NF组件，确定与第二NF组件相同功能的其他可用NF组件来完成第二NF组件200的工作，并通过通信接口3011向第一NF组件200返回NF发现响应消息，通信接口1011接收到NF发现响应消息后，处理器1012根据通信接口1011接收到的NF发现响应消息，将接收到的用户设备发送的信令全部转发给其他第二NF组件进行处理。
如此，在NF组件出现异常的情况下，可以通过与该NF组件相同功能的其他NF组件来处理用户设备发送的部分或者全部信令，实现NF组件间信令消息的正常交互，很好地保证了网络的网络服务质量。
其中，在实际应用中，图1和图1a中所述的第一NF组件可以 为：MM组件，第二NF组件可以为：SM组件或者SD组件，例如，如图2所示，该网络***可以包括：用户设备、接入网、用户面网元、数据网络、MM组件、SM组件以及SD组件；其中，用户设备、MM组件和SM组件之间可以相互交互消息或信令，以完成用户设备的协议数据单元(英文：Protocol Data Unit，PDU)会话(session)处理，且在会话过程中若该SM组件出现异常，则可以通过本发明实施例提供的方案来保证MM组件与其他可用SM组件间进行消息或信令交互，以保证PDU会话的正常进行；SD组件、MM组件以及用户设备之间也可以相互交互消息或信令，为用户设备提供小数据服务，当SD组件出现异常时，同样的，也可以采用本发明实施例提供的方案来保证MM组件与其他可用SD组件间进行消息或信令交互，以便其他SD继续为用户设备提供小数据服务，避免服务中断，提高网络的网络服务质量。
此外，可理解的是，第二NF组件还可以为其他NF组件(图2未示出)，如：多媒体广播多播业务(英文：Multimedia Broadcast and Multicast Service，MBMS)组件、策略(Policy)组件、用户数据(英文：Subscriber Data)组件，当第二NF组件为SM组件或者SD组件之外的其他NF组件时，也可以采用本发明实施例提供的方案来解决该组件异常时出现的问题。
为便于描述，以下实施例以图2所示的第一NF组件为MM组件，第二NF组件为SM组件或者SD组件为例，通过步骤的形式示出并详细描述了本发明实施例提供的NF组件异常的处理过程，其中，示出的步骤也可以在一组可执行指令的计算机***中执行。此外，虽然在图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
图3为本发明实施例提供的一种NF组件异常的处理方法的流 程图，由图2所示网络中的设备交互执行，用于解决用户设备与SM组件间进行会话的过程中SM组件过载的问题，如图3所示，该方法可以包括以下步骤：
步骤101：至少一个用户设备与SM组件1之间建立PDU会话。
其中，每个用户设备可以通过AN、MM组件与SM组件1建立PDU会话，该过程为现有过程，在此不再详细赘述。需要说明的是，图3为便于描述，仅示出了一个用户设备与SM组件1之间建立PDU会话，并执行图3所示方案的过程，其用户设备的个数对本申请所述方案不构成限制，对于每个用户设备而言，都可以执行图3所示的方案，在此不再一一赘述。
步骤102：SM组件1向MM组件发送PDU会话注册请求消息。
其中，该PDU会话注册请求消息可以包含：与SM组件1之间建立PDU会话连接的用户设备的标识、PDU会话连接的标识、SM组件1的标识、以及SM组件1所属的群组标识。
步骤103：MM组件接收到该PDU会话注册请求消息，建立和保存PDU会话连接的上下文，并向SM组件1返回PDU会话注册响应消息。
其中，PDU会话连接的上下文记录有该PDU会话连接的会话标识、用户设备的标识、SM组件1的标识间的对应关系。
该PDU会话注册响应消息用于通知SM组件1完成该次PDU会话的注册。
PDU会话的会话标识用于标识PDU会话；用户设备的标识用于唯一识别该用户设备，该标识可以为国际移动用户识别码(英文：International Mobile Subscriber Identity，IMSI)；SM组件1的标识用于唯一标识该SM组件1。
步骤104：SM组件1检测到自身过载。
可选的，SM组件1可以检测自身接收到的消息的个数是否大于等于预设阈值，若大于等于预设阈值，则确定自身过载，需要进行负载均衡；
或者，检测自身CPU的负荷是否大于等于预设阈值，若大于等于预设阈值，则确定自身过载，需要进行负载均衡；
或者，检测自身内存消耗(如内存占有率)是否大于等于预设阈值，若大于等于预设阈值，则确定自身过载，需要进行负载均衡。
其中，预设阈值可以根据需要进行设置，本发明实施例对此不进行限定。
步骤105：SM组件1向NF仓库管理功能组件发送NF发现请求消息。
其中，该NF发现请求消息用于请求NF仓库管理功能组件查询在SM组件所在网络中否存在备选的SM组件。
其中，备选的SM组件可以为与SM组件1具有相同功能且在同一SM组件群组的SM组件。
该NF发现请求消息可以包含SM组件1所属的群组标识，或者可以包含SM组件1的标识。
其中，NF仓库管理功能组件中预先存储有至少一个SM组件群组，每个SM组件群组包含至少一个SM组件，一个SM组件对应一个标识，且同一SM组件群组中的SM组件具有相同的网络功能。NF仓库管理功能组件可以以列表的形式存储至少一个SM组件群组，也可以通过其他形式进行存储，本发明实施例对此不进行限定。
可选的，可以通过图3a所示的方案将至少一个SM组件群组存 储在NF仓库管理功能组件中。如图3a所示，网络管理功能服务器部署和管理网络中的每个SM组件，确定每个SM组件的相关信息，如：SM组件的标识、SM组件所对应的NF类型、SM组件所属的群组标识，并向NF仓库管理功能组件发送NF注册请求消息，该NF注册请求消息中包含每个SM组件的相关信息；NF仓库管理功能组件接收到注册请求消息后，将相同NF类型、相同群组标识的SM组件、以及每个SM组件的标识对应记录在一个群组中，以SM组件所属的群组标识标识该群组，并向网络管理功能服务器发送NF注册响应消息，至此NF仓库管理功能完成SM组件群组信息的存储。
其中，SM组件的标识用于唯一标识该SM组件在网络中的位置，该SM组件的标识可以为SM组件的网络地址；SM组件所对应的NF类型用于标识该SM对应执行的网络功能，SM组件所属的群组标识用于标识该SM组件所属的群组。
例如：SM组件1的标识为因特网协议(英文：Internet Protocol，IP)地址1，SM组件1所对应的NF类型为类型1，SM组件1所属的群组标识为A；SM组件2的标识为IP地址2，SM组件2所对应的NF类型为类型1，SM组件2所属的群组标识为A；SM组件3的标识为IP地址3，SM组件3所对应的NF类型为类型2，SM组件3所属的群组标识为B；SM组件4的标识为IP地址4，SM组件4所对应的NF类型为类型2，SM组件4所属的群组标识为B，则NF仓库管理功能组件接收到这些SM组件的相关信息，可以采用列表的形式进行存储(如下表1所示)：
表1
Figure PCTCN2016106685-appb-000001
可理解的是，上述SM组件的相关信息包含但不限于：SM组件的标识、SM组件所对应的NF类型、SM组件所属的群组标识，还可以包含：该SM组件可访问的其他NF组件的相关信息等等，本发明实施例对此不进行限定。
步骤106：NF仓库管理功能组件接收NF发现请求消息，查询存储的至少一个SM组件群组，确定存在备选的SM组件2，向SM组件1发送NF发现响应消息。
其中，NF发现响应消息可以包含：SM组件2的标识，该NF发现响应消息用于通知SM组件1该核心网中存在与SM1组件相同功能的SM组件2，可以分担SM组件1上的负载。
可选的，NF仓库管理功能组件可以根据SM组件1的标识查找与该标识对应的SM组件群组，即该SM组件所在的SM组件群组，若查询到的SM组件群组中存在除SM组件1之外的其他SM组件，则从其他SM组件中任选一SM组件作为SM组件2，将该SM组件2的标识包含在NF发现响应消息中发送至SM组件1。
或者，NF仓库管理功能组件可以查询至少一个SM组件群组，找到NF发现请求消息中SM组件1所属的群组标识所标识的SM组件群组，若查询到的SM组件群组中存在除SM组件1之外的其他SM组件，则从其他SM组件中任选一SM组件作为SM组件2，将该SM组件2的标识包含在NF发现响应消息中发送至SM组件1。
例如，若SM组件1所属的群组标识为A，则NF仓库管理功能组件接收到NF发现请求消息后，查询上述表1，确定群组标识为A的群组中还包含SM组件2，且SM组件2的标识为：IP地址2，则将IP地址2包含在NF发现响应消息中发送至SM组件1。
步骤107：SM组件1向MM组件发送NF更新请求消息。
其中，该NF更新请求消息可以包含：SM组件2的标识；还可以包含SM组件2的标识和负载均衡策略。
其中，负载均衡策略可以由SM组件1根据自身负载的情况而定，该负载均衡策略用于明确负载分担时每个SM组件所承担的负载，如：SM组件1、SM组件2的负载情况，以实现负载均衡。
具体的，该负载均衡策略可以为：将与SM组件1建立PDU会话的至少一个用户设备中，与连续IMSI段对应的多个用户设备分配给SM组件2，由SM组件2承担这些用户设备的PDU会话，SM组件1承担至少一个用户设备中剩余的用户设备的PDU会话，或者，与连续IMSI段对应的多个用户设备分配给SM组件1，由SM组件1承担这些用户设备的PDU会话，SM组件1承担至少一个用户设备中剩余的用户设备的PDU会话；其中，连续IMSI段可以为至少一个用户设备对应的IMSI中的一部分连续的IMSI，而不是全部。
例如，与SM组件1建立PDU会话的有200个用户设备，这些用户设备对应的IMSI从1～200，此时，SM组件1可以根据自身负载情况制定负载均衡策略，如：可以将从60～100的IMSI段对应的这40个用户设备分配给SM组件2，由SM组件2完成这40个设备的PDU会话，而其余160个用户设备的PDU会话仍由SM组件1完成。
该负载均衡策略还可以为：IMSI散列规则，如：将与SM组件 1建立PDU会话的至少一个用户设备对应的IMSI分为偶数IMSI群组和奇数IMSI群组，偶数IMSI群组包含：至少一个用户设备对应的IMSI中的全部偶数IMSI，奇数IMSI群组包含：至少一个用户设备对应的IMSI中的全部奇数IMSI，由SM组件1完成偶数IMSI对应的用户设备的PDU会话，由SM组件2完成奇数IMSI对应的用户设备的PDU会话，或者由SM组件2完成偶数IMSI对应的用户设备的PDU会话，由SM组件1完成奇数IMSI对应的用户设备的PDU会话，
例如，与SM组件1建立PDU会话的有200个用户设备，这些用户设备对应的IMSI从1～200，此时，可以将这200个IMSI中的偶数IMSI对应的用户设备分配给SM组件2，由SM组件2完成这100个设备的PDU会话，而其余100个用户设备的PDU会话仍由SM组件1完成。
步骤108：MM组件接收NF更新请求消息，根据负载均衡策略，更新SM组件1的上下文，并建立SM组件2的上下文。
可选的，MM组件接收到仅包含SM组件2的标识的NF更新请求消息后，可以自主决定将与SM组件1进行PDU会话的哪些用户设备分配给SM组件2；
或者，MM组件接收到包含SM组件2的标识和负载均衡策略的NF更新请求消息后，根据负载均衡策略确定将与SM组件1进行PDU会话的哪些用户设备分配给SM组件2，查询自身存储的SM组件1的上下文，删除SM组件1的上下文中分配给SM组件2的用户设备的标识，将分配给SM组件2的用户设备的标识、该PDU会话的会话标识、SM组件2的标识间的对应关系记录为SM2组件的上下文。
步骤109：MM组件接收用户设备发送的SM信令，查询自身存 储的SM组件的上下文，根据查询到的SM组件的上下文中SM组件的标识向该SM组件(如SM组件2)转发SM信令。
其中，该SM信令可以包含：用户设备的标识以及PDU会话的会话标识。
可选的，MM组件接收到用户设备发送的SM信令后，根据SM信令携带的用户设备的标识以及PDU会话的会话标识，从自身存储的SM组件的上下文中查询包含该用户设备的标识以及PDU会话的标识的SM组件的上下文，根据查询到的SM组件的上下文中SM组件的标识向该SM组件发送SM信令。例如：若用户设备的标识以及PDU会话的标识包含在SM组件1的上下文中，则向SM组件1发送该SM信令，若用户设备的标识以及PDU会话的标识包含在SM组件2的上下文中，则向SM组件2发送该SM信令。
如此，采用图3所示的技术方案，在服务于用户设备的SM组件处于过载的状态下，获取同一SM组件群组中的其他可用SM组件，由新的SM组件分担原SM组件的部分业务，为用户设备提供服务，避免业务出现中断，同时降低了原SM组件的负荷，并且在该负载分担的过程中不需要用户设备参与，即对于用户设备而言是不可知的，提高了网络业务的可靠性。
在本发明实施例的又一实现方案中，还可以解决用户设备与SM组件间进行会话的过程中SM组件宕机(不能工作)的问题，具体的，如图4所示，为又一种NF组件异常的处理方法的流程图，由图2所示网络中的设备交互执行，该方法可以包括以下步骤：
步骤201-203，其中，步骤201与图3所示步骤101相同，步骤202与图3所示步骤102相同，步骤203与图3所示步骤103相同，在此不再重复赘述。
步骤204：MM组件检测到SM组件1宕机。
可选的，MM组件可以通过现有技术检测到SM组件1宕机，本发明实施例对此不再进行详细描述。
步骤205：MM组件向NF仓库管理功能组件发送NF发现请求消息。
其中，该NF发现请求消息用于请求NF仓库管理功能组件查询在SM组件所在网络中否存在备选的SM组件，该NF发现请求消息可以包含SM组件1的标识，或者可以包含SM组件1所属的群组标识；备选的SM组件为与SM组件1具有相同功能且在同一SM组件群组的SM组件。
NF仓库管理功能组件中预先存储有至少一个SM组件群组，每个SM组件群组包含至少一个SM组件，一个SM组件对应一个标识，且同一SM组件群组中的SM组件具有相同的网络功能。NF仓库管理功能组件可以以列表的形式存储至少一个SM组件群组，也可以通过其他形式进行存储，本发明实施例对此不进行限定。
具体的，NF仓库管理功能组件中预先存储有至少一个SM组件群组的过程如图3a所示，在此不再重复赘述。
步骤206：NF仓库管理功能组件接收NF发现请求消息，查询存储的至少一个SM组件群组，确定存在备选的SM组件2，向MM组件发送NF发现响应消息。
其中，NF发现响应消息可以包含：SM组件2的标识，该NF发现响应消息用于通知SM组件1所在网络中存在与SM1组件相同功能的SM组件2，可以分担SM组件1上的负载。
其中，步骤206确定存在备选的SM组件2的过程与上述步骤106相同，在此不再重复赘述。
步骤207：MM组件接收NF发现响应消息，根据NF发现响应消息，删除SM组件1的上下文，并建立SM组件2的上下文。
可选的，MM组件接收到NF发现响应消息后，根据该响应消息中SM组件2的标识，确定将SM组件1上的业务全部分配给SM组件2进行处理，查询自身存储的SM组件1的上下文，删除SM组件1的上下文，将SM组件1中的用户设备的标识、PDU会话的会话标识、SM组件2的标识间的对应关系记录为SM2组件的上下文。
步骤208：MM组件接收用户设备发送的SM信令，查询自身存储的SM组件的上下文，根据查询到的SM上下文中的SM组件的标识向SM组件2转发SM信令。
其中，该SM信令可以包含：用户设备的标识以及PDU会话的会话标识。
可选的，MM组件接收到用户设备发送的SM信令后，根据SM信令携带的用户设备的标识以及PDU会话的会话标识，从自身存储的SM组件的上下文中查询包含该用户设备的标识以及PDU会话的标识的SM组件的上下文，根据查询到的SM组件的上下文中SM组件的标识向该SM组件发送SM信令。
如此，采用图4所示的技术方案，在服务于用户设备的SM组件处于宕机(完全不能工作)的状态下，获取同一SM组件群组中的其他可用SM组件，由新的SM组件分担原SM组件的全部业务，为用户设备提供服务，避免业务出现中断，并且在该过程中不需要用户设备参与，即对于用户设备而言是不可知的，提高了网络业务的可靠性。
在本发明实施例的再一实现方案中，还可以解决用户设备与SD组件间进行小数据传输过程中SD组件宕机(不能工作)的问题， 具体的，如图5所示，为又一种NF组件异常的处理方法的流程图，由图2所示网络中的设备交互执行，该方法可以包括以下步骤：
步骤301：MM组件检测到SD组件1宕机。
可选的，MM组件可以通过现有技术检测到SD组件1宕机，本发明实施例对此不再进行详细描述。
步骤302：MM组件向NF仓库管理功能组件发送NF发现请求消息。
其中，该NF发现请求消息用于请求NF仓库管理功能组件查询在SD组件所在网络中否存在备选的SD组件，该NF发现请求消息可以包含SD组件1所属的群组标识，或者可以包含SD组件1的标识；备选的SD组件可以为与SD组件1功能相同且在同一SD组件群组的SD组件。
NF仓库管理功能组件中预先存储有至少一个SD组件群组，每个SD组件群组包含至少一个SD组件，一个SD组件对应一个标识，且同一SD组件群组中的SD组件具有相同的网络功能。NF仓库管理功能组件可以以列表的形式存储至少一个SD组件群组，也可以通过其他形式进行存储，本发明实施例对此不进行限定。
具体的，NF仓库管理功能组件中预先存储有至少一个SD组件群组的过程如图3a所示，在此不再重复赘述。
步骤303：NF仓库管理功能组件接收NF发现请求消息，查询存储的至少一个SD组件群组，确定存在备选的SD组件2，向MM发送NF发现响应消息。
其中，NF发现响应消息可以包含：SD组件2的标识，该NF发现响应消息用于通知SD组件1该EPC网络中存在与SD1组件相同功能的SD组件2，可以分担SD组件1上的负载。
其中，步骤303确定存在备选的SD组件2的过程与上述步骤106相同，在此不再重复赘述。
步骤304：MM组件接收NF发现响应消息，根据NF发现响应消息，删除SD组件1的上下文，并建立SD组件2的上下文。
可选的，MM组件接收到NF发现响应消息后，根据该响应消息中SD组件2的标识，确定将SD组件1上的业务全部分配给SD组件2进行处理，查询自身存储的SD组件1的上下文，删除SD组件1的上下文，将SD组件1中的用户设备的标识、PDU会话的会话标识、SD组件2的标识间的对应关系记录为SD2组件的上下文。
步骤305：MM组件接收用户设备发送的SD信令，查询自身存储的SD组件的上下文，根据查询到的SD上下文中的SD组件的标识向SD组件2转发SD信令。
其中，该SD信令可以包含：用户设备的标识以及PDU会话的会话标识。
可选的，MM组件接收到用户设备发送的SD信令后，根据SD信令携带的用户设备的标识以及PDU会话的会话标识，从自身存储的SD组件的上下文中查询包含该用户设备的标识以及PDU会话的标识的SD组件的上下文，根据查询到的SD组件的上下文中SD组件的标识向该SD组件发送SD信令。
如此，采用图5所示的技术方案，在服务于用户设备的SD组件处于宕机(完全不能工作)的状态下，获取同一SD组件群组中的其他可用SD组件，由新的SD组件分担原SD组件的全部业务，为用户设备提供服务，避免业务出现中断，并且在该过程中不需要用户设备参与，即对于用户设备而言是不可知的，提高了网络业务的可靠性。
上述主要从NF仓库管理功能组件、第一NF组件、第二NF组件交互的角度对本发明实施例提供的NF组件异常的处理方法进行了介绍。可以理解的是，上述节点或网元为了实现上述功能，其包括了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
本发明实施例可以根据上述方法示例、结合附图6～8分别对NF仓库管理功能组件、第一NF组件、第二NF组件进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本发明实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下，图6为本发明实施例中所涉及的NF仓库管理功能组件10的一种可能的结构示意图，如图6所示，NF仓库管理功能组件10可以用于实施方法实施例中NF仓库管理功能组件所执行的方法，该NF仓库管理功能组件10可以包括：接收单元101、确定单元102、发送单元103；接收单元101用于支持NF仓库管理功能组件执行图3～4中的步骤105、步骤205以及步骤302；确定单元102用于支持NF仓库管理功能组件执行图3～5中的步骤106、步骤206以及步骤303；进一步的，如图6所示，NF仓库管理功能组件10还可以包括生成单元104，该 生成单元104用于支持NF仓库管理功能组件生成至少一个NF组件群组。
在采用集成的单元的情况下，图6所示的接收单元101、发送单元103可以集成在图1a所示的NF仓库管理功能组件300的通信接口3011中，由通信接口3011执行接收单元101和发送单元103的功能；图6所示的确定单元102、生成单元104可以集成在图1a所示的NF仓库管理功能组件300的处理器3012中，由处理器3012执行确定单元102以及生成单元104的功能。进一步的，NF仓库管理功能组件10还可以包括存储模块，存储模块用于存储NF仓库管理功能组件10的程序代码和数据，其中，处理模块可以为图1a所示的NF仓库管理功能组件300的实体结构中的存储器3013。
在采用对应各个功能划分各个功能模块的情况下，图7为本发明实施例中所涉及的第一NF组件20的一种可能的结构示意图，如图7所示，第一NF组件20可以用于实施上述方法实施例中第一NF组件所执行的方法，该第一NF组件20可以包括：接收单元201、发送单元202；接收单元201用于支持第一NF组件20执行上述图3～5所述的步骤102、步骤107、步骤202、步骤206以及步骤303；发送单元202用于支持第一NF组件20执行上述图3～5所述的步骤103、步骤109、步骤203、步骤205、步骤208、步骤302以及步骤305；进一步的，该第一NF组件20还可以包括：建立单元203和检测单元204，建立单元203用于支持第一NF组件20执行上述图3～5所述的步骤103、步骤203、步骤207、以及步骤304；检测单元204用于支持第一NF组件20执行上述图3～5所述的步骤108、步骤204、步骤203、步骤205、步骤208、步骤301。
在采用集成的单元的情况下，图7所示的接收单元201、发送单元202可以集成在图1a所示的第一NF组件100的通信接口1011 中，由通信接口1011执行接收单元201、发送单元202的功能；图7所示的建立单元203、检测单元204可以集成在图1a所示的第一NF组件100的处理器1012中，由处理器1012执行建立单元203、检测单元204的功能。进一步的，第一NF组件20还可以包括存储模块，存储模块用于存储第一NF组件20的程序代码和数据，其中，处理模块可以为图1a所示的第一NF组件100的实体结构中的存储器1013。
在采用对应各个功能划分各个功能模块的情况下，图8为本发明实施例中所涉及的第二NF组件30的一种可能的结构示意图，如图8所示，第二NF组件30可以用于实施上述方法实施例中第二NF组件执行的方法，该第二NF30可以包括：发送单元301、接收单元302；发送单元301用于支持第二NF组件30执行图3～5所示的步骤102、步骤105、步骤107、步骤202；接收单元302用于支持第二NF组件30执行图3～5所示的步骤103、步骤106以及步骤203；进一步的，如图8所示，第二NF组件30还可以包括：检测单元303，该检测单元303用于支持第二NF组件30执行图3～5所示的步骤104。
在采用集成的单元的情况下，图8所示的发送单元301、接收单元302可以集成在图1a所示的第二NF组件200的通信接口2011中，由通信接口2011执行发送单元301、接收单元302的功能；图8所示的检测单元303可以集成在图1a所示的第二NF组件200的处理器2012中，由处理器2012执行检测单元303的功能。进一步的，第二NF组件20还可以包括存储模块，存储模块用于存储第二NF组件20的程序代码和数据，其中，处理模块可以为图1a所示的第二NF组件200的实体结构中的存储器2013。
需要说明的是，上述方法实施例涉及的各步骤的所有相关内容 均可以援引到对应功能模块的功能描述，在此不再重复赘述。
再一方面，本发明实施例还提供一种NF组件异常的处理***，如图9所示，该处理***可以包括：用户设备、NF仓库管理功能组件10、第一NF组件20、第二NF组件30。
其中，NF仓库管理功能组件10、第一NF组件20、第二NF组件30与上述设备相同，在此不再重复赘述。
此外，本发明实施例提供的NF组件异常的处理***，实现上述图3～5所示的NF组件异常的处理方法，因此，可以达到与上述业务传输方法相同的有益效果，此处不再重复赘述。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的***，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络设备上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个功能单元独立存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
上述以软件功能单元的形式实现的集成的单元，可以存储在一个计算机可读取存储介质中。上述软件功能单元存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述方法的部分步骤。而前述的存储介质包括：通用串行总线(英文：Universal Serial Bus，USB)闪存驱动器(英文：USB flash drive)、移动硬盘、只读存储器(英文：read-only memory，ROM)、随机存取存储器(英文：random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
最后应说明的是：以上实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案脱离权利要求的范围。

Claims (34)

  1. 一种网络功能NF组件异常的处理方法，所述方法应用于包含用户设备、第一NF组件、以及第二NF组件的网络，所述用户设备通过所述第一NF组件与所述第二NF组件进行通信，其特征在于，所述网络还包括：NF仓库管理功能组件，所述方法包括：
    NF仓库管理功能组件接收NF发现请求消息，所述NF发现请求消息用于请求所述NF仓库管理功能组件查询所述第二NF组件所在网络内是否存在备选的NF组件；
    所述NF仓库管理功能组件确定所述网络内存在备选的第三NF组件；
    所述NF仓库管理功能组件向所述第一NF组件发送第一消息，所述第一消息包含所述第三NF组件的标识，所述第一消息用于通知所述第一NF组件将接收到的所述用户设备发送的信令发往所述第三NF组件。
  2. 根据权利要求1所述的方法，其特征在于，在NF仓库管理功能组件接收NF发现请求消息之前，所述方法还包括：
    所述NF仓库管理功能组件接收NF注册请求消息，所述NF注册请求消息包含所述网络中每个NF组件的标识、每个NF组件所对应的NF类型、每个所述NF组件所属的群组标识；
    所述NF仓库管理功能组件根据所述NF注册请求消息，生成至少一个NF组件群组，每个NF组件群组包含NF组件、以及NF组件的标识，同一NF组件群组包含的NF组件的类型和群组标识相同；
    所述NF仓库管理功能组件向每个NF组件发送NF注册响应消息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述NF发现请求消息包含所述第二NF组件所属的群组标识，所述NF仓库管理功能组件确定所述网络内存在备选的第三NF组件，包括：
    所述NF仓库管理功能组件查询所述至少一个NF组件群组；
    若所述至少一个NF组件群组存在第一NF组件群组，所述第一NF组件群组与所述第二NF组件所属的群组标识相同，且所述第一NF组件群组包含除所述第二NF组件之外的其他NF组件，则将其他NF组件中的任一NF组件确定为备选的第三NF组件。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述NF仓库管理功能组件接收NF发现请求消息，包括：
    所述NF仓库管理功能组件接收所述第二NF组件发送的NF发现请求消息；
    所述NF仓库管理功能组件向所述第一NF组件发送第一消息，包括：
    所述NF仓库管理功能组件经所述第二NF组件向所述第一NF组件发送NF发现响应消息，所述NF发现响应消息包含所述第三NF组件的标识。
  5. 根据权利要求1-3任一项所述的方法，其特征在于，所述NF仓库管理功能组件接收NF发现请求消息，包括：
    所述NF仓库管理功能组件接收所述第一NF组件发送的NF发现请求消息。
  6. 一种网络功能NF组件异常的处理方法，所述方法应用于包含用户设备、第一NF组件、以及第二NF组件的网络，所述用户设备通过第一NF组件与所述第二NF组件进行通信，其特征在于，所述网络还包括：NF仓库管理功能组件，所述方法包括：
    所述第一NF组件接收所述NF仓库管理功能组件发送的第一消息，所述第一消息包含第三NF组件的标识，所述第三NF组件与所述第二NF组件属于同一NF组件群组，同一NF组件群组中的NF组件的功能相同；
    所述第一NF组件接收所述用户设备发送的信令；
    所述第一NF组件根据所述第三NF组件的标识，向所述第三NF组件发送所述信令。
  7. 根据权利要求6所述的方法，其特征在于，在所述第一NF组件接收所述NF仓库管理功能组件发送的第一消息之前，所述方法还包括：
    所述第一NF组件检测到所述第二NF组件宕机；
    所述第一NF组件向所述NF仓库管理功能组件发送NF发现请求消息；所述NF发现请求消息用于请求所述NF仓库管理功能组件查询所述网络内是否存在备选的NF组件。
  8. 根据权利要求6所述的方法，其特征在于，所述第一NF组件接收所述NF仓库管理功能组件发送的第一消息，包括：
    所述第一NF组件通过所述第二NF组件接收所述NF仓库管理功能组件发送的第一消息；
    其中，所述第一消息在所述第二NF组件接收到所述NF仓库管理功能组件发送的NF发现响应消息后发送，所述NF发现响应消息包含所述第三NF组件的标识。
  9. 根据权利要求6-8任一项所述的方法，其特征在于，所述第一NF组件中存储有所述第二NF组件的上下文，所述第二NF组件的上下文包含：所述第二NF组件的标识、与所述第二NF组件通信的至少一个用户设备的标识；
    所述信令包含所述用户设备的标识，所述第一NF组件根据所述第三NF组件的标识，向所述第三NF组件发送所述信令，包括：
    所述第一NF组件根据根据第三NF组件的标识，建立所述第三NF组件的上下文；
    根据所述用户设备的标识、查询所述第三NF组件的上下文，向所述第三NF组件发送所述信令。
  10. 一种网络功能NF组件异常的处理方法，所述方法应用于包 含用户设备、第一NF组件、以及第二NF组件的网络，所述用户设备通过第一NF组件与所述第二NF组件进行通信，其特征在于，所述网络还包括：NF仓库管理功能组件，所述方法包括：
    所述第二NF组件向所述NF仓库管理功能组件发送NF发现请求消息；所述NF发现请求消息用于请求所述NF仓库管理功能组件查询所述网络内存在是否存在备选的NF组件；
    所述第二NF组件接收所述NF仓库管理功能组件发送的NF发现响应消息；所述NF发现响应消息包含所述第三NF组件的标识；
    所述第二NF组件向所述第一NF组件发送第一消息，第一消息包含：所述第三NF组件的标识；所述第一消息用于通知所述第一NF组件将接收到的所述用户设备发送的信令发往所述第三NF组件。
  11. 根据权利要求10所述的方法，其特征在于，在所述第二NF组件向所述NF仓库管理功能组件发送NF发现请求消息之前，所述方法还包括：
    所述第二NF组件检测到自身过载。
  12. 一种网络功能NF仓库管理功能组件，其特征在于，所述NF仓库管理功能组件包括：
    接收单元，用于接收NF发现请求消息，所述NF发现请求消息用于请求所述NF仓库管理功能组件查询所述第二NF组件所在网络内是否存在备选的NF组件；
    确定单元，用于确定所述NF仓库管理功能组件所在网络内存在备选的第三NF组件；
    发送单元，用于向第一NF组件发送第一消息，所述第一消息包含所述第三NF组件的标识，所述第一消息用于通知所述第一NF组件将接收到的用户设备发送的信令发往所述第三NF组件。
  13. 根据权利要求12所述的NF仓库管理功能组件，其特征在于，所述接收单元，还用于：
    在所述接收单元接收NF发现请求消息之前，所述NF仓库管理功能组件接收NF注册请求消息，所述NF注册请求消息包含所述网络中每个NF组件的标识、每个NF组件所对应的NF类型、每个所述NF组件所属的群组标识；
    所述NF仓库管理功能组件，还包括：
    生成单元，用于根据所述NF注册请求消息，生成至少一个NF组件群组，每个NF组件群组包含NF组件、以及NF组件的标识，同一NF组件群组包含的NF组件的类型和群组标识相同；
    所述发送单元，还用于向每个NF组件发送NF注册响应消息。
  14. 根据权利要求12或13所述的NF仓库管理功能组件，其特征在于，所述NF发现请求消息包含所述第二NF组件所属的群组标识，所述确定单元，具体用于：
    查询所述至少一个NF组件群组；
    若所述至少一个NF组件群组存在第一NF组件群组，所述第一NF组件群组与所述第二NF组件所属的群组标识相同，且所述第一NF组件群组包含除所述第二NF组件之外的其他NF组件，则将其他NF组件中的任一NF组件确定为备选的第三NF组件。
  15. 根据权利要求12-14任一项所述的NF仓库管理功能组件，其特征在于，所述接收单元，具体用于：
    接收所述第二NF组件发送的NF发现请求消息；
    所述发送单元，具体用于：经所述第二NF组件向所述第一NF组件发送NF发现响应消息，所述NF发现响应消息包含所述第三NF组件的标识。
  16. 根据权利要求12-14任一项所述的NF仓库管理功能组件，其特征在于，所述接收单元，具体用于：
    接收所述第一NF组件发送的NF发现请求消息。
  17. 一种第一网络功能NF组件，其特征在于，所述第一NF组 件包括：
    接收单元，用于接收NF仓库管理功能组件发送的第一消息，所述第一消息包含第三NF组件的标识，所述第三NF组件与第二NF组件属于同一NF组件群组，同一NF组件群组中的NF组件的功能相同，所述第二NF组件用于接收用户设备发送的信令；
    所述接收单元，还用于接收用户设备发送的信令；
    发送单元，用于根据所述第三NF组件的标识，向所述第三NF组件发送所述信令。
  18. 根据权利要求17所述的第一NF组件，其特征在于，所述第一NF组件，还包括：
    检测单元，检测到所述第二NF组件宕机；
    所述发送单元，还用于在所述接收单元接收所述NF仓库管理功能组件发送的第一消息之前，向所述NF仓库管理功能组件发送NF发现请求消息；所述NF发现请求消息用于请求所述NF仓库管理功能组件查询所述网络内是否存在备选的NF组件。
  19. 根据权利要求17所述的第一NF组件，其特征在于，所述接收单元，具体用于：
    通过所述第二NF组件接收所述NF仓库管理功能组件发送的第一消息；
    其中，所述第一消息在所述第二NF组件接收到所述NF仓库管理功能组件发送的NF发现响应消息后发送，所述NF发现响应消息包含所述第三NF组件的标识。
  20. 根据权利要求17-19任一项所述的第一NF组件，其特征在于，所述第一NF组件中存储有所述第二NF组件的上下文，所述第二NF组件的上下文包含：所述第二NF组件的标识、与所述第二NF组件通信的至少一个用户设备的标识；所述信令包含所述用户设备的标识；
    所述第一NF组件还包括；
    建立单元，用于根据第三NF组件的标识，建立所述第三NF组件的上下文；
    所述发送单元，具体用于：
    根据所述用户设备的标识、查询所述第三NF组件的上下文，向所述第三NF组件发送所述信令。
  21. 一种第二网络功能NF组件，其特征在于，所述第二NF组件包括：
    发送单元，用于向NF仓库管理功能组件发送NF发现请求消息；所述NF发现请求消息用于请求所述NF仓库管理功能组件查询所述第二NF组件所在网络内存在是否存在备选的NF组件；
    接收单元，用于接收所述NF仓库管理功能组件发送的NF发现响应消息；所述NF发现响应消息包含第三NF组件的标识；
    所述发送单元，还用于向第一NF组件发送第一消息，第一消息包含：所述第三NF组件的标识；所述第一消息用于通知所述第一NF组件将接收到的所述用户设备发送的信令发往所述第三NF组件。
  22. 根据权利要求21所述的第二NF组件，其特征在于，所述第二NF组件还包括：
    检测单元，用于在所述发送单元向所述NF仓库管理功能组件发送NF发现请求消息之前，检测到所述第二NF组件过载。
  23. 一种网络功能NF仓库管理功能组件，其特征在于，所述NF仓库管理功能组件包括：
    通信接口，用于接收NF发现请求消息，所述NF发现请求消息用于请求所述NF仓库管理功能组件查询所述第二NF组件所在网络内是否存在备选的NF组件；
    处理器，用于确定所述NF仓库管理功能组件所在网络内存在备选的第三NF组件；
    所述通信接口，还用于向第一NF组件发送第一消息，所述第一消息包含所述第三NF组件的标识，所述第一消息用于通知所述第一NF组件将接收到的用户设备发送的信令发往所述第三NF组件。
  24. 根据权利要求23所述的NF仓库管理功能组件，其特征在于，所述通信接口，还用于：
    在所述通信接口接收NF发现请求消息之前，所述NF仓库管理功能组件接收NF注册请求消息，所述NF注册请求消息包含所述网络中每个NF组件的标识、每个NF组件所对应的NF类型、每个所述NF组件所属的群组标识；
    所述处理器，还用于根据所述NF注册请求消息，生成至少一个NF组件群组，每个NF组件群组包含NF组件、以及NF组件的标识，同一NF组件群组包含的NF组件的类型和群组标识相同；
    所述通信接口，还用于向每个NF组件发送NF注册响应消息。
  25. 根据权利要求23或24所述的NF仓库管理功能组件，其特征在于，所述NF发现请求消息包含所述第二NF组件所属的群组标识，所述处理器，具体用于：
    查询所述至少一个NF组件群组；
    若所述至少一个NF组件群组存在第一NF组件群组，所述第一NF组件群组与所述第二NF组件所属的群组标识相同，且所述第一NF组件群组包含除所述第二NF组件之外的其他NF组件，则将其他NF组件中的任一NF组件确定为备选的第三NF组件。
  26. 根据权利要求23-25任一项所述的NF仓库管理功能组件，其特征在于，所述通信接口，具体用于：
    接收所述第二NF组件发送的NF发现请求消息；
    所述通信接口，具体用于：经所述第二NF组件向所述第一NF组件发送NF发现响应消息，所述NF发现响应消息包含所述第三NF组件的标识。
  27. 根据权利要求23-25任一项所述的NF仓库管理功能组件，其特征在于，所述通信接口，具体用于：
    接收所述第一NF组件发送的NF发现请求消息。
  28. 一种第一网络功能NF组件，其特征在于，所述第一NF组件包括：
    通信接口，用于接收NF仓库管理功能组件发送的第一消息，所述第一消息包含第三NF组件的标识，所述第三NF组件与第二NF组件属于同一NF组件群组，同一NF组件群组中的NF组件的功能相同，所述第二NF组件用于接收用户设备发送的信令；
    所述通信接口，还用于接收用户设备发送的信令；
    处理器，用于根据所述第三NF组件的标识，通过所述通信接口向所述第三NF组件发送所述信令。
  29. 根据权利要求28所述的第一NF组件，其特征在于，
    所述处理器，还用于检测到所述第二NF组件宕机；
    所述通信接口，还用于在所述通信接口接收所述NF仓库管理功能组件发送的第一消息之前，向所述NF仓库管理功能组件发送NF发现请求消息；所述NF发现请求消息用于请求所述NF仓库管理功能组件查询所述网络内是否存在备选的NF组件。
  30. 根据权利要求28所述的第一NF组件，其特征在于，所述通信接口，具体用于：
    通过所述第二NF组件接收所述NF仓库管理功能组件发送的第一消息；
    其中，所述第一消息在所述第二NF组件接收到所述NF仓库管理功能组件发送的NF发现响应消息后发送，所述NF发现响应消息包含所述第三NF组件的标识。
  31. 根据权利要求28-30任一项所述的第一NF组件，其特征在于，所述第一NF组件中存储有所述第二NF组件的上下文，所述第 二NF组件的上下文包含：所述第二NF组件的标识、与所述第二NF组件通信的至少一个用户设备的标识；所述信令包含所述用户设备的标识；
    所述处理器，还用于根据第三NF组件的标识，建立所述第三NF组件的上下文；
    所述通信接口，具体用于：根据所述用户设备的标识、查询所述第三NF组件的上下文，向所述第三NF组件发送所述信令。
  32. 一种第二网络功能NF组件，其特征在于，所述第二NF组件包括：
    通信接口，用于向NF仓库管理功能组件发送NF发现请求消息；所述NF发现请求消息用于请求所述NF仓库管理功能组件查询所述第二NF组件所在网络内存在是否存在备选的NF组件；
    通信接口，用于接收所述NF仓库管理功能组件发送的NF发现响应消息；所述NF发现响应消息包含第三NF组件的标识；
    所述通信接口，还用于向第一NF组件发送第一消息，第一消息包含：所述第三NF组件的标识；所述第一消息用于通知所述第一NF组件将接收到的所述用户设备发送的信令发往所述第三NF组件。
  33. 根据权利要求32所述的第二NF组件，其特征在于，所述第二NF组件还包括：
    处理器，用于在所述通信接口向所述NF仓库管理功能组件发送NF发现请求消息之前，检测到所述第二NF组件过载。
  34. 一种网络功能NF组件异常的处理***，其特征在于，包括：权利要求12-16任一项所述的NF仓库管理功能组件、权利要求17-20任一项所述的第一NF组件、以及权利要求21-22任一项所述的第二NF组件；
    或者权利要求23-27任一项所述的NF仓库管理功能组件、权利要求28-31任一项所述的第一NF组件、以及权利要求32-33任一项 所述的第二NF组件。
PCT/CN2016/106685 2016-11-21 2016-11-21 一种nf组件异常的处理方法、设备及*** WO2018090386A1 (zh)

Priority Applications (9)

Application Number Priority Date Filing Date Title
PCT/CN2016/106685 WO2018090386A1 (zh) 2016-11-21 2016-11-21 一种nf组件异常的处理方法、设备及***
PCT/CN2017/096262 WO2018090677A1 (zh) 2016-11-21 2017-08-07 一种nf组件异常的处理方法、设备及***
KR1020197018051A KR20190088060A (ko) 2016-11-21 2017-08-07 Nf 구성요소의 예외를 처리하기 위한 방법 및 시스템, 그리고 기기
JP2019527222A JP6900481B2 (ja) 2016-11-21 2017-08-07 Ｎｆコンポーネントの例外を処理するための方法およびシステム、ならびにデバイス
BR112019010207A BR112019010207A2 (pt) 2016-11-21 2017-08-07 método, dispositivo, armazenamento legível por computador, produto de programa de computador, e sistema para processar exceção de componente de nf, e dispositivo”
EP17872745.9A EP3544232B1 (en) 2016-11-21 2017-08-07 Processing method, device and system for nf component abnormality
KR1020217012526A KR102392120B1 (ko) 2016-11-21 2017-08-07 Nf 구성요소의 예외를 처리하기 위한 방법 및 시스템, 그리고 기기
CN201780072067.8A CN109983736B (zh) 2016-11-21 2017-08-07 一种nf组件异常的处理方法、设备及***
US16/418,029 US11178000B2 (en) 2016-11-21 2019-05-21 Method and system for processing NF component exception, and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/106685 WO2018090386A1 (zh) 2016-11-21 2016-11-21 一种nf组件异常的处理方法、设备及***

Publications (1)

Publication Number Publication Date
WO2018090386A1 true WO2018090386A1 (zh) 2018-05-24

Family

ID=62145171

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2016/106685 WO2018090386A1 (zh) 2016-11-21 2016-11-21 一种nf组件异常的处理方法、设备及***
PCT/CN2017/096262 WO2018090677A1 (zh) 2016-11-21 2017-08-07 一种nf组件异常的处理方法、设备及***

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/096262 WO2018090677A1 (zh) 2016-11-21 2017-08-07 一种nf组件异常的处理方法、设备及***

Country Status (7)

Country Link
US (1) US11178000B2 (zh)
EP (1) EP3544232B1 (zh)
JP (1) JP6900481B2 (zh)
KR (2) KR20190088060A (zh)
CN (1) CN109983736B (zh)
BR (1) BR112019010207A2 (zh)
WO (2) WO2018090386A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109996349A (zh) * 2019-04-02 2019-07-09 华为技术有限公司 一种会话恢复方法及其装置

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108401273B (zh) * 2017-02-06 2020-04-17 电信科学技术研究院 一种路由方法和装置
US10581984B2 (en) * 2018-07-23 2020-03-03 Cisco Technology, Inc. Methods and apparatus for providing information associated with network function (NF) instances of a 5G mobile network
EP3949354B1 (en) * 2019-04-02 2023-09-13 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for service discovery
US20220353263A1 (en) * 2021-04-28 2022-11-03 Verizon Patent And Licensing Inc. Systems and methods for securing network function subscribe notification process
US11888946B2 (en) 2021-06-02 2024-01-30 Oracle International Corporation Methods, systems, and computer readable media for applying or overriding preferred locality criteria in processing network function (NF) discovery requests
US20220400158A1 (en) * 2021-06-10 2022-12-15 Red Hat, Inc. Message format indicator for resource-constrained devices
US11930083B2 (en) 2021-08-09 2024-03-12 Oracle International Corporation Methods, systems, and computer readable media for processing network function (NF) discovery requests at NF repository function (NRF) using prioritized lists of preferred locations
US11888957B2 (en) 2021-12-07 2024-01-30 Oracle International Corporation Methods, systems, and computer readable media for locality and serving scope set based network function (NF) profile prioritization and message routing

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1984076A (zh) * 2006-06-08 2007-06-20 华为技术有限公司 在虚拟专用网的链路故障时传送报文的方法及***
CN102387083A (zh) * 2011-11-28 2012-03-21 中国联合网络通信集团有限公司 网络访问控制方法和***
CN104284359A (zh) * 2014-06-17 2015-01-14 南京邮电大学 一种epc网络下跨地区容灾***及控制方法
CN105052205A (zh) * 2013-03-15 2015-11-11 思科技术公司 提供无服务中断的备份网络拓扑

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8767584B2 (en) * 2010-01-29 2014-07-01 Alcatel Lucent Method and apparatus for analyzing mobile services delivery
CN103269282A (zh) * 2013-04-25 2013-08-28 杭州华三通信技术有限公司 网络配置自动部署方法和装置
CN104579889B (zh) * 2013-10-16 2018-03-09 华为技术有限公司 一种用于调用网络功能的方法及装置
CN104579732B (zh) * 2013-10-21 2018-06-26 华为技术有限公司 虚拟化网络功能网元的管理方法、装置和***
US9806979B1 (en) * 2013-12-19 2017-10-31 Amdocs Software Systems Limited System, method, and computer program for optimizing a chain of virtual network functions in a network based on network function virtualization (NFV)
EP2955631B1 (en) * 2014-06-09 2019-05-01 Nokia Solutions and Networks Oy Controlling of virtualized network functions for usage in communication network
US9742690B2 (en) * 2014-08-20 2017-08-22 At&T Intellectual Property I, L.P. Load adaptation architecture framework for orchestrating and managing services in a cloud computing system
CN105490908A (zh) * 2014-09-16 2016-04-13 中兴通讯股份有限公司 目标资源占用情况的处理方法及装置
EP3202086B1 (en) * 2014-09-29 2021-03-17 Koninklijke KPN N.V. State replication of virtual network function instances
US9794352B2 (en) * 2014-11-04 2017-10-17 Telefonaktiebolaget Lm Ericsson (Publ) Network function virtualization service chaining
US9584377B2 (en) * 2014-11-21 2017-02-28 Oracle International Corporation Transparent orchestration and management of composite network functions
WO2016086214A1 (en) * 2014-11-28 2016-06-02 Huawei Technologies Co., Ltd Systems and methods for providing customized virtual wireless networks based on service oriented network auto-creation
US20160212048A1 (en) * 2015-01-15 2016-07-21 Hewlett Packard Enterprise Development Lp Openflow service chain data packet routing using tables
CN106161077B (zh) * 2015-04-24 2019-07-09 中兴通讯股份有限公司 接入汇聚装置和认证注册方法
US10506489B2 (en) * 2015-09-18 2019-12-10 Huawei Technologies Co., Ltd. System and methods for network slice reselection
CN107925681B (zh) * 2015-09-23 2021-07-30 谷歌有限责任公司 用于分布式软件定义网络分组核心***中的负载平衡的***和方法
US10129108B2 (en) * 2015-11-13 2018-11-13 Huawei Technologies Co., Ltd. System and methods for network management and orchestration for network slicing
US10142994B2 (en) * 2016-04-18 2018-11-27 Electronics And Telecommunications Research Institute Communication method and apparatus using network slicing
EP3542515B1 (en) * 2018-02-06 2023-12-27 Telefonaktiebolaget LM Ericsson (publ.) Method and apparatus for a network function
US10581984B2 (en) * 2018-07-23 2020-03-03 Cisco Technology, Inc. Methods and apparatus for providing information associated with network function (NF) instances of a 5G mobile network
US10848576B2 (en) * 2018-10-29 2020-11-24 Cisco Technology, Inc. Network function (NF) repository function (NRF) having an interface with a segment routing path computation entity (SR-PCE) for improved discovery and selection of NF instances

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1984076A (zh) * 2006-06-08 2007-06-20 华为技术有限公司 在虚拟专用网的链路故障时传送报文的方法及***
CN102387083A (zh) * 2011-11-28 2012-03-21 中国联合网络通信集团有限公司 网络访问控制方法和***
CN105052205A (zh) * 2013-03-15 2015-11-11 思科技术公司 提供无服务中断的备份网络拓扑
CN104284359A (zh) * 2014-06-17 2015-01-14 南京邮电大学 一种epc网络下跨地区容灾***及控制方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109996349A (zh) * 2019-04-02 2019-07-09 华为技术有限公司 一种会话恢复方法及其装置
CN109996349B (zh) * 2019-04-02 2021-03-23 华为技术有限公司 一种会话恢复方法及其装置

Also Published As

Publication number Publication date
BR112019010207A2 (pt) 2019-09-03
CN109983736B (zh) 2021-02-12
CN109983736A (zh) 2019-07-05
JP2019536369A (ja) 2019-12-12
JP6900481B2 (ja) 2021-07-07
EP3544232A1 (en) 2019-09-25
KR20210048610A (ko) 2021-05-03
KR102392120B1 (ko) 2022-04-27
EP3544232A4 (en) 2019-11-20
KR20190088060A (ko) 2019-07-25
US20190273650A1 (en) 2019-09-05
EP3544232B1 (en) 2023-10-11
WO2018090677A1 (zh) 2018-05-24
US11178000B2 (en) 2021-11-16

Similar Documents

Publication Publication Date Title
WO2018090386A1 (zh) 一种nf组件异常的处理方法、设备及***
US11882485B2 (en) Session management function entity selection method, apparatus, and system
AU2021277736B2 (en) Pdu type setting method, ue policy setting method, and related entity
CN110012437B (zh) 一种组播报文的发送方法、装置及***
EP3462691B1 (en) Method and system for determining network slice
CN112868206A (zh) 在使用基于服务的体系架构的电信网络核心中提供服务代理功能的方法、***和计算机可读介质
US10979285B2 (en) Service transmission method, device, and system
US20220060881A1 (en) Group management method, apparatus, and system
US10999881B2 (en) Session management method and device
US11251981B2 (en) Communication method and apparatus
US9807179B2 (en) Method for implementing session border controller pool, and session border controller
WO2018000202A1 (zh) 一种负载迁移方法、装置及***
WO2020057445A1 (zh) 一种通信***、方法及装置
WO2015123876A1 (zh) 通信数据处理方法、装置和***
CN110730487A (zh) 一种选择会话管理功能网元的方法、装置及***
US9710513B2 (en) Access management method, device and system
US11108734B2 (en) Error indication processing and system, and device
WO2023284366A1 (zh) Dbng-cp的备份方法及装置
JP7261759B2 (ja) 移動通信ネットワークにおけるプレーン間の死活監視方法、ｐｇｗ－ｃ及びプログラム
US11240639B2 (en) Information transmission method, network element selector, and controller
EP4243379A1 (en) Methods, systems, and computer readable media for discovering network function service producers in a hierarchical network
WO2020063251A1 (zh) 一种通信方法及相关设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16921908

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16921908

Country of ref document: EP

Kind code of ref document: A1