Configuring Vertical Applications and Services with Route Descriptors

Abstract

Various aspects of the present disclosure relate to configuring vertical applications and services with route descriptors, such as network slice configuration. For example, NSCE functionality with an extended NSCE server can configure (or reconfigure) VAL applications / services with network slices or (e.g., without network slices) with route selection descriptors. The NSCE server can assist with VAL reconfiguration (including slice adaptation), extending the capabilities and usage of the NSCE functionality, among other benefits.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 63 / 337,935, filed May 3, 2022, and entitled “CONFIGURING VERTICAL APPLICATIONS AND SERVICES VIA ROUTE DESCRIPTORS,” which is incorporated by reference in its entirety.

[0002] The present disclosure relates to wireless communications, and more particularly to the configuration of vertical applications and services supported by a vertical application layer (VAL) of a wireless communications system. [Background technology]

[0003] A wireless communication system may include one or more network communication devices, such as base stations, which may be known by other names, eNodeB (eNB), next generation NodeB (gNB), or other suitable terminology. Each network communication device, such as a base station, may support wireless communication for one or more user communication devices, which may be known by other names, user equipment (UE), or other suitable terminology. A wireless communication system may support wireless communication with one or more user communication devices by using resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). Furthermore, a wireless communication system may support wireless communication over a variety of radio access technologies, including third generation (3G) radio access technologies, fourth generation (4G) radio access technologies, 5G radio access technologies, among other suitable radio access technologies beyond fifth generation (5G).

[0004] A service enabler architecture layer (SEAL) for verticals (e.g., vertical applications or services) implements network slice capability enablement (NSCE) to support slice reconfiguration for vertical applications and services. Slice reconfiguration may be based on an NSCE server configuration, and the NSCE server acts as an application function (AF) that influences UE Route Selection Policy (URSP) rules. The NSCE server can communicate with a Policy Control Function (PCF) node of the wireless communication system to provide guidance for route selection descriptors (e.g., single network slice selection assistance information (S-NSSAI) and data network name (DNN) information) as defined in 3rd Generation Partnership Project (3GPP®) Technical Specification (TS) 24.526. Summary of the Invention [Means for solving the problem]

[0005] The present disclosure relates to methods, apparatus, and systems that support configuring vertical applications and services with route descriptors, such as network slice configuration. For example, these methods, apparatus, and systems extend NSCE functionality to configure (or reconfigure) VAL applications / services with network slices or (e.g., without network slices) route selection descriptors via an NSCE server. The NSCE server can assist with VAL reconfiguration (including slice adaptation), extending the capabilities and uses of the NSCE functionality, among other benefits.

[0006] Some implementations of the methods and apparatus described herein may further include a network entity receiving a network slice configuration request for a vertical application, the network slice configuration request including an identifier of the vertical application, an identifier of a network route selection including one or more route selection descriptors of a network route for the vertical application, and a group identifier for a group of one or more user devices associated with the vertical application, and messaging the core network entity to trigger a network slice configuration for each user device of the group of one or more user devices associated with the vertical application and to adapt the route selection descriptors to the vertical application.

[0007] In some implementations of the methods and apparatus described herein, a network entity messages a PCF node of a wireless communication system to adapt a route selection descriptor to a vertical application.

[0008] In some implementations of the methods and apparatus described herein, the message for adapting the route selection descriptor to a vertical application includes a command to update one or more route selection policies for the vertical application when establishing a protocol data unit (PDU) session for the vertical application.

[0009] In some implementations of the methods and apparatus described herein, a network slice configuration request for a vertical application is received from a VAL client included by one or more user devices associated with the vertical application.

[0010] In some implementations of the methods and apparatus described herein, a network slice configuration request for a vertical application is received from a VAL server that communicates with a VAL client included by one or more user devices associated with the vertical application.

[0011] In some implementations of the methods and apparatus described herein, the network slice configuration request is part of a constrained application protocol (CoAP) message constructed with an application programming interface (API) uniform resource identifier (URI) that includes a value identifying the vertical application and a value identifying a configuration defining one or more route selection descriptors of a network route for the vertical application and a group identifier for one or more groups of user devices associated with the vertical application.

[0012] In some implementations of the methods and apparatus described herein, the network slice configuration request is part of a Constrained Application Protocol (CoAP) message constructed with an Application Programming Interface (API) Uniform Resource Identifier (URI) that includes a value identifying the vertical application and a value identifying a slice configuration that defines one or more route selection descriptors of a network route for the vertical application and a group identifier for one or more groups of user devices associated with the vertical application.

[0013] In some implementations of the methods and apparatus described herein, the network slice configuration request is part of a hypertext transfer protocol (HTTP) message that includes a request uniform resource identifier (URI) that identifies an entity of the vertical application, a configuration identifier that identifies a configuration identity, a group identifier that identifies a group of one or more user devices, a network route selection that includes one or more route selection descriptors, and a configuration reason that identifies the reason for the configuration represented by the configuration identity.

