CN112153698B - Method and equipment for generating cross-domain multi-access edge calculation strategy - Google Patents

Method and equipment for generating cross-domain multi-access edge calculation strategy Download PDF

Info

Publication number
CN112153698B
CN112153698B CN202010948996.4A CN202010948996A CN112153698B CN 112153698 B CN112153698 B CN 112153698B CN 202010948996 A CN202010948996 A CN 202010948996A CN 112153698 B CN112153698 B CN 112153698B
Authority
CN
China
Prior art keywords
policy
pcf entity
pcf
mec server
policy generation
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202010948996.4A
Other languages
Chinese (zh)
Other versions
CN112153698A (en
Inventor
吕华章
张力方
朱常波
冯毅
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China United Network Communications Group Co Ltd
Original Assignee
China United Network Communications Group Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China United Network Communications Group Co Ltd filed Critical China United Network Communications Group Co Ltd
Priority to CN202010948996.4A priority Critical patent/CN112153698B/en
Publication of CN112153698A publication Critical patent/CN112153698A/en
Application granted granted Critical
Publication of CN112153698B publication Critical patent/CN112153698B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/10Flow control between communication endpoints
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/16Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]

Abstract

The application discloses a method and equipment for generating a cross-domain multi-access-edge computing strategy, which can realize the generation of the cross-domain multi-access-edge computing strategy. The method comprises the following steps: the multi-access edge computing MEC server sends a first policy generation request to a first policy control function PCF entity; the first policy generation request is used for requesting to generate a policy in the first PCF entity; the first PCF entity is a PCF entity in a network where the MEC server moves to a visiting place; the MEC server receives a first policy generation response sent by a first PCF; the first policy generation response is used to indicate that the generation of the policy in the first PCF entity was successful. According to the method for generating the cross-domain edge computing strategy, when the MEC server moves to the visiting place network, the PCF entity in the visiting place network can be requested to generate the strategy, so that the cross-domain multi-access edge computing strategy is generated.

Description

