RU2787208C2 - Method, and device, and user equipment for display of policies - Google Patents

Abstract

FIELD: communication.

SUBSTANCE: invention relates to means for display of policies. User equipment (hereinafter – UE) displays parts of policies used in the first mobile communication system to corresponding policy(ies) used in the second mobile communication system, while policies used in the first mobile communication system at least include UE route selection policy (hereinafter – URSP). At the same time, display by UE of part of policies used in the first mobile communication system to corresponding policies used in the second mobile communication system includes display by UE of all rules or parts of rules of URSP to the second mobile communication system for use. In this case, the first rule used in the first mobile communication system and the second rule used in the second mobile communication system correspond to the same traffic descriptor and/or rule priority, and the second rule is obtained by display of the first rule.

EFFECT: increase in the accuracy of determination of the use of policy by user equipment.

14 cl, 16 dwg

Description

FIELD OF TECHNOLOGY TO WHICH THE INVENTION RELATES

Embodiments of the present invention relate to the technical field of mobile communications and, in particular, to a method and apparatus and user equipment (UE) for policy mapping.

BACKGROUND OF THE INVENTION

Some UE policies are defined in the 4th generation (4G) mobile communication system, such as access network discovery and selection (ANDSP) policy. Therefore, it is necessary to deploy the ANDSF network element in the 4G network in order for the UE to receive the ANDSP. However, many service providers have not yet deployed or planned to deploy ANDSF. As a consequence, the UE cannot determine which UE policy to use in the 4G mobile communication system.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide a method and a device and a UE for policy mapping.

In embodiments of the present invention, a policy mapping method is provided, which may include:

UE mapping of all or part of the policies used in the first mobile communication system to the policy used in the second mobile communication system, wherein the policies used in the first system include at least one element from ANDSF and the UE route selection policy (URSP) .

Embodiments of the present invention provide a policy mapper, which may include a mapper.

The mapper may be configured to map all or part of the policies used in the first mobile communication system to the policy used in the second mobile communication system, wherein the policies used in the first system include at least one of ANDSF and URSP.

In embodiments of the present invention, a UE is provided, which may include a processor and a storage device. The storage device may be configured to store a computer program, and the processor may be configured to call and run the computer program stored in the storage device to execute the policy mapping method.

Embodiments of the present invention provide a chip that can be configured to implement a policy mapping method.

In particular, the chip may include a processor configured to call and run a computer program in a storage device to allow the device in which the chip is installed to execute the policy mapping method.

Embodiments of the present invention provide a computer-readable storage medium that can be configured to store a computer program, the computer program allowing the computer to execute a policy mapping method.

Embodiments of the present invention provide a computer program product that may comprise a computer program instruction, wherein the computer program instruction allows the computer to execute a policy mapping method.

Embodiments of the present invention provide a computer program that can run on a computer to allow the computer to execute a policy mapping method.

Through the technical solutions, the UE can map the policies used in the first mobile communication system to the policy used in the second mobile communication system, so that when the UE moves from the first mobile communication system to the second mobile communication system, the policy obtained by mapping can be used in the second mobile communication system.

BRIEF DESCRIPTION OF GRAPHICS

The drawings described in this document are used to provide additional understanding of the present application and form part of the present invention. Schematic embodiments of the present invention and its description are used to explain the present application, and are not intended to impose undue restrictions on the present application. On graphics:

in fig. 1 is a schematic representation of the architecture of a communication system according to an embodiment of the present invention.

In FIG. 2 is an architecture diagram of a 5th generation (5G) network system according to an embodiment of the present invention.

In FIG. 3 is a flowchart of a UE Configuration Update (UCU) according to an embodiment of the present invention.

In FIG. 4 is a flowchart of an active UE policy request performed by a UE according to an embodiment of the present invention.

In FIG. 5 is a session establishment flowchart for a protocol data unit (PDU) according to an embodiment of the present invention.

In FIG. 6 is a flowchart of a policy mapping method according to an embodiment of the present invention.

In FIG. 7-1 is a first schematic representation of a policy mapping according to an embodiment of the present invention.

In FIG. 7-2 is a second schematic representation of a policy mapping according to an embodiment of the present invention.

In FIG. 7-3 is a third policy mapping diagram according to an embodiment of the present invention.

In FIG. 8 is a first flowchart for transmitting first indication information according to an embodiment of the present invention.

In FIG. 9 is a second flowchart for transmitting first indication information according to an embodiment of the present invention.

In FIG. 10 is a third flowchart for transmitting first indication information according to an embodiment of the present invention.

In FIG. 11 is a block diagram of the composition of a policy mapper according to an embodiment of the present invention.

In FIG. 12 is a schematic structural view of a communication device according to an embodiment of the present invention.

In FIG. 13 is a schematic structural view of a chip according to another embodiment of the present invention.

In FIG. 14 is a block diagram of a communication system according to an embodiment of the present invention.

DETAILED DESCRIPTION

The technical solutions in the embodiments of the present invention will be described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are not all embodiments, but part of the embodiments of the present invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present application without any creative effort are within the scope of the present invention.

