CN114885382B

CN114885382B - Service session management method, device and storage medium

Info

Publication number: CN114885382B
Application number: CN202210811929.7A
Authority: CN
Inventors: 俞一帆
Original assignee: Beijing Ailingke Technology Co ltd
Current assignee: Beijing Ailingke Technology Co ltd
Priority date: 2022-07-12
Filing date: 2022-07-12
Publication date: 2022-10-25
Anticipated expiration: 2042-07-12
Also published as: CN114885382A

Abstract

The embodiment of the invention provides a service session management method, a device and a storage medium, which relate to the field of communication and are applied to a local network service presentation function Network Element (NEF), wherein the method comprises the following steps: the local NEF receives a query request and a call request sent by a private network management system, wherein the query request comprises: the address of the industrial controller is determined according to a control instruction sent to the private network management system by the enterprise fusion operation management and control system; the call request includes: a service session quality of service (QoS) strategy; the local NEF inquires and acquires context information of the accessible local terminal according to the inquiry request, and extracts a permanent identifier from the context information; and the local NEF determines a target network element according to the call request and sends the permanent identifier and the service session QoS strategy to the target network element. By adopting the method and the system, the step of deploying the private network management system by an enterprise can be simplified, and the security risk of the public network can be reduced.

Description

Service session management method, device and storage medium

Technical Field

The present invention relates to the field of communications, and in particular, to a method, an apparatus, and a storage medium for managing a service session.

Background

At present, the deployment of a 5G private network becomes a necessary means for promoting 5G innovation application, expanding production efficiency and accelerating digital transformation in the vertical industry.

In the 5G mixed private network, a 5G private network management system and an enterprise fusion operation management and control system are deployed in an enterprise security control domain, and a lightweight 5G core network is deployed in a public network operator security domain. The 5G private network management system must access the UDM (unified data management) of the 5G public network to issue the management and control instruction to the terminal accessing the 5G core network.

However, since the UDM of the 5G public network belongs to a key core network element, the 5G private network management system must be modified complicatedly according to the requirements of the public network operator to access the network element, which will greatly increase the complexity and cost of enterprise users developing the system. In addition, because of the numerous enterprise users, directly exposing the UDM of the 5G public network to a large number of third-party systems also increases the potential safety hazard of the 5G public network.

Disclosure of Invention

Embodiments of the present invention provide a method, an apparatus, and a storage medium for managing a service session, which can simplify a step of deploying a private network management system by an enterprise, and reduce security risks faced by a public network.

The first invention provides a service session management method, which is applied to a local network open function Network Element (NEF), and the method comprises the following steps:

the local NEF receives a query request and a call request sent by a private network management system, wherein the query request comprises: the address of the industrial controller is determined according to a control instruction sent to the private network management system by the enterprise convergence operation management and control system; the call request includes: a service session quality of service (QoS) strategy;

the local NEF inquires and acquires context information of an accessible local terminal according to the inquiry request, and extracts a permanent identifier from the context information;

and the local NEF determines a target network element according to the calling request and sends the permanent identifier and the service session QoS strategy to the target network element.

Optionally, the control instruction includes: the address of the industrial controller is determined by the private network management system according to the service identifier, and the service session QoS strategy is determined by the enterprise convergence operation management and control system according to the service identifier obtained by an internal database;

the local NEF receives a query request and a call request sent by a private network management system, and comprises the following steps:

and the local NEF receives the query request sent by the private network management system and the call request which can be identified by the local NEF and is generated by the private network management system based on the control instruction conversion.

Optionally, the querying, by the local NEF according to the query request, to acquire context information of an accessible local terminal includes:

the local NEF sends a context query request to a local unstructured data storage function network element UDSF according to the query request;

and the local NEF receives the context information returned by the local UDSF according to the context query request.

Optionally, the method further comprises:

if the service session QoS policy needs to be processed by a local policy control function network element PCF, the local NEF converts the service session QoS policy into a policy and charging control network element PCC rule and sends a protocol data unit network element PDU session policy update request to the local PCF, wherein the local PCF notifies a local session management function network element SMF and triggers PDU session update after receiving the PDU session policy update request.

Optionally, the method further comprises:

and if the service session QoS strategy needs to be processed by a local unified data management network element UDM, the local NEF converts the service session QoS strategy into user subscription data and sends a user subscription data updating request to the local UDM, wherein after receiving the user subscription data updating request, the local UDM initiates a query through the unified data management network element UDM in the public network to request for changing the legality of the user subscription data.

Optionally, when detecting that the context information changes, the local SMF sends the updated context information to a local unstructured data storage function network element UDSF.

In a second aspect, an embodiment of the present invention further provides a service session management method, which is applied to a private network management system, and the method includes:

the private network management system receives a control instruction sent by the enterprise fusion operation management and control system, and generates a query request and a call request according to the control instruction;

the private network management system sends the query request and the call request to a local network open function network element NEF, where the query request includes: an industrial controller address, the call request comprising: a service session quality of service (QoS) strategy; and the local NEF queries and acquires context information of an accessible local terminal according to the query request, extracts a permanent identifier from the context information, determines a target network element according to the call request, and sends the permanent identifier and the service session QoS strategy to the target network element.

In a third aspect, an embodiment of the present invention further provides a service session management apparatus, which is applied to a local network open function network element NEF, where the apparatus includes:

a receiving module, configured to receive, by the local NEF, a query request and a call request sent by a private network management system, where the query request includes: the address of the industrial controller is determined according to a control instruction sent to the private network management system by the enterprise fusion operation management and control system; the call request comprises: a service session quality of service (QoS) strategy;

an obtaining module, configured to query and obtain context information of an accessible local terminal according to the query request by the local NEF, and extract a permanent identifier from the context information;

a first sending module, configured to determine, by the local NEF, a target network element according to the invocation request, and send the permanent identifier and the service session QoS policy to the target network element.

In a fourth aspect, an embodiment of the present invention further provides a service session management apparatus, which is applied to a private network management system, where the apparatus includes:

the processing module is used for receiving a control instruction sent by the enterprise fusion operation management and control system by the private network management system, and generating a query request and a call request according to the control instruction;

