High-cost-performance 5G slice data transmission method and system

Abstract

The invention relates to the technical field of data transmission, and provides a 5G slice data transmission method and system with high cost performance. The method comprises the following steps: when a data reporting condition of a first FTU is reached, the first FTU broadcasts a common reporting message in a ZigBee network; the second FTU returns a common reporting response to the first FTU when receiving the common reporting message and judging that a data cooperative sending condition of the second FTU is reached; the first FTU establishes a data reporting group according to the received common reporting responses; the first FTU carries the equipment identification of each FTU in the data reporting group in a network slice registration request and sends the network slice registration request to an AMF node, so that each FTU in the data reporting group can commonly use the network slice instance to report data; and when the reporting stop condition of each FTU in the data reporting group is reached, stopping data reporting, and canceling distribution of the network slice instances after the idle time exceeds the preset time. According to the invention, the network bandwidth occupation is optimized.

Description

Technical Field

[0001] The present invention relates to the field of data transmission technology, and in particular to a cost-effective 5G slice data transmission method and system. Background Art

[0002] To promote intelligent and efficient management of power distribution in substations and reduce the intensity of traditional operations and maintenance, smart IoT systems have emerged. These systems use converged distribution terminals to upload business data to the IoT platform. As edge devices in the smart IoT system, converged distribution terminals are responsible for collecting information from distribution substations (for example, transformer load conditions, voltage and current parameters of transmission lines, etc.), uploading and receiving data, and performing edge computing (for example, locally processing and analyzing collected data). They can monitor the operating status of distribution substations in real time, providing strong support for fault analysis and data display of substation distribution networks. Converged distribution terminals include distribution transformer supervisory terminal units (TTUs), switchgear terminal units (DTUs), and feeder terminal units (FTUs).

[0003] In existing technologies, each FTU often transmits data independently. However, in the network, due to the uncertainty of the amount of data collected by the FTU, in order to ensure the transmission speed, it is necessary to reserve corresponding bandwidth for each FTU. When the FTU does not need to transmit data, its bandwidth occupancy still exists, which leads to excessive overall bandwidth occupancy.

[0004] In view of this, overcoming the defects of the prior art is an urgent problem to be solved in this technical field. Summary of the Invention

[0005] The technical problem to be solved by the present invention is to provide a cost-effective 5G slice data transmission method and system to optimize network bandwidth occupancy.

[0006] The present invention adopts the following technical solutions: In a first aspect, the present invention provides a cost-effective 5G slice data transmission method. Each FTU stores the collected data locally and determines whether the data reporting conditions are met at preset intervals. When the data reporting conditions of the corresponding feeder terminal device FTU are met, the data is reported. The data reporting method includes: Establish a ZigBee network in advance between multiple FTUs connected to the same base station; When the data reporting conditions of the first FTU are met, the first FTU broadcasts a joint reporting message in the ZigBee network; Upon receiving the joint reporting message, the second FTU determines whether its own data collaborative transmission conditions are met. If it is determined that its own data collaborative transmission conditions are met, it returns a joint reporting response to the first FTU; wherein the joint reporting response carries the device identifier of the second FTU, and the second FTU is an FTU located in the same ZigBee network as the first FTU; The first FTU establishes a data reporting group according to the received common reporting responses; The first FTU carries the device identifier of each FTU in the data reporting group in the network slice registration request and sends it to the AMF node, so that the AMF node allocates a network slice instance to the data reporting group and sends relevant information of the network slice instance to the first FTU; The first FTU sends relevant information of the network slice instance to each FTU in the data reporting group through ZigBee networking, so that each FTU in the data reporting group jointly uses the network slice instance to report data; When the reporting stop condition of each FTU in the data reporting group is met, data reporting is stopped, and the network slice instance is de-allocated after the idle time exceeds the preset time.

[0007] Preferably, the step of pre-establishing a ZigBee network between multiple FTUs connected to the same base station specifically includes: After successfully accessing the base station, the FTU sends an access message to the monitoring master station, which carries the FTU's device identifier and the cell global identifier NCGI; wherein the NCGI is obtained by the FTU during the process of accessing the base station by monitoring the SIB1 message broadcast by the base station; The monitoring master station adds multiple FTUs with the same NCGI to the same network group, assigns a corresponding networking role to each FTU in the network group, and sends the networking role to each FTU in the access response; The FTU switches its own ZigBee role to the networking role according to the networking role in the access response and performs corresponding networking operations to establish a ZigBee network between multiple FTUs accessing the same base station; wherein the networking roles include coordinators and terminal devices.

