Ims service acquisition method, terminal, network side device and medium

Abstract

The application discloses an IMS service acquisition method, a terminal, a network side device and a medium, and belongs to the technical field of communication. The IMS service acquisition method comprises the following steps: a terminal receives a URSP rule from a network side device; the terminal acquires IMS information through the URSP rule; and the terminal establishes a PDU session and an IMS signaling connection for the IMS service based on the IMS information.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to an IMS service acquisition method, terminal, network-side equipment, and medium. Background Technology

[0002] Currently, when a terminal uses Internet Protocol Multimedia Subsystem (IMS) services, it first registers with the 5G system (5GS), obtains network slice selection assistance information (NSSAI) from the Access and Mobility Management Function (AMF) entity, and selects a 5G network slice based on this NSSAI to establish a Protocol Data Unit (PDU) session. Then, the terminal accesses IMS through the User Plane Function (UPF) entity to ultimately obtain IMS services. However, when a terminal uses IMS services, the 5G network slice does not involve the IMS network function entity. Therefore, how to obtain IMS services through a two-layer network slicing architecture to provide corresponding quality of service guarantees for different IMS service types is a problem that urgently needs to be solved. Summary of the Invention

[0003] This application provides an IMS service acquisition method, terminal, network-side device, and medium, which can solve the problem of acquiring IMS services through a two-layer network slicing architecture.

[0004] Firstly, an IMS service acquisition method is provided, applied to a terminal. The method includes: the terminal receiving URSP rules from a network-side device; the terminal acquiring IMS information through the URSP rules; and the terminal establishing a PDU session and IMS signaling connection for IMS services based on the IMS information.

[0005] Secondly, an IMS service acquisition device is provided, comprising: a receiving module, an acquisition module, and an establishment module. The receiving module is used to receive URSP rules from network-side equipment; the acquisition module is used to acquire IMS information using the URSP rules received by the receiving module; and the establishment module is used to establish a PDU session and IMS signaling connection for IMS services based on the IMS information acquired by the acquisition module.

[0006] Thirdly, an IMS service acquisition method is provided, applied to a network-side device. The method includes: the network-side device sending URSP rules to the terminal; wherein the URSP rules include IMS information; the IMS information is used by the terminal to establish a PDU session and IMS signaling connection for IMS services.

[0007] Fourthly, an IMS service acquisition device is provided, comprising: a sending module. The sending module is used to send URSP rules to a terminal; wherein the URSP rules include IMS information; the IMS information is used by the terminal to establish a PDU session and IMS signaling connection for IMS service.

[0008] Fifthly, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0009] In a sixth aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used to receive URSP rules from a network-side device; the processor is used to obtain IMS information through the URSP rules, and establish a PDU session and IMS signaling connection for IMS services based on the IMS information.

[0010] In a seventh aspect, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the third aspect.

[0011] Eighthly, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used to send URSP rules to a terminal; wherein the URSP rules include IMS information; the IMS information is used by the terminal to establish a PDU session and an IMS signaling connection for IMS services.

[0012] A ninth aspect provides a communication system comprising: a terminal and a network-side device, wherein the terminal is configured to perform the steps of the IMS service acquisition method as described in the first aspect, and the network-side device is configured to perform the steps of the IMS service acquisition method as described in the third aspect.

[0013] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the third aspect.

[0014] Eleventhly, a chip is provided, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the third aspect.

[0015] In a twelfth aspect, a computer program / program product is provided, which is stored in a storage medium and executed by at least one processor to implement the steps of the IMS service acquisition method as described in the first aspect.

[0016] In this embodiment, the terminal can receive URSP rules from the network-side device and obtain IMS information through these URSP rules. Based on this IMS information, a PDU session and IMS signaling connection for IMS services can be established. Through this solution, the terminal can obtain IMS information through URSP rules and establish a PDU session and IMS signaling connection for IMS services based on this IMS information, thereby enabling the use of 5G network slices and IMS network slices to obtain IMS services, further ensuring the quality of service for IMS services. Attached Figure Description

[0017] Figure 1 This is a schematic diagram of a possible communication system architecture provided in an embodiment of this application;

[0018] Figure 2 A flowchart illustrating an IMS service acquisition method provided in this application embodiment;

[0019] Figure 3 This is one of the structural schematic diagrams of an IMS service acquisition device provided in an embodiment of this application;

[0020] Figure 4 A second schematic diagram of an IMS service acquisition device provided in this application embodiment;

[0021] Figure 5 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0022] Figure 6 This is a schematic diagram of the hardware structure of a terminal according to an embodiment of this application;

[0023] Figure 7 This is a schematic diagram of the structure of a network-side device provided in an embodiment of this application. Detailed Implementation

[0024] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0025] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0026] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, 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), and other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and NR terminology is used in most of the following description; however, these technologies can also be applied to applications beyond NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0027] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. Terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. It should be noted that the specific type of terminal 11 is not limited in this embodiment. Network-side equipment 12 may include access network equipment or core network equipment. Access network equipment 12 may also be referred to as radio access network equipment, radio access network (RAN), radio access network function, or radio access network unit. Access network equipment 12 may include base stations, WLAN access points, or WiFi nodes, etc. Base stations may be referred to as Node B, evolved Node B (eNB), access point, base transceiver station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), home B node, home evolved B node, Transmitting Receiving Point (TRP), or any other suitable term 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 this application embodiment, only a base station in an NR system is used as an example for description, and the specific type of base station is not limited.Core network equipment may include, but is not limited to, at least one of the following: core network node, core network function, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), Binding Support Function (BSF), and Application Function. Function (AF), etc. It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment.

[0028] The IMS service acquisition method provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0029] 1) Network slicing

[0030] Network slicing creates different logical partitions of a network and meets various service requirements through appropriate network isolation and specific configurations. In existing protocols, the slicing operation of a terminal mainly includes the following steps: during initial registration, an AMF is selected, and during this process, permissible single network slice auxiliary information is obtained. Then, the terminal selects a slice according to the network slice selection policy (NSSP) in the user equipment route selection policy (URSP) rules, and queries or selects the relevant NF based on the slice information to request the establishment of a PDU session.

[0031] 2) IMS

