KR20200079352A - Network slicing operation - Google Patents

Abstract

The network control node (main CTRL or CTRL N) may receive the service requested by the WTRU, and the service information may include one or more of a service class, quality of service (QoS) requirements, or mobility characteristics. Includes. The network control node can determine slice information associated with a plurality of network slices and can select at least a first network slice to service the WTRU. The network control node can determine whether the network control node should provide service or another network control node should provide service for the WTRU to access the first network slice. If the network control node determines that another network control node must provide service to allow the WTRU to access the first network slice, the network control node controls another network to allow the WTRU to access the first network slice. It may send a request to another network control node indicating that the node should provide service.

Description

Network slicing operation {NETWORK SLICING OPERATION}

Cross reference of related applications

This application is filed on February 16, 2016, United States Provisional Application No. 62/296,030, filed on March 11, 2016, and United States Provisional Application No. 62, filed on March 11, 2016, the entirety of which is incorporated herein by reference, as set forth in its entirety. /306,738 priority claims.

The types of use cases for 5G networks are expected to vary and one or more of the use cases may be associated with relatively extreme and/or stubborn service requirements. To support many different use cases with different requirements within a cellular communication network (eg, 3GPP), network slices (eg, 5G slice) can be defined, for example, to support communication services of a particular connection type. A network slice includes a set of one or more network functions (eg, 5G network functions) and/or one or more radio access technology (RAT) settings that can be used to provide service for a given application. can do. The use of network slicing can make the 5G network architecture more flexible and/or flexible.

Conventional core network architectures have used a relatively monolithic network and transport framework. Such a framework has been relatively limited in terms of providing differentiated services to several wireless transmit/receive units (WTRUs). Although the use of network slicing can take into account network flexibility, such a scheme has considered relatively uniform procedures and systems in terms of the need to allocate network resources to the WTRU. The introduction of 5G network slicing addresses many potential problems associated with discovering which network slices are being provided by the operator, selecting network slices for one or more WTRUs, and/or connecting to a particular network slice. I can make it.

Systems, methods, and means are provided for a network control node to connect a wireless transmit/receive unit (WTRU) to a network slice of a network. The network control node may receive service information associated with a service requested by the WTRU, and the service information includes one or more of a service class, quality of service (QoS) requirements, or mobility characteristics. The network control node may determine slice information associated with a plurality of network slices, and the slice information includes the identifier of the network slice, the priority of the network slice, the service class serviced by the network slice, the target device class, and the QoS target. , Mobility support, security services, charging information, and/or performance information. The network control node can determine subscriber information for the WTRU. The network control node may select at least a first network slice among a plurality of network slices to provide a service to the WTRU, where the network control node may include service information, slice information associated with the first network slice, and subscribers to the WTRU. The first network slice is selected based on the information. The network control node can determine whether the network control node should provide service or another network control node should provide service for the WTRU to access the first network slice. If the network control node determines that the network control node must provide service in order for the WTRU to access the first network slice, the network control node may provide the WTRU with at least one network service associated with the first network slice. Or, if the network control node determines that another network control node must provide service in order for the WTRU to access the first network slice, the network control node controls another network to allow the WTRU to access the first network slice. It may send a request to another network control node indicating that the node should provide service.

1 shows a diagram illustrating exemplary network slices implemented on the same infrastructure (eg, by employing combinations of multiple RATs and/or nodes).
2 is a diagram illustrating network slice information provided by a network when a wireless transmit/receive unit (WTRU) first attaches or registers with the network.
3 shows a diagram showing network slice information retrieval by request, for example, after an initial connection to a network slice.
4A shows a diagram illustrating an exemplary network slice selection made on a per-WTRU basis (WTRU).
4B shows a diagram illustrating an exemplary network slice selection made on a per-service basis.
5 shows a diagram illustrating an exemplary network control slice.
6 shows an exemplary initial network slice connection.
7 shows a diagram illustrating an exemplary multiple network slice connection forking.
8A shows a diagram of an exemplary communication system in which one or more disclosed embodiments can be implemented.
8B shows a diagram of an exemplary WTRU that may be used within the communication system shown in FIG. 8A.
8C shows a diagram of an exemplary radio access network (RAN) and an exemplary core network that may be used within the communication system shown in FIG. 8A.
8D shows a diagram of another exemplary RAN and example core network that may be used within the communication system shown in FIG. 8A.
8E shows a diagram of another exemplary RAN and example core network that may be used within the communication system shown in FIG. 8A.

Detailed description of exemplary embodiments will now be described with reference to various drawings. While this description provides a detailed illustration of possible implementations, the details are intended to be exemplary and never limit the scope of the present application.

3GPP is in the process of designing a next-generation core network to meet future 5G requirements. Exemplary requirements include control plane/user place (CP/UP) separation, access agnostic services, integration of cross-domain networks, and network-function virtualization (NFV). , SDN and the introduction of technology enablers such as network slicing.

NFV is a network architecture concept that can use technologies related to IT virtualization to virtualize entire classes of network node functions into building blocks that can be chained or linked together to create communication services.

NFV relies on conventional server-virtualization technologies such as those used in enterprise IT, but it is different. Virtualized network functions (VNFs) are different software and processes besides standard high-volume servers, switches and storage, rather than or in addition to having custom hardware devices for each network function. It may include one or more virtual machines running them, or even a cloud computing infrastructure.

The exemplary NFV framework includes three components: virtualized network functions (VNFs), network function virtualization infrastructure (NFVI), and network functions virtualization management and orchestration architecture framework (NFV- MANO Architectural Framework). For example, VNFs can be software-based implementations for network functions that can be deployed on one or more NFVI. The NFVI can correspond to the hardware and software components used to build the environment in which the VNFs are deployed. For example, an NFV infrastructure may cover several locations, and a network providing connectivity between these locations may be considered part of the NFV infrastructure. The NFV-MANO architecture framework includes functional blocks, data stores used by functional blocks, and reference points and interfaces through which these functional blocks exchange information for the purpose of managing and orchestrating NFVI and VNFs. Can respond to a set of people.

The building blocks for both NFVI and NFV-MANO can be NFV platforms. In the role of NFVI, the NFV platform can include virtual and physical processing and storage resources, and virtualization software. In the role of NFV-MANO, the NFV platform may include VNF and NFVI managers and virtualization software running on a hardware controller. The NFV platform can implement carrier-grade features that are used to manage and monitor platform components, recover from failures, and provide efficient security (which may be needed for public carrier networks).

Software-defined networking (SDN) is an approach to computer networking that allows network administrators to manage network services through abstraction of higher-level functionality. This can be done by separating the system that determines where traffic can be transmitted (the control area) from underlying systems that forward traffic to the selected destination (data area).

SDN enables a dynamic, manageable, cost-effective, adaptable architecture suitable for today's applications with high bandwidth and dynamic properties. The SDN architecture allows network control to be directly programmable by separating network control and forwarding functions, allowing the underlying infrastructure to be extracted from applications and network services.

The SDN architecture can include one or more of the following features in any combination. For example, the SDN architecture can be directly programmable (eg, network control can be directly programmable because it can be separated from forwarding functions). The SDN architecture can be fast (eg, extracting control from forwarding can allow administrators to dynamically adjust network-wide traffic flow to meet changing needs). The SDN architecture can be centrally managed (eg, the information network can be (logically) centralized to software-based SDN controllers that maintain a global view of the network, which is represented by a single logical switch to applications and policy engines). Can be). The SDN architecture can be configured programmatically relatively quickly, which enables network administrators to configure, manage, protect, and optimize network resources through dynamic and/or automated SDN programs. The SDN architecture can be open standards-based and/or vendor-neutral.

When implemented through an open standard, SDN can simplify network design and operation because instructions can be provided by SDN controllers instead of multiple, vendor-specific devices and protocols. have.

