CN111669751A

CN111669751A - Data stream establishing method, device and communication system

Info

Publication number: CN111669751A
Application number: CN202010378562.5A
Authority: CN
Inventors: 吕华章; 张力方; 冯毅; 朱常波
Original assignee: China United Network Communications Group Co Ltd
Current assignee: China United Network Communications Group Co Ltd
Priority date: 2020-05-07
Filing date: 2020-05-07
Publication date: 2020-09-15
Anticipated expiration: 2040-05-07
Also published as: CN111669751B

Abstract

The application provides a method, a device and a communication system for establishing data streams, relates to the technical field of communication, ensures the use of terminal services by establishing at least two data streams at the same level, and can meet the requirements of highly reliable services. The method comprises the following steps: the NEF network element acquires first data from the process of establishing a first data stream between the first MEC server and the NEF network element; then sending a first message carrying the first data to a second MEC server, wherein the first message is used for indicating the second MEC server to initiate a first request to the NEF network element; receiving a first request carrying a first parameter sent by a second MEC server; the first parameter is used for indicating the establishment of data flow with the second MEC server; the first parameter includes first data; and establishing a second data flow between the second MEC server and the second MEC server according to the first parameters.

Description

Data stream establishing method, device and communication system

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method, an apparatus, and a communication system for establishing a data stream.

Background

In the current core network architecture, when a terminal service needs to open a network data function, communication with a multi-access edge computing (MEC) server is established first. Then, the MEC server may initiate a quality of service (QoS) flow establishment request to a network capability exposure function (NEF) network element of the core network, so as to establish a QoS flow to guarantee service communication of the terminal.

However, when the MEC server fails or the manner in which the terminal accesses the MEC server changes due to the mobility of the terminal, the QoS flow established between the terminal and the NEF network element may be interrupted, affecting the use of the terminal service.

Disclosure of Invention

The application provides a data flow establishing method, a data flow establishing device and a communication system, and solves the problem that when an MEC server breaks down, QoS flow is interrupted, and use of terminal services is affected.

In order to achieve the purpose, the technical scheme is as follows:

in a first aspect, the present application provides a method for establishing a data stream, where the method includes: the NEF network element acquires the first data from the process of establishing the first data flow with the first MEC server. And the NEF network element sends a first message carrying the first data to the second MEC server, wherein the first message is used for indicating the second MEC server to initiate a first request to the NEF network element. Wherein the second MEC server and the first MEC server are two different servers. The NEF network element receives a first request sent by a second MEC server, wherein the first request carries a first parameter used for indicating the NEF network element to establish a data flow between the NEF network element and the second MEC server, and the first parameter comprises first data. And after receiving the first request, the NEF network element establishes a second data flow between the NEF network element and the second MEC server according to the indication of the first parameter.

Since the NEF network element establishes a second data flow with the second MEC server after establishing the first data flow (such as QoS flow) with the first MEC server. And a second data stream established between the second MEC server and the NEF network element is established according to the first parameters, and the first data in the first parameters is acquired by the NEF network element from the process of establishing the first data stream. Therefore, the first data stream and the second data stream are data streams in the same level, and when one of the data streams is interrupted, the other data stream in the same level can still guarantee the use of the terminal service. Then, when the first MEC server fails, the use of the terminal service may be guaranteed by a second data flow established between the second MEC server and the NEF network element. Or, when the second MEC server fails, the use of the terminal service may be guaranteed through the first data flow established between the first MEC server and the NEF network element. Therefore, the method for establishing the data stream provided by the application ensures the use of the terminal service by establishing at least two data streams in the same level, and can adapt to the requirement of the highly reliable service.

In a second aspect, the present application provides a NEF network element, including: the device comprises an acquisition module, a sending module, a receiving module and a processing module. The acquiring module is configured to acquire first data, where the first data is acquired in a process of establishing a first data flow, and the first data flow is a data flow established between a first MEC server and an NEF network element. And the sending module is used for sending the first message to the second MEC server. The first message carries first data acquired by the acquisition module, and the first message is used for indicating the second MEC server to initiate a first request to the NEF network element; the second MEC server is different from the first MEC server. And the receiving module is used for receiving the first request sent by the second MEC server. The first request carries a first parameter, and the first parameter is used for indicating the NEF network element to establish a data flow between the NEF network element and the second MEC server; the first parameter includes first data sent by the sending module to the second MEC server. And the processing module is used for establishing a second data flow between the NEF network element and the second MEC server according to the first parameter received by the receiving module.

