Configuring network services to support applications

Abstract

Embodiments of systems and methods for configuring a network service to support an application may include launching an application that communicates with a network element to perform an application operation; sending a service request to a uniform resource locator (URL) associated with a data processing service that supports the application operation in response to launching the application, the service request configured to cause activation of the data processing service; and performing the application operation using a communication received from the network element and supported by the data processing service. In some embodiments, the service request may be automatically sent to the URL associated with the data processing service in response to launching the application. Activation of the data processing service may occur at the UE, in the communication network, or both. The application may be a portal application. The network element may include a network service provider.

Description

[Technical Field]

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS) This application claims priority to Greek Patent Application No. 20220100907, entitled "Configuring Network Services To Support An Application," filed November 7, 2022, and U.S. Non-Provisional Application No. 18 / 503,139, entitled "Configuring Network Services To Support An Application," filed November 6, 2023, the entire contents of which are incorporated herein by reference for all purposes. [Background technology]

[0002] 3rd Generation Partnership Project (3GPP®) Long Term Evolution (LTE), Fifth Generation (5G) New Radio (NR), and other communication technologies enable improved communication and data services. Endpoint computing devices can utilize the data processing and transport capabilities of 3GPP communication networks to send and receive various information that enables the operation of applications and services on the endpoint devices. To invoke and use such data processing and transport capabilities of a 3GPP communication network, endpoint computing devices and network elements must be instructed to perform operations to initiate or activate the data processing and transport capabilities of the network. Summary of the Invention

[0003] Various aspects include a method for configuring a network service to support an application, and a user equipment (UE) configured to perform the method. Various aspects may include launching an application that communicates with a network element to perform an application operation; in response to launching the application, sending a service request to a uniform resource locator (URL) associated with a data processing service supporting the application operation, the service request configured to cause activation of the data processing service; and performing the application operation using a communication received from the network element and supported by the data processing service. In some aspects, sending the service request to the URL associated with the data processing service supporting the application operation may include automatically sending the service request to the URL in response to launching the application.

[0004] Some aspects may include obtaining a URL from a communication network, the URL associated with a data processing service and the data service provided by the network element. In some aspects, activation of the data processing service may occur at the UE, at the communication network, or both. In some aspects, the application may be a portal application. In some aspects, the network element may include a network service provider.

[0005] In some aspects, automatically sending the service request to a URL associated with a data processing service supporting the application operation may include sending the service request to a URL of a network service handler function in the communications network, the service request being configured to be resolved by the network service handler function to initiate a network data processing service in the communications network.

[0006] Some aspects may include receiving a redirection message from a network service handler function in response to the service request, executing at the UE a media service application configured to receive a communication from the network element in response to the received redirection message, receiving by the media service application from the network element a communication supported by the network data processing service, and performing by the media service application an operation using the received communication to support the application operation. In some aspects, automatically directing the service request to a URL associated with the data processing service supporting the application operation may include resolving the URL associated with the data processing service using a UE service handler function executing on a processor of the UE, initiating at the UE a UE data processing service supporting the application operation, and executing at the UE a media service application configured to receive from the network element a communication supported by the UE data processing service.

[0007] In some aspects, performing an application operation using the received communication supported by the data processing service may include receiving the communication from a network service provider by the UE data processing service, providing the received communication to a media service application, and performing an operation by the media service application using the received communication to support the application operation. Some aspects may include activating a media application function by the UE service handler function.

[0008] In some aspects, automatically sending the service request to a network URL associated with a data processing service supporting the application operation may include resolving the URL associated with the data processing service using a UE service handler function executing on a processor of the UE, initiating at the UE the UE data processing service supporting the application operation, executing at the UE a media service application configured to receive communications from a network element, sending a second service request to a network service handler function in the communications network, the second service request configured to be resolved by the network service handler function to initiate the network data processing service in the communications network, and receiving by the media service application from the network element the network data processing service and the communications supported by the UE data processing service. In such aspects, performing the application operation using the received communications from the network element, the communications supported by the network data processing service and the UE data processing service may include performing an operation by the media service application using the received communications from the network element, the received communications supported by the network data processing service and the UE data processing service. Some aspects may include sending a request for service parameters associated with the data processing service from a UE service handler function to a network service handler function, receiving the service parameters from the network service handler function, and configuring the UE data processing service based on the received service parameters.

[0009] Further aspects include a UE having a processor configured to perform one or more operations of any of the methods summarized above. Further aspects include a UE configured with processor-executable instructions for performing operations of any of the methods summarized above. Further aspects include a non-transitory processor-readable storage medium storing processor-executable instructions configured to cause a processor of the UE to perform operations of any of the methods summarized above. Further aspects include a UE having means for performing the functions of any of the methods summarized above. Further aspects include a system-on-chip for use in a UE including a processor configured to perform one or more operations of any of the methods summarized above.

[0010] Various aspects include a method and a network element configured to perform a method for configuring a network service to support an application. Various aspects may include receiving a service request directed to a URL associated with a data processing service that supports application operation of an application at a UE, resolving the URL to the network data processing service by a network service handler function, and activating the network data processing service in response to resolving the URL to the network data processing service. In some aspects, the application may be a portal application. In some aspects, the network element may be implemented as part of a communications network. Some aspects may include sending a redirection message from the network service handler function to the UE in response to the service request, the redirection message configured to trigger a media service application at the UE that is configured to support the application operation of the application at the UE.

[0011] Further aspects include a network element having a processor configured to perform one or more operations of any of the methods summarized above. Further aspects include a network element configured with processor-executable instructions for performing operations of any of the methods summarized above. Further aspects include a non-transitory processor-readable storage medium storing processor-executable instructions configured to cause a processor of the network element to perform operations of any of the methods summarized above. Further aspects include a network element having means for performing the functions of any of the methods summarized above. Further aspects include a system-on-chip for use in a network element, including a processor configured to perform one or more operations of any of the methods summarized above. [Brief explanation of the drawings]

[0012] [Figure 1A] FIG. 1 is a system block diagram illustrating an exemplary communication system suitable for implementing any of the various embodiments. [Figure 1B] FIG. 1 is a system block diagram illustrating an exemplary distributed base station architecture suitable for implementing any of the various embodiments. [Figure 2] FIG. 1 is a component block diagram illustrating an exemplary computing and wireless modem system suitable for implementing any of the various embodiments. [Figure 3] FIG. 1 is a component block diagram illustrating a software architecture including radio protocol stacks for user and control planes in wireless communications suitable for implementing any of the various embodiments. [Figure 4A] FIG. 1 is a component block diagram illustrating a system configured to perform operations for configuring network services to support applications, according to various embodiments. [Figure 4B]FIG. 1 is a message flow diagram illustrating a method for configuring a network service to support an application, according to various embodiments. [Figure 4C] FIG. 1 is a component block diagram illustrating a system configured to perform operations for configuring network services to support applications, according to various embodiments. [Figure 4D] FIG. 1 is a message flow diagram illustrating a method for configuring a network service to support an application, according to various embodiments. [Figure 4E] FIG. 1 is a component block diagram illustrating a system configured to perform operations for configuring network services to support applications, according to various embodiments. [Figure 4F] FIG. 1 is a message flow diagram illustrating a method for configuring a network service to support an application, according to various embodiments. [Figure 5A] FIG. 1 is a process flow diagram illustrating a method for configuring a network service to support an application, performed by a processor of a UE, according to various embodiments. [Figure 5B] FIG. 10 is a process flow diagram illustrating operations that may be performed by a processor of a UE as part of a method for configuring network services to support an application, according to various embodiments. [Figure 5C] FIG. 10 is a process flow diagram illustrating operations that may be performed by a processor of a UE as part of a method for configuring network services to support an application, according to various embodiments. [Figure 5D] FIG. 10 is a process flow diagram illustrating operations that may be performed by a processor of a UE as part of a method for configuring network services to support an application, according to various embodiments. [Figure 5E]FIG. 10 is a process flow diagram illustrating operations that may be performed by a processor of a UE as part of a method for configuring network services to support an application, according to various embodiments. [Figure 5F] FIG. 10 is a process flow diagram illustrating operations that may be performed by a processor of a UE as part of a method for configuring network services to support an application, according to various embodiments. [Figure 6A] FIG. 1 is a process flow diagram illustrating a method for configuring a network service to support an application, performed by a processor of a network element, according to various embodiments. [Figure 6B] FIG. 1 is a process flow diagram illustrating operations that may be performed by a processor of a network element as part of a method for configuring a network service to support an application, according to various embodiments. [Figure 7] FIG. 1 is a component block diagram of a network element device suitable for use in various embodiments. [Figure 8] FIG. 1 is a component block diagram of a wireless device suitable for use in various embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0013] Various embodiments will now be described in detail with reference to the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts. References made to specific examples and implementations are for illustrative purposes only and do not limit the scope of the claims.

[0014] Various embodiments may include a user equipment (UE) and a network element (network computing device) configured to perform operations to configure network services to support applications executing on the UE. Various embodiments improve the operation of the UE and the network element by increasing the efficiency with which the UE and the network element may initiate or activate data processing and transport functions of a 3GPP communication network.

[0015] The term "computing device" is used herein to refer to any one or all of cellular telephones, smartphones, portable computing devices, personal or mobile multimedia players, laptop computers, tablet computers, smartbooks, ultrabooks, palmtop computers, wireless email receivers, multimedia Internet-enabled cellular telephones, medical devices and equipment, biometric sensors / devices, wearable devices including smart watches, smart clothing, smart glasses, smart wristbands, and smart jewelry (e.g., smart rings and smart bracelets), entertainment devices (e.g., wireless game controllers, music and video players, satellite radio, etc.), wireless network-enabled Internet of Things (IoT) devices including smart meters / sensors, industrial manufacturing equipment, large and small home or business appliances, wireless communication elements in autonomous and semi-autonomous vehicles, wireless devices attached to or embedded in various mobile platforms, global positioning system devices, and similar electronic devices that include memory, wireless communication components, and a programmable processor.