a second sending module, configured to send, by the private network management system, the query request and the invocation request to a local network open function network element NEF, where the query request includes: an industrial controller address, the call request comprising: and the QoS strategy of the service session enables the local NEF to acquire the context information of the accessible local terminal according to the query request query, extracts the permanent identifier from the context information, enables the local NEF to determine a target network element according to the call request, and sends the permanent identifier and the QoS strategy of the service session to the target network element.

In a fifth aspect, an embodiment of the present invention further provides a computer-readable storage medium, where the storage medium stores a computer program, and the computer program is executed by a processor to perform the steps of the service session management method according to any one of the first aspect and the second aspect.

The beneficial effect of this application is:

the application provides a service session management method, a device and a storage medium, which are applied to a local network service presentation function network element NEF, and the method comprises the following steps: the local NEF receives a query request and a call request sent by a private network management system, wherein the query request comprises: the address of the industrial controller is determined according to a control instruction sent to the private network management system by the enterprise fusion operation management and control system; the call request includes: a service session quality of service (QoS) strategy; the local NEF inquires and acquires context information of the accessible local terminal according to the inquiry request, and extracts a permanent identifier from the context information; and the local NEF determines a target network element according to the call request and sends the permanent identifier and the service session QoS strategy to the target network element. By the method, the enterprise terminal can control the QoS strategy of the service session to the local terminal without building a complex system, complexity and cost of strategy control cost of the enterprise terminal are reduced, meanwhile, the problem that a key core network element of a public network in a traditional framework must be directly opened to a third-party system is avoided, possibility of attacking the public network is reduced, and safety of the public network is guaranteed.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.

Fig. 1 is a schematic diagram of a local network architecture of a service session management method according to an embodiment of the present application;

fig. 2 is a schematic diagram of a network system architecture of a service session management method according to an embodiment of the present application;

fig. 3 is a schematic flowchart of a service session management method according to an embodiment of the present application;

fig. 4 is a flowchart illustrating another service session management method according to an embodiment of the present application;

fig. 5 is a schematic flowchart of another service session management method according to an embodiment of the present application;

fig. 6 is a schematic diagram of a service session management apparatus according to an embodiment of the present application;

fig. 7 is a schematic diagram of another service session management apparatus according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all embodiments of the present invention. The components of embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.

Thus, the following detailed description of the embodiments of the present invention, as presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. All other embodiments, which can be obtained by a person skilled in the art without inventive step based on the embodiments of the present invention, are within the scope of protection of the present invention.

It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined or explained in subsequent figures.

Before explaining the present invention in detail, an application scenario of the present invention will be described.

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: global system for mobile communications (GSM) systems, code Division Multiple Access (CDMA) systems, wideband Code Division Multiple Access (WCDMA) systems, general Packet Radio Service (GPRS), long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD), universal mobile telecommunications system (universal mobile telecommunications system, UMTS), worldwide Interoperability for Microwave Access (WiMAX) communication systems, fifth generation (5, 5 g) communication systems, or future radio access (NR) technologies.

Fig. 1 is a schematic diagram of a local network architecture suitable for a service session management method provided in an embodiment of the present application. As shown in fig. 1, the home network architecture may be, for example, a non-roaming (non-roaming) architecture. The network architecture may specifically include the following network elements:

1. terminal equipment (UE): may be referred to as user equipment, a terminal, an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or user equipment. The UE may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network or a terminal device in a Public Land Mobile Network (PLMN) for future evolution, and the like, and may also be an end device, a logic entity, an intelligent device, a terminal device such as a mobile phone, an intelligent terminal, and the like, or a communication device such as a server, a gateway, a base station, a controller, and the like, or an Internet of things device such as a sensor, an electric meter, a water meter, and the like (Internet of things, ioT) device. The embodiments of the present application do not limit this.

2. NG radio access network (NG-RAN): the Radio Access Network (RAN) of a 5G system (5 GS) is named NG-RAN by the third generation partnership project (3 gpp) access technology (e.g., the radio access technology employed in 3G, 4G, or 5G systems). The radio access network can manage radio resources, provide access service for the terminal, and further complete the forwarding of control signals and user data between the terminal and the core network. The 3GPP access technology refers to an access technology conforming to the 3GPP standard specification. The NG-RAN is called Next Generation (NG) because it is a multi-layer heterogeneous network that can satisfy multiple scenarios, and can accommodate various radio access technologies that have been widely used to satisfy the requirements of characteristics such as mobility, time-delay, access rate, traffic density, connection number density, spectrum efficiency, and energy efficiency of 5 GS.

The access network equipment may include, among other things, equipment in the access network that communicates over the air-interface, through one or more sectors, with the wireless terminals. The access network system may be configured to interconvert received air frames and Internet Protocol (IP) packets as routers between the wireless terminal and the rest of the access network, which may include an IP network. The radio access network system may also coordinate management of attributes for the air interface. It should be understood that access network devices include, but are not limited to: evolved node B (eNB), radio Network Controller (RNC), node B (NB), base Station Controller (BSC), base transceiver station (base transceiver station, BTS), home base station (e.g., home evolved node B, or home node B, HNB), base Band Unit (BBU), wireless fidelity (WIFI), etc., and may also be 5G, such as NR, gNB in the system, or transmission point (TRP or TP), one or a set of antenna panels (including multiple antenna panels) of a base station in the 5G system, or may also be a distributed antenna panel (NB), or may be a Radio Network Controller (RNC) panel, or a distributed antenna panel (distribution node) of a base station in the 5G system, such as a Base Transceiver Station (BTS), a home base station (HNB), or a radio backhaul base station (BBU), etc.

In some deployments, the gNB may include a Centralized Unit (CU) and a DU. The gNB may also include a Radio Unit (RU). The CU implements part of functions of the gNB, the DU implements part of functions of the gNB, for example, the CU implements Radio Resource Control (RRC) and Packet Data Convergence Protocol (PDCP) layers, and the DU implements Radio Link Control (RLC), media Access Control (MAC) and Physical (PHY) layers. Since the information of the RRC layer eventually becomes or is converted from the information of the PHY layer, the higher layer signaling, such as the RRC layer signaling, may also be considered to be transmitted by the DU or the DU + CU under this architecture. It is to be understood that the access network device may be a CU node, or a DU node, or a device including a CU node and a DU node. In addition, the CU may be divided into access network devices in a Radio Access Network (RAN), or may be divided into access network devices in a Core Network (CN), which is not limited herein.

