CN112752301B

CN112752301B - Method and system for switching multiple operation scenes and communication equipment

Info

Publication number: CN112752301B
Application number: CN202011637636.9A
Authority: CN
Inventors: 尤建洁; 石磊
Original assignee: Network Communication and Security Zijinshan Laboratory
Current assignee: Zijinshan Laboratory
Priority date: 2020-12-31
Filing date: 2020-12-31
Publication date: 2022-10-14
Anticipated expiration: 2040-12-31
Also published as: WO2022141708A1; CN112752301A

Abstract

The application relates to a method for switching multiple operation scenes of a multi-access edge computing system. The method comprises the following steps: the multi-access edge computing system receives a first request sent by a session management function unit to request to modify an N4 session, wherein the first request comprises a PDU session identifier, user terminal position information and QoS information; the multi-access edge computing system carries out authorization check on the first request, and queries a host level arranged in the multi-access edge computing system based on the information included in the first request when the authorization check is passed; the multi-access edge computing system determines a new multi-access edge computing router involved in the user terminal switching scenario, wherein the new multi-access edge computing router is located in the queried host level; and the multi-access edge computing system sending a response to the session management function to make the N4 session modification.

Description

Method and system for switching multiple operation scenes and communication equipment

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method for switching multiple operation scenarios based on a Multi-Access Edge Computing (MEC) system.

Background

With the sudden change of international situation, the construction of the fifth generation mobile communication technology 5G is further accelerated domestically, and various secondary development and application schemes based on the 5G technology are accelerated. The third Generation Partnership project (3 rd Generation Partnership project,3 GPP) 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 scenario provides large-traffic data communication, such as high-speed downloading, high-definition video, etc., which causes great pressure on the wireless backhaul network, because in this scenario, the service needs to be sunk to the edge of the network as much as possible, that is, the data stream in the network needs to be sent to the network layer of the access user terminal, so as to stream the data locally. The URLLC scenario provides ultra-high speed, reliable, ultra-low latency communication services, such as services for unmanned driving, industrial control, etc., which also requires that traffic is sunk to the edge of the network to reduce network latency caused by network transmission.

In the face of the feature that 5G applications need to be sunk to the edge of the network, MECs have come and are already incorporated into the 3gpp 5G standard as a key technology. The 5G core network is separated from the UP (User Plane) by a CP (Control Plane), and the UPF (User Plane Function, user Plane network element) can be flexibly deployed to the network edge, while the Control Plane functions such as PCF (Policy Control Function) and SMF (Session Management Function) can be deployed in a centralized manner. MEC enables operator and third party services to be hosted near an 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 architecture of 5G combined with MEC, the MEC system interfaces with 5G core networks of different operators. When a user terminal of an external operator is switched, an MEC system under the current architecture cannot meet the requirements of service continuity guarantee in the aspects of security management, policy controllability and the like, which also causes that an MEC access network and internet services cannot be deeply fused.

Disclosure of Invention

In view of the above, the present application provides improved edge computing system-related solutions.

According to one aspect of the present application, a method of multi-operational scenario switching based on a multi-access edge computing system is provided. The method comprises the following steps: the multi-access edge computing system receives a first request sent by a session management function unit to request modification of an N4 session, the first request comprising a PDU session identification, user terminal location information and QoS (quality of service) information; the multi-access edge computing system carries out authorization check on the first request, and queries a host level subsystem arranged in the multi-access edge computing system based on the information included in the first request when the authorization check is passed; the multi-access edge computing system determines a new router in the multi-access edge computing system related to the user terminal switching scene, wherein the new multi-access edge computing router is located in the inquired host-level subsystem; and the multi-access edge computing system sending a response to the session management function to make the N4 session modification.

In some examples, according to the method, the multi-access edge computing system may further include instructing the source multi-access edge computing router to release the data path with the source access network. According to this example, optionally, the multi-access edge computing system also instructs the multi-access edge computing router that was already in use before the handover to release the data path with the source access network.