A network slice (e.g., 5G slice) includes, for example, software modules running on cloud nodes, specific configurations of a transport network supporting flexible location of functional units, dedicated radio configuration, specific radio access technology (RAT) technology), the configuration of a network device (eg, a 5G device), and/or the like, and may include one or more or all domains of a given network. Several network slices can include the same or different functions. Some functions for a mobile network may not be included in some of the network slices, while other functions may be included in all network slices provided by a given network. Network slices can be designed to provide traffic handling for use cases. For example, some network slices may be targeted to support large-scale broadband (eg, high-speed, high-bandwidth applications), while other network slices may be large-scale machine-type communication (eg, Internet of Things (IoT)). -of-Things use cases) while other network slices can be used for ultra-reliable low-latency communication (e.g. for critical infrastructure communication). I can apply. Network slices can be designed to share some or all of the underlying network resources, while being relatively functionally independent for the service of different WTRUs using different use cases. Network slices can be designed to avoid unnecessary functionality. The slice concept can be flexible, for example, to allow expansion of an existing business and/or creation of a new business. Third-party entities may be given authority to control certain aspects of slicing, for example, through an appropriate application program interface (API). Tailored services can be provided.

Methods and devices associated with network slicing operations are provided. For example, the WTRU and/or one or more network nodes can be configured to discover one or more network slices for use by the WTRU. For example, information broadcast by a radio access network (RAN) may enable network slice selection. This information can include the identifier for the network slices, the priority of the network slices, the service classes served by the network slices, and/or the like. When multiple network slices serving different target user groups and/or services are found, the methods associated with network slicing operations to select the appropriate network slice to service the WTRU are WTRU and/or It can be used by one or more network nodes. The selection may be made autonomously by the WTRU, and/or may include a selection procedure involving both the WTRU and/or one or more network nodes, and/or may be made by one or more network nodes. The selection may be made by one WTRU and/or one service. The WTRU may use multiple network slices, for example, for different types of services.

1 shows an example in which multiple 5G slices can be operated (eg, operated simultaneously) on the same network infrastructure. As an example and for purposes of illustration, a 5G slice supporting a specific smartphone use case may be realized by distributing functions (eg, CP functions and/or UP functions) to multiple nodes across the network. have. At the same time, a 5G slice supporting automotive (e.g., autonomous driving) use cases may emphasize security, reliability, and/or latency requirements. For such a slice, functions (eg, all of the required and/or potential dedicated functions) can be instantiated at the cloud edge node, eg, to ensure that performance targets are achieved. For example, vertical applications may be included due to latency constraints. Sufficient open interfaces can be defined to enable such vertical applications to be on-boarded on a cloud node. For 5G slices that support large-scale machine-type devices (e.g., sensors, IoT, etc.), basic C-plane functions are used, e.g., using contention-based resources for access. Can be configured. For example, where a given device is known to be relatively stationary, one or more mobility functions may be omitted. Other dedicated slices can be operated in parallel. For example, a generic slice may be used that provides a basic connection (eg, best-effort connection) to cope with unknown use cases and/or traffic. Regardless of the slices supported by the network (eg, 5G network), the network may include functionality to control and/or protect the operation of the network, eg, from end to end and/or in any situation. .

Dedicated infrastructure resources can be used for specific slices. Infrastructure resources and functions can be shared among multiple slices. An example of a sharing function may be a wireless scheduler. The RAT's scheduler can be shared among multiple slices. For example, the scheduler can play a role in allocating resources and/or setting the performance of a network slice (eg, 5G slice). The role may include determining the extent to which a consistent user experience can be realized. The scheduler implementation of the network can be proprietary, but the level of openness can be defined to perform sufficient control over the functions of the scheduler, for example, to meet scheduling requirements for a given network slice.

In an exemplary system architecture (eg, 5G system architecture), C-region and U-region functions (control area and user area functions, respectively) can be separated. For example, according to the SDN principle, open interfaces can be defined between C-region and U-region functions. Open interfaces between access-specific and access-agnostic functions to enable integration into additional access technologies (eg fixed/wired and/or wireless) networks Can be defined. The fronthaul interface(s) between remote wireless units and baseband units may be open and/or flexible. Multi-vendor operation and/or forward and backward compatibility can be provided. Options for reducing transport bandwidth can be provided. Interfacing between functions allows for multi-vendor provisioning for multiple functions.

To support this flexible open architecture, the granularity in which functions are defined can be considered in the system architecture design. Finer granularity may improve flexibility, but may cause additional network complexity and/or load. For example, testing efforts for different functional combinations and/or slice implementations can be disruptive and functional interworking problems between multiple networks can occur. A granularity level that balances flexibility goals and complexity can be identified. The granularity level can affect how the eco system delivers the solutions.

Network slice operation can be transparent to the end user/devices or can be made visible. Devices may be configured to discover which network slices are being provided by the operator (eg, in the current location of the devices and/or in the radio access network). In one example, network slices may encompass core network functions, sub-resources, radio access resources, and/or the like. A radio access network can belong to several network slices. In such a situation, information about the network slices may cause the wireless transmit/receive unit (WTRU) to select an appropriate radio access technology (RAT) or radio access network (RAN) for the target network slice. In another example, a network slice providing a service may be susceptible to dynamic changes according to certain criteria, such as a device's mobility status. For example, because mobility state information may be available on the device side (eg, the device is more conveniently available than other network components), the device can initiate its changes. In one example, the network is on behalf of the WTRU based on information stored for the WTRU (eg, subscription information, capability information, etc.) and/or information provided by the WTRU (eg, mobility information, service information, etc.). It is also possible to select one or more network slices.

The 5G system or next-generation core network architecture enables a third-party application server (AS) to provide information about services provided by the network (eg, connection information, quality of service (QoS), mobility, and power saving). Etc.), and dynamically customize network capabilities for a variety of different use cases. The core network may provide such an exchange of network capabilities to a third-party service provider through an API or service capability exposure function (SCEF) of the core network. In the case where network configuration and connection information is exchanged, the AS may provide information to assist in requesting a specific network slice or making a decision for the core network to select a particular slice. Methods can be defined for a supported selection of such a triggered application server or core network slice.

As indicated by the examples below, the WTRU can operate in various modes when discovering network slices. WTRU can operate in early detection mode. In this mode, the WTRU can discover available or supported network slices before accessing or connecting to the radio access network. In one example, the RAN may belong to one or more network slices, but not all available network slices. The WTRU can determine whether to access this RAN or select another RAN based on the found network slices supported by the RAN. The WTRU may employ one or more of the following methods to discover network slices.

For example, the RAN may broadcast information associated with available network slices to which the RAN belongs or is connected. The RAN may broadcast information using radio interface signaling (eg, system information and/or beacon messages). Network slice information for a specific network slice includes the following example fields or parameters, i.e., the identifier of the network slice, the priority of the network slice, the service class(s) served by the network slice, the target device class, and the QoS targets. , Mobility support, security service, charging information, and/or performance information.

The WTRU and/or network node may use network slice information parameters to select the appropriate slice for the WTRU. A device that performs slice selection for a WTRU (eg, one or more network nodes, a WTRU, a combination of one or more network nodes and a WTRU, etc.) may partially or all examples of network slice information parameters to perform slice selection Can be used. Various combinations can be used, and the identity of the set of parameters used for the selection of a given slice can be based on the service, the identity of the WTRU, network capabilities, and the like. The device of choice (eg, network node and/or WTRU) can ensure that values for network slice information parameters are sufficient (or support anyway) to support expected services to be used by the WTRU through that network slice. have.

An example of a network slice information parameter that can be used for network slice selection may include a network slice identifier. The network slice identifier can be unique (eg, globally unique or unique in the operator's network). If the slice identifier is unique in the operator's network, a combination of a network ID (eg, a public land mobile network or PLMN ID) and a network slice identifier can uniquely identify the network slice. Slice identifiers broadcast for discovery purposes may be the same or different from slice identifiers used in core network slice operation. For example, broadcasted network slice identifiers may be human-readable text, while identifiers used in slice operation may include multiprotocol label switching (MPLS) labels or virtual LAN (VLAN) ; virtual LAN) IDs.

