User Equipment (UE) Method and UE

Abstract

The Policy Control Function (PCF) provides UE policies (e.g., URSP, ANDSP, V2XP) to a UE supporting S1 and N1 modes when the UE is registered to 5GS. In addition, UE policies are also used while the UE is registered to EPS. In the current 3GPP specifications, there is no procedure defined to send UE policies to the UE when the UE is attached to EPS. Without UE policies, user data from the UE cannot be properly routed when the UE is registered to EPS. [Solution] A method for a user equipment (UE) includes sending a first message including information for obtaining a UE policy to a mobility management entity (MME) and receiving a second message including the UE policy from the MME.

Description

[Technical Field]

[0001] The present disclosure relates to a User Equipment (UE) method, a communication device method, a UE, and a communication device. [Background technology]

[0002] At the SA#94e plenary, the study on improving 5G UE policy (NPL 2) was agreed as a new research item in 3GPP Release 18. The study has the following objectives:

[0003] #5 Although TS 24.526 specifies the handling of UE policies (i.e., URSPs) that interoperate in 5GS and EPS, there are networks that do not have ANDSF deployment, or the UE cannot receive URSPs in the EPC. In such cases, there is a mismatch in UE behavior when the UE is under EPC coverage because the UE lacks policy on the EPC side and cannot update the UE policy. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". V17.1.0 (2021-12) [Non-patent document 2] SP-211641 "Study on Enhancement of Network Slicing Phase 3" https: / / www.3gpp.org / ftp / tsg_sa / TSG_SA / TSGS_94E_Electronic_2021_12 / Docs / SP-211641.zip [Non-patent document 3] 3GPP TS 24.526: "User Equipment (UE) policies for 5G System (5GS) Stage 3". V17.5.0 (2021-12)

Non-licensed Document 4

Non-licensed Document 5

Non-licensed Document 6

Non-licensed Document 7

Non-licensed literature 9

Non-licensed literature 10

[0005] The Policy Control Function (PCF) provides UE policies (e.g., URSP, ANDSP, V2XP) to UEs supporting S1 and N1 modes when the UE registers with 5GS. In addition, UE policies are also used while the UE is registered with EPS. In the current 3GPP specifications, there is no defined procedure for sending UE policies to the UE when the UE attaches to EPS. Without UE policies, user data from the UE cannot be properly routed when the UE registers with EPS. [Means for solving the problem]

[0006] In an aspect of the present disclosure, a method for a User Equipment (UE) includes sending a first message to a Mobility Management Entity (MME) including information for obtaining a UE policy, and receiving a second message from the MME including the UE policy.

[0007] In an aspect of the present disclosure, a method of a communications device includes receiving a first message from a User Equipment (UE) including information for obtaining a UE policy, sending a second message including the information to a Serving Gateway (S-GW), receiving a third message including the UE policy from the S-GW, and sending a fourth message including the UE policy to the UE, wherein the communications device is a Mobility Management Entity (MME).

[0008] In an aspect of the present disclosure, a method of a communications device receives a first message including information for obtaining a UE policy from a Mobility Management Entity (MME), sends a second message including the information to a Packet Data Network (PDN) Gateway Control plane function (PGW-C) and a Session Management Function (SMF), receives a third message including the UE policy from the PGW-C and the SMF, and sends a fourth message including the UE policy to the MME, wherein the communications device is a Serving Gateway (S-GW).

[0009] In an aspect of the present disclosure, a method of a communications device receives a first message from a Serving Gateway (S-GW) including information for obtaining a UE policy, sends a second message including the information to a Policy Control Function (PCF), receives a third message from the PCF including the UE policy, and sends a fourth message including the UE policy to the S-GW, wherein the communications device is a Packet Data Network (PDN) Gateway Control plane function (PGW-C) and a Session Management Function (SMF).

[0010] In an aspect of the present disclosure, a method of a communications device receives a first message including information for obtaining a UE policy from a Packet Data Network (PDN) Gateway Control plane function (PGW-C) and a Session Management Function (SMF), sends a second message including the information to a Unified Data Management (UDM) or a Unified Data Repository (UDR), receives a third message including the UE policy from the UDM or the UDR, and sends a fourth message including the UE policy to the PGW-C and the SMF, wherein the communications device is a Policy Control Function (PCF).

[0011] In an aspect of the present disclosure, a User Equipment (UE) includes means for transmitting a first message including information for obtaining a UE policy to a Mobility Management Entity (MME), and means for receiving a second message including the UE policy from the MME.

[0012] In an aspect of the present disclosure, a communications device includes means for receiving a first message from a User Equipment (UE) including information for obtaining a UE policy, means for sending a second message including the information to a Serving Gateway (S-GW), means for receiving a third message from the S-GW including the UE policy, and means for sending a fourth message including the UE policy to the UE, wherein the communications device is a Mobility Management Entity (MME).

[0013] In an aspect of the present disclosure, a communications device includes: means for receiving a first message including information for obtaining a UE policy from a Mobility Management Entity (MME); means for sending a second message including the information to a Packet Data Network (PDN) Gateway Control plane function (PGW-C) and a Session Management Function (SMF); means for receiving a third message including the UE policy from the PGW-C and the SMF; and means for sending a fourth message including the UE policy to the MME, wherein the communications device is a Serving Gateway (S-GW).

[0014] In an aspect of the present disclosure, a communications device includes means for receiving a first message from a Serving Gateway (S-GW) including information for obtaining a UE policy, means for sending a second message including the information to a Policy Control Function (PCF), means for receiving a third message including the UE policy from the PCF, and means for sending a fourth message including the UE policy to the S-GW, wherein the communications device is a Packet Data Network (PDN) Gateway Control plane function (PGW-C) and a Session Management Function (SMF).

[0015] In an aspect of the present disclosure, a communications device includes means for receiving a first message including information for obtaining a UE policy from a Packet Data Network (PDN) Gateway Control plane function (PGW-C) and a Session Management Function (SMF), means for sending a second message including the information to a Unified Data Management (UDM) or a Unified Data Repository (UDR), means for receiving a third message including the UE policy from the UDM or the UDR, and means for sending a fourth message including the UE policy to the PGW-C and the SMF, wherein the communications device is a Policy Control Function (PCF). [Brief explanation of the drawings]

[0016] [Figure 1]FIG. 1 is a diagram illustrating a non-roaming architecture interoperating between 5GS and EPC / E-UTRAN (a non-roaming architecture interoperating between 5GS and EPC / E-UTRAN). [Figure 2] FIG. 2 is a signaling diagram of a first example of the first aspect (UE policy update in EPS during attach procedure). [Figure 3] FIG. 3 is a signaling diagram of a second example of the first aspect (UE policy update in EPS during ESM procedure). [Figure 4] FIG. 4 is a signaling diagram of a third example of the first aspect (UE policy transmission procedure when a UE registers with an EPS). [Figure 5] FIG. 5 is a signaling diagram of a fourth example of the first aspect (EPS UE policy obtained from PCF in 5GS). [Figure 6] FIG. 6 is a diagram showing an outline of the system. [Figure 7] FIG. 7 is a block diagram illustrating a user equipment (UE). [Figure 8] FIG. 8 is a block diagram illustrating an (R)AN node. [Figure 9] FIG. 9 is a diagram illustrating a system overview of an (R)AN node based on the O-RAN architecture. [Figure 10] FIG. 10 is a block diagram showing a radio unit (RU). [Figure 11] FIG. 11 is a block diagram showing a distributed unit (DU). [Figure 12] FIG. 12 is a block diagram showing a centralized unit (CU). [Figure 13] FIG. 13 is a block diagram illustrating the Access and Mobility Management Function (AMF). [Figure 14]FIG. 14 is a block diagram illustrating the Session Management Function (SMF). [Figure 15] FIG. 15 is a block diagram illustrating the User Plane Function (UPF). [Figure 16] FIG. 16 is a block diagram illustrating a Policy Control Function (PCF). [Figure 17] FIG. 17 is a block diagram illustrating the Authentication Server Function (AUSF). [Figure 18] FIG. 18 is a block diagram illustrating Unified Data Management (UDM). [Figure 19] FIG. 19 is a block diagram illustrating the Network Data Analytics Function (NWDAF). [Figure 20] FIG. 20 is a block diagram illustrating the Network Exposure Function (NEF). [Figure 21] FIG. 21 is a block diagram illustrating a Network Slice Admission Control Function (NSACF). DETAILED DESCRIPTION OF THE INVENTION

[0017] <abbreviation> For purposes of this specification, the abbreviations given in Non-Patent Document 1 and the following apply: Abbreviations defined in this specification take precedence over the definition of the same abbreviation in Non-Patent Document 1 if the same abbreviation appears in that document.

[0018] 4G-GUTI 4G Globally Unique Temporary UE Identity 5GC 5G Core Network 5GLAN 5G Local Area Network 5GS 5G System 5G-AN 5G Access Network 5G-AN PDB 5G Access Network Packet Delay Budget 5G-EIR 5G-Equipment Identity Register 5G-GUTI 5G Globally Unique Temporary Identifier 5G-BRG 5G Broadband Residential Gateway 5G-CRG 5G Cable Residential Gateway 5G GM 5G Grand Master 5G-RG 5G Residential Gateway 5G-S-TMSI 5G S-Temporary Mobile Subscription Identifier 5G VN 5G Virtual Network 5QI 5G QoS Identifier AF Application Function AMF Access and Mobility Management Function AMF-G Geographically selected Access and Mobility Management Function AMF-NG Non-Geographically selected Access and Mobility Management Function ANDSF Access Network Discovery and Selection Function AS Access Stratum ATSSS Access Traffic Steering, Switching, Splitting ATSSS-LL ATSSS Low-Layer AUSF Authentication Server Function AUTN Authentication token BCCH Broadcast Control Channel BMCA Best Master Clock Algorithm BSF Binding Support Function CAG Closed Access Group CAPIF Common API Framework for 3GPP northbound APIs CHF Charging Function CN PDB Core Network Packet Delay Budget CP Control Plane DAPS Dual Active Protocol Stacks DL Downlink DN Data Network DNAI DN Access Identifier DNN Data Network Name DRX Discontinuous Reception DS-TT Device-side TSN translator ePDG evolved Packet Data Gateway EBI EPS Bearer Identity EPS Evolved Packet System ESM EPS Session Management EUI Extended Unique Identifier FAR Forwarding Action Rule FN-BRG Fixed Network Broadband RG FN-CRG Fixed Network Cable RG FN-RG Fixed Network RG FQDN Fully Qualified Domain Name GFBR Guaranteed Flow Bit Rate GMLC Gateway Mobile Location Centre GPSI Generic Public Subscription Identifier GUAMI Globally Unique AMF Identifier GUTI Globally Unique Temporary UE Identity HPLMN Home Public Land Mobile Network HR Home Routed (roaming) IAB Integrated access and backhaul IMEI / TAC IMEI Type Allocation Code IPUPS Inter PLMN UP Security I-SMF Intermediate SMF I-UPF Intermediate UPF LADN Local Area Data Network LBO Local Break Out (roaming) LMF Location Management Function LoA Level of Automation LPP LTE Positioning Protocol LRF Location Retrieval Function MCC Mobile country code MCX Mission Critical Service MDBV Maximum Data Burst Volume MFBR Maximum Flow Bit Rate MICO Mobile Initiated Connection Only MITM Man In the Middle MME Mobility Management Entity MNC Mobile Network Code MPS Multimedia Priority Service MPTCP Multi-Path TCP Protocol N3IWF Non-3GPP InterWorking Function N3GPP Non-3GPP access N5CW Non-5G-Capable over WLAN NAI Network Access Identifier NAS Non-Access-Stratum NEF Network Exposure Function NF Network Function NGAP Next Generation Application Protocol NID Network identifier NPN Non-Public Network NR New Radio NRF Network Repository Function NSI ID Network Slice Instance Identifier NSSAA Network Slice-Specific Authentication and Authorization NSSAAF Network Slice-Specific Authentication and Authorization Function NSSAI Network Slice Selection Assistance Information NSSF Network Slice Selection Function NSSP Network Slice Selection Policy NSSRG Network Slice Simultaneous Registration Group NW-TT Network-side TSN translator NWDAF Network Data Analytics Function PCF Policy Control Function PCO Protocol Configuration Options PDB Packet Delay Budget PDR Packet Detection Rule PDU Protocol Data Unit PEI Permanent Equipment Identifier PER Packet Error Rate PFD Packet Flow Description PGW Packet Data Network (PDN) Gateway PGW-C PDN Gateway Control plane function PLMN Public Land Mobile Network PNI-NPN Public Network Integrated Non-Public Network PPD Paging Policy Differentiation PPF Paging Proceed Flag PPI Paging Policy Indicator PSA PDU Session Anchor PTP Precision Time Protocol QFI QoS Flow Identifier QoE Quality of Experience RACS Radio Capabilities Signalling optimisation (R)AN (Radio) Access Network RAT Radio Access Technology RG Residential Gateway RIM Remote Interference Management RQA Reflective QoS Attribute RQI Reflective QoS Indication RSN Redundancy Sequence Number SA NR Standalone New Radio SBA Service Based Architecture SBI Service Based Interface SCP Service Communication Proxy SD Slice Differentiator SEAF Security Anchor Functionality SEPP Security Edge Protection Proxy S-GW Serving Gateway SMF Session Management Function SMSF Short Message Service Function SN Sequence Number SN name Serving Network Name. SNPN Stand-alone Non-Public Network S-NSSAI Single Network Slice Selection Assistance Information SSC Session and Service Continuity SSCMSP Session and Service Continuity Mode Selection Policy SST Slice / Service Type SUCI Subscription Concealed Identifier SUPI Subscription Permanent Identifier SV Software Version TMSI Temporary Mobile Subscriber Identity TNAN Trusted Non-3GPP Access Network TNAP Trusted Non-3GPP Access Point TNGF Trusted Non-3GPP Gateway Function TNL Transport Network Layer TNLA Transport Network Layer Association TSC Time Sensitive Communication TSCAI TSC Assistance Information TSN Time Sensitive Networking TSN GM TSN Grand Master TSP Traffic Steering Policy TT TSN Translator TWIF Trusted WLAN Interworking Function UCMF UE radio Capability Management Function UDM Unified Data Management UDR Unified Data Repository UDSF Unstructured Data Storage Function UE User Equipment UL Uplink UL CL Uplink Classifier UPF User Plane Function UPSI UE Policy Section Identifier URLLC Ultra Reliable Low Latency Communication URRP-AMF UE Reachability Request Parameter for AMF URSP UE Route Selection Policy VID VLAN Identifier VLAN Virtual Local Area Network VPLMN Visited Public Land Mobile Network W-5GAN Wireline 5G Access Network W-5GBAN Wireline BBF Access Network W-5GCAN Wireline 5G Cable Access Network W-AGF Wireline Access Gateway Function

[0019] <Definition> For purposes of this specification, the terms and definitions given in Non-Patent Document 1 and the following apply: Terms defined in this specification take precedence over the definition of the same term in Non-Patent Document 1, if any.

[0020] <General remarks> Those skilled in the art will appreciate that elements in the figures may be shown in simplified form and not necessarily drawn to scale. Furthermore, with respect to the structure of a device, one or more components of the device may be represented by conventional symbols in the figures, and the figures may show only certain details relevant to understanding aspects of the present disclosure so as not to obscure the figures with details that will be readily apparent to those skilled in the art having the benefit of the description herein.

[0021] To promote an understanding of the principles of the present disclosure, reference will now be made to embodiments illustrated in the drawings and specific language will be used to describe those principles. It will nevertheless be understood that no limitation on the scope of the present disclosure is intended thereby. Such alterations and further modifications in the illustrated systems, and such further applications of the principles of the present disclosure as would normally occur to one skilled in the art, are to be construed as being within the scope of the present disclosure.

[0022] The terms "comprises," "comprising," or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method comprising a list of steps not only includes those steps, but may also include other steps not expressly listed or inherent in such process or method. Similarly, the reference to one or more devices, entities, subsystems, elements, structures, or components preceded by "comprises" does not, absent further constraints, preclude the presence of other devices, subsystems, elements, structures, components, additional devices, additional subsystems, additional elements, additional structures, or additional components. Throughout this specification, the phrases "in an embodiment," "in another embodiment," and similar terms may all refer to the same embodiment, but do not necessarily do so.

[0023] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. The systems, methods, and examples provided herein are illustrative only and are not intended to be limiting.

[0024] In the following specification and claims, reference will be made to a number of terms that shall be defined to have the following meanings: The singular forms "a," "an," and "the" include plural references unless the context clearly dictates otherwise.

[0025] As used herein, information refers to data and knowledge, as data is meaningful information and represents values ​​attributed to parameters. Furthermore, knowledge refers to an understanding of an abstract or concrete concept. It should be noted that this exemplary system is simplified to facilitate explanation of the subject matter of the present disclosure and is not intended to limit the scope of the present disclosure. Other devices, systems, and configurations may be used in addition to or instead of the system to implement aspects disclosed herein, and all such aspects are contemplated as being within the scope of the present disclosure.

