CN115835184A

CN115835184A - Management method and device of terminal equipment

Info

Publication number: CN115835184A
Application number: CN202111111095.0A
Authority: CN
Inventors: 曹龙雨; 王耀光; 于益俊
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-09-18
Filing date: 2021-09-18
Publication date: 2023-03-21
Also published as: WO2023040927A1

Abstract

The application provides a method and a device for managing terminal equipment, wherein the method comprises the following steps: the terminal equipment for providing wireless network access service sends equipment type information to a terminal equipment management entity, wherein the equipment type information is used for indicating the type of the terminal equipment; the terminal equipment management entity sends configuration parameters to the terminal equipment, the configuration parameters are determined according to the equipment type information, and the configuration parameters are used for the configuration of the terminal equipment; and the terminal equipment carries out configuration according to the configuration parameters. According to the method and the device for managing the terminal equipment, the terminal equipment management entity can send the configuration parameters to the terminal equipment according to the equipment type information reported by the terminal equipment, so that the terminal equipment providing the wireless network access service can execute parameter configuration, the terminal equipment management entity can manage the terminal equipment without depending on end-to-end network resources, the consumption of the network resources is reduced, and the network construction and maintenance cost is reduced.

Description

Management method and device of terminal equipment

Technical Field

The present application relates to the field of communications, and in particular, to a method and an apparatus for managing a terminal device.

Background

Currently, a terminal equipment management entity (UE mgt) is used for managing terminal equipment such as customer-premise equipment (CPE) and Road Side Unit (RSU) based on a management scheme of a data plane path provided by a third generation partnership project (3 gpp) network. The UE mgt depends on end-to-end (E2E) network resources for the management of the terminal device, and consumes large network resources, especially resources of a User Plane Function (UPF) of a core network, so that a large amount of network construction and maintenance costs are required. Therefore, how to reduce the consumption of network resources when managing the CPE/RSU and other terminal devices and reduce the cost of network construction and maintenance is an urgent problem to be solved.

Disclosure of Invention

The application provides a management method and a management device for terminal equipment, which can reduce consumption of network resources and reduce network construction and maintenance costs.

In a first aspect, a method for managing a terminal device is provided, including: a terminal device management entity receives device type information from a terminal device, wherein the device type information is used for indicating the type of the terminal device, and the terminal device is used for providing wireless network access service; and the terminal equipment management entity sends configuration parameters to the terminal equipment, wherein the configuration parameters are determined according to the equipment type information, and the configuration parameters are used for the configuration of the terminal equipment.

According to the scheme, the terminal equipment actively reports the equipment type information, and the terminal equipment management entity can send the configuration parameters to the terminal equipment according to the equipment type information, so that the terminal equipment providing the wireless network access service can execute parameter configuration, the terminal equipment management entity can manage the terminal equipment without depending on end-to-end network resources, the consumption of the network resources is reduced, and the network construction and maintenance cost is reduced.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: and the terminal equipment management entity determines configuration parameters according to the equipment type information.

With reference to the first aspect, in some implementations of the first aspect, the determining, by the terminal device management entity, the configuration parameter according to the device type information includes: the terminal equipment management entity determines a parameter type according to the equipment type information, wherein the parameter type is used for indicating the type of a configuration parameter required by the terminal equipment for providing the wireless network access service; and the terminal equipment management entity determines the configuration parameters according to the parameter types.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes:

the terminal equipment management entity receives protocol information from the terminal equipment, wherein the protocol information comprises one or more of the following items: the terminal equipment comprises protocol type information or version information, wherein the protocol type information is used for indicating the management protocol type supported by the terminal equipment, and the version information is used for indicating the version number of the management protocol type supported by the terminal equipment; wherein, the sending the configuration parameter to the terminal device by the terminal device management entity includes: and the terminal equipment management entity sends the configuration parameters to the terminal equipment according to the protocol information.

According to the scheme, the terminal equipment actively reports the equipment information and the protocol information, and the terminal equipment management entity can more quickly and accurately determine the type of the configuration parameters required by the terminal equipment for providing the wireless network access service.

With reference to the first aspect, in some implementations of the first aspect, the sending, by the terminal device management entity, the configuration parameter to the terminal device according to the protocol information includes: the terminal device management entity sends the configuration parameters to the terminal device according to target protocol information, wherein the target protocol information comprises one or more of the following items: target protocol type information or target version information; the protocol information comprises a plurality of protocol type information, and the target protocol type information of the target protocol information is one of the plurality of protocol type information; or, the protocol information includes a plurality of protocol version information, and the target protocol version information of the target protocol information is one of the plurality of protocol version information; or, the protocol information includes a plurality of protocol type information and a plurality of protocol version information, the target protocol type information of the target protocol information is one of the plurality of protocol type information, and the target protocol version information of the target protocol information is one of the plurality of protocol version information.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: the terminal device management entity sends the target protocol information to the terminal device.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: the device management entity receives priority information from the terminal device, the priority information being used for indicating the priority of the protocol information, the priority of the protocol information including one or more of the following items: the priority of the protocol type information or the priority of the version information; wherein, the sending, by the terminal device management entity, the configuration parameter to the terminal device according to the protocol information includes: and the terminal equipment management entity sends the configuration parameters to the terminal equipment according to the protocol information and the priority of the protocol information.

According to the scheme, the terminal equipment actively reports the equipment information, the protocol information and the protocol optimization strategy, and the terminal equipment management entity can more quickly and accurately determine the type of the configuration parameters required by the terminal equipment for providing the wireless network access service according to the information reported by the terminal equipment.

With reference to the first aspect, in some implementations of the first aspect, the sending, by the terminal device management entity, the configuration parameter to the terminal device according to the protocol information includes: and the terminal equipment management entity sends the configuration parameters to the terminal equipment according to the protocol information and the strategy.

With reference to the first aspect, in some implementation manners of the first aspect, the configuration parameter includes a wireless network service set identifier SSID of a wireless network access service provided by the terminal device, a password corresponding to the SSID, an internet protocol IP address of a clock synchronization server, and the like, and the configuration parameter further includes other parameter types, which is not limited in this application.

In a second aspect, a method for managing a terminal device is provided, including: the terminal equipment sends equipment type information to a terminal equipment management entity, wherein the protocol type information is used for indicating a management protocol type supported by the terminal equipment, and the terminal equipment is used for providing wireless network access service; the terminal equipment receives configuration parameters from the terminal equipment management entity, wherein the configuration parameters are used for the configuration of the terminal equipment and are determined according to the equipment type information; and the terminal equipment carries out configuration according to the configuration parameters.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the terminal equipment sends protocol information to the terminal equipment management entity, wherein the protocol information comprises one or more of the following items: the terminal device comprises protocol type information or version information, wherein the protocol type information is used for indicating the management protocol types supported by the terminal device, and the version information is used for indicating the version number of the management protocol types supported by the terminal device.

According to the scheme, the terminal equipment actively reports the equipment information and the protocol information, so that the terminal equipment management entity can determine the type of the configuration parameters required by the terminal equipment for providing the wireless network access service more quickly and accurately.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the terminal equipment receives target protocol information from the terminal equipment management entity, wherein the target protocol information comprises one or more of the following items: target protocol type information or target version information; the protocol information comprises a plurality of protocol type information, and the target protocol type information of the target protocol information is one of the plurality of protocol type information; or, the protocol information includes a plurality of protocol version information, and the target protocol version information of the target protocol information is one of the plurality of protocol version information; or, the protocol information includes multiple pieces of protocol type information and multiple pieces of protocol version information, the target protocol type information of the target protocol information is one of the multiple pieces of protocol type information, and the target protocol version information of the target protocol information is one of the multiple pieces of protocol version information.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the terminal device sends priority information to the terminal device management entity, wherein the priority information is used for indicating the priority of the protocol information, and the priority of the protocol information comprises one or more of the following items: a priority of protocol type information or a priority of version information.

According to the scheme, the terminal equipment actively reports the equipment information, the protocol information and the protocol optimization strategy, so that a subsequent terminal equipment management entity can combine the information reported by the terminal equipment to more quickly and accurately determine the type of the configuration parameters required by the type of the configuration parameters for providing the wireless network access service by the terminal equipment.

With reference to the second aspect, in some implementation manners of the second aspect, the configuration parameter includes a wireless network service set identifier SSID of a wireless network access service provided by the terminal device, a password corresponding to the SSID, an internet protocol IP address of a clock synchronization server, and the like, and the configuration parameter further includes other parameter types, which is not limited in this application.

In a third aspect, an apparatus for managing a terminal device is provided, including: the terminal equipment comprises a receiving and sending module, a processing module and a processing module, wherein the receiving and sending module is used for receiving equipment type information from the terminal equipment, the equipment type information is used for indicating the type of the terminal equipment, and the terminal equipment is used for providing wireless network access service; the transceiver module is further configured to send a configuration parameter to the terminal device, where the configuration parameter is determined according to the device type information, and the configuration parameter is used for configuring the terminal device.

With reference to the third aspect, in certain implementations of the third aspect, the apparatus further includes: and the processing module is used for determining the configuration parameters according to the equipment type information.