[0032] 5GS itself does not provide voice services; terminals access IMS and use voice services through 5GS. For 5GS, both IMS signaling and IMS media belong to user plane data, meaning the terminal needs to establish user plane resources in 5GS before it can use IMS voice services. The user establishes a PDU session with IMS as the DNN, transmitting IMS signaling data, including IMS registration signaling and IMS call signaling, through a Quality of Service (QoS) stream with a "5G QoS identifier (5QI) = 5". During a call, the IMS network, through the PCRF, triggers the network to establish the corresponding QoS stream to transmit IMS media data based on different IMS service types.

[0033] In existing technologies, the terminal first registers with 5GS, obtains an allowable NSSAI from the AMF entity, and selects a 5G network slice based on the NSSAI to establish a PDU session through the 5G network slice. Then, the terminal accesses IMS through UPF to ultimately obtain IMS services. However, when the terminal uses IMS services, the 5G network slice does not involve the IMS network function entity, and 5GS provides the same QoS guarantee for different IMS services through different QoS flows. In order to provide corresponding quality of service guarantees for different IMS service types (such as real-time audio, real-time video, instant messaging, etc.), how to obtain IMS services through a two-layer network slicing architecture has become an urgent problem to be solved.

[0034] To address the aforementioned technical issues, this application provides a method for a terminal to obtain IMS services using a two-layer network slicing architecture. Specifically, an IMS network slice is added to the existing 5G network slice, enabling the use of complete IMS network functions based on the IMS network slice. Specifically, IMS information is added to the URSP rules, allowing the terminal to obtain IMS information through these rules. Based on this IMS information, a PDU session and IMS signaling connection for IMS services are established, thereby enabling the use of both 5G and IMS network slices to obtain IMS services.

[0035] This application provides a method for obtaining IMS services. Figure 2 A flowchart illustrating an IMS service acquisition method provided in an embodiment of this application is shown. Figure 2 As shown, the IMS service acquisition method provided in this application embodiment includes the following steps 201 to 204.

[0036] Step 201: The network-side device sends URSP rules to the terminal.

[0037] In this embodiment of the application, the URSP rule mentioned above includes IMS information; the IMS information is used by the terminal to establish a PDU session and IMS signaling connection for IMS service.

[0038] In this embodiment of the application, the terminal can receive URSP rules from the network-side device and obtain IMS information through the URSP rules. Based on the IMS information, a PDU session and IMS signaling connection for IMS service can be established, thereby enabling the use of 5G network slices and IMS network slices to obtain IMS service.

[0039] Optionally, in this embodiment of the application, the URSP rule mentioned above can be pre-configured on the terminal by the network-side device, or it can be currently configured on the terminal by the network-side device.

[0040] Optionally, in the embodiments of this application, the above-mentioned IMS information includes at least one of the following: IMS slice information, P-CSCF address indication information, and IMS data network name.

[0041] The P-CSCF address indication information is used to indicate the address of the P-CSCF (e.g., the IP address of the P-CSCF).

[0042] Optionally, in this embodiment, the IMS slice information may include the identifier of the IMS slice; the P-CSCF address indication information is used to indicate the entry information of the IMS service requested by the terminal. The P-CSCF is the entry point for the UE to request IMS service from the IMS network.

[0043] Optionally, in this embodiment of the application, the above-mentioned IMS slice information includes single network slice selection assistance information (S-NSSAI), which includes slice / service type (SST) and slice differentiator (SD).

[0044] In this case, SST indicates the service type as IMS, and SD is used to indicate the type of IMS service; or, SST indicates the service type as a service type other than IMS, and SD is used to indicate the type of IMS service.

[0045] It should be noted that the service type indicated by the SST above, "IMS," can be understood as the newly added IMS type in SST. The service type indicated by the SST above, excluding IMS, can be understood as the existing service types in SST.

[0046] For example, as shown in Table 1, a new IMS type is added to SST.

[0047] Table 1. Service Types and Characteristics Indicated by SST

[0048]

[0049] Optionally, in this embodiment of the application, different IMS services are distinguished by different SD codes. For example, multimedia telephony (MMTel) voice service, multimedia telephony video service, and mobile originate (MO) IMS registration-related signalling correspond to different SD codes, and the specific encoding method depends on the operator's implementation.

[0050] Step 202: The terminal receives URSP rules from the network-side device.

[0051] Step 203: The terminal obtains IMS information through URSP rules.

[0052] Optionally, in this embodiment of the application, the terminal can obtain IMS information from URSP rules.

[0053] Optionally, in the embodiments of this application, when the IMS information includes IMS slice information, the route selection descriptor (RSD) in the URSP rule includes an IMS slice selection component, which includes IMS slice information; or, the network slice selection component in the RSD includes IMS slice information.

[0054] It is understandable that network-side devices can add an IMS slice selection component to the RSD in the traffic descriptor of the URSP rule, and the terminal can obtain IMS slice information from the IMS slice selection component; or, network-side devices can add IMS slice information to the network slice selection component in the RSD, and the terminal can obtain IMS slice information from the network slice selection component.

[0055] Optionally, in this embodiment, the IMS slice selection component is used to indicate the IMS slice that matches the IMS session. Specifically, the IMS slice selection component is used to indicate that traffic for the matching IMS service should be routed through any IMS session that supports IMS S-NSSAI. The IMS slice selection component includes at least one IMS S-NSSAI.

[0056] In other words, network-side devices can add new components to the RSD, which include IMS slice information, or add IMS slice information to existing components in the RSD.

[0057] For example, as shown in Table 2, the network-side device adds an IMS slice selection component to the RSD, which includes IMS slice information; or, the network-side device adds IMS slice information to the network slice selection component in the RSD.

[0058] Table 2 RSD and related explanations

[0059]

[0060] Table 2 RSD and related explanations

[0061]

[0062] Optionally, in this embodiment, the terminal can obtain IMS information and 5G slice information through URSP rules. In one implementation, when the network-side device adds IMS slice information to the network slice selection component in the RSD, the terminal can obtain IMS information and 5G slice information through the network slice selection component; in another implementation, when the network-side device adds an IMS slice selection component to the RSD, the terminal can obtain 5G slice information through the network slice selection component and IMS information through the IMS slice selection component.

