CN114521004A

CN114521004A - Data transmission method, device, equipment and storage medium

Info

Publication number: CN114521004A
Application number: CN202011298958.5A
Authority: CN
Inventors: 尚宇翔; 胡臻平; 纪文娟
Original assignee: China Mobile Communications Group Co Ltd
Current assignee: China Mobile Communications Group Co Ltd
Priority date: 2020-11-19
Filing date: 2020-11-19
Publication date: 2022-05-20

Abstract

The application discloses a data transmission method, a data transmission device, data transmission equipment and a storage medium. The data transmission method comprises the following steps: receiving an access request of a target application program, wherein the access request comprises a target data network identifier corresponding to the target application program; determining a target network slice identifier associated with the target data network identifier according to the association relationship between the data network identifier and the network slice identifier; establishing session connection of the target network slice corresponding to the target network slice identifier; and sending the data of the target application program to a cloud server through the session connection. By adopting the data transmission method, the data transmission device, the data transmission equipment and the storage medium, the dependency on the application program in the data transmission process can be effectively reduced.

Description

Data transmission method, device, equipment and storage medium

Technical Field

The present application relates to the field of communications technologies, and in particular, to a data transmission method, apparatus, device, and storage medium.

Background

In cloud services, when a User uses User Equipment (UE), that is, an Application (APP) on a User terminal, the UE may transmit data of the APP to a cloud APP entity according to a User Equipment routing selection policy (URSP) of the APP object.

At present, before establishing session connection with a Network slice corresponding to an APP, the UE needs to obtain a Data Network Name (DNN) and an Identity (ID) of the Network slice corresponding to the APP from the APP, so that the UE can establish session connection with the Network slice corresponding to the APP according to the DNN and the ID of the Network slice, and route Data of the APP to the cloud server through the Network slice. Therefore, when the user uses the cloud service each time, the UE needs to acquire the DNN and the network slice ID corresponding to the APP to send data from the terminal to the cloud server, which results in a higher dependency of sending data on the APP.

Disclosure of Invention

An object of the embodiments of the present application is to provide a data transmission method, apparatus, device and storage medium, which can effectively reduce the dependency on an application program in data transmission.

The technical scheme of the application is as follows:

in a first aspect, a data transmission method is provided, which is applied to a user terminal, and the method may include:

receiving an access request of a target application program, wherein the access request comprises a target data network identifier corresponding to the target application program;

determining a target network slice identifier associated with the target data network identifier according to the association relationship between the data network identifier and the network slice identifier;

establishing session connection of the target network slice corresponding to the target network slice identifier;

and sending the data of the target application program to the cloud server through the session connection.

In one embodiment, the method may further comprise:

sending a registration request of a target application program to an operator server;

receiving a routing strategy sent by an operator server according to the registration request, wherein the routing strategy comprises a network slice identifier corresponding to the target application program;

and associating the data network identification corresponding to the target application program with the network slice identification.

In one embodiment, receiving a routing policy sent by an operator server according to a registration request includes:

receiving a non-access stratum (NAS) message sent by an operator server through a base Band Processor (BP), wherein the NAS message comprises a routing strategy;

associating the data network identifier corresponding to the target application program with the network slice identifier, including:

transmitting the routing strategy to an AP layer of an application processor of an operating system through a BP;

transmitting the target data network identification of the target application program to an AP layer through a preset transfer function;

and associating the data network identification corresponding to the target application program with the network slice identification in the AP layer.

In one embodiment, the routing policy further includes a routing policy version identification corresponding to the target application.

In one embodiment, the routing policies also include routing policies corresponding to applications other than the target application.

In one embodiment, establishing a session connection for a target network slice corresponding to a network slice identification comprises:

and sending the target data network identification and the target network slice identification to a mobile management function AMF and a session management function SMF so that the AMF and the SMF establish session connection between the terminal and a user plane function UPF corresponding to the target data network identification and the target network slice identification.

In a second aspect, a data transmission method is provided, which is applied to an operator server, and the method may include:

receiving a registration request of a target application program sent by a user terminal;

and sending a routing strategy to the user terminal according to the registration request, wherein the routing strategy comprises a network slice identifier corresponding to the target application program.