The technical solutions of the embodiments of the present invention can be applied to various communication systems, such as Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Packet Data Service. General Use (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Universal Mobile Telecommunications System (UMTS), Broadband Access Technology Communication System in microwave band (WiMAX) or the future 5G system.

As an example, a communications system 100 to which embodiments of the present invention apply is shown in FIG. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal 120 (or called a communication terminal and a terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with a terminal located in the coverage area. Optionally, network device 110 may be a base transceiver station (BTS) in a GSM or CDMA system, may also be a NodeB (NB) in a WCDMA system, and may further be an evolved Node B (eNB or eNodeB) in an LTE system, or a wireless controller in an LTE system. cloud radio access network (CRAN). Or, the network device can be a mobile switching center, relay station, access point, vehicle device, wearable device, hub, switch, network bridge, router, network side device in the future 5G network, network device in the future advanced public terrestrial mobile network (PLMN) or the like.

The communication system 100 may further comprise at least one terminal 120 within the coverage area of the network device 110. As used herein, the term "terminal" includes, but is not limited to, a device capable of receiving/sending a communication signal over a wired line connection, such as , via the public switched telephone network (PSTN), digital subscriber line (DSL), digital cable and direct cable connections, and/or other data connection/network, and/or via a wireless interface such as cellular, wireless LAN (WLAN), a digital television network such as a digital broadcast network for handheld devices (DVB-H), a satellite network, and an amplitude-frequency modulation (AM-FM) broadcast transmitter, and/or another terminal, and/or an Internet device things (IoT). A terminal configured to communicate via a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal", or "mobile terminal". Examples of a mobile terminal include, but are not limited to, a satellite or cellular telephone, a personal communications system (PCS) terminal that may integrate a cellular radiotelephone with data processing, facsimile and data communications capabilities, a personal digital assistant (PDA) that may include a radiotelephone, pager, Internet/Intranet access, web browser, notepad, calendar and/or global positioning system (GPS) receiver, and conventional laptop computer and/or pocket receiver or other electronic device containing a radiotelephone transceiver. A terminal may refer to an access terminal, UE, user unit, user station, mobile station, mobile radio, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The access terminal may be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless subscriber access station (WLL), a PDA, a wireless capable handheld device, a computing device, other processing device connected to the wireless a modem, a device in a vehicle, a wearable device, a terminal in a 5G network, a terminal in a future advanced PLMN, or the like.

Optionally, device-to-device (D2D) communication may be between terminals.

Optionally, a 5G system or 5G network may also be referred to as a New Radio (NR) system or NR network.

The network device and two terminals are shown as an example in FIG. 1. Optionally, communication system 100 may include multiple network devices, and a different number of terminals may be included in the coverage area of each network device. In the embodiments of the present invention, there are no restrictions on this.

Optionally, communication system 100 may further comprise another network entity, such as a network controller and a mobility management node. In the embodiments of the present invention, there are no restrictions on this.

It should be understood that a device having a network/system communication function may be referred to as a communication device in embodiments of the present invention. For example, for the communication system 100 shown in FIG. 1, communication devices may include a network device 110 and a terminal 120 with a communication function. Network device 110 and terminal 120 may be the specific devices mentioned above and will not be described in detail herein. The communication devices may further include other devices in the communication system 100, such as other network entities such as a network controller and a mobility management node. In the embodiments of the present invention, there are no restrictions on this.

It should be understood that the terms "system" and "network" in the present invention can generally be used interchangeably in the present invention. In the present invention, the term "and/or" is only a relationship relationship describing related objects, and means that there may be three relationships. For example, A and/or B can denote three states: i.e., the independent existence of A, the existence of both A and B, and the independent existence of B. In addition, the symbol "/" in the present invention usually indicates that the previous and subsequent related objects form an "or" relation.

To facilitate understanding of the technical solutions of the embodiments of the invention, the technologies involved in the embodiments of the invention will now be described.

5G network architecture

In FIG. 2 is a diagram of a 5G network system architecture according to an embodiment of the present invention. As shown in FIG. 2, devices included in the 5G network system include:

UE, Radio Access Network (RAN), User Plane Function (UPF), Data Network (DN), Access and Mobility Management Function (AMF), Session Management Function (SMF), Policy Control Function (PCF), Application Function (AF), Authentication Server Function (AUSF); and Unified Data Management (UDM).

As shown in FIG. 2, policy-related network elements mainly include PCF, AMF, SMF, RAN, and UE. The SMF is primarily responsible for enforcing session related policies. The AMF is mainly responsible for executing policies related to access and policy of the UE. Policy propagation and updating of both NEs (AMF and SMF) is controlled and managed by the PCF.

For the UE policy, information related to the UE policy, including the contents of the UE policy, the UE policy ID, and the like, may be tracked between the PCF and the UE via the store object. In the upstream direction, the storage entity may be sent to the AMF UE via a Non-Access Layer (NAS) message and may continue to be transmitted transparently (without acknowledgment or modification) to the AMF PCF. Conversely, in the downstream direction, the storage object may be sent to the AMF PCF and may be further transparently transmitted to the AMF UE via a NAS message.

5G UE policy and its configuration

The UE policy may include ANDSP and URSP. The ANDSP may include a WLAN Selection Policy (WLANSP) and Evolved Packet Data Gateway (ePDG)/Non-Internetwork Function (N3IWF) 3rd Generation Partnership Project (3GPP) selection information. In ANDSP, WLANSP is mandatory and ePDG/N3IWF NE selection information is optional.

1) WLANSP: WLANSP includes several rules (called WLANSP rules) that are applied by the UE to select a WLAN access point.

2) URSP: URSP includes several rules (called URSP rules), and each URSP rule consists of a traffic descriptor and a group of route selection descriptors (RSD). The traffic descriptor in a URSP is tailored to describe a specific service. For example, a microblogging service may be described with Internet Protocol (IP) @1~9. As another example, an IP Multimedia Subsystem (IMS) service may be described using an IMS Data Network Name (DNN). There may also be one or more RSDs corresponding to a traffic descriptor, and each RSD corresponds to a PDU session attribute. That is, the overhead corresponding to the traffic descriptor may be transmitted in a session PDU corresponding to the RSD. Related URSP content is shown in Table 1 and Table 2.

Information name Description Category Allow PCF modification in UE context Borders Rule Priority Specifies the order in which the URSP rule is enforced in the UE. Mandatory (REC 1) Yes UE context Traffic descriptor This part defines the components of the traffic descriptor for the URSP rule. Mandatory (REC 3) Application Descriptors Consists of OSId and OSAppId. (RECORD 2) Not necessary Yes UE context IP Descriptors
(REC 5) Destination IP 3 tuple(s) (IP address or IPv6 network prefix, port number, protocol ID in protocol over IP). Not necessary Yes UE context Domain Descriptors Target(s) FQDN Not necessary Yes UE context Non-IP Descriptors
(REC 5) Descriptor(s) for non-IP traffic target information Not necessary Yes UE context DNN This is matched against the DNN information provided by the application. Not necessary Yes UE context Connectivity This is compared with the information provided by the UE application when requesting a network connection with certain capabilities. (REC 4) Not necessary Yes UE context List of route selection descriptors List of route selection descriptors The components of a route selection descriptor are described in Table 6.6.2.1-3. Necessarily

Table 1: URSP rule

Information name Description Category Allow PCF Modification in URSP Borders Priority of route selection descriptors Specifies the order in which route selection descriptors should be applied. Mandatory (REC 1) Yes UE context Route Selection Components This part defines the route selection components Mandatory (REC 2) SSC mode selection One single SSC mode value.
(REC 5) Not necessary Yes UE context Selecting a network fragment Either a single value or a list of S-NSSAI values. Optional (REC 3) Yes UE context DNN selection Either a single value or a list of DNN values. Not necessary Yes UE context Selecting the PDU session type One single PDU session type value Not necessary Yes UE context Specifying a Non-Breakless Discharge Indicates whether conforming application traffic should be offloaded to non-3GPP access outside of the session PDU. Optional (REC 4) Yes UE context Access type preference Indicates the preferred access type (3GPP or non-3GPP or multiple access) when the UE establishes a session PDU for a negotiating application. Not necessary Yes UE context Criteria for checking the correctness of the route selection
(REC 6) This part defines the components of the route validation criteria. Not necessary Time interval The time interval in which conforming traffic is allowed. The RSD is not considered valid if the current time is not within the given time interval. Not necessary Yes UE context Location criteria The location of the UE where the negotiated traffic is allowed. The RSD rule is not considered valid if the location of the UE does not match the location criteria. Not necessary Yes UE context

Table 2: RSD

The UE policy configuration is implemented by the UCU flow. The connection architecture of each network element in a UCU flow may be referred to in FIG. 2. As shown in FIG. 3, the UCU flow includes the following operations.

At operation 301, the PCF determines whether the UE policy needs to be updated.

At operation 302, the PCF includes the UE policy that needs to be updated in the store object and passes the store object to the AMF.

At operation 303, the AMF directly redirects the storage object to the UE via a NAS message.

In operation 304, the UE sends a policy configuration result (UE policy delivery result) to the AMF.

The 3GPP indicates the active UE policy request flow performed by the UE. As shown in FIG. 4, the flow includes the following operations.

At operation 401, the UE sends a UE policy request message to the AMF.

At operation 402, the AMF sends a UE policy update control message to the PCF.

At operation 403, a UE policy configuration flow is carried out between the UE and the PCF.

In this document, a UE policy configuration flow refers to a flow as shown in FIG. 3.

It should be noted that the UE may simultaneously receive several types of UE policies, such as URSP policies and transport-to-neighborhood (V2X) communications from the network side. On the other hand, the active UE policy request flow performed by the UE in FIG. 4 only applies to requesting a UE policy (ie V2X policy) for a V2X service.

In the flows in Fig. 3 and FIG. 4, the UE policy is transmitted as follows: the UE policy is divided by the network device into one or more policy sections and sent to the UE, each policy section corresponding to a policy section identifier (PSI).

Using the 5G URSP method

Based on the URSP, the UE associates the application data with the corresponding session PDU for transmission through the following mechanism.