[0014] In some implementations of the methods and apparatus described herein, the network slice configuration request is part of a HyperText Transfer Protocol (HTTP) message that includes a request Uniform Resource Identifier (URI) that identifies an entity of the vertical application, a slice configuration identifier that identifies a configuration identity for a network slice associated with the vertical application, a group identifier that identifies a group of one or more user devices, a network route selection that includes one or more route selection descriptors, and a configuration reason that identifies the reason for the configuration represented by the configuration identity.

[0015] In some implementations of the methods and apparatus described herein, the network entity sends a network slice configuration response including information confirming the adaptation of the route selection descriptor to the vertical application.

[0016] In some implementations of the methods and apparatus described herein, one or more route selection descriptors of a network route for a vertical application include an S-NSSAI and DNN information.

[0017] Some implementations of the methods and apparatus described herein may further include a user device configured to provide a vertical application service profile for the vertical application from a VAL client of the user device to an NSCE client of the user device, and to send a network configuration request from the NSCE client of the user device to a network entity including the vertical application service profile.

[0018] In some implementations of the methods and apparatus described herein, the network configuration request includes a requested network slice for the vertical application or one or more route selection descriptors of a network route for the vertical application.

[0019] In some implementations of the methods and apparatus described herein, the network configuration request includes a request to map the vertical application to a network slice that is different from the current network slice to which the vertical application is mapped. [Brief description of the drawings]

[0020] [Figure 1] FIG. 1 illustrates an example of a wireless communication system that supports configuring vertical applications and services according to an aspect of the present disclosure. [Diagram 2]1 is an example diagram supporting composing vertical applications and services using NSCE, according to an embodiment of the present disclosure. [Figure 3A] FIG. 1 is an example diagram illustrating a pathway for composing vertical applications and services using an NSCE, according to an embodiment of the present disclosure. [Figure 3B] FIG. 1 is an example diagram illustrating a pathway for composing vertical applications and services using an NSCE, according to an embodiment of the present disclosure. [Figure 4] 1 is an example diagram of an NSCE that supports messaging between entities for configuring vertical applications and services, according to an embodiment of the present disclosure. [Diagram 5] FIG. 1 is an example diagram supporting a resource URI structure for Constrained Application Protocol (CoAP) messages, according to an aspect of the disclosure. [Figure 6] 1 is another example diagram of a system for supporting messaging between entities for configuring vertical applications and services using an NSCE, according to an embodiment of the present disclosure. [Figure 7] FIG. 11 is another example of a diagram supporting a resource URI structure for Constrained Application Protocol (CoAP) messages, according to an aspect of the disclosure. [Figure 8] 1 is a flowchart of a method for supporting network entities configuring vertical applications and services using an NSCE, according to an aspect of the disclosure. [Figure 9] 11 is another flow chart of a method for supporting network entities configuring vertical applications and services using an NSCE, according to an aspect of the disclosure. [Figure 10] 1 is an example block diagram of a device that supports configuring vertical applications and services using an NSCE, according to an embodiment of the disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0021] Although the SEAL for Verticals specification describes network slice capability enablement support when configuring network slices for vertical applications, the specification is limited to slice adaptation (e.g., covering adjustment of route selection descriptor S-NSSAI (and potentially DNN)) so that VAL services / applications can be set up by establishing the correct PDU sessions. Therefore, NSCE support is currently limited to responses to a single request type, namely slice adaptation requests.

[0022] However, the NSCE can support functionality in addition to slice adaptation operations when serving vertical applications and services. Thus, the systems, methods, and devices described herein provide a solution for using the NSCE for different functions or operations associated with vertical applications and services, such as vertical applications and services that use wireless communication systems via a VAL and associated SEAL (e.g., internet of things (IoT) systems, vehicle-to-everything (V2X) systems, etc.).

[0023] For example, the NSCE functionality provided by the NSCE server can configure (or reconfigure) VAL applications / services with network slices or (without network slices) route selection descriptors. Thus, the NSCE server can assist with VAL reconfiguration (including slice adaptation), enhancing the capabilities and usage of the NSCE functionality, among other benefits.

[0024] Aspects of the present disclosure are described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated and described with reference to the following device diagrams and flow charts relating to configuring vertical applications and services using NSCE functionality.

[0025] FIG. 1 illustrates an example of a wireless communication system 100 supporting configuration of vertical applications and services according to aspects of the disclosure. The wireless communication system 100 may include one or more base stations 102, one or more UEs 104, and a core network 106. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of a 4G network and a 5G network. The wireless communication system 100 may support radio access technologies beyond 5G. Additionally, the wireless communication system 100 may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0026] One or more base stations 102 (e.g., aggregator nodes) may be distributed in a geographic region to form a wireless communication system 100. One or more of the base stations 102 described herein may be or include or be referred to as a base transceiver station, access point, Node B, eNode B (eNB), next generation Node B (gNB), or other suitable terminology. The base stations 102 and the UEs 104 may communicate over a communication link 108, which may be a wireless or wired connection. For example, the base stations 102 and the UEs 104 may communicate wirelessly over a Uu interface.

