Method and device based on network slice communication and terminal equipment

By using coprocessors to process data in terminal devices and determining network slice selection auxiliary information (S-NSSAI) based on service identification, the problem of resource and power consumption waste in the prior art is solved, and efficient real-time and flexibility are achieved .

CN119052089AActive Publication Date: 2024-11-29HONOR DEVICE CO LTD

Patent Information

Application Number
CN202310621613.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-29
Publication Date
2024-11-29
Estimated Expiration
2043-05-29

AI Technical Summary

Technical Problem

The prior art is difficult to effectively meet the real-time requirements of different network slicing scenarios, resulting in waste of resources and power consumption.

Method used

By using a coprocessor to process data in a terminal device, network slice selection auxiliary information (S-NSSAI) is determined based on service identification, and the coprocessor is used for physical layer processing, improving real-timeness and preventing waste of resources and power consumption.

Benefits of technology

It realizes the real-time requirements of different application scenarios without causing waste of resources and power, and improves processing speed and flexibility.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119052089A_ABST
    Figure CN119052089A_ABST
Patent Text Reader

Abstract

The invention relates to the field of communication, and provides a method and device based on network slice communication and terminal equipment. The terminal equipment determines a first S-NSSAI used for indicating the first network slice based on the first service identifier, and determines a target processing module of a data channel processed by the coprocessor according to the first S-NSSAI, so that the coprocessor is adopted to perform physical layer processing on data through the target processing module, the processing speed can be remarkably improved, and the real-time performance can be improved; for S-NSSAIs of different network slices, different target processing modules can be determined based on different S-NSSAIs, the situation that resources and power consumption are wasted due to undifferentiated scheduling of computing resources of the coprocessor in different network slice scenes can be prevented, the real-time requirements of different application scenes can be met, and the real-time performance of the coprocessor is improved. And the flexibility of the processing process is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a method, apparatus and terminal device based on network slicing communications in the field of communications. Background Art

[0002] At present, mobile communications are developing rapidly. In the 5G era, many new application scenarios have emerged, such as enhanced mobile broadband (eMBB) (for example, live broadcast, cloud gaming, ultra-high-definition video), ultra-reliable and low latency communications (URLLC) (for example, unmanned driving, automatic factories), massive Internet of Things (mloT) (for example, massive sensors deployed in measurement, agriculture, construction, logistics, smart cities, etc.), etc. Different application scenarios have different requirements for the network. In order to meet the network requirements of different application scenarios, network slicing technology has emerged. Network slicing technology can provide different network capabilities for different users in a targeted manner, so that the differentiated requirements of different application scenarios can be met under the same network, and the purpose of flexible resource scheduling and customized design can be achieved.

[0003] It can be seen that different network slices have different requirements for the real-time performance (i.e., latency) of the network. How to better meet the real-time requirements of different network slicing scenarios is a technical problem that needs to be solved urgently. Summary of the invention

[0004] The embodiments of the present application provide a method, apparatus and terminal device based on network slicing communication, which can meet the real-time requirements of different network slicing scenarios without causing waste of resources and power consumption.

[0005] In a first aspect, a method based on network slicing communication is provided, which is applied to a terminal device, and the method includes:

[0006] In response to a user operation, generating a first service identifier, where the first service identifier is used to identify a first service to be currently executed;

[0007] Determine, according to the first service identifier, first network slice selection auxiliary information S-NSSAI corresponding to the first service identifier, where the first S-NSSAI is used to indicate a first network slice corresponding to the first service;

[0008] Determine, according to the first S-NSSAI, a target processing module of a data channel processed by a coprocessor, wherein the target processing module includes at least some processing modules of all processing modules of the data channel;

[0009] The coprocessor is used to process first data related to the first service through the target processing module.

[0010] In the method based on network slicing communication provided in the embodiment of the present application, the terminal device determines the first S-NSSAI for indicating the first network slice based on the first service identifier, and determines the target processing module of the data channel processed by the coprocessor according to the first S-NSSAI, so that the coprocessor is used to process the data at the physical layer through the target processing module. Compared with the use of the CPU to process the data at the physical layer, the use of the coprocessor to process the data can significantly improve the processing speed and improve the real-time performance; in addition, the target processing module of the data channel is determined according to the first S-NSSAI, and for the S-NSSAI of different network slices, different target processing modules can be determined based on different S-NSSAI, which can prevent the waste of resources and power consumption caused by the indifferent scheduling of the computing resources of the coprocessor in different network slicing scenarios, and can meet the real-time requirements of different application scenarios and improve the flexibility of the processing process. Therefore, the embodiment of the present application generally realizes adaptive acceleration based on network slicing without causing waste of resources and power consumption, and meets the real-time requirements of different application scenarios.

[0011] In combination with any implementation of the first aspect, the terminal device includes an application module, a user routing policy URSP module and a protocol stack; and,

[0012] The generating a first service identifier in response to a user operation includes:

[0013] The application module generates the first service identifier in response to the user operation; and the method further includes:

[0014] The application module sends the first service identifier to the URSP module;

[0015] The determining, according to the first service identifier, a first S-NSSAI corresponding to the first service identifier includes:

[0016] The URSP module determines the first S-NSSAI according to the first service identifier; and the method further includes:

[0017] The URSP module sends the first S-NSSAI to the protocol stack;

[0018] The step of determining, according to the first S-NSSAI, a target processing module for the data channel to be processed by the coprocessor comprises:

[0019] The protocol stack determines the target processing module according to the first S-NSSAI;

[0020] The using the coprocessor to process the first data related to the first service through the target processing module includes:

[0021] The protocol stack calls the coprocessor, and the coprocessor processes the first data through the target processing module.

[0022] The method based on network slicing communication provided in the embodiment of the present application completes the accelerated processing process of the physical layer of the data through the interaction between various modules. Since the protocol stack includes a high-level protocol stack and a physical layer, the processing of the data needs to be processed through each layer of the protocol stack. Here, the target processing module is determined by the protocol stack, which facilitates the protocol stack to call the GPU to process the data at the physical layer, and the implementation process is relatively convenient.

[0023] In combination with any implementation of the first aspect, after the URSP module sends the first S-NSSAI to the protocol stack, the method further includes:

[0024] The protocol stack establishes a packet data unit (PDU) session with a network device according to the first S-NSSAI;

[0025] After the PDU session is established, the protocol stack generates a slice service interface corresponding to the first S-NSSAI;

[0026] The protocol stack sends service interface information indicating the slice service interface to the URSP module;

[0027] The URSP module determines, according to the slice service interface, a slice data interface corresponding to the slice service interface;

[0028] The URSP module sends data interface information indicating the slice data interface to the application module, so that the application module transmits service data through the slice data interface.

[0029] In the method based on network slicing communication provided by the embodiment of the present application, the slice data interface is the interface of the application module, and the slice service interface is the interface of the slice channel. For the uplink service data sent through the slice data interface, it is impossible to automatically go through the slice channel, or for the downlink service data sent through the slice service interface, it is impossible to automatically send it to the application module through the slice data interface. In the embodiment of the present application, the URSP module determines the corresponding slice data interface according to the slice service interface, binds the two slice interfaces, and the service data can be normally transmitted through the slice service interface and the slice data interface, that is, the URSP module forwards the uplink service data received through the slice data interface to the protocol stack through the slice service interface corresponding to the slice data interface, so as to transmit the uplink service data through the slice channel of the slice service interface, or the URSP module forwards the downlink service data received through the slice through the slice service interface to the application module through the slice data interface corresponding to the slice service interface, thereby realizing the normal transmission of service data (uplink service data and downlink service data) based on network slicing.

[0030] In combination with any implementation of the first aspect, the application module is configured in the application layer, the URSP module is configured in the application framework layer, and the protocol stack is configured in the modem.

[0031] Compared with the solution of configuring the URSP module in the modem of a device such as a mobile phone or tablet, the method based on network slicing communication provided in the embodiment of the present application configures the URSP module in the application framework layer to implement the URSP function. This does not involve modification of the content of the modem, can reduce the difficulty for developers to participate in the network slicing technology simulation of 5G terminals, and improves the flexibility of implementing the URSP function.

[0032] In combination with any implementation of the first aspect, the application module is configured in the application layer, and the URSP module and the protocol stack are both configured in the application layer.

[0033] Compared with the solution of configuring the URSP module in the operating system of a device such as a computer, the method based on network slicing communication provided in the embodiment of the present application configures the URSP module in the application layer to implement the URSP function. This does not involve modification of the content of the operating system layer, and can reduce the difficulty of developers participating in the network slicing technology simulation of 5G terminals, thereby improving the flexibility of implementing the URSP function.

[0034] In combination with any implementation of the first aspect, the protocol stack is configured in a software defined radio SDR, and the URSP module is configured in the SDR.

[0035] The network slicing communication-based method provided in the embodiment of the present application can better realize the integration of multiple functional modules, reduce memory usage, and facilitate system management by integrating the URSP module and the protocol stack in the SDR.

[0036] In combination with any implementation of the first aspect, determining, according to the first S-NSSAI, a target processing module for a data channel processed by the coprocessor includes:

[0037] According to the first S-NSSAI, the target processing module corresponding to the first S-NSSAI is determined from a first correspondence relationship indicating multiple S-NSSAIs and multiple groups of processing modules, and one S-NSSAI corresponds to at least one group of processing modules.

[0038] The network slice communication-based method provided in an embodiment of the present application determines the target processing module corresponding to the first S-NSSAI by indicating a first correspondence between multiple S-NSSAIs and multiple groups of processing modules, which can simplify the design and facilitate implementation.

[0039] In combination with any implementation method of the first aspect, the first correspondence relationship includes an uplink correspondence relationship and a downlink correspondence relationship, wherein the uplink correspondence relationship is used to indicate a one-to-one correspondence between M S-NSSAIs and M groups of processing modules, and the downlink correspondence relationship is used to indicate a one-to-one correspondence between N S-NSSAIs and N groups of processing modules, and M and N are both integers greater than or equal to 1.

[0040] The method based on network slicing communication provided in the embodiment of the present application, the first correspondence relationship includes an uplink correspondence relationship and a downlink correspondence relationship, which fully considers the uplink transmission and the downlink transmission, and can provide accelerated processing of the physical layer of uplink transmission and downlink transmission for more network slices to the greatest extent, thereby better meeting the real-time requirements of different application scenarios.

[0041] In combination with any implementation of the first aspect, determining, according to the first service identifier, a first S-NSSAI corresponding to the first service identifier includes:

[0042] The first S-NSSAI is determined according to the first service identifier from a second correspondence relationship indicating multiple service identifiers and multiple S-NSSAIs, and at least one service identifier corresponds to one S-NSSAI.

[0043] In combination with any implementation of the first aspect, the target processing module includes a first target processing module, the first target processing module is a processing module of a physical uplink shared channel PUSCH, and the first data includes signaling or uplink service data transmitted through the PUSCH.

[0044] In combination with any implementation of the first aspect, the first service is a live broadcast service, a data backhaul service, or a real-time monitoring service.

[0045] In combination with any implementation of the first aspect, the target processing module includes a second target processing module, the second target processing module is a processing module of a physical downlink shared channel PDSCH, and the first data includes signaling or downlink service data transmitted through the PDSCH.

[0046] In combination with any implementation manner of the first aspect, the first service is a video service or an audio service.

[0047] In combination with any implementation method of the first aspect, the target processing module includes a first target processing module and a second target processing module, the first target processing module is a processing module for a physical uplink shared channel PUSCH, the second target processing module is a processing module for a physical downlink shared channel PDSCH, the first data includes signaling or uplink service data transmitted through the PUSCH, and the first data includes signaling or downlink service data transmitted through the PDSCH.

[0048] In combination with any implementation of the first aspect, the first service is a cloud gaming service.

[0049] In combination with any implementation of the first aspect, the coprocessor is any one of the following processors: a graphics processor GPU, an image signal processor ISP, a digital signal processor DSP, a neural network processor NPU, and a field programmable gate array FPGA.

[0050] In a second aspect, a terminal device is provided, wherein the terminal device is used to execute the method provided in the first aspect. Specifically, the terminal device may include a module for executing any possible implementation of the first aspect.

[0051] In a third aspect, a terminal device is provided, comprising a processor. The processor is coupled to a memory and can be used to execute instructions in the memory to implement the method in any possible implementation of the first aspect. Optionally, the terminal device also includes a memory. Optionally, the device also includes a communication interface, and the processor is coupled to the communication interface.

[0052] According to a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a device, the device implements the method in any possible implementation manner of the first aspect.

[0053] According to a fifth aspect, a computer program product comprising instructions is provided, wherein when the instructions are executed by a computer, the device implements the method in any possible implementation manner of the first aspect.

[0054] In a sixth aspect, a chip is provided, comprising: an input interface, an output interface, a processor and a memory, wherein the input interface, the output interface, the processor and the memory are connected via an internal connection path, and the processor is used to execute the code in the memory. When the code is executed, the processor is used to execute the method in any possible implementation of the first aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] Figure 1 It is a schematic diagram of the architecture of a communication system applicable to an embodiment of the present application.

[0056] Figure 2 It is a schematic flowchart of the PDU session establishment process provided in an embodiment of the present application.

[0057] Figure 3 It is the protocol stack of the 5G user plane provided in the embodiment of the present application.

[0058] Figure 4a It is an exemplary block diagram of the physical layer processing process of PDSCH at the transmitting end provided in an embodiment of the present application.

[0059] Figure 4b It is an exemplary block diagram of the physical layer processing process of PDSCH at the receiving end provided in an embodiment of the present application.

[0060] Figure 5a It is an exemplary block diagram of the physical layer processing process of the PUSCH of the transmitting end provided in an embodiment of the present application.

[0061] Figure 5b It is an exemplary block diagram of the physical layer processing process of the PUSCH at the receiving end provided in an embodiment of the present application.

[0062] Figure 6 This is a diagram of the software and hardware architecture of the terminal device provided in an embodiment of the present application.

[0063] Figure 7 This is another hardware and software architecture diagram of the terminal device provided in an embodiment of the present application.

[0064] Figure 8 This is an exemplary flowchart of the method based on network slicing communication provided in an embodiment of the present application.

[0065] Fig. 9 This is another exemplary flowchart of the method based on network slicing communication provided in an embodiment of the present application.

[0066] Fig.10 This is another exemplary flowchart of the method based on network slicing communication provided in an embodiment of the present application.

[0067] Fig.11 This is another exemplary flowchart of the method based on network slicing communication provided in an embodiment of the present application.

[0068] Fig.12 This is another exemplary flowchart of the method based on network slicing communication provided in an embodiment of the present application.

[0069] Fig.13 It is an exemplary block diagram of the device provided in the embodiment of the present application.

[0070] Fig.14 It is a schematic structural diagram of the device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0071] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0072] The technical solutions of the embodiments of the present application can be applied to various communication systems that can support network slicing, such as the fifth generation (5th generation, 5G) system, or the future sixth generation (6th generation, 6G) system.

[0073] Figure 1 Schematic diagram of the architecture of a communication system applicable to the embodiment of the present application. Figure 1 As shown, the communication system includes a core network device 110, an access network device 120 and at least one terminal device (such as Figure 1 The terminal device 131 and the terminal device 132 in the figure). The terminal device is connected to the access network device by wireless means, and the access network device is connected to the core network device by wireless or wired means. The core network device and the access network device can be independent and different physical devices, or the functions of the core network device and the logical functions of the access network device can be integrated on the same physical device, or the functions of some core network devices and some access network devices can be integrated on one physical device. The terminal device can be fixed in place or movable. Figure 1 This is just a schematic diagram. The communication system may also include other network devices, such as wireless relay devices and wireless backhaul devices. Figure 1 The embodiments of the present application do not limit the number of core network devices, access network devices and terminal devices included in the mobile communication system.

[0074] It should be understood that the terminal devices, access network devices and core network devices of the embodiments of the present application are all devices that can support network slicing.

