Policy configuration method and apparatus

Abstract

The present application relates to the technical field of communications, and in particular to a policy configuration method and apparatus, aiming to enable a terminal device side and a network side to have consistent understanding on a terminal device policy used by a terminal device. The method may be executed by a hosted AMF network element. The method comprises: acquiring a first policy of a hosted PLMN for a terminal device, the first policy carrying a hosted PLMN identifier of the hosted PLMN; on the basis of determining that the terminal device is in an INS scenario, deleting the hosted PLMN identifier carried by the first policy, or replacing the hosted PLMN identifier carried by the first policy with a participating PLMN identifier of a participating PLMN to which the terminal device registers, to obtain a second policy; and sending the second policy to the terminal device.

Description

A strategy configuration method and apparatus

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411042231.9, filed on July 30, 2024, entitled "A Strategy Configuration Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and in particular to a strategy configuration method and apparatus. Background Technology

[0004] Network sharing refers to the sharing of network facilities between two or more operators. By sharing network facilities, network construction costs can be reduced, and network operating expenses can be lowered. Network sharing can be categorized by the scope of sharing, including site sharing, base station sharing, transmission sharing, radio network controller (RNC) sharing, and / or core network sharing, or even sharing the entire network. The cost savings vary depending on the level of network sharing. Since site sharing and base station sharing account for the majority of network construction and maintenance costs, sharing site sharing and / or base station sharing represents the network sharing model with the highest potential for cost savings and is the most effective.

[0005] The 3rd Generation Partnership Project (3GPP) working group is discussing indirect network sharing (INS), in which different operators can share access network equipment. For example, Operator 1 can act as a managed operator and share its access network equipment with other participating operators (such as Operator 2, Operator 3, etc.). When a managed operator shares access network equipment with other participating operators, the shared access network equipment is managed by its respective managed operator, and communication between the shared access network equipment and the core networks of the participating operators is routed through the core network of the managed operator connected to the shared access network equipment.

[0006] Shared access network (SNR) devices (such as those belonging to an operator) can broadcast the public land mobile network (PLMN) identifiers (IDs) of other participating operators, allowing terminal devices to access other participating operators' PLMNs through the shared SNR device. However, when a terminal device accesses another participating operator's PLMN through the shared SNR device, because the terminal device is registered with that other participating operator's PLMN, it is unaware of the managed operator's PLMN and will not use the corresponding managed operator's (e.g., Operator 1) PLMN policy issued by the network. Since communication between the shared SNR device and the participating operator's core network is routed through the managed operator's core network, the network side can detect the terminal device accessing the managed operator's PLMN and will assume that the terminal device is using the corresponding managed operator's PLMN policy. This leads to a discrepancy between the terminal device's and the network side's understanding of the policy used by the terminal device. This may result in the terminal device making incorrect routing choices and / or selecting the wrong radio LAN due to incorrect policy usage. It may also cause the network side to continuously issue policy updates for the corresponding managed operator's PLMN to the terminal device, which the terminal device cannot use, resulting in a waste of signaling and other resources. Summary of the Invention

[0007] This application provides a policy configuration method and apparatus to align the understanding of the policies used by the terminal device and the network side, thereby avoiding incorrect routing and / or selection of the wrong wireless LAN by the terminal device due to incorrect policy usage, and the waste of signaling and other resources caused by inconsistent understanding of the policies used by the terminal device.

[0008] In a first aspect, embodiments of this application provide a policy configuration method, which can be executed by a managed core network element. The method includes: obtaining a first policy from a managed PLMN for a terminal device, the first policy carrying a managed PLMN identifier; based on the determined terminal device being in an INS scenario, deleting the managed PLMN identifier carried in the first policy, or replacing the managed PLMN identifier carried in the first policy with a participating PLMN identifier registered by the terminal device, to obtain a second policy; and sending the second policy to the terminal device. The managed core network element can be a managed access and mobility management network element or a managed policy control function network element, i.e., an access and mobility management network element or a policy control function network element of the managed PLMN.

[0009] Using the above method, in scenarios where terminal devices register with the INS participating in the PLMN through shared access network devices of the managed PLMN, the managed AMF network element or managed PCF network element can disguise the first policy of the managed PLMN for the terminal device as the policy of the PLMN to which the terminal device belongs or the policy of the PLMN to which the terminal device is registered. This allows the terminal device to use the policy of the managed PLMN for the terminal device, aligns the understanding of the policy used by the terminal device on the terminal device side and the network side, avoids the terminal device making incorrect routing selection and / or selecting the wrong wireless LAN due to incorrect policy usage, and avoids the waste of signaling and other resources caused by inconsistent understanding of the policy used by the terminal device.

[0010] In one possible design, the method further includes: determining that the terminal device is in an INS scenario before obtaining the first policy of the managed PLMN for the terminal device; or, determining that the terminal device is in an INS scenario after obtaining the first policy of the managed PLMN for the terminal device.

[0011] The above design allows managed core network elements to obtain the first policy before determining that the terminal device is in an INS scenario, and also allows core network elements to obtain the first policy after determining that the terminal device is in an INS scenario, which helps to improve the flexibility of the managed core network elements in executing policy configuration methods.

[0012] In one possible design, the first policy is a user equipment (UE) routing selection policy (URSP), which leads to a second policy, including: if the participating PLMN is the home PLMN of the terminal equipment, the managed PLMN identifier carried in the first policy is deleted to obtain the second policy; or, if the participating PLMN is the equivalent home PLMN of the terminal equipment, the managed PLMN identifier carried in the first policy is replaced with the participating PLMN identifier to obtain the second policy.

[0013] Through the above design, the URSP of the managed PLMN for the terminal device can be disguised as the URSP of the PLMN registered by the corresponding terminal device, so that the terminal device can use the URSP of the managed PLMN for the terminal device, and the understanding of the URSP used by the terminal device can be aligned between the terminal device side and the network side.

[0014] In one possible design, the first strategy is a wireless local area network (WLAN) selection policy (WLANSP), which leads to a second strategy, including: the participating PLMN is the home PLMN or equivalent home PLMN of the terminal device, and the managed PLMN identifier carried in the first strategy is replaced with the participating PLMN identifier of the participating PLMN, thus obtaining the second strategy.

[0015] Through the above design, the WLANSP of the managed PLMN for the terminal device can be disguised as the WLANSP of the PLMN registered by the corresponding terminal device, so that the terminal device can use the WLANSP of the managed PLMN for the terminal device, and the understanding of the WLANSP used by the terminal device can be aligned between the terminal device side and the network side.

[0016] In one possible design, the participating PLMN is the home PLMN of the terminal device, and the method further includes setting the priority of the rules carried by the second policy to be higher than the priority of the rules carried by the participating PLMN for the terminal device in the third policy.

[0017] Through the above design, when the participating PLMN is the home PLMN of the terminal device, after the corresponding managed policy is disguised as the policy of the home PLMN of the corresponding terminal device, the rule priority of the disguised policy can be set to be higher than the rule priority of the real home PLMN of the corresponding terminal device, so that the terminal device can use the policy of the corresponding managed PLMN without being aware of the managed PLMN.

[0018] In one possible design, if the participating PLMN identifier is the same as the PLMN identifier carried in the terminal device's identification information, the participating PLMN is determined to be the terminal device's home PLMN; or, if the participating PLMN identifier is different from the PLMN identifier carried in the terminal device's identification information, the participating PLMN is determined to be the terminal device's equivalent home PLMN.

[0019] The above design allows the managed core network element to identify whether the participating PLMN is the home PLMN of the terminal device or the equivalent home PLMN of the terminal device, thereby supporting the adjustment of the managed PLMN identifier carried by the first strategy.

[0020] In one possible design, the method further includes: receiving first information from a terminal device, the first information including a policy section identifier (PSI) corresponding to the second policy and a participating PLMN identifier; based on the determined terminal device being in an INS scenario, replacing the participating PLMN identifier included in the first information with a managed PLMN identifier to obtain a second message; and sending the second information to the policy control function network element of the terminal device's home PLMN.

[0021] Through the above design, since the terminal device is in an INS scenario, the PLMN identifier is modified before the first policy is sent to the terminal device. The second policy is then sent to the terminal device. When the terminal device re-initiates registration in cases such as network loss or power-off and power-on, the managed core network element can replace the PLMN identifier corresponding to the PSI and the participating PLMN identifier corresponding to the PSI with the managed PLMN identifier, thus avoiding the policy control function network element of the terminal device's home PLMN misinterpreting the PLMN identifier corresponding to the PSI.

[0022] In one possible design, before sending the second policy to the terminal device, the method further includes: receiving first indication information from the access and mobility management function network element of the managed PLMN, the first indication information indicating that the terminal device is in an INS scenario, or indicating that the terminal device is not registered to the managed PLMN.

[0023] Through the above design, the managed policy control function network element can determine that the terminal device is in the INS scenario based on the first instruction information from the managed access and mobility management function network element.

[0024] In one possible design, receiving first indication information from the managed PLMN's access and mobility management function network element includes: receiving first indication information and a PLMN participation identifier from the managed PLMN's access and mobility management function network element.

[0025] The above design allows the managed policy control function network element to obtain the participating PLMN identifier of the terminal device registered with the managed access and mobility management function network element.

[0026] In one possible design, the first terminal device policy may include one or more of the following: access network discovery and selection policy (ANDSP), URSP, vehicle to X (V2X) policy (V2XP), proximity based services (ProSe) policy (ProSeP), WLANSP, etc., wherein ANDSP may include WLANSP.

[0027] Secondly, embodiments of this application provide a policy configuration method, which can be executed by a home policy control function network element (i.e., the policy control function network element of the home PLMN of the terminal device). The method includes: receiving a policy association establishment request from the policy control function network element of the managed PLMN, wherein the policy association establishment request carries the identification information of the terminal device for establishing a policy association for the terminal device; determining a fourth policy of the managed PLMN for the terminal device based on the determined terminal device being in an INS scenario, wherein the fourth policy includes a traffic descriptor and / or a routing descriptor corresponding to the managed PLMN, and the fourth policy does not carry the managed PLMN identifier of the managed PLMN, or carries the participating PLMN identifier of the participating PLMN registered by the terminal device; and sending the fourth policy to the policy control function network element of the managed PLMN.

[0028] Using the above method, when the terminal device is in an INS scenario, and the home policy control function network element determines the fourth policy of the managed PLMN for the terminal device, the fourth policy can be disguised as the policy of the home PLMN of the corresponding terminal device or the policy of the PLMN registered by the terminal device. This allows the terminal device to use the policy of the managed PLMN for the terminal device, which can align the understanding of the policy used by the terminal device and the network side. This avoids the terminal device making incorrect routing selection due to incorrect policy usage, and the waste of signaling and other resources caused by inconsistent understanding of the policy used by the terminal device.

[0029] In one possible design, the participating PLMN is the home PLMN of the terminal device, and the fourth strategy does not carry the host PLMN identifier; or, the participating PLMN is the equivalent home PLMN of the terminal device, and the fourth strategy carries the participating PLMN identifier.

[0030] In one possible design, the participating PLMN is the home PLMN of the terminal device, and the rule priority carried by the fourth policy is higher than the rule priority carried by the home PLMN for the terminal device by the fifth policy.

[0031] In one possible design, the method further includes: receiving third information from a policy control function network element of a managed PLMN, the third information including the PSI corresponding to the fourth policy and the PLMN participation identifier; and determining that the PSI is associated with the managed PLMN identifier based on the fact that the terminal device is in an INS scenario.

[0032] In one possible design, before sending the fourth policy to the terminal device, the method further includes: receiving first indication information from a policy control function network element of the managed PLMN, the first indication information indicating that the terminal device is in an INS scenario, or indicating that the terminal device is not registered to the managed PLMN.

[0033] In one possible design, the fourth strategy is URSP.

[0034] Thirdly, embodiments of this application provide a policy configuration method, which can be executed by a managed policy control function network element (i.e., a policy control function network element of a managed PLMN). The method includes: receiving a policy association establishment request from an access and mobility management function network element of the managed PLMN, wherein the policy association establishment request carries the identification information of a terminal device for establishing a policy association for the terminal device; determining a sixth policy of the managed PLMN for the terminal device based on the determined terminal device being in an indirect network sharing (INS) scenario, wherein the sixth policy includes a service set identifier (SSID) corresponding to the managed PLMN, and the sixth policy carries the participating PLMN identifier of the participating PLMN registered by the terminal device; and sending the sixth policy to the policy control function network element of the managed PLMN.

[0035] Using the above method, when the terminal device is in an INS scenario, and the home policy control function network element determines the sixth policy of the managed PLMN for the terminal device, the sixth policy can be disguised as the policy of the home PLMN of the corresponding terminal device or the policy of the PLMN registered by the terminal device. This allows the terminal device to use the policy of the managed PLMN for the terminal device, which can align the understanding of the policy used by the terminal device on the terminal device side and the network side, and avoid the terminal device selecting the wrong wireless LAN due to incorrect policy usage.

[0036] In one possible design, the participating PLMN is the home PLMN of the terminal device, and the rule priority carried by the sixth policy is higher than the rule priority carried by the home PLMN for the terminal device by the seventh policy.

[0037] In one possible design, the sixth strategy is WLANSP.

[0038] Fourthly, embodiments of this application provide a policy configuration method, which can be executed by a policy control function network element. The method includes: receiving a policy association establishment request, the policy association establishment request carrying the identification information of a terminal device for establishing a policy association for the terminal device; determining that the terminal device is in a non-INS scenario, and sending an eighth policy of the first PLMN for the terminal device and / or a ninth policy of the terminal device's home PLMN for the terminal device to the terminal device, wherein the terminal device accesses the communication network through the access network device of the first PLMN, and the first PLMN is different from the terminal device's home PLMN; determining that the terminal device is in an INS scenario, and sending the ninth policy of the terminal device's home PLMN for the terminal device to the terminal device.

[0039] In the above policy configuration method, the policy control function network element can be a policy control function network element in the first PLMN or the home policy control function network element of the terminal device, etc. Through this method, for the eighth policy corresponding to the first PLMN, the policy control function network element may only issue it to the terminal device when the terminal device is in a non-INS scenario. When the terminal device is in an INS scenario, the policy control function network element does not issue the eighth policy of the first PLMN where the shared access network device is located, and the terminal device does not need to execute the eighth policy of the corresponding first PLMN. This aligns the understanding of the policy used by the terminal device on both the terminal device side and the network side, avoiding inconsistencies in their understanding and preventing the control policy function network element from continuously sending policy updates to the terminal device, thus avoiding waste of signaling and other resources.

[0040] Fifthly, embodiments of this application provide a communication device that has the function of implementing the method of any one of the first to fourth aspects described above. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions, such as an interface unit and a processing unit.

[0041] In one possible design, the device can be a chip or an integrated circuit.

[0042] In one possible design, the device includes a memory and a processor, the memory for storing instructions executed by the processor, and when the instructions are executed by the processor, the device can perform the methods of any one of the first to fourth aspects.

[0043] Sixthly, embodiments of this application provide a communication device including an interface circuit and a processor, wherein the processor and the interface circuit are coupled to each other. The interface circuit is used for inputting and / or outputting signals, and the processor is used to implement the methods of any one of the first to fourth aspects described above through logic circuits or execution instructions. It is understood that the interface circuit can be a transceiver, a transceiver device, or an input / output interface.