[0063] Optionally, in this embodiment of the application, when the IMS information includes P-CSCF address indication information, the RSD in the URSP rule includes a P-CSCF selection component, which includes P-CSCF address indication information.

[0064] It is understandable that network-side devices can add a P-CSCF selection component to the RSD in the traffic descriptor of the URSP rule, and the terminal can obtain the P-CSCF address indication information from the P-CSCF selection component.

[0065] Optionally, in this embodiment, the P-CSCF selection component is used to indicate the P-CSCF that matches the IMS session. Furthermore, the P-CSCF selection component is used to indicate that traffic for the matching IMS service should be routed through any IMS session that supports a P-CSCF IP address. The P-CSCF selection component includes one or more P-CSCF IP addresses.

[0066] In other words, network-side devices can add new components to the RSD, which include P-CSCF address indication information.

[0067] For example, as shown in Table 3, the network-side device adds a P-CSCF selection component to the RSD, which includes P-CSCF address indication information.

[0068] Table 3 RSD and related explanations

[0069]

[0070] Optionally, in this embodiment of the application, before step 203 above, the IMS service acquisition method provided in this embodiment of the application further includes the following step 301.

[0071] Step 301: The terminal obtains IMS service instruction information.

[0072] The aforementioned IMS service indication information includes at least one of the following: application identifier of IMS service, demand indication information, and IMS connection capability indication information;

[0073] The above requirement information is used to indicate the type of IMS service;

[0074] The aforementioned IMS connectivity indication information is used to request a network connection with IMS capability;

[0075] The above IMS information is the information in the URSP rules that matches the type of IMS service.

[0076] Optionally, in this embodiment, the terminal obtaining IMS service indication information may include: the terminal receiving IMS service indication information from an upper layer. Optionally, "upper layer" may be the NAS layer, RRC layer, or application layer, and this embodiment does not specifically limit it.

[0077] Optionally, in this embodiment, the type of IMS service can be real-time audio service, real-time video service, and instant messaging, etc. The specific type can be determined according to actual usage needs, and this embodiment does not impose any limitations.

[0078] Optionally, in this embodiment of the application, the URSP rule includes a traffic descriptor that matches the IMS service indication information, or the application descriptor in the URSP rule includes information that matches the IMS service indication information.

[0079] It can be understood that the above IMS information can be a traffic descriptor in the URSP rule that matches the IMS service indication information; or, the above IMS information can be information in the application descriptor in the URSP rule that matches the IMS service indication information.

[0080] Optionally, in this embodiment of the application, the information that matches the IMS service indication information may be: information that matches the application identifier of the IMS service and / or information that matches the demand indication information.

[0081] For example, suppose the information matching the IMS service requirement indication is the information matching the requirement indication. As shown in Table 4, the URSP rule includes a traffic descriptor that matches the requirement indication, i.e., the IMS service requirement indication; or, the application descriptors in the URSP rule include information that matches the IMS service requirement indication, i.e., the IMS service requirement indication.

[0082] Table 4. Flow descriptors and related explanations

[0083]

[0084] Optionally, in this embodiment of the application, the above-mentioned IMS service requirement indication may be in the form of IMS service ID or IMS service type, and may also be in any other possible form. The specific form can be determined according to actual usage requirements, and this embodiment of the application does not impose any restrictions.

[0085] In this embodiment, the terminal can obtain IMS information matching the IMS service indication information from the URSP rules based on the IMS service indication information, and establish a PDU session and IMS signaling connection for the IMS service based on the IMS information, thereby realizing the use of 5G network slices and IMS network slices to obtain IMS services, further ensuring the service quality of IMS services.

[0086] The following describes in detail the method for the terminal to obtain IMS information through URSP rules in this application embodiment, based on different IMS service indication information, through three cases.

[0087] Optionally, in the embodiments of this application, in the first case, the aforementioned IMS service indication information includes demand indication information. Step 203 can be specifically implemented through step 203a as described below.

[0088] Step 203a: The terminal determines the first URSP rule and the second URSP rule from the URSP rules according to the demand instruction information.

[0089] The aforementioned IMS information is the information in the second URSP rule; the aforementioned first URSP rule is used to establish a PDU session, and the aforementioned second URSP rule is used to establish an IMS signaling connection.

[0090] Optionally, in the embodiments of this application, in the first implementation, the terminal can determine the first URSP rule and the second URSP rule from the URSP rules according to the demand indication information; in the second implementation, the terminal can determine the first URSP rule according to the demand indication information, and determine the second URSP rule according to the demand indication information and the IMS connectivity indication information; in the third implementation, the terminal can determine the first URSP rule according to the demand indication information and the IMS connectivity indication information, and determine the second URSP rule according to the demand indication information; in the fourth implementation, the terminal can determine the first URSP rule and the second URSP rule according to the demand indication information and the IMS connectivity indication information.

[0091] Optionally, in this embodiment of the application, the first URSP rule and the second URSP rule have the same data network name, thereby associating the PDU session and the IMS signaling connection.

[0092] In this embodiment, the terminal can determine the first URSP rule and the second URSP rule from the URSP rules according to the demand indication information, so as to establish a PDU session using the first URSP rule and establish an IMS signaling connection using the second URSP rule, thereby realizing the use of 5G network slices and IMS network slices to obtain IMS services, and further ensuring the service quality of IMS services.

[0093] Optionally, in the second case of this application embodiment, the aforementioned IMS service indication information includes application identifier and demand indication information. Step 203 can be specifically implemented through steps 203b and 203c as described below.

[0094] Step 203b: The terminal determines the first URSP rule from the URSP rules based on the application identifier.

[0095] Step 203c: The terminal determines the second URSP rule from the URSP rules based on the demand instruction information.

[0096] The aforementioned IMS information is the information in the second URSP rule; the aforementioned first URSP rule is used to establish a PDU session, and the aforementioned second URSP rule is used to establish an IMS signaling connection.

[0097] For example, as shown in Table 5, the terminal can determine the URSP rule (i.e., the first URSP rule) for application identifier APP3 based on the application identifier, and determine the URSP rule (i.e., the second URSP rule) for requirement indication information IMS service3 based on the requirement indication information.

[0098] Table 5 URSP Rules and Related Explanations

[0099]

