External IP interface management in 5GS IP router nodes

Abstract

Embodiments of the present disclosure relate to external IP interface management in an IP router node. According to one aspect of the present disclosure, a device sends an indication regarding a device-side IP interface of an IP router node to a first core network element. The device then receives IP address information for the device-side IP interface from the first core network element or the second core network element. In this way, an external IP interface on the device side is implemented.

Description

Technical Field

[0001] Embodiments of the present disclosure relate generally to the field of telecommunications, and in particular to methods, devices, apparatus, and computer-readable media for external Internet Protocol (IP) interface management in a fifth generation (5G) system (5GS) as an IP router node. Background Art

[0002] As is known, 5GS can operate as a DetNet node in a deterministic network (DetNet) domain and defines common enablers for time-sensitive networking (TSN) and local time-sensitive communication (TSC). 5GS, as one of the DetNet nodes in the DetNet domain, needs to expose all its externally visible interfaces to the DetNet controller. On the user equipment (UE) side, when a device with a device-side TSN converter (DS-TT) joins a 5GSDetNet node, the DS-TT side interface of the device becomes the external IP interface of the 5GSDetNet node. However, the management of such external IP interfaces of the 5GSDetNet node is still imperfect and requires further development. Summary of the invention

[0003] In general, example embodiments of the present disclosure provide a scheme for external IP interface management in a 5GS IP router node.

[0004] In a first aspect, a device is provided. The device includes at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, cause the device to: send an indication of a device-side Internet Protocol interface of an Internet Protocol router node to a first core network element; and receive Internet Protocol address information for the device-side Internet Protocol interface from the first core network element or a second core network element.

[0005] In a second aspect, a first core network element is provided. The first core network element comprises at least one processor; and at least one memory comprising computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, enable the first core network element to: receive an indication of a device-side Internet Protocol interface of an Internet Protocol router node from a device; and send Internet Protocol address information of the device-side Internet Protocol interface to the device.

[0006] In a third aspect, a first core network element is provided. The first core network element comprises at least one processor; and at least one memory comprising computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, enable the first core network element to: receive an indication of a device-side Internet Protocol interface of an Internet Protocol router node from a device; and send an interface number for the device-side Internet Protocol interface and an identifier of the Internet Protocol router node to a second core network element for allocation of Internet Protocol address information of the device-side Internet Protocol interface.

[0007] In a fourth aspect, a second core network element is provided. The second core network element comprises at least one processor; and at least one memory, comprising computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, enable the second core network element to: receive an interface number of a device-side Internet protocol interface for an Internet protocol router node and an identifier of the Internet protocol router node from the first core network element, the interface number corresponding to a protocol data unit session; and send Internet protocol address information for the device-side Internet protocol interface to the device.

[0008] In a fifth aspect, a second core network element is provided. The second core network element comprises at least one processor; and at least one memory comprising computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, enable the second core network element to: receive Internet protocol address information of a device-side Internet protocol interface of an Internet protocol router node and an interface number of the device-side Internet protocol interface corresponding to a protocol data unit session from the first core network element; generate information of the Internet protocol router node, the information comprising an identifier of the Internet protocol router node, the interface number and the Internet protocol address information; and expose the information of the Internet protocol router node to a controller.

[0009] In a sixth aspect, a third core network element is provided. The third core network element includes at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, enable the third core network element to: receive a request for obtaining at least one of Internet Protocol address information or Internet Protocol configuration information for a device-side Internet Protocol interface of an Internet Protocol router node from a first core network element or from a second core network element; and send at least one of the Internet Protocol address information or Internet Protocol configuration information to the first core network element or to the second core network element.

[0010] In a seventh aspect, a method of communication is provided, comprising: at a device, sending an indication of a device-side Internet Protocol interface of an Internet Protocol router node to a first core network element; and receiving Internet Protocol address information for the device-side Internet Protocol interface from the first core network element or a second core network element.

[0011] In an eighth aspect, a communication method is provided, comprising: receiving, at a first core network element, an indication of a device-side Internet Protocol interface of an Internet Protocol router node from a device; and sending Internet Protocol address information of the device-side Internet Protocol interface to the device.

[0012] In a ninth aspect, a method of communication is provided, the method comprising: receiving, at a first core network element, an indication of a device-side Internet Protocol interface of an Internet Protocol router node from a device; and sending, to a second core network element, an interface number for the device-side Internet Protocol interface, an identifier of the Internet Protocol router node, and an identifier of a protocol data unit session, so that the second core network element allocates Internet Protocol address information of the device-side Internet Protocol interface.

[0013] In a tenth aspect, a method of communication is provided, comprising: receiving, at a second core network element, an interface number of a device-side Internet Protocol interface for an Internet Protocol router node and an identifier of the Internet Protocol router node from a first core network element, the interface number corresponding to a protocol data unit session; and sending Internet Protocol address information for the device-side Internet Protocol interface to the first core network element.

[0014] In an eleventh aspect, a method of communication is provided. The method includes: receiving, at a second core network network element, Internet protocol address information for a device-side Internet protocol interface of an Internet protocol router node and an interface number of the device-side Internet protocol interface corresponding to a protocol data unit session from a first core network network element; generating information of the Internet protocol router node, the information including an identifier of the Internet protocol router node, the interface number, and the Internet protocol address information; and exposing the information of the Internet protocol router node to a controller.

[0015] In a twelfth aspect, a communication method is provided. The method includes: receiving, at a third core network element, a request for obtaining at least one of Internet Protocol address information or Internet Protocol configuration information of a device-side Internet Protocol interface of an Internet Protocol router node from a first core network element or from a second core network element via the first core network element; and sending at least one of the Internet Protocol address information or Internet Protocol configuration information to the first core network element or to the second core network element via the first core network element.

[0016] In a thirteenth aspect, a communication apparatus is provided. The method includes: a component for sending an indication of a device-side Internet Protocol interface of an Internet Protocol router node to a first core network element at a device; and a component for receiving Internet Protocol address information for the device-side Internet Protocol interface from the first core network element or a second core network element.

[0017] In a fourteenth aspect, a communication apparatus is provided. The method includes: a component for receiving an indication of a device-side Internet Protocol interface of an Internet Protocol router node from a device at a first core network element; and a component for sending Internet Protocol address information of the device-side Internet Protocol interface to the device.

[0018] In a fifteenth aspect, a communication apparatus is provided. The method includes: a component for receiving an indication of a device-side Internet Protocol interface of an Internet Protocol router node from a device at a first core network element; and a component for sending an interface number for the device-side Internet Protocol interface, an identifier of the Internet Protocol router node, and an identifier of a protocol data unit session to a second core network element, so that the second core network element allocates Internet Protocol address information of the device-side Internet Protocol interface.

[0019] In a sixteenth aspect, a communication apparatus is provided. The method includes: a component for receiving, at a second core network element, from a first core network element, an interface number of a device-side Internet Protocol interface for an Internet Protocol router node and an identifier of the Internet Protocol router node, the interface number corresponding to a protocol data unit session; and a component for sending Internet Protocol address information for the device-side Internet Protocol interface to the first core network element.

[0020] In a seventeenth aspect, a communication apparatus is provided. The method includes: a component for receiving, at a second core network network element, from a first core network network element, Internet protocol address information for a device-side Internet protocol interface of an Internet protocol router node and an interface number of the device-side Internet protocol interface corresponding to a protocol data unit session; a component for generating information of the Internet protocol router node, the information including an identification of the Internet protocol router node, the interface number and the Internet protocol address information; and a component for exposing the information of the Internet protocol router node to a controller.

[0021] In a nineteenth aspect, a communication apparatus is provided. The method includes: a component for receiving, at a third core network element, a request for obtaining at least one of Internet Protocol address information or Internet Protocol configuration information for a device-side Internet Protocol interface of an Internet Protocol router node from a first core network element or from a second core network element via the first core network element; and a component for sending at least one of the Internet Protocol address information or Internet Protocol configuration information to the first core network element or to the second core network element via the first core network element.

[0022] In a twentieth aspect, a non-transitory computer-readable medium comprising program instructions is provided, wherein the program instructions are used to cause an apparatus to execute the method according to any one of the seventh to twelfth aspects.

[0023] It should be understood that the summary is not intended to identify the key or essential features of the embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Some example embodiments will now be described with reference to the accompanying drawings, in which:

[0025] Figure 1 An example DetNet architecture is shown in which embodiments of the present disclosure may be implemented;

[0026] Figure 2 shows an example 5GSDetNet node architecture in which embodiments of the present disclosure may be implemented;

[0027] Figure 3A An example IP architecture model of a device acting as a device-side IP interface of a 5G SDetNet node is shown in which embodiments of the present disclosure may be implemented;

[0028] Figure 3B An example IP architecture model of a device acting as a network-side IP interface of a 5G SDetNet node is shown in which embodiments of the present disclosure may be implemented;

[0029] Figure 4 A diagram illustrating a communication process according to some embodiments of the present disclosure is shown;

[0030] Figure 5 shows a diagram illustrating another communication process according to some embodiments of the present disclosure;

[0031] Figure 6 A flowchart illustrating an example method implemented at a device according to some embodiments of the present disclosure;

[0032] Figure 7 A flowchart showing an example method implemented at a first core network element according to some embodiments of the present disclosure;

[0033] Figure 8 A flowchart showing an example method implemented at a first core network element according to some embodiments of the present disclosure;

[0034] Fig. 9 A flowchart showing an example method implemented at a second core network element according to some embodiments of the present disclosure is shown;

[0035] Fig.10 A flowchart showing an example method implemented at a second core network element according to some embodiments of the present disclosure is shown;

[0036] Fig.11 A flowchart showing another example method implemented at a third core network element according to some embodiments of the present disclosure is shown;

[0037] Fig.12 shows a simplified block diagram of a device suitable for implementing an embodiment of the present disclosure; and

[0038] Fig.13 A block diagram of an example computer-readable medium is shown in accordance with some embodiments of the present disclosure.

[0039] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0040] The principles of the present disclosure will now be described with reference to some example embodiments. It should be understood that these embodiments are described for illustrative purposes only and to help those skilled in the art understand and implement the present disclosure without implying any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in various ways different from the ways described below.

[0041] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art.

[0042] References in this disclosure to "one embodiment," "an embodiment," "an example embodiment," etc., indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it is considered to be within the knowledge of those skilled in the art to affect such feature, structure, or characteristic in conjunction with other embodiments (whether or not explicitly described).

[0043] It should be understood that although the terms "first" and "second", etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element without departing from the scope of the example embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0044] The terms used herein are only used for the purpose of describing specific embodiments and are not intended to limit the exemplary embodiments. As used herein, the singular forms "a", "an", and "the" are also intended to include the plural forms, unless the context clearly indicates otherwise. It will also be understood that the terms "comprise", "include", "have", "have", "include" and / or "comprising" when used herein specify the presence of the features, elements and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components and / or combinations thereof.

[0045] As used in this application, the term "circuitry" may refer to one or more or all of the following:

[0046] (a) only hardware circuit implementation (e.g., only implementation in analog and / or digital circuitry) and

[0047] (b) a combination of hardware circuitry and software, such as (where applicable):

[0048] (i) a combination of analog and / or digital hardware circuitry and software / firmware, and