An example of a network slice information parameter that can be used for network slice selection may include slice priority. Available network slices may be assigned a selection priority. In one example, the WTRU may not have a specific target network slice. The WTRU may follow the priority order in selecting network slices. For example, the highest priority network slice may be considered the default network slice. Other network slice information, such as slice identifier or service class, may be associated with a certain priority. The presence of such information (eg, slice identifier and/or class of service) may indicate a priority and may not require explicit priority information.

An example of a network slice information parameter that can be used for network slice selection may include a slice service class. The service class may indicate a target service type and/or user group to which the network slice intends to provide a service. The service class may indicate general performance parameters of the network slice (eg, delay, throughput, service continuity, security, etc.). An example list of service classes may include the following: a mission critical service, a general broadcasting service, a delay-tolerant service, and/or a high mobility service. In one example, the broadcast slice information may include two or more service classes because the network slice may support multiple service classes.

One example of a network slice information parameter that can be used for network slice selection may include association with certain types of WTRUs. The network slice can be arranged to serve a specific target group of WTRUs (eg, not all WTRUs). For example, services critical to the performance of a mission may only be accessible to WTRUs belonging to an emergency service group (eg, police, fire department, medical assistance, etc.). WTRUs may be pre-configured to be associated with a certain access class. A network slice (eg, each network slice) may indicate a range of device access classes allowed to access the network slice.

One example of a network slice information parameter that can be used for network slice selection may include one or more QoS metrics. QoS indicators (eg, minimum or maximum delay, minimum or maximum throughput) may be displayed. For example, QoS metrics can reflect what the network slice is expected to achieve. Such an indicator can be used by devices that are critical to mission performance (eg, devices with strict QoS requirements).

One example of a network slice information parameter that can be used for network slice selection may include an indication of support for types of mobility management mechanisms. Different network slices may adopt different mobility management mechanisms. Details of the mobility management mechanism may be indicated through mobility support information. For example, the following, i.e., supported mobility protocols (e.g. GTP, PMIP, DSMIP, etc.), whether IP address preservation is supported, and whether service persistence (with or without IP address preservation) is supported. , Whether or not distributed mobility is supported, and/or one or more of the similar can be indicated in the mobility assistance information.

One example of a network slice information parameter that can be used for network slice selection may include a security mechanism. Different network slices may adopt different security mechanisms. The mobility support information may indicate details regarding the security mechanism. Billing rate related information may be displayed for each network slice (eg, each network slice). Performance related information such as percentage of load, congestion, and/or the like can be displayed.

For example, when the WTRU performs or assists with network slice selection, the WTRU may acquire broadcast network slice information. For example, the WTRU may obtain information from air interface signaling (eg, system information or beacon messages). The WTRU may store the acquired network slice information in its memory. The WTRU may pass the obtained slice information to higher layers, for example, to determine whether to select a specific network slice. The obtained network slice information may be presented to the user through the user interface.

The WTRU can act as a relay node and provide communication relay services to other WTRUs. For example, the WTRU may act as a relay WTRU for proximity services (ProSe) and/or device to device (D2D) communication. The WTRU may act as a relay for a roadside unit (RSU) in a vehicle communication system. The WTRU may broadcast network slice information of a slice to which the WTRU is currently provided or belongs. Broadcasting may urge other WTRUs (eg, remote WTRUs) to select a relay WTRU for desired services. For example, broadcasting may be transmitted through a D2D/ProSe interface, such as a PC5 interface.

The WTRU may receive network slice information from a network server (eg, using JSON or web APIs such as XML-based APIs). The network service can identify available network slices and/or provide network slice information parameters (eg, slice identifier, service classes, etc.) for one or more slices. Slice information provided by a network server can be organized in a number of ways. In one example, slice information may be organized based on geographic locations where slices are available (eg, RAN IDs, cell IDs, various area IDs, network IDs, GPS coordinates, etc.). In one example, slice information may be organized based on the period during which slices are available (eg, “always”, “every 8-10 am”, “every Saturday”, etc.). In one example, slice information may be organized based on radio access technologies or networks of slices (eg, LTE access, WLAN access, etc.).

Detailed network slice information may be pre-configured in the non-volatile memory (eg, of the WTRU). Slice identifiers can be used as indices for pre-configured information. In such a case, the network may provide available network slice identifier(s). The WTRU may use the slice identifier(s) provided by the network to retrieve the stored corresponding slice information. Pre-configured network slice information in the WTRU may be susceptible to changes by the network (eg, using the Over the Air (OTA) method).

After the WTRU selects and connects to the RAN, for example, the WTRU's initial network message, such as an attachment or location area update, or PDN connection request, is a network with information about the network slices available through that RAN. You can head to the functional unit/entity. Such a network function may be a mobility management control function or a network slice selection function. In the initial network messages, the WTRU may provide the associated RAN ID, the RAT of the connected RAN, the selected PLMN, desired services or other information related to network slice selection. The network function receiving the message will select an appropriate network slice for the WTRU or return network slice information available to the WTRU in a response message.

The network function providing network slice information may be independent of any network slices, or may belong to a default network slice that processes the WTRU's initial network messages if no other network slice is selected for the WTRU. Each RAN may direct the WTRU's initial network messages to this network function, for example, if no other specific network slice is indicated in the WTRU's message. The received network slice information can be used by the WTRU to autonomously select a network slice, or it can be presented to the user through a user interface for future user intervention network slice selection.

2 is a diagram illustrating exemplary network slice information provided by a network when a WTRU (or UE) first attaches or registers to the network.

The WTRU may initially select or connect to a network slice, such as the default network slice. The WTRU may request additional information regarding other available slice information. The WTRU may use (additional) information to reselect a network slice for current or future services. Additional network slice information may be provided by a RAN, a mobility control function unit, or a network slice selection function unit. The request of the WTRU may be sent directly to a centralized control function/database independent of the network slice, and the requested information may be provided by the function/database; Or the request can be sent to some control function of the currently connected network slice and forwarded from there to a centralized control function, such as a common network slice selection function. Similarly, the WTRU may provide information related to network slice selection in the request.

3 is a diagram illustrating network slice information retrieval after initial connection to a network slice.

Other network slice discovery modes may be possible. For example, a late discovery mode can be used. In this mode, after the WTRU selects the RAN and connects to it, the WTRU can discover available or supported network slices. A transparent mode can be used. In this mode, the network may select (eg, randomly select) a service provisioning network slice suitable for the WTRU (eg, the WTRU may not perform slice discovery). Network slice operation can be transparent to the WTRU. The WTRU can provide information such as its service class, QoS requirements, mobility characteristics, etc. to help the network select a slice.

When a network supports network slicing and multiple network slices are deployed (eg, to provide services to different target user groups and/or services), the WTRU may, for example, service and/or the WTRU's services. Based on the characteristics, a network slice can be selected (or serviced by a network slice). For example, the WTRU may be connected to a network slice optimized for WTRU's services and/or characteristics. In one example, both the WTRU and the network can participate in network slice selection, and agreement can be reached between the WTRU and the network regarding the selection. In one example, the WTRU is simultaneously connected to multiple network slices for its various applications.

4A and 4B illustrate exemplary network slice selection methods. As shown in FIG. 4A, network slice selection may be performed on a per-WTRU basis (WTRU). In an implementation of an exemplary per-WTRU selection, the WTRU may be connected to a network slice, and all services and/or applications running on the WTRU may be serviced by the selected network slice.

As shown in FIG. 4B, network slice selection may be performed on a per-service basis. In an example per-service selection implementation, the WTRU may select different network slices for different services and/or applications. The WTRU may be serviced by multiple network slice instances at the same time.

