CN115835184A - Management method and device of terminal equipment - Google Patents

Abstract

The present application provides a method and device for managing terminal equipment. The method includes: a terminal equipment for providing wireless network access services sends equipment type information to a terminal equipment management entity, and the equipment type information is used to indicate the terminal equipment's type; the terminal device management entity sends a configuration parameter to the terminal device, the configuration parameter is determined according to the device type information, and the configuration parameter is used for configuration of the terminal device; the terminal device is configured according to the configuration parameter. In the method and device for managing terminal equipment provided in this application, the terminal equipment management entity can send configuration parameters to the terminal equipment according to the equipment type information reported by the terminal equipment, so that the terminal equipment that provides wireless network access services can perform parameter configuration, so that The terminal device management entity can realize the management of terminal devices without relying on end-to-end network resources, reduce the consumption of network resources, and reduce the cost of network construction and maintenance.

Description

Terminal equipment management method and device

technical field

The present application relates to the communication field, and more specifically, to a management method and device for terminal equipment.

Background technique

At present, the terminal equipment management entity (user equipment management, UE mgt) is based on the management solution of the data plane path provided by the third generation partnership project (3rd generation partnership project, 3GPP) network, and is used to manage the customer terminal equipment (customer-premises equipment) , CPE), roadside unit (road sideunit, RSU) and other terminal equipment. However, UE mgt's management of terminal equipment depends on end-to-end (end to end, E2E) network resources, which consumes a lot of network resources, especially the resources of the user plane function (UPF) of the core network, thus Need to invest a lot of network construction and maintenance costs. Therefore, how to reduce the consumption of network resources when managing terminal equipment such as CPE/RSU, and reduce the cost of network construction and maintenance is an urgent problem to be solved.

Contents of the invention

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

In a first aspect, a terminal device management method is provided, including: a terminal device management entity receives device type information from a terminal device, the device type information is used to indicate the type of the terminal device, and the terminal device is used to provide a wireless network Access service: the terminal device management entity sends configuration parameters to the terminal device, the configuration parameters are determined according to the device type information, and the configuration parameters are used for configuration of the terminal device.

In the above solution, through the terminal device actively reporting the device type information, the terminal device management entity can send configuration parameters to the terminal device according to the device type information, so that the terminal device that provides wireless network access services can perform parameter configuration, so that the terminal device management entity Management of terminal equipment can be realized without relying on end-to-end network resources, reducing the consumption of network resources and reducing the cost of network construction and maintenance.

With reference to the first aspect, in some implementation manners of the first aspect, the method further includes: the terminal device management entity determines configuration parameters according to the device type information.

With reference to the first aspect, in some implementation manners of the first aspect, the terminal device management entity determines configuration parameters according to the device type information, including: the terminal device management entity determines a parameter type according to the device type information, and the parameter type is used in The terminal device is used to instruct the terminal device to provide the type of configuration parameter required for the wireless network access service; the terminal device management entity determines the configuration parameter according to the parameter type.

In combination with the first aspect, in some implementations of the first aspect, the method further includes:

The terminal device management entity receives the protocol information from the terminal device, the protocol information includes one or more of the following: protocol type information or version information, the protocol type information is used to indicate the management protocol type supported by the terminal device, the version information A version number used to indicate the type of management protocol supported by the terminal device; where the terminal device management entity sends the configuration parameter to the terminal device, including: the terminal device management entity sends the configuration parameter to the terminal device according to the protocol information .

In the above solution, through the terminal device actively reporting device information and protocol information, the terminal device management entity can more quickly and accurately determine the type of configuration parameters required for the terminal device to provide wireless network access services.

With reference to the first aspect, in some implementation manners of the first aspect, the terminal device management entity sending the configuration parameter to the terminal device according to the protocol information includes: the terminal device management entity sending the configuration parameter to the terminal device according to the target protocol information The configuration parameter, the target protocol information includes one or more of the following: target protocol type information or target version information; wherein, the protocol information includes multiple protocol type information, and the target protocol type information of the target protocol information is the multiple One of the protocol type information; or, the protocol information includes multiple protocol version information, and the target protocol version information of the target protocol information is one of the multiple protocol version information; or, the protocol information includes multiple 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 some implementation manners of the first aspect, the method further includes: the terminal device management entity sending the target protocol information to the terminal device.

With reference to the first aspect, in some implementation manners of the first aspect, the method further includes: the device management entity receives priority information from the terminal device, where the priority information is used to indicate the priority of the protocol information, the The priority of the protocol information includes one or more of the following: the priority of the protocol type information or the priority of the version information; wherein, the terminal device management entity sends the configuration parameter to the terminal device according to the protocol information, including: the terminal The device management entity sends the configuration parameters to the terminal device according to the protocol information and the priority of the protocol information.

In the above solution, through the terminal device actively reporting device information, protocol information, and protocol preference policy, the terminal device management entity can determine the configuration parameters required for the terminal device to provide wireless network access services more quickly and accurately according to the information reported by the terminal device type.

With reference to the first aspect, in some implementation manners of the first aspect, the terminal device management entity sends the configuration parameter to the terminal device according to the protocol information, including: the terminal device management entity sends the configuration parameter to the terminal device according to the protocol information and policy The device sends this configuration parameter.

With reference to the first aspect, in some implementations of the first aspect, the configuration parameters include the wireless network service set identifier SSID of the wireless network access service provided by the terminal device, the password corresponding to the SSID, and the clock synchronization server Internet protocol The IP address, etc., configuration parameters also include other parameter types, which are not limited in this application.

In a second aspect, a terminal device management method is provided, including: the terminal device sends device type information to a terminal device management entity, the protocol type information is used to indicate the management protocol type supported by the terminal device, and the terminal device is used to provide Wireless network access service; the terminal device receives configuration parameters from the terminal device management entity, the configuration parameters are used for the configuration of the terminal device, and the configuration parameters are determined according to the device type information; the terminal device receives the configuration parameters according to the configuration parameters to configure.

In the above solution, through the terminal device actively reporting the device type information, the terminal device management entity can send configuration parameters to the terminal device according to the device type information, so that the terminal device that provides wireless network access services can perform parameter configuration, so that the terminal device management entity Management of terminal equipment can be realized without relying on end-to-end network resources, reducing the consumption of network resources and reducing the cost of network construction and maintenance.

With reference to the second aspect, in some implementations of the second aspect, the method further includes: the terminal device sends protocol information to the terminal device management entity, where the protocol information includes one or more of the following: protocol type information or version information, the protocol type information is used to indicate the management protocol type supported by the terminal device, and the version information is used to indicate the version number of the management protocol type supported by the terminal device.

In the above solution, the terminal device actively reports device information and protocol information, so that the terminal device management entity can more quickly and accurately determine the type of configuration parameters required by the terminal device to provide wireless network access services.

With reference to the second aspect, in some implementations of the second aspect, the method further includes: the terminal device receives 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, the protocol information includes multiple protocol type information, and the target protocol type information of the target protocol information is one of the multiple protocol type information; or, the protocol information includes multiple protocol version information , the target protocol version information of the target protocol information is one of the multiple protocol version information; or, the protocol information includes multiple protocol type information and multiple protocol version information, and the target protocol type information of the target protocol information is the One of multiple protocol type information, the target protocol version information of the target protocol information is one of the multiple protocol version information.