In some examples, according to the method, when the new router is a multi-access edge computing router that is already in use before the current handover, the multi-access edge computing system instructs the new router to release the data path with the source access network and establish the data path with the target access network.

In some examples, according to the method, further comprising the new router sending an N3 end marker to the source access network.

In some examples, according to the method, the source access network sends an N3 end marker to the target access network after receiving the N3 end marker.

In some examples, according to the method, the session management function unit receives a PDU session update request sent by an access and mobility management function unit before sending the first request, wherein the PDU session update request is sent by the target access network to the access and mobility management function unit after the handover preparation of the user terminal, the source access network and the target access network is completed.

In some examples, according to the method, the session management function is to respond to the PDU session update request after the source access network sends an N3 end marker to the target access network.

In some examples, according to the method, the multi-access edge computing system is further configured to formulate a offloading policy rule, and issue the formulated offloading policy rule to a relevant multi-access edge computing router, so that the multi-access edge computing router forwards an uplink data packet sent by a user terminal to a specified path according to the offloading policy rule. In still other examples, the multi-access edge computing system is configured to insert or delete routers on the data path that support offload policy rules as needed.

According to another aspect of the present application, there is also provided a multi-access edge computing system comprising a communication interface for receiving a first request sent by a session management function to request modification of an N4 session, the first request comprising a PDU session identification, user terminal location information and QoS information; and a UPF agent module (user plane function management module). The UPF agent module is configured to perform authorization check on the first request and query a host-level subsystem arranged in the multi-access edge computing system based on the information included in the first request if the authorization check is passed; determining a new router in a multi-access edge computing system involved in the user terminal switching scenario, the new router being located in the queried host-level subsystem; and sending a response to the session management function for the N4 session modification.

According to some examples of the present application, the multi-access edge computing system includes a DN controller (data network controller) configured to: and formulating a distribution strategy rule and issuing the formulated distribution strategy rule to a related multi-access edge computing router so that the multi-access edge computing router forwards an uplink data packet sent by a user terminal to an appointed path according to the distribution strategy rule. In some examples, the DN controller is configured to insert or delete routers on the data path that support offload policy rules as needed.

According to some examples of the present application, there is also provided a communication device configured to perform the method of switching multi-operational scenarios for a multi-access edge computing system as described above.

According to still further examples of the present application, there is also provided a communication device comprising a storage module storing instructions and a processing module configured to execute the instructions and when executing the instructions, implement the method for switching multi-operational scenarios for a multi-access edge computing system described above.

Drawings

These and other features, aspects, and advantages of the present disclosure will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:

fig. 1 is a schematic illustration of the basic architecture of a prior art 5G system in combination with an MEC system;

FIG. 2 is a block diagram of an MEC system in accordance with an exemplary embodiment of the present application;

FIG. 3 is a flow chart of a method of multi-operational scenario switching based on an MEC system in accordance with one example of the present application;

FIG. 4 is a flow chart of a multi-operational scenario switching method according to one example of the present application;

fig. 5 is an interaction flowchart of a 5G core network and an MEC system at UE handover according to the present application.

Detailed Description

In order that those skilled in the art will better understand the technical solutions of the present invention, the present invention will be described in detail with reference to the accompanying drawings and specific embodiments. In the following examples, the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions. It should be noted that the embodiments described below in conjunction with the drawings are illustrative and should not 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. 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.

Some acronyms appear in this application to explain:

AF (Application Function);

AN (Access Network );

AUSF (Authentication Server Function);

AMF (Access and Mobility Management Function);

a CP (control plane);

DN (Data Network );

DN-C(DN Controller)；

eMBB (Enhanced Mobile Broadband );

and g NB: a 5G base station;

MEC (Multi-Access Edge Computing);

MEC Router (MEC Router);

mtc (Massive Machine Type Communication);

NEF (Network Exposure Function, network open Function);

NSSF (Network Slice Selection Function);

NRF (NF replication Function, network storage Function);

NG-RAN (Next Generation-Radio Access Network, next Generation Radio Access Network);

NFs (Network Functions);