[0049] (ii) any portion of a hardware processor with software (including a digital signal processor, software, and memory that work together to enable a device such as a mobile phone or server to perform various functions), and (c) a hardware circuit and / or processor that requires software (e.g., firmware) to operate, such as a microprocessor or a portion of a microprocessor, but where software is not required to operate, the software may not be present.

[0050] This definition of circuitry applies to all uses of this term in this application, including in any claims. As another example, as used in this application, the term circuitry also covers implementations of only a hardware circuit or processor (or multiple processors), or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers (for example and if applicable to a particular claim element) a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0051] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard, such as Long Term Evolution (LTE), Advanced LTE (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. In addition, the communication between the terminal equipment and the network equipment in the communication network can be performed according to any suitable generation of communication protocols, including but not limited to the first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G), future sixth generation (6G) communication protocols, and / or any other protocols currently known or to be developed in the future. In view of the rapid development of communication, there are of course future types of communication technologies and systems, which can be used to implement the present disclosure. The scope of the present disclosure should not be considered to be limited to the above-mentioned systems.

[0052] As used herein, the term "network device" refers to a node in a communication network via which a terminal device accesses the network and receives services from the network. Depending on the terminology and technology applied, a network device may refer to a base station (BS) or an access point (AP), such as a NodeB (NodeB or NB), an evolved NodeB (eNodeB or eNB), a NR next-generation NodeB (gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, a low-power node such as a femto, a pico, etc. The radio access network (RAN) split architecture includes a gNB-CU (centralized unit, hosting the radio resource control (RRC) layer, the service data adaptation protocol (SDAP) layer, and the packet data convergence protocol (PDCP) layer), which controls multiple gNB-DUs (distributed units, hosting the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer).

[0053] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not limitation, a terminal device may also be referred to as a communication device, a user equipment (UE), a subscriber station (SS), a portable subscriber station, a mobile station (MS), or an access terminal (AT). The terminal device may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable terminal device, a personal digital assistant (PDA), a portable computer, a desktop computer, an image capture terminal device such as a digital camera, a game terminal device, a music storage and playback device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, a smart device, a wireless client device (CPE), an Internet of Things (IoT) device, a watch or other wearable device, a head mounted display (HMD), a vehicle, a drone, medical equipment and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.

[0054] Although the functions described herein may be performed in fixed and / or wireless network nodes in various example embodiments, in other example embodiments, the functions may also be implemented in a user equipment device (such as a cellular phone or a tablet computer or a laptop computer or a desktop computer or a mobile IoT device or a fixed IoT device). The user equipment device may, for example, be appropriately equipped with the corresponding capabilities described in conjunction with the fixed and / or wireless network nodes. The user equipment device may be a user device, and / or a control device such as a chipset or a processor, which is configured to control the user device when installed in the user device. Examples of such functions include a bootstrap server function and / or a home user server, which may be implemented in a user equipment device by providing the user equipment device with software configured to cause the user equipment device to execute from the perspective of these functions / nodes.

[0055] Starting from Release 16, the 3rd Generation Partnership Project (3GPP) has considered how to define technology building blocks in cellular networks for delivering reliable and predictable network services defined by other standardization groups such as the Institute of Electrical and Electronics Engineers (IEEE) TSN.

[0056] In 3GPP Release 16, the integration of Layer 2 (L2) Ethernet TSN features into 5GS was introduced as a fundamental part of Ultra-Reliable and Low-Latency Communication (URLLC). 5GS bridges utilize a fully centralized configuration model. In this model, the TSN application function (TSN AF) discovers the capabilities of the ingress / egress ports (DS-TT: device-side TSN translator, or NW-TT: network-side TSN translator), configures them, and gets notifications about configuration updates from them via the Port Management Information Container (PMIC) and / or the User Plane Node Management Information Container (UMIC).

[0057] In 3GPP Release 17, generalized Time-Sensitive Communication (TSC) support was introduced to provide deterministic transmission capabilities without relying on TSN specific functions. Since then, 5GS has defined generic enablers for TSC and local TSC. The Time-Sensitive Communication and Time Synchronization Function (TSCTSF) was introduced to handle time synchronization, individual Quality of Service (QoS) parameters, and TSC Assisted Container (TSCAC) determination. TSCTSF discovers ingress / egress port (DS-TT or NW-TT) capabilities, configures them, and gets notifications about configuration updates from them. Similar to TSN AF, TSCTSF is able to utilize PMIC and UMIC to communicate with DS-TT and NW-TT, depending on the capabilities and configuration data models they support.

[0058] As mentioned above, on the UE side, when a device with DS-TT joins a 5GSDetNet node, the DS-TT side interface of the device becomes the IP interface of the 5GSDetNet node. However, the management of this DS-TT side interface of the device is still imperfect and needs further development.

[0059] In view of this, an embodiment of the present disclosure provides a solution for managing external IP interfaces in a 5GS IP router node. In the context of the present disclosure, the external IP interface in a 5GS IP router node includes a DS-TT side interface (also referred to as a device side IP interface for convenience) and / or an NW-TT side interface (also referred to as a network side IP interface for convenience).

[0060] In the scheme, a method is provided to enable a 5G core network (5GC) function operating as a 5GS IP router node. The method is designed to configure and discover IP management information of an external IP interface of a 5GS IP router node. The IP management information may include IP address information and IP configuration information.

[0061] In one aspect, the core network element can configure the corresponding IP address information and IP configuration information to the device side IP interface or the network side IP interface. That is, the core network element acts as a "management owner" for IP management. On the other hand, the core network element can learn the corresponding IP address information and IP configuration information of the device side IP interface or the network side IP interface. That is, the core network element acts as a "management learner" for IP management. Both modes can be used for different external IP interfaces within the same IP router node.

[0062] In some embodiments, the device sends an indication of the external IP interface of the IP router node to a core network element, and receives IP address information from the core network element. In this way, the external IP interface on the device side can be managed.

[0063] In some embodiments, the core network element allocates IP address information to the external IP interface of the IP router node, generates information of the IP router node, and exposes the information of the IP router node to the IP router controller. In this way, the core network element can be enabled as the owner of the external IP interface management for the IP router node.

[0064] In some embodiments, the core network element learns at least the IP address information and interface number of the external IP interface of the IP router node, and binds the interface number to at least the IP address information. In this way, the core network element can be enabled as a learner for external IP interface management of the IP router node.

[0065] In some embodiments, the core network element stores the subscription information of the device in association with at least one of the following items: a pairing of an identifier of the IP router node and an interface number of an external Internet Protocol interface, IP address information of the external Internet Protocol interface, or IP configuration information of the external Internet Protocol interface. In this way, the core network element can support the management of the external IP interface of the IP router node.

[0066] The principles and implementations of the present disclosure will be described in detail below with reference to the accompanying drawings. For illustration, the following description will be given using the DetNet architecture as an example of an IP router architecture. It should be understood that the embodiments of the present disclosure are also applicable to any suitable IP router architecture.

[0067] Example of communication environment

[0068] Figure 1 An example DetNet architecture 100 is shown in which embodiments of the present disclosure may be implemented. The DetNet architecture 100 is a reference architecture for a DetNet network with a centralized controller plane. Figure 1As shown, the DetNet architecture 100 may include DetNet end systems 110 - 1 and 110 - 2 (for convenience, they may also be collectively referred to as DetNet end systems 110 herein). The DetNet end system 110 may be a robot in a factory or any other suitable terminal.

[0069] The DetNet architecture 100 may further include DetNet nodes 120 - 1 , 120 - 2 , and 120 - 3 (for convenience, they may also be collectively referred to herein as DetNet nodes 120 ).

[0070] like Figure 1 As shown, the DetNet architecture 100 may further include a DetNet controller 130. The DetNet controller 130 may be connected to a database (DB) 140. The DetNet controller 130 may collect topology and capability and resource availability information from the DetNet nodes 120. Using this information and the ability to configure explicit routing and reserve resources along the routing, the DetNet controller may calculate and establish an end-to-end (E2E) deterministic path for a DetNet service flow based on a request from an application.

[0071] It should be understood that Figure 1 These are merely examples, and the DetNet architecture 100 may include any other suitable type or number of elements.

[0072] The communication in the DetNet architecture 100 may be implemented according to any appropriate communication protocol, including but not limited to cellular communication protocols of first generation (1G), second generation (2G), third generation (3G), fourth generation (4G), fifth generation (5G) or future sixth generation (6G) wireless local area network communication protocols, and / or any other protocol currently known or developed in the future. In addition, the communication may utilize any appropriate wireless communication technology, including but not limited to: code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplex (FDD), time division duplex (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiplexing (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM) and / or any other technology currently known or to be developed in the future.

[0073] For 3GPP Release 18, a study item is to investigate whether and how 3GPP can support DetNet to provide mapping between the central DetNet controller entity and 5GS. This study considers 5GS to act as a central DetNet controller entity in the DetNet domain. Figure 1 One of the DetNet nodes in .

[0074] The Release 18 study has the following architectural assumptions (not all assumptions are listed below): IP-based DetNet services are carried in IP-type protocol data unit (PDU) sessions; mapping functionality for DetNet is implemented in TSC TSF; the solution should reuse the functionality of the TSC framework defined in Release 17, if applicable; the granularity of the 5GSDetNet node is per user plane function (UPF) for each network instance; and the solution should not be affected by any 5G access network (AN) and UE.

[0075] The 5GS is extended to support the following: The UE is part of the 5GS logical DetNet node and is therefore not itself a DetNet node or end system.

[0076] 5GS has defined various ways to configure the UE's IP address information and the 5GC internal IP routing information related to the UE. 5GC and UE support the following IP address allocation mechanisms:

[0077] - During the PDU session establishment procedure, the Session Management Function (SMF) sends the IP address to the UE via Non-Access Stratum (NAS) Session Management (SM) signaling or via IPv6 Router Advertisement. Once the PDU session is established, IPv4 address allocation and / or IPv4 parameter configuration via DHCPv4 may also be used.

[0078] - If IPv6 is supported, IPv6 prefix allocation should be supported via IPv6 stateless autoconfiguration. IPv6 parameter configuration via stateless DHCPv6 may also be supported.

[0079] In addition, for residential gateway (GW) implementations, the following address configuration mechanisms are specified: IPv6 address allocation using DHCPv6 can be supported to allocate individual IPv6 addresses for PDU sessions; and IPv6 prefix delegation using DHCPv6 can be supported to allocate additional IPv6 prefixes for PDU sessions.

[0080] To support IP routing behind the UE, 3GPP has specified a framed routing mechanism. 3GPP has defined a mechanism called "framed routing" that allows the 5GC to be configured with an IP prefix / subnet that should be forwarded to the UE in addition to the UE's own or delegated prefix. The framed routing information can be provided to the SMF by the Data Network Authentication Authorization Accounting (DN-AAA) server or Unified Data Management (UDM) that stores the information. The SMF configures this framed routing information in the UPF using normal packet detection rules (PDR) / forwarding action rules (FAR). Framed routing does not cover routing or forwarding performed by the UE acting as a router, but this part needs to be configured separately in the UE router itself.

[0081] Figure 2 An example 5G S DetNet node architecture 200 is shown in which embodiments of the present disclosure may be implemented. Figure 2 As shown, the 5GSDetNet node 210 may include a UE / DS-TT module 211, a radio access network (RAN) 212, and multiple core network elements, such as a UPF / NW-TT module 213, an SMF 214, an access management function (AMF) 215, an UDM 216, a TSCTSF 217, a policy control function (PCF) 218, and a network exposure function (NEF) 219. The TSCTSF may be connected to the DetNet controller 220 via the NEF 219. It should be understood that Figure 2 These are merely examples, and the architecture 200 and the 5G S DetNet node 210 may also include any other suitable greater or fewer elements.

[0082] like Figure 2 As shown, the UE / DS-TT module 211 can provide the external IP interface #2 of the 5GSDetNet node 210 to the DetNet node or DetNet end system 201. The UPF / NW-TT module 213 can provide the external IP interface #3 of the 5GSDetNet node 210 to the DetNet node or DetNet end system 202.

[0083] In the context of the present disclosure, interface #2 may also be referred to as a device-side IP interface, and interface #3 may also be referred to as a network-side IP interface. The device-side IP interface and the network-side IP interface may also be collectively referred to as an external IP interface of a DetNet node.

[0084] In some embodiments, the UE / DS-TT module 211 may include a device (e.g., a terminal device) and a DS-TT, and the DS-TT may provide interface #2. In some embodiments, the device may not be accompanied by a DS-TT. That is, the UE / DS-TT module 211 may only include the device. In this case, the device itself provides interface #2.

[0085] In some embodiments, the UPF / NW-TT module 213 may include a UPF and a NW-TT, and the NW-TT may provide interface #3. In some embodiments, the UPF may not be accompanied by the NW-TT. That is, the UPF / NW-TT module 213 may include only the UPF. In this case, the UPF itself provides interface #3.

[0086] The granularity of a 5GSDetNet node is per UPF per network instance. Therefore, a 5GSDetNet node consists of a single UPF and one or more devices. Each device may be accompanied by one or more DS-TTs that provide the 5GSDetNet node with an IP interface to an external DetNet network. A UPF may be accompanied by one or more NW-TTs and have a collection of IP interfaces that also connect the 5GSDetNet node to an external DetNet network. For simplicity, Figure 2 Only one device-side or network-side IP interface is shown, and it should be understood that multiple device-side or network-side IP interfaces are also feasible.

[0087] In the 5GSDetNet node 210, the TSCTSF 217 is responsible for the interaction with the DetNet controller 220. The DetNet controller 220 requires the IP topology and routing information of each DetNet node in the DetNet domain as input for calculating the path of the DetNet service flow. Therefore, the integration of DetNet into 5GS puts forward new requirements for 5GS, especially for TSCTSF and TT functionality.

[0088] For IP address management, the 5GS as one of the DetNet nodes in the DetNet domain shall expose all its externally visible interfaces to the DetNet controller. On the device side, when a device joins a 5GSDetNet node, its device-side IP interface becomes the external IP interface of the 5GSDetNet node. The device-side interface as an IP router interface may require at least an IP address and IP prefix / subnet information.

[0089] Although the current 3GPP specifications support various ways to configure the IP address information of the UE, these mechanisms mean configuring the 3GPP access network (e.g., 5G AN) side IP interface of the terminal device, such as Figure 2 Interface #1 is shown instead of interface #2. IPv6 prefix delegation can be used to provide additional prefixes for the network behind the terminal device in addition to the prefix assigned to interface #1. However, it is not clearly defined how the terminal device uses the delegated prefixes or forms its own IP address from the delegated prefixes. In this case, it is necessary to know exactly which prefixes are adopted by the device-side IP interfaces and which IPv6 addresses are used by the device-side IP interfaces. IPv6 prefix delegation also only works for IPv6 and not for IPv4. For the UPF / NW-TT module, if the UPF or NW-TT provides multiple network-side IP interfaces, these interfaces may require separate configuration.

[0090] After the external IP interfaces obtain their IP address information, TSCTSF needs to know the IP address information of all external IP interfaces for 5GSDetNet nodes.

[0091] For IP interface properties, external IP interfaces may have some basic properties, such as the IP routing protocols or algorithms and L2 technologies they support, IP parameters related to the IP routing protocols or algorithms, the L2 / MAC addresses they have, or what their bit rates are. The TSCTSF responsible for the 5GSDetNet node needs to learn these properties and also needs to configure at least part of these properties.

[0092] In view of this, efforts are made to address how 5GS network functions and terminal devices and / or DS-TT / NW-TT generally operate as DetNet nodes from the perspective of IP interface addressing and management as well as IP routing and packet forwarding. In addition, efforts are made to address how to assign IP addresses to external IP interfaces of DetNet nodes. In addition, efforts are made to address how to learn or configure IP parameters of external IP interfaces and how to make the TSCTSF aware of the IP addresses and IP parameters of external IP interfaces.

[0093] 3GPP Release 17 defines how TSCTSF and DS-TT / NW-TT can exchange management information containers for TSC, including UMIC and PMIC. However, the UMIC and PMIC defined by 3GPP for TSC currently focus on Ethernet layer information, while IP layer information is not defined.

[0094] The embodiments of the present disclosure provide a solution for managing external IP interfaces in DetNet nodes to solve the above and other potential problems. Figures 3A to 5 Describe in more detail.

[0095] Example Implementation of IP Architecture Model

[0096] Figure 3A An example IP architecture model 300A of a device acting as a device-side IP interface of a 5G SDetNet node is shown in which embodiments of the present disclosure may be implemented. For the purpose of discussion, reference will be made to Figure 2 Model 300A is described. Model 300A may be implemented at UE / DS-TT module 211 .

[0097] like Figure 3A As shown, the UE / DS-TT module 211 may include a device 310 and a DS-TT 311. The device 310 may provide a 5G IP interface 320 (i.e., Figure 2 Interface #1 as shown), and DS-TT 311 can provide 5GSDetNet node IP interface 321 (i.e., as Figure 2 Interface #2 shown). 5GSDetNet node IP interface 321 corresponds to the device-side IP interface of the DetNet node. In some embodiments, device 310 may be a terminal device.

[0098] The 5G IP interface 320 is a "normal" 5G AN IP interface of the device 310, and the device 310 can be connected to the data network via the UPF. The IP address of the 5G IP interface 320 is allocated or configured by existing means such as NAS SM signaling, IPv6 router advertisement messages, or Dynamic Host Configuration Protocol (DHCP) messages. From the perspective of the 5G SDetNet node, the 5G IP interface 320 is not an externally visible interface, but is mainly used only for packet forwarding within the 5G SDetNet node.

[0099] The 5GSDetNet node IP interface 321 is an externally visible interface of the 5GSDetNet node. In principle, the 5GSDetNet node IP interface 321 can be any type of interface that supports IP and DetNet compatible IP QoS, but in practice the 5GSDetNet node IP interface 321 is most often an Ethernet interface.

[0100] Alternatively, the UE / DS-TT module 211 may consist of only the device 310, without including the DS-TT 311. In this case, the device 310 may provide the 5G IP interface 320 and the 5GSDetNet node IP interface 321 by itself.

[0101] Figure 3B An example IP architecture model 300B of a device acting as a network-side IP interface of a 5G SDetNet node in which embodiments of the present disclosure may be implemented is shown. For the purpose of discussion, reference will be made to Figure 2 Model 300B is described. Model 300B may be implemented at UPF / NW-TT module 213 .

[0102] like Figure 3B As shown, the UPF / NW-TT module 213 may include a UPF 330 and a NW-TT 331. The NW-TT 331 may provide a 5GSDetNet node IP interface 340 (i.e., Figure 2 Interface #3 shown). The 5GSDetNet node IP interface 340 corresponds to the network-side IP interface of the DetNet node.

[0103] The 5GSDetNet node IP interface 340 is an externally visible interface of the 5GSDetNet node. In principle, the 5GSDetNet node IP interface 340 can be any type of interface that supports IP and DetNet compatible IP QoS, but in practice the 5GSDetNet node IP interface 340 is most often an Ethernet interface.

[0104] Alternatively, the UPF / NW-TT module 213 may consist of only the UPF 330, without including the NW-TT 331. In this case, the UPF 330 may provide the 5GSDetNet node IP interface 340 by itself.

[0105] Embodiments of the present disclosure are intended to provide IP management for an externally visible interface (i.e., 5GSDetNet node IP interface 321 or 340) of a 5GS IP router node (e.g., 5GSDetNet node). Externally visible means, for example, that an adjacent DetNet node will see the interface as a next-hop interface for IP services (such as DetNet service flows), or an interface that is relevant to a DetNet controller to understand network topology or routing.

[0106] In one scheme, IP management can be implemented using TSCTSF as the owner and SMF as the learner. In another scheme, IP management can be implemented using TSCTSF as the learner and SMF as the owner. What these two schemes have in common is that they allow 5GC to detect new external IP interfaces or lists of external IP interfaces and configure IP address information and / or IP configuration information to the detected external IP interfaces. In addition, allowing TSCTSF to know IP address information and / or IP configuration information and to update using IP address information and / or IP configuration information allows TSCTSF to expose IP address information and / or IP configuration information to a DetNet controller or any other IP software defined network (SDN) controller.

[0107] In some embodiments, the IP address information may include an IP address and a prefix length. For example, the IP address information may include an IP address and a subnet mask for IPv4. As another example, the IP address information may include one or more IP prefixes and an interface identifier (ID) for IPv6. For example, the complete IP address of an external IP interface may be a concatenation of a prefix and an interface ID. It should be understood that these are merely examples, and the IP address information may take any other suitable form.

[0108] In the context of the present disclosure, IP configuration information can refer to additional IP or lower layer information of an interface. In certain embodiments, IP configuration information can include IP routing protocols or algorithms applied to an interface and IP parameters configured for the IP routing protocols or algorithms. In certain embodiments, IP configuration information can include the maximum transmission unit (MTU) size of an interface. In certain embodiments, IP configuration information can include configuration or neighbor / address resolution protocol (ARP) cache of an interface about how to perform duplicate address detection. For example, IP configuration information can include lower layer information, such as L2 technology type (for example, Ethernet), bit rate and address (for example, MAC address). As another example, IP configuration information can include cost and / or priority of an IP link. It should be appreciated that these are merely examples, and IP configuration information can include any other suitable information.

[0109] Depending on the implementation, IP configuration information can be read-only or read-and-write to the TSCTSF. For example, lower layer information such as L2 technology type (e.g., Ethernet), bit rate, and address (e.g., MAC address) can be read-only to the TSCTSF because they originate from the interface hardware and cannot be changed by configuration. As another example, the IP routing protocol or algorithm applied to the interface and the IP parameters configured for the IP routing protocol or algorithm can be "read and write" to the TSCTSF. As another example, parameters such as the cost and / or priority of an IP link can be "read and write" to the TSCTSF. It should be understood that these are merely examples and are not intended to be limiting.

[0110] For the purpose of illustration, reference will be made to Figure 4 and Figure 5 Some example embodiments of external IP interface management are described in detail.

[0111] Example implementation of external IP interface management with TSCTSF as owner

[0112] Figure 4 A diagram illustrating a communication process 400 according to some embodiments of the present disclosure is shown. For the purpose of discussion, reference will be made to Figure 2 Describe the model 400. Assume that the device 310 is accompanied by the DS-TT 311 and the UPF 330 is accompanied by the NW-TT 331. The TSCTSF 217 acts as the management owner and the SMF 214 acts as the management learner. The UPF 330 is pre-configured with the interface numbers of the external IP interfaces of the 5GSDetNet nodes and the list of 5GSDetNet node IDs. It should be understood that Figure 4 The order and number of steps in the drawings are for illustration only and are not intended to be limiting.

[0113] like Figure 4As shown, in step 401, the device 310 sends an indication of the device-side IP interface of the DetNet node to the first core network element (eg, SMF 214). The indication may be implemented in any appropriate manner.

[0114] In some embodiments, the device 310 may send the indication in a PDU session establishment request. For example, the device 310 may send the indication in a NAS SM message via an AMF (not shown).

[0115] In some alternative embodiments, the device 310 may send the indication in the DHCP request after the PDU session is established. In some embodiments, the DHCP request may include an identifier dedicated to the device-side IP interface as the indication.

[0116] In some embodiments for IPv4, the identifier may be a DHCP client ID dedicated to the device-side IP interface. In some embodiments, the DHCP client ID may be assigned by the SMF 214 in the NAS SM PDU session establishment signaling during the PDU session establishment. In some alternative embodiments, the DHCP client ID may be predefined. In this case, the device 310 may indicate the DHCP client ID to the SMF 214 in the NAS SM PDU session establishment signaling during the PDU session establishment.

[0117] In some embodiments for IPv6, the identifier may be an IA_PD identifier of an IA_PD option dedicated to the device-side IP interface. For example, when the device 310 requests an IPv6 prefix for a DetNet interface from the SMF 214 with IPv6 prefix delegation. The device 310 acts as a "requesting router" and inserts the DetNet interface-specific IA_PD option into the DHCPv6 request message sent to the SMF 214. In some embodiments, the IA_PD identifier may be allocated by the SMF 214 in the NAS SM PDU session establishment signaling during the PDU session establishment. In some alternative embodiments, the IA_PD identifier may be predefined. In this case, the device 310 may indicate the IA_PD identifier to the SMF 214 in the NAS SM PDU session establishment signaling during the PDU session establishment.

[0118] Upon receiving the indication, SMF 214 determines, at step 402, that a new device-side IP interface is detected. In some embodiments where the indication is sent in a PDU session establishment request, SMF 214 can identify that the PDU session is established to join a 5GSDetNet node. In some embodiments where the indication is sent in a DHCP request, SMF 214 can associate the DHCP request to a specific device-side IP interface.

[0119] In step 403, SMF 214 requests the fourth core network element (eg, UPF 330) to allocate an interface number for the device side IP interface. For the first joining device side IP interface to the 5GSDetNet node, UPF 330 may also feedback the 5GSDetNet node ID to SMF 214.

[0120] In step 404, SMF 214 sends the interface number, 5GSDetNet node ID and PDU session ID to the second core network element (e.g., TSCTSF 217) via PCF (not shown).

[0121] At step 405, TSCTSF 217 determines IP address information for the device-side IP interface. In some embodiments, TSCTSF 217 is pre-configured with a set of IP address information for a set of device-side IP interfaces. In this case, as shown in step 405-1, TSCTSF 217 can determine IP address information for the device-side IP interface from the set of IP address information.

[0122] In some alternative embodiments, as shown in step 405-2, TSCTSF 217 may send a request (also referred to herein as a second request for convenience) to SMF 214 for obtaining at least one of the IP address information or IP configuration information for the device-side IP interface. SMF 214 may send a request (also referred to herein as a first request for convenience) to a third core network element (e.g., UDM 216) for obtaining at least one of the IP address information or IP configuration information for the device-side IP interface. Then, SMF 214 may receive at least one of the IP address information or IP configuration information for the device-side IP interface from UDM 216, and send at least one of the IP address information or IP configuration information for the device-side IP interface to TSCTSF 217.

[0123] In some embodiments, the first request may be actively sent by SMF 214. In some embodiments, the first request may be sent by SMF 214 in response to receiving the second request.

[0124] In some embodiments, each of the first request and the second request may include as a key the ID of the device 310. For example, if the mapping between the UE ID and the DetNet node ID / interface number is already known when the information is stored in the UDM 216, the UE ID may be used to request the information.

[0125] In some embodiments, each of the first request and the second request may include a pairing of a 5GS DetNet node ID and an interface number of a device-side IP interface as a key. In some embodiments, SMF 214 may derive a pairing of an identifier of a 5GS DetNet node and an interface number of a device-side IP interface from a general public subscription identifier (GPSI) of device 310. The GPSI is within the subscription data of device 310. Device 310 may have multiple GPSIs associated with the same UE ID (e.g., an International Mobile Subscriber Identity (IMSI)). For example, the information may be requested using the GPSI by a specific locally meaningful mapping from a GPSI associated with the UE ID to a pairing of {DetNet node ID and interface number}.

[0126] In some alternative embodiments, as shown in step 405-3, TSCTSF 217 may send a request to UDM 216 for obtaining at least one of the IP address information or IP configuration information of the device-side IP interface. In some embodiments, the request may include the ID of the device 310 as a key. In some embodiments, the request may include a pairing of the 5GSDetNet node ID and the interface number of the device-side IP interface as a key. In this regard, the request may be implemented similarly to the first request or the second request, so other details are omitted here for simplicity. Then, TSCTSF 217 may receive at least one of the IP address information or IP configuration information for the device-side IP interface from UDM 216.

[0127] The information stored in the UDM 216 or DN-AAA server (not shown) can be considered as an extension of the current framed routing information stored in accordance with earlier 3GPP releases. This information will need to be augmented by two additional mandatory information segments for the prefix for the device-side IP interface of the UE: an indicator indicating that the prefix is ​​for the device-side IP interface of the UE; and an IP interface ID by which a complete IP address can be formed from the prefix. Optionally, this information may also include other IP configuration parameters (e.g., MTU size) specified for the device-side IP interface.

[0128] In the above manner, TSCTSF uses the received extended information to learn IP address information, that is, the IP prefix and address (IP interface ID) specified for the device-side interface.

[0129] In some alternative embodiments, after receiving the request from TSCTSF 217, SMF 214 may request the information from UDM 216 or DN-AAA server (not shown) by using DHCP to request the IP configuration information of the device-side IP interface. For example, SMF 214 may use the {DetNet node ID and interface number} pairing in the DHCP query. SMF 214 may pass the information received from the DHCP server to TSCTSF 217.

[0130] At step 406, DS-TT 311 sends the IP management capability of the device-side IP interface to TSCTSF 217. In some embodiments, DS-TT 311 may send the IP management capability via PMIC. In some embodiments without DS-TT, device 310 may send the IP management capability of the device-side IP interface to TSCTSF 217.

[0131] In step 406', NW-TT 331 may send the IP management capabilities of the network side IP interface to TSCTSF 217. In some embodiments, NW-TT 331 may send the IP management capabilities via PMIC or UMIC. In some embodiments for transmission via PMIC, PMIC may carry information of one port or interface. In some embodiments for transmission via UMIC, UMIC may carry information of one or more ports or interfaces. In some embodiments without NW-TT, UPF 330 may send the IP management capabilities of the network side IP interface to TSCTSF 217 via N4 session level message.

[0132] In some embodiments, DS-TT 311 or NW-TT 331 may send the types of supported IP routing protocols or algorithms as IP management capabilities to TSCTSF 217. For example, IP management capabilities may indicate that DS-TT 311 may support routing protocols: Open Shortest Path First (OSPF) protocol and Intermediate System to Intermediate System (IS-IS) protocol.

[0133] In step 407, if necessary, TSCTSF 217 may update the IP configuration information of the device-side IP interface based on the IP management capability of the device-side IP interface. If necessary, TSCTSF 217 may update the IP configuration information of the network-side IP interface based on the IP management capability of the network-side IP interface.

[0134] In some embodiments where the IP management capability indicates that the DS-TT 311 or the NW-TT 331 can support OSPF and IS-IS protocols, the TSCTSF 217 can configure the type of routing protocol or algorithm and the parameters of the routing protocol or algorithm applied in the interface in the updated IP configuration information. For example, these parameters can include at least one of the following items: hello interval (the number of seconds for the interface to send an OSPF hello packet to the network), the cost of the interface, the retransmission interval (the number of seconds that the interface retransmits a link state advertisement (LSA) to a neighbor that did not respond to the original LSA), etc.

[0135] In step 408, the TSCTSF 217 may bind the interface number with the IP address information corresponding to the PDU session. For example, the TSCTSF 217 may establish binding information of the IP address information of the interface corresponding to the PDU session and the interface number. If the TSCTSF 217 knows the IP address of the device having the interface, the TSCTSF 217 may also include the IP address of the device in the binding information. In this way, it is ensured that the PMIC is sent to the correct interface.

[0136] As another example, IPv6 interface ID determination may be done based on the MAC address of DS-TT 311. The MAC address may be sent to TSCTSF 217 during the PDU session establishment process. In this case, TSCTSF 217 may provide an IPv6 prefix to the interface. If a full IP address is provided, TSCTSF 217 may provide an IPv6 prefix based on the MAC address.

[0137] TSCTSF 217 also maintains up-to-date information of IP address information and IP configuration information provided to each interface or interface number.

[0138] In step 409, TSCTSF 217 may send the IP address information to DS-TT 311. In some embodiments, TSCTSF 217 may also send IP configuration information. In some embodiments, TSCTSF 217 may send at least one of the IP address information or the IP configuration information via PMIC. For example, if the IP configuration information can be written, TSCTSF 217 may send the IP address information and may also send any other "read-write" parameters of the IP configuration information to DS-TT 311 via PMIC.

[0139] In some embodiments without DS-TT, TSCTSF 217 may send at least one of IP address information or IP configuration information via a NAS SM message.

[0140] In step 409', the TSCTSF 217 may determine the IP address information of the network side IP interface and send the IP address information to the NW-TT 331. In some embodiments, the TSCTSF 217 may also send the IP configuration information of the network side IP interface. In some embodiments, the TSCTSF 217 may send at least one of the IP address information or the IP configuration information of the network side IP interface via the PMIC or the UMIC. For example, if the IP configuration information can be written, the TSCTSF 217 may send the IP address information and may also send any other "read-write" parameters of the IP configuration information to the NW-TT 331 via the PMIC or the UMIC. In some embodiments without the NW-TT, the TSCTSF 217 may send at least one of the IP address information or the IP configuration information via the SM policy association modification process.

[0141] In step 410, the TSCTSF 217 may send the IP address information associated with the DS-TT to the SMF 214, and the SMF 214 may send the IP address information to the UPF 330. In this way, the TSCTSF 217 may ensure that the UPF 330 starts forwarding IP packets to the IP address information of the PDU session associated with the DS-TT 311. For example, the TSCTSF 217 notifies the SMF 214 that an IPv4 address or an IPv6 prefix should be associated with the PDU session. The SMF 214 may configure the IP address information to the UPF 330 via the PDR.

[0142] In step 411, the TSCTSF 217 may generate information of the DetNet node. The information may include the DetNet node ID of the DetNet node, the interface number and IP address information of the IP interface, and / or the IP configuration information. In some embodiments, the information of the DetNet node may include the interface number and IP address information of each external IP interface in the same DetNet node.

[0143] At step 412, TSCTSF 217 may expose the information of the DetNet node to a controller (e.g., DetNet controller 220). In some embodiments, the information of the DetNet node may be exchanged by any means such as a YANG data model and NETCONF / RESTCONF protocol, a path computation element protocol, or a master information block (MIB) data model and a simple network management protocol (SNMP). The present disclosure is not limited in this respect.

[0144] Using process 400, external IP interface management may be implemented for an IP router node. Using TSCTSF as a learner Example implementation of external IP interface management

[0145] Figure 5 A diagram illustrating a communication process 500 according to some embodiments of the present disclosure is shown. For the purpose of discussion, reference will be made to Figure 2 , Figure 3A and Figure 3B Model 500 is described. It is assumed that device 310 is accompanied by DS-TT 311 and UPF 330 is accompanied by NW-TT 331. TSCTSF 217 acts as a management learner and SMF 214 acts as a management owner. UPF 330 is pre-configured with a list of interface numbers of external IP interfaces of 5GSDetNet nodes and 5GSDetNet node IDs. It should be understood that Figure 5 The order and number of steps in the drawings are for illustration only and are not intended to be limiting.

[0146] like Figure 5 As shown, in step 501, the device 310 sends an indication of the device-side IP interface of the DetNet node to the first core network element (eg, SMF 214). The indication may be implemented in any appropriate manner.

[0147] In some embodiments, the device 310 may send the indication in a PDU session establishment request. For example, the device 310 may send the indication in a NAS SM message via an AMF (not shown). In some embodiments, the PDU session establishment request may also include a protocol configuration option (PCO) value indicating the configuration of the device-side IP interface. In some embodiments, the PCO value may include a MAC address or an IP interface ID of the DS-TT 311.

[0148] In some alternative embodiments, the device 310 may send the indication in the DHCP request after the PDU session is established. In some embodiments, the DHCP request may include an identifier dedicated to the device-side IP interface as the indication.

[0149] The operation in step 501 is the same as Figure 4 The operation in step 401 is similar, so other details are omitted here for simplicity.

[0150] Upon receiving the indication, SMF 214 determines that a new device-side IP interface is detected in step 502. In some embodiments where the indication is sent in a PDU session establishment request, SMF 214 can identify that the PDU session is established for the purpose of joining a 5G SDetNet node. In some embodiments where the indication is sent in a DHCP request, SMF 214 can associate the DHCP request to a specific device-side IP interface.

[0151] In step 503, SMF 214 may request a fourth core network element (eg, UPF 330) to allocate an interface number to the device side IP interface. For the first joining device side IP interface to the 5GSDetNet node, UPF 330 may also feedback the 5GSDetNet node ID to SMF 214.

[0152] In step 504, SMF 214 may determine the IP address information of the device-side IP interface. In some embodiments, SMF 214 may select the IP address and prefix length for the device-side IP interface from an IP pool. In some embodiments, the index of the IP pool may be obtained from UPF, PCF, or UDM. It should be understood that any other suitable approach is also feasible.

[0153] In step 505, SMF 214 may bind the interface number with the IP address information and the PDU session ID. For example, SMF 214 may establish binding information of the interface number, the IP address information, and the PDU session ID. If the SMF knows the IP address of the device associated with the interface, the SMF also includes the IP address of the device in the binding information.

[0154] At step 506, SMF 214 may receive IP management capabilities of the device-side IP interface from device 310, for example, via a NAS SM message.

[0155] In step 506 ′, SMF 214 may receive IP management capabilities of the network-side IP interface from UPF 330 .

[0156] In step 507, if necessary, SMF 214 can update the IP configuration information of the device-side IP interface based on the IP management capability of the device-side IP interface. If necessary, SMF 214 can update the IP configuration information of the network-side IP interface based on the IP management capability of the network-side IP interface.

[0157] In step 508, SMF 214 may send the IP address information to device 310. In some embodiments, SMF 214 may also send IP configuration information. In some embodiments, SMF 214 may send at least one of the IP address information or the IP configuration information via a NAS SM message.

[0158] For example, if the PDU session establishment request includes a PCO value dedicated to the device-side IP interface, the SMF 214 can respond with the PCO value, which includes the IP prefix and / or IP configuration information for the device-side IP interface. As another example, if the device 310 provides the MAC address or IP interface ID of the device-side IP interface in the PCO, the SMF 214 can consider them when determining the IPv6 address for the device-side IP interface.

[0159] In some embodiments, SMF 214 may send at least one of the IP address information or the IP configuration information via a DHCP message. For example, SMF 214 may allocate an IPv4 address and / or an IPv6 prefix for a device-side IP interface, construct a DHCP server message, and send the allocated address / prefix to device 310. Device 310 may pass the IP address / prefix to the device-side IP interface.

[0160] In step 508', SMF 214 may determine the IP address information of the network side IP interface and send the IP address information to UPF 330. In some embodiments, SMF 214 may also send IP configuration information of the network side IP interface to UPF 330. In some embodiments, SMF 214 may send at least one of the IP address information or the IP configuration information of the network side IP interface.

[0161] In step 509, SMF 214 may send the IP address information of the external IP interface to TSCTSF 217. In some embodiments, SMF 214 may also send the IP configuration information of the external IP interface to TSCTSF 217.

[0162] At step 510 , TSCTSF 217 may receive IP management capabilities and IP configuration information of the device-side IP interface from DS-TT 311 , for example, via PMIC.

[0163] In step 510', TSCTSF 217 may receive IP management capabilities and IP configuration information of the network-side IP interface from NW-TT 331, for example, via PMIC or UMIC. In some embodiments for receiving via PMIC, PMIC may carry information of one port or interface. In some embodiments for receiving via UMIC, UMIC may carry information of one or more ports or interfaces.

[0164] In step 511, the TSCTSF 217 may learn the interface number and IP address information corresponding to the PDU session for the device-side IP interface, and bind the interface number with the IP address information corresponding to the PDU session. In some embodiments, the TSCTSF 217 may also learn the interface number and IP address information for each external IP interface, and bind the interface number and IP address information for each external IP interface. If the TSCTSF 217 knows the IP address of the device associated with the external IP interface, the TSCTSF 217 may also include the IP address of the device in the binding information.

[0165] In step 512, TSCTSF 217 may generate information of the DetNet node. The information may include the DetNet node ID of the DetNet node, the interface number and IP address information of the IP interface, and / or IP configuration information. In some embodiments, the information of the DetNet node may include the interface number and IP address information of each external IP interface in the same DetNet node.

[0166] In step 513, TSCTSF 217 may expose the information of the DetNet node to a controller (e.g., DetNet controller 220). In some embodiments, the information of the DetNet node may be exchanged by any means such as YANG data model and NETCONF / RESTCONF protocol, path computation element protocol, or MIB data model and SNMP. The present disclosure is not limited in this respect.

[0167] Using process 500, external IP interface management may also be implemented for an IP router node.

[0168] It should be understood that Figure 4 and Figure 5 This is for illustration only and is not intended to be limiting. The operations in processes 400 and 500 may be implemented in any suitable combination.

[0169] Example implementation of method

[0170] Corresponding to the above process, the exemplary embodiments of the present disclosure also provide a communication method. Figure 6 FIG. 6 is a flow chart showing an example method 600 implemented at a device according to some embodiments of the present disclosure. For the purpose of discussion, reference will be made to Figure 2 Method 600 is described.

[0171] At block 610, a device (eg, UE / DS-TT module 211) sends an indication of a device-side IP interface of an IP router node to a first core network element (eg, SMF 214).

[0172] In some embodiments, the UE / DS-TT module 211 may send the indication in the PDU setup request. In some embodiments, the PDU setup request may also include a PCO value indicating the configuration of the device-side IP interface.

[0173] In some embodiments, the UE / DS-TT module 211 may send the indication in a DHCP request. In some embodiments, the DHCP request may include an identifier dedicated to the device-side Internet Protocol interface as the indication.

[0174] At block 620, the UE / DS-TT module 211 receives IP address information for the device-side IP interface from the SMF 214 or a second core network element (eg, TSCTSF 217). In some embodiments, the UE / DS-TT module 211 may receive the IP address information via a PMIC or NASSM message.

[0175] In some embodiments, the UE / DS-TT module 211 may send the IP management capability of the device-side IP interface to the SMF 214 or the TSCTSF 217. In some embodiments, the UE / DS-TT module 211 may send the IP management capability via a PMIC or NAS SM message. Then, the UE / DS-TT module 211 may receive IP configuration information updated based on the IP management capability from the SMF 214 or the TSCTSF 217.

[0176] In this way, the external IP interface at the UE / DS-TT module can be managed.

[0177] Figure 7 FIG. 7 is a flow chart showing an example method 700 implemented at a core network element according to some embodiments of the present disclosure. For the purpose of discussion, reference will be made to Figure 2 Method 700 is described.

[0178] At block 710, a first core network element (eg, SMF 214) receives an indication of a device-side IP interface of an IP router node from a device (eg, UE / DS-TT module 211).

[0179] In some embodiments, the SMF 214 may receive the indication in a PDU setup request. In some embodiments, the PDU setup request may also include a PCO value indicating the configuration of the device-side IP interface.

[0180] In some embodiments, SMF 214 may send the indication in a DHCP request. In some embodiments, the DHCP request may include an identifier dedicated to the device-side Internet Protocol interface as the indication.

[0181] At block 720, the SMF 214 sends the IP address information of the device-side IP interface to the UE / DS-TT module 211. In some embodiments, the UE / DS-TT module 211 may send the IP address information via a NAS SM message.

[0182] In some embodiments, SMF 214 may receive IP management capabilities of the device-side IP interface from UE / DS-TT module 211. In some embodiments, SMF 214 may receive IP management capabilities via PMIC or NAS SM messages. SMF 214 may then send IP configuration information updated based on the IP management capabilities to UE / DS-TT module 211.

[0183] In some embodiments, SMF 214 may send the IP address information to the second core network element (eg, TSCTSF 217). In some embodiments, SMF 214 may also send IP configuration information for the device-side IP interface to TSCTSF 217.

[0184] In some embodiments, the SMF 214 may determine an interface number for the device-side IP interface and an identifier of a PDU session associated with the device-side IP interface, and bind the interface number to the IP address information and the identifier of the PDU session. In some embodiments, if the IP address information of the device 310 is available, the SMF 214 may bind the interface number to the IP address information of the device 310, the IP address information of the device-side IP interface, and the identifier of the PDU session.

[0185] In this way, the core network element may be enabled as the owner of management for the external IP interface of the IP router node.

[0186] Figure 8 FIG. 8 is a flow chart showing an example method 800 implemented at a core network element according to some embodiments of the present disclosure. For the purpose of discussion, reference will be made to Figure 2 Method 800 is described.

[0187] At block 810, a first core network element (eg, SMF 214) receives an indication of a device-side IP interface of an IP router node from a device (eg, UE / DS-TT module 211).

[0188] In some embodiments, the SMF 214 may receive the indication in the PDU setup request. In some embodiments, the PDU setup request may also include a PCO value indicating the configuration of the device-side IP interface.

[0189] In some embodiments, SMF 214 may send the indication in a DHCP request. In some embodiments, the DHCP request may include an identifier dedicated to the device-side Internet Protocol interface as the indication.

[0190] In block 820, SMF 214 sends the interface number for the device-side IP interface and the identifier of the IP router node to the second core network element (eg, TSCTSF 217) for allocation of IP address information for the device-side IP interface.

[0191] In some embodiments, SMF 214 may send a first request for obtaining at least one of IP address information or IP configuration information for the device-side IP interface to a third core network element (e.g., UDM 216). SMF 214 may receive at least one of IP address information or IP configuration information from UDM 216 and send it to TSCTSF 217. In some embodiments, SMF 214 may send the first request in response to receiving a second request for obtaining at least one of IP address information or IP configuration information for the device-side IP interface from TSCTSF 217.

[0192] In some embodiments, the first request and the second request include at least one of the following items: an identifier of the device, or a pairing of an identifier of an IP router node and an interface number of an IP interface on the device side. In some embodiments, SMF 214 may derive a pairing of an identifier of an IP router node and an interface number of an IP interface on the device side from the GPSI of the device.

[0193] In some embodiments, SMF 214 may receive IP management capabilities of the device-side IP interface from UE / DS-TT module 211, and send the IP management capabilities of the device-side IP interface to TSCTSF 217. Then, SMF 214 may receive IP configuration information updated based on the IP management capabilities from TSCTSF 217.

[0194] In this way, the core network element may be enabled as a learner for management of the external IP interface of the IP router node.

[0195] Fig. 9 FIG. 9 is a flow chart showing an example method 900 implemented at a core network element according to some embodiments of the present disclosure. For the purpose of discussion, reference will be made to Figure 2 Method 900 is described.

[0196] In box 910, the second core network element (e.g., TSCTSF 217) receives the interface number of the device-side IP interface of the IP router node and the identifier of the IP router node from the first core network element (e.g., SMF 214), and the interface number corresponds to the protocol data unit session.

[0197] At block 920, the TSCTSF 217 sends IP address information for the device-side IP interface to the device (eg, UE / DS-TT 210).

[0198] In some embodiments, TSCTSF 217 may determine the Internet Protocol address information for the device-side Internet Protocol interface from a set of preconfigured Internet Protocol address information for the set of device-side Internet Protocol interfaces.

[0199] In some embodiments, TSCTSF 217 may send a request to SMF 214 or to a third core network element (e.g., UDM 216) for obtaining at least one of Internet Protocol address information or Internet Protocol configuration information for a device-side Internet Protocol interface. TSCTSF 217 may receive Internet Protocol address information from SMF 214 or UDM 216.

[0200] In some embodiments, the request includes at least one of: an identification of the device, or a pair of an identification of the Internet Protocol router node and an interface number of the device-side Internet Protocol interface.

[0201] In some embodiments, the TSCTSF 217 may receive the Internet protocol management capability of the external Internet protocol interface from the device (e.g., the UE / DS-TT module 211 or the UPF / NW-TT module 213) via a port management information container, a user plane node management information container, or a non-access layer message. The TSCTSF 217 may send Internet protocol configuration information updated based on the Internet protocol management capability to the device via a port management information container, a user plane node management information container, or a non-access layer message.

[0202] In some embodiments, TSCTSF 217 may bind the interface number to the IP address information corresponding to the PDU session. In some embodiments, if the IP address information of device 310 is available, TSCTSF 217 may bind the interface number to the IP address information of the device-side IP interface corresponding to the PDU session and the IP address information of device 310.

[0203] In some embodiments, TSCTSF 217 may receive the interface number of the network side IP interface of the IP router node and at least one of the IP address information or IP configuration information of the network side IP interface from UPF / NW-TT 213. TSCTSF 217 may bind the interface number of the network side IP interface with at least one of the IP address information or IP configuration information of the network side IP interface.

[0204] In some embodiments, TSCTSF 217 may generate information of an IP router node. The information includes: an identifier of the IP router node; at least one of the interface number and IP address information or IP configuration information for the device-side IP interface; and at least one of the interface number and IP address information or IP configuration information for the network-side IP interface. Then, TSCTSF 217 may expose the information of the IP router node to the controller.

[0205] In this way, the core network element may also be enabled as the owner of management for the external IP interface of the IP router node.

[0206] Fig.10 FIG. 1 is a flow chart showing an example method 1000 implemented at a core network element according to some embodiments of the present disclosure. For the purpose of discussion, reference will be made to Figure 2 Method 1000 is described.

[0207] In box 1010, the second core network element (e.g., TSCTSF 217) receives Internet Protocol address information for the device-side IP interface of the IP router node and the interface number of the device-side IP interface corresponding to the PDU session from the first core network element (e.g., SMF214).

[0208] In some embodiments, if the IP address information of the device 310 is available, the TSCTSF 217 may bind the interface number with the IP address information of the device-side IP interface corresponding to the PDU session and the IP address information of the device 310 .

[0209] In some embodiments, TSCTSF 217 may receive the interface number of the network-side IP interface of the IP router node and at least one of the IP address information or IP configuration information of the network-side IP interface from UPF / NW-TT 213. TSCTSF 217 may bind the interface number of the network-side IP interface with at least one of the IP address information or IP configuration information of the network-side IP interface.

[0210] In block 1011, TSCTSF 217 generates information of an Internet Protocol router node. The information includes: an identifier of the IP router node; an interface number and at least one of IP address information or IP configuration information for a device-side IP interface; and an interface number and at least one of IP address information or IP configuration information for a network-side IP interface.

[0211] At block 1012, the TSCTSF 217 exposes the information of the IP router node to the controller.

[0212] In some embodiments, the TSCTSF 217 may receive at least one of Internet Protocol address information or Internet Protocol configuration information for an external IP interface from a device (e.g., a UE / DS-TT module 211 or a UPF / NW-TT module 213) via a port management information container, a user plane node management information container, or a non-access layer message.

[0213] In this way, core network elements may also be enabled as learners for management of external IP interfaces of IP router nodes.

[0214] Fig.11 FIG. 1 is a flow chart showing an example method 1100 implemented at a core network element according to some embodiments of the present disclosure. For the purpose of discussion, reference will be made to Figure 2 Method 1100 is described.

[0215] In box 1110, the third core network network element (e.g., UDM 216) receives a request for obtaining at least one of Internet Protocol address information or Internet Protocol configuration information for a device-side Internet Protocol interface of an Internet Protocol router node from the first core network network element (e.g., SMF 214) or from the second core network network element (e.g., TSCTSF 217).

[0216] In block 1120 , the UDM 216 sends at least one of the Internet Protocol address information or the Internet Protocol configuration information to the SMF 214 or the TSCTSF 217 .

[0217] In some embodiments, the request includes at least one of: an identification of the device, or a pair of an identification of an Internet Protocol router node and an interface number of a device-side Internet Protocol interface.

[0218] In some embodiments, UDM 216 stores the subscription information of the device in association with at least one of: a pairing of an identification of an Internet Protocol router node and an interface number of a device-side Internet Protocol interface, Internet Protocol address information, or Internet Protocol configuration information.

[0219] In this way, the core network element can support the management of the external IP interface of the IP router node.

[0220] It should be noted that the operations of the above method may correspond to the operations of the above processes 400 and 500, so for the sake of brevity, other details are not repeated here.

[0221] Example implementations of apparatus and devices

[0222] The example embodiments of the present disclosure also provide corresponding devices. In some embodiments, the device capable of performing one of the methods 600 to 1100 may include a component for performing the corresponding steps of one of the methods 600 to 1100. The component can be implemented in any suitable form. For example, the component can be implemented in a circuit system or a software module.

[0223] Fig.12 1 is a simplified block diagram of a device 1200 suitable for implementing embodiments of the present disclosure. The device 1200 may be provided to implement a communication device, such as Figure 2 The device 1200 includes one or more processors 1210, one or more memories 1220 coupled to the processors 1210, and one or more communication modules 1240 coupled to the processors 1210.

[0224] The communication module 1240 is used for two-way communication. The communication module 1240 has at least one antenna to facilitate communication. The communication interface may represent any interface required to communicate with other network elements.

[0225] Processor 1210 may be of any type suitable for the local technology network, and may include, as non-limiting examples, one or more of the following: a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 1200 may have multiple processors, such as application specific integrated circuit chips that are time slaved to a clock that synchronizes a main processor.

[0226] The memory 1220 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 1224, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disk (CD), digital video disk (DVD), and other magnetic storage devices and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 1222 and other volatile memories that do not persist during power-off periods.

[0227] Computer program 1230 includes computer executable instructions executed by associated processor 1210. Program 1230 may be stored in ROM 1220. Processor 1210 may perform any suitable actions and processes by loading program 1230 into RAM 1220.

[0228] The embodiments of the present disclosure may be implemented by means of the program 1230, so that the device 1200 may execute the reference Figures 4 to 11 Any process of the present disclosure discussed. The embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0229] In some embodiments, the program 1230 may be tangibly embodied in a computer-readable medium, which may be included in the device 1200 (such as in the memory 1220) or in other storage devices accessible by the device 1200. The device 1200 may load the program 1230 from the computer-readable medium to the RAM 1222 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Fig.13 An example of a computer readable medium 1300 in the form of a CD or DVD is shown. The computer readable medium has the program 1230 stored thereon.

[0230] Generally, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be run by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are shown and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof.

[0231] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer executable instructions such as those included in program modules that are executed in a device on a target real or virtual processor to perform the above-referenced Figures 6 to 11The methods 600 to 1100 are described. In general, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The functionality of program modules can be combined or separated between program modules as desired in various embodiments. The machine executable instructions of program modules can be run in local devices or distributed devices. In distributed devices, program modules can be located in local storage media and remote storage media.

[0232] The program code for executing the disclosed method can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code enables the function / operation specified in the flow chart and / or block diagram to be realized when the processor or controller is run. The program code can be run completely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or completely on a remote machine or server.

[0233] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of carriers include signals, computer readable media, etc.

[0234] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable medium may include, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared or semiconductor system, apparatus or device, or any suitable combination of the foregoing. More specific examples of computer readable storage media would include: an electrical connection having one or more conductors, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0235] In summary, the embodiments of the present disclosure can provide the following solutions:

[0236] Item 1. A device comprising:

[0237] at least one processor; and

[0238] at least one memory including computer program code,

[0239] The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to:

[0240] sending an indication of a device-side Internet Protocol interface of an Internet Protocol router node to a first core network element; and

[0241] The Internet Protocol address information for the device-side Internet Protocol interface is received from the first core network element or the second core network element.

[0242] Clause 2. The apparatus of clause 1, wherein the apparatus is caused to send the indication by:

[0243] sending the indication in a protocol data unit session establishment request; or

[0244] The indication is sent in a dynamic host configuration protocol request.

[0245] Item 3. A device according to item 2, wherein the protocol data unit session establishment request also includes a protocol configuration option value indicating a configuration of the device-side Internet Protocol interface.

[0246] Item 4. The device according to Item 2, wherein the dynamic host configuration protocol request includes an identifier specific to the device-side Internet Protocol interface as the indication.

[0247] Item 5. The apparatus of item 1, wherein the apparatus is further configured to:

[0248] Sending the Internet protocol management capability of the device-side Internet protocol interface to the first core network network element or the second core network network element; and

[0249] Receive Internet protocol configuration information updated based on the Internet protocol management capability from the first core network element or the second core network element.

[0250] Clause 6. The apparatus of clause 5, wherein the apparatus is caused to send the Internet Protocol management capabilities by:

[0251] The Internet protocol management capability is sent via a port management information container, a user plane node management information container, or a non-access stratum session management message.

[0252] Clause 7. The apparatus of clause 1, wherein the apparatus is caused to receive the Internet Protocol address information by:

[0253] The Internet Protocol address information is received via a port management information container, a user plane node management information container, or a non-access stratum session management message.

[0254] Item 8. A device according to item 1, wherein the device is a terminal device, the first core network element is a session management function, and the second core network element is a time-sensitive communication and time synchronization function.

[0255] Item 9. A first core network element, comprising:

[0256] at least one processor; and

[0257] at least one memory including computer program code,

[0258] The at least one memory and the computer program code are configured to, together with the at least one processor, cause the first core network element to:

[0259] receiving, from the device, an indication of a device-side Internet Protocol interface of an Internet Protocol router node; and

[0260] The Internet Protocol address information of the Internet Protocol interface on the device side is sent to the device.

[0261] Item 10. The first core network element according to Item 9, wherein the first core network element is configured to receive the indication by:

[0262] receiving the indication in a protocol data unit session establishment request; or

[0263] The indication is received in a dynamic host configuration protocol request.

[0264] Item 11. The first core network element according to Item 9, wherein the first core network element is further configured to:

[0265] receiving Internet Protocol management capabilities of the device-side Internet Protocol interface from the device; and

[0266] Internet protocol configuration information updated based on the Internet protocol management capability is sent to the device.

[0267] Item 12. The first core network element according to Item 9, wherein the first core network element is further configured to:

[0268] The Internet Protocol address information is sent to the second core network element.

[0269] Item 13. The first core network element according to Item 12, wherein the first core network element is further configured to:

[0270] Send Internet Protocol configuration information for the device-side Internet Protocol interface to the second core network network element.

[0271] Item 14. The first core network element according to Item 9, wherein the first core network element is further configured to:

[0272] determining an interface number for the device-side Internet Protocol interface and an identification of a protocol data unit session associated with the device-side Internet Protocol interface; and

[0273] The interface number is bound to the internet protocol address information and the identifier of the protocol data unit session.

[0274] Item 15. A first core network element, comprising:

[0275] at least one processor; and

[0276] at least one memory including computer program code,

[0277] The at least one memory and the computer program code are configured to, together with the at least one processor, cause the first core network element to:

[0278] receiving, from the device, an indication of a device-side Internet Protocol interface of an Internet Protocol router node; and

[0279] An interface number for the device-side Internet Protocol interface and an identifier of the Internet Protocol router node are sent to the second core network network element for allocation of Internet Protocol address information of the device-side Internet Protocol interface.

[0280] Item 16. The first core network element according to Item 15, wherein the first core network element is further configured to:

[0281] Sending a first request to a third core network network element for obtaining at least one of Internet Protocol address information or Internet Protocol configuration information for the device-side Internet Protocol interface;

[0282] receiving the at least one of the Internet Protocol address information or the Internet Protocol configuration information from the third core network element; and

[0283] Sending at least one of the Internet Protocol address information or the Internet Protocol configuration information to the second core network element.

[0284] Item 17. The first core network element according to item 16, wherein the first core network element is caused to send the first request by:

[0285] The first request is sent in response to receiving a second request from the second core network element for obtaining at least one of Internet Protocol address information or Internet Protocol configuration information for the device-side Internet Protocol interface.

[0286] Item 18. A first core network element according to Item 17, wherein the first request and the second request include at least one of the following: an identification of the device, or a pairing of an identification of the Internet Protocol router node and an interface number of the Internet Protocol interface on the device side.

[0287] Item 19. The first core network element according to Item 18, wherein the first core network element is further configured to:

[0288] A pair of an identification of the Internet Protocol router node and an interface number of the device-side Internet Protocol interface is derived from a universal public subscription identifier of the device.

[0289] Item 20. The first core network element according to Item 15, wherein the first core network element is further configured to:

[0290] receiving Internet Protocol management capabilities of the device-side Internet Protocol interface from the device;

[0291] Sending the Internet protocol management capability of the device-side Internet protocol interface to the second core network network element; and

[0292] Receive Internet protocol configuration information updated based on the Internet protocol management capability from the second core network element.

[0293] Item 21. A second core network element, comprising:

[0294] at least one processor; and

[0295] at least one memory including computer program code,

[0296] The at least one memory and the computer program code are configured to, together with the at least one processor, cause the second core network element to:

[0297] receiving, from the first core network element, an interface number of a device-side Internet protocol interface for an Internet protocol router node and an identification of the Internet protocol router node, the interface number corresponding to a protocol data unit session; and

[0298] Internet protocol address information for the device-side Internet protocol interface is sent to the device.

[0299] Item 22. The second core network element according to Item 21, wherein the second core network element is further configured to:

[0300] The Internet Protocol address information for the device-side Internet Protocol interface is determined from a set of preconfigured Internet Protocol address information for a set of device-side Internet Protocol interfaces.

[0301] Item 23. The second core network element according to Item 22, wherein the second core network element is further configured to:

[0302] Sending a request for obtaining at least one of Internet Protocol address information or Internet Protocol configuration information for the device-side Internet Protocol interface to the first core network element or the third core network element; and

[0303] The Internet Protocol address information is received from the first core network element or the third core network element.

[0304] Item 24. A second core network element according to Item 23, wherein the request comprises at least one of the following: an identification of the device, or a pairing of an identification of the Internet Protocol router node and an interface number of the Internet Protocol interface on the device side.

[0305] Item 25. The second core network element according to Item 21, wherein the second core network element is further configured to:

[0306] receiving, from the device via a port management information container, a user plane node management information container, or a non-access stratum message, internet protocol management capabilities of an external internet protocol interface; and

[0307] The Internet protocol configuration information updated based on the Internet protocol management capability is sent to the device via a port management information container, a user plane node management information container or a non-access layer message.

[0308] Item 26. The second core network element according to Item 21, wherein the second core network element is further configured to:

[0309] The interface number is bound to the Internet Protocol address information corresponding to the protocol data unit session.

[0310] Item 27. The second core network element according to Item 21, wherein the second core network element is further configured to:

[0311] generating information of the Internet Protocol router node, the information comprising an identifier of the Internet Protocol router node, the interface number, and the Internet Protocol address information; and

[0312] The information of the Internet Protocol router node is exposed to a controller.

[0313] Item 28. A second core network element, comprising:

[0314] at least one processor; and

[0315] at least one memory including computer program code,

[0316] The at least one memory and the computer program code are configured to, together with the at least one processor, cause the second core network element to:

[0317] receiving, from the first core network network element, Internet protocol address information for a device-side Internet protocol interface of an Internet protocol router node and an interface number of the device-side Internet protocol interface corresponding to a protocol data unit session;

[0318] generating information of the Internet Protocol router node, the information comprising an identifier of the Internet Protocol router node, the interface number, and the Internet Protocol address information; and

[0319] The information of the Internet Protocol router node is exposed to a controller.

[0320] Item 29. The second core network element according to Item 28, wherein the second core network element is further configured to:

[0321] At least one of Internet Protocol address information or Internet Protocol configuration information for an external IP interface is received from the device via a port management information container, a user plane node management information container, or a non-access layer message.

[0322] Item 30. A third core network element, comprising:

[0323] at least one processor; and

[0324] at least one memory including computer program code,

[0325] The at least one memory and the computer program code are configured to, together with the at least one processor, cause the third core network element to:

[0326] receiving a request for obtaining at least one of Internet Protocol address information or Internet Protocol configuration information for a device-side Internet Protocol interface of an Internet Protocol router node from the first core network element or from the second core network element; and

[0327] Send at least one of the Internet Protocol address information or the Internet Protocol configuration information to the first core network network element or to the second core network network element.

[0328] Item 31. A third core network element according to Item 30, wherein the request comprises at least one of the following: an identification of the device, or a pairing of an identification of an Internet Protocol router node and an interface number of an Internet Protocol interface on the device side.

[0329] Item 32. The third core network element according to Item 30, wherein the third core network element is further configured to:

[0330] The subscription information of the device is stored in association with at least one of: a pairing of an identification of an Internet Protocol router node and an interface number of an Internet Protocol interface on the device side, Internet Protocol address information, or Internet Protocol configuration information.

[0331] Item 33. A method of communication, comprising:

[0332] At the device, sending an indication of the device-side Internet Protocol interface of the Internet Protocol router node to the first core network element; and

[0333] Receive Internet Protocol address information for the device-side Internet Protocol interface from the first core network element or the second core network element.

[0334] Item 34. A method of communication, comprising:

[0335] At the first core network element, receiving from the device an indication of a device-side Internet Protocol interface of an Internet Protocol router node; and

[0336] The Internet Protocol address information of the Internet Protocol interface on the device side is sent to the device.

[0337] Item 35. A method of communication, comprising:

[0338] At the first core network element, receiving from the device an indication of a device-side Internet Protocol interface of an Internet Protocol router node; and

[0339] The interface number of the device-side Internet Protocol interface, the identifier of the Internet Protocol router node and the identifier of the protocol data unit session are sent to the second core network network element so that the second core network network element can allocate Internet Protocol address information of the device-side Internet Protocol interface.

[0340] Item 36. A method of communication, comprising:

[0341] receiving, at the second core network element, an interface number of a device-side Internet protocol interface for an Internet protocol router node and an identification of the Internet protocol router node from the first core network element, the interface number corresponding to the protocol data unit session; and

[0342] Send Internet Protocol address information for the device-side Internet Protocol interface to the first core network network element.

[0343] Item 37. A method of communication, comprising:

[0344] receiving, at the second core network network element, from the first core network network element, Internet protocol address information for a device-side Internet protocol interface of an Internet protocol router node and an interface number of the device-side Internet protocol interface corresponding to the protocol data unit session;

[0345] generating information of the Internet Protocol router node, the information comprising an identifier of the Internet Protocol router node, the interface number, and the Internet Protocol address information; and

[0346] The information of the Internet Protocol router node is exposed to a controller.

[0347] Item 38. A method of communication, comprising:

[0348] receiving, at the third core network element, from the first core network element or from the second core network element via the first core network element, a request for obtaining at least one of Internet Protocol address information or Internet Protocol configuration information for a device-side Internet Protocol interface of an Internet Protocol router node; and

[0349] Send at least one of the Internet Protocol address information or the Internet Protocol configuration information to the first core network network element or to the second core network element via the first core network element.

[0350] Item 39. A communication device, comprising:

[0351] means for sending, at the device, to the first core network element, an indication of the device-side Internet Protocol interface of the Internet Protocol router node; and

[0352] A component for receiving Internet Protocol address information for the device-side Internet Protocol interface from the first core network element or the second core network element.

[0353] Item 40. A communication device, comprising:

[0354] means for receiving, at a first core network element, from a device an indication of a device-side Internet Protocol interface of an Internet Protocol router node; and

[0355] A component for sending Internet Protocol address information of the device-side Internet Protocol interface to the device.

[0356] Item 41. A communication device, comprising:

[0357] means for receiving, at a first core network element, from a device an indication of a device-side Internet Protocol interface of an Internet Protocol router node; and

[0358] A component for sending the interface number of the device-side Internet Protocol interface, the identifier of the Internet Protocol router node and the identifier of the protocol data unit session to the second core network network element, so that the second core network network element allocates the Internet Protocol address information of the device-side Internet Protocol interface.

[0359] Item 42. A communication device, comprising:

[0360] means for receiving, at the second core network element, from the first core network element, an interface number of a device-side Internet protocol interface for an Internet protocol router node and an identification of the Internet protocol router node, the interface number corresponding to the protocol data unit session; and

[0361] A component for sending Internet Protocol address information for the device-side Internet Protocol interface to the first core network element.

[0362] Item 43. A communication device, comprising:

[0363] means for receiving, at the second core network element, from the first core network element, internet protocol address information for the device-side internet protocol interface of the internet protocol router node and an interface number of the device-side internet protocol interface corresponding to the protocol data unit session;

[0364] means for generating information of said Internet Protocol router node, said information comprising an identification of said Internet Protocol router node, said interface number and said Internet Protocol address information; and

[0365] A component for exposing information of an Internet Protocol router node to a controller.

[0366] Item 44. A communication device, comprising:

[0367] means for receiving, at a third core network element, from the first core network element, or from the second core network element via the first core network element, a request for obtaining at least one of internet protocol address information or internet protocol configuration information for a device-side internet protocol interface of an internet protocol router node; and

[0368] A component for transmitting at least one of the Internet Protocol address information or the Internet Protocol configuration information to the first core network element or to the second core network element via the first core network element.

[0369] Item 45. A non-transitory computer-readable medium comprising program instructions for causing a device to perform a method according to any one of Items 33 to 38.

[0370] In addition, although operations are described in a particular order, this should not be understood as requiring the specific order shown or to perform these operations in sequence, or to perform all the operations shown, to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these details should not be interpreted as limitations on the scope of the present disclosure, but should be interpreted as descriptions of features peculiar to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.

[0371] Although the disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or actions described above. Instead, the specific features and actions described above are disclosed as example forms of implementing the claims.

Claims

1. A device comprising: at least one processor; as well as at least one memory including computer program code, The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to: Sending an indication of a device-side Internet Protocol interface of an Internet Protocol router node to a first core network network element; as well as Receive Internet Protocol address information for the device-side Internet Protocol interface from the first core network element or the second core network element.

2. The apparatus according to claim 1, wherein the apparatus is caused to send the indication by: sending the indication in a protocol data unit session establishment request; or The indication is sent in a dynamic host configuration protocol request. 3 . The device according to claim 2 , wherein the protocol data unit session establishment request further comprises a protocol configuration option value indicating a configuration of the device-side Internet Protocol interface. 4 . The device according to claim 2 , wherein the dynamic host configuration protocol request includes an identifier specific to the device-side Internet Protocol interface as the indication.

5. The apparatus of claim 1, wherein the apparatus is further configured to: Sending the Internet protocol management capability of the device-side Internet protocol interface to the first core network network element or the second core network network element; and Receive Internet protocol configuration information updated based on the Internet protocol management capability from the first core network element or the second core network element.

6. The apparatus of claim 5, wherein the apparatus is caused to send the Internet Protocol management capabilities by: sending the Internet Protocol management capabilities via a port management information container, a user plane node management information container, or a non-access stratum session management message; and The device is configured to receive the Internet protocol configuration information in the following manner: receiving the Internet protocol configuration information via a port management information container, a user plane node management information container or a non-access layer session management message.

7. The device of claim 1, wherein the device is caused to receive the Internet Protocol address information by: The Internet protocol address information is received via a port management information container, a user plane node management information container or a non-access layer session management message.

8. The device according to claim 1, wherein the device is a terminal device or a terminal device with a device-side time-sensitive network converter, the first core network element is a session management function, and the second core network element is a time-sensitive communication and time synchronization function.

9. A first core network element, comprising: at least one processor; as well as at least one memory including computer program code, The at least one memory and the computer program code are configured to, together with the at least one processor, cause the first core network element to: receiving, from the device, an indication of a device-side Internet Protocol interface of an Internet Protocol router node; as well as The Internet Protocol address information of the Internet Protocol interface on the device side is sent to the device.

10. The first core network element according to claim 9, wherein the first core network element is configured to receive the indication in the following manner: receiving the indication in a protocol data unit session establishment request; or The indication is received in a dynamic host configuration protocol request.

11. The first core network element according to claim 9, wherein the first core network element is further configured to: receiving Internet Protocol management capabilities of the device-side Internet Protocol interface from the device; and Internet protocol configuration information updated based on the Internet protocol management capability is sent to the device.

12. The first core network element according to claim 9, wherein the first core network element is further configured to: The Internet Protocol address information is sent to the second core network element.

13. The first core network element according to claim 12, wherein the first core network element is further configured to: Send Internet Protocol configuration information for the device-side Internet Protocol interface to the second core network network element.

14. The first core network element according to claim 9, wherein the first core network element is further configured to: determining an interface number of the device-side Internet Protocol interface and an identifier of a protocol data unit session associated with the device-side Internet Protocol interface; and The interface number is bound to the internet protocol address information and the identifier of the protocol data unit session.

15. The first core network element according to claim 14, wherein the first core network element is configured to bind the interface number in the following manner: Based on determining that the Internet Protocol address information of the device is available, the interface number is bound to the following items: the Internet Protocol address information of the device-side Internet Protocol interface, the Internet Protocol address information of the device, and the identifier of the protocol data unit session associated with the interface number.

16. A second core network element, comprising: at least one processor; as well as at least one memory including computer program code, The at least one memory and the computer program code are configured to, together with the at least one processor, cause the second core network element to: receiving, from a first core network network element, an interface number of a device-side Internet protocol interface for an Internet protocol router node and an identifier of the Internet protocol router node, the interface number corresponding to a protocol data unit session; as well as Internet protocol address information for the device-side Internet protocol interface is sent to the device.

17. The second core network element according to claim 16, wherein the second core network element is further configured to: The Internet Protocol address information for the device-side Internet Protocol interface is determined from a set of preconfigured Internet Protocol address information for a set of device-side Internet Protocol interfaces.

18. The second core network element according to claim 16, wherein the second core network element is further configured to: Sending a request for acquiring at least one of Internet Protocol address information or Internet Protocol configuration information for the device-side Internet Protocol interface to the first core network element or the third core network element; and The Internet Protocol address information is received from the first core network element or the third core network element.

19. The second core network element according to claim 18, wherein the request comprises at least one of the following items: an identification of the device, or a pairing of the identification of the Internet Protocol router node and the interface number of the Internet Protocol interface on the device side.

20. The second core network element according to claim 16, wherein the second core network element is further configured to: receiving, from the device via a port management information container, a user plane node management information container or a non-access layer message, Internet protocol management capabilities of the device-side Internet protocol interface; and The Internet protocol configuration information updated based on the Internet protocol management capability is sent to the device via a port management information container, a user plane node management information container or a non-access layer message.

21. The second core network element according to claim 16, wherein the second core network element is further configured to: The interface number is bound to the Internet Protocol address information corresponding to the protocol data unit session.

22. The second core network element according to claim 21, wherein the second core network element is configured to bind the interface number in the following manner: Based on determining that the Internet Protocol address information of the device is available, the interface number is bound with the Internet Protocol address information of the device-side Internet Protocol interface and the Internet Protocol address information of the device.

23. The second core network element according to claim 21, wherein the second core network element is further configured to: receiving from another device at least one of Internet Protocol address information or Internet Protocol configuration information of a network-side Internet Protocol interface of the Internet Protocol router node and an interface number of the network-side Internet Protocol interface; and The interface number of the network-side Internet Protocol interface is bound to the at least one item of the Internet Protocol address information or the Internet Protocol configuration information of the network-side Internet Protocol interface.

24. The second core network element according to claim 23, wherein the second core network element is further configured to: Generate information of the Internet Protocol router node, the information of the Internet Protocol router node comprising: said identification of said Internet Protocol router node, the at least one of the internet protocol address information or internet protocol configuration information for the device-side internet protocol interface and the interface number for the device-side internet protocol interface, and at least one of the Internet Protocol address information or Internet Protocol configuration information for the network-side Internet Protocol interface and the interface number for the device-side Internet Protocol interface; as well as The information of the internet protocol router node is exposed to a controller.

25. A third core network element, comprising: at least one processor; as well as at least one memory including computer program code, The at least one memory and the computer program code are configured to, together with the at least one processor, cause the third core network element to: receiving, from the first core network element or from the second core network element, a request for obtaining at least one of Internet Protocol address information or Internet Protocol configuration information for a device-side Internet Protocol interface of an Internet Protocol router node; as well as Send at least one of the Internet Protocol address information or the Internet Protocol configuration information to the first core network network element or to the second core network network element.

26. The third core network element according to claim 25, wherein the request comprises at least one of the following: an identification of a device, or a pairing of an identification of the Internet Protocol router node and an interface number of the Internet Protocol interface on the device side.

27. The third core network element according to claim 25, wherein the third core network element is further configured to: The subscription information of the device is stored in association with at least one of the following items: a pairing of an identification of the Internet Protocol router node and an interface number of the device-side Internet Protocol interface, the Internet Protocol address information, or the Internet Protocol configuration information.

28. A method of communication, comprising: At the device, sending an indication of a device-side Internet Protocol interface of an Internet Protocol router node to a first core network element; as well as Receive Internet Protocol address information for the device-side Internet Protocol interface from the first core network element or the second core network element.

29. The method of claim 28, wherein sending the indication comprises: sending the indication in a protocol data unit session establishment request; or The indication is sent in a dynamic host configuration protocol request.

30. The method of claim 28, further comprising: Sending the Internet protocol management capability of the device-side Internet protocol interface to the first core network network element or the second core network network element; as well as Receive Internet protocol configuration information updated based on the Internet protocol management capability from the first core network element or the second core network element.

31. The method of claim 30, wherein sending the Internet Protocol management capabilities comprises: sending the internet protocol management capability via a port management information container, a user plane node management information container, or a non-access stratum session management message; as well as The receiving of the Internet protocol configuration information includes: receiving the Internet protocol configuration information via a port management information container, a user plane node management information container or a non-access layer session management message.

32. The method of claim 28, wherein receiving the Internet Protocol address information comprises: The Internet Protocol address information is received via a port management information container, a user plane node management information container, or a non-access stratum session management message.

33. A method of communication, comprising: At the first core network element, receiving from the device an indication of a device-side Internet Protocol interface of an Internet Protocol router node; as well as The Internet Protocol address information of the Internet Protocol interface on the device side is sent to the device.

34. The method of claim 33, wherein receiving the indication comprises: receiving the indication in a protocol data unit session establishment request; or The indication is received in a dynamic host configuration protocol request.

35. The method of claim 33, further comprising: receiving Internet Protocol management capabilities of the device-side Internet Protocol interface from the device; as well as Internet protocol configuration information updated based on the Internet protocol management capability is sent to the device.

36. The method of claim 33, further comprising: The Internet Protocol address information is sent to the second core network element.

37. A method of communication, comprising: receiving, at the second core network network element, from the first core network network element, an interface number of a device-side Internet protocol interface of an Internet protocol router node and an identifier of the Internet protocol router node, the interface number corresponding to a protocol data unit session; as well as Internet protocol address information for the device-side Internet protocol interface is sent to the device.

38. The method of claim 37, further comprising: The Internet Protocol address information for the device-side Internet Protocol interface is determined from a set of preconfigured Internet Protocol address information for a set of device-side Internet Protocol interfaces.

39. The method of claim 37, further comprising: Sending a request to the first core network element or the third core network element for obtaining at least one of Internet Protocol address information or Internet Protocol configuration information for the device-side Internet Protocol interface; as well as The Internet Protocol address information is received from the first core network element or the third core network element.

40. The method of claim 39, wherein the request comprises at least one of: an identification of the device, or a pairing of the identification of the Internet Protocol router node and the interface number of the device-side Internet Protocol interface.

Images