Method, system and device for acquiring and transmitting slice associated information

Abstract

The invention discloses a slice associated information acquisition and transmission method, system and device, and belongs to the technical field of communication, the slice associated information acquisition method of the embodiment of the invention comprises the steps that a terminal acquires first information, the first information is used for indicating an association relationship between a target object and a slice, and the first information is used for indicating the association relationship between the target object and the slice; the target object comprises at least one of a target application APP and a target service, the first information is used for preferentially using a slice associated with the first object when the terminal uses the first object, and the target object comprises the first object.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a method, system and device for acquiring and transmitting slice association information. Background Art

[0002] The fifth generation (5 th In the 5G (5th Generation) communication 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 public land mobile network (PLMN) and include at least two parts: the access network and the core network. Such a combination is called a slice.

[0003] In the related art, when a user equipment (UE) uses an application (APP) or service (Service), it will use a slice (Slice), but when the visited public land mobile network (VPLMN) cannot provide the communication service of the APP / service, the home network (HPLMN) is required to provide the priority of VPLMN network selection. The UE selects a suitable VPLMN to reside in based on the network priority information related to the slice, registers the slice and obtains the service.

[0004] However, some Slices can only provide services for specific APPs or Services. There may be a situation where the slice selected by the UE cannot serve the APP or Service used by the UE. At this time, the UE cannot accurately select the slice that can serve the APP or Service used by the UE. Summary of the invention

[0005] The embodiments of the present application provide a method, system and device for obtaining and transmitting slice association information. A terminal can obtain association information between a Slice and an APP or Service. Through the association information, the terminal can know which Slice or Slices are suitable for the APP or Service specified by the service. In this way, when the terminal uses a certain APP or Service, it can select a suitable Slice for the APP or Service based on the association information.

[0006] In a first aspect, a method for obtaining slice association information is provided, the method comprising:

[0007] The terminal obtains first information, where the first information is used to indicate an association relationship between a target object and a slice, wherein the target object includes at least one of a target application APP and a target service, and the first information is used to give priority to using the slice associated with the first object when the terminal uses the first object, and the target object includes the first object.

[0008] In a second aspect, a method for transmitting slice association information is provided, the method comprising:

[0009] The first network side device sends first information to the terminal, where the first information is used to indicate the association relationship between the target object and the slice, and the target object includes at least one of a target application APP and a target service.

[0010] In a third aspect, a method for transmitting slice association information is provided, the method comprising:

[0011] The second network side device sends third information to the terminal, where the third information is information obtained by encapsulating the first information in a roaming guidance SOR payload, where the first information is used to indicate an association relationship between a target object and a slice, where the target object includes at least one of a target application APP and a target service;

[0012] or,

[0013] The second network side device sends second information to the first network side device, where the second information is used to indicate an association relationship between at least one application or at least one service of the terminal and their respectively associated slices.

[0014] In a fourth aspect, a method for transmitting slice association information is provided, the method comprising:

[0015] The third network side device sends the first information or the updated first information to the second network side device, wherein the first information is used to indicate the association relationship between the target object and the slice, and the target object includes at least one of a target application APP and a target service.

[0016] In a fifth aspect, a system for transmitting slice association information is provided, including:

[0017] terminal;

[0018] A first network side device is used to send first information to the terminal; or,

[0019] A second network side device, configured to send third information to the terminal, where the third information includes the first information encapsulated in a roaming guidance SOR payload;

[0020] Among them, the first information is used to indicate the association relationship between the target object and the slice, the target object includes at least one of a target application APP and a target service, the first information is used to give priority to using the slice associated with the first object when the terminal uses the first object, and the target object includes the first object.

[0021] In a sixth aspect, a device for acquiring slice association information is provided, including:

[0022] The first acquisition module is used to acquire first information, where the first information is used to indicate an association relationship between a target object and a slice, wherein the target object includes at least one of a target application APP and a target service, and the first information is used to give priority to using the slice associated with the first object when the terminal uses the first object, and the target object includes the first object.

[0023] In a seventh aspect, a device for transmitting slice association information is provided, including:

[0024] The first sending module is used to send first information to the terminal, where the first information is used to indicate the association relationship between the target object and the slice, and the target object includes at least one of a target application APP and a target service.

[0025] In an eighth aspect, a device for transmitting slice association information is provided, including:

[0026] a second sending module, configured to send third information to the terminal, where the third information is information obtained by encapsulating the first information in a roaming guidance SOR payload, where the first information is used to indicate an association relationship between a target object and a slice, where the target object includes at least one of a target application APP and a target service;

[0027] or,

[0028] The third sending module is used to send second information to the first network side device, where the second information is used to indicate the association relationship between at least one application or at least one service of the terminal and their respectively associated slices.

[0029] In a ninth aspect, a device for transmitting slice association information is provided, including:

[0030] The fourth sending module is used to send the first information or the updated first information to the second network side device, wherein the first information is used to indicate the association relationship between the target object and the slice, and the target object includes at least one of the target application APP and the target service.

[0031] In a tenth aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be executed on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0032] In the eleventh aspect, a terminal is provided, comprising a processor and a communication interface, wherein the communication interface is used to obtain first information, the first information being used to indicate an association relationship between a target object and a slice, wherein the target object includes at least one of a target application APP and a target service, and the first information being used to give priority to using the slice associated with the first object when the terminal uses the first object, and the target object includes the first object.

[0033] In a twelfth aspect, a network side device is provided, the network side device comprising a processor and a memory;

[0034] In the case where the network side device is a first network side device, 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 according to the second aspect are implemented;

[0035] In the case where the network side device is a second network side device, 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 according to the third aspect are implemented;

[0036] In the case where the network side device is a third network side device, 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 the fourth aspect are implemented.

[0037] In a thirteenth aspect, a network side device is provided, including a processor and a communication interface;

[0038] In the case where the network side device is a first network side device, the communication interface is used to send first information to the terminal, where the first information is used to indicate an association relationship between a target object and a slice, and the target object includes at least one of a target application APP and a target service.

[0039] In the case where the network side device is a second network side device, the communication interface is used to send third information to the terminal, and the third information is information obtained by encapsulating the first information in a roaming guidance SOR payload, and the first information is used to indicate the association relationship between the target object and the slice, wherein the target object includes at least one of a target application APP and a target service; or, the communication interface is used to send second information to the first network side device, and the second information is used to indicate the association relationship between at least one application or at least one service of the terminal and their respectively associated slices.

[0040] In the case where the network side device is a third network side device, the communication interface is used to send the first information or the updated first information to the second network side device, wherein the first information is used to indicate the association relationship between the target object and the slice, and the target object includes at least one of a target application APP and a target service.

[0041] 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 the first aspect, the second aspect, the third aspect, or the fourth aspect are implemented.

[0042] In the fifteenth aspect, a wireless communication system is provided, including: a terminal, a first network side device, a second network side device and a third network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect, the first network side device can be used to execute the steps of the method described in the second aspect, the second network side device can be used to execute the steps of the method described in the third aspect, and the third network side device can be used to execute the steps of the method described in the fourth aspect.

[0043] In the sixteenth 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 the first aspect, the second aspect, the third aspect, or the fourth aspect.

[0044] In the seventeenth 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 steps of the method described in the first aspect, the second aspect, the third aspect, or the fourth aspect.

[0045] In an embodiment of the present application, the terminal is able to obtain the association information between the target object and the slice, so that through the association information, the terminal can know which slice or slices are suitable for the application or service specified by the service, so that when the terminal uses a first object, it can select a suitable slice for the first object based on the association information, thereby improving the communication performance of the terminal when using the first object. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] Figure 1 is a schematic diagram of the structure of a wireless communication system to which the embodiments of the present application can be applied;

[0047] Figure 2 This is a flow chart of a method for obtaining slice association information provided by an embodiment of the present application;

[0048] Figure 3 This is one of the flowcharts of a method for transmitting slice association information provided in an embodiment of the present application;

[0049] Figure 4 This is a second flowchart of a method for transmitting slice association information provided in an embodiment of the present application;

[0050] Figure 5 This is a flowchart of a method for transmitting slice association information provided in an embodiment of the present application;

[0051] Figure 6a This is one of the interactive schematic diagrams of a system for transmitting slice association information provided in an embodiment of the present application;

[0052] Figure 6b This is the second interactive schematic diagram of a system for transmitting slice association information provided in an embodiment of the present application;

[0053] Figure 6c This is a third interactive schematic diagram of a system for transmitting slice association information provided in an embodiment of the present application;

[0054] Figure 6d This is a fourth interactive schematic diagram of a system for transmitting slice association information provided in an embodiment of the present application;

[0055] Figure 7 It is a structural schematic diagram of a device for obtaining slice association information provided by an embodiment of the present application;

[0056] Figure 8 This is one of the structural schematic diagrams of a device for transmitting slice association information provided in an embodiment of the present application;

[0057] Fig. 9 This is a second structural diagram of a device for transmitting slice association information provided in an embodiment of the present application;

[0058] Fig.10 This is a third structural diagram of a device for transmitting slice association information provided in an embodiment of the present application;

[0059] Fig.11 It is a structural diagram of a communication device provided in an embodiment of the present application;

[0060] Fig.12 is a schematic diagram of the structure of a terminal provided in an embodiment of the present application;

[0061] Fig.13 It is a structural diagram of a network side device provided in an embodiment of the present application;

[0062] Fig.14 It is a structural diagram of another network side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0063] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.

[0064] 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.

[0065] 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.

[0066] 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.

[0067] 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.

[0068] The core network device may include but is not limited to at least one of the following: core network node, core network function, location management function (Location Management Function, LMF), 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

[0069] (Local NEF, or L-NEF), Binding Support Function (BSF), 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 taken as an example for introduction, and the specific type of the core network device is not limited. It should be noted that in the embodiments of the present application, only the core network device in the NR system is taken as an example for introduction, and the specific type of the core network device is not limited.

[0070] In the related technology, in the registration process, the UE will send a registration request message to the network side, wherein the UE can encapsulate the requested slice (requested NSSAI) in the registration request message and report it to the network, where the UE will select the slice it wants to register (intend to register) for registration. If there is an allowed NSSAI (allowed NSSAI) or a configured NSSAI (configured NSSAI), the UE selects a subset thereof; if there is neither of the above, the default configured NSSAI (default configured NSSAI) is used; if there is no default configured NSSAI, the registration request message does not carry the requested NSSAI. Among them, NSSAI stands for Network Slice Selection Assistance Information.

[0071] The network side determines whether it can provide services for the requested S-NSSAI based on the UE's contract status and the current network conditions. If the requested S-NSSAI can be provided, the S-NSSAI is placed in the allowedNSSAI and replied to the UE; if the requested NSSAI cannot be provided, the S-NSSAI is placed in the rejectedNSSAI and replied to the UE. Optionally, if the UE indicates support for extended rejected NSSAI in the 5GMM capability IE (5GMM capability information element) in the registration request message, the network side will also place the slices that cannot be provided in the extended rejected NSSAI and reply to the UE, along with the corresponding rejection reason.

[0072] In the related art, when the UE uses a certain APP / service, it will use slices, but the current network VPLMN cannot provide it, and the HPLMN is required to provide the priority of VPLMN network selection. The UE selects a suitable VPLMN to reside on based on the network priority information related to the slice, registers the slice and obtains the service. This process can be called slice-based network selection. Specifically, the UE mainly includes the following three steps in the process of performing slice-based network selection:

[0073] 1) The UE determines which slice to use based on the APP / service;

[0074] 2) The UE selects a network VPLMN with a higher priority and can reside according to the network priority information related to the slice. It should be noted that in this step 2), if the UE has the network priority information related to the slice, it is directly selected. If not, it is necessary to obtain the network priority information related to the slice from the HPLMN;

[0075] 3) The UE executes the network selection process and uses the slice to access the VPLMN network.

[0076] For the above step 1), the relevant technology only supports the UE to request a certain slice. However, the slice selected by the UE may not be suitable for the APP / service used on the UE, which will cause the slice selected in step 1) to be inappropriate, and then cause the VPLMN selected in steps 2) and 3) to be unable to provide high-quality services for the APP / service. In other words, if the selected slice is inappropriate, it may cause the final selected network to not be the most suitable network for the APP / service.

[0077] In the embodiment of the present application, the slice applicable to the APP / service can be associated with the APP / service through the association information between the target object and the slice. In this way, when the terminal uses a certain APP / service, the slice applicable to the APP / service is selected based on the association information, and then, the network that matches the APP / service can be selected based on the slice.

[0078] For the convenience of description, the following terms in the embodiments of the present application are first explained:

[0079] 1) Slice association information can be used to indicate the association between a slice and an APP, or the association between a slice and a service.

[0080] Optionally, the association information may be joint information of the slice information and the target object information. For example, the first information may include identification information of a slice and identification information of at least one application associated with the slice.

[0081] In the embodiments of the present application, slice association information is generally referred to as APP / slice combinations information.

[0082] 2) The target object may include at least one APP or at least one service. For the sake of convenience, the APP and service in the first information are collectively referred to as target objects.

[0083] 3) The first network side device can be the terminal’s visited AMF.

[0084] 4) The second network side device may be the home network UDM of the terminal.

[0085] 5) The third network side device may be a roaming steering application server (Steering of Roaming application function, SOR-AF).

