Systems and methods for network configuration transfer

Abstract

A method (1300) by a first node (110) for network configuration transfer includes transmitting (1302), to a second node (108), information comprising an identifier of a type of network configuration information that the first node and / or a node in communication with the first node is capable of receiving. The first node receives (1304), from the second node, the network configuration information of the type associated with the identifier in the information.

Description

[0001] SYSTEMS AND METHODS FOR NETWORK CONFIGURATION TRANSFER

[0002] TECHNICAL FIELD

[0003] The present disclosure relates, in general, to wireless communications and, more particularly, systems and methods for network configuration transfer.

[0004] BACKGROUND

[0005] In the case of Time Sensitive Network (TSN) and Deterministic Networking (DetNet) networks, as defined in 3GPP TS 23.501, the 5thGeneration System (5GS) is acting as a logical Ethernet Bridge or Internet Protocol (IP) Router, which is being configured by an external controller such as, for example, a Central Network Controller (CNC) in the case of TSN and a DetNet controller in the case of DetNet. FIGURE 1 illustrates an example TSN and / or DetNet.

[0006] As illustrated in FIGURE 1, a controller provides configuration to the 5GS node, where the interface from the controller is terminated in the TSN Application Function (AF) or Time Sensitive Communication Time Synchronization Function (TSCTSF). More specifically, the controller is terminated in the TSN AF for Ethernet when the controller is a CNC, and the controller is terminated in the TSCTSF for IP when the controller is a DetNet controller. Internet Engineering Task Force (IETF) protocols are used for the configuration such as Netconf or Restconf. The TSCTSF / TSN AF terminates the Netconf or Restconf interface and needs to parse the configuration and determine which parameters are relevant for the 5GS. The TSCTSF / TSN AF uses the 3rdGeneration Partnership Project (3GPP) defined Port Management Information Container (PMIC) or User-plane Node Management Information Container (UMIC) (which may also be known as a Bridge Management Information Container (BMIC)) as containers to deliver the relevant information elements (IES) to the Device-Side TSN Translator (DS-TT) in the terminal or Network-side TSN Translator (NW-TT) at the User Plane Function (UPF). The response to the configuration is signaled in the reverse direction. The TSCTSF / TSN AF also maps configuration to 3GPP parameters where applicable.

[0007] In FIGURE 1, R2 and R3 are example routers or bridges on the network side that are directly configured by the Controller. R2 is directly attached to the UPF, while R3 is a standalone router outside of the 5GS.

[0008] Similarly, R1 is an example router or bridge on the terminal side that is directly configured by the Controller. In this case, R1 may be reachable over the 5GS, meaning that the configuration takes place over the air, but the actual protocol for configuration is an IETF protocol such as Netconf / Restconf, and no 3GPP protocol would be used for the configuration of R1 even though that node may be part of a terminal device. That means that the configuration is carried out using user plane packets that are not detected or influenced by the 3 GPP network. In the example of FIGURE 1, R1 is reachable over 2 UEs and R1 is directly attached to the UEs. Any of the UEs could be used for the configuration.

[0009] The Controller may also configure nodes that are not part of the 5GS.

[0010] There currently exist certain challenge(s), however. For example, according to the current mechanism for configuration, there is no way to send configuration to the terminal or network node beyond the parameters that are defined in 3GPP. In certain deployments, it may be necessary to use other Information Elements (IEs) besides what 3GPP has defined, but the current mechanism does not allow that since PMIC and UMIC can only carry 3GPP defined parameters. Additionally, the 3GPP standardization process is rather slow, and it may not be able to keep up with the new parameters that may need to be used in practice. Use cases for such additional configuration beyond what has been standardized by 3GPP may include, for example, routing configuration and / or configuration of redundant paths,. In other cases, additional IETF / IEEE standardized parameters or vendor specific attributes may be needed in some deployments beyond what 3GPP has defined.

[0011] Another shortcoming of current mechanisms for configuration is that there is no way for the terminal or network node to receive a full block of configuration. The current PMIC and UMIC only provides IEs, and cannot provide a block of configuration, such as a full “Yet Another Next Generation” YANG configuration or a block of such configuration. YANG is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols, as defined in RFC 7950. The parsing of the configuration is currently only possible in the TSN AF or TSCTSF, and not the actual terminal or network node. This may be suitable for specific scenarios standardized by 3GPP. However, as new scenarios may arise, it may be necessary for the configured nodes (in the terminal or network side) to parse the configuration on their own, and in that way make use of the full potential of network configuration, as defined in IETF, IEEE, or elsewhere. Otherwise, even if the controller and the network element support a given function, it may not be possible to use.

[0012] SUMMARY

[0013] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, methods and systems are provided for network configuration transfer in 5GS. According to certain embodiments, a method by a first node for network configuration transfer includes transmitting, to a second node, information including an identifier of a type of network configuration information that the first node and / or a node in communication with the first node is capable of receiving. The first node receives, from the second node, the network configuration information of the type associated with the identifier in the information.

[0014] According to certain embodiments, a first node for network configuration transfer is configured to transmit, to a second node, information including an identifier of a type of network configuration information that the first node and / or a node in communication with the first node is capable of receiving. The first node is configured to receive, from the second node, the network configuration information of the type associated with the identifier in the information..

[0015] According to certain embodiments, a method by a second node for network configuration transfer includes receiving, from a first node, information including an identifier of a type of network configuration information that the first node and / or a node in communication with the first node is capable of receiving. The second node transmits, to the first node, the network configuration information of the type associated with the identifier in the information.

[0016] According to certain embodiments, a second node for network configuration transfer is configured to receive, from a first node, information including an identifier of a type of network configuration information that the first node and / or a node in communication with the first node is capable of receiving. The second node is configured to transmit, to the first node, the network configuration information of the type associated with the identifier in the information.

[0017] According to certain embodiments, a method by a controller for network configuration transfer includes receiving, from a second node, information comprising an identifier of a type of network configuration information that a first node and / or a node in communication with the first node is capable of receiving. The controller transmits, to the second node, the network configuration information of the type associated with the identifier in the information.

[0018] According to certain embodiments, a controller for network configuration transfer is configured to receive, from a second node, information comprising an identifier of a type of network configuration information that a first node and / or a node in communication with the first node is capable of receiving. The controller is configured to transmit, to the second node, the network configuration information of the type associated with the identifier in the information.

[0019] Certain embodiments may provide one or more of the following technical advantage (s). For example, certain embodiments may provide a technical advantage of supporting network deployments where other configuration parameters are needed besides what 3GPP has defined. As another example, certain embodiments may provide a technical advantage of supporting network deployments where the processing of the configuration takes place at the configured entity rather than at a central 3GPP network function. In that way, the network configuration becomes more powerful, allowing for more features, and / or the processing in the 3GPP network functions is simplified.

[0020] As still another example, certain embodiments may provide a technical advantage of using 3GPP signaling to configure nodes attached to the terminal or network entities. Thus, certain embodiments simplify the network configuration task and do not require additional configuration protocol (such as Netconf / Restconf) to be supported at the terminal or network side.

[0021] Other advantages may be readily apparent to one having skill in the art. Certain embodiments may have none, some, or all of the recited advantages.

[0022] BRIEF DESCRIPTION OF THE DRAWINGS

[0023] For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

[0024] FIGURE 1 illustrates an example TSN and / or DetNet;

[0025] FIGURE 2 illustrates an example system architecture for network configuration transfer in 5GS, according to certain embodiments;

[0026] FIGURE 3 illustrates example signaling for indicating whether an entity is capable of receiving a full configuration or portion of a configuration, according to certain embodiments;

[0027] FIGURE 4 illustrates another example architecture of a system where the configuration that is provided by the Controller to the CTF is further delivered to the R1 or R2 entity via the DS- TT function at UE1 or via the NW-TT, according to certain embodiments;

[0028] FIGURE 5 illustrates example signalling for delivering the configuration from controller to R via CTF and TT, according to certain embodiments;

[0029] FIGURES 6A, 6B, and 6C illustrate the different options for R2, according to certain embodiments;

[0030] FIGURE 7 illustrates an example communication system, according to certain embodiments;

[0031] FIGURE 8 illustrates an example UE, according to certain embodiments;

[0032] FIGURE 9 illustrates an example network node, according to certain embodiments;

[0033] FIGURE 10 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments; FIGURE 11 illustrates an example method by a first radio node for network configuration transfer, according to certain embodiments;

[0034] FIGURE 12 illustrates an example method by a second radio node for network configuration transfer, according to certain embodiments; FIGURE 13 illustrates a method by a first node for network configuration transfer, according to certain embodiments;

[0035] FIGURE 14 illustrates a method by a second node for network configuration transfer, according to certain embodiments; and

[0036] FIGURE 15 illustrates a method by a controller for network configuration transfer, according to certain embodiments.

[0037] DETAILED DESCRIPTION

[0038] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0039] As used herein, ‘node’ can be a network node or a UE. Examples of network nodes are NodeB, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB (eNB), gNodeB (gNB), Master eNB (MeNB), Secondary eNB (SeNB), integrated access backhaul (IAB) node, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), Central Unit (e.g. in a gNB), Distributed Unit (e.g. in a gNB), Baseband Unit, Centralized Baseband, C-RAN, access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), core network node (e.g. Mobile Switching Center (MSC), Mobility Management Entity (MME), etc.), Operations & Maintenance (O&M), Operations Support System (OSS), Self Organizing Network (SON), positioning node (e.g. E- SMLC), etc.

[0040] Another example of a node is user equipment (UE), which is a non-limiting term and refers to any type of wireless device communicating with a network node and / or with another UE in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, vehicular to vehicular (V2V), machine type UE, MTC UE or UE capable of machine to machine (M2M) communication, Personal Digital Assistant (PDA), Tablet, mobile terminals, smart phone, laptop embedded equipment (LEE), laptop mounted equipment (LME), Unified Serial Bus (USB) dongles, etc.

