WO2022080976A1 - Procédés et systèmes destinés à l'amélioration l'expérience de tranche de réseau d'utilisateur - Google Patents

Procédés et systèmes destinés à l'amélioration l'expérience de tranche de réseau d'utilisateur Download PDF

Info

Publication number
WO2022080976A1
WO2022080976A1 PCT/KR2021/014416 KR2021014416W WO2022080976A1 WO 2022080976 A1 WO2022080976 A1 WO 2022080976A1 KR 2021014416 W KR2021014416 W KR 2021014416W WO 2022080976 A1 WO2022080976 A1 WO 2022080976A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
pdu session
icons
nssai
list
Prior art date
Application number
PCT/KR2021/014416
Other languages
English (en)
Inventor
Brijendra Kumar ASTHANA
Danish Ehsan Hashmi
Subhrodip MAZUMDAR
Original Assignee
Samsung Electronics Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Samsung Electronics Co., Ltd. filed Critical Samsung Electronics Co., Ltd.
Publication of WO2022080976A1 publication Critical patent/WO2022080976A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/78—Architectures of resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1059—End-user terminal functionalities specially adapted for real-time communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels

Definitions

  • the present disclosure in general, relates to network procedures performed at a User Equipment (UE), and, in particular, relates to systems and methods and systems for managing network slices in the UE.
  • UE User Equipment
  • the 5G or pre-5G communication system is also called a 'Beyond 4G Network' or a 'Post LTE System'.
  • the 5G communication system is considered to be implemented in higher frequency (mmWave) bands, e.g., 60GHz bands, so as to accomplish higher data rates.
  • mmWave e.g., 60GHz bands
  • MIMO massive multiple-input multiple-output
  • FD-MIMO Full Dimensional MIMO
  • array antenna an analog beam forming, large scale antenna techniques are discussed in 5G communication systems.
  • RANs Cloud Radio Access Networks
  • D2D device-to-device
  • CoMP Coordinated Multi-Points
  • FQAM Hybrid FSK and QAM Modulation
  • SWSC sliding window superposition coding
  • ACM advanced coding modulation
  • FBMC filter bank multi carrier
  • NOMA non-orthogonal multiple access
  • SCMA sparse code multiple access
  • the Internet which is a human centered connectivity network where humans generate and consume information
  • IoT Internet of Things
  • IoE Internet of Everything
  • sensing technology “wired/wireless communication and network infrastructure”, “service interface technology”, and “Security technology”
  • M2M Machine-to-Machine
  • MTC Machine Type Communication
  • IoT Internet technology services
  • IoT may be applied to a variety of fields including smart home, smart building, smart city, smart car or connected cars, smart grid, health care, smart appliances and advanced medical services through convergence and combination between existing Information Technology (IT) and various industrial applications.
  • IT Information Technology
  • 5G communication systems to IoT networks.
  • technologies such as a sensor network, Machine Type Communication (MTC), and Machine-to-Machine (M2M) communication may be implemented by beamforming, MIMO, and array antennas.
  • MTC Machine Type Communication
  • M2M Machine-to-Machine
  • Application of a cloud Radio Access Network (RAN) as the above-described Big Data processing technology may also be considered to be as an example of convergence between the 5G technology and the IoT technology.
  • RAN Radio Access Network
  • NW can guarantee a very high QoS for Ultra-High Speed Video by steering data through a specific Slice/DNN.
  • NW needs to indicate UE to tunnel the data traffic for video applications through a PDU session with the specified
  • PCF Policy Control Function
  • Table 1 illustrates a URSP table.
  • Subscription to network slice can be provided by the operator alone or can be provided by operators based on Service layer agreement with application, Operators and application developer can decide the icon policy based on URSP Rules to have a uniformity among all users. Current state of art doesn’t have this provision.
  • Users may avoid the problem of video buffering by only opening the applications in PLMNs or Tracking Areas supporting the Superior Video Streaming Slice.
  • Application can use the information to decide codec to use (e.g. - if connected to better QoS slice, streaming application start with HD if not start with SD )
  • Slice based Icon can be shown when an application is active on screen and is using the slice.
  • any over the air media streaming application is open “Video Slice” icon is displayed.
  • the Video Icon is removed and “Social Slice” Icon is displayed.
  • the over the air media streaming application uses slice depicted by icon "video slice” and Facebook uses a slice depicted by icon by "social slice” Icons will change based on the active application usage.
  • Slice Icons may be displayed if they are actively using the Slice.
  • UI can show multiple icons corresponding to the slices being used or best slice being used.
  • RAT 5G,4G, WiFi, PDU session like IMS, Internet, Hotspot etc.
  • UE shows icon for IMS and Internet PDU session when service is in use (e.g. UE shows VoLTE when IMS VoLTE is registered or Internet when Internet PDU session is connected). These icons are permanent icon and will be available until IMS is registered or Internet PDU session is active. It is static information and UE show icon based on the RAT, IMS service or PDU session for the internet is active.
  • the application is not aware of network connection ability for 5G slices. If a network operator supports some slices for the application, the application does not know which network slices are possibly available to it. The data traffic flow is abstract from the point of view of the application. If the application is aware of the S-NSSAI and PDU Session Information then the application can use certain abilities like better security, low latency, better codecs and higher bandwidth to its advantage. Slice and PDU Session information is not currently advertised to Applications.
  • MODEM starts to map the requirements to the traffic descriptors (TDs) and route section descriptor (RSDs) of URSP rules in order of precedence. Suppose we have three RSDs in a TD of a URSP rule as following:
  • RSD3 will be chosen and a PDU session will be established. But RSD1 and RSD2 are higher precedence options and application will get a better QoS if they are selected.
  • RSD1 is rejected because current time or location is not suitable to use this option. This information can be helpful for user as he might want to use the application with best services and he can then use the application in a suitable time.
  • RSD2 is rejected since network doesn’t have enough resources currently to allocate for this slice. MODEM will get to know this when it will send a PDU session establishment request. Once we relay this reject cause to AP, user will know there is a lot of traffic in higher priority slice.
  • MODEM In current state of art, there is no transparency to the user on the process of accepting/rejecting a particular RSD and URSP rule.
  • MODEM receives request to establish data session, MODEM checks the TDs and if matching rule found, it checks RSDs for PDU session establishment (if not exist), it selects RSDs 3 (RSDs 1 and RSDs 2 can't be used as it is reject or not allowed for the current time), establish PDU session and sends data session connected with IP address to AP.
  • RSDs 3 RSDs 1 and RSDs 2 can't be used as it is reject or not allowed for the current time
  • MODEM doesn’t indicate the reject causes of higher priority slices (in this example RSDs 1, RSDs 2) to AP.
  • Fig. 1 illustrates an operational flow diagram 100 depicting a process for receiving information related to one or more services, in accordance with an existing technique.
  • applications send application specific info to access point (AP).
  • the AP generates a PDU session request (App ID, DNN, NSSAI, SCC Mode, etc.) to be sent to a CP.
  • the AP sends the request to the CP via an opaque interface with no slice transparency.
  • the AP receives the generic information from a CP layer from the interface.
  • the CP module maps to a URSP rule and tries to establish the PDU Session.
  • the CP sends the PDU session request to MODEM and MODEM stores all configured URSP rules by network. Further, the CP module generates a response which has PDU session information (DNN AMBR, QCI, etc) and rote Routine PDU Session info to AP via the interface.
  • PDU session information DNN AMBR, QCI, etc
  • a method, for displaying an icon for a network slice at a User Equipment includes initiating, by a modem, a Protocol Data Unit (PDU) session with a network by transmitting one of a PDU session establishment request, a PDU session modification, and a (Non-Access stratum) NAS message.
  • the method includes receiving, by an Application Processor (AP), an indication about one or more network slices being active for the PDU session from at least one of the modem and the network.
  • AP Application Processor
  • the method includes displaying, by the AP, one or more icons associated with the one or more network slices on an interface of the UE.
  • a method, for network slice enhancement for a 5G UE includes receiving, at an AP from a modem, a list of URSP rules, one or more S-NSSAI associated with one or more network slices categorized among configured, rejected, requested and allowed network slices and PDU session information.
  • the method includes maintaining, by the AP, a database to store information received at the AP.
  • the one or more network slices execute one or more services at the UE.
  • a system for displaying an icon for a network slice at a UE.
  • the system includes initiating, by a modem, a Protocol Data Unit (PDU) session with a network by transmitting one of a PDU session establishment request, a PDU session modification, and a (Non-Access stratum) NAS message.
  • the system includes receiving, by an Application Processor (AP), an indication about one or more network slices being active for the PDU session from at least one of the modem and the network.
  • AP Application Processor
  • the system includes displaying, by the AP, one or more icons associated with the one or more network slices on an interface of the UE.
  • a system, for network slice enhancement for a 5G UE includes receiving at an AP from a modem, a list of URSP rules, one or more S-NSSAI associated with one or more network slices categorized among configured, rejected, requested and allowed network slices and PDU session information.
  • the system includes maintaining, by the AP, a database to store information received at the AP, wherein the one or more network slices execute one or more services at the UE.
  • Fig. 1 illustrates an operational flow diagram depicting a process for receiving information related to one or more services, in accordance with an existing technique
  • Fig. 2 illustrates a illustrates an operational flow diagram depicting a process for displaying one or more icons for one or more network slices at a User Equipment (UE), in accordance with an embodiment of the present subject matter;
  • UE User Equipment
  • Fig. 3 illustrates an operational flow diagram depicting a process for displaying one or more icons for one or more network slices at a UE based on a route selection policy precedence, in accordance with an embodiment of the present subject matter
  • Fig. 4 illustrates an operational flow diagram depicting a process for displaying one or more icons for one or more network slices at a UE based on a network, in accordance with an embodiment of the present subject matter
  • Fig. 5 illustrates an operational flow diagram depicting a process for displaying one or more icons for one or more network slices at a UE from web Application Programming Interface (API), in accordance with an embodiment of the present subject matter;
  • API Application Programming Interface
  • Fig. 6 illustrates an operational flow diagram depicting a process for indicating one or more services about one or more network slices, in accordance with an embodiment of the present subject matter
  • Fig. 7 illustrates a tabular representation of URSP rules, in accordance with an embodiment of the present subject matter
  • Fig. 8 is an example illustration of a 5G network slice visibility at a UE, in accordance with an embodiment of the present subject matter
  • Fig. 9 is another example illustration of a 5G network slice visibility at a UE, in accordance with an embodiment of the present subject matter.
  • Fig. 10 illustrates a flow diagram depicting a process for receiving 5G network slice visibility by a UE, in accordance with an embodiment of the present subject matter
  • Fig. 11 illustrates a block diagram depicting a process to indicate an icon policy to an AP through a web Application Programming Interface (API), in accordance with an embodiment of the present subject matter;
  • API Application Programming Interface
  • Fig. 12 illustrates an operational flow diagram depicting a process for a network slice enhancement for a 5G UE, in accordance with an embodiment of the present subject matter
  • Fig. 13 illustrates an operational flow diagram depicting a process for displaying one or more icons associated with one or more Subscriber Identity Modules (SIMs) in a UE, in accordance with an embodiment of the present subject matter;
  • SIMs Subscriber Identity Modules
  • Fig. 14 illustrates an operational flow diagram depicting a process for a Network Slice Management for a 5G UE, in accordance with an embodiment of the present subject matter
  • Fig. 15 illustrates a schematic block diagram for slice information awareness, in accordance with an embodiment of the present subject matter
  • Fig. 16A, Fig. 16B, Fig. 17A, and Fig. 17B illustrate use case line diagrams and depicting a PDU session reject causes and relaying of PDU Session Accept information to an Application Processor through an abstract layer, in accordance with an embodiment of the present subject matter;
  • Fig. 18 illustrates a schematic block diagram for use case implementation of fig. 16A to and fig. 17B for multi-SIM UE, in accordance with an embodiment of the present subject matter
  • Fig. 19 illustrates a use case diagram for Coder decoders (CODECs), according to an embodiment of the present subject matter.
  • Fig. 20 is a diagram illustrating the configuration of a terminal in a wireless communication system according to an embodiment of the present subject matter.
  • Fig. 2 illustrates a illustrates an operational flow diagram 200 depicting a process for displaying one or more icons for one or more network slices at a User Equipment (UE), in accordance with an embodiment of the present subject matter.
  • the one or more icons may determine a status associated with the one or more network slices.
  • the one or more icons may be displayed to indicate an active usage of one or more network slices subscribed by one or more services at the UE.
  • the one or more icons may be stored in the UE.
  • the one or more icons may be stored in a memory in the UE.
  • the method may include initiating (step 202), by a modem incorporated in the UE, a Protocol Data Unit (PDU) session establishment with a network.
  • PDU Protocol Data Unit
  • the PDU session may be initiated by transmitting one of a PDU session establishment request, a PDU session modification, and a Non-Access Stratum (NAS) message by the UE to the network by the modem.
  • NAS Non-Access Stratum
  • the modem may be triggered to initiate the PDU session upon receiving a data connection from the AP, that may instruct the modem to initiate a PDU session establishment or initiate Protocol Data Unit (PDU) session with the network.
  • PDU Protocol Data Unit
  • the method in response to initiating the PDU session, may proceed towards receiving a PDU session establishment response at the modem from the network.
  • the PDU session establishment response, the PDU session modification, and the NAS message may include a service descriptive text, one of a URL for the one or more icons, the one or more icons, and an indication to form a Fully Qualified Domain Name (FQDN) with Single - Network Slice Selection Assistance Information (S-NSSAI) for the one or more icons associated with the S-NSSAI.
  • FQDN Fully Qualified Domain Name
  • S-NSSAI Single - Network Slice Selection Assistance Information
  • the S-NSSAI may be associated with the one or more network slices.
  • the method may proceed towards receiving (step 204), by the AP, an indication about one or more network slices being active for the PDU session from at least one of a modem and the network.
  • the AP may further receive, icon information for at least one other active PDU session available at the modem.
  • the icon information may be updated based on receiving on of a NAS message and new icon information related to an existing PDU session from the network.
  • the one or more icons may be stored in the memory prior to displaying the one or more icons.
  • the method may include displaying (step 206), by the AP, the one or more icons associated with the one or more network slices on an interface of the UE.
  • the process may further include classifying, by the AP, the one or more services based on the Single - Network Slice Selection Assistance Information (S-NSSAI) associated with the one or more services.
  • the one or more icons may be displayed based on one or more of a Standardized Slice/Service of the S-NSSAI associated with the one or more network slices currently active in the UE.
  • Examples of the Standardized Slice/Service of the one or more network slices may include, enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communications (URLLC), massive Machine Type Communications (mMTC), Vehicle-to-everything (V2X) and High-Performance Machine-Type Communications (HMTC).
  • the one or more icons may be displayed by the AP on an Application Programming Interface (API) at the UE.
  • the process may include updating, by the AP, the one or more icons displayed based on a data activity, the one or more services, QFIs, and GBR associated to the PDU session.
  • the one or more icons may be shared by the network to display the one or more icons based on one or more RRC States. Examples of the RRC states may include an RRC idle mode, an RRC connected mode and an RRC inactive mode.
  • Fig. 3 illustrates an operational flow diagram 300 depicting a process for displaying one or more icons for one or more network slices at a UE based on a route selection policy precedence, in accordance with an embodiment of the present subject matter.
  • the one or more icons may determine a status associated with the one or more network slices.
  • the one or more icons may be displayed to indicate an active usage of the one or more network slices subscribed by one or more services at the UE.
  • the route selection policy precedence may be based on a UE Route Selection Policy (URSP) table.
  • the route selection policy precedence may indicate an icon policy determined by one or more Original Equipment Manufacturer (OEMs).
  • the URSP table may include a list of URSP rules.
  • the list of URSP rules may include one or more traffic flow descriptors, one or more Route Selection Descriptors (RSDs).
  • the one or more RSDs may include the one or more icons.
  • the one or more icons may be displayed based on the one or more RSDs used for a PDU session establishment.
  • the process may include receiving (step 302) information associated with the one or more RSDs from a modem in the UE.
  • the information may be received from a modem in the UE by the AP.
  • the information may include a route selection descriptor precedence.
  • the process may proceed towards initiating (step 304) a PDU session by the UE with the network.
  • the PDU session may be initiated by the modem incorporated within the UE.
  • the PDU session may be established upon initiation by the UE based on the list of URSP rules.
  • the modem may be triggered to initiate the PDU session upon receiving a data connection from the AP, that may instruct the modem to initiate a PDU session establishment or initiate Protocol Data Unit (PDU) session with the network.
  • PDU Protocol Data Unit
  • the process may proceed towards displaying (step 306) the one or more icons based on the route selection descriptor precedence.
  • the one or more icons may be displayed by the AP on an interface of the UE.
  • the route selection descriptor precedence may be associated with the URSP table.
  • the one or more icons may be displayed based on the PDU session between the UE and the network.
  • the one or more icons may be displayed based on the active PDU session and a URSP table.
  • Fig. 4 illustrates an operational flow diagram 400 depicting a process for displaying one or more icons for one or more network slices at a UE based on a network, in accordance with an embodiment of the present subject matter.
  • the UE has an active PDU session with the network.
  • the one or more icons may determine a status associated with the one or more network slices.
  • the one or more icons may be displayed to indicate an active usage of the one or more network slices subscribed by one or more services at the UE.
  • the process may include configuring (step 402) a list of URSP rules by the network for the UE.
  • the list of URSP rules may be configured based on a Service-Level Agreement (SLA) with an application developer or specific policies enabled by operator for the set of application based on UE subscription.
  • the list of URSP rules may include one or more traffic flow descriptors, one or more Route Selection Descriptors (RSDs).
  • the one or more RSDs may include the one or more icons, a Fully Qualified Domain Names (FQDN) to fetch the one or more icons, and a URL to fetch the one or more icon.
  • SLA Service-Level Agreement
  • RSDs Route Selection Descriptors
  • FQDN Fully Qualified Domain Names
  • the process may include configuring a service-based icon policy based on a URSP table including the one or more RSDs including SST (Slice/Service Type) and Slice Differentiator (SD).
  • the icon policy may be depicted by an icon policy table including the SST and the SD, the one or more RSDs, a category, and the one or more icons associated with the category.
  • the SST may be an Ultra-Reliable Low Latency Communications (URLLC).
  • examples of the category may include, music, video, voice calling and video calling, and gaming.
  • the one or more RSDs may be "Route_Selection_Descriptor1(Precedence: 1 ,SSC Mode : 3 , DNN : Internet , Network Slice Selection : S-NSSAI1 , S-NSSAI2 )", and "Route_Selection_Descriptor2(Precedence : 3 , SSC Mode : 1 , DNN : IMS , Network Slice Selection : S-NSSAI4 , S-NSSAI5)”.
  • Table 2 depicts an example of icon policy table.
  • the icon policy table may be configured by the network.
  • the process may include transmitting one or more of a list of URLs, and a list of FQDNs, an indication to use the list of FQDNs with the S-NSSAI to the modem in the UE.
  • each URL may be FQDNs constructed by S-NSSAI.
  • the list of URLs/FQDN may be transmitted by the network.
  • the list of URLs/FQDN may include at least one icon corresponding to S-NSSAI.
  • the S-NSSAI may be associated with the one or more network slices and the one or more RSDs to the modem.
  • the list of URLs/FQDN may be provided to the UE in the URSP or a network provide such as a 5G Session Management Function during one of a PDU session establishment procedure and a PDU session modification procedure.
  • network may further provide information of the icon policy through a Representational State Transfer (REST) API support or through a (Common API Framework) CAPIF in URSP or during the PDU session establishment procedure or PDU session modification procedure or through any other Non-Access-Stratum (NAS) message.
  • REST Representational State Transfer
  • NAS Non-Access-Stratum
  • the process may proceed towards indicating (step 404) the list of URSP rules, and the list of URLs/FQDN to the AP from the modem.
  • the process may further include indicating by the modem, the AP about the S-NSSAI and the one or more RSDs utilized for establishing the PDU session between the UE and the network.
  • the S-NSSAI and the one or more RSDs may be mapped to a PDU session.
  • the process may proceed towards establishing (step 406) a PDU session by the modem incorporated with the UE with the network.
  • the modem may be triggered to initiate the PDU session upon receiving a data connection from the AP, that may instruct the modem to initiate a PDU session establishment or initiate the PDU session with the network.
  • the PDU session may be initiated by transmitting one of a PDU session establishment request, a PDU session modification, and a NAS message by the UE to the network by the modem.
  • the process may further include fetching (step 408) the one or more icons stored in the memory.
  • the memory may include at least one icon corresponding to one or more PDU Sessions. Subsequently, in an embodiment, where it is determined that the at least one icon is not identified by the AP from the from the memory for the one or more PDU sessions, the process may proceed towards step 410. In an embodiment, where it is determined that the at least one icon is identified, the process may terminate.
  • the process may further include fetching (step 410) at least one icon amongst the one or more icons from the list of URLs/FQDN corresponding to the S-NSSAI and the one or more RSDs utilized for establishing the PDU session.
  • the at least one icon may be fetched by the AP.
  • the process may include displaying (step 412) the one or more icons on a user Interface of the UE by the AP.
  • the UE may store the one or more icons associated with one or more PDU Sessions with the S-NSSAI in the memory by anyone.
  • the at least one icon may be fetched by one of a web API, the REST API, and the URSP table or the like.
  • Fig. 5 illustrates an operational flow diagram 500 depicting a process for displaying one or more icons for one or more network slices at a UE from web Application Programming Interface (API), in accordance with an embodiment of the present subject matter.
  • the network and the UE may have established one or more PDU Sessions.
  • the one or more icons may determine a status associated with the one or more network slices.
  • the one or more icons may be displayed to indicate an active usage of the one or more network slices subscribed by one or more services at the UE.
  • the process may include updating (step 502) a list of URSP rules with S-NSSAI and one or more RSDs present in an URSP table.
  • the updating may be performed by the network at the UE.
  • the S-NSSAI may be associated with the one or more network slices.
  • the list of URSP rules may include one or more traffic flow descriptors, the one or more Route Selection Descriptors (RSDs).
  • the process may include updating and caching by the AP an icon policy as depicted in the URSP table.
  • the process may include transmitting (step 504) the updated list of URSP rules to the AP.
  • the transmitting may be performed by the modem.
  • the process may include generating (step 506) a unique key by the AP based on the updated list of URSP rules.
  • the unique key may include, but are not limited to, the FQDN associated with the S-NSSAI, and one or more keys provided in the URSP table.
  • the process may include fetching (step 508) the one or more icons by the AP from the web API.
  • the web API may include the unique key.
  • the unique key at the web API may be similar to the unique key generated by the AP.
  • the unique key at the web API may be generated by an operator.
  • the AP may be indicated by the network for utilizing at least one of a RESTful API and a CAPIF for fetching the one or more icons.
  • the process may include fetching, by the AP, the one or more icons through at least one of the RESTful API and the CAPIF.
  • the process may include indicating (step 510) by the modem the S-NSSAI and the one or more RSDs utilized for the establishing the PDU session to the AP.
  • the process may include displaying the one or more icons on the API of the UE.
  • the one or more icons may be selected by the AP upon browsing through the one or more icons stored in a memory of the UE.
  • the one or more icons may be stored in a database in the memory.
  • the one or more icons may be selected by the AP upon determining that the one or more icons matches the S-NSSAI and the one or more RSDs utilized for establishing the PDU session.
  • Fig. 6 illustrates an operational flow diagram 600 depicting a process for indicating one or more services about one or more network slices, in accordance with an embodiment of the present subject matter.
  • the one or more services may be installed in a UE and the one or more network slices may be subscribed by the UE.
  • the process may include transmitting (step 602), by the modem, an indication to the AP including S-NSSAI associated with a PDU Session and at least one service amongst the one or more services available in the UE and in a network coverage in an area through a call back API.
  • the process may include receiving (step 604), by the API, the indication associated with the S-NSSAI and the at least one service available in the network coverage.
  • the process may proceed towards displaying (step 606), by the API, the one or more network slices available in the network coverage.
  • the AP may further display a highlighted icon associated with the at least one service, a semi-highlighted icon associated with at least another service unavailable in the network coverage based on the indication on the API.
  • the at least other service may include a network slice subscription.
  • the network slice may be amongst the one or more network slices.
  • the AP may further display an icon associated with at least one alternative service based on the indication.
  • Fig. 7 illustrates a tabular representation 700 of URSP rules, in accordance with an embodiment of the present subject matter.
  • the tabular representation 700 may interchangeably be referred as a URSP table.
  • the URSP table may be configured to provide a route selection policy precedence to the UE.
  • the route selection policy precedence may indicate an icon policy determined by one or more Original Equipment Manufacturer (OEMs).
  • the URSP table may include a list of URSP rules.
  • the list of URSP rules may include one or more traffic flow descriptors, one or more Route Selection Descriptors (RSDs).
  • the one or more RSDs may include the one or more icons.
  • the one or more icons may be displayed based on the one or more RSDs used for a PDU session establishment.
  • the list of URSP rules present in the URSP table may be utilized to create a PDU session on a modem in a UE.
  • Fig. 8 is an example illustration 800 of a user 5G network slice visibility at a UE, in accordance with an embodiment of the present subject matter.
  • the user may be provided with an icon and a service message description like "You are now enjoying Ultra-High-Speed Video Pack" from an operator.
  • the video application may be one or more services a referred in the fig. 1.
  • each slice related application information can also be displayed.
  • Fig. 9 is another example illustration 900 of a 5G network slice visibility at a UE, in accordance with an embodiment of the present subject matter.
  • the gaming application may be one or more services a referred in the fig. 1.
  • each slice related application information can also be displayed.
  • Fig. 10 illustrates a flow diagram 1000 depicting a process for receiving 5G network slice visibility by a UE, in accordance with an embodiment of the present subject matter.
  • a slice activity icon may be shown on an AP notification area.
  • the slice activity icon may be shown based on a Standardized Slice/Service (SST) of an active slice. Examples may include, but are not limited to, eMBB, URLLC, and MIoT.
  • SST Standardized Slice/Service
  • OEMs and operators may agree on various service specific icons.
  • the service specific icons may be displayed on the AP notification area, to indicate an active usage of a service subscription.
  • a modem may indicate the AP on the active slices for PDU Sessions.
  • the AP may use the indication to show agreed upon icon.
  • the slice activity may also be shown on an application, through an API.
  • the slice activity icon may also be shown based on a Route Selection Policy Precedence.
  • An URSP Rule table - icon policy may be decided by the OEMs.
  • the modem may indicate the AP, the icon to display. Upon creation of the PDU session one the modem through a URSP rule, the slice icon may be displayed. Later, the slice icon may be differentiated on based on the route selection descriptor precedence. Accordingly, the modem may indicate AP, the Precedence of the PDU session and based on the precedence, the AP may show an agreed upon icon.
  • Fig. 11 illustrates a block diagram 1100 depicting a process to indicate an icon policy to an AP through a web API, in accordance with an embodiment of the present subject matter.
  • a Policy Control Function (PCF) in a network updates a UE URSP table with S-NSSAIs in one or more RSDs along with other parameters.
  • the update may be a trigger for the AP to update an icon policy associated with the AP cache the icon policy.
  • a modem may provide the URSP table with the one or more RSDs to the AP.
  • the AP may make a unique key with the one or more RSDs, and an operator may make the same unique key in the operator's web API.
  • the AP may fetch all icons from the Web API, provided by the operator.
  • the modem may indicate the S-NSSAAIs and the one or more RSDs used for the PDU session to the AP. Further, the AP may browse through the icons stored that matches to a tuple received from the modem and display the icon at a UI.
  • the icon for a PDU Session may be available in a PDU Session Establishment Accept message.
  • the IE may contain an URL for the icon or the icon.
  • the IE may also include a service description text for a user.
  • multiple icons may be shared by the network to show each one on the basis of a RRC Idle/Inactive/Connected, or on the basis of a number of applications mapped, a number of user App IP tuples associated.
  • the icons may also be set to update based on certain app conditions, such as app service registration/deregistration, new QoS Flow Identifier (QFI) enabled, Guaranteed Bit Rate (GBR) assigned, URSP priority, number of DRBs associated, current bandwidth (BW) or the like.
  • app service registration/deregistration new QoS Flow Identifier (QFI) enabled
  • QFI QoS Flow Identifier
  • GRR Guaranteed Bit Rate
  • URSP priority number of DRBs associated
  • BW current bandwidth
  • standard slice type such as Internet of Things (IOT), Ultra-Reliable Low-Latency Communication (URLLC), Mobile Broadband (MBB) or the like. Any application mapped to the slices may be shown with a different icon.
  • IOT Internet of Things
  • URLLC Ultra-Reliable Low-Latency Communication
  • MBB Mobile Broadband
  • Fig. 12 illustrates an operational flow diagram 1200 depicting a process for a network slice enhancement for a 5G UE, in accordance with an embodiment of the present subject matter.
  • the process may include receiving (step 1202) at an AP from a modem, a list of URSP rules, one or more S-NSSAI associated with one or more network slices categorized among configured, rejected, requested and allowed network slices and PDU session information.
  • the list of URSP rules, the one or more S-NSSAI associated with one or more network slices categorized among configured, rejected, requested and allowed network slices and the PDU session information may also be referred as information.
  • the information may be received by the AP through generating an API within the AP at the UE.
  • the API may be configured for informing the one or more services within the UE about a number of events. Examples of the number of events may include a PDU Session Establishment Accept, a PDU session modification, a PDU session release, a PDU session reject procedure and one or more Network Access Stratum (NAS) mobility and session management related procedures.
  • the API may further be configured for updating the one or more services with data related parameters comprising one or more of a reject cause, a SSC mode, a PDU session type, a QoS rules, a Session AMBR, a 5GS network feature support, network slice information, a 5GSM capability and a multi access support.
  • the process may further include maintaining (step 1204), by the AP, a database to store information received at the AP, wherein the one or more network slices execute one or more services at the UE.
  • Fig. 13 illustrates an operational flow diagram 1300 depicting a process for displaying one or more icons associated with one or more Subscriber Identity Modules (SIMs) in a UE, in accordance with an embodiment of the present subject matter.
  • the one or more icons may correspond to one or more services in the UE.
  • the one or more SIMs may include a subscription for the one or more services at the UE.
  • the one or more services may be executed at the UE through one or more network slices subscribed by the one or more services at the UE.
  • the one or more icons may be displayed at an API generated by an AP at the UE.
  • the one or more icons may be displayed to show a subscription associated with the one or more network slices in a particular network registration area for each SIM.
  • the process may include fetching (step 1302), the S-NSSAI associated with at least one configured network slice and at least one allowed network slice amongst the one or more network slices.
  • the NSSAI associated with at least one configured network slice and at least one allowed network slice amongst the one or more network slices may be fetched from information received by the AP through the API.
  • the information may include the list of URSP rules, the one or more S-NSSAI associated with one or more network slices categorized among configured, rejected, requested and allowed network slices and PDU session information
  • the process may include discarding (step 1304), any rule from the set of URSP rules upon determining an absence of the S-NSSAI associated in the Route Selection Descriptor with at least one configured network slice or at least one allowed network slice.
  • the process may further include determining (step 1306) the one or more services in the UE with an available active network slice description with priorities at a current time and a location.
  • the determining may be performed by accessing a database associated with the one or more services at the UE in a memory.
  • the database may be associated with the one or more services in the UE.
  • the database may further include corresponding one or more network descriptors including APP_ID, IP 3 tuples, Connection Capability requirements (“V2X”, “Internet”, “ProSe”, etc.), specific DNNs, FQDNs, and one or more non-IP descriptors.
  • the process may proceed towards, triggering (step 1308), the AP, for displaying the one or more icons associated with the one or more services with a service descriptive text at an API of the UE.
  • the one or more icons may be displayed corresponding to the one or more SIMs.
  • the one or more icons may be displayed in an order based on a number of factors.
  • the number of factors may include the one or more services associated with the list of URSP rules in an order of the list of URSP rules precedence, most used one or more services, most recently used one or more services.
  • the one or more icons may be displayed within a Dedicated Data Subscription (DDS)selection menu on a User Interface (UI) of the UE.
  • DDS Dedicated Data Subscription
  • UI User Interface
  • the one or more icons associated with the one or more services may correspond to the one or more SIMs.
  • Fig. 14 illustrates an operational flow diagram 1400 depicting a process for a Network Slice Management for a 5G UE, in accordance with an embodiment of the present subject matter.
  • one or more network slices may be managed based on one or more services and one or more SIMs of a UE.
  • the process may include initiating (step 1402), by the UE, a data session for at least one service amongst the one or more services on a higher precedence network slice.
  • the data session may be a PDU session between the UE and the network initiated by the UE.
  • the data session may be initiated by the modem.
  • the data session may be initiated upon receiving a data connection from the AP.
  • the data connection may instruct the modem to initiate a PDU session establishment or initiate Protocol Data Unit (PDU) session with the network.
  • PDU Protocol Data Unit
  • the process may proceed towards receiving (step 1404), a reject message indicating a reason for failure to connect to the higher precedence network slice.
  • the reason for failure may be based on one of an operator determined barring, insufficient resources, missing or unknown DNN, user authentication or authorization failed, service option not supported, requested service option not subscribed, out of LADN service area, insufficient resources for specific slice and DNN, not supported SSC mode, insufficient resources for specific slice, and missing or unknown DNN in a network slice.
  • the process may include determining (step 1406) an alternate to continue the data session on higher precedence Network Slice. Continuing with the above embodiment, the process may further include performing at least one of steps 1408, step 1410 and step 1412.
  • the process may include sending (step 1408) a request for a plurality of attributes in the one or more RSDs of the plurality of URSP rules.
  • the plurality of attributes may include setting one or more new attributes such as one or more of S-NSSAI, an Access Point Name (APN), other TD parameter and RSD parameter, a minimum precedence value of one of a one or more TDs, and the one or more RSDs through which the UE may establish a connection.
  • the process may include resending (step 1410) a request for the data session after a time period indicated in the reject message;
  • the process may include sending (step 1412) by the AP, an evaluation request to the modem, to re-evaluate the plurality of new URSP rules;
  • the process may include registering (step 1414) the UE on a new Public Land Mobile Network (PLMN) based on the reject message.
  • the reject message may determine that the one or more services is not available on a current PLMN.
  • the UE may try to establish the PDU session for a network slice, or the UE may try to establish a session with one of the one or more TDs, and the one or more RSDs with a minimum precedence value unavailable due to S-NSSAI being absent from an allowed list.
  • the new PLMN may be manually selected by fetching by the AP an allowed S-NSSAI associated with at least one PLMN and the list of URSP rules from a web API with a UE ID and a location associated with the UE.
  • the PLMN may be selected manually by fetching by the AP, the allowed S-NSSAI associated with at least one PLMN and the list of URSP rules through a one of a Steering of Roaming (SoR) Container transport, NAS transport procedure or a UE Configuration Update (UCU) procedure of a Home Public Land Mobile Network (HPLMN).
  • SoR Steering of Roaming
  • UCU UE Configuration Update
  • the PLMN may be selected manually by fetching by the AP the allowed S-NSSAI associated with at least one PLMN and the list of URSP rules by temporarily registering on each scanned VPLMN providing an allowed S-NSSAI with a mapped HPLMN S-NSSAI utilized to check the URSP rules for the session establishment.
  • the PLMN may be selected automatically when the UE is in a roaming area.
  • fetching the S-NSSAI associated with the at least one configured network slice and the at least one allowed network slice may be based on determining by the AP a probability of utilizing the one or more services in the UE by a user through a Machine Learning (ML) module.
  • ML Machine Learning
  • the probability may be based on a previous history of utilizing one or more services by the user. In an embodiment, determining the probability of utilizing the one or more services in the UE by the user through the ML module may be based on monitoring over a period of time, a historical utilization the one or more services by the user. In an embodiment, the process may further include upon monitoring the historical utilization, determining, the probability of utilizing the one or more services by the user after the said period of time.
  • the process may include updating (step 1416) by the AP a database in the UE.
  • the database may include mapped S-NSSAI and a URSP table.
  • the updating may be performed with the web API when the allowed S-NSSAI associated with at least one PLMN and the list of URSP rules is fetched from the web API.
  • the updating may be performed with one of SoR container transport, the NAS transport procedure and the UCU procedure when the allowed S-NSSAI associated with at least one PLMN and the list of URSP rules is fetched through one of the SoR container transport, the NAS transport procedure and the UCU procedure of the HPLMN.
  • the updating may be performed upon temporarily registering on each scanned VPLMN when the Allowed S-NSSAI associated with at least one PLMN and the list of URSP rules is fetched by temporarily registering on each scanned VPLMN.
  • the process may include displaying (step 1418) by the AP one or more icons for the one or more services associated with the Allowed S-NSSAIs.
  • the one or more icons may be displayed within a DDS selection menu on a User Interface (UI) of the UE.
  • UI User Interface
  • Fig. 15 illustrates a schematic block diagram 1500 for slice information awareness, in accordance with an embodiment of the present subject matter.
  • a slice related information may be shared with an AP.
  • the AP may be configured to generate a PDU session request (APP_ ID, DNN, NSSAI, SCC Mode, etc.) with a network.
  • the PDU session request may include a slice priority and at least one other preference.
  • the AP may receive PDU session information and serving slice information for enhancing an interface of a UE. Further, the interface may broadcast one or more network slices and URSP rules related information for transparency.
  • a CP may generate a response including PDU session information (DNN AMBR, QCI, etc), slice information (serving and rejected), and the URSP Rules on "Need to know basis".
  • PDU session information DNN AMBR, QCI, etc
  • slice information serving and rejected
  • the URSP Rules and active and reject slices amongst the one or more network slices may be broadcasted as per need basis such as showing Icons for better QoS Slices, providing serving slice details to enhance a user experience, providing rejected slice details, indicating the URSP Rules stored to tweak Traffic Descriptor of data requesting one or more services to avoid a slice congestion.
  • the response is then routed to the AP to establish the session.
  • Fig. 16A to Fig. 17B illustrate use case line diagrams depicting a PDU session reject causes and relaying of PDU Session Accept information to an Application Processor through an abstract layer, in accordance with an embodiment of the present subject matter.
  • Fig. 18 illustrates a schematic block diagram 1800 for use case implementation of fig. 16A to fig. 17B for multi-SIM UE, in accordance with an embodiment of the present subject matter.
  • a SIM#1 -TD1 may include an application id and an RSD for the TD1 may include a route selection descriptor.
  • an application may be an over the air media streaming application.
  • an RSD11 DNN as Internet and S-NSSAI_A, precedence 1.
  • RSD12 Data Network Name (DNN) as Internet and S-NSSAI_B, precedence 2.
  • a user may set the data preference on SIM 1 or currently SIM 1 is being used for the data.
  • FIG. 17 when the Application starts, the application may request for a call establishment (application may use parameters such as priority, minimum QoS support or the like). Further, priority means, whether application may want to camp to any slice in the route selection descriptor or referred slice only (precedence 1 slice or up to precedence 2). If a precedence is defined, a UE may try establishing a PDU session with TD with corresponding precedence. If connection is not possible, an abstraction later return error with other possible option such as a second precedence available, other Subscriber Identity Module (SIM) has the slice for the application or the like. Further application may use the information to show information like "on best network".
  • SIM Subscriber Identity Module
  • the application requested for the call establishment (any priority).
  • User priority is SIM#1
  • two traffic descriptors is identified for the over the air media streaming application.
  • the UE may try PDU session establishment with attributes of first traffic descriptor but fail.
  • the UE may try PDU session establishment with attributes of second traffic descriptor which is successful.
  • the URSP from SIM2 may be checked for available policy.
  • the abstraction layer may receive information about a data call success with information about a reject cause of the first traffic descriptor, timer, information about availability of better slice on second SIM.
  • the application may take the information to show, not on the best network, better system available in SIM#2.
  • Fig. 19 illustrates a use case diagram 1900 for Coder decoders (CODECs), according to an embodiment of the present subject matter.
  • Codecs are used by applications for data compression and decompression to transfer data, For Example: CODEC#1 for video uses more battery but requires less data rate, CODEC#2 for video uses less battery but requires more data rate.
  • a flow diagram is proposed for optimal switch between CODEC#1 and CODEC#2.
  • Fig. 20 is a diagram illustrating the configuration of a terminal 2000 in a wireless communication system according to an embodiment of the present subject matter.
  • terms including “unit” or “er” at the end may refer to the unit for processing at least one function or operation and may be implemented in hardware, software, or a combination of hardware and software.
  • the terminal 2000 may include an Application Processor (AP) 2002 (e.g., at least one processor), a memory 2004 (e.g., storage), data 2006 and, module(s) 2008, and a modem 2010 (e.g., communicator or communication interface).
  • AP Application Processor
  • the terminal 2000 may be a User Equipment, such as a cellular phone or other device that communicates over a plurality of cellular networks (such as a 4G, a 5G or pre-5G network or any future wireless communication network).
  • the AP 2002, the memory 2004, the data 2006, and the module(s) 2008, and the modem 2010 may be communicably coupled with one another.
  • the terminal 2000 may be understood as one or more of a hardware, a software, a logic-based program, a configurable hardware, and the like.
  • the AP 2002 may be a single processing unit or a number of units, all of which could include multiple computing units.
  • the processor may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, processor cores, multi-core processors, multiprocessors, state machines, logic circuitries, application-specific integrated circuits, field-programmable gate arrays and/or any devices that manipulate signals based on operational instructions.
  • the AP 2002 may be configured to fetch and/or execute computer-readable instructions and/or data 2006 stored in the memory 2004.
  • the memory 2004 may include any non-transitory computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM) and/or dynamic random access memory (DRAM), and/or non-volatile memory, such as read-only memory (ROM), erasable programmable ROM (EPROM), flash memory, hard disks, optical disks, and/or magnetic tapes.
  • volatile memory such as static random access memory (SRAM) and/or dynamic random access memory (DRAM)
  • non-volatile memory such as read-only memory (ROM), erasable programmable ROM (EPROM), flash memory, hard disks, optical disks, and/or magnetic tapes.
  • the memory 2004 may store data, such as a basic program, an application program, configuration information, and the like for operating the terminal 2000.
  • the memory 2004 may be configured as a volatile memory, a non-volatile memory, or a combination of a volatile memory and a non-volatile memory.
  • the memory 2004 may include the data
  • the data 2006 serves, amongst other things, as a repository for storing data processed, received, and generated by one or more of, the AP 2002, the memory 2004, the module(s) 2008, and the modem 2010.
  • the module(s) 2008 may include routines, programs, objects, components, data structures, etc., which perform particular tasks or implement data types.
  • the module(s) 2008 may also be implemented as, signal processor(s), state machine(s), logic circuitries, and/or any other device or component that manipulate signals based on operational instructions.
  • the module(s) 2008 may be implemented in hardware, instructions executed by at least one processing unit, for e.g., AP 2002, or by a combination thereof.
  • the processing unit may be a general-purpose processor which executes instructions to cause the general-purpose processor to perform operations or, the processing unit may be dedicated to performing the required functions.
  • the module(s) 2008 may be machine-readable instructions (software) which, when executed by a processor/processing unit, may perform any of the described functionalities.
  • the module(s) 2008 may be machine-readable instructions (software) which, when executed by a processor/processing unit, perform any of the described functionalities.
  • the AP 2002 may control overall operations of the terminal 2000. For example, the AP 2002 may transmit and receive a signal via the modem 2010. Further, the AP 2002 records data in the memory 2004 and reads the recorded data. The AP 2002 may perform the functions of a protocol stack required by a particular communication standard. To this end, the AP 2002 may include at least one processor or micro-processor or may be a part of the processor. Also, a part of the modem 2010 and the AP 2002 may be referred to as a communication processor (CP).
  • CP communication processor
  • the AP 2002 may be configured to initiate a data connection, that may instruct the modem 2010 to initiate a PDU session establishment or initiate Protocol Data Unit (PDU) session with a network.
  • initiating the PDU session may include receiving a PDU session establishment response at the modem 2010from the network.
  • the PDU session establishment response may be received upon transmitting a PDU session establishment request from the modem 2010 to the network.
  • the PDU session establishment response may include a service descriptive text, one of a URL for the one or more icons, the one or more icons and an indication to form a FQDN with S- NSSAI for the one or more icons associated with the S-NSSAI.
  • the S-NSSAI may be associated with the one or more network slices.
  • the AP 2002 may be configured to receive an indication about one or more network slices being active for the PDU session from at least one of a modem 2010 and the network.
  • the AP 2002 may further receive, icon information for at least one other active PDU session available at the modem 2010.
  • the icon information may be updated based on receiving on of a NAS message and new icon information related to an existing PDU session from the network
  • the one or more icons may be stored in a memory 2004 prior to displaying the one or more icons.
  • the AP 2002 may be configured to display the one or more icons associated with the one or more network slices on an interface of the UE.
  • the AP 2002 may further be configured to classify the one or more services based on the S-NSSAI associated with the one or more services.
  • the one or more icons may be displayed based on one or more of a Standardized Slice/Service of the S-NSSAI associated with the one or more network slices currently active in the UE. Examples of the Standardized Slice/Service of the one or more network slices may include, enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communications (URLLC), massive Machine Type Communications (mMTC), Vehicle-to-everything (V2X) and High-Performance Machine-Type Communications(HMTC).
  • eMBB enhanced Mobile Broadband
  • URLLC Ultra Reliable Low Latency Communications
  • mMTC massive Machine Type Communications
  • V2X Vehicle-to-everything
  • HMTC High-Performance Machine-Type Communications
  • the one or more icons may be displayed based on one or more of a Standardized Slice/Service of the one or more network slices.
  • the Standardized Slice/Service of the one or more network slices may include, enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communications (URLLC), massive Machine Type Communications (mMTC), Vehicle-to-everything (V2X) and High-Performance Machine-Type Communications (HMTC).
  • the one or more icons may be displayed by the AP 2002 on an API at the UE.
  • the AP 2002 may be configured to update the one or more icons displayed based on a data activity, the one or more services, QFIs, and GBR associated to the PDU session.
  • the one or more icons may be shared by the network to display the one or more icons based on one or more RRC States. Examples of the RRC states may include an RRC idle mode, an RRC connected mode and an RRC inactive mode.
  • a process for displaying one or more icons for one or more network slices at a UE based on a route selection policy precedence is disclosed.
  • the one or more icons may determine a status associated with the one or more network slices.
  • the one or more icons may be displayed to indicate an active usage of the one or more network slices subscribed by one or more services at the UE.
  • the route selection policy precedence may be based on a UE Route Selection Policy (URSP) table.
  • the route selection policy precedence may indicate an icon policy determined by one or more Original Equipment Manufacturer (OEMs).
  • the URSP table may include a list of URSP rules.
  • the list of URSP rules may include one or more traffic flow descriptors, one or more Route Selection Descriptors (RSDs).
  • the one or more RSDs may include the one or more icons.
  • the one or more icons may be displayed based on the one or more RSDs.
  • the AP 2002 may be configured to receive information associated with the one or more RSDs from the modem 2010 in the UE.
  • the information may include a route selection descriptor precedence.
  • the UE may be configured to initiate a PDU session with the network.
  • the PDU session may be initiated by the modem 2010.
  • the PDU session may be established upon initiation by the UE based on the list of URSP rules.
  • the modem 2010 may be triggered to initiate the PDU session upon receiving a data connection from the AP 2002, that may instruct the modem to initiate a PDU session establishment or initiate Protocol Data Unit (PDU) session with the network.
  • PDU Protocol Data Unit
  • the AP 2002 may be configured to display the one or more icons based on the route selection descriptor precedence on an interface of the UE.
  • the route selection descriptor precedence may be associated with the URSP table.
  • the one or more icons may be displayed based on the PDU session between the UE and the network.
  • the one or more icons may be displayed based on the active PDU session and a URSP table.
  • a process for displaying one or more icons for one or more network slices at a UE based on a network is disclosed.
  • the network and the UE may be connected in a PDU session with one another.
  • the one or more icons may determine a status associated with the one or more network slices.
  • the one or more icons may be displayed to indicate an active usage of the one or more network slices subscribed by one or more services at the UE.
  • the network may configure a list of URSP rules by the network for the UE.
  • the list of URSP rules may be configured based on a Service-Level Agreement (SLA) with an application developer or specific policies enabled by operator for the set of application based on UE subscription.
  • the list of URSP rules may include one or more traffic flow descriptors, one or more Route Selection Descriptors (RSDs).
  • the one or more RSDs may include the one or more icons, a Fully Qualified Domain Names (FQDN) to fetch the one or more icons, and a URL to fetch the one or more icon.
  • SLA Service-Level Agreement
  • RSDs Route Selection Descriptors
  • FQDN Fully Qualified Domain Names
  • the network may configure a service-based icon policy based on a URSP table including the one or more RSDs including SST (Slice/Service Type) and Slice Differentiator (SD).
  • the icon policy may be depicted by an icon policy table including the SST and the SD, the one or more RSDs, a category, and the one or more icons associated with the category.
  • the SST may be an Ultra-Reliable Low Latency Communications (URLLC).
  • examples of the category may include, music, video, voice calling and video calling, and gaming.
  • the one or more RSDs may be "Route_Selection_Descriptor1(Precedence: 1 ,SSC Mode : 3 , DNN : Internet , Network Slice Selection : S-NSSAI1 , S-NSSAI2 )", and "Route_Selection_Descriptor2(Precedence : 3 , SSC Mode : 1 , DNN : IMS , Network Slice Selection : S-NSSAI4 , S-NSSAI5)”.
  • the network may transmit one or more of a list of URLs, and a list of FQDNs, an indication to use the list of FQDNs with the S-NSSAI to the modem in the UE.
  • each URL may be FQDNs constructed by S-NSSAI.
  • the list of URLs/FQDN may include at least one icon corresponding to S-NSSAI.
  • the S-NSSAI may be associated with the one or more network slices and the one or more RSDs to the modem.
  • the list of URLs/FQDN may be provided to the UE in the URSP or a network provide such as a 5G Session Management Function during one of a PDU session establishment procedure and a PDU session modification procedure.
  • network may further provide information of the icon policy through REST API support or through CAPIF (Common API Framework) in URSP or during the PDU session establishment procedure or PDU session modification procedure or through any other Non-Access-Stratum (NAS) message.
  • CAPIF Common API Framework
  • the modem 2010 may be configured to indicate the list of URSP rules, and the list of URLs/FQDN to the AP 2002.
  • the modem 2010 may further be configured to indicate the AP 2002 about the S-NSSAI and the one or more RSDs utilized for establishing the PDU session between the UE and the network.
  • the S-NSSAI and the one or more RSDs may be mapped to a PDU session.
  • the modem 2010 may be configured to establish a PDU session with the network.
  • the modem 2010 may be triggered to initiate the PDU session upon receiving a data connection from the AP 2002, that may instruct the modem 2010 to initiate a PDU session establishment or initiate the PDU session with the network.
  • the PDU session may be initiated by transmitting one of a PDU session establishment request, a PDU session modification, and a NAS message by the UE to the network by the modem.
  • the AP 2002 may be configured to fetch the one or more icons stored in the memory 2004.
  • the memory 2004 may include at least one icon corresponding to one or more PDU Sessions.
  • the AP 2002 may be configured to fetch at least one icon amongst the one or more icons from the list of URLs/FQDN corresponding to the S-NSSAI and the one or more RSDs utilized for establishing the PDU session.
  • the AP 2002 may be configured to display the one or more icons on a user interface of the UE. Furthermore, the UE may store the one or more icons associated with one or more PDU Sessions with the S-NSSAI in the memory 2004 by anyone.
  • the at least one icon may be fetched by one of a web API, the REST API, and the URSP table or the like.
  • a process for displaying one or more icons for one or more network slices at a UE from web Application Programming Interface is disclosed.
  • the network and the UE may be connected in a PDU session with one another.
  • the one or more icons may determine a status associated with the one or more network slices.
  • the one or more icons may be displayed to indicate an active usage of the one or more network slices subscribed by one or more services at the UE.
  • the network may be configured to update a list of URSP rules with S-NSSAI and one or more RSDs present in an URSP table.
  • the S-NSSAI may be associated with the one or more network slices.
  • the list of URSP rules may include one or more traffic flow descriptors, the one or more Route Selection Descriptors (RSDs).
  • the AP 2002 may be configured to update and cache an icon policy as depicted in the URSP table.
  • the modem 2010 be configured to transmit the updated list of URSP rules to the AP 2002.
  • the AP 2002 may be configured to generate a unique key based on the updated list of URSP rules. Examples of the unique key may include, but are not limited to, the FQDN associated with the S-NSSAI, and one or more keys provided in the URSP table.
  • the AP 2002 may be configured to fetch the one or more icons by the AP 2002 from the web API.
  • the web API may include the unique key.
  • the unique key at the web API may be similar to the unique key generated by the AP 2002.
  • the unique key at the web API may be generated by an operator.
  • the AP 2002 may be indicated by the network for utilizing at least one of a RESTful API and a CAPIF for fetching the one or more icons. Moving forward, the AP 2002 may be configured to fetch the one or more icons through at least one of the RESTful API and the CAPIF.
  • the modem 2010 may be configured to indicate the S-NSSAI and the one or more RSDs utilized for the establishing the PDU session to the AP2002.
  • the AP 2002 may be configured to display the one or more icons on the API of the UE.
  • the one or more icons may be selected by the AP 2002 upon browsing through the one or more icons stored in a memory of the UE.
  • the one or more icons may be stored in a database in the memory.
  • the one or more icons may be selected by the AP 2002 upon determining that the one or more icons matches the S-NSSAI and the one or more RSDs utilized for establishing the PDU session.
  • a process for indicating one or more services about one or more network slices is disclosed.
  • the one or more services may be installed in a UE and the one or more network slices may be subscribed by the UE.
  • the modem 2010 may be configured to transmit an indication to the AP 2002 including S-NSSAI associated with a PDU Session and at least one service amongst the one or more services available in the UE and in a network coverage in an area through a call back API.
  • the AP 2002 may be configured to receive at the API, the indication associated with the S-NSSAI and the at least one service available in the network coverage.
  • the AP 2002 may be configured to display at the API, the one or more network slices available in the network coverage.
  • the AP 2002 may further display a highlighted icon associated with the at least one service, a semi-highlighted icon associated with at least another service unavailable in the network coverage based on the indication on the API.
  • the at least other service may include a network slice subscription.
  • the network slice may be amongst the one or more network slices.
  • the AP 2002 may further display an icon associated with at least one alternative service based on the indication.
  • the AP 2002 may be configured to receive from the modem 2010, a list of URSP rules, one or more S-NSSAI associated with one or more network slices categorized among configured, rejected, requested and allowed network slices and PDU session information.
  • the list of URSP rules, the one or more S-NSSAI associated with one or more network slices categorized among configured, rejected, requested and allowed network slices and the PDU session information may also be referred as information.
  • the information may be received by the AP 2002 through generating an API within the AP 2002 at the UE.
  • the API may be configured for informing the one or more services within the UE about a number of events. Examples of the number of events may include a PDU Session Establishment Accept, a PDU session modification, a PDU session release, a PDU session reject procedure and one or more Network Access Stratum (NAS) mobility and session management related procedures.
  • the API may further be configured for updating the one or more services with data related parameters comprising one or more of a reject cause, a SSC mode, a PDU session type, a QoS rules, a Session AMBR, a 5GS network feature support, network slice information, a 5GSM capability and a multi access support.
  • the AP 2002 may be configured to maintain a database to store information received at the AP 2002, wherein the one or more network slices execute one or more services at the UE.
  • a process for displaying one or more icons associated with one or more Subscriber Identity Modules (SIMs) in a UE for assisting a DDS selection is disclosed.
  • the one or more icons may correspond to one or more services in the UE.
  • the one or more SIMs may include a subscription for the one or more services at the UE.
  • the one or more services may be executed at the UE through one or more network slices subscribed by the one or more services at the UE.
  • the one or more icons may be displayed at an API generated by the AP 2002 at the UE.
  • the one or more icons may be displayed to show a subscription associated with the one or more network slices in a particular network registration area for each SIM.
  • the AP 2002 may be configured to fetch the S-NSSAI associated with at least one configured network slice and at least one allowed network slice amongst the one or more network slices from information received through the API.
  • the information may include the list of URSP rules, the one or more S-NSSAI associated with one or more network slices categorized among configured, rejected, requested and allowed network slices and PDU session information.
  • the AP 2002 may be configured to discard any rule from the set of URSP rules upon determining an absence of the S-NSSAI associated in the Route Selection Descriptor with at least one configured network slice or at least one allowed network slice.
  • AP 2002 may be configured to determine the one or more services in the UE with an available active network slice description with priorities at a current time and a location.
  • the determining may be performed by accessing a database associated with the one or more services at the UE in a memory.
  • the database may be associated with the one or more services in the UE.
  • the database may further include corresponding one or more network descriptors including APP_ID, IP 3 tuples, Connection Capability requirements (“V2X”, “Internet”, “ProSe”, etc.), specific DNNs, FQDNs, and one or more non-IP descriptors.
  • AP 2002 may be configured to display the one or more icons associated with the one or more services at an API of the UE.
  • the one or more icons may be displayed corresponding to the one or more SIMs.
  • the one or more icons may be displayed in an order based on a number of facts.
  • the number of factors may include the one or more services associated with the list of URSP rules in order of the list of URSP rules precedence, most used one or more services, most recently used one or more services.
  • the one or more icons may be displayed within a Dedicated Data Subscription (DDS)selection menu on a User Interface (UI) of the UE.
  • DDS Dedicated Data Subscription
  • UI User Interface
  • the one or more icons associated with the one or more services may correspond to the one or more SIMs.
  • one or more network slices may be managed based on one or more services and one or more SIMs of a UE.
  • the modem 2002 may be configured to initiate a data session for at least one service amongst the one or more services on a higher precedence network slice.
  • the data session may be a PDU session between the UE and the network.
  • the data session may be initiated upon receiving a data connection from the AP 2002.
  • the data connection may instruct the modem 2010 to initiate a PDU session establishment or initiate Protocol Data Unit (PDU) session with the network.
  • PDU Protocol Data Unit
  • AP 2002 may be configured to receive a reject message indicating a reason for failure to connect to the higher precedence network slice.
  • the reason for failure may be based on one of an operator determined barring, insufficient resources, missing or unknown DNN, user authentication or authorization failed, service option not supported, requested service option not subscribed, out of LADN service area, insufficient resources for specific slice and DNN, not supported SSC mode, insufficient resources for specific slice, and missing or unknown DNN in a network slice.
  • the AP 2002 may be configured to determine an alternate to continue the data session on higher precedence Network Slice. Continuing with the above embodiment, Subsequently, AP 2002 may be configured to perform at least one of sending a request for a plurality of new URSP rules and resending a request for the data session after a time period indicated in the reject message.
  • the AP 2002 may be configured to send an evaluation request to the modem 2010, to re-evaluate the plurality of new URSP rules and initiating a PDU session request with the S-NSSAI in a rejected list with a corresponding back off timer expiry.
  • AP 2002 may be configured to register the UE on a new Public Land Mobile Network (PLMN) based on the reject message.
  • PLMN Public Land Mobile Network
  • the reject message may determine that the one or more services is not available on a current PLMN.
  • the UE may try to establish the PDU session for a network slice, or the UE may try to establish a session with one of the one or more TDs, and the one or more RSDs with a minimum precedence value unavailable due to S-NSSAI being absent from an allowed list.
  • the new PLMN may be manually selected by fetching by the AP 2002 an allowed S-NSSAI associated with at least one PLMN and the list of URSP rules from a web API with a UE ID and a location associated with the UE.
  • the PLMN may be selected manually by fetching by the AP 2002, the allowed S-NSSAI associated with at least one PLMN and the list of URSP rules through a one of a SoR container transport, a NAS transport procedure and a UCU procedure of a HPLMN.
  • the PLMN may be selected manually by fetching by the AP 2002 the allowed S-NSSAI associated with at least one PLMN and the list of URSP rules by temporarily registering on each scanned VPLMN providing an allowed S-NSSAI with a mapped HPLMN S-NSSAI utilized to check the URSP rules for the session establishment.
  • the PLMN may be selected automatically when the UE is in a roaming area.
  • fetching the S-NSSAI associated with the at least one configured network slice and the at least one allowed network slice may be based on determining by the AP 2002 a probability of utilizing the one or more services in the UE by a user through a ML module.
  • the probability may be based on a previous history of utilizing one or more services by the user. In an embodiment, determining the probability of utilizing the one or more services in the UE by the user through the ML module may be based on monitoring over a period of time, a historical utilization the one or more services by the user. In an embodiment, the AP 2002 may further be configured to determine, the probability of utilizing the one or more services by the user after the said period of time. upon monitoring the historical utilization.
  • AP 2002 may be configured to update a database in the UE.
  • the database may include mapped S-NSSAI and a URSP table.
  • the updating may be performed with the web API when the allowed S-NSSAI associated with at least one PLMN and the list of URSP rules is fetched from the web API.
  • the updating may be performed with one of the SoR container transport, the NAS transport procedure and the UCU procedure when the allowed S-NSSAI associated with at least one PLMN and the list of URSP rules is fetched through a one of the SoR container transport, the NAS transport procedure and the UCU procedure of the HPLMN.
  • the updating may be performed upon temporarily registering on each scanned VPLMN when the Allowed S-NSSAI associated with at least one PLMN and the list of URSP rules is fetched by temporarily registering on each scanned VPLMN.
  • AP 2002 may be configured to display one or more icons for the one or more services associated with the Allowed S-NSSAIs.
  • the one or more icons may be displayed within a DDS selection menu on a User Interface (UI) of the UE.
  • UI User Interface

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Security & Cryptography (AREA)
  • Telephonic Communication Services (AREA)

Abstract

Dans un mode de réalisation, un procédé, destiné à l'affichage d'une icône pour une tranche de réseau au niveau d'un équipement utilisateur (UE), est divulgué. Le procédé comprend l'initiation, par un modem, d'une session d'unité de données de protocole (PDU) avec un réseau par transmission d'une demande d'établissement de session PDU, d'une modification de session PDU, et d'un message NAS. Le procédé comprend la réception, par un AP, d'une indication concernant une ou plusieurs tranches de réseau qui sont actives pour la session PDU en provenance d'au moins l'un du modem et du réseau. Le procédé comprend l'affichage, par l'AP, d'une ou plusieurs icônes associées à la ou aux tranches de réseau sur une interface de l'UE.
PCT/KR2021/014416 2020-10-16 2021-10-15 Procédés et systèmes destinés à l'amélioration l'expérience de tranche de réseau d'utilisateur WO2022080976A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202041045181 2020-10-16
IN202041045181 2020-10-16

Publications (1)

Publication Number Publication Date
WO2022080976A1 true WO2022080976A1 (fr) 2022-04-21

Family

ID=81209469

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2021/014416 WO2022080976A1 (fr) 2020-10-16 2021-10-15 Procédés et systèmes destinés à l'amélioration l'expérience de tranche de réseau d'utilisateur

Country Status (1)

Country Link
WO (1) WO2022080976A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2625548A (en) * 2022-12-20 2024-06-26 Nokia Technologies Oy Logical network configuration

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190069229A1 (en) * 2017-08-25 2019-02-28 Qualcomm Incorporated Techniques and apparatuses for search, measurement, and icon display in new radio non-standalone mode
US20200037387A1 (en) * 2018-07-24 2020-01-30 Samsung Electronics Co., Ltd. Electronic device for displaying indicator regarding network and method thereof
US20200068482A1 (en) * 2018-08-27 2020-02-27 T-Mobile Usa, Inc. Variable interval signal scanning in dual connectivity communication networks
US20200169921A1 (en) * 2017-08-04 2020-05-28 Huawei Technologies Co., Ltd. Method and apparatus for associating application with network slice, and communications system
US20200187085A1 (en) * 2018-12-10 2020-06-11 Verizon Patent And Licensing Inc. Application-based user equipment route selection policy mapping

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200169921A1 (en) * 2017-08-04 2020-05-28 Huawei Technologies Co., Ltd. Method and apparatus for associating application with network slice, and communications system
US20190069229A1 (en) * 2017-08-25 2019-02-28 Qualcomm Incorporated Techniques and apparatuses for search, measurement, and icon display in new radio non-standalone mode
US20200037387A1 (en) * 2018-07-24 2020-01-30 Samsung Electronics Co., Ltd. Electronic device for displaying indicator regarding network and method thereof
US20200068482A1 (en) * 2018-08-27 2020-02-27 T-Mobile Usa, Inc. Variable interval signal scanning in dual connectivity communication networks
US20200187085A1 (en) * 2018-12-10 2020-06-11 Verizon Patent And Licensing Inc. Application-based user equipment route selection policy mapping

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2625548A (en) * 2022-12-20 2024-06-26 Nokia Technologies Oy Logical network configuration

Similar Documents

Publication Publication Date Title
WO2020197288A1 (fr) Procédé et dispositif pour fournir une connectivité à un terminal afin d'utiliser un service informatique périphérique
US11026080B2 (en) Policy control function determining method, apparatus, and system
CN109076422B (zh) 一种通信系统间移动方法、用户设备和存储介质
EP3499838B1 (fr) Procédé de traitement de session et dispositif associé
WO2021091285A1 (fr) Procédé et appareil pour commander une tranche de réseau dans un système de communication sans fil
CN111567113B (zh) 会话建立方法、中继设备的选择方法和注册方法及设备
CN113708947B (zh) 切片接入方法、装置及系统
CN110383790A (zh) 无需会话连续性的网络服务连续性
WO2019035638A1 (fr) Procédé de vérification d'une modification d'un type de connexion sans fil d'un terminal dans un serveur d'applications tiers
WO2016099174A1 (fr) Procédé et appareil de réception, par un terminal mobile en mode de repos, d'un service d'extrémité mobile dans un système de communications
WO2022080972A1 (fr) Procédé et systèmes pour améliorer l'expérience utilisateur de tranche de réseau
CN114175600A (zh) 一种获取信息的方法及装置
WO2022025666A1 (fr) Procédé et dispositif d'utilisation simultanée de tranches de réseau
WO2021096325A1 (fr) Procédé et appareil pour améliorer une précision de contrôle de tranche de réseau dans un système de communication sans fil
US20220124609A1 (en) Method and systems for enhancing user network slice experience
WO2021045531A1 (fr) Appareil et procédé d'automatisation de réseau dans un système de communication sans fil
WO2022080976A1 (fr) Procédés et systèmes destinés à l'amélioration l'expérience de tranche de réseau d'utilisateur
WO2022164199A1 (fr) Procédé et appareil de configuration d'une session dans un système de communication sans fil
US11991781B2 (en) Subscriber data management method and apparatus
WO2022216047A1 (fr) Procédé et appareil de configuration d'informations de service informatique en périphérie
CN114786142B (zh) 呼叫方法、装置、计算机可读存储介质及电子设备
WO2023059141A1 (fr) Procédé et dispositif d'accès d'une session à routage de rattachement à un plmn visité dans un système de communication sans fil
US20240187374A1 (en) Method and apparatus for improving a server discovery handling procedure
WO2023191465A1 (fr) Procédés et appareil pour la configuration d'une politique de sélection d'itinéraire
JP5272851B2 (ja) 通信傍受システム、通信傍受装置、通信傍受方法およびプログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21880622

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21880622

Country of ref document: EP

Kind code of ref document: A1