If there is data in the application layer, the UE may check whether the application data tag matches the traffic descriptor of a specific rule from the URSP rules based on the URSP rules belonging to the URSP. The check sequence can be determined by the traffic descriptor priorities in the URSP rules. That is, the UE sequentially checks the negotiation condition based on the priority sequence. If there is a match with the URSP rule, the RSD list according to the URSP rule may be used to associate with the session PDU.

If there is a match with the URSP rule, the UE may check for a suitable PDU session according to the RSD priority sequence. In this document, RSD with high priority is preferred. When a certain RSD parameter has one or more values, the UE may select and combine one and the other parameters to check if a session PDU exists:

1) If a session PDU exists, the application data may be associated with the session for transmission.

2) If the PDU session does not exist, the UE may start establishing the PDU session and the establishment request message contains the attribute parameter reported by the UE of the session PDU.

In addition, the following operations are performed:

2.1) If the session is successfully established, the UE associates the application data with the session for transmission.

2.2) If the session establishment fails, the UE checks if the session PDU exists again based on a different RSD parameter combination or a lower priority RSD parameter combination (1 repeated).

If it fails to find a suitable session PDU to associate according to the negotiated URSP, the UE may sequentially check if the traffic descriptor in the lower priority URSP rule can be matched to the application data tag according to the priorities. If there is an agreement, the above process is repeated.

The process of finding a suitable session PDU for an application is referred to as "evaluation" in the present invention. After finding and associating a suitable session PDU, the UE may re-evaluate under the following conditions to determine whether an update of the original association between the application data and the session PDU is required. The conditions below include the following:

-PCF updates URSP;

-UE moves from Evolved Packet Core (EPC) to 5G Core (5GC);

- update of allowed network fragment selection assistance information (NSSAI) or configured NSSAI;

-updating local data network (LADN) DNN availability;

-the UE registers with a 3GPP access network or a non-3GPP access network; and

-UE establishes a connection to the WLAN access network.

4G ANDSP

4G ANDSPs typically include the following types.

1) Intersystem Mobility Policy (IMSP)

The UE selects a preferred radio access technology (RAT) to route the data packet based on the IMSP. For example, a core network is connected with two types of RAT access, which are LTE RAT access and WLAN RAT access. The UE may select a type among them to transmit the data packet based on the IMSP.

The ISMP rule may include the following information: the actual state (eg, time and location), the priority list of the access systems or access networks, and the priority of the ISMP rule.

2) Access network opening information

The network side may send a variety of access network information around the UE. The information may include: access system type (eg, WLAN and WiMAX), RAN identifier (eg, WLAN service set identifier (SSID), other specific technical information (eg, frequency information of one or more carriers), and validity condition (eg, location).

3) Intersystem Routing Policy (ISRP)

The data packet may be transmitted over one or more wireless access interfaces (eg, multiple RATs) at the same time by the UE according to ISRP. There are three types of ISRP, namely, IP Flow Mobility (IFOM), Multi-Access Public Data Network (PDN) Interoperability (MAPCON), and Non-Seamless WLAN Offloading (NSWO). The first two types are primarily used to associate a specific data stream or PDN connection with a specific access point name (APN) and access system. The third type may be used to indicate whether non-hopeless WLAN handover is allowed for a particular traffic.

4) Inter-APN Routing Policy (IARP)

IARP can be applied to the UE to determine specific data flows that require transmission over different connections via PDN and specific data flows that require NSWO. For transmission by PDN connection, the PDN connection corresponding to a particular APN may also be selected based on IARP.

5) WLAN selection policy (WLANSP)

The WLANSP may be applied to the UE to select a particular access point (SSID) of the WLAN.

The above UE policies regarding 4G may have duplicate parts. Thus, it is possible that only one policy is chosen to be deployed at the time of actual use.

PDU Session Establishment Thread

In the PDU session establishment flow, the most important for the UE side is the PDU session establishment request message and the received response message. In FIG. 5 is a block diagram of establishing a PDU session. The following operations are included.

In step 1, a PDU session request message is sent to the AMF UE via a NAS message. The NAS message may include a single NSSAI(s) (S-NSSAI), a DNN, a PDU session ID, a request type, an old PDU session ID, and a session management (SM) store object. The SM storage object is also sent to the AMF SMF and mainly includes session tag related information. The UE may add a "requires always-on" identifier to instruct the SMF to establish a always-on PDU session in this operation.

In step 2, the AMF selects the SMF based on the NAS message sent by the UE and sends the NAS N1 including the NAS message to 1 to the SMF.

In steps 3-10, the SMF determines whether to establish a PDU session based on the NAS message from the UE, subscription information, and dynamic or local static policy.

In steps 11 to 13, the SMF sends a message to the RAN, the message mainly including a parameter such as SM N1 storage object, Quality of Service (QoS) information, N2 SM information, [always-on PDU session admission], selected session continuity mode and Services (SSC), S-NSSAI, NDD, dedicated IP version 4 (IPv4) address, and interface ID. The RAN may send the storage object SM N1 to the UE. The SM N2 information is applied to the RAN to create a radio bearer. Other parameters such as the [always-on PDU session admission] parameter may also be sent to the UE.

In addition, in case the UE does not request always-on in the Session Establishment Request PDU, the SMF may still determine the persistent-on task on its own. In such a case, the SMF may add a parameter [always-on PDU session admission] in the PDU Session Establishment Accept message.

ANDSP is defined in the 4G network, and therefore it is necessary to deploy the ANDSP network element in the 4G network in order for the UE to receive the ANDSP. However, on the one hand, many service providers do not deploy or plan to deploy ANDSP network elements, so it is necessary to provide for mapping the policy (UE policy) received by the UE from the 5G network to the policy used in the 4G network. On the other hand, service providers are wary of independent mapping of the 5G policy performed by the UE to the 4G network for use, and may plan to control part of the mapping operations or all of the mapping operations, so there is a need for a method to control the mapping operations of the UE.

In FIG. 6 is a flowchart of a policy mapping method according to an embodiment of the present invention. As shown in FIG. 6, the policy display method includes the following operation.

In step 601, the UE maps all or part of the policies used in the first mobile communication system to the policy used in the second mobile communication system, where the policies used in the first system include at least one of ANDSF and URSP.

In an embodiment of the present invention, the policies may be UE policies. UE policies include ANDSP and/or URSP. ANDSP may include WLANSP. The ANDSP may optionally additionally include ePDG/N3IWF NE selection information.

In an optional embodiment of the present invention, the first mobile communication system is a 5G mobile communication system (i.e., 5G (5GS) system) and the second mobile communication system is a 4G mobile communication system (i.e., Evolved Packet System (EPS) ). In the example with reference to FIG. 7-1, the UE, when in 5GS, can obtain the policies used in 5GS from the network and map all or part of the policies used in 5GS to the policies used in EPS. Below, how the UE maps policies will be described.

1) The policies used in the first mobile communication system at least include ANDSP, and the UE copies all or part of the ANDSP content to the second mobile communication system for use.

With reference to FIG. 7-2 to display ANDSPs, part (eg, WLANSP) or all ANDSPs can be directly copied to the EPS for use without changing any parameter. WLANSP content and ePDG/N3IWF NE selection information content are compatible in 5GS and EPS.

2) The policies used in the first mobile communication system at least include URSP, and the UE copies all or part of the URSP rules to the second mobile communication system for use.

Herein, the first rule used in the first mobile communication system and the second rule used in the second mobile communication system correspond to the same traffic descriptor and/or rule priority, and the second rule is obtained by mapping the first rule.

With reference to FIG. 7-3 URSP includes one or more URSP rules. For URSP mapping, part of the URSP rules or all of the URSP rules belonging to the URSP can be mapped to the EPS for use. For each URSP rule, the 5GS URSP rule and the EPS URSP rule have the same traffic descriptor and/or rule priority.