[0041] In some embodiments, generic terminology, “radio network node” or simply “network node (NW node)”, is used. It can be any kind of network node which may comprise base station, radio base station, base transceiver station, base station controller, network controller, evolved Node B (eNB), Node B, gNodeB (gNB), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH), Central Unit (e.g. in a gNB), Distributed Unit (e.g. in a gNB), Baseband Unit, Centralized Baseband, C-RAN, access point (AP), etc.

[0042] The term radio access technology (RAT), may refer to any RAT such as, for example, Universal Terrestrial Radio Access Network (UTRA), Evolved Universal Terrestrial Radio Access Network (E-UTRA), narrow band internet of things (NB-IoT), WiFi, Bluetooth, next generation RAT, NR, 4G, 5G, etc. Any of the equipment denoted by the terms node, network node or radio network node may be capable of supporting a single or multiple RATs. The term signal or radio signal used herein can be any physical signal or physical channel. Examples of downlink (DL) physical signals are reference signal (RS) such as Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), Channel State Information-Reference Signal (CSI-RS), Demodulation Reference Signal (DMRS) signals in SS / PBCH block (SSB), discovery reference signal (DRS), Cell Specific Reference Signal (CRS), Positioning Reference Signal (PRS), etc. RS may be periodic. For example, RS occasions carrying one or more RSs may occur with certain periodicity (e.g., 20 ms, 40 ms, etc.). The RS may also be aperiodic.

[0043] Each SSB carries New Radio-Primary Synchronization Signal (NR-PSS), New RadioSecondary Synchronization Signal (NR-SSS) and New Radio-Physical Broadcast Channel (NR- PBCH) in four successive symbols. One or multiple Synchronization Signal Blocks (SSBs) are transmitted in one SSB burst which is repeated with certain periodicity such as, for example, 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160 ms. The UE is configured with information about SSB on cells of certain carrier frequency by one or more SS / PBCH block measurement timing configuration (SMTC) configurations. The SMTC configuration comprising parameters such as SMTC periodicity, SMTC occasion length in time or duration, SMTC time offset with regard to reference time (e.g., serving cell’s SFN) etc. Therefore, SMTC occasion may also occur with certain periodicity (e.g., 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160 ms). Examples of uplink (UL) physical signals are reference signals such as Sounding Reference Signals (SRS), Demodulation Reference Signals (DMRS), etc. The term physical channel refers to any channel carrying higher layer information e.g. data, control etc. Examples of physical channels are Physical Broadcast Channel (PBCH), Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), Short PUSCH (sPUCCH), Short PDSCH (sPDSCH), Short PUCCH (sPUCCH), Short PUSCH (sPUSCH), MTC PDCCH (MPDCCH), Narrowband PBCH (NPBCH), Narrowband PDCCH (NPDCCH), Narrowband PDSCH (NPDSCH), Narrowband PUSCH (NPUSCH), Enhanced PDCCH (E-PDCCH), etc.

[0044] The term time resource used herein may correspond to any type of physical resource or radio resource expressed in terms of length of time. Examples of time resources are: symbol, time slot, subframe, radio frame, TTI, interleaving time, slot, sub-slot, mini-slot, system frame number (SFN) cycle, hyper-SFN (H-SFN) cycle etc.

[0045] Some shortcomings of current techniques and mechanisms for configuration are described above. Another example of a shortcoming of current techniques and mechanisms for configuration is that there is no way to send the configuration using the 3GPP signaling to nodes directly attached to 3GPP entities. For example, a terminal side router (Rl) could be configured via the 3GPP signaling if the UEs are able to deliver the configuration to the Rl node (and get the responses back) using e.g., an Application Programming Interface (API) within the device. Similarly, a network side router (R2) could be configured via the 3GPP signaling if the UPF is able to deliver the configuration to the R2 node (and get the response back). But the current 3GPP procedures do not allow for this, even though such configuration could be useful and make the nodes simpler.

[0046] According to certain embodiments described herein, methods and systems are provided that include a terminal side entity (such as the DS-TT) or a network side entity (such as the NW- TT), or a node attached to one of these entities (such as Rl or R2 in certain particular example embodiments) indicating that the terminal or network side entity is capable of receiving a block of network configuration of a certain type. In a particular embodiment, the indication also includes the identity of the node / entity. Based on the indication, a Configuration transfer function (CTF), which may be realized separately or as part of the TSN AF or TSCTSF, provides, within a signaling container (such as the PMIC or UMIC), the configuration, together with addressing information, which is delivered to the destination node / entity. If needed, the terminal or network side entity forwards the configuration based on the addressing information to the attached node.

[0047] According to various particular embodiments, the limitations of previous systems and methods may be overcome by one or more of the following enhancements:

[0048] • Indication of the type of configuration a terminal or network side entity or node attached to them requests to receive, together with addressing information. The signaling may take place in PMIC or UMIC.

[0049] • Terminal or network side entity forwards a block of configuration (received in PMIC or UMIC) to a node attached to them based on the addressing information contained together with the configuration information.

[0050] • Terminal or network side entity forwards configuration (or updates) together with addressing information from a node attached to them to a CTF, which may be realized in a TSN AF or TSCTSF in PMIC or UMIC.

[0051] • Based on indications from the terminal or network side entity or an attached node indicating the type of configuration, the CTF provides a block of configuration (which may, possibly, include the full configuration) when available.

[0052] • The CTF exposes to the central controller the configured entities that may receive a full block of configuration as separate network nodes and assigns individual addresses or identifiers for configuration. The CTF also exposes responses or configuration updates to the central controller so that the identity of the concerned node / entity is provided either using individual addresses assigned, or by identifiers.

[0053] Delivering a Full Block of Configuration

[0054] FIGURE 2 illustrates an example architecture for a system 100 for network configuration transfer in 5GS, according to certain embodiments. As illustrated, a central controller 102 may provide configuration to, for example, nodes Rl, R2 and R3 (denoted on FIGURE 2 as 104a, 104b, and 104c, respectively), and also to the 5GS node 106. Within the 5GS node 106, the CTF 108 receives the configuration. In particular embodiments, the CTF 108 may correspond to a TSN AF or TSCTSF.

[0055] As described above, according to certain embodiments, the DS-TT 110a or NW-TT 110b entities (or other entities) may indicate whether they are capable of receiving a full configuration of a certain type. The CTF provides the full configuration or a block (i.e., portion) of the configuration to the DS-TT 110a or NW-TT 110b entities that have indicated interest in receiving such configuration.

[0056] FIGURE 3 illustrates example signaling 200 for indicating whether an entity is capable of receiving a full configuration or portion of a configuration, according to certain embodiments. As illustrated, the signaling includes:

[0057] • At step 202, a terminal or network side entity (such as the DS-TT 110a or NW-TT 110b), abbreviated here and depicted as TT 110 may indicate to the CTF 108 (which may be located at the TSN AF or TSCTSF) that the TT 110 can receive a certain type of block of configuration. The indication may include a reference to the type of configuration (e.g., based on the name of the configuration in IETF, or its designated namespace, or other identifier), and it may also indicate which part of the configuration the indication applies to (such as, for example, a filtering criterion may be given for which data within the configuration is relevant). It is recognized, however, that the indication of step 202 is optional; instead of the indication, the information may also be pre-configured into the CTF 108, or the information may be downloaded from a database such as via the UDM.

[0058] • At step 204, the Controller 102 provides configuration to 5GS, which is received at the CTF 108.

[0059] • At step 206, the CTF 108 filters whether a configuration block of type X is part of the configuration. • If the configuration block of type X is part of the configuration, the configuration block of type X is delivered from CTF 108 to TT 110, at step 208. In particular embodiments, the block of configuration of type X is included in a PMIC or UMIC message to the relevant TT 110. The type of block may also be indicated.

[0060] • At step 210, the TT 110 may provide a response, or it may provide an update of the configuration to the CTF 108.

[0061] • At step 212, the CTF 108 provides the configuration update to the Controller 102. It may be possible for the CTF 108 to aggregate the configuration from multiple TTs 110 and provide them to the Controller 108 simultaneously.

[0062] It is noted that the solution may be applied in combination with existing mechanisms. For example, in a particular embodiment, a TT 110 may receive a block of configuration, and also individual IES, as processed in the CTF 108 (e.g., TSCTSF or TSN AF). Thus, it is possible that a full block of configuration is sent to a TT, and additionally, TSCTSF or TSN AF may extract some configuration parameters, which are also sent separately as information elements in a message. As such, there may be an overlap between the two methods, i.e., the same information may appear twice. However, this is not necessarily a problem since this may help to make all information available to the TT implementation.

[0063] Delivering Configuration to Nodes Attached to 3GPP Entities

[0064] According to certain embodiments, a node attached to a 3GPP entity could be configured using the 3GPP PMIC / UMIC signaling. FIGURE 4 illustrates another example architecture of a system 300 where the configuration that is provided by the Controller 102 to the CTF 108 is further delivered to the R1 104a or R2 104b entity via the DS-TT 110a at UE1 or via the NW-TT 110b, according to certain embodiments.

[0065] FIGURE 5 illustrates example signalling 400 for delivering the configuration from Controller 102 to R 104 via CTF 108 and TT 110, according to certain embodiments. As denoted below and depicted in FIGURE 5, R 104 corresponds to R1 104a or R2 104b, and TT 110 corresponds to DS-TT 110a at UE1 or UE2, or to NW-TT 110b, as depicted in FIGURE 4.

[0066] As illustrated in FIGURE 5, the signaling includes:

[0067] • At step 402, a node R 104, such as a router that is attached to a TT entity 110 indicates (over an API that may be internal in a device) to the TT 110 that it is ready to receive configuration via the TT 110. The indication also provides the identity of R 104, and may also include the type of configuration required. In certain embodiments, the address of the central controller 102 may also be preconfigured into R 104 and may also be provided in the message. Furthermore, in a particular embodiment, R 104 indicates whether or not it requests to be exposed as a separate entity to the controller 102. In case R 104 is exposed as a separate entity, it will be considered by the controller 102 as a separate node, attached to the 5GS by a virtual interface. In case R 104 is not exposed as a separate entity, the controller 102 will not see R 104 as a separate node, and R 104 gets a (block of the) configuration for 5GS.

