Method and apparatus for managing terminal devices

Abstract

The application provides a method and device for managing terminal equipment, the method comprising: a terminal equipment for providing wireless network access service sending equipment type information to a terminal equipment management entity, the equipment type information being used for indicating the type of the terminal equipment; the terminal equipment management entity sending configuration parameters to the terminal equipment, the configuration parameters being determined according to the equipment type information, the configuration parameters being used for the configuration of the terminal equipment; and the terminal equipment being configured according to the configuration parameters. The method and device for managing terminal equipment provided by the application can make the terminal equipment management entity send configuration parameters to the terminal equipment according to the equipment type information reported by the terminal equipment, so that the terminal equipment for providing wireless network access service can perform parameter configuration, the terminal equipment management entity can manage the terminal equipment without relying on end-to-end network resources, the consumption of network resources is reduced, and the network construction and maintenance cost is reduced.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communication, and more particularly, to a terminal device management method and apparatus. BACKGROUND

[0002] Currently, a user equipment management (UE mgt) based on a management scheme of a data plane path provided by a 3rd generation partnership project (3GPP) network is used to manage customer-premises equipment (CPE), road side unit (RSU) and other terminal devices. The management of the UE mgt on the terminal device relies on end to end (E2E) network resources, which consumes a large amount of network resources, especially the resources of a core network user plane function (UPF), thereby requiring a large amount of network construction and maintenance costs. Therefore, how to reduce the consumption of network resources when managing CPE / RSU and other terminal devices and reduce network construction and maintenance costs is a problem to be solved. SUMMARY

[0003] The present application provides a terminal device management method and apparatus, which can reduce the consumption of network resources and reduce network construction and maintenance costs.

[0004] In a first aspect, a terminal device management method is provided, comprising: receiving, by a terminal device management entity, device type information from a terminal device, the device type information being used to indicate a type of the terminal device, the terminal device being used to provide a wireless network access service; and sending, by the terminal device management entity, configuration parameters to the terminal device, the configuration parameters being determined according to the device type information, the configuration parameters being used for configuration of the terminal device.

[0005] The above scheme, by actively reporting the device type information by the terminal device, 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 the wireless network access service can perform parameter configuration, so that the terminal device management entity can manage the terminal device without relying on end to end network resources, reduce the consumption of network resources, and reduce network construction and maintenance costs.

[0006] In combination with the first aspect, in some implementations of the first aspect, the method further comprises: determining, by the terminal device management entity, the configuration parameters according to the device type information.

[0007] In some implementations of the first aspect, the terminal device management entity determines the configuration parameter according to the device type information, including: the terminal device management entity determines a parameter type according to the device type information, the parameter type being used to indicate a type of the configuration parameter required by the terminal device to provide the wireless network access service; and the terminal device management entity determines the configuration parameter according to the parameter type.

[0008] In some implementations of the first aspect, the method further includes:

[0009] The terminal device management entity receives protocol information from the terminal device, the protocol information including one or more of: protocol type information used to indicate a type of management protocol supported by the terminal device, or version information used to indicate a version number of the type of management protocol supported by the terminal device; and 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.

[0010] The above scheme enables the terminal device management entity to more quickly and accurately determine the type of the configuration parameter required by the terminal device to provide the wireless network access service, by the terminal device actively reporting the device information and the protocol information.

[0011] In some implementations 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 target protocol information, the target protocol information including one or more of: target protocol type information or target version information; the protocol information includes a plurality of protocol type information, the target protocol type information of the target protocol information being one of the plurality of protocol type information; or the protocol information includes a plurality of protocol version information, the target protocol version information of the target protocol information being one of the plurality of protocol version information; or the protocol information includes a plurality of protocol type information and a plurality of protocol version information, the target protocol type information of the target protocol information being one of the plurality of protocol type information, and the target protocol version information of the target protocol information being one of the plurality of protocol version information.

[0012] In some implementations of the first aspect, the method further includes: the terminal device management entity sends the target protocol information to the terminal device.

[0013] In some implementations of the first aspect, the method further includes: receiving, by the device management entity, priority information from the terminal device, the priority information being used to indicate a priority of the protocol information, the priority of the protocol information including one or more of: a priority of the protocol type information or a priority of the version information; and transmitting, by the device management entity, the configuration parameter to the terminal device according to the protocol information, including: transmitting, by the device management entity, the configuration parameter to the terminal device according to the protocol information and the priority of the protocol information.

[0014] The above scheme enables the terminal device management entity to determine the type of the configuration parameter required by the terminal device for providing wireless network access service more quickly and accurately by actively reporting the device information, the protocol information and the protocol preference strategy by the terminal device.

[0015] In some implementations of the first aspect, transmitting, by the device management entity, the configuration parameter to the terminal device according to the protocol information includes: transmitting, by the device management entity, the configuration parameter to the terminal device according to the protocol information and the strategy.

[0016] In some implementations of the first aspect, the configuration parameter includes a wireless network service set identifier (SSID) of the wireless network access service provided by the terminal device and a password corresponding to the SSID, an Internet Protocol (IP) address of a clock synchronization server, and the like, and the configuration parameter can further include other parameter types, which are not limited in the present application.

[0017] The second aspect provides a management method of a terminal device, including: transmitting, by a terminal device, device type information to a terminal device management entity, the protocol type information being used to indicate a management protocol type supported by the terminal device, the terminal device being used to provide wireless network access service; receiving, by the terminal device, a configuration parameter from the terminal device management entity, the configuration parameter being used for configuration of the terminal device, the configuration parameter being determined according to the device type information; and configuring, by the terminal device, according to the configuration parameter.

[0018] The above scheme enables the terminal device management entity to transmit the configuration parameter to the terminal device according to the device type information, so that the terminal device providing wireless network access service can perform parameter configuration, and the terminal device management entity can manage the terminal device without relying on end-to-end network resources, thereby reducing consumption of network resources and reducing network construction and maintenance costs.

[0019] With reference to the second aspect, in some implementations of the second aspect, the method further includes: sending, by the terminal device, protocol information to the terminal device management entity, the protocol information including one or more of: protocol type information indicating a type of management protocol supported by the terminal device, or version information indicating a version number of the type of management protocol supported by the terminal device.

[0020] The above scheme enables the terminal device to actively report device information and protocol information, so that the terminal device management entity can more quickly and accurately determine the type of configuration parameter required by the terminal device to provide wireless network access services.

[0021] With reference to the second aspect, in some implementations of the second aspect, the method further includes: receiving, by the terminal device, target protocol information from the terminal device management entity, the target protocol information including one or more of: target protocol type information or target version information; wherein the protocol information includes a plurality of protocol type information, the target protocol type information of the target protocol information being one of the plurality of protocol type information; or the protocol information includes a plurality of protocol version information, the target protocol version information of the target protocol information being one of the plurality of protocol version information; or the protocol information includes a plurality of protocol type information and a plurality of protocol version information, the target protocol type information of the target protocol information being one of the plurality of protocol type information, and the target protocol version information of the target protocol information being one of the plurality of protocol version information.

[0022] With reference to the second aspect, in some implementations of the second aspect, the method further includes: sending, by the terminal device, priority information to the terminal device management entity, the priority information indicating a priority of the protocol information, the priority of the protocol information including one or more of: a priority of the protocol type information or a priority of the version information.

[0023] The above scheme enables the terminal device to actively report device information, protocol information, and protocol preference strategy, so that the terminal device management entity can subsequently determine the type of configuration parameter required by the terminal device to provide wireless network access services based on the information reported by the terminal device.

[0024] With reference to the second aspect, in some implementations of the second aspect, the configuration parameter includes a wireless network service set identifier (SSID) of wireless network access services provided by the terminal device, a password corresponding to the SSID, an Internet Protocol (IP) address of a clock synchronization server, and the like, and the configuration parameter can include other parameter types, which are not limited by the present disclosure.

[0025] In a third aspect, a terminal device management apparatus is provided, comprising: a transceiver configured to receive device type information from a terminal device, the device type information being used to indicate a type of the terminal device, the terminal device being configured to provide a wireless network access service; and the transceiver is further configured to send configuration parameters to the terminal device, the configuration parameters being determined according to the device type information, the configuration parameters being used for configuration of the terminal device.

[0026] According to the above scheme, the terminal device actively reports the device type information, and the terminal device management entity can send the configuration parameters to the terminal device according to the device type information, so that the terminal device providing the wireless network access service can perform parameter configuration, and the terminal device management entity can manage the terminal device without relying on end-to-end network resources, thereby reducing consumption of network resources and reducing network construction and maintenance costs.

[0027] In some implementations of the third aspect, the apparatus further comprises a processing module configured to determine the configuration parameters according to the device type information.

