WO2023277743A1

WO2023277743A1 - Bootstrapping a wireless communication device

Info

Publication number: WO2023277743A1
Application number: PCT/SE2021/050655
Authority: WO
Inventors: Icaro Leonardo DA SILVA; Szilveszter NÁDAS; Gunnar Mildh; Gergely PONGRÁCZ; Zoltán Richárd TURÁNYI
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2021-06-30
Filing date: 2021-06-30
Publication date: 2023-01-05

Abstract

A wireless communication device (600), a radio access node (700) and methods for bootstrapping the wireless communication device (600). The wireless communication device performing a method (300) of receiving (310), from a radio access node (700), information relating to bootstrapping the wireless communication device, obtaining, (320) using the information relating to bootstrapping, a protocol stack software and performing (340) an action using the obtained protocol stack software, wherein the wireless communication device is capable of programming a protocol stack for radio communication, stored at the wireless communication device. Computer programs and a computer program product are also disclosed.

Description

BOOTSTRAPPING A WIRELESS COMMUNICATION DEVICE

TECHNICAL FIELD

The disclosure herein relates to a communication device and a network node in a wireless communication network, and methods thereof. In particular, the embodiments relate to bootstrapping a communication device. Computer programs and a computer program product are also disclosed.

BACKGROUND

In 3^rd Generation Partnership Project (3GPP) systems, such as 5^th Generation (5G) New Radio (NR) and Long-Term Evolution (LTE) a set of protocols form a protocol stack for communication between a User Equipment (UE) and a radio access network (RAN). The protocol stack can be divided into Control Plane (for signaling), see Figure 1, and User Plane (for data) see Figure 2.

For the Control Plane, a package data convergence protocol (PDCP), radio link control (RLC), medium access control (MAC) and Radio Resource Control (RRC) terminate in a gNodeB (gNB) on the network side. A Non-access stratum (NAS) control protocol terminates in the Access and Mobility Management Function (AMF) on the network side, see Figure 1. The User Plane may comprise a Service Data Adaptation Protocol (SDAP), PDCP, RLC and MAC which typically terminate in a gNB on the network side, see figure 2.

The functions executed by these protocols are specified in 3GPP specifications. For example, a main control plane protocol, RRC, is specified in 3GPP TS 38.331 V 16.1.0, which discloses the following protocol functions for implementation in the UE side: Broadcast of System Information related to Access Stratum (AS) and NAS;

Paging initiated by 5G Core (5GC) or Next Generation Radio Access Network (NG- RAN)

Establishment, maintenance and release of an RRC connection between the UE and NG-RAN including: o Addition, modification and release of carrier aggregation; o Addition, modification and release of Dual Connectivity in NR or between Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) and NR.

Security functions including key management;

Establishment, configuration, maintenance and release of Signaling Radio Bearers (SRBs) and Data Radio Bearers (DBRs); Mobility functions including: o Handover and context transfer; o UE cell selection and reselection and control of cell selection and reselection o Inter- Radio Access Technology (RAT) mobility Quality of Service (QoS) management functions;

UE measurement reporting and control of the reporting;

Detection of and recovery from radio link failure;

NAS Message transfer to/from NAS from/to UE.

Sidelink (SI) specific service and functions of the RRC sublayer over the Uu interface include:

Configuration of SL resource allocation via system information or dedicated signaling;

Reporting of UE SL information;

Measurement configuration and reporting related to SL Reporting of UE assistance information for SL traffic pattern(s).

Once functions are specified, UE manufacturers can implement them according to these specifications, and a network manufacturer can implement the counter-part of these functions taking, into account what has been specified.

However, a UE behavior that a network manufacturer can use when programming a software is limited to what has been specified. For example, a network vendor can design a handover algorithm based on A1-A6 events see TS 38.331 V 16.1.0 clauses 5.5.4.1-5.5.4.7, to take a handover decision, for example in response to a certain configuration and a process measurement report. Further, the introduction of a new event, a new trigger, and/or a new report associated with a handover decision would require standardization.

Recent initiatives, such as separation between Control Plane and User Plane functions, and the opening of Application programing Interfaces API(s) that could be used by a third party so that control functions could be programmed, may open up for new ideas in the 5G Core Network. In addition, virtualization and cloud technologies have been used to program APIs on the network side.

In the RAN domain, initiatives in the area of RAN programmability have also started to emerge. However, they have been limited to initiatives to open API(s) on the network side, so that a third part vendor could use these opened API(s) to program algorithms.

The benefits are limited to functions and/or features a terminal would support in a given version of the 3GPP specifications. In other words, while a programmer benefiting from opened API’s could design a new scheduling algorithm, the programmers cannot substantially influence the type of information a terminal reports, or some specific behavior of the UE upon receiving a given command: the type of information or specific behavior would have to be introduced via standardization.