[0068] • At step 404, the TT 110 relays the message from R 104, together with all relevant information, within a PMIC (or UMIC in case ofNW-TT 110b), and provides it to the CTF 108. This indicates to the CTF 108 that configuration of R 104 is possible via the given TT 110. This message establishes the indirect signaling path between CTF 108 and R 104 via the given TT 110; CTF 108 stores this signaling path. According to a particular embodiment, it is possible to exchange additional setup messages between CTF 108 and R 104 to set up subscription to notification on changes in the configuration.

[0069] • In case R 104 indicates its request to be considered as a separate entity to the Controller (or if this is determined by the CTF 108 based on configuration or other information), the CTF 108 may notify the Controller 102 about the presence of R 104 that is possible to be configured. The address of the Controller 102 may already be known (preconfigured) in the CTF 108, or be based on the indication from R 104 or discovered in other ways (e.g., using Domain Name Service (DNS)). In a particular embodiment, this notification signalling uses a dedicated address at CTF 108 that is unique to R 104, so that the address used for the signalling between CTF 108 and R 104 identifies R 104. Alternatively, in a particular embodiment, the notification includes an identifier of R 104, and this identifier identifies the information that is applicable to R 104 later on for the configuration provided by the Controller 102. As another alternative, in a particular embodiment, CTF 108 also provides a network topology update to the controller 102, which includes the node R 104 as a neighbor to the 5GS node to make the controller 102 aware of R 104.

[0070] • This step is optional, it is also possible that if needed, the Controller becomes aware of the presence of R in other ways, or based on preconfiguration. Also steps 1-2 are optional and could be skipped if the presence of R is pre-configured into the CTF and the UE. • The controller provides configuration for R. To identify R, the configuration may be addressed to an address at the CTF that is unique for R, or the configuration includes an identifier of R, in case R is considered as a separate entity.

[0071] • Based on the earlier indication in step 2 (or by preconfiguration), CTF knows that R is reachable via TT. Hence, the configuration is delivered to TT within a PMIC / UMIC, including addressing information to identify R as the destination of the configuration. In case R is not a separate logical entity, CTF filters which part of the configuration is relevant for R based on earlier indication from R on the type of configuration required.

[0072] • TT determines that the configuration is addressed to R, hence TT delivers the config to R using an API between R and TT.

[0073] • A response or update of the configuration is signalled from R to TT.

[0074] • The response or update of the configuration is signalled from TT to CTF, indicating also R as the source, within a PMIC or UMIC

[0075] • container.

[0076] • The response or update of the configuration is signalled from the CTF to the Controller. In case R is to be considered as a separate entity, R is indicated as the source, either as an explicit source parameter, or based on the address of the signalling message from the CTF.

[0077] It is noted that the mechanisms presented above may be combined as well.

[0078] It may be possible that there are multiple TTs 110 that can relay between R 104 and the CTF 108. As illustrated in FIGURES 2 and 4, UE1 and UE2 may also provide connectivity to and from the same R1 104a, in a particular embodiment. In that case, it may be possible that the signalling between R1 104a and CTF 108 takes multiple paths. The CTF 108 may send the configuration via all available paths. Each configuration can be assigned a unique identifier, and if delivered via multiple paths, the receiving side can determine, based on the unique transaction identifier, whether it has already processed the given message and eliminate duplicates. Using multiple paths for signalling can increase the reliability of the signalling in case of failures.

[0079] On the network side, the node R2 104b may be attached to the NW-TT 110b, similarly to the terminal case for R1 104a. For the network side, there may be several types of nodes, which are attached to a NW-TT 110b, that may be configured: an internal router node function within the UPF; a router node function that works on the N6 side traffic; a router node function realized within the NW-TT 110b; and other cases.

[0080] According to a particular embodiment, in addition to identifying itself, R 104 also indicates which type of node it is (as the examples above illustrate) and provides the information also via the NW-TT 110b to the CTF 108. In a particular embodiment, the CTF 108 decides to allow or disallow certain types of nodes based on operator policies.

[0081] Regarding the relationship of 5GS routing and the N6 routing function, in case of Internet Protocol (IP) based networks, there can be multiple options. FIGURES 6A, 6B, and 6C illustrate the different options 500A, 500b, and 500c, respectively, for R2 104b, according to certain embodiments.

[0082] Specifically, as illustrated in FIGURE 6A, the UPF 502 and the N6 router 504 act as a single logical router (per UPF 502), hence the controller 102 sends a single node configuration. Within the 5GS node 106, the relevant configuration is delivered from the CTF 108 to the NW- TT 1 lOb / UPF 502. It may be that the N6 router 504 also requires parts of the configuration, and for that the N6 router 504 may register itself at the CTF 108. However, in this case, the N6 router 504 is not made visible to the controller 102, as it acts as a single logical node with the UPF 502. This case is realized by the solution(s) described herein.

[0083] As illustrated in FIGURE 6B, the N6 router 504 is considered logically separate from the 5GS node 106, connected by a virtual interface in the topology, even though the N6 router 504 may be directly attached to the NW-TT 1 lOb / UPF 502. The N6 router 504 may be configured via the 5GS node 106, which in this case exposes the N6 router 504 using a separate logical interface, identified by a separate address or an identifiers. That is, the controller 102 considers the 5GS node 106 and the N6 router 504 as separate entities. This case is realized by the solution(s) described herein.

[0084] As illustrated in FIGURE 6C, the N6 router 504 is again considered logically separate from the 5GS node 106, connected by a virtual interface. However, in this case, the N6 router 504 is directly configured by the controller 102 independent of 5GS. For this case, there may be no need for the solution(s) described herein. On the other hand, the configuration of N6 router 504 needs to use a separate protocol and cannot make use of the available signalling path via 5GS.

[0085] In this description, the controller 102 is described as a separate entity from the CTF 108. However, according to certain embodiments, the controller 102 is combined with the CTF 108.

[0086] In certain embodiments, an operator may use policies or subscription information to allow or disallow the mechanism presented in this document. The use of these mechanisms may be allowed or disallowed such as, for example, on a per UE basis, or on a per network instance basis. The TT 110 may provide capability information to the CTF 108 to indicate whether it is capable of acting as a signalling relay to an attached node.

[0087] Other Options

[0088] In addition to the task of delivering configuration to a node attached to a 3 GPP entity, the solutions, mechanisms, techniques, and embodiments presented herein can also be used for other purposes, making use of the signalling path between the node attached to a 3GPP entity and a 3GPP network function such as the 3GPP CTF. The following scenarios can also be supported using the solutions, mechanisms, techniques, and embodiments:

[0089] • Delivering a set of parameters describing configuration or capabilities of the node attached to the 3GPP entity to the 3GPP network function, and possibly further delivering to a controller (which may reside inside or outside of the 5GS).

[0090] • Delivering software or firmware updates. This may include the identification of the current software or firmware versions, and returning information on the success of the update process.

[0091] • Installing, updating, or uninstalling software modules to the node attached to the 3GPP entity. Notifications may be provided on the success or failure of the operations. Functionality may also be included to start or stop software or applications on the node.

[0092] • Status and performance monitoring, where the node attached to the 3GPP entity provides status and / or performance updates to the 3GPP network function, and can possibly be further delivered to a server that may reside inside or outside of the 5GS. The status and performance information can be provided periodically, or by other local triggers at the node attached to the 3GPP entity, or upon request from a server.

[0093] • Diagnostics information, including information at failure situations or information from running diagnostic tests, which may be provided from the node attached to the 3GPP entity to a 3GPP network function, and can possibly be further delivered to a server collecting such information.

[0094] Such scenarios are known in fixed networks, but with the solutions, mechanisms, techniques, and embodiments presented herein, these scenarios can also be extended to nodes attached to a 3GPP entity. As another option, the solutions, mechanisms, techniques, and embodiments described herein may also be applied to the 3GPP entities (such as the DS-TT or NW-TT) themselves, as described above.

[0095] For these options, the concerned entity needs to first announce its capabilities and requests to perform the above tasks, so that the 3GPP network function (CTF) can trigger these actions. The concerned parameters need to be identified. The CTF may also contact the relevant servers inside or outside the 5GS and trigger the actions as needed.

[0096] FIGURE 7 shows an example of a communication system 600 in accordance with some embodiments. In the example, the communication system 600 includes a telecommunication network 602 that includes an access network 604, such as a RAN, and a core network 606, which includes one or more core network nodes 608. The access network 604 includes one or more access network nodes, such as network nodes 610a and 610b (one or more of which may be generally referred to as network nodes 610), or any other similar 3GPP access node or non-3GPP access point. The network nodes 610 facilitate direct or indirect connection of UE, such as by connecting UEs 612a, 612b, 612c, and 612d (one or more of which may be generally referred to as UEs 612) to the core network 606 over one or more wireless connections.

[0097] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 600 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 600 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0098] The UEs 612 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 610 and other communication devices. Similarly, the network nodes 610 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 612 and / or with other network nodes or equipment in the telecommunication network 602 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 602.

[0099] In the depicted example, the core network 606 connects the network nodes 610 to one or more hosts, such as host 616. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 606 includes one more core network nodes (e.g., core network node 608) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 608. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0100] The host 616 may be under the ownership or control of a service provider other than an operator or provider of the access network 604 and / or the telecommunication network 602, and may be operated by the service provider or on behalf of the service provider. The host 616 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0101] As a whole, the communication system 600 of FIGURE 7 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0102] In some examples, the telecommunication network 602 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 602 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 602. For example, the telecommunications network 602 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.

