CN111935738B - Method and system for multi-operator core network docking MEC - Google Patents

Abstract

The embodiment of the invention discloses a method and a system for docking an MEC (Multi-operator core network), which relate to the technical field of communication and can realize that an MEC system docks 5G core networks of different operators. The invention includes: the AF of the MEC inquires and obtains a core network entrance of an operator to which the request message points according to the locally stored association information or configuration information; the AF of the MEC sends the request message to the NEF, and the NEF saves the received request message in the UDR; PCF receives the notice of data change from the UDR and updates PCC rule of SMF; and after receiving the updated PCC rules from the PCF, the SMF reconfigures the user plane of the PDU conversation. The invention is suitable for the 5G core network butted by the MEC system.

Description

Method and system for multi-operator core network docking MEC

Technical Field

The invention relates to the technical field of communication, in particular to a method and a system for multi-operator core network (MEC) docking.

Background

With the mutation of international situation, the construction of 5G (5th Generation mobile networks or 5th Generation wireless systems, 5th-Generation, fifth Generation mobile communication technology) is further accelerated in China, and various secondary development and application schemes based on the 5G technology are accelerated. The 3GPP (3rd Generation Partnership Project, third Generation Partnership Project) defines three major scenarios for 5G applications: eMBBs (Enhanced Mobile Broadband ), URLLC (Ultra-reliable and Low Latency Communications), and mMTC (Massive Machine Type Communications). The eMBB scene provides large-flow mobile broadband services, such as high-speed downloading, high-definition video and the like, which causes great pressure on a wireless backhaul network, and the services need to be sunk to the edge of the network as much as possible so as to realize local shunting of the services; however, the URLLC scenario provides ultra-high reliable ultra-low delay communication, such as unmanned driving and industrial control, which also requires that services are sunk to the edge of the network, so that network delay caused by network transmission is reduced.

In the face of the feature that 5G applications need to be sunk to the Edge of the network, MEC (Multi-Access Edge Computing) has come and has been incorporated as a key technology into the 3GPP5G standard. The 5G core network is separated from the UP (User Plane) by a CP (Control Plane), the UPF (User Plane Function, User Plane network element) can be flexibly deployed to the network edge, and the Control Plane functions such as PCF (Policy Control Function) and SMF (Session Management Function) can be deployed in a centralized manner. Whereas MEC enables operator and third party services to be hosted near the access point of a UE (User Equipment), thereby enabling efficient service delivery by reducing end-to-end delay and load on the transport network. The 5G core network selects a UPF close to the UE and performs flow control from the UPF to the local data network over the N6 interface.

However, in the current 5G + MEC architecture, only the MEC system can be supported to interface with the 5G core network of a single operator, that is, the MEC system and the 5G core network need to belong to the same operator, but the MEC system cannot interface with the 5G core networks of different operators, which also results in that the cost of 5G application is difficult to further reduce, and the construction cost of the operators is high.

Disclosure of Invention

The embodiment of the invention provides a method and a system for docking an MEC (Multi-operator core network), which can realize that an MEC system docks 5G core networks of different operators.

In order to achieve the above purpose, the embodiment of the invention adopts the following technical scheme:

in a first aspect, an embodiment of the present application provides a method for multi-operator core network docking an MEC, including:

the AF of the MEC inquires and obtains a core network entrance of an operator to which the request message points according to the locally stored association information or configuration information; the AF of the MEC sends the request message to the NEF, and the NEF stores the received request message in the UDR; PCF receives the notice of data change from the UDR and updates PCC rule of SMF; and after receiving the updated PCC rules from the PCF, the SMF reconfigures the user plane of the PDU conversation.

In a second aspect, an embodiment of the present application provides a system for multi-operator core network docking MEC, including:

the MEC is used for inquiring and obtaining a core network entrance of an operator to which the request message points through the AF according to the locally stored association information or configuration information; then, sending the request message to NEF; the NEF is used for saving the received request message in the UDR; PCF, for receiving the data change notice from the UDR and updating PCC rule of SMF; SMF, for reconfiguring PDU conversation user surface after receiving updated PCC rule from PCF.