3. Access and mobility management function (AMF): the method is mainly used for mobility management, access management, and the like, and can be used for implementing functions other than session management in Mobility Management Entity (MME) functions, such as functions of lawful interception, or access authorization (or authentication), and the like. In the embodiment of the present application, the method can be used for implementing the functions of the access and mobility management network element.

4. Session management function network element (SMF): the method is mainly used for session management, internet Protocol (IP) address allocation and management of the UE, selection of a termination point of an interface capable of managing a user plane function, policy control or charging function, downlink data notification, and the like. In the embodiment of the present application, the method and the device can be used for implementing the function of the session management network element.

5. User Plane Function network element (User Plane Function, UPF): i.e. a data plane gateway. The method can be used for packet routing and forwarding, or quality of service (QoS) processing of user plane data, and the like. The user data can be accessed to a Data Network (DN) through the network element. In the embodiment of the application, the method can be used for realizing the function of the user plane gateway.

6. Policy control function network element (PCF): the unified policy framework is used for guiding network behaviors, providing policy rule information for control plane function network elements (such as AMF and SMF network elements) and the like.

7. Unified data management network element (UDM): for handling subscriber identification, access authentication, registration, or mobility management, etc.

8. Data Network (DN): such as operator services, internet or third party services, etc.

9. Network open Function (NEF): and all external applications which are positioned between the 5G core network and the external third-party application function body and are responsible for managing the data of the external open network need to pass through the NEF when the external applications want to access the internal data of the core network. The NEF provides corresponding security guarantee to ensure the security of the external application to the 3gpp network, and provides functions of external application Qos customization capability opening, mobility state event subscription, AF request distribution, and the like.

10. Network Slice Selection Function (NSSF) entity: and determining the network slice example which is allowed to be accessed by the UE according to the slice selection auxiliary information, the subscription information and the like of the UE.

11. Network storage function network element (NRF): a new Function that provides registration and discovery functions enables Network Functions (NFs) to discover each other and communicate through an API (Application Programming Interface) Interface.

12. Authentication server function network element (AUSF): and the authentication server function is used for realizing the access authentication of 3GPP and non-3 GPP.

13. Application function network element (AF): the AF may interact with the NF of the core network to obtain network information and send control information to obtain the required diversified services.

14. Unstructured data storage function network element (UDSF): any NF is allowed in the 5G system architecture to store and retrieve its unstructured data into the UDSF, such as session IDs, state data, UE context real-time data used by the AMF and SMF. Multiple NFs may share a UDSF store, or a NF may have a dedicated UDSF.

In the network architecture, an N1 interface is a reference point between a terminal and an AMF network element; the N2 interface is a reference point of NG-RAN and AMF network elements and is used for sending non-access stratum (NAS) messages and the like; the N3 interface is a reference point between the NG-RAN and the UPF network element and is used for transmitting data of a user plane and the like; the N4 interface is a reference point between the SMF network element and the UPF network element, and is used to transmit information such as tunnel identifier information, data cache indicator information, and downlink data notification message for the N3 connection; the N5 interface is a reference point between the UPF network element and the DN, and is used for transmitting user plane data and the like.

It should be understood that the network architecture applied to the embodiments of the present application is only an exemplary network architecture described in terms of a conventional point-to-point architecture and a service architecture, and the network architecture to which the embodiments of the present application are applied is not limited thereto, and any network architecture capable of implementing the functions of the network elements described above is applicable to the embodiments of the present application.

It should also be understood that the AMFs, SMFs, UPFs, PCFs, UDMs, NEFs, NSSFs, NRFs, AUSFs, AFs and UDSFs shown in fig. 1 may be understood as network elements in the core network for implementing different functions, e.g. may be combined into network slices as needed. The core network elements may be independent devices, or may be integrated in the same device to implement different functions, which is not limited in this application.

As shown in fig. 1, NSSF network elements are connected to a bus through an NSSF interface, NEF network elements are connected to the bus through an Nnef interface, NRF network elements are connected to the bus through an nrrf interface, PCF network elements are connected to the bus through an Npcf interface, UDM network elements are connected to the bus through a numdm interface, AF network elements are connected to the bus through a Naf interface, AUSF network elements are connected to the bus through a Nausf interface, AMF network elements are connected to the bus through a Namf interface, SMF network elements are connected to the bus through an Nsmf interface, and UDSF network elements are connected to the bus through a Nudsf interface. The NSsf interface is a service-based interface displayed by an NSSF network element, the Nnef interface is a service-based interface displayed by an NEF network element, the Npcf is a service-based interface displayed by a PCF network element, the Nudm is a service-based interface displayed by a UDM network element, the Naf is a service-based interface displayed by an AF network element, the Nausf is a service-based interface displayed by an AUSF network element, the Namf is a service-based interface displayed by an AMF network element, the Nsmf is a service-based interface displayed by an SMF network element, and the Nudsf is a service-based interface displayed by an UDSF network element.

It should be understood that the above-mentioned names are only used for distinguishing different functions, and do not represent that these network elements are respectively independent physical devices, and the present application is not limited to the specific form of the above-mentioned network elements, for example, they may be integrated in the same physical device, or they may be different physical devices. Furthermore, the above nomenclature is used only to distinguish between different functions and should not be construed as limiting the application in any way, and the application does not preclude the possibility of other nomenclature being used in 5G networks and other networks in the future. For example, in a 6G network, some or all of the above network elements may follow the terminology in 5G, and may also adopt other names. The description is unified here, and will not be repeated below.

It should also be understood that the name of the interface between each network element in fig. 1 is only an example, and the name of the interface in the specific implementation may be other names, which is not specifically limited in this application. In addition, the name of the transmitted message (or signaling) between the network elements is only an example, and the function of the message itself is not limited in any way.

For better understanding of the embodiment of the present application, the present application takes a 5G network as an example, a 5G local network developed based on 5G technology is also referred to as a private 5G network, and the private 5G network is created on the local user site by using 5G technology, has uniform connectivity, optimized services and a secure communication mode in a specific area, and provides characteristics of high transmission speed, low delay and mass connection supported by 5G technology. The 5G local network is constructed based on 5G equipment, and comprises 5G terminal equipment, a 5G wireless base station and 5G core network equipment, wherein the equipment is dedicated to a network owner, namely a local user, and can be independently managed and easily deployed. The 5G home network may eliminate reliance on wired devices such as ethernet, which are not only expensive and cumbersome, but also unable to connect large numbers of mobile devices and personnel.