[0016] The term "network element" is used herein to refer to any one or all of the following computing devices that are part of or communicate with a communications network: a server, a router, a gateway, a hub device, a switch device, a bridge device, a repeater device, or another electronic device that includes memory, communication components, and a programmable processor. A wireless device that communicates with a network may be considered a network element of such a network.

[0017] As used herein, the terms "network," "communications network," and "system" may interchangeably refer to part or all of a communications network or internetwork. A network may include multiple network elements. A network may include a wireless network and / or support one or more functions or services of a wireless network.

[0018] As used herein, the terms “wireless network,” “cellular network,” and “wireless communications network” may interchangeably refer to a portion or all of a carrier's wireless network associated with a wireless device and / or a subscription on a wireless device. The techniques described herein may be used for various wireless communications networks, such as Code Division Multiple Access (CDMA), time division multiple access (TDMA), FDMA, orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), and other networks. Generally, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support at least one radio access technology, which may operate on one or more frequencies or ranges of frequencies. For example, a CDMA network may implement Universal Terrestrial Radio Access (UTRA) (including the Wideband Code Division Multiple Access (WCDMA) standard), CDMA2000 (including the IS-2000, IS-95, and / or IS-856 standards), etc. In another example, a TDMA network may implement Enhanced Data rates for GSM Evolution (EDGE). In another example, an OFDMA network may implement Evolved UTRA (E-UTRA) (including the LTE standard), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc.Reference may be made to wireless networks using the LTE standard; thus, the terms "Evolved Universal Terrestrial Radio Access," "E-UTRAN," and "eNodeB" may also be used interchangeably herein to refer to wireless networks. However, such references are provided by way of example only and are not intended to exclude wireless networks using other communication standards. For example, while various third-generation (3G), fourth-generation (4G), and fifth-generation (5G) systems are discussed herein, these systems are mentioned by way of example only and, in various instances, may be substituted with future-generation systems (e.g., sixth-generation (6G) or later systems).

[0019] The term "system on chip" (SOC) is used herein to refer to a single integrated circuit (IC) chip that includes multiple resources or processors integrated on a single substrate. A single SOC may include circuitry for digital, analog, mixed-signal, and radio frequency functions. A single SOC may also include any number of general-purpose or special-purpose processors (such as digital signal processors, modem processors, video processors, etc.), memory blocks (such as ROM, RAM, flash, etc.), and resources (such as timers, voltage regulators, oscillators, etc.). A SOC may also include software for controlling the integrated resources and processors, as well as for controlling peripheral devices.

[0020] The term "system in a package" (SIP) is sometimes used herein to refer to a single module or package that includes multiple resources, computing units, cores, or processors on two or more IC chips, substrates, or SOCs. For example, a SIP may include a single substrate on which multiple IC chips or semiconductor dies are stacked in a vertical configuration. Similarly, a SIP may include one or more multi-chip modules (MCMs) on which multiple ICs or semiconductor dies are packaged in a unified substrate. A SIP may also include multiple independent SOCs packaged in close proximity and coupled to each other via high-speed communication circuitry, such as on a single motherboard or within a single wireless device. The proximity of the SOCs facilitates high-speed communication and memory and resource sharing.

[0021] Endpoint computing devices can send and receive various information that enables applications and services to operate on the endpoint devices. Transport of such information may utilize certain data processing and transport capabilities (referred to herein as "data processing services") of 3GPP communication networks. Examples of data processing services include Dynamic Adaptive Streaming over Hypertext Transfer Protocol (DASH) and Hypertext Transfer Protocol Live Streaming (HLS). DASH or HLS may use or be used in conjunction with, for example, Multimedia Broadcast Multicast Services (MBMS) user services, 5G broadcast services (e.g., MBMS Receive-Only Mode (MBMS ROM)), Multicast Broadcast Service (MBS) user services, and / or 5G media streaming functionality. Another example of a data processing service includes Extended Reality (XR) services that use 5G edge network enablers (including edge computing devices). In various embodiments, XR may include or refer to a variety of services, including virtual reality (VR), augmented reality (AR), mixed reality (MR), and other similar services.In various embodiments, data processing services may be enabled and / or provided by various functions instantiated in the communications network, such as a Broadcast-Multicast Service Center (BMSC), a Multicast-Broadcast Service Function (MBSF), a Multicast-Broadcast Service Transport Function (MBSTF), a 5G Media Streaming Application Function (5GMS AF), a 5G Broadcast Receiver Function (e.g., which may be instantiated in a UE), an Edge Application Server, and an Edge Enablement Client (e.g., which may be instantiated in a UE), and / or other suitable data processing functions. To invoke and use such data processing and transport functions of a 3GPP communications network, endpoint computing devices and network elements must be instructed to perform operations to initiate or activate the data processing and transport functions of the network.

[0022] Various embodiments may include methods, and UEs and network elements configured to perform operations of the methods, for configuring a network service to support an application using information received from a network element of a communications network, such as an application server that is part of the communications network or an application provider in communication with the communications network. In some embodiments, the UE and / or network element may be configured to receive a service request message directed to a specifically configured uniform resource locator (URL) associated with a data processing service. Functionality instantiated in the UE and / or network element may be configured to receive the service request message directed to the URL, and based on the information in the service request message, the UE and / or network element may perform operations to configure the network service to support the application (e.g., to support communications for the application). In some embodiments, the URL may include a Hypertext Transfer Protocol (HTTP) or Hypertext Transfer Protocol Secure (HTTPS) URL as an entry point to which the service request message may be directed. The operations performed by the UE and / or network element may activate (initiate, bootstrap) a data processing service (or multiple data processing services) including functionality of a 3GPP communications network to support communications for the application.

[0023] In various embodiments, a handler function or resolver function may be instantiated in the UE and / or the communication network. The handler function or resolver function may be configured to receive a service request message directed to a URL and resolve the URL to a function configured to perform operations to activate (start, bootstrap) a data processing service(s) for an application. In some embodiments, the service request message may include information specifying the requested data processing service(s). In some embodiments, the service request message may also include information for configuring one or more aspects of the data processing service(s). In some embodiments, aspects of the data processing service(s) may be activated in a network computing device of the communication network. For example, the data processing service may allocate communication resources, set up transport resources, and perform operations to transport MBMS information (e.g., packets). As another example, a data processing service may allocate communication resources, set up transport resources, and perform operations to transport 5G media streaming packets (e.g., via a Media Session Handling Application Function (MSH AF) and other suitable network functions). In some embodiments, aspects of the data processing service(s) may be activated in the UE. For example, aspects of an MBMS ROM service may be activated in the UE to enable reception and / or processing of multicast / broadcast information. In various embodiments, a URL may be defined to enable performance of data processing service bootstrapping, such as activating pre-configured device capabilities of a network element and / or UE, or to support invocation of one or more device capabilities of a network element and / or UE.

[0024] In various embodiments, the UE may be configured to launch an application that communicates with a network element to perform an application operation, such as a portal application for the UE that communicates with a network element to obtain various data services, such as media content, among other examples. The UE may send a service request to a URL associated with a data processing service that supports the application operation in response to launching the application. In some embodiments, the UE may send the service request to the URL automatically, i.e., without further user input, in response to launching the application. Automatically sending the service request may improve the user experience by reducing the number of user inputs required to launch the application and allowing the application to quickly begin receiving data services after a single user action of launching the application. The service request may be configured to trigger activation of a data processing service, for example, at the UE and / or at a network element of the communication network. The UE may execute the application operation using communications supported by the data processing service received from the network element.

[0025] In some embodiments, the URL may be configured to be resolved by a function of a network element of a communications network. The URL may resolve to a network function that activates a data processing service(s). In some embodiments, the network element may send a message including a media entry point URL to a media service application running on the UE. The media entry point URL may enable the media service application running on the UE to request content from a media service provider network element (e.g., over a communications network).

[0026] In some embodiments, sending the service request to a URL associated with a data processing service supporting the application operation may include sending the service request to a URL of a network service handler function in the communication network. In such embodiments, the service request may be configured to be resolved by the network service handler function to initiate a network data processing service in the communication network. In some embodiments, a media service application at the UE may receive a redirection message from the network service handler function in response to the service request. In some embodiments, the UE may execute a media service application configured to receive a communication from a network element in response to the received redirection message. The UE may receive a communication from the network element via the media service application that is supported by the network data processing service. The UE may perform an operation via the media service application using the received communication to support the application operation.

[0027] In some embodiments, the URL may be configured to be resolved by a UE service handler function running on the UE. In some embodiments, the URL may be configured to include an indication of one or more data processing services, parameters of the data processing services, and a media entry point URL. In such embodiments, the UE may be configured with a service handler function. The UE service handler function may receive a service request directed to the URL. The UE service handler function may initiate a data processing service on the UE and may also activate (start, launch, run) a media service application on the UE. The UE media service application may receive communications from network elements and perform operations using the received communications to support application operations.

[0028] In some embodiments, sending the service request to a URL associated with a data processing service supporting the application operation may include resolving the URL associated with the data processing service using a UE service handler function executing on a processor of the UE, starting the UE data processing service at the UE that supports the application operation, and executing a media service application at the UE configured to receive communications supported by the UE data processing service from a network element, all of which may be performed automatically, i.e., without further user input. In some embodiments, the UE service handler function may activate a UE media application function. In some embodiments, the UE may perform the application operation by receiving a communication from a network service provider via the UE data processing service, providing the received communication to a media service application, and performing an operation by the media service application using the received communication to support the application operation.

[0029] In some embodiments, the URL may be configured to be resolved by a UE service handler function executing in the UE and by a network service handler function in the communication network. In such embodiments, the UE function and the network function may be configured to receive a service request directed to the URL. For example, the UE service handler function executing in a processor of the UE may resolve the URL associated with a data processing service, and the UE may initiate the UE data processing service that supports the application operation. The UE may also execute a media service application in the UE configured to receive communications from a network element (e.g., a media service provider). The UE may send a second service request to a network service handler function in the communication network. The second service request may be configured to be resolved by the network service handler function to initiate the network data processing service in the communication network.

