A method and related apparatus for establishing a Protocol Data Unit (PDU) session.

Abstract

This application discloses a method and related apparatus for establishing a Protocol Data Unit (PDU) session, relating to the field of mobile communication technology. In this application, the server determines the target URSP rule based on the service descriptor carried in the Internet Protocol Multimedia System (IMS) service request initiated by the target terminal. The target URSP rule is either an IMS URSP rule or an IMS TC URSP rule. Finally, based on the routing descriptor carried in the target URSP rule, a target IMS network slice is allocated for the IMS service request, and an IMS PDU session is established based on the target IMS network slice. Thus, by adding IMS URSP rules and IMS TC URSP rules to the URSP rules issued by the network, the problem of terminal IMS PDU session failure caused by the network not configuring corresponding IMS rules can be solved.

Description

Technical Field

[0001] This application relates to the field of mobile communication technology, and in particular to a method and related apparatus for establishing a Protocol Data Unit (PDU) session. Background Technology

[0002] To meet the differentiated network requirements of 5G mobile communication systems, the 3rd Generation Partnership Project (3GPP) proposed network slicing technology and User Equipment Routing Selection Policy (URSP). Network slicing divides a physical network into multiple logical networks; a network slice is a collective term for one or more of these logical networks. Terminals can access network slices and execute services using them. Specifically, the terminal determines which network slices to use for the current service based on the URSP matching results.

[0003] Currently, the Global System for Mobile Communications Association (GSMA) defines Internet Protocol Multimedia Subsystem (IMS) Traffic Categories (TCs) in the URSP to identify IMS service flows. Under related technologies, when the Traffic Descriptor (TD) carried by an IMS service is equal to the IMS TC, the terminal will match the appropriate URSP rule according to TD = IMS TC and parse the corresponding Route Selection Descriptor (RSD) parameter in the URSP rule, thereby establishing a new Protocol Data Unit (PDU) session for the service or reusing the original IMS PDU session.

[0004] However, when the terminal and network support for IMS TC is out of sync, it can cause the user's IMS session to fail, making it impossible to make or receive IMS PDU sessions.

[0005] For example, when a terminal supports and uses the IMS TC function, but the network has not configured IMS TC URSP rules, the terminal will match the IMS TC service flow to the match-all URSP rule according to the existing URSP matching rules. The match-all URSP rule generally corresponds to the default data network name and the default network slice, non-IMSPDU sessions and slice resources, which will cause the terminal to not trigger the IMS PDU session establishment process, causing the user's IMS PDU session to fail. Summary of the Invention

[0006] This application provides a method and related apparatus for establishing a Protocol Data Unit (PDU) session to improve the stability of IMS PDU sessions.

[0007] In a first aspect, embodiments of this application provide a method for establishing a Protocol Data Unit (PDU) session, the method comprising:

[0008] Based on the service descriptor carried in the Internet Protocol Multimedia System (IMS) service request initiated by the target terminal, the target user terminal routing selection policy URSP rule is determined, wherein the target URSP rule is an IMS URSP rule or an IMS Traffic Classification (TC) URSP rule.

[0009] Based on the routing descriptor corresponding to the service descriptor contained in the target URSP rule, a target IMS network slice is allocated for the IMS service request, and an IMS PDU session is established based on the target IMS network slice.

[0010] Secondly, embodiments of this application also provide a Protocol Data Unit (PDU) session establishment apparatus, the apparatus comprising:

[0011] The matching module is used to determine the target user terminal routing selection policy URSP rule based on the service descriptor carried in the Internet Protocol Multimedia System (IMS) service request initiated by the target terminal. The target URSP rule is either an IMS URSP rule or an IMS Traffic Classification (TC) URSP rule.

[0012] The module is used to allocate target IMS network slices for IMS service requests based on the routing descriptors corresponding to the service descriptors contained in the target URSP rules, and to establish IMS PDU sessions based on the target IMS network slices.

[0013] Optionally, when determining the URSP (Usage Routing Policy) rules for the target user terminal based on the service descriptor carried in the Internet Protocol Multimedia System (IMS) service request initiated by the target terminal, the matching module is used for:

[0014] If the parameter corresponding to the service descriptor carried in the IMS service request is only IMS, then the target URSP rule is determined to be an IMS URSP rule;

[0015] If the parameter corresponding to the service descriptor carried in the IMS service request is only IMS TC, then the target URSP rule is determined to be the IMS TC URSP rule;