[0008] Preferably, the performing of corresponding networking operations to establish a ZigBee network between multiple FTUs connected to the same base station specifically includes: The coordinator establishes the PAN network; The terminal device scans the PAN network and sends a network access request to the coordinator in the scanned PAN network; wherein the network access request carries NCGI; The coordinator determines whether the NCGI in the network access request is consistent with the NCGI of its own access base station. If they are consistent, it allocates the network address and network key of the ZigBee network to the terminal device, and carries the network address and network key in the network access permission response to the terminal device, so that the terminal device can use the network address and network key to join the PAN network to realize ZigBee network communication.

[0009] Preferably, the assigning of a corresponding networking role to each FTU in the network group specifically includes: The first FTU added to the network group has a networking role of coordinator, and the subsequent FTUs added to the network group have a networking role of terminal device. Alternatively, the networking role of the FTU with the most resources in the network group is the coordinator, and the networking roles of other FTUs are terminal devices.

[0010] Preferably, the first FTU carries the device identifier of each FTU in the data reporting group in the network slice registration request and sends it to the AMF node, so that the AMF node allocates a network slice instance to the data reporting group and sends the relevant information of the network slice instance to the first FTU, specifically including: The network slice registration request carries the subscribed NSSAI and the device identifier of each FTU in the data reporting group, and sends the network slice request to the AMF node; The AMF node sends a query request to the NSSF node according to the network slice registration request, where the query request includes the NSSAI and the device identifier of each FTU; The NSSF node performs access verification based on the query request. If the verification allows access, the size of the required resources is determined based on the device identifier of each FTU. Based on the size of the required resources, the corresponding network slice instance is allocated to the data reporting group, and the slice instance identifier SNSSAI of the network slice instance and the AMF node identifier of the slice instance are carried in the network slice registration response and sent to the first FTU.

[0011] Preferably, each FTU in the data reporting group jointly uses the network slice instance to report data, specifically including: Each FTU sends a session request to the AMF node; wherein the session request carries the slice instance identifier SNSSAI of the network slice instance, the AMF node identifier of the slice instance, and the data network name DNN, so that the AMF node establishes a PDU session for the FTU according to the session request; Each FTU reports data through the corresponding PDU session.

[0012] Preferably, the data reporting condition of the first FTU is met, specifically: The interval between the current moment and the last data reporting moment of the first FTU is greater than the first preset interval, or the data size of the first FTU itself is greater than the first preset size.

[0013] Preferably, the reporting stop conditions of each FTU are met, specifically: The data reporting duration exceeds the preset duration, and the data size stored locally in the FTU is smaller than the second preset size.

[0014] In a second aspect, the present invention further provides a cost-effective 5G slice data transmission device, which is used to implement the cost-effective 5G slice data transmission method described in the first aspect, and the device includes: At least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the processor to execute the cost-effective 5G slice data transmission method described in the first aspect.

[0015] In a third aspect, the present invention further provides a non-volatile computer storage medium, wherein the computer storage medium stores computer-executable instructions, and the computer-executable instructions are executed by one or more processors to complete the method described in the first aspect.

[0016] In a fourth aspect, a chip is provided, comprising: a processor and an interface, for calling and running a computer program stored in a memory from a memory, and executing any method of the first aspect.

[0017] In a fifth aspect, a computer program product comprising instructions is provided, which, when executed on a computer or a processor, causes the computer or the processor to execute any of the methods of the first aspect.

[0018] In the sixth aspect, a cost-effective 5G slice data transmission system is provided, comprising multiple cost-effective 5G slice data transmission devices of the second aspect, i.e., multiple FTUs; the multiple FTUs use the cost-effective 5G slice data transmission method described in the first aspect to report data.

[0019] The present invention enables each FTU to store data locally first, and then report the data when certain conditions (such as a large amount of data) are met. Before reporting data, it first queries other FTUs through ZigBee networking so that the FTUs in need can form a data reporting group together, thereby using the same network slice instance for data reporting. The bandwidth resources of the network slice instance can be used by any FTU in the data reporting group, so there is no need to reserve bandwidth for each FTU separately, reducing the overall bandwidth usage. Moreover, after the data reporting of each FTU in the data reporting group is completed, the network slice instance is canceled, thereby releasing resources for other data transmission, thereby optimizing network bandwidth occupancy. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] To more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the embodiments of the present invention. Obviously, the drawings described below are only some embodiments of the present invention. Those skilled in the art can also derive other drawings based on these drawings without inventive effort.