[0026] Each aspect and elements included in each aspect described below can be implemented independently or in combination with each other, and the aspects include different novel features, and therefore contribute to achieving different objectives or solving different problems and achieving different advantages.

[0027] An exemplary object of the present disclosure is to provide a method and apparatus that can solve the above problems.

[0028] A method for a User Equipment (UE) according to an example aspect of the present disclosure includes transmitting an Attach Request message including information for obtaining a UE policy for the UE, and receiving an Attach Accept message including the UE policy.

[0029] A method of a communications device according to an exemplary aspect of the present disclosure includes receiving an Attach Request message including information for obtaining a UE policy. The method includes transmitting a Create Session Request message including the information. After transmitting the Create Session Request message, the method includes receiving a Create Session Response message including the UE policy. The method includes transmitting an Attach Accept message including the UE policy.

[0030] A method of a communications device according to an exemplary aspect of the present disclosure includes receiving a create session request message including information for obtaining a UE policy. The method includes transmitting the create session request message. The method includes, after transmitting the create session request message, receiving a create session response message including the UE policy. The method includes transmitting the create session response message.

[0031] A method for a communications device according to an exemplary aspect of the present disclosure includes receiving a create session request message including information for obtaining a UE policy, transmitting a first message including the information, receiving a second message including the UE policy after transmitting the first message, and transmitting a third message including the UE policy.

[0032] A method for a communications device according to an exemplary aspect of the present disclosure includes receiving a first message including information for obtaining a UE policy. The method includes transmitting a second message including the information. The method includes, after transmitting the first message, receiving a third message including the UE policy. The method includes transmitting a fourth message including the UE policy.

[0033] A method for a communications device according to an exemplary aspect of the present disclosure includes receiving a first message including information for obtaining a UE policy, obtaining the UE policy, and receiving a second message including the UE policy.

[0034] A method for a communications device according to an exemplary aspect of the present disclosure includes receiving a first message including information for obtaining a UE policy, obtaining the UE policy, and receiving a second message including the UE policy.

[0035] A method for a User Equipment (UE) according to an example aspect of the present disclosure includes transmitting a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy for the UE, and receiving a second EPS SM message including the UE policy.

[0036] A method for a communications device according to an exemplary aspect of the present disclosure includes receiving a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy. The method includes transmitting a second EPS SM message including the information. The method includes, after transmitting the second EPS SM message, receiving a third EPS SM message including the UE policy. The method includes transmitting a fourth EPS SM message including the UE policy.

[0037] A method for a communications device according to an exemplary aspect of the present disclosure includes receiving a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy. The method includes transmitting a second EPS SM message including the information. The method includes, after transmitting the second EPS SM message, receiving a third EPS SM message including the UE policy. The method includes transmitting a fourth EPS SM message including the UE policy.

[0038] A method for a communications device according to an exemplary aspect of the present disclosure includes receiving a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy. The method includes transmitting the first message including the information. The method includes, after transmitting the first message, receiving a second message including the UE policy. The method includes transmitting a second EPS SM message including the UE policy.

[0039] A method for a User Equipment (UE) according to an example aspect of the present disclosure includes transmitting a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy for the UE. The method includes receiving a message including an indicator that the UE policy is pending. The method includes performing cell selection. The method includes performing a registration procedure for a 5G system. The method includes receiving the UE policy after performing the registration procedure.

[0040] A method for a communications device according to an exemplary aspect of the present disclosure includes receiving a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy. The method includes transmitting a second EPS SM message including the information. The method includes, after transmitting the second EPS SM message, receiving a third EPS SM message including an indicator indicating that the UE policy is pending. The method includes transmitting the message including the indicator.

[0041] A communications device method according to an exemplary aspect of the present disclosure includes receiving a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy. The method includes transmitting a second EPS SM message including the information. The method includes, after transmitting the second EPS SM message, receiving a third EPS SM message including an indicator that the UE policy is pending. The method includes transmitting a fourth EPS SM message including the indicator.

[0042] A method for a communications device according to an exemplary aspect of the present disclosure includes receiving a message including an indicator indicating that a UE policy is pending, receiving a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining the UE policy, and transmitting a second EPS SM message including the indicator.

[0043] A method for a communications device according to an exemplary aspect of the present disclosure includes receiving a first message including a UE policy, and transmitting a second message including an indicator that the UE policy is pending.

[0044] A method for a User Equipment (UE) according to an exemplary aspect of the present disclosure includes transmitting a Registration Request message. The Registration Request message includes information indicating that the UE supports receiving a UE policy for an evolved packet system over a 5G system. The method includes receiving the UE policy after transmitting the Registration Request message.

[0045] A method for a communications device according to an exemplary aspect of the present disclosure includes receiving a registration request message from a user equipment (UE). The registration request message includes information indicating that the UE supports receiving a UE policy for an evolved packet system over a 5G system. The method includes transmitting a message including the information. The method includes receiving the UE policy after transmitting the message. The method includes transmitting the UE policy to the UE.

[0046] A method for a communications device according to an exemplary aspect of the present disclosure includes receiving a message, the message including information indicating that a User Equipment (UE) supports receiving a UE policy for an evolved packet system over a 5G system, and transmitting the UE policy after receiving the message.

[0047] A User Equipment (UE) according to an example aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory, the at least one hardware processor configured to transmit an attach request message including information for obtaining a UE policy for the UE, and receive an attach accept message including the UE policy.

[0048] A communications device according to an exemplary aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to receive an attach request message including information for obtaining a UE policy. The at least one hardware processor is configured to transmit a create session request message including the information. After transmitting the create session request message, the at least one hardware processor is configured to receive a create session response message including the UE policy. The at least one hardware processor is configured to transmit an attach accept message including the UE policy.

[0049] A communications device according to an exemplary aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to receive a create session request message including information for obtaining a UE policy. The at least one hardware processor is configured to transmit a create session request message. The at least one hardware processor is configured to receive a create session response message including the UE policy after transmitting the create session request message. The at least one hardware processor is configured to transmit the create session response message.

[0050] A communications device according to an exemplary aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to receive a create session request message including information for obtaining a UE policy. The at least one hardware processor is configured to transmit a first message including the information. After transmitting the first message, the at least one hardware processor is configured to receive a second message including the UE policy. The at least one hardware processor is configured to transmit a third message including the UE policy.

[0051] A communications device according to an exemplary aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to receive a first message including information for obtaining a UE policy. The at least one hardware processor is configured to transmit a second message including the information. The at least one hardware processor is configured to receive a third message including the UE policy after transmitting the first message. The at least one hardware processor is configured to transmit a fourth message including the UE policy.

[0052] A communications apparatus according to an exemplary aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory, wherein the at least one hardware processor is configured to receive a first message including information for obtaining a UE policy, wherein the at least one hardware processor is configured to obtain the UE policy, and wherein the at least one hardware processor is configured to receive a second message including the UE policy.

[0053] A communications apparatus according to an exemplary aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory, wherein the at least one hardware processor is configured to receive a first message including information for obtaining a UE policy, wherein the at least one hardware processor is configured to obtain the UE policy, and wherein the at least one hardware processor is configured to receive a second message including the UE policy.

[0054] A User Equipment (UE) according to an example aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory, the at least one hardware processor configured to transmit a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy for the UE, and the at least one hardware processor configured to receive a second EPS SM message including the UE policy.

[0055] A communications device according to an exemplary aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to receive a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy. The at least one hardware processor is configured to transmit a second EPS SM message including the information. After transmitting the second EPS SM message, the at least one hardware processor is configured to receive a third EPS SM message including the UE policy. The at least one hardware processor is configured to transmit a fourth EPS SM message including the UE policy.

[0056] A communications device according to an exemplary aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to receive a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy. The at least one hardware processor is configured to transmit a second EPS SM message including the information. After transmitting the second EPS SM message, the at least one hardware processor is configured to receive a third EPS SM message including the UE policy. The at least one hardware processor is configured to transmit a fourth EPS SM message including the UE policy.

[0057] A communications device according to an exemplary aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to receive a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy. The at least one hardware processor is configured to transmit the first message including the information. The at least one hardware processor is configured to receive a second message including the UE policy after transmitting the first message. The at least one hardware processor is configured to transmit a second EPS SM message including the UE policy.

[0058] A User Equipment (UE) according to an exemplary embodiment of the present disclosure includes a memory and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to transmit a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy for the UE. The at least one hardware processor is configured to receive a message including an indicator that the UE policy is pending. The at least one hardware processor is configured to perform cell selection. The at least one hardware processor is configured to perform a registration procedure for a 5G system. The at least one hardware processor is configured to receive the UE policy after performing the registration procedure.

[0059] A communications device according to an exemplary aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to receive a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy. The at least one hardware processor is configured to transmit a second EPS SM message including the information. After transmitting the second EPS SM message, the at least one hardware processor is configured to receive a third EPS SM message including an indicator that the UE policy is pending. The at least one hardware processor is configured to transmit the message including the indicator.

[0060] A communications device according to an exemplary aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to receive a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy. The at least one hardware processor is configured to transmit a second EPS SM message including the information. After transmitting the second EPS SM message, the at least one hardware processor is configured to receive a third EPS SM message including an indicator that the UE policy is pending. The at least one hardware processor is configured to transmit a fourth EPS SM message including the indicator.

[0061] A communications apparatus according to an exemplary aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to receive a message including an indicator indicating that a UE policy is pending. The at least one hardware processor is configured to receive a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining the UE policy. The at least one hardware processor is configured to transmit a second EPS SM message including the indicator.

[0062] A communications apparatus according to an exemplary aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory, the at least one hardware processor configured to receive a first message including a UE policy, the at least one hardware processor configured to transmit a second message including an indicator that the UE policy is pending.

[0063] A user equipment (UE) according to an exemplary embodiment of the present disclosure includes a memory and at least one hardware processor connected to the memory. The at least one hardware processor is configured to transmit a registration request message. The registration request message includes information indicating that the UE supports receiving a UE policy for an evolved packet system over a 5G system. The at least one hardware processor is configured to receive the UE policy after transmitting the registration request message.

[0064] A communications device according to an exemplary aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to receive a registration request message from a User Equipment (UE). The registration request message includes information indicating that the UE supports receiving a UE policy for an evolved packet system over a 5G system. The at least one hardware processor is configured to transmit a message including the information. The at least one hardware processor is configured to receive the UE policy after transmitting the message. The at least one hardware processor is configured to transmit the UE policy to the UE.

[0065] A communications device according to an exemplary aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to receive a message. The message includes information indicating that a User Equipment (UE) supports receiving a UE policy for an evolved packet system over a 5G system. The at least one hardware processor is configured to transmit the UE policy after receiving the message.

[0066] A User Equipment (UE) is assumed to be aware of all network slices available in a cell in a VPLMN when the UE is in a CM-IDLE state, a CM-CONNECTED state, or a CM-CONNECTED state with RRC inactivity.

[0067] The UE policy in the following aspects refers to URSP, ANDSP, V2XP, and ProseP. For example, the UE policy in the following aspects may include URSP, ANDSP, V2XP, and ProseP. The UE policy is transmitted in the UE policy section management list information element of the Manage UE Policy command message as defined in Section D.6.2 of Non-Patent Document 11.

[0068] Non-Patent Document 10 defines the use of URSP and ANDSP rules in EPS. In the following aspects, the UE follows the same procedure for using URSP and ANDSP as defined in Non-Patent Document 10.

[0069] In the following aspects, the PCF uses the Nudr_DM_Query service operation (SUPI, Policy Data, UE Context Policy Control Data, Policy Set Entry) to obtain the latest list of policy subscription related information and PSI from the UDR if either or both are not available, and makes policy decisions. If there is a change in the UE's policy in the UDR or UDM, the UDR notifies the PCF about the UE policy change using existing messages between the UDR and the PCF.

[0070] In the following aspects:

[0071] The UPSI list is transferred from the UE to the PCF and is a list of UPSI. This information element is defined in Section D.6.4 of Non-Patent Document 11. The UPSI list may be referred to as a UE policy list in this disclosure.

[0072] The purpose of the UE Policy Classmark information element is to provide the network with information about the UE policy aspects of the UE. This IE is defined in 3GPP TS 36.2(11) section D.6.5.

[0073] The purpose of the UE OS Id information element is to provide the network with information about the UE's OS. The IE is defined in 3GPP TS 36.210.2, section D.6.6.

[0074] If not operating in the SNPN access operation mode, the UE includes in the UPSI list IE the UPSI in the UE policy section identified by the UPSI with a PLMN ID portion indicating the HPLMN or selected PLMN that is available to the UE.

[0075] When operating in the SNPN access mode of operation, the UE: -having a PLMN ID portion indicating the MCC and MNC of the selected SNPN; - Associated with the NID of the selected SNPN, -Available to the UE in the UPSI list IE, Contains the UPSI of the UE policy section identified by the UPSI.

[0076] The UE may specify whether the UE supports ANDSP in the UE Policy Classmark IE, and the UE may include one or more OS IDs of the UE in the UE OS Id IE.

[0077] When the PCF or UDR / UDM receives the UPSI List IE, the PCR or UDM / UDR verifies the UE policy or policies currently stored in the UE based on the UPSI (or UPSI list). If the PCF or UDM / UDR determines that the UE policy stored in the UE is outdated and needs to be changed, the PCF or UDM / UDR sends the UE policy accordingly.

[0078] If the UE policy class mark indicates that the UE supports ANDSP, the PCF or UDR / UDM sends the ANDSP policy to the UE in the UE policy.

[0079] The PCF or UDM / UDR may send a UE policy, e.g., a URSP corresponding to the received OS ID IE. There may be different URSPs or ANDSPs depending on the OS ID. For an Android UE, the PCF sends different URSP rules than a UE with iOS.

[0080] In one example, the UE sends a UE STATE INDICATION message including a UPSI list IE, a UE policy class mark, or an OS ID IE in an attach request message or a PDN connection request. When the MME receives this message, it transparently passes it to the S-GW, which sends it to the SMF-C+PGW-C, which then passes it to the PCF. In one example, the UE STATE INDICATION message is sent in the PCO IE of a PDN connection request message, and the PDN connection request message is passed in the PCO IE to the SMF+PGW-C via the S-GW in an ESM message, for example, a create session request message.

[0081] In one example, the PCF sends a MANAGE UE POLICY COMMAND including a UE policy section management list as defined in 3GPP TS 36.11 to the PGW-C+SMF node, and the PGW-C+SMF node sends the MANAGE UE POLICY COMMAND message to the UE via the S-GW and MME in an existing IE (e.g., PCO) of the existing session management for the UE. When the UE receives the MANAGE UE POLICY COMMAND message, the UE initiates an existing ESM procedure or a new ESM procedure, and the UE sends a MANAGE UE POLICY COMPLETE message or a MANAGE UE POLICY REJECT message to the MME in an existing information element, e.g., PCO, in the existing ESM message or the new ESM message. The MME forwards the IE including the MANAGE UE POLICY COMPLETE or MANAGE UE POLICY REJECT message to the SMF+PGW-C via the S-GW in the existing session management message. When the SMF+PGW-C receives the MANAGE UE POLICY COMPLETE or MANAGE UE POLICY REJECT message, it sends it to the PCF. When the PCF receives the MANAGE UE POLICY COMPLETE, it determines that the UE policy transmission is successful. When the PCF receives the MANAGE UE POLICY REJECT message, it determines that the UE policy update is not successful.

[0082] Figure 1 is a diagram showing a non-roaming architecture interoperating between 5GS and EPC / E-UTRAN. In Figure 1, a telecommunications system 1 includes a UE 3, an E-UTRAN, an NG-RAN, and a core network 7. The core network 7 includes logical nodes (or "functions") that support communication in the telecommunications system 1. More specifically, the core network 7 includes an AMF 70, an SMF+PGW-C (or PGW-C+SMF) 71, a UPF+PGW-U 72, a PCF 73, an HSS+UDM 75, an MME 80, and an SGW (or S-GW) 81. The SMF+PGW-C 71 has the functionality of a PGW-C in the EPC and the functionality of an SMF in 5GC. The UPF+PGW-U 72 has the functionality of a PGW-U in the EPC and the functionality of a UPF in 5GC. HSS+UDM75 has the functions of HSS in EPC and UDM in 5GC.

[0083] The N26 interface is an inter-CN interface between the MME 80 and the 5GS AMF 70 to enable interworking between the EPC and the NG core. Support for the N26 interface in the network is optional for interworking. N26 supports a subset of the functions supported in S10 (which are mandatory for interworking). The PGW-C+SMF 71 and UPF+PGW-U 72 are dedicated to interworking between the 5GS and the EPC and are optional and based on the UE MM core network functions and UE subscription. UEs 3 that do not comply with the interworking between the 5GS and the EPC can be served by entities that are not dedicated to interworking, i.e., either the PGW or the SMF / UPF. There may be another UPF (not shown in FIG. 1) between the NG-RAN and the UPF+PGW-U 72; i.e., the UPF+PGW-U 72 may support N9 to additional UPFs if needed.