With reference to the third aspect, in certain implementations of the third aspect, the processing module is specifically configured to determine a parameter type according to the device type information, where the parameter type is used to indicate a type of a configuration parameter required by the terminal device to provide the wireless network access service; the processing module is specifically further configured to determine the configuration parameter according to the parameter type.

With reference to the third aspect, in certain implementations of the third aspect, the transceiver module is configured to receive protocol information from the terminal device, where the protocol information includes one or more of: the terminal equipment comprises protocol type information or version information, wherein the protocol type information is used for indicating the management protocol type supported by the terminal equipment, and the version information is used for indicating the version number of the management protocol type supported by the terminal equipment; the processing module is specifically configured to send the configuration parameter to the terminal device according to the protocol information.

With reference to the third aspect, in certain implementation manners of the third aspect, the processing module is specifically configured to send the configuration parameter to the terminal device according to target protocol information, where the target protocol information includes one or more of the following: target protocol type information or target version information; the protocol information comprises a plurality of protocol type information, and the target protocol type information of the target protocol information is one of the plurality of protocol type information; or, the protocol information includes a plurality of protocol version information, and the target protocol version information of the target protocol information is one of the plurality of protocol version information; or, the protocol information includes a plurality of protocol type information and a plurality of protocol version information, the target protocol type information of the target protocol information is one of the plurality of protocol type information, and the target protocol version information of the target protocol information is one of the plurality of protocol version information.

With reference to the third aspect, in some implementations of the third aspect, the transceiver module is further configured to send the target protocol information to the terminal device.

With reference to the third aspect, in certain implementations of the third aspect, the transceiver module is further configured to receive priority information from the terminal device, where the priority information is used to indicate a priority of the protocol information, and the priority of the protocol information includes one or more of: the priority of the protocol type information or the priority of the version information; the processing module is specifically configured to send the configuration parameter to the terminal device according to the protocol information and the priority of the protocol information.

With reference to the third aspect, in certain implementations of the third aspect, the processing module is further configured to send the configuration parameter to the terminal device according to the protocol information and the policy.

With reference to the third aspect, in some implementation manners of the third aspect, the configuration parameter includes a wireless network service set identifier SSID of a wireless network access service provided by the terminal device, a password corresponding to the SSID, an internet protocol IP address of a clock synchronization server, and the like, and the configuration parameter further includes other parameter types, which is not limited in this application.

In a fourth aspect, a management apparatus for a terminal device is provided, including: a transceiver module, configured to send device type information to a terminal device management entity, where the protocol type information is used to indicate a management protocol type supported by the terminal device, and the terminal device is used to provide a wireless network access service; the transceiver module is configured to receive a configuration parameter from the terminal device management entity, where the configuration parameter is used for configuring the terminal device, and the configuration parameter is determined according to the device type information; and the processing module is used for configuring according to the configuration parameters.

With reference to the fourth aspect, in some implementations of the fourth aspect, the transceiver module is configured to send protocol information to the terminal device management entity, where the protocol information includes one or more of the following: the terminal device comprises protocol type information or version information, wherein the protocol type information is used for indicating the management protocol types supported by the terminal device, and the version information is used for indicating the version number of the management protocol types supported by the terminal device.

With reference to the fourth aspect, in some implementations of the fourth aspect, the transceiver module is configured to receive target protocol information from the terminal device management entity, where the target protocol information includes one or more of the following: target protocol type information or target version information; the protocol information comprises a plurality of protocol type information, and the target protocol type information of the target protocol information is one of the plurality of protocol type information; or, the protocol information includes a plurality of protocol version information, and the target protocol version information of the target protocol information is one of the plurality of protocol version information; or, the protocol information includes a plurality of protocol type information and a plurality of protocol version information, the target protocol type information of the target protocol information is one of the plurality of protocol type information, and the target protocol version information of the target protocol information is one of the plurality of protocol version information.

With reference to the fourth aspect, in some implementations of the fourth aspect, the transceiver module is further configured to send priority information to the terminal device management entity, where the priority information is used to indicate a priority of the protocol information, and the priority of the protocol information includes one or more of: a priority of protocol type information or a priority of version information.

With reference to the fourth aspect, in some implementation manners of the fourth aspect, the configuration parameter includes a wireless network service set identifier SSID of a wireless network access service provided by the terminal device, a password corresponding to the SSID, an internet protocol IP address of a clock synchronization server, and the like, and the configuration parameter further includes other parameter types, which is not limited in this application.

In a fifth aspect, a communication apparatus is provided, including: a processor and a memory; the memory for storing a computer program; the processor is configured to execute the computer program stored in the memory to cause the communication apparatus to perform the communication method according to the first aspect or the second aspect.

A sixth aspect provides a computer-readable storage medium having stored thereon a computer program which, when run on a computer, causes the computer to perform the communication method of the first or second aspect.

In a seventh aspect, a chip system is provided, including: a processor for calling and running the computer program from the memory so that the communication device in which the system-on-chip is installed performs the communication method according to the first aspect or the second aspect.

In an eighth aspect, a management system of a terminal device is provided, including a terminal device and a terminal device management entity, where the terminal device management entity is configured to perform the method according to any one of the first aspect and possible implementations of the first aspect, and the terminal device is configured to perform the method according to any one of the second aspect and possible implementations of the second aspect.

A ninth aspect provides a management system for a terminal device, comprising a terminal device management entity and a radio access network device, the terminal device management entity being configured to perform the method according to the first aspect and any one of the possible implementations of the first aspect; the wireless access network equipment is used for receiving the equipment type information from the terminal equipment and forwarding the equipment type information to the terminal equipment management entity; and the terminal equipment management entity is also used for receiving the configuration parameters from the terminal equipment management entity and forwarding the configuration parameters to the terminal equipment.

Drawings

Fig. 1 shows a network architecture diagram of a 2B or V2X scenario.

Fig. 2 shows a schematic diagram of a management architecture of a CPE or RSU or other end device.

Fig. 3 is a schematic diagram illustrating an example of a converged framework for communication management of a wireless operation and maintenance terminal.

Fig. 4 is a schematic diagram illustrating another example of a converged framework for communication management of a wireless operation and maintenance terminal.

Fig. 5 shows a schematic interaction diagram of a management method 100 of a terminal device according to an embodiment of the present application.

Fig. 6 shows a schematic interaction diagram of a management method 200 of a terminal device according to an embodiment of the present application.

Fig. 7 shows a schematic interaction diagram of a management method 300 of a terminal device according to an embodiment of the present application.

Fig. 8 shows a schematic interaction diagram of a management method 400 of a terminal device according to an embodiment of the present application.

Fig. 9 is a schematic block diagram of a communication apparatus for management of a terminal device according to an embodiment of the present application.

Fig. 10 is a schematic diagram of an apparatus 20 for managing a terminal device according to an embodiment of the present application.

Detailed Description

The technical solution in the present application will be described below with reference to the accompanying drawings.

The technical scheme provided by the embodiment of the application can be applied to various communication systems, such as: a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD) system, a Universal Mobile Telecommunications System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication system, a fifth generation (5 g) system, a New Radio (NR) system, or a future 3GPP system, etc.

Generally, the conventional communication system supports a limited number of connections and is easy to implement, however, with the development of communication technology, the mobile communication system will support not only conventional communication but also, for example, device to device (D2D) communication, machine to machine (M2M) communication, machine Type Communication (MTC), vehicle to anything (V2X) communication (also may be referred to as vehicle network communication), for example, vehicle to vehicle (V2V) communication (also may be referred to as vehicle to vehicle communication), vehicle to infrastructure (V2I) communication (also may be referred to as vehicle to infrastructure communication), vehicle to pedestrian to vehicle (V2P) communication (also may be referred to as vehicle to vehicle communication), and vehicle to network (N2N) communication.

The application scenarios of the 5G network are rich and diverse, such as a business (2B) oriented scenario oriented to vertical industry, a V2X (automated driving) oriented scenario oriented to automatic driving, and an Augmented Reality (AR)/Virtual Reality (VR) oriented scenario oriented to general users.

Currently, in 2B industry scenarios and V2X scenarios, a common terminal device (UE) (such as an AGV, a video camera, a vehicle, etc.) is basically connected to an NR base station of a 5G network through a customer-premise equipment (CPE) or a Road Side Unit (RSU), and the CPE/RSU is connected to the 5G network of an operator through an air interface, so the CPE or RSU terminal device is a key network device node for user service provisioning.

Fig. 1 shows a network architecture diagram of a 2B or V2X scenario. In the architecture of fig. 1, the CPE or RSU is a terminal device providing a wireless network access function for other common terminals, and the NR is a wireless access network base station (e.g., gNB) of a 5G network. An Element Management System (EMS) is used to manage radio access network devices, including parameter configuration, performance management, fault alarm, etc. of network elements. A 5GC control plane network element (CNF) refers to all control plane network elements (including AMF, SMF, NEF, NWDAF, and the like) of a 5G core network, and a User Plane Function (UPF) is a user plane network element of the 5G core network. The UE mgt (UE management system) is a management system of a CPE or RSU terminal device, and its functions include registration, parameter configuration, software upgrade, fault diagnosis, status and performance monitoring, and other functions for the CPE or RSU terminal device.