[0021] Figure 1 This is a flowchart of a cost-effective 5G slice data transmission method provided by an embodiment of the present invention; Figure 2 This is a schematic diagram of the network architecture of a cost-effective 5G slice data transmission method provided by an embodiment of the present invention; Figure 3 is a schematic diagram of a cost-effective 5G slice data transmission method provided by an embodiment of the present invention; Figure 4 is a schematic diagram of a cost-effective 5G slice data transmission method provided by an embodiment of the present invention; Figure 5 This is a flowchart of a cost-effective 5G slice data transmission method provided by an embodiment of the present invention; Figure 6 This is a signaling diagram of a cost-effective 5G slice data transmission method provided by an embodiment of the present invention; Figure 7 This is a flowchart of a cost-effective 5G slice data transmission method provided by an embodiment of the present invention; Figure 8 This is a signaling diagram of a cost-effective 5G slice data transmission method provided by an embodiment of the present invention; Figure 9 This is a flowchart of a cost-effective 5G slice data transmission method provided by an embodiment of the present invention; Figure 10is a schematic diagram of a cost-effective 5G slice data transmission method provided by an embodiment of the present invention; Figure 11 This is a flowchart of a cost-effective 5G slice data transmission method provided by an embodiment of the present invention; Figure 12 This is a signaling diagram of a cost-effective 5G slice data transmission method provided by an embodiment of the present invention; Figure 13 This is a schematic diagram of the architecture of a cost-effective 5G slice data transmission device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0022] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0023] Unless the context requires otherwise, throughout the specification and claims, the term "including" is to be interpreted as meaning open inclusion, that is, "including, but not limited to". In the description of the specification, the terms "one embodiment", "some embodiments", "exemplary embodiments", "example", "specific example" or "some examples" and the like are intended to indicate that the specific features, structures, materials or characteristics associated with the embodiment or example are included in at least one embodiment or example of the present disclosure. The schematic representation of the above terms does not necessarily refer to the same embodiment or example. In addition, the specific features, structures, materials or characteristics may be included in any one or more embodiments or examples in any appropriate manner, that is, although they may be carried in the embodiments or examples of the above terms due to reasons such as the order and position of appearance, it is not limited to that they can be carried in combination by one embodiment or example.

[0024] In the description of the present invention, the terms "first" and "second" are used for descriptive purposes only, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of the embodiments of the present disclosure, unless otherwise specified, "multiple" means two or more. In addition, for example, the description may also use the method of adding "A" and "B" at the end to describe the same type of nouns as two independent individuals. In this case, the corresponding features defined as "A" and "B" are only used to distinguish the description purposes of the same type of individuals, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated.

[0025] In the description of the present invention, the expression "A and / or B" (where A and B are used to formally represent specific characteristic contents) is involved, and the corresponding expressions include the following three combinations: only A, only B, and a combination of A and B.

[0026] As used herein, "about," "substantially," or "approximately" includes the stated value and an average value that is within an acceptable range of deviation from the particular value as determined by one of ordinary skill in the art taking into account the measurements in question and errors associated with measurement of the particular quantity (i.e., limitations of the measurement system).

[0027] In addition, the technical features involved in the various embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other.

[0028] Embodiment 1: Considering that there are often some data in FTU that do not have high real-time requirements, that is, these data are often not used for real-time alarms, but for later analysis of alarm causes and tracing and debugging of equipment failure causes, for this type of data, embodiment 1 of the present invention provides a cost-effective 5G slice data transmission method. Each FTU stores the collected data locally and determines whether the data reporting conditions are met at every preset period. When the data reporting conditions of the corresponding feeder terminal device FTU are met, the data is reported. Figure 1 and Figure 2 As shown, the data reporting methods include: In step 201, a ZigBee network is pre-established between multiple FTUs connected to the same base station. The preset period is obtained by those skilled in the art based on empirical analysis.

[0029] In step 202, when the data reporting condition of the first FTU is met, the first FTU broadcasts a common reporting message in the ZigBee network.

[0030] In step 203, upon receiving the joint reporting message, the second FTU determines whether its own conditions for coordinated data transmission are met. If so, it returns a joint reporting response to the first FTU. The joint reporting response carries the device identifier of the second FTU, which is located in the same ZigBee network as the first FTU. ZigBee is a wireless network protocol for low-speed, short-range transmission. Each FTU is pre-installed with a module supporting ZigBee communication functions, and this module supports switching networking roles to perform the functions of the corresponding networking role. In actual use, the FTU's device identifier can be the FTU's Subscription Concealed Identifier (SUCI). If the second FTU determines that its own conditions for coordinated data transmission are not met, it does not return the joint reporting response to the first FTU, or instead returns a joint reporting rejection message to the first FTU.