[0030] In some embodiments, the UE media service application may receive network data processing services and communications supported by the UE data processing services from a network element. The UE media service application may perform operations using the network data processing services and communications supported by the UE data processing services received from the network element (e.g., to support an application). In some embodiments, the UE may launch a media service provider application using a media entry point URL (e.g., which may be included in a service request).

[0031] In some embodiments, the UE service handler function may request and / or receive service parameters associated with the data processing service(s) from the network service handler function. The UE service handler function can receive the service parameters from the network service handler function. The UE service handler function can configure the UE data processing service(s) based on the received service parameters.

[0032] Various embodiments may include a network element including a processor configured to perform operations to configure a network service to support an application. In some embodiments, the network element may receive a service request directed to a URL associated with a data processing service that supports application operation of an application at the UE. A network service handler function may resolve the URL to the network data processing service. The network element may perform operations to activate the network data processing service in response to resolving the URL to the network data processing service. In some embodiments, the network element may send a redirection message from the network service handler function to the UE in response to the service request. In such embodiments, the redirection message may be configured to trigger a media service application at the UE that is configured to support application operation of the application at the UE.

[0033] In some embodiments, the UE may obtain (e.g., receive, request, be provided, etc.) HTTP URLs configured to be associated with data services and network data processing services. The UE may issue (e.g., send or send a message including) a request (e.g., a service request) to the URL on the UE. In response to the request issued by the UE, the data processing service may be invoked at the UE (e.g., by or at the UE data processing service), at a network element of the communications network (the network data processing service), or at both the UE and the network element. In some embodiments, the UE may also automatically invoke (e.g., run, start, launch, etc.) applications configured to process data service communications received from and / or transmitted to the communications network, where such communications are supported by the UE and / or network data processing services.

[0034] In embodiments in which the data processing service is invoked at a network element (i.e., a network data processing service), in response to issuing a request to the URL, the UE may communicate with a network service handler in the communications network. The network service handler function may provide support functionality for the associated data service. The network service handler function may send a message to the UE including a redirection message to the data service URL. In response to the redirection message and / or using the data service URL and / or other information in the redirection message, the UE may initiate (e.g., launch, launch, etc.) a second application that can use (e.g., consume, utilize, perform an operation using) the communication (e.g., information or data) of the associated data service. In some embodiments, the UE may receive a redirection message in response to the request sent to the URL. In some embodiments, the UE may execute a media service application configured to receive a communication from a network element in response to the received redirection message. The media service application may receive communications from the network element that are supported by the network data processing service(s). The media service application may perform an operation using the received communication to support the application operation.

[0035] In embodiments in which the data processing service is invoked at the UE, in response to the UE issuing a request to the URL, the UE may send a message (e.g., an instruction, a command, etc.) to a function or module of the UE to invoke the data processing service (i.e., a UE data processing service) at the UE. The UE data processing service may receive (e.g., obtain, request and receive, collect, etc.) service access parameter(s) and / or media entry point(s) related to the application and / or application operation of the application executing at the UE. The UE data processing service may execute (e.g., start, launch, invoke, etc.) a second application that may receive communications from a network element via the UE data processing service. In some embodiments, a UE service handler function executing at the UE may resolve a URL associated with the network service. The UE may start one or more UE data processing services that support the application operation. The UE may execute a media service application configured to receive communications from a network element that are supported by the UE data processing service.

[0036] In embodiments in which a data processing service is invoked at both the UE and a network element of the communication network, in response to the UE issuing a request to the URL, the UE may send a message (e.g., an instruction, a command, etc.) to a function or module of the UE to invoke the data processing service (i.e., a UE data processing service) at the UE. In addition, the UE service handler function may communicate with the network service handler function to obtain (e.g., receive, collect, etc.) additional data (information, parameters, configuration information) from the network service handler function. In such embodiments, the UE may initiate the UE data processing service based on (e.g., using, in response to, etc.) the obtained information. The UE service handler function may launch a second application configured to consume information of or from the data service to perform operations to support the application operation.

[0037] Various embodiments improve the operation of UEs and network elements by increasing the efficiency with which the UEs and network elements may initiate or activate data processing and transport functions of a 3GPP communications network. Various embodiments simplify the operation of UEs and network elements by simplifying the activation of data processing services to support application operations.

[0038] 1A is a system block diagram illustrating an exemplary communication system 100 suitable for implementing any of the various embodiments. The communication system 100 may be a 5G New Radio (NR) network or any other suitable network, such as a Long Term Evolution (LTE) network. While FIG. 1 illustrates a 5G network, subsequent generation networks may include the same or similar elements. Accordingly, references to a 5G network or 5G network elements in the following description are for purposes of illustration and not limitation.

[0039] Communications system 100 may include a heterogeneous network architecture including a core network 140 and various wireless devices (depicted in FIG. 1 as user equipment (UE) 120a-120e). Communications system 100 may also include several base stations (depicted as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station is an entity that communicates with the wireless devices and may also be called a NodeB, an LTE Evolved NodeB (eNodeB or eNB), an access point (AP), a radio head, a transmit receive point (TRP), a New Radio base station (NR BS), a 5G NodeB (NB), a Next Generation NodeB (gNodeB or gNB), etc. Each base station may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" can refer to a coverage area of ​​a base station, a base station subsystem serving this coverage area, or a combination thereof, depending on the context in which the term is used. Core network 140 can be any type of core network, such as an LTE core network (e.g., an EPC network), a 5G core network, etc.

[0040] The base stations 110a-110d may provide communication coverage for a macro cell, a pico cell, a femto cell, another type of cell, or a combination thereof. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by wireless devices with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by wireless devices with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by wireless devices that associate with the femto cell (e.g., wireless devices in a closed subscriber group (CSG)). A base station for a macro cell may be referred to as a macro BS. A base station for a pico cell may be referred to as a pico BS. A base station for a femto cell may be referred to as a femto BS or a home BS. 1, base station 110a may be a macro BS for macro cell 102a, base station 110b may be a pico BS for pico cell 102b, and base station 110c may be a femto BS for femto cell 102c. Base stations 110a-110d may support one or multiple (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “node B,” “5G NB,” and “cell” may be used interchangeably herein.

[0041] In some examples, the cells may not be stationary, and the geographic area of ​​the cells may move according to the location of the mobile base station. In some examples, the base stations 110a-110d may be interconnected to each other and to one or more other base stations or network nodes (not shown) in the communication system 100 through various types of backhaul interfaces, such as direct physical connections, virtual networks, or combinations thereof, using any suitable transport network.

[0042] Base stations 110a-110d may communicate with core network 140 over wired or wireless communication links 126. Wireless devices 120a-120e may communicate with base stations 110a-110d over wireless communication links 122.

[0043] Wired communication link 126 may use a variety of wired networks (such as Ethernet, TV cable, telephone, fiber optic, and other forms of physical network connections) that may use one or more wired communication protocols, such as Ethernet, Point-to-Point Protocol, High-Level Data Link Control (HDLC), Advanced Data Communication Control Protocol (ADCCP), and Transmission Control Protocol / Internet Protocol (TCP / IP).

[0044] Communications system 100 may also include relay stations (such as relay BS 110d). A relay station is an entity that can receive data transmissions from an upstream station (e.g., a base station or a wireless device) and send data transmissions to a downstream station (e.g., a wireless device or a base station). A relay station may also be a wireless device that can relay transmissions for other wireless devices. In the example shown in FIG. 1, relay station 110d can communicate with macro base station 110a and wireless device 120d to facilitate communication between base station 110a and wireless device 120d. A relay station may also be referred to as a relay base station, a repeater, etc.

[0045] Communications system 100 may be a heterogeneous network including different types of base stations, e.g., macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations may have different transmit power levels, different coverage areas, and may have different impacts on interference in communications system 100. For example, macro base stations may have high transmit power levels (e.g., 5-40 watts), while pico base stations, femto base stations, and relay base stations may have lower transmit power levels (e.g., 0.1-2 watts).

[0046] A network controller 130 can couple to a set of base stations and provide coordination and control for these base stations. The network controller 130 can communicate with the base stations via a backhaul. The base stations can also communicate with each other directly or indirectly, e.g., via wireless or wireline backhaul.

[0047] Wireless devices 120a, 120b, 120c may be dispersed throughout communication system 100, and each wireless device may be fixed or mobile. A wireless device may also be called an access terminal, a terminal, a mobile station, a subscriber unit, a station, user equipment (UE), etc.

[0048] The macro base station 110a may communicate with the communication network 140 over a wired or wireless communication link 126. The wireless devices 120a, 120b, 120c may communicate with the base stations 110a-110d over a wireless communication link 122.

[0049] The wireless communication links 122 and 124 may include multiple carrier signals, frequencies, or frequency bands, each of which may include multiple logical channels. The wireless communication links 122 and 124 may use one or more radio access technologies (RATs). Examples of RATs that may be used in the wireless communication links include 3GPP LTE, 3G, 4G, 5G (such as NR), GSM, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMAX), Time Division Multiple Access (TDMA), and other mobile telephony communication technology cellular RATs. Further examples of RATs that may be used in one or more of the various wireless communication links within communication system 100 include medium-range protocols such as Wi-Fi, LTE-U, LTE-Direct, LAA, and MuLTEfire, as well as relatively short-range RATs such as ZigBee, Bluetooth, and Bluetooth Low Energy (LE).

[0050] Some wireless networks (e.g., LTE) use orthogonal frequency division multiplexing (OFDM) on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. Generally, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may depend on the system bandwidth. For example, the subcarrier spacing may be 15 kHz, and the minimum resource allocation (called a "resource block") may be 12 subcarriers (or 180 kHz). Thus, the nominal Fast File Transfer (FFT) size may be equal to 128, 256, 512, 1024, or 2048 for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively. The system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0051] Although descriptions of some implementations may use terminology and examples related to LTE technology, some implementations may be applicable to other wireless communication systems, such as New Radio (NR) or 5G networks. NR may utilize OFDM with cyclic prefix (CP) on the uplink (UL) and downlink (DL) and may include support for half-duplex operation using Time Division Duplex (TDD). A single component carrier bandwidth of 100 MHz may be supported. An NR resource block may span 12 subcarriers with a subcarrier bandwidth of 75 kHz over a duration of 0.1 milliseconds (ms). Each radio frame may consist of 50 subframes with a length of 10 ms. Thus, each subframe may have a length of 0.2 ms. Each subframe may indicate a link direction (i.e., DL or UL) of data transmission, and the link direction for each subframe may be dynamically switched. Each subframe may contain DL / UL data as well as DL / UL control data. Beamforming may be supported, and beam directions may be dynamically configured. Multiple Input Multiple Output (MIMO) transmission with precoding may also be supported. MIMO configuration in the DL may support up to eight transmit antennas, with multi-layer DL transmission of up to eight streams, up to two streams per wireless device. Multi-layer transmission with up to two streams per wireless device may be supported. Multiple cell aggregation may be supported with up to eight serving cells. Alternatively, NR may support an air interface different from an OFDM-based air interface.