[0100] Optionally, in this embodiment of the application, the IMS service indication information may further include IMS connectivity indication information. Step 203b can be specifically implemented through step 203b1, and step 203c can be specifically implemented through step 203c1.

[0101] Step 203b1: The terminal determines the first URSP rule from the URSP rules based on the application identifier and IMS connection capability indication information.

[0102] Step 203c1: The terminal determines the second URSP rule from the URSP rules based on the demand indication information and the IMS connection capability indication information.

[0103] Optionally, in this embodiment of the application, the first URSP rule and the second URSP rule have the same data network name, thereby associating the PDU session and the IMS signaling connection.

[0104] Optionally, in this embodiment of the application, after determining the first URSP rule, the terminal can determine the third RSD from the first URSP rule; and after determining the second URSP rule, the terminal can determine the fourth RSD from the second URSP rule.

[0105] Optionally, in this embodiment, the terminal can determine the third RSD from the first URSP rule and the fourth RSD from the second URSP rule based on the preference indication of the IMS service and the terminal's configuration information. Furthermore, the terminal can also determine the third and fourth RSDs based on other information from the IMS service; the specific determination can be made according to actual usage requirements, and this embodiment does not impose any limitations.

[0106] It can be understood that the third RSD mentioned above is the RSD that best matches the current IMS service in the first URSP rule, that is, the optimal RSD in the first URSP rule; the fourth RSD mentioned above is the RSD that best matches the current IMS service in the second URSP rule, that is, the optimal RSD in the second URSP rule.

[0107] In this embodiment, the terminal can determine a first URSP rule from the URSP rules based on the application identifier, and determine a second URSP rule from the URSP rules based on the demand indication information, so as to establish a PDU session using the first URSP rule and establish an IMS signaling connection using the second URSP rule, thereby realizing the use of 5G network slices and IMS network slices to obtain IMS services, further ensuring the service quality of IMS services.

[0108] Optionally, in the third case of this application embodiment, the aforementioned IMS service indication information includes application identifier or demand indication information. Step 203 can be specifically implemented through steps 203d and 203e below.

[0109] Step 203d: The terminal determines the third URSP rule from the URSP rules based on the application identifier or requirement indication information.

[0110] Step 203e: The terminal determines the first RSD and the second RSD from the third URSP rule.

[0111] The IMS information mentioned above is the information in the second RSD; the first RSD is used to establish a PDU session, and the second RSD is used to establish an IMS signaling connection.

[0112] For example, as shown in Table 6, assuming that the IMS service indication information includes demand indication information, the terminal can determine the URSP rule (i.e., the third URSP rule) of the demand indication information as IMS service3 based on the demand indication information, and determine the RSD (i.e., the first RSD) belonging to the PDU session and the RSD (i.e., the second RSD) belonging to the IMS signaling connection from the URSP rule.

[0113] Table 6 URSP Rules and Related Explanations

[0114]

[0115] Optionally, in this embodiment of the application, the aforementioned IMS service indication information may further include IMS connectivity indication information. That is, the terminal determines a third URSP rule from the URSP rules based on the application identifier and the IMS connectivity indication information; or, the terminal determines a third URSP rule from the URSP rules based on the demand indication information and the IMS connectivity indication information.

[0116] Optionally, in this embodiment, the terminal can determine the first RSD and the second RSD from the third URSP rules based on the preference indication of the IMS service, the terminal's configuration information, etc. Furthermore, the terminal can also determine the first RSD and the second RSD from the third URSP rules based on other information from the IMS service. The specific determination can be made according to actual usage requirements, and this embodiment does not impose any limitations.

[0117] It can be understood that the first RSD and the second RSD mentioned above are the two RSDs in the third URSP rule that best match the current IMS service, that is, the two optimal RSDs.

[0118] Optionally, in this embodiment, the terminal can obtain IMS information and 5G slice information through URSP rules. In one implementation, when the network-side device adds IMS slice information to the network slice selection component in the RSD, the terminal can obtain IMS information and 5G slice information through the network slice selection component; in another implementation, when the network-side device adds an IMS slice selection component to the RSD, the terminal can obtain 5G slice information through the network slice selection component and IMS information through the IMS slice selection component.

[0119] In this embodiment, the terminal can determine a third URSP rule from the URSP rules based on the application identifier or demand indication information, and determine a first RSD and a second RSD from the second URSP rules, so as to establish a PDU session using the first RSD and establish an IMS signaling connection using the second RSD, thereby realizing the use of 5G network slices and IMS network slices to obtain IMS services, and further ensuring the service quality of IMS services.

[0120] Step 204: The terminal establishes a PDU session and IMS signaling connection for IMS services based on IMS information.

[0121] Optionally, in this embodiment of the application, the terminal can establish a PDU session for IMS service based on the 5G slice information in the URSP rules, and establish an IMS signaling connection based on the IMS information in the URSP rules.

[0122] Optionally, in this embodiment of the application, the terminal may carry IMS information (including S-NSSAI indicating IMS) in the PDU session establishment request message and send it to the UPF through the SMF, so that the UPF can access the appropriate P-CSCF according to the P-CSCF address indication information in the IMS information, and the P-CSCF can select other IMS network elements according to the IMS slice information in the IMS information.

[0123] It should be noted that in traditional solutions, since the PDU session establishment request message only carries the 5G system's S-NSSAI and not IMS information, the SMF typically selects a P-CSCF for the terminal based on operator policies and local configuration information, enabling the UPF to access that P-CSCF. In contrast to traditional solutions, this embodiment can select a suitable P-CSCF for the terminal based on IMS information. Furthermore, different P-CSCFs can be selected for different IMS services. In other words, a customized P-CSCF can be selected for the terminal for each IMS service. This provides customized resource configuration for different IMS services, meeting the service requirements of different IMS services and thus providing more efficient and high-quality IMS services to the terminal.

[0124] Optionally, in this embodiment, the terminal can perform registration and session initialization procedures based on IMS information. Furthermore, when different IMS services arrive, the UE uses different IMS services through the established PDU and different bearers.

[0125] Optionally, in this embodiment of the application, the terminal may first establish a PDU session and then establish an IMS signaling connection to use the IMS service.

