Protocol data unit PDU session establishment method and related device

Abstract

The invention discloses a protocol data unit (PDU) session establishment method and a related device, and relates to the technical field of mobile communication. In the application, a server determines a target URSP rule based on a service descriptor carried in an IMS service request initiated by a target terminal, the target URSP rule is an IMS URSP rule or an IMS TC URSP rule, and finally, a target IMS network slice is allocated to the IMS service request based on a route selection descriptor carried in the target URSP rule. And establishing an IMS PDU session based on the target IMS network slice. Therefore, the IMS URSP rule and the IMS TC URSP rule are newly added in the URSP rules issued by the network, so that the problem that the IMS PDU session of the terminal fails due to the fact that the network is not configured with the corresponding IMS rule can be solved.

Description

Technical Field

[0001] The present application relates to the field of mobile communication technology, and in particular to a method for establishing a protocol data unit (PDU) session and related devices. Background Art

[0002] In order to meet the network differentiation requirements in the fifth generation (5G) mobile communication system, the 3rd Generation Partnership Project (3GPP) proposed network slicing technology and User Equipment Routing Selection Policy (URSP). Network slicing technology divides a physical network into multiple logical networks. Network slicing is the collective name for one or more logical networks. Terminals can access network slices and use network slices to perform services. Among them, the terminal mainly determines which network slices to use for the current service based on the matching results of URSP.

[0003] At present, the Global System for Mobile communications Association (GSMA) defines Internet Protocol Multimedia Subsystem (IMS) Traffic Categories (TC) in URSP to identify IMS service flows. Under related technologies, when the service descriptor (TD) carried by the 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 the network are not synchronized in their support of IMS TC, the user's IMS session will fail and the user will not be able to make or receive IMS PDU sessions.

[0005] For example, when the terminal supports and uses the IMS TC function, but the network is not configured with the IMS TC URSP rule, the terminal will match the IMS TC service flow to the match-all URSP rule according to the existing URSP matching rule. The match-all URSP rule generally corresponds to the default data network name (DataNetwork Name) and the default network slice, non-IMSPDU session 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] The present application provides a protocol data unit (PDU) session establishment method and related devices, which are used to improve the stability of an IMS PDU session.

[0007] In a first aspect, an embodiment of the present application provides a method for establishing a protocol data unit (PDU) session, the method comprising:

[0008] Determine a target user terminal routing policy URSP rule based on a service descriptor carried in an 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;

[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] In a second aspect, an embodiment of the present application further provides a protocol data unit (PDU) session establishment device, the device comprising:

[0011] A matching module, configured to determine a target user terminal routing selection policy URSP rule based on a service descriptor carried in an Internet Protocol Multimedia System IMS service request initiated by a target terminal, wherein the target URSP rule is an IMS URSP rule or an IMS traffic classification TC URSP rule;

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

[0013] Optionally, when determining 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 matching module is used to:

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

[0015] If the parameter corresponding to the service descriptor carried in the IMS service request is only the IMS TC, 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, it is determined that the target URSP rule is the IMS TC URSP rule.

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

[0018] If the parameter corresponding to the service descriptor carried in the IMS service request is only the IMS TC, or the parameter corresponding to the service descriptor carried in the IMS service request is the IMS and the IMS TC, and the multiple URSP rules do not include the IMS TCURSP rule, then the target URSP rule is determined to be the IMS URSP rule;

[0019] If the parameter corresponding to the service descriptor carried in the IMS service request is IMS and / or IMS TC, and the multiple URSP rules do not include IMS URSP rules and IMS TC URSP rules, an IMS PDU session with the data network name DNN as IMS is 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 IMS URSP rule is lower than that of the IMS TC URSP rule, and higher than that of the default routing 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 include at least one or any combination of the following two types:

[0023] DNN business descriptor;

[0024] Network connection capability CC service descriptor.

[0025] In a third aspect, an embodiment of the present application provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements a method as described in any one of the first aspects when executing the computer program.

[0026] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of any method described in the first aspect.