an OLT (Optical Line Terminal);

PCF (Policy Control Function);

PCC (Policy Control and Charging);

PLB (Policy-based Local Breakout, policy diversion function);

PLB-MEC (MEC router supporting policy offload function);

SMF (Session Management Function);

UPF (User Plane Function);

UPF-P (UPF Proxy );

URLLC (Ultra-reliable and Low Latency Communications);

UDM (Unified Data Management );

UP (User Plane ), UE (User Equipment);

5G (5 th Generation mobile networks or 5th Generation with less systems, 5th-Generation, fifth Generation mobile communication technology);

5GoC (5G over Cable, 5G access to Cable TV network);

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

The ETSI GS MEC specification of the european telecommunications standardization institute ETSI defines the reference architecture of MECs. According to this specification, an MEC system includes an MEC host and MEC management functions. The MEC host includes an MEC platform, virtualization infrastructure, and various MEC applications and services running on the MEC host. The MEC management functions include MEC system level management functions and host level management functions. The MEC system level management functions include a user application lifecycle management agent, an operation support system, and a MEC orchestrator (organizer), and the MEC host level management functions include a MEC platform manager and a virtualization infrastructure manager. MEC enables 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 user plane function UPF close to the UE and performs flow control from the UPF to the local data network over the N6 interface. This may be governed based on subscription data of the UE, UE location, information from Application Functions (AFs), policies, or other related traffic.

In this kind of Application scenario, the MEC system is in the role of AF (Application Function) plus DN (Data Network) with respect to the 5G core Network, and the MEC orchestrator is an MEC system-level functional entity, which acts as an AF and can interact with NEF (Network expose Function), or in some cases directly interact with target 5G NFs, for example, the order of sending messages is shown by NEF- > PCF- > SMF (this shows the order of sending messages, i.e. messages are sent from NEF to PCF and then to SMF) to affect the user plane policy, or the user plane policy is affected by directly connecting to PCF- > SMF in the 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, may interact with the NEF/PCF more, invoking other 5G core network open capabilities, such as message subscription, qoS, etc.

Fig. 1 is a schematic illustration of the basic architecture of an existing 5G system in combination with an MEC system. As shown, MEC system 10 includes a MEC orchestrator 100, a MEC platform 102, a MEC platform manager 104, a virtualization infrastructure manager 106, a data network 108, and a plurality of applications (not identified) and a plurality of services (not identified). MEC orchestrator 100 is considered to be located within system level subsystems of MEC system 10; the MEC platform 102, MEC platform manager 104, virtualization infrastructure manager 106, data network 108, and the plurality of applications and services are considered to be distributed within the host-level subsystems of the MEC system. The 5G core network selects a user interface function UPF 21 close to the user terminal UE 20 and performs flow control from the UPF 21 to the local data network (not shown) over the N6 interface. It should be noted that, in the description of the present application with reference to the drawings, a System Level in the MEC System architecture is referred to as an MEC System Level subsystem to indicate that different functional units, modules, devices, entities, etc. may be included therein, and in this document, the MEC System Level and the MEC System Level subsystem are replaceable with each other. Host Level (Host Level) in the MEC system architecture is referred to as MEC Host Level subsystem to indicate that functional units, modules, devices, entities, etc. may be included therein; in this context, MEC host-level and MEC host-level subsystems are interchangeable.

MEC orchestrator 100 is a functional entity at the MEC system level that may act as an AF to interact with the network open function NEF, or in some cases MEC orchestrator 100 may interact directly with different network functions NFs of the target 5G network. For example, the user plane policy is affected by the NEF, PCF, SMF in the role of untrusted AF, or by directly affecting the user plane policy by PCF, SMF in the role of trusted AF. In the MEC host level subsystem, the MEC platform 102 may also interact with NFs of the 5G network as an AF. The MEC system 10, 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.

