CN117897983A

CN117897983A - Method for access and mobility policy decision

Info

Publication number: CN117897983A
Application number: CN202180101947.XA
Authority: CN
Inventors: 严晓健; 朱进国
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2021-11-05
Filing date: 2021-11-05
Publication date: 2024-04-16
Also published as: WO2023077391A1

Abstract

A wireless communication method for use in access and mobility management functions is disclosed. The method includes transmitting non-public network information associated with a wireless terminal to a policy control function, and receiving from the policy control function at least one access and mobility policy parameter determined based on the non-public network information of the wireless terminal.

Description

Method for access and mobility policy decision

Technical Field

The present application is directed generally to wireless communications, and more particularly to 5 th generation (5G) wireless communications.

Background

Public network integrated non-public networks (PNI-NPN) are NPN made available via Public Land Mobile Network (PLMN), for example by means of a private Data Network Name (DNN) or by means of one or more network slice instances assigned to the NPN. When the PNI-NPN is made available via the PLMN, the UE should have a subscription to the PLMN in order to access the PNI-NPN.

A Policy Control Function (PCF) may be configured to determine policies in a (5G) network. In some scenarios, a single network slice may be assigned to multiple PNI-NPN when considering that the number of network slices is limited and that PNI-NPN may have different requirements on the relevant policies. However, the PCF may not consider the PNI-NPN in determining the corresponding policy. Thus, the determined policy may not meet the different requirements of different PNI-NPN.

Disclosure of Invention

The present application relates to methods, systems, and devices for access and mobility policy decisions, and more particularly, to methods, systems, and devices for NPN access and mobility policy decisions.

The present disclosure relates to a wireless communication method for use in access and mobility management functions. The method comprises the following steps: transmitting non-public network information associated with the wireless terminal to the policy control function, and

at least one access and mobility policy parameter determined based on non-public network information of the wireless terminal is received from the policy control function.

Various embodiments may preferably implement the following features:

preferably, the non-public network information is associated with at least one non-public network to which the wireless terminal is allowed to access.

Preferably, the non-public network information includes a Closed Access Group (CAG) list.

Preferably, the at least one access and mobility policy parameter comprises at least one of a radio access technology/frequency selection priority index, a maximum aggregate bit rate or a CAG list.

Preferably, the wireless communication method further comprises:

transmitting at least one access and mobility policy parameter obtained from the unified data management to the policy control function,

wherein the at least one access and mobility policy parameter received from the policy control function is determined further based on the at least one access and mobility policy parameter obtained from the unified data management.

Preferably, the wireless communication method further comprises:

subscription data associated with the wireless terminal is obtained from a unified data management,

wherein the non-public network information is determined based on subscription data.

Preferably, the subscription data comprises at least one of a subscribed wireless access technology/frequency selection priority index, a subscribed maximum aggregate bit rate or a subscribed CAG list.

Preferably, the wireless communication method further comprises transmitting the at least one access and mobility policy parameter to at least one of a wireless network node or a wireless terminal serving the wireless terminal.

The present disclosure relates to a wireless communication method for use in a policy control function. The method comprises the following steps:

receiving non-public network information associated with a wireless terminal from an access and mobility management function, an

At least one access and mobility policy parameter determined based on non-public network information of the wireless terminal is transmitted to the access and mobility management function.

Various embodiments may preferably implement the following features:

preferably, the non-public network information is associated with at least one non-public network allowing the wireless terminal to access.

Preferably, the wireless communication method further comprises:

at least one access and mobility policy parameter obtained from the unified data management is received from the access and mobility management function,

wherein the at least one access and mobility policy parameter transmitted to the access and mobility function is determined further based on the at least one access and mobility policy parameter obtained from the unified data management.

The present disclosure relates to a wireless device including access and mobility management functions. The wireless device includes:

a communication unit configured to:

transmitting non-public network information associated with the wireless terminal to the policy control function, and

Various embodiments may preferably implement the following features:

preferably, the wireless device further comprises a processor configured to perform any of the aforementioned wireless communication methods.