In a third aspect, the present application provides a data stream establishing apparatus, including a processor, where the processor is configured to be coupled with a memory, and read and execute instructions in the memory, so as to implement the data stream establishing method provided in the first aspect.

Optionally, the data stream establishing means may further comprise a memory for storing program instructions and data of the data processing apparatus. Further optionally, the data stream establishing apparatus may further include a transceiver, and the transceiver is configured to perform the step of transceiving data, signaling or information under the control of the processor of the data stream establishing apparatus, for example, the transceiver may acquire the first data in the process of establishing the first data stream.

Alternatively, the device for establishing the data stream may be a server, or may be a part of a device in the server, for example, a system on chip in the server. The system-on-chip is adapted to support the establishing means of the data stream to perform the functions referred to in the first aspect, such as receiving, sending or processing data and/or information referred to in the establishing method of the data stream. The chip system includes a chip and may also include other discrete devices or circuit structures.

In a fourth aspect, the present application provides a computer-readable storage medium, in which instructions are stored, and when the instructions are executed by a computer, the method for establishing a data stream as provided in the first aspect is implemented.

In a fifth aspect, the present application provides a computer program product comprising computer instructions which, when run on a computer, cause the computer to perform the method for establishing a data stream according to the first aspect.

In a sixth aspect, the present application provides a communication system comprising the NEF network element, the first MEC server, and the second MEC server as provided in the second aspect.

It should be noted that all or part of the computer instructions may be stored on the computer readable storage medium. The computer-readable storage medium may be packaged with the processor of the apparatus for establishing a data stream, or may be packaged separately from the processor of the apparatus for establishing a data stream, which is not limited in this application.

For the description of the second, third, fourth, fifth and sixth aspects in this application, reference may be made to the detailed description of the first aspect; in addition, for the beneficial effects described in the second aspect, the third aspect, the fourth aspect, the fifth aspect and the sixth aspect, reference may be made to the beneficial effect analysis of the first aspect, and details are not repeated here.

In the present application, the names of the above-mentioned means for establishing a data stream do not limit the devices or functional modules themselves, which may appear by other names in an actual implementation. Insofar as the functions of the respective devices or functional blocks are similar to those of the present invention, they are within the scope of the claims of the present application and their equivalents.

These and other aspects of the present application will be more readily apparent from the following description.

Drawings

Fig. 1 is a schematic structural diagram of a communication system according to an embodiment of the present application;

fig. 2 is a schematic flowchart of a method for establishing a data stream according to an embodiment of the present application;

fig. 3 is a schematic flowchart of another data flow establishing method according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of another communication system provided in the embodiment of the present application;

fig. 5 is a schematic signaling interaction diagram of a method for establishing a data flow according to an embodiment of the present application;

fig. 6 is a schematic signaling interaction diagram of another data flow establishing method according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of an NEF network element according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of an apparatus for establishing a data stream according to an embodiment of the present application.

Detailed Description

A method, an apparatus and a communication system for establishing a data stream according to the embodiments of the present application are described in detail below with reference to the accompanying drawings.

The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone.

The terms "first" and "second" and the like in the description and drawings of the present application are used for distinguishing different objects or for distinguishing different processes for the same object, and are not used for describing a specific order of the objects.

Furthermore, the terms "including" and "having," and any variations thereof, as referred to in the description of the present application, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements but may alternatively include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

It should be noted that in the description of the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or illustrations. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

In the description of the present application, the meaning of "a plurality" means two or more unless otherwise specified.

The MEC server is an open platform which integrates network, computing, storage and application core capabilities at the network edge side close to human, object or data sources. The MEC server can provide services for users nearby, and meets the key requirements of industry digitization on agile connection, real-time service, data optimization, application intelligence, safety, privacy protection and the like.

