CN110545333A

CN110545333A - message processing method and device and network system

Info

Publication number: CN110545333A
Application number: CN201810521601.5A
Authority: CN
Inventors: 吴鹏程
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2018-05-28
Filing date: 2018-05-28
Publication date: 2019-12-06
Anticipated expiration: 2038-05-28
Also published as: CN110545333B

Abstract

the application discloses a message processing method, a message processing device and a network system, which are used for processing a DNS request message according to a pre-configured DNS rule, so that the DNS request message can be shunted, and thus, the network transmission load is reduced and the network transmission delay is reduced. The method provided by the application comprises the following steps: acquiring a Domain Name System (DNS) request message sent by User Equipment (UE); and processing the DNS request message according to a preset DNS rule list.

Description

message processing method and device and network system

Technical Field

the present application relates to the field of communications technologies, and in particular, to a message processing method and apparatus, and a network system.

background

In the existing network architecture, referring to fig. 1, a Mobile Edge Computing (MEC) service platform is deployed behind a core network (SAE-GW, or 5 GC). Through MEC technology, a service platform may be deployed near a mobile edge. As shown in fig. 1, an MEC server (mobile edge host) is connected to a base station and a mobile edge application, and is deployed in the same network layer (near the mobile edge); the mobile edge host is connected with an Evolved Packet Core (EPC) through a transmission network (such as a PTN network); the EPC and the remote service servers thereafter are deployed at a higher network level (e.g., core room). The service is divided into a mobile edge application and a far-end service application according to the actual deployment position of the service platform, wherein the far-end service application means non-local deployment relative to local; the mobile edge application is deployed on a mobile edge host.

At present, a Domain Name System (DNS) request message is routed through a core network and reaches a terminal, the core network has a large load, and the terminal has a long time delay for accessing related content, and the characteristics of high bandwidth and low time delay of an MEC service platform are not utilized.

disclosure of Invention

The embodiment of the application provides a message processing method, a message processing device and a network system, which are used for processing a DNS request message according to a preset DNS rule (rule), so that the DNS request message can be shunted, and thus, the network transmission load is reduced and the network transmission delay is reduced.

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

acquiring a Domain Name System (DNS) request message sent by User Equipment (UE);

And processing the DNS request message according to a preset DNS rule list.

According to the method, the domain name system DNS request message sent by the user equipment UE is obtained, and the DNS request message is processed according to the preset DNS rule list, so that the DNS request message can be shunted, for example, the DNS request message can be directly shunted to a local content server without passing through a core network, and therefore, the network transmission load is reduced and the network transmission delay is reduced.

Optionally, the DNS rule list includes at least one DNS rule, and each DNS rule includes the following contents:

Index, domain name, IP type of content server, IP address of content server, life cycle of DNS rule, status of DNS rule.

optionally, for each DNS rule in the DNS rule list, if the time for which the DNS rule exists is longer than a preset life cycle, the state of the DNS rule is an inactive state, and otherwise, the DNS rule is an active state.

optionally, processing the DNS request message according to a preset DNS rule list specifically includes:

And querying whether a preset DNS rule list has a domain name carried in the DNS request message, if so, querying the state of the DNS rule corresponding to the domain name, and if the state of the DNS rule corresponding to the domain name is an activated state, constructing a DNS response message by taking the IP type and the IP address of the content server corresponding to the domain name, and returning the DNS response message to the UE.

optionally, processing the DNS request message according to a preset DNS rule list, further includes:

And if the domain name carried in the DNS request message does not exist in a preset DNS rule list, or if the state of the DNS rule corresponding to the domain name is an inactivated state, sending the DNS request message to a core network.

Inquiring whether a preset DNS rule list has a domain name carried in the DNS request message, and sending the DNS request message to a core network;

If the domain name carried in the DNS request message exists in a preset DNS rule list, inquiring the state of the DNS rule corresponding to the domain name, and if the state of the DNS rule corresponding to the domain name is an activated state, constructing a DNS response message by taking the IP type and the IP address of the content server corresponding to the domain name and returning the DNS response message to the UE;

If the domain name carried in the DNS request message does not exist in the preset DNS rule list, or if the state of the DNS rule corresponding to the domain name is an inactive state, returning a DNS response message to the DNS request message returned by the core network to the UE.

Optionally, the method further comprises:

and receiving and storing the DNS rule list configured and sent by the application APP server.

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

