CN112752253B

CN112752253B - Message transmission method and device

Info

Publication number: CN112752253B
Application number: CN201911047669.5A
Authority: CN
Inventors: 陶源; 侯云静; 王胡成
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2019-10-30
Filing date: 2019-10-30
Publication date: 2021-10-29
Anticipated expiration: 2039-10-30
Also published as: WO2021083054A1; CN112752253A

Abstract

The application discloses a message transmission method and a message transmission device, which are used for notifying a terminal of a new server address when the address of an MEC server and/or an MEC application server is changed. The message transmission method provided by the embodiment of the application comprises the following steps: receiving a trigger message; notifying the terminal of the new address of the mobile edge computing MEC related server based on the trigger message; wherein the MEC-related server comprises an MEC server and/or an MEC application server.

Description

Message transmission method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for transmitting a message.

Background

The Mobile Edge Computing (MEC) technology migrates the computing storage capacity and the business service capacity to the network edge, so that data does not need to be transmitted back to the cloud as far as possible, and the waiting time of the data to and from the cloud and the network cost are reduced. Based on the 5G distributed cloud infrastructure, a 5G user plane function module and 5G MEC nodes are constructed in an edge cloud mode, and the 5G MEC nodes provide MEC application platforms to achieve deployment and management capacity of third-party applications. A user may obtain services through the MEC application.

5G defines an application function, which sends an application function Request (AF Request) to a non-trusted domain (NEF) or to a trusted domain (PCF), wherein the AF Request contains a series of parameters such as a target Data Network Name (DNN), an application identification (APP ID), an N6 interface routing requirement, and an application location. The PCF generates Policy and Charging Control (PCC) rules for the target PDU Session (Session) service flow according to the information parameters provided by the AF in combination with its own Policy Control, and selects an appropriate UPF for it through the SMF. The MEC provides functions of application infrastructure resource orchestration, application instantiation, application rule configuration, and the like. Therefore, when the MEC is deployed in the 5G system, the MEC may also serve an Application Function role, interacting with the 5G system control plane Function module on behalf of applications deployed on the MEC.

Fig. 1 is an edge computing network architecture, and the main network functions are introduced as follows:

AMF: access and Mobility Management Function, registration, connection Management, and the like.

UPF: user Plan Function, User plane Function. An external PDU session node interconnected to the data network, message routing and forwarding.

SMF: session Management Function, Session Management Function. Session establishment, deletion, user plane selection and control, UE IP allocation and the like.

AF: application Function, Application Function. Interact with the 3GPP core network to provide services. Based on operator deployment, trusted AFs can interact directly with the relevant NFs, whereas untrusted AFs cannot interact directly with NFs, but should do so through NEFs using an external public framework.

PCF: policy Control Function, Policy Control Function. A unified policy framework is supported to manage network behavior, providing policy rules for control plane NF enforcement.

NRF: network connectivity Function, Network storage Function. Supporting a service discovery function.

UDM: unified Data Management, Unified Data Management. Information of the UE, such as subscription information, information that the PDU session has been established, is stored.

NEF: network Exposure Function, Network open Function. Providing for securely exposing services and capabilities provided by a 3GPP network to external network related functions.

UDR: unified Data Repository, Unified database UDR. Storage of subscription data, and retrieval of subscription data by the UDM FE. Storage of policy information, and retrieval of policy information by the PCF.

There are currently solutions at the relevant application layer. The availability of the UE to subscribe to the target MEC application server may be supported, e.g., the MEC application server is available for a certain time period and location. And supporting the application context and the UE context to be migrated to a new server when the current MEC application server is unavailable.

The UE can only know the availability of a specific MEC application server and when not available, the application context and the UE context are migrated to a new server, and the UE cannot immediately obtain the address information of the new server to ensure the continuity of its service. In addition, when the application layer does not support the function or the application layer function cannot be executed, the conventional problem cannot be solved.

Disclosure of Invention

The embodiment of the application provides a message transmission method and a message transmission device, which are used for notifying a terminal of a new server address when the address of an MEC server and/or an MEC application server is changed.

The message transmission method provided by the embodiment of the application comprises the following steps:

receiving a trigger message;

notifying the terminal of the new address of the mobile edge computing MEC related server based on the trigger message; wherein the MEC-related server comprises an MEC server and/or an MEC application server.

By the method, a trigger message is received; notifying the terminal of the new address of the mobile edge computing MEC related server based on the trigger message; the MEC related server comprises an MEC server and/or an MEC application server, so that when the address of the MEC server and/or the MEC application server is changed, the new server address can be notified to the terminal.

Optionally, the new address of the MEC related server is notified to the terminal through a protocol data unit PDU session modification procedure.

Optionally, when receiving an update message sent by a policy control function PCF entity and containing a policy and charging control PCC rule requested to be generated based on an application function AF entity, initiating, by a session management function SMF entity, the PDU session modification procedure;

or when receiving a change message which is sent by a Unified Data Management (UDM) entity and informs the SMF entity about MEC subscription information, the SMF entity initiates the PDU session modification process;