Fig. 2 shows a schematic diagram of a management architecture of a CPE or RSU or other end device. As shown in fig. 2, currently, a terminal management system (UE mgt) is deployed separately, which can implement management of CPE or RSU terminal devices based on a 3GPP network data plane path (i.e., UE-gNB-UPF-UE mgt). Specifically, after the CPE or RSU terminal completes the attachment to the 5G network, the 5G network establishes a PDU session dedicated to terminal device management data transmission for the CPE or RSU terminal, where the PDU session is a PDU session different from normal service data transmission of the terminal device, and the two PDU sessions respectively correspond to different Access Point Name (APN) or Data Network Name (DNN) identifiers. In fig. 2, a path through which a solid line with an arrow passes is used for PDU session for management data (UE mgt data) transmission of the CPE or RSU terminal device, and a path through which a dotted line with an arrow passes is used for PDU session for normal traffic data (user data) transmission of the CPE or RSU terminal device.

At present, the CPE or RSU terminal devices of each manufacturer are managed by the CPE or RSU terminal management system provided by each manufacturer. CPE or RSU termination capabilities (e.g., supported protocol types, versions) are coordinated with the management capabilities of the CPE or RSU termination management system.

At present, management of CPE and RSU devices and management of network elements are two independent management systems, as shown in fig. 2, a UE mgt is used for managing CPE or RSU terminal devices, an EMS is used for managing network elements (e.g., gNB), and a terminal device management entity UE mgt is based on a management scheme of a data plane path provided by a 3GPP network, depends on network resources of an End-to-End E2E (End to End), consumes a large amount of network resources, and particularly needs to consume resources of a core network UPF. Fig. 3 is a schematic diagram illustrating an example of a converged framework for communication management of a wireless operation and maintenance terminal. Under the fusion architecture, the UE mgt can reuse the EMS to manage the wireless network element so as to realize the management of CPE or RSU terminal equipment, thereby saving 5G network resources, especially the resources of a 5G core network.

Further, since the radio access network element gNB may further perform function splitting, that is, the gNB may be split into a centralized unit-control plane (CU-CP), a centralized unit-user plane (CU-UP), and a Distributed Unit (DU), the CPE/RSU management and radio network element convergence architecture may also be the architecture shown in fig. 4.

Fig. 4 is a schematic diagram illustrating another example of a converged framework for communication management of a wireless operation and maintenance terminal. The key nodes involved in the architecture are briefly introduced below.

(1) The UE: the UE mentioned in this application mainly refers to a terminal device capable of providing a wireless network access function by other common terminals, and mainly refers to a CPE or an RSU in this document.

(2) The gNB is a radio access network base station of the 5G NR network, and mainly provides radio network access functions, including Radio Resource Control (RRC) connection management, security, user data forwarding, packet reassembly/fragmentation, retransmission, and other functions.

(3) The CU-CP mainly provides functions of radio connection management (i.e., RRC connection management), security, and the like.

(4) The CU-UP mainly provides functions of encrypting and decrypting user data packets, integrity protection and the like.

(5) The DU mainly provides functions of data packet reorganization/fragmentation, retransmission, channel management and the like

(6) The 5GC CNF refers to all control plane network elements of the 5G core network, including AMF, SMF, NEF, NWDAF, etc., and these different 5GC control plane network elements are respectively responsible for different network functions, for example, the AMF is mainly responsible for authentication and location tracking of the UE, and the SMF is mainly responsible for session management functions such as IP address allocation and QoS management. NEF mainly provides the ability to open 3GPP networks to external service entities. The NWDAF mainly provides a data analysis function of a 5G core network. Further network element types and functions encompassed by the 5GC CNF can be referred to the description in section 6.2 of the 3GPP standard protocol TS 23.501.

(7) The UPF is a user plane network element of a 5G core network and mainly provides functions of user plane data forwarding, charging statistics, qoS execution and the like.

(8) The EMS is a network element management function, and the EMS in fig. 3 of the present application refers to a network element management system of a wireless network, and is responsible for performing management of wireless access network devices, including parameter configuration, performance management, fault alarm, and the like of a wireless network element. The UE mgt is a terminal management function module added in the EMS for implementing the technical solution of the present application, and the main functions of the module are registration, parameter configuration, software upgrade, fault diagnosis, status and performance monitoring of the CPE or RSU and other terminal devices.

It should be noted that, the 5GC core network may also have at least one corresponding management system EMS for a core network element, but the technical solution of the present application does not relate to a network element management system for the core network, and therefore, a network element management system corresponding to the core network is not shown in the architectures of fig. 3 and 4, but the present application does not limit this.

(9) The NMS is a management system in an operator network for providing network device management across domains (such as across radio access networks and core networks) or across equipment providers, and its specific functions include parameter configuration, performance monitoring, fault alarm and other functions for network devices.

Under the architecture of the convergence of radio operation and terminal management in fig. 3 or fig. 4, the UE mgt is a unified terminal management function converged in the radio network element management system, and is not a terminal management system matched with a terminal device of a certain manufacturer, and manages all terminal devices within its coverage area based on the unified management interface of the radio network element management system and a corresponding radio network element, including terminal devices of different manufacturers (produced terminal devices) and different types of terminal devices. However, different manufacturers and different types of terminals have the following characteristics:

(1) Different types of corresponding parameters of different types of terminal equipment (such as CPE, RSU, AR module, etc.) are different, and the parameter types are used for indicating the types of configuration parameters required by the terminal equipment for providing wireless network access service;

(2) Terminal equipment of different manufacturers supports different protocol types of management protocols, such as protocols of TR-069, MQTT, LWM2M and the like;

(3) Different types or different manufacturers of terminal equipment support different versions of the same protocol type of management protocol, such as some V1 versions supporting TR-069protocol, some V3 versions supporting TR-069protocol, and the like.

For the above description, under a new architecture in which the wireless operation and maintenance and the terminal management are integrated, the integrated terminal management system manages the terminal devices of different types and different manufacturers in a unified manner, so a method for determining parameter configuration according to the terminal device information is required, but the scheme in which the CPE/RSU and the UE mgt are managed by the same manufacturer in a matching manner before the wireless operation and terminal management are integrated cannot adapt to the change caused by the integrated management architecture, and cannot support correct parameter configuration processing on the terminal devices. In the converged architecture, how the UE mgt configures parameters of terminal devices of different manufacturers or types through a unified management interface becomes an urgent problem to be solved.

The following describes the management method 100 of the terminal device according to the embodiment of the present application in detail with reference to fig. 5. Fig. 5 is a schematic interaction diagram of the method 100 of the present application.

S101, the terminal device sends the device type information of the terminal device to a terminal device management entity, and correspondingly, the terminal device management entity receives the device type information from the terminal device, wherein the device type information is used for indicating the type of the terminal device.

It should be understood that the end device herein is an end device that can provide wireless network access service for other end devices, and the type of the end device herein may include CPE-type, RSU-type, or AR module-type, etc., which respectively indicate that the end device is a CPE, RSU, or AR module.

S102, the terminal equipment management entity sends configuration parameters to the terminal equipment, and correspondingly, the terminal equipment receives the configuration parameters from the terminal equipment management entity, wherein the configuration parameters are used for the configuration of the terminal equipment.

It should be understood that the configuration parameters include a wireless network Service Set Identifier (SSID) of a wireless network access service provided by the terminal device, a password corresponding to the SSID, an IP address of a clock synchronization server, and other parameter types, which are not limited in this application.

S103, the terminal equipment carries out configuration according to the configuration parameters.

According to the scheme, the terminal equipment actively reports the equipment type information, and the terminal equipment management entity can send the configuration parameters to the terminal equipment according to the equipment type information, so that the terminal equipment providing the wireless network access service can execute parameter configuration. The terminal equipment management entity and the wireless network element management system are fused to obtain a fusion management system, and the fusion management system is used for managing the terminal equipment providing the wireless network access service, so that the terminal equipment does not depend on end-to-end network resources, the consumption of the network resources is reduced, and the network construction and maintenance cost is reduced.

Optionally, before S102, the terminal device may determine the configuration parameters according to the device type information.

Illustratively, the terminal device management entity determines a parameter type according to the device type information, where the parameter type is used to indicate a type of a configuration parameter required by the terminal device for providing the wireless network access service, and the terminal device management entity determines the configuration parameter according to the parameter type.

Specifically, with respect to S102, the terminal device management entity may transmit the configuration parameters to the terminal device according to the protocol information received from the terminal device, or, further, the terminal device management entity may transmit the configuration parameters to the terminal device according to the protocol information received from the terminal device and the priority of the protocol information. The following respectively describes the protocol information, the priority of the protocol information, and how the terminal device management entity sends the configuration parameters.

The protocol information includes one or more of: the terminal equipment comprises protocol type information or version information, wherein the protocol type information is used for indicating the management protocol type supported by the terminal equipment, and the version information is used for indicating the version number of the management protocol type supported by the terminal equipment.

It should be understood that the management protocol types herein may include TR-069protocol, MQTT protocol, LWM2Mprotocol, or the like.

