Patent classifications
H04L61/3005
Extended discontinuous reception (DRX) cycle length in wireless communication networks
Embodiments of wireless communication devices and method for discontinuous reception (DRX) mode in wireless communication are generally described herein. Some of these embodiments describe a wireless communication device having a module to cause the wireless communication device to enter the DRX mode in an operational state of the wireless communication device. The DRX mode may include a DRX cycle having a DRX cycle length. The DRX cycle length may have a value greater than at least four values of DRX cycle lengths supported by an enhanced node-B.
REGISTRY DOMAIN NAME MANAGEMENT
Methods and systems for managing domain names are disclosed. A server hosts a platform that interfaces with users. The server is operably coupled to the registry and domain management database, and receives transaction requests to assign tags to one or more domain names, the tags used as identifiers to associate information with the domain names. The server stores the domain names with one or more tags and associated information in the domain management database. The server receives a request to perform a registry event on a domain name and checks if there are tags associated with the domain name of which the event was requested. If there is no assigned tag the server performs the registry event action. If there is an associated tag the server complies with the tag and associated tag information.
Method and apparatus for controlling small data transmission on the uplink
Apparatuses and methods for control of uplink transmission by a user equipment (UE) using machine-type communications (MTC) applications are described herein. The UE may transmit first data on a logical uplink channel. The logical uplink channel may have been assigned for use by machine-type communications (MTC) applications. The UE may receive transmission time restriction information, responsive to the transmitting, that indicates time periods during which the UE is permitted to transmit additional data on the logical uplink channel. The UE may refrain from transmitting additional data in a time period on the logical uplink channel based on the transmission time restriction information.
Long-term evolution device-to-device discovery using control channel
Device-to-device (D2D) communications between user equipment (UE) allows two UEs in a long-term evolution (LTE) network to communicate directly with each other without the need to first send their communications to a network (such as via an evolved node B). In order to communicate in a D2D mode, the UEs first need to discover each other. One method of allowing the UEs to discover each other involves the use of a physical uplink control channel (PUCCH). After a network determines that certain UEs would benefit from D2D communication, the UEs can be set up to send and receive discovery signals using the PUCCH.
PREVENTING COLLISION OF MOBILE SESSION IDENTIFIERS IN NEUTRAL HOST NETWORK
A first identifier of a mobile session is generated for a mobile device accessing a network operating in an unlicensed radio band, wherein at least one part of the first mobile session identifier comprises a decimal format consistent with an identifier recognizable by a network operating in a licensed radio band. The first mobile session identifier is compared to one or more previously generated mobile session identifiers currently allocated in the unlicensed radio band network to prevent collision there between.
PCI partition and allocation for cellular network
Generally discussed herein are systems and apparatuses that can implement Physical Cell Identity assignments that reduce collision or confusion of small cell identities at User Equipment and techniques for using the same. According to an example apparatus a device can be configured to estimate a location of the small cell eNodeB based on at least one of Global Positioning System (GPS) coordinates of the location of the small cell eNodeB and an RSRP measured at the small cell eNodeB, determine if the location of the small cell eNodeB is within a first region or a second region of a large cell transmission area, wherein the first and second regions do not overlap, and in response to determining which region the small cell eNodeB is deployed in, assign a PCI code from a respective group of available PCI codes to the small cell eNodeB.
DOMAIN CONTROL METHOD AND DOMAIN CONTROL DEVICE
An integrated control device, to implement automatic address assignment in a path spanning two or more administrative domains, and to implement communication between a plurality of administrative domains, acquires definition information that defines protocols used in each administrative domain from an inter-administrative domain communication protocol stack list table, acquires available addresses of each protocol in each administrative domain which can be used for communication between the respective administrative domains from an available address range table, acquires a communication route from a starting point administrative domain to an ending point administrative domain, specifies domains that use the respective protocols on the communication route by using the definition information, assigns protocol information such as available addresses of each protocol between the specified domains by using an available address range table and notifies the assigned address to each domain.
METHOD AND APPARATUS FOR MANAGING REHOMING OF USER ENDPOINT DEVICES IN A COMMUNICATION NETWORK
A system that incorporates teachings of the present disclosure may include, for example, a Domain Name System (DNS) server having a controller to receive new provisioning information for updating a Fully Qualified Domain Name (FQDN), and update the FQDN with the new provisioning information. The new provisioning information can include among other things a start time for rehoming one or more user endpoint devices (UEs) assigned to a current session border Controller (S/BC), a move-from record comprising a descriptor of at least the current S/BC, a move-to record comprising a descriptor of at least a new S/BC to which to rehome the one or more UEs, a transfer window representing a total time for the rehoming the one or more UEs to the new S/BC, and a pacing parameter for rehoming the one or more UEs to the new S/BC during the transfer window. Additional embodiments are disclosed.
DETECTING AND MITIGATING REGISTRAR COLLUSION IN DROP-ADD ACQUISITIONS OF DOMAIN NAMES
Systems and method for detecting domain name system (DNS) registrar collusion include a collusion detector at a registry. The collusion detector obtains information related to name acquisition requests submitted by DNS registrars attempting to acquire domain names in a drop pool of expired domain names and provides attempt sets containing the domain names targeted by the DNS registrars for acquisition. Each attempt set contains at least one targeted domain name that a respective DNS registrar attempted to acquire via at least one name acquisition request. The collusion detector determines a degree of similarity between two or more attempt sets corresponding to a pair of the DNS registrars, estimates a likelihood of collusion between the pair of DNS registrars based on the degree of similarity, and performs any mitigation action warranted by the likelihood of collusion.
CCN ROUTING USING HARDWARE-ASSISTED HASH TABLES
One embodiment provides a system that facilitates forwarding of packets with variable length names. During operation, the system receives a packet with a hierarchically structured variable length identifier (HSVLI) which comprises contiguous name components ordered from a most general level to a most specific level. The system performs a longest prefix match lookup by selecting an entry from a first data structure of entries. The entries indicate a name component, forwarding information for the name component, and a plurality of entry identifiers that chain an entry to another entry. If a size of the name component is less than or equal to a predetermined threshold, the system selects an entry based on the name component. If the size is greater, the system selects an entry based on a compressed key which can be a hash of the name component. The system also resolves collisions associated with the selected entry.