[0103] In some examples, the UEs 612 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 604 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 604. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi -radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0104] In the example, the hub 614 communicates with the access network 604 to facilitate indirect communication between one or more UEs (e.g., UE 612c and / or 612d) and network nodes (e.g., network node 610b). In some examples, the hub 614 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 614 may be a broadband router enabling access to the core network 606 for the UEs. As another example, the hub 614 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 610, or by executable code, script, process, or other instructions in the hub 614. As another example, the hub 614 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 614 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 614 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 614 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 614 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

[0105] The hub 614 may have a constant / persistent or intermittent connection to the network node 610b. The hub 614 may also allow for a different communication scheme and / or schedule between the hub 614 and UEs (e.g., UE 612c and / or 612d), and between the hub 614 and the core network 606. In other examples, the hub 614 is connected to the core network 606 and / or one or more UEs via a wired connection. Moreover, the hub 614 may be configured to connect to an M2M service provider over the access network 604 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 610 while still connected via the hub 614 via a wired or wireless connection. In some embodiments, the hub 614 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 610b. In other embodiments, the hub 614 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 610b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0106] FIGURE 8 shows a UE 700 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0107] A UE may support device -to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0108] The UE 700 includes processing circuitry 702 that is operatively coupled via a bus 704 to an input / output interface 706, a power source 708, a memory 710, a communication interface 712, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIGURE 8. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0109] The processing circuitry 702 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 710. The processing circuitry 702 may be implemented as one or more hardware -implemented state machines (e.g., in discrete logic, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 702 may include multiple central processing units (CPUs).

[0110] In the example, the input / output interface 706 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 700. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0111] In some embodiments, the power source 708 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 708 may further include power circuitry for delivering power from the power source 708 itself, and / or an external power source, to the various parts of the UE 700 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 708. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 708 to make the power suitable for the respective components of the UE 700 to which power is supplied.

[0112] The memory 710 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 710 includes one or more application programs 714, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 716. The memory 710 may store, for use by the UE 700, any of a variety of various operating systems or combinations of operating systems.

[0113] The memory 710 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 710 may allow the UE 700 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 710, which may be or comprise a device -readable storage medium.

[0114] The processing circuitry 702 may be configured to communicate with an access network or other network using the communication interface 712. The communication interface 712 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 722. The communication interface 712 may include one ormore transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 718 and / or a receiver 720 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 718 and receiver 720 may be coupled to one or more antennas (e.g., antenna 722) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0115] In the illustrated embodiment, communication functions of the communication interface 712 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0116] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 712, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0117] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0118] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or itemtracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 700 shown in FIGURE 8. As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0119] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0120] FIGURE 9 shows a network node 800 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NRNodeBs (gNBs)).

[0121] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0122] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0123] The network node 800 includes a processing circuitry 802, a memory 804, a communication interface 806, and a power source 808. The network node 800 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 800 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 800 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 804 for different RATs) and some components may be reused (e.g., a same antenna 810 may be shared by different RATs). The network node 800 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 800, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 800.

[0124] The processing circuitry 802 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 800 components, such as the memory 804, to provide network node 800 functionality.

[0125] In some embodiments, the processing circuitry 802 includes a system on a chip (SOC). In some embodiments, the processing circuitry 802 includes one or more of radio frequency (RF) transceiver circuitry 812 and baseband processing circuitry 814. In some embodiments, the radio frequency (RF) transceiver circuitry 812 and the baseband processing circuitry 814 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 812 and baseband processing circuitry 814 may be on the same chip or set of chips, boards, or units. The memory 804 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 802. The memory 804 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 802 and utilized by the network node 800. The memory 804 may be used to store any calculations made by the processing circuitry 802 and / or any data received via the communication interface 806. In some embodiments, the processing circuitry 802 and memory 804 is integrated.

[0126] The communication interface 806 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 806 comprises port(s) / terminal(s) 816 to send and receive data, for example to and from a network over a wired connection. The communication interface 806 also includes radio frontend circuitry 818 that may be coupled to, or in certain embodiments a part of, the antenna 810. Radio front-end circuitry 818 comprises filters 820 and amplifiers 822. The radio front-end circuitry 818 may be connected to an antenna 810 and processing circuitry 802. The radio frontend circuitry may be configured to condition signals communicated between antenna 810 and processing circuitry 802. The radio front-end circuitry 818 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 818 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 820 and / or amplifiers 822. The radio signal may then be transmitted via the antenna 810. Similarly, when receiving data, the antenna 810 may collect radio signals which are then converted into digital data by the radio front-end circuitry 818. The digital data may be passed to the processing circuitry 802. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0127] In certain alternative embodiments, the network node 800 does not include separate radio front-end circuitry 818, instead, the processing circuitry 802 includes radio front-end circuitry and is connected to the antenna 810. Similarly, in some embodiments, all or some of the RF transceiver circuitry 812 is part of the communication interface 806. In still other embodiments, the communication interface 806 includes one or more ports or terminals 816, the radio front-end circuitry 818, and the RF transceiver circuitry 812, as part of a radio unit (not shown), and the communication interface 806 communicates with the baseband processing circuitry 814, which is part of a digital unit (not shown).

[0128] The antenna 810 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 810 may be coupled to the radio front-end circuitry 818 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 810 is separate from the network node 800 and connectable to the network node 800 through an interface or port.

[0129] The antenna 810, communication interface 806, and / or the processing circuitry 802 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 810, the communication interface 806, and / or the processing circuitry 802 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0130] The power source 808 provides power to the various components of network node 800 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 808 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 800 with power for performing the functionality described herein. For example, the network node 800 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 808. As a further example, the power source 808 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0131] Embodiments of the network node 800 may include additional components beyond those shown in FIGURE 9 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 800 may include user interface equipment to allow input of information into the network node 800 and to allow output of information from the network node 800. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 800. FIGURE 10 is a block diagram illustrating a virtualization environment 1000 in which functions implemented by some embodiments may be virtualized.

[0132] In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, 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. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1000 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.

[0133] Applications 1002 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0134] Hardware 1004 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1006 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1008a and 1008b (one or more of which may be generally referred to as VMs 1008), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1006 may present a virtual operating platform that appears like networking hardware to the VMs 1008.

[0135] The VMs 1008 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1006. Different embodiments of the instance of a virtual appliance 1002 may be implemented on one or more of VMs 1008, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment. In the context of NFV, a VM 1008 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1008, and that part of hardware 1004 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1008 on top of the hardware 1004 and corresponds to the application 1002.

[0136] Hardware 1004 may be implemented in a standalone network node with generic or specific components. Hardware 1004 may implement some functions via virtualization. Alternatively, hardware 1004 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1010, which, among others, oversees lifecycle management of applications 1002. In some embodiments, hardware 1004 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1012 which may alternatively be used for communication between hardware nodes and radio units.

[0137] FIGURE 11 illustrates an example method 1100 by a first radio node for network configuration transfer, according to certain embodiments. In the illustrated embodiment, the method includes a transmitting step at 1102 and a receiving step at 1104. For example, at step 1102, the first radio node may transmit, to a second radio node, information comprising an indication that the first radio node and / or a node in communication with the first radio node is capable of receiving a type of network configuration information. At step 1104, for example, the first radio node may receive, from the second radio node, the network configuration information of the type indicated in the information.

[0138] FIGURE 12 illustrates an example method 1200 by a second radio node for network configuration transfer, according to certain embodiments. In the illustrated embodiment, the method includes a receiving step at 1202 and a transmitting step at 1204. For example, at step 1202, the second radio node may receive, from a first radio node, information comprising an indication that the first radio node and / or a node in communication with the first radio node is capable of receiving a type of network configuration information. At step 1204, for example, the second radio node may transmit, to the first radio node, the network configuration information of the type indicated in the information.

[0139] FIGURE 13 illustrates a method 1300 by a first node for network configuration transfer, according to certain embodiments. In the illustrated embodiment, the method begins at step 1302 with transmitting, to a second node, information comprising an identifier of a type of network configuration information that the first node and / or a node in communication with the first node is capable of receiving. At step 1304, the first node receives, from the second node, the network configuration information of the type associated with the identifier in the information.

[0140] In a particular embodiment, the information includes an indication that the first node and / or the node in communication with the first node is capable of receiving at least one of: a portion of a network configuration and a full network configuration.

[0141] In a particular embodiment, the information includes an indication that the first node and / or the node in communication with the first node is capable of receiving a block of IES associated with the network configuration. The network configuration information received from the second radio node includes the block of IEs associated with the network configuration.

[0142] In a particular embodiment, the identifier incudes at least one of: a name of the network configuration or the portion of the network configuration, a designated namespace associated with the network configuration or the portion of the network configuration, and a filtering criterion to be applied to the network configuration.

[0143] In a particular embodiment, the information includes at least one of: identification information associated with the first node; address information associated with the first node; identification information associated with the node in communication with the first node; address information associated with the node in communication with the first node; and information indicating a type of the node in communication with the first node.

[0144] In a particular embodiment, the first node includes a DS-TT 110a for transmitting the information to the second node. In another embodiment, the first node includes aNW-TT 110b for receiving the information from the node in communication with the first node.

[0145] In a particular embodiment, the second node includes a CTF 108, which may include a TSN AF or TSCTSF.

[0146] In a particular embodiment, the information is transmitted to the CTF 108 by the first node on behalf of the node in communication with the first node.

[0147] In a particular embodiment, the node in communication with the first node includes at least one of: a router in communication with the first node (e.g., R1 104a or R2 104b), a bridge in communication with the first node, an internal router node function within a UPF, and a router node function.

[0148] In a particular embodiment, the first node receives, from the node in communication with the first node, the information comprising the identifier of the type of network configuration information that the node in communication with the first node is capable of receiving. The first node forwards the information to the second node.

[0149] In a particular embodiment, the first node forwards the network configuration information received from the second node to the node in communication with the first node.

[0150] In a particular embodiment, the information includes an indication that the node in communication with the first node is to be exposed to the second node as a separate entity from the first node. In another particular embodiment, the information includes an indication that the node in communication with the first node is not to be exposed to the second node as a separate entity from the first node.

[0151] In a particular embodiment, the first node transmits, to the second node, a response message indicating receipt of the network configuration information.