[0126] This application provides a method for obtaining IMS services. A terminal can receive URSP rules from a network-side device and obtain IMS information through these URSP rules. Based on this IMS information, a PDU session and IMS signaling connection for IMS services can be established. Through this solution, the terminal can obtain IMS information through URSP rules and establish a PDU session and IMS signaling connection for IMS services based on this information, thereby enabling the use of 5G network slices and IMS network slices to obtain IMS services, further ensuring the quality of service for IMS services.

[0127] Optionally, in this embodiment of the application, before step 201 above, the IMS service acquisition method provided in this embodiment of the application further includes steps 401 to 404 as described below.

[0128] Step 401: The terminal sends IMS slicing capability indication information to the network-side device.

[0129] In this embodiment of the application, the above-mentioned IMS slicing capability indication information is used to indicate that the terminal supports using IMS services based on IMS slices.

[0130] Optionally, in this embodiment of the application, the terminal can perform a registration process in the 5G system and send IMS slicing capability indication information to the network-side device during the registration process.

[0131] Optionally, in this embodiment of the application, the IMS slice capability indication information can be transmitted during the initial registration of the terminal; or, the IMS slice capability indication information can be transmitted during the mobility registration update process.

[0132] Step 402: The network-side device receives the IMS slicing capability indication information sent by the terminal.

[0133] Step 403: The network-side device sends a first instruction message to the terminal.

[0134] In this embodiment of the application, the first instruction message is used to instruct the terminal to use IMS services based on IMS slices.

[0135] Optionally, in this embodiment of the application, after receiving the IMS slicing capability indication information of the terminal, the network-side device can indicate to the terminal whether to allow the terminal to use IMS services based on information such as the terminal's subscription, network policy, and local configuration.

[0136] Step 404: The terminal receives the first instruction message sent by the network-side device.

[0137] In this embodiment of the application, during the registration process, the terminal can indicate to the network-side device that the terminal supports using IMS services based on IMS slices. The terminal will only use IMS services if the network-side device indicates that the terminal is allowed to use IMS services based on IMS slices, thereby further ensuring the service quality of the terminal using IMS services.

[0138] The IMS service acquisition method provided in this application can be executed by an IMS service acquisition device. This application uses an IMS service acquisition device executing the IMS service acquisition method as an example to illustrate the IMS service acquisition device provided in this application.

[0139] This application provides an IMS service acquisition device, applied to a terminal, such as... Figure 3 As shown, the IMS service acquisition device 500 includes a receiving module 501, an acquisition module 502, and an establishment module 503. The receiving module 501 receives URSP rules from network-side devices. The acquisition module 502 acquires IMS information based on the URSP rules received by the receiving module 501. The establishment module 503 establishes a PDU session and IMS signaling connection for IMS services based on the IMS information acquired by the acquisition module 502.

[0140] The IMS service acquisition device provided in this application embodiment can obtain IMS information through URSP rules, and establish a PDU session and IMS signaling connection for IMS service based on the IMS information, thereby realizing the acquisition of IMS service using 5G network slice and IMS network slice, and further ensuring the service quality of IMS service.

[0141] Optionally, in this embodiment of the application, the above-mentioned IMS information includes at least one of the following: IMS slice information, P-CSCF address indication information, and IMS data network name; wherein, the P-CSCF address indication information is used for P-CSCF address.

[0142] Optionally, in this embodiment of the application, the above-mentioned IMS information includes IMS slice information;

[0143] Specifically, the RSD in the aforementioned URSP rule includes an IMS slice selection component, which in turn includes IMS slice information; or, the network slice selection component in the RSD includes IMS slice information.

[0144] Optionally, in this embodiment of the application, the above-mentioned IMS information includes P-CSCF address indication information;

[0145] The RSD in the aforementioned URSP rule includes a P-CSCF selection component, which in turn includes P-CSCF address indication information.

[0146] Optionally, in this embodiment of the application, the above-mentioned acquisition module 502 is further configured to acquire IMS service indication information before acquiring IMS information through URSP rules;

[0147] The aforementioned IMS service indication information includes at least one of the following: application identifier of IMS service, demand indication information, and IMS connection capability indication information;

[0148] The above requirement information is used to indicate the type of IMS service;

[0149] The aforementioned IMS connectivity indication information is used to request a network connection with IMS capability;

[0150] The above IMS information is the information in the URSP rules that matches the type of IMS service.

[0151] Optionally, in the embodiments of this application, the above-mentioned URSP rule includes a traffic descriptor that matches the IMS service indication information, or the application descriptor in the above-mentioned URSP rule includes information that matches the IMS service indication information.

[0152] Optionally, in this embodiment of the application, the IMS service indication information includes demand indication information; the acquisition module 502 is specifically used to determine the first URSP rule and the second URSP rule from the URSP rules according to the demand indication information.

[0153] The IMS information is the information in the second URSP rule; the first URSP rule is used to establish a PDU session, and the second URSP rule is used to establish an IMS signaling connection.

[0154] Optionally, in this embodiment of the application, the IMS service indication information includes an application identifier and a demand indication information; the acquisition module 502 is specifically used to determine a first URSP rule from the URSP rules based on the application identifier; and to determine a second URSP rule from the URSP rules based on the demand indication information.

[0155] The IMS information is the information in the second URSP rule; the first URSP rule is used to establish a PDU session, and the second URSP rule is used to establish an IMS signaling connection.

[0156] Optionally, in this embodiment of the application, the IMS service indication information includes application identifier or demand indication information; the acquisition module 502 is specifically used to determine a third URSP rule from the URSP rules based on the application identifier or demand indication information; and to determine a first RSD and a second RSD from the third URSP rule.

[0157] The IMS information is the information in the second RSD; the first RSD is used to establish a PDU session, and the second RSD is used to establish an IMS signaling connection.

[0158] Optionally, in this embodiment of the application, the above-mentioned IMS slice information includes S-NSSAI, which includes SST and SD;

[0159] In this case, SST indicates the service type as IMS, and SD is used to indicate the type of IMS service; or, SST indicates the service type as a service type other than IMS, and SD is used to indicate the type of IMS service.

[0160] Optionally, in this embodiment, the apparatus 500 further includes a sending module. The sending module is configured to send IMS slice capability indication information to the network-side device before the acquisition module 502 acquires IMS information through URSP rules. This IMS slice capability indication information is used to indicate that the terminal supports using IMS services based on IMS slices. The receiving module 501 is further configured to receive a first indication message sent by the network-side device. This first indication message is used to indicate that the terminal is allowed to use IMS services based on IMS slices.