[0016] If the parameters corresponding to the service descriptor carried in the IMS service request are IMS and IMS TC, then the target URSP rule is determined to be the IMS TC URSP rule.

[0017] Optionally, the matching module is also used for:

[0018] If the parameter corresponding to the service descriptor carried in the IMS service request is only IMS TC, or if the parameter corresponding to the service descriptor carried in the IMS service request is both IMS and IMS TC, and among the multiple URSP rules, there is no IMS TCURSP rule, then the target URSP rule is determined to be the IMS URSP rule.

[0019] If the parameters corresponding to the service descriptor carried in the IMS service request are IMS and / or IMS TC, and among the multiple URSP rules, there are no IMS URSP rules and IMS TC URSP rules, then an IMS PDU session with the data network name DNN as IMS will be directly established.

[0020] Optionally, when the parameters corresponding to the service descriptor carried in the IMS service request are IMS and IMS TC, the matching priority of the IMSURSP rule is lower than that of the IMS TC URSP rule, but higher than that of the default routing selection policy match-all URSP rule.

[0021] Optionally, the network quality provided by the IMS network slice corresponding to the IMS TC URSP rule is higher than or equal to the network quality provided by the IMS network slice corresponding to the IMS URSP rule.

[0022] Optionally, the service descriptors included in the IMS service request and the target URSP rule shall each include at least one or any combination of the following two types:

[0023] DNN service descriptor;

[0024] Network connectivity capability CC service descriptor.

[0025] Thirdly, embodiments of this application provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method as described in any of the first aspects.

[0026] Fourthly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of any of the methods described in the first aspect.

[0027] Fifthly, embodiments of this application provide a computer program product that, when invoked by a computer, causes the computer to execute the method described in the first aspect.

[0028] In this embodiment, IMS URSP rules and IMSTC URSP rules are added to the URSP rules sent from the network side to the terminal. When the target terminal triggers an IMS service request, it can determine the target URSP rule corresponding to the IMS service request from multiple preset URSP rules based on the service descriptor carried in the IMS service request, and obtain the target IMS network slice based on the routing descriptor carried in the target URSP rule, thereby establishing an IMS PDU session. This solves the problem of terminal IMS PDU session failure caused by the network not configuring the corresponding IMS rules.

[0029] Other features and advantages of this application will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the application. The objectives and other advantages of this application may be realized and obtained by means of the structures particularly pointed out in the written description, claims, and drawings. Attached Figure Description

[0030] Figure 1 This is a schematic diagram illustrating possible application scenarios in the embodiments of this application;

[0031] Figure 2 This is a flowchart of a method for establishing a Protocol Data Unit (PDU) session according to an embodiment of this application;

[0032] Figure 3 This is a flowchart of a first method for matching URSP rules in an embodiment of this application;

[0033] Figure 4 This is a flowchart of a second method for matching URSP rules in an embodiment of this application;

[0034] Figure 5 This is a schematic diagram of a first scenario for establishing an IMS PDU session in an embodiment of this application;

[0035] Figure 6 This is a schematic diagram of a second scenario for establishing an IMS PDU session in an embodiment of this application;

[0036] Figure 7 This is a schematic diagram of a third scenario for establishing an IMS PDU session in an embodiment of this application;

[0037] Figure 8 A schematic diagram of a fourth scenario for establishing an IMS PDU session in an embodiment of this application;

[0038] Figure 9 This is a schematic diagram of the structure of a Protocol Data Unit (PDU) session establishment device according to an embodiment of this application;

[0039] Figure 10 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0040] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings of the embodiments of this application. Obviously, the described embodiments are only some embodiments of the technical solutions of this application, and not all embodiments. Based on the embodiments recorded in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the technical solutions of this application.

[0041] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention described herein can be implemented in sequences other than those illustrated or described herein.

[0042] The following explanations of some terms used in the embodiments of this application are provided to facilitate understanding by those skilled in the art.

[0043] (1) Internet Protocol Multimedia Subsystem (IMS): IMS is a multimedia communication network based on Internet Protocol (IP). This network has a separate IMS protocol and is an independent network separate from the Internet and RAN / CN. It can provide multimedia services and the public institution has complete control over the network.

[0044] (2) User Equipment Routing Selection Policy (URSP): This is a set of terminal routing policies defined by 3GPP to describe the association between service flows and network slices. URSP typically contains one or more URSP rules, and each URSP rule contains one or more service descriptors and one or more routing descriptors.

[0045] (3) Traffic Descriptor (TD): In the field of communications, the main function of TD is to describe communication service flows, such as service type and service parameters.