[0027] In a fifth aspect, an embodiment of the present application provides a computer program product, which, when called by a computer, enables the computer to execute the method described in the first aspect.

[0028] In the embodiment of the present application, 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, the target URSP rule corresponding to the IMS service request can be determined from the preset multiple URSP rules according to the service descriptor carried in the IMS service request, and the target IMS network slice is obtained based on the routing descriptor carried in the target URSP rule, so as to establish an IMS PDU session. In this way, the problem of the failure of the terminal IMS PDU session caused by the network not configuring the corresponding IMS rules can be solved.

[0029] Other features and advantages of the present application will be described in the subsequent description, and partly become apparent from the description, or be understood by practicing the present application. The purpose and other advantages of the present application can be realized and obtained by the structures specifically pointed out in the written description, claims, and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 A schematic diagram of possible application scenarios in the embodiments of the present application;

[0031] Figure 2 This is a flow chart of a method for establishing a protocol data unit (PDU) session in an embodiment of the present application;

[0032] Figure 3 This is a flow chart of a first method for matching URSP rules in an embodiment of the present application;

[0033] Figure 4 This is a flow chart of a second method for matching URSP rules in an embodiment of the present application;

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

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

[0036] Figure 7 A schematic diagram of a third scenario of establishing an IMS PDU session in an embodiment of the present application;

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

[0038] Fig. 9 This is a structural diagram of a protocol data unit PDU session establishment device in an embodiment of the present application;

[0039] Fig.10 This is a schematic diagram of the structure of an electronic device in an embodiment of the present application. DETAILED DESCRIPTION

[0040] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the technical solution of the present application, rather than all of the embodiments. Based on the embodiments recorded in the application documents, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the technical solution of the present application.

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

[0042] Some of the terms used in the embodiments of the present application are explained below to facilitate understanding by those skilled in the art.

[0043] (1) Internet Protocol Multimedia Subsystem (IMS): IMS is a multimedia call network based on the Internet Protocol (IP). This network has a separate IMS protocol and is independent of the Internet and RAN / CN. It can provide multimedia services and public institutions have full control over the network.

[0044] (2) User Equipment Routing Selection Policy (URSP): It is a set of terminal routing selection policies defined by 3GPP, which is used to describe the association between service flows and network slices. URSP usually contains one or more URSP rules, each of which 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 the communication service flow, such as service type, service parameters, etc.

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

[0047] (5) Data Network Name (DNN): It is a new feature in 5G networks 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 the core unit in the 5G network and is mainly responsible for terminal identity authentication, authorization, registration, mobility management, and connection management.

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