The present disclosure relates to a wireless device including a policy control function. The wireless device includes:

a communication unit configured to:

Various embodiments may preferably implement the following features:

The present disclosure relates to a computer program product comprising computer readable program medium code stored thereon, which code, when executed by a processor, causes the processor to implement a wireless communication method in any of the foregoing methods.

The exemplary embodiments disclosed herein are intended to provide features that will become apparent by reference to the following description when taken in conjunction with the accompanying drawings. According to various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. However, it should be understood that these embodiments are presented by way of example and not limitation, and that various modifications of the disclosed embodiments may be made while remaining within the scope of the disclosure, as would be apparent to one of ordinary skill in the art having read the present disclosure.

Thus, the disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Additionally, the specific order and/or hierarchy of steps in the methods disclosed herein are merely exemplary approaches. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes may be rearranged while remaining within the scope of the present disclosure. Thus, it will be appreciated by one of ordinary skill in the art that the methods and techniques disclosed herein present various steps or acts in a sample order and that the present disclosure is not limited to the particular order or hierarchy presented unless specifically stated otherwise.

Drawings

The above and other aspects and embodiments thereof will be described in more detail in the accompanying drawings, description and claims.

Fig. 1 shows a schematic diagram of a network (architecture) according to an embodiment of the present disclosure.

Fig. 2 shows a schematic diagram of a registration process according to an embodiment of the present disclosure.

Fig. 3 shows a schematic diagram of a registration process according to an embodiment of the present disclosure.

Fig. 4 shows a schematic diagram of a registration process according to an embodiment of the present disclosure.

Fig. 5 shows an example of a schematic diagram of a wireless terminal according to an embodiment of the present disclosure.

Fig. 6 shows an example of a schematic diagram of a wireless network node according to an embodiment of the disclosure.

Fig. 7 shows a flow chart of a method according to an embodiment of the present disclosure.

Fig. 8 shows a flow chart of a method according to an embodiment of the present disclosure.

Detailed Description

Fig. 1 shows a schematic diagram of a network (architecture) according to an embodiment of the present disclosure. In fig. 1, the network comprises the following network functions/entities:

1) UE: user equipment

2) RAN: radio access network

In this disclosure, the RAN may be equivalent to a RAN node or a next generation RAN (NG-RAN) (node).

3) AMF: access and mobility management functions

The AMF includes the following functions: registration management, connection management, reachability management, and mobility management. The AMF terminates RAN Control Plane (CP) interface N2 and NAS interface N1, non-access stratum (NAS) ciphering and integrity protection. It also allocates a Session Management (SM) NAS to the appropriate Session Management Function (SMF) via interface N11. The AMF serves other consumer Network Functions (NF) to subscribe to or obtain notifications of mobility related events and information.

4) SMF: session management function

The SMF includes the following functions: session establishment, modification and release, UE IP address allocation & management (including optional authorization functions), selection and control of User Plane (UP) functions, downlink data notification. The SMF may subscribe to mobility related events and information from the AMF.

5) UPF: user plane functionality

The UPF includes the following functions: acting as anchor points for intra/inter Radio Access Technology (RAT) mobility and external session points interconnected to the data network, packet routing & forwarding as indicated by SMF, traffic usage reporting, quality of service (QoS) handling by UP, downlink packet buffering and downlink data notification triggering, etc.

6) UDM: unified data management

The UDM manages subscription profiles for the UEs. The subscription includes data for mobility management (e.g., restricted area), session management (e.g., qoS profile for each slice of each DNN). The subscription data also includes a slice selection parameter that is used by the AMF to select the appropriate SMF. AMF and SMF obtain subscriptions from UDM. The subscription data is stored in a unified data store (UDR). UDM uses these data when receiving a request from AMF or SMF.

7) PCF: policy control function

The PCF supports a unified policy framework to manage network behavior. The PCF provides access and mobility policies to the AMF via the N15 interface, and/or session management policies to the SMF via the N7 interface, and/or UE policies to the UE. Note that the PCFs for the N7 and N15 interfaces may be the same or different. The PCF may access the UDR to obtain subscription information related to policy decisions. The PCF may also generate policies that govern network behavior based on subscriptions and indications from Application Functions (AFs). The PCF may then provide policy rules to the CP function (e.g., AMF and/or SMF) to enforce the CP function.