[0161] This application also provides an IMS service acquisition device, applied to network-side devices, such as... Figure 4 As shown, the IMS service acquisition device 600 includes a sending module 601. The sending module 601 is used to send URSP rules to the terminal. The URSP rules include IMS information; this IMS information is used by the terminal to establish a PDU session and IMS signaling connection for IMS services.

[0162] The IMS service acquisition device provided in this application embodiment can send URSP rules including IMS information to the terminal, so that the terminal can establish a PDU session and IMS signaling connection for IMS service based on the IMS information, thereby realizing the acquisition of IMS service using 5G network slice and IMS network slice, and further ensuring the service quality of IMS service.

[0163] Optionally, in this embodiment of the application, the above-mentioned IMS information includes at least one of the following: IMS slice information, P-CSCF address indication information, and IMS data network name; wherein, the P-CSCF address indication information is used to indicate the address of the P-CSCF.

[0164] Optionally, in this embodiment of the application, the above-mentioned IMS information includes IMS slice information;

[0165] Specifically, the RSD in the aforementioned URSP rule includes an IMS slice selection component, which in turn includes IMS slice information; or, the network slice selection component in the RSD includes IMS slice information.

[0166] Optionally, in this embodiment of the application, the above-mentioned IMS information includes P-CSCF address indication information;

[0167] The RSD in the aforementioned URSP rule includes a P-CSCF selection component, which in turn includes P-CSCF address indication information.

[0168] Optionally, in this embodiment of the application, the above-mentioned IMS slice information includes S-NSSAI, which includes SST and SD;

[0169] In this case, SST indicates the service type as IMS, and SD is used to indicate the type of IMS service; or, SST indicates the service type as a service type other than IMS, and SD is used to indicate the type of IMS service.

[0170] Optionally, in this embodiment of the application, the apparatus 600 further includes a receiving module. The receiving module is configured to receive IMS slice capability indication information sent by the terminal before the sending module 601 sends URSP rules to the terminal. This IMS slice capability indication information is used to indicate that the terminal supports using IMS services based on IMS slices. The sending module 601 is further configured to send a first indication message to the terminal, which indicates that the terminal is allowed to use IMS services based on IMS slices.

[0171] The IMS service acquisition device in this application embodiment can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal or other devices besides a terminal. For example, the terminal can include, but is not limited to, the type of terminal 11 listed above; other devices can be servers, network attached storage (NAS), etc., and this application embodiment does not specifically limit the type.

[0172] The IMS service acquisition device provided in this application embodiment can achieve... Figure 2 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0173] Optional, such as Figure 5 As shown, this application embodiment also provides a communication device 700, including a processor 701 and a memory 702. The memory 702 stores programs or instructions that can run on the processor 701. For example, when the communication device 700 is a terminal, the program or instructions executed by the processor 701 implement the various steps of the terminal in the above-described IMS service acquisition method embodiment, and achieve the same technical effect. When the communication device 700 is a network-side device, the program or instructions executed by the processor 701 implement the various steps of the network-side device in the above-described IMS service acquisition method embodiment, and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0174] This application also provides a terminal, including a processor and a communication interface. The communication interface is used to receive URSP rules from a network-side device, and the processor is used to obtain IMS information through the URSP rules, and establish a PDU session and IMS signaling connection for IMS services based on the IMS information. This terminal embodiment corresponds to the above-described terminal-side method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and achieve the same technical effects. Specifically, Figure 6 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0175] The terminal 800 includes, but is not limited to, at least some of the following components: radio frequency unit 801, network module 802, audio output unit 803, input unit 804, sensor 805, display unit 806, user input unit 807, interface unit 808, memory 809, and processor 810.

[0176] Those skilled in the art will understand that the terminal 800 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 810 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 6 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0177] It should be understood that, in this embodiment, the input unit 804 may include a graphics processing unit (GPU) 8041 and a microphone 8042. The GPU 8041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 806 may include a display panel 8061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 807 includes at least one of a touch panel 8071 and other input devices 8072. The touch panel 8071 is also called a touch screen. The touch panel 8071 may include a touch detection device and a touch controller. Other input devices 8072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0178] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 801 can transmit it to the processor 810 for processing; in addition, the radio frequency unit 801 can send uplink data to the network-side device. Typically, the radio frequency unit 801 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

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

[0180] Processor 810 may include one or more processing units; optionally, processor 810 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 810.

[0181] The radio frequency unit 801 is used to receive URSP rules from network-side equipment. The processor 810 is used to obtain IMS information through URSP rules and establish PDU sessions and IMS signaling connections for IMS services based on the IMS information.

[0182] This application provides a terminal that can obtain IMS information through URSP rules and establish a PDU session and IMS signaling connection for IMS services based on the IMS information, thereby enabling the use of 5G network slices and IMS network slices to obtain IMS services, further ensuring the quality of IMS services.

[0183] Optionally, in this embodiment of the application, the processor 810 is further configured to obtain IMS service indication information;

[0184] The aforementioned IMS service indication information includes at least one of the following: application identifier of IMS service, demand indication information, and IMS connection capability indication information;

[0185] The above requirement information is used to indicate the type of IMS service;

[0186] The aforementioned IMS connectivity indication information is used to request a network connection with IMS capability;

[0187] The above IMS information is the information in the URSP rules that matches the type of IMS service.

[0188] Optionally, in this embodiment of the application, the above-mentioned IMS service indication information includes demand indication information; the processor 810 is specifically used to determine the first URSP rule and the second URSP rule from the URSP rules according to the demand indication information;

[0189] The IMS information is the information in the second URSP rule; the first URSP rule is used to establish a PDU session, and the second URSP rule is used to establish an IMS signaling connection.

[0190] Optionally, in this embodiment of the application, the above-mentioned IMS service indication information includes an application identifier and a demand indication information; the processor 810 is specifically used to determine a first URSP rule from the URSP rules according to the application identifier; and to determine a second URSP rule from the URSP rules according to the demand indication information;

[0191] The IMS information is the information in the second URSP rule; the first URSP rule is used to establish a PDU session, and the second URSP rule is used to establish an IMS signaling connection.