[0152] In a particular embodiment, the method further includes at least one of: updating a configuration of the first node based on the network configuration information received from the second node; receiving, from the node in communication with the first radio node, an updated network configuration; and transmitting, to the second radio node, an updated configuration of the first radio node and / or the node in communication with the first radio node.

[0153] In a particular embodiment, the network configuration information is received in a PMIC or a UMIC, and / or the information transmitted to the second radio node is transmitted in the PMIC or the UMIC.

[0154] FIGURE 14 illustrates a method 1400 by a second node for network configuration transfer, according to certain embodiments. As illustrated, the method begins at step 1402 when the second node receives, from a first node, information that includes an identifier of a type of network configuration information that the first node and / or a node in communication with the first node is capable of receiving. At step 1404, the second node transmits, to the first node, the network configuration information of the type associated with the identifier in the information.

[0155] In a particular embodiment, the information includes an indication that the first node and / or the node in communication with the first node is capable of receiving at least one of: a portion of a network configuration, and a full network configuration.

[0156] In a particular embodiment, the information includes an indication that the first node and / or the node in communication with the first node is capable of receiving a block of IES associated with a network configuration. The network configuration information transmitted to the first includes the block of IES associated with the network configuration. In a particular embodiment, the identifier includes at least one of: a name of the network configuration or the portion of the network configuration, a designated namespace associated with the network configuration or the portion of the network configuration, and a filtering criterion to be applied to the network configuration.

[0157] In a particular embodiment, the information includes at least one of: identification information associated with the first node; address information associated with the first node; identification information associated with the node in communication with the first node; address information associated with the node in communication with the first node; and information indicating a type of the node in communication with the first node.

[0158] In a particular embodiment, the first node comprises a DS-TT, and / or the first node comprises a NW-TT for receiving the information from the node in communication with the first node.

[0159] In a particular embodiment, the second radio node includes a CTF, which may include a TSN AF or TSCTSF.

[0160] In a particular embodiment, the information is received by the CTF via the first node on behalf of the node in communication with the first node.

[0161] In a particular embodiment, the node in communication with the first node includes at least one of: a router in communication with the first node, a bridge in communication with the first node, an internal router node function within a UPF, and a router node function.

[0162] In a particular embodiment, the second node forwards the information to a controller and receives the network configuration information from the controller.

[0163] In a particular embodiment, the controller is external to the second node.

[0164] In a particular embodiment, the controller is within the second node.

[0165] In a particular embodiment, the second node determines that the network configuration information received from the controller is of the type associated with the identifier in the information from the first node, and the network configuration information is forwarded to the first node based on determining that the network configuration information is of the type associated with the identifier in the information.

[0166] In a particular embodiment, the second node determines that a portion of the network configuration information received from the controller is of the type associated with the identifier in the information from the first node and filters out at least another portion of the network configuration information that is not of the type associated with the identifier in the information from the first node. Only the portion of the network configuration information that is of the type associated with the identifier is forwarded to the first node.

[0167] In a particular embodiment, the information includes an indication that the node in communication with the first node is to be exposed to the second node as a separate entity from the first node. Alternatively, the information includes an indication tha the node in communication with the first node is not to be exposed to the second node as a separate entity from the first node.

[0168] In a particular embodiment, the second node determines that a network configuration is of the type associated with the identifier in the information from the first node, and the network configuration information is transmitted to the first node based on determining that the network configuration is of the type associated with the identifier in the information.

[0169] In a particular embodiment, the second node determines that a portion of a network configuration is of the type associated with the identifier in the information from the first node and filters out at least a portion of the network configuration that is not of the type associated with the information from the first node. The network configuration information is transmitted to the first node based on determining that the portion of the network configuration is of the type associated with the identifier in the information.

[0170] In a particular embodiment, the second node receives, from the first node, a response message indicating receipt of the network configuration information. Additionally or alternatively, the second node receives, from the first node, an updated configuration of the first node and / or the node in communication with the first node.

[0171] In a particular embodiment, the network configuration information is transmitted in a PMIC or a UMIC and / or the information received from the first node is received in a PMIC or UMIC.

[0172] FIGURE 15 illustrates a method 1500 by a controller for network configuration transfer, according to certain embodiments. As illustrate, the method begins at step 1502 when the controller receives, from a second node, information includes an identifier of a type of network configuration information that a first node and / or a node in communication with the first node is capable of receiving. At step 1504, the controller transmits, to the second node, the network configuration information of the type associated with the identifier in the information.

[0173] In a particular embodiment, the controller determines that a network configuration is of the type associated with the identifier of the type of network configuration information that the first node and / or the node in communication with the first node is capable of receiving. The network configuration information is transmitted to the second node based on determining that the network configuration is of the type associated with the identifier in the information. In a particular embodiment, the controller determines that a portion of a network configuration is of the type associated with the identifier of the type of network configuration information that the first node and / or the node in communication with the first node is capable of receiving. The controller filters out at least a portion of the network configuration that is not of the type associated with the identifier. The network configuration information transmitted to the second node includes the portion of the network configuration that is of the type associated with the identifier and excludes the portion of the network configuration that is not of the type associated with the identifier.

[0174] In a particular embodiment, the information includes an indication that the first node and / or the node in communication with the first node is capable of receiving at least one of: a portion of a network configuration, and a full network configuration.

[0175] In a particular embodiment, the information includes an indication that the first node and / or the node in communication with the first node is capable of receiving a block of IES associated with a network configuration. The network configuration information transmitted to the first node comprises the block of IEs associated with the network configuration.

[0176] In a particular embodiment, the identifier includes at least one of: a name of the network configuration or the portion of the network configuration, a designated namespace associated with the network configuration or the portion of the network configuration, and a filtering criterion to be applied to the network configuration.

[0177] In a particular embodiment, the information includes at least one of: identification information associated with the first node; address information associated with the first node; identification information associated with the node in communication with the first node; address information associated with the node in communication with the first node; and information indicating a type of the node in communication with the first node.

[0178] In a particular embodiment, the first node comprises a DS-TT or a NW-TT, and the second radio node includes a CTF, which includes a TSN AF or TSCTSF.

[0179] In a particular embodiment, the node in communication with the first node comprises at least one of: a router in communication with the first node, a bridge in communication with the first node, an internal router node function within a UPF, and a router node function.

[0180] In a particular embodiment, the controller is external to the second node.

[0181] In a particular embodiment, the controller is within the second node.

[0182] In a particular embodiment, the information includes an indication that the node in communication with the first node is to be exposed to the second node as a separate entity from the first node. Alternatively, the information includes an indication tha the node in communication with the first node is not to be exposed to the second node as a separate entity from the first node.

[0183] In a particular embodiment, the network configuration information is transmitted in a PMIC or a UMIC, and / or the information received from the first node is received in a PMIC or UMIC.

[0184] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0185] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0186] EXAMPLE EMBODIMENTS

[0187] Group A Example Embodiments

[0188] Example Embodiment Al. A method by UE for network configuration transfer, the method comprising: any of the user equipment steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.

[0189] Example Embodiment A2. The method of the previous embodiment, further comprising one or more additional user equipment steps, features or functions described above.

[0190] Example Embodiment A3. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to the network node.

[0191] Group B Example Embodiments

[0192] Example Embodiment Bl. A method performed by a network node for network configuration transfer, the method comprising: any of the network node steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.

[0193] Example Embodiment B2. The method of the previous embodiment, further comprising one or more additional network node steps, features or functions described above.

[0194] Example Embodiment B3. The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.

[0195] Group C Example Embodiments

[0196] Example Embodiment Cl. A method by a first radio node for network configuration transfer, the method comprising: transmitting, to a second radio node, information comprising an indication that the first radio node and / or a node in communication with the first radio node is capable of receiving a type of network configuration information; and receiving, from the second radio node, the network configuration information of the type indicated in the information.

[0197] Example Embodiment C2. The method of Example Embodiment Cl, wherein the indication indicates that the first radio node and / or the node in communication with the first radio node is capable of receiving at least one of: a portion of a network configuration, and a full network configuration. Example Embodiment C3. The method of any one of Example Embodiments C 1 to C2, wherein: the indication indicates that the first radio node and / or the node in communication with the first radio node is capable of receiving a block of IES associated with a network configuration; and the network configuration information received from the second radio node comprises the block of IEs associated with the network configuration.

[0198] Example Embodiment C4. The method of any one of Example Embodiments Cl to C3, wherein the indication comprises an identifier of the type of network configuration information.

[0199] Example Embodiment C5. The method of Example Embodiment C4, wherein the identifier comprises at least one of: a name of a network configuration or a portion of a network configuration in IETF, a designated namespace associated with a network configuration or a portion of a network configuration, and a filtering criterion to be applied to a network configuration.

[0200] Example Embodiment C6. The method of any one of Example Embodiments Cl to C5, wherein the information comprises at least one of: identification information associated with the first radio node; address information associated with the first radio node; identification information associated with the node in communication with the first radio node; address information associated with the node in communication with the first radio node; and information indicating a type of the node in communication with the first radio node.

[0201] Example Embodiment C7. The method of any one of Example Embodiments Cl to C6, wherein at least one of: the first radio node is a UE, and the second radio node is a first network node.

[0202] Example Embodiment C8. The method of Example Embodiment C7, wherein at least one of: the first radio node comprises a DS-TT for transmitting the information to the second radio node, and the second radio node comprises a CTF.

[0203] Example Embodiment C9. The method of Example Embodiment C8, wherein the CTF comprises: a TSN AF, or a TSCTSF.

[0204] Example Embodiment CIO. The method of any one of Example Embodiments C8 to C9, wherein the information is transmitted to the CTF via a second network node in communication with the UE and CTF.

[0205] Example Emboidment C 11. The method of Example Embodiment CIO, wherein the second network node comprises a User Plane Function that forwards the information to the CTF.