[0028] In some implementations of the third aspect, the processing module is specifically configured to determine a parameter type according to the device type information, the parameter type being used to indicate a type of the configuration parameters required by the terminal device to provide the wireless network access service; and the processing module is further specifically configured to determine the configuration parameters according to the parameter type.

[0029] In some implementations of the third aspect, the transceiver is configured to receive protocol information from the terminal device, the protocol information comprising one or more of the following: protocol type information or version information, the protocol type information being used to indicate a type of a management protocol supported by the terminal device, and the version information being used to indicate a version number of the type of the management protocol supported by the terminal device; and the processing module is specifically configured to send the configuration parameters to the terminal device according to the protocol information.

[0030] In some implementations of the third aspect, the processing module is specifically configured to send the configuration parameters to the terminal device according to target protocol information, the target protocol information comprising 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, the target protocol type information of the target protocol information being one of the plurality of protocol type information; or the protocol information comprises a plurality of protocol version information, the target protocol version information of the target protocol information being 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 being one of the plurality of protocol type information, and the target protocol version information of the target protocol information being one of the plurality of protocol version information.

[0031] In some implementations of the third aspect, the transceiver module is further configured to send the target protocol information to the terminal device.

[0032] In some implementations of the third aspect, the transceiver module is further configured to receive priority information from the terminal device, the priority information being used to indicate a priority of the protocol information, the priority of the protocol information including one or more of a priority of the protocol type information or a priority of the version information; and 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.

[0033] In some implementations of the third aspect, the processing module is further configured to send the configuration parameter to the terminal device according to the protocol information and a policy.

[0034] In some implementations of the third aspect, the configuration parameter includes a wireless network service set identifier (SSID) of a wireless network access service provided by the terminal device and a password corresponding to the SSID, an Internet Protocol (IP) address of a clock synchronization server, and the like, and the configuration parameter can further include other parameter types, which are not limited in the present application.

[0035] A fourth aspect provides a management apparatus of a terminal device, including: a transceiver module configured to send device type information to a terminal device management entity, the protocol type information being used to indicate a management protocol type supported by the terminal device, the terminal device being configured to provide a wireless network access service; the transceiver module being configured to receive a configuration parameter from the terminal device management entity, the configuration parameter being used for configuration of the terminal device, the configuration parameter being determined according to the device type information; and a processing module configured to perform configuration according to the configuration parameter.

[0036] The above scheme enables the terminal device to actively report the device type information, and the terminal device management entity can send a configuration parameter to the terminal device according to the device type information, so that the terminal device providing the wireless network access service can perform parameter configuration, and the terminal device management entity can manage the terminal device without relying on end-to-end network resources, thereby reducing consumption of network resources and reducing network construction and maintenance costs.

[0037] In some implementations of the fourth aspect, the transceiver module is configured to send protocol information to the terminal device management entity, the protocol information including one or more of protocol type information or version information, the protocol type information being used to indicate a management protocol type supported by the terminal device, and the version information being used to indicate a version number of the management protocol type supported by the terminal device.

[0038] In some implementations of the fourth aspect, in combination with the fourth aspect, the transceiver is configured to receive target protocol information from the terminal device management entity, the target protocol information including one or more of target protocol type information or target version information; the protocol information includes a plurality of protocol type information, the target protocol type information of the target protocol information being one of the plurality of protocol type information; or the protocol information includes a plurality of protocol version information, the target protocol version information of the target protocol information being one of the plurality of protocol version information; or the protocol information includes a plurality of protocol type information and a plurality of protocol version information, the target protocol type information of the target protocol information being one of the plurality of protocol type information, and the target protocol version information of the target protocol information being one of the plurality of protocol version information.

[0039] In some implementations of the fourth aspect, in combination with the fourth aspect, the transceiver is further configured to send priority information to the terminal device management entity, the priority information being used to indicate a priority of the protocol information, the priority of the protocol information including one or more of a priority of protocol type information or a priority of version information.

[0040] In some implementations of the fourth aspect, in combination with the fourth aspect, the configuration parameters include a wireless network service set identifier (SSID) of a wireless network access service provided by the terminal device, a password corresponding to the SSID, an Internet Protocol (IP) address of a clock synchronization server, and the like, and the configuration parameters further include other parameter types, which are not limited in the present application.

[0041] In a fifth aspect, a communication apparatus is provided, including a processor and a memory; the memory is configured to store a computer program; the processor is configured to execute the computer program stored in the memory, so that the communication apparatus executes the communication method of the first aspect or the second aspect.

[0042] In a sixth aspect, a computer readable storage medium is provided, the computer readable storage medium storing a computer program, when the computer program is executed on a computer, the computer program causes the computer to execute the communication method of the first aspect or the second aspect.

[0043] In a seventh aspect, a chip system is provided, including a processor configured to call and execute a computer program from a memory, so that a communication device installed with the chip system executes the communication method of the first aspect or the second aspect.

[0044] In an eighth aspect, a management system of a terminal device is provided, comprising a terminal device and a terminal device management entity, wherein the terminal device management entity is configured to perform the method according to any one of the first aspect and possible implementation manners of the first aspect, and the terminal device is configured to perform the method according to any one of the second aspect and possible implementation manners of the second aspect.

[0045] In a ninth aspect, a management system of a terminal device is provided, comprising a terminal device management entity and a radio access network device, wherein the terminal device management entity is configured to perform the method according to any one of the first aspect and possible implementation manners of the first aspect, and the radio access network device is configured to receive device type information from the terminal device and forward the device type information to the terminal device management entity, and further configured to receive configuration parameters from the terminal device management entity and forward the configuration parameters to the terminal device. BRIEF DESCRIPTION OF DRAWINGS

[0046] Figure 1 A network architecture schematic diagram of a 2B or V2X scenario is shown.

[0047] Figure 2 A management architecture schematic diagram of a terminal device such as a CPE or RSU is shown.

[0048] Figure 3 A schematic diagram of an example of a converged architecture for wireless operation and maintenance terminal communication management is shown.

[0049] Figure 4 A schematic diagram of another example of a converged architecture for wireless operation and maintenance terminal communication management is shown.

[0050] Figure 5 A schematic interaction diagram of a management method 100 of a terminal device according to an embodiment of the present application is shown.

[0051] Figure 6 A schematic interaction diagram of a management method 200 of a terminal device according to an embodiment of the present application is shown.

[0052] Figure 7 A schematic interaction diagram of a management method 300 of a terminal device according to an embodiment of the present application is shown.

[0053] Figure 8 A schematic interaction diagram of a management method 400 of a terminal device according to an embodiment of the present application is shown.

[0054] Figure 9 A schematic block diagram of a communication apparatus for management of a terminal device according to an embodiment of the present application is shown.

[0055] Figure 10 A schematic diagram of an apparatus 20 for management of a terminal device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0056] The technical solutions in the application will be described below with reference to the drawings.

[0057] The technical solutions provided by the embodiments of the application can be applied to various communication systems, for example, a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD), a universal mobile telecommunication system (UMTS), a worldwide interoperability for microwave access (WiMAX) communication system, a 5th generation (5G) system or a new radio (NR) or a future 3GPP system, and the like.

[0058] Generally, a conventional communication system supports a limited number of connections, and is easy to implement. However, with the development of communication technology, a mobile communication system will not only support conventional communication, but also support, for example, device to device (D2D) communication, machine to machine (M2M) communication, machine type communication (MTC), vehicle to everything (V2X) communication (which can also be referred to as vehicle network communication), for example, vehicle to vehicle (V2V) communication (which can also be referred to as car to car communication), vehicle to infrastructure (V2I) communication (which can also be referred to as car to infrastructure communication), vehicle to pedestrian (V2P) communication (which can also be referred to as car to person communication), vehicle to network (V2N) communication (which can also be referred to as car to network communication).

[0059] The application scenarios of a 5G network are various, such as a to business (2B) scenario for vertical industries, a V2X scenario for automatic driving, and an augmented reality (AR) / virtual reality (VR) scenario for ordinary users.

[0060] Currently, in 2B industry scenarios and V2X scenarios, ordinary terminal devices (user equipment, UE) such as AGV, video camera, vehicle, etc. are basically connected to the NR base station of the 5G network through customer-premises equipment (CPE) or road side unit (RSU), and the CPE / RSU is connected to the 5G network of the operator through the air interface, therefore, the CPE or RSU terminal device is a key network device node for user service guarantee.

[0061] Figure 1 A network architecture diagram of a 2B or V2X scenario is shown. In the architecture, Figure 1 , the CPE or RSU is a terminal device that provides wireless network access function for other ordinary terminals, and the NR is a wireless access network base station (such as gNB) of the 5G network. The element management system (EMS) is used to manage the wireless access network device, including parameter configuration, performance management, fault alarm, etc. of the network element. The control plane network function (CNF) of the 5GC means all control plane network elements (including AMF, SMF, NEF, NWDAF, etc.) of the 5G core network, and the user plane function (UPF) is the user plane network element of the 5G core network. The UE mgt (UE management system) is the management system of the CPE or RSU terminal device, and its functions include functions such as registration, parameter configuration, software upgrade, fault diagnosis, state and performance monitoring of the CPE or RSU terminal device.

