Network node device encoding, registration method, topology generation method and related equipment

Abstract

The present disclosure provides a network node device coding method, a registration method, a network topology generation method and related devices, and relates to the field of communication technology. The method includes: generating device coding information of each node device in the target network according to the network type, device type and device identification of each node device in the target network, so that when the terminal device sends a device registration or update request message to the network element device, the device coding information of one or more node devices through which the device registration or update request message passes is added to the device registration or update request message, and finally a network link topology diagram is generated according to the connection relationship between each node device. The present disclosure can realize the unified management of near-field communication devices and dynamic monitoring of network links.

Description

Background Art

[0002] As users' demand for mobile broadband data continues to increase, 4G / 5G increasingly needs to use high-frequency bands and large bandwidths to increase capacity. The resulting problem is that coverage easily forms a bottleneck indoors. Traditional cellular indoor distributed systems have problems such as high construction costs, long cycles, and difficult construction. How to make full use of low-frequency band resources to solve indoor coverage is a technical problem that needs to be solved urgently.

[0003] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0004] The present disclosure provides a network node device encoding method, a registration method, a network topology generation method and related equipment, which at least to a certain extent overcome the problems of traditional cellular room distributed systems such as high construction cost, long period and difficult construction.

[0005] Other features and advantages of the present disclosure will become apparent from the following detailed description, or may be learned in part by the practice of the present disclosure.

[0006] According to one aspect of the present disclosure, a network node device encoding method is provided, the method comprising: obtaining the network type, device type and device identification of each node device in the target network; generating device encoding information of each node device in the target network according to the network type, device type and device identification of each node device.

[0007] In some embodiments, device coding information of each node device in the target network is generated based on the network type, device type and device identification of each node device, including: performing a hash operation on the network type, device type and device identification of each node device, and using the hash operation result as the device coding information of each node device in the target network.

[0008] In some embodiments, the network type includes at least one of the following: a cellular network, a WLAN network, a wired network, and a satellite network.

[0009] In some embodiments, the device type includes at least one of the following: a mobile phone, a computer, a sensor, and a wearable device.

[0010] In some embodiments, the device identification is a MAC address.

[0011] According to one aspect of the present disclosure, a network topology generation method is also provided, the method comprising: obtaining the connection relationship between each node device based on a device registration or update request message sent by a terminal device to a network element device, wherein the device registration or update request message is added with device coding information of one or more node devices through which the device registration or update request message passes, and the device coding information is coding information generated based on the network type, device type and device identification of each node device; and generating a network link topology diagram based on the connection relationship between each node device.

[0012] In some embodiments, the method further includes: dynamically updating the generated network link topology map.

[0013] According to one aspect of the present disclosure, a terminal device information reporting method is also provided, which is applied to a network element device, including: receiving a device registration or update request message from a terminal device, wherein the device registration or update request message sent by the terminal device to the network element device passes through one or more node devices to reach the network element device, and when the device registration or update request message passes through a node device each time, the device coding information of the corresponding node device is added to the device registration or update request message, and the device coding information is the coding information generated according to the network type, device type and device identification of each node device; and returning a device registration or update response message to the terminal device.

[0014] In some embodiments, the method further includes: acquiring a connection relationship between each node device according to a received device registration or update request message; and generating a network link topology diagram according to the connection relationship between each node device.

[0015] In some embodiments, the method further includes: dynamically updating the generated network link topology map.

[0016] In some embodiments, the device encoding information is a hash operation result obtained by performing a hash operation on the network type, device type and device identification of each node device.

[0017] According to one aspect of the present disclosure, a terminal device information reporting method is also provided, which is applied to a terminal device, including: sending a device registration or update request message to a network element device, wherein the device registration or update request message sent by the terminal device passes through one or more node devices to reach the network element device; when the device registration or update request message passes through a node device each time, adding device coding information of the corresponding node device to the device registration or update request message, wherein the device coding information is coding information generated according to the network type, device type and device identification of each node device; and receiving a device registration or update response message returned by the network element device.

[0018] In some embodiments, the device encoding information is a hash operation result obtained by performing a hash operation on the network type, device type and device identification of each node device.

[0019] In some embodiments, the network element device is further used to obtain the connection relationship between each node device according to the received device registration or update request message, and generate a network link topology diagram according to the connection relationship between each node device.

[0020] According to one aspect of the present disclosure, a network node device encoding device is also provided, which includes: a device information acquisition module for acquiring the network type, device type and device identification of each node device in the target network; a device encoding module for generating device encoding information of each node device in the target network according to the network type, device type and device identification of each node device.

[0021] According to one aspect of the present disclosure, a network topology generation device is also provided, including: a node device connection relationship acquisition module, used to obtain the connection relationship between each node device according to a device registration or update request message sent by a terminal device to a network element device, wherein the device registration or update request message is added with device coding information of one or more node devices through which the device registration or update request message passes, and the device coding information is coding information generated according to the network type, device type and device identification of each node device; a network topology generation module, used to generate a network link topology diagram according to the connection relationship between each node device.