Even if the UE behavior is updated in the standards, network vendors must support legacy behavior for a long period of time. This makes standardization cautious, and also network design more and more complex as the given generation of mobile network evolves.

SUMMARY

An object of embodiments herein is to enable a wireless communication device to connect to a radio access node without having pre-loaded radio protocol stack software versions compatible with the wireless network’s communications procedures.

According to a first aspect a method is provided for a wireless communication device for bootstrapping the wireless communication device. The method comprising, receiving, from a radio access node, information relating to bootstrapping the wireless communication device, obtaining using the information relating to bootstrapping, a protocol stack software, and performing an action using the obtained protocol stack software, wherein the wireless communication device is capable of programming a protocol stack, for radio communication, stored in the wireless communication device.

Hereby is achieved the wireless communication device has been enabled to bootstrap itself with a protocol stack software compatible with the network. As such, there is achieved the ability to add new devices to a wireless network with minimum preconfiguration or pre-loading of the software or firmware on the communication devices.

According to a second aspect a wireless communication device is provided, the wireless communication device comprising a transceiver, a processor, and a memory. The memory storing instruction that when executed by the processes, causes the wireless communication device to receive from a radio access node, information relating to bootstrapping the wireless communication device, to obtain a protocol stack software, and to perform an action using the obtained protocol stack software, wherein the wireless communication device is enabled to program a protocol stack, for radio communication, stored in the wireless communication device. A third aspect is a method performed by a radio access node for bootstrapping a wireless communication device. The method comprising, transmitting, to the wireless communication device, information relating to bootstrapping the wireless communication device, wherein the information relating to bootstrapping comprises information enabling the communication device to obtain a protocol stack software.

In a fourth aspect, a radio access node is provide comprising a transceiver, a processor, and a memory. The memory storing instructions that when executed by the processor cause the radio access node to transmit, to the wireless communication device, information relating to bootstrapping the wireless communication device, wherein the information relating to bootstrapping comprises information enabling the wireless communication device to obtain a protocol stack software.

In a fifth aspect a computer program comprising program code is provided. The program code to be executed by at least one processor of a wireless communication device whereby the execution of the program code causes the wireless communication device to perform operations according the first aspect and embodiments thereof.

In a sixth aspect, a computer program comprising program code is provided. The program code to be executed by at least one processor of a radio access node whereby the execution of the program code causes the radio access node to perform operations according to the third aspect and embodiments thereof.

A seventh aspect is a computer program product comprising a computer program. The computer program as in the fifth or sixth aspect. Further provided is a computer readable means on which the computer program is stored.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure is now described, by way of example, with reference to the accompanying drawings, in which:

Figure 1 illustrates protocol stacks comprised within the control plane;

Figure 2 illustrates protocol stacks comprised within the user plane;

Figures 3, 3A & 4 are flow charts of methods of bootstrapping a wireless communication device; Figure 5 is a signal diagram of signaling between a wireless communication device and a radio access node for bootstrapping the wireless communication device;

Figure 6 is a block diagram of a wireless communication device according to an embodiment;

Figure 7 is a block diagram of a radio access node according to an embodiment.

DETAILED DESCRIPTION

The disclosure will now be described more in detail hereinafter with reference to the accompanying drawings, in which certain embodiments of the disclosure are shown. This disclosure may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided as examples of embodiments within the claimed scope.

A problem that exists is how to achieve a synchronization of a network and a wireless communication device (WD), for example wherein a new (WD) first connects to a network, or if the WD has not connected to the network for a while and the protocol stack software used by the network has changed significantly. For example, consider a newly bought WD with a Universal Subscriber identify Module (USIM) card comprised within for example a universal integrated circuit card, UICC that, when it is turned on, tries to register to a network, wherein the WD has stored its protocol stack and can simply run it upon turning on, and, as the protocol of the air interface is completely standardized both network and WD know what is expected from each side.

However, if a programmable protocol stack for radio communication is introduced, the WD may not be aware of how to access (and/or after accessing, how to register to, initiate security with, etc.) the network. Even if the WD has a pre-programmed access method, it is not certain that the network supports that method, especially considering that with a programmable framework, different network vendors or network operators may design different access methods. Another problem related to WD programmability is related to failure cases, wherein the WD is not able to run a specific software version that is being used by the network at a given moment in time.

Figure 3, Figure 3A and Figure 4 are flow charts illustrating embodiments of methods for bootstrapping a WD. Figure 3 illustrates a method 300 performed by a WD for bootstrapping the WD. The bootstrapping method comprises receiving 310, from a radio access node, information relating to bootstrapping the WD. The information relating to bootstrapping enabling the WD perform a step of obtaining 320 a protocol stack software (e.g. during initial registration, for example in a NAS message; from an over the top protocol or downloading/retrieving the information from an address location e.g. a Uniform Resource Locator). Further, the method comprises performing 340 an action using the obtained protocol stack software. For example, in some embodiments an action performed by the WD is to re-start the WD’s registration operations with the obtained protocol stack activated / loaded. In another embodiment, the action performed by the WD is to activate and/or run the obtained software without re-starting the registration operations. The WD is capable of programming a protocol stack, used for radio communication, stored at the WD.

As used herein, the term “bootstrapping” refers to a procedure performed when a device, which does not have a protocol stack compatible for use in any network available to the device, is switched on. The bootstrapping ends when a protocol stack software, which is required in a network available to the device, has been downloaded to the device. If there is no need to download a new protocol stack or update an existing protocol stack upon the device being switched on, bootstrapping will typically not be performed. As used herein the bootstrapping procedure for the WD may comprise steps of activating or using the obtained protocol stack software.

In an optional step of Figure 3, selecting 315 a network and/ora protocol stack, the WD may select one or more networks, with which the WD may be able to connect to. As such, if there are two or more networks, the WD device may want to select a network, with which it wants to communicate. Further, one or more compatible protocol stack software may be available for communication, to either one or more networks. Thus, selecting a protocol stack software that is compatible with the selected network may be performed by the WD. In another embodiment the WD is presented with a network and a selection of two or more protocol stack software, compatible with the network, that are available from the radio access node. Thus, the selecting of a protocol stack software may be performed by the WD. Further, the selecting a network may be based on subscription date (e.g. USIM data), or a choice by a user of the WD.

Further, in an optional connecting 345 step the WD may connect to the radio access node utilizing the connection procedures of the obtained protocol stack software. In some embodiments, the WD switches from the radio access node to another access node, before connecting to the other radio access node that is compatible with the obtained protocol stack software.

In figure 3A, an embodiment of the method 300 is illustrated. At a receiving 310A step the information relating to bootstrapping the WD may for example be received on a bootstrapping broadcast channel (BBC). In an embodiment the information relating to bootstrapping further comprises receiving, on the BBC, information relating to selecting a wireless communication network. The BBC may be a physical channel or a logical channel for broadcasting information relating to bootstrapping. The BBC may be a dedicated channel used for the purpose of bootstrapping, a broadcast channel reserved for bootstrapping or the BBC may be information elements transmitted on a broadcast channel, for example a broadcast channel used for transmitting system information, such as a Broadcast Control Chanel, or a Physical Broadcast Channel. The content transmitted on the BBC may include reference signals. The information may be encoded using a modulation and/or a coding scheme. Further, the information relating to bootstrapping may comprise information enabling the WD to perform a transition from RRCJDLE to RRC_CONNECTED (e.g. TS 38.331 V 16.1.0, 4.2 Architecture). Even further, information received on the BBC may assist the WD in selecting a network or Mobile Network Operator (MNO) for example by the radio access node broadcasting all the information needed for network related selections that the WD would be required to perform the selection, e.g. MNOs, protocol stack versions etc.

The information relating to selecting a wireless communication network transmitted on the BBC may, for example, comprise information about network slices, and/or Public Land Mobile Networks (PLMNs), or other information that may facilitate the selection of a wireless communication network or MNO.

In an embodiment, the information relating to bootstrapping the WD is, for example, broadcasted on the BBC per cell within a cellular network. Thus, the receiving 310 information relating to bootstrapping may be performed during a cell selection or a cell search procedure. Furthermore, the information relating to bootstrapping the WD may comprise information about which WD protocol stacks could be utilized to access the radio access node and/or a wireless communication network, and/or the information relating to bootstrapping the WD may be an indication about which protocol stacks software may be provided over a bootstrapping data channel (BDCFI).

In an embodiment, illustrated in figure 3A, the obtaining 320A the protocol stack software is received on the BDCH. In some embodiments, the protocol stack software is obtained before initial registration. The BDCH may be the same physical and/or logical channel as the BBC. Alternatively, it could be a separate physical or logical channel compared to the BBC, i.e. the BBC and the BCH are different physical or logical channels. In the case that the BDCH is a separate channel, the information relating to bootstrapping that is transmitted on the BBC may provide information on the presence and resource location of the BDCH, alternatively, information on the presence and resource location of the BDCH could be provided in a dedicated message from the radio access node. The BDCH may be limited by the network to only have functions needed for a bootstrapping process available. In some further embodiments, the functionality of the BDCH is expanded to also include supporting functions such as Internet Protocol assignment and/or Domain Name System, in addition to the required functions for bootstrapping the WD. The BDCH may be a dedicated channel or it may be a broadcast channel.

The BBC and the BDCH may have different optimization goals than other air interface channels. Thus, the BBC and BDCH may be optimized for long term compatibility of the two bootstrapping channels with, for example, legacy procedures, legacy equipment, and/or legacy protocol stacks. Optimization of the BBC and BDCH may be a simplicity in communication procedures, and minimal resource demands when the channels are not being utilized to provide a stack to a WD. Further, the BBC and/or BDCH may use legacy Radio Access Technology, data channels and public URL.

The BBC or BCDH may be simple channels, e.g. no handover, a simple radio physical channel, minimal protocols, no authentication from WD. The BBC and BCDH may build on Internet protocols present in the WD (e.g. IPv6 and/or http/2 ).

Further, if the WD obtaining a new protocol stack software experiences a link failure to the network during the bootstrapping method, the WD may re-select another cell and re initiate the bootstrapping method. The re-initiation of the bootstrapping method may be performed from where it was in the method when the failure occurred, (e.g. only requesting missing parts of the stack). Alternatively, the WD may restart the procedure and discard any previously downloaded stack.

Bootstrapping is typically a rare event, and a bootstrapping procedure may be part of a programmable network, which is intended to be supported for several years (e.g. a range of years such as 5-10 years of support).

In an embodiment, a network restricts the maximum resource usage of the bootstrapping channels, for example by limiting the rate at which information is transmitted over the bootstrapping channel. Thus, the risk that these channels are used by malicious WD as a form of denial of service is minimized. For example, the network restricting the maximum resource usage at congestion to for example, 1 %. As such, other traffic will not suffer performance losses.

In an embodiment, the performing 340 an action comprises performing an action the obtained protocol stack software. As used herein performing an action on the obtained protocol stack software means the WD applies the protocol stack software on the WD, for example storing the protocol stack in a data storage system. Furthermore, the WD may activate the protocol stack software on the WD, the activating may comprise the WD updating the protocol stack software currently running on the WD. Further, applying the protocol stack software may further comprise any one or more of replacing the current, activated, protocol stack software with the obtained protocol stack software, activating the obtained protocol stack, concurrently with the current, activated protocol stack, or activating the obtained protocol stack for example if there is no currently activated protocol stack. In some embodiments, applying the protocol stack software comprises loading the obtained protocol stack software into a specific memory.

In further embodiments the WD initiates a re-start, (i.e., a re-boot), of the WD to activate the obtained protocol stack.

After activating the obtained protocol stack software, the WD may use the obtained protocol stack software’s procedures, and thus the WD has been enabled to utilize the obtained protocol stack software’s connection procedure. The connection procedure may be a native connection procedure of the protocol stack software, wherein a native procedure is a procedure designed to run specifically for that protocol stack.

In another embodiment of the disclosure, illustrated in Figure 3A, the method comprises connecting 345A to the radio access node utilizing the obtain protocol stack software’s connection procedures. Herein, connecting to the radio access node could include performing an initial registration, authentication procedures.

As used herein, receiving 310, obtaining 320 and transmitting 410, 420 may comprise receiving/transmitting the information as an information element in a RRC or a NAS signaling. For example, receiving the information relating to bootstrapping in an RRC message during a transition from RRCJDLE to RRC_Connected. A further example of receiving 310 the information relating to bootstrapping using RRC or NAS signaling comprises transferring data as an Abstract Syntax notation One (ASN.1) formatted message. Other suitable formats include JavaScript Object Notation (JSON), YAML Ain’t Markup Language (YAML), or Protobuf. In a further embodiment the WD is pre-loaded with a light-weight version of the RRC and NAS protocol stack (in addition to e.g. the MAC and RLC). Thus, the WD is enabled to perform RRC and NAS signaling. In one embodiment, during a NAS procedure, the WD receives 310 in a NAS message an indication enabling the WD to download a protocol stack software, for example from a BDCH or an address location.

The obtaining 320 of a protocol stack software may for example be performed using the File Transfer Protocol (FTP), Secure Shell (SSH) FTP (SFTP) or Hypertext Transfer Protocol (HTTP), or NAS and RRC signaling. Further, obtaining the protocol stack software using FTP, SFTP or HTTP the protocol stack software could be transferred as a file. For example, a HTTP message may be a HTTP GET or HTTP POST message. Example of (S)FTP messages are (S)FTP GET or MGET messages, and (S)FTP PUT or MPUT messages. The file format could, in one instance, be an Extensible markup Language (XML) format. In another example, the file could be a serialized data format, for example JSON, (YAML), or Protobuf. In some embodiments, the WD obtains the protocol stack software by obtaining an indication such as a pointer or an index to a protocol stack software. In other words, the pointer or index may point to an address location where the protocol stack software is stored, which a receiver (i.e. the WD) can obtain. In another embodiment, such pointer may be an URL to a server from which the receiver (i.e. the WD) can retrieve the protocol stack software, for example using FTP, SFTP, or HTTP.