or, when receiving a response message to the notification information of the SMF entity, which contains MEC-related information and is sent by the AF entity, initiating, by the SMF entity, the PDU session modification procedure.

Optionally, the update message includes: an application identifier, an application new address, a terminal identifier and/or an address;

the change message includes: an application identifier, an application new address, a terminal identifier and/or an address;

the response message includes: an application identifier, an application new address, a terminal identifier and/or an address;

the PDU session modification command in the PDU session modification process comprises: application identification, application new address.

Optionally, any of the messages further includes N6 interface traffic routing information.

Optionally, the new address of the MEC related server is notified to the terminal through a terminal configuration modification process.

Optionally, when receiving an update message sent by a policy control function PCF entity and containing a new policy and charging control PCC rule generated based on an application function AF entity request, initiating, by an access and mobility management function AMF entity, the terminal configuration modification process;

or, when receiving a change message containing information notifying an access and mobility management function (AMF) entity about MEC subscription information sent by a Unified Data Management (UDM) entity, initiating a terminal configuration modification process by the AMF entity.

the terminal policy container or the terminal configuration update command in the terminal configuration modification process includes: application identification, application new address.

Correspondingly, on the side of sending the trigger message, another message transmission method provided in the embodiment of the present application includes:

determining a trigger message of a first network entity, wherein the trigger message is used for triggering a second network entity to inform a terminal of a new address of a server related to a Mobile Edge Computing (MEC); wherein the MEC-related server comprises an MEC server and/or an MEC application server;

and sending the trigger message of the first network entity to a second network entity.

Optionally, the triggering message is specifically configured to trigger the second network entity to notify the terminal of the new address of the MEC-related server through a protocol data unit PDU session modification process.

Alternatively,

the first network entity is a Policy Control Function (PCF) entity, the trigger message is an update message containing a new Policy and Charging Control (PCC) rule generated based on a request of an Application Function (AF) entity, and the second network entity is a Session Management Function (SMF) entity;

or, the first network entity is a unified data management UDM entity, the trigger message is a change message notifying an SMF entity about MEC subscription information, and the second network entity is an SMF entity;

or, the first network entity is an AF entity, the trigger message is a response message to the notification information of the SMF entity or the NEF entity, where the response message includes MEC-related information, and the second network entity is an SMF entity.

the response message includes: application identification, application new address, terminal identification and/or address.

Optionally, the triggering message is specifically used to trigger the second network entity to notify the terminal of the new address of the MEC-related server through a terminal configuration modification process.

Optionally, the first network entity is a policy control function PCF entity, the trigger message is an update message including a request for generating a new policy and charging control PCC rule based on an application function AF entity, and the second network entity is an access and mobility management function AMF entity;

or, the first network entity is a unified data management UDM entity, the trigger message is a change message notifying an access and mobility management function AMF entity of MEC subscription information, and the second network entity is an AMF entity.

the change message includes: application identification, application new address, terminal identification and/or address.

Correspondingly, on the terminal side, the message transmission method provided by the embodiment of the application includes:

receiving a new address notification of a Mobile Edge Computing (MEC) related server; wherein the MEC-related server comprises an MEC server and/or an MEC application server;

and sending a message to the MEC related server according to the new address of the MEC related server.

An embodiment of the present application provides a message transmission apparatus, including:

a receiving unit, configured to receive a trigger message;

a notification unit, configured to notify the terminal of a new address of the server related to the mobile edge computing MEC based on the trigger message; wherein the MEC-related server comprises an MEC server and/or an MEC application server.

a determining unit, configured to determine a trigger message of a first network entity, and configured to trigger a second network entity to notify a terminal of a new address of a server related to a mobile edge computing MEC; wherein the MEC-related server comprises an MEC server and/or an MEC application server;

and the sending unit is used for sending the trigger message of the first network entity to a second network entity.

a receiving unit, configured to receive a new address notification of a server related to the mobile edge computing MEC; wherein the MEC-related server comprises an MEC server and/or an MEC application server;

and the sending unit is used for sending a message to the MEC related server according to the new address of the MEC related server.

At a new address notification side of an MEC-related server, another message transmission apparatus provided in an embodiment of the present application includes:

a memory for storing program instructions;

a processor for calling the program instructions stored in the memory and executing according to the obtained program:

receiving a trigger message;

Optionally, the processor notifies the terminal of the new address of the MEC related server through a protocol data unit PDU session modification procedure.

Optionally, the apparatus is a session management function, SMF, entity, and the processor initiates the PDU session modification process when receiving an update message sent by a policy control function, PCF, entity that contains a policy and charging control, PCC, rule requested to be generated based on an application function, AF, entity;

or, the device is an SMF entity, and the processor initiates the PDU session modification process when receiving a change message which is sent by a unified data management UDM entity and informs the SMF entity of MEC subscription information;

or, the apparatus is an SMF entity, and the processor initiates the PDU session modification procedure when receiving a response message to the notification information of the SMF entity, which contains MEC-related information and is sent by an AF entity.

Optionally, the processor notifies the terminal of the new address of the MEC related server through a terminal configuration modification process.