[0022] According to one aspect of the present disclosure, a network element device is also provided, which includes: a device registration request message receiving module, used to receive a device registration or update request message from a terminal device, wherein the device registration or update request message sent by the terminal device to the network element device passes through one or more node devices to reach the network element device, and when the device registration or update request message passes through a node device each time, the device coding information of the corresponding node device is added to the device registration or update request message, and the device coding information is the coding information generated according to the network type, device type and device identification of each node device; a device registration response message sending module, used to return a device registration or update response message to the terminal device.

[0023] According to one aspect of the present disclosure, a terminal device is also provided, which includes: a device registration request message sending module, used to send a device registration or update request message to a network element device, wherein the device registration or update request message sent by the terminal device passes through one or more node devices to reach the network element device; when the device registration or update request message passes through a node device each time, the device coding information of the corresponding node device is added to the device registration or update request message, wherein the device coding information is coding information generated according to the network type, device type and device identification of each node device; a device registration response message receiving module, used to receive the device registration or update response message returned by the network element device.

[0024] According to one aspect of the present disclosure, an electronic device is also provided, which includes: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute any one of the network node device encoding methods described above, or any one of the network topology generation methods described above, or any one of the terminal device information reporting methods described above by executing the executable instructions.

[0025] According to one aspect of the present disclosure, a computer-readable storage medium is also provided, on which a computer program is stored. When the computer program is executed by a processor, it implements any one of the network node device encoding methods described above, or any one of the network topology generation methods described above, or any one of the terminal device information reporting methods described above.

[0026] According to another aspect of the present disclosure, a computer program product or a computer program is also provided, the computer program product or the computer program including computer instructions, the computer instructions being stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes any one of the above-mentioned network node device encoding methods, or any one of the above-mentioned network topology generation methods, or any one of the above-mentioned terminal device information reporting methods.

[0027] The network node device encoding method, registration method, network topology generation method and related devices provided in the embodiments of the present invention generate device coding information for each node device in the target network according to the network type, device type and device identification of each node device in the target network, so that when the terminal device sends a device registration or update request message to the network element device, the device coding information of one or more node devices through which the device registration or update request message passes is added to the device registration or update request message, and finally a network link topology diagram is generated according to the connection relationship between each node device, so as to realize unified management of near-field communication devices and dynamic monitoring of network links.

[0028] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] The accompanying drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the specification are used to explain the principles of the present disclosure. Obviously, the accompanying drawings described below are only some embodiments of the present disclosure, and for ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without creative work.

[0030] Figure 1 A schematic diagram of a communication system architecture in an embodiment of the present disclosure is shown;

[0031] Figure 2 A flow chart of a network node device encoding method in an embodiment of the present disclosure is shown;

[0032] Figure 3 A flow chart of a network topology generation method according to an embodiment of the present disclosure is shown;

[0033] Figure 4 A flow chart of a method for reporting terminal device information applied to a network element device in an embodiment of the present disclosure is shown;

[0034] Figure 5 A flow chart of a method for reporting terminal device information applied to a terminal device in an embodiment of the present disclosure is shown;

[0035] Figure 6 A schematic diagram of a device registration process in an embodiment of the present disclosure is shown;

[0036] Figure 7 A schematic diagram of a network link topology in an embodiment of the present disclosure is shown;

[0037] Figure 8 A schematic diagram showing the unified interaction between a remote terminal, a relay terminal and a network element device in an embodiment of the present disclosure is shown;

[0038] Fig. 9 A schematic diagram of a network node device encoding device in an embodiment of the present disclosure is shown;

[0039] Fig.10 A schematic diagram of a network topology generating device according to an embodiment of the present disclosure is shown;

[0040] Fig.11 A schematic diagram showing a component module of a network element device in an embodiment of the present disclosure is shown;

[0041] Fig.12 A schematic diagram showing the components of a terminal device according to an embodiment of the present disclosure is shown;

[0042] Fig.13 A structural block diagram of an electronic device according to an embodiment of the present disclosure is shown;

[0043] Fig.14 A schematic diagram of a computer-readable storage medium in an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0044] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that the disclosure will be more comprehensive and complete and to fully convey the concepts of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0045] In addition, the accompanying drawings are only schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.

[0046] For ease of understanding, before introducing the embodiments of the present disclosure, several terms involved in the embodiments of the present disclosure are first explained as follows:

[0047] UE: User Equipment, also known as user terminal or terminal equipment, abbreviated as terminal;

[0048] EID: Electronic Identity, translated as electronic identity identification;

[0049] P-RAN: Proximity Radio Access Network, translated as near-area cellular network;

[0050] P-RAN Anchor: Proximity Radio Access Network, translated as proximity cellular network access node;

[0051] TCP: Transmission Control Protocol, translated as transmission control protocol;

[0052] UDP: User Datagram Protocol, translated as User Datagram Protocol;

[0053] IP: Internet Protocol, translated as Internet Protocol.

[0054] The specific implementation of the embodiment of the present disclosure is described in detail below with reference to the accompanying drawings.

[0055] Figure 1 The following is a schematic diagram of an exemplary communication system architecture to which the network node device encoding method, network topology generation method, and terminal device information reporting method in the embodiments of the present disclosure can be applied. Figure 1 As shown, the system architecture may include a terminal device 10, a network 20 and a network element device 30. The terminal device 10 includes: a remote terminal 101, a relay terminal 102 based on a WiFi protocol and a relay terminal 103 based on a cellular communication protocol (4G or 5G).