Fig. 2 is a schematic structural diagram of an MEC system according to an example of the present application. As shown, the MEC system of the illustrated example is compared to that shown in fig. 1, where a UPF proxy module 3051 and a DN controller 3052 are provided at the system level subsystems of the MEC system. The system level control plane of the MEC system provides communication connection to a plurality of 5G core networks outside the MEC system and supports the N4 interface defined by 3 GPP. The plurality of 5G core networks referred to herein includes 2 or more 5G core networks. In fig. 2, a 5G core network 90 of operator a and a 5G core network 92 of operator B are illustrated. As shown, the UPF proxy module 3051 communicates with the carrier a 5G core network 90 and the carrier B5G core network 92 via an N4 interface. The system level data plane of the MEC system provides communication connection to a plurality of 5G core networks outside the MEC system and supports the N6 interface defined by 3 GPP. As shown in fig. 2, the system level of the MEC system communicates with DN 91 of operator a, DN 93 of operator B over an N6 interface. The communication connection described herein indicates that the MEC system has a communication interface (not labeled) for communication.

The MEC system level may communicate with a host level of the MEC system. For example, the UPF proxy module 3051 may be connected to multiple MEC host levels of the MEC system for information interaction with routers, APPs, etc. within the host levels. As shown in fig. 2, the UPF proxy module 3051 communicates with the router at the host level 80 of the MEC system shown in the figure, and with the router at the host level 82 of the MEC system shown in the figure. Only host level 80 and host level 82 are illustrated in fig. 2, but the MEC system may include more host levels.

According to some examples of the present application, the UPF proxy module 3051 may receive messages from the 5G core network through the N4 interface, where the messages include policy rules of the traffic flow, user information, and the like, and the policy rules may include information of bandwidth and priority (e.g., priority of message being processed/forwarded). As an example, these policy rules, user information, etc. are sent by the SMF to the UPF proxy module 3051 via an N4 session request. The UPF agent module 3051 performs authorization check on the policy rule from the 5G core network according to the local configuration of the MEC system, and maps the policy rule into policy rule information which can be identified and processed by the MEC system; the authorization check of the policy rule from the 5G core network checks whether the operator of the 5G core network is authorized to issue such policy rule, that is, whether the operator of the 5G core network is a contracted operator. In some cases, the UPF agent module 3051 may properly adjust the policy rules from the core network according to the local configuration and the subscription information of the core network operator. For example, if the bandwidth requested in the requested policy rule is greater than the contracted bandwidth, the adjustment is performed to adopt the contracted bandwidth.

In the event that the UPF proxy module 3051 can match an MEC router satisfying the core network policy rules from among the plurality of MEC routers of the MEC system, then a modified response is made to the N4 session modification request issued by the SMF.

DN controller 3052 is configured to connect with MEC routers supporting Policy-based Local Breakout (PLB) and to interact with information from these MEC routers. DN controller 3052 is configured to formulate a policy offloading rule and issue the policy offloading rule to an MEC router supporting a policy offloading function. In the example of the present application, the policy splitting rule is adapted to indicate which part of the traffic is split to the 5G core network and which part of the traffic is split to the local data network, so that the destination IP address/prefix and the like of the uplink IP data packet sent by the UE can be checked and known, and the MEC router forwards the data packet to a specified path according to the information known from the splitting rule, where the path may lead to different data networks (e.g., to the local core network, or to the local data network, and the like). Furthermore, DN controller 3052 is also configured such that MEC routers supporting PLBs can be inserted or deleted on a data path as needed.

Fig. 3 is a flowchart of a method for multi-operational scenario switching based on MEC system according to an example of the present application. As shown, at step S300, a multi-access edge computing system, i.e., an MEC system, receives a first request sent by a session management function over its communication interface to request modification of an N4 session. The first request includes a PDU (Protocol Data Unit) session identification, user terminal location information, and QoS information. In step S302, the MEC system performs an authorization check on the first request, and queries an MEC host-level subsystem provided in the MEC system based on information included in the first request if the authorization check passes. More specifically, the MEC system queries the MEC routers within the MEC host level subsystem for the status of available resources such as APPs. At step S304, the MEC system determines a new router, also referred to herein as a new MEC router, in the MEC system involved in the user terminal handover scenario. Wherein the new MEC router is located within the queried MEC host-level subsystem. At step S306, the MEC system sends a response to the session management function unit to perform N4 session modification to ensure continuity of the user terminal service.