The 5G home network may be configured locally and the network is fully controlled by the network owner, e.g., security, network resource usage, etc., who may assign critical devices a higher priority to use the network resources. Almost any campus, enterprise building or public place can deploy 5G local networks, and especially in certain areas where public 5G networks are slow to deploy, 5G local networks can achieve rapid deployment.

As a new important growth point of the communication market, 5G can greatly improve the broadband experience of mobile Internet users, and service objects also take user demands of more industries into consideration from traditional personal users. In a 5G hybrid private network, a loan enhancement and low-delay private network can be provided for enterprise customers through flexible customization of technologies such as multi-frequency cooperation, edge node, qos (Quality of Service) enhancement, slicing and the like, so that the digitization of the enterprise customers is realized. In specific implementation, the local nodes are deployed in a client side environment, and the central nodes are deployed in a public network operator environment. And part of public network operators access the local nodes to the central node based on the return line of the 5G public network. The local node is special for enterprise customers, can meet the network information safety requirements of the customers, and ensures that the customers can independently control each core network element in the local node. In a security control domain of an enterprise network, a local node is connected to an enterprise information system through a firewall configured with an enterprise information security policy.

For enterprise customers, deep control of terminals accessing a 5G hybrid private network needs to be performed through a 5G private network management system, but the existing system cannot support the control. Specifically, the 5G private network management system and the enterprise converged operation management system are deployed in an enterprise security control domain, and the lightweight 5GC (5G core,5G core network) is deployed in a public network operator security domain. In the existing system, a 5G private network management system must access a 5G public network UDM in a central node, and then issue a management and control instruction to a terminal accessing a local 5G core network. Because the 5G public network UDM belongs to a key core network element, the 5G private network management system must be modified complicatedly according to the requirements of public network operators to access the network element, which will greatly increase the complexity and cost of enterprise users developing the system. In addition, because of numerous enterprise users, directly exposing the 5G public network UDM to a large number of third party systems also increases the potential safety hazard of the 5G public network.

Based on the above, the application provides a business session management method to simplify the step of deploying the private network management system by an enterprise and reduce the security risk faced by the public network.

Fig. 2 is a schematic diagram of a network system architecture of a service session management method according to an embodiment of the present application. As shown in fig. 2, in the network system architecture, the 5G private network management system accesses the 5G local NEF through a private line. Therefore, when the enterprise convergence operation management system wants to perform related service session control on the local UE, the service session control instruction related to the local UE can be issued to the 5G private network management system, and the 5G private network management system sends the control instruction from the enterprise convergence operation management system to the local NEF, so that the local NEF can complete control and adjustment of the related service session of the local UE through interaction with other local network elements. Meanwhile, for a 5G public network, interaction with a local UDM in a security domain of a public network operator can be realized through the public network UDM.

In order to describe in detail specific steps of the local NEF implementing the service session management method provided by the present application, the following describes a plurality of embodiments.

Fig. 3 is a schematic flowchart of a service session management method provided in an embodiment of the present application, where an execution subject of the method is a local NEF. As shown in fig. 3, the method may include:

s110, the local NEF receives the query request and the call request sent by the private network management system.

The query request includes: the address of the industrial controller is determined according to a control instruction sent to the private network management system by the enterprise fusion operation management and control system; the call request includes: traffic session QoS policies.

In order to meet the demand of people for higher-performance mobile communication, a 5G network architecture needs to support various new services which are continuously emerging, and different services under a 5G application scenario have different characteristics and Qos requirements. In the present application, the 5G network architecture includes: the system comprises a 5G local network (hereinafter referred to as local), a 5G public network (hereinafter referred to as public network), a 5G private network management system (hereinafter referred to as private network management system), and an enterprise convergence operation management and control system. The private network management system and the enterprise fusion operation management and control system are deployed in an enterprise security control domain, and the local node is deployed in a public network operator security domain.

In the Application, the NEF is deployed locally, the local NEF provides the external opening of the 5G network capability, the local NEF is in butt joint with all other network elements in a bus mode, and an Application Programming Interface (API) Interface is provided through an Nnef Interface for calling to support the external opening of the Qos capability, so that the private network management system can open the network capability for the enterprise client through the local NEF, so that the enterprise client can perform related service session control on the local UE, and different services can obtain corresponding service session Qos requirements.

In this embodiment, after the enterprise converged operation management and control system accesses the network, a control instruction may be sent to the private network management system.

The enterprise convergence operation management and control system reads a specific service identifier (for example, an IP address of a certain industrial server or an IP address of a certain industrial controller) from an internal database; a service session QoS policy may also be generated corresponding to the particular service identification. And then the enterprise convergence operation management and control system packages the service identification and the corresponding service session QoS strategy into a control instruction and sends the control instruction to the private network management system. Optionally, in an actual usage scenario, an enterprise user may input a service adjustment instruction in the enterprise converged operation management and control system according to a target service that needs to be adjusted, where the service adjustment instruction includes an IP address of an industrial controller corresponding to the target service, so that the enterprise converged operation management and control system generates a control instruction based on the IP address of the industrial controller in the service adjustment instruction to send the control instruction to the private network management system.

Optionally, the virtual industrial fieldbus includes a plurality of UEs, the plurality of UEs and the local SMF have a plurality of established PDU sessions (sessions), and an IP address of each industrial controller corresponds to a service subscribed by the local UE one to one. When the enterprise convergence operation management and control system needs to control and adjust the related service session of the local UE, the encapsulated control instruction includes an IP address of the industrial controller and a QoS policy of the service session that needs to be managed and controlled. A traffic session QoS policy refers to a series of QoS parameters for a data flow between a core network, an access network, and a UE. Optionally, the traffic session QoS policy may include, but is not limited to: average rate, priority level, average window, maximum data burst size, minimum delay and delay jitter, etc.

After receiving the control instruction sent by the enterprise convergence operation management and control system, the private network management system needs to send a query request and a call request to the local NEF according to the information of the control instruction. Wherein, the query request includes: the address of the industrial controller, that is, the IP address of the industrial controller, and the local NEF may obtain the relevant information of the UE according to the query request. The call request includes: and a service session QoS strategy, wherein the local NEF can determine a target network element for initiating the service session modification at this time and a specific service session QoS strategy according to the call request.