In the current core network architecture, when a terminal service needs to open a network data function, a QoS flow establishment request is initiated to an NEF network element of a core network to establish a QoS flow to guarantee service communication of the terminal. With the advent of MEC technology, a terminal can establish a QoS flow with a NEF network element through an MEC server after establishing communication with the MEC server.

However, in the above QoS flow establishment method, when the MEC server fails, the QoS flow established between the terminal and the NEF network element is interrupted, which affects the use of the terminal service. In addition, since the MEC server is an edge computing server, when the terminal moves out of the coverage of the current MEC server, the terminal establishes communication with another MEC server, and at the same time, the QoS flow established between the terminal and the NEF network element is also interrupted. In addition, in the existing QoS flow establishing method, only one QoS flow is provided to guarantee the terminal service, and the method cannot meet the requirement of high reliability of the service.

In view of the above problems in the prior art, an embodiment of the present application provides a method for establishing a data stream. By establishing at least two data streams in the same level, when the data stream between one MEC server and the NEF network element is interrupted, the use of the terminal service can be guaranteed through other MEC servers.

The method for establishing the data stream provided by the embodiment of the application can be applied to a communication system. Fig. 1 shows a structure of the communication system. The communication system comprises a plurality of MEC servers (only a first MEC server and a second MEC server are shown in fig. 1) and a NEF network element, each MEC server being connected to the NEF network element.

Wherein the first MEC server and the second MEC server are two different MEC servers under the coverage area of the NEF network element.

The following describes a method for establishing a data stream according to an embodiment of the present application with reference to the communication system shown in fig. 1.

In practical applications, the method for establishing the data flow between the NEF network element and each MEC server is the same. The following will describe an example of establishing a data flow between the NEF network element and the second MEC server.

Referring to fig. 2, a method for establishing a data stream according to an embodiment of the present application includes steps S101 to S104:

s101, the NEF network element acquires first data.

When the NEF network element establishes a data flow with the MEC server, it needs to establish according to the related data carried in the establishment request sent by the MEC server. In the method for establishing a data flow provided in the embodiment of the present application, before establishing a data flow (corresponding to the second data flow related to the embodiment of the present application) with the second MEC server, the NEF network element already establishes a data flow (corresponding to the first data flow related to the embodiment of the present application) with the first MEC server. Therefore, in order to ensure that the first data stream and the second data stream are at the same level, the NEF network element may directly obtain the required data (corresponding to the first data referred to in the embodiments of the present application) from the process of establishing the first data stream with the first MEC server before establishing the second data stream with the second MEC server.

Illustratively, the first data flow and the second data flow may be QoS flows. After a service is created by a terminal, a QoS flow guarantee mechanism is established first through the NEF element of the core network (that is, the terminal establishes a first data flow with the first MEC server through the NEF element) to guarantee communication of the service by the terminal.

Optionally, the first data includes at least: terminal address, quality of service reference data and traffic flow request data.

Of course, the first data may also include data required by the NEF network element when establishing the second data flow. Such as the duration of the second data stream, the occupancy of communication resources, etc.

The NEF network element may determine the real-time location of the terminal according to the terminal address, and determine whether the service created by the terminal is legal or not according to the service flow request data. The NEF network element may forward the terminal address, the quality of service reference data, and the service flow request data to a policy function (PCF) network element, and the PCF network element calculates a QoS parameter required for the terminal service according to the first data.

And S102, the NEF network element sends a first message to the second MEC server.

After the NEF network element acquires the first data, it may actively send a first message carrying the first data to the second MEC server.

Wherein the first message is used for instructing the second MEC server to initiate a first request to the NEF network element.

In addition, because the NEF network element performs signaling interaction with the multiple MEC servers, in order to ensure that no confusion occurs during communication, the NEF network element may allocate a physical number to the first message after sending the first message to the second MEC server. When the NEF network element receives the first request sent by the second MEC server or sends a message to the second MEC server later, the NEF network element also allocates the same physical number as the first message to the interactive signaling between the NEF network element and the second MEC server.