[0046] (4) Route selection descriptor (RSD): It is used to influence which path the terminal device chooses for data transmission, and is responsible for considering factors such as path reliability, delay, and bandwidth during the routing process in order to provide the terminal device with the best routing decision.

[0047] (5) Data Network Name (DNN): This is a new feature in 5G networks used to support network slicing. Network slicing is a technology used in 5G to divide the physical network infrastructure into multiple virtual networks. Each virtual network is identified by a unique DNN. The 5G core network uses this name to route traffic to the appropriate network slice.

[0048] (6) Access and Mobility Management Function (AMF): It is a core unit in the 5G network and is mainly responsible for terminal authentication, authorization, registration, mobility management and connection management.

[0049] (7) Session Management Function (SMF): This is a core network element of 5G, responsible for session management-related functions, including establishing, modifying, and releasing sessions. Specific functions include IP address allocation, selection and control of user plane functions, configuration of service routing and UP traffic guidance, determination of SSC mode, and configuration of QoS policies for UPF during session establishment.

[0050] (8) User Plane Function (UPF): It is an important component of the 3GPP 5G core network system architecture. It is mainly responsible for the routing and forwarding of user plane data packets in the 5G core network and serves as the connection anchor between the 5G network and multi-access edge computing.

[0051] (9) Policy Control Function (PCF): It is one of the core network elements of 5G. Its role is to support a unified policy framework to manage network behavior, provide policy rules to network entities for implementation, and access subscription information of a unified data warehouse.

[0052] The design concept of the embodiments of this application is briefly introduced below:

[0053] Under the relevant technology, when the IMS service triggered by the terminal carries CC TD=IMS TC, the terminal will perform URSP rule matching according to the URSP rules issued by the network side, that is, match the appropriate URSP rule according to CC TD=IMS TC, and parse out the corresponding RSD parameter in the URSP rule, thereby establishing a new PDU session for the service or reusing the original PDU session.

[0054] However, existing standards and solutions have the following problems:

[0055] (1) When the terminal and the network are not in sync with each other for IMS TC, it will cause the user's IMS session to fail and the user will be unable to make or receive IMS PDU sessions.

[0056] For example, when a terminal supports and uses the IMS TC function, but the network has not configured the corresponding IMS TC URSP rules, the terminal will match the IMS TC service flow to the match-all URSP rule according to the existing URSP matching rules. The match-all URSP rule generally corresponds to the default DNN and the default network slice, not the IMS PDU session and slice resources. As a result, the terminal will not trigger the IMS PDU session establishment process, causing the user's IMS PDU session to fail.

[0057] For example, when the URSP policy issued by the network side includes the IMS IC URSP policy, some applications in the terminal may not carry CC TD=IMS TC when triggering the IMS session due to reasons such as the system not being upgraded. This will cause the IMS session triggered by the application to match the match-all URSP rule, resulting in the failure of the IMS PDU session.

[0058] (2) In the case of roaming, when the local network supports IMS TC, but the roaming location does not support or has not configured IMS TC, the terminal that supports and uses IMS TC normally will fail to establish an IMS PDU session in the roaming location for the same reason as the above problem (1).

[0059] In view of this, this application proposes a method and related apparatus for establishing a Protocol Data Unit (PDU) session.

[0060] In this embodiment, the server responds to an Internet Protocol Multimedia System (IMS) service request triggered by a target terminal, obtains the service descriptor carried in the IMS service request, and determines the target URSP rule corresponding to the IMS service request from a set of preset User Terminal Routing Policy (URSP) rules based on the service descriptor. The target URSP rule is either an IMS URSP rule or an IMS Traffic Classification (TC) URSP rule. Finally, based on the routing descriptor carried in the target URSP rule, a target IMS network slice is allocated to the IMS service request, and an IMS PDU session is established based on the target IMS network slice. Thus, by adding IMS URSP rules and IMS TC URSP rules to the URSP rules issued by the network, the problem of terminal IMS PDU session failure caused by the network not configuring corresponding IMS rules can be solved.

[0061] The preferred embodiments of this application are described below with reference to the accompanying drawings. It should be understood that the preferred embodiments described herein are for illustration and explanation only and are not intended to limit this application. Furthermore, the embodiments and features in the embodiments of this application can be combined with each other without conflict.

[0062] See Figure 1 As shown, it is a schematic diagram of possible application scenarios in the embodiments of this application.

[0063] This application scenario includes terminal device 110 (including terminal device 1101, terminal device 1102... terminal device 110n) and server 120. Terminal device 110 and server 120 can communicate with each other through a communication network.