[0206] Example Embodiment Cl 2. The method of any one of Example Embodiments C7 to CI I, comprising: receiving, from the node in communication with the first radio node, the information comprising the indication that the node in communication with the first radio node is capable of receiving a type of network configuration information, and wherein transmitting the information to the second radio node comprises forwarding the information to the second radio node.

[0207] Example Embodiment Cl 3. The method of Example Embodiment C12, comprising forwarding (e.g., transmitting) the network configuration information received from the second radio node to the node in communication with the first radio node.

[0208] Example Embodiment Cl 4. The method of any one of Example Embodiments C12 to C13, wherein the information comprises: an indication that the node in communication with the first radio node is to be exposed to the second radio node as a separate entity from the first radio node, or an indication tha the node in communication with the first radio node is not to be exposed to the second radio node as a separate entity from the first radio node.

[0209] Example Embodiment Cl 5. The method of any one of Example Embodiments C7 to Cl 4, wherein the node in communication with the first radio node comprises a router or a bridge.

[0210] Example Embodiment C16.The method of any one of Example Embodiments Cl to C6, wherein: the first radio node is a router or bridge in communication with a UE, and the second radio node is the UE in communication with the router or bridge.

[0211] Example Embodiment Cl 7. The method of Example Embodiment C16, wherein transmitting the information to the second radio node comprises transmitting the information to a DS-TT of the second radio node for forwarding to a third radio node.

[0212] Example Embodiment Cl 8. The method of any one of Example Embodiments C 16 to C 17, wherein the information comprises: an indication that the first radio node is to be exposed to the third radio node as a separate entity from the second radio node, or an indication that the first radio node is not to be exposed to the third radio node as a separate entity from the second radio node.

[0213] Example Embodiment C19.The method of any one of Example Embodiments Cl to C6, wherein at least one of: the first radio node is a first network node, and the second radio node is a second network node.

[0214] Example Embodiment C20.The method of Example Embodiments C19, wherein at least one of: the first radio node is a base station and / or a gNB, and the second radio node is a controller.

[0215] Example Embodiment C21.The method of any one of Example Embodiments C19 to C20, wherein the first radio node comprises a NW-TT for receiving the information from the node in communication with the first radio node.

[0216] Example Embodiment C22.The method of any one of Example Embodiments C19 to C21, comprising: receiving, from the node in communication with the first radio node, the information comprising the indication that the node in communication with the first radio node is capable of receiving a type of network configuration information, and wherein transmitting the information to the second radio node comprises forwarding the information to the second network node.

[0217] Example Embodiment C23.The method of any one of Example Embodiments C19 to C22, wherein the node in communication with the first radio node comprises at least one of: a router or a bridge in communication with the first radio node, an internal router node function within a UPF, and a router node function within the NW-TT.

[0218] Example Embodiment C24.The method of any one of Example Embodiments C23, wherein the information comprises: an indication that the node is to be exposed as a separate entity from the first radio node, or an indication that the node is not to be exposed as a separate entity from the first radio node.

[0219] Example Embodiment C25.The method of any one of Example Embodiments C23 to C24, wherein the information comprises an address or identifier of the node in communication with the first radio node and / or an indication of a type of node in communication with the first radio node.

[0220] Example Embodiment C26.The method of any one of Example Embodiments C19 to C21, wherein the node in communication with the first radio node comprises a User Equipment (UE) in communication with the first radio node.

[0221] Example Embodiment C27.The method of Example Embodiment C26, wherein the information is associated with a router or bridge in communication with the UE.

[0222] Example Embodiment C28.The method of any one of Example Embodiments C27, wherein the information comprises: an indication that the router or bridge is to be exposed as a separate entity from the UE, or an indication that the router or bridge is not to be exposed as a separate entity from the UE.

[0223] Example Embodiment C29.The method of any one of Example Embodiments C27 to C28, wherein the information comprises an address or identifier of the node in communication with the UE and / or an indication of a type of node in communication with the UE.

[0224] Example Embodiment C30.The method of any one of Example Embodiments Cl to C29, comprising at least one of: transmitting, to the second radio node, a response message indicating receipt of the network configuration information; updating a configuration of the first radio node based on the network configuration information received from the second radio node; receiving, from the node in communication with the first radio node, an updated network configuration; transmitting, to the second radio node, an updated configuration of the first radio node and / or the node in communication with the first radio node; and transmitting, to the node in communication with the first radio node, the network configuration information received from the second radio node.

[0225] Example Embodiment C31.The method of any one of Example Embodiments Cl to C30, wherein the network configuration information is received in a PMIC or a UMIC.

[0226] Example Embodiment C32.The method of any one of Example Embodiments Cl to C31, wherein the information transmitted to the second radio node is transmitted in a PMIC or a UMIC.

[0227] Example Embodiment C33.The method of any one of Example Embodiments Cl to C32, wherein the information comprises at least one of: at least one parameter and / or a set of parameters associated with a configuration of the node in communication with the first radio node; information indicating at least one capability of the node in communication with the first radio node; software and / or software updates for the node in communication with the first radio node; firmware and / or firmware updates for the node in communication with the first radio node; information for installing software modules on the node in communication with the first radio node; information for uninstalling software modules on the node in communication with the first radio node; information associated with status and / or performance monitoring of the node in communication with the first radio node; and diagnostics information associated with the node in communication with the first radio node.

[0228] Example Embodiment C34.The method of any one of Example Embodiments Cl to C33, further comprising : providing user data; and forwarding the user data to a host via the transmission to the network node.

[0229] Example Embodiment C35.A user equipment comprising processing circuitry configured to perform any of the methods of Example Embodiments Cl to C33.

[0230] Example Embodiment C36. A user equipment configured to perform any of the methods of Example Embodiments Cl to C33.

[0231] Example Embodiment C37.A wireless device comprising processing circuitry configured to perform any of the methods of Example Embodiments Cl to C33.

[0232] Example Embodiment C38.The method of any one of Example Embodiments C31 to C33, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.

[0233] Example Embodiment C39.A network node comprising processing circuitry configured to perform any of the methods of Example Embodiments Cl to C33.

[0234] Example Embodiment C40.A network node configured to perform any of the methods of Example Embodiments Cl to C33.

[0235] Example Embodiment C41. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Cl to C33.

[0236] Example Embodiment C42. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Cl to C33. Example Embodiment C43. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments Cl to C33.

[0237] Group D Example Embodiments

[0238] Example Embodiment DI. A method by a second radio node for network configuration transfer, the method comprising: receiving, from a first radio node, information comprising an indication that the first radio node and / or a node in communication with the first radio node is capable of receiving a type of network configuration information; and transmitting, to the first radio node, the network configuration information of the type indicated in the information.

[0239] Example Embodiment D2. The method of Example Embodiment DI, wherein the indication indicates that the first radio node and / or the node in communication with the first radio node is capable of receiving at least one of: a portion of a network configuration, and a full network configuration.

[0240] Example Embodiment D3. The method of any one of Example Embodiments D 1 to D2, wherein: the indication indicates that the first radio node and / or the node in communication with the first radio node is capable of receiving a block of IES associated with a network configuration; and the network configuration information transmitted to the first radio node comprises the block of IEs associated with the network configuration.

[0241] Example Embodiment D4. The method of any one of Example Embodiments DI to D3, wherein the indication comprises an identifier of the type of network configuration information.

[0242] Example Embodiment D5. The method of Example Embodiment D4, wherein the identifier comprises at least one of: a name of a network configuration or a portion of a network configuration in IETF, a designated namespace associated with a network configuration or a portion of a network configuration, and a filtering criterion to be applied to a network configuration.

[0243] Example Embodiment D6. The method of any one of Example Embodiments DI to D5, wherein the information comprises at least one of: identification information associated with the first radio node; address information associated with the first radio node; identification information associated with the node in communication with the first radio node; address information associated with the node in communication with the first radio node; and information indicating a type of the node in communication with the first radio node.

[0244] Example Embodiment D7. The method of any one of Example Embodiments DI to D4, wherein at least one of: the first radio node is a UE, and the second radio node is a first network node.

[0245] Example Embodiment D8. The method of Example Embodiment D7, wherein at least one of: the first radio node comprises a DS-TT, and the second radio node comprises a CTF.

[0246] Example Embodiment D9. The method of Example Embodiment D8, wherein the CTF comprises: a TSN AF, or a TSCTSF.

[0247] Example Embodiment DIO. The method of any one of Example Embodiments D8 to D9, wherein the information is received by the CTF via a second network node in communication with the UE and CTF.

[0248] Example Embodiment Dl l. The method of Example Embodiment DIO, wherein the second network node comprises a User Plane Function that receives the information from the UE and forwards the information to the CTF.

[0249] Example Embodiment D 12. The method of any one of Example Embodiments D7 to DI 1, comprising: forwarding the information to a controller.

[0250] Example Embodiment D13. The method of Example Embodiment D12, comprising receiving the network configuration information from the controller.

[0251] Example Embodiment D 14. The method of any one of Example Embodiments D 11 to D12, wherein the controller comprises a second network node.

[0252] Example Embodiment D 15. The method of any one of Example Embodiments D 11 to D12, wherein the controller is within the second radio node.

[0253] Example Embodiment DI 6. The method of any one of Example Embodiments D 13 to D15, comprising determining that the network configuration information received from the controller is of the type indicated in the information from the first radio node, and wherein the network configuration information is forwarded to the first radio node based on determining that the network configuration information is of the type indicated in the information.

[0254] Example Embodiment DI 7. The method of any one of Example Embodiments D 14 to D15, comprising determining that a portion of a network configuration information received from the controller is of the type indicated in the information from the first radio node, and wherein only the portion of the network configuration information that is of the type indicated is forwarded to the first radio node.

[0255] Example Embodiment D18. The method of Example Embodiment DI 7, comprising filtering out at least another portion of the network configuration information that is not of the type indicated in the information, and wherein the network configuration information that is forwarded to the first radio node excludes the other portion of the network configuration information that is not of the type indicated in the information. Example Embodiment DI 9. The method of any one of Example Embodiments D 12 to DI 8, wherein the information comprises: an indication that the node in communication with the first radio node is to be exposed to the second radio node as a separate entity from the first radio node, or an indication tha the node in communication with the first radio node is not to be exposed to the second radio node as a separate entity from the first radio node.