[0075] The access network device in the embodiment of the present application is an access device that the terminal device accesses to the communication system by wireless means, which may be a base station NodeB, an evolved base station (evolved NodeB, eNodeB), a transmission reception point (TRP), a next generation base station (nextgeneration NodeB, gNB) in a 5G mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system, or a wireless controller in a cloud radio access network (CRAN) scenario, or a relay station, a vehicle-mounted device, a wearable device, and a network device in a future evolved PLMN network, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the access network device.

[0076] The terminal device in the embodiment of the present application may also be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal device may be a mobile phone, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. The embodiment of the present application does not limit the specific technology and specific device form adopted by the terminal device.

[0077] Below, the technical terms and related processing procedures involved in the embodiments of the present application are first explained.

[0078] Network Slicing

[0079] Network slicing is to divide the 5G network into "many slices", each of which meets different user needs. At present, the 4G network does not segment user needs. Regardless of the needs, the network capacity is fixed. In fact, different users have different needs for the network. For example, live broadcast users have higher requirements for uploading, while game users require low latency. Network slicing technology can provide different network capabilities for different users in a targeted manner, thereby meeting the network needs of different business scenarios.

[0080] In network slicing technology, it is not necessary to build a network for each application scenario. Instead, a physical network is divided into multiple virtual logical networks. Each virtual network corresponds to a different application scenario. This is called network slicing.

[0081] 3GPP divides the main types of 5G network slices into the following three categories: eMBB type network slices, mloT type network slices and URLLC type network slices. The main requirements of eMBB type network slices for the network are high bandwidth and low latency. For example, mobile phones can access eMBB type network slices for high-speed downloads, watch 4K high-definition videos, live broadcasts, cloud games and other services. URLLC type network slices are mainly for terminals of the Internet of Vehicles, which have high requirements for latency and reliability. mloT type network slices are mainly for terminals of the Internet of Things, which have large-scale, low mobility, low power consumption, low speed and high data capacity requirements. For example, sensor devices can access mMTC type network slices for transmission of small data packets (such as data collection) and updates of system configurations. In addition, different network slices can be provided under each type of network slice. For example, for eMBB type network slices, there can be network slices that are respectively applied to different scenarios such as high-definition video, live streaming, cloud gaming, etc., that is, the high-definition video scenario corresponds to one network slice in the eMBB type network slice (for example, network slice 11), the live streaming scenario corresponds to another network slice in the eMBB type network slice (for example, network slice 12), and the cloud gaming scenario corresponds to another network slice in the eMBB type network slice (for example, network slice 13).

[0082] In order to realize network slicing, network function virtualization (NFV) is a prerequisite. The so-called NFV is to transfer the software and hardware functions of dedicated devices in the network (such as the mobility management entity (MME) in the core network and the distributed unit (DU) in the wireless access network) to virtual machines (VMs). These virtual hosts are based on industry-standard commercial servers. They are commercial off-the-shelf products, low-cost and easy to install. Simply put, it is to replace the dedicated network element devices in the network with industry-standard servers, storage and network devices.

[0083] After the network is virtualized, the wireless access network is called the edge cloud, and the core network is called the core cloud. VMs in the edge cloud and VMs in the core cloud are interconnected through software defined networks (SDN).

[0084] Currently, network slicing mainly includes two types of network slicing: standardized globally applicable network slicing and operator-customized network slicing.

[0085] User route selection policy (URSP) rules

[0086] Based on network slicing, the URSP rule describes the correspondence between multiple services and multiple network slices. At least one service can correspond to one network slice. Electronic devices can select different network slices for different services based on the correspondence described by the URSP rule. For example, for high-definition video services in eMBB, you can select the corresponding network slice 11; for live broadcast services in eMBB, you can select the corresponding network slice 12; for data collection services in mloT, you can select the corresponding network slice 21; for unmanned driving services in URLLC, you can select the corresponding network slice 31.

[0087] Different services can be identified by different service identifiers, and one service can be identified by one service identifier. For example, the video service is identified by service identifier 1, the massive IoT service can be identified by service identifier 2, and the live broadcast service can be identified by service identifier 3.

[0088] Different network slices may use different single network slice selection assistance information (S-NSSAI) identifiers, that is, one network slice uses one S-NSSAI identifier.

[0089] S-NSSAI includes SST information for indicating the type or service type (slice / service type, SST) of a single network slice, and the SST information is 1 byte. At present, when the value of the SST information is 1, it indicates that the type of the network slice or the service type is the eMBB type, and the SST information can also correspond to 00000001 in 1 byte of binary; when the value of the SST information is 2, it indicates that the type of the network slice or the service type is the URLLC type, and the SST information can also correspond to 00000010 in 1 byte of binary; when the value of the SST information is 3, it indicates that the type of the network slice or the service type is the mloT type, and the SST information can also correspond to 00000011 in 1 byte of binary.

[0090] Exemplarily, S-NSSAI also includes SD information for identifying a slice differentiator (SD), and the SD information includes 3 bytes. As a supplement to the SST information, the SD information is used to further distinguish multiple network slices of the same SST. For example, for eMBB type network slices, the SD information can further indicate network slices of types such as high-definition video, live broadcast, and cloud gaming.

[0091] In the embodiment of the present application, the URSP rules may be obtained from the network or from a local universal platform, and no limitation is made thereto.

[0092] Packet data unit (PDU) session

[0093] Network slices are carried through PDU sessions, and one PDU session can only carry one network slice. After the electronic device determines the network slice, it initiates a PDU session based on the network slice to the core network through the access network device to connect the electronic device to the network for uplink and downlink transmission.

[0094] Figure 2 This is a schematic flowchart of the PDU session establishment process provided in the embodiment of the present application. The PDU session establishment process is explained by taking UE as an example of a terminal device and gNB as an example of an access network device.

[0095] It should be noted that Figure 2 The PDU session establishment process shown is a simplified process, which shows the important steps of the PDU session establishment process. For other related details, please refer to the relevant description of the existing standard protocol (for example, Section 4.3.2.2 of TS 23502 protocol) and will not be repeated here.

[0096] In step S201, the UE sends a PDU session establishment request to the access and mobility management function (AMF) through the gNB. The PDU session establishment request may include: PDU Session ID, Requested PDU Session Type, S-NSSAI, data network name (DNN) and other information.

[0097] In step S202, the AMF selects an appropriate session management function (SMF) according to the PDU session establishment request.

[0098] In step S2031, AMF sends NsmfPDU session create SM Context Request to SMF, including PDU Session Establishment Request, subscription permanent identifier (SUPI), DNN, AMF ID, User Location Information and other information.

[0099] In step S2032, SMF responds to Nsmf PDU session create SM Context Request and replies Nsmf PDU session create SM Context Response to AMF.

[0100] In step S204, the SMF selects a policy control function (PCF) to obtain policy data.

[0101] In step S205, the SMF selects a user plane function (UPF) and allocates an IP Address or prefix to the UE. If IPv6 is involved, the SMF allocates an Interface Identifier to the UE for forming a link-local address.

[0102] In step S206, the signaling interaction of the N4 interface is completed between the SMF and the UPF.

[0103] In step S2071, SMF sends a NamfCommunicationN1N2MessageTransfer message to AMF. It can be understood that through this message, SMF sends information about the N1 interface and the N2 interface to AMF. The message includes the PDU session establishment response (PDU Session Resource Setup Accept) replied by AMF to the UE and the resource establishment request (AN-specific resource setup) initiated by SMF to gNB.

[0104] In step S2072, AMF sends a NamfCommunication N1 N2MessageTransfer Ack message to SMF.

[0105] In step S2081, the AMF sends an N2 PDU Session Request (i.e., PDU Session Resource Setup Request) message and an N1 NAS message to the gNB, where the N2 PDU Session Request is used to request the creation of an N2 PDU session, and the N1 NAS message includes a PDU Session Establishment Accept message and an AN-specific resource setup message initiated by the SMF.

[0106] In step S2082, AMF transparently transmits the PDU Session Establishment Accept message and the resource establishment request (AN-specific resource setup) message initiated by SMF to the UE through the gNB.

[0107] In step S2083, a resource connection is established between the UE and the gNB according to the AN-specific resource setup message.

[0108] In step S2084, the gNB replies to the AMF with an N2 PDU Session Request Ack (i.e., PDU Session Resource Setup Response) message, which carries the gNB side downlink media plane tunnel endpoint information.

[0109] At this point, the transmission channel for uplink transmission has been completed and uplink transmission can be performed.

[0110] In step S2091, AMF sends a NsmfPDUSessionUpdateSMContext Request message to SMF, which carries the resource establishment response from gNB to SMF.

[0111] In step S2092, SMF initiates N4 Session Modification signaling to UPF to negotiate the downlink media plane tunnel information on the gNB side.

[0112] In step S2093, SMF replies NsmfPDUSessionUpdateSMContext Response message to AMF.

[0113] In step S2110, SMF sends a Nsmf PDU Session SM Context Status Notify (Nsmf PDU Session Notify SMContext Status) message to AMF.

[0114] At this point, the transmission channel for downlink transmission has been completed and downlink transmission can be performed.

[0115] Protocol stack, high-level protocol stack

[0116] Figure 3 It is the protocol stack of the 5G user plane provided in the embodiment of the present application.

[0117] For terminal devices (e.g., UE) and access network devices (e.g., gNB), exemplarily, the protocol stack of the user plane includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control layer protocol (RLC) layer, a media access control element (MAC) layer and a physical layer (PHY), and the terminal device and the access network device can interact through signaling of each layer.

[0118] The SDAP layer is a new sublayer added to the user plane of 5G / NR. One of the functions of this layer is to map the quality of service (QoS) flow to the data radio bearer (DRB). Since the interface between gNB and 5G core network in 5G / NR is a new interface, and this interface is based on QoS flow, and the air interface is based on the user's DRB bearer, it can also be said that it is a DRB bearer starting from PDCP, so a new adaptation sublayer SDAP needs to be added in 5G / NR to map QoS to DRB.

[0119] The PDCP layer is used for data transmission, SN number management, PDCP PDU duplication detection, encryption and decryption, and integrity protection.

[0120] The RLC layer is responsible for segmentation / concatenation, retransmission control, duplication detection, and sequence transmission to upper layers.

[0121] The MAC layer is used to control the multiplexing of logical channels, hybrid ARQ retransmission, and scheduling of uplink and downlink. MAC serves the RLC in the form of logical channels.

[0122] The PHY layer is used to implement data encoding / decoding, modulation / demodulation, multi-antenna mapping and other types of physical layer functions (see below for a detailed description of the physical layer processing process). The physical layer provides services to the MAC layer in the form of a transmission channel.

[0123] In the embodiment of the present application, the high-level protocol stack includes each layer above the PHY layer in the protocol stack, for example, Figure 3 In the user plane, the high-level protocol stack includes the MAC layer, PLC layer, PDCP layer and SDAP layer.

[0124] It should be understood that the protocol stack can implement the functions of the protocol stack by pure software, or the functions of the protocol stack can be implemented by a combination of software and hardware. In the case where the protocol stack implements the functions of the protocol stack by pure software, the protocol stack does not rely on dedicated hardware (dedicated chips, modules, etc.), and the protocol stack can adopt an open source protocol stack (OAI, srsRAN, etc.) or a commercial protocol stack, without any limitation here.

[0125] Physical layer processing

[0126] The physical downlink shared channel (PDSCH) and the physical uplink shared channel (PUSCH) are channels of the physical layer. PDSCH is used for downlink transmission, and PUSCH is used for uplink transmission. Both are used to transmit service data and signaling.

[0127] The processing of the PHY layer includes the physical layer processing of PDSCH and PUSCH. It should be understood that the physical layer processing of PDSCH or PUSCH mentioned in the embodiments of the present application means the processing of data (or service data or signaling or information) at the physical layer of PDSCH or PUSCH, wherein the data (or service data or signaling or information) is carried on PDSCH or PUSCH.

[0128] The following, combined Figure 4a and Figure 4b , and briefly introduce the physical layer processing processes of PDSCH and PUSCH respectively.

[0129] Figure 4a It is an exemplary block diagram of the physical layer processing process of PDSCH at the transmitting end provided in an embodiment of the present application. Figure 4b is an exemplary block diagram of the physical layer processing process of the PDSCH at the receiving end provided by the embodiment of the present application. That is, Figure 4b The physical layer processing process of PDSCH at the receiving end is Figure 4a The reverse process of the physical layer processing of PDSCH at the transmitting end.

[0130] exist Figure 4a In the physical layer processing of the PDSCH at the transmitting end, the process includes: cyclic redundancy check (CRC) insertion, code block segmentation, channel coding, rate matching, scrambling, modulation, layer mapping, antenna port mapping and resource block mapping. Figure 4bThe physical layer processing of the PDSCH at the receiving end includes: resource block demapping, antenna port demapping, layer demapping, demodulation, descrambling, rate matching, channel decoding, code block merging, and CRC removal.

[0131] CRC insertion, CRC removal

[0132] For the transmitting side, a CRC is added to each transport block to provide error detection.

[0133] For the receiving end, the added CRC is removed from the transport block to restore the original transport block.

[0134] Code block segmentation and code block merging

[0135] For the transmitter, the internal interleaver defined in the encoder is only used for coded blocks of limited size. If the coded block size of the transport block (including the transport block CRC) exceeds the maximum code block size, the transport block needs to be segmented into smaller code blocks. In addition, after the transport block is segmented into multiple code blocks, a CRC is added after each code block.

[0136] For the receiving end, the previously segmented code blocks can be merged and the decoded transport blocks can be restored according to the scheduling information.

[0137] Channel coding, channel decoding

[0138] For the transmitting end, each code block is channel-coded to improve the reliability of the transmission process. For the convenience of description, the data after channel coding is referred to as a coded bit block.

[0139] For the receiving end, the coded bit block is decoded using the same coding method to restore the code block before channel coding.

[0140] Rate matching, de-rate matching

[0141] For the transmitter, the purpose of rate matching is to parse the coded bit blocks sent by the signal encoder to determine the exact set of coded bits to be transmitted in a given transmission time interval (TTI) or subframe. It should be understood that rate matching operates on the set of all coded bit blocks corresponding to a transport block, rather than operating separately on the coded bits corresponding to a single code block.

[0142] For the receiving end, the rate-matched coded block transport block is de-rate matched to recover the coded bit block that is not rate-matched.

[0143] Scrambling and descrambling

[0144] If scrambling is not performed, the signal encoder at the receiving end will, at least in theory, match and receive both the interference signal and the desired signal, so that interference cannot be suppressed. Therefore, in order to effectively suppress interference, at the transmitting end, the rate-matched transmission block is scrambled, and adjacent cells use different scrambling code sequences. In this way, the scrambled interference signal is randomized, thereby ensuring that the processing gain provided by the channel coding is fully utilized. In addition, illustratively, scrambling is also performed based on the identifier of the receiving end. For ease of description, the scrambled data is referred to as a scrambled bit block.

[0145] For the receiving end, the scrambled bit block is descrambled to recover the rate-matched coded bit block.

[0146] Modulation, demodulation

[0147] For the transmitting end, the scrambled bit blocks are converted into corresponding complex-valued modulation symbol blocks, and modulation schemes such as QPSK, 16QAM, 64QAM and 256QAM can be used. For the convenience of description, the modulated data is referred to as modulation symbols.

[0148] At the receiving end, the modulation symbols are demodulated to restore the scrambled bit blocks.

[0149] Layer Mapping, De-Layer Mapping

[0150] For the transmitter, the modulation symbols are mapped to multiple layers (for example, 4 or 8 layers) in order to split the data into multiple channels for transmission. In 3GPP R10, the maximum number of layers for uplink transmission is 4, and the maximum number of layers for downlink transmission is 8, and there is also a diversity mode for downlink.

[0151] For the receiving end, the data is de-layered and mapped.

[0152] Antenna port mapping, antenna demapping

[0153] For the transmitter, antenna port mapping performs joint processing on the modulation symbols and maps the result to a set of antenna ports for transmission. Depending on different multi-antenna transmission schemes, antenna port mapping can be configured in different ways, including transmit diversity, beamforming, and spatial division multiplexing.

[0154] For the receiving end, the data is de-antenna-port-mapped.

[0155] Resource block mapping, resource block demapping