In a first possible implementation manner of the second aspect, the method further includes: a first processing unit, a second processing unit, and a transmit pre-processing unit disposed on the MEC:

the first processing unit is configured to, in a process of creating the request message, trigger the AF to invoke an Nnef _ trafficinfiffice _ Create service operation, where the request message includes a transaction identifier of the AF.

And the second processing unit is used for updating or removing the existing request message, triggering the AF to call an Nnef _ Traficinfluence _ Update service operation or an Nnef _ Traficinfluence _ Delete service operation, and simultaneously providing the transaction identifier of the AF corresponding to the existing request message.

And the transmission preprocessing unit is used for triggering the AF to reach the PCF selected for the current PDU session according to the configuration or calling the Nbsf _ management _ Discovery service operation.

In a second possible implementation manner of the second aspect, a mapping unit and a data saving unit are deployed on the NEF, where:

a mapping unit for mapping information provided by the AF of the MEC to information required by 5 GC.

A data management unit to: when the AF of the MEC calls an Nnef _ Trafficinfluence _ Create service operation or calls an Nnef _ Trafficinfluence _ Update service operation, the NEF saves the request message in the UDR;

and when the AF of the MEC calls an Nnef _ Trafficinfluence _ delete service operation, the NEF deletes the AF requirement of the MEC from the UDR;

and after the NEF saves the request message in the UDR or deletes the AF requirement of the MEC from the UDR, the NEF sends response information to the AF of the MEC.

In a third possible implementation manner of the second aspect, the PCF is deployed with a detection unit and a rule management unit, where:

a detecting unit, configured to receive, by the PCF, a notification Nudr _ DM _ Notify notification of data change from the UDR, where the PCF subscribes to an AF request modification of the MEC.

A rule management unit, configured to determine, by the PCF, a PDU session currently affected by an AF request of the MEC, and for each determined PDU session, the PCF invokes an Npcf _ SMPolicyControl _ UpdateNotify service operation to update a PCC rule of the SMF; wherein, when the request message contains a request for a notification report of a user plane path change, the information added by the PCF in the PCC rule includes: a notification target address pointing to the AF of the NEF or the MEC, and a notification association identifier containing an AF transaction internal identifier.

In a fourth possible implementation manner of the second aspect, a rule forwarding unit is deployed on the SMF, and is configured to issue, to the UPF, a message carrying a PCC rule and operator network identification information through an N4 interface.

In a fifth possible implementation manner of the second aspect, a rule loading unit is deployed on the UPF, and is configured to, after receiving the message sent by the SMF, associate and manage the request message and the resource occupied by the operator on the MEC and the UPF according to the operator network identifier information, and perform corresponding resource control.

In a sixth possible implementation manner of the second aspect, a feedback unit is deployed on the MEC host level, and is used for feeding back, by the MEC host level to the MEC system level, a resource usage situation of the operator at the MEC host level.

In a seventh possible implementation manner of the second aspect, a resource maintenance unit is deployed on an MEC system level, and is configured to maintain network identification information and a resource request message table of different operators at the MEC system level.

According to the method and the system for the multi-operator core network to interface the MEC, provided by the embodiment of the invention, the MEC system level is provided with a resource management module which is responsible for managing the resource use condition of the UPF for interfacing different operator 5G core networks, specifically, the UPF is at the MEC host level, the MEC host level reports the use condition of different local UPF operators to the MEC system level, and the MEC system level carries out statistics and management according to the contract agreement with different operators. The resource management module at the MEC system level can also issue corresponding policy rules to the UPF at the MEC host level, and the resource execution module on the UPF executes the relevant policies. The resource management module manages and maintains different operator network identification information and corresponding resource request message tables. The SMF issues a message carrying the PCC rule to the mecuff through an N4 interface, and specifically, the message also carries operator network identification information, for example, a PLMN-ID. After receiving the SMF message, the MEC UPF associates and manages the request message and the resource occupied by the operator on the MEC UPF according to the operator network identification information, and executes corresponding resource control. The MEC host level feeds back the resource use condition of the operator at the MEC host level to the MEC system level, and the MEC system level maintains network identification information of different operators and a resource request message table corresponding to the network identification information. Therefore, the MEC system is connected with the 5G core networks of different operators.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a schematic diagram of the current 5G and MEC basic architecture provided by the embodiment of the present invention;