In an embodiment, signaling herein is encrypted and/or integrity protected. As used herein, encryption and/or integrity protection, for signaling, for example messages, such as. NAS, RRC , FTP, SFTP, or HTTP messages, may be signed with a secure checksum. The secure checksum would enable the network to verify the capability information, thereby ensuring that the capability information has not been modified or tampered with. The secure checksum may be a SHA-256, a MD5 or another secure checksum. In some embodiments, the checksum is calculated and verified using a public key. In further embodiments, the checksum may be calculated and verified using a private key. In even further embodiments the checksum may be calculated and verified using a shared secret key. Furthermore, the signaling may also be encrypted using a key, e.g. the public key, the private key, and/or the shared secret key. Further, in some embodiments the protocol stack software may be signed by an operator or other entity responsible for the protocol stack software to verify the protocol stack software. In an embodiment where the information is transmitted using the BBC and/or the BDCH channels, the BBC and/or BDCH are encrypted. This may be used by the WD to verify that the WD is communicating with the correct network (though the radio access node). The encryption and/or integrity may be used to prevent a man-in-the-middle attack, for example where the communication on a channel, e.g. a broadcast channel, the BBC, or the BDCH channels are modified by an attacker. Furthermore, a signing of the protocol stack by a network operator or other entity responsible for the obtained protocols stack may be used to validate the authenticity of the obtained protocol stack, i.e. the protocol stack is from a legit source. Furthermore, the network operator and other entity may be certified by the WD manufacture.

Figure 4 illustrates a method 400 performed by a radio access node bootstrapping a wireless communication device (WD). The method 400 comprises transmitting 410, to the WD, information relating to bootstrapping the WD wherein the information comprises information enabling the WD to obtain protocol stack software

In an optional step illustrated in Figure 4 the method may further comprise the radio access node transmitting 420 a protocol stack software to the WD. Thus, the WD may obtain the protocol stack software from the radio access node.

In another optional step illustrated in Figure 4, the method may further comprise the radio access node connecting 425 to the WD. For example, the radio access node may be connected to the WD by responding to the communication procedures initiated by the WD.

The transmitting 410 information relating to bootstrapping may comprise transmitting the information relating to bootstrapping as at least one information element in RRC or NAS signaling. In an embodiment, the transmitting 410 information relating to bootstrapping is performed using a broadcast message, e.g. on a bootstrapping broadcast channel, such as the BBC, or another broadcast channel, for example a broadcast channel used for transmitting system information, such as a Broadcast Control Chanel, or a Physical Broadcast Channel. The transmitting of information relating to bootstrapping at 410 comprises information enabling the WD to obtain a protocol stack software. Thus, the information enabling the WD to obtain a protocol stack software may comprise a protocol stack software, a protocol stack software identifier, and/or an address location of a protocol stack software. Furthermore, the transmitting of a protocol stack software at 420 may be performed, for example, using FTP, STFP or HTTP messages. For example, a HTTP message may be a HTTP GET or HTTP POST message. Examples of (S)FTP messages are (S)FTP GET or MGET messages, and (S)FTP PUT or MPUT messages. Furthermore, the transmitting of a protocol stack software at 420 may be performed using the BDCH (which in some embodiments is the same channel as the BBC).

In an embodiment of the disclosure, the transmitting of information relating to bootstrapping at 410 comprises transmitting information indicating a server, for example a URL pointing to the server, to the WD. The server may comprise storage means on which a protocol stack software is stored. The transmitting 410 information relating to bootstrapping may be performed by the radio access node as a response to a WD cell selection or cell search procedure. Thus, the radio access node enables a WD with insufficient protocol stack software pre-loaded for a connection procedure to obtain a radio access node and/or network compatible protocol stack software. In another embodiment the transmitting 420 information relating to bootstrapping comprises transmitting information relating to a selection of a wireless communication network.

Figure 5 illustrates a signaling diagram between two entities according to embodiments of the disclosure. For illustrative purposes the signaling diagram shows more specifically, signaling between a wireless communication device and a radio access node. Another example that may use the signaling is a first communication device and a second communication device connected to a radio access node, wherein the first communication device receives bootstrapping information from the second communication device, to connect to the radio access node. A signal 510 from the radio access node to the wireless communication device, comprises information relating to bootstrapping (i.e. bootstrapping information). For example, the signal may an RRC or NAS signal. The information enables the WD to obtain a protocol tack software. For example, the information may be an indication enabling the WD to download a new protocol stack software, such as an address location comprising a storage date system, from which the new protocol stack software can be downloaded from. Further, the information may be a network slice identifier, a PLMN identifier, an indication of a BDCH, or other information elements, e.g. identification of reference signals, for bootstrapping a wireless communication device with a protocol stack software. Illustrated in Figure 5 is a protocol stack software message 520 sent from the radio access node to the WD. In one embodiment, when the communication device receives the protocol stack software directly from the radio access node, the protocol stack software is comprised within the bootstrapping information signaling. Thus, in an embodiment the signal 520 is comprised within signal 510. Alternatively, the protocol stack software may be transmitted in another signal 520. Thus, the protocols stack software is not comprised within the bootstrapping information signaling but transmitted in another signal 520 from the radio access node to the WD, for example a signal on the BDCH, or in another message transmitted on the BBC after the bootstrapping information message has been sent from the radio access node to the WD.

The signal 520 may be transmitted as a response to a request signal 515 from the WD to the radio access node. The protocol stack software may be provided from the radio access node to the WD over the BDCH, the BBC, or through other suitable channels for the purpose of transmitting protocol stack softwares..

In an optional signaling message, 545 the WD indicates to the radio access node the WD’s selected network and/or protocol stack. The optional signaling message 545 may send the indication, using RRC or NAS signaling, during RRC or NAS procedures, for example in an RRC Setup Complete message, which network and/or protocol stack the WD would prefer. In other words, a request 515 for a protocol stack or a network. Furthermore, the WD may indicate in a similar message to the radio access node (not shown) that the WD is a programmable WD and inform the radio access node that it can provide a protocol stack software to the WD.

In another optional signal message, the WD sends a connection initiation message to the radio access node. The WD and radio access node can then perform connection procedures utilizing the protocol stack software obtained by the WD.

Figure 6 illustrates a block diagram of an embodiment of a WD 600. As shown in Figure 6, WD 600 comprises processing circuity (PC) 610 which includes one or more processors 615, e.g. one or more general purpose microprocessor, one or more data processing circuits, such as an application specific integrated circuit, and/or one or more field-programmable gate arrays. The processing circuitry may be located in a single, housing or data center or the processing circuitry may be geographically distributed. The WD 600 in some embodiments further includes a network interface 620, comprising a transmitter 623 and/or a receiver 627 for enabling the WD 600 to transmit data to and receive data from nodes connected to a network with which the WD is in communication. Moreover, the transmitter 623 and receiver 627 may be coupled to one or more antennas (not shown). The transmitter 623 and receiver 627 may share circuit components, software or firmware, (for example in a joint transceiver implementation) or alternatively be implemented separately. The WD further comprises a data storage system 630, which may include one or more non-volatile storage devices and/or one or more volatile storage devices. The data storage system 630 of Figure 6 comprises a computer program product 640 in the form of a data storage for storing information, which may include one or more computer readable storage medium in the form of non-volatile memory, and/or one or more volatile memory such as one or more random-access memory (a non-volatile memory can retain stored information even after power is removed from the non-volatile memory). The computer program product stores a computer program (CP) 643, which comprises computer instructions or code 647. A computer readable storage medium can be a non-transitory computer readable medium such as, a magnetic medium where a hard disk is an example thereof, optical media, such as a DVD, and a flash memory. The computer instructions of the computer program when executed by the processing circuitry cause the computer to perform some or all of the functions and operations described herein.

Figure 7 illustrates a block diagram of an embodiment of a radio access node 700. As shown in Figure. 7 radio access node 700 may comprises processing circuity (PC) 710 which includes one or more processors 715, e.g. one or more, general purpose microprocessor, one or more data processing circuits, such as an application specific integrated circuit, and/or one or more field-programmable gate arrays. The processing circuitry may be located in a single, housing or data center or the processing circuitry may be geographically distributed. The radio access node 700 in some embodiments further includes a network interface 720, comprising a transmitter 723 and a receiver 727 for enabling the radio access node to transmit data to and receive data from other nodes or WDs connected to a network with which the radio access node communicates. Moreover, the transmitter 723 and receiver 727 may be coupled to one or more antennas (not shown). The transmitter 723 and receiver may share circuit components, software or firmware, (for example in a joint transceiver implementation) or alternatively be implemented separately. The radio access node 700 further comprises a data storage system 730 which may include one or more non-volatile storage devices and/or one or more volatile storage devices. The data storage system 730 of Figure 7 further comprises a computer program product 740 in the form of a data storage for storing information, which may include one or more computer readable storage medium in the form of non-volatile memories, and/or one or more volatile memory such as one or more random access memory. The computer program product stores a computer program (CP) 743, which comprises computer instructions or code 747. A computer readable storage medium can be a non-transitory computer readable medium, such as, a magnetic medium of which a hard disk is an example, or an optical medium, such as a DVD, and a flash memory. The computer instructions of the computer program are configured such that when executed by computer the computer instructions cause the computer to perform some or all the functions and operations described herein.

The various embodiments described herein may be implemented by means of a recording medium readable by a computer or its similar device by employing for example, software, hardware or combinations thereof.

A software implementation of the embodiments described may be implemented as procedures and functions that may be implemented in separate modules and/or computer program parts, each of which is written to cause a computer system to perform one or more of the functions and operations described herein. Software code may be implemented using a software application written in any suitable programming language.

As used herein a radio access node may be a physical network device, such as a radio access network device, a radio core network device, a distributed network system node, a wi-fi router. Further, a distributed networks node may be a computing platform (e.g a cloud computing platform) node such as a server, an over-the-top server, or a virtual network node which can be implemented in a cloud.

Further, the radio access node may be a radio base station in the form of a standardized base station such as nodeB or evolved NodeB (eNB), for Long Term Evolution (LTE) or gNodeB for New Radio (NR).

It will be appreciated that the term radio access node may further refer to a base transceiver station, an access point, a network control node such as a network controller, a radio network controller, a base station controller, and the like or some combination thereof. The radio access node may, in an embodiment, be a modem, hub, bridge, switch or other data communication equipment, or a data terminal equipment such as a host computer.

As used herein the term wireless communication device, which may alternatively be known as a “wireless terminal” or a “User Equipment” (UE), may refer to a mobile phone, a cellular phone, a Personal Digital Assistant (PDA), equipped with radio communications capabilities, a smart phone, an iPAD, a USB dongle e.g. with a radio modem, a laptop or a personal computer, PC, equipped with an internal or external mobile broadband modem, a tablet PC with radio communication capabilities, a laptop embedded equipment, a laptop mounted equipment, a device-to-device UE, a machine type UE, a UE capable of machine-to-machine communications, customer premises equipment, a portable electronic radio communication device, a sensor device equipped with radio communication capabilities, a telematics unit within a vehicle, a vehicle- mounted or vehicle embedded wireless device, a VR headset, a display, a loudspeaker or other media delivery device, etc. In particular, the term “wireless communication device” should be interpreted as a non-limiting term comprising any type of wireless device communicating with a radio network node in a cellular or a mobile communication system. As such, a wireless communication device may be any of a wide variety of communication devices arranged, configured, and/or operable to communicate wirelessly with the network node. In the present context, the term virtualizing means creating virtual versions of apparatuses or devices e.g. virtualizing hardware platforms, storage devices and networking resources. Virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components.

As used herein, the term “protocol stack” refers to one or more protocol and/or protocol function at an entity in a mobile network, such a WD and/or a network node (such as a gNodeB, eNodeB, CU-eNodeB, DU-eNodeB, AMF, SMF, MME, etc.). For example, the control plane protocol stack in comprises NAS, RRC, PDCP, RLC, MAC, PHY, the user plane protocol stack comprises SDAP, PDCP, RLC MAC, PHY. As used herein, the term protocol stack may refer to any one or a subset of the compositions e.g. only RRC, or RRC and MAC, etc.

Instead of a whole network stack, a protocol stack may be network specific detailed configuration data. The network specific detailed configuration data can be needed for actual communication (e.g. channel settings, random access procedure parameters)

The term “protocol stack software” refers to a data file comprising a software that, when executed on processing circuity enables the entity on which the software is executed to run protocol functions.

While various embodiments of the present disclosure are described herein, it should be understood that they have been presented by way of example only, and not limitation.

Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments. Moreover, any combination of the above- described elements in all possible variations thereof is comprised by the disclosure unless otherwise indicated herein or otherwise clearly contradicted by context. Additionally, while the processes described above and illustrated in the drawings are shown as a sequence of steps this was done for the sake of illustration only, unless otherwise stated. It is contemplated that some steps may be added, some steps omitted, the order of the steps may be re-arranged, and some steps may be performed in parallel.

Claims

1. A method (300) performed by a wireless communication device, WD, for a bootstrapping the WD, comprising: receiving (310), from a radio access node, information relating to bootstrapping the WD; obtaining (320), using the information relating to bootstrapping, a protocol stack software; and performing (340) an action using the obtained protocol stack software; wherein the WD is capable of programming a protocol stack for radio communication, stored in the WD.

2. The method according to claim 1, comprising; the receiving (310) information relating to bootstrapping comprises receiving (310A), on a bootstrapping broadcast channel, the information relating to bootstrapping; and the bootstrapping broadcast channel is a channel reserved for bootstrapping WDs.

3. The method according to claim 2 comprising searching (303A), using the bootstrapping broadcast channel prior to obtaining information relating to bootstrapping, for the radio access node.

4. The method according to any one of claims 1 - 3, comprising: selecting (315) a wireless communication network, wherein the information relating to bootstrapping comprises information relating to selecting a wireless communication network.

5. The method according to any one of claims 1 - 4, wherein the obtaining (320) a protocol stack software comprises obtaining (320A) the protocol stack software on a bootstrapping data channel.

6. The method according to any one of claims 1 - 5, wherein the receiving (310, 310A) information relating to bootstrapping is performed during a cell selection or cell search procedure.

