A device and method for supporting communication between various types of secure elements is provided. The device comprises a protocol converter, and the protocol converter comprises: a plurality of communication interfaces for correspondingly coupling with each type of secure element; and a management module coupled with each communication interface; wherein different types of secure elements follow different bottom level communication protocols, each communication interface is configured to follow the same bottom level communication protocol as the secure element it correspondingly couples with; the management module is configured to follow the same upper level communication protocol so as to realize a protocol conversion between any bottom level communication protocol and the upper level communication protocol, and the management module is used for dynamically establishing a connection channel for any two of the communication interfaces, thus realizing a corresponding communication between the secure elements of any two different types.

A system and method for allowing legacy devices to be discovered on a DotDot network is disclosed. The system includes a gateway device to interface between DotDot devices and legacy devices. In some embodiments, the gateway device has a plurality of network interfaces to communicate with these legacy devices. The gateway device discovers the legacy devices that it can communicate with. The gateway device then presents information about these legacy devices in a Resource Directory. In some embodiments, the Resource Directory is maintained within the gateway device. In other embodiments, the gateway device utilizes a Resource Directory that exists on the DotDot network.

Access points can be mounted in a variety of locations or orientations and can support multiple communications protocols. In some embodiments, an access point includes a main housing and a front housing. The main and front housing are connected by a hinge. A Wi-Fi antenna is included in the front housing in some embodiments. The access point is configured for use in either an open or closed position. When mounted in a vertical position, the front housing can be lowered into a horizontal position, which facilitates a preferred orientation of an antenna with respect to the ground. A first set of cooling fins serves to maintain components of the access point offset from a wall to which the access point is mounted. This facilitates airflow. Additional fins act as a spacer between the main housing and the front housing when the access point is used in a closed position. This facilitates air flow around both sides of the main housing.

Access points which can be mounted in a variety of locations or orientations and can support multiple communications protocols are described. The access point includes a main housing, e.g., main body, and a front housing connected together by a hinge. A Wi-Fi antenna is included in the front housing in some embodiments. The access point can be used in an open or closed position. When mounted in a vertical position the front housing can be lowered into a horizontal position facilitating preferred antenna orientation. A first set of cooling fins serves to keep the internal components of the access point off a wall when the access point is wall mounted facilitating air flow. Additional fins act as a spacer between the main housing and the front housing when the access point is used in a closed position facilitating air flow around both sides of the main housing.

One example includes a capability gateway that is comprised of a receiver and a transmitter. The receiver receives, from a ground station associated with a satellite system, a standard protocol associated with the ground station and a non-standard alternate protocol that includes alternate service layers inserted into an inter-layer boundary of standard radio layers, the alternate service layers providing end-to-end signaling between the capability gateway and a user equipment. The transmitter transmits the non-standard alternate protocol to the user equipment.

A system and method for allowing legacy devices to be discovered on a DotDot network is disclosed. The system includes a gateway device to interface between DotDot devices and legacy devices. In some embodiments, the gateway device has a plurality of network interfaces to communicate with these legacy devices. The gateway device discovers the legacy devices that it can communicate with. The gateway device then presents information about these legacy devices in a Resource Directory. In some embodiments, the Resource Directory is maintained within the gateway device. In other embodiments, the gateway device utilizes a Resource Directory that exists on the DotDot network.

The disclosed technology separates session management function signaling from the AMF. In particular, an SMF key is created for each SMF following the AMF generating an SM context request that contains gNB information and UE subscription information. Each PDU session creates a direct connection between the SMF and a local gNB. The gNB communicates with each SMF directly over a new interface (N3-C) for session management that is independent of the N2 interface used by the gNB to communicate with the AMF for mobility management. In this way, each SMF independently handles NAS signaling with the UE, using the SMF key and gNB related session-management signaling over an independent interface with the gNB. This removes the burden of relaying these communications through the AMF, which is then freed up to solely to handle mobility management signaling, resulting in an improved architecture.

The present disclosure relates to a pre-5.sup.th-Generation (5G) or 5G communication system to be provided for supporting higher data rates Beyond 4.sup.th-Generation (4G) communication system such as Long Term Evolution (LTE). Embodiments herein provide an oneM2M system. The oneM2M system includes an interworking proxy entity (IPE) and a oneM2M client. The IPE is configured to discover resources hosted by a RESTful server. The RESTful server is external to the oneM2M system. The IPE is configured to create an application entity (AE) resource associated with the RESTful server. The IPE is configured to create one or more containers with labels indicating information of resources associated with the RESTful server. Each container includes a content instance (CI) resource having a representation of mapped resources associated with the RESTful server. Further, the IPE is configured to send service subscription information update about the discovered RESTful server to a middle node. The oneM2M client is configured to send a request to the IPE to discover the container from the IPE using the labels.

One example includes a capability gateway that is comprised of a receiver and a transmitter. The receiver receives, from a ground station associated with a satellite system, a standard protocol associated with the ground station and a non-standard alternate protocol that includes alternate service layers inserted into an inter-layer boundary of standard radio layers, the alternate service layers providing end-to-end signaling between the capability gateway and a user equipment. The transmitter transmits the non-standard alternate protocol to the user equipment.

A device on a network is searched for by using the first protocol, and the first device information is acquired. The second device information about the second protocol is acquired from a device on the network. The second device information is preferentially processed over the first device information.