FIG. 2 is a schematic flow chart of a method provided by an embodiment of the present invention;

fig. 3 is a MEC and multi-operator 5G core network architecture according to an embodiment of the present invention;

fig. 4 is a flowchart of a route for processing an MEC AF request to affect a session that is not identified by a UE address according to an embodiment of the present invention.

Detailed Description

In order to make the technical solutions of the present invention better understood, the present invention will be described in further detail with reference to the accompanying drawings and specific embodiments. Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the accompanying drawings are illustrative only for the purpose of explaining the present invention, and are not to be construed as limiting the present invention. As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. The subject matter of the present invention does not exclude the presence of other elements or steps than those expressly stated. Terms such as "first" and "second" do not denote an order of elements in time, space, size, etc., but rather are used to distinguish one element from another. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Further, "connected" or "coupled" as used herein may include wirelessly connected or coupled. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items. It will be understood by those skilled in the art that, unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the prior art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

Some english abbreviations appearing in the present examples respectively represent:

MEC (Multi-Access Edge Computing),

UPF (User Plane Function),

PCF (Policy Control Function),

PCC (Policy Control and Charging),

SMF (Session Management Function),

NEF (Network expose Function),

5G (5th Generation mobile networks or 5th Generation wireless systems, 5th-Generation, fifth Generation mobile communication technology),

3GPP (3rd Generation Partnership Project, third Generation Partnership Project),

eMBB (Enhanced Mobile Broadband),

URLLC (Ultra-reliable and Low Latency Communications),

mMTC (Massive Machine Type Communication),

A CP (control plane),

UP (User plane),

UE (User Equipment),

AF (Application Function),

DN (Data Network),

NFs (Network Functions).

In practical applications, the ETSI GS MEC specification defines the MEC reference architecture, and the ETSIMEC system is composed of a MEC host and MEC management functions. The MEC host contains the MEC platform, virtualization infrastructure, and the various MEC applications and services running thereon. The MEC management function comprises an MEC system level management function and a host level management function, wherein the MEC system level management function comprises a user application lifecycle management agent, an operation support system and an MEC orchestrator, and the MEC host level management function comprises an MEC platform manager and a virtualization infrastructure manager. MEC allows operator and third party services to be hosted near the access point of the UE, thereby enabling efficient service delivery by reducing end-to-end delay and load on the transport network. The 5G core network selects a UPF close to the UE and performs flow control from the UPF to the local data network over the N6 interface. This may be based on subscription data of the UE, UE location, information from an Application Function (AF), policy, or other relevant traffic rules.

In this kind of application scenario, the MEC system is a role of AF + DN with respect to the 5G core Network, as shown in fig. 1, the MEC orchestrator is a MEC system level functional entity, which acts as an AF and can interact with NEF (Network Exposure Function), or in some cases directly interact with target 5G NFs, for example, the user plane policy is affected by NEF- > PCF- > SMF in a role of untrusted AF, or the user plane policy is affected by directly connecting to PCF- > SMF in a role of trusted AF. At the MEC host level, the MEC platform may also interact with 5G NFs as AFs. The MEC system, as a special form of AF, can interact with the NEF/PCF more, invoking other 5GC (5G core network) open capabilities, such as message subscription, QoS, etc.