[0056] The network 20 is a medium for providing a communication link between the terminal device 10 and the network element device 30, and may be a wired network or a wireless network.

[0057] Optionally, the wireless network or wired network described above uses standard communication technology and / or protocol. The network is usually the Internet, but it can also be any network, including but not limited to a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a mobile, wired or wireless network, a dedicated network or any combination of a virtual private network). In some embodiments, technologies and / or formats including Hyper Text Mark-up Language (HTML), Extensible Markup Language (XML), etc. are used to represent data exchanged through the network. In addition, conventional encryption technologies such as Secure Socket Layer (SSL), Transport Layer Security (TLS), Virtual Private Network (VPN), Internet Protocol Security (IPsec) can also be used to encrypt all or some links. In other embodiments, customized and / or dedicated data communication technologies can also be used to replace or supplement the above data communication technologies.

[0058] The terminal device 10 can be various electronic devices, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, wearable devices, augmented reality devices, virtual reality devices, etc.

[0059] Optionally, the client of the application installed in different terminal devices 10 is the same, or the client of the same type of application based on different operating systems. Based on the different terminal platforms, the specific form of the client of the application can also be different, for example, the application client can be a mobile client, a PC client, etc.

[0060] The network element device 30 may be a base station, a relay or an access point, etc. The base station may be a base station of 5G or later versions (e.g., 5G NR NB), or a base station in other communication systems (e.g., an eNB base station). It should be noted that the specific type of the network side device is not limited in the embodiments of the present disclosure.

[0061] Those skilled in the art will know that Figure 1 The number of terminal devices, networks, and network element devices in the embodiment is only for illustration, and any number of terminal devices, networks, and network element devices may be provided according to actual needs. The embodiments of the present disclosure do not limit this.

[0062] Under the above system architecture, a network node device encoding method is provided in an embodiment of the present disclosure, and the method can be executed by any electronic device with computing and processing capabilities.

[0063] In some embodiments, the network node device encoding method provided in the embodiments of the present disclosure can be executed by the network element device of the above-mentioned system architecture; in other embodiments, the network node device encoding method provided in the embodiments of the present disclosure can be executed by the terminal device in the above-mentioned system architecture; in other embodiments, the network node device encoding method provided in the embodiments of the present disclosure can be implemented by the terminal device and the network element device in the above-mentioned system architecture through interaction; in other embodiments, the network node device encoding method provided in the embodiments of the present disclosure can also be executed by third-party devices such as network management devices.

[0064] Figure 2 A flow chart of a network node device encoding method in an embodiment of the present disclosure is shown as follows: Figure 2 As shown, the network node device encoding method provided in the embodiment of the present disclosure may include the following steps:

[0065] S202, obtaining the network type, device type and device identification of each node device in the target network.

[0066] It should be noted that the target network in the embodiments of the present disclosure may be, but is not limited to, a near-field communication network (P-RAN) formed by combining WiFi D2D multi-hop technology and cellular communication technology. In the embodiments of the present disclosure, each node device may be a terminal device serving as a relay terminal. The relay terminal may be a relay terminal based on the WiFi protocol or a relay terminal based on a cellular communication protocol (4G or 5G).

[0067] In order to achieve unified management of various terminal devices and dynamic monitoring of network links by network-side devices (which may be various network element devices, including but not limited to P-RAN Anchor network elements), it is necessary to encode each node device in the network. In order to distinguish terminal devices using different network protocols in the target network, in the embodiment of the present disclosure, the network type, device type and device identification of each node device are used to generate device coding information of each node device in the target network.

[0068] Optionally, the network type in the embodiments of the present disclosure may include but is not limited to at least one of the following: a cellular network, a WLAN network, a wired network, and a satellite network; the device type in the embodiments of the present disclosure may include but is not limited to at least one of the following: a mobile phone, a computer, a sensor, a wearable device; the device identifier in the embodiments of the present disclosure may be but is not limited to a MAC address.

[0069] S204: Generate device coding information of each node device in the target network according to the network type, device type and device identification of each node device.

[0070] It should be noted that the embodiments of the present disclosure are intended to protect the network type, device type and device identification of each node device to generate device coding information for each node device in the target network, but do not limit the specific coding method. Technical personnel in this field may adopt different coding methods according to actual needs.

[0071] In one embodiment, the above S204 can be specifically implemented by the following steps: performing a hash operation on the network type, device type and device identification of each node device, and using the hash operation result as the device coding information of each node device in the target network.

[0072] Since the hash algorithm can protect data, in this embodiment, a hash operation is performed on the network type, device type and device identification of each node device, and the hash operation result is used as the device coding information of each node device in the target network, which can fully protect the device information of the terminal device from being leaked.

[0073] Based on the same inventive concept, a network topology generation method is also provided in an embodiment of the present disclosure. The method can be executed by any electronic device with computing and processing capabilities.

[0074] In some embodiments, the network topology generation method provided in the embodiments of the present disclosure can be executed by the network element device of the above-mentioned system architecture; in other embodiments, the network node device encoding method provided in the embodiments of the present disclosure can be executed by the terminal device in the above-mentioned system architecture; in other embodiments, the network node device encoding method provided in the embodiments of the present disclosure can be implemented by the terminal device and the network element device in the above-mentioned system architecture through interaction; in other embodiments, the network node device encoding method provided in the embodiments of the present disclosure can also be executed by third-party devices such as network management devices.