[0156] For the transmitter, the symbols to be sent on each antenna port are mapped to available resource elements in a set of resource blocks, where each resource block may include 84 resource elements (7 orthogonal frequency division multiplexing (OFDM) symbols, each symbol having 12 subcarriers).

[0157] For the receiving end, the symbol carried by each resource element is mapped to each antenna port.

[0158] Figure 5a It is an exemplary block diagram of the physical layer processing process of the PUSCH of the transmitting end provided in an embodiment of the present application. Figure 5b is an exemplary block diagram of the physical layer processing process of the PUSCH at the receiving end provided by the embodiment of the present application. That is, Figure 5b The physical layer processing process of PUSCH at the receiving end is Figure 5a The reverse process of the physical layer processing of the PUSCH at the transmitting end.

[0159] exist Figure 5a In the physical layer processing of the PUSCH at the transmitting end, the process includes: CRC insertion, code block segmentation, channel coding, rate matching, scrambling, modulation, layer mapping, precoding, antenna port mapping and resource block mapping. Figure 5b The physical layer processing of the PUSCH at the receiving end includes: resource block demapping, antenna port demapping, precoding demapping, layer demapping, demodulation, descrambling, rate matching demapping, channel decoding, code block merging, and CRC removal.

[0160] It can be seen that the physical layer processing process of PUSCH is roughly the same as that of PDSCH. The biggest difference is that the physical layer processing process of PUSCH adds precoding and de-precoding processes, which are optional and specific to UE implementation.

[0161] The above is only a brief introduction to the physical layer processing of PDSCH and PUSCH. For the specific description of each process, please refer to the relevant description of the prior art, which will not be repeated here.

[0162] Since the embodiments of the present application are mainly applied to various terminal devices, the present application mainly involves the processing of the physical layer of the PDSCH and PUSCH by the terminal device. Figure 5a In the downlink transmission, the terminal device acts as the receiving end and executes each step in the direction of the arrow. Figure 4b Perform each step in the direction of the arrow shown.

[0163] In the following, for the convenience of description, a plurality of processing modules with different functions of PDSCH or PUSCH are defined, and one processing module is used to perform a step in the processing of the physical layer of PDSCH or PUSCH. For example, a processing module for performing channel coding is defined as a channel coding module, and a processing module for performing channel decoding is defined as a channel decoding module.

[0164] Coprocessor

[0165] A coprocessor is a processor developed and applied to assist the central processing unit in completing tasks that it cannot perform or that are inefficient or ineffective. There are many tasks that the central processing unit cannot perform, such as signal transmission between devices and management of access devices; and tasks that are inefficient or ineffective include graphics processing and audio processing. In order to perform these tasks, coprocessors were born.

[0166] Exemplarily, the coprocessor may include, but is not limited to, any of the following processors: a graphics processing unit (GPU), an image signal processor (ISP), a digital signal processor (DSP), a neural-network processing unit (NPU), and / or a field-programmable gate array (FPGA) and other processors.

[0167] In an embodiment of the present application, based on the judgment of the protocol stack, the coprocessor can perform physical layer processing on the data to increase the processing speed.

[0168] The following is a schematic description of the software and hardware architecture applicable to the embodiments of the present application.

[0169] Mobile phone software system

[0170] Figure 6 It is a diagram of the software and hardware architecture of the terminal device provided in the embodiment of the present application. It can be understood that Figure 6 This is a hardware and software architecture diagram using the Android system as an example, which is applicable to devices such as mobile phones, tablets, and smart watches. Figure 6 The layered architecture divides the software into several layers, each layer has a clear role and division of labor, and the layers communicate with each other through software interfaces. In some embodiments, the Android software system is divided into four layers, from top to bottom, namely the application layer, application framework layer, Android runtime (Android runtime) and system library and driver layer, and below the driver layer is the hardware layer.

[0171] The application layer may include a series of applications. For example, the application may include applications such as camera, call, short message, video, music, gallery, calendar, map, navigation, Bluetooth, etc.

[0172] The application framework layer provides an application programming interface (API) and a programming framework for the application programs in the application layer. The application framework layer includes some predefined functions.

[0173] Exemplarily, the application framework layer may include a window manager, a content provider, a telephony manager, a resource manager, a connection manager, a URSP module, and the like.

[0174] The window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc.

[0175] Content providers are used to store and retrieve data and make it accessible to applications. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0176] The phone manager is used to provide communication functions of the electronic device 100, such as management of call status (including connecting, hanging up, etc.).

[0177] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0178] The connection manager is used to provide functions related to network changes. Exemplarily, the connection manager can be used to monitor network connections (Wi-Fi, GPRS, UMTS, etc.), to send broadcast attempts when network connections change, to try to switch to another network when a network connection fails, and to provide an application interface that allows applications to query coarse-grained or fine-grained status of available networks.

[0179] The URSP module is used to determine the network slice corresponding to the service according to the URSP rule and the service, and is also used to receive, update, and delete the URSP rule, and is used to map the data interface of the application layer to the corresponding service interface, forward the uplink service data from the application layer to the protocol stack, and forward the downlink service data from the protocol stack to the application layer. Exemplarily, the URSP module is also used to store the URSP rule.

[0180] Android runtime includes core libraries and virtual machines. Android runtime is responsible for scheduling and management of the Android system.

[0181] The core library consists of two parts: one part is the function that needs to be called by the Java language, and the other part is the Android core library.

[0182] The application layer and the application framework layer run in the virtual machine. 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 life cycle management, stack management, thread management, security and exception management, and garbage collection.

[0183] The system library may include multiple functional modules, such as surface manager, media libraries, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.

[0184] The surface manager is used to manage the display subsystem and provide the fusion of 2D and 3D layers for multiple applications.

[0185] The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0186] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0187] A 2D graphics engine is a drawing engine for 2D drawings.

[0188] The driver layer is a layer between hardware and software. Exemplarily, the driver layer may include display driver, camera driver, audio driver, sensor driver, etc.

[0189] The hardware layer is the lowest level module in the device, including various types of processors, cameras and other devices. The processors may include modems, GPUs, central processing units (CPUs), application processors (APs), ISPs, video codecs, DSPs, baseband processors, FPGAs, and / or NPUs.

[0190] The modem is configured with a protocol stack, which is used to initiate a PDU session based on the network slice, and determine whether to use a coprocessor (for example, a GPU) to perform physical layer processing on the data based on the network slice. When it is determined that a coprocessor is required to perform physical layer processing on the data, at least one processing module of the physical layer is selected based on the network slice, and the GPU is used to process the data through the at least one processing module to achieve physical layer acceleration and improve the processing speed.

[0191] In the embodiment of the present application, as mentioned above, the above processors such as GPU, ISP, DSP, NPU, and / or FPGA can be collectively referred to as coprocessors. Based on the judgment of the protocol stack, the coprocessor can perform physical layer processing on the data to increase the processing speed.

[0192] It should be understood that Figure 6 The hardware and software architecture diagram shown is for illustrative purposes only and should not be construed as limiting the embodiments of the present application.

[0193] For example, in some embodiments, the URSP module can be configured in the modem to implement the functions of the URSP module in the modem, that is, the URSP module and the protocol stack are integrated in the modem. However, in the embodiment where the URSP module is configured in the modem, due to the combination of software and hardware, when implementing the functions of the URSP module, the relevant contents of the modem will be modified, thereby increasing the difficulty for developers to participate in the network slicing technology simulation of 5G terminals, and the URSP function based on the modem lacks flexibility.

[0194] As a preferred method, Figure 6 As shown, the URSP module is removed from the modem as hardware and configured in the application framework layer to implement the URSP function. This does not involve modification of the content of the modem, which can reduce the difficulty for developers to participate in the network slicing technology simulation of 5G terminals and improve the flexibility of implementing the URSP function.

[0195] Figure 7 It is another hardware and software architecture diagram of the terminal device provided in the embodiment of the present application. It can be understood that Figure 7 The software architecture above the hardware layer shown is more suitable for computer devices such as laptops, personal computers, etc. Figure 7 ,The software architecture from top to bottom may include: application layer, operating system layer and driver layer, and below the driver layer is the hardware layer.

[0196] The application layer may include, for example, URSP modules, software defined radio (SDR) modules, video, office software, music, video and other applications.

[0197] SDR is a radio broadcast communication technology that is based on software-defined wireless communication protocols rather than hard-wired. In other words, frequency bands, air interface protocols and functions can be upgraded through software downloads and updates without completely replacing the hardware. SDR provides an effective and secure solution to the problem of building multi-mode, multi-frequency and multi-function wireless communication devices.

[0198] Different from Figure 6 The modem is configured with a protocol stack. Figure 7 In the software architecture shown, a protocol stack is configured in the SDR. For a specific description of the protocol stack, please refer to the relevant description above and will not be repeated here.

[0199] Different from Figure 6 The URSP module is configured in the application framework layer. Figure 7 In the software architecture shown, the URSP module is set in the application layer. For the specific description of the URSP module, please refer to the relevant description above and will not be repeated here.

[0200] Understandably, Figure 7 In the software architecture shown, the URSP module and SDR can be installed as applications on a device such as a computer, and the technical solution of the present application can be implemented by running the URSP module and SDR applications.

[0201] It should also be understood that the URSP module can be used as an independent instance process of the software framework (such as Figure 7 As shown), it can also be integrated in the SDR, so that the protocol stack and the URSP module are both integrated in the SDR.

[0202] The operating system layer is the intermediate bridge between hardware and software, which consists of machine instructions and generalized instructions. Among them, machine instructions refer to instructions that the CPU can directly recognize and execute, and generalized instructions refer to software instructions defined and interpreted by the system. Exemplarily, the operating system layer includes: content management module, process management module, file management module, device management module, and driver management module.

[0203] The memory management module is mainly used for the management of internal memory. Its main tasks are: allocating memory space, ensuring that there is no conflict in the storage space occupied by each job, and preventing each job from interfering with each other in its own storage area.

[0204] The essence of the process management module is to manage the central processing unit, so the process management module is often called the processor management module. The process management module can be used to manage process control, process synchronization, inter-process communication and process scheduling. Among them, process control mainly deals with the creation state transition of the process, process cancellation, and the allocation and recovery of related process resources; process synchronization mainly deals with the relationship between inheritance, including process synchronization and mutual exclusion, inter-process communication mainly deals with the exchange of information between mutually cooperating processes, and process scheduling is to select a process from the ready queue according to a certain algorithm to actually execute it in the processor.

[0205] The file management module is used to manage various hardware resources, such as USB flash drives, network disks, keyboards, etc.

[0206] The device management module is mainly responsible for managing various peripheral devices (referred to as: peripherals), including allocation, startup and fault handling. The main task is: when users use external devices, they must make requests and wait for the operating system to make unified allocations before they can be used. When the user's program runs to use a peripheral, the operating system is responsible for driving the peripheral.

[0207] The driver management module is used to provide the connection between programs and hardware, and to provide various system services and interfaces.

[0208] The driver layer is a layer between hardware and software. Exemplarily, the driver layer may include a network card driver, a hard disk driver, a graphics card driver, and an audio driver.

[0209] The hardware layer is the lowest level module in the device. For example, it can include network cards, hard disks, graphics cards, and various types of processors. For example, the processor can include GPU, CPU, AP, ISP, video codec, DSP, NPU and other processors.

[0210] It should be understood that Figure 7 The hardware and software architecture diagram shown is for illustrative purposes only and should not be construed as limiting the embodiments of the present application.

[0211] For example, in some embodiments, the URSP module can be configured in the operating system layer to implement the functions of the URSP module in the operating system layer. However, in the embodiment where the URSP module is configured in the operating system layer, when implementing the functions of the URSP module, the modification of the relevant contents of the operating system layer will be involved, thereby increasing the difficulty for developers to participate in the network slicing technology simulation of 5G terminals, and the implementation of the URSP function based on the operating system layer lacks flexibility.

[0212] As a preferred method, Figure 7As shown, the URSP module is removed from the operating system layer and configured in the application layer to implement the URSP function. This does not involve the modification of the content of the operating system layer, which can reduce the difficulty for developers to participate in the network slicing technology simulation of 5G terminals and improve the flexibility of implementing the URSP function.

[0213] It should be understood that Figure 6 and Figure 7 The hardware and software architecture diagram shown is only for illustrative purposes and should not be construed as limiting the embodiments of the present application. In other embodiments, the software architecture in the hardware and software architecture may also exist in other forms, including more or fewer modules, but at least including the functional modules of the application layer, URSP module, and protocol stack.

[0214] Based on the problem of how to better meet the real-time requirements in different network slicing scenarios in the prior art, the embodiment of the present application provides a method based on network slicing communication, which determines whether it is necessary to use a coprocessor to process the data at the physical layer according to the network slice corresponding to the service. When it is determined that the coprocessor needs to be used to process the data at the physical layer, at least one processing module of the physical layer is determined according to the network slice, and the coprocessor is used to process the data through the at least one processing module. Compared with using the CPU to process the data at the physical layer, using a coprocessor to process the data can significantly improve the processing speed and improve the real-time performance; in addition, the processing module of the physical layer to be processed by the coprocessor is determined according to the network slice, and different processing modules to be processed by the coprocessor can be determined according to different network slices, which can prevent the indifferent scheduling of the computing resources using the coprocessor in different network slicing scenarios to cause waste of resources and power consumption, and can match the real-time requirements of different application scenarios, and can also improve the flexibility of the processing process. The embodiment of the present application generally realizes adaptive acceleration based on network slicing to meet the real-time requirements of different application scenarios.

[0215] It should be noted that the "data" mentioned in the embodiments of the present application is data in a broad sense, which means any content transmitted through bits, including business data and signaling. Business data can also be understood as application data, such as video data, audio data and other data associated with actual business, and signaling can be some information used for business data transmission, such as the PDU session establishment request sent by the terminal in establishing a PDU session and the PDU session establishment response received.

[0216] The following, combined Figures 8 to 10, through the interaction between the modules in the terminal device, the embodiment of the present application is described in detail. Taking the GPU as an example of a coprocessor, through the mutual interaction between the application layer, the URSP module, the protocol stack, the GPU and the CPU (not shown in the figure), the GPU is used to process the data at the physical layer to achieve physical layer acceleration, improve the processing speed, and meet the real-time requirements of the current network slicing scenario.

[0217] It should be understood that the URSP module and protocol stack can be applied to Figure 6 and Figure 7 And any other forms of software architecture, the embodiments of the present application are not limited in any way.

[0218] Figure 8 It is an exemplary flow chart of a method 800 based on network slicing communication provided in an embodiment of the present application. In method 800, the terminal device determines the target processing module of PUSCH processed by GPU based on S-NSSAI used to identify the network slice, and the GPU processes the data (service data and signaling) through the target processing module to achieve physical layer acceleration, improve the processing speed, and meet the real-time requirements of the current network slicing scenario.

[0219] It should be understood that in method 800, for data (service data and signaling) transmitted via PDSCH, the CPU is used to perform physical layer processing on the data in a manner according to the prior art.

[0220] In step 801, application #1 detects a user's operation on application #1.

[0221] For example, the user opens application #1, and application #1 can detect the user's operation of opening application #1.

[0222] Application #1 can be a client application or a browser application, without any limitation. For example, application #1 can be a live video application that has high real-time requirements for uplink transmission (for example, ), real-time high-definition monitoring, high-definition industrial video backhaul, etc., require the transmission of a large amount of uplink data to the network. For another example, application #1 can also be, for example etc.

[0223] In step 802, application #1 sends service identifier #1 to the URSP module.

[0224] Correspondingly, the URSP module receives the service identifier #1.

[0225] After detecting the user's operation, application #1 generates service identifier #1 based on the service executed by application #1, and sends the service identifier #1 to the URSP module.

[0226] It can be understood that service identifier #1 is used to identify the service executed by application #1 (recorded as service #1). For example, service #1 is a live broadcast service, and service identifier #1 is used to identify the live broadcast service.

