Transmission processing method, network selection processing method and related equipment

Abstract

The invention discloses a transmission processing method, a network selection processing method and related equipment, and belongs to the technical field of communication, and the transmission processing method comprises the steps that a first functional entity of a terminal receives a first request message from an upper layer of the terminal, and the first request message comprises network slice selection auxiliary information NSSAI, the NSSAI comprises a slice identifier of at least one target slice, and the first request message is used for requesting to transmit application data of a target application of the upper layer on a protocol data unit PDU session established on the target slice; and the first functional entity sends a first response message to the upper layer.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a transmission processing method, a network selection processing method and related equipment. Background Art

[0002] With the development of communication technology, network slicing has been introduced in communication systems. For example, a terminal can select a suitable slice based on the slice associated with the application layer, and use the slice to access the Virtual Public Land Mobile Network (VPLMN) network. Currently, there is no clear definition of the behavior of the terminal before the slice selection is triggered, which needs to be solved urgently. Summary of the invention

[0003] The embodiments of the present application provide a transmission processing method, a network selection processing method and related equipment, which clarify the behavior inside the terminal before triggering the network selection of the slice.

[0004] In a first aspect, a transmission processing method is provided, comprising:

[0005] A first functional entity of the terminal receives a first request message from an upper layer of the terminal, where the first request message includes network slice selection assistance information NSSAI, where the NSSAI includes a slice identifier of at least one target slice, and the first request message is used to request transmission of application data of a target application of the upper layer on a protocol data unit PDU session established by the target slice;

[0006] The first functional entity sends a first response message to the upper layer.

[0007] In a second aspect, a transmission processing method is provided, including:

[0008] The second functional entity of the terminal receives a second request message from the first functional entity of the terminal, where the second request message includes the NSSAI, and the second request message is used to request policy matching for an upper layer target application of the terminal;

[0009] The second functional entity sends a second response message to the first functional entity, where the second response message is used to indicate whether the target application matches a non-default rule.

[0010] In a third aspect, a transmission processing method is provided, including:

[0011] The second functional entity of the terminal receives a fourth request message from an upper layer of the terminal, where the fourth request message includes network slice selection auxiliary information NSSAI, where the NSSAI includes a slice identifier of at least one target slice, and the fourth request message is used to request policy matching for a target application of the upper layer;

[0012] In case the policy matching fails, the second functional entity performs the target operation;

[0013] The target operation includes any of the following:

[0014] Sending a fourth response message to the upper layer, where the fourth response message is used to indicate that the policy match fails, and the fourth response message is used to trigger the upper layer to send a fifth request message to the first functional entity of the terminal, where the fifth request message is used to trigger a slice-based network selection operation;

[0015] A sixth request message is sent to the first functional entity of the terminal, where the sixth request message is used to trigger a slice-based network selection operation.

[0016] In a fourth aspect, a transmission processing method is provided, including:

[0017] The upper layer of the terminal sends a fourth request message to the second functional entity of the terminal, and the fourth request message includes network slice selection auxiliary information NSSAI, and the NSSAI includes a slice identifier of at least one target slice, and the fourth request message is used to request policy matching for the target application of the upper layer.

[0018] In a fifth aspect, a network selection processing method is provided, including:

[0019] The first functional entity of the terminal receives a target message, where the target message is used to trigger execution of a slice-based network selection operation;

[0020] The first functional entity performs a slice-based network selection operation according to the target message;

[0021] The target message includes any of the following:

[0022] A second response message sent by the second functional entity of the terminal, wherein the second response message is used to indicate that an upper layer target application of the terminal does not match a non-default rule;

[0023] A first request message sent by an upper layer of the terminal, the first request message includes network slice selection auxiliary information NSSAI, the NSSAI includes a slice identifier of at least one target slice, and the slice identifier of the target slice belongs to a rejected NSSAI;

[0024] A third response message sent by the network side device, wherein the third response message is used to indicate that the slice identifier of the target slice included in the registered NSSAI belongs to the rejected NSSAI;

[0025] A fifth request message sent by an upper layer of the terminal, wherein the fifth request message is used to trigger a slice-based network selection operation;

[0026] The sixth request message sent by the second functional entity is used to trigger a slice-based network selection operation.

[0027] In a sixth aspect, a transmission processing device is provided, including:

[0028] A first receiving module, configured to receive a first request message from an upper layer of the terminal, where the first request message includes network slice selection auxiliary information NSSAI, where the NSSAI includes a slice identifier of at least one target slice, and the first request message is used to request transmission of application data of a target application of the upper layer on a protocol data unit PDU session established by the target slice;

[0029] The first sending module is used to send a first response message to the upper layer.

[0030] In a seventh aspect, a transmission processing device is provided, including:

[0031] A second receiving module, configured to receive a second request message from the first functional entity of the terminal, wherein the second request message includes the NSSAI, and the second request message is used to request policy matching for an upper layer target application of the terminal;

[0032] The second sending module is used to send a second response message to the first functional entity, where the second response message is used to indicate whether the target application matches a non-default rule.

[0033] In an eighth aspect, a transmission processing device is provided, including:

[0034] A third receiving module is configured to receive a fourth request message from an upper layer of the terminal, where the fourth request message includes network slice selection auxiliary information NSSAI, where the NSSAI includes a slice identifier of at least one target slice, and the fourth request message is used to request policy matching for a target application of the upper layer;

[0035] A first execution module, used for executing a target operation when a policy match fails;

[0036] The target operation includes any of the following:

[0037] Sending a fourth response message to the upper layer, where the fourth response message is used to indicate that the policy match fails, and the fourth response message is used to trigger the upper layer to send a fifth request message to the first functional entity of the terminal, where the fifth request message is used to trigger a slice-based network selection operation;

[0038] A sixth request message is sent to the first functional entity of the terminal, where the sixth request message is used to trigger a slice-based network selection operation.

[0039] In a ninth aspect, a transmission processing device is provided, including:

[0040] The fourth sending module is used to send a fourth request message to the second functional entity of the terminal, wherein the fourth request message includes network slice selection auxiliary information NSSAI, the NSSAI includes a slice identifier of at least one target slice, and the fourth request message is used to request policy matching for the upper-layer target application of the terminal.

[0041] In a tenth aspect, a network selection processing device is provided, comprising:

[0042] A fifth receiving module, used to receive a target message, where the target message is used to trigger a slice-based network selection operation;

[0043] A second execution module, used to perform a slice-based network selection operation according to the target message;

[0044] The target message includes any of the following:

[0045] A second response message sent by the second functional entity of the terminal, wherein the second response message is used to indicate that an upper layer target application of the terminal does not match a non-default rule;

[0046] A first request message sent by an upper layer of the terminal, the first request message includes network slice selection auxiliary information NSSAI, the NSSAI includes a slice identifier of at least one target slice, and the slice identifier of the target slice belongs to a rejected NSSAI;

[0047] A third response message sent by the network side device, wherein the third response message is used to indicate that the slice identifier of the target slice included in the registered NSSAI belongs to the rejected NSSAI;

[0048] A fifth request message sent by an upper layer of the terminal, wherein the fifth request message is used to trigger a slice-based network selection operation;

[0049] The sixth request message sent by the second functional entity is used to trigger a slice-based network selection operation.

[0050] In the eleventh aspect, a terminal is provided, which includes a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in any one of the first to fifth aspects are implemented.

[0051] In a twelfth aspect, a terminal is provided, including a processor and a communication interface, wherein:

[0052] A processor is configured to receive a first request message from an upper layer of a terminal, wherein the first request message includes network slice selection auxiliary information NSSAI, the NSSAI includes a slice identifier of at least one target slice, and the first request message is used to request transmission of application data of a target application of the upper layer on a protocol data unit PDU session established by the target slice; and send a first response message to the upper layer;

[0053] Alternatively, the processor is configured to receive a second request message from a first functional entity of the terminal, the second request message includes the NSSAI, and the second request message is used to request policy matching for a target application at an upper layer of the terminal; the second sending module is configured to send a second response message to the first functional entity, the second response message is used to indicate whether the target application matches a non-default rule;