As is known, the session management function SMF is a session function management unit of the 5G core network. In this application, the session management function is also referred to as a session management function unit. Similarly, the access and mobility management function AMF is a management unit in the network, also referred to herein as an access and mobility management function.

In some examples, the method shown in fig. 3 further comprises the multi-access edge computing system issuing policy information instructing the new MEC router to establish a data path with a target access network. In this example, the multi-access edge computing system optionally also sends an indication to the multi-access edge computing router that was already in use before the handover, i.e. the old MEC router, to release the data path with the source access network.

In still other examples, i.e., in the case where the selected new MEC router is also an old MEC router that is already in use before the handover, the multi-access edge computing system instructs the old MEC router to establish a data path with the source access network and to establish a data path with the target access network.

In each example of the method for switching multiple operation scenarios based on a multi-access edge computing system, by way of example and not limitation, the multi-access edge computing system is configured to formulate a offloading policy rule, and issue the formulated offloading policy rule to a relevant multi-access edge computing router, so that the multi-access edge computing router forwards an uplink data packet sent by a user terminal to a specified path according to the offloading policy rule. Further, the multi-access edge computing system may also be configured to insert or delete routers on the data path that support offload policy rules as needed.

The method shown in fig. 3 may be performed by the MEC system shown in fig. 2. For example, the UPF agent module 3051 of the MEC system receives (step S300) a first request transmitted by the SMF to request modification of the N4 session, the first request including a PDU session identification, user terminal location information, and QoS information. The UPF agent module 3051 of the MEC system performs an authorization check on the first request (step S302). The UPF proxy module 3051 is further arranged to interact with the MEC orchestrator, in case the authorization check passes, to query (step S302) a host level, e.g. the query host level 80 and/or the host level 82, provided within the MEC system, in particular to query available resources, such as MEC routers and APPs, within it, based on the information comprised by the first request. Based on the query result, the UPF proxy module 3051 further determines (step S304) a new MEC router involved in the user terminal handover scenario, for example, a router possibly set in the host level 80 or a router possibly set in the host level 82. After the above authorization check, the query of available routers and available resources such as APP in the MEC system, and the confirmation of the involved new MEC router are performed in the MEC system, the MEC system sends (step S306) a response to perform N4 session modification to the SMF, so that the service after the user terminal switches the scenario runs safely and continuously. In some examples, the method further includes formulating, by DN controller 3052 of the MEC system, offloading policy rules and issuing the formulated offloading policy rules to the relevant MEC routers; wherein, the related multi-access edge computing router refers to an MEC router supporting the offloading policy rule. And the MEC router receiving the shunting strategy rule forwards the uplink data packet sent by the user terminal to the designated path according to the shunting strategy rule. In still other examples according to the method, DN controller 3052 of the MEC system is also used to insert or delete routers supporting offload policy rules on the data path as needed.

FIG. 4 is a flow chart of a multi-operational scenario switching method according to one example of the present application. According to the present example, the UE 301 has registered and established a PDU session with the 5G network and is using the service. The UE 301 has access to the local data network via the source 5G radio access network S-NG-RAN 301. When the location of the UE 301 changes and the source 5G radio access network S-NG-RAN301 will be moved into the new NG RAN service area, i.e. the target 5G radio access network T-NG-RAN 302, a handover preparation is performed, as shown in step S41.

In step S42, the execution of the switching operation is started.

The source 5G radio access network S-NG-RAN301 forwards the data to the target 5G radio access network T-NG-RAN 302 at step S43.

The target 5G radio access network T-NG-RAN 302 sends an N2 path switch request to the AMF 303 at step S44. The N2 path switch request includes a PDU session list to be switched and session management (N2 SM) information of a corresponding N2 interface, location information of the UE 300, and the like. As mentioned above, the AMF is an access and mobility management function, which is also referred to as an access and mobility management function element in the present application.