[0086] In combination with the accompanying drawings, the following detailed description will be given of the slice association information acquisition method, slice association information transmission method, slice association information transmission system, slice association information acquisition device, slice association information transmission device and related equipment provided in the embodiments of the present application through some embodiments and their application scenarios.

[0087] See also Figure 2 The present application embodiment provides a method for obtaining slice association information, the execution subject of which may be a terminal, and the terminal may be as follows Figure 1 The various types of terminals 11 listed in, or in addition to Figure 1 Terminals other than the terminal types listed in the illustrated embodiment are not specifically limited herein.

[0088] like Figure 2 As shown, the method for obtaining slice association information may include the following steps:

[0089] Step 201: The terminal obtains first information, where the first information is used to indicate an association relationship between a target object and a slice, wherein the target object includes at least one of a target application (APP) and a target service, and the first information is used to give priority to using the slice associated with the first object when the terminal uses the first object, and the target object includes the first object.

[0090] In an embodiment of the present application, a slice suitable for an APP / service can be associated with the APP / service through the association relationship between the target object and the slice. In this way, when a terminal uses a certain APP / service, a slice suitable for the APP / service is selected based on the association relationship. Furthermore, a network that meets the communication requirements of the APP / service can be selected based on the slice. For example, when a user uses application A to watch a 3D movie, a suitable slice can be selected based on the association information between application A and the slice.

[0091] As an optional implementation manner, the first information may include at least one of the following:

[0092] Identification information of one or more target objects, wherein the target object includes at least one of: APP information, target service information, such as APP identification, etc.;

[0093] One or more slice identifiers, such as Single Network Slice Selection Assistance Information (S-NSSAI), where each S-NSSAI contains a slice / service type (SST) and a slice differentiator (SD). Multiple S-NSSAIs are combined into NSSAI;

[0094] first association information, wherein the first association information corresponds to each of the target objects one by one, and the first association information indicates an association relationship between a corresponding object and at least one slice;

[0095] second association information, wherein the second association information corresponds to the slices one by one, and the second association information indicates an association relationship between a corresponding slice and at least one of the target objects;

[0096] Priority information indicating priorities of at least two slices associated with the same object in the target object.

[0097] It should be noted that the first association information, the second association information and the priority information may be implicit information, and at least one of the first association information, the second association information and the priority information may be represented by the coding structure of the first information.

[0098] For example, the encoding structure of the first information may be as shown in Table 1:

[0099] Table 1

[0100]

[0101]

[0102] As shown in Table 1 above, each APP may correspond to a list, and the slice information in the list includes one or more S-NSSAI information, where the S-NSSAI with the earlier code indicates that the slice has a higher priority when using the corresponding APP, and the S-NSSAI with the later code indicates that the slice has a lower priority when using the corresponding APP. That is, for a list corresponding to a certain APP, the first association information between the APP and at least one slice can be implicitly indicated, and according to the arrangement order of the S-NSSAI, the priority information of at least one slice associated with the APP can be implicitly indicated.

[0103] For another example, the encoding structure of the first information may be as shown in Table 2 below:

[0104] Table 2

[0105]

[0106] As shown in Table 2 above, each slice may correspond to a list, and the APP information list in the list contains one or more APP information. Among them, there may be no slice priority information in the second association information shown in Table 2 above. That is, for a list corresponding to a certain slice, the second association information of the slice and at least one APP may be implicitly indicated.

[0107] As an optional implementation manner, the target object includes at least one of the following:

[0108] The services contracted by the terminal;

[0109] APP installed on the terminal;

[0110] The APP that the terminal tends to use;

[0111] The services that the terminal tends to use;

[0112] an APP targeted by a first operation, wherein the first operation is a user operation received on the terminal;

[0113] The service to which the first operation is directed.

[0114] In one implementation, the terminal may obtain slices associated with all contracted services, or obtain slices associated with all installed apps.

[0115] In another implementation, the terminal may obtain slices associated with an APP or service that is preferred to be used, for example, when the terminal uses an APP, the slices associated with the APP are obtained.

[0116] In another embodiment, the terminal can obtain the slices associated with the APP or service operated by the user. For example, when the terminal uses a certain APP, the terminal outputs a prompt message "Do you want to obtain the slices associated with the APP?" If the user performs a confirmation operation, the terminal obtains the slices associated with the APP. At this time, the first operation may include the above-mentioned confirmation operation of the prompt information.

[0117] In some implementations, the terminal may actively request association information between the target object and the slice from the network side device.

[0118] In one implementation, the terminal may request first information from the AMF network element of the Visited Public Land Mobile Network (VPLMN), for example: the terminal sends a first request message to the AMF network element, and the first request message carries identification information of the target object for which association information with the slice needs to be obtained. Thereafter, the visited AMF network element may obtain second information from the UDM network element of the Home Public Land Mobile Network (HPLMN), and the second information may include slice association information of the default or all APPs or services, so that the visited AMF network element can determine the first information requested by the terminal.

[0119] It should be noted that, for the sake of convenience of explanation, in the embodiment of the present application, the AMF of the VPLMN is referred to as the visited AMF, and the UDM of the HPLMN is referred to as the home network UDM.

[0120] In another implementation, the terminal may send a third request message to the home network UDM through the visited network AMF, and the home network UDM determines the first information and then transparently transmits it to the terminal through the visited network AMF.

[0121] The identification information of the target object requested by the terminal may be carried in the request message. For example, when the target object is at least one APP, the framework of the identification information of the target object may be as shown in Table 3 below:

[0122] Table 3

[0123]

[0124]

[0125] The APP information in Table 3 above may be at least one of the APP's open science identity (OSID) and the APP ID.

[0126] Of course, the terminal may also reside on the HPLMN. In this case, the terminal may also send a first request message to the AMF network element, and the AMF network element sends a third request message to the home network UDM. After that, the home network UDM may provide the first information to the terminal according to the third request message. For the sake of convenience, in the embodiments of the present application, an example is usually taken that the terminal resides on the VPLMN, which is not specifically limited here.

[0127] In other implementations, the network side device can actively send the association information between the target object and the slice to the terminal. For example, when the slice associated with a service changes, the Steering of Roaming application function (SOR-AF) can trigger the transmission of the changed association information between the service and the slice to the terminal.

[0128] Optionally, the method further comprises:

[0129] When the terminal determines, based on the first information, that the slice associated with the target object has changed, the terminal updates the stored association information between the target object and the slice.

[0130] In this embodiment, the terminal can store the association relationship between the target object and the slice, and the stored association information can be updated. In this way, when the terminal uses a certain object, if the association relationship between the object and the slice has been stored, the terminal can directly use the slice associated with the object, thereby eliminating the need to repeatedly request the association relationship between the object and the slice from the network side. In addition, when the slice associated with the object changes, the network side can send updated association information to the terminal, and the terminal can update the stored information according to the updated association information.

[0131] As an optional implementation, the method further includes at least one of the following:

[0132] The terminal stores the first information in a first entity, wherein the first entity includes a Universal Subscriber Identity Module (USIM) or a Management Entity (ME);

[0133] When using the first object, the terminal preferentially uses a first slice, wherein the first slice is a slice with the highest priority associated with the first object.

[0134] In one embodiment, when the first information includes association information between the first object and at least two slices, the first slice is the slice with the highest priority; of course, the first information may also only include association information between the first object and one slice, in which case the first slice is the one slice.

[0135] Optionally, when using the first object, the terminal may request the slices associated with the first object and having a higher priority in the requested NSSAI.

[0136] In an optional implementation, the non-access stratum (NAS) of the terminal may also send the first information to the APP layer of the terminal.

[0137] In this way, the APP layer of the terminal can determine the associated slice based on the first information, and thus use the network corresponding to the slice for communication transmission.

[0138] As an optional implementation manner, the terminal obtains the first information, including at least one of the following:

[0139] The terminal obtains pre-configured first information;

[0140] The terminal receives an application layer message from an application server, where the application layer message includes the first information;

[0141] The terminal receives first information from a first network element, where the first network element includes an access and mobility management function AMF network element or a unified data management function UDM network element of a home network;

[0142] The terminal receives third information from a second network element, wherein the third information is information obtained by encapsulating the first information in a roaming guidance SOR payload, and the second network element includes a UDM network element of a home network.

[0143] In the first implementation, the terminal may pre-install some APPs before leaving the factory. In this case, the slices associated with each APP pre-installed in the terminal may be configured in a pre-configured manner. Optionally, the APP / slice combinations information configured by the APP pre-installed in the terminal may be stored in the USIM and / or ME (e.g., non-volatile memory).

[0144] (non-volatile memory)).

[0145] In this implementation, the preconfigured first information may be used to indicate the association between the APP pre-installed on the terminal and the slice, that is, the target APP may include the APP pre-installed on the terminal.

[0146] Of course, in another possible implementation, the preconfigured first information is used to indicate the association between the preset APP or preset service and the slice. In this way, after the subsequent terminal installs the preset APP or signs up for the preset service, when using the preset APP or signing up for the preset service, it gives priority to the slice associated with the preset APP or signing up for the preset service.

[0147] In the second implementation, when the terminal installs the APP, the terminal may request the AF (the server of the APP) for relevant APP / slice combinations information through the app layer (such as Http message), and the request message may include information such as APP ID, PLMNID, access type, etc.

[0148] Optionally, the target object may include the first APP served by the application server, that is, the terminal requests the slice association information of the first APP from the application server of the first APP through an application layer message.

[0149] The access type may be a first access type, which may specifically include at least one of 3GPP access, non-3GPP access, 3GPP and non-3GPP access, etc. The first access type is applicable to obtaining the first information, or to using the target APP or the target service. For example, the first access type may be an access type used by the terminal when using the APP subsequently.

[0150] On the network side, based on the fact that the network side device may only support a certain access type, at this time, the network side device may provide the first information to the terminal while supporting the first access type.

[0151] In a third implementation manner, the terminal receives first information from a first network element.

[0152] For example: the terminal receives the first information from the AMF network element. Prior to this, the AMF network element may receive the first request message from the terminal. The first request message is used to request the association information between the target object and the slice. Then, the AMF network element can query the second information of the terminal from the UDM. The second information is used to indicate the association relationship between at least one application or at least one service of the terminal and the slices associated with each other. For example, the second information is an APP / slice mapping list. In this way, the AMF network element can determine the first information based on the first request message and the second information. For example: the second information is used to indicate the association relationship between the slices associated with all APPs installed by the terminal and all services signed by the terminal, and the first request message is used to request the association information between the target APP and the slice. The AMF network element can determine the identifier of the target APP based on the first request message, and find the slice associated with the identifier of the target APP from the second information, thereby sending the association information between the target APP and the slice to the terminal.

[0153] It should be noted that the first information may be a subset of the second information, for example, the second information is an APP / slicemapping list, and the first information is an APP / slice combinations. In this case, the APP / slice combinations are a subset of the APP / slice mapping list. When the terminal does not request the association information of an APP, but the VPLMN AMF receives the association information of the APP, then optionally, the VPLMN AMF finally sends APP / slice combinations to the terminal, and the association information of the APP and the slice contained in the APP / slice combinations may be less than that in the APP / slice mapping list.

[0154] For another example, the terminal can receive the first information from the UDM network element. For example, when the terminal resides in the HPLMN, the first information is requested from the UDM network element in a manner similar to the above-mentioned method of requesting the first information from the AMF network element, which will not be repeated here.

[0155] In the fourth embodiment, the terminal receives the third information from the second network element, which can be: when the AMF network element can receive the first request message from the terminal, it sends the third request message to the UDM network element, and the UDM network element determines the first information based on the slices associated with all the APPs installed on the terminal and all the services signed, as well as the third request message, and encapsulates the first information in a roaming guidance (Steering of Roaming, SOR) payload, and then sends the SOR payload to the AMF network element, and the AMF network element forwards the SOR payload to the terminal, for example: the AMF network element encapsulates the SOR payload in a first response message, and the first response message can be a response message to the first request message, so that the UDM network element can transparently transmit the first information to the terminal through the AMF network element.

[0156] It should be noted that the above-mentioned UDM network element may not store the association information between all APPs installed on the terminal and all subscribed services and their respectively associated slices. At this time, the UDM network element can obtain the second information from the SOR-AF, which is not specifically limited here.

[0157] In addition, the terminal may actively initiate a request to obtain the first information.

[0158] As an optional implementation, the method further includes:

[0159] The terminal sends a first request message to the first network element, wherein the first request message is used to request the first information.

[0160] The first request message may reuse the registration request sent in the initial registration process and registration update process of the target APP in the related technology. Alternatively, the first request message may reuse the service request of the target service in the related technology. The first request message may indicate that the terminal wishes to obtain the APP / service or the APP / slice combinations information associated with the APP / service in the contract information. For example, obtain the association information of the specified APP and the slice, or obtain the association information of each APP and the slice in the contract information.

[0161] Optionally, the first request message may be an uplink (UL) NAS transport message.

[0162] Of course, the first request message may also be a newly added message, which is not specifically limited here.

[0163] In this implementation manner, the terminal actively requests the network-side device for the first information.

[0164] Optionally, the first request message carries at least one of the following:

[0165] identification information of the network where the terminal resides;

[0166] First indication information, where the first indication information indicates that the terminal supports a slice-based network selection function;

[0167] Target APP information, the target APP information including identification information of the APP that the terminal tends to use or install;

[0168] Target service information, the target service information including identification information of the service that the terminal tends to use or subscribe to;