The solution of this embodiment is a secondary development based on the architecture shown in fig. 1, and finally designs an MEC and multi-operator 5G core network architecture shown in fig. 3. The present embodiment aims to provide a multi-operator 5GMEC communication method to support an MEC system to interface with 5G core networks of different operators, deeply merge an access network and internet services, and provide services at a network edge closer to a user, so as to improve user experience. Specifically, in the scheme of fig. 3, the MEC system level has a resource management module, and is responsible for managing resource usage of UPFs interfacing with 5G core networks of different operators, specifically, the UPFs are at the MEC host level, the MEC host level reports usage of different local UPFs for the MEC system level, and the MEC system level performs statistics and management according to contract agreements with different local UPFs. The resource management module at the MEC system level can also issue corresponding policy rules to the UPF at the MEC host level, and the resource execution module on the UPF executes the relevant policies. The resource management module manages and maintains different operator network identification information and corresponding resource request message tables.

An embodiment of the present invention provides a method for docking an MEC with a multi-operator core network, as shown in fig. 2, including:

s1, the AF of the MEC queries the core network entry of the operator to which the request message is directed according to the locally stored association information or configuration information.

Wherein, according to the locally stored association information or configuration information, the core network entry is queried, which may be according to the general understanding in the current 5G scheme, that is: assuming 5G core networks a and B, if the MEC AF is based on local configuration information (e.g. the configured entry address of 5GCA is IPA), it sends according to the address of the configuration information; if MECAF needs to send a request for a user of the 5G core network A, the user is known to belong to the 5G core network A according to the association information, and then the request message is sent to the past, and the association information records the 5G core network to which the user belongs.

S2, the AF of the MEC sending the request message to the NEF, and the NEF saving the received request message in the UDR.

S3, PCF receives the notice of data change from said UDR and updates the PCC rule of SMF.

The notification of the data change can be according to the common understanding in the current 5G scheme, that is: firstly, storing AF request message in UDR, if PCF subscribes AF request modification, then UDR sends notification to PCF, said notification is used to inform PCF: the AF request message saved in the UDR changes. The PCC rules described in this embodiment generally include a service data flow template, QoS parameters, and the like, where the UPF implements control of service traffic of a specific UE by executing the PCC rules, and a core network of an operator may formulate the PCC rules.

S4, after receiving the updated PCC rule from the PCF, the SMF reconfigures the user plane of the PDU session.

In an actual landing implementation, the UPF and the MEC belong to a large system and are usually deployed by an operator, where the implementation is different from an operator that deploys a 5G core network. In the process of reconfiguring the user plane of the PDU session, "reconfiguration" is parameters of the user plane, such as: after reconfiguration, the updated PCC rules turn down the QoS parameters of the user, such as priority, bandwidth, etc.

Further, the method also comprises the following steps: in the process of creating the request message, the AF of the MEC invokes an Nnef _ TrafficInfluence _ Create service operation, and the request message includes a transaction identifier of the AF. The called string of "Nnef _ trafficinfiluence _ Create" is a message name, and is specifically implemented as a service operation (service operation). And updating or removing the existing request message, calling an Nnef _ TrapaCinfluence _ Update service operation or an Nnef _ TrapaCinfluence _ Delete service operation by the AF of the MEC, and simultaneously providing a transaction identifier of the AF corresponding to the existing request message. For example: fig. 4 shows a routing procedure for processing the MEC AF request to affect the session that is not identified by the UE address in this embodiment, where: step 1. to Create a new request, the AF of the MEC invokes the Nnef _ trafficinfiluence _ Create service operation. The request includes an AF transaction identification. The AF of the MEC also indicates where it wishes to receive the corresponding notification (AF notification report information) if it subscribes to event notifications related to said PDU session. To Update or remove an existing request, the AF of the MEC invokes an nftrafficinfluence Update or nftrafficinfluence Delete service operation, while providing a corresponding AF transaction identity.