In addition, when one or more first URSP rules need to be displayed, the UE may display and/or copy at least a portion of the RSD parameters in accordance with the one or more first rules to the second mobile communication system for use. In an embodiment, at least a portion of the parameters (part of the parameters or all of the parameters) of the RSD in a 5GS URSP rule may be mapped and/or copied to the EPS for use. Since the URSP rule in 5GS and the URSP rule in EPS have the same traffic descriptor, when the UE transitions from 5GS to EPS, the data flow corresponding to the traffic descriptor can be transmitted with the PDN connection corresponding to the mapped RSD.

In an embodiment of the present invention, the RSD in the policy used in the first mobile communication system (e.g., 5GS) includes at least one of the following: SSC mode, S-NSSAI, PDU session type, DNN, non-seamless offload indication, preference access type, valid time interval and valid area. The RSD in the policy used in the second mobile communication system (eg, EPS) may include at least one of the following: APN, PDN connection type, non-seamless offload indication, access type preference, valid time interval, and valid area.

The valid time interval and the valid area are not necessarily supported by the UE, i.e. the UE may not be able to recognize these two parameters. While the other parameters are not necessarily configured by the network side, it is understood that the UE upon receiving them will be able to recognize them under normal condition. In addition, each of the S-NSSAI and DNN may have one or more multiple values, and any other parameters have a single value. It should be indicated that the first four parameters (ie SSC mode, S-NSSAI, PDU session type and DNN) refer to the PDU session attribute.

It should be noted that the PDN connection of the second mobile communication system usually includes the following attribute parameters: APN and PDN connection type. In addition, the SSC mode only supports the first SSC mode (ie, SSC-1 mode). Therefore, in the embodiment of the present invention, the following policy mapping method is applied.

Optionally, the UE may map the S-NSSAI and/or DNN to the APN.

Optionally, the UE may map the PDU session type to the PDN connection type.

Furthermore, as long as the session type of the PDU is an Ethernet type, in response to the support of the UE and the network in the second mobile communication system of the PDN Ethernet connection type, the UE may map the PDN connection type to the Ethernet type; and in response to not being supported by the UE and/or the network in the second mobile communication system of the Ethernet type, but having support of the non-IP type, the UE may map the PDN connection type to the non-IP type.

Optionally, assuming that the session type of the PDU in the UE policy in 5GS is an Ethernet type, in response to the UE and the network in the EPS supporting the PDN Ethernet connection type, the UE may map the PDN connection type to the Ethernet type; and in response to the lack of UE and/or network support of the Ethernet type in the EPS, but the presence of non-IP type support, the UE may map the PDN connection type to the non-IP type.

In addition, as long as the session type of the PDU is a non-structured type, the UE may map the PDN connection type to a non-IP type.

Optionally, as long as the PDU session type in the 5GS UE policy is an unstructured type, the UE may map the PDN connection type to a non-IP type.

In an optional implementation, the UE may copy at least one element of the non-seamless offload indication, access type preference, valid time slot, and valid area indication to the second mobile communication system for use.

Optionally, the UE may set the SSC mode in RSD to zero or the first SSC mode.

It should be noted that SSC modes in 5GS mean three modes, i.e. SSC-1 mode, SSC-2 mode and SSC-3 mode, respectively. The SSC-1 mode is that the UPF does not change after the PDU session is established. The SSC-2 mode is that the network side can change the UPF by triggering a drop-to-on switch after a PDU session is established. The SSC-3 mode is that the network side can change the UPF by triggering a switch-to-break after a PDU session is established.

In an embodiment of the present invention, the UE may display some or all of the RSD parameters. In addition, the UE may optionally add the first parameter to the policy obtained by mapping and apply the policy with the added first parameter to the second mobile communication system. Herein, the first parameter may be a parameter related to the second mobile communication system. In an optional implementation, after mapping a UE policy in 5GS to a policy for EPS, another parameter may continue to be added to the policy obtained by mapping to form a new policy for use in EPS.

In addition, the method according to an embodiment of the present invention may further include the following: the UE receives the first indication information from the network device, the first indication information indicating at least one of the following:

whether the UE is allowed to display policies;

the first policy to be displayed;

a rule available to display policies in the first policy;

whether RSD is available according to each rule of the first policy to display policies;

option available for displaying policies in RSD; and

option not available for displaying policies in RSD.

In deciding whether the UE is allowed to map policies, specifically refers to whether the UE is allowed to map the policy used in the first mobile communication system (eg, 5GS) to the policy used in the second mobile communication system (eg, EPS).

In a solution, the first policy to be mapped may include ANDSP and/or URSP.

In the decision, the rule available for policy mapping in the first policy may be, for example, whether policy mapping can be performed on a URSP rule to URSP, or, for example, whether policy mapping can be performed on a WLANSP rule to ANDSP.

In the decision, whether RSD policy mapping can be performed according to each rule in the first policy may be, for example, whether RSD policy mapping can be performed according to the URSP rule in the URSP.

In a solution, a parameter available for policy mapping in RSD may be, for example, S-NSSAI, DNN, PDU session type, non-seamless offload indication, access type preference, valid time interval, and valid area. An indication of a non-breakless download, an access type preference, a valid time interval, and a valid area can be displayed in a direct copy manner.

In a solution, a setting not available for displaying policies in RSD could be, for example, SSC mode.

The implementation of the first indication information in combination with specific application scenarios will be described below.

First scenario: the network device is the first core network element, the first indication information is sent to the second core network element by the first core network element through the first storage entity, and the first storage entity is sent to the UE by the second core network entity through a NAS message.

Herein, the first core network element may be a PCF and the second core network element may be an AMF. The NAS message refers to the downstream NAS message.

In an embodiment, the first indication information and the first policy may be transmitted via the same message. In another implementation, the first indication information and the first policy may be transmitted via different messages. The first policy is a policy transmitted to the UE by the first core network element.

In addition, as long as the first indication information and the first policy are transmitted by the same message, the first indication information may be included in the first rule rule and/or the first indication information may be included in the RSD according to the first policy rule.

With reference to FIG. 8 The PCF may send the first indication information to the UE. The first pointing information is included in the storage object. The storage object is sent to the AMF from the PCF and transparently transmitted to the UE by the AMF via a downstream NAS message. That is, the storage object does not need to be checked or modified by the intermediate network element (AMF and RAN) when transmitted to the UE from the PCF. In addition, the first indication information may be sent to the UE together with the UE policy through the same message. In particular, the first indication information may include the following possible forms:

1. The first indication information is sent independently, and the first indication information is independent of the rest of the UE policy; and

2. The first indication information is included in the policy rule of the UE. URSP is taken as an example. The first indication information may be added to the rule or RSD in accordance with this rule. As shown in Table 3, the first indication information is added to the URSP rule, and the first indication information indicates whether (can be) a rule-to-rule mapping used in EPS (simply, whether policy mapping can be performed on the rule). In addition, as shown in Table 4, the first indication information may also be added to the RSD according to the URSP rule, and the first indication information indicates whether the mapping of the RSD to the rule parameter used in the EPS is allowed (simply, whether the policy mapping can be performed for RSD). The first indication information may also be added to one or more parameters in accordance with the RSD, for example, the first indication information may be added to at least one of SSC mode, S-NSSAI, DNN, PDU session type, non-seamless offload indication, preferences for access type, valid time slot, and valid area. It should be noted that the first indication information may optionally be added as shown in Table 3 and Table 4.