In a third aspect, a data transmitting apparatus is provided, which may include:

the system comprises a receiving module, a processing module and a processing module, wherein the receiving module can be used for receiving an access request of a target application program, and the access request can comprise a target data network identifier corresponding to the target application program;

the determining module may be configured to determine, according to an association relationship between the data network identifier and the network slice identifier, a target network slice identifier associated with the target data network identifier;

the connection module can be used for establishing session connection of a target network slice corresponding to the network slice identifier;

the sending module may be configured to send data of the target application to the cloud server through the session connection.

In a fourth aspect, there is provided a data transmission device, which may include:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the data transmission method as shown in any embodiment of the first aspect.

In a fifth aspect, there is provided a storage medium, wherein instructions of the storage medium, when executed by a processor of an information processing apparatus or a server, cause the information processing apparatus or the server to implement the data transmission method as shown in any one of the embodiments of the first aspect.

According to a fifth aspect of embodiments of the present application, there is provided a computer program product comprising a computer program stored in a readable storage medium, from which at least one processor of a device reads and executes the computer program, so that the device performs the data transmission method shown in any one of the embodiments of the first aspect.

The technical scheme provided by the embodiment of the application at least has the following beneficial effects:

according to the embodiment of the application, the target network slice identification corresponding to the target data network identification carried by the target application program is determined, and session connection is established with the target network slice corresponding to the target network slice identification, so that data transmission of the target application program is realized. Therefore, the data transmission from the user terminal to the cloud server can be realized without acquiring the data network name and the network slice identifier corresponding to the application program from the application program every time the user terminal accesses the application program, and the dependency on the application program in the data transmission process can be effectively reduced.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the application and are not to be construed as limiting the application.

Fig. 1 is a diagram of a network architecture provided by an embodiment of the present application;

fig. 2 is a schematic flowchart illustrating a process of configuring a routing policy for a target application according to an embodiment of the present application;

fig. 3 is a flowchart illustrating a data transmission method according to an embodiment of the present application;

fig. 4 is a schematic diagram illustrating an android network connection establishment process and DNN parameter passing provided in an embodiment of the present application;

fig. 5 is a schematic diagram of establishing a session connection between a user terminal and a UPF corresponding to a target application according to this embodiment of the present application

Fig. 6 is a flowchart illustrating a data transmission method according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a data transmission apparatus according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a data transmission device according to an embodiment of the present application.

Detailed Description

In order to make the technical solutions of the present application better understood by those of ordinary skill in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.

It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

Based on the background art, when a user uses a cloud service each time, the UE needs to acquire a DNN and a network slice ID corresponding to the APP to send data from the terminal to the cloud server, which results in a higher dependency of data sending on the APP.

Specifically, the continuous development of the fifth generation mobile communication technology (5th generation mobile networks, 5G) provides a gorgeous and rich space and platform for the development of various services, and especially provides a wide development space for cloud service applications such as cloud games and cloud live broadcast. The 5G network can provide a special network slice for the cloud service application program, for example, a special network slice, namely a special logic network channel, can be provided for the cloud live broadcast application program, and better service experience such as high safety, high isolation, high real-time service bandwidth and the like is brought to a user.

Moreover, in the prior art, it is usually required that an application developer writes routing policies corresponding to an application, including DNNs and network slice IDs corresponding to APPs, into configuration parameters of the APPs, and carries and updates all routing policies corresponding to the APPs through the APPs.

Based on the above findings, the inventors of the present application provide the data sending method of the present application, which can establish session connection with a target network slice corresponding to a target network slice identifier by determining the target network slice identifier corresponding to the target data network identifier carried by a target application program, thereby implementing data sending of the target application program. Therefore, the data transmission from the user terminal to the cloud server can be realized without acquiring the data network name and the network slice identifier corresponding to the application program from the application program every time the user terminal accesses the application program, and the dependency on the application program in the data transmission process can be effectively reduced.

The data transmission method provided by the application can be applied to the network architecture shown in fig. 1. As shown in fig. 1, the network architecture may include a user equipment UE (i.e., user terminal), an operator server, a cloud server, a network slice.