[0084] Further details of the architecture shown in FIG. 1 are described in Non-Patent Document 4.

[0085] <First aspect> This aspect discloses a method for transmitting UE policies to a UE 3 when the UE 3 is attached to an EPS.

[0086] <First Example of First Aspect> A first example of the first aspect discloses a method in which the PCF 73 transmits a UE policy to the UE 3 when the UE 3 is attaching to the EPS and a default PDN connection is established during the attach procedure. While the default PDN connection is being established, the PGW-C+SMF 71 transmits a message requesting the PCF 73 to provide the UE policy to the UE 3. The PCF 73 transmits the UE policy to the PGW-C+SMF 71. The PGW-C+SMF 71 transmits the UE policy to the S-GW 81 in an existing GTP-C message or a new GTP-C message. The S-GW 81 transmits the UE policy to the MME 80 in an existing GTP-C message or a new GTP-C message. The MME 80 transmits the UE policy in either an existing EPS Session Management message, a new EPS Session Management message, an existing EPS Mobility Management message, or a new Mobility Management message. The UE policy is transmitted as part of the attach procedure or after the attach procedure when the default PDN connection establishment is completed.

[0087] The detailed process of the first example of the first aspect is as follows. The detailed process is shown in Figure 2. In the following, the UDM 75 may correspond to the HSS+UDM 75 in Figure 1.

[0088] Step 1: The UE 3 initiates an attach procedure to a PLMN by sending an attach request message to the MME 80. The UE 3 includes at least one of a UE policy list, a UE policy class mark, and a UE OS ID information element (IE) in the PDN connection request message or in the attach request message without being in the PDN connection request message. The UE policy list, the UE policy class mark, and the UE OS ID information element (IE) may be configured in a PCO parameter in the attach request message.

[0089] Step 2: Upon receiving the Attach Request message, the MME 80 sends a Create Session Request message to the S-GW 81, including the PCO, the UE state, and at least one of a UE policy list, a UE policy class mark, and a UE OS ID information element (IE). The UE state may be added to the Create Session Request message by the MME 80. The UE state may include the following information:

[0090] CN type: This information indicates the CN type, or core network type, to which the UE 3 is attached or has been attached, for example, EPC or 5GC. Access Type: This information indicates the access that the UE 3 is accessing, for example, 3GPP access or non-3GPP access. RAT type: This information indicates the radio access technology that the UE 3 is accessing, for example, EUTRAN, EUTRAN-NB-IoT, LTE-M, or NR. - Permanent Device Identifier: for example IMEI-SV. The permanent device identifier may be obtained by the MME 80 by the identification request and identification response procedures as defined in 3GPP TS 23.210. -GPSI. -User location information. -UE time zone. Serving network (PLMN ID or PLMN ID and NID).

[0091] In the present disclosure, the MME 80 may determine the UE state based on local information about the UE 3 at the MME 80 or received information about the UE 3 from other network nodes.

[0092] Step 3: Upon receiving the create session request message, S-GW81 sends a create session request message to PGW-C+SMF71, including the PCO, the UE state, and at least one of a UE policy list, a UE policy class mark, and a UE OS ID information element (IE).

[0093] For the contents of the UE state, see step 2 in Figure 2. The PGW-C+SMF 71 may be referred to as a communication device including a PGW-C and an SMF.

[0094] Step 4: Upon receiving the create session request message, the PGW-C+SMF 71 sends an existing message defined between the SMF (e.g., the PGW-C+SMF 71) and the PCF 73, or a new message, e.g., an Npcf_get_UEpolicy request message, including at least one of a policy type, supported S1 modes, supported N1 modes, a UE policy list, a UE policy classmark, a UE OS ID IE, and a UE state. The policy type indicates the type of UE policy that the PGW-C+SMF 71 wants to fetch for the UE 3. If at least one of the UE policy list, the UE policy classmark, and the UE OS ID information element (IE) is encapsulated in the PCO, the PGW-C+SMF 71 extracts at least one of the UE policy list, the UE policy classmark, and the UE OS ID information element (IE) from the PCO.

[0095] In one example, if a policy list is not included in the create session request message, the PGW-C+SMF 71 includes a policy type information element. In the present disclosure, the PGW-C+SMF 71 may determine the policy type information element based on the UE policy list. In the present disclosure, the PGW-C+SMF 71 may determine the policy type information element based on local configuration in the PGW-C+SMF 71 or stored information regarding the policy list of the UE 3.

[0096] Please refer to step 2 in Figure 2 for the contents of the UE state.

[0097] The information "S1 mode supported" may indicate that the UE 3 supports the S1 mode.

[0098] The information "N1 mode supported" may indicate that the UE 3 supports the N1 mode.

[0099] PGW-C+SMF71 may obtain at least one of the "supported S1 modes" and the "supported N1 modes" based on information about UE3 stored in PGW-C+SMF71 or received information about UE3 from other network nodes.

[0100] Step 5: Upon receiving the message from PGW-C+SMF71, PCF73 sends an existing message defined between PCF73 and UDR or UDM75, or a new message including at least one of policy type, supported S1 modes, supported N1 modes, UE policy list, UE policy class mark, UE OS ID, and UE state, for example, a Nudm_get_UEpolicy request message, to UDM75 or UDR.

[0101] Please refer to step 2 in Figure 2 for the contents of the UE state.

[0102] Step 6: Upon receiving the message from the PCF 73, the UDR or UDM 75 forwards the UE policy to the PCF 73 in an existing message between the UDM 75 / UDR and the PCF 73 or in a new message, for example, a Nudm_get_UEpolicy response message.

[0103] In one example, the UDR or UDM 75 sends all UE policies to the PCF 73. For example, the UDR or UDM 75 sends all UE policies for UE3 to the PCF 73.

[0104] In one example, the UDM 75 or UDR transmits a UE policy corresponding to a value defined in a UE policy type IE, a UE policy class mark, or a UE policy list.

[0105] For example, the UDM 75 or the UDR may obtain a UE policy corresponding to a value defined in the UE policy type IE, the UE policy class mark, or the UE policy list, and transmit the UE policy.

[0106] For example, the UDM 75 or UDR may obtain the UE policy based on the values ​​defined in the UE policy classmark or UE policy list in the manner mentioned in the general discussion section.

[0107] For example, the UDM 75 or the UDR may obtain a UE policy corresponding to the policy type. For example, the UDM 75 or the UDR may obtain a UE policy corresponding to a policy type value. The policy type value may be URSP, ANDSP, V2XP, or ProseP, or a combination of policy type values, such as URSP and ANDSP.

[0108] For example, the UDM 75 or UDR may obtain a UE policy appropriate for a UE supporting the S1 mode based on the information "supported S1 mode."

[0109] For example, the UDM 75 or UDR may obtain a UE policy appropriate for a UE supporting the N1 mode based on the information "supported N1 mode."

[0110] For example, the UDM 75 or UDR may obtain the UE policy based on the UE state.

[0111] For example, the UDM 75 or UDR may obtain the appropriate UE policy in the CN indicated by the CN type in the UE state.

[0112] For example, the UDM 75 or UDR may obtain the appropriate UE policy for the access type indicated by the UE state.

[0113] For example, the UDM 75 or UDR may obtain the appropriate UE policy for the RAT type indicated by the UE state.

[0114] For example, the UDM 75 or UDR may obtain the UE policy corresponding to the permanent device identifier indicated by the UE state.

[0115] For example, the UDM 75 or UDR may obtain the UE policy corresponding to the GPSI indicated by the UE state.

[0116] For example, the UDM 75 or UDR may obtain the appropriate UE policy at the location indicated by the user location information in the UE state.

[0117] For example, the UDM 75 or UDR may obtain the appropriate UE policy for the time zone (or time or period) indicated by the UE time zone in the UE state.

[0118] For example, the UDM 75 or UDR may obtain the appropriate UE policy in the network indicated by the serving network in the UE state.

[0119] For example, when the UDM 75 or UDR obtains a UE policy, the UDM 75 or UDR may send the obtained UE policy to the PCF 73.

[0120] Step 7: Upon receiving the UE policy in the response message from the UDM 75 or UDR, the PCF 73 sends an existing message or a new message, for example, an Npcf_get_UEpolicy response message, established between the PCF 73 and the SMF to the PGW-C+SMF 71. The existing message or the new message may include the UE policy.

[0121] Step 8: Upon receiving the UE policy in the response message from the PCF 73, the PGW-C+SMF 71 sends a create session response message including the UE policy to the S-GW 81. The UE policy may be stored in the PCO. The UE policy may be stored in the PCO of the create session response message.

[0122] Step 9: Upon receiving the create session response message, the S-GW81 sends the create session response message to the MME80, including at least one of the PCO and the UE policy.

[0123] Upon receiving the create session response message, the MME 80 performs either step 10a or step 10b.

[0124] Step 10a: The MME 80 sends an Attach Accept message including at least one of the PCO and an Activate Default EPS Bearer Context Request message including the UE policy. If the UE policy is encapsulated in the PCO, the UE 3 extracts the UE policy from the PCO.

[0125] Step 10b: The MME 80 sends an attach accept message including at least one of the PCO, the UE policy, and the activate default EPS bearer context request message.

[0126] Step 11: When the UE 3 receives the UE policy, it applies the UE policy when the UE 3 registers with EPS or when the UE 3 registers with 5GS, as defined in Non-Patent Document 10.

[0127] In the present disclosure, at least one of a policy type, a supported S1 mode, a supported N1 mode, a UE policy list, a UE policy class mark, a UE OS ID IE, and a UE state may be represented as information for obtaining a UE policy.

[0128] According to the above process, for example, a first example of the first aspect may provide a procedure for transmitting a UE policy to a UE when the UE is attached to an EPS.

[0129] <Modification 1 of the first example of the first aspect> A first example of the first aspect may also be performed when the UE 3 performs a tracking area update procedure. In this case, the following substitutions are required in Figure 2: Step 1 is replaced by a TAU request message. Step 10a is replaced with a TAU acknowledgement message. Step 10b is replaced with a TAU acknowledgement message.

[0130] <Modification 2 of the first example of the first aspect> Some messages in the first example of the first aspect may also be performed when the UE policy is updated in the PCF 73. In this case, the following replacements and updates are required in Figure 2. The contents of the replaced messages may be the same as the contents of the messages in Figure 2.

[0131] Step 7 is triggered when the PCF 73 decides to update the UE policy in the UE 3.

[0132] Step 7 is replaced by an existing message defined between the PCF 73 and the SMF, or a new message to the PGW-C+SMF 71, for example, an Npcf_UEPolicyControl_UpdateNotify message.

[0133] Step 8 is replaced by an Update Bearer Request message.

[0134] Step 9 is replaced by an Update Bearer Request message.

[0135] Step 10a is replaced by a Bearer Modify Request message.

[0136] Step 10b is replaced by a Modify Bearer Request message.

[0137] -The following steps are added after step 11:

[0138] Step 12: The UE 3 sends a Bearer Modify Response message to the MME 80 indicating that the UE 3 has successfully updated the UE policy.

[0139] Step 13: Upon receiving the message in step 12, the MME 80 sends an Update Bearer Response message to the S-GW 81.

[0140] --Step 14: Upon receiving the message in step 13, S-GW81 sends an update bearer response message to PGW-C+SMF71.

[0141] <Modification 3 of the first example of the first aspect> In step 1 in FIG. 2, the UE 3 may also indicate its capability to receive and process UE policies, e.g., URSP rules, while the UE 3 is registered with EPS. In this regard, the UE 3 may include a new "UE Policy update in EPS support" parameter in the attach request message to the AMF 70 in step 1. This new parameter may be referred to as "UE Policy update in EPS support" or any other indication of a parameter to indicate the UE 3's capability to receive and process UE policies, e.g., URSP rule updates, at the UE while the UE 3 is registered with EPS. This new "UE Policy update in EPS support" parameter may also be indicated from the UE 3 to the AMF 70 in the RA update procedure or any other NAS message between the UE 3 and the AMF 70. If the UE 3 has included the "UE Policy update in EPS support" parameter in the NAS message to the AMF 70, the AMF 70 obtains the UE policy according to steps 2 to 9 in FIG. 2. Also, if the UE 3 includes the "UE Policy Update in EPS Support" parameter in the NAS message to the AMF 70, the AMF 70 includes the UE policy, i.e., the URSP rule, in the attach accept message to the UE 3 in step 10 in Figure 2. The AMF 70 may also use any of the existing NAS messages, including the UE Configuration Update message, to convey the UE policy to the UE 3. As soon as the UE 3 receives the UE policy, e.g., the URSP rule, from the network, i.e., the AMF 70, the UE 3 stores the UE policy in the UE 3, and the UE 3 starts applying the newly updated UE policy, e.g., the URSP rule.

[0142] It should be noted that in another implementation aspect, the "UE Policy Updates in EPS Support" parameter may be represented as a new "UE Policy Updates in EPS Support" field in the UE Policy Classmark.

[0143] <Modification 4 of the first example of the first aspect> In one example, the UE 3 may not send any of the UE policy list, UE policy class mark, or UE OS ID information element (IE) in the attach request message. In this case, when the PCF 73 or UDM 75 / UDR receives a policy type from the PGW-C+SMF 71, the PCF 73 or UDM 75 / UDR sends a UE policy corresponding to the value in the policy type. The value of the policy type is URSP, ANDSP, V2XP, or ProseP, or a combination of the policy type values, for example, URSP and ANDSP.

[0144] <Second Example of First Aspect> A second example of the first aspect discloses a method in which the UE 3 requests the network to send a UE policy after the UE 3 is successfully attached to the EPS in an ESM message during an ESM procedure, for example, in a PDN connection request message during a standalone PDN connection establishment procedure. Upon receiving a request to download the UE policy from the UE 3, the EPS network requests the PCF 73 to send the UE policy. The PCF 73 sends the UE policy to the EPS, and the EPS responds by sending the UE policy to the UE 3 in an ESM message.

[0145] The detailed process of the second example of the first embodiment is as follows: The detailed process is shown in FIG.

[0146] Step 0. The UE 3 is registered with the EPS network as defined in [8].

[0147] Step 1. The UE 3 initiates an ESM procedure, such as a standalone PDN connection establishment procedure or a UE requested bearer resource allocation procedure. The UE 3 sends a first ESM message, such as a PDN connection request message, including at least one of a UE policy list, a UE policy classmark, and a UE OS ID information element (IE). The UE policy list, the UE policy classmark, and the UE OS ID information element (IE) can be configured in a PCO parameter in the first ESM message.

[0148] Step 2: Upon receiving the first ESM message, the MME 80 sends a second ESM message to the S-GW 81, the second ESM message including the PCO, the UE state, and at least one of a UE policy list, a UE policy class mark, and a UE OS ID information element (IE). The UE state may be added to the second ESM message by the MME 80.

[0149] Please refer to step 2 in Figure 2 for the contents of the UE state.

[0150] Step 3: Upon receiving the second ESM message, S-GW81 sends a third ESM message, for example, a Create Session Request message, to PGW-C+SMF71, including the PCO, the UE state, and at least one of a UE policy list, a UE policy class mark, and a UE OS ID information element (IE).

[0151] Please refer to step 2 in Figure 2 for the contents of the UE state.

[0152] Step 4: The PGW-C+SMF 71 sends an existing message, or a new message, for example, an Npcf_get_UEpolicy request message, that includes at least one of a policy type, supported S1 modes, supported N1 modes, a UE policy list, a UE policy classmark, a UE OS ID IE, and a UE state, that is determined between the SMF and the PCF 73. The policy type indicates the type of UE policy that the PGW-C+SMF 71 wants to fetch for the UE 3. If at least one of the UE policy list, the UE policy classmark, and the UE OS ID information element (IE) is encapsulated in the PCO, the PGW-C+SMF 71 extracts at least one of the UE policy list, the UE policy classmark, and the UE OS ID information element (IE) from the PCO.

[0153] Please refer to step 2 in Figure 2 for the contents of the UE state.

[0154] In one example, if the UE policy list is not included in the third ESM message (eg, a create session request message), the PGW-C+SMF71 includes a policy type information element.

[0155] Step 5: Upon receiving the message from PGW-C+SMF71, PCF73 sends an existing message defined between PCF73 and UDR or UDM75, or a new message including at least one of policy type, supported S1 modes, supported N1 modes, UE policy list, UE policy class mark, UE OS ID, and UE state, for example, a Nudm_get_UEpolicy request message, to UDM75 or UDR.

[0156] Step 6: Upon receiving the message from the PCF 73, the UDR or UDM 75 forwards the UE policy to the PCF 73 in an existing message between the UDM 75 / UDR and the PCF 73 or in a new message, for example, a Nudm_get_UEpolicy response message.