S103, the NEF network element receives the first request sent by the second MEC server.

After receiving the first message sent by the NEF network element, the second MEC server initiates a first request carrying the first parameter to the NEF network element according to the indication of the first message.

The first parameter is used to instruct the NEF network element to establish a data flow with the second MEC server, and the first parameter may include first data such as a terminal address, quality of service reference data, and service flow request data, and may further include an identifier of the second MEC server.

And S104, the NEF network element establishes a second data flow between the first MEC server and the second MEC server according to the first parameter.

For example, after receiving the first request carrying the first parameter sent by the second MEC server, the NEF network element may authenticate the first request according to the first parameter. Specifically, the NEF network element may authenticate the identifier of the second MEC server, and determine whether the second MEC server is a legitimate device. The NEF network element may further determine whether the service created by the terminal is legal according to the service flow request data in the first parameter. That is, the NEF network element needs to determine whether the first request initiated by the second MEC server is legal.

In addition, the second MEC server may have sent some other request to the NEF network element to apply for the creation of other services for the terminal before initiating the first request, possibly due to a network outage or other reason the signaling of the request is interrupted. Accordingly, while receiving the first request initiated by the second MEC server, the NEF network element may also apply the policy control of the first request to other requests initiated before the second MEC server, that is, may process other requests initiated before the second MEC server.

When the NEF network element determines that the authentication of the first request is successful, a second request carrying the first parameter may be sent to the PCF network element. Wherein the second request is used for instructing the PCF network element to determine whether the first request is allowed.

Optionally, after the NEF network element determines that the authentication of the first request is successful, the policy control of the first request may also be stored. In this way, when the NEF network element receives the same request sent by the second MEC server again, the NEF network element may not authenticate the same request any more.

After receiving the second request, the PCF network element calculates specific parameters of a data flow (i.e. a second data flow) that guarantees the terminal service according to the first parameters carried in the second request, and then determines whether the first request is allowed or not according to the calculation result, that is, determines whether the second data flow is allowed to be established or not. Illustratively, when the first parameter includes the qos reference data, and the packet loss rate of the qos reference data, which indicates the current terminal service requirement, is 10^-3. That is, the requirement of terminal service is that the loss of 1000 packets is the maximum range that can be allowed by the current network. However, the result calculated by the PCF network element is a packet loss rate of 10^-2It is indicated that the current network cannot meet the service requirement of the terminal, and at this time, the PCF network element sends the third message to the NEF network element. Wherein the third message is for informing the NEF network element that the first request is not allowed.

In another embodiment, the qos reference data indicates that the maximum delay of the current terminal service cannot exceed 100 ms, and the maximum delay calculated by the PCF network element is 10 ms, and the current network can meet the requirements of other parameters. At this time, the PCF network element sends a second message to the NEF network element. Wherein the second message is used to inform the NEF network element that the first request is allowed.

When the NEF network element receives the second message sent by the PCF network element, it sends a first response to the second MEC server, where the first response is used to notify the second MEC server that the second data stream is established. At this time, the data flows between the NEF network element and the second MEC server, the first MEC server are all established, that is, two data flows are provided to guarantee the use of the terminal service. At this time, the NEF network element may initiate a request for establishing a data stream to another MEC server in the coverage area of the NEF network element, that is, use of the terminal service is guaranteed by a plurality of data streams.

When the NEF network element receives the third message sent by the PCF network element, it sends a second response to the second MEC server, where the second response is used to instruct the second MEC server to reinitiate the first request, and then repeats steps S101-S104 until the first request is allowed by the PCF network element.

In the method for establishing a data flow provided in the embodiment of the present application, after the NEF network element establishes a first data flow (for example, a QoS flow) with the first MEC server, a second data flow with the second MEC server is established. And a second data stream established between the second MEC server and the NEF network element is established according to the first parameters, and the first data in the first parameters is acquired by the NEF network element from the process of establishing the first data stream. Therefore, the first data stream and the second data stream are data streams in the same level, and when one of the data streams is interrupted, the other data stream in the same level can still guarantee the use of the terminal service. Then, when the first MEC server fails, the use of the terminal service may be guaranteed by a second data flow established between the second MEC server and the NEF network element. Or, when the second MEC server fails, the use of the terminal service may be guaranteed through the first data flow established between the first MEC server and the NEF network element. Therefore, the method for establishing the data stream provided by the application ensures the use of the terminal service by establishing at least two data streams in the same level, and can adapt to the requirement of the highly reliable service.

