A cost-effective 5G slicing data transmission method and system

Abstract

This invention relates to the field of data transmission technology, providing a cost-effective 5G slice data transmission method and system. The method includes: when the data reporting conditions of a first FTU are met, the first FTU broadcasts a joint reporting message in the ZigBee network; when a second FTU receives the joint reporting message and determines that its own data collaborative transmission conditions are met, it returns a joint reporting response to the first FTU; the first FTU establishes a data reporting group based on the received joint reporting responses; the first FTU sends the device identifiers of each FTU in the data reporting group to the AMF node in a network slice registration request, so that each FTU in the data reporting group can jointly use the network slice instance for data reporting; when the reporting stop condition of each FTU in the data reporting group is met, data reporting stops, and the network slice instance is canceled after the idle time exceeds a preset time. This invention optimizes network bandwidth utilization.

Description

Technical Field

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

[0002] To promote intelligent and efficient management of power distribution in transformer substations and reduce the intensity of traditional operation and maintenance, smart IoT systems have emerged. These systems use integrated distribution terminals to upload business data to the IoT platform. As edge devices within the smart IoT system, these integrated distribution terminals are responsible for information collection from the distribution substations (e.g., transformer load status, voltage and current parameters of transmission lines), uploading and receiving data, and edge computing (e.g., processing and analyzing the collected data locally). They can monitor the operational status of the distribution substations in real time, providing strong support for fault diagnosis and data display in the distribution network. Integrated distribution terminals include Distribution Transformer Supervisory Terminal Units (TTUs), Distribution Terminal Units (DTUs), and Feeder Terminal Units (FTUs).

[0003] In existing technologies, each FTU often transmits data independently. However, due to the uncertainty of the amount of data collected by the FTU in the network, 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 usage still exists, which leads to excessive overall bandwidth usage.

[0004] Therefore, overcoming the shortcomings of the existing technology 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 usage.

[0006] The present invention adopts the following technical solution:

[0007] In a first aspect, the present invention provides a cost-effective 5G slice data transmission method, wherein 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:

[0008] A ZigBee network is pre-established among multiple FTUs connected to the same base station;

[0009] When the data reporting conditions of the first FTU are met, the first FTU broadcasts a joint reporting message in the ZigBee network;

[0010] When the second FTU receives the joint reporting message, it determines whether its own data collaborative transmission conditions have been met. If it determines that its own data collaborative transmission conditions have been met, it returns a joint reporting response to the first FTU. The joint reporting response carries the device identifier of the second FTU, which is an FTU located in the same ZigBee network as the first FTU.

[0011] The first FTU establishes a data reporting group based on the received common reporting responses;

[0012] The first FTU sends the device identifier of each FTU in the data reporting group to the AMF node in the network slice registration request, so that the AMF node can allocate a network slice instance to the data reporting group and send the relevant information of the network slice instance to the first FTU.

[0013] 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 use the network slice instance to report data.

[0014] When the reporting stop condition of each FTU in the data reporting group is met, data reporting stops, and the network slice instance is canceled after the idle time exceeds a preset time.

[0015] Preferably, the step of pre-establishing a ZigBee network among multiple FTUs accessing the same base station specifically includes:

[0016] 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 (NCGI). The NCGI is obtained by the FTU by listening to the SIB1 message broadcast by the base station during the access process.

[0017] The monitoring master station adds multiple FTUs with the same NCGI to the same network group, assigns corresponding networking roles to each FTU in the network group, and sends the networking roles to each FTU in the access response.

[0018] According to the networking role in the access response, the FTU switches its own ZigBee role to the networking role and performs corresponding networking operations to establish a ZigBee network among multiple FTUs accessing the same base station; wherein, the networking role includes coordinator and terminal equipment.

[0019] Preferably, the execution of the corresponding networking operation to establish a ZigBee network among multiple FTUs accessing the same base station specifically includes:

[0020] The coordinator establishes the PAN network;

[0021] The terminal device scans the PAN network and sends a network entry request to the coordinator in the scanned PAN network; wherein the network entry request carries NCGI;

[0022] 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, the coordinator assigns a ZigBee network address and network key to the terminal device and sends the network address and network key to the terminal device in the network access permission response, so that the terminal device can use the network address and network key to join the PAN network and realize ZigBee network communication.