[0075] Figure 3 A flow chart of a network topology generation method according to an embodiment of the present disclosure is shown as follows: Figure 3 As shown, the network topology generation method provided in the embodiment of the present disclosure may include the following steps:

[0076] S302, according to the device registration or update request message sent by the terminal device to the network element device, obtain the connection relationship between each node device, wherein the device registration or update request message is added with device coding information of one or more node devices through which the device registration or update request message passes, and the device coding information is coding information generated according to the network type, device type and device identification of each node device;

[0077] S304: Generate a network link topology diagram according to the connection relationship between each node device.

[0078] It should be noted that the terminal device that sends the device registration or update request message in the embodiment of the present disclosure may be a remote terminal. When the remote terminal device accesses the network through the relay terminal (node ​​device), it will report its own device information to the network, usually through a device registration request message or a device update request message. After the device coding information of each node device is generated by the network node device coding method provided in the embodiment of the present disclosure, the device coding information of each node device can be added to the device registration request message or the device update request message during the process of the terminal device sending the device registration request message or the device update request message to the network element device, so as to obtain the connection relationship between each node device according to the device registration or update request message sent by the terminal device to the network element device, and then generate a network link topology diagram according to the connection relationship between each node device.

[0079] Furthermore, in some embodiments, the network topology generation method provided in the embodiments of the present disclosure may also include the following steps:

[0080] S306, dynamically update the generated network link topology map.

[0081] Since the network status is constantly changing, after the network link topology map is generated, the generated network link topology map can be continuously updated according to the network status.

[0082] Based on the same inventive concept, a terminal device information reporting method applied to a network element device side is also provided in the embodiment of the present disclosure. In principle, the method can be executed by any electronic device with computing and processing capabilities.

[0083] Figure 4 A flow chart of a method for reporting terminal device information applied to a network element device in an embodiment of the present disclosure is shown. Figure 4 As shown, the method may include the following steps:

[0084] S402, receiving a device registration or update request message from a terminal device, wherein the device registration or update request message sent by the terminal device to the network element device passes through one or more node devices to reach the network element device, and when the device registration or update request message passes through each node device, the device coding information of the corresponding node device is added to the device registration or update request message, and the device coding information is coding information generated according to the network type, device type and device identification of each node device;

[0085] S404, returning a device registration or update response message to the terminal device.

[0086] It should be noted that the network element device in the embodiment of the present disclosure may be, but is not limited to, a P-RAN Anchor network element used to connect a terminal device to a P-RAN network.

[0087] In some embodiments, the above-mentioned device encoding information is a hash operation result obtained by performing a hash operation on the network type, device type and device identification of each node device.

[0088] In some embodiments, the above-mentioned terminal device information reporting method provided in the embodiments of the present disclosure may also include the following steps: obtaining the connection relationship between each node device based on the received device registration or update request message; generating a network link topology map based on the connection relationship between each node device.

[0089] In some embodiments, the above-mentioned terminal device information reporting method provided in the embodiments of the present disclosure may also include the following steps: dynamically updating the generated network link topology map.

[0090] Based on the same inventive concept, a terminal device information reporting method applied to the terminal device side is also provided in the embodiment of the present disclosure. In principle, the method can be executed by any electronic device with computing and processing capabilities.

[0091] Figure 5 A flow chart of a method for reporting terminal device information applied to a terminal device in an embodiment of the present disclosure is shown. Figure 5 As shown, the method may include the following steps:

[0092] S502, sending a device registration or update request message to a network element device, wherein the device registration or update request message sent by the terminal device passes through one or more node devices to reach the network element device; when the device registration or update request message passes through each node device, the device coding information of the corresponding node device is added to the device registration or update request message, wherein the device coding information is coding information generated according to the network type, device type and device identification of each node device;

[0093] S504: Receive a device registration or update response message returned by the network element device.

[0094] It should be noted that the terminal device that sends the device registration or update request message in the above S502 may be a remote terminal.

[0095] In some embodiments, the above-mentioned device encoding information is a hash operation result obtained by performing a hash operation on the network type, device type and device identification of each node device.

[0096] In some embodiments, the network element device is further used to obtain the connection relationship between each node device according to the received device registration or update request message, and generate a network link topology diagram according to the connection relationship between each node device.

[0097] Figure 6 A schematic diagram of a device registration process in an embodiment of the present disclosure is shown. Figure 6 As shown, a device information reporting module is set on the UE side, and a device coding information generation module and a network link topology generation module are set on the P-RAN Anchor network element. When the UE initiates a device registration or update request message, the UEID of the UE is carried. Each time the device registration or update request message passes through an IP connection node, the UEID of the node device passed through is added to the device identification field of the device registration or update request message; a device identification management information base is established on the P-RAN Anchor network element, and a Hash algorithm is used to calculate the device type and device ID information reported by the UE to generate a unique device identification EID, and the UE device is uniformly managed through the EID.

[0098] The P-RAN Anchor network element parses the device identification field in the device registration or update request message, adopts a graph data structure, establishes the connection relationship between each UE node (i.e., the network link topology graph) according to the order in which the nodes are added, and dynamically updates the connection relationship.