[0054] Alternatively, a processor is configured to receive a fourth request message from an upper layer of the terminal, the fourth request message including network slice selection auxiliary information NSSAI, the NSSAI including a slice identifier of at least one target slice, and the fourth request message is used to request policy matching for a target application of the upper layer; in the case where the policy matching fails, performing a target operation; wherein the target operation includes any one of the following: sending a fourth response message to the upper layer, the fourth response message is used to indicate a policy matching failure, and the fourth response message is used to trigger the upper layer to send a fifth request message to the first functional entity of the terminal, the fifth request message is used to trigger a slice-based network selection operation; sending a sixth request message to the first functional entity of the terminal, the sixth request message is used to trigger a slice-based network selection operation;

[0055] Alternatively, the processor is configured to send a fourth request message to the second functional entity of the terminal, where the fourth request message includes network slice selection auxiliary information NSSAI, where the NSSAI includes a slice identifier of at least one target slice, and the fourth request message is used to request policy matching for an upper layer target application of the terminal;

[0056] Alternatively, the processor is configured to receive a target message, where the target message is used to trigger a slice-based network selection operation; and perform a slice-based network selection operation according to the target message;

[0057] The target message includes any of the following:

[0058] A second response message sent by the second functional entity of the terminal, wherein the second response message is used to indicate that an upper layer target application of the terminal does not match a non-default rule;

[0059] A first request message sent by an upper layer of the terminal, the first request message includes network slice selection auxiliary information NSSAI, the NSSAI includes a slice identifier of at least one target slice, and the slice identifier of the target slice belongs to a rejected NSSAI;

[0060] A third response message sent by the network side device, wherein the third response message is used to indicate that the slice identifier of the target slice included in the registered NSSAI belongs to the rejected NSSAI;

[0061] A fifth request message sent by an upper layer of the terminal, wherein the fifth request message is used to trigger a slice-based network selection operation;

[0062] The sixth request message sent by the second functional entity is used to trigger a slice-based network selection operation.

[0063] In the thirteenth aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in any one of the first to fifth aspects are implemented.

[0064] In a fourteenth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in any one of the first to fifth aspects are implemented.

[0065] In the fifteenth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in any one of the first to fifth aspects.

[0066] In the sixteenth aspect, a computer program / program product is provided, wherein the computer program / program product is stored in a storage medium, and the program / program product is executed by at least one processor to implement the method as described in any one of the first to fifth aspects.

[0067] In an embodiment of the present application, a first request message is received from an upper layer of the terminal through a first functional entity of the terminal, the first request message includes network slice selection auxiliary information NSSAI, the NSSAI includes a slice identifier of at least one target slice, and the first request message is used to request the transmission of application data of the target application of the upper layer on the protocol data unit PDU session established by the target slice; the first functional entity sends a first response message to the upper layer. In this way, the first functional entity can determine whether to trigger a slice-based network selection operation based on NSSAI. Therefore, the embodiment of the present application clarifies the behavior inside the terminal before triggering the slice network selection, thereby improving the reliability of application data transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0068] Figure 1 It is a schematic diagram of a network structure to which this application can be applied;

[0069] Figure 2 It is one of the flow charts of a transmission processing method provided by this application;

[0070] Figure 3 This is the second flow chart of a transmission processing method provided by this application;

[0071] Figure 4 This is the third flow chart of a transmission processing method provided by this application;

[0072] Figure 5 This is a fourth flow chart of a transmission processing method provided by the present application;

[0073] Figure 6 It is a flow chart of a network selection processing method provided by the present application;

[0074] Figure 7 It is one of the structural schematic diagrams of a transmission processing device provided by the present application;

[0075] Figure 8 This is the second structural diagram of a transmission processing device provided by the present application;

[0076] Fig. 9 This is the third structural diagram of a transmission processing device provided by the present application;

[0077] Fig.10 This is the fourth structural diagram of a transmission processing device provided by the present application;

[0078] Fig.11 It is a structural schematic diagram of a network selection processing device provided by the present application;

[0079] Fig.12 It is a structural schematic diagram of a communication device provided by the present application;

[0080] Fig.13 It is a structural schematic diagram of a terminal provided by this application; DETAILED DESCRIPTION

[0081] The terms "first", "second", etc. of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of one type, and the number of objects is not limited, for example, the first object can be one or more. In addition, "or" in the present application represents at least one of the connected objects. For example, "A or B" covers three schemes, namely, Scheme 1: including A but not including B; Scheme 2: including B but not including A; Scheme 3: including both A and B. The character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0082] The term "indication" in this application can be a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, operations to be performed, or request results in the sent indication; an indirect indication can be understood as the receiver determining the corresponding information according to the indication sent by the sender, or making a judgment and determining the operation to be performed or the request result according to the judgment result.

[0083] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following descriptions, but these technologies can also be applied to systems other than NR systems, such as the 6th generation (6 th Generation, 6G) communication system.

[0084] Figure 1A block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network side device 12. Among them, the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (Ultra-mobile Personal Computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), an augmented reality (Augmented Reality, AR), a virtual reality (Virtual Reality, VR) device, a robot, a wearable device (Wearable Device), an aircraft (flight vehicle), a vehicle-mounted device (Vehicle User Equipment, VUE), a ship-mounted device, a pedestrian terminal (Pedestrian User Equipment, PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.), a game console, a personal computer (Personal Computer, PC), a teller machine or a self-service machine and other terminal side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be referred to as a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) access point (Access Point, AS) or a wireless fidelity (Wireless Fidelity, WiFi) node, etc.Among them, the base station may be referred to as a Node B (NB), an evolved Node B (eNB), a next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a Relay Base Station (RBS), a Serving Base Station (SBS), a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a Home Node B (HNB), a Home Evolved Node B, a Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0085] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (Mobility Management Entity, MME), access mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), user plane function (User Plane Function, UPF), policy control function (Policy Control Function, PCF), policy and charging rules function unit (Policy and Charging Rules Function, PCRF), edge application service discovery function (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data storage (Unified Data Repository, UDR), home user server (Home Subscriber Server, HSS), centralized network configuration (CNC), network storage function (Network Repository Function, NRF), network exposure function (Network Exposure Function, NEF), local NEF (Local NEF, or L-NEF), binding support function (Binding Support Function, BSF), application function (Application Function, AF), etc. It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0086] For ease of understanding, some contents involved in the embodiments of the present application are described below:

[0087] 1. Slice.

[0088] In the 5G network, the logical functions of network resources are divided into several combinations, such as the combination of core network elements and wireless links. The network elements in a combination are limited to the same PLMN and contain at least two parts: the access network and the core network. Each combination is called a slice. In order to identify these slices, an ID is set for each slice, called Single Network Slice Selection Assistance Information (S-NSSAI). Each S-NSSAI contains a slice type or service type (Slice / service type, SST) and a slice differentiator (SliceDifferentiator, SD). Multiple S-NSSAIs are combined into NSSAI.

[0089] Several types of NSSAI in terminals and networks:

[0090] 1. Requested NSSAI, which is carried by the terminal in the registration request message. When the terminal registers in a PLMN, it tells the network which slices of the current PLMN the terminal wants to request services on.

[0091] 2. Allowed NSSAI: This is configured by the network side device and can be sent to the terminal in a registration accept message or a configuration update command message. After the terminal successfully registers in the current PLMN, the slices of the current PLMN are allowed to be used by the terminal's services, which are indicated by Allowed NSSAI. For example, the terminal is allowed to establish a protocol data unit (PDU) session in these slices.

[0092] 3. Configured NSSAI, which is configured by the network side device. It can be sent to the UE through the registration accept message or the configuration update command message. Unlike the allowed NSSAI, the slices in the configured NSSAI cannot be completely determined to be directly used by the UE. The UE still needs to carry it in the requested NSSAI to ask the network whether it can become the allowed NSSAI.

[0093] 4. Default configured NSSAI, which is configured by the UDM of the Home Public Land Mobile Network (HPLMN) for the UE. Generally, it is configured inside the UE and can also be modified through the configuration update command message. The purpose of its introduction is: when the serving network does not provide the configured NSSAI to the UE, the UE can use the default configured NSSAI to request registration.

[0094] 5. Subscribed NSSAI, which is stored in the UDM after the UE joins the network. It is the slice subscribed by the UE. For slices not in this subscribed NSSAI, the network cannot provide services of the slice to the UE.

[0095] 6. Default NSSAI: One or more S-NSSAIs in the Subscribed NSSAI are marked as default, also known as Default Subscribed S-NSSAI.