[0023] Preferably, assigning corresponding networking roles to each FTU in the network group specifically includes:

[0024] The first FTU to join the network group has the role of coordinator, and subsequent FTUs to join the network group have the role of terminal device.

[0025] Alternatively, the FTU with the most resources in the network group can act as the coordinator, while the other FTUs can act as end devices.

[0026] Preferably, the first FTU sends the device identifier of each FTU in the data reporting group to the AMF node in the network slice registration request, 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:

[0027] The network slice registration request carries the signed NSSAI and the device identifier of each FTU in the data reporting group and is sent to the AMF node.

[0028] The AMF node sends a query request to the NSSF node based on the network slice registration request. The query request includes the NSSAI and the device identifier of each FTU.

[0029] The NSSF node performs access verification based on the query request. If the verification is successful and access is allowed, the required resource size is determined based on the device identifier of each FTU. Based on the required resource size, the corresponding network slice instance is allocated to the data reporting group. The slice instance identifier SNSSAI and the AMF node identifier of the slice instance are carried in the network slice registration response and sent to the first FTU.

[0030] Preferably, each FTU in the data reporting group jointly uses the network slice instance to report data, specifically including:

[0031] 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 can establish a PDU session for the FTU according to the session request;

[0032] Each FTU reports data through its corresponding PDU session.

[0033] Preferably, the data reporting conditions of the first FTU are met, specifically:

[0034] The interval between the current time and the previous 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.

[0035] Preferably, the reporting stop condition for each FTU is met, specifically as follows:

[0036] The data reporting time exceeds the preset time, and the data size stored locally by the FTU is less than the second preset size.

[0037] Secondly, the present invention also provides a cost-effective 5G slice data transmission device for implementing the cost-effective 5G slice data transmission method described in the first aspect, the device comprising:

[0038] 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 for performing the cost-effective 5G slice data transmission method described in the first aspect.

[0039] Thirdly, the present invention also provides a non-volatile computer storage medium storing computer-executable instructions that are executed by one or more processors to perform the method described in the first aspect.

[0040] Fourthly, a chip is provided, comprising: a processor and an interface for calling and running a computer program stored in a memory, performing the method as described in any of the first aspects.

[0041] Fifthly, a computer program product comprising instructions is provided, which, when executed on a computer or processor, cause the computer or processor to perform the method as described in any of the first aspects.

[0042] Sixthly, a cost-effective 5G slice data transmission system is provided, including multiple cost-effective 5G slice data transmission devices as described in the second aspect, namely multiple FTUs; the multiple FTUs use the cost-effective 5G slice data transmission method described in the first aspect to report data.

[0043] This invention enables each FTU to store data locally first, and then report the data when certain conditions are met (such as a large amount of data). Before reporting the data, other FTUs are queried through ZigBee networking so that FTUs with needs can form a data reporting group. This allows them to use 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, thus eliminating the need to reserve bandwidth for each FTU separately, reducing the overall bandwidth usage. After each FTU in the data reporting group has finished reporting its data, the network slice instance is de-allocated, thereby releasing resources for other data transmissions, thus optimizing network bandwidth usage. Attached Figure Description

[0044] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments of the present invention will be briefly described below. Obviously, the drawings described below are merely some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without any creative effort.

[0045] Figure 1 This is a flowchart illustrating a cost-effective 5G slice data transmission method provided in an embodiment of the present invention.

[0046] Figure 2 This is a schematic diagram of the network architecture of a cost-effective 5G slice data transmission method provided in an embodiment of the present invention;

[0047] Figure 3 This is a schematic diagram of a cost-effective 5G slice data transmission method provided in an embodiment of the present invention;

[0048] Figure 4 This is a schematic diagram of a cost-effective 5G slice data transmission method provided in an embodiment of the present invention;

[0049] Figure 5 This is a flowchart illustrating a cost-effective 5G slice data transmission method provided in an embodiment of the present invention.

[0050] Figure 6 This is a signaling diagram illustrating a cost-effective 5G slice data transmission method provided in an embodiment of the present invention;

[0051] Figure 7 This is a flowchart illustrating a cost-effective 5G slice data transmission method provided in an embodiment of the present invention.