[0044] Optionally, the communication device may also include a memory for storing instructions executed by the processor, or storing input data required by the processor to execute instructions, or storing data generated after the processor executes instructions. The memory may be a physically independent unit, or it may be coupled to the processor, or the processor may include the memory (i.e., the processor and the memory are integrated together).

[0045] In one possible implementation, the communication device is a chip.

[0046] In a seventh aspect, embodiments of this application provide a computer-readable storage medium storing a computer program or instructions, which, when executed by a processor, can implement the methods of any one of the first to fourth aspects described above.

[0047] Eighthly, embodiments of this application also provide a computer program product, including a computer program or instructions, which, when executed by a processor, can implement the methods of any one of the first to fourth aspects described above.

[0048] Ninthly, embodiments of this application also provide a chip system including a processor, the processor being coupled to a memory, the memory being used to store programs or instructions, and when the program or instructions are executed by the processor, the methods of any one of the first to fourth aspects described above can be implemented.

[0049] The technical effects that can be achieved by aspects four through nine above are the same as those that can be achieved by aspects one through four above, and will not be repeated here. Attached Figure Description

[0050] Figure 1 is a schematic diagram of the INS provided in an embodiment of this application;

[0051] Figures 2 and 3 are schematic diagrams of strategy generation and distribution provided in the embodiments of this application;

[0052] Figures 4A, 4B, 5A, 5B, 6A, and 6B are schematic diagrams of the system architecture provided in the embodiments of this application;

[0053] Figure 7 is a schematic diagram of the indirect network sharing architecture provided in an embodiment of this application;

[0054] Figures 8, 9, 10, 11, 12, and 13 are schematic diagrams of the strategy configuration method provided in the embodiments of this application;

[0055] Figures 14 and 15 are schematic diagrams of the communication device provided in the embodiments of this application. Detailed Implementation

[0056] This application provides a strategy configuration method and apparatus. The method and apparatus are based on the same inventive concept. Since the principles by which the method and apparatus solve problems are similar, their implementations can be mutually referenced, and repeated details will not be elaborated further.

[0057] To facilitate understanding by those skilled in the art, some terms used in this application are explained below.

[0058] 1) PLMN.

[0059] A PLMN is a public mobile network established and operated by a specific operator in a particular country or region to provide terrestrial mobile communication services to the public. The PLMN identifier (PLMN ID) includes a mobile country code (MCC) and a mobile network code (MNC). The mobile country code is typically 3 digits, and the mobile network code is typically 2 digits. For example, China's country code is 460, and China Unicom's mobile network code is 01, so China Unicom's PLMN ID is 46001. The mobile network code can also be 3 digits, but currently 2 digits are used, so it is usually written as 2 digits.

[0060] The PLMN ID is a crucial component of the International Mobile Subscriber Identity (IMSI). An IMSI typically consists of 15 digits between 0 and 9, with the first 5 digits forming the PLMN ID, and the remaining digits assigned by the network operator as needed. The IMSI can be stored in the user's Subscriber Identity Module (SIM) or Universal Subscriber Identity Module (USIM) card. The PLMN to which this IMSI belongs is called the Home PLMN (HPLMN), which is the PLMN to which the user is registered. This PLMN is where the user opened their account, and all user information and available services are stored in the Home Location Register (HLR) within this PLMN network. When a user leaves the coverage area of ​​this PLMN and registers with another PLMN, that user enters roaming mode.

[0061] PLMN Classification: For a specific terminal device, it is usually necessary to maintain several different types of PLMN lists, each of which contains one or more PLMNs.

[0062] Registered PLMN (RPLMN): This is the PLMN that the terminal device registered before it was last powered off or disconnected from the network.

[0063] Equivalent PLMN (EPLMN): A PLMN that is of equal status to the PLMN currently selected (or registered) by the terminal device, and has the same priority. For example, if an operator has three number segments: 46000, 46002, and 46007, and the terminal device currently selects PLMN 46002, then PLMN 46002 will provide services to the terminal device. PLMNs 46000 and 46007 can be considered equivalent PLMNs to the PLMN currently selected by the terminal device.

[0064] Home PLMN (HPLMN): This is the PLMN to which the terminal device user belongs. In other words, the MCC and MNC contained in the IMSI number on the terminal device's USIM card are consistent with the MCC and MNC on the HPLMN. For a given terminal device, it has only one home PLMN.

[0065] Equivalent Home PLMN (EHPLMN): This is a local PLMN that has the same status as the terminal device's home PLMN. For example, the operator corresponding to an HPLMN may have different number ranges. For instance, an operator may have three number ranges: 46000, 46002, and 46007. 46000 is the terminal device's HPLMN, while 46002 and 46007 are considered the terminal device's EHPLMN.

[0066] Visited PLMN (VPLMN): A PLMN accessed by a terminal device user, also known as a visited PLMN. Its PLMN ID is not exactly the same as the MCC and MNC of the IMSI stored in the SIM card.

[0067] User-controlled PLMN (UPLMN): This is a parameter stored on the USIM card that relates to PLMN selection.

[0068] Operator-controlled PLMN (OPLMN): This is a parameter related to PLMN selection stored on the USIM card.

[0069] Disabled PLMN (forbidden PLMN, FPLMN): This is a PLMN that is prohibited from access. Typically, when a terminal device is denied access to a PLMN, it will be added to this list.

[0070] 2) Network sharing.

[0071] Network sharing refers to the sharing of network facilities between two or more operators. The aim is to reduce network construction costs and lower network operating expenses. Currently, network sharing is gaining increasing acceptance among operators. Network sharing can be categorized by scope, including site sharing, access network equipment sharing, transmission sharing, RNC sharing, and / or core network sharing, or even sharing the entire network. The cost savings vary depending on the level of network sharing. Since site sharing and access network equipment account for the majority of network construction and maintenance costs, sharing site sharing and / or access network equipment offers the highest potential for cost savings and is arguably the most effective sharing model. Through network sharing, operators can free up resources to focus on network coverage optimization, concentrate more on user experience, provide more competitive service capabilities, and reduce energy consumption and avoid redundant site construction, thus meeting energy conservation and emission reduction requirements.

[0072] The 3GPP working group is discussing In-Service Network (INS), in which different operators (OPs) can share access network equipment. Referring to the INS diagram in Figure 1, OP1, as the hosting operator, can share access network equipment with participating operators, such as OP2, OP3, and OP4 in Figure 1. The hosting operator can also be called a shared network operator, and the shared access network equipment can be called shared access network equipment or shared radio access network (shared RAN) equipment. This shared access network equipment only has an N2 / N3 interface with OP1's core network (CN). That is, the shared access network equipment does not need to introduce an N2 / N3 interface with the participating operator. The shared access network equipment is only managed by its parent OP1. Thus, all data traffic passes through OP1's CN. Interoperability interfaces can be introduced between OP1 and other OPs (such as OP2, OP3, etc.), allowing data traffic to pass through OP1's CN and be transmitted to the CNs of other OPs via these interfaces. In other words, communication between the shared access network equipment and the core network of the participating operator is routed through the core network of the hosting operator connected to the shared access network equipment.

[0073] To ensure that OP2 terminal devices (whose HPLMN is OP2, with terminal device 2 as an example in Figure 1) can access the shared access network devices, the shared access network devices can broadcast the PLMN ID of the OP2 PLMN, such as the terminal device's HPLMN ID and / or EHPLMN ID. Taking the broadcast EHPLMN ID as an example, this EHPLMN ID cannot be derived from the terminal device's Subscription Permanent Identifier (SUPI). When selecting network access, OP2 terminal devices can use the EHPLMN ID to select the EHPLMN for network access. The hosting operator's access and mobility management function (AMF) network element can determine whether the terminal device is accessing from another network based on the PLMN ID selected by the terminal device (i.e., the terminal device's EHPLMN ID) (because the EHPLMN ID is different from the PLMN ID to which the AMF network element belongs); a roaming architecture is used between the hosting operator and the participating operator.

[0074] When the shared access network device broadcasts the EHPLMN ID of a terminal device, and OP2's terminal device is within the coverage of the shared access network device, since OP2's terminal device cannot find the HPLMN network, it can determine that the PLMN ID broadcast by the shared access network device is an EHPLMN ID and access the network. At this time, the terminal device will assume that the current network is a regular EHPLMN network and will not be aware of the PLMN of the hosting operator OP1.

[0075] 3) Terminal equipment policy, also known as user equipment (UE) policy, or simply policy, is a policy provided by the policy control function (PCF) network element to the terminal equipment (which can also be UE) via the AMF network element. It can include access network discovery and selection policy (ANDSP), UE route selection policy (URSP), vehicle to X (V2X) policy (V2XP), proximity based services (ProSe) policy (ProSeP), etc.

[0076] 4) URSP.

[0077] 5G introduced URSP, where the terminal device acts as the executor of URSP, selecting a suitable Protocol Data Unit (PDU) session for uplink traffic. The PDU session established by the terminal device has attributes such as network slice, data network name (DNN), and session service continuity (SSC) mode. 3GPP defines URSP to determine the correspondence between applications (APPs) and slices, DNNs, and SSC modes.

[0078] A URSP can include one or more URSP rules. A URSP rule mainly consists of two parts: a traffic descriptor and a route selection descriptor (RSD). The traffic descriptor includes the names or identifiers of multiple applications, etc., while the route selection descriptor includes network slice selection information for each application, as well as wildcard network slice selection information (i.e., network slice selection information that can be used by applications not included in the traffic descriptor), etc.

[0079] The distribution path of URSP is: PCF network element -> AMF network element -> terminal equipment.

[0080] URSP Execution: Taking the UE as an example, the UE may trigger the establishment or modification of a PDU session. For instance, if no suitable PDU session exists, the UE will initiate the PDU session establishment process; if a suitable session exists, it may directly use an existing PDU session. Upon detecting a new application, the UE evaluates whether the application matches the traffic descriptor in the rule according to the order of URSP rules indicated by the rule precedence. If it matches, the UE selects the RSD in the rule according to the order of RSDs indicated by the routing descriptor precedence in the URSP.

[0081] Taking the UE as an example, referring to the URSP generation and distribution diagram in Figure 2, in roaming scenarios, the network side can distribute VPLMN-specific URSPs (also known as VPLMN-specific URSPs) to the UE. This is because the VPLMN may temporarily deploy some applications that the HPLMN is unaware of. Therefore, it needs to visit the PCF (visited PCF, V-PCF) network element to provide some auxiliary UE policy information (such as DNN, SSC mode, and slice information of applications deployed in the VPLMN) to help the home PCF (home PCF, H-PCF) network element determine a suitable URSP for the roaming UE. After the H-PCF network element determines the VPLMN-specific URSP for the roaming UE, it can distribute the VPLMN-specific URSP to the UE. This VPLMN-specific URSP can be indexed by the VPLMN ID. The UE prioritizes using the VPLMN-specific URSP when roaming in the VPLMN (e.g., when the UE roams to the VPLMN).

[0082] When H-PCF network elements issue URSPs, they include the corresponding policy section identifier (PSI) to group the URSPs. They also include the corresponding PLMN ID to identify which PLMN the URSP corresponding to the PSI should be used in. The location region contained in a VPLMN-specific URSP is the VPLMN's location region.

[0083] 5) Wireless Local Area Network (WLAN) Selection Policy (WLANSP).

[0084] WLANSP is a part of ANDSP, and its priority varies in different PLMNs. For terminal devices, WLANSPs issued by the VPLMN have a higher priority than those issued by the HPLMN because the VPLMN is more aware of its own WLAN deployment. Taking the UE as an example, refer to Figure 3 for the WLANSP issuance and usage diagram. In roaming scenarios, both the VPLMN and HPLMN (specifically, the V-PCF network element and the H-PCF network element) will issue WLANSPs to the UE. The UE will prioritize the WLANSPs of the currently serving PLMN (i.e., the VPLMN) and use them accordingly.

[0085] A WLANSP may contain information such as validity conditions, one or more WLAN selection criteria, and additional attributes.

[0086] Validity conditions are the conditions that indicate when a provided rule is valid. Validity conditions can include time of day, geographic location, network location (e.g., PLMN, location region), etc.

[0087] One or more WLAN selection criteria, arranged in order of priority. Each group contains one or more conditions that a WLAN access network must meet to be eligible for selection.

[0088] Additional attributes:

[0089] Service set identifier (SSID) list: A list of preferred SSIDs.

[0090] Home network: When home network is set in a set of selection criteria, it means that this set of selection criteria only applies to WLAN access networks that directly interconnect with the home operator. When home network is not set or is not in a set of selection criteria, it means that this set of selection criteria applies to all WLAN access networks.

[0091] 6) Sending / receiving information. In this application, "sending information" can be understood as one device sending information to another device, or it can also be understood as one logic module within a device sending information to another logic module. For example, "device A sending information" can be understood as device A sending information to another device (device B), or it can be understood as logic module 1 in device A sending information to logic module 2 in device A.

[0092] In this application, "receiving information" can be understood as one device receiving information from another device, or it can also be understood as a logical module within a device receiving information from another logical module. For example, "device A receives information" can be understood as device A receiving information from another device (such as device B), or it can be understood as logical module 1 in device A receiving information from logical module 2 in device A.

[0093] In this application, the phrase "sending information to... (e.g., device B)" or the related illustrations in the accompanying drawings can be understood as the destination of the information being device B. This can include sending information directly or indirectly to device B. Similarly, the phrase "receiving information from... (e.g., device A)," "receiving information from... (e.g., device A)," or "receiving information sent by (e.g., device A)," or the related illustrations in the accompanying drawings, can be understood as the source of the information being device A. This can include receiving information directly or indirectly from device A. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly, and will not be elaborated further here.

[0094] As described above, when a terminal device accesses another participating operator's PLMN via a shared access network device (INS scenario), because the terminal device is registered with the PLMN of another participating operator, it is unaware of the managed operator's PLMN and therefore will not use the corresponding managed operator's PLMN policy issued by the network. Since communication between the shared access network device and the participating operator's core network is routed through the managed operator's core network, the network side can detect the terminal device's access to the managed operator's PLMN and will assume the terminal device is using the corresponding managed operator's PLMN policy. This leads to a discrepancy between the terminal device's and the network side's understanding of the policy used by the terminal device. This may result in the terminal device making incorrect routing choices and / or selecting the wrong Wi-Fi network. It may also cause the network side to continuously issue policy updates for the corresponding managed operator's PLMN to the terminal device, which the terminal device cannot use, resulting in a waste of signaling and other resources.

[0095] Based on this, embodiments of this application provide a policy configuration method and apparatus to align the understanding of terminal device policies used by the terminal device on the terminal device side and the network side. The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0096] The embodiments of this application can be applied to 5G system architecture, as well as other system architectures, such as future communication system architectures. This application does not limit them. The following description uses 5G system architecture as an example.

[0097] The 5G system architecture further includes both 5G non-roaming and 5G roaming architectures. Within a 5G system, both service-oriented and reference-point-based architectures can be used.

[0098] Figure 4A shows a 5G non-roaming system architecture based on service-oriented interfaces, and Figure 4B shows a 5G non-roaming system architecture based on reference points.

[0099] There are two main networking methods for 5G core network roaming: home routed (HR) and local breakout (LBO).

[0100] The local roaming scheme is shown in Figures 5A and 5B. User plane service flows access the data network through the roaming user plane functional network elements, without requiring assistance from the home network. The local roaming scheme has the advantage of a short user plane data transmission path. Figure 5A shows the 5G roaming system architecture based on service-oriented interfaces under the local roaming scheme, and Figure 5B shows the 5G roaming system architecture based on reference points under the local roaming scheme.