[0027] A base station 102 may provide a geographic coverage area 110 for which the base station 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area 110. For example, the base station 102 and the UEs 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or more radio access technologies. In some implementations, the base station 102 may be mobile, for example, a satellite associated with a non-terrestrial based network. In some implementations, different geographic coverage areas 110 associated with the same or different radio access technologies may overlap, although different geographic coverage areas 110 may be associated with different base stations 102. Information and signals described herein may be represented using any of a wide variety of technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols and chips that may be referenced throughout this description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0028] One or more UEs 104 (e.g., sensor nodes) may be distributed in a geographical region of the wireless communication system 100. The UEs 104 may include or be referred to as a mobile device, a wireless device, a remote device, a handheld device, a user device, or a subscriber device, or some other suitable terminology. In some implementations, the UEs 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally or alternatively, the UEs 104 may be referred to as an Internet of Things (IoT) device, an Internet-of-Everything (IoE) device, or a machine-type communication (MTC) device, and / or any other device associated with a vertical application or service, among other examples. In some implementations, the UEs 104 may be stationary within the wireless communication system 100. In some other implementations, the UEs 104 may be mobile within the wireless communication system 100.

[0029] One or more UEs 104 may be devices of different shapes or with different capabilities. Several examples of UEs 104 are shown in FIG. 1. The UE 104 may be capable of communicating with various types of devices, such as base stations 102, other UEs 104, or network equipment (e.g., a core network 106, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment) as shown in FIG. 1. Additionally or alternatively, the UE 104 may support communication with other base stations 102 or UEs 104, which may act as relays in the wireless communication system 100.

[0030] The UE 104 may also be capable of supporting direct wireless communication with other UEs 104 via the communication link 112. For example, the UE 104 may support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V), vehicle-to-exchange (V2X), or cellular V2X deployments, the communication link 112 may be referred to as a sidelink. For example, the UE 104 may support direct wireless communication with another UE 104 via a PC5 interface.

[0031] The base stations 102 may support communication with the core network 106 or with other base stations 102, or both. For example, the base stations 102 may interface with the core network 106 through one or more backhaul links 114 (e.g., via an S1, N2, or another network interface). The base stations 102 may communicate with each other through the backhaul links 114 (e.g., by an X2, Xn, or another network interface). In some implementations, the base stations 102 may communicate with each other directly (e.g., between the base stations 102). In some other implementations, the base stations 102 may communicate with each other or indirectly (e.g., via the core network 106). In some implementations, one or more base stations 102 may include sub-components such as an access network entity, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 through one or more other access network transmission entities, which may be referred to as radio heads, smart radio heads, or transmit receive points (TRPs).

[0032] The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an Evolved Packet Core (EPC) or 5G Core (5GC), which may include a control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) that manages access and mobility, as well as a user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) that routes packets or interconnects to external networks. In some implementations, the control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for one or more UEs 104 served by one or more base stations 102 associated with the core network 106.

[0033] 2 illustrates an example diagram supporting configuring vertical applications and services using NSCE, according to an embodiment of the disclosure. The diagram provides a functional model or system 200 for an NSCE. A VAL UE 210 (e.g., an IoT device, a V2X device, or another VAL user device) includes a VAL client 220 and an NSCE client 230. The VAL client 220 communicates via a VAL, and the NSCE client 230 communicates via a SEAL.

[0034] The NSCE client 230 communicates with the NSCE server 250 over the NSCE-UU reference point. The NSCE client 230 provides support for NSCE functionality to the VAL client 220 (or multiple clients) over the NSCE-C reference point. The VAL server 240 (or server) communicates with the NSCE server 250 over the NSCE-S reference point. In some cases, the NSCE server 250 is deployed within a 5G system domain or core network.

[0035] The NSCE server 250 may act as an application (AF) and communicate with the 5G core network 260 via a network exposure function (NEF) (N33) reference point for interaction with PCF nodes of the core network 260. The functional model 200 facilitates the VAL server 240 or the VAL UE 210 to trigger a slice configuration request, which is performed by a network entity (e.g., the NSCE server 250). However, the current specification for the functional model 200 only addresses adaptation as a configuration for VAL applications and services. Thus, extensions of the functional model 200 can facilitate other configuration capabilities for the VAL UE 210 and associated vertical applications and services, as described herein.

[0036] 3A-3B illustrate example diagrams illustrating paths for configuring vertical applications and services using NSCEs, according to aspects of the disclosure. The paths illustrate or represent extending the functional model 200 to provide additional configuration capabilities for vertical applications and services (e.g., in addition to or in conjunction with slice adaptation).

[0037] For example, Figure 3A shows a first structure 300 in which a VAL application / service 310 is configured / reconfigured by a network slice (or other route selection descriptor) 320. A network slice, or slice, may be an independent virtualization instance defined by an allocation of a subset of available network resources, such as network resources allocated to a particular vertical application or service (e.g., one slice is allocated to a virtual reality application and another slice is allocated to a V2X application). The reconfiguration of the VAL application / service 310 uses an adaptation 330 of the network slice configuration (or other route selection descriptor) 320.