[0096] 7. Pending NSSAI: Some slices require network slice-specific authentication and authorization (NSSAA) on the network side. When the UE requests this type of slice, the network will authenticate and authorize it. Before the result is determined, the slice is called pending NSSAI.

[0097] 2. Allow and deny slicing.

[0098] In the registration process, the UE will first send a registration request message to the network side device. The UE will encapsulate the requested slice (requested NSSAI) in the registration request message and report it to the network. The requested NSSAI contains one or more S-NSSAIs. In general, the UE will select the slice it intends to register (intend to register) for registration. If there is allowed NSSAI or configured NSSAI, the UE selects a subset of them; if there is neither of the above, the default configured NSSAI is used; if there is none, the requested NSSAI is not carried.

[0099] The network determines whether it can provide services for the requested S-NSSAI based on the UE's subscription status and the current network status. If it can provide services for the requested S-NSSAI, the network puts the S-NSSAI in the allowed NSSAI and responds to the UE. If it cannot provide services for the requested NSSAI, the network puts the S-NSSAI in the rejected NSSAI and responds to the UE.

[0100] Optionally, if the UE indicates support for delayed rejection of NSSAI extended rejected NSSAI in the 5GMM capability IE in the registration request message, the network side device will also put the slices that cannot provide service into extended rejected NSSAI and reply to the UE, carrying the corresponding rejection reason.

[0101] 3. Network selection based on slicing.

[0102] When a UE uses an application (APP) / service, it will use a slice, but the current network VPLMN cannot provide it, so the HPLMN is required to provide the priority of VPLMN network selection. The UE selects a suitable VPLMN to register for the slice and obtain services based on the network priority information related to the slice. We call this process slice-based network selection.

[0103] The transmission processing method provided in the embodiment of the present application is described in detail below through some embodiments and their application scenarios in combination with the accompanying drawings.

[0104] Reference Figure 2 , the embodiment of the present application provides a transmission processing method, such as Figure 2 As shown, the transmission processing method includes:

[0105] Step 201: A first functional entity of a terminal receives a first request message from an upper layer of the terminal, where the first request message includes network slice selection assistance information NSSAI, where the NSSAI includes a slice identifier of at least one target slice, and the first request message is used to request transmission of application data of a target application of the upper layer on a protocol data unit PDU session established by the target slice;

[0106] Step 202: The first functional entity sends a first response message to the upper layer.

[0107] In the embodiment of the present application, the first response message is a reply message to the first request message. Optionally, in some embodiments, the first request message may also include but is not limited to the following description information: request identifier, operating system identifier (operator system identifier, OS ID) and application identifier (APP ID).

[0108] Optionally, the NSSAI type associated with the slice identifier of the target slice may include allowed NSSAI, rejected NSSAI and configured NSSAI, and the corresponding first response message is different for different NSSAI types. The following embodiments describe this in detail.

[0109] Optionally, the slice identifier of a target slice may be indicated by S-NSSAI.

[0110] Optionally, the first functional entity can be understood or replaced by a non-access stratum (NAS layer), or can be understood or replaced by a functional entity of a NAS layer. The upper layer can be understood or replaced by an APP layer, and can also be referred to as an upper layer of the first functional entity.

[0111] It should be noted that the terminal APP layer can interact with the APP server (Application Function) to obtain the association information between the application and the slice. The association information may include OS ID, APP ID and NSSAI, which is used to select one or more slices when the subsequent application needs to transmit data. Different APPs may interact with different servers to obtain the association information between the application and the slice. In an embodiment of the present application, NSSAI may contain only a slice identifier of one slice, or it may be a slice identifier of multiple slices. When NSSAI contains slice identifiers of multiple slices, the application can select one slice or multiple slices. When multiple slices are selected, the slice with the first ranking is the slice with the highest priority. If it cannot be met, the second ranked slice is used (the ranking here refers to the order of priority encoding and decoding in encoding and decoding), and so on.

[0112] In an embodiment of the present application, a first request message is received from an upper layer of the terminal through a first functional entity of the terminal, the first request message includes network slice selection auxiliary information NSSAI, the NSSAI includes a slice identifier of at least one target slice, and the first request message is used to request the transmission of application data of the target application of the upper layer on the protocol data unit PDU session established by the target slice; the first functional entity sends a first response message to the upper layer. In this way, the first functional entity can determine whether to trigger a slice-based network selection operation based on NSSAI. Therefore, the embodiment of the present application clarifies the behavior inside the terminal before triggering the slice network selection, thereby improving the reliability of application data transmission.

[0113] Optionally, in some embodiments, after the first functional entity receives the first request message from the upper layer, the method further includes:

[0114] In a case where the slice identifier of the target slice belongs to allowing NSSAI, the first functional entity sends a second request message to a second functional entity of the terminal, where the second request message includes the NSSAI, and the second request message is used to request policy matching for the target application;

[0115] The first functional entity receives a second response message from the second functional entity, where the second response message is used to indicate whether the target application matches a non-default rule;

[0116] The first functional entity generates the first response message based on the second response message.

[0117] In the embodiment of the present application, the second functional entity may be understood or replaced by a UE Route Selection Policy layer (URSP layer), or may be understood or replaced by a functional entity of the URSP layer.

[0118] Optionally, in some embodiments, the second request message may also include, but is not limited to, the following description information: request ID, OS ID, APP ID, IP address, and data network name. It should be understood that the second request message may be understood or replaced by a policy matching request message, and the policy matching of the target application may be understood as finding a policy that matches the description of the target application.

[0119] It should be understood that in an embodiment of the present application, the slice identifier of the target slice belongs to the allowed NSSAI, which can be used to determine for the first functional entity that the slice identifier of the target slice belongs to the allowed NSSAI, or it can be used to indicate to the network side device that the slice identifier of the target slice belongs to the allowed NSSAI.

[0120] Optionally, when the second functional entity receives the second request message, there are two situations:

[0121] Case 1: a non-default rule in the URSP is matched, that is, an established PDU session is matched or a new PDU session is successfully established. At this time, the second response message returned by the second functional entity is used to indicate that the policy match is successful. The second response message may include a request ID and a message type (i.e., a match success message or a match failure message). After the first functional entity receives the second response message, the first functional entity sends a first response message to the upper layer. At this time, the first response message includes a request ID and a PDU session identifier.

[0122] Case 2: Failure to match a non-default rule (for example, although the TD containing the APP ID is matched, the TD does not contain the NSSAI carried in the second request message) or the default rule in the URSP is matched. At this time, the second response message returned by the second functional entity is used to indicate that the policy match fails.

[0123] Optionally, for the above situation 2, it can also be understood that the target application does not match any non-default rule.

[0124] Optionally, in some embodiments, when the second response message indicates that the target application does not match a non-default rule, after the first functional entity receives the second response message from the second functional entity, the method further includes:

[0125] The first functional entity performs a slice-based network selection operation;

[0126] Optionally, in some embodiments, after the first functional entity receives the first request message from the upper layer, the method further includes:

[0127] In the case that the slice identifier of the target slice belongs to rejecting NSSAI, the first functional entity generates the first response message, and the first response message is used to indicate the rejection of the transmission of the application data of the upper layer.

[0128] It should be understood that in an embodiment of the present application, the slice identifier of the target slice belonging to the rejected NSSAI can be determined by the first functional entity, or it can be indicated by the network side device that the slice identifier of the target slice belongs to the rejected NSSAI.

[0129] Optionally, in some embodiments, when the slice identifier of the target slice belongs to a rejected NSSAI, the method further includes:

[0130] The first functional entity performs a slice-based network selection operation.

[0131] Optionally, in some embodiments, the first functional entity performing a slice-based network selection operation includes:

[0132] When a preset condition is met, the first functional entity performs a slice-based network selection operation;

[0133] The preset condition includes at least one of the following:

[0134] The terminal supports the network selection feature based on slicing;

[0135] The terminal stores information on the association of slices with applicable networks;

[0136] The terminal is in automatic network selection mode;

[0137] The terminal is in non-emergency service;

[0138] The application being used by the terminal allows network interruption.

[0139] Optionally, when the second response message indicates that the target application does not match a non-default rule, the first functional entity can determine whether to perform a slice-based network selection operation based on the above-mentioned preset conditions. After the first functional entity initiates a slice-based network selection operation, it indicates that the current network cannot support the service of the APP. At this time, the first functional entity can send a first response message to the upper layer.

