The Experts below are selected from a list of 180 Experts worldwide ranked by ideXlab platform

David J. Goodman - One of the best experts on this subject based on the ideXlab platform.

  • Network protocols for the cellular packet Switch
    IEEE Transactions on Communications, 1994
    Co-Authors: Kathleen S. Meier-hellstern, G.p. Pollini, David J. Goodman
    Abstract:

    Future wireless information networks will employ dense grids of base stations to support a high user population. While small cells mitigate capacity problems, lengthen battery life, and improve signal quality, the frequent movement of users across cell boundaries imposes new burdens on network controllers. Previous work suggests that a cellular packet Switch, based on distributed network control, can support high density personal communications. This paper proposes an allocation of control functions to elements of the cellular packet Switch and specifies the flow of information within the Switch. Message flows, defined for key procedures, form the foundation of a network layer protocol. Functionality is divided into the categories of call processing (set up and release), mobility management (location updates, handover, and path optimization), and radio resource management. Central Office Switches perform call processing. Mobility management and radio resource management are performed by interface units of the metropolitan area network at the heart of the cellular packet Switch. This architecture delivers advanced services with minimal impact on Central Office Switch software. It also relies on distributed, rather than Centralized mobility management to provide prompt, accurate communications as users move about. >

Jim Euchner - One of the best experts on this subject based on the ideXlab platform.

  • Atoms and Bits: Rethinking Manufacturing
    Research-Technology Management, 2015
    Co-Authors: Neil Gershenfeld, Jim Euchner
    Abstract:

    An Interview with Neil GershenfeldNeil Gershenfeld talks with Jim Euchner about the Internet of Things and the coming revolution in manufacturing.Neil Gershenfeld is a pioneer in understanding the boundary between the digital and physical worlds-how objects become data in the network and how data in the network become objects. The technology from his lab, MIT's Center for Bits and Atoms, has been seen and used in a wide variety of settings, from the Museum of Modern Art in New York and the World Economic Forum to rural Indian villages and innercity community centers. In this interview, he discusses the true nature of the Internet of Things, how distributed fab labs can enable anyone to make almost anything, the power of global knowledge sharing with innovation at the nodes, and the future of manufacturing using digital materials.JIM EUCHNER [JE]: The Internet of Things has become quite a buzzword. I think you define it more precisely than some do. Can you give your definition-what is the Internet of Things and what is it not?NEIL GERSHENFELD [NG]: Sure. I was part of a group that started what became called the Internet of Things. A decade or so ago, a group at MIT was working on embedding Internet protocols into devices and showing that, with a few hundred bytes of code and a dollar a part, you could implement a minimal IP stack. That meant that individual devices could talk to the Internet. So the simplest statement about the Internet of Things is that it means IP embedded in devices.A lot of the things called Internet of Things today are really BITNET of Things, and they're being done by people who don't understand the difference between the BITNET and the Internet. They are ignorant of the underlying architecture. There are a few core architectural principles that make the Internet work that you can apply to embedded devices. After 10 or so years, we've had to reconnect the future with the past concerning those architectural principles.BITNET was a connection of mainframes, and it was a very high barrier to entry. To expand the BITNET, you needed to add another mainframe, and that was a large investment that was Centrally managed. Users used terminals connected to the mainframes. It was similar to the old phone system: what a telephone did was defined not by the phone but by the Central Office Switch. Adding a new Central Office Switch was a big investment. One of the core principles that led to the Internet was the concept of what was called end-to-end, which roughly means that what the Internet does is defined by what you connect to it.The Internet transports packets; it uses a common representation for those packets. At the time it was emerging, there were many dissimilar networks, and the Internet settled on a common representation that could travel across them. But the Internet is really defined by what you connect to it, not by its physical construction. The Internet could grow by adding things to the edges, not by changing what was at the center. That enabled people to invent instant messaging and VoIP and video streaming and search engines, not by changing the architecture of the Internet but by innovating at the edges.Now the reason so many of the things called Internet of Things are actually the BITNET of Things is that people think in terms of devices, like a light sensor or a thermostat or a Switch, connected to a server that proxies its state to build an application. Manipulation of the sensor can be done through the Internet, but the state of the Switch or the light is not contained in the Switch or light, it's contained in the remote server. That means that to change the function of the device, you have to change the remote thing, not the local thing. You can't innovate at the edges because you need access to the Central controller.To be the Internet of Things in my definition, the light or the Switch has to be a full-fledged citizen of the Internet. …

  • Atoms and Bits: Rethinking Manufacturing: An Interview with Neil Gershenfeld: Neil Gershenfeld Talks with Jim Euchner about the Internet of Things and the Coming Revolution in Manufacturing
    Research-technology Management, 2015
    Co-Authors: Neil Gershenfeld, Jim Euchner
    Abstract:

    Neil Gershenfeld is a pioneer in understanding the boundary between the digital and physical worlds--how objects become data in the network and how data in the network become objects. The technology from his lab, MIT's Center for Bits and Atoms, has been seen and used in a wide variety of settings, from the Museum of Modern Art in New York and the World Economic Forum to rural Indian villages and inner-city community centers. In this interview, he discusses the true nature of the Internet of Things, how distributed fab labs can enable anyone to make almost anything, the power of global knowledge sharing with innovation at the nodes, and the future of manufacturing using digital materials. JIM EUCHNER [JE]: The Internet of Things has become quite a buzzword. I think you define it more precisely than some do. Can you give your definition--what is the Internet of Things and what is it not? NEIL GERSHENFELD [NG]: Sure. I was part of a group that started what became called the Internet of Things. A decade or so ago, a group at MIT was working on embedding Internet protocols into devices and showing that, with a few hundred bytes of code and a dollar a part, you could implement a minimal IP stack. That meant that individual devices could talk to the Internet. So the simplest statement about the Internet of Things is that it means IP embedded in devices. A lot of the things called Internet of Things today are really BITNET of Things, and they're being done by people who don't understand the difference between the BITNET and the Internet. They are ignorant of the underlying architecture. There are a few core architectural principles that make the Internet work that you can apply to embedded devices. After 10 or so years, we've had to reconnect the future with the past concerning those architectural principles. BITNET was a connection of mainframes, and it was a very high barrier to entry. To expand the BITNET, you needed to add another mainframe, and that was a large investment that was Centrally managed. Users used terminals connected to the mainframes. It was similar to the old phone system: what a telephone did was defined not by the phone but by the Central Office Switch. Adding a new Central Office Switch was a big investment. One of the core principles that led to the Internet was the concept of what was called end-to-end, which roughly means that what the Internet does is defined by what you connect to it. The Internet transports packets; it uses a common representation for those packets. At the time it was emerging, there were many dissimilar networks, and the Internet settled on a common representation that could travel across them. But the Internet is really defined by what you connect to it, not by its physical construction. The Internet could grow by adding things to the edges, not by changing what was at the center. That enabled people to invent instant messaging and VoIP and video streaming and search engines, not by changing the architecture of the Internet but by innovating at the edges. Now the reason so many of the things called Internet of Things are actually the BITNET of Things is that people think in terms of devices, like a light sensor or a thermostat or a Switch, connected to a server that proxies its state to build an application. Manipulation of the sensor can be done through the Internet, but the state of the Switch or the light is not contained in the Switch or light, it's contained in the remote server. That means that to change the function of the device, you have to change the remote thing, not the local thing. You can't innovate at the edges because you need access to the Central controller. To be the Internet of Things in my definition, the light or the Switch has to be a full-fledged citizen of the Internet. It needs to be able to implement services so that you can innovate by what you make the device do, not by changing the thing it's connected to. …