With reference to the second aspect, in some implementation manners of the second aspect, the method further includes: the terminal device sends priority information to the terminal device management entity, where the priority information is used to indicate the priority of the protocol information, the The priority of the protocol information includes one or more of the following: the priority of the protocol type information or the priority of the version information.

In the above solution, the terminal device actively reports device information, protocol information, and protocol preference policy, so that the subsequent terminal device management entity can combine the information reported by the terminal device to determine more quickly and accurately that the terminal device provides wireless network access services. The type of configuration parameter is the type of configuration parameter required.

With reference to the second aspect, in some implementations of the second aspect, the configuration parameters include the wireless network service set identifier SSID of the wireless network access service provided by the terminal device, the password corresponding to the SSID, and the clock synchronization server Internet protocol The IP address, etc., configuration parameters also include other parameter types, which are not limited in this application.

In a third aspect, a terminal device management device is provided, including: a transceiver module, configured to receive device type information from a terminal device, where the device type information is used to indicate the type of the terminal device, and the terminal device is used to provide wireless Network access service; the transceiver module is also used to send configuration parameters to the terminal device, the configuration parameters are determined according to the device type information, and the configuration parameters are used for configuration of the terminal device.

In the above solution, through the terminal device actively reporting the device type information, the terminal device management entity can send configuration parameters to the terminal device according to the device type information, so that the terminal device that provides wireless network access services can perform parameter configuration, so that the terminal device management entity Management of terminal equipment can be realized without relying on end-to-end network resources, reducing the consumption of network resources and reducing the cost of network construction and maintenance.

With reference to the third aspect, in some implementation manners of the third aspect, the apparatus further includes: a processing module, configured to determine configuration parameters according to the device type information.

With reference to the third aspect, in some implementation manners of the third aspect, the processing module is specifically configured to determine a parameter type according to the device type information, and the parameter type is used to indicate that the terminal device provides the wireless network access service. The type of the configuration parameter; the processing module is further configured to determine the configuration parameter according to the parameter type.

With reference to the third aspect, in some implementation manners 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 following: protocol type information or version information, the The protocol type information is used to indicate the management protocol type supported by the terminal device, and the version information is used to indicate the version number of the management protocol type supported by the terminal device; the processing module is specifically used to send the terminal device the protocol information according to the protocol information. configuration parameters.

With reference to the third aspect, in some 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; wherein, the protocol information includes multiple protocol type information, and the target protocol type information of the target protocol information is one of the multiple protocol type information; or, the protocol information includes multiple protocol version information , the target protocol version information of the target protocol information is one of the multiple protocol version information; or, the protocol information includes multiple protocol type information and multiple protocol version information, and the target protocol type information of the target protocol information is the One of multiple protocol type information, the target protocol version information of the target protocol information is one of the multiple protocol version information.

With reference to the third aspect, in some implementation manners 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 some implementation manners 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 the priority of the protocol information, and the protocol information The priority includes one or more of the following: the priority of the protocol type information or the priority of the version information; the processing module is specifically used 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 some implementation manners 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 policy.

With reference to the third aspect, in some implementations of the third aspect, the configuration parameters include the wireless network service set identifier SSID of the wireless network access service provided by the terminal device, the password corresponding to the SSID, and the clock synchronization server Internet protocol The IP address, etc., configuration parameters also include other parameter types, which are not limited in this application.

In a fourth aspect, there is provided a terminal device management device, 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 the management protocol type supported by the terminal device, and the terminal device Used to provide wireless network access services; the transceiver module is used to receive configuration parameters from the terminal device management entity, the configuration parameters are used for the configuration of the terminal device, and the configuration parameters are determined according to the device type information; processing module for configuration based on this directive.

In the above solution, through the terminal device actively reporting the device type information, the terminal device management entity can send configuration parameters to the terminal device according to the device type information, so that the terminal device that provides wireless network access services can perform parameter configuration, so that the terminal device management entity Management of terminal equipment can be realized without relying on end-to-end network resources, reducing the consumption of network resources and reducing the cost of network construction and maintenance.

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: protocol type information or version information, The protocol type information is used to indicate the management protocol type supported by the terminal device, and the version information is used to indicate the version number of the management protocol type supported by the terminal device.

With reference to the fourth aspect, in some implementation manners 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; wherein, the protocol information includes multiple protocol type information, and the target protocol type information of the target protocol information is one of the multiple protocol type information; or, the protocol information includes multiple protocol version information, the The target protocol version information of the target protocol information is one of the multiple protocol version information; or, the protocol information includes multiple protocol type information and multiple protocol version information, and the target protocol type information of the target protocol information is the multiple One of the protocol type information, the target protocol version information of the target protocol information is one of the multiple protocol version information.

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

With reference to the fourth aspect, in some implementations of the fourth aspect, the configuration parameters include the wireless network service set identifier SSID of the wireless network access service provided by the terminal device, the password corresponding to the SSID, and the clock synchronization server Internet protocol The IP address, etc., configuration parameters also include other parameter types, which are not limited in this application.

In a fifth aspect, a communication device is provided, including: a processor and a memory; the memory is used to store a computer program; the processor is used to execute the computer program stored in the memory, so that the communication device performs the claims The communication method of the first aspect or the second aspect.

In a sixth aspect, a computer-readable storage medium is provided. A computer program is stored on the computer-readable storage medium. When the computer program is run on a computer, the computer is made to execute the computer program described in the first aspect or the second aspect. communication method.

In a seventh aspect, a chip system is provided, including: a processor, configured to invoke and run a computer program from a memory, so that a communication device installed with the chip system executes the communication method as described in the first aspect or the second aspect.

In an eighth aspect, a terminal device management system is provided, including a terminal device and a terminal device management entity, where the terminal device management entity is configured to implement any one of the first aspect and the possible implementation manners of the first aspect The method described in item 1, the terminal device is configured to execute the method described in any one of the second aspect and possible implementation manners of the second aspect.

A ninth aspect provides a terminal device management system, including a terminal device management entity and a radio access network device, and the terminal device management entity is configured to implement any of the first aspect and the possible implementation manners of the first aspect. The method described in one item; the wireless access network device is used to receive the device type information from the terminal device and forward the device type information to the terminal device management entity; and is also used to receive the configuration from the terminal device management entity parameters and forwards the configuration parameters to the end device.

Description of drawings

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

Fig. 2 shows a schematic diagram of management architecture of terminal equipment such as CPE or RSU.

FIG. 3 shows a schematic diagram of an example of a converged architecture for communication management of wireless operation and maintenance terminals.

FIG. 4 shows a schematic diagram of another example of a converged architecture for communication management of wireless operation and maintenance terminals.

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

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

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

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

FIG. 9 is a schematic block diagram of a communication apparatus for terminal device management provided by an embodiment of the present application.

FIG. 10 is a schematic diagram of an apparatus 20 for terminal device management provided by an embodiment of the present application.

Detailed ways

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

The technical solution provided by the embodiment of the present application can be applied to various communication systems, for example: long term evolution (longterm evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex) system , TDD), Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) Communication System, Fifth Generation (5th Generation, 5G) System or New Radio (New Radio, NR) Or the future 3GPP system, etc.