[0101] The home-location routing scheme is shown in Figures 6A and 6B. User plane service flows return to the home user plane functional network element to access the data network. Figure 6A shows the 5G roaming system architecture based on service-oriented interfaces under the home-location routing scheme, and Figure 6B shows the 5G roaming system architecture based on reference points under the home-location routing scheme.

[0102] Adding "V", "v", or "V-" before a network element has the same meaning: it indicates that the element belongs to a VPLMN. For example, a V-PCF network element or a vPCF network element indicates a PCF network element in a VPLMN. Similarly, adding "H", "h", or "H-" before a network element has the same meaning: it indicates that the element belongs to an HPLMN. For example, an H-PCF network element or an hPCF network element indicates a PCF network element in an HPLMN. In other words, "V" or "H" only describes the network or location and does not imply any functional limitation. For example, a V-PCF network element and an H-PCF network element may have the same or different functions.

[0103] Figure 7 is a schematic diagram of an indirect network sharing architecture provided in an embodiment of this application. Referring to Figure 7, operator X acts as the hosting operator, while operators A, B, and C can act as participating operators. Operator X's shared access network equipment (which can be shared base stations, shared access points, etc.) can be shared with operators A, B, and C. Operator X's 5G core network (5GC) can have one or more interfaces such as N8, N9, N12, or N16 with the 5GCs of operators A, B, and C. Uplink traffic from the terminal devices of participating operators can be transmitted to their corresponding participating operator's 5GC via the hosting operator X's 5GC, and downlink traffic can also be sent from their corresponding participating operator's 5GC to the terminal devices via the hosting operator X's 5GC. From a service flow perspective, the indirect network sharing architecture is similar to a home-location routing architecture.

[0104] A 5G system includes terminal equipment (e.g., user equipment (UE)), operator networks, and data networks (DN). The operator network may include an access network and a core network (CN).

[0105] Terminal equipment can be a UE, handheld terminal, laptop computer, subscriber unit, cellular phone, smartphone, wireless data card, personal digital assistant (PDA) computer, tablet computer, wireless modem, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, machine type communication (MTC) terminal, or other devices that can access the network.

[0106] Access network equipment: This refers to equipment that provides access for terminal devices, including access network (AN) equipment and RAN equipment. RAN equipment: Primarily 3GPP network wireless network equipment, while AN equipment can be access network equipment not defined by 3GPP. RAN equipment is mainly responsible for functions such as radio resource management, quality of service (QoS) management, data compression, and encryption on the air interface side. RAN equipment can include various forms of base stations, such as macro base stations, micro base stations (also known as small stations), relay stations, and access points. In systems employing different wireless access technologies, the names of equipment with base station functions may differ. For example, in 5G systems, it is called RAN or next-generation NodeB (gNB), or 5G NodeB; in Long Term Evolution (LTE) systems, it is called evolved NodeB (eNB or eNodeB); and in 3rd generation (3G) systems, it is called Node B, etc.

[0107] AN equipment: This equipment allows terminal equipment and the 3GPP core network to interconnect using non-3GPP technologies, such as wireless fidelity (Wi-Fi), worldwide interoperability for microwave access (WiMAX), and code division multiple access (CDMA) networks.

[0108] The core network user plane includes user plane functions (UPF); the core network control plane includes access and mobility management function (AMF) network elements, session management function (SMF) network elements, network exposure function (NEF) network elements, network function repository function (NRF) network elements, unified data management (UDM) network elements, policy control function (PCF) network elements, application function (AF) network elements, network slice admission control function (NSACF) network elements, etc.

[0109] Among them, the AMF network element is mainly responsible for mobility management in the mobile network, such as user location updates, user registration with the network, and user handover.

[0110] SMF network elements are primarily responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to users and selecting UPF network elements that provide packet forwarding capabilities.

[0111] UPF network elements are responsible for forwarding and receiving user data in terminal devices. They can receive user data from the data network and transmit it to the terminal device through the access network equipment; UPF network elements can also receive user data from the terminal device through the access network equipment and forward it to the data network. The transmission resources and scheduling functions that provide services to the terminal device in the UPF network element are managed and controlled by the SMF network element.

[0112] PCF network element: It mainly supports providing a unified policy framework to control network behavior, provides policy rules to the control layer network functions, and is also responsible for obtaining user subscription information related to policy decisions.

[0113] NEF network elements: primarily used to support the opening of capabilities and events.

[0114] NSACF network elements: support monitoring and controlling the number of registered users in each network slice, support monitoring and controlling the number of PDU sessions established in each network slice, support event-based network slice status notifications and reporting to other network functions (NFs).

[0115] AF network element: mainly supports interaction with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing some third-party services to the network side.

[0116] UDM network elements are used to generate authentication credentials, process user identification information (such as storing and managing permanent user identities), control access authorization, and manage subscription data.

[0117] DN: Refers to the service network that provides data transmission services to users, such as IP multimedia service (IMS) and the Internet. The UE accesses the DN through a PDU session established between the UE and the DN.

[0118] It is understood that the core network may also include other network elements, and this application does not limit this. It should be understood that the network architectures shown in Figures 5A, 5B, 5A, 5B, 6A, and 6B can be applied to the embodiments of this application. Furthermore, the network architectures applicable to the embodiments of this application are not limited thereto, and any network architecture capable of implementing the functions of the above-mentioned network elements can be applied to the embodiments of this application.

[0119] It should also be understood that the interface names between the various network elements in the above diagram are merely examples. In actual implementations, the interface names may differ, and this application does not impose any specific limitations on them. The naming of the network elements is solely for distinguishing different functions and should not constitute any limitation on this application. This application does not exclude the possibility of using other names in 5G networks and other future networks, and the above naming does not mean that these network elements are independent physical devices. This application does not limit the specific form of the above functional entities; for example, they can be integrated into the same physical device or they can be different physical devices. Furthermore, they can be combined into network slices as needed.

[0120] It should be noted that the aforementioned "network element" can also be referred to as a functional entity, entity, device, apparatus, or module, etc., and this application does not specifically limit it.

[0121] Additionally, it should be understood that the ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the size, content, order, timing, priority, or importance of the multiple objects. For example, "first strategy" and "second strategy" do not indicate a difference in priority or importance between the two strategies.

[0122] In this application embodiment, the number of nouns, unless otherwise specified, refers to "singular nouns or plural nouns," that is, "one or more." "At least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. For example, A / B means: A or B. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c means: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

[0123] In the embodiments of this application, the access and mobility management function network element involved can be the aforementioned AMF network element, or it can be a network element in other communication systems (such as future communication systems) that has the aforementioned AMF network element function; the policy control function network element can be the aforementioned PCF network element, or it can be a network element in other communication systems (such as future communication systems) that has the aforementioned PCF network element function. For ease of explanation, in the embodiments of this application, the access and mobility management function network element is an AMF network element and the policy control function network element is a PCF network element as an example. In addition, in the embodiments of this application, managed PCF refers to the PCF network element of managed PLMN (or the PCF network element in managed PLMN), managed AMF network element refers to the AMF network element of managed PLMN (or the AMF network element in managed PLMN), and H-PCF network element refers to the PCF network element of HPLMN of the terminal device (or the PCF network element in HPLMN of the terminal device).

[0124] Figure 8 is a schematic diagram of one of the policy configuration methods provided in the embodiments of this application. The method includes:

[0125] S801: The managed AMF network element obtains the first policy of the managed PLMN for the terminal device. The first policy carries the managed PLMN identifier.

[0126] In the INS scenario, the managed operator can share its shared access network equipment with the participating operator. The shared access network equipment can broadcast not only the managed PLMN identifier (such as PLMN ID) of the managed PLMN of the managed operator, but also the participating PLMN identifier of the participating operator. The terminal device can use the shared access network equipment as the access network equipment of the participating operator's participating PLMN and access the participating PLMN through the shared access network equipment.

[0127] As an example: A terminal device is a subscriber of operator B. Operator A (as the hosting operator) can share its managed PLMN's shared access network equipment with operator B (as the participating operator)'s participating PLMN. The participating PLMN can be the terminal device's HPLMN or EHPLMN. The shared access network equipment of the managed PLMN can broadcast the managed PLMN identifier (e.g., managed PLMN ID) and the participating PLMN identifier (e.g., participating PLMN ID). When the terminal device loses network coverage due to movement or restarts, it needs to search for a PLMN. If the terminal device is within the coverage area of ​​the shared access network equipment, it can receive the managed PLMN identifier and the participating PLMN identifier broadcast by the shared access network equipment. The participating PLMN corresponding to the participating PLMN identifier is either the terminal device's HPLMN or EHPLMN. For the terminal device, the selection priority of HPLMN or EHPLMN is usually higher than the selection priority of other PLMNs; that is, the selection priority of the participating PLMN is usually higher than the selection priority of the managed PLMN. The terminal device can choose to initiate access from the participating PLMN.

[0128] It should be noted that the above description uses the example of sharing the managed PLMN access network equipment with the terminal device's HPLMN or EHPLMN. It is understood that the managed PLMN access network equipment can also be shared with the terminal device's HPLMN and EHPLMN. The managed PLMN access network equipment can also broadcast the managed PLMN identifier, the HPLMN's PLMN identifier, and / or the EHPLMN's PLMN identifier. When selecting a PLMN, the terminal device can select either the HPLMN or EHPLMN to initiate access based on the priority configuration of its own PLMN.