Information name Description Category Allow PCF modification in UE context Borders Rule Priority Specifies the order in which the URSP rule is enforced in the UE. Mandatory (REC 1) Yes UE context Traffic descriptor This part defines the components of the traffic descriptor for the URSP rule. Mandatory (REC 3) Application Descriptors Consists of OSId and OSAppId. (RECORD 2) Not necessary Yes UE context IP Descriptors (ENTRY 5) Destination IP 3 tuple(s) (IP address or IPv6 network prefix, port number, protocol ID in protocol over IP). Not necessary Yes UE context Domain Descriptors Target(s) FQDN Not necessary Yes UE context Non-IP Descriptors (ENTRY 5) Descriptor(s) for non-IP traffic target information Not necessary Yes UE context DNN This is matched against the DNN information provided by the application. Not necessary Yes UE context Connectivity This is compared with the information provided by the UE application when requesting a network connection with certain capabilities. (REC 4) Not necessary Yes UE context First pointing information Specifies whether (may be) allowed to configure a rule to map to a rule used in EPS. List of route selection descriptors List of route selection descriptors. The components of a route selection descriptor are described in Table 6.6.2.1-3. Necessarily

Table 3: URSP rule (including first indication information)

Information name Description Category Allow PCF Modification in URSP Borders Priority of route selection descriptors Specifies the order in which route selection descriptors should be applied. Mandatory (REC 1) Yes UE context First pointing information Indicates whether RSD configuration is allowed to map to a rule parameter used in EPS. Route Selection Components This part defines the route selection components Mandatory (REC 2) SSC mode selection One single SSC mode value.
(REC 5) Not necessary First pointing information Yes UE context Selecting a network fragment Either a single value or a list of S-NSSAI values. Optional (REC 3) First pointing information Yes UE context DNN selection Either a single value or a list of DNN values. Not necessary First pointing information Yes UE context Selecting the PDU session type One single PDU session type value Not necessary First pointing information Yes UE context Specifying a Non-Breakless Discharge Indicates whether conforming application traffic should be offloaded to non-3GPP access outside of the session PDU. Optional (REC 4) First pointing information Yes UE context Access type preference Indicates the preferred access type (3GPP or non-3GPP or multiple access) when the UE establishes a session PDU for a negotiating application. Not necessary First pointing information Yes UE context Criteria for validating route selection (REC 6) This part defines the components of the route validation criteria. Not necessary Time interval The time interval in which conforming traffic is allowed. The RSD is not considered valid if the current time is not within the given time interval. Not necessary First pointing information Yes UE context Location criteria The location of the UE where the negotiated traffic is allowed. The RSD rule is not considered valid if the location of the UE does not match the location criteria. Not necessary First pointing information Yes UE context

Table 4: RSD (including first index information)

In an optional implementation, the UE may send the second indication information to the network device. The second indication information indicates the UE's policy mapping capability and/or the UE's waiting or not waiting for the policy mapping to be performed. In a specific implementation, the second indication information may be sent to the second core network element (eg, AMF) of the UE via the second storage entity, and the second storage entity may be sent to the first core network element (eg, PCF) by the second core network element (eg, AMF). ) via a NAS message. In addition, the second storage object is included in the registration request message. Therefore, the PCF may transmit the first indication information based on the second indication information reported by the UE.

Second scenario: the network device is the second core network element, the first indication information is sent to the UE by the second core network element in the registration process, and the first indication information is included in the registration request response message.

In this document, the second core network element may be an AMF.

In an optional implementation, the UE may send the second indication information to the network device. The second indication information indicates the UE's policy mapping capability and/or the UE's waiting or not waiting for the policy mapping to be performed. In addition, the second indication information is included in the registration request message.

With reference to FIG. 9, the UE may report the second indication information in the registration request (the second indication information is optionally reported), so that the AMF may transmit the first indication information based on the second indication information reported by the UE. For example, the AMF may determine whether to allow the UE to map policies (by making the determination according to the UE's subscription information or a parameter such as the network fragment parameter reported by the UE in the registration request) and notify the UE of the first indication information via a request response message. registration (eg, registration acceptance messages).

It should be pointed out that the granularity of the display of policies in the first indication information in the first scenario and the second scenario is not limited in the present invention. The following third scenario is a solution for performing policy mapping by accepting a session PDU as a granularity.

Third Scenario: The network device is the third core network element, and the first indication information is sent to the UE by the third core network element in the process of establishing or modifying a PDU session. The PDU session establishment or modification process is implemented to establish or modify the first PDU session, and the first PDU session corresponds to the first RSD according to the first rule.

In this document, the third core network element may be an SMF.

The first pointing information may indicate at least one of the following:

whether the UE is allowed to display policies;

whether the first rule corresponding to the first PDU session is available for policy mapping;

whether the first RSD is available according to the first rule corresponding to the first session PDU for policy mapping;

option available for displaying policies in the first RSD; and

option not available for displaying policies in the first RSD.

Optionally, the UE may send second indication information to the network device, the second indication information indicating the UE's policy mapping capability and/or the UE waiting or not waiting for the policy mapping to be performed. In addition, the second indication information is included in the PDU session establishment or modification request message.

With reference to FIG. 10, the UE may report the second indication information in the registration request when starting the session establishment of the PDU (the second indication information is optionally reported), so that the SMF may transmit the first indication information based on the second indication information reported by the UE. For example, the SMF after receiving the second indication information may determine whether to allow the UE to execute the policy mapping. Similarly, in the PDU session modification flow, the SMF may also interact with the UE via a NAS message to transmit the first indication information to the UE.

It should be pointed out that in the third scenario, the first indication information may be transmitted based on the flow regarding the establishment or modification of the session PDU. Thus, the mapping of policies in the first indication information is that the session PDU is received as granularity.

In an optional implementation, the URSP includes URSP-rule-1/2/3 and URSP-rule-1/2/3 has corresponding RSD-1/2/3. After matching the traffic descriptor to the URSP rule-2 traffic descriptor and successfully associating it with the session PDU corresponding to RSD-2, based on the RSD in accordance with the URSP rule, the UE may: 1) display all or part of the RSD-1/2/3 parameters according to URSP rule-2 to use when the UE transitions to EPS, or 2) display all or part of the RSD-2 parameters according to URSP rule-2 to use when the UE transitions to EPS. For example, when the UE executes the mapping process according to 2), the parameter obtained by mapping based on RSD-2 is the flag parameter corresponding to the PDN connection in the EPS. In addition, a data flow matching a traffic descriptor in URSP-rule-2 may be associated with a PDN connection for transmission.

In an embodiment of the present invention, docking data binding (including handover or handover) from 5GS to EPS is considered. In particular, the UE may execute two processes, which are evaluation/reassessment and binding/rebinding under a certain condition. However, PDN connection data corresponding to some PDU sessions should not be rebound immediately, as this may affect the continuity of the data service (eg, the IP address may change). When docking, the following two methods of handling sessions are used.

Condition 1): In the handover process, the network side maps the session PDU to a parameter corresponding to the PDN connection, thereby generating an SM context. In this process, the UE does not need to send a request to establish a PDN connection, and a parameter related to the establishment of a PDN connection is generated by the network side.

Condition 2): For the 5GS to EPS UE handover scenario via Radio Resource Control (RRC), the UE sends a Tracking Area Update Request (TAU) or an attached request message after completing RRC establishment with UMTS Evolved Terrestrial Radio Access Network (E-UTRAN). Under this condition, the PDN connection parameter corresponding to the PDU session is generated (mapped) by the network side. Under the condition that the UE transitions to the EPS, the UE may send a PDN connection establishment request message, the PDN connection establishment request message including a handover flag and a PDU session identifier, so that the network side, after receiving the message, may display a context corresponding to PDU session ID, per SM EPS context to use.