The priority information is used for indicating the priority of the protocol information, and the priority of the protocol information comprises one or more of the following items: the priority of the protocol type information or the priority of the version information; the method for sending the configuration parameters to the terminal equipment by the terminal equipment management entity according to the protocol information comprises the following steps: and the terminal equipment management entity sends the configuration parameters to the terminal equipment according to the protocol information and the priority of the protocol information.

The terminal device management entity sends the configuration parameters to the terminal device according to the protocol information received by the terminal device, and has a plurality of possible implementation modes. For example, (1) when the terminal device supports a management protocol, the protocol information sent by the terminal device is the protocol information of the management protocol, and the terminal device sends the configuration parameters to the terminal device by using the management information according to the protocol information of the management protocol, which may specifically refer to the first possible implementation manner in the method 200 and the first possible implementation manner in the method 400. Or, (2) when the terminal device supports multiple management protocols, the protocol sent by the terminal device is the protocol information of all types of management protocols supported by the terminal device, the terminal device management entity selects a target management protocol according to the protocol information to send configuration parameters to the terminal device, and sends the target protocol information to the terminal device, where the target protocol information is the protocol information corresponding to the target management protocol. Further, the terminal device management entity may also send the configuration parameters to the terminal device according to the protocol information and the local policy, where the policy may be configured locally by the terminal device management entity or received from the NMS, specifically refer to the first possible implementation manner in the second possible implementation manner in the method 200 and the second possible implementation manner in the method 400, or refer to the second possible implementation manner in the first possible implementation manner in the method 300 and the first possible implementation manner in the method 400.

The terminal device management entity sends the configuration parameters to the terminal device according to the protocol information received by the terminal device and the priority of the protocol information, and has a plurality of possible implementation modes. For example, when the terminal device supports multiple management protocols, the terminal device sends protocol information of the multiple management protocols and priority of the protocol information to the terminal device management entity, the terminal device management entity selects a target management protocol according to the protocol information and the priority of the protocol information to send configuration parameters to the terminal device, and sends target protocol information to the terminal device, where the target protocol information is protocol information corresponding to the target management protocol. Further, the terminal device management entity may also send the configuration parameter to the terminal device according to the protocol information, the priority of the protocol information, and the protocol capability supported by itself, which may specifically refer to a second possible implementation manner in the method 200 and a second possible implementation manner in the method 400, or may specifically refer to a third possible implementation manner in the method 300 and a first possible implementation manner in the method 400.

According to the scheme, the terminal equipment actively reports the equipment information, the protocol information and the protocol optimization strategy, so that the subsequent EMS can combine the information reported by the terminal equipment to more quickly and accurately determine the type of the configuration parameter required by the type of the configuration parameter for providing the wireless network access service by the terminal equipment.

It should be understood that the above target protocol information includes one or more of the following: target protocol type information or target version information; the protocol information comprises a plurality of protocol type information, and the target protocol type information of the target protocol information is one of the plurality of protocol type information; or the protocol information comprises a plurality of protocol version information, and the target protocol version information of the target protocol information is one of the plurality of protocol version information; or, the protocol information includes a plurality of protocol type information and a plurality of protocol version information, the target protocol type information of the target protocol information is one of the plurality of protocol type information, and the target protocol version information of the target protocol information is one of the plurality of protocol version information.

The following describes the management method 200 of the terminal device according to the embodiment of the present application in detail with reference to fig. 6. Fig. 6 is a schematic interaction diagram of a method 200 of the present application.

Fig. 6 illustrates a plug and play (PnP) or management channel establishment procedure of a terminal device, and several possible implementations of the method 200 are described below.

A first possible implementation:

under the scene that the terminal equipment only supports one management protocol, the terminal equipment establishes a flow in a PnP or management channel and sends equipment type information, protocol information and the like of the terminal equipment to an EMS (information management system).

S201-S203 are RRC connection establishment procedures. The RRC connection establishment may occur after the UE is powered on, the UE searches for a wireless signal of the wireless network base station, selects and determines a cell to camp on based on a cell selection policy, and establishes an RRC connection with the wireless network base station corresponding to the cell. The RRC connection establishment procedure is performed according to a 3GPP standard protocol procedure, and includes:

s201, UE initiates an RRC connection establishment request (RRC setup request) to a network side.

S202, the gNB sends RRC connection configuration information (RRC setup) to the UE through the message.

S203, after the UE completes the related configuration based on the RRC connection configuration information sent by the gNB, the UE replies an RRC connection setup complete confirmation message (RRC setup complete) to the gNB. The RRC setup complete includes PnP requested, UE ID.

The detailed flow of S201-S203 can be described with reference to section 5.3.3 of 3gpp TS 38.331, which is not described in detail herein.

After the UE completes RRC connection establishment, the UE may carry an NAS request in an RRC setup complete message to implement specific service processing (e.g., UE attach registration request, etc.).

The RRC setup complete message of S203 further includes device type information (terminal type) and protocol information, where the protocol information includes protocol type information (protocol type) and version information (version). The device type information indicates the type of the terminal device, and the specific value may be CPE-type, RSU-type, AR module-type, or the like, which indicates that the terminal device is a CPE, RSU, or AR module, respectively. The protocol type information represents a management protocol type supported by the terminal device, and a specific value of the protocol type information can be TR-069protocol, MQTT protocol or LWM2Mprotocol and other terminal management protocols. The version information is a version number of the terminal management Protocol identified by the Protocol type. It should be noted that the device type information, the protocol type information, and the version information may also be other names with corresponding functions, which is not limited in this application.

In a first possible implementation manner, since the terminal device only supports one management protocol, only the protocol type information and version information of the management protocol are carried in S203.

S204, after receiving the RRC setup complete message request of the UE, the gNB triggers the sending of the equipment registration information of the UE to the wireless network element management system based on the PnP requested registration indication in S203, wherein the message carries the PnP requested, the UE ID, the equipment type information, the protocol type information and the version information.

Illustratively, the gNB may send the UE device registration information through a management channel (e.g., through an operation, administration, and maintenance (OAM) notification message) with the wireless network element management system, and the specific implementation of this step may be based on a proprietary scheme of the gNB device manufacturer, or may refer to a VES-based scheme, an OAM notification, or a StreamData Report method of a 3GPP standard protocol.

And S205, registering and maintaining the UE information.

The EMS determines that the reported information is a PnP registration request sent by the UE according to a PnP requested registration instruction in the UE registration message, and then the UE mgt executes device registration management of the UE and maintains a corresponding relationship between the UE ID and the gNB IP, where the corresponding relationship is used for a downlink terminal management data route, that is, the EMS can determine through which management channel of the radio network element identified by the gNB IP the UE corresponding to the UE ID should send.

S206, after the EMS finishes the registration of the terminal equipment, replying a registration response message through a management interface between the EMS and the gNB, wherein the message comprises a registration result (registration success or registration failure);

s207, the gNB feeds back the registration result of the terminal device to the UE through an air interface bearer (e.g., data Radio Bearer (DRB) or Signaling Radio Bearer (SRB)) of the terminal device.

In the embodiment of the application, an Element Management System (EMS) and the UE mgt are fused to obtain a fusion management system, and the fusion management system manages the terminal device, so that the consumption of network resources is reduced, and the network construction and maintenance cost is reduced. Under the scene that the terminal equipment only supports one management protocol, the equipment information and the capability information are actively reported by the terminal equipment, so that the subsequent EMS can more quickly and accurately determine the type of the configuration parameters required by the terminal equipment for providing the wireless network access service. A second possible implementation:

under the scene that the terminal equipment supports various types of management protocols or supports various versions of one management protocol, the terminal equipment establishes a process in a PnP or management channel and sends equipment type information of the terminal equipment supported by the terminal equipment, all protocol type information and version information supported by the terminal equipment, and the like to an EMS (information management system).

S201-S207 may specifically refer to the description in the first possible implementation manner, where the difference is:

the protocol type information and version information carried in the RRC setup complete message in S203 and the UE registration information in S204 respectively include protocol type information and version information of all management protocols supported by the UE.

In the embodiment of the application, an Element Management System (EMS) and the UE mgt are fused to obtain a fusion management system, and the fusion management system manages the terminal device, so that the consumption of network resources is reduced, and the network construction and maintenance cost is reduced. Under the scene that the terminal equipment supports various types of management protocols or various protocol versions, the equipment information and the capability information are actively reported by the terminal equipment, so that the subsequent EMS can combine the information reported by the terminal equipment to more quickly and accurately determine the type of the configuration parameters required by the terminal equipment for providing the wireless network access service.

A third possible implementation:

under the scene that the terminal equipment supports various types of management protocols or supports various versions of one management protocol, the terminal equipment sends equipment type information of the terminal equipment supported by the terminal equipment, all protocol type information and version information supported by the terminal equipment and the like to an EMS (information management system) in a PnP or management channel establishing process, and simultaneously, the terminal equipment also reports an optimal strategy of the protocol.

S201-S207 may specifically refer to the description in the second possible implementation manner, where the difference is:

the RRC setup complete message in S203 and the UE registration information in S204 also carry the corresponding priority of each protocol type information/version information, respectively. This priority may be the priority with which such protocol type information or version information is selected for use.

As an example, the priority information may be in the form { [ TR069, high priority ], [ MQTT, low priority ], [ LWM2M, medium priority ] }, which expresses that the terminal device supports three management protocol types of TR069, MQTT and LWM2M, and the priority of the three protocols selected for use is TR069 > MQTT > LWM2M. The priority information is sent to the EMS so that the EMS determines a target management protocol among all management protocols supported by the UE in combination with the capability information of the EMS.

According to the embodiment of the application, an Element Management System (EMS) and the UE mgt are fused to obtain the fusion management system, and the fusion management system is used for managing the terminal equipment, so that the consumption of network resources is reduced, and the network construction and maintenance cost is reduced. Under the scene that the terminal equipment supports various types of management protocols or various protocol versions, the terminal equipment actively reports the equipment information, the capability information and the protocol optimization strategy, so that the subsequent EMS can combine the information reported by the terminal equipment to more quickly and accurately determine the type of the configuration parameters required by the terminal equipment for providing the wireless network access service.

The following describes the management method 300 of the terminal device according to the embodiment of the present application in detail with reference to fig. 7. Fig. 7 is a schematic interaction diagram of a method 300 of the present application.

Fig. 7 illustrates a plug and play (PnP) or management channel establishment procedure for a terminal device, and several possible implementations of the method 300 are described below.

A first possible implementation:

under the scene that the terminal equipment supports various types of management protocols or supports various versions of one management protocol, the terminal equipment establishes a flow in a PnP or a management channel and sends equipment type information of the terminal equipment supported by the terminal equipment, all protocol type information and version information supported by the terminal equipment, and the like to an EMS (information management system). When the terminal device PnP is registered, the EMS determines the protocol type information or the version information of the management protocol to be adopted based on the local strategy, records the information, then feeds back the selected information to the UE in the device registration response message to the gNB or the UE, and the UE records the information returned by the EMS.

S301-S304 may refer specifically to the descriptions of S201-S204 in the second possible implementation of method 200.

S305, selecting the protocol type and version of the management protocol.

Meanwhile, the EMS determines a target management protocol from the protocol type information and/or the version information of the management protocols supported by the terminal device based on a policy locally configured by the EMS, such as random selection or other automatic rules, that is, determines the target protocol information and/or the target version information.

Several cases in which the EMS determines the target protocol information and/or the target version information are separately described below by several examples.

Illustratively, the UE sends a plurality of protocol type information to the EMS, and the EMS determines target protocol information based on a locally configured policy, and selects a management protocol corresponding to the target protocol information to communicate with the UE. Or the UE sends a plurality of protocol type information and a plurality of version information to the EMS, the EMS selects target protocol information and target version information based on the locally configured strategy, and selects a management protocol corresponding to the target protocol information and the target version information to communicate with the UE. Or the UE sends a plurality of version information to the EMS, the EMS selects target version information based on the locally configured strategy, and selects a management protocol corresponding to the target version information to communicate with the UE.

S306, after the EMS completes registration of the terminal device, the EMS replies a UE registration response message through the management interface with the gNB, where the message includes a registration result (registration success or registration failure), and selected protocol type information and/or version information (i.e., selected protocol or selected version).

S307, the gNB feeds back the registration result of the terminal device and the selected management protocol or protocol version information (i.e., selected protocol or selected version) to the UE through an air interface bearer (e.g., DRB or SRB) of the terminal device.

S308, the UE receives the EMS feedback and records the selected protocol type information or version information (i.e., selected protocol or selected version). Therefore, in the subsequent parameter configuration process, the UE can perform protocol processing based on the target management protocol corresponding to the recorded management protocol type information or version information.

In the embodiment of the application, an Element Management System (EMS) and the UE mgt are fused to obtain a fusion management system, and the fusion management system manages the terminal device, so that the consumption of network resources is reduced, and the network construction and maintenance cost is reduced. Under the scene that the terminal equipment supports various types of management protocols or various protocol versions, equipment information and capability information are actively reported by the terminal equipment, and the type of configuration parameters required by the terminal equipment for providing wireless network access service can be determined more quickly and accurately by combining the information reported by the terminal equipment and a local strategy through the EMS.

A second possible implementation:

under the scene that the terminal equipment supports various types of management protocols or supports multiple versions of one management protocol, the terminal equipment sends equipment type information of the terminal equipment supported by the terminal equipment, all protocol type information and version information supported by the terminal equipment and the like to an EMS (information management system) in a PnP or management channel establishing process, and simultaneously, the terminal equipment also reports an optimal strategy of the protocol. When the terminal device PnP is registered, the EMS determines the protocol type information or version information of the management protocol to be adopted based on the protocol capability supported by the EMS and the preferred strategy of the terminal device, records the information, then feeds back the selected information to the UE in the device registration response message to the gNB or the UE, and the UE records the information returned by the EMS.

S301-S304 may refer specifically to the descriptions of S201-S204 in the third possible implementation of method 200.

S305, selecting the protocol type and version of the management protocol.

Meanwhile, the EMS determines the target management protocol from the protocol type information and/or the version information of the multiple management protocols supported by the terminal equipment based on the protocol capability supported by the EMS and the preferred strategy of the terminal equipment, namely determines the target protocol information and/or the target version information.

Several cases in which the EMS determines the target protocol information and/or the target version information, respectively, are described below by several examples.

In an example, a UE sends multiple protocol type information to an EMS, and the EMS determines target protocol information based on a locally configured policy, and selects a management protocol corresponding to the target protocol information to communicate with the UE. Or, in example two, the UE sends multiple pieces of protocol type information and multiple pieces of version information to the EMS, and the EMS selects target protocol information and target version information based on the locally configured policy, and selects a management protocol corresponding to the target protocol information and the target version information to communicate with the UE. Or, in the third example, the UE sends multiple version information to the EMS, and the EMS selects target version information based on the locally configured policy, and selects a management protocol corresponding to the target version information to communicate with the UE.

In the following, by taking the above example one as an example, how the EMS supports the protocol type information of the plurality of management protocols supported from the terminal device based on the protocol capability supported by the EMS and the preferred policy of the terminal device is described in detail.

Illustratively, the priority information may be in the form { [ TR069, high priority ], [ MQTT, low priority ], [ LWM2M, medium priority ] }, which expresses the fact that the terminal device supports three management protocol types of TR069, MQTT and LWM2M, and the priority of the three protocols selected for use is TR069 > MQTT > LWM2M. The priority information is sent to the EMS so that the EMS determines a target management protocol among all management protocols supported by the UE in combination with the capability information of the EMS. Assuming that EMS (UE mgt) only supports MQTT and LWM2M management protocols, EMS (UE mgt) refers to the selection priority of terminal device for each management protocol (i.e. the selection priority of MQTT is low priority, but the selection priority of LWM2M2 is Medium priority), and finally selects the LWM2M management protocol with Medium priority to perform protocol processing on configuration parameters.

S306-S308 may specifically refer to the corresponding description of the first possible implementation manner of the method 300.

In the embodiment of the application, an Element Management System (EMS) and the UE mgt are fused to obtain a fusion management system, and the fusion management system manages the terminal device, so that the consumption of network resources is reduced, and the network construction and maintenance cost is reduced. Under the scene that the terminal equipment supports various types of management protocols or various protocol versions, the terminal equipment actively reports the equipment information, the capability information and the protocol optimization strategy, and the EMS combines the information reported by the terminal equipment and the self capability, so that the type of the configuration parameters required by the terminal equipment for providing the wireless network access service can be determined more quickly and accurately.

The following describes the management method 400 of the terminal device according to the embodiment of the present application in detail with reference to fig. 8. Fig. 8 is a schematic interaction diagram of a method 400 of the present application.

Fig. 8 shows a terminal device parameter configuration flow, which is two independent flows from the terminal device PnP device registration flow shown in fig. 6 and 7, and the management system can initiate the parameter configuration flow to configure the terminal device parameters only after the terminal device starts and completes the PnP device registration flow first. But the parameter configuration process is triggered immediately after the PnP device registration process is not completed. The method 400 of the embodiments of the present application may be combined with the method 200 or 300, and the method 200 or 300 may be performed before the method 400, but is not limited to performing the method 200 or 300 immediately after performing the method 400.

Several possible implementations of method 400 are described below.

A first possible implementation:

before the method 400, the EMS has already obtained the device type information of the UE and the protocol type information and/or version information of the management protocol used in the subsequent parameter configuration, and the EMS determines a template and a protocol processing mode for parameter configuration based on the terminal type information, the protocol type information, and the version information in the parameter configuration process, and sends configuration parameters to the UE based on the protocol processing mode.

It should be appreciated that the EMS may obtain the terminal type information, the protocol type information, and the version information in a variety of ways, depending on how the method 400 is combined with the methods 200 or 300, and several possible combinations are described below.

The first method is as follows:

in combination with the first possible implementation manner of the method 200, in a scenario where the terminal device only supports one management protocol, the EMS receives device type information, protocol information, and the like of the terminal device in the PnP or management channel establishment procedure and sends the received device type information, protocol information, and the like to the EMS of the convergence management system.