[0052] Figure 8 This is a signaling diagram illustrating a cost-effective 5G slice data transmission method provided in an embodiment of the present invention;

[0053] Figure 9 This is a flowchart illustrating a cost-effective 5G slice data transmission method provided in an embodiment of the present invention.

[0054] Figure 10 This is a schematic diagram of a cost-effective 5G slice data transmission method provided in an embodiment of the present invention;

[0055] Figure 11 This is a flowchart illustrating a cost-effective 5G slice data transmission method provided in an embodiment of the present invention.

[0056] Figure 12 This is a signaling diagram illustrating a cost-effective 5G slice data transmission method provided in an embodiment of the present invention;

[0057] Figure 13 This is a schematic diagram of the architecture of a cost-effective 5G slice data transmission device provided in an embodiment of the present invention. Detailed Implementation

[0058] To make the objectives, technical solutions, and advantages of this invention clearer, the 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 merely illustrative and not intended to limit the invention.

[0059] Unless the context otherwise requires, throughout the specification and claims, the term "comprising" is interpreted as openly inclusive, meaning "including, but not limited to." In the description of the specification, terms such as "one embodiment," "some embodiments," "exemplary embodiment," "example," "specific example," or "some examples" are intended to indicate that a particular feature, structure, material, or characteristic associated with that embodiment or example is included in at least one embodiment or example of this disclosure. The illustrative representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics mentioned may be included in any suitable manner in any one or more embodiments or examples; that is, although they may be incorporated into embodiments or examples using the above terms for reasons such as order and position, it does not limit them to be incorporated in combination by a single embodiment or example.

[0060] In the description of this invention, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined with "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of embodiments of this disclosure, unless otherwise stated, "a plurality of" means two or more. Furthermore, for example, the description may use the prefix "A" or "B" to describe the same type of nouns as two independent entities. In this case, the corresponding features defined with "A" and "B" are used only to distinguish between similar entities and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features.

[0061] In the description of this invention, the expression “A and / or B” (where A and B are used to formally represent specific features) will be used. The corresponding expression includes the following three combinations: only A, only B, and a combination of A and B.

[0062] As used in this invention, “about,” “approximately,” or “approximately” includes the stated value and the average value within an acceptable range of deviation from a particular value, wherein the acceptable range of deviation is determined by a person skilled in the art taking into account the measurement under discussion and the error associated with the measurement of the particular quantity (i.e., the limitations of the measurement system).

[0063] Furthermore, 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.

[0064] Example 1:

[0065] Considering that some data in FTUs often has low real-time requirements—that is, this data is often not used for real-time alarms but for later analysis of alarm causes and tracing and debugging of equipment failures—this invention, in embodiment 1, provides a cost-effective 5G slice data transmission method. Each FTU stores the collected data locally and checks whether the data reporting conditions are met at preset intervals. Data is reported when the data reporting conditions of the corresponding feeder terminal equipment FTU are met. Figure 1 and Figure 2 As shown, the data reporting methods include:

[0066] In step 201, a ZigBee network is pre-established among multiple FTUs accessing the same base station. The pre-established period is obtained by those skilled in the art based on experience.

[0067] In step 202, when the data reporting conditions of the first FTU are met, the first FTU broadcasts a joint reporting message in the ZigBee network.

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

[0069] In step 204, the first FTU establishes a data reporting group based on the received joint reporting responses; that is, it adds the device identifiers of each FTU carried in the joint reporting response to a data reporting group, so as to indicate that these FTUs need to jointly report data.

[0070] In step 205, the first FTU sends the device identifiers of each FTU in the data reporting group to the Access and Mobility Management Function (AMF) node in the network slice registration request. This allows the AMF node to allocate network slice instances to the data reporting group and send the relevant information of the network slice instances to the first FTU. In practice, the network slice registration request also carries a preset identifier to represent 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 experience. For example, the first bit in the reserved field of the network slice registration request can be used as an identifier; a value of 1 indicates the presence of a preset identifier, while a value of 0 indicates the absence of a preset identifier. Furthermore, the network slice registration request also carries the number of FTUs in the data reporting group, allowing the reading of the corresponding number of bits for each FTU device identifier.