If the PLMN (Public land Mobile Network) configures a Secondary RAT usage (Secondary RAT usage) report, in step S34, the source 5G radio access Network S-NG-RAN301 provides a RAN usage data report to the AMF 303.

At step S45, AMF 303 transmits a PDU session update request containing N2 SM information, UE 300 location information, and the like, to SMF 304.

At step S46, the SMF304 sends a first request to the MEC network control platform 305 to request a modification of the N4 session request. In this example, this first request is referred to hereinafter as an N4 session modification request, which includes a PDU session ID, UE location information, qoS list, etc.

According to some examples of the present application, an MEC network control platform is provided in the MEC system, which receives the N4 session modification request from the SMF 304.

Furthermore, the MEC network control platform 305 also receives information including policy rules of the traffic flow, user information, and the like from the 5G core network, wherein the policy rules received from the 5G core network include, for example, bandwidth and priority information. In some examples of the present application, MEC network control platform 305 receives information including policy rules, user information, etc. for traffic flows from SMF 304.

At step S47, the MEC network control platform 305 performs an authorization check on the request from the 5G core network according to the local configuration and the local policy rules to confirm whether authorization is given.

According to some examples of the application, the MEC network control platform 305 is configured to include a UPF proxy module 3051 and a DN controller 3052. The UPF proxy module 3051 receives a message containing policy rules (e.g., bandwidth, priority, etc.) of a traffic flow, user information, etc. from a 5G core network (specifically, SMF), where the policy rules from the core network indicate quality of service requirements of the 5G core network that need to be met. The UPF agent module 3051 performs authorization check on the policy rules from the 5G core network according to the local configuration and the local policy rules, and maps to the policy rule information that the MEC system can recognize and process. In some cases, the UPF proxy module 3051 may make appropriate adjustments to policy rules from the core network. The DN controller 3052 is configured to formulate a offloading policy rule, and issue the offloading policy rule to the MEC router supporting the policy offloading function. Specifically, according to the offloading rule, the destination IP address/prefix, etc. of the uplink IP packet sent by the UE 300 may be checked, and then the packet is forwarded to the specified path according to the information indicated by the rule. The MEC network control platform 305 is configured to insert or delete a plcb capable MEC router on the data path as needed.

If the check made in step S47 passes, step S38 is executed. Otherwise, an unauthorized response is sent to SMF304, which may carry the reason for the unauthorized.

In step S48, the MEC network control platform 305 performs information interaction with the MEC orchestrator 307, including querying the MEC host level, available resources, and the like, which have been arranged in the MEC system. Specifically, the MEC orchestrator 307 matches the router in the corresponding MEC host level and the application resource such as APP according to the location information of the UE 300, and determines the availability of the matched router and application resource in the MEC host level according to the service requirement of the UE 300.

At step S49, the MEC network control platform 305 makes a policy decision. Specifically, the MEC network control platform 305 may know that the UE 300 is switched according to the change of the location information of the UE 300, and in order to ensure the service continuity of the UE 300, the UPF agent module 3051 of the MEC network control platform 305 determines the MEC router to be involved; where the change in the UE 300 location information may be determined by the originally stored UE 300 location information and the new UE location information received from SMF 304. According to an example of the present application, a router, which matches a policy rule from a core network, among a plurality of MEC routers in an MEC system is determined as an MEC router to be involved.

In the example where the MEC network control platform 305 includes the UPF agent module 3051 and the DN controller 3052, the policy decision of step S39 may be optionally performed by the UPF agent module 3051.

At step S410, the MEC network control platform sends a response message to the SMF304 indicating that N4 session modification is authorized.

At step S411, the MEC network control platform 305 issues policy information to the MEC router 308 determined at step S39. This information includes policy information from the 5G core network (which may be appropriately modified in some cases) so that the MEC router 308 knows the 5G core network's requirements for quality of service, among other information. The policy information also includes policy information indicating that it establishes a data path with the target access network. It should be noted that the number of routers 308 may be one or more.