[0157] In one example, the UDR or UDM 75 sends all UE policies to the PCF 73. For example, the UDR or UDM 75 sends all UE policies for UE3 to the PCF 73.

[0158] In one example, the UDM 75 or UDR transmits a UE policy corresponding to a value defined in a UE policy type IE, a UE policy class mark, or a UE policy list.

[0159] For example, the UDM 75 or UDR may obtain and send the UE policy in the same manner as step 6 in FIG.

[0160] Step 7: Upon receiving the UE policy in the response message from the UDM 75 or UDR, the PCF 73 sends an existing message or a new message, for example, an Npcf_get_UEpolicy response message, established between the PCF 73 and the SMF to the PGW-C+SMF 71. The existing message or the new message includes the UE policy.

[0161] Step 8: Upon receiving the UE policy in the response message from the PCF 73, the PGW-C+SMF 71 sends a fourth ESM message, such as a create session response message, including the UE policy to the S-GW 81. The UE policy may be stored in the PCO. The UE policy may be stored in the PCO of the fourth ESM message.

[0162] Step 9: Upon receiving the fourth ESM message, for example, a create session response message, the S-GW 81 sends a fifth ESM message, for example, a create session response message, including a UE policy to the MME 80. The UE policy may be stored in a PCO. The UE policy may be stored in the PCO of the fifth message.

[0163] Step 10: Upon receiving the fifth ESM message, for example, a Create Session Response message, the MME 80 sends a sixth message, for example, an Activate Default EPS Bearer Context Request message, including the UE policy. The UE policy may be stored in the PCO. If the UE policy is encapsulated in the PCO, the UE 3 extracts the UE policy from the PCO.

[0164] Step 11: When the UE 3 receives the UE policy, it applies the UE policy when the UE 3 registers with EPS or when the UE 3 registers with 5GS, as defined in Non-Patent Document 10.

[0165] According to the above process, for example, the second example of the first aspect may provide a procedure for sending a UE policy to UE3 when UE3 is attached to EPS.

[0166] <Modification 1 of the second example of the first aspect> In step 1 in FIG. 3, the UE 3 may also indicate its capability to receive and process UE policies, e.g., URSP rules, while the UE 3 is registered with EPS. In this regard, the UE 3 may include a new “UE Policy Updates in EPS Support” parameter in the first session management message to the AMF 70 in step 1. This new parameter may be referred to as “UE Policy Updates in EPS Support” or any other indication of a parameter to indicate the UE 3's capability to receive and process UE policies, e.g., URSP rule updates, while the UE 3 is registered with EPS. If the UE 3 includes the “UE Policy Updates in EPS Support” parameter in the first session management message to the AMF 70, the AMF 70 obtains the UE policies according to steps 2 to 9 in FIG. 3. Also, if the UE 3 includes the “UE Policy Updates in EPS Support” parameter in the first session management message to the AMF 70 in step 1, the AMF 70 includes the UE policies, i.e., the URSP rules, in the session management message in step 10 of FIG. 3. As soon as the UE 3 receives the UE policy, e.g., the URSP rule, from the network, i.e., the AMF 70, the UE 3 stores the UE policy in the UE 3, and the UE 3 starts applying the newly updated UE policy, e.g., the URSP rule.

[0167] <Modification 2 of the second example of the first aspect> In one example, the UE 3 may not send any of the UE policy list, UE policy class mark, or UE OS ID information element (IE) in the first session management message. In this case, when the PCF 73 or UDM 75 / UDR receives a policy type from the PGW-C+SMF 71, the PCF 73 or UDM 75 / UDR sends a UE policy corresponding to the value in the policy type. The value of the policy type is URSP, ANDSP, V2XP, or ProseP, or a combination of the policy type values, for example, URSP and ANDSP.

[0168] <Third Example of the First Aspect> A third example of the first aspect discloses a method in which the PCF 73 indicates to the PGW-C+SMF 71 that a UE policy update is pending. The PGW-C+SMF 71 sends an indication that a user policy update (e.g., a UE policy update) is pending to the UE 3 in an ESM message via the S-GW 81 and the MME 80. When the UE 3 receives the indication that a user policy update is pending, the UE 3 selects an NG-RAN cell even if the UE 3 meets the cell (re)selection criteria to camp on an E-UTRAN cell connected to EPS. After selecting the NG-RAN cell, the UE 3 registers with 5GS. After successfully registering with 5GS, the PCF 73 sends a UE policy to the UE 3 as defined in Non-Patent Document 11. The UE 3 remains registered with 5GS until the UE 3 receives the UE policy. The UE 3 stores the UE policy and applies the UE policy while the UE 3 is registered with 5GS or EPS. After receiving the UE policy, the UE3 may apply cell reselection criteria, select an E-UTRAN cell to connect to the EPS, register with the EPS, and apply the UE policy in the EPS.

[0169] The detailed process of the third example of the first embodiment is as follows: The detailed process is shown in FIG.

[0170] Step 0. The UE 3 registers (or attaches) to the EPS as defined in Non-Patent Document 8.

[0171] In one example, the UE 3 and the network may follow steps 1 to 6 in the first example of the first aspect.

[0172] Step 1: When UDM 75 decides to update a UE policy (e.g., a UE policy for UE 3), UDM 75 sends an existing message or a new message containing the UE policy between UDM 75 or UDR and PCF 73. UDM 75 may send a Nudm_UEPolicy_update_Notification message containing the UE policy.

[0173] Step 2: When the PCF 73 decides to update the UE policy, for example, when the PCF 73 receives an updated UE policy from the UDM 75, or when the PCF 73 itself decides to update the UE policy based on, for example, the current network conditions or an operator policy, and the UE 3 is registered with the EPS, the PCF 73 sends an existing message or a new message to the PGW-C+SMF 71 including an indicator that a UE policy update is pending. The PCF 73 may determine that the UE 3 is registered with the EPS based on local information about the registration state of the UE 3 or based on received information about the registration state of the UE 3 from other network nodes. The indicator that a UE policy update is pending may be represented as a UE policy pending indicator.

[0174] Step 3. While the PGW-C+SMF 71 stores the UE policy pending indicator for the UE 3, the UE 3 may initiate an ESM procedure, such as a standalone PDN connection establishment procedure or a UE requested bearer resource allocation procedure. The UE 3 sends a first ESM message, such as a PDN connection request message, including at least one of a UE policy list, a UE policy classmark, and a UE OS ID information element (IE). The UE policy list, the UE policy classmark, and the UE OS ID information element (IE) may be set in a PCO parameter in the first ESM message.

[0175] Step 4: Upon receiving the first ESM message, the MME 80 sends a second ESM message to the S-GW 81, the second ESM message including the PCO, the UE state, and at least one of a UE policy list, a UE policy class mark, and a UE OS ID information element (IE). The UE state may be added to the first ESM message by the MME 80.

[0176] Please refer to step 2 in Figure 2 for the contents of the UE state.

[0177] Step 5: Upon receiving the second ESM message, S-GW81 sends a third ESM message, for example, a Create Session Request message, to PGW-C+SMF71, including the PCO, the UE state, and at least one of a UE policy list, a UE policy class mark, and a UE OS ID information element (IE).

[0178] Please refer to step 2 in Figure 2 for the contents of the UE state.

[0179] Step 6: Upon receiving the third ESM message, the PGW-C+SMF71 sends a fourth ESM message, for example, a create session response message, to the S-GW81, including an indicator indicating that the UE policy is pending (e.g., a UE policy pending indicator for UE3). The indicator may be stored in the PCO. The indicator may be stored in the PCO of the fourth ESM message. After the PGW-C+SMF71 sends the third ESM message with the indicator to the S-GW81, the PGW-C+SMF71 may clear (or delete) the indicator for UE3.

[0180] Step 7: Upon receiving the fourth ESM message, e.g., a create session response message, the S-GW 81 sends a fifth ESM message, e.g., a create session response message, including the PCO and an indicator that the UE policy is pending, to the MME 80. Upon receiving the fourth ESM message, the MME 80 performs either step 8a or step 8b.

[0181] Step 8a: Upon receiving the fifth ESM message, e.g., a Create Session Response message, the MME 80 sends a sixth ESM message, e.g., an Activate Default EPS Bearer Context Request message, including the PCO and an indicator that the UE policy is pending. If the indicator is encapsulated in the PCO, the UE 3 extracts the indicator from the PCO. The sixth ESM message may include the UE policy.

[0182] Step 8b: Upon receiving the fifth ESM message, e.g., a Create Session Response message, the MME 80 sends a first EMM message, e.g., a Downlink NAS Transport message, an EMM Information message, or an EMM STATUS message, including the PCO and an indicator indicating that the UE policy is pending. If the indicator is encapsulated in the PCO, the UE 3 extracts the indicator from the PCO. The first EMM message may include the UE policy. The indicator indicating that the UE policy is pending may be represented as an indicator indicating that a user policy update is pending.

[0183] Step 9: If the UE 3 receives an indicator that a user policy update is pending, the UE 3 selects an NG-RAN cell even if the UE 3 meets the cell (re)selection criteria to camp on an E-UTRAN cell connected to the EPS. After selecting the NG-RAN cell, the UE 3 registers with the 5GS. The AMF notifies the PCF 73 that the UE 3 is registered with the 5GS.

[0184] Step 10: The PCF 73 sends a manage UE policy command message to the UE 3, including a UE policy section management list, as defined in Non-Patent Document 11. For example, the PCF 73 may send the manage UE policy command message when the AMF notifies the PCF 73 that the UE 3 is registered with 5GS.

[0185] Step 11: Upon receiving the Manage UE Policy Command message, the UE 3 stores a UE policy section management list, and the UE 3 sends a Manage UE policy complete message to the PCF 73. The UE policy section management list may include UE policies.

[0186] Step 12: After (re)selecting an E-UTRAN cell and performing an attach procedure to the EPS, the UE 3 may apply the UE policy stored in step 11 while the UE 3 is attached to the EPS. For example, the UE 3 may (re)select an E-UTRAN cell after receiving a Manage UE Policy Command message or after sending a Manage UE Policy Complete message, and then the UE 3 may apply the UE policy stored in step 11 while the UE 3 is attached to the EPS.

[0187] According to the above process, for example, the third example of the first aspect may provide a procedure for sending a UE policy to UE3 when UE3 is attached to EPS.

[0188] <Modification 1 of the third example of the first aspect> When the PCF73 receives the Manage UE Policy Complete message from UE3 in step 11, the PCF73 may send an existing message or a new message including an indicator instructing PGW-C+SMF71 to clear the UE policy update pending state for UE3.

[0189] After PGW-C+SMF71 clears the UE policy update pending state for UE3, PGW-C+SMF71 sends an existing message or a new message indicating a response to clear the UE policy update pending state for UE3.

[0190] For example, after PGW-C+SMF71 sends a fourth ESM message including an indicator indicating that UE policy is pending, PGW-C+SMF71 may store state information indicating that UE policy for UE3 is pending. The state information may be represented as a UE policy update pending state for UE3. Then, if PGW-C+SMF71 receives an existing message or a new message including an indicator instructing PGW-C+SMF71 to clear the UE policy update pending state for UE3, PGW-C+SMF71 may clear the UE policy update pending state for UE3.

[0191] <Modification 2 of the third example of the first aspect> In one example, the UE 3 may not send any of the UE policy list, UE policy class mark, or UE OS ID information element (IE) in the first session management message. In this case, when the PCF 73 or UDM 75 / UDR receives a policy type from the PGW-C+SMF 71, the PCF 73 or UDM 75 / UDR sends a UE policy corresponding to the value in the policy type. The value of the policy type is URSP, ANDSP, V2XP, or ProseP, or a combination of the policy type values, for example, URSP and ANDSP.

[0192] <Fourth Example of the First Aspect> A fourth example of the first aspect discloses a method in which the PCF 73 sends EPS-specific UE policies to the UE 3 when the UE 3 registers with 5GS.

[0193] The detailed process of the fourth example of the first aspect is as follows. The detailed process is shown in Figure 5. In the following, each of the new AMF 7001 and the old AMF 7002 may correspond to the AMF 70 in Figure 1.

[0194] Step 1. When UE 3 is camped on an NG-RAN cell, UE 3 may initiate a registration procedure to the cell by sending a registration request message including an EPS-specific UE policy support capability to new AMF 7001. The EPS-specific UE policy support capability indicates that UE 3 supports receiving EPS UE policies via 5GS. The EPS UE policies may be UE policies used in EPS or UE policies for EPS. The EPS UE policies may be referred to as EPS-specific UE policies.

[0195] Step 2: The UE 3 and 5GS perform steps 4 to 21 of the registration procedure defined in Non-Patent Document 5.

[0196] Step 3. The new AMF 7001 sends a create Npcf_UEPolicyControl request including EPS-specific UE policy support capabilities to the PCF 73. The EPS-specific UE policy support capabilities may be represented as an EPS-specific UE policy support capabilities information element.

[0197] Step 4. The PCF 73 stores the EPS-specific UE policy support capability information element. Then, the PCF 73 sends an Npcf_UEPolicyControl create response message to the new AMF 7001. A UE policy pending indicator may be included in the Npcf_UEPolicyControl create response message when the PCF 73 needs to send UE policy information (or UE policy) to the UE 3. The UE policy information may be an EPS-specific UE policy. The UE policy pending indicator may be an indicator that the UE policy (EPS-specific UE policy) is pending.

[0198] If the new AMF7001 receives a UE policy pending indicator, the new AMF7001 does not release the N1 connection because a new NAS message needs to be sent to the UE3 after step 4.

[0199] Please note that if UE3 and new AMF7001 maintain the N1 connection after step 4, the management UE policy command message in step 9 can be sent from new AMF7001 to UE3 without performing step 8, since UE3 will not be in 5GMM-IDLE state.

[0200] Step 5: The UE 3 sends a Registration Complete message to the new AMF 7001.

[0201] Steps 3-4 and step 5 can be performed in any order.

[0202] Steps 6-7: To support UE 3 receiving EPS-specific UE policies via 5GS according to the capabilities received in step 3, PCF 73 determines to send EPS-specific UE policies to UE 3. Then, PCF 73 sends a Namf_Communication_N1N2MessageTransfer service message including the EPS UE policies.

[0203] Step 8: Upon receiving the Namf_Communication_N1N2MessageTransfer service message containing the EPS UE policy, the new AMF 7001 initiates a network initiated service request procedure if the UE 3 is in 5GMM idle state.

[0204] Step 9: The new AMF 7001 sends a Manage UE Policy Command message containing the EPS UE policy to the UE 3.

[0205] Step 10: Upon receiving the Manage UE Policy Command message, the UE 3 stores the EPS UE policy and sends a Manage UE Policy Complete message to the new AMF 7001. The UE 3 uses the EPS UE policy when the UE 3 attaches to the EPS.

[0206] Step 11: Upon receiving the managed UE policy complete message, the new AMF 7001 sends a Namf_Communication_N1MessageNotify message to the PCF 73.

[0207] According to the above process, for example, the fourth example of the first aspect may provide a procedure for transmitting a UE policy (e.g., a UE policy used in EPS) to UE3.

[0208] <First variant of the fourth example of the first aspect> In one example, the registration request message includes an indicator indicating the UE capability to support the UE policy update procedure via EPS. The AMF 70 (e.g., new AMF 7001) sends the indicator to the PCF 73 or UDM 75 or UDR during the registration procedure as defined in Section 4.2.2.2.2.2 of 3GPP TS 23.0101. The PCF 73 or UDM 75 / UDR stores the indicator. When the UE 3 registers with EPS, the PCF 73 or UDR / UDM 75 may trigger a UE policy update using embodiments defined in this disclosure. The indicator is also sent to the PGW-C+SMF 71 during an existing 5GSM procedure, for example, a PDU session establishment procedure, in an existing 5GSM message in an existing information element or a new information element. The PGW-C+SMF 71 sends the indicator to the PCF 73 or UDM 75 or UDR.

[0209] <System Overview> FIG. 6 shows a schematic diagram of a mobile (cellular or wireless) telecommunications system 1 to which the above aspects are applicable.

[0210] The telecommunications system 1 represents an overview of a system capable of end-to-end communication, e.g., UEs 3 (or user equipment, "mobile devices" 3) communicating with other UEs 3 or service servers within a data network 20 via respective (R)AN nodes 5 and a core network 7.

[0211] The (R)AN node 5 supports any radio access, including 5G radio access technology (RAT), E-UTRA radio access technology, Beyond 5G RAT, 6G RAT, and non-3GPP RAT including wireless local area network (WLAN) technology as defined by the Institute of Electrical and Electronics Engineers (IEEE).

[0212] The (R)AN node 5 may be separated into a Radio Unit (RU), a Distributed Unit (DU), and a Centralized Unit (CU). In some aspects, each of the units may be connected to each other to form the (R)AN node 5 by employing an architecture such as that defined by the Open RAN (O-RAN) Alliance, where the above units are referred to as the O-RU, O-DU, and O-CU, respectively.

[0213] The (R)AN node 5 may be separated into control plane functions and user plane functions. Furthermore, multiple user plane functions may be allocated to support communications. In some aspects, user traffic may be distributed across multiple user plane functions, with user traffic in each user plane function being aggregated at both the UE 3 and the (R)AN node 5. This separated architecture may be referred to as "dual connectivity" or "multi-connectivity."

[0214] The (R)AN node 5 may also support communications using satellite access. In some aspects, the (R)AN node 5 may support satellite access and terrestrial access.

[0215] In addition, the (R)AN node 5 may also be referred to as an access node for non-wireless access, including fixed access as defined by the Broadband Forum (BBF) and optical access as defined by the Innovative Optical and Wireless Network (IOWN).

[0216] The core network 7 may include logical nodes (or "functions") that support communications in the telecommunications system 1. For example, the core network 7 may be a 5G Core Network (5GC) that includes, among other functions, control plane functions and user plane functions. Each function in a logical node may be considered a network function. A network function may be provided to another node by adapting a Service Based Architecture (SBA).

[0217] By applying network virtualization technologies such as those defined by the European Telecommunications Standards Institute, Network Functions Virtualization (ETSI NFV), network functions can be deployed as distributed, redundant, stateless, and scalable, providing services from several locations and providing several execution instances at each location.

[0218] The core network 7 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0219] As is known, as a UE 3 moves around the geographic area covered by the telecommunications system 1, the UE 3 may move in and out of areas (i.e., radio cells) served by (R)AN nodes 5. To keep track of the UE 3 and facilitate movement between various (R)AN nodes 5, the core network 7 comprises at least one access and mobility management function (AMF) 70. The AMF 70 communicates with the (R)AN nodes 5 connected to the core network 7. In some core networks, a mobility management entity (MME) or mobility management node for Beyond 5G or a mobility management node for 6G may be used instead of the AMF 70.

[0220] The core network 7 also includes, among other functions, a Session Management Function (SMF) 71, a User Plane Function (UPF) 72, a Policy Control Function (PCF) 73, an Authentication Server Function (AUSF) 74, a Unified Data Management (UDM) 75, a Network Data Analytics Function (NWDAF) 76, a Network Exposure Function (NEF) 77, and a Network Slice Admission Control Function (NSACF) 78. When a UE 3 roams into a visited public land mobile network (VPLMN), the home public land mobile network (HPLMN) of the UE 3 provides the UDM 75 and at least some of the functions of the SMF 71, UPF 72, and PCF 73 to the roaming-out UE 3.

[0221] The UE 3 and each serving (R)AN node 5 are connected via an appropriate air interface (e.g., a so-called "Uu" interface and / or the like). Neighboring (R)AN nodes 5 are connected to each other via appropriate (R)AN node 5-to-(R)AN node interfaces (e.g., a so-called "Xn" interface and / or the like). Each (R)AN node 5 is also connected to nodes in the core network 7 (e.g., so-called core network nodes) via appropriate interfaces (e.g., a so-called "N2" / "N3" interface and / or the like). From the core network 7, a connection is also provided to a data network 20. The data network 20 may be the Internet, a public network, an external network, a private network, or an internal network of a PLMN. If the data network 20 is provided by a PLMN operator or a Mobile Virtual Network Operator (MVNO), IP Multimedia Subsystem (IMS) services may be provided by that data network 20. The UE 3 may be connected to the data network 20 using IPv4, IPv6, IPv4v6, Ethernet, or unstructured data types.

[0222] The "Uu" interface may include a control plane of the Uu interface and a user plane of the Uu interface.

[0223] The user plane of the Uu interface is responsible for carrying user traffic between the UE 3 and the serving (R)AN node 5. The user plane of the Uu interface may have a layered structure with SDAP, PDCP, RLC, and MAC sublayers over the physical connection.

[0224] The control plane of the Uu interface is responsible for establishing, modifying, and releasing the connection between the UE 3 and the serving (R)AN node 5. The control plane of the Uu interface may have a hierarchical structure with RRC, PDCP, RLC, and MAC sublayers depending on the physical connection.

[0225] For example, the following messages are communicated in the RRC layer to support AS signaling:

[0226] RRC Setup Request message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together in the RRC Setup Request message: --establishmentCause and ue-Identity. The ue-Identity may have the value of ng-5G-S-TMSI-Part1 or a random value.

[0227] RRC Setup message: This message is sent from the (R)AN node 5 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together in the RRC Setup message: --Master cell group (masterCellGroup) and radio bearer configuration (radioBearerConfig)

[0228] - RRC Setup Complete message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together in the RRC Setup Complete message: --guami type (guami-Type), iab node indication (iab-NodeIndication), idle measurement available (idleMeasAvailable), mobility state (mobilityState), ng-5G-S-TMSI-Part2 (ng-5G-S-TMSI-Part2), registered AMF (registeredAMF), selected PLMN identity (selectedPLMN-Identity)

[0229] The UE 3 and the AMF 70 are connected via an appropriate interface (e.g., a so-called N1 interface and / or the like). The N1 interface is responsible for providing communication between the UE 3 and the AMF 70 to support NAS signaling. The N1 interface can be established in 3GPP access and non-3GPP access. For example, the following messages are communicated on the N1 interface:

[0230] Registration Request Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together in the registration request message: --5GS registration type, ngKSI, 5GS mobile identity, Non-current native NAS key set identifier, 5GMM capability, UE security capability, Requested NSSAI, Last visited registered TAI, S1 UE network capability, Uplink data status, PDU session status, MICO indication, UE status, Additional GUTI, Allowed PDU session status, UE's usage setting, Requested DRX parameters, EPS NAS message container, LADN indication, Payload container type, Payload container container, Network slicing indication, 5GS update type, Mobile station classmark 2, Supported codecs, NAS message container, EPS bearer context status, Requested extended DRX parameters, T3324 value, UE radio capability IDID), Requested mapped NSSAI, Additional information requested, Requested WUS assistance information, N5GC indication, and Requested NB-N1 mode DRX parameters.

[0231] Registration Accept Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together in the registration accept message: --5GS registration result, 5G-GUTI, Equivalent PLMNs, TAI list, Allowed NSSAI, Rejected NSSAI, Configured NSSAI, 5GS network feature support, PDU session status, PDU session reactivation result, PDU session reactivation result error cause, LADN information, MICO indication, Network slicing indication, Service area list, T3512 value, Non-3GPP de-registration timer value, T3502 value, Emergency number list list, Extended emergency number list, SOR transparent container, EAP message, NSSAI inclusion mode, Operator-defined access category definitions, Negotiated DRX parameters, Non-3GPP NW policies, EPS bearer context status, Negotiated extended DRX parameters, T3447 value, T3448 valuevalue, T3324 value, UE radio capability ID, UE radio capability ID deletion indication, Pending NSSAI, Ciphering key data, CAG information list, Truncated 5G-S-TMSI configuration, Negotiated WUS assistance information, Negotiated NB-N1 mode DRX parameters, and Extended rejected NSSAI.

[0232] Registration Complete message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together in the Registration Complete message: --SOR transparent container.

[0233] -Authentication Request message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together in the Authentication Request message: --ngKSI, ABBA, Authentication parameter RAND (5G authentication challenge), Authentication parameter AUTN (5G authentication challenge), and EAP message.

[0234] Authentication Response message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the authentication response message: Authentication response message identity, authentication response parameters, and EAP message.

[0235] -Authentication Result message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the Authentication Result message: --ngKSI, EAP message, and ABBA.

[0236] -Authentication Failure message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the authentication failure message: --Authentication failure message identity, 5GMM cause, and authentication failure parameter.

[0237] -Authentication Reject message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the authentication reject message: --EAP message.

[0238] - Service Request message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the Service Request message: --ngKSI, Service type, 5G-S-TMSI, Uplink data status, PDU session status, Allowed PDU session status, NAS message container.

[0239] - Service Accept message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the Service Accept message: --PDU session status, PDU session reactivation result, PDU session reactivation result error cause, EAP message, and T3448 value.

[0240] - Service Reject message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the Service Reject message: --5GMM cause, PDU session status, T3346 value, EAP message, T3448 value, and CAG information list.

[0241] -Configuration Update Command message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the Configuration Update Command message: --Configuration update indication, 5G-GUTI, TAI list, Allowed NSSAI, Service area list, Full name for network, Short name for network, Local time zone, Universal time and local time zone, Network daylight saving time, LADN information, MICO indication, Network slicing indication, Configured NSSAI, Rejected NSSAI, Operator-defined access category definitions, SMS indication, T3447 value, CAG information list, UE radio capability ID, UE radio capability ID deletion indication indication, 5GS registration result, Truncated 5G-S-TMSI configuration, Additional configuration indication, and Extended rejected NSSAI.

[0242] -Configuration Update Complete message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the Configuration Update Complete message: --Configuration update complete message identity.

[0243] <User equipment (UE)> FIG. 7 is a block diagram illustrating the main components of a mobile device 3 (UE 3). As shown, the UE 3 includes a transceiver circuit 31 operable to transmit signals to and receive signals from a connection node via one or more antennas 32. The UE 3 may also include a user interface 34 for inputting and outputting information from an external device. Although not necessarily illustrated, the UE 3 may have all the usual functions of a conventional mobile device, which may be provided by any one or any combination of hardware, software, and firmware, as needed. For example, the software may be pre-installed in memory and / or downloaded via a telecommunications network or from a removable data storage device (RMD). The controller 33 controls the operation of the UE 3 in accordance with software stored in the memory 36. The software includes, among other things, an operating system 361 and a communication control module 362 having at least a transceiver control module 3621. The communications control module 362 (using its transceiver control module 3621) is responsible for handling (generating / sending / receiving) signaling and uplink / downlink data packets between the UE 3 and other nodes, such as the (R)AN node 5 and the AMF 70. Such signaling may include, for example, appropriately formatted signaling messages (e.g., registration request messages and associated response messages) related to access and mobility management procedures (for the UE 3). The controller 33 interacts with one or more Universal Subscriber Identity Modules (USIMs) 35. In the case of multiple USIMs 35, the controller 33 may activate only one USIM 35 or may activate multiple USIMs 35 simultaneously.

[0244] The UE 3 may, for example, support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0245] UE3 may be, for example, an item of production or manufacturing equipment and / or an item of energy-related machinery (e.g., equipment or machinery such as boilers, engines, turbines, solar panels, wind turbines, hydroelectric generators, thermal generators, nuclear generators, batteries, nuclear systems and / or related equipment, heavy electrical machinery, pumps including vacuum pumps, compressors, fans, blowers, hydraulic equipment, pneumatic equipment, metalworking machinery, manipulators, robots and / or application systems thereof, tools, molds or dies, rolls, conveying equipment, lifting equipment, material handling equipment, textile machinery, sewing machinery, printing machinery and / or related machinery, paper converting machinery, chemical machinery, mining machinery and / or construction machinery and / or related equipment, agricultural, forestry, and / or fishing machinery and / or implements, safety and / or environmental protection equipment, tractors, precision bearings, chains, gears, power transmission equipment, lubrication equipment, valves, fittings, and / or application systems for any of the foregoing equipment or machines).

[0246] UE 3 may be, for example, an item of transportation equipment (e.g., vehicles, automobiles, motorcycles, bicycles, trains, buses, carts, rickshaws, ships and other watercraft, aircraft, rockets, satellites, drones, balloons, etc.).

[0247] The UE 3 may be, for example, an item of information and communications equipment (eg, information and communications equipment such as electronic computers and related equipment, communications and related equipment, electronic components, etc.).

[0248] The UE3 may be, for example, a refrigeration machine, a refrigeration machine application product, an item of commercial and / or service industry equipment, a vending machine, an automated service machine, an office machine or device, a consumer electronic device and appliance (e.g., consumer electronic appliances such as audio equipment, video equipment, loudspeakers, radios, televisions, microwave ovens, rice cookers, coffee machines, dishwashers, washing machines, dryers, electronic fans or related appliances, vacuum cleaners, etc.).

[0249] The UE 3 may be, for example, an electrical application system or device (eg, an electrical application system or device such as an x-ray system, a particle accelerator, a radioisotope device, a sonic device, an electromagnetic application device, a power application device, etc.).

[0250] The UE3 may be, for example, an electronic lamp, a lighting fixture, a measuring instrument, an analyzer, a tester, or a surveying or detecting device (e.g., a smoke alarm, a occupancy alarm sensor, a motion sensor, a radio tag, or other surveying or detecting device), a watch or wall clock, laboratory equipment, optical equipment, medical equipment and / or systems, a weapon, an item of cutlery, a hand tool, or the like.

[0251] UE 3 may be, for example, a wireless-equipped personal digital assistant or related equipment (such as a wireless card or module designed to be attached to or inserted into another electronic device (eg, a personal computer, electrical measuring machine)).

[0252] The UE 3 may be part of a device or system that uses various wired and / or wireless communication technologies to provide the applications, services, and solutions described below with respect to the "Internet of Things (IoT)."

[0253] Internet of Things devices (or "Things") may be equipped with appropriate electronics, software, sensors, network connectivity, and / or the like, allowing them to collect and exchange data with each other and with other communicating devices. IoT devices may comprise autonomous machines that follow software instructions stored in internal memory. IoT devices may operate without the need for human supervision or interaction. IoT devices may also remain stationary and / or idle for long periods of time. IoT devices may be implemented as part of (generally) stationary equipment. IoT devices may also be incorporated into non-stationary equipment (e.g., vehicles) or attached to animals or people being monitored / tracked.

[0254] It will be understood that IoT technology may be implemented on any communication device that can connect to a communication network to transmit / receive data, whether such communication device is controlled by human input or by software instructions stored in memory.

[0255] It will be appreciated that an IoT device is sometimes referred to as a Machine-Type Communication (MTC) device or a Machine-to-Machine (M2M) communication device, or a Narrow Band-IoT UE (NB-IoT UE). It will be appreciated that a UE 3 may support one or more IoT or MTC applications.

[0256] The UE 3 may be a smartphone or a wearable device (e.g., smart glasses, a smart watch, a smart ring, or a hearable device).

[0257] The UE3 may be a car, a connected car, an autonomous vehicle, a vehicle device, a motorcycle, or a Vehicle to Everything (V2X) communication module (e.g., a vehicle-to-vehicle communication module, a vehicle-to-infrastructure communication module, a vehicle-to-person communication module, and a vehicle-to-network communication module).

[0258] <(R)AN node> FIG. 8 is a block diagram illustrating the main components of an exemplary (R)AN node 5, e.g., a base station (eNB in ​​LTE, gNB in ​​5G, a base station for Beyond 5G, or a base station for 6G). As shown, the (R)AN node 5 includes transceiver circuitry 51 operable to transmit signals to and receive signals from connected UEs 3 via one or more antennas 52, and to transmit signals to and receive signals from other network nodes (directly or indirectly) via a network interface 53. A controller 54 controls operation of the (R)AN node 5 according to software stored in memory 55. For example, the software may be pre-installed in the memory and / or downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 551 and a communications control module 552 having at least a transceiver control module 5521.

[0259] The communication control module 552 (using its transceiver control sub-module) is responsible for processing (generating / sending / receiving) signaling between the (R)AN node 5 and other nodes such as the UE 3, another (R)AN node 5, the AMF 70, and the UPF 72, either directly or indirectly. The signaling may include, for example, properly formatted signaling messages (such as RRC connection establishment messages and other RRC messages), NG Application Protocol (NGAP) messages (i.e., messages at the N2 reference point), Xn Application Protocol (XnAP) messages (i.e., messages at the Xn reference point), etc., regarding the radio connection and connection to the core network 7 for a specific UE 3, particularly regarding connection establishment and maintenance. Such signaling may also include, in the case of transmission, for example, broadcast information (such as master information and system information).

[0260] When implemented, the controller 54 is also configured (by software or hardware) to handle related tasks such as UE mobility estimation and / or movement trajectory estimation.

[0261] (R)AN node 5 may support a Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0262] <System Overview of (R)AN Node Based on O-RAN Architecture> FIG. 9 schematically shows the (R)AN node 5 based on the O-RAN architecture to which the (R)AN node 5 aspect is applicable.

[0263] The (R)AN node 5 based on the O-RAN architecture represents a system overview in which the (R)AN node is separated into a Radio Unit (RU) 60, a Distributed Unit (DU) 61, and a Centralized Unit (CU) 62. In some aspects, each unit may be combined. For example, the RU 60 may be combined with the DU 61 as a combiner / combiner, and the DU 61 may be combined with the CU 62 as another combiner / combiner. Any functionality described for a unit (e.g., one of the RU 60, DU 61, and CU 62) may be implemented in the combiner / combiner. Furthermore, the CU 62 may be separated into two functional units, such as a CU Control plane (CP) and a CU User plane (UP). The CU CP has a control plane function in the (R)AN node 5. The CU UP has a user plane function in the (R)AN node 5. Each CU CP is connected to a CU UP via an appropriate interface (such as a so-called "E1" interface and / or the like).

[0264] The UE 3 and each serving RU 60 are connected via an appropriate air interface (e.g., a so-called "Uu" interface and / or the like). Each RU 60 is connected to a DU 61 via an appropriate interface (such as a so-called "fronthaul", "open fronthaul", "F1" interface, and / or the like). Each DU 61 is connected to a CU 62 via an appropriate interface (such as a so-called "midhaul", "open midhaul", "E2" interface, and / or the like). Each CU 62 is also connected to a node in the core network 7 (such as a so-called core network node) via an appropriate interface (such as a so-called "backhaul", "open backhaul", "N2" / "N3" interface, and / or the like). In addition, the user plane part of the DU 61 may also be connected to the core network node 7 via an appropriate interface (such as a so-called "N3" interface and / or the like).

[0265] Depending on the functionality split between the RU 60, DU 61, and CU 62, each unit provides a portion of the functionality provided by the (R)AN node 5. For example, the RU 60 may provide functionality for communicating with the UE 3 over the air interface, the DU 61 may provide functionality supporting the MAC and RLC layers, and the CU 62 may provide functionality supporting the PDCP, SDAP, and RRC layers.

[0266] <Radio Unit (RU)> FIG. 10 is a block diagram illustrating the main components of an exemplary RU 60, e.g., the RU portion of a base station (eNB in ​​LTE, gNB in ​​5G, Beyond 5G base station, 6G base station). As shown, the RU 60 includes a transceiver circuit 601 operable to transmit signals to and receive signals from an attached UE 3 via one or more antennas 602, and to transmit and receive signals to and from other network nodes or network portions via a network interface 603 (directly or indirectly). A controller 604 controls the operation of the RU 60 according to software stored in memory 605. For example, the software may be pre-installed in the memory and / or downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 6051 and a communications control module 6052 having at least a transceiver control module 60521.

[0267] The communications control module 6052 (using its transceiver control sub-module) is responsible for handling (generating / sending / receiving) signaling between (e.g., directly or indirectly) the RU 60 and other nodes or units, such as the UE 3, another RU 60, and the DU 61. The signaling may include, for example, appropriately formatted signaling messages relating to the radio connection and connectivity with the RU 60 (for a particular UE 3), in particular the MAC and RLC layers.

[0268] When implemented, the controller 604 is also configured (by software or hardware) to handle related tasks such as UE mobility estimation and / or motion trajectory estimation.

[0269] The RU 60 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0270] As described above, the RU 60 may be integrated / combined with the DU 61 as an integration / combination unit. Any function described for the RU 60 may be implemented in the integration / combination unit.

[0271] <Distributed Unit (DU)> FIG. 11 is a block diagram illustrating the main components of an exemplary DU 61, e.g., the DU portion of a base station (eNB in ​​LTE, gNB in ​​5G, a base station for Beyond 5G, or a base station for 6G). As shown, the device includes a transceiver circuit 611 operable to transmit signals to and receive signals from other nodes or units (including RU 60) via a network interface 612. A controller 613 controls the operation of the DU 61 in accordance with software stored in memory 614. For example, the software may be pre-installed in memory 614 and / or downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 6141 and a communication control module 6142 having at least a transceiver control module 61421. The communication control module 6142 (using its transceiver control module 61421) is responsible for handling (generating / sending / receiving) signaling between the DU 61 and other nodes or units, such as the RU 60 and other nodes and units.

[0272] The DU 61 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0273] As mentioned above, the RU 60 may be integrated / combined with the DU 61 or the CU 62 as an integrated / combined unit. Any functionality described for the DU 61 may be implemented in one of the integrated / combined units.

[0274] <Centralized Unit (CU)> FIG. 12 is a block diagram illustrating the main components of an exemplary CU 62, e.g., the CU portion of a base station (eNB in ​​LTE, gNB in ​​5G, a base station for Beyond 5G, or a base station for 6G). As shown, the device includes a transceiver circuit 621 operable to transmit signals to and receive signals from other nodes or units (including the DU 61) via a network interface 622. A controller 623 controls the operation of the CU 62 according to software stored in memory 624. For example, the software may be pre-installed in the memory 624 and / or downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 6241 and a communications control module 6242 having at least a transceiver control module 62421. The communication control module 6242 (using its transceiver control module 62421) is responsible for handling (generating / sending / receiving) signaling between the CU 62 and other nodes or units, such as the DU 61 and other nodes and units.

[0275] CU 62 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0276] As described above, the CU 62 may be integrated / combined with the DU 61 as an integration / combination unit. Any functionality described for the CU 62 may be implemented in the integration / combination unit.

[0277] <amf> 13 is a block diagram illustrating the main components of the AMF 70. As shown, the device includes a transceiver circuit 701 operable to transmit signals to and receive signals from other nodes (including UE 3) via a network interface 702. A controller 703 controls the operation of the AMF 70 in accordance with software stored in memory 704. For example, the software may be pre-installed in the memory 704 and / or downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 7041 and a communications control module 7042 having at least a transceiver control module 70421. The communications control module 7042 (using its transceiver control module 70421) is responsible for handling (generating / sending / receiving) signaling between the AMF 70 and other nodes, such as the UE 3 (e.g., via (R)AN node 5) and other nodes, such as other core network nodes (including core network nodes in the UE 3's HPLMN when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (e.g., registration request messages and associated response messages) relating to access and mobility management procedures (for the UE 3).

[0278] The AMF 70 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0279] The new AMF7001 may have the same components as the AMF70. The old AMF7002 may have the same components as the AMF70.

[0280] <smf> 14 is a block diagram illustrating the major components of the SMF 71. As shown, the device includes a transceiver circuit 711 operable to transmit signals to and receive signals from other nodes (including the AMF 70) via a network interface 712. A controller 713 controls the operation of the SMF 71 in accordance with software stored in memory 714. For example, the software may be pre-installed in the memory 714 and / or downloaded via a telecommunications network or from a removable memory device (RMD). The software includes, among other things, an operating system 7141 and a communications control module 7142 having at least a transceiver control module 71421. The communications control module 7142 (using its transceiver control module 71421) is responsible for handling (generating / sending / receiving) signaling between the SMF 71 and other nodes, such as the UPF 72 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (e.g., Hypertext Transfer Protocol (HTTP) RESTful methods based on service-based interfaces) relating to session management procedures (for the UE 3).

[0281] The SMF 71 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0282] <upf> 15 is a block diagram illustrating the major components of the UPF 72. As shown, the device includes a transceiver circuit 721 operable to transmit signals to and receive signals from other nodes (including the SMF 71) via a network interface 722. A controller 723 controls the operation of the UPF 72 in accordance with software stored in memory 724. For example, the software may be pre-installed in the memory 724 and / or downloaded via a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes, among other things, an operating system 7241 and a communications control module 7242 having at least a transceiver control module 72421. The communications control module 7242 (using its transceiver control module 72421) is responsible for handling (generating / sending / receiving) signaling between the UPF 72 and other nodes, such as the SMF 71 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (e.g., GPRS Tunneling Protocol (GTP) for the user plane) related to user data processing (for the UE 3).

[0283] The UPF 72 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0284] <pcf> 16 is a block diagram illustrating the main components of the PCF 73. As shown, the device includes a transceiver circuit 731 operable to transmit signals to and receive signals from other nodes (including the AMF 70) via a network interface 732. A controller 733 controls the operation of the PCF 73 in accordance with software stored in memory 734. For example, the software may be pre-installed in the memory 734 and / or downloaded via a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes, among other things, an operating system 7341 and a communications control module 7342 having at least a transceiver control module 73421. The communications control module 7342 (using its transceiver control module 73421) is responsible for handling (generating / sending / receiving) signaling between the PCF 73 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the UE 3's HPLMN when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP RESTful methods based on service-based interfaces) relating to policy management procedures (for the UE 3).

[0285] The PCF 73 may support a Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The PCF 7301 and PCF 7302 may have the same components as the PCF 73.

[0286] <ausf> 17 is a block diagram illustrating the major components of the AUSF 74. As shown, the device includes a transceiver circuit 741 operable to transmit signals to and receive signals from other nodes (including UDMs 75) via a network interface 742. A controller 743 controls the operation of the AUSF 74 in accordance with software stored in memory 744. For example, the software may be pre-installed in memory 744 and / or downloaded via a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes, among other things, an operating system 7441 and a communications control module 7442 having at least a transceiver control module 74421. The communications control module 7442 (using its transceiver control module 74421) is responsible for handling (generating / sending / receiving) signaling between the AUSF 74 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the UE 3's HPLMN when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP RESTful methods based on service-based interfaces) relating to policy management procedures (for the UE 3).

[0287] The AUSF 74 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0288] <udm> 18 is a block diagram illustrating the major components of the UDM 75. As shown, the device includes a transceiver circuit 751 operable to transmit signals to and receive signals from other nodes (including the AMF 70) via a network interface 752. A controller 753 controls the operation of the UDM 75 in accordance with software stored in memory 754. For example, the software may be pre-installed in memory 754 and / or downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 7541 and a communications control module 7542 having at least a transceiver control module 75421. The communications control module 7542 (using its transceiver control module 75421) is responsible for handling (generating / sending / receiving) signaling between the UDM 75 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the UE 3's VPLMN when the UE 3 is roaming out). Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP RESTful methods based on service-based interfaces) relating to mobility management procedures (for the UE 3).

[0289] The UDM 75 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0290] <nwdaf> 19 is a block diagram illustrating the major components of the NWDAF 76. As shown, the device includes a transceiver circuit 761 operable to transmit signals to and receive signals from other nodes (including the AMF 70) via a network interface 762. A controller 763 controls the operation of the NWDAF 76 according to software stored in memory 764. For example, the software may be pre-installed in memory 764 and / or downloaded via a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes, among other things, an operating system 7641 and a communications control module 7642 having at least a transceiver control module 76421. The communications control module 7642 (using its transceiver control module 76421) is responsible for handling (generating / sending / receiving) signaling between the NWDAF 76 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the UE 3's HPLMN when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP RESTful methods based on service-based interfaces) related to network data analysis function procedures (for the UE 3).

[0291] The NWDAF 76 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0292] <nef> 20 is a block diagram illustrating the major components of the NEF 77. As shown, the device includes a transceiver circuit 771 operable to transmit signals to and receive signals from other nodes (including the UDM 75) via a network interface 772. A controller 773 controls the operation of the NEF 77 in accordance with software stored in memory 774. For example, the software may be pre-installed in memory 774 and / or downloaded over a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes, among other things, an operating system 7741 and a communications control module 7742 having at least a transceiver control module 77421. The communications control module 7742 (using its transceiver control module 77421) is responsible for handling (generating / sending / receiving) signaling between the NEF 77 and other nodes, such as the UDM 75 and other core network nodes (including core network nodes in the UE 3's HPLMN when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP RESTful methods based on service-based interfaces) related to network exposure function procedures (for the UE 3).

[0293] The NEF 77 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0294] <nsacf> 21 is a block diagram illustrating the major components of the NSACF 78. As shown, the device includes a transceiver circuit 781 operable to transmit signals to and receive signals from other nodes (including the AMF 70) via a network interface 782. A controller 783 controls the operation of the NSACF 78 in accordance with software stored in memory 784. For example, the software may be pre-installed in the memory 784 and / or downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 7841 and a communications control module 7842 having at least a transceiver control module 78421. The communications control module 7842 (using its transceiver control module 78421) is responsible for handling (generating / sending / receiving) signaling between the NSACF 78 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the UE 3's HPLMN when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP RESTful methods based on service-based interfaces) relating to network data analysis function procedures (for the UE 3).

[0295] The NSACF 78 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0296] <Other core network nodes> The PGW-C+SMF71 may have the same components as the SMF71 in FIG.

[0297] The UPF+PGW-U 72 may have the same components as the UPF 72 in FIG.

[0298] The HSS+UDM 75 may have the same components as the UDM 75 in FIG.

[0299] The MME 80 may have the same components as the AMF 70 in FIG. 13 or the SMF 71 in FIG.

[0300] The S-GW 81 may have the same components as the AMF 70 in FIG. 13, the SMF 71 in FIG. 14, or the UPF 72 in FIG.

[0301] <Modifications and Replacements> Detailed embodiments have been described above. Still, those skilled in the art will appreciate that numerous modifications and alternatives may be made to the above embodiments while having the benefit of the disclosure embodied herein. By way of example only, many such alternatives and modifications are now described.

[0302] In the above description, the UE 3 and network devices are described for ease of understanding as having a number of separate modules (such as a communications control module). These modules may be provided in this manner for particular applications, for example, where an existing system is modified to implement the present disclosure; in other applications, for example, in a system designed with inventive features in mind from the beginning; however, these modules may not be recognizable as separate entities because they may be built into an overall operating system or code. These modules may also be implemented in software, hardware, firmware, or a mixture of these.

[0303] Each controller may comprise any suitable form of processing circuitry, including, but not limited to, one or more hardware-implemented computer processors, microprocessors, central processing units (CPUs), arithmetic logic units (ALUs), input / output (IO) circuitry, internal memory / cache (program and / or data), processing registers, communication buses (e.g., control buses, data buses, and / or address buses), direct memory access (DMA) functions, hardware or software-implemented counters, pointers, and / or timers, and / or the like.

[0304] In the above embodiments, a number of software modules have been described. Those skilled in the art will understand that the software modules may be provided in compiled or uncompiled form, and may be provided to the UE 3 and network devices as signals over a computer network or on a recording medium. Furthermore, the functions performed by some or all of the software may be performed using one or more dedicated hardware circuits. However, the use of software modules is preferred for updating the functions of the UE 3 and network devices, as they facilitate updating the UE 3 and network devices.

[0305] In the above embodiment, 3GPP wireless communication (radio access) technology is used, but any other wireless communication technology (e.g., WLAN, Wi-Fi, WiMAX, Bluetooth, etc.) and other fixed line communication technology (e.g., BBF access, cable access, optical access, etc.) can also be used in accordance with the above embodiment.

[0306] Items of user equipment may include, for example, communication devices such as mobile phones, smartphones, user devices, personal digital assistants, laptop / tablet computers, web browsers, e-book readers, and / or the like. Such mobile (and even generally fixed) devices are typically operated by a user, although so-called "Internet of Things" (IoT) devices and similar machine-type communication (MTC) devices may also be connected to the network. For simplicity, this application will refer to mobile devices (or UEs) in the description, but it will be understood that the described techniques may be implemented on any (mobile and / or generally fixed) communication device that can connect to a communication network to transmit / receive data, regardless of whether such communication device is controlled by human input or by software instructions stored in memory.

[0307] Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.

[0308] As will be appreciated by those skilled in the art, the present disclosure may be embodied as a method and a system, and thus may take the form of an entirely hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects.

[0309] It will be understood that each block of the block diagrams can be implemented by computer program instructions. The computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to create a machine, such that the instructions, executed by the processor of the computer or other programmable data processing apparatus, create means for implementing the function / acts specified in the block or blocks of the flowcharts and / or block diagrams. A general-purpose processor can be a microprocessor, but alternatively, the processor can be any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, e.g., multiple microprocessors, one or more microprocessors, or any other such configuration.

[0310] The methods or algorithms described in connection with the examples disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. The storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. Alternatively, the storage medium may be integrated into the processor. The processor and the storage medium may reside in an ASIC.

[0311] The previous description of examples of the present disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the examples will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other examples without departing from the spirit or scope of the present disclosure. Thus, the present disclosure is not intended to be limited to the examples set forth herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0312] Although the present disclosure has been shown and described in detail with reference to exemplary embodiments thereof, the present disclosure is not limited to such embodiments. It will be understood by those skilled in the art that various changes in form and details may be made without departing from the spirit and scope of the present disclosure as defined herein. For example, the above embodiments are not limited to 5GS, and the embodiments may also be applied to communication systems other than 5GS (e.g., 6G systems, Beyond 5G systems).

[0313] <First Addendum> All or part of the exemplary aspects of the above disclosure may be described as, but are not limited to, the following supplementary notes.

[0314] Supplementary Note 1. A method for a User Equipment (UE), the method comprising: Sending an Attach Request message including information for obtaining a UE policy for the UE; receiving an Attach Accept message including the UE policy; method.

[0315] Appendix 2. The method of Appendix 1, wherein the information includes at least one of a UE policy list, a UE policy class mark, and a UE OS ID.

[0316] Appendix 3. A method for a communication device, the method comprising: receiving an Attach Request message including information for obtaining a UE policy; sending a Create Session Request message including said information; receiving a Create Session Response message including the UE policy after sending the Create Session Request message; sending an Attach Accept message including the UE policy; A method comprising:

[0317] Supplementary Note 4. The method of Supplementary Note 3, wherein the communication device is a Mobility Management Entity (MME).

[0318] Appendix 5. A method for a communication device, the method comprising: receiving a Create Session Request message including information for obtaining a UE policy; sending the create session request message; receiving a Create Session Response message including the UE policy after sending the Create Session Request message; sending the create session response message; A method comprising:

[0319] Supplementary Note 6. The method of Supplementary Note 5, wherein the communication device is a Serving Gateway (S-GW).

[0320] Appendix 7. A method for a communication device, the method comprising: receiving a Create Session Request message including information for obtaining a UE policy; sending a first message including said information; receiving a second message including the UE policy after sending the first message; sending a third message including the UE policy; and A method comprising:

[0321] Supplementary Note 8. The method of Supplementary Note 7, wherein the communications device includes a Packet Data Network (PDN) Gateway Control plane function (PGW-C) and a Session Management Function (SMF).

[0322] Supplementary Note 9. The first message is an Npcf_get_UEpolicy request message, The second message is an Npcf_get_UEpolicy response message, 9. The method of claim 7 or 8, wherein the third message is a Create Session Response message.

[0323] Appendix 10. A method for a communication device, the method comprising: receiving a first message including information for obtaining a UE policy; sending a second message including said information; receiving a third message including the UE policy after sending the first message; sending a fourth message including the UE policy; and A method comprising:

[0324] Clause 11. The method of clause 10, wherein the communications device is a Policy Control Function (PCF) device.

[0325] Supplementary Note 12. The first message is an Npcf_get_UEpolicy request message, the second message is a Nudm_get_UEpolicy request message, The third message is a Nudm_get_UEpolicy response message, 12. The method of claim 10 or 11, wherein the fourth message is an Npcf_get_UEpolicy response message.

[0326] Appendix 13. A method for a communication device, the method comprising: receiving a first message including information for obtaining a UE policy; obtaining the UE policy; receiving a second message including the UE policy; A method comprising:

[0327] Clause 14. The method of clause 13, wherein the communications device is a Unified Data Management (UDM) device.

[0328] Supplementary Note 15. The first message is a Nudm_get_UEpolicy request message, 15. The method of claim 13 or 14, wherein the second message is a Nudm_get_UEpolicy response message.

[0329] Appendix 16. A method for a communication device, the method comprising: receiving a first message including information for obtaining a UE policy; obtaining the UE policy; receiving a second message including the UE policy; A method comprising:

[0330] Clause 17. The method of clause 16, wherein the communications device is a Unified Data Repository (UDR) device.

[0331] Supplementary Note 18. The first message is a Nudm_get_UEpolicy request message, 18. The method of claim 16 or 17, wherein the second message is a Nudm_get_UEpolicy response message.

[0332] Appendix 19. A method for a User Equipment (UE), the method comprising: sending a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy for the UE; receiving a second EPS SM message including the UE policy; A method comprising:

[0333] Supplementary Note 20. The method of Supplementary Note 19, wherein the first EPS SM message includes at least one of a UE policy list, a UE policy classmark, and a UE OS ID.

[0334] Appendix 21. A method for a communication device, the method comprising: receiving a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy; sending a second EPS SM message containing said information; receiving a third EPS SM message including the UE policy after sending the second EPS SM message; sending a fourth EPS SM message including the UE policy; method.

[0335] Supplementary Note 22. The method of Supplementary Note 21, wherein the communications device is a Mobility Management Entity (MME).

[0336] Addendum 23. A method for a communication device, the method comprising: receiving a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy; sending a second EPS SM message containing said information; receiving a third EPS SM message including the UE policy after sending the second EPS SM message; sending a fourth EPS SM message including the UE policy; and A method comprising:

[0337] Addendum 24. The method of Addendum 23, wherein the communications device is a Serving Gateway (S-GW).

[0338] Addendum 25. A method for a communication device, the method comprising: receiving a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy; sending a first message including said information; receiving a second message including the UE policy after sending the first message; sending a second EPS SM message including the UE policy; A method comprising:

[0339] Clause 26. The method of clause 25, wherein the communications device includes a Packet Data Network (PDN) Gateway Control plane function (PGW-C) and a Session Management Function (SMF).

[0340] Supplementary Note 27. The first message is an Npcf_get_UEpolicy request message, 27. The method of claim 25 or 26, wherein the second message is an Npcf_get_UEpolicy response message.

[0341] Appendix 28. A method for a User Equipment (UE), the method comprising: sending a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy for the UE; receiving a message including an indicator that the UE policy is pending; performing a cell selection; Carrying out registration procedures for the 5G system; receiving the UE policy after performing the registration procedure; A method comprising:

[0342] Appendix 29. The method of Appendix 28, wherein the information includes at least one of a UE policy list, a UE policy class mark, and a UE OS ID.

[0343] Addendum 30. A method for a communication device, the method comprising: receiving a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy; sending a second EPS SM message containing said information; receiving a third EPS SM message after sending the second EPS SM message, the third EPS SM message including an indicator that the UE policy is pending; sending a message including said indicator; A method comprising:

[0344] Supplementary Note 31. The method of Supplementary Note 30, wherein the communications device is a Mobility Management Entity (MME).

[0345] Addendum 32. A method for a communication device, the method comprising: receiving a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy; sending a second EPS SM message containing said information; receiving a third EPS SM message after sending the second EPS SM message, the third EPS SM message including an indicator that the UE policy is pending; transmitting a fourth EPS SM message including said indicator; A method comprising:

[0346] Addendum 33. The method of Addendum 32, wherein the communications device is a Serving Gateway (S-GW).

[0347] Addendum 34. A method for a communication device, the method comprising: receiving a message including an indicator that a UE policy is pending; receiving a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining the UE policy; transmitting a second EPS SM message including the indicator; A method comprising:

[0348] Clause 35. The method of Clause 34, wherein the communications device includes a Packet Data Network (PDN) Gateway Control plane function (PGW-C) and a Session Management Function (SMF).

[0349] Addendum 36. The method of Addendum 34 or 35, wherein the message is an Npcf_UEPolicy_update_Notification message.

[0350] Addendum 37. A method for a communication device, the method comprising: receiving a first message including a UE policy; transmitting a second message including an indicator that the UE policy is pending; and A method comprising:

[0351] Clause 38. The method of clause 10, wherein the communications device is a Policy Control Function (PCF) device.

[0352] Addendum 39. A method for a User Equipment (UE), the method comprising: sending a Registration Request message; The registration request message includes information indicating that the UE supports receiving a UE policy for an evolved packet system via a 5G system; and receiving the UE policy after sending the registration request message; A method comprising:

[0353] Addendum 40. A method for a communication device, the method comprising: receiving a Registration Request message from a User Equipment (UE); The registration request message includes information indicating that the UE supports receiving a UE policy for an evolved packet system via a 5G system; and sending a message containing said information; receiving the UE policy after sending the message; sending the UE policy to the UE; A method comprising:

[0354] Clause 41. The method of clause 40, wherein the communications device is an Access and Mobility Management Function (AMF) device.

[0355] Addendum 42. After sending the message, receiving an indicator that the UE policy is pending; maintaining the N1 connection upon receiving said indicator; 42. The method of claim 40 or 41, further comprising:

[0356] Addendum 43. A method for a communication device, the method comprising: receiving a message, The message includes information indicating that a User Equipment (UE) supports receiving a UE policy for an evolved packet system over a 5G system; and sending the UE policy after receiving the message; A method comprising:

[0357] Clause 44. The method of Clause 43, wherein the communications device is a Policy Control Function (PCF) device.

[0358] Addendum 45. The method of Addendum 43 or 44, further comprising, after receiving the message, sending an indicator indicating that the UE policy is pending.

[0359] Appendix 46. A User Equipment (UE), comprising: means for sending an Attach Request message including information for obtaining a UE policy for the UE; means for receiving an Attach Accept message including the UE policy; UE equipped with.

[0360] Appendix 47. The UE of Appendix 46, wherein the information includes at least one of a UE policy list, a UE policy class mark, and a UE OS ID.

[0361] Appendix 48. A communication device, means for receiving an Attach Request message including information for obtaining a UE policy; means for transmitting a Create Session Request message including the information; means for receiving a Create Session Response message including the UE policy after sending the Create Session Request message; means for transmitting an Attach Accept message including the UE policy; A communication device comprising:

[0362] Supplementary Note 49. The communications device of Supplementary Note 48, wherein the communications device is a Mobility Management Entity (MME).

[0363] Appendix 50. A communication device, means for receiving a Create Session Request message including information for obtaining a UE policy; means for transmitting the create session request message; means for receiving a Create Session Response message including the UE policy after sending the Create Session Request message; means for sending the create session response message; A communication device comprising:

[0364] Supplementary Note 51. The communications device of Supplementary Note 50, wherein the communications device is a Serving Gateway (S-GW).

[0365] Appendix 52. A communication device, means for receiving a Create Session Request message including information for obtaining a UE policy; means for transmitting a first message including said information; means for receiving, after sending the first message, a second message including the UE policy; means for transmitting a third message including the UE policy; A communication device comprising:

[0366] Appendix 53. The communications device of Appendix 52, wherein the communications device includes a Packet Data Network (PDN) Gateway Control plane function (PGW-C) and a Session Management Function (SMF).

[0367] Addendum 54. The first message is an Npcf_get_UEpolicy request message, The second message is an Npcf_get_UEpolicy response message, 54. The communications device of claim 52 or 53, wherein the third message is a Create Session Response message.

[0368] Appendix 55. A communication device, means for receiving a first message including information for obtaining a UE policy; means for transmitting a second message including said information; means for receiving, after sending the first message, a third message including the UE policy; means for transmitting a fourth message including the UE policy; A communication device comprising:

[0369] Clause 56. The communications device of Clause 55, wherein the communications device is a Policy Control Function (PCF) device.

[0370] Addendum 57. The first message is an Npcf_get_UEpolicy request message, the second message is a Nudm_get_UEpolicy request message, The third message is a Nudm_get_UEpolicy response message, 57. The communication device of claim 55 or 56, wherein the fourth message is an Npcf_get_UEpolicy response message.

[0371] Appendix 58. A communication device, means for receiving a first message including information for obtaining a UE policy; means for obtaining the UE policy; means for receiving a second message including the UE policy; A communication device comprising:

[0372] Clause 59. The communications device of Clause 58, wherein the communications device is a Unified Data Management (UDM) device.

[0373] Addendum 60. The first message is a Nudm_get_UEpolicy request message, 60. The communications device of claim 59, wherein the second message is a Nudm_get_UEpolicy response message.

[0374] Appendix 61. A communication device, means for receiving a first message including information for obtaining a UE policy; means for obtaining the UE policy; means for receiving a second message including the UE policy; A communication device comprising:

[0375] Clause 62. The communications device of Clause 61, wherein the communications device is a Unified Data Repository (UDR) device.

[0376] Supplementary Note 63. The first message is a Nudm_get_UEpolicy request message, 63. The communication device according to claim 61 or 62, wherein the second message is a Nudm_get_UEpolicy response message.

[0377] Addendum 64. A User Equipment (UE), comprising: means for transmitting a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy for the UE; means for receiving a second EPS SM message including the UE policy; UE equipped with.

[0378] Appendix 65. The UE of Appendix 64, wherein the first EPS SM message includes at least one of a UE policy list, a UE policy classmark, and a UE OS ID.

[0379] Appendix 66. A communication device, means for receiving a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy; means for transmitting a second EPS SM message containing said information; means for receiving a third EPS SM message including the UE policy after sending the second EPS SM message; means for transmitting a fourth EPS SM message including the UE policy; A communication device comprising:

[0380] Supplementary Note 67. The communications device of Supplementary Note 66, wherein the communications device is a Mobility Management Entity (MME).

[0381] Appendix 68. A communication device, means for receiving a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy; means for transmitting a second EPS SM message containing said information; means for receiving a third EPS SM message including the UE policy after sending the second EPS SM message; means for transmitting a fourth EPS SM message including the UE policy; A communication device comprising:

[0382] Appendix 69. The communications device of Appendix 68, wherein the communications device is a Serving Gateway (S-GW).

[0383] Appendix 70. A communication device, means for receiving a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy; means for transmitting a first message including said information; means for receiving, after sending the first message, a second message including the UE policy; means for transmitting a second EPS SM message including the UE policy; A communication device comprising:

[0384] Attachment 71. The communications device of Addendum 70, wherein the communications device includes a Packet Data Network (PDN) Gateway Control plane function (PGW-C) and a Session Management Function (SMF).

[0385] Addendum 72. The first message is an Npcf_get_UEpolicy request message, 72. The communications device of claim 70, wherein the second message is an Npcf_get_UEpolicy response message.

[0386] Addendum 73. A User Equipment (UE), comprising: means for transmitting a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy for the UE; means for receiving a message including an indicator that the UE policy is pending; means for performing cell selection; means for performing a registration procedure for a 5G system; means for receiving the UE policy after performing the registration procedure; UE equipped with.

[0387] Clause 74. The UE of Clause 73, wherein the information includes at least one of a UE policy list, a UE policy class mark, and a UE OS ID.

[0388] Appendix 75. A communication device, means for receiving a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy; means for transmitting a second EPS SM message containing said information; means for receiving, after sending the second EPS SM message, a third EPS SM message including an indicator that the UE policy is pending; means for transmitting a message including said indicator; A communication device comprising:

[0389] Addendum 76. The communications device of Addendum 75, wherein the communications device is a Mobility Management Entity (MME).

[0390] Appendix 77. A communication device, means for receiving a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining a UE policy; means for transmitting a second EPS SM message containing said information; means for receiving, after sending the second EPS SM message, a third EPS SM message including an indicator that the UE policy is pending; means for transmitting a fourth EPS SM message including the indicator; A communication device comprising:

[0391] Addendum 78. The communications device of Addendum 77, wherein the communications device is a Serving Gateway (S-GW).

[0392] Appendix 79. A communication device, means for receiving a message including an indicator that a UE policy is pending; means for receiving a first Evolved Packet System (EPS) Session Management (SM) message including information for obtaining the UE policy; means for transmitting a second EPS SM message including the indicator; A communication device comprising:

[0393] Attachment 80. The communications device of Addendum 79, wherein the communications device includes a Packet Data Network (PDN) Gateway Control plane function (PGW-C) and a Session Management Function (SMF).

[0394] Addendum 81. The communication device of Addendum 79 or 80, wherein the message is an Npcf_UEPolicy_update_Notification message.

[0395] Appendix 82. A communication device, means for receiving a first message including a UE policy; means for transmitting a second message including an indicator that the UE policy is pending; A communication device comprising:

[0396] Clause 83. The communications device of Clause 82, wherein the communications device is a Policy Control Function (PCF) device.

[0397] Addendum 84. A User Equipment (UE), comprising: A means for sending a Registration Request message, comprising: The registration request message includes information indicating that the UE supports receiving a UE policy for an evolved packet system via a 5G system; means for receiving the UE policy after sending the registration request message; UE equipped with.

[0398] Appendix 85. A communication device, A means for receiving a Registration Request message from a User Equipment (UE), comprising: The registration request message includes information indicating that the UE supports receiving a UE policy for an evolved packet system via a 5G system; means for sending a message containing said information; means for receiving the UE policy after sending the message; means for transmitting the UE policy to the UE; A communication device comprising:

[0399] Clause 86. The communications device of Clause 85, wherein the communications device is an Access and Mobility Management Function (AMF) device.

[0400] Addendum 87. Means for receiving, after sending said message, an indicator that said UE policy is pending; means for maintaining the N1 connection upon receiving said indicator; 87. The communication device of claim 85 or 86, further comprising:

[0401] Appendix 88. A communication device, A means for receiving a message, The message includes information indicating that a User Equipment (UE) supports receiving a UE policy for an evolved packet system over a 5G system; means for sending the UE policy after receiving the message; A communication device comprising:

[0402] Clause 89. The communications device of Clause 88, wherein the communications device is a Policy Control Function (PCF) device.

[0403] Addendum 90. The communications device of Addendum 88 or 89, further comprising means for sending an indicator indicating that the UE policy is pending after receiving the message.

[0404] <Second Note> All or part of the exemplary aspects of the above disclosure may be described as, but are not limited to, the following supplementary notes.

[0405] Supplementary Note 1. A method for a User Equipment (UE), the method comprising: Sending a first message to a Mobility Management Entity (MME) including information for obtaining a UE policy; receiving a second message from the MME including the UE policy; method.

[0406] Appendix 2. The method of Appendix 1, wherein the information includes at least one of a UE policy list, a UE policy class mark, and a UE OS ID.

[0407] Appendix 3. The method of any one of Appendixes 1 to 2, wherein the information is Protocol Configuration Options (PCO).

[0408] Appendix 4. The method of any one of Appendixes 1 to 3, wherein the UE policy is a UE Route Selection Policy (URSP).

[0409] Supplementary Note 5. The first message is an Attach Request message or a Packet Data Network (PDN) connection request message, 5. The method of any one of Supplementary Notes 1 to 4, wherein the second message is an Attach Accept message or a Bearer Modify Request message.

[0410] Supplementary Note 6. The method of any one of Supplementary Notes 1 to 5, wherein the UE receives the second message from the MME when a Policy Control Function (PCF) decides to update the UE policy.

[0411] Supplementary Note 7. The method of any one of Supplementary Notes 1 to 6, wherein the UE indicates to a 5G System (5GS) its capability to receive and process the UE policy in an Evolved Packet System (EPS).

[0412] Appendix 8. The first message is a first Evolved Packet System (EPS) Session Management (ESM) message, 5. The method of any one of claims 1 to 4, wherein the second message is a second ESM message.

[0413] Addendum 9. The first ESM message is a Packet Data Network (PDN) connection request message, 9. The method of claim 8, wherein the second ESM message is an Activate Default EPS Bearer Context Request message.

[0414] Appendix 10. A method for a communication device, the method comprising: receiving a first message from a User Equipment (UE) including information for obtaining a UE policy; sending a second message including the information to a Serving Gateway (S-GW); receiving a third message from the S-GW including the UE policy; sending a fourth message to the UE including the UE policy; The method, wherein the communication device is a Mobility Management Entity (MME).

[0415] Appendix 11. The method of Appendix 10, wherein the UE policy is a UE Route Selection Policy (URSP).

[0416] Supplementary Note 12. The first message is an Attach Request message or a Packet Data Network (PDN) connection request message, the second message is a Create Session Request message, The third message is a Create Session Response message or an Update Bearer Request message, 12. The method according to claim 10 or 11, wherein the fourth message is an Attach Accept message or a Bearer Modify Request message.

[0417] Supplementary Note 13. The method of any one of Supplementary Notes 10 to 12, wherein the MME receives the third message from the S-GW and sends the fourth message to the UE if a Policy Control Function (PCF) decides to update the UE policy.

[0418] Clause 14. The first message is a first Evolved Packet System (EPS) Session Management (ESM) message, the second message is a second ESM message, the third message is a third ESM message, 12. The method of claim 10 or 11, wherein the fourth message is a fourth ESM message.

[0419] Supplementary Note 15. The first ESM message is a PDN connection request message, The third ESM message is a Create session response message, 15. The method of claim 14, wherein the fourth ESM message is an Activate Default EPS Bearer Context Request message.

[0420] Appendix 16. A method for a communication device, the method comprising: receiving a first message from a Mobility Management Entity (MME) including information for obtaining a UE policy; sending a second message including the information to a Packet Data Network (PDN) Gateway Control plane function (PGW-C) and a Session Management Function (SMF); receiving a third message from the PGW-C and SMF, the third message including the UE policy; sending a fourth message to the MME including the UE policy; The method, wherein the communication device is a Serving Gateway (S-GW).

[0421] Appendix 17. The method of Appendix 16, wherein the UE policy is a UE Route Selection Policy (URSP).

[0422] Supplementary Note 18. The first message is a Create Session Request message, the second message is the create session request message, The third message is a Create Session Response message or an Update Bearer Request message, 18. The method of claim 16 or 17, wherein the fourth message is the Create Session Response message or the Update Bearer Request message.

[0423] Supplementary Note 19. The method of any one of Supplementary Notes 16 to 18, wherein the S-GW receives the third message from the PGW-C and SMF and sends the fourth message to the MME when a Policy Control Function (PCF) decides to update the UE policy.

[0424] Clause 20. The first message is a first Evolved Packet System (EPS) Session Management (ESM) message, the second message is a second ESM message, the third message is a third ESM message, 18. The method of claim 16 or 17, wherein the fourth message is a fourth ESM message.

[0425] Appendix 21. A method for a communication device, the method comprising: Receive a first message from a Serving Gateway (S-GW) including information for obtaining a UE policy; sending a second message including said information to a Policy Control Function (PCF); receiving a third message from the PCF including the UE policy; sending a fourth message to the S-GW including the UE policy; The communication device is a Packet Data Network (PDN) Gateway Control plane function (PGW-C) and a Session Management Function (SMF), method.

[0426] Appendix 22. The method of Appendix 21, wherein the UE policy is a UE Route Selection Policy (URSP).

[0427] Supplementary Note 23. The first message is a Create Session Request message, the second message is an Npcf_get_UEpolicy request message, the third message is an Npcf_get_UEpolicy response message or an Npcf_UEPolicyControl_UpdateNotify message, 23. The method of claim 21 or 22, wherein the fourth message is a Create Session Response message or an Update Bearer Request message.

[0428] Supplementary Note 24. The method of any one of Supplementary Notes 21 to 23, wherein the PGW-C and SMF receive the third message from the PCF and send the fourth message to the S-GW when the PCF decides to update the UE policy.

[0429] Clause 25. The first message is a first Evolved Packet System (EPS) Session Management (ESM) message, 23. The method of claim 21 or 22, wherein the fourth message is a second ESM message.

[0430] Addendum 26. A method for a communication device, the method comprising: receiving a first message from a Packet Data Network (PDN) Gateway Control plane function (PGW-C) and a Session Management Function (SMF) including information for obtaining a UE policy; sending a second message containing the information to a Unified Data Management (UDM) or a Unified Data Repository (UDR); receiving a third message from the UDM or the UDR that includes the UE policy; Send a fourth message including the UE policy to the PGW-C and SMF; The method, wherein the communication device is a Policy Control Function (PCF).

[0431] Appendix 27. The method of Appendix 26, wherein the UE policy is a UE Route Selection Policy (URSP).

[0432] Supplementary Note 28. The first message is an Npcf_get_UEpolicy request message, the second message is a Nudm_get_UEpolicy request message, The third message is a Nudm_get_UEpolicy response message, 28. The method of claim 26 or 27, wherein the fourth message is an Npcf_get_UEpolicy response message or an Npcf_UEPolicyControl_UpdateNotify message.

[0433] Supplementary Note 29. The method of any one of Supplementary Notes 26 to 28, wherein the PCF sends the fourth message to the PGW-C and SMF if the PCF decides to update the UE policy.

[0434] Supplementary Note 30. A User Equipment (UE), comprising: means for sending a first message to a Mobility Management Entity (MME), the first message including information for obtaining a UE policy; means for receiving a second message from the MME, the second message including the UE policy; UE equipped with.

[0435] Appendix 31. The UE of Appendix 30, wherein the information includes at least one of a UE policy list, a UE policy class mark, and a UE OS ID.

[0436] Addendum 32. The UE of Addendum 30 or 31, wherein the information is Protocol Configuration Options (PCO).

[0437] Addendum 33. The UE of any one of Addendums 30 to 32, wherein the UE policy is a UE Route Selection Policy (URSP).

[0438] Addendum 34. The first message is an Attach Request message or a Packet Data Network (PDN) connection request message, 34. The UE of any one of Supplementary Notes 30 to 33, wherein the second message is an Attach Accept message or a Bearer Modify Request message.

[0439] Supplementary Note 35. The UE of any one of Supplementary Notes 30 to 34, wherein the UE receives the second message from the MME when a Policy Control Function (PCF) decides to update the UE policy.

[0440] Supplementary Note 36. The UE of any one of Supplementary Notes 30 to 35, wherein the UE indicates to a 5G System (5GS) the UE's capability to receive and process the UE policy in an Evolved Packet System (EPS).

[0441] Addendum 37. The first message is a first Evolved Packet System (EPS) Session Management (ESM) message, 34. The UE of any one of Supplementary Notes 30 to 33, wherein the second message is a second ESM message.

[0442] Addendum 38. The first ESM message is a Packet Data Network (PDN) connection request message, 38. The UE of claim 37, wherein the second ESM message is an Activate Default EPS Bearer Context Request message.

[0443] Appendix 39. A communication device, means for receiving a first message from a User Equipment (UE) including information for obtaining a UE policy; means for sending a second message including the information to a Serving Gateway (S-GW); means for receiving a third message from the S-GW, the third message including the UE policy; means for sending a fourth message to the UE, the fourth message including the UE policy; Equipped with The communication device is a Mobility Management Entity (MME).

[0444] Appendix 40. The communications device of Appendix 39, wherein the UE policy is a UE Route Selection Policy (URSP).

[0445] Addendum 41. The first message is an Attach Request message or a Packet Data Network (PDN) connection request message, the second message is a Create Session Request message, The third message is a Create Session Response message or an Update Bearer Request message, 41. The communications device of claim 39 or 40, wherein the fourth message is an Attach Accept message or a Bearer Modify Request message.

[0446] Supplementary Note 42. The communications device of any one of Supplementary Notes 39 to 41, wherein the MME receives the third message from the S-GW and sends the fourth message to the UE when a Policy Control Function (PCF) decides to update the UE policy.

[0447] Addendum 43. The first message is a first Evolved Packet System (EPS) Session Management (ESM) message, the second message is a second ESM message, the third message is a third ESM message, 41. The communication device of claim 39 or 40, wherein the fourth message is a fourth ESM message.

[0448] Supplementary Note 44. The first ESM message is a PDN connection request message, The third ESM message is a Create session response message, 44. The communications device of claim 43, wherein the fourth ESM message is an Activate Default EPS Bearer Context Request message.

[0449] Appendix 45. A communication device, means for receiving a first message from a Mobility Management Entity (MME), the first message including information for obtaining a UE policy; means for sending a second message including the information to a Packet Data Network (PDN) Gateway Control plane function (PGW-C) and a Session Management Function (SMF); means for receiving a third message including the UE policy from the PGW-C and SMF; means for sending a fourth message to the MME, the fourth message including the UE policy; Equipped with The communication device is a Serving Gateway (S-GW).

[0450] Appendix 46. The communications device of Appendix 45, wherein the UE policy is a UE Route Selection Policy (URSP).

[0451] Addendum 47. The first message is a Create Session Request message, the second message is the create session request message, The third message is a Create Session Response message or an Update Bearer Request message, 47. The communications device of claim 45 or 46, wherein the fourth message is the create session response message or the update bearer request message.

[0452] Supplementary Note 48. The communications device of any one of Supplementary Notes 45 to 47, wherein the S-GW receives the third message from the PGW-C and SMF and sends the fourth message to the MME when a Policy Control Function (PCF) decides to update the UE policy.

[0453] Addendum 49. The first message is a first Evolved Packet System (EPS) Session Management (ESM) message, the second message is a second ESM message, the third message is a third ESM message, 47. The communication device of claim 45, wherein the fourth message is a fourth ESM message.

[0454] Appendix 50. A communication device, means for receiving a first message from a Serving Gateway (S-GW), the first message including information for obtaining a UE policy; means for sending a second message including said information to a Policy Control Function (PCF); means for receiving a third message from the PCF, the third message including the UE policy; means for sending a fourth message to the S-GW, the fourth message including the UE policy; Equipped with The communication device is a Packet Data Network (PDN) Gateway Control plane function (PGW-C) and a Session Management Function (SMF).

[0455] Appendix 51. The communications device of Appendix 50, wherein the UE policy is a UE Route Selection Policy (URSP).

[0456] Addendum 52. The first message is a Create Session Request message, the second message is an Npcf_get_UEpolicy request message, the third message is an Npcf_get_UEpolicy response message or an Npcf_UEPolicyControl_UpdateNotify message, 52. The communications device of claim 50 or 51, wherein the fourth message is a Create Session Response message or an Update Bearer Request message.

[0457] Supplementary Note 53. The communications device of any one of Supplementary Notes 50 to 52, wherein the PGW-C and SMF receive the third message from the PCF and send the fourth message to the S-GW when the PCF decides to update the UE policy.

[0458] Clause 54. The first message is a first Evolved Packet System (EPS) Session Management (ESM) message; 52. The communication device of claim 50 or 51, wherein the fourth message is a second ESM message.

[0459] Appendix 55. A communication device, means for receiving a first message from a Packet Data Network (PDN) Gateway Control plane function (PGW-C) and a Session Management Function (SMF), the first message including information for obtaining a UE policy; means for sending a second message containing said information to a Unified Data Management (UDM) or Unified Data Repository (UDR); means for receiving a third message from the UDM or the UDR, the third message including the UE policy; means for sending a fourth message including the UE policy to the PGW-C and SMF; Equipped with The communication device is a Policy Control Function (PCF).

[0460] Appendix 56. The communications device of Appendix 55, wherein the UE policy is a UE Route Selection Policy (URSP).

[0461] Addendum 57. The first message is an Npcf_get_UEpolicy request message, the second message is a Nudm_get_UEpolicy request message, The third message is a Nudm_get_UEpolicy response message, 57. The communication device according to claim 55 or 56, wherein the fourth message is an Npcf_get_UEpolicy response message or an Npcf_UEPolicyControl_UpdateNotify message.

[0462] Supplementary Note 58. A communications device according to any one of Supplementary Notes 55 to 57, wherein the PCF sends the fourth message to the PGW-C and SMF when the PCF decides to update the UE policy.

[0463] Although the present invention has been described above with reference to the embodiments (and examples), the present invention is not limited to the above-described embodiments (and examples). Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

[0464] This application claims priority from Indian Provisional Patent Application No. 202211004541, filed on January 27, 2022, the disclosure of which is incorporated herein in its entirety. [Explanation of symbols]

[0465] 1. Telecommunications Systems 3UE 5 (R)AN nodes 7 Core Network 20 Data Network 31 Transceiver Circuit 32 Antenna 33 Controller 34 User Interface 35 USIM 36 memory 51 Transceiver circuit 52 Antenna 53 Network Interface 54 Controller 55 memory 60RU 61 DU 62 CU 70 AMF 71 SMF 72 UPF 73 PCF 74 AUSF 75 UDM 76 NWDAF 77 NEF 78 NSACF 80 MME 81 SGW 361 Operating Systems 362 Communication Control Module 551 Operating Systems 552 Communication Control Module 601 Transceiver Circuit 602 Antenna 603 Network Interface 604 Controller 605 memory 611 Transceiver Circuit 612 Network Interface 613 Controller 614 memory 621 Transceiver Circuit 622 network interface 623 Controller 624 memory 701 Transceiver Circuit 702 network interface 703 Controller 704 memory 711 Transceiver Circuit 712 Network Interface 713 Controller 714 memory 721 Transceiver Circuit 722 network interface 723 Controller 724 memory 731 Transceiver Circuit 732 network interface 733 Controller 734 memory 741 Transceiver Circuit 742 network interfaces 743 Controller 744 memory 751 Transceiver Circuit 752 network interfaces 753 Controller 754 memory 761 Transceiver Circuit 762 network interfaces 763 Controller 764 memory 771 Transceiver Circuit 772 network interfaces 773 Controller 774 memory 781 Transceiver Circuit 782 network interfaces 783 Controller 784 memory 3621 Transceiver Control Module 5521 Transceiver Control Module 6051 Operating System 6052 Communication Control Module 6141 Operating System 6142 Communication Control Module 6241 Operating System 6242 Communication Control Module 7001 AMF 7002 AMF 7041 Operating System 7042 Communication Control Module 7141 Operating System 7142 Communication Control Module 7241 Operating System 7242 Communication Control Module 7341 Operating System 7342 Communication Control Module 7441 Operating System 7442 Communication Control Module 7541 Operating Systems 7542 Communication Control Module 7641 Operating System 7642 Communication Control Module 7741 Operating System 7742 Communication Control Module 7841 Operating System 7842 Communication Control Module 60521 Transceiver Control Module 61421 Transceiver Control Module 62421 Transceiver Control Module 70421 Transceiver Control Module 71421 Transceiver Control Module 72421 Transceiver Control Module 73421 Transceiver Control Module 74421 Transceiver Control Module 75421 Transceiver Control Module 76421 Transceiver Control Module 77421 Transceiver Control Module 78421 Transceiver Control Module< / nsacf> < / nef> < / nwdaf> < / udm> < / ausf> < / pcf> < / upf> < / smf> < / amf>

Claims

1. 1. A method for a User Equipment (UE), the method comprising: Supports handling of UE policies in the Evolved Packet System (EPS), sending a parameter included in a first message, the parameter indicating support for handling the UE policy in the EPS, to an Access and Mobility Management Function (AMF) device; method.

2. the UE policy is a UE Route Selection Policy (URSP); The method of claim 1.

3. The UE policy handling is UE Route Selection Policy (URSP) provisioning.

3. The method according to claim 1 or 2.

4. A User Equipment (UE), comprising: means for supporting UE policy handling in an Evolved Packet System (EPS); means for transmitting a parameter included in a first message, the parameter indicating support for handling the UE policy in the EPS, to an Access and Mobility Management Function (AMF) device; A UE comprising:

5. the UE policy is a UE Route Selection Policy (URSP); The UE of claim 4.

6. The UE policy handling is UE Route Selection Policy (URSP) provisioning.

6. The UE according to claim 4 or 5.

Images