[0064] In one alternative implementation, the communication network can be a wired network or a wireless network. Therefore, the terminal device 110 and the server 120 can be connected directly or indirectly via wired or wireless communication. For example, the terminal device 110 can be indirectly connected to the server 120 via a wireless access point, or the terminal device 110 can be directly connected to the server 120 via the Internet; this application does not impose any limitations on this.

[0065] In this application embodiment, the terminal device 110 includes, but is not limited to, mobile phones, tablets, laptops, desktop computers, e-book readers, smart voice interaction devices, smart home appliances, vehicle terminals, and other devices; various clients can be installed on the terminal device, which can be applications that support video preview, video playback, and other functions (such as browsers, game software, etc.), or web pages, mini programs, etc.

[0066] Server 120 is a backend server corresponding to the client installed in terminal device 110. Server 120 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms.

[0067] It should be noted that the Protocol Data Unit (PDU) session establishment method in this application embodiment can be executed by an electronic device, which can be a server 120 or a terminal device 110. That is, the method can be executed by the server 120 or the terminal device 110 alone, or by the server 120 and the terminal device 110 together.

[0068] It should be noted that the following text mainly uses the example of the server running alone, and no specific limitations are made here.

[0069] It should be noted that, Figure 1 The examples shown are merely illustrative; in reality, the number of terminal devices 110 and servers 120 is not limited and is not specifically limited in this embodiment.

[0070] In this embodiment of the application, when there are multiple servers 120, the multiple servers 120 can form a blockchain, and the servers 120 are nodes on the blockchain.

[0071] See Figure 2 As shown, it is a flowchart of a Protocol Data Unit (PDU) session establishment method in an embodiment of this application. The following is a description of the flowchart in conjunction with the attached diagram. Figure 2 The specific execution steps are explained in detail below:

[0072] Step S201: Based on the service descriptor carried in the Internet Protocol Multimedia System (IMS) service request initiated by the target terminal, determine the URSP (Usage Routing Policy) rules for the target user terminal.

[0073] The service descriptor is used to characterize the service type corresponding to the IMS service request. The target URSP rule is an IMS URSP rule or an IMS traffic classification TC URSP rule. The target URSP rule carries at least a routing descriptor that matches the service descriptor.

[0074] Specifically, the server in this embodiment supports both IMS and IMS TC. Therefore, in the URSP rules sent to the terminal, in addition to the default routing policy match-all URSP rule, a URSP rule with DNN=IMS, namely the IMS URSP rule, and a URSP rule with CC=IMS TC, namely the IMS TC URSP rule, are also configured, corresponding to IMS network resources and IMS TC network resources, respectively.

[0075] The server receives an IMS service request triggered by the target terminal and obtains the service descriptor carried in the IMS service request. In this embodiment, the IMS service request and the service descriptor contained in the target URSP rule each include at least one or any combination of the following two types:

[0076] (1) DNN service descriptor.

[0077] (2) Network connectivity capability CC service descriptor.

[0078] For example, if the terminal supports IMS, the service descriptor can be DNN TD=IMS when triggering an IMS service request; if the terminal supports IMS TC, the service descriptor can be CC TD=IMS when triggering an IMS service request; furthermore, if the terminal supports both IMS and IMS TC, the service descriptors can be DNN TD=IMS and CC TD=IMS when triggering an IMS service request, and this application does not impose any restrictions on this.

[0079] Furthermore, in this embodiment of the application, the server matches the corresponding target URSP rule among a plurality of preset URSP rules based on the service descriptor carried when the terminal triggers the IMS service request.

[0080] See Figure 3 As shown, it is a flowchart of a method for matching URSP rules in an embodiment of this application, which specifically includes:

[0081] Step S301: If the parameter corresponding to the service descriptor carried in the IMS service request is only IMS, then the target URSP rule is determined to be the IMS URSP rule.

[0082] For example, when a terminal only supports IMS and carries the service descriptor DNN TD=IMS when triggering an IMS service request, the server matches the target URSP rule for the IMS service request as the IMS URSP rule.

[0083] Step S302: If the parameter corresponding to the service descriptor carried in the IMS service request is only IMS TC, then the target URSP rule is determined to be the IMS TC URSP rule.

[0084] For example, when a terminal supports IMS TC and only carries the service descriptor CC TD = IMS TC when triggering an IMS service request, the server matches the target URSP rule for the IMS service request as the IMS TC URSP rule.