[0099] In the specific implementation, the vertices of the network link topology graph are composed of all EIDs, the edges are generated by the transmission book sequence of the UEID domain, and the weights of the edges are dynamically configured by the network type and the depth of the graph.

[0100] It can be seen that in the embodiments of the present disclosure, by unified coding of node devices, unified management of P-RAN devices and dynamic monitoring of IP links are established on the network side, which can make the hybrid networking of WiFi and cellular indoors become an operator-level operational product.

[0101] Figure 7 A schematic diagram of the network link topology is shown in FIG. Figure 7 As shown, the vertex information is as follows:

[0102] UE1_ID: indicates 4G / 5G relay UE;

[0103] UE1_ID = hash value (00010001 + MAC address);

[0104] UE2_ID: indicates WiFi relay mobile phone type UE;

[0105] UE2_ID = hash value (00100001 + MAC address);

[0106] UE3_ID: indicates WiFi relay mobile phone type UE;

[0107] UE3_ID = hash value (00100001 + MAC address);

[0108] UE4_ID: indicates WiFi remote sensor type UE;

[0109] UE4_ID = hash value (00100100 + MAC address);

[0110] UE5_ID: indicates the WiFi Remote mobile phone type UE;

[0111] UE5_ID = hash value (00100100 + MAC address);

[0112] UE6_ID: indicates the WiFi Remote wearable device type UE;

[0113] UE6_ID = hash value (00101000 + MAC address);

[0114] The vertex set of the graph: {UE1_ID, UE2_ID, UE3_ID, UE4_ID, UE5_ID, UE6_ID, UE7_ID, UE8_ID};

[0115] The edge matrix of the graph is shown in Table 1:

[0116] Table 1

[0117] BTS1_ID UE1_ID UE2_ID UE3_ID UE4_ID UE5_ID UE6_ID UE7_ID UE8_ID BTS1_ID UE1_ID 1 UE2_ID 0.8 UE3_ID 0.7 UE4_ID 0.6 UE5_ID 0.6 UE6_ID 0.6 UE7_ID 0.8 UE8_ID 0.7

[0118] Figure 8 A schematic diagram of the overall interaction between the remote terminal, the relay terminal and the network element device in the embodiment of the present disclosure is shown. Figure 8As shown, after the 4G / 5G relay UE can establish a 4G / 5G connection with the P-RANAnchor network element through a 4G / 5G establishment request message and a 4G / 5G establishment response message, it sends a device registration request message carrying a user ID and a UEID to the P-RAN Anchor network element, and receives a device registration response message returned by the P-RAN Anchor network element; after the WiFi relay UE establishes a WiFi connection with the 4G / 5G relay UE through a WiFi establishment request message and a WiFi establishment response message, it sends a device registration request message carrying a user ID and a UEID to the P-RANAnchor network element through the 4G / 5G relay UE, and receives a device registration response message returned by the P-RANAnchor network element through the 4G / 5G relay UE; after the remote UE establishes a WiFi connection with the WiFi relay UE through a WiFi establishment request message and a WiFi establishment response message, it sends a device registration request message carrying a user ID and a UEID to the P-RANAnchor network element through the WiFi relay UE and the 4G / 5G relay UE. The Anchor network element sends a device registration request message carrying the user ID and UEID, and receives the device registration response message returned by the P-RANAnchor network element through the 4G / 5G relay UE and the 4G / 5G relay UE.

[0119] Based on the same inventive concept, the embodiment of the present disclosure also provides a network node device encoding device, as described in the following embodiment. Since the principle of solving the problem in the device embodiment is similar to that in the above method embodiment, the implementation of the device embodiment can refer to the implementation of the above method embodiment, and the repeated parts will not be repeated.

[0120] Fig. 9 A schematic diagram of a network node device encoding device in an embodiment of the present disclosure is shown. Fig. 9 As shown, the apparatus includes: a device information acquisition module 901 and a device encoding module 902.

[0121] Among them, the device information acquisition module 901 is used to obtain the network type, device type and device identification of each node device in the target network; the device coding module 902 is used to generate the device coding information of each node device in the target network according to the network type, device type and device identification of each node device.

[0122] It should be noted that the above-mentioned device information acquisition module 901 and device encoding module 902 correspond to S202 to S204 in the method embodiment, and the examples and application scenarios implemented by the above-mentioned modules and corresponding steps are the same, but are not limited to the contents disclosed in the above-mentioned method embodiment. It should be noted that the above-mentioned modules as part of the apparatus can be executed in a computer system such as a set of computer executable instructions.

[0123] Based on the same inventive concept, the present disclosure also provides a network topology generation device, as described in the following embodiments. Since the principle of solving the problem in the device embodiment is similar to that in the above method embodiment, the implementation of the device embodiment can refer to the implementation of the above method embodiment, and the repeated parts will not be repeated.

[0124] Fig.10 A schematic diagram of a network topology generating device in an embodiment of the present disclosure is shown. Fig.10 As shown, the device includes: a node device connection relationship acquisition module 1001 and a network topology generation module 1002.