[0031] In step 204, the first FTU establishes a data reporting group based on the received common reporting responses; that is, the device identifiers of the FTUs carried in the common reporting responses are added to a data reporting group to represent that these FTUs need to report data together.

[0032] In step 205, the first FTU carries the device identifier of each FTU in the data reporting group in a network slice registration request and sends it to the Access and Mobility Management Function (AMF) node, so that the AMF node allocates a network slice instance to the data reporting group and sends relevant information about the network slice instance to the first FTU. In actual use, the network slice registration request also carries a preset identifier to indicate that the request contains device identifiers of multiple FTUs. The position of the preset identifier in the network slice registration request can be determined by those skilled in the art based on empirical analysis, such as using the first bit in the reserved field in the network slice registration request as an identifier. When the value of the identifier is 1, it indicates that the preset identifier is carried, and when the value of the identifier is 0, it indicates that the preset identifier is not carried. In addition, the network slice registration request also carries the number of FTUs in the data reporting group, so that the device identifiers of each FTU of the corresponding length can be read according to the number.

[0033] In step 206, the first FTU sends the relevant information of the network slice instance to each FTU in the data reporting group through ZigBee networking, so that each FTU in the data reporting group can jointly use the network slice instance to report data; the relevant information of the network slice instance can be the SNSSAI of the network slice instance and the Temp.ID of the corresponding AMF node.

[0034] In step 207, when the reporting stop condition of each FTU in the data reporting group is met, data reporting is stopped, and the network slice instance is de-allocated after the idle time exceeds the preset time to release resources and prepare for the subsequent data transmission of the data reporting group under other base stations until the data reporting condition of the next FTU is met, and the network slice instance is reallocated. The preset time is obtained by those skilled in the art based on empirical analysis. The data reporting condition, data collaborative transmission condition and reporting stop condition are all obtained by those skilled in the art based on demand analysis, wherein each condition can be set according to the size of the locally stored data volume, such as when the locally stored data volume is greater than the first data volume, the data reporting condition is met; when the locally stored data volume is greater than the second data volume, the data collaborative transmission condition is met; when the locally stored data volume is less than the third data volume, the reporting stop condition is met. The first data volume is greater than the second data volume, and the second data volume is greater than the third data volume.

[0035] In an actual application scenario, the data reporting condition for the first FTU is met when: the interval between the current time and the last data reporting time of the first FTU is greater than a first preset interval, or the data size of the first FTU itself is greater than a first preset size. The first preset interval and the first preset size are determined by those skilled in the art based on empirical analysis.

[0036] The reporting stop condition of each FTU is met, specifically: the data reporting duration exceeds the preset duration, and the data size stored locally by the FTU is less than a second preset size. The preset duration and the second preset size are obtained by those skilled in the art based on empirical analysis.

[0037] The data coordinated transmission condition is met when: the interval between the current time and the last data reporting time of the data unit is greater than a second preset interval, or the size of the stored data of the data unit is greater than a third preset size. The first preset size is greater than the third preset size, and the third preset size is greater than the second preset size. The first preset interval is greater than the second preset interval.

[0038] This embodiment enables each FTU to store data locally first, and then report the data when certain conditions (such as a large amount of data) are met. Before reporting data, it first queries other FTUs through ZigBee networking so that the FTUs in need can form a data reporting group together, thereby using the same network slice instance for data reporting. The bandwidth resources of the network slice instance can be used by any FTU in the data reporting group, so there is no need to reserve bandwidth for each FTU separately, reducing the overall bandwidth usage. Moreover, after the data reporting of each FTU in the data reporting group is completed, the network slice instance is canceled to release resources for other data transmission, thereby optimizing network bandwidth occupancy.

[0039] This embodiment also has a deeper consideration: this implementation method can, on the one hand, meet the reporting needs of each FTU. That is, when the corresponding FTU has a large amount of data, it can quickly report data to ensure that its own storage space can be released in time for subsequent data collection and storage. On the other hand, this one-call-hundred-response approach (that is, when an FTU has a reporting need, other FTUs report data together with it) can reduce the number of network slice instance allocations and reduce resource consumption caused by frequent dynamic allocation and cancellation of network slice instances. In addition, the first FTU requests relevant information about the network slice instance from the AMF, which is then sent to other FTUs in the data reporting group via the ZigBee network. This allows all FTUs in the data reporting group to obtain the network slice instance with a single network slice registration request, without requiring each FTU to make a separate network slice registration request. This achieves the effect of partially replacing 5G network functions with a local ZigBee network, thereby reducing bandwidth usage during the request process.