Generally speaking, the number of connections supported by traditional communication systems is limited and easy to implement. However, with the development of communication technologies, mobile communication systems will not only support traditional communication, but also support, for example, device-to-device (D2D ) communication, machine to machine (machine to machine, M2M) communication, machine type communication (machine type communication, MTC), vehicle to everything (vehicle to everything, V2X) communication (also called vehicle network communication), for example, vehicle and Vehicle (vehicle to vehicle, V2V) communication (also known as vehicle-to-vehicle communication), vehicle-to-infrastructure (V2I) communication (also known as vehicle-to-infrastructure communication), vehicle-to-pedestrian (vehicle to pedestrian (V2P) communication (also called vehicle-to-person communication), and vehicle-to-network (V2N) communication (also called vehicle-to-network communication).

The application scenarios of 5G networks are rich and diverse, such as business-oriented (to business, 2B) scenarios for vertical industries, V2X scenarios for autonomous driving, and augmented reality (augmented reality, AR)/virtual reality (virtual reality, VR) for ordinary users. )Scenes.

At present, in 2B industry scenarios and V2X scenarios, common terminal equipment (user equipment, UE) (such as AGV, video camera, car, etc.) basically pass through customer-premises equipment (customer-premises equipment, CPE) side unit, RSU) is connected to the NR base station of the 5G network, and the CPE/RSU is connected to the operator's 5G network through the air interface. Therefore, the CPE or RSU terminal equipment is the key network equipment node for user service guarantee.

Fig. 1 shows a schematic diagram of a network architecture in a 2B or V2X scenario. In the architecture of Figure 1, CPE or RSU is a terminal device that provides wireless network access functions for other common terminals, and NR is a wireless access network base station (such as gNB) of a 5G network. An element management system (element management system, EMS) is used to manage wireless access network devices, including parameter configuration, performance management, and fault alarms of network elements. The 5GC control plane network function (CNF) refers to all control plane network elements (including AMF, SMF, NEF, NWDAF, etc.) of the 5G core network, and the user plane function (UPF) is the 5G core network user network element. UE mgt (UE management system) is a management system for terminal equipment such as CPE or RSU. Its functions include registration of CPE or RSU terminal equipment, parameter configuration, software upgrade, fault diagnosis, status and performance monitoring and other functions.

Fig. 2 shows a schematic diagram of management architecture of terminal equipment such as CPE or RSU. As shown in Figure 2, at present, the terminal management system (UE management, UE mgt) is deployed separately, which can implement the CPE or RSU terminal equipment based on the 3GPP network data plane path (ie UE-gNB-UPF-UE mgt). manage. Specifically, after the CPE or RSU terminal equipment attaches to the 5G network, the 5G network establishes a PDU session for the CPE or RSU terminal equipment dedicated to terminal equipment management data transmission. The PDU session is different from the normal service data of the terminal equipment. The transmitted PDU sessions, where the two types of PDU sessions correspond to different access point names (access point names, APNs) or data network names (data network names, DNNs) identifiers respectively. The path passed by the solid line with the arrow in Figure 2 is used for the PDU session of the management data (UE mgt data) transmission of the CPE or RSU terminal equipment, and the path passed by the dotted line with the arrow is used for the normal service data of the CPE or RSU terminal equipment (user data) transmitted PDU session.

At present, the CPE or RSU terminal equipment of each manufacturer is managed by the CPE or RSU terminal management system provided by each manufacturer. The CPE or RSU terminal capability (such as supported protocol type and version) is compatible with the management capability of the CPE or RSU terminal management system.

At present, the management of CPE and RSU equipment and the management of network elements are two independent management systems. As shown in Figure 2, UE mgt is used to manage CPE or RSU terminal equipment, and EMS is used to manage network elements (such as gNB) Yes, and the terminal equipment management entity UE mgt is based on the data plane path management scheme provided by the 3GPP network, which relies on end-to-end E2E (End to End) network resources, which consumes a lot of network resources, especially the core network UPF Therefore, in order to reduce resource consumption by CPE/RSU management and reduce network construction and maintenance costs, this application proposes a converged architecture for CPE/RSU management and wireless network elements. FIG. 3 shows a schematic diagram of an example of a converged architecture for communication management of wireless operation and maintenance terminals. Under this converged architecture, UEmgt can reuse the management channel of EMS for wireless network elements to realize the management of CPE or RSU terminal equipment, thereby saving 5G network resources, especially 5G core network resources.

Furthermore, since the radio access network element gNB can further perform functional splitting, that is, the gNB can be split into a centralized unit-control plane (centralized unit-control plane, CU-CP), a centralized unit-user plane (centralized unit-user plane) , CU-UP) and a distributed unit (distributed unit, DU), so the CPE/RSU management and wireless network element convergence architecture may also be the architecture shown in FIG. 4 .

FIG. 4 shows a schematic diagram of another example of a converged architecture for communication management of wireless operation and maintenance terminals. The key nodes involved in the architecture are briefly introduced below.

(1) UE: The UE mentioned in this application mainly refers to a terminal device capable of providing wireless network access functions for other common terminals, and in this paper mainly refers to a CPE or RSU.

(2) gNB is the wireless access network base station of the 5G NR network. It mainly provides wireless network access functions, including radio resource control (radio resource control, RRC) connection management, security, user data forwarding, data packet reassembly/fragmentation, Retransmission and other functions.

(3) The CU-CP mainly provides wireless connection management (that is, RRC connection management), security and other functions.

(4) CU-UP mainly provides user data packet encryption and decryption, integrity protection and other functions.

(5) DU mainly provides data packet reassembly/fragmentation, retransmission, channel management and other functions

(6) 5GC CNF refers to all control plane network elements of the 5G core network, including AMF, SMF, NEF, NWDAF, etc. These different 5GC control plane network elements are responsible for different network functions. For example, AMF is mainly responsible for UE authentication. SMF mainly provides session management functions such as IP address allocation and QoS management. NEF mainly provides the ability to open the 3GPP network to external service entities. NWDAF mainly provides the data analysis function of 5G core network. For more network element types and functions included in the 5GC CNF, please refer to the description in Section 6.2 of the 3GPP standard protocol TS 23.501.

(7) UPF is the user plane network element of the 5G core network, which mainly provides functions such as user plane data forwarding, billing statistics, and QoS execution.

(8) EMS is a network element management function. The EMS in Figure 3 of this application refers to the network element management system of the wireless network, which is responsible for performing the management of wireless access network equipment, including parameter configuration and performance management of wireless network elements. , fault alarm, etc. Among them, UE mgt is a terminal management function module newly added in EMS in order to realize the technical solution of this application. The main functions of this module are registration, parameter configuration, software upgrade, fault diagnosis, status and performance monitoring of terminal equipment such as CPE or RSU and other functions.

It should be noted that the 5GC core network may also have at least one corresponding core network element management system EMS, but the technical solution of this application does not involve the core network element management system, so in the architectures of Figures 3 and 4 The network element management system corresponding to the core network is not drawn, but this application does not limit it.

(9) NMS is a management system that provides cross-domain (such as cross-radio access network and core network) or cross-equipment vendor network equipment management in the operator's network. Its specific functions include parameter configuration, performance monitoring, and fault management of network equipment. Alarm and other functions.