[0169] a first access type, where the first access type is applicable to obtaining the first information, or to using the target APP or the target service;

[0170] Third indication information, where the third indication information indicates that the first request message is used to request the first information.

[0171] In one implementation, the network where the terminal resides may include an HPLMN and a VPLMN, and the identification information of the network may be a PLMN ID, etc. Thus, based on the identification information of the network where the terminal resides, it is possible to know from which network side device or devices the first information is obtained.

[0172] In one implementation, the first indication information may be an SbPS support indication, which indicates that the terminal supports a slice-based network selection function.

[0173] When the first request message carries the first indication information, it indicates that the terminal supports the slice-based network selection function. If the terminal does not support the slice-based network selection function, even if the network side device feeds back the association information between the target object and the slice to the terminal, the terminal uses the target object and the slice associated with the target object. It cannot select a network that meets the target object based on the slice.

[0174] Optionally, the AMF network element or UDM network element may feedback the association information between the target object and the slice based on the terminal request only when the first request message carries the first indication information. Otherwise, even if the AMF network element or UDM network element receives the request message from the terminal, it may not feedback the association information between the target object and the slice requested by the terminal.

[0175] In this way, when the terminal does not support the slice-based network selection function, the resource waste caused by transmitting the association information between the target object and the slice can be reduced.

[0176] In one implementation, when a terminal installs one or more APPs and a user prefers to use a certain APP (such as when the terminal starts a certain APP), the terminal may carry the identifiers of these APPs through a first request message to indicate to the network side device that the terminal needs to obtain the association information between these APPs and slices.

[0177] In one implementation, when a terminal signs up for one or more services and a user prefers to use a certain service, the terminal may carry the identifiers of these services through a first request message to indicate to the network side device that the terminal needs to obtain the association information between these services and slices.

[0178] In one implementation, the first request message may explicitly indicate, through third indication information, that the first request message is used to request the first information.

[0179] Of course, the first request message may not carry the third indication information, but may implicitly indicate that the first request message is used to request the first information through at least one of the first indication information, the target APP information and the target service information.

[0180] For example: when the first request message carries the first indication information and the target APP information, the AMF network element sends a third request message to the UDM network element, and the third request message carries the information in the first request message. The UDM network element can determine that the terminal supports the slice-based network selection function based on the first indication information. On this basis, the UDM network element determines whether the slice association information of the target APP is stored locally. If so, it determines the first information used to indicate the association relationship between the target APP and the slice, and encapsulates the first information in the SOR payload and transmits it to the terminal through the AMF network element.

[0181] It should be noted that before sending the first request message, the terminal can interact with the user and obtain authorization, that is, when the terminal obtains the user authorization information, it can use the AT command to control the function of the mobile station (MS) to interact with the identification information of the target object of the Global System for Mobile Communications (GSM) network service. For example: Only on the premise of obtaining user authorization can the first request message carry the APP information list that needs to request slice association information.

[0182] In an implementation manner, the first request message may also carry a first access type, that is, an access type applicable to obtaining the first information, or an access type applicable to using the target APP or the target service.

[0183] In this implementation, the network side device can provide the terminal with first information that complies with the first access type according to the first access type.

[0184] As an optional implementation manner, before the terminal receives the first information from the application server, the method further includes:

[0185] The terminal sends a second request message to the application server, wherein the second request message is used to request association information between a first APP and a slice, the target APP includes the first APP, and the application server is a server of the first APP.

[0186] The application server may be an application server of the first APP, such as AF.

[0187] Optionally, the second request message carries at least one of the following:

[0188] Identification information of the first APP;

[0189] identification information of the network where the terminal resides;

[0190] The first access type is applicable to obtaining the first information or using the first APP.

[0191] In one implementation, when a terminal installs or intends to use a certain APP, it can request APP / slicecombinations information related to the APP from the server of the APP through a second request message of the application layer (ie, the app layer (HTTP message)).

[0192] In this implementation, the terminal can actively request the association information between the APP and the slice from the application server through an application layer message.

[0193] It should be noted that, in another implementation, when the slice associated with the APP changes, the application server can also actively send the updated association information between the APP and the slice to the terminal where the APP is installed through an HTTP message.

[0194] In one implementation, for an APP pre-installed before the terminal leaves the factory, the association information between the pre-installed APP and the slice can be pre-configured; for an APP installed after leaving the factory, the association information between the APP and the slice can be obtained from the corresponding application server through an application layer message.

[0195] In an embodiment of the present application, the terminal is able to obtain the association information between the target object and the slice, so that through the association information, the terminal can know which slice or slices are suitable for the application or service specified by the service, so that when the terminal uses a first object, it can select a suitable slice for the first object based on the association information, thereby improving the communication performance of the terminal when using the first object.

[0196] See also Figure 3 , a method for transmitting slice association information provided in an embodiment of the present application, the execution subject of which may be a first network side device, and the first network side device may be an AMF network element.

[0197] like Figure 3 As shown, the method for transmitting slice association information may include the following steps:

[0198] Step 301: A first network-side device sends first information to a terminal, where the first information is used to indicate an association relationship between a target object and a slice, and the target object includes at least one of a target application APP and a target service.

[0199] It should be noted that if Figure 3 In the embodiment shown, the first information, the target object, the first network side device and the Figure 2 The first information, target object, and first network-side device in the illustrated method embodiment have the same meaning and function, which will not be described in detail herein.

[0200] As an optional implementation manner, before the first network side device sends the first information to the terminal, the method further includes:

[0201] The first network side device receives a first request message from the terminal, wherein the first request message is used to request the first information;

[0202] The first network side device obtains second information or third information from the second network side device, wherein the second information is used to indicate the association relationship between at least one application or at least one service of the terminal and their respectively associated slices, or the third information includes the first information encapsulated in the roaming guidance SOR payload.

[0203] In one implementation, when the first network side device obtains the second information from the second network side device, the first information is information determined by the first network side device based on the second information and the first request message. At this time, the first network side device sends the first information to the terminal, and the first network side device may carry the first information in a response message to the first request message.

[0204] In another implementation, when the first network side device obtains the third information from the second network side device, the first information is the association information between the application / service and the slice of the terminal determined by the second network side device. At this time, the first information is encapsulated in the SOR payload and transparently transmitted to the terminal through the first network side device. At this time, the first network side device sends the first information to the terminal, which can be that the first network side device receives the SOR payload from the second network side device, and encapsulates the SOR payload in a response message to the first request message to send to the terminal. At this time, since the first information is encapsulated in the SOR payload, the terminal can obtain the first information by performing security verification, decoding, and other operations on the SOR payload.

[0205] Optionally, the first request message carries at least one of the following:

[0206] identification information of the network where the terminal resides;

[0207] First indication information, where the first indication information indicates that the terminal supports a slice-based network selection function;

[0208] Target APP information, the target APP information including identification information of the APP that the terminal tends to use or install;

[0209] Target service information, the target service information including identification information of the service that the terminal tends to use or subscribe to;

[0210] a first access type, where the first access type is applicable to obtaining the first information, or to using the target APP or the target service;

[0211] Third indication information, where the third indication information indicates that the first request message is used to request the first information.

[0212] Among them, the information carried in the first request message is similar to Figure 2 The meaning and function of each piece of information carried in the first request message in the illustrated method embodiment are the same and will not be described again here.

[0213] In one implementation, the first network side device obtains the second information from the second network side device, including:

[0214] The first network side device sends a third request message to the second network side device, wherein the third request message is used to request to obtain slice subscription information of the terminal;

[0215] The first network side device receives the second information from the second network side device, wherein the second information is used to indicate an association relationship between at least one application or at least one service of the terminal and the respective associated slices;

[0216] The method further comprises:

[0217] The first network side device determines the first information according to the second information and the first request message.

[0218] The third request message may be Nudm_SDM_Get req, and the Nudm_SDM_Get req may carry the same or different information content as the first request message.

[0219] For example, the third request message carries at least one of the following:

[0220] The identification information of the terminal, wherein the identification information of the terminal may be a Subscription Concealed Identifier (SUCI), based on which the second network side device may obtain the APP registered or the contracted service corresponding to the identification information, and the association information between each APP or service and the slice, such as APP / slicemapping list;

[0221] Identification information of the network where the terminal resides, wherein the identification information of the network where the terminal resides may include a VPLMN ID and a HPLMN ID, and the first network side device may determine a transmission path of the second information or the third information based on the identification information;

[0222] First indication information, wherein the first indication information indicates that the terminal supports a slice-based network selection function, and the first indication information is related to Figure 2 The meaning and function of the first indication information in the illustrated method embodiment are the same and will not be described in detail here;

[0223] Target APP information, the target APP information including identification information of an APP that the terminal tends to use or install. Optionally, the second network side device may determine association information between the target APP and the slice as the first information according to the target APP information carried in the third request message;

[0224] target service information, the target service information including identification information of a service that the terminal prefers to use or subscribes to, and optionally, the second network side device may determine association information between the target service and the slice as the first information according to the target service information carried in the third request message;

[0225] A first access type, the first access type is applicable to obtaining the first information, or applicable to using the target APP or the target service, and ... Figure 2 The first access type in the illustrated method embodiment has the same meaning and function, for example: the second network side device may provide the first information to the terminal when supporting the first access type;

[0226] Second indication information, the second indication information instructs the second network side device to provide second information to the first network side device, the second information is used to indicate the association relationship between at least one application or at least one service of the terminal and their respectively associated slices, such as instructing the UDM network element to provide the slice subscription information of the terminal to the AMF network element, and the slice subscription information may include the association information between all applications or services subscribed by the terminal and their respectively associated slices.

[0227] It should be noted that the second indication information can be generated or converted by the AMF network element after understanding the information in the first request message from the terminal. For example, when the third indication information is carried in the first request message, the AMF network element generates the second indication information by understanding the third indication information.

[0228] Optionally, the third request message may carry the following information:

[0229] Terminal identification information;

[0230] Information carried in the first request message;

[0231] The second indication information.

[0232] For example: the first request message carries: target APP information, identification information of the network where the terminal resides, first indication information and first access type, then the first network side device forwards the identification information of the network where the terminal resides, the first indication information and the first access type in the first request message to the second network side device, and also carries the identification information of the terminal sending the first request message, and carries the second indication information.

[0233] In this way, the first network side device can obtain the association information of all applications or services subscribed by the terminal and their respectively associated slices from the second network side device based on the third request message, and based on the target APP information carried in the first request message, find the association information of the target APP and the slice as the first information from the association information of all applications or services subscribed by the terminal and their respectively associated slices.

[0234] Optionally, corresponding to the first request message, the first network side device may feed back the first information to the terminal via a downlink (DL) NAS Transport message such as a registration accept message or a service accept message, which will not be elaborated herein.

[0235] In this embodiment, the first network side device can determine the first information requested by the terminal based on the first request message sent by the terminal and the second information from the second network side device (UDM network element of the home network), and thus feedback the first information to the terminal, wherein the second information may include association information of at least one application or at least one service of the terminal and their respectively associated slices.

[0236] In another implementation manner, the first network side device obtains the third information from the second network side device, including:

[0237] The first network side device sends a third request message to the second network side device;

[0238] The first network side device receives the third information from the second network side device, wherein the third information includes the first information encapsulated in the SOR payload;

[0239] The first network side device sends first information to the terminal, including:

[0240] The first network side device sends the SOR payload to the terminal.

[0241] In this embodiment, the first network side device can send a third request message to the second network side device based on the first request message sent by the terminal, so that the second network side device determines the first information requested by the terminal based on the third request message and the association information of at least one application or at least one service of the terminal and the slices associated with each other, and encapsulates the first information in the SOR payload. Then, the SOR payload can be transparently transmitted to the terminal through the first network side device, and the terminal can obtain the first information by decoding the SOR payload.

[0242] It is worth mentioning that in this implementation, the third request message may not carry the second indication information, that is, the second network side device may not provide the first network side device with the association information of all applications or services subscribed by the terminal and their associated slices. Instead, the second network side device directly determines the first information based on the information carried in the third request message and the contract information of the terminal, and encapsulates the first information in the SOR payload and then transparently transmits it to the terminal through the first network side device. In this way, the privacy performance of the terminal contract information can be improved.

[0243] As an optional implementation manner, after the first network side device obtains the second information, the method further includes:

[0244] The first network side device determines the NSSAI (configured NSSAI) configured for the terminal according to the second information and the first request message.

[0245] Optionally, the NSSAI configured for the terminal may include at least one of the following:

[0246] a slice associated with the target object in the first information;

[0247] The slice in the first information that is associated with the target object and has the highest priority.

[0248] Optionally, when the first request carries identification information of the target object, and the second information does not include association information between the target object and the slice, the method further includes:

[0249] The first network side device determines that the first information includes at least one of the following:

[0250] Association information between the target object and the default S-NSSAI;

[0251] Association information between the target object and the slice in the NSSAI configured for the terminal.

[0252] In one implementation, the default S-NSSAI may be a non-implementation (default) S-NSSAI.

[0253] For example, the visited network AMF determines the configured NSSAI and APP / slice combinations, including one or more of the following:

[0254] The slices associated with APP in APP / slice combinations are included in the configured NSSAI;

[0255] The slice with the highest priority associated with APP in the APP / slice combinations is included in configuredNSSAI;