7. The method according to any one of claims 1 - 6, wherein performing (340) at least one action comprises activating (340) the obtained protocol stack software.

8. The method according to any one of claims 1 - 7 comprises connecting (345) to the radio access node using the connection procedures of the obtained protocol stack software.

9. A wireless communication device, WD, (600) comprising: a processor (615) a transceiver (620); and a memory (630) storing instructions that, when executed by the processor, cause the WD to: receive (310), from a radio access node, information relating to bootstrapping the WD; obtain (320) a protocol stack software; and perform (340) an action using the obtained protocol stack software; wherein the WD is enabled to program a protocol stack for radio communication stored in the WD.

10. The WD according to claim 9, wherein to receive (310), information relating to bootstrapping the WD comprises to receive (310A) on a bootstrapping broadcast channel, the information relating to bootstrapping; and the bootstrapping broadcast channel is a channel reserved for bootstrapping WDs.

11. The WD according to claim 10, further configured to search (303A), using the bootstrapping broadcast channel prior to obtaining information relating to bootstrapping, for the radio access node.

12. The WD according to any one of claims 9 - 11 further configured to select (315) a wireless communication network, wherein the information relating to bootstrapping comprises information relating to selecting a wireless communication network.

13. The WD according to any one of claims 9-12, wherein to obtain (320) a protocol stack software comprises to obtain (320A) the protocol stack software on a bootstrapping data channel.

14. The WD according to any one of claims 9-13 configured to receive (310, 310A) information relating to bootstrapping during a cell selection or cell search procedure.

15. The WD according to any one of claims 9-14 configured to connect (345) to the radio access node using the connection procedures of the obtained protocol stack software.

16. A method (400) performed by a radio access node for bootstrapping a wireless communication device, WD; the method comprising: transmitting (410), to the WD, information relating to bootstrapping the WD, wherein the information comprises information enabling WD to obtain a protocol stack software.

17. The method of claim 16 wherein the information enabling the obtaining of a protocol stack software comprises: one or more of at least one protocol stack software, at least one protocol stack software identifier, at least one address location of a protocol stack software.

18. The method according to claim 17 comprises: transmitting (420) a protocol stack software on a bootstrapping data channel.

19. The method according to any one of claims 16 - 18, wherein the information relating to bootstrapping the WD comprises information relating to the selection of a wireless communication network.

20. The method according to any one of claims 16 - 19, wherein the transmitting of information relating to bootstrapping is transmitted on a bootstrapping broadcast channel, the bootstrapping broadcast channel is a channel reserved for bootstrapping WDs.

21. The method according to any one of claims 16 - 20, wherein the transmitting of information relating to bootstrapping the WD is performed during a cell selection or cell search procedure.

22. The method according to any one of claims 16 - 21 comprising, upon the transmitting of information relating to bootstrapping the WD, connecting (425) to the WD.

23. A radio access node (700) for bootstrapping a wireless communication device, WD; the radio access node (700) comprising: a processor (715); a transceiver (720); and a memory (730) storing instructions that, when executed by the processor, cause the radio access node to: transmit (410), to the WD, information relating to bootstrapping the WD, wherein the information comprises information enabling the communication device to obtain a protocol stack software.

24. The radio access node (700) of claim 23, wherein the information enabling the WD to obtain a protocol stack comprises: one or more of at least one protocol stack software, at least one protocol stack software identifier, and/or at least one address location of a protocol stack software.

25. The radio access node (700) of claim 24 configure to transmit (420) a protocol stack software on a bootstrapping data channel.

26. The radio access node (700) of any one of claims 23 -25, wherein the information relating to bootstrapping the WD comprises information relating to a selection of a wireless communication network.

27. The radio access node (700) of any one of claims 23-26, wherein the information relating to bootstrapping is transmitted on a bootstrapping broadcast channel, the bootstrapping broadcast channel is a channel reserved for bootstrapping WDs.

28. The radio access node (700) of any one of claims 23-27 configured to transmit (410) information relating to bootstrapping the WD during a cell selection or cell search procedure.

29. The radio access node (700) of any one of claims 23-28 configure to connect (425) to the WD, upon transmitting information relating to bootstrapping the WD.

30. A computer program (643) comprising program code (647) to be executed by at least one processor (615) of a wireless communication device (600), whereby the execution of the program code (647) causes the wireless communication device (600) to perform operations according to any one of claims 1 to 8

31. A computer program (743) comprising program code (747) to be executed by at least one processor (715) of a radio access node (700) whereby the execution of the program code (743) causes the radio access node to perform operations according to any one of claims 16 to 22.

32. A computer program product (640, 740) comprising a computer program (643, 743) as claimed in claim 30 or 31 and a computer readable means on which the computer program (643, 743) is stored.