P.s. Parikh - One of the best experts on this subject based on the ideXlab platform.

  • ICNP - From formal specification to implementation: experience with protocol tools
    1993 International Conference on Network Protocols, 1
    Co-Authors: T.j. Baumgartner, D.m. Kristol, J.d. Milleville, P.s. Parikh
    Abstract:

    The authors describe efforts to develop the Q.931 protocol software for the 5ESS Central Office Switch. Q.931 is a layer-3 message-based, user/network interface protocol for the integrated services digital network (ISDN). The approach uses a single formal specification written in the Augmented Protocol Specification Language to model the 1.931 protocol as a set of communicating extended finite state machines. From this specification, tools validate the protocol and generate the bulk of a C language implementation. The authors successfully integrated this code, along with other handwritten code, into a working system in the lab. Their results demonstrate that protocol tools can be used effectively to develop high quality protocol software quickly from formal specifications. >

Kathleen S. Meier-hellstern - One of the best experts on this subject based on the ideXlab platform.

  • Network protocols for the cellular packet Switch
    IEEE Transactions on Communications, 1994
    Co-Authors: Kathleen S. Meier-hellstern, G.p. Pollini, David J. Goodman
    Abstract:

    Future wireless information networks will employ dense grids of base stations to support a high user population. While small cells mitigate capacity problems, lengthen battery life, and improve signal quality, the frequent movement of users across cell boundaries imposes new burdens on network controllers. Previous work suggests that a cellular packet Switch, based on distributed network control, can support high density personal communications. This paper proposes an allocation of control functions to elements of the cellular packet Switch and specifies the flow of information within the Switch. Message flows, defined for key procedures, form the foundation of a network layer protocol. Functionality is divided into the categories of call processing (set up and release), mobility management (location updates, handover, and path optimization), and radio resource management. Central Office Switches perform call processing. Mobility management and radio resource management are performed by interface units of the metropolitan area network at the heart of the cellular packet Switch. This architecture delivers advanced services with minimal impact on Central Office Switch software. It also relies on distributed, rather than Centralized mobility management to provide prompt, accurate communications as users move about. >