[0052] Some wireless devices may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) wireless devices. MTC and eMTC wireless devices include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc. that may communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless computing platform may provide connectivity for or to a network (e.g., a wide area network such as the Internet or a cellular network), for example, via a wired or wireless communication link. Some wireless devices may be considered Internet of Things (IoT) devices or may be implemented as NB-IoT (narrowband Internet of Things) devices. Wireless devices 120a-120e may be included within a housing that houses components of the wireless devices 120a-120e, such as a processor component, a memory component, similar components, or a combination thereof.

[0053] In general, any number of communication systems and any number of wireless networks may be deployed in a given geographic area. Each communication system and wireless network may support a particular radio access technology (RAT) and may operate on one or more frequencies. A RAT may also be referred to as a radio technology, air interface, etc. A frequency may also be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between communication systems of different RATs. In some cases, 4G / LTE and / or 5G / NR RAT networks may be deployed. For example, a 5G non-standalone (NSA) network may utilize both a 4G / LTE RAT on the 4G / LTE RAN side of the 5G NSA network and a 5G / NR RAT on the 5G / NR RAN side of the 5G NSA network. Both the 4G / LTE RAN and the 5G / NR RAN may connect to each other and to a 4G / LTE core network (e.g., an evolved packet core (EPC) network) within the 5G NSA network. Other example network configurations may include a 5G standalone (SA) network in which a 5G / NR RAN connects to a 5G core network.

[0054] In some implementations, two or more wireless devices 120a-120e (e.g., shown as wireless device 120a and wireless device 120e) may communicate directly (e.g., without using base station 110a-110d as an intermediary for communicating with each other) using one or more sidelink channels 124. For example, the wireless devices 120a-120e may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, a vehicle-to-everything (V2X) protocol (which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or similar protocol), a mesh network, or similar network, or a combination thereof. In this case, wireless devices 120a-120e may perform scheduling operations, resource selection operations, and other operations described elsewhere herein as being performed by base stations 110a-110d.

[0055] 1B is a system block diagram illustrating the architecture of an exemplary separated base station 160 suitable for implementing any of the various embodiments. Referring to FIG. 1A and FIG. 1B, the separated base station 160 architecture may include one or more central units (CUs) 162 that can communicate directly with the core network 180 via a backhaul link or indirectly with the core network 180 through one or more separated base station units, such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 164 via an E2 link, or a Non-Real Time (Non-RT) RIC 168 associated with a Service Management and Orchestration (SMO) framework 166, or both. The CUs 162 can communicate with one or more distributed units (DUs) 170 via respective midhaul links, such as an F1 interface. The DUs 170 can communicate with one or more radio units (RUs) 172 via respective fronthaul links. The RUs 172 can communicate with respective UEs 120 via one or more radio frequency (RF) access links. In some implementations, a UE 120 can be served by multiple RUs 172 simultaneously.

[0056] Each of the units (i.e., CU 162, DU 170, RU 172), as well as quasi-RT RIC 164, non-RT RIC 168, and SMO framework 166, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) over a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the unit's communication interface, may be configured to communicate with one or more of the other units over a transmission medium. For example, a unit may include a wired interface configured to receive signals from or transmit signals to one or more of the other units over a wired transmission medium. In addition, the units may include a wireless interface, which may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive, transmit, or transmit signals over a wireless transmission medium to one or more of the other units.

[0057] In some aspects, the CU 162 can host one or more upper layer control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by the CU 162. The CU 162 may be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 162 may be logically divided into one or more CU-UP units and one or more CU-CP units. The CU-UP units may communicate bidirectionally with the CU-CP units via an interface, such as an E1 interface, when implemented in an O-RAN configuration. The CU 162 may be implemented to communicate with the DU 170, as needed, for network control and signaling.

[0058] The DU 170 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 172. In some aspects, the DU 170 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more upper physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional division such as that defined by the Third Generation Partnership Project (3GPP). In some aspects, the DU 170 may further host one or more lower PHY layers. Each layer (or module) may be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 170 or with control functions hosted by the CU 162.

[0059] Lower layer functionality may be implemented by one or more RUs 172. In some deployments, the RUs 172 controlled by the DUs 170 may correspond to logical nodes hosting RF processing functions, lower PHY layer functions (such as performing fast Fourier transforms (FFTs), inverse FFTs (iFFTs), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional division, such as a lower layer functional division. In such an architecture, the RU(s) 172 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU(s) 172 may be controlled by the corresponding DUs 170. In some scenarios, this configuration may enable the DU(s) 170 and CU 162 to be implemented in a cloud-based radio access network (RAN) architecture, such as a virtual RAN (vRAN) architecture.

[0060] The SMO framework 166 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 166 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (e.g., an O1 interface). For virtualized network elements, the SMO framework 166 may be configured to interact with a cloud computing platform (e.g., an open cloud (O-Cloud) 176) via a cloud computing platform interface (e.g., an O2 interface) to perform network element lifecycle management (e.g., instantiate virtualized network elements). Such virtualized network elements may include, but are not limited to, the CU 162, the DU 170, the RU 172, and the quasi-RT RIC 164. In some implementations, the SMO framework 166 may communicate with hardware aspects of a 4G RAN, such as an open eNB (O-eNB) 174, via the O1 interface. Additionally, in some implementations, the SMO framework 166 can communicate directly with one or more RUs 172 via an O1 interface. The SMO framework 166 can also include a non-RT RIC 168 configured to support the functionality of the SMO framework 166.

[0061] The non-RT RIC 168 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the quasi-RT RIC 164. The non-RT RIC 168 may be coupled to or in communication with the quasi-RT RIC 164 (e.g., via an A1 interface). The quasi-RT RIC 164 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources through data collection and action via one or more CUs 162, one or more DUs 170, or both, and an interface connecting the O-eNB to the quasi-RT RIC 164 (e.g., via an E2 interface).

[0062] In some implementations, the non-RT RIC 168 may receive parameters or external enrichment information from an external server to generate the AI / ML models deployed to the quasi-RT RIC 164. Such information may be utilized by the quasi-RT RIC 164 or may be received at the SMO framework 166 or the non-RT RIC 168 from non-network data sources or from network functions. In some examples, the non-RT RIC 168 or the quasi-RT RIC 164 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 168 may monitor long-term trends and patterns in performance and employ the AI / ML models to implement corrective actions through the SMO framework 166 (e.g., reconfiguration via O1) or through the creation of RAN management policies (e.g., A1 policies).

[0063] 2 is a component block diagram illustrating an exemplary computing and wireless modem system 200 suitable for implementing any of the various embodiments. The various embodiments may be implemented on a number of single-processor and multi-processor computer systems, including systems-on-chips (SOCs) or systems-in-packages (SIPs).

[0064] 1A-2 , the illustrated exemplary computing device 200 (which may be a SIP in some embodiments) includes two SOCs 202, 204 coupled to a clock 206, a voltage regulator 208, and a wireless transceiver 266 configured to transmit and receive wireless communications to and from a wireless device (e.g., 120a-120e) or base station (e.g., 110a-110d) via an antenna (not shown). In some implementations, the first SOC 202 may operate as a central processing unit (CPU) of the wireless device, carrying out instructions of a software application program by performing arithmetic, logic, control, and input / output (I / O) operations specified by the instructions. In some implementations, the second SOC 204 may operate as a dedicated processing unit. For example, the second SOC 204 may operate as a 5G dedicated processing unit responsible for managing high-volume, high-speed (e.g., 5 Gbps), and / or very high-frequency, short-wavelength (e.g., 28 GHz millimeter-wave spectrum) communications.

[0065] The first SOC 202 may include a digital signal processor (DSP) 210, a modem processor 212, a graphics processor 214, an application processor 216, one or more coprocessors 218 (such as a vector coprocessor) connected to one or more of the processors, memory 220, custom circuitry 222, system components and resources 224, an interconnect / bus module 226, one or more temperature sensors 230, a thermal management unit 232, and a thermal power envelope (TPE) component 234. The second SOC 204 may include a 5G modem processor 252, a power management unit 254, an interconnect / bus module 264, multiple mmWave transceivers 256, memory 258, and various additional processors 260, such as application processors, packet processors, etc.

[0066] Each processor 210, 212, 214, 216, 218, 252, 260 may include one or more cores, and each processor / core may perform operations independently of the other processors / cores. For example, a first SOC 202 may include a processor that runs a first type of operating system (e.g., FreeBSD, LINUX, OS X), and a processor that runs a second type of operating system (e.g., MICROSOFT WINDOWS 10). Additionally, any or all of the processors 210, 212, 214, 216, 218, 252, 260 may be included as part of a processor cluster architecture (e.g., a synchronous processor cluster architecture, an asynchronous or heterogeneous processor cluster architecture, etc.).

[0067] The first SOC 202 and the second SOC 204 may include various system components, resources, and custom circuitry for managing sensor data, analog-to-digital conversion, wireless data transmission, and for performing other specialized operations, such as processing encoded audio and video signals for decoding data packets and rendering in a web browser. For example, the system components and resources 224 of the first SOC 202 may include power amplifiers, voltage regulators, oscillators, phase-locked loops, peripheral bridges, data controllers, memory controllers, system controllers, access ports, timers, and other similar components used to support processors and software clients running on the wireless device. The system components and resources 224 and / or custom circuitry 222 may also include circuitry for interfacing with peripheral devices, such as cameras, electronic displays, wireless communication devices, external memory chips, etc.

[0068] The first SOC 202 and the second SOC 204 may communicate via an interconnect / bus module 250. The various processors 210, 212, 214, 216, 218 may be interconnected to one or more memory elements 220, system components and resources 224, custom circuitry 222, and a thermal management unit 232 via an interconnect / bus module 226. Similarly, the processor 252 may be interconnected to a power management unit 254, a millimeter wave transceiver 256, memory 258, and various additional processors 260 via an interconnect / bus module 264. The interconnect / bus modules 226, 250, 264 may include arrays of reconfigurable logic gates and / or implement bus architectures (e.g., CoreConnect, AMBA, etc.). Communication may occur via advanced interconnects such as high-performance networks-on-chip (NoCs).

[0069] The first SOC 202 and / or the second SOC 204 may further include input / output modules (not shown) for communicating with resources external to the SOC, such as a clock 206 and a voltage regulator 208. Resources external to the SOC (such as the clock 206 and the voltage regulator 208) may be shared by two or more of the internal SOC processors / cores.

[0070] In addition to the exemplary SIP 200 described above, some implementations may be implemented in a wide variety of computing systems, which may include a single processor, multiple processors, multi-core processors, or any combination thereof.

[0071] 3 is a component block diagram illustrating a software architecture 300 including radio protocol stacks for user and control planes in wireless communications suitable for implementing any of the various embodiments. Referring to FIGS. 1A-3, a wireless device 320 may implement software architecture 300 to facilitate communications between the wireless device 320 (e.g., wireless devices 120a-120e, 200) and a base station 350 (e.g., base stations 110a-110d) of a communications system (e.g., 100). In various embodiments, layers in software architecture 300 may form logical connections with corresponding layers in the software of base station 350. Software architecture 300 may be distributed among one or more processors (e.g., processors 212, 214, 216, 218, 252, 260). Although illustrated with respect to one radio protocol stack in a multi-SIM (Subscriber Identity Module) wireless device, software architecture 300 may include multiple protocol stacks, each associated with a different SIM (e.g., two protocol stacks associated with two SIMs in a dual-SIM wireless communication device). Although described below with respect to an LTE communication layer, software architecture 300 may support any of a variety of standards and protocols for wireless communication and / or may include additional protocol stacks supporting any of a variety of standards and protocols for wireless communication.

[0072] Software architecture 300 may include a Non-Access Stratum (NAS) 302 and an Access Stratum (AS) 304. NAS 302 may include functions and protocols to support packet filtering, security management, mobility control, session management, traffic and signaling between a wireless device's SIM(s) (e.g., SIM(s) 204) and its core network 140. AS 304 may include functions and protocols to support communication between a SIM(s) (e.g., SIM(s) 204) and supported access network entities (e.g., base stations). Specifically, AS 304 may include at least three layers (Layer 1, Layer 2, and Layer 3), each of which may include various sublayers.

[0073] In the user and control planes, Layer 1 (L1) of the AS 304 may be a physical layer (PHY) 306 that may oversee functions that enable transmission and / or reception over the air interface via a wireless transceiver (e.g., 266). Examples of such physical layer 306 functions may include cyclic redundancy check (CRC) attachment, coding blocks, scrambling and descrambling, modulation and demodulation, signal measurement, MIMO, etc. The physical layer may include various logical channels, including a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH).