[0129] After a terminal device selects to participate in a PLMN, it can send a registration message to the managed AMF network element through the shared access network equipment. This registration message can carry the PLMN identifier of the selected (or registered) PLMN, as well as the terminal device's identification information (such as SUPI or Subscription Concealed Identifier, SUCI). Upon receiving the registration message, the managed AMF network element can obtain the managed PLMN's first policy for the terminal device from the managed PCF network element and / or the terminal device's H-PCF network element. For the H-PCF network element, the managed AMF network element can be determined based on the PLMN identifier carried in the terminal device's identification information (this PLMN identifier is the HPLMN identifier of the terminal device's HPLMN). The H-PCF network element is the PCF network element of the PLMN identified by this PLMN identifier.

[0130] In one possible implementation, the first strategy may include one or more of ANDSP, URSP, V2XP, or proximity service strategy, wherein ANDSP may include WLANSP.

[0131] Taking URSP (denoted as URSP#1) as the first policy, the managed AMF network element can send a policy association establishment request to the managed PCF network element. This request can carry the terminal device's identification information to establish a policy association for the terminal device. Upon receiving this request, the managed PCF network element can send it to the terminal device's H-PCF network element. Upon receiving the request, the H-PCF network element can determine the managed PLMN's URSP#1 for the terminal device. The H-PCF network element can determine URSP#1 based on the auxiliary UE policy information corresponding to the managed PLMN (such as the DNN, SSC mode, or slice information of the application deployed on the managed PLMN). URSP#1 carries the managed PLMN identifier. The auxiliary UE policy information corresponding to the managed PLMN can come from the managed PCF network element and be sent to the H-PCF network element.

[0132] After determining the URSP#1 of the corresponding managed PLMN, the H-PCF network element can send URSP#1 to the managed AMF network element via the managed PCF network element. For example, the H-PCF network element can send a terminal device policy notification (or terminal device policy update notification) including URSP#1 to the managed PCF network element. This terminal device policy notification (or terminal device policy update notification) may also include the terminal device's identification information. After receiving the terminal device policy notification, the managed PCF network element can send it to the managed AMF network element.

[0133] Taking WLANSP (denoted as WLANSP#1) as an example, the managed AMF network element can send a policy association establishment request to the managed PCF network element. This request can carry the terminal device's identification information to establish a policy association for the terminal device. Upon receiving this request, the managed PCF network element can determine the managed PLMN's WLANSP#1. The managed PCF network element can determine the managed PLMN's WLANSP#1 for the terminal device based on one or more of the managed PLMN's SSID, validity conditions, and one or more sets of WLAN selection standard configurations. WLANSP#1 carries the managed PLMN's identifier. After determining the managed PLMN's WLANSP#1, the managed PCF network element can send WLANSP#1 to the managed AMF network element, for example, through a terminal device policy notification (or terminal device policy update notification) including WLANSP#1.

[0134] S802: The managed AMF network element, based on the determined terminal device being in an INS scenario, deletes the managed PLMN identifier carried by the first policy, or replaces the managed PLMN identifier carried by the first policy with the participating PLMN identifier registered by the terminal device, to obtain the second policy.

[0135] After a terminal device initiates access through a shared access network device, such as sending a registration message to a managed AMF network element through the shared access network device, the managed AMF network element can determine whether the terminal device is in an INS scenario.

[0136] In one possible implementation, to determine whether a terminal device is in an INS scenario, the managed AMF network element can determine this by comparing the PLMN identifier carried in the terminal device's identification information with the managed PLMN identifier.

[0137] As an example: The PLMN identifier carried in the terminal device's identification information (such as SUPI or SUCI) is the terminal device's HPLMN identifier. If the PLMN identifier carried in the terminal device's identification information is different from the managed PLMN identifier, the managed AMF network element can determine that the terminal device is in an INS scenario. If the PLMN identifier carried in the terminal device's identification information is the same as the managed PLMN identifier, the managed AMF network element can determine that the managed PLMN is the terminal device's home PLMN, and the terminal device is in a non-INS scenario.

[0138] In some embodiments, if the PLMN identifier carried in the identification information of the terminal device is different from the managed PLMN identifier, the terminal device can further determine whether the PLMN identifier of the PLMN registered by the terminal device (which can be obtained by the PLMN identifier of the PLMN registered by the terminal device carried in the registration message sent by the terminal device) belongs to the participating PLMN identifier other than the managed PLMN identifier broadcast by the shared access network device of the managed PLMN. If it is a managed AMF network element, it can also be determined that the terminal device is in an INS scenario; otherwise, the managed AMF network element can determine that the terminal device is in a non-INS scenario.

[0139] Of course, the managed AMF network element can also directly determine whether the PLMN identifier of the PLMN registered (or selected) by the terminal device (which can be obtained from the PLMN identifier of the PLMN registered by the terminal device carried in the terminal device registration message, etc.) belongs to the participating PLMN identifier broadcast by the shared access network device of the managed PLMN other than the managed PLMN identifier. If so, the managed AMF network element can determine that the terminal device is in an INS scenario; otherwise, the managed AMF network element can determine that the terminal device is in a non-INS scenario.

[0140] It should be noted that the determination of whether the terminal device is in the INS scenario by the managed AMF network element can occur before the managed AMF network element obtains the first policy (i.e., step S801 above), or after the managed AMF network element obtains the first policy (i.e., step S801 above), or it can occur simultaneously with the managed AMF network element obtaining the first policy (i.e., step S801 above). This application does not limit this.

[0141] Because communication between the shared access network device and the core network of the participating PLMN is routed through the core network of the managed PLMN connected to the shared access network device, if a terminal device registers with a participating PLMN through the shared access network device, the managed PLMN to which the shared access network device belongs is the terminal device's VPLMN. However, since the terminal device is registered with a participating PLMN, it is unaware of the managed PLMN. Therefore, if the managed AMF network element determines that the terminal device is in an INS scenario, the managed AMF network element can delete the managed PLMN identifier carried in the first policy of the managed PLMN, or replace the managed PLMN identifier carried in the first policy with the participating PLMN identifier of the participating PLMN registered by the terminal device, thus obtaining a second policy. This second policy disguises the first policy as the policy of the terminal device's home PLMN or the policy of the registered participating PLMN, so that the terminal device can use this policy.

[0142] As an example: taking the first device policy as URSP#1 and the second policy as URSP#2, if the participating PLMN registered (or selected) by the terminal device is the terminal device's EHPLMN, the managed AMF network element can replace the managed PLMN identifier in URSP#1 with the participating PLMN identifier to obtain URSP#2; if the participating PLMN is the terminal device's HPLMN, since the URSP of the corresponding HPLMN usually does not carry the PLMN identifier, the managed AMF network element can delete the managed PLMN identifier in URSP#1 to obtain URSP#2.

[0143] Taking WLANSP#1 as the first strategy and WLANSP#2 as the second strategy as an example, since WLANSPs, whether corresponding to HPLMNs or other PLMNs, usually carry PLMN identifiers, regardless of whether the participating PLMN is the EHPLMN or HPLMN of the terminal device, the managed AMF network element can replace the managed PLMN identifier in WLANSP#1 (such as the managed PLMN identifier in the validity conditions of WLANSP#1) with the participating PLMN identifier to obtain WLANSP#2.

[0144] In the case of the terminal device being in the INS scenario, the hosting AMF network element can use one or more of the following methods to determine whether the participating PLMN is the EHPLMN of the terminal device.

[0145] Method A1: The managed AMF network element determines whether the participating PLMN is the EHPLMN of the terminal equipment based on the service level agreement (SLA) or network configuration between the managed PLMN and the participating PLMN. The SLA is a contract or agreement signed between the service provider (e.g., the managed PLMN or its operator) and the user (e.g., the participating PLMN or its operator), which regulates their business relationship or parts thereof.

[0146] As an example: The access network equipment of the managed PLMN is shared with the participating PLMN. The SLA or network configuration between the managed PLMN and the participating PLMN may include the participating PLMN identifier and the EPLMN identifier of the participating PLMN's EPLMN.

[0147] The shared access network equipment broadcasts the participating PLMN identifier. The terminal equipment selects to participate in the PLMN and initiates access. If the HPLMN identifier carried by the terminal equipment's identity identifier (such as SUPI or SUCI) is the EPLMN identifier of the participating PLMN, then the managed AMF network element can determine that the participating PLMN is the terminal equipment's EHPLMN. Otherwise, the managed AMF network element can determine that the participating PLMN is not the terminal equipment's EHPLMN.

[0148] Method A2: The managed AMF network element determines whether the participating PLMN is the EHPLMN of the terminal device by judging whether the participating PLMN initiated by the terminal device is the EPLMN of the terminal device's HPLMMN.

[0149] As an example: The managed AMF network element can obtain the PLMN identifier carried in the identity identifier of the terminal device. If the participating PLMN identifier is different from the PLMN identifier carried in the identity identifier of the terminal device, the managed AMF network element can determine the EPLMN of the HPLMN registered by the terminal device. Regardless of whether the participating PLMN is the EHPLMN of the terminal device, the managed AMF network element can process the participating PLMN as the EHPLMN of the terminal device. For example, the managed PLMN identifier in the first policy can be replaced with the participating PLMN identifier to obtain the second terminal device policy.

[0150] Method A3: The managed AMF network element determines whether the participating PLMN is the terminal device's EHPLMN based on the EHPLMN identifier list reported by the terminal device.

[0151] As an example: a terminal device can report its own EHPLMN identifier list to the hosting AMF network element. The EHPLMN identifier list may include the EHPLMN identifiers of one or more EHPLMNs of the terminal device. If the participating PLMN identifier belongs to the EHPLMN identifier list, the hosting AMF network element can determine that the participating PLMN is the terminal device's EHPLMN. Otherwise, the hosting AMF network element can determine that the participating PLMN is not the terminal device's EHPLMN.

[0152] In addition, to determine whether the participating PLMN is the HPLMN of the terminal device, the hosting AMF network element can obtain the PLMN identifier (i.e., the HPLMN identifier of the terminal device) carried in the terminal device's identification information (such as SUPI or SUCI). If the participating PLMN identifier is the same as the PLMN identifier carried in the terminal device's identity identifier, the hosting AMF network element can determine that the participating PLMN is the HPLMN of the terminal device.

[0153] S803: The managed AMF network element sends the second policy to the terminal device, and the terminal device receives the second policy accordingly.

[0154] Upon receiving the second policy, the managed AMF network element sends it to the terminal device. Since the second policy either does not carry the managed PLMN identifier (a policy without a PLMN identifier defaults to the corresponding HPLMN's policy) or carries the participating PLMN identifier registered by the terminal device, the terminal device can use the second policy.

[0155] In some embodiments, if the participating PLMN is the HPLMN of the terminal device, the managed PLMN identifier carried in the first policy is deleted or replaced with the participating PLMN identifier. After obtaining the second policy, the managed AMF network element can also set the rule priority carried in the second policy to be higher than the rule priority carried in the third policy of the HPLMN for the terminal device. In this way, when both the second policy and the corresponding third policy of the HPLMN are issued to the terminal device, the terminal device will use the second policy because the rule priority of the second policy is higher.

[0156] Taking URSP#1 as the first strategy, URSP#2 as the second strategy, and URSP#3 as the third strategy as an example, if the participating PLMN is the HPLMN of the terminal device, the managed AMF network element can delete the managed PLMN identifier in URSP#1 to obtain URSP#2, and set the rule precedence in URSP#2 to be higher than the rule precedence in URSP#3. Thus, if both URSP#2 and URSP#3 are issued to the terminal device, the terminal device will use URSP#2 because the rule precedence in URSP#2 is higher than that in URSP#3. URSP#3 can be sent to the terminal device by the H-PCF network element of the terminal device via the managed PCF and managed AMF network elements.

[0157] In some embodiments, if the policy (such as the first policy) is URSP, for URSP#1, the H-PCF network element will send URSPs with the corresponding PSI for URSP grouping. The PSI is associated with the PLMN identifier of the PLMN applied by the URSP. For example, for URSP#1 (i.e., the first policy), PSI#1 will be carried, and for URSP#3 (i.e., the third policy), PSI#3 will be carried. PSI#1 is associated with the managed PLMN identifier of the managed PLMN applied by URSP#1, and PSI#3 is associated with the HPLMN identifier of the terminal device applied by URSP#3.

[0158] In cases such as initial registration of terminal devices (e.g., re-registration after network loss or power-on after shutdown); or when a terminal device moves from an evolved packet system (EPS) to 5GS and there is no existing terminal device policy association between the managed AMF network element and the H-PCF network element; or when the value of the terminal device policy association indicator received by the terminal device from the UDM network element changes from "disabled" to "enabled", the terminal device can report the PSI and PLMN identifiers corresponding to the second policy it is using. Since the managed AMF network element replaces or deletes the managed PLMN identifier in the first policy with the participating PLMN identifier, it disguises the first policy as the second policy corresponding to the participating PLMN identifier. The terminal device reports the PSI and PLMN identifiers corresponding to the stored second policy, but what is actually reported is the PSI and participating PLMN identifiers corresponding to the first policy. Therefore, if the managed AMF network element receives the first information from the terminal device, including the PSI and the participating PLMN identifier, the managed AMF network element can replace the participating PLMN identifier back with the managed PLMN identifier and send the second information, including the PSI and the managed PLMN identifier, to the H-PCF network element of the terminal device, so that the H-PCF network element of the terminal device can correctly know that the PSI corresponds to the managed PLMN identifier (or managed PLMN).

[0159] Figure 8 above illustrates the policy configuration method using a managed AMF network element as the execution subject. It can be understood that the execution subject in Figure 8 could also be a managed PCF network element. Alternatively, the managed PCF network element could obtain the first policy from the managed PLMN for the terminal device. If the terminal device is determined to be in an INS scenario, the first policy could be disguised as a second policy registered by the terminal device with the participating PLMN for the terminal device, allowing the terminal device to use the managed PLMN's policy for the terminal device. The policy configuration method shown in Figure 9 will be explained below.

[0160] Figure 9 is a second schematic diagram of a strategy configuration method provided in an embodiment of this application. The method includes:

[0161] S901: The terminal device sends a registration request to the managed AMF network element, and the managed AMF network element receives the registration request from the terminal device accordingly.

[0162] In an INS (Instrument Service) scenario, the shared access network device hosting the PLMN can broadcast the PLMN identifier for participating devices. If a terminal device loses network access (this could mean the terminal device has lost its network connection, the network connection is interrupted and it cannot access the internet, or it is not registered on the cell), or needs to search for a PLMN after being powered off and restarted, and if the terminal device is within the coverage area of ​​the shared access network device, it can choose to participate in the PLMN to initiate access.

[0163] After a terminal device selects to participate in a PLMN, it can send a registration message (such as a registration request) to the managed AMF network element through the shared access network device. The registration message can carry the PLMN identifier of the registered (or selected) PLMN participant, as well as the terminal device's identification information (such as SUPI or SUCI).

[0164] S902: The managed AMF network element sends a policy association establishment request to the managed PCF network element, and the managed PCF network element receives the policy association establishment request accordingly.

[0165] Upon receiving a registration message from a terminal device, the managed AMF network element can decide to establish a policy association for the terminal device. This is possible in cases such as initial user registration or when there is no existing policy association between the managed AMF network element and the terminal device's H-PCF network element. For H-PCF network elements, the managed AMF network element can be determined based on the PLMN identifier carried in the terminal device's identification information (this PLMN identifier is the HPLMN identifier of the terminal device's HPLMN). The H-PCF network element is the PCF network element of the PLMN identified by this PLMN identifier.

[0166] If the managed AMF network element decides to establish a policy association for the terminal device, the managed AMF network element can send a policy association establishment request to the managed PCF network element. The policy association establishment request carries the identification information of the terminal device and is used to establish a policy association for the terminal device.

[0167] In one possible implementation, after receiving a registration request from a terminal device, the managed AMF network element can also determine whether the terminal device is in an INS scenario. If it is determined that the terminal device is in an INS scenario, the managed AMF network element can also send a first indication message to the managed PCF network element. The first indication message can indicate that the terminal device is in an INS scenario or indicate that the terminal device has not registered with the managed PLMN. Upon receiving the first indication message, the managed PCF network element can determine that the terminal device is in an INS scenario.

[0168] Furthermore, the managed AMF network element can also determine whether the participating PLMN registered by the terminal device is the terminal device's HPLMN or EHPLMN (i.e., whether the PLMN identifier registered by the terminal device is the terminal device's HPLMN identifier or EHPLMN identifier). The managed AMF network element can also send a second indication message to the managed PCF network element, which can indicate whether the participating PLMN registered by the terminal device is the terminal device's HPLMN or EHPLMN. It is understood that the first and second indication messages can be sent via different messages or via the same message; this application does not limit this. For example, the first and second indication messages can be carried in a policy association establishment request and sent by the managed AMF network element to the managed PCF network element.

[0169] The process of the managed AMF network element determining whether the terminal device is in an INS scenario and whether the participating PLMN registered by the terminal device is the terminal device's HPLMMN or EHPLMN can be referred to in step S802 and will not be repeated here.

[0170] In one possible implementation, the policy association establishment request may also carry the participating PLMN identifier registered (or selected) by the terminal device, or, if the managed PLMN shares an access network device with only one participating PLMN, it may carry the participating PLMN identifier broadcast by the shared access network device (in the case of the terminal device being registered to the PLMN in an INS scenario), so that the managed PCF network element can know the participating PLMN information registered by the terminal device.

[0171] S903: The managed PCF network element sends a policy association establishment request to the H-PCF network element, and the H-PCF network element receives the policy association establishment request accordingly.

[0172] When a managed PCF network element receives a policy association establishment request from a managed AMF network element, it can send this request to the H-PCF network element of the terminal device to establish a policy (such as URSP) association for the terminal device. The managed PCF network element can be identified based on the PLMN identifier carried in the terminal device's identification information (this PLMN identifier is the HPLMN identifier of the terminal device's HPLMN). The H-PCF network element is the PCF network element of the PLMN identified by this PLMN identifier.

[0173] In some embodiments, after receiving a policy association establishment request, the H-PCF network element can send a terminal device policy association establishment response to the managed PCF network element, informing the H-PCF network element that it has received the policy association establishment request. The managed PCF network element can then send the terminal device policy association establishment response to the managed AMF network element.

[0174] S904: The H-PCF network element sends the first policy of the managed PLMN for the terminal device to the managed PCF network element, and the managed PCF network element receives the first policy accordingly.

[0175] After receiving the policy association establishment request, the H-PCF network element can determine the first policy of the managed PLMN for the terminal device.

[0176] Taking URSP (represented by URSP#1) as an example, after the H-PCF network element receives a policy association establishment request from the managed PCF network element, it can determine URSP#1 based on the auxiliary UE policy information corresponding to the managed PLMN (such as the DNN, SSC mode, or slice information of the application deployed on the managed PLMN). URSP#1 carries the managed PLMN identifier. The auxiliary UE policy information corresponding to the managed PLMN can come from the managed PCF network element and be sent by the managed PCF network element to the H-PCF network element.

[0177] After determining the first policy of the managed PLMN for the terminal device, the H-PCF network element can send the first policy to the managed PCF network element. The first policy can be sent to the managed PCF network element through terminal device policy notification (or terminal device policy update notification), etc. This application does not limit the way in which the H-PCF network element can send the first policy to the managed PCF network element.

[0178] S905: Based on the fact that the terminal device is in an INS scenario, the managed PCF network element deletes the managed PLMN identifier carried by the first policy, or replaces the managed PLMN identifier carried by the first policy with the participating PLMN identifier registered by the terminal device, thus obtaining the second policy.

[0179] Whether a terminal device is in an INS scenario can be reported by the managed AMF network element to the managed PCF network element. For example, in step S902 above, if it is determined that the terminal device is in an INS scenario, the managed AMF network element can send a first indication message to the managed PCF network element. The first indication message indicates that the terminal device is in an INS scenario.

[0180] Of course, whether the terminal device is in an INS scenario can also be determined by the managed PCF network element itself.

[0181] As an example: The PLMN identifier carried in the terminal device's identification information (such as SUPI or SUCI) is the HPLMN identifier of the terminal device's HPLMN. If the PLMN identifier carried in the terminal device's identification information is different from the managed PLMN identifier, the managed PCF network element can determine that the terminal device is in an INS scenario. If the PLMN identifier carried in the terminal device's identification information is the same as the managed PLMN identifier, the managed PCF network element can determine that the terminal device is in a non-INS scenario.

[0182] Alternatively, the managed PCF network element can directly determine whether the PLMN identifier of the PLMN registered by the terminal device (which can be obtained from the PLMN identifier of the PLMN registered by the terminal device carried in the terminal device registration message, etc.) belongs to the participating PLMN identifier broadcast by the shared access network device of the managed PLMN other than the managed PLMN identifier. If it is the managed PCF network element, it can determine that the terminal device is in an INS scenario; otherwise, the managed AMF network element can determine that the terminal device is in a non-INS scenario.

[0183] Because communication between the shared access network device and the core network of the participating PLMN is routed through the core network of the managed PLMN connected to the shared access network device, if a terminal device registers with a participating PLMN through the shared access network device, the managed PLMN to which the shared access network device belongs is the terminal device's VPLMN. However, since the terminal device is registered with a participating PLMN, it is unaware of the managed PLMN. Therefore, if the managed PCF network element determines that the terminal device is in an INS scenario, the managed PCF network element can delete the managed PLMN identifier carried in the first policy corresponding to the managed PLMN, or replace the managed PLMN identifier carried in the first policy with the participating PLMN identifier registered by the terminal device, thus obtaining a second policy. This second policy disguises the first policy as a policy of the HPLMN or a participating PLMN, allowing the terminal device to use this policy.

[0184] As an example: taking the first device policy as URSP#1 and the second policy as URSP#2, if the participating PLMN registered (or selected) by the terminal device is the terminal device's EHPLMN, the managed PCF network element can replace the managed PLMN identifier in URSP#1 with the participating PLMN identifier to obtain URSP#2; if the participating PLMN is the terminal device's HPLMN, since the URSP of the corresponding HPLMN usually does not carry the PLMN identifier, the managed PCF network element can delete the managed PLMN identifier in URSP#1 to obtain URSP#2.

[0185] In this scenario, where the terminal device is in an INS environment, the host AMF network element can report whether the participating PLMN registered by the terminal device is the terminal device's HPLMN or EHPLMN to the host PCF network element. For example, in step S902 above, the host AMF network element can send a second indication message to the host PCF network element, indicating whether the participating PLMN registered by the terminal device is the terminal device's HPLMN or EHPLMN. Alternatively, the PCF can determine whether the participating PLMN registered by the terminal device is the terminal device's HPLMN or EHPLMN.

[0186] In the case of the terminal device being in the INS scenario, the hosting PCF network element can use one or more of the following methods to determine whether the participating PLMN is the EHPLMN of the terminal device.

[0187] Method B1: The managed PCF network element determines whether the participating PLMN is the EHPLMN of the terminal device based on the SLA or network configuration between the managed PLMN and the participating PLMN.

[0188] As an example: The access network equipment of the managed PLMN is shared with the participating PLMN. The SLA or network configuration between the managed PLMN and the participating PLMN may include the participating PLMN identifier and the EPLMN identifier of the participating PLMN's EPLMN.

[0189] The shared access network equipment broadcasts the participating PLMN identifier. The terminal equipment selects to participate in the PLMN and initiates access. If the HPLMN identifier of the terminal equipment carried in the terminal equipment's registration message (such as SUPI or SUCI) is the EPLMN identifier of the participating PLMN, then the managed PCF network element can determine that the participating PLMN is the terminal equipment's EHPLMN. Otherwise, the managed PCF network element can determine that the participating PLMN is not the terminal equipment's EHPLMN.

[0190] Method B2: The managed PCF network element determines whether the participating PLMN is the EHPLMN of the terminal device by judging whether the participating PLMN registered by the terminal device is the EPLMN of the terminal device's HPLMMN.

[0191] As an example: The managed PCF network element can obtain the PLMN identifier carried in the identification information of the terminal device. If the participating PLMN identifier is different from the PLMN identifier carried in the identification information of the terminal device, the managed PCF network element can determine the EPLMN of the HPLMN registered by the terminal device. Regardless of whether the participating PLMN is the EHPLMN of the terminal device, the managed PCF network element can process the participating PLMN as the EHPLMN of the terminal device. For example, the managed PLMN identifier in the first strategy can be replaced with the participating PLMN identifier to obtain the second strategy.

[0192] Method B3: The managed PCF network element determines whether the participating PLMN is the terminal device's EHPLMN based on the EHPLMN identifier list reported by the terminal device.

[0193] As an example: a terminal device can report its own EHPLMN identifier list to the managed PCF network element (for example, the EHPLMN identifier list can be reported by the terminal device to the managed PCF network element through the managed AMF network element). The EHPLMN identifier list may include the EHPLMN identifiers of one or more EHPLMNs of the terminal device. If the participating PLMN identifier belongs to the EHPLMN identifier list, the managed PCF network element can determine that the participating PLMN is the terminal device's EHPLMN. Otherwise, the managed PCF network element can determine that the participating PLMN is not the terminal device's EHPLMN.

[0194] To determine whether a participating PLMN is the HPLMN of a terminal device, the hosting PCF network element can obtain the PLMN identifier carried in the terminal device's identification information (i.e., the HPLMN identifier of the terminal device's HPLMN). If the participating PLMN identifier is the same as the PLMN identifier carried in the terminal device's identification information, the hosting PCF network element can determine that the participating PLMN is the HPLMN of the terminal device.

[0195] S906: The managed PCF network element sends the second policy to the managed AMF network element, and the managed AMF network element receives the second policy accordingly.

[0196] After obtaining the second policy, the managed PCF network element can send the second policy to the managed AMF network element. The second policy can be sent to the managed AMF network element through terminal device policy notification (or terminal device policy update notification), etc. This application does not limit the way in which the PCF network element can send the second policy to the managed AMF network element.

[0197] S907: The managed AMF network element sends the second policy to the terminal device, and the terminal device receives the second policy accordingly.

[0198] After receiving the second policy, the terminal device considers the second policy to be the policy of the corresponding HPLMN or the policy of the registered participating PLMN of the terminal device, since the second policy does not carry the managed PLMN identifier (the policy without carrying the PLMN identifier is the policy of the corresponding HPLMN by default) or carries the participating PLMN identifier registered by the terminal device. Therefore, the terminal device can use the second policy.

[0199] In some embodiments, if the participating PLMN is the HPLMN of the terminal device, the managed PLMN identifier carried in the first policy is deleted or replaced with the participating PLMN identifier. After obtaining the second policy, the managed AMF network element can also set the rule priority carried in the second policy to be higher than the rule priority carried in the third policy of the HPLMN for the terminal device. In this way, when both the second policy and the third policy of the HPLMN for the terminal device are issued to the terminal device, the terminal device will still use the second policy because the rule priority of the second policy is higher.

[0200] Taking URSP#1 as the first strategy, URSP#2 as the second strategy, and URSP#3 as the third strategy as an example, if the participating PLMN is the HPLMN of the terminal device, the managed AMF network element can delete the managed PLMN identifier in URSP#1 to obtain URSP#2, and set the rule precedence in URSP#2 to be higher than the rule precedence in URSP#3. Thus, if both URSP#2 and URSP#3 are issued to the terminal device, the terminal device will use URSP#2 because the rule precedence in URSP#2 is higher than that in URSP#3. URSP#3 can be sent to the terminal device by the terminal device's H-PCF network element via the managed PCF and managed AMF network elements. The implementation of sending URSP#3 to the terminal device is similar to the implementation of sending URSP#1 to the terminal device and will not be elaborated further.

[0201] In some embodiments, if the policy (such as the first policy or the third policy) is URSP, the H-PCF network element will send the URSP with the corresponding PSI for URSP grouping. The PSI is associated with the PLMN identifier of the PLMN applied by the URSP. For example, for URSP#1 (i.e., the first policy), it will carry PSI#1, and for URSP#3 (i.e., the third policy), it will carry PSI#3. PSI#1 is associated with the managed PLMN identifier of the managed PLMN applied by URSP#1, and PSI#3 is associated with the HPLMN identifier of the terminal device applied by URSP#3.

[0202] In cases such as initial registration of terminal devices (e.g., re-registration after network loss or power-on after shutdown); when a terminal device moves from EPS to 5GS and there is no existing terminal device policy association between the managed AMF network element and the H-PCF network element; or when the value of the terminal device policy association indicator received by the terminal device from the UDM network element changes from "disabled" to "enabled", the terminal device can report the PSI and PLMN identifiers corresponding to the second policy it is using. Since the managed PCF network element replaces or deletes the managed PLMN identifier in the first policy to obtain the second policy, the terminal device reports the PSI and PLMN identifiers corresponding to the second policy stored in the store. What is actually reported is the PSI and PLMN identifiers corresponding to the first policy. Therefore, if the managed PCF network element receives the first information from the terminal device, including the PSI corresponding to the second policy and the participating PLMN identifier, the managed PCF network element can replace the participating PLMN identifier back with the managed PLMN identifier and send the second information, including the PSI and the managed PLMN identifier, to the H-PCF network element of the terminal device, so that the H-PCF network element of the terminal device can correctly know that the PSI corresponds to the managed PLMN identifier (or managed PLMN).

[0203] In some embodiments, when the managed PLMN shares access network equipment with participating PLMNs, before issuing the managed PLMN's four policies for the terminal devices to the terminal devices, the terminal devices' H-PCF network elements can also disguise the managed PLMN's fourth policy for the terminal devices as the corresponding policy of the participating PLMNs. The policy configuration method shown in Figure 10 will be described below.

[0204] Figure 10 illustrates a third strategy configuration method provided in this application embodiment, the method comprising:

[0205] S1001: The managed PCF network element sends a policy association establishment request to the H-PCF network element, and the H-PCF network element receives the policy association establishment request accordingly. The policy association establishment request carries the identification information of the terminal device, which is used to establish a policy association for the terminal device.

[0206] In an INS (In-Service Network) scenario, the shared access network equipment hosting the PLMN can broadcast the PLMN participation identifier. When a terminal device loses network access (this could mean the terminal device has lost its network connection, the network connection is interrupted and it cannot access the internet, or it is not registered on the cell), or after being powered off and restarted, it needs to search for the PLMN. If the terminal device is within the coverage area of ​​the shared access network equipment, it can choose to participate in the PLMN and initiate access. After selecting to participate in the PLMN, the terminal device can send a registration message (e.g., a registration request) to the hosting AMF (Active Network Function) element through the shared access network equipment. This registration message can carry the participating PLMN identifier (also known as the selected PLMN) and the terminal device's identification information (e.g., SUPI or SUCI).

[0207] Upon receiving a registration message from a terminal device, the managed AMF network element can decide to establish a policy association for the terminal device. This is possible in cases such as initial user registration or when there is no existing policy association between the managed AMF network element and the terminal device's H-PCF network element. For H-PCF network elements, the managed AMF network element can be determined based on the PLMN identifier carried in the terminal device's identification information (this PLMN identifier is the HPLMN identifier of the terminal device's HPLMN). The H-PCF network element is the PCF network element of the PLMN identified by this PLMN identifier.

[0208] If the managed AMF network element decides to establish a policy association for the terminal device, the managed AMF network element can send a policy association establishment request to the managed PCF network element. The policy association establishment request carries the identification information of the terminal device and is used to establish a policy association for the terminal device.

[0209] Optionally, the policy association establishment request may also carry the participating PLMN identifier registered (or selected) by the terminal device, or, if the managed PLMN shares an access network device with only one participating PLMN, it may carry the participating PLMN identifier broadcast by the shared access network device (in the case of the terminal device being registered to the PLMN in the INS scenario), so that the managed PCF network element can know the participating PLMN information registered by the terminal device.

[0210] When a managed PCF network element receives a policy association establishment request from a managed AMF network element, it can send this request to the H-PCF network element of the terminal device to establish a policy (such as URSP) association for the terminal device. The managed PCF network element can be identified based on the PLMN identifier carried in the terminal device's identification information (this PLMN identifier is the HPLMN identifier of the terminal device's HPLMN). The H-PCF network element is the PCF network element of the PLMN identified by this PLMN identifier.

[0211] S1002: The H-PCF network element determines the fourth strategy of the managed PLMN for the terminal device based on the fact that the terminal device is in the INS scenario.

[0212] The fourth strategy includes the traffic descriptor and / or routing descriptor of the corresponding managed PLMN. The fourth strategy does not carry the managed PLMN identifier of the managed PLMN, or carries the participating PLMN identifier of the participating PLMN registered by the terminal device.

[0213] To determine whether a terminal device is in an INS scenario, the managed PCF network element can report this information to the H-PCF network element. For example, if it is determined that the terminal device is in an INS scenario, the managed AMF network element can send a first indication message to the managed PCF network element. This first indication message indicates that the terminal device is in an INS scenario, or indicates that the terminal device has not registered with the managed PLMN. Upon receiving this first indication message, the H-PCF network element can determine that the terminal device is in an INS scenario. The implementation of the managed PCF network's determination of whether a terminal device is in an INS scenario can be referenced from step S905 above, and will not be elaborated further.

[0214] Of course, whether a terminal device is in an INS scenario can also be determined by the H-PCF network element.

[0215] As an example: The PLMN identifier carried in the terminal device's identification information (such as SUPI or SUCI) is the HPLMN identifier of the terminal device's HPLMN. If the PLMN identifier carried in the terminal device's identification information is different from the managed PLMN identifier, the H-PCF network element can determine that the terminal device is in an INS scenario. If the PLMN identifier carried in the terminal device's identification information is the same as the managed PLMN identifier, the H-PCF network element can determine that the terminal device is in a non-INS scenario.

[0216] Alternatively, the H-PCF network element can directly determine whether the PLMN identifier of the PLMN registered by the terminal device (which can be obtained from the PLMN identifier of the PLMN registered by the terminal device carried in the terminal device registration message, etc.) belongs to the participating PLMN identifier other than the managed PLMN identifier broadcast by the shared access network device of the managed PLMN (the participating PLMN identifier other than the managed PLMN identifier broadcast by the shared access network device of the managed PLMN can be obtained from the managed PCF network element or the managed AMF network element). If it is the H-PCF network element, it can determine that the terminal device is in an INS scenario; otherwise, the H-PCF network element can determine that the terminal device is in a non-INS scenario.

[0217] Because communication between the shared access network device and the core network of the participating PLMN is routed through the core network of the managed PLMN connected to the shared access network device, if a terminal device registers with a participating PLMN through the shared access network device, the managed PLMN to which the shared access network device belongs is the terminal device's VPLMN. However, since the terminal device is registered with a participating PLMN, it is unaware of the managed PLMN. Therefore, if the H-PCF network element determines that the terminal device is in an INS scenario, and the H-PCF network element determines the fourth policy of the managed PLMN for the terminal device, it can make the fourth policy either not carry the managed PLMN identifier or carry the participating PLMN identifier, thus disguising the fourth policy as the policy of the terminal device's home PLMN or participating PLMN, so that the terminal device can use this policy.

[0218] Taking the fourth policy as URSP (denoted as URSP#4) as an example, after the H-PCF network element receives the policy association establishment request from the managed PCF network element, it can determine URSP#4 based on the auxiliary UE policy information corresponding to the managed PLMN (such as the DNN, SSC mode, or slice information of the application deployed in the managed PLMN). URSP#4 may include the traffic descriptor and / or routing descriptor of the corresponding managed PLMN. If the participating PLMN registered (or selected) by the terminal device is the terminal device's EHPLMN, the fourth policy determined by the H-PCF network element may carry the participating PLMN identifier instead of the managed PLMN identifier; if the participating PLMN registered (or selected) by the terminal device is the terminal device's HPLMN, the fourth policy determined by the H-PCF network element does not carry the PLMN identifier (i.e., it does not carry the managed PLMN identifier).

[0219] In an INS scenario, the terminal device's registered participating PLMN (whether it's an HPLMN or an EHPLMN) can be reported by the hosting PCF network element to the H-PCF network element. For example, the hosting AMF network element can send a second indication message to the hosting PCF network element, indicating whether the terminal device's registered participating PLMN is an HPLMN or an EHPLMN. Alternatively, the H-PCF network element can also determine whether the terminal device's registered participating PLMN is an HPLMN or an EHPLMN.

[0220] In the INS scenario, the H-PCF network element can use one or more of the following methods to determine whether the participating PLMN is the EHPLMN of the terminal device.

[0221] Method C1: The H-PCF network element determines whether the participating PLMN is the EHPLMN of the terminal device based on the SLA or network configuration between the managed PLMN and the participating PLMN.

[0222] As an example: The access network equipment of the managed PLMN is shared with the participating PLMN. The SLA or network configuration between the managed PLMN and the participating PLMN may include the participating PLMN identifier and the EPLMN identifier of the participating PLMN's EPLMN.

[0223] The shared access network equipment broadcasts the participating PLMN identifier. The terminal equipment selects to participate in the PLMN and initiates access. If the HPLMN identifier of the terminal equipment's HPLMN carried in the terminal equipment's identification information (such as SUPI or SUCI) is the EPLMN identifier of the participating PLMN, then the H-PCF network element can determine that the participating PLMN is the terminal equipment's EHPLMN. Otherwise, the H-PCF network element can determine that the participating PLMN is not the terminal equipment's EHPLMN.

[0224] Method C2: The H-PCF network element determines whether the participating PLMN is the EHPLMN of the terminal device by judging whether the participating PLMN initiated by the terminal device is the EPLMN of the terminal device's HPLMMN.

[0225] As an example: H-PCF network elements can obtain the PLMN identifier carried in the identification information of terminal devices. If the PLMN identifier of the participating PLMN is different from the PLMN identifier carried in the identification information of the terminal device, H-PCF network elements can determine the EPLMN of the HPLMN registered by the terminal device. Regardless of whether the participating PLMN is the EHPLMN of the terminal device, H-PCF network elements can process the participating PLMN as the EHPLMN of the terminal device.

[0226] Method C3: The H-PCF network element determines whether the participating PLMN is the terminal device's EHPLMN based on the EHPLMN identifier list reported by the terminal device.

[0227] As an example: a terminal device can report its own EHPLMN identifier list to the H-PCF network element (for example, the EHPLMN identifier list can be reported by the terminal device to the H-PCF network element through the managed AMF network element and the managed PCF network element). The EHPLMN identifier list may include the EHPLMN identifiers of one or more EHPLMNs of the terminal device. If the participating PLMN identifier belongs to the EHPLMN identifier list, the H-PCF network element can determine that the participating PLMN is the terminal device's EHPLMN; otherwise, the H-PCF network element can determine that the participating PLMN is not the terminal device's EHPLMN.

[0228] To determine whether a participating PLMN is the HPLMN of a terminal device, the H-PCF network element can obtain the PLMN identifier carried in the terminal device's identification information (i.e., the HPLMN identifier of the terminal device's HPLMN). If the participating PLMN identifier is the same as the PLMN identifier carried in the terminal device's identification information, the H-PCF network element can determine that the participating PLMN is the HPLMN of the terminal device.

[0229] It should be noted that this application does not limit the timing of H-PCF network elements determining policies (such as the fourth policy of the managed PLMN for terminal devices). For example, H-PCF network elements can determine policies after receiving a policy association establishment request; H-PCF network elements can also determine policies after receiving a policy association establishment request and meeting certain conditions.

[0230] As an example, after receiving a policy association establishment request, an H-PCF network element may temporarily refrain from determining the policy (such as the fourth policy of the managed PLMN for terminal devices) until it receives a policy association modification request or policy association update notification, at which point the policy will be determined.

[0231] Among them, the policy association modification request or policy association update notification can come from the managed AMF network element, which sends it to the H-PCF network element via the managed PCF network element. The policy association modification request or policy association update notification can carry the serving PLMN ID of the terminal device. The H-PCF network element can determine the PLMN serving the terminal device based on the serving PLMN ID, that is, the PLMN selected by the terminal device when it initiates access (or registration).

[0232] For example, after receiving a registration request from a terminal device, the shared access network device can send a selected PLMN ID to the managed AMF network element. This selected PLMN ID is the PLMN ID of the PLMN selected by the terminal device when initiating access (or registration). After obtaining this selected PLMN ID, the managed AMF network element can send a service PLMN ID to the H-PCF network element through messages such as policy association modification requests or policy association update notifications (which can be sent to the H-PCF network element via the managed PCF). In an INS scenario, when the terminal device selects a participating PLMN to initiate access (or registration), the value of the service PLMN ID can be equal to the selected PLMN ID or the participating PLMN ID broadcast by the shared access network device.

[0233] S1003: The H-PCF network element sends the fourth policy to the managed PCF network element, and the managed PCF receives the fourth policy accordingly.

[0234] After determining the fourth policy of the managed PLMN for the terminal device, the H-PCF network element can send the fourth policy to the managed PCF network element. The fourth policy can be sent to the managed PCF network element through terminal device policy notification (or terminal device policy update notification), etc. This application does not limit the way the H-PCF network element can send the fourth policy to the managed PCF network element.

[0235] After receiving the fourth policy, the managed PCF network element can send the fourth policy to the managed AMF network element. The fourth policy can be sent to the managed AMF network element via terminal device policy notification (or terminal device policy update notification), etc. This application does not limit the method by which the managed PCF network element can send the fourth policy to the managed AMF network element. After receiving the fourth policy, the managed AMF network element can send the fourth policy to the terminal device.

[0236] After receiving the fourth policy, the terminal device recognizes it as either the policy of the corresponding HPLMN or the policy of the registered participating PLMN, since the fourth policy does not carry the managed PLMN identifier (a policy without a PLMN identifier is the default policy of the corresponding HPLMN) or carries the participating PLMN identifier registered by the terminal device. This allows the terminal device to use the fourth policy.

[0237] In some embodiments, if the participating PLMN is the HPLMN of the terminal device, when the H-PCF network element determines the fourth policy, the rule priority carried by the fourth policy can be set to be higher than the rule priority carried by the fifth policy of the HPLMN for the terminal device. In this way, when both the fourth policy and the fifth policy are sent to the terminal device, the terminal device will still use the fourth policy because the rule priority of the fourth policy is higher.

[0238] In some embodiments, if the policy (such as the fourth and fifth policies) is URSP, the H-PCF network element will carry the corresponding PSI when issuing the URSP for packetization. The PSI is associated with the PLMN identifier of the PLMN applied by the URSP. For example, URSP#4 (i.e., the fourth policy) will carry PSI#4, and URSP#5 (i.e., the fifth policy) will carry PSI#5. PSI#4 is associated with the managed PLMN identifier of the managed PLMN applied by URSP#4, and PSI#5 is associated with the HPLMN identifier of the terminal device applied by URSP#5.

[0239] In cases such as initial registration of terminal devices (e.g., re-registration after network loss or power-on after shutdown); when a terminal device moves from EPS to 5GS and there is no existing terminal device policy association between the managed AMF network element and the H-PCF network element; or when the value of the terminal device policy association indicator received by the terminal device from the UDM network element changes from "disabled" to "enabled," the terminal device can report the PSI and PLMN identifiers corresponding to the previously used fourth policy. Since the fourth policy issued by the H-PCF network element to the terminal device carries either a participating PLMN identifier or no PLMN identifier, but not a managed PLMN identifier, the terminal device reporting the PSI and PLMN corresponding to the fourth policy is actually reporting the PSI and participating PLMN identifier corresponding to the fourth policy. Therefore, if the H-PCF network element receives third information from the terminal device including the PSI and participating PLMN identifier corresponding to the fourth policy, the H-PCF network element can replace the participating PLMN identifier with the managed PLMN identifier, or interpret the PSI as corresponding to the managed PLMN identifier, to correctly determine that the PSI corresponds to the managed PLMN identifier (or managed PLMN).

[0240] In some embodiments, when the managed PLMN shares access network equipment with participating PLMNs, before issuing the managed PLMN's six policies for terminal devices to the terminal devices, the managed PCF network element can also disguise the managed PLMN's sixth policy for terminal devices as the corresponding policy of the participating PLMN. The policy configuration method shown in Figure 11 will be described below.

[0241] Figure 11 illustrates a fourth strategy configuration method provided in an embodiment of this application, the method comprising:

[0242] S1101: The managed AMF network element sends a policy association establishment request to the managed PCF network element, and the managed PCF network element receives the policy association establishment request accordingly. The policy association establishment request carries the identification information of the terminal device, which is used to establish a policy association for the terminal device.

[0243] In an INS (In-Service Network) scenario, the shared access network equipment hosting the PLMN can broadcast the PLMN participation identifier. When a terminal device loses network access (this could mean the terminal device has lost its network connection, the network connection is interrupted and it cannot access the internet, or it is not registered on the cell), or after being powered off and restarted, it needs to search for the PLMN. If the terminal device is within the coverage area of ​​the shared access network equipment, it can choose to participate in the PLMN and initiate access. After selecting to participate in the PLMN, the terminal device can send a registration message (e.g., a registration request) to the hosting AMF (Active Network Function) element through the shared access network equipment. This registration message can carry the participating PLMN identifier (also known as the selected PLMN) and the terminal device's identification information (e.g., SUPI or SUCI).

[0244] Upon receiving a registration message from a terminal device, the managed AMF network element can decide to establish a policy association for the terminal device. For example, in the case of initial user registration, the managed AMF network element can decide to establish a policy association for the terminal device.

[0245] If the managed AMF network element decides to establish a policy association for the terminal device, the managed AMF network element can send a policy association establishment request to the managed PCF network element. The policy association establishment request carries the identification information of the terminal device and is used to establish a policy association for the terminal device.

[0246] Optionally, the policy association establishment request may also carry the participating PLMN identifier registered (or selected) by the terminal device, or, if the managed PLMN shares an access network device with only one participating PLMN, it may carry the participating PLMN identifier broadcast by the shared access network device (in the case of the terminal device being registered to the PLMN in the INS scenario), so that the managed PCF network element can know the participating PLMN information registered by the terminal device.

[0247] S1102: Based on the determined terminal device being in an indirect network sharing INS scenario, the managed PCF network element determines the sixth policy of the managed PLMN for the terminal device.

[0248] The sixth strategy includes the SSID of the corresponding managed PLMN, and carries the PLMN identifier of the participating PLMN registered by the terminal device.

[0249] Whether a terminal device is in an INS scenario can be reported by the managed AMF network element to the managed PCF network element, or it can be determined by the managed PCF network element itself. The implementation of the managed PCF determining whether a terminal device is in an INS scenario can refer to the implementation in step S905. The repeated parts will not be described again.

[0250] Because communication between the shared access network device and the core network of the participating PLMN is routed through the core network of the managed PLMN connected to the shared access network device, if a terminal device registers with a participating PLMN through the shared access network device, the managed PLMN to which the shared access network device belongs is the terminal device's VPLMN. However, since the terminal device is registered with a participating PLMN, it is unaware of the managed PLMN. Therefore, if the managed PCF network element determines that the terminal device is in an INS scenario, and the managed PCF network element determines the sixth policy of the managed PLMN for the terminal device, it can make the sixth policy carry the participating PLMN identifier, disguising the sixth policy as the terminal device's participating PLMN policy, so that the terminal device uses this policy.

[0251] Taking the sixth strategy, WLANSP#6, as an example, the managed PCF network element can determine (or generate) WLANSP#6 containing the participating PLMN identifier. The managed PCF network element can determine WLANSP#6 based on information such as the managed PLMN's SSID, validity conditions, and one or more sets of WLAN selection standard configurations. WLANSP#6 carries the participating PLMN identifier, not the managed PLMN identifier.

[0252] It should be noted that this application does not limit the timing of policy determination by the managed PCF network element (such as the sixth policy of the managed PLMN for terminal devices). For example, the managed PCF network element can determine the policy after receiving a policy association establishment request; the managed PCF network element can also determine the policy after receiving a policy association establishment request and meeting certain conditions.

[0253] As an example: After receiving a policy association establishment request, a managed PCF network element may temporarily refrain from determining the policy (such as the sixth policy of the managed PLMN for terminal devices) until it receives a policy association modification request or policy association update notification, at which point the policy will be determined.

[0254] Among them, the policy association modification request or policy association update notification can come from the managed AMF network element and be sent by the managed AMF network element to the managed PCF network element. The policy association modification request or policy association update notification can carry the service PLMN identifier of the terminal device. The managed PCF network element can determine the PLMN serving the terminal device based on the service PLMN identifier, that is, the PLMN selected by the terminal device when initiating access (or registration).

[0255] For example, after receiving a registration request from a terminal device, the shared access network device can send a selected PLMN identifier to the managed AMF network element. This selected PLMN identifier is the PLMN identifier of the PLMN selected by the terminal device when initiating access (or registration). After obtaining this selected PLMN identifier, the managed AMF network element can send a service PLMN identifier to the managed PCF network element through messages such as policy association modification requests or policy association update notifications. In an INS scenario, when the terminal device selects a participating PLMN to initiate access (or registration), the value of the service PLMN identifier can be equal to the selected PLMN identifier or the participating PLMN identifier broadcast by the shared access network device.

[0256] S1103: The managed PCF network element sends the sixth policy to the managed AMF network element, and the managed AMF network element receives the sixth policy accordingly.

[0257] After determining the sixth policy, the managed PCF network element can send the sixth policy to the managed AMF network element. The sixth policy can be sent to the managed AMF network element via terminal device policy notification (or terminal device policy update notification), etc. This application does not limit the method by which the managed PCF network element can send the sixth policy to the managed AMF network element. After receiving the sixth policy, the managed AMF network element can send it to the terminal device.

[0258] After receiving the sixth policy, the terminal device recognizes it as the policy of the PLMN it registered with, since the sixth policy carries the identifier of the PLMN it registered with. Therefore, the terminal device can use the sixth policy.

[0259] In some embodiments, if the participating PLMN is the HPLMN of the terminal device, when the managed PCF network element determines the sixth policy, the rule priority carried by the sixth policy can be set to be higher than the rule priority carried by the seventh policy of the HPLMN for the terminal device. In this way, when both the sixth policy and the seventh policy are issued to the terminal device, the terminal device will still use the sixth policy because the rule priority of the sixth policy is higher.

[0260] In some embodiments, if the terminal device initiates access through the first PLMN (non-home PLMN), and if the terminal device is in an INS scenario, the PCF network element may not send the eighth policy corresponding to the first PLMN to the terminal device, so that the terminal device uses the ninth policy corresponding to the HPLMN, thus aligning the understanding of the policy used by the terminal device on both the terminal device side and the network side.

[0261] Figure 12 is a fifth schematic diagram of the strategy configuration method provided in this application embodiment. The method includes the following steps:

[0262] S1201: The first AMF network element sends a policy association establishment request to the first PCF network element, and correspondingly, the first PCF network element receives the policy association establishment request. The policy association establishment request carries the identification information of the terminal device, used to establish a policy association for the terminal device.

[0263] Among them, the first AMF network element and the first PCF network element are the AMF network element and PCF network element of the first PLMN. The terminal device accesses the communication network through the access network equipment of the first PLMN. The first PLMN is not the home PLMN of the terminal device, that is, the first PLMN is different from the home PLMN of the terminal device.

[0264] When a terminal device loses network access (this could mean the terminal device has lost its network connection, the network connection is interrupted and it cannot access the internet, or it is not registered in the cell), or after being powered off and restarted, it needs to search for a PLMN. If the terminal device is within the coverage area of ​​the access network device of the first PLMN, it can select a PLMN to initiate access based on the PLMN identifier broadcast by the access network device of the first PLMN. After selecting a PLMN, the terminal device can send a registration message (such as a registration request) to the first AMF network element through the access network device of the first PLMN. The registration message can carry the PLMN identifier of the registered (or selected) PLMN, as well as the terminal device's identification information (such as SUPI or SUCI).

[0265] Upon receiving a registration message from a terminal device, the first AMF network element can decide to establish a policy association for the terminal device. For example, in the case of initial user registration, the first AMF network element can decide to establish a policy (such as WLANSP) association for the terminal device.

[0266] If the first AMF network element decides to establish a policy association for the terminal device, the first AMF network element can send a policy association establishment request to the first PCF network element. The policy association establishment request carries the identification information of the terminal device and is used to establish a policy association for the terminal device.

[0267] In one possible implementation, the first PLMN is an unmanaged PLMN, meaning that the access network equipment of the first PLMN does not share with other PLMNs and does not broadcast the PLMN identifiers of other PLMNs. Since the terminal device accesses the communication network through the access network equipment of the first PLMN, the PLMN registered by the terminal device is the first PLMN. The terminal device is roaming to the first PLMN, and the first PLMN is the visited PLMN of the terminal device.

[0268] In one possible implementation, the first PLMN is a managed PLMN, meaning that the access network equipment of the first PLMN can share with participating PLMNs and broadcast the participating PLMNs. If the PLMN registered by the terminal device is the first PLMN, the terminal device is roaming to the first PLMN, and the first PLMN is the visited PLMN of the terminal device. If the PLMN registered by the terminal device is a participating PLMN, then the terminal device is in an INS scenario, that is, it registers to the participating PLMN through the access network equipment of the managed PLMN (first PLMN).

[0269] S1202: The first PCF network element determines that the terminal device is in a non-INS scenario and sends the eighth policy of the first PLMN for the terminal device and / or the ninth policy of the HPLMN for the terminal device to the terminal device.

[0270] Whether a terminal device is in an INS scenario can be determined by the first PCF network element or by the first AMF network element after determination and reporting to the first PCF network element. This application does not limit this.

[0271] As an example: The PLMN identifier carried in the identification information of the terminal device (such as SUPI or SUCI) is the HPLM identifier of the HPLM of the terminal device. If the PLMN identifier carried in the identification information of the terminal device is different from the first PLMN identifier, the first PCF network element can determine that the terminal device is in an INS scenario. If the PLMN identifier carried in the identification information of the terminal device is the same as the first PLMN identifier, the first PCF network element can determine that the terminal device is in a non-INS scenario.

[0272] As another example: The first PLMN is a managed PLMN. A certain PLMN identifier broadcast by the shared access network equipment of the first PLMN is the PLMN identifier of the PLMN registered by the terminal device. The first AMF network element can report the PLMN identifier to the first PCF network element. The first PCF network element can determine whether the PLMN identifier is the same as the first PLMN identifier of the first PLMN. If they are the same, it means that the terminal device is in a non-INS scenario. If they are different, it means that the first PLMN shares the access network equipment with the PLMN registered by the terminal device, and the terminal device is in an INS scenario.

[0273] As another example: The first PLMN is a managed PLMN. The first PLMN only shares access network equipment with a certain PLMN and broadcasts the PLMN identifier of that PLMN. If the PLMN registered by the terminal device is not the first PLMN, the first AMF network element can also report the PLMN identifier to the first PCF network element. Since the PLMN identifier is different from the first PLMN identifier of the first PLMN, the first PCF network element can determine that the terminal device is in the INS scenario.

[0274] In one possible implementation, the terminal device policy may include one or more of ANDSP, URSP, V2XP, or ProSeP, wherein ANDSP may include WLANSP.

[0275] If the terminal device is in a non-INS scenario, it may roam to the first PLMN and initiate access by selecting the first PLMN. The first PCF network element can send the eighth policy of the first PLMN to the terminal device, and can also send the ninth policy of the terminal device's home PLMN to the terminal device. The terminal device can know that it has roamed to the first PLMN and use the ninth policy of the corresponding first PLMN.

[0276] In the INS scenario, communication between the first PLMN shared access network device and the core network of the participating PLMN is routed through the core network of the managed PLMN connected to the shared access network device. Therefore, if the terminal device registers with the participating PLMN through the shared access network device, the managed PLMN to which the shared access network device belongs is the visited PLMN of the terminal device. However, the terminal device is unaware of the managed PLMN. Therefore, if the managed AMF network element determines that the terminal device is in the INS scenario, the first PCF network element may not send the eighth policy of the first PLMN to the terminal device, so that the terminal device can use the ninth policy of the terminal device's HPLMN.

[0277] Taking WLANSP (Policy 8 and Policy 9) as an example, upon receiving a policy association establishment request, the first PCF network element can determine WLANSP#8 (i.e., Policy 8) based on the SSID, validity conditions, and one or more sets of WLAN selection standard configurations of the first PLMN. WLANSP#8 carries the managed PLMN identifier. It can also obtain the HPLMN of the terminal device from the H-PCF network element for WLANSP#9 (i.e., Policy 9) of the terminal device. WLANSP#9 carries the HPLMN identifier. Policy 9 can be determined by the H-PCF network element based on the SSID, validity conditions, and one or more sets of WLAN selection standard configurations of the terminal device's HPLMN.

[0278] Taking URSP (Policy 8 and Policy 9) as an example, the first PCF network element can obtain URSP#8 (i.e., Policy 8) and URSP#9 (i.e., Policy 9) from the H-PCF network element. The H-PCF network element can determine URSP#8 (Policy 8) based on the auxiliary UE policy information corresponding to the first PLMN (such as the DNN, SSC mode, or slice information of the application deployed on the first PLMN). URSP#8 carries the first PLMN identifier. The auxiliary UE policy information corresponding to the first PLMN can come from the first PCF network element and be sent to the H-PCF network element. The H-PCF network element can determine URSP#9 (Policy 9) based on the auxiliary UE policy information corresponding to the HPLMN (such as the DNN, SSC mode, or slice information of the application deployed on the HPLMN). URSP#9 carries the HPLMN identifier.

[0279] In one possible implementation, if the first PCF determines that the terminal device is in an INS scenario, it will not send URSP#8 to the terminal device. The first PCF network element may also not send auxiliary UE policy information to the H-PCF network element, and the H-PCF network element may not determine URSP#8, in order to save signaling or processing resource overhead.

[0280] In some embodiments, if the terminal device initiates access through the first PLMN (non-home PLMN), and if the terminal device is in an INS scenario, the H-PCF network element may not send the eighth policy corresponding to the first PLMN to the terminal device, so that the terminal device uses the ninth policy corresponding to the HPLMN, thus aligning the understanding of the policy used by the terminal device on both the terminal device side and the network side.

[0281] Figure 13 is a schematic diagram of the sixth method for configuring a strategy according to an embodiment of this application. The method includes the following steps:

[0282] S1301: The first PCF network element sends a policy association establishment request to the H-PCF network element, and the H-PCF network element receives the policy association establishment request accordingly. The policy association establishment request carries the identification information of the terminal device, which is used to establish a policy association for the terminal device.

[0283] In this embodiment, the first AMF network element and the first PCF network element are the AMF network element and PCF network element of the first PLMN, and the terminal device accesses the communication network through the access network device of the first PLMN. The H-PCF network element is the PCF network element of the HPLMN of the terminal device.

[0284] When a terminal device loses network access (this could mean the terminal device has lost its network connection, the network connection is interrupted and it cannot access the internet, or it is not registered in the cell), or after being powered off and restarted, it needs to search for a PLMN. If the terminal device is within the coverage area of ​​the access network device of the first PLMN, it can select a PLMN to initiate access based on the PLMN identifier broadcast by the access network device of the first PLMN. After selecting a PLMN, the terminal device can send a registration message (such as a registration request) to the first AMF network element through the access network device of the first PLMN. The registration message can carry the PLMN identifier of the registered (or selected) PLMN, as well as the terminal device's identification information (such as SUPI or SUCI).

[0285] Upon receiving a registration message from a terminal device, the first AMF network element can decide to establish a policy association for the terminal device. For example, in the case of initial user registration, the first AMF network element can decide to establish a policy association for the terminal device.

[0286] If the first AMF network element decides to establish a policy association for the terminal device, the first AMF network element can send a policy association establishment request to the first PCF network element. The policy association establishment request carries the identification information of the terminal device and is used to establish a policy association for the terminal device.

[0287] When the first PCF network element receives a policy association establishment request from the first AMF network element, it can send the request to the H-PCF network element of the terminal device to establish a policy (such as URSP) association for the terminal device. The first PCF network element can be determined based on the PLMN identifier carried in the terminal device's identification information (this PLMN identifier is the HPLMN identifier of the terminal device's HPLMN). The H-PCF network element is the PCF network element of the PLMN identified by this PLMN identifier.

[0288] In one possible implementation, the first PLMN is an unmanaged PLMN, meaning that the access network equipment of the first PLMN does not share with other PLMNs and does not broadcast the PLMN identifiers of other PLMNs. Since the terminal device accesses the communication network through the access network equipment of the first PLMN, the PLMN registered by the terminal device is the first PLMN. The terminal device is roaming to the first PLMN, and the first PLMN is the visited PLMN of the terminal device.

[0289] In one possible implementation, the first PLMN is a managed PLMN, meaning that the access network equipment of the first PLMN can share with participating PLMNs and broadcast the participating PLMNs. If the PLMN registered by the terminal device is the first PLMN, the terminal device is roaming to the first PLMN, and the first PLMN is the visited PLMN of the terminal device. If the PLMN registered by the terminal device is a participating PLMN, then the terminal device is in an INS scenario, that is, it registers to the participating PLMN through the access network equipment of the managed PLMN (first PLMN).

[0290] S1302: Determining that the terminal device is in a non-INS scenario, the H-PCF network element sends the eighth policy of the first PLMN for the terminal device and / or the ninth policy of the HPLMN for the terminal device to the terminal device.

[0291] Whether a terminal device is in an INS scenario can be determined by the H-PCF network element, or it can be determined by the first PCF network element and then reported to the first PCF network element. This application does not limit this.

[0292] As an example: The PLMN identifier carried in the terminal device's identification information (such as SUPI or SUCI) is the HPLMN identifier of the terminal device's HPLMN. If the PLMN identifier carried in the terminal device's identification information is different from the first PLMN identifier, the H-PCF network element can determine that the terminal device is in an INS scenario. If the PLMN identifier carried in the terminal device's identification information is the same as the first PLMN identifier, the H-PCF network element can determine that the terminal device is in a non-INS scenario.

[0293] As another example: The first PLMN is a managed PLMN. A certain PLMN identifier broadcast by the shared access network equipment of the first PLMN is the PLMN identifier of the PLMN registered by the terminal device. The first AMF network element can report the PLMN identifier to the H-PCF network element. The H-PCF network element can determine whether the PLMN identifier is the same as the first PLMN identifier of the first PLMN. If they are the same, it means that the terminal device is in a non-INS scenario. If they are different, it means that the first PLMN shares the access network equipment with the PLMN registered by the terminal device, and the terminal device is in an INS scenario.

[0294] As another example: The first PLMN is a managed PLMN. The first PLMN only shares access network equipment with a certain PLMN and broadcasts the PLMN identifier of that PLMN. If the PLMN registered (or selected) by the terminal device is not the first PLMN, the H-PCF network element can also report the PLMN identifier to the H-PCF network element. Since the PLMN identifier is different from the first PLMN identifier of the first PLMN, the H-PCF network element can determine that the terminal device is in the INS scenario.

[0295] If the terminal device is in a non-INS scenario, it may roam to the first PLMN and initiate access by selecting the first PLMN. The first PCF network element can send the eighth policy of the first PLMN to the terminal device, and can also send the ninth policy of the terminal device's home PLMN to the terminal device. The terminal device can know that it has roamed to the first PLMN and use the ninth policy of the corresponding first PLMN.

[0296] In the INS scenario, communication between the first PLMN shared access network device and the core network of the participating PLMN is routed through the core network of the managed PLMN connected to the shared access network device. Therefore, if the terminal device registers with the participating PLMN through the shared access network device, the managed PLMN to which the shared access network device belongs is the visited PLMN of the terminal device. However, the terminal device is unaware of the managed PLMN. Therefore, if the managed AMF network element determines that the terminal device is in the INS scenario, the H-PCF network element may not send the eighth policy of the first PLMN to the terminal device, so that the terminal device can use the ninth policy of the terminal device's home PLMN.

[0297] Taking the eighth and ninth policies as URSPs as an example, upon receiving a policy association establishment request, the H-PCF network element can determine URSP#8 (i.e., the eighth policy) based on the auxiliary UE policy information corresponding to the first PLMN (such as the DNN, SSC mode, or slice information of the application deployed in the first PLMN). URSP#8 carries the first PLMN identifier. The auxiliary UE policy information corresponding to the first PLMN can come from the first PCF network element and be sent by the first PCF network element to the H-PCF network element. The H-PCF network element can determine URSP#9 (i.e., the ninth policy) based on the auxiliary UE policy information corresponding to the HPLMN (such as the DNN, SSC mode, or slice information of the application deployed in the HPLMN). URSP#9 carries the HPLMN identifier.

[0298] In one possible implementation, if the first PCF determines that the terminal device is in an INS scenario, the first PCF network element may not send auxiliary UE policy information to the H-PCF network element, and the H-PCF network element may not determine URSP#8, in order to save signaling or processing resource overhead.

[0299] The communication device provided in the embodiments of this application is described below. Please refer to FIG14, which is a schematic diagram of the structure of a communication device according to an embodiment of this application. The communication device may include units or modules corresponding to all or part of the steps in the above method embodiments, and can be used to execute the steps executed by each network element in the above embodiments. For details, please refer to the relevant descriptions in the above method embodiments.

[0300] As shown in Figure 14, the communication device 1400 includes a processing unit 1410 and an interface unit 1420. The processing unit 1410 can be a processor or a processing circuit, and the interface unit 1420 can be a transceiver unit or an input / output interface. The communication device 1400 can be used to implement the steps executed by each network element in the above embodiments.

[0301] When the communication device 1400 is used to implement the steps performed by the managed AMF network element or the managed PCF network element in the above embodiments:

[0302] Interface unit 1420 is used to obtain a first policy of the managed public land mobile network (PLMN) for the terminal device, the first policy carrying the managed PLMN identifier of the managed PLMN; processing unit 1410 is used to delete the managed PLMN identifier carried in the first policy or replace the managed PLMN identifier carried in the first policy with the participating PLMN identifier of the participating PLMN registered by the terminal device, based on the determination that the terminal device is in an INS scenario, to obtain a second policy; interface unit 1420 is also used to send the second policy to the terminal device.

[0303] In one possible design, the processing unit 1410 determines that the terminal device is in an INS scenario before the interface unit 1420 obtains the first policy of the managed PLMN for the terminal device; or, after the interface unit 1420 obtains the first policy of the managed PLMN for the terminal device, it determines that the terminal device is in an INS scenario.

[0304] In one possible design, the first strategy is URSP. When the processing unit 1410 obtains the second strategy, it specifically uses the participating PLMN as the home PLMN of the terminal device, deletes the managed PLMN identifier carried in the first strategy, and obtains the second strategy; or, the participating PLMN is the equivalent home PLMN of the terminal device, and replaces the managed PLMN identifier carried in the first strategy with the participating PLMN identifier, and obtains the second strategy.

[0305] In one possible design, the first strategy is WLANSP, and the processing unit 1410 obtains a second strategy, which includes: the participating PLMN is the home PLMN or equivalent home PLMN of the terminal device, and the managed PLMN identifier carried in the first strategy is replaced with the participating PLMN identifier of the participating PLMN to obtain the second strategy.

[0306] In one possible design, the participating PLMN is the home PLMN of the terminal device, and the processing unit 1410 is further configured to set the priority of the rule carried by the second policy to be higher than the priority of the rule carried by the participating PLMN for the terminal device in the third policy.

[0307] In one possible design, the processing unit 1410 is further configured to determine that the participating PLMN is the home PLMN of the terminal device if the participating PLMN identifier is the same as the PLMN identifier carried in the identification information of the terminal device; or, if the participating PLMN identifier is different from the PLMN identifier carried in the identification information of the terminal device, determine that the participating PLMN is the equivalent home PLMN of the terminal device.

[0308] In one possible design, the interface unit 1420 is further configured to receive first information from the terminal device, the first information including the policy section identifier (PSI) and the participating PLMN identifier corresponding to the second policy; the processing unit 1410 is further configured to replace the participating PLMN identifier included in the first information with the managed PLMN identifier based on the determined terminal device being in an INS scenario, thereby obtaining a second message; the interface unit 1420 is further configured to send the second information to the policy control function network element of the home PLMN of the terminal device.

[0309] In one possible design, the interface unit 1420 is also used to receive first indication information from the access and mobility management function network element of the managed PLMN before sending the second policy to the terminal device. The first indication information indicates that the terminal device is in an INS scenario or indicates that the terminal device has not registered with the managed PLMN.

[0310] In one possible design, when interface unit 1420 receives first indication information from the access and mobility management function network element of the managed PLMN, it is specifically used to receive the first indication information and the participating PLMN identifier from the access and mobility management function network element of the managed PLMN.

[0311] In one possible design, the first strategy includes one or more of the following: ANDSP, URSP, WLANSP, V2XP, or ProSeP.

[0312] When the communication device 1400 is used to implement the steps performed by the H-PCF network element in the above embodiments:

[0313] Interface unit 1420 is configured to receive a policy association establishment request from a policy control function network element of a managed public land mobile network (PLMN). The policy association establishment request carries the identification information of the terminal device and is used to establish a policy association for the terminal device. Processing unit 1410 is configured to determine a fourth policy of the managed PLMN for the terminal device based on the determined scenario that the terminal device is in an indirect network sharing (INS) scenario. The fourth policy includes a traffic descriptor and / or a routing descriptor corresponding to the managed PLMN. The fourth policy does not carry the managed PLMN identifier, or carries the participating PLMN identifier registered by the terminal device. Interface unit 1420 is also configured to send the fourth policy to the policy control function network element of the managed PLMN.

[0314] In one possible design, the participating PLMN is the home PLMN of the terminal device, and the fourth strategy does not carry the host PLMN identifier; or, the participating PLMN is the equivalent home PLMN of the terminal device, and the fourth strategy carries the participating PLMN identifier.

[0315] In one possible design, the participating PLMN is the home PLMN of the terminal device, and the rule priority carried by the fourth policy is higher than the rule priority carried by the home PLMN for the terminal device by the fifth policy.

[0316] In one possible design, the interface unit 1420 is further configured to receive third information from the policy control function network element of the managed PLMN, the third information including the policy section identifier (PSI) corresponding to the fourth policy and the participating PLMN identifier; the processing unit 1410 is further configured to determine the association between the PSI and the managed PLMN identifier based on the determined terminal device being in an INS scenario.

[0317] In one possible design, the interface unit 1420 is also used to receive first indication information from the policy control function network element of the managed PLMN before sending the fourth policy to the terminal device. The first indication information indicates that the terminal device is in an INS scenario or indicates that the terminal device has not registered with the managed PLMN.

[0318] In one possible design, the fourth strategy is URSP.

[0319] When the communication device 1400 is used to implement the steps performed by the managed PCF network element in the above embodiments:

[0320] Interface unit 1420 is used to receive a policy association establishment request from the access and mobility management function network element of the managed PLMN. The policy association establishment request carries the identification information of the terminal device and is used to establish a policy association for the terminal device. Processing unit 1410 is used to determine the sixth policy of the managed PLMN for the terminal device based on the determination that the terminal device is in an INS scenario. The sixth policy includes the SSID of the corresponding managed PLMN and carries the participating PLMN identifier of the participating PLMN registered by the terminal device. Interface unit 1420 is used to send the sixth policy to the policy control function network element of the managed PLMN.

[0321] In one possible design, the participating PLMN is the home PLMN of the terminal device, and the rule priority carried by the sixth policy is higher than the rule priority carried by the home PLMN for the terminal device by the seventh policy.

[0322] In one possible design, the sixth strategy is WLANSP.

[0323] When the communication device 1400 is used to implement the steps performed by the first PCF network or HCF network element in the above embodiments:

[0324] Interface unit 1420 is used to receive a policy association establishment request, which carries the identification information of the terminal device and is used to establish a policy association for the terminal device; and when the processing unit 1410 determines that the terminal device is in a non-INS scenario, it sends the eighth policy of the first PLMN for the terminal device and / or the ninth policy of the terminal device's home PLMN for the terminal device to the terminal device, wherein the terminal device accesses the communication network through the access network device of the first PLMN, and the first PLMN is different from the terminal device's home PLMN.

[0325] In one possible design, interface unit 1420 is also used to send the ninth policy of the terminal device’s home PLMN to the terminal device if the terminal device is in an INS scenario.

[0326] As shown in Figure 15, this application also provides a communication device 1500, including a processor 1510 and potentially a communication interface 1520. The processor 1510 and the communication interface 1520 are coupled to each other. It is understood that the communication interface 1520 can be a transceiver, input / output interface, input interface, output interface, interface circuit, etc. Optionally, the communication device 1500 may further include a memory 1530 for storing instructions executed by the processor 1510, or storing input data required by the processor 1510 to execute instructions, or storing data generated after the processor 1510 executes instructions. The memory 1530 can be a physically independent unit, or it can be coupled to the processor 1510, or the processor 1510 may include the memory 1530.

[0327] When the communication device 1500 is used to implement the steps executed by each network element in the above embodiments, the processor 1510 can be used to implement the function of the processing unit 1410, and the communication interface 1520 can be used to implement the function of the interface unit 1420.

[0328] In this application embodiment, the processor (e.g., processor 1510) can be one or more central processing units (CPUs). If the processor is a CPU, it can be a single-core CPU or a multi-core CPU. The processor can also be one or a combination of several of the following: CPU, general-purpose processor, application-specific integrated circuit (ASIC), digital signal processor (DSP), microprocessor unit (MPU), microcontroller unit (MCU), graphics processing unit (GPU), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, artificial intelligence processor (AI processor), or neural processing unit (NPU). The processor can implement or execute the methods, steps, and logic block diagrams disclosed in this application embodiment. The steps of the methods disclosed in this application embodiment can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0329] In this embodiment, the memory (e.g., memory 1530) may include, but is not limited to, cache, read-only memory (ROM), random access memory (RAM), synchronous dynamic random access memory (SDRAM), hard disk drive (HDD) or solid-state drive (SSD), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), etc. Memory is any other medium capable of carrying or storing desired program code having an instruction or data structure form and accessible by a computer, but is not limited thereto. The memory in this embodiment may also be a circuit or any other device capable of implementing storage functions for storing computer programs or instructions, and / or data.