[0256] If the APP is not provided in the APP / slice mapping list, but the terminal carries the APP in the APPinfo list in the first request message, the VPLMN AMF sets the slice associated with the APP to the designated slice (not implementing (default) S-NSSAI or the slice included in the configured NSSAI).

[0257] In an embodiment of the present application, the first network side device can transmit the association information between the target object and the slice to the terminal, so that when the terminal uses a first object, it can select a suitable slice for the first object based on the association information, thereby improving the communication performance of the terminal when using the first object. Figure 2 In the illustrated method embodiment, similar beneficial effects of the first network side device transmitting the first information or the third information to the terminal are not repeated here to avoid duplication.

[0258] See also Figure 4 , another method for transmitting slice association information provided by an embodiment of the present application, the execution subject of which may be a second network side device, and the second network side device may be a UDM network element.

[0259] like Figure 4 As shown, the method for transmitting slice association information may include at least one of the following steps:

[0260] Step 401: The second network side device sends third information to the terminal, where the third information is information obtained by encapsulating the first information in a roaming guidance SOR payload, where the first information is used to indicate an association relationship between a target object and a slice, where the target object includes at least one of a target application APP and a target service;

[0261] Step 402: The second network side device sends second information to the first network side device, where the second information is used to indicate an association relationship between at least one application or at least one service of the terminal and their respectively associated slices.

[0262] It should be noted that the first information, target object, second information, and third information in the embodiments of the present application are similar to those in the embodiments of the present invention. Figure 2 The first information, target object, second information, and third information in the illustrated method embodiment have the same meaning and function, which will not be described in detail herein.

[0263] It should be noted that the second network side device sends the third information to the terminal, and the third information sent by the second network side device may be transmitted through the first network side device to the terminal. For example: after the UDM determines the first information and encapsulates the first information in the SOR payload, the SOR payload is sent to the AMF network element. In this way, the AMF network element transparently transmits the SOR payload to the terminal, so that the terminal obtains the first information after security verification and decoding the SOR payload.

[0264] In another implementation, the second network side device may provide the first network side device with auxiliary information for determining the first information, namely, the second information, and the first network side device may determine the first information according to the first request message of the terminal and the second information. For example: the terminal sends a first request message to the AMF network element of the VPLMN, and the AMF network element then sends a third request message to the UDM network element of the HPLMN, and the UDM network element feeds back the second information to the AMF network element based on the third request message, and the AMF network element feeds back the first information to the terminal according to the second information and the first request message.

[0265] In other words, if the UDM network element feeds back the second information to the AMF network element based on the third request message, the AMF network element can determine the first information based on the second information and the first request message, and feed back the first information to the terminal; if the UDM network element feeds back the third information based on the third request message, the AMF network element transparently transmits the third information to the terminal.

[0266] Optionally, after determining the first information, the UDM network element may encapsulate it in the SOR payload to form third information, and transparently transmit the third information to the terminal through the AMF network element. The terminal can obtain the first information by decoding the third information.

[0267] Optionally, the UDM network element can provide second information to the AMF network element, such as association information between all applications or services subscribed by the terminal and their respectively associated slices, so that the AMF network element can determine the first information based on the second information and the target object for which the terminal needs to obtain the associated slices.

[0268] It should be noted that the above-mentioned UDM network element can transmit the second information or the third information at the request of the terminal. For example, the terminal sends a first request message to the AMF network element to request the association information of the target APP or target service and the slice. The AMF network element then queries the UDM network element for the association information of the target APP or target service and the slice, and the UDM network element uses the queried information as the first information or the second information. If the UDM network element uses the queried information as the first information, the UDM encapsulates it in the SOR payload and transmits it to the terminal through the AMF network element; if the UDM network element uses the queried information as the second information, the second information is directly fed back to the AMF network element.

[0269] Alternatively, the UDM network element may also transmit the second information or the third information under the trigger of SOR-AF. For example, when SOR-AF detects that a slice associated with a service has changed, it sends updated association information to the UDM network element or sends update indication information to the UDM network element, where the update indication information is used to indicate that the association information between the service and the slice has been updated, and the UDM network element can determine that the first information is the updated association information between the service and the slice.

[0270] It is worth noting that the UDM network element may or may not store the first information locally. If the terminal does not store the first information, the UDM network element needs to obtain the first information from a third network side device, such as SOR-AF.

[0271] As an optional implementation manner, before the second network side device sends the third information to the terminal, the method further includes:

[0272] The second network side device receives a third request message from the first network side device, wherein the third request message is used to request the first information;

[0273] The second network side device sends third information to the terminal, including:

[0274] When the first condition is met, the second network side device sends the third information to the terminal according to the third request message;

[0275] or,

[0276] When the second condition is met, the second network side device sends a fourth request message to the third network side device according to the third request message;

[0277] The second network side device receives the first information or the updated first information from the third network side device, and sends third information to the terminal, wherein the third information is information obtained by encapsulating the first information or the updated first information in a SOR payload.

[0278] Among them, before the second network side device receives the third request message from the first network side device, the terminal sends a first request message to the first network side device, and the first network side device understands the first request message, and then sends a third request message to the second network side device. At this time, the third request message can carry the information in the first request message, and can also carry other additional information, or the information carried can be information obtained after understanding and converting the information in the first request message.

[0279] Optionally, the first condition includes at least one of the following:

[0280] The terminal supports a network selection function based on slicing;

[0281] The second network side device locally stores the first information;

[0282] Locally indicating that the first information is not updated;

[0283] or,

[0284] The second condition includes at least one of the following:

[0285] The terminal supports a network selection function based on slicing;

[0286] The second network side device does not store the first information locally;

[0287] The first information is locally indicated to be updated.

[0288] For example, when the home network UDM network element receives the third request message from the AMF network element, it can perform the following operations:

[0289] 1) First, determine whether the terminal supports the slice-based network selection function; including two methods: a) determine based on the subscription information of the terminal; b) determine based on whether the third request message carries SbPS support indication;

[0290] 2) If it is determined that the terminal supports the slice-based network selection function, execute the next judgment 3); otherwise, directly reply a rejection message of the third request message to the terminal;

[0291] 3) UDM further determines whether the latest APP / slice combinations information of the terminal is stored locally;

[0292] a) If the UDM network element locally stores the APP / slice combinations information of the terminal or locally indicates that the APP / slice combinations information of the terminal does not need to be updated, the UDM network element sends a SOR payload encapsulating the first information to the terminal, wherein, when the third request message carries the APP info list, the first information may include the association information of each APP and slice in the APP info list; when the third request message does not carry the APPinfo list, the first information may include the default APP / slice combinations or include all the APP / slice combinations information of the terminal;

[0293] b) If the UDM network element does not locally store the APP / slice combinations of the terminal or locally instructs the terminal to update the APP / slice combinations, the UDM may send a fourth request message to the SOR-AF to obtain the first information from the SOR-AF.

[0294] Optionally, the first request message carries at least one of the following:

[0295] identification information of the network where the terminal resides;

[0296] First indication information, where the first indication information indicates that the terminal supports a slice-based network selection function;

[0297] Target APP information, the target APP information including identification information of the APP that the terminal tends to use or install;

[0298] Target service information, the target service information including identification information of the service that the terminal tends to use or subscribe to;

[0299] a first access type, where the first access type is applicable to obtaining the first information, or to using the target APP or the target service;

[0300] Third indication information, where the third indication information indicates that the first request message is used to request the first information.

[0301] Among them, the information carried in the first request message is similar to Figure 2 The meaning and function of each piece of information carried in the first request message in the illustrated method embodiment are the same and will not be repeated here.

[0302] Optionally, the fourth request message carries at least one of the following:

[0303] identification information of the terminal;

[0304] Target APP information, the target APP information including identification information of the APP that the terminal tends to use or install;

[0305] Target service information, the target service information including identification information of the service that the terminal tends to use or subscribe to;

[0306] The first access type is applicable to obtaining the first information, or applicable to using the target APP or the target service.

[0307] Among them, the terminal identifier, target APP information, target service information and first access type in the fourth request message are the same as those in the example Figure 2 The meaning and function of the corresponding content carried in the first request message in the illustrated method embodiment are the same and will not be repeated here.

[0308] As an optional implementation manner, before the second network side device sends the second information to the first network side device, the method further includes:

[0309] The second network side device receives a third request message from the first network side device, wherein the third request message is used to request to obtain slice subscription information of the terminal;

[0310] The second network side device sends the second information to the first network side device.

[0311] Optionally, the third request message carries at least one of the following:

[0312] identification information of the terminal;

[0313] identification information of the network where the terminal resides;

[0314] First indication information, where the first indication information indicates that the terminal supports a slice-based network selection function;

[0315] Target APP information, the target APP information including identification information of the APP that the terminal tends to use or install;

[0316] Target service information, the target service information including identification information of the service that the terminal tends to use or subscribe to;

[0317] a first access type, where the first access type is applicable to obtaining the first information, or to using the target APP or the target service;

[0318] Second indication information, the second indication information indicates that the second network side device provides second information to the first network side device, and the second information is used to indicate the association relationship between at least one application or at least one service of the terminal and their respectively associated slices.

[0319] In one implementation, the second network side device may query the slice information subscribed by the terminal based on the identification information of the terminal.

[0320] In one implementation, the second network side device may determine a transmission path of the first information, the second information, or the third information, such as a relay transmission node and a transmission destination, based on identification information of the network where the terminal resides.

[0321] In one implementation, the second network side device may, based on the first indication information, feedback the third information to the terminal or feedback the second information to the AMF only when it determines that the terminal supports the slice-based network selection function.

[0322] In one implementation, the second network side device may determine, based on the target APP information, that the first information or the second information is used to indicate the association relationship between the target APP information and the slice.

[0323] In one implementation, the second network side device may determine, based on the target service information, that the first information or the second information is used to indicate the association between the target service information and the slice.

[0324] In one implementation, the second network side device may determine, based on the first access type, an access type suitable for obtaining the first information, or suitable for using the target APP or the target service.

[0325] In one implementation, the second network side device may provide the second information to the first network side device based on the second indication information.

[0326] For example, upon receiving the third request message from the AMF network element, the home network UDM may perform the following operations:

[0327] 1) First, determine whether the terminal supports the slice-based network selection function; including two methods: a) determine based on the subscription information of the terminal; b) determine based on whether the third request message carries SbPS support indication;

[0328] 2) If it is determined that the terminal supports the slice-based network selection function, execute the next judgment 3); otherwise, directly reply a Nudm_SDM_Get response message to the visited network AMF, and the Nudm_SDM_Get response message does not carry the second information;

[0329] 3) UDM further determines whether the latest APP / slice mapping list of the terminal is saved locally;

[0330] a) If the UDM network element locally stores the APP / slice mapping list of the terminal or locally indicates that the APP / slice mapping list information of the terminal does not need to be updated, the UDM network element replies to the visited network AMF with a Nudm_SDM_Get response message, and the Nudm_SDM_Get response message carries the APP / slicemapping list or part of the APP / slice mapping list of the terminal, such as: when the third request message carries the APPinfo list, the second information may include the association information of each APP and slice in the APP info list; when the third request message does not carry the APP info list, the second information may include the default APP / slicecombinations or the APP / slice combinations information of all the terminals;

[0331] b) If the UDM network element does not locally store the APP / slice mapping list of the terminal or locally instructs the terminal to update the APP / slice mapping list, the UDM may send a fourth request message to the SOR-AF to obtain the first information from the SOR-AF.

[0332] In this implementation, the UDM needs to communicate with the terminal through the AMF network element. In this implementation, the AMF network element obtains the first request message from the terminal, and obtains the second information from the UDM network element based on the first request message, and then the AMF network element can determine the first information according to the first request message and the second information.

[0333] In an embodiment of the present application, the second network side device can transmit third information to the terminal, and the third information encapsulates the first information; or provide the second information to the first network side device, so that the first network side device can feed back the first information to the terminal according to the second information and the first request message from the terminal. In this way, the terminal can obtain the association information between the target object and the slice, and then when the terminal uses a first object, it can select a suitable slice for the first object based on the association information, thereby improving the communication performance of the terminal when using the first object, which has the same effect as Figure 2In the method embodiment shown, the second network side device provides the second information to the first network side device to assist the first network side device in determining the first information, or the first network side device transparently transmits the third information to the terminal to achieve similar beneficial effects. Repetition is not avoided and will not be repeated here.

[0334] See also Figure 5 , another method for transmitting slice association information provided in an embodiment of the present application, the execution subject of which may be a third network side device, and the third network side device may be a SOR-AF network element.

[0335] like Figure 5 As shown, the method for transmitting slice association information may include the following steps:

[0336] Step 501: The third network side device sends the first information or the updated first information to the second network side device, wherein the first information is used to indicate the association relationship between the target object and the slice, and the target object includes at least one of the target application APP and the target service.

[0337] The first information, the target object and the like in the embodiment of the present application are Figure 2 The first information and the target object in the illustrated method embodiment have the same meaning and function, which will not be described in detail here.

[0338] In one implementation, the third network side device sends the first information or the updated first information to the second network side device, including:

[0339] When the association information between the target object and the slice changes, the third network side device sends the updated first information to the second network side device.

[0340] For example: When the SOR-AF network element detects that a slice associated with a service has changed, it can send updated association information to the UDM network element or send update indication information to the UDM network element.