8) NEF: network opening function

NEF supports the ability and events to open the network towards AF. The third party AF may invoke services provided by the network via the NEF, and the NEF performs authentication and authorization of the third party application. The NEF also provides translation of information exchanged with the AF and information exchanged with the internal NF.

9) AF: application function

The AF interacts with the core network to provide services (e.g., support applications in the impact of traffic routing, access the NEF, interact with policy frameworks for policy control, etc.). An AF considered to be trusted by the operator may be allowed to interact directly with the associated NF. An AF that the operator does not allow direct access to the NF should interact with the associated NF via the NEF using an external open framework. The AF may store application information in the UDR via the NEF.

In some scenarios, since the PCF is unaware of the PNI-NPN to which the UE belongs, the PCF cannot take the PNI-NPN into account when determining the corresponding policy. Thus, the determined policy may not meet the different requirements of different PNI-NPN.

Furthermore, in some cases, the PCF may still grant a higher UE Aggregate Maximum Bit Rate (AMBR) for the UE even though the total requested bandwidth of the PNI-NPN to which the UE belongs is lower, because the PCF is not aware of the PNI-NPN to which the UE belongs. Thus, radio resources may be wasted.

Further, the UE may subscribe to multiple PNI-NPN using different subscription plans. When the total usage quota for the subscription plan for the UE is reached, the PCF cannot first ensure the UE with the gold PNI-NPN (e.g., the PNI-NPN with the highest limited bit rate after the usage quota is reached in the subscribed PNI-NPN) service because the PCF does not know the PNI-NPN to which the UE belongs.

Since the network slice does not enable the possibility of preventing the UE from attempting to access the network in areas where the UE is not allowed to use the network slice allocated to NPN, the concept of Closed Access Group (CAG) is used to apply access control.

In one embodiment, a CAG identifies a set of users that are permitted to access one or more CAG cells associated with the CAG. The CAG is used for the PNI-NPN to prevent one or more UEs not allowed to access the NPN via the associated cell from automatically selecting and accessing the associated CAG cell.

In one embodiment, one CAG is identified by a CAG Identifier (ID) that is unique within the range of PLMN IDs.

In one embodiment, the CAG cell broadcasts one or more CAG IDs per PLMN.

To use CAGs, a UE supporting CAGs indicated as part of the UE 5GMM core network capabilities may be preconfigured or (re) configured with CAG information included in the subscription as part of the mobility restriction:

-a list of allowed CAGs, i.e. a list of CAG identifiers that the UE is allowed to access; and

-optionally, a CAG only indication indicating whether the UE is only allowed to access 5GS via a CAG cell.

In one embodiment, when the AMF receives the subscribed CAG information from the UDM, the AMF provides the allowed CAG information to the UE based on the CAG information received from the UDM.

In one embodiment, a CAG ID may represent a PNI-NPN. In other words, a single CAG ID may be associated with a single PNI-NPN. Thus, the allowed CAG list for a UE indicates PNI-NPN that the UE is allowed to access. To make the policy more accurate, the AMF may send the PCF an allowed CAG list for the UE. Under such conditions, the PCF can confirm the PNI-NPN to which the UE belongs. Thus, PNI-NPN information may be considered when the PCF makes policy decisions.

Fig. 2 shows a schematic diagram of a registration process according to an embodiment of the present disclosure. In fig. 2, the PCF considers the allowed CAG list when the PCF grants the RFSP index. Specifically, the registration process shown in fig. 2 includes the steps of:

step 201: the UE initiates (e.g., transmits) a registration request towards the NG-RAN. The NG-RAN selects the AMF and forwards the registration request to the AMF. In one embodiment, the UE indicates "CAG supporting" capability in the message.