[0085] Step S303: If the parameters corresponding to the service descriptor carried in the IMS service request are IMS and IMS TC, then the target URSP rule is determined to be the IMS TC URSP rule.

[0086] For example, when a terminal supports both IMS and IMS TC, and carries both service descriptors DNN TD=IMS and CC TD=IMS TC when triggering an IMS service request, the two IDs do not need to be matched simultaneously. Instead, the IMS TC URSP rule corresponding to IMS TC is matched first. That is, the server prioritizes matching the target URSP rule as the IMS TC URSP rule for this IMS service request.

[0087] In addition, see Figure 4 As shown, it is a flowchart of a second method for matching URSP rules in an embodiment of this application, which includes:

[0088] Step S401: If the parameter corresponding to the service descriptor carried in the IMS service request is only IMS TC, or the parameter corresponding to the service descriptor is both IMS and IMS TC, and among the multiple URSP rules, there is no IMS TC URSP rule, then the target URSP rule is determined to be the IMS URSP rule.

[0089] For example, in another optional embodiment, if the terminal does not configure the IMSTC URSP rule in the URSP rule sent by the network, when the terminal supports and triggers a 5G IMS session and carries CC TD = IMS TC, the server matches the IMS URSP rule for the terminal as the target URSP rule, thereby realizing the IMS PDU session.

[0090] Furthermore, it should be noted that when both IMS and IMS TC are supported on the network side, both IMSURSP rules and IMS TC URSP rules must be configured on the network side, rather than just configuring IMS URSP rules. This can prevent situations where some applications do not carry IMS TC due to user access control or other reasons, thus preventing them from accessing the IMSTC URSP rules corresponding to IMS TC. In this way, access to IMS URSP rules can still be ensured, thereby guaranteeing IMS service.

[0091] Step S402: If the parameters corresponding to the service descriptor carried in the IMS service request are IMS and / or IMS TC, and among the multiple URSP rules, there are no IMS URSP rules and IMS TC URSP rules, then directly establish an IMS PDU session with the data network name DNN as IMS.

[0092] For example, in another optional embodiment, if the URSP rules sent by the network to the terminal do not have IMSURSP rules and IMS TC URSP rules configured, when the terminal supports and triggers a 5G IMS session and carries DNN TD=IMS and / or CC TD=IMS TC, the terminal determines that it is an IMS session based on DNN TD=IMS or CC TD=IMS TC. It will not match the existing default routing policy match-all URSP rules, but will directly trigger the establishment of an IMS PDU session with DNN=IMS to realize IMS calling.

[0093] This avoids IMS session failures when the network does not support IMS or IMS TC and IMS resources are not configured in the match-all URSP rules.

[0094] It is understandable that, in the above process, when the parameters corresponding to the service descriptor carried in the IMS service request are IMS and IMS TC, the matching priority of the IMS URSP rule is lower than that of the IMS TC URSP rule, but higher than that of the default routing selection policy match-all URSP rule.

[0095] Specifically, when the target terminal triggers the IMS service, the IMS URSP rule is the default routing selection strategy in the IMS service scenario, rather than the match-all URSP rule.

[0096] Step S202: Based on the routing descriptor corresponding to the service descriptor contained in the target URSP rule, allocate a target IMS network slice for the IMS service request, and establish an IMS PDU session based on the target IMS network slice.

[0097] Furthermore, in this embodiment of the application, after the server matches the target URSP rule for the IMS service request, it will parse the routing descriptor (RSD) parameter carried in the target URSP rule, so that the target terminal or the application in the target terminal can access the corresponding target IMS network slice, thereby establishing an IMS PDU session.

[0098] Specifically, in the above embodiments, the network quality provided by the IMS network slice corresponding to the IMS TC URSP rule is higher than or equal to the network quality provided by the IMS network slice corresponding to the IMS URSP rule.

[0099] Based on the above embodiments, the process of establishing a Protocol Data Unit (PDU) session in this application embodiment will be further described in detail below using a specific application scenario:

[0100] See Figure 5 As shown, this is a schematic diagram of a first scenario for establishing an IMS PDU session in an embodiment of this application. The network side simultaneously supports and configures IMS URSP rules and IMS TC URSP rules. The specific steps for a UE to establish an IMS PDU session include:

[0101] Step S501: The UE initiates an IMS session request, carrying DNN TD=IMS.

[0102] Step S502: The server performs URSP rule matching and matches the IMS URSP rule according to DNN TD=IMS.