[0071] 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 use the network slice instance to report data. The relevant information of the network slice instance may be the SNSSAI of the network slice instance and the Temp.ID of the corresponding AMF node.

[0072] In step 207, when the reporting stop condition of each FTU in the data reporting group is met, data reporting stops. The network slice instance is canceled after the idle time exceeds a preset time to release resources and prepare for data transmission in data reporting groups under other base stations, until the data reporting condition of the next FTU is met, at which point the network slice instance is reallocated. The preset time is obtained by those skilled in the art based on experience. The data reporting condition, data collaborative transmission condition, and reporting stop condition are all obtained by those skilled in the art based on requirements. Each condition can be set according to the size of the locally stored data volume. For example, the data reporting condition is met when the locally stored data volume is greater than a first data volume; the data collaborative transmission condition is met when the locally stored data volume is greater than a second data volume; and the reporting stop condition is met when the locally stored data volume is less than a third data volume. The first data volume is greater than the second data volume, and the second data volume is greater than the third data volume.

[0073] In a practical application scenario, the data reporting conditions of the first FTU are met, specifically: the interval between the current time and the previous 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 obtained by those skilled in the art based on experience.

[0074] The reporting stop condition for each FTU is met, specifically: the data reporting time exceeds a preset time, and the size of the data stored locally by the FTU is less than a second preset size. The preset time and the second preset size are determined by those skilled in the art based on experience.

[0075] The data collaborative transmission condition is met specifically when: the interval between the current time and the previous data reporting time is greater than a second preset interval, or the size of the data stored is greater than a third preset size. Wherein, 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.

[0076] This embodiment allows each FTU to store data locally first, and then report the data when certain conditions are met (such as a large amount of data). Before reporting the data, other FTUs are queried through ZigBee networking so that FTUs with needs can form a data reporting group together. This allows them to use 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, thus eliminating the need to reserve bandwidth for each FTU separately, reducing the overall bandwidth usage. After each FTU in the data reporting group has finished reporting its data, the network slice instance is de-allocated, thereby releasing resources for other data transmission and optimizing network bandwidth usage.

[0077] This embodiment also has a deeper consideration: This implementation method satisfies the reporting needs of each FTU. When a corresponding FTU has a large amount of data, it can quickly report the data to ensure its storage space is released in time for subsequent data collection and storage. Furthermore, this "one-call-all-response" approach (where other FTUs report data together when one FTU has a reporting need) reduces the number of network slice instance allocations, lowering resource consumption caused by frequent dynamic allocation and cancellation of network slice instances. Moreover, the first FTU requests network slice instance information from the AMF and then sends it to other FTUs in the data reporting group via the ZigBee network. This allows all FTUs in the data reporting group to obtain a network slice instance with only one network slice registration request, eliminating the need for each FTU to make a separate network slice registration request. This achieves the effect of using a local ZigBee network to partially replace 5G network functionality, thereby reducing bandwidth consumption during the request process.

[0078] It should be noted that this embodiment is for data with low real-time requirements. For data with high real-time requirements, a fixed network slice instance is still used for real-time data transmission. Figure 2 Each FTU in the system is connected to a 5G base station (generation nodeB, abbreviated as gNB), and through the base station, it is connected to the AMF node. Figure 2 For clarity, the connection relationship of only one FTU is shown in the attached diagram. It should be understood that in actual use, the connection relationship between each FTU and the AMF node and gNB is the same.

[0079] Figure 2The 5G network in the document includes: Network Repository Function (NRF) nodes, Network Slice Selection Function (NSSF) nodes, Authentication Server Function (AUSF) nodes, Unified Data Management (UDM) nodes, Network Data Analytics Function (NWDAF) nodes, AMF nodes, Session Management Function (SMF) nodes, Policy Control Function (PCF) nodes, Network Exposure Function (NEF) nodes, Application Function (AF) nodes, User Plane Function (UPF) nodes, and Data Network (DN).