Step 202: if the AMF does not have subscription data for the UE, the AMF obtains access and mobility subscription data for the UE by using/sending Nudm_SDM_get (request) to the UDM. The UDM sends a nudm_sdm_get response to the AMF that includes access and mobility subscription data (e.g., subscribed-to CAG list and subscribed-to RFSP index associated with the UE).

Step 203: by using nudm_sdm_subscribe (request), the AMF subscription is notified when access and mobility subscription data of the UE is modified.

Step 204: during registration, the AMF selects a PCF for acquiring an AM policy and sends an npcf_ampoliccontrol_create request to the selected PCF. In this embodiment, the npcf_ampoliccontrol_create request includes an allowed CAG list determined by the AMF based on the subscribed CAG list. Alternatively or additionally, the npcf_ampoliccontrol_create request also includes the subscribed RFSP index received from the UDM and/or the allowed nsai determined by the AMF.

Step 205: the PCF evaluates the RFSP index based on at least one of the subscribed RFSP index, the allowed NSSAI, and the allowed CAG list received in step 204 and triggers the authorized RFSP index to the AMF using the npcf_ampoliccontrol_create response.

Step 206: the AMF accepts the UE registration and forwards the authorized RFSP index to the NG-RAN in a registration accept message. If the UE is "CAG-enabled" and the AMF needs to update the UE's CAG information, the AMF may include the CAG information in the registration accept message as part of the mobility restriction.

Step 207: if the CAG list subscribed to in the UDM is changed, the UDM informs the AMF about the change via using Nudm_SDM_Notif.

Step 208: the AMF determines that the allowed CAG list is updated based on the subscribed CAG list received in step 207 and sends the updated allowed CAG list to the PCF using the npcf_ampoliccontrol_update request.

Step 209: the PCF re-evaluates the RFSP index based on the updated allowed CAG list and triggers the updated authorized RFSP index to the AMF via the use of the npcf_ampoliccontrol_update response.

Step 210: the AMF forwards the updated authorized RFSP index to the NG-RAN in an N2 message (e.g., NGAP message).

Fig. 3 shows a schematic diagram of a registration process according to an embodiment of the present disclosure. In this embodiment, the PCF considers the allowed CAG list when the PCF grants the UE-AMBR. The registration process shown in fig. 3 includes the steps of:

step 301: the UE initiates a registration request towards the NG-RAN. The NG-RAN selects the AMF and forwards the registration request to the AMF. In one embodiment, the UE indicates "CAG supporting" capability in the message.

Step 302: if the AMF does not have subscription data for the UE, the AMF obtains access and mobility subscription data for the UE by using/transmitting Nudm_SDM_get (request). The UDM sends a nudm_sdm_get response including access and mobility subscription data to the AMF. In this embodiment, the access and mobility subscription data includes subscribed to UE-AMBR.

Step 303: by using nudm_sdm_subscribe (request), the AMF subscription is notified when access and mobility subscription data of the UE is modified.

Step 304: during registration, the AMF selects a PCF for acquiring an AM policy and sends an npcf_ampoliccontrol_create request to the selected PCF. In this embodiment, the npcf_ampoliccontrol_create request includes an allowed CAG list determined by the AMF based on the subscribed CAG list received from the UDM. In addition, the npcf_ampoliccontrol_create request may also include the subscribed UE-AMBR received from the UDM.

Step 305: the PCF evaluates the UE-AMBR based on the subscribed UE-AMBR and the allowed CAG list received in step 304 and sends the authorized UE-AMBR to the AMF in an npcf_ampoliccontrol_create response. For example, if a CAG ID (e.g., an associated NPN) included in the allowed CAG list does not require high QoS requirements, the PCF may grant the UE a low UE-AMBR.

Step 306: the AMF accepts the UE registration and forwards the authorized UE-AMBR to the NG-RAN in a registration accept message. If the UE is "CAG-enabled" and the AMF needs to update the UE's CAG information, the AMF may include the CAG information in the registration accept message as part of the mobility restriction.

Step 307: if a change occurs to the CAG list subscribed to in the UDM, the UDM notifies the AMF of the change by using Nudm_SDM_Notif.