[0341] Among them, if the SOR-AF network element sends updated association information to the UDM network element, the UDM network element can determine that the first information is the updated association information between the service and the slice; if the SOR-AF network element sends update indication information to the UDM network element, when the UDM network element provides the first information, the second information or the third information to the terminal or the AMF network element, if it detects that the update indication information is stored locally, it determines that the association information between the service and the slice is not the latest, thereby triggering the acquisition of the latest association information from the SOR-AF network element, and determining that the latest association information is the first information or the second information.

[0342] The second information and the third information are as follows: Figure 2The second information and the third information in the illustrated method embodiment have the same meaning and function, which will not be described in detail here.

[0343] In another implementation manner, before the third network side device sends the first information to the second network side device, the method further includes:

[0344] The third network side device receives a fourth request message from the second network side device, wherein the fourth request message is used to request the first information or the updated first information.

[0345] For example, the request of the terminal is transmitted to the UDM network element through the AFM network element. Under the action of the request, the UDM network element may query the SOR-AF network element for the first information or the updated first information.

[0346] In an embodiment of the present application, the SOR-AF network element can actively indicate the updated first information to the UDM network element, or provide the UDM network element with the first information or the updated first information. In this way, the first information or the updated first information can be transmitted to the terminal through the UDM network element and the AMF network element, so that the terminal obtains the association information between the target object and the slice, and then when the terminal uses a first object, it can select a suitable slice for the first object based on the association information, thereby improving the communication performance of the terminal when using the first object, which has the same effect as Figure 2 In the illustrated method embodiment, similar beneficial effects of the third network side device transmitting the updated first information to the second network side device or the second network side device querying the third network side device for the first information or the second information are not repeated here to avoid duplication.

[0347] An embodiment of the present application also provides a system for transmitting slice association information, which may include a first network side device or a second network side device, and a terminal.

[0348] terminal;

[0349] A first network side device is used to send first information to the terminal; or,

[0350] A second network side device, configured to send third information to the terminal, where the third information includes the first information encapsulated in a roaming guidance SOR payload;

[0351] Among them, the first information is used to indicate the association relationship between the target object and the slice, the target object includes at least one of a target application APP and a target service, the first information is used to give priority to using the slice associated with the first object when the terminal uses the first object, and the target object includes the first object.

[0352] It should be noted that, in the embodiment of the present application, the terminal may execute the following Figure 2 In the steps of the method embodiment shown in the figure, the first network side device may perform the following steps: Figure 3 In the steps of the method embodiment shown in the figure, the second network side device may perform the following steps: Figure 4 In the steps of the method embodiment shown in the figure, the third network side device may perform the following steps: Figure 5 The steps in the method embodiment shown are similar to those in Figure 2 , Figure 3 , Figure 4 and Figure 5 The same or similar beneficial effects of the method embodiments shown are not described again here to avoid repetition.

[0353] The first information, the third information, the target object and the like in the embodiment of the present application are Figure 2 The first information, the third information, and the target object in the illustrated method embodiment have the same meaning and function, and will not be described in detail here.

[0354] Optionally, before the first network side device sends the first information to the terminal:

[0355] The terminal is used to send a first request message to the first network side device, wherein the first request message is used to request first information;

[0356] The first network side device is further used to send a third request message to the second network side device, wherein the third request message is used to request to obtain the slice subscription information of the terminal;

[0357] The second network side device is further used to send second information to the first network side device, wherein the second information is used to indicate an association relationship between at least one application or at least one service of the terminal and the respectively associated slices;

[0358] The first network side device is further used to determine the first information according to the second information and the first request message.

[0359] Optionally, the transmission system of the slice association information further includes: a third network side device;

[0360] The second network side device is specifically used for:

[0361] When the first condition is met, the second network side device sends the second information to the first network side device according to the third request message;

[0362] or,

[0363] When the second condition is met, the second network side device sends a fourth request message to the third network side device according to the third request message;

[0364] The second network side device receives the second information from the third network side device.

[0365] Optionally, before the second network side device sends the third information to the terminal:

[0366] The terminal is used to send a first request message to the first network side device, wherein the first request message is used to request first information;

[0367] The first network side device is further used to send a third request message to the second network side device;

[0368] The second network side device is further configured to determine the first information according to the third request message when the first condition is met, and encapsulate the first information in a SOR payload to obtain the third information;

[0369] or,

[0370] The second network side device is further configured to send a fourth request message to the third network side device according to the third request message when the second condition is met;

[0371] The second network side device is further used to receive the first information from the third network side device, and encapsulate the first information in a SOR payload to obtain the third information.

[0372] Optionally, the first condition includes at least one of the following:

[0373] The terminal supports a network selection function based on slicing;

[0374] The second network side device locally stores the first information;

[0375] Locally indicating that the first information is not updated;

[0376] or,

[0377] The second condition includes at least one of the following:

[0378] The terminal supports a network selection function based on slicing;

[0379] The second network side device does not store the first information locally;

[0380] The first information is locally indicated to be updated.

[0381] Optionally, the first request message carries at least one of the following:

[0382] identification information of the network where the terminal resides;

[0383] First indication information, where the first indication information indicates that the terminal supports a slice-based network selection function;

[0384] Target APP information, the target APP information including identification information of the APP that the terminal tends to use or install;

[0385] Target service information, the target service information including identification information of the service that the terminal tends to use or subscribe to;

[0386] a first access type, where the first access type is applicable to obtaining the first information, or to using the target APP or the target service;

[0387] Third indication information, where the third indication information indicates that the first request message is used to request the first information.

[0388] Optionally, the third request message carries at least one of the following:

[0389] identification information of the terminal;

[0390] identification information of the network where the terminal resides;

[0391] First indication information, where the first indication information indicates that the terminal supports a slice-based network selection function;

[0392] Target APP information, the target APP information including identification information of the APP that the terminal tends to use or install;

[0393] Target service information, the target service information including identification information of the service that the terminal tends to use or subscribe to;

[0394] a first access type, where the first access type is applicable to obtaining the first information, or to using the target APP or the target service;

[0395] Second indication information, the second indication information indicates that the second network side device provides second information to the first network side device, and the second information is used to indicate the association relationship between at least one application or at least one service of the terminal and their respectively associated slices.

[0396] Optionally, the fourth request message carries at least one of the following:

[0397] identification information of the terminal;

[0398] Target APP information, the target APP information including identification information of the APP that the terminal tends to use or install;

[0399] Target service information, the target service information including identification information of the service that the terminal tends to use or subscribe to;

[0400] The first access type is applicable to obtaining the first information, or applicable to using the target APP or the target service.

[0401] Optionally, the system for transmitting slice association information further includes:

[0402] The third network side device is used to send the updated first information to the second network side device when it is determined that the slice associated with the target object has changed.

[0403] Optionally, the first network side device is specifically configured to:

[0404] The first network side device receives the updated first information through the second network side device;

[0405] The first network side device sends the updated first information to the terminal.

[0406] Optionally, the second network side device is specifically used to:

[0407] The second network side device encapsulates the updated first information in the SOR payload to obtain the third information;

[0408] The second network side device sends the third information to the terminal through the first network side device.

[0409] In the embodiment of the present application, it is possible to achieve Figure 2 , Figure 3 , Figure 4 and Figure 5 To avoid repetition, the beneficial effects of at least one method embodiment are not described here.

[0410] For ease of understanding, the following embodiment is taken as an example in the embodiment of the present application to illustrate the interaction process between the terminal, the AMF network element of the VPLMN, the UDM network element of the HPLMN, the SOR-AF network element, and the AF network element in the embodiment of the present application:

[0411] Embodiment 1: The terminal requests slice information related to the APP list, and the network-side AMF determines the APP / slice combinations and sends it to the UE.

[0412] like Figure 6a As shown, the interaction process between the terminal, the AMF network element of the VPLMN, the UDM network element of the HPLMN, and the SOR-AF network element includes the following steps:

[0413] Step 1: The terminal sends a first request message to the visited network AMF.

[0414] The first request message may be a registration request (including an initial registration process and a registration update process); a service request; or a UL NAS TRANSPORT message. The first request message indicates that the terminal wishes to obtain the specified APP / service or the APP / slicecombinations information associated with the APP / service in the contract information.

[0415] Optionally, the first request message may carry at least one of the following:

[0416] 1) Network identification information (PLMN ID, etc., indicating the current network PLMN ID);

[0417] 2) SbPS support indication; (indicates that the terminal supports the slice-based network selection function)

[0418] 3) APP info list; (indicates the APP information that the current UE tends to use or that the system installs, which can be represented by OS ID+APP ID, and the coding is shown in Example 5)

[0419] 4) Access type; (indicates the access type applicable to obtaining APP / slice combinations information, including 3GPP access, non-3GPP access, 3GPP and non-3GPP access).

[0420] It should be noted that before step 1, the application display interaction can be performed on the terminal, and the APP info list information can be sent to the network only after obtaining the user's authorization.

[0421] Step 2: The visited AMF sends the existing message Nudm_SDM_Get req to the home network UDM, requesting to obtain the slice subscription information of the terminal. The message carries the terminal identifier (SUCI, etc.).

[0422] Optionally, the Nudm_SDM_Get req message carries the information in the first request message.

[0423] Optionally, the Nudm_SDM_Get req message carries second indication information, indicating that the APP / slice mapping list of the terminal is desired to be obtained.

[0424] Step 3: The home network UDM performs the following operations:

[0425] 1) First, determine whether the terminal supports the slice-based network selection function; including two determination methods: a) determining based on the subscription information of the terminal; b) determining based on whether the SbPS support indication is carried in step 2;

[0426] 2) If the terminal supports the slice-based network selection function, execute the next judgment 3); otherwise, directly execute the operation of step 6, skipping steps 4 and 5, wherein step 6 does not carry the APP / slice mapping list of the terminal;

[0427] 3) UDM further determines whether the latest APP / slice mapping list of the terminal is saved locally:

[0428] a) If the UDM locally stores the APP / slice mapping list of the terminal or locally indicates that the APP / slice mapping list of the terminal does not need to be updated, the UDM directly executes the operation of step 6, skipping steps 4 and 5. The UDM provides the APP / slice mapping list associated with the APP / service specified in step 2 (if the APP info list is carried in step 2) or provides the default or all APP / slice mapping lists of the terminal (if the APP info list is not carried in step 2);

[0429] b) If the UDM does not locally store the APP / slice mapping list of the terminal or locally instructs the APP / slice mapping list of the terminal to be updated, the UDM executes step 4 to obtain the APP / slice mapping list of the terminal from the SOR-AF.

[0430] Step 4: The home network UDM sends a fourth request message to the SOR-AF to request to obtain the APP / slicemapping list of the terminal.

[0431] Optionally, the fourth request message may carry the following information:

[0432] 1) Terminal identification (SUCI, etc.);

[0433] 2) Access type;

[0434] 3)APP info list.

[0435] Step 5. SOR-AF replies to the home network UDM. The reply message includes the APP / slicemapping list of the terminal, identifying the mapping relationship between one or more APP / services and slices.

[0436] The fourth request message and the reply message to the fourth request message may be newly added messages.

[0437] Step 6. The home network UDM replies to the visited network AMF with the existing message Nudm_SDM_Get response, where the message carries the APP / slice mapping list. Optionally, as described in step 3, if the terminal does not support the slice-based network selection function, the APP / slice mapping list is not carried.

[0438] Step 7: The visited network AMF determines the configured NSSAI and APP / slice combinations, including one or more of the following:

[0439] 1) The slices associated with APP in APP / slice combinations are included in the configured NSSAI;

[0440] 2) The slice with the highest priority associated with APP in the APP / slice combinations is included in the configuredNSSAI;

[0441] 3) If the APP is not provided in the APP / slice mapping list, but the terminal carries the APP in the APP info list in step 1, the VPLMN AMF sets the slice associated with the APP to the specified slice ((not fulfilled) default S-NSSAI or the slice included in the configured NSSAI).

[0442] Step 8: The visited network AMF replies to the terminal with a first response message, which includes APP / slicecombinations information. The first response message is a response message to the first request message, which may specifically be a registration accept, service accept, or DL ​​NAS TRANSPORT message.

[0443] Step 9: After receiving the app / slice combinations information, the terminal performs at least one of the following operations:

[0444] Stored in entities such as USIM or ME;

[0445] Pass the information to the APP layer;

[0446] When the terminal is using an APP / service, if the APP / service appears in the APP / slice combinations information, the terminal will prioritize slices with higher priorities when requesting slices (i.e., placing slices with higher priorities in the requested NSSAI); otherwise, the terminal will request slices according to existing regulations.

[0447] Embodiment 2: The terminal requests slice information related to the APP list, and the UDM on the network side determines the APP / slice combinations and sends them to the UE through a SOR message.

[0448] The difference between the second embodiment and the first embodiment is that there is no concept of APP / slice mapping list in the present embodiment. In the whole interaction process, there are only APP / slice combinations, that is, UDM directly encrypts and protects APP / slice combinations and directly transmits them to the terminal without being processed by the visited network AMF. This can avoid the leakage of privacy information to a certain extent.

[0449] like Figure 6b As shown, the interaction process between the terminal, the AMF network element of the VPLMN, the UDM network element of the HPLMN, and the SOR-AF network element includes the following steps:

[0450] Steps 1 and 2 are the same as Figure 6a Step 1 and step 2 in the embodiment 1 are the same, and the details can be referred to as follows Figure 6a The description of step 1 and step 2 in the above will not be repeated here.

