Method, device, equipment and storage medium for managing user front-end equipment
By receiving management information from the session management function network element, user front-end devices are managed based on IP addresses, and remote control and management are performed using the network management system. This solves the problems of low operation and maintenance efficiency and security risks of user front-end devices, achieving efficient operation and maintenance and reducing network security risks.
Patent Information
- Application Number
- CN202111565958.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-12-20
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2041-12-20
AI Technical Summary
User-side equipment is difficult to maintain efficiently and poses network service security risks; self-management leads to management difficulties for operators.
By receiving management information sent by the session management function network element, management is carried out based on the IP address of the user's front-end device. Remote control and management are carried out using the network management system, including automatic configuration, dynamic service provisioning, software firmware management, status and performance statistics monitoring and fault diagnosis, so as to realize unified management of user's front-end devices.
It improves the operation and maintenance efficiency of user front-end equipment, reduces network security risks, reduces operator management costs, and achieves end-to-end automated service activation and fault localization.
Smart Images

Figure CN114268938B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a method, apparatus, device and storage medium for managing user front-end equipment. Background Art
[0002] Customer Premise Equipment (CPE) is a mobile signal access device that receives mobile signals and forwards them as wireless WIFI signals. The customer premises equipment can convert high-speed 4G / 5G signals into WiFi signals, and can support a large number of mobile terminals accessing the Internet at the same time. Customer premises equipment can be widely used in rural areas, towns, hospitals, units, factories, communities, etc., and can provide wireless network access, save broadband costs and eliminate wiring links. Customer premises equipment includes but is not limited to wireless routers, firewalls, computers, optical modems, 4G to WiFi wireless routers, etc. At present, customer premises equipment is managed by users themselves, and it is difficult to achieve efficient operation and maintenance of customer premises equipment, and there are certain network business security risks. Summary of the invention
[0003] To solve the above technical problems, the embodiments of the present application provide a method for managing user front-end equipment, a device for managing user front-end equipment, an electronic device, and a computer-readable storage medium, which can improve the operation and maintenance efficiency of the user front-end equipment.
[0004] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by the practice of the present application.
[0005] According to one aspect of an embodiment of the present application, a method for managing a user front-end device is provided. The method for managing a user front-end device is applied to a network management system, including: receiving management information sent by a session management function network element, the management information including the IP address of the user front-end device to be managed, wherein the management information is sent by the session management function network element when the received PDU session establishment request includes an operator management identifier; and managing the user front-end device based on the IP address.
[0006] In an exemplary embodiment, the user front-end device is managed based on the management information, including: logging in to the user front-end device based on the IP address and obtaining the device information of the user front-end device; authenticating the user front-end device based on the device information; if the authentication is successful, the user front-end device is managed.
[0007] In an exemplary embodiment, the user front-end device is authenticated based on the device information, including: setting a management whitelist, in which the device information of multiple user front-end devices to be managed is pre-set; matching the device information with the management whitelist, and if the match is successful, determining that the authentication of the user front-end device is passed.
[0008] In an exemplary embodiment, after the user front-end device is managed based on the management information, it includes: receiving a service request sent by the user front-end device; in response to the service request, obtaining a first service configuration file corresponding to the service request; sending the first service configuration file to the user front-end device, so that the user front-end device executes the service corresponding to the service request based on the first service configuration file.
[0009] In an exemplary embodiment, the first service profile includes address information of a third-party device; sending the first service profile to a user premise device so that the user premise device executes a service corresponding to the service request based on the first service profile includes: sending the address information of the third-party device to the user premise device so that the user premise device obtains a second service profile from the third-party device based on the address information of the third-party device, and executes the service corresponding to the service request based on the second service profile.
[0010] In an exemplary embodiment, after sending the first service configuration file to the user premise equipment, the method further includes: receiving service execution information sent by the user premise equipment; and updating the service processing status according to the service processing status contained in the service execution information.
[0011] According to one aspect of an embodiment of the present application, a method for managing a user front-end device is provided, and the method is applied to an SMF network element, including: receiving a PDU session establishment request sent by the user front-end device; determining whether the PDU session establishment request includes an operator management identifier, the operator management identifier being used to indicate that the user front-end device is managed by the operator device; and if so, sending management information to the operator device, so that the operator device manages the user front-end device according to the management information.
[0012] According to one aspect of an embodiment of the present application, a management device for a user front-end device is provided, including: a first receiving module, used to receive a PDU session establishment request sent by the user front-end device; a judgment module, used to judge whether the PDU session establishment request includes an operator management identifier, the operator management identifier is used to indicate that the user front-end device is managed by the operator device; a sending module, used to send management information to the operator device when the PDU session establishment request includes the operator management identifier, so that the operator device manages the user front-end device according to the management information.
[0013] According to one aspect of an embodiment of the present application, an electronic device is provided, including a processor and a memory, wherein computer-readable instructions are stored in the memory, and when the computer-readable instructions are executed by the processor, the above-mentioned method for managing a user front-end device is implemented.
[0014] According to one aspect of an embodiment of the present application, a computer-readable storage medium is provided, on which computer-readable instructions are stored. When the computer-readable instructions are executed by a processor of a computer, the computer executes the method for managing a user front-end device as provided above.
[0015] According to one aspect of an embodiment of the present application, a computer program product or a computer program is provided, the computer program product or the computer program including computer instructions, the computer instructions being stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the user front-end device management method provided in the above-mentioned various optional embodiments.
[0016] In the technical solution provided in the embodiments of the present application, management information sent by a session management function network element is received, and the management information includes the IP address of the user front-end device to be managed, wherein the management information is sent by the session management function network element when the received PDU session establishment request includes the operator management identifier; the user front-end device is managed based on the IP address, and through the above method, the user front-end device is uniformly managed based on the operator management identifier included in the PDU session establishment request, so as to realize efficient operation and maintenance of the user front-end device and reduce the possibility of network security risks caused by users managing the user front-end device by themselves.
[0017] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] The drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work. In the drawings:
[0019] Figure 1 is a flow chart of a method for managing a user front-end device shown in an exemplary embodiment of the present application;
[0020] Figure 2 This is a network framework diagram of an exemplary embodiment of a method for managing a user front-end device provided in the present application;
[0021] Figure 3 is a message parameter diagram of a PDU session establishment request shown in an exemplary embodiment;
[0022] Figure 4 yes Figure 1 Step S102 in the illustrated embodiment is a flow chart of an exemplary embodiment;
[0023] Figure 5 yes Figure 4 Step S402 in the illustrated embodiment is a flow chart of an exemplary embodiment;
[0024] Figure 6 is Figure 1 A flowchart of an exemplary embodiment of a method for managing a user front-end device proposed on the basis of the illustrated embodiment;
[0025] Figure 7 is Figure 6 A flowchart of an exemplary method for managing user premise equipment proposed based on the illustrated embodiment;
[0026] Figure 8 It is a flowchart of managing the upgrade service of the user front-end equipment shown in an exemplary embodiment of the present application;
[0027] Fig. 9 is a flow chart of a method for managing a user front-end device shown in an exemplary embodiment of the present application;
[0028] Fig.10 It is a block diagram of a management device for a user front-end device shown in an exemplary embodiment of the present application;
[0029] Fig.11 It is a block diagram of a management device for a user front-end device shown in an exemplary embodiment of the present application;
[0030] Fig.12 A schematic diagram of the structure of a computer system suitable for implementing an electronic device of an embodiment of the present application is shown. DETAILED DESCRIPTION
[0031] Here, exemplary embodiments will be described in detail, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are only examples of devices and methods consistent with some aspects of the present application as detailed in the attached claims.
[0032] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.
[0033] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.
[0034] It should also be noted that the "multiple" mentioned in this application refers to two or more than two. "And / or" describes the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship.
[0035] It should be noted that the network elements involved in the embodiments of the present application may also be referred to as functions or functional entities, and this application does not limit this. For example, the access and mobility management function network element may also be referred to as the access and mobility management function or the access and mobility management function entity, and the session management function network element may be referred to as the session management function or the session management function entity, etc. The names of the various network elements are not limited in this application, and those skilled in the art may replace the names of the above network elements with other names and perform the same functions, which are all within the scope of protection of this application.
[0036] It can be understood that the network elements, functions or functional entities involved in this embodiment can be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (for example, a cloud platform), and this application does not impose any restrictions.
[0037] At present, in the fifth generation (5G) communication, user front-end equipment is generally managed by users themselves. For example, before using the user front-end equipment, users must complete a large amount of service data configuration work on the user front-end equipment to ensure that the user front-end equipment can correctly and stably provide network services, which puts very high demands on end users. It is not included in the scope of basic network management of operators, making it difficult to achieve end-to-end automated service activation, efficient operation and maintenance, and fault demarcation; and user self-configuration has certain network and service security risks.
[0038] In order to solve at least the above problems existing in the prior art, the embodiments of the present application respectively propose a method for managing a user front-end device, a management device for a user front-end device, an electronic device, and a computer-readable storage medium. These embodiments will be described in detail below.
[0039] The user premise equipment management method, user premise equipment management device, electronic device and computer-readable storage medium provided in this embodiment are applied to a network management system (Network Management System, NMS) constructed by an operator.
[0040] The network management system is an operation and maintenance center that is responsible for equipment fault diagnosis and operation and maintenance of the wireless access system, network operation and network management, and provides data and statistical systems for network management and planning. With the rapid development of telecommunications technology, the scale of the telecommunications market has been further expanded, and the equipment operated in the network has become more and more complex. A large number of newly introduced services will bring more and more workload, thereby increasing the network management and maintenance costs of operators. The network management system provides operators with a way to manage networks in different regions and different equipment suppliers. Network administrators can better manage and maintain the network by comprehensively monitoring the operating status of the network through the network management system. The network management system can improve the availability and reliability of the network, thereby improving the efficiency of network operation as a whole and reducing management costs. For example, the ACS (Auto Configuration Server) remote management system can be used to implement the user front-end device management method provided in this embodiment.
[0041] This embodiment utilizes a network management system and combines one or more network elements in a 5G network architecture to execute a method for managing user front-end devices. The 5G network architecture includes a network exposure function (NEF) network element, a network storage function (NRF) network element, a policy control function (PCF) network element, a unified data management (UDM) network element, an application function (AF) network element, an authentication server function (ASF) network element, an access and mobility management function (AMF) network element, a session management function (SMF) network element, an access network (AN) and a user plane function (UPF) network element.
[0042] See also Figure 1 , Figure 1 FIG. 1 is a flow chart of a method for managing a user front-end device shown in an exemplary embodiment of the present application. Figure 1 As shown, the method for managing a user front-end device provided in this embodiment includes steps S101 and S102, and a detailed description is as follows:
[0043] Step S101: receiving management information sent by a session management function network element.
[0044] In this embodiment, the management information includes the device identification, IP address (Internet Protocol Address) and other information of the user front-end device to be managed. The IP address refers to the Internet Protocol address, which is also translated as the Internet Protocol address. The IP address is a unified address format provided by the IP protocol. It assigns a logical address to each network and each host on the Internet to shield the difference in physical addresses.
[0045] In this embodiment, the management information is sent by the session management function network element when the received PDU session establishment request includes the operator management identifier.
[0046] Currently in the fifth generation of communications, service data will be carried in the form of sessions at the bottom layer. A session represents a data path between a terminal device and the network. Multiple sessions can be established between the terminal device and the network without exceeding the maximum concurrent sessions. A PDU session refers to the process of communication between a terminal (User Equipment, UE) and a data network (Data Network, DN). After a PDU session is established, a data transmission channel is established between the UE and the DN. The session management function network element is mainly responsible for creating, updating or deleting PDU sessions, and managing the session context of the session with the UPF.
[0047] For example, see Figure 2 , Figure 2 FIG. 1 is a network framework diagram of an exemplary embodiment of a method for managing a user front-end device provided in the present application. Figure 2 As shown, if the powered-on user front-end equipment CPE wants to join the 5G network architecture, it needs to send a PDU session establishment request to the AMF network element, and the AMF network element then sends the PDU session establishment request to the SMF network element. The SMF network element first decodes the PDU session establishment request and allocates an IP address to the CPE based on the decoded PDU session establishment request so that the CPE can connect to the operator network through this IP address. In addition, if it is recognized that the decoded PDU session establishment request includes the operator management identifier, indicating that the CPE is willing to be managed, the SMF network element sends the management information to the network management system NMS to notify the network management system NMS to manage the CPE, otherwise there is no need to send the management information.
[0048] For example, see Figure 3 , Figure 3 is a message parameter diagram of a PDU session establishment request shown in an exemplary embodiment, such as Figure 3As shown, when the user premises equipment sends a PDU session establishment request, it takes an unused bit in the 5G SM Capability IEI field of the PDU session establishment request message and defines it as the operator management identification bit, namely CD-Flag. The value in the operator management identification bit is used to identify whether the user premises equipment is managed; for example, if the CD-Flag value is 1, it indicates that the user premises equipment is a device managed by the operator network, and if the CD-Flag value is 0, it indicates that the user premises equipment is not managed by the operator network. Specifically, the 5GSM capability IEI field is used to indicate UE capabilities related to PDU session management. The 5GSM capability IEI field is a type 4 information element with a minimum length of 3 bytes and a maximum length of 15 bytes. Therefore, the length of the operator management identification in this embodiment needs to meet the condition of being greater than 3 bytes and less than 15 bytes. As shown in FIG. Figure 3 As shown, the 5GSM Capability IEI field of the PDU session request message also includes other parameters, such as TPMIC, ATSSS-ST, EPT-S1, MH6-PDU, RqoS and other parameters. Their meanings and placeholder sizes belong to the prior art and will not be described in detail here.
[0049] Step S102: Manage the user front-end device based on the IP address.
[0050] In this embodiment, the user front-end device is managed based on the IP address of the user front-end device. Exemplarily, the network management system establishes a communication connection with the user front-end device based on the IP address, so that there is a data transmission channel between the network management system and the user front-end device. In this embodiment, the network management system can perform a variety of management services on the user front-end device, which are not specifically limited here.
[0051] Exemplarily, the network management system remotely controls and manages the user front-end equipment. Currently, operators can remotely control and manage the user front-end equipment through the ACS remote management system on the network side. The ACS remote management system can remotely control and manage the user front-end equipment in the following ways: automatic configuration and dynamic service provision, software and firmware management, status performance statistics monitoring, and fault diagnosis. Automatic configuration and dynamic service provision means that the ACS remote management system can send configuration files to a specific user front-end equipment or to a group of user front-end equipment. Exemplarily, the user front-end equipment automatically requests the configuration information in the ACS remote management system after it is turned on, and the ACS remote management system can also actively send configuration files at any required time.
[0052] Software and firmware management means that the ACS remote management system can identify the version number of the user's front-end device, decide whether to remotely upgrade the software version of the user's front-end device, and remotely back up the user's front-end device configuration, supporting digital signatures to ensure the security of the upgrade.
[0053] Status performance statistics monitoring means that the ACS remote management system can monitor the status and performance statistics of user front-end devices and remotely read the device information, status parameters, etc. of user front-end devices. When the device status changes, the user front-end device will also actively initiate device status reporting to notify the ACS remote management system and the user front-end device to actively report the status change.
[0054] Fault diagnosis means that when a user front-end device fails, the ACS remote management system can check the connectivity, bandwidth, etc. between the user front-end device and the core network device through Ping (Packet Internet Groper) or other detection methods, and return the detection results to the ACS remote management system. Among them, ping is an Internet packet explorer, a program used to test the network connection volume. Ping is a service command working in the application layer of the TCP / IP network architecture. It mainly sends ICMP (Internet Control Message Protocol) Echo request messages to a specific destination host to test whether the destination station is reachable and understand its relevant status. In this way, the operator can perform remote operations through the ACS remote management system to simply locate the user front-end device failure reported by the user and make corresponding processing.
[0055] In this embodiment, the ACS remote management system can use the TR069 series of protocols to remotely control and manage the user front-end equipment, and some of them can also use other gateway protocols, such as the Simple Network Management Protocol (SNMP). TR069 is a management protocol on the TCP / IP layer, and its full name is "User Front-end Equipment Wide Area Network Management Protocol". The basic idea of the TR069 protocol is to use the Remote Procedure Call (RPC) method based on the Simple Object Access Protocol (SOAP) that is widely used in the new generation of Web services. Its session protocol uses the HTTP1.1 protocol, so TR069 can easily use the transport layer security technology used in the Web, such as the Secure Sockets Layer (SSL) / Transport Layer Security (TLS). The lower layers of the TR069 protocol stack make full use of the communication protocols widely used on the Internet, such as TCP, HTTP, SOAP and other protocols. Through these mature protocols, the basic communication channel can be easily established between the ACS remote management system and the user front-end equipment.
[0056] Exemplarily, when there is no message interaction between the user front-end device and the network management system, the connection between the user front-end device and the network management system is disconnected, which effectively reduces the burden on the network management system.
[0057] The method for managing user front-end devices provided in this embodiment receives management information sent by a session management function network element, where the management information includes the IP address of the user front-end device to be managed, wherein the management information is sent by the session management function network element when the received PDU session establishment request includes the operator management identifier; the user front-end devices are managed based on the IP address, and through the above method, the user front-end devices are uniformly managed based on the operator management identifier included in the PDU session establishment request, so as to realize efficient operation and maintenance of the user front-end devices and reduce the possibility of network security risks caused by users managing the user front-end devices by themselves.
[0058] See also Figure 4 , Figure 4 yes Figure 1 Step S102 in the illustrated embodiment is a flow chart of an exemplary embodiment, as shown in FIG. Figure 4 As shown, step S102 includes steps S401 to S403, which are described in detail as follows:
[0059] Step S401: Log in to the user's front-end device based on the IP address and obtain device information of the user's front-end device.
[0060] In this embodiment, after the network management system establishes a data transmission channel with the user front-end device through the IP address, it receives the user name and password of the user front-end device sent by the user front-end device, so that the network management system remotely logs in to the user front-end device based on the user name, password and IP address, and then obtains the device information of the user front-end device.
[0061] Exemplarily, the device information of the user front-end device includes information such as the manufacturer identification and device model of the user front-end device, which is not specifically limited here.
[0062] Step S402: Authenticate the user's front-end device based on the device information.
[0063] This embodiment authenticates the user premise equipment based on the equipment information, so as to prevent illegal user premise equipment from illegally accessing the network management system, thereby preventing leakage of network data in the network management system.
[0064] See also Figure 5 , Figure 5 yes Figure 4 Step S402 in the illustrated embodiment is a flow chart of an exemplary embodiment, as shown in FIG. Figure 5 As shown, step S402 includes steps S501 and S502, which are described in detail as follows:
[0065] Step S501: Set a management whitelist and save the management whitelist in the network management system.
[0066] In this embodiment, the management whitelist includes the device information of multiple user front-end devices to be managed. The user front-end devices that the network management system has the right to manage are stored in the management whitelist. For example, the network management system only manages the user front-end devices in a preset area. Then, the management whitelist can include all user front-end devices located in the preset area and the device information corresponding to each user front-end device. For example, in order to protect the rights and interests of VIP users, a management whitelist is set according to the contract information of the user front-end device, wherein, if the contract information of the user front-end device includes a preset management identifier, the device information corresponding to the user front-end device is stored in the management whitelist, and conversely, if the contract information of the user front-end device does not include the preset management identifier, the device information corresponding to the user front-end device is not stored in the management whitelist.
[0067] Step S502: Match the device information with the managed whitelist. If the match is successful, it is determined that the authentication of the user's front-end device is successful.
[0068] In this embodiment, if the device information of the user's front-end device exists in the managed whitelist, the match is successful. Exemplarily, the manufacturer identification and one or more information of the device model of the user's front-end device are compared with the managed whitelist. If the comparison determines that the relevant device information of the user's front-end device exists in the managed whitelist, the authentication is passed.
[0069] It can be understood that this embodiment can also save a preset management blacklist in the network management system. The management blacklist includes device information of multiple user front-end devices that the network management system is not allowed to manage. The device information is matched with the preset management blacklist. If the match is successful, the authentication fails.
[0070] Step S403: If the authentication is successful, the user's front-end device is managed.
[0071] This embodiment authenticates the user front-end device through a preset management whitelist to ensure the legitimacy of the user front-end device, prevent illegal user front-end devices from illegally accessing the network management system, and further prevent leakage of network data in the network management system.
[0072] See also Figure 6 , Figure 6 is Figure 1 The flowchart of an exemplary embodiment of a method for managing a user front-end device proposed based on the embodiment shown in the figure is executed after step S102. Figure 4 As shown, after step S102, steps S601 and S603 are included, which are described in detail as follows:
[0073] Step S601: receiving a service request sent by a user front-end device.
[0074] In this embodiment, the service request is transmitted through the data transmission channel between the user front-end device and the network management system. If the data transmission channel between the user front-end device and the network management system is disconnected so that the service request cannot be sent to the network management system, the user front-end device generates a PDU session request and sends it to the session management function network element, so that the session management function network element resends the IP address of the user front-end device to the network management system, and the gateway management system re-establishes the data transmission channel with the user front-end device according to the IP address.
[0075] Exemplarily, the service request includes a configuration file delivery request, a fault diagnosis request, a maintenance and software upgrade request, etc., which are not specifically limited here.
[0076] Step S602: In response to the service request, a first service configuration file corresponding to the service request is obtained.
[0077] In this embodiment, the network management system parses the service request and detects whether the first service configuration file is stored locally. If so, there is no need to obtain the first service configuration file from other channels. Otherwise, the first service configuration file is obtained from other devices.
[0078] Exemplarily, if the service request is a software upgrade request, the first service configuration file includes a configuration file related to the software upgrade; if the service request is a fault diagnosis request, the first service configuration file includes a fault heartbeat packet, etc.; if the service request is a request for data transmission with a third-party device, the first service configuration file includes address information of the third-party device, etc.
[0079] Step S603: Send the first service configuration file to the user premises equipment, so that the user premises equipment executes the service corresponding to the service request based on the first service configuration file.
[0080] Exemplarily, the first service profile includes address information of a third-party device. If the service request includes a second service profile, and the second service profile is stored in a third-party device different from the network management device, the address information of the third-party device is sent to the user front-end device, so that the user front-end device obtains the second service profile from the third-party device based on the address information of the third-party device, and executes the service corresponding to the service request based on the second service profile; or establishes a data transmission channel with the third-party device according to the address information of the third-party device, receives the second service profile sent by the third-party device, and sends the second service profile as the first service profile to the user front-end device to execute the service corresponding to the service request based on the second service profile.
[0081] See also Figure 7 , Figure 7 is Figure 6 A flowchart of an exemplary method for managing a user front-end device is proposed based on the embodiment shown in FIG. Figure 7 As shown, after step S603, steps S701 and S702 are included, which are described in detail as follows:
[0082] Step S701: receiving service execution status information sent by a user front-end device.
[0083] In this embodiment, the service execution status information is actually the execution status information that the user front-end device feeds back to the network management system after executing the service corresponding to the service request. For example, the service execution status information includes service identification information, service execution success information, service execution failure information, etc., which is not specifically limited here.
[0084] Step S702: Update the business processing status according to the business processing status contained in the business execution status information.
[0085] In this embodiment, the service processing status contained in the service execution information is saved, and when the service processing status contained in the received service execution information changes, the service processing status is updated to supervise, control and manage the service execution status of the user front-end device.
[0086] In a specific application scenario, see Figure 8 , Figure 8 FIG. 1 is a flowchart of managing the upgrade service of the user front-end device shown in an exemplary embodiment of the present application. Figure 8 As shown, the upgrade service for the user's front-end equipment includes steps S801-S803, which are explained in detail as follows:
[0087] Step S801: receiving an upgrade work order and obtaining upgrade instruction information from a third-party server.
[0088] In this embodiment, the upgrade indication information may be that the third-party server sends the upgrade indication information to the network management system after the software is upgraded; or, the network management system sends an inquiry request message to the third-party server at a preset time or period, and the third-party server returns the upgrade indication information in response to the request message to the network management system after the software is upgraded.
[0089] Exemplarily, an upgrade work order is received from a support system, which may be a business support system (BSS) and an operation support system (OSS). The upgrade work order may include the device ID of the user front-end device to be upgraded, the address information of the third-party server, an operation code indicating a business status upgrade, and the version number of the software to be upgraded. Exemplarily, the support system may be configured to issue upgrade work orders periodically or at a fixed time, or the third-party server may issue an instruction command to the support system at the same time after issuing the upgrade instruction information, instructing the support system to generate and issue the upgrade work order.
[0090] Step S802: after acquiring the upgrade instruction information, the upgrade information is sent to the user front-end device indicated by the upgrade work order, so that the user front-end device is upgraded according to the upgrade information.
[0091] Exemplarily, a batch upgrade plan is customized based on the upgrade work order and upgrade instruction information, and the batch upgrade plan specifies the upgrade of multiple preset software for multiple preset user front-end devices. The batch upgrade plan is sent to the user front-end devices, so that after the multiple user front-end devices receive the upgrade information, they respectively connect to the third-party server according to the address information of the third-party server, obtain the upgrade file from the third-party server, and perform batch upgrade services for the user front-end devices according to the upgrade file.
[0092] Exemplarily, the upgrade information may include the address information of the third-party server. At this time, the user front-end device connects to the third-party server according to the received address information of the third-party server, obtains the upgrade file from the third-party server, and performs the upgrade according to the upgrade file. The upgrade information may also include the version number of the software to be upgraded, etc.
[0093] Exemplarily, the network management system obtains the upgrade file from the third-party server, sends the upgrade file to the user front-end device, and enables the user front-end device to upgrade according to the upgrade file. Specifically, after obtaining the upgrade file from the third-party server, the network management system saves the upgrade file in a specific unit in the network management system, and sends the address information of the specific unit to the user front-end device through the upgrade information, and then the user front-end device obtains the upgrade file from the specific unit according to the address information of the specific unit. The upgrade file can be transmitted between the network management system and the user front-end device through a data transmission channel.
[0094] Step S803: receiving the upgrade execution status information sent by each user front-end device, and performing subsequent processing according to the upgrade execution status information.
[0095] Exemplarily, the subsequent processing includes: performing a separate upgrade operation again on the user front-end equipment that the upgrade execution status information indicates has not been successfully upgraded; or for the user front-end equipment that the upgrade execution status information indicates has been successfully upgraded or the user front-end equipment that succeeded after a separate upgrade, saving or updating the upgraded service status information in the network management system, such as updating the version number corresponding to each user front-end equipment, historical upgrade records, etc.; for the user front-end equipment that still fails after a separate upgrade, performing alarm processing or fault detection processing.
[0096] For example, the network management system fills the URL address of the third-party server in the "URL" field of the sent configuration file, indicates the login authority in the "Username" field and the "Password" field; and indicates the version number of the software to be upgraded in the "FileSize" field and the "TargetFileName" field. When the user front-end device sends the upgrade execution status information to the network management system, the "Status" field is used to indicate the upgrade result information.
[0097] This embodiment controls the user front-end equipment to upgrade and receives the upgrade execution information of the user front-end equipment through the network management system, performs subsequent processing according to the upgrade results, realizes the unified management of the operator's user front-end equipment, and also enables the operator to obtain relevant information during the user front-end equipment upgrade process. In addition, the network management system performs subsequent processing on the results of the upgrade process, which can ensure the effect of the user front-end equipment upgrade and prevent the failure to maintain the latest service status from affecting the normal performance of service functions and affecting the user's service experience.
[0098] participate Fig. 9 , Fig. 9 1 is a flowchart of a method for managing a user front-end device shown in an exemplary embodiment of the present application. The method for managing a non-user front-end device provided in this embodiment is applicable to SMF network elements, such as Fig. 9 As shown, the method for managing a user front-end device includes steps S901 to S903, which are described in detail as follows:
[0099] Step S901: receiving a PDU session establishment request sent by a user front-end device.
[0100] The flowchart of the method for managing a user front-end device provided in this embodiment is applicable to a session management function network element.
[0101] In this embodiment, the establishment of the PDU session establishment request refers to step S100, which will not be described in detail here.
[0102] Step S902: Determine whether the PDU session establishment request includes an operator management identifier, where the operator management identifier is used to indicate that the user front-end device is managed by the operator device.
[0103] In this embodiment, the received PDU session establishment request is first decoded, and then an IP address is allocated to the user premise equipment, and the IP address is sent to the user premise equipment.
[0104] In this embodiment, it is identified whether the decoded PDU session establishment request includes an operator management identifier. If so, it indicates that the user premise equipment is willing to be managed. Otherwise, it indicates that the user premise equipment is a self-managed device.
[0105] Step S903: If yes, sending management information to the operator device, so that the operator device manages the user front-end device according to the management information.
[0106] In this embodiment, the management information includes information such as the IP address and device ID of the user premise equipment, so that the operator equipment manages the user premise equipment according to the management information.
[0107] The user front-end equipment management method provided in this embodiment uniformly manages the user front-end equipment based on the operator management identifier included in the PDU session establishment request, thereby achieving efficient operation and maintenance of the user front-end equipment and reducing the possibility of network security risks caused by users managing the user front-end equipment by themselves.
[0108] participate Fig.10 , Fig.10 is a block diagram of a management device for a user front-end device shown in an exemplary embodiment of the present application, such as Fig.10 As shown, the management device 10 of the user front-end equipment includes a first receiving module 11, a judging module 12 and a sending module 13.
[0109] Among them, the first receiving module 11 is used to receive a PDU session establishment request sent by a user front-end device; the judgment module 12 is used to judge whether the PDU session establishment request includes an operator management identifier, and the operator management identifier is used to indicate that the user front-end device is managed by the operator device; the sending module 13 is used to send management information to the operator device when the PDU session establishment request includes an operator management identifier, so that the operator device manages the user front-end device according to the management information.
[0110] participate Fig.11 , Fig.11 is a block diagram of a management device for a user front-end device shown in an exemplary embodiment of the present application, such as Fig.11 As shown, the management device 20 of the user front-end equipment includes a second receiving module 21 and a management module 22.
[0111] Among them, the second receiving module 21 is used to receive the management information sent by the session management function network element, and the management information includes the IP address of the user front-end device to be managed, wherein the management information is sent by the session management function network element when the received PDU session establishment request includes the operator management identifier; the management module 22 is used to manage the user front-end device based on the IP address.
[0112] In another exemplary embodiment, the management module 22 includes a login unit, an authentication unit and a management unit, wherein the login unit is used to log in to the user front-end device based on the IP address and obtain the device information of the user front-end device; the authentication unit is used to authenticate the user front-end device based on the device information; and the management unit is used to manage the user front-end device when the authentication is successful.
[0113] In another exemplary embodiment, the authentication unit includes a setting subunit and a matching unit, wherein the setting subunit is used to set a management whitelist, in which the device information of multiple user front-end devices to be managed is pre-set; the matching subunit is used to match the device information with the management whitelist, and if the match is successful, the authentication is passed.
[0114] In another exemplary embodiment, the management module 22 includes a first receiving unit, a responding unit and a sending unit, wherein the receiving unit is used to receive a service request sent by a user front-end device; the responding unit is used to respond to the service request and obtain a first service profile corresponding to the service request; the sending unit is used to send the first service profile to the user front-end device, so that the user front-end device executes the service corresponding to the service request based on the first service profile.
[0115] In another exemplary embodiment, the management module 22 also includes a second receiving unit and an updating unit, wherein the second receiving unit is used to receive the service execution status information sent by the user front-end device; the updating unit is used to update the service processing status according to the service processing status contained in the service execution status information.
[0116] It should be noted that the device provided in the above embodiment and the method provided in the above embodiment belong to the same concept, wherein the specific manner in which each module and unit performs the operation has been described in detail in the method embodiment and will not be repeated here.
[0117] In another exemplary embodiment, the present application provides an electronic device, including a processor and a memory, wherein the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the method for managing a user front-end device as described above is implemented.
[0118] Fig.12 A schematic diagram of the structure of a computer system suitable for implementing an electronic device of an embodiment of the present application is shown.
[0119] It should be noted that Fig.12 The computer system 1000 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0120] like Fig.12 As shown, the computer system 1000 includes a central processing unit (CPU) 1001, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 1002 or the program loaded from the storage part 1008 to the random access memory (RAM) 1003, such as executing the information recommendation method in the above embodiment. In the RAM 1003, various programs and data required for system operation are also stored. The CPU 1001, the ROM 1002 and the RAM 1003 are connected to each other through the bus 1004. The input / output (I / O) interface 1005 is also connected to the bus 1004.
[0121] The following components are connected to the I / O interface 1005: an input section 1006 including a keyboard, a mouse, etc.; an output section 1007 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1008 including a hard disk, etc.; and a communication section 1009 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to the I / O interface 1005 as needed. A removable medium 1011, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1010 as needed so that a computer program read therefrom is installed into the storage section 1008 as needed.
[0122] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication section 1009, and / or installed from a removable medium 1011. When the computer program is executed by a central processing unit (CPU) 1001, various functions defined in the system of the present application are executed.
[0123] It should be noted that the computer-readable medium shown in the embodiment of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, a system, device or device of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by an instruction execution system, device or device or used in combination with it. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a computer-readable computer program is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.
[0124] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0125] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.
[0126] Another aspect of the present application provides a computer-readable storage medium having computer-readable instructions stored thereon, which, when executed by a processor, implements the method for managing a user front-end device as in any of the previous embodiments.
[0127] Another aspect of the present application also provides a computer program product or a computer program, which includes a computer instruction stored in a computer-readable storage medium. A processor of a computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the user front-end device management method provided in each of the above embodiments.
[0128] It should be noted that the computer-readable medium shown in the embodiment of the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it. In the present application, a computer-readable signal medium can include a data signal propagated in a baseband or as a part of a carrier wave, wherein a computer-readable computer program is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.
[0129] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0130] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.
[0131] The above content is only a preferred exemplary embodiment of the present application and is not intended to limit the implementation scheme of the present application. A person skilled in the art can easily make corresponding changes or modifications based on the main concept and spirit of the present application. Therefore, the scope of protection of the present application shall be based on the scope of protection required by the claims.
Claims
1. A method for managing user front-end equipment, the method being applied to a network management system, characterized in that: include: Receiving management information sent by a session management function network element, the management information including the IP address of the user front-end device to be managed, wherein the management information is sent by the session management function network element when the received PDU session establishment request includes the operator management identifier; Managing the user front-end device based on the IP address; After the user front-end device is managed based on the IP address, the method further includes: Receiving a service request sent by the user front-end device; In response to the service request, obtaining a first service configuration file corresponding to the service request; The first service configuration file is sent to the user premises equipment, so that the user premises equipment executes the service corresponding to the service request based on the first service configuration file.
2. The method according to claim 1, characterized in that The managing the user front-end device based on the management information includes: Logging in to the user front-end device based on the IP address and obtaining device information of the user front-end device; Authenticating the user front-end device based on the device information; If the authentication is successful, the user front-end device is managed.
3. The method according to claim 2, characterized in that The authenticating the user front-end device based on the device information includes: Setting a management whitelist, wherein the management whitelist is pre-set with device information of multiple user front-end devices to be managed; The device information is matched with the managed whitelist, and if the match is successful, it is determined that the authentication of the user's front-end device is passed.
4. The method according to claim 1, characterized in that: The first service configuration file includes address information of a third-party device; and sending the first service configuration file to the user premise equipment so that the user premise equipment performs a service corresponding to the service request based on the first service configuration file includes: The address information of the third-party device is sent to the user premise equipment, so that the user premise equipment obtains a second service configuration file from the third-party device based on the address information of the third-party device, and executes the service corresponding to the service request based on the second service configuration file.
5. The method according to claim 1, characterized in that After sending the first service configuration file to the user premise equipment, the method further includes: Receiving service execution information sent by the user front-end device; The business processing status is updated according to the business processing status contained in the business execution status information.
6. A method for managing user front-end equipment, the method being applied to SMF network elements, characterized in that: include: Receiving a PDU session establishment request sent by the user front-end device; Determine whether the PDU session establishment request includes an operator management identifier, where the operator management identifier is used to indicate that the user front-end device is managed by an operator device; If so, sending management information to the operator device so that the operator device manages the user front-end device according to the management information, receiving the service request sent by the user front-end device, and in response to the service request, obtaining a first service configuration file corresponding to the service request, and sending the first service configuration file to the user front-end device so that the user front-end device executes the service corresponding to the service request based on the first service configuration file.
7. A management device for user front-end equipment, characterized in that: include: A first receiving module, configured to receive a PDU session establishment request sent by the user front-end device; A judging module, used to judge whether the PDU session establishment request includes an operator management identifier, where the operator management identifier is used to indicate that the user front-end device is managed by an operator device; A sending module, configured to send management information to the operator device when the PDU session establishment request includes an operator management identifier, so that the operator device manages the user front-end device according to the management information; The device also includes a management module, which includes a first receiving unit, a response unit and a sending unit, wherein the first receiving unit is used to receive a service request sent by a user front-end device; the response unit is used to respond to the service request and obtain a first service configuration file corresponding to the service request; the sending unit is used to send the first service configuration file to the user front-end device, so that the user front-end device executes the service corresponding to the service request based on the first service configuration file.
8. An electronic device, characterized in that: include: a memory storing computer-readable instructions; A processor reads the computer-readable instructions stored in the memory to execute the method according to any one of claims 1 to 6.
9. A computer-readable storage medium, characterized in that: Computer-readable instructions are stored thereon, and when the computer-readable instructions are executed by a processor of a computer, the computer is caused to execute the method according to any one of claims 1 to 6.