Method and equipment for generating cross-domain multi-access edge calculation strategy
Technical Field
The present invention relates to the field of communications, and in particular, to a method and apparatus for generating a cross-domain multi-access edge computing policy.
Background
Multi-access edge computing (MEC) refers to an open platform that merges network, computing, storage, and application core capabilities at the network edge side near a person, object, or data source, and provides edge intelligent services nearby, meeting the key requirements of industry digitization in terms of agile connection, real-time business, data optimization, application intelligence, security, privacy protection, and the like. The MEC server can provide an open-source, open and friendly deployment environment for third-party Applications (APP), and the APP can also provide better quality services for users by utilizing various capabilities provided by the MEC server. The MEC technology has become one of the important technologies supported by the fifth generation mobile communication technology 5G.
Existing MEC servers request policy generation by requesting Policy Control Functions (PCFs) in the home network. However, when the MEC server leaves the home and enters the visited place, there is no prior art related to how the MEC server requests policy generation.
Disclosure of Invention
The application provides a method and a device for generating a cross-domain multi-access-edge computing strategy, which can realize the generation of the cross-domain multi-access-edge computing strategy.
In order to achieve the above purpose, the present application adopts the following technical scheme:
in a first aspect, the present application provides a method for generating a cross-domain edge computing policy, the method comprising: and the MEC server sends a first policy generation request for requesting policy generation in the first PCF entity to the first PCF entity, wherein the first PCF entity is the PCF entity in the network where the MEC server moves to a visiting place, and receives a first policy generation response sent by the first PCF and used for indicating that policy generation in the first PCF entity is successful.
It can be seen that, in the method for generating the cross-domain edge computing policy, when the MEC server moves to the visited network, the policy can be requested to be generated from the PCF entity in the visited network, so that the cross-domain multi-access edge computing policy is generated.
In a second aspect, the present application provides a method for generating a cross-domain edge computing policy, the method comprising: the first PCF entity receives a first policy generation request sent by the MEC server and used for requesting to generate a policy in the first PCF entity, the first PCF entity is the PCF entity in the network where the MEC server moves to a visiting place, the first PCF entity sends the first policy generation request to the second PCF entity, the second PCF entity is the PCF entity in the network where the MEC server belongs, the first PCF entity receives a second policy generation response comprising a trigger parameter of the policy and sent by the second PCF entity, and the first PCF entity generates a first policy generation response used for indicating that the policy generation in the first PCF entity is successful according to the trigger parameter and sends the first policy generation response to the MEC server.
It can be seen that, in the method for generating the cross-domain edge computing policy, when the MEC server moves to the visited network, the policy can be requested to be generated from the PCF entity in the visited network, so that the cross-domain multi-access edge computing policy is generated.
In a third aspect, the present application provides a multi-access edge computing MEC server comprising: a sending unit, configured to send a first policy generation request to a first policy control function PCF entity; the first policy generation request is used for requesting to generate a policy in the first PCF entity; the first PC F entity is a PCF entity in a network where the MEC server moves to a visiting place; the receiving unit is used for receiving a first policy generation response sent by the first PCF; the first policy generation response is used to indicate that the generation of the policy in the first PCF entity was successful.
In a fourth aspect, the present application provides a PCF entity of a policy control function, the PCF entity comprising: the receiving unit is used for receiving a first strategy generation request sent by the multi-access edge computing MEC server; the first policy generation request is used for requesting to generate a policy in the first PCF entity; the first PCF entity is a PCF entity in a network where the M EC server moves to a visiting place; a sending unit, configured to send a first policy generation request to a second PCF entity; the second PCF entity is a PCF entity in a network of the MEC server home location; the receiving unit is further used for receiving a second policy generation response sent by the second PCF entity; the second policy generation response includes trigger parameters for the policy; the generating unit is used for generating a first strategy generation response according to the trigger parameters; the first strategy generation response comprises content corresponding to the strategy; and the sending unit is also used for sending the first strategy generation response to the MEC server.
In a fifth aspect, the present application provides a multi-access edge computing MEC server comprising a memory and a processor. The memory is coupled to the processor. The memory is for storing computer program code, the computer program code comprising computer instructions. When the processor executes the computer instructions, the MEC server performs the method of cross-domain multi-access edge computation policy generation as described in the first aspect and any one of its possible designs.
In a sixth aspect, the present application provides a PCF entity comprising a memory and a processor. The memory is coupled to the processor. The memory is for storing computer program code, the computer program code comprising computer instructions. When the processor executes the computer instructions, the PCF entity performs the method of cross-domain multi-access edge calculation policy generation as described in the second aspect and any one of its possible designs.
In a seventh aspect, the present application provides a computer readable storage medium having instructions stored therein, which when run on a MEC server, cause the MEC server to perform a method of cross-domain multi-access edge computation policy generation as described in the first aspect and any one of its possible designs.
In an eighth aspect, the present application provides a computer readable storage medium having instructions stored therein, which when run on a PCF entity, cause the PCF entity to perform a method of cross-domain multiple access edge calculation policy generation as described in the second aspect and any one of its possible design manners.
In a ninth aspect, the present application provides a computer program product comprising computer instructions which, when run on a MEC server, cause the MEC server to perform a method of cross-domain multi-access edge calculation policy generation as described in the first aspect and any one of its possible designs.
In a tenth aspect, the present application provides a computer program product comprising computer instructions which, when run on a PCF entity, cause the PCF entity to perform the method of cross-domain multiple access edge calculation policy generation as described in the second aspect and any one of its possible design modes.
For a detailed description of the third aspect, the fifth aspect, the seventh aspect, the ninth aspect, and various implementations thereof in this application, reference may be made to the detailed description of the first aspect and various implementations thereof; moreover, the advantages of the third aspect, the fifth aspect, the seventh aspect, the ninth aspect, and various implementations thereof may be referred to the analysis of the advantages of the first aspect and various implementations thereof, and are not described herein.
For a detailed description of the fourth, sixth, eighth, tenth and various implementations thereof in this application, reference may be made to the detailed description of the second and various implementations thereof; further, the advantages of the fourth aspect, the sixth aspect, the eighth aspect, the tenth aspect, and various implementations thereof may be referred to for analysis of the advantages of the second aspect and various implementations thereof, and are not described herein.
These and other aspects of the present application will be more readily apparent from the following description.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic architecture diagram of a network according to an embodiment of the present application;
fig. 2 is a flowchart of a method for generating a cross-domain multi-access edge computing policy according to an embodiment of the present application;
fig. 3 is a second flowchart of a method for generating a cross-domain multi-access edge computing policy according to an embodiment of the present application;
fig. 4 is a schematic hardware structure of a communication device according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of an MEC server according to an embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of a PCF entity according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
The terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature. In the description of the present application, unless otherwise indicated, the meaning of "a plurality" is two or more.
Existing MEC servers request policy generation by a policy control function PCF in the home network. However, when the MEC server leaves the home and enters the visited place, there is no prior art related to how the MEC server requests policy generation.
In view of the above problems, the present application provides a method and an apparatus for generating a cross-domain edge computing policy, which can implement generation of the cross-domain edge computing policy.
Fig. 1 is a schematic diagram of a network architecture according to an embodiment of the present application. The network comprises an authentication server function (authentication server function, AUSF) 101, a unified data management (uni fied data management, UDM) 102, a network storage function (network repository functi on, NRF) 103, a policy control function (policy control function, PCF) 104, a network opening capability (network exposure function, NEF) 105, an access and mobility management function (access management function, AMF) 106, a session management function (sessionmanagement functio n, SMF) 107, a User Equipment (UE) 108, a radio access network (radio accessnetwork, RAN) 109, and a multi-access edge computing MEC server 110. The MEC server 110 includes, among other things, a user plane function (User Plane Function, UPF) 110a and an application function (Ap plication Function, AF) 110b.
The AUSF101 is mainly responsible for authenticating and authorizing the access of the user equipment; the UDM102 is mainly responsible for storing subscription data of the user; NRF103 is mainly responsible for registering and managing network functions; PCF104 is primarily responsible for policy decisions; the NEF105 is mainly responsible for opening network data to the outside; the AMF106 is mainly responsible for access authentication, authorization, and mobility management; SMF107 is mainly responsible for session management, I P address allocation; the UPF110a is mainly responsible for routing, forwarding, and policy enforcement of protocol data units (protocol data unit, PDUs) for packet data; AF110b is primarily responsible for providing PCF104 with traffic information for user access traffic for policy decisions of PCF 104.
The method for generating the cross-domain edge computing strategy provided by the embodiment of the application is described below.
As shown in fig. 2, the method for generating the cross-domain edge computing strategy includes:
s201, the MEC server sends a first policy generation request to a first PCF entity.
The first PCF entity is a PCF entity in the network where the MEC server moves to the visited place.
The first policy generation request is for requesting generation of a policy in the first PCF entity.
Optionally, when the MEC server moves to the coverage area of the visit area, a new PCF is requested to be generated, and the MEC server sends a first policy generation request to the first PCF entity; or when the MEC makes a service for the first time in the coverage area of the visit place, the MEC server sends a first policy generation request to the first PCF entity.
Optionally, the first policy generation request may include: the identity of the MEC server, the identity of the UE generating the policy, the identity information of the context of the APP session associated with the policy.
Illustratively, the identification of the MEC server may be the MEC server's ID, the MEC server's internet protocol (internet protocol, IP) address, or the (media access control, MAC) address. The identity of the UE may be the IP address or MAC address of the UE.
Further optionally, the first policy generation request may further include: permanent subscription identity (subscr iption permanent identifier, SUPI), universal public user identifier, deep neural data network (deep neural network, DNN), bandwidth requirements, traffic description, identifier of MEC APP, traffic status, priority indication, provider of APP service, resource allocation result.
Alternatively, the first policy generation request may be an npcf_mecpoliicycontrol_createquest message.
Alternatively, the first policy generation request may be sent by way of a hypertext transfer protocol (hyper text trans fer protocol, HTTP) _post.
S202, the first PCF entity receives a first policy generation request sent by the MEC server.
S203, the first PCF entity sends a second policy generation request to the second PCF entity.
The second policy generates a trigger parameter requesting the policy.
The second PCF entity is a PCF entity in the network of the MEC server home.
Optionally, the content included in the second policy generation request may be the same as or different from the content included in the first policy generation request.
S204, the second PCF entity receives a second policy generation request sent by the first PCF entity.
S205, the second PCF entity sends a second policy generation response to the first PCF entity.
The second policy generation response includes trigger parameters for the policy.
Alternatively, the second policy generation response may be an npcf_ MECPolicyControl Create Res ponse message.
Alternatively, the second policy generation response may be a hypertext transfer protocol (hyper text transfe r protocol, HTTP) 201 message.
S206, the first PCF entity receives a second policy generation response sent by the second PCF entity.
S207, the first PCF entity generates a first strategy generation response according to the trigger parameters.
The first policy generation response is used to indicate that the generation of the policy in the first PCF entity was successful.
Alternatively, the first policy generation response may be an npcf_ MECPolicyControl Create Res ponse message.
S208, the first PCF entity sends a first policy generation response to the MEC server.
Alternatively, the first policy generation response may be an npcf_ MECPolicyControl Create Res ponse message.
Illustratively, since the MEC is control plane signaling and user plane data with the SMF and UPF, the first PCF may subscribe to policy information for the SMF and UPF associated with the MEC after this message.
S209, the MEC server receives a first policy generation response sent by the first PCF entity.
Optionally, in conjunction with fig. 2, as shown in fig. 3, after S209, the method for generating a cross-domain edge computing policy provided in the present application further includes S210-S217.
S210, the MEC server sends a first policy update request to the first PCF entity.
The first policy update request is used to indicate an update of a policy in the first PCF.
Optionally, the first policy update request may include a base station to which the MEC accesses, a MEC offload policy, a DNN of the connection, and context information of the APP on the MEC.
S211, the first PCF entity receives a first policy update request sent by the MEC server.
S212, the first PCF entity sends a first policy update response to the MEC server.
The first policy update response is used to indicate that the policy update was successful in the first PCF entity.
Alternatively, the first policy update response may be an npcf_ MECPolicyControl Update No tify Respond message.
Alternatively, the first policy update response may be an HTTP 200OK message.
S213, the MEC server receives a first policy update response sent by the first PCF entity.
S214, the first PCF entity sends a second policy update request to the second PCF entity.
Optionally, the content included in the second policy update request may be the same as or different from the content included in the first policy update request.
Optionally, the second policy update request includes: the identity of the MEC server, the identity of U E that generated the policy, the identity information of the context of the APP session associated with the policy.
Illustratively, the identification of the MEC server may be the MEC server's ID, the MEC server's internet protocol (internet protocol, IP) address, or the (media access control, MAC) address. The identity of the UE may be the IP address or MAC address of the UE.
Further optionally, the first policy generation request may further include: permanent subscription identity (subscr iption permanent identifier, SUPI), universal public user identifier, deep neural data network (deep neural network, DNN), bandwidth requirements, traffic description, identifier of MEC APP, traffic status, priority indication, provider of APP service, resource allocation result.
S215, the second PCF entity receives a second policy update request sent by the first PCF entity.
S216, the second PCF entity sends a second policy update response to the first PCF entity.
The second policy update response is used to indicate that the policy update was successful in the second PCF entity.
Alternatively, the second policy update response may be an npcf_ MECPolicyControl Update No tify Respond message.
Alternatively, the first policy update response may be an HTTP 200OK message.
S217, the first PCF entity receives a second policy update response sent by the second PCF entity.
According to the method for generating the cross-domain edge computing strategy, when the MEC server moves to the visiting place network, the PCF entity in the visiting place network can be requested to generate the strategy, so that the cross-domain multi-access edge computing strategy is generated.
The foregoing description of the solution provided in the embodiments of the present application has been mainly presented in terms of a method. To achieve the above functions, it includes corresponding hardware structures and/or software modules that perform the respective functions. Those of skill in the art will readily appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
As shown in fig. 4, the embodiment of the present application provides a communication device 400, where the communication device 400 may be a MEC server or a PCF entity, which is not limited in this application. The communication device 400 may include at least one processor 401, communication lines 402, memory 403, and a communication interface 404.
Specifically, the processor 401 is configured to execute computer-executable instructions stored in the memory 403, thereby implementing steps or actions of the terminal.
The processor 401 may be a chip. For example, it may be a field programmable gate array (field programmable gate array, FPGA), an application specific integrated chip (application spe cific integrated circuit, ASIC), a system on chip (So C), a central processing unit (central processor unit, CPU), a network processor (network processor, NP), a digital signal processing circuit (digital si gnal processor, DSP), a microcontroller (micro controller unit, MCU), a programmable controller (programmable logic device, PLD) or other integrated chip.
A communication line 402 for transmitting information between the processor 401 and the memory 403.
Memory 403 for storing computer-executable instructions for execution and for execution controlled by processor 401.
The memory 403 may be self-contained and be coupled to the processor via communication line 402. The memory 403 may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM). It should be noted that the memory of the systems and devices described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
A communication interface 404 for communicating with other devices or communication networks. The communication network may be an ethernet, a radio access network (radio access network, RAN), or a wireless local area network (w ireless local area networks, WLAN), among others.
It is noted that the structure shown in fig. 4 does not constitute a limitation of the communication device, and the communication device may comprise more or less components than shown in fig. 4, or may combine certain components, or may be arranged in different components.
As shown in fig. 5, embodiments of the present application provide a MEC server 50. The MEC server 50 may include a transmitting unit 51, a receiving unit 52.
A sending unit 51, configured to send a first policy generation request to a first policy control function PCF entity. For example, in connection with fig. 2, the transmitting unit 51 may be used to perform S201.
And a receiving unit 52, configured to receive the first policy generation response sent by the first PCF. For example, in connection with fig. 2, the receiving unit 52 may be used to perform S209.
In actual implementation, the transmitting unit 51 and the receiving unit 52 may be implemented by the processor 401 shown in fig. 4 calling the program code in the memory 403. For a specific implementation process, reference may be made to a description of a method portion for generating a cross-domain multi-access edge computing policy shown in fig. 2, which is not repeated herein.
As shown in fig. 6, an embodiment of the present application provides a PCF entity 60. The PCF entity 60 may comprise a receiving unit 61, a sending unit 62 and a generating unit 63.
A receiving unit 61, configured to receive a first policy generation request sent by the multi-access edge computing MEC server. For example, in connection with fig. 2, the receiving unit 61 may be used to perform S202.
And the sending unit 62 sends the first policy generation request to the second PCF entity. For example, in connection with fig. 2, the transmitting unit 62 may be used to perform S203.
The receiving unit 61 is further configured to receive a second policy generation response sent by the second PCF entity. For example, in connection with fig. 2, the receiving unit 61 may be used to perform S206.
The generating unit 63 is configured to generate a first policy generation response according to the trigger parameter. For example, in connection with fig. 2, the generation unit 63 may be used to perform S207.
The sending unit 62 is further configured to send the first policy generation response to the MEC server. For example, in connection with fig. 2, the sending unit 62 may also be used to perform S208.
In actual implementation, the receiving unit 61, the transmitting unit 62, and the generating unit 63 may be implemented by the processor 401 shown in fig. 4 calling the program code in the memory 403. For a specific implementation process, reference may be made to a description of a method portion for generating a cross-domain multi-access edge computing policy shown in fig. 2, which is not repeated herein.
It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.
Another embodiment of the present application further provides a computer readable storage medium, where computer instructions are stored, where the computer instructions, when executed on an MEC server, cause the MEC server to perform each step performed by the MEC server in the method flow shown in the foregoing method embodiment.
Another embodiment of the present application further provides a computer readable storage medium, where computer instructions are stored in the computer readable storage medium, where the computer instructions, when executed on a PCF entity, cause the PCF entity to perform each step performed by the PCF entity in a method flow shown in the foregoing method embodiment.
In another embodiment of the present application, there is also provided a computer program product comprising instructions that, when run on an MEC server, cause the MEC server to perform the steps performed by the MEC server in the method flow shown in the method embodiment described above.
In another embodiment of the present application, there is also provided a computer program product comprising instructions that, when executed on a PCF entity, cause the PCF entity to perform the steps performed by the PCF entity in the method flow shown in the method embodiment described above.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not described in detail herein.
In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, e.g., the partitioning of elements is merely a logical functional partitioning, and there may be additional partitioning in actual implementation, e.g., multiple elements or components may be combined or integrated into another system, or some features may be omitted, or not implemented. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interface, indirect coupling or communication connection of devices or units, electrical, mechanical, or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions easily conceivable by those skilled in the art within the technical scope of the present application should be covered in the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (7)