[0451] Step 3: After receiving the Nudm_SDM_Get req message from the AMF network element, the home network UDM performs the following operations:

[0452] 1) First, determine whether the terminal supports the slice-based network selection function; including two determination methods: a) determining based on the subscription information of the terminal; b) determining based on whether the SbPS support indication is carried in step 2;

[0453] 2) If the terminal supports the slice-based network selection function, execute the next judgment 3); otherwise, directly execute the operation of step 6, skipping steps 4 and 5, wherein step 6 does not carry the APP / slice combinations information of the terminal;

[0454] 3) UDM further determines whether the latest APP / slice combinations information of the terminal is saved locally:

[0455] a) If the UDM locally stores the APP / slice combinations information of the terminal or locally indicates that the APP / slice combinations information of the terminal does not need to be updated, the UDM directly performs the operations of step 6 and step 7, skipping steps 4 and 5. The UDM provides the APP / slice combinations information associated with the APP / service specified in step 2 (if the APP info list is carried in step 2) or provides the default or all APP / slice combinations information of the terminal (if the APP info list is not carried in step 2);

[0456] b) If the UDM does not locally store the APP / slice combinations information of the terminal or locally instructs the terminal to update the APP / slice combinations information, the UDM executes step 4 to obtain the APP / slice combinations information of the terminal from the SOR-AF.

[0457] Steps 4 and 5 are the same as Figure 6a Step 4 and step 5 in the embodiment 1 are the same, and the details can be referred to as follows Figure 6a The description of step 4 and step 5 in the above will not be repeated here.

[0458] In steps 6 and 7, the home network UDM securely encrypts the APP / slice combinations information received in step 5, encapsulates it in the SOR payload, and sends it to the visited network AMF through the existing message Nudm_SDM_Get response.

[0459] Step 8: The visited network AMF encapsulates the SOR payload carrying the APP / slice combinations information in the payload container of the first response message and transparently transmits it to the terminal. The first response message is a response message to the first request message.

[0460] Step 9: If the requested APP has no associated APP / slice combinations information, when the terminal uses the APP, if the terminal supports the slice-based network selection function, the default S-NSSAI is used to request the slice; otherwise, the slice request is made according to the prior art.

[0461] Embodiment 3: The network side updates APP / slice combinations and sends them to the UE.

[0462] like Figure 6c As shown, the interaction process between the terminal, the AMF network element of the VPLMN, the UDM network element of the HPLMN, and the SOR-AF network element includes the following steps:

[0463] Step 1: When the APP / slice combinations information needs to be updated, SOR-AF triggers to send the updated APP / slice combinations information to UDM. UDM can reply to SOR-AF in step 7.

[0464] Step 2: UDM will send the updated APP / slice combinations information to the visited network AMF, encapsulated in SOR. AMF can reply to UDM in step 6.

[0465] Step 3: The visited network AMF encapsulates the SOR message carrying the updated APP / slice combinations information in a first message and sends it to the terminal. The first message here may be a UE configuration update command message; it may be a DL NAS TRANSPORT message. The terminal may reply to the first message in step 5, such as replying to the first message through a UE configuration update complete message or a UL NAS TRANSPORT message.

[0466] Step 4: The terminal performs security verification on the SOR message to decode and obtain the updated APP / slicecombinations information.

[0467] Step 8: The terminal updates the local APP / slice combinations and replaces the old APP / slice combinations.

[0468] It should be noted that this third embodiment can be combined with the above-mentioned first and second embodiments. For example, when requesting APP / slice combinations for the first time, APP / slice combinations can be requested in the manner shown in the first or second embodiment. When updating APP / slice combinations subsequently, APP / slice combinations can be updated in the manner shown in the third embodiment.

[0469] Embodiment 4: The terminal is pre-configured locally, and the terminal queries the AF for APP / slice combinations information.

[0470] like Figure 6c As shown, the interaction process between the terminal and the AF network element includes the following steps:

[0471] Step 0: The terminal is configured with APP / slice combinations information for the factory pre-installed APPs, which are stored in the USIM and / or ME (such as non-volatile memory);

[0472] Step 1: If a new APP is added later, the terminal requests the relevant APP / slice combinations information from AF (the server of the APP) through the app layer (Http message). The request message includes information such as APP ID, PLMN ID, and access type.

[0473] It should be noted that before step 1, the interaction can be displayed through the application on the terminal, and the APP information can be sent to the network only after obtaining the user's authorization.

[0474] Step 2: The terminal receives an app layer reply message from AF, which carries the APP / slicecombinations information corresponding to the newly added APP.

[0475] The interactions in step 2 and step 3 belong to the HTTP level and are not 3GPP standards.

[0476] Optionally, AF can also update app / slice combinations information via HTTP.

[0477] Step 3: The terminal stores the received app / slice combinations information in an entity such as USIM or ME; if updated app / slice combinations information is received, the old app / slice combinations information is replaced.

[0478] The method for obtaining slice association information provided in the embodiment of the present application can be executed by a device for obtaining slice association information. In the embodiment of the present application, the device for obtaining slice association information performs the method for obtaining slice association information as an example to illustrate the device for obtaining slice association information provided in the embodiment of the present application.

[0479] See also Figure 7 The slice association information acquisition device 700 provided in the embodiment of the present application may be a device in a terminal. Figure 7 As shown, the slice association information acquisition device 700 may include the following modules:

[0480] The first acquisition module 701 is used to acquire first information, where the first information is used to indicate the association relationship between the target object and the slice, wherein the target object includes at least one of a target application APP and a target service, and the first information is used to give priority to using the slice associated with the first object when the terminal uses the first object, and the target object includes the first object.

[0481] Optionally, the target object includes at least one of the following:

[0482] The services contracted by the terminal;

[0483] APP installed on the terminal;

[0484] The APP that the terminal tends to use;

[0485] The services that the terminal tends to use;

[0486] an APP targeted by a first operation, wherein the first operation is a user operation received on the terminal;

[0487] The service to which the first operation is directed.

[0488] Optionally, the slice association information acquisition device 700 further includes:

[0489] An updating module is used to update the stored association information between the target object and the slice when it is determined according to the first information that the slice associated with the target object has changed.

[0490] Optionally, the slice association information acquisition device 700 further includes at least one of the following:

[0491] A storage module, configured to store the first information in a first entity, wherein the first entity includes a universal subscriber identity module USIM or a management entity ME;

[0492] The slice selection module is used to preferentially use a first slice when using the first object, wherein the first slice is a slice with the highest priority associated with the first object.

[0493] Optionally, the first acquisition module 701 includes at least one of the following:

[0494] A first acquisition unit, used to acquire pre-configured first information;

[0495] A first receiving unit, configured to receive an application layer message from an application server, wherein the application layer message includes the first information;

[0496] A second receiving unit is used to receive first information from a first network element, where the first network element includes an access and mobility management function AMF network element or a unified data management function UDM network element of a home network;

[0497] The third receiving unit is used to receive third information from the second network element, where the third information is obtained by encapsulating the first information in a roaming guidance SOR payload, and the second network element includes a UDM network element of a home network.

[0498] Optionally, the slice association information acquisition device 700 further includes:

[0499] A fifth sending module is used to send a first request message to the first network element, wherein the first request message is used to request the first information.

[0500] Optionally, the first request message carries at least one of the following:

[0501] identification information of the network where the terminal resides;

[0502] First indication information, where the first indication information indicates that the terminal supports a slice-based network selection function;

[0503] Target APP information, the target APP information including identification information of the APP that the terminal tends to use or install;

[0504] Target service information, the target service information including identification information of the service that the terminal tends to use or subscribe to;

[0505] a first access type, where the first access type is applicable to obtaining the first information, or to using the target APP or the target service;

[0506] Third indication information, where the third indication information indicates that the first request message is used to request the first information.

[0507] Optionally, the slice association information acquisition device 700 further includes:

[0508] The sixth sending module is used to send a second request message to the application server, wherein the second request message is used to request association information between the first APP and the slice, the target APP includes the first APP, and the application server is the server of the first APP.

[0509] Optionally, the second request message carries at least one of the following:

[0510] Identification information of the first APP;

[0511] identification information of the network where the terminal resides;

[0512] The first access type is applicable to obtaining the first information or using the first APP.

[0513] The slice association information acquisition device 600 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. Exemplarily, the terminal can include but is not limited to the types of terminals 11 listed above, and the embodiment of the present application does not specifically limit this.

[0514] The slice association information acquisition device 700 provided in the embodiment of the present application can achieve Figure 2 The various processes implemented by the illustrated method embodiment achieve the same technical effect and will not be described again here to avoid repetition.

[0515] The method for transmitting slice association information provided in the embodiment of the present application can be executed by a transmission device for slice association information. In the embodiment of the present application, the transmission method for slice association information performed by a transmission device for slice association information is taken as an example to illustrate the transmission device for slice association information provided in the embodiment of the present application.

[0516] See also Figure 8 The slice association information transmission device 800 provided in the embodiment of the present application may be a device in the first network side device. Figure 8 As shown, the transmission device 800 of the slice association information may include the following modules:

[0517] The first sending module 801 is used to send first information to the terminal, where the first information is used to indicate the association relationship between the target object and the slice, and the target object includes at least one of a target application APP and a target service.

[0518] Optionally, the device 800 for transmitting slice association information further includes:

[0519] A first receiving module, configured to receive a first request message from the terminal, wherein the first request message is used to request the first information;

[0520] The second acquisition module is used to obtain second information or third information from a second network side device, wherein the second information is used to indicate the association relationship between at least one application or at least one service of the terminal and their respectively associated slices, or the third information includes the first information encapsulated in a roaming guidance SOR payload.

[0521] Optionally, the first request message carries at least one of the following:

[0522] identification information of the network where the terminal resides;

[0523] First indication information, where the first indication information indicates that the terminal supports a slice-based network selection function;

[0524] Target APP information, the target APP information including identification information of the APP that the terminal tends to use or install;

[0525] Target service information, the target service information including identification information of the service that the terminal tends to use or subscribe to;

[0526] a first access type, where the first access type is applicable to obtaining the first information, or to using the target APP or the target service;

[0527] Third indication information, where the third indication information indicates that the first request message is used to request the first information.

[0528] Optionally, the second acquisition module includes:

[0529] A first sending unit, configured to send a third request message to the second network side device, wherein the third request message is used to request to obtain slice subscription information of the terminal;

[0530] a fourth receiving unit, configured to receive the second information from the second network side device, wherein the second information is used to indicate an association relationship between at least one application or at least one service of the terminal and the respective associated slices;

[0531] The device 800 for transmitting slice association information further includes:

[0532] The first determining module is used to determine the first information according to the second information and the first request message.

[0533] Optionally, the second acquisition module includes:

[0534] A second sending unit, configured to send a third request message to the second network side device;

[0535] a fifth receiving unit, configured to receive the third information from the second network side device, wherein the third information includes the first information encapsulated in the SOR payload;

[0536] The first sending module 801 is specifically configured to send the SOR payload to the terminal.

[0537] Optionally, the third request message carries at least one of the following:

[0538] identification information of the terminal;

[0539] identification information of the network where the terminal resides;

[0540] First indication information, where the first indication information indicates that the terminal supports a slice-based network selection function;

[0541] Target APP information, the target APP information including identification information of the APP that the terminal tends to use or install;

[0542] Target service information, the target service information including identification information of the service that the terminal tends to use or subscribe to;

[0543] a first access type, where the first access type is applicable to obtaining the first information, or to using the target APP or the target service;

[0544] Second indication information, the second indication information indicates that the second network side device provides second information to the first network side device, and the second information is used to indicate the association relationship between at least one application or at least one service of the terminal and their respectively associated slices.

[0545] Optionally, the device 800 for transmitting slice association information further includes:

[0546] The second determination module is used to determine the network slice selection auxiliary information NSSAI configured for the terminal based on the second information and the first request message.

[0547] Optionally, the NSSAI configured for the terminal includes at least one of the following:

[0548] a slice associated with the target object in the first information;

[0549] The slice in the first information that is associated with the target object and has the highest priority.

[0550] Optionally, when the first request carries identification information of the target object, and the second information does not include association information between the target object and the slice, the slice association information transmission device 800 further includes:

[0551] A third determining module is configured to determine that the first information includes at least one of the following:

[0552] Association information between the target object and the default S-NSSAI;

[0553] Association information between the target object and the slice in the NSSAI configured for the terminal.

[0554] The slice association information transmission device 800 provided in the embodiment of the present application can achieve Figure 3 The various processes implemented by the illustrated method embodiment achieve the same technical effect and will not be described again here to avoid repetition.

[0555] See also Fig. 9 The slice association information transmission device 900 provided in the embodiment of the present application may be a device in the second network side device. Fig. 9 As shown, the transmission device 900 of the slice association information may include the following modules:

[0556] The second sending module 901 is used to send third information to the terminal, where the third information is information obtained by encapsulating the first information in a roaming guidance SOR payload, where the first information is used to indicate an association relationship between a target object and a slice, where the target object includes at least one of a target application APP and a target service;

[0557] or,

[0558] The third sending module 902 is used to send second information to the first network side device, where the second information is used to indicate the association relationship between at least one application or at least one service of the terminal and their respectively associated slices.

