CN117528462B - Industrial Internet of things data transmission method realized by multi-network networking - Google Patents

Industrial Internet of things data transmission method realized by multi-network networking Download PDF

Info

Publication number
CN117528462B
CN117528462B CN202410025755.0A CN202410025755A CN117528462B CN 117528462 B CN117528462 B CN 117528462B CN 202410025755 A CN202410025755 A CN 202410025755A CN 117528462 B CN117528462 B CN 117528462B
Authority
CN
China
Prior art keywords
service
nms
network element
area
npns
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202410025755.0A
Other languages
Chinese (zh)
Other versions
CN117528462A (en
Inventor
雷金繁
邓红龙
邓淼平
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Chilink Iot Technology Co ltd
Original Assignee
Shenzhen Chilink Iot Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shenzhen Chilink Iot Technology Co ltd filed Critical Shenzhen Chilink Iot Technology Co ltd
Priority to CN202410025755.0A priority Critical patent/CN117528462B/en
Publication of CN117528462A publication Critical patent/CN117528462A/en
Application granted granted Critical
Publication of CN117528462B publication Critical patent/CN117528462B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50Service provisioning or reconfiguring
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16YINFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
    • G16Y10/00Economic sectors
    • G16Y10/75Information technology; Communication
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16YINFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
    • G16Y40/00IoT characterised by the purpose of the information processing
    • G16Y40/30Control
    • G16Y40/35Management of things, i.e. controlling in accordance with a policy or in order to achieve specified objectives
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16YINFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
    • G16Y40/00IoT characterised by the purpose of the information processing
    • G16Y40/50Safety; Security of things, users, data or systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60Context-dependent security
    • H04W12/66Trust-dependent, e.g. using trust scores or trust relationships
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/02Arrangements for optimising operational condition
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18Service support devices; Network management devices

Abstract

The application provides a data transmission method of an industrial Internet of things realized by multi-network networking, and belongs to the technical field of communication. The service for realizing the public network can be carried by the private network through the fusion of the public network and the private network, so that the service deployment can be more flexible. The method comprises the following steps: the NMS receives a service request from an application service AS, wherein the service request is used for requesting the NMS to carry out user plane configuration on a first service of the industrial Internet of things, and the AS provides the first service; the NMS determines that the first service needs to be borne by N private networks NPN according to the service request, wherein N is an integer greater than 1; the NMS performs user plane configuration for the first service on each user plane function UPF network element of the N NPNs, wherein the user plane configuration for the first service on the UPF network element is used for the UPF network element to bear the user plane data of the first service.

Description

Industrial Internet of things data transmission method realized by multi-network networking
Technical Field
The application relates to the field of artificial intelligence, in particular to a data transmission method of an industrial Internet of things realized by multi-network networking.
Background
The 3GPP is collectively referred to as "3rd Generation Partnership Project", and Chinese means "third Generation partnership project". It is a nationwide collaborative organization composed of the telecommunication standardization institute ETSI (european telecommunication standardization institute) and the global telecommunication institute (Global System for Mobile Communications Association) and is mainly responsible for the standard making work in the mobile communication field.
The 3GPP defines 5G networks to be of different types, such as public network (NPN) and private network (non-public network). Their main differences are access range and purpose of use. The public network is also called an external network, and refers to a network that can be accessed by users who can access the internet without limitation. Public network addresses refer to addresses directly reachable over the internet, meaning that you can access not only others, but also by people if you have a public network address. Private networks refer to local area networks, such as networks that do not have access to data outside of the campus, only members belonging to the local area network. One reason for private network address generation is that because of the very lack of public network addresses, it is common to have to use the same public Internet Protocol (IP) address to surf the internet, which is the origin of the shared surfing.
In the present day, the service deployment of the private network and the public network are isolated from each other, but as the network or the demand evolves, some service fusion may occur between the private network and the public network in the future, so the current service deployment mode may not meet the future demand.
Disclosure of Invention
The embodiment of the application provides a data transmission method of an industrial Internet of things realized by multi-network networking, which is used for realizing that the business of a public network can be borne by a private network through the integration of the public network and the private network, so that the deployment of the business can be more flexible.
In order to achieve the above purpose, the present application adopts the following technical scheme:
in a first aspect, an embodiment of the present application provides a data transmission method of an industrial internet of things implemented by multi-network networking, where the method is applied to a network management system NMS, and the method includes: the NMS receives a service request from an application service AS, wherein the service request is used for requesting the NMS to carry out user plane configuration on a first service of the industrial Internet of things, and the AS provides the first service; the NMS determines that the first service needs to be borne by N private networks NPN according to the service request, wherein N is an integer greater than 1; the NMS performs user plane configuration for the first service on each user plane function UPF network element of the N NPNs, wherein the user plane configuration for the first service on the UPF network element is used for the UPF network element to bear the user plane data of the first service.
Optionally, the service request includes at least one of: information for the first service, information for indicating that the first service is provided by the AS, or information for requesting user plane configuration, wherein at least one of the information for jointly indicating that the requesting NMS performs user plane configuration on the first service.
Optionally, the service request further includes application scope information of the first service, where the application scope information is used to indicate that a function/entity providing the first service is an AS, and an area to be served by the first service is a first area, and the first area is an area served by a public network, and the public network is an operator network; the NMS determines that the first service needs to be born by N private network NPNs according to the service request, and comprises the following steps: the NMS determines that M NPNs are deployed between the position of the AS and the first area according to the application range information, wherein M is an integer greater than 1; the NMS determines from the M nps that the first service needs to be carried by the N nps.
Optionally, the NMS determines, according to the application range information, that M NPN are disposed between the location of the AS and the first area, including: the NMS determines that M NPNs are covered in the area between the position of the AS and the first area according to the application range information and the coverage range of each NPN preconfigured by the NMS.
Optionally, the NMS determines from the M NPN that the first service needs to be carried by the N NPN, including: the NMS determines N NPNs which can cover the area between the position of the AS and the first area and have the front N high credibility levels from the M NPNs according to the credibility levels of the M NPNs; or alternatively; the NMS determines whether an independent private network SNPN covers an area between the position of the AS and the first area in the M NPNs according to the types of the M NPNs; if the area between the AS position and the first area can be covered, selecting SNPN, wherein the SNPN is N NPNs; if the area between the AS position and the first area cannot be covered, selecting SNPN, and selecting public integrated private network PNI-NPN which can cover the area which cannot be covered by the SNPN from M NPNs, wherein the area which cannot be covered by the SNPN is the area which is between the AS position and the first area and cannot be covered by the SNPN, and the selected SNPN and the selected PNI-NPN are N NPNs.
Optionally, the respective trust level of the M nps is determined by periodically performing trust measurement on network elements in the M nps by the NMS, and if one NPN determines that more network elements are trusted in the NPN through the trust measurement, the trust level of the NPN is higher, and if the trust level of one NPN is higher, the NPN is trusted by the NMS; wherein, determining whether the network element in one NPN is trusted by the trusted metric means: the following evidence in the network element is collected by the trusted metric: the number of times the network element reports the abnormality, the data volume of the network element and other communication, or the number of times the network element is restarted, whether the evidence that the value exceeds the upper limit value or the lower limit value exists or not, if the evidence that the value exceeds the upper limit value or the lower limit value exists, the network element is not trusted, otherwise, the network element is trusted.
Optionally, the NMS performs user plane configuration for the first service on the user plane function UPF network element of each of the N NPN, including: the NMS obtains policy and charging rules PCC rules of the first service from PCF network elements of the operator network, wherein the PCC rules comprise user plane configuration of the first service; the NMS converts the PCC rules into N4 session configurations corresponding to the UPF network elements of each of the N NPN, N4 session configurations in total; the NMS configures N4 session configurations in a one-to-one correspondence manner to the UPF network element configurations of N NPNs respectively.
Optionally, the NMS obtains policy and charging rules PCC rules for the first service from a PCF network element of the operator network, including: the NMS sends a capability opening request to the PCF network element, wherein the capability opening request is used for requesting the PCF network element to open PCC rules of the first service to the NMS; specifically, the capability open request includes one or more of the following: information for indicating the first service, in particular flow description information of the first service, information for indicating the NMS, or information for requesting an open PCC rule; one or more PCC rules for jointly indicating to request the PCF network element to open the first service to the NMS; the NMS receives a capability opening response returned by the PCF network element for the capability opening request, wherein the capability opening response carries PCC rules of the first service.
Optionally, the NMS converts the PCC rule into N4 session configurations corresponding to the UPF network elements of each of the N NPN, including: the NMS selects UPF network elements with the lowest load from the UPF network elements of each of the N NPNs, and selects N UPF network elements altogether; the NMS determines the transfer relation of N UPF network elements according to the direction of the first service to be transferred by the AS to the first area, wherein the transfer relation of the N UPF network elements is used for indicating the next node of each UPF network element in the N UPF network elements, and the next node of each UPF network element refers to: the data of the first service needs to be transmitted to the 1 st UPF network element in the N UPF network elements by the AS, and transmitted to the 2 nd UPF network element in the N UPF network elements by the 1 st UPF network element, and so on until being transmitted to the N UPF network element in the N UPF network elements, and finally transmitted to the UPF network element in the operator network by the N UPF network element; the NMS copies the PCC rules to obtain N PCC rules, and encapsulates information for the next node of each UPF network element into a corresponding PCC rule in the N PCC rules according to the transfer relation of the N UPF network elements to obtain corresponding N4 session configurations, and N4 session configurations are obtained.
Optionally, each of the N UPF network elements is a PDU session anchor.
In a second aspect, embodiments of the present application provide a data transmission apparatus of an industrial internet of things implemented by multi-network networking, the apparatus being applied to a network management system NMS, the apparatus being configured to: the NMS receives a service request from an application service AS, wherein the service request is used for requesting the NMS to carry out user plane configuration on a first service of the industrial Internet of things, and the AS provides the first service; the NMS determines that the first service needs to be borne by N private networks NPN according to the service request, wherein N is an integer greater than 1; the NMS performs user plane configuration for the first service on each user plane function UPF network element of the N NPNs, wherein the user plane configuration for the first service on the UPF network element is used for the UPF network element to bear the user plane data of the first service.
Optionally, the service request includes at least one of: information for the first service, information for indicating that the first service is provided by the AS, or information for requesting user plane configuration, wherein at least one of the information for jointly indicating that the requesting NMS performs user plane configuration on the first service.
Optionally, the service request further includes application scope information of the first service, where the application scope information is used to indicate that a function/entity providing the first service is an AS, and an area to be served by the first service is a first area, and the first area is an area served by a public network, and the public network is an operator network; the apparatus is configured to: the NMS determines that M NPNs are deployed between the position of the AS and the first area according to the application range information, wherein M is an integer greater than 1; the NMS determines from the M nps that the first service needs to be carried by the N nps.
Optionally, the NMS determines, according to the application range information, that M NPN are disposed between the location of the AS and the first area, including: the NMS determines that M NPNs are covered in the area between the position of the AS and the first area according to the application range information and the coverage range of each NPN preconfigured by the NMS.
Optionally, the apparatus is configured to: the NMS determines N NPNs which can cover the area between the position of the AS and the first area and have the front N high credibility levels from the M NPNs according to the credibility levels of the M NPNs; or alternatively; the NMS determines whether an independent private network SNPN covers an area between the position of the AS and the first area in the M NPNs according to the types of the M NPNs; if the area between the AS position and the first area can be covered, selecting SNPN, wherein the SNPN is N NPNs; if the area between the AS position and the first area cannot be covered, selecting SNPN, and selecting public integrated private network PNI-NPN which can cover the area which cannot be covered by the SNPN from M NPNs, wherein the area which cannot be covered by the SNPN is the area which is between the AS position and the first area and cannot be covered by the SNPN, and the selected SNPN and the selected PNI-NPN are N NPNs.
Optionally, the respective trust level of the M nps is determined by periodically performing trust measurement on network elements in the M nps by the NMS, and if one NPN determines that more network elements are trusted in the NPN through the trust measurement, the trust level of the NPN is higher, and if the trust level of one NPN is higher, the NPN is trusted by the NMS; wherein, determining whether the network element in one NPN is trusted by the trusted metric means: the following evidence in the network element is collected by the trusted metric: the number of times the network element reports the abnormality, the data volume of the network element and other communication, or the number of times the network element is restarted, whether the evidence that the value exceeds the upper limit value or the lower limit value exists or not, if the evidence that the value exceeds the upper limit value or the lower limit value exists, the network element is not trusted, otherwise, the network element is trusted.
Optionally, the apparatus is configured to: the NMS obtains policy and charging rules PCC rules of the first service from PCF network elements of the operator network, wherein the PCC rules comprise user plane configuration of the first service; the NMS converts the PCC rules into N4 session configurations corresponding to the UPF network elements of each of the N NPN, N4 session configurations in total; the NMS configures N4 session configurations in a one-to-one correspondence manner to the UPF network element configurations of N NPNs respectively.
Optionally, the apparatus is configured to: the NMS sends a capability opening request to the PCF network element, wherein the capability opening request is used for requesting the PCF network element to open PCC rules of the first service to the NMS; specifically, the capability open request includes one or more of the following: information for indicating the first service, in particular flow description information of the first service, information for indicating the NMS, or information for requesting an open PCC rule; one or more PCC rules for jointly indicating to request the PCF network element to open the first service to the NMS; the NMS receives a capability opening response returned by the PCF network element for the capability opening request, wherein the capability opening response carries PCC rules of the first service.
Optionally, the apparatus is configured to: the NMS selects UPF network elements with the lowest load from the UPF network elements of each of the N NPNs, and selects N UPF network elements altogether; the NMS determines the transfer relation of N UPF network elements according to the direction of the first service to be transferred by the AS to the first area, wherein the transfer relation of the N UPF network elements is used for indicating the next node of each UPF network element in the N UPF network elements, and the next node of each UPF network element refers to: the data of the first service needs to be transmitted to the 1 st UPF network element in the N UPF network elements by the AS, and transmitted to the 2 nd UPF network element in the N UPF network elements by the 1 st UPF network element, and so on until being transmitted to the N UPF network element in the N UPF network elements, and finally transmitted to the UPF network element in the operator network by the N UPF network element; the NMS copies the PCC rules to obtain N PCC rules, and encapsulates information for the next node of each UPF network element into a corresponding PCC rule in the N PCC rules according to the transfer relation of the N UPF network elements to obtain corresponding N4 session configurations, and N4 session configurations are obtained.
Optionally, each of the N UPF network elements is a PDU session anchor.
In a third aspect, embodiments of the present application provide a computer readable storage medium having program code stored thereon, which when executed by the computer, performs the method according to the first aspect.
In summary, the method and the device have the following technical effects:
1) So that the service deployment can be more flexible. For the first service of the industrial internet of things provided by the AS, namely, the first service of the public network, the user plane configuration for the first service is carried out on the UPF network elements of the N NPNs through the NMS, so that the first service can be carried by the NPNs, and the service of the public network can be carried by the private network through the fusion of the public network and the private network, thereby enabling the service deployment to be more flexible.
2) The reliability and the safety of the industrial Internet of things are improved. By using a plurality of NPNs to bear the first service, the redundancy and fault tolerance of the system can be improved, and thus the reliability of the whole industrial Internet of things is improved. Meanwhile, the user plane configuration aiming at the first service can ensure that the UPF network element can bear the user plane data of the first service, improve the safety of the data, optimize the network performance and improve the data transmission efficiency.
3) The scalability of the system is improved, i.e. when more NPNs need to be added to carry the first service, the system can be realized by adding more UPF network elements, without modifying the existing system on a large scale.
Drawings
FIG. 1 is a schematic diagram of a 5G system architecture;
fig. 2 is a schematic architecture diagram of a communication system according to an embodiment of the present application;
fig. 3 is a flowchart of a data transmission method of an industrial internet of things implemented by multi-network networking according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
1. Fifth generation (5th generation,5G) mobile communication system:
fig. 1 is a schematic architecture diagram of a 5G system, as shown in fig. 1, where the 5G system includes: access Networks (ANs) and Core Networks (CNs), may further include: and (5) a terminal.
The terminal may be a terminal having a transceiver function, or a chip system that may be provided in the terminal. The terminal may also be referred to as a User Equipment (UE), an access terminal, a subscriber unit (subscriber unit), a subscriber station, a Mobile Station (MS), a remote station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user device. The terminals in embodiments of the present application may be mobile phones (mobile phones), cellular phones (cellular phones), smart phones (smart phones), tablet computers (pads), wireless data cards, personal digital assistants (personal digital assistant, PDAs), wireless modems (modems), handheld devices (handsets), laptop computers (lap computers), machine type communication (machine type communication, MTC) terminals, computers with wireless transceiving functions, virtual Reality (VR) terminals, augmented reality (augmented reality, AR) terminals, wireless terminals in industrial control (industrial control), wireless terminals in unmanned aerial vehicle (self driving), wireless terminals in smart grid (smart grid), wireless terminals in transportation security (transportation safety), wireless terminals in smart city (smart city), wireless terminals in smart home (smart home), roadside units with functions, RSU, etc. The terminal of the present application may also be an in-vehicle module, an in-vehicle component, an in-vehicle chip, or an in-vehicle unit built into a vehicle as one or more components or units.
The AN is used for realizing the function related to access, providing the network access function for authorized users in a specific area, and determining transmission links with different qualities according to the level of the users, the service requirements and the like so as to transmit user data. The AN forwards control signals and user data between the terminal and the CN. The AN may include: an access network element, which may also be referred to as a radio access network element (radio access network, RAN) device.
The RAN device may be a device that provides access to the terminal. For example, the RAN device may include: the RAN apparatus may also include a 5G, such as a gNB in a new radio, NR, system, or one or a group (including multiple antenna panels) of base stations in the 5G, or may also be a network node, such as a baseband unit (building base band unit, BBU), or a Centralized Unit (CU) or a Distributed Unit (DU), an RSU with base station functionality, or a wired access gateway, or a core network element of the 5G, constituting a gNB, a transmission point (transmission and reception point, TRP or transmission point, TP), or a transmission measurement function (transmission measurement function, TMF). Alternatively, the RAN device may also include an Access Point (AP) in a wireless fidelity (wireless fidelity, wiFi) system, a wireless relay node, a wireless backhaul node, various forms of macro base stations, micro base stations (also referred to as small stations), relay stations, access points, wearable devices, vehicle devices, and so on. Alternatively, the RAN device may also include a next generation mobile communication system, for example, an access network element of 6G, for example, a 6G base station, or in the next generation mobile communication system, the network device may also have other naming manners, which are covered in the protection scope of the embodiments of the present application, which is not limited in any way.
The CN is mainly responsible for maintaining subscription data of the mobile network and providing session management, mobility management, policy management, security authentication and other functions for the terminal. The CN mainly comprises the following network elements: a user plane function (user plane function, UPF) network element, an authentication service function (authentication server function, AUSF) network element, an access and mobility management function (access and mobility management function, AMF) network element, a session management function (session management function, SMF) network element, a network slice selection function (network slice selection function, NSSF) network element, a network opening function (network exposure function, NEF) network element, a network function warehousing function (NF repository function, NRF) network element, a policy control function (policy control function, PCF) network element, a unified data management (unified data management, UDM) network element, an application function (application function, AF) network element, and a network slice and independent non-public network (nsaaf) authentication authorization function (network slice-specific and SNPN authentication and authorization function, nsaaf) network element.
Wherein the UPF network element is mainly responsible for user data processing (forwarding, receiving, charging, etc.). For example, the UPF network element may receive user data from a Data Network (DN), which is forwarded to the terminal through the access network element. The UPF network element may also receive user data from the terminal through the access network element and forward the user data to the DN. DN network elements refer to the operator network that provides data transmission services for subscribers. Such as the internet protocol (internet protocol, IP) Multimedia Services (IMS), the internet, etc.
The AUSF network element may be used to perform security authentication of the terminal.
The AMF network element is mainly responsible for mobility management in the mobile network. Such as user location updates, user registration networks, user handoffs, etc.
The SMF network element is mainly responsible for session management in the mobile network. Such as session establishment, modification, release. Specific functions are, for example, assigning internet protocol (internet protocol, IP) addresses to users, selecting a UPF that provides a message forwarding function, etc.
The PCF network element mainly supports providing a unified policy framework to control network behavior, provides policy rules for a control layer network function, and is responsible for acquiring user subscription information related to policy decision. The PCF network element may provide policies, such as quality of service (quality of service, qoS) policies, slice selection policies, etc., to the AMF network element, SMF network element.
The NSSF network element may be used to select a network slice for the terminal.
The NEF network element may be used to support the opening of capabilities and events.
The UDM network element may be used to store subscriber data, such as subscription data, authentication/authorization data, etc.
The AF network element mainly supports interactions with the CN to provide services, such as influencing data routing decisions, policy control functions or providing some services of a third party to the network side.
In the embodiment of the invention, the indication can comprise direct indication and indirect indication, and can also comprise explicit indication and implicit indication. In the specific implementation process, the manner of indicating the information to be indicated is various, for example, but not limited to, the information to be indicated may be directly indicated, such as the information to be indicated itself or an index of the information to be indicated. The information to be indicated can also be indicated indirectly by indicating other information, wherein the other information and the information to be indicated have an association relation. It is also possible to indicate only a part of the information to be indicated, while other parts of the information to be indicated are known or agreed in advance. For example, the indication of the specific information may also be achieved by means of a pre-agreed (e.g., protocol-specified) arrangement sequence of the respective information, thereby reducing the indication overhead to some extent. And meanwhile, the universal part of each information can be identified and indicated uniformly, so that the indication cost caused by independently indicating the same information is reduced.
The specific indication means may be any of various existing indication means, such as, but not limited to, the above indication means, various combinations thereof, and the like. Specific details of various indications may be referred to the prior art and are not described herein. As can be seen from the above, for example, when multiple pieces of information of the same type need to be indicated, different manners of indication of different pieces of information may occur. In a specific implementation process, a required indication mode can be selected according to specific needs, and the selected indication mode is not limited in the embodiment of the present invention, so that the indication mode according to the embodiment of the present invention is understood to cover various methods that can enable a party to be indicated to learn information to be indicated.
It should be understood that the information to be indicated may be sent together as a whole or may be sent separately in a plurality of sub-information, and the sending periods and/or sending timings of these sub-information may be the same or different. Specific transmission method the embodiment of the present invention is not limited. The transmission period and/or the transmission timing of the sub-information may be predefined, for example, predefined according to a protocol, or may be configured by the transmitting end device by transmitting configuration information to the receiving end device.
The "pre-defining" or "pre-configuring" may be implemented by pre-storing corresponding codes, tables, or other manners that may be used to indicate relevant information in the device, and the embodiments of the present invention are not limited to the specific implementation manner. Where "save" may refer to saving in one or more memories. The one or more memories may be provided separately or may be integrated in an encoder or decoder, processor, or electronic device. The one or more memories may also be provided separately as part of a decoder, processor, or electronic device. The type of memory may be any form of storage medium, and embodiments of the invention are not limited in this regard.
The "protocol" referred to in the embodiments of the present invention may refer to a protocol family in the communication field, a standard protocol similar to a frame structure of the protocol family, or a related protocol applied to a reliable access method system of future internet of things equipment, which is not specifically limited in the embodiments of the present invention.
In the embodiment of the invention, the descriptions of "when … …", "in the case of … …", "if" and "if" all refer to that the device will perform corresponding processing under some objective condition, and are not limited in time, nor do the descriptions require that the device must have a judging action when implementing, nor do the descriptions mean that other limitations exist.
In the description of the embodiments of the present invention, unless otherwise indicated, "/" means that the objects associated in tandem are in a "or" relationship, e.g., A/B may represent A or B; the "and/or" in the embodiment of the present invention is merely an association relationship describing the association object, and indicates that three relationships may exist, for example, a and/or B may indicate: a alone, a and B together, and B alone, wherein A, B may be singular or plural. Also, in the description of the embodiments of the present invention, unless otherwise indicated, "plurality" means two or more than two. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b or c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or plural. In addition, in order to facilitate the clear description of the technical solution of the embodiments of the present invention, in the embodiments of the present invention, the words "first", "second", etc. are used to distinguish the same item or similar items having substantially the same function and effect. It will be appreciated by those of skill in the art that the words "first," "second," and the like do not limit the amount and order of execution, and that the words "first," "second," and the like do not necessarily differ. Meanwhile, in the embodiments of the present invention, words such as "exemplary" or "such as" are used to mean serving as examples, illustrations or explanations. Any embodiment or design described herein as "exemplary" or "e.g." in an embodiment should not be taken as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion that may be readily understood.
The network architecture and the service scenario described in the embodiments of the present invention are for more clearly describing the technical solution of the embodiments of the present invention, and do not constitute a limitation on the technical solution provided by the embodiments of the present invention, and those skilled in the art can know that, with the evolution of the network architecture and the appearance of the new service scenario, the technical solution provided by the embodiments of the present invention is applicable to similar technical problems.
The technical solutions in the present application will be described below with reference to the accompanying drawings.
Referring to fig. 2, an embodiment of the present application provides a communication system, which may include: a network management system (Network Management System, NMS) and NPN.
An NMS is a system that combines hardware and software for monitoring and managing a network. Five major functions of NMS include alarm, performance, configuration, security, billing. The system can comprehensively monitor the running states, events, faults, performances and the like of the whole network, the server and the service system. The NMS is an operation maintenance center and is responsible for equipment fault diagnosis, operation maintenance, network operation and network management of the wireless access system, and data and statistics are provided for network management and planning. The NMS communicates with the managed devices through a simple network management protocol SNMP (Simple Network Management Protocol). NMS can implement cross-over management, such as managing network elements/networks themselves in both public and private networks.
NPN refers to a local area network, such as a data-out-of-park network, that is accessible only by members belonging to the local area network. One reason for private network address generation is that because of the very lack of public network addresses, it is common to have to use the same public Internet Protocol (IP) address to surf the internet, which is the origin of the shared surfing.
The interaction of NMS and NPN in the above communication system will be described in detail with respect to the method.
Referring to fig. 3, an embodiment of the present application provides a data transmission method of an industrial internet of things implemented by multi-network networking. The method may be applicable to communication between the NMS and the NPN. The method comprises the following steps:
s301, the NMS receives a service request from an application service (Application Service, AS).
The service request is used for requesting the NMS to perform user plane configuration on a first service of the industrial Internet of things. The AS provides a first service. The service request may include at least one of: information for the first service (e.g., flow description information of the first service), information for indicating that the first service is provided by the AS, or information for requesting user plane configuration. As such, at least one of the above suggestions is for jointly indicating that the requesting NMS is to perform user plane configuration for the first service. The service request may further include application scope information of the first service, where the application scope information is used to indicate that a function/entity providing the first service is an AS, and an area to be served by the first service is a first area (e.g., latitude and longitude information of the first area), and the first area is an area served by a public network, where the public network is an operator network.
The service request may be implemented by using an existing message or a newly defined message, which is not limited.
S302, NMS determines that the first service needs to be carried by N private network NPN according to the service request.
N is an integer greater than 1. The NMS may determine, according to the application range information, that M NPN are disposed between the location of the AS and the first area, where M is an integer greater than 1. The NMS may then determine from the M NPN that the first service needs to be carried by the N NPN.
Optionally, the NMS may determine, according to the application range information, that M NPN are disposed between the location of the AS and the first area, including: the NMS may determine that M NPN are covered in an area between the location of the AS and the first area according to the application range information and coverage of each NPN preconfigured by the NMS. That is, in the above manner, it is possible to accurately determine which NPN coverage exists in the area between the location of the AS and the first area.
Optionally, the NMS may determine from the M nps that the first service needs to be carried by the N nps, including: the NMS may determine, from the M nps, N nps that can cover an area between the location of the AS and the first area according to respective trust levels of the M nps, where N is high before the trust level, so AS to ensure security of the service. Or alternatively; the NMS may also determine, according to the type of the M nps, whether an independently networked NPN network (SNPN) of the M nps covers an area between the location of the AS and the first area. And if the area between the AS position and the first area can be covered, selecting SNPN, wherein the SNPN is N NPNs. If the area between the AS location and the first area cannot be covered, selecting SNPN, and selecting a Public Network integrated non-Public Network (Public Network Integrated Non-Public Network, PNI-NPN) capable of covering the area which cannot be covered by SNPN from M NPNs. The area which can not be covered by SNPN is the area which is between the position of AS and the first area and can not be covered by SNPN, and the selected SNPN and PNI-NPN are N NPNs. That is, SNPN is more trusted than PNI-NPN, so that it is necessary to preferentially select SNPN to secure traffic as much as possible.
Optionally, the respective trust level of the M nps is determined by periodically performing a trust metric on network elements in the M nps by the NMS, and if one NPN determines that more network elements are trusted in the NPN through the trust metric, the trust level of the NPN is higher, and if the trust level of one NPN is higher, the trust level of the NPN is indicated to be trusted by the NMS. Wherein, determining whether the network element in one NPN is trusted by the trusted metric means: the following evidence in the network element is collected by the trusted metric: the number of times the network element reports the abnormality, the data volume of the network element and other communication, or the number of times the network element is restarted, whether the evidence that the value exceeds the upper limit value or the lower limit value exists or not, if the evidence that the value exceeds the upper limit value or the lower limit value exists, the network element is not trusted, otherwise, the network element is trusted.
The user plane configuration for the first service is performed on the UPF network element, and the user plane configuration is used for enabling the UPF network element to bear user plane data of the first service.
The NMS may obtain policy and charging rules PCC rules for the first service from the PCF network element of the operator network. The PCC rule includes a user plane configuration of the first service. The NMS may convert the PCC rule into N4 session configurations corresponding to the UPF network elements of each of the N NPNs, for a total of N4 session configurations. The NMS configures N4 session configurations in a one-to-one correspondence manner to the UPF network element configurations of N NPNs respectively.
For example, the NMS may obtain policy and charging rules PCC rules for the first service from a PCF network element of the operator network, including: the NMS may send a capability open request to the PCF network element. Wherein the capability opening request is used for requesting the PCF network element to open PCC rules of the first service to the NMS. Specifically, the capability open request includes one or more of the following: information for indicating the first service, in particular flow description information of the first service, information for indicating the NMS, or information for requesting an open PCC rule; one or more PCC rules for jointly indicating to the requesting PCF network element to open the first service to the NMS. The NMS may receive a capability open response from the PCF network element returned for the capability open request. Wherein the capability open response carries the PCC rule of the first service.
For example, the NMS converts the PCC rule into N4 session configurations corresponding to the UPF network elements of the N NPN respectively, including: the NMS may select the UPF network element with the lowest load from the UPF network elements of each of the N NPN, and select the N UPF network elements altogether. The NMS may determine, according to a direction in which the first service needs to be transferred by the AS to the first area, a transfer relationship of N UPF network elements, where the transfer relationship of the N UPF network elements is used to indicate a next node of each UPF network element in the N UPF network elements, and each next node of the UPF network element refers to: the data of the first service needs to be transferred from the AS to the 1 st UPF element of the N UPF elements, from the 1 st UPF element to the 2 nd UPF element of the N UPF elements, and so on, until being transferred to the nth UPF element of the N UPF elements, and finally from the nth UPF element to the UPF element of the operator network. The NMS may copy the PCC rule for N shares to obtain N PCC rules, and encapsulate information for a next node of each UPF network element into a corresponding one of the N PCC rules according to a transfer relationship of the N UPF network elements, to obtain a corresponding N4 session configuration, and obtain N4 session configurations altogether.
It is understood that each of the N UPF network elements is a PDU session anchor. That is, no UPF element of each of the N NPN senses the presence of the UPF element of the other NPN, and therefore can be considered as a UPF element of the PDU session anchor.
It may be further understood that, unlike the prior art, the foregoing method is different from the prior art in that, in the prior art, the user plane configuration is performed on the UPF network elements in the same network by the SMF network elements in the network, and in this application, the user plane configuration of the same PDU session is performed on the UPF network elements in different networks by the NMS.
In summary, the method has the following technical effects:
1) So that the service deployment can be more flexible. For the first service of the industrial internet of things provided by the AS, namely, the first service of the public network, the user plane configuration for the first service is carried out on the UPF network elements of the N NPNs through the NMS, so that the first service can be carried by the NPNs, and the service of the public network can be carried by the private network through the fusion of the public network and the private network, thereby enabling the service deployment to be more flexible.
2) The reliability and the safety of the industrial Internet of things are improved. By using a plurality of NPNs to bear the first service, the redundancy and fault tolerance of the system can be improved, and thus the reliability of the whole industrial Internet of things is improved. Meanwhile, the user plane configuration aiming at the first service can ensure that the UPF network element can bear the user plane data of the first service, improve the safety of the data, optimize the network performance and improve the data transmission efficiency.
3) The scalability of the system is improved, i.e. when more NPNs need to be added to carry the first service, the system can be realized by adding more UPF network elements, without modifying the existing system on a large scale.
The method provided in the embodiment of the present application is described in detail above in connection with fig. 3. The following describes a data transmission device of an industrial internet of things for implementing a multi-network networking for executing the method provided by the embodiment of the present application.
The apparatus is applied to a network management system, NMS, the apparatus being configured to: the NMS receives a service request from an application service AS, wherein the service request is used for requesting the NMS to carry out user plane configuration on a first service of the industrial Internet of things, and the AS provides the first service; the NMS determines that the first service needs to be borne by N private networks NPN according to the service request, wherein N is an integer greater than 1; the NMS performs user plane configuration for the first service on each user plane function UPF network element of the N NPNs, wherein the user plane configuration for the first service on the UPF network element is used for the UPF network element to bear the user plane data of the first service.
Optionally, the service request includes at least one of: information for the first service, information for indicating that the first service is provided by the AS, or information for requesting user plane configuration, wherein at least one of the information for jointly indicating that the requesting NMS performs user plane configuration on the first service.
Optionally, the service request further includes application scope information of the first service, where the application scope information is used to indicate that a function/entity providing the first service is an AS, and an area to be served by the first service is a first area, and the first area is an area served by a public network, and the public network is an operator network; the apparatus is configured to: the NMS determines that M NPNs are deployed between the position of the AS and the first area according to the application range information, wherein M is an integer greater than 1; the NMS determines from the M nps that the first service needs to be carried by the N nps.
Optionally, the NMS determines, according to the application range information, that M NPN are disposed between the location of the AS and the first area, including: the NMS determines that M NPNs are covered in the area between the position of the AS and the first area according to the application range information and the coverage range of each NPN preconfigured by the NMS.
Optionally, the apparatus is configured to: the NMS determines N NPNs which can cover the area between the position of the AS and the first area and have the front N high credibility levels from the M NPNs according to the credibility levels of the M NPNs; or alternatively; the NMS determines whether an independent private network SNPN covers an area between the position of the AS and the first area in the M NPNs according to the types of the M NPNs; if the area between the AS position and the first area can be covered, selecting SNPN, wherein the SNPN is N NPNs; if the area between the AS position and the first area cannot be covered, selecting SNPN, and selecting public integrated private network PNI-NPN which can cover the area which cannot be covered by the SNPN from M NPNs, wherein the area which cannot be covered by the SNPN is the area which is between the AS position and the first area and cannot be covered by the SNPN, and the selected SNPN and the selected PNI-NPN are N NPNs.
Optionally, the respective trust level of the M nps is determined by periodically performing trust measurement on network elements in the M nps by the NMS, and if one NPN determines that more network elements are trusted in the NPN through the trust measurement, the trust level of the NPN is higher, and if the trust level of one NPN is higher, the NPN is trusted by the NMS; wherein, determining whether the network element in one NPN is trusted by the trusted metric means: the following evidence in the network element is collected by the trusted metric: the number of times the network element reports the abnormality, the data volume of the network element and other communication, or the number of times the network element is restarted, whether the evidence that the value exceeds the upper limit value or the lower limit value exists or not, if the evidence that the value exceeds the upper limit value or the lower limit value exists, the network element is not trusted, otherwise, the network element is trusted.
Optionally, the apparatus is configured to: the NMS obtains policy and charging rules PCC rules of the first service from PCF network elements of the operator network, wherein the PCC rules comprise user plane configuration of the first service; the NMS converts the PCC rules into N4 session configurations corresponding to the UPF network elements of each of the N NPN, N4 session configurations in total; the NMS configures N4 session configurations in a one-to-one correspondence manner to the UPF network element configurations of N NPNs respectively.
Optionally, the apparatus is configured to: the NMS sends a capability opening request to the PCF network element, wherein the capability opening request is used for requesting the PCF network element to open PCC rules of the first service to the NMS; specifically, the capability open request includes one or more of the following: information for indicating the first service, in particular flow description information of the first service, information for indicating the NMS, or information for requesting an open PCC rule; one or more PCC rules for jointly indicating to request the PCF network element to open the first service to the NMS; the NMS receives a capability opening response returned by the PCF network element for the capability opening request, wherein the capability opening response carries PCC rules of the first service.
Optionally, the apparatus is configured to: the NMS selects UPF network elements with the lowest load from the UPF network elements of each of the N NPNs, and selects N UPF network elements altogether; the NMS determines the transfer relation of N UPF network elements according to the direction of the first service to be transferred by the AS to the first area, wherein the transfer relation of the N UPF network elements is used for indicating the next node of each UPF network element in the N UPF network elements, and the next node of each UPF network element refers to: the data of the first service needs to be transmitted to the 1 st UPF network element in the N UPF network elements by the AS, and transmitted to the 2 nd UPF network element in the N UPF network elements by the 1 st UPF network element, and so on until being transmitted to the N UPF network element in the N UPF network elements, and finally transmitted to the UPF network element in the operator network by the N UPF network element; the NMS copies the PCC rules to obtain N PCC rules, and encapsulates information for the next node of each UPF network element into a corresponding PCC rule in the N PCC rules according to the transfer relation of the N UPF network elements to obtain corresponding N4 session configurations, and N4 session configurations are obtained.
Optionally, each of the N UPF network elements is a PDU session anchor.
The following describes the various constituent elements of the electronic device 500 in detail with reference to fig. 4:
the processor 501 is a control center of the electronic device 500, and may be one processor or a collective term of a plurality of processing elements. For example, processor 501 is one or more central processing units (central processing unit, CPU), but may also be an integrated circuit (application specific integrated circuit, ASIC), or one or more integrated circuits configured to implement embodiments of the present application, such as: one or more microprocessors (digital signal processor, DSPs), or one or more field programmable gate arrays (field programmable gate array, FPGAs).
Alternatively, the processor 501 may perform various functions of the electronic device 500, such as the functions in the method shown in FIG. 3 described above, by running or executing a software program stored in the memory 502 and invoking data stored in the memory 502.
In a particular implementation, the processor 501 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG. 4, as an embodiment.
In a particular implementation, as one embodiment, the electronic device 500 may also include multiple processors. Each of these processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).
The memory 502 is configured to store a software program for executing the present application, and the processor 501 controls the execution of the software program, and the specific implementation may refer to the above method embodiment, which is not described herein again.
Alternatively, memory 502 may be read-only memory (ROM) or other type of static storage device that may store static information and instructions, random access memory (random access memory, RAM) or
Other types of dynamic storage devices, which can store information and instructions, can also be, but are not limited to, an electrically erasable programmable read-only memory (EEPROM), a compact disk read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disc, etc.), magnetic disk storage or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and capable of being accessed by a computer. The memory 502 may be integral with the processor 501 or may exist separately from the processor and the electronic device 500
Is coupled to the processor 501 (not shown in fig. 4), as embodiments of the present application are not particularly limited.
A transceiver 503 for communication with other devices. For example, the multi-beam based positioning device is a terminal and the transceiver 503 may be used to communicate with a network device or with another terminal.
Alternatively, the transceiver 503 may include a receiver and a transmitter (not separately shown in fig. 4). The receiver is used for realizing the receiving function, and the transmitter is used for realizing the transmitting function.
Alternatively, the transceiver 503 may be integrated with the processor 501, or may exist separately, and be coupled to the processor 501 through an interface circuit (not shown in fig. 4) of the electronic device 500, which is not specifically limited in this embodiment of the present application.
It should be noted that the structure of the electronic device 500 shown in fig. 4 does not limit the apparatus, and the actual electronic device 500 may include more or less components than those shown, or may combine some components, or may be different in arrangement of components.
In addition, the technical effects of the method according to the above method embodiment may be referred to for the technical effects of the electronic device 500, which are not described herein.
It should be appreciated that the processor in embodiments of the present application may be a central processing unit (central processing unit, CPU), which may also be other general purpose processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits (application specific integrated circuit, ASIC), off-the-shelf programmable gate arrays (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
It should also be appreciated that the memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM) which acts as an external cache. By way of example but not limitation, many forms of random access memory (random access memory, RAM) are available, such as Static RAM (SRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced Synchronous Dynamic Random Access Memory (ESDRAM), synchronous Link DRAM (SLDRAM), and direct memory bus RAM (DR RAM).
The above embodiments may be implemented in whole or in part by software, hardware (e.g., circuitry), firmware, or any other combination. When implemented in software, the above-described embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product comprises one or more computer instructions or computer programs. When the computer instructions or computer program are loaded or executed on a computer, the processes or functions in accordance with the embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website site, computer, server, or data center to another website site, computer, server, or data center by wired (e.g., infrared, wireless, microwave, etc.) means. Computer readable storage media can be any available media that can be accessed by a computer or data storage devices, such as servers, data centers, etc. that contain one or more collections of available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. The semiconductor medium may be a solid state disk.
It should be understood that the term "and/or" is merely an association relationship describing the associated object, and means that three relationships may exist, for example, a and/or B may mean: there are three cases, a alone, a and B together, and B alone, wherein a, B may be singular or plural. In addition, the character "/" herein generally indicates that the associated object is an "or" relationship, but may also indicate an "and/or" relationship, and may be understood by referring to the context.
In the present application, "at least one" means one or more, and "a plurality" means two or more. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b, or c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or plural.
It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the partitioning of elements is merely a logical functional partitioning, and there may be additional partitioning in actual implementation, e.g., multiple elements or components may be combined or integrated into another system, or some feature fields may be omitted, or not implemented. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods of the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes or substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (8)

1. A data transmission method of an industrial internet of things implemented by multi-network networking, wherein the method is applied to a network management system NMS, the method comprising:
the NMS receives a service request from an application service AS, wherein the service request is used for requesting the NMS to carry out user plane configuration on a first service of the industrial Internet of things, and the AS provides the first service;
the NMS determines that the first service needs to be borne by N private networks NPN according to the service request, wherein N is an integer greater than 1;
the NMS performs user plane configuration for the first service on the user plane function UPF network elements of the N NPNs, wherein the user plane configuration for the first service is performed on the UPF network elements so that the UPF network elements can bear user plane data of the first service;
The service request further includes application scope information of the first service, where the application scope information is used to indicate that a function/entity providing the first service is the AS, and an area to be served by the first service is a first area, where the first area is an area served by a public network, and the public network is an operator network;
the NMS determining, according to the service request, that the first service needs to be carried by N private networks NPN, including:
the NMS determines that M NPNs are deployed between the position of the AS and the first area according to the application range information, wherein M is an integer greater than 1;
the NMS determines that the first service needs to be carried by the N NPNs from the M NPNs;
the NMS determining from the M nps that the first service needs to be carried by the N nps, including:
the NMS determines N NPNs which can cover the area between the position of the AS and the first area from the M NPNs according to the respective credibility levels of the M NPNs, and the N NPNs with the credibility levels being higher than the front N;
or alternatively;
the NMS determines whether an independent private network SNPN covers an area between the position of the AS and the first area in the M NPNs according to the types of the M NPNs; if the area between the AS position and the first area can be covered, selecting the SNPN, wherein the SNPN is the N NPNs; and if the area between the AS position and the first area cannot be covered, selecting the SNPN, and selecting a public integrated private network PNI-NPN which can cover the area which cannot be covered by the SNPN from the M NPNs, wherein the area which cannot be covered by the SNPN is the area which is between the AS position and the first area and cannot be covered by the SNPN, and the selected SNPN and the selected PNI-NPN are the N NPNs.
2. The method of claim 1, wherein the service request comprises at least one of: information for the first service, information for indicating that the first service is provided by the AS, or information for requesting user plane configuration, wherein the at least one item is used to jointly indicate that the NMS is requested to perform user plane configuration on the first service.
3. The method of claim 1 wherein the NMS determining, based on the application scope information, that M NPN are disposed between the location of the AS and the first area comprises:
and the NMS determines that the M NPNs are covered in the area between the position of the AS and the first area according to the application range information and the coverage range of each NPN preconfigured by the NMS.
4. The method of claim 1 wherein the respective trust level of the M nps is determined by the NMS periodically by a trust metric for each of the network elements in the M nps, the trust level of one NPN being higher if the one NPN determines that the more of the network elements are trusted by the trust metric, and the trust level of the one NPN being higher if the one NPN is trusted by the NMS; wherein, determining whether the network element in one NPN is trusted by the trusted metric means: the following evidence in the network element is collected by the trusted metric: the number of times the network element reports the abnormality, the data volume of the network element and other communication, or the number of times the network element is restarted, whether the evidence that the value exceeds the upper limit value or the lower limit value exists or not, if the evidence that the value exceeds the upper limit value or the lower limit value exists, the network element is not trusted, otherwise, the network element is trusted.
5. The method according to claim 1, 3 or 4, wherein the NMS performing user plane configuration for the first service on the respective user plane function UPF network elements of the N NPN comprises:
the NMS obtains policy and charging rules PCC rules of the first service from PCF network elements of the operator network, wherein the PCC rules comprise user plane configuration of the first service;
the NMS converts the PCC rule into N4 session configurations corresponding to the UPF network elements of the N NPNs respectively, and N4 session configurations are altogether;
the NMS configures the N4 session configurations in a one-to-one correspondence manner to the UPF network element configurations of the N NPNs respectively.
6. The method of claim 5 wherein the NMS obtaining policy and charging rules, PCC, rules for the first service from a PCF network element of the operator network, comprising:
the NMS sends a capability opening request to the PCF network element, wherein the capability opening request is used for requesting the PCF network element to open the PCC rule of the first service to the NMS; specifically, the capability open request includes one or more of the following: information for indicating the first service, in particular, flow description information of the first service, information for indicating the NMS, or information for requesting an open PCC rule; the one or more items are configured to jointly instruct requesting the PCF network element to open the PCC rule for the first service to the NMS;
The NMS receives a capability open response returned by the PCF network element for the capability open request, wherein the capability open response carries the PCC rule of the first service.
7. The method of claim 5, wherein the NMS converting the PCC rule into an N4 session configuration corresponding to the UPF network element for each of the N NPN, comprising:
the NMS selects UPF network elements with the lowest load from the UPF network elements of the N NPNs, and selects N UPF network elements altogether;
the NMS determines the transfer relation of the N UPF network elements according to the direction of the first service to be transferred by the AS to the first area, wherein the transfer relation of the N UPF network elements is used for indicating the next node of each UPF network element in the N UPF network elements, and the next node of each UPF network element refers to: the data of the first service needs to be transferred from the AS to a 1 st UPF network element in the N UPF network elements, and from the 1 st UPF network element to a 2 nd UPF network element in the N UPF network elements, and so on until being transferred to the N UPF network element in the N UPF network elements, and finally from the N UPF network element to the UPF network element in the operator network;
The NMS copies the PCC rules to obtain N PCC rules, and encapsulates information for the next node of each UPF network element into a corresponding PCC rule in the N PCC rules according to the transfer relation of the N UPF network elements to obtain corresponding N4 session configurations, and N4 session configurations are obtained.
8. The method of claim 7, wherein each of the N UPF network elements is a PDU session anchor.
CN202410025755.0A 2024-01-08 2024-01-08 Industrial Internet of things data transmission method realized by multi-network networking Active CN117528462B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202410025755.0A CN117528462B (en) 2024-01-08 2024-01-08 Industrial Internet of things data transmission method realized by multi-network networking

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202410025755.0A CN117528462B (en) 2024-01-08 2024-01-08 Industrial Internet of things data transmission method realized by multi-network networking

Publications (2)

Publication Number Publication Date
CN117528462A CN117528462A (en) 2024-02-06
CN117528462B true CN117528462B (en) 2024-03-22

Family

ID=89764871

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202410025755.0A Active CN117528462B (en) 2024-01-08 2024-01-08 Industrial Internet of things data transmission method realized by multi-network networking

Country Status (1)

Country Link
CN (1) CN117528462B (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022032598A1 (en) * 2020-08-13 2022-02-17 华为技术有限公司 Subscription data configuration method and apparatus
WO2022095047A1 (en) * 2020-11-09 2022-05-12 Oppo广东移动通信有限公司 Wireless communication method, terminal device, and network device
WO2022270893A1 (en) * 2021-06-23 2022-12-29 주식회사맥데이타 Network security monitoring device and method based on security packet of terminal
WO2023071316A1 (en) * 2021-10-29 2023-05-04 华为技术有限公司 Network capability exposure method, apparatus, and system
WO2023185015A1 (en) * 2022-03-29 2023-10-05 华为技术有限公司 Communication method, communication apparatus and communication system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022032598A1 (en) * 2020-08-13 2022-02-17 华为技术有限公司 Subscription data configuration method and apparatus
WO2022095047A1 (en) * 2020-11-09 2022-05-12 Oppo广东移动通信有限公司 Wireless communication method, terminal device, and network device
WO2022270893A1 (en) * 2021-06-23 2022-12-29 주식회사맥데이타 Network security monitoring device and method based on security packet of terminal
WO2023071316A1 (en) * 2021-10-29 2023-05-04 华为技术有限公司 Network capability exposure method, apparatus, and system
WO2023185015A1 (en) * 2022-03-29 2023-10-05 华为技术有限公司 Communication method, communication apparatus and communication system

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
Futurewei, Sennheiser, Philips.S2-2004235 "KI #2, New Sol: simultaneous connection with NPN and PLMN with QoS consideration for VIAPA.".3GPP tsg_sa\wg2_arch.2020,(tsgs2_139e_electronic),全文. *
Huawei, HiSilicon.S2-1911567 "Key Issue: Optimizations of 5GS for NPN.".3GPP tsg_sa\wg2_arch.2019,(tsgs2_136_reno),第1页至第2页. *
Key Issue: Optimizations of 5GS for NPN;Huawei, HiSilicon;《SA WG2 Meeting #136 S2-1912335》;20191122;全文 *

Also Published As

Publication number Publication date
CN117528462A (en) 2024-02-06

Similar Documents

Publication Publication Date Title
EP4138438A1 (en) Communication method and apparatus, and chip
CA3117004C (en) Method for obtaining capability information of terminal, apparatus, and system
CN113630749A (en) Method and device for acquiring edge service
US20240056496A1 (en) Method and Apparatus for Selecting Edge Application Server
US20240073848A1 (en) Network Slice in a Wireless Network
CN117528462B (en) Industrial Internet of things data transmission method realized by multi-network networking
CN117478431B (en) Industrial Internet of things control method based on trusted network
CN117221884B (en) Base station system information management method and system
CN117202287B (en) Order distribution management method and device based on big data analysis
CN117439819B (en) PDU cabinet safety monitoring method
CN115567899B (en) Error analysis method and device for intelligent ammeter
EP4210302A1 (en) Apparatus, methods, and computer programs
CN115499470B (en) Storage management method and device for intelligent ammeter data
CN115320428B (en) Charging control method and device for electric automobile charging pile
CN115499788B (en) Distributed node-based risk area determination method and device
CN117715040B (en) Distribution network communication method and device of DPLC modules
CN117768965A (en) High-performance connection and transmission method of bonding silver wire equipment
WO2024012230A1 (en) Communication method and apparatus
WO2022261972A1 (en) Apparatus, methods, and computer programs
US20230148200A1 (en) Apparatus, methods, and computer programs
CN117439992A (en) Self-adaptive control method and system for electrical equipment
CN117062015A (en) Data connection distribution method and device using Beidou positioning and short message system
CN117858084A (en) Management method and device for group control charging pile of group management
CN116996985A (en) Communication method and device based on edge network
CN117715040A (en) Distribution network communication method and device of DPLC module

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant