Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W28/00—Network traffic management; Network resource management
  • H04W28/02—Traffic management, e.g. flow control or 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/50—Queue scheduling
  • H04L47/62—Queue scheduling characterised by scheduling criteria
  • H04L47/625—Queue scheduling characterised by scheduling criteria for service slots or service orders
  • H04L47/626—Queue scheduling characterised by scheduling criteria for service slots or service orders channel conditions
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/01—Protocols
  • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/50—Network services
  • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L67/62—Establishing a time schedule for servicing the requests
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/50—Network services
  • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L67/61—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources taking into account QoS or priority requirements

Definitions

• the technology disclosed herein relates generally to the field of wireless communication systems, and in particular uploading and downloading of data within such wireless communication systems in a postponed manner.
• wireless communication devices to increase correspondingly.
• the performance and capabilities of the wireless communication devices are also improving, for example in that they comprise larger storage space for downloaded content as well as increased processing power. These as well as other improvements render multimedia experiences more enjoyable even on smaller, portable communication devices, which further encourages increase of traffic volumes. Further still, the cost for chipsets is decreasing and will allow massive deployment of standalone unmanned control equipment, such as e.g. surveillance cameras, which may be constantly connected to the wireless
• congestion problems may result in users of the communication devices perceiving and experiencing a degradation in the services provided.
• the congestion problems may also result in high processing load in radio access nodes of the communication system during peak requests.
• An object of the invention is to overcome or at least alleviate one or more of the above mentioned problems.
• the object is, according to a first aspect, achieved by a method in a control node of a communication system for scheduling delivery of data.
• the control node is arranged to communicate with a base station node of the communication system, and the base station node is arranged to communicate wirelessly with a user device.
• the method comprises receiving, from the user device, a request for delivery of data to or retrieval of data from the user device, the request comprising a time limit by which to provide the requested data, and scheduling, based on downloading and/or uploading conditions, the requested data for provision to the user device or to a client node associated with the user device before the expiry of the received time limit.
• the data may be delivered in a postponed manner.
• the data traffic within the communication system can thereby be planned, for example in such a way to avoid traffic load peaks. This results in an improvement in user satisfaction, and users can be encouraged to send data during off-peak load times for example by differentiating the pricing in dependence on time of day.
• the object is, according to a second aspect, achieved by a control node of a communication system for scheduling delivery of data.
• the control node is arranged to communicate with a base station node of the communication system, and the base station node is arranged to communicate with a wireless user device.
• the control node comprises a processing unit configured to: receive, from the user device, a request for delivery of data to or retrieval of data from the user device, the request comprising a time limit by which to provide the requested data, and schedule, based on downloading and/or uploading conditions, the requested data for provision to the user device or to a client node associated with the user device before the expiry of the received time limit.
• control node is arranged to communicate with a base station node of the communication system, and the base station node is arranged to communicate with a wireless user device.
• the computer program comprises computer program code, which, when run on a processing unit of the control node, causes the processing unit to perform the steps of: receiving, from the user device, a request for delivery of data to or retrieval of data from the user device, the request comprising a time limit by which to provide the requested data; and scheduling, based on downloading and/or uploading
• the object is, according to a fourth aspect, achieved by a computer program product comprising a computer program as above, and computer readable means on which the computer program is stored.
• the object is, according to a fifth aspect, achieved by a method performed in a user device of a communication system comprising a base station node and a control node.
• the control node is arranged to communicate with the base station node, and the base station node is arranged to communicate with the user device.
• FIG 1 illustrates schematically an environment in which
• Figure 2a is a sequence diagram illustrating the providing of data in an aspect of the disclosure.
• Figure 2b is another sequence diagram illustrating the providing of data in another aspect of the disclosure.
• FIG. 3 is still another sequence diagram illustrating the
• Figure 4 illustrates an embodiment and exemplifying signaling paths for providing data.
• Figure 5 is a flow chart of a method performed in a control node.
• Figure 6 illustrates an exemplifying control node comprising means for implementing embodiments of the disclosure.
• Figure 7 is a flow chart of a method performed in a user device.
• Figure 8 illustrates an exemplifying user device comprising means for implementing embodiments of the disclosure.
• Figure 9 illustrates a mobile user device to mobile user device scenario .
• Figure 10 illustrates a handover scenario when implementing aspects of the present disclosure.
• FIG. 1 illustrates schematically an environment in which
• a communication system 1 comprises a control node 2 arranged to communicate with a base station node 3, 4, 5.
• the base station node 3 is in turn arranged to communicate wirelessly with a user device 6, 7, 10, i.e. over a radio interface.
• the communication system 1 may comprise a Long Term Evolution (LTE) system, in which case the base station 3, 4, 5 comprises an evolved node B (eNB) and the control node 2 may then e.g. be embodied as a mobility management entity (MME) .
• LTE Long Term Evolution
• eNB evolved node B
• MME mobility management entity
• WCDMA Wideband Code Division Multiple Access
• the base station node 3, 4, 5 may comprise a base transceiver station (BTS) and the control node may then comprise a radio network controller (RNC) .
• BTS base transceiver station
• RNC radio network controller
• the communication system 1 further comprises or provides
• the service provider 8 may for example comprise a web site from which the user of the user device 6, 7 may download movies or music using an internet protocol (IP) .
• IP internet protocol
• the user devices 10 may be associated with a client node 9.
• a central office of a company has installed a user device 10 with which it may communicate over the communication system 1.
• the user device 10 may comprise a surveillance unit comprising a camera device taking pictures used for monitoring toll gates.
• the surveillance unit is then provided with communication means for transmitting the pictures wirelessly to the base station node 3, 4, 5, and further to e.g. a governmental office handling toll fees.
• the governmental office then comprises a client node 9, in particular a fixed client node, for requesting and receiving the pictures conveyed from the base station node and over a wire lined part of the communication system 1.
• client node is intended to encompass devices such as a computer or other processing unit implementing aspects of the disclosure.
• the client node may comprise a network entity, located at the core network side, terminating a protocol, Nb-CAP, provided in an aspect of the present disclosure and which will be described later.
• Nb-CAP terminating a protocol
• the client node enables submission of requests to send data through a protocol transfer or to receive data via a protocol transfer.
• client node can be implemented in a variety of devices connected to the core network, ranging from tablets and personal computers for personal peer to peer scenarios, up to medium/huge servers explicitly dedicated to the service in case of commercial usage.
• the present disclosure provides devices and methods for delivering requested data in a postponed manner. Delivery can be effectuated when availability of radio resources and/or upload/download conditions are such that the requested data, which is typically non-delay sensitive data, can be sent without impacting the transmission of delay sensitive data. Radio resource contention caused by simultaneous access to a radio channel by a user with low priority demands and a user with high priority is thereby avoided.
• FIG. 2a is a sequence diagram illustrating the providing of data in an aspect of the disclosure, and in particular a scenario wherein data is obtained from a mobile device client to a fixed network client.
• a client node 9, in particular a fixed network client sends a data transfer request to a user device 10 , which may be a wireless network device client (arrow 100) .
• the client node 9 may request image data from the user device 10, which comprises a surveillance unit with a camera and which is able to communicate over a wireless network part of the communication system 1.
• the user device 10 sends an acknowledgment to the client node 9, acknowledging the data transfer request.
• the user device 10 also sends (arrow 102) a message to the control node 2, informing it about the data transfer request and providing
• control node 2 then takes charge of the data transfer request for effectuating the data transfer at a suitable time.
• the control node 2 monitors (arrows 103a and 103b) download
• the download conditions may for example comprise channel availability and/or cell load of the base station node 3.
• the control node 2 schedules (arrow 104) a suitable download time.
• a download time is suitable e.g. when the download would not affect delay-sensitive data. For example, since the requested data typically is non-delay sensitive data, e.g.
• arrows 103a, 103b and 104) may be considered as a periodic loop between the control node 2 and the base station node 3 , as indicated by the box 105, drawn with dashed lines.
• control node 2 When a scheduled download time occurs the control node 2 requests (arrow 106) the data from the user device 10, the request being made via the base station node 3. The user device 10 then transmits
• the requested data to the control node 2, via the base station node 3 and the communication system 1. That is, the user device 10 sends the requested data wirelessly to the base station node 3, which forwards it over a fixed network to the control node 2.
• the control node 2 Upon reception of the requested data, the control node 2 stores it (arrow 108) .
• Storage medium for this end may be included in the control node 2 or be located external to the control node 2.
• the monitoring of download conditions, scheduling of download time, requesting and transmitting of data and storage thereof i.e. arrows 103a, 103b, 104, 106, 107 and 108) may be considered as a loop between the control node 2, base station node 3 and the user device 10, wherein the requested data is transferred and stored in chunks in the control node 2.
• the control node 2 transfers (arrow 110) it to the requesting part, i.e. to the client node 9.
• the transfer of the requested data from the control node 2 to the client node 9 is typically effectuated over a fixed network part of the communication system 1 and performed at a single transfer occasion, i.e. all data is transferred over a wired connection without dividing it in several chunks of data spread over time. It is noted that the data may well be divided in several packets as is customary within a packet network and therefore also over a relatively short time period. However, the data transfer is performed within a relatively short time period, which "single transfer occasion" is intended to mean.
• the client node 9 may acknowledge the reception of the requested data (arrow 111) to the control node 2.
• the control node 2 may then delete (arrow 112) the data from the storage medium.
• Figure 2b is another sequence diagram illustrating the providing of data in another aspect of the disclosure, and in particular a scenario wherein data is transferred from a fixed network client to a mobile device client.
• the data transfer may comprise uploading to the user device 10 updated software to be used, e.g. to replace former software.
• a client node 9, in particular a fixed network client sends to a user device 10, in particular a wireless network device client, a request (arrow 201) for a data transfer.
• the request may be done using an internet protocol.
• the user device 10 acknowledges the data transfer request by sending (arrow 202b) an acknowledgement to the client node 9, thereby acknowledging the permission to send data and also providing e.g. an IP address of the control node 2 from where the data will be requested.
• the acknowledgment is sent (arrow 202a) also to the control node 2, informing the control node 2 about the forthcoming data request and requesting the transfer of data from the client node 9 to the control node 2.
• the data is then sent (arrow 203b) to the control node 2 from the client node 9 when the control node 2 requires it to be sent (arrow 203a) , and stored (arrow 204) by the control node 2 in a storage medium.
• the storage medium may also in this case be storage space located internally in the control node or located externally thereto.
• Loops 207 and 210 correspond to the loops 105 and 109 of figure 2a, but with the reverse data transfer direction.
• the control node 2 monitors (arrows 205a and 205b) upload conditions (instead of download conditions) by inquiring the base station node 3 about such conditions and receiving from the base station node 3 the inquired conditions.
• upload conditions may comprise the monitoring of the same type of parameters. That is, the upload conditions may for example comprise channel availability and/or cell load of the base station node 3.
• the control node 2 schedules (arrow 206) a suitable upload time. Again, an upload time is suitable e.g. when the uploading would not affect delay-sensitive data.
• the monitoring and scheduling i.e. arrows
• 205a, 205b and 206) may be considered as a periodic loop between the control node 2 and the base station node 3 , as indicated by the box 207, drawn with dashed lines.
• the control node 2 When a scheduled upload time occurs, e.g. when the traffic load in a cell provided by the base station node 3 is low, the control node 2 sends (arrow 208) the data to the user device 10, the transmission being made via the base station node 3. That is, the control node 2 sends the data to the base station node 3, e.g. over a fixed network, which base station node 3 forwards it over a wireless network part of the communication system 1 to the user device 10. The user device 10 may then transmit (arrow 209) a confirmation message in response, confirming the reception of the data.
• transmitting and confirming of data may be considered as a loop between the control node 2, base station node 3 and the user device 10, whereby the requested data is transferred in chunks.
• This loop is indicated by box 210 drawn with dashed lines.
• control node 2 may send (arrow 211) a confirmation to the client node 9, confirming that delivery of the data has been completed.
• control node 2 may delete (arrow 212) the stored data.
• FIG. 3 is still another sequence diagram illustrating the
• figure 3 discloses a scenario for data download from a service provider 8, e.g. a fixed network content distributor, to a user device 6, e.g. a wireless user device such as a mobile
• Figure 3 thus illustrates a content distributor scenario in contrast to the peer to peer transaction type described earlier.
• the user device 6 requests (arrow 301) a particular service from a service provider 8. This request may comprise or be preceded by a number of sub-steps, e.g. payment of the service, authentication etc.
• the service provider 8 transmits (arrow 302) a message
• the user device 6 sends (arrow 303) the received access information to the control node 2 and includes a time limit by which the data should be provided to it .
• the access information enables the control node 2 to request the data, which may be (and typically is) ciphered.
• the control node 2 thus requests (arrow 304) , from the service provider 8, the data by using the access information.
• the service provider 8 sends (arrow 305) the requested data to the control node 2, which stores the data (arrow 306) .
• Loops 309 and 310 indicated at respective boxes drawn with dashed lines, corresponds to loops 105 and 109 of figure 2a.
• control node 2 monitors (arrows 307a and 307b) upload conditions (uploading from control node 2 to user device 6) by inquiring the base station node 3 about such conditions and receiving from the base station node 3 the inquired conditions.
• upload conditions uploading from control node 2 to user device 6
• the control node 2 schedules (arrow 308) a suitable upload time.
• An upload time is suitable e.g. when the upload would not affect delay- sensitive data.
• the user of the user device 6 may e.g. be offered a lower traffic rate if the uploading is performed during night and therefore choose a time limit accordingly.
• the monitoring and scheduling i.e. arrows 307a, 307b and 308) may be considered as a periodic loop between the control node 2 and the base station node 3, as indicated by the box 309, drawn with dashed lines.
• the control node 2 sends (arrow 310) the data to the user device 6, the transmission being made via the base station node 3 , which in turn sends the data wirelessly to the user device 6.
• the user device 6 Upon reception of the requested data, the user device 6 sends (arrow 311) a confirmation message to the control node 2.
• the monitoring of upload conditions, scheduling of upload time, transmitting of data and confirmation thereof i.e. arrows 307a, 307b, 308, 310 and 311) may be considered as a loop between the control node 2, base station node 3 and the user device 6, wherein the requested data is transferred to the user device 6 in chunks. It is noted that in another embodiment, the confirming (arrow 311) of reception of a chunk of data may be omitted.
• control node 2 may delete (arrow 312) the stored data from the storage medium.
• Figure 4 illustrates an embodiment and exemplifies signaling paths for providing data.
• the nodes are denoted in accordance with the vocabulary used for 3GPP/LTE systems, but it is noted that corresponding signaling paths may be implemented in other communication systems.
• a server side software (SW) a client side SW and a protocol connecting the two is implemented and used.
• the protocol is denoted Network-based Content access protocol, Nb-CAP, herein.
• a transaction element is used on elements of the communication system 1 that distribute third parties content in compliance with the Nb-CAP.
• the control node hosts such server module, serving the requests from client instances installed in the user equipment or in core network elements.
• the transaction elements may also be installed in web sites of service providers selling some content.
• the queries are made and served using the Nb-CAP to request access to the content, which will be downloaded/uploaded later, i.e. in a delayed manner as has been described.
• the server module may receive requests from the user device comprising information on the network location of resource to access, a timeframe within which the request should be processed, information related to secure access to the desired data. Using such information, the server module will take care of accessing the resources via the core (or fixed) network part of the communication system and locally store them until the radio access network conditions are such as to allow content delivery.
• a user uses a user device (denoted UE, user equipment, in the figure) to access a web site of a content distributor (also denoted service provider herein) , completing a purchase procedure (signaling path indicated at box 1) .
• the web site sends an Nb-CAP transaction report back to the user device when the transaction is completed (signaling path indicated at box 2) .
• These both signaling paths go over a radio interface between the user device and eNB, a gateway PS-GW, core network FN.
• the user device forwards (signaling path indicated at box 3) to the Nb-CAP server comprised in the MME the access information. If the data is to be sent ciphered from the content distributor (service provider) , deciphering information is kept at the user device, and not forwarded to the MME.
• the Nb-CAP server of the MME requests data using the access
• the data may be downloaded ciphered, and the file comprising the data is still ciphered when transferred to the MME.
• FIG. 5 is a flow chart of a method 20 for scheduling delivery of data in a postponed manner.
• the method 20 is performed in a control node 2 of a communication system 1, such as the communication system 1 described in relation to figure 1.
• the method 20 comprises receiving 21, from the user device 6; 10, a request for
• the request comprises a time limit by which to provide the requested data (also refer to figures 2a, 2b and 3, arrows 100, 201 and 301, respectively, and related description) . It is noted that the request typically comprises other information as well, e.g. the Network Address of the peer client node, i.e. where the data should be delivered/accessed, a transaction ID etc.
• the method 20 further comprises scheduling 22, based on downloading and/or uploading conditions, the requested data for provision to the user device 6; 10 or to a client node 9 associated with the user device 6; 10 before the expiry of the received time limit (also refer to figures 2a, 2b, 3, loops 105, 207 and 309, respectively, and related description) .
• the method 20 comprises sending 23 the requested data as scheduled to the user device 6; 10 or to the client node 9 associated with the user device 6; 10 (also refer to figures 2a, 2b and 3, arrows 110, 208 and 310, respectively, and related
• the receiving 21 of a request for data comprises receiving, from a user device 6, access information for accessing the requested data from an identified service provider 8.
• the method 20 comprises retrieving from the identified service provider 8 the requested data using the access information (refer also to figure 4 and related description) .
• the method 20 comprises storing the retrieved data. This is typically the case, as the data is delivered/received to/from a party when deemed suitable.
• the method 20 then comprises deleting the stored data after the provision of data to the user device 6; 10 or to a client node 9 associated with the user device 6; 10 has been completed, for example after the expiry of the received time limit by which the provision of data should be completed.
• the scheduling 22 comprises scheduling the requested data based on downloading and/or uploading conditions comprising one or more of: traffic load in a cell controlled by the base station node 3, radio channel conditions, mobility of the user device 6, 10, load history of a cell controlled by the base station node 3.
• Figure 6 illustrates an exemplifying control node comprising means for implementing embodiments of the disclosure, and in particular to implement the various embodiments of the methods as described.
• a control node 2 of a communication system 1 as
• the processing unit 34 may for example be a central processing unit, microcontroller, digital signal processor (DSP), etc., capable of executing software instructions, e.g. a computer program 32, stored in a computer program product 33 e.g. in the form of a memory.
• DSP digital signal processor
• the processing unit 34 is thus able to retrieve data and/or instructions from such computer program product 33.
• control node 2 comprises a server module, configured to serve the requests from client instances installed in the user device or in core network elements in compliance with Nb-CAP.
• the control node 2 may also comprise a storage medium 31 in which the data retrieved upon request is stored.
• the storage medium 31 may be an internal part of the control node 2 , or be an external storage medium connected to the control node 2.
• the control node 2 further comprises an input/output device 30 connected to the processing unit 34. Although illustrated as a single device, the input/output device 30 could comprise one or more separate input device (s) and one or more separate output device (s).
• the processing unit is configured to: receive, from the user device 6; 10, a request for delivery/retrieval of data to/from the user device 6; 10, the request comprising a time limit by which to provide the requested data, and schedule, based on downloading and/or uploading conditions, the requested data for provision to the user device 6; 10 or to a client node 9 associated with the user device 6; 10 before the expiry of the received time limit.
• processing unit 34 is further configured to send, by means of an output device 30, the requested data as scheduled to the user device 6; 10 or to the client node 9
• the request for data comprises access information for accessing the requested data from an identified service provider 8.
• processing unit 34 is further configured to retrieve the requested data from the identified service provider 8 using the access information.
• the processing unit 34 is configured to store the retrieved data.
• the processing unit 34 is configured to delete the stored data after delivery of the data.
• the request comprises data identifying the user device 10.
• the downloading or uploading conditions comprises one or more of traffic load in a cell controlled by the base station node 3, radio channel conditions, mobility of the user device 6, 10, load history of a cell controlled by the base station node 3.
• a computer program 32 for scheduling delivery of data for such a control node 2 is provided.
• the computer program 32 comprises computer program code, which, when run on a processing unit 34 of the control node 2, causes the processing unit 34 to perform the steps of the methods as described.
• the processing unit 34 causes the processing unit 34 to receive, from the user device 6; 10, a request for delivery/retrieval of data to/from the user device 6; 10, the request comprising a time limit by which to provide the requested data, and schedule, based on downloading and/or uploading conditions, the requested data for provision to the user device 6; 10 or to a client node 9 associated with the user device 6; 10 before the expiry of the received time limit.
• a computer program product 33 for scheduling delivery of data comprises a computer program 32 as described above, and computer readable means on which the computer program 32 is stored.
• the computer program product 33 may for example comprise any combination of read and write memory (RAM) or read only memory (ROM) .
• the computer program product 33 may also comprise persistent storage, which, for example can be any single one or combination of magnetic memory, optical memory, or solid state memory.
• Figure 7 is a flow chart of a method 40 performed in a user device 6, 10 of a communication system 1, such as the communication system described in relation to figure 1.
• the method 40 comprises
• the request may be any resource provisioned.
• the request may be any resource provisioned.
• Figure 8 illustrates an exemplifying user device 6 comprising means for implementing embodiments of the disclosure.
• the specification of a time limit by which the requested data should be provided may be configured in hardware, software or any combination thereof.
• the user device 6 comprises a client side software, terminating the Network-based Content access protocol (Nb-CAP) , mentioned earlier in relation to figure 4.
• the user of the user device 6, may select the Nb-CAP delivery, and inputs the time limit by means of which the data delivery should be completed.
• Nb-CAP Network-based Content access protocol
• a processor unit 50, provided in the user device 6, may be
• the processor unit 50 may be configured to receive the time limit as input by the user of the user device 6, for example by means of a keyboard (not illustrated) and process it suitably.
• a computer program 53 may be provided in the user device 6, comprising computer program code for cooperation with the processor unit 50.
• a computer program product 52 may be provided comprising the computer program 53 and computer readable means on which the computer program 53 is stored.
• the computer program product 52 may for example comprise any combination of read and write memory (RAM) or read only memory (ROM) .
• the computer program product 52 may also comprise persistent storage, which, for example can be any single one or combination of magnetic memory, optical memory, or solid state memory.
• the user device 6 comprises receiver unit 54 and transmitter unit 51 for receiving and transmitting radio signaling and typically also various other components, not illustrated, such as modulator, encoder, decoder, antennas, radio front end circuitry etc .
• Figure 9 illustrates a mobile user device to mobile user device scenario. That is, a first user device 6 may transfer data to a second user device 7 in the postponed manner as has been described in various embodiments. The first user device 6 sends a request for data transmission to the second user device 7 (arrow 401) . The request may comprise details on the data to be transferred,
• the second user 7 then either accepts or rejects the request, and in case of rejection, the communication ends.
• the second user device 7 sends a message (arrow 402) informing the first user device 6 of the acceptance and also informing the first user device 6 about its own control node details (denoted 2 control node in the figure) .
• the second user device 7 then transmits (arrow 403) a message to the 2 nd control node informing about an incoming request for delivery that will be received from the 1 st control node and that the request has been authorized so data should be accepted and delivered, using the Nb-CAP.
• the data transfer is performed in accordance with loops 407 and 412 (compare loops 105 and 109 of figure 2a and related text) . That is, the 1 st control node monitors the download conditions by inquiring the 1 st base station with which the first user device 6 communicates wirelessly, (arrows 405a, 405b) , and schedules a download time
• the 1 st control node Upon occurrence of the scheduled download time, the 1 st control node requests data (arrow 408) from the first user device 6, which then transmits the corresponding chunk of data (arrow 409) to the 1 st control node .
• the l sc control node may store the chunk of data (arrow 410) in a storage medium and forward all data to the 2 nd control node once all data has been received or the 1 st control node may forward the chunk of data immediately to the 2 nd control node (arrow 411) upon reception of each chunk of data (which reception, as before, may be spread over a longer time period) .
• FIG. 10 illustrates a handover scenario when implementing aspects of the present disclosure.
• a wireless network device e.g.
• the user device 6 has an ongoing transaction (box 501) of data transfer with a control node, it typically only needs to communicate with one and the same control node (1 st control node of the figure 10) for the duration of the data transfer, since a single control node typically controls many base stations. That is, even if the user device 6 is moving around much and occasionally performs a handover from one base station to another, it typically does not need to change control node. A change of base station does not affect the ongoing transaction as the control node is the one in control of the transaction.
• a server in the 1 st control node comprising the Nb-CAP
• the 1 st control node simply starts polling the new base station to retrieve the downloading conditions.
• the Nb-CAP relies on control node to base station interworking for monitoring e.g. cell load or other upload/download conditions in order to decide when to transfer chunks of data, so such control node change would benefit from transfer of the protocol transaction from the control node having started the transfer to the new control node controlling the base station with which the user device 6 now is in contact with.
• the user device 6 communicates with a 1 st base station, which is controlled by the 1 st control node, is handed over (box 502) to a 2 nd base station, which is controlled by a 2 nd control node, the following signaling may be performed.
• Such handover is performed in accordance with known procedures .
• the user device 6 When the user device 6 detects that a change of control node is to be performed, its Nb-CAP software informs (arrow 503) the new control node (2 nd control node in the figure 10) that a Nb-CAP transaction is pending. The 2 nd control node is thus made aware of that it may expect a Nb-CAP update message from another control node (i.e. from the 1 st control node) . The user device 6 then sends a message (arrow 504) to the 1 st (old) control node, instructing the 1 st control node to transfer to the 2 nd control node the following: the data received so far, in case of upload from the user device 6, or data still to be transferred in case of download, and also
• transaction details such as details of the endpoint involved in the transaction.
• the 1 st control node then sends (arrow 505) to the 2 nd control node in accordance with the instructions of the user device 6.
• the data transfer to/from the user device 6 is then continued ⁇ box 506) as described earlier, now with the 2 nd control node controlling the data transfer.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Mobile Radio Communication Systems (AREA)

Applications Claiming Priority (1)

Publications (1)

Family

ID=46201779

Family Applications (1)

Country Status (2)

Families Citing this family (4)

Family Cites Families (5)

• 2012
  • 2012-05-03 EP EP12725167.6A patent/EP2845408A1/de not_active Withdrawn
  • 2012-05-03 WO PCT/SE2012/050455 patent/WO2013165284A1/en active Application Filing

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events