[0227] Exemplarily, the service identifier can be represented by at least one of an application identification (APP ID), an Internet protocol (IP) triplet information, a fully qualified domain name (FQDN), and a DNN. The IP triplet information includes: a source IP address, a target IP address, and an upper-layer protocol type. Specifically, the source IP address is the IP address of the PDU session corresponding to the UE, the target IP address is the IP address of the server storing the service data of the target service, and the upper-layer protocol type is the transmission control protocol (TCP) or the user datagram protocol (UDP). For example, for a client application, an APP ID or FQDN can be used as a service identifier. For another example, for a browser application, an FQDN can be used as a service identifier.

[0228] In step 803, after receiving the service identifier #1, the URSP module determines the S-NSSAI #1 corresponding to the service identifier #1.

[0229] The URSP module stores a correspondence between multiple service identifiers and multiple S-NSSAIs (recorded as correspondence #1), at least one service identifier corresponds to one S-NSSAI, one S-NSSAI is used to uniquely identify one network slice, and one service identifier is used to uniquely identify one service. The URSP module receives service identifier #1, and determines the S-NSSAI corresponding to service identifier #1 (recorded as S-NSSAI #1) from the correspondence #1 between multiple service identifiers and multiple S-NSSAIs. S-NSSAI #1 is used to indicate network slice #1, that is, the URSP module determines the network slice #1 corresponding to the service identified by service identifier #1.

[0230] In the implementation, the URSP module may include a database unit, a URSP unit, and a routing unit. The database unit stores a correspondence relationship #1 between multiple service identifiers and multiple S-NSSAIs. The URSP unit is used to determine the corresponding S-NSSAI from the correspondence relationship #1 stored in the database unit according to a service identifier. For service identifier #1, the URSP unit is used to determine the S-NSSAI corresponding to service identifier #1 from the correspondence relationship #1 stored in the database unit according to service identifier #1. The routing unit is used to map the data interface of the application layer to the service interface (refer to the description of step S809 for details).

[0231] In step S804, the URSP module sends S-NSSAI#1 to the protocol stack.

[0232] Correspondingly, the protocol stack receives S-NSSAI#1.

[0233] In step S805, the protocol stack determines the target processing module for PUSCH to be processed by GPU according to S-NSSAI#1.

[0234] After receiving S-NSSAI#1, the protocol stack determines that the GPU needs to be used to process PUSCH according to S-NSSAI#1, and determines the target processing module to be processed by the GPU from the multiple processing modules of PUSCH, so that the GPU processes the data (service data and signaling) transmitted through PUSCH through the target processing module to improve the processing speed. It should be understood that the multiple processing modules of PUSCH are all processing modules of PUSCH. Among them, the high-level protocol stack in the protocol stack can perform this step.

[0235] As mentioned above, a PUSCH (or PDSCH) processing module is used to perform a step in the physical layer processing of the PUSCH (or PDSCH). Figure 5a The multiple processing modules of the PUSCH of the terminal device include: a CRC insertion module, a code block segmentation module, a channel coding module, a rate matching module, a scrambling module, a modulation module, a layer mapping module, a precoding module, an antenna port mapping module and a resource block mapping module.

[0236] The target module unit of PUSCH includes at least one processing module, which may be some of the multiple processing modules of PUSCH, or all of the multiple processing modules, and is specifically related to the network slice #1 identified by S-NSSAI #1.

[0237] For example, if the service #1 corresponding to network slice #1 is a high-definition real-time data backhaul service, a live broadcast service, or a high-definition real-time monitoring service, the target processing module determined based on S-NSSAI #1 used to identify network slice #1 may be all processing modules of PUSCH. For another example, if the service #1 corresponding to network slice #1 is a non-high-definition data backhaul service or a non-high-definition real-time monitoring service, the target processing module determined based on S-NSSAI #1 used to identify network slice #1 may be a partial processing module of PUSCH.

[0238] Exemplarily, a correspondence relationship (denoted as correspondence relationship #2) is stored in the protocol stack, and the correspondence relationship #2 includes an uplink correspondence relationship and a downlink correspondence relationship. The uplink correspondence relationship and the downlink correspondence relationship are both used to indicate the correspondence between multiple S-NSSAIs and multiple groups of processing modules. One S-NSSAI corresponds to a group of processing modules, each group of processing modules includes at least one processing module, and the processing modules in each group of processing modules are not exactly the same.

[0239] In the implementation, the protocol stack matches S-NSSAI#1 with the above-mentioned correspondence #2 (uplink correspondence and downlink correspondence), and finally matches a group of processing modules corresponding to S-NSSAI#1 from the uplink correspondence. This group of processing modules is the target processing module of PUSCH using GPU processing corresponding to S-NSSAI#1.

[0240] Table 1 is the uplink correspondence shown in the embodiment of the present application. The first column represents the S-NSSAI, and the second column represents a group of processing modules corresponding to a specific S-NSSAI. For example, a group of processing modules corresponding to S-NSSAI#A includes: a channel coding module, a rate matching module, and an scrambling module; a group of processing modules corresponding to S-NSSAI#B includes a channel coding module; a group of processing modules corresponding to S-NSSAI#C are all processing modules of PUSCH; a group of processing modules corresponding to S-NSSAI#D includes: a channel coding module and a modulation module. S-NSSAI#1 can be any S-NSSAI in Table 1.

[0241] Table 2 is a downlink correspondence relationship shown in an embodiment of the present application. For specific descriptions, please refer to the description in Table 1 and will not be repeated here.

[0242] It should be noted that the same S-NSSAI can correspond to a set of processing modules for PUSCH and a set of processing modules for PDSCH, that is, the data under the network slice identified by the S-NSSAI needs to use the GPU to perform physical layer processing on PUSCH and PDSCH to achieve physical layer acceleration of PUSCH and PDSCH. As shown in Tables 1 and 2, S-NSSAI#A corresponds to the channel coding module, rate matching module, and scrambling module of PUSCH, as well as the channel decoding module and rate matching module of PDSCH.

[0243] Alternatively, an S-NSSAI may correspond only to a set of processing modules for PUSCH, that is, the data under the network slice identified by the S-NSSAI needs to use the GPU to perform physical layer processing on PUSCH only. As shown in Table 1, S-NSSAI#B corresponds only to the channel coding module of PUSCH.

[0244] Alternatively, an S-NSSAI may correspond only to a set of processing modules for PDSCH, that is, the data under the network slice identified by the S-NSSAI needs to use the GPU to perform physical layer processing only on PDSCH.

[0245] It should be understood that the uplink correspondence shown in Table 1 and the downlink correspondence shown in Table 2 are merely illustrative and should not constitute a limitation on the embodiments of the present application.

[0246] Table 1 Uplink correspondence

[0247]

[0248] Table 2 Downlink Correspondence

[0249]

[0250] In step S806, the protocol stack initiates a PDU session according to S-NSSAI#1 and performs a PDU session establishment process.

[0251] That is to say, the protocol stack initiates a PDU session for network slice #1 identified by S-NSSAI #1, and completes the establishment of the PDU session through the interaction between the access network device and the core network device.

[0252] In the process of establishing a PDU session, combined with Figure 2In step S201, the protocol stack of the terminal device generates a PDU session establishment request. After the physical layer processes the PDU session establishment request, it is sent to the AMF through the transceiver in the terminal device through the access network device to start the establishment of the PDU session. Then, through the interaction between the terminal device, the access network device and the various network elements of the core network device, the establishment of the PDU session is completed. Among them, the PDU session establishment request includes the S-NSSAI#1 determined and sent by the URSP module received by the protocol stack. For a detailed description of the PDU session establishment process, please refer to Figure 2 The relevant description will not be repeated here.

[0253] During the PDU session establishment process, for signaling transmitted through PUSCH, the GPU can be used to process the signaling through the target processing module. For signaling transmitted through PDSCH, the CPU can be used to process the signaling through the PDSCH processing module. The following, through steps S8061 and S8062, the process of processing signaling transmitted through PUSCH and PDSCH is specifically described.

[0254] In step S8061, the protocol stack calls the GPU, and the GPU processes the signaling transmitted through the PUSCH during the PDU session establishment process through the target processing module.

[0255] Combination Figure 2 For example, the signaling transmitted through PUSCH during the PDU session establishment process may include: the PDU session establishment request (PDU session establishment request) in step S201, and the relevant information of the terminal device (such as UE) and the access network device (such as gNB) establishing a resource connection in step S2083. Of course, the signaling transmitted through PUSCH during the PDU session establishment process may also include other Figure 2 For the signaling shown, please refer to the more specific PDU session establishment process in the prior art.

[0256] For the signaling transmitted through PUSCH during the PDU session establishment process, after the high-level protocol stack of the protocol stack processes the signaling (processing the signaling through the SDAP layer, PDCP layer, RLC layer, and MAC layer in sequence), the GPU can be called through the high-level protocol stack or the physical layer, and the embodiments of the present application do not impose any restrictions. In addition, after the GPU (or, the GPU and the CPU) performs complete physical layer processing on the signaling, the CPU obtains the final processing result (i.e., the signaling after complete processing at the physical layer), and finally the CPU controls the transceiver to send the processed signaling.

[0257] In the case where the target processing module includes all processing modules of PUSCH, the protocol stack calls the GPU, and after the GPU processes the signaling through the target processing module, it feeds back the final processing result (the signaling after complete processing at the physical layer) to the CPU, so that the CPU controls the transceiver to send the processed signaling. In this case, the GPU performs complete physical layer processing on the signaling, and the GPU obtains the signaling after the physical layer processing is completed, that is, the final processing result, and feeds back the final processing result to the CPU.

[0258] In the case where the target processing module includes a partial processing module of PUSCH, the protocol stack calls the GPU, and the GPU processes the signaling through the target processing module. For other processing modules in PUSCH except the target processing module, the protocol stack calls the CPU (not shown in the figure), and the CPU processes the signaling through the other processing modules. The CPU obtains the final processing result (the signaling after complete processing at the physical layer), and finally the CPU controls the transceiver to send the processed signaling. In this case, the GPU processes part of the signaling at the physical layer, and the CPU processes another part of the signaling at the physical layer. Therefore, the signaling is completely processed at the physical layer by the CPU and the GPU.

[0259] If the processing flow of some processing modules of the PUSCH included in the target processing module is discontinuous, for example, the previous processing module is processed by the GPU, the next processing module is processed by the CPU, and the next processing module is processed by the GPU, the GPU and the CPU mutually feed back the processing result of the current processing module, so that the GPU or the CPU processes the next processing module according to the fed-back processing result. For example, the target processing module processed by the GPU includes a channel coding module, a rate matching module, and an scrambling module, then the CPU processes the remaining processing modules, the CPU first processes the signaling through the CRC insertion module and the code block segmentation module, and feeds back the obtained processing result #1 to the GPU, the GPU continues to process the signaling through the channel coding module, the rate matching module, and the scrambling module according to the processing result #1, and feeds back the obtained processing result #2 to the CPU, the CPU continues to process the signaling through the remaining processing modules according to the processing result #2, to obtain the final processing result.

[0260] In the implementation, exemplarily, the GPU is configured with interfaces of various processing modules for PUSCH and PDSCH. After the protocol stack determines the target processing module for PUSCH, the interface of each processing module in the target processing module is called to enable the GPU to run. In this way, the GPU is called by calling the interfaces of various processing modules configured in the GPU, and the signaling transmitted through the PUSCH is processed by the target processing module.

[0261] In step S8062, the protocol stack calls the CPU, so that the CPU processes the signaling transmitted through the PDSCH through the PDSCH processing module.

[0262] Combination Figure 2 For example, the signaling transmitted through the PDSCH during the PDU session establishment process may include: the PDU session establishment response (PDU Session Establishment Accept) and AN specific resource setup in step S2082, and the relevant information of the terminal device (such as UE) and the access network device (such as gNB) establishing a resource connection in step S2083. Of course, the signaling transmitted through the PDSCH during the PDU session establishment process may also include other Figure 2 For the signaling shown, please refer to the more specific PDU session establishment process in the prior art.

[0263] In the implementation, the protocol stack receives the signaling transmitted through the PDSCH through the transceiver, the protocol stack calls the CPU, the CPU performs physical layer processing on the signaling transmitted through the PDSCH through the PDSCH processing module, and executes processing on the high-level protocol stack (processed by the MAC layer, RLC layer, PDCP layer and SDAP layer in sequence) on the processed signaling.

[0264] It should be understood that in the process of CPU processing the signaling through the PDSCH processing module, reference Figure 4b The signaling is processed in sequence through the resource block mapping module, the antenna port mapping module, the layer mapping module, the demodulation module, the descrambling module, the rate matching module, the channel decoding module, the code block merging module, and the CRC removal module.

[0265] In step S807, after the PDU session is established, the protocol stack generates slice service interface #1.

[0266] It should be noted that during the PDU session establishment process, after the terminal device receives the PDU session establishment response (PDU Session Establishment Accep) in step S2082, although there are various signaling interactions between the network sides, for the terminal device, after receiving the PDU session establishment response, it can be considered that the PDU session establishment is completed. After that, the above-mentioned business data can actually be transmitted.

[0267] It should be understood that the slice service interface #1 corresponds to S-NSSAI #1, or that the slice service interface #1 corresponds to the network slice #1 identified by S-NSSAI #1, or that the slice service interface #1 is generated based on S-NSSAI #1. It should also be understood that after the slice service interface #1 is generated, it means that the slice channel of the network slice is established, but the service data cannot be transmitted through the slice channel. It is necessary to associate the slice service interface #1 with the slice data interface #1 of the application layer (refer to the description of step S809 for details) so that the service data transmitted through the slice data interface #1 can be transmitted through the slice channel of the corresponding slice service interface #1.

[0268] In step S808, the protocol stack sends slice service interface #1 to the URSP module.

[0269] Correspondingly, the URSP module receives slice service interface #1.

[0270] In step S809, the URSP module determines the corresponding slice data interface #1 according to the slice service interface #1.

[0271] The URSP module stores the correspondence between multiple slice service interfaces and multiple slice data interfaces (recorded as correspondence #3). After the URSP module receives slice service interface #1, it determines the slice data interface #1 corresponding to slice service interface #1 according to the correspondence #3.

[0272] In the implementation, exemplarily, the routing unit of the URSP module can determine the slice data interface #1 corresponding to the slice service interface #1 according to the corresponding relationship #3. The corresponding relationship #3 can be stored in the database unit.

[0273] It should be understood that the slice data interface is an interface of the application layer.

[0274] In step S810, the URSP module sends interface information to application #1, where the interface information is used to indicate slice data interface #1.

[0275] Correspondingly, application #1 receives the interface information.

[0276] After that, application #1 starts to transmit service data, including uplink service data and downlink service data. Specifically, application #1 uses the slice data interface #1 indicated by the interface information to transmit service data.

[0277] It should be understood that uplink service data is service data transmitted through PUSCH, and downlink service data is service data transmitted through PDSCH.

[0278] In step S811, the protocol stack receives uplink service data from application layer #1, the protocol stack calls the GPU, the GPU processes the uplink service data through the target processing module, the CPU obtains the final processing result (i.e., the uplink service data after complete processing at the physical layer), and finally the CPU controls the transceiver to send the processed uplink service data.

[0279] In the implementation, after the protocol stack receives the uplink service data, the high-level protocol stack of the protocol stack processes the uplink service data (processed in sequence by the SDAP layer, PDCP layer, RLC layer and MAC layer), the GPU can be called through the high-level protocol stack or the physical layer, so that the GPU performs physical layer processing on the processed uplink service data, and the embodiment of the present application does not impose any restrictions. In addition, after the GPU (or, the GPU and the CPU) performs complete physical layer processing on the uplink service data, the CPU obtains the final processing result (i.e., the uplink service data after complete processing at the physical layer), and finally the CPU controls the transceiver to send the processed uplink service data.

[0280] Since in step S805, the protocol stack has determined the target processing module for PUSCH processed by GPU, the protocol stack can directly call the GPU for uplink service data, so that the GPU processes the uplink service data through the target processing module.

[0281] In the case where the target processing module includes all processing modules of PUSCH, the protocol stack calls the GPU, and after the GPU processes the uplink service data through the target processing module, it feeds back the final processing result (uplink service data after complete processing at the physical layer) to the CPU, so that the CPU controls the transceiver to send the processed uplink service data. In this case, the GPU performs complete physical layer processing on the uplink service data, and the GPU obtains the uplink service data after the processing at the physical layer, that is, the final processing result, and feeds back the final processing result to the CPU.

[0282] In the case where the target processing module includes a partial processing module of PUSCH, the protocol stack calls the GPU, and the GPU processes the uplink service data through the target processing module. For other processing modules in PUSCH except the target processing module, the protocol stack calls the CPU (not shown in the figure), and the CPU processes the uplink service data through the other processing modules. The CPU obtains the final processing result (uplink service data after complete processing at the physical layer), and finally the CPU controls the transceiver to send the processed uplink service data. In this case, the GPU processes part of the uplink service data at the physical layer, and the CPU processes another part of the uplink service data at the physical layer. Therefore, the uplink service data is completely processed at the physical layer by the CPU and the GPU.

[0283] If the processing flow of some processing modules of the PUSCH included in the target processing module is discontinuous, the GPU and the CPU mutually feed back the processing results of the current processing module, so that the GPU or the CPU processes the next processing module according to the fed-back processing results. For example, the target processing module processed by the GPU includes a channel coding module, a rate matching module, and an scrambling module, then the CPU processes the remaining processing modules, the CPU first processes the uplink service data through the CRC insertion module and the code block segmentation module, and feeds back the obtained processing result #1 to the GPU, the GPU continues to process the uplink service data through the channel coding module, the rate matching module, and the scrambling module according to the processing result #1, and feeds back the obtained processing result #2 to the CPU, the CPU continues to process the uplink service data through the remaining processing modules according to the processing result #2, to obtain the final processing result.

[0284] It should be understood that application #1 sends the uplink service data to the URSP module through the slice data interface #1, and the URSP module forwards the uplink service data to the protocol stack through the slice service interface #1 corresponding to the slice data interface #1, so that the protocol stack transmits the uplink service data through the slice channel of the slice service interface #1.

[0285] In step S812, the protocol stack receives downlink service data through the transceiver, and the protocol stack calls the CPU so that the CPU processes the downlink service data through the PDSCH processing module. After the protocol stack completely processes the downlink service data, the protocol stack sends the processed downlink service data to application #1 through the URSP module.

[0286] In the implementation, after the CPU completes the physical layer processing of the downlink service data through the PDSCH processing module, the processed downlink service data is processed in the high-level protocol stack (i.e., processed by the MAC layer, RLC layer, PDCP layer and SDAP layer in sequence). It can be understood that after the high-level protocol stack completes the processing of the downlink service data, it can be considered that the protocol stack has completed the complete processing of the downlink service data. After the protocol stack completes the complete processing of the downlink service data, the protocol stack sends the processed downlink service data to application #1 through the URSP module.

[0287] In addition, when the protocol stack sends the processed downlink service data to application #1 through the URSP module, the protocol stack sends the downlink service data to the URSP module through the slice service interface #1, and the URSP module forwards the downlink service data to application #1 through the slice data interface #1 corresponding to the slice service interface #1.

[0288] For a specific description of the process in which the CPU processes downlink service data through the PDSCH processing module, reference may be made to the above description of the process in which the CPU processes signaling through the PDSCH processing module, which will not be repeated here.

[0289] It should be understood that the order of step S811 and step S812 is not based on the size of the label, and the order of transmission of uplink service data and downlink service data is based on the specific service. For example, step S811 may also be after step S812.

[0290] In the above embodiment, the terminal device determines the network slice #1 corresponding to the service identifier #1 according to the service identifier #1, and determines the target processing module of the PUSCH processed by the GPU according to the network slice #1. In this way, the GPU can be used to perform physical layer processing on the data (service data and signaling) transmitted through the PUSCH through the target processing module. Compared with using the CPU to process the data at the physical layer, using the GPU to process the data at the physical layer can significantly improve the processing speed and improve the real-time performance of the scenario of the network slice #1 corresponding to the service identifier #1.

[0291] Fig. 9 It is an exemplary flow chart of a method 900 based on network slicing communication provided in an embodiment of the present application. In method 900, the terminal device determines the target processing module for processing PDSCH using GPU based on S-NSSAI for identifying the network slice, and the GPU processes the data (service data and signaling) through the target processing module to achieve physical layer acceleration, improve the processing speed, and meet the real-time requirements of the current network slicing scenario.

[0292] It should be understood that in method 900, for data (service data and signaling) transmitted via PUSCH, the CPU is used to perform physical layer processing on the data in a manner according to the prior art.

[0293] For the detailed description of step S901 and step S904, please refer to the relevant description of step S801 and step S804 in method 800, which will not be repeated here. The only difference is that the service identifier #1 and S-NSSAI #1 in method 900 are not exactly the same as the application #1, service identifier #1 and S-NSSAI #1 in method 800.

[0294] It can be understood that the service #1 identified by the service identifier #1 of method 900 and the network slice #1 identified by S-NSSAI #1 are suitable for scenarios with high real-time requirements for PDSCH. For example, application #1 can be a video application (e.g., applications that can watch long videos) or audio applications (for example, ), service #1 is a video service or an audio service, the service identifier #1 used to identify service #1 is used to identify the video service or the audio service, and the corresponding network slice #1 is applicable to the video service or the audio service.

[0295] In step S905, the protocol stack determines the target processing module of the PDSCH to be processed by the GPU according to S-NSSAI#1.

[0296] After receiving S-NSSAI#1, the protocol stack determines that the GPU needs to be used to process PDSCH according to S-NSSAI#1, and determines the target processing module to be processed by the GPU from the multiple processing modules of PDSCH, so that the GPU processes the data (service data and signaling) transmitted through PDSCH to improve the processing speed. It should be understood that the multiple processing modules of PDSCH are all processing modules of PDSCH. For terminal devices, refer to Figure 4b The processing module shown.

[0297] The target processing module unit of PDSCH includes at least one processing module, which may be a part of the multiple processing modules of PDSCH, or all the processing modules among the multiple processing modules, and is specifically related to the network slice #1 identified by S-NSSAI #1.

[0298] For example, if service #1 corresponding to network slice #1 is a high-definition live video service, the target processing module determined based on S-NSSAI #1 used to identify network slice #1 may be all processing modules of PDSCH. For another example, if service #1 corresponding to network slice #1 is a non-high-definition live video service, the target processing module determined based on S-NSSAI #1 used to identify network slice #1 may be a partial processing module of PDSCH.

[0299] In the implementation, the protocol stack matches S-NSSAI#1 with the above correspondence #2 (uplink correspondence and downlink correspondence), and finally matches a group of processing modules corresponding to S-NSSAI#1 from the downlink correspondence. This group of processing modules is the target processing module of PDSCH processed by GPU corresponding to S-NSSAI#1. For the specific description of the uplink correspondence, please refer to the above description of Table 2, which will not be repeated.

[0300] In step S906, the protocol stack initiates a PDU session according to S-NSSAI#1 and performs a PDU session establishment process.

[0301] For a detailed description of this step, please refer to the relevant description of step S806 in method 800, which will not be repeated here.

[0302] During the PDU session establishment process, for signaling transmitted through PUSCH, the CPU can be used to process the signaling through the PUSCH processing module. For signaling transmitted through PDSCH, the GPU can be used to process the signaling through the target processing module. The following is a specific description of the process of processing signaling transmitted through PUSCH and PDSCH through steps S9061 and S9062.

[0303] In step S9061, the protocol stack calls the CPU, so that the CPU processes the signaling transmitted through the PUSCH through the PUSCH processing module.

[0304] Regarding the signaling transmitted through PUSCH during the PDU session establishment process, please refer to the relevant description of step S8061 above and will not be repeated here.

[0305] In the implementation, exemplarily, for the signaling transmitted through PUSCH, after being processed by the high-level protocol stack of the protocol stack (that is, after being processed by the SDAP layer, PDCP layer, RLC layer and MAC layer in sequence), the CPU can be called through the high-level protocol stack or the physical layer, and the CPU processes the signaling transmitted through PUSCH through the PUSCH processing module, and finally the CPU controls the transceiver to send the processed signaling.

[0306] In step S9062, the protocol stack calls the GPU, and the GPU processes the signaling transmitted through the PDSCH during the PDU session establishment process through the target processing module.

[0307] Regarding the signaling transmitted through PDSCH during the PDU session establishment process, please refer to the relevant description of step S8062 above and will not be repeated here.

[0308] In the implementation, the protocol stack receives the signaling transmitted through the PDSCH through the transceiver, and the protocol stack calls the GPU through the high-level protocol stack or the physical layer, so that the GPU performs physical layer processing on the signaling transmitted through the PDSCH through the target processing module of the PDSCH, and no limitation is made here. In addition, after the GPU (or, the GPU and the CPU) performs complete physical layer processing on the signaling, the CPU obtains the final processing result (that is, the signaling after complete physical layer processing), so that the CPU performs processing on the processed signaling in the high-level protocol stack based on the final processing result (that is, processing through the MAC layer, the RLC layer, the PDCP layer, and the SDAP layer in sequence).

[0309] In the case where the target processing module includes all processing modules of PDSCH, the protocol stack calls the GPU, and after the GPU processes the signaling transmitted through the PDSCH through the target processing module, it feeds back the final processing result (i.e., the signaling after complete processing at the physical layer) to the CPU, so that the CPU performs processing on the processed signaling in the high-level protocol stack based on the final processing result. In this case, the GPU performs complete physical layer processing on the signaling, and the GPU obtains the signaling after complete physical layer processing, i.e., the final processing result, and feeds back the final processing result to the CPU.

[0310] In the case where the target processing module includes a partial processing module of PDSCH, the protocol stack calls the GPU, the GPU processes the signaling through the target processing module, the CPU processes the signaling through other processing modules in PDSCH except the target processing module, the CPU obtains the final processing result (the signaling after complete processing at the physical layer), and finally the CPU performs processing on the processed signaling in the high-level protocol stack based on the final processing result. In this case, the GPU processes part of the signaling at the physical layer, and the CPU processes another part of the signaling at the physical layer. Therefore, the signaling is completely processed at the physical layer by the CPU and the GPU together.

[0311] If the processing flow of some processing modules of the PDSCH included in the target processing module is discontinuous, for example, the previous processing module is processed by the GPU, the next processing module is processed by the CPU, and the next processing module is processed by the GPU, the GPU and the CPU mutually feedback the processing result of the current processing module, so that the GPU or the CPU processes the next processing module according to the feedback processing result. For example, the target processing module processed by the GPU includes a channel decoding module, a rate matching module and a descrambling module, then the CPU processes the remaining processing modules, and the CPU processes the signaling through the resource mapping module, the antenna port module, the layer mapping module and the demodulation module in sequence, and feeds back the obtained processing result #1 to the GPU, and the GPU continues to process the signaling through the descrambling module, the rate matching module and the channel decoding module in sequence according to the processing result #1, and feeds back the obtained processing result #2 to the CPU, and the CPU continues to process the signaling through the code block merging module and the CRC removal module in sequence according to the processing result #2 to obtain the final processing result.

[0312] As described above, in the implementation, exemplarily, the GPU is configured with interfaces of various processing modules for PUSCH and PDSCH. After the protocol stack determines the target processing module for PDSCH, the interface of each processing module in the target processing module is called to enable the GPU to run. In this way, the GPU is called by calling the interfaces of various processing modules configured in the GPU, and the signaling transmitted through the PDSCH is processed by the target processing module.

[0313] After the PDU session is established, steps S907 to S910 are executed. For the specific description of steps S907 to S910, reference may be made to the relevant description of steps S807 to S810 of method 800, which will not be repeated here.

[0314] In step S911, the protocol stack receives uplink service data from application layer #1, and the protocol stack calls the CPU so that the CPU processes the uplink service data through the PUSCH processing module, and the CPU controls the transceiver to send the processed uplink service data.

[0315] In the implementation, after the protocol stack receives the uplink service data, the CPU processes the uplink service data at the higher layer of the protocol stack (processed by the SDAP layer, PDCP layer, RLC layer and MAC layer in sequence), and then processes the uplink service data at the physical layer through the PUSCH processing module. In addition, after completing the physical layer processing of the uplink service data, the CPU finally controls the transceiver to send the processed uplink service data.

[0316] As mentioned above, application #1 sends the uplink service data to the URSP module through the slice data interface #1, and the URSP module forwards the uplink service data to the protocol stack through the slice service interface #1 corresponding to the slice data interface #1. Thus, the protocol stack transmits the uplink service data through the slice channel of the slice service interface #1.

[0317] In step S912, the protocol stack receives downlink service data through the transceiver, the protocol stack calls the GPU, and the GPU processes the downlink service data through the target processing module of PDSCH. After the protocol stack completes the complete processing of the downlink service data, the protocol stack sends the processed downlink service data to application #1 through the URSP module.

[0318] In the implementation, after receiving the downlink service data, the protocol stack can call the GPU through the high-level protocol stack or the physical layer, so that the GPU performs physical layer processing on the downlink service data through the target processing module of the PDSCH, and no limitation is made here. After the GPU (or, the GPU and the CPU) performs complete physical layer processing on the downlink service data, the CPU obtains the final processing result (i.e., the downlink service data after complete processing at the physical layer), and performs processing on the processed downlink service data in the high-level protocol stack (i.e., processing through the MAC layer, RLC layer, PDCP layer and SDAP layer in sequence). It can be understood that after the high-level protocol stack has processed the downlink service data, it can be considered that the protocol stack has completed the complete processing of the downlink service data. After the protocol stack completes the complete processing of the downlink service data, the protocol stack sends the processed downlink service data to application #1 through the URSP module.

[0319] In addition, when the protocol stack sends the processed downlink service data to application #1 through the URSP module, the protocol stack sends the downlink service data to the URSP module through the slice service interface #1, and the URSP module forwards the downlink service data to application #1 through the slice data interface #1 corresponding to the slice service interface #1.

[0320] Since in step S905, the protocol stack has determined the target processing module of the PDSCH to be processed by the GPU, the protocol stack can directly call the GPU for the downlink service data, so that the GPU processes the downlink service data through the target processing module.

[0321] In the case where the target processing module includes all processing modules of PDSCH, the protocol stack calls the GPU, and after the GPU processes the downlink service data through the target processing module, it feeds back the final processing result (i.e., the downlink service data after complete processing at the physical layer) to the CPU, so that the CPU performs processing on the processed downlink service data in the high-level protocol stack based on the final processing result. In this case, the GPU performs complete processing of the downlink service data at the physical layer, and the GPU obtains the downlink service data after complete processing at the physical layer, i.e., the final processing result, and feeds back the final processing result to the CPU.

[0322] In the case where the target processing module includes a partial processing module of PDSCH, the protocol stack calls the GPU, and the GPU processes the downlink service data through the target processing module. For other processing modules in PDSCH except the target processing module, the protocol stack calls the CPU, and the CPU processes the downlink service data through other processing modules. The CPU obtains the final processing result (downlink service data after complete processing at the physical layer), and finally the CPU performs processing on the processed downlink service data set in the high-level protocol stack based on the final processing result. In this case, the GPU processes part of the downlink service data at the physical layer, and the CPU processes another part of the downlink service data at the physical layer. Therefore, the downlink service data is completely processed at the physical layer by the CPU and the GPU.

[0323] If the processing flow of some processing modules of the PDSCH included in the target processing module is discontinuous, for example, the previous processing module is processed by the GPU, the next processing module is processed by the CPU, and the next processing module is processed by the GPU, the GPU and the CPU mutually feedback the processing result of the current processing module, so that the GPU or the CPU processes the next processing module according to the feedback processing result. For example, the target processing module processed by the GPU includes a channel decoding module, a rate matching module and a descrambling module, then the CPU processes the remaining processing modules, and the CPU processes the downlink service data through the resource mapping module, the antenna port module, the layer mapping module and the demodulation module in sequence, and feeds back the obtained processing result #1 to the GPU, and the GPU continues to process the downlink service data through the descrambling module, the rate matching module and the channel decoding module in sequence according to the processing result #1, and feeds back the obtained processing result #2 to the CPU, and the CPU continues to process the downlink service data through the code block merging module and the CRC removal module in sequence according to the processing result #2 to obtain the final processing result.

[0324] It should be understood that the order of step S911 and step S912 is not indicated by the size of the numbers, and the order of transmission of uplink service data and downlink service data depends on the specific services. For example, step S911 may also be after step S912.

[0325] In the above embodiment, the terminal device determines the network slice #1 corresponding to the service identifier #1 according to the service identifier #1, and determines the target processing module of the PDSCH processed by the GPU according to the network slice #1. In this way, the GPU can be used to perform physical layer processing on the data (service data and signaling) transmitted through the PDSCH through the target processing module. Compared with using the CPU to process the data at the physical layer, using the GPU to process the data at the physical layer can significantly improve the processing speed and improve the real-time performance of the scenario of the network slice #1 corresponding to the service identifier #1.

[0326] Fig.10 It is an exemplary flow chart of a method 1000 based on network slicing communication provided in an embodiment of the present application. In method 1000, the terminal device determines the target processing module of PUSCH and the target processing module of PDSCH processed by GPU based on S-NSSAI used to identify the network slice. The GPU processes uplink data (service data and signaling) and downlink data through the target processing module of PUSCH and the target processing module of PDSCH respectively to achieve physical layer acceleration, improve processing speed, and meet the real-time requirements of the current network slicing scenario.

[0327] For the detailed description of step S1001 and step S1004, please refer to the relevant description of step S801 and step S804 in method 800, which will not be repeated here. The only difference is that the service identifier #1 and S-NSSAI #1 in method 1000 are not exactly the same as the application #1, service identifier #1 and S-NSSAI #1 in method 800.

[0328] It can be understood that the service #1 identified by the service identifier #1 of method 1000 and the network slice #1 identified by S-NSSAI #1 are applicable to scenarios with high real-time requirements for PDSCH and PUSCH. For example, application #1 may be a cloud gaming application, service #1 is a gaming service, the service identifier #1 used to identify service #1 is used to identify the gaming service, and the corresponding network slice #1 is applicable to the gaming service.

[0329] In step S1005, the protocol stack determines the target processing module #1 for PUSCH and the target processing module #2 for PDSCH to be processed by GPU according to S-NSSAI #1.

[0330] In step S1006, the protocol stack initiates a PDU session according to S-NSSAI#1 and performs a PDU session establishment process. During the PDU session establishment process, the protocol stack calls the GPU, and the GPU processes the signaling transmitted through the PUSCH and PDSCH during the PDU session establishment process through the target processing module #1 and the target processing module #2, respectively.

[0331] In this step, the GPU processes the signaling transmitted through the PUSCH during the PDU session establishment process through the target processing module #1, and processes the signaling transmitted through the PDSCH during the PDU session establishment process through the target processing module #2.

[0332] Regarding the specific description of the process in which the protocol stack calls the GPU and the GPU processes the signaling transmitted through the PUSCH during the PDU session establishment process through the target processing module #1, please refer to the relevant description of step S8061, which will not be repeated here. Regarding the specific description of the process in which the protocol stack calls the GPU and the GPU processes the signaling transmitted through the PDSCH during the PDU session establishment process through the target processing module #2, please refer to the relevant description of step S9062, which will not be repeated here.

[0333] After the PDU session is established, steps S1007 to S1010 are executed. For the specific description of steps S1007 to S1010, please refer to the relevant description of steps S807 to S810 of method 800, which will not be repeated here.

[0334] In step S1011, the protocol stack receives uplink service data from application layer #1, the protocol stack calls the GPU, the GPU processes the uplink service data through the target processing module #1, the CPU obtains the final processing result (i.e., the uplink service data after complete processing at the physical layer), and finally the CPU controls the transceiver to send the processed uplink service data.

[0335] Since in step S1005, the protocol stack has determined the target processing module #1 for PUSCH to be processed by the GPU, the protocol stack can directly call the GPU for uplink service data, so that the GPU processes the uplink service data through the target processing module #1.

[0336] For the specific description of this step, please refer to the relevant description of step S811, which will not be repeated here.

[0337] In step S1012, the protocol stack receives downlink service data through the transceiver, the protocol stack calls the GPU, and the GPU processes the downlink service data through the target processing module #2 of the PDSCH. After the protocol stack completes the complete processing of the downlink service data, the protocol stack sends the processed downlink service data to application #1 through the URSP module.

[0338] Since in step S1005, the protocol stack has determined the target processing module #2 for PDSCH to be processed by the GPU, the protocol stack can directly call the GPU for downlink service data, so that the GPU processes the downlink service data through the target processing module #2.

[0339] For the specific description of this step, please refer to the relevant description of step S912, which will not be repeated here.

[0340] It should be understood that the order of step S1011 and step S1012 is not indicated by the size of the numbers, and the order of transmission of uplink service data and downlink service data depends on the specific services. For example, step S1011 may also be after step S1012.

[0341] In the above embodiment, the terminal device determines the network slice #1 corresponding to the service identifier #1 according to the service identifier #1, and determines the target processing module #1 for PUSCH and the target processing module #2 for PDSCH processed by the GPU according to the network slice #1. In this way, the GPU can be used to perform physical layer processing on the data (service data and signaling) transmitted through the PUSCH through the target processing module #1, and the GPU can be used to perform physical layer processing on the data (service data and signaling) transmitted through the PDSCH through the target processing module #2. Compared with using the CPU to process the data at the physical layer, using the GPU to process the data at the physical layer can significantly increase the processing speed and improve the real-time performance of the scenario of the network slice #1 corresponding to the service identifier #1.

[0342] exist Figures 8 to 10 In an embodiment, the terminal device determines a target processing module for PUSCH and / or PDSCH to be processed by a coprocessor such as a GPU according to the network slice, and uses the coprocessor to perform physical layer processing on the data through the target processing module. Compared with using the CPU to process the data at the physical layer, using the coprocessor to process the data can significantly improve the processing speed and improve the real-time performance. In addition, the target processing module for PUSCH and / or PDSCH is determined according to the network slice, and different target processing modules to be processed by the coprocessor can be determined according to different network slices. This can prevent the indifferent scheduling of the computing resources of the coprocessor in different network slicing scenarios to cause waste of resources and power consumption, while matching the real-time requirements of different application scenarios and improving the flexibility of the processing process.

[0343] In other massive IoT scenarios such as data collection from IoT devices (e.g., smart meters and various sensors), the terminal device can also determine based on network slicing that it does not need to use a coprocessor to perform any physical layer processing on the data, and use the CPU to process the data at the physical layer. In this way, resources and power consumption can be saved to the maximum extent based on the needs of the network slicing scenario.

[0344] The following, combined Fig.11 A brief description is given of the process by which the terminal device determines that it is not necessary to use a coprocessor to perform physical layer processing on data. Similarly, a GPU is used as an example of a coprocessor for description.

[0345] Fig.11It is an exemplary flowchart of the method 1100 based on network slicing communication provided in an embodiment of the present application.

[0346] For the detailed description of step S1101 and step S1104, please refer to the relevant description of step S801 and step S804 in method 800, which will not be repeated here. The only difference is that the service identifier #1 and S-NSSAI #1 in method 1000 are not exactly the same as the application #1, service identifier #1 and S-NSSAI #1 in method 800.

[0347] It can be understood that the service #1 identified by the service identifier #1 of method 1100 and the network slice #1 identified by S-NSSAI #1 are applicable to scenarios where the real-time requirements for PDSCH and PUSCH are not too high. For example, application #1 can be an application such as a smart meter, service #1 is a data collection service, and the service identifier #1 used to identify service #1 is used to identify the data collection service, and the corresponding network slice #1 is applicable to the data collection service. Taking the data collection of smart meters as an example, the data collection service not only does not have high requirements on the real-time performance of the service, but also has low power consumption.

[0348] In step S1105, the protocol stack determines, based on S-NSSAI#1, not to use the GPU to perform physical layer processing on the data.

[0349] Since the network slice #1 identified by S-NSSAI#1 does not have high real-time performance for data, there is no need to use GPU to process the data at the physical layer to prevent waste of GPU resources and power consumption. Therefore, it is determined not to use GPU to process the data at the physical layer.

[0350] In the implementation, exemplarily, the protocol stack matches S-NSSAI#1 with the above correspondence #2 (uplink correspondence and downlink correspondence). If a group of processing modules corresponding to S-NSSAI#1 is not matched in the correspondence, it is determined that the GPU will not be used to perform physical layer processing on the data.

[0351] In step S1106, the protocol stack initiates a PDU session according to S-NSSAI#1 and performs a PDU session establishment process. During the PDU session establishment process, the protocol stack calls the CPU so that the CPU processes the signaling transmitted during the PDU session establishment process through the PUSCH and PDSCH processing modules.

[0352] It should be understood that the signaling transmitted during the PDU session establishment process represents the signaling transmitted between the terminal device and the access network device through PUSCH and PDSCH. For specific descriptions, please refer to the relevant descriptions above and will not be repeated here.

[0353] It should also be understood that the CPU processes the signaling transmitted through the PUSCH during the PDU session establishment process through the PUSCH processing module, and the CPU processes the signaling transmitted through the PDSCH during the PDU session establishment process through the PDSCH processing module.

[0354] After the PDU session is established, steps S1107 to S1110 are executed. For the specific description of steps S1107 to S1110, please refer to the relevant description of steps S807 to S810 of method 800, which will not be repeated here.

[0355] After step S1110, the terminal device starts transmitting service data.

[0356] In step S1111, the protocol stack receives uplink service data from application layer #1, and the protocol stack calls the CPU so that the CPU processes the uplink service data through the PUSCH processing module, and the CPU controls the transceiver to send the processed uplink service data.

[0357] For the specific description of this step, please refer to the relevant description of step S911 and will not be repeated here.

[0358] In step S1112, the protocol stack receives downlink service data through the transceiver, and the protocol stack calls the CPU so that the CPU processes the downlink service data through the PDSCH processing module. After the protocol stack completely processes the downlink service data, the protocol stack sends the processed downlink service data to application #1 through the URSP module.

[0359] For the specific description of this step, please refer to the relevant description of step S812 and will not be repeated here.

[0360] In this embodiment, the terminal device determines the network slice #1 corresponding to the service identifier #1 based on the service identifier #1, and determines that the GPU does not need to be used to perform any physical layer processing on the data based on the network slice #1. In this way, only the CPU needs to be used to process the data at the physical layer, which can maximize resource savings and power consumption based on the requirements of the network slicing scenario.

[0361] Fig.12 1 is an exemplary flow chart of a method 1200 based on network slicing communication provided by an embodiment of the present application. Method 1200 only describes an embodiment in which a terminal device determines to process data through a coprocessor. For embodiments in which a coprocessor is not required to process data, reference can be made to the relevant description of method 1100, which will not be repeated. In addition, the terminal device is taken as an example as the execution subject of method 1200 to illustrate method 1200.

[0362] In step S1210, the terminal device generates a first service identifier in response to a user operation, where the first service identifier is used to identify a first service to be currently executed.

[0363] In this step, the user performs an operation on the terminal device, the terminal device detects the user operation, and generates a first service identifier based on a first service related to the user operation.

[0364] Exemplarily, a user may input user operations through an application module. The application module may be a client application or a browser application, without any limitation. For specific examples of the application module, please refer to the example descriptions of application #1 in the above methods. Application #1 above may correspond to the application module here.

[0365] Exemplarily, the first service may be any service, for example, the first service may be various types of services such as a live broadcast service, a data backhaul service, a real-time monitoring service, a video service, an audio service, and a cloud gaming service.

[0366] Exemplarily, the first service identifier may be represented by at least one of APP ID, IP triplet information, FQDN, and DNN. For a specific description, please refer to the description of service identifier #1 (corresponding to the first service identifier here) in step S802, which will not be repeated here.

[0367] It should be understood that the first service and the first service identifier exemplified above are merely illustrative and should not limit the embodiments of the present application.

[0368] In step S1220, the terminal device determines a first S-NSSAI corresponding to the first service identifier based on the first service identifier, and the first S-NSSAI is used to indicate a first network slice corresponding to the first service.

[0369] In this step, in some embodiments, the terminal device determines the first S-NSSAI based on the first service identifier from a second correspondence relationship indicating multiple service identifiers and multiple S-NSSAIs, wherein at least one service identifier corresponds to one S-NSSAI, one S-NSSAI is used to uniquely identify a network slice, and one service identifier is used to uniquely identify a service.

[0370] Exemplarily, the second corresponding relationship may be obtained from a network, or may be obtained from a general platform of the terminal device itself, and no limitation is made to this.

[0371] Due to the diversity of service transmission and network changes, in an embodiment where the second correspondence is obtained from the network, the terminal device may periodically obtain the second correspondence from the network to obtain an updated second correspondence as much as possible, thereby obtaining an S-NSSAI that accurately matches the current service.

[0372] In other embodiments, the terminal device may also determine the first S-NSSAI corresponding to the first service identifier in other ways, and the embodiments of the present application do not impose any limitation thereto.

[0373] In step S1230, the terminal device determines, based on the first S-NSSAI, a target processing module for a data channel processed by a coprocessor, where the target processing module includes at least some of all processing modules of the data channel.

[0374] It should be understood that at least part of the processing modules herein include all processing modules or part of the processing modules of all processing modules. The target processing module includes one or more processing modules of the data channel.

[0375] When the target processing module includes some of the processing modules among all the processing modules, it means that the real-time requirements can be met by using some of the processing modules to process the data, and there is no need to waste extra resources and power consumption to use the coprocessor to process the data through the remaining processing modules except some of the processing modules. When the target processing module includes all the processing modules, it means that the first network slicing scenario of the first S-NSSAI has a high real-time requirement, so the coprocessor is used to process the data through all the processing modules.

[0376] As mentioned above, a coprocessor is a processor developed and applied to assist the central processing unit to complete processing tasks that it cannot perform or performs inefficiently or ineffectively. For example, the coprocessor can be any of the following processors: GPU, ISP, DSP, NPU, FPGA. It should be understood that the types of coprocessors exemplified here are only for illustrative purposes, and any processor that can assist the CPU to complete some processing tasks that require high execution efficiency and execution effect can be used as an example of a coprocessor.

[0377] In this step, according to the first S-NSSAI, the target processing module corresponding to the first S-NSSAI is determined. When data processing is performed subsequently, a coprocessor can be used to process the data through the target processing module. In this way, the speed of data processing can be improved to meet the real-time performance of the first network slice corresponding to the first S-NSSAI.

[0378] The processing modules of the data channel are processing modules of the physical layer, and each processing module is used to execute a step of the physical layer.

[0379] As mentioned above, the data channel includes PUSCH and PDSCH, and the target processing module corresponding to the first S-NSSAI may include a PUSCH processing module, a PDSCH processing module, or a PUSCH and PDSCH processing module. The following describes each case.

[0380] Case 1

[0381] The target processing module includes a first target processing module, and the first target processing module is a PUSCH processing module.

[0382] Among them, all processing modules of PUSCH can refer to the following Figure 5a Each module shown in the figure processes the data according to Figure 5a The first target processing module is a part or all of the processing modules of the PUSCH.

[0383] It can be understood that in this case 1, the first service (or the first network slice) is a scenario with high real-time requirements for uplink transmission, and a large amount of uplink data needs to be transmitted to the network. Exemplarily, the first service can be a type of service such as a live broadcast service, a data backhaul service, a real-time monitoring service, etc.

[0384] In the case where the first target processing module is a part of all processing modules of PUSCH, exemplarily, the first service may be, for example, a non-HD live broadcast service, a non-HD data backhaul service, or a non-HD real-time monitoring service.

[0385] In the case where the first target processing module is all processing modules of PUSCH, illustratively, the first service may be a service such as a high-definition live broadcast service, a high-definition data backhaul service, or a high-definition real-time monitoring service.

[0386] Case 2

[0387] The target processing module includes a second target processing module, and the second target processing module is a PDSCH processing module.

[0388] Among them, all processing modules of PDSCH can refer to Figure 4b Each module shown in the figure processes the data according to Figure 4b The second target processing module is a part or all of the processing modules in all the processing modules of the PDSCH.

[0389] It can be understood that in this situation 2, the first service (or the first network slice) is a scenario with high real-time requirements for downlink transmission, and a large amount of downlink data needs to be transmitted to the terminal device. Exemplarily, the first service can be a service such as a video service, an audio service, etc.

[0390] In the case where the second target processing module is a part of all processing modules of the PDSCH, illustratively, the first service may be a non-HD video service, a non-super quality (SQ) audio service, or the like.

[0391] In the case where the second target processing module is all processing modules of the PDSCH, illustratively, the first service may be a service such as a high-definition video service, an SQ audio service, or the like.

[0392] Case 3

[0393] The target processing module includes a first target processing module and a second target processing module. The first target processing module is a PUSCH processing module, and the second target processing module is a PDSCH processing module.

[0394] It can be understood that in this situation 3, the first service (or the first network slice) is a scenario that requires high real-time performance of both uplink and downlink transmissions, and requires transmitting a large amount of uplink data to the network and downloading a large amount of downlink data to the terminal device. Exemplarily, the first service can be a service such as a cloud gaming service.

[0395] It should be noted that, when the first target processing module includes all processing modules of PUSCH and the second target processing module includes all processing modules of PDSCH, it is considered that the target processing module includes all processing modules of data channels.

[0396] In step S1240, the terminal device uses a coprocessor to process first data related to the first service through a target processing module.

[0397] The following describes the first data and the processing of the first data in combination with the three situations in step 1230 .

[0398] Combined with situation 1

[0399] In case 1 where the target processing module includes the first target processing module, the first data includes signaling or uplink service data transmitted via PUSCH. The signaling transmitted via PUSCH may be signaling of a PDU session establishment process, and the specific description may refer to the above related description, which will not be repeated here.

[0400] In the case that the first target processing module includes all processing modules of the PUSCH, the coprocessor is used to perform all physical layer processing on the first data through the target processing module.

[0401] In the case where the first target processing module includes a part of the processing modules of the PUSCH, the first data is processed not only by the coprocessor but also by the CPU. That is, the first data is processed by the coprocessor through the first target processing module, and the first data is processed by the CPU through other processing modules among all the processing modules of the PUSCH except the first target processing module, so as to perform complete physical layer processing on the first data.

[0402] If the processing flow of the PUSCH part processing module included in the first target processing module is discontinuous, for example, the previous processing module is processed by the coprocessor, the next processing module is processed by the CPU, and the next processing module is processed by the coprocessor, then the coprocessor and the CPU mutually feedback the processing result of the current processing module, so that the coprocessor or the CPU performs the processing of the next processing module according to the feedback processing result, so as to finally complete the complete processing of the first data at the physical layer. For the specific description here, please refer to the relevant description of step S8061, which will not be repeated.

[0403] It should be understood that after performing complete physical layer processing on the first data transmitted via the PUSCH, the terminal device can send the processed first data through the transceiver.

[0404] Combined with situation 2

[0405] In case 2 where the target processing module includes the second target processing module, the first data includes signaling or downlink service data transmitted via PDSCH. The signaling transmitted via PDSCH may be signaling of a PDU session establishment process, and the specific description may refer to the above related description, which will not be repeated here.

[0406] In the case that the second target processing module includes all processing modules of the PDSCH, the coprocessor is used to perform all physical layer processing on the first data through the second target processing module.

[0407] In the case where the second target processing module includes a part of the processing modules of the PDSCH, the first data is processed not only by the coprocessor but also by the CPU, that is, the first data is processed by the coprocessor through the second target processing module, and the first data is processed by the CPU through other processing modules among all the processing modules of the PDSCH except the second target processing module, so as to perform complete physical layer processing on the first data.

[0408] If the processing flow of the partial processing modules of the PDSCH included in the second target processing module is discontinuous, for example, the previous processing module is processed by the coprocessor, the next processing module is processed by the CPU, and the next processing module is processed by the coprocessor, then the coprocessor and the CPU mutually feedback the processing result of the current processing module, so that the coprocessor or the CPU performs the processing of the next processing module according to the feedback processing result, so as to finally complete the complete processing of the first data at the physical layer. For the specific description here, please refer to the relevant description of step S9061, which will not be repeated.

[0409] It should be understood that after complete physical layer processing of the first data transmitted via the PDSCH, the terminal device performs high-level protocol stack processing on the processed first data (i.e., processing through the MAC layer, RLC layer, PDCP layer and SDAP layer in sequence) to obtain the final processed first data.

[0410] Combined with situation 3

[0411] In case 3 where the target processing module includes the first target processing module and the second target processing module, the first data includes signaling or downlink service data transmitted via PUSCH, and the first data includes signaling or downlink service data transmitted via PDSCH. The signaling transmitted via PDSCH or PUSCH may be signaling of a PDU session establishment process, and the specific description may refer to the above related description, which will not be repeated here.

[0412] It should be understood that in situation 3, the coprocessor is used to process the signaling or uplink service data transmitted via PUSCH through the first target processing module, and the coprocessor is used to process the signaling or downlink service data transmitted via PDSCH through the second target processing module.

[0413] In the case where the first target processing module includes all processing modules of the PUSCH, the coprocessor is used to perform all physical layer processing on the first data through the first target processing module. In the case where the first target processing module includes some processing modules of the PUSCH, not only the coprocessor is used to process the first data, but the CPU is used to process the first data. For a specific description, please refer to the relevant description of step S8061, which will not be repeated here.

[0414] In the case where the second target processing module includes all processing modules of the PDSCH, the coprocessor is used to perform all physical layer processing on the first data through the second target processing module. In the case where the second target processing module includes some processing modules of the PDSCH, not only the coprocessor is used to process the first data, but the CPU is used to process the first data. For a specific description, please refer to the relevant description of step S9061, which will not be repeated here.

[0415] In the method based on network slicing communication provided in the embodiment of the present application, the terminal device determines the first S-NSSAI for indicating the first network slice based on the first service identifier, and determines the target processing module of the data channel processed by the coprocessor according to the first S-NSSAI, so that the coprocessor is used to process the data at the physical layer through the target processing module. Compared with the physical layer processing of the data by the CPU, the coprocessor is used to process the data, which can significantly improve the processing speed and improve the real-time performance; in addition, the target processing module of the data channel is determined according to the first S-NSSAI, and different target processing modules can be determined according to the S-NSSAI of different network slices, which can prevent the indifferent scheduling of the computing resources of the coprocessor in different network slicing scenarios to cause waste of resources and power consumption, and can match the real-time requirements of different application scenarios, and can also improve the flexibility of the processing process. Therefore, the embodiment of the present application generally realizes adaptive acceleration based on network slicing without causing waste of resources and power consumption, and meets the real-time requirements of different application scenarios.

[0416] Regarding the terminal device determining the target processing module in step S1230, in some embodiments, the process may be as follows:

[0417] The terminal device determines, based on the first S-NSSAI, a target processing module corresponding to the first S-NSSAI from a first correspondence relationship indicating multiple S-NSSAIs and multiple groups of processing modules, where each S-NSSAI corresponds to at least one group of processing modules.

[0418] It should be understood that the target processing module corresponding to the first S-NSSAI is at least one group of processing modules in the multiple groups of processing modules. After the terminal device determines at least one group of processing modules corresponding to the first S-NSSAI from the first corresponding relationship, it determines the at least one group of processing modules as the target processing module.

[0419] The above-mentioned first corresponding relationship may be acquired by the terminal device from the network, or may be pre-stored in the terminal device, and no limitation is made here.

[0420] In this way, by indicating the first correspondence between multiple S-NSSAIs and multiple groups of processing modules, the target processing module corresponding to the first S-NSSAI is determined, which can simplify the design and facilitate implementation.

[0421] In some embodiments, the first correspondence includes an uplink correspondence and a downlink correspondence. The uplink correspondence is used to indicate a one-to-one correspondence between M S-NSSAIs and M groups of processing modules, and the downlink correspondence is used to indicate a one-to-one correspondence between N S-NSSAIs and N groups of processing modules. Both M and N are integers greater than or equal to 1.

[0422] Here, M and N may be the same or different, without limitation, and shall be subject to the specific implementation.

[0423] In this embodiment, the terminal device may match the first S-NSSAI with the uplink correspondence and the downlink correspondence respectively, so as to finally determine the target processing module corresponding to the first S-NSSAI.

[0424] Since the same S-NSSAI exists in the uplink correspondence relationship and the downlink correspondence relationship, one S-NSSAI may correspond to one group of processing modules or two groups of processing modules.

[0425] In an embodiment where an S-NSSAI corresponds to two groups of processing modules, one group of processing modules of the two groups of processing modules is a processing module for PUSCH, and the other group of processing modules is a processing module for PDSCH. For example, referring to Tables 1 and 2 above, S-NSSAI#A may correspond to a group of processing modules for PUSCH (including a channel coding module, a rate matching module, and an scrambling module), and may also correspond to a group of processing modules for PDSCH (including a channel decoding module and a rate matching module). Therefore, S-NSSAI#A corresponds to two groups of processing modules.

[0426] In an embodiment where an S-NSSAI corresponds to a group of processing modules, the group of processing modules is a PUSCH processing module or a PDSCH processing module. For example, referring to Table 1 and Table 2 above, S-NSSAI#B corresponds only to a PUSCH processing module (including a channel coding module).

[0427] It should be understood that in this embodiment, since the first correspondence includes an upstream correspondence and a downstream correspondence, the determined target processing module can be any one of the three cases mentioned above, that is, the target processing module includes a first target processing module, the target processing module includes a second target processing module, and the target processing module includes a first target processing module and a second target processing module.

[0428] In other embodiments, the first corresponding relationship only includes the above-mentioned upstream corresponding relationship.

[0429] In this embodiment, the terminal device may match the first S-NSSAI with the uplink correspondence to determine the target processing module. It can be understood that in this embodiment, the device only allows accelerated processing of data transmitted via the PUSCH.

[0430] It should be understood that in this embodiment, since the first corresponding relationship only includes the upstream corresponding relationship, the determined target processing module includes the first target processing module.

[0431] In some other embodiments, the first corresponding relationship only includes the above-mentioned downlink corresponding relationship.

[0432] In this embodiment, the terminal device may match the first S-NSSAI with the downlink corresponding relationship to determine the target processing module. It can be understood that in this embodiment, the device only allows accelerated processing of data transmitted via the PDSCH.

[0433] It should be understood that in this embodiment, since the first corresponding relationship only includes the downlink corresponding relationship, the determined target processing module includes the second target processing module.

[0434] The following describes the implementation method 1200 through the interaction between various modules in the terminal device. The terminal device includes an application module, a URSP module and a protocol stack, wherein the application module can be any application program in the application layer.

[0435] In some embodiments, the application module generates a first service identifier in response to a user operation;

[0436] The application module sends a first service identifier to the URSP module;

[0437] The URSP module determines a first S-NSSAI according to the first service identifier;

[0438] The URSP module sends the first S-NSSAI to the protocol stack;

[0439] The protocol stack determines a target processing module according to the first S-NSSAI;

[0440] The protocol stack calls the coprocessor, and the coprocessor processes the first data through the target processing module.

[0441] In some embodiments, after the URSP module sends the first S-NSSAI to the protocol stack, the method 1200 further includes:

[0442] The protocol stack establishes a PDU session with the network device according to the first S-NSSAI;

[0443] After the PDU session is established, the protocol stack generates a slice service interface corresponding to the first S-NSSAI;

[0444] The protocol stack sends service interface information indicating the slice service interface to the URSP module;

[0445] The URSP module determines the slice data interface corresponding to the slice service interface according to the slice service interface;

[0446] The URSP module sends data interface information indicating the slice data interface to the application module, so that the application module transmits service data through the slice data interface.

[0447] For the detailed description of the steps executed by each module, please refer to the above related description, which will not be repeated here.

[0448] In some embodiments, reference Figure 6 , the application module is configured in the application layer, the URSP module is configured in the application framework layer, and the protocol stack is configured in the modem. In this way, configuring the URSP module in the application framework layer to implement the URSP function does not involve the modification of the content of the modem, compared with configuring the URSP module in the modem, which can reduce the difficulty of developers participating in the network slicing technology simulation of 5G terminals and improve the flexibility of implementing the URSP function.

[0449] In other embodiments, reference Figure 7 , the application module is configured in the application layer, and, the URSP module and the protocol stack are both configured in the application layer. In this way, configuring the URSP module in the application layer to implement the URSP function does not involve the modification of the content of the operating system layer, compared with configuring the URSP module in the operating system, which can reduce the difficulty of developers participating in the network slicing technology simulation of 5G terminals and improve the flexibility of implementing the URSP function.

[0450] For example, continue to refer to Figure 7 The protocol stack is configured in the software defined radio SDR, and the URSP module is configured in the SDR. In this way, by integrating both the URSP module and the protocol stack in the SDR, the integration of multiple functional modules can be better achieved, memory usage can be reduced, and system management is convenient.

[0451] It should be noted that the size of the serial numbers of the steps in the above method embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0452] Above, combined Figures 1 to 12, describes in detail the method based on network slicing communication provided by the embodiment of the present application, and will be combined with Figure 13 to Figure 14 , describes in detail a device based on network slicing communication provided according to an embodiment of the present application.

[0453] Fig.13 1 is an exemplary block diagram of an apparatus 1300 provided in an embodiment of the present application. The apparatus 1300 is a terminal device, and may also be a chip in the terminal device.

[0454] The apparatus 1300 is used to execute each process and step corresponding to the terminal device in the above method 1200. The apparatus 1300 includes: a processing unit 1310, and the processing unit 1310 is used to execute the following steps:

[0455] In response to a user operation, generating a first service identifier, where the first service identifier is used to identify a first service to be currently executed;

[0456] Determine, according to the first service identifier, first network slice selection auxiliary information S-NSSAI corresponding to the first service identifier, where the first S-NSSAI is used to indicate a first network slice corresponding to the first service;

[0457] Determine, according to the first S-NSSAI, a target processing module of a data channel processed by a coprocessor, wherein the target processing module includes at least some processing modules of all processing modules of the data channel;

[0458] The coprocessor is used to process first data related to the first service through the target processing module.

[0459] Optionally, the device 1300 includes an application module, a user routing policy URSP module and a protocol stack; and the processing unit 1310 is specifically used for:

[0460] Control the application module to generate the first service identifier in response to the user operation; and the processing unit 1310 is further specifically configured to:

[0461] Control the application module to send the first service identifier to the URSP module;

[0462] The processing unit 1310 is specifically configured to:

[0463] controlling the URSP module to determine the first S-NSSAI according to the first service identifier; and the processing unit 1310 is further configured to:

[0464] Control the URSP module to send the first S-NSSAI to the protocol stack;

[0465] The processing unit 1310 is specifically configured to:

[0466] Controlling the protocol stack to determine the target processing module according to the first S-NSSAI;

[0467] The control protocol stack calls the coprocessor, and the coprocessor processes the first data through the target processing module.

[0468] Optionally, the processing unit 1310 is further configured to:

[0469] Controlling the protocol stack to establish a packet data unit (PDU) session with a network device according to the first S-NSSAI;

[0470] After the PDU session is established, controlling the protocol stack to generate a slice service interface corresponding to the first S-NSSAI;

[0471] Control the protocol stack to send service interface information indicating the slice service interface to the URSP module;

[0472] Control the URSP module to determine a slice data interface corresponding to the slice service interface according to the slice service interface;

[0473] The URSP module is controlled to send data interface information indicating the slice data interface to the application module, so that the application module transmits service data through the slice data interface.

[0474] Optionally, the application module is configured in an application layer, the URSP module is configured in an application framework layer, and the protocol stack is configured in a modem.

[0475] Optionally, the application module is configured in an application layer, and the URSP module and the protocol stack are both configured in the application layer.

[0476] Optionally, the protocol stack is configured in a software defined radio SDR, and the URSP module is configured in the SDR.

[0477] Optionally, the processing unit 1310 is specifically configured to:

[0478] According to the first S-NSSAI, the target processing module corresponding to the first S-NSSAI is determined from a first correspondence relationship indicating multiple S-NSSAIs and multiple groups of processing modules, and one S-NSSAI corresponds to at least one group of processing modules.

[0479] Optionally, the first correspondence includes an uplink correspondence and a downlink correspondence, wherein the uplink correspondence is used to indicate a one-to-one correspondence between M S-NSSAIs and M groups of processing modules, and the downlink correspondence is used to indicate a one-to-one correspondence between N S-NSSAIs and N groups of processing modules, and M and N are both integers greater than or equal to 1.

[0480] Optionally, the processing unit 1310 is specifically configured to:

[0481] The first S-NSSAI is determined according to the first service identifier from a second correspondence relationship indicating multiple service identifiers and multiple S-NSSAIs, and at least one service identifier corresponds to one S-NSSAI.

[0482] Optionally, the target processing module includes a first target processing module, the first target processing module is a processing module for a physical uplink shared channel PUSCH, and the first data includes signaling or uplink service data transmitted through the PUSCH.

[0483] Optionally, the target processing module includes a second target processing module, the second target processing module is a processing module of a physical downlink shared channel PDSCH, and the first data includes signaling or downlink service data transmitted through the PDSCH.

[0484] Optionally, the target processing module includes a first target processing module and a second target processing module, the first target processing module is a processing module for a physical uplink shared channel PUSCH, the second target processing module is a processing module for a physical downlink shared channel PDSCH, the first data includes signaling or uplink service data transmitted via the PUSCH, and the first data includes signaling or downlink service data transmitted via the PDSCH.

[0485] Optionally, the coprocessor is any one of the following processors: a graphics processor GPU, an image signal processor ISP, a digital signal processor DSP, a neural network processor NPU, and a field programmable gate array FPGA.

[0486] It should be understood that the processing unit 1310 can be used to execute each step performed by the terminal device in the method 1200. For specific descriptions, please refer to the relevant descriptions above and will not be repeated here.

[0487] In the embodiments of the present application, Fig.13 The device may also be a chip or a chip system, such as a system on chip (SoC).

[0488] Fig.141400 is a schematic structural diagram of an apparatus 1400 provided in an embodiment of the present application. The apparatus 1400 is used to execute the corresponding steps and / or processes in the above method embodiment.

[0489] The device 1400 includes a processor 1410, a transceiver 1420, and a memory 1430. The processor 1410, the transceiver 1420, and the memory 1430 communicate with each other through an internal connection path, and the processor 1410 can implement the functions of the processor 1410 in various possible implementations of the device 1400. The memory 1430 is used to store instructions, and the processor 1410 is used to execute the instructions stored in the memory 1430, or in other words, the processor 1410 can call these stored instructions to implement the functions of the processor 1410 in the device 1400.

[0490] Optionally, the memory 1430 may include a read-only memory and a random access memory, and provide instructions and data to the processor. A portion of the memory may also include a non-volatile random access memory. For example, the memory may also store information about the device type. The processor 1410 may be used to execute instructions stored in the memory, and when the processor 1410 executes instructions stored in the memory, the processor 1410 is used to execute the various steps and / or processes of the above-mentioned method embodiment corresponding to the network device or the terminal device.

[0491] The apparatus 1400 is used to execute each process and step corresponding to the terminal device in the above method 1200. The processor 1410 is used to execute the following steps:

[0492] In response to a user operation, generating a first service identifier, where the first service identifier is used to identify a first service to be currently executed;

[0493] Determine, according to the first service identifier, first network slice selection auxiliary information S-NSSAI corresponding to the first service identifier, where the first S-NSSAI is used to indicate a first network slice corresponding to the first service;

[0494] Determine, according to the first S-NSSAI, a target processing module of a data channel processed by a coprocessor, wherein the target processing module includes at least some processing modules of all processing modules of the data channel;

[0495] The coprocessor is used to process first data related to the first service through the target processing module.

[0496] Optionally, the device 1400 includes an application module, a user routing policy URSP module and a protocol stack; and the processor 1410 is specifically configured to:

[0497] controlling the application module to generate the first service identifier in response to the user operation; and the processor 1410 is further configured to:

[0498] Control the application module to send the first service identifier to the URSP module;

[0499] The processor 1410 is specifically configured to:

[0500] controlling the URSP module to determine the first S-NSSAI according to the first service identifier; and the processor 1410 is further configured to:

[0501] Control the URSP module to send the first S-NSSAI to the protocol stack;

[0502] The processor 1410 is specifically configured to:

[0503] Controlling the protocol stack to determine the target processing module according to the first S-NSSAI;

[0504] The control protocol stack calls the coprocessor, and the coprocessor processes the first data through the target processing module.

[0505] Optionally, the processor 1410 is further configured to:

[0506] Controlling the protocol stack to establish a packet data unit (PDU) session with a network device according to the first S-NSSAI;

[0507] After the PDU session is established, controlling the protocol stack to generate a slice service interface corresponding to the first S-NSSAI;

[0508] Control the protocol stack to send service interface information indicating the slice service interface to the URSP module;

[0509] Control the URSP module to determine a slice data interface corresponding to the slice service interface according to the slice service interface;

[0510] The URSP module is controlled to send data interface information indicating the slice data interface to the application module, so that the application module transmits service data through the slice data interface.

[0511] Optionally, the application module is configured in an application layer, the URSP module is configured in an application framework layer, and the protocol stack is configured in a modem.

[0512] Optionally, the application module is configured in an application layer, and the URSP module and the protocol stack are both configured in the application layer.

[0513] Optionally, the protocol stack is configured in a software defined radio SDR, and the URSP module is configured in the SDR.

[0514] Optionally, the processor 1410 is specifically configured to:

[0515] According to the first S-NSSAI, the target processing module corresponding to the first S-NSSAI is determined from a first correspondence relationship indicating multiple S-NSSAIs and multiple groups of processing modules, and one S-NSSAI corresponds to at least one group of processing modules.

[0516] Optionally, the first correspondence includes an uplink correspondence and a downlink correspondence, wherein the uplink correspondence is used to indicate a one-to-one correspondence between M S-NSSAIs and M groups of processing modules, and the downlink correspondence is used to indicate a one-to-one correspondence between N S-NSSAIs and N groups of processing modules, and M and N are both integers greater than or equal to 1.

[0517] Optionally, the processor 1410 is specifically configured to:

[0518] The first S-NSSAI is determined according to the first service identifier from a second correspondence relationship indicating multiple service identifiers and multiple S-NSSAIs, and at least one service identifier corresponds to one S-NSSAI.

[0519] Optionally, the target processing module includes a first target processing module, the first target processing module is a processing module for a physical uplink shared channel PUSCH, and the first data includes signaling or uplink service data transmitted through the PUSCH.

[0520] Optionally, the target processing module includes a second target processing module, the second target processing module is a processing module of a physical downlink shared channel PDSCH, and the first data includes signaling or downlink service data transmitted through the PDSCH.

[0521] Optionally, the target processing module includes a first target processing module and a second target processing module, the first target processing module is a processing module for a physical uplink shared channel PUSCH, the second target processing module is a processing module for a physical downlink shared channel PDSCH, the first data includes signaling or uplink service data transmitted via the PUSCH, and the first data includes signaling or downlink service data transmitted via the PDSCH.

[0522] Optionally, the coprocessor is any one of the following processors: a graphics processor GPU, an image signal processor ISP, a digital signal processor DSP, a neural network processor NPU, and a field programmable gate array FPGA.

[0523] It should be understood that the specific process of each device executing the corresponding steps in the above methods has been described in detail in the above method embodiments, and for the sake of brevity, it will not be repeated here.

[0524] It should be understood that in the embodiments of the present application, the processor of the above-mentioned device may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0525] In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in a processor or an instruction in the form of software. The steps of the method disclosed in conjunction with the embodiment of the present application can be directly embodied as a hardware processor for execution, or a combination of hardware and software units in a processor for execution. The software unit can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor executes the instructions in the memory, and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it is not described in detail here.

[0526] The embodiment of the present application provides a computer program product, when the computer program product is run on a terminal device, the terminal device executes the technical solution in the above embodiment. Its implementation principle and technical effect are similar to those of the above method-related embodiments, and will not be repeated here.

[0527] The embodiment of the present application provides a readable storage medium, the readable storage medium contains instructions, when the instructions are executed in a terminal device, the terminal device executes the technical solution of the above embodiment. The implementation principle and technical effect are similar, and will not be repeated here.

[0528] The embodiment of the present application provides a chip, the chip is used to execute instructions, when the chip is running, the technical solution in the above embodiment is executed. The implementation principle and technical effect are similar, and will not be repeated here.

[0529] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0530] It should be understood that the "embodiment" mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, the various embodiments in the entire specification do not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in various embodiments of the present application, the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.