Step 308: the AMF updates/modifies the allowed CAG list based on the updated subscribed-to CAG list received in step 307 and sends the updated allowed CAG list to the PCF in an npcf_ampoliccontrol_update request.

Step 309: the PCF re-evaluates the UE-AMBR based on the updated allowed CAG list and sends the updated authorized UE-AMBR to the AMF using the Npcf_AMPolicControl_update response.

Step 310: the AMF forwards the updated authorized UE-AMBR to the NG-RAN in an N2 message (e.g., NGAP message).

Fig. 4 shows a schematic diagram of a registration process according to an embodiment of the present disclosure. In fig. 4, the PCF further adjusts the allowed CAG list received from the AMF. The registration process shown in fig. 4 includes the steps of:

step 401: the UE initiates a registration request (message) towards the NG-RAN. The NG-RAN selects the AMF and forwards the registration request to the AMF. In one embodiment, the UE indicates "CAG supporting" capability in the registration request.

Step 402: if the AMF does not have subscription data for the UE, the AMF acquires access and mobility subscription data for the UE by using the Nudm_SDM_get (request). The UDM sends a nudm_sdm_get response to the AMF including access and mobility subscription data of the UE. In one embodiment, the access and mobility subscription data includes a list of subscribed-to CAGs for the UE.

Step 403: using nudm_sdm_subscribe, AMF subscription is notified when access and mobility subscription data is modified.

Step 404: during registration, the AMF selects a PCF for the AM policy and sends an npcf_ampoliccontrol_create request to the selected PCF. In this embodiment, the npcf_ampoliccontrol_create request includes an allowed CAG list determined by the AMF based on the subscribed CAG list received in step 402.

Step 405: the PCF further adjusts the allowed CAG list based on the operator local policy and sends the adjusted allowed CAG list to the AMF using the npcf_ampoliccontrol_create response.

Step 406: the AMF accepts the UE registration and forwards the allowed CAG list received in step 405 to the NG-RAN and UE.

Step 407: if the PCF decides to update the allowed CAG list (e.g., when the total usage quota of the UE is reached and the service of the gold NPN should be ensured, the PCF may only reserve the CAG identifier associated with the gold NPN in the allowed CAG list and remove other CAG identifiers from the allowed CAG list), the PCF sends the updated allowed CAG list to the UE and NG-RAN via the AMG using the npcf_ampolicccontrol_update notify request.

Step 408: the AMF sends an Npcf_AMPolicControl_UpdateNotify response to the PCF.

Step 409: the AMF sends a downlink NAS transport (message) to the NG-RAN. In this embodiment, the downlink NAS transport (message) includes the allowed CAG list received in step 407.

Step 410: the NG-RAN sends a UE configuration update order message to the UE, wherein the UE configuration update order message includes the allowed CAG list received in step 409.

In some embodiments, the AMF performs at least one of:

-obtaining a list of subscribed CAGs from the UDM;

-determining an allowed CAG list based on the subscribed CAG list and sending to the PCF;

receiving an allowed CAG list adjusted by the PCF,

-sending the allowed CAG list to the NG-RAN and the UE.

In some embodiments, the PCF performs at least one of:

-receiving an allowed CAG list determined by the AMF;

-adjusting the allowed CAG list and sending it to the AMF;

-considering the allowed CAG list when granting RFSP indexes;

-considering the allowed CAG list when authorizing the UE-AMBR.

Fig. 5 relates to a schematic diagram of a wireless terminal 50 according to an embodiment of the present disclosure. The wireless terminal 50 may be a User Equipment (UE), a mobile phone, a laptop, a tablet, an electronic book, or a portable computer system, and is not limited thereto. The wireless terminal 50 may include a processor 500, such as a microprocessor or an Application Specific Integrated Circuit (ASIC), a storage unit 510, and a communication unit 520. The storage unit 510 may be any data storage device that stores program code 512 that is accessed and executed by the processor 500. Examples of storage unit 512 include, but are not limited to, a Subscriber Identity Module (SIM), read Only Memory (ROM), flash memory, random Access Memory (RAM), hard disk, and optical data storage devices. The communication unit 520 may be a transceiver and is used to transmit and receive signals (e.g., messages or data packets) according to the processing result of the processor 500. In one embodiment, the communication unit 520 transmits and receives signals via at least one antenna 522 as shown in fig. 5.

