WO2022001192A1 - 应用数据的传输方法、终端及系统 - Google Patents

应用数据的传输方法、终端及系统 Download PDF

Info

Publication number
WO2022001192A1
WO2022001192A1 PCT/CN2021/081093 CN2021081093W WO2022001192A1 WO 2022001192 A1 WO2022001192 A1 WO 2022001192A1 CN 2021081093 W CN2021081093 W CN 2021081093W WO 2022001192 A1 WO2022001192 A1 WO 2022001192A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
terminal
app
slice
information
Prior art date
Application number
PCT/CN2021/081093
Other languages
English (en)
French (fr)
Inventor
刘彬俊
于晓靓
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to US18/013,502 priority Critical patent/US20230289432A1/en
Priority to EP21832898.7A priority patent/EP4163808A4/en
Publication of WO2022001192A1 publication Critical patent/WO2022001192A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/51—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/302—Route determination based on requested QoS
    • H04L45/306—Route determination based on the nature of the carried application
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/03—Indexing scheme relating to G06F21/50, monitoring users, programs or devices to maintain the integrity of platforms
    • G06F2221/033—Test or assess software
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/66—Layer 2 routing, e.g. in Ethernet based MAN's

Definitions

  • the embodiments of the present application relate to the field of terminals, and in particular, to a method, terminal, and system for transmitting application data.
  • each application market (or application store, also called application platform) will perform uniqueness verification on the application to ensure the uniqueness of the application.
  • application platform When users download and install applications from such platforms, counterfeit applications may be installed, causing counterfeit applications to occupy high-priority resources of the operator.
  • the present application proposes a method, terminal and system for transmitting application data.
  • the network device can indicate the App Store Id and App Id to the terminal through URSP information, so that the Only applications that match the App Store Id and App Id in the terminal can route data to the slice network indicated by the URSP information, thereby avoiding the problem of counterfeit applications occupying the operator's resources and effectively improving resource utilization.
  • a first aspect provides a transmission system for application data, the system includes a network device and a terminal; the network device is used to send a first message to the terminal, the first message includes URSP information, and the URSP information includes App Store Id, App Id and slices Parameter information, App Store Id is used to identify the app store, App Id is used to identify the application, and slice parameter information is used to indicate the slice network.
  • the terminal is used to run the first application, and transmit the data of the first application through the slice network indicated by the slice parameter information, wherein the first application is from the application store indicated by the App Store Id of the USRP information, and the App Id of the first application is in the URSP information.
  • the App Id is the same. In this way, the terminal can route the data of the application with the same App Store Id and App Id indicated by the URSP information to the slice network, so as to avoid the problem of counterfeit applications occupying the operator's resources and effectively improve the resource utilization.
  • the terminal is further configured to run the second application, and transmit the data of the second application through the non-slicing network, wherein the download source of the second application is not the application store indicated by the App Store Id of the USRP information, and the App Store of the second application
  • the Id is the same or different from the App Id in the URSP information.
  • the terminal can transmit the applications that fail to match the App Store Id and App Id indicated by the URSP information through the non-slicing network to further avoid the problem of counterfeit applications occupying the operator's resources and effectively improve the resource utilization.
  • the terminal if a protocol data unit PUD session corresponding to the slice network indicated by the slice parameter information has been established between the terminal and the network device, the terminal is used to The data of the first application is transmitted on the slice network indicated by the slice parameter information. In this way, the terminal can transmit the data of the application based on the established PDU session, so as to realize the binding applied to the PDU session.
  • the terminal if a PUD session corresponding to the slice network indicated by the slice parameter information is not established between the terminal and the network device, the terminal is used to communicate with the network device based on the slice parameter information.
  • a PDU session is established, and based on the PDU session, data of the first application is transmitted on the slice network indicated by the slice parameter information.
  • the terminal can newly establish a PDU session for the application, and the terminal can transmit data of the application based on the established PDU session, so as to realize the binding applied to the PDU session.
  • the URSP information further includes an operating system identifier OS Id, which is used to identify the operating system; the OS Id of the operating system of the terminal is the same as the OS Id in the URSP information.
  • OS Id operating system identifier
  • the network device can indicate to the corresponding terminal the App Store Id and App Id corresponding to the operating system of the terminal for different operating systems, that is to say, the present application can be applied to each current operating system.
  • the URSP information further includes indication information, which is used to indicate that the URSP information includes the App Store Id and the App Id.
  • indication information which is used to indicate that the URSP information includes the App Store Id and the App Id.
  • the terminal can determine that the URSP includes the App Store Id and the App Id by reading the indication information.
  • the network device is further configured to send a second message to the terminal, where the second message includes allowed network slice selection assistance information Allowed NSSAI, which is used to indicate that the terminal is allowed to transmit data Slice network set; the slice network indicated by the slice parameter information is included in the slice network set.
  • the terminal can learn the slice network that the network device allows the terminal to route, and in the case of the slice network indicated by the slice parameter information, route the application data to the slice network indicated by the slice parameter information.
  • the terminal is further configured to send a registration message to the network device for registering and access the network device, or the terminal is further configured to send a service update message to the network device , used to indicate service update in the terminal.
  • the terminal can trigger the network device to issue the URSP information in the case of registering to the network or updating the service.
  • the App Id is the application package name of the application.
  • the application market can verify the validity and uniqueness of the application based on the application registration of the application to ensure the uniqueness of the App Id contained in the URSP information.
  • the application store is an application collection including one or more applications.
  • a terminal including: a processor and a memory, the memory is coupled to the processor; the memory stores program instructions, and when the program instructions are executed by the processor, the terminal performs the following steps: receiving a first message, the first message includes the terminal device routing policy URSP information, the URSP information includes the application store identifier App Store Id, the application identifier App Id and slice parameter information, the App Store Id is used to identify the application store, the App Id is used to identify the application, the slice The parameter information is used to indicate the slice network; run the first application, and transmit the data of the first application through the slice network indicated by the slice parameter information, wherein the first application comes from the application store indicated by the App Store Id of the USRP information, and the App of the first application The Id is the same as the App Id in the URSP information.
  • the terminal when the program instructions are executed by the processor, the terminal is caused to perform the following steps: run the second application, and transmit the data of the second application through the non-slicing network, wherein the download source of the second application is not the App Store of USRP information In the application store indicated by Id, the App Id of the second application is the same or different from the App Id in the URSP information.
  • the terminal when the program instructions are executed by the processor, the terminal is caused to perform the following steps: a network device corresponding to the slice network indicated by the slice parameter information has been established between the terminal and the network device.
  • the protocol data unit PUD session based on the PDU session, transmits the data of the first application on the slice network indicated by the slice parameter information.
  • the terminal when the program instructions are executed by the processor, the terminal is caused to perform the following steps: if the terminal and the network device have not established a network corresponding to the slice indicated by the slice parameter information
  • the protocol data unit PUD session based on the slice parameter information, establishes a PDU session with the network device, and based on the PDU session, transmits the data of the first application on the slice network indicated by the slice parameter information.
  • the URSP information further includes an operating system identifier OS Id, which is used to identify the operating system; the OS Id of the operating system of the terminal is the same as the OS Id in the URSP information.
  • OS Id operating system identifier
  • the URSP information further includes indication information, which is used to indicate that the URSP information includes the App Store Id and the App Id.
  • the program instructions when executed by the processor, the program instructions cause the terminal to perform the following steps: receiving a second message from the network device, where the second message includes an allowed network slice selection
  • the auxiliary information Allowed NSSAI is used to indicate that the terminal is allowed to transmit the data slice network set; the slice network indicated by the slice parameter information is included in the slice network set.
  • the terminal when the program instructions are executed by the processor, the terminal causes the terminal to perform the following steps: sending a registration message to the network device for registering and accessing the network device, or, A service update message is sent to the network device to indicate service update in the terminal.
  • the App Id is the application package name of the application.
  • the application store is an application collection including one or more applications.
  • a method for transmitting application data comprising: a terminal receiving a first message from a network device, where the first message includes terminal device routing policy URSP information, and the URSP information includes an application store identifier App Store Id, an application identifier App Id and slice parameter information, the App Store Id is used to identify the application store, the App Id is used to identify the application, and the slice parameter information is used to indicate the slice network; the terminal runs the first application, and transmits the first application through the slice network indicated by the slice parameter information.
  • the first application is from the application store indicated by the App Store Id of the USRP information, and the App Id of the first application is the same as the App Id in the URSP information.
  • the method further includes: the terminal runs the second application, and transmits the data of the second application through the non-slicing network, wherein the download source of the second application is not the application store indicated by the App Store Id of the USRP information, and the second application's download source is not the application store indicated by the App Store Id of the USRP information.
  • the App Id is the same or different from the App Id in the URSP information.
  • transmitting the data of the first application through the slice network indicated by the slice parameter information includes: if the slice network indicated by the slice parameter information has been established between the terminal and the network device The corresponding protocol data unit PUD session, based on the PDU session, transmits the data of the first application on the slice network indicated by the slice parameter information.
  • transmitting the data of the first application through the slice network indicated by the slice parameter information includes: if the slice network indicated by the slice parameter information is not established between the terminal and the network device For the corresponding protocol data unit PUD session, the terminal establishes a PDU session with the network device based on the slice parameter information, and transmits the data of the first application on the slice network indicated by the slice parameter information based on the PDU session.
  • the URSP information further includes an operating system identifier OS Id, which is used to identify the operating system; the OS Id of the operating system of the terminal is the same as the OS Id in the URSP information.
  • OS Id operating system identifier
  • the URSP information further includes indication information, which is used to indicate that the URSP information includes the App Store Id and the App Id.
  • the method before the terminal receives the first message from the network device, the method further includes: the terminal receives a second message from the network device, where the second message includes an allowed network slice selection
  • the auxiliary information Allowed NSSAI is used to indicate that the terminal is allowed to transmit the data slice network set; the slice network indicated by the slice parameter information is included in the slice network set.
  • the method before receiving the second message from the network device, the method further includes: the terminal sending a registration message to the network device for registering and accessing the network device, or, the terminal A service update message is sent to the network device to indicate service update in the terminal.
  • the App Id is the application package name of the application.
  • an application store is an application collection including one or more applications.
  • a network device comprising a processor and a memory, the memory is coupled to the processor; the memory stores program instructions, and when the program instructions are executed by the processor, the network device is made to perform the following steps: sending a first message to the terminal , the first message includes URSP information, the URSP information includes App Store Id, App Id, and slice parameter information, where the App Store Id is used to identify the application store, the App Id is used to identify the application, and the slice parameter information is used to indicate the slice network.
  • the slice parameter information is used to instruct the slice network to receive the data of the first application sent by the terminal, wherein the first application is from the application store indicated by the App Store Id in the USRP information, and the App Id of the first application is the same as the App Id in the URSP information. Id are the same.
  • a fifth aspect provides a method for transmitting application data, comprising: a network device sending a first message to a terminal, the first message including URSP information, the URSP information including App Store Id, App Id and slice parameter information, and the App Store Id is used for Identifies the app store, the App Id is used to identify the application, and the slice parameter information is used to indicate the slice network.
  • the network device uses the slice parameter information to instruct the slice network to receive the data of the first application sent by the terminal, wherein the first application comes from the application store indicated by the App Store Id of the USRP information, and the App Id of the first application and the URSP information are in the application store.
  • the App Id is the same.
  • a device for transmitting application data comprising: a transceiver module and a processing module, the transceiver module is configured to receive a first message from a network device, the first message includes terminal equipment routing policy URSP information, and the URSP information includes App store identifier App Store Id, application identifier App Id, and slice parameter information, App Store Id is used to identify the app store, App Id is used to identify the application, and slice parameter information is used to indicate the slice network; processing module, used to run the first application , the transceiver module is also used to transmit the data of the first application through the slice network indicated by the slice parameter information, wherein the first application comes from the application store indicated by the App Store Id of the USRP information, and the App Id of the first application is from the URSP information.
  • the App Id is the same.
  • a seventh aspect provides a device for transmitting application data, comprising a transceiver module for sending a first message to a terminal, the first message including URSP information, the URSP information including App Store Id, App Id and slice parameter information, App Store Id Used to identify the app store, App Id is used to identify the application, and slice parameter information is used to indicate the slice network.
  • the slice parameter information is used to instruct the slice network to receive the data of the first application sent by the terminal, wherein the first application is from the application store indicated by the App Store Id in the USRP information, and the App Id of the first application is the same as the App Id in the URSP information. Id are the same.
  • a chip in an eighth aspect, includes a processing circuit and a transceiver pin.
  • the transceiver pin and the processing circuit communicate with each other through an internal connection path, and the processing circuit executes the method in the third aspect or any implementation manner of the third aspect to control the receiving pin to receive signals to control the transmission pin sends a signal.
  • an embodiment of the present application provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program, and the computer program includes at least a piece of code, and at least a piece of code can be executed by a terminal to control the terminal to execute the third aspect or the third aspect.
  • the method in any one implementation manner of the three aspects.
  • an embodiment of the present application provides a computer program, where the computer program includes instructions for executing the method in the third aspect or any implementation manner of the third aspect.
  • FIG. 1 is a schematic diagram of a hardware structure of a terminal provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of a software structure of a terminal provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a communication system provided by an embodiment of the present application.
  • Fig. 4 is the format schematic diagram of the URSP shown by way of example.
  • FIG. 5 is a schematic diagram of an exemplary user interface
  • FIG. 6 is a schematic diagram of an exemplary user interface
  • FIG. 7 is a schematic flowchart of a method for transmitting application data provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of the format of an exemplary URSP
  • FIG. 9 is a schematic diagram of an exemplary user interface
  • FIG. 10 is a schematic diagram of the format of an exemplary URSP
  • FIG. 11 is a schematic diagram of the format of an exemplary URSP
  • FIG. 12 is a schematic structural diagram of a terminal provided by an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of an apparatus provided by an embodiment of the present application.
  • first and second in the description and claims of the embodiments of the present application are used to distinguish different objects, rather than to describe a specific order of the objects.
  • first target object, the second target object, etc. are used to distinguish different target objects, rather than to describe a specific order of the target objects.
  • words such as “exemplary” or “for example” are used to represent examples, illustrations or illustrations. Any embodiments or designs described in the embodiments herein as “exemplary” or “such as” should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as “exemplary” or “such as” is intended to present the related concepts in a specific manner.
  • multiple processing units refers to two or more processing units; multiple systems refers to two or more systems.
  • the application in the terminal may also be referred to as an application program or application software, which is not limited in this application.
  • a terminal may be referred to as a terminal, a terminal, a user equipment (user equipment, UE), or the like.
  • the terminal can be a mobile phone, a tablet computer, a wearable device, a vehicle-mounted device, an augmented reality (AR)/virtual reality (VR) device, a laptop, an ultra-mobile personal computer (UMPC) , netbook, personal digital assistant (personal digital assistant, PDA) and other devices that can access the network.
  • AR augmented reality
  • VR virtual reality
  • UMPC ultra-mobile personal computer
  • PDA personal digital assistant
  • FIG. 1 shows a schematic structural diagram of the terminal 100 .
  • the terminal 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, Mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, sensor module 180, buttons 190, motor 191, indicator 192, camera 193, display screen 194, and user Identity module (subscriber identification module, SIM) card interface 195 and so on.
  • SIM subscriber identification module
  • the sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, and ambient light. Sensor 180L, bone conduction sensor 180M, etc.
  • the terminal 100 may include more or less components than shown, or some components may be combined, or some components may be separated, or different component arrangements.
  • the illustrated components may be implemented in hardware, software, or a combination of software and hardware.
  • the processor 110 may include one or more processing units, for example, the processor 110 may include an application processor (application processor, AP), a modem processor (Modem), a graphics processor (graphics processing unit, GPU), an image processor Image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and/or neural-network processing unit , NPU) etc. Wherein, different processing units may be independent devices, or may be integrated in one or more processors.
  • application processor application processor, AP
  • Modem modem
  • GPU graphics processor
  • ISP image processor Image signal processor
  • DSP digital signal processor
  • NPU neural-network processing unit
  • different processing units may be independent devices, or may be integrated in one or more processors.
  • the controller may be the nerve center and command center of the terminal 100 .
  • the controller can generate an operation control signal according to the instruction operation code and timing signal, and complete the control of fetching and executing instructions.
  • a memory may also be provided in the processor 110 for storing instructions and data.
  • the memory in processor 110 is cache memory. This memory may hold instructions or data that have just been used or recycled by the processor 110 . If the processor 110 needs to use the instruction or data again, it can be called directly from the memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby increasing the efficiency of the system.
  • the processor 110 may include one or more interfaces.
  • the interface may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous transceiver (universal asynchronous transmitter) receiver/transmitter, UART) interface, mobile industry processor interface (MIPI), general-purpose input/output (GPIO) interface, subscriber identity module (SIM) interface, and / or universal serial bus (universal serial bus, USB) interface, etc.
  • I2C integrated circuit
  • I2S integrated circuit built-in audio
  • PCM pulse code modulation
  • PCM pulse code modulation
  • UART universal asynchronous transceiver
  • MIPI mobile industry processor interface
  • GPIO general-purpose input/output
  • SIM subscriber identity module
  • USB universal serial bus
  • the USB interface 130 is an interface that conforms to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, and the like.
  • the USB interface 130 can be used to connect a charger to charge the terminal 100, and can also be used to transmit data between the terminal 100 and peripheral devices. It can also be used to connect headphones to play audio through the headphones.
  • the interface can also be used to connect other electronic devices, such as AR devices.
  • the interface connection relationship between the modules illustrated in the embodiments of the present application is only a schematic illustration, and does not constitute a structural limitation of the terminal 100 .
  • the terminal 100 may also adopt different interface connection manners in the foregoing embodiments, or a combination of multiple interface connection manners.
  • the charging management module 140 is used to receive charging input from the charger.
  • the charger may be a wireless charger or a wired charger.
  • the charging management module 140 may receive charging input from the wired charger through the USB interface 130 .
  • the charging management module 140 may receive wireless charging input through the wireless charging coil of the terminal 100 . While the charging management module 140 charges the battery 142 , it can also supply power to the terminal through the power management module 141 .
  • the power management module 141 is used for connecting the battery 142 , the charging management module 140 and the processor 110 .
  • the power management module 141 receives input from the battery 142 and/or the charging management module 140 and supplies power to the processor 110 , the internal memory 121 , the external memory, the display screen 194 , the camera 193 , and the wireless communication module 160 .
  • the power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle times, battery health status (leakage, impedance).
  • the power management module 141 may also be provided in the processor 110 .
  • the power management module 141 and the charging management module 140 may also be provided in the same device.
  • the wireless communication function of the terminal 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modulation and demodulation processor, the baseband processor, and the like.
  • the terminal 100 may implement audio functions through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, an application processor, and the like. Such as music playback, recording, etc.
  • the audio module 170 is used for converting digital audio information into analog audio signal output, and also for converting analog audio input into digital audio signal. Audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be provided in the processor 110 , or some functional modules of the audio module 170 may be provided in the processor 110 .
  • Speaker 170A also referred to as a "speaker" is used to convert audio electrical signals into sound signals.
  • the terminal 100 can listen to music through the speaker 170A, or listen to a hands-free call.
  • the receiver 170B also referred to as "earpiece" is used to convert audio electrical signals into sound signals.
  • the voice can be answered by placing the receiver 170B close to the human ear.
  • the microphone 170C also called “microphone” or “microphone” is used to convert sound signals into electrical signals.
  • the user can make a sound near the microphone 170C through the human mouth, and input the sound signal into the microphone 170C.
  • the terminal 100 may be provided with one or more microphones 170C.
  • the terminal 100 may be provided with two microphones 170C, which can implement a noise reduction function in addition to collecting sound signals.
  • the terminal 100 may further be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, and implement directional recording functions.
  • the earphone jack 170D is used to connect wired earphones.
  • the earphone interface 170D may be the USB interface 130, or may be a 3.5mm open mobile terminal platform (OMTP) standard interface, a cellular telecommunications industry association of the USA (CTIA) standard interface.
  • OMTP open mobile terminal platform
  • CTIA cellular telecommunications industry association of the USA
  • the terminal 100 implements a display function through a GPU, a display screen 194, an application processor, and the like.
  • the GPU is a microprocessor for image processing, and is connected to the display screen 194 and the application processor.
  • the GPU is used to perform mathematical and geometric calculations for graphics rendering.
  • Processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.
  • Display screen 194 is used to display images, videos, and the like.
  • Display screen 194 includes a display panel.
  • the display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (active-matrix organic light).
  • LED diode AMOLED
  • flexible light-emitting diode flexible light-emitting diode (flex light-emitting diode, FLED), Miniled, MicroLed, Micro-oLed, quantum dot light-emitting diode (quantum dot light emitting diodes, QLED) and so on.
  • the terminal 100 may include one or N display screens 194 , where N is a positive integer greater than one.
  • the terminal 100 can realize the shooting function through the ISP, the camera 193, the video codec, the GPU, the display screen 194 and the application processor.
  • the ISP is used to process the data fed back by the camera 193 .
  • the shutter is opened, the light is transmitted to the camera photosensitive element through the lens, the light signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing, and converts it into an image visible to the naked eye.
  • ISP can also perform algorithm optimization on image noise, brightness, and skin tone.
  • ISP can also optimize the exposure, color temperature and other parameters of the shooting scene.
  • the ISP may be provided in the camera 193 .
  • Camera 193 is used to capture still images or video.
  • the object is projected through the lens to generate an optical image onto the photosensitive element.
  • the photosensitive element may be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor.
  • CMOS complementary metal-oxide-semiconductor
  • the photosensitive element converts the optical signal into an electrical signal, and then transmits the electrical signal to the ISP to convert it into a digital image signal.
  • the ISP outputs the digital image signal to the DSP for processing.
  • DSP converts digital image signals into standard RGB, YUV and other formats of image signals.
  • the terminal 100 may include 1 or N cameras 193 , where N is a positive integer greater than 1.
  • a digital signal processor is used to process digital signals, in addition to processing digital image signals, it can also process other digital signals. For example, when the terminal 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the energy of the frequency point, and so on.
  • Video codecs are used to compress or decompress digital video.
  • Terminal 100 may support one or more video codecs.
  • the terminal 100 can play or record videos in various encoding formats, for example, moving picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4, and so on.
  • MPEG moving picture experts group
  • the NPU is a neural-network (NN) computing processor.
  • NN neural-network
  • Applications such as intelligent cognition of the terminal 100 can be implemented through the NPU, such as image recognition, face recognition, speech recognition, text understanding, and the like.
  • the external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal 100.
  • the external memory card communicates with the processor 110 through the external memory interface 120 to realize the data storage function. For example to save files like music, video etc in external memory card.
  • Internal memory 121 may be used to store computer executable program code, which includes instructions.
  • the processor 110 executes various functional applications and data processing of the terminal 100 by executing the instructions stored in the internal memory 121 .
  • the internal memory 121 may include a storage program area and a storage data area.
  • the storage program area may store an operating system, an application program required for one or more functions (such as a sound playback function, an image playback function, etc.), and the like.
  • the storage data area may store data (such as audio data, phone book, etc.) created during the use of the terminal 100 and the like.
  • the internal memory 121 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, universal flash storage (UFS), and the like.
  • the keys 190 include a power-on key, a volume key, and the like. Keys 190 may be mechanical keys. It can also be a touch key.
  • the terminal 100 may receive key input and generate key signal input related to user settings and function control of the terminal 100 .
  • Motor 191 can generate vibrating cues.
  • the motor 191 can be used for vibrating alerts for incoming calls, and can also be used for touch vibration feedback.
  • touch operations acting on different applications can correspond to different vibration feedback effects.
  • the motor 191 can also correspond to different vibration feedback effects for touch operations on different areas of the display screen 194 .
  • Different application scenarios for example: time reminder, receiving information, alarm clock, games, etc.
  • the touch vibration feedback effect can also support customization.
  • the indicator 192 can be an indicator light, which can be used to indicate the charging state, the change of the power, and can also be used to indicate a message, a missed call, a notification, and the like.
  • the SIM card interface 195 is used to connect a SIM card.
  • the SIM card can be contacted and separated from the terminal 100 by inserting into the SIM card interface 195 or pulling out from the SIM card interface 195 .
  • the terminal 100 may support 1 or N SIM card interfaces, where N is a positive integer greater than 1.
  • the SIM card interface 195 can support Nano SIM card, Micro SIM card, SIM card and so on. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The types of the plurality of cards may be the same or different.
  • the SIM card interface 195 can also be compatible with different types of SIM cards.
  • the SIM card interface 195 is also compatible with external memory cards.
  • the terminal 100 interacts with the network through the SIM card to realize functions such as calls and data communication.
  • the terminal 100 employs an eSIM, ie an embedded SIM card.
  • the eSIM card can be embedded in the terminal 100 and cannot be separated from the terminal 100 .
  • the software system of the terminal 100 may adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture.
  • the embodiments of the present application take an Android system with a layered architecture as an example to exemplarily describe the software structure of the terminal 100 .
  • FIG. 2 is a block diagram of a software structure of the terminal 100 according to the embodiment of the present application.
  • the layered architecture divides the software into several layers, and each layer has a clear role and division of labor. Layers communicate with each other through software interfaces.
  • the Android system is divided into four layers, which are, from top to bottom, an application layer, an application framework layer, an Android runtime (Android runtime) and a system library, and a kernel layer.
  • the application layer can include a series of application packages.
  • the application package can include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, chat, etc.
  • the application framework layer provides an application programming interface (application programming interface, API) and a programming framework for applications in the application layer.
  • the application framework layer includes some predefined functions.
  • the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, and the like.
  • a window manager is used to manage window programs.
  • the window manager can get the size of the display screen, determine whether there is a status bar, lock the screen, take screenshots, etc.
  • Content providers are used to store and retrieve data and make these data accessible to applications.
  • the data may include video, images, audio, calls made and received, browsing history and bookmarks, phone book, etc.
  • the view system includes visual controls, such as controls for displaying text, controls for displaying pictures, and so on. View systems can be used to build applications.
  • a display interface can consist of one or more views.
  • the display interface including the short message notification icon may include a view for displaying text and a view for displaying pictures.
  • the telephony manager is used to provide the communication function of the terminal 100 .
  • the management of call status including connecting, hanging up, etc.).
  • the resource manager provides various resources for the application, such as localization strings, icons, pictures, layout files, video files and so on.
  • the notification manager enables applications to display notification information in the status bar, which can be used to convey notification-type messages, and can disappear automatically after a brief pause without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc.
  • the notification manager can also display notifications in the status bar at the top of the system in the form of graphs or scroll bar text, such as notifications of applications running in the background, and notifications on the screen in the form of dialog windows. For example, text information is prompted in the status bar, a prompt tone is issued, the terminal vibrates, and the indicator light flashes.
  • Android Runtime includes core libraries and a virtual machine. Android runtime is responsible for scheduling and management of the Android system.
  • the core library consists of two parts: one is the function functions that the java language needs to call, and the other is the core library of Android.
  • the application layer and the application framework layer run in virtual machines.
  • the virtual machine executes the java files of the application layer and the application framework layer as binary files.
  • the virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, safety and exception management, and garbage collection.
  • a system library can include multiple functional modules. For example: surface manager (surface manager), media library (media library), 3D graphics processing library (eg: OpenGL ES), 2D graphics engine (eg: SGL), etc.
  • surface manager surface manager
  • media library media library
  • 3D graphics processing library eg: OpenGL ES
  • 2D graphics engine eg: SGL
  • the Surface Manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications.
  • the media library supports playback and recording of a variety of commonly used audio and video formats, as well as still image files.
  • the media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.
  • the 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.
  • 2D graphics engine is a drawing engine for 2D drawing.
  • the kernel layer is the layer between hardware and software.
  • the kernel layer contains at least display drivers, camera drivers, audio drivers, and sensor drivers.
  • FIG. 3 it is a schematic diagram of a communication system according to an embodiment of the present application.
  • the communication system includes a terminal and a core network.
  • the number of terminals may be one or more, and the number of terminals in the communication system shown in FIG. 3 is only an example of adaptability, which is not limited in this application.
  • the core network includes one or more core network devices.
  • the core network device may be an access and mobility management function (AMF), which is mainly responsible for access control, mobility Management (mobility management, MM), attach and detach, and gateway selection functions.
  • AMF access and mobility management function
  • the core network device involved in the embodiments of the present application is not limited to the AMF.
  • the fifth generation (5th Generation, 5G) communication system introduces the concept of network slicing.
  • the network slicing technology can realize the division of a physical network into multiple virtual networks.
  • a virtual network is regarded as a "network slice", and each network slice is independent of each other.
  • Different protocol data unit (PDU) sessions in a terminal may require network slices corresponding to the PDU sessions to provide services.
  • PDU protocol data unit
  • a network slice is a logical network (Network Slice: A logical network that provides specific network capabilities and network characteristics). It can be a logical network with different network capabilities and network characteristics customized according to different service requirements or tenants on the physical or virtual network infrastructure.
  • a network slice consists of a set of network functions and their required resources (eg, computing resources, storage resources, network resources).
  • the network slices supported by each cell are configured by the operation, administration and maintenance system (operation, administration and maintenance, OAM).
  • OAM operation, administration and maintenance
  • S-NSSAI Single network slice selection assistance information
  • the S-NSSAI includes at least one of the following: slice type and service type (slice/service type, SST) information, optionally, the S-NSSAI may also include slice differentiater information (slice differentiator, SD).
  • the SST information is used to indicate the behavior of the network slice, such as the characteristics of the network slice and the service type
  • the SD information is the supplementary information of the SST. For example, if the SST points to multiple network slices, the SD can assist in corresponding to a unique network slice. .
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable low latency communications
  • mMTC massive machine type communication
  • the network slices corresponding to PDU sessions of different types of services may be different.
  • different applications in the terminal may correspond to different service types, that is, applications in the terminal may correspond to different network slices.
  • the same service type may correspond to different network slices due to different operators or service providers. That is, the network slice may provide network resources for at least one PDU session of the terminal.
  • "whitelist” or "blacklist” applications can also be set. For example, when the terminal device runs the first application, so the first application is a whitelisted application, the terminal device can use the slice The resource interacts with the network side. It can be understood that when the terminal device runs the second application, the second application is a non-whitelisted application, and the sliced resource is not used; similarly, the application in the blacklist can be prohibited from using network switching, Second, non-blacklisted applications can use sliced resources.
  • the core network sends a UE route selection policy (UE route selection policy, URSP) to the terminal, and the URSP can be used to indicate the traffic characteristics that need to be transmitted on the slice network and the activation of the slice network.
  • URSP UE route selection policy
  • the terminal can determine the routing mode of data (which can be understood as data of applications of different service types), and the routing mode includes specific routing to which slice, or using a non-slicing network to transmit data.
  • FIG. 4 is a schematic diagram of the format of the URSP exemplarily shown, the URSP includes but is not limited to: a URSP rule length (Length of URSP rule) field, a URSP rule priority (Precedence value of URSP rule) field, traffic Length of Traffic descriptor field, Traffic descriptor field, Length of Route selection descriptor list field, and Route selection descriptor field.
  • a URSP rule length Length of URSP rule
  • URSP rule priority Precedence value of URSP rule
  • the Route selection descriptor list field is used to carry the slice network activation parameters, and the slice network activation parameters include but are not limited to: parameters such as S-NSSAI corresponding to one or more slices.
  • the Traffic descriptor field is used to carry the above-mentioned information (or parameters) corresponding to the traffic characteristics that need to be transmitted on the slice.
  • information or parameters
  • Traffic descriptor component type identifier (traffic descriptor field type definition)
  • OS Id+OS App Id type OS ID+OS App ID type
  • IPv4 remote address type ipv4 remote address type
  • IPv6 remote address/prefix length type ipv6 remote address/prefix length type
  • Protocol identifier/next header type (protocol identifier/next header type)
  • Remote port range type (remote port range type)
  • Security parameter index type (security parameter index type)
  • Destination MAC address type (destination MAC address type)
  • 802.1Q S-TAG VID type (802.1Q service tag virtual local area network identifier type)
  • OS Id+OS App Id constitutes application descriptors (Application descriptors) information, which is used to identify applications in the operating system. It can also be understood that Application descriptors can be used to indicate which applications in the operating system can transmit data through the slice network.
  • OS Id is used to identify the operating system
  • OS App Id is used to identify the application in the operating system.
  • the OS App Id (hereinafter referred to as the App Id) corresponding to the application in the Android operating system is the application Package name, the Android operating system defines App Id as follows:
  • Every Android application has a unique application ID, like the Java package name, such as com.example.myapp. This ID uniquely identifies your app across the device manufacturer and the Google Play Store. If you're uploading a new version of your app, the app ID (and the certificate used to sign it) is, for example, the same as the original APK. If you change the app ID, the Google Play Store treats that Android application package (APK) as a completely different app. Therefore, after publishing your app, the app ID should never be changed.
  • API Android application package
  • the App Id in the Android operating system is specified by the app developer in the development program, such as build.gradle.
  • the app developer publishes the app on the Android app market (such as Huawei App Market or Google Play)
  • the app market will verify the App Id
  • the uniqueness of the app that is, as mentioned above, if the App Id is different, it will be considered as two completely different applications. Therefore, the app market can guarantee the uniqueness of the App Id in the app market.
  • FIG. 5 is a schematic diagram of a user usage scenario exemplarily shown.
  • the terminal can download the application through the Huawei AppGallery in the mobile phone.
  • the user can download and install the chat application by clicking on the screen.
  • the terminal device can obtain the identification information of the application, for example, the version number of the application, the supported operating system type OS Id, the App Id number and other information, the identification information can also be obtained when the terminal device runs the application (for example, running in the foreground) for the first time.
  • the terminal device When the terminal device needs to exchange data with the core network, for example, when sending a voice message, the terminal can compare the obtained OS Id and App Id with the OS Id+OS App Id type indicated in the URSP pre-delivered by the core network.
  • the OS Id and the App Id (that is, the OS App Id) are matched. If the match is successful, the data of the chat application is routed to the specified slice for transmission according to the instructions of the URSP. If the match is unsuccessful, the data is transmitted over the non-sliced network.
  • users may download apps through the adb install (Android Debug Bridge install) tool or from the download page provided by a third-party server.
  • the third-party server does not provide App Ids
  • the validity is verified, so the map application downloaded by the user may be a counterfeit application, wherein the App Id (for example, the application package name) of the counterfeit application is consistent with the App Id of any application in the application market.
  • the App Id for example, the application package name
  • FIG. 6 a user can access a download page provided by a third-party server through a mobile phone to download a map application.
  • the terminal downloads the map application from the third-party server through the download page according to the user's instruction.
  • the application package name of the map application is the same as the application package name of the chat application in the Huawei AppGallery, that is, the App Id is the same.
  • the terminal will successfully match the App Id of the map application (that is, the same counterfeit Id as the chat application) with the OS App Id in the URSP, and route the data of the map application to this site according to the instructions of the URSP. This is the transmission on the slice corresponding to the chat application.
  • the slice corresponding to the chat application is a high-priority slice
  • the slice that the map application should correspond to is a low-priority slice
  • the transmission method that the map application should correspond to is non-3GPP transmission, that is, it does not transmit through slices, because
  • the map application uses a fake App Id, which makes the map application occupy high-priority slices for transmission, resulting in a waste of operator resources.
  • the embodiment of the present application proposes a method for transmitting application data, which uses the AppStore Id and App Id in the URSP, so that when the terminal verifies the application, the AppStore Id and the App Id are combined, thereby solving the problem that the App Id is counterfeited.
  • the terminal is described as a UE.
  • FIG. 7 is a schematic flowchart of a method for transmitting application data in an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of a method for transmitting application data in an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of a method for transmitting application data in an embodiment of the present application.
  • Step 101 the Modem sends a Registration request message to the core network.
  • a registration process will be initiated. For example, after the mobile phone (ie, the UE) is powered on, a registration process will be initiated. Alternatively, after the user refreshes the mobile phone, a registration process will also be initiated.
  • the registration process can be understood as the mobile phone registering to access the network. For details, refer to the UE registration process in the existing standard, which will not be repeated in this application.
  • the Modem of the UE sends a registration request (Registration request) message to the core network for requesting to initiate a registration process.
  • the message may carry information such as registration type, security parameters, etc.
  • registration request Registration request
  • the registration process in the existing standard, which will not be repeated in this application.
  • Step 102a the core network sends a registration accept (Registration accept) message to the Modem.
  • the core network approves the UE to register and join the network, it sends a Registration accept message to the UE, and the message carries one or more parameters used to instruct the terminal to access the core network.
  • the Registration accept message carries allowed network slice selection assistance information (Allowed NSSAI), which is used to indicate one or more slices that the terminal is allowed to access.
  • Allowed NSSAI allowed network slice selection assistance information
  • Step 102b the Modem transmits the Allowed NSSAI to the Framework.
  • the Modem in the UE can be used to receive and parse the message from the core network, and forward the information carried in the message to the Framework. It should be noted that this article only takes the Modem as an example for description. In fact, the device or chip or software program used in the UE for receiving, parsing and forwarding information from the core network is not limited to the Modem.
  • Step 103 Framwork saves the Allowed NSSAI.
  • Framwork saves the Allowed NSSAI to a storage unit, such as the memory of the UE, for use in subsequent establishment of a PDU session.
  • Step 104a the core network sends a management terminal policy command message (Manage UE policy command) message to the Modem.
  • a management terminal policy command message Manage UE policy command
  • the core network sends a Manage UE policy command message to the UE, which includes but is not limited to URSP.
  • the description of the Traffic descriptor field in the URSP is as follows:
  • FIG. 8 is a schematic diagram of the format of the URSP exemplarily shown.
  • the URSP includes but is not limited to the Traffic descriptor field, and other fields are not shown in FIG. 8 .
  • the Traffic descriptor field includes one or more Traffic descriptor component type identifier fields, and each Traffic descriptor component type identifier field may include any of the enumeration values listed above, for example, the Traffic descriptor component type identifier field includes an enumeration The value [0 0 0 0 0 0 0 1] is used to indicate that the information carried by the subsequent code stream (until the next Traffic descriptor component type identifier field) is Match-all type.
  • OS Id+AppStore Id+OS App Id type is taken as an example in FIG. 8 .
  • Traffic descriptor field may also include code streams corresponding to other types, which will not be repeated in this application.
  • the Traffic descriptor component type identifier field includes [0 0 0 0 1 0 0 0], which is used to indicate that the information carried by the subsequent code stream (until the next Traffic descriptor component type identifier field) is OS Id+AppStore Id +OS App Id type, including OS Id, AppStore Id and App Id.
  • OS Id length Length of OS Id
  • OS Id field OS Id field
  • number of AppStore Ids Number of AppStore Ids
  • Length of AppStore Id fields one or more AppStore Id fields
  • App Id fields Length of App Id fields, App Id fields.
  • the Length of OS Id field is used to indicate the length of the OS Id field, or it can also be understood as being used to indicate the length of the OS Id. It should be noted that the length of the field or information referred to in this application refers to the length of the occupied time domain resource, for example, 3 symbol bits or 3 bits are occupied. Exemplarily, the length of the Length of OS Id field is 1 byte.
  • the OS Id field is used to indicate the identification information of the operating system, that is, it carries the OS Id.
  • Num of AppStore Ids field used to indicate the number of reliable app marketplaces or app stores.
  • the field length is 1 byte.
  • Length of AppStore Id field used to indicate the length of the AppStore Id field.
  • the field length is 1 byte.
  • the AppStore Id field is used to indicate the App Store, or the AppStore Id that may be called an App Platform, App Market, etc.
  • the reliable AppStore in the Android operating system can include, but is not limited to: google play, Huawei App Store, etc.
  • the AppStore Id is the result of negotiation between the core network and each application market, and the core network stores the AppStore Id of one or more AppStores corresponding to different operating systems.
  • the core network will verify the legality of each application market, that is, the AppStore Id corresponding to the application market whose legality verification is successful will be carried in the URSP.
  • the core network can obtain the operating system information of the UE, that is, the information (or parameters) such as the OS Id, AppStore Id and APP Id in the URSP are all related to the UE.
  • the information corresponding to the operating system in the UE is, for example, the OS Id corresponding to the operating system of the UE, the AppStore Id of the application market corresponding to the operating system of the UE, and the ID corresponding to the application in the operating system of the UE.
  • the Num of AppStore Ids field can be used to indicate that the number of app stores contained in the operating system corresponding to the OS Id is 2, that is, the following code stream will contain 2 Length of AppStore Id fields, and 2 AppStore Id field.
  • one of the AppStore Id fields carries the AppStore Id of Huawei AppGallery
  • the other AppStore Id field carries the AppStore Id of Goolge Play. It should be noted that, the "behind" of the fields involved in this application all refer to the context in the time domain, which will not be repeated hereinafter.
  • Length of App Id field used to indicate the length of the App Id field.
  • the length of the Length of App Id field is 1 byte.
  • the App Id field is used to indicate the App Id of the application, that is, it carries one or more App Ids. It should be noted that the App Id carried in the App Id field is the App Id verified by each application market. Optionally, multiple App Ids included in the App Id field can be separated by a separator to distinguish different App Ids. The separation method is only a schematic example, which is not limited in this application. Optionally, the App Id field may also include multiple App Id subfields, and each App Id subfield carries an App Id.
  • the core network stores the App Ids of each application corresponding to the application market of the operating system, and one or more App Ids carried in the App Id field of the URSP are the same as those in each application market in the operating system of the UE. corresponding to the application.
  • one or more App Ids carried in the App Id field of the URSP sent by the core network to the UE are the App Ids of the Huawei AppGallery in the Android operating system and the applications in Google Play.
  • the App Id in the App Id field refers to the application whose data needs to be routed to the slicing network, that is, only the App Id of the application in the App Market that needs to be routed to the slicing network will be carried in the App Id field , the data of the application not in the App Id field will be transmitted through the non-slicing network.
  • Step 104b the Modem transmits the URSP to the Framework.
  • the Modem receives and parses the Manage UE policy command message to obtain the URSP, and transmits the URSP to the URSP.
  • Step 105 the Framework saves the URSP.
  • the Framework After the Framework obtains the URSP transmitted from the Modem, it decodes and checks the validity of the URSP to obtain parameters and information carried by each field in the URSP.
  • the information stored in the Framework includes but is not limited to: OS Id, AppStore Id, and App Id.
  • the above information may be stored in the memory, which is not limited in this application.
  • the storing of the URSP in this application refers to storing the parameters and information carried in the URSP, which will not be described in detail below.
  • Step 106a the Framework sends a Manage UE policy complete message.
  • the Framework After the Framework successfully saves the parameters included in the URSP, it sends a Manage UE policy complete message to the Modem to indicate that the Framework has successfully processed the URSP.
  • the Framework if the Framework fails to parse the URSP or the Framework fails to save the URSP due to other reasons, the Framework sends a Manage UE policy command reject message to the Modem, and the Modem forwards the message to the core network.
  • Step 106b the Modem sends the Manage UE policy complete message to the core network.
  • Step 107 the App is started.
  • the user can download and install the chat application in the Huawei application market. After the application is installed, the user can start the chat application by clicking on the screen, as shown in FIG. 9 .
  • Step 108 the Framework obtains the OS Id, AppStore Id, and App Id.
  • the Framework can monitor the application to the foreground, and the Framework can obtain the OS Id of the UE's operating system, the App Id of the chat application, and the installation source (that is, the download source) of the chat application, that is, the AppStore of Huawei AppGallery Id.
  • the OS Id of the operating system may be stored in the memory, and the Framework may call the OS Id through an interface or program instruction.
  • the App Id may be the application package name of the chat application, and the Framework may retrieve the application package name from a related file (for example, an application description file) of the application.
  • the installation source of the chat application can also be included in the related files of the application, and the Framework can retrieve the information of the installation source through an interface, program instruction or tool, for example, getInstallerPackageName in FrameworkPackageManager.java to obtain the installation source of the chat application. , which is the AppStore ID of Huawei AppGallery.
  • Step 109 the Framework verifies the OS Id, AppStore Id, and App Id.
  • the Framework matches the OS Id, AppStore Id and App Id with the OS Id and one or more AppStore Ids and one or more App Ids in the URSP saved in step 105. If the OS Id, AppStore Id and App Id If all matches are successful, that is to say, they all exist in the URSP issued by the core network, then the Framework determines that the OS Id, AppStore Id, and App Id verification are successful, and the data of the application (such as a chat application) can be routed to the slice network.
  • the OS Id, AppStore Id and App Id If all matches are successful, that is to say, they all exist in the URSP issued by the core network, then the Framework determines that the OS Id, AppStore Id, and App Id verification are successful, and the data of the application (such as a chat application) can be routed to the slice network.
  • the Framework determines that the verification fails, and the data of the application cannot be routed to the slicing network, that is, transmitted through the non-slicing network. .
  • the terminal downloads the map application through the webpage provided by the third-party server according to the user's instruction
  • the Framework monitors the map application before and after, obtains the OS Id, and installs the map application Source and App Id (same as chat app), where the installation source can be a web page URL.
  • Framewrok verifies the OS Id.
  • the OS Id exists in the URSP, and the OS Id verification is successful.
  • Framewrok verifies the installation source of the map application, that is, the web page URL.
  • the web page URL does not exist in the AppStore Id indicated by the URSP.
  • Framewrok determines that the verification of the installation source has failed, that is, even if the App Id of the map application is the same as the App Id of the chat application that needs to be routed to the slice network, because the verification of the installation source of the map application fails, in the follow-up In the process, the Framework does not allow the data of the map application to be transmitted through the slice network, thereby reducing the overhead of the operator's network.
  • Step 110 the Framework binds the App to the slice.
  • the Framework after the Framework successfully verifies the OS Id, AppStore Id, and App Id, it can further obtain the information about the chat application based on other information in the URSP, such as the above-mentioned slice network activation parameters, etc.
  • the corresponding slice and other related information of the slice such as the NSSAI of the slice.
  • the Framework may match the NSSAI of the slice with the Allowed NSSAI stored in step 103 to determine whether the core network allows the data of the UE to be routed to the slice.
  • the Framework detects that the PDU session corresponding to the slice is not established, it needs to trigger the PDU session establishment process. Referring to FIG. 7 , the method further includes:
  • Step 110a the Framework sends a PDU session establishment request message to the Modem.
  • Step 110b the Modem sends a PDU session establishment request message to the core network.
  • the Framework initiates a PDU session establishment process to the core network to establish a PDU session corresponding to the slice of the chat application.
  • the PDU session establishment request message carries the NSSAI of the slice corresponding to the chat application.
  • Step 110c the core network sends a PDU seesion establishment success message to the Modem.
  • Step 110d the Modem sends a PDU seesion establishment success message to the Framework.
  • the core network establishes the PDU session of the slice corresponding to the NSSAI based on the received PDU session establishment request message, and returns a PDU session establishment success message to the Modem after the PDU session establishment is successful.
  • PDU seesion establishment process may refer to the PDU seesion establishment process specified in the existing standards, which will not be repeated in this application.
  • binding may mean that the Framework records the App Id of the chat application in correspondence with the relevant information (such as traffic interface or routing table entry) of the PDU seesion in the memory, so that after the Framework detects the data corresponding to the App Id. , determine the PDU seesion bound to the App Id, and route the chat application data to the slice corresponding to the PDU seesion.
  • the Framework detects that the PDU session of the slice corresponding to the chat application has been established, the Framework directly applies the chat to the PDU session binding without executing the PDU session establishment process.
  • steps 107 to 110 may be repeatedly performed after the applications are initially started.
  • the data transmission process may be directly performed, that is, the data of the application is routed to the corresponding slice.
  • the description of the Traffic descriptor field can be as follows:
  • the value of the Traffic descriptor component type identifier field is [00001000], which is used to indicate AppStore Id+OS App Id type, that is, the subsequent code stream includes AppStore Id and App Id, but not OS Id.
  • FIG. 10 is a schematic diagram of the format of the Traffic descriptor field corresponding to the description of the above Traffic descriptor field.
  • the description of each field can refer to the above, and will not be repeated here.
  • the OS Id may not be included in the URSP.
  • the Framework in step 108, the Framework only obtains the AppStore Id and App Id corresponding to the started application. And, in step 109, the Framework verifies the AppStore Id and the App Id, and other details are still consistent with the description in FIG. 7, and are not repeated in this embodiment.
  • the description of the Traffic descriptor field can be as follows:
  • the rules in the 3GPP standard are still used to indicate the OS Id+OS App Id type, that is, the subsequent code stream includes the OS Id and the OS App Id.
  • the value of the Traffic descriptor component type identifier field is [1 0 1 0 0 0 0 0], it is used to indicate AppStore Id+App Id type, that is, the subsequent code stream includes AppStore Id and App Id.
  • FIG. 11 is a schematic diagram of the format of the Traffic descriptor field corresponding to the description of the above Traffic descriptor field.
  • the description of each field can refer to the above, and will not be repeated here.
  • the registration process will also be initiated.
  • the user modifies the carrier package of the mobile phone.
  • the user can modify the carrier package through the carrier APP of the mobile phone. , and the mobile phone will notify the core network operator that the package has been modified.
  • the user can also call the operator to change the operator package, and the operator can directly change the user's operator package in the core network.
  • the core network will re-send the URSP to the UE, that is, repeat steps 104a to 110.
  • the chat application is bound to PDU session1, and the chat application's The data is routed to slice 1.
  • the UE may be triggered to re-establish a PDU session 2 corresponding to the chat application with the core network, and the data of the chat application is routed to slice 2.
  • slice 2 may have a lower priority than slice 1, and the above examples are only illustrative, and are not limited in this application.
  • the terminal includes corresponding hardware and/or software modules for executing each function.
  • the present application can be implemented in hardware or a combination of hardware and computer software in conjunction with the algorithm steps of the examples described in conjunction with the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functionality for each particular application in conjunction with the embodiments, but such implementations should not be considered beyond the scope of this application.
  • the terminal may be divided into functional modules according to the foregoing method example.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware. It should be noted that, the division of modules in this embodiment is schematic, and is only a logical function division, and there may be other division manners in actual implementation.
  • FIG. 12 shows a schematic structural diagram of a terminal 200.
  • the terminal 200 includes a transceiving module 201, a processing module 202, and a transceiving module 201, which are used for receiving first data from a network device.
  • the first message includes terminal device routing policy URSP information
  • the URSP information includes App Store Id, App Id and slice parameter information
  • the App Store Id is used to identify the application store
  • the App Id is used to identify application
  • the slice parameter information is used to indicate the slice network
  • the processing module 202 is used to run the first application.
  • the transceiver module 201 is further configured to transmit the data of the first application through the slice network indicated by the slice parameter information, wherein the first application comes from the application store indicated by the App Store Id of the USRP information, and the first application is from the application store indicated by the App Store Id of the USRP information.
  • the App Id of an application is the same as the App Id in the URSP information.
  • the processing module 202 is further configured to run a second application
  • the transceiver module 201 is further configured to transmit data of the second application through a non-slicing network, wherein the download source of the second application is not In the application store indicated by the App Store Id of the USRP information, the App Id of the second application is the same or different from the App Id in the URSP information.
  • the transceiver module 201 is further configured to: if a protocol data unit PUD session corresponding to the slice network indicated by the slice parameter information has been established between the terminal and the network device, based on the PDU session, and transmit the data of the first application on the slice network indicated by the slice parameter information.
  • the transceiver module 201 is further configured to: if a protocol data unit PUD session corresponding to the slice network indicated by the slice parameter information has not been established between the terminal and the network device, the The terminal establishes a PDU session with the network device based on the slice parameter information, and transmits data of the first application on the slice network indicated by the slice parameter information based on the PDU session.
  • the URSP information further includes an operating system identification OS Id, which is used to identify the operating system; the OS Id of the operating system of the terminal is the same as the OS Id in the URSP information.
  • OS Id operating system identification
  • the URSP information further includes indication information, which is used to indicate that the URSP information includes App Store Id and App Id.
  • the transceiver module 201 is further configured to receive a second message from the network device, where the second message includes the allowed network slice selection assistance information Allowed NSSAI, which is used to indicate that the terminal is allowed to transmit data A slice network set; the slice network indicated by the slice parameter information is included in the slice network set.
  • the transceiver module 201 is further configured to send a registration message to the network device to register and access the network device, or to send a service update message to the network device to indicate Service update in the terminal.
  • the App Id is the application package name of the application.
  • the application store is an application collection including one or more applications.
  • FIG. 13 shows a schematic block diagram of an apparatus 300 according to an embodiment of the present application.
  • the apparatus 300 may include: a processor 301 , a transceiver/transceiver pin 302 , and optionally, a memory 303 .
  • bus system 304 includes a power bus, a control bus and a status signal bus in addition to a data bus.
  • bus system 304 includes a power bus, a control bus and a status signal bus in addition to a data bus.
  • bus system 304 includes a power bus, a control bus and a status signal bus in addition to a data bus.
  • bus system 304 includes a power bus, a control bus and a status signal bus in addition to a data bus.
  • bus system 304 includes a power bus, a control bus and a status signal bus in addition to a data bus.
  • the memory 303 may be used for the instructions in the foregoing method embodiments.
  • the processor 301 can be used to execute the instructions in the memory 303, and control the receive pins to receive signals, and control the transmit pins to transmit signals.
  • This embodiment also provides a computer storage medium, where computer instructions are stored in the computer storage medium, and when the computer instructions are executed on the terminal, the terminal executes the above-mentioned relevant method steps to implement the application data transmission method in the above-mentioned embodiment.
  • This embodiment also provides a computer program product, which when the computer program product runs on a computer, causes the computer to execute the above-mentioned relevant steps, so as to implement the method in the above-mentioned embodiment.
  • This embodiment also provides a system including a terminal and a network server, which can implement the methods in the foregoing embodiments.
  • the embodiments of the present application also provide an apparatus, which may specifically be a chip, a component or a module, and the apparatus may include a connected processor and a memory; wherein, the memory is used for storing computer execution instructions, and when the apparatus is running, The processor can execute the computer-executed instructions stored in the memory, so that the chip executes the methods in the foregoing method embodiments.
  • the terminal, computer storage medium, computer program product or chip provided in this embodiment are all used to execute the corresponding method provided above. Therefore, for the beneficial effects that can be achieved, reference may be made to the corresponding method provided above. The beneficial effects of , will not be repeated here.
  • the disclosed apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of modules or units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or May be integrated into another device, or some features may be omitted, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • Units described as separate components may or may not be physically separated, and components shown as units may be one physical unit or multiple physical units, that is, may be located in one place, or may be distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a readable storage medium.
  • a readable storage medium including several instructions to make a device (which may be a single chip microcomputer, a chip, etc.) or a processor (processor) to execute all or part of the steps of the methods in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read only memory (ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other media that can store program codes.

Abstract

一种应用数据的传输方法、终端及系统，该方法包括：终端接收来自网络设备的第一消息，第一消息包括终端设备路由选择策略URSP信息，URSP信息包括应用商店标识App Store Id、应用标识App Id和切片参数信息，App Store Id用于标识应用商店，App Id用于标识应用，切片参数信息用于指示切片网络；终端运行第一应用，通过切片参数信息指示的切片网络传输第一应用的数据，其中，第一应用来自USRP信息的App Store Id指示的应用商店，第一应用的App Id与URSP信息中的App Id相同。上述方法避免仿冒应用对运营商资源的占用，有效提升资源利用率。

Description

应用数据的传输方法、终端及系统
本申请要求于2020年6月30日提交中国专利局、申请号为202010615517.7、申请名称为“应用数据的传输方法、终端及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及终端领域，尤其涉及一种应用数据的传输方法、终端及系统。
背景技术
随着终端的使用场景越来越广泛，为满足不同使用场景下的用户的需求，终端中的应用也越来越多。目前，各应用市场(或应用商店，也可以称为应用平台)均会对应用进行唯一性校验，以保证应用的唯一性，但是，对于其它可下载应用的平台，尤其是不具备对应用的唯一性进行校验的平台，当用户从该类平台下载并安装应用时，可能会安装仿冒应用，导致仿冒应用占用运行商的高优先级资源。
发明内容
为了解决现有技术中存在的上述技术问题，本申请提出了一种应用数据的传输方法、终端及系统，该方法中，网络设备可通过URSP信息向终端指示App Store Id和App Id，以使终端中符合App Store Id和App Id的应用才能将数据路由到URSP信息指示的切片网络上，从而避免仿冒应用占用运行商资源的问题，有效提升了资源利用率。
第一方面，提供一种应用数据的传输系统，该系统包括网络设备与终端；网络设备用于向终端发送第一消息，第一消息包括URSP信息，URSP信息包括App Store Id、App Id和切片参数信息，App Store Id用于标识应用商店，App Id用于标识应用，切片参数信息用于指示切片网络。终端用于运行第一应用，通过切片参数信息指示的切片网络传输第一应用的数据，其中，第一应用来自USRP信息的App Store Id指示的应用商店，第一应用的App Id与URSP信息中的App Id相同。这样，终端可将与URSP信息指示的App Store Id和App Id相同的应用的数据路由到切片网络，以避免仿冒应用占用运行商资源的问题，有效提升了资源利用率。
根据第一方面，终端还用于运行第二应用，通过非切片网络传输第二应用的数据，其中，第二应用的下载来源非USRP信息的App Store Id指示的应用商店，第二应用的App Id与URSP信息中的App Id相同或不同。这样，终端可将与URSP信息指示的App Store Id和App Id匹配不成功的应用，通过非切片网络传输，以进一步避免仿冒应用占用运行商资源的问题，有效提升了资源利用率。
根据第一方面，或者以上第一方面的任意一种实现方式，若终端与网络设备之间已 建立与切片参数信息指示的切片网络对应的协议数据单元PUD会话，终端用于基于PDU会话，在切片参数信息指示的切片网络上传输第一应用的数据。这样，终端可基于已建立的PDU会话，传输应用的数据，以实现应用于PDU会话的绑定。
根据第一方面，或者以上第一方面的任意一种实现方式，若终端与网络设备之间未建立与切片参数信息指示的切片网络对应的PUD会话，终端用于基于切片参数信息，与网络设备建立PDU会话，并基于PDU会话，在切片参数信息指示的切片网络上传输第一应用的数据。这样，终端可为应用新建立PDU会话，终端可基于已建立的PDU会话，传输应用的数据，以实现应用于PDU会话的绑定。
根据第一方面，或者以上第一方面的任意一种实现方式，URSP信息还包括操作系统标识OS Id，用于标识操作系统；终端的操作系统的OS Id与URSP信息中的OS Id相同。这样，网络设备可针对不同的操作系统，向对应的终端指示与终端的操作系统对应的App Store Id和App Id，也就是说，本申请可以应用于目前的各操作系统中。
根据第一方面，或者以上第一方面的任意一种实现方式，URSP信息还包括指示信息，用于指示URSP信息中包括App Store Id和App Id。这样，终端可通过读取指示信息，确定URSP中包括App Store Id和App Id。
根据第一方面，或者以上第一方面的任意一种实现方式，网络设备还用于向终端发送第二消息，第二消息包括允许的网络切片选择辅助信息Allowed NSSAI，用于指示允许终端传输数据切片网络集合；切片参数信息指示的切片网络包含于切片网络集合中。这样，终端可获知网络设备允许终端路由的切片网络，并在切片参数信息指示的切片网络的情况下，将应用的数据路由到切片参数信息指示的切片网络上。
根据第一方面，或者以上第一方面的任意一种实现方式，终端还用于向网络设备发送注册消息，用于注册并接入网络设备，或者，终端还用于向网络设备发送业务更新消息，用于指示终端中的业务更新。这样，终端可在注册入网或者业务更新的情况下，触发网络设备下发URSP信息。
根据第一方面，或者以上第一方面的任意一种实现方式，App Id为应用的应用包名。这样，应用市场可基于应用的应用报名，对应用的合法性及唯一性进行校验，以保证URSP信息中包含的App Id的唯一性。
根据第一方面，或者以上第一方面的任意一种实现方式，应用商店为包括一个或多个应用的应用集合。
第二方面，提供一种终端，包括：处理器和存储器，存储器与处理器耦合；存储器 存储有程序指令，程序指令由处理器执行时，使得终端执行下述步骤：接收来自网络设备的第一消息，第一消息包括终端设备路由选择策略URSP信息，URSP信息包括应用商店标识App Store Id、应用标识App Id和切片参数信息，App Store Id用于标识应用商店，App Id用于标识应用，切片参数信息用于指示切片网络；运行第一应用，通过切片参数信息指示的切片网络传输第一应用的数据，其中，第一应用来自USRP信息的App Store Id指示的应用商店，第一应用的App Id与URSP信息中的App Id相同。
根据第二方面，程序指令由处理器执行时，使得终端执行下述步骤：运行第二应用，通过非切片网络传输第二应用的数据，其中，第二应用的下载来源非USRP信息的App Store Id指示的应用商店，第二应用的App Id与URSP信息中的App Id相同或不同。
根据第二方面，或者以上第二方面的任意一种实现方式，程序指令由处理器执行时，使得终端执行下述步骤：终端与网络设备之间已建立与切片参数信息指示的切片网络对应的协议数据单元PUD会话，基于PDU会话，在切片参数信息指示的切片网络上传输第一应用的数据。
根据第二方面，或者以上第二方面的任意一种实现方式，程序指令由处理器执行时，使得终端执行下述步骤：若终端与网络设备之间未建立与切片参数信息指示的切片网络对应的协议数据单元PUD会话，基于切片参数信息，与网络设备建立PDU会话，并基于PDU会话，在切片参数信息指示的切片网络上传输第一应用的数据。
根据第二方面，或者以上第二方面的任意一种实现方式，URSP信息还包括操作系统标识OS Id，用于标识操作系统；终端的操作系统的OS Id与URSP信息中的OS Id相同。
根据第二方面，或者以上第二方面的任意一种实现方式，URSP信息还包括指示信息，用于指示URSP信息中包括App Store Id和App Id。
根据第二方面，或者以上第二方面的任意一种实现方式，程序指令由处理器执行时，使得终端执行下述步骤：接收来自网络设备的第二消息，第二消息包括允许的网络切片选择辅助信息Allowed NSSAI，用于指示允许终端传输数据切片网络集合；切片参数信息指示的切片网络包含于切片网络集合中。
根据第二方面，或者以上第二方面的任意一种实现方式，程序指令由处理器执行时，使得终端执行下述步骤：向网络设备发送注册消息，用于注册并接入网络设备，或者，向网络设备发送业务更新消息，用于指示终端中的业务更新。
根据第二方面，或者以上第二方面的任意一种实现方式，App Id为应用的应用包名。
根据第二方面，或者以上第二方面的任意一种实现方式，应用商店为包括一个或多个应用的应用集合。
第三方面，提供一种应用数据的传输方法，包括：终端接收来自网络设备的第一消息，第一消息包括终端设备路由选择策略URSP信息，URSP信息包括应用商店标识App Store Id、应用标识App Id和切片参数信息，App Store Id用于标识应用商店，App Id用于标识应用，切片参数信息用于指示切片网络；终端运行第一应用，通过切片参数信息指示的切片网络传输第一应用的数据，其中，第一应用来自USRP信息的App Store Id指示的应用商店，第一应用的App Id与URSP信息中的App Id相同。
根据第三方面，方法还包括：终端运行第二应用，通过非切片网络传输第二应用的数据，其中，第二应用的下载来源非USRP信息的App Store Id指示的应用商店，第二应用的App Id与URSP信息中的App Id相同或不同。
根据第三方面，或者以上第三方面的任意一种实现方式，通过切片参数信息指示的切片网络传输第一应用的数据包括：若终端与网络设备之间已建立与切片参数信息指示的切片网络对应的协议数据单元PUD会话，基于PDU会话，在切片参数信息指示的切片网络上传输第一应用的数据。
根据第三方面，或者以上第三方面的任意一种实现方式，通过切片参数信息指示的切片网络传输第一应用的数据包括：若终端与网络设备之间未建立与切片参数信息指示的切片网络对应的协议数据单元PUD会话，终端基于切片参数信息，与网络设备建立PDU会话，并基于PDU会话，在切片参数信息指示的切片网络上传输第一应用的数据。
根据第三方面，或者以上第三方面的任意一种实现方式，URSP信息还包括操作系统标识OS Id，用于标识操作系统；终端的操作系统的OS Id与URSP信息中的OS Id相同。
根据第三方面，或者以上第三方面的任意一种实现方式，URSP信息还包括指示信息，用于指示URSP信息中包括App Store Id和App Id。
根据第三方面，或者以上第三方面的任意一种实现方式，终端接收来自网络设备的第一消息之前，还包括：终端接收来自网络设备的第二消息，第二消息包括允许的网络切片选择辅助信息Allowed NSSAI，用于指示允许终端传输数据切片网络集合；切片参数信息指示的切片网络包含于切片网络集合中。
根据第三方面，或者以上第三方面的任意一种实现方式，接收来自网络设备的第二消息之前，还包括：终端向网络设备发送注册消息，用于注册并接入网络设备，或者，终端向网络设备发送业务更新消息，用于指示终端中的业务更新。
根据第三方面，或者以上第三方面的任意一种实现方式，App Id为应用的应用包名。
根据第三方面，或者以上第三方面的任意一种实现方式，应用商店为包括一个或多个应用的应用集合。
第四方面，提供一种网络设备，包括处理器和存储器，存储器与处理器耦合；存储器存储有程序指令，程序指令由处理器执行时，使得网络设备执行下述步骤：向终端发送第一消息，第一消息包括URSP信息，URSP信息包括App Store Id、App Id和切片参数信息，App Store Id用于标识应用商店，App Id用于标识应用，切片参数信息用于指示切片网络。通过所述切片参数信息用于指示切片网络接收终端发送的第一应用的数据，其中，第一应用来自USRP信息的App Store Id指示的应用商店，第一应用的App Id与URSP信息中的App Id相同。
第五方面，提供一种应用数据的传输方法，包括：网络设备向终端发送第一消息，第一消息包括URSP信息，URSP信息包括App Store Id、App Id和切片参数信息，App Store Id用于标识应用商店，App Id用于标识应用，切片参数信息用于指示切片网络。网络设备通过所述切片参数信息用于指示切片网络接收终端发送的第一应用的数据，其中，第一应用来自USRP信息的App Store Id指示的应用商店，第一应用的App Id与URSP信息中的App Id相同。
第六方面，提供一种应用数据的传输装置，包括：收发模块和处理模块，收发模块，用于接收来自网络设备的第一消息，第一消息包括终端设备路由选择策略URSP信息，URSP信息包括应用商店标识App Store Id、应用标识App Id和切片参数信息，App Store Id用于标识应用商店，App Id用于标识应用，切片参数信息用于指示切片网络；处理模块，用于运行第一应用，收发模块，还用于通过切片参数信息指示的切片网络传输第一应用的数据，其中，第一应用来自USRP信息的App Store Id指示的应用商店，第一应用的App Id与URSP信息中的App Id相同。
第七方面，提供一种应用数据的传输装置，包括收发模块，用于向终端发送第一消息，第一消息包括URSP信息，URSP信息包括App Store Id、App Id和切片参数信息，App Store Id用于标识应用商店，App Id用于标识应用，切片参数信息用于指示切片网络。通过所述切片参数信息用于指示切片网络接收终端发送的第一应用的数据，其中，第一应用来自USRP信息的App Store Id指示的应用商店，第一应用的App Id与URSP信息中的App Id相同。
第八方面，提供一种芯片，该芯片包括处理电路、收发管脚。其中，该收发管脚、和该处理电路通过内部连接通路互相通信，该处理电路执行第三方面或者第三方面的任 意一种实现方式中的方法，以控制接收管脚接收信号，以控制发送管脚发送信号。
第九方面，本申请实施例提供一种计算机可读存储介质，计算机可读存储介质存储有计算机程序，计算机程序包含至少一段代码，至少一段代码可由终端执行，以控制终端执行第三方面或者第三方面的任意一种实现方式中的方法。
第十方面，本申请实施例提供了一种计算机程序，该计算机程序包括用于执行第三方面或者第三方面的任意一种实现方式中的方法的指令。
附图说明
为了更清楚地说明本申请实施例的技术方案，下面将对本申请实施例的描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为本申请实施例提供的终端的硬件结构示意图；
图2为本申请实施例提供的终端的软件结构示意图；
图3为本申请实施例提供的通信系统示意图；
图4为示例性示出的URSP的格式示意图；
图5为示例性示出的用户界面的示意图；
图6为示例性示出的用户界面的示意图；
图7为本申请实施例提供的应用数据的传输方法的流程示意图；
图8为示例性示出的URSP的格式示意图；
图9为示例性示出的用户界面的示意图；
图10为示例性示出的URSP的格式示意图；
图11为示例性示出的URSP的格式示意图；
图12为本申请实施例提供的终端的结构示意图；
图13为本申请实施例提供的装置的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
下表为本申请所涉及到的术语及其解释：
Figure PCTCN2021081093-appb-000001
本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。
本申请实施例的说明书和权利要求书中的术语“第一”和“第二”等是用于区别不同的对象，而不是用于描述对象的特定顺序。例如，第一目标对象和第二目标对象等是用于区别不同的目标对象，而不是用于描述目标对象的特定顺序。
在本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解 释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
在本申请实施例的描述中，除非另有说明，“多个”的含义是指两个或两个以上。例如，多个处理单元是指两个或两个以上的处理单元；多个系统是指两个或两个以上的系统。
在本申请实施例的描述中，终端中的应用也可以称为应用程序或应用软件等，本申请不做限定。
在本申请实施例的描述中，终端可以称为终端、终端、用户终端(user equipment，UE)等。终端可以是手机、平板电脑、可穿戴设备、车载设备、增强现实(augmented reality，AR)/虚拟现实(virtual reality，VR)设备、笔记本电脑、超级移动个人计算机(ultra-mobile personal computer，UMPC)、上网本、个人数字助理(personal digital assistant，PDA)等可以接入网络的设备。
示例性的，图1示出了终端100的结构示意图。终端100可以包括处理器110，外部存储器接口120，内部存储器121，通用串行总线(universal serial bus，USB)接口130，充电管理模块140，电源管理模块141，电池142，天线1，天线2，移动通信模块150，无线通信模块160，音频模块170，扬声器170A，受话器170B，麦克风170C，耳机接口170D，传感器模块180，按键190，马达191，指示器192，摄像头193，显示屏194，以及用户标识模块(subscriber identification module，SIM)卡接口195等。其中传感器模块180可以包括压力传感器180A，陀螺仪传感器180B，气压传感器180C，磁传感器180D，加速度传感器180E，距离传感器180F，接近光传感器180G，指纹传感器180H，温度传感器180J，触摸传感器180K，环境光传感器180L，骨传导传感器180M等。
可以理解的是，本申请实施例示意的结构并不构成对终端100的具体限定。在本申请另一些实施例中，终端100可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件和硬件的组合实现。
处理器110可以包括一个或多个处理单元，例如：处理器110可以包括应用处理器(application processor，AP)，调制解调处理器(Modem)，图形处理器(graphics processing unit，GPU)，图像信号处理器(image signal processor，ISP)，控制器，存储器，视频编解码器，数字信号处理器(digital signal processor，DSP)，基带处理器，和/或神经网络处理器(neural-network processing unit，NPU)等。其中，不同的处理单元可以是独立的器件，也可以集成在一个或多个处理器中。
其中，控制器可以是终端100的神经中枢和指挥中心。控制器可以根据指令操作码和时序信号，产生操作控制信号，完成取指令和执行指令的控制。
处理器110中还可以设置存储器，用于存储指令和数据。在一些实施例中，处理器110中的存储器为高速缓冲存储器。该存储器可以保存处理器110刚用过或循环使用的指令或数据。如果处理器110需要再次使用该指令或数据，可从所述存储器中直接调用。避免了重复存取，减少了处理器110的等待时间，因而提高了系统的效率。
在一些实施例中，处理器110可以包括一个或多个接口。接口可以包括集成电路 (inter-integrated circuit，I2C)接口，集成电路内置音频(inter-integrated circuit sound，I2S)接口，脉冲编码调制(pulse code modulation，PCM)接口，通用异步收发传输器(universal asynchronous receiver/transmitter，UART)接口，移动产业处理器接口(mobile industry processor interface，MIPI)，通用输入输出(general-purpose input/output，GPIO)接口，用户标识模块(subscriber identity module，SIM)接口，和/或通用串行总线(universal serial bus，USB)接口等。
USB接口130是符合USB标准规范的接口，具体可以是Mini USB接口，Micro USB接口，USB Type C接口等。USB接口130可以用于连接充电器为终端100充电，也可以用于终端100与外围设备之间传输数据。也可以用于连接耳机，通过耳机播放音频。该接口还可以用于连接其他电子设备，例如AR设备等。
可以理解的是，本申请实施例示意的各模块间的接口连接关系，只是示意性说明，并不构成对终端100的结构限定。在本申请另一些实施例中，终端100也可以采用上述实施例中不同的接口连接方式，或多种接口连接方式的组合。
充电管理模块140用于从充电器接收充电输入。其中，充电器可以是无线充电器，也可以是有线充电器。在一些有线充电的实施例中，充电管理模块140可以通过USB接口130接收有线充电器的充电输入。在一些无线充电的实施例中，充电管理模块140可以通过终端100的无线充电线圈接收无线充电输入。充电管理模块140为电池142充电的同时，还可以通过电源管理模块141为终端供电。
电源管理模块141用于连接电池142，充电管理模块140与处理器110。电源管理模块141接收电池142和/或充电管理模块140的输入，为处理器110，内部存储器121，外部存储器，显示屏194，摄像头193，和无线通信模块160等供电。电源管理模块141还可以用于监测电池容量，电池循环次数，电池健康状态(漏电，阻抗)等参数。在其他一些实施例中，电源管理模块141也可以设置于处理器110中。在另一些实施例中，电源管理模块141和充电管理模块140也可以设置于同一个器件中。
终端100的无线通信功能可以通过天线1，天线2，移动通信模块150，无线通信模块160，调制解调处理器以及基带处理器等实现。
终端100可以通过音频模块170，扬声器170A，受话器170B，麦克风170C，耳机接口170D，以及应用处理器等实现音频功能。例如音乐播放，录音等。
音频模块170用于将数字音频信息转换成模拟音频信号输出，也用于将模拟音频输入转换为数字音频信号。音频模块170还可以用于对音频信号编码和解码。在一些实施例中，音频模块170可以设置于处理器110中，或将音频模块170的部分功能模块设置于处理器110中。
扬声器170A，也称“喇叭”，用于将音频电信号转换为声音信号。终端100可以通过扬声器170A收听音乐，或收听免提通话。
受话器170B，也称“听筒”，用于将音频电信号转换成声音信号。当终端100接听电话或语音信息时，可以通过将受话器170B靠近人耳接听语音。
麦克风170C，也称“话筒”，“传声器”，用于将声音信号转换为电信号。当拨打电话或发送语音信息时，用户可以通过人嘴靠近麦克风170C发声，将声音信号输入到麦克风 170C。终端100可以设置一个或者多个麦克风170C。在另一些实施例中，终端100可以设置两个麦克风170C，除了采集声音信号，还可以实现降噪功能。在另一些实施例中，终端100还可以设置三个，四个或更多麦克风170C，实现采集声音信号，降噪，还可以识别声音来源，实现定向录音功能等。
耳机接口170D用于连接有线耳机。耳机接口170D可以是USB接口130，也可以是3.5mm的开放移动电子设备平台(open mobile terminal platform，OMTP)标准接口，美国蜂窝电信工业协会(cellular telecommunications industry association of the USA，CTIA)标准接口。
终端100通过GPU，显示屏194，以及应用处理器等实现显示功能。GPU为图像处理的微处理器，连接显示屏194和应用处理器。GPU用于执行数学和几何计算，用于图形渲染。处理器110可包括一个或多个GPU，其执行程序指令以生成或改变显示信息。
显示屏194用于显示图像，视频等。显示屏194包括显示面板。显示面板可以采用液晶显示屏(liquid crystal display，LCD)，有机发光二极管(organic light-emitting diode，OLED)，有源矩阵有机发光二极体或主动矩阵有机发光二极体(active-matrix organic light emitting diode的，AMOLED)，柔性发光二极管(flex light-emitting diode，FLED)，Miniled，MicroLed，Micro-oLed，量子点发光二极管(quantum dot light emitting diodes，QLED)等。在一些实施例中，终端100可以包括1个或N个显示屏194，N为大于1的正整数。
终端100可以通过ISP，摄像头193，视频编解码器，GPU，显示屏194以及应用处理器等实现拍摄功能。
ISP用于处理摄像头193反馈的数据。例如，拍照时，打开快门，光线通过镜头被传递到摄像头感光元件上，光信号转换为电信号，摄像头感光元件将所述电信号传递给ISP处理，转化为肉眼可见的图像。ISP还可以对图像的噪点，亮度，肤色进行算法优化。ISP还可以对拍摄场景的曝光，色温等参数优化。在一些实施例中，ISP可以设置在摄像头193中。
摄像头193用于捕获静态图像或视频。物体通过镜头生成光学图像投射到感光元件。感光元件可以是电荷耦合器件(charge coupled device，CCD)或互补金属氧化物半导体(complementary metal-oxide-semiconductor，CMOS)光电晶体管。感光元件把光信号转换成电信号，之后将电信号传递给ISP转换成数字图像信号。ISP将数字图像信号输出到DSP加工处理。DSP将数字图像信号转换成标准的RGB，YUV等格式的图像信号。在一些实施例中，终端100可以包括1个或N个摄像头193，N为大于1的正整数。
数字信号处理器用于处理数字信号，除了可以处理数字图像信号，还可以处理其他数字信号。例如，当终端100在频点选择时，数字信号处理器用于对频点能量进行傅里叶变换等。
视频编解码器用于对数字视频压缩或解压缩。终端100可以支持一种或多种视频编解码器。这样，终端100可以播放或录制多种编码格式的视频，例如：动态图像专家组(moving picture experts group，MPEG)1，MPEG2，MPEG3，MPEG4等。
NPU为神经网络(neural-network，NN)计算处理器，通过借鉴生物神经网络结构，例如借鉴人脑神经元之间传递模式，对输入信息快速处理，还可以不断的自学习。通过NPU 可以实现终端100的智能认知等应用，例如：图像识别，人脸识别，语音识别，文本理解等。
外部存储器接口120可以用于连接外部存储卡，例如Micro SD卡，实现扩展终端100的存储能力。外部存储卡通过外部存储器接口120与处理器110通信，实现数据存储功能。例如将音乐，视频等文件保存在外部存储卡中。
内部存储器121可以用于存储计算机可执行程序代码，所述可执行程序代码包括指令。处理器110通过运行存储在内部存储器121的指令，从而执行终端100的各种功能应用以及数据处理。内部存储器121可以包括存储程序区和存储数据区。其中，存储程序区可存储操作系统，一个或者多个功能所需的应用程序(比如声音播放功能，图像播放功能等)等。存储数据区可存储终端100使用过程中所创建的数据(比如音频数据，电话本等)等。此外，内部存储器121可以包括高速随机存取存储器，还可以包括非易失性存储器，例如一个或者多个磁盘存储器件，闪存器件，通用闪存存储器(universal flash storage，UFS)等。
按键190包括开机键，音量键等。按键190可以是机械按键。也可以是触摸式按键。终端100可以接收按键输入，产生与终端100的用户设置以及功能控制有关的键信号输入。
马达191可以产生振动提示。马达191可以用于来电振动提示，也可以用于触摸振动反馈。例如，作用于不同应用(例如拍照，音频播放等)的触摸操作，可以对应不同的振动反馈效果。作用于显示屏194不同区域的触摸操作，马达191也可对应不同的振动反馈效果。不同的应用场景(例如：时间提醒，接收信息，闹钟，游戏等)也可以对应不同的振动反馈效果。触摸振动反馈效果还可以支持自定义。
指示器192可以是指示灯，可以用于指示充电状态，电量变化，也可以用于指示消息，未接来电，通知等。
SIM卡接口195用于连接SIM卡。SIM卡可以通过插入SIM卡接口195，或从SIM卡接口195拔出，实现和终端100的接触和分离。终端100可以支持1个或N个SIM卡接口，N为大于1的正整数。SIM卡接口195可以支持Nano SIM卡，Micro SIM卡，SIM卡等。同一个SIM卡接口195可以同时插入多张卡。所述多张卡的类型可以相同，也可以不同。SIM卡接口195也可以兼容不同类型的SIM卡。SIM卡接口195也可以兼容外部存储卡。终端100通过SIM卡和网络交互，实现通话以及数据通信等功能。在一些实施例中，终端100采用eSIM，即：嵌入式SIM卡。eSIM卡可以嵌在终端100中，不能和终端100分离。
终端100的软件系统可以采用分层架构，事件驱动架构，微核架构，微服务架构，或云架构。本申请实施例以分层架构的Android系统为例，示例性说明终端100的软件结构。
图2是本申请实施例的终端100的软件结构框图。分层架构将软件分成若干个层，每一层都有清晰的角色和分工。层与层之间通过软件接口通信。在一些实施例中，将Android系统分为四层，从上至下分别为应用程序层，应用程序框架层，安卓运行时(Android runtime)和系统库，以及内核层。应用程序层可以包括一系列应用程序包。
如图2所示，应用程序包可以包括相机，图库，日历，通话，地图，导航，WLAN，蓝牙，音乐，视频，聊天等应用程序。
应用程序框架层为应用程序层的应用程序提供应用编程接口(application programming interface，API)和编程框架。应用程序框架层包括一些预先定义的函数。
如图2所示，应用程序框架层(Framework)，可以包括窗口管理器，内容提供器，视图系统，电话管理器，资源管理器，通知管理器等。
窗口管理器用于管理窗口程序。窗口管理器可以获取显示屏大小，判断是否有状态栏，锁定屏幕，截取屏幕等。
内容提供器用来存放和获取数据，并使这些数据可以被应用程序访问。所述数据可以包括视频，图像，音频，拨打和接听的电话，浏览历史和书签，电话簿等。
视图系统包括可视控件，例如显示文字的控件，显示图片的控件等。视图系统可用于构建应用程序。显示界面可以由一个或多个视图组成的。例如，包括短信通知图标的显示界面，可以包括显示文字的视图以及显示图片的视图。
电话管理器用于提供终端100的通信功能。例如通话状态的管理(包括接通，挂断等)。
资源管理器为应用程序提供各种资源，比如本地化字符串，图标，图片，布局文件，视频文件等等。
通知管理器使应用程序可以在状态栏中显示通知信息，可以用于传达告知类型的消息，可以短暂停留后自动消失，无需用户交互。比如通知管理器被用于告知下载完成，消息提醒等。通知管理器还可以是以图表或者滚动条文本形式出现在系统顶部状态栏的通知，例如后台运行的应用程序的通知，还可以是以对话窗口形式出现在屏幕上的通知。例如在状态栏提示文本信息，发出提示音，终端振动，指示灯闪烁等。
Android Runtime包括核心库和虚拟机。Android runtime负责安卓系统的调度和管理。
核心库包含两部分：一部分是java语言需要调用的功能函数，另一部分是安卓的核心库。
应用程序层和应用程序框架层运行在虚拟机中。虚拟机将应用程序层和应用程序框架层的java文件执行为二进制文件。虚拟机用于执行对象生命周期的管理，堆栈管理，线程管理，安全和异常的管理，以及垃圾回收等功能。
系统库可以包括多个功能模块。例如：表面管理器(surface manager)，媒体库(media libraries)，三维图形处理库(例如：OpenGL ES)，2D图形引擎(例如：SGL)等。
表面管理器用于对显示子系统进行管理，并且为多个应用程序提供了2D和3D图层的融合。
媒体库支持多种常用的音频，视频格式回放和录制，以及静态图像文件等。媒体库可以支持多种音视频编码格式，例如:MPEG4，H.264，MP3，AAC，AMR，JPG，PNG等。
三维图形处理库用于实现三维图形绘图，图像渲染，合成，和图层处理等。
2D图形引擎是2D绘图的绘图引擎。
内核层是硬件和软件之间的层。内核层至少包含显示驱动，摄像头驱动，音频驱动，传感器驱动。
在介绍本申请实施例的技术方案之前，首先结合附图对本申请实施例的通信系统进行说明。参见图3，为本申请实施例提供的一种通信系统示意图。该通信系统中包括终端与核心网。
需要说明的是，在实际应用中，终端的数量均可以为一个或多个，图3所示通信系统的终端的数量仅为适应性举例，本申请对此不做限定。
进一步需要说明的是核心网包括一个或多个核心网设备，可选地，核心网设备可以是接入和移动性管理功能(access and mobility management function，AMF)，主要负责接入控制、移动性管理(mobility management，MM)、附着与去附着以及网关选择等功能。本申请实施例所涉及的核心网设备不限于AMF。
第五代(5th Generation，5G)通信系统引入了网络切片的概念，网络切片技术能够实现将一个物理网络划分为多个虚拟网络。一个虚拟网络当作一个“网络切片”，每个网络切片之间是相互独立的。一个终端中的不同协议数据单元(protocol data unit，PDU)会话可能需要与PDU会话相对应的网络切片来提供服务。
为使本领域技术人员更好的理解本申请，下面对本申请涉及到的网络切片的概念进行简单说明：
网络切片作为5G的一项关键技术，在3GPP和其他各种国际标准化组织得到了广泛的重视和研究。其可以满足运营商对于各种工业、垂直市场和各种虚拟运营业务的定制化需求。网络切片是一个提供特定网络能力和网络特征的逻辑网络(Network Slice:A logical network that provides specific network capabilities and network characteristics)。它可以是在物理或者虚拟的网络基础设施之上，根据不同的服务需求或者租户等定制化的有不同网络能力和网络特性的逻辑网络。网络切片由一组网络功能及其所需的资源(例如，计算资源、存储资源、网络资源)构成。
每个小区所支持的网络切片由操作、管理和维护系统(operation，administration and maintenance，OAM)配置。单一网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)用于标识一个网络切片。
S-NSSAI包括以下至少之一：切片类型、服务类型(slice/service type，SST)信息，可选地，S-NSSAI还可以包括切片区分信息(slice differentiator，SD)。其中，SST信息用于指示网络切片的行为，例如网络切片的特征以及服务类型，SD信息是SST的补足信息，例如：若SST指向多个网络切片，那么SD可以辅助对应到唯一的一个网络切片。
终端中存在多种类型的业务，例如增强的移动宽带业务(enhanced mobile broadband，eMBB)，超可靠低时延通信(ultra-reliable low latency communications，URLLC)，海量机器类通信(massive machine type communication，mMTC)等，而不同类型业务的PDU会话对应的网络切片可能不同。在本申请实施例中，终端中的不同应用可以对应于不同的业务类型，也就是说，终端中的应用可以对应不同的网络切片。需要说明的是，即使是相同的业务类型，由于提供的运营商或者业务提供商不同，也可能对应不同的网络切片。也就是说，网络切片可以给终端的至少一个PDU会话提供网络资源。
在一些实施例中，也可以设置“白名单”或者“黑名单”应用，例如，当终端设备运行第一应用程序时，所以第一应用为白单名应用程序，则终端设备可以通过使用切片 资源与网络侧进行交互，可以理解，当终端设备运行第二应用程序的时候，第二应用程序为非白名单应用，则不使用切片资源；同样，可以禁止黑名单中的应用使用网络切换，二非黑名单中的应用可以使用切片资源。
示例性的，结合图3，在5G应用场景中，核心网通过向终端发送UE路由选择策略(UE route selection policy，URSP)，URSP可用于指示需要在切片网络上传输的流量特征和切片网络激活参数，以使终端确定数据(可以理解为不同业务类型的应用的数据)的路由方式，路由方式包括具体路由到哪个切片，或者是采用非切片网络传输数据。
示例性的，如图4为示例性示出的URSP的格式示意图，URSP包括但不限于：URSP规则长度(Length of URSP rule)字段、URSP规则的优先级(Precedence value of URSP rule)字段、流量描述符长度(Length of Traffic descriptor)字段、Traffic descriptor字段、路由选择描述符列表长度(Length of Route selection descriptor list)字段以及Route selection descriptor字段。
其中，Route selection descriptor list字段用于承载切片网络激活参数，切片网络激活参数包括但不限于：一个或多个切片对应的S-NSSAI等参数。
Traffic descriptor字段用于承载上文所述的需要在切片上传输的流量特征对应的信息(或参数)。其它字段的定义可参照3GPP标准中的描述，此处不赘述。
3GPP 24526协议中对于Traffic descriptor字段的描述如下：
Traffic descriptor component type identifier(流量描述符字段类型定义)
Bits(比特位)
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 1  Match-all type(全匹配类型)
0 0 0 0 1 0 0 0  OS Id+OS App Id type(操作系统标识+操作系统应用标识类型)
0 0 0 1 0 0 0 0  IPv4 remote address type(ipv4远端地址类型)
0 0 1 0 0 0 0 1  IPv6 remote address/prefix length type(ipv6远端地址/前缀长度类型)
0 0 1 1 0 0 0 0  Protocol identifier/next header type(协议标识/下一个协议头类型)
0 1 0 1 0 0 0 0  Single remote port type(单个远端端口类型)
0 1 0 1 0 0 0 1  Remote port range type(远端端口范围类型)
0 1 1 0 0 0 0 0  Security parameter index type(安全参数索引类型)
0 1 1 1 0 0 0 0  Type of service/traffic class type(服务/流量等级类型)
1 0 0 0 0 0 0 0  Flow label type(流标签类型)
1 0 0 0 0 0 0 1  Destination MAC address type(目标MAC地址类型)
1 0 0 0 0 0 1 1  802.1Q C-TAG VID type(802.1Q用户标签虚拟局域网识别符类型)
1 0 0 0 0 1 0 0  802.1Q S-TAG VID type(802.1Q业务标签虚拟局域网识别符类型)
1 0 0 0 0 1 0 1  802.1Q C-TAG PCP/DEI type(802.1Q用户标签优先权代码点/丢弃指示器类型)
1 0 0 0 0 1 1 0  802.1Q S-TAG PCP/DEI type(802.1Q业务标签优先权代码点/丢弃指示器类型)
1 0 0 0 0 1 1 1  Ethertype type(以太网类型)
1 0 0 0 1 0 0 0  DNN type(数据网络名称(Data Network Name)类型)
1 0 0 1 0 0 0 0  Connection capabilities type(连接能力类型)
其中，OS Id+OS App Id组成应用描述符(Application descriptors)信息，用于标识操作系统中的应用，也可以理解为，Application descriptors可用于指示操作系统中的哪些应用可以通过切片网络传输数据。其中，OS Id用于标识操作系统，OS App Id用于标识操作系统中的应用。
以安卓(Android)操作系统为例(需要说明的是，其它操作系统与Android操作系统类似，本申请不再赘述)，Android操作系统中的应用对应的OS App Id(以下简称App Id)为应用包名，Android操作系统对App Id的定义如下：
每个Android应用均有一个唯一的应用ID，像Java软件包名称一样，如com.example.myapp。此ID可以在设备商和Google Play商店中对您的应用进行唯一标识。如果您要上传新版本的应用，应用ID(以及用于为其签名的证书)比如与原始APK相同。如果您更改了应用ID，Google Play商店会将该Android应用程序包(Android application package，APK)视为完全不同的应用。因此，发布您的应用后，绝不应更改应用ID。
Android操作系统中的App Id是应用开发者在开发程序，例如build.gradle中指定的，应用开发者在Android应用市场(例如华为应用市场或者Google Play)上发布应用时，应用市场会验证App Id的唯一性，也就是如上文所述的，如果是不相同的App Id，则会认为是两个完全不同的应用，因此，应用市场可保证App Id在该应用市场的唯一性。
如图5为示例性示出的用户使用场景的示意图，以终端为手机为例，用户可通过手机中的华为应用市场下载应用，参照图5，用户可通过点击屏幕，下载并安装聊天应用，当所述终端设备从应用商店下载并安装了所述聊天应用时，终端设备可以获取到所述应用的标识信息，例如，该应用的版本号、所支持的操作系统类型OS Id、应用程序的App Id号等信息，该标识信息也可以是当终端设备首次运行该应用(例如，前台运行)程序时获取的。当终端设备需要与核心网进行数据交互时，例如，发送语音消息时，终端可将获取到的OS Id和App Id与核心网预先下发的URSP中的OS Id+OS App Id type所指示的OS Id和App Id(即OS App Id)进行匹配，如果匹配成功，则按照URSP的指示将该聊天应用的数据路由到指定的切片上进行传输。如果匹配不成功，则通过非切片网络传输数据。但是，在一些场景中，用户可能会通过adb install(Android Debug Bridge install，安卓调试桥安装)工具或者从第三方服务器提供的下载页面下载应用，需要说明的是，三方服务器是不提供App Id的合法性(即唯一性)校验的，因此可能使得用户下载的地图应用为仿冒的应用，其中，仿冒应用的App Id(例如应用包名)与应用市场中的任一应用的App Id一致。举例说明，参照图6，用户可通过手机访问第三方服务器提供的下载页面，以下载地图应用。终端根据用户指令，通过下载页面从第三方服务器下载地图应用，该地图应用的应用包名与华为应用市场中的聊天应用的应用包名一致，即，App Id相同。则当该地图应用到前台后，终端将地图应用的App Id(即与聊天应用相同的仿冒Id)与URSP中的OS App Id匹配成功后，按照URSP的指示将该地图应用的数据路由到本该是聊天应用对应的切片上进行传输。假设聊天应用所对应的切片为高优先 级切片，而地图应用本该对应的切片为低优先级切片，或者地图应用本该对应的传输方式为非3GPP传输，即不通过切片进行传输，则由于地图应用使用仿冒的App Id，使得地图应用占用高优先级切片进行传输，导致运营商资源浪费。
本申请实施例提出一种应用数据的传输方法，通过URSP中的AppStore Id和App Id，以使得终端对应用进行校验时，结合AppStore Id和App Id，从而解决App Id被仿冒的问题。
下面采用几个具体的实施例，对上述方法实施例的技术方案进行详细说明。需要说明的是，在下述实施例均已终端为UE进行说明。
场景一
结合图3，如图7所示为本申请实施例中的应用数据的传输方法的流程示意图，在图7中：
步骤101，Modem向核心网发送Registration request消息。
具体的，UE开机或者退出飞行模式、掉网等情况下会发起注册流程，例如，手机(即UE)在开机后，将会发起注册流程。或者，用户将手机刷新后，也会发起注册流程，注册流程可以理解为手机注册入网，具体细节可参照已有标准中的UE注册流程，本申请不再赘述。
示例性的，参照图7，UE的Modem向核心网发送注册请求(Registration request)消息，用于请求发起注册流程。示例性的，消息中可携带注册类型、安全参数等信息，具体可参照已有标准中的注册流程，本申请不再赘述。
步骤102a，核心网向Modem发送注册接受(Registration accept)消息。
具体的，核心网同意UE注册入网后，向UE发送Registration accept消息，消息中携带用于指示终端接入核心网的一个或多个参数。示例性的，在本实施例中，Registration accept消息中携带允许网络切片选择辅助信息(Allowed NSSAI)，用于指示允许终端接入的一个或多个切片。
步骤102b，Modem将Allowed NSSAI传输至Framework。
示例性的，UE中的Modem可用于接收并解析来自核心网的消息，并将消息中携带的信息转发给Framework。需要说明的是，本文仅以Modem为例进行说明，实际上，UE中用于接收、解析并转发来自核心网的信息的器件或芯片或软件程序不限于Modem。
步骤103，Framwork保存Allowed NSSAI。
示例性的，Framwork将Allowed NSSAI保存至存储单元，例如UE的内存中，以在后续的建立PDU session时使用。
步骤104a，核心网向Modem发送管理终端策略命令消息(Manage UE policy command)消息。
具体的，核心网向UE发送Manage UE policy command消息，该消息中包括但不限于URSP。
示例性的，在本实施例中，URSP中的Traffic descriptor字段的描述如下：
Traffic descriptor component type identifier
Bits(比特位)
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 1  Match-all type
0 0 0 0 1 0 0 0  OS Id+AppStore Id+OS App Id type
0 0 0 1 0 0 0 0  IPv4 remote address type
0 0 1 0 0 0 0 1  IPv6 remote address/prefix length type
0 0 1 1 0 0 0 0  Protocol identifier/next header type
0 1 0 1 0 0 0 0  Single remote port type
0 1 0 1 0 0 0 1  Remote port range type
0 1 1 0 0 0 0 0  Security parameter index type
0 1 1 1 0 0 0 0  Type of service/traffic class type
1 0 0 0 0 0 0 0  Flow label type
1 0 0 0 0 0 0 1  Destination MAC address type
1 0 0 0 0 0 1 1  802.1Q C-TAG VID type
1 0 0 0 0 1 0 0  802.1Q S-TAG VID type
1 0 0 0 0 1 0 1  802.1Q C-TAG PCP/DEI type
1 0 0 0 0 1 1 0  802.1Q S-TAG PCP/DEI type
1 0 0 0 0 1 1 1  Ethertype type
1 0 0 0 1 0 0 0  DNN type
1 0 0 1 0 0 0 0  Connection capabilities type
示例性的，如图8为示例性示出的URSP的格式示意图，参照图8，URSP包括但不限于Traffic descriptor字段，其它字段未在图8中示出。
示例性的，Traffic descriptor字段包括一个或多个Traffic descriptor component type identifier字段，每个Traffic descriptor component type identifier字段可包括上文所列任一枚举值，例如，Traffic descriptor component type identifier字段包括枚举值[0 0 0 0 0 0 0 1]，用于指示后续码流(直至下一个Traffic descriptor component type identifier字段之前)携带的信息为Match-all type。
需要说明的是，图8中仅以OS Id+AppStore Id+OS App Id type为例，实际上，Traffic descriptor字段还可以包括其它类型所对应的码流，本申请不再赘述。
参照图8，Traffic descriptor component type identifier字段中包括[0 0 0 0 1 0 0 0]，用于指示后续码流(直至下一个Traffic descriptor component type identifier字段之前)携带的信息为OS Id+AppStore Id+OS App Id type，即包括OS Id、AppStore Id以及App Id。示例性的，OS Id+AppStore Id+OS App Id type对应的格式如图8所示，包括：OS Id长度(Length of OS Id)字段、OS Id字段、应用商店标识数量(Num of AppStore Ids)字段，一个或多个Length of AppStore Id字段、一个或多个AppStore Id字段、Length of App Id字段、App Id字段。
下面对各字段进行详细描述：
Length of OS Id字段，用于指示OS Id字段的长度，或者也可以理解为，用于指示 OS Id的长度。需要说明的是，本申请所指的字段或信息的长度是指所占时域资源长度，例如占用3个符号位，或者3个比特。示例性的，Length of OS Id字段的长度为1字节。
OS Id字段，用于指示操作系统的标识信息，即，携带OS Id。
Num of AppStore Ids字段，用于指示可靠的应用市场或应用商店的数量。示例性的，字段长度为1字节。
Length of AppStore Id字段，用于指示AppStore Id字段的长度。示例性的，字段长度为1字节。
AppStore Id字段，用于指示应用商店，或可称为应用平台、应用市场等的AppStore Id。
以Android操作系统为例，Android操作系统中的可靠AppStore可以包括但不限于：google play、华为应用市场等。需要说明的是，AppStore Id是核心网与各应用市场协商后的结果，核心网存储有不同的操作系统所对应的一个或多个AppStore的AppStore Id。进一步需要说明的是，核心网对各应用市场会进行合法性验证，也就是说，合法性验证成功的应用市场对应的AppStore Id才会携带在URSP中。
可选地，UE在步骤101的注册流程中，核心网可获取到UE的操作系统信息，也就是说，URSP中的OS Id、AppStore Id和APP Id等信息(或参数)，均是与UE中的操作系统对应的信息，例如是UE的操作系统对应的OS Id，UE的操作系统对应的应用市场的AppStore Id，以及UE的操作系统中的应用对应的ID。
举例说明，Num of AppStore Ids字段可用于指示OS Id对应的操作系统中包含的应用商店的数量为2个，也就是说，后面的码流中会包含2个Length of AppStore Id字段，以及2个AppStore Id字段。示例性的，其中一个AppStore Id字段携带华为应用市场的AppStore Id，另一个AppStore Id字段携带Goolge Play的AppStore Id。需要说明的是，本申请中涉及的字段的“后面”均是指时域上的前后关系，下文中不再赘述。
Length of App Id字段，用于指示App Id字段的长度。示例性的，Length of App Id字段的长度为1字节。
App Id字段，用于指示应用的App Id，即携带一个或多个App Id。需要说明的是，App Id字段中携带的App Id即为经过各应用市场校验后的App Id。可选地，App Id字段中包括的多个App Id可以用分隔符进行分隔，以区分不同的App Id，分隔方式仅为示意性举例，本申请不做限定。可选地，App Id字段也可以包括多个App Id子字段，每个App Id子字段携带一个App Id。
示例性的，核心网存储有与操作系统的应用市场对应的各应用的App Id，URSP的App Id字段中携带的一个或多个App Id，是与UE的操作系统中的各应用市场中的应用对应的。以Android操作系统为例，核心网向UE发送的URSP的App Id字段携带的一个或多个App Id，即是Android操作系统中的华为应用市场和Google Play中应用的App Id。
需要说明的是，App Id字段中的App Id是指数据需要路由到切片网络的应用，也就是说，只有应用市场中的需要路由到切片网络的应用的App Id才会携带在App Id字段中，而不在App Id字段中的应用的数据将会通过非切片网络传输。
步骤104b，Modem向Framework传输URSP。
具体的，Modem接收并解析Manage UE policy command消息，以获取URSP，并将URSP传输给URSP。
步骤105，Framework保存URSP。
具体的，Framework获取到来自Modem传输的URSP后，对URSP进行解码及合法性校验，以获取URSP中各字段携带的参数及信息。示例性的，Framework保存的信息中包括但不限于：OS Id、AppStore Id以及App Id。
示例性的，上述信息可保存在内存中，本申请不做限定。
需要说明的是，本申请中所述的保存URSP，是指保存URSP中携带的各参数及信息，下文中不再赘述。
步骤106a，Framework发送Manage UE policy complete消息。
具体的，Framework成功保存URSP包括的各参数后，向Modem发送Manage UE policy complete消息，以指示Framework已对URSP成功处理。
示例性的，如果Framework未能成功解析URSP或由于其他原因导致Framework未能成功保存URSP，则Framework向Modem发送Manage UE policy command reject消息，并由Modem将该消息转发给核心网。
步骤106b，Modem将Manage UE policy complete消息发送至核心网。
步骤107，App启动。
示例性的，以UE为具有Android操作系统的手机为例，用户可在华为应用市场中下载并安装聊天应用。应用安装完成后，用户可通过点击屏幕启动聊天应用，如图9所示。
步骤108，Framework获取OS Id、AppStore Id以及App Id。
示例性的，聊天应用启动，Framework可监听到应用到前台，Framework可获取UE的操作系统的OS Id、聊天应用的App Id以及聊天应用的安装来源(即下载来源)，即华为应用市场的AppStore Id。
示例性的，操作系统的OS Id可存储在内存中，Framework可通过接口或程序指令调取OS Id。示例性的，App Id可以为聊天应用的应用包名，Framework可从应用的相关文件(例如应用描述文件)中调取应用包名。示例性的，聊天应用的安装来源也可以包含于应用的相关文件中，Framework可通过接口、程序指令或工具调取该安装来源的信息，例如，FrameworkPackageManager.java中的getInstallerPackageName获取聊天应用的安装来源，即华为应用市场的AppStore Id。
步骤109，Framework对OS Id、AppStore Id以及App Id进行校验。
具体的，Framework将OS Id、AppStore Id以及App Id与步骤105中保存的URSP中的OS Id和一个或多个AppStore Id以及一个或多个App Id进行匹配，若OS Id、AppStore Id以及App Id均匹配成功，也就是说，均存在于核心网下发的URSP中，则Framework确定OS Id、AppStore Id以及App Id校验成功，该应用(例如聊天应用)的数据可路由到切片网络。
示例性的，若OS Id、AppStore Id以及App Id中的任一参数匹配失败，即不存在URSP中，则Framework确定校验失败，该应用的数据不可路由到切片网络，即通过非切片网络传输。
举例说明，仍以上文中具有仿冒App Id的地图应用为例，终端根据用户指令，通过第三方服务器提供的网页下载地图应用，Framework监听到地图应用到前后，获取OS Id，以及该地图应用的安装来源和App Id(与聊天应用相同)，其中，安装来源可以为网页网址。Framewrok对OS Id进行校验，OS Id存在于URSP中，确定OS Id校验成功，接着，Framewrok对地图应用的安装来源，即网页网址进行校验，网页网址未存在于URSP所指示的AppStore Id中，Framewrok确定安装来源校验失败，也就是说，该地图应用的App Id即使与需要路由到切片网络的聊天应用的App Id一致的情况下，由于地图应用的安装来源校验失败，在后续流程中，Framework不允许地图应用的数据通过切片网络传输，从而降低运营商网络的开销。
步骤110，Framework将App与切片进行绑定。
示例性的，仍以聊天应用为例，Framework对OS Id、AppStore Id以及App Id验证成功后，可进一步基于URSP中的其它信息，例如上文所述的切片网络激活参数等，获取聊天应用所对应的切片及切片的其它相关信息，例如切片的NSSAI。
示例性的，Framework可将切片的NSSAI与步骤103中存储的Allowed NSSAI进行匹配，以确定核心网是否允许UE的数据路由到该切片。
一个示例中，如果Framework检测到未建立与该切片对应的PDU session，则需触发PDU session建立流程，参照图7，方法还包括：
步骤110a，Framework向Modem发送PDU session建立请求消息。
步骤110b，Modem向核心网发送PDU session建立请求消息。
示例性的，Framework向核心网发起PDUsession建立流程，以建立对应于聊天应用的切片的PDU session。示例性的，PDU session建立请求消息携带聊天应用对应的切片的NSSAI。
步骤110c，核心网向Modem发送PDU seesion建立成功消息。
步骤110d，Modem向Framework发送PDU seesion建立成功消息。
示例性的，核心网基于接收到的PDU session建立请求消息，建立与NSSAI对应的切片的PDU session，并在PDU session建立成功后，向Modem返回PDU seesion建立成功消息。
需要说明的是，PDU seesion建立流程的具体细节可参照已有标准中规定的PDU seesion建立流程，本申请不再赘述。
具体的，Framework接收到PDU seesion建立成功消息后，确定PDU seesion建立成功，并将聊天应用与PDU seesion进行绑定。示例性的，绑定可以是指Framework将聊天应用的App Id与PDU seesion的相关信息(例如流量接口或者路由表项)对应记录在内存中，以使Framework检测到与该App Id对应的数据后，确定与App Id绑定的PDU seesion，并将聊天应用的数据路由到PDU seesion所对应的切片上。
另一个示例中，若Framework检测到聊天应用对应的切片的PDU session已建立，则Framework直接将聊天应用于PDU session绑定，而无需执行PDU session建立流程。
需要说明的是，对于UE中的其它应用，在应用初次启动后，可重复执行步骤107～步骤110。示例性的，对于已完成PDU session绑定的应用，可直接进行数据传输过程， 即将应用的数据路由到对应的切片。
在一种可能的实现方式中，Traffic descriptor字段的描述可如下：
Traffic descriptor component type identifier
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 1  Match-all type
0 0 0 0 1 0 0 0  AppStore Id+OS App Id type
0 0 0 1 0 0 0 0  IPv4 remote address type
0 0 1 0 0 0 0 1  IPv6 remote address/prefix length type
0 0 1 1 0 0 0 0  Protocol identifier/next header type
0 1 0 1 0 0 0 0  Single remote port type
0 1 0 1 0 0 0 1  Remote port range type
0 1 1 0 0 0 0 0  Security parameter index type
0 1 1 1 0 0 0 0  Type of service/traffic class type
1 0 0 0 0 0 0 0  Flow label type
1 0 0 0 0 0 0 1  Destination MAC address type
1 0 0 0 0 0 1 1  802.1Q C-TAG VID type
1 0 0 0 0 1 0 0  802.1Q S-TAG VID type
1 0 0 0 0 1 0 1  802.1Q C-TAG PCP/DEI type
1 0 0 0 0 1 1 0  802.1Q S-TAG PCP/DEI type
1 0 0 0 0 1 1 1  Ethertype type
1 0 0 0 1 0 0 0  DNN type
1 0 0 1 0 0 0 0  Connection capabilities type
具体的，Traffic descriptor component type identifier字段的值为[00001000]，用于指示AppStore Id+OS App Id type，即后续码流中包括AppStore Id和App Id，而不包括OS Id。
相应的，如图10所示为与上述Traffic descriptor字段的描述对应的Traffic descriptor字段的格式示意图，各字段的描述可参照上文，此处不赘述。
也就是说，在本实施例中，URSP中可不包括OS Id，相应的，在上述图7所示的实施例中，步骤108中，Framework仅获取启动后的应用对应的AppStore Id与App Id。以及，在步骤109中，Framework对AppStore Id与App Id进行校验，其它细节仍与图7中描述一致，本实施例不再赘述。
在一种可能的实现方式中，Traffic descriptor字段的描述可如下：
Traffic descriptor component type identifier
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 1  Match-all type
0 0 0 0 1 0 0 0  OS Id+OS App Id type
0 0 0 1 0 0 0 0  IPv4 remote address type
0 0 1 0 0 0 0 1  IPv6 remote address/prefix length type
0 0 1 1 0 0 0 0  Protocol identifier/next header type
0 1 0 1 0 0 0 0  Single remote port type
0 1 0 1 0 0 0 1  Remote port range type
0 1 1 0 0 0 0 0  Security parameter index type
0 1 1 1 0 0 0 0  Type of service/traffic class type
1 0 0 0 0 0 0 0  Flow label type
1 0 0 0 0 0 0 1  Destination MAC address type
1 0 0 0 0 0 1 1  802.1Q C-TAG VID type
1 0 0 0 0 1 0 0  802.1Q S-TAG VID type
1 0 0 0 0 1 0 1  802.1Q C-TAG PCP/DEI type
1 0 0 0 0 1 1 0  802.1Q S-TAG PCP/DEI type
1 0 0 0 0 1 1 1  Ethertype type
1 0 0 0 1 0 0 0  DNN type
1 0 0 1 0 0 0 0  Connection capabilities type
1 0 1 0 0 0 0 0  AppStore Id+App Id type
具体的，Traffic descriptor component type identifier字段的值为[00001000]时，仍沿用3GPP标准中规则，用于指示OS Id+OS App Id type，即后续码流中包括OS Id和OS App Id。
示例性的，Traffic descriptor component type identifier字段的值为[1 0 1 0 0 0 0 0]时，用于指示AppStore Id+App Id type，即后续码流中包括AppStore Id和App Id。
相应的，如图11所示为与上述Traffic descriptor字段的描述对应的Traffic descriptor字段的格式示意图，各字段的描述可参照上文，此处不赘述。
在又一种可能的实现方式中，UE对应的业务更新后，同样会发起注册流程，例如，用户修改了手机的运营商套餐，一个示例中，用户可通过手机的运行商APP修改运行商套餐，并由手机通知核心网运行商套餐已修改。另一个示例中，用户也可以拨打运营商电话，以更改运营商套餐，运营商可直接在核心网中更改用户的运营商套餐。具体的，运营商套餐更改后，核心网将会重新向UE发送URSP，即重复步骤104a～步骤110，例如聊天应用在图7中所示的步骤中，其与PDU session1绑定，聊天应用的数据路由到切片1，UE的运营商套餐更新后，可能会触发UE重新与核心网建立与聊天应用对应的PDU session2，聊天应用的数据路由到切片2。示例性的，切片2可能比切片1的优先级低，上述举例仅为示意性说明，本申请不做限定。
可以理解的是，终端为了实现上述功能，其包含了执行各个功能相应的硬件和/或软件模块。结合本文中所公开的实施例描述的各示例的算法步骤，本申请能够以硬件或硬 件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。本领域技术人员可以结合实施例对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本实施例可以根据上述方法示例对终端进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块可以采用硬件的形式实现。需要说明的是，本实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下，图12示出了一种终端200的结构示意图，终端200包括收发模块201，处理模块202，收发模块201，用于接收来自网络设备的第一消息，所述第一消息包括终端设备路由选择策略URSP信息，所述URSP信息包括App Store Id、App Id和切片参数信息，所述App Store Id用于标识应用商店，所述App Id用于标识应用，所述切片参数信息用于指示切片网络；处理模块202，用于运行第一应用。收发模块201，还用于通过所述切片参数信息指示的切片网络传输所述第一应用的数据，其中，所述第一应用来自所述USRP信息的App Store Id指示的应用商店，所述第一应用的App Id与所述URSP信息中的App Id相同。
在一种可能的实现方式中，处理模块202还用于运行第二应用，收发模块201还用于通过非切片网络传输所述第二应用的数据，其中，所述第二应用的下载来源非所述USRP信息的App Store Id指示的应用商店，所述第二应用的App Id与所述URSP信息中的App Id相同或不同。
在一种可能的实现方式中，收发模块201还用于若所述终端与所述网络设备之间已建立与所述切片参数信息指示的切片网络对应的协议数据单元PUD会话，基于所述PDU会话，在所述切片参数信息指示的切片网络上传输第一应用的数据。
在一种可能的实现方式中，收发模块201，还用于若所述终端未与所述网络设备之间已建立与所述切片参数信息指示的切片网络对应的协议数据单元PUD会话，所述终端基于所述切片参数信息，与所述网络设备建立PDU会话，并基于所述PDU会话，在所述切片参数信息指示的切片网络上传输第一应用的数据。
在一种可能的实现方式中，所述URSP信息还包括操作系统标识OS Id，用于标识操作系统；所述终端的操作系统的OS Id与所述URSP信息中的OS Id相同。
在一种可能的实现方式中，所述URSP信息还包括指示信息，用于指示所述URSP信息中包括App Store Id和App Id。
在一种可能的实现方式中，收发模块201，还用于接收来自所述网络设备的第二消息，所述第二消息包括允许的网络切片选择辅助信息Allowed NSSAI，用于指示允许终端传输数据切片网络集合；所述切片参数信息指示的切片网络包含于所述切片网络集合中。
在一种可能的实现方式中，收发模块201还用于向所述网络设备发送注册消息，用于注册并接入所述网络设备，或者，向所述网络设备发送业务更新消息，用于指示所述终端中的业务更新。
在一种可能的实现方式中，所述App Id为应用的应用包名。
在一种可能的实现方式中，所述应用商店为包括一个或多个应用的应用集合。
在另一个示例中，图13示出了本申请实施例的一种装置300的示意性框图装置300可以包括：处理器301和收发器/收发管脚302，可选地，还包括存储器303。
装置300的各个组件通过总线304耦合在一起，其中总线系统304除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图中将各种总线都标为总线系统304。
可选地，存储器303可以用于前述方法实施例中的指令。该处理器301可用于执行存储器303中的指令，并控制接收管脚接收信号，以及控制发送管脚发送信号。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
本实施例还提供一种计算机存储介质，该计算机存储介质中存储有计算机指令，当该计算机指令在终端上运行时，使得终端执行上述相关方法步骤实现上述实施例中的应用数据的传输方法。
本实施例还提供了一种计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行上述相关步骤，以实现上述实施例中的方法。
本实施例还提供了一种系统包括终端和网络服务器，可实现上述实施例中的方法。
另外，本申请的实施例还提供一种装置，这个装置具体可以是芯片，组件或模块，该装置可包括相连的处理器和存储器；其中，存储器用于存储计算机执行指令，当装置运行时，处理器可执行存储器存储的计算机执行指令，以使芯片执行上述各方法实施例中的方法。
其中，本实施例提供的终端、计算机存储介质、计算机程序产品或芯片均用于执行上文所提供的对应的方法，因此，其所能达到的有益效果可参考上文所提供的对应的方法中的有益效果，此处不再赘述。
通过以上实施方式的描述，所属领域的技术人员可以了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个装置，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是一个物理单元或多个物理单元，即可以位于一个地方，或者也可以分布到多个不同地方。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是 各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个可读取存储介质中。基于这样的理解，本申请实施例的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该软件产品存储在一个存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器(processor)执行本申请各个实施例方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (30)

  1. 一种应用数据的传输系统，其特征在于，包括网络设备与终端；
    所述网络设备，用于向所述终端发送第一消息，所述第一消息包括终端设备路由选择策略URSP信息，所述URSP信息包括应用商店标识App Store Id、应用标识App Id和切片参数信息，所述App Store Id用于标识应用商店，所述App Id用于标识应用，所述切片参数信息用于指示切片网络；
    所述终端，用于运行第一应用，通过所述切片参数信息指示的切片网络传输所述第一应用的数据，其中，所述第一应用来自所述USRP信息的App Store Id指示的应用商店，所述第一应用的App Id与所述URSP信息中的App Id相同。
  2. 根据权利要求1所述的系统，其特征在于，
    所述终端，还用于运行第二应用，通过非切片网络传输所述第二应用的数据，其中，所述第二应用的下载来源非所述USRP信息的App Store Id指示的应用商店，所述第二应用的App Id与所述URSP信息中的App Id相同或不同。
  3. 根据权利要求1所述的系统，其特征在于，若所述终端与所述网络设备之间已建立与所述切片参数信息指示的切片网络对应的协议数据单元PUD会话，所述终端用于基于所述PDU会话，在所述切片参数信息指示的切片网络上传输第一应用的数据。
  4. 根据权利要求1所述的系统，其特征在于，若所述终端与所述网络设备之间未建立与所述切片参数信息指示的切片网络对应的PUD会话，所述终端用于基于所述切片参数信息，与所述网络设备建立PDU会话，并基于所述PDU会话，在所述切片参数信息指示的切片网络上传输第一应用的数据。
  5. 根据权利要求1所述的系统，其特征在于，所述URSP信息还包括操作系统标识OS Id，用于标识操作系统；所述终端的操作系统的OS Id与所述URSP信息中的OS Id相同。
  6. 根据权利要求1所述的系统，其特征在于，所述URSP信息还包括指示信息，用于指示所述URSP信息中包括App Store Id和App Id。
  7. 根据权利要求1所述的系统，其特征在于，
    所述网络设备，还用于向所述终端发送第二消息，第二消息包括允许的网络切片选择辅助信息Allowed NSSAI，用于指示允许终端传输数据切片网络集合；所述切片参数信息指示的切片网络包含于所述切片网络集合中。
  8. 根据权利要求1所述的系统，其特征在于，
    所述终端，还用于向所述网络设备发送注册消息，用于注册并接入所述网络设备，
    或者，
    所述终端，还用于向所述网络设备发送业务更新消息，用于指示所述终端中的业务更新。
  9. 根据权利要求1所述的系统，其特征在于，所述App Id为应用的应用包名。
  10. 根据权利要求1所述的系统，其特征在于，所述应用商店为包括一个或多个应用的应用集合。
  11. 一种终端，其特征在于，包括：
    处理器和存储器，所述存储器与所述处理器耦合；
    所述存储器存储有程序指令，所述程序指令由所述处理器执行时，使得所述终端执行下述步骤：
    接收来自网络设备的第一消息，所述第一消息包括终端设备路由选择策略URSP信息，所述URSP信息包括应用商店标识App Store Id、应用标识App Id和切片参数信息，所述App Store Id用于标识应用商店，所述App Id用于标识应用，所述切片参数信息用于指示切片网络；
    运行第一应用，通过所述切片参数信息指示的切片网络传输所述第一应用的数据，其中，所述第一应用来自所述USRP信息的App Store Id指示的应用商店，所述第一应用的App Id与所述URSP信息中的App Id相同。
  12. 根据权利要求11所述的终端，其特征在于，所述程序指令由所述处理器执行时，使得所述终端执行下述步骤：
    运行第二应用，通过非切片网络传输所述第二应用的数据，其中，所述第二应用的下载来源非所述USRP信息的App Store Id指示的应用商店，所述第二应用的App Id与所述URSP信息中的App Id相同或不同。
  13. 根据权利要求11所述的终端，其特征在于，所述程序指令由所述处理器执行时，使得所述终端执行下述步骤：
    所述终端与所述网络设备之间已建立与所述切片参数信息指示的切片网络对应的协议数据单元PUD会话，基于所述PDU会话，在所述切片参数信息指示的切片网络上传输第一应用的数据。
  14. 根据权利要求11所述的终端，其特征在于，所述程序指令由所述处理器执行时，使得所述终端执行下述步骤：
    若所述终端与所述网络设备之间未建立与所述切片参数信息指示的切片网络对应的PUD会话，基于所述切片参数信息，与所述网络设备建立PDU会话，并基于所述PDU 会话，在所述切片参数信息指示的切片网络上传输第一应用的数据。
  15. 根据权利要求11所述的终端，其特征在于，所述URSP信息还包括操作系统标识OS Id，用于标识操作系统；所述终端的操作系统的OS Id与所述URSP信息中的OS Id相同。
  16. 根据权利要求11所述的系统，其特征在于，所述URSP信息还包括指示信息，用于指示所述URSP信息中包括App Store Id和App Id。
  17. 根据权利要求11所述的终端，其特征在于，所述程序指令由所述处理器执行时，使得所述终端执行下述步骤：
    接收来自所述网络设备的第二消息，所述第二消息包括允许的网络切片选择辅助信息Allowed NSSAI，用于指示允许终端传输数据切片网络集合；所述切片参数信息指示的切片网络包含于所述切片网络集合中。
  18. 根据权利要求11所述的终端，其特征在于，所述程序指令由所述处理器执行时，使得所述终端执行下述步骤：
    向所述网络设备发送注册消息，用于注册并接入所述网络设备，
    或者，
    向所述网络设备发送业务更新消息，用于指示所述终端中的业务更新。
  19. 根据权利要求11所述的终端，其特征在于，所述App Id为应用的应用包名。
  20. 根据权利要求11所述的终端，其特征在于，所述应用商店为包括一个或多个应用的应用集合。
  21. 一种应用数据的传输方法，其特征在于，包括：
    终端接收来自网络设备的第一消息，所述第一消息包括终端设备路由选择策略URSP信息，所述URSP信息包括应用商店标识App Store Id、应用标识App Id和切片参数信息，所述App Store Id用于标识应用商店，所述App Id用于标识应用，所述切片参数信息用于指示切片网络；
    所述终端运行第一应用，通过所述切片参数信息指示的切片网络传输所述第一应用的数据，其中，所述第一应用来自所述USRP信息的App Store Id指示的应用商店，所述第一应用的App Id与所述URSP信息中的App Id相同。
  22. 根据权利要求21所述的方法，其特征在于，所述方法还包括：
    终端运行第二应用，通过非切片网络传输所述第二应用的数据，其中，所述第二应用的下载来源非所述USRP信息的App Store Id指示的应用商店，所述第二应用的App Id 与所述URSP信息中的App Id相同或不同。
  23. 根据权利要求21所述的方法，其特征在于，所述通过所述切片参数信息指示的切片网络传输所述第一应用的数据包括：
    若所述终端与所述网络设备之间已建立与所述切片参数信息指示的切片网络对应的协议数据单元PUD会话，基于所述PDU会话，在所述切片参数信息指示的切片网络上传输第一应用的数据。
  24. 根据权利要求21所述的方法，其特征在于，所述通过所述切片参数信息指示的切片网络传输所述第一应用的数据包括：
    若所述终端与所述网络设备之间未建立与所述切片参数信息指示的切片网络对应的PUD会话，所述终端基于所述切片参数信息，与所述网络设备建立PDU会话，并基于所述PDU会话，在所述切片参数信息指示的切片网络上传输第一应用的数据。
  25. 根据权利要求21所述的方法，其特征在于，所述URSP信息还包括操作系统标识OS Id，用于标识操作系统；所述终端的操作系统的OS Id与所述URSP信息中的OS Id相同。
  26. 根据权利要求21所述的系统，其特征在于，所述URSP信息还包括指示信息，用于指示所述URSP信息中包括App Store Id和App Id。
  27. 根据权利要求21所述的方法，其特征在于，所述终端接收来自网络设备的第一消息之前，还包括：
    所述终端接收来自所述网络设备的第二消息，所述第二消息包括允许的网络切片选择辅助信息Allowed NSSAI，用于指示允许终端传输数据切片网络集合；所述切片参数信息指示的切片网络包含于所述切片网络集合中。
  28. 根据权利要求21所述的方法，其特征在于，所述接收来自所述网络设备的第二消息之前，还包括：
    所述终端向所述网络设备发送注册消息，用于注册并接入所述网络设备，
    或者，
    所述终端向所述网络设备发送业务更新消息，用于指示所述终端中的业务更新。
  29. 根据权利要求21所述的方法，其特征在于，所述App Id为应用的应用包名。
  30. 根据权利要求21所述的方法，其特征在于，所述应用商店为包括一个或多个应用的应用集合。