[0062] Figure 2 A management architecture diagram of the CPE or RSU terminal device is shown. As Figure 2 shown, at present, the terminal management system (UE management, UE mgt) is separately deployed, and it can realize management of the CPE or RSU terminal device based on the 3GPP network data plane path (i.e. UE-gNB-UPF-UE mgt). Specifically, after the CPE or RSU terminal device completes the attachment in the 5G network, the 5G network establishes a PDU session for the CPE or RSU terminal device of the 5G network, which is specially used for transmission of terminal device management data. The PDU session is different from the PDU session for normal service data transmission of the terminal device, and the two PDU sessions correspond to different access point names (APN) or data network name (DNN) identifiers respectively.Figure 2 The path passed through by the arrowed solid line in FIG. 1 is a PDU session for UE mgt data transmission of the CPE or RSU terminal device, and the path passed through by the arrowed dashed line is a PDU session for user data transmission of the CPE or RSU terminal device.

[0063] At present, the CPE or RSU terminal device 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 the supported protocol type and version) and the management capability of the CPE or RSU terminal management system are matched.

[0064] At present, the management of the CPE and RSU device and the management of the network element are two independent management systems, such as Figure 2 In the prior art, the UE mgt is used for managing the CPE or RSU terminal device, the EMS is used for managing the network element (such as a gNB), and the terminal device management entity UE mgt is based on the management scheme of the data plane path provided by the 3GPP network and relies on the end-to-end E2E network resource, which consumes a large amount of network resource, especially the resource of the core network UPF. Therefore, in order to reduce the resource consumption of the CPE / RSU management and reduce the network construction and maintenance cost, the present application proposes a CPE / RSU management and wireless network element fusion architecture. Figure 3 FIG. 1 shows a schematic diagram of an example of a fusion architecture of wireless operation and maintenance terminal communication management. Under the fusion architecture, the UE mgt can reuse the management channel of the EMS to the wireless network element to realize the management of the CPE or RSU terminal device, thereby saving the 5G network resource, especially the resource of the 5G core network.

[0065] Further, since the wireless access network element gNB can be further functionally split, that is, the gNB can be split into a centralized unit control plane (CU-CP), a centralized unit user plane (CU-UP) and a distributed unit (DU), the CPE / RSU management and wireless network element fusion architecture can also be Figure 4 as shown in the architecture.

[0066] Figure 4 FIG. 2 shows a schematic diagram of another example of a fusion architecture of wireless operation and maintenance terminal communication management. The key nodes involved in the architecture are briefly introduced as follows.

[0067] (1) UE: The UE referred to in the present application mainly refers to a terminal device capable of providing wireless network access functions, and in the present application, mainly refers to a CPE or an RSU.

[0068] (2) gNB is a wireless access network base station of a 5G NR network, mainly providing wireless network access functions, including radio resource control (RRC) connection management, security, user data forwarding, data packet reassembly / slicing, retransmission, and the like.

[0069] (3) CU-CP mainly provides functions of wireless connection management (i.e., RRC connection management), security, and the like.

[0070] (4) CU-UP mainly provides functions of user data packet encryption / decryption, integrity protection, and the like.

[0071] (5) DU mainly provides functions of data packet reassembly / slicing, retransmission, channel management, and the like

[0072] (6) 5GC CNF refers to all control plane network elements of a 5G core network, including AMF, SMF, NEF, NWDAF, and the like. Different 5GC control plane network elements are respectively responsible for different network functions, such as that the AMF is mainly responsible for authentication and location tracking of a UE, the SMF is mainly responsible for session management functions such as IP address allocation and QoS management. The NEF is mainly responsible for opening 3GPP network capabilities to external service entities. The NWDAF is mainly responsible for data analysis functions of the 5G core network. More network element types and functions contained in the 5GC CNF can be referred to the description in chapter 6.2 of the 3GPP standard protocol TS 23.501.

[0073] (7) UPF is a user plane network element of a 5G core network, mainly providing functions of user plane data forwarding, charging statistics, QoS execution, and the like.

[0074] (8) EMS is a network element management function, and the EMS in the present application Figure 3 refers to a network element management system of a wireless network, which is responsible for performing management of wireless access network devices, including parameter configuration, performance management, fault alarm, and the like of the wireless network element. The UE mgt is a terminal management function module newly added in the EMS for implementing the technical solution of the present application, and the main functions of the module are registration, parameter configuration, software upgrade, fault diagnosis, state and performance monitoring, and the like of a terminal device such as a CPE or an RSU.

[0075] It should be noted that the 5GC core network can also have at least one management system EMS of a corresponding core network network element, but the technical solution of the present application does not involve the network element management system of the core network, and therefore in the present application Figure 3 and Figure 4The architecture does not show the network element management system corresponding to the core network, but this application does not limit this.

[0076] (9) NMS is a management system in the operator's network that provides cross-domain (such as cross-wireless access network and core network) or cross-equipment vendor network device management. Its specific functions include parameter configuration, performance monitoring, fault alarm and other functions for network devices.

[0077] exist Figure 3 or Figure 4 In the architecture of integrated wireless operation and maintenance and terminal management, UE mgt is a unified terminal management function integrated into the wireless network element management system. It is not a terminal management system paired with terminal equipment from a specific vendor. It manages all terminal equipment within its coverage area, including terminal equipment from different vendors and of different types, based on the unified management interface of the wireless network element management system and the corresponding wireless network elements. However, terminals from different vendors and of different types have the following characteristics:

[0078] (1) Different types of terminal devices (such as CPE, RSU, AR module, etc.) have different parameter types. The parameter type is used to indicate the type of configuration parameters required by the terminal device to provide wireless network access services.

[0079] (2) Terminal devices from different manufacturers support different management protocol types, such as TR-069, MQTT, LWM2M, etc.

[0080] (3) Terminal devices of different types or from different manufacturers support different versions of the same protocol type of management protocol, such as some supporting the V1 version of the TR-069 protocol, and some supporting the V3 version of TR-069, etc.

[0081] In the new architecture that integrates wireless operations and maintenance (O&M) and terminal management, the unified terminal management system manages terminal devices of different types and manufacturers. Therefore, it's necessary to determine the parameter configuration method based on the terminal device information. However, the previous solution where CPE / RSU and UE manager were managed by the same manufacturer is unsuitable for the changes brought about by the unified management architecture and cannot correctly support parameter configuration for terminal devices. Therefore, how the UE manager can configure parameters for terminal devices from different manufacturers or of different types through a unified management interface under the unified architecture is a problem that urgently needs to be solved.

[0082] The following is combined with Figure 5 The management method 100 for terminal devices according to embodiments of this application will be described in detail. Figure 5 This is a schematic interactive diagram of method 100 of this application.

[0083] S101, the terminal device sends device type information of the terminal device to a terminal device management entity, and correspondingly, the terminal device management entity receives the device type information from the terminal device, where the device type information is used to indicate the type of the terminal device.

[0084] It should be understood that the terminal device herein is a terminal device that can provide wireless network access services for other terminal devices, and the type of the terminal device herein can include CPE-type, RSU-type, or AR module-type, etc., which respectively represent that the terminal device is a CPE, an RSU, or an AR module.

[0085] S102, the terminal device management entity sends configuration parameters to the terminal device, and correspondingly, the terminal device receives the configuration parameters from the terminal device management entity, where the configuration parameters are used for configuration of the terminal device.

[0086] It should be understood that the configuration parameters include a service set identifier (SSID) of the wireless network access service provided by the terminal device, a password corresponding to the SSID, an Internet Protocol (IP) address of a clock synchronization server, and the like, and the configuration parameters can also include other parameter types, which are not limited in the present application.

[0087] S103, the terminal device is configured according to the configuration parameters.

[0088] The above scheme can enable the terminal device management entity to send configuration parameters to the terminal device according to the device type information reported by the terminal device, so that the terminal device providing wireless network access services can perform parameter configuration. The terminal device management entity and a wireless network element management system are fused to obtain a fusion management system, and the terminal device providing wireless network access services is managed through the fusion management system, which can reduce the consumption of network resources and reduce the cost of network construction and maintenance without relying on end-to-end network resources.

[0089] Optionally, before S102, the terminal device can determine the configuration parameters according to the device type information.

[0090] Exemplarily, the terminal device management entity determines a parameter type according to the device type information, where the parameter type is used to indicate the type of the configuration parameters required by the terminal device providing wireless network access services, and the terminal device management entity determines the configuration parameters according to the parameter type.