In one embodiment, the storage unit 510 and the program code 512 may be omitted, and the processor 500 may include a storage unit having stored program code.

Processor 500 may implement any of the steps of the exemplary embodiments on wireless terminal 50, for example, by executing program code 512.

The communication unit 520 may be a transceiver. Alternatively or additionally, the communication unit 520 may combine a transmitting unit and a receiving unit configured to transmit and receive signals to and from a radio network node (e.g., a base station), respectively.

Fig. 6 relates to a schematic diagram of a wireless network node 60 according to an embodiment of the present disclosure. The radio network node 60 may be a satellite, a Base Station (BS), a network entity, a Mobility Management Entity (MME), a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), a Radio Access Network (RAN) node, a next generation RAN (NG-RAN) node, a gNB, eNB, gNB centralized unit (gNB-CU), a gNB distributed unit (gNB-DU), a data network, a core network, or a Radio Network Controller (RNC), and is not limited thereto. In addition, the wireless network node 60 may include (perform) at least one network function such as an access and mobility management function (AMF), a Session Management Function (SMF), a user location function (UPF), a Policy Control Function (PCF), an Application Function (AF), and the like. The radio network node 60 may comprise a processor 600, such as a microprocessor or ASIC, a storage unit 610 and a communication unit 620. The storage unit 610 may be any data storage device that stores program code 612 that is accessed and executed by the processor 600. Examples of storage unit 612 include, but are not limited to, a SIM, ROM, flash memory, RAM, hard disk, and optical data storage devices. The communication unit 620 may be a transceiver and is used to transmit and receive signals (e.g., messages or data packets) according to the processing result of the processor 600. In one example, communication unit 620 transmits and receives signals via at least one antenna 622 shown in fig. 6.

In one embodiment, the storage unit 610 and the program code 612 may be omitted. The processor 600 may include a memory unit with stored program code.

Processor 600 may implement any of the steps described in the exemplary embodiments on radio network node 60, for example, via execution of program code 612.

The communication unit 620 may be a transceiver. Alternatively or additionally, the communication unit 620 may combine a transmitting unit and a receiving unit configured to transmit and receive signals to and from a wireless terminal (e.g., a user equipment or another wireless network node), respectively.

Fig. 7 shows a flow chart of a method according to an embodiment of the present disclosure. The method shown in fig. 7 may be used in an AMF (e.g., a wireless device that includes an AMF and/or performs at least a portion of the AMF functions), and comprises the steps of:

step 701: non-public network information associated with the wireless terminal is transmitted to the PCF.

Step 702: at least one access and mobility policy parameter determined based on non-public network information of the wireless terminal is received from the PCF.

In fig. 7, the AMF transmits non-public network information associated with a wireless terminal (e.g., UE) to the PCF. Based on the non-public network information, the PCF may update/modify/determine at least one access and mobility policy parameter and transmit the at least one access and mobility policy parameter to the AMF. Note that the AMF may communicate non-public network information to the PCF during registration and/or during other procedures related to access and mobility policy acquisition/determination/transmission. Alternatively or in addition, the AMF may transmit non-public network information to the PCF when the non-public network information is updated and/or the AMF requires/needs (de-updates) access and mobility policies.

In some embodiments, the non-public network information may be information of a (PNI) NPN associated with the wireless terminal. For example, the non-public network information is associated with at least one NPN that allows the wireless terminal to access. Alternatively or additionally, the non-public network information includes a CAG list.

In some embodiments, the access and mobility policy parameters may be parameters/values/lists (for the wireless terminal) associated with the access and mobility policies. For example, the at least one access and mobility policy parameter includes at least one of an RFSP index, an AMBR (e.g., UE-AMBR), and/or a CAG list.