The WTRU may be configured to autonomously select one or more network slices. In one example, the WTRU can autonomously select the network slice(s) by comparing the WTRU's preconfigured designation or target service providing network slices with the discovered available network slices. The WTRU may be pre-configured using target or preferred network slice(s). For example, the WTRU may be configured using a list of preferred or target network slice identifiers and/or an order of selection priority of the WTRU's non-volatile memory. The WTRU may discover one or more available network slice instances. The WTRU can search in its configured list of preferred network slices to determine whether one of those slices is available. The WTRU can select the highest priority slice available. The WTRU includes, for example, the following: the service class(s) to which the WTRU belongs, mobility mechanisms supported and/or preferred by the WTRU, security mechanisms supported and/or preferred by the WTRU, QoS targets, and/or Or other related information, such as one or more of the similar. The WTRU may use one or more of the information described herein to match pre-configured/target network slices with the discovered network slice information, and accordingly may select a network slice that provides service. In one example, a network (eg, a node in a network) uses one or more information described herein (eg, the service class(s) to which the WTRU belongs, WTRU, for use in selecting a service provisioning network slice suitable for the WTRU) Can obtain support and/or preferred mobility mechanisms, WTRU support and/or preferred security mechanisms, QoS targets, and/or the like).

The WTRU may have a set of configurations (eg, as described herein) for a home network. The WTRU may have a set of configurations (eg, as described herein) for a visited network. The WTRU may have such configurations one service at a time. The WTRU may have such configurations one by one session. The WTRU may select different network slices for various services or sessions. The WTRU can select multiple network slices simultaneously if such services/sessions are running simultaneously. The WTRU can be configured to have a default or fallback network slice. The WTRU may step back to select a default network slice, eg, when the WTRU's preferred network slices are not available. The default network slice may be configured by, for example, one service or one network operator.

The WTRU may receive network slice selection policies from the network. For example, a network slice selection policy can describe which network slices can be selected under certain conditions/criteria. For example, the selection policy may specify the following conditions, i.e., which particular network slice(s) can be selected in a particular geographic area and may include RAN IDs, cell IDs, various area IDs, network IDs, Geographic locations that can be identified by GPS coordinates, and/or the like; Access technologies that can specify which specific network slice(s) can be selected when the WTRU adopts a specific radio access technology such as LTE or WLAN; Services that can specify which network slices can be selected for particular services (eg, if multiple services are running on the WTRU, multiple network slices may be selected according to policy); And/or one or more of the mobility levels that may indicate that slice A may be selected when the WTRU is low mobility and slice B may be selected when high mobility.

After the WTRU selects one or more network slices (eg, autonomously selects), the WTRU may display the selection result. In one example, the indication may include targeted network slice identifiers in WTRU-network signaling (eg, initial attachment, PDN connection request, etc.). In one example, the found network slices can be presented to the user, eg, through user interfaces, and the user can manually select the desired network slices. The results of user selection can be passed to related radio access modules and/or other higher layer modules. The WTRU may make slice selection recommendations to the user. The user can select slices by one service, and thus multiple slices simultaneously.

The network can be configured to control the selection of network slices. For example, the network can be configured to select one or more network slices for the WTRU (eg, the WTRU can be assigned multiple network slices and can access these slices simultaneously).

5 shows an exemplary network control slice selection. A number of techniques can be used to allocate at least one network slice to the WTRU. The term "slice" as used herein may refer to a complete network slice or sub-network slice.

In one example, a main control node can be used to perform slice selection between a set of network slices. This primary control node can receive messages from higher layers (eg, Non-Access Stratum (NAS) messages or equivalent, and may be referred to as NAS messages in this document). The primary control node can process the message to determine which slice to allocate for the WTRU. The primary control node can use one or more network slice information parameters to select a network slice. The primary control node can use the information provided by the WTRU to select the network slice. For example, the WTRU can indicate the services the WTRU wants to use, and the primary control node can use the service information provided to select the slice. The primary control node can use subscription information for the WTRU to select a slice. The primary control node can use local policy information to select a network slice.

In one example, the WTRU may send a NAS message for initial registration with the system. When sending the first NAS message for registration (e.g., when the WTRU has not been previously registered), the WTRU tells the wireless layer that the NAS message or established connection is to register the WTRU for the first time (e.g., via RRC message). Can be displayed. In one example, the WTRU may indicate that a network slice has not been allocated. Based on the indication, the RAN can send a NAS message to the main control node and the NAS message can contain a set of information related to the services the WTRU wants to get. Once the NAS message arrives at the primary control node (e.g., shown as 1A in Figure 5), the node determines the set of network slices (and/or addresses of these nodes) that can be assigned to the WTRU. Information included in the message and/or other information (eg, local policy information, subscriber information, etc.) may be used. For example, the primary control node can use the service information provided by the WTRU to select a network slice with appropriate network slice information parameters to provide service for the WTRU.