[0330] It is understood that the method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium well known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Additionally, the ASIC can reside in a network device or a terminal device. Alternatively, the processor and storage medium can exist as discrete components in the network device or terminal device.

[0331] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one network device, terminal, computer, server, or data center to another network device, terminal, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0332] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0333] In the embodiments of this application, the term "exemplary" is used to indicate that it is an example, illustration, or description. Any embodiment or design that is described as "exemplary" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Rather, the use of the term "exemplary" is intended to present the concept in a specific manner.

[0334] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

Claims

1. A policy configuration method, characterized by, The method comprises: obtaining a first policy of a hosting public land mobile network (PLMN) for a terminal device, the first policy carrying a hosting PLMN identifier of the hosting PLMN; based on a determination that the terminal device is in an indirect network sharing (INS) scenario, deleting or replacing the hosting PLMN identifier carried by the first policy with a participating PLMN identifier of a participating PLMN in which the terminal device is registered, to obtain a second policy; sending the second policy to the terminal device.

2. The method of claim 1, wherein, The method further comprises: determining that the terminal device is in an INS scenario before obtaining the first policy of the hosting PLMN for the terminal device; or determining that the terminal device is in an INS scenario after obtaining the first policy of the hosting PLMN for the terminal device.

3. The method of claim 1 or 2, wherein, The first policy is a user equipment route selection policy (URSP), and the obtaining of the second policy comprises: the participating PLMN is a home PLMN of the terminal device, and the hosting PLMN identifier carried by the first policy is deleted to obtain the second policy; or the participating PLMN is an equivalent home PLMN of the terminal device, and the hosting PLMN identifier carried by the first policy is replaced with the participating PLMN identifier to obtain the second policy.