[0531] It should also be understood that in the present application, "when", "if" and "if" all mean that the UE or base station will take corresponding actions under certain objective circumstances. It is not a time limit, and it does not require the UE or base station to make judgments when implementing it, nor does it mean that there are other limitations.

[0532] A person skilled in the art may understand that the various numerical numbers such as first and second involved in the present application are only used for the convenience of description and are not used to limit the scope of the embodiments of the present application, and also indicate the order of precedence.

[0533] In this application, elements expressed in the singular are intended to mean "one or more" rather than "one and only one", unless otherwise specified. In this application, "at least one" is intended to mean "one or more", and "more than one" is intended to mean "two or more", unless otherwise specified.

[0534] The term "and / or" in this article is merely a description of the association relationship of associated objects, indicating that there may be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. A can be singular or plural, and B can be singular or plural.

[0535] In this document, the term "at least one of..." or "at least one of..." means all or any combination of the listed items. For example, "at least one of A, B, and C" may mean: A exists alone, B exists alone, C exists alone, A and B exist at the same time, B and C exist at the same time, and A, B, and C exist at the same time, where A may be singular or plural, B may be singular or plural, and C may be singular or plural.

[0536] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0537] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0538] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0539] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0540] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0541] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories (ROM), random access memories (RAM), magnetic disks or optical disks.