[0040] It should be noted here that this embodiment is described for data with low real-time requirements. For data with higher real-time requirements, fixed network slice instances are still used for real-time data transmission. Figure 2 Each FTU in the 5G network is connected to a 5G base station (generation node B, referred to as gNB), and is connected to the AMF node through the base station. Figure 2 For the clarity of the accompanying drawings, only the connection relationship of one FTU is schematically presented. It should be understood that in actual use, the connection relationship between each FTU and the AMF node and gNB is the same.

[0041] Figure 2The 5G network in the network includes: Network Storage Function (NF Repository Function, abbreviated as: NRF) node, Network Slice Selection Function (Network Slice Selection Function, abbreviated as: NSSF) node, Authentication Service Function (Authentication Server Function, abbreviated as: AUSF) node, Unified Data Management Function (Unified Data Management, abbreviated as: UDM) node, Network Data Analysis Function (Network Data Analytics Function, abbreviated as: NWDAF) node, AMF node, Session Management Function (Session Management Function, SMF) node, Policy Control Function (Policy Control Function, abbreviated as: PCF) node, Network Exposure Function (Network Exposure Function, abbreviated as: NEF) node, Application Function (Application Function, abbreviated as: AF) node, User Plane Function (User plane Function, abbreviated as: UPF) node and Data Network (Data Network, abbreviated as: DN).

[0042] In some practical application scenarios, the network slice instance can be realized by the 5G network function on the operator side, or a dedicated 5G network for the power grid can be set up, and the dedicated 5G network can provide the network slice instance, such as Figure 3 As shown, Figure 3 Three transmission methods (a), (b), and (c) are shown. Method (a) directly provides network slices and transmits data through the dedicated power grid network. In this method, the dedicated power grid network and the operator's 5G network reuse the same base station. Figure 4 As shown in the figure, public network service data is forwarded by the base station to the operator's network for transmission, while power grid service data is forwarded by the base station to the power grid's dedicated network for transmission. In method (b), the operator's 5G network provides network slicing, while in method (c), the operator provides network slicing, which transmits data to the power grid's dedicated network, and then reaches the monitoring master station through the power grid's dedicated network.

[0043] In a specific application scenario, the ZigBee network is pre-established between multiple FTUs connected to the same base station, such as Figure 5 and Figure 6 As shown, specifically including: In step 301, after successfully accessing the base station, the FTU sends an access message to the monitoring master station, which carries the FTU's device identifier and cell global identifier (NR Cell Global Identifier, abbreviated as: NCGI); wherein, the NCGI is obtained by the FTU during the process of accessing the base station by monitoring the SIB1 message broadcast by the base station, that is, the base station broadcasts the SIB1 message at a fixed time, and after the surrounding FTUs receive the SIB1 message, they obtain the NCGI from the SIB1 message and use the NCGI to request access to the base station; for a region, it can be understood that a base station has a unique NCGI.

[0044] The monitoring master station can be understood as a pre-set server, which allows the FTU to use low-speed bandwidth to transmit messages before the FTU is registered on the 5G network.

[0045] In step 302, the monitoring master adds multiple FTUs with the same NCGI to the same network group, assigns each FTU a corresponding networking role, and sends the networking role to each FTU in an access response. In practice, the networking role is represented in the access response as a 2-bit roleID: roleID=0 represents the coordinator, roleID=1 represents the terminal device, and roleID=2 represents the router.

[0046] In step 303, the FTU switches its own ZigBee role to the networking role in the access response and performs corresponding networking operations to establish a ZigBee network between multiple FTUs connected to the same base station; wherein the networking roles include coordinators and terminal devices. The coordinator is used to establish a PAN network, and the terminal devices join the PAN network, thereby forming a star network centered on the coordinator. At this time, the corresponding networking operations are performed to establish a ZigBee network between multiple FTUs connected to the same base station, such as Figure 7 and Figure 8 As shown, specifically including: In step 401 , the coordinator establishes a personal area network (PAN).

[0047] In step 402, the terminal device scans the PAN network and sends a network access request to the coordinator in the scanned PAN network; wherein the network access request carries the NCGI, specifically: carries the NCGI of the base station to which the terminal device is connected.

[0048] In step 403, the coordinator determines whether the NCGI in the network access request is consistent with the NCGI of the base station to which it accesses. If they are consistent, the coordinator allocates the network address and network key of the ZigBee network to the terminal device, and carries the network address and network key in the network access permission response and sends it to the terminal device, so that the terminal device can use the network address and network key to join the PAN network to achieve ZigBee network communication. When the NCGI of the network access request is consistent with the NCGI of the base station to which the coordinator accesses itself, it can be considered that the sender of the network access request and the coordinator are located in the same base station. When the NCGI of the network access request is inconsistent with the NCGI of the base station to which the coordinator accesses itself, the network address and network key are not allocated to the terminal device.

