TECHNICAL FIELD
[0001] The present invention relates to the field of information processing technologies,
and in particular, to an inter-system policy using method, user equipment (UE), and
a computer storage medium.
BACKGROUND
[0002] In a communications system, policies of a terminal device, such as UE, may include
a WLANSP policy and a URSP policy. The URSP policy in UE policies is used when different
applications are applied for different network slices. Currently, related content
has been formulated in the URSP policy. However, currently, the policy is merely used
in a 5GS system, and when the UE is handed over between the 5GS and an EPS, it is
unclear how the UE is bound to an application.
SUMMARY
[0003] To resolve the foregoing technical problems, embodiments of the present invention
provide an inter-system policy using method, UE, and a computer storage medium.
[0004] An embodiment of the present invention provides an inter-system policy using method,
including:
using a first UE policy applied to a first system when traffic is processed in the
first system; and using a UE policy applied to a second system when traffic is processed
in the second system, where
the UE policy applied to an EPS system and the first UE policy applied to a 5GS system
are applied to same UE.
[0005] An embodiment of the present invention provides UE, including:
a processing unit, configured to use a first UE policy applied to a first system when
traffic is processed in the first system, and use a UE policy applied to a second
system when traffic is processed in the second system, where
the UE policy applied to an EPS system and the first UE policy applied to a 5GS system
are applied to same UE.
[0006] An embodiment of the present invention provides UE, including: a processor and a
memory configured to store a computer program that can be run on the processor, where
the processor is configured to perform the operations of the foregoing method when
the processor runs the computer program.
[0007] An embodiment of the present invention provides a computer storage medium, where
the computer storage medium stores a computer-executable instruction, and when the
computer-executable instruction is executed, the operations of the foregoing method
are performed.
[0008] By using the technical solutions of the embodiments of the present invention, it
can be determined that the UE performs traffic processing by separately using different
UE policies in two systems, so that UE policies for the UE to perform processing in
different systems are specified, thereby ensuring continuity of traffic processing
of the UE after a handover.
BRIEF DESCRIPTION OF DRAWINGS
[0009]
FIG. 1 is a schematic flowchart of an inter-system policy using method according to
an embodiment of the present invention;
FIG. 2 is a schematic diagram of a policy included in UE;
FIG. 3 is a schematic structural diagram of composition of UE according to an embodiment
of the present invention; and
FIG. 4 is a schematic diagram of a hardware architecture according to an embodiment
of the present invention.
DETAILED DESCRIPTION
[0010] To make the features and technical content of the embodiments of the present invention
more compressible, the following describes implementations of the embodiments of the
present invention in detail with reference to the accompanying drawings. The accompanying
drawings are intended for reference only, and are not intended to limit the embodiments
of the present invention.
Embodiment 1
[0011] An embodiment of the present invention provides an inter-system policy using method.
As shown in FIG. 1, the method includes the following operations:
Operation 101: Use a first UE policy applied to a first system when traffic is processed
in the first system. Operation 102: Use a UE policy applied to a second system when
traffic is processed in the second system.
[0012] The UE policy applied to an EPS system and the first UE policy applied to a 5GS system
are applied to same UE.
[0013] The first system may be understood as the 5GS system, and the second system may be
understood as the EPS system.
[0014] It should be noted that, there is no fixed sequential relationship between operation
101 and operation 102. Operation 102 may be performed first, and then, operation 101
is performed during a handover to the 5GS system. Certainly, operation 101 may also
be performed in the 5GS system, and then, operation 102 is performed after a handover
to the EPS system.
[0015] A policy provided in this embodiment may be a URSP policy formulated on the 5GS and
the EPS. In addition, introducing a DCN-ID (the DCN-ID is used on a dedicated network
of the EPS, and corresponds to S-NSSAI of the 5GS) to the URSP may be considered.
A set of rules that are used on the EPS and that correspond to rules used on the 5GS
may be input into the URSP.
[0016] For the URSP policy, refer to the following example. For example, the URSP policy
may include a URSP rule 1 (rule 1):
Policy: 1
Traffic filter: App = DummyApp
Direct offload: Prohibited
Slice Info: S-NSSAI-a
Continuity Types: SSC Mode 3
DNNs: internet
Access Type: 3GPP access.
[0017] URSP rule 2 (rule 2):
Traffic filter: App (application) = Appl, App2
Direct offload: Permitted
Slice Info: S-NSSAI-a
Access Type: Non-3GPP access.
[0018] The following gives an example about a route selection policy of UE with reference
to Table 1 and Table 2.
[0019] As shown in the following table:
Table 1: UE Route Selection Policy Rule
Information name |
Description |
Type |
Whether a PCF is allowed to adjust a UE context |
Range |
Rule precedence |
Determine an execution order of URSP rules in UE |
Mandatory execution |
Yes |
UE context |
Traffic descriptor |
Traffic description of a using policy |
|
|
|
Application identifier |
Application identifier |
Optional |
Yes |
UE context |
IP descriptor |
IP triplet |
Optional |
Yes |
UE context |
No IP descriptor |
Description for no IP traffic |
Optional |
Yes |
UE context |
Rule precedence |
Determine an execution order of URSP rules in UE |
Mandatory execution |
Yes |
UE context |
List of route selection descriptors |
Table 6.6.2-2. |
Mandatory execution |
|
|
Table 2
Information name |
Description |
Type |
Whether a PCF is allowed to adjust a UE context |
Range |
Route selection precedence |
Determines the order in which the Route Selection Descriptors are to be applied. |
Execution |
Yes |
UE context |
Route selection composition |
This part defines the route selection components |
Execution |
|
|
SSC mode selection |
One single value of SSC mode. |
Optional |
Yes |
UE context |
Network slice selection |
One value is used to represent S-NSSAI, or a list of values are used to represent
a plurality of pieces of S-NSSAI |
Optional |
Yes |
UE context |
DNN selection |
Either one single value or a list of values of DNN(s). |
Optional |
Yes |
UE context |
Non-seamless offload indication |
Indicates if the traffic of the matching application is to be offloaded to non-3GPP
access outside of a PDU Session. |
Optional |
Yes |
UE context |
Preferred access type |
Indicates the preferred Access Type (3GPP or non-3GPP) when the UE establishes a PDU
Session for the matching application. |
Optional |
Yes |
UE context |
[0020] In this embodiment, descriptions are made below by always using a 5GS system as the
first system and an EPS system as the second system. Specifically, for a UE policy
applied to the EPS system, there may be a plurality of configuration manners as follows.
[0021] Manner 1: A UE policy applied to the second system is a second UE policy.
[0022] Parameters in the second UE policy and parameters in a first UE policy are all separately
defined.
[0023] To be specific, a 5GS rule and an EPS rule that are separate are used. The UE policy
applied to the EPS system is the second UE policy, and the parameters in the second
UE policy and the parameters in the first UE policy are all separately defined.
[0024] That is, a set of EPS Rules corresponding to the 5GS URSP Rules is directly introduced,
and all parameters are separately defined.
[0025] Manner 2: A UE policy applied to the second system is a second UE policy.
[0026] At least some of the parameters in the second UE policy and at least some of the
parameters of the first UE policy are different, and there is a mapping relationship
between the at least some of the parameters of the second UE policy and the at least
some of the parameters of the first UE policy.
[0027] That is, a UE policy applied to the EPS system is the second UE policy.
[0028] At least some of the parameters in the second UE policy and at least some of the
parameters of the first UE policy are different, and there is a mapping relationship
between the at least some of the parameters of the second UE policy and the at least
some of the parameters of the first UE policy.
[0029] Specifically, a dedicated core network DCN identifier and an APN are configured in
the second UE policy.
[0030] A DCN identifier in the first UE policy corresponds to S-NSSAI in the first UE policy,
and the APN in the second UE policy corresponds to a DNN in the first UE policy.
[0031] For example, referring to Table 2 above, when Precedence and a Traffic Descriptor
in Table-1 in the 5GS URSP Rules are reused, for a set of parameters for the EPS added
to an RSD, mapping relationships are as follows:
SSC Mode Selection -> SSC Mode Selection
S-NSSAI -> DCN-ID
DNN -> APN
Non-seamless Offload indication -> Non-seamless Offload indication
Access Type preference -> Access Type preference
It should be further noted that, the foregoing one or more parameters may be set to
"empty", that is, there is a specified value on the 5GS, but there is no value on
the EPS.
[0032] Herein, it should be further noted that, for a configuration method for the first
UE policy and the second UE policy, for example, when the UE obtains the first UE
policy configured by a network side on the first system, the UE obtains the second
UE policy that is applied to the second system and policy that is sent by a network
side to the UE.
[0033] That is, the method may include: obtaining the second UE policy that is applied to
the EPS system and that is sent by the network side to the UE when the UE obtains
the first UE policy of the 5GS system configured by the network side on the 5GS system.
[0034] In addition, the UE receives the second UE policy delivered by the network side when
the UE accesses the second system.
[0035] The foregoing separate EPS URSP policy may be configured in two manners:
While a 5GS URSP policy is configured on the 5GS, an EPS URSP policy is also delivered;
and when the UE is attached to the EPS, the EPS URSP policy is delivered to the UE.
[0036] Manner 3: A set of 5GS URSP policies is still used.
[0037] The configured policy applied to the second system is the same as the first UE policy,
that is, the configured policy applied to the EPS system is the same as the first
UE policy.
[0038] Alternatively, the configured policy applied to the second system is partially the
same as the first UE policy, that is, the configured policy applied to the EPS system
is partially the same as the first UE policy.
[0039] For example, for a DNN parameter, there is a 5GS-EPS mapping relationship, and other
parameters are kept unchanged: DNN -> APN.
[0040] Except for that the UE policy applied to the EPS system is different from the first
UE policy of the 5GS system in terms of the DNN parameter and/or the S-NSSAI parameter,
the remaining parameters of the UE policy applied to the EPS system are same as those
of the first UE policy.
[0041] In addition, the DNN in the first UE policy applied to the 5GS system corresponds
to an APN in the UE policy of the EPS system, the S-NSSAI in the first UE policy applied
to the 5GS system corresponds to a DCN identifier in the UE policy applied to the
EPS system, and a mapping relationship between the APN in the UE policy applied to
the EPS system and the DNN in the first UE policy and/or a mapping relationship between
a DCN identifier applied to the EPS system and the S-NSSAI in the first UE policy
are/is configured.
[0042] The following focuses on describing use of a UE policy.
[0043] The second UE policy is used when the UE is connected to the second system.
[0044] The second system receives the second UE policy by using an attachment acknowledgment
message when the UE is connected to the second system through an attachment procedure.
That is, the EPS receives the second UE policy by using an attachment reply message
when the UE is attached to the EPS system.
[0045] Specifically, when the UE is attached to the EPS, the UE uses a URSP policy of the
EPS and uses a URSP policy of the 5GS.
[0046] When the UE establishes a PDN Connection on the EPS, S-NSSAI and/or a DNN corresponding
to the PDN Connection are/is returned. If a returned message includes the DNN, the
UE directly uses the DNN. If the DNN is not returned, then the UE autonomously performs
mapping processing to obtain a corresponding APN. The UE selects, based on the URSP
policy used on the 5GS, a PDN Connection for a specific data flow to perform data
transmission.
[0047] Processing is performed by using the first UE policy when the UE is registered with
the 5GS system.
[0048] To ensure traffic continuity in a handover procedure, a URSP execution manner after
a 5GS->EPS handover to the EPS is used as follows.
[0049] A corresponding relationship between a PDU session and the PDN connection is stored
after the UE completes establishment of the PDU session. After the UE completes establishment
of the PDU Session by using the S-NSSAI, the UE stores an EPS Bearer ID sent by the
network side to the UE. In addition, the EPS Bearer ID may further be used as an identifier
of the PDN Connection corresponding to the PDU Session.
[0050] It should be noted that, association is performed on a corresponding relationship
between the PDU session and the PDN connection by using a bearer identifier of the
second system.
[0051] It should be understood that, the bearer identifier is a default bearer identifier.
[0052] Specifically, after the UE completes establishment of a PDU session on the 5GS, the
UE stores an EPS default bearer identifier corresponding to the PDN connection on
the EPS corresponding to the PDU session. Before a handover is performed, a default
bearer identifier on the second system corresponding to the PDN connection on the
second system corresponding to the PDU session sent by the network side is stored.
[0053] When the UE is handed over from the 5GS system to the EPS system, the UE determines,
based on a PDU session corresponding to the first UE policy of the 5GS system, to
hand over application data to a PDN connection corresponding to the EPS bearer identifier
corresponding to the PDU session. That is, when a 5GS->EPS handover occurs, the UE
determines, based on a PDU Session corresponding to a URSP policy of the 5GS, to place
application data to a PDN Connection corresponding to an EPS Bearer ID corresponding
to an original PDU Session.
[0054] In addition, there is another case. When the UE is handed over from the first system
to the second system and the PDN connection corresponding to the PDU session is deleted
or cannot be handed over, a PDU session and a PDN connection corresponding to a parameter
combination corresponding to a second preferred UE policy rule of the first system
are selected based on precedence of the first UE policy of the first system, a corresponding
target PDU session is determined based on the parameter combination corresponding
to the second preferred UE policy rule, and application data is handed over to a PDN
connection corresponding to the target PDU session.
[0055] That is, when the UE is handed over from the 5GS system to the EPS system, and the
PDN connection corresponding to the PDU session is deleted or cannot be handed over,
a second preferred UE policy of the 5GS is selected based on precedence of the first
UE policy of the 5GS, a corresponding target PDU session is determined based on the
selected second preferred UE policy, and application data is handed over to a PDN
connection corresponding to the target PDU session. That is, for a case in which a
PDN Connection corresponding to the original PDU Session is deleted in the handover
procedure, the UE searches, based on Rule Precedence (precedence) in the URSP, for
a PDN Connection corresponding to a PDU Session corresponding to a second preferred
URSP Rule parameter, and transfers a data flow of the application to the PDN Connection.
[0056] It should be understood that, the parameter combination corresponding to the second
preferred UE policy rule of the first system may be understood as follows: a plurality
of UE policy rules corresponding to a plurality of orders of precedence currently
exist (each policy rule may correspond to a parameter combination); then, a most preferred
policy rule is selected from the plurality of orders of precedence, and whether a
PDU session and a PDU connection corresponding to the policy rule are a PDN connection
to which application data can be handed over is determined; if yes, the policy rule
may be understood as a parameter combination corresponding to the second preferred
UE policy of the first system; otherwise, a less preferred policy rule is selected,
and so on until a PDN connection to which the application data can be handed over
is selected, and it is determined that a parameter combination corresponding to the
second preferred UE policy rule of the first system is selected.
[0057] For a relationship between a policy and a policy rule, refer to FIG. 2. UE policies
may include a static policy and a dynamic policy, and this embodiment is directed
to a dynamic policy. The dynamic policy further includes a WLANSP and a URSP. The
URSP may include a plurality of rules, for example, may include precedence, traffic
description, and an RSD list. The RSD list may further include a combination of a
plurality of parameters such as precedence, an SSC mode, and a DNN. Details are not
described herein again.
[0058] Second preference means that the UE selects another parameter combination that meets
a Rule corresponding to the Traffic Descriptor for the foregoing data flow if a current
PDU Session is not handed over, and the another parameter combination includes: a
second parameter combination in a same RSD, and a parameter combination in another
RSD.
[0059] A definition of precedence: Precedence of URSP Rules is used to determine a sequential
order of using the Rules; contents described in Traffic descriptors in a plurality
of Rules overlap, PDU Sessions of the overlapped data flows is transferred by preferentially
using a URSP Rule that has higher Precedence.
[0060] Finally, it should be noted that, although description is made by mainly using a
traffic processing manner during a handover from the 5GS system to the EPS system
in this embodiment, an EPS->5GS handover also has a same mechanism, and details are
not described again.
[0061] It can be seen that, by using the foregoing solution, it can be determined that the
UE performs traffic processing in the 5GS system and the EPS system by separately
using different UE policies, so that UE policies for the UE to perform processing
in different systems are specified, thereby ensuring continuity of UE traffic processing
after a handover.
Embodiment 2
[0062] An embodiment of the present invention provides UE. As shown in FIG. 3, the UE includes:
a processing unit 21, configured to use a first UE policy applied to a first system
when traffic is processed in the first system, and use a UE policy applied to a second
system when traffic is processed in the second system.
[0063] The UE policy applied to the second system and the first UE policy applied to the
first system are applied to same UE.
[0064] The first system may be understood as a 5GS system, and the second system may be
understood as an EPS system.
[0065] A policy provided in this embodiment may be a URSP policy formulated on the 5GS and
the EPS. In addition, introducing a DCN-ID (the DCN-ID is used on a dedicated network
of the EPS, and corresponds to S-NSSAI of the 5GS) to the URSP may be considered.
A set of rules that are used on the EPS and that correspond to rules used on the 5GS
may be input into the URSP.
[0066] For the URSP policy, refer to the following example. For example, the URSP policy
may include a URSP rule 1 (rule 1):
Policy: 1
Traffic filter: App = DummyApp
Direct offload: Prohibited
Slice Info: S-NSSAI-a
Continuity Types: SSC Mode 3
DNNs: internet
Access Type: 3GPP access.
[0067] URSP rule 2 (rule 2):
Traffic filter: App (application) = Appl, App2
Direct offload: Permitted
Slice Info: S-NSSAI-a
Access Type: Non-3GPP access.
[0068] In this embodiment, descriptions are made below by always using a 5GS system as the
first system and an EPS system as the second system. Specifically, for a UE policy
applied to the EPS system, there may be a plurality of configuration manners as follows.
[0069] Manner 1: A UE policy applied to the second system is a second UE policy.
[0070] Parameters in the second UE policy and parameters in a first UE policy are all separately
defined.
[0071] To be specific, a 5GS rule and an EPS rule that are separate are used. The UE policy
applied to the EPS system is the second UE policy, and the parameters in the second
UE policy and the parameters in the first UE policy are all separately defined.
[0072] That is, a set of EPS Rules corresponding to the 5GS URSP Rules is directly introduced,
and all parameters are separately defined.
[0073] Manner 2: A UE policy applied to the second system is a second UE policy.
[0074] At least some of the parameters in the second UE policy and at least some of the
parameters of the first UE policy are different, and there is a mapping relationship
between the at least some of the parameters of the second UE policy and the at least
some of the parameters of the first UE policy.
[0075] That is, a UE policy applied to the EPS system is the second UE policy.
[0076] At least some of the parameters in the second UE policy and at least some of the
parameters of the first UE policy are different, and there is a mapping relationship
between the at least some of the parameters of the second UE policy and the at least
some of the parameters of the first UE policy.
[0077] Specifically, a dedicated core network DCN identifier and an APN are configured in
the second UE policy.
[0078] A DCN identifier in the first UE policy corresponds to S-NSSAI in the first UE policy,
and the APN in the second UE policy corresponds to a DNN in the first UE policy.
[0079] For example, referring to Table 2 above, when Precedence and a Traffic Descriptor
in Table-1 in the 5GS URSP Rules are reused, for a set of parameters for the EPS added
to an RSD, mapping relationships are as follows:
SSC Mode Selection -> SSC Mode Selection
S-NSSAI -> DCN-ID
DNN -> APN
Non-seamless Offload indication -> Non-seamless Offload indication
Access Type preference -> Access Type preference
It should be further noted that, the foregoing one or more parameters may be set to
"empty", that is, there is a specified value on the 5GS, but there is no value on
the EPS.
[0080] Herein, it should be further noted that, for the configuration method for the first
UE policy and the second UE policy, for example, the UE further includes:
a communications unit 22, configured to obtain the second UE policy that is applied
to the second system and that is sent by a network side to the UE when the UE obtains
the first UE policy configured by the network side on the first system. That is, the
UE obtains the second UE policy that is applied to the EPS system and that is sent
by the network side to the UE when the UE obtains the first UE policy of the 5GS system
configured by the network side on the 5GS system. The UE receives the second UE policy
delivered by the network side when the UE is attached to the EPS system.
[0081] That is, the foregoing separate EPS URSP policy may be configured in two manners:
When the first UE policy of the 5GS system is configured on the 5GS system, the second
UE policy that is applied to the EPS system and that is sent to the UE is configured.
In addition, when access is performed on the second system, the second UE policy is
delivered.
[0082] Manner 3: A set of 5GS URSP policies is still used.
[0083] The configured policy applied to the EPS system is the same as the first UE policy.
[0084] Alternatively, the configured policy applied to the EPS system is partially the same
as the first UE policy.
[0085] For example, for a DNN parameter, there is a 5GS-EPS mapping relationship, and other
parameters are kept unchanged: DNN -> APN.
[0086] Except for that the UE policy applied to the EPS system is different from the first
UE policy of the 5GS system in terms of the DNN parameter and/or the S-NSSAI parameter,
the remaining parameters of the UE policy applied to the EPS system are same as those
of the first UE policy.
[0087] In addition, the DNN in the first UE policy applied to the 5GS system corresponds
to an APN in the UE policy of the EPS system, the S-NSSAI in the first UE policy applied
to the 5GS system corresponds to a DCN identifier in the UE policy applied to the
EPS system, and a mapping relationship between the APN in the UE policy applied to
the EPS system and the DNN in the first UE policy and/or a mapping relationship between
a DCN identifier applied to the EPS system and the S-NSSAI in the first UE policy
are/is configured.
[0088] The following focuses on describing use of a UE policy.
[0089] The second UE policy is used when the UE is connected to the second system.
[0090] The second system receives the second UE policy by using an attachment acknowledgment
message when the UE is connected to the second system through an attachment procedure.
[0091] The EPS receives the second UE policy by using an attachment reply message when the
UE is attached to the EPS system.
[0092] Specifically, when the UE is attached to the EPS, the UE uses a URSP policy of the
EPS and uses a URSP policy of the 5GS.
[0093] When the UE establishes a PDN Connection on the EPS, S-NSSAI and/or a DNN corresponding
to the PDN Connection are/is returned. If a returned message includes the DNN, the
UE directly uses the DNN. If the DNN is not returned, then the UE autonomously performs
mapping processing to obtain a corresponding APN. The UE selects, based on the URSP
policy used on the 5GS, a PDN Connection for a specific data flow to perform data
transmission.
[0094] Processing is performed by using the first UE policy when the UE is registered with
the 5GS system.
[0095] To ensure traffic continuity in a handover procedure, a URSP execution manner after
a 5GS->EPS handover to the EPS is used as follows.
[0096] A corresponding relationship between a PDU session and the PDN connection is stored
after the UE completes establishment of the PDU session. After the UE completes establishment
of the PDU Session by using the S-NSSAI, the UE stores an EPS Bearer ID sent by the
network side to the UE. In addition, the default EPS Bearer ID may further be used
as an identifier of the PDN Connection corresponding to the PDU Session.
[0097] It should be noted that, association is performed on a corresponding relationship
between the PDU session and the PDN connection by using a bearer identifier of the
second system.
[0098] The bearer identifier may be understood as a default bearer identifier.
[0099] Specifically, after the UE completes establishment of a PDU session on the 5GS, the
UE stores an EPS default bearer identifier corresponding to the PDN connection on
the EPS corresponding to the PDU session. Before a handover is performed, a default
bearer identifier on the second system corresponding to the PDN connection on the
second system corresponding to the PDU session sent by the network side is stored.
[0100] When the UE is handed over from the 5GS system to the EPS system, the UE determines,
based on a PDU session corresponding to the first UE policy of the 5GS system, to
hand over application data to a PDN connection corresponding to the EPS bearer identifier
corresponding to the PDU session. That is, when a 5GS->EPS handover occurs, the UE
determines, based on a PDU Session corresponding to a URSP policy of the 5GS, to place
application data to a PDN Connection corresponding to an EPS Bearer ID corresponding
to an original PDU Session.
[0101] In addition, there is another case. When the UE is handed over from the first system
to the second system and the PDN connection corresponding to the PDU session is deleted
or cannot be handed over, a PDU session and a PDN connection corresponding to a parameter
combination corresponding to a second preferred UE policy rule of the first system
are selected based on precedence of the first UE policy of the first system, a corresponding
target PDU session is determined based on the parameter combination corresponding
to the second preferred UE policy rule, and application data is handed over to a PDN
connection corresponding to the target PDU session.
[0102] That is, when the UE is handed over from the 5GS system to the EPS system, and the
PDN connection corresponding to the PDU session is deleted or cannot be handed over,
a second preferred UE policy of the 5GS is selected based on precedence of the first
UE policy of the 5GS, a corresponding target PDU session is determined based on the
selected second preferred UE policy, and application data is handed over to a PDN
connection corresponding to the target PDU session. That is, for a case in which a
PDN Connection corresponding to the original PDU Session is deleted in the handover
procedure, the UE searches, based on Rule Precedence (precedence) in the URSP, for
a PDN Connection corresponding to a PDU Session corresponding to a second preferred
URSP Rule parameter, and transfers a data flow of the application to the PDN Connection.
[0103] It should be understood that, the parameter combination corresponding to the second
preferred UE policy rule of the first system may be understood as follows: a plurality
of UE policy rules corresponding to a plurality of orders of precedence currently
exist (each policy rule may correspond to a parameter combination); then, a most preferred
policy rule is selected from the plurality of orders of precedence, and whether a
PDU session and a PDU connection corresponding to the policy rule are a PDN connection
to which application data can be handed over is determined; if yes, the policy rule
may be understood as a parameter combination corresponding to the second preferred
UE policy of the first system; otherwise, a less preferred policy rule is selected,
and so on until a PDN connection to which the application data can be handed over
is selected, and it is determined that a parameter combination corresponding to the
second preferred UE policy rule of the first system is selected.
[0104] For a relationship between a policy and a policy rule, refer to FIG. 2. UE policies
may include a static policy and a dynamic policy, and this embodiment is directed
to a dynamic policy. The dynamic policy further includes a WLANSP and a URSP. The
URSP may include a plurality of rules, for example, may include precedence, traffic
description, and an RSD list. The RSD list may further include a combination of a
plurality of parameters such as precedence, an SSC mode, and a DNN. Details are not
described herein again.
[0105] Second preference means that the UE selects another parameter combination that meets
a Rule corresponding to the Traffic Descriptor for the foregoing data flow if a current
PDU Session is not handed over, and the another parameter combination includes: a
second parameter combination in a same RSD, and a parameter combination in another
RSD.
[0106] A definition of precedence: Precedence of URSP Rules is used to determine a sequential
order of using the Rules; contents described in Traffic descriptors in a plurality
of Rules overlap, PDU Sessions of the overlapped data flows is transferred by preferentially
using a URSP Rule that has higher Precedence.
[0107] Finally, it should be noted that, although description is made by mainly using a
traffic processing manner during a handover from the 5GS system to the EPS system
in this embodiment, an EPS->5GS handover also has a same mechanism, and details are
not described again.
[0108] It can be seen that, by using the foregoing solution, it can be determined that the
UE performs traffic processing in the 5GS system and the EPS system by separately
using different UE policies, so that UE policies for the UE to perform processing
in different systems are specified, thereby ensuring continuity of UE traffic processing
after a handover.
[0109] An embodiment of the present invention further provides a hardware composition architecture
of user equipment or a receiver device. As shown in FIG. 4, the hardware composition
architecture includes at least one processor 31, a memory 32, and at least one network
interface 33. All the components are coupled together through a bus system 34. It
may be understood that the bus system 34 is configured to implement a connection and
communication between the components. The bus system 34 further includes a power supply
bus, a control bus, and a status signal bus in addition to a data bus. However, for
the purpose of clear description, all buses are marked as the bus system 34 in FIG.
4.
[0110] It may be understood that the memory 32 in the embodiments of the present invention
may be a volatile memory or a nonvolatile memory, or may include both of a volatile
memory and a nonvolatile memory.
[0111] In some implementations, the memory 32 stores the following elements: an executable
module or a data structure, or a subset thereof, or an extended set thereof:
an operating system 321 and an application program 322.
[0112] The processor 31 is configured to perform the method operations of the foregoing
Embodiment 1. Details are not described herein again.
[0113] An embodiment of the present invention provides a computer storage medium, where
the computer storage medium stores a computer-executable instruction, and when the
computer-executable instruction is executed, the operations of the foregoing Embodiment
1 are performed.
[0114] In the embodiments of the present invention, if implemented in a form of a software
functional module and sold or used as an independent product, the foregoing apparatus
may alternatively be stored in a computer-readable storage medium. Based on such an
understanding, the technical solutions of the embodiments of the present invention
essentially or the part contributing to the prior art may be implemented in a form
of a software product. The computer software product is stored in a storage medium
and includes several instructions for instructing a computer device (which may be
a personal computer, a server, a network device, or the like) to perform all or some
of the methods described in the embodiments of the present invention. The foregoing
storage medium includes: various mediums that can store program code, for example,
a USB flash drive, a removable hard disk, a read-only memory (ROM, Read-Only Memory),
a magnetic disk, or an optical disc. In this way, the embodiments of the present invention
are not limited to any specific combination of hardware and software.
[0115] Correspondingly, an embodiment of the present invention further provides a computer
storage medium storing a computer program, where the computer program is configured
to perform a data scheduling method in an embodiment of the present invention.
[0116] Although for a purpose of illustration, preferred embodiments of the present invention
are disclosed, a person skilled in the art should be aware of that a variety of improvements,
additions, and substitutions are possible. Therefore, the scope of the present invention
should not be limited to the foregoing embodiments.
1. An inter-system policy using method, comprising:
using a first UE policy applied to a first system when traffic is processed in the
first system; and using a UE policy applied to a second system when traffic is processed
in the second system, wherein
the UE policy applied to the second system and the first UE policy applied to the
first system are applied to same UE.
2. The method according to claim 1, wherein the UE policy applied to the second system
is a second UE policy; and
parameters in the second UE policy and parameters in the first UE policy are all separately
defined.
3. The method according to claim 1, wherein the UE policy applied to the second system
is a second UE policy; and
at least some of the parameters in the second UE policy and at least some of the parameters
of the first UE policy are different, and there is a mapping relationship between
the at least some of the parameters of the second UE policy and the at least some
of the parameters of the first UE policy.
4. The method according to claim 3, wherein a dedicated core network DCN identifier and
an APN are configured in the second UE policy; and
a DCN identifier in the first UE policy corresponds to S-NSSAI in the first UE policy,
and the APN in the second UE policy corresponds to a DNN in the first UE policy.
5. The method according to claim 2 or 3, wherein the method further comprises:
obtaining the second UE policy that is applied to the second system and that is sent
by a network side to the UE when the UE obtains the first UE policy configured by
the network side on the first system.
6. The method according to claim 2 or 3, wherein the method further comprises:
receiving the second UE policy delivered by a network side when the UE accesses the
second system.
7. The method according to claim 1, wherein the configured policy applied to the second
system is the same as the first UE policy.
8. The method according to claim 1, wherein the configured policy applied to the second
system is partially the same as the first UE policy.
9. The method according to claim 8, wherein except for that the UE policy applied to
the second system is different from the first UE policy of the first system in terms
of the DNN parameter and/or the S-NSSAI parameter, the remaining parameters of the
UE policy applied to the second system are the same as those of the first UE policy;
and
a DNN in the first UE policy applied to the first system corresponds to an APN in
the UE policy of the second system, S-NSSAI in the first UE policy applied to the
first system corresponds to a DCN identifier in the UE policy of the second system,
and a mapping relationship between the APN in the UE policy applied to the second
system and the DNN in the first UE policy and/or a mapping relationship between the
DCN identifier applied to the second system and the S-NSSAI in the first UE policy
are/is configured.
10. The method according to claim 2, wherein the method further comprises:
using the second UE policy when the UE is connected to the second system.
11. The method according to claim 10, wherein the method further comprises:
receiving, by the second system, the second UE policy by using an attachment acknowledgment
message when the UE is connected to the second system through an attachment procedure.
12. The method according to claim 1, wherein the method further comprises:
performing processing by using the first UE policy when the UE is registered with
the first system.
13. The method according to claim 1, wherein the method further comprises:
storing a corresponding relationship between a PDU session and a PDN connection after
the UE establishes the PDU session.
14. The method according to claim 13, wherein the method further comprises:
when the UE is handed over from the first system to the second system, determining,
by the UE based on a PDU session corresponding to the first UE policy of the first
system, to hand over application data to a PDN connection corresponding to a bearer
identifier of the second system corresponding to the PDU session.
15. The method according to claim 13, wherein the method further comprises:
when the UE is handed over from the first system to the second system, and the PDN
connection corresponding to the PDU session is deleted or cannot be handed over, selecting,
based on precedence of the first UE policy of the first system, a PDU session and
a PDN connection corresponding to a parameter combination corresponding to a second
preferred UE policy rule of the first system, determining a corresponding target PDU
session based on the parameter combination corresponding to the second preferred UE
policy rule, and handing over application data to a PDN connection corresponding to
the target PDU session.
16. The method according to any one of claims 13 to 15, wherein the method further comprises:
performing association on a corresponding relationship between the PDU session and
the PDN connection by using a bearer identifier of the second system.
17. The method according to claim 16, wherein the method further comprises:
before a handover is performed, storing, by the UE, the bearer identifier on the second
system corresponding to the PDN connection on the second system corresponding to the
PDU session sent by a network side.
18. The method according to any one of claims 1 to 17, wherein:
the first system is a 5GS system, and the second system is an EPS system.
19. UE, comprising:
a processing unit, configured to use a first UE policy applied to a first system when
traffic is processed in the first system, and use a UE policy applied to a second
system when traffic is processed in the second system, wherein
the UE policy applied to the second system and the first UE policy applied to the
first system are applied to same UE.
20. The UE according to claim 19, wherein the UE policy applied to the second system is
a second UE policy; and
parameters in the second UE policy and parameters in the first UE policy are all separately
defined.
21. The UE according to claim 19, wherein the UE policy applied to the second system is
a second UE policy; and
at least some of the parameters in the second UE policy and at least some of the parameters
of the first UE policy are different, and there is a mapping relationship between
the at least some of the parameters of the second UE policy and the at least some
of the parameters of the first UE policy.
22. The UE according to claim 21, wherein a dedicated core network DCN identifier and
an APN are configured in the second UE policy; and
a DCN identifier in the first UE policy corresponds to S-NSSAI in the first UE policy,
and the APN in the second UE policy corresponds to a DNN in the first UE policy.
23. The UE according to claim 20 or 21, wherein the UE further comprises:
a communications unit, configured to obtain the second UE policy that is applied to
the second system and that is sent by a network side when obtaining the first UE policy
configured by the network side on the first system.
24. The UE according to claim 20 or 21, wherein the UE further comprises:
a communications unit, configured to receive the second UE policy delivered by a network
side during attachment to the second system.
25. The UE according to claim 19, wherein the configured policy applied to the second
system is the same as the first UE policy.
26. The UE according to claim 19, wherein the configured policy applied to the second
system is partially the same as the first UE policy.
27. The UE according to claim 26, wherein except for that the UE policy applied to the
second system is different from the first UE policy of a 5GS system in terms of the
DNN parameter and/or the S-NSSAI parameter, the remaining parameters of the UE policy
applied to the second system are the same as those of the first UE policy; and
a DNN in the first UE policy applied to the first system corresponds to an APN in
the UE policy of the second system, an S-NSSAI in the first UE policy applied to the
first system corresponds to a DCN identifier in the UE policy of an EPS system, and
a mapping relationship between the APN in the UE policy applied to the second system
and the DNN in the first UE policy and/or a mapping relationship between the DCN identifier
applied to the EPS system and the S-NSSAI in the first UE policy are/is configured.
28. The UE according to claim 20, wherein the processing unit uses the second UE policy
when the UE is connected to the second system.
29. The UE according to claim 28, wherein the processing unit receives the second UE policy
by using an attachment acknowledgment message when the UE is connected to the second
system through an attachment procedure.
30. The UE according to claim 19, wherein the processing unit performs processing by using
the first UE policy when the UE is registered with the first system.
31. The UE according to claim 19, wherein the processing unit stores a corresponding relationship
between a PDU session and a PDN connection after the UE establishes the PDU session.
32. The UE according to claim 31, wherein when the UE is handed over from the first system
to the second system, the processing unit determines, based on a PDU session corresponding
to the first UE policy of the first system, to hand over application data to a PDN
connection corresponding to the EPS bearer identifier corresponding to the PDU session.
33. The UE according to claim 32, wherein when the UE is handed over from the first system
to the second system, and the PDN connection corresponding to the PDU session is deleted
or cannot be handed over, the processing unit selects, based on precedence of the
first UE policy of the first system, a PDU session and a PDN connection corresponding
to a parameter combination corresponding to a second preferred UE policy rule of the
first system, determines a corresponding target PDU session based on the parameter
combination corresponding to the second preferred UE policy rule, and hands over application
data to a PDN connection corresponding to the target PDU session.
34. The UE according to any one of claims 31 to 33, wherein the processing unit performs
association on a corresponding relationship between the PDU session and the PDN connection
by using a bearer identifier of the second system.
35. The UE according to claim 34, wherein the processing unit stores, before a handover
execution stage, the EPS bearer identifier that is sent by the network side and that
corresponds to the PDN connection on the EPS corresponding to the PDU session.
36. The UE according to any one of claims 19 to 35, wherein the first system is a 5GS
system, and the second system is an EPS system.
37. UE, comprising a processor and a memory configured to store a computer program that
can be run on the processor, wherein
the processor is configured to perform the operations of the method according to any
one of claims 1 to 18 when the computer program is run.
38. A computer storage medium, wherein the computer storage medium stores a computer-executable
instruction, and when the computer-executable instruction is executed, the operations
of the method according to any one of claims 1 to 18 are implemented.