Abstract: The present technology provides a versatile content management system that can also support bi-directional synchronization of an organization account. The organization account is maintained as a plurality of root directories that can be mounted under an organization directory top-level folder. The organization directory top-level folder can appear in a user account's view of the organization account, by does not actually exist as a directory in the content management system. The organization directory top-level folder can be a folder created on a client device in which root directories of an organization account are mounted, but the organization directory top-level folder is not a synchronized directory. The organization directory top-level folder gives the appearance of a single directory structure for an organization even though the organization content is actually organized into the plurality of root directories.

Abstract: A UE includes one or more non-transitory computer-readable media storing computer-executable instructions for configuring the UE to support legacy and robust paging functions is provided. The UE includes at least one processor that executes the instructions to cause the UE to receive an indication from a network that the UE is allowed to start the legacy paging function; monitor, during the legacy paging function, a legacy paging occasion to receive a legacy paging message, where each legacy paging message includes several records, each record includes the identity of a different UE; start the robust paging function after the number of consecutive legacy paging occasions the UE fails to receive reaches a threshold value; and monitor, during the robust paging function, a robust paging occasion to receive a robust paging message, where each robust paging message includes only one paging record that includes the identity of only one UE.

Abstract: A UE is configured with a first parameter indicating whether the UE is allowed to start robust paging function and a second parameter indicating the maximum number of consecutive legacy paging messages the UE has to fail to receive before the robust paging function is started. The UE's processor monitors a legacy paging occasion to receive a legacy paging message, determines that the number of consecutive legacy paging occasions that the UE fails to receive legacy paging messages has reached the value of the second parameter, starts the robust paging function after determining that the value of the first parameter indicates that the UE is allowed to start the robust paging function, and the number of consecutive legacy paging occasions that the UE fails to receive the legacy paging messages has reached the value of the second parameter, and monitors a robust paging occasion to receive a robust paging message.

Abstract: A UE includes one or more non-transitory computer-readable media storing one or more computer-executable instructions for configuring the UE to support legacy and robust paging functions is provided. The UE includes at least one processor that executes the computer-executable instructions to cause the UE to receive, from a network, an indication that the UE is allowed to start the robust paging function; monitor, during the legacy paging function, a paging legacy occasion to receive a legacy paging message; start the robust paging function after the number of consecutive legacy paging occasions that the UE fails to receive reaches a threshold value; monitor, during the robust paging function, a robust paging occasion to receive a robust paging message, where the same robust paging message with the same content is retransmitted several times during each robust paging occasion; and decode a complete robust paging message from the retransmitted robust paging messages.

Abstract: The present technology provides a versatile content management system that can also support bi-directional synchronization of an organization account. The organization account is maintained as a plurality of root directories that can be mounted under an organization directory top-level folder. The organization directory top-level folder can appear in a user account's view of the organization account, by does not actually exist as a directory in the content management system. The organization directory top-level folder can be a folder created on a client device in which root directories of an organization account are mounted, but the organization directory top-level folder is not a synchronized directory. The organization directory top-level folder gives the appearance of a single directory structure for an organization even though the organization content is actually organized into the plurality of root directories.

Abstract: The present technology pertains to restoring a directory to a state prior to a past synchronization event. A content management system can present an interface including history of synchronization events for a directory, and a user can select to restore a directory to a state prior to any one of the past synchronization events.

Abstract: The present technology pertains to restoring a directory to a state prior to a past synchronization event. A content management system can present an interface including history of synchronization events for a directory, and a user can select to restore a directory to a state prior to any one of the past synchronization events.

Abstract: The present technology pertains to restoring a directory to a state prior to a past synchronization event. A content management system can present an interface including history of synchronization events for a directory, and a user can select to restore a directory to a state prior to any one of the past synchronization events.

Abstract: A user equipment participates in vehicle-to-anything (V2X) communications. The user equipment comprises processor circuitry and a transmitter and/or receiver. The processor circuitry configured is to autonomously make a selection, from radio resources of at least two radio access technologies, of a radio resource(s) for transmission and/or reception of a V2X message of the V2X communication. The transmitter and/or receiver is configured to use the selected radio resource(s) for the transmission and/or reception of the V2X message.

Abstract: The present technology pertains to restoring a directory to a state prior to a past synchronization event. A content management system can present an interface including history of synchronization events for a directory, and a user can select to restore a directory to a state prior to any one of the past synchronization events.

Abstract: The present technology pertains to restoring a directory to a state prior to a past synchronization event. A content management system can present an interface including history of synchronization events for a directory, and a user can select to restore a directory to a state prior to any one of the past synchronization events.

Abstract: Techniques for domain capture. In one embodiment, for example, a method comprises detecting an attempt by a personal user account to use the online service where the account is associated with an electronic mail address that belongs to an owner of a domain name service domain. Based on detecting the attempt, the online service prompts the particular personal user account to join a team of user accounts. Upon receiving an acceptance of the particular personal user account to join the team, the personal user account is offered an option between converting the personal user account to a team user account that is a member of the team or changing the electronic mail address associated with the personal user account to a different electronic mail address that is not owned.

Abstract: Techniques for domain capture. In one embodiment, for example, a method comprises detecting an attempt to create a personal user account with an online service that uses an electronic mail address that belongs to an owner of a particular domain name service domain. Based on the detecting, the online service prompts a user associated with the attempt to create a team account with the online service that is under management of the owner of the particular domain name service domain. Also based on the detecting the online service offers the user an option of creating a personal user account with the online service using an unowned electronic mail address.

Abstract: In one embodiment, for example, a method comprises: receiving an acceptance of an invitation to join a team of one or more team user accounts held with the online service; based on receiving the acceptance and based on determining that an owned domain name service domain of an owned electronic mail address is associated with the team, offering a personal user account an option between at least: (a) converting the personal user account to a team user account that is a member of the team, and (b) changing an electronic mail address associated with the personal user account from the owned electronic mail address to one that has a different domain name service domain than the owned domain name service domain associated with the team.

Abstract: Techniques for invite enforcement and domain capture. In one embodiment, for example, a method performed in an online service computing environment comprises the operations of: storing, in a database, an association between a team of one or more user accounts and a domain name service domain; receiving a request to invite an e-mail address belonging to the domain name service domain to join the team; creating, in a database, a placeholder user account that is a member of the team; associating, in a database, the e-mail address with the placeholder user account; and after an invitation for the e-mail address to join the team is accepted, converting, in a database, the individual user account to a team account that is (a) a member of the team and (b) associated with the e-mail address.

Abstract: Techniques for invite enforcement and domain capture. In one embodiment, for example, a method performed in an online service computing environment comprises the operations of: storing, in a database, an association between a team of one or more user accounts and a domain name service domain; receiving a request to invite an e-mail address belonging to the domain name service domain to join the team; creating, in a database, a placeholder user account that is a member of the team; associating, in a database, the e-mail address with the placeholder user account; and after an invitation for the e-mail address to join the team is accepted, converting, in a database, the individual user account to a team account that is (a) a member of the team and (b) associated with the e-mail address.