[0049] In some specific application scenarios, the allocation of corresponding networking roles to each FTU in the network group specifically includes: The networking role of the first FTU added to the network group is the coordinator, and the networking role of the FTUs added to the network group subsequently is the terminal device.

[0050] Alternatively, the networking role of the FTU with the most resources in the network group is the coordinator, and the networking roles of other FTUs are terminal devices; wherein the resources of each FTU can be pre-stored in the monitoring master station, such as storing the correspondence between the resources and the device identification of the FTU in the monitoring master station.

[0051] Alternatively, the FTU closest to the base station in the network group plays the role of coordinator, and the other FTUs play the role of terminal devices. The distance between each FTU and the base station is determined by the position of each FTU and the base station. The position of the FTU can be entered and stored in the monitoring master station when the commissioning personnel install the FTU. The position of the base station can be provided by a third party (i.e., the network provider).

[0052] In actual use, since the coverage range of the PAN network is relatively small (usually less than 10m), while the network coverage range of the base station is relatively large, often reaching 100~350m, the coordinator alone may not be able to cover all terminal devices under the base station. Therefore, in a preferred embodiment, the monitoring master station makes the FTU closest to the corresponding base station (i.e., the base station to which each FTU in the network group is connected) the coordinator according to the location of each base station and each FTU, and assigns networking roles to other FTUs according to the preset strategy; among them, the networking roles of other FTUs are routers or terminal devices.

[0053] The preset strategy is manifested as: constructing a mathematical model, solving the mathematical model, and obtaining the networking roles of other FTUs.

[0054] The objective function of the mathematical model is:

[0055] Where N is the number of FTUs to be assigned networking roles in a network group; is the networking role of the i-th FTU. When the networking role of the i-th FTU is a router, ; When the networking role of the i-th FTU is a terminal device, The objective function can be understood as minimizing the number of allocated routers.

[0056] The constraint function of the mathematical model is:

[0057] Among them, P is the set of FTUs whose networking roles are coordinators and routers, and Q is the set of FTUs whose networking roles are terminal devices. is the connectivity factor between the pth FTU in P and the coordinator. When the distance between every two connected FTUs on the connectivity line between the pth FTU and the coordinator is less than or equal to the preset distance, ;otherwise, ; Among them, when the pth FTU in P is the coordinator, The preset distance is obtained by those skilled in the art based on empirical analysis. The preset distance is less than or equal to the effective network coverage range of the coordinator and less than or equal to the effective network coverage range of the router. In actual use, the The value of is obtained by establishing edges for FTUs in P whose distances between each other are less than or equal to the preset distance, and then judging whether the pth FTU can be connected to the coordinator through one or more edges. If it can be connected, then ,otherwise, .

[0058]

[0059] in, is the pth FTU in P and The distance factor between the qth FTU in P and When the distance between the qth FTU in is less than or equal to the preset distance, ;otherwise, .

[0060] The constraint function can be understood as ensuring that each terminal device is located within the network coverage of at least one router or coordinator, and ensuring that each router is located within the network coverage of at least one other router or coordinator.

[0061] In an optional embodiment, the first FTU carries the device identifier of each FTU in the data reporting group in the network slice registration request and sends it to the AMF node, so that the AMF node allocates a network slice instance to the data reporting group and sends the relevant information of the network slice instance to the first FTU, such as Figure 9 As shown, specifically including: In step 501, the network slice registration request carries the signed NSSAI (full name: Network Slice Selection Assistance Information) and the device identifier of each FTU in the data reporting group, and sends the network slice request to the AMF node.

[0062] In step 502, the AMF node sends a query request to the Network Slice Selection Function (NSSF) node according to the network slice registration request, and the query request includes the NSSAI and the device identifier of each FTU.

[0063] In step 503, the NSSF node performs access verification according to the query request. If the verification allows access (i.e., verifies whether the NSSAI has been registered and verifies whether each FTU is a device that can use the NSSAI, etc.), the size of the required resources is determined according to the device identifier of each FTU. According to the size of the required resources, the corresponding network slice instance is allocated to the data reporting group, and the slice instance identifier SNSSAI of the network slice instance and the AMF node identifier of the slice instance are carried in the network slice registration response and sent to the first FTU. The determination of the size of the required resources according to the device identifier of each FTU can be ,in, and is a resource size preset by those skilled in the art, is the number of FTUs identified by the equipment identification of each FTU, The size of the required resources is matched with the corresponding network slice template according to the resource size, thereby establishing and allocating the corresponding network slice instance. In an optional embodiment, the message of the network slice registration request can be as follows: Figure 10As shown, bit 0 of the second byte in the Registration Request message is set to 1, indicating that it carries a preset identifier. The requested NSSAI is stored in bytes 14 to n, with the total length of the requested S-NSSAI or S-NSSAIs stored in byte 15. The value of n is determined by the length of the NSSAI. The total length of all carried SUCIs is stored in byte n+1, and the SUCIs of each FTU in the data reporting group are stored in bytes n+2 to m. A SUCI occupies 8 bytes, and the value of m is determined by the length of all SUCIs.