[0256] Example Embodiment D20. The method of any one of Example Embodiments D7 to DI 9, wherein the node in communication with the first radio node comprises a router or a bridge.

[0257] Example Embodiment D21. The method of any one of Example Embodiments D 1 to D6, wherein: the first radio node is a router or bridge in communication with a UE, and the second radio node is the UE in communication with the router or bridge.

[0258] Example Embodiment D22. The method of Example Embodiment D21, wherein receiving the information from the first radio node comprises receiving the information by a DS-TT of the second radio node for forwarding to a third radio node.

[0259] Example Embodiment D23. The method of any one of Example Embodiments D21 to D22, wherein the information comprises: an indication that the first radio node is to be exposed to the third radio node as a separate entity from the second radio node, or an indication that the first radio node is not to be exposed to the third radio node as a separate entity from the second radio node.

[0260] Example Embodiment D24. The method of any one of Example Embodiments DI to D6, wherein at least one of: the first radio node is a first network node, and the second radio node is a second network node.

[0261] Example Embodiment D25. The method of Example Embodiments D24, wherein at least one of: the first radio node is a base station and / or a gNB, and the second radio node is a controller.

[0262] Example Embodiment D26. The method of any one of Example Embodiments D24 to D25, wherein the first radio node comprises aNW-TT for transmitting the information to the controller.

[0263] Example Embodiment D27. The method of any one of Example Embodiments D24 to D26, comprising determining that a network configuration is of the type indicated in the information from the first radio node, and wherein the network configuration information is transmitted to the first radio node based on determining that the network configuration is of the type indicated in the information.

[0264] Example Embodiment D28. The method of any one of Example Embodiments D24 to D26, comprising determining that a portion of a network configuration is of the type indicated in the information from the first radio node, and wherein the network configuration information is transmitted to the first radio node based on determining that the portion of the network configuration is of the type indicated in the information. Example Embodiment D29. The method of Example Embodiment D28, comprising filtering out at least a portion of the network configuration that is not of the type indicated in the information, and wherein the network configuration information tha tis transmitted to the first radio node excludes the portion of the network configuration that is not of the type indicated in the information.

[0265] Example Embodiment D30. The method of any one of Example Embodiments D24 to D29, wherein the node in communication with the first radio node comprises at least one of: a router or a bridge in communication with the first radio node, an internal router node function within a UPF, and a router node function within the NW-TT.

[0266] Example Embodiment D31. The method of any one of Example Embodiments D30, wherein the information comprises: an indication that the node is to be exposed as a separate entity from the first radio node, or an indication that the node is not to be exposed as a separate entity from the first radio node.

[0267] Example Embodiment D32. The method of any one of Example Embodiments D30 to D31, wherein the information comprises an address or identifier of the node in communication with the first radio node and / or an indication of a type of node in communication with the first radio node.

[0268] Example Embodiment D33. The method of any one of Example Embodiments D24 to D32, wherein the node in communication with the first radio node comprises a User Equipment (UE) in communication with the first radio node.

[0269] Example Embodiment D34. The method of Example Embodiment D33, wherein the information is associated with a router or bridge in communication with the UE.

[0270] Example Embodiment D35. The method of any one of Example Embodiments D34, wherein the information comprises: an indication that the router or bridge is to be exposed as a separate entity from the UE, or an indication that the router or bridge is not to be exposed as a separate entity from the UE.

[0271] Example Embodiment D36. The method of any one of Example Embodiments D34 to D35, wherein the information comprises an address or identifier of the node in communication with the UE and / or an indication of a type of node in communication with the UE.

[0272] Example Embodiment D37. The method of any one of Example Embodiments DI to D36, comprising at least one of: receiving, from the first radio node, a response message indicating receipt of the network configuration information; receiving an updated network configuration; and receiving, from the first radio node, an updated configuration of the first radio node and / or the node in communication with the first radio node.

[0273] Example Embodiment D38. The method of any one of Example Embodiments DI to D37, wherein the network configuration information is transmitted in a PMIC or a UMIC.

[0274] Example Embodiment D39. The method of any one of Example Embodiments DI to D38, wherein the information received from the first radio node is received in a PMIC or a UMIC.

[0275] Example Embodiment D40. The method of any one of Example Embodiments DI to D39, wherein the information comprises at least one of: at least one parameter and / or a set of parameters associated with a configuration of the node in communication with the first radio node; information indicating at least one capability of the node in communication with the first radio node; software and / or software updates for the node in communication with the first radio node; firmware and / or firmware updates for the node in communication with the first radio node; information for installing software modules on the node in communication with the first radio node; information for uninstalling software modules on the node in communication with the first radio node; information associated with status and / or performance monitoring of the node in communication with the first radio node; and diagnostics information associated with the node in communication with the first radio node.

[0276] Example Embodiment D41. The method of any one of Example Embodiments D 1 to D40, further comprising : providing user data; and forwarding the user data to a host via the transmission to the network node.

[0277] Example Embodiment D42. A user equipment comprising processing circuitry configured to perform any of the methods of Example Embodiments DI to D40.

[0278] Example Embodiment D43. A user equipment configured to perform any of the methods of Example Embodiments DI to D40.

[0279] Example Embodiment D44. A wireless device comprising processing circuitry configured to perform any of the methods of Example Embodiments DI to D40.

[0280] Example Embodiment D45. The method of any one of Example Embodiments D 1 to D40, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.

[0281] Example Embodiment D46. A network node comprising processing circuitry configured to perform any of the methods of Example Embodiments DI to D40.

[0282] Example Embodiment D47. A network node configured to perform any of the methods of Example Embodiments DI to D40.

[0283] Example Embodiment D48. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments DI to D40.

[0284] Example Embodiment D49. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments DI to D40. Example Embodiment D50. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments DI to D40.

[0285] Group E Example Embodiments

[0286] Example Embodiment El. A user equipment for network configuration transfer, the UE comprising: processing circuitry configured to perform any of the steps of any of the Group A, C, and D Example Embodiments; and power supply circuitry configured to supply power to the processing circuitry.

[0287] Example Embodiment E2. A network node for network configuration transfer, the network node comprising: processing circuitry configured to perform any of the steps of any of the Group B, C, and D Example Embodiments; power supply circuitry configured to supply power to the processing circuitry.

[0288] Example Embodiment E3. A user equipment (UE) for network configuration transfer, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A, C, and D Example Embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

[0289] Example Embodiment E4. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A, C, and D Example Embodiments to receive the user data from the host.

[0290] Example Embodiment E5. The host of the previous Example Embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.

[0291] Example Embodiment E6. The host of the previous 2 Example Embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0292] Example Embodiment E7. A method implemented by a host operating in a communication system that further includes a network node and a UE, the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations of any of the Group A embodiments to receive the user data from the host.

[0293] Example Emboidment E8. The method of the previous Example Embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.

[0294] Example Embodiment E9. The method of the previous Example Embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

[0295] Example Emboidment El 0. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A, C, and D Example Embodiments to transmit the user data to the host.

[0296] Example Emboidment El l. The host of the previous Example Embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.

[0297] Example Embodiment El 2. The host of the previous 2 Example Embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0298] Example Embodiment El 3. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A, C, and D Example Embodiments to transmit the user data to the host. Example Embodiment El 4. The method of the previous Example Embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.

[0299] Example Embodiment El 5. The method of the previous Example Embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

[0300] Example Embodiment El 6. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B, C, and D Example Embodiments to transmit the user data from the host to the UE.

[0301] Example Embodiment E17.The host of the previous Example Embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.

[0302] Example Embodiment El 8. A method implemented in a host configured to operate in a communication system that further includes a network node and a UE, the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B, C, and D Example Embodiments to transmit the user data from the host to the UE.

[0303] Example Embodiment El 9. The method of the previous Example Embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.

[0304] Example Emboidment E20.The method of any of the previous 2 Example Embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.

[0305] Example Embodiment E21. A communication system configured to provide an over-the- top service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B, C, and D Example Embodiments to transmit the user data from the host to the UE.

[0306] Example Embodiment E22. The communication system of the previous Example Embodiment, further comprising: the network node; and / or the user equipment.

[0307] Example Embodiment E23. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B, C, and D Example Embodiments to receive the user data from a user equipment (UE) for the host.

[0308] Example Embodiment E24. The host of the previous 2 Example Embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0309] Example Embodiment E25. The host of the any of the previous 2 Example Embodiments, wherein the initiating receipt of the user data comprises requesting the user data.

[0310] Example Embodiment E26. A method implemented by a host configured to operate in a communication system that further includes a network node and a UE, the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of the Group B, C, and D Example Embodiments to receive the user data from the UE for the host.

[0311] Example Embodiment E27. The method of the previous Example Embodiment, further comprising at the network node, transmitting the received user data to the host.

Claims

CLAIMS1. A method (1300) by a first node (110) for network configuration transfer, the method comprising: transmitting (1302), to a second node (108), information comprising an identifier of a type of network configuration information that the first node and / or a node in communication with the first node is capable of receiving; and receiving (1304), from the second node, the network configuration information of the type associated with the identifier in the information.

2. The method of Claim 1, wherein the information comprises an indication that the first node and / or the node in communication with the first node is capable of receiving at least one of: a portion of a network configuration, and a full network configuration.

3. The method of any one of Claims 1 to 2, wherein: the information comprises an indication that the first node and / or the node in communication with the first node is capable of receiving a block of Information Elements, IES, associated with the network configuration; and the network configuration information received from the second radio node comprises the block of IEs associated with the network configuration.

4. The method of any one of Claims 1 to 3, wherein the identifier comprises at least one of: a name of the network configuration or the portion of the network configuration, a designated namespace associated with the network configuration or the portion of the network configuration, and a filtering criterion to be applied to the network configuration.