[0091] Specifically, as to S102, the terminal device management entity can send the configuration parameters to the terminal device according to the protocol information received from the terminal device, or, further, the terminal device management entity can send the configuration parameters to the terminal device according to the protocol information received from the terminal device and the priority of the protocol information. The protocol information, the priority of the protocol information and how the terminal device management entity sends the configuration parameters are introduced as follows.

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

[0093] It should be understood that the type of the management protocol herein can include TR-069 protocol, MQTT protocol or LWM2M protocol, etc.

[0094] 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: priority of the protocol type information or priority of the version information; wherein the terminal device management entity sends the configuration parameters to the terminal device according to the protocol information, including that 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.

[0095] The terminal device management entity sends the configuration parameters to the terminal device according to the protocol information received from the terminal device, and there are various possible implementation manners. For example, (1) when the terminal device supports one type of management protocol, the protocol information sent by the terminal device is the protocol information of the management protocol, and the terminal device sends the configuration parameters to the terminal device using the management information according to the protocol information of the management protocol. For details, see the first possible implementation manner in method 200 and the first possible implementation manner in method 400. Alternatively, (2) when the terminal device supports multiple types of management protocols, the terminal device sends the protocol information of all types of management protocols it supports, and the terminal device management entity selects a target management protocol according to the protocol information to send the configuration parameters to the terminal device, and will send the target protocol information to the terminal device, wherein the target protocol information is the protocol information corresponding to the target management protocol. Further, the terminal device management entity can also send the configuration parameters to the terminal device according to the protocol information and a local policy, wherein the policy can be configured locally by the terminal device management entity or received from the NMS. For details, see the second possible implementation manner in method 200 and manner one of the second possible implementation manner in method 400, or see the first possible implementation manner in method 300 and manner two of the first possible implementation manner in method 400.

[0096] The terminal device actively reports the device information and the protocol information, and the terminal device management entity can more quickly and accurately determine the type of the configuration parameter required by the terminal device to provide the wireless network access service.

[0097] The terminal device management entity sends the configuration parameter to the terminal device according to the protocol information received by the terminal device and the priority of the protocol information. There are various possible implementation manners. For example, when the terminal device supports multiple management protocols, the terminal device sends the protocol information of the multiple management protocols and the priority of the protocol information to the terminal device management entity. The terminal device management entity selects a target management protocol according to the protocol information and the priority of the protocol information, and sends the configuration parameter to the terminal device according to the target management protocol, and sends the target protocol information to the terminal device. The target protocol information is the protocol information corresponding to the target management protocol. Further, the terminal device management entity can also send the configuration parameter to the terminal device according to the protocol information, the priority of the protocol information, and the protocol capability supported by the terminal device. For details, refer to the third possible implementation manner of the method 200 and the second possible implementation manner of the method 400, or refer to the second possible implementation manner of the method 300 and the third possible implementation manner of the method 400.

[0098] The terminal device actively reports the device information, the protocol information, and the protocol preference strategy, so that the EMS can more quickly and accurately determine the type of the configuration parameter required by the terminal device to provide the wireless network access service.

[0099] It should be understood that the target protocol information includes one or more of the following: target protocol type information or target version information; 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 the multiple protocol version information; or the protocol information includes multiple protocol type information and multiple protocol version information, the target protocol type information of the target 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.

[0100] The following describes the method 200 for managing the terminal device of the embodiment of the present application. Figure 6 The method 200 for managing the terminal device of the embodiment of the present application is described in detail. Figure 6 FIG. 1 is a schematic interaction diagram of the method 200 of the present application.

[0101] Figure 6The terminal device plug and play (PnP) or management channel establishment process is shown, and the following describes several possible implementation manners of the method 200.

[0102] The first possible implementation manner is as follows.

[0103] In a scenario in which the terminal device supports only one management protocol, the terminal device sends device type information, protocol information, and the like of the terminal device to the converged management system EMS in the PnP or management channel establishment process.

[0104] S201-S203 are an RRC connection establishment process. The RRC connection establishment can occur after the UE is powered on. The UE searches for a wireless signal of a wireless network base station, selects a camping cell based on a cell selection strategy, and establishes an RRC connection with the wireless network base station corresponding to the cell. The RRC connection establishment process is performed according to a 3GPP standard protocol process, including:

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

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

[0107] S203, after the UE completes relevant configuration based on the RRC connection configuration information sent by the gNB, the UE replies to the gNB with an RRC connection establishment completion confirmation message (RRC setup complete). The RRC setup complete includes PnP requested and UE ID.

[0108] The detailed process of S201-S203 can be referred to the 5.3.3 chapter of 3GPP TS 38.331, and the present application will not be described again.

[0109] When the UE completes the RRC connection establishment, the UE can carry a NAS request in the RRC setup complete message to implement specific service processing (such as a UE attachment registration request).

[0110] In the RRC setup complete message of S203, device type information (terminal type) and protocol information are further included, the protocol information including protocol type information and version information. The device type information indicates the type of terminal device, and can 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 type of management protocol supported by the terminal device, and can be TR-069 protocol, MQTT protocol or LWM2M protocol, etc. The version information is the version number of the terminal management protocol identified by the protocol type information. It should be noted that the device type information, protocol type information and version information can also be other names with corresponding functions, which are not limited in the present application.

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

[0112] In S204, after receiving the RRC setup complete message of the UE, the gNB triggers the sending of device registration information of the UE to the wireless network element management system based on the PnPrequested indication in S203, and the message carries PnPrequested, UE ID, device type information, protocol type information and version information.

[0113] For example, the gNB can send the UE device registration information through a management channel between the gNB and the wireless network element management system, such as through an operation, administration, and maintenance (OAM) notification message. The specific implementation of this step can be based on a private scheme of the gNB device manufacturer, or can be implemented by referring to the VES-based scheme, OAM notification or StreamData Report method of the 3GPP standard protocol.

[0114] In S205, the UE information is registered and maintained.

[0115] The EMS determines, according to the PnP requested registration indication in the UE registration message, that the reporting information is a PnP registration request sent by the UE, and then performs device registration management of the UE by the UE mgt, and maintains a correspondence between the UE ID and the gNB IP, wherein the correspondence is used for downlink terminal management data routing, that is, the EMS can determine the management channel through which the UE corresponding to the UE ID transmits the wireless network element identified by the gNB IP.

[0116] In S206, after the EMS completes the registration and registration of the terminal device, the EMS replies to a registration response message through a management interface with the gNB, and the message includes a registration result (registration success or registration failure).

[0117] In S207, the gNB feeds back the registration result of the terminal device to the UE through an air interface bearer (such as a data radio bearer (DRB) or a signaling radio bearer (SRB)) of the terminal device.

[0118] In the embodiments of the present application, the element management system (EMS) is fused with the UE mgt to obtain a fusion management system, and the terminal device is managed through the fusion management system, so that the consumption of network resources is reduced, and the network construction and maintenance costs are reduced. In the scenario in which the terminal device only supports one management protocol, the terminal device actively reports device information and capability information, so that the EMS can more quickly and accurately determine the type of configuration parameters required by the terminal device to provide wireless network access services. In the scenario in which the terminal device supports multiple types of management protocols or supports multiple versions of one management protocol, the terminal device sends device type information of the terminal device it supports, all protocol type information and version information it supports, and the like to the fusion management system EMS in a PnP or management channel establishment process.

[0119] In the scenario in which the terminal device supports multiple types of management protocols or supports multiple versions of one management protocol, the terminal device sends device type information of the terminal device it supports, all protocol type information and version information it supports, and the like to the fusion management system EMS in a PnP or management channel establishment process.

[0120] S201-S207 can refer to the description in the first possible implementation, and the difference is that:

[0121] 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.

[0122] Embodiments of the present application fuse an element management system (EMS) with a UE mgt to obtain a fused management system, and manage terminal equipment through the fused management system, thereby reducing consumption of network resources and reducing network construction and maintenance costs. In a scenario in which terminal equipment supports multiple types of management protocols or multiple protocol versions, the terminal equipment actively reports device information and capability information, so that a subsequent EMS can more quickly and accurately determine the type of configuration parameters required by the terminal equipment to provide wireless network access services based on the information reported by the terminal equipment.

[0123] A third possible implementation:

[0124] In a scenario in which terminal equipment supports multiple types of management protocols or multiple versions of a management protocol, the terminal equipment sends device type information of the terminal equipment, all protocol type information and version information supported by the terminal equipment, and the like to the fused management system EMS in a PnP or management channel establishment process, and the terminal equipment also reports a preferred strategy for the protocol.

[0125] S201-S207 can refer to the description in the second possible implementation, where the difference is that:

[0126] The RRC setup complete message in S203 and the UE registration information in S204 each further carries a priority corresponding to each protocol type information / version information. The priority can be a priority for selecting to use the protocol type information or version information.