Optionally, the apparatus is an access and mobility management function, AMF, entity, and the processor initiates the terminal configuration modification process when receiving an update message sent by a policy control function, PCF, entity and containing a new policy and charging control, PCC, rule generated based on an application function, AF, entity request;

or, the device is an AMF entity, and the processor initiates a terminal configuration modification process when receiving a change message which is sent by a unified data management UDM entity and contains information notifying an access and mobility management function AMF entity about MEC subscription information.

At a trigger message sending side, another message transmission apparatus provided in an embodiment of the present application includes:

a memory for storing program instructions;

Alternatively,

At a terminal side, another message transmission apparatus provided in an embodiment of the present application includes:

a memory for storing program instructions;

Another embodiment of the present application provides a computer storage medium having stored thereon computer-executable instructions for causing a computer to perform any one of the methods described above.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a schematic diagram of an edge computing network architecture according to an embodiment of the present application;

fig. 2 is a schematic flow chart of an information transmission method according to an embodiment of the present application;

fig. 3 is a schematic flow chart of an information transmission method according to an embodiment of the present application;

fig. 4 is a schematic flow chart of an information transmission method according to an embodiment of the present application;

fig. 5 is a schematic flow chart of an information transmission method according to an embodiment of the present application;

fig. 6 is a schematic flow chart of an information transmission method according to an embodiment of the present application;

fig. 7 is a schematic flowchart of a message transmission method provided by any network entity in the embodiment of the present application;

fig. 8 is a schematic flowchart of a message transmission method provided by a sending side of a trigger message according to an embodiment of the present application;

fig. 9 is a flowchart illustrating a message transmission method provided by a terminal side according to an embodiment of the present application

Fig. 10 is a schematic structural diagram of a message transmission apparatus provided in any network entity side of the embodiment of the present application;

fig. 11 is a schematic structural diagram of a message transmission apparatus provided at a sending side of a trigger message according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of a message transmission apparatus provided at a terminal side according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of another message transmission apparatus provided in any network entity side of the embodiment of the present application;

fig. 14 is a schematic structural diagram of another message transmission apparatus provided on a sending side of a trigger message according to an embodiment of the present application;

fig. 15 is a schematic structural diagram of another message transmission apparatus provided at a terminal side according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The method and the device are based on the same application concept, and because the principles of solving the problems of the method and the device are similar, the implementation of the device and the method can be mutually referred, and repeated parts are not repeated.

The technical scheme provided by the embodiment of the application can be suitable for various systems, particularly 5G systems. For example, the applicable system may be a global system for mobile communication (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS) system, a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), a universal microwave Access (WiMAX) system, a 5G NR system, and the like. These various systems include terminal devices and network devices.

The terminal device referred to in the embodiments of the present application may refer to a device providing voice and/or data connectivity to a user, a handheld device having a wireless connection function, or other processing device connected to a wireless modem. The names of the terminal devices may also be different in different systems, for example, in a 5G system, the terminal devices may be referred to as User Equipments (UEs). Wireless terminal devices, which may be mobile terminal devices such as mobile telephones (or "cellular" telephones) and computers with mobile terminal devices, e.g., mobile devices that may be portable, pocket, hand-held, computer-included, or vehicle-mounted, communicate with one or more core networks via the RAN. Examples of such devices include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), and the like. The wireless terminal device may also be referred to as a system, a subscriber unit (subscriber unit), a subscriber station (subscriber station), a mobile station (mobile), a remote station (remote station), an access point (access point), a remote terminal device (remote terminal), an access terminal device (access terminal), a user terminal device (user terminal), a user agent (user agent), and a user device (user device), which are not limited in this embodiment of the present application.

The network device according to the embodiment of the present application may be a base station, and the base station may include a plurality of cells. A base station may also be referred to as an access point, or a device in an access network that communicates over the air-interface, through one or more sectors, with wireless terminal devices, or by other names, depending on the particular application. The network device may be configured to interconvert received air frames with Internet Protocol (IP) packets as a router between the wireless terminal device and the rest of the access network, which may include an Internet Protocol (IP) communication network. The network device may also coordinate attribute management for the air interface. For example, the network device according to the embodiment of the present application may be a Base Transceiver Station (BTS) in a global system for mobile communications (GSM) or a Code Division Multiple Access (CDMA), may also be a network device (NodeB) in a Wideband Code Division Multiple Access (WCDMA), may also be an evolved network device (eNB or e-NodeB) in a long term evolution (long term evolution, LTE) system, a 5G base station in a system (next generation system) including a 5G network architecture, may also be a home evolved node B (HeNB), a relay node (relay node), a home base station (femto), a pico base station (pico) and the like, which are not limited in the embodiments of the present application.

Various embodiments of the present application will be described in detail below with reference to the accompanying drawings. It should be noted that the display sequence of the embodiment of the present application only represents the sequence of the embodiment, and does not represent the merits of the technical solutions provided by the embodiments.

