Network-based device registration for content distribution platforms
A device can receive, from a network device, information that identifies a user device. The network device might have authenticated the user device based on the user device accessing a radio access network. The device can receive, from the user device, a request for a first token. The request can include an encrypted session identifier. A server device might have encrypted the session identifier. The device can determine the session identifier, and generate the first token based on the session identifier and the information that identifies the user device. The device can encrypt the first token using an application public key, and provide, to the user device, the encrypted first token. The user device can provide, to the server device, the encrypted first token. The server device can register the user device to receive content based on the encrypted first token.
1. A device, comprising:
one or more memories; and
one or more processors, coupled to the one or more memories, to:
receive, from a network device, information that identifies a user device and comprises four-tuple information for the user device,
the user device to access a radio access network associated with the network device,
the network device to authenticate the user device based on the user device accessing the radio access network, and
the network device to provide, to the device, the information that identifies the user device based on authenticating the user device;
receive, from the user device, a request for a first token,
a server device to generate a session identifier,
the server device to provide, to the user device, encrypted information that includes the session identifier and the four-tuple information, and
the request for the first token including the encrypted information that includes the session identifier and the four-tuple information;
generate the first token based on decrypting the encrypted information that includes the session identifier and the four-tuple information; and
provide, to the user device, information that identifies the first token and the session identifier,
the user device to provide, to the server device, a registration request that includes information that identifies the first token and the session identifier,
the server device to generate a second token based on information associated with the user device and the session identifier,
the server device to compare the first token and the second token,
the server device to provide, to the user device, a device identifier based on comparing the first token and the second token, and
the device identifier to enable the user device to receive content associated with the server device.
2. The device of claim 1 , where the request for the first token includes an application identifier; and
where the one or more processors, when determining the session identifier, are to:
determine the session identifier using the application identifier.
3. The device of claim 1 , where the one or more processors are further to:
receive, from the network device, information that identifies an application identifier and information that identifies the server device; and
where the one or more processors, when generating the first token, are to:
generate the first token based on the information that identifies the user device,
the application identifier, and the information that identifies the server device.
4. The device of claim 1 , where the one or more processors are further to:
identify information that identifies a first network address of the user device and a second network address of the server device based on the request for the first token; and
where the one or more processors, when generating the first token, are to:
generate the first token based on the first network address and the second network address.
5. The device of claim 1 , where the one or more processors are further to:
receive, from the network device, information that identifies an application identifier,
where the application identifier is identified by the network device based on information contained in a packet received from the user device.
6. The device of claim 1 , where four-tuple information comprises:
a source Internet Protocol (IP) address;
a destination IP address;
a source port identifier; and
a destination port identifier.
7. The device of claim 1 , where the one or more processors are further to:
receive, from the network device, information that identifies a mobile directory number of the user device,
where the mobile directory number is identified by the network device based on information contained in a packet received from the user device.
8. A non-transitory computer-readable medium storing instructions, the instructions comprising:
one or more instructions that, when executed by one or more processors, cause the one or more processors to:
receive, from a network device, information that identifies a user device and comprises four-tuple information for the user device,
the user device to access a network associated with the network device,
the network device to authenticate the user device based on the user device accessing the network, and
the network device to provide the information that identifies the user device based on authenticating the user device;
receive, from the user device, a request for a first token,
the request for the first token including encrypted information that includes a session identifier and the four-tuple information, and
a server device to provide, to the user device, the encrypted information that includes the session identifier and the four-tuple information;
generate the first token based on decrypting the encrypted information that includes the session identifier and the four-tuple information; and
provide, to the user device, the first token and the session identifier,
the user device to provide, to the server device, a registration request that includes the first token,
the server device to generate a second token based on information that identifies the user device and the session identifier,
the server device to compare the first token and the second token,
the server device to selectively authenticate the user device based on comparing the first token and the second token.
9. The non-transitory computer-readable medium of claim 8 , where the request for the first token includes an application identifier; and
where the one or more instructions, that cause the one or more processors to generate the first token, cause the one or more processors to:
generate the first token based on the application identifier.
10. The non-transitory computer-readable medium of claim 8 , where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
receive, from the network device, information that identifies an application identifier and information that identifies the server device; and
where the one or more instructions, that cause the one or more processors to generate the first token, cause the one or more processors to:
generate the first token based on the information that identifies the application identifier and the information that identifies the server device.
11. The non-transitory computer-readable medium of claim 8 , where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
identify a mobile directory number of the user device based in part on the four-tuple information; and
where the one or more instructions, that cause the one or more processors to generate the first token, cause the one or more processors to:
generate the first token based in part on the mobile directory number and the four-tuple information.
12. The non-transitory computer-readable medium of claim 11 ,
where the four-tuple information comprises:
a source Internet Protocol (IP) address;
a destination IP address;
a source port identifier; and
a destination port identifier.
13. The non-transitory computer-readable medium of claim 8 , where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
receive, from the network device, information that identifies an application identifier,
where the application identifier is identified by the network device based on information contained in a packet received from the user device.
14. The non-transitory computer-readable medium of claim 8 , where the first token is generated based on an application identifier, the session identifier, a mobile directory number of the user device, and the four-tuple information.
15. A method, comprising:
receiving, by a device and from a network device, information that identifies a user device and comprises four-tuple information for the user device,
the user device to access a radio access network associated with the network device,
the network device to authenticate the user device based on the user device accessing the radio access network, and
the network device to provide the information that identifies the user device based on authenticating the user device;
receiving, by the device and from the user device, a request for a first token,
the request including encrypted information including a session identifier and the four-tuple information, and
a server device to provide, to the user device, the encrypted information;
decrypting, by the device, the encrypted information, to determine the session identifier and the four-tuple information;
generating, by the device, the first token based on the session identifier and the four-tuple information; and
providing, by the device and to the user device, the first token and the session identifier,
the user device to provide, to the server device, a registration request that includes the first token,
the server device to generate a second token based on information that identifies the user device and the session identifier,
the server device to compare the first token and the second token,
the server device to provide, to the user device, a device identifier based on comparing the first token and the second token, and
the device identifier to enable the user device to receive content associated with the server device.
16. The method of claim 15 , further comprising:
receiving, from the user device, information that identifies an application identifier and the server device based on the request for the first token; and
where generating the first token comprises:
generating the first token based on the information that identifies the application identifier and the server device.
17. The method of claim 15 , further comprising:
receiving, from the network device, information that identifies an application identifier, the user device, and the server device; and
where generating the first token comprises:
generating the first token based on the information that identifies the application identifier, the user device, and the server device.
18. The method of claim 15 , where the information that identifies the user device includes a mobile directory number.
19. The method of claim 18 , where the mobile directory number is identified by the network device based on the four-tuple information.
20. The method of claim 15 ,
where the four-tuple information comprises:
a source Internet Protocol (IP) address;
a destination IP address;
a source port identifier; and
a destination port identifier.