[0103] Step S503: Based on the RSD parameter in the IMS URSP rule, the server connects the UE to the target IMS network slice and triggers the creation of a new or selected existing IMS PDU session to execute the IMS call process.

[0104] See Figure 6 As shown, this is a schematic diagram of a second scenario for establishing an IMS PDU session according to an embodiment of this application. In this scenario, the network side simultaneously supports and configures both IMS URSP rules and IMS TC URSP rules. The specific steps involved in establishing an IMS PDU session by the UE are as follows:

[0105] Step S601: The UE initiates an IMS session request, carrying CC TD = IMS TC.

[0106] Step S602: The server performs URSP rule matching and matches the IMS TC URSP rule based on CC TD = IMS TC.

[0107] Step S603: Based on the RSD parameter in the IMS TC URSP rule, the server connects the UE to the target IMS network slice and triggers the creation of a new or selected existing IMS PDU session to execute the IMS call process.

[0108] See Figure 7 As shown, this is a schematic diagram of a third scenario for establishing an IMS PDU session in an embodiment of this application. In this scenario, the network side only supports and configures IMS URSP rules. The specific steps for the UE to establish an IMS PDU session are as follows:

[0109] Step S701: The UE initiates an IMS session request, carrying DNN TD=IMS and CC TD=IMS TC.

[0110] Step S702: The server performs URSP rule matching, matching the IMS URSP rule based on DNN TD=IMS and CC TD=IMS TC.

[0111] Step S703: Based on the RSD parameter in the IMS URSP rule, the server connects the UE to the target IMS network slice and triggers the creation of a new or selected existing IMS PDU session to execute the IMS call process.

[0112] See Figure 8 As shown, this is a schematic diagram of a fourth scenario for establishing an IMS PDU session in an embodiment of this application. In this scenario, the network side does not support and has not configured IMS URSP rules and IMS TC URSP rules. The specific steps for the UE to establish an IMS PDU session are as follows:

[0113] Step S801: The UE initiates an IMS session request, carrying DNN TD=IMS and CC TD=IMS TC.

[0114] Step S802: The server does not perform URSP rule matching, but directly triggers the establishment of an IMS PDU session for DNN=IMS based on DNN TD=IMS and CC TD=IMS TC.

[0115] Step S803: The UE executes the IMS call procedure.

[0116] In the above application scenarios, when the UE or application accesses the target IMS network slice and establishes an IMS PDU session, the functions of the Access and Mobility Management Function Entity (AMF), Session Management Function Entity (SMF), User Port Function Entity (UPF), and Policy Control Function Entity (PCF) are also implemented, which will not be elaborated here.

[0117] In summary, in this embodiment of the application, adding IMS URSP rules and IMS TC URSP rules to the URSP rules sent from the network side to the terminal can ensure the normal establishment of the IMS PDU session when the terminal supports and carries the service descriptor as IMS and IMS TC. Furthermore, even if the network side does not configure IMS URSP rules and IMS TC URSP rules, when the terminal carries IMS and / or IMS TC, the terminal directly refers to the existing IMS process and directly triggers the establishment of the IMS PDU session with DNN=IMS, without matching the match-all URSP rule, further avoiding IMS call failure. In addition, the above process is also applicable to roaming scenarios.

[0118] Furthermore, although the operations of the method of this application are described in a specific order in the accompanying drawings, this does not require or imply that these operations must be performed in that specific order, or that all the operations shown must be performed to achieve the desired result. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.

[0119] Based on the same technical concept, see [reference] Figure 9 As shown in the figure, this application embodiment also provides a Protocol Data Unit (PDU) session establishment apparatus, which includes:

[0120] The matching module 901 is used to determine the target user terminal routing selection policy URSP rule based on the service descriptor carried in the Internet Protocol Multimedia System (IMS) service request initiated by the target terminal. The target URSP rule is either an IMS URSP rule or an IMS Traffic Classification (TC) URSP rule.

[0121] The module 902 is used to allocate a target IMS network slice for an IMS service request based on the routing descriptor corresponding to the service descriptor contained in the target URSP rule, and to establish an IMS PDU session based on the target IMS network slice.

[0122] Optionally, when determining the URSP (Universal Routing Service Request) rules for the target user terminal based on the service descriptor carried in the Internet Protocol Multimedia System (IMS) service request initiated by the target terminal, the matching module 901 is used for:

[0123] If the parameter corresponding to the service descriptor carried in the IMS service request is only IMS, then the target URSP rule is determined to be an IMS URSP rule;