1. A method for cross-domain multi-access edge computing policy generation, comprising:
the PCF entity receives a first policy generation request sent by a multi-access edge computing (MEC) server; the first policy generation request is used for requesting to generate a policy in the first PCF entity; the first PCF entity is a PCF entity in a network where the MEC server moves to a visiting place;
the first PCF entity sends a second policy generation request to a second PCF entity; the second policy generates a trigger parameter requesting the policy; the second PCF entity is a PCF entity in the network of the MEC server home location;
the first PCF entity receives a second policy generation response sent by the second PCF entity; the second policy generation response includes trigger parameters for the policy;
the first PCF entity generates a first strategy generation response according to the trigger parameter; the first policy generation response is used for indicating that the policy generation in the first PCF entity is successful;
the PCF entity sends the first policy generation response to the MEC server.
2. The method of claim 1, wherein the step of determining the position of the substrate comprises,
the first policy generation request includes: the identity of the MEC server, the identity of the UE requesting the policy, and the identity information of the context of the APP session associated with the policy.
3. The method according to claim 1, wherein the method further comprises:
the first PCF entity receives a first policy update request sent by the MEC server; the first policy update request is used to indicate an update of a policy in the first PCF.
4. A method according to claim 3, characterized in that the method further comprises:
the first PCF entity sends a second policy update request to the second PCF entity so that the second PCF entity updates the policy in the second PCF.
5. A policy control function, PCF, entity, said PCF entity comprising:
the receiving unit is used for receiving a first strategy generation request sent by the multi-access edge computing MEC server; the first policy generation request is used for requesting to generate a policy in a first PCF entity; the first PCF entity is a PCF entity in a network where the MEC server moves to a visiting place;
a sending unit, configured to send the first policy generation request to a second PCF entity; the second PCF entity is a PCF entity in the network of the MEC server home location;
the receiving unit is further configured to receive a second policy generation response sent by the second PCF entity; the second policy generation response includes trigger parameters for the policy;
the generating unit is used for generating a first strategy generation response according to the trigger parameters; the first policy generation response is used for indicating that the policy generation in the first PCF entity is successful;
the sending unit is further configured to send the first policy generation response to the MEC server.
6. A PCF entity, wherein the PCF entity comprises a memory and a processor; the memory is coupled to the processor; the memory is used for storing computer program codes, and the computer program codes comprise computer instructions; the PCF entity, when executing the computer instructions, performs the method of cross-domain multiple access edge computing policy generation of any one of claims 1-4.
7. A computer readable storage medium having instructions stored therein that, when executed on a PCF entity, cause the PCF entity to perform the method of cross-domain multiple access edge computing policy generation of any one of claims 1-4.
CN202010948996.4A 2020-09-10 2020-09-10 Method and equipment for generating cross-domain multi-access edge calculation strategy Active CN112153698B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010948996.4A CN112153698B (en) 2020-09-10 2020-09-10 Method and equipment for generating cross-domain multi-access edge calculation strategy

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010948996.4A CN112153698B (en) 2020-09-10 2020-09-10 Method and equipment for generating cross-domain multi-access edge calculation strategy