[0064] In a specific application scenario, each FTU in the data reporting group uses the network slice instance to report data, such as Figure 11 As shown, specifically including: In step 601, each FTU sends a session request to the AMF node; wherein, the session request carries the slice instance identifier SNSSAI (full name in English: Single Network Slice Selection Assistance Information) of the network slice instance, the AMF node identifier of the slice instance and the data network name (Data Network Name, abbreviated as: DNN), so that the AMF node establishes a PDU session for the FTU according to the session request.

[0065] In step 602, each FTU reports data through the corresponding PDU session. The PDU session is managed based on the network slice instance, and the network resources of the network slice instance are used for data transmission. It should be noted here that the network slice request is sent to the AMF node, which is sent to the default AMF node. The default AMF node is used to interact with the NSSF node to obtain the AMF node identifier of the AMF node serving the network slice instance. The AMF node serving the network slice instance may not be the same node as the default AMF node. In the subsequent process of using the network slice instance for data transmission (i.e., in step 601), the data is sent to the AMF node corresponding to the AMF node identifier for transmission based on the AMF node identifier. In actual use, the AMF node identifier is also called the Temp.ID of the AMF node. Figure 12 As shown, assuming that the default AMF node is AMF1, after AMF1 interaction, the Temp.ID of AMF2 is returned, then in step 601, a session request is sent to AMF2.

[0066] Example 2: like Figure 13, is a schematic diagram of the architecture of a cost-effective 5G slice data transmission device according to an embodiment of the present invention. The cost-effective 5G slice data transmission device according to this embodiment includes one or more processors 21 and a memory 22. Figure 13 A processor 21 is taken as an example.

[0067] The processor 21 and the memory 22 may be connected via a bus or other means. Figure 13 The bus connection is taken as an example.

[0068] The memory 22, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs and non-volatile computer executable programs, such as the cost-effective 5G slice data transmission method in Example 1. The processor 21 executes the cost-effective 5G slice data transmission method by running the non-volatile software programs and instructions stored in the memory 22.

[0069] The memory 22 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state memory device. In some embodiments, the memory 22 may optionally include a memory remotely located relative to the processor 21, and such remote memory may be connected to the processor 21 via a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0070] The program instructions / modules are stored in the memory 22, and when executed by the one or more processors 21, the cost-effective 5G slice data transmission method in the above-mentioned embodiment 1 is executed.

[0071] This embodiment also provides a cost-effective 5G slice data transmission system, including multiple FTUs; the multiple FTUs use the cost-effective 5G slice data transmission method described in Example 1 to report data.

[0072] It is worth noting that the information interaction, execution process, etc. between the modules and units within the above-mentioned devices and systems are based on the same concept as the processing method embodiment of the present invention. The specific content can be found in the description of the method embodiment of the present invention and will not be repeated here.

[0073] Those skilled in the art will understand that all or part of the steps in the various methods of the embodiments can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium, which may include: read-only memory (ROM), random access memory (RAM), a disk or an optical disk, etc.

[0074] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A cost-effective 5G slice data transmission method, characterized in that: Each FTU stores the collected data locally and determines whether the data reporting conditions are met at preset intervals. When the data reporting conditions of the corresponding feeder terminal equipment FTU are met, the data is reported. The data reporting method includes: Establish a ZigBee network in advance between multiple FTUs connected to the same base station; When the data reporting condition of the first FTU is met, the first FTU broadcasts a joint reporting message in the ZigBee network; Upon receiving the joint reporting message, the second FTU determines whether its own data collaborative transmission conditions are met. If it is determined that its own data collaborative transmission conditions are met, it returns a joint reporting response to the first FTU; wherein the joint reporting response carries the device identifier of the second FTU, and the second FTU is an FTU located in the same ZigBee network as the first FTU; The first FTU establishes a data reporting group according to the received common reporting responses; The first FTU carries the device identifier of each FTU in the data reporting group in the network slice registration request and sends it to the AMF node, so that the AMF node allocates a network slice instance to the data reporting group and sends relevant information of the network slice instance to the first FTU; The first FTU sends relevant information of the network slice instance to each FTU in the data reporting group through ZigBee networking, so that each FTU in the data reporting group jointly uses the network slice instance to report data; When the reporting stop condition of each FTU in the data reporting group is met, data reporting is stopped, and the network slice instance is de-allocated after the idle time exceeds the preset time.