The UE may send a registration request of a target application to an operator server, and after receiving the registration request of the target application sent by the UE, the operator server may send a routing policy to the UE according to the registration request, where the routing policy may include a network slice identifier corresponding to the target application. After receiving the routing policy sent by the operator server, the UE may associate the data network identifier corresponding to the target application with the network slice identifier in the routing policy. After receiving an access request of a target application program, the UE may determine a target network slice identifier associated with a target data network identifier carried in the access request according to an association relationship between the data network identifier and the network slice identifier, and establish a session connection of a target network slice corresponding to the network slice identifier, so as to send data of the target application program to the cloud server through the session connection.

As a specific example, as shown in fig. 2, fig. 2 illustrates, by taking a target application as a live cloud, a flowchart illustrating configuring a routing policy for the target application according to an embodiment of the present application, where a specific implementation method of the method may include the following steps:

step 1-1, a cloud live broadcast manufacturer can subscribe a cloud live broadcast accelerated network slice with an operator, and the operator can allocate a corresponding dedicated data network identifier and a network slice identifier for a cloud live broadcast APP, such as DNN-1 and S-NSSAI-1.

Step 1-2, the user terminal may subscribe to an Enhanced Mobile Broadband (EMBB) package with the operator.

And 2-1, a cloud live broadcast manufacturer develops a cloud live broadcast APP, and a data network identifier corresponding to the cloud live broadcast APP can be written into the cloud live broadcast APP, such as DNN-1.

Step 2-2, the operator server may update a preset URSP of the cloud live vendor, where the preset URSP may include a data network identifier DNN-0 and a network slice identifier S-NSSAI-0, or may further include a version identifier default of the preset URSP.

And 3, the cloud live broadcast manufacturer can apply for the network slice ID corresponding to the cloud live broadcast APP from the operator.

Step 4, the operator server may divide a network slice identifier ID for the cloud live APP, for example, S-NSSAI-1 may be defined by the third Generation Partnership Project (3 GPP), configure corresponding URSPs DNN-1 and S-NSSAI-1 for the cloud live APP, and configure corresponding network resources.

And step 5, installing a cloud live APP by the user terminal, wherein the cloud live APP can comprise a parameter DNN-1.

And 6, subscribing the cloud live broadcast acceleration service by the user terminal.

Step 7, the operator server may update the URSP corresponding to the cloud live APP and send the URSP corresponding to the cloud live APP to the user terminal, where the URSP may include a data network identifier DNN-1 and a network slice identifier S-NSSAI-1, or may further include a version identifier SUPI-1 of the URSP. And correlating cloud live broadcast APP, DNN-1 and S-NSSAI-1.

Based on the above architecture, the data transmission method provided by the embodiment of the present application is described in detail below with reference to fig. 3.

Fig. 3 shows a flowchart of a data transmission method provided in an embodiment of the present application, where the data transmission method may be applied to a user equipment UE, that is, may be applied to a user terminal. Also, the data transmission method shown in fig. 3 can be applied to the following cases: 1. the user terminal already stores a network slice identifier corresponding to the cloud service application program, such as S-NSSAI-1, and the cloud service application program modifies a signed data network identifier; 2. the user terminal does not store the network slice identifier corresponding to the cloud service application program, and does not store the data network identifier corresponding to the cloud service application program; 3. the user terminal stores the network slice identifier corresponding to the cloud service application program, but does not store the network slice identifier corresponding to the cloud service application program.

As a specific example, as shown in fig. 3, the data transmission method applied to the user terminal may include the following steps:

s310, receiving an access request of the target application program.

As one example, the access request may include a target data network identification corresponding to the target application.

The target application may be any application installed in the user terminal that corresponds to a dedicated network slice.

The target data network identification may be an identification corresponding to a data network name DNN corresponding to the target application.

In this embodiment, when a user accesses a target application, the target application may be operated through a user terminal to trigger the target application to send an access request to the user terminal, where the access request may include a target data network identifier corresponding to the target application.

It is understood that, when the developer of the application develops the cloud service application, the developer may cooperate with an operator, and the operator may allocate a dedicated DNN and a network slice to the application, and feed back a DNN identifier and a network slice identifier corresponding to each application to the developer of the application, so that the developer of the application may write the DNN identifier corresponding to each application into the configuration of the application.

