EP4183223A1 - Informations spécifiques à des tranches verticales - Google Patents

Informations spécifiques à des tranches verticales

Info

Publication number
EP4183223A1
EP4183223A1 EP20743851.6A EP20743851A EP4183223A1 EP 4183223 A1 EP4183223 A1 EP 4183223A1 EP 20743851 A EP20743851 A EP 20743851A EP 4183223 A1 EP4183223 A1 EP 4183223A1
Authority
EP
European Patent Office
Prior art keywords
network slice
specific information
node
information
network
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
EP20743851.6A
Other languages
German (de)
English (en)
Inventor
Ankur DAUNERIA
George Foti
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP4183223A1 publication Critical patent/EP4183223A1/fr
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data

Definitions

  • the present disclosure relates to wireless communication and in particular, to methods and apparatuses for vertical slice specific information.
  • the Global System for Mobile Communications Association is considering certain aspects for multiple subscriber identification module (multi-SIM) device services.
  • user contact lists are being considered for multi-SIM devices according to e.g., the following table, Table 1, and the GSMA has considered that reading and writing of contact details to and from each SIM may be in accordance with 3 rd Generation Partnership Project (3GPP).
  • 3GPP 3 rd Generation Partnership Project
  • 5G 5 th Generation
  • UE user equipment
  • a network slice may be considered a complete logical network and may include a Core Network (CN).
  • CN Core Network
  • Each slice may offer one or more network services and/or network capabilities.
  • Some embodiments advantageously provide methods and apparatuses for vertical slice specific information.
  • a method implemented in a user equipment, UE, configured to communicate with nodes in a network includes receiving network slice-specific information associated with a network slice identifier, the network slice-specific information being usable by the UE for a network slice indicated by the network slice identifier and the network slice- specific information being transparent to the nodes in the network.
  • the method further includes sending a registration request to register the UE with the network; and wherein receiving the network slice-specific information further comprises, as a result of the registration request, receiving a registration response message comprising allowed network slice selection assistance information, NSSAI, including the network slice-specific information for an allowed selected NSSAI, S-NSSAI, that is transparent to the nodes in the network.
  • NSSAI allowed network slice selection assistance information
  • the method further includes sending a protocol data unit, PDU, session establishment request comprising a selected network slice selection assistance information, NSSAI, S-NSSAI; and wherein receiving the network slice- specific information further comprises, as a result of the PDU session establishment request, receiving a PDU session establishment response comprising the network slice-specific information for the S-NSSAI that is transparent to the nodes in the network.
  • the method further includes storing the received network slice-specific information as associated with the network slice indicated by the network slice identifier; and using the network slice-specific information when the UE is connected to the network slice.
  • using the network slice- specific information further comprises displaying the network slice-specific information, the display indicating the network slice associated with the network slice- specific information and identified by the network slice identifier; and/or storing the received network slice- specific information further comprises storing the network slice-specific information per network slice identifier in at least one of a memory at the UE, at least one subscriber identification module, SIM, at the UE and a cloud application server associated with the UE.
  • the network slice- specific information includes a contacts list associated with the network slice identifier. In some embodiments of this aspect, the network slice-specific information includes at least one of UE configuration information and advertisement information each associated with the network slice identifier. In some embodiments of this aspect, the network is a 5 th Generation Core, 5GC, network. In some embodiments of this aspect, the network slice-specific information is provisioned on behalf of a network slice owner. In some embodiments of this aspect, the network slice identifier is a Single Network Slice Selection Assistance Information. In some embodiments of this aspect, the network slice-specific information is received in a transparent container associated with the Single Network Slice Selection Assistance Information.
  • the method further includes updating at least a part of the network slice- specific information associated with the network slice identifier; and sending an uplink Non-access Stratum, NAS, transport message including at least the updated part of the network slice-specific information.
  • information indicating whether the UE is able to update the network slice-specific information being included within the received network slice- specific information.
  • a method implemented in a network slice selection function, NSSF, node in a network includes receiving, from an access management function, AMF, node, a request to retrieve information related to at least one network slice; and as a result of the request, sending network slice- specific information to the AMF node, the network slice- specific information being associated with a network slice identifier and the network slice-specific information being transparent to nodes in the network.
  • the method further includes receiving, from an operations and management node, a request to store the network slice- specific information associated with the network slice identifier; and as a result of the request to store, storing the network slice- specific information associated with the network slice identifier at the NSSF node.
  • the method further includes, as a result of the request to retrieve, determining allowed network slice selection assistance information, NSSAI; and obtaining the network slice-specific information for at least one network slice indicated by the allowed NSSAI.
  • the method further includes receiving, from the AMF node, an update to at least a part of the network slice-specific information via an NSSF NSSAI Availability Update service operation; and updating and storing the at least the updated part of the network slice- specific information.
  • the network slice-specific information is provisioned on behalf of a network slice owner.
  • the network slice identifier is a Single Network Slice Selection Assistance Information.
  • the network slice-specific information is sent to the AMF node in a transparent container associated with the Single Network Slice Selection Assistance Information.
  • the request from the AMF node is received via a NSSF Network Slice Selection Get service operation.
  • the network slice- specific information includes at least one of: a contacts list associated with the network slice identifier; UE configuration information associated with the network slice identifier; and advertisement information associated with the network slice identifier.
  • the method includes receiving, from an access management function, AMF, node, a request to retrieve access and mobility subscription information for a user equipment, UE; and obtaining and sending the access and mobility subscription information for the UE, the access and mobility subscription information including allowed network slice selection assistance information, NSSAI comprising network slice- specific information, the network slice- specific information being associated with a network slice identifier and the network slice-specific information being transparent to nodes in the network.
  • the method further includes receiving, from an operations and management node, a request to store the network slice- specific information associated with the network slice identifier; and as a result of the request to store, storing the network slice- specific information associated with the network slice identifier at the UDM node.
  • obtaining the access and mobility subscription information for the UE includes determining the allowed network slice selection assistance information, NSSAI, for the UE; determining that there is network slice-specific information for at least one network slice indicated in the allowed NSSAI; and as a result of the determination, obtaining the network slice- specific information for the at least one network slice indicated in the allowed NSSAI.
  • the network slice-specific information is provisioned on behalf of a network slice owner.
  • the network slice identifier is a Single Network Slice Selection Assistance Information.
  • the network slice- specific information is sent to the AMF node in a transparent container associated with the Single Network Slice Selection Assistance Information.
  • the request from the AMF node is received via a Subscription Data Management, SDM, service operation.
  • the network slice-specific information includes at least one of: a contacts list associated with the network slice identifier; UE configuration information associated with the network slice identifier; and advertisement information associated with the network slice identifier.
  • a method implemented in a cloud application server, AS, node includes receiving, from a user equipment, UE, one of a contacts list and an update to the contacts list, the received one of the contacts list and the update to the contacts list being associated with a network slice identifier; and storing, for the UE, the one of the contacts list and the update to the contacts list as associated with a network slice indicated by the network slice identifier.
  • a user equipment configured to communicate with nodes in a network.
  • the UE includes processing circuitry.
  • the processing circuitry is configured to cause the UE to receive network slice- specific information associated with a network slice identifier, the network slice- specific information being usable by the UE for a network slice indicated by the network slice identifier and the network slice-specific information being transparent to the nodes in the network.
  • the processing circuitry is configured to cause the UE to send a registration request to register the UE with the network; and receive the network slice- specific information by being configured to cause the UE to, as a result of the registration request, receive a registration response message comprising allowed network slice selection assistance information, NSSAI, including the network slice-specific information for an allowed selected NSSAI, S-NSSAI, that is transparent to nodes in the network.
  • NSSAI allowed network slice selection assistance information
  • the processing circuitry is configured to cause the UE to send a protocol data unit, PDU, session establishment request comprising a selected network slice selection assistance information, NSSAI, S-NSSAI; and receive the network slice- specific information by being configured to cause the UE to, as a result of the PDU session establishment request, receive a PDU session establishment response comprising the network slice- specific information for the S-NSSAI that is transparent to nodes in the network.
  • the processing circuitry is configured to cause the UE to store the received network slice-specific information as associated with the network slice indicated by the network slice identifier; and use the network slice- specific information when the UE is connected to the network slice.
  • the processing circuitry is configured to cause the UE to use the network slice-specific information by being configured to cause the UE to display the network slice- specific information, the display indicating the network slice associated with the network slice- specific information and identified by the network slice identifier and/or store the received network slice-specific information by being configured to cause the UE to store the network slice-specific information per network slice identifier in a memory at the UE, at least one subscriber identification module, SIM, at the UE and a cloud application server associated with the UE.
  • the network slice- specific information includes a contacts list associated with the network slice identifier. In some embodiments of this aspect, the network slice-specific information includes at least one of UE configuration information and advertisement information each associated with the network slice identifier. In some embodiments of this aspect, the network is a 5 th Generation Core, 5GC, network. In some embodiments of this aspect, the network slice-specific information is provisioned on behalf of a network slice owner. In some embodiments of this aspect, the network slice identifier is a Single Network Slice Selection Assistance Information. In some embodiments of this aspect, the network slice-specific information is received in a transparent container associated with the Single Network Slice Selection Assistance Information.
  • the processing circuitry is configured to cause the UE to update at least a part of the network slice-specific information associated with the network slice identifier; and send an uplink Non-access Stratum, NAS, transport message including at least the updated part of the network slice-specific information.
  • NAS Non-access Stratum
  • information indicating whether the UE is able to update the network slice-specific information being included within the received network slice-specific information.
  • a network slice selection function, NSSF, node in a network includes processing circuitry.
  • the processing circuitry is configured to cause the NSSF node to receive, from an access management function, AMF, node, a request to retrieve information related to at least one network slice; and as a result of the request, send network slice- specific information to the AMF node, the network slice-specific information being associated with a network slice identifier and the network slice-specific information being transparent to nodes in the network.
  • the processing circuitry is configured to cause the NSSF node to receive, from an operations and management node, a request to store the network slice- specific information associated with the network slice identifier; and as a result of the request to store, store the network slice- specific information associated with the network slice identifier at the NSSF node.
  • the processing circuitry is configured to cause the NSSF node to as a result of the request to retrieve, determine allowed network slice selection assistance information, NSSAI; and obtain the network slice- specific information for at least one network slice indicated by the allowed NSSAI.
  • the processing circuitry is configured to cause the NSSF node to receive, from the AMF node, an update to at least a part of the network slice-specific information via an NSSF NSSAI Availability Update service operation; and update and store the at least the updated part of the network slice- specific information.
  • the network slice- specific information is provisioned on behalf of a network slice owner.
  • the network slice identifier is a Single Network Slice Selection Assistance Information.
  • the network slice- specific information is sent to the AMF node in a transparent container associated with the Single Network Slice Selection Assistance Information.
  • the request from the AMF node is received via a NSSF Network Slice Selection Get service operation.
  • the network slice-specific information includes at least one of: a contacts list associated with the network slice identifier; UE configuration information associated with the network slice identifier; and advertisement information associated with the network slice identifier.
  • a unified data management, UDM, node in a network includes processing circuitry.
  • the processing circuitry is configured to cause the UDM node to receive, from an access management function, AMF, node, a request to retrieve access and mobility subscription information for a user equipment, UE; and obtain and send the access and mobility subscription information for the UE, the access and mobility subscription information including allowed network slice selection assistance information, NSSAI comprising network slice-specific information, the network slice- specific information being associated with a network slice identifier and the network slice- specific information being transparent to nodes in the network.
  • the processing circuitry is further configured to cause the UDM node to receive, from an operations and management node, a request to store the network slice- specific information associated with the network slice identifier; and as a result of the request to store, store the network slice- specific information associated with the network slice identifier at the UDM node.
  • the processing circuitry is configured to cause the UDM node to obtain the access and mobility subscription information for the UE by being configured to cause the UDM node to determine the allowed network slice selection assistance information, NSSAI, for the UE; determine that there is network slice- specific information for at least one network slice indicated in the allowed NSSAI; and as a result of the determination, obtain the network slice-specific information for the at least one network slice indicated in the allowed NSSAI.
  • NSSAI allowed network slice selection assistance information
  • the network slice- specific information is provisioned on behalf of a network slice owner.
  • the network slice identifier is a Single Network Slice Selection Assistance Information.
  • the network slice-specific information is sent to the AMF node in a transparent container associated with the Single Network Slice Selection Assistance Information; and the request from the AMF node is received via a Subscription Data Management, SDM, service operation.
  • the network slice- specific information includes at least one of: a contacts list associated with the network slice identifier; UE configuration information associated with the network slice identifier; and advertisement information associated with the network slice identifier.
  • a cloud application server (AS) node comprising processing circuitry.
  • the processing circuitry is configured to cause the cloud AS node to receive, from a user equipment, UE, one of a contacts list and an update to the contacts list, the received one of the contacts list and the update to the contacts list being associated with a network slice identifier; and store, for the UE, the one of the contacts list and the update to the contacts list as associated with a network slice indicated by the network slice identifier.
  • FIG. 1 illustrates an example verticals that may define the slice specific information proposed in the present disclosure
  • FIG. 2 illustrates an example of robot technology that may use the slice specific information proposed in the present disclosure
  • FIG. 3 illustrates an example system architecture according to some embodiments of the present disclosure
  • FIG. 4 illustrates yet another example system architecture and example hardware arrangements for devices in the system, according to some embodiments of the present disclosure
  • FIG. 5 is a flowchart of an example process in a user equipment according to some embodiments of the present disclosure
  • FIG. 6 is a flowchart of an example process in a NSSF node according to some embodiments of the present disclosure
  • FIG. 7 is a flowchart of an example process in a UDM node according to some embodiments of the present disclosure.
  • FIG. 8 is a flowchart of an example process in an AS node according to some embodiments of the present disclosure.
  • FIGS. 9 is a call flow diagram for an example process of providing slice specific information via a NSSF node as a result of a registration request according to some embodiments of the present disclosure
  • FIG. 10 is a call flow diagram for an example process of updating the slice specific information according to some embodiments of the present disclosure
  • FIG. 11 is a call flow diagram for an example process of providing slice specific information via a UDM node as a result of a registration request according to some embodiments of the present disclosure
  • FIG. 12 is a call flow diagram for an example process of updating the slice specific information according to some embodiments of the present disclosure.
  • FIG. 13 is a call flow diagram for an example of providing slice specific information via a NSSF node as a result of a PDU session establishment request according to some embodiments of the present disclosure.
  • FIG. 14 is a call flow diagram for an example process of providing slice specific information via a UDM node as a result of a PDU session establishment request according to some embodiments of the present disclosure.
  • SIMs with multiple slices and services may be offered.
  • a contact list may be part of a device (e.g., UE), the cloud, a SIM, such as, SIMx, SIMy.
  • a contact list may be available at a cloud server, which may be accessible via a data service which may be part of a slice out of multiple slices.
  • gaps may include one or more of the following:
  • menu structure at the UE may display the contact list from the slice (having the cloud server).
  • slice details may be included in contact lists;
  • the user may be asked for a cloud location which in itself may be part of one of many sets of slices; thus, the user may be asked to select the slice(s) out of many slices; • an option to delete a contact from a cloud location available in a slice or multiple slices having the cloud servers for the contact list; the user may be asked to select such slice(s) when the user/UE determines to delete a contact from a slice or multiple slices; and/or
  • corporate slices may include corporate contact lists from e.g., a corporate server, such that when a corporation is assigned to a UE (either at a corporate location, or during the office hours) employees may be provided access to a full corporate contact list as part of an assigned new slice to the employee’s UE.
  • a storage server e.g., contact list
  • a storage server e.g., contact list
  • assigning such corporate slice to active employees in a limited manner e.g., during the office hours, or at the office location, etc.
  • a corporate slice is assigned to such employee’s UE and access to the full corporate contact list is available to the employee’s UE as long as the slice is assigned to the UE.
  • this slice may be unassigned from the employee’s UE and access to the full corporate contact list is no longer available.
  • a business slice may be assigned to a user’s UE as the user enters the specific mall perimeter/location, which may prompt slice- specific information, such as, for example, a contact list specific to mall services, mall emergency numbers, helplines, individual shops inside the mall, etc. to become available to the user’s UE.
  • the contact list may be managed by a storage server in a (business- specific) slice which is assigned to the UE as the UE enters the mall and may be unassigned as the UE leaves the area. Once the UE leaves, the slice may be unassigned to the UE and the mall/slice-specific information may become unavailable to the UE.
  • tourist tour operators may purchase a slice for its customers that is specific to a tour.
  • Such slice may offer communication services along with a contacts list (e.g., including tour operators, location-based emergency phone numbers, location-based hotel information, allotted bus driver phone number, tour manager phone number, etc.).
  • the contacts list may be specific to a tour operator that purchased the slice and may be made available to all users/UEs that are part of the tour, as part of the slice which is assigned to all members of a planned tour. Once the tour is over, the slice may be unassigned to those UEs and the tour/slice- specific contacts list becomes unavailable to those UEs.
  • some embodiments of the present disclosure may be used in the robotics industry.
  • Robots generally involves several levels of control and processing, involving on-board hardware and software, and increasingly also involving cloud processing and pooling knowledge from multiple robots to learn from that knowledge. Robots may also be able to sense their surroundings. Depending on the applications, robots may include sensors that are sensitive to touch, heat, light, vibration, and sound, or even certain chemicals.
  • the core segment in robot value chains are illustrated in FIG. 2.
  • a network operator or third party may want to add configuration information with respect to robots. That is, limiting specific configuration information with respect to specific network slice and robot. As slice is assigned by business to a robot (as per industry), configuration information is available to robot (UE) as per the UE interpretation. Once slice is unassigned, robotic configuration information become inaccessible to robot.
  • a network operator, third-parties and/or business partners may be able to limit specific advertisements to specific slices using the arrangements in the present disclosure. For example, as a specific slice is assigned to a subscriber UE by e.g., a business, the UE may interpret the advertisement information received as part of a specific slice assignment; thus, limiting specific advertisements to a specific slice.
  • slice-specific information may include one or more of the following, which may be available to a UE as per the UE’s interpretation of its assignment of a specific slice, e.g., by businesses (industries):
  • slice-specific information that is made available (via a slice) to certain UEs as e.g., a customer visits a location, or during office hours, or as part of a team/department at a particular location/time (e.g., school, college, office, malls, airport/railway stations, etc.).
  • slice-specific information e.g., contact list
  • a slice may provide select communication services as per a business’s policy depending on the respective business’s UE(s).
  • slice-specific information may be made available to customers’ UEs as the slice is assigned to the UEs based on one or more criteria. The customer may be able to contact businesses as per the allowed communication services offered by the slice.
  • slice- specific information becomes accessible to the UE.
  • Techniques existing today such as short message service (SMS) advertisements, information desk, pamphlets, emails, etc. which businesses use to provide information to their (potential) customers are antiquated and require effort by customers to delete the information from their UE when no longer useful.
  • SMS short message service
  • some embodiments of the present disclosure provide for a seamless and context specific arrangement in which a UE is assigned a slice by businesses.
  • Contact information e.g., a mobile number
  • a subscriber which may be considered a subscriber’s identity
  • SMS advertisements e.g., SMS advertisements, information desks, pamphlets, emails, etc.
  • this may cut into potential revenues as the mechanism for information dissemination is distributed among various other players.
  • Example 5G Industries and Verticals for Network Slicing Use Cases Different industries that are expected to use 5G include agriculture, energy and utilities, manufacturing, public safety, healthcare, public transport, media and entertainment, automotive, financial services, and retail. Also, the GSMA network slicing use cases requirements have considered some of the verticals illustrated in FIG. 1 during its use case collections.
  • B2C to provide consumers differentiated experiences, such as guaranteed data speed or less lag time, and consumers pay for the service.
  • B2B2C operator cooperates with partners, e.g. mobile gaming provider, to provide a consumer service that bundles the benefits of a specific service from a “middle B” partner with aspects of 5G slicing Service Level Agreements (SLAs) such as latency or security to provide better end-user experience.
  • partners e.g. mobile gaming provider
  • SLAs Service Level Agreements
  • the partner may sponsor the service, and the operator monetizes some metric of the SLA provided to the partner to improve its services to its consumer customers.
  • B2B operator offers services directly to businesses with SLAs structured around different parameters depending on the use case.
  • B2B2B network slice to be integrated into the partner’s solution and sold to enterprise customers.
  • the “middle B” vertical-centric service providers
  • operators can solve the fragmentation challenge of addressing many distinct industries. Considering these facts, businesses making a transition into network slicing use cases for its customers, may be benefitted by some embodiments of the present disclosure. Operators may be able to monetize the capabilities provided in some embodiments in different business models.
  • Single-network slice selection assistance information (S-NSSAI) specific contact lists may offer new business opportunities to network operators, to monetize new scenarios arising in the 5G ecosystem. Limiting a contact list to a slice may allow businesses to customize the end-user experience. Operators may be able to monetize these customized availability of business- specific contacts as per slice.
  • S-NSSAI single-network slice selection assistance information
  • Some embodiments may be widely applicable. Each day countless users travel to offices, shopping centers, airports, railway stations, etc., and limiting specific information availability (e.g., contacts) to a UE as a slice is assigned to the UE in different use cases/criteria may offer a great value to operators, businesses and/or improved the user’s experience.
  • contacts lists represent one aspect that is slice- specific information
  • some embodiments of the present disclosure may be extended to support provision of any transparent, slice specific information that is relevant for the industry and the UE.
  • Non-limiting examples may include policies, configuration specific information, which may be dependent on a device model, policies related to the device operation for a robot, etc.
  • the joining term, “in communication with” and the like may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example.
  • electrical or data communication may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example.
  • the term “coupled,” “connected,” and the like may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.
  • the phrase “communicate with” and the like may be used herein to indicate a communication, although not necessarily a direct communication.
  • communication of a UE with nodes of a network such as a 5G core network, may be via a common core network function, such as, an access and mobility function (AMF) node.
  • AMF access and mobility function
  • the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably.
  • the UE herein can be any type of wireless device capable of communicating with a network node or another UE over radio signals.
  • the UE may be an autonomous machine configured to communicate via IMS.
  • the UE herein can by any type of communication device capable of communicating with another UE, an application server, a network node, a server, an IMS NF or other IMS network node, via a wired connection and/or a wireless connection.
  • the UE may also be a radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), low-cost and/or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (IoT) device, or a Narrowband IoT (NB-IOT) device etc.
  • D2D device to device
  • M2M machine to machine communication
  • M2M machine to machine communication
  • Tablet mobile terminals
  • smart phone laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles
  • CPE Customer Premises Equipment
  • IoT Internet of Things
  • NB-IOT Narrowband IoT
  • the term “node” is used herein and can be any kind of node, such as, an Access and Mobility Function (AMF) node, a session management node (e.g., session management function (SMF) node), or an application server (AS) node (e.g., device cloud storage node).
  • the node may be a core network node of, e.g., a Third Generation Partnership Project (3GPP) Fifth Generation (5G) and/or New Radio (NR) core network, such as, an AMF node, SMF node, NSSF node, UDM node and/or OAM node.
  • 3GPP Third Generation Partnership Project
  • 5G Fifth Generation
  • NR New Radio
  • a node may include physical components, such as processors, allocated processing elements, or other computing hardware, computer memory, communication interfaces, and other supporting computing hardware.
  • the node may use dedicated physical components, or the node may be allocated use of the physical components of another device, such as a computing device or resources of a datacenter, in which case the node is said to be virtualized.
  • a node may be associated with multiple physical components that may be located either in one location, or may be distributed across multiple locations.
  • PDU session establishment request may also encompass a PDU session modification request in addition to a PDU session establishment request.
  • the phrase “network slice owner” may also encompass a network slice lessee in addition to a network slice owner.
  • the network slice owner/lessee may be one or more of the verticals discussed herein that may provision the network slice- specific information or on whose behalf the network slice-specific information may be provisioned.
  • the S-NSSAI may be considered selected network slice selection assistance information and/or single network slice selection assistance information.
  • wireless systems such as, for example, 3 rd Generation Partnership Project (3GPP), Long Term Evolution (LTE), 5 th Generation (5G) and/or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system.
  • 3GPP 3 rd Generation Partnership Project
  • LTE Long Term Evolution
  • 5G 5 th Generation
  • NR New Radio
  • WCDMA Wide Band Code Division Multiple Access
  • WiMax Worldwide Interoperability for Microwave Access
  • UMB Ultra Mobile Broadband
  • GSM Global System for Mobile Communications
  • functions described herein as being performed by a UE or any of the nodes discussed herein may be distributed over a plurality of UEs and/or a plurality of nodes.
  • the functions of the UE, AMF node, SMF node, NSSF node, UDM node, AS node, OAM node and node described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.
  • FIG. 3 a schematic diagram of an example communication system 10 constructed in accordance with the principles of the present disclosure.
  • the communication system 10 in FIG. 3 is a non-limiting example and other embodiments of the present disclosure may be implemented by one or more other systems and/or networks.
  • system 10 includes a UE 12, in addition to various support elements for supporting communications with the UE 12, such as, a radio access network (RAN) 14 (e.g., 5G or NR RAN, gNB, eNB, base station, etc.).
  • RAN radio access network
  • the system may further include an AMF node 16, an SMF node 18, an NSSF node 20, a UDM node 22, AS node 24 and OAM node 26.
  • the AMF node 16 may provide access and mobility management for the UE 12.
  • the SMF node 18 may provide session management for the user plane.
  • the NSSF node 20 may assist with selecting network slice instances to serve the UE 12.
  • the UDM node 22 may provide a database of subscriber information.
  • the AS node 24 may provide, for example, cloud storage services to the UE 12.
  • the OAM node 26 may provide operations, administration, and maintenances services to the system 10.
  • the system 10 may include a core network (e.g., 5G Core), which may include the AMF node 16, the SMF node 18, the NSSF node 20, the UDM node 22 and the OAM node 26, as well as other core network nodes.
  • 5G Core 5G Core
  • the UE 12 may include a slice specific information (SSI) using unit 28 which may be configured to receive network slice- specific information associated with a network slice identifier, the network slice-specific information being usable by the UE 12 for a network slice indicated by the network slice identifier and the network slice- specific information being transparent to the nodes in the network.
  • SSI slice specific information
  • the NSSF node 20 may include a slice specific information (SSI) retrieving unit 30 which may be configured to receive, from an access management function, AMF, node, a request to retrieve information related to at least one network slice; and as a result of the request, send network slice- specific information to the AMF node, the network slice-specific information being associated with a network slice identifier and the network slice-specific information being transparent to nodes in the network.
  • SSI slice specific information
  • the UDM node 22 may include a slice specific information (SSI) obtaining unit 32 which may be configured to receive, from an access management function, AMF, node, a request to retrieve access and mobility subscription information for a user equipment, UE; and obtain and send the access and mobility subscription information for the UE, the access and mobility subscription information including allowed network slice selection assistance information, NSSAI comprising network slice- specific information, the network slice-specific information being associated with a network slice identifier and the network slice-specific information being transparent to nodes in the network.
  • SSI slice specific information
  • the AS node 24 may include a slice specific information (SSI) storage unit 34 which may be configured to receive, from a user equipment, UE, one of a contacts list and an update to the contacts list, the received one of the contacts list and the update to the contacts list being associated with a network slice identifier; and store, for the UE, the one of the contacts list and the update to the contacts list as associated with a network slice indicated by the network slice identifier.
  • SSI slice specific information
  • Example implementations, in accordance with an embodiment, of the UE 12, NSSF node 20, UDM node 22 and a node 36 (e.g., AS node 24, AMF node 16, SMF node 18, OAM node 26) discussed in the preceding paragraphs will now be described with reference to FIG. 4.
  • a node 36 e.g., AS node 24, AMF node 16, SMF node 18, OAM node 26
  • the UE 12 includes a communication interface 38, processing circuitry 40, and memory 42.
  • the communication interface 38 may be configured to communicate with one or more of the other elements in the system 10 according to the techniques in the present disclosure.
  • the communication interface 38 may be formed as or may include, for example, one or more radio frequency (RF) transmitters, one or more RF receivers, and/or one or more RF transceivers, and/or may be considered a radio interface.
  • the communication interface 38 may also include a wired interface.
  • the processing circuitry 40 may include one or more processors 44 and memory, such as, the memory 42.
  • the processing circuitry 40 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • processors 44 and memory such as, the memory 42.
  • the processing circuitry 40 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • FPGAs Field Programmable Gate Array
  • ASICs Application Specific Integrated Circuitry
  • the processor 44 may be configured to access (e.g., write to and/or read from) the memory 42, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • volatile and/or nonvolatile memory e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the UE 12 may further include software stored internally in, for example, memory 42, or stored in external memory (e.g., database) accessible by the UE 12 via an external connection.
  • the software may be executable by the processing circuitry 40.
  • the processing circuitry 40 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by the UE 12.
  • the memory 42 is configured to store data, programmatic software code and/or other information described herein.
  • the software may include instructions stored in memory 42 that, when executed by the processor 44 and/or SSI Using Unit 28, causes the processing circuitry 40 and/or configures the UE 12 to perform the processes described herein with respect to the UE 12 (e.g., processes described with reference to FIG. 5 and/or any of the other figures).
  • the NSSF node 20 includes a communication interface 46, processing circuitry 48, and memory 50.
  • the communication interface 46 may be configured to communicate with one or more of the other elements in the system 10 according to the techniques in the present disclosure.
  • the communication interface 46 may be formed as or may include, for example, one or more radio frequency (RF) transmitters, one or more RF receivers, and/or one or more RF transceivers, and/or may be considered a radio interface.
  • RF radio frequency
  • the communication interface 46 may also include a wired interface.
  • the processing circuitry 48 may include one or more processors 52 and memory, such as, the memory 50.
  • the processing circuitry 48 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • processors and/or processor cores and/or FPGAs Field Programmable Gate Array
  • ASICs Application Specific Integrated Circuitry
  • the processor 52 may be configured to access (e.g., write to and/or read from) the memory 50, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • volatile and/or nonvolatile memory e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the NSSF node 20 may further include software stored internally in, for example, memory 50, or stored in external memory (e.g., database) accessible by the NSSF node 20 via an external connection.
  • the software may be executable by the processing circuitry 48.
  • the processing circuitry 48 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by the NSSF node 20.
  • the memory 50 is configured to store data, programmatic software code and/or other information described herein.
  • the software may include instructions stored in memory 50 that, when executed by the processor 52 and/or SSI retrieving unit 30, causes the processing circuitry 48 and/or configures the NSSF node 20 to perform the processes described herein with respect to the NSSF node 20 (e.g., processes described with reference to FIG. 6 and/or any of the other figures).
  • the UDM node 22 includes a communication interface 54, processing circuitry 56, and memory 58.
  • the communication interface 54 may be configured to communicate with one or more of the other elements in the system 10 according to the techniques in the present disclosure.
  • the communication interface 54 may be formed as or may include, for example, one or more radio frequency (RF) transmitters, one or more RF receivers, and/or one or more RF transceivers, and/or may be considered a radio interface.
  • RF radio frequency
  • the communication interface 54 may also include a wired interface.
  • the processing circuitry 56 may include one or more processors 60 and memory, such as, the memory 58.
  • the processing circuitry 56 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • processors and/or processor cores and/or FPGAs Field Programmable Gate Array
  • ASICs Application Specific Integrated Circuitry
  • the processor 60 may be configured to access (e.g., write to and/or read from) the memory 58, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the memory 58 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the UDM node 22 may further include software stored internally in, for example, memory 58, or stored in external memory (e.g., database) accessible by the UDM node 22 via an external connection.
  • the software may be executable by the processing circuitry 56.
  • the processing circuitry 56 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by the UDM node 22.
  • the memory 58 is configured to store data, programmatic software code and/or other information described herein.
  • the software may include instructions stored in memory 58 that, when executed by the processor 60 and/or SSI obtaining unit 32, causes the processing circuitry 56 and/or configures the UDM node 22 to perform the processes described herein with respect to the UDM node 22 (e.g., processes described with reference to FIG. 7 and/or any of the other figures).
  • the node 36 (e.g., AS node, AMF node, SMF node, OAM node) includes a communication interface 62, processing circuitry 64, and memory 66.
  • the communication interface 62 may be configured to communicate with one or more of the other elements in the system 10 according to the techniques in the present disclosure.
  • the communication interface 62 may be formed as or may include, for example, one or more radio frequency (RF) transmitters, one or more RF receivers, and/or one or more RF transceivers, and/or may be considered a radio interface.
  • the communication interface 62 may also include a wired interface.
  • the processing circuitry 64 may include one or more processors 68 and memory, such as, the memory 66.
  • the processing circuitry 64 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • FPGAs Field Programmable Gate Array
  • ASICs Application Specific Integrated Circuitry
  • the processor 68 may be configured to access (e.g., write to and/or read from) the memory 66, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • volatile and/or nonvolatile memory e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the node 36 may further include software stored internally in, for example, memory 66, or stored in external memory (e.g., database) accessible by the node 36 via an external connection.
  • the software may be executable by the processing circuitry 64.
  • the processing circuitry 64 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by the node 36.
  • the memory 66 is configured to store data, programmatic software code and/or other information described herein.
  • the software may include instructions stored in memory 66 that, when executed by the processor 68 and/or SSI storage unit 34, causes the processing circuitry 64 and/or configures the node 36 to perform the processes described herein with respect to the node 36, such as the AS node (e.g., processes described with reference to FIG. 8 and/or any of the other figures).
  • FIG. 4 the connections between the devices such as UE 12, NSSF node 20, UDM node 22 and node 36 are shown without explicit reference to any intermediary devices or connections. However, it should be understood that intermediary devices and/or connections may exist between these devices, although not explicitly shown. Also, although the UE 12, NSSF node 20, UDM node 22 and node 36 are shown connected in serial fashion, it is understood that such depiction is for ease of explanation and that the UE 12, NSSF node 20, UDM node 22 and node 36 may each be connected to a network, e.g., cloud network, to facilitate communication between the any of the elements shown in FIG. 4.
  • a network e.g., cloud network
  • FIG. 4 shows SSI using unit 28, SSI retrieving unit 30, SSI obtaining unit 32 and SSI storage unit 34, as being within a respective processor, it is contemplated that these elements may be implemented such that a portion of the elements is stored in a corresponding memory within the processing circuitry. In other words, the elements may be implemented in hardware or in a combination of hardware and software within the processing circuitry.
  • FIG. 5 is a flowchart of an example process in a UE 12 according to some embodiments of the present disclosure.
  • One or more Blocks and/or functions and/or methods performed by the UE 12 may be performed by one or more elements of UE 12 such as by SSI using unit 28 in processing circuitry 40, memory 42, processor 44 and/or communication interface 38 according to the example process/method.
  • the example process includes receiving (Block S100), such as via SSI using unit 28, processing circuitry 40, memory 42, processor 44 and/or communication interface 38, network slice-specific information associated with a network slice identifier, the network slice-specific information being usable by the UE 12 for a network slice indicated by the network slice identifier and the network slice-specific information being transparent to the nodes in the network.
  • the method further includes sending, such as via SSI using unit 28, processing circuitry 40, memory 42, processor 44 and/or communication interface 38, a registration request to register the UE with the network; and wherein receiving the network slice- specific information further comprises, as a result of the registration request, receiving a registration response message comprising allowed network slice selection assistance information, NSSAI, including the network slice- specific information that is transparent to the nodes in the network.
  • sending such as via SSI using unit 28, processing circuitry 40, memory 42, processor 44 and/or communication interface 38
  • receiving the network slice- specific information further comprises, as a result of the registration request, receiving a registration response message comprising allowed network slice selection assistance information, NSSAI, including the network slice- specific information that is transparent to the nodes in the network.
  • the method further includes sending, such as via SSI using unit 28, processing circuitry 40, memory 42, processor 44 and/or communication interface 38, a protocol data unit, PDU, session establishment request; and wherein receiving the network slice-specific information further comprises, as a result of the PDU session establishment request, receiving a PDU session establishment response comprising the network slice- specific information that is transparent to the nodes in the network.
  • the method further includes storing, such as via SSI using unit 28, processing circuitry 40, memory 42, processor 44 and/or communication interface 38, the received network slice- specific information as associated with the network slice indicated by the network slice identifier; and using, such as via SSI using unit 28, processing circuitry 40, memory 42, processor 44 and/or communication interface 38, the network slice- specific information when the UE 12 is connected to the network slice.
  • using the network slice- specific information further comprises displaying, such as via SSI using unit 28, processing circuitry 40, memory 42, processor 44 and/or communication interface 38, the network slice-specific information, the display indicating the network slice associated with the network slice- specific information and identified by the network slice identifier; and/or storing the received network slice- specific information further comprises storing, such as via SSI using unit 28, processing circuitry 40, memory 42, processor 44 and/or communication interface 38, the network slice-specific information per network slice identifier in at least one of a memory (e.g., memory 42) at the UE 12, at least one subscriber identification module, SIM, at the UE 12 and a cloud application server associated with the UE 12.
  • a memory e.g., memory 42
  • the network slice-specific information includes a contacts list associated with the network slice identifier. In some embodiments, the network slice-specific information includes at least one of UE configuration information and advertisement information each associated with the network slice identifier. In some embodiments, the network is a 5 th Generation Core, 5GC, network. In some embodiments, the network slice- specific information is transparent to the 5GC. In some embodiments, the network slice is a core network slice. In some embodiments, the network slice-specific information is provisioned on behalf of a network slice owner/lessee. In some embodiments, the network slice identifier is a Single Network Slice Selection Assistance Information.
  • the Single Network Slice Selection Assistance Information may include a slice/service type and/or a slice differentiator and may be used to uniquely identify a network slice.
  • the network slice-specific information is received in a transparent container associated with the S-NSSAI.
  • the method further includes updating, such as via SSI using unit 28, processing circuitry 40, memory 42, processor 44 and/or communication interface 38, at least a part of the network slice-specific information associated with the network slice identifier; and sending, such as via SSI using unit 28, processing circuitry 40, memory 42, processor 44 and/or communication interface 38, an uplink Non-access Stratum, NAS, transport message including at least the updated part of the network slice- specific information.
  • information indicating whether the UE is able to update the network slice-specific information being included within the received network slice-specific information.
  • FIG. 6 is a flowchart of an example process in a NSSF node 20 according to some embodiments of the present disclosure.
  • One or more Blocks and/or functions and/or methods performed by the NSSF node 20 may be performed by one or more elements of NSSF node 20 such as by SSI retrieving unit 30 in processing circuitry 48, memory 50, processor 52 and/or communication interface 46 according to the example process/method.
  • the example process includes receiving (Block S102), such as via SSI retrieving unit 30, processing circuitry 48, memory 50, processor 52 and/or communication interface 46, from an access management function, AMF, node, a request to retrieve information related to at least one network slice.
  • the process includes, as a result of the request, sending (Block S104), such as via SSI retrieving unit 30, processing circuitry 48, memory 50, processor 52 and/or communication interface 46, network slice-specific information to the AMF node, the network slice- specific information being associated with a network slice identifier and the network slice- specific information being transparent to nodes in the network.
  • the method includes receiving, such as via SSI retrieving unit 30, processing circuitry 48, memory 50, processor 52 and/or communication interface 46, from an operations and management node, a request to store the network slice-specific information associated with the network slice identifier; and as a result of the request to store, storing, such as via SSI retrieving unit 30, processing circuitry 48, memory 50, processor 52 and/or communication interface 46, the network slice-specific information associated with the network slice identifier at the NSSF node 20.
  • the method further includes, as a result of the request to retrieve, determining, such as via SSI retrieving unit 30, processing circuitry 48, memory 50, processor 52 and/or communication interface 46, allowed network slice selection assistance information, NSSAI; and obtaining, such as via SSI retrieving unit 30, processing circuitry 48, memory 50, processor 52 and/or communication interface 46, the network slice-specific information for at least one network slice indicated by the allowed NSSAI.
  • the method further includes receiving, such as via SSI retrieving unit 30, processing circuitry 48, memory 50, processor 52 and/or communication interface 46, from the AMF node, an update to at least a part of the network slice-specific information via an NSSF NSSAI Availability Update service operation; and updating and storing, such as via SSI retrieving unit 30, processing circuitry 48, memory 50, processor 52 and/or communication interface 46, the at least the updated part of the network slice-specific information.
  • the network slice-specific information is provisioned on behalf of a network slice owner/lessee.
  • the network slice identifier is a Single Network Slice Selection Assistance Information.
  • the Single Network Slice Selection Assistance Information may include a slice/service type and/or a slice differentiator and may be used to uniquely identify a network slice.
  • the network slice-specific information is sent to the AMF node in a transparent container associated with the Single Network Slice Selection Assistance Information.
  • the request from the AMF node is received via a NSSF Network Slice Selection Get service operation.
  • the network slice-specific information includes at least one of: a contacts list associated with the network slice identifier; UE configuration information associated with the network slice identifier; and advertisement information associated with the network slice identifier.
  • FIG. 7 is a flowchart of an example process in a UDM node 22 according to some embodiments of the present disclosure.
  • One or more Blocks and/or functions and/or methods performed by the UDM node 22 may be performed by one or more elements of UDM node 22 such as by SSI obtaining unit 32 in processing circuitry 56, memory 58, processor 60 and/or communication interface 54 according to the example process/method.
  • the example process includes receiving (Block S106), such as via SSI obtaining unit 32, processing circuitry 56, memory 58, processor 60 and/or communication interface 54, from an access management function, AMF, node, a request to retrieve access and mobility subscription information for a user equipment, UE.
  • AMF access management function
  • the method includes obtaining and sending (Block S108), such as via SSI obtaining unit 32, processing circuitry 56, memory 58, processor 60 and/or communication interface 54, the access and mobility subscription information for the UE, the access and mobility subscription information including allowed network slice selection assistance information, NSSAI comprising network slice-specific information, the network slice- specific information being associated with a network slice identifier and the network slice-specific information being transparent to nodes in the network.
  • Block S108 such as via SSI obtaining unit 32, processing circuitry 56, memory 58, processor 60 and/or communication interface 54, the access and mobility subscription information for the UE, the access and mobility subscription information including allowed network slice selection assistance information, NSSAI comprising network slice-specific information, the network slice- specific information being associated with a network slice identifier and the network slice-specific information being transparent to nodes in the network.
  • the method further includes receiving, such as via SSI obtaining unit 32, processing circuitry 56, memory 58, processor 60 and/or communication interface 54, from an operations and management node, a request to store the network slice-specific information associated with the network slice identifier; and as a result of the request to store, storing, such as via SSI obtaining unit 32, processing circuitry 56, memory 58, processor 60 and/or communication interface 54, the network slice-specific information associated with the network slice identifier at the UDM node 22.
  • obtaining the access and mobility subscription information for the UE comprises determining, such as via SSI obtaining unit 32, processing circuitry 56, memory 58, processor 60 and/or communication interface 54, the allowed network slice selection assistance information, NSSAI, for the UE; determining, such as via SSI obtaining unit 32, processing circuitry 56, memory 58, processor 60 and/or communication interface 54, that there is network slice- specific information for at least one network slice indicated in the allowed NSSAI; and as a result of the determination, obtaining, such as via SSI obtaining unit 32, processing circuitry 56, memory 58, processor 60 and/or communication interface 54, the network slice-specific information for the at least one network slice indicated in the allowed NSSAI.
  • the network slice-specific information is provisioned on behalf of a network slice owner.
  • the network slice identifier is a Single Network Slice Selection Assistance Information.
  • the network slice-specific information is sent to the AMF node in a transparent container associated with the Single Network Slice Selection Assistance Information.
  • the request from the AMF node is received via a Subscription Data Management, SDM, service operation.
  • the network slice-specific information includes at least one of: a contacts list associated with the network slice identifier; UE configuration information associated with the network slice identifier; and advertisement information associated with the network slice identifier.
  • FIG. 8 is a flowchart of an example process in a node 36 according to some embodiments of the present disclosure.
  • One or more Blocks and/or functions and/or methods performed by the node 36 may be performed by one or more elements of node 36 such as by SSI storage unit 34 in processing circuitry 64, memory 66, processor 68 and/or communication interface 62 according to the example process/method.
  • the example process includes receiving (Block SI 10), such as via SSI storage unit 34, processing circuitry 64, memory 66, processor 68 and/or communication interface 62, from a user equipment, UE, 12 one of a contacts list and an update to the contacts list, the received one of the contacts list and the update to the contacts list being associated with a network slice identifier.
  • the process includes storing (Block SI 12), for the UE 12, such as via SSI storage unit 34, processing circuitry 64, memory 66, processor 68 and/or communication interface 62, the one of the contacts list and the update to the contacts list as associated with a network slice indicated by the network slice identifier.
  • FIGS. 9-14 Having generally described arrangements for vertical slice specific information, a more detailed description of some of the embodiments are provided as follows with reference to FIGS. 9-14, and which may be implemented by one or more of RAN 14, AMF node 16, SMF node 18, NSSF node 20, UDM node 22, AS node 24, OAM node 26, node 36.
  • a new parameter is proposed to be included to the Network Slice Type (NEST) document in NG.116, which may include an Single Network Slice Selection Assistance Information information container that may include, for example, the contacts list, among other information, specific to a network slice identified by the Single Network Slice Selection Assistance Information.
  • the parameter may be called e.g., Single Network Slice Selection Assistance Information container specific information or network slice- specific information. It may be called by other names, as well.
  • this parameter is transparent to the network, e.g., 5GC.
  • the parameter may be merely stored and transported by the network (e.g., for the slice owner/lessee provisioning the information) to the UE 12 during e.g., 5GC registration and/or PDU session establishment but not actually used by the 5GC.
  • the network slice-specific container may include any information relevant to the UE 12 and is basically a transparent container, fetched during e.g., 5GC registration and/or PDU session establishment and transported to the UE 12.
  • the contacts list may be used merely to facilitate the description of some embodiments; however, the examples are not limited to contacts lists but can include any slice-specific information provisioned by the network slice owner (vertical), such as for example advertisement information specific to a network slice/vertical, UE/robot configuration information specific to a network slice/vertical, other types of business information specific to a network slice/vertical, etc.
  • the term “contacts list” may be replaced with the more general term slice-specific information.
  • the network slice owner may allow or optionally may not allow an update to the contacts list by any UE 12, or any other S-NSSAEslice- specific information through additional parameters associated with the contact list attribute.
  • the UE 12 is configured to display to the end user the contacts list per S-NSSAI per SIM. This may be particularly pertinent in a single radio UE 12 with dual-SIM cases and the S-NSSAI/slice container specific information (e.g., contact list) will be applicable to the registering SIM. For other types of information included in the container to be transported, it may simply be used by the UE 12 for its operation. The nature of the slice-specific information is only known to the UE 12 given that it belongs to the vertical industry.
  • the present disclosure describes at least two embodiments that may be supported for transporting S-NSSAEslice-specific information contained in the transparent container to the UE 12; one using the NSSF node 20, and the other using the UDM node 22 for managing the slice-specific information per S-NSSAI.
  • the AMF node 16 in cooperation with the NSSF node 20, provides the UE 12 with the slice-specific information including in this example the contacts list per allowed S-NSSAI only at initial 5GC registration and/or during PDU session establishment. This does not prevent using other existing procedures to push updates, through forced de-registration and re-registration.
  • the NSSF node 20 may be updated when the UE 12 modifies the slice-specific information including the S-NSSAI contacts list.
  • the UE 12 may initiate an uplink (UL) Non- access Stratum (NAS) transport message having a new payload container type Information Element (IE) to convey the S-NSSAEslice-specific information including in this example the contacts list to the AMF node 16.
  • NAS Non- access Stratum
  • IE payload container type Information Element
  • the AMF node 16 uses existing NSSF operations (e.g., Nnssf_NSSAIAvailability_Update service operation) that may be modified to support new inputs to update the NSSF node 20 with the modified contacts list.
  • a new NSSF operation could optionally be used instead.
  • network updates/modifications to the contacts list may be conveyed to the UE 12 only at the next initial 5GC registration and/or PDU session establishment.
  • the device cloud environment may store the slice-specific information including in this example the contacts list per S-NSSAI.
  • FIG. 9 is a call flow diagram that illustrates an example of the NSSF embodiment:
  • step S 114 the OAM node 26 is pre-provisioned with the slice-specific information container attribute including the contacts list for the target network slice in accordance with e.g., the GSMA NEST and NG.116.
  • the OAM node 26 is local to the operator.
  • step S 116 the OAM node 26 then issues a request to the NSSF node 20 to store the slice-specific container information including the contact information.
  • This request may be a new service or an existing service, modified to handle the new input data.
  • step S 118 the OAM node 26 receives the response to the request.
  • step S 120 the UE 12 initiates an initial 5GC registration request to the AMF node 16 in accordance with 3 GPP Technical Specification (TS)
  • step S122 the AMF node 16 performs the 5GC registration procedure as defined in TS 23.502.
  • step S124 the AMF node 16 initiates an Nssf_NSSelection_Get request to the NSSF node 20 in accordance with the TS 23.502 procedure.
  • This procedure may have to be performed for every initial UE 12 registration to the 5GC to fetch every S-NSSAFslice-specific container related information which may include contacts lists associated with S-NSSAs for subscribed S- NSSAIs.
  • step S126 the NSSF node 20 locates the slice-specific information container which includes in this example contacts lists for the S-NSSAIs.
  • step S 128 the NSSF node 20 returns to the AMF node 16 the list of S- NSSAIs and any S-NSSA slice-specific information container which includes in this example contacts lists/information associated with the S- NSSAIs.
  • the AMF node 16 returns a registration accept message to the UE 12 including the allowed S-NSSAIs and any S-NSSAFslice-specific information container which includes in this example contacts lists associated with any of the allowed S-NSSAIs.
  • the contacts lists may be rather large, and hence, in some embodiments, a pointer may be optionally returned to the UE 12 instead of the contacts list itself.
  • the UE 12 may then fetch the contacts list via the returned link.
  • the NSSF node 20 may store the contacts list before forwarding such a link to the UE 12.
  • the contacts list may be included in the registration accept message only in the initial 5GC registration and may not be included in a registration refresh request, or a mobility registration procedure. This assumes that the UE 12 stores the contacts list per S-NSSAFslice.
  • step S132 if the UE 12 receives a contacts list in the slice-specific information which is the case in this example, the UE 12 may store any received contacts per S-NSSAEslice, or the UE 12 may fetch the contacts if the UE 12 received a link instead. The UE 12 displays to the user the contacts per S-NSSAI/slice.
  • the UE 12 may update the locally stored information with the received information, as this may be considered to be the most updated contacts list per S-NSSAI.
  • the UE 12 may not display any local information per S-NSSAI unless the information is in the allowed S- NSSAI.
  • the UE 12 For cloud backup, in steps S134 and S136, the UE 12 provides the contacts list information to the UE’s 12 cloud AS node 24 and the AS node 24 then stores the information, accordingly, i.e., contacts list per allowed S-NSSAI. In step S138, the UE 12 stores the information in the SIM (e.g., memory 42) for backup purposes per allowed S-NSSAI.
  • SIM e.g., memory 42
  • the call flow in FIG. 10 illustrates an example case for when the UE 12 updates locally the slice-specific contacts list, if allowed to do so, and how the information may be stored in the NSSF node 20.
  • step S140 the UE 12 updates the slice-specific contacts list per S-NSSAI.
  • step S 142 when the contacts list is updated, and if the S-NSSAI enables the UE 12 to update the contacts list, the UE 12 initiates an UL NAS transport message with a new payload container type IE, which may be considered an S-NSSAI specific IE that includes the updated contacts list per S-NSSAI. This new payload container is transparent to the network.
  • the AMF node 16 updates the NSSF node 20 using e.g., an existing
  • Nnssf_NSSAIAvailability_Update service operation a new input is added to the operation reflecting the S-NSSAI changes in the contacts list, or an entire new contacts list.
  • the AMF node 16 may validate the syntax of the data in the new container type or the NSSF node 20 may perform the validation instead.
  • step S150 the AMF node 16 sends the response back to the UE 12.
  • changes to the contacts list of a slice in the NSSF node 20 may be sent to the UE 12 when the UE 12 initiates a new initial registration; otherwise, this may be signaling intensive, if there is an attempt to update every UE 12 using such an S-NSSAI that has been subject to a change to its contacts list.
  • UE-initiated or network- initiated changes to the slice- specific contacts list may apply to any information received by the UE 12 as part of the slice-specific container information received at e.g., UE 12 registration.
  • the UDM node 22 stores the container including the slice-specific information.
  • the UDM node 22 is used instead of the NSSF node 20 to support providing the transparent slice-specific information to UEs 12.
  • the UDM node 22 may use this element in the S-NSSAI (e.g., only for internal purposes) to obtain the actual S-NSSAI slice-specific container information, including in this example the contacts list from the OAM node 26 or any other data store.
  • the setting of this element in the UDM node 22 may be through offline means or interaction with the OAM node 26.
  • FIG. 11 is a call flow diagram that illustrates an example of the UDM embodiment:
  • step S152 the OAM node 26 is pre-provisioned with the slice-specific information container attribute including the contacts list for the target network slice in accordance with e.g., the GSMA NEST and NG.116.
  • the OAM node 26 is local to the operator.
  • step S 154 the OAM node 26 then issues a request to the UDM node 22 to store the slice-specific container information including the contacts list information. This request may be a new service or an existing service, modified to handle the new input data.
  • the UDM node 22 is informed of the S-NSSAI for whom the slice-specific information including in this example a contacts list is available. The UDM node 22 sets the local information accordingly.
  • step S 156 the OAM node 26 receives the response to the request.
  • the procedures in steps S152-S156 may also be administratively performed.
  • step S 158 the UE 12 initiates an initial 5GC registration request to the AMF node 16 in accordance with 3 GPP Technical Specification (TS)
  • step S160 the AMF node 16 performs the 5GC registration procedure as defined in TS 23.502.
  • step S162 when the AMF node 16 fetches the Access and Mobility Subscription Data Management (SDM), the UDM node 22 locates the slice- specific information including in this example the contacts list per its internal information for all subscribed S-NSSAIs for the registering UE 12.
  • SDM Access and Mobility Subscription Data Management
  • Steps S164-S172 may be the same as steps S130-S138 from FIG. 9 and therefore are not repeated here.
  • FIG. 12 illustrates an example of UE-initiated contacts list changes, assuming the UE 12 is allowed to make changes to the slice- specific information.
  • the AMF node 16 communicates directly with the UDM node 22 to update the information:
  • step S174 the UE 12 updates the slice-specific contacts list per S-NSSAI.
  • step S 178 when the contacts list is updated, and if the S-NSSAI enables the UE 12 to update the contacts list, the UE 12 initiates an UL NAS transport message with a new payload container type IE, which may be considered an S-NSSAI specific IE that includes the updated contacts list per S-NSSAI.
  • the AMF node 16 updates the UDM node 22 with the updated contacts list per S-NSSAI. In step S182, the AMF node 16 sends the response back to the UE 12.
  • a new parameter is proposed to be included to the NEST document in NG.116, which includes a transparent container for slice-specific information including in this example a contacts list specific to the slice.
  • the device vendor cloud server e.g., AS node 24, may also store the contacts list per S-NSSAI.
  • the OAM node 26 updates the corresponding nodes (e.g., NSSF, UDM).
  • FIG. 13 is a call flow diagram illustrating an example of an embodiment in which the slice-specific information is returned to the UE 12 during the PDU session establishment phase.
  • the NSSF node 20 stores the slice-specific information:
  • the OAM node 26 is pre-provisioned with the slice-specific information container attribute including the contacts list for the target network slice.
  • step S 186 the OAM node 26 requests to the NSSF node 20 to store the slice-specific information including the contacts list information.
  • step S 188 the OAM node 26 receives the response to the request.
  • step S190 the UE 12 attempts a 5GC registration e.g., as per existing procedures in TS 23.502.
  • step S192 the AMF node 16 performs the 5GC registration procedure as defined in TS 23.502.
  • step S194 the AMF node 16 initiates an Nssf_NSSelection_Get request to the NSSF node 20.
  • step S196 the NSSF node 20 locates the slice-specific information container which includes in this example contacts lists for the S-NSSAIs.
  • step S 198 the NSSF node 20 returns to the AMF node 16 the list of S- NSSAIs and any slice-specific information associated with the S-NSSAIs.
  • step S200 the AMF node 16 stores the slice-specific information. However, in this embodiment, the AMF node 16 does not return it to the UE 12 in a registration accept message.
  • step S202 the AMF node 16 sends the registration accept message to the UE 12 indicating the allowed S-NSSAIs.
  • step S204 the UE 12 establishes a PDU session establishment request as per existing procedures.
  • step S206 the AMF node 16 selects the SMF node 18 and initiates an Nsmf_PDUSession_CreateSMContext Request which includes the S-NSSAI slice-specific information.
  • step S208 the PDU session establishment procedure may be performed such as per TS 23.502
  • step S210 the UE 12 receive a PDU session establishment accept message including the slice-specific information.
  • step S212 the UE 12 stores the slice-specific information per S-NSSAI.
  • step S214 the backup aspects, such as in steps S134, S136 and S138 may be performed to store the slice- specific information in the cloud and the UE’s 12 SIM(s) per S-NSSAI.
  • FIG. 14 is a call flow diagram illustrating an example of an embodiment in which the slice-specific information is returned to the UE 12 during the PDU establishment phase. The following is a brief description of the steps in the call flow diagram in which the UDM node 22 stores the slice-specific information:
  • step S216 the OAM node 26 is pre-pro visioned with the slice-specific information container attribute including the contacts list for the target network slice.
  • step S218 the OAM node 26 requests to the UDM node 22 to store the slice-specific information including the contacts list information.
  • step S220 the OAM node 26 receives the response to the request.
  • step S222 the UE 12 attempts a 5GC registration e.g., as per existing procedures in e.g., TS 23.502.
  • step S224 the AMF node 16 initiates the 5GC registration procedure as defined in e.g., TS 23.502.
  • step S226 when the AMF node 16 fetches the Access and Mobility Subscription Data Management (SDM), the UDM node 22 locates the slice- specific information including in this example the contacts list per its internal information for all subscribed S-NSSAIs for the registering UE 12.
  • SDM Access and Mobility Subscription Data Management
  • step S2208 the AMF node 16 stores the slice-specific information.
  • step S230 the AMF node 16 sends the registration accept message to the UE 12 indicating the allowed S-NSSAIs.
  • step S232 the UE 12 establishes a PDU session establishment request as per existing procedures.
  • step S234 the AMF node 16 selects the SMF node 18 and initiates an Nsmf_PDUSession_CreateSMContext Request which includes the S-NSSAI slice-specific information.
  • step S2366 the PDU session establishment procedure may be performed such as per 3GPP Technical Specification (TS) 23.502.
  • TS Technical Specification
  • step S2308 the UE 12 receive a PDU session establishment accept message including the slice-specific information.
  • step S240 the UE 12 stores the slice-specific information per S-NSSAI.
  • step S242 the backup aspects, such as in steps S134, S136 and S138 may be performed to store the slice- specific information in the cloud and the UE’s 12 SIM(s) per S-NSSAI.
  • the concepts described herein may be embodied as a method, data processing system, and/or computer program product. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.
  • These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.
  • the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Java® or C++.
  • the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language.
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer.
  • the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
  • LAN local area network
  • WAN wide area network
  • Internet Service Provider for example, AT&T, MCI, Sprint, EarthLink, MSN, GTE, etc.

Landscapes

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

Abstract

L'invention concerne des appareils et des procédés pour des informations spécifiques à des tranches verticales. Dans un mode de réalisation, un équipement utilisateur (UE) est configuré pour amener l'UE à recevoir des informations spécifiques à des tranches de réseau associées à un identifiant de tranche de réseau, les informations spécifiques à des tranches de réseau pouvant être utilisées par l'UE pour une tranche de réseau indiquée par l'identifiant de tranche de réseau et les informations spécifiques à des tranches de réseau étant transparentes aux nœuds dans le réseau. Dans un mode de réalisation, un nœud de fonction de sélection de tranche de réseau (NSSF) est configuré pour amener le nœud de NSSF à recevoir, en provenance d'un nœud de fonction de gestion d'accès, AMF, une requête d'extraction d'informations relatives à au moins une tranche de réseau ; et en conséquence de la requête, envoyer des informations spécifiques à des tranches de réseau au nœud d'AMF, les informations spécifiques à des tranches de réseau étant associées à un identifiant de tranche de réseau et les informations spécifiques à des tranches de réseau étant transparentes aux nœuds dans le réseau.
EP20743851.6A 2020-07-15 2020-07-15 Informations spécifiques à des tranches verticales Pending EP4183223A1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/IB2020/056667 WO2022013602A1 (fr) 2020-07-15 2020-07-15 Informations spécifiques à des tranches verticales

Publications (1)

Publication Number Publication Date
EP4183223A1 true EP4183223A1 (fr) 2023-05-24

Family

ID=71738252

Family Applications (1)

Application Number Title Priority Date Filing Date
EP20743851.6A Pending EP4183223A1 (fr) 2020-07-15 2020-07-15 Informations spécifiques à des tranches verticales

Country Status (2)

Country Link
EP (1) EP4183223A1 (fr)
WO (1) WO2022013602A1 (fr)

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10142994B2 (en) * 2016-04-18 2018-11-27 Electronics And Telecommunications Research Institute Communication method and apparatus using network slicing
CN108632945B (zh) * 2017-03-20 2020-11-06 华为技术有限公司 一种网络切片选择方法、用户设备及网络设备
CN109391648B (zh) * 2017-08-04 2020-12-22 华为技术有限公司 一种应用与网络切片的关联方法、装置和通信系统
US10764789B2 (en) * 2017-08-11 2020-09-01 Comcast Cable Communications, Llc Application-initiated network slices in a wireless network
US10979886B2 (en) * 2017-10-11 2021-04-13 Nec Corporation UE configuration and update with network slice selection policy
KR102327021B1 (ko) * 2017-11-17 2021-11-17 한국전자통신연구원 네트워크 슬라이스를 통한 서비스 제공 방법 및 장치

Also Published As

Publication number Publication date
WO2022013602A1 (fr) 2022-01-20

Similar Documents

Publication Publication Date Title
US20230413024A1 (en) Method of Discovering Services Provided by a Network Repository Function
US10848526B2 (en) Device triggering
KR102615419B1 (ko) 가입 및 통지 서비스
US20200322884A1 (en) Managing network enrollment and redirection for internet-of-things and like devices
EP3800934A1 (fr) Procédé de routage d'un service de l'internet des objets
US9088624B2 (en) Method and apparatus for routing notification messages
US20130073671A1 (en) Offloading traffic to device-to-device communications
WO2015034337A1 (fr) Procédé et dispositif pour le traitement d'un message de requête spécifique dans un système de communication sans fil
US10932171B2 (en) Access point switching method and apparatus
EP3185598B1 (fr) Procédé et appareil d'inscription de demandes
CN109478153B (zh) 机器到机器服务层通信中的消息重定向
US20150119033A1 (en) Devices, Methods, and Computer Readable Storage Devices for Providing Application Services
US20230379392A1 (en) Methods and systems for managing service enabler architecture layer (seal) services
KR101713092B1 (ko) 원엠투엠 환경에서의 배치 통지
AU2021419641A1 (en) Vertical application in edge computing
WO2019091174A1 (fr) Procédé et dispositif d'envoi de message court
KR102285352B1 (ko) 이기종 IoT 장치와 IoT 플랫폼의 연동을 위한 프록시, 방법 및 상기 프록시를 포함하는 시스템
EP4183223A1 (fr) Informations spécifiques à des tranches verticales
JP7428265B2 (ja) 通信端末及びその方法
CN113424608A (zh) 用于为网络提供外部服务的实体
US20230275974A1 (en) Network functionality (nf) aware service provision based on service communication proxy (scp)
WO2023246431A1 (fr) Procédé et appareil de communication
US20230198853A1 (en) Apparatus and method for providing analytics to user equipment
US10169399B2 (en) Flexible profile grouping download
WO2022239349A1 (fr) Serveur, entité de requête, et procédés associés

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20230130

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)