When the UE communicates with the MEC application, the address of the MEC server and/or the MEC application server may change, for example, due to the MEC server being unavailable, the MEC application server migrating to the cloud or other MEC servers, the application deployment changes within the MEC application server, and the like. In order to guarantee the continuity of the service, the MEC needs to notify the UE of a new address of the MEC server and/or MEC application server that can provide the same service, and a solution of how to notify this information is provided in the following embodiments.

Example one

The present embodiment describes that the PCF generates a new PCC rule update to the SMF based on the AF request (request), and the SMF initiates PDU session modification to notify the UE of the new address of the MEC server and/or MEC application server.

Referring to fig. 2, the information transmission method provided in this embodiment includes the following steps:

200. the MEC server and/or MEC application server address changes, e.g., MEC application server (app server) migrates to the cloud or other MEC server, application deployment changes within the MEC application server, etc., due to MEC server unavailability.

201. The AF creates a request message by calling a first operation instruction Nnef traffic Create service operation.

The request message contains one or a combination of the following contents: the corresponding relationship between the application identification (list), the application new address (list), the UE identification/address (list), and the N6 interface traffic routing information, wherein the N6 interface traffic routing information at least includes one of the following parameters: app ID, New IP (New IP), UE ID/UE IP, N6 interface traffic routing information (traffic routing info). Wherein each parameter can be in one-to-one or one-to-many relationship. For example, if the addresses of the application 1 and the application 2 connected to the UE1 and the UE2 are changed to IP1, the corresponding relationship is { (app ID1, app ID2), new IP, (UE ID1, UE ID2), N6 traffic routing info }. These parameters are used to indicate that the address of the MEC server and/or MEC application server to which a particular UE is currently connected has changed, and a connection can be established with the server via the new address provided.

202. AF sends request information to NEF, NEF stores AF request to UDR, PCF subscribes change of AF request to UDR, and obtains information of AF request from notice information. Or the AF sends the information directly to the PCF.

203. And the PCF generates a new PCC rule according to the AF request and updates the new PCC rule to the SMF.

204. The PCF sends the PCC rule to the SMF by invoking a second operation instruction Npcf _ SMPolicyControl _ UpdateNotify (PCF _ session management policy control update notification).

205. The SMF sends an N4 interface Session Modification Request (Session Modification Request) to the UPF, providing N6 interface traffic routing information. The UPF replies to the N4 interface Session Modification Response (Session Modification Response).

206. The SMF sends one or more PDU Session Modification commands (Session Modification Command) to the AMF according to the UE ID parameter in the received information, where the information includes parameters such as application identification, application new address, etc., and the parameters may be in a one-to-one or one-to-many relationship, for example, when different applications connected to the UE migrate to different application servers, the corresponding relationship between the parameters includes { (app ID1, new IP1), (app ID2, new IP2) }.

207. And the AMF sends a PDU Session Modification Command (carrying the application identifier and the new application address) to the corresponding UE.

208. And the UE sends information to the MEC according to the new server address.

Example two

The present embodiment describes that the PCF generates a new PCC rule update to the AMF based on the AF request, and the AMF initiates a UE configuration modification to notify the UE of the new address of the MEC server and/or MEC application server.

Referring to fig. 3, the information transmission method provided in this embodiment includes the following steps:

300. the MEC server and/or MEC application server address changes.

301. The AF creates a request message by calling the nff _ trafficlnflux _ Create service operation, where the message includes the corresponding relationship (app ID, new IP, UE ID/UE IP, N6 traffic routing info) between the application identifier (list), the new application address (list), the UE identifier/address (list), and the N6 interface traffic routing information, and each parameter may be in a one-to-one, one-to-many relationship. These parameters are used to indicate that the address of the MEC server and/or MEC application server to which a particular UE is currently connected has changed, and a connection can be established with the server via the new address provided.

302. The AF sends request information (by calling Nnef _ trafficinflluence _ Create/Update) to the NEF, which stores the AF request to the UDR, and the PCF subscribes to changes in the AF request to the UDR, obtaining information of the AF request from the notification information. Or the AF sends the information (including app ID, new IP, UE ID/UE IP) directly to the PCF.

It should be noted that, in this step, the AF may send the request message to the PCF directly or indirectly through interaction between the NEF and the UDR. In the indirect method, two entities, NEF and UDR, are provided between the AF and PCF (not shown in the figure).

303. The PCF calls a third operation command, Namf _ Communication _ N1N2message transfer, service operation, and sends information to the AMF, where the information includes UE ID and UE policy container, and the UE policy container includes a correspondence between application ID and new application address, for example, { (app ID1, new IP1), (app ID2, new IP2) }.

304. The AMF transparently transmits the received UE policy container (including app ID, new IP) to one or more UEs.

305. And the UE sends information to the MEC according to the new server address.

EXAMPLE III

This embodiment describes the UDM informing the SMF about the change of MEC subscription information, the SMF initiating a PDU session modification to inform the UE about the new address of the MEC server and/or MEC application server.

The prerequisites are: the UDM stores MEC related subscription information, e.g. server addresses.

Referring to fig. 4, the information transmission method provided in this embodiment includes the following steps:

400. the MEC server and/or MEC application server address changes. The MEC sends the information to the UDM through the NEF.