PCT/CN2021/081093 2020-06-30 2021-03-16 应用数据的传输方法、终端及系统 WO2022001192A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US18/013,502 US20230289432A1 (en) 2020-06-30 2021-03-16 Application Data Transmission Method, User Equipment, and System
EP21832898.7A EP4163808A4 (en) 2020-06-30 2021-03-16 METHOD FOR TRANSMITTING APPLICATION DATA AS WELL AS TERMINAL DEVICE AND SYSTEM

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010615517.7A CN113868635A (zh) 2020-06-30 2020-06-30 应用数据的传输方法、终端及系统
CN202010615517.7 2020-06-30

Publications (1)

Publication Number Publication Date
WO2022001192A1 true WO2022001192A1 (zh) 2022-01-06

Family

ID=78981475

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/081093 WO2022001192A1 (zh) 2020-06-30 2021-03-16 应用数据的传输方法、终端及系统

Country Status (4)

Country Link
US (1) US20230289432A1 (zh)
EP (1) EP4163808A4 (zh)
CN (1) CN113868635A (zh)
WO (1) WO2022001192A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220053444A1 (en) * 2020-08-13 2022-02-17 Alibaba Group Holding Limited Network Communication Method and Apparatus

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109391648A (zh) * 2017-08-04 2019-02-26 华为技术有限公司 一种应用与网络切片的关联方法、装置和通信系统
CN109429277A (zh) * 2017-07-05 2019-03-05 中兴通讯股份有限公司 网络切片的选择方法、装置及系统
CN110120879A (zh) * 2018-02-06 2019-08-13 华为技术有限公司 一种应用服务水平协议的保障方法、设备及系统
CN110768836A (zh) * 2019-10-28 2020-02-07 中国联合网络通信集团有限公司 一种网络切片管理方法及装置
US20200187106A1 (en) * 2017-06-20 2020-06-11 Motorola Mobility Llc Creating a network slice selection policy rule

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105608369B (zh) * 2015-10-30 2019-06-25 周奇 应用软件的安装方法及装置
CN109743766B (zh) * 2018-02-13 2020-06-16 华为技术有限公司 一种数据路由选择的方法及装置
CN111988828B (zh) * 2018-11-23 2021-08-10 腾讯科技（深圳）有限公司 路由选择策略的获取方法、装置及设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200187106A1 (en) * 2017-06-20 2020-06-11 Motorola Mobility Llc Creating a network slice selection policy rule
CN109429277A (zh) * 2017-07-05 2019-03-05 中兴通讯股份有限公司 网络切片的选择方法、装置及系统
CN109391648A (zh) * 2017-08-04 2019-02-26 华为技术有限公司 一种应用与网络切片的关联方法、装置和通信系统
CN110120879A (zh) * 2018-02-06 2019-08-13 华为技术有限公司 一种应用服务水平协议的保障方法、设备及系统
CN110768836A (zh) * 2019-10-28 2020-02-07 中国联合网络通信集团有限公司 一种网络切片管理方法及装置