[0542] The same or similar parts between the various embodiments in this application can refer to each other. In the various embodiments in this application, and the various implementation methods / implementation methods / implementation methods in each embodiment, if there is no special explanation and logical conflict, the terms and / or descriptions between different embodiments and the various implementation methods / implementation methods / implementation methods in each embodiment are consistent and can be referenced to each other. The technical features in different embodiments and the various implementation methods / implementation methods / implementation methods in each embodiment can be combined to form new embodiments, implementation methods, implementation methods, or implementation methods according to their inherent logical relationships. The above-described implementation methods of this application do not constitute a limitation on the scope of protection of this application.

[0543] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims. In short, the above is only a preferred embodiment of the technical solution of the present application, and is not used to limit the protection scope of the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.

Claims

1. A method based on network slicing communication, applied to a terminal device, characterized in that: The method comprises: In response to a user operation, generating a first service identifier, where the first service identifier is used to identify a first service to be currently executed; Determine, according to the first service identifier, first network slice selection auxiliary information S-NSSAI corresponding to the first service identifier, where the first S-NSSAI is used to indicate a first network slice corresponding to the first service; Determine, according to the first S-NSSAI, a target processing module of a data channel processed by a coprocessor, wherein the target processing module includes at least some processing modules of all processing modules of the data channel; The coprocessor is used to process first data related to the first service through the target processing module.