[0127] As an example, the priority information can be {[TR069, high priority], [MQTT, low priority], [LWM2M, medium priority]}, which expresses the meaning that the terminal equipment supports three types of management protocols TR069, MQTT, and LWM2M, and the priorities for selecting to use the three protocols are TR069 > MQTT > LWM2M. The priority information is sent to the EMS, so that the EMS determines a target management protocol from all management protocols supported by the UE based on capability information of the EMS.

[0128] Embodiments of the present application fuse an element management system (EMS) with a UE mgt to obtain a fusion management system, and manage terminal devices through the fusion management system, thereby reducing consumption of network resources and reducing network construction and maintenance costs. In a scenario in which a terminal device supports multiple types of management protocols or multiple protocol versions, the terminal device actively reports device information, capability information, and protocol preference strategies, so that a subsequent EMS can more quickly and accurately determine the type of configuration parameters required by the terminal device to provide wireless network access services based on the information reported by the terminal device.

[0129] The following describes the management method 300 of the terminal device according to the embodiments of the present application in detail. Figure 7 The following describes the management method 300 of the terminal device according to the embodiments of the present application in detail. Figure 7 FIG. 3 is a schematic interaction diagram of the method 300 of the present application.

[0130] Figure 7 FIG. 3 is a schematic interaction diagram of the method 300 of the present application.

[0131] The first possible implementation manner is as follows.

[0132] In a scenario in which a terminal device supports multiple types of management protocols or multiple versions of a type of management protocol, the terminal device sends device type information of the terminal device, all protocol type information and version information supported by the terminal device, and the like to the fusion management system EMS in a plug and play (PnP) or management channel establishment process. The EMS determines protocol type information or version information of a management protocol to be used based on a local strategy when the terminal device performs PnP registration, and records the information. Subsequently, the EMS feeds back the selected information to a UE in a device registration response message to the gNB or the UE, and the UE records the information returned by the EMS.

[0133] S301-S304 can refer to the description of S201-S204 in the second possible implementation manner of the method 200.

[0134] S305, select a protocol type and a version of a management protocol.

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

[0136] Meanwhile, the EMS determines the target management protocol, i.e., determines the target protocol information and / or the target version information, from the protocol type information and / or the version information of the multiple management protocols supported by the terminal device based on the policy configured locally by the EMS, such as random selection or other automatic rules.

[0137] The following describes several cases of the EMS determining the target protocol information and / or the target version information through several examples.

[0138] For example, the UE sends multiple protocol type information to the EMS, the EMS determines the target protocol information based on the policy configured locally, and selects the management protocol corresponding to the target protocol information to communicate with the UE. Alternatively, the UE sends multiple protocol type information and multiple version information to the EMS, the EMS selects the target protocol information and the target version information based on the policy configured locally, and selects the management protocol corresponding to the target protocol information and the target version information to communicate with the UE. Alternatively, the UE sends multiple version information to the EMS, the EMS selects the target version information based on the policy configured locally, and selects the management protocol corresponding to the target version information to communicate with the UE.

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

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

[0141] S308, the UE receives the feedback of the EMS, and records the selected protocol type information or version information (i.e., selected protocol or selected version). In order to facilitate 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.

[0142] Embodiments of the present application fuse an element management system (EMS) with a UE mgt to obtain a fusion management system, which manages terminal devices, reduces consumption of network resources, and reduces network construction and maintenance costs. In a scenario in which a terminal device supports multiple types of management protocols or multiple protocol versions, the terminal device actively reports device information and capability information, and the EMS, in combination with the information reported by the terminal device and a local policy, can more quickly and accurately determine the type of configuration parameter required by the terminal device to provide wireless network access services.

[0143] The second possible implementation is:

[0144] In a scenario in which a terminal device supports multiple types of management protocols or multiple versions of a management protocol, the terminal device sends device type information of the terminal device, all protocol type information and version information supported by the terminal device, and the like to the fusion management system EMS in a PnP or management channel establishment process. Meanwhile, the terminal device also reports a preferred policy of the protocol. The EMS determines protocol type information or version information of a management protocol to be used based on protocol capability supported by the EMS and the preferred policy of the terminal device when the terminal device is registered in PnP, and records the information. Subsequently, the EMS feeds back the selected information to the UE in a device registration response message to the gNB or the UE, and the UE records the information returned by the EMS.

[0145] S301-S304 can refer to the description of S201-S204 in the third possible implementation of the method 200.

[0146] S305, selecting protocol type and version of a management protocol.

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

[0148] Meanwhile, the EMS determines, based on protocol capability supported by the EMS and the preferred policy of the terminal device, a target management protocol from protocol type information and / or multiple version information of multiple management protocols supported by the terminal device, that is, determines target protocol information and / or target version information.

[0149] The following describes several cases in which the EMS determines target protocol information and / or target version information through several examples.

[0150] In example one, the UE sends multiple protocol type information to the EMS, 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. In example two, the UE sends multiple protocol type information and multiple version information to the EMS, the EMS selects target protocol information and target version information based on a locally configured policy, and selects a management protocol corresponding to the target protocol information and the target version information to communicate with the UE. In example three, the UE sends multiple version information to the EMS, 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.

[0151] In the following, example one is taken as an example to describe in detail how the EMS determines protocol type information of multiple management protocols supported by a terminal device based on protocol capabilities supported by the EMS and a preferred policy of the terminal device.

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

[0153] S306-S308 can refer to the description of the first possible implementation of method 300.

[0154] In this embodiment, the element management system (EMS) and the UE mgt are integrated to obtain a converged management system. This converged management system manages terminal devices, reducing network resource consumption and lowering network construction and maintenance costs. In scenarios where terminal devices support multiple management protocols or multiple protocol versions, the EMS, by combining the information reported by the terminal devices and its own capabilities, can more quickly and accurately determine the type of configuration parameters required for the terminal device to provide wireless network access services by proactively reporting device information, capability information, and protocol optimization strategies.

[0155] The following is combined with Figure 8 The management method 400 for terminal devices according to embodiments of this application will be described in detail. Figure 8 This is a schematic interactive diagram of method 400 of this application.

[0156] Figure 8 The terminal device parameter configuration process is shown, and this process is similar to... Figure 6 and Figure 7 The terminal device PnP device registration process shown is a two independent process. The management system can only initiate the parameter configuration process to configure the terminal device's parameters after the terminal device completes the PnP device registration process upon startup. However, the parameter configuration process is not triggered immediately after the PnP device registration process is completed. Therefore, method 400 in this embodiment can be combined with 200 or 300, and method 200 or 300 is executed before 400, but it is not limited to executing 400 immediately after method 200 or 300 is completed.

[0157] The following describes several possible implementations of method 400.

[0158] The first possible implementation:

[0159] Prior to method 400, the EMS has already obtained the UE's device type information and the protocol type and / or version information of the management protocol used in subsequent parameter configuration. In the parameter configuration process, the EMS determines the template and protocol processing method for parameter configuration based on the terminal type information, protocol type information and version information, and sends the configuration parameters to the UE based on the protocol processing method.

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

[0161] Method 1:

[0162] In combination with the first possible implementation of the method 200, in a scenario where the terminal device only supports one management protocol, the EMS receives the device type information, protocol information, etc. of the terminal device sent to the converged management system EMS in the PnP or management channel establishment process.

[0163] In S401, the EMS (UE mgt) determines the type of the terminal device based on the terminal device type information when performing parameter configuration of the terminal device, thereby determining the corresponding parameter type of the terminal device, which is used to indicate the type of the configuration parameter required by the UE to provide wireless network access service for other terminal devices, determines the target management protocol used when sending the configuration parameter to the UE based on the protocol information (including protocol type information and / or version information), and models and processes the configuration parameter according to the processing mode (such as message format, parameter format) of the target management protocol (including encapsulating the configuration parameter according to the parameter object format of the protocol).

[0164] The device type information indicates the type of the terminal device, and its specific values can be CPE-type, RSU-type, AR module-type, etc., respectively indicating that the terminal device is a CPE, an RSU or an AR module. The protocol type information indicates the type of the management protocol supported by the terminal device, and its specific values can be TR-069 protocol, MQTT protocol or LWM2M protocol, etc. 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, the protocol type information and the version information herein can also be other names with corresponding functions, which are not limited in the present application.

[0165] It should be understood that under the converged architecture, the UE mgt can reuse the management channel of the EMS for the wireless network element to manage the terminal device such as CPE or RSU. Since the EMS manages the gNB by adopting the mode of including various parameters of the gNB in the model for management, the EMS (UE mgt) in the present embodiment can also include various configuration parameters of the UE in the model for management.

[0166] In S402, the EMS sends the UE configuration information to the gNB.