Publications (2)

Publication Number Publication Date
CN112153698A CN112153698A (en) 2020-12-29
CN112153698B true CN112153698B (en) 2023-06-23

Family

ID=73890015

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010948996.4A Active CN112153698B (en) 2020-09-10 2020-09-10 Method and equipment for generating cross-domain multi-access edge calculation strategy

Country Status (1)

Country Link
CN (1) CN112153698B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115225363B (en) * 2022-07-13 2024-01-30 中国电信股份有限公司 Edge capability opening method and device, storage medium and electronic equipment

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008083630A1 (en) * 2007-01-11 2008-07-17 Huawei Technologies Co., Ltd. Method, system and device for policy and rules decision
CN109673005A (en) * 2017-10-17 2019-04-23 华为技术有限公司 A kind of method, apparatus and system of determining PCF
CN109729181A (en) * 2017-10-27 2019-05-07 华为技术有限公司 A kind of method for accessing domain name and equipment
CN109922472A (en) * 2017-12-13 2019-06-21 华为技术有限公司 The acquisition of subscriber policy
CN110519746A (en) * 2018-05-21 2019-11-29 华为技术有限公司 One kind is for terminating access and the associated method and apparatus of Mobility Management Strategy
CN111565385A (en) * 2019-02-14 2020-08-21 华为技术有限公司 Policy providing method, device and system

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109428781B (en) * 2017-08-30 2021-11-05 中兴通讯股份有限公司 Session usage monitoring control method, server and storage medium

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008083630A1 (en) * 2007-01-11 2008-07-17 Huawei Technologies Co., Ltd. Method, system and device for policy and rules decision
CN109673005A (en) * 2017-10-17 2019-04-23 华为技术有限公司 A kind of method, apparatus and system of determining PCF
EP3700241A1 (en) * 2017-10-17 2020-08-26 Huawei Technologies Co., Ltd. Method, apparatus and system for determining pcf
CN109729181A (en) * 2017-10-27 2019-05-07 华为技术有限公司 A kind of method for accessing domain name and equipment
CN109922472A (en) * 2017-12-13 2019-06-21 华为技术有限公司 The acquisition of subscriber policy
CN110519746A (en) * 2018-05-21 2019-11-29 华为技术有限公司 One kind is for terminating access and the associated method and apparatus of Mobility Management Strategy
CN111565385A (en) * 2019-02-14 2020-08-21 华为技术有限公司 Policy providing method, device and system

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
"S2-165172-revision of 4740-PCR-Solutions to Policy framework for roaming cases".3GPP tsg_sa\WG2_Arch.2016,1-3页. *
Ericsson.C3-190211 "Corrections for Location Change Policy Control Request Triggers".3GPP tsg_ct\wg3_interworking_ex-cn3.2019,(第tsgc3_101_montreal期),全文. *
Ericsson.S2-165534 "Updates in Policy Reference Architecture to reflect roaming aspects".3GPP tsg_sa\WG2_Arch.2016,(第TSGS2_117_Kaohsiung_City期),全文. *
Nokia, Nokia Shanghai Bell.S2-1903668 "Correcting AMF behaviour for Service Request that is not integrity protected".3GPP tsg_sa\wg2_arch.2019,(第tsgs2_132_xian期),全文. *
ZTE, Oracle, Telecom Italia, ETRI(?), Sandvine, China Telecom(?).S2-166368 "NextGen roaming interface between VPF and HPF in case of LBO".3GPP tsg_sa\WG2_Arch.2016,(第TSGS2_118_Reno期),1-3页. *