Further, the sending, by the AF of the MEC, the request message to the NEF includes: the AF of the MEC operates according to configuration or calls Nbsf _ management _ Discovery service to reach the PCF selected for the current PDU session, wherein "according to configuration" means that the MEC AF finds a corresponding PCF according to a pre-configured address, and if the MEC AF calls service, finds a corresponding PCF based on BSF (binding support function), and then sends the message. "reach" herein refers to sending a message to the PCF that the previous provisioning or invocation of a service was intended to find the PCF, thereby enabling the flow of information. The PDU session can be understood as: and (3) a channel for exchanging data between the UE and the network. The NEF maps the information provided by the AF of the MEC to the information required by the 5GC, where the "information provided by the AF of the MEC" specifically includes the parameters carried in the AF request message, and the "information provided by the AF is mapped to the information required by the 5 GC" may be understood as: the conversion of the parameters of one or more MEC systems to the parameters of another one or more 5GC systems is carried out, the names of the parameters before and after the conversion are different, and the information required by the 5GC is the converted parameters, namely the result of the parameter mapping. For example: shown in fig. 4, wherein: step 2.MEC AF sends request to NEF. Specifically, the AF sends the request message to the corresponding operator 5G core network according to the service requirement, and the AF of the MEC may find the corresponding operator 5G core network entry according to the local association information or configuration information. If the request is sent directly to the PCF by the AF of the MEC, the AF of the MEC reaches the PCF selected for the current PDU session according to the configuration or calling Nbsf _ management _ Discovery service operation. The NEF ensures necessary authorization control including flow control of AF requests to the MEC and maps information provided by the AF of the MEC to information required for 5 GC.

Specifically, the NEF stores the received request message in the UDR, which includes: when the AF of the MEC calls an Nnef _ TransFFICInfluency _ Create service operation or calls an Nnef _ TransFFICInfluency _ Update service operation, the NEF saves the request message in the UDR. When the AF of the MEC calls an nftrafficinfiluence-delete service operation, the NEF deletes the AF requirement of the MEC from the UDR, where the "requirement" refers to an already existing AF request message, and a parameter carried in the request message is used as the "requirement". And after the NEF saves the request message in the UDR or deletes the AF requirement of the MEC from the UDR, the NEF sends response information to the AF of the MEC. For example: shown in fig. 4, wherein: and 3, when the Nnef _ Trafficinfluence _ Create or the Update: the NEF saves the AF request message of the MEC in the UDR. When Nnef _ Trafficinfluence _ delete: the NEF deletes the AF requirements of the MEC from the UDR. The NEF sends a response to the AF of the MEC.

Further, the PCF receiving the notification of the data change from the UDR, comprising: the PCF receives a notification of a change in data from the UDR, Nudr _ DM _ Notification, wherein the PCF subscribes to AF request modification of the MEC, in particular, it understands that the PCF may subscribe to "AF request modification" from the UDR, i.e. if the AF request is modified, the UDR will send a message to the PCF. For example: shown in fig. 4, wherein: and 4, the PCF subscribed to the AF request modification of the MEC receives the notice Nudr _ DM _ Notification of the data change from the UDR.

The updating the PCC rule of the SMF comprises the following steps: the PCF determines the PDU sessions currently affected by the AF request of the MEC, and for each determined PDU session, the PCF invokes an Npcf _ SMPolicyControl _ UpdateNotify service operation to update the PCC rules of the SMF, where a PDU session affected by the AF request of the MEC may be understood as: since the AF request message carries parameters, these parameters are finally converted into PCC rules and executed on the UPF, thereby affecting the PDU session of the UE. When the request message contains a request for a notification report of a user plane path change, the information added by the PCF in the PCC rule includes: a notification target address pointing to the AF of the NEF or the MEC, and a notification association identifier including an AF transaction internal identifier, where it needs to be described that: "request for notification report of …" is an interpretation of the current 5G standard english script, showing: if the user plane path is changed, the PCF needs to send a notification report to the corresponding destination address object, and the above operation of sending the notification report needs to be indicated in the request message, otherwise, no subsequent notification report is sent, so it is called "request for notification report". For example: shown in fig. 4, wherein: and 5, the PCF judges whether the current PDU session is possibly influenced by the AF request of the MEC. For each affected PDU session, the PCF updates the PCC rules of the SMF by invoking an Npcf _ SMPolicyControl _ UpdateNotify service operation. If the AF request of the MEC contains a request for notification report of user plane path change, the PCF includes in the PCC rules the information needed for reporting the event, including the notification destination address of the AF pointing to the NEF or MEC, and the notification association identifier containing the AF transaction internal identifier, where "notification association identifier" is a parameter, which in turn contains "AF transaction internal identifier", belonging to the concept and definition in the 5G standard manuscript.