[0167] After the EMS (UE mgt) completes the configuration parameter modeling, the configuration parameters modeled in S401 according to the target management protocol are sent to the gNB through the management interface message between the gNB, the message carries the configuration terminal device identifier UEID or UE IP, and the configuration information (Config info) of the configuration parameters of the terminal device. The Config info can 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, the clock synchronization server IP address, and other vendor-defined parameter information.

[0168] As an example, the above management interface message can be a CreateMOI interface message defined in the 3GPP standard, and the terminal device identifier UE ID or UE IP and the configuration parameter Config info of the terminal device should be modeled according to the information model matched with the CreateMOI interface message. For example, the DeviceConfig information object class (IOC) defined in the embodiment of the present application can be defined as Table 1. Table 1 shows the DeviceConfig IOC parameter attribute, that is, the first column of Table 1 is the parameter name of the configuration parameter of the UE, and the second column is the corresponding parameter function.

[0169] Table 1

[0170] Parameter name Parameter function UE ID Terminal device identification ConfigFile Vendor-defined parameter NTPServer Clock synchronization server name or IP address SSID Network identification of wireless network service provided by terminal device

[0171] It should be noted that the above management interface message can also be other interface messages and corresponding message parameter formats, which are not limited in the present application.

[0172] S403, the gNB receives the configuration parameters of the EMS, parses the message parameters of step 2, and obtains the UE identifier and configuration parameters (i.e. the parameter information of Table 1) and matches the air interface bearer (such as data radio bearer / DRB or signaling radio bearer / SRB) used to transmit the terminal device management data based on the UE ID or UE IP.

[0173] S404, the gNB sends the UE configuration information to the UE through the air interface bearer corresponding to the UE identifier for transmitting the terminal device management data.

[0174] S405, after the UE receives the configuration information, the message parameters are parsed based on the corresponding terminal device management protocol, and the corresponding parameter configuration is executed.

[0175] The element management system (EMS) is fused with the UE mgt to obtain a fusion management system, terminal equipment is managed through the fusion management system, consumption of network resources is reduced, and network construction and maintenance costs are reduced. In a scenario in which terminal equipment only supports one type of management protocol, the EMS can more quickly and accurately determine the type of configuration parameter required by the terminal equipment to provide wireless network access services and perform a corresponding parameter configuration process according to device information and capability information actively reported by the terminal equipment.

[0176] Method two:

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

[0178] The S401-S405 can be specifically referred to the corresponding description in the method one.

[0179] The element management system (EMS) is fused with the UE mgt to obtain a fusion management system, terminal equipment is managed through the fusion management system, consumption of network resources is reduced, and network construction and maintenance costs are reduced. In a scenario in which terminal equipment supports multiple types of management protocols or supports multiple versions of one type of management protocol, terminal equipment actively reports device information and capability information, the EMS combines the information reported by the terminal equipment and a local policy, more quickly and accurately determines the type of configuration parameter required by the terminal equipment to provide wireless network access services, and performs a corresponding parameter configuration process.

[0180] Method three:

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

[0182] The S401-S405 can be specifically referred to the corresponding description in the method one.

[0183] In the embodiment of the present application, an element management system (EMS) is fused with a UE mgt to obtain a fusion management system, and the terminal device is managed through the fusion management system, so as to reduce the consumption of network resources and reduce the network construction and maintenance cost. In the scene where the terminal device supports multiple types of management protocols or multiple protocol versions, the terminal device actively reports device information, capability information and protocol optimization strategy, and the EMS combines the information reported by the terminal device and the capability of the EMS, so as to more quickly and accurately determine the type of configuration parameters required by the terminal device to provide wireless network access service and perform a corresponding parameter configuration process.

[0184] The second possible implementation manner is as follows:

[0185] Before the method 400, the EMS has obtained the device type information of the UE, but has not determined the protocol information of the management protocol used in the subsequent parameter configuration process. The EMS selects the protocol information of the target management protocol in the parameter configuration process, and then determines the template of the parameter configuration and the protocol processing manner based on the device type information and the protocol information, and sends the configuration parameters to the UE based on the protocol processing manner.

[0186] It should be understood that, according to different combination manners of the method 400 and the method 200, the EMS can obtain the device type information and the protocol information in multiple manners. The following describes several possible combination manners.

[0187] The first possible implementation manner is as follows:

[0188] In combination with the second possible implementation manner of the method 200, in the scene where the terminal device supports multiple types of management protocols or supports multiple versions of one type of management protocol, the EMS receives the device type information of the terminal device supported by the UE, the information of all protocol types supported by the UE and / or the version information, and sends the information to the fusion management system EMS in the PnP or management channel establishment process. The EMS (UE mgt) determines the protocol type information and the version information to be used in the parameter configuration process based on the local configuration strategy, and performs parameter modeling processing based on the determined protocol type and version. Meanwhile, the EMS returns the selected protocol type and version information to the terminal device in the parameter configuration process.

[0189] The S401-S405 can refer to the descriptions of the S401-S405 in the first possible implementation manner of the method 400 in the first possible implementation manner, and the difference is that:

[0190] In S401, before determining the protocol processing mode, the EMS also needs to determine the target management protocol to be used for 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 the policy configured locally by the EMS, such as random selection or other automatic rules.

[0191] The following describes several cases of determining the target protocol information and / or target version information by the EMS through several examples.

[0192] For example, the UE sends multiple protocol type information to the EMS, the EMS determines the target protocol information based on the policy configured locally, and selects the management protocol corresponding to the target protocol information to communicate with the UE. Alternatively, the UE sends multiple protocol type information and multiple version information to the EMS, the EMS selects the target protocol information and the target version information based on the policy configured locally, and selects the management protocol corresponding to the target protocol information and the target version information to communicate with the UE. Alternatively, the UE sends multiple version information to the EMS, the EMS selects the target version information based on the policy configured locally, and selects the management protocol corresponding to the target version information to communicate with the UE.

[0193] 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 the protocol type information and / or the version information.

[0194] In S405, before performing the parameter configuration, the UE needs to parse the configuration parameters based on the received protocol information to obtain the corresponding parameter information.

[0195] Embodiments of the present application fuse the element management system (EMS) and the UE mgt to obtain a fusion management system, manage the terminal device through the fusion management system, reduce the consumption of network resources, and reduce the network construction and maintenance cost. In the scenario where the terminal device supports multiple types of management protocols or multiple protocol versions, the EMS can more quickly and accurately determine the type of configuration parameters required by the terminal device to provide wireless network access services and perform the corresponding parameter configuration process according to the device information and capability information actively reported by the terminal device.

[0196] Method two:

[0197] In combination with the third possible implementation of the method 200, in a scenario where the terminal device supports multiple types of management protocols or supports multiple versions of one type of management protocol, the EMS receives the device type information of the terminal device supported by the UE, the information of all protocol types supported by the UE and the version information, and the like, which are sent to the converged management system EMS in the PnP or management channel establishment process. Meanwhile, the EMS also receives the protocol preference strategy sent by the UE. The converged management system EMS (UE mgt) determines the type of management protocol or the version of the protocol to be used based on the protocol capability supported by the EMS (UE mgt) itself and the preference strategy of the terminal device when configuring parameters, and performs parameter modeling processing based on the determined type of protocol and version, and returns the selected protocol information to the terminal device in the configuration process.

[0198] The S401-S405 can refer to the corresponding description in the S401-S405 of the first mode in the second possible implementation of the method 400 for details. The difference lies in that:

[0199] In the S401, since the UE sends the protocol preference strategy to the EMS in the third possible implementation of the method 200, the EMS refers to the management protocol type supported by itself when selecting the target management protocol, and also refers to the preference strategy of the terminal device.

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

[0201] The element management system (EMS) and the UE mgt are fused to obtain a fusion management system in the embodiments of the present application. The terminal device is managed through the fusion management system, consumption of network resources is reduced, and network construction and maintenance costs are reduced. In a scenario where the terminal device supports multiple types of management protocols or multiple protocol versions, the EMS can combine device information, capability information and protocol preference policies reported by the terminal device to more quickly and accurately determine the type of configuration parameters required by the terminal device to provide wireless network access services and perform a corresponding parameter configuration process.

[0202] The above, in combination with Figures 1 to 8 The method provided by the embodiments of the present application is described in detail. The following, in combination with Figures 9 to 10 The device provided by the embodiments of the present application is described in detail.

[0203] Figure 9 is a schematic block diagram of a communication device for management of a terminal device provided by the embodiments of the present application. As Figure 9 indicated, the communication device 10 can include a transceiver module 11 and a processing module 12.

[0204] The transceiver module 11 can be used to receive information sent by other devices, and can also be used to send information to other devices. For example, receiving a device type message or sending a configuration parameter. The processing module 12 can be used for content processing of the device, such as determining a configuration parameter.

[0205] In a possible design, the communication device 10 can correspond to the terminal device in the method embodiments described above.