4. The method of claim 1 or 2, wherein, The first policy is a wireless local area network selection policy (WLANSP), and the obtaining of the second policy comprises: the participating PLMN is a home PLMN or an equivalent home PLMN of the terminal device, and the hosting PLMN identifier carried by the first policy is replaced with a participating PLMN identifier of the participating PLMN to obtain the second policy.

5. The method of claim 3 or 4, wherein, The participating PLMN is a home PLMN of the terminal device, and the method further comprises: setting a rule priority carried by the second policy to be higher than a rule priority carried by a third policy of the participating PLMN for the terminal device.

6. The method of any one of claims 3-5, wherein, If the participating PLMN identifier is the same as a PLMN identifier carried by identification information of the terminal device, the participating PLMN is determined to be a home PLMN of the terminal device; or if the participating PLMN identifier is not the same as the PLMN identifier carried by the identification information of the terminal device, the participating PLMN is determined to be an equivalent home PLMN of the terminal device.

7. The method of claim 3, wherein, The method further comprises: receiving first information from the terminal device, the first information comprising a policy section identifier (PSI) corresponding to the second policy and the participating PLMN identifier; based on a determination that the terminal device is in an INS scenario, replacing the participating PLMN identifier included in the first information with the hosting PLMN identifier to obtain second information; sending the second information to a policy control function network element of a home PLMN of the terminal device.