[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 is 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 in a unified data warehouse.

[0052] The following is a brief introduction to the design concept of the embodiment of the present application:

[0053] Under the related 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 rule sent by the network side, that is, match the appropriate URSP rule according to CC TD=IMS TC, and parse the corresponding RSD parameters in the URSP rule, so as to establish a new PDU session for the service or reuse the original PDU session.

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

[0055] (1) When the terminal and the network are out of sync in terms of their support for IMS TC, the user's IMS session will fail and the user will not be able to make or receive IMS PDU sessions.

[0056] For example, when the terminal supports and uses the IMS TC function, but the network is not configured with 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, non-IMS PDU session and slice resources, resulting in the terminal not triggering the IMS PDU session establishment process, causing the user's IMS PDU session to fail.

[0057] For another example, when the URSP policy sent 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, causing the IMS session triggered by the application to match the match-all URSP rule, thereby causing the IMS PDU session to fail.

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

[0059] In view of this, in an embodiment of the present application, a method for establishing a protocol data unit (PDU) session and a related device are proposed.

[0060] In an embodiment of the present application, the server responds to an Internet Protocol Multimedia System IMS service request triggered by a target terminal, obtains a service descriptor carried in the IMS service request, and based on the service descriptor, determines the target URSP rule corresponding to the IMS service request from a plurality of preset user terminal routing selection policy URSP rules, wherein the target URSP rule is an IMS URSP rule or an IMS traffic classification TC URSP rule, and finally, based on the routing selection descriptor carried in the target URSP rule, allocates a target IMS network slice to the IMS service request, and establishes an IMS PDU session based on the target IMS network slice. In this way, by adding IMS URSP rules and IMS TC URSP rules to the URSP rules sent by the network, the problem of the failure of the terminal IMS PDU session caused by the network not configuring the corresponding IMS rules can be solved.

[0061] The preferred embodiments of the present application are described below in conjunction with the drawings in the specification. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present application, and are not used to limit the present application. In addition, the embodiments and features in the embodiments of the present application may be combined with each other if there is no conflict.

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

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

[0064] In an optional implementation, the communication network may be a wired network or a wireless network. Therefore, the terminal device 110 and the server 120 may be directly or indirectly connected via a wired or wireless communication. For example, the terminal device 110 may be indirectly connected to the server 120 via a wireless access point, or the terminal device 110 may be directly connected to the server 120 via the Internet, and this application does not limit this.

[0065] In the embodiment of the present application, the terminal device 110 includes but is not limited to mobile phones, tablet computers, laptop computers, desktop computers, e-book readers, intelligent voice interaction devices, smart home appliances, vehicle-mounted terminals and other devices; various clients may be installed on the terminal device, and the client may be an application program (such as a browser, game software, etc.) that supports functions such as video preview and video playback, or a web page, a small program, etc.;

[0066] The server 120 is a background server corresponding to the client installed in the terminal device 110. The server 120 may be an independent physical server, or 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 communications, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms.

[0067] It should be noted that the protocol data unit PDU session establishment method in the embodiment of the present application can be executed by an electronic device, which may 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 can be executed jointly by the server 120 and the terminal device 110.

[0068] It should be noted that, in the following, the example of execution by a server alone is mainly used for illustration, and no specific limitation is made here.

[0069] It should be noted that Figure 1 The figure is only an example. In fact, the number of terminal devices 110 and servers 120 is not limited and is not specifically limited in the embodiments of the present application.

[0070] In the embodiment of the present 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 also Figure 2 As shown, it is a flow chart of a method for establishing a protocol data unit PDU session in an embodiment of the present application. Figure 2 , and explain the specific execution steps in detail:

[0072] Step S201: determining a target user terminal routing policy URSP rule based on a service descriptor carried in an Internet Protocol Multimedia System IMS service request initiated by a target terminal.

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

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

[0075] The server receives an IMS service request triggered by the target terminal, and obtains a service descriptor carried in the IMS service request, wherein the service descriptor contained in the IMS service request and the target URSP rule in the embodiment of the present application respectively includes at least one or any combination of the following two types:

[0076] (1) DNN service descriptor.

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

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

[0079] Furthermore, in the embodiment of the present application, the server matches a 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 also Figure 3 As shown, it is a flow chart of a method for matching URSP rules in an embodiment of the present application, which specifically includes:

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

[0082] For example, when the terminal only supports IMS and the service descriptor carried when triggering the IMS service request is DNN TD=IMS, the server matches the target URSP rule for the IMS service request to the IMS URSP rule.

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

[0084] For example, when the 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 to 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, it is determined that the target URSP rule is the IMS TC URSP rule.

[0086] For example, when the terminal supports both IMS and IMS TC, and when triggering an IMS service request, the service descriptors carried at the same time are DNN TD=IMS and CC TD=IMS TC, the two IDs do not need to be matched at the same time, but the IMS TC URSP rule corresponding to the IMS TC is matched first, that is, the server prioritizes matching the target URSP rule for the IMS service request to the IMS TC URSP rule.

[0087] In addition, see Figure 4 As shown, it is a flow chart of a second method for matching URSP rules in an embodiment of the present 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 parameters corresponding to the service descriptor are IMS and IMS TC, and the multiple URSP rules do not include the 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 IMSTC URSP rule is not configured in the URSP rule sent by the terminal receiving the network, when the terminal supports and triggers the 5G IMS session and carries CC TD=IMS TC, the server matches the IMS URSP rule as the target URSP rule for the terminal, thereby realizing the IMS PDU session.

[0090] In addition, it should be noted that when the network side supports both IMS and IMS TC, the network side needs to configure both IMS URSP rules and IMS TC URSP rules, instead of only configuring IMS URSP rules. In this way, when the terminal supports IMS TC, it can be avoided that some applications do not carry IMS TC due to user access control and other reasons, resulting in the inability to access the IMS TC URSP rules corresponding to the IMS TC. The IMS URSP rules can still be accessed, thereby ensuring IMS services.

[0091] Step S402: If the parameter corresponding to the service descriptor carried in the IMS service request is IMS and / or IMS TC, and the multiple URSP rules do not include IMS URSP rules and IMS TC URSP rules, an IMS PDU session with the data network name DNN being IMS is directly established.

[0092] For example, in another optional embodiment, if the URSP rules sent by the terminal receiving the network do not configure the IMSURSP rules and IMS TC URSP rules, when the terminal supports and triggers the 5G IMS session and carries DNN TD=IMS and / or CC TD=IMS TC, the terminal determines that it is an IMS session according to DNN TD=IMS or CC TD=IMS TC, and will not match the existing default routing selection strategy match-all URSP rule, but directly triggers the establishment of an IMS PDU session with DNN=IMS to realize the IMS call.

[0093] In this way, it is possible to avoid the IMS session failure caused when the network side does not support IMS or IMS TC and IMS resources are not configured in the match-all URSP rule.

[0094] It can be understood 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, and higher than the default routing policy match-all URSP rule.

[0095] Specifically, when the target terminal triggers an IMS service, the IMS URSP rule is the default routing selection policy 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, 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.

[0097] Furthermore, in an embodiment of the present 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 embodiment, 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 embodiment, a specific application scenario is used below to further describe the process of establishing a protocol data unit PDU session in the embodiment of the present application in detail:

[0100] See also Figure 5 As shown, it is a schematic diagram of a first scenario of establishing an IMS PDU session in an embodiment of the present application, wherein the network side supports and configures both the IMS URSP rule and the IMS TC URSP rule, and the UE specifically includes the following steps when establishing the IMS PDU session:

[0101] Step S501: 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 parameters in the IMS URSP rules, the server connects the UE to the target IMS network slice, triggers a new or selects an existing IMS PDU session, and executes the IMS call process.

[0104] See also Figure 6 As shown, it is a schematic diagram of a second scenario of establishing an IMS PDU session in an embodiment of the present application, wherein the network side supports and configures both the IMS URSP rule and the IMS TC URSP rule, and the UE specifically includes the following steps when establishing the IMS PDU session:

[0105] Step S601: 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 according to CC TD=IMS TC.

[0107] Step S603: Based on the RSD parameters in the IMS TC URSP rules, the server connects the UE to the target IMS network slice, triggers a new or selects an existing IMS PDU session, and executes the IMS call process.

[0108] See also Figure 7 As shown, it is a schematic diagram of a third scenario of establishing an IMS PDU session in an embodiment of the present application, wherein the network side only supports and configures the IMS URSP rule, and the UE specifically includes the following steps when establishing the IMS PDU session:

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

[0110] Step S702: The server performs URSP rule matching and matches the IMS URSP rule according to DNN TD=IMS and CC TD=IMS TC.

[0111] Step S703: Based on the RSD parameters in the IMS URSP rules, the server connects the UE to the target IMS network slice, triggers a new or selects an existing IMS PDU session, and executes the IMS call process.

[0112] See also Figure 8 As shown, it is a schematic diagram of a fourth scenario of establishing an IMS PDU session in an embodiment of the present application, wherein the network side does not support and does not configure the IMS URSP rule and the IMS TC URSP rule, and the UE establishes the IMS PDU session specifically including the following steps:

[0113] Step S801: 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, and directly triggers the establishment of an IMS PDU session with DNN=IMS according to DNN TD=IMS and CC TD=IMS TC.

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

[0116] In the above application scenarios, when the UE or application accesses the target IMS network slice and establishes an IMS PDU session, it also includes the functional implementation of the access and mobility management function entity AMF, the session management function entity SMF, the user port function entity UPF, and the policy control function entity PCF, which will not be elaborated in this application.

[0117] To summarize, in the embodiment of the present application, new IMS URSP rules and IMS TC URSP rules are added to the URSP rules sent from the network side to the terminal, which can ensure the normal establishment of the IMS PDU session process when the terminal supports and carries the service descriptor of IMS and IMS TC. Moreover, even if the network side is not configured with 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 an IMS PDU session with DNN=IMS without matching the match-all URSP rule, thereby further avoiding IMS call failure. In addition, the above process is also applicable to roaming scenarios.

[0118] In addition, although the operations of the method of the present application are described in a specific order in the drawings, this does not require or imply that the operations must be performed in this specific order, or that all the operations shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps.

[0119] Based on the same technical concept, see Fig. 9 As shown, the embodiment of the present application also provides a protocol data unit PDU session establishment device, the device comprising:

[0120] A matching module 901 is used to determine a target user terminal routing selection policy URSP rule based on a service descriptor carried in an Internet Protocol Multimedia System IMS service request initiated by a target terminal, wherein the target URSP rule is an IMS URSP rule or an IMS traffic classification TC URSP rule;

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

[0122] Optionally, when determining 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 matching module 901 is used to:

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

[0124] If the parameter corresponding to the service descriptor carried in the IMS service request is only the IMS TC, 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, it is determined that the target URSP rule is the IMS TC URSP rule.

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

[0127] If the parameter corresponding to the service descriptor carried in the IMS service request is only the IMS TC, or the parameter corresponding to the service descriptor carried in the IMS service request is the IMS and the IMS TC, and the multiple URSP rules do not include the IMS TCURSP rule, then the target URSP rule is determined to be the IMS URSP rule;

[0128] If the parameter corresponding to the service descriptor carried in the IMS service request is IMS and / or IMS TC, and the multiple URSP rules do not include IMS URSP rules and IMS TC URSP rules, an IMS PDU session with the data network name DNN as IMS is 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 IMS URSP rule is lower than that of the IMS TC URSP rule, and higher than that of the default routing 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 include at least one or any combination of the following two types:

[0132] DNN business descriptor;

[0133] Network connection capability CC service descriptor.

[0134] Based on the same technical concept, an embodiment of the present application also provides an electronic device, which can implement the method flow for establishing a protocol data unit PDU session provided in the above embodiment of the present application.

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

[0136] See also Fig.10 As shown, the electronic device may include:

[0137] At least one processor 1001, and a memory 1002 connected to the at least one processor 1001. The specific connection medium between the processor 1001 and the memory 1002 is not limited in the embodiment of the present application. Fig.10 In the example, the processor 1001 and the memory 1002 are connected via the bus 1000. Fig.10 The connections between other components are shown in bold lines, and are not intended to be limiting. The bus 1000 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.10 Only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus. Alternatively, the processor 1001 can also be called a controller, and there is no limitation on the name.

[0138] In the embodiment of the present application, the memory 1002 stores instructions that can be executed by at least one processor 1001. The at least one processor 1001 can execute a protocol data unit PDU session establishment method discussed above by executing the instructions stored in the memory 1002. The processor 1001 can implement Fig. 9 The functions of each module in the device shown.

[0139] Among them, processor 1001 is the control center of the device, and can use various interfaces and lines to connect various parts of the entire control device. By running or executing instructions stored in memory 1002 and calling data stored in memory 1002, various functions of the device and processing data, the device can be monitored as a whole.

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

[0141] Processor 1001 may be a general-purpose processor, such as a CPU, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of a protocol data unit PDU session establishment method disclosed in the embodiments of the present application may be directly embodied as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.

[0142] The memory 1002 is a non-volatile computer-readable storage medium that can be used to store non-volatile software programs, non-volatile computer executable programs and modules. The memory 1002 may include at least one type of storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory, a random access memory (Random Access Memory, RAM), a static random access memory (Static Random Access Memory, SRAM), a programmable read-only memory (Programmable Read Only Memory, PROM), a read-only memory (Read Only Memory, ROM), an electrically erasable programmable read-only memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), a magnetic memory, a disk, an optical disk, etc. The memory 1002 is any other medium that can be used to carry or store a desired program code in the form of an instruction or data structure and can be accessed by a computer, but is not limited thereto. The memory 1002 in the embodiment of the present application can also be a circuit or any other device that can realize a storage function, 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 introduced in the above embodiment can be fixed into the chip, so that the chip can execute the code when running. Figure 2 The steps of a method for establishing a protocol data unit (PDU) session in the embodiment shown are as follows: How to design and program the processor 1001 is a technology well known to those skilled in the art and will not be described in detail here.