[0074] In the user and control planes, Layer 2 (L2) of the AS 304 may be responsible for the link between the wireless device 320 and the base station 350 over the physical layer 306. In some implementations, Layer 2 may include a Medium Access Control (MAC) sublayer 308, a Radio Link Control (RLC) sublayer 310, a Packet Data Convergence Protocol (PDCP) 312 sublayer, and a Service Data Adaptation Protocol (SDAP) 317 sublayer, each forming a logical connection that terminates at the base station 350.

[0075] In the control plane, Layer 3 (L3) of the AS 304 may include a radio resource control (RRC) sublayer 3. Although not shown, the software architecture 300 may include additional Layer 3 sublayers, as well as various upper layers above Layer 3. In some implementations, the RRC sublayer 313 may provide functions including broadcasting system information, paging, and establishing and releasing RRC signaling connections between the wireless device 320 and the base station 350.

[0076] In various embodiments, the SDAP sublayer 317 may provide mapping between Quality of Service (QoS) flows and data radio bearers (DRBs). In various implementations, the PDCP sublayer 312 may provide uplink functions including multiplexing between different radio bearers and logical channels, sequence numbering, handover data processing, integrity protection, ciphering, and header compression. In the downlink, the PDCP sublayer 312 may provide functions including in-order delivery of data packets, duplicate data packet detection, integrity verification, decryption, and header recovery.

[0077] In the uplink, the RLC sublayer 310 may provide segmentation and concatenation of upper layer data packets, retransmission of lost data packets, and Automatic Repeat Request (ARQ). In the downlink, the RLC sublayer 310 functions may include reordering of data packets to compensate for out-of-order reception, reassembly of upper layer data packets, and ARQ.

[0078] In the uplink, the MAC sublayer 308 may provide functions including multiplexing between logical and transport channels, random access procedures, logical channel priorities, and hybrid-ARQ (HARQ) operations. In the downlink, MAC layer functions may include channel mapping within a cell, demultiplexing, discontinuous reception (DRX), and HARQ operations.

[0079] While the software architecture 300 may provide functionality for transmitting data over a physical medium, the software architecture 300 may further include at least one host layer 314 for providing data transfer services to various applications in the wireless device 320. In some implementations, the application-specific functionality provided by the at least one host layer 314 may provide an interface between the software architecture and a general-purpose processor.

[0080] In other implementations, software architecture 300 may include one or more upper logical layers (e.g., transport, session, presentation, application) that provide host layer functionality. For example, in some implementations, software architecture 300 may include a network layer (e.g., an Internet Protocol (IP) layer) where a logical connection terminates at a packet data network (PDN) gateway (PGW). In some implementations, software architecture 300 may include an application layer where a logical connection terminates at another device (e.g., an end-user device, a server). In some implementations, software architecture 300 may further include a hardware interface 316 between physical layer 306 and communications hardware (e.g., one or more radio frequency (RF) transceivers) in AS 304.

[0081] FIG. 4A is a component block diagram illustrating a system 400a configured to perform operations for configuring network services to support an application, according to various embodiments. FIG. 4B is a message flow diagram illustrating a method 400b for configuring network services to support an application, according to various embodiments. With reference to FIGS. 1-4B, the system 400a may include a UE 402 (e.g., 110a-110d, 200, 320), a communication network (e.g., 140), a portal application provider 406, and a media application provider 408. In various embodiments, the portal application provider 406 and the media application provider 408 may execute or be instantiated in one or more network elements that communicate with the communication network 404. In various embodiments, the communication network 404 may include one or more network elements as part of the communication network 404. In some embodiments, a uniform resource locator (URL) associated with a data processing service 416 that supports application operation of an application of a UE may be configured to be resolved by functionality of a network element of the communication network.

[0082] In some embodiments, the media application provider 408 and the portal application provider 406 may perform an operation 430 to communicate to generate and provide a media service entry point (e.g., an entry point URL). At operation 432, the media application provider 408 and the network data processing service 416 may perform an operation 432 to provision data processing services for one or more applications provided or supported by the media application provider 408.

[0083] The UE 402 and a User Plane Function (UPF) 418 of the communication network 404 may perform operation 434 to establish a communication link (e.g., a best-effort IP communication link). In some embodiments, the UE 402 may execute a portal application 410. The portal application 410 may include an application that communicates with network elements, such as a portal application provider 406 and / or a media application provider 408, to perform application operations. In some embodiments, the portal application 410 and the portal application provider 406 may perform operation 436, in which the portal application provider 406 may provide an indication of media services (e.g., a list or another suitable data structure) and a 3GPP media service entry point URL to the portal application 410.

[0084] At operation 438, the UE 402 may receive input (e.g., from a user via an input device of the UE 402) selecting a media service via the portal application 410. In response to receiving the input selecting the media service, the portal application 410 may perform operation 440 of communicating with a network service handler function 414 of the communications network 404 to request a media service entry point URL for the selected media service. As part of operation 440, the portal application 410 may send a service request to the network service handler function 414 that includes a URL associated with a data processing service that supports the operation of the portal application (the application operation).

[0085] The network service handler function 414 may resolve the URL to which the service request is directed. The network service handler function 414 and the network data processing service 416 may perform operation 442 to activate (start, launch) aspects or functions of the network data processing service 416. The network service handler function 414 may also send a redirection message 444 to the media service application 412 at the UE. In response to the received redirection message, the UE may perform operation 446 to execute the media service application 412. In some embodiments, the UE 402 may automatically activate or launch the media service application 412 based on the URL associated with the data processing service.

[0086] The media service application 412 and the media application provider 408 may perform operations 448 to obtain media content from the media application provider 408. Using the received communication (i.e., the media content), the media service application 412 may perform operations 450 to support application operations of the portal application 410.

[0087] FIG. 4C is a component block diagram illustrating a system 400c configured to perform operations for configuring a network service to support an application, according to various embodiments. FIG. 4D is a message flow diagram illustrating a method 400d for configuring a network service to support an application, according to various embodiments. With reference to FIGS. 1-4D, the system 400c may include a UE 402 (e.g., 110a-110d, 200, 320), a communication network (e.g., 140), a portal application provider 406, and a media application provider 408. In various embodiments, the portal application provider 406 and the media application provider 408 may execute or be instantiated within one or more network elements that communicate with the communication network 404. In various embodiments, the communication network 404 may include one or more network elements as part of the communication network 404. In some embodiments, the URL may be configured to be resolved by a UE service handler function 452 executing on the UE 402.