The system comprises a TOF module, a domain name system DNS request message and a domain name system DNS request message, wherein the domain name system DNS request message is sent by User Equipment (UE);

And the DAM module is used for processing the DNS request message according to a preset DNS rule list.

Optionally, the DAM module is specifically configured to: and querying whether a preset DNS rule list has a domain name carried in the DNS request message, if so, querying the state of the DNS rule corresponding to the domain name, and if the state of the DNS rule corresponding to the domain name is an activated state, constructing a DNS response message by taking the IP type and the IP address of the content server corresponding to the domain name, and returning the DNS response message to the UE.

Optionally, the DAM module is further configured to: if the domain name carried in the DNS request message does not exist in a preset DNS rule list, or if the state of the DNS rule corresponding to the domain name is an inactivated state, sending the DNS request message and a failure indication to the TOF module;

the TOF module is further to: and when receiving a failure indication sent by the DAM module and the DNS request message, sending the DNS request message to a core network.

Optionally, after acquiring the DNS request message, the TOF module sends the DNS request message to the DAM module and the core network;

the DAM module is specifically configured to: inquiring whether a domain name carried in the DNS request message exists in a preset DNS rule list, if the domain name carried in the DNS request message exists in the preset DNS rule list, inquiring the state of the DNS rule corresponding to the domain name, and if the state of the DNS rule corresponding to the domain name is an activated state, constructing a DNS response message by taking the IP type and the IP address of a content server corresponding to the domain name, and returning the DNS response message and a success indication to the TOF module; if the domain name carried in the DNS request message does not exist in a preset DNS rule list, or if the state of the DNS rule corresponding to the domain name is an inactivated state, sending a failure indication aiming at the DNS request message to the TOF module;

The TOF module is further to: intercepting a DNS response message which is returned by the core network and aims at the DNS request message, and sending the DNS response message sent by the DAM module to the UE when the DNS response message sent by the DAM module and a success indication are received; and when the failure indication sent by the DAM module is received, returning a DNS response message which is returned by the core network and aims at the DNS request message to the UE.

Optionally, the method further comprises:

and the SR module is used for receiving the DNS rule list configured and sent by the application APP server and sending the DNS rule list to the DAM module for storage.

another message processing apparatus provided in an embodiment of the present application includes:

a memory for storing program instructions;

and the processor is used for calling the program instructions stored in the memory and executing any one of the methods according to the obtained program.

A computer storage medium is provided in an embodiment of the present application, and stores computer-executable instructions for causing a computer to perform any one of the methods.

an embodiment of the present application provides a network system, including: any of the devices described herein.

optionally, the network system further includes: at least one access network device, and/or core network device, and/or APP server, connected to the apparatus.

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 a traffic data flow of a mobile edge host in the prior art;

Fig. 2 is a schematic structural diagram of an MEC provided in an embodiment of the present application;

fig. 3 is a schematic structural diagram of a network system according to an embodiment of the present application;

Fig. 4 is a schematic configuration flow diagram of a DNS rule list according to an embodiment of the present application;

fig. 5 is a schematic processing flow diagram of a DAM provided in an embodiment of the present application;

fig. 6 is a schematic diagram illustrating a processing flow of a DNS request message according to an embodiment of the present application;

Fig. 7 is a schematic diagram illustrating a processing flow of a DNS request message according to an embodiment of the present application;

Fig. 8 is a schematic diagram illustrating a processing flow of a DNS request message according to an embodiment of the present application;

Fig. 9 is a schematic flowchart of a message processing method according to an embodiment of the present application;

Fig. 10 is a schematic structural diagram of a message processing apparatus according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of another message processing apparatus according to an embodiment of the present application.

Detailed Description

In 4G LTE networks and 5G networks, there is a general demand for edge networks. Access to local services through the edge network results in "fog computing". How to configure a Domain Name System (DNS) rule (rule) for distribution, so that a local content server can be guided when a Domain Name address is accessed, thereby reducing network transmission load and network transmission delay.