Based on the above two conditions, a case is considered in which the network side maps the PDU session parameter to the PDN connection when the UE transitions from 5GS to EPS, and the UE may be required to maintain the association between the application data and the corresponding PDN connection to ensure service continuity. That is, the application data originally transmitted in the session PDU is still transmitted in the PDN connection to which the network side is mapped. For example, application-1 data may be associated with session-1 PDU in 5GS. Assuming that the UE transitions from 5GS to EPS (handover or handover process is performed), the network side obtains PDN connection parameter-1 corresponding to session-1 PDU by mapping, the UE can determine by mapping based on the policy of the UE in 5GS that app-1 should be bound, or preferably bound, to PDN connection-2. In such a case, the UE retains the association between Application-1 and PDN Connection-1, subject to transition to PDN Connection-1. The UE, when triggered by a particular condition (eg, the UE enters idle state or PDN connection-1 is deleted), can create a new association, namely application-1 binding to PDN connection-2.

Based on this, the UE, under the condition of switching from the first mobile communication system to the second mobile communication system, can update the association between data and the first connection according to a policy corresponding to the second mobile communication system. It should be noted that the policy in the second mobile communication system may be obtained by mapping the policy in the first mobile communication system, or may also be obtained other than by mapping the policy in the first mobile communication system, for example, by obtaining the policy in the second mobile communication system from the network. .

In an optional implementation, assuming the UE transitions to EPS, the association between data and the first connection (e.g., PDN connection) should be updated according to the UE's policy in the EPS (the UE's policy in the EPS may be obtained by mapping the UE's policy in 5GS, or may also be obtained other than by mapping the UE policy to 5GS, for example, by obtaining the UE policy to EPS from the network).

In addition, the operation of updating the association between the data and the first connection according to the policy corresponding to the second mobile communication system may include the following: according to the policy corresponding to the second mobile communication system, at least one of the following operations is performed: evaluating the first connection corresponding to data (i.e. evaluation operation); and associating data with the first connection.

Optionally, provided that the UE transitions from the first mobile communication system to the second mobile communication system when the UE enters the idle state or the first timer expires, the association between the data and the first connection can be updated. In an optional implementation, provided that the UE transitions to the EPS, the UE does not evaluate the UE policy belonging to the EPS to the EPS. Upon entering the idle state, the UE evaluates the UE policy in the EPS and then associates the data with the PDN connection based on the result of the evaluation. In an optional implementation, provided that the UE transitions to the EPS, the UE evaluates the UE policy belonging to the EPS to the EPS, but does not associate data with the PDN connection based on the evaluation result before entering the idle state.

In another optional implementation, provided that the UE transitions from the first mobile communication system to the second mobile communication system, the association between the data and the first connection can be updated in the connected state. In an optional implementation, provided that the UE transitions to the EPS, the UE may evaluate the UE policy belonging to the EPS in the connected EPS and associate the data with the PDN connection. It should be noted that when the association between the data and the PDN connection corresponding to the PDU session under these two conditions needs to be changed, the association is changed only when the handover or UE reorientation to the EPS is performed and enters the idle state, or a certain time passes, or a specific carrier or QoS data stream is emitted.

Optionally, the first connection in the solution may be a PDN connection or a PDU session.

In an optional implementation, during a voice transition in an EPS transition, a PDU session including a QoS flow with a 5G Quality Index (5QI) = 1 may be mapped to a PDN connection of a QoS carrier with a QoS Class Identifier (QCI) = 1 (here flow / the QoS carrier is adapted to carry the IMS data packet), and then a PDU session can be established in the EPS. In such a case, although the association judged based on the UE's policy in the EPS requires the IMS message to be bound to another session for transmission, the association must be changed after the UE enters the idle state in the EPS or emits a QoS carrier with QCI = 1, otherwise voice the service may be interrupted.

According to the technical solution of an embodiment of the present invention, a method is provided for mapping a UE policy from 5GS to an EPS under the control of a service provider, so that the data flow in the EPS can be controlled by using the UE policy in 5GS, provided that an ANDSF network element is not deployed in the 4G network to configure the policy. U.E. In addition, UE policy mapping can be triggered based on different existing flows to reduce the impact on the existing protocol and mechanism.

Most of the examples in the technical solution of an embodiment of the present invention are based on a UE transition scenario from 5GS to EPS. It should be understood that the UE transition scenario from EPS to 5GS may also apply to the technical solution of an embodiment of the present invention.

In FIG. 11 is a block diagram of the composition of a policy mapper according to an embodiment of the present invention. As shown in FIG. 11, the policy mapper includes a mapper 1101.

The mapper 1101 is configured to map all or part of the policies used in the first mobile communication system to the policy used in the second mobile communication system, the policies used in the first system including at least one of ANDSF and URSP.

In an embodiment, the policies used in the first mobile communication system may at least include ANDSP.

The mapper 1101 is configured to copy all or part of the ANDSP content to the second mobile communication system for use.

In an embodiment, the policies used in the first mobile communication system may at least include a URSP.

The mapper 1101 is configured to map all or part of the URSP rules to the second mobile communication system for use.

The first rule used in the first mobile communication system and the second rule used in the second mobile communication system correspond to the same traffic descriptor and/or rule priority, and the second rule is obtained by mapping the first rule.

In an embodiment, when one or more first URSP rules are to be displayed, the mapper 1101 may display and/or copy at least a portion of the RSD parameters in accordance with the one or more first rules to a second mobile communication system for use.

In an embodiment, the RSD may include at least one of the following: SSC Mode, S-NSSAI, PDU Session Type, DNN, Non-Seamless Offload Indication, Access Type Preference, Valid Time Slot, and Valid Area.

In an optional implementation, mapper 1101 is configured to map S-NSSAI and/or DNN to APN.

In an optional implementation, the mapper 1101 is configured to map the PDU session type to the PDN connection type.

In an implementation, assuming the session type of the PDU is an Ethernet type,

in response to the UE and the network in the second mobile communication system supporting the Ethernet PDN connection type, the mapping unit 1101 may map the PDN connection type to the Ethernet type; or

in response to the UE and/or the network in the second mobile communication system supporting the non-IP type and not supporting the Ethernet type, the mapper 1101 may map the PDN connection type to the non-IP type.

In an implementation, assuming the session type of the PDU is a flat type:

the mapping unit 1101 may map the PDN connection type to a non-IP type.

In an embodiment, the mapper 1101 is configured to copy at least one of the non-seamless download indication, access type preference, valid time slot, and valid area to the second mobile communication system for use.

In an embodiment, the device may further comprise a setting unit configured to set the SSC mode in RSD to zero or the first SSC mode.

In the embodiment, the mapper 1101 is further configured to add the first parameter to the policy obtained by mapping, and apply the policy with the added first parameter to the second mobile communication system.

In an embodiment, the device may further comprise a receive block 1102.

The receiving unit 1102 is configured to receive first indication information from the network device, wherein the first indication information points to at least one of the following:

whether the UE is allowed to display policies;

the first policy to be displayed;

a rule available to display policies in the first policy;

whether RSD is available according to each rule of the first policy to display policies;

option available for displaying policies in RSD; and

option not available for displaying policies in RSD.

In an embodiment, the network device may be the first element of the core network.

The first indication information may be sent to the second core network element by the first core network element via the first storage entity, and the first storage entity may be sent to the UE by the second core network element via a NAS message.

In an embodiment, the first indication information and the first policy may be transmitted via the same message or different messages, and the first policy may be a policy transmitted to the UE by the first core network element.

In an embodiment, provided that the first indication information and the first policy can be transmitted via the same message,