In some embodiments, the AMF further transmits the at least one access and mobility policy parameter to the PCF, for example, if the non-public network information does not include the at least one access and mobility policy parameter. The at least one access and mobility policy parameter may be obtained from the UDM. The PCF determines/modifies/updates the at least one access and mobility policy based on the non-public network information and the at least one access and mobility policy parameter obtained from the UDM.

In some embodiments, the AMF obtains subscription data associated with the wireless terminal from the UDM. Based on the acquired subscription data, the AMF determines non-public network information.

In some embodiments, the subscription data includes at least one of a subscribed RFSP index, a subscribed AMBR, or a subscribed CAG list.

In some embodiments, the AMF transmits at least one access and mobility policy parameter to the wireless terminal and/or a wireless network node (e.g., BS, RAN (node) or NG-RAN (node)) serving the wireless terminal.

Fig. 8 shows a flow chart of a method according to an embodiment of the present disclosure. The method shown in fig. 8 may be used in a PCF (e.g., a wireless device including a PCF or an overall wireless device performing at least a portion of the PCF functionality), and comprises the steps of:

step 801: non-public network information associated with the wireless terminal is received from the AMF.

Step 802: at least one access and mobility policy parameter determined based on non-public network information of the wireless terminal is transmitted to the AMF.

In fig. 8, the PCF receives non-public network information associated with a wireless terminal (e.g., UE) from the AMF. Based on the non-public network information, the PCF may determine/update/modify at least one access and mobility policy parameter. The PCF transmits the at least one access and mobility policy parameter to the AMF. Note that the PCF may receive this non-public network information from the AMF during registration and/or during other procedures associated with access and mobility policy acquisition/determination/transmission. Alternatively or in addition, the PCF may receive the non-public network information from the AMF when the non-public network information is updated and/or the AMF requires/needs (de-updates) access and mobility policies.

In some embodiments, the non-public network information may be information of a (PNI) NPN associated with the wireless terminal. For example, the non-public network information may be associated with at least one NPN that the wireless terminal is permitted to access. Alternatively or additionally, the non-public network information includes a CAG list.

In some embodiments, the PCF further receives the at least one access and mobility policy parameter from the AMF, for example, in case the non-public network information does not include the at least one access and mobility policy parameter. The at least one access and mobility policy parameter may be obtained from the UDM. The PCF determines/modifies/updates the at least one access and mobility policy based on non-public network information and at least one access and mobility policy parameter obtained from the UDM.

While various embodiments of the present disclosure have been described above, it should be understood that they have been presented by way of example only, and not limitation. Likewise, the various figures may depict example architectures or configurations that are provided to enable those of ordinary skill in the art to understand the example features and functions of the disclosure. However, those skilled in the art will appreciate that the present disclosure is not limited to the example architectures or configurations shown, but may be implemented using a variety of alternative architectures and configurations. In addition, as will be appreciated by one of ordinary skill in the art, one or more features of one embodiment can be combined with one or more features of another embodiment described herein. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments.

It should also be appreciated that any reference herein to an element using a designation such as "first," "second," or the like generally does not limit the number or order of such elements. Rather, these names may be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, reference to a first element and a second element does not mean that only two elements can be used, or that the first element must precede the second element in some way.

Further, those of ordinary skill in the art would understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols, for example, that can be referenced throughout the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

Those of skill would further appreciate that any of the various illustrative logical blocks, units, processors, devices, circuits, methods, and functions described in connection with the aspects disclosed herein may be implemented as electronic hardware (e.g., digital, analog, or a combination of both), firmware, various forms of program or design code containing instructions (which may be referred to herein as "software" or "software elements" for convenience), or any combination of these techniques.

To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, units, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software, or as a combination of these techniques, depends upon the particular application and design constraints imposed on the overall system. Those skilled in the art will be able to implement the described functionality in varying ways for each particular application, but such implementation decisions will not result in a departure from the scope of the present disclosure. According to various embodiments, processors, devices, components, circuits, structures, machines, units, etc. may be configured to perform one or more of the functions described herein. The term "configured to" or "configured for" as used herein with respect to a specified operation or function refers to a processor, device, component, circuit, structure, machine, unit, or the like that is physically constructed, programmed, and/or arranged to perform the specified operation or function.