[0206] Specifically, the communication device 10 can correspond to the terminal device or UE in any one of the method 100 to the method 400 according to the embodiments of the present application. The communication device 10 can include a module for performing the operations performed by the terminal device in the corresponding method, and each unit in the communication device 10 is respectively for realizing the operations performed by the terminal device in the corresponding method.

[0207] For example, when the communication device 10 corresponds to the terminal device in the method 100, the transceiver module 11 is used to perform steps S101 and S102, and the processing module 12 is used to perform S103.

[0208] For example, when the communication device 10 corresponds to the UE in the method 200, the transceiver module 11 is used to perform steps S201-S203 and S207.

[0209] Exemplarily, when the communication apparatus 10 corresponds to the UE in the method 300, the transceiver module 11 is configured to perform steps S301-S303, S307, and the processing module 12 is configured to perform S308.

[0210] Exemplarily, when the communication apparatus 10 corresponds to the UE in the method 400, the transceiver module 11 is configured to perform step S404, and the processing module 12 is configured to perform S405.

[0211] In another possible design, the communication apparatus 10 can correspond to the terminal device management entity, or UE mgt, or EMS, or the fusion system of the EMS and the UE mgt in the method embodiments.

[0212] Specifically, the communication apparatus 10 can correspond to the terminal device management entity, or UE mgt, or EMS, or the fusion system of the EMS and the UE mgt in any one of the methods 100 to 400 according to the embodiments of the present application, the communication apparatus 10 can include modules for performing operations performed by the terminal device management entity, or UE mgt, or EMS, or the fusion system of the EMS and the UE mgt in the corresponding method, and each unit in the communication apparatus 10 is respectively for implementing operations performed by the terminal device management entity, or UE mgt, or EMS, or the fusion system of the EMS and the UE mgt in the corresponding method.

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

[0214] Exemplarily, when the communication apparatus 10 corresponds to the UE mgt, or EMS, or the fusion system of the EMS and the UE mgt in the method 200, the transceiver module 11 is configured to perform steps S204, S206, and the processing module 12 is configured to perform S205.

[0215] Exemplarily, when the communication apparatus 10 corresponds to the UE mgt, or EMS, or the fusion system of the EMS and the UE mgt in the method 300, the transceiver module 11 is configured to perform steps S304, S306, and the processing module 12 is configured to perform S305.

[0216] Exemplarily, when the communication apparatus 10 corresponds to the UE mgt, or EMS, or the fusion system of the EMS and the UE mgt in the method 400, the transceiver module 11 is configured to perform step S402, and the processing module 12 is configured to perform S401.

[0217] Figure 10 A schematic diagram of the apparatus 20 for managing terminal devices according to an embodiment of the present application.

[0218] In a possible design, the apparatus 20 can be a terminal device management entity, or a chip or chip system located on the terminal device management entity.

[0219] In a possible design, the apparatus 20 can be a terminal device including various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to wireless modems, and various forms of terminals, mobile stations, terminals, user equipment, soft terminals, and the like, and can be a chip or chip system located on the terminal device.

[0220] The apparatus 20 can include a processor 21 (i.e., an example of a processing module) and a memory 22. The memory 22 is configured to store instructions, and the processor 21 is configured to execute the instructions stored in the memory 22, so that the apparatus 20 implements the steps performed by the devices in various possible designs in the corresponding methods as described in the above Figures 5 to 8

[0221] Further, the apparatus 20 can further include an input port 23 (i.e., an example of a transceiver module) and an output port 24 (i.e., 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 configured to store a computer program, and the processor 21 can be configured to call and run the computer program from the memory 22, to control the input port 23 to receive signals, and control the output port 24 to send signals, to complete the steps of the terminal device or the wireless access network device or the UE or the base station in the above methods. The memory 22 can be integrated in the processor 21, or can be separately arranged from the processor 21.

[0222] Optionally, if the apparatus 20 for transmitting the packet is a communication device, the input port 23 is a receiver, and the output port 24 is a transmitter. The receiver and the transmitter can be the same or different physical entities. When they are the same physical entity, they can be collectively referred to as a transceiver.

[0223] Optionally, if the apparatus 20 is a chip or a circuit, the input port 23 is an input interface, and the output port 24 is an output interface.

[0224] As an implementation manner, the functions of the input port 23 and the output port 24 can be implemented by a transceiver circuit or a dedicated transceiver chip. The processor 21 can be implemented by a dedicated processing chip, a processing circuit, a processor or a general-purpose chip.

[0225] ​As another implementation manner, the device provided by the embodiment of the present application can be implemented by using a general computer. That is, program codes for implementing 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 implements the functions of the processor 21, the input port 23 and the output port 24 by executing the codes in the memory 22.

[0226] The modules or units in the device 20 can be used to perform the actions or processes performed by the device (for example, the terminal device) performing the random access in the above method. Here, the detailed description is omitted.

[0227] The concepts, explanations, detailed descriptions and other steps related to the technical solutions provided by the embodiments of the present application involved in the device 20 are described in the foregoing method or other embodiments, and are not described here.

[0228] It should be understood that the processor in the embodiments of the present application can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0229] The embodiment of the present application further provides a computer readable storage medium, which stores computer instructions for implementing the method executed by the authentication service function entity or the unified data management entity or the terminal device in the method embodiment.

[0230] For example, the computer program is executed by a computer, so that the computer can implement the method executed by the terminal device management entity or the terminal device in the method embodiment.

[0231] The embodiment of the present application further provides a computer readable storage medium, which stores computer instructions for implementing the method executed by the terminal device management entity or the terminal device in the method embodiment.

[0232] For example, the computer program is executed by a computer, so that the computer can implement the method executed by the terminal device management entity or the terminal device in the method embodiment.

[0233] It should also be understood that the memory in the embodiments of the present application can be a volatile memory or a nonvolatile memory, or can include both volatile and nonvolatile memory. Among them, the nonvolatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically EPROM (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM) used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0234] The above-described embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any combination thereof. When implemented by software, the above-described embodiments can be implemented, in whole or in part, in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another, for example, the computer instructions can be transferred from one website, computer, server or data center to another website, computer, server or data center through wired (such as infrared, wireless, microwave, etc.) mode. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. containing one or more available medium collections. The available medium can be a magnetic medium (such as a floppy disk, a hard disk, a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium. The semiconductor medium can be a solid state disk.

[0235] It should be understood that the term "and / or" in this document merely describes an associated relationship, which means that there can be three relationships, for example, A and / or B can represent three cases: A exists alone, A and B exist together, and B exists alone. In addition, the character " / " in this document generally represents an "or" relationship between the front and rear associated objects.

[0236] It should be understood that the size of the sequence number of the above-mentioned processes in various embodiments of the present application does not mean the order of execution, and the execution order of the processes should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0237] Those skilled in the art can realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed in this document can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are realized in hardware or software depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

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

[0239] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.

[0240] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or they can be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

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

[0242] If the functions 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 solutions of the present application or the parts of the present application that essentially contribute to the prior art or the parts of the technical solutions can be embodied in the form of software products. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the embodiments of the present application. The aforementioned storage medium includes a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.

[0243] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A management method of a terminal device, characterized by, The method comprises: a terminal device management entity receiving device type information from a terminal device, the device type information being used to indicate a type of the terminal device, the terminal device being used to provide a wireless network access service; the terminal device management entity receiving protocol information from the terminal device, the protocol information comprising one or more of the following: protocol type information or version information, the protocol type information being used to indicate a type of a management protocol supported by the terminal device, the version information being used to indicate a version number of the type of the management protocol supported by the terminal device; the terminal device management entity sending configuration parameters to the terminal device, the configuration parameters being determined according to the device type information and the protocol information, the configuration parameters being used for configuration of the terminal device.

2. The method of claim 1, wherein, The method further comprises the terminal device management entity determining the configuration parameters according to the device type information.

3. The method of claim 2, wherein, The terminal device management entity determining the configuration parameters according to the device type information comprises: the terminal device management entity determining a parameter type according to the device type information, the parameter type being used to indicate a type of the configuration parameters required by the terminal device to provide the wireless network access service; the terminal device management entity determining the configuration parameters according to the parameter type.

4. The method of claim 1, wherein the terminal device management entity sending the configuration parameters to the terminal device according to the protocol information comprises the terminal device management entity sending the configuration parameters to the terminal device according to target protocol information, the target protocol information comprising one or more of the following: target protocol type information or target version information; and the protocol information comprises a plurality of protocol type information, the target protocol type information of the target protocol information being one of the plurality of protocol type information; or the protocol information comprises a plurality of protocol version information, the target protocol version information of the target protocol information being 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 being one of the plurality of protocol type information, and the target protocol version information of the target protocol information being one of the plurality of protocol version information.

5. The method according to claim 1 or 4, characterized in that, The method further comprises: the terminal device management entity sending the target protocol information to the terminal device.