Also Published As

Publication number Publication date
US20230289432A1 (en) 2023-09-14
CN113868635A (zh) 2021-12-31
EP4163808A4 (en) 2023-11-15
EP4163808A1 (en) 2023-04-12

Similar Documents

Publication Publication Date Title
US20220163932A1 (en) Device control page display method, related apparatus, and system
EP4084486A1 (en) Cross-device content projection method, and electronic device
US11934352B2 (en) Card rendering method and electronic device
WO2021017894A1 (zh) 一种使用远程sim模块的方法及电子设备
WO2021218864A1 (zh) 一种Wi-Fi点对点业务的实现方法以及相关设备
WO2021179990A1 (zh) 一种应用服务器的访问方法及终端
WO2022228011A1 (zh) Quic数据传输方法、装置、客户端及服务端
WO2022042637A1 (zh) 一种蓝牙数据传输方法及相关装置
EP4181003A1 (en) Permission management method and terminal device
CN111316604B (zh) 一种数据传输方法及电子设备
WO2022135157A1 (zh) 页面显示的方法、装置、电子设备以及可读存储介质
WO2022001192A1 (zh) 应用数据的传输方法、终端及系统
CN113746945A (zh) 反向地址解析方法及电子设备
CN114928898B (zh) 建立基于WiFi直接连接的会话的方法和装置
EP4293997A1 (en) Display method, electronic device, and system
WO2021218544A1 (zh) 一种提供无线上网的系统、方法及电子设备
CN115454454A (zh) 应用部署方法、分布式操作系统、电子设备及存储介质
WO2023046028A1 (zh) 用于分布式显示的屏幕识别方法、介质及电子设备
WO2023051204A1 (zh) 跨设备连接方法、电子设备及存储介质
WO2024067170A1 (zh) 设备管理方法及电子设备
WO2023142940A1 (zh) 应用组件分享方法及相关设备
WO2024078315A1 (zh) 一种应用控制方法、电子设备和系统
CN116033592B (zh) 蜂窝通信功能的使用方法和装置
WO2023280160A1 (zh) 一种通道切换方法及装置
EP4362507A1 (en) Communication system and communication method

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21832898

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021832898

Country of ref document: EP

Effective date: 20230103

NENP Non-entry into the national phase

Ref country code: DE