[0124] If the parameter corresponding to the service descriptor carried in the IMS service request is only IMS TC, then the target URSP rule is determined to be the IMS TC URSP rule;

[0125] If the parameters corresponding to the service descriptor carried in the IMS service request are IMS and IMS TC, then the target URSP rule is determined to be the IMS TC URSP rule.

[0126] Optionally, the matching module 901 is also used for:

[0127] If the parameter corresponding to the service descriptor carried in the IMS service request is only IMS TC, or if the parameter corresponding to the service descriptor carried in the IMS service request is both IMS and IMS TC, and among the multiple URSP rules, there is no IMS TCURSP rule, then the target URSP rule is determined to be the IMS URSP rule.

[0128] If the parameters corresponding to the service descriptor carried in the IMS service request are IMS and / or IMS TC, and among the multiple URSP rules, there are no IMS URSP rules and IMS TC URSP rules, then an IMS PDU session with the data network name DNN as IMS will be directly established.

[0129] Optionally, when the parameters corresponding to the service descriptor carried in the IMS service request are IMS and IMS TC, the matching priority of the IMSURSP rule is lower than that of the IMS TC URSP rule, but higher than that of the default routing selection policy match-all URSP rule.

[0130] Optionally, the network quality provided by the IMS network slice corresponding to the IMS TC URSP rule is higher than or equal to the network quality provided by the IMS network slice corresponding to the IMS URSP rule.

[0131] Optionally, the service descriptors included in the IMS service request and the target URSP rule shall each include at least one or any combination of the following two types:

[0132] DNN service descriptor;

[0133] Network connectivity capability CC service descriptor.

[0134] Based on the same technical concept, this application also provides an electronic device that can implement the method flow for establishing a Protocol Data Unit (PDU) session provided in the above embodiments of this application.

[0135] In one embodiment, the electronic device may be a server, a terminal device, or other electronic devices.

[0136] See Figure 10 As shown, the electronic device may include:

[0137] At least one processor 1001 and a memory 1002 connected to at least one processor 1001. In this embodiment, the specific connection medium between the processor 1001 and the memory 1002 is not limited. Figure 10 The example shown is the connection between processor 1001 and memory 1002 via bus 1000. Bus 1000 is... Figure 10 The connections between other components are indicated by thick lines and are for illustrative purposes only, not as limiting information. The Bus 1000 can be divided into address bus, data bus, control bus, etc., for ease of representation. Figure 10 The term 1001 is represented by a single thick line, but this does not imply that there is only one bus or one type of bus. Alternatively, the processor 1001 can also be called a controller; there are no restrictions on the name.

[0138] In this embodiment, the memory 1002 stores instructions executable by at least one processor 1001. By executing the instructions stored in the memory 1002, the at least one processor 1001 can execute the Protocol Data Unit (PDU) session establishment method described above. The processor 1001 can implement... Figure 9 The functions of each module in the device shown.

[0139] The processor 1001 is the control center of the device. It can connect to various parts of the control device through various interfaces and lines. By running or executing instructions stored in memory 1002 and calling data stored in memory 1002, the processor can perform various functions and process data, thereby monitoring the device as a whole.

[0140] In one possible design, processor 1001 may include one or more processing units. Processor 1001 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may also not be integrated into processor 1001. In some embodiments, processor 1001 and memory 1002 may be implemented on the same chip; in some embodiments, they may also be implemented on separate chips.

[0141] The processor 1001 can be a general-purpose processor, such as a CPU, digital signal processor, application-specific integrated circuit, field-programmable gate array or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the Protocol Data Unit (PDU) session establishment method disclosed in the embodiments of this application can be directly manifested as execution by a hardware processor, or execution by a combination of hardware and software modules within the processor.