[0140] Optionally, in some embodiments, when the target application does not match a non-default rule, the second response message includes a first failure reason, where the first failure reason is used to indicate that the target application does not match a non-default rule.

[0141] Optionally, in the case that the slice identifier of the target slice belongs to rejecting NSSAI, the first functional entity can determine whether to perform a slice-based network selection operation according to the above-mentioned preset conditions. After the first functional entity initiates a slice-based network selection operation, it indicates that the current network cannot support the service of the APP. At this time, the first functional entity can send a first response message to the upper layer.

[0142] Optionally, in some embodiments, when the slice identifier of the target slice belongs to configuring NSSAI, the method further includes:

[0143] The first functional entity sends a third request message to the network side device, where the third request message is used to register the NSSAI;

[0144] The first functional entity receives a third response message from the network side device, and the third response message is used to indicate that the slice identifier of the target slice belongs to allowed NSSAI or rejected NSSAI.

[0145] Optionally, the third request message may be understood or replaced by a registration request message, and the third response message may be understood as a reply of the network side device to the third request message, that is, may be understood or replaced by a registration accept message.

[0146] It should be understood that in an embodiment of the present application, the slice identifier of the target slice contained in the first request message received by the first functional entity belongs to the configured NSSAI, that is, the first functional entity is currently unable to determine whether the slice identifier of the target slice is allowed NSSAI or rejected NSSAI. The terminal will trigger a periodic registration update, carry the slice identifier of the target slice contained in the first request message in the requested NSSAI, and include it in the third request message and send it to the network side device, waiting for the network side device to reply through a third response message whether the slice identifier of the target slice belongs to allowed NSSAI or rejected NSSA. And based on the result of the reply, execute the corresponding process. For example, when the slice identifier of the target slice belongs to allowed NSSAI, the first functional entity sends a second request message to the second functional entity; when the slice identifier of the target slice belongs to rejected NSSAI, the first functional entity generates the first response message, and the first response message is used to indicate the rejection of the transmission of the upper layer application data.

[0147] Optionally, in some embodiments, when the target application does not match a non-default rule or the slice identifier of the target slice belongs to a rejected NSSAI, the first response message includes at least one of a second failure cause and target time information, and the target time information is used to indicate the waiting time for the upper layer to resend the first request message.

[0148] In an embodiment of the present application, the second failure cause is used to indicate that the slice identifier of the target slice belongs to rejectedNSSAI or indicates that the target application does not match a non-default rule. In other words, the second failure cause is used to indicate that the target slice is unavailable, resulting in the inability to transmit application data on the PDU session established with the target slice.

[0149] Optionally, in the case where the first response message includes the target time information, the upper layer may send the first request message again after a preset time interval, where the preset time is determined based on the target time information.

[0150] It should be noted that the slice-based network selection operation can be understood as selecting a network according to the priority of the PLMN associated with the slice. For example, when a user needs to use S-NSSAI 1, S-NSSAI 1 is associated with a set of PLMN lists, with a priority order from PLMN A to PLMN C. The UE will first try to reside on the network of PLMN A. If it cannot reside (for example, it cannot reside after 5 attempts), it will try to reside on PLMN B, and so on.

[0151] It should be understood that the above embodiment refers to the interactive process performed by the UE after the terminal initiates the initial registration, when the terminal uses the APP application, the URSP rule information is stored inside the UE. Before the initial registration, the URSP rule information may not be stored inside the UE. At this time, there is only interaction between the upper layer and the first functional entity of the terminal, that is, the first functional entity directly determines whether the slice is rejected NSSAI after receiving the first request message. If the slice is rejected, the first functional entity performs a slice-based network selection operation when the preset conditions are met. The preset conditions are as above and will not be repeated here.

[0152] Reference Figure 3 , the embodiment of the present application also provides a transmission processing method, such as Figure 3 As shown, the transmission processing method includes:

[0153] Step 301: A second functional entity of a terminal receives a second request message from a first functional entity of the terminal, where the second request message includes NSSAI, and the second request message is used to request policy matching for a target application at an upper layer of the terminal;

[0154] Step 302: The second functional entity sends a second response message to the first functional entity, where the second response message is used to indicate whether the target application matches a non-default rule.

[0155] Optionally, when the target application does not match a non-default rule, the second response message includes a first failure reason, where the first failure reason is used to indicate that the target application does not match a non-default rule.

[0156] Optionally, the first functional entity is a non-access layer, the upper layer is an application layer, and the second functional entity is a terminal routing policy layer.

[0157] Reference Figure 4, the embodiment of the present application also provides a transmission processing method, such as Figure 4 As shown, the transmission processing method includes:

[0158] Step 401: A second functional entity of the terminal receives a fourth request message from an upper layer of the terminal, where the fourth request message includes network slice selection auxiliary information NSSAI, where the NSSAI includes a slice identifier of at least one target slice, and the fourth request message is used to request policy matching for a target application of the upper layer;

[0159] Step 402: when the policy matching fails, the second functional entity performs the target operation;

[0160] The target operation includes any of the following:

[0161] Sending a fourth response message to the upper layer, where the fourth response message is used to indicate that the policy match fails, and the fourth response message is used to trigger the upper layer to send a fifth request message to the first functional entity of the terminal, where the fifth request message is used to trigger a slice-based network selection operation;

[0162] A sixth request message is sent to the first functional entity of the terminal, where the sixth request message is used to trigger a slice-based network selection operation.

[0163] In an embodiment of the present application, the fourth response message is a reply message to the fourth request message. Optionally, in some embodiments, the fourth request message may also include but is not limited to the following description information: request ID, OSID, APP ID, IP address and data network name (Data Network Name). It should be understood that the fourth request message can be understood or replaced by a policy matching request message, and the policy matching of the target application can be understood as finding a policy that meets the description of the target application.

[0164] Optionally, when the second functional entity receives the second request message, there are two situations:

[0165] Case 1, the policy matches successfully, that is, after the URSP receives the policy match message, the URSP layer matches the rule that conforms to the APP descriptor (including OS ID, APP ID, NSSAI), and finds that the non-default rule meets the requirements; at this time, the established PDU session is used or a new PDU session is created. That is to say, after the second functional entity receives the fourth request message, the second functional entity matches the rule that conforms to the APP descriptor (including OS ID, APP ID, NSSAI), and finds that the non-default rule meets the requirements, reuses the existing PDU session, or creates a new PDU session using the target slice. The existing PDU session refers to the PDU session established using the target slice before receiving the fourth request message. At this time, the response message in reply to the fourth request message indicates that the policy match is successful, and the response message can carry the request ID and the PDU session identifier.

[0166] Case 2: Policy matching fails, that is, no non-default rule is matched. For example, although the TD containing the APP ID is matched, the TD does not contain the NSSAI carried in the fourth request message or matches the default rule in the URSP. That is to say, when the second functional entity cannot complete the policy matching, the second functional entity can send the fourth response message to the upper layer, or send the fifth request message to the first functional entity, thereby triggering the slice-based network selection operation.

[0167] It should be understood that the second functional entity sending the fourth response message to the upper layer can be understood as indirectly triggering the first functional entity to perform a slice-based network selection operation; the second functional entity sending the fifth request message to the first functional entity can be understood as directly triggering the first functional entity to perform a slice-based network selection operation.

[0168] It should be noted that the terminal APP layer can interact with the APP server (Application Function) to obtain the association information between the application and the slice. The association information may include OS ID, APP ID and NSSAI, which is used to select one or more slices when the subsequent application needs to transmit data. Different APPs may interact with different servers to obtain the association information between the application and the slice. In an embodiment of the present application, NSSAI may contain only a slice identifier of one slice, or it may be a slice identifier of multiple slices. When NSSAI contains slice identifiers of multiple slices, the application can select one slice or multiple slices. When multiple slices are selected, the slice with the first ranking is the slice with the highest priority. If it cannot be met, the second ranked slice is used (the ranking here refers to the order of priority encoding and decoding in encoding and decoding), and so on.

