Communication device method and communication device

Abstract

Current standards lack a mechanism or procedure to achieve this objective. This disclosure provides a solution to this objective. [Solution] The method of the communication device includes transmitting information requesting User Equipment Route Selection Policy (URSP) rules and, when transmitting the information, receiving the URSP rules.

Description

[Technical Field]

[0001] The present disclosure relates to a communication device method, a User Equipment (UE) method, a communication device, and a UE. [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] -#4 Research into whether and how the network can be made aware when the UE is implementing URSP rules, and whether and what actions the 5G network can take. [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-patent document 4] 3GPP TS 23.501: "System architecture for the 5G System (5GS)". V17.3.0 (2021-12) [Non-patent document 5] 3GPP TS 23.502: "Procedures for the 5G System (5GS)". V17.3.0 (2021-12) [Non-patent document 6] 3GPP TS 23.503: "Policy and charging control framework for the 5G System (5GS) Stage 2". V17.3.0 (2021-12) [Non-Patent Document 7] IETF RFC 5580: "Carrying Location Objects in RADIUS and Diameter". (2009-08) Summary of the Invention [Problem to be solved by the invention]

[0005] Current standards lack a mechanism or procedure to achieve this goal. This disclosure provides a solution to this goal. [Means for solving the problem]

[0006] In an aspect of the present disclosure, a method of a communications device includes transmitting information requesting User Equipment Route Selection Policy (URSP) rules, and receiving the URSP rules when transmitting the information.

[0007] In an aspect of the present disclosure, a method for a User Equipment (UE) includes receiving information requesting a User Equipment Route Selection Policy (URSP) rule, and, if the information is received, transmitting the URSP rule.

[0008] In an aspect of the present disclosure, a method of a communications device includes receiving information requesting a User Equipment Route Selection Policy (URSP) rule, and, upon receiving the information, transmitting the URSP rule.

[0009] In an aspect of the present disclosure, a method of a communications device includes transmitting information to request monitoring of traffic routing, and, upon transmitting the information, receiving results of the monitoring of the traffic routing.

[0010] In an aspect of the present disclosure, a method of a communications device includes receiving information for requesting monitoring of traffic routing; after receiving the information, performing a validation check on a User Equipment Route Selection Policy (URSP) rule; and if the validation is successfully completed, transmitting the information for monitoring the traffic routing.

[0011] In an aspect of the present disclosure, a method of a communications device includes receiving information for monitoring traffic routing, monitoring the traffic routing based on the information, and transmitting results of the monitoring of the traffic routing.

[0012] In an aspect of the disclosure, a method of a communications device includes receiving results of traffic routing monitoring and transmitting the results.

[0013] In an aspect of the present disclosure, a method in a User Equipment (UE) includes transmitting a Protocol Data Unit (PDU) Session Establishment Request message, the PDU Session Establishment Request message including a Data Network Name (DNN), a Single Network Slice Selection Assistance Information (S-NSSAI), and an identifier of an application for which the UE is requesting a service. The method also includes receiving a PDU Session Establishment Reject message, the PDU Session Establishment Reject message including a rejection cause indicating that the UE or the application is not entitled to the service in the S-NSSAI and the DNN.

[0014] In an aspect of the present disclosure, a communications device includes means for transmitting information requesting User Equipment Route Selection Policy (URSP) rules, and means for receiving the URSP rules when transmitting the information.

[0015] In an aspect of the present disclosure, a User Equipment (UE) includes means for receiving information requesting a User Equipment Route Selection Policy (URSP) rule, and means for transmitting the URSP rule upon receiving the information.

[0016] In an aspect of the present disclosure, a communications device includes means for receiving information requesting a User Equipment Route Selection Policy (URSP) rule, and means for transmitting the URSP rule upon receiving the information.

[0017] In an aspect of the present disclosure, a communications device includes means for transmitting information to request monitoring of traffic routing, and means for receiving results of the monitoring of the traffic routing when the information is transmitted.

[0018] In an aspect of the present disclosure, a communications device includes means for receiving information for requesting traffic routing monitoring, means for performing a validation check on a User Equipment Route Selection Policy (URSP) rule after receiving the information, and means for transmitting information for monitoring the traffic routing if the validation check is successfully completed.

[0019] In an aspect of the present disclosure, a communications device includes means for receiving information for monitoring traffic routing, means for monitoring the traffic routing based on the information, and means for transmitting results of the monitoring of the traffic routing.

[0020] In an aspect of the present disclosure, a communications device includes means for receiving results of traffic routing monitoring and means for transmitting the results.

[0021] In an aspect of the present disclosure, a User Equipment (UE) includes means for transmitting a Protocol Data Unit (PDU) Session Establishment Request message, the PDU Session Establishment Request message including a Data Network Name (DNN), a Single Network Slice Selection Assistance Information (S-NSSAI), and an identifier of an application for which the UE requests service. The UE includes means for receiving a PDU Session Establishment Reject message, the PDU Session Establishment Reject message including a rejection cause indicating that the UE or the application is not entitled to the service in the S-NSSAI and the DNN. [Brief explanation of the drawings]

[0022] [Figure 1] FIG. 1 is a signaling diagram of a first example of a first aspect (UE policy query from an application function). [Figure 2] FIG. 2 is a signaling diagram of a second example of the first aspect (UE policy query from an application function via NEF and AMF). [Figure 3] FIG. 3 is a signaling diagram of a third example of the first aspect (UE policy query from application function via PCF). [Figure 4] FIG. 4 is a signaling diagram of a fourth example of the first aspect (UE policy obtained from PCF). [Figure 5] FIG. 5 is a signaling diagram of a first example of the second embodiment (monitoring of external application services via NWDAF). [Figure 6] FIG. 6 is a signaling diagram of a second example of the second embodiment (monitoring of external application services via NSACF). [Figure 7] FIG. 7 is a diagram showing an outline of the system. [Figure 8] FIG. 8 is a block diagram illustrating a user equipment (UE). [Figure 9] FIG. 9 is a block diagram illustrating an (R)AN node. [Figure 10] FIG. 10 is a diagram illustrating a system overview of an (R)AN node based on the O-RAN architecture. [Figure 11] FIG. 11 is a block diagram showing a radio unit (RU). [Figure 12] FIG. 12 is a block diagram showing a distributed unit (DU). [Figure 13] FIG. 13 is a block diagram showing a centralized unit (CU). [Figure 14] FIG. 14 is a block diagram illustrating the Access and Mobility Management Function (AMF). [Figure 15] FIG. 15 is a block diagram illustrating the Session Management Function (SMF). [Figure 16] FIG. 16 is a block diagram illustrating the User Plane Function (UPF). [Figure 17] FIG. 17 is a block diagram illustrating a Policy Control Function (PCF). [Figure 18] FIG. 18 is a block diagram illustrating the Authentication Server Function (AUSF). [Figure 19] FIG. 19 is a block diagram illustrating Unified Data Management (UDM). [Figure 20] FIG. 20 is a block diagram illustrating the Network Data Analytics Function (NWDAF). [Figure 21] FIG. 21 is a block diagram illustrating the Network Exposure Function (NEF). [Figure 22] FIG. 22 is a block diagram illustrating a Network Slice Admission Control Function (NSACF). [Figure 23] FIG. 23 is a block diagram showing an Application Function (AF). DETAILED DESCRIPTION OF THE INVENTION

[0023] <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.

[0024] 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 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 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 NSACF Network Slice Admission Control 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 PDB Packet Delay Budget PDR Packet Detection Rule PDU Protocol Data Unit PEI Permanent Equipment Identifier PER Packet Error Rate PFD Packet Flow Description 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 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 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

[0025] <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.

[0026] <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.

[0027] 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.

[0028] 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.

[0029] 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.

[0030] 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.

[0031] 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.

[0032] 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.

[0033] 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.

[0034] In the following aspects, the URSP rules may be included in the UE policy.

[0035] In the following aspects, a URSP rule may be expressed as a URSP policy or a UE policy.

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

[0037] A method for a communications device according to an exemplary aspect of the present disclosure includes transmitting information requesting User Equipment Route Selection Policy (URSP) rules. The method includes receiving the URSP rules when transmitting the information.

[0038] A method for a User Equipment (UE) according to an exemplary aspect of the present disclosure includes receiving information requesting a User Equipment Route Selection Policy (URSP) rule, and, if the information is received, transmitting the URSP rule.

[0039] A method of a communications device according to an exemplary aspect of the present disclosure includes receiving information requesting User Equipment Route Selection Policy (URSP) rules, and, if the method receives the information, transmitting the URSP rules.

[0040] A method for a communications device according to an exemplary aspect of the present disclosure includes transmitting information to request monitoring of traffic routing, and, upon transmitting the information, receiving results of the monitoring of traffic routing.

[0041] A method for a communications device according to an exemplary aspect of the present disclosure includes receiving information for requesting traffic routing monitoring. After receiving the information, the method includes performing a validation check on a User Equipment Route Selection Policy (URSP) rule. If the validation check is successful, the method includes transmitting the information for monitoring the traffic routing.

[0042] A method for a communications device according to an exemplary aspect of the present disclosure includes receiving information for monitoring traffic routing, monitoring the traffic routing based on the information, and transmitting results of the traffic routing monitoring.

[0043] A method of a communications device according to an exemplary aspect of the present disclosure includes receiving results of traffic routing monitoring, the method including transmitting the results.

[0044] A method for a User Equipment (UE) according to an example aspect of the present disclosure includes transmitting a Protocol Data Unit (PDU) Session Establishment Request message. The PDU Session Establishment Request message includes a Data Network Name (DNN), a Single Network Slice Selection Assistance Information (S-NSSAI), and an identifier of an application for which the UE is requesting service. The method includes receiving a PDU Session Establishment Reject message. The PDU Session Establishment Reject message includes a rejection cause indicating that the UE or the application is not entitled to the service in the S-NSSAI and the DNN.

[0045] 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 configured to transmit information requesting User Equipment Route Selection Policy (URSP) rules, and the at least one hardware processor configured to receive the URSP rules when transmitting the information.

[0046] A User Equipment (UE) 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 information requesting a User Equipment Route Selection Policy (URSP) rule, and, upon receiving the information, the at least one hardware processor configured to transmit the URSP rule.

[0047] 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 configured to receive information requesting a User Equipment Route Selection Policy (URSP) rule, and, upon receiving the information, the at least one hardware processor configured to transmit the URSP rule.

[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 configured to transmit information to request traffic routing monitoring, and, when transmitting the information, to receive results of the traffic routing monitoring.

[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 information for requesting traffic routing monitoring. After receiving the information, the at least one hardware processor is configured to perform a validation check on a User Equipment Route Selection Policy (URSP) rule. If the validation check is successful, the at least one hardware processor is configured to transmit the information for monitoring the traffic routing.

[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 information for monitoring traffic routing. The at least one hardware processor is configured to monitor the traffic routing based on the information. The at least one hardware processor is configured to transmit results of the monitoring of the traffic routing.

[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 configured to receive results of traffic routing monitoring, and the at least one hardware processor configured to transmit the results.

[0052] A User Equipment (UE) 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 transmit a Protocol Data Unit (PDU) session establishment request message. The PDU session establishment request message includes a Data Network Name (DNN), a Single Network Slice Selection Assistance Information (S-NSSAI), and an identifier of an application for which the UE requests service. The at least one hardware processor is configured to receive a PDU session establishment reject message. The PDU session establishment reject message includes a reject cause indicating that the UE or the application is not entitled to service in the S-NSSAI and the DNN.

[0053] <First aspect> In 5G deployments, operators may restrict the use of a particular network slice to some particular third-party service provider (e.g., based on a combination of S-NSSAI and DNN), which can be achieved by configuring appropriate URSP rules in the PCF and provisioning them on the UE side, but currently the 5G network is not aware of whether URSP is being implemented by the UE, and it may be necessary to make the network aware when a third-party service provider's application is routed using the provisioned URSP rules.

[0054] To enable a third party service provider to know which network slice (or URSP rule) is being used for its application, the present aspect discloses a mechanism that allows a third party service provider to inquire about the network slice (or URSP rule) being used within the operator network.

[0055] <First Example of First Aspect> A first example of the first aspect discloses a method in which the AF 201 provides a query request to the PLMN using application identity information to obtain a UE policy (e.g., a URSP rule). The UE policy may be used, for example, to allocate network resources for the application indicated by the AF 201. The PLMN uses the NWDAF 76 as a contact point for the query.

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

[0057] Step 1. The AF 201 sends an Nnef_AnalyticsExposure_Subscribe message containing a user ID and a URSP collection parameter to the NEF 77. The user ID may be an identifier of the UE 3. The AF 201 may be controlled by a third-party service provider.

[0058] The URSP collection parameters can be one or a combination of the following parameters: -(list of) application identifiers (e.g., APL ID) -(list of) application descriptors (e.g., OS identifiers (IDs)) -(List of) application descriptors (e.g., OS ID+APL ID) Event. An event indicates a request from the AF 201. For example, an event may indicate information that the AF 201 requests. An event may be identified by an event ID. The event ID (or event) may be one of the following parameters: --URSP Policy in the UE --Session status of the application. --UE location

[0059] The event ID may be included in the Nnef_AnalyticsExposure_Subscribe message. The event ID may be included in the Nnef_AnalyticsExposure_Subscribe message instead of an event. A URSP policy (e.g., a URSP rule) in the UE may correspond to at least one of an application identifier and an application descriptor. For example, if AF201 controlling application 1 wants to recognize the URSP policy for application 1, AF201 may include at least one of an application identifier that identifies application 1 and an application descriptor corresponding to application 1 in the Nnef_AnalyticsExposure_Subscribe message. In this case, AF201 may set corresponding parameters in the event. For example, if AF201 wants to recognize the URSP policy for application 1, AF201 may include the event set in the URSP policy in the Nnef_AnalyticsExposure_Subscribe message. For example, if AF201 wants to know the session state of application 1, AF201 may include an event set to session state in the Nnef_AnalyticsExposure_Subscribe message. For example, if AF201 wants UE3 to know the UE location where application 1 is running, AF201 may include an event set to UE location in the Nnef_AnalyticsExposure_Subscribe message.

[0060] Step 2. Upon receiving the Nnef_AnalyticsExposure_Subscribe message from the AF 201, the NEF 77 sends a Nnwdaf_AnalyticsSubscription_Subscribe message containing the user ID and URSP set parameters to the NWDAF 76. The user ID and URSP set parameters in the Nnwdaf_AnalyticsSubscription_Subscribe message may be the same as those in the Nnef_AnalyticsExposure_Subscribe message.

[0061] Step 3. The NWDAF 76 sends a Nudm_UECM_Get message including the user ID to the UDM 75 to find the AMF with which the UE 3 is associated. If the NWDAF 76 knows the AMF with which the UE 3 is associated, step 3 may be skipped.

[0062] Step 4. The UDM 75 sends a Nudm_UECM_Get response message including the AMF ID to the NWDAF 76. In this disclosure, the AMF ID may indicate the AMF with which the UE 3 is associated.

[0063] Step 5. The NWDAF 76 sends a Namf_EventExposure subscribe message to the AMF 70, including the user ID and the event ID set in "URSP Set." In the present disclosure, the event ID set in "URSP Set" may indicate the URSP Set parameter. The Namf_EventExposure subscribe message may include an event parameter that includes the URSP Set parameter. The Namf_EventExposure subscribe message may include an event parameter or a URSP Set parameter.

[0064] Step 6. If the UE 3 is in CM idle state in both the 3GPP access and the non-3GPP access, the AMF 70 performs a paging procedure in the 3GPP access to establish a connection with the UE 3. For example, the AMF 70 may page the UE 3 identified by the received user ID.

[0065] Step 7. The AMF 70 sends a NAS request message including the URSP set parameters to the UE 3. The NAS request message may be a DL NAS transport message, a UE configuration update command message, an identity information request message, or any other NAS message. Upon receiving the NAS request message from the AMF 70, the UE 3 finds related UE policy information (e.g., URSP rules) and other requested information from the AMF 70 and stores them in the URSP information parameters. For example, the UE 3 may find related UE policy information and other requested information corresponding to the URSP set parameters. The URSP information parameters may be represented as URSP information or information related to the URSP rules, or URSP rules. For example, the AMF 70 may send a NAS request message to the UE 3 identified by the received user ID.

[0066] Step 8. The UE 3 sends a NAS response message including the URSP information parameter to the AMF 70. The NAS response message can be a UL NAS transport message, a UE configuration update complete message, an identity response message, or any NAS message. The URSP information parameter can be one or a combination of the following parameters:

[0067] - (List of) Route Selection Descriptors for designated application, i.e., both route selection components and route selection validation criteria, corresponding to the designated application descriptor or designated application identifier. The application identifier may be expressed as an APL ID.

[0068] If the event in the received URSP set parameter indicates "application session status", (list of) the PDU session status of the designated application. The PDU session status may be whether a PDU session for the designated application is established. If a PDU session is established, the associated S-NSSAI, associated DNN, assigned IP address, access type (3GPP access or non-3GPP access), SSC mode, and session ID may be included in this parameter.

[0069] For example, if UE3 receives a URSP set parameter for application 1 (e.g., if the application identifier or application descriptor in the URSP set parameter indicates application 1, or if UE3 determines that the application identifier or application descriptor in the URSP set parameter is for application 1), UE3 transmits a URSP information parameter for application 1. For example, if UE3 receives a URSP set for application 1, UE3 transmits a URSP information parameter including a route selection descriptor for application 1. In this case, if the URSP set parameter indicates "application session state," UE3 includes the PDU session state of application 1 in the URSP information parameter. The PDU session state of application 1 may include the S-NSSAI, DNN, IP address access type, SSC mode, and session ID associated with application 1.

[0070] Step 9. The AMF 70 sends a Namf_EventExposure subscribe response message to the NWDAF 76, including the user ID, URSP information, TAI, and PLMN ID. In the present disclosure, the TAI may be referred to as TAI information. If the event in the URSP set parameter received in the Namf_EventExposure subscribe message indicates "UE location," the AMF 70 may include the TAI information where the UE 3 is located in the Namf_EventExposure subscribe response message. The AMF 70 may include the PLMN ID, i.e., either the PLMN name or the PLMN identification information comprising the MCC and MNC of the PLMN to which the AMF 70 belongs, in the Namf_EventExposure subscribe response message. The URSP information may be included in the event parameter of the Namf_EventExposure subscribe response message. The user ID may be an identifier of the UE 3. The user ID may be the same as that in the Namf_EventExposure subscribe message. The URSP information may be the same as that in the NAS response message.

[0071] Step 10. The NWDAF 76 sends a Nnwdaf_EventExposure notification message containing the User ID, TAI, and PLMN ID to the NEF 77. The Nnwdaf_EventExposure notification message may contain URSP information. The Nnwdaf_EventExposure notification message may contain the PLMN name or PLMN identity information comprising the MCC and MNC of the PLMN to which the AMF 70 belongs.

[0072] Step 11. The NEF 77 sends an Nnef_EventExposure notification message to the AF 201, including the user ID, URSP information, UE location information, and PLMN ID. When the NEF 77 receives the TAI information from the NWDAF 76 in the Nnwdaf_EventExposure notification message, the NEF 77 converts the received TAI information into UE location information, including a location formed from a general city name, zip code, GPS location, or expressed in urban and geospatial location format as defined in 3GPP TS 23.0100, 2013. The Nnef_EventExposure notification message may include the PLMN name or PLMN identity information comprising the MCC and MNC of the PLMN to which the AMF 70 belongs. The NEF 77 may send an Nnef_AnalyticsSubscription_Notify message, including the user ID, URSP information, UE location information, and PLMN ID, instead of the Nnef_EventExposure notification message.

[0073] According to the above, for example, the 5G network and the third party service provider (e.g., AF201) can recognize which network slice (or URSP rule) is being used for the third party service provider's application within the operator network.

[0074] <Second Example of First Aspect> A second example of the first aspect discloses a method in which the AF 201 provides a query request to the PLMN using application identity information to obtain a UE policy (e.g., a URSP rule). The UE policy can be used, for example, to allocate network resources for the application indicated by the AF 201. The NEF 77 contacts the AMF 70 for the query.

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

[0076] Step 1. This step 1 is the same as step 1 in FIG.

[0077] Step 2. If the NEF 77 does not know the AMF ID for the UE 3, the NEF 77 sends a Nudm_UECM_Get message containing the user ID of the UE 3 to the UDM 75 to find the AMF with which the UE 3 is associated. If the NEF 77 knows the AMF with which the UE 3 is associated, step 2 may be skipped.

[0078] Step 3. Upon receiving the Nudm_UECM_Get message, the UDM 75 sends a Nudm_UECM_Get response message to the NEF 77 including an AMF ID that identifies the AMF with which the UE 3 is associated.

[0079] Step 4. The NEF 77 sends a Namf_EventExposure subscribe message to the AMF 70, including the user ID and the event ID set in the "URSP set". The Namf_EventExposure subscribe message may include an event parameter that includes a URSP set parameter. The Namf_EventExposure subscribe message may include an event parameter or a URSP set parameter.

[0080] Steps 5, 6, and 7 are the same as steps 6, 7, and 8 in FIG. 1, respectively.

[0081] Step 8. The AMF 70 sends a Namf_EventExposure subscribe response message to the NEF 77, including the user ID, URSP information, TAI, and PLMN ID. If the event in the URSP set parameter received in the Namf_EventExposure subscribe message indicates "UE location," the AMF 70 may include the TAI information where the UE 3 is located in the Namf_EventExposure subscribe response message. The AMF 70 may include the PLMN ID, i.e., either the PLMN name or the PLMN identification information comprising the MCC and MNC of the PLMN to which the AMF 70 belongs, in the Namf_EventExposure subscribe response message. The URSP information may be included in the event parameter of the Namf_EventExposure subscribe response message. The user ID may be the identifier of the UE 3. The user ID may be the same as that in the Namf_EventExposure subscribe message. The URSP information may be the same as that in the NAS response message.

[0082] Step 9. The NEF 77 sends an Nnef_EventExposure notification message to the AF 201, including the user ID, URSP information, UE location information, and PLMN ID. When the NEF 77 receives the TAI information from the AMF 70 in the Nnef_EventExposure subscribe response message, the NEF 77 converts the received TAI information into UE location information, including a location formed from a general city name, zip code, GPS location, or expressed in urban and geospatial location format as defined in 3GPP TS 23.110.2013. The Nnef_EventExposure notification message may include the PLMN name or PLMN identification information comprising the MCC and MNC of the PLMN to which the AMF 70 belongs. Instead of the Nnef_EventExposure notification message, the NEF 77 may send an Nnef_AnalyticsSubscription_Notify message, including the user ID, URSP information, UE location information, and PLMN ID.

[0083] According to the above, for example, the 5G network and the third party service provider (e.g., AF201) can recognize which network slice (or URSP rule) is being used for the third party service provider's application within the operator network.

[0084] <Third Example of the First Aspect> A third example of the first aspect discloses a method in which the AF 201 provides a query request to the PLMN using application identity information to obtain a UE policy (e.g., a URSP rule). The UE policy may be used, for example, to allocate network resources for the application indicated by the AF 201. The PLMN uses the PCF 73 as a contact point for the query.

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

[0086] Step 1. This step 1 is the same as step 1 in FIG.

[0087] Step 2. Upon receiving the Nnef_AnalyticsExposure_Subscribe message from the AF 201, the NEF 77 sends an Npcf_UEPolicyControl_query message or any other message of the PCF service to the PCF 73, containing the user ID and URSP set parameters.

[0088] Step 3. The PCF 73 sends a Namf_EventExposure subscribe message to the AMF 70, including the user ID and the event ID set in the "URSP set". The Namf_EventExposure subscribe message may include an event parameter including a URSP set parameter. The Namf_EventExposure subscribe message may include an event parameter or a URSP set parameter.

[0089] Steps 4, 5, and 6 are the same as steps 6, 7, and 8 in FIG. 1, respectively.

[0090] Step 7. The AMF 70 sends a Namf_EventExposure subscribe response message to the PCF 73, including the user ID, URSP information, TAI, and PLMN ID. If the event in the URSP set parameter received in the Namf_EventExposure subscribe message indicates "UE location," the AMF 70 may include the TAI information where the UE 3 is located in the Namf_EventExposure subscribe response message. The AMF 70 may include the PLMN ID, i.e., either the PLMN name or the PLMN identification information comprising the MCC and MNC of the PLMN to which the AMF 70 belongs, in the Namf_EventExposure subscribe response message. The URSP information may be included in the event parameter of the Namf_EventExposure subscribe response message. The user ID may be the identifier of the UE 3. The user ID may be the same as that in the Namf_EventExposure subscribe message. The URSP information may be the same as that in the NAS response message.

[0091] Step 8. The PCF 73 sends an Npcf_UEPolicyControl_query Reply message or any other message of a PCF service including the user ID, URSP information, and PLMN ID to the NEF 77. The Npcf_UEPolicyControl_query Reply message or any other message of a PCF service may include the TAI. The Npcf_UEPolicyControl_query Reply message or any other message of a PCF service may include the PLMN name or PLMN identity information comprising the MCC and MNC of the PLMN to which the AMF 70 belongs. In the present disclosure, the Npcf_UEPolicyControl_query Reply message may be referred to as an Npcf_UEPolicyControl_query Response message.

[0092] In step 9, NEF77 sends an Nnef_EventExposure notification message containing the user ID, URSP information, UE location information, and PLMN ID to AF201. When NEF77 receives TAI information from PCF73 in the Npcf_UEPolicyControl_query response message, NEF77 converts the received TAI into UE location information including a location represented by a general city name, zip code, GPS location, or a city and geospatial location format as defined in Non-Patent Document 7. The Nnef_EventExposure notification message may include PLMN identification information including the PLMN name or the MCC and MNC of the PLMN to which AMF70 belongs. Instead of the Nnef_EventExposure notification message, NEF77 may send an Nnef_AnalyticsSubscription_Notify message containing the user ID, URSP information, UE location information, and PLMN ID.

[0093] According to the above, for example, a 5G network and a third-party service provider (e.g., AF201) can recognize which network slice (or URSP rule) is being used for the third-party service provider's application within the operator network.

[0094] <Variant 1 of the third example of the first aspect> <The AF contacts the PCF directly> In this variant, AF201 contacts PCF73 directly for UE policy query. In the present disclosure, the UE policy query may be represented as a URSP rule query. In this case, the following substitutions from FIG. 3 are applicable.

[0095] - Step 1 is replaced with an Npcf_UEPolicyControl_query message from AF201 to PCF73 or any other message of the PCF service. The Npcf_UEPolicyControl_query message includes the user ID and the URSP set parameter.

[0096] -Step 2 is disabled.

[0097] Step 8 is replaced by an Npcf_UEPolicyControl_query response message from the PCF 73 to the AF 201 or any other message of the PCF service. The Npcf_UEPolicyControl_query response message includes the user ID, URSP information, TAI or user location information (or UE location information), and PLMN ID. The TAI may be included if the TAI is understandable by the AF 201 when the AF 201 may be within the operator domain; otherwise, the PCF 73 converts the received TAI into user location information (or UE location information) including a location formed by a common city name, zip code, GPS location, or expressed in city and geospatial location format as defined in 3GPP TS 26.0100, 2013.

[0098] -Step 9 is disabled.

[0099] <Fourth Example of the First Aspect> A fourth example of the first aspect discloses a method in which the AF 201 provides a query request to the PLMN using application identity information to obtain a UE policy (e.g., a URSP rule). The UE policy may be used, for example, to allocate network resources for the application indicated by the AF 201. The PLMN obtains the UE policy from the PCF 73.

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

[0101] Step 1. This step 1 is the same as step 1 in FIG.

[0102] Step 2. This step 2 is the same as step 2 in FIG.

[0103] Step 3. Upon receiving the Npcf_UEPolicyControl_query message or any other message of the PCF service from the NEF 77, the PCF 73 collects the URSP policy and the request information according to the URSP set parameters for the UE 3. If the PCF 73 subscribes to the UE location-related service provided by the AMF 70, the TAI where the UE 3 is currently located can be collected by the PCF 73. The URSP policy and the request information for the UE 3 can be represented as URSP information. For example, the PCF 73 can collect the request information according to the URSP policy and the URSP set parameters for the UE 3 based on the stored information in the PCF 73.

[0104] The PCF 73 sends an Npcf_UEPolicyControl_query response message or any other message of the PCF service containing the user ID, URSP information, TAI, and PLMN ID to the NEF 77. The PCF 73 may include the PLMN ID, i.e., either the PLMN name or the PLMN identification information comprising the MCC and MNC of the PLMN to which the PCF 73 belongs, in the Npcf_UEPolicyControl_query response message or any other message of the PCF service.

[0105] Step 4. NEF77 sends an Nnef_EventExposure notification message containing the user ID, URSP information, UE location information, and PLMN ID to AF201. When NEF77 receives TAI information from PCF73 in an Npcf_UEPolicyControl_query response message or any other message of the PCF service, NEF77 converts the received TAI information into UE location information including a location represented in the name of a general city, zip code, GPS location, or a city and geospatial location format as defined in Non-Patent Document 7. Instead of the Nnef_EventExposure notification message, NEF77 may send an Nnef_AnalyticsSubscription_Notify message containing the user ID, URSP information, UE location information, and PLMN ID to AF201. The Nnef_EventExposure notification message may include either the PLMN name or the PLMN identification information including the MCC and MNC of the PLMN to which PCF73 belongs.

[0106] According to the above, for example, a 5G network and a third-party service provider (e.g., AF201) can recognize which network slice (or URSP rule) is being used for the third-party service provider's application within the operator network.

[0107] <Variant 1 of the fourth example of the first aspect> <AF contacts the PCF directly> In this variant, AF201 contacts PCF73 directly for UE policy query. In this case, the following substitutions from FIG. 4 apply.

[0108] - Step 1 is replaced with an Npcf_UEPolicyControl_query message or any other message of the PCF service from AF201 to PCF73. The Npcf_UEPolicyControl_query message includes the user ID and the URSP set parameter.

[0109] -Step 2 is disabled.

[0110] Step 3 is replaced by an Npcf_UEPolicyControl_query response message from the PCF 73 to the AF 201 or any other message of the PCF service. The Npcf_UEPolicyControl_query response message includes a URSP information parameter. The Npcf_UEPolicyControl_query response message may include a user ID. The TAI information may be set in the URSP information if the TAI may be understandable by the AF 201 when the AF 201 may be within the operator domain.

[0111] -Step 4 is disabled.

[0112] <Second aspect> In 5G deployments, operators may restrict the use of a particular network slice to some particular third-party service provider (e.g., based on a combination of S-NSSAI and DNN), which can be achieved by configuring appropriate URSP rules in the PCF and provisioning them on the UE side, but currently the 5G network is not aware of whether URSP is being implemented by the UE, and it may be necessary to make the network aware when a third-party service provider's application is routed using the provisioned URSP rules.

[0113] A second aspect discloses a method for monitoring and controlling the use of services provided by an external service provider, e.g., an AF, by a 3GPP network, such that services in the S-NSSAI and DNN provided by the external service provider can only be used by UEs and applications that are entitled to such services via URSP rules provided to the UE.

[0114] <First example of the second aspect> The first example of the second aspect in Figure 5 proposes a solution for access control and monitoring for services provided in S-NSSAI and DNN by external service providers, where access control is performed by PCF73 and monitoring is performed by NWDAF76.

[0115] The detailed process of the first example of the second embodiment is as follows.

[0116] Step 1. AF Request Creation—The AF 201 may provide service specific parameters to the 5G system via the NEF 77 as specified in section 4.15.6.7 of 3GPP TS 36.210. The AF 201 may issue the request on behalf of an external application that may or may not be owned by the PLMN serving the UE 3.

[0117] Step 2. The AF 201 sends an Nnef_ServiceParameter_Create / Update message to the NEF 77. The Nnef_ServiceParameter_Create / Update message includes the App_ID, ext_UE_ID, S-NSSAI, DNN, and traffic routing monitoring required. The Nnef_ServiceParameter_Create / Update message may include location_info. The location_info may be expressed as location information. The App_ID may identify the service provider, i.e., the AF 201. The ext_UE_ID may be in the form of GPSI or external group identity. The AF 201 includes the S-NSSAI and DNN in the message to identify the service provided by the AF 201. The AF201 may also include in the message to the NEF77 a "required traffic routing monitoring" parameter or any other indication of a parameter that identifies a request by the AF201 to the 3GPP system regarding monitoring and access control for services provided by the combination of the S-NSSAI and the DNN, for example, whether the UE3 and / or application on the UE3 requesting a service in the S-NSSAI and / or the DNN is entitled to that service according to the URSP rules for that UE3. In this disclosure, the "required traffic routing monitoring" parameter may be referred to as "required traffic routing monitoring." The "required traffic routing monitoring" parameter may be referred to as information for requesting monitoring of traffic routing.

[0118] If AF201 includes the "required traffic routing monitoring" parameter, the 3GPP system monitors and controls the use of services provided by at least one of the S-NSSAI and the DNN. For example, the 3GPP system may deny service from applications and UEs that are not entitled to the service based on the latest URSP rules provided to the UE by the 3GPP system. If AF201 includes the location_info parameter, the use of services in the S-NSSAI and the DNN, e.g., PDU sessions, may be monitored and controlled by the network only at locations identified by the location_info parameter, which may be expressed in a geographical or any other manner.

[0119] Step 3. The NEF 77 stores the AF 201 requested information in the UDM 75 in the "Application Data" section, and also performs any mapping such as ext_UE_ID to 3GPP UE identity (e.g., GPSI to SUPI), or service identity to S-NSSAI and DNN if the AF 201 provides a service identity instead of S-NSSAI and DNN. If location_info is provided by the AF 201, the NEF 77 maps the provided location_info to 3GPP-compatible location information, e.g., 3gpp_location_info, defined as one or more cells or one or more TAs. The NEF 77 also stores the "Required Traffic Routing Monitoring" parameter in the UDM 75. The NEF 77 may store the 3GPP-compatible location information from the "3gpp_location_info" parameter associated with the UE_ID (e.g., SUPI), if provided by the AF 201. Alternatively, the "required traffic routing monitoring" parameter and the "3gpp_location_info" parameter may be stored in the UDM 75 by a network operator based on an SLA agreement with an external service provider, i.e., the AF 201. In the present disclosure, the "required traffic routing monitoring" parameter may be represented as a "required traffic routing monitoring" flag. The NEF 77 may store the above information in the UDM.

[0120] Step 4. The UDM 75 sends a Nudr_DM_Notify message to the PCF 73 according to section 5.2.12.2.1-1 in Non-Patent Document 5. The Nudr_DM_Notify message may include the App_ID, the UE_ID, the S-NSSAI, the DNN, the required traffic routing monitoring, and 3gpp_location_info. For example, if the UE 3 registers with the network and the PCF 73 subscribes to notifications by the UDM 75 when application data for the UE 3 is modified, the UDM 75 may send the Nudr_DM_Notify message to the PCF 73. For example, if the information mentioned in step 3 is stored in the UDM 75, e.g., in the UDR of the UDM 75. The UDR of the UDM 75 may send the Nudr_DM_Notify message to the PCF 73.

[0121] Step 5. The PCF 73 updates the UE policy (i.e., URSP rule) for the UE 3 indicated by the Nudr_DM_Notify message from the UDM 75, and the PCF 73 stores the traffic monitoring required parameter and the 3gpp_location_info parameter in the PCC rule in the PCF 73 for the UE 3. The PCF 73 may associate and store the App_ID, UE_ID, S-NSSAI, DNN, the required traffic monitoring parameter, and the 3gpp_location_info parameter.

[0122] Step 6. The PCF 73 provides the updated UE policy with the updated URSP rules to the UE 3 via the UE policy update procedure according to section 4.2.4.3 in Non-Patent Document 5.

[0123] Step 7. At some stage, an application in UE 3 having an App_ID requests a service in at least one of S-NSSAI and DNN. In this case, UE 3 sends a PDU Session Establishment Request message to AMF 70. UE 3 includes the PDU_Session_ID, DNN, and S-NSSAI in the PDU Session Establishment Request message. UE 3 also includes a service application identification (i.e., App_ID) in the PDU Session Establishment Request message to AMF 70. In the present disclosure, the service application identification may be represented as App_ID. App_ID may be an application identifier or an OS identifier, or a combination of an application identifier and an OS identifier. In the present disclosure, this definition of App_ID may be valid for the entire second aspect. In the present disclosure, App_ID may be represented as App-ID. In the present disclosure, App_ID may be identification information of the application in UE 3 requesting a service in at least one of S-NSSAI and DNN.

[0124] Step 8. The AMF 70 selects an SMF 71 in accordance with the requirements in Non-Patent Document 5 and sends an Nsmf_PDUSession_CreateSMContext request message to the SMF 71. The AMF 70 includes the UE_ID, PDU_Session_ID, DNN, and S-NSSAI parameters received from the UE 3 in the Nsmf_PDUSession_CreateSMContext request message. The AMF 70 also includes an application identifier (i.e., App_ID), UE location, and PLMN ID in the Nsmf_PDUSession_CreateSMContext request message to the SMF 71.

[0125] The AMF 70 may include in the Nsmf_PDUSession_CreateSMContext request message a PLMN ID, i.e., either a PLMN name or PLMN identification information comprising the MCC and MNC of the PLMN to which the AMF 70 belongs. In the present disclosure, the UE location may be represented as UE_location information.

[0126] The UE location may indicate location information of the UE 3, for example, the TAI where the UE 3 is located. The UE location may not be included in the Nsmf_PDUSession_CreateSMContext request message. The UE_ID may be an identifier of the UE 3.

[0127] Step 9. The SMF 71 triggers a policy association with the PCF 73 and sends an Npcf_SMPpolicy_Control_Create message to the PCF 73. The SMF 71 includes the UE_ID, PDU_Session_ID, DNN, S-NSSAI, and PLMN ID received from the AMF 70 as parameters in the Npcf_SMPpolicy_Control_Create message. The SMF 71 also includes the App_ID and UE_location information in the Npcf_SMPpolicy_Control_Create message to the PCF 73. If the UE_location information has been provided to the SMF 71, the SMF 71 may include the UE_location information in the Npcf_SMPpolicy_Control_Create message.

[0128] Step 10. Ursp Validation—If the PCF 73 does not have the subscriber's subscription-related information, it sends a request to the UDM 75 by invoking the Nudr_DM_Query service to receive information related to the Session_ID of the PDU. The Nudr_DM_Query service or Nudr_DM_Query message may include a SUPI (e.g., the SUPI of the UE 3), a DNN, and an S-NSSAI. The PCF 73 may request notification from the UDM 75 regarding changes in subscription information by invoking a Nudr_DM_Subscribe message according to session 4.16.9 in 3GPP TS 23.2006-01-01 16:20 Page 17 of 21. The PCF 73 checks the UE's Ursp validity, i.e., whether the UE 3 or an application in the UE 3 is entitled to the service in the requested S-NSSAI and DNN. For example, the PCF 73 may verify whether the application identification information (i.e., App_ID) in the UE 3 can be mapped to the S-NSSAI and DNN provided in the Npcf_SMPpolicy_Control_Create message from the SMF 71. The PCF 73 verifies the PDU session routing rules for the UE 3 from the latest URSP rules for the UE 3 stored in the PCF 73. To pass the URSP validation, the App_ID mapping to the S-NSSAI and DNN, and optionally the PDU_Session_ID, in the URSP rule copy for the UE 3 stored in the PCF 73 must match the App_ID, S-NSSAI and DNN, and optionally the PDU_Session_ID parameters provided from the AMF 70, i.e., the URSP rule copy for the UE 3 provided by the UE 3 and the URSP rule copy for the UE 3 stored in the PCF 73 must match. If 3gpp_location_info is provided to the PCF 73, the PCF 73 checks whether the location of the UE 3 is among the locations provided via 3gpp_location_info.If the location of UE3 is outside the location provided via 3gpp_location_info, UE3 is not entitled to the service in S-NSSAI and DNN even if the App_ID requesting the service is mapped to S-NSSAI and DNN (e.g., passes URSP validation). For example, the PCF73 determines that the URSP validity check of the UE passes (e.g., the PCF73 determines that the URSP rules of the UE3 provided by the UE3 match the URSP rules of the UE3 stored in the PCF73, or the PCF73 determines that the combination of the App_ID, S-NSSAI and DNN, and optionally the Session_ID of the PDU stored in the PCF73 in step 5 matches the combination of the App_ID, S-NSSAI and DNN, and optionally the PDU_Session_ID received from the AMF70 via the SMF71), and the PCF73 determines that the App_ID in the UE3 is entitled to the service in the requested S-NSSAI and DNN. If 3gpp_location_info is not provided to the PCF73, the PCF73 may skip checking whether the location of the UE3 is among the locations provided via 3gpp_location_info.

[0129] Step 11. As a result of the URSP validation by the PCF 73 (e.g., the PCF 73 determines that the App_ID in UE 3 is entitled to the service in the requested S-NSSAI and DNN, and optionally the Session_ID in the PDU), if the App_ID in UE 3 and UE 3 itself are entitled to the service in the requested S-NSSAI and DNN, the PCF 73 sends a Nnwdaf_ServiceMonitoring_Request message to the NWDAF 76. The PCF 73 includes the App_ID, UE_ID, S-NSSAI, DNN, 3gpp_location_info, PLMN ID, and optionally the Session_ID in the PDU in the Nnwdaf_ServiceMonitoring_Request message. Alternatively, the PCF 73 may utilize any other existing or new message between the PCF 73 and the NWDAF 76 to convey the App_ID, UE_ID, S-NSSAI, DNN, 3gpp_location_info, and PLMN ID for the purpose of monitoring service usage for the S-NSSAI and DNN, and optionally the PDU_Session_ID. If the 3gpp_location_info is provided to the PCF 73, the PCF 73 may include the 3gpp_location_info in the Nnwdaf_ServiceMonitoring_Request message. In the present disclosure, at least one of the App_ID, UE_ID, S-NSSAI, DNN, 3gpp_location_info, PLMN ID, and Session_ID of the PDU may be collectively referred to as information for monitoring traffic routing.

[0130] Step 12. The NWDAF 76 starts monitoring traffic routing for the S-NSSAI and DNN according to the App_ID at the UE 3, and optionally the PDU session having the PDU_Session_ID, if provided. For example, the NWDAF 76 starts monitoring traffic routing for the S-NSSAI and DNN, and optionally the PDU_Session_ID, corresponding to the App_ID provided by the PCF 73. If the PCF 73 includes 3gpp_location_info, the monitoring applies to the location defined in the 3gpp_location_info parameter. The location information may be defined for one or more cells or one or more TAs. If the 3gpp_location_info parameter is provided by the PCF 73, the NWDAF 76 may subscribe to location tracking of the UE 3 by the AMF according to 3GPP TS 23.288, such that the NWDAF 76 may monitor service access to the S-NSSAI and DNN by the UE 3 only if the UE 3 is within the location defined by the 3gpp_location_info parameter.

[0131] Step 13. If the AF 201 subscribes to notifications of traffic routing by the NWDAF 76, the NWDAF 76 may trigger a notification to the NEF 77 each time a service in the S-NSSAI and DNN is accessed. The NWDAF 77 sends a Nnwdaf_Service_Routing notification message to the NEF 77. The NWDAF 76 includes in the Nnwdaf_Service_Routing notification message service_usage_info, which may include information about the App_ID, UE_ID, S-NSSAI, DNN, Session_ID of the PDU, 3gpp_location_info, PLMN ID, and the duration of the service access in the S-NSSAI and DNN. Alternatively, the NWDAF 76 may utilize any other existing or new notification service or message between the NWDAF 76 and the NEF 77 to convey the App_ID, UE_ID, S-NSSAI, DNN, PDU Session_ID, 3gpp_location_info, PLMN ID, and service_usage_info to the NEF 77. If 3gpp_location_info is provided to the NWDAF 76, the NWDAF 76 may include the 3gpp_location_info in an Nnwdaf_Service_Routing notification message. For example, if the NWDAF 77 detects traffic routing for a PDU session with an S-NSSAI and DNN, and optionally a PDU_Session_ID, corresponding to the App_ID, the NWDAF 77 may send an Nnwdaf_Service_Routing notification message. For example, if the AF 201 subscribes to notifications of traffic routing by the NWDAF 76 and the NWDAF 77 detects traffic routing for a PDU session having an S-NSSAI and DNN corresponding to the App_ID and a PDU_Session_ID, the NWDAF 77 may send a Nnwdaf_Service_Routing notification message.

[0132] Step 14. The NEF 77 maps the UE_ID to ext_UE_ID and the 3gpp_location_info to geographical location_info and sends a Nnef_Service_Routing notification message to the AF 201. The Nnef_Service_Routing notification message may include the App_ID, ext_UE_ID, S-NSSAI, DNN, location_info (e.g., geographical location_info), service_usage_info, and PLMN ID. Alternatively, the NEF 77 may utilize any other existing or new notification service or message between the NEF 77 and the AF 201 to convey the App_ID, ext_UE_ID, S-NSSAI, DNN, location_info, and service_usage_info to the AF 201. In the present disclosure, at least one of the App_ID, ext_UE_ID, S-NSSAI, DNN, PDU_Session_ID, location_info (e.g., geographic location_info), service_usage_info, and PLMN ID may be collectively represented as a result of monitoring traffic routing.

[0133] Step 15. If the URSP validation fails in step 10, i.e., if the PCF73 determines that the application in UE3 that requested the service in the S-NSSAI and DNN is not entitled to the service in that S-NSSAI and DNN (for example, if the PCF73 determines that the URSP rules for UE3 provided by UE3 do not match the URSP rules for UE3 stored in PCF73, or if the PCF73 determines that the combination of App_ID, S-NSSAI and DNN, and optionally PDU_Session_ID, stored in PCF73 in step 5 does not match the combination of App_ID, S-NSSAI and DNN, and optionally PDU_Session_ID, received from AMF70 via SMF71), the PCF73 returns an Npcf_SMPolicy_Control_Create response message to SMF71. The PCF 73 includes a Failure result parameter and a reject cause in the Npcf_SMPolicy_Control_Create response message. The reject cause may be set to "URSP rules not followed" or any other indication for the reject cause, indicating that the UE 3 or an application at the UE 3 is not entitled to the service in the requested S-NSSAI and DNN, for example, the URSP rules for the UE 3 do not allow mapping of App_ID to S-NSSAI and DNN. The reason for the service mapping mismatch may either be that the UE 3 does not have the latest URSP rules, i.e., the URSP rules do not match between the URSP copy at the UE 3 and the URSP copy at the PCF 73, or that the UE 3 does not follow the URSP rules.

[0134] Step 16. If the SMF 71 receives an Npcf_SMPolicy_Control_Create response message from the PCF 73 with a failure result and a rejection cause set to "not according to URSP rules", the SMF 71 responds with an Nsmf_PDUSession_CreateSMContext_Response message to the AMF 70. The SMF 71 includes the rejection cause sent by the PCF 73 in the Nsmf_PDUSession_CreateSMContext_Response message.

[0135] Step 17. Upon receiving the Nsmf_PDUSession_CreateSMContext_Response message, AMF 70 rejects the PDU session establishment request from UE 3 by sending a PDU session establishment reject message. AMF 70 includes in the PDU session establishment reject message a reject cause set to "not according to URSP rules" or any other indication for the reject cause, indicating that UE 3 or an application in UE 3 is not entitled to the service in the requested S-NSSAI and DNN, e.g., the URSP rules for UE 3 do not allow mapping of App_ID to S-NSSAI and DNN.

[0136] When UE3 receives a PDU session establishment rejection message with the rejection cause set to "URSP rules not followed," UE3 will not attempt another request for PDU session establishment in the S-NSSAI and DNN where the PDU session establishment was rejected until UE3 receives an update to the URSP rules from the network. If UE3 continues to be rejected multiple times with the same rejection cause set to "URSP rules not followed" (this number may be a 3GPP standard value or may be configurable by configuration in UE3), UE3 will not attempt another PDU session establishment request in the S-NSSAI and DNN until UE3 re-registers.

[0137] According to the above, for example, the 5G network and the third party service provider (e.g., AF201) can recognize when the third party service provider's application is routed using the provisioned URSP rules.

[0138] <Modification 1 of the first example of the second aspect> 5 , before the AMF 70 selects the SMF 71 and triggers an Nsmf_PDUSession_CreateSMContext request message to the SMF 71, the AMF 70 may first interact with the PCF 73 to confirm whether the App_ID from the UE 3 and the UE 3 are entitled to the requested service in the PDU session having the S-NSSAI and DNN, and optionally the PDU-Session_ID provided by the UE 3. In this regard, the AMF 70 may utilize the UE policy association procedure of the AMF 70 with the PCF 73 as defined in Section 4.16.11 in Non-Patent Document 5. To establish the UE policy association with the PCF 73, the AMF 70 sends an Npcf_UEPolicyControl_Create request message to the PCF 73. Along with the parameters related to the policy association, the AMF 70 also includes the App_ID, UE ID, PDU_Session_ID, S-NSSAI, DNN, and UE_location in the Npcf_UEPolicyControl_Create request. Based on these additional parameters provided by the AMF 70, the PCF 73 checks the PDU session routing rules for the UE 3 from the latest URSP rule copy for that UE 3 stored in the PCF 73. To pass the URSP validation, the App_ID mapping to the S-NSSAI and DNN in the URSP rule copy for UE 3 stored in the PCF 73 must match the App_Id, S-NSSAI, DNN, and optionally PDU_Session_ID parameters provided by the AMF 70, i.e., the URSP rule copy for UE 3 provided by the UE and the URSP rule copy for UE 3 stored in the PCF 73 must match. If 3gpp_location_info is provided to the PCF 73, the PCF 73 checks whether the UE_location provided by the AMF 70 is among the locations provided via 3gpp_location_info.If the location of the UE 3 provided in the UE_location parameter from the AMF 70 is outside the location provided via 3gpp_location_info, the UE 3 is not entitled to the service in the S-NSSAI and DNN even if the App_ID requesting the service is correctly mapped to the S-NSSAI and DNN. If the PCF 73 concludes that the App_ID in the UE 3 is not entitled to the service in the PDU session with the requested S-NSSAI and DNN and PDU_Session_ID, i.e., the URSP validation fails, the PCF 73 returns an Npcf_UEPolicyControl_Create response to the AMF 70 with a reject cause set to "not following the URSP rules," and the AMF 70 rejects the PDU session establishment request from the UE in accordance with step 17 of Figure 5. The URSP validation may be performed in the same manner as in the first example of the second aspect. If the PCF 73 concludes that the App_ID in the UE 3 is entitled to the service for the requested S-NSSAI and DNN, and optionally the Session_ID of the PDU, i.e., that the URSP validation has been completed successfully, the PCF 73 may return an Npcf_UEPolicyControl_Create response including information indicating that the URSP validation has been completed successfully. In this case, the AMF 70 may select the SMF 71, and the AMF 70 may trigger an Nsmf_PDUSession_CreateSMContext request message to the SMF 71 including information indicating that the URSP validation has been completed successfully, together with the information mentioned in step 8. Upon receiving the Nsmf_PDUSession_CreateSMContext request message, the SMF 71 may send an Npcf_SMPpolicy_Control_Create message including information indicating that the URSP validation has been completed successfully, together with the information mentioned in step 9.Upon receiving the Npcf_SMPpolicy_Control_Create message, the PCF 73 may determine that the URSP validation has been successfully completed based on the information indicating that the URSP validation has been successfully completed, and may skip the URSP validation. The PCF 73 may then perform the process of step 11.

[0139] <Modification 2 of the first example of the second aspect> In another implementation aspect, URSP rule validation for the UE 3, for example, whether the App_ID of an application in the UE 3 requesting a service in the S-NSSAI and DNN is entitled to the service, may be performed in the AMF 70 instead of the PCF 73 according to the description of FIG. 5 . In this case, after step 7 of FIG. 5 , the AMF 70 may use its UE policy association procedure with the PCF 73 as defined in section 4.16.11 of 3GPP TS 23.02.02.002 to request the PCF 73 for the latest copy of the URSP rules related to the UE 3. The AMF 70 sends an Npcf_UEPolicyControl_Create request message to the PCF 73. Along with parameters related to the policy association, the AMF 70 also includes the UE_ID and a “URSP_required” parameter in the Npcf_UEPolicyControl_Create request message. The “URSP_required” parameter may indicate that the AMF 70 requests the URSP rules for the UE 3 identified by the UE_ID. Alternatively, the AMF 70 may use any other existing or new service or message between the AMF 70 and the PCF 73 to obtain the URSP rules of the UE 3 from the PCF 73. When the PCF 73 receives a request from the AMF 70 to provide the URSP rules for a UE_ID (e.g., the URSP rules for the UE identified by the UE_ID), the PCF 73 responds with an Npcf_UEPolicyControl_Create response message. The PCF 73 includes the UE_ID and the latest copy of the URSP rules for the UE_ID (e.g., the latest copy of the URSP rules for the UE identified by the UE_ID).Next, the AMF 70 performs an URSP validation for the UE 3, i.e., the AMF 70 checks whether the UE 3 or an application in the UE 3 is entitled to the service in the PDU session having the S-NSSAI and DNN, and optionally the PDU_Session_ID requested by the UE 3, e.g., whether the App_ID in the URSP copy from the PCF 73 is mapped to the S-NSSAI and DNN, and optionally the PDU_Session_ID. For example, the AMF 70 may perform the URSP validation in the same manner as step 10 of Figure 5. If the URSP validation by the AMF 70 is successful, the AMF 70 continues the PDU session establishment procedure. For example, if the URSP validation by the AMF 70 is successful, the AMF 70 may send an Nsmf_PDUSession_CreateSMContext request message in accordance with step 8 of Figure 5. For example, if the URSP validation by the AMF 70 is successful, the AMF 70 may include information indicating that the URSP validation has been completed successfully in the Nsmf_PDUSession_CreateSMContext request message in step 8 of Figure 5. In this case, the SMF 71 includes information indicating that the URSP validation has been completed successfully in the Npcf_SMPpolicy_Control_Create message in step 9 of Figure 5. Upon receiving the Npcf_SMPpolicy_Control_Create message, the PCF 73 may skip the URSP validation in step 10 of Figure 5 or may perform the URSP validation. The PCF 73 may then perform the process of step 11. If the URSP validation by the AMF 70 is not successful, i.e., if the URSP validation fails, the AMF 70 rejects the PDU session establishment request from the UE in accordance with step 17 of Figure 5.

[0140] <Modification 3 of the first example of the second aspect> The reject cause set to "URSP rules not followed" in steps 15, 16, and 17 may have associated information about the reason for the rejection. UE3 takes appropriate action based on the associated information. The associated information may be one or a combination of the following:

[0141] -The requested application ID (e.g., App-ID or App_ID) is not allowed to establish a PDU session with the specified S-NSSAI.

[0142] The requesting application ID is not allowed to establish a PDU session with the specified DNN.

[0143] -The requesting application ID is not allowed to establish a PDU session with the specified S-NSSAI and DNN.

[0144] The requesting application ID is not allowed to route traffic in an already established PDU session with the PDU_Session_ID.

[0145] The requesting application ID is not allowed to establish a PDU session in the specified SSC mode.

[0146] The requesting application ID is not allowed to establish a PDU session with the specified access type, which can be 3GPP access, non-3PP access, or multi-access.

[0147] The requesting application ID is not allowed to establish a PDU session at the current UE location, i.e. the location criteria in the route selection verification criteria in the route selection descriptor do not match.

[0148] The requested application ID is not allowed to establish a PDU session at the requested time, i.e., the time window in the route selection validation criteria in the route selection descriptor does not match.

[0149] <Modification 4 of the first example of the second aspect> In step 10 of FIG. 5, if the URSP validation fails, i.e., if the PCF 73 can determine that the UE 3 does not have the latest version of the UE policy, e.g., the latest version of the URSP rules, the PCF can initiate a UE policy update in the UE 3 in accordance with section 4.2.4.3 in non-patent document 5.

[0150] <Second Example of the Second Aspect> The second example of the second aspect in Figure 6 proposes a solution for access control and monitoring for services provided in S-NSSAI and DNN by external service providers, where access control is performed by PCF73 and monitoring is performed by NSACF78.

[0151] The detailed process of the second example of the second embodiment is as follows.

[0152] Step 1. AF Request Creation—The AF 201 may provide service specific parameters to the 5G system via the NEF 77 as specified in section 4.15.6.7 of 3GPP TS 36.210. The AF 201 may issue the request on behalf of an external application that may or may not be owned by the PLMN serving the UE 3.

[0153] Step 2. The AF 201 sends an Nnef_ServiceParameter_Create / Update message to the NEF 77. The Nnef_ServiceParameter_Create / Update message includes the App_ID, ext_UE_ID, S-NSSAI, DNN, and required traffic routing monitoring. The Nnef_ServiceParameter_Create / Update message may include location_info. The location_info may be expressed as location information. The App_ID may identify the service provider, i.e., the AF 201. The ext_UE_ID may be in the form of GPSI or external group identity information. The AF 201 includes the S-NSSAI and DNN in the message to identify the service provided by the AF 201. AF201 may also include in the message to NEF77 a "required traffic routing monitoring" parameter or any other indication of a parameter that identifies a request by AF201 to the 3GPP system regarding monitoring and access control to services provided by the combination of S-NSSAI and DNN, for example, whether UE3 and / or an application in UE3 requesting a service in S-NSSAI and / or DNN is entitled to that service according to the URSP rules for that UE3.

[0154] If AF201 includes the "required traffic routing monitoring" parameter, the 3GPP system monitors and controls the use of services provided by at least one of the S-NSSAI and the DNN. For example, the 3GPP system may deny service from applications and UEs that are not entitled to the service based on the latest URSP rules provided to the UE by the 3GPP system. If AF201 includes the location_info parameter, the use of services in the S-NSSAI and the DNN, e.g., PDU sessions, may be monitored and controlled by the network only at locations identified by the location_info parameter, which may be expressed in a geographical or any other manner.

[0155] Step 3. The NEF 77 stores the AF 201 requested information in the UDM 75 in the "Application Data" section, and also performs any mapping such as ext_UE_ID to 3GPP UE identity (e.g., GPSI to SUPI), or service identity to S-NSSAI and DNN if the AF 201 provides a service identity instead of S-NSSAI and DNN. If location_info is provided by the AF 201, the NEF 77 maps the provided location_info to 3GPP-compatible location information, e.g., 3gpp_location_info, defined as one or more cells or one or more TAs. The NEF 77 also stores the "Required Traffic Routing Monitoring" parameter in the UDM 75. The NEF 77 may store the 3GPP-compatible location information from the "3gpp_location_info" parameter associated with the UE_ID (e.g., SUPI), if provided by the AF 201. Alternatively, the "required traffic routing monitoring" parameter and the "3gpp_location_info" parameter may be stored in the UDM 75 by the network operator based on an SLA agreement with an external service provider, i.e., the AF 201. The NEF 77 may store the above information in the UDR.

[0156] Step 4. The UDM 75 sends a Nudr_DM_Notify message to the PCF 73 according to section 5.2.12.2.1-1 in Non-Patent Document 5. The Nudr_DM_Notify message may include the App_ID, the UE_ID, the S-NSSAI, the DNN, the required traffic routing monitoring, and 3gpp_location_info. For example, if the UE 3 registers with the network and the PCF 73 subscribes to notifications by the UDM 75 when application data for the UE 3 is modified, the UDM 75 may send the Nudr_DM_Notify message to the PCF 73. For example, if the information mentioned in step 3 is stored in the UDM 75, e.g., in the UDR of the UDM 75. The UDR of the UDM 75 may send the Nudr_DM_Notify message to the PCF 73.

[0157] Step 5. The PCF 73 updates the UE policy (i.e., URSP rule) for the UE 3 indicated by the Nudr_DM_Notify message from the UDM 75, and the PCF 73 stores the required traffic monitoring parameters and the 3gpp_location_info parameter in the PCC rule in the PCF 73 for the UE 3. The PCF 73 may associate and store the App_ID, UE_ID, S-NSSAI, DNN, the required traffic monitoring parameters, and the 3gpp_location_info parameter.

[0158] Step 6. The PCF 73 provides the updated UE policy with the updated URSP rules to the UE 3 via the UE policy update procedure according to section 4.2.4.3 in Non-Patent Document 5.

[0159] Step 7. At some stage, an application in UE 3 having App_ID requests a service in at least one of S-NSSAI and DNN. In this case, UE 3 sends a PDU session establishment request message to AMF 70. UE 3 includes PDU_Session_ID, DNN, and S-NSSAI in the PDU session establishment request message. UE 3 also includes service application identification information (i.e., App_ID) in the PDU session establishment request message to AMF 70. App_ID can be an application identifier or an OS identifier, or a combination of an application identifier and an OS identifier.

[0160] Step 8. The AMF 70 selects an SMF 71 in accordance with the requirements in Non-Patent Document 5 and sends an Nsmf_PDUSession_CreateSMContext request message to the SMF 71. The AMF 70 includes the UE_ID, PDU_Session_ID, DNN, and S-NSSAI parameters received from the UE 3 in the Nsmf_PDUSession_CreateSMContext request message. The AMF 70 also includes an application identifier (i.e., App_ID), UE location, and PLMN ID in the Nsmf_PDUSession_CreateSMContext request message to the SMF 71.

[0161] The AMF 70 may include a PLMN ID, i.e. either the PLMN name or the PLMN identification information comprising the MCC and MNC of the PLMN to which the AMF 70 belongs, in the Nsmf_PDUSession_CreateSMContext request message.

[0162] The UE location may indicate location information of the UE 3, for example, the TAI where the UE 3 is located. The UE location may not be included in the Nsmf_PDUSession_CreateSMContext request message. The UE_ID may be an identifier of the UE 3.

[0163] Step 9. The SMF 71 triggers a policy association with the PCF 73 and sends an Npcf_SMPpolicy_Control_Create message to the PCF 73. The SMF 71 includes the UE_ID, PDU_Session_ID, DNN, S-NSSAI, and PLMN ID received from the AMF 70 as parameters in the Npcf_SMPpolicy_Control_Create message. The SMF 71 also includes the App_ID and UE_location information in the Npcf_SMPpolicy_Control_Create message to the PCF 73. If the UE_location information has been provided to the SMF 71, the SMF 71 may include the UE_location information in the Npcf_SMPpolicy_Control_Create message.

[0164] Step 10. Ursp Validation—If the PCF 73 does not have the subscriber's subscription-related information, it sends a request to the UDM 75 by invoking the Nudr_DM_Query service to receive information related to the Session_ID of the PDU. The Nudr_DM_Query service or Nudr_DM_Query message may include a SUPI (e.g., the SUPI of the UE 3), a DNN, and an S-NSSAI. The PCF 73 may request notification from the UDM 75 regarding changes in subscription information by invoking a Nudr_DM_Subscribe message according to session 4.16.9 in 3GPP TS 23.2006-01-01 16:20 Page 17 of 21. The PCF 73 checks the UE's Ursp validity, i.e., whether the UE 3 or an application in the UE 3 is entitled to the service in the requested S-NSSAI and DNN. For example, the PCF 73 may verify whether the application identification information (i.e., App_ID) in the UE 3 can be mapped to the S-NSSAI and DNN provided in the Npcf_SMPpolicy_Control_Create message from the SMF 71. The PCF 73 verifies the PDU session routing rules for the UE 3 from the latest URSP rules for the UE 3 stored in the PCF 73. To pass the URSP validation, the App_ID mapping to the S-NSSAI and DNN, and optionally the PDU_Session_ID, in the URSP rule copy for the UE 3 stored in the PCF 73 must match the App_ID, S-NSSAI and DNN, and optionally the PDU_Session_ID parameters provided from the AMF 70, i.e., the URSP rule copy for the UE 3 provided by the UE 3 and the URSP rule copy for the UE 3 stored in the PCF 73 must match. If 3gpp_location_info is provided to the PCF 73, the PCF 73 checks whether the location of the UE 3 is among the locations provided via 3gpp_location_info.If the location of UE3 is outside the location provided via 3gpp_location_info, UE3 is not entitled to the service in S-NSSAI and DNN even if the App_ID requesting the service is mapped to S-NSSAI and DNN (e.g., passes URSP validation). For example, the PCF73 determines that the URSP validity check of the UE passes (e.g., the PCF73 determines that the URSP rules of the UE3 provided by the UE3 match the URSP rules of the UE3 stored in the PCF73, or the PCF73 determines that the combination of the App_ID, S-NSSAI and DNN, and optionally the PDU_Session_ID stored in the PCF73 in step 5 matches the combination of the App_ID, S-NSSAI and DNN, and optionally the PDU_Session_ID received from the AMF70 via the SMF71), and the PCF73 determines that the App_ID in the UE3 is entitled to the service in the requested S-NSSAI and DNN. If 3gpp_location_info is not provided to the PCF73, the PCF73 may skip checking whether the location of the UE3 is among the locations provided via 3gpp_location_info.

[0165] Step 11. As a result of the PCF 73's URSP validation (e.g., the PCF 73 determines that the App_ID in UE 3 is entitled to the service in the requested S-NSSAI and DNN, and optionally the PDU_Session_ID), if the App_ID in UE 3 and UE 3 itself are entitled to the service in the requested S-NSSAI and DNN, the PCF 73 sends an Nnsacf_ServiceMonitoring_Request message to the NSACF 78. The PCF 73 includes the App_ID, UE_ID, S-NSSAI, DNN, 3gpp_location_info, PLMN ID, and optionally the Session_ID of the PDU in the Nnsacf_ServiceMonitoring_Request message to the NSACF 78. Alternatively, the PCF 73 may utilize any other existing or new message between the PCF 73 and the NSACF 78 to convey the App_ID, UE_ID, S-NSSAI, DNN, and 3gpp_location_info for the purpose of monitoring service usage for the S-NSSAI and DNN, and optionally the PDU_Session_ID. If the 3gpp_location_info is provided to the PCF 73, the PCF 73 may include the 3gpp_location_info in the Nnsacf_ServiceMonitoring_Request message.

[0166] Step 12. The NSACF 78 starts monitoring traffic routing for the PDU session having the S-NSSAI and DNN according to the App_ID at the UE 3, and optionally the PDU_Session_ID, if provided. For example, the NSACF 78 starts monitoring traffic routing for the S-NSSAI and DNN, and optionally the PDU_Session_ID, corresponding to the App_ID provided by the PCF 73. If the PCF 73 includes 3gpp_location_info, the monitoring applies to the location defined in the 3gpp_location_info parameter. The location information may be defined for one or more cells or one or more TAs. If the 3gpp_location_info parameter is provided by the PCF 73, the NSACF 78 may subscribe to location tracking of the UE 3 by the AMF, such that the NSACF 78 may monitor service access to the S-NSSAI and DNN by the UE 3 only if the UE 3 is within the location defined by the 3gpp_location_info parameter.

[0167] Step 13. If the AF 201 subscribes to notification of traffic routing by the NSACF 78, the NSACF 78 may trigger a notification to the NEF 77 each time a service in the S-NSSAI and DNN is accessed. The NSACF 78 sends an Nnsacf_Service_Routing notification message to the NEF 77. The NSACF 78 includes in the Nnsacf_Service_Routing notification message the App_ID, UE_ID, S-NSSAI, DNN, PDU_Session_ID, 3gpp_location_info if applicable, PLMN ID, and service_usage_info, which may include information about the duration of the service access in the S-NSSAI and DNN.

[0168] Alternatively, the NSACF 78 may utilize any other existing or new notification service or message between the NSACF 78 and the NEF 77 to convey the App_ID, UE_ID, S-NSSAI, DNN, PDU_Session_ID, 3gpp_location_info, PLMN ID, and service_usage_info to the NEF 77. If 3gpp_location_info is provided to the NSACF 78, the NSACF 78 may include the 3gpp_location_info in an Nnsacf_Service_Routing notification message. For example, if the NSACF 78 detects traffic routing for a PDU session having an S-NSSAI and DNN, and optionally a PDU_Session_ID, that corresponds to the App_ID, the NSACF 78 may send an Nnsacf_Service_Routing notification message. For example, if the AF 201 subscribes to notifications of traffic routing by the NSACF 78 and the NSACF 78 detects traffic routing for a PDU session having an S-NSSAI and DNN corresponding to the App_ID and a PDU_Session_ID, the NSACF 78 may send an Nnsacf_Service_Routing notification message.

[0169] Step 14. The NEF 77 maps the UE_ID to ext_UE_ID and the 3gpp_location_info to geographical location_info and sends a Nnef_Service_Routing notification message to the AF 201. The Nnef_Service_Routing notification message may include the App_ID, ext_UE_ID, S-NSSAI, DNN, location_info (e.g., geographical location_info), service_usage_info, and PLMN ID. Alternatively, the NEF 77 may utilize any other existing or new notification service or message between the NEF 77 and the AF 201 to convey the App_ID, ext_UE_ID, S-NSSAI, DNN, PDU_Session_ID, location_info, and service_usage_info to the AF 201.

[0170] Step 15. If the URSP validation fails in step 10, that is, if the PCF 73 determines that the application in the UE 3 that requested the service in the S-NSSAI and DNN is not entitled to the service in the S-NSSAI and DNN (e.g., the PCF 73 determines that the URSP rules for the UE 3 provided by the UE 3 do not match the URSP rules for the UE 3 stored in the PCF 73, or the PCF 73 determines that the combination of the App_ID, S-NSSAI, and DNN, and optionally the PDU_Session_ID, stored in the PCF 73 in step 5 does not match the combination of the App_ID, S-NSSAI, and DNN, and optionally the PDU_Session_ID, received from the AMF 70 via the SMF 71), the PCF 73 returns an Npcf_SMPolicy_Control_Create response message to the SMF 71. The PCF 73 includes a failure result parameter and a rejection cause in the Npcf_SMPolicy_Control_Create response message. The reject cause may be set to "URSP rules not followed" or any other indication for a reject cause, indicating that the UE3 or an application in the UE3 is not entitled to the service in the requested S-NSSAI and DNN, for example, the URSP rules for the UE3 do not allow for mapping of App_ID to S-NSSAI and DNN. The reason for the mismatch in the mapping of the service may either be that the UE3 does not have the latest URSP rules, i.e., the URSP rules do not match between the URSP copy in the UE3 and the URSP copy in the PCF73, or that the UE3 is not following the URSP rules.

[0171] Step 16. If the SMF 71 receives an Npcf_SMPolicy_Control_Create response message from the PCF 73 with a failure result and a rejection cause set to "not according to URSP rules", the SMF 71 responds with an Nsmf_PDUSession_CreateSMContext_Response message to the AMF 70. The SMF 71 includes the rejection cause sent by the PCF 73 in the Nsmf_PDUSession_CreateSMContext_Response message.

[0172] Step 17. Upon receiving the Nsmf_PDUSession_CreateSMContext_Response message, AMF 70 rejects the PDU session establishment request from UE 3 by sending a PDU session establishment reject message. AMF 70 includes in the PDU session establishment reject message a reject cause set to "not according to URSP rules" or any other indication for the reject cause, indicating that UE 3 or an application in UE 3 is not entitled to the service in the requested S-NSSAI and DNN, e.g., the URSP rules for UE 3 do not allow mapping of App_ID to S-NSSAI and DNN.

[0173] When UE3 receives a PDU session establishment rejection message with the rejection cause set to "URSP rules not followed," UE3 will not attempt another request for PDU session establishment in the S-NSSAI and DNN where the PDU session establishment was rejected until UE3 receives an update to the URSP rules from the network. If UE3 continues to be rejected multiple times with the same rejection cause set to "URSP rules not followed" (this number may be a 3GPP standard value or may be configurable by configuration in UE3), UE3 will not attempt another PDU session establishment request in the S-NSSAI and DNN until UE3 re-registers.

[0174] According to the above, for example, the 5G network and the third party service provider (e.g., AF201) can recognize when the third party service provider's application is routed using the provisioned URSP rules.

[0175] <Modification 1 of the second example of the second aspect> Variants 1 to 3 of the first example of the second embodiment can be applied as variant 1 to the second example of the second embodiment.

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

[0177] 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.

[0178] 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).

[0179] 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.

[0180] 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."

[0181] 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.

[0182] 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).

[0183] 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).

[0184] 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.

[0185] 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).

[0186] 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.

[0187] 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.

[0188] 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 an unstructured data type. In one example, the AF 201 may be a network element in the data network 20 with which the UE 3 communicates (see FIG. 7). In another example, the AF 201 may be a network element in the core network 7.

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

[0190] 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.

[0191] 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.

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

[0193] - 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.

[0194] 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)

[0195] - 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)

[0196] 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:

[0197] 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.

[0198] 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.

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

[0200] -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.

[0201] 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.

[0202] 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.

[0203] 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.

[0204] -Authentication Rejection 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 rejection message: --EAP message.

[0205] - 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.

[0206] - Service Authorization 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 Authorization Message: --PDU session status, PDU session reactivation result, PDU session reactivation result error cause, EAP message, and T3448 value.

[0207] - Service Rejection 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 Rejection Message: --5GMM cause, PDU session status, T3346 value, EAP message, T3448 value, and CAG information list.

[0208] 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.

[0209] 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.

[0210] <User equipment (UE)> FIG. 8 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.

[0211] 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).

[0212] 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).

[0213] 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.).

[0214] 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.).

[0215] 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.).

[0216] 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.).

[0217] 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.

[0218] 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)).

[0219] 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)."

[0220] 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.

[0221] 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.

[0222] 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.

[0223] 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).

[0224] 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).

[0225] <(R)AN node> FIG. 9 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.

[0226] 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 related to the radio connection and connection with the core network 7 for a specific UE 3, particularly those related to connection establishment and maintenance, 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. Such signaling may also include, in the case of transmission, for example, broadcast information (such as master information and system information).

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

[0228] (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).

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

[0230] 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).

[0231] 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).

[0232] 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.

[0233] <Radio Unit (RU)> FIG. 11 is a block diagram illustrating the main components of an exemplary RU 60, e.g., the RU portion of a base station (e.g., an eNB in ​​LTE, a gNB in ​​5G, a base station for Beyond 5G, or a base station for 6G). 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.

[0234] 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.

[0235] 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.

[0236] 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).

[0237] 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.

[0238] <Distributed Unit (DU)> FIG. 12 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 according to 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.

[0239] 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).

[0240] 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.

[0241] <Centralized Unit (CU)> FIG. 13 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.

[0242] 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).

[0243] 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.

[0244] <amf> 14 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).

[0245] 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).

[0246] <smf> 15 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 data storage 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).

[0247] 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).

[0248] <upf> 16 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).

[0249] 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).

[0250] A communication device that performs the functions of a collocated gNB-CU-UP and UPF, or a communication device that performs the functions of a gNB-CU-UP and a UPF, or a communication device that performs the functions of a gNB-CU-UP and a UPF, may have the same components as UPF72.

[0251] <pcf> 17 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).

[0252] The PCF 73 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).

[0253] <ausf> 18 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).

[0254] 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).

[0255] <udm> 19 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).

[0256] 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).

[0257] <nwdaf> 20 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).

[0258] 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).

[0259] <nef> 21 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).

[0260] 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).

[0261] <nsacf> 22 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 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).

[0262] 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).

[0263] <af> 23 is a block diagram illustrating the main components of the AF 201. As shown, the device includes a transceiver circuit 2011 operable to transmit signals to and receive signals from other nodes (including the NEF 77) via a network interface 2012. A controller 2013 controls the operation of the AF 201 in accordance with software stored in memory 2014. For example, the software may be pre-installed in the memory 2014 and / or downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 20141 and a communications control module 20142 having at least a transceiver control module 201421. The communication control module 20142 (using its transceiver control module 201421) is responsible for handling (generating / sending / receiving) signaling between the AF 201 and other nodes, such as the NEF 77 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) related to mobility management procedures (for the UE 3).

[0264] The AF 201 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).

[0265] <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.

[0266] 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.

[0267] 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.

[0268] 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.

[0269] 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.

[0270] 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.

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

[0272] 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.

[0273] 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.

[0274] 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.

[0275] 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.

[0276] 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).

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

[0278] Appendix 1. Sending information requesting User Equipment Route Selection Policy (URSP) rules; When transmitting the information, receive the URSP rules. Method of communication device.

[0279] Appendix 2. the communication device is an Application Function (AF) device; The method described in Appendix 1.

[0280] Appendix 3. the communication device is a Network Exposure Function (NEF) device; The method described in Appendix 1.

[0281] Appendix 4. The communication device is a Network Data Analytics Function (NWDAF) device. The method described in Appendix 1.

[0282] Appendix 5. the communication device is an Access and Mobility Management Function (AMF) device; The method described in Appendix 1.

[0283] Appendix 6. the communication device is a Policy Control Function (PCF) device; The method described in Appendix 1.

[0284] Appendix 7. receiving information requesting a User Equipment Route Selection Policy (URSP) rule; If the information is received, transmit the URSP rule. A User Equipment (UE) method.

[0285] Appendix 8. receiving information requesting a User Equipment Route Selection Policy (URSP) rule; If the information is received, transmit the URSP rule. Method of communication device.

[0286] Appendix 9. the communication device is a Policy Control Function (PCF) device; The method described in Appendix 8.

[0287] Appendix 10. Submit information to request monitoring of traffic routing, receiving results of said monitoring of said traffic routing when said information is transmitted; Method of communication device.

[0288] Appendix 11. the communication device is an Application Function (AF) device; 11. The method described in Appendix 10.

[0289] Appendix 12. Receive information to request monitoring of traffic routing; After receiving the information, performing a validation check against User Equipment Route Selection Policy (URSP) rules; If the validation is successful, sending information for monitoring the traffic routing. Method of communication device.

[0290] Appendix 13. if the validation fails, sending a rejection reason. 12. The method described in Appendix 12.

[0291] Appendix 14. the communication device is a Policy Control Function (PCF) device; 14. The method according to claim 12 or 13.

[0292] Appendix 15. Receive information to monitor traffic routing, monitoring the traffic routing based on the information; transmitting results of said monitoring of said traffic routing. Method of communication device.

[0293] Appendix 16. The communication device is a Network Data Analytics Function (NWDAF) device. The method described in Appendix 15.

[0294] Appendix 17. The communication device is a Network Slice Admission Control Function (NSACF) device. The method described in Appendix 15.

[0295] Appendix 18. Receive the results of traffic routing monitoring, Sending the results; Method of communication device.

[0296] Appendix 19. the communication device is a Network Exposure Function (NEF) device; 18. The method described in Appendix 18.

[0297] Appendix 20. Sending a Protocol Data Unit (PDU) session establishment request message; The PDU session establishment request message includes a Data Network Name (DNN), Single Network Slice Selection Assistance Information (S-NSSAI), and an identifier of an application for which a User Equipment (UE) requests service; A PDU session establishment rejection message is received. The PDU session establishment rejection message includes a rejection cause indicating that the UE or the application is not entitled to the service in the S-NSSAI and the DNN. A method for a user equipment (UE).

[0298] Appendix 21. means for transmitting information requesting a User Equipment Route Selection Policy (URSP) rule; means for receiving the URSP rules when transmitting the information; A communication device comprising:

[0299] Appendix 22. the communication device is an Application Function (AF) device; 22. The communication device of claim 21.

[0300] Appendix 23. the communication device is a Network Exposure Function (NEF) device; 22. The communication device of claim 21.

[0301] Appendix 24. The communication device is a Network Data Analytics Function (NWDAF) device. 22. The communication device of claim 21.

[0302] Appendix 25. the communication device is an Access and Mobility Management Function (AMF) device; 22. The communication device of claim 21.

[0303] Appendix 26. the communication device is a Policy Control Function (PCF) device; 22. The communication device of claim 21.

[0304] Appendix 27. means for receiving information requesting a User Equipment Route Selection Policy (URSP) rule; means for transmitting said URSP rules when said information is received; A user equipment (UE) comprising:

[0305] Appendix 28. means for receiving information requesting a User Equipment Route Selection Policy (URSP) rule; means for transmitting said URSP rules when said information is received; A communication device comprising:

[0306] Appendix 29. the communication device is a Policy Control Function (PCF) device; 29. The communication device of claim 28.

[0307] Appendix 30. means for transmitting information to request monitoring of traffic routing; means for receiving results of said monitoring of said traffic routing when said information is sent; A communication device comprising:

[0308] Appendix 31. the communication device is an Application Function (AF) device; 31. The communication device of claim 30.

[0309] Appendix 32. means for receiving information requesting monitoring of traffic routing; means for performing a validation check against User Equipment Route Selection Policy (URSP) rules after receiving the information; means for transmitting information for monitoring the traffic routing if the validation is successful; A communication device comprising:

[0310] Appendix 33. and means for transmitting a rejection cause if the validation fails. 33. The communication device of claim 32.

[0311] Appendix 34. the communication device is a Policy Control Function (PCF) device; 34. The communication device of claim 32 or 33.

[0312] Appendix 35. means for receiving information for monitoring traffic routing; means for monitoring the traffic routing based on the information; means for transmitting results of said monitoring of said traffic routing; A communication device comprising:

[0313] Appendix 36. The communication device is a Network Data Analytics Function (NWDAF) device. 36. The communications device of claim 35.

[0314] Appendix 37. The communication device is a Network Slice Admission Control Function (NSACF) device. 36. The communications device of claim 35.

[0315] Appendix 38. means for receiving results of the traffic routing monitoring; means for transmitting the results; A communication device comprising:

[0316] Appendix 39. the communication device is a Network Exposure Function (NEF) device; 39. The communications device of claim 38.

[0317] Appendix 40. A means for transmitting a Protocol Data Unit (PDU) session establishment request message, comprising: The PDU session establishment request message includes a Data Network Name (DNN), a Single Network Slice Selection Assistance Information (S-NSSAI), and an identifier of an application for which a User Equipment (UE) requests service; A means for receiving a PDU session establishment rejection message, The PDU session establishment rejection message includes a rejection cause indicating that the UE or the application is not entitled to the service in the S-NSSAI and the DNN; A user equipment (UE) comprising:

[0318] 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.

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

[0320] 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 201AF 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 2011 Transceiver Circuit 2012 Network Interface 2013 Controller 2014 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 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 20141 Operating System 20142 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 201421 Transceiver Control Module< / af> < / nsacf> < / nef> < / nwdaf> < / udm> < / ausf> < / pcf> < / upf> < / smf> < / amf>

Claims

1. receiving first information and second information from a User Equipment (UE); the first information includes parameters related to a Protocol Data Unit (PDU) session; the second information includes information related to User Equipment Route Selection Policy (URSP) rules; the second information is associated with an application; verifying whether the first information and the second information comply with the URSP rules of the UE; Method of communication device.

2. adjusting the URSP rules of the UE based on a determination that the UE does not have up-to-date URSP rules after receiving the second information; The method of claim 1.

3. updating the UE with the adjusted URSP rules of the UE; The method of claim 2.

4. the communication device is a Policy Control Function (PCF) device; 4. The method according to any one of claims 1 to 3.

5. The first information is Single Network Slice Selection Assistance Information (S-NSSAI) or Data Network Name (DNN), The method of claim 1.

6. The UE receives a PDU session establishment rejection message based on a confirmation performed by the communication device. The method of claim 1.

7. means for receiving first information and second information from a User Equipment (UE); means for verifying whether the first information and the second information comply with a User Equipment Route Selection Policy (URSP) rule of the UE; Equipped with the first information includes parameters related to a Protocol Data Unit (PDU) session; the second information includes information related to a URSP rule; the second information is associated with an application; Communication equipment.

8. means for adjusting the URSP rules of the UE based on a determination that the UE does not have up-to-date URSP rules after receiving the second information. The communication device according to claim 7.

9. means for updating the UE with the adjusted URSP rules of the UE. The communication device according to claim 8.

10. the communication device is a Policy Control Function (PCF) device; A communication device according to any one of claims 7 to 9.

11. The first information is Single Network Slice Selection Assistance Information (S-NSSAI) or Data Network Name (DNN), The communication device according to claim 7.

12. The UE receives a PDU session establishment rejection message based on a confirmation performed by the communication device. The communication device according to claim 7.

Images