In summary, as shown in fig. 3, step S104 in fig. 2 can be replaced by steps S1041-S1046:

and S1041, the NEF network element authenticates the first request according to the first parameter.

S1042, the NEF network element determines that the first request is successfully authenticated, and sends a second request to the PCF network element.

The second request carries the first parameter, and the second request is used for indicating the PCF network element to judge whether the first request is allowed or not.

And S1043, the NEF network element receives the second message or the third message sent by the PCF network element.

The second message is for notifying the NEF network element that the first request is allowed, and the third message is for notifying the NEF network element that the first request is not allowed.

S1044, the NEF network element judges whether the message sent by the received PCF network element is the second message.

When the NEF network element judges that the received message sent by the PCF network element is the second message, S1045 is executed; when the NEF network element determines that the received message sent by the PCF network element is not the second message, indicating that the message sent by the PCF network element received by the NEF network element is the third message, S1046 is executed.

S1045, the NEF network element sends the first response to the second MEC server.

Wherein the first response is to notify the second MEC server that the second data flow is established.

S1046, the NEF network element sends a second response to the second MEC server.

The second response is to instruct the second MEC server to reinitiate the first request.

The above embodiment is performed on the premise that the first data flow is established between the NEF network element and the first MEC server. Hereinafter, a procedure of establishing a data flow between the NEF network element and the first MEC server and the second MEC server will be fully described in one embodiment.

Referring to fig. 4, an embodiment of the present application further provides a communication system, including: the system comprises a terminal, a first MEC server, a second MEC server, a NEF network element and a PCF network element.

As shown in fig. 5, a signaling interaction diagram of a method for establishing a data flow applied to the system architecture shown in fig. 5 is provided. First, the terminal first initiates a request for establishing communication to the first MEC server (corresponding to S1 in fig. 5). Then, the first MEC server may send a MEC session generation request with QoS (MECsessionWithQoS _ Create, corresponding to the third request of S2 in fig. 5) to the NEF network element. After receiving a request for generating a MEC session QoS sent by a first MEC server, the NEF network element allocates a physical number to the signaling, authenticates the request (corresponding to S3 in fig. 5), and after the authentication is determined to be passed, the NEF network element sends a policy authorization creation request (Npcf _ policy authorization _ credit, corresponding to a fourth request of S4 in fig. 5) to the PCF network element, where the request carries second parameters such as a terminal address, an identifier of the first MEC server, quality of service reference data, and service flow request data.

The PCF network element may calculate the QoS parameter required by the terminal service according to the second parameter carried in the policy authorization creation request, and then determine whether the MEC session generation request with QoS, sent to the NEF network element by the first MEC server, is allowed according to the calculation result (corresponding to S5 in fig. 5). The PCF network element, after determining, sends a policy authorization creation response (a fourth response corresponding to S6 in fig. 5) to the NEF network element. When the PCF network element determines that the MEC session generation request with QoS is allowed, the policy authorization creation response is used for informing the NEF network element that the MEC session generation request with QoS is allowed. When the PCF network element determines that the MEC session generation request with QoS is not allowed, the strategy authorization creation response is used for indicating that the first MEC server needs to initiate the generation request for informing the NEF network element to initiate the MEC session QoS again.

The NEF network element, after receiving the policy authorization creation response, replies to the first MEC server a MEC session zone QoS generation response (corresponding to the third response of S7 in fig. 5) notifying the first MEC server whether the MEC session zone QoS generation request is allowed.

When the MEC session bandwidth QoS generation request is allowed, it indicates that the first data flow between the NEF network element and the first MEC server is established. At this time, the first MEC server replies to the terminal with a setup communication response (corresponding to S8 in fig. 5), informing the terminal that the first data flow is established.