[0125] Among them, the node device connection relationship acquisition module 1001 is used to obtain the connection relationship between each node device according to the device registration or update request message sent by the terminal device to the network element device, wherein the device registration or update request message is added with the device coding information of one or more node devices through which the device registration or update request message passes, and the device coding information is the coding information generated according to the network type, device type and device identification of each node device; the network topology generation module 1002 is used to generate a network link topology diagram according to the connection relationship between each node device.

[0126] It should be noted that the node device connection relationship acquisition module 1001 and the network topology generation module 1002 correspond to S302 to S304 in the method embodiment, and the examples and application scenarios implemented by the modules and the corresponding steps are the same, but are not limited to the contents disclosed in the method embodiment. It should be noted that the modules as part of the device can be executed in a computer system such as a set of computer executable instructions.

[0127] In some embodiments, in the network topology generation device provided in the embodiments of the present disclosure, the network topology generation module 1002 is further used to: dynamically update the generated network link topology map.

[0128] Based on the same inventive concept, the embodiment of the present disclosure also provides a network element device, as described in the following embodiment. Since the principle of solving the problem in the network element device embodiment is similar to that in the above method embodiment, the implementation of the network element device embodiment can refer to the implementation of the above method embodiment, and the repeated parts will not be repeated.

[0129] Fig.11 A schematic diagram of a network element device in an embodiment of the present disclosure is shown. Fig.11 As shown, the network element device includes: a device registration request message receiving module 1101 and a device registration response message sending module 1102 .

[0130] Among them, the device registration request message receiving module 1101 is used to receive the device registration or update request message from the terminal device, wherein the device registration or update request message sent by the terminal device to the network element device passes through one or more node devices to reach the network element device, and when the device registration or update request message passes through a node device each time, the device coding information of the corresponding node device is added to the device registration or update request message, and the device coding information is the coding information generated according to the network type, device type and device identification of each node device; the device registration response message sending module 1102 is used to return the device registration or update response message to the terminal device.

[0131] It should be noted that the device registration request message receiving module 1101 and the device registration response message sending module 1102 correspond to S402 to S404 in the method embodiment, and the examples and application scenarios implemented by the modules and the corresponding steps are the same, but are not limited to the contents disclosed in the method embodiment. It should be noted that the modules as part of the apparatus can be executed in a computer system such as a set of computer executable instructions.

[0132] In some embodiments, the above-mentioned device encoding information is a hash operation result obtained by performing a hash operation on the network type, device type and device identification of each node device.

[0133] In some embodiments, the above-mentioned terminal device information reporting method provided in the embodiments of the present disclosure may also include the following steps: obtaining the connection relationship between each node device based on the received device registration or update request message; generating a network link topology map based on the connection relationship between each node device.

[0134] In some embodiments, the above-mentioned terminal device information reporting method provided in the embodiments of the present disclosure may also include the following steps: dynamically updating the generated network link topology map.

[0135] Based on the same inventive concept, the present disclosure also provides a terminal device in the following embodiments. Since the principle of solving the problem in the terminal device embodiment is similar to that in the above method embodiment, the implementation of the terminal device embodiment can refer to the implementation of the above method embodiment, and the repeated parts will not be repeated.

[0136] Fig.12 A schematic diagram of the components of a terminal device in an embodiment of the present disclosure is shown. Fig.12 As shown, the terminal device includes: a device registration request message sending module 1201 and a device registration response message receiving module 1202.

[0137] Among them, the device registration request message sending module 1201 is used to send a device registration or update request message to the network element device, wherein the device registration or update request message sent by the terminal device passes through one or more node devices to reach the network element device; when the device registration or update request message passes through a node device each time, the device coding information of the corresponding node device is added to the device registration or update request message, wherein the device coding information is the coding information generated according to the network type, device type and device identification of each node device; the device registration response message receiving module 1202 is used to receive the device registration or update response message returned by the network element device.

[0138] It should be noted that the device registration request message sending module 1201 and the device registration response message receiving module 1202 correspond to S502 to S504 in the method embodiment, and the examples and application scenarios implemented by the modules and the corresponding steps are the same, but are not limited to the contents disclosed in the method embodiment. It should be noted that the modules as part of the apparatus can be executed in a computer system such as a set of computer executable instructions.

[0139] In some embodiments, the above-mentioned device encoding information is a hash operation result obtained by performing a hash operation on the network type, device type and device identification of each node device.

[0140] In some embodiments, the network element device is further used to obtain the connection relationship between each node device according to the received device registration or update request message, and generate a network link topology diagram according to the connection relationship between each node device.

[0141] Those skilled in the art will appreciate that various aspects of the present disclosure may be implemented as systems, methods or program products. Therefore, various aspects of the present disclosure may be specifically implemented in the following forms, namely: complete hardware implementation, complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software, which may be collectively referred to herein as "circuits", "modules" or "systems".

[0142] Refer to the following Fig.13 1300 according to this embodiment of the present disclosure is described. Fig.13 The electronic device 1300 shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0143] like Fig.13As shown, the electronic device 1300 is in the form of a general computing device. The components of the electronic device 1300 may include but are not limited to: at least one processing unit 1310, at least one storage unit 1320, and a bus 1330 connecting different system components (including the storage unit 1320 and the processing unit 1310).