Also Published As

Publication number Publication date
CN112153698A (en) 2020-12-29

Similar Documents

Publication Publication Date Title
CN112437456B (en) Communication method and equipment in non-public network
US10412667B2 (en) Method for establishing a roaming connection
CN112202844B (en) Method and equipment for opening cross-domain multi-access edge computing capability
CN114902634A (en) Apparatus and method for providing information of application server in mobile communication system
KR20220114638A (en) Method, device, and system for updating an anchor key in a communication network for encrypted communication with a service application
US20210377054A1 (en) Systems and methods for managing public key infrastructure certificates for components of a network
US20220191028A1 (en) Authorization of network request
WO2021093162A1 (en) Method, device, and system for anchor key generation and management in a communication network for encrypted communication with service applications
CN112153698B (en) Method and equipment for generating cross-domain multi-access edge calculation strategy
Doumiati et al. Analytical study of a service discovery system based on an LTE-A D2D implementation
CN112202917A (en) Method and equipment for terminating multi-access edge computing service
Boubakri et al. Access control in 5G communication networks using simple PKI certificates
WO2021093163A1 (en) Method, device, and system for application key generation and management in a communication network for encrypted communication with service applications
Kalalas et al. Lightweight and space-efficient vehicle authentication based on cuckoo filter
US20230030315A1 (en) Network Security
EP3955542A1 (en) Enhancements for secure updating in communication networks
JP7068687B2 (en) Wireless communication system, wireless communication method
KR20210040776A (en) Method and apparatus for activating 5g user in 5g system
CN114268945B (en) Communication network access method, device and system
US11800596B2 (en) Systems and methods for temporary service provisioning
US9788229B2 (en) Method and apparatus for traffic re-routing based on application-layer traffic optimization services in wireless networks
CN117478431B (en) Industrial Internet of things control method based on trusted network
US20230413353A1 (en) Inter-plmn user plane integration
US20240137366A1 (en) Systems and methods for providing prioritization for data transport services
US11432158B2 (en) Systems and methods for using a unique routing indicator to connect to a network

Legal Events

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