[0080] In some practical application scenarios, the network slice instance can be implemented by the operator's 5G network function, or it can be a dedicated 5G network for the power grid, with the network slice instance provided by this dedicated 5G network, such as... Figure 3 As shown, Figure 3 Three transmission methods (a), (b), and (c) are demonstrated. Method (a) directly utilizes a network slice provided by the dedicated power grid network for data transmission. In this method, the dedicated power grid network and the operator's 5G network reuse the same base station, such as... Figure 4 As shown, 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 dedicated power grid network for transmission. In method (b), the operator's 5G network provides network slicing, and in method (c), the operator provides network slicing, which transmits data to the dedicated power grid network, and then reaches the monitoring master station through the dedicated power grid network.

[0081] In a specific application scenario, the ZigBee network is pre-established among multiple FTUs accessing the same base station, such as... Figure 5 and Figure 6 As shown, it specifically includes:

[0082] In step 301, after successfully accessing the base station, the FTU sends an access message to the monitoring master station. The access message carries the FTU's device identifier and the Cell Global Identifier (NCGI). The NCGI is obtained by the FTU during the access process by listening to the SIB1 message broadcast by the base station. That is, the base station broadcasts the SIB1 message periodically, and the surrounding FTUs obtain the NCGI from the SIB1 message after receiving it, and use the NCGI to request access from the base station. For a region, it can be understood that each base station has a unique NCGI.

[0083] The monitoring master station can be understood as a pre-configured server that allows the FTU to use low-speed bandwidth for message transmission before the FTU has registered with the 5G network.

[0084] In step 302, 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. In actual use, the networking role is represented by a 2-bit roleID in the access response: roleID=0 represents the networking role as a coordinator, roleID=1 represents the networking role as a terminal device, and roleID=2 represents the networking role as a router.

[0085] In step 303, the FTU switches its ZigBee role to the network role specified in the access response and performs corresponding networking operations to establish a ZigBee network among multiple FTUs accessing the same base station. The network role includes a coordinator and terminal devices. The coordinator establishes a PAN network, and the terminal devices join the PAN network, forming a star network centered on the coordinator. At this time, the corresponding networking operations are performed to establish a ZigBee network among multiple FTUs accessing the same base station, such as... Figure 7 and Figure 8 As shown, it specifically includes:

[0086] In step 401, the coordinator establishes a Personal Area Network (PAN network).

[0087] 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: carrying the NCGI of the base station to which the terminal device is connected.

[0088] In step 403, the coordinator determines whether the NCGI in the network access request matches the NCGI of its own access base station. If they match, the coordinator assigns a ZigBee network address and network key to the terminal device and sends these to the terminal device in the network access permission response. This allows the terminal device to join the PAN network using the network address and network key, enabling ZigBee network communication. When the NCGI in the network access request matches the NCGI of the coordinator's own access base station, it can be assumed that the sender of the network access request and the coordinator are located under the same base station. When the NCGI in the network access request does not match the NCGI of the coordinator's own access base station, no network address and network key are assigned to the terminal device.

[0089] In some specific application scenarios, assigning corresponding networking roles to each FTU in the network group specifically includes:

[0090] The first FTU to join the network group will act as a coordinator, and subsequent FTUs will act as end devices.

[0091] Alternatively, the FTU with the most resources in the network group can be designated as the coordinator, while the other FTUs can be designated as terminal devices. The resources of each FTU can be pre-stored in the monitoring master station, such as storing the correspondence between resources and FTU device identifiers in the monitoring master station.

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

[0093] In practical use, since the coverage area of ​​a PAN network is relatively small (usually less than 10m), while the coverage area of ​​a base station network 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, based on the location of each base station and each FTU, assigns the network role of the FTU closest to the corresponding base station (i.e., the base station accessed by each FTU in the network group) as the coordinator, and assigns network roles to other FTUs according to a preset strategy; wherein, the network roles of other FTUs are routers or terminal devices.

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

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

[0096]

[0097] Where N is the number of FTUs in a network group that need to be assigned networking roles; Let i be 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 routers allocated.

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

[0099]

[0100] Where P is the set of FTUs whose networking roles are coordinator and router, and Q is the set of FTUs whose networking roles are terminal devices. Let be the connectivity factor between the p-th FTU and the coordinator in P. When the distance between any two connected FTUs on the connection line between the p-th FTU and the coordinator is less than or equal to a preset distance, ;otherwise, Where the p-th FTU in P is the coordinator, The preset distance is determined by those skilled in the art based on experience, and 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 practical use, the preset distance... The value is obtained by creating edges for FTUs in P whose distances to each other are less than or equal to a preset distance, and then determining whether the p-th FTU can be connected to the coordinator through one or more edges. If it can be connected, then... ,otherwise, .