Once determined, the primary control node can take one or more of the following exemplary actions. The primary control node can contact one or more network slices that can provide service to the WTRU (eg, based on the services requested by the WTRU). The primary control node can forward NAS messages received from the WTRU. The primary control node is a subset of NAS messages (e.g., to include information related to the type of service a slice can provide and not to include other information not related to the service(s) that can be provided by a network slice ( sub-set) can be forwarded. The main control node can forward new NAS messages. The primary control node may send another type of message (eg, a different protocol type) based on the interface that exists between the primary control node and the control entity nodes of the slices. The primary control node may include service information, eg, service information allowed for the WTRU (shown as 1B and 1C, for example).

In one example, the WTRU may be allowed to obtain service from a single slice. In such a case, the main control node can contact the control entity of the selected slice. In addition, although only two network slices are shown in FIG. 5 (eg, indicated by 1B and 1C), more network slices may be contacted or allocated by the primary control node. The primary control node can send subscriber information for the associated WTRU. The primary control node can send a response NAS message to the WTRU, for example, to reply to the receipt of the NAS message. The primary control node can inform the WTRU of the number of slices allocated to the WTRU (eg, via a response message). The primary control node can inform the WTRU that network slices are processing the request(s) of the WTRU (eg, via a response message).

The control entity of the network slice may receive a request to provide service to the WTRU. For example, the control entity can receive a NAS message or another message from the main control node. The control entity determines whether it can provide service to the WTRU based on information included in the message (eg, service related information from the WTRU) and/or other information (eg, subscriber information, local policies, etc.). Can be confirmed. Once the control entity determines that it can provide service to the WTRU, the control entity can send a NAS message to the WTRU and indicate that the WTRU has been registered for a particular set of services. A network slice that includes a control entity (eg, a slice's control entity) may provide the WTRU with an identity and/or address indicating a particular network slice.

There may be a primary control node for network selection and/or slice control/network nodes may not have a "main" or "master" node. The RAN can forward the NAS message to the control entity in the network slice (eg, any network slice) using the RAN's normal methods for selecting the core network. Once the NAS message arrives at the control entity of the network slice for the core network connection selected by the RAN, the control entity can confirm whether or not to provide the service to the WTRU for some or all of the required services. The confirmation may be made based on information included in the NAS message and/or other information (eg, subscriber information, local policies, etc.). If the control entity determines that one or more of its supported slices can provide service to the WTRU, and for all services, the control entity can process the NAS message and process the WTRU Can respond to If the control entity determines that it is unable to service the WTRU and/or that at least one service must be provided by a network slice associated with a different control entity, then the control entity can take one or more of the following actions: have. The control entity can forward the NAS message to the primary control node (eg, as shown at 2A). The control entity can send the NAS message to another network slice (eg, as shown in 2B). The control entity can use the (enhanced) Dedicated Core Network Selection (eDECOR) method to forward the NAS message to another network slice (eg, as shown in 2C). The control entity may be configured using information about which other slices are capable of serving the WTRU (eg, addresses of those slices or control entities of those slices).

If the control entity determines that it can provide some of the required services of the WTRU, the control entity can process NAS messages for the services it can provide. In one example, for services that the control entity cannot provide and/or services that it has decided not to provide, the control entity may forward NAS messages to other network slices. The control entity can also forward new NAS messages to other network slices. The new NAS message may contain information about services that may be provided for the WTRU by other slices. The control entity may forward the message (eg, existing or new) either directly (eg, as shown in 2B) or using eDECOR (eg, as shown in 2C). In one example, for services that a particular network slice cannot provide, the network slice (or control entity of that slice) may forward a message to the primary control node (eg, as shown in 2A). The primary control node can take any of the actions described herein.

An application server (AS) may trigger or assist slice selection. For example, a third-party AS can request a new network slice, or provide certain application level criteria or characteristics that can assist the network to make a slice selection decision. The AS can communicate directly with the network, for example, via an API exposed through exposure functions, or through the WTRU's application client. The AS can send information to the WTRU through application level signaling. Information can be passed over the network via WTRU as a network signaling protocol. For example, an application running on the WTRU may display service information in network signaling layers (eg, NAS, RRC, etc.) capable of transmitting service information to a network control node for slice selection. As described in this document, an AS that provides information to assist in slice selection is an AS and/or WTRU that provides information directly to a network node (eg, through an API, through an SCEF, without WTRU involvement, etc.) It should be understood that it refers to both AS providing information via (eg, WTRU application layer providing service information to lower layers delivering information to the network node via RAN). One or more of the following information, i.e. application QoS requirements, type of application, and/or frequency of application data transmission (e.g., via the WTRU and/or from the AS to the network backend) of the network slice It can be sent to the network to aid in selection.

In one example regarding application QoS requirements, the AS may send application level QoS requirements to the network for slice selection purposes. QoS requirements may include a level of application priority. The AS may (eg, also) include user priorities within the application. Other QoS parameters (eg, bit rate required, type of expected flows (voice, video, etc.)) may be included.

In one example regarding the type of application, there may be various types of applications running on the WTRU. The network slice decision can be made based on the category of the application. These categories can include machine type applications or Internet of Things (IoT) applications, health care applications, emergency or public safety applications, and the like. The application type or category can be determined by the application ID, or the AS can explicitly indicate the application type in the API request to the impression layer or network.

In one example regarding the frequency of application data transmission, the third party AS may indicate the expected data rate for a particular application on the network. This may be in the form of transmitting the expected time intervals when the data is being transmitted or the average amount of data for a given time (eg, average data (bits) to be transmitted within an hour or during a day). Such information can also be passed over the network for slice selection purposes as described herein.

A third-party AS can play a part in slice selection with a very large capacity. For example, the AS may assist the network slice selection node in the network during the initial decision (called early detection in this document) to allocate one or more network slices to the WTRU. The network can request to provide information to the AS to make the appropriate slice allocation decision. The AS can provide information that can be considered input by the network to make the final selection. The network node can obtain application information from various application servers and make a final decision regarding allocating one or more network slices to the WTRU after considering application specific information from multiple application servers. For example, in the case of multiple application servers providing slice selection assistance information, the network may allocate one or more network slices that best meet the needs of this AS. The network may contact application servers based on the application ID or other application information provided to the network in the initial service template by the WTRU.

The network may allow third-party AS to experience slice selection or similar services. Certain APIs may be available for the AS to enable a particular slice to be requested (or, for example, that the current network slice does not satisfy application requirements, or services provided by the AS by the current network slice) At least allow AS to notify the network). The AS may initiate an API request when accessing the service through the exposure function, or may send a request directly to the network (eg, if there is a direct interface between the AS and the network to request a new network slice). . The AS can include application parameters in the request to the network. The network can make a new slice decision, for example, based on the request received from the AS. The network decision may also take into account requirements from other application servers sending data to the WTRU. The network may accept or reject requests from the AS to allocate new network slices to the WTRU. If the request is accepted, new slice information can be delivered to the WTRU. The network may notify the WTRU directly to the network through the WTRU. The network can inform the AS that the API request has been accepted. The AS can inform the WTRU via application level signaling about new slice(s) that should be selected by the WTRU. This procedure can be used in "late discovery". The information sent to the WTRU in order to be able to connect to the appropriate slice(s) may include one or more of the following: slice information, PLMN or network ID, and/or time/case to disconnect.

In one example of slice information (eg, slice ID number, slice name), multiple slice information (ID number, name, etc.) may be provided for a case where the WTRU needs to be connected to multiple network slices.

In one example for a PLMN or network ID, the WTRU may be asked to connect to the roaming partner's network slice, as the home network or service provider network may not meet the WTRU/application requirements.

In one example of the time or case when the WTRU needs to disconnect from the current serving slice and attach/connect to a new slice, immediately when the WTRU enters idle mode or has data to send for a particular application, immediately The network slices may be changed or the WTRU may be advised to change the network slices. The WTRU may be given a certain amount of time (eg, seconds or minutes) before the WTRU needs to disconnect/disconnect from the current network and send a request to attach/attach a new slice.

The third party AS can be charged by the network to use slice selection services. There may be multiple levels of billing based on the type of request. Requests that the application is not satisfied with the current slice may be billed differently than an explicit request that the application server may prefer a new network slice.

6 is a diagram illustrating an exemplary initial network slice connection. When the WTRU autonomously selects a network slice, the WTRU may explicitly initiate an attachment or PDN connection procedure for the selected network slice. In the attach or PDN connection request, the WTRU may directly include the identifier or service name (eg, similar to the APN) of the selected network slice, which may be mapped to the target network slice. The initial attachment or PDN connection procedure may be processed by the control function of the selected network slice. There may be a "Portal Function" in each network slice that processes the initial connection request from WTRUs. The "portal function" may have the ability to download a user subscription profile from a central database, and may bring other necessary control functions into the same network slice to complete the connection procedure.

There are several ways such messages can be forwarded to the portal function of the target network slice. For example, the RAN may have the ability to identify the target network slice of such messages by parsing the network slice identifier or service name of the messages, or the selected network slice is stored in the RAN's WTRU context in previous signaling. have. Since the RAN can be configured with the address of the portal function portion of each network slice, the RAN can forward a message to the portal function portion of the target network slice. For example, the message can be forwarded without exception by the RAN as a common control function that can be independent of the network slices, and the common control function is capable of analyzing the target network slice and forwarding the message to the portal function of the target network slice. Can have For example, the message can be forwarded without exception by the RAN to the common control function or the portal function of the default network slice. The common control function or the portal function of the default network slice can analyze the actual target network slice and instruct the RAN to direct the message back to the portal function of the target network slice.

Upon receiving the initial attachment or PDN connection request, the process control function may initiate interaction with other network functions to complete the connection. For example, the portal functionality is the following: the network-slice-specific authentication functionality to perform additional authentication to the WTRU (the WTRU may have been generally authenticated when accessing the RAN and the network), first for the WTRU One or more of the gateway control function of the same slice to establish a PDN connection (eg, a default bearer), and/or a QoS control function to install a QoS profile for the connection may be invoked.

Network slice connections can be proxied by the same common control function. The network slice connection can occur directly between the WTRU and the network slice. The interaction between the WTRU and the network functions of the network slice may be through a portal function, for example, messages from the WTRU to a specific network function (eg, an Auth function) to the portal function by the RAN. Can be forwarded. The portal functionality can forward the messages to the appropriate functionality to process the messages. For example, messages from various network functionalities within the network slice to the WTRU may go to the portal functionalities. The portal function can forward messages to the RAN and WTRU. The RAN may need to store the address of the portal functionality of the network slice.

7 is a diagram illustrating multiple network slice connection forking. The WTRU may be connected to multiple network slices (eg, for the first time). The WTRU may decide to connect to multiple network slices based on configuration on the device, network policy regarding network slice selection, and the like. The WTRU may sequentially initiate a single connection to each selected network slice using the procedures described herein. Each connection request (first attachment or PDN connection request) may include a single slice identifier or service name. The WTRU may include multiple network slice identifiers or service names in a single initial connection request and send the request to the common control function. The common control function can “fork” multiple individual connection requests to multiple target network slices.

8A is a diagram of an exemplary communication system 500 in which one or more examples disclosed herein can be implemented. The communication system 500 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. Communication system 500 may enable multiple wireless users to access such content through sharing of system resources, including wireless bandwidth. For example, communication systems 500 include code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA ( One or more channel access methods such as orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), and the like can be employed.

Although it will be appreciated that the disclosed embodiments take into account any number of WTRUs, base stations, networks and/or network components, as shown in FIG. 8A, the communication system 500 is configured to transmit and receive a wireless transmission/reception unit ( Wireless transmit/receive units (WTRUs) 502a, 502b, 502c, and/or 502d (which may collectively or collectively be referred to as WTRU 502), radio access network (RAN) 503 /504/505), core network 506/507/509, public switched telephone network (PSTN) 508, internet 510, and other networks 512. Each of the WTRUs 502a, 502b, 502c, and/or 502d may be any type of device configured to operate and/or communicate in a wireless environment. By way of example, WTRUs 502a, 502b, 502c, and/or 502d may be configured to transmit and/or receive wireless signals, and may include user equipment (UE), mobile station, fixed or mobile subscriber unit, wireless Pagers, cellular phones, personal digital assistants (PDAs), smart phones, laptops, netbooks, personal computers, wireless sensors, consumer electronics, and the like.

Communication system 500 may also include a base station 514a and a base station 514b. Each of the base stations 514a, 514b, WTRUs to enable access to one or more communication networks, such as the core network 506/507/509, the Internet 510, and/or networks 512. It can be any type of device configured to wirelessly interface with at least one of (502a, 502b, 502c, and/or 502d). As an example, base stations 514a and/or 514b may include a base transceiver station (BTS), node B, eNode B, home node B, home eNode B, site controller, access point (AP), Wireless routers, and the like. Although base stations 514a, 514b are each shown as a single component, it can be seen that base stations 514a, 514b can include any number of interconnected base stations and/or network components. will be.

Base station 514a may also include other base stations and/or network components (not shown), such as a base station controller (BSC), radio network controller (RNC), relay nodes, and the like. It can be part of the RAN (503 / 504 / 505). Base station 514a and/or base station 514b may be configured to transmit and/or receive wireless signals within a particular geographic area that may be referred to as a cell (not shown). The cell can be further divided into cell sectors. For example, the cell associated with the base station 514a can be divided into three sectors. Thus, in one embodiment, the base station 514a may include three transceivers, one transceiver for each sector of the cell. In another embodiment, the base station 514a may employ multiple input multiple output (MIMO) technology, and accordingly, may use multiple transceivers for each sector of the cell.

Base stations 514a and/or 514b may be any suitable wireless communication link (eg, radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, etc.). Capable of communicating with one or more of the WTRUs 502a, 502b, 502c, and/or 502d through the air interface 515/516/517. The radio interface 515/516/517 can be established using any suitable radio access technology (RAT).

More specifically, as mentioned above, the communication system 500 can be multiple access systems and can employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 514a and WTRUs 502a, 502b, and/or 502c of the RAN 503/504/505 utilize a wideband CDMA (WCDMA) wide interface CDMA (515/516/517). It is possible to implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Advanced HSPA (HSPA+). HSPA may include High-Speed Downlink Packet Access (HSDPA) and/or High-Speed Uplink Packet Access (HSUPA).

In another embodiment, the base station 514a and the WTRUs 502a, 502b, and/or 502c are configured for Long Term Evolution (LTE) and/or LTE-A (LTE-Advanced). It is possible to implement a radio technology such as Evolutionary UMTS Terrestrial Radio Access (E-UTRA) that can establish a radio interface 515/516/517.

In other embodiments, the base station 514a and WTRUs 502a, 502b, and/or 502c are IEEE 802.16 (ie, Worldwide Interoperability for Microwave Access (WiMAX)), CDMA 2000, CDMA 2000 1X, CDMA 2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Wireless technologies such as Enhanced Data Rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like can be implemented.

The base station 514b of FIG. 8A can be, for example, a wireless router, a home Node B, a home eNode B, or an access point, to enable wireless connectivity in local areas such as a business office, home, car, campus, etc. Any suitable RAT can be used. In one embodiment, base station 514b and WTRUs 502c and 502d may implement a wireless technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In another embodiment, base station 514b and WTRUs 502c, 502d may implement a wireless technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In another embodiment, base station 514b and WTRUs 502c, 502d are cellular based RATs (eg, WCDMA, CDMA 2000, GSM, LTE, LTE-) to establish picocells or femtocells. A, etc.). 8A, the base station 514b can be directly connected to the Internet 510. Thus, the base station 514b may not need to access the Internet 510 through the core network 506/507/509.