[0144] Based on the same inventive concept, an embodiment of the present application also provides a storage medium, which stores computer instructions. When the computer instructions are executed on a computer, the computer executes a protocol data unit PDU session establishment method discussed above.

[0145] In some possible implementations, various aspects of a protocol data unit (PDU) session establishment method provided by the present application may also be implemented in the form of a program product, which includes a program code. When the program product is run on an apparatus, the program code is used to enable the control device to execute the steps of a protocol data unit (PDU) session establishment method according to various exemplary implementations of the present application described above in this specification.

[0146] It should be noted that, although several units or subunits of the device are mentioned in the above detailed description, this division is merely exemplary and not mandatory. In fact, according to the embodiments of the present 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 into multiple units to be embodied.

[0147] In addition, although the operations of the method of the present application are described in a specific order in the drawings, this does not require or imply that the operations must be performed in this specific order, or that all the operations shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps.

[0148] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0149] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0150] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0151] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0152] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A method for establishing a protocol data unit (PDU) session, characterized in that: include: Determine a target user terminal routing policy URSP rule based on a service descriptor carried in an 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; 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 according to claim 1, characterized in that The determining of 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 includes: If the parameter corresponding to the service descriptor carried in the IMS service request is only IMS, determining that the target URSP rule is the IMS URSP rule; If the parameter corresponding to the service descriptor carried in the IMS service request is only the IMS TC, determining that the target URSP rule is the IMS TC URSP rule; If the parameters corresponding to the service descriptor carried in the IMS service request are IMS and IMS TC, it is determined that the target URSP rule is the IMS TC URSP rule.