[0169] In an embodiment of the present application, a fourth request message is received from an upper layer through a second functional entity, the fourth request message includes network slice selection auxiliary information NSSAI, the NSSAI includes a slice identifier of at least one target slice, and the fourth request message is used to request policy matching for the target application of the upper layer; in the case of a policy match failure, the terminal performs a target operation; wherein the target operation includes any one of the following: the second functional entity sends a fourth response message to the upper layer, the fourth response message is used to indicate a policy match failure, and the fourth response message is used to trigger the upper layer to send a fifth request message to the first functional entity; the second functional entity sends a fifth request message to the first functional entity; wherein the fifth request message is used to trigger a slice-based network selection operation. In this way, since the behavior of the terminal before triggering the slice network selection is clarified, the reliability of application data transmission is improved.

[0170] It should be noted that in an embodiment of the present application, the above occurs before the UE initiates the initial registration, and the terminal has not saved the URSP rule when using the APP application. Therefore, the second functional entity will directly send the fourth response message to the upper layer to notify the upper layer that the policy match fails, thereby indirectly triggering the first functional entity of the terminal to perform a slice-based network selection operation.

[0171] Optionally, the policy matching failure can be understood as not matching a non-default rule. For example, in some embodiments, the policy matching failure condition includes at least one of the following:

[0172] Matches the default rule;

[0173] A non-default rule is matched, and the traffic descriptor of the non-default rule does not include a slice identifier, or the slice identifier in the traffic descriptor of the non-default rule is inconsistent with the slice identifier of the target slice.

[0174] Optionally, in some embodiments, the fourth response message includes at least one of the first failure cause, the NSSAI and target time information, and the target time information is used to indicate the waiting time for the upper layer to resend the fourth request message.

[0175] In the embodiment of the present application, the first failure reason is used to indicate that the target application does not match a non-default rule. Optionally, the fourth response message may further carry a request ID.

[0176] Optionally, in the case that the fourth response message includes the target time information, the upper layer may send the fourth request message again after a preset time interval, where the preset time is determined based on the target time information.

[0177] It should be noted that the slice-based network selection operation can be understood as selecting a network according to the priority of the PLMN associated with the slice. For example, when a user needs to use S-NSSAI 1, S-NSSAI 1 is associated with a set of PLMN lists, with a priority order from PLMN A to PLMN C. The UE will first try to reside on the network of PLMN A. If it cannot reside (for example, it cannot reside after 5 attempts), it will try to reside on PLMN B, and so on.

[0178] Optionally, the fifth request message or the sixth request message may include descriptive information such as request ID, APP ID and NSSAI. After the first functional entity receives the fifth request message or the sixth request message, the first functional entity may determine whether the identification information of the target slice contained in the NSSAI belongs to allowed NSSAI or rejected NSSAI. If it is allowed NSSAI, the UE uses the slice to establish a new PDU session; if it belongs to rejected NSSAI, the slice-based network selection operation is directly triggered.

[0179] Optionally, when the first functional entity receives the fifth request message, the first functional entity may further reply to the upper layer. For example, when the identification information of the target slice contained in the NSSAI belongs to allowed NSSAI, the reply message may include the request ID and the newly created PDU session identifier; when the identification information of the target slice contained in the NSSAI belongs to rejected NSSAI, the reply message (i.e., the sixth response message) may be based on the success or failure of the slice network selection request, and carry the request ID.

[0180] Optionally, when the first functional entity receives the sixth request message, the first functional entity may further reply to the second layer of the terminal; for example, when the identification information of the target slice contained in the NSSAI belongs to the allowed NSSAI, the reply message may include the request ID and the newly created PDU session identifier; when the identification information of the target slice contained in the NSSAI belongs to the rejected NSSAI, the reply message (i.e., the fifth response message) may be based on the success or failure of the slice network selection request, and carry the request ID. After receiving the reply message to the sixth request message, the second functional entity may return a response message to the fourth request (i.e., the seventh response message) to the upper layer.

[0181] Optionally, the first functional entity is a non-access layer, the upper layer is an application layer, and the second functional entity is a terminal routing policy layer.

[0182] Reference Figure 5, the embodiment of the present application also provides a transmission processing method, such as Figure 5 As shown, the transmission processing method includes:

[0183] Step 501: The upper layer of the terminal sends a fourth request message to the second functional entity of the terminal, where the fourth request message includes network slice selection auxiliary information NSSAI, where the NSSAI includes a slice identifier of at least one target slice, and the fourth request message is used to request policy matching for the target application of the upper layer.

[0184] Optionally, after the upper layer sends the fourth request message to the second functional entity, the method further includes:

[0185] In the case where the policy matching fails, the upper layer receives a fourth response message from the second functional entity, where the fourth response message is used to indicate the policy matching failure;

[0186] The upper layer sends a fifth request message to the first functional entity of the terminal based on the fourth response message, and the fifth request message is used to request triggering a slice-based network selection operation, and the fifth request message includes the NSSAI.

[0187] Optionally, after the upper layer sends a fifth request message to the first functional entity based on the fourth response message, the method further includes:

[0188] The upper layer receives a seventh response message from the first functional entity, where the seventh response message is used to indicate success or failure of slice-based network selection.

[0189] Optionally, after the upper layer sends the fourth request message to the second functional entity, the method further includes:

[0190] The upper layer receives a sixth response message from the second functional entity, where the sixth response message is used to indicate a result of policy matching.

[0191] Optionally, the first functional entity of the terminal is a non-access layer, the upper layer is an application layer, and the second functional entity is a terminal routing policy layer.

[0192] Reference Figure 6 , the embodiment of the present application also provides a network selection processing method, such as Figure 6 As shown, the network selection processing method includes:

[0193] Step 601: A first functional entity of a terminal receives a target message, where the target message is used to trigger a slice-based network selection operation.

[0194] Step 602: When a preset condition is met, the first functional entity performs a slice-based network selection operation according to the target message;

[0195] The target message includes any of the following:

[0196] A second response message sent by the second functional entity of the terminal, wherein the second response message is used to indicate that an upper layer target application of the terminal does not match a non-default rule;

[0197] A first request message sent by an upper layer of the terminal, the first request message includes network slice selection auxiliary information NSSAI, the NSSAI includes a slice identifier of at least one target slice, and the slice identifier of the target slice belongs to a rejected NSSAI;

[0198] A third response message sent by the network side device, wherein the third response message is used to indicate that the slice identifier of the target slice included in the registered NSSAI belongs to the rejected NSSAI;

[0199] A fifth request message sent by an upper layer of the terminal, wherein the fifth request message is used to trigger a slice-based network selection operation;

[0200] The sixth request message sent by the second functional entity is used to trigger a slice-based network selection operation.

[0201] Optionally, the first functional entity performing a slice-based network selection operation according to the target message includes:

[0202] When a preset condition is met, the first functional entity performs a slice-based network selection operation according to the target message;

[0203] The preset condition includes at least one of the following:

[0204] The terminal supports the network selection feature based on slicing;

[0205] The terminal stores information on the association of slices with applicable networks;

[0206] The terminal is in automatic network selection mode;

[0207] The terminal is in non-emergency service;

[0208] The application being used by the terminal allows network interruption.

[0209] Optionally, the first functional entity is a non-access layer, the upper layer is an application layer, and the second functional entity is a terminal routing policy layer.

[0210] The transmission processing method provided in the embodiment of the present application can be executed by a transmission processing device. In the embodiment of the present application, the transmission processing device provided in the embodiment of the present application is described by taking the transmission processing method executed by the transmission processing device as an example.

[0211] Reference Figure 7 , the embodiment of the present application also provides a transmission processing device, such as Figure 7 As shown, the transmission processing device 700 includes:

[0212] The first receiving module 701 is used to receive a first request message from an upper layer of the terminal, where the first request message includes network slice selection auxiliary information NSSAI, where the NSSAI includes a slice identifier of at least one target slice, and the first request message is used to request transmission of application data of the target application of the upper layer on a protocol data unit PDU session established by the target slice;

[0213] The first sending module 702 is configured to send a first response message to the upper layer.

[0214] Optionally, the transmission processing device 700 further includes a generation module, wherein:

[0215] The first sending module 702 is further configured to send a second request message to a second functional entity of the terminal when the slice identifier of the target slice allows NSSAI, wherein the second request message includes the NSSAI, and the second request message is used to request policy matching for the target application;

[0216] The first receiving module 701 is further used to receive a second response message from the second functional entity, where the second response message is used to indicate whether the target application matches a non-default rule;

[0217] The generating module is used to generate the first response message based on the second response message.

[0218] Optionally, the transmission processing device 700 further includes:

[0219] The third execution module is used to perform a slice-based network selection operation when the second response message indicates that the target application does not match a non-default rule.