It should be noted that, in this embodiment, after receiving the updated PCC rule from the PCF, the SMF reconfigures the user plane of the PDU session, including:

and the SMF issues a message carrying a PCC rule and operator network identification information to the UPF through an N4 interface.

And after receiving the message sent by the SMF, the UPF performs associated management on the request message and the resources occupied by the operator on the MEC and the UPF according to the network identification information of the operator, and executes corresponding resource control. The UPF that receives the message sent by the SMF is referred to as MECUPF, that is, the UPF belongs to the MEC large system and is deployed by the same operator.

And the MEC host level feeds back the resource use condition of the operator at the MEC host level to the MEC system level.

And the MEC system level maintains network identification information and a resource request message table of different operators.

For example: shown in fig. 4, wherein: step 6, after receiving the PCC rule from the PCF, the SMF may take appropriate measures to reconfigure the user plane of the PDU session, and the SMF issues a message carrying the PCC rule to the UPF through the N4 interface, specifically, the message also carries operator network identification information, such as PLMN-ID. After receiving the SMF message, the MEC UPF associates and manages the request message and the resources occupied by the operator on the MEC UPF according to the operator network identification information, and executes corresponding resource control. The MEC host level feeds back the resource use condition of the operator at the MEC host level to the MEC system level, and the MEC system level maintains network identification information of different operators and a resource request message table corresponding to the network identification information. Such as actions performed by SMF:

1-add, replace or remove a UPF on the data path, such as UL-CL or a split point.

2-assign a new prefix (applicable to IPv6 multi-timing) to the UE.

3-update the new traffic steering rules to the UPF in the target DNAI.

4-Subscribe to AMF for notification of regions of interest through Namf _ EventExpo _ Subscribe service operation.

In this embodiment, a system for docking an MEC with a multi-operator core network is further provided, as shown in fig. 3, including:

and the MEC is used for inquiring and obtaining the core network entrance of the operator to which the request message points according to the locally stored association information or configuration information through the AF. Thereafter, the request message is sent to the NEF.

The NEF is used for storing the received request message in the UDR.

PCF, for receiving the data change notice from the UDR and updating PCC rule of SMF.

And the SMF is used for reconfiguring the user plane of the PDU session after receiving the updated PCC rules from the PCF.