Under the framework of wireless operation and maintenance and terminal management integration shown in Figure 3 or Figure 4, UE mgt is a unified terminal management function integrated in the wireless network element management system, not a terminal management that is matched with a certain manufacturer's terminal equipment The system manages all terminal devices within its coverage area based on the wireless network element management system and the unified management interface of the corresponding wireless network elements, including different manufacturers (terminal devices produced) and different types of terminal devices. However, different manufacturers and different types of terminals have the following characteristics:

(1) Different types of terminal equipment (such as CPE, RSU, AR module, etc.) correspond to different parameter types, which are used to indicate the type of configuration parameters required for the terminal equipment to provide wireless network access services;

(2) Terminal devices of different manufacturers support different protocol types of management protocols, such as TR-069, MQTT, LWM2M and other protocols;

(3) Terminal devices of different types or different manufacturers support different versions of the same protocol type management protocol, for example, some support the V1 version of the TR-069 protocol, and some support the V3 version of the TR-069 protocol.

For the above description, under the new architecture of wireless operation and maintenance and terminal management integration, the integrated terminal management system manages terminal devices of different types and manufacturers in a unified manner. Therefore, the parameter configuration method needs to be determined according to terminal device information, but wireless operation and maintenance and Before the convergence of terminal management, the solution that CPE/RSU and UE mgt were managed by the same manufacturer could not adapt to the changes brought about by the converged management architecture, and could not support correct parameter configuration of terminal devices. Then, under the converged architecture, how UE mgt implements parameter configuration for different manufacturers or types of terminal equipment through a unified management interface has become an urgent problem to be solved.

The terminal device management method 100 according to the embodiment of the present application will be described in detail below 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 the terminal device management entity. Correspondingly, the terminal device management entity receives the device type information from the terminal device, where the device type information is used to indicate the type of the terminal device.

It should be understood that the terminal device here is a terminal device that can provide wireless network access services for other terminal devices, and the type of the terminal device here may include CPE-type, RSU-type, or AR module-type, etc., respectively indicating that the terminal device is CPE, RSU or AR module.

S102. The terminal device management entity sends configuration parameters to the terminal device. Correspondingly, the terminal device receives configuration parameters from the terminal device management entity, where the configuration parameters are used for configuration of the terminal device.

It should be understood that the configuration parameters include the wireless network service set identifier (service set identifier, SSID) of the wireless network access service provided by the terminal device and the password corresponding to the SSID, the clock synchronization server Internet Protocol IP address, etc., and the configuration parameters also include other The parameter type is not limited in this application.

S103, the terminal device configures according to the configuration parameters.

In the above solution, the terminal device actively reports the device type information, and the terminal device management entity can send configuration parameters to the terminal device according to the device type information, so that the terminal device providing wireless network access service can perform parameter configuration. The integrated management system is obtained by integrating the terminal equipment management entity with the wireless network element management system. Through the integrated management system, the terminal equipment that provides wireless network access services can be managed without relying on end-to-end network resources and reducing the need for network resources. consumption, reducing network construction and maintenance costs.

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

Exemplarily, the terminal device management entity determines the parameter type according to the device type information, and the parameter type is used to indicate the type of configuration parameters required for the terminal device to provide wireless network access services, and the terminal device management entity determines the configuration parameters according to the parameter type.

Specifically, regarding S102, the terminal device management entity may send configuration parameters to the terminal device according to the protocol information received from the terminal device, or, further, the terminal device management entity may The level sends configuration parameters to the terminal device. The protocol information, the priority of the protocol information, and how the terminal device management entity sends the configuration parameters are respectively introduced below.

The protocol information includes one or more of the following: protocol type information or version information, the protocol type information is used to indicate the management protocol type supported by the terminal device, and the version information is used to indicate the version number of the management protocol type supported by the terminal device.

It should be understood that the management protocol type here may include TR-069protocol, MQTT protocol or LWM2Mprotocol and so on.

The priority information is used to indicate the priority of the protocol information, and the priority of the protocol information includes one or more of the following: the priority of the protocol type information or the priority of the version information; wherein, the terminal device management entity sends the terminal device Sending the configuration parameters includes: the terminal device management entity sends the configuration parameters to the terminal device according to the protocol information and the priority of the protocol information.

The terminal device management entity sends configuration parameters to the terminal device according to the protocol information received by the terminal device, and there are many possible implementations. 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 uses the management information to send configuration parameters to the terminal device according to the protocol information of the management protocol, specifically Reference may be made to the first possible implementation manner in method 200 and the first possible implementation manner in 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 it supports, and the terminal device management entity selects the target management protocol according to the protocol information to send configuration parameters to the terminal device, And the target protocol information will be sent to the terminal device, where the target protocol information is the protocol information corresponding to the aforementioned target management protocol. Further, the terminal device management entity may also send configuration parameters to the terminal device according to the protocol information and local policies, where the policy may be configured locally by the terminal device management entity or received from the NMS. For details, refer to the second One possible implementation and the first possible implementation in method 400, or, refer to the first possible implementation in method 300 and the second possible implementation in method 400 .

In the above solution, through the terminal device actively reporting device information and protocol information, the terminal device management entity can more quickly and accurately determine the type of configuration parameters required for the terminal device to provide wireless network access services.

The terminal device management entity sends configuration parameters to the terminal device according to the protocol information received by the terminal device and the priority of the protocol information, and there are many possible implementation manners. For example, when a terminal device supports multiple management protocols, the terminal device sends the protocol information and the priority of the protocol information of the multiple management protocols to the terminal device management entity, and the terminal device management entity selects the target according to the protocol information and the priority of the protocol information The management protocol sends configuration parameters to the terminal device, and sends target protocol information to the terminal device, where the target protocol information is the protocol information corresponding to the above target management protocol. Furthermore, the terminal device management entity can also send configuration parameters to the terminal device according to the protocol information, the priority of the protocol information, and the protocol capabilities supported by itself. For details, refer to the third possible implementation of method 200 and the second possible implementation of method 400. The second possible implementation manner, or, for details, refer to the second possible implementation manner in method 300 and the third possible implementation manner in method 400 .

In the above solution, the terminal device actively reports device information, protocol information, and protocol preference policy, so that the subsequent EMS can combine the information reported by the terminal device to more quickly and accurately determine the configuration parameters for the terminal device to provide wireless network access services. The type of the desired configuration parameter.

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; wherein, the protocol information includes multiple protocol type information, and the target protocol type information of the target protocol information is one of the multiple protocol type information or, the protocol information includes multiple protocol version information, and the target protocol version information of the target protocol information is one of multiple protocol version information; or, the protocol information includes multiple protocol type information and multiple protocol version information, and the target The target protocol type information of the protocol information is one of the multiple protocol type information, and the target protocol version information of the target protocol information is one of the multiple protocol version information.

The terminal device management method 200 according to the embodiment of the present application will be described in detail below with reference to FIG. 6 . FIG. 6 is a schematic interaction diagram of the method 200 of the present application.

FIG. 6 shows a plug and play (PnP, PnP) or management channel establishment process of a terminal device. Several possible implementations of the method 200 are introduced below.

First possible implementation:

In the scenario where the terminal device only supports one management protocol, the terminal device sends the device type information and protocol information of the terminal device to the integrated management system EMS during the PnP or management channel establishment process.

S201-S203 are RRC connection establishment procedures. The establishment of the RRC connection can occur after the UE is turned on. The UE searches for the wireless signal of the wireless network base station, selects and determines the cell to camp on based on the cell selection strategy, and establishes an RRC connection with the wireless network base station corresponding to the cell. The RRC connection establishment process is executed in accordance with the 3GPP standard protocol process, including:

S201, the UE initiates an RRC connection establishment request (RRC setup request) to the network side.

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

S203. After completing relevant configuration based on the RRC connection configuration information sent by the gNB, the UE returns an RRC connection setup completion confirmation message (RRC setup complete) to the gNB. The RRC setup complete includes PnP requested and UEID.

For the description of the detailed process of S201-S203, refer to Section 5.3.3 of 3GPP TS 38.331, which will not be repeated in this application.

After the UE completes the establishment of the RRC connection, the UE can carry the NAS request in the RRC setup complete message to implement specific service processing (such as the UE attach registration request, etc.).

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

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

S204. After receiving the RRC setup complete message request from the UE, the gNB triggers sending the UE's device registration information to the wireless network element management system based on the PnPrequested registration indication in S203. The message carries PnPrequested, UE ID, device type information, and protocol type information and version information.

Exemplarily, the gNB may send UE device registration information through a management channel with the wireless network element management system (such as through an operation, administration, and maintenance, OAM notification message), and the specific implementation of this step It can be implemented based on the private solution of the gNB equipment manufacturer, or can refer to the VES-based solution of the 3GPP standard protocol, OAM notification or StreamData Report method.

S205, UE information registration and maintenance.

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