[0220] Optionally, the third execution module is specifically used to perform a slice-based network selection operation when the second response message indicates that the target application does not match a non-default rule and a preset condition is met;

[0221] The preset condition includes at least one of the following:

[0222] The terminal supports the network selection feature based on slicing;

[0223] The terminal stores information on the association of slices with applicable networks;

[0224] The terminal is in automatic network selection mode;

[0225] The terminal is in non-emergency service;

[0226] The application being used by the terminal allows network interruption.

[0227] Optionally, when the target application does not match a non-default rule, the second response message includes a first failure reason, where the first failure reason is used to indicate that the target application does not match a non-default rule.

[0228] Optionally, the transmission processing device 700 further includes:

[0229] A generation module is used to generate the first response message by the first functional entity when the slice identifier of the target slice belongs to the rejected NSSAI, and the first response message is used to indicate the rejection of the transmission of the application data of the upper layer.

[0230] Optionally, the transmission processing device 700 further includes:

[0231] The third execution module is used to perform a slice-based network selection operation when the slice identifier of the target slice belongs to a rejected NSSAI.

[0232] Optionally, the third execution module is specifically configured to perform a slice-based network selection operation when the slice identifier of the target slice belongs to a rejected NSSAI and a preset condition is met;

[0233] The preset condition includes at least one of the following:

[0234] The terminal supports the network selection feature based on slicing;

[0235] The terminal stores information on the association of slices with applicable networks;

[0236] The terminal is in automatic network selection mode;

[0237] The terminal is in non-emergency service;

[0238] The application being used by the terminal allows network interruption.

[0239] Optionally, the first sending module 702 is further used to send a third request message to the network side device, where the third request message is used to register the NSSAI;

[0240] The first receiving module 701 is also used to receive a third response message from a network side device, and the third response message is used to indicate that the slice identifier of the target slice belongs to allowed NSSAI or rejected NSSAI.

[0241] Optionally, when the target application does not match a non-default rule or the slice identifier of the target slice belongs to a rejected NSSAI, the first response message includes at least one of a second failure cause and target time information, and the target time information is used to indicate the waiting time for the upper layer to resend the first request message.

[0242] Reference Figure 8 , the embodiment of the present application also provides a transmission processing device, such as Figure 8 As shown, the transmission processing device 800 includes:

[0243] The second receiving module 801 is used to receive a second request message from the first functional entity of the terminal, where the second request message includes the NSSAI, and the second request message is used to request policy matching for an upper layer target application of the terminal;

[0244] The second sending module 802 is used to send a second response message to the first functional entity, where the second response message is used to indicate whether the target application matches a non-default rule.

[0245] Optionally, when the target application does not match a non-default rule, the second response message includes a first failure reason, where the first failure reason is used to indicate that the target application does not match a non-default rule.

[0246] Reference Fig. 9 , the embodiment of the present application also provides a transmission processing device, such as Fig. 9 As shown, the transmission processing device 900 includes:

[0247] The third receiving module 901 is used to receive a fourth request message from an upper layer of the terminal, where the fourth request message includes network slice selection auxiliary information NSSAI, where the NSSAI includes a slice identifier of at least one target slice, and the fourth request message is used to request policy matching for a target application of the upper layer;

[0248] The first execution module 902 is used to execute the target operation when the policy matching fails;

[0249] The target operation includes any of the following:

[0250] Sending a fourth response message to the upper layer, where the fourth response message is used to indicate that the policy match fails, and the fourth response message is used to trigger the upper layer to send a fifth request message to the first functional entity of the terminal, where the fifth request message is used to trigger a slice-based network selection operation;

[0251] A sixth request message is sent to the first functional entity of the terminal, where the sixth request message is used to trigger a slice-based network selection operation.

[0252] Optionally, the policy matching failure condition includes at least one of the following:

[0253] Matches the default rule;

[0254] A non-default rule is matched, and the traffic descriptor of the non-default rule does not include a slice identifier, or the slice identifier in the traffic descriptor of the non-default rule is inconsistent with the slice identifier of the target slice.

[0255] Optionally, the fourth response message includes at least one of the first failure cause, the NSSAI and target time information, and the target time information is used to indicate the waiting time for the upper layer to resend the fourth request message.

[0256] Optionally, the transmission processing device further includes a third sending module, wherein:

[0257] The third receiving module 901 is further used to receive a fifth response message from the first functional entity, where the fifth response message is used to indicate success or failure of slice-based network selection;

[0258] The third sending module is used to send a sixth response message to the upper layer, the sixth response message is determined based on the fifth response message, and the sixth response message is used to indicate a result of policy matching.

[0259] Reference Fig.10 , the embodiment of the present application also provides a transmission processing device, such as Fig.10 As shown, the transmission processing device 1000 includes:

[0260] The fourth sending module 1001 is used to send a fourth request message to the second functional entity of the terminal, wherein the fourth request message includes network slice selection auxiliary information NSSAI, wherein the NSSAI includes a slice identifier of at least one target slice, and the fourth request message is used to request policy matching for an upper-layer target application of the terminal.

[0261] Optionally, the transmission processing device 1000 further includes:

[0262] A fourth receiving module, configured to receive a fourth response message from the second functional entity when the policy matching fails, wherein the fourth response message is used to indicate the policy matching failure;

[0263] The fourth sending module 1001 is also used to send a fifth request message to the first functional entity based on the fourth response message terminal, and the fifth request message is used to request triggering a slice-based network selection operation, and the fifth request message includes the NSSAI.

[0264] Optionally, the fourth receiving module is further used to receive a seventh response message from the first functional entity, where the seventh response message is used to indicate success or failure of slice-based network selection.

[0265] Optionally, the transmission processing device 1000 further includes:

[0266] The fourth receiving module is used to receive a sixth response message from the second functional entity, where the sixth response message is used to indicate a result of policy matching.

[0267] The network selection processing method provided in the embodiment of the present application can be executed by a network selection processing device. In the embodiment of the present application, the network selection processing device executing the network selection processing method is taken as an example to illustrate the network selection processing device provided in the embodiment of the present application.

[0268] Reference Fig.11 The embodiment of the present application also provides a network selection processing device, such as Fig.11 As shown, the network selection processing device 1100 includes:

[0269] A fifth receiving module 1101 is used to receive a target message, where the target message is used to trigger a slice-based network selection operation;

[0270] A second execution module 1102, configured to perform a slice-based network selection operation according to the target message;

[0271] The target message includes any of the following:

[0272] A second response message sent by the second functional entity of the terminal, wherein the second response message is used to indicate that an upper layer target application of the terminal does not match a non-default rule;

[0273] A first request message sent by an upper layer of the terminal, the first request message includes network slice selection auxiliary information NSSAI, the NSSAI includes a slice identifier of at least one target slice, and the slice identifier of the target slice belongs to a rejected NSSAI;

[0274] A third response message sent by the network side device, wherein the third response message is used to indicate that the slice identifier of the target slice included in the registered NSSAI belongs to the rejected NSSAI;

[0275] A fifth request message sent by an upper layer of the terminal, wherein the fifth request message is used to trigger a slice-based network selection operation;

[0276] The sixth request message sent by the second functional entity is used to trigger a slice-based network selection operation.

[0277] Optionally, the second execution module 1102 is specifically configured to perform a slice-based network selection operation according to the target message when a preset condition is met;

[0278] The preset condition includes at least one of the following:

[0279] The terminal supports the network selection feature based on slicing;

[0280] The terminal stores information on the association of slices with applicable networks;

[0281] The terminal is in automatic network selection mode;

[0282] The terminal is in non-emergency service;

[0283] The application being used by the terminal allows network interruption.

[0284] The transmission processing device or network selection processing device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or it can be other devices other than a terminal. Exemplarily, the terminal can include but is not limited to the types of terminals 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.

[0285] The transmission processing device or network selection processing device provided in the embodiment of the present application can achieve Figures 2 to 6 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.

[0286] like Fig.12 As shown, an embodiment of the present application also provides a communication device 1200, including a processor 1201 and a memory 1202, and the memory 1202 stores a program or instruction that can be executed on the processor 1201. When the program or instruction is executed by the processor 1201, the various steps of the above-mentioned transmission processing method or network selection processing method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0287] The embodiment of the present application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the following Figures 2 to 6 The steps in the method embodiment shown. This terminal embodiment corresponds to the above-mentioned terminal side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, Fig.13 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0288] The terminal 1300 includes but is not limited to: a radio frequency unit 1301, a network module 1302, an audio output unit 1303, an input unit 1304, a sensor 1305, a display unit 1306, a user input unit 1307, an interface unit 1308, a memory 1309 and at least some of the components of a processor 1310.