And S120, the local NEF inquires and acquires the context information of the accessible local terminal according to the inquiry request, and extracts the permanent identifier from the context information.

When the local NEF receives the query request, the context information of the accessible local terminal, that is, the context information of the accessible local UE, can be obtained according to the query request. In this application, the context information of the UE includes at least: a Permanent Identifier (UE SUPI) information of the terminal, which uniquely identifies the terminal. Optionally, the context information of the UE may further include: current service type, terminal connection state, terminal registration state, etc.

S130, the local NEF determines a target network element according to the calling request, and sends the permanent identifier and the service session QoS strategy to the target network element.

When the local NEF receives the invocation request, it can determine the information of the target network element according to the invocation request, and in this application, the target network element is a network element that can process the service session QoS policy included in the invocation request. Optionally, the local NEF may determine the type of the target network element according to specific content of the service session QoS policy in the invocation request.

In a possible implementation manner, if the service session QoS Policy included in the invocation request is a Policy related to PCC (Policy and Charging Control) rules, the local NEF needs to find a local PCF as a target network element; if the service session QoS policy included in the invocation request is a policy related to the user subscription data, the local NEF needs to find a local UDM as a target network element.

After the local NEF determines the target network element, the permanent identifier determined by the query request and the service session QoS policy determined by the invocation request need to be sent to the target network element, so that the target network element can update the service session QoS policy.

In summary, in the service session management method provided by the present application, by deploying the NEF locally, after the local NEF receives the query request and the call request sent from the private network management system, the address of the industrial controller can be obtained from the query request, and then the context information of the local UE is obtained according to the query request and the SUPI of the UE is extracted; meanwhile, the local NEF can acquire a service session quality of service (QoS) strategy from the control instruction, and determines a target network element according to the calling request so as to send the UE SUPI and the service session QoS strategy to the target network element, so that an enterprise end can manage and control the service session QoS strategy for the local terminal without constructing a complex system, the complexity and the cost of the strategy management and control cost of the enterprise end are reduced, meanwhile, the problem that a key core network element of a public network in a traditional architecture needs to be directly opened to a third-party system is avoided, the possibility of attacking the public network is reduced, and the safety of the public network is guaranteed.

To elaborate the query request and the call request received by the local NEF from the private network management system, optionally, in the above S110, the receiving, by the local NEF, the query request and the control instruction sent by the private network management system includes: and the local NEF receives the query request sent by the private network management system and the call request which can be recognized by the local NEF and is generated by the private network management system based on the control instruction conversion.

Optionally, the control instructions include: a service session QoS policy and a service identifier; the address of the industrial controller is determined by the private network management system according to the service identifier, and the service session QoS strategy is determined by the enterprise fusion operation management and control system according to the service identifier obtained by the internal database.

Optionally, in order to implement relevant service session control on the local UE, the enterprise convergence operation management system may first read a service identifier corresponding to the target service from an internal database. Optionally, the service identifier includes an IP address of an industrial controller or an IP address of an industrial server, each industrial controller and each industrial server may be used as a unique service identifier, and a plurality of service identifiers are pre-stored in the enterprise convergence management system. When the enterprise user inputs a target task to be controlled, the enterprise fusion management system may read a service identifier corresponding to the target service from the internal database.

In a possible implementation manner, the enterprise convergence management system reads the IP address of the industrial controller or the IP address of the industrial server from the business adjustment instruction as the business identifier based on the business adjustment instruction for the target business input by the enterprise user. The service adjusting instruction comprises an IP address of an industrial controller or an IP address of an industrial server corresponding to the target service.

And after the enterprise convergence management system obtains the service identifier, the business session QoS strategy corresponding to the service identifier can be obtained. Then, the enterprise convergence management system packages the service identification and the service session QoS strategy into a control command and sends the control command to the private network management system.

Optionally, in this application, in order to enable the local NEF to recognize the service session QoS policy included in the sent control instruction, after the private network management system receives the control instruction from the enterprise converged job management and control system, the control instruction needs to be first converted into a call request that can be processed by the local NEF, and then the call request is initiated to the local NEF. The call request may be an API call request.

In this embodiment, the local NEF receives the recognizable invocation request converted by the private network management system, so that the local NEF can read the service session QoS policy that the enterprise convergence management system wants to manage and control from the invocation request, thereby achieving the technical purpose of opening the service session QoS policy control capability from the local network to the enterprise convergence management system.

In order to explain in detail how the local NEF obtains the context information of the local terminal, on the basis of the service session management method provided in fig. 3, the present application also provides a possible implementation manner of service session management. Fig. 4 is a flowchart illustrating another service session management method according to an embodiment of the present application. As shown in fig. 4, in the above S120, the acquiring, by the local NEF, the context information of the accessible local terminal according to the query request includes:

s310, the local NEF sends a context query request to the local UDSF according to the query request.

Optionally, for the enterprise convergence operation management system, the service identifier included in the control instruction sent to the private network management system includes an IP address of the industrial controller or an IP address of the industrial server, and then, after the private network management system receives the control instruction, the type of the service identifier included in the control instruction needs to be determined first.

If the service identifier is the IP address of the industrial server, the private network management system needs to query the IP address of the industrial controller that can access the industrial server in the local database, and set the IP address of the industrial controller as an index for querying the local NEF, that is, send a query request with the IP address of the industrial controller to the local NEF, and request to acquire context information of the access local UE corresponding to the index.

If the service identifier is the IP address of the industrial controller, the private network management system directly sets the IP address of the industrial controller as an index for querying the local NEF, that is, sends a query request with the IP address of the industrial controller to the local NEF, and requests to acquire context information corresponding to the index and accessed to the local UE.

In the 5G network framework, any NF is allowed to store and retrieve its unstructured data into the UDSF, such as session IDs, state data, UE context information used by the AMFs and SMFs.

Optionally, after receiving the query request sent by the private network management system, the local NEF sends a context query request to the local UDSF according to an index included in the query request, that is, an IP address of the industrial controller, and requires to acquire context information corresponding to the access local UE.

And S320, the local NEF receives context information returned by the local UDSF according to the context query request.