S206, after the EMS completes the registration of the terminal device, it returns a registration response message through the management interface with the gNB, and the message includes the 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 of the terminal device (such as a data radio bearer (date radio bearer, DRB) or a signaling radio bearer (date radio bearer, SRB).

In the embodiment of the present application, the element management system (element management system, EMS) is integrated with the UE mgt to obtain the integrated management system, and the terminal equipment is managed through the integrated management system, which reduces the consumption of network resources and reduces the cost of network construction and maintenance . In the scenario where the terminal device only supports one management protocol, the terminal device actively reports the device information and capability information, so that the subsequent EMS can more quickly and accurately determine the type of configuration parameters required for the terminal device to provide wireless network access services . Second possible implementation:

In the scenario where a terminal device supports multiple types of management protocols or supports multiple versions of a management protocol, the terminal device sends the device type information of the terminal device it supports, and all the protocol types it supports in the PnP or management channel establishment process Information and version information are sent to the fusion management system EMS.

For details of S201-S207, refer to the description in the first possible implementation manner, where the difference lies in:

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 present application, the element management system (element management system, EMS) is integrated with the UE mgt to obtain the integrated management system, and the terminal equipment is managed through the integrated management system, which reduces the consumption of network resources and reduces the cost of network construction and maintenance . In the scenario where the terminal device supports multiple types of management protocols or multiple protocol versions, the terminal device actively reports the device information and capability information, so that the subsequent EMS can combine the information reported by the terminal device to determine the terminal device more quickly and accurately The type of configuration parameters required to provide wireless network access services.

A third possible implementation:

In the scenario where the terminal device supports multiple types of management protocols or supports multiple versions of a management protocol, the terminal device will support the device type information of the terminal device and all the protocol types it supports in the PnP or management channel establishment process and version information are sent to the integrated management system EMS, and at the same time, the terminal device also reports the preferred policy of the protocol.

For details of S201-S207, refer to the description in the second possible implementation manner, where the difference lies in:

The RRC setup complete message in S203 and the UE registration information in S204 also carry the priority corresponding to each type of protocol information/version information. This priority may be the priority selected for use by the protocol type information or version information.

As an example, the priority information may be in the form of {[TR069,high priority],[MQTT,lowpriority],[LWM2M,medium priority]}, which means that the terminal device supports TR069, MQTT and LWM2M management protocol type, and the priorities of the three protocols selected for use are TR069>MQTT>LWM2M. The priority information is sent to the EMS, so that the EMS can determine the target management protocol among all the management protocols supported by the UE in combination with its own capability information.

In the embodiment of the present application, the element management system (element management system, EMS) is integrated with the UE mgt to obtain the integrated management system, and the terminal equipment is managed through the integrated management system, which reduces the consumption of network resources and reduces the cost of network construction and maintenance . In the scenario where the terminal device supports multiple types of management protocols or multiple protocol versions, the terminal device actively reports the device information, capability information, and protocol preference policy, so that the subsequent EMS can combine the information reported by the terminal device to more quickly and accurately Determine the type of configuration parameters required for the terminal device to provide the wireless network access service.

The terminal device management method 300 according to the embodiment of the present application will be described in detail below with reference to FIG. 7 . FIG. 7 is a schematic interaction diagram of the method 300 of the present application.

FIG. 7 shows a plug and play (PnP, PnP) or management channel establishment process of a terminal device, and several possible implementations of the method 300 are introduced below.

First possible implementation:

In the scenario where a terminal device supports multiple types of management protocols or supports multiple versions of a management protocol, the terminal device sends the device type information of the terminal device it supports, and all the protocol types it supports in the PnP or management channel establishment process Information and version information are sent to the fusion management system EMS. When the terminal device PnP registers, the EMS determines the protocol type or version information of the management protocol to be adopted based on the local policy, and records this information, and then feeds back the selected information to the UE in the device registration response message to the gNB or UE , the UE records the information returned by the EMS.

For details of S301-S304, refer to the description of S201-S204 in the second possible implementation manner in the method 200.

S305. Select the protocol type and version of the management protocol.

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

At the same time, EMS determines the target management protocol from the protocol type information and/or multiple version information of multiple management protocols supported by the terminal device based on the EMS local configuration strategy, such as random selection or other automatic rules, that is, determines the target protocol information and/or target version information.

Several situations in which the EMS determines target protocol information and/or target version information are introduced below through several examples.

Exemplarily, 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 multiple protocol type information and multiple version information to the EMS, and the EMS selects the target protocol information and target version information based on a locally configured policy, and selects the management protocol corresponding to the target protocol information and target version information to communicate with the UE . Or, the UE sends multiple versions of information to the EMS, and the EMS selects target version information based on a locally configured policy, and selects a management protocol corresponding to the target version information to communicate with the UE.

S306. After the EMS completes the registration of the terminal device, it returns a UE registration response message through the management interface with the gNB, and the message includes the registration result (registration successful or registration failure), and the selected protocol type information and/or version information ( Namely 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 (ie selected protocol or selected version) to the UE through the air interface bearer of the terminal device (such as DRB or SRB).

S308, the UE receives the feedback from the EMS, and records the selected protocol type information or version information (that is, selectedprotocol or selected version). In order to facilitate 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 present application, the element management system (element management system, EMS) is integrated with the UE mgt to obtain the integrated management system, and the terminal equipment is managed through the integrated management system, which reduces the consumption of network resources and reduces the cost of network construction and maintenance . In the scenario where the terminal device supports multiple types of management protocols or multiple protocol versions, through the terminal device actively reporting device information and capability information, EMS can determine the terminal device more quickly and accurately by combining the information reported by the terminal device and local policies The type of configuration parameters required to provide wireless network access services.

Second possible implementation:

In the scenario where a terminal device supports multiple types of management protocols or supports multiple versions of a management protocol, the terminal device sends the device type information of the terminal device it supports, and all the protocol types it supports in the PnP or management channel establishment process Information and version information are sent to the integrated management system EMS, and at the same time, the terminal device also reports the preferred policy of the protocol. When the terminal device PnP registers, the EMS determines the protocol type or version information of the management protocol to be adopted based on the protocol capabilities it supports and the preferred strategy of the terminal device, and records this information, and then sends a device registration response message to the gNB or UE Feeds back the selected information to the UE, and the UE records the information returned by the EMS.

For details of S301-S304, refer to the description of S201-S204 in the third possible implementation manner in the method 200.

S305. Select the protocol type and version of the management protocol.

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

At the same time, the EMS determines the target management protocol from the protocol type information and/or multiple version information of multiple management protocols supported by the terminal device based on the protocol capabilities supported by itself and the preferred strategy of the terminal device, that is, determines the target protocol information and/or Target version information.

Several situations in which the EMS determines target protocol information and/or target version information are introduced below through several examples.

Example 1, the UE sends multiple protocol type information to the EMS, and the EMS determines the target protocol information based on a locally configured policy, and selects the management protocol corresponding to the target protocol information to communicate with the UE. Or, in Example 2, the UE sends multiple protocol type information and multiple version information to the EMS, and the EMS selects the target protocol information and target version information based on a locally configured policy, and selects the management protocol corresponding to the target protocol information and target version information. UEs communicate. Or, in Example 3, the UE sends multiple versions of information to the EMS, and the EMS selects target version information based on a locally configured policy, and selects a management protocol corresponding to the target version information to communicate with the UE.

The following takes the above example 1 as an example to describe in detail how the EMS obtains the protocol type information of multiple management protocols supported by the terminal device based on the protocol capabilities supported by itself and the preferred strategy of the terminal device.

Exemplarily, the priority information may be in the form of {[TR069, high priority], [MQTT, low priority], [LWM2M, medium priority]}, which means that the terminal device supports TR069, MQTT and LWM2M management protocol type, and the priorities of the three protocols selected for use are TR069>MQTT>LWM2M. The priority information is sent to the EMS, so that the EMS can determine the target management protocol among all the management protocols supported by the UE in combination with its own capability information. Assuming that EMS (UE mgt) only supports MQTT and LWM2M management protocols, EMS (UE mgt) refers to the selection priority of terminal equipment for each management protocol (that is, the selection priority of MQTT is low priority, but the selection priority of LWM2M2 is Medium priority), and finally select the LWM2M management protocol with medium priority to perform protocol processing on the configuration parameters.

For details of S306-S308, refer to the description corresponding to the first possible implementation manner of the method 300.

In the embodiment of the present application, the element management system (element management system, EMS) is integrated with the UE mgt to obtain the integrated management system, and the terminal equipment is managed through the integrated management system, which reduces the consumption of network resources and reduces the cost of network construction and maintenance . In the scenario where the terminal device supports multiple types of management protocols or multiple protocol versions, through the terminal device actively reporting device information, capability information and protocol optimization strategy, EMS can combine the information reported by the terminal device and its own capabilities to more quickly and accurately Determine the type of configuration parameters required for the terminal device to provide the wireless network access service.

The terminal device management method 400 according to the embodiment of the present application will be described in detail below with reference to FIG. 8 . FIG. 8 is a schematic interaction diagram of a method 400 of the present application.

Figure 8 shows the terminal device parameter configuration process, which is two independent processes with the terminal device PnP device registration process shown in Figure 6 and Figure 7, and only after the terminal device starts and completes the PnP device registration process, the management system Only then can the parameter configuration process be initiated to configure the parameters of the terminal device. However, the parameter configuration process is not triggered immediately after the PnP device registration process is completed. Therefore, the method 400 of the embodiment of the present application can be combined with 200 or 300, and the method 200 or 300 is executed before 400, but it is not limited to execute 400 immediately after the method 200 or 300 is executed.

Several possible implementations of the method 400 are introduced below.

First possible implementation:

Before method 400, the EMS has acquired the UE's device type information and the protocol type information and/or version information of the management protocol used for subsequent parameter configuration, and the EMS is based on the terminal type information, protocol type information, and version information in the parameter configuration process Determine the template and protocol processing mode for parameter configuration, and send configuration parameters to the UE based on the protocol processing mode.

It should be understood that, depending on how method 400 is combined with method 200 or 300, the EMS can obtain terminal type information, protocol type information, and version information in various ways, and several possible combination ways are introduced below.

method one:

Combined with the first possible implementation of method 200, in the scenario where the terminal device only supports one management protocol, the EMS receives the device type information, protocol information, etc. of the terminal device during the PnP or management channel establishment process and sends them to the integrated management System EMS.

S401, when the EMS (UE mgt) performs parameter configuration on the terminal device, it determines the type of the terminal device based on the terminal device type information, thereby determining its corresponding parameter type, and the parameter type is used to instruct the UE to provide wireless network for other terminal devices The type of configuration parameters required to access the service, based on the protocol information (including protocol type information and/or version information), determine the target management protocol used when sending the configuration parameters to the UE, and follow the processing method of the target management protocol (such as message format , parameter format) to model the configuration parameters (including encapsulating the configuration parameters according to the parameter object format of the protocol).

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

It should be understood that under the converged architecture, the UE mgt can reuse the management channel of the EMS to the wireless network element, so as to realize the management of terminal equipment such as CPE or RSU. Since the EMS manages the gNB by incorporating various parameters of the gNB into the model for management, the EMS (UE mgt) in the embodiment of the present application may also incorporate various configuration parameters of the UE into the model for management.

S402. The EMS sends UE configuration information to the gNB.

After the EMS (UE mgt) completes the configuration parameter modeling, it sends the configuration parameters after the modeling process in S401 according to the target management protocol to the gNB through the management interface message with the gNB, and the message carries the configured terminal device identifier UEID or UE IP, and configuration information (Config info) for the configuration parameters of the terminal device. The Config info may include the wireless network service set identifier (service setidentifier, SSID) of the wireless network access service provided by the terminal device and the password corresponding to the SSID , clock synchronization server IP address and other parameter information customized by the manufacturer.

As an example, the above-mentioned management interface message may be the CreateMOI interface message defined by the 3GPP standard, then the corresponding terminal device identification UE ID or UE IP and the configuration parameter Config info for the terminal device should be constructed according to the information model supporting the CreateMOI interface message For example, in the embodiment of the present application, the terminal device parameter configuration resource model DeviceConfig information object class (information object class, IOC) can be defined as Table 1. Table 1 shows the DeviceConfig IOC parameter attributes, that is, the first column in Table 1 is the parameter name of the configuration parameters of the UE, and the second column is the corresponding parameter function.

Table 1

parameter name parameter function UE ID terminal equipment identification ConfigFile Manufacturer-defined parameters NTPServer Clock synchronization server name or IP address SSID The network identifier of the wireless network service provided by the terminal device

It should be noted that the above-mentioned 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, and obtains the UE identification and configuration parameters (that is, the parameter information in Table 1) and matches them for transmitting the terminal device based on the UE ID or UE IP Manage the air interface bearer of data (such as data radio bearer/DRB or signaling radio bearer/SRB).

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

S405. After receiving the configuration information, the UE parses the message parameters based on the corresponding terminal device management protocol, and performs corresponding parameter configuration.

In the embodiment of the present application, the element management system (element management system, EMS) is integrated with the UE mgt to obtain the integrated management system, and the terminal equipment is managed through the integrated management system, which reduces the consumption of network resources and reduces the cost of network construction and maintenance . In the scenario where the terminal device supports only one management protocol, the EMS can more quickly and accurately determine the type of configuration parameters required for the terminal device to provide wireless network access services based on the device information and capability information actively reported by the terminal device and execute The corresponding parameter configuration process.

Method 2:

Combined with the first possible implementation of method 300, in the scenario where the terminal device supports multiple types of management protocols or supports multiple versions of a management protocol, the EMS receives the terminal device support protocol during the PnP or management channel establishment process. The device type information of the terminal device, all the management protocol type information and version information it supports, etc., determine the protocol type information or version information of the management protocol to be adopted based on the local policy, and record these information.

For details of S401-S405, refer to the corresponding description in the first method.

In the embodiment of the present application, the element management system (element management system, EMS) is integrated with the UE mgt to obtain the integrated management system, and the terminal equipment is managed through the integrated management system, which reduces the consumption of network resources and reduces the cost of network construction and maintenance . In the scenario where the terminal device supports multiple types of management protocols or multiple protocol versions, the terminal device actively reports the device information and capability information, and the EMS combines the information reported by the terminal device and local policies to more quickly and accurately determine the information provided by the terminal device. The type of configuration parameters required by the wireless network access service and execute the corresponding parameter configuration process.

Method 3:

Combined with the second possible implementation of method 300, in the scenario where the terminal device supports multiple types of management protocols or supports multiple versions of a management protocol, the EMS receives the information supported by the UE during the PnP or management channel establishment process. The device type information of the terminal device, all the protocol type information and version information it supports, and the preferred strategy of the protocol, and determine the protocol type information or version information of the management protocol to be adopted based on the protocol capabilities supported by itself and the preferred strategy of the terminal device, and record this information.

For details of S401-S405, refer to the corresponding description in the first method.

In the embodiment of the present application, the element management system (element management system, EMS) is integrated with the UE mgt to obtain the integrated management system, and the terminal equipment is managed through the integrated management system, which reduces the consumption of network resources and reduces the cost of network construction and maintenance . In the scenario where the terminal device supports multiple types of management protocols or multiple protocol versions, through the terminal device actively reporting device information, capability information and protocol optimization strategy, EMS can combine the information reported by the terminal device and its own capabilities to more quickly and accurately Determine the type of configuration parameters required by the terminal device to provide the wireless network access service and execute a corresponding parameter configuration process.

Second possible implementation:

Before method 400, the EMS has acquired the UE's device type information, but has not yet determined the protocol information of the management protocol used for subsequent parameter configuration. In the parameter configuration process, the EMS first selects the protocol information of the target management The type information and protocol information determine the template for parameter configuration and the protocol processing method, and send the configuration parameters to the UE based on the protocol processing method.

It should be understood that, depending on the combination of method 400 and method 200, the EMS can obtain device type information and protocol information in various ways, and several possible combination ways are introduced below.

method one:

Combined with the second possible implementation of method 200, in the scenario where the terminal device supports multiple types of management protocols or supports multiple versions of a management protocol, the EMS receives the terminal supported by the UE in the PnP or management channel establishment process The device type information of the device, all supported protocol type information and/or version information, etc. are sent to the integrated management system EMS, and the EMS (UE mgt) determines the adopted protocol type information and version information based on the local configuration policy during parameter configuration, and based on The determined protocol type and version are processed by parameter modeling. At the same time, the selected protocol type and version information are returned to the terminal device in the parameter configuration process.

For details of S401-S405, please refer to the description corresponding to S401-S405 in the first possible implementation of method 400, the difference is:

In S401, before the EMS determines the protocol processing mode, it also needs to determine the target management protocol to be used when sending the configuration parameters subsequently from the multiple management protocols supported by the terminal device. Specifically, the EMS selects the protocol type information and/or version information of the target management protocol to be used based on a policy locally configured by the EMS, such as random selection or other automatic rules.

Several situations in which the EMS determines target protocol information and/or target version information are introduced below through several examples.

Exemplarily, 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 multiple protocol type information and multiple version information to the EMS, and the EMS selects the target protocol information and target version information based on a locally configured policy, and selects the management protocol corresponding to the target protocol information and target version information to communicate with the UE . Or, the UE sends multiple versions of information to the EMS, and the EMS selects target version information based on a locally configured policy, and selects a management protocol corresponding to the target version information to communicate with the UE.

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, and 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 present application, the element management system (element management system, EMS) is integrated with the UE mgt to obtain the integrated management system, and the terminal equipment is managed through the integrated management system, which reduces the consumption of network resources and reduces the cost of network construction and maintenance . In the scenario where the terminal device supports multiple types of management protocols or multiple protocol versions, EMS can more quickly and accurately determine the configuration required for the terminal device to provide wireless network access services according to the device information and capability information actively reported by the terminal device The type of the parameter and execute the corresponding parameter configuration process.

Method 2:

Combined with the third possible implementation of method 200, in the scenario where the terminal device supports multiple types of management protocols or supports multiple versions of a management protocol, the EMS receives the terminal supported by the UE in the PnP or management channel establishment process The device type information of the device, all supported protocol type information and version information are sent to the integrated management system EMS, and at the same time, the protocol preference policy sent by the UE is also received. The integrated management system EMS (UE mgt) determines the type or version of the management protocol adopted based on the protocol capabilities supported by the EMS (UE mgt) itself and the preferred strategy of the terminal device during parameter configuration, and performs parameterization based on the determined protocol type and version. The modeling process, and returns selected protocol information to the end device during the configuration process.

For details of S401-S405, please refer to the description corresponding to S401-S405 in the first possible implementation of the second possible implementation of the method 400, the difference is:

In S401, because in the third possible implementation of method 200, the UE sends the preferred policy of the protocol to the EMS, so the EMS refers to the type of management protocol supported by itself when selecting the target management protocol, and refers to the preferred strategy.

As an example, the priority information may be in the form of {[TR069,high priority],[MQTT,lowpriority],[LWM2M,medium priority]}, which means that the terminal device supports TR069, MQTT and LWM2M management protocol type, and the priorities of the three protocols selected for use are TR069>MQTT>LWM2M. The priority information is sent to the EMS, so that the EMS can determine the target management protocol among all the management protocols supported by the UE in combination with its own capability information. Assuming that EMS (UE mgt) only supports MQTT and LWM2M management protocols, EMS (UE mgt) refers to the selection priority of terminal equipment for each management protocol (that is, the selection priority of MQTT is low priority, but the selection priority of LWM2M2 is Medium priority), and finally select the LWM2M management protocol with medium priority to perform protocol processing on the configuration parameters.

In the embodiment of the present application, the element management system (element management system, EMS) is integrated with the UE mgt to obtain the integrated management system, and the terminal equipment is managed through the integrated management system, which reduces the consumption of network resources and reduces the cost of network construction and maintenance . In the scenario where the terminal device supports multiple types of management protocols or multiple protocol versions, the EMS can combine the device information, capability information and protocol preference policy reported by the terminal device to more quickly and accurately determine that the terminal device provides wireless network access services Types of required configuration parameters and execute the corresponding parameter configuration process.

Above, the method provided by the embodiment of the present application is described in detail with reference to FIG. 1 to FIG. 8 . Hereinafter, the device provided by the embodiment of the present application will be described in detail with reference to FIG. 9 to FIG. 10 .

FIG. 9 is a schematic block diagram of a communication apparatus for terminal device management provided by 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 .

Wherein, the transceiver module 11 can be used for receiving information sent by other devices, and can also be used for sending information to other devices. For example, receiving device type messages or sending configuration parameters. The processing module 12 may be used to perform content processing of the device, such as determining configuration parameters.

In a possible design, the communication device 10 may correspond to the terminal device in the foregoing method embodiments.

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

Exemplarily, 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 S103.

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

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

Exemplarily, when the communication device 10 corresponds to the UE in the method 400, the transceiving 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 equipment management entity in the above method embodiment, or UE mgt, or EMS, or a fusion system of EMS and UEmgt.

Specifically, the communication device 10 may correspond to the terminal equipment management entity in any one of the methods 100 to 400 according to the embodiment of the present application, or UE mgt, or EMS, or a fusion system of EMS and UEmgt, the communication device 10 may include a module for performing operations performed by a terminal equipment management entity, or UE mgt, or EMS, or a fusion system of EMS and UE mgt in a corresponding method, and each unit in the communication device 10 is used to implement the corresponding In the method, operations performed by a terminal equipment management entity, or UE mgt, or EMS, or a fusion system of EMS and UEmgt.

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

Exemplarily, when the communication device 10 corresponds to UE mgt, or EMS, or a fusion system of EMS and UEmgt in method 200, the transceiver module 11 is used to perform steps S204 and S206, and the processing module 12 is used to perform step S205.

Exemplarily, when the communication device 10 corresponds to UE mgt, or EMS, or a fusion system of EMS and UEmgt in method 300, the transceiver module 11 is used to perform steps S304 and S306, and the processing module 12 is used to perform step S305.

Exemplarily, when the communication device 10 corresponds to UE mgt, or EMS, or a fusion system of EMS and UEmgt in the method 400, the transceiver module 11 is used to perform step S402, and the processing module 12 is used to perform step S401.

FIG. 10 is a schematic diagram of an apparatus 20 for terminal device management provided by an embodiment of the present application.

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

In a possible design, the device 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 wireless modems, and various forms of A terminal, mobile station, terminal, user equipment, soft terminal, etc. may also be a chip or a chip system on a terminal device.

The device 20 may include a processor 21 (ie, an example of a processing module) and a memory 22 . The memory 22 is used to store instructions, and the processor 21 is used to execute the instructions stored in the memory 22, so that the device 20 realizes the execution of the equipment in the above-mentioned various possible designs in the corresponding methods as shown in Fig. 5 to Fig. 8 step.

Further, the device 20 may also include an input port 23 (ie, an example of a transceiver module) and an output port 24 (ie, another example of a transceiver module). Further, the processor 21 , the memory 22 , the input port 23 and the output port 24 can communicate with each other through internal connection paths, and transmit control and/or data signals. The memory 22 is used to store a computer program, and the processor 21 can be used to call and run the computer program from the memory 22, to control the input port 23 to receive signals, and to control the output port 24 to send signals, so as to complete the terminal equipment or Steps of the radio access network device or UE or base station. The memory 22 can be integrated in the processor 21 or can be set separately from the processor 21 .

Optionally, if the message transmission device 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 they are the same physical entity, they can be collectively referred to as transceivers.

Optionally, 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, the functions of the input port 23 and the output port 34 may be realized by a transceiver circuit or a dedicated chip for transceiver. The processor 21 may be realized by a dedicated processing chip, a processing circuit, a processor or a general-purpose chip.

As another implementation manner, it may be considered to use a general-purpose computer to implement the device provided in the embodiment of the present application. The program codes to realize the functions of the processor 21 , the input port 23 and the output port 24 are stored in the memory 22 , and the general processor realizes the functions of the processor 21 , the input port 23 and the output port 24 by executing the codes in the memory 22 .

Wherein, each module or unit in the apparatus 20 can be used to execute each action or process performed by the device (for example, terminal device) performing random access in the above method, and here, in order to avoid redundant description, its detailed description is omitted.

For the concepts, explanations, detailed descriptions and other steps involved in the device 20 related to the technical solutions provided by the embodiments of the present application, please refer to the foregoing methods or descriptions of these contents in other embodiments, and details are not repeated here.

It should be understood that in the embodiment of the present application, the processor may be a central processing unit (CPU, central processing unit), and the processor may also be other general-purpose processors, digital signal processors (DSP, digital signal processors), application specific integrated circuits ( Application specific integrated circuit (ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. 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 also provides a computer-readable storage medium, on which computer instructions for implementing the method performed 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, when the computer program is executed by a computer, the computer can implement the methods performed by the terminal device management entity or the terminal device in the foregoing method embodiments.

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

For example, when the computer program is executed by a computer, the computer can implement the methods performed by the terminal device management entity or the terminal device in the foregoing method embodiments.

It should also be understood that the memory in the embodiments of the present application may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories. Among them, the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory. Volatile memory can be random access memory (RAM), which acts as external cache memory. By way of illustration and 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 (synchronous DRAM, SDRAM), dual Double data rate synchronous dynamic random access memory (double data rate SDRAM, DDRSDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synchlink DRAM, SLDRAM) and direct memory bus Random access memory (direct rambusRAM, DR RAM).

The above-mentioned embodiments may be implemented in whole or in part by software, hardware, firmware or other arbitrary combinations. When implemented using software, the above-described embodiments may be implemented in whole or in part in the form of computer program products. The computer program product comprises one or more computer instructions or computer programs. When the computer instruction or computer program is loaded or executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server or data center by wired (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center that includes one or more sets of available media. The available media may be magnetic media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, DVD), or semiconductor media. The semiconductor medium may be a solid state drive.

It should be understood that the term "and/or" in this article is only an association relationship describing associated objects, which means that there may be three relationships, for example, A and/or B may mean: A exists alone, and A and B exist at the same time , there are three cases of B alone. In addition, the character "/" in this article generally indicates that the contextual objects are an "or" relationship.

It should be understood that, in various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the order of execution, and the execution order of the processes should be determined by their functions and internal logic, and should not be used in the embodiments of the present application. The implementation process constitutes any limitation.

Those skilled in the art can appreciate that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

Those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

If the functions described above are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other various media that can store program codes. .

The above is only a specific implementation of the application, but the scope of protection of the application is not limited thereto. Anyone familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the application. Should be covered within the protection scope of this application. Therefore, the protection scope of the present application should be determined by the protection scope of the claims.

Claims (32)

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,

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.

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,

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.

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,

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.

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.

Images