KR20010071878A - Distributed local and wide area network independent of connection media supported in networked devices, and managed by the networked devices - Google Patents

Abstract

Dynamically configurable networks include data stations and radio protocol stations. The wireless protocol station and at least one data station form a local area network. Separate local area networks are connected to each other via wireless protocol stations. The wireless protocol station and data station have a physical layer protocol suitable for the physical layer, whereby the wireless protocol station has all the physical layer protocols of the data station to which this station is currently connected so as to dynamically support various media. The wireless protocol station and data station also have a service application layer protocol suitable for the service layer and a service access point protocol between the service layer and the physical layer. The service application layer of the data station provides data services. Data between data stations, or data between a data application and a wireless protocol station, is physically exchanged over a communication link using a physical layer protocol. The data service is accessed via a service access protocol.

Description

DISTRIBUTED LOCAL AND WIDE AREA NETWORK INDEPENDENT OF CONNECTION MEDIA SUPPORTED IN NETWORKED DEVICES, AND MANAGED BY THE NETWORKED DEVICES}

The design architecture of existing mobile phones offers users a convenient compact product that is well suited for voice communications. However, this existing design architecture reveals limitations. The design architecture is closed. Upgrades, applications or accessory products cannot be easily added after the first purchase of a mobile phone. In new generations of products, new services will be created constantly. Mobile phone manufacturers will not be able to cope with these services ahead of time, and adding new services will mean redesigning their products. Thus, the life of the product will be significantly reduced. All mobile phone applications must use displays and generic keypads that must be the same size. If a generic user interface is used, the assumption is that the display will increase the size of the product, and that all users will be familiar with the computer. This approach is expensive and only valid for upstream products, meeting only a limited percentage of demand in the consumer market. The user interface is integrated into the mobile phone, providing a means for accessing and running all available data applications. Due to the expected increase in data functionality, the user interface will be more complex and the user will be less familiar with it. The reduction in product size and thus the pressure to reduce display size for manufacturing companies adds to the complexity. Ergonomics is also tricky to keep up with the future expansion of data services. This is more easily highlighted in one example. During a mobile call, one person sends a report to the other party by e-mail. Both sides discuss this report and want to see it during the conversation. In order to view or modify the report, the conversation is interrupted because each must take the phone away from the ear. If the product has speakerphone capability, conversations can continue but privacy is reduced. Many data applications exist with different ergonomic requirements. For example, compare the requirements for mobile video conferencing products with the requirements for an all-weather sports headset communicator. The latter does not require a large display screen.

Following mobile phone systems, there are high-end consumer electronics network systems. These high-end network systems provide so-called 'plug and play' distributed computing services that provide generic hardware compatibility and automatic configuration of software drivers for required services. Once these systems are available, the user will simply 'plug in' to access the necessary services.

The importance of data communication in a mobile communication environment is expected to be greater. It is inevitable that the mobile phone itself can be regarded as a device for providing services in a mobile distributed computing network. Users need easy access to the services provided in these distributed networks. If the mobile network can also interact with fixed propriety networks currently under development, the use of mobile phones in home environments can be facilitated. Fixed network systems under development that correspond to the importance of mobile phones are:

HAVI-This system provides access to the home network of home appliances. The home network uses an IEEE 1394 standard bus with a bandwidth of 400 Mbps.

JINI-This is a communication layer based on JAVA. JINI requires large processing power, fast memory, and large network bandwidth (around 100 Mbps). To provide a fixed home appliance network, there are plans to merge JINI with HAVI.

USB-This is a plug and play bus system with 12 Mbps bandwidth suitable for fixed area networks. Hardware access to the bus is standard.

These fixed networks target large bandwidths that are relatively expensive. Mobile phone environment generally has the following differences.

The maximum available bandwidth will typically be on the order of 2 Mbps and will vary with user mobility.

The transmission of network configuration data must be limited because the user will pay for all data to be sent to the public. Therefore, there is a network limitation imposed by the mobile communication environment that all fixed networks do not have. The number of devices connected to the mobile network at the same time will be small. Cost and size constraints may make the JAVA virtual machine inapplicable to most devices, especially the mobile phone itself.

The lifetime of the mobile network is short. Wide area service coverage is limited for duration of calls. The network is configured to meet the requirements of the user whenever required.

Currently, there are a variety of solutions under development to provide remote wireless point to point and point to multi-point connectivity. In particular, Bluetooth, Home RF and IrDA technologies are attracting attention for mobile phone products.

This specification claims priority to US Provisional Application No. 60 / 133,901, filed May 13, 1999.

The present invention relates to a local area network (LAN) and a wide area network (WAN) of networked devices. More specifically, the present invention relates to data devices such as networked devices that provide data services in a mobile environment.

1 illustrates a local area network in accordance with the present invention.

2 illustrates a telecommunications network in accordance with the present invention.

3 illustrates another telecommunication network in accordance with the present invention.

4 illustrates access to a network service through a MADI service access point.

5 illustrates the interaction of stations within a MADI local area network node.

6 shows a protocol station of a MADI-WAN node providing interconnection to an external node.

7 illustrates the positioning of a protocol layer in MADI-WAN.

8 is a diagram illustrating inter-node data transmission of MADI-WAN.

9 illustrates a structure of a parent transport packet.

FIG. 10 illustrates a transport packet from a PDA to a mobile telephone in a first node. FIG.

11 illustrates a transport packet from a mobile phone of a first node to a mobile phone of a second node.

Fig. 12 shows a transport packet from the PDA of the second node to the mobile telephone of the first node.

13 shows a service station record in the MADI Service List.

14 is a diagram showing the overall structure of a MADI service list.

15 illustrates a transmit and receive service transport interface structure.

16 illustrates service data encapsulation.

17 illustrates a directory record format of a MADI controller.

18 shows the whole directory structure.

FIG. 19 illustrates directory contents of directory records in multiple MADI controllers. FIG.

20 illustrates a MADI-SAP software architecture.

21 illustrates MADI transmission management.

22 illustrates a MADI transmit buffer structure.

FIG. 23 illustrates fixed network mobility using MADI. FIG.

It is an object of the present invention to provide a new architecture for distributed areas and telecommunication networks.

Another object of the present invention is to provide a mobile network managed by virtually networked devices, without the need for a central server or service provider support.

It is a further object of the present invention to provide a mobile device in a mobile network, which is inexpensive to purchase and use, and a limited bandwidth so that mobile network overhead is not memory or bandwidth intensive.

Another object of the present invention is to provide functional modularity in a mobile network.

Another object of the present invention is to provide a network architecture in which current data services and new data services can be easily updated or added.

According to the present invention, a dynamically configurable network,

A first data station comprising a first service application layer protocol and a first physical layer protocol for providing a first data service;

A first wireless protocol station comprising a second service application layer protocol, the first wireless protocol station physically communicating data with the first data station via a first communication link using the first physical layer protocol. Configured to exchange and access the first data service through peer-to-peer communication using a service access point protocol included in the first data station and the first wireless protocol station, At the first data station, the service access point protocol is configured to transmit data between a first service application layer protocol and the first physical layer protocol, respectively, and at the first wireless protocol station, the service access point protocol is Prize A second service application layer protocol and the second being configured to transmit data between the first physical layer protocol;

The first data station and the first wireless protocol station form a first local area network in the dynamically configurable network.

The present invention provides that, via a service access point protocol included in a data and protocol station, stations can be added to a node or nodes, at a layer between the service application layer and the physical layer, whereby It is based on creating networks of various sizes that are configured by the user or automatically.