[0088] In some embodiments, elements of the UE 402, the communication network 404, the portal application provider 406, and the media application provider 408 may perform operations 430-438 substantially as described with respect to Figures 4A and 4B.

[0089] In response to receiving input selecting a media service in operation 438, the portal application 410 may communicate with a UE service handler function 452 of the UE to send a service request 460 to the UE service handler function 452, the service request 460 including a URL associated with a data processing service that supports the operation of the portal application (application operation). The UE service handler function 452 may resolve the URL to which the service request is directed. The UE service handler function 452 may send a message 462 to activate (start, invoke) an aspect or function of the UE data processing service 454. The UE service handler function 454 may receive one or more messages 463 including service access parameters that may include a media service entry point. The UE service handler function 452 may also send a message 464 to initiate an operation to launch (execute, start) the media service application 412. In some embodiments, the UE 402 may automatically activate or launch the media service application 412 based on the URL associated with the data processing service.

[0090] The media application service 412 and the UE data processing service 454 may perform an operation 466 to establish inter-process communication to enable the UE data processing service 454 to provide the communication received from the media application provider 408 to the media service application 412. The media service application 412 and the UE data processing service 454 may perform an operation 468 in which the media service application 412 sends a request to the UE data processing service 454 requesting content from the media application provider 408. The UE data processing service 454 and the media application provider 408 may perform an operation 470 in which the UE data processing service 454 requests the content from the media application provider 408, and in response, the media application provider 408 sends a communication including the requested content for the portal application 410 to the UE data processing service 454 of the UE 402. The UE data processing service 454 may receive the communication including the requested content and may send the communication to the media service application 412. Using the received communication (ie, media content), the media services application 412 may perform operations 450 to support application operations of the portal application 410 substantially as described.

[0091] FIG. 4E is a component block diagram illustrating a system 400e configured to perform operations for configuring a network service to support an application, according to various embodiments. FIG. 4F is a message flow diagram illustrating a method 400f for configuring a network service to support an application, according to various embodiments. With reference to FIGS. 1-4F, the system 400d may include a UE 402 (e.g., 110a-110d, 200, 320), a communication network (e.g., 140), a portal application provider 406, and a media application provider 408. In various embodiments, the portal application provider 406 and the media application provider 408 may execute or be instantiated within one or more network elements that communicate with the communication network 404. In various embodiments, the communication network 404 may include one or more network elements as part of the communication network 404. In some embodiments, the URL may be configured to be resolved by a UE service handler function 452 function executing on the UE 402. In some embodiments, the URL may be configured for resolution by a UE service handler function 452 running on the UE 402 and by a network service handler function 414 in the communication network 404.

[0092] In some embodiments, elements of the UE 402, the communication network 404, the portal application provider 406, and the media application provider 408 may perform operations 430-438 substantially as described with respect to Figures 4A and 4B.

[0093] In response to receiving input selecting a media service in operation 438, the portal application 410 may communicate with a UE service handler function 452 of the UE to send a service request 460 to the UE service handler function 452, the service request including a URL associated with a data processing service that supports the operation of the portal application (application operation). The UE service handler function 452 may resolve the URL to which the service request is directed.

[0094] The UE service handler function 452 and the network service handler function 414 may perform operation 472 to determine, generate, send, and / or exchange service parameters related to the data processing service. The UE service handler function 452 may send a message 462 to activate (start, invoke) an aspect or function of the UE data processing service 454. The UE data processing service 454 and the network data processing service 416 may perform operation 474 to exchange service parameters for the data processing service. The UE data processing service 454 may perform operation 476 to configure the UE data processing service 454 according to the service parameters. The network data processing service 416 may perform operation 478 to configure the network data processing service 416 according to the service parameters.

[0095] The UE service handler function 452 can send a message 464 to initiate an operation to launch (execute, start) the media service application 412. In some embodiments, the UE 402 can automatically activate or launch the media service application 412 based on a URL associated with the data processing service.

[0096] The media application service 412, the UE data processing service 454, and the media application provider 408 may perform operations 468, 470, and 450 substantially as described with respect to Figures 4C and 4D.

[0097] 5A is a process flow diagram illustrating a method 500a performed by a processor of a UE for configuring network services to support an application, according to various embodiments. Referring to FIGS. 1A-5A, the operations of method 500 may be performed by a processor (e.g., processor 210, 212, 214, 216, 218, 252, 260, 428, etc.) of a UE (e.g., 110a-110d, 200, 320, 800).

[0098] In block 502, the processor may launch an application that communicates with a network element to perform an application operation. For example, the UE may obtain (receive, request, be provided) an HTTP URL configured to associate with a data service and a network data processing service.

[0099] At block 504, the processor may, in response to launching the application, send a service request configured to cause activation of the data processing service to a URL associated with a data processing service supporting the application operation. In some embodiments, the UE may, in response to launching the application, send the service request to the URL automatically, i.e., without further user input. Automatically sending the service request may improve the user experience by reducing the number of user inputs required to launch the application and allowing the processor to quickly begin receiving data services after a single user action of launching the application. In some embodiments, the processor may send the service request to a URL of a network service handler function in the communications network. In such embodiments, the service request may be configured to be resolved by the network service handler function to initiate a network data processing service in the communications network. For example, the UE may issue (send, send a message including) a request (e.g., a service request) to a URL on the UE. In response to the request issued by the UE, the data processing service may be invoked at the UE (UE data processing service), at a network element of the communications network (network data processing service), or at both the UE and the network element. In some embodiments, the UE may also automatically launch (execute, start, launch) applications configured to process data service communications received from and / or transmitted to the communications network, such communications being supported by data processing services of the UE and / or the network.

[0100] At block 506, the processor may execute an application operation using the communication received from the network element and supported by the data processing service.

[0101] 5B-5F are process flow diagrams illustrating operations 500b-500f that may be performed by a processor of a UE as part of a method 500a for configuring a network service to support an application, according to various embodiments. With reference to FIGS. 1A-5F, operations 500b-500f may be performed by a processor (e.g., processor 210, 212, 214, 216, 218, 252, 260, 428, etc.) of a UE (e.g., 110a-110d, 200, 320, 800).

[0102] Referring to FIG. 5B, as described, after sending a service request to a URL associated with a data processing service that supports the application operation in response to launching the application in block 504, the processor may receive a redirection message from a network service handler function in response to the service request in block 510.

[0103] At block 512, the processor may execute a media service application at the UE configured to receive a communication from the network element in response to the received redirection message.

[0104] At block 514, the processor may receive, by the media service application, a communication supported by the network data processing service from the network element.

[0105] At block 516, the processor may perform operations by the media services application using the received communication to support the application operations.

[0106] As described, in block 506, the processor may execute an application operation using the communication received from the network element and supported by the data processing service.

[0107] Referring to FIG. 5C, as described above, after launching an application that communicates with a network element to perform an application operation in block 502, the processor may resolve a URL associated with a data processing service in block 520 using a UE service handler function running in the processor of the UE.

[0108] In block 522, the processor may initiate a UE data processing service in the UE that supports application operation.

[0109] At block 524, the processor may execute a media service application at the UE configured to receive communications from a network element supported by the UE data processing service.

[0110] In block 526, the processor may activate the media application function through the UE service handler function.

[0111] As described, in block 506, the processor may execute an application operation using the communication received from the network element and supported by the data processing service.

[0112] Referring to FIG. 5D , as described above, after sending a service request to a URL associated with a data processing service that supports the application operation in response to launching the application in block 504, the processor may receive a communication from a network service provider via the UE data processing service in block 530.

[0113] In block 532, the processor may provide the received communication to a media service application.

[0114] At block 534, the processor may perform operations by the media services application using the received communication to support the application operations.

[0115] As described, in block 506, the processor may execute an application operation using the communication received from the network element and supported by the data processing service.

[0116] Referring to FIG. 5E, as described, after launching an application that communicates with a network element to perform an application operation in block 502, the processor may resolve a URL associated with a data processing service in block 540 using a UE service handler function running in the processor of the UE.

[0117] In block 542, the processor may initiate a UE data processing service in the UE that supports application operation.

[0118] At block 544, the processor may execute a media services application at the UE configured to receive communications from the network element.

[0119] The processor may send a second service request to a network service handler function in the communications network at block 546. In some embodiments, the second service request may be configured to be resolved by the network service handler function to initiate a network data processing service in the communications network.

[0120] At block 548, the processor may receive, by the media service application, communications supported by the network data processing services and the UE data processing services from the network element.

[0121] At block 550, the processor may perform operations by a media service application using communications supported by the network data processing services and the UE data processing services received from the network element.

[0122] Referring to FIG. 5F, as described above, after initiating a UE data processing service in the UE that supports application operation in block 542, the processor may send a request for service parameters associated with the data processing service from a service handler function in the UE to a network service handler function in block 560.

[0123] At block 562, the processor may receive service parameters from the network service handler function.

[0124] At block 564, the processor may configure the UE data processing service based on the received service parameters.

[0125] The processor may execute a media services application at the UE configured to receive communications from the network element, as described, at block 544 .

[0126] 6A is a process flow diagram illustrating a method 600a for configuring a network service to support an application, performed by a processor of a network element, according to various embodiments. With reference to FIGS. 1A-6A, the operations of method 600a may be performed by a processor (e.g., processors 210, 212, 214, 216, 218, 252, 260, 428, etc.) of a network element (e.g., 414, 416, 418, 700).

[0127] At block 602, the processor may receive a service request directed to a uniform resource locator (URL) associated with a data processing service that supports application operation of an application of a user equipment (UE).

[0128] In block 604, the processor may resolve the URL to a network data processing service through a network service handler function.

[0129] At block 606, the processor may activate the network data processing service in response to resolving the URL to the network data processing service.

[0130] 6B is a process flow diagram illustrating operations 600b that may be performed by a processor of a network element as part of a method 600a for configuring a network service to support an application, according to various embodiments. With reference to FIGS. 1A-6B, the operations of method 600b may be performed by a processor (e.g., processor 210, 212, 214, 216, 218, 252, 260, 428, etc.) of a network element (e.g., 414, 416, 418, 700).