In some examples, the determined MEC router is still the MEC router in use in the UE 300 data path prior to the handover. In this case, the policy information sent by the MEC network control platform 305 includes a handover instruction of the UE 300, that is, the MEC router is instructed to release the data path with the source 5G radio access network S-NG-RAN301 and establish the data path with the target 5G radio access network T-NG-RAN 302.

In still other examples, the determined MEC router is a new MEC router, i.e., a MEC router not in use prior to the switchover. In this case, the policy information issued by the MEC network control platform 305 is transmitted to the new MEC router to indicate its data path with the target 5G radio access network T-NG-RAN 302. Meanwhile, the MEC network control platform 305 issues a handover instruction to the MEC router in use before handover, instructing it to release the data path with the source 5G radio access network S-NG-RAN 301.

In step S412, the router 308 that receives the policy information issued by the MEC network platform 305 sends a response message to the MEC network platform 305. In this regard, in some examples, the old router, i.e., the MEC router that received the handover indication of the UE 300, sends an N3 end marker to the source 5G radio access network S-NG-RAN301, as shown in step S413.

At step S414, the source 5G radio access network S-NG-RAN sends an N3 end marker to the target 5G radio access network T-NG-RAN 302 after receiving the N3 end marker.

At step S415, SMF304 replies a PDU session update response to AMF 303 to indicate that the PDU session is updated.

The AMF 303 sends an N2 path switch request acknowledgement to the target 5G radio access network T-NG-RAN 302 at step S416.

At step S417, the target 5G radio access network T-NG-RAN 302 sends a resource release message to the source 5G radio access network S-NG-RAN301 to release the resources occupied before the handover of the UE 300.

According to the examples of the method for switching a multi-operation scenario for a multi-access edge computing system described in the present application, since the MEC system performs authorization check after receiving an N4 session modification request sent by an SMF, the MEC system ensures the security of service switching to a certain extent; the method has the advantages that resources such as MEC routers and APPs in the MEC system are queried, and the MEC routers involved in switching are confirmed in the queried MEC routers, so that the availability of the routers and the resources is confirmed before switching, and compared with direct switching in a blind manner, the success rate after service switching is ensured, and the reliability and the continuity of execution after service switching are ensured. Further, after confirming the involved router, according to the present application, the MEC router is further notified to establish a data path with the target NG RAN, and when the involved MEC router is a router used before handover, the MEC router is first notified to release the data path of the source NG RAN. In summary, according to the core network of the present application and the architecture of the MEC, when the MEC is docked with the 5G core networks of different operators, the communication architecture and mechanism inside the MEC can meet the service continuity guarantee when the users from the external operators are switched in terms of security and policy management, which is helpful for the fact that the MEC access network and the internet service cannot be deeply integrated.

According to an example of the present application, a communication device is also provided. The communication device is configured to be able to perform a method of switching multiple operational scenarios as described in different examples of the present application. The communication device may be implemented in software modules, or in a combination of software and hardware, in existing devices having a communication interface.

According to an example of the present application, there is also provided yet another communication device comprising a processor and a storage module having instructions stored therein. When these instructions are executed by a processor of the communication device, the method of switching multiple operational scenarios according to examples of the present application may be implemented.

Fig. 5 is an interaction flowchart of a 5G core network and an MEC system at UE handover according to an example of the present application. As shown in the figure, in step S50, the MEC system subscribes to the location information of the UE from the 5G core network, and specifically, the MEC orchestrator in the MEC system subscribes to the location information of the UE from the AMF through the network open function NEF in the 5G core network. When the AMF detects that the condition notified by the MEC system is satisfied (i.e. the location of the UE changes, such as going online, switching, going offline, etc.), the AMF sends a notification to the NEF, where the notification includes the location information of the UE, as shown in step S52. At step S54, the NEF forwards the received notification further to the MEC system level, in particular to the MEC orchestrator at the MEC system level. At step S56, the MEC system level relocates the user 'S context and/or application instance from the old MEC host to the new MEC host according to the UE' S location information. At step S56, the MEC system level releases the occupied application resources on the old MEC hosts to continue to provide the optimized service experience for the user.