[0559] It should be noted that, in one embodiment, the transmission device 900 of slice association information may include a second sending module 901 but not a third sending module 902; in another embodiment, the transmission device 900 of slice association information may include a third sending module 902 but not a second sending module 901; in yet another embodiment, the transmission device 900 of slice association information may include a second sending module 901 and a third sending module 902. Fig. 9 The accompanying drawing of the slice association information transmission device 900 is only taken as an example that the slice association information transmission device 900 includes a second sending module 901 and a third sending module 902, which does not constitute a specific limitation herein.

[0560] Optionally, the device 900 for transmitting slice association information further includes:

[0561] A second receiving module, configured to receive a third request message from the first network side device, wherein the third request message is used to request the first information;

[0562] The second sending module 901 is specifically used for:

[0563] When the first condition is met, sending the third information to the terminal according to the third request message;

[0564] or,

[0565] When the second condition is met, a fourth request message is sent to the third network side device according to the third request message, and the first information or the updated first information from the third network side device is received, and third information is sent to the terminal, wherein the third information is the information obtained by encapsulating the first information or the updated first information in the SOR payload.

[0566] Optionally, the first condition includes at least one of the following:

[0567] The terminal supports a network selection function based on slicing;

[0568] The second network side device locally stores the first information;

[0569] Locally indicating that the first information is not updated;

[0570] or,

[0571] The second condition includes at least one of the following:

[0572] The terminal supports a network selection function based on slicing;

[0573] The second network side device does not store the first information locally;

[0574] The first information is locally indicated to be updated.

[0575] Optionally, the first request message carries at least one of the following:

[0576] identification information of the network where the terminal resides;

[0577] First indication information, where the first indication information indicates that the terminal supports a slice-based network selection function;

[0578] Target APP information, the target APP information including identification information of the APP that the terminal tends to use or install;

[0579] Target service information, the target service information including identification information of the service that the terminal tends to use or subscribe to;

[0580] a first access type, where the first access type is applicable to obtaining the first information, or to using the target APP or the target service;

[0581] Third indication information, where the third indication information indicates that the first request message is used to request the first information.

[0582] Optionally, the fourth request message carries at least one of the following:

[0583] identification information of the terminal;

[0584] Target APP information, the target APP information including identification information of the APP that the terminal tends to use or install;

[0585] Target service information, the target service information including identification information of the service that the terminal tends to use or subscribe to;

[0586] The first access type is applicable to obtaining the first information, or applicable to using the target APP or the target service.

[0587] Optionally, the device 900 for transmitting slice association information further includes:

[0588] A third receiving module is used to receive a third request message from the first network side device, wherein the third request message is used to request to obtain the slice subscription information of the terminal;

[0589] A sixth sending module is used to send the second information to the first network side device.

[0590] Optionally, the third request message carries at least one of the following:

[0591] identification information of the terminal;

[0592] identification information of the network where the terminal resides;

[0593] First indication information, where the first indication information indicates that the terminal supports a slice-based network selection function;

[0594] Target APP information, the target APP information including identification information of the APP that the terminal tends to use or install;

[0595] Target service information, the target service information including identification information of the service that the terminal tends to use or subscribe to;

[0596] a first access type, where the first access type is applicable to obtaining the first information, or to using the target APP or the target service;

[0597] Second indication information, the second indication information indicates that the second network side device provides second information to the first network side device, and the second information is used to indicate the association relationship between at least one application or at least one service of the terminal and their respectively associated slices.

[0598] The slice association information transmission device 900 provided in the embodiment of the present application can achieve Figure 4 The various processes implemented by the illustrated method embodiment achieve the same technical effect and will not be described again here to avoid repetition.

[0599] See also Fig.10 The slice association information transmission device 1000 provided in the embodiment of the present application may be a device in a third network side device. Fig.10 As shown, the device 1000 for transmitting slice association information may include the following modules:

[0600] The fourth sending module 1001 is used to send the first information or the updated first information to the second network side device, wherein the first information is used to indicate the association relationship between the target object and the slice, and the target object includes at least one of the target application APP and the target service.

[0601] Optionally, the fourth sending module 1001 is specifically configured to:

[0602] When the association information between the target object and the slice changes, the updated first information is sent to the second network side device.

[0603] Optionally, the device 1000 for transmitting slice association information further includes:

[0604] The fourth receiving module is used to receive a fourth request message from the second network side device, wherein the fourth request message is used to request the first information or the updated first information.

[0605] The slice association information transmission device 1000 provided in the embodiment of the present application can achieve Figure 5 The various processes implemented by the illustrated method embodiment achieve the same technical effect and will not be described again here to avoid repetition.

[0606] like Fig.11As shown, the embodiment of the present application also provides a communication device 1100, including a processor 1101 and a memory 1102, and the memory 1102 stores a program or instruction that can be run on the processor 1101. For example, when the communication device 1100 is a terminal, the program or instruction is executed by the processor 1101 to implement the various steps of the above-mentioned information transmission method embodiment, and can achieve the same technical effect. When the communication device 1100 is a network side device, the program or instruction is executed by the processor 1101 to implement the following Figure 2 , Figure 3 , Figure 4 or Figure 5 The various steps of the method embodiment shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0607] 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 Figure 2 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.12 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0608] The terminal 1200 includes but is not limited to: a radio frequency unit 1201, a network module 1202, an audio output unit 1203, an input unit 1204, a sensor 1205, a display unit 1206, a user input unit 1207, an interface unit 1208, a memory 1209 and at least some of the components of the processor 1210.

[0609] Those skilled in the art will appreciate that the terminal 1200 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 1210 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Fig.12 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.

[0610] It should be understood that in the embodiment of the present application, the input unit 1204 may include a graphics processing unit (GPU) 12041 and a microphone 12042, and the graphics processor 12041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1206 may include a display panel 12061, and the display panel 12061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1207 includes a touch panel 12071 and at least one of other input devices 12072. The touch panel 12071 is also called a touch screen. The touch panel 12071 may include two parts: a touch detection device and a touch controller. Other input devices 12072 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.

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

[0612] The memory 1209 can be used to store software programs or instructions and various data. The memory 1209 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 1209 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 1209 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0613] The processor 1210 may include one or more processing units; optionally, the processor 1210 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 1210.

[0614] Among them, the processor 1210 is used to obtain first information through at least one of the radio frequency unit 1201, the memory 1209 and the network module 1202, and the first information is used to indicate the association relationship between the target object and the slice, wherein the target object includes at least one of a target application APP and a target service, and the first information is used to give priority to using the slice associated with the first object when the terminal uses the first object, and the target object includes the first object.

[0615] Optionally, the target object includes at least one of the following:

[0616] The services contracted by the terminal;

[0617] APP installed on the terminal;

[0618] The APP that the terminal tends to use;

[0619] The services that the terminal tends to use;

[0620] an APP targeted by a first operation, wherein the first operation is a user operation received on the terminal;

[0621] The service to which the first operation is directed.

[0622] Optionally, the processor 1210 is further configured to update the stored association information between the target object and the slice when it is determined according to the first information that the slice associated with the target object has changed.

[0623] Optionally, the terminal 1200 further includes a device for performing at least one of the following:

[0624] The memory 1209 is configured to store the first information in a first entity, wherein the first entity includes a universal subscriber identity module USIM or a management entity ME;

[0625] The radio frequency unit 1201 is used to give priority to using a first slice when the terminal 1200 uses the first object, wherein the first slice is a slice with the highest priority associated with the first object.

[0626] Optionally, the acquiring of the first information performed by the processor 1210 includes at least one of the following:

[0627] Acquire preconfigured first information through the memory 1209;

[0628] Receiving an application layer message from an application server through the network module 1202, wherein the application layer message includes the first information;

[0629] Receiving, through the radio frequency unit 1201, first information from a first network element, where the first network element includes an access and mobility management function AMF network element or a unified data management function UDM network element of a home network;

[0630] The radio frequency unit 1201 receives third information from the second network element, where the third information is information obtained by encapsulating the first information in a roaming guidance SOR payload, and the second network element includes a UDM network element of the home network.

[0631] Optionally, the radio frequency unit 1201 is further used to send a first request message to the first network element, wherein the first request message is used to request the first information.

[0632] Optionally, the first request message carries at least one of the following:

[0633] identification information of the network where the terminal resides;

[0634] First indication information, where the first indication information indicates that the terminal supports a slice-based network selection function;

[0635] Target APP information, the target APP information including identification information of the APP that the terminal tends to use or install;

[0636] Target service information, the target service information including identification information of the service that the terminal tends to use or subscribe to;

[0637] a first access type, where the first access type is applicable to obtaining the first information, or to using the target APP or the target service;

[0638] Third indication information, where the third indication information indicates that the first request message is used to request the first information.

[0639] Optionally, before the processor 1210 executes the receiving, through the network module 1202, the first information from the application server:

[0640] The network module 1202 is also used to send a second request message to the application server, wherein the second request message is used to request association information between the first APP and the slice, the target APP includes the first APP, and the application server is the server of the first APP.

[0641] Optionally, the second request message carries at least one of the following:

[0642] Identification information of the first APP;

[0643] identification information of the network where the terminal resides;

[0644] The first access type is applicable to obtaining the first information or using the first APP.

[0645] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the following Figure 2 The relevant descriptions of the method embodiments shown in the figure achieve the same or corresponding technical effects, and will not be repeated here to avoid repetition.

[0646] 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 Figure 3 , Figure 4 or Figure 5 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.

[0647] Specifically, the embodiment of the present application also provides a network side device. Fig.13 As shown, the network side device 1300 includes: an antenna 1301, a radio frequency device 1302, a baseband device 1303, a processor 1304 and a memory 1305. The antenna 1301 is connected to the radio frequency device 1302. In the uplink direction, the radio frequency device 1302 receives information through the antenna 1301 and sends the received information to the baseband device 1303 for processing. In the downlink direction, the baseband device 1303 processes the information to be sent and sends it to the radio frequency device 1302. The radio frequency device 1302 processes the received information and sends it out through the antenna 1301.

[0648] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 1303, which includes a baseband processor.

[0649] The baseband device 1303 may include, for example, at least one baseband board on which a plurality of chips are arranged. Fig.13 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 1305 through a bus interface to call the program in the memory 1305 to execute the network device operations shown in the above method embodiment.

[0650] The network side device may further include a network interface 1306, which is, for example, a Common Public Radio Interface (CPRI).

[0651] Specifically, the network side device 1300 of the embodiment of the present application further includes: instructions or programs stored in the memory 1305 and executable on the processor 1304, and the processor 1304 calls the instructions or programs in the memory 1305 to execute Figure 8 , Fig. 9 or Fig.10 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.

[0652] Specifically, the embodiment of the present application also provides a network side device. Fig.14 As shown, the network side device 1400 includes: a processor 1401, a network interface 1402 and a memory 1403. The network interface 1402 is, for example, a Common Public Radio Interface (CPRI).

[0653] Specifically, the network side device 1400 of the embodiment of the present application further includes: instructions or programs stored in the memory 1403 and executable on the processor 1401, and the processor 1401 calls the instructions or programs in the memory 1403 to execute as follows: Figure 8 , Fig. 9 or Fig.10 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.

[0654] The 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, the following is implemented: Figure 2 , Figure 3 , Figure 4 or Figure 5 The various processes of the method embodiment shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0655] 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.

[0656] The present application embodiment further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, the processor is used to run a program or instruction, to implement the following Figure 2 , Figure 3 , Figure 4 or Figure 5 The various processes of the method embodiment shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0657] 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.

[0658] The present application embodiment further provides a computer program / program product, wherein the computer program / program product is stored in a storage medium, and the computer program / program product is executed by at least one processor to implement the following Figure 2 , Figure 3 , Figure 4 or Figure 5The various processes of the method embodiment shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0659] The embodiment of the present application also provides a transmission system of slice association information, including: a terminal, a first network side device, a second network side device and a third network side device, wherein the terminal can be used to perform the following steps: Figure 2 The steps of the method shown in the figure, the first network side device can be used to perform the following steps: Figure 3 The steps of the method shown in the figure, the second network side device can be used to perform the following steps: Figure 4 The steps of the method shown in the figure, the third network side device can be used to perform the following steps: Figure 5 The steps of the method are shown.

[0660] 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.

[0661] 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.

[0662] 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 method for obtaining slice association information, characterized in that: include: The terminal obtains first information, where the first information is used to indicate an association relationship between a target object and a slice, wherein the target object includes at least one of a target application APP and a target service, and the first information is used to give priority to using the slice associated with the first object when the terminal uses the first object, and the target object includes the first object.

2. The method according to claim 1, characterized in that: The target object includes at least one of the following: The services contracted by the terminal; APP installed on the terminal; The APP that the terminal tends to use; The services that the terminal tends to use; an APP targeted by a first operation, wherein the first operation is a user operation received on the terminal; The service to which the first operation is directed.

3. The method according to claim 2, characterized in that The method further comprises: When the terminal determines, based on the first information, that the slice associated with the target object has changed, the terminal updates the stored association information between the target object and the slice.

4. The method according to any one of claims 1 to 3, characterized in that The method further comprises at least one of the following: The terminal stores the first information in a first entity, wherein the first entity includes a universal subscriber identity module USIM or a management entity ME; When using the first object, the terminal preferentially uses a first slice, wherein the first slice is a slice with the highest priority associated with the first object.