6. The method according to claim 1 or 4, characterized in that, The method further comprises: the device management entity receiving priority information from the terminal device, the priority information being used to indicate a priority of the protocol information, the priority of the protocol information comprising one or more of the following: a priority of protocol type information or a priority of version information; and wherein the terminal device management entity sending the configuration parameters to the terminal device according to the protocol information comprises: the terminal device management entity sending the configuration parameters to the terminal device according to the protocol information and the priority of the protocol information.

7. The method according to claim 1 or 4, characterized in that, the terminal device management entity sending the configuration parameters to the terminal device according to the protocol information comprises: The terminal device management entity sends the configuration parameter to the terminal device according to the protocol information and a policy.

8. The method according to any one of claims 1 to 4, characterized in that, The configuration parameter comprises a wireless network service set identifier (SSID) of a wireless network access service provided by the terminal device, a password corresponding to the SSID, an Internet Protocol (IP) address of a clock synchronization server, and manufacturer information.

9. A management method of a terminal device, characterized by, The method comprises: The terminal device sends device type information to a terminal device management entity, the device type information being used to indicate a type of the terminal device, the terminal device being configured to provide a wireless network access service; The terminal device sends protocol information to the terminal device management entity, the protocol information comprising one or more of the following: protocol type information or version information, the protocol type information being used to indicate a type of a management protocol supported by the terminal device, and the version information being used to indicate a version number of the type of the management protocol supported by the terminal device; The terminal device receives configuration parameter from the terminal device management entity, the configuration parameter being used for configuration of the terminal device, the configuration parameter being determined according to the device type information and the protocol information; The terminal device is configured according to the configuration parameter.

10. The method of claim 9, wherein, The method further comprises: The terminal device receives target protocol information from the terminal device management entity, the target protocol information comprising 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, the target protocol type information of the target protocol information being one of the plurality of protocol type information; or The protocol information comprises a plurality of protocol version information, the target protocol version information of the target protocol information being 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 being one of the plurality of protocol type information, and the target protocol version information of the target protocol information being one of the plurality of protocol version information.

11. The method according to claim 9 or 10, characterized in that, The method further comprises: The terminal device sends priority information to the terminal device management entity, the priority information being used to indicate a priority of the protocol information, the priority of the protocol information comprising one or more of the following: a priority of the protocol type information or a priority of the version information.

12. The method of any one of claims 9-10, wherein, The configuration parameter comprises a wireless network service set identifier (SSID) of a wireless network access service provided by the terminal device, a password corresponding to the SSID, an Internet Protocol (IP) address of a clock synchronization server, and manufacturer information.

13. A management apparatus of a terminal device, characterized by, The method comprises: The transceiver module is configured to receive device type information from a terminal device, the device type information being used to indicate a type of the terminal device, the terminal device being configured to provide a wireless network access service; The transceiver module is further configured to receive protocol information from the terminal device, the protocol information comprising one or more of the following: protocol type information or version information, the protocol type information being used to indicate a type of a management protocol supported by the terminal device, and the version information being used to indicate a version number of the type of the management protocol supported by the terminal device; The transceiver module is further configured to send configuration parameters to the terminal device, the configuration parameters being determined according to the device type information and the protocol information, and the configuration parameters being used for configuration of the terminal device.

14. The apparatus of claim 13, wherein, The apparatus further includes: The processing module is configured to determine the configuration parameters according to the device type information.

15. The apparatus of claim 14, wherein, The processing module is specifically configured to determine the parameter type according to the device type information, the parameter type being used to indicate a type of the 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 parameters according to the parameter type.

16. The apparatus of claim 13, wherein The processing module is specifically configured to send the configuration parameters to the terminal device according to target protocol information, the target protocol information including one or more of the following: target protocol type information or target version information; wherein The protocol information includes a plurality of protocol type information, the target protocol type information of the target protocol information being one of the plurality of protocol type information; or The protocol information includes a plurality of protocol version information, the target protocol version information of the target protocol information being one of the plurality of protocol version information; or The protocol information includes a plurality of protocol type information and a plurality of protocol version information, the target protocol type information of the target protocol information being one of the plurality of protocol type information, and the target protocol version information of the target protocol information being one of the plurality of protocol version information.

17. The apparatus of claim 13 or 16, wherein The transceiver module is further configured to send the target protocol information to the terminal device.

18. The apparatus of claim 13 or 16, wherein, The transceiver module is further configured to receive priority information from the terminal device, the priority information being used to indicate a priority of the protocol information, the priority of the protocol information including one or more of the following: a priority of protocol type information or a priority of version information; The processing module is specifically configured to send the configuration parameters to the terminal device according to the protocol information and the priority of the protocol information.

19. The apparatus of claim 13 or 16, wherein The processing module is further configured to send the configuration parameters to the terminal device according to the protocol information and a policy.

20. The apparatus of any one of claims 13-16, wherein, The configuration parameters include a service set identifier (SSID) of a wireless network service provided by the terminal device, a password corresponding to the SSID, an Internet Protocol (IP) address of a clock synchronization server, and vendor information.

21. A management apparatus of a terminal device, characterized by, The apparatus includes: The transceiver module is configured to send device type information to a terminal device management entity, the device type information being used to indicate a type of the terminal device, the terminal device being used to provide wireless network access service. The transceiver module is configured to send protocol information to the terminal device management entity, the protocol information including one or more of the following: protocol type information or version information, the protocol type information being used to indicate a type of a management protocol supported by the terminal device, and the version information being used to indicate a version number of the type of the management protocol supported by the terminal device. The transceiver module is configured to receive configuration parameters from the terminal device management entity, the configuration parameters being used for configuration of the terminal device, and the configuration parameters being determined according to the device type information and the protocol information. The processing module is configured to perform configuration according to the configuration parameters.

22. The apparatus of claim 21, wherein The transceiver module is configured to receive target protocol information from the terminal device management entity, the target protocol information including one or more of target protocol type information or target version information; wherein The protocol information includes a plurality of protocol type information, the target protocol type information of the target protocol information being one of the plurality of protocol type information; or The protocol information includes a plurality of protocol version information, the target protocol version information of the target protocol information being one of the plurality of protocol version information; or The protocol information includes a plurality of protocol type information and a plurality of protocol version information, the target protocol type information of the target protocol information being one of the plurality of protocol type information, and the target protocol version information of the target protocol information being one of the plurality of protocol version information.

23. The apparatus of claim 21 or 22, wherein The transceiver module is further configured to send priority information to the terminal device management entity, the priority information being used to indicate a priority of the protocol information, the priority of the protocol information including one or more of a priority of protocol type information or a priority of version information.

24. The apparatus of any one of claims 21-22, wherein, The configuration parameters include a wireless network service set identifier (SSID) of a wireless network access service provided by the terminal device, a password corresponding to the SSID, an Internet Protocol (IP) address of a clock synchronization server, and manufacturer information.

25. A communications device, characterized by The apparatus comprises: a processor and a memory; the memory is configured to store a computer program; the processor is configured to execute the computer program stored in the memory, so that the communication apparatus executes the communication method of any one of claims 1 to 8, or executes the communication method of any one of claims 9 to 12.

26. A computer-readable storage medium, characterized in that, The computer program is stored on the computer readable storage medium, and when the computer program runs on a computer, the computer executes the communication method of any one of claims 1 to 8, or executes the communication method of any one of claims 9 to 12.

27. A chip system, characterized by The chip system comprises: a processor configured to call and run a computer program from a memory, so that the chip system is installed in a communication device and performs: receiving device type information from a terminal device, the device type information being used to indicate a type of the terminal device, the terminal device being configured to provide wireless network access service; receiving protocol information from the terminal device, the protocol information including one or more of protocol type information or version information, the protocol type information being used to indicate a type of management protocol supported by the terminal device, and the version information being used to indicate a version number of the type of management protocol supported by the terminal device. sending configuration parameters to the terminal device, the configuration parameters being determined according to the device type information and the protocol information, the configuration parameters being used for configuration of the terminal device.

28. A chip system, characterized by comprising a processor configured to invoke and run a computer program from a memory, so that the chip system installed with the computer program performs: sending device type information to a terminal device management entity, the device type information being used to indicate a type of the terminal device, the terminal device being used to provide wireless network access service; sending protocol information to the terminal device management entity, the protocol information comprising one or more of the following: protocol type information or version information, the protocol type information being used to indicate a type of management protocol supported by the terminal device, the version information being used to indicate a version number of the type of management protocol supported by the terminal device; receiving configuration parameters from the terminal device management entity, the configuration parameters being used for configuration of the terminal device, the configuration parameters being determined according to the device type information and the protocol information; configuring according to the configuration parameters.

29. A management system of a terminal device, characterized by, 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 8, and the terminal device is configured to perform the method of any one of claims 9 to 12.

Images