S320, determining a target network slice identifier associated with the target data network identifier according to the association relationship between the data network identifier and the network slice identifier.

As one example, the target network slice identification may be an identification of a network slice associated with the target data network identification.

In this embodiment, after receiving an access request of a target application program, a user terminal may analyze the access request to obtain a target data network identifier corresponding to the target application program. Then, according to the association relationship between the data network identifier and the network slice identifier, a target network slice identifier associated with a target data network identifier corresponding to the target application program is determined, that is, the target application program matches a target network slice corresponding to the target application program.

It can be understood that the target application program has a corresponding DNN identifier and a network slice identifier, and the user terminal may locally associate the DNN identifier and the network slice identifier corresponding to each application program to obtain an association relationship between the DNN identifier and the network slice identifier corresponding to each application program.

S330, establishing the session connection of the target network slice corresponding to the target network slice identifier.

In this embodiment, after determining the target network slice identifier associated with the target data network identifier corresponding to the target application program, the target network slice corresponding to the target network slice identifier may be determined. A session connection, such as a Protocol Data Unit (PDU) session connection, may then be established with the target network slice.

And S340, sending the data of the target application program to the cloud server through session connection.

In this embodiment, after establishing a session connection of a target network slice corresponding to a target network slice identifier, a user terminal may send data of a target application program to a cloud server through the session connection, so as to implement use of the target application program.

For in the background art, data transmission of an application program is realized by acquiring a data network name and a network slice identifier carried by an APP, a large amount of work needs to be done by an APP side, the dependence degree on the APP is high, and if the APP side has a problem, a routing strategy corresponding to the APP cannot be updated. In the application, the application program side only needs to carry the corresponding DNN identification, thereby effectively reducing the dependence on the APP in the data sending process,

in some embodiments, when the target application is used for the first time, the association relationship between the data network identifier and the network slice identifier corresponding to the target application may be established, and the specific implementation manner may be as follows:

receiving a routing strategy sent by an operator server according to the registration request;

As one example, the routing policy may include a network slice identification corresponding to the target application;

when the target application program is accessed for the first time, a registration request of the target application program can be sent to the operator server, and the registration request can carry the identifier of the target application program, so that the operator server can analyze the registration request to obtain the identifier of the target application program, determine a routing strategy corresponding to the target application program according to the identifier of the target application program, and send the routing strategy to the user terminal. It is to be understood that the operator server may also send network slice identifications corresponding to a plurality of applications and network slice identifications corresponding to applications without dedicated network slices to the user terminal.

Then, the user terminal may receive a routing policy sent by the operator server according to the registration request of the target application, where the routing policy may include a network slice identifier corresponding to the target application. After receiving a routing strategy sent by an operator server according to a registration request of a target application program, the routing strategy can be analyzed to obtain a network slice identifier corresponding to the target application program, the data network identifier corresponding to the target application program can be obtained, the data network identifier and the network slice identifier of the target application program are locally associated, and an association relation between the data network identifier and the network slice identifier of the target application program is established.

Referring to table 1, in table 1, taking the target application as the cloud live broadcast, and taking the program except the target application as the default as an example, an association relationship between the data network identifier and the network slice identifier of the target application is shown.

TABLE 1

Application program	DNN identification	Network slice identification
			Cloud live broadcast	DNN-0	S-NSSA1-0
default	DNN-1	S-NSSA1-1

Therefore, when the target application program is accessed for the first time, the association relationship between the data network identifier corresponding to the target application program and the network slice identifier is established, and a data basis can be provided for determining the target network slice identifier associated with the target data network identifier of the target application program when the target application program is accessed again, so that the data sending efficiency can be improved.

In some embodiments, the specific implementation manner of the routing policy sent by the receiving operator server according to the registration request may be as follows:

and receiving a non-access stratum (NAS) message sent by an operator server through a Baseband Processor (BP), wherein the non-access stratum (NAS) message comprises a routing strategy.

Correspondingly, the specific implementation manner for associating the data network identifier corresponding to the target application program with the network slice identifier may be as follows:

transmitting the routing strategy to an application processor AP layer of an operating system through a BP;

As an example, the preset transfer function may be a preset function for transferring the data network identification from the application layer to the AP layer, as may be denoted as URSP facility ().

In this embodiment, the user terminal may receive a Non-access stratum (NAS) message including a routing policy of the target application sent by the operator through a Baseband Processor (BP), and since the user terminal typically receives the NAS message through an N1 interface, the NAS message may also be referred to as an N1 NAS message. The user terminal may then transmit the routing policy to an Application Processor (AP) layer of the operating system layer through the BP layer via the communication protocol layer. And transmitting the data network identification corresponding to the target application program to the AP layer through a preset transfer function, associating the data network identification corresponding to the target application program with the network slice identification on the AP layer, and establishing an association relation between the data network identification corresponding to the target application program and the network slice identification.

Since DNN is visible on Modem side, a large multi-chip vendor already supports configuration of DNN parameters on the chip side to implement mapping and binding of DNN and network slice ID, but the android system does not support DNN transfer from APP application layer to bottom layer at present. In the new DNN parameter transferring method provided by the application, the user terminal can complete the transfer of the DNN parameters from the application layer to the AP layer by adding a self-defined preset transfer function in addition to the Android existing function, and simultaneously, the storage function of the user terminal is utilized to store the data network identification and the network slice identification corresponding to the application program.

As a specific example, referring to fig. 4, fig. 4 shows a schematic diagram of an android network connection establishment process and DNN parameter delivery provided in an embodiment of the present application. As shown in fig. 4, in the present application, by adding a preset transfer function, skipping an Android function, and getting rid of the limitation that the original telephone (Telephony) function does not support the transfer of DNN parameters, so that DNN parameters can cross a layer 2 connection Manager layer (connectivity Manager), a layer 3 connection server layer (connectivity Service), a layer 4 telephone Network Factory layer (Telephony Network Factory), and a layer 5 Dc Tracker layer (Dc Tracker), APP can directly carry DNN parameters and directly transfer the DNN parameters from the layer 1 application layer (application) to an Apn context layer (apntext), update DNN parameters at the sixth layer, and the layer 7 can select an Apn meeting Network requirements according to the type of an Access Point (Access Point Name, Apn), complete the association binding of DNN and a Network slice identifier, and transfer the Apn to a Modem, thereby establishing a Network connection Modem. As shown in fig. 4, the specific process of establishing the network connection may be:

layer 1 sends a request network (request network) to layer 2, and layer 2 sends a request network (request network) to layer 3. Layer 3 sends a request NETWORK (request NETWORK) to layer 4, layer 4 feeds back a NETWORK request FACTORY (request NETWORK function) to layer 3, and layer 4 feeds back an EVENT REGISTER NETWORK FACTORY (EVENT _ REGISTER _ NETWORK _ factor) to layer 3. Layer 3 is connected (connect) with layer 5, and sends all request providers (allrequesttopprovider), layer 3 sends request network (request network) to layer 4, layer 5 sends networking (onenetworkfor) to layer 4, and layer 5 sends request network (requestnetworklnternal) to layer 4. Layer 4 sends a request network (requestNetwork) to layer 5. Layer 5 sends a request network (requestNetwork) to layer 6, and layer 6 sends an enabled apn (enablepann) to layer 5. Layer 6 sends setup data (setappdata) to layer 5. Layer 5 sends a create data connection (CreatDataConnection) to layer 7 and a propose bringap to layer 7.

Therefore, the data network identification corresponding to the application program is transferred through the preset transfer function independent of the android system, the limitation of the android operating system can be broken through, the DNN corresponding to the application program can be accurately and reliably directly transmitted to the AP layer, the DNN and the slice ID are bound on the AP layer, and the purpose that the cloud service application program uses the proprietary network slice service is achieved.

In some embodiments, the received is sent by the operator server; the routing policy may further include a routing policy version identifier corresponding to an application other than the target application.

Referring to table 2, in table 2, taking the target application as the cloud live broadcast, and taking a program other than the target application as the default as an example, an association relationship between the routing policy version identifier, the data network identifier, and the network slice identifier of the target application is shown.

