Abstract: Various mechanisms are disclosed for a service domain charging system that can interact with underlying networks. A service domain charging architecture is defined with several logical functions. Service-based charging types may be and applied to existing event, session, online, and offline charging mechanisms. Service domain charging messages may be exchanged over the X, Y, Z reference points. An E reference point may be used for interfacing with a service domain billing system, and a B reference point may be used between a service domain billing system and underlying network's billing system.

Abstract: Techniques are disclosed for Machine-to-Machine (M2M) Announce procedures that allow advertisement machine-to-machine service capabilities layer resources and subresources. Resource structures and signal flows of the various disclosed embodiments are defined.

Abstract: Systems, methods and apparatus for managing machine-to-machine (M2M) entities are disclosed. Included herein is a method that may include implementing one or more management layers for managing M2M entities in an M2M environment. The method may also include using a plurality of management layers to manage a M2M area network, wherein the M2M area network may include one or more M2M end devices. The M2M end devices may include, for example, an M2M gateway and/or an M2M device. The management layers may include any of an application management layer, service management layer, network management layer and a device management layer. The management layers may provide any of configuration management, fault management, and performance management of the M2M entities.

Abstract: A system is disclosed for orchestrating services. Service orchestration profiles specify attributes defining desired services. The service orchestration profiles may be distributed amongst nodes and hierarchically related to each other. Service orchestration management functions process the information in the service orchestration profiles in order to determine the desired services and use the information to implement the desired services. The service orchestration management functions may be hierarchically related to each other.

Abstract: Methods, systems, and devices may be used to annotate and store “semantics of normal resources” (hereinafter resource semantics). These methods, systems, and devices may be a part of a functional architecture for semantics support and allow for semantics based query. Also methods, systems, and devices associated with a semantics child resource may be created within a resource in order to represent semantics information.

Abstract: Methods, devices, and systems for migration or sharing of existing M2M service layer sessions are disclosed. In one embodiment, a Session Migration and Sharing Function (SMSF) performs the migration or sharing of a M2M service layer session. Various forms of service layer session context may be used to enable the migration and sharing of M2M service layer sessions.

Abstract: A system is disclosed for publication and discovery of M2M/IoT services. An M2M gateway system receives resource descriptions from M2M/IoT devices. The gateway system creates for each received resource description an individual web services description language file (WSDL-I file) recording information about the resource. The gateway identifies groups of services with similar characteristics and generates for each identified group a web service description file (WSDL-G file) recording information regarding the group. The WSDL-G files are communicated to a service registry infrastructure (SRI). A consumer system queries the SRI for services satisfying particular criteria and receives WSDL-G files for groups of services that satisfy the criteria. The consumer system requests the WSDL-I files corresponding to a selected WSDL-G files from the gateway.

Abstract: The service layer may leverage the access network infrastructure so that applications on a device may bootstrap with a machine-to-machine server without requiring provisioning beyond what is already required by the access network.

Abstract: A machine to machine (M2M) service layer can facilitate acquiring and providing location information for use by M2M devices. The service layer can also ensure that privacy controls are maintained and enforced for location information. A device can report its location and its privacy preferences to a service layer device. Other devices can receive this location information subject to qualifying to receive it based on the privacy preferences. Devices in an area may advertise services with the service layer acting as a filter and relay point ensuring that such advertisements satisfy the privacy policies of the devices involved.

Abstract: Method and apparatus for supporting machine-to-machine (M2M) communications in a hierarchical network architecture including an M2M gateway are disclosed. An M2M entity, (such as M2M device, M2M gateway, or M2M network entity), may perform a service capability discovery procedure to discover an M2M service capability entity that may provide an M2M service capability, and register with the discovered M2M service capability entity. The address or identity of the service capability entity may be pre-configured or obtained from the dispatcher server. The M2M entity may indicate a support M2M service identifier and receive an identity or address of the M2M service capability entity mapping the service identifier. The gateway may advertise M2M service identifiers supported by the gateway so that the M2M device may access the gateway if there is a match. The address of M2M service capability entities may be obtained from the core network.

Abstract: Apparatuses, computer readable media, and methods are disclosed for supporting services at an application service layer (ASL). The method may include responding to receiving batched requests from an entity by processing the batched requests, and sending a response to the batched requests to the entity. The method may include sending a separate response to each request indicated in the batched request to the entity, or sending a batched response. Two or more batched requests may have the same operation and the operation may be only specified once. The operation may be determined based on a name of the batched requests or an attribute of the batched request. The request may be determined to be a batch request based on a name of the batched request, attributes associated with the batched request, or an address to which the batched request is addressed. The ASL may be a service capability layer.

Abstract: A method for forecasting thermal runaway safety of a full battery by a computer is provided and including receiving a self heat generation onset temperature T0 of a first power battery, wherein the first power battery is a half cell; calculating a maximum temperature Tmax of thermal runaway of the first power battery based on a thermal runaway reaction kinetic model stored in the computer, calculating a maximum temperature rise ?T by making difference between the maximum temperature Tmax and the self heat generation onset temperature T0; and judging the thermal runaway safety of the first power battery by the relationship between the self heat generation onset temperature T0 and the maximum temperature rise ?T.

Abstract: A system is disclosed for orchestrating services. Service orchestration profiles specify attributes defining desired services. The service orchestration profiles may be distributed amongst nodes and hierarchically related to each other. Service orchestration management functions process the information in the service orchestration profiles in order to determine the desired services and use the information to implement the desired services. The service orchestration management functions may be hierarchically related to each other.

Abstract: Methods, devices, and systems for migration or sharing of existing M2M service layer sessions are disclosed. In one embodiment, a Session Migration and Sharing Function (SMSF) performs the migration or sharing of a M2M service layer session. Various forms of service layer session context may be used to enable the migration and sharing of M2M service layer sessions.

Abstract: Method and apparatus are described for delivering triggers and small data. In an embodiment, a receiver may be configured to receive a trigger or small data packet, and a transmitter may be configured to transmit a subscriber information request to see whether a subscriber is present. The receiver may be further configured to receive an identity of a second node on a condition that the subscriber is present.

Abstract: A detachable floating shaver includes a head, a casing having a third through hole, a main housing, a first floating member, and a second floating member. Through the connection and positioning relationship between the two parent and child pivot portions, that is, the first floating member and the second floating member, the head can achieve a cross rotation relative to the main housing. The second floating member has a connecting member; through the detachable connection between the second floating member and the connecting member, the head of the shaver is detachably connected, which is convenient for replacement, cleaning and maintenance and is more practical. The shaver can achieve 360° rotation through two parent and child pivot portions and two elastic sleeves, and the effect of floating contact of the shaver with the user's face is good.

Abstract: A method of accessing services affiliated with a service provider is disclosed. An issuer performs a bootstrap procedure with the at least one discovered service provider. The issuer performs a discovery procedure to determine available service capability layers (SCLs) supported by the at least one discovered service provider. The issuer transmits a domain name system-based service discovery (DNS-SD) query from the issuer to a DNS-SD M2M service discovery function (MSDF) server. The DNS-SD MSDF server is provisioned with SCL discovery records. The DNS-SD MSDF server is registered with a public DNS registrar entity. The SCL discovery records include, for each SCL, a type of M2M service capabilities supported by each SCL and a class of M2M services supported by each SCL. The issuer receives SCL discovery records from the DNS-SD MSDF server in response to the DNS-SD query.

Abstract: The service layer may leverage the access network infrastructure so that applications on a device may bootstrap with a machine-to-machine server without requiring provisioning beyond what is already required by the access network.