S401, when executing parameter configuration for terminal equipment, EMS (UE mgt) determines the type of the terminal equipment based on the terminal equipment type information, thereby determining the corresponding parameter type, the parameter type is used for indicating the type of configuration parameters required by the UE for providing wireless network access service for other terminal equipment, determines a target management protocol used when transmitting the configuration parameters to the UE based on protocol information (including protocol type information and/or version information), and carries out modeling processing (including packaging the configuration parameters according to the parameter object format of the protocol) on the configuration parameters according to the processing mode (such as message format and parameter format) of the target management protocol.

The device type information indicates the type of the terminal device, and the specific value may be CPE-type, RSU-type, AR module-type, or the like, which indicates that the terminal device is a CPE, RSU, or AR module, respectively. The protocol type information represents a management protocol type supported by the terminal device, and a specific value of the protocol type information may be a terminal management protocol such as TR-069protocol, MQTT protocol or LWM2 mprog protocol. The version information is a version number of the terminal management Protocol identified by the Protocol type. It should be noted that the device type information, the protocol type information, and the version information may also be other names with corresponding functions, which is not limited in this application.

It should be understood that, under the converged architecture, the UE mgt may reuse a management channel of the EMS to the wireless network element, so as to implement management of the CPE or RSU and other terminal devices. Since the EMS manages the gNB by incorporating each parameter of the gNB into the model, the EMS (UE mgt) in the embodiment of the present application may also manage each configuration parameter of the UE into the model.

S402, EMS sends UE configuration information to the gNB.

After the EMS (UE mgt) completes configuration parameter modeling, the configuration parameters modeled according to the target management protocol in S401 are sent to the gNB through a management interface message between the gNB, the message carries a configured UE identifier (UE ID) or UE IP, and configuration information (Config info) for the configuration parameters of the UE, where the Config info may include a wireless network Service Set Identifier (SSID) of a wireless network access service provided by the UE, a password corresponding to the SSID, a clock synchronization server IP address, and other vendor-defined parameter information.

As an example, the management interface message may be a CreateMOI interface message defined by the 3GPP standard, and then both the corresponding terminal device identifier UE ID or UE IP and the configuration parameter Config info for the terminal device should be modeled according to an information model supporting the CreateMOI interface message, for example, in this embodiment of the present application, an Information Object Class (IOC) of a terminal device parameter configuration resource model DeviceConfig information may be defined as table 1. Table 1 shows DeviceConfig IOC parameter attributes, i.e., table 1 lists the parameter name of the configuration parameter of the UE for the first column and the corresponding parameter function for the second column.

TABLE 1

Parameter name	Parameter function
		UE ID	Terminal equipment identification
ConfigFile	Vendor defined parameters
		NTPServer	Clock synchronization server name or IP address
SSID	Network identification of wireless network service provided by terminal equipment

It should be noted that the management interface message may also be other interface messages and corresponding message parameter formats, which is not limited in this application.

S403, the gNB receives the configuration parameters of the EMS, parses the message parameters in step 2, obtains the UE identifier and the configuration parameters (i.e. the parameter information in table 1) therein, and matches an air interface bearer (such as a data radio bearer/DRB or a signaling radio bearer/SRB) for transmitting the management data of the terminal device based on the UE ID or the UE IP.

And S404, the gNB sends the UE configuration information to the UE through an air interface bearer for transmitting the terminal equipment management data corresponding to the terminal equipment identified by the UE Id.

S405, after receiving the configuration information, the UE analyzes the message parameters based on the corresponding terminal equipment management protocol and executes the corresponding parameter configuration.

In the embodiment of the application, an Element Management System (EMS) and the UE mgt are fused to obtain a fusion management system, and the fusion management system manages the terminal device, so that the consumption of network resources is reduced, and the network construction and maintenance cost is reduced. Under the scene that the terminal equipment only supports one management protocol, the EMS can more quickly and accurately determine the type of configuration parameters required by the terminal equipment for providing the wireless network access service and execute a corresponding parameter configuration process according to the equipment information and the capability information actively reported by the terminal equipment.

The second method comprises the following steps:

in combination with the first possible implementation manner of the method 300, in a scenario where the terminal device supports multiple types of management protocols or supports multiple versions of one management protocol, the EMS receives, in the PnP or management channel establishment procedure, device type information of the terminal device supported by the terminal device, all pieces of management protocol type information and version information supported by the terminal device, and determines protocol type information or version information of a management protocol to be used based on a local policy, and records the information.

S401-S405 may specifically refer to the corresponding description in manner one.

In the embodiment of the application, an Element Management System (EMS) and the UE mgt are fused to obtain a fusion management system, and the fusion management system manages the terminal device, so that the consumption of network resources is reduced, and the network construction and maintenance cost is reduced. Under the scene that the terminal equipment supports various types of management protocols or various protocol versions, equipment information and capability information are actively reported by the terminal equipment, and EMS combines the information reported by the terminal equipment and a local strategy to more quickly and accurately determine the type of configuration parameters required by the terminal equipment for providing wireless network access service and execute a corresponding parameter configuration flow.

The third method comprises the following steps:

in combination with the second possible implementation manner of the method 300, in a scenario where the terminal device supports multiple types of management protocols or supports multiple versions of one management protocol, the EMS receives, in the PnP or management channel establishment procedure, the device type information of the terminal device supported by the UE, all the protocol type information and version information supported by the UE, and the preferred policy of the protocol, determines the protocol type information or version information of the management protocol to be used based on the protocol capability supported by the EMS and the preferred policy of the terminal device, and records these pieces of information.

S401-S405 may refer to the corresponding description in manner one.

In the embodiment of the application, an Element Management System (EMS) and the UE mgt are fused to obtain a fusion management system, and the fusion management system manages the terminal device, so that the consumption of network resources is reduced, and the network construction and maintenance cost is reduced. Under the scene that the terminal equipment supports various types of management protocols or various protocol versions, the terminal equipment actively reports the equipment information, the capability information and the protocol optimization strategy, and the EMS combines the information reported by the terminal equipment and the self capability, so that the type of configuration parameters required by the terminal equipment for providing the wireless network access service can be determined more quickly and accurately, and a corresponding parameter configuration process is executed.

A second possible implementation:

before the method 400, the EMS has already obtained the device type information of the UE, but has not yet determined the protocol information of the management protocol used in the subsequent parameter configuration, and the EMS first selects the protocol information of the target management protocol in the parameter configuration process, then determines the template and the protocol processing mode of the parameter configuration based on the device type information and the protocol information, and sends the configuration parameters to the UE based on the protocol processing mode.

It should be appreciated that the EMS may obtain the device type information, protocol information in a variety of ways, depending on how the method 400 is combined with the method 200, and several possible combinations are described below.

The first method is as follows:

in combination with the second possible implementation manner of the method 200, in a scenario where the terminal device supports multiple types of management protocols or supports multiple versions of one management protocol, the EMS receives, in a PnP or management channel establishment procedure, device type information of the terminal device supported by the UE, all pieces of supported protocol type information and/or version information, and the like, and sends the information to the EMS (convergence management system), and the EMS (UE mgt) determines adopted protocol type information and version information based on a local configuration policy during parameter configuration, and performs parameter modeling processing based on the determined protocol type and version. And simultaneously returning the selected protocol type and version information to the terminal equipment in the parameter configuration process.

S401 to S405 may specifically refer to descriptions corresponding to S401 to S405 in a first possible implementation manner of the method 400, and the differences are:

in S401, before determining the protocol processing mode, the EMS further needs to determine a target management protocol used when the configuration parameters are subsequently transmitted from among a plurality of management protocols supported by the terminal device. Specifically, the EMS selects protocol type information and/or version information for the target management protocol to use based on policies configured locally by the EMS, such as random selection or other automated rules.

In S402-S404, in addition to sending the UE configuration information to the UE, the EMS also sends the protocol information selected in S401 to the UE through the gNB, where the protocol information includes protocol type information and/or version information.

In S405, before performing parameter configuration, the UE needs to analyze the configuration parameters according to the received protocol information to obtain corresponding parameter information.

In the embodiment of the application, an Element Management System (EMS) and the UE mgt are fused to obtain a fusion management system, and the fusion management system manages the terminal device, so that the consumption of network resources is reduced, and the network construction and maintenance cost is reduced. Under the scene that the terminal equipment supports various types of management protocols or various protocol versions, the EMS actively reports the equipment information and the capability information according to the terminal equipment, can more quickly and accurately determine the type of configuration parameters required by the terminal equipment for providing the wireless network access service and execute a corresponding parameter configuration process.

The second method comprises the following steps:

in combination with the third possible implementation manner of the method 200, in a scenario where the terminal device supports multiple types of management protocols or supports multiple versions of one management protocol, the EMS receives, in the PnP or management channel establishment procedure, device type information of the terminal device supported by the UE, all protocol type information and version information supported by the UE, and sends the received information to the EMS, and also receives a protocol optimization policy sent by the UE. The method comprises the steps that when parameter configuration is carried out, an integration management system EMS (UE mgt) determines the type or the version of an adopted management protocol based on the protocol capability supported by the combination EMS (UE mgt) and the preferred strategy of the terminal equipment, parameter modeling processing is carried out based on the determined protocol type and version, and selected protocol information is returned to the terminal equipment in a configuration flow.