3. The method according to 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 the parameter corresponding to the service descriptor carried in the IMS service request is IMS and IMS TC, and the multiple URSP rules do not include the IMS TC URSP rule, determining that the target URSP rule is the IMS URSP rule; If the parameter corresponding to the service descriptor carried in the IMS service request is IMS and / or IMS TC, and the multiple URSP rules do not include the IMS URSP rule and the IMS TC URSP rule, an IMS PDU session with a data network name DNN of IMS is directly established.

4. The method according to any one of claims 1 to 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 IMS URSP rule is lower than that of the IMS TC URSP rule, and higher than that of the default routing policy match-all URSP rule.

5. The method according to any one of claims 1 to 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 to 3, characterized in that: The service descriptors included in the IMS service request and the target URSP rule respectively include at least one or any combination of the following two types: DNN business descriptor; Network connection capability CC service descriptor.

7. A protocol data unit (PDU) session establishment device, characterized in that: include: A matching module, configured to determine a target user terminal routing selection policy URSP rule based on a service descriptor carried in an Internet Protocol Multimedia System IMS service request initiated by a target terminal, wherein the target URSP rule is an IMS URSP rule or an IMS traffic classification TC URSP rule; A module is established to allocate a target IMS network slice for the IMS service request based on a 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, the method according to any one of claims 1 to 6 is implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, characterized in that When the computer program product is called by a computer, the computer executes the method according to any one of claims 1 to 6.

Images