[0289] Those skilled in the art will appreciate that the terminal 1300 may also include a power source (such as a battery) for supplying power to each component, and the power source may be logically connected to the processor 1310 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Fig.13 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0290] It should be understood that in the embodiment of the present application, the input unit 1304 may include a graphics processing unit (GPU) 13041 and a microphone 13042, and the graphics processor 13041 processes the image data of the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the image capture mode. The display unit 1306 may include a display panel 13061, and the display panel 13061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1307 includes a touch panel 13071 and at least one of other input devices 13072. The touch panel 13071 is also called a touch screen. The touch panel 13071 may include two parts: a touch detection device and a touch controller. Other input devices 13072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0291] In the embodiment of the present application, after receiving downlink data from the network side device, the RF unit 1301 can transmit the data to the processor 1310 for processing; in addition, the RF unit 1301 can send uplink data to the network side device. Generally, the RF unit 1301 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0292] The memory 1309 can be used to store software programs or instructions and various data. The memory 1309 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 1309 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DRRAM). The memory 1309 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0293] The processor 1310 may include one or more processing units; optionally, the processor 1310 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 1310.

[0294] The processor 1310 is configured to receive a first request message from an upper layer of the terminal, where the first request message includes network slice selection auxiliary information NSSAI, where the NSSAI includes a slice identifier of at least one target slice, and the first request message is used to request transmission of application data of a target application of the upper layer on a protocol data unit PDU session established by the target slice; and send a first response message to the upper layer;

[0295] Alternatively, the processor 1310 is configured to receive a second request message from a first functional entity of the terminal, where the second request message includes the NSSAI, and the second request message is used to request policy matching for an upper-layer target application of the terminal; a second sending module is configured to send a second response message to the first functional entity, where the second response message is used to indicate whether the target application matches a non-default rule;

[0296] Alternatively, the processor 1310 is configured to receive a fourth request message from an upper layer of the terminal, the fourth request message including network slice selection auxiliary information NSSAI, the NSSAI including a slice identifier of at least one target slice, and the fourth request message is used to request policy matching for a target application of the upper layer; if the policy matching fails, perform a target operation; wherein the target operation includes any one of the following: sending a fourth response message to the upper layer, the fourth response message is used to indicate a policy matching failure, and the fourth response message is used to trigger the upper layer to send a fifth request message to the first functional entity of the terminal, the fifth request message is used to trigger a slice-based network selection operation; sending a sixth request message to the first functional entity of the terminal, the sixth request message is used to trigger a slice-based network selection operation;

[0297] Alternatively, the processor 1310 is configured to send a fourth request message to the second functional entity of the terminal, where the fourth request message includes network slice selection auxiliary information NSSAI, where the NSSAI includes a slice identifier of at least one target slice, and the fourth request message is used to request policy matching for an upper layer target application of the terminal;

[0298] Alternatively, the processor 1310 is configured to receive a target message, where the target message is used to trigger a slice-based network selection operation; and perform a slice-based network selection operation according to the target message;

[0299] The target message includes any of the following:

[0300] A second response message sent by the second functional entity of the terminal, wherein the second response message is used to indicate that an upper layer target application of the terminal does not match a non-default rule;

[0301] A first request message sent by an upper layer of the terminal, the first request message includes network slice selection auxiliary information NSSAI, the NSSAI includes a slice identifier of at least one target slice, and the slice identifier of the target slice belongs to a rejected NSSAI;

[0302] A third response message sent by the network side device, wherein the third response message is used to indicate that the slice identifier of the target slice included in the registered NSSAI belongs to the rejected NSSAI;

[0303] A fifth request message sent by an upper layer of the terminal, wherein the fifth request message is used to trigger a slice-based network selection operation;

[0304] The sixth request message sent by the second functional entity is used to trigger a slice-based network selection operation.

[0305] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effect. To avoid repetition, it will not be repeated here.

[0306] The embodiment of the present application also provides a network side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the following Figures 2 to 6 The steps of the method embodiment shown. This network side device embodiment corresponds to the above network side device method embodiment, and each implementation process and implementation mode of the above method embodiment can be applied to this network side device embodiment and can achieve the same technical effect.

[0307] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned transmission processing method or network selection processing method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0308] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0309] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned transmission processing method or network selection processing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0310] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0311] The embodiments of the present application further provide a computer program / program product, which is stored in a storage medium, and is executed by at least one processor to implement the various processes of the above-mentioned transmission processing method or network selection processing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0312] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the embodiment of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0313] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general hardware platform, and of course, can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, disk, CD, etc.), including several instructions to enable a terminal or a network-side device to execute the methods described in each embodiment of the present application.

[0314] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of the present application and the scope of protection of the claims, and these implementation methods are all within the protection of the present application.

Claims

1. A transmission processing method, characterized in that: include: A first functional entity of the terminal receives a first request message from an upper layer of the terminal, where the first request message includes network slice selection assistance information NSSAI, where the NSSAI includes a slice identifier of at least one target slice, and the first request message is used to request transmission of application data of a target application of the upper layer on a protocol data unit PDU session established by the target slice; The first functional entity sends a first response message to the upper layer.

2. The method according to claim 1, characterized in that After the first functional entity receives the first request message from the upper layer, the method further includes: In a case where the slice identifier of the target slice belongs to allowing NSSAI, the first functional entity sends a second request message to a second functional entity of the terminal, where the second request message includes the NSSAI, and the second request message is used to request policy matching for the target application; The first functional entity receives a second response message from the second functional entity, where the second response message is used to indicate whether the target application matches a non-default rule; The first functional entity generates the first response message based on the second response message.

3. The method according to claim 2, characterized in that In a case where the second response message indicates that the target application does not match a non-default rule, after the first functional entity receives the second response message from the second functional entity, the method further includes: The first functional entity performs a slice-based network selection operation.

4. The method according to claim 2, characterized in that: In a case where the target application does not match a non-default rule, the second response message includes a first failure reason, where the first failure reason is used to indicate that the target application does not match a non-default rule.

5. The method according to claim 1, characterized in that After the first functional entity receives the first request message from the upper layer, the method further includes: In the case that the slice identifier of the target slice belongs to rejecting NSSAI, the first functional entity generates the first response message, and the first response message is used to indicate the rejection of the transmission of the application data of the upper layer.

6. The method according to claim 5, characterized in that In a case where the slice identifier of the target slice belongs to a rejected NSSAI, the method further includes: The first functional entity performs a slice-based network selection operation.

7. The method according to claim 3 or 6, characterized in that: The first functional entity performing a slice-based network selection operation includes: When a preset condition is met, the first functional entity performs a slice-based network selection operation; The preset condition includes at least one of the following: The terminal supports the network selection feature based on slicing; The terminal stores information on the association of slices with applicable networks; The terminal is in automatic network selection mode; The terminal is in non-emergency service; The application being used by the terminal allows network interruption.

8. The method according to any one of claims 1 to 7, characterized in that: In a case where the slice identifier of the target slice belongs to configuring NSSAI, the method further includes: The first functional entity sends a third request message to the network side device, where the third request message is used to register the NSSAI; The first functional entity receives a third response message from the network side device, and the third response message is used to indicate that the slice identifier of the target slice belongs to allowed NSSAI or rejected NSSAI.

9. The method according to any one of claims 1 to 8, characterized in that: In the case that the target application does not match a non-default rule or the slice identifier of the target slice belongs to a rejected NSSAI, the first response message includes at least one of a second failure cause and target time information, the target time information is used to indicate the waiting time for the upper layer to resend the first request message, and the second failure cause is used to indicate that the slice identifier of the target slice belongs to a rejected NSSAI or that the target application does not match a non-default rule.

10. The method according to any one of claims 1 to 9, characterized in that: The first functional entity is a non-access layer, and the upper layer is an application layer.

11. A transmission processing method, characterized in that: include: The second functional entity of the terminal receives a second request message from the first functional entity of the terminal, where the second request message includes the NSSAI, and the second request message is used to request policy matching for a target application at an upper layer of the terminal; The second functional entity sends a second response message to the first functional entity, where the second response message is used to indicate whether the target application matches a non-default rule.