[0038] As another example, Figure 3B shows a second structure 335, in which the VAL application / service 340 is configured / reconfigured by any route selection descriptor 350. The reconfiguration then uses slice adaptation 360 (or other route selection descriptor, such as DNN). Thus, the reconfiguration performed by the structure 335 does not always use network slices, although slices may be used during slice adaptation 360. Further details regarding messaging procedures of the structure 300 and the structure 335 are described herein.

[0039] 4 illustrates an example diagram 400 supporting messaging between entities for configuring vertical applications and services using NSCEs, according to an aspect of the disclosure. A VAL server 410, or an NSCE client (where the NSCE client has a new service profile for a VAL application / service by the VAL client), sends a network slice configuration request 432 to an NSCE server 420 for the VAL application (and a VAL UE within or associated with the VAL application / service).

[0040] The network slice configuration request 432 includes information identifying a requested network slice and / or other route selection descriptor (e.g., DNN) for each VAL UE associated with the VAL application. In some cases, the request 432 includes a request to remap the VAL application / service to a different network slice and / or other route selection descriptor.

[0041] The NSCE server 420 processes the request 432 and triggers 434 network slice configuration for each VAL UE (e.g., identified by a VAL group identifier) ​​of the VAL application. The NSCE server 420 acts as an AF and provides an updated route selection descriptor (e.g., S-NSSAI, DNN, etc.) for each VAL UE. For example, the NSCE server 420 sends the updated route selection descriptor to the 5G core network node (e.g., PCF) 430 at 436 by the network exposure function (NEF) as part of the AF-driven guidance for URSP determination to the 5G system. The guidance can update the route selection descriptor to indicate a different set of PDU session information (e.g., S-NSSA, DNN, etc.) that may be associated with a vertical application / service that matches the associated application data traffic.

[0042] If the route selection descriptor adaptation is successful, the NSCE server 420 may provide a network slice configuration response 438 to the VAL server 410, providing information or verifying that the PCF has completed network slice configuration (e.g., including slice adaptation) for the requesting VAL application / service.

[0043] In some embodiments, the messaging can be performed via HTTP, such as an HTTP POST message. For example, the VAL server 410 can send a network slice configuration request 432 via HTTP that includes the following information: A Request-URI to a URI identifying the origin (VAL server 410 or NSCE client) with the VAL application / service identity and the value of " / UE-triggered-slice-configuration" if requested by an NSCE client, or " / server-triggered-slice-configuration" if requested by a VAL server, A “Host” header field to the URI, identifying the NSCE server 420 and port information; and Parameters such as slice configuration ID set to the value "slice adaptation", the VAL UE of the VAL group ID, the requested slice, the requested DNN, and / or the slice configuration reason identified as S-NSSAI.

[0044] Table 1 presents the parameters (and associated descriptions) for the network slice configuration triggers.

[0045] [Table 1]

[0046] Upon receiving the request 432, the NSCE server 420 may attempt to update the network slice for one or more of the VAL UEs associated with the VAL Group ID for the VAL application / service identified by the VAL Service ID. The NSCE server 420 uses the parameters for the requested S-NSSAI and other possible requested route selection descriptors (e.g., DNNs) and slice configuration reasons from the HTTP message request to update the network slice.

[0047] In some embodiments, the messaging can be performed by CoAP, such as a CoAP POST message. For example, the VAL server 410 can send a network slice configuration request 432 by CoAP, including the following information: set "apiRoot" to the NSCE-server URI, "valServiceId" to a value identifying a given VAL application / service, "sliceConfigId" to a value identifying a network slice adaptation, and "slice-configuration" to include (1) the VAL group ID of a VAL group that contains one or more VAL UEs, (2) the requested S-NSSAI, and (3) other requested route selection descriptors, such as DNN, and the requested slice configuration reason; An Application Programming Interface (API) Uniform Resource Identifier (URI) by setting the "Uri-Host" and "Uri-Port" options to a URI that identifies the NSCE server 420 and associated port information: {apiRoot} / <apiname> / <apiversion> / val-services / {valServiceId} / slice-configuration / {sliceConfigId} A CoAP URI that identifies a network slice configuration for a given VAL group that contains one or more VAL UEs for a given VAL application / service.

[0048] Upon receiving the request 432, the NSCE server 420 may attempt to update the network slice for one or more VAL UEs associated with the VAL group ID for the VAL service identified by the VAL service ID by using parameters for the requested S-NSSAI and other possible requested route selection descriptors (e.g., DNN), as well as the slice configuration reason from the CoAP message request, send the updated S-NSSAI and any route selection descriptors, such as DNN, to the PCF, and send a CoAP 2.04 response message indicating adaptation of the requested network slice adaptation (or an error response for failure status) to the originator of the CoAP message (e.g., CoAP POST) request (the VAL server 410 or the NSCE client).