For the local UDSF, when a context query request sent by the local NEF is received, querying is performed, and if the context information of the UE matching the index exists, that is, the context information of the corresponding access local UE exists, the context information of the corresponding local UE is returned to the local NEF, so that the local NEF receives the context information returned by the local UDSF according to the context query request.

In a possible implementation manner, after the local NEF sends the context query request to the local UDSF, if the local UDSF does not query the context information of the UE matching the index, that is, the context information of the UE accessing the local UE does not exist, an empty result is returned to the local NEF, which indicates that no corresponding UE accesses the local network currently.

In this embodiment, through the interaction between the local NEF and the local USDF, the local NEF obtains the context information of the access local UE matching the address of the industrial controller, so as to update the QoS policy of the related service session in the subsequent process.

To describe in detail the processing procedure after the local NEF receives the invocation request, optionally, on the basis of the service session management method provided in fig. 3, optionally, in the method, the method further includes: if the service session QoS strategy needs to be processed by the local PCF, the local NEF converts the service session QoS strategy into a PCC rule and sends a protocol data unit network element PDU session strategy updating request to the local PCF, wherein the local PCF notifies the local SMF and triggers PDU session updating after receiving the PDU session strategy updating request.

After receiving the invocation request, the local NEF may determine information of a target network element according to the invocation request, where in this application, the target network element is a network element capable of processing a service session QoS policy included in the invocation request. Optionally, the local NEF may determine the type of the target network element according to the specific content of the service session QoS policy in the invocation request.

In a possible implementation manner, if the service session QoS policy included in the invocation request is a policy related to PCC rules, the local NEF needs to find a local PCF as a target network element. The local PCF provides the rules of the network behavior management behaviors, can complete the issuing of the strategies according to the QoS strategy of the service session, and provides flexible dynamic configuration.

And when the local PCF is determined as the target network element, the local NEF converts the service session QoS strategy into PCC rules, and the PCC rules can carry out dynamic strategy management and charging control according to the service characteristics and the user type. If the service session QoS strategy is converted into PCC rules, the local NEF sends the PCC rules obtained after conversion together with the UE SUPI to the local PCF, and sends a protocol data unit network element PDU session strategy updating request to the local PCF.

For the local PCF, after receiving a PDU session strategy updating request sent by the local NEF, the local PCF initiates a PDU session strategy modification process to inform the local SMF to trigger PDU session modification. The local SMF is responsible for the establishment, modification and release of user sessions.

And when the local SMF triggers the PDU session modification, the PDU session modification returns an update result to the local PCF, and the local PCF replies to the local NEF, so that the local NEF can return the result to the private network management system, and the private network management system further returns the result to the enterprise convergence operation management and control system.

In this embodiment, the service session QoS policy is converted into PCC rules, so that the local PCF may initiate the PDU session update to the local SMF, thereby completing the service session update.

Optionally, the method further includes:

if the service session QoS strategy needs to be processed by the local UDM, the local NEF converts the service session QoS strategy into user subscription data and sends a user subscription data updating request to the local UDM, wherein after receiving the user subscription data updating request, the local UDM initiates a query through the public network UDM to request for changing the legality of the user subscription data.

After receiving the invocation request, the local NEF may determine information of a target network element according to the invocation request, where in this application, the target network element is a network element capable of processing a service session QoS policy included in the invocation request. Optionally, the local NEF may determine the type of the target network element according to specific content of the service session QoS policy in the invocation request.

In a possible implementation manner, if the service session QoS policy included in the invocation request is a policy related to user subscription data, the local NEF needs to find a local UDM as a target network element. The local UDM may send network configuration parameters, such as subscriber subscription data, to other network elements, such as a local SMF, to enable configuration of the relevant parameters to be effected.

When the local UDM is determined as the target network element, the local NEF converts the service session QoS policy into user subscription data, and optionally, the user subscription data may include a subscription identity, a security credential, subscription data related to access and mobility, subscription data related to a session, and the like. And if the service session QoS strategy is converted into user subscription data, the local NEF sends the converted user subscription data together with the UE SUPI to the local UDM, and sends a user subscription data updating request to the local UDM.

For the local UDM, after receiving a user subscription data update request sent by the local NEF, the local UDM extracts the user subscription data from the local NEF, and issues a query to the public network UDM through the public network NEF or directly to request for changing the validity of the user subscription data.

If the public network UDM allows the user subscription data to be changed, the validity of the change is confirmed to the local UDM. And if the user subscription information is not changed, the user subscription information is refused to be changed.

And after the local UDM judges the result according to the validity of the received UDM from the public network, if the result shows that the user subscription data is allowed to be changed, the local UDM sends the user session subscription data and informs the local SMF to modify the PDU session through service operation, such as sending a subscription data Notification (Nudm-SDM-Notification). The local SMF is responsible for the establishment, modification and release of user sessions.

And when the PDU session modification is triggered by the local SMF, an updating result is returned to the local UDM, and then the local UDM replies to the local NEF, so that the local NEF can return the result to the private network management system, and the private network management system further returns the result to the enterprise convergence operation management and control system.

In this embodiment, the service session QoS policy is converted into the user subscription data, so that the local UDM can verify the validity of changing the user subscription data to the public network UDM, and initiate the update of the PDU session to the local SMF under the permission, thereby completing the update of the service session.

Optionally, on the basis of the foregoing embodiment, the foregoing method further includes: and when detecting the change of the context information, the local SMF sends the updated context information to the local UDSF.

Since the context information of the UE is stored in the local UDSF, when the local SMF performs PDU session management, the updated context information is sent to the local UDSF as long as it is detected that the current UE context information is changed.

Optionally, in the local UDSF, the context information is recorded in a manner, for example, as follows: { ID: SUPI, ext: IP, int: IP, cnxt: xxxx }, where ID represents identification information SUPI of the UE, ext represents an IP address of an industrial controller to which the UE is connected, int represents an IP address of the UE, and cnxt represents other context information of the UE, such as a PDU session ID.

In a possible implementation manner, for the local UPF, as long as a GTP (General Packet Radio Service Tunnel Protocol) Packet from the local UE is received, a source IP address (IP address of the UE) and a source IP address (IP address of the industrial controller) of an IP Packet encapsulated in the GTP Packet are extracted from the GTP Packet, so as to update the ext and int fields matched in the record to the local UDSF.