The RAN 503/504/505 provides voice over internet protocol (VoIP) services to WTRUs 502a, 502b, 502c, and/or 502d using voice, data, applications, and/or Internet protocols. It can communicate with the core network (506/507/509), which may be any type of network configured to provide to one or more of. For example, the core network 506/507/509 provides call control, billing services, mobile location-based services, prepaid calls, Internet connectivity, video distribution, and/or high-level security functions such as user authentication. It can be done. Although not shown in FIG. 8A, the RAN 503/504/505 and/or the core network 506/507/509 are different from other RANs adopting the same RAT or different RAT as the RAN 503/504/505. It can communicate directly or indirectly. For example, in addition to being connected to a RAN (503/504/505) that can use E-UTRA wireless technology, the core network (506/507/509) also communicates with another RAN (not shown) that adopts GSM wireless technology. Can communicate.

The core network 506/507/509 is a gateway for allowing WTRUs 502a, 502b, 502c, and/or 502d to access the PSTN 508, the Internet 510, and/or other networks 512. It can also play a role. The PSTN 508 may include circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet 510 is such as a transmission control protocol (TCP), a user datagram protocol (UDP), and an Internet protocol (IP) of the TCP/IP Internet protocol suite. And a global system of interconnected computer networks and devices using common communication protocols. The networks 512 may include wired or wireless communication networks owned and/or operated by other service providers. For example, networks 512 may include another core network coupled to one or more RANs that may adopt the same RAT or different RAT as RAN 503/504/505.

Some or all of the WTRUs 502a, 502b, 502c, and/or 502d of the communication system 500 may include multi-mode capabilities, that is, WTRUs 502a, 502b, 502c, and/or 502d ) May include multiple transceivers to communicate with multiple wireless networks over multiple wireless links. For example, the WTRU 502c shown in FIG. 8A may be configured to communicate with a base station 514a that can employ cellular-based radio technology and a base station 514b that can employ IEEE 802 radio technology.

8B shows a schematic diagram of an exemplary WTRU 502. 8B, the WTRU 502 includes a processor 518, a transceiver 520, a transmit/receive component 522, a speaker/microphone 524, a keypad 526, a display/touchpad 528. ), non-removable memory 530, removable memory 532, power source 534, global positioning system (GPS) chipset 536, and other peripheral devices ( 538). It will be appreciated that the WTRU 502 can include any sub-combination of the components described above while maintaining consistency with the embodiment. Further, embodiments are not limited to, but not limited to, base stations 514a and 514b, in particular, base station (BTS), node B, site controller, access point (AP), home node B, evolved home node B Nodes that base stations 514a and 514b can represent, such as (eNodeB; evolved home node-B), home evolved node-B (HeNB), home evolved node B gateway, and proxy nodes It is contemplated that it may include some or all of the components shown in FIG. 8B and described herein.

The processor 518 includes a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, and a custom semiconductor (ASIC; Applicaton Specific Integrated Circuit), Field Programmable Gate Array (FPGA) circuit, any other type of integrated circuit (IC), state machine, and the like. The processor 518 may perform signal coding, data processing, power control, input/output processing, and/or any other function to enable the WTRU 502 to operate in a wireless environment. The processor 518 can be coupled to a transceiver 520 that can be coupled to a transmit/receive component 522. Although FIG. 8B shows the processor 518 and the transceiver 520 as separate components, it can be seen that the processor 518 and the transceiver 520 can be integrated together in an electronic package or chip.

The transmit/receive component 522 may be configured to transmit signals to or receive signals from a base station (eg, base station 514a) via a wireless interface 515/516/517. You can. For example, in one embodiment, the transmit/receive component 522 may be an antenna configured to transmit and/or receive RF signals. In another embodiment, the transmit/receive component 522 can be, for example, an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals. In another embodiment, the transmit/receive component 522 can be configured to transmit and receive both RF and optical signals. It will be appreciated that the transmit/receive component 522 can be configured to transmit and/or receive any combination of wireless signals.

