[go: up one dir, main page]

WO2023212872A1 - Gestion d'interface ip externe dans un nœud de routeur ip 5gs - Google Patents

Gestion d'interface ip externe dans un nœud de routeur ip 5gs Download PDF

Info

Publication number
WO2023212872A1
WO2023212872A1 PCT/CN2022/091030 CN2022091030W WO2023212872A1 WO 2023212872 A1 WO2023212872 A1 WO 2023212872A1 CN 2022091030 W CN2022091030 W CN 2022091030W WO 2023212872 A1 WO2023212872 A1 WO 2023212872A1
Authority
WO
WIPO (PCT)
Prior art keywords
internet protocol
core network
interface
network element
address information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2022/091030
Other languages
English (en)
Inventor
Hua Chao
Markus Sakari ISOMÄKI
Matti Einari Laitila
Laurent Thiebaut
Wei Xing Wang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
Original Assignee
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Shanghai Bell Co Ltd, Nokia Solutions and Networks Oy filed Critical Nokia Shanghai Bell Co Ltd
Priority to CN202280095551.3A priority Critical patent/CN119138101A/zh
Priority to PCT/CN2022/091030 priority patent/WO2023212872A1/fr
Publication of WO2023212872A1 publication Critical patent/WO2023212872A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels

Definitions

  • Embodiments of the present disclosure generally relate to the field of telecommunication and in particular, to a method, device, apparatus and computer readable medium for external Internet Protocol (IP) interface management in the fifth generation (5G) system (5GS) as an IP router node.
  • IP Internet Protocol
  • 5GS may operate as a deterministic networking (DetNet) node in a DetNet domain and define generic enablers for time-sensitive networking (TSN) and native time-sensitive communication (TSC) .
  • 5GS as one of the DetNet nodes in the DetNet domain is required to expose all its external visible interfaces to a DetNet controller.
  • UE user equipment
  • DS-TT device-side TSN translator
  • a DS-TT side interface of the device becomes an external IP interface of the 5GS DetNet node.
  • management on such external IP interface of the 5GS DetNet node is still incomplete and needs to be further developed.
  • example embodiments of the present disclosure provide a solution for external IP interface management in a 5GS IP router node.
  • a device comprising 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, with the at least one processor, cause the device to: transmit, to a first core network element, an indication regarding a device-side Internet Protocol interface of an Internet Protocol router node; and receive, from the first core network element or a second core network element, Internet Protocol address information for the device-side Internet Protocol interface.
  • a first core network element comprises 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, with the at least one processor, cause the first core network element to: receive, from a device, an indication regarding a device-side Internet Protocol interface of an Internet Protocol router node; and transmit, to the device, Internet Protocol address information of the device-side Internet Protocol interface.
  • a first core network element comprises 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, with the at least one processor, cause the first core network element to: receive, from a device, an indication regarding a device-side Internet Protocol interface of an Internet Protocol router node; and transmit, to a second core network element, an interface number for the device-side Internet Protocol interface and an identity of the Internet Protocol router node for allocation of Internet Protocol address information of the device-side Internet Protocol interface.
  • a second core network element comprises 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, with the at least one processor, cause the second core network element to: receive, from a first core network element, an interface number for a device-side Internet Protocol interface of an Internet Protocol router node and an identity of the Internet Protocol router node, the interface number corresponding to a protocol data unit session; and transmit, to a device, Internet Protocol address information for the device-side Internet Protocol interface.
  • a second core network element comprises 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, with the at least one processor, cause the second core network element to: receive, from a first core 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; generate information of the Internet Protocol router node, the information comprising the identity 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.
  • a third core network element comprises 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, with the at least one processor, cause the third core network element to: receive, from a first core network element or from a 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; and transmit, to the first core network element or to the second core network element, the at least one of the Internet Protocol address information or Internet Protocol configuration information.
  • a method for communication comprises: transmitting, at a device and to a first core network element, an indication regarding a device-side Internet Protocol interface of an Internet Protocol router node; and receiving, from the first core network element or a second core network element, Internet Protocol address information for the device-side Internet Protocol interface.
  • a method for communication comprises: receiving, at a first core network element and from a device, an indication regarding a device-side Internet Protocol interface of an Internet Protocol router node; and transmitting, to the device, Internet Protocol address information of the device-side Internet Protocol interface.
  • a method for communication comprises: receiving, at a first core network element and from a device, an indication regarding a device-side Internet Protocol interface of an Internet Protocol router node; and transmitting, to a second core network element, an interface number for the device-side Internet Protocol interface, an identity of the Internet Protocol router node and an identity of a protocol data unit session for the second core network element to allocate Internet Protocol address information of the device-side Internet Protocol interface.
  • a method for communication comprises: receiving, at a second core network element and from a first core network element, an interface number for a device-side Internet Protocol interface of an Internet Protocol router node and an identity of the Internet Protocol router node, the interface number corresponding to a protocol data unit session; and transmitting, to the first core network element, Internet Protocol address information for the device-side Internet Protocol interface.
  • a method for communication comprises: receiving, at a second core network element and from a first core 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; generating information of the Internet Protocol router node, the information comprising the identity 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.
  • a method for communication comprises: receiving, at a third core network element and from a first core network element or from a 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 transmitting, to the first core network element or to the second core network element via the first core network element, the at least one of the Internet Protocol address information or Internet Protocol configuration information.
  • apparatus for communication comprises: means for transmitting, at a device and to a first core network element, an indication regarding a device-side Internet Protocol interface of an Internet Protocol router node; and means for receiving, from the first core network element or a second core network element, Internet Protocol address information for the device-side Internet Protocol interface.
  • apparatus for communication comprises: means for receiving, at a first core network element and from a device, an indication regarding a device-side Internet Protocol interface of an Internet Protocol router node; and means for transmitting, to the device, Internet Protocol address information of the device-side Internet Protocol interface.
  • apparatus for communication comprises: means for receiving, at a first core network element and from a device, an indication regarding a device-side Internet Protocol interface of an Internet Protocol router node; and means for transmitting, to a second core network element, an interface number for the device-side Internet Protocol interface, an identity of the Internet Protocol router node and an identity of a protocol data unit session for the second core network element to allocate Internet Protocol address information of the device-side Internet Protocol interface.
  • apparatus for communication comprises: means for receiving, at a second core network element and from a first core network element, an interface number for a device-side Internet Protocol interface of an Internet Protocol router node and an identity of the Internet Protocol router node, the interface number corresponding to a protocol data unit session; and means for transmitting, to the first core network element, Internet Protocol address information for the device-side Internet Protocol interface.
  • apparatus for communication comprises: means for receiving, at a second core network element and from a first core 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; means for generating information of the Internet Protocol router node, the information comprising the identity of the Internet Protocol router node, the interface number and the Internet Protocol address information; and means for exposing the information of the Internet Protocol router node to a controller.
  • apparatus for communication comprises: means for receiving, at a third core network element and from a first core network element or from a 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 means for transmitting, to the first core network element or to the second core network element via the first core network element, the at least one of the Internet Protocol address information or Internet Protocol configuration information.
  • a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform the method according to any of the seventh to twelfth aspects.
  • Fig. 1 illustrates an example DetNet architecture in which embodiments of the present disclosure may be implemented
  • Fig. 2 illustrates an example 5GS DetNet node architecture in which embodiments of the present disclosure may be implemented
  • Fig. 3A illustrates an example IP architecture model for a device acting as a device-side IP interface of a 5GS DetNet node in which embodiments of the present disclosure may be implemented;
  • Fig. 3B illustrates an example IP architecture model for a device acting as a network-side IP interface of a 5GS DetNet node in which embodiments of the present disclosure may be implemented;
  • Fig. 4 illustrates a diagram illustrating a process of communication according to some embodiments of the present disclosure
  • Fig. 5 illustrates a diagram illustrating another process of communication according to some embodiments of the present disclosure
  • Fig. 6 illustrates a flowchart of an example method implemented at a device according to some embodiments of the present disclosure
  • Fig. 7 illustrates a flowchart of an example method implemented at a first core network element according to some embodiments of the present disclosure
  • Fig. 8 illustrates a flowchart of an example method implemented at a first core network element according to some embodiments of the present disclosure
  • Fig. 9 illustrates a flowchart of an example method implemented at a second core network element according to some embodiments of the present disclosure
  • Fig. 10 illustrates a flowchart of an example method implemented at a second core network element according to some embodiments of the present disclosure
  • Fig. 11 illustrates a flowchart of another example method implemented at a third core network element according to some embodiments of the present disclosure
  • Fig. 12 illustrates a simplified block diagram of a device that is suitable for implementing embodiments of the present disclosure.
  • Fig. 13 illustrates a block diagram of an example computer readable medium in accordance with some embodiments of the present disclosure.
  • references in the present disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • 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. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.
  • the term “and/or” includes any and all combinations of one or more of the listed terms.
  • circuitry may refer to one or more or all of the following:
  • circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware.
  • circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
  • the term “communication network” refers to a network following any suitable communication standards, such as Long Term Evolution (LTE) , LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , Narrow Band Internet of Things (NB-IoT) and so on.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • NB-IoT Narrow Band Internet of Things
  • the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) , the future sixth generation (6G) communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.
  • the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom.
  • the network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a NR next generation NodeB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, a low power node such as a femto, a pico, and so forth, depending on the applied terminology and technology.
  • BS base station
  • AP access point
  • NodeB or NB node B
  • eNodeB or eNB evolved NodeB
  • gNB next generation NodeB
  • RRU Remote Radio Unit
  • RH radio header
  • RRH
  • An radio access network (RAN) split architecture comprises a gNB-CU (centralized unit, hosting radio resource control (RRC) , service data adaptation protocol (SDAP) and packet data convergence protocol (PDCP) layers) controlling a plurality of gNB-DUs (distributed unit, hosting radio link control (RLC) , medium access control (MAC) and physical (PHY) layers) .
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • RLC radio link control
  • MAC medium access control
  • PHY physical
  • terminal device refers to any end device that may be capable of wireless communication.
  • a terminal device may also be referred to as a communication device, user equipment (UE) , a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) .
  • UE user equipment
  • SS Subscriber Station
  • MS Mobile Station
  • AT Access Terminal
  • the terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA) , portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , USB dongles, smart devices, wireless customer-premises equipment (CPE) , an Internet of Things (IoT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device and applications (e.g., remote surgery) , an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and/
  • a user equipment apparatus such as a cell phone or tablet computer or laptop computer or desktop computer or mobile IoT device or fixed IoT device
  • This user equipment apparatus can, for example, be furnished with corresponding capabilities as described in connection with the fixed and/or the wireless network node (s) , as appropriate.
  • the user equipment apparatus may be the user equipment and/or or a control device, such as a chipset or processor, configured to control the user equipment when installed therein. Examples of such functionalities include the bootstrapping server function and/or the home subscriber server, which may be implemented in the user equipment apparatus by providing the user equipment apparatus with software configured to cause the user equipment apparatus to perform from the point of view of these functions/nodes.
  • TSN AF TSN application function
  • PMIC port management information container
  • UMIC user plane node management information container
  • TSC time sensitive communication
  • a time sensitive communication and time synchronization function (TSCTSF) is introduced to take care of time synchronization, individual quality of service (QoS) parameters, and TSC assistance container (TSCAC) determination.
  • TSCTSF discovers ingress/egress port (DS-TT or NW-TT) capabilities, configures them and get notifications about configuration updates from them.
  • TSCTSF is able to communicate with DS-TTs and NW-TTs with PMICs and UMICs similarly to TSN AF, depending on their supported capabilities and configuration data models.
  • a DS-TT side interface of the device becomes an IP interface of the 5GS DetNet node.
  • management on such DS-TT side interface of the device is still incomplete and needs to be further developed.
  • an external IP interface in a 5GS IP router node comprises a DS-TT side interface (for convenience, also referred to as a device-side IP interface) and/or a NW-TT side interface (for convenience, also referred to as a network-side IP interface) .
  • the method is designed to configure and discovery IP management information of an external IP interface of a 5GS IP router node.
  • the IP management information may comprise IP address information and IP configuration information.
  • a core network element may configure respective IP address information and IP configuration information to a device-side IP interface or a network-side IP interface. That is, the core network element serves as “management owner” for IP management.
  • a core network element may learn respective IP address information and IP configuration information of a device-side IP interface or a network-side IP interface. That is, the core network element serves as “management learner” for IP management. It is possible to use both modes for different external IP interfaces within the same IP router node.
  • a device transmits indication regarding an external IP interface of an IP router node to a core network element and receives IP address information from the core network element. In this way, an external IP interface at a device-side may be managed.
  • a core network element allocates IP address information for an external IP interface of an IP router node, generates information of the IP router node and exposes the information of the IP router node to an IP router controller. In this way, a core network element may be enabled as an owner for management of an external IP interface of an IP router node.
  • a core network element learns at least IP address information and an interface number for an external IP interface of an IP router node, and bind the interface number to at least the IP address information.
  • a core network element may be enabled as a learner for management of an external IP interface of an IP router node.
  • a core network element stores subscription information of a device in association with at least one of a pair of an identity of an 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, a core network element may support management of an external IP interface of an IP router node.
  • Fig. 1 illustrates an example DetNet architecture 100 in which embodiments of the present disclosure may be implemented.
  • the DetNet architecture 100 is a reference architecture of DetNet network with a centralized controller plane.
  • the DetNet architecture 100 may comprise DetNet end systems 110-1 and 110-2 (for convenience, may also be collectively referred to as a DetNet end system 110 herein) .
  • the DetNet end system 110 may be a robot in factory or any other suitable terminals.
  • the DetNet architecture 100 may also comprise DetNet nodes 120-1, 120-2 and 120-3 (for convenience, may also be collectively referred to as a DetNet node 120 herein) .
  • the DetNet architecture 100 may further comprise 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 DetNet nodes 120. With this information and ability to configure explicit routes and reserve resources along the routes, the DetNet controller may calculate and setup an end-to-end (E2E) deterministic path for DetNet traffic flows according to requests from applications.
  • E2E end-to-end
  • Fig. 1 is merely an example, and the DetNet architecture 100 may comprise any other suitable type or number of elements.
  • Communications in the DetNet architecture 100 may be implemented according to any proper communication protocol (s) , comprising, but not limited to, cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) , the fifth generation (5G) or the future sixth generation (6G) wireless local network communication protocols, and/or any other protocols currently known or to be developed in the future.
  • s any proper communication protocol
  • s comprising, but not limited to, cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) , the fifth generation (5G) or the future sixth generation (6G) wireless local network communication protocols, and/or any other protocols currently known or to be developed in the future.
  • the communication may utilize any proper wireless communication technology, comprising 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 Multiple (OFDM) , Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and/or any other technologies currently known or to be developed in the future.
  • CDMA Code Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • MIMO Multiple-Input Multiple-Output
  • OFDM Orthogonal Frequency Division Multiple
  • DFT-s-OFDM Discrete Fourier Transform spread OFDM
  • one study item is to study whether and how to enable 3GPP support for DetNet such that a mapping is provided between the central DetNet controller entity and the 5GS.
  • the study considers 5GS acting as a one of the DetNet nodes in the Figure 1 in the DetNet domain.
  • IP based DetNet traffic is carried in protocol data unit (PDU) sessions of IP type; mapping functionality for DetNet is realized in the TSCTSF; solutions should reuse functionality of a TSC framework defined in Release 17 where applicable; and granularity of a 5GS DetNet node is per user plane function (UPF) for each network instance; and solutions shall not have any 5G access network (AN) and UE impacts.
  • PDU protocol data unit
  • UPF user plane function
  • the 5GS is extended to support the following: UE is part of a 5GS logical DetNet Node, and thus is not a DetNet node or end system on its own.
  • the 5GS has already defined various ways to configure UE’s IP address information and 5GC internal IP routing information related to the UE.
  • the 5GC and the UE support the following IP address allocation mechanisms:
  • a session management function sends an IP address to UE via non-access-stratum (NAS) session management (SM) signaling or via IPv6 router advertisement.
  • IPv4 address allocation and/or IPv4 parameter configuration via DHCPv4 may also be used once a PDU session is established.
  • IPv6 prefix allocation shall be supported via IPv6 Stateless Auto-configuration, if IPv6 is supported. IPv6 parameter configuration via Stateless DHCPv6 may also be supported.
  • IPv6 address allocation using DHCPv6 may be supported for allocating individual IPv6 address (es) for a PDU session; and IPv6 prefix delegation using DHCPv6 may be supported for allocating additional IPv6 prefixes for a PDU session.
  • framed routing mechanism To support IP routes behind UE, framed routing mechanism has been specified by 3GPP. 3GPP has defined a mechanism called “framed routing” that allows 5GC to be configured with IP prefixes/subnets that should be forwarded to UE in addition to UE’s own or delegated prefixes.
  • the framed route information may be provided to the SMF by a data network-authentication authorization accounting (DN-AAA) server or unified data management (UDM) who stores the information.
  • DNS data network-authentication authorization accounting
  • UDM unified data management
  • the SMF configures them in the UPF using normal packet detection rules (PDR) /forwarding action rules (FAR) .
  • PDR packet detection rules
  • FAR forwarding action rules
  • Fig. 2 illustrates an example 5GS DetNet node architecture 200 in which embodiments of the present disclosure may be implemented.
  • a 5GS DetNet node 210 may comprise a UE/DS-TT module 211, a radio access network (RAN) 212 and a plurality of core network elements such as a UPF/NW-TT module 213, a SMF 214, an access management function (AMF) 215, a UDM 216, a TSCTSF 217, a policy control function (PCF) 218 and a network exposure function (NEF) 219.
  • the TSCTSF may be connected to a DetNet controller 220 via the NEF 219.
  • Fig. 2 is merely an example, and the architecture 200 and the 5GS DetNet node 210 may also comprise any other suitable more or less elements.
  • the UE/DS-TT module 211 may provide an external IP interface #2 of the 5GS DetNet node 210 towards DetNet node or DetNet end system 201.
  • the UPF/NW-TT module 213 may provide an external IP interface #3 of the 5GS DetNet node 210 towards DetNet node or DetNet end system 202.
  • the interface #2 may also be referred to as a device-side IP interface
  • the 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 external IP interfaces of a DetNet node.
  • the UE/DS-TT module 211 may comprise a device (e.g., a terminal device) and a DS-TT and the DS-TT may provide the interface #2.
  • the device may be not accompanied by a DS-TT. That is, the UE/DS-TT module 211 may only comprise the device. In this case, the device provides the interface #2 by itself.
  • the UPF/NW-TT module 213 may comprise a UPF and a NW-TT and the NW-TT may provide the interface #3.
  • a UPF may be not accompanied by a NW-TT. That is, the UPF/NW-TT module 213 may only comprise a UPF. In this case, the UPF provides the interface #3 by itself.
  • a 5GS DetNet node comprises a single UPF and one or more devices.
  • Each device may be accompanied by one or more DS-TTs that provide a 5GS DetNet Node with IP interfaces to an external DetNet network.
  • the UPF may be accompanied by one or more NW-TTs and has a set of IP interfaces that also connect the 5GS DetNet Node to the external DetNet Network.
  • NW-TTs has a set of IP interfaces that also connect the 5GS DetNet Node to the external DetNet Network.
  • only one device-side or network-side IP interface is shown in Fig. 2 and it is to be understood that multiple device-side or network-side IP interfaces may also be feasible.
  • the TSCTSF 217 is responsible for an interaction with the DetNet controller 220.
  • the DetNet controller 220 needs IP topology and routing information of each DetNet node within the DetNet domain as inputs to calculate paths for DetNet traffic flows.
  • DetNet integration into 5GS puts new requirements on 5GS, especially on TSCTSF and TT functionalities.
  • 5GS as one of DetNet nodes in the DetNet domain shall expose all its external visible interfaces to a DetNet controller.
  • a device side when a device joins a 5GS DetNet node, its device-side IP interface becomes an external IP interface of the 5GS DetNet node.
  • the device-side interface as an IP router interface, may need at least an IP address and IP prefix/subnet information.
  • IPv6 prefix delegation may be used to provide additional prefixes besides the prefixes allocated to the interface#1 for a network behind the terminal device.
  • IPv6 prefix delegation also works only for IPv6 but not for IPv4. For UPF/NW-TT module, if UPF or NW-TT provides multiple network-side IP interfaces, these interfaces may need separate configurations.
  • the TSCTSF needs to be aware of the IP address information for all the external IP interfaces of a 5GS DetNet node.
  • the external IP interfaces may have some basic properties such as which IP routing protocol (s) or algorithm (s) and L2 technology they support, what the IP parameters relevant to the IP routing protocol (s) or algorithm (s) , what L2/MAC addresses they have or what their bitrate is.
  • the TSCTSF responsible for the 5GS DetNet Node needs to learn these properties and may also need to configure at least part of these properties.
  • 5GS network functions and terminal device and/or DS-TT/NW-TT in general operate as a DetNet node from IP interface addressing and management and IP routing and packet forwarding perspective. Further, how to allocate IP address for an external IP interface of a DetNet node is to be solved. In addition, it is to be addressed how to learn or configure IP parameters of the external IP interface and how to make the TSCTSF be aware of the IP address and IP parameters of the external IP interface.
  • 3GPP Release 17 defines how TSCTSF and DS-TT/NW-TT can exchange management information containers for TSC, including both UMIC and PMIC.
  • UMIC and PMIC focus on Ethernet layer information, and IP layer information is not defined.
  • Embodiments of the present disclosure provide a solution of external IP interface management in a DetNet node to solve the above and other potential issues. More details will be described below in connection with Figs. 3A to 5.
  • Fig. 3A illustrates an example IP architecture model 300A for a device acting as a device-side IP interface of a 5GS DetNet node in which embodiments of the present disclosure may be implemented.
  • the model 300A will be described with reference to Fig. 2.
  • the model 300A may be implemented at the UE/DS-TT module 211.
  • the UE/DS-TT module 211 may consist of a device 310 and a DS-TT 311.
  • the device 310 may provide a 5G IP interface 320 (i.e., the interface #1 as shown in Fig. 2)
  • the DS-TT 311 may provide a 5GS DetNet node IP interface 321 (i.e., the interface #2 as shown in Fig. 2) .
  • the 5GS DetNet node IP interface 321 corresponds to a device-side IP interface of a DetNet node.
  • the device 310 may be a terminal device.
  • the 5G IP interface 320 is an “ordinary” 5G AN IP interface of the device 310, and the device 310 may be connected to a data network via a UPF.
  • An IP address of the 5G IP interface 320 is allocated or configured by existing means such as NAS SM signaling, IPv6 router advertisement message or dynamic host configuration protocol (DHCP) message.
  • DHCP dynamic host configuration protocol
  • the 5GS DetNet node IP interface 321 is an externally visible interface of the 5GS DetNet Node.
  • the 5GS DetNet node IP interface 321 may be any type of interface that supports IP and DetNet compliant IP QoS, but in practice the 5GS DetNet node IP interface 321 is most often an Ethernet interface.
  • the UE/DS-TT module 211 may only consist of the device 310 and does not comprise the DS-TT 311.
  • the device 310 may provide both the 5G IP interface 320 and the 5GS DetNet node IP interface 321 on its own.
  • Fig. 3B illustrates an example IP architecture model 300B for a device acting as a network-side IP interface of a 5GS DetNet node in which embodiments of the present disclosure may be implemented.
  • the model 300B will be described with reference to Fig. 2.
  • the model 300B may be implemented at the UPF/NW-TT module 213.
  • the UPF/NW-TT module 213 may consist of a UPF 330 and a NW-TT 331.
  • the NW-TT 331 may provide a 5GS DetNet node IP interface 340 (i.e., the interface #3 as shown in Fig. 2) .
  • the 5GS DetNet node IP interface 340 corresponds to a network-side IP interface of a DetNet node.
  • the 5GS DetNet node IP interface 340 is an externally visible interface of the 5GS DetNet Node.
  • the 5GS DetNet node IP interface 340 may be any type of interface that supports IP and DetNet compliant IP QoS, but in practice the 5GS DetNet node IP interface 340 is most often an Ethernet interface.
  • the UPF/NW-TT module 213 may only consist of the UPF 330 and does not comprise the NW-TT 331.
  • the UPF 330 may provide the 5GS DetNet node IP interface 340 on its own.
  • Embodiments of the present disclosure are intended to provide IP management for an externally visible interface (i.e., the 5GS DetNet node IP interface 321 or 340) of a 5GS IP router node (for example, a 5GS DetNet node) .
  • Externally visible means that for instance adjacent DetNet nodes would see the interface as a next hop interface for IP traffic such as DetNet traffic flows, or an interface that matters to a DetNet controller for understanding network topology or routing.
  • the IP management may be implemented with a TSCTSF as an owner and a SMF as a learner.
  • the IP management may be implemented with a TSCTSF as a learner and a SMF as an owner.
  • a TSCTSF as a learner and a SMF as an owner.
  • 5GC detects a new external IP interface or a list of external IP interfaces and configure IP address information and/or IP configuration information to the detected external IP interface (s) .
  • the TSCTSF is allowed to be aware of and up-to-date with the IP address information and/or IP configuration information, so that the TSCTSF can expose the IP address information and/or IP configuration information to the DetNet controller or any other IP software defined network (SDN) controller.
  • SDN IP software defined network
  • the IP address information may comprise an IP address and a prefix length.
  • the IP address information may comprise an IP address and subnet mask for IPv4.
  • the IP address information may comprise one or more IP prefixes and an interface identity (ID) for IPv6.
  • ID interface identity
  • the full IP address of an external IP interface may be concatenation of the prefix and the interface ID. It is to be understood that these are merely examples and the IP address information may adopt any other suitable forms.
  • the IP configuration information may refer to additional IP or lower layer information of the interface.
  • the IP configuration information may comprise IP routing protocol (s) or algorithm (s) applied to the interface and IP parameters configured to the IP routing protocol (s) or algorithm (s) .
  • the IP configuration information may comprise a maximum transmission unit (MTU) size of the interface.
  • the IP configuration information may comprise a configuration on how duplicate address detection should be performed or a neighbor/address resolution protocol (ARP) cache of the interface.
  • the IP configuration information may comprise lower layer information such as the L2 technology type (e.g., Ethernet) , bitrate and address (e.g., MAC address) .
  • the IP configuration information may comprise cost and/or priority of IP links. It is to be understood that these are merely examples and the IP configuration information may comprise any other suitable information.
  • the IP configuration information may be read-only or read-and-write for the TSCTSF depending on the implementation.
  • the lower layer information such as the L2 technology type (e.g., Ethernet) , bitrate and address (e.g., MAC address) may be read-only for the TSCTSF because they stem from the interface hardware and are not changeable by configuration.
  • IP routing protocol (s) or algorithm (s) applied to the interface and IP parameters configured to the IP routing protocol (s) or algorithm (s) may be “read and write” for the TSCTSF.
  • parameters such as cost and/or priority of IP links may be “read and write” for the TSCTSF. It is to be understood that these are merely examples and are not intended for limitation.
  • Fig. 4 illustrates a diagram illustrating a process 400 of communication according to some embodiments of the present disclosure.
  • the model 400 will be described with reference to Fig. 2. It is assumed 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 serves as a management owner, and the SMF 214 serves as a management learner.
  • UPF 330 is preconfigured with interface numbers of external IP interfaces of a 5GS DetNet node and a list of 5GS DetNet node IDs. It is to be understood that an order and the number of the steps in Fig. 4 are merely for illustration, and are not intended for limitation.
  • the device 310 transmits, to a first core network element (e.g., the SMF 214) , an indication regarding a device-side IP interface of a DetNet node.
  • a first core network element e.g., the SMF 214
  • the indication may be implemented in any suitable ways.
  • the device 310 may transmit the indication in a PDU session establishment request.
  • the device 310 may transmit the indication in a NAS SM message via AMF (not shown) .
  • the device 310 may transmit the indication in a DHCP request after PDU session establishment.
  • the DHCP request may comprise an identifier specific to the device-side IP interface as the indication.
  • the identifier may be a DHCP client ID specific to the device-side IP interface.
  • the DHCP client ID may be allocated by the SMF 214 in NAS SM PDU session establishment signaling during the PDU session establishment.
  • the DHCP client ID may be predefined. In this case, the device 310 may indicate the DHCP client ID to the SMF 214 in NAS SM PDU session establishment signaling during the PDU session establishment.
  • the identifier may be an IA_PD identifier of an IA_PD option specific to the device-side IP interface. For example, when the device 310 requests IPv6 prefix for the DetNet interface from the SMF 214 with the IPv6 Prefix Delegation. The device 310 acts as a "Requesting Router" and inserts DetNet interface specific IA_PD option (s) into a DHCPv6 Solicit message sent to the SMF 214.
  • the IA_PD identifier may be allocated by the SMF 214 in NAS SM PDU session establishment signaling during the PDU session establishment.
  • the IA_PD identifier may be predefined. In this case, the device 310 may indicate the IA_PD identifier to the SMF 214 in NAS SM PDU session establishment signaling during the PDU session establishment.
  • the SMF 214 determines that a new device-side IP interface is detected.
  • the SMF 214 is able to identify that the PDU session is established for the purpose of joining a 5GS DetNet node.
  • the SMF 214 may associate the DHCP request to the specific device-side IP interface.
  • the SMF 214 requests a fourth core network element (e.g., the UPF 330) to allocate an interface number for the device-side IP interface.
  • the UPF 330 may also feedback a 5GS DetNet Node ID to the SMF 214.
  • the SMF 214 transmits the interface number, the 5GS DetNet Node ID and a PDU session ID to a second core network element (e.g., the TSCTSF 217) via a PCF (not shown) .
  • a second core network element e.g., the TSCTSF 217
  • the TSCTSF 217 determines IP address information for the device-side IP interface.
  • the TSCTSF 217 is preconfigured with a set of IP address information for a set of device-side IP interfaces. In this case, as shown by step 405-1, the TSCTSF 217 may determine, from the set of IP address information, the IP address information for the device-side IP interface.
  • the TSCTSF 217 may transmit, to the SMF 214, a request (for convenience, also referred to as a second request herein) for obtaining at least one of IP address information or IP configuration information for the device-side IP interface.
  • the SMF 214 may transmit, to a third core network element (e.g., the UDM 216) , a request (for convenience, also referred to as a first request herein) for obtaining the at least one of IP address information or IP configuration information for the device-side IP interface.
  • the SMF 214 may receive, from the UDM 216, the at least one of IP address information or IP configuration information for the device-side IP interface, and transmit the at least one of IP address information or IP configuration information for the device-side IP interface to the TSCTSF 217.
  • the first request may be transmitted by the SMF 214 on its own initiative. In some embodiments, the first request may be transmitted by the SMF 214 in response to receiving the second request.
  • each of the first request and the second request may comprise an ID of the device 310 as a key.
  • the information may be requested with UE ID if mapping between UE ID and the DetNet Node ID/interface number is known already when the information is stored in the UDM 216.
  • each of the first request and the second request may comprise a pair of the 5GS DetNet node ID and an interface number of the device-side IP interface as a key.
  • the SMF 214 may derive, from a generic public subscription identifier (GPSI) of the device 310, the pair of the identity of the 5GS DetNet node and the interface number of the device-side IP interface. GPSI is within the subscription data of the device 310.
  • the device 310 may have multiple GPSIs associated to the same UE ID (e.g., International Mobile Subscriber Identity (IMSI) ) .
  • IMSI International Mobile Subscriber Identity
  • the information may be requested with GPSI by a specific locally meaningful mapping from a GPSI associated to the UE ID to the pair of ⁇ DetNet Node ID and interface number ⁇ .
  • the TSCTSF 217 may transmit, to the UDM 216, a request for obtaining at least one of IP address information or IP configuration information for the device-side IP interface.
  • the request may comprise an ID of the device 310 as a key.
  • the request may comprise a pair of the 5GS DetNet node ID and an interface number of the device-side IP interface as a key.
  • the request may be implemented similar with the first request or the second request, and thus other details are omitted here for concise.
  • the TSCTSF 217 may receive the at least one of IP address information or IP configuration information for the device-side IP interface from the UDM 216.
  • the information stored in the UDM 216 or DN-AAA server may be considered as an extension of the current Framed Route information stored them according to earlier 3GPP releases.
  • This information would have to be augmented by two additional mandatory pieces of information for the prefixes that are meant for the device-side IP interface of the UE: an indicator that the prefix is targeted for the device-side IP interface of the UE; and an IP interface ID by which a full IP address can be formed from the prefix.
  • the information may also comprise other IP configuration parameters (such as the MTU size) designated for the device-side IP interface.
  • the TSCTSF uses the received augmented information to learn the IP address information, i.e., IP prefixes and addresses (IP interface IDs) that are designated for the device-side interface.
  • IP address information i.e., IP prefixes and addresses (IP interface IDs) that are designated for the device-side interface.
  • the SMF 214 may request the information from the UDM 216 or DN-AAA server (not shown) by using DHCP to ask for the IP configuration information of the device-side IP interface. For example, the SMF 214 may use the pair of ⁇ DetNet Node ID and interface number ⁇ in a DHCP query. The SMF 214 may pass the information received from the DHCP server to the TSCTSF 217.
  • the DS-TT 311 transmits, to the TSCTSF 217, IP management capability of the device-side IP interface.
  • the DS-TT 311 may transmit the IP management capability via a PMIC.
  • the device 310 may transmit the IP management capability of the device-side IP interface to the TSCTSF 217.
  • the NW-TT 331 may transmit, to the TSCTSF 217, IP management capability of the network-side IP interface.
  • the NW-TT 331 may transmit the IP management capability via a PMIC or UMIC.
  • the PMIC may carry information of one port or interface.
  • the UMIC may carry information of one or more ports or interfaces.
  • the UPF 330 may transmit the IP management capability of the network-side IP interface to the TSCTSF 217 via N4 session level message.
  • the DS-TT 311 or the NW-TT 331 may transmit types of supported IP routing protocols or algorithms to the TSCTSF 217 as the IP management capability.
  • the IP management capability may indicate that the DS-TT 311 may support routing protocols: open shortest path first (OSPF) protocol and intermediate system-to-intermediate system (IS-IS) protocol.
  • OSPF open shortest path first
  • IS-IS intermediate system-to-intermediate system
  • the TSCTSF 217 may update IP configuration information of the device-side IP interface based on the IP management capability of the device-side IP interface if needed.
  • the TSCTSF 217 may update IP configuration information of the network-side IP interface based on the IP management capability of the network-side IP interface if needed.
  • the TSCTSF 217 may configure, in the updated IP configuration information, the type of routing protocol or algorithm and parameters of the routing protocol or algorithm applied in the interface.
  • the parameters may comprise at least one of the following: Hello Interval (number of seconds that the interface sends out OSPF hello packets to the network) , cost of the interface, retransmit interval (configure the number of seconds that elapse before the interface resends a link state advertisement (LSA) to a neighbor that did not respond to the original LSA) , etc..
  • the TSCTSF 217 may bind the interface number to the IP address information corresponding to a PDU session. For example, the TSCTSF 217 may build up binding information of the interface number and the IP address information of the interface corresponding to the PDU session. If IP address of the device with the interface is known by the TSCTSF 217, the TSCTSF 217 may also include the IP address of the device in the binding information. In this way, it is ensured to transmit PMIC to the correct interface.
  • IPv6 interface ID determination may be done based on a MAC address of the DS-TT 311.
  • the MAC address may be transmitted to the TSCTSF 217 during the PDU session establishment procedure.
  • the TSCTSF 217 may provide the IPv6 prefix to the interface. If a full IP address is provided, the TSCTSF 217 may provide the IPv6 prefix based on the MAC address.
  • the TSCTSF 217 also maintains the up-to-date information of the IP address information and IP configuration information provided to each interface or interface number.
  • the TSCTSF 217 may transmit the IP address information to the DS-TT 311. In some embodiments, the TSCTSF 217 may also transmit the IP configuration information. In some embodiments, the TSCTSF 217 may transmit at least one of the IP address information or the IP configuration information via a PMIC. For example, if IP configuration information can be written, the TSCTSF 217 may transmit the IP address information and may also transmit any other “read-and-write” parameters of IP configuration information to the DS-TT 311 via a PMIC.
  • the TSCTSF 217 may transmit at least one of the IP address information or the IP configuration information via a NAS SM message.
  • the TSCTSF 217 may determine IP address information of the network-side IP interface and transmit it to the NW-TT 331. In some embodiments, the TSCTSF 217 may also transmit the IP configuration information of the network-side IP interface. In some embodiments, the TSCTSF 217 may transmit at least one of the IP address information or the IP configuration information of the network-side IP interface via a PMIC or UMIC. For example, if IP configuration information can be written, the TSCTSF 217 may transmit the IP address information and may also transmit any other “read-and-write” parameters of IP configuration information to the NW-TT 331 via a PMIC or UMIC. In some embodiments where there is no NW-TT, the TSCTSF 217 may transmit at least one of the IP address information or the IP configuration information via a SM policy association modification procedure.
  • the TSCTSF 217 may transmit the IP address information associated with the DS-TT to the SMF 214 and the SMF 214 may transmit the IP address information to the UPF 330.
  • the TSCTSF 217 may ensure that the UPF 330 starts to forward IP packets to that IP address information to the PDU session associated with the DS-TT 311.
  • the TSCTSF 217 informs the SMF 214 that an IPv4 address or IPv6 prefix should be associated with the PDU session.
  • the SMF 214 may configure the IP address information to the UPF 330 via PDR.
  • the TSCTSF 217 may generate information of the DetNet node.
  • the information may comprise the DetNet node ID, the interface number and the IP address information and/or IP configuration information of the IP interface (s) of the DetNet node.
  • the information of the DetNet node may comprise an interface number and IP address information of each external IP interface in a same DetNet node.
  • the TSCTSF 217 may expose the information of the DetNet node to a controller (e.g., the DetNet controller 220) .
  • the information of the DetNet node may be exchanged by any means such as YANG data models and NETCONF/RESTCONF protocols, the Path Computation Element Protocol, or master information block (MIB) data models and simple network management protocol (SNMP) .
  • MIB master information block
  • SNMP simple network management protocol
  • external IP interface management may be achieved for an IP router node.
  • Fig. 5 illustrates a diagram illustrating a process 500 of communication according to some embodiments of the present disclosure.
  • the model 500 will be described with reference to Figs. 2, 3A and 3B. It is assumed 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 serves as a management learner, and the SMF 214 serves as a management owner.
  • UPF 330 is preconfigured with interface numbers of external IP interfaces of a 5GS DetNet node and a list of 5GS DetNet node IDs. It is to be understood that an order and the number of the steps in Fig. 5 are merely for illustration, and are not intended for limitation.
  • the device 310 transmits, to a first core network element (e.g., the SMF 214) , an indication regarding a device-side IP interface of a DetNet node.
  • a first core network element e.g., the SMF 214
  • the indication may be implemented in any suitable ways.
  • the device 310 may transmit the indication in a PDU session establishment request.
  • the device 310 may transmit the indication in a NAS SM message via AMF (not shown) .
  • the PDU session establish request may further comprise a protocol configuration option (PCO) value indicating a configuration of the device-side IP interface.
  • the PCO value may comprise a MAC address or IP interface ID of the DS-TT 311.
  • the device 310 may transmit the indication in a DHCP request after PDU session establishment.
  • the DHCP request may comprise an identifier specific to the device-side IP interface as the indication.
  • step 501 The operation in the step 501 is similar with that in the step 401 in Fig. 4, and thus other details are omitted here for concise.
  • the SMF 214 determines that a new device-side IP interface is detected.
  • the SMF 214 is able to identify that the PDU session is established for the purpose of joining a 5GS DetNet node.
  • the SMF 214 may associate the DHCP request to the specific device-side IP interface.
  • the SMF 214 may request a fourth core network element (e.g., the UPF 330) to allocate an interface number for the device-side IP interface.
  • a fourth core network element e.g., the UPF 330
  • the UPF 330 may also feedback a 5GS DetNet Node ID to the SMF 214.
  • the SMF 214 may determine IP address information of the device-side IP interface. In some embodiments, the SMF 214 may select an IP address and prefix length for the device-side IP interface from an IP pool. In some embodiments, an index of the IP pool may be obtained from UPF, PCF or UDM. It is to be understood that any other suitable ways are also feasible.
  • the SMF 214 may bind the interface number to the IP address information and the PDU session ID. For example, the SMF 214 may build up binding information of the interface number, the IP address information, and the PDU session ID. If IP address of the device associated with the interface is known by the SMF, the SMF also include the IP address of the device in the binding information.
  • the SMF 214 may receive IP management capability of the device-side IP interface from the device 310, for example, via a NAS SM message.
  • the SMF 214 may receive IP management capability of the network-side IP interface from the UPF 330.
  • the SMF 214 may update IP configuration information of the device-side IP interface based on the IP management capability of the device-side IP interface if needed.
  • the SMF 214 may update IP configuration information of the network-side IP interface based on the IP management capability of the network-side IP interface if needed.
  • the SMF 214 may transmit the IP address information to the device 310. In some embodiments, the SMF 214 may also transmit the IP configuration information. In some embodiments, the SMF 214 may transmit at least one of the IP address information or the IP configuration information via a NAS SM message.
  • the SMF 214 may respond with that PCO value including IP prefix and/or IP configuration information for the device-side IP interface.
  • the SMF 214 may take them into account when determining an IPv6 address for the device-side IP interface.
  • the SMF 214 may transmit at least one of the IP address information or the IP configuration information via a DHCP message. For example, the SMF 214 may allocate IPv4 address and/or IPv6 prefix for the device-side IP interface, construct a DHCP server message and send the allocated address/prefix to the device 310. The device 310 may pass the IP address/prefix to the device-side IP interface.
  • the SMF 214 may determine IP address information of the network-side IP interface and transmit it to the UPF 330. In some embodiments, the SMF 214 may also transmit, to the UPF 330, the IP configuration information of the network-side IP interface. In some embodiments, the SMF 214 may transmit at least one of the IP address information or the IP configuration information of the network-side IP interface.
  • the SMF 214 may transmit the IP address information of the external IP interfaces to the TSCTSF 217. In some embodiments, the SMF 214 may also transmit the IP configuration information of the external IP interfaces to the TSCTSF 217.
  • the TSCTSF 217 may receive, from the DS-TT 311, IP management capability and IP configuration information of the device-side IP interface, for example, via a PMIC.
  • the TSCTSF 217 may receive, from the NW-TT 331, IP management capability and IP configuration information of the network-side IP interface, for example, via a PMIC or UMIC.
  • the PMIC may carry information of one port or interface.
  • the UMIC may carry information of one or more ports or interfaces.
  • the TSCTSF 217 may learn the interface number and the IP address information corresponding to the PDU session for the device-side IP interface, and bind the interface number to the IP address information corresponding to the PDU session. In some embodiments, the TSCTSF 217 may also learn an interface number and IP address information for each external IP interface, and bind the interface number to the IP address information for each external IP interface. If IP address of the device associated with the external IP interface is known by the TSCTSF 217, the TSCTSF 217 may also include the IP address of the device in the binding information.
  • the TSCTSF 217 may generate information of the DetNet node.
  • the information may comprise the DetNet node ID, the interface number and the IP address information and/or the IP configuration information of IP interface (s) of the DetNet node.
  • the information of the DetNet node may comprise an interface number and IP address information of each external IP interface in a same DetNet node.
  • the TSCTSF 217 may expose the information of the DetNet node to a controller (e.g., the DetNet controller 220) .
  • the information of the DetNet node may be exchanged by any means such as YANG data models and NETCONF/RESTCONF protocols, the Path Computation Element Protocol, or MIB data models and SNMP.
  • YANG data models and NETCONF/RESTCONF protocols e.g., the DetNet controller 220
  • the information of the DetNet node may be exchanged by any means such as YANG data models and NETCONF/RESTCONF protocols, the Path Computation Element Protocol, or MIB data models and SNMP.
  • the present disclosure does not limit this aspect.
  • external IP interface management may also be achieved for an IP router node.
  • Figs. 4 and 5 are merely examples and are not intended for limitation.
  • the operations in the processes 400 and 500 may be implemented in any suitable combination.
  • Fig. 6 illustrates a flowchart of an example method 600 implemented at a device according to some embodiments of the present disclosure. For the purpose of discussion, the method 600 will be described with reference to Fig. 2.
  • a device for example, the UE/DS-TT module 211 transmits, to a first core network element (for example, the SMF 214) , an indication regarding a device-side IP interface of an IP router node.
  • a first core network element for example, the SMF 214.
  • the UE/DS-TT module 211 may transmit the indication in a PDU establishment request.
  • the PDU establishment request may further comprise a PCO value indicating a configuration of the device-side IP interface.
  • the UE/DS-TT module 211 may transmit the indication in a DHCP request.
  • the DHCP request may comprise an identifier specific to the device-side Internet Protocol interface as the indication.
  • the UE/DS-TT module 211 receives, from the SMF 214 or a second core network element (for example, the TSCTSF 217) , IP address information for the device-side IP interface.
  • the UE/DS-TT module 211 may receive the IP address information via a PMIC or a NAS SM message.
  • the UE/DS-TT module 211 may transmit, to the SMF 214 or the TSCTSF 217, IP management capability of the device-side IP interface. In some embodiments, the UE/DS-TT module 211 may transmit the IP management capability via a PMIC or a NAS SM message. Then the UE/DS-TT module 211 may receive, from the SMF 214 or the TSCTSF 217, IP configuration information updated based on the IP management capability.
  • an external IP interface at a UE/DS-TT module can be managed.
  • Fig. 7 illustrates a flowchart of an example method 700 implemented at a core network element according to some embodiments of the present disclosure. For the purpose of discussion, the method 700 will be described with reference to Fig. 2.
  • a first core network element receives, from a device (for example, the UE/DS-TT module 211) , an indication regarding a device-side IP interface of an IP router node.
  • the SMF 214 may receive the indication in a PDU establishment request.
  • the PDU establishment request may further comprise a PCO value indicating a configuration of the device-side IP interface.
  • the SMF 214 may transmit the indication in a DHCP request.
  • the DHCP request may comprise an identifier specific to the device-side Internet Protocol interface as the indication.
  • the SMF 214 transmits, to the UE/DS-TT module 211, IP address information of the device-side IP interface.
  • the UE/DS-TT module 211 may transmit the IP address information via a NAS SM message.
  • the SMF 214 may receive, from the UE/DS-TT module 211, IP management capability of the device-side IP interface. In some embodiments, the SMF 214 may receive the IP management capability via a PMIC or a NAS SM message. Then the SMF 214 may transmit, to the UE/DS-TT module 211, IP configuration information updated based on the IP management capability.
  • the SMF 214 may transmit the IP address information to a second core network element (for example, the TSCTSF 217) .
  • the SMF 214 may also transmit IP configuration information for the device-side IP interface to the TSCTSF 217.
  • the SMF 214 may determine an interface number for the device-side IP interface and an identity of a PDU session associated with the device-side IP interface, and bind the interface number to the IP address information and the identity of the PDU session. In some embodiments, if 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 identity of the PDU session.
  • a core network element may be enabled as an owner for management of an external IP interface of an IP router node.
  • Fig. 8 illustrates a flowchart of an example method 800 implemented at a core network element according to some embodiments of the present disclosure. For the purpose of discussion, the method 800 will be described with reference to Fig. 2.
  • a first core network element receives, from a device (for example, the UE/DS-TT module 211) , an indication regarding a device-side IP interface of an IP router node.
  • the SMF 214 may receive the indication in a PDU establishment request.
  • the PDU establishment request may further comprise a PCO value indicating a configuration of the device-side IP interface.
  • the SMF 214 may transmit the indication in a DHCP request.
  • the DHCP request may comprise an identifier specific to the device-side Internet Protocol interface as the indication.
  • the SMF 214 transmits, to a second core network element (for example, the TSCTSF 217) , an interface number for the device-side IP interface and an identity of the IP router node for allocation of IP address information of the device-side IP interface.
  • a second core network element for example, the TSCTSF 217
  • the SMF 214 may transmit, to a third core network element (for example, the UDM 216) , a first request for obtaining at least one of IP address information or IP configuration information for the device-side IP interface.
  • the SMF 214 may receive, from the UDM 216, the at least one of the IP address information or IP configuration information, and transmit it to the TSCTSF 217.
  • the SMF 214 may transmit the first request in response to receiving, from the TSCTSF 217, a second request for obtaining the at least one of IP address information or IP configuration information for the device-side IP interface.
  • the first request and the second request comprise at least one of an identity of the device or a pair of an identity of the IP router node and an interface number of the device-side IP interface.
  • the SMF 214 may derive, from a GPSI of the device, the pair of the identity of the IP router node and the interface number of the device-side IP interface.
  • the SMF 214 may receive, from the UE/DS-TT module 211, IP management capability of the device-side IP interface, and transmit the IP management capability of the device-side IP interface to the TSCTSF 217. Then the SMF 214 may receive, from the TSCTSF 217, IP configuration information updated based on the IP management capability.
  • a core network element may be enabled as a learner for management of an external IP interface of an IP router node.
  • Fig. 9 illustrates a flowchart of an example method 900 implemented at a core network element according to some embodiments of the present disclosure. For the purpose of discussion, the method 900 will be described with reference to Fig. 2.
  • a second core network element receives, from a first core network element (for example, the SMF 214) , an interface number for a device-side IP interface of an IP router node and an identity of the IP router node, the interface number corresponding to a protocol data unit session.
  • the TSCTSF 217 transmits, to a device (for example, the UE/DS-TT 210) , IP address information for the device-side IP interface.
  • the TSCTSF 217 may determine, from a preconfigured set of Internet Protocol address information for a set of device-side Internet Protocol interfaces, the Internet Protocol address information for the device-side Internet Protocol interface.
  • the TSCTSF 217 may transmit, to the SMF 214 or to a third core network element (e.g., UDM 216) , a request for obtaining at least one of Internet Protocol address information or Internet Protocol configuration information for the device-side Internet Protocol interface.
  • the TSCTSF 217 may receive the Internet Protocol address information from the SMF 214 or UDM 216.
  • the request comprises at least one of an identity of the device or a pair of the identity of the Internet Protocol router node and the interface number of the device-side Internet Protocol interface.
  • the TSCTSF 217 may receive, from a device (for example, UE/DS-TT module 211 or UPF/NW-TT module 213) , Internet Protocol management capability of an external Internet Protocol interface via a port management information container, a user plane node management information container or a non-access-stratum message.
  • the TSCTSF 217 may transmit, to the device, Internet Protocol configuration information updated based on the Internet Protocol management capability via a port management information container, a user plane node management information container or a non-access-stratum message.
  • the TSCTSF 217 may bind the interface number to the IP address information corresponding to the PDU session. In some embodiments, if IP address information of the device 310 is available, the 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 the device 310.
  • the TSCTSF 217 may receive, from the UPF/NW-TT 213, an interface number of a network-side IP interface of the IP router node and at least one of IP address information or IP configuration information of the network-side IP interface.
  • the TSCTSF 217 may bind the interface number of the network-side IP interface to the at least one of the IP address information or IP configuration information of the network-side IP interface.
  • the TSCTSF 217 may generate information of the IP router node.
  • the information comprises: the identity of the IP router node; the interface number and at least one of the IP address information or IP configuration information for the device-side IP interface; and the interface number and at least one of the IP address information or IP configuration information for the network-side IP interface. Then the TSCTSF 217 may expose the information of the IP router node to a controller.
  • a core network element may also be enabled as an owner for management of an external IP interface of an IP router node.
  • Fig. 10 illustrates a flowchart of an example method 1000 implemented at a core network element according to some embodiments of the present disclosure. For the purpose of discussion, the method 1000 will be described with reference to Fig. 2.
  • a second core network element receives, from a first core network element (for example, the SMF 214) , Internet Protocol address information for a device-side IP interface of an IP router node, and an interface number of the device-side IP interface corresponding to a PDU session.
  • the 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 the device 310.
  • the TSCTSF 217 may receive, from the UPF/NW-TT 213, an interface number of a network-side IP interface of the IP router node and at least one of IP address information or IP configuration information of the network-side IP interface.
  • the TSCTSF 217 may bind the interface number of the network-side IP interface to the at least one of the IP address information or IP configuration information of the network-side IP interface.
  • the TSCTSF 217 generates information of the Internet Protocol router node.
  • the information comprises: the identity of the IP router node; the interface number and at least one of the IP address information or IP configuration information for the device-side IP interface; and the interface number and at least one of the IP address information or IP configuration information for the network-side IP interface.
  • the TSCTSF 217 exposes the information of the IP router node to a controller.
  • the TSCTSF 217 may receive, from a device (for example, UE/DS-TT module 211 or UPF/NW-TT module 213) , at least one of Internet Protocol address information or Internet Protocol configuration information for an external IP interface via a port management information container, a user plane node management information container or a non-access-stratum message.
  • a device for example, UE/DS-TT module 211 or UPF/NW-TT module 2113
  • a device for example, UE/DS-TT module 211 or UPF/NW-TT module 213
  • at least one of Internet Protocol address information or Internet Protocol configuration information for an external IP interface via a port management information container, a user plane node management information container or a non-access-stratum message.
  • a core network element may also be enabled as a learner for management of an external IP interface of an IP router node.
  • Fig. 11 illustrates a flowchart of an example method 1100 implemented at a core network element according to some embodiments of the present disclosure. For the purpose of discussion, the method 1100 will be described with reference to Fig. 2.
  • a third core network element receive, from a first core network element (for example, the SMF 214) or from a second core network element (for example, TSCTSF 217) , 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.
  • the UDM 216 transmits, to the SMF 214 or to the TSCTSF 217, the at least one of the Internet Protocol address information or Internet Protocol configuration information.
  • the request comprises at least one of an identity of a device or a pair of an identity of the Internet Protocol router node and an interface number of the device-side Internet Protocol interface.
  • the UDM 216 stores subscription information of a device in association with at least one of a pair of an identity 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.
  • a core network element may support management of an external IP interface of an IP router node.
  • an apparatus capable of performing one of the methods 600 to 1100 may comprise means for performing the respective steps of the one of the methods 600 to 1100.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • Fig. 12 is a simplified block diagram of a device 1200 that is suitable for implementing embodiments of the present disclosure.
  • the device 1200 may be provided to implement the communication device, for example the devices 310, the DS-TT 311, the NW-TT 331, or the core network elements as shown in Fig. 2.
  • the device 1200 includes one or more processors 1210, one or more memories 1220 coupled to the processor 1210, and one or more communication modules 1240 coupled to the processor 1210.
  • the communication module 1240 is for bidirectional communications.
  • the communication module 1240 has at least one antenna to facilitate communication.
  • the communication interface may represent any interface that is necessary for communication with other network elements.
  • the processor 1210 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • the device 1200 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • the memory 1220 may include one or more non-volatile memories and one or more volatile memories.
  • the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 1224, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , and other magnetic storage and/or optical storage.
  • the volatile memories include, but are not limited to, a random access memory (RAM) 1222 and other volatile memories that will not last in the power-down duration.
  • a computer program 1230 includes computer executable instructions that are executed by the associated processor 1210.
  • the program 1230 may be stored in the ROM 1220.
  • the processor 1210 may perform any suitable actions and processing by loading the program 1230 into the RAM 1220.
  • the embodiments of the present disclosure may be implemented by means of the program 1230 so that the device 1200 may perform any process of the disclosure as discussed with reference to Figs. 4 to 11.
  • the embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
  • the program 1230 may be tangibly contained in a computer readable medium which may be included in the device 1200 (such as in the memory 1220) or other storage devices that are 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 types of tangible non-volatile storage, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like.
  • Fig. 13 shows an example of the computer readable medium 1300 in form of CD or DVD.
  • the computer readable medium has the program 1230 stored thereon.
  • various embodiments of the present disclosure may be implemented in hardware or special purpose 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 executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • 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, being executed in a device on a target real or virtual processor, to carry out the method 600 to 1100 as described above with reference to Figs. 6-11.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various embodiments.
  • Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
  • Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented.
  • the program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
  • the computer program codes or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above.
  • Examples of the carrier include a signal, computer readable medium, and the like.
  • the computer readable medium may be a computer readable signal medium or a computer readable storage medium.
  • a computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, 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 disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • Embodiments of the present disclosure may provide the following solutions:
  • a device comprising:
  • At least one memory including computer program code
  • the at least one memory and the computer program code configured to, with the at least one processor, cause the device to:
  • Clause 2 The device of Clause 1, wherein the device is caused to transmit the indication by:
  • Clause 3 The device of Clause 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.
  • Clause 4 The device of Clause 2, wherein the dynamic host configuration protocol request comprises an identifier specific to the device-side Internet Protocol interface as the indication.
  • Clause 6 The device of Clause 5, wherein the device is caused to transmit the Internet Protocol management capability by:
  • Clause 7 The device of Clause 1, wherein the device is caused to receive the Internet Protocol address information by:
  • Clause 8 The device of Clause 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.
  • a first core network element comprising:
  • At least one memory including computer program code
  • the at least one memory and the computer program code configured to, with the at least one processor, cause the first core network element to:
  • Clause 10 The first core network element of Clause 9, wherein the first core network element is caused to receive the indication by:
  • Clause 11 The first core network element of Clause 9, wherein the first core network element is further caused to:
  • Clause 12 The first core network element of Clause 9, wherein the first core network element is further caused to:
  • Clause 13 The first core network element of Clause 12, wherein the first core network element is further caused to:
  • Clause 14 The first core network element of Clause 9, wherein the first core network element is further caused to:
  • a first core network element comprising:
  • At least one memory including computer program code
  • the at least one memory and the computer program code configured to, with the at least one processor, cause the first core network element to:
  • Clause 16 The first core network element of Clause 15, wherein the first core network element is further caused to:
  • Clause 17 The first core network element of Clause 16, wherein the first core network element is caused to transmit the first request by:
  • Clause 18 The first core network element of Clause 17, wherein the first request and the second request comprise at least one of an identity of the device or a pair of an identity of the Internet Protocol router node and an interface number of the device-side Internet Protocol interface.
  • Clause 19 The first core network element of Clause 18, wherein the first core network element is further caused to:
  • Clause 20 The first core network element of Clause 15, wherein the first core network element is further caused to:
  • a second core network element comprising:
  • At least one memory including computer program code
  • the at least one memory and the computer program code configured to, with the at least one processor, cause the second core network element to:
  • Clause 22 The second core network element of Clause 21, wherein the second core network element is further caused to:
  • the Internet Protocol address information for the device-side Internet Protocol interface determines, from a preconfigured set of Internet Protocol address information for a set of device-side Internet Protocol interfaces, the Internet Protocol address information for the device-side Internet Protocol interface.
  • Clause 23 The second core network element of Clause 22, wherein the second core network element is further caused to:
  • Clause 24 The second core network element of Clause 23, wherein the request comprises at least one of an identity of the device or a pair of the identity of the Internet Protocol router node and the interface number of the device-side Internet Protocol interface.
  • Clause 25 The second core network element of Clause 21, wherein the second core network element is further caused to:
  • Clause 26 The second core network element of Clause 21, wherein the second core network element is further caused to:
  • Clause 27 The second core network element of Clause 21, wherein the second core network element is further caused to:
  • a second core network element comprising:
  • At least one memory including computer program code
  • the at least one memory and the computer program code configured to, with the at least one processor, cause the second core network element to:
  • Clause 29 The second core network element of Clause 28, wherein the second core network element is further caused to:
  • a third core network element comprising:
  • At least one memory including computer program code
  • the at least one memory and the computer program code configured to, with the at least one processor, cause the third core network element to:
  • Clause 31 The third core network element of Clause 30, wherein the request comprises at least one of an identity of a device or a pair of an identity of the Internet Protocol router node and an interface number of the device-side Internet Protocol interface.
  • Clause 32 The third core network element of Clause 30, wherein the third core network element is further caused to:
  • a method of communication comprising:
  • a method of communication comprising:
  • a method of communication comprising:
  • a method of communication comprising:
  • a method of communication comprising:
  • the information comprising the identity of the Internet Protocol router node, the interface number and the Internet Protocol address information
  • a method of communication comprising:
  • An apparatus of communication comprising:
  • An apparatus of communication comprising:
  • An apparatus of communication comprising:
  • An apparatus of communication comprising:
  • An apparatus of communication comprising:
  • An apparatus of communication comprising:
  • Clause 45 A non-transitory computer readable medium comprising program instructions for causing an apparatus to perform the method according to any of Clauses 33 to 38.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Des modes de réalisation de la présente divulgation concernent la gestion d'interface IP externe dans un nœud de routeur IP. Selon un aspect de la présente divulgation, un dispositif transmet, à un premier élément de réseau central, une indication concernant une interface IP côté dispositif d'un nœud de routeur IP. Le dispositif reçoit ensuite, en provenance du premier élément de réseau central ou d'un second élément de réseau central, des informations d'adresse IP pour l'interface IP côté dispositif. De cette manière, une interface IP externe côté dispositif est obtenue.
PCT/CN2022/091030 2022-05-05 2022-05-05 Gestion d'interface ip externe dans un nœud de routeur ip 5gs Ceased WO2023212872A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202280095551.3A CN119138101A (zh) 2022-05-05 2022-05-05 5gs ip路由器节点中的外部ip接口管理
PCT/CN2022/091030 WO2023212872A1 (fr) 2022-05-05 2022-05-05 Gestion d'interface ip externe dans un nœud de routeur ip 5gs

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/091030 WO2023212872A1 (fr) 2022-05-05 2022-05-05 Gestion d'interface ip externe dans un nœud de routeur ip 5gs

Publications (1)

Publication Number Publication Date
WO2023212872A1 true WO2023212872A1 (fr) 2023-11-09

Family

ID=88646096

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/091030 Ceased WO2023212872A1 (fr) 2022-05-05 2022-05-05 Gestion d'interface ip externe dans un nœud de routeur ip 5gs

Country Status (2)

Country Link
CN (1) CN119138101A (fr)
WO (1) WO2023212872A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4608052A1 (fr) * 2024-02-20 2025-08-27 Siemens Aktiengesellschaft Procédé de fonctionnement d'un réseau déterministe au moyen d'un dispositif de calcul électronique, produit programme informatique, support de stockage lisible par ordinateur et dispositif de calcul électronique

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105612508A (zh) * 2013-10-11 2016-05-25 华为技术有限公司 用于在分布式演进型分组核心网络架构中进行信号中介的系统和方法
US20200351973A1 (en) * 2019-05-03 2020-11-05 Nokia Technologies Oy Method and apparatus for port management of ethernet bridges
US20220030530A1 (en) * 2018-11-27 2022-01-27 Telefonaktiebolaget Lm Ericsson (Publ) Devices and Methods for Handling Precise Timing Protocol Frames
WO2022020020A1 (fr) * 2020-07-23 2022-01-27 Intel Corporation Configuration de pont de mise en réseau à contrainte temporelle 5g

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105612508A (zh) * 2013-10-11 2016-05-25 华为技术有限公司 用于在分布式演进型分组核心网络架构中进行信号中介的系统和方法
US20220030530A1 (en) * 2018-11-27 2022-01-27 Telefonaktiebolaget Lm Ericsson (Publ) Devices and Methods for Handling Precise Timing Protocol Frames
US20200351973A1 (en) * 2019-05-03 2020-11-05 Nokia Technologies Oy Method and apparatus for port management of ethernet bridges
WO2022020020A1 (fr) * 2020-07-23 2022-01-27 Intel Corporation Configuration de pont de mise en réseau à contrainte temporelle 5g

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ZTE: "RFCs related to DHCPv6 are obsoleted by RFC 8415", 3GPP DRAFT; C1-205904, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG1, no. Electronic meeting; 20201015 - 20201023, 7 October 2020 (2020-10-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051950670 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4608052A1 (fr) * 2024-02-20 2025-08-27 Siemens Aktiengesellschaft Procédé de fonctionnement d'un réseau déterministe au moyen d'un dispositif de calcul électronique, produit programme informatique, support de stockage lisible par ordinateur et dispositif de calcul électronique
WO2025176695A1 (fr) 2024-02-20 2025-08-28 Siemens Aktiengesellschaft Procédé de fonctionnement d'un réseau déterministe au moyen d'un dispositif informatique électronique, produit-programme d'ordinateur, support de stockage lisible par ordinateur et dispositif informatique électronique

Also Published As

Publication number Publication date
CN119138101A (zh) 2024-12-13

Similar Documents

Publication Publication Date Title
KR102664128B1 (ko) 향상된 nef 기능, mec 및 5g 통합
TWI817612B (zh) 通信方法和裝置
EP3585095B1 (fr) Méthode et dispositif de contrôle de qos, smf, upf, ue, pcf, et an
EP3923625A1 (fr) Procédé, système et appareil d'acquisition de paramètre de latence de paquet de données
CN113630749B (zh) 一种获取边缘服务的方法和装置
KR102469973B1 (ko) 통신 방법 및 장치
CN115552992B (zh) 用于在上线期间调配专用网络设备的方法和装置
US20230156833A1 (en) Packet Forwarding Method, Apparatus, and System
KR20240060722A (ko) 논리적 tsn 브리지를 위한 방법 및 장치
JP2024513904A (ja) Ｄｌ ｕｌ ｔｃｉ状態を処理するための方法
CN116868603A (zh) 针对af会话的外部参数提供的新方法
WO2023016395A1 (fr) Procédé et appareil de communication pour une communication sécurisée
US20240259343A1 (en) Apparatus, method, and computer program
WO2022247432A1 (fr) Procédé de synchronisation temporelle, dispositif électronique et support de stockage
WO2023137579A1 (fr) Procédé et appareil de fourniture de service d'urgence, dispositif, et support de stockage
WO2023212872A1 (fr) Gestion d'interface ip externe dans un nœud de routeur ip 5gs
CN116319958A (zh) 通信方法和装置
US20230071815A1 (en) Path section between uu and pc5
WO2020263139A1 (fr) Premier noeud mandataire de communication de service, second noeud mandataire de communication et procédés dans un réseau de communication sans fil
WO2023213210A1 (fr) Procédé de communication et appareil de communication
WO2023212882A1 (fr) Opération de routage et de transfert ip et gestion de noeud de routeur ip
WO2025171607A1 (fr) Mesure de qualité de service
WO2022021239A1 (fr) Notification de réseau concernant le résultat d'authentification et d'autorisation d'un dispositif terminal
WO2024221305A1 (fr) Traitement de sessions pdu ancré à une upf
TWI891740B (zh) 以分佈式sfc控制執行區域生命週期管理之方法及裝置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22940568

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202280095551.3

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 202447090699

Country of ref document: IN

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22940568

Country of ref document: EP

Kind code of ref document: A1