[0144] The storage unit stores program codes, which can be executed by the processing unit 1310, so that the processing unit 1310 executes the steps described in the above “Exemplary Method” section of this specification according to various exemplary embodiments of the present disclosure.

[0145] In some embodiments, when the electronic device 1300 in the embodiment of the present disclosure is a network node device encoding device, the processing unit 1310 can execute the following steps of the above method embodiment: obtain the network type, device type and device identification of each node device in the target network; generate device coding information for each node device in the target network according to the network type, device type and device identification of each node device.

[0146] In some embodiments, when the electronic device 1300 in the embodiment of the present disclosure is a network topology generation device, the processing unit 1310 can execute the following steps of the above-mentioned method embodiment: according to the device registration connection request message sent by the terminal device to the network element device, obtain the connection relationship between each node device, wherein the device registration connection request message is added with device coding information of one or more node devices through which the device registration connection request message passes, and the device coding information is coding information generated according to the network type, device type and device identification of each node device; generate a network link topology diagram according to the connection relationship between each node device.

[0147] In some embodiments, when the electronic device 1300 in the embodiment of the present disclosure is a network element device, the processing unit 1310 can execute the following steps of the above method embodiment: receiving a device registration connection request message from a terminal device, wherein the device registration connection request message sent by the terminal device to the network element device passes through one or more node devices to reach the network element device, and when the device registration connection request message passes through a node device each time, the device coding information of the corresponding node device is added to the device registration connection request message, and the device coding information is the coding information generated according to the network type, device type and device identification of each node device; and returning a device registration connection response message to the terminal device.

[0148] In some embodiments, when the electronic device 1300 in the embodiment of the present disclosure is a terminal device, the processing unit 1310 can execute the following steps of the above method embodiment: sending a device registration connection request message to a network element device, wherein the device registration connection request message sent by the terminal device passes through one or more node devices to reach the network element device; when the device registration connection request message passes through a node device each time, the device coding information of the corresponding node device is added to the device registration connection request message, wherein the device coding information is the coding information generated according to the network type, device type and device identification of each node device; and receiving the device registration connection response message returned by the network element device.

[0149] The storage unit 1320 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 13201 and / or a cache storage unit 13202 , and may further include a read-only storage unit (ROM) 13203 .

[0150] The storage unit 1320 may also include a program / utility 13204 having a set (at least one) of program modules 13205, such program modules 13205 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0151] Bus 1330 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0152] The electronic device 1300 may also communicate with one or more external devices 1340 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 1300, and / or communicate with any device that enables the electronic device 1300 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed via an input / output (I / O) interface 1350. Furthermore, the electronic device 1300 may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via a network adapter 1360. As shown, the network adapter 1360 communicates with other modules of the electronic device 1300 via a bus 1330. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 1300, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0153] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation methods of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network element device, etc.) to execute the method according to the implementation methods of the present disclosure.

[0154] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart may be implemented as a computer program product or a computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes any of the above-mentioned methods for sending inactive security configuration information.

[0155] In an exemplary embodiment of the present disclosure, a computer-readable storage medium is further provided, which may be a readable signal medium or a readable storage medium. Fig.14 A schematic diagram of a computer-readable storage medium in an embodiment of the present disclosure is shown. Fig.14 As shown, a program product capable of implementing the above method of the present disclosure is stored on the computer-readable storage medium 1400. In some possible implementations, various aspects of the present disclosure may also be implemented in the form of a program product, which includes a program code. When the program product is run on a terminal device, the program code is used to enable the terminal device to execute the steps according to various exemplary implementations of the present disclosure described in the above “Exemplary Method” section of this specification.

[0156] More specific examples of computer-readable storage media in the present disclosure may include, but are not limited to, an electrical connection having one or more conductors, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0157] In the present disclosure, a computer readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, wherein a readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A readable signal medium may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0158] Alternatively, the program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.

[0159] In a specific implementation, the program code for performing the operations of the present disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., using an Internet service provider to connect through the Internet).

[0160] It should be noted that, although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into multiple modules or units to be embodied.

[0161] In addition, although the steps of the method in the present disclosure are described in a specific order in the drawings, this does not require or imply that the steps must be performed in this specific order, or that all the steps shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps, etc.

[0162] Through the description of the above implementation modes, it is easy for those skilled in the art to understand that the example implementation modes described here can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the implementation mode of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a mobile terminal, or a network element device, etc.) to execute the method according to the implementation mode of the present disclosure.

[0163] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure, which follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are intended to be exemplary only, and the true scope and spirit of the present disclosure are indicated by the appended claims.

Claims

1. A network node device encoding method, characterized in that: include: Obtain the network type, device type and device identification of each node device in the target network; Generate device coding information of each node device in the target network according to the network type, device type and device identification of each node device; Wherein, the method further comprises: In the process of a terminal device sending a device registration request message or a device update request message to a network element device, the device coding information of each node device is added to the device registration request message or the device update request message, so as to obtain the connection relationship between each node device according to the device registration or update request message sent by the terminal device to the network element device, and then generate a network link topology diagram according to the connection relationship between each node device.

2. The network node device encoding method according to claim 1, characterized in that: Generate device coding information of each node device in the target network according to the network type, device type and device identification of each node device, including: A hash operation is performed on the network type, device type and device identification of each node device, and the hash operation result is used as the device coding information of each node device in the target network.