[0131] After activating the network data processing service in response to resolving the URL to the network data processing service at block 606 as described, the processor may send a redirection message from the network service handler function to the UE in response to the service request at block 610. In some embodiments, the redirection message may be configured to trigger a media service application at the UE configured to support application operations of an application of the UE.

[0132] FIG. 7 is a component block diagram of a network element device suitable for use in various embodiments. Referring to FIGS. 1A-7, a network element device may implement functions (e.g., 414, 416, 418) in a communications network (e.g., 100, 150) and may include at least the components shown in FIG. 7. Network element device 700 may include a processor 701 coupled to volatile memory 702 and mass non-volatile memory, such as a disk drive 708. Network element device 700 may also include a peripheral memory access device 706, such as a floppy disk drive, compact disc (CD) drive, or digital video disc (DVD) drive, coupled to processor 701. Network element device 700 may also include a network access port 704 (or interface) coupled to processor 701 for establishing a data connection with a network, such as the Internet or a local area network coupled to other system computers and servers. Network element device 700 may include one or more antennas 707 for transmitting and receiving electromagnetic radiation, which may be connected to a wireless communications link. The network element device 700 may include additional access ports such as USB, Firewire, Thunderbolt, etc. for coupling to peripherals, external memory, or other devices.

[0133] FIG. 8 is a component block diagram of a wireless device 800 suitable for use in various embodiments. In some embodiments, the wireless device 800 may operate as a network element. With reference to FIGS. 1A-8, various embodiments may be implemented in various wireless devices 800 (e.g., wireless devices 120a-120e, 200, 320, 404), an example of which is illustrated in FIG. 8 in the form of a smartphone. The wireless device 800 may include a first SOC 202 (e.g., a SOC-CPU) coupled to a second SOC 204 (e.g., a 5G-capable SOC). The first SOC 202 and the second SOC 204 may be coupled to an internal memory 816, a display 812, and a speaker 814. Additionally, the wireless device 800 may include an antenna 804 for transmitting and receiving electromagnetic radiation, which may be connected to a transceiver 427 coupled to one or more processors within the first SOC 202 and / or second SOC 204. The wireless device 800 may include menu selection buttons or rocker switches 820 for receiving user input.

[0134] The wireless device 800 may include a voice encoding / decoding (CODEC) circuit 810 that digitizes sound received from a microphone into data packets suitable for wireless transmission and decodes the received sound data packets to generate analog signals that are provided to a speaker to generate sound. One or more of the processors in the first SOC 202 and second SOC 204, the wireless transceiver 266, and the CODEC 810 may include digital signal processor (DSP) circuitry (not separately shown).

[0135] The processors of the network element device 700 and the wireless device 800 may be any programmable microprocessor, microcomputer, or one or more multiple processor chips that can be configured by software instructions (applications) to perform various functions, including the functions of some implementations described below. In some wireless devices, multiple processors may be provided, such as one processor dedicated to wireless communication functions in the SOC 204 and one processor dedicated to running other applications in the SOC 202. Software applications may be stored in memory 702, 816 before they are accessed and loaded into the processors. The processors may include sufficient internal memory to store application software instructions.

[0136] The various embodiments shown and described are provided merely as examples to illustrate various features of the claims. However, features shown and described with respect to any given embodiment are not necessarily limited to the associated embodiment and may be used with or combined with other embodiments shown and described. Moreover, the claims are not intended to be limited to any one exemplary embodiment. For example, one or more of the methods and operations 400b, 400d, 400f, 500a-500f, 600a, and 600b may be replaced by or combined with one or more of the methods and operations 400b, 400d, 400f, 500a-500f, 600a, and 600b.

[0137] Example implementations are described in the following paragraphs. While some of the following implementation examples are described with reference to example methods, further example implementations may include the example methods described in the following paragraphs implemented by a base station including a processor configured with processor-executable instructions for performing the operations of the methods of the following implementation examples, the example methods discussed in the following paragraphs implemented by a base station including means for performing the functions of the methods of the following implementation examples, and the example methods described in the following paragraphs that may be implemented as a non-transitory processor-readable storage medium storing processor-executable instructions configured to cause a processor of a base station to perform the operations of the methods of the following implementation examples.

[0138] Example 1. A method executed by a processor of a user equipment (UE) for configuring a network service to support an application, the method including: launching the application that communicates with a network element to perform an application operation; in response to launching the application, sending a service request to a uniform resource locator (URL) associated with a data processing service that supports the application operation, the service request being configured to cause activation of the data processing service; and executing the application operation using a communication received from the network element, the communication being supported by the data processing service.

[0139] Example 2. The method of example 1, wherein sending the service request to a URL associated with a data processing service that supports application operation includes automatically (i.e., without further user input) sending the service request to the URL in response to launching the application.

[0140] Example 3. The method of example 1 or example 2, further comprising: obtaining a URL from the communication network, the URL relating to the data processing service and the data service provided by the network element.

[0141] Example 4. The method of any one of Examples 1 to 3, wherein activation of the data processing service occurs in the UE, in the communication network, or both.

[0142] Example 5. The method of any one of Examples 1 to 4, wherein the application is a portal application that uses information received from a network element of the communication network.

[0143] Example 6. The method of any one of Examples 1-5, wherein the network element comprises a network service provider.

[0144] Example 7. The method of any one of Examples 1-6, wherein automatically sending the service request to a URL associated with a data processing service supporting the application operation includes sending the service request to a URL of a network service handler function in the communications network, the service request being resolved by the network service handler function to initiate a network data processing service in the communications network.

[0145] Example 8. The method of Example 7, further comprising: receiving a redirection message from a network service handler function in response to a service request; executing, in the UE, a media service application configured to receive a communication from a network element in response to the received redirection message; receiving, by the media service application, a communication from the network element that is supported by the network data processing service; and performing, by the media service application, an operation using the received communication to support the application operation.

[0146] Example 9. The method according to any one of Examples 1 to 8, wherein automatically sending a service request to a URL associated with a data processing service supporting an application operation includes: resolving the URL associated with the data processing service using a UE service handler function running on a processor of the UE; initiating, in the UE, the UE data processing service supporting the application operation; and executing, in the UE, a media service application configured to receive, from a network element, communications supported by the UE data processing service.

[0147] Example 10. The method of Example 9, wherein performing an application operation using the received communication supported by the data processing service includes receiving, by the UE data processing service, the communication from a network service provider; providing the received communication to a media service application; and performing, by the media service application, an operation using the received communication to support the application operation.

[0148] Example 11. The method of Example 9, further comprising activating a media application function by a UE service handler function.

[0149] Example 12. The method of any one of Examples 1 to 11, wherein automatically sending a service request to a network URL associated with a data processing service supporting the application operation includes resolving the URL associated with the data processing service using a UE service handler function running on a processor of the UE, initiating the UE data processing service supporting the application operation in the UE, executing a media service application in the UE configured to receive communications from a network element, sending a second service request to a network service handler function in the communication network, the second service request being configured to be resolved by the network service handler function to initiate the network data processing service in the communication network, receiving by the media service application from the network element the network data processing service and communications supported by the UE data processing service, and performing the application operation using the received communications supported by the data processing service includes performing by the media service application an operation using the received communications from the network element, the received communications supported by the network data processing service and the UE data processing service.

[0150] Example 13. The method of Example 12, further comprising: sending a request for service parameters associated with the data processing service from the UE service handler function to a network service handler function; receiving the service parameters from the network service handler function; and configuring the UE data processing service based on the received service parameters.

[0151] Example 14. A method executed by a processor of a network element for configuring a network service to support an application, the method comprising: receiving a service request directed to a uniform resource locator (URL) associated with a data processing service that supports application operation of an application of a user equipment (UE); resolving, by a network service handler function, the URL to a network data processing service; and activating the network data processing service in response to resolving the URL to the network data processing service.

[0152] Example 15. The method of example 14, wherein the application is a portal application.

[0153] Example 16. The method of example 14 or example 15, wherein the network element is implemented as part of a communications network.

[0154] Example 17. The method described in any one of Examples 14 to 16, further including: sending a redirection message from the network service handler function to the UE in response to a service request, the redirection message being configured to trigger a media service application in the UE configured to support application operations of an application of the UE.

[0155] As used herein, terms such as “component,” “module,” and “system” are intended to include computer-related entities, such as, but not limited to, hardware, firmware, a combination of hardware and software, software, or software in execution, configured to perform particular operations or functions. For example, a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, or a computer. By way of example, both an application running on a wireless device and the wireless device may be referred to as a component. One or more components may reside within a process or thread of execution; components may be localized on one processor or core or distributed among two or more processors or cores. In addition, these components may execute from various non-transitory computer-readable media having various instructions or data structures stored thereon. Components may communicate via local or remote processes, function or procedure calls, electronic signals, data packets, memory read / writes, and other known network-, computer-, processor-, or process-related communication methods.

[0156] Several different cellular and mobile communication services and standards are available or are contemplated in the future, all of which may implement and benefit from various embodiments. Such services and standards include, for example, 3rd Generation Partnership Project (3GPP), Long Term Evolution (LTE) systems, third generation wireless mobile communications technology (3G), fourth generation wireless mobile communications technology (4G), fifth generation wireless mobile communications technology (5G), and subsequent generations of 3GPP technologies, global system for mobile communications (GSM), universal mobile telecommunications system (UMTS), 3GSM, general packet radio service (GPRS), code division multiple access (CDMA) systems (e.g., cdmaOne, CDMA1020), enhanced data rates for GSM evolution (EDGE), advanced mobile phone system (AMPS), digital AMPS (IS-136 / TDMA), evolution-data optimized (EV-DO), digital enhanced cordless telecommunications (DET), and the like. These technologies include, for example, Directive 2005 / 2008 / 02224 (DECT), Worldwide Interoperability for Microwave Access (WiMAX), wireless local area network (WLAN), Wi-Fi Protected Access I & II (WPA, WPA2), and integrated digital enhanced network (iDEN). Each of these technologies involves the transmission and reception of voice, data, signaling, and / or content messages.It should be understood that any reference to terminology and / or technical details relating to particular telecommunications standards or technologies is for illustrative purposes only and does not limit the scope of the claims to any particular communications system or communications technology unless specifically recited in the claim language.