The embodiment of the application provides a method and a device for shunting services according to a DNS. The DNS rule is issued to a Mobile Edge Computing (MEC) device by way of an Application Programming Interface (API), and the DNS request is processed by a certain rule. The effect of shunting the service according to the DNS rule is formed, that is, in the prior art, the DNS request message is sent to the core network, but in the embodiment of the present application, the DNS request message is intercepted and processed by the MEC mobile edge computing device between the base station and the core network. The technical scheme provided by the embodiment of the application can be widely applied to various scenes such as unmanned driving, digital libraries and the like. Specifically, the effect of MEC offloading is achieved through DNS operations. The MEC is located between the base station and the core network. The MEC is shunted to the content providing server in advance, and the MEC does not pass through a plurality of equipment routes of a core network and reaches the terminal, so that the time for the terminal to access the content is shortened, and the MEC has the characteristic of low time delay, and the characteristic of low time delay can be used for unmanned driving; meanwhile, the MEC transmits the content to the terminal at the front end, has the characteristic of high bandwidth and can be used for a digital library.

the message processing apparatus provided in the embodiment of the present application may be, for example, an MEC device (abbreviated as MEC), see fig. 2, and for example, include:

DAM Module (Domain Analysis Module): and the application component is deployed in the MEC and is responsible for storing DNS domain name rules, matching the rules and generating local DNS response.

a Transmit Offload (TOF) module: and the shunt execution component is used for the MEC and is responsible for intercepting and analyzing the shunt of the data packet.

An SR (Service Register) module, a Service registration component of the MEC, is responsible for registration of applications, RESTful (where REST refers to a set of architectural constraints and principles, and an application or design that satisfies these constraints and principles is RESTful) distribution and response of HyperText Transfer Protocol (HTTP) messages.

The network architecture provided in the embodiment of the present Application is shown in fig. 3, and includes UE, a base station (access network device), MEC, an Application (APP) server (APP for short), EPC, or NGC (core network device).

Referring to fig. 4, the process of pre-configuring the DNS rule list is as follows:

first, APP needs to be registered in SR, and APP is an application registered in SR and is used to obtain a service provided by MEC.

the APP needs to be registered in the SR, the APP performs registration by sending a registration request message to the SR, and the registration request message carries the address and the name of the APP; SR records the corresponding relation between the name and address of APP, and judges whether the APP user is legal, and the contract rule replies successful registration in the registration response; an irregularity replies to the registration failure in the registration response.

the APP issues a DNS rule list to the SR in the MEC, namely the APP configures the DNS rule, transmits the DNS rule to the SR, and the SR forwards the DNS rule to the DAM module for processing. The method comprises the following specific steps:

A DNS rule list is issued using the RESTful HTTP API form, defined as follows:

Uniform Resource Locator (URL):

{apiRoot}/{apiName}/{apiVersion}/applications/dns_rules/

The format is as follows: JSON

HTTP request mode: push (PUT).

the input parameters (parameters for transferring SR), that is, the contents in the JSON packet carried in the HTTP message, are used as input, and specifically are as follows:

parameter name	Whether it is necessary to select	Data type	Description of the meanings
				dnsRule	is that	DNSRule	Updated DNS redirection rules

TABLE 1

and the DNS is redirected, so that the set domain name is directly accessed to the IP address corresponding to the domain name without being analyzed by a DNS server.

The output parameters, that is, the content carried in the response message 200OK (agreement) message corresponding to the PUT request message in HTTP format, are returned to the PUT request sender, and the output parameters are specifically as follows:

TABLE 2

the DNS Rule comprises the following attributes:

TABLE 3

And the SR issues the configuration list of the DNS rule into a DAM component of the MEC. For example, if the SR determines that the APP configuring the DNS rule list is legitimate, the DNS rule list is forwarded to the DAM process.

The DAM treatment process is as follows:

The DAM searches according to a domain name (domainName), and if the DAM finds the domain name, the DAM updates the rule; if the DNS rule corresponding to the domain name is not found, the DNS rule corresponding to the domain name is newly written in the domain name management table, that is, a row of content, a specific DNS rule list, is added to the existing DNS rule list, for example, as shown in the following table 4:

TABLE 4

The management of the DNS rule list by the DAM includes: the life cycle of the DNS rule, calculating time from the completion of configuration, and if the configured time is greater than the life cycle, setting the information to be in an INACTIVE (INACTIVE) state; otherwise, the state is set as Activated (ACTIVE).

the process of the MEC for DNS request messages is as follows:

the method comprises the following steps:

And the TOF module analyzes the message received from the terminal UE, forwards the message to DAM processing if the message is a DNS request message, and waits for different processing of the processing result of the DAM.

Referring to fig. 5, the processing method of the DAM includes:

the DAM matches the DNS request message forwarded by the TOF, firstly queries whether the domain name contained in the DNS request message is in a DNS rule list, and if not, directly returns a failure indication to the TOF module and carries the original DNS request; if yes, further inquiring whether the state of the record is an activated state, and if not, directly returning a failure indication to the TOF module and carrying the original DNS request;

And if the table entry is in the activated state, constructing a DNS response message according to the IP address and the type in the table entry, returning a success indication to the TOF, and simultaneously carrying the constructed DNS response.

And the TOF receives the processing instruction message of the DAM module and judges success or failure. If the indication is successful, replying the carried DNS response message to the UE; if the DNS request message is a failure indication, the carried DNS request message is forwarded to a core network (EPC or 5GC) for processing.

Referring to fig. 6, the specific process is as follows:

presetting conditions, and successfully attaching the UE to a core network;

Step 1, UE sends DNS request to base station;

and 2, the base station sends the DNS request message to a core network, and the message is intercepted by a TOF module of the MEC.

And 3, the TOF analyzes the message format, and if the DNS request is found, the DNS request is forwarded to the DAM module for processing.

step 4, the DAM module receives the DNS request message, firstly queries whether the domain name exists, if so, then queries the status item corresponding to the index, and if so, then takes the IP type and IP address of the corresponding local server (corresponding to the domain name in a certain DNS, the local content server connected to the MEC) to construct the DNS response.

And 5, returning a success indication to the TOF module by the DAM module, and simultaneously carrying a DNS response message of the DAM group.

And 6, the TOF module receives a success indication returned by the TOF module, and then sends a DNS response message to the UE.

the flow of the DAM query failure, see fig. 7, is as follows:

presetting conditions, and successfully attaching the UE to a core network;

Step 11, UE sends DNS request to base station;

And step 12, the base station sends the DNS request message to a core network (EPC or 5GC), and the message is intercepted by a TOF module of the MEC.

And step 13, the TOF analyzes the message format, and if the DNS request is found, the DNS request is forwarded to the DAM module for processing. The TOF to the DAM adopt an internal message format, and the message comprises DNS request message content.

Step 14, the DAM module receives the DNS request message, first inquires that the domain name exists, if the domain name cannot be found, returns a failure indication to the TOF, and sends the original DNS request message to the TOF; if the domain name is found but the status list shows that the domain name is not activated, a failure indication is returned to the TOF, and an original DNS request message is sent to the TOF.

step 15, the DAM module returns a failure indication to the TOF module, together with the original DNS request message.

And step 16, the TOF module takes out the original DNS request message and sends the message to the core network EPC or 5 GC.

And step 17, the DNS response message is returned after the processing of the core network EPC or 5 GC.

Method two (in parallel with method one):

the TOF sends a DAM request to the DAM and the core network (EPC or 5GC) at the same time, collects two returned DNS responses for judgment, and determines which DNS response to return to the UE.

referring to fig. 8, another message processing flow is as follows:

Presetting conditions, and successfully attaching the UE to a core network;

Step 21, the UE sends a DNS request to a base station;

step 22, the base station sends the DNS request message to the core network (EPC or 5GC), and the TOF module of the MEC intercepts the message.

Step 23a, the TOF analyzes the message format, and if the DNS request is found, the TOF forwards the DNS request to the DAM module for processing. The TOF to the DAM adopt an internal message format, and the message comprises DNS request message content.

at step 23b, the TOF forwards the DNS request message to the core network (EPC or 5GC) at the same time.

While steps 23a and 23b are in progress, the DNS response to the request needs to be intercepted and blocked. That is, the MEC receives the response between the core network and the base station, and the response is not sent to the lower end, but is stored by the MEC for processing.

Step 24, the DAM module receives the DNS request message, first queries that the domain name exists, and if the table entry is found and the state of the table entry is displayed as activated, returns a success indication to the TOF, and sends a DNS response message to the TOF by grouping the IP type and the IP address in the table entry. Otherwise, a failure indication is returned (without returning the original DNS request).

In step 25a, the DAM module sends a processing result (success or failure) indication to the TOF module, and carries a DNS response message in case of the success indication.

in step 25b, the core network (EPC or 5GC) returns a DNS response message.

Step 26, if the DAM replies the DNS response and replies the success indication, determining that the DNS response message sent by the DAM needs to be replied to the UE, and discarding the DNS response message replied by the core network; otherwise, determining that the DNS response message replied by the core network needs to be replied to the UE.

step 27, the TOF returns a DNS response message to the UE through the base station, where the DNS response message needs to be replied to the UE.