[0192] Optionally, in this embodiment of the application, the above-mentioned IMS service indication information includes application identifier or demand indication information; the processor 810 is specifically used to determine a third URSP rule from the URSP rules according to the application identifier or demand indication information; and to determine a first RSD and a second RSD from the third URSP rule;

[0193] The IMS information is the information in the second RSD; the first RSD is used to establish a PDU session, and the second RSD is used to establish an IMS signaling connection.

[0194] Optionally, in this embodiment of the application, the radio frequency unit 801 is further configured to send IMS slice capability indication information to the network-side device, the IMS slice capability indication information being used to indicate that the terminal supports using IMS services based on IMS slices; and to receive a first indication message sent by the network-side device, the first indication message being used to indicate that the terminal is allowed to use IMS services based on IMS slices.

[0195] This application also provides a network-side device, including a processor and a communication interface. The communication interface is used to send URSP rules to a terminal. The URSP rules include IMS information. The IMS information is used by the terminal to establish a PDU session and an IMS signaling connection for IMS services. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above method embodiments can be applied to this network-side device embodiment and achieve the same technical effects.

[0196] Specifically, embodiments of this application also provide a network-side device. For example... Figure 7 As shown, the network-side device 900 includes a processor 901, a network interface 902, and a memory 903. The network interface 902 is, for example, a common public radio interface (CPRI).

[0197] Specifically, the network-side device 900 of this embodiment further includes: instructions or programs stored in a memory 903 and executable on a processor 901, wherein the processor 901 calls the instructions or programs in the memory 903 to execute. Figure 4 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0198] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described IMS service acquisition method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0199] The processor is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0200] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described IMS service acquisition method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0201] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0202] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described IMS service acquisition method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0203] This application also provides a communication system, including: a terminal and a network-side device, wherein the terminal can be used to execute the steps of the IMS service acquisition method described above, and the network-side device can be used to execute the steps of the IMS service acquisition method described above.

[0204] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0205] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0206] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for obtaining Internet Protocol Multimedia Subsystem (IMS) services, characterized in that, include: The terminal receives the Terminal Routing Policy (URSP) rules from the network-side device. The terminal obtains IMS information through the URSP rules; Based on the IMS information, the terminal establishes a Protocol Data Unit (PDU) session and an IMS signaling connection for IMS services; When the IMS information includes IMS slice information, the routing descriptor RSD in the URSP rule includes an IMS slice selection component, and the IMS slice selection component includes the IMS slice information; or, the network slice selection component in the RSD includes the IMS slice information. When the IMS information includes P-CSCF address indication information, the RSD in the URSP rule includes a P-CSCF selection component, and the P-CSCF selection component includes the P-CSCF address indication information, which is used to indicate the P-CSCF matched by the IMS session.

2. The method according to claim 1, characterized in that, The IMS information also includes: the IMS data network name.

3. The method according to claim 1, characterized in that, Before the terminal obtains IMS information through the URSP rules, the method further includes: The terminal obtains IMS service indication information; The IMS service indication information includes at least one of the following: the application identifier of the IMS service, the demand indication information, and the IMS connection capability indication information; The demand indication information is used to indicate the type of the IMS service; The IMS connectivity indication information is used to request a network connection with IMS capability. The IMS information is the information in the URSP rule that matches the type of the IMS service.

4. The method according to claim 3, characterized in that, The URSP rule includes a traffic descriptor that matches the IMS service indication information, or the application descriptor in the URSP rule includes information that matches the IMS service indication information.

5. The method according to claim 3 or 4, characterized in that, The IMS service indication information includes the demand indication information; The terminal obtains IMS information through the URSP rules, including: The terminal determines the first URSP rule and the second URSP rule from the URSP rules based on the demand indication information; The IMS information is the information in the second URSP rule; the first URSP rule is used to establish the PDU session, and the second URSP rule is used to establish the IMS signaling connection.

6. The method according to claim 3 or 4, characterized in that, The IMS service indication information includes the application identifier and the demand indication information; The terminal obtains IMS information through the URSP rules, including: The terminal determines a first URSP rule from the URSP rules based on the application identifier; The terminal determines a second URSP rule from the URSP rules based on the demand indication information; The IMS information is the information in the second URSP rule; the first URSP rule is used to establish the PDU session, and the second URSP rule is used to establish the IMS signaling connection.

7. The method according to claim 3 or 4, characterized in that, The IMS service indication information includes the application identifier or the demand indication information; The terminal obtains IMS information through the URSP rules, including: The terminal determines a third URSP rule from the URSP rules based on the application identifier or the demand indication information; The terminal determines the first RSD and the second RSD from the third URSP rule; The IMS information is the information in the second RSD; the first RSD is used to establish the PDU session, and the second RSD is used to establish the IMS signaling connection.

8. The method according to claim 2, characterized in that, The IMS slice information includes Single Network Slice Auxiliary Information (S-NSSAI), which includes Slice Service Type (SST) and Slice Distinguisor (SD). Wherein, the service type indicated by SST is IMS, and the SD is used to indicate the type of IMS service; or, the service type indicated by SST is a service type other than IMS, and the SD is used to indicate the type of IMS service.

9. The method according to claim 1, characterized in that, Before the terminal obtains IMS information through the URSP rules, the method further includes: The terminal sends IMS slicing capability indication information to the network-side device. The IMS slicing capability indication information is used to indicate that the terminal supports using the IMS service based on IMS slicing. The terminal receives a first indication message sent by the network-side device, the first indication message being used to indicate that the terminal is allowed to use the IMS service based on IMS slices.

10. A method for obtaining IMS services, characterized in that, include: Network-side devices send URSP rules to terminals; The URSP rules include IMS information; the IMS information is used by the terminal to establish a PDU session and IMS signaling connection for IMS services. When the IMS information includes IMS slice information, the routing descriptor RSD in the URSP rule includes an IMS slice selection component, and the IMS slice selection component includes the IMS slice information; or, the network slice selection component in the RSD includes the IMS slice information. When the IMS information includes P-CSCF address indication information, the RSD in the URSP rule includes a P-CSCF selection component, and the P-CSCF selection component includes the P-CSCF address indication information, which is used to indicate the P-CSCF matched by the IMS session.