the first indication information may be included in the first policy rule; and/or

the first indication information may be included in the RSD according to the first policy rule.

In an embodiment, the device may further comprise a sender 1103.

The sender 1103 is configured to send second indication information to the network device, the second indication information indicating the UE's policy mapping capability and/or the UE waiting or not waiting for the policy mapping to be performed.

In an embodiment, the second pointing information may be sent to the second core network element of the UE via the second storage entity, and the second storage entity may be sent to the first core network element by the second core network element via the NAS message.

In an embodiment, the second store object may be included in the registration request message.

In an embodiment, the network device may be the second core network element.

The first indication information may be sent to the UE by the second core network element in the registration process, and the first indication information may be included in the registration request response message.

In an embodiment, the device may further comprise a sender 1103.

The sender 1103 is configured to send second indication information to the network device, the second indication information indicating the UE's policy mapping capability and/or the UE waiting or not waiting for the policy mapping to be performed.

In an embodiment, the second store object may be included in the registration request message.

In an embodiment, the device may further comprise a receive block 1102.

The receiving unit 1102 is configured to receive first indication information from the network device, wherein the first indication information points to at least one of the following:

whether the UE is allowed to display policies;

whether the first rule corresponding to the first PDU session is available for policy mapping;

whether the first RSD is available according to the first rule corresponding to the first session PDU for policy mapping;

option available for displaying policies in the first RSD; and

option not available for displaying policies in the first RSD.

In an embodiment, the network device may be the third core network element.

The first indication information may be sent to the UE by a third core network element in the process of establishing or modifying a PDU session. The PDU session establishment or modification process is implemented to establish or modify the first PDU session, and the first PDU session corresponds to the first RSD according to the first rule.

In an embodiment, the device may further comprise a sender 1103.

The sender 1103 is configured to send second indication information to the network device, the second indication information indicating the UE's policy mapping capability and/or the UE waiting or not waiting for the policy mapping to be performed.

In an embodiment, the second indication information may be included in the PDU session establishment or modification request message.

In an embodiment, the device may further comprise an updater 1104, configured to, on condition that the UE transitions from the first mobile communication system to the second mobile communication system, update the association between the data and the first connection according to a policy corresponding to the second mobile communication system.

In an embodiment, updater 1104 is configured to perform at least one of the following operations according to a policy corresponding to the second mobile communication system:

evaluate the first connection that matches the data; and

associating data with the first connection.

In an embodiment, updater 1104 is configured to, on the condition that the UE transitions from the first mobile communication system to the second mobile communication system when the UE enters an idle state or the first timer expires, update the association between the data and the first connection.

In an embodiment, the updater 1104 is configured to, provided that the UE transitions from the first mobile communication system to the second mobile communication system, update the association between the data and the first connection in the connected state.

In an implementation, the first connection may be a PDN connection or a PDU session.

Those skilled in the art will appreciate that descriptions relating to a policy mapper according to embodiments of the present invention can be understood with reference to descriptions relating to a policy mapping method according to embodiments of the present invention.

In FIG. 12 is a schematic structural view of a communication device 1200 according to an embodiment of the present invention. The communication device may be a terminal. Communication device 1200 shown in FIG. 12 includes a processor 1210, and the processor 1210 can call and run a computer program in a storage device to implement the method in the embodiments of the present invention.

Optionally, as shown in FIG. 12, communication device 1200 may further comprise a memory 1220. Processor 1210 may call and execute a computer program in memory 1220 to implement the method in embodiments of the present invention.

Memory 1220 may be independent of processor 1210 and may also be integrated with processor 1210.

Optionally, as shown in FIG. 12, communications device 1200 may further include a transceiver 1230. Processor 1210 may control transceiver 1230 to communicate with another device, such as sending information or data to another device, or receiving information or data sent by another device.

The transceiver 1230 may include a transmitter and a receiver. The transceiver 1230 may further comprise an antenna, and the number of antennas may be one or more.

The communication device 1200 may optionally, in particular, be a network device according to an embodiment of the present invention. Communication device 1200 may implement respective flows implemented by a network device in each method according to embodiments of the present invention. In this document, detailed descriptions are omitted for simplicity.

Communication device 1200 may optionally, in particular, be a mobile terminal/terminal according to embodiments of the present invention. The communication device 1200 may implement the respective flows implemented by the mobile terminal/terminal in each method according to the embodiments of the present invention. In this document, detailed descriptions are omitted for simplicity.

In FIG. 13 is a schematic structural view of a chip according to another embodiment of the present invention. Chip 1300 shown in FIG. 13 includes a processor 1310, and the processor 1310 can call and run a computer program in a storage device to implement the method in the embodiments of the present invention.

Optionally, as shown in FIG. 13, the chip 1300 may further comprise a memory 1320. The processor 1310 may call and execute a computer program in the memory 1320 to implement the method in the embodiments of the present invention.

Memory 1320 may be independent of processor 1310 and may also be integrated with processor 1310.

Optionally, chip 1300 may further include input interface 1330. Processor 1310 may control input interface 1330 to communicate with another device or chip, such as receiving information or data sent by another device or chip.

Optionally, chip 1300 may further comprise an output interface 1340. Processor 1310 may control output interface 1340 to communicate with another device or chip, such as outputting information or data sent by another device or chip.

Optionally, a chip according to embodiments of the present invention may be applied to the network device. The chip may implement the respective flows implemented by the network device in each method according to the embodiments of the present invention. In this document, detailed descriptions are omitted for simplicity.

Optionally, a chip may be applied to the mobile terminal/terminal according to the embodiment of the present invention. The chip may implement the respective flows implemented by the mobile terminal/terminal in each method according to the embodiments of the present invention. In this document, detailed descriptions are omitted for simplicity.

It should be understood that the chip mentioned in the embodiment of the present invention may also be referred to as a system-level chip, system chip, chip system or system on a chip, etc.

In FIG. 14 is a second block diagram of a communications system 1400 according to an embodiment of the present invention. As shown in FIG. 14, communication system 1400 includes a terminal 1410 and a network device 1420.

Terminal 1410 may be configured to implement respective functions implemented by the terminal in the method, and network device 1420 may be configured to implement respective functions implemented by the network device in the method. In this document, detailed descriptions are omitted for simplicity.

It should be understood that the processor in an embodiment of the present invention may be an integrated circuit chip and has signal processing capability. During implementation, each operation of the method embodiments may be performed by a hardware integrated logic circuit in a processor or by an instruction in the form of software. The processor may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete logic element or a transistorized logic device, and a discrete hardware component. Each method, operation, and flowchart disclosed in the embodiments of the present invention may be implemented or executed. The general purpose processor may be a microprocessor, or the processor may also be any conventional processor, and the like. hardware and software modules in the decoding processor. The software module may be located on a storage medium well known in the art such as random access memory (RAM), flash memory, read only memory (ROM), programmable ROM (PROM) or electrically erasable PROM (EEPROM) and a register. . The storage medium is located in the storage device, and the processor reads the information in the storage device and performs the operations of the method in conjunction with the hardware.

It should be understood that the storage device in an embodiment of the present invention may be a volatile storage device or a non-volatile storage device, or may contain both volatile and non-volatile storage devices. The non-volatile storage device may be ROM, PROM, Erasable PROM (EPROM), EEPROM, or flash memory. The volatile memory may be RAM and is used as an external high speed cache. By way of example, and not limitation, it is described that RAM in various forms can be used, for example, static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), advanced SDRAM (ESDRAM), Synchronous Channel DRAM (SLDRAM) and Direct Resident Access Bus RAM (DR RAM). It should be noted that the memory of the system and method described herein is intended to include, but is not limited to, these and any other suitable types of memory.