S401 to S405 may specifically refer to descriptions corresponding to S401 to S405 in a first manner of a second possible implementation manner in the method 400, and the difference is that:

in S401, since in the third possible implementation manner of the method 200, the UE sends the preferred policy of the protocol to the EMS, the EMS refers to the management protocol type supported by the EMS on one hand and refers to the preferred policy of the terminal device on the other hand when selecting the target management protocol.

As an example, the priority information may be in the form { [ TR069, high priority ], [ MQTT, low priority ], [ LWM2M, medium priority ] }, which expresses that the terminal device supports three management protocol types of TR069, MQTT and LWM2M, and the priority of the three protocols selected for use is TR069 > MQTT > LWM2M. The priority information is sent to the EMS so that the EMS determines a target management protocol among all management protocols supported by the UE in combination with the capability information of the EMS. Assuming that EMS (UE mgt) only supports MQTT and LWM2M management protocols, EMS (UE mgt) refers to the selection priority of terminal device for each management protocol (i.e. the selection priority of MQTT is low priority, but the selection priority of LWM2M2 is Medium priority), and finally selects the LWM2M management protocol with Medium priority to perform protocol processing on configuration parameters.

In the embodiment of the application, an Element Management System (EMS) and the UE mgt are fused to obtain a fusion management system, and the fusion management system manages the terminal device, so that the consumption of network resources is reduced, and the network construction and maintenance cost is reduced. Under the scenario that the terminal device supports multiple types of management protocols or multiple protocol versions, the EMS may determine the type of configuration parameters required by the terminal device to provide the wireless network access service more quickly and accurately and execute a corresponding parameter configuration flow by combining the device information, the capability information and the protocol preference policy reported by the terminal device.

The method provided by the embodiment of the present application is described in detail above with reference to fig. 1 to 8. Hereinafter, the apparatus provided in the embodiment of the present application will be described in detail with reference to fig. 9 to 10.

Fig. 9 is a schematic block diagram of a communication apparatus for management of a terminal device according to an embodiment of the present application. As shown in fig. 9, the communication device 10 may include a transceiver module 11 and a processing module 12.

The transceiver module 11 may be configured to receive information sent by another apparatus, and may also be configured to send information to another apparatus. Such as receiving a device type message or sending configuration parameters. The processing module 12 may be used to perform content processing of the device, such as determining configuration parameters.

In one possible design, the communication device 10 may correspond to a terminal device in the above-described method embodiment.

Specifically, the communication apparatus 10 may correspond to a terminal device or a UE in any one of the methods 100 to 400 according to the embodiment of the present application, the communication apparatus 10 may include a module for performing an operation performed by the terminal device in the corresponding method, and each unit in the communication apparatus 10 is respectively for implementing the operation performed by the terminal device in the corresponding method.

Illustratively, when the communication device 10 corresponds to the terminal device in the method 100, the transceiver module 11 is configured to execute steps S101 and S102, and the processing module 12 is configured to execute step S103.

Illustratively, when the communication device 10 corresponds to a UE in the method 200, the transceiver module 11 is configured to perform steps S201-S203, S207.

Illustratively, when the communication device 10 corresponds to the UE in the method 300, the transceiver module 11 is configured to execute steps S301-S303, S307, and the processing module 12 is configured to execute step S308.

Illustratively, when the communication device 10 corresponds to the UE in the method 400, the transceiver module 11 is configured to execute step S404, and the processing module 12 is configured to execute step S405.

In another possible design, the communication device 10 may correspond to the terminal device management entity in the above method embodiment, or the UE mgt, or the EMS, or the converged system of the EMS and the UE mgt.

Specifically, the communication device 10 may correspond to the terminal device management entity, or the UE mgt, or the EMS, or the converged system of the EMS and the UE mgt in any one of the methods 100 to 400 according to the embodiments of the present application, the communication device 10 may include a module for performing operations performed by the terminal device management entity, or the UE mgt, or the EMS, or the converged system of the EMS and the UE mgt in the corresponding method, and each unit in the communication device 10 is respectively for implementing operations performed by the terminal device management entity, or the UE mgt, or the EMS, or the converged system of the EMS and the UE mgt in the corresponding method.

Illustratively, when the communication apparatus 10 corresponds to the terminal device management entity in the method 100, the transceiver module 11 is configured to perform steps S101 and S102.

Illustratively, when the communication device 10 corresponds to the UE mgt, or EMS, or the converged system of EMS and UE mgt in the method 200, the transceiver module 11 is configured to execute steps S204 and S206, and the processing module 12 is configured to execute step S205.

Illustratively, when the communication device 10 corresponds to the UE mgt, or EMS, or the converged system of EMS and UEmgt in the method 300, the transceiver module 11 is configured to execute steps S304 and S306, and the processing module 12 is configured to execute step S305.

Illustratively, when the communication device 10 corresponds to UE mgt, or EMS, or a converged system of EMS and UE mgt in the method 400, the transceiving module 11 is configured to perform step S402, and the processing module 12 is configured to perform step S401.

In a possible design, the apparatus 20 may be a terminal device management entity, or may be a chip or a system of chips located on the terminal device management entity.

In one possible design, the apparatus 20 may be a terminal device including various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem, and various forms of terminals, mobile stations, terminals, user equipment, soft terminals, etc., and may also be a chip or a system of chips located on the terminal device, etc.

The apparatus 20 may include a processor 21 (i.e., an example of a processing module) and a memory 22. The memory 22 is used for storing instructions, and the processor 21 is used for executing the instructions stored in the memory 22 to make the apparatus 20 implement the steps performed by the devices in the various possible designs in the corresponding methods in fig. 5 to 8.

Further, the apparatus 20 may further include an input port 23 (i.e., one example of a transceiver module) and an output port 24 (i.e., another example of a transceiver module). Further, the processor 21, memory 22, input 23 and output 24 may communicate with each other via internal connection paths to transfer control and/or data signals. The memory 22 is used for storing a computer program, and the processor 21 may be used for calling and running the computer program from the memory 22 to control the input port 23 to receive a signal and the output port 24 to send a signal, so as to complete the steps of the method described above for the terminal device, the radio access network device, the UE, or the base station. The memory 22 may be integrated in the processor 21 or may be provided separately from the processor 21.

Alternatively, if the message transmission apparatus 20 is a communication device, the input port 23 is a receiver, and the output port 24 is a transmitter. Wherein the receiver and the transmitter may be the same or different physical entities. When the same physical entity, may be collectively referred to as a transceiver.

Alternatively, if the device 20 is a chip or a circuit, the input port 23 is an input interface, and the output port 24 is an output interface.

As an implementation manner, the functions of the input port 23 and the output port 34 may be realized by a transceiver circuit or a dedicated chip for transceiving. The processor 21 may be considered to be implemented by a dedicated processing chip, processing circuit, processor, or a general purpose chip.

As another implementation manner, a device provided by the embodiment of the present application may be implemented by using a general-purpose computer. Program codes that will implement the functions of the processor 21, the input port 23 and the output port 24 are stored in the memory 22, and a general-purpose processor implements the functions of the processor 21, the input port 23 and the output port 24 by executing the codes in the memory 22.

Each module or unit in the apparatus 20 may be configured to execute each action or processing procedure executed by a device (e.g., a terminal device) performing random access in the foregoing method, and a detailed description thereof is omitted here to avoid redundancy.

For the concepts, explanations, details and other steps related to the technical solutions provided in the embodiments of the present application related to the apparatus 20, please refer to the descriptions of the foregoing methods or other embodiments, which are not repeated herein.

It should be understood that in the embodiments of the present application, the processor may be a Central Processing Unit (CPU), and the processor may also be other general-purpose processors, digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The embodiment of the present application further provides a computer-readable storage medium, on which computer instructions for implementing the method executed by the authentication service function entity or the unified data management entity or the terminal device in the above method embodiments are stored.

For example, the computer program, when executed by a computer, causes the computer to implement the method performed by the terminal device management entity or the terminal device in the above-described method embodiments.

Embodiments of the present application further provide a computer-readable storage medium, on which computer instructions for implementing the method performed by the terminal device management entity or the terminal device in the foregoing method embodiments are stored.

It will also be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and direct bus RAM (DR RAM).

The above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, the above-described embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. The procedures or functions according to the embodiments of the present application are wholly or partially generated when the computer instructions or the computer program are loaded or executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more collections of available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. The semiconductor medium may be a solid state disk.

It should be understood that the term "and/or" herein is merely one type of association relationship that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one type of logical functional division, and other divisions may be realized in practice, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A management method for terminal equipment is characterized by comprising the following steps:

a terminal equipment management entity receives equipment type information from terminal equipment, wherein the equipment type information is used for indicating the type of the terminal equipment, and the terminal equipment is used for providing wireless network access service;

and the terminal equipment management entity sends configuration parameters to the terminal equipment, the configuration parameters are determined according to the equipment type information, and the configuration parameters are used for the configuration of the terminal equipment.