8. The method of any one of claims 1-7, wherein, Before the sending of the second policy to the terminal device, the method further comprises: receiving first indication information from an access and mobility management function network element of the hosting PLMN, the first indication information indicating that the terminal device is in an indirect network sharing INS scenario, or indicating that the terminal device is not registered to the hosting PLMN.

9. The method of claim 8, wherein, receiving first indication information from an access and mobility management function network element of the hosting PLMN, including: receiving the first indication information and the participating PLMN identity from the access and mobility management function network element of the hosting PLMN.

10. The method of any one of claims 1-9, wherein, the first policy includes one or more of the following: an access network discovery and selection policy ANDSP, a user equipment route selection policy URSP, a WLAN policy WLANSP, a vehicle-to-everything policy V2XP, or a proximity service policy ProSeP.

11. A policy configuration method, characterized by, including: receiving a policy association establishment request from a policy control function network element of a hosting public land mobile network PLMN, the policy association establishment request carrying identity information of a terminal device, for establishing a policy association for the terminal device; determining a fourth policy of the hosting PLMN for the terminal device based on the determination that the terminal device is in an INS scenario, wherein the fourth policy includes a traffic descriptor and / or a routing selection descriptor corresponding to the hosting PLMN, and the fourth policy does not carry a hosting PLMN identity of the hosting PLMN or carries a participating PLMN identity of a participating PLMN to which the terminal device is registered; sending the fourth policy to the policy control function network element of the hosting PLMN.