Neil Gershenfeld - One of the best experts on this subject based on the ideXlab platform.

  • Atoms and Bits: Rethinking Manufacturing
    Research-Technology Management, 2015
    Co-Authors: Neil Gershenfeld, Jim Euchner
    Abstract:

    An Interview with Neil GershenfeldNeil Gershenfeld talks with Jim Euchner about the Internet of Things and the coming revolution in manufacturing.Neil Gershenfeld is a pioneer in understanding the boundary between the digital and physical worlds-how objects become data in the network and how data in the network become objects. The technology from his lab, MIT's Center for Bits and Atoms, has been seen and used in a wide variety of settings, from the Museum of Modern Art in New York and the World Economic Forum to rural Indian villages and innercity community centers. In this interview, he discusses the true nature of the Internet of Things, how distributed fab labs can enable anyone to make almost anything, the power of global knowledge sharing with innovation at the nodes, and the future of manufacturing using digital materials.JIM EUCHNER [JE]: The Internet of Things has become quite a buzzword. I think you define it more precisely than some do. Can you give your definition-what is the Internet of Things and what is it not?NEIL GERSHENFELD [NG]: Sure. I was part of a group that started what became called the Internet of Things. A decade or so ago, a group at MIT was working on embedding Internet protocols into devices and showing that, with a few hundred bytes of code and a dollar a part, you could implement a minimal IP stack. That meant that individual devices could talk to the Internet. So the simplest statement about the Internet of Things is that it means IP embedded in devices.A lot of the things called Internet of Things today are really BITNET of Things, and they're being done by people who don't understand the difference between the BITNET and the Internet. They are ignorant of the underlying architecture. There are a few core architectural principles that make the Internet work that you can apply to embedded devices. After 10 or so years, we've had to reconnect the future with the past concerning those architectural principles.BITNET was a connection of mainframes, and it was a very high barrier to entry. To expand the BITNET, you needed to add another mainframe, and that was a large investment that was Centrally managed. Users used terminals connected to the mainframes. It was similar to the old phone system: what a telephone did was defined not by the phone but by the Central Office Switch. Adding a new Central Office Switch was a big investment. One of the core principles that led to the Internet was the concept of what was called end-to-end, which roughly means that what the Internet does is defined by what you connect to it.The Internet transports packets; it uses a common representation for those packets. At the time it was emerging, there were many dissimilar networks, and the Internet settled on a common representation that could travel across them. But the Internet is really defined by what you connect to it, not by its physical construction. The Internet could grow by adding things to the edges, not by changing what was at the center. That enabled people to invent instant messaging and VoIP and video streaming and search engines, not by changing the architecture of the Internet but by innovating at the edges.Now the reason so many of the things called Internet of Things are actually the BITNET of Things is that people think in terms of devices, like a light sensor or a thermostat or a Switch, connected to a server that proxies its state to build an application. Manipulation of the sensor can be done through the Internet, but the state of the Switch or the light is not contained in the Switch or light, it's contained in the remote server. That means that to change the function of the device, you have to change the remote thing, not the local thing. You can't innovate at the edges because you need access to the Central controller.To be the Internet of Things in my definition, the light or the Switch has to be a full-fledged citizen of the Internet. …

  • Atoms and Bits: Rethinking Manufacturing: An Interview with Neil Gershenfeld: Neil Gershenfeld Talks with Jim Euchner about the Internet of Things and the Coming Revolution in Manufacturing
    Research-technology Management, 2015
    Co-Authors: Neil Gershenfeld, Jim Euchner
    Abstract:

    Neil Gershenfeld is a pioneer in understanding the boundary between the digital and physical worlds--how objects become data in the network and how data in the network become objects. The technology from his lab, MIT's Center for Bits and Atoms, has been seen and used in a wide variety of settings, from the Museum of Modern Art in New York and the World Economic Forum to rural Indian villages and inner-city community centers. In this interview, he discusses the true nature of the Internet of Things, how distributed fab labs can enable anyone to make almost anything, the power of global knowledge sharing with innovation at the nodes, and the future of manufacturing using digital materials. JIM EUCHNER [JE]: The Internet of Things has become quite a buzzword. I think you define it more precisely than some do. Can you give your definition--what is the Internet of Things and what is it not? NEIL GERSHENFELD [NG]: Sure. I was part of a group that started what became called the Internet of Things. A decade or so ago, a group at MIT was working on embedding Internet protocols into devices and showing that, with a few hundred bytes of code and a dollar a part, you could implement a minimal IP stack. That meant that individual devices could talk to the Internet. So the simplest statement about the Internet of Things is that it means IP embedded in devices. A lot of the things called Internet of Things today are really BITNET of Things, and they're being done by people who don't understand the difference between the BITNET and the Internet. They are ignorant of the underlying architecture. There are a few core architectural principles that make the Internet work that you can apply to embedded devices. After 10 or so years, we've had to reconnect the future with the past concerning those architectural principles. BITNET was a connection of mainframes, and it was a very high barrier to entry. To expand the BITNET, you needed to add another mainframe, and that was a large investment that was Centrally managed. Users used terminals connected to the mainframes. It was similar to the old phone system: what a telephone did was defined not by the phone but by the Central Office Switch. Adding a new Central Office Switch was a big investment. One of the core principles that led to the Internet was the concept of what was called end-to-end, which roughly means that what the Internet does is defined by what you connect to it. The Internet transports packets; it uses a common representation for those packets. At the time it was emerging, there were many dissimilar networks, and the Internet settled on a common representation that could travel across them. But the Internet is really defined by what you connect to it, not by its physical construction. The Internet could grow by adding things to the edges, not by changing what was at the center. That enabled people to invent instant messaging and VoIP and video streaming and search engines, not by changing the architecture of the Internet but by innovating at the edges. Now the reason so many of the things called Internet of Things are actually the BITNET of Things is that people think in terms of devices, like a light sensor or a thermostat or a Switch, connected to a server that proxies its state to build an application. Manipulation of the sensor can be done through the Internet, but the state of the Switch or the light is not contained in the Switch or light, it's contained in the remote server. That means that to change the function of the device, you have to change the remote thing, not the local thing. You can't innovate at the edges because you need access to the Central controller. To be the Internet of Things in my definition, the light or the Switch has to be a full-fledged citizen of the Internet. It needs to be able to implement services so that you can innovate by what you make the device do, not by changing the thing it's connected to. …