5. The method of any one of Claims 1 to 4, wherein the information comprises at least one of: identification information associated with the first node; address information associated with the first node; identification information associated with the node in communication with the first node; address information associated with the node in communication with the first node; and information indicating a type of the node in communication with the first node.

6. The method of any one of Claims 1 to 5, wherein:the first node comprises a Device-side TSN Translator, DS-TT, (110a) for transmitting the information to the second node, or the first node comprises a Network-side TSN Translator, NW-TT, (110b) for receiving the information from the node in communication with the first node.

7. The method of any one of Claims 1 to 6, wherein the second node comprises a Configuration Transfer Function, CTF, (108) comprising a Time Sensitive Network Application Function, TSN AF, or Time Sensitive Communication Time Synchronization Function, TSCTSF.

8. The method of Claim 7, wherein the information is transmitted to the CTF by the first node on behalf of the node in communication with the first node.

9. The method of any one of Claims 1 to 8, wherein the node in communication with the first node comprises at least one of: a router in communication with the first node, a bridge in communication with the first node, an internal router node function within a User Plane Function, UPF, and a router node function.

10. The method of any one of Claims 1 to 9, comprising: receiving, from the node in communication with the first node, the information comprising the identifier of the type of network configuration information that the node in communication with the first node is capable of receiving, and wherein transmitting the information to the second node comprises forwarding the information to the second node.

11. The method of any one of Claims 1 to 10, comprising forwarding the network configuration information received from the second node to the node in communication with the first node.

12. The method of any one of Claims 1 to 11, wherein the information comprises: an indication that the node in communication with the first node is to be exposed to the second node as a separate entity from the first node, or an indication that the node in communication with the first node is not to be exposed to the second node as a separate entity from the first node13. The method of any one of Claims 1 to 12, comprising: transmitting, to the second node, a response message indicating receipt of the network configuration information.

14. The method of any one of Claims 1 to 13, comprising at least one of:updating a configuration of the first node based on the network configuration information received from the second node; receiving, from the node in communication with the first radio node, an updated network configuration; and transmitting, to the second radio node, an updated configuration of the first radio node and / or the node in communication with the first radio node.

15. The method of any one of Claims 1 to 14, wherein: the network configuration information is received in a Port Management Information Container, PMIC, or a User-plane Node Management Information Container, UMIC, and / or the information transmitted to the second radio node is transmitted in the PMIC or the UMIC.

16. A method (1400) by a second node (108) for network configuration transfer, the method comprising: receiving (1402), from a first node (110), information comprising an identifier of a type of network configuration information that the first node and / or a node in communication with the first node is capable of receiving; and transmitting (1404), to the first node, the network configuration information of the type associated with the identifier in the information.

17. The method of Claim 16, wherein the information comprises an indication that the first node and / or the node in communication with the first node is capable of receiving at least one of: a portion of a network configuration, and a full network configuration.

18. The method of any one of Claims 16 to 17, wherein: the information comprises an indication that the first node and / or the node in communication with the first node is capable of receiving a block of Information Elements, IES, associated with a network configuration; and the network configuration information transmitted to the first node comprises the block of IEs associated with the network configuration.

19. The method of any one of Claims 16 to 18, wherein the identifier comprises at least one of: a name of the network configuration or the portion of the network configuration, a designated namespace associated with the network configuration or the portion of the network configuration, anda filtering criterion to be applied to the network configuration.

20. The method of any one of Claims 16 to 19, wherein the information comprises at least one of: identification information associated with the first node; address information associated with the first node; identification information associated with the node in communication with the first node; address information associated with the node in communication with the first node; and information indicating a type of the node in communication with the first node.

21. The method of any one of Claims 16 to 20, wherein at least one of: the first node comprises a Device-side TSN Translator, DS-TT, (110a) or the first node comprises a Network-side TSN Translator, NW-TT, (110b) for receiving the information from the node in communication with the first node.

22. The method of any one of Claims 16 to 21, wherein the second radio node comprises a Configuration Transfer Function, CTF, (108) comprising a Time Sensitive Network Application Function, TSN AF, or Time Sensitive Communication Time Synchronization Function, TSCTSF.

23. The method of Claim 22, wherein the information is received by the CTF via the first node on behalf of the node in communication with the first node.

24. The method of any one of Claims 16 to 23, wherein the node in communication with the first node comprises at least one of: a router in communication with the first node, a bridge in communication with the first node, an internal router node function within a User Plane Function, UPF, and a router node function.

25. The method of any one of Claims 16 to 24, comprising: forwarding the information to a controller; and receiving the network configuration information from the controller.

26. The method of Claim 25, wherein the controller is external to the second node.

27. The method Claim 25, wherein the controller is within the second node.

28. The method of any one of Claims 25 to 27, comprising determining that the network configuration information received from the controller is of the type associated with the identifier in the information from the first node, and wherein the network configuration information isforwarded to the first node based on determining that the network configuration information is of the type associated with the identifier in the information.

29. The method of any one of Claims 25 to 27, comprising: determining that a portion of the network configuration information received from the controller is of the type associated with the identifier in the information from the first node, and filtering out at least another portion of the network configuration information that is not of the type associated with the identifier in the information from the first node, and wherein only the portion of the network configuration information that is of the type associated with the identifier is forwarded to the first node.

30. The method of any one of Claims 16 to 29, wherein the information comprises: an indication that the node in communication with the first node is to be exposed to the second node as a separate entity from the first node, or an indication tha the node in communication with the first node is not to be exposed to the second node as a separate entity from the first node.

31. The method of any one of Claims 16 to 30, comprising at least one of: receiving, from the first node, a response message indicating receipt of the network configuration information; and receiving, from the first node, an updated configuration of the first node and / or the node in communication with the first node.

32. The method of any one of Claims 16 to 31, wherein: the network configuration information is transmitted in a Port Management Information Container, PMIC, or a User-plane Node Management Information Container, UMIC, and / or the information received from the first node is received in a PMIC or UMIC.

33. A method by a controller ( 102) for network configuration transfer, the method comprising : receiving (1502), from a second node (108), information comprising an identifier of atype of network configuration information that a first node (110) and / or a node in communication with the first node is capable of receiving; and transmitting (1504), to the second node, the network configuration information of the type associated with the identifier in the information.

34. The method of Claim 33, comprising determining that a network configuration is of the type associated with the identifier of the type of network configuration information that the first node and / or the node in communication with the first node is capable of receiving, and whereinthe network configuration information is transmitted to the second node based on determining that the network configuration is of the type associated with the identifier in the information.

35. The method of any one of Claims 33 to 34, comprising: determining that a portion of a network configuration is of the type associated with the identifier of the type of network configuration information that the first node and / or the node in communication with the first node is capable of receiving, filtering out at least a portion of the network configuration that is not of the type associated with the identifier, and wherein the network configuration information transmitted to the second node includes the portion of the network configuration that is of the type associated with the identifier and excludes the portion of the network configuration that is not of the type associated with the identifier.

36. The method of any one of Claims 33 to 35 , wherein the information comprise s an indication that the first node and / or the node in communication with the first node is capable of receiving at least one of: a portion of a network configuration, and a full network configuration.

37. The method of any one of Claims 33 to 35, wherein: the information comprises an indication that the first node and / or the node in communication with the first node is capable of receiving a block of Information Elements, IES, associated with a network configuration; and the network configuration information transmitted to the first node comprises the block of IEs associated with the network configuration.

38. The method of any one of Claims 33 to 37, wherein the identifier comprises at least one of: a name of the network configuration or the portion of the network configuration, a designated namespace associated with the network configuration or the portion of the network configuration, and a filtering criterion to be applied to the network configuration.

39. The method of any one of Claims 33 to 38, wherein the information comprises at least one of: identification information associated with the first node; address information associated with the first node; identification information associated with the node in communication with the first node;address information associated with the node in communication with the first node; and information indicating a type of the node in communication with the first node.

40. The method of any one of Claims 33 to 39, wherein at least one of: the first node comprises a Device-side TSN Translator, DS-TT, (110a) or a Network-side TSN Translator, NW-TT (110b), and the second radio node comprises a Configuration Transfer Function, CTF, (108) comprising a Time Sensitive Network Application Function, TSN AF, or Time Sensitive Communication Time Synchronization Function, TSCTSF.

41. The method of any one of Claims 33 to 40, wherein the node in communication with the first node comprises at least one of: a router in communication with the first node, a bridge in communication with the first node, an internal router node function within a User Plane Function, UPF, and a router node function.

42. The method of any one of Claims 33 to 41, wherein the controller is external to the second node.

43. The method of any one of Claims 33 to 41, wherein the controller is within the second node.

44. The method of any one of Claims 33 to 43, wherein: the network configuration information is transmitted in a Port Management Information Container, PMIC, or a User-plane Node Management Information Container, UMIC, and / or the information received from the first node is received in a PMIC or UMIC.

45. A first radio node (110) for network configuration transfer, the first radio node configured to: transmit, to a second node (108), information comprising an identifier of a type of network configuration information that the first node and / or a node in communication with the first node is capable of receiving; and receive from the second node, the network configuration information of the type associated with the identifier in the information.

46. The first radio node of Claim 45, configured to perform any of the methods of Claims 2 to 15.

47. A second radio node (108) for network configuration transfer, the second radio node configured to: receive, from a first node (110), information comprising an identifier of a type of network configuration information that the first node and / or a node in communication with the first node is capable of receiving; and transmit, to the first node, the network configuration information of the type associated with the identifier in the information.

48. The second radio node of Claim 47, configured to perform any of the methods of Claims 17 to 32.

49. A controller (102) for network configuration transfer, the controller configured to: receive, from a second node (108), information comprising an identifier of a type of network configuration information that a first node (110) and / or a node in communication with the first node is capable of receiving; and transmit, to the second node, the network configuration information of the type associated with the identifier in the information.

50. The controller of Claim 49, configured to perform any of the methods of Claims 34 to 44.

Images