3. The network node device encoding method according to claim 1 or 2, characterized in that: The network type includes at least one of the following: a cellular network, a WLAN network, a wired network, and a satellite network.

4. The network node device encoding method according to claim 1 or 2, characterized in that: The device type includes at least one of the following: a mobile phone, a computer, a sensor, and a wearable device.

5. The network node device encoding method according to claim 1 or 2, characterized in that: The device identifier is a MAC address.

6. A network topology generation method, characterized in that: include: According to the device registration or update request message sent by the terminal device to the network element device, the connection relationship between each node device is obtained, wherein the device registration or update request message is added with the device coding information of one or more node devices through which the device registration or update request message passes, and the device coding information is the coding information generated according to the network type, device type and device identification of each node device; Generate a network link topology diagram based on the connection relationship between each node device.

7. The network topology generation method according to claim 6, characterized in that: The method further comprises: Dynamically update the generated network link topology diagram.

8. A method for reporting terminal device information, characterized in that: Applied to network element equipment, including: Receiving a device registration or update request message from a terminal device, wherein the device registration or update request message sent by the terminal device to the network element device passes through one or more node devices to reach the network element device, and when the device registration or update request message passes through each node device, the device coding information of the corresponding node device is added to the device registration or update request message, and the device coding information is coding information generated according to the network type, device type and device identification of each node device; A device registration or update response message is returned to the terminal device.

9. The method for reporting terminal device information according to claim 8, characterized in that: The method further comprises: Obtaining the connection relationship between each node device according to the received device registration or update request message; Generate a network link topology diagram based on the connection relationship between each node device.

10. The method for reporting terminal device information according to claim 9, characterized in that: The method further comprises: Dynamically update the generated network link topology diagram.

11. The method for reporting terminal device information according to any one of claims 8 to 10, characterized in that: The device encoding information is a hash operation result obtained by performing a hash operation on the network type, device type and device identification of each node device.

12. A method for reporting terminal device information, characterized in that: Applied to terminal equipment, including: Sending a device registration or update request message to a network element device, wherein the device registration or update request message sent by the terminal device reaches the network element device through one or more node devices; when the device registration or update request message passes through each node device, adding device coding information of the corresponding node device to the device registration or update request message, wherein the device coding information is coding information generated according to the network type, device type and device identification of each node device; Receive a device registration or update response message returned by the network element device.

13. The method for reporting terminal device information according to claim 12, characterized in that: The device encoding information is a hash operation result obtained by performing a hash operation on the network type, device type and device identification of each node device.

14. The method for reporting terminal device information according to claim 12, characterized in that: The network element device is also used to obtain the connection relationship between each node device according to the received device registration or update request message, and generate a network link topology diagram according to the connection relationship between each node device.

15. A network node device encoding device, characterized in that: include: The device information acquisition module is used to obtain the network type, device type and device identification of each node device in the target network; A device coding module, used to generate device coding information of each node device in the target network according to the network type, device type and device identification of each node device; Among them, the network node device encoding device is also used to: in the process of the terminal device sending a device registration request message or a device update request message to the network element device, add the device coding information of each node device to the device registration request message or the device update request message, so as to obtain the connection relationship between each node device according to the device registration or update request message sent by the terminal device to the network element device, and then generate a network link topology diagram according to the connection relationship between each node device.

16. A network topology generation device, characterized in that: include: A node device connection relationship acquisition module, used to acquire the connection relationship between each node device according to the device registration or update request message sent by the terminal device to the network element device, wherein the device registration or update request message is added with device coding information of one or more node devices through which the device registration or update request message passes, and the device coding information is coding information generated according to the network type, device type and device identification of each node device; The network topology generation module is used to generate a network link topology diagram based on the connection relationship between each node device.

17. A network element device, characterized in that: include: A device registration request message receiving module, configured to receive a device registration or update request message from a terminal device, wherein the device registration or update request message sent by the terminal device to the network element device passes through one or more node devices to reach the network element device, and when the device registration or update request message passes through each node device, the device coding information of the corresponding node device is added to the device registration or update request message, and the device coding information is coding information generated according to the network type, device type and device identification of each node device; The device registration response message sending module is used to return a device registration or update response message to the terminal device.

18. A terminal device, characterized in that: include: A device registration request message sending module is used to send a device registration or update request message to a network element device, wherein the device registration or update request message sent by the terminal device reaches the network element device through one or more node devices; when the device registration or update request message passes through a node device each time, the device coding information of the corresponding node device is added to the device registration or update request message, wherein the device coding information is coding information generated according to the network type, device type and device identification of each node device; The device registration response message receiving module is used to receive the device registration or update response message returned by the network element device.

19. An electronic device, characterized in that: include: processor; as well as A memory, configured to store executable instructions of the processor; Wherein, the processor is configured to execute the network node device encoding method described in any one of claims 1 to 5, or the network topology generation method described in any one of claims 6 to 7, or the terminal device information reporting method described in any one of claims 8 to 14 by executing the executable instructions.

20. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, it implements the network node device encoding method described in any one of claims 1 to 5, or the network topology generation method described in any one of claims 6 to 7, or the terminal device information reporting method described in any one of claims 8 to 14.

Images