12. The method according to claim 11, characterized in that In a case where the target application does not match a non-default rule, the second response message includes a first failure reason, where the first failure reason is used to indicate that the target application does not match a non-default rule.

13. The method according to claim 11 or 12, characterized in that: The first functional entity is a non-access layer, the upper layer is an application layer, and the second functional entity is a terminal routing policy layer.

14. A transmission processing method, characterized in that: include: The second functional entity of the terminal receives a fourth request message from an upper layer of the terminal, where the fourth request message includes network slice selection auxiliary information NSSAI, where the NSSAI includes a slice identifier of at least one target slice, and the fourth request message is used to request policy matching for a target application of the upper layer; In case the policy matching fails, the second functional entity performs the target operation; The target operation includes any of the following: Sending a fourth response message to the upper layer, where the fourth response message is used to indicate that the policy match fails, and the fourth response message is used to trigger the upper layer to send a fifth request message to the first functional entity of the terminal, where the fifth request message is used to trigger a slice-based network selection operation; A sixth request message is sent to the first functional entity of the terminal, where the sixth request message is used to trigger a slice-based network selection operation.

15. The method according to claim 14, characterized in that The conditions for the policy matching failure include at least one of the following: Matches the default rule; A non-default rule is matched, and the traffic descriptor of the non-default rule does not include a slice identifier, or the slice identifier in the traffic descriptor of the non-default rule is inconsistent with the slice identifier of the target slice.

16. The method according to claim 14 or 15, characterized in that The fourth response message includes at least one of the first failure reason, the NSSAI and target time information, where the target time information is used to indicate a waiting time for the upper layer to resend the fourth request message.

17. The method according to claim 14 or 15, characterized in that After the second functional entity sends the fifth request message to the first functional entity, the method further includes: The second functional entity receives a fifth response message from the first functional entity, where the fifth response message is used to indicate success or failure of slice-based network selection; The second functional entity sends a sixth response message to the upper layer, where the sixth response message is determined based on the fifth response message and is used to indicate a result of policy matching.

18. The method according to any one of claims 14 to 17, characterized in that The first functional entity is a non-access layer, the upper layer is an application layer, and the second functional entity is a terminal routing policy layer.

19. A transmission processing method, characterized in that: include: The upper layer of the terminal sends a fourth request message to the second functional entity of the terminal, and the fourth request message includes network slice selection auxiliary information NSSAI, and the NSSAI includes a slice identifier of at least one target slice, and the fourth request message is used to request policy matching for the target application of the upper layer.

20. The method according to claim 19, characterized in that After the upper layer sends the fourth request message to the second functional entity, the method further includes: In the case where the policy matching fails, the upper layer receives a fourth response message from the second functional entity, where the fourth response message is used to indicate the policy matching failure; The upper layer sends a fifth request message to the first functional entity of the terminal based on the fourth response message, and the fifth request message is used to request triggering a slice-based network selection operation, and the fifth request message includes the NSSAI.

21. The method according to claim 20, characterized in that After the upper layer sends a fifth request message to the first functional entity based on the fourth response message, the method further includes: The upper layer receives a seventh response message from the first functional entity, where the seventh response message is used to indicate success or failure of slice-based network selection.

22. The method according to claim 19, characterized in that After the upper layer sends the fourth request message to the second functional entity, the method further includes: The upper layer receives a sixth response message from the second functional entity, where the sixth response message is used to indicate a result of policy matching.

23. The method according to any one of claims 19 to 22, characterized in that The first functional entity of the terminal is a non-access layer, the upper layer is an application layer, and the second functional entity is a terminal routing policy layer.

24. A network selection processing method, characterized in that: include: The first functional entity of the terminal receives a target message, where the target message is used to trigger execution of a slice-based network selection operation; The first functional entity performs a slice-based network selection operation according to the target message; The target message includes any of the following: A second response message sent by the second functional entity of the terminal, wherein the second response message is used to indicate that an upper layer target application of the terminal does not match a non-default rule; A first request message sent by an upper layer of the terminal, the first request message includes network slice selection auxiliary information NSSAI, the NSSAI includes a slice identifier of at least one target slice, and the slice identifier of the target slice belongs to a rejected NSSAI; A third response message sent by the network side device, wherein the third response message is used to indicate that the slice identifier of the target slice included in the registered NSSAI belongs to the rejected NSSAI; A fifth request message sent by an upper layer of the terminal, wherein the fifth request message is used to trigger a slice-based network selection operation; The sixth request message sent by the second functional entity is used to trigger a slice-based network selection operation.

25. The method according to claim 24, characterized in that The first functional entity performing a slice-based network selection operation according to the target message includes: When a preset condition is met, the first functional entity performs a slice-based network selection operation according to the target message; The preset condition includes at least one of the following: The terminal supports the network selection feature based on slicing; The terminal stores information on the association of slices with applicable networks; The terminal is in automatic network selection mode; The terminal is in non-emergency service; The application being used by the terminal allows network interruption.

26. The method according to claim 24 or 25, characterized in that The first functional entity is a non-access layer, the upper layer is an application layer, and the second functional entity is a terminal routing policy layer.

27. A transmission processing device, characterized in that: include: A first receiving module, configured to receive a first request message from an upper layer of the terminal, where the first request message includes network slice selection auxiliary information NSSAI, where the NSSAI includes a slice identifier of at least one target slice, and the first request message is used to request transmission of application data of a target application of the upper layer on a protocol data unit PDU session established by the target slice; The first sending module is used to send a first response message to the upper layer.

28. A transmission processing device, characterized in that: include: A second receiving module, configured to receive a second request message from the first functional entity of the terminal, wherein the second request message includes the NSSAI, and the second request message is used to request policy matching for an upper layer target application of the terminal; The second sending module is used to send a second response message to the first functional entity, where the second response message is used to indicate whether the target application matches a non-default rule.

29. A transmission processing device, characterized in that: include: A third receiving module is configured to receive a fourth request message from an upper layer of the terminal, where the fourth request message includes network slice selection auxiliary information NSSAI, where the NSSAI includes a slice identifier of at least one target slice, and the fourth request message is used to request policy matching for a target application of the upper layer; A first execution module, used for executing a target operation when a policy match fails; The target operation includes any of the following: Sending a fourth response message to the upper layer, where the fourth response message is used to indicate that the policy match fails, and the fourth response message is used to trigger the upper layer to send a fifth request message to the first functional entity of the terminal, where the fifth request message is used to trigger a slice-based network selection operation; A sixth request message is sent to the first functional entity of the terminal, where the sixth request message is used to trigger a slice-based network selection operation.

30. A transmission processing device, characterized in that: include: The fourth sending module is used to send a fourth request message to the second functional entity of the terminal, wherein the fourth request message includes network slice selection auxiliary information NSSAI, the NSSAI includes a slice identifier of at least one target slice, and the fourth request message is used to request policy matching for the upper-layer target application of the terminal.

31. A network selection processing device, characterized in that: include: A fifth receiving module, used to receive a target message, where the target message is used to trigger a slice-based network selection operation; A second execution module, used to perform a slice-based network selection operation according to the target message; The target message includes any of the following: A second response message sent by the second functional entity of the terminal, wherein the second response message is used to indicate that an upper layer target application of the terminal does not match a non-default rule; A first request message sent by an upper layer of the terminal, the first request message includes network slice selection auxiliary information NSSAI, the NSSAI includes a slice identifier of at least one target slice, and the slice identifier of the target slice belongs to a rejected NSSAI; A third response message sent by the network side device, wherein the third response message is used to indicate that the slice identifier of the target slice included in the registered NSSAI belongs to the rejected NSSAI; A fifth request message sent by an upper layer of the terminal, wherein the fifth request message is used to trigger a slice-based network selection operation; The sixth request message sent by the second functional entity is used to trigger a slice-based network selection operation.

32. A terminal, characterized in that: It includes a processor and a memory, the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, it implements the steps of the transmission processing method as described in any one of claims 1 to 23, or implements the steps of the network selection processing method as described in any one of claims 24 to 26.

33. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, it implements the steps of the transmission processing method as described in any one of claims 1 to 23, or implements the steps of the network selection processing method as described in any one of claims 24 to 26.

Images