[0049] 5 illustrates an example of a diagram supporting a resource URI structure 500 for a Constrained Application Protocol (CoAP) message, according to an embodiment of the present disclosure. Additionally, Table 2 provides an overview of resources and applicable CoAP methods.

[0050] [Table 2]

[0051] As shown in Table 2, the slice configuration resource allows the NSCE client to send a request, which may be for slice adaptation, for a specific slice configuration identified by a slice configuration ID, including a group of one or more VAL UEs, a requested S-NSSAI, other possible requested route selection descriptors (e.g., DNNs), and a requested slice configuration reason for a specific VAL application / service identified by a VAL service ID to the NSCE server to perform network-triggered slice adaptation for a group of one or more VAL UEs for that specific VAL service.

[0052] Resource URI: {apiRoot} / etn-sa / <apiversion> / val-services / {valServiceId} / slice-configurations / {sliceConfigId} supports the resource URI variables defined as follows in Table 3 (and shown in Figure 5):

[0053] [Table 3]

[0054] The operation triggers a given slice adaptation to be performed for a group of one or more VAL UEs for a given VAL application / service provided by the NSCE server 420. The CoAP message request may be a CoAP POST request and may support the data structure shown in Table 4.

[0055] [Table 4]

[0056] A CoAP message response can support the data structures shown in Table 5.

[0057] [Table 5]

[0058] 6 illustrates another example diagram 600 supporting messaging between entities for configuring vertical applications and services using NSCEs according to an aspect of the disclosure. The VAL server 410, or an NSCE client (where the NSCE client has a new service profile for a VAL application / service by the VAL client), sends a network slice configuration request 612 to the NSCE server 420 for the VAL application (and the VAL UE within or associated with the VAL application / service).

[0059] The network slice configuration request 612 includes information identifying a requested network slice and / or other route selection descriptor (e.g., DNN) for each VAL UE associated with the VAL application. In some cases, the request 612 includes a request to remap the VAL application / service to a different network slice and / or other route selection descriptor.

[0060] The NSCE server 420 processes the request 612 and triggers 614 network slice configuration for each VAL UE (e.g., identified by a VAL group identifier) ​​of the VAL application. The NSCE server 420 acts as an AF and provides an updated route selection descriptor (e.g., S-NSSAI, DNN, etc.) for each VAL UE. For example, the NSCE server 420 sends the updated route selection descriptor to the 5G core network node (e.g., PCF) 430 by the network exposure function (NEF) at 616 as part of the AF-driven guidance for URSP determination to the 5G system. The guidance can update the route selection descriptor to indicate a different set of PDU session information (e.g., S-NSSA, DNN, etc.) that may be associated with a vertical application / service that matches the associated application data traffic.

[0061] If the route selection descriptor adaptation is successful, the NSCE server 420 may provide a network slice configuration response 618 to the VAL server 410, providing information or verifying that the PCF has completed network slice configuration (e.g., including slice adaptation) for the requesting VAL application / service.

[0062] As with the messaging described herein, in some embodiments, the messaging can be performed via HTTP, such as an HTTP POST message. For example, the VAL server 410 can send a network slice configuration request 612 via HTTP with a modified parameter "configuration ID" that identifies the configuration as independent of the slice configuration, as described herein.

[0063] Also, in some embodiments, messaging can be performed via CoAP, such as a CoAP POST message. For example, the VAL server 410 can send a network slice configuration request 612 via CoAP, as described herein, using a "configuration" resource rather than a "slice configuration" resource, and an associated resource URI structure. FIG. 7 illustrates another example of a diagram supporting a resource URI structure 700 for a Constrained Application Protocol (CoAP) message, according to aspects of the present disclosure. Additionally, Table 6 provides an overview of resources and applicable CoAP methods, illustrating the "configuration" resource.

[0064] [Table 6]

[0065] Thus, as described herein, different but related structures (structures 300 and 335) implement NSCE to support vertical application to slice adaptation and can be extended beyond slice adaptation to other configurations (including slice adaptation). For example, the structures can leverage, among other benefits, various messaging procedures and implementations by which slice adaptation can be extended to cover or from other configurations.

[0066] FIG. 8 illustrates a flowchart of a method 800 for supporting network entities configuring vertical applications and services using NSCEs, according to an aspect of the disclosure. The operations of method 800 may be performed by a device or components thereof as described herein. For example, the operations of method 800 may be performed by a device described with reference to FIG. 10. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may perform aspects of the described functions using dedicated hardware.

[0067] At 810, the method 800 may include receiving a network slice configuration request for a vertical application. For example, the NSCE server 420 may receive the request from the VAL server 410 or a VAL client. The operations of 810 may be performed according to examples described herein. In some implementations, aspects of the operations of 810 may be performed by a device described with reference to FIG.

[0068] At 820, the method 800 may include triggering a network slice configuration for one or more user devices. The operations of 820 may be performed according to examples described herein. In some implementations, aspects of the operations of 820 may be performed by a device described with reference to FIG.