TABLE 2

Application program	Routing policy version identification	DNN identification	Network slice identification
				Cloud live broadcast	1	DNN-0	S-NSSA1-0
default	0	DNN-1	S-NSSA1-1

Alternatively, as shown in table 3, a routing policy version name may also be included.

TABLE 3

Application program	Routing policy version name	Routing policy version identification	DNN identification	Network slice identification
					Cloud live broadcast	Yunzhibo-URSP Vesion	1	DNN-0	S-NSSA1-0
default	default-URSP Vesion	0	DNN-1	S-NSSA1-1

Therefore, when the incidence relation between the target data network identification and the target network slice identification corresponding to the target application program is established, the routing strategy version identification can be added. Therefore, on one hand, the user terminal can directly determine the routing strategy version corresponding to the target application program, session connection is established between the routing strategy version and the network slice according to the routing strategy version, a target network slice identifier is not required to be determined according to the incidence relation between the data network identifier and the network slice identifier, and then the network slice corresponding to the target network slice identifier is determined to be in session connection with the network slice, so that the data sending efficiency can be further improved. On the other hand, by adding the routing strategy version corresponding to the target application program, the user terminal can realize the session connection between the user terminal and the target network slice by matching the routing strategy version identification, and the data network identification, the network slice identification and the routing strategy version identification are updated only when the routing strategy is subjected to version update, so that the updating and matching times of the routing strategy can be reduced to a certain extent, and the resource consumption is reduced.

In some embodiments, the routing policy may further include a routing policy corresponding to an application other than the target application.

Thus, to enable normal use of applications other than the target application, default routing policies may be configured for the applications, taking into account that the applications may not have corresponding separate DNNs and network slices. Therefore, when accessing the application programs except the target application program, the session connection can be established according to the default routing strategy and the network slice corresponding to the default routing strategy, so as to ensure the normal access of the application program.

In some embodiments, the ue may establish a session connection with a User Port Function (UPF) through an Access and mobility management Function (AMF) and a Session Management Function (SMF), and the specific implementation formula may be as follows:

In this embodiment, the user terminal may send the target data network identifier and the target network slice identifier corresponding to the target application program to the AMF and the SMF, and the AMF and the SMF may determine the UPF corresponding to the target application program according to the target data network identifier and the target network slice identifier, and establish a session connection between the user terminal and the UPF corresponding to the target application program. Therefore, the session connection between the user terminal and the corresponding UPF can be established through the AMF and the SMF, and the problem of the network element address selection of core networks such as the AMF, the SMF, the UPF and the like is solved.

As shown in fig. 5, fig. 5 illustrates a schematic diagram of establishing a session connection between a user terminal and a UPF corresponding to a target application, where a routing policy includes a routing policy version identifier. In fig. 5, the developer represents a developer of the target application, and the URSP subscription is a routing policy (UE route selection policy, URSP) that the developer signs with the operator before online use of the target application. As shown in fig. 5, if the URSP version identifier corresponding to the target application is 1, which is denoted by DNN-1 in fig. 5, AMF and SMF may establish a session connection between the user terminal and UPF 1; if the target application does not correspond to a single network slice, it may be considered that the application corresponds to a preset routing policy, which is denoted by defaultDNN-0 in fig. 5, and AMF and SMF may establish a session connection between the user terminal and the UPF 0.

The above detailed description of the data transmission method applied to the user terminal provided in the embodiment of the present application also provides a data transmission method applied to an operator server based on the data transmission method applied to the user terminal. As shown in fig. 6, the data transmission method may include the steps of:

s610, receiving a registration request of a target application program sent by a user terminal.

S620, sending a routing strategy to the user terminal according to the registration request.

As one example, the routing policy may include a network slice identification corresponding to the target application.

The principle of implementing the data transmission method applied to the operator server provided in this embodiment is similar to the principle of the method embodiments shown in fig. 1 to fig. 3, and can achieve the same technical effect, and for brevity, no further description is given here.

Based on the same inventive concept, the present application further provides a data transmitting apparatus 700. As shown in fig. 7, the data transmitting apparatus 700 may specifically include:

a receiving module 710, configured to receive an access request of a target application, where the access request may include a target data network identifier corresponding to the target application;

a determining module 720, configured to determine, according to an association relationship between the data network identifier and the network slice identifier, a target network slice identifier associated with the target data network identifier;

a connection module 730, configured to establish a session connection of a target network slice corresponding to the network slice identifier;

the sending module 740 may be configured to send the data of the target application to the cloud server through the session connection.

In one embodiment, the data transmission apparatus 700 may further include:

the registration module can be used for sending a registration request of a target application program to an operator server;

the policy receiving module can be used for receiving a routing policy sent by the operator server according to the registration request, wherein the routing policy comprises a network slice identifier corresponding to the target application program;

and the association module can be used for associating the data network identifier corresponding to the target application program with the network slice identifier.

In an embodiment, the policy receiving module may be specifically configured to:

the association module may specifically include:

the first transmission unit can be used for transmitting the routing strategy to an AP layer of an operating system application processor through a BP;

the second transmission unit may be configured to transmit the target data network identifier of the target application to the AP layer through a preset transfer function;

and the associating unit may be configured to associate, at the AP layer, the network slice identifier with the data network identifier corresponding to the target application.

In one embodiment, the routing policy may further include a routing policy version identification corresponding to the target application.

In one embodiment, the routing policy may also include routing policies corresponding to applications other than the target application.

In an embodiment, the connection module 630 may be specifically configured to:

It should be noted that each module in the data sending apparatus shown in fig. 7 has a function of implementing each step of the data sending method shown in fig. 3, and can achieve the corresponding technical effect, and for brevity, no further description is given here.

Based on the same inventive concept, the present application also provides a data transmission device, as shown in fig. 8, which may include a processor 801 and a memory 802 storing computer program instructions.

Specifically, the processor 801 may include a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits configured to implement the embodiments of the present invention.

Memory 802 may include mass storage for data or instructions. By way of example, and not limitation, memory 802 may include a Hard Disk Drive (HDD), a floppy Disk Drive, flash memory, an optical Disk, a magneto-optical Disk, a tape, or a Universal Serial Bus (USB) Drive or a combination of two or more of these. Memory 802 may include removable or non-removable (or fixed) media, where appropriate. The memory 802 may be internal or external to the integrated gateway disaster recovery device, where appropriate. In one embodiment, the memory 802 is a non-volatile solid-state memory. In one embodiment, memory 802 comprises Read Only Memory (ROM). Where appropriate, the ROM may be mask-programmed ROM, Programmable ROM (PROM), Erasable PROM (EPROM), Electrically Erasable PROM (EEPROM), electrically rewritable ROM (EAROM), or flash memory or a combination of two or more of these.

The processor 801 reads and executes the computer program instructions stored in the memory 802 to implement any data transmission method in the foregoing embodiments, and achieve the corresponding technical effect achieved by executing the method/step in the embodiment shown in fig. 3, and for brevity, no further description is provided here.

In one example, the data transmission device may also include a communication interface 803 and a bus 810. As shown in fig. 8, the processor 801, the memory 802, and the communication interface 803 are connected via a bus 810 to complete communication therebetween.

The communication interface 803 is mainly used for implementing communication between modules, apparatuses, units and/or devices in the embodiments of the present invention.

Bus 810 includes hardware, software, or both to couple the components of the data transmission device to each other. By way of example, and not limitation, bus 810 may include Accelerated Graphics Port (AGP) or other graphics bus, Enhanced Industry Standard Architecture (EISA) bus, Front Side Bus (FSB), Hyper Transport (HT) interconnect, Industry Standard Architecture (ISA) bus, infiniband interconnect, Low Pin Count (LPC) bus, memory bus, Micro Channel Architecture (MCA) bus, Peripheral Component Interconnect (PCI) bus, PCI-Express (PCI-X) bus, Serial Advanced Technology Attachment (SATA) bus, video electronics standards association local (VLB) bus, or other suitable bus or a combination of two or more of these. Bus 810 may include one or more buses, where appropriate. Although specific buses have been described and illustrated with respect to embodiments of the invention, any suitable buses or interconnects are contemplated by the invention.