2. The method of claim 1, further comprising: and the terminal equipment management entity determines the configuration parameters according to the equipment type information.

3. The method of claim 2, wherein the determining, by the terminal device management entity, the configuration parameter according to the device type information comprises:

the terminal equipment management entity determines a parameter type according to the equipment type information, wherein the parameter type is used for indicating the type of the configuration parameter required by the terminal equipment for providing the wireless network access service;

and the terminal equipment management entity determines the configuration parameters according to the parameter types.

4. The method of claim 1, further comprising:

the method comprises the following steps that a terminal equipment management entity receives protocol information from the terminal equipment, wherein the protocol information comprises one or more of the following items: the protocol type information is used for indicating the management protocol type supported by the terminal equipment, and the version information is used for indicating the version number of the management protocol type supported by the terminal equipment;

wherein, the sending, by the terminal device management entity, the configuration parameter to the terminal device includes:

and the terminal equipment management entity sends the configuration parameters to the terminal equipment according to the protocol information.

5. The method of claim 4,

the terminal device management entity sends the configuration parameters to the terminal device according to the protocol information, and the configuration parameters comprise: the terminal device management entity sends the configuration parameters to the terminal device according to target protocol information, wherein the target protocol information comprises one or more of the following items: target protocol type information or target version information; wherein,

the protocol information comprises a plurality of protocol type information, and the target protocol type information of the target protocol information is one of the plurality of protocol type information; or,

the protocol information comprises a plurality of protocol version information, and the target protocol version information of the target protocol information is one of the plurality of protocol version information; or,

the protocol information comprises a plurality of protocol type information and a plurality of protocol version information, the target protocol type information of the target protocol information is one of the plurality of protocol type information, and the target protocol version information of the target protocol information is one of the plurality of protocol version information.

6. The method according to claim 4 or 5, characterized in that the method further comprises:

and the terminal equipment management entity sends the target protocol information to the terminal equipment.

7. The method according to any one of claims 4 to 6, further comprising:

the device management entity receives priority information from the terminal device, wherein the priority information is used for indicating the priority of the protocol information, and the priority of the protocol information comprises one or more of the following items: priority of protocol type information or priority of version information;

wherein, the sending, by the terminal device management entity, the configuration parameter to the terminal device according to the protocol information includes:

and the terminal equipment management entity sends the configuration parameters to the terminal equipment according to the protocol information and the priority of the protocol information.

8. The method according to any one of claims 4 to 7, wherein the terminal device management entity sends the configuration parameters to the terminal device according to the protocol information, and comprises:

and the terminal equipment management entity sends the configuration parameters to the terminal equipment according to the protocol information and the strategy.

9. The method according to any one of claims 1 to 8, wherein the configuration parameters comprise a wireless network Service Set Identifier (SSID) of a wireless network access service provided by the terminal device, a password corresponding to the SSID, a clock synchronization server Internet Protocol (IP) address and vendor information.

10. A management method for terminal equipment is characterized by comprising the following steps:

the terminal equipment sends equipment type information to a terminal equipment management entity, wherein the protocol type information is used for indicating a management protocol type supported by the terminal equipment, and the terminal equipment is used for providing wireless network access service;

the terminal equipment receives configuration parameters from the terminal equipment management entity, wherein the configuration parameters are used for the configuration of the terminal equipment and are determined according to the equipment type information;

and the terminal equipment carries out configuration according to the configuration parameters.

11. The method of claim 10, further comprising:

the terminal equipment sends protocol information to the terminal equipment management entity, wherein the protocol information comprises one or more of the following items: the protocol type information is used for indicating the management protocol type supported by the terminal equipment, and the version information is used for indicating the version number of the management protocol type supported by the terminal equipment.

12. The method of claim 11, further comprising:

the terminal equipment receives target protocol information from the terminal equipment management entity, wherein the target protocol information comprises one or more of the following items: target protocol type information or target version information; wherein,

13. The method according to claim 11 or 12, characterized in that the method further comprises:

the terminal device sends priority information to the terminal device management entity, the priority information is used for indicating the priority of the protocol information, and the priority of the protocol information comprises one or more of the following items: a priority of protocol type information or a priority of version information.

14. The method according to any one of claims 10 to 13, wherein the configuration parameters comprise a wireless network Service Set Identification (SSID) of a wireless network access service provided by the terminal device and a password corresponding to the SSID, a clock synchronization server Internet Protocol (IP) address and vendor information.

15. A management apparatus of a terminal device, comprising:

the terminal equipment comprises a receiving and sending module, a processing module and a processing module, wherein the receiving and sending module is used for receiving equipment type information from the terminal equipment, the equipment type information is used for indicating the type of the terminal equipment, and the terminal equipment is used for providing wireless network access service;

the transceiver module is further configured to send configuration parameters to the terminal device, where the configuration parameters are determined according to the device type information, and the configuration parameters are used for configuring the terminal device.

16. The apparatus of claim 15, further comprising:

and the processing module is used for determining the configuration parameters according to the equipment type information.

17. The apparatus according to claim 16, wherein the processing module is specifically configured to determine the parameter type according to the device type information, where the parameter type is used to indicate a type of configuration parameters required by the terminal device to provide the wireless network access service;

the processing module is specifically further configured to determine the configuration parameter according to the parameter type.

18. The apparatus of claim 15,

the transceiver module is configured to receive protocol information from the terminal device, where the protocol information includes one or more of the following: the protocol type information is used for indicating the management protocol type supported by the terminal equipment, and the version information is used for indicating the version number of the management protocol type supported by the terminal equipment;

the processing module is specifically configured to send the configuration parameter to the terminal device according to the protocol information.

19. The apparatus of claim 18,

the processing module is specifically configured to send the configuration parameter to the terminal device according to target protocol information, where the target protocol information includes one or more of the following: target protocol type information or target version information; wherein,

20. The apparatus of claim 18 or 19,

the transceiver module is further configured to send the target protocol information to the terminal device.

21. The apparatus according to any of claims 18 to 20, wherein the transceiver module is further configured to receive priority information from the terminal device, the priority information indicating a priority of the protocol information, the priority of the protocol information including one or more of: the priority of the protocol type information or the priority of the version information;

the processing module is specifically configured to send the configuration parameter to the terminal device according to the protocol information and the priority of the protocol information.

22. The apparatus of any one of claims 18 to 21,

and the processing module is further configured to send the configuration parameters to the terminal device according to the protocol information and the policy.

23. The apparatus according to any of claims 15 to 22, wherein the configuration parameters comprise a wireless network service set identifier SSID of a wireless network access service provided by the terminal device and a password corresponding to the SSID, a clock synchronization server internet protocol IP address, and vendor information.

24. A management apparatus of a terminal device, comprising:

the terminal equipment comprises a receiving and sending module, a processing module and a processing module, wherein the receiving and sending module is used for sending equipment type information to a terminal equipment management entity, the protocol type information is used for indicating a management protocol type supported by the terminal equipment, and the terminal equipment is used for providing wireless network access service;

the transceiver module is configured to receive a configuration parameter from the terminal device management entity, where the configuration parameter is used for configuring the terminal device, and the configuration parameter is determined according to the device type information;

and the processing module is used for configuring according to the configuration parameters.

25. The apparatus of claim 24,

the transceiver module is configured to send protocol information to the terminal device management entity, where the protocol information includes one or more of the following: the protocol type information is used for indicating the management protocol type supported by the terminal equipment, and the version information is used for indicating the version number of the management protocol type supported by the terminal equipment.

26. The apparatus of claim 25,

the transceiver module is configured to receive target protocol information from the terminal device management entity, where the target protocol information includes one or more of the following: target protocol type information or target version information; wherein,

27. The apparatus of claim 25 or 26,

the transceiver module is further configured to send priority information to the terminal device management entity, where the priority information is used to indicate a priority of the protocol information, and the priority of the protocol information includes one or more of the following: priority of protocol type information or priority of version information.

28. The apparatus according to any of claims 24 to 27, wherein the configuration parameters comprise a wireless network service set identifier SSID of a wireless network access service provided by a terminal device and a password corresponding to the SSID, a clock synchronization server internet protocol IP address, and vendor information.

29. A communications apparatus, comprising:

a processor and a memory;

the memory for storing a computer program;

the processor is configured to execute the computer program stored in the memory to cause the communication apparatus to perform the communication method according to any one of claims 1 to 9 or perform the communication method according to any one of claims 10 to 14.

30. A computer-readable storage medium, having stored thereon a computer program which, when run on a computer, causes the computer to perform the communication method according to any one of claims 1 to 9, or to perform the communication method according to any one of claims 10 to 14.

31. A chip system, comprising: a processor for calling and running a computer program from a memory so that a communication device in which the system-on-chip is installed performs the communication method according to any one of claims 1 to 9, or performs the communication method according to any one of claims 10 to 14.

32. A management system of a terminal device, comprising a terminal device and a terminal device management entity, wherein the terminal device management entity is configured to perform the method of any one of claims 1 to 9, and the terminal device is configured to perform the method of any one of claims 10 to 14.