12. The method of claim 11, wherein, the participating PLMN is a home PLMN of the terminal device, and the fourth policy does not carry the hosting PLMN identity; or the participating PLMN is an equivalent home PLMN of the terminal device, and the fourth policy carries the participating PLMN identity.

13. The method of claim 12, wherein, the participating PLMN is a home PLMN of the terminal device, and a rule priority carried by the fourth policy is higher than a rule priority carried by a fifth policy of the home PLMN for the terminal device.

14. The method of claim 13, wherein, the method further includes: receiving third information from the policy control function network element of the hosting PLMN, the third information including a policy section identity PSI corresponding to the fourth policy and the participating PLMN identity; determining that the PSI is associated with the hosting PLMN identity based on the determination that the terminal device is in an INS scenario.

15. The method of any one of claims 11-14, wherein, before sending the fourth policy to the terminal device, the method further includes: receiving first indication information from an access and mobility management function network element of the hosting PLMN, the first indication information indicating that the terminal device is in an INS scenario, or indicating that the terminal device is not registered to the hosting PLMN.

16. The method of any one of claims 11-15, wherein, the fourth policy is a user equipment route selection policy URSP.

17. A policy configuration method, characterized by, including: receiving a policy association establishment request from an access and mobility management function network element of a hosting public land mobile network PLMN, the policy association establishment request carrying identity information of a terminal device, for establishing a policy association for the terminal device; determine a sixth policy for the terminal device from the hosting PLMN based on the determination that the terminal device is in the indirect network sharing INS scenario, wherein the sixth policy comprises a service set identifier, SSID, corresponding to the hosting PLMN, and the sixth policy carries a participating PLMN identifier of a participating PLMN to which the terminal device registers; send the sixth policy to a policy control function network element of the hosting PLMN.

18. The method of claim 17, wherein, The participating PLMN is a home PLMN of the terminal device, and a rule priority carried by the sixth policy is higher than a rule priority carried by a seventh policy for the terminal device from the home PLMN.

19. The method of claim 17 or 18, wherein, The sixth policy is a wireless local area network selection policy, WLANSP.

20. A policy configuration method, characterized by, Comprising: receiving a policy association establishment request carrying identification information of a terminal device, for establishing a policy association for the terminal device; determining that the terminal device is in a non-indirect network sharing INS scenario, and sending a first PLMN policy for the terminal device and / or a ninth policy for the terminal device from a home PLMN of the terminal device to the terminal device, wherein the terminal device accesses a communication network through an access network device of the first PLMN, and the first PLMN is different from the home PLMN of the terminal device.

21. A communications device, characterized by comprise a module or unit for performing the method of any one of claims 1-10; or, comprise a module or unit for performing the method of any one of claims 11-16; or, comprise a module or unit for performing the method of any one of claims 17-19; or, comprise a module or unit for performing the method of claim 20.

22. A communications device, characterized by comprise a processor and an interface circuit for inputting and / or outputting signals, and the processor is configured to implement the method of any one of claims 1-10 through a logic circuit or an execution instruction; or, implement the method of any one of claims 11-16; or, implement the method of any one of claims 17-19; or, implement the method of claim 20.

23. A computer program product, characterised in that, comprise a computer program or instruction, when executed by a processor, so that the method of any one of claims 1-10 is implemented; or, so that the method of any one of claims 11-16 is implemented; or, so that the method of any one of claims 17-19 is implemented; or, so that the method of claim 20 is implemented.

24. A chip system, characterized by The chip system comprises a processor configured to be coupled with a memory configured to store a computer program or instruction, when the computer program or instruction is executed by the processor, the method of any one of claims 1-10 is implemented; or, the method of any one of claims 11-16 is implemented; or, the method of any one of claims 17-19 is implemented; or, the method of claim 20 is implemented.

25. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, when the computer program or instructions are executed by a processor, causes the method of any one of claims 1-10 to be implemented; or causes the method of any one of claims 11-16 to be implemented; or causes the method of any one of claims 17-19 to be implemented; or causes the method of claim 20 to be implemented.

Images