Preferably, the network comprises a second wireless protocol station at a second local area network node, whereby a dynamically configurable telecommunication network consisting of a plurality of local area networks interconnected with the concept of a dynamically configurable local area network. Expands to

Preferably, data transmission between stations is packet switched.

Preferably, the controller stations of the network, i.e., stations that are part of the current data service request, are dynamically or directly generated indirect network nodes and stations, to support direct and indirect transmissions with minimal control and routing data overhead. Operates based on a directory containing addresses. In indirect transmission, the intermediate station updates the intermediate destination of the next station based on the directory entry containing the next station node and station address.

Preferably, the directory in the station is updated through a station scanning process to obtain the node addresses and station addresses of newly acquired stations.

Throughout the drawings, like reference numerals refer to like features.

As will be described in detail hereinafter, the present invention broadly provides a framework for providing mobile auxiliary device interoperability (MADI) and for allowing mobile phones and their peripheral devices to interact in a telecommunications network consisting of a number of interconnected local area networks. Provide (framework).

1 shows a local area network 1 according to the invention, i.e. a MADI local area network, comprising a protocol station (PS) 2, an associated data station (DS) device, a printer 3, a television set 4 ), Music center 5, personal computer 6 (above, fixed data station), watch 7, camera 8, music player 9, personal digital assistant (PDA) 10 And a headset 11 (above, a wireless mobile data station). The protocol station 2 provides a two-way over-the-air to the base station services of the mobile communication network (not shown in detail) and via a simple numeric keypad in stand-alone performance. Only user voice-only functionality can be provided. Such standalone performance is well known in the field of cellular telephony. The data service is typically at the MADI protocol station 2 and the data services may be transparent to the user and are typically transparent. In this respect, the protocol station 2 is a transparent data pipe that provides a gateway to the data services for the DS devices 3 to 11. Typically, all data applications are serviced through subordinate DS devices 3-11. DS devices 3 to 11 have a user interface that is well suited to the particular task of the device. Various DS devices 3-11 allow the user to select a user interface. For example, if a data station device is used to perform speakerphone voice communication, a powerful PS transmitter may be removed from the backpack or ear, for example, and placed in a backpack or briefcase. Some data stations 3-11 may be specifically designed for use with a portable music player that 'records' a track from certain Internet data services, for example an Internet service. The MADI architecture is open, facilitating the addition of new services and data station products without substantially changing the protocol station 2.

The data station devices 3 to 11 are configured to communicate with the protocol station 20 via a standardized communication link to form a local area network 1. The physical interface within the local area network may consist of various different standards, such as a Bluetooth RF link to headset 11 or an IrDA connection to printer 3. Since the protocol station 2 of the local area network 1 can communicate with another PS capable of supporting its own local area network, this concept allows any data station device to be connected to any other place via mobile services. Can be extended to a telecommunication network.

2 shows one configuration of a telecommunications network, that is, a MADI telecommunications network, in accordance with the present invention, and FIG. 3 shows another configuration of the MADI telecommunications network.

In the system shown in FIG. 2, the local area network 2 has a local data station (LDS) 21, 22, and 23 and a local protocol station (LPS) 24, a remote network remote from the local area network 20. At 25 there is a remote protocol station (RPS) 26 and remote data stations 27, 28 and 29. In this system, all the devices are accessible to each other and are considered to be devices connected by the MADI network shown schematically in FIG. In order for the local data station in the local network 20 to communicate with the remote data station of the remote network 25, the continuous path for communication is as follows. The local LDS communicates with the local LPS, which communicates with the remote RPS, which communicates with the remote RDS. Therefore, it can be seen that the message routing requirements of the MADI network 30 are specific to the mobile environment. By their nature, mobile communication products are moving. Access to peripheral devices is temporary. This means that the MADI network 30 must be dynamically configured whenever required. It may also require the LDS user to access another LDS device without a PS in the local area network. For example, a local personal digital assistant (PDA) user may want to print an agenda with a local printer. You certainly do not need a PS. It is important that the MADI system be as simple and flexible as possible.

The network needs to be used in an efficient manner and must provide a simple means for accessing the desired device. To this end, the following facilities, ie several device control coordinations at the same time, control information (sending commands from one device to another) and data content (sending data streams from one device to another) are transmitted in a timely and efficient manner. And a simple user configuration of a timely and appropriate size tailored to the user's special needs. Because this network is designed for mobile products, power, memory overhead, and remote network transmission costs are minimized. In addition, the network is self-managing, multiple device access protocols supported, new device access protocols can be easily added, and interfaces to other fixed appliance networks are provided.

In order to provide these services, a network management system is required and it is a MADI system.

The MADI system according to the present invention is a network management system, which can be regarded as a distributed computing platform. The basic purpose of the MADI system is to ensure that products can interoperate to perform application tasks. To facilitate a generic interface to the MADI network, this architecture defines a set of application programming interfaces (APIs). As will be discussed in detail later, the MADI architecture is open, lightweight, platform-independent, with structurally neutral details, provides an infrastructure to control the routing and processing of data in a timely manner, and supports the MADI architecture. Support legacy devices that are not used, support future devices through software-based mechanisms, enable devices to represent multiple user interfaces, accommodate both user needs and manufacturer needs for brand differentiation, It facilitates the transparent transmission of peer-to-peer communication data to support communication protocols such as those used in fixed network systems (eg JINI) and higher layer network systems.