401. The UDM updates the subscription information of the MEC (updates the address of the MEC server and/or the MEC application server), and sends notification information of the MEC address change to the SMF, where the notification information includes the correspondence (app ID, new IP, UE ID/UE IP, N6 traffic routing info) between the application identifier (list), the new application address (list), the UE identifier/address (list), and the N6 interface traffic routing information, and each parameter may be one-to-one or one-to-many correspondence. These parameters are used to indicate that the address of the MEC server and/or MEC application server to which a particular UE is currently connected has changed, and a connection can be established with the server via the new address provided.

402. The SMF sends a N4 Session Modification Request (Session Modification Request) to the UPF, provides N6 interface traffic routing information, and the like. The UPF replies to the N4 Session Modification Response (Session Modification Response).

403. The SMF sends one or more PDU Session Modification commands (Session Modification Command) to the AMF, the message contains application identification and application new address, and the parameters can be in one-to-one or one-to-many correspondence.

404. And the AMF sends a PDU Session Modification Command (carrying the application identifier and the new application address) to the corresponding UE.

405. And the UE sends information to the MEC according to the new server address.

Example four

This embodiment describes that the UDM informs the AMF about the change of MEC subscription information, and the AMF initiates a UE configuration modification to inform the UE of the new address of the MEC server and/or MEC application server.

Referring to fig. 5, the information transmission method provided in this embodiment includes the following steps:

500. the MEC server and/or MEC application server address changes. The MEC sends the information to the UDM through the NEF.

501. The UDM updates the subscription information of the MEC (updates the address of the MEC server and/or the MEC application server), and sends notification information of the MEC address change to the AMF, wherein the information includes the correspondence (app ID, new IP, UE ID/UE IP, N6 traffic routing info) between the application identifier (list), the new application address (list), the UE identifier/address (list), and the N6 interface traffic routing information, and each parameter may be one-to-one or one-to-many correspondence. These parameters are used to indicate that the address of the MEC server and/or MEC application server to which a particular UE is currently connected has changed, and a connection can be established with the server via the new address provided.

502. The AMF sends a UE Configuration Update Command (Configuration Update Command) to one or more UEs according to the received information, wherein the information comprises an application identifier and an application new address.

503. And the UE sends information to the MEC according to the new server address.

EXAMPLE five

This embodiment describes that the AF sends MEC related information to the SMF in response to the notification information of the SMF, and the SMF initiates PDU session modification to notify the UE of the new address of the MEC server and/or MEC application server.

Referring to fig. 6, the information transmission method provided in this embodiment includes the following steps:

601. the AF notification is triggered (e.g., the SMF receives notification request information of the AF) the SMF invokes a fourth operation instruction Nsmf _ EventExposure _ Notify (SMF _ eventexconsent _ notification) service operation, sends information to the NEF, the NEF triggers the Nsmf _ trafficinfifficience _ Notify notification AF, or the SMF directly invokes the Nsmf _ EventExposure _ Notify notification AF.

602. The AF replies to the information (directly sent to the SMF or sent to the SMF through the NEF) by calling a fifth operation instruction Nsmf _ EventExposure _ AppRelocation Info (SMF _ event trigger _ application relocation), where the information includes an application identifier (list), an application new address (list), and a correspondence (app ID, new IP, UE ID/UE IP) between UE identifiers/addresses (list), and each parameter may be a one-to-one, one-to-many correspondence. The address of the MEC server and/or MEC application server indicating that a particular UE is currently connected to changes, and a connection can be established with the server through the new address provided.

603. The SMF sends one or more PDU conversation Modification commands (Session Modification commands) to the AMF according to the UE ID parameters in the received information, wherein the information comprises application identification and application new address, and the parameters can be in one-to-one or one-to-many relationship.

604. And the AMF sends a PDU Session Modification Command (carrying the application identifier and the new application address) to the corresponding UE.

In summary, referring to fig. 7, in an arbitrary network entity, a message transmission method provided in an embodiment of the present application includes:

s101, receiving a trigger message;

s102, based on the trigger message, notifying a terminal of a new address of a server related to the mobile edge computing MEC; wherein the MEC-related server comprises an MEC server and/or an MEC application server.

Correspondingly, referring to fig. 8, on the sending side of the trigger message, another message transmission method provided in the embodiment of the present application includes:

s201, determining a trigger message of a first network entity, and triggering a second network entity to notify a terminal of a new address of a server related to a Mobile Edge Computing (MEC); wherein the MEC-related server comprises an MEC server and/or an MEC application server;

s202, sending the trigger message of the first network entity to a second network entity.

Alternatively,

Correspondingly, on the terminal side, referring to fig. 9, a message transmission method provided in an embodiment of the present application includes:

s301, receiving a new address notification of a server related to the mobile edge computing MEC; wherein the MEC-related server comprises an MEC server and/or an MEC application server;

s302, according to the new address of the MEC related server, sending a message to the MEC related server.

Correspondingly to the above method, referring to fig. 10, on any network node side, a message transmission apparatus provided in an embodiment of the present application includes:

a receiving unit 11, configured to receive a trigger message;

a notification unit 12, configured to notify the terminal of the new address of the server related to the mobile edge computing MEC based on the trigger message; wherein the MEC-related server comprises an MEC server and/or an MEC application server.

Referring to fig. 11, on the side of sending a trigger message, a message transmission apparatus provided in an embodiment of the present application includes:

a determining unit 21, configured to determine a trigger message of a first network entity, configured to trigger a second network entity to notify a terminal of a new address of a server related to a mobile edge computing MEC; wherein the MEC-related server comprises an MEC server and/or an MEC application server;

a sending unit 22, configured to send the trigger message of the first network entity to a second network entity.

Alternatively,

Referring to fig. 12, on the terminal side, a message transmission apparatus provided in an embodiment of the present application includes:

a receiving unit 31, configured to receive a new address notification of a mobile edge computing MEC-related server; wherein the MEC-related server comprises an MEC server and/or an MEC application server;

a sending unit 32, configured to send a message to the MEC-related server according to the new address of the MEC-related server.

It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation. In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

Referring to fig. 13, at any network node side, another message transmission apparatus provided in the embodiment of the present application includes:

the processor 500, which is used to read the program in the memory 520, executes the following processes:

receiving a trigger message;

Optionally, the processor 500 notifies the terminal of the new address of the MEC related server through a protocol data unit PDU session modification procedure.

Optionally, the apparatus is a session management function SMF entity, and the processor 500 initiates the PDU session modification process when receiving an update message sent by a policy control function PCF entity and containing a new policy and charging control PCC rule based on a request of an application function AF entity;

or, the apparatus is a session management function, SMF, entity, and the processor 500 initiates the PDU session modification process when receiving a change message, which is sent by a unified data management, UDM entity and informs the SMF entity of the MEC subscription information;

or, the apparatus is a session management function, SMF, entity, and the processor 500 initiates the PDU session modification process when receiving a response message to the notification information of the SMF entity, which contains MEC-related information and is sent by an AF entity.

Optionally, the processor 500 notifies the terminal of the new address of the MEC related server through a terminal configuration modification process.

Optionally, the apparatus is an access and mobility management function, AMF, entity, and the processor 500 initiates the terminal configuration modification process when receiving an update message sent by a policy control function, PCF, entity and containing a new policy and charging control, PCC, rule generated based on an application function, AF, entity request;

or, the apparatus is an AMF entity, and the processor 500 initiates a terminal configuration modification process when receiving a change message which is sent by a unified data management UDM entity and contains a notification about MEC subscription information of an AMF entity having an access and mobility management function.

A transceiver 510 for receiving and transmitting data under the control of the processor 500.

Where in fig. 13, the bus architecture may include any number of interconnected buses and bridges, with various circuits being linked together, particularly one or more processors represented by processor 500 and memory represented by memory 520. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 510 may be a number of elements, including a transmitter and a transceiver, providing a means for communicating with various other apparatus over a transmission medium. The processor 500 is responsible for managing the bus architecture and general processing, and the memory 520 may store data used by the processor 500 in performing operations.

The processor 500 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or a Complex Programmable Logic Device (CPLD).

Referring to fig. 14, on the side of sending a trigger message, another message transmission apparatus provided in the embodiment of the present application includes:

a processor 504, configured to read the program in the memory 505, and execute the following processes:

Alternatively,

A transceiver 501 for receiving and transmitting data under the control of a processor 504.

In FIG. 14, a bus architecture (represented by bus 506), the bus 506 may include any number of interconnected buses and bridges, with the bus 506 linking together various circuits including one or more processors, represented by the processor 504, and memory, represented by the memory 505. The bus 500 may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. A bus interface 503 provides an interface between the bus 506 and the transceiver 501. The transceiver 501 may be one element or may be multiple elements, such as multiple receivers and transmitters, providing a means for communicating with various other apparatus over a transmission medium. Data processed by processor 504 is transmitted over a wireless medium via antenna 502, and further, antenna 502 receives data and transmits data to processor 504.

The processor 504 is responsible for managing the bus 506 and general processing, and may also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And memory 505 may be used to store data used by processor 504 in performing operations.

Alternatively, the processor 504 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a CPLD (Complex Programmable Logic Device).

Referring to fig. 15, on the terminal side, another message transmission apparatus provided in the embodiment of the present application includes:

the processor 600, which is used to read the program in the memory 620, executes the following processes:

A transceiver 610 for receiving and transmitting data under the control of the processor 600.

Where in fig. 15, the bus architecture may include any number of interconnected buses and bridges, with various circuits being linked together, particularly one or more processors represented by processor 600 and memory represented by memory 620. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 610 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium. For different user devices, the user interface 630 may also be an interface capable of interfacing with a desired device externally, including but not limited to a keypad, display, speaker, microphone, joystick, etc.

The processor 600 is responsible for managing the bus architecture and general processing, and the memory 620 may store data used by the processor 600 in performing operations.

Alternatively, the processor 600 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a CPLD (Complex Programmable Logic Device).