[0069] At 830, the method 800 may include messaging a core network entity to adapt the route selection descriptor to the vertical application. The operations of 830 may be performed according to examples described herein. In some implementations, aspects of the operations of 830 may be performed by a device described with reference to FIG.

[0070] At 840, the method 800 may include transmitting a network slice configuration including confirmation of adaptation of the route selection descriptor. The operations of 840 may be performed according to examples described herein. In some implementations, aspects of the operations of 840 may be performed by a device described with reference to FIG.

[0071] As described herein, the VAL server 410, or a VAL client (e.g., a VAL client 220 in collaboration with an NSCE client 230 of a VAL UE 210), may generate and send a request to adapt a network slice to a vertical application / service associated with the VAL client.

[0072] FIG. 9 illustrates another flowchart of a method 900 for supporting network entities configuring vertical applications and services using NSCEs, according to an aspect of the disclosure. The operations of method 900 may be performed by a device or components thereof as described herein. For example, the operations of method 900 may be performed by a device described with reference to FIG. 10. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may perform aspects of the described functions using dedicated hardware.

[0073] At 910, the method 900 may include a step in which the VAL client provides the vertical application service profile to the NSCE client. The operations of 910 may be performed according to examples described herein. In some implementations, aspects of the operations of 910 may be performed by a device described with reference to FIG.

[0074] At 920, the method 900 may include the NSCE client sending a network configuration request to a network entity, such as the NSCE server 420. The operations of 920 may be performed according to examples described herein. In some implementations, aspects of the operations of 920 may be performed by a device described with reference to FIG.

[0075] At 930, the method 900 may include receiving a response from the network entity confirming the network configuration (e.g., route or network slice adaptation) for the vertical application. The operations of 930 may be performed according to examples described herein. In some implementations, aspects of the operations of 930 may be performed by a device described with reference to FIG.

[0076] FIG. 10 illustrates an example block diagram 1000 of a device 1002 supporting configuring vertical applications according to aspects of the disclosure. The device 1002 may be an example of an NSCE server 250 or 420 as described herein. The device 1002 may support wireless communication with one or more base stations 102, UEs 104, or any combination thereof. The device 1002 may include components for bidirectional communication, including components for transmitting and receiving communications, such as a communications manager 1004, a processor 1006, a memory 1008, a receiver 1010, a transmitter 1012, and an I / O controller 1014. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0077] The communications manager 1004, the receiver 1010, the transmitter 1012, or various combinations or components thereof may be examples of means for implementing various aspects of the disclosure described herein. For example, the communications manager 1004, the receiver 1010, the transmitter 1012, or various combinations or components thereof may support a method for implementing one or more of the functions described herein.

[0078] In some implementations, the communications manager 1004, the receiver 1010, the transmitter 1012, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing functions described in this disclosure. In some implementations, the processor 1006 and a memory 1008 coupled with the processor 1006 may be configured to perform one or more of the functions described herein (e.g., by the processor 1006 executing instructions stored in the memory 1008).

[0079] Additionally or alternatively, in some implementations, the communications manager 1004, the receiver 1010, the transmitter 1012, or various combinations or components thereof may be implemented in code executed by the processor 1006 (e.g., as communications management software or firmware). When implemented in code executed by the processor 1006, the functions of the communications manager 1004, the receiver 1010, the transmitter 1012, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in this disclosure).

[0080] In some implementations, the communications manager 1004 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with the receiver 1010, the transmitter 1012, or both. For example, the communications manager 1004 may be integrated to receive information from the receiver 1010, send information to the transmitter 1012, or in combination with the receiver 1010, the transmitter 1012, or both to receive information, transmit information, or perform various other operations described herein. Although the communications manager 1004 is shown as a separate component, in some implementations, one or more functions described with respect to the communications manager 1004 may be supported or performed by the processor 1006, the memory 1008, or any combination thereof. For example, the memory 1008 may store code that may include instructions executable by the processor 1006 to cause the device 1002 to perform various aspects of the disclosure described herein, or the processor 1006 and the memory 1008 may be otherwise configured to perform or support such operations.

[0081] For example, the communications manager 1004 may support wireless communications in a first device (e.g., device 1002) according to examples disclosed herein. The communications manager 1004 may be configured or otherwise support a means for configuring a vertical application using NSCE functionality. For example, the communications manager 1004 may receive a network slice configuration request for the vertical application, trigger a network slice configuration for each user device of a group of one or more user devices associated with the vertical application, and send a message to a core network entity, the message including a command to update one or more route selection policies for the vertical application when establishing a protocol data unit (PDU) session for the vertical application.

[0082] The processor 1006 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, the processor 1006 may be configured to operate a memory array using a memory controller. In some implementations, the memory controller may be integrated into the processor 1006. The processor 1006 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1008) to cause the device 1002 to perform various functions of the disclosure.

[0083] The memory 1008 may include random access memory (RAM) and read only memory (ROM). The memory 1008 may store computer-readable computer-executable code including instructions that, when executed by the processor 1006, cause the device 1002 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as a system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 1006, but may (e.g., when compiled and executed) cause a computer to perform functions described herein. In some implementations, the memory 1008 may include a basic input / output system (BIOS), which may control basic hardware or software operations, such as interactions with peripheral components or devices, among others.