Services provided to a MADI system are distributed across a network within connected devices. Services run under the execution environment of the device and are accessible through a well-defined interface. In this respect, it is noted that different devices may use different execution environments. These services are on top of the peer to peer communication layer provided by the MADI system. The MADI layer according to the present invention provides a mechanism for data exchange between these device entities, and provides facilities for characterizing this data exchange organization. The nature of the service interface is not related to MADI. Services may be provided by device manufacturers or may be added by third party merchant services (such as new merchant applications added to the manufacturer's device). Services are required and provided through the MADI Message Transfer Model, which provides a complete generic software model that is flexible enough to be implemented in multiple software systems and languages.

4 shows access to a network service through a MADI service access point 40. The SAP 40 resides in all MADI compliant stations and data station devices and protocol stations and provides a peer-to-peer communication layer between service entities. In Fig. 4, the service layer 41 is shown.

5 illustrates the interaction of stations within a MADI local area network node (node 0) 50. Node 50 includes data stations (DS) 51, 52 and protocol station (PS) 53. Stations 51 to 53 all have different MADI layers according to the present invention.

6 shows a protocol station 53 at node 50 of a wide area network (MADI-WAN) providing interconnection to external nodes 60, 70 (node 1, node n, respectively). The outer node 60 includes data stations 61 and 62 and protocol station 63. The outer node 70 includes data stations 71 and 72 and a protocol station 73. MADI-WAN consists of multiple local area network nodes interconnected through protocol stations. A MADI Service Access Point of the type shown in FIG. 4 facilitates the distribution of the services provided by each station everywhere else in the MADI-WAN. Protocol station 53 provides interconnection to external nodes 60 and 70. 6 shows all possible interconnection paths. Stations in a MADI network are either controller stations or controlled stations. The controller station requests one service or several services from the controlled station, and possesses a network view or network knowledge. The controller station knows all the services available and the access mechanism to get them. The controlled station acts like a dumb station and responds only to a given command. They do not have information about the network. This reduces the need for unnecessary network configuration transmissions and limits the transmission of directory information. The remaining controller stations also control the controller stations because they will also serve the MADI network.

FIG. 7 illustrates the location of the protocol layer in MADI-WAN of the type shown in FIG. 6. Shown are the protocol layer stacks for the data station and the protocol station.

The data station or protocol station has the following protocol layer.

Low level physical media layer 80-87 providing a physical interface to other stations. There will be different media interface choices in the MADI network 30. One station may have access to multiple media options, such as UMTP (M1), Bluetooth (M2), IrDA (M3) or other media options (M4). Other media options are, for example, HomeRF or RS232.

MADI SAP layer (90-97) above the low-level physical media layer (80-87), which provides a network and data link layer for MADI communication. The MADI SAP layer 90-97 rarely depends on the low level physical media layer 80-87. Some stations in this network can also support higher layer networks such as JINI. In these stations, such as those in the data stations 98, 99, the MADI SAP layer 91, 95 is directly below the higher network layer, eg, each JINI layer 100, 101 given. In this case, the MADI layer extends the higher layer network to a higher layer compliant station of the MADI network.

Service layer 110-117, which is above the MADI SAP layer 90, 92, 93, 94, 96, and 97, or optionally above the JINI layer 100, 101. In FIG. 7, the data station 98 is in the first local area network 118, the data station 99 is in the second local area network 119, and the networks 118, 119 are remotely connected to each other. .

The protocol stations include all the media options of the data station devices they support, given by way of example M1 to M4. Data stations typically have fewer media options, or even only one media option.

To facilitate simultaneous control and data transfer between network entities, and to provide maximum flexibility for data transfer, all network transmissions are in the form of Transport Packets as shown in Table I below. have.

Packet segment Field identifier Size in bytes Explanation Justice DNODE Destination Node Identifier One Identify the node to which the packet will be sent. The address range is 0 to 255. DNODE is allocated for the duration of the network, and the range is full. DSTATION Destination Station Identifier One Identify the station of the node to which the packet will be sent. The address range is 0 to 255. DSTATION is allocated for the duration of the network, and the range is local to the node. data COMMAND command identifier One Materializes instruction instructions. The value ranges from 0 to 255. Merged instruction instructions are supported. In a merged instruction, the contents of another instruction are merged into consecutive INFO bytes. ILENINFO field length One Display the length of the INFO field. The range is 0 to 255. INFO Information N Length of data content defined by DLEN. Note: The INFO contains the command content for the merged command instructions. sauce SNODE source node identifier One Identify the node sending the packet. The address range is 0 to 255. SNODE is allocated for the duration of the network, and the range is full. SSTATION source station identifier One Station identification of the node sending the packet. The address range is 0 to 255. SSTATION is allocated for the duration of the network and its range is local to the node. Confirm CHKSM checksum 2 Check all preceding packet segments.

Table I

As shown in Table I, a transport packet includes several packet segments as follows.

Destination segment specifying the packet destination. The destination segment includes a destination node identifier DNODE and a destination station identifier DSTATION.

Data segment containing transmission information. The data segment includes the command identifier COMMAND, information field length ILEN and information INFO.

Source segment that specifies the originator of the packet transmission. This information is needed to facilitate acknowledgment. The source segment includes a source node identifier SNODE and a source station identifier SSTATION.

Acknowledgment segment that detects any packet corruption due to processing errors. The low level physical media layer 80-87 below the MADI layer 90-97 provides error detection and correction for communication errors. The verification segment contains the checksum CHKSM.

8 shows packet data transmission between nodes of the MADI-WAN 30. Shown are transmission paths or interfaces A through G for inter-node or inter-node transmission with nodes 130 and 140 (node 1, node 2). Node 130 includes data stations 131 and 132 and protocol station 133. Node 140 includes data stations 141 and 142 and protocol station 143. In the given example, data station 131 is a PDA, protocol station 133 is a mobile phone, protocol station 143 is a mobile phone, and data station 142 is a PDA.

Direct transmission may be performed such that this data is transmitted directly to the destination station, such as the transmission via interface A of FIG. 8. The destination segment with fields DNODE and DSTATION in the transport packet specifies the target recipient of the message, and the source segment with fields SNODE and SSTATION specifies the sender. The service request sender is preferably identified in each transport packet. This allows confirmations to be carried by the controlled station without requiring knowledge of the network. Since all received packets are acknowledged, packets in the network can be easily interspered.

For indirect transmissions through other stations, such as DS-DS out-of-node transfers, the intermediate station relaying the packet may report any message history for return acknowledgment transfer. No need to save Indirect transmission is a transmission sent through an intermediate station to a destination station. Indirect transmission consists of a number of intermediate transmissions. For example, in FIG. 8, in the transmission from the data station 131 of the node 130 to the data station 142 of the node 140, the remote transmission between the two personal digital assistants (PDAs) is indirect, and the interface ( Requires transmission via B, D, and G). Alternatively, this indirect transmission can also occur with the transmission over the interfaces A, C, D, E and F.

For all intermediate transmissions, the transport packet can be encapsulated in the INFO field of the parent transport packet. The parent packet provides all the information necessary to perform an immediate transmission. The encapsulated packet contains the information required to determine the transmission path to the final destination.

9 shows the structure of a parent transport packet 150. This packet 150 has field branches similar to the packets described in the relevant table I, but contains the final destination information of the parent information field, so that intermediate transmissions between stations can be performed with minimal overhead information. Referring to FIG. 8, indirect transmission is from station 131 of node 130 to station 142 of node 140. Intermediate transmissions are carried over interfaces B, D and G, and the commands and INFO to be transmitted are X and Y, as mentioned above. The parent transport packet 150 is composed of a parent destination segment, a parent data segment, a parent source segment, and a parent confirmation segment. The parent destination segment includes a parent destination node identifier (PDNODE) 152 and a parent destination station identifier (PDSTATION) 153 that defines an intermediate destination for packet delivery. The parent data segment includes a parent command field (PCOMMAND) 154 that defines an action at the intermediate station, the parent information field length (PILEN) 155 and the parent information contained in the parent transport packet 150. A method of interpreting the field (PINFO) 151 is displayed. The parent confirmation segment includes a parent checksum (PCHKSM) 156. The parent source segment includes a parent source node identifier (PSNODE) 157 and a parent source station identifier (PSSTATION) 158. In the intermediate packet transmission chain from the initial parent source station to the final destination station, the intermediate stations become parent and thus update the encapsulation field so that packet transmission can be performed with minimal overhead. Parent information field (PINFO) 151 indicates the final destination node address (DNODE) 160, the final destination station address (DSTATION) 161, how to define the operation at the last destination station and how to interpret the following information fields: Command field (COMMAND) 162, information length field (ILEN) 163, final destination data field (INFO) 164, originating source node address field (SNODE) 165, and return for transmission path selection. Source station address (SSTATION) 166 used to establish the confirmation path.

In direct transmission or indirect transmission within a node, acknowledgment transmission is returned from each receiving station. If indirect transmission is performed across node boundaries, the verification process is different. Within the remote node, all acknowledgments are accumulated in the remote protocol station 143 which maintains the internode link. When this is done, in response to the last ACK or error ACK, the remote protocol station 143 sends an acknowledgment report to the local protocol station 133 and then relays it to the initial data station 131. If no final acknowledgment is received, knowledge is accumulated to accurately indicate the source location of the problem for the user.

FIG. 10 shows a transport packet 170 from node 131 to mobile phone 133 at node 130. For all packets through a chain of packets from PDA 131 to PDA 142, the contents of parent information field 151 are the same, i.e. final destination node / station address 140/142 and final destination address 140 / 142), length information field 163, destination information field (Y) 164, and originating node / station address (130/131). The length information field 163 defines the length of the destination information field 164. Since the parent packet information encapsulates the parent information field 151, the packet 170 is the intermediate station destination node / address of the mobile phone 133 and the protocol station 130/133 in the node 130, and the node ( The source node / station address 130/131 of the originating PDA 131 at 130, and the information is not intended for the mobile phone 133, but the packet is to be sent to another station. In addition, the command further includes a parent command "NETWORK_RQST_INDIRECT_SEND".

11 shows a transport packet 171 from the mobile phone 133 at the node to the mobile phone 143 at the second node 140. Since the parent packet information encapsulates the same parent information field 151, the packet 171 is the intermediate station destination node / address of the intermediate mobile phone 143 and the protocol station 140/143 at node 140, A mobile phone that includes the source node / station address 130/131 of the intermediate mobile phone 133 at node 130, and whose information is not intended for the mobile phone 143, but whose packets must be sent to another station ( And a parent command "NETWORK_RQST_INDIRECT_SEND" to command 143).

12 shows a transport packet 172 from the mobile phone 143 at the node 140 to the PDA 142 at the node 140. Because the parent packet information encapsulates the same parent information field 151, the packet 172 is the last station destination node / address of the PDA 142 and the data station 140/142 at the node 140, and the node ( Add the parent command "NETWORK_RQST_INDIRECT_DELIVERY" to include the source node / station address 140/143 of the intermediate mobile phone 143 at 140 and the information to command the PDA 142 intended for the PDA 142. It includes.

An application programming interface (API) is provided to represent MADI SAPs in higher layers in a simple and convenient way. The API provides access to all MADI functionality and to a distributed set of services in the MADI network. The API consists of a single MADI Service List and multiple MADI Service Transport Interface instances.

13 shows a single service station record 180 in the MADI service list.

14 shows the overall structure 190 of the MADI Service List.

The MADI Service List provides a "view" to the higher layers of all services available in the MADI network 30 and lists important information about these services. In the given example, the user selects a service station that has been accessed and controlled, so that the user is given a short ASCII text description of each of the available service stations (although this need does not actually occur). This appears in the service station tag field (STNTAG) 181. Record 180 adds a Service Station Identifier Field (STNID) 183 and a Service Station Node Field (NODEID) 182 to the higher tier to provide the service station address of the service station providing the service in the network 30. It includes. A service station attribute field (STNATRB) 184 is provided to indicate higher layer specific performance information about the service station. For example, if a higher layer needs to access the JINI enable device, the STNATRB field can be scanned to determine which station accesses if there is a station to access. This reduces the number of transmissions since individual stations in the network do not need to be polled with a compatibility request. The service station receive capability is indicated in the service station receive capability field (STNSIZE) 185 to support varying memory limits at the MADI compliant station. The field 185 defines the maximum size of the information field that can be received and stored at the service station. The controller station performing the transmission checks the transmission packet size prior to transmission. This may overcome the generation of transmitted transmissions that are too large for the receiving station, otherwise a carrier error check will occur. Thus, the STNSIZE field 185 will greatly reduce the number of transmissions. In Fig. 14, service station records 191-194 are shown as (record 1, record 2, record 3 and record n).

MADI Service Transport Interface (MTSI) provides a gateway to MADI services. Access to the MADI layer is obtained through this interface only. To understand the MSTI, it is necessary to briefly discuss the underlying principles. First, it is important to ensure that the memory requirements and processing power for the MADI layer are minimized in order for all stations to be MADI compliant. However, if the MADI layers 90-97 are not able to properly process transfers within the network, a large amount of retransmissions will be made into the network, which will reduce efficiency. Since the transport mechanism is packet-based, the following concepts for communication are established. It can be limited that the transmission is continuous, that is, after one transmission is made, the other transmission is made. The reception may be limited continuously, i.e. after one reception is made, the other reception is made. The transmission and reception will be done together, but the reception can be done while the transmission is taking place. This means that all MADI compliant stations can communicate in full duplex at all times within the network. Therefore, the MSTI is composed of one transmit transfer interface (TXSTI) and one receive transfer interface (RXSTI) as a minimum requirement. However, the memory limits of MADI compliant stations will change significantly. Some of the more powerful stations (such as protocol stations) with more fully enriched memory may find it useful to transmit and receive multiple transmissions together. The MADI layer will facilitate this by supporting multiple TXSTI and RXSTI instances.

15 shows the structure of a transmit and receive transmission interface (TXSTI / RXSTI) 200. The structures of TXSTI and RXSTI are completely separate but identical and are as shown in FIG. 15. The higher service layer, as shown in FIG. 7, requests MADI service via TXSTI. The higher layer loads the TXSTI interface as follows.

Destination address of the service station providing the service. The destination address includes a destination node address 201 and a destination station address 202. The higher layer obtains this address from the MSL as shown in FIGS. 13 and 14.

MADI command 203 (described in more detail below). This command 203 indicates how to define the action and interpret the information field at the final destination.

The length of the data field 204 to indicate the length of the INFO field.

Transmission data when needed in the INFO field.

Source address of the station initiating the transfer. The source address includes a source node address 206 and a source station address 207.

For service requests at other stations, the TXSTI request is sent through the MADI network 30 and, via the MADI layer RXSTI, to a higher service layer at the receiving station.

In Table II below, the commands available for the MADI command set are shown.

Decimal value Command format Explanation 0-99 Service set Service commands delivered to the service layer above the MADI layer. Examples of such commands are as follows: SERVICE_RQST_CTRL_MGR-By requesting an encapsulated UI model for download to the controller, the user can control the service through a graphical UI. By requesting a list of controller UI prompts for download to the SERVICE_RQST_PRMPT_LST controller, the user can control the service via a text prompt. SERVICE_RQST_SHRT_PRMPT_LST By requesting a list of reduced length controller UI prompts for download to the controller, the user The prompt allows you to control the following service behavior: SERVICE_RQST_SECURED_CTRL Control request from the receiving station for password protected services.SERVICE_ACK_FINAL Received and accepted service commands.SERVICE_ACK_ERROR_1 Unacknowledged received service commands. 100 Extended service set Service-specific commands passed to the service layer, specifically defined for specific services. The service specific command is issued in the first byte of the service INFO field. 101 -119 Spare

120-149 Service delivery set Service delivery command indicating that the service command has been merged into the INFO field for delivery to the service layer. The passed command value is specified in the format of the INFO field, for example 120 command, INFO field = service priority, service identifier byte, service command, service INFO length, service INFO.149 command, INFO field = user Justice 150-159 Spare 160-239 Network set Network commands used to perform all network administrative duties, for example: NETWORK_RQST_INDIRECT_SEND-Perform indirect transfers NETWORK_RQST_LOCAL_NODE_SCAN-Create a node NETWORK_ACK_STATION_SCAN-Station response to a scan NETWORK_ACK_LOCAL_SCAN-Created nodes 240 Extended service set If necessary, this command extends the range of available network commands. The extended network command is indicated in the first byte of the subsequent network INFO field. 241-255 Spare

Table II

Command formats have been defined and many examples have been given.

The stations themselves are considered as services in the MADI network strategy. Service commands are communicated between network service stations via a peer to peer MADI layer as shown in FIG. In order to deliver service commands to the service layer of another station, a parent transport packet is used as shown in FIG. The COMMAND field indicates delivery requirements to the service layer and is loaded with a service transfer command (see Table II) indicating the format that guarantees the INFO section. Service commands (or extended service commands) for transmission to the service layer are merged into the INFO section.

Referring to the intermediate transmission illustrated in FIG. 10, the service transmission may be as follows. COMMAND = X = 120 and INFO = Y.

16 shows INFO = Y, service priority of field 210, service identifier of field 211, service command of field 212, service information field length of field 213, and service information of field 214. With service data encapsulation.

An extended service set of service specific commands facilitates the use of commands specifically defined for a particular service. In order to use the extended service set, the service command of FIG. 16 is set to 100. The service specific command then appears in the first position of the service INFO field.

The MADI network directory must be maintained in order for the service stations to be selected to provide their services. Attempts to distribute current directory information to stations constituting the network should be prevented because transmission bandwidth, power consumption and radio transmission costs of mobile communications are of fundamental importance.

In a MADI system, the network includes an initial controller station and one or more controlled stations. At any time, if the controlled station obtains the service of another station or relays information to another station, this station becomes the controller station. The controller station must have current directory knowledge to generate requests for services in the network. This knowledge must be able to "know the network", but the controlled station does not "grasp" and merely follows its commands and responses. As a result, each controller has a directory.

17 illustrates directory record format 220 in a MADI controller. Record 220 includes a Service Station Node Identifier (NODEID) 221 and a Service Station Identifier (STNID) 222, these identifiers 221, 222 of the service station providing service to the network 30. Specify the address. Record 220 includes a Service Station Receive Performance Field (STNSIZE) 223 that defines an information field of maximum size that can be received and stored at the service station. Record 220 includes a Service Station Attribute Field (STNATRB) 224 that specifies service station performance for higher layer networks such as the JINI network. Record 220 includes a service station tag field 225, which is an ASCII text description of the service station for the user to select. Record 220 has direct access, i.e. 1 = UMTS, 2 = Bluetooth, 3 = IrDA, and 255 = indirect required through intermediate stations defined in field (ANODEID) 227 and field (ASTNID) 228. A service station access identifier field (STNACC) 226 that specifies the physical layer for access. In the case of indirect access, field 227 specifies an indirect access station node for indirect access to the service station providing the service, and field 228 specifies an indirect access service station identifier.

18 shows the entire directory structure. Records 230, 231, 232 and 233 are shown.

Referring to the example given in FIG. 8, the media access fields shown in FIG. 17 correspond to the directory contents of the protocol station 133 and data station 131 of node 130 and the data station 142 of node 140. It becomes apparent from the directory contents of the protocol station 143, and the stations 131, 133, 143 and 142 become MADI controllers.

19 shows directory contents of a directory record in a MADI controller. As shown in FIG. 19, for example, controllers have access fields (NODEID, STNID, STNACC, ANODEID and ASTNID) 221, 222, 226-228 in their directory.

There may be cases where a regional node may grow due to the addition of the remaining other regional service stations. In order to provide an enhanced level of service to other stations in the network, it must be possible to exchange control period directory listing information. MADI systems will need to provide a full range of network commands to support the entire host of directory exchange commands.

The following rules apply to directory updates:

The controller station stopping and leaving the service maintains the service by providing link access to the service. This means that the next field is passed as follows:

STNACC = 255.

ANODEID = node identifier of the controller station passing through the entity.

ASTNID = station identifier of the controller station passing through the entity.

For indirect directory transfers, the passed directory information is added to the directories of all intermediate stations, with the ANODEID and ASTNID modified as mentioned for each intermediate transfer. Received directory records will be ignored if NODEID and STNID already exist in the directory. If a station in the directory has an STNACC field = 255 and the node scan acquires the station directly, the STNACC field, the ANODEID field, and the ASTNID field are updated with direct access information. The controller does not log directory records, which contain their own NODEID and STNID. This methodology allows controller stations to simply exchange directory structures without much processing power. This minimizes the size of the structure since the indirect access path is limited to the first station path setup. In general, the use of separate node and station identifiers adds some overhead to MADI transport packet size and directory memory requirements. However, this methodology provides for network flexibility. If the node and station identifier are replaced with a single station identifier, the value will have to be assigned throughout the network. All directories will need to be updated automatically each time a station is added to local load. This greatly affects station power consumption and overall transmission bandwidth. In the selected methodology, a MADI command is provided to add a particular node of another WAN in which the user is required, or to send a specific station directory entity to another user so that the specific nodes can connect to only one station of a remote node. Can be. They authorize users within the network of nodes, providing bandwidth and power savings.

We now describe some of the functional aspects associated with the delivery of intermediate transmissions. Referring to the example system shown in FIG. 8 and the transport packets defined in FIGS. 10, 11, and 12, operations that need to be performed within the MADI layer, for example, receive a NETWORK_RQST_INDIRECT_SEND command.

The receiving station compares DNODE and DSTATION with the directory listing, sets new values for PDNODE and PDSTATION and PCOMMAND from it, resets PSNODE and PSSTATION with station specific values, recalculates PCHKSM and reformats it to the new destination. The generated message.

Confirmation is returned. To set up the return confirmation, the station performs the following operations.

Set PDNODE and PDSTATION values from the received PSNODE and PSSTATION values.

Set the PCOMMAND to be the same as the received PCOMMAND, that is, either NETWORK_RQST_INDIRECT_SEND or NETWORK_RQST_INDIRECT_DELIVERY.

Set the PSNODE, PSSTATION, SNODE and SSTATION values to the station's own address values.

Set the DNODE and DSTATION values from the received SNODE and SSTATION values.

-Set COMMAND according to received PCOMMAND.

-Set ILEN = 1.

-Set the INFO field to contain validation information, such as VALID_RECEPTION or an error code.

Recalculate PCHKSM

-Finally, send a confirmation signal to your destination.

NETWORK_RQST_INDIRECT_SEND returns NETWORK_ACK_INTERMEDIATE. NTWORK_RQST_INDIRECT_DELIVERY returns NETWORK_ACK_FINAL.

As shown, the directory contents 240 of the data station 131 which is the controller C1, the directory contents 241 of the protocol station 133 which is the controller C2, and the directory of the protocol station 143 which is the controller C3. Contents 242 and directory contents 243 of data station 142, which is controller C4.

Referring to FIG. 8, directory contents 240 of controller C1 have a record for direct transmission to stations 132 and 133 via transmission paths A and B, and a record for indirect transmission. In addition, the protocol station 133 at the node 130 is configured for indirect access to the service station 141, 142 or 143 providing a service in the network 30 and the controller C1 requesting the service. 1 is an intermediate station.

Similarly, controller 133 has three direct transmission paths B, C, and D and two indirect transmission paths for service stations 141 and 142, where controller 143 is configured for the indirect path. 1 is an intermediate station.

Similarly, controller 143 has three direct transmission paths (E, G, and D) and two indirect transmission paths for service stations (131 and 132), with controller 133 providing for the indirect path. 1 is an intermediate station.

Similarly, controller 142 has two direct transmission paths (F and G) and three indirect transmission paths for service stations (131, 132, and 133), and controller 143 is configured for the indirect path. 1 is an intermediate station.

20 illustrates a MADI-SAP software structure with a MADI layer 250. The MADI layer consists of a processing lower layer 251 and a driver lower layer 252. The processing lower layer 251 performs MADI network processing control. In addition to confirming the input checksum, the layer 253 calculates and adds the output checksum, verifies the input destination address and data length, and reports the status. The processing layer 251 is the next manager, i.e.

A message manager 254 that handles all internal messages passed between software components and layers,

Directory Manager (255) that performs all direct operations such as compiling, modifying, clearing down, initializing, providing information request services, and providing a list of services for MSL.

A transfer manager 256 that manages shared transfer memory (which provides and controls access and status),

Transport Configuration Manager (257), which configures transport data,

A command interpreter 258 that interprets the received commands and performs the necessary actions except network configuration actions,

A network manager 259 interpreting the received network configuration commands and performing the required operations, such as adding stations to and removing stations from the network, and

Media access manager 260 to select a media driver for the transfer operation.

Driver layer 252 includes a media driver 261, one for each of the supported media interfaces. Shown are Bluetooth media interface 262, IrDA media interface 263, UMTS media interface 264, and other media interfaces 265. Media driver 261 configures MADI output transport data for the appropriate media interface layer. The media driver also constructs data received from the media interface for the MADI layer and reports the media status. The media driver fulfills all necessary signaling and data management requirements necessary to support the exchange of information between the MADI processing sublayer 251 and the media layer. Media driver interface 266 provides a consistent exchange mechanism between processing lower layer 251 and driver layer 252. This provision facilitates the addition of these new media interfaces as new media interfaces become available. The addition of a new media driver to the driver lower layer 261 is all that is required to support the new media interface in the MADI layer. The delivery configuration manager 257 configures the added new media manager. Media access manager 260 selects a media driver. Further shown in FIG. 20 are service applications 267, 268, and 269 on MADI layer 250, MADI service application programming interface 270, and media layer application programming interface 271.

21 illustrates modeling of transmission data over MADI layer 250. The mechanism for transmitting the data communicated through the MADI layer 250 must be configured as efficiently as possible in view of the memory constraints imposed by the various mobile products that need to be compliant and the timing constraints of the system. . For this reason, it is considered that a system of shared memories is used. A single buffer is used to propagate MADI transmitted data through the MADI layer 250. Although a larger number may exist, there are at least two buffers in the MADI layer 250. This ensures that the requirement for full dual communication is met for all compliant stations. In this regard, variable buffer size provides greater flexibility in the system. For example, one special station may need to be able to handle high rates of short messages. If a variable buffer size is supported, the station can choose to only accept short messages and provide a large number of MADI transmit buffers without using more memory. For this reason, MADI systems support variable size transmit buffers. This is facilitated through the STNSIZE field (shown in FIG. 13) and the directory record (shown in FIG. 17) in the MSL. The service application checks their transmission length for the MSL before requesting the transmission. If the station receives an oversized transport packet, the station will reject it and return an error acknowledgment. In FIG. 21, MADI transmit buffer 280 is shown as buffer service transmit data 281 exchanged via MADI service API 270 and media transfer data 282 exchanged via media driver interface 266. It became. Further shown are MADI_Send_Indication 283, which indicates the transmission requirement and confirms the associated buffer, MADI_Send_Report 284, which reports the transmission status (valid or error) and confirms the associated buffer, indicating a MADI received event and indicating the reception status (valid or MADI_Delivery_Indication (285) to check the associated buffer and verify the associated buffer, Media_Send_Indication (286) to indicate the transmission requirement and identify the relevant buffer and media driver, report the sent status (valid or error), and check the associated buffer and media driver. Media_Send_Report 287, a Media_Delivery_Indication 288 that indicates a media reception event and conveys a reception status (valid or error) and identifies the associated buffer and media driver, and a MADI_Memory_Status 289 that indicates buffer availability and allows its acquisition. Further shown is the service layer 290. The exchange of information is completely double for the transmit and receive operations.

20 and 21, a transmission operation is performed as follows.

The service application selects an available buffer from MADI transmit buffer 280 using MADI_Memory_Status 289 indicating that the buffer is available. After the service obtains the buffer resource by updating the MADI_Memory_Status 289, the service data is loaded into the available buffer. The service application then sends a MADI_Send_Indication 283, which indicates which buffer to send to the MADI SAP. Upon receiving MADI_Send_Indication 283, MADI processing layer 251 parses the associated MADI transmit buffer and generates a parent transmit packet if necessary. Once the transport packet is correctly configured, processing layer 251 sends Media_Send_Indication 286 to driver layer 252. This represents the driver that will be used for transmission and the buffer containing the transport packet. When a particular media driver completes the transmission, it reports the transmission status to the processing layer 251 via Media_Send_Report 287, which indicates the associated buffer, the media driver used and the error status (valid or error). When the processing layer 251 receives the Media_Send_Report 287, it constructs a MADI_Send_Report 284 indicating an associated buffer and an error state (valid or error) and returns it to the service layer.

20 and 21, a reception operation is performed as follows.

The particular media driver obtains an available buffer using MADI_Memory_Status 289, which indicates which buffer is available. Once the media driver obtains a buffer resource by updating MADI_Memory_Status 289, the incoming transport packet is loaded into an available buffer. When the buffer load is complete, the media driver sends Media_Delivery_Indication 288 to the processing layer 251. This indicates a media reception event, conveys the reception status (valid or error), and identifies the associated buffer and media manager. Upon receipt of Media_Delivery_Indication 288, processing layer 251 analyzes the received data and performs the following operations. The received data is valid and an appropriate acknowledgment is passed. A small separate confirmation buffer may be needed to convey the confirmation. Confirmation of the service commands the service layer 290 to be reset. Service orders are provided to enable signal changes to be performed if necessary. However, the MADI layer 250 always confirms receipt of the transmission. Actions necessary for valid reception are performed. If the received COMMAND is a service delivery command, processing layer 251 sends MADI_Delivery_Indication 285 to service layer 290. This indicates a MADI receive event, conveys the receive status (valid or error), and checks the associated buffer.

Access to the MADI layer 250 is provided to the service layer 290 via the MADI Service API (shown in FIG. 21). This consists of MSL, MSTI and signaling, as initially defined. The MSTI consists of TXSTI / RXSTI 200 as shown in FIG. 15. These elements of the API are contained within MADI transmit buffer 280.

22 illustrates a MADI transmit buffer structure with buffer contents for a transmit TXSTI or a receive RXSTI. The buffer contents correspond to the fields of the transport packet shown in FIG. 12, and are the parent destination node address 300 (PDNODE), parent destination station address 301 (PDSTATION), parent command 302 (PCOMMAND), and parent information length. Buffer field 303 (PILEN), encapsulated parent information buffer field 304 (PINFO), parent source node address 305 (PSNODE), parent source station address 306 (PSSTATION), and parent checksum 307 (PCHKSM). The encapsulated parent information buffer field 304 (PINFO) includes the final destination node address 310 (DNODE), the final destination station address 311 (DSTATION), the command field 312 (COMMAND), and the length field 313 ( ILEN), final destination information field 314 (INFO), start source node address field 315 (SNODE), and start source station address field 316 (SSTATION).

Support for prioritizing service processing is provided within the MADI system. Some service delivery instructions define an INFO format (shown in FIG. 16) that includes a service priority field. All these commands will have a higher priority than all other commands. This allows the service layer 290 to check the priority of the added MADI delivery and handle them accordingly.

In addition to the described packet-switch service, the circuit-switch service can be emulated in MADI for a particular service. This will be an independent priority assignment in the service layer 290, triggered by the receipt of the SERVICE_RQST_CIRCUIT_SWITCHED service command. If the service layer 290 does not assign circuit-switch attributes for other services, the service station requesting the circuit-switch service may be assigned the highest priority at the service level.

The services may provide their own security mechanism encapsulated in the Service INFO field passed through the MADI system. This will provide a layer of security within a particular service. Some service delivery commands will define an INFO format that includes a password field. This will provide an additional layer of security on top of service layer protection. Network commands may also be provided to configure access permissions for the controlled station. The outline is as follows. The controller station requires access to the controlled station that confirms the password request. The controller passes a password to gain access.

Next, some of the main network configuration activities are described.

To create a local node, the following operations are performed.

NETWORK_RQST_LOCAL_NODE_SCAN, that is, a network request local node scan command is requested in TXSTI. The MADI layer 250 processes the request and constructs a NETWORK_RQST_STATION_SCAN, that is, a network request station scan command, which sends the command via Media_Send_Indication 286. Within the driver layer 252 the media driver conveys the movement to the associated media interface that performs the transmission. Available stations respond to NETWORK_ACK_STATION_SCAN, a network acknowledgment station scan command, which includes NODEID and STNID (both zero if not already assigned), STNSIZE, STNATRB, STNTAG and STNACC (shown in FIG. 17). After receiving NETWORK_ACK_STATION_SCAN, processing layer 251 responds to a NETWORK_RQST_STATION_CONFIG, i.e., network request station configuration command, which includes the NODEID and STNID assigned to the newly acquired station (if not already assigned a value). Processing layer 251 adds the station's information to its directory. The NETWORK_RQST_STATION_SCAN transmission is then repeated until there are no more NETWORK_ACK_STATION_SCAN returns. Processing layer 251 then selects the next available media driver and repeats the first five of the six steps. All six steps are repeated until all media drivers are executed. Processing layer 251 then returns a NETWORK_ACK_LOCAL_NODE_SCAN, that is, a network confirm local node scan command to the RXSTI with an updated list of MADI services. The local node is configured in this way. The action executes all media layers present on the local node. Partial local node scans may also be supported to allow only necessary media to be scanned.

The following operations are performed to create a remote node.

The connection between the local protocol station and the remote protocol station must be established by sending a NETWORK_RQST_CALL_SETUP command, ie a network request call setup command, to the TXSTI. This instructs the local PS to call the number provided in the INFO field. According to NETWORK_RQST_CALL_SETUP, the remote PS returns a NETWORK_ACK_CALL_SETUP, or network acknowledgment call setup command, which includes NODEID and STNID (both 0 if not already assigned), STNSIZE, STNATRB, STNTAG and STNACC (shown in FIG. 17). do. After receiving NETWORK_ACK_CALL_SETUP, the processing layer responds to NETWORK_RQST_STATION_CONFIG, the network request station configuration command, which includes the NODEID and STNID assigned to the newly obtained PS (if not already assigned). Processing layer 251 adds the station's information to the directory. If the connection between the local PS and the remote PS has already been established, the above three steps are omitted.

Once the connection of the local PS and the remote PS is established, a NETWORK_RQST_REMOTE_NODE_SCAN command, i.e. a network request remote node scan command, may be required in the TXSTI. This command is sent to the remote PS. Upon receiving this command, the remote PS itself becomes a controller station and performs a local node scan, as defined in the first seven steps of creating a local node. In this way, the remote controller configures its directory for the local node. When the operation ends and the node is created, the remote controller sends back a NETWORK_ACK_REMOTE_NODE_SCAN, a network acknowledgment remote node scan command, which includes a copy of its local directory information for the initiating station. Processing layer 251 in the initiating station then updates its directory and returns the received NETWORK_ACK_REMOTE_NODE_SCAN to the RXSTI with the updated MSL. The remote node is thus configured and obtained by the initiating station. The operation executes all media layers present in the remote node. Partial remote node scan may also be supported to allow only necessary media to be scanned. This MADI methodology reduces the transmission over remote connections, thus reducing transmission bandwidth and processing power within the system.

The controller can add a new station to their local node, as described in the creation of the local node. This process only updates the directory on the local controller. One option may be included to allow notification of directory updates to all connected controllers after a directory update has occurred. For this reason, one field is provided in the INFO field of NETWORK_RQST_LOCAL_NODE_SCAN, and NETWORK_RQST_REMOTE_NODE_SCAN is divided into packets to indicate whether this is necessary. If one station receives an update indication after one directory is changed, a new directory change must be required.

Figure 23 shows a possible overview in which network mobility is fixed, using MADI. A mobile MADI PDA 330, which is a data station capable of communicating with a mobile JINI network 331, and a MADI mobile phone 332, which is a protocol station, are shown. Within the home 333, or others of that kind, there is provided a MADI fixed or mobile phone 334, which is another protocol station that can communicate with the MADI mobile phone 332. Within home 333, phone 334 may communicate with a MADI data station 335, such as a personal computer or television set, which may also communicate with home JINI network 336.

The advantages of the MADI system can be summarized as follows.

The concept is simple. One MADI compliant PS can access an unlimited array of peripheral DS devices. The complexity of the user application is limited for non-PS DS devices. The PS providing voice service to the user via the keypad (UI) can therefore be very simple. The PS need not have any kind of display element, and thus can be considered independent of language. This means that the same PS products can target markets in many different countries. Since the display in the PS is not needed, its size is limited only by the battery module, which can be smaller and less noticeable. PS is compatible with an unlimited array of DS devices. PS is an open architecture and facility for future new data services, service enhancements, and the addition of new DS products. For the modular design concept, the base protocol unit containing all the elements for the baseband service would have to be user replaceable. The MADI concept places the PS as a modular device in the family, making it easy to connect to distributed computing networks.

MADI systems provide facilities for local and wide area networks that are self contained within any fixed or mobile device. MADI networks can be configured simply and efficiently by users, or automatically by service applications when needed. MADI systems are specifically designed for mobile environments that limit transmission bandwidth, processing power, and memory requirements. The total cost of network management is generally proportional to the number of stations supported. The MADI system is optimized to reduce these total expenses by extracting directory details for stations, by distributing processing requirements among connected stations, and by providing dispatch information in transport packets. The MADI network can also be thoroughly processed from two stations up to 65,536 stations as needed right now. The MADI system provides networking facilities to all without incurring any cost to the cellular service provider. There is no need for capital expenditures or installation costs for service providers. The buyer of the station pays for the MADI layer in the purchased product, and all users pay only a small fee for the increased functionality. The MADI system is independent of the Internet and therefore accessible to everyone with compliant PS TMPEG standard video compression (no Internet cost is required). However, if an Internet-enabled station is part of a MADI network, Internet services can be useful for other connected stations. MADI systems are primarily independent of the media interface because the necessary drivers can be added as needed. This is especially useful for remote connection protocols such as UMTS, GSM, TDMA and W-CDMA for PS devices, and local area networking interfaces such as Bluetooth and IRDA. A MADI system is designed to interface to a fixed network such as JINI, to support the fixed network, and to provide the mobility network with mobility management for a higher level networking strategy. Transparent access is provided within the MADI network to access only connection stations that are compatible with higher level networks.

In view of the foregoing, it will be apparent to those skilled in the art that various changes may be made without departing from the spirit and scope of the invention as defined in the appended claims. The term "comprises" does not exclude the presence of elements or steps other than those listed in the claims.

Claims (20)

A first data station (51) comprising a first service application layer protocol (111) and a first physical layer protocol (M2) for providing a first data service; A first wireless protocol station 53 comprising a second service application layer protocol 110, the first wireless protocol station 53 being a first communication link using the first physical layer protocol M2; Configured to physically exchange data with the first data station 51 via a service access point protocol 91 included in the first data station 51 and the first wireless protocol station 53. Is configured to access the first data service via peer-to-peer communication; At the first data station (51), the service access point protocol (90; 91) is set to transmit data between the first service application layer protocol (111) and the first physical layer protocol (M2); At the first radio protocol station 53, the service access point protocol 90; 91 is configured to transmit data between the second service application layer protocol 110 and the first physical layer protocol M2. ; Wherein said first data station (51) and said first wireless protocol station (53) form a first local area network node (50) in said dynamically configurable network (20). A second data station (52) at the first local network node (50); The second data station 52 includes a third service application layer protocol 112, a second physical layer protocol M3, and the service access point protocol 90; 91; 92 for providing a second data service; ; The first radio access protocol station 53 physically exchanges data with the second data station 52 via a second communication link using the first physical layer protocol M3, and the service access point protocol ( 90; 91; 92, a dynamically configurable network (20) configured to access the second data service via peer to peer communication with the second data station (52). In the dynamically configurable network (20, 25) of claim 1, The first radio protocol station 53 includes a third physical layer protocol M1, The network 20, 25 comprises a second wireless protocol station 63 having a fourth service application layer protocol 114, the third physical layer protocol M1 and the service access point protocol 90; 94. To; The second radio protocol station (63) is included in a second local network node (60); The first radio protocol station 53 physically exchanges data with the second radio protocol station 63 via a third communication link using the third physical layer protocol M1, and the service access point protocol. A dynamically configurable network (20, 25) configured to access the fourth service application layer protocol (114) via peer to peer communication using (90; 94). The method of claim 3, wherein The second radio protocol station 63 includes a fourth physical layer protocol M2, The network (20, 25) is a third data station 61 having a fifth service application layer protocol 115 for providing a third data service and the fourth physical layer protocol (M2) and the service access point protocol ( 94; 95); The third data station (61) is included in a second local area network node (60); The second radio protocol station 63 physically exchanges data over a fourth communication link using the fourth physical layer protocol (M2) and peer to peer using the service access point protocol 94 (95). A dynamically configurable network (20, 25) configured to access said third data service via communication. 3. The method of claim 2, wherein the service access point protocols (90; 91; 92) are configured to transmit the second data at the second data station (52) when the second data service is requested from the first data station (51). Dynamically configurable network 20, configured to (A) run the service directly. 3. The service access point protocol (90; 91; 92) of claim 2 (B) indirectly requests service request (154) from the first data station (51) to perform the second data service (162). Configured to run as The indirect execution is performed by the first radio protocol station (53). The method of claim 4, wherein The service access protocol (94; 95) is configured to indirectly execute a service request from the first data station (51) to perform the third data service at the third data station (61), And said indirect execution is performed via intermediary of said first and said second wireless protocol stations (53, 56). 2. The dynamically configurable network (20) of claim 1, wherein data transmission between the first data station (51) and the first radio protocol station (63) is packet switched. 7. The method of claim 6 wherein the data transmission is packet switched, At the first and second data stations 51, 52; 131, 132 and the first wireless protocol station 53; 133, the service access protocols 90; 91; 92 are configured to perform the indirect execution. Each directory uses 240, 241, and 242. The directories 240, 241, and 242 include a node address 221, a station address 222 of a data station 51, 52 that provides data services to the network 20, and a first intermediate station in the network. And a station address 228 and a node address 228 of the dynamically configurable network 20. 7. The method of claim 6 wherein the data transmission is packet switched, The data station 131, 132 in the network 20, originating the service request 154 for data service, sends a packet to the first intermediate station 133, The packet is dynamically configurable, including an intermediate destination node address 152 and an intermediate destination station address 153, an intermediate station operation instruction 154 and a destination information field 151 for the final destination station 141. Network 20. 11. The dynamically configurable network (20) of claim 10, wherein the destination information field (151) comprises a final destination node address (160), a final destination station address (161) and a final destination operation instruction (162). 12. The dynamically configurable network (20) of claim 11, wherein the destination information field (151) comprises a final destination station data field (164) and a final destination data length field (163). 11. The method of claim 10, wherein the packet comprises an intermediate source node address 157 and an intermediate source station address 158, The destination information field 151 includes an originating source node address 165 and an originating source station address 166 between the data service requesting station and the final destination service execution data station to provide a confirmation path for the stations. , Dynamically configurable network 20. The method of claim 1 wherein the data transmission is packet switched, The service access point protocol 90; 91 is at least one from a buffer pool 280 to form a parent transport packet 150 based on transmission information from the first service application layer protocol 111. Uses a buffer of, sends the parent transport packet 150 to a media driver 261, The service access point protocol (90; 91) uses the at least one buffer to load a received transport packet from the media driver 261, and uses destination information of the received transport packet in the first service layer application. 20, dynamically configurable network. 10. The dynamically configurable network (20) of claim 9, wherein the directories (240, 241, 242) are updated with node address information and station address information of packets passed when they are not present at the station containing the directory. ) 10. The system of claim 9, wherein the directories 240, 241, 242 are dynamically updated with node addresses and station addresses of stations obtained through a station scan by stations including the directories 240, 241, 242. Configurable Network (20) 18. The apparatus of claim 16, wherein prior to a scan for a station outside the first local network node (50; 130), the first wireless protocol station (53; 133) is external to the first local network node (50; 130). Dynamically configurable network (20) for establishing a link to a wireless protocol station (63; 73; 143). In a wireless protocol station 53 for use in a dynamically configurable network 20 comprising a first service application layer protocol 111 providing a data service and a data station 51 having a physical layer protocol, The wireless protocol station 53 includes a second service application layer protocol 110, The radio protocol station 53 is configured to physically exchange data with the data station 51 via a communication link using the physical layer protocol M2, and the data station 51 and the radio protocol station 53 Is configured to access the data service via peer to peer communication using a service access point protocol (90; 91) included in At the radio protocol station 53, the service access point protocol 90 is configured to transmit data between the second service application layer protocol 110 and the physical layer protocol M2. . 19. The method of claim 18 wherein the data transmission is packet switched, The service access point protocol 90 uses at least one buffer from a buffer pool 280 to form a parent transport packet 150 based on transmission information from the first service application layer protocol 111, Sends the parent transport packet 150 to a media driver 261, The service access point protocol 91 uses the at least one buffer to load a received transport packet from the media driver 261, and transmits destination information of the received transport packet to the first service application layer protocol ( Radio protocol station 18, which transmits to " 111 ". A data station 51 for use in a dynamically configurable network 20 with a radio protocol station 53 comprising a first service application layer protocol 110 and a service access point protocol 90, The radio protocol station 53 is configured to physically exchange data with the data station 51 via a communication link using a physical layer protocol M2, The data station, A second service application layer protocol 111 for providing data services; The physical layer protocol (M2), The service access point protocol 91, The data station 51 is configured to provide the data service to the wireless protocol station 53 via peer to peer communication using the service access point protocol 91, At the data station (51), the service access point protocol (91) is configured to transfer data between the second service application layer protocol (111) and the physical layer protocol (M2).