Moreover, those of skill will appreciate that the various illustrative logical blocks, units, devices, components, and circuits described herein may be implemented within or performed by an Integrated Circuit (IC) that may comprise a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, or any combination thereof. Logic blocks, units, and circuits may also include antennas and/or transceivers to communicate with various components within the network or within the device. A general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration for performing the functions described herein. If implemented in software, the functions can be stored on a computer-readable medium as one or more instructions or code. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer readable medium.

Computer-readable media includes both computer storage media and communication media including any medium that enables a computer program or code to be transferred from one place to another. Storage media can be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.

In this application, the term "unit" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the relevant functions described herein. Furthermore, for ease of discussion, various units are described as discrete units; however, it will be apparent to one of ordinary skill in the art that two or more units may be combined to form a single unit that performs the relevant functions in accordance with embodiments of the present disclosure.

Additionally, memory or other memory and communication components may be employed in embodiments of the present disclosure. It should be appreciated that for clarity, the above description has described embodiments of the disclosure with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements, or domains may be used without detracting from the disclosure. For example, functions illustrated as being performed by different processing logic elements or controllers may be performed by the same processing logic element or controller. Thus, references to specific functional units are only to references to suitable means for providing the described functionality rather than indicative of a strict logical or physical structure or organization.

Various modifications to the embodiments described in the disclosure should be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the scope of the disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the novel features and principles as disclosed herein, as recited in the claims.

Claims

1. A wireless communication method for use in access and mobility management functions, the method comprising:

2. The wireless communication method of claim 1, wherein the non-public network information is associated with at least one non-public network that the wireless terminal is allowed to access.

3. The wireless communication method according to claim 1 or 2, wherein the non-public network information comprises a closed access group, CAG, list.

4. A wireless communication method according to any of claims 1 to 3, wherein the at least one access and mobility policy parameter comprises at least one of a radio access technology/frequency selection priority index, a maximum aggregate bit rate or a CAG list.

5. The wireless communication method according to any one of claims 1 to 4, further comprising:

transmitting to the policy control function at least one access and mobility policy parameter obtained from a unified data management,

6. The wireless communication method according to any one of claims 1 to 5, further comprising:

wherein the non-public network information is determined based on the subscription data.

7. The wireless communication method of claim 6, wherein the subscription data comprises at least one of a subscribed wireless access technology/frequency selection priority index, a subscribed maximum aggregate bit rate, or a subscribed CAG list.

8. The wireless communication method according to any one of claims 1 to 7, further comprising:

transmitting the at least one access and mobility policy parameter to at least one of a radio network node serving the radio terminal or the radio terminal.

9. A wireless communication method for use in a policy control function, the method comprising:

10. The wireless communication method of claim 9, wherein the non-public network information is associated with at least one non-public network that the wireless terminal is allowed to access.

11. The wireless communication method according to claim 9 or 10, wherein the non-public network information comprises a closed access group, CAG, list.

12. The wireless communication method according to any of claims 9 to 11, wherein the at least one access and mobility policy parameter comprises at least one of a radio access technology/frequency selection priority index, a maximum aggregate bit rate, or a CAG list.

13. The wireless communication method according to any one of claims 9 to 12, further comprising:

receiving from said access and mobility management function said at least one access and mobility policy parameter obtained from unified data management,

wherein at least one access and mobility policy parameter transmitted to the access and mobility function is determined further based on at least one access and mobility policy parameter obtained from the unified data management.

14. A wireless device comprising access and mobility management functions, the wireless device comprising:

a communication unit configured to:

15. The wireless device of claim 14, further comprising a processor configured to perform the wireless communication method of any of claims 2-8.

16. A wireless device comprising a policy control function, the wireless device comprising:

a communication unit configured to:

17. The wireless device of claim 16, further comprising a processor configured to perform the wireless communication method of any of claims 10 to 13.

18. A computer program product comprising computer readable program medium code stored thereon, which when executed by a processor causes the processor to implement the wireless communication method according to any of claims 1 to 13.