[0101]

[0102] in, For the p-th FTU in P and The distance factor between the q-th FTU in P, when the p-th FTU in P and When the distance between the q-th FTUs is less than or equal to the preset distance, ;otherwise, .

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

[0104] In one optional implementation, the first FTU sends the device identifiers of each FTU in the data reporting group to the AMF node in the network slice registration request, so that the AMF node allocates network slice instances to the data reporting group and sends the relevant information of the network slice instances to the first FTU, such as... Figure 9 As shown, it specifically includes:

[0105] In step 501, the network slice registration request is sent to the AMF node by carrying the signed NSSAI (NetworkSliceSelection Assistance Information) and the device identifier of each FTU in the data reporting group.

[0106] 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. The query request includes the NSSAI and the device identifiers of each FTU.

[0107] In step 503, the NSSF node performs access verification based on the query request. If the verification is successful (i.e., verifying whether the NSSAI has been registered and whether each FTU is a device capable of using the NSSAI), the required resource size is determined based on the device identifier of each FTU. Based on the required resource size, a corresponding network slice instance is allocated to the data reporting group. The slice instance identifier (SNSSAI) and the AMF node identifier of the slice instance are included in the network slice registration response and sent to the first FTU. The determination of the required resource size based on the device identifier of each FTU can be... ,in, and The resource size is preset by those skilled in the art. The number of FTUs identified based on the equipment identifier of each FTU. The required resource size is determined. Based on this resource size, a corresponding network slice template is matched, thereby establishing and allocating the corresponding network slice instance. In an optional implementation, the network slice registration request message can be as follows: Figure 10As shown, setting bit 0 of the second byte in the Registration Request message to 1 indicates the inclusion of a preset identifier. The requested NSSAI is stored in bytes 14 through n, where the total length of the requested one or more S-NSSAIs is stored in byte 15, and 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 through m, where each SUCI occupies 8 bytes, and the value of m is determined by the total length of all SUCIs.

[0108] In a specific application scenario, each FTU in the data reporting group jointly uses the network slice instance to report data, such as... Figure 11 As shown, it specifically includes:

[0109] In step 601, each FTU sends a session request to the AMF node; wherein the session request carries the slice instance identifier SNSSAI (Single NetworkSliceSelectionAssistance Information), the AMF node identifier of the slice instance, and the data network name (DNN) of the slice instance, so that the AMF node can establish a PDU session for the FTU according to the session request.

[0110] In step 602, each FTU reports data through its corresponding PDU session. The PDU session is managed based on the network slice instance and uses the network resources of the network slice instance for data transmission. It should be noted that sending the network slice request to the AMF node is to send it to the default AMF node. This default AMF node interacts with the NSSF node to obtain the AMF node identifier serving the network slice instance. This AMF node serving the network slice instance may not be the same as the default AMF node. In subsequent data transmission using the network slice instance (i.e., in step 601), data is sent to the AMF node corresponding to that AMF node identifier for transmission. In practical use, the AMF node identifier is also called the Temp.ID of the AMF node, such as... Figure 12 As shown, assuming the default AMF node is AMF1, and after interacting with AMF1, the Temp.ID of AMF2 is returned, then in step 601, a session request is sent to AMF2.

[0111] Example 2:

[0112] like Figure 13The diagram shown is an architectural schematic of a cost-effective 5G slice data transmission device according to an embodiment of the present invention. This cost-effective 5G slice data transmission device includes one or more processors 21 and a memory 22. Figure 13 Take a processor 21 as an example.

[0113] Processor 21 and memory 22 can be connected via a bus or other means. Figure 13 Taking the example of a connection between China and Israel via a bus.

[0114] 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 Embodiment 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.

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

[0116] The program instructions / modules are stored in the memory 22 and, when executed by one or more processors 21, perform the cost-effective 5G slice data transmission method described in Embodiment 1.

[0117] 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 Embodiment 1 to report data.