2. The cost-effective 5G slice data transmission method according to claim 1, characterized in that: The step of pre-establishing a ZigBee network between multiple FTUs connected to the same base station specifically includes: After successfully accessing the base station, the FTU sends an access message to the monitoring master station, which carries the FTU's device identifier and the cell global identifier NCGI; wherein the NCGI is obtained by the FTU during the process of accessing the base station by monitoring the SIB1 message broadcast by the base station; The monitoring master station adds multiple FTUs with the same NCGI to the same network group, assigns a corresponding networking role to each FTU in the network group, and sends the networking role to each FTU in an access response; The FTU switches its own ZigBee role to the networking role according to the networking role in the access response and performs corresponding networking operations to establish a ZigBee network between multiple FTUs accessing the same base station; wherein the networking roles include coordinators and terminal devices.

3. The cost-effective 5G slice data transmission method according to claim 2, characterized in that: The execution of corresponding networking operations to establish a ZigBee network between multiple FTUs connected to the same base station specifically includes: The coordinator establishes the PAN network; The terminal device scans the PAN network and sends a network access request to the coordinator in the scanned PAN network; wherein the network access request carries NCGI; The coordinator determines whether the NCGI in the network access request is consistent with the NCGI of its own access base station. If they are consistent, it allocates the network address and network key of the ZigBee network to the terminal device, and carries the network address and network key in the network access permission response to the terminal device, so that the terminal device can use the network address and network key to join the PAN network to realize ZigBee network communication.

4. The cost-effective 5G slice data transmission method according to claim 2, characterized in that: The allocation of corresponding networking roles to each FTU in the network group specifically includes: The first FTU added to the network group has a networking role of coordinator, and the subsequent FTUs added to the network group have a networking role of terminal device. Alternatively, the networking role of the FTU with the most resources in the network group is the coordinator, and the networking roles of other FTUs are terminal devices.

5. The cost-effective 5G slice data transmission method according to claim 1, characterized in that: The first FTU carries the device identifier of each FTU in the data reporting group in the network slice registration request and sends it to the AMF node, so that the AMF node allocates a network slice instance to the data reporting group and sends the relevant information of the network slice instance to the first FTU, specifically including: The network slice registration request carries the subscribed NSSAI and the device identifier of each FTU in the data reporting group, and sends the network slice request to the AMF node; The AMF node sends a query request to the NSSF node according to the network slice registration request, where the query request includes the NSSAI and the device identifier of each FTU; The NSSF node performs access verification based on the query request. If the verification allows access, the size of the required resources is determined based on the device identifier of each FTU. Based on the size of the required resources, the corresponding network slice instance is allocated to the data reporting group, and the slice instance identifier SNSSAI of the network slice instance and the AMF node identifier of the slice instance are carried in the network slice registration response and sent to the first FTU.

6. The cost-effective 5G slice data transmission method according to claim 5, characterized in that: Each FTU in the data reporting group jointly uses the network slice instance to report data, specifically including: Each FTU sends a session request to the AMF node; wherein the session request carries the slice instance identifier SNSSAI of the network slice instance, the AMF node identifier of the slice instance, and the data network name DNN, so that the AMF node establishes a PDU session for the FTU according to the session request; Each FTU reports data through the corresponding PDU session.

7. The cost-effective 5G slice data transmission method according to any one of claims 1 to 6, characterized in that: The data reporting conditions of the first FTU are met, specifically: The interval between the current moment and the last data reporting moment of the first FTU is greater than the first preset interval, or the data size of the first FTU itself is greater than the first preset size.

8. The cost-effective 5G slice data transmission method according to any one of claims 1 to 6, characterized in that: The reporting stop conditions of each FTU are met, specifically: The data reporting duration exceeds the preset duration, and the data size stored locally in the FTU is smaller than the second preset size.

9. A non-volatile computer storage medium, characterized in that The computer storage medium stores computer-executable instructions, which are executed by one or more processors to complete the cost-effective 5G slice data transmission method described in any one of claims 1-8.

10. A cost-effective 5G slice data transmission system, characterized in that: It includes multiple FTUs; the multiple FTUs use the cost-effective 5G slice data transmission method described in any one of claims 1-8 to report data.

Images