5. The method according to any one of claims 1 to 4, characterized in that The terminal obtains first information, including at least one of the following: The terminal obtains pre-configured first information; The terminal receives an application layer message from an application server, where the application layer message includes the first information; The terminal receives first information from a first network element, where the first network element includes an access and mobility management function AMF network element or a unified data management function UDM network element of a home network; The terminal receives third information from a second network element, where the third information is information obtained by encapsulating the first information in a roaming guidance SOR payload, wherein the second network element includes a UDM network element of a home network.

6. The method according to claim 5, characterized in that The method further comprises: The terminal sends a first request message to the first network element, wherein the first request message is used to request the first information.

7. The method according to claim 6, characterized in that The first request message carries at least one of the following: identification information of the network where the terminal resides; First indication information, where the first indication information indicates that the terminal supports a slice-based network selection function; Target APP information, the target APP information including identification information of the APP that the terminal tends to use or install; Target service information, the target service information including identification information of the service that the terminal tends to use or subscribe to; a first access type, where the first access type is applicable to obtaining the first information, or to using the target APP or the target service; Third indication information, where the third indication information indicates that the first request message is used to request the first information.

8. The method according to any one of claims 5 to 7, characterized in that Before the terminal receives the first information from the application server, the method further includes: The terminal sends a second request message to the application server, wherein the second request message is used to request association information between a first APP and a slice, the target APP includes the first APP, and the application server is a server of the first APP.

9. The method according to claim 8, characterized in that The second request message carries at least one of the following: Identification information of the first APP; identification information of the network where the terminal resides; The first access type is applicable to obtaining the first information or using the first APP.

10. A method for transmitting slice association information, characterized in that: The method comprises: The first network side device sends first information to the terminal, where the first information is used to indicate the association relationship between the target object and the slice, and the target object includes at least one of a target application APP and a target service.

11. The method according to claim 10, characterized in that Before the first network side device sends the first information to the terminal, the method further includes: The first network side device receives a first request message from the terminal, wherein the first request message is used to request the first information; The first network side device obtains second information or third information from the second network side device, wherein the second information is used to indicate the association relationship between at least one application or at least one service of the terminal and their respectively associated slices, or the third information includes the first information encapsulated in the roaming guidance SOR payload.

12. The method according to claim 11, characterized in that The first request message carries at least one of the following: identification information of the network where the terminal resides; First indication information, where the first indication information indicates that the terminal supports a slice-based network selection function; Target APP information, the target APP information including identification information of the APP that the terminal tends to use or install; Target service information, the target service information including identification information of the service that the terminal tends to use or subscribe to; a first access type, where the first access type is applicable to obtaining the first information, or to using the target APP or the target service; Third indication information, where the third indication information indicates that the first request message is used to request the first information.

13. The method according to claim 11 or 12, characterized in that: The first network side device obtains second information from the second network side device, including: The first network side device sends a third request message to the second network side device, wherein the third request message is used to request to obtain slice subscription information of the terminal; The first network side device receives the second information from the second network side device, wherein the second information is used to indicate an association relationship between at least one application or at least one service of the terminal and the respective associated slices; The method further comprises: The first network side device determines the first information according to the second information and the first request message.

14. The method according to claim 11 or 12, characterized in that: The first network side device obtains third information from the second network side device, including: The first network side device sends a third request message to the second network side device; The first network side device receives the third information from the second network side device, wherein the third information includes the first information encapsulated in the SOR payload; The first network side device sends first information to the terminal, including: The first network side device sends the SOR payload to the terminal.

15. The method according to claim 13 or 14, characterized in that The third request message carries at least one of the following: identification information of the terminal; identification information of the network where the terminal resides; First indication information, where the first indication information indicates that the terminal supports a slice-based network selection function; Target APP information, the target APP information including identification information of the APP that the terminal tends to use or install; Target service information, the target service information including identification information of the service that the terminal tends to use or subscribe to; a first access type, where the first access type is applicable to obtaining the first information, or to using the target APP or the target service; Second indication information, the second indication information indicates that the second network side device provides second information to the first network side device, and the second information is used to indicate the association relationship between at least one application or at least one service of the terminal and their respectively associated slices.

16. The method according to claim 13, characterized in that The method further comprises: The first network side device determines the network slice selection auxiliary information NSSAI configured for the terminal based on the second information and the first request message.

17. The method according to claim 16, characterized in that The NSSAI configured for the terminal includes at least one of the following: a slice associated with the target object in the first information; The slice in the first information that is associated with the target object and has the highest priority.

18. The method according to any one of claims 11 to 17, characterized in that In a case where the first request carries identification information of the target object, and the second information does not include association information between the target object and the slice, the method further includes: The first network side device determines that the first information includes at least one of the following: Association information between the target object and the default S-NSSAI; Association information between the target object and the slice in the NSSAI configured for the terminal.

19. A method for transmitting slice association information, characterized in that: The method comprises: The second network side device sends third information to the terminal, where the third information is information obtained by encapsulating the first information in a roaming guidance SOR payload, where the first information is used to indicate an association relationship between a target object and a slice, where the target object includes at least one of a target application APP and a target service; or, The second network side device sends second information to the first network side device, where the second information is used to indicate an association relationship between at least one application or at least one service of the terminal and their respectively associated slices.

20. The method according to claim 19, characterized in that Before the second network side device sends the third information to the terminal, the method further includes: The second network side device receives a third request message from the first network side device, wherein the third request message is used to request the first information; The second network side device sends third information to the terminal, including: When the first condition is met, the second network side device sends the third information to the terminal according to the third request message; or, When the second condition is met, the second network side device sends a fourth request message to the third network side device according to the third request message; The second network side device receives the first information or the updated first information from the third network side device, and sends third information to the terminal, wherein the third information is information obtained by encapsulating the first information or the updated first information in a SOR payload.

21. The method according to claim 20, characterized in that The first condition includes at least one of the following: The terminal supports a network selection function based on slicing; The second network side device locally stores the first information; Locally indicating that the first information is not updated; or, The second condition includes at least one of the following: The terminal supports a network selection function based on slicing; The second network side device does not store the first information locally; The first information is locally indicated to be updated.

22. The method according to claim 20 or 21, characterized in that The fourth request message carries at least one of the following: identification information of the terminal; Target APP information, the target APP information including identification information of the APP that the terminal tends to use or install; Target service information, the target service information including identification information of the service that the terminal tends to use or subscribe to; The first access type is applicable to obtaining the first information, or applicable to using the target APP or the target service.

23. The method according to claim 19, characterized in that Before the second network side device sends the second information to the first network side device, the method further includes: The second network side device receives a third request message from the first network side device, wherein the third request message is used to request to obtain slice subscription information of the terminal; The second network side device sends the second information to the first network side device.

24. The method according to any one of claims 20 to 23, characterized in that The third request message carries at least one of the following: identification information of the terminal; identification information of the network where the terminal resides; First indication information, where the first indication information indicates that the terminal supports a slice-based network selection function; Target APP information, the target APP information including identification information of the APP that the terminal tends to use or install; Target service information, the target service information including identification information of the service that the terminal tends to use or subscribe to; a first access type, where the first access type is applicable to obtaining the first information, or to using the target APP or the target service; Second indication information, the second indication information indicates that the second network side device provides second information to the first network side device, and the second information is used to indicate the association relationship between at least one application or at least one service of the terminal and their respectively associated slices.

25. A method for transmitting slice association information, characterized in that: The method comprises: The third network side device sends the first information or the updated first information to the second network side device, wherein the first information is used to indicate the association relationship between the target object and the slice, and the target object includes at least one of a target application APP and a target service.

26. The method according to claim 25, characterized in that The third network side device sends the first information or the updated first information to the second network side device, including: When the association information between the target object and the slice changes, the third network side device sends the updated first information to the second network side device.

27. The method according to claim 25, characterized in that Before the third network side device sends the first information to the second network side device, the method further includes: The third network side device receives a fourth request message from the second network side device, wherein the fourth request message is used to request the first information or the updated first information.

28. A system for transmitting slice association information, characterized in that: include: terminal; A first network side device, used to send first information to the terminal; or, A second network side device, configured to send third information to the terminal, where the third information includes the first information encapsulated in a roaming guidance SOR payload; Among them, the first information is used to indicate the association relationship between the target object and the slice, the target object includes at least one of a target application APP and a target service, the first information is used to give priority to using the slice associated with the first object when the terminal uses the first object, and the target object includes the first object.

29. The system according to claim 28, characterized in that Before the first network side device sends the first information to the terminal: The terminal is used to send a first request message to the first network side device, wherein the first request message is used to request first information; The first network side device is further used to send a third request message to the second network side device, wherein the third request message is used to request to obtain the slice subscription information of the terminal; The second network side device is further used to send second information to the first network side device, wherein the second information is used to indicate an association relationship between at least one application or at least one service of the terminal and the respectively associated slices; The first network side device is further used to determine the first information according to the second information and the first request message.

30. The system according to claim 29, characterized in that Also includes: A third network side device; The second network side device is specifically used for: When the first condition is met, the second network side device sends the second information to the first network side device according to the third request message; or, When the second condition is met, the second network side device sends a fourth request message to the third network side device according to the third request message; The second network side device receives the second information from the third network side device.

31. The system according to claim 28, characterized in that Before the second network side device sends the third information to the terminal: The terminal is used to send a first request message to the first network side device, wherein the first request message is used to request first information; The first network side device is further used to send a third request message to the second network side device; The second network side device is further configured to determine the first information according to the third request message when the first condition is met, and encapsulate the first information in a SOR payload to obtain the third information; or, The second network side device is further configured to send a fourth request message to the third network side device according to the third request message when the second condition is met; The second network side device is further used to receive the first information from the third network side device, and encapsulate the first information in a SOR payload to obtain the third information.

32. The system according to claim 30 or 31, characterized in that The first condition includes at least one of the following: The terminal supports a network selection function based on slicing; The second network side device locally stores the first information; Locally indicating that the first information is not updated; or, The second condition includes at least one of the following: The terminal supports a network selection function based on slicing; The second network side device does not store the first information locally; The first information is locally indicated to be updated.

33. The system according to claim 29 or 31, characterized in that The first request message carries at least one of the following: identification information of the network where the terminal resides; First indication information, where the first indication information indicates that the terminal supports a slice-based network selection function; Target APP information, the target APP information including identification information of the APP that the terminal tends to use or install; Target service information, the target service information including identification information of the service that the terminal tends to use or subscribe to; a first access type, where the first access type is applicable to obtaining the first information, or to using the target APP or the target service; Third indication information, where the third indication information indicates that the first request message is used to request the first information.

34. A system according to any one of claims 29 to 31, characterized in that The third request message carries at least one of the following: identification information of the terminal; identification information of the network where the terminal resides; First indication information, where the first indication information indicates that the terminal supports a slice-based network selection function; Target APP information, the target APP information including identification information of the APP that the terminal tends to use or install; Target service information, the target service information including identification information of the service that the terminal tends to use or subscribe to; a first access type, where the first access type is applicable to obtaining the first information, or to using the target APP or the target service; Second indication information, the second indication information indicates that the second network side device provides second information to the first network side device, and the second information is used to indicate the association relationship between at least one application or at least one service of the terminal and their respectively associated slices.

35. The system according to claim 30 or 31, characterized in that The fourth request message carries at least one of the following: identification information of the terminal; Target APP information, the target APP information including identification information of the APP that the terminal tends to use or install; Target service information, the target service information including identification information of the service that the terminal tends to use or subscribe to; The first access type is applicable to obtaining the first information, or applicable to using the target APP or the target service.

36. The system of claim 28, wherein: The system further comprises: The third network side device is used to send the updated first information to the second network side device when it is determined that the slice associated with the target object has changed.

37. The system according to claim 36, characterized in that The first network side device is specifically used for: The first network side device receives the updated first information through the second network side device; The first network side device sends the updated first information to the terminal.

38. The system according to claim 36, characterized in that The second network side device is specifically used for: The second network side device encapsulates the updated first information in the SOR payload to obtain the third information; The second network side device sends the third information to the terminal through the first network side device.

39. A device for obtaining slice association information, characterized in that: include: The first acquisition module is used to acquire first information, where the first information is used to indicate an association relationship between a target object and a slice, wherein the target object includes at least one of a target application APP and a target service, and the first information is used to give priority to using the slice associated with the first object when the terminal uses the first object, and the target object includes the first object.

40. A device for transmitting slice association information, characterized in that: include: The first sending module is used to send first information to the terminal, where the first information is used to indicate the association relationship between the target object and the slice, and the target object includes at least one of a target application APP and a target service.

41. A device for transmitting slice association information, characterized in that: include: a second sending module, configured to send third information to the terminal, where the third information is information obtained by encapsulating the first information in a roaming guidance SOR payload, where the first information is used to indicate association information between a target object and a slice, where the target object includes at least one of a target application APP and a target service; or, The third sending module is used to send second information to the first network side device, where the second information is used to indicate the association relationship between at least one application or at least one service of the terminal and their respectively associated slices.

42. A device for transmitting slice association information, characterized in that: include: The fourth sending module is used to send the first information or the updated first information to the second network side device, wherein the first information is used to indicate the association relationship between the target object and the slice, and the target object includes at least one of the target application APP and the target service.

43. A communication device, 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 method for obtaining slice association information as described in any one of claims 1 to 9, or implements the steps of the method for transmitting slice association information as described in any one of claims 10 to 27.

44. 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 method for obtaining slice association information as described in any one of claims 1 to 9, or implements the steps of the method for transmitting slice association information as described in any one of claims 10 to 27.

Images