In addition, after receiving the policy authorization creation response, the NEF network element also sends a first message (MECsessionWithQoS _ Notify, corresponding to S9 in fig. 5) to the second MEC server to Notify the second MEC server that the first data flow is established. Meanwhile, the NEF network element may obtain the first data from the establishment process of the first data stream and send the first data to the second MEC server.

After receiving the first message sent by the NEF network element, the second MEC server establishes a second data flow according to the first data in the first message (corresponding to S10-S15 in fig. 5). The process of establishing the second data stream may refer to the related description about the process of establishing the first data stream in the foregoing or the establishing method of the data stream provided with reference to fig. 3.

Optionally, as shown in fig. 6, after step S15, the NEF network element further sends a subscription request (Npcf _ PolicyAuthorization _ Subscribe, corresponding to S16 in fig. 5) to the PCF network element, where the subscription message is used to indicate that the NEF network element periodically visits the PCF network element. Thus, after the policy of the first MEC server or the second MEC server is changed (for example, parameters such as time delay, bandwidth, and the like are changed) by the PCF network element, the NEF network element can timely know the information and feed the information back to the first MEC server or the second MEC server. The PCF network element also replies a subscription response, feeding back the result of the subscription (Npcf _ PolicyAuthorization _ Notify, corresponding to S17 in fig. 5).

In addition, when the environment change on the core network side causes that the previously established data stream cannot guarantee the terminal service, the NEF network element also sends a first notification message and a second notification message to the first MEC server and the second MEC server (corresponding to S18 and S19 in fig. 5).

It should be noted that, in the method for establishing a data stream provided in the embodiment of the present application, the request for establishing a second data stream is initiated by the NEF network element to the second MEC server actively. In practical application, the method can also be initiated by a terminal side. For example, in the signaling interaction diagram shown in fig. 5, after step S8, that is, after the terminal receives the message that the first data flow sent by the first MEC server is established, the terminal may initiate a request for establishing the second data flow to the second server.

As shown in fig. 7, a schematic diagram of a possible structure of the NEF network element 01 in the data flow establishing system (the data flow establishing system provided in fig. 1 or fig. 4) involved in the foregoing embodiments is provided. The NEF network element 01 includes: the device comprises an acquisition module 11, a sending module 12, a receiving module 13 and a processing module 14.

The obtaining module 11 executes S101 in the above method embodiment, the sending module 12 executes S102 in the above method embodiment, the receiving module 13 executes S103 in the above method embodiment, and the processing module 14 executes S104 in the above method embodiment.

Specifically, the obtaining module 11 is configured to obtain first data. The first data is data acquired in a process of establishing a first data flow, and the first data flow is a data flow established between the first MEC server 02 and the NEF network element 01.

A sending module 12, configured to send the first message to the second MEC server 03. The first message carries the first data acquired by the acquiring module 11, and the first message is used to instruct the second MEC server 03 to initiate a first request to the NEF network element 01. The second MEC server 03 is different from the first MEC server 02.

The receiving module 13 is configured to receive the first request sent by the second MEC server 03. The first request carries a first parameter, the first parameter is used to instruct the NEF network element 01 to establish a data flow with the second MEC server 03, and the first parameter includes first data sent by the sending module 12 to the second MEC server 03.

A processing module 14, configured to establish a second data flow between the NEF network element 01 and the second MEC server 03 according to the first parameter received by the receiving module 13.

Optionally, the processing module 14 is specifically configured to: authenticating the first request according to the first parameter; and determining that the first request passes the authentication, and sending a second request to the PCF network element through the sending module 12. The second request carries the first parameter, and the second request is used for indicating the PCF network element to judge whether the first request is allowed or not.

The processing module 14 is further specifically configured to: and receiving the second message or the third message sent by the PCF network element by the receiving module 13. Wherein the second message is used for informing the NEF network element 01 that the first request is allowed, and the third message is used for informing the NEF network element 01 that the first request is not allowed.