[0142] Memory 1002, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. Memory 1002 may include at least one type of storage medium, such as flash memory, hard disk, multimedia card, card-type memory, random access memory (RAM), static random access memory (SRAM), programmable read-only memory (PROM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic memory, magnetic disk, optical disk, etc. Memory 1002 can be any other medium capable of carrying or storing desired program code in the form of instructions or data structures that can be accessed by a computer, but is not limited thereto. In the embodiments of this application, memory 1002 can also be a circuit or any other device capable of implementing storage functions for storing program instructions and / or data.

[0143] By designing and programming the processor 1001, the code corresponding to the Protocol Data Unit (PDU) session establishment method described in the foregoing embodiments can be embedded into the chip, thereby enabling the chip to execute the code during runtime. Figure 2 The illustrated embodiment describes the steps of a Protocol Data Unit (PDU) session establishment method. How to design and program the processor 1001 is a technique well-known to those skilled in the art and will not be elaborated upon here.

[0144] Based on the same inventive concept, embodiments of this application also provide a storage medium storing computer instructions that, when executed on a computer, cause the computer to perform a Protocol Data Unit (PDU) session establishment method as described above.

[0145] In some possible implementations, various aspects of the Protocol Data Unit (PDU) session establishment method provided by this application can also be implemented as a program product including program code. When the program product is run on a device, the program code is used to cause the control device to perform the steps in the Protocol Data Unit (PDU) session establishment method according to various exemplary embodiments of this application described above.

[0146] It should be noted that although several units or sub-units of the device have been mentioned in the detailed description above, this division is merely exemplary and not mandatory. In fact, according to embodiments of this application, the features and functions of two or more units described above can be embodied in one unit. Conversely, the features and functions of one unit described above can be further divided and embodied by multiple units.

[0147] Furthermore, although the operations of the method of this application are described in a specific order in the accompanying drawings, this does not require or imply that these operations must be performed in that specific order, or that all the operations shown must be performed to achieve the desired result. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.

[0148] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0149] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0150] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0151] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0152] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method for establishing a Protocol Data Unit (PDU) session, applied to a server, characterized in that, include: Based on the service descriptor carried in the Internet Protocol Multimedia System (IMS) service request initiated by the target terminal, the target user terminal routing selection policy URSP rule is determined, wherein the target URSP rule is an IMS URSP rule or an IMS Traffic Classification (TC) URSP rule. Based on the routing descriptor corresponding to the service descriptor contained in the target URSP rule, a target IMS network slice is allocated for the IMS service request, and an IMS PDU session is established based on the target IMS network slice.

2. The method as described in claim 1, characterized in that, The service descriptor carried in the Internet Protocol Multimedia System (IMS) service request initiated by the target terminal is used to determine the target user terminal routing selection policy URSP rules, including: If the parameter corresponding to the service descriptor carried in the IMS service request is only IMS, then the target URSP rule is determined to be the IMS URSP rule; If the parameter corresponding to the service descriptor carried in the IMS service request is only IMS TC, then the target URSP rule is determined to be the IMS TC URSP rule; If the parameters corresponding to the service descriptor carried in the IMS service request are IMS and IMS TC, then the target URSP rule is determined to be the IMS TC URSP rule.

3. The method as described in claim 1, characterized in that, Also includes: If the parameter corresponding to the service descriptor carried in the IMS service request is only IMS TC, or if the parameter corresponding to the service descriptor carried in the IMS service request is both IMS and IMS TC, and the IMS TC URSP rule is not included among the multiple URSP rules, then the target URSP rule is determined to be the IMS URSP rule. If the parameters corresponding to the service descriptor carried in the IMS service request are IMS and / or IMS TC, and the IMS URSP rule and the IMS TC URSP rule are not included among the multiple URSP rules, then an IMS PDU session with the data network name DNN as IMS is directly established.

4. The method according to any one of claims 1-3, characterized in that, Also includes: When the parameters corresponding to the service descriptor carried in the IMS service request are IMS and IMS TC, the matching priority of the IMSURSP rule is lower than that of the IMS TC URSP rule, but higher than that of the default routing policy match-allURSP rule.

5. The method according to any one of claims 1-3, characterized in that, Also includes: The network quality provided by the IMS network slice corresponding to the IMS TC URSP rule is higher than or equal to the network quality provided by the IMS network slice corresponding to the IMS URSP rule.

6. The method according to any one of claims 1-3, characterized in that, The service descriptors contained in the IMS service request and the target URSP rule respectively include at least one or any combination of the following two types: DNN service descriptor; Network connectivity capability CC service descriptor.

7. A Protocol Data Unit (PDU) session establishment device, applied to a server, characterized in that, include: The matching module is used to determine the target user terminal routing selection policy URSP rule based on the service descriptor carried in the Internet Protocol Multimedia System (IMS) service request initiated by the target terminal, wherein the target URSP rule is an IMS URSP rule or an IMS Traffic Classification (TC) URSP rule. The module is used to allocate a target IMS network slice for the IMS service request based on the routing descriptor corresponding to the service descriptor contained in the target URSP rule, and to establish an IMS PDU session based on the target IMS network slice.

8. An electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method as described in any one of claims 1-6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1-6.

10. A computer program product, characterized in that, When the computer program product is invoked by a computer, it causes the computer to perform the method as described in any one of claims 1-6.

Images