The steps of a method or algorithm described in connection with the disclosure herein may be embodied in hardware or may be embodied in software instructions executed by a processor. The software instructions may be comprised of corresponding software modules that may be stored in Random Access Memory (RAM), flash memory, Read Only Memory (ROM), Erasable Programmable Read Only Memory (EPROM), Electrically Erasable Programmable Read Only Memory (EEPROM), registers, a hard disk, a removable hard disk, a compact disc read only memory (CD-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. Additionally, the ASIC may reside in a core network interface device. Of course, the processor and the storage medium may reside as discrete components in a core network interface device.

The embodiment further includes a first processing unit, a second processing unit, and a transmission preprocessing unit disposed on the MEC, where:

the first processing unit is used for triggering the AF to call the Nnef _ Trafficinfluence _ Create service operation in the process of creating the request message, wherein the request message comprises the transaction identifier of the AF;

a second processing unit, configured to Update or remove an existing request message, trigger an AF to invoke an Nnef _ trafficinfilflue _ Update service operation or an Nnef _ trafficinfilflue _ Delete service operation, and provide a transaction identifier of the AF corresponding to the existing request message;

a transmission preprocessing unit, configured to trigger an AF to operate according to configuration or call Nbsf _ management _ Discovery service, and reach a PCF selected for a current PDU session;

further, at the host level of the MEC (i.e. MEC host level), a feedback unit is deployed, and is used for the MEC host level to feed back the resource usage of the operator at the MEC host level to the MEC system level;

at a system level of the MEC (i.e. at the MEC system level), a resource maintenance unit is deployed for maintaining network identification information and resource request message tables of different operators at the MEC system level.

The NEF is provided with a mapping unit and a data storage unit, wherein:

a mapping unit for mapping information provided by the AF of the MEC to information required by 5 GC.

A data management unit to: when the AF of the MEC calls an Nnef _ Trafficinfluence _ Create service operation or calls an Nnef _ Trafficinfluence _ Update service operation, the NEF saves the request message in the UDR;

and when the AF of the MEC calls an Nnef _ Trafficinfluence _ delete service operation, the NEF deletes the AF requirement of the MEC from the UDR;

and after the NEF saves the request message in the UDR or deletes the AF requirement of the MEC from the UDR, the NEF sends response information to the AF of the MEC.

The PCF is provided with a detection unit and a rule management unit, wherein:

a detecting unit, configured to receive, by the PCF, a notice Nudr _ DM _ Notifynotification of a data change from the UDR, where the PCF subscribes to an AF request modification of the MEC;

a rule management unit, configured to determine a PDU session currently affected by an AF request of the MEC, and for each determined PDU session, the PCF invokes an Npcf _ SMPolicyControl _ UpdateNotify service operation to update a PCC rule of the SMF; wherein, when the request message contains a request for a notification report of a user plane path change, the information added by the PCF in the PCC rule includes: a notification target address pointing to the AF of the NEF or the MEC, and a notification association flag containing an AF transaction internal flag.

A rule forwarding unit is deployed on the SMF, and is used for the SMF to issue a message carrying PCC rules and operator network identification information to the UPF through an N4 interface.

And the UPF is provided with a rule loading unit and is used for associating and managing the request message and the resources occupied by the operator on the MEC and the UPF according to the operator network identification information after the UPF receives the message sent by the SMF, and executing corresponding resource control. Those skilled in the art will recognize that in one or more of the examples described above, the functions described herein may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

The above-mentioned embodiments, objects, technical solutions and advantages of the present application are further described in detail, it should be understood that the above-mentioned embodiments are only examples of the present application, and are not intended to limit the scope of the present application, and any modifications, equivalent substitutions, improvements and the like made on the basis of the technical solutions of the present application should be included in the scope of the present application.

Claims (8)

1. A method for multi-operator core network interfacing, MEC, comprising:

the AF of the MEC inquires and obtains a core network entrance of an operator to which the request message points according to the locally stored association information or configuration information; the method comprises the steps that an MEC host level feeds back the resource use condition of an operator at the MEC host level to the MEC system level, and the MEC system level maintains network identification information of different operators and a corresponding resource request message table;

the AF of the MEC sends the request message to the NEF, the NEF stores the received request message in the UDR, wherein parameters carried in the AF request message are mapped to information required by 5 GC;

PCF receives the notice of data change from the UDR and updates PCC rule of SMF;

after receiving the updated PCC rule from the PCF, the SMF reconfigures the user plane of the PDU session, including:

the SMF issues a message carrying a PCC rule and operator network identification information to the UPF through an N4 interface;

after receiving the message sent by the SMF, the UPF performs associated management on the request message and the resources occupied by the operator on the MEC and the UPF according to the operator network identification information, and executes corresponding resource control;

the updating the PCC rule of the SMF comprises the following steps: the PCF determines the PDU session currently affected by the AF request of the MEC, and for each determined PDU session, the PCF calls an NPCF _ SMPolicyControl _ UpdateNotify service operation to update the PCC rule of the SMF;

if parameters carried in the AF request message are converted into PCC rules and executed on the UPF, the PDU session is judged to be influenced by the AF request of the MEC;

when the request message contains a request for a notification report of a user plane path change, the information added by the PCF in the PCC rule includes: a notification target address pointing to the AF of the NEF or the MEC, and a notification association identifier containing an AF transaction internal identifier.

2. The method of claim 1, further comprising:

in the process of creating the request message, the AF of the MEC invokes an Nnef _ trafficlnfluency _ Create service operation, and the request message includes a transaction identifier of the AF;

and updating or removing the existing request message, calling an Nnef _ TrapaCinfluence _ Update service operation or an Nnef _ TrapaCinfluence _ Delete service operation by the AF of the MEC, and simultaneously providing a transaction identifier of the AF corresponding to the existing request message.

3. The method of claim 1, wherein the AF of the MEC sends the request message to a NEF, comprising:

the AF of the MEC operates according to the configuration or calling Nbsf _ management _ Discovery service to reach the PCF selected for the current PDU conversation;

the NEF maps information provided by the AF of the MEC to information required for 5 GC.

4. The method according to claim 3, wherein the NEF saves the received request message in the UDR, comprising:

when the AF of the MEC calls an Nnef _ TransFFICInfluency _ Create service operation or calls an Nnef _ TransFFICInfluency _ Update service operation, the NEF saves the request message in the UDR;

when the AF of the MEC calls an Nnef _ Trafficinfluence _ delete service operation, the NEF deletes the AF requirement of the MEC from the UDR;

and after the NEF saves the request message in the UDR or deletes the AF requirement of the MEC from the UDR, the NEF sends response information to the AF of the MEC.

5. The method of claim 1, wherein the PCF receiving notification of data changes from the UDR comprises:

the PCF receives notification of data change Nudr _ DM _ Notification notification from the UDR, wherein the PCF subscribes to AF request modification of the MEC.

6. The method of claim 1, further comprising: and the MEC host level feeds back the resource use condition of the operator at the MEC host level to the MEC system level.

7. The method of claim 6, further comprising: the MEC system level maintains network identification information and resource request message tables for different operators.

8. A system for multi-operator core network interfacing, MEC, comprising:

the MEC is used for inquiring and obtaining a core network entrance of an operator to which the request message points through the AF according to the locally stored association information or configuration information; then, sending the request message to NEF; the method comprises the steps that an MEC host level feeds back the resource use condition of an operator at the MEC host level to the MEC system level, and the MEC system level maintains network identification information of different operators and a corresponding resource request message table;

the NEF is used for saving the received request message in the UDR;

PCF, used for receiving the notice of data change from the UDR and updating PCC rule of SMF;

the SMF, configured to reconfigure the user plane of the PDU session after receiving the updated PCC rule from the PCF, includes:

the SMF issues a message carrying PCC rule and operator network identification information to the UPF through an N4 interface;

after receiving the message sent by the SMF, the UPF performs associated management on the request message and the resources occupied by the operator on the MEC and the UPF according to the operator network identification information, and executes corresponding resource control;

the updating the PCC rule of the SMF comprises the following steps: the PCF determines the PDU session currently affected by the AF request of the MEC, and for each determined PDU session, the PCF calls an NPCF _ SMPolicyControl _ UpdateNotify service operation to update the PCC rule of the SMF;

if parameters carried in the AF request message are converted into PCC rules and executed on the UPF, the PDU session is judged to be influenced by the AF request of the MEC; mapping parameters carried in the AF request message into information required by 5 GC;

when the request message contains a request for a notification report of a user plane path change, the information added by the PCF in the PCC rule includes: a notification target address pointing to the AF of the NEF or the MEC, and a notification association flag containing an AF transaction internal flag.

Images