Optionally, the processing module 14 is further specifically configured to: after receiving the second message or the third message sent by the PCF network element through the receiving module 13, if the receiving module 13 receives the second message sent by the PCF network element, the sending module 12 sends a first response to the second MEC server 03. Wherein the first response is used to inform the second MEC server 03 that the second data stream is established.

The processing module 14 is further specifically configured to: if the receiving module 13 receives the third message sent by the PCF network element, it sends a second response to the second MEC server 03 through the sending module 12. Wherein the second response is used to instruct the second MEC server 03 to reinitiate the first request.

Optionally, the first parameter further includes an identifier of the second MEC server 03, and the first data includes at least: terminal address, quality of service reference data and traffic flow request data.

Optionally, the NEF network element 01 further includes a storage module. The storage module is used for storing the program codes of the NEF network element 01 and the like.

As shown in fig. 8, an apparatus for establishing a data stream according to an embodiment of the present application further includes a memory 41, a processor 42, a bus 43, and a communication interface 44; the memory 41 is used for storing computer execution instructions, and the processor 42 is connected with the memory 41 through a bus 43; when the data stream establishing apparatus operates, the processor 42 executes computer-executable instructions stored in the memory 41 to cause the data stream establishing apparatus to execute the data stream establishing method applied to the NEF network element as provided in the above embodiments.

In particular implementations, processor 42(42-1 and 42-2) may include one or more Central Processing Units (CPUs), such as CPU0 and CPU1 shown in FIG. 8, as one example. And as an example, the means for establishing the data stream may comprise a plurality of processors 42, such as processor 42-1 and processor 42-2 shown in fig. 8. Each of the processors 42 may be a single-Core Processor (CPU) or a multi-Core Processor (CPU). Processor 42 may refer herein to one or more devices, circuits, and/or processing cores that process data (e.g., computer program instructions).

The memory 41 may be, but is not limited to, a read-only memory 41 (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), a magnetic disc storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory 41 may be self-contained and coupled to the processor 42 via a bus 43. The memory 41 may also be integrated with the processor 42.

In a specific implementation, the memory 41 is used for storing data in the present application and computer-executable instructions corresponding to software programs for executing the present application. The processor 42 may set up the various functions of the apparatus by running or executing software programs stored in the memory 41 and calling up data stored in the memory 41, the data stream.

The communication interface 44 is any device, such as a transceiver, for communicating with other devices or communication networks, such as a control system, a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), and the like. The communication interface 44 may include a receiving unit implementing a receiving function and a transmitting unit implementing a transmitting function.

The bus 43 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an extended ISA (enhanced industry standard architecture) bus, or the like. The bus 43 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 8, but this is not intended to represent only one bus or type of bus.

As an example, in connection with fig. 7, the function implemented by the receiving module in the data stream establishing apparatus is the same as the function implemented by the receiving unit in fig. 8, the function implemented by the processing module in the data stream establishing apparatus is the same as the function implemented by the processor in fig. 8, and the function implemented by the storage module in the data stream establishing apparatus is the same as the function implemented by the memory in fig. 8.

For the explanation of the related contents in this embodiment, reference may be made to the above method embodiments, which are not described herein again.

Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions. For the specific working processes of the system, the apparatus and the unit described above, reference may be made to the corresponding processes in the foregoing method embodiments, and details are not described here again.

The embodiment of the present application further provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the instructions are executed by a computer, the computer is enabled to execute the method for establishing a data stream applied to a NEF network element, which is provided in the foregoing embodiment.

The computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a RAM, a ROM, an erasable programmable read-only memory (EPROM), a register, a hard disk, an optical fiber, a CD-ROM, an optical storage device, a magnetic storage device, any suitable combination of the foregoing, or any other form of computer readable storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an Application Specific Integrated Circuit (ASIC). In embodiments of the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for establishing a data flow is applied to a network capability openness function (NEF) network element, and is characterized in that the method for establishing the data flow comprises the following steps:

acquiring first data, wherein the first data is acquired in the process of establishing a first data flow, and the first data flow is a data flow established between a first multi-access edge computing (MEC) server and the NEF network element;