In the examples of the present application, the MEC system level may also be referred to as an MEC system layer, and the MEC host level may also be referred to as an MEC host layer.

In addition, in each example of the present application, a 5G network is used for communication of a network, but the method, system, device, and the like of the present application can be applied to a network based on a sixth generation mobile communication standard, and are not excluded from being applied to a network based on other communication standards.

Various examples of the present application have been set forth in conjunction with the accompanying drawings, and the examples and embodiments above are meant to be illustrative only and not limiting. It will be apparent to those skilled in the art that various changes and modifications can be made without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

1. A method for multi-operational scenario switching based on a multi-access edge computing system, the method comprising:

the multi-access edge computing system receives a first request sent by a session management function unit to request to modify an N4 session, wherein the first request comprises PDU session identification, user terminal position information and QoS information;

the multi-access edge computing system performs authorization check on the first request, and queries a host-level subsystem arranged in the multi-access edge computing system based on information included in the first request when the authorization check is passed;

the multi-access edge computing system determines a new router in the multi-access edge computing system involved in the user terminal switching scenario, wherein the new router is located in the queried host;

the multi-access edge computing system issues an N4 session modification to respond to the first request.

2. The method of claim 1, further comprising:

the multi-access edge computing system sends out policy information to instruct the new router to establish a data path with a target access network.

3. The method of claim 2, further comprising:

when the new router adopts the multi-access edge computing router which is used before the switching, the multi-access edge computing system instructs the new router to release the data path with the source access network and establish the data path with the target access network.

4. The method of claim 2, further comprising:

the new router sends an N3 end marker to the source access network.

5. The method of claim 4, further comprising:

and after receiving the N3 end mark, the source access network sends the N3 end mark to the target access network.

6. The method of claim 5, wherein the session management function receives a PDU session update request sent by an Access and mobility management function before sending the first request, wherein the PDU session update request is sent by the target access network to the Access and mobility management function after the handover preparation of the UE, the source access network, and the target access network is completed.

7. The method of claim 6, further comprising:

and the session management functional unit responds to the PDU session updating request after the source access network sends an N3 end mark to the target access network.

8. The method according to any one of claims 1 to 7, further comprising:

the multi-access edge computing system formulates a distribution strategy rule and issues the formulated distribution strategy rule to a related multi-access edge computing router, so that the multi-access edge computing router forwards an uplink data packet sent by a user terminal to an appointed path according to the distribution strategy rule.

9. The method of claim 8, further comprising:

the multi-access edge computing system inserts or deletes the router supporting the shunting policy rule on the data path according to the requirement.

10. A communication device, characterized in that the communication device is configured to perform the method of any of claims 1 to 9.

11. A communication device, characterized in that the communication device comprises a storage module storing instructions and a processing module configured to be able to execute the instructions and when executing the instructions implement the method according to any one of claims 1 to 9.

12. A multiple access edge computing system, the system comprising:

a communication interface for receiving a first request sent by a session management function unit to request modification of an N4 session, the first request including a PDU session identification, user terminal location information and QoS information;

a UPF proxy module configured to:

performing authorization check on the first request, and interacting with a multi-access edge computing system orchestrator to query a host-level subsystem set in the multi-access edge computing system based on information included in the first request if the authorization check passes;

determining a new router in a multi-access edge computing system involved in the user terminal switching scenario, the new router being located in the queried host-level subsystem; and

a response to the N4 session modification is sent to the session management function.

13. The multiple access edge computing system of claim 12, wherein the system further comprises a DN controller configured to: and formulating a distribution strategy rule and issuing the formulated distribution strategy rule to a related multi-access edge computing router so that the multi-access edge computing router forwards an uplink data packet sent by a user terminal to an appointed path according to the distribution strategy rule.

14. The multi-access edge computing system of claim 13, wherein the DN controller is configured to insert or delete routers on a data path that support offload policy rules as needed.