In addition, in combination with the data transmission method in the foregoing embodiment, the embodiment of the present invention may be implemented by providing a computer storage medium. The computer storage medium having computer program instructions stored thereon; the computer program instructions, when executed by a processor, implement any of the data transmission methods of the above embodiments.

It is to be understood that the invention is not limited to the specific arrangements and instrumentality described above and shown in the drawings. A detailed description of known methods is omitted herein for the sake of brevity. In the above embodiments, several specific steps are described and shown as examples. However, the method processes of the present invention are not limited to the specific steps described and illustrated, and those skilled in the art can make various changes, modifications and additions or change the order between the steps after comprehending the spirit of the present invention.

The functional blocks shown in the above-described structural block diagrams may be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, it may be, for example, an electronic circuit, an Application Specific Integrated Circuit (ASIC), suitable firmware, plug-in, function card, or the like. When implemented in software, the elements of the invention are the programs or code segments used to perform the required tasks. The program or code segments may be stored in a machine-readable medium or transmitted by a data signal carried in a carrier wave over a transmission medium or a communication link. A "machine-readable medium" may include any medium that can store or transfer information. Examples of a machine-readable medium include electronic circuits, semiconductor memory devices, ROM, flash memory, Erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, Radio Frequency (RF) links, and so forth. The code segments may be downloaded via computer networks such as the internet, intranet, etc.

It should also be noted that the exemplary embodiments mentioned in this patent describe some methods or systems based on a series of steps or devices. However, the present invention is not limited to the order of the above-described steps, that is, the steps may be performed in the order mentioned in the embodiments, may be performed in an order different from the order in the embodiments, or may be performed simultaneously.

As described above, only the specific embodiments of the present invention are provided, and it can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the system, the module and the unit described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again. It should be understood that the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive various equivalent modifications or substitutions within the technical scope of the present invention, and these modifications or substitutions should be covered within the scope of the present invention.

Claims

1. A data transmission method is applied to a user terminal, and comprises the following steps:

and sending the data of the target application program to a cloud server through the session connection.

2. The method of claim 1, further comprising:

receiving a routing strategy sent by the operator server according to the registration request, wherein the routing strategy comprises a network slice identifier corresponding to the target application program;

3. The method of claim 2, wherein the receiving the routing policy sent by the operator server according to the registration request comprises:

receiving a non-access stratum (NAS) message sent by the operator server through a Baseband Processor (BP), wherein the NAS message comprises a routing strategy;

the associating the data network identifier corresponding to the target application program with the network slice identifier includes:

transmitting the routing strategy to an AP layer of an application processor of an operating system through the BP;

transmitting the target data network identification of the target application program to the AP layer through a preset transfer function;

and associating the data network identification corresponding to the target application program with the network slice identification on the AP layer.

4. The method of claim 2 or 3, wherein the routing policy further comprises a routing policy version identification corresponding to the target application.

5. The method of claim 2 or 3, wherein the routing policy further comprises a routing policy corresponding to an application outside the target application.

6. The method of claim 1, wherein establishing a session connection for a target network slice corresponding to the network slice identifier comprises:

and sending the target data network identifier and the target network slice identifier to a mobile management function AMF and a session management function SMF, so that the AMF and the SMF establish session connection between the terminal and a user plane function UPF corresponding to the target data network identifier and the target network slice identifier.

7. A data transmission method is applied to an operator server and comprises the following steps:

8. A data transmission apparatus, comprising:

the system comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving an access request of a target application program, and the access request comprises a target data network identifier corresponding to the target application program;

the determining module is used for determining a target network slice identifier associated with the target data network identifier according to the association relationship between the data network identifier and the network slice identifier;

the connection module is used for establishing session connection of the target network slice corresponding to the network slice identifier;

and the sending module is used for sending the data of the target application program to a cloud server through the session connection.

9. A data transmission apparatus, characterized in that the apparatus comprises: a processor and a memory storing computer program instructions;

the processor, when executing the computer program instructions, implements the data transmission method of any one of claims 1-7.

10. A storage medium having stored thereon computer program instructions which, when executed by a processor, implement a data transmission method according to any one of claims 1 to 7.