[0084] The I / O controller 1014 may manage input and output signals for the device 1002. The I / O controller 1014 may also manage peripheral devices that are not integrated into the device 1002. In some implementations, the I / O controller 1014 may represent a physical connection or port to an external peripheral device. In some implementations, the I / O controller 1014 may use an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, the I / O controller 1014 may be implemented as part of a processor, such as the processor 1006. In some implementations, a user may interact with the device 1002 through the I / O controller 1014 or through hardware components controlled by the I / O controller 1014.

[0085] In some implementations, the device 1002 may include a single antenna 1016. However, in other implementations, the device 1002 may have two or more antennas 1016, which may be capable of simultaneously transmitting or receiving multiple wireless transmissions. The receiver 1010 and the transmitter 1012 may communicate bidirectionally via one or more antennas 1016, wired or wireless links as described herein. For example, the receiver 1010 and the transmitter 1012 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver may include a modem for demodulating packets received from the one or more antennas 1016 and for modulating the packets and providing the modulated packets to the one or more antennas 1016 for transmission.

[0086] In addition to supporting wireless communications at a first device, such as the NSCE server 250 or 420, the communications manager 1004, when implemented as part of the UE 104, can support wireless communications at a second device in accordance with examples disclosed herein. The communications manager 1004 may be configured or otherwise support a means for sending configuration requests for vertical applications. For example, the communications manager 1004 may provide a vertical application service profile for a vertical application from a VAL client of the user device to an NSCE client of the user device, and send a network configuration request including the vertical application service profile from the NSCE client of the user device to a network entity.

[0087] The various example blocks and components described with respect to the disclosure herein may be implemented or performed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0088] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or a combination thereof. When implemented in software executed by a processor, the functions may be stored on or transmitted via a computer-readable medium as one or more instructions or codes. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions may also be physically located in different locations, including being distributed such that parts of the functions are implemented in different physical locations.

[0089] Computer-readable media includes both non-transitory computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another. Non-transitory storage media may be any available medium that can be accessed by a general purpose or special purpose computer. By way of example and not limitation, non-transitory computer-readable media may include RAM, ROM, Electrically Erasable Programmable ROM (EEPROM), Flash memory, Compact Disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer or a general purpose or special purpose processor.

[0090] Any connection may be properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disk and disc include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blue-ray discs, where a disk typically reproduces data magnetically and a disc reproduces data optically with a laser. Combinations of the above are also included within the scope of computer-readable media.

[0091] As used herein, including in the claims, "or" used in a list of items (e.g., a list of items ending with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such as, for example, a list of at least one of A, B, or C means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). Also, the phrase "based on" as used herein should not be construed as a reference to a closed set of conditions. For example, an exemplary step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" is intended to be construed in the same manner as the phrase "based at least in part on." Additionally, as used herein, including in the claims, a "set" may include one or more elements.

[0092] The description set forth herein with respect to the accompanying drawings describes exemplary configurations and does not represent every example that may be implemented or that falls within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration" and does not mean "preferred" or "advantageous over other examples." The detailed description includes specific details for the purposes of providing an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

[0093] The description herein is provided to enable any person skilled in the art to make or use the disclosure. Various modifications of the disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein. [Explanation of symbols]

[0094] 100 Wireless communication system 102 Base station 104UE 106 Core Network 108 Communication Links 110 Geographic Coverage Areas 112 Communication Links 114 Backhaul Link 200 Function Models or Systems 210 VALUE 220 VAL Client 230 NSCE Clients 240 VAL Server 250 NSCE Servers 260 Core Network 300 First Structure 310 VAL Applications / Services 320 Network Slice 330 Adaptation 335 Second Structure 340 VAL Applications / Services 350 Route Selection Descriptor 360 Slice Adaptation 410 VAL Server 420 NSCE Server 430 5G core network nodes 432 Network Slice Configuration Request 434 Trigger 612 Network Slice Configuration Request 700 Resource URI Structure 1002 Devices 1004 Communications Manager 1006 Processor 1008 Memory 1010 Receiver 1012 Transmitter 1014 I / O Controller 1016 Antenna< / apiversion> < / apiversion> < / apiname>

Claims

1. A network entity for wireless communication, The system comprises at least one memory and at least one processor coupled to the at least one memory, the at least one processor being Receiving a network slice configuration request for a vertical application, wherein the network slice configuration request is: The identifier of the aforementioned vertical application, A network route selection identifier including one or more route selection descriptors for the network route for the aforementioned vertical application, and A group identifier for a group of one or more user devices associated with the aforementioned vertical application, Including receiving, Triggering a network slice configuration for each user device in the group of one or more user devices associated with the vertical application, Sending a message to the core network entity to adapt the aforementioned route selection descriptor to the vertical application The network entity is configured to perform the above action. Network entity.