It should be understood that the storage device is described by way of example and not limitation. For example, the storage device in embodiments of the present invention may also be SRAM, DRAM, SDRAM, DDR SDRAM, ESDRAM, SLDRAM, and DR RAM. That is, the storage device in the embodiments of the present invention is intended to include, but is not limited to, storage devices of these and any other suitable types.

Embodiments of the present invention also provide a computer-readable storage medium that is configured to store a computer program.

Optionally, a computer-readable storage medium may be used in a network device in the embodiments of the present invention, and a computer program allows the computer to execute the respective streams implemented by the network device in each method according to the embodiments of the present invention. In this document, detailed descriptions are omitted for simplicity.

Optionally, a computer-readable storage medium may be used in the mobile terminal/terminal in the embodiments of the present invention, and the computer program allows the computer to execute the respective streams implemented by the mobile terminal/terminal in each method according to the embodiments of the present invention. In this document, detailed descriptions are omitted for simplicity.

Embodiments of the present invention also provide a computer program product that contains a computer program instruction.

Optionally, the computer program product may be applied to the network device in the embodiments of the present invention, and the computer program instruction allows the computer to execute the respective flows implemented by the network device in each method according to the embodiments of the present invention. In this document, detailed descriptions are omitted for simplicity.

Optionally, the computer program product may be applied to the mobile terminal/terminal in the embodiments of the present invention, and the computer program instruction allows the computer to execute the respective flows implemented by the mobile terminal/terminal in each method according to the embodiments of the present invention. In this document, detailed descriptions are omitted for simplicity.

Embodiments of the present invention also provide a computer program.

Optionally, a computer program may be applied to the network device in the embodiments of the present invention, and the computer program runs on the computer to allow the computer to execute the respective flows implemented by the network device in each method according to the embodiments of the present invention. In this document, detailed descriptions are omitted for simplicity.

Optionally, a computer program may be applied to the mobile terminal/terminal in the embodiments of the present invention, and the computer program runs on the computer to allow the computer to execute the respective flows implemented by the mobile terminal/terminal in each method according to the embodiments of the present invention. In this document, detailed descriptions are omitted for simplicity.

Those skilled in the art will appreciate that the blocks and operations of the algorithms of each example described in conjunction with the embodiments disclosed herein may be implemented in electronic hardware or a combination of computer software and electronic hardware. Depending on specific applications and design constraints of technical solutions, these functions are performed either in hardware or in software. Skilled artisans may implement the described functions for each particular application using different methods, but such implementation will be within the scope of the present invention.

Those skilled in the art may clearly understand that the specific processes of operation of the system, apparatus, and unit described above may refer to corresponding processes in the method embodiment and will not be detailed herein for convenience and brevity.

It should be understood that in some embodiments provided herein, the disclosed system, apparatus, and method may be implemented in other ways. For example, the device embodiment described above is only schematic. For example, the division of blocks is only the division of logical functions. In practical implementation, other methods of separation can be applied. For example, several blocks or components may be combined or integrated into another system, or certain features may be omitted or not implemented. In addition, the connection, or direct connection, or communication connection between each of the shown or discussed components may be an indirect connection or communication connection implemented through some interfaces of the device or blocks, and may be electrical and mechanical or take other forms.

Blocks described as separate parts may or may not be physically separated. The parts shown as blocks may or may not be physical blocks, namely they may be located in the same place or may also be distributed over several network blocks. Some or all of the blocks may be selected to achieve the solutions of the embodiments according to practical requirement.

In addition, each functional block in each embodiment of the present invention can be integrated into a processing block, each block can also physically exist separately, and two or more than two blocks can also be integrated into one block.

When implemented as a functional block of software and sold or used as a stand-alone product, the function may also be stored on a computer-readable storage medium. Based on such an understanding, the technical solutions of the present invention per se, or parts contributing to the prior art, or part of the technical solutions can be implemented in the form of a software product. The computer program product may be stored on a storage medium including a plurality of instructions for allowing a computing device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the operations of the method in each embodiment of the present invention. inventions. The above-mentioned storage medium includes: various media that can store program codes such as U-disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk.

The above is only a specific mode of implementation of the present invention, and is not intended to limit the scope of legal protection of the present invention. Any modifications or substitutions obvious to those skilled in the art, within the technical scope disclosed in this application, are within the scope of the legal protection of the present invention. Therefore, the scope of legal protection of the present invention will depend on the scope of legal protection of the claims.

Claims (30)

1. A method for displaying policies, including: mapping by the user equipment (UE) of a part of the policies used in the first mobile communication system to the corresponding policy(s) used(s) in the second mobile communication system, wherein the policies used in the first mobile communication system at least include a UE Route Selection Policy (URSP); wherein the UE's mapping of a portion of the policies used in the first mobile communication system to corresponding policies used in the second mobile communication system includes: mapping by the UE of all the rules or parts of the URSP rules to the second mobile communication system for use, wherein the first rule used in the first mobile communication system and the second rule used in the second mobile communication system correspond to the same traffic descriptor and/or rule priority, and the second rule is obtained by mapping the first rule. 2. The method of claim. 1, characterized in that in response to the need to display the first URSP rule, at least part of the parameters of the descriptor (descriptors) route selection (RSD) in accordance with the first rule is displayed and/or copied by the UE to the second mobile communication system for use. 3. The method according to claim 2, characterized in that the RSD includes at least one of the following parameters: session and service continuity mode (SSC), supporting information Single Network Fragment Selection (S-NSSAI), Session Type for Protocol Data Unit (PDU), Data Network Name (DNN), Non-Bearless Offload Indication, Access Type Preference, Valid Time Slot, and Valid Area. 4. The method of claim 3, wherein the S-NSSAI and/or DNN are mapped by the UE to an access point name (APN). 5. The method according to claim 3 or 4, wherein the session type of the PDU is mapped by the UE to a public data network (PDN) connection type. 6. The method of claim. 5, characterized in that, provided that the session type of the PDU is an Ethernet type, in response to the support by the UE and the network in the second mobile communication system of the PDN Ethernet connection type, the PDN connection type is mapped by the UE to the Ethernet type; or the PDN connection type is mapped by the UE to a non-Internet (IP) protocol type. 7. The method of claim 5, wherein, provided that the session type of the PDU is an unstructured type, the connection type of the PDN is mapped by the UE to a non-Internet (IP) protocol type. 8. The method according to any one of paragraphs. 3-7, characterized in that at least one of the non-seamless offload indication, access type preference, valid time slot, and valid area is copied by the UE to the second mobile communication system for use. 9. The method according to any one of paragraphs. 3-8, characterized in that the RSD SSC mode is set by the UE to zero or the first SSC mode. 10. The method according to any one of paragraphs. 1-9, characterized in that it additionally includes: UE receiving first indication information from the network device, wherein the first indication information points to at least one of the following: whether the UE is allowed to display policies; the first policy to be displayed; a rule available to display policies in the first policy; whether RSD is available according to each rule of the first policy to display policies; option available for displaying policies in RSD; and option not available for displaying policies in RSD. 11. The method according to p. 10, characterized in that the network device is the first element of the core network; and the first indication information is sent to the second core network element by the first core network element via the first storage entity, and the first storage entity is sent to the UE by the second core network entity via a Non-Access Layer (NAS) message. 12. A policy-mapping chip, comprising a processor configured to call and run a computer program in a storage device to allow a device in which the chip is installed to execute the method of any one of claims. 1-11. 13. A computer-readable storage medium configured to store a computer program, and moreover, the computer program allows the computer to execute the method according to any one of paragraphs. 1-11.

Images