[0118] It is worth noting that the information interaction and execution process between the modules and units in the above-mentioned device and system are based on the same concept as the processing method embodiment of the present invention. For details, please refer to the description in the method embodiment of the present invention, and will not be repeated here.

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

[0120] 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 within the protection scope of the present invention.

Claims

1. A cost-effective 5G slicing data transmission method, characterized in that, Each FTU stores the collected data locally and checks whether the data reporting conditions are met at preset intervals. Data is reported when the data reporting conditions of the corresponding feeder terminal unit (FTU) are met. The data reporting methods include: A ZigBee network is pre-established among 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; When the second FTU receives the joint reporting message, it determines whether its own data collaborative transmission conditions have been met. If it determines that its own data collaborative transmission conditions have been met, it returns a joint reporting response to the first FTU. The joint reporting response carries the device identifier of the second FTU, which is an FTU located in the same ZigBee network as the first FTU. The first FTU establishes a data reporting group based on the received common reporting responses; The first FTU sends the device identifier of each FTU in the data reporting group to the AMF node in the network slice registration request, so that the AMF node can allocate a network slice instance to the data reporting group and send the relevant information of the network slice instance to the first FTU. 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 use the network slice instance to report data. When the reporting stop condition of each FTU in the data reporting group is met, data reporting stops, and the network slice instance is canceled after the idle time exceeds a preset time.

2. The cost-effective 5G slicing data transmission method according to claim 1, characterized in that, The pre-establishment of a ZigBee network among multiple FTUs accessing 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 cell global identifier (NCGI). The NCGI is obtained by the FTU by listening to the SIB1 message broadcast by the base station during the access process. The monitoring master station adds multiple FTUs with the same NCGI to the same network group, assigns corresponding networking roles to each FTU in the network group, and sends the networking roles to each FTU in the access response. According to the networking role in the access response, the FTU switches its own ZigBee role to the networking role and performs corresponding networking operations to establish a ZigBee network among multiple FTUs accessing the same base station; wherein, the networking role includes coordinator and terminal equipment.

3. The cost-effective 5G slicing data transmission method according to claim 2, characterized in that, The execution of corresponding networking operations to establish a ZigBee network among multiple FTUs accessing the same base station specifically includes: The coordinator establishes the PAN network; The terminal device scans the PAN network and sends a network entry request to the coordinator in the scanned PAN network; wherein the network entry 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, the coordinator assigns a ZigBee network address and network key to the terminal device and sends the network address and network key to the terminal device in the network access permission response, so that the terminal device can use the network address and network key to join the PAN network and realize ZigBee network communication.

4. The cost-effective 5G slicing data transmission method according to claim 2, characterized in that, Assigning corresponding networking roles to each FTU in the network group specifically includes: The first FTU to join the network group has the role of coordinator, and subsequent FTUs to join the network group have the role of terminal device. Alternatively, the FTU with the most resources in the network group can act as the coordinator, while the other FTUs can act as end devices.

5. The cost-effective 5G slicing data transmission method according to claim 1, characterized in that, The first FTU sends the device identifiers of each FTU in the data reporting group to the AMF node in the network slice registration request, so that the AMF node can allocate network slice instances to the data reporting group and send the relevant information of the network slice instances to the first FTU, specifically including: The network slice registration request carries the signed NSSAI and the device identifier of each FTU in the data reporting group and is sent to the AMF node. The AMF node sends a query request to the NSSF node based on the network slice registration request. 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 is successful and access is allowed, the required resource size is determined based on the device identifier of each FTU. Based on the required resource size, the corresponding network slice instance is allocated to the data reporting group. The slice instance identifier SNSSAI 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 slicing 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 can establish a PDU session for the FTU according to the session request; Each FTU reports data through its corresponding PDU session.

7. The cost-effective 5G slicing data transmission method according to any one of claims 1-6, characterized in that, The data reporting conditions for the first FTU have been met, specifically: The interval between the current time and the previous 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.

8. The cost-effective 5G slicing data transmission method according to any one of claims 1-6, characterized in that, The reporting stop conditions for each FTU have been met, specifically: The data reporting time exceeds the preset time, and the data size stored locally by the FTU is less 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 perform the cost-effective 5G slice data transmission method as described in any one of claims 1-8.

10. A cost-effective 5G slicing 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