[0157] The above method descriptions and process flow diagrams are provided as illustrative examples only and do not require or imply that the operations of the various embodiments must be performed in the order presented. As will be understood by one of ordinary skill in the art, the order of operations in the above-described embodiments may be performed in any order. Terms such as "thereafter," "then," and "next" do not limit the order of operations. These terms are used to guide the reader through the method descriptions. Furthermore, any reference to claim elements in the singular, for example, using the articles "a," "an," or "the," should not be construed as limiting the element to the singular.

[0158] The various illustrative logical blocks, modules, components, circuits, and algorithmic operations described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, the various illustrative components, blocks, modules, circuits, and operations have been described generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the particular application and design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in varying ways for each particular application, and such implementation decisions should not be interpreted as causing a departure from the scope of the claims.

[0159] The hardware used to implement the various exemplary logic, logic blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed using general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, 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 conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of receiver smart objects, 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. Alternatively, some operations or methods may be performed by circuitry specific to a given function.

[0160] In one or more embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions or code on a non-transitory computer-readable or processor-readable storage medium. The operations of a method or algorithm disclosed herein may be embodied in a processor-executable software module or processor-executable instructions, which may reside on a non-transitory computer-readable or processor-readable storage medium. A non-transitory computer-readable or processor-readable storage medium may be any storage medium that can be accessed by a computer or processor. By way of example, and not limitation, such non-transitory computer-readable or processor-readable storage medium may include RAM, ROM, EEPROM, FLASH memory, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage smart objects, or any other medium that can be accessed by a computer and that can be used to store desired program code in the form of instructions or data structures. As used herein, disk and disc include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically while discs reproduce data optically using lasers. Combinations of the above are also included within the scope of non-transitory computer-readable and processor-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of code and / or instructions on a non-transitory processor-readable storage medium and / or a non-transitory computer-readable storage medium, which may be incorporated into a computer program product.

[0161] The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the claims. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of the claims. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the following claims and the principles and novel features disclosed herein.

Claims

1. 1. A method executed by a processor of a user equipment (UE) for configuring a network service to support an application, the method comprising: launching an application that communicates with a network element to perform an application operation; In response to launching the application, sending a service request to a uniform resource locator (URL) associated with a data processing service supporting the application operation, the service request configured to cause activation of the data processing service; and executing the application operation using communications supported by the data processing service received from the network element.

2. 2. The method of claim 1, wherein sending the service request to the URL associated with the data processing service supporting the application operation comprises automatically sending the service request to the URL in response to launching the application.

3. The method of claim 1 , further comprising obtaining the URL from a communications network, the URL associated with the data processing service and a data service provided by the network element.

4. The method of claim 1 , wherein the activation of the data processing service occurs at the UE, at a communications network, or both.

5. The method of claim 1 , wherein the application is a portal application.

6. The method of claim 1 , wherein the network element comprises a network service provider.

7. 2. The method of claim 1, wherein automatically sending the service request to the URL associated with the data processing service supporting the application operation comprises sending the service request to a URL of a network service handler function in a communications network, the service request being resolved by the network service handler function to initiate a network data processing service in the communications network.

8. receiving a redirection message from the network service handler function in response to the service request; executing, in the UE, a media services application configured to receive the communication from the network element in response to the received redirection message; receiving, by the media service application, from the network element, the communication supported by the network data processing service; performing an operation by the media services application using the received communication to support the application operation. The method of claim 7.

9. automatically sending the service request to the URL associated with the data processing service supporting the application operation; resolving the URL associated with the data processing service using a UE service handler function running on the processor of the UE; initiating a UE data processing service at the UE that supports the application operation; and executing, at the UE, a media service application configured to receive from the network element the communications supported by the UE data processing service.

10. performing the application operations using the received communications supported by the data processing service; receiving, by the UE data processing service, the communication from a network service provider; providing the received communication to the media services application; and performing an operation by the media services application using the received communication to support the application operation.

11. The method of claim 9 , further comprising activating a media application function by the UE service handler function.

12. automatically sending the service request to a network URL associated with the data processing service supporting the application operation; resolving the URL associated with the data processing service using a UE service handler function running on the processor of the UE; initiating a UE data processing service at the UE that supports the application operation; executing, at the UE, a media services application configured to receive the communication from the network element; sending a second service request to a network service handler function in the communications network, the second service request configured to be resolved by the network service handler function to initiate a network data processing service in the communications network; receiving, by the media service application, from the network element, the communications supported by the network data processing services and the UE data processing services; 2. The method of claim 1, wherein performing the application operation using the received communication supported by the data processing service comprises performing an operation by the media service application using the received communication from the network element that is supported by the network data processing service and the UE data processing service.

13. sending a request from said UE service handler function to a network service handler function for service parameters associated with said data processing service; receiving the service parameters from the network service handler function; and configuring the UE data processing service based on the received service parameters. The method of claim 12.

14. A user equipment (UE), a processor, the processor comprising: launching an application that communicates with a network element to perform an application operation; In response to launching the application, sending a service request to a uniform resource locator (URL) associated with a data processing service supporting the application operation, the service request configured to cause activation of the data processing service; configured to execute the application operation using communications supported by the data processing service received from the network element. UE.

15. 15. The UE of claim 14, wherein the processor is further configured to, in response to launching the application, automatically send the service request to the URL associated with the data processing service supporting the application.

16. The UE of claim 14 , wherein the processor is further configured to obtain the URLs associated with the data processing service and the data services provided by the network element from a communications network.

17. 15. The UE of claim 14, wherein the processor is further configured to send the service request to a URL of a network service handler function in a communications network, the service request being resolved by the network service handler function to initiate a network data processing service in the communications network.

18. the processor: receiving a redirection message from the network service handler function in response to the service request; executing, at the UE, a media services application configured to receive the communication from the network element in response to the received redirection message; receiving, by the media service application, from the network element, the communication supported by the network data processing service; 18. The UE of claim 17, further configured to perform an operation by the media services application using the received communication to support the application operation.

19. the processor: resolving the URL associated with the data processing service using a UE service handler function executing on the processor of the UE; Initiating a UE data processing service at the UE that supports the application operation; 15. The UE of claim 14, further configured to execute a media service application at the UE, the media service application configured to receive from the network element the communications supported by the UE data processing service.

20. the processor: receiving, by the UE data processing service, the communication from a network service provider; providing the received communication to the media service application; 20. The UE of claim 19, further configured to perform an operation by the media services application using the received communication to support the application operation.

21. 20. The UE of claim 19, wherein the processor is further configured to activate a media application function via the UE service handler function.

22. the processor: resolving the URL associated with the data processing service using a UE service handler function executing on the processor of the UE; Initiating a UE data processing service at the UE that supports the application operation; executing a media services application at the UE configured to receive the communication from the network element; sending a second service request to a network service handler function in the communications network, the second service request being resolved by the network service handler function to initiate a network data processing service in the communications network; receiving, by the media service application from the network element, the communications supported by the network data processing service and the UE data processing service; 15. The UE of claim 14, further configured to perform an operation by the media service application using the received communication from the network element supported by the network data processing service and the UE data processing service.

23. the processor: sending a request for service parameters associated with the data processing service from the UE service handler function to a network service handler function in the UE; receiving the service parameters from the network service handler function; 23. The UE of claim 22, further configured to configure the UE data processing service based on the received service parameters.

24. A user equipment (UE), means for invoking an application that communicates with a network element to perform an application operation; means for, in response to launching the application, sending a service request to a uniform resource locator (URL) associated with a data processing service supporting the application operation, the service request configured to cause activation of the data processing service; and means for executing the application operation using communications supported by the data processing service received from the network element; UE.

25. 25. The UE of claim 24, wherein the means for sending the service request to the URL associated with the data processing service supporting the application operation in response to launching the application comprises means for automatically sending the service request to the URL associated with the data processing service supporting the application operation in response to launching the application.

26. a processing device in a user equipment (UE), launching an application that communicates with a network element to perform an application operation; In response to launching the application, sending a service request to a uniform resource locator (URL) associated with a data processing service supporting the application operation, the service request configured to cause activation of the data processing service; and performing the application operation using communications received from the network element that are supported by the data processing service.

27. 1. A method executed by a processor of a network element for configuring a network service to support an application, comprising: receiving a service request directed to a uniform resource locator (URL) associated with a data processing service supporting application operation of an application on a user equipment (UE); resolving the URL to a network data processing service by a network service handler function; activating the network data processing service in response to resolving the URL to the network data processing service.

28. 28. The method of claim 27, wherein the application is a portal application.

29. 28. The method of claim 27, wherein the network element is implemented as part of a communications network.

30. and sending a redirection message from the network service handler function to the UE in response to the service request, the redirection message being configured to trigger a media service application in the UE configured to support the application operation of the application of the UE.

28. The method of claim 27.

31. 1. A network element comprising: a processor, receiving a service request directed to a uniform resource locator (URL) associated with a data processing service supporting application operation of an application on a user equipment (UE); resolving said URL to a network data processing service via a network service handler function; configured with processor-executable instructions to activate the network data processing service in response to resolving the URL to the network data processing service. Network elements.

32. 32. The network element of claim 31, wherein the processor is further configured with processor-executable instructions for sending a redirection message from the network service handler function to the UE in response to the service request, the redirection message being configured to trigger a media service application at the UE configured to support the application operation of the application at the UE.

33. 1. A network element comprising: means for receiving a service request directed to a uniform resource locator (URL) associated with a data processing service supporting application operation of an application of a user equipment (UE); means for resolving said URL to a network data processing service by a network service handler function; means for activating the network data processing service in response to resolving the URL to the network data processing service; Network elements.

34. A processing device within the network element receiving a service request directed to a uniform resource locator (URL) associated with a data processing service supporting application operation of an application on a user equipment (UE); resolving the URL to a network data processing service by a network service handler function; and activating the network data processing service in response to resolving the URL to the network data processing service.

Images