2. The method according to claim 1, characterized in that The terminal device includes an application module, a user routing strategy URSP module and a protocol stack; and, The generating a first service identifier in response to a user operation includes: The application module generates the first service identifier in response to the user operation; and the method further includes: The application module sends the first service identifier to the URSP module; The determining, according to the first service identifier, a first S-NSSAI corresponding to the first service identifier includes: The URSP module determines the first S-NSSAI according to the first service identifier; and the method further includes: The URSP module sends the first S-NSSAI to the protocol stack; The step of determining, according to the first S-NSSAI, a target processing module for the data channel to be processed by the coprocessor comprises: The protocol stack determines the target processing module according to the first S-NSSAI; The using the coprocessor to process the first data related to the first service through the target processing module includes: The protocol stack calls the coprocessor, and the coprocessor processes the first data through the target processing module.

3. The method according to claim 2, characterized in that After the URSP module sends the first S-NSSAI to the protocol stack, the method further includes: The protocol stack establishes a packet data unit (PDU) session with a network device according to the first S-NSSAI; After the PDU session is established, the protocol stack generates a slice service interface corresponding to the first S-NSSAI; The protocol stack sends service interface information indicating the slice service interface to the URSP module; The URSP module determines, according to the slice service interface, a slice data interface corresponding to the slice service interface; The URSP module sends data interface information indicating the slice data interface to the application module, so that the application module transmits service data through the slice data interface.