In this embodiment, the context information of the local UDSF is updated in real time by the local SMF, so that the real-time performance when the local NEF queries the context information of the UE according to the query request is ensured.

Optionally, the present application further provides a service session management method, which is applied to a private network management system, and fig. 5 is a schematic flow diagram of another service session management method provided in the embodiment of the present application. As shown in fig. 5, the method includes:

and S710, the private network management system receives the control instruction sent by the enterprise fusion operation management and control system, and generates a query request and a call request according to the control instruction.

In this embodiment, after the enterprise convergence operation management and control system accesses the network, a control instruction may be sent to the private network management system.

The enterprise convergence operation management and control system reads a specific service identifier (for example, an IP address of a certain industrial server or an IP address of a certain industrial controller) from an internal database; a service session QoS policy may also be generated corresponding to a particular service identification. And the enterprise convergence operation management and control system packages the service identification and the corresponding service session QoS strategy into a control command and sends the control command to the private network management system. Optionally, in an actual usage scenario, an enterprise user may input a service adjustment instruction in the enterprise converged operation management and control system according to a target service that needs to be adjusted, where the service adjustment instruction includes an IP address of an industrial controller corresponding to the target service, so that the enterprise converged operation management and control system generates a control instruction based on the IP address of the industrial controller in the service adjustment instruction to send the control instruction to the private network management system.

Optionally, the virtual industrial fieldbus includes a plurality of UEs, the plurality of UEs and the local SMF have a plurality of established PDU sessions, and an IP address of each industrial controller corresponds to a service subscribed by the local UE one to one. When the enterprise convergence operation management and control system needs to control and adjust the related service session of the local UE, the encapsulated control instruction includes the IP address information of the industrial controller and the QoS policy of the service session that needs to be managed and controlled. A traffic session QoS policy refers to a series of QoS parameters for a data flow between a core network, an access network, and a UE. Optionally, the traffic session QoS policy may include, but is not limited to: average rate, priority level, average window, maximum data burst size, minimum delay and delay jitter, etc.

After the private network management system receives the control instruction sent by the enterprise fusion operation management and control system, a query request and a call request need to be generated according to the information of the control instruction.

S720, the private network management system sends a query request and a call request to the local NEF.

The query request includes: the industrial controller address, the call request includes: a service session QoS policy; and the local NEF acquires the context information of the accessible local terminal according to the query request, extracts the permanent identifier from the context information, determines a target network element according to the call request and sends the permanent identifier and the service session QoS strategy to the target network element.

After the private network management system generates a query request and a call request for the local NEF according to the control instruction sent by the enterprise fusion operation management and control system, the query request and the call request can be sent to the local NEF. Wherein, the query request includes: the industrial controller address, i.e. the IP address of the industrial controller, the local NEF may obtain the relevant information of the UE according to the query request. The call request includes: and a service session QoS strategy, wherein the local NEF can determine a target network element for initiating the service session modification at this time and a specific service session QoS strategy according to the call request.

When the local NEF receives the query request, the context information of the accessible local UE can be obtained by query according to the query request, that is, the context information of the accessible local UE is obtained. In this application, the context information of the UE includes at least: permanent identifier of terminal (UE SUPI) information, the UE SUPI uniquely identifying the terminal. Optionally, the context information of the UE may further include: current service type, terminal connection state, terminal registration state, etc.

In a possible implementation manner, if the service session QoS policy included in the invocation request is a policy related to PCC rules, the local NEF needs to find a local PCF as a target network element; if the service session QoS policy included in the invocation request is a policy related to the user subscription data, the local NEF needs to find a local UDM as a target network element.

In this embodiment, the enterprise terminal can manage and control the QoS policy of the service session to the local terminal without building a complex system, so that complexity and cost of the cost for policy management and control by the enterprise terminal are reduced, and meanwhile, the problem that a key core network element of the public network in a traditional architecture must be directly opened to a third-party system is avoided, the possibility that the public network is attacked is reduced, and the security of the public network is ensured.

Fig. 6 is a schematic diagram of a service session management apparatus provided in an embodiment of the present application, which may be applied to a local NEF, and the basic principle and the generated technical effect of the apparatus are the same as those of the corresponding method embodiment described above, and for brief description, the corresponding contents in the method embodiment may be referred to for parts not mentioned in this embodiment. As shown in fig. 6, the service session management apparatus 100 may include:

a receiving module 1000, configured to receive, by the local NEF, a query request and a call request sent by the private network management system, where the query request includes: the address of the industrial controller is determined according to a control instruction sent to the private network management system by the enterprise convergence operation management and control system; the call request includes: traffic session QoS policies.

The obtaining module 2000 is configured to obtain, according to the query request, context information of the accessible local terminal by the local NEF, and extract the permanent identifier from the context information.

The first sending module 3000 is configured to determine, by the local NEF, a target network element according to the invocation request, and send the permanent identifier and the service session QoS policy to the target network element.

Optionally, the receiving module 1000 is further specifically configured to receive, by the local NEF, an inquiry request sent by the private network management system, and a call request that is generated by the private network management system based on the control instruction conversion and is recognizable by the local NEF.

Optionally, the first sending module 3000 is further specifically configured to send, by the local NEF, the context query request to the local UDSF according to the query request.

Optionally, the receiving module 1000 is further specifically configured to receive, by the local NEF, context information returned by the local UDSF according to the context query request.

Optionally, the first sending module 3000 is further specifically configured to, if the service session QoS policy needs to be processed by the local PCF, convert the service session QoS policy into a PCC rule by the local NEF, and send a PDU session policy update request to the local PCF, where the local PCF notifies the local SMF and triggers PDU session update after receiving the PDU session policy update request.

Optionally, the first sending module 3000 is further specifically configured to, if the service session QoS policy needs to be processed by the local UDM, convert the service session QoS policy into user subscription data by the local NEF, and send a user subscription data update request to the local UDM, where after receiving the user subscription data update request, the local UDM initiates an inquiry through the public network UDM to request to change the validity of the user subscription data.

Optionally, the first sending module 3000 is specifically further configured to send, by the local SMF, the updated context information to the local UDSF when detecting that the context information changes.

Fig. 7 is a schematic diagram of another service session management apparatus provided in this embodiment of the present application, which may be applied to a private network management system, and the basic principle and the resulting technical effect of the apparatus are the same as those of the foregoing corresponding method embodiment, and for brief description, reference may be made to corresponding contents in the method embodiment for parts that are not mentioned in this embodiment. As shown in fig. 7, the service session management apparatus 200 may include:

and the processing module 4000 is configured to receive a control instruction sent by the enterprise fusion operation management and control system by the private network management system, and generate a query request and a call request according to the control instruction.

A second sending module 5000, configured to send, by the private network management system, a query request and a call request to the local NEF, where the query request includes: an industrial controller address, the call request comprising: and the service session QoS strategy is used for enabling the local NEF to acquire the context information of the accessible local terminal according to the query request, extracting the permanent identifier from the context information, enabling the local NEF to determine the target network element according to the call request, and sending the permanent identifier and the service session QoS strategy to the target network element.

The above-mentioned apparatus is used for executing the method provided by the foregoing embodiment, and the implementation principle and technical effect are similar, which are not described herein again.

These above modules may be one or more integrated circuits configured to implement the above methods, such as: one or more Application Specific Integrated Circuits (ASICs), or one or more microprocessors, or one or more Field Programmable Gate Arrays (FPGAs), etc. For another example, when one of the above modules is implemented in the form of a Processing element scheduler code, the Processing element may be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. For another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).

Fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present application, and as shown in fig. 8, the electronic device may include: a processor 21, a storage medium 22 and a bus 23, wherein the storage medium 22 stores machine-readable instructions executable by the processor 21, and when the electronic device is operated, the processor 21 communicates with the storage medium 22 through the bus 230, and the processor 21 executes the machine-readable instructions to perform the steps of the above-mentioned method embodiments. The specific implementation and technical effects are similar, and are not described herein again.

Optionally, the present application further provides a storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the computer program performs the steps of the above method embodiments. The specific implementation and technical effects are similar, and are not described herein again.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit may be implemented in the form of hardware, or in the form of hardware plus a software functional unit.

The integrated unit implemented in the form of a software functional unit may be stored in a computer-readable storage medium. The software functional unit is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device) or a processor (processor) to execute some steps of the methods according to 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 (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising one of 8230; \8230;" 8230; "does not exclude the presence of additional like elements in a process, method, article, or apparatus that comprises the element.

The above description is only for the specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are included in the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A service session management method, applied to a local network open function network element NEF, the method includes:

the local NEF receives a query request and a call request sent by a private network management system, wherein the query request comprises: the address of the industrial controller is determined according to a control instruction sent to the private network management system by the enterprise fusion operation management and control system; the call request comprises: a service session quality of service (QoS) strategy;

the local NEF determines a target network element according to the call request and sends the permanent identifier and the service session QoS strategy to the target network element, wherein the target network element is a network element capable of processing the service session QoS strategy contained in the call request;

the method further comprises the following steps: and if the service session QoS strategy needs to be processed by a local unified data management network element UDM, the local NEF converts the service session QoS strategy into user subscription data and sends a user subscription data updating request to the local UDM, wherein after receiving the user subscription data updating request, the local UDM initiates inquiry through the unified data management network element UDM in the public network to request the legality of the user subscription data updating.

2. The method of claim 1, wherein the control instructions comprise: the address of the industrial controller is determined by the private network management system according to the service identifier, and the service session QoS strategy is determined by the enterprise convergence operation management and control system according to the service identifier obtained by an internal database;

3. The method according to claim 1 or 2, wherein the local NEF queries and obtains context information of the accessible local terminal according to the query request, and comprises:

4. The method of claim 1, further comprising:

5. The method according to claim 4, wherein said local SMF sends updated context information to a local unstructured data storage function network element UDSF when said context information change is detected.

6. A service session management method is applied to a private network management system, and the method comprises the following steps:

the private network management system sends the query request and the call request to a local network open function Network Element (NEF), wherein the query request comprises: an industrial controller address, the call request comprising: a QoS policy of service session quality of service, so that the local NEF queries and acquires context information of an accessible local terminal according to the query request, and extracts a permanent identifier from the context information, so that the local NEF determines a target network element according to the call request, and sends the permanent identifier and the QoS policy of service session to the target network element, wherein the target network element is a network element capable of processing the QoS policy of service session contained in the call request;

and if the service session QoS strategy needs to be processed by a local unified data management network element UDM, the private network management system sends the calling request to a local network open function network element NEF, so that the local NEF converts the service session QoS strategy into user subscription data and sends a user subscription data updating request to the local UDM, wherein after receiving the user subscription data updating request, the local UDM initiates inquiry through the unified data management network element UDM in a public network to request the legality of user subscription data updating.

7. A service session management apparatus, applied to a local network open function network element NEF, the apparatus comprising:

a first sending module, configured to determine, by the local NEF, a target network element according to the invocation request, and send the permanent identifier and the service session QoS policy to the target network element, where the target network element is a network element that can process the service session QoS policy included in the invocation request;

the first sending module is further configured to, if the service session QoS policy needs to be processed by a local unified data management network element UDM, convert the service session QoS policy into user subscription data by the local NEF, and send a user subscription data update request to the local UDM, where after receiving the user subscription data update request, the local UDM initiates a query through the unified data management network element UDM in a public network to request validity of user subscription data update.

8. A service session management apparatus, applied to a private network management system, the apparatus comprising:

a second sending module, configured to send, by the private network management system, the query request and the invocation request to a local network open function network element NEF, where the query request includes: an industrial controller address, the call request comprising: a service session quality of service (QoS) policy, so that the local NEF queries and acquires context information of an accessible local terminal according to the query request, extracts a permanent identifier from the context information, so that the local NEF determines a target network element according to the call request, and sends the permanent identifier and the service session QoS policy to the target network element, wherein the target network element is a network element capable of processing the service session QoS policy contained in the call request;

the second sending module is further configured to, if the service session QoS policy needs to be processed by a local unified data management network element UDM, send the invocation request to the local network open function network element NEF by the private network management system, so that the local NEF converts the service session QoS policy into user subscription data and sends a user subscription data update request to the local UDM, where after receiving the user subscription data update request, the local UDM initiates a query through the unified data management network element UDM in a public network to request validity of the user subscription data update.

9. A computer-readable storage medium, characterized in that the storage medium has stored thereon a computer program which, when being executed by a processor, performs the steps of the service session management method according to any one of claims 1 to 5 or 6.