US9825863B2 - Buffer control for multi-transport architectures - Google Patents

Buffer control for multi-transport architectures Download PDF

Info

Publication number
US9825863B2
US9825863B2 US12/920,041 US92004108A US9825863B2 US 9825863 B2 US9825863 B2 US 9825863B2 US 92004108 A US92004108 A US 92004108A US 9825863 B2 US9825863 B2 US 9825863B2
Authority
US
United States
Prior art keywords
transport
data buffer
information
specific data
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active, expires
Application number
US12/920,041
Other languages
English (en)
Other versions
US20110002344A1 (en
Inventor
Arto Palin
Juha-Matti Tuupola
Timo Eriksson
Jukka Reunamäki
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Technologies Oy
Original Assignee
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy filed Critical Nokia Technologies Oy
Assigned to NOKIA CORPORATION reassignment NOKIA CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ERIKSSON, TIMO, PALIN, ARTO, REUNAMAKI, JUKKA, TUUPOLA, JUHA-MATTI
Publication of US20110002344A1 publication Critical patent/US20110002344A1/en
Assigned to NOKIA TECHNOLOGIES OY reassignment NOKIA TECHNOLOGIES OY ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: NOKIA CORPORATION
Application granted granted Critical
Publication of US9825863B2 publication Critical patent/US9825863B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/19—Flow control; Congestion control at layers above the network layer
    • H04L47/193—Flow control; Congestion control at layers above the network layer at the transport layer, e.g. TCP related
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/30—Flow control; Congestion control in combination with information about buffer occupancy at either end or at transit nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/90—Buffering arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/90—Buffering arrangements
    • H04L49/9036—Common buffer combined with individual queues
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the present invention relates to a communication architecture, and more specifically, to a communication architecture for establishing connectivity between devices using one or more transports.
  • software programs may include instruction sets that are executable by a processor, and are further organized to receive input (e.g., data) for use in a calculation or determination resulting in an output.
  • input e.g., data
  • Software technology has evolved to transform these individual instruction sets into program modules that may in turn be integrated together to form the more complex programs.
  • Today's more-sophisticated software programs may receive various forms of input such as raw data, for example as stored in magnetic or optical storage, user input through various known types of user interfaces, measured or monitored information converted to electronic information from electronic and/or electromechanical sensors, etc.
  • programs may be configured to produce data usable by other software applications.
  • a problem may be presented in conveying the information from one program to another. If the relationship is known before the programs are created, then a specific strategy may be devised to convert one program's output into another program's input. Traditionally this strategy has led to functional but rigid software applications, requiring frequent and possibly substantial revisions due to changes in functionality, platform, architecture, etc.
  • nodes that can be revised or replaced without having to interrupt overall device operation.
  • some nodes may contribute information to a shared memory space, while others may read previously stored information from the shared memory space or may combine these functions.
  • Other types of nodes may also be specialized to provide communication services.
  • altering program elements e.g., altering, adding or deleting one or more nodes
  • memory usage may be optimized since information may be stored in a single location while being accessible to all of the nodes.
  • a risk may further exist with respect to lost data (e.g., dropped packets) as data already allocated to resources supporting a failing or failed transport cannot be recovered, and therefore, this information may have to be resent and/or recreated.
  • This recovery process will unavoidably occupy system resources and delay the sending of any following data, resulting in a negative impact on the overall quality of service (QoS) provided by the communication device.
  • QoS quality of service
  • the present invention may include at least a method, computer program, device and system for automating connection management in a manner that may be transparent to any actively communicating applications operating in a Network on Terminal Architecture (NoTA).
  • An application level entity such as an application node, may access another node by making a request to a high level communication structure via a high level interface. The high level structure may then interact with a lower level structure in order to facilitate a connection to a programmatic element on another device, for example, via a particular communication transport.
  • information provided from one or more application and/or service level entities for transmission to another device may initially be stored in a transport-independent data buffer.
  • the information may be forwarded to a lower level transport-specific data buffer corresponding to the selected transport as part of the preparation for transmission.
  • the information in the transport-specific buffer may then be sent to the other device via the selected transport.
  • a strategy may be employed to account for possible problems that may be encountered in the selected transport.
  • a failure may occur in a communication link conducted using the selected transport due to, for example, physical disconnection of a communication line, moving out of range, environmental interference, etc.
  • information already transferred to the transport-specific buffer in preparation for transmission may be lost.
  • various embodiments of the present invention may retain a copy of the information that was most recently passed to the transport-specific data buffer in the transport-independent data buffer until transport-related resources can confirm that the transmission was successful. In this way, corrective action in response to a failed transport may be performed expeditiously, which may reduce any impact on QoS.
  • the transport-independent data buffer may only delete the retained copy of the previously-passed information after a some sort of confirmation of receipt message has been received from the other device. This is not to say that transport itself cannot also attempt to resend the information, for example, until some threshold condition has been met. However, if a determination is made that the currently selected transport can no longer provide a viable link, various embodiments of the present invention may then take action to establish a link with an alternative transport. After a new connection has been established using the newly selected transport, the transport-independent data buffer may send the retained copy of the information that may have been lost when the previous transport failed to the transport-specific data buffer corresponding to the newly selected transport in preparation for retransmission.
  • FIG. 1A discloses an exemplary intra-device Network on Terminal Architecture (NoTA) in accordance with at least one exemplary embodiment of the present invention.
  • NoTA Network on Terminal Architecture
  • FIG. 1B discloses a structural diagram of various exemplary layers of an inter-device Network on Terminal Architecture (NoTA) including a Whiteboard-type exchange service in accordance with at least one exemplary embodiment of the present invention.
  • NoTA Inter-device Network on Terminal Architecture
  • FIG. 2 discloses an exemplary need for underlying connectivity establishment in accordance with at least one exemplary embodiment of the present invention.
  • FIG. 3A discloses a structural example of communication establishment in accordance with at least one exemplary embodiment of the present invention.
  • FIG. 3B discloses an example of establishing access to a target service residing in another device in accordance with at least one exemplary embodiment of the present invention.
  • FIG. 4 discloses an example of various software levels and interfaces through which information may be conveyed in accordance with at least one exemplary embodiment of the present invention.
  • FIG. 5 discloses an exemplary configuration for the lower level communication structure in accordance with at least one exemplary embodiment of the present invention.
  • FIG. 6 discloses an example of connection establishment in accordance with at least one exemplary embodiment of the present invention.
  • FIG. 7 discloses an example of buffer level condition factors in accordance with at least one embodiment of the present invention.
  • FIG. 8 discloses an example of the utilization of one or more wireless transports for controlling buffer levels in accordance with at least one embodiment of the present invention.
  • FIG. 9 discloses an example of multi-transport communication in accordance with at least one embodiment of the present invention.
  • FIG. 10A discloses an exemplary communication scenario including multiple buffers containing data in accordance with at least one embodiment of the present invention.
  • FIG. 10B discloses an example of information routing between buffers in accordance with at least one embodiment of the present invention.
  • FIG. 10C discloses at least one impact of the loss of a selected transport on message routing in accordance with at least one embodiment of the present invention.
  • FIG. 11A discloses an example of information routing between buffers including transport failure protection in accordance with at least one embodiment of the present invention.
  • FIG. 11B discloses a further example the transport failure protection described with respect to FIG. 11A in accordance with at least one embodiment of the present invention.
  • FIG. 11C discloses an example of transport failure protection activity during a transport failure in accordance with at least one embodiment of the present invention.
  • FIG. 12 discloses a flowchart of an exemplary information handling process in accordance with at least one embodiment of the present invention.
  • NoTA Network on Terminal Architecture
  • NoTA Network on Terminal Architecture
  • NoTA is a service based interconnect-centric platform architecture usable in various electronic apparatuses including wired and/or wireless (e.g., mobile) devices.
  • the interconnect-centric approach incorporated in NoTA may allow any physical sub-system to directly communicate with other sub-systems while supporting multiple parallel connections. Direct connections are possible due to simple switches optimized for the underlying physical media.
  • NoTA interconnect architecture and related interfaces may be complexity and performance optimized for service and data communication, and may be designed in such a way that different communication media technologies can be utilized.
  • FIG. 1A discloses an example of NoTA implemented in a single device 100 .
  • the NoTA platform architecture consists of subsystems 102 connected together via interconnects as shown, for example, at 104 . It is also possible for subsystems to be directly coupled to other subsystems as shown at 102 ′ in FIG. 1A .
  • a coupled configuration may exist in a scenario where subsystems frequently cooperate during operation.
  • FIG. 1A also discloses service nodes (SN) 106 and application nodes (AN) 108 (e.g., PN, RN and AG) that may be mapped into subsystems 102 and 102 ′.
  • Subsystems in NoTA context may encompass all of the resources (e.g., computing, software, peripherals, etc.) required to implement the services and/or applications running in the corresponding subsystem.
  • Whiteboard 110 is an example of an application and service level that may comprise the highest level of operation in this architecture.
  • operational groups 112 may be formed including whiteboards 114 and various application nodes 108 .
  • Application nodes 108 may correspond to application existing on a plurality of wireless communication devices, and may be utilized to exchange information between these applications, for example, by placing data into, and removing data from, whiteboard 114 .
  • the various nodes may consist of proactive nodes (PN) 116 that may place information into whiteboard 114 , reactive nodes (RN) 120 that may take information from whiteboard 114 and agent nodes (AG) 122 that may operate either in a PN or RN mode depending on the particular application.
  • PN proactive nodes
  • RN reactive nodes
  • AG agent nodes
  • ITI Information semantics interpreter
  • whiteboard 114 may provide a standardized means for application interaction that overcomes many incompatibilities.
  • Billboard level 124 may facilitate interaction between services available on the one or more devices. Services 134 and clients 136 that may utilize these services may be organized in service domains 126 .
  • service domains 126 may correspond to a particular protocol, such as UPnP, BT SDP, Bonjour, etc.
  • services 134 may be represented by service nodes (SN) 130 , and likewise, application nodes (AN) 132 may be established to correspond to applications.
  • service domains 126 may interact utilizing service ontology interpreters (SOI) 128 . SOI 128 may allow service domains 126 to interact with other service domains (e.g., 138 ), even if service domain 138 resides on another wirelessly-linked device (e.g., to provide access information to service domains 126 ).
  • SOI service ontology interpreters
  • Connectivity map 144 may define connectivity methods/possibilities and topology for different devices participating in sharing resources in order to support a top level, for example whiteboard 110 , and also billboard-type services in billboard level 122 .
  • devices 144 may be linked in directly connected groups 142 .
  • Examples of directly connected groups of devices (Dev) 142 may include devices connected via BluetoothTM piconet, a WLAN network, a wUSB link, etc.
  • Each directly connected group of devices 142 may further be linked by gateways (GW) 146 .
  • FIG. 2 discloses an example scenario wherein application and/or service nodes may reside on two different devices 200 and 202 .
  • Whiteboard sections 152 A and 152 B also reside on these devices, respectively, ideally providing a common memory space via which the nodes may interact.
  • interaction with a common memory space in the form of whiteboard 152 may initially depend upon the establishment a wireless connection between whiteboard sections 152 A and 152 B.
  • whiteboard 152 may utilize SN 212 and 214 to interact with whiteboard section 152 B as shown in FIG. 2
  • whiteboard 152 A may allow PN 210 access to other shared memory spaces, such as service domain 126 (e.g., to allow an application to access a desired service, like a printer service), or any other exemplary subsystem 102 as previously discussed in accordance with various embodiments of the present invention.
  • service domain 126 e.g., to allow an application to access a desired service, like a printer service
  • any other exemplary subsystem 102 e.g., to allow an application to access a desired service, like a printer service
  • FIG. 3A discloses an example of an underlying logical architecture that may be utilized in implementing NoTA in accordance with at least one exemplary embodiment of the present invention.
  • NoTA may be configured as multiple subsystems (e.g., 300 and 350 ) coupled by interconnect 312 .
  • a communication link between devices that may be both established and managed by a lower operational level may facilitate the routing of messages for higher level subsystems, such as sections ( 152 A and 152 B) of the same shared memory space (whiteboard) 152 , without the actual involvement of the higher levels in any communication configuration.
  • NoTA interconnect 312 may comprise two layers: High Interconnect (H_IN) layer 302 and Low Interconnect (L_IN) layer 304 coupled to corresponding H_IN 352 and L_IN 354 by switch 310 .
  • the various communication layers may further interact over interfaces (abbreviated “IF” in FIG. 3 ).
  • H_IF 380 may serve as the interface between the application level and H_IN 302 / 352
  • L_IF 382 may serve as the interface between H_IN 302 / 352 and L_IN 304 / 354
  • Low interconnect layer 304 may include ISO/OSI layers L1-L4 and may provide transport socket type interface upwards.
  • High Interconnect layer 302 may act as the middleware between L_IN 304 and the higher level Application nodes 306 (AN) and Service nodes (SN) 308 residing in subsystems like 300 and 350 .
  • Key H_IN 302 functionality may include providing client nodes (AN 306 or SN 308 ) a direct access to services without having to disclose the location of the latter (e.g., transparent at the top level). All communication establishment may be connection-oriented, meaning that before any service or data communication may take place, connection setup procedures must first be carried out. Security features have been added to countermeasure identified threats.
  • NoTA is an architecture that may be used to provide inter-device service access, making it possible to build independent subsystems providing both services and applications. In an exemplary implementation there may be several individual NoTA devices involved in direct inter sub-system communication.
  • FIG. 3B An example of establishing access to a service on another device via a wireless link, in accordance with at least one exemplary embodiment of the present invention, is disclosed in FIG. 3B .
  • a node in the application/service level of subsystem 300 in device 200 desires to access a service.
  • the service may be identified, for example, by a service description (SID). This service description may be used to locate and establish access to the desired service.
  • SID Service description
  • the SID may be mapped to an Interconnect Address (IA) that may further identify the subsystem in which the service resides.
  • IA Interconnect Address
  • the desired service resides in subsystem 350 in target device 202 .
  • a transport In order to make an H_IN level connection with the subsystem offering this service, a transport must be selected that is suitable for making a connection between the devices. The IA may then be mapped to the selected transport in L_IN 304 . In the example of FIG. 3B , a wireless link must be established because the devices are not coupled by a wired connection. This wireless link is established over interconnect 312 via the wireless transport. Once devices 200 and 202 are wirelessly coupled, H_IN level connection between subsystem 300 and 350 may be possible. In H_IN level 352 a corresponding H_IN protocol is usable to negotiate service usage.
  • the (SID ⁇ IA) and (IA ⁇ transport) mapping is used only in subsystem 300 in order to build a connection with a proper subsystem offering the needed service (e.g., subsystem 350 ).
  • upper level e.g., application/service level
  • access may be established from a requesting node in device 200 to a service that is able to fulfill the request, even though the service resides in device 202 .
  • This access may be facilitated by lower level link establishment via one or more transports.
  • FIG. 4 describes the interaction of the various communication levels and examples of functions that may be performed by each level and its corresponding interface in accordance with at least one exemplary embodiment of the present invention.
  • 400 discloses an exemplary service node (SN) that may facilitate the set-up and establishment of connections supporting various application nodes (AN) such as 108 shown in FIG. 1A .
  • the interface between the top application level and the H_IN level 404 may provide service access, registration and communication stream access via H_IF interface level 402 .
  • services may be identified by a Service Identification (SID).
  • SID Service Identification
  • H_IN level 404 may then obtain device-to-device access and communication interface access to L_INup level 408 via L_IF interface level 406 .
  • the H_IN level access may be identified by an Interconnect Address (IA) which separates different devices/subsystems in high level middleware layer.
  • IA Interconnect Address
  • a general connectivity control interface L_IFdown level 410 may then provide access from transport-independent L_INup level 408 to L_IN down 412 including transport-specific L_IN adaptors as disclosed at 414 .
  • Wired and/or wireless transports 418 supported, for example in a mobile device may then utilize the physical hardware and/or corresponding software in device PHY layer 420 to communicate.
  • the service level may utilize an SID to identify different services
  • H_IN level middleware layer may then map this SID into a certain IA, which corresponds to an address of a device/subsystem where the respective service may be accessed in the high level middleware layer.
  • L_INup level 408 may then map this IA to one or more physical connections (e.g., transports) that may offer connectivity to the device/subsystem that corresponds to the IA.
  • L_INdown level 410 may then establish physical connections with the specific transport.
  • FIG. 5 depicts an exemplary low interconnect architecture (L_IN) 304 , in accordance with at least one exemplary embodiment of the present invention.
  • L_IN 304 may provide service upwards to H_IN 302 via L_IF interface 382 , and may comprise a unified L_INup communication structure 408 and one or more L_INdown communication structures 412 .
  • L_INdown 412 may further include at least one L_INdown adaptor 414 corresponding to each transport 418 that may be utilized in a device.
  • L_INup 408 may be transport-independent (e.g., L_INup operation does not change in dependence upon the transport in use), while L_INdown adaptors 414 in L_INdown 412 may be specifically configured for use with each transport 418 .
  • Each L_INdown adaptor 414 may provide service to L_INup 408 through one or more L_IFdown interface 410 .
  • L_IFdown interfaces 410 may be configured similarly for each transport 418 except in the addressing and access mechanism.
  • L_INup 408 may perform multiple functions in embodiments of the present invention. For example, activation and deactivation may be controlled in this layer of the communication structure. The L_IN activation process is controlled over the L_IF 382 . During the activation process, the L_IN 304 may be configured to be able to use wireless and/or wired transports as L_IN transports. As a result of successful activation, L_IN 304 may then be able to resolve an Interconnect Address (IA) as well as IAs for the existing Resource Managers (IArm). L_INup 408 may use the query services provided to L_INdown 412 during this activation.
  • IA Interconnect Address
  • IArm Resource Managers
  • L_IN 304 When active, L_IN 304 may be able to detect loss of a L_IN network connection. As a result, any earlier allocated IA and IArms may be released in order to, for example, automatically reconnect the network connection using the same or a different transport.
  • the deactivation process is also controlled over L_IF 382 . In the deactivation process, L_IN 304 is deactivated in respect of all available transports. During this process, the IA is released.
  • the L_IN connection creation process may establish a L_IN-level connection between different devices such as shown in FIG. 6 .
  • This connection may utilize different types of transport technologies in-between the end-points.
  • the choice of transport may be transparent at the application level, since interfaces with which the nodes may interact may be transport-independent.
  • applications and services e.g., represented in the NoTA architecture by AN 306 and SN 308
  • L_IF interface 382 may therefore be equipped with a mechanism to enable a quality of service (QoS) parameter setup to monitor each connection.
  • QoS quality of service
  • the quality of service parameters may not be bound to an actual transport since the transport technology used to carry out data would not be selected at this level. Rather, the QoS requirements may be mapped to an L_IN communication instantiation, or “socket,” that are abstractions of the actual connection that upper protocols may use.
  • the connectivity requirements may be achieved using, for example, buffer state-based transport selection and flow control.
  • the interface does not have to address transport-specific parameters. Instead the requirements, or wishes, may be described in more universal manner.
  • L_IN In order for L_IN to carry out its function, a set of basic L_INup-L_INup connection protocols may be defined. All of these may be utilized by the L_INup communication structure 408 , hence making the implementation of the L_INdown adapter 412 simple (e.g., because no generic L_INdown-L_INdown peer protocols are required).
  • the following L_INup protocols may be defined for facilitating communication between L_IN communication structures existing in two separate devices (e.g., devices 200 and 202 as shown in FIG. 6 ):
  • a protocol that may provide a means to allocate and identify unique interconnect addresses for each device may be called an Interconnect Address Resolution Protocol (IARP) in accordance with at least one exemplary embodiment of the present invention.
  • IARP Interconnect Address Resolution Protocol
  • DAP Device Access Protocol
  • This protocol may be called the Connectivity Environment Protocol (CEP) in accordance with at least one exemplary embodiment of the present invention.
  • CEP Connectivity Environment Protocol
  • IARP may be specified to provide inter-device NoTA architecture Interconnect Address (IA) resolution within a network of devices, in an ad-hoc communication connection, etc.
  • IARP may contain four messages in order to retrieve and release a unique IA.
  • the IA resolution process may handle IA address allocation between devices as a connection is established. Address resolution may utilize IARP as a resource for supporting connection establishment. Address resolution may be centralized or distributed/autonomous requiring zero manual configuration.
  • the data delivery process may manage data flow control between the sending device and the receiving device. L_IF ring-buffer based sockets may be used in this process.
  • the data delivery process may further implement connection loss detection and recovery process in order to provide more reliable data delivery using inter-transport switching.
  • DAP may provide connectivity initialization, creation, and disconnection.
  • L_IN layer internal interface, L_IFdown 410 may provide uniform way for DAP to access individual transports. Each transport needs an adaptor 412 which implements L_IFdown interface 410 .
  • FIG. 6 shows how the architecture scales from a transport-independent intra-device domain (e.g., L_INup 408 ) to transport-independent inter-device domain (e.g. L_INdown 412 ).
  • the depicted communication layers may be coupled data sockets 600 that may directly couple H_IN 302 and L_INdown 412 via transport-independent L_INup communication structure 408 .
  • Inter-transport switch triggering decisions may be controlled in view of condition information obtained by monitoring the transmit (TX) and receive (RX) buffer fill levels. All data conveyance may be considered “Best Effort” (BE) type. Introduction of some simple QoS classes (e.g. BE, low-latency delivery, minimized power consumption, etc.) may then be possible while still keeping the overall implementation complexity of NoTA manageable.
  • the connection loss and recovery process is a supplemental action in L_IN communication structure 304 that can be utilized for restoration and reconnection procedures that could not otherwise be handled in as part of the inherent abilities of resources operating at the transport level.
  • connection setup, data delivery, and connectivity recovery solutions may include sharing and distributing information about the connectivity in the surrounding environment by means of the CEP protocol. This method may retrieve information about the available connectivity technologies used by other surrounding devices and enables smart decision making procedures when choosing optimal transport to access devices and services.
  • control sockets 602 for enabling L_INup-to-L_INup protocol communication are shown interacting with the TARP, DAP and CEP protocols in furthering inter-device communication.
  • the L_INdown communication structure 412 may provide other communication-related functionality.
  • a query operation may be an L_INdown internal function that is intended to provide information concerning transport-specific connection opportunities. This functionality may be tightly coupled with scene and connectivity maps by which information regarding the overall space/proximity/neighborhood connectivity may be obtained.
  • the query function is mainly employed during the establishment of a connection.
  • a data delivery process may handle data flow control between the same transport peer entities (e.g., between L_IN up communication structures such as shown in FIG. 6 ).
  • the same ring buffers may be used as in the previously described case with respect to L_IF.
  • a transport-specific connection loss and recovery process may also be implemented in L_INdown 412 .
  • the implementation may substantially depend on the applied transport technology.
  • FIG. 7 discloses an exemplary implementation of the present invention, in accordance with at least one embodiment, wherein services (e.g., represented by SN 700 ) may produce data into general transmit buffer 702 . While a one-way wireless transmission from device 200 to device 202 has been disclosed in FIG. 7 for the sake of explanation, the present invention is not limited to this specific example, and may be implemented to manage two-way communication via wired or wireless communication. Further, while FIG. 7 discloses an example of general buffers 702 located above interconnect structure 312 and transport-specific buffers 704 located within L_IN level 304 , other possible configurations may include, for example, general buffer 702 also residing in L_IN level 304 .
  • control elements may monitor buffer status as shown graphically at 706 , 708 , 712 and 714 .
  • various embodiments may also incorporate dynamic buffer allocation which may be taken into account.
  • control elements may identify one or more wireless transports appropriate to implement according to various factors including, for example, buffer level.
  • buffer level In the exemplary scenario depicted in FIG. 7 , SN produces information into general buffer 706 which is operating at a level as shown at 706 .
  • the transport specific buffer 704 is approaching full. This may further affect buffers 712 and 714 by starving them of information.
  • resources such as power, processing capacity, etc. may be utilized inefficiently due to the limitations imposed by the wireless transport, which could be the same transport that was utilized when, for example, communication was initially established.
  • FIG. 8 an exemplary implementation wherein co-operation of one or more wireless transports may help to resolve such a problematic scenario is disclosed in FIG. 8 .
  • a low power low rate wireless transport 750 may be utilized.
  • general buffer 706 may start to fill up because high speed service data cannot be delivered efficiently over transport 750 .
  • various control elements may utilize transport 750 to negotiate a switch to transport 800 .
  • L_INup 408 may determine (e.g., through previously mentioned connectivity map 140 ) that high speed transport 800 can be used and may then facilitate a switch to high speed transport 800 .
  • connection speed may be much faster, and therefore, an overflow of the various buffers may be prevented.
  • the same strategy may also be implemented based on receiving device(s) characteristics, meaning that a frequently empty buffers 712 and 714 may indicate that the amount of data being received is too low from the perspective of the data consumer (e.g., device 202 in this example).
  • This characteristic may indicate different situations depending, for example, on the particular transport currently in use. In a scenario where a low speed transport is employed, the limited speed of the transport may be creating a bottleneck in conveying the data. In such a situation it may be beneficial to employ a faster transport having better data-handling capacity.
  • a high speed and/or capacity transport is already in use when a determination is made that receiving-side buffers are near empty, then the problem may be that the volume of data being sent is too low to create a steady stream of incoming data over the transport. In this case, a lower power and/or capacity transport may be selected to convey the data while also conserving power.
  • a decision to perform the switch may be implemented based on many factors, and also in view of the particular configuration of the present invention that is being utilized. For example, a number of empty (or full) buffers and/or per time period, estimated needed bit-rate (e.g., determined based on monitoring the buffer filling level), etc.
  • the request to perform the switch from one transport to another may be triggered by either end (TX or RX).
  • TX or RX In the case of push type configuration (e.g., stream from device 200 is pushed into storage in device 202 ) the TX side may be more likely to initiate a switch.
  • pull systems e.g. data is being pulled from device 200 to device 202 ), the RX side may initiate a switch.
  • the implementation of one or more transports may result in a balancing of buffer levels as shown at 706 , 708 , 712 and 714 in FIG. 8 , and as a result, an optimization of device resources.
  • Another exemplary use may include that during utilization of transport 800 communication is suddenly lost and hence some “fallback” procedure is needed.
  • This procedure may be negotiated during the setup phase of link 800 .
  • link 750 may be used (e.g., in accordance with certain factors) if the link 800 is lost.
  • transport protocols do not control packet retransmission, for example, in a case where a transport delivered an erroneous packet.
  • a bearer may be carrying a data packet successfully from device to another but there is an error in the packet that is not noticed by the bearer error-checking mechanism.
  • TX buffer 704 is intentionally filled up and then emptied with high bit rate communication link (depending, for example, on whether the provider application can support the increased speed).
  • transport 800 may, in at least one instance, not support a sleep mode that increases operational efficiency, which may mean that substantial power will be consumed during waiting time until TX buffer 704 is filled up again.
  • a low rate radio sleep mode may be utilized, which would mean that the transport 750 is active during the time when TX buffer 704 is filling. This activity may be controlled, as previously set forth, by various hardware and/or software control elements in device 200 .
  • Transport control may also be implemented in view of receiving side flow control factors.
  • a transport-specific RX buffer corresponding to TX buffer 704 may become filled resulting in receiver-side data flow control issues. In such a situation the TX side may stop its transmission. If the link was high bit rate link (e.g., transport 800 ) it might be beneficial to negotiate that the slower transport 750 should become active until a “GO” signal is again issued. It is also possible for connectivity control elements to monitor radio operation. Either side (TX or RX) may trigger a low power transport mode, but now the TX side control may understand that there is no point trying to use high bit rate link despite its TX buffer filled condition because the RX side issued flow control, and thus cannot process incoming data as fast as the TX side.
  • FIG. 9 discloses devices 1 - 4 .
  • device 1 may be a controlling device, such as a personal communicator, a personal digital assistant (PDA), a wireless tablet device, etc. that is enabled to support a variety of wireless transports.
  • Device 2 may be a low power temperature sensor that is enabled to communicate using BluetoothTM (BT) and Ultra Low Power BluetoothTM (ULP-BT).
  • Device 3 may be a display (e.g., an LCD display) capable of communicating via BT and Ultra Wide Band (UWB).
  • Device 4 may be a file server (e.g., a video server) capable of communicating via ULP-BT, WLAN and UWB.
  • a connection may be established between device 1 and the other devices utilizing a low power medium. This is shown in FIG. 9 by the use of the ULP-BT and BT links. This initial link may be established, for example, to obtain information about the other devices (e.g., supported mediums, available applications, etc.) Otherwise, device 1 may already be aware of the capabilities of the other devices (e.g., from previous connections). In the case of device 2 , only a small amount of data is being exchanged. Therefore, device 1 and device 2 may continue to utilize ULP-BT in order to conserve power.
  • the possible connectivity techniques between device 1 and device 4 include ULP-BT, WLAN and UWB.
  • ULP-BT is a low power/speed, transport that would be too slow for video streaming, so the best transport would be either WLAN or UWB.
  • UWB can provide data rate that is much faster than is needed for the video streaming, and thus, UWB would spend a great deal of time in the idle mode (e.g., no transmission or reception) during the video streaming.
  • UWB power consumption during the inactivity periods is much higher compared to ULP-BT, resulting is a waste of power.
  • An optimal solution would then be to use UWB only for transmission and reception of streaming video, and to use ULP-BT to manipulate UWB activity states and related wake-up cycle control.
  • a first exemplary implementation may negotiate the duty cycle already at the beginning of video streaming.
  • the role of ULP-BT would then be to set up the video streaming link as shown in FIG. 9 , and to provide a timing reference (e.g., to the UWB radio so that it can awaken at correct moment).
  • This kind of scenario may be used in the situations where the timing between active and inactive states may be fixed. Operation according to this exemplary scenario may be challenging in some situations. For example, if the connectivity patterns are fixed at the beginning of the service, it may be difficult to change or modify the connectivity patterns if any of the parameters change during the connection.
  • the system may operate by utilizing ULP-BT to asynchronously control the WLAN reactivation.
  • a ULP-BT and WLAN are both active.
  • the ULP-BT radio may be used during the WLAN inactive periods, and as soon as high bit rate is needed (e.g., application data is generated) ULP-BT may trigger the WLAN radio to awaken.
  • WLAN radios Once active over the ULP BT radio link, WLAN radios may, for example, communicate on the physical channel utilizing a RTS/CTS (Request-to-Send/Clear-to-Send) mechanism. This type of strategy may be used to manage asynchronous TX/RX activity.
  • RTS/CTS Request-to-Send/Clear-to-Send
  • Another example may include a scenario where a UWB is being used, but then the UWB radio enters hibernation mode.
  • the UWB radios When signaled over the active low power ULP-BT link, the UWB radios may return to the active mode and can reserve enough air time according to information that may be provided from the other wirelessly coupled devices over the ULP-BT link. This information exchange may decrease the time required for UWB connection set-up and/or reestablishment.
  • the operation may be as follows: a first video packet of the stream content is transported over the UWB link from the video server to device 1 . Once packet is received, UWB radio may enter into an idle mode.
  • the ULP-BT radio of the device receiving the video stream may then be used to launch the transport of the next video packet of the stream over UWB link when the receiving device notices that the previous video packet of the stream is approaching its end. This operation may enable the higher power usage UWB radios to remain in idle mode most of the time, and as a result, may further significantly enhance power conservation in wirelessly coupled devices.
  • the controlling of WLAN or UWB radio over ULP-BT may be arranged as follows:
  • a ULP-BT connection is created, one logical link may be reserved as a connectivity control channel.
  • This channel may carry information regarding connectivity between devices.
  • connectivity map information may be exchanged.
  • this channel may make it possible to provide timing information (e.g., transport awakening and synchronization reference point delivery between devices) for control purposes.
  • This connectivity information may be exchanged using any available transport, and may be used with many different applications to provide better initial transport selection, faster service discovery, optimal transport medium selection, transport handover etc.
  • Connectivity map 140 may also be beneficial when selecting active bearer from multiple available bearers during link setup, link maintenance and data delivery. For example, at some point in FIG.
  • a user of device 1 may want to watch a movie, and then finds the device 4 and the video streaming service using ULP-BT.
  • the two devices may negotiate that UWB will be used to provide an air interface for the video streaming due to the bandwidth performance requirements.
  • the UWB radio may be activated in device 1 to receive the data, but as described above, during an inactive period (e.g., when no data is being delivered) ULP-BT may be used in “doze” mode to keep the link alive.
  • the UWB radio may then be reactivated when higher data rates are once again needed during data delivery. If device 1 was to move out of UWB radio range at some point, the video streaming service would become unusable unless device 1 is able to determine alternative high rate transport to use.
  • both the device 1 and device 4 support WLAN, which may be used instead of UWB.
  • control elements in the devices may have negotiated a backup transport and continue with that if needed as before.
  • radio activity information may be used for optimally performing multiradio control in devices.
  • Earlier multiradio control relied upon device internal parameters, while in various embodiments of the present invention activity information of another device may be shared.
  • This information may include negotiation of the connectivity technologies used and the timing synchronization of those technologies, taking into account the overall connectivity situation of the devices. This may enable the most optimal overall service quality and power consumption for both devices.
  • FIG. 10A discloses an exemplary communication configuration in accordance with at least one exemplary embodiment of the present invention. Additional detail is given to general buffer 702 , which may be transport-independent (e.g., operation is not influenced by the particular transport in use) and transport-specific buffer 704 . As set forth above, while a one-way wireless transmission from device 200 to device 202 has been disclosed in FIG. 10A for the sake of explanation, the present invention is not limited to this specific example, and may be implemented to manage two-way communication via wired or wireless communication.
  • general buffer 702 may contain information for transmission.
  • Exemplary data units A, B, C . . . are disclosed in FIG. 10A , wherein these units may be, for example, data packets for transmission to another node in a subsystem on another device (e.g., device 202 ).
  • FIG. 10A all of the information for transmission currently resides in general buffer 702 .
  • an exemplary data conveyance, and the effect that a transport failure or switching due to, for example a change in connection parameters, may have on this data conveyance will now be described with respect to FIG. 10B-10C .
  • FIG. 10B discloses an example of data being conveyed from an application and/or service level in device 200 to a node in the corresponding level in device 202 .
  • General buffer 702 has released data unit A to transport-specific buffer 704 .
  • transport-specific buffer 704 has released data unit A for conveyance over transport link 750 to device 202 .
  • Data A is also shown in a hold pending confirmation mode in transport-specific buffer 704 .
  • transport-specific buffer 704 will keep a copy of data A until a receipt confirmation is received (e.g., in the form of a return packet) from device 202 . At this point the copy of data A may be deleted.
  • the selected transport may resend data A until, for example, a threshold condition is achieved. Examples of threshold conditions governing the resending of information may include a number of retries, a timeout period, etc.
  • a connection established using a particular transport may become broken, or alternatively, parameters relating to the connection may become altered in a manner where another transport may become more preferable transport for maintaining the connection.
  • a wired transport may experience failure due to the physical disconnection of media (e.g., cables).
  • a wireless transport may experience a loss of connection due to a device leaving the transmission range of a particular transport, interference experienced from other radios in the same device or nearby wireless devices, electromagnetic emission, etc.
  • FIG. 10C Such an instance of disconnect is shown with respect to FIG. 10C .
  • the link 750 established over the selected transport has been lost.
  • the related hardware and/or software at the transport control level has attempted to reestablish the link with no success (e.g., the threshold condition governing retries has been met).
  • the loss of link 750 may abandon data A in transport-specific buffer 704 . Since this data cannot be recovered to general buffer 702 , the data may be deemed lost. To accommodate the loss of data A, device 200 may have to recreate data A. This may impact overall communications in that data B, C . . . may have to be delayed until data A is recreated and sent. All of the above activities related to recovering data A may in turn impact the overall QoS of communication being conducted in device 200 , and therefore, the overall operation of any application and/or service that is relying on the transport for communication.
  • FIG. 11A that may be structurally similar to FIG. 10A is disclosed. However, in FIG. 11A a copy of data A may be retained in general buffer 702 after the data A has been passed to transport-specific buffer 704 . The “copy” of data A may be retained until a confirmation has been received from device 202 that the information has been received. An example of this process is disclosed in FIG. 11B .
  • FIG. 11B shows an example of a successful transaction. More specifically, information is being sent from transport-specific buffer 704 in device 200 to the corresponding transport-specific buffer 704 in device 202 over transport link 750 .
  • data A has been received in device 202 , which may be confirmed, for example, by a receipt confirmation packet being transmitted back from device 202 to device 200 .
  • TX buffer may empty and accept the next data unit to be sent (e.g., data B).
  • Either action listed above e.g., the receipt of a confirmation packet or the acceptance of data B into transport-specific buffer 704
  • transport-specific buffer 704 may send a message to general buffer 702 indicating that the previous transaction was successful.
  • General buffer 702 may then delete the copy of data A it was holding and may hold a copy of the next data unit sent.
  • FIG. 11C The effect of the above exemplary configuration, in accordance with at least one embodiment, on a situation where the previously selected transport experiences a failure, or alternatively, parameters relating to the connection have changed so that the previously selected transport is no longer preferable, and a transport switch is determined to happen, is shown with respect to FIG. 11C . Similar to FIG. 10C , the original link 750 over the previously selected transport has failed, leaving data A in transport-specific buffer 704 without any means to send or recover this data. However, since general buffer 702 has retained a copy of data A, corrective action may begin quickly. In this scenario a new link is established with another transport that has a corresponding transport-specific buffer 1100 . General buffer 702 may then re-forward data A to transport-specific buffer 1100 over link 800 .
  • general buffer 702 does not delete the information for data A until a successful transaction is confirmed over the new transport link 800 . Therefore, once transport-specific buffer 1100 has received a confirmation and/or is ready to accept a new data unit, general buffer 702 may delete data A and forward a new data unit for transmission (e.g., data B). As in the process previously described above, general buffer 702 will save a copy of data B until a successful transaction is confirmed. Otherwise, a new transport may be selected if needed, and data B may be passed to the corresponding transport-specific buffer for sending.
  • the principle of releasing memory reserved in general buffer 702 for storing data copies may vary depending on the particular transport(s) in use. For example, since there may be various ways to indicate the receipt of some amount of data on the receiving end (e.g., transmission has been successful), then also the actual amount of received data confirmed may vary. More specifically, the granularity of general buffer 702 and transport-specific buffer 704 may differ, and thus, special consideration may be required when general buffer memory is released. In other words, the number of data copies that may be simultaneously maintained in general buffer 702 may depend on various transport-specific factors such as the speed of the transport(s) being used, whether the transport(s) supports error correction, the transmission data unit size of the transport(s), etc.
  • step 1200 a request for communication from the application and/or service level may be recognized.
  • the data that is to be transmitted may then be stored in the general buffer, which may then be passed (possibly in smaller increments or units) to a transport-specific buffer in step 1202 .
  • the transport-specific buffer may then access the selected transport in order to send the information in step 1204 , the transaction being conducted, for example, using a wired or wireless transport.
  • step 1206 a determination is made as to whether the information sent in step 1204 was successfully received. This may be confirmed, for example, by a receipt confirmation message being received. If receipt is not confirmed, then in step 1208 a determination may be made as to whether the transport should try to resend the data. This determination may be made in view of a threshold condition such as described above. If the option to retry is available, the transport may trigger the information to be resent in step 1210 . The information may be sent in step 1204 , and the verification of successful data transmission occurs again in step 1206 .
  • step 1212 the copy of the previously sent data may be deleted in step 1212 . If more data remains to be sent as determined in step 1214 , then the process may return to step 1202 where the next data unit may be passed from the general buffer to the transport-specific buffer, and in accordance with at least one exemplary embodiment of the present invention, a copy of the passed data may be stored in the general buffer. However, the occurrence of a transport failure may trigger an alternate flow.
  • step 1218 a determination may be made as to whether a transport switch (e.g., transport switch 310 ) has been enabled in the configuration of the system.
  • This configuration may reside on one or more of the devices participating in the NoTA system, and may be set on any or all of the devices depending on the specific configuration and abilities (e.g., user interface capability) of the device. If the transport switch is not set in step 1218 , then the process may terminate in step 1216 (shown as same-page reference “A” in FIG.
  • step 12 in preparation for the next communication requirement in step 1200 .
  • a transport change may be triggered in step 1220 .
  • Information regarding available transports may be obtained in step 1222 and a transport may be selected. In at least one exemplary embodiment of the present invention, this information may be ordered, for example, based on the applicability of each available transport to the information to be communicated, the conditions of the environment (e.g., interference), the condition of the device (e.g., power level), etc.
  • the selection of a transport may be verified in step 1224 .
  • the process may return to step 1222 in order to possibly refresh the transport information and choose another transport.
  • step 1226 a communication link may be established using the new transport.
  • the general buffer may then pass the saved copy of the unsuccessfully sent data to the transport-specific buffer corresponding to the newly selected transport in step 1228 .
  • the process flow may then return to step 1204 (shown as same-page reference “B” in FIG. 12 ) where the data may then be sent from the transport-specific buffer to its destination (e.g., other device) via the new transport, and a determination may again be made in step 1206 as to whether the retransmitted data, now being sent using an alternative transport, was successfully received at the destination device.
  • expedient connection reestablishment and data retransmission may be realized in scenarios where one or more active transports may fail or a determination to switch an active transport for the connection has been made.
  • data that may be awaiting transmission via Bluetooth when the transport experiences problems may be lost.
  • a copy of the unsent data abandoned in the Bluetooth data buffer may still reside in the general data buffer.
  • This backup data copy may be immediately allocated to an alternative transport (e.g., WLAN) without the burden of trying to recover and convert the Bluetooth-formatted data packets back into a transport-independent format because the “raw” data is still available in the transport-independent general data buffer in a transport-independent format.
  • the data stored in the general data buffer may be fragmented into transport-suitable packets, so that whenever the general data buffer receives an indication that the corresponding data has been successfully reached its destination, the copy stored in the general data buffer may then be removed.
  • an indication that the data has been reallocated to another transport may be provided to the Bluetooth radio control entity so that the data that was successfully sent via the alternative transport may be removed from the Bluetooth buffer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
US12/920,041 2008-02-27 2008-02-27 Buffer control for multi-transport architectures Active 2030-01-21 US9825863B2 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/IB2008/050711 WO2009106932A1 (en) 2008-02-27 2008-02-27 Buffer control for multi-transport architectures

Publications (2)

Publication Number Publication Date
US20110002344A1 US20110002344A1 (en) 2011-01-06
US9825863B2 true US9825863B2 (en) 2017-11-21

Family

ID=40245903

Family Applications (1)

Application Number Title Priority Date Filing Date
US12/920,041 Active 2030-01-21 US9825863B2 (en) 2008-02-27 2008-02-27 Buffer control for multi-transport architectures

Country Status (5)

Country Link
US (1) US9825863B2 (de)
EP (1) EP2248309B1 (de)
KR (1) KR101175689B1 (de)
CN (1) CN101960792B (de)
WO (1) WO2009106932A1 (de)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2186265B1 (de) * 2007-07-30 2011-12-21 Marvell World Trade Ltd. Gleichzeitige aufrechterhaltung von bluetooth- und 802.11-verbindungen für erhöhten datendurchsatz
EP2248309B1 (de) * 2008-02-27 2017-06-21 Nokia Technologies Oy Puffersteuerung für multitransportarchitekturen
WO2010035100A1 (en) * 2008-09-25 2010-04-01 Nokia Corporation Synchronization for device-to-device communication
CN101931576B (zh) * 2010-07-21 2015-04-01 中兴通讯股份有限公司 一种无线接入设备及方法
US8613609B2 (en) 2011-04-15 2013-12-24 Hamilton Sundstrand Corporation Bi-metal pump gear
JP5880256B2 (ja) * 2012-04-26 2016-03-08 ソニー株式会社 情報処理装置及び方法、プログラム、並びに情報処理システム
US9635677B1 (en) 2014-03-14 2017-04-25 Apple Inc. Dynamic link adaptation for improved link margin
US10516740B2 (en) 2014-05-30 2019-12-24 Apple Inc. Dynamic transport switching in inter-device communication
US10999792B2 (en) 2017-03-15 2021-05-04 Avago Technologies International Sales Pte. Limited Low power high definition wireless media transport
DE102018002069A1 (de) * 2017-03-15 2018-09-20 Avago Technologies General Ip (Singapore) Pte. Ltd. Drahtloser High-Definition-Medientransport mit geringer Leistung
US10917919B2 (en) * 2018-05-31 2021-02-09 Qualcomm Incorporated Reference signal design for medium access in cellular V2X communication
EP3930287A1 (de) * 2020-06-24 2021-12-29 Sandvine Corporation System und verfahren zur verwaltung von video-streaming mit adaptiver bitrate

Citations (65)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5491693A (en) 1993-12-30 1996-02-13 International Business Machines Corporation General transport layer gateway for heterogeneous networks
US5548723A (en) 1993-12-17 1996-08-20 Taligent, Inc. Object-oriented network protocol configuration system utilizing a dynamically configurable protocol stack
US5822598A (en) 1996-07-12 1998-10-13 Ast Research, Inc. Audio activity detection circuit to increase battery life in portable computers
US5886645A (en) * 1995-11-24 1999-03-23 Motorola, Inc. Method and apparatus for providing duplicate messages in an acknowledge-back communication system
US6148377A (en) 1996-11-22 2000-11-14 Mangosoft Corporation Shared memory computer networks
US6233224B1 (en) * 1997-09-25 2001-05-15 Sony Computer Laboratory, Inc. Communication method and data communications terminal, with data communication protocol for inter-layer flow control
US6247057B1 (en) 1998-10-22 2001-06-12 Microsoft Corporation Network server supporting multiple instance of services to operate concurrently by having endpoint mapping subsystem for mapping virtual network names to virtual endpoint IDs
US6260158B1 (en) * 1998-05-11 2001-07-10 Compaq Computer Corporation System and method for fail-over data transport
US20010051981A1 (en) 2000-06-05 2001-12-13 Microsoft Corporation Methods and systems for discovering object-exchange resources on a network
US20020080719A1 (en) * 2000-12-22 2002-06-27 Stefan Parkvall Scheduling transmission of data over a transmission channel based on signal quality of a receive channel
US20020150045A1 (en) * 2001-01-19 2002-10-17 Gereon Vogtmeier Method and device for reliable transmission of data packets
US6526487B2 (en) * 1999-12-06 2003-02-25 Legato Systems, Inc. Performing acknowledged operations on original and mirrored copies of data
US20030100308A1 (en) 2001-11-27 2003-05-29 Intel Corporation Device and method for intelligent wireless communication selection
US6597919B1 (en) * 2000-06-23 2003-07-22 Motorola, Inc. Optimal radio channel allocation in a distributed connection and transport network
US6601093B1 (en) 1999-12-01 2003-07-29 Ibm Corporation Address resolution in ad-hoc networking
US6604140B1 (en) 1999-03-31 2003-08-05 International Business Machines Corporation Service framework for computing devices
US20030231598A1 (en) * 2002-06-18 2003-12-18 Ramesh Venkataraman Method and apparatus for tracking data packets in a packet data communication system
US20030236890A1 (en) 2002-06-25 2003-12-25 Intel Corporation Wireless communication device and method for sharing device resources
WO2004008793A1 (en) 2002-07-11 2004-01-22 Qualcomm Incorporated Interface selection in a wireless communication network
US20040019640A1 (en) 2002-07-25 2004-01-29 Bartram Linda Ruth System and method for distributing shared storage for collaboration across multiple devices
US20050003822A1 (en) 2003-07-01 2005-01-06 Markus Aholainen Method and apparatus for automatically selecting a bearer for a wireless connection
US20050013259A1 (en) 2001-12-31 2005-01-20 Israel Papoushado Technique of determining connectivity solutions for network elements
US6871257B2 (en) * 2002-02-22 2005-03-22 Sandisk Corporation Pipelined parallel programming operation in a non-volatile memory system
US20050066033A1 (en) 2003-09-24 2005-03-24 Cheston Richard W. Apparatus, system, and method for dynamic selection of best network service
US20050071879A1 (en) 2003-07-10 2005-03-31 University Of Florida Research Foundation, Inc. Smart space appliance control using a mobile communications device
US6879561B1 (en) 2000-11-03 2005-04-12 Nortel Networks Limited Method and system for wireless packet scheduling with per packet QoS support and link adaptation
US20050097087A1 (en) 2003-11-03 2005-05-05 Punaganti Venkata Murali K. System and method for providing a unified framework for service discovery
US20050114448A1 (en) 2003-11-03 2005-05-26 Apacheta Corporation System and method for delegation of data processing tasks based on device physical attributes and spatial behavior
EP1542409A1 (de) 2003-12-10 2005-06-15 Sony International (Europe) GmbH Protokoll für Multi-Hop Ad-Hoc-Netzwerke
US6909721B2 (en) 2002-10-31 2005-06-21 Nokia Corporation Device detection and service discovery system and method for a mobile ad hoc communications network
US20050138173A1 (en) 2003-12-22 2005-06-23 Ha Young G. Ontology-based service discovery system and method for ad hoc networks
CN1633097A (zh) 2005-01-11 2005-06-29 中国科学院计算技术研究所 宽带无线城域网中语音业务的服务质量调度器及其方法
US20050193056A1 (en) 2002-12-26 2005-09-01 Schaefer Diane E. Message transfer using multiplexed connections in an open system interconnection transaction processing environment
US20050193106A1 (en) 2004-03-01 2005-09-01 University Of Florida Service discovery and delivery for ad-hoc networks
US20050254472A1 (en) 2004-05-11 2005-11-17 Samsung Electronics Co., Ltd. Method for service discovery in mobile ad-hoc network
US6976186B1 (en) * 2002-08-27 2005-12-13 At&T Corp. Asymmetric data mirroring
CN1758604A (zh) 2004-10-10 2006-04-12 中兴通讯股份有限公司 分布式系统中保持多个数据副本一致性的方法
US20060140146A1 (en) 2003-07-03 2006-06-29 Johannes Funk Method for controlling data circuits
US7110405B2 (en) 2001-09-18 2006-09-19 Integrated Device Technology, Inc. Multicast cell buffer for network switch
US20060221933A1 (en) * 2005-03-29 2006-10-05 Bauer Markus G Managing internet protocol based resources in a packet-based access network
US20060259606A1 (en) 2005-04-18 2006-11-16 Research In Motion Limited Method and system for executing a container managed application on a processing device
EP1758312A1 (de) 2005-08-26 2007-02-28 Matsushita Electric Industrial Co., Ltd. Steuerung abhängig von der Dienstqualität und den Kanaleigenschaften
US20070058630A1 (en) 2005-09-12 2007-03-15 Funai Electric Co., Ltd. Wireless network information distribution method
CN1949697A (zh) 2005-10-14 2007-04-18 大唐移动通信设备有限公司 一种确保收发双方数据一致的数据传输方法
CN1949698A (zh) 2005-10-10 2007-04-18 华为技术有限公司 Lte技术中的自动重传方法、发送设备和接收设备
US20070112915A1 (en) * 2003-06-04 2007-05-17 Klassen Gerhard D System and method of message transport selection
US20070141984A1 (en) 2005-12-20 2007-06-21 Microsoft Corporation Proximity service discovery in wireless networks
US20070180073A1 (en) 1999-11-08 2007-08-02 Boyle Phosphorus Llc Generic quality of service protocol and architecture for user applications in multiple transport protocol environments
WO2007095966A1 (en) 2006-02-24 2007-08-30 Telefonaktiebolaget Lm Ericsson (Publ) Technique for configuring link layer entities for a handover
US20070204275A1 (en) * 2005-08-29 2007-08-30 Rhysome, Inc. Method and system for reliable message delivery
EP1858210A1 (de) 2006-05-19 2007-11-21 Whitestein Information Technology Group AG Verfahren und System zu einem adaptiven Kommunikationsdienstzugang
US20070280111A1 (en) * 2006-05-30 2007-12-06 Martin Lund Method and system for adaptive queue and buffer control based on monitoring and active congestion avoidance in a packet network switch
US20070280277A1 (en) * 2006-05-30 2007-12-06 Martin Lund Method and system for adaptive queue and buffer control based on monitoring in a packet network switch
US7352998B2 (en) 2003-09-12 2008-04-01 Nokia Corporation Method and system for establishing a wireless communications link
US7549080B1 (en) * 2002-08-27 2009-06-16 At&T Corp Asymmetric data mirroring
US7567570B2 (en) * 2002-03-19 2009-07-28 Network Equipment Technologies, Inc. Reliable transport of TDM data streams over packet networks
US7627767B2 (en) * 2004-06-30 2009-12-01 At&T Intellectual Property I, L.P. Methods and systems for remotely securing data in a wireless device in a communications network
US7668565B2 (en) 2006-11-07 2010-02-23 Nokia Corporation Multiradio priority control based on modem buffer load
US7693952B2 (en) * 2003-03-27 2010-04-06 Microsoft Corporation Availability and scalability in a messaging system in a manner transparent to the application
US7697893B2 (en) 2004-06-18 2010-04-13 Nokia Corporation Techniques for ad-hoc mesh networking
US7787367B2 (en) * 2006-05-23 2010-08-31 International Business Machines Corporation Method and a system for flow control in a communication network
US20110002344A1 (en) * 2008-02-27 2011-01-06 Nokia Corporation Buffer control for multi-transport architectures
US8320373B2 (en) * 2007-08-23 2012-11-27 Qualcomm Incorporated Packet-based processing system
US8576861B2 (en) * 2007-05-21 2013-11-05 International Business Machines Corporation Method and apparatus for processing packets
US9119180B2 (en) * 2008-02-27 2015-08-25 Nokia Corporation Transport independent architecture

Patent Citations (68)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5548723A (en) 1993-12-17 1996-08-20 Taligent, Inc. Object-oriented network protocol configuration system utilizing a dynamically configurable protocol stack
US5491693A (en) 1993-12-30 1996-02-13 International Business Machines Corporation General transport layer gateway for heterogeneous networks
US5886645A (en) * 1995-11-24 1999-03-23 Motorola, Inc. Method and apparatus for providing duplicate messages in an acknowledge-back communication system
US5822598A (en) 1996-07-12 1998-10-13 Ast Research, Inc. Audio activity detection circuit to increase battery life in portable computers
US6148377A (en) 1996-11-22 2000-11-14 Mangosoft Corporation Shared memory computer networks
US6233224B1 (en) * 1997-09-25 2001-05-15 Sony Computer Laboratory, Inc. Communication method and data communications terminal, with data communication protocol for inter-layer flow control
US6260158B1 (en) * 1998-05-11 2001-07-10 Compaq Computer Corporation System and method for fail-over data transport
US6247057B1 (en) 1998-10-22 2001-06-12 Microsoft Corporation Network server supporting multiple instance of services to operate concurrently by having endpoint mapping subsystem for mapping virtual network names to virtual endpoint IDs
US6604140B1 (en) 1999-03-31 2003-08-05 International Business Machines Corporation Service framework for computing devices
US20070180073A1 (en) 1999-11-08 2007-08-02 Boyle Phosphorus Llc Generic quality of service protocol and architecture for user applications in multiple transport protocol environments
US6601093B1 (en) 1999-12-01 2003-07-29 Ibm Corporation Address resolution in ad-hoc networking
US6526487B2 (en) * 1999-12-06 2003-02-25 Legato Systems, Inc. Performing acknowledged operations on original and mirrored copies of data
US6931502B2 (en) * 1999-12-06 2005-08-16 Emc Corporation Recovery of data using write request copies in delta queue
US20010051981A1 (en) 2000-06-05 2001-12-13 Microsoft Corporation Methods and systems for discovering object-exchange resources on a network
US6597919B1 (en) * 2000-06-23 2003-07-22 Motorola, Inc. Optimal radio channel allocation in a distributed connection and transport network
US6879561B1 (en) 2000-11-03 2005-04-12 Nortel Networks Limited Method and system for wireless packet scheduling with per packet QoS support and link adaptation
US20020080719A1 (en) * 2000-12-22 2002-06-27 Stefan Parkvall Scheduling transmission of data over a transmission channel based on signal quality of a receive channel
US20020150045A1 (en) * 2001-01-19 2002-10-17 Gereon Vogtmeier Method and device for reliable transmission of data packets
US7110405B2 (en) 2001-09-18 2006-09-19 Integrated Device Technology, Inc. Multicast cell buffer for network switch
US20030100308A1 (en) 2001-11-27 2003-05-29 Intel Corporation Device and method for intelligent wireless communication selection
US20050013259A1 (en) 2001-12-31 2005-01-20 Israel Papoushado Technique of determining connectivity solutions for network elements
US6871257B2 (en) * 2002-02-22 2005-03-22 Sandisk Corporation Pipelined parallel programming operation in a non-volatile memory system
US7162569B2 (en) * 2002-02-22 2007-01-09 Sandisk Corporation Pipelined parallel programming operation in a non-volatile memory system
US7567570B2 (en) * 2002-03-19 2009-07-28 Network Equipment Technologies, Inc. Reliable transport of TDM data streams over packet networks
US20030231598A1 (en) * 2002-06-18 2003-12-18 Ramesh Venkataraman Method and apparatus for tracking data packets in a packet data communication system
US20030236890A1 (en) 2002-06-25 2003-12-25 Intel Corporation Wireless communication device and method for sharing device resources
WO2004008793A1 (en) 2002-07-11 2004-01-22 Qualcomm Incorporated Interface selection in a wireless communication network
US20040019640A1 (en) 2002-07-25 2004-01-29 Bartram Linda Ruth System and method for distributing shared storage for collaboration across multiple devices
US7549080B1 (en) * 2002-08-27 2009-06-16 At&T Corp Asymmetric data mirroring
US6976186B1 (en) * 2002-08-27 2005-12-13 At&T Corp. Asymmetric data mirroring
US6909721B2 (en) 2002-10-31 2005-06-21 Nokia Corporation Device detection and service discovery system and method for a mobile ad hoc communications network
US7590097B2 (en) 2002-10-31 2009-09-15 Nokia Corporation Device detection and service discovery system and method for a mobile ad hoc communications network
US20050193056A1 (en) 2002-12-26 2005-09-01 Schaefer Diane E. Message transfer using multiplexed connections in an open system interconnection transaction processing environment
US7693952B2 (en) * 2003-03-27 2010-04-06 Microsoft Corporation Availability and scalability in a messaging system in a manner transparent to the application
US20070112915A1 (en) * 2003-06-04 2007-05-17 Klassen Gerhard D System and method of message transport selection
US20050003822A1 (en) 2003-07-01 2005-01-06 Markus Aholainen Method and apparatus for automatically selecting a bearer for a wireless connection
US20060140146A1 (en) 2003-07-03 2006-06-29 Johannes Funk Method for controlling data circuits
US20050071879A1 (en) 2003-07-10 2005-03-31 University Of Florida Research Foundation, Inc. Smart space appliance control using a mobile communications device
US7352998B2 (en) 2003-09-12 2008-04-01 Nokia Corporation Method and system for establishing a wireless communications link
US20050066033A1 (en) 2003-09-24 2005-03-24 Cheston Richard W. Apparatus, system, and method for dynamic selection of best network service
US20050097087A1 (en) 2003-11-03 2005-05-05 Punaganti Venkata Murali K. System and method for providing a unified framework for service discovery
US20050114448A1 (en) 2003-11-03 2005-05-26 Apacheta Corporation System and method for delegation of data processing tasks based on device physical attributes and spatial behavior
EP1542409A1 (de) 2003-12-10 2005-06-15 Sony International (Europe) GmbH Protokoll für Multi-Hop Ad-Hoc-Netzwerke
US20050138173A1 (en) 2003-12-22 2005-06-23 Ha Young G. Ontology-based service discovery system and method for ad hoc networks
US20050193106A1 (en) 2004-03-01 2005-09-01 University Of Florida Service discovery and delivery for ad-hoc networks
US20050254472A1 (en) 2004-05-11 2005-11-17 Samsung Electronics Co., Ltd. Method for service discovery in mobile ad-hoc network
US7697893B2 (en) 2004-06-18 2010-04-13 Nokia Corporation Techniques for ad-hoc mesh networking
US7627767B2 (en) * 2004-06-30 2009-12-01 At&T Intellectual Property I, L.P. Methods and systems for remotely securing data in a wireless device in a communications network
CN1758604A (zh) 2004-10-10 2006-04-12 中兴通讯股份有限公司 分布式系统中保持多个数据副本一致性的方法
CN1633097A (zh) 2005-01-11 2005-06-29 中国科学院计算技术研究所 宽带无线城域网中语音业务的服务质量调度器及其方法
US20060221933A1 (en) * 2005-03-29 2006-10-05 Bauer Markus G Managing internet protocol based resources in a packet-based access network
US20060259606A1 (en) 2005-04-18 2006-11-16 Research In Motion Limited Method and system for executing a container managed application on a processing device
EP1758312A1 (de) 2005-08-26 2007-02-28 Matsushita Electric Industrial Co., Ltd. Steuerung abhängig von der Dienstqualität und den Kanaleigenschaften
US20070204275A1 (en) * 2005-08-29 2007-08-30 Rhysome, Inc. Method and system for reliable message delivery
US20070058630A1 (en) 2005-09-12 2007-03-15 Funai Electric Co., Ltd. Wireless network information distribution method
CN1949698A (zh) 2005-10-10 2007-04-18 华为技术有限公司 Lte技术中的自动重传方法、发送设备和接收设备
CN1949697A (zh) 2005-10-14 2007-04-18 大唐移动通信设备有限公司 一种确保收发双方数据一致的数据传输方法
US20070141984A1 (en) 2005-12-20 2007-06-21 Microsoft Corporation Proximity service discovery in wireless networks
WO2007095966A1 (en) 2006-02-24 2007-08-30 Telefonaktiebolaget Lm Ericsson (Publ) Technique for configuring link layer entities for a handover
EP1858210A1 (de) 2006-05-19 2007-11-21 Whitestein Information Technology Group AG Verfahren und System zu einem adaptiven Kommunikationsdienstzugang
US7787367B2 (en) * 2006-05-23 2010-08-31 International Business Machines Corporation Method and a system for flow control in a communication network
US20070280277A1 (en) * 2006-05-30 2007-12-06 Martin Lund Method and system for adaptive queue and buffer control based on monitoring in a packet network switch
US20070280111A1 (en) * 2006-05-30 2007-12-06 Martin Lund Method and system for adaptive queue and buffer control based on monitoring and active congestion avoidance in a packet network switch
US7668565B2 (en) 2006-11-07 2010-02-23 Nokia Corporation Multiradio priority control based on modem buffer load
US8576861B2 (en) * 2007-05-21 2013-11-05 International Business Machines Corporation Method and apparatus for processing packets
US8320373B2 (en) * 2007-08-23 2012-11-27 Qualcomm Incorporated Packet-based processing system
US20110002344A1 (en) * 2008-02-27 2011-01-06 Nokia Corporation Buffer control for multi-transport architectures
US9119180B2 (en) * 2008-02-27 2015-08-25 Nokia Corporation Transport independent architecture

Non-Patent Citations (37)

* Cited by examiner, † Cited by third party
Title
Celeste Campo, et al: "DNS-Based Service Discovery in Ad Hoc Networks: Evaluation and Improvements" Personal Wireless Commnications Lecture Notes in Computer Science; LNCS, Springer Berlin, DE, vol. 4217, Jan. 1, 2006 (Jan. 1, 2006), pp. 111-122, XP019044018 ISBN: 978-3-540-45174-7, section 2.
Desoli et al., "An Outlook on the Evolution of Mobile Terminals: From monolithic to modular multiradio, multiapplication platforms", IEEE Circuits and Systems Magazine, IEEE Service Center, New York, vol. 6, No. 2, Jan. 1, 2006, pp. 17-29.
Dobrev et al., "Device and Service Discovery in Home Networks with OSGi", In-Home Networking, IEEE Communications Magazine, Aug. 2002, 7 pages.
EP Communication dated Aug. 22, 2016 for European Patent Application No. 08719493.2, 6 pages.
Eriksson et al., "Providing Quality of Service in Always Best Connected Networks", IEEE Communicaitons Magazine, IEEE Service Center, Piscataway, US, vol. 41, No. 7, Jul. 2003, pp. 154-163.
Final Technology Evaluation Report SIRENA Service Infrastructure for Real-time Embedded Networked Applications ITEA 02014 Project Reference WP2/110 Version V1.0 Author(s) / Organisation SIRENA Consortium Date May 14, 2004.
Frank et al, "A Customizable Shared Information Space to Support Concurrent Design", Computers in INdustry, Elsevier Science Publishers, Amsterdam, NL, vol. 48, No. 1, May 1, 2002, pp. 45-57.
International Search Report and Written Opinion for corresponding Patent Cooperation Treaty Application No. PCT/IB2008/050711, dated Feb. 2, 2009, 14 pages.
International Search Report and Written Opinion for PCT/FI2008/050242, dated Aug. 18, 2008, 12 pages.
International Search Report and Written Opinion for PCT/IB2008/052437, dated May 1, 2009, 14 pages.
International Search Report and Written Opinion for PCT/IB2008/053759 dated Mar. 27, 2009, 15 pages.
International Search Report and Written Opinion of the International Searching Authority for corresponding Patent Cooperation Treaty Application No. PCT/IB2007/054550 dated Oct. 15, 2008, 12 pages.
International Search Report and Written Opinion of the International Searching Authority for Patent Cooperation Treaty Application No. PCT/IB2008/050708 dated Mar. 3, 2009, 17 pages.
International Search Report and Written Opinion of the International Searching Authority for PCT/IB2008/050709, dated Feb. 25, 2009, 18 pages.
Kim et al., "Service Discovery Using FIPA-Compliant AP to Support Scalability in Ubiquitous Environments", Proceedings of the Fourth Annual ACIS International Conference on Computer and Information Science on 2005, pp. 647-652.
Kliazovich et al., "A Delayed-ACK Scheme for MAC-Level Performance Enhancement of Wireless LANs", Telecommunications and Networking—ICT 2004; [Lecture Notes in Computer Science; ; LNCS], Springer-Verlag, Berlin/Heidelberg, vol. 3124, Jul. 2004, pp. 1289-1295.
Kronlof et al., "Advances in Design and Specification Languages for Embedded Systems", Jul. 19, 2007, Springer, Netherlands.
Lapetelainen et al., "Networked Systems, Services and Information", NOTA2008, 1st International network on Terminal Architecture Conference, Jun. 11, 2008, pp. 1-7.
Lee et al., "Protocols for Service Discovery in Dynamic and Mobile Networks", International Journal of Computer Research, vol. 11, No. 1, 2002, pp. 1-12.
Lent, R.; "Smart packet-based selection of reliable paths in ad hoc networks" Design of Reliable Communication Networks, 2005. (DRCN 2005). Proceedings.5th International Workshop on Oct. 16-19, 2005 pp. 5 pp.
Miaoqing, "Service Discovery between Multiple Home Networks", TKK T-110.5190 Seminar on Internetworking, Mar. 4-5, 2007.
Office Action from European Patent Application No. 08776431.2, dated Aug. 2, 2010, 6 pages.
Quiroz, et al., "Version vectors based synchronization engine for mobile devices", Proceeding PDCN'07 Proceedings of the 25th conference on Proceedings of the 25th IASTED International Multi-Conference: parallel and distributed computing and networks 2007.
Raverdy et al., "A Multi-Protocol Approach to Service Discovery and Acces in Pervasive Environments", Mobile and Ubiquitous Systems: Networking & Services, 2006 Third Annual International Conference on Jul. 2006, IEEE 2006, pp. 1-9.
Raverdy et al., "Efficient Context-aware Service Discovery in Multi-Progtocol Pervasive Environments", Mobile Data Management, 7th International Conference, Conference Proceedings Article, IEEE, May 10, 2006.
Rekimoto et al., "A Multiple Device Approach for Supporting Whiteboard-Based Interactions", Chi '98. Human Factors in Computing Systems, Conference Proceedings, Los Angeles, CA, Apr. 18-23, 1998.
Scholten et al., "Secure Service Discovery in Home Networks", International Conference on Consumer Electronics, 2006, ICCE '06, 2006 Digest of Technical Papers, Jan. 7-11, 2006, pp. 115-116.
SE GI HONG ; SUMAN SRINIVASAN ; HENNING SCHULZRINNE: "Accelerating Service Discovery in Ad-Hoc Zero Configuration Networking", GLOBAL TELECOMMUNICATIONS CONFERENCE, 2007. GLOBECOM '07. IEEE, IEEE, PISCATAWAY, NJ, USA, 1 November 2007 (2007-11-01), Piscataway, NJ, USA, pages 961 - 965, XP031196113, ISBN: 978-1-4244-1042-2, DOI: 10.1109/GLOCOM.2007.853
Se Gi Hong, et al: "Accelerating Service Discovery in Ad-Hoc Zero Configuration Networking" Global Telecommunications Conference, 2007. Globecom '07. IEEE, IEEE, Piscataway, NJ, USA, Nov. 1, 2007 (Nov. 1, 2007), pp. 962-965, XP031196113 ISBN: 978-1-4244-1042-2, section II.
Steenkiste, P. A., "A Systematic Approach to Host Interface Design for High-Speed Networks", Computer, IEEE Service Center, Mar. 1994, pp. 47-57 and pp. 12-13.
Sttenkiste, "A Systematic Approach to Host Interface Design for High Speed Networks", Computer, IEEE Service Center, Los Alamitos, CA, US, vol. 27, No. 3, Mar. 1994, pp. 47-57.
Stuart Cheshire; Marc Krochmal, Apple Computer, et al: "DNA-Based Service Discovery; draft-cheshire-dnsext-dnssd-04.text" IETF Standard-Working-Draft, Internet Engineering Task Force, IETF, CH, No. 4, Aug. 10, 2006 (Aug. 10, 2006), XP015046478 ISSN: 0000-0004, section 14.
Suoranta et al., "New Directions in Mobile Device Architectures", Digital System Design: Architectures, Methods and Tools, 2006. DSD 200 6, 9th Euromicro Conference on IEEE PI, Jan. 2006, pp. 17-26.
Suoranta et al., "New Directions in Mobile Device Architectures", Digital System Design: Architectures, Methods and Tools, 2006. DSD 200 6. 9th Euromicro Conference on, IEEE, PI, Jan. 1, 2006, pp. 17-26.
Tandler, "Software Infrastructure for Ubiquitous Computing Environments: Supporting Synchronous Collaboration with Heterogeneous Devices", Lecture Notes in Computer Science, LNCS, vol. 2201/2001, Jan. 1, 2001, pp. 95-115.
The Salutation Corsortium, "Salutation Architecture Specification (Part 1), Version 2.1" Salutation Architecture Specification, XX, XX, Dec. 31, 1999, i-v, 1.
WALTER DIDIMO;MAURIZIO PATRIGNANI: "Network and Parallel Computing", vol. 4217, 1 January 2006, SPRINGER INTERNATIONAL PUBLISHING, Cham, ISBN: 978-3-642-24784-2, ISSN: 0302-9743, article CELESTE CAMPO; CARLOS GARCÍA-RUBIO;: "DNS-Based Service Discovery in Ad Hoc Networks: Evaluation and Improvements", pages: 111 - 122, XP019044018, 032548

Also Published As

Publication number Publication date
CN101960792B (zh) 2014-05-28
CN101960792A (zh) 2011-01-26
EP2248309B1 (de) 2017-06-21
US20110002344A1 (en) 2011-01-06
KR101175689B1 (ko) 2012-08-23
WO2009106932A1 (en) 2009-09-03
EP2248309A1 (de) 2010-11-10
KR20100127796A (ko) 2010-12-06

Similar Documents

Publication Publication Date Title
US9825863B2 (en) Buffer control for multi-transport architectures
US11381514B2 (en) Methods and apparatus for early delivery of data link layer packets
US10321513B2 (en) Method for PDCP control PDU transmission by user equipment (UE)
JP5301533B2 (ja) ニアフィールド・リンクを最適化する方法
US8605578B1 (en) System and method for handling of destination host side congestion
CN101491005A (zh) 用于无线通信系统中的策略执行的方法和装置
CN108023683A (zh) 一种发送报文的方法、装置、芯片及终端
CA2656660C (en) Client/bridge and method and system for using same
WO2022001175A1 (zh) 数据包发送的方法、装置
CN107735985B (zh) 电子装置、其无线通信方法及非暂时性计算机可读存储介质
US9081905B2 (en) Low latency interconnect bus protocol
US20150016246A1 (en) Communication terminal
WO2006002579A1 (fr) Procede de transmission de donnees entre des appareils de reseau
EP3410637B1 (de) Informationsübertragungsverfahren, gateway und steuergerät
WO2009106931A1 (en) Transport selection for multi-transport structures
CN102946402B (zh) 通信方法以及蓝牙装置
WO2007074343A2 (en) Processing received data
CN116192863B (zh) 微服务流量处理方法、dpu服务网格部署方法及系统
WO2024037254A1 (zh) 一种通信方法及装置
CN103812606A (zh) 提高无线链路的效率的方法和系统
EP2177064B1 (de) Kontrolle des datenflusses
JP3941560B2 (ja) 無線通信システム
KR102406213B1 (ko) 이동단말기의 데이터 전송 방법
CN118467454A (zh) 一种数据传输方法、装置、设备、介质及计算机程序产品
CN118714183A (zh) 报文传输的方法和装置

Legal Events

Date Code Title Description
AS Assignment

Owner name: NOKIA CORPORATION, FINLAND

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:PALIN, ARTO;TUUPOLA, JUHA-MATTI;ERIKSSON, TIMO;AND OTHERS;SIGNING DATES FROM 20100611 TO 20100614;REEL/FRAME:024902/0191

AS Assignment

Owner name: NOKIA TECHNOLOGIES OY, FINLAND

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NOKIA CORPORATION;REEL/FRAME:035496/0698

Effective date: 20150116

STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4