11. The method according to claim 10, characterized in that, The IMS information also includes: the IMS data network name.

12. The method according to claim 11, characterized in that, The IMS slice information includes S-NSSAI, which includes SST and SD; Wherein, the service type indicated by SST is IMS, and the SD is used to indicate the type of IMS service; or, the service type indicated by SST is a service type other than IMS, and the SD is used to indicate the type of IMS service.

13. The method according to claim 10, characterized in that, Before the network-side device sends URSP rules to the terminal, the method further includes: The network-side device receives IMS slice capability indication information sent by the terminal, and the IMS slice capability indication information is used to indicate that the terminal supports using the IMS service based on IMS slice; The network-side device sends a first indication message to the terminal, the first indication message being used to indicate that the terminal is allowed to use the IMS service based on the IMS slice.

14. An IMS service acquisition device, characterized in that, include: Receive module, acquire module, and create module; The receiving module is used to receive URSP rules from network-side devices; The acquisition module is used to acquire IMS information through the URSP rules received by the receiving module; The establishment module is used to establish a PDU session and an IMS signaling connection for IMS services based on the IMS information obtained by the acquisition module. Wherein, when the IMS information includes IMS slice information, the routing descriptor RSD in the URSP rule includes an IMS slice selection component, and the IMS slice selection component includes the IMS slice information; or, the network slice selection component in the RSD includes the IMS slice information. When the IMS information includes P-CSCF address indication information, the RSD in the URSP rule includes a P-CSCF selection component, and the P-CSCF selection component includes the P-CSCF address indication information, which is used to indicate the P-CSCF matched by the IMS session.

15. The apparatus according to claim 14, characterized in that, The IMS information also includes: the IMS data network name; The P-CSCF address indication information is used to indicate the address of the P-CSCF.

16. The apparatus according to claim 14, characterized in that, The acquisition module is further configured to acquire IMS service indication information before acquiring the IMS information through the URSP rules; The IMS service indication information includes at least one of the following: the application identifier of the IMS service, the demand indication information, and the IMS connection capability indication information; The demand indication information is used to indicate the type of the IMS service; The IMS connectivity indication information is used to request a network connection with IMS capability. The IMS information is the information in the URSP rule that matches the type of the IMS service.

17. The apparatus according to claim 16, characterized in that, The URSP rule includes a traffic descriptor that matches the IMS service indication information, or the application descriptor in the URSP rule includes information that matches the IMS service indication information.

18. The apparatus according to claim 16 or 17, characterized in that, The IMS service indication information includes the demand indication information; The acquisition module is specifically used to determine the first URSP rule and the second URSP rule from the URSP rules according to the demand indication information; The IMS information is the information in the second URSP rule; the first URSP rule is used to establish the PDU session, and the second URSP rule is used to establish the IMS signaling connection.

19. The apparatus according to claim 16 or 17, characterized in that, The IMS service indication information includes the application identifier and the demand indication information; The acquisition module is specifically used to determine a first URSP rule from the URSP rules based on the application identifier; and to determine a second URSP rule from the URSP rules based on the demand indication information. The IMS information is the information in the second URSP rule; the first URSP rule is used to establish the PDU session, and the second URSP rule is used to establish the IMS signaling connection.

20. The apparatus according to claim 16 or 17, characterized in that, The IMS service indication information includes the application identifier or the demand indication information; The acquisition module is specifically used to determine a third URSP rule from the URSP rules based on the application identifier or the demand indication information; and to determine a first RSD and a second RSD from the third URSP rule. The IMS information is the information in the second RSD; the first RSD is used to establish the PDU session, and the second RSD is used to establish the IMS signaling connection.

21. The apparatus according to claim 15, characterized in that, The IMS slice information includes S-NSSAI, which includes SST and SD; Wherein, the service type indicated by SST is IMS, and the SD is used to indicate the type of IMS service; or, the service type indicated by SST is a service type other than IMS, and the SD is used to indicate the type of IMS service.

22. The apparatus according to claim 14, characterized in that, The device further includes: a transmitting module; The sending module is configured to send IMS slice capability indication information to the network-side device before the acquisition module acquires the IMS information through the URSP rules. The IMS slice capability indication information is used to indicate that the terminal supports using the IMS service based on IMS slices. The receiving module is further configured to receive a first indication message sent by the network-side device, the first indication message being used to indicate that the terminal is allowed to use the IMS service based on IMS slices.

23. An IMS service acquisition device, characterized in that, include: Sending module; The sending module is used to send URSP rules to the terminal; The URSP rules include IMS information; the IMS information is used by the terminal to establish a PDU session and IMS signaling connection for IMS services. When the IMS information includes IMS slice information, the routing descriptor RSD in the URSP rule includes an IMS slice selection component, and the IMS slice selection component includes the IMS slice information; or, the network slice selection component in the RSD includes the IMS slice information. When the IMS information includes P-CSCF address indication information, the RSD in the URSP rule includes a P-CSCF selection component, and the P-CSCF selection component includes the P-CSCF address indication information, which is used to indicate the P-CSCF matched by the IMS session.

24. The apparatus according to claim 23, characterized in that, The IMS information also includes: the IMS data network name.

25. The apparatus according to claim 24, characterized in that, The IMS slice information includes S-NSSAI, which includes SST and SD; Wherein, the service type indicated by SST is IMS, and the SD is used to indicate the type of IMS service; or, the service type indicated by SST is a service type other than IMS, and the SD is used to indicate the type of IMS service.

26. The apparatus according to claim 23, characterized in that, The device further includes: a receiving module; The receiving module is configured to receive IMS slice capability indication information sent by the terminal before the sending module sends the URSP rule to the terminal. The IMS slice capability indication information is used to indicate that the terminal supports using the IMS service based on IMS slice. The sending module is further configured to send a first indication message to the terminal, the first indication message being used to indicate that the terminal is allowed to use the IMS service based on the IMS slice.

27. A terminal, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the IMS service acquisition method as described in any one of claims 1 to 9.

28. A network-side device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the IMS service acquisition method as described in any one of claims 10 to 13.

29. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the IMS service acquisition method as described in any one of claims 1 to 9, or implement the steps of the IMS service acquisition method as described in any one of claims 10 to 13.

Images