In summary, referring to fig. 9, a message processing method provided in the embodiment of the present application includes:

S101, acquiring a Domain Name System (DNS) request message sent by User Equipment (UE);

s102, processing the DNS request message according to a preset DNS rule list.

For example, in table 4 above, each row of contents is a DNS rule.

that is, each DNS rule may be provided with a validity period, available during the validity period (i.e., in an active state), and unavailable beyond the validity period (i.e., in an inactive state).

That is, this method corresponds to the method one described above, as shown in the flow chart shown in fig. 6.

that is, this method corresponds to the method one described above, as shown in the flow chart shown in fig. 7.

that is, this method corresponds to the above-described method two, as shown in the flow shown in fig. 8.

Optionally, the method further comprises:

And receiving and storing the DNS rule list configured and sent by the application APP server. Such as the flow described above in connection with fig. 4.

correspondingly, referring to fig. 10, an embodiment of the present application provides a message processing apparatus, including:

The TOF module 31 is configured to obtain a domain name system DNS request message sent by the user equipment UE;

The DAM module 32 is configured to process the DNS request message according to a preset DNS rule list.

optionally, for example, as shown in fig. 2 or 3, further comprising:

Referring to fig. 11, another message processing apparatus provided in an embodiment of the present application includes:

a memory 41 for storing program instructions;

A processor 42 for calling program instructions stored in said memory to execute any of said methods in accordance with the obtained program.

an embodiment of the present application provides a network system, including: the device as described in any of the embodiments of the present application.

Optionally, the network system further includes: at least one access network device, and/or core network device, and/or APP server, connected to the apparatus. For example, as shown in fig. 3.

Any of the devices, units, modules, and the like provided in the embodiments of the present application may be a computing device, and the computing device 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.

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.

to sum up, the embodiment of the present Application provides a method for performing DNS rule list configuration and distribution by using an Application Programming Interface (API), and a system plans a flow and a processing method of the whole process. The method is applied to scenes of edge calculation application such as unmanned driving and digital libraries, and has wide application and wide coverage.

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 processing, the method comprising:

Processing the DNS request message according to a preset DNS rule list;

for each DNS rule in the DNS rule list, if the existing time of the DNS rule is longer than a preset life cycle, the state of the DNS rule is a non-activated state, otherwise, the DNS rule is an activated state;

processing the DNS request message according to a preset DNS rule list, specifically including:

Inquiring whether a domain name carried in the DNS request message exists in a preset DNS rule list, if so, inquiring the state of the DNS rule corresponding to the domain name, and if the state of the DNS rule corresponding to the domain name is an activated state, constructing a DNS response message by taking the IP type and the IP address of a content server corresponding to the domain name and returning the DNS response message to the UE;

2. the method of claim 1, wherein the list of DNS rules includes at least one DNS rule, and wherein each DNS rule includes the following:

3. The method according to claim 1, wherein the processing the DNS request message according to a preset DNS rule list specifically includes:

4. A method according to any one of claims 1 to 3, further comprising:

5. a message processing apparatus, comprising:

The DAM module is used for processing the DNS request message according to a preset DNS rule list;

The DAM module is specifically configured to: inquiring whether a domain name carried in the DNS request message exists in a preset DNS rule list, if so, inquiring the state of the DNS rule corresponding to the domain name, and if the state of the DNS rule corresponding to the domain name is an activated state, constructing a DNS response message by taking the IP type and the IP address of a content server corresponding to the domain name and returning the DNS response message to the UE; if the domain name carried in the DNS request message does not exist in a preset DNS rule list, or if the state of the DNS rule corresponding to the domain name is an inactivated state, sending the DNS request message and a failure indication to the TOF module;

6. the apparatus of claim 5, wherein the list of DNS rules comprises at least one DNS rule, and wherein each DNS rule comprises the following:

7. the apparatus of claim 5, wherein the TOF module sends the DNS request message to the DAM module and a core network after obtaining the DNS request message;

8. the apparatus of any one of claims 5 to 7, further comprising:

9. A message processing apparatus, comprising:

a memory for storing program instructions;

a processor for calling program instructions stored in said memory to execute the method of any of claims 1 to 4 in accordance with the obtained program.

10. 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 4.

11. A network system, comprising: the device of any one of claims 5 to 9.

12. the system of claim 11, further comprising: at least one access network device, and/or core network device, and/or APP server, connected to the apparatus.