4. The method according to claim 2 or 3, characterized in that: The application module is configured in the application layer, the URSP module is configured in the application framework layer, and the protocol stack is configured in the modem.

5. The method according to claim 2 or 3, characterized in that: The application module is configured in the application layer, and the URSP module and the protocol stack are both configured in the application layer.

6. The method according to claim 5, characterized in that The protocol stack is configured in a software defined radio SDR, and the URSP module is configured in the SDR.

7. The method according to any one of claims 1 to 6, characterized in that The step of determining, according to the first S-NSSAI, a target processing module for the data channel to be processed by the coprocessor comprises: According to the first S-NSSAI, the target processing module corresponding to the first S-NSSAI is determined from a first correspondence relationship indicating multiple S-NSSAIs and multiple groups of processing modules, and one S-NSSAI corresponds to at least one group of processing modules.

8. The method according to claim 7, characterized in that The first correspondence relationship includes an uplink correspondence relationship and a downlink correspondence relationship, wherein the uplink correspondence relationship is used to indicate a one-to-one correspondence between M S-NSSAIs and M groups of processing modules, and the downlink correspondence relationship is used to indicate a one-to-one correspondence between N S-NSSAIs and N groups of processing modules, and M and N are both integers greater than or equal to 1.

9. The method according to any one of claims 1 to 8, characterized in that The determining, according to the first service identifier, a first S-NSSAI corresponding to the first service identifier includes: The first S-NSSAI is determined according to the first service identifier from a second correspondence relationship indicating multiple service identifiers and multiple S-NSSAIs, and at least one service identifier corresponds to one S-NSSAI.

10. The method according to any one of claims 1 to 9, characterized in that The target processing module includes a first target processing module, which is a processing module for a physical uplink shared channel PUSCH, and the first data includes signaling or uplink service data transmitted through the PUSCH.

11. The method according to any one of claims 1 to 9, characterized in that The target processing module includes a second target processing module, the second target processing module is a processing module of a physical downlink shared channel PDSCH, and the first data includes signaling or downlink service data transmitted through the PDSCH.

12. The method according to any one of claims 1 to 9, characterized in that The target processing module includes a first target processing module and a second target processing module, the first target processing module is a processing module for a physical uplink shared channel PUSCH, the second target processing module is a processing module for a physical downlink shared channel PDSCH, the first data includes signaling or uplink service data transmitted via the PUSCH, and the first data includes signaling or downlink service data transmitted via the PDSCH.

13. The method according to any one of claims 1 to 12, characterized in that The coprocessor is any one of the following processors: a graphics processor GPU, an image signal processor ISP, a digital signal processor DSP, a neural network processor NPU, and a field programmable gate array FPGA.

14. A terminal device, characterized in that: include: Memory, for storing computer instructions; A processor, configured to call the computer instructions stored in the memory to execute the method according to any one of claims 1 to 13.

15. A computer-readable storage medium, characterized in that: Used to store computer instructions, wherein the computer instructions are used to implement the method according to any one of claims 1 to 13.

16. A chip, characterized in that: The chip comprises: Memory: used to store instructions; A processor is used to call and execute the instructions from the memory so that a terminal device equipped with the chip system executes the method as described in any one of claims 1 to 13.

Citation Information

Patent Citations

  • Network slice selection method and related product

    CN110881207A

  • Application data transmission method and system and electronic equipment

    CN114221869A

  • Network system and network optimization method based on cloud network fusion technology

    CN114337939A

  • Slice resource allocation method, SMF entity, UPF entity and storage medium

    CN114501635A

  • Network slice association method, equipment main body, communication module and terminal equipment

    CN114978911A

Cited By

  • Method and apparatus based on network slice communication, and terminal device

    EP4701270A1

  • Method and apparatus based on network slice communication, and terminal device

    WO2024244576A1