sending a first message to a second MEC server; the first message carries the first data; the first message is used for instructing the second MEC server to initiate a first request to the NEF network element; the second MEC server and the first MEC server are different;

receiving the first request sent by the second MEC server; the first request carries a first parameter; the first parameter is used for instructing the NEF network element to establish a data flow with the second MEC server; the first parameter comprises the first data;

and establishing a second data flow between the second MEC server and the second MEC server according to the first parameter.

2. The method according to claim 1, wherein the establishing a second data flow with the second MEC server according to the first parameter includes:

authenticating the first request according to the first parameter;

determining that the first request is successfully authenticated, and sending a second request to a policy function PCF network element; the second request carries the first parameter; the second request is used for indicating the PCF network element to judge whether the first request is allowed or not;

receiving a second message or a third message sent by the PCF network element; the second message is used for informing the NEF network element that the first request is allowed; the third message is used to inform the NEF network element that the first request is not allowed.

3. The method for establishing a data flow according to claim 2, wherein after receiving the second message or the third message sent by the PCF network element, the method for establishing a data flow further comprises:

if receiving a second message sent by the PCF network element, sending a first response to the second MEC server; the first response is to notify the second MEC server that the second data stream is established;

if receiving a third message sent by the PCF network element, sending a second response to the second MEC server; the second response is to instruct the second MEC server to reinitiate the first request.

4. A method for establishing a data flow according to any one of claims 1-3, wherein the first parameter further comprises an identifier of the second MEC server; the first data includes at least: terminal address, quality of service reference data and traffic flow request data.

5. A NEF network element, comprising: the device comprises an acquisition module, a sending module, a receiving module and a processing module;

the acquiring module is configured to acquire first data, where the first data is acquired in a process of establishing a first data flow, and the first data flow is a data flow established between a first MEC server and the NEF network element;

the sending module is used for sending a first message to the second MEC server; the first message carries the first data acquired by the acquisition module; the first message is used for instructing the second MEC server to initiate a first request to the NEF network element; the second MEC server and the first MEC server are different;

the receiving module is configured to receive the first request sent by the second MEC server; the first request carries a first parameter; the first parameter is used for instructing the NEF network element to establish a data flow with the second MEC server; the first parameter comprises the first data sent by the sending module to the second MEC server;

the processing module is configured to establish a second data flow between the NEF network element and the second MEC server according to the first parameter received by the receiving module.

6. The NEF network element of claim 5, wherein the processing module is specifically configured to:

authenticating the first request according to the first parameter;

determining that the first request is successfully authenticated, and sending a second request to the PCF network element through the sending module; the second request carries the first parameter; the second request is used for indicating the PCF network element to judge whether the first request is allowed or not;

receiving a second message or a third message sent by the PCF network element through the receiving module; the second message is used for informing the NEF network element that the first request is allowed; the third message is used to inform the NEF network element that the first request is not allowed.

7. The NEF network element of claim 6, wherein the processing module is further specifically configured to:

after receiving the second message or the third message sent by the PCF network element through the receiving module, if the receiving module receives the second message sent by the PCF network element, sending a first response to the second MEC server through the sending module; the first response is to notify the second MEC server that the second data stream is established;

if the receiving module receives a third message sent by the PCF network element, a second response is sent to the second MEC server through the sending module; the second response is to instruct the second MEC server to reinitiate the first request.

8. The NEF network element of any one of claims 5-7, wherein said first parameters further comprise an identifier of said second MEC server; the first data includes at least: terminal address, quality of service reference data and traffic flow request data.

9. The device for establishing the data stream is characterized by comprising a memory, a processor, a bus and a communication interface; the memory is used for storing computer execution instructions, and the processor is connected with the memory through the bus;

when the data stream establishing device runs, the processor executes the computer-executable instructions stored in the memory to cause the data stream establishing device to execute the data stream establishing method according to any one of claims 1 to 4.

10. A computer-readable storage medium having stored therein instructions, which when executed by a computer, cause the computer to execute the method of establishing a data stream according to any one of claims 1 to 4.

11. A communication system comprising a first MEC server, a second MEC server and a NEF network element according to any one of claims 5-8.