2. The at least one processor is further configured to cause the network entity to message a policy control function (PCF) node of the wireless communication system to adapt the route selection descriptor to the vertical application. The network entity according to claim 1.

3. The network entity according to claim 1, wherein the message for adapting the route selection descriptor to the vertical application includes a command for updating one or more route selection policies for the vertical application when establishing a protocol data unit (PDU) session for the vertical application.

4. The network entity according to claim 1, wherein the network slice configuration request for the vertical application is received from a vertical application layer (VAL) client included by one or more user devices associated with the vertical application.

5. The network entity according to claim 1, wherein the network slice configuration request for the vertical application is received from a VAL server that communicates with vertical application layer (VAL) clients included by one or more user devices associated with the vertical application.

6. The aforementioned network slice configuration request is part of a Constrained Application Protocol (CoAP) message constructed by an Application Programming Interface (API) Uniform Resource Identifier (URI), where the URI is: A value that identifies the aforementioned vertical application, A value that identifies a configuration defining one or more route selection descriptors for the network route for the vertical application, and a group identifier for one or more user devices associated with the application. A network entity according to claim 1, including the network entity described in claim 1.

7. The aforementioned network slice configuration request is part of a Constrained Application Protocol (CoAP) message constructed by an Application Programming Interface (API) Uniform Resource Identifier (URI), where the URI is: A value that identifies the aforementioned vertical application, A value that identifies a slice configuration defining one or more route selection descriptors for the network route for the vertical application, and a group identifier for one or more user devices associated with the application. A network entity according to claim 1, including the network entity described in claim 1.

8. The aforementioned network slice configuration request is part of a hypertext transfer protocol (HTTP) message, and the HTTP message is: The requested uniform resource identifier (URI) that identifies the entity of the aforementioned vertical application, A configuration identifier that identifies the configuration identity, The group identifier of the one or more user devices, Network route selection including the one or more route selection descriptors, The reason for the configuration, which identifies the reason for the configuration represented by the aforementioned configuration identity, A network entity according to claim 1, including the network entity described in claim 1.

9. The aforementioned network slice configuration request is part of a hypertext transfer protocol (HTTP) message, and the HTTP message is: The requested uniform resource identifier (URI) that identifies the entity of the aforementioned vertical application, A slice configuration identifier that identifies the configuration identity for the network slice associated with the aforementioned vertical application, The group identifier of the one or more user devices, Network route selection including the one or more route selection descriptors, The reason for the configuration, which identifies the reason for the configuration represented by the aforementioned configuration identity, A network entity according to claim 1, including the network entity described in claim 1.

10. The aforementioned at least one processor is The network entity is further configured to cause the network entity to send a network slice configuration response that includes information confirming the adaptation of the route selection descriptor to the vertical application. The network entity according to claim 1.

11. The network entity according to claim 1, wherein the one or more route selection descriptors for the network route for the vertical application include single network slice selection assistance information (S-NSSAI) and data network name (DNN) information.

12. A method implemented by a network entity, The steps include receiving a network slice configuration request for a vertical application, The steps include triggering a network slice configuration for each user device in a group of one or more user devices associated with the vertical application, A step of sending a message to a core network entity, wherein the message includes a command to update one or more route selection policies for the vertical application when establishing a protocol data unit (PDU) session for the vertical application. Methods that include...

13. The aforementioned network slice configuration request is: The identifier of the aforementioned vertical application, A network route selection identifier that includes one or more route selection descriptors for network routes for the aforementioned vertical application, A group identifier for the group of one or more user devices associated with the vertical application and The method according to claim 12, including the method described in claim 12.

14. The method according to claim 12, wherein the message is configured to adapt one or more route selection descriptors to the vertical application.

15. The method according to claim 12, wherein the network slice configuration request is received by a Constrained Application Protocol (CoAP) message constructed by an Application Programming Interface (API) Uniform Resource Identifier (URI).

16. The method according to claim 12, wherein the network slice configuration request is received by a hypertext transfer protocol (HTTP) message.

17. A user device for wireless communication, The system comprises at least one memory and at least one processor coupled to the at least one memory, the at least one processor being The Vertical Application Layer (VAL) client of the user device provides a Vertical Application Service Profile for the Vertical Application to the Network Slice Capability Enable (NSCE) client of the user device. The NSCE client of the user device sends a network configuration request, including the vertical application service profile, to the network entity. The user device is configured to perform the action. User device.

18. The network configuration request includes one or more route selection descriptors for the requested network slice or network route for the vertical application. The user device according to claim 17.

19. The network configuration request includes a request to map the vertical application to a network slice different from the current network slice to which the vertical application is mapped. The user device according to claim 17.

20. A processor for wireless communication, It comprises at least one memory and at least one controller coupled to the at least one memory, and the at least one controller is The vertical application service profile for the vertical application is provided from the vertical application layer (VAL) client of the processor to the network slice capability enable (NSCE) client of the processor. The NSCE client of the processor sends a network configuration request, including the vertical application service profile, to the network entity. The processor is configured to perform the above action. Processor.

Images