The embodiment of the present application provides a computing device, which may specifically be a desktop computer, a portable computer, a smart phone, a tablet computer, a Personal Digital Assistant (PDA), and the like. The computing device may include a Central Processing Unit (CPU), memory, input/output devices, etc., the input devices may include a keyboard, mouse, touch screen, etc., and the output devices may include a Display device, such as a Liquid Crystal Display (LCD), a Cathode Ray Tube (CRT), etc.

The memory may include Read Only Memory (ROM) and Random Access Memory (RAM), and provides the processor with program instructions and data stored in the memory. In the embodiments of the present application, the memory may be used for storing a program of any one of the methods provided by the embodiments of the present application.

The processor is used for executing any one of the methods provided by the embodiment of the application according to the obtained program instructions by calling the program instructions stored in the memory.

Embodiments of the present application provide a computer storage medium for storing computer program instructions for an apparatus provided in the embodiments of the present application, which includes a program for executing any one of the methods provided in the embodiments of the present application.

The computer storage media may be any available media or data storage device that can be accessed by a computer, including, but not limited to, magnetic memory (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical memory (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor memory (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND FLASH), Solid State Disks (SSDs)), etc.

The method provided by the embodiment of the application can be applied to terminal equipment and also can be applied to network equipment.

The Terminal device may also be referred to as a User Equipment (User Equipment, abbreviated as "UE"), a Mobile Station (Mobile Station, abbreviated as "MS"), a Mobile Terminal (Mobile Terminal), or the like, and optionally, the Terminal may have a capability of communicating with one or more core networks through a Radio Access Network (RAN), for example, the Terminal may be a Mobile phone (or referred to as a "cellular" phone), a computer with Mobile property, or the like, and for example, the Terminal may also be a portable, pocket, hand-held, computer-built-in, or vehicle-mounted Mobile device.

A network device may be a base station (e.g., access point) that refers to a device in an access network that communicates over the air-interface, through one or more sectors, with wireless terminals. The base station may be configured to interconvert received air frames and IP packets as a router between the wireless terminal and the rest of the access network, which may include an Internet Protocol (IP) network. The base station may also coordinate management of attributes for the air interface. For example, the Base Station may be a Base Transceiver Station (BTS) in GSM or CDMA, a Base Station (NodeB) in WCDMA, an evolved Node B (NodeB or eNB or e-NodeB) in LTE, or a gNB in 5G system. The embodiments of the present application are not limited.

The above method process flow may be implemented by a software program, which may be stored in a storage medium, and when the stored software program is called, the above method steps are performed.

To sum up, in the embodiment of the present application, the AF sends an AF request for indicating that the address of the MEC server and/or the MEC application server to which the specific UE is currently connected changes, and a connection can be established with the server through the provided new address. The AF request includes an application identifier, an application new address, a UE identifier/address, and N6 interface traffic routing information. And the UDM sends notification information of MEC address change to the SMF, wherein the information comprises an application identifier, an application new address and a UE identifier/address. And the AF replies an application relocation response of the SMF notification, wherein the information comprises an application identifier, an application new address and a UE identifier/address. And the SMF initiates PDU session modification and informs the UE of the application identification and the application new address. And the AMF initiates the UE configuration modification and informs the UE of the application identification and the application new address. Therefore, the method and the device for processing the address change of the edge computing server solve the problem of supporting the address change of the edge computing server.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A method for message transmission, the method comprising:

receiving a trigger message;

notifying the terminal of the new address of the mobile edge computing MEC related server based on the trigger message; wherein the MEC-related server comprises an MEC server and/or an MEC application server; a new address of the MEC related server, a notification from the MEC related server or an Application Function (AF) entity;

the notifying the terminal of the new address of the server related to the mobile edge computing MEC specifically includes:

the first method is as follows: notifying the new address of the MEC related server to a terminal through a Protocol Data Unit (PDU) session modification process;

when receiving an update message which is sent by a Policy Control Function (PCF) entity and contains a Policy and Charging Control (PCC) rule requested to be generated based on an Application Function (AF) entity, a Session Management Function (SMF) entity initiates a PDU session modification process;

or, when receiving a response message to the notification information of the SMF entity or the NEF entity, which contains MEC-related information and is sent by the AF entity, initiating the PDU session modification process by the SMF entity;

the update message includes: an application identifier, an application new address, a terminal identifier and/or an address;

the PDU session modification command in the PDU session modification process comprises: an application identifier and an application new address;

the second method comprises the following steps: notifying the new address of the MEC related server to the terminal through a terminal configuration modification process;

when receiving an update message which is sent by a Policy Control Function (PCF) entity and contains a new Policy and Charging Control (PCC) rule generated based on a request of an Application Function (AF) entity, initiating a terminal configuration modification process by an access and mobility management function (AMF) entity;

or when receiving a change message which is sent by a Unified Data Management (UDM) entity and contains information notifying an access and mobility management function (AMF) entity about MEC subscription information, initiating a terminal configuration modification process by the AMF entity;

2. The method of claim 1, wherein in mode one, any of the messages further includes N6 interface traffic routing information.

3. A method for message transmission, the method comprising:

determining a trigger message of a first network entity, wherein the trigger message is used for triggering a second network entity to inform a terminal of a new address of a server related to a Mobile Edge Computing (MEC); wherein the MEC-related server comprises an MEC server and/or an MEC application server; a new address of the MEC related server, a notification from the MEC related server or an Application Function (AF) entity;

sending the trigger message of the first network entity to a second network entity; wherein the content of the first and second substances,

the first method is as follows: the triggering message is specifically used for triggering a second network entity to notify a terminal of a new address of the MEC-related server through a Protocol Data Unit (PDU) session modification process;

or, the first network entity is an AF entity, the trigger message is a response message to the notification information of the SMF entity or the NEF entity, the response message including MEC-related information, and the second network entity is an SMF entity;

the second method comprises the following steps: the triggering message is specifically used for triggering a second network entity to notify the terminal of a new address of the MEC-related server through a terminal configuration modification process;

the first network entity is a Policy Control Function (PCF) entity, the trigger message is an update message containing a Policy and Charging Control (PCC) rule requested to be generated based on an Application Function (AF) entity, and the second network entity is an access and mobility management function (AMF) entity;

or, the first network entity is a Unified Data Management (UDM) entity, the trigger message is a change message for notifying an access and mobility management function (AMF) entity of MEC subscription information, and the second network entity is an AMF entity;

4. The method of claim 3, wherein in mode one, any of the messages further comprises N6 interface traffic routing information.

5. A method for message transmission, comprising:

receiving a new address notification of a Mobile Edge Computing (MEC) related server; wherein the MEC-related server comprises an MEC server and/or an MEC application server; a new address of the MEC related server, a notification from the MEC related server or an Application Function (AF) entity;

sending a message to the MEC related server according to the new address of the MEC related server;

wherein, the new address of the MEC related server is notified to the terminal by the network side in one of the following ways:

6. A message transmission apparatus, comprising:

a receiving unit, configured to receive a trigger message;

a notification unit, configured to notify the terminal of a new address of the server related to the mobile edge computing MEC based on the trigger message; wherein the MEC-related server comprises an MEC server and/or an MEC application server; a new address of the MEC related server, a notification from the MEC related server or an Application Function (AF) entity;

7. A message transmission apparatus, comprising:

a determining unit, configured to determine a trigger message of a first network entity, and configured to trigger a second network entity to notify a terminal of a new address of a server related to a mobile edge computing MEC; wherein the MEC-related server comprises an MEC server and/or an MEC application server; a new address of the MEC related server, a notification from the MEC related server or an Application Function (AF) entity;

a sending unit, configured to send the trigger message of the first network entity to a second network entity; wherein the content of the first and second substances,

8. A message transmission apparatus, comprising:

a receiving unit, configured to receive a new address notification of a server related to the mobile edge computing MEC; wherein the MEC-related server comprises an MEC server and/or an MEC application server; a new address of the MEC related server, a notification from the MEC related server or an Application Function (AF) entity;

a sending unit, configured to send a message to the MEC-related server according to the new address of the MEC-related server;

9. A message transmission apparatus, comprising:

a memory for storing program instructions;

receiving a trigger message;

wherein, the mode one: the processor informs a terminal of a new address of the MEC related server through a Protocol Data Unit (PDU) session modification process;

the device is a Session Management Function (SMF) entity, and the processor initiates the PDU session modification process when receiving an update message which is sent by a Policy Control Function (PCF) entity and contains a Policy and Charging Control (PCC) rule requested to be generated based on an Application Function (AF) entity;

or, the apparatus is an SMF entity, and the processor initiates the PDU session modification process when receiving a response message to the notification information of the SMF entity, which contains MEC-related information and is sent by an AF entity;

the second method comprises the following steps: the processor informs the new address of the MEC related server to the terminal through a terminal configuration modification process;

the device is an access and mobility management function (AMF) entity, and the processor initiates a terminal configuration modification process when receiving an update message which is sent by a Policy Control Function (PCF) entity and contains a new Policy and Charging Control (PCC) rule generated based on an Application Function (AF) entity request;

or, the device is an AMF entity, and the processor initiates a terminal configuration modification process when receiving a change message which is sent by a Unified Data Management (UDM) entity and contains information notifying an access and mobility management function (AMF) entity about MEC subscription information;

10. The apparatus according to claim 9, wherein in the first mode, any of the messages further includes N6 interface traffic routing information.

11. A message transmission apparatus, comprising:

a memory for storing program instructions;

sending the trigger message of the first network entity to a second network entity;

wherein, the mode one: the triggering message is specifically used for triggering a second network entity to notify a terminal of a new address of the MEC-related server through a Protocol Data Unit (PDU) session modification process;

12. The apparatus of claim 11, wherein in mode one, any of the messages further includes N6 interface traffic routing information.

13. A message transmission apparatus, comprising:

a memory for storing program instructions;

14. A computer storage medium having stored thereon computer-executable instructions for causing a computer to perform the method of any one of claims 1 to 5.