Verizon Patent and Licensing Inc.

Umesh Kumar Gupta

Jyotsna Kachroo

Muhammad Salman Nomani

Manuel Enrique Caceres

Lily H Zhu

Bjorn Hjelm

Mauricio Pati Caldeira De Andrada

Jun Yuan

Raghuram Parvataneni

Bharadwaj Vemuri

Masudur Rahman

Binaben Dipesh Patel

Sudhakar Reddy Patil

Ye Huang

Suzann Hua

Miguel Angel Carames

Ning Zhang

Mun Wei Low

John Patrick Hickey, Iii

Ramanathan Subramaniam

Mahesh Chapalamadugu

Syed Rehman

Michael A Adel

A method may include receiving, by at least one network device and from a user device, a registration message including a service identifier and at least one of a network slice identifier or a network slice token. The method may also include determining, based on information included in the registration message, whether the user device is authorized to use a network slice associated with the service identifier. The method may further include setting up a data session to be serviced by the network slice, in response to determining that the user device is authorized to use the network slice.

Systems and methods for network-based slice access authorization

A system described herein may provide for multiple levels of authentication, such that a User Equipment ('UE') may receive secure content from an application server, which may include or may be implemented by a multi-access edge computing (“MEC”) system. As described herein, a user associated with a UE may register the UE and/or a particular application with an authentication system and/or the application server. The registration of the UE and/or the application may establish a “trust” relationship between the authentication system and the UE, such that a user-level authentication performed by the UE, such as biometric authentication, may be accepted by the authentication system and/or the application system as an authentication of the user.

Systems and methods for multi-level authentication

A device may receive a consent address from a user device accessing an application that requires application data associated with consent of a user of the user device, and may provide, to the user device, a consent form associated with the consent address. The device may receive, from the user device, user authentication data provided via the consent form and via a first option or a second option, and may provide, to an application server device associated with the application, a notification indicating that the user authentication data was received. The device may provide, to a cloud service provider web services device, an authorization code and an authorization token based on providing the notification. The cloud service provider web services device may cause the application data to be provided to the application server device based on receiving the authorization code and the authorization token.

Systems and methods for obtaining consent for user data sharing by a network

An application client on a user device receives an internal request from within the application client. The internal request is associated with edge application device(s) hosted by a computing platform. In response to the internal request, the application client obtains an authorization token from the computing platform and initiates an edge discovery request to the computing platform using the authorization token. In response to the edge discovery request, the application client receives connection information of a particular edge application device among the edge application device(s) that is identified for the application client by the computing platform. The application client establishes a connection between the application client and the particular edge application device using the connection information of the particular edge application device.

Edge discovery authorization for a user device

A user device may receive a traffic category and/or slice usage policy, and may provide a request for an application. The user device may receive the application with a traffic category and/or slice usage requirement, and may install the application on the user device. The user device may subscribe to traffic categories and/or slices, and may receive approval to utilize the traffic categories and/or slices. The user device may provide, by the application and to an operating system, a connection request for a particular traffic category and/or slice, and may determine whether the application is approved for the particular traffic category and/or slice. The device may provide, to a modem, the connection request and traffic descriptors for the particular traffic category and/or slice based on the application being approved, and may establish a protocol data unit session, for the application, utilizing the particular traffic category and/or slice.

Systems and methods for preventing abuse of traffic categories and network slices by applications

In some implementations, an authentication system may receive a user authentication request identifying a primary device. The authentication system may generate a challenge associated with a user profile mapped to the primary device. The authentication system may transmit a challenge message including the challenge. The authentication system may receive a challenge response including a response to the challenge, wherein the response to the challenge includes identification information regarding the user profile. The authentication system may determine a set of primary services associated with the user profile mapped to the primary device and a set of secondary services associated with a set of secondary devices. The authentication system may generate a set of security keys mapped to the set of primary services and the set of secondary services. The authentication system may provision the primary device and the set of secondary devices with the set of security keys.

Systems and methods for network-based authentication for connected vehicle access

A device may receive, from a user equipment, a token request associated with an application, wherein the token request is associated with a device identifier. The device may generate a device token for the application and the user equipment. The device may provide, using the device identifier, the device token to the user equipment to enable a user to access the application via an application platform. The device may receive, from the application platform, a slice request for a network slice of a network that is to be used for an application session. The device may determine that the user equipment is associated with the application session based on the device token and the device identifier. The device may configure a network slice instance of the network slice. The device may determine a user equipment route selection policy for the application session according to the network slice instance.

Systems and methods for user-specific slice configuration for an application

A network device may determine, based on a provisioning request to host an application platform, a configuration of resources of a network for maintaining the application platform within the network. The network device may provision the resources to permit access to the application platform via a domain. The network device may receive, from a user device, a domain request that includes the domain, wherein the domain request is associated with configuring an application session between an application of the user device and the application platform. The network device may provide, to the user device, a response that includes an address of a host resource of the application platform, wherein the host resource is one of the resources. The network device may receive, from the user device, a session request that includes the address and may establish the application session between the user device and the host resource.

Systems and methods for configuring an application platform using resources of a network

A system described herein may provide for multiple levels of authentication, such that a User Equipment ('UE') may receive secure content from an application server, which may include or may be implemented by a multi-access edge computing ('MEC') system. As described herein, a user associated with a UE may register the UE and/or a particular application with an authentication system and/or the application server. The registration of the UE and/or the application may establish a &#x201c;trust&#x201d; relationship between the authentication system and the UE, such that a user-level authentication performed by the UE, such as biometric authentication, may be accepted by the authentication system and/or the application system as an authentication of the user.

Growing community of inventors

Morris Plains, NJ, United States of America

Umesh Kumar Gupta