In addition, although the transmit/receive component 522 is shown as a single component in FIG. 8B, the WTRU 502 can include any number of transmit/receive components 522. More specifically, WTRU 502 may employ MIMO technology. Thus, in one embodiment, the WTRU 502 sends two or more transmit/receive components 522 (eg, multiple antennas) to transmit and receive wireless signals over the air interface 515/516/517. It may include.

Transceiver 520 may be configured to modulate signals to be transmitted by transmit/receive component 522 and to demodulate signals received by transmit/receive component 522. As described above, WTRU 502 may have multi-mode capabilities. Accordingly, the transceiver 520 may include multiple transceivers to enable the WTRU 502 to communicate via multiple RATs, such as UTRA and IEEE 802.11, for example.

The processor 518 of the WTRU 502 may include a speaker/microphone 524, a keypad 526, and/or a display/touchpad 528 (eg, a liquid crystal display (LCD) display unit or organic light emitting diode) (OLED; organic light-emitting diode) display unit, and receive user input data therefrom. Processor 518 may also output user data to speaker/microphone 524, keypad 526, and/or display/touchpad 528. Further, processor 518 may access information from any type of suitable memory, such as non-removable memory 530 and/or removable memory 532 and store data in any type of suitable memory. The non-removable memory 530 may include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 532 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 518 accesses information from a memory that is not physically located on the WTRU 502, for example, on a server or home computer (not shown), and stores data in the memory. Can be saved.

Processor 518 may receive power from power source 534 and may be configured to distribute and/or control power to other components of WTRU 502. The power supply 534 can be any suitable device for powering on the WTRU 502. For example, the power source 534 may include one or more batteries (eg, nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, Fuel cells, and the like.

The processor 518 can also be coupled to a GPS chipset 536 that can be configured to provide location information (eg, longitude and latitude) regarding the current location of the WTRU 502. In addition to or instead of information from the GPS chipset 536, the WTRU 502 receives location information from the base station (eg, base stations 514a, 514b) via the air interface 515/516/517. And/or determine their location based on timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 502 can acquire location information in any suitable location determination method while maintaining consistency with the embodiment.

The processor 518 can also be coupled to other peripherals 538 that can include one or more software and/or hardware modules that provide additional features, functionality, and/or wired or wireless connectivity. For example, peripherals 538 include accelerometers, e-compasses, satellite transceivers, digital cameras (for photos or videos), universal serial bus (USB) ports, vibration devices, television transceivers, hands-free headsets, Bluetooth ^® Modules, frequency modulated (FM) wireless units, digital music players, media players, video game player modules, Internet browsers, and the like.

8C shows a schematic diagram of the RAN 503 and the core network 506 according to an embodiment. As previously mentioned, the RAN 503 can employ UTRA radio technology to communicate with the WTRUs 502a, 502b, and/or 502c through the air interface 515. The RAN 503 can also communicate with the core network 506. As shown in FIG. 8C, the RAN 503 includes Node Bs (which may each include one or more transceivers to communicate with the WTRUs 502a, 502b, and/or 502c via the air interface 515) 540a, 540b, and/or 540c). Node Bs 540a, 540b, and/or 540c may each be associated with a particular cell (not shown) within RAN 503. The RAN 503 may also include RNCs 542a and/or 542b. It will be appreciated that the RAN 503 can include any number of Node Bs and RNCs while maintaining consistency with the embodiment.

As shown in FIG. 8C, node Bs 540a and/or 540b may communicate with RNC 542a. Additionally, node B 540c may communicate with RNC 542b. Node Bs 540a, 540b, and/or 540c may communicate with respective RNCs 542a, 542b via the Iub interface. The RNCs 542a and 542b can communicate with each other through the Iur interface. Each of the RNCs 542a, 542b can be configured to control each of the Node Bs 540a, 540b, and/or 540c to which they are connected. In addition, each of the RNCs 542a, 542b performs other functions such as outer loop power control, load control, admission control, packet scheduling, handover control, macrodiversity, security functions, data encryption, or the like. It can be configured to support.

The core network 506 illustrated in FIG. 8C includes a media gateway (MGW) 544, a mobile switching center (MSC) 546, and a serving GPRS support node (SGSN). 548, and/or a gateway GPRS support node (GGSN) 550. Although each of the aforementioned components is shown as part of the core network 506, it will be appreciated that any one of these components may be owned and/or operated by an entity other than the core network operator. .

The RNC 542a of the RAN 503 may be connected to the MSC 546 of the core network 506 through the IuCS interface. The MSC 546 can be connected to the MGW 544. MSC 546 and MGW 544, such as PSTN 508, to enable communication between WTRUs 502a, 502b, and/or 502c with conventional land-line communication devices. Access to circuit switched networks may be provided to WTRUs 502a, 502b, and/or 502c.

The RNC 542a of the RAN 503 may also be connected to the SGSN 548 of the core network 506 via the IuPS interface. SGSN 548 may be connected to GGSN 550. SGSN 548 and GGSN 550 are for packet-switched networks such as the Internet 510, to enable communication between WTRUs 502a, 502b, and/or 502c and IP-enabled devices. Access may be provided to WTRUs 502a, 502b, and/or 502c.

As previously mentioned, the core network 506 may also be connected to networks 512 that may include other wired or wireless networks owned and/or operated by other service providers.

8D shows a schematic diagram of the RAN 504 and the core network 507 according to an embodiment. As previously mentioned, the RAN 504 can employ E-UTRA radio technology to communicate with the WTRUs 502a, 502b, and/or 502c through the air interface 516. The RAN 504 can also communicate with the core network 507.

It will be understood that RAN 504 may include any number of eNode Bs while maintaining consistency with the embodiment, but RAN 504 includes eNode Bs 560a, 560b, and/or 560c. can do. The eNode Bs 560a, 560b, and/or 560c may each include one or more transceivers to communicate with the WTRUs 502a, 502b, and/or 502c via the air interface 516. In one embodiment, eNode Bs 560a, 560b, and/or 560c may implement MIMO technology. Thus, eNode B 560a may use multiple antennas, for example, to transmit wireless signals to WTRU 502a and to receive wireless signals from WTRU 502a.

Each of the eNode Bs 560a, 560b, and/or 560c may be associated with a specific cell (not shown), and scheduling radio resource management decisions, handover decisions, users of the uplink and/or downlink And the like. As shown in FIG. 8D, e-node Bs 560a, 560b, and/or 560c may communicate with each other through an X2 interface.

The core network 507 illustrated in FIG. 8D may include a mobility management gateway (MME) 562, a service provision gateway 564, and a packet data network (PDN) gateway 566. Although each of the aforementioned components is shown as part of the core network 507, it will be appreciated that any one of these components may be owned and/or operated by an entity other than the core network operator. .

The MME 562 may be connected to each of the e-Node Bs 560a, 560b, and/or 560c of the RAN 504 through the S1 interface and may act as a control node. For example, the MME 562 may be configured for a specific service provisioning gateway during authentication of users of the WTRUs 502a, 502b, and/or 502c, bearer activation/deactivation, and initial attachment of the WTRUs 502a, 502b, and/or 502c. Can take responsibility for choices, etc. The MME 562 can also provide a control area function for switching between the RAN 504 and other RANs (not shown) employing other radio technologies such as GSM or WCDMA.

The service provision gateway 564 may be connected to each of the eNode Bs 560a, 560b, and/or 560c of the RAN 504 through the S1 interface. The service provisioning gateway 564 can route and forward user data packets globally to/from the WTRUs 502a, 502b, and/or 502c. The service provisioning gateway 564 secures user areas during handover between eNode Bs, triggers paging when downlink data is available for WTRUs 502a, 502b, and/or 502c, WTRU Other functions may also be performed, such as managing and storing the contexts of fields 502a, 502b, and/or 502c.

The service delivery gateway 564 provides access to packet-switched networks, such as the Internet 510, to the WTRU, to enable communication between the WTRUs 502a, 502b, and/or 502c and IP-enabled devices. It may also be connected to a PDN gateway 566 that may provide to fields 502a, 502b, and/or 502c.

The core network 507 may enable communication with other networks. For example, the core network 507 accesses circuit switched networks, such as the PSTN 508, to enable communication between WTRUs 502a, 502b, and/or 502c and conventional terrestrial communication devices. Can be provided to WTRUs 502a, 502b, and/or 502c. For example, the core network 507 may include an IP gateway (eg, an IP multimedia subsystem (IMS) server) that serves as an interface between the core network 507 and the PSTN 508, or Or you can communicate with that IP gateway. In addition, the core network 507 provides access to the networks 512, which may include other wired or wireless networks owned and/or operated by other service providers, WTRUs 502a, 502b, and/or 502c. ).

8E shows a schematic diagram of the RAN 505 and the core network 509 according to an embodiment. The RAN 505 may be an access service network (ASN) that employs IEEE 802.16 wireless technology to communicate with the WTRUs 502a, 502b, and/or 502c via the air interface 517. As discussed further below, communication links between various functional entities of WTRUs 502a, 502b, and/or 502c, RAN 505, and core network 509 may be defined as reference points. .

It will be appreciated that the RAN 505 can include any number of base stations and ASN gateways while maintaining consistency with the embodiment, but as shown in FIG. 8E, the RAN 505 can be used as the base stations 580a, 580b, and/or 580c) and ASN gateway 582. Base stations 580a, 580b, and/or 580c may be associated with a particular cell (not shown) of RAN 505, respectively, and WTRUs 502a, 502b, and/or 502c through air interface 517 ) To include one or more transceivers. In one embodiment, base stations 580a, 580b, and/or 580c may implement MIMO technology. Thus, the base station 580a can use multiple antennas, for example, to transmit wireless signals to the WTRU 502a and receive wireless signals from the WTRU 502a. Base stations 580a, 580b, and/or 580c may also provide mobility management functions such as handoff triggering, tunnel establishment, radio resource management, traffic classification, quality of service (QoS) policy enforcement, and the like. The ASN gateway 582 can serve as a traffic integration point, and can be responsible for paging, caching of subscriber profiles, routing to the core network 509, and the like.

The air interface 517 between the WTRUs 502a, 502b, and/or 502c and the RAN 505 may be defined as an R1 reference point that implements the IEEE 802.16 specification. In addition, each of the WTRUs 502a, 502b, and/or 502c may establish a logical interface (not shown) with the core network 509. The logical interface between WTRUs 502a, 502b, and/or 502c and core network 509 can be defined as an R2 reference point that can be used for authentication, authorization, IP host configuration management, and/or mobility management. have.

The communication link between each of the base stations 580a, 580b, and/or 580c may be defined as an R8 reference point that includes protocols to enable WTRU handover and data transmission between base stations. The communication link between base stations 580a, 580b, and/or 580c and ASN gateway 582 may be defined as an R6 reference point. The R6 reference point may include protocols to enable mobility management based on mobility events associated with respective WTRUs 502a, 502b, and/or 502c.

8E, the RAN 505 can be coupled to the core network 509. The communication link between the RAN 505 and the core network 509 may be defined as an R3 reference point, including protocols for enabling data transmission and mobility management capabilities, for example. The core network 509 includes a mobile IP home agent (MIP-HA) 584, an authentication, authorization, accounting (AAA) server 586, and a gateway 588. can do. Although each of the aforementioned components is shown as part of the core network 509, it will be appreciated that any one of these components may be owned and/or operated by an entity other than the core network operator.

MIP-HA may be responsible for IP address management and may allow WTRUs 502a, 502b, and/or 502c to roam between multiple ASNs and/or multiple core networks. MIP-HA 584 provides WTRU access to packet-switched networks, such as Internet 510, to enable communication between WTRUs 502a, 502b, and/or 502c and IP-enabled devices. Field 502a, 502b, and/or 502c. The AAA server 586 may be responsible for user authentication and support of user services. The gateway 588 may enable interworking with other networks. For example, gateway 588 provides access to circuit switched networks, such as PSTN 508, to enable communication between WTRUs 502a, 502b, and/or 502c and conventional terrestrial communication devices. WTRUs 502a, 502b, and/or 502c. In addition, gateway 588 provides access to WTRUs 502a, 502b, and/or 502c to networks 512 that may include other wired or wireless networks owned and/or operated by other service providers. ).

Although not shown in FIG. 8E, the RAN 505 can be connected to other ASNs and the core network 509 can be connected to other core networks. The communication link between RAN 505 and other ASNs, see R4, which may include protocols to coordinate the mobility of WTRUs 502a, 502b, and/or 502c between RAN 505 and other ASNs. Can be defined as points. The communication link between the core network 509 and other core networks may be defined as an R5 reference point, which may include protocols to enable interworking between home core networks and visited core networks.

Although the features and components have been described above in specific combinations, one of ordinary skill in the art may use each feature or component alone or in any combination with other features and components. You will see that you can. In addition, the methods described herein may be implemented as computer programs, software, or firmware integrated in a computer readable medium for execution by a computer or processor. Examples of computer readable media may include electronic signals (transmitted over wired or wireless connections) and computer readable storage media. Examples of computer readable storage media include, but are not limited to, magnetic media such as read only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, internal hard disks and removable disks, Magneto-optical media, and optical media such as CD-ROM disks and digital versatile disks (DVDs). The processor associated with the software can be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

Claims (15)

In the method implemented by a wireless transmit/receive unit (WTRU),
Receiving network slice selection policy information from a network, wherein the network slice selection policy information indicates one or more target network slices for one or more services to be used by the WTRU;
Initiating a connection to at least one of the one or more services indicated by the network slice selection policy information; And
Transmitting a connection request to the network, wherein the connection request is associated with the at least one service of the one or more services, and the connection request is the at least one service of the one or more services among the one or more target network slices Indicating a target slice to provide, wherein the target slice is selected based on the network slice selection policy information, the transmitting step
A method implemented by a wireless transmit/receive unit (WTRU). According to claim 1,
The network slice selection policy information is also indicative of radio access network information for the one or more target network slices, a method implemented by a wireless transmit/receive unit (WTRU). According to claim 1,
Providing slice assistance information to the network, wherein the slice assistance information indicates the at least one service among the one or more services to be used by the WTRU;
And further comprising a wireless transmit/receive unit (WTRU). According to claim 3,
The slice assistance information is provided by an attach message, a method implemented by a wireless transmit/receive unit (WTRU). According to claim 1,
Receiving an indication of one or more allowed network slices from the network
And further comprising a wireless transmit/receive unit (WTRU). The method of claim 5,
The target slice is selected based on the indication of the one or more allowed network slices, the method implemented by a wireless transmit/receive unit (WTRU). According to claim 1,
The connection comprises a packet data network (PDN) connection, wherein the connection request comprises a PDN connection request, a method implemented by a wireless transmit/receive unit (WTRU). A wireless transmit/receive unit (WTRU),
Receive network slice selection policy information from the network, wherein the network slice selection policy information indicates one or more target network slices for one or more services to be used by the WTRU;
Initiate a connection to at least one of the one or more services indicated by the network slice selection policy information;
Connection request to the network-the connection request is associated with the at least one of the one or more services, and the connection request is a target slice to provide the at least one of the one or more services among the one or more target network slices And the target slice is selected based on the network slice selection policy information.
A wireless transmit/receive unit (WTRU) configured. The method of claim 8,
The network slice selection policy information also indicates radio access network information for the one or more target network slices, wireless transmit/receive unit (WTRU). The method of claim 8,
The WTRU is further configured to provide slice assistance information to the network, wherein the slice assistance information indicates the at least one service among the one or more services to be used by the WTRU. The method of claim 10,
The slice assistance information is provided as an attach message, a wireless transmit/receive unit (WTRU). The method of claim 10,
The slice assistance information includes an identifier for the target slice, a wireless transmit/receive unit (WTRU). The method of claim 8,
The WTRU is further configured to receive an indication of one or more allowed network slices from the network, WTRU. The method of claim 13,
The target slice is selected based also on an indication of the one or more allowed network slices, WTRU. The method of claim 8,
The connection includes a packet data network (PDN) connection, and the connection request comprises a PDN connection request, a wireless transmit/receive unit (WTRU).

Images