Source routing in a wireless communication system

Abstract

Various aspects of the present disclosure relate to a first network entity for wireless communication. The first network entity may be configured to, capable of, or operable to: receive, from a second network entity, a PDU session create request including downlink segment routing information; and send, to the second network entity, a PDU session create response including uplink segment routing information.

Description

SOURCE ROUTING IN A WIRELESS COMMUNICATION SYSTEMTECHNICAL FIELD

[0001] The present disclosure relates generally to wireless communication, including source routing in a wireless communication system.BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, which may be otherwise knowns as network equipment (NE) supporting wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).SUMMARY

[0003] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, asDocket No. SMM920250140-GR-NPused herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0004] A first network entity for wireless communication is described. The first network entity may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the first network entity may include at least one memory, and at least one processor coupled with the at least one memory and configured to cause the first network entity to: receive, from a second network entity, a protocol data unit (PDU) session create request including downlink segment routing information; and send, to the second network entity, a PDU session create response including uplink segment routing information.

[0005] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with at least one memory and configured to cause the processor to: receive, from a second network entity, a PDU session create request including downlink segment routing information; send, to the second network entity, a PDU session create response including uplink segment routing information.

[0006] A method performed or performable by the first network entity is described herein. The method may comprise: receiving, from a second network entity, a PDU session create request including downlink segment routing information; and sending, to the second network entity, a PDU session create response including uplink segment routing information.

[0007] A second network entity for wireless communication is described. The second network entity may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the second network entity may include at least one memory, and at least one processor coupled with the at least one memory and configured to cause the second network entity to: send, to a first network entity, a PDU session create request including downlink segment routing information; receive, from theDocket No. SMM920250140-GR-NPfirst network entity, a PDU session create response including uplink segment routing information.

[0008] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with at least one memory and configured to cause the processor to: send, to a first network entity, a PDU session create request including downlink segment routing information; and receive, from the first network entity, a PDU session create response including uplink segment routing information.

[0009] A method performed or performable by the second network entity is described herein. The method may comprise: sending, to a first network entity, a PDU session create request including downlink segment routing information; and receiving, from the first network entity, a PDU session create response including uplink segment routing information.

[0010] A first network entity for wireless communication is described. The first network entity may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the first network entity may include at least one memory, and at least one processor coupled with the at least one memory and configured to cause the first network entity to: receive a request for downlink segment routing information from a second network entity; and send downlink segment routing information to the second network entity.

[0011] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with at least one memory and configured to cause the processor to: receive a request for downlink segment routing information from a second network entity; and send downlink segment routing information to the second network entity

[0012] A method performed or performable by the first network entity is described herein. The method may comprise: receiving a request for downlink segment routingDocket No. SMM920250140-GR-NPinformation from a second network entity; and sending downlink segment routing information to the second network entity.

[0013] A second network entity for wireless communication is described. The second network entity may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the second network entity may include at least one memory, and at least one processor coupled with the at least one memory and configured to cause the second network entity to: send a request for downlink segment routing information to a first network entity; and receive downlink segment routing information from the first network entity.

[0014] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with at least one memory and configured to cause the processor to: send a request for downlink segment routing information to a first network entity; and receive downlink segment routing information from the first network entity

[0015] A method performed or performable by the second network entity is described herein. The method may comprise: sending a request for downlink segment routing information to a first network entity; and receiving downlink segment routing information from the first network entity.

[0016] A first network entity for wireless communication is described. The first network entity may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the first network entity may include at least one memory, and at least one processor coupled with the at least one memory and configured to cause the first network entity to: receive a session modification request including uplink segment routing information from a second network entity; send a response message to the second network entity.

[0017] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with atDocket No. SMM920250140-GR-NPleast one memory and configured to cause the processor to: receive a session modification request including uplink segment routing information from a second network entity; and send a response message to the second network entity.

[0018] A method performed or performable by the first network entity is described herein. The method may comprise: receiving a session modification request including uplink segment routing information from a second network entity; and sending a response message to the second network entity.

[0019] A second network entity for wireless communication is described. The second network entity may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the second network entity may include at least one memory, and at least one processor coupled with the at least one memory and configured to cause the second network entity to: send a session modification request including uplink segment routing information to a first network entity; and receive a response message from the first network entity.

[0020] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with at least one memory and configured to cause the processor to: send a session modification request including uplink segment routing information to a first network entity; and receive a response message from the first network entity.

[0021] A method performed or performable by a second network entity is described herein. The method may comprise: sending a session modification request including uplink segment routing information to a first network entity; and receiving a response message from the first network entity.BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0023] Figure 2 illustrates the Home-routed Roaming architecture 200 for 5GSDocket No. SMM920250140-GR-NP

[0024] Figure 3 illustrates an example deployment 300 of a HR roaming scenarios

[0025] Figures 4a and 4b illustrate an example of a process flow for UE-requested PDU Session Establishment for home-routed roaming scenarios in accordance with aspects of the present disclosure.

[0026] Figures 5a and 5b illustrate an example of a process flow for UE or network requested PDU Session Modification for a home-routed roaming scenario in accordance with aspects of the present disclosure.

[0027] Figure 6 gives an example of how the SRv6 locator prefix information element may be encoded.

[0028] Figure 7 gives an example of how the SID format encoding template information element may be encoded

[0029] Figure 8 gives an example of how the SRv6 SID list information element may be encoded.

[0030] Figure 9 illustrates an example of a UE 900 in accordance with aspects of the present disclosure.

[0031] Figure 10 illustrates an example of a processor 1000 in accordance with aspects of the present disclosure.

[0032] Figure 11 illustrates an example of an NE 1100 in accordance with aspects of the present disclosure.

[0033] Figure 12 illustrates a flowchart of a method 1200 performed by a NE in accordance with aspects of the present disclosure.

[0034] Figure 13 illustrates a flowchart of a method 1300 performed by a NE in accordance with aspects of the present disclosure.

[0035] Figure 14 illustrates a flowchart of a method 1400 performed by a NE in accordance with aspects of the present disclosure.

[0036] Figure 15 illustrates a flowchart of a method 1500 performed by a NE in accordance with aspects of the present disclosure.Docket No. SMM920250140-GR-NP

[0037] Figure 16 illustrates a flowchart of a method 1600 performed by a NE in accordance with aspects of the present disclosure.

[0038] Figure 17 illustrates a flowchart of a method 1700 performed by a NE in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0039] A wireless communication system, including one or more UE and NE may use a Segment Routing Header (SRH) to implement source routing, which may comprise deterministic path control and may have use cases such as traffic engineering, service chaining, and network slicing. In a 5G wireless communication network, source routing can be used for transport.

[0040] There is described herein an arrangement whereby capabilities such as deterministic path control and network programming are integrated into the 5GS signalling and / or service orchestration. Service chaining across network domains is allowed by enabling source routing to support domain-specific segment identifiers (SIDs) with embedded Session identifier and QoS parameters. This may allow networks to dynamically exchange and interpret SID lists and encoding formats, enabling flexible, per-flow and / or per- PDU Set Importance (PSI) traffic handling and QoS enforcement in multi-domain environments.

[0041] Aspects of the present disclosure are described in the context of a wireless communications system.

[0042] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combinationDocket No. SMM920250140-GR-NPof a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0043] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signalling, transmit signalling) over a Uu interface.

[0044] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0045] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as anDocket No. SMM920250140-GR-NPInternet-of-Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.

[0046] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0047] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0048] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.Docket No. SMM920250140-GR-NP

[0049] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a PDU session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0050] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0051] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., / t=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., / t=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., / / =1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., g=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., / t=3) may be associated with a fourth subcarrier spacingDocket No. SMM920250140-GR-NP(e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., / t=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0052] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a l ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0053] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., / t=0, / t=l, =2, jtz=3, =4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., / t=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0054] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designationsDocket No. SMM920250140-GR-NPFR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0055] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., / t=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., / / =1), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., g=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., =2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., / t=3), which includes 120 kHz subcarrier spacing.

[0056] Segment Routing over IPv6 (SRv6) is a modem network architecture based on the principles of source routing. In source routing, the sender of a data packet specifies the path it should take through the network. This differs from traditional hop-by-hop routing where each intermediate router independently determines the next hop using a local routing table. SRv6 implements source routing in IETF RFC 8754 “IPv6 Segment Routing Header (SRH)” by introducing the SRH, which enables deterministic path control. This tends to facilitate use cases such as traffic engineering, service chaining, and network slicing. In addition, SRv6 supports network programming by allowing instructions to be encoded directly into packet headers, as specified in IETF RFC 8986 “Segment Routing over IPv6 (SRv6) Network Programming”. These instructions, known as segments, can represent not only forwarding paths but also service functions such as firewalls or NAT functions. This design enables flexible and programmable network behaviour, making SRv6 a potentially powerful solution for modern IP networks, particularly in the context of the 5G cloudnative infrastructure.Docket No. SMM920250140-GR-NP

[0057] Accordingly, the 3GPP CT4 working group studied in 3GPP TR 29.892 16.0.0 titled “Study on User Plane Protocol in 5GC” (September 2019), the potential use of SRv6 in the 5G System (5GS) transport layer. While SRv6 was acknowledged as a viable transport option, the study did not introduce support for SRv6 in the 5GS control plane. This means SRv6 can be used for transport, but capabilities such as deterministic path control and network programming are not yet integrated into the 5GS signalling or service orchestration.

[0058] Figure 2 illustrates the Home-routed Roaming architecture 200 for 5GS. The architecture 200 may implement or be implemented by aspects of the wireless communication system 100. For example, the architecture 200 may include a UE 210, a VPLMN 211 and an HPLMN 221 which may be one or more examples of devices described herein with reference to Figure 1. The VPLMN 211 may comprise a RAN 212, an AMF 214, a vUPF 216 and a vSMF 218. The HPLMN 221 may comprise an hUPF 226, an hSMF 228, and a data network 240.

[0059] When introducing SRv6 on the N9 interface in a Home-Routed (HR) Roaming architecture, the hUPF 226 in the HPLMN 221 encapsulates each downlink packet in an IPv6 header and includes an SRH containing a list of Segment IDs (SIDs) that define the downlink path. Similarly, the vUPF 216 in the VPLMN 211 or the RAN 212 encapsulates each uplink packet in an IPv6 header with an SRH that includes the uplink segment addresses.

[0060] Figure 3 illustrates an example deployment 300 of a HR roaming scenarios where two SRv6-aware Edge Routers (Cl and C2, 341 and 342) are used in the transport plane to forwards PDUs from the vUPF (Ul, 316) to the hUPF (U2, 326) and vice versa. The example deployment 300 may implement or be implemented by aspects of the wireless communication system 100. The example deployment 300 comprises a UE 310, a VPLMN 311 and an HPLMN 321. The VPLMN 311 comprises a RAN 312, a vUPF Ul 316, and an edge router Cl 341. The HPLMN 321 comprises an edge router C2 342, an hUPF U2 326 and a data network 340. Figure 3 also illustrates the composition of data packets at hops, or sections of the wireless communication network between these network nodes and network functions. Figure 3 illustrates a downlink path 344 and an uplink path 346.Docket No. SMM920250140-GR-NP

[0061] Figure 3 shows the composition of downlink packets along the downlink path 344. A downlink PDU originates in the data network 340 and is sent towards the UE 310. In the hops between the hUPF U2 326 and the edge router C2 342, and between the edge router C2 342 and the edge router Cl 341, the downlink PDU includes both an IPv6 header and an SR header. The SR header is omitted from the downlink PDU in the hops between the edge router Cl 341 and the vUPF ul 316, and between the vUPF U1 316 and the RAN 312.

[0062] Figure 3 also shows the composition of uplink packets along the uplink path 346. An uplink PDU originates in the UE 310 and is sent towards the data network 340. In the hops between the vUPF Ul 316 and the edge router Cl 341, and between the edge router Cl 341 and the edge router C2 342, the uplink PDU includes both an IPv6 header and an SR header. The SR header is omitted from the uplink PDU in the hops between the RAN 312 and the vUPF ul 316, and between the edge router C2 342 and hUPF U2 326.

[0063] The vUPF Ul 316 includes an SRH in every uplink packet, with a SID list that specifies the segments, namely the IPv6 addresses of the hUPF U2 326, Edge Router C2 342, and Edge Router Cl 341, in reverse order of traversal. This means the final destination appears first in the list. Similarly, the hUPF U2 326 includes an SRH in every downlink packet with a SID list that defines the segments of the downlink path. The SRH contains a parameter called Segment Left (SL), which indicates the next segment in the SID list. When an edge router receives a packet, it updates the IPv6 destination address with the next segment from the list, decrements the SL value, and forwards the packet. In this example, the Tunnel Endpoint Identifier (TEID) is encoded into the SID of the RAN 312, vUPF Ul 316, and hUPF U2 326 to enable direct mapping of a packet to a specific PDU session. The encoding of the TEID is based on an implementation-specific SID format, such as locator: :function:args, which may vary between PLMNs.

[0064] Although 3GPP TR 29.892 vl6.0.0 section 6.2.2.10 proposes an extension to the N16 interface by introducing a new “SRv6 Capable” Information Element (IE) in the Nsmf_PDUSession_Create Request / Response messages, allowing the vSMF and hSMF to learn about SRv6 support on the N9 interface, it does not define how the UPF obtains the SRH with the SID list for either the downlink or uplink path.Docket No. SMM920250140-GR-NP

[0065] It should be noted that provisioning the SID list via the management plane is not feasible in a Home-Routed Roaming architecture when the VPLMN and HPLMN belong to different domains with independent management systems.

[0066] There are provided herein solutions to enable Inter-Domain Service Chaining using SRv6, and which facilitate Home-Routed Roaming, MEC, and Private 5G deployments.

[0067] There is provided herein a mechanism for the SMF or UPF to learn the SID list or the SID format and encoding (e.g., QFI, TEID / PDU Session ID) of the remote PLMN via the N16 interface. Such an arrangement advantageously facilitates inter-domain SRv6 service chaining. The arrangement described herein further tends to facilitate QoS enforcement using SRv6.

[0068] In some examples, the proposed arrangement provides support for the dynamic exchange and interpretation of domain specific SID lists to enable inter domain service chaining. In some examples, the proposed arrangement provides support for domain specific SID encoding formats (i.e., encoding of the QFI and PDU Session ID into the IPv6 address). In some examples, the proposed arrangement provides support for the dynamic exchange and interpretation of domain specific SID encoding formats to enable inter domain QoS handling and policy rule enforcement. In some examples, the proposed arrangement provides support for QoS flow specific Service Chains to allow differentiated handling e.g. deep packet inspection (DPI) for video, low latency for voice, and firewall for data).

[0069] Enhancements to the Nsmf PDUSession service operations for home-routed roaming scenarios over the N16 are described herein. In some examples these may tend to support the exchange of Uplink SID list specifying the service chain an uplink data packet should traverse towards the UPF in the home PLMN. In some examples there might be a separate uplink SID list per QoS Flow to allow differentiated traffic handling. In some examples these may tend to support the exchange of the Downlink SID list specifying the service chain a downlink data packet should traverse towards the UPF in the visited PLMN. In some examples there might be a separate downlink SID list per QoS Flow to allow differentiated traffic handling. In some examples these may tend to support the IPv6Docket No. SMM920250140-GR-NPlocator prefix of the home UPF and visited UPF. In some examples these may tend to support the SID format encoding template (locator: :function:args) of the home Network and visited Network.

[0070] Enhancements to the PFCP Session Establishment procedure and the PFCP Session Update procedure over the N4 interface are described herein. In some examples these may tend to support the exchange of Uplink SID list specifying the service chain an uplink data packet should traverse towards the UPF in the home PLMN. There may be provided a separate uplink SID list per QoS Flow to allow differentiated traffic handling. In some examples these may tend to support the exchange of Downlink SID list specifying the service chain a downlink data packet should traverse towards the UPF in the visited PLMN. There may be provided a separate downlink SID list per QoS Flow to allow differentiated traffic handling. In some examples these may tend to support the exchange of IPv6 locator prefix of the home UPF and visited UPF. In some examples these may tend to support the exchange of the SID format encoding template (locator: :function:QFI:args) of the home Network and visited Network.

[0071] The following options are examples of how the uplink SID list may be generated.

[0072] The hSMF may provide to the vSMF, via the N16 interface, an uplink SID list per QoS flow with PDU Session ID and / or QFI encoding embedded in the SID of the hUPF. The vSMF may then append the SIDs of the uplink path in the visited PLMN as needed to the received SID list and forward the updated SID list per QoS flow to the vUPF via the N4 interface. Alternatively, or additionally, the vUPF may append the SID list per QoS flow with the SIDs of the uplink path to the received SID list. The vUPF, based on the PDU Session ID and / or QFI of the uplink packet, may add an SRH with the SID list to the uplink packet.

[0073] Alternatively, the hSMF may provide to the vSMF, via the N16 interface, a single SID list for the PDU session, the IPv6 locator prefix of the hUPF, and the SID format encoding template. The vSMF may then append the SIDs of the uplink path in the visited domain as needed to the received SID list, generate a SID list per QoS flow by encoding the PDU Session ID and / or the QFI into the SID of the hUPF, and forward theDocket No. SMM920250140-GR-NPSID list per QoS flow to the vUPF via the N4 interface. The vUPF, based on the PDU Session ID and / or QFI of the uplink packet, may add an SRH with the SID list to the uplink packet.

[0074] The hSMF may provide to the vSMF, via the N16 interface, a single SID list for the PDU session, the IPv6 locator prefix, and the SID format encoding template. The vSMF may append the SIDs of the uplink path in the visited domain as needed to the received SID list and forward the updated SID list for the PDU session, the IPv6 locator prefix, and the SID format encoding template to the vUPF via the N4 interface. The vUPF, based on the PDU Session ID and / or QFI of the uplink packet, may encode the PDU Session ID and / or QFI into the SID of the hUPF and add an SRH with the SID list to the uplink packet.

[0075] The following options are examples of how the downlink SID list may be generated.

[0076] The vSMF may provide to the hSMF, via the N16 interface, a downlink SID list per QoS flow with PDU Session ID and / or QFI encoding embedded in the SID of the vUPF. The hSMF may append the SIDs of the downlink path in the home PLMN as needed to the received SID list per QoS flow and forwards the updated SID list per QoS flow to the hUPF via the N4 interface. The hUPF, based on the PDU Session ID and / or QFI of the downlink packet, may add an SRH with the SID list to the downlink packet.

[0077] The vSMF may provide to the hSMF, via the N16 interface, a single SID list for the PDU session, the IPv6 locator prefix of the vUPF, and the SID format encoding template. The hSMF may append the SIDs of the downlink path in the home PLMN as needed to the received SID list, generate a SID list per QoS flow by encoding the PDU Session ID and / or the QFI into the SID of the vUPF, and forward the SID list per QoS flow to the hUPF via the N4 interface. The hUPF, based on the PDU Session ID and / or QFI of the downlink packet, may add an SRH with the SID list to the downlink packet.

[0078] The vSMF may provide to the hSMF, via the N16 interface, a single SID list for the PDU session, the IPv6 locator prefix, and the SID format encoding template. The home SMF may append the SIDs of the downlink path in the home PLMN as needed to theDocket No. SMM920250140-GR-NPreceived SID list and forwards the updated SID list for the PDU session, the IPv6 locator prefix, and the SID format encoding template to the hUPF via the N4 interface. The hUPF, based on the PDU Session ID and / or QFI of the downlink packet, may encode the PDU Session ID and / or QFI into the SID of the vUPF and add an SRH with the SID list to the downlink packet.

[0079] Accordingly, the vSMF may retrieve the uplink SID list specifying the uplink path in the visited PLMN, along with the IPv6 locator prefix of the vUPF and the SID format encoding template, from the vUPF and / or from local configuration. Similarly, the hSMF may retrieve the downlink SID list specifying the downlink path in the home PLMN, the IPv6 locator prefix of the hUPF, and the SID format encoding template, from the hUPF and / or from local configuration.

[0080] The encoding of the PDU Session ID and QFI may be performed by, for example: PDU Session ID and / or QFI encoding embedded in the SID; and / or PDU Session ID and / or QFI encoding provided in TLVs instead of encoding in the SID.

[0081] Additional support may be provided for per PSI SID lists. In addition to per QFI and per PDU session SID lists, the arrangements described herein may be extended to support per PSI SID lists. This enhancement enables more refined service chaining and QoS enforcement by allowing the SMF, vSMF, or LSMF to generate and exchange SID lists tailored to the importance level of a PDU Set within a Qos flow. By associating specific SID lists with different PSI values, operators can prioritize traffic based on its criticality, for example, ensuring low-congestion paths for high-importance PDU sets, while applying standard processing for less critical PDU sets. These per PSI SID lists can be exchanged over N16, N16a, N4, N2 and network exposure interfaces. The PSI values may be either embedded in the SID or conveyed via TLVs.

[0082] Additional support may be provided for LSMF / SMF scenarios. In addition to the home-routed roaming case using the N16 interface between vSMF and hSMF, the arrangements described herein may also support scenarios where an LSMF controls an I- UPF in one domain (e.g. for EAS, local breakout, or private 5G) while the anchor UPF remains under the control of an SMF in another domain. In these cases, the exchange of uplink and downlink SID lists, locator prefixes, and SID format encoding templates isDocket No. SMM920250140-GR-NPperformed over the N16a interface between the SMF and I-SMF, and over N4 towards their respective UPFs. As with the vSMF / hSMF case, the SID lists may be provided per PSI, per QoS flow or per PDU session, with PDU Session ID, QFI, PSI either embedded in the SID or carried in TLVs, ensuring consistent service chaining and QoS enforcement across domains.

[0083] Support of inter-domain service chaining over the N3 interface may be provided. In addition to supporting inter-domain service chaining over the N9 interface, the arrangements described herein may be extended to enable SRv6 operation over the N3 interface, allowing service chaining and QoS enforcement to begin directly at the RAN. This includes support for scenarios where part of the downlink service chain resides in the RAN, such as RAN-based firewalls, edge analytics, or enterprise-specific service functions. In such cases, the gNodeB may define a local downlink SID list, which can be provided to the SMF via the N2 interface using NGAP signaling extensions or via a management / configuration interface. The SMF retrieves this RAN-specific SID list and appends it to the core network SID list, forming a complete end-to-end service chain. This combined SID list, along with the SID format encoding template and IPv6 locator prefixes, is then provided to the UPF via the N4 interface, enabling the UPF to construct the SRH for downlink packets before forwarding them to the gNodeB over the N3 interface. For uplink traffic, the gNodeB inserts the SRH based on SID lists received from the SMF or derived from local configuration. The SMF may also retrieve the RAN-specific uplink SID list from the gNodeB to gain visibility into the RAN service path. Additionally, the SMF derives the core network uplink SID list by querying the UPF or using local configuration and policy rules, ensuring that the complete uplink service chain is consistently applied across both RAN and core network domains. The arrangements described herein may support SID list granularity at the level of per QFI, per PSI, or per PDU session ID, with PDU Session ID, QFI values, PSI values either embedded in the SID or carried in TLVs, depending on the domain’s encoding strategy.

[0084] Support of inter-domain service chaining over the N6 interface may be provided. To support edge computing scenarios where the edge platform resides in a separate domain, the arrangements described herein may be extended to enable interDocket No. SMM920250140-GR-NPdomain service chaining over the N6 interface. This allows traffic to be steered through service functions hosted on external edge platforms such as MEC applications, enterprise gateways, or localized breakout nodes before reaching the Data Network. To enable coordinated service chaining across domains, the arrangements described herein may introduce the use of the network exposure interface between the SMF / PCF and the edge platform. For uplink traffic, the SMF receives form the PCF / edge platform via network exposure the uplink SID list, the SID format encoding template, and IPv6 locator prefixes associated with service functions in the edge domain. Since the edge platform is not aware of QFI, PSI, or PDU session IDs, the SMF and / or the PCF is responsible for mapping these parameters to the appropriate SID list granularity (per QFI, per PSI, or per PDU session ID) and distributing the correct SID list to the UPF for SRH insertion. For downlink traffic, the SMF provides the downlink SID list to the PCF / edge platform via the same network exposure interface. To support per QFI SID lists, the PCF may translate the SID list associated with each QFI into a per-packet-filter SID list before forwarding it to the edge platform. The edge platform receives the list and appends it to the edge domain SID list, forming a complete end-to-end service chain, and uses this SID list to apply the SRH to downlink packets before forwarding them towards the core network.

[0085] Figures 4a and 4b illustrate an example of a process flow 400 in accordance with aspects of the present disclosure. The process flow 400 may implement or be implemented by aspects of the wireless communication system 100. For example, the process flow 400 may include a UE 410, a RAN 412, an AMF 414, a vUPF 416, a vSMF 418, an hUPF 426, an hSMF 428, an hPCF 430 and a UDM 432, which may be one or more examples of devices described herein with reference to Figure 1. A VPLMN 411 may comprise the RAN 412, the AMF 414, the vUPF 416, and the vSMF 418. An HPLMN 421 may comprise the hUPF 426, the hSMF 428, the hPCF 430 and the UDM 432.

[0086] The process flow 400 may be referred to as a procedure, including one or more operations performed by one or more of the UE 410, the RAN 412, the AMF 414, the vUPF 416, the vSMF 418, the hUPF 426, the hSMF 428, the hPCF 430 and the UDM 432. In the example of Figures 4a and 4B, the process flow 400 may include a process for UE- requested PDU Session Establishment for home-routed roaming scenarios.Docket No. SMM920250140-GR-NP

[0087] In the following description of the process flow 400, the operations or signalling performed between one or more of the UE 410, the RAN 412, the AMF 414, the vUPF 416, the vSMF 418, the hUPF 426, the hSMF 428, the hPCF 430 and the UDM 432may be performed or signalled (e.g., transmitted, received) in a different order than the example order shown, or the operations or signalling performed by one or more of the UE 410, the RAN 412, the AMF 414, the vUPF 416, the vSMF 418, the hUPF 426, the hSMF 428, the hPCF 430 and the UDM 432may be performed or signalled (e.g., transmitted, received) in different orders or at different times. Some operations or signalling may also be omitted from the process flow 400. Additionally, although some operations or signalling may be shown to occur at different times, these operations or signalling may occur at the same time or in overlapping time periods.

[0088] Figures 4a and 4b illustrates a process for UE-requested PDU Session Establishment for home-routed roaming scenarios. This figure is derived from Figure 4.3.2.2.2-1 of 3GPP TS 23.502 vl9.4.0 (June 2025) titled “Procedures for the 5G System (5GS)”. There are described herein some changes to are suggested to Figure 4.3.2.2.2-1 so as to facilitate Inter-domain service chaining and QoS enforcement using SRv6.

[0089] The process flow 400 begins at 471 when the UE 410 may send (e.g. transmit, output), and the AMF 414 may receive (e.g. acquire, obtain), a PDU session establishment request. At 472 the AMF 414 may make a selection of an SMF.

[0090] At 473a the AMF 414 may send (e.g. transmit, output), and the vSMF 418 may receive (e.g. acquire, obtain), an Nsmf_PDUSession_CreateSMContext Request. At 473b the vSMF 418 may send (e.g. transmit, output), and the AMF 414 may receive (e.g. acquire, obtain), an Nsmf_PDUSession_CreateSMContext Response. At 474 the vSMF 418 may make a selection of a UPF.

[0091] At 475a the vSMF 418 may send (e.g. transmit, output), and the vUPF 416 may receive (e.g. acquire, obtain), an N4 Session Establishment Request. The vSMF 418 initiates an N4 Session Establishment procedure with the selected vUPF 416. The vSMF 418 sends an N4 Session Establishment Request to the vUPF 416. The vSMF 418 provides Trace Requirements to the vUPF 416 if the vSMF 418 has received Trace Requirements from the AMF 414. If vSMF 418 supports HR-SBO and receives HR-SBO allowedDocket No. SMM920250140-GR-NPindication from the AMF 414 for this PDU session, vSMF 418 includes SUPI of the UE 410, HPLMN DNN and S-NSSAI, and an indication that the UE PDU session is working in HR-SBO mode. If SRv6 in HR-Roaming scenario is supported, the vSMF 418 includes an indication in the N4 Session Establishment Request for the vUPF 416 to provide SRv6 information.

[0092] At 475b the vUPF 416 may send (e.g. transmit, output), and the vSMF 418 may receive (e.g. acquire, obtain), an N4 Session Establishment Response. The vUPF 416 acknowledges the N4 Session Establishment Request by sending an N4 Session Establishment Response. The CN Tunnel Info is provided to vSMF 418 in this step. If requested, the vUPF 416 includes SRv6 information (the IPv6 Locator prefix, the Downlink SID list and the Downlink SID format encoding template).

[0093] At 476 the vSMF 418 may send (e.g. transmit, output), and the hSMF 428 may receive (e.g. acquire, obtain), an Nsmf PDUSession Create Request. TheNsmf PDUSession Create Request may include any combination of the following: (SUPI, GPSI (if available), V-SMF SM Context ID, DNN, S-NSSAI with the value defined by the HPLMN, [HPLMN Alternative S-NSSAI], PDU Session ID, SRv6 information (Downlink SID list, IPv6 Locator prefix, Downlink SID format encoding template), V-SMF ID, V-CN- Tunnel-Info, PDU Session Type, PCO, Number Of Packet Filters, User location information, Access Type, RAT Type, PCF ID, [Small Data Rate Control Status], SM PDU DN Request Container, DNN Selection Mode, Control Plane CIoT 5GS Optimisation Indication, [Always-on PDU Session Requested], AMF ID, Serving Network, [ECS Address Configuration Information associated with PLMN ID of visited network], the QoS constraints from the VPLMN, Satellite backhaul category, Disaster Roaming service indication, [URSP rule enforcement reports]) or Nsmf PDUSession Update Request (V- CN-Tunnel-Info, SRv6 information (Updated downlink SID list, IPv6 Locator prefix, Downlink SID format encoding template), PCO, User location information, Access Type, RAT Type, SM PDU DN Request Container, Control Plane CIoT 5GS Optimisation Indication, [Always-on PDU Session Requested], Serving Network, Satellite backhaul category, [URSP rule enforcement reports]). Protocol Configuration Options may contain information that H-SMF may needs to properly establish the PDU Session (e.g. SSC modeDocket No. SMM920250140-GR-NPor SM PDU DN Request Container to be used to authenticate the UE by the DN-AAA). The H-SMF may use DNN Selection Mode when deciding whether to accept or reject the UE request. If the V-SMF does not receive any response from the H-SMF due to communication failure on the N16 interface, depending on operator policy the V-SMF may create the PDU Session to one of the alternative H-SMF(s) if additional H-SMF information is provided in step 473a. The Small Data Rate Control Status is included if received from the AMF. The Control Plane CIoT 5GS Optimisation Indication is set by the V-SMF, if the PDU Session is intended for Control Plane CIoT 5GS Optimisation. The Disaster Roaming service indication is included if the indication is received from AMF in step 473a above.

[0094] The QoS constraints from the VPLMN may be provided by the VPLMN to avoid the risk that V-SMF rejects the PDU Session in step 483 when controlling SLA with the HPLMN. The V-SMF SM Context ID contains the addressing information it has allocated for service operations related with this PDU Session. The H-SMF stores an association of the PDU Session and V-SMF Context ID for this PDU Session for this UE 410.

[0095] The SRv6 capability information may contain information on SRv6 support for the downlink data towards the V-UPF. The Downlink SID list may contain the segment identifiers of the downlink data path towards the V-UPF. The IPv6 Locator prefix may contain the IPv6 Locator prefix of the downlink data towards the V-UPF. The Downlink SID format encoding template may contain the SID format encoding template of the downlink data towards the V-UPF.

[0096] At 477, the hSMF 428 may retrieve subscription data from the UDM 432.

[0097] At 478 PDU session authentication and authorization is performed by the system.

[0098] At 479a, the hSMF 428 performs PCF selection.

[0099] At 479b SM Policy Association Establishment or SMF initiated SM Policy Association Modification is performed by the hPCF 430 and the hSMF 428.Docket No. SMM920250140-GR-NP

[0100] At 480, the hSMF 428 performs UPF selection.

[0101] At 481 SMF initiated SM Policy Association Modification is performed by the hPCF 430 and the hSMF 428.

[0102] At 482a the hSMF 428 may send (e.g. transmit, output), and the hUPF 426 may receive (e.g. acquire, obtain), an N4 Session Establishment Request. The hSMF 428, based on the SRv6 information received in step 476, derives the Downlink SID list. The hSMF 428 includes the derived Downlink SID list, the IPv6 Locator prefix, and the Downlink SID format encoding template in the N4 Session Establishment / Modification Request.

[0103] At 482b, the hUPF 426 may send (e.g. transmit, output), and the hSMF 428 may receive (e.g. acquire, obtain), an N4 Session Establishment Response, the hUPF 426 may include SRv6 information (the Uplink SID list, the IPv6 Locator prefix, and the Uplink SID format encoding template) in the N4 Session Establishment / Modification Response.

[0104] At 482c, the hSMF 428 performs registration with the UDM 432.

[0105] At 483 the hSMF 428 may send (e.g. transmit, output), and the vSMF 418 may receive (e.g. acquire, obtain), an Nsmf PDUSession Create Response. TheNsmf PDUSession Create Response may comprise, for example: (QoS Rule(s), QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s), PCO including session level information that the vSMF 418 is not expected to understand, selected PDU Session Type and SSC mode, Reliable Data Service Support, H-CN Tunnel Info, SRv6 information (Uplink SID list, IPv6 Locator prefix, Uplink SID format encoding template), QFI(s), QoS profile(s), Session-AMBR, Reflective QoS Timer (if available), information needed by vSMF 418 in the case of EPS interworking such as the PDN Connection Type, User Plane Policy Enforcement, [ECS Address Configuration Information for the serving PLMN]).

[0106] If the PDU Session being established was requested to be an always-on PDUSession, the hSMF 428 may indicate to the vSMF 418 whether the request is accepted or not via the Always-on PDU Session Granted indication in the response message to vSMF 418. If the PDU Session being established was not requested to be an always-on PDU Session but the hSMF 428 determines that the PDU Session needs to be established as anDocket No. SMM920250140-GR-NPalways-on PDU Session, the hSMF 428 may indicate it to the vSMF 418 by including Always-on PDU Session Granted indication that the PDU Session is an always-on PDU Session.

[0107] The SRv6 capability information may contain information on SRv6 support for the uplink data towards the hUPF 426. The Uplink SID list may contain the segment identifiers of the uplink data path towards the hUPF 426. The IPv6 Locator prefix may contain the IPv6 Locator prefix of the uplink data towards the hUPF 426. The Uplink SID format encoding template may contain the SID format encoding template of the uplink data towards the hUPF 426.

[0108] At 483a the vSMF 418 may send (e.g. transmit, output), and the vUPF 416 may receive (e.g. acquire, obtain), an N4 Session Modification Request. At 483b the vUPF 416may send (e.g. transmit, output), and the vSMF 418 may receive (e.g. acquire, obtain), an N4 Session Modification Response. The vSMF 418 initiates an N4 Session Modification procedure with the vUPF 416. The vSMF 418 may provide N4 rules to the vUPF 416 for this PDU Session, including rules to forward UL traffic to the hUPF 426.The vSMF 418, based on the SRv6 information received in step 483, may derive the Uplink SID list, and provide the Uplink SID list, the IPv6 Locator prefix, and the Uplink SID format encoding template to the vUPF 416.

[0109] Steps 484 to 494 are executed as described with reference to Figure 4.3.2.2.2-1 in 3 GPP TS 23.502 vl9.4.0.

[0110] Figures 5a and 5b illustrate an example of a process flow 500 in accordance with aspects of the present disclosure. The process flow 500 may implement or be implemented by aspects of the wireless communication system 100. For example, the process flow 500 may include a UE 510, a RAN 512, an AMF 514, a vUPF 516, a vSMF 518, an hUPF 526, an hSMF 528, an hPCF 530 and a UDM 532, which may be one or more examples of devices described herein with reference to Figure 1. A VPLMN 511 may comprise the RAN 512, the AMF 514, the vUPF 516, and the vSMF 518. An HPLMN 521 may comprise the hUPF 526, the hSMF 528, the PCF 530 and the UDM 532.Docket No. SMM920250140-GR-NP

[0111] The process flow 500 may be referred to as a procedure, including one or more operations performed by one or more of the UE 510, the RAN 512, the AMF 514, the vUPF 516, the vSMF 518, the hUPF 526, the hSMF 528, the PCF 530 and the UDM 532. In the example of Figures 5a and 5B, the process flow 500 may include a process for UE or network requested PDU Session Modification for a home-routed roaming scenario.

[0112] In the following description of the process flow 500, the operations or signalling performed between one or more of the UE 510, the RAN 512, the AMF 514, the vUPF 516, the vSMF 518, the hUPF 526, the hSMF 528, the PCF 530 and the UDM 532may be performed or signalled (e.g., transmitted, received) in a different order than the example order shown, or the operations or signalling performed by one or more of the UE 510, the RAN 512, the AMF 514, the vUPF 516, the vSMF 518, the hUPF 526, the hSMF 528, the PCF 530 and the UDM 532may be performed or signalled (e.g., transmitted, received) in different orders or at different times. Some operations or signalling may also be omitted from the process flow 500. Additionally, although some operations or signalling may be shown to occur at different times, these operations or signalling may occur at the same time or in overlapping time periods.

[0113] Figures 5a and 5b illustrates a process for UE or network requested PDU Session Modification for a home-routed roaming scenario. This figure is derived from Figure 4.3.3.3-1 of 3GPP TS 23.502 vl9.4.0. There are described herein some changes to Figure 4.3.3.3-1 of 3GPP TS 23.502 vl9.4.0 so as to facilitate Inter-domain service chaining and QoS enforcement using SRv6.

[0114] The process flow 500 begins at 571 when the UE 510 may send (e.g. transmit, output), and the AMF 514 may receive (e.g. acquire, obtain), a PDU session establishment request. At 572 the AMF 514 may make a selection of an SMF.

[0115] Steps 571 and 572 are executed as described with reference to Figure 4.3.3.3-1 in 3GPP TS 23.502 vl9.4.0. These steps include a PDU session modification request being sent from the UE 510 to AMF 514. These steps also include a PCF initiated SM policy association modification, and an SMF initiated SM policy association modification.Docket No. SMM920250140-GR-NP

[0116] At 573 the hSMF 528 may send (e.g. transmit, output), and the vSMF 518 may receive (e.g. acquire, obtain), a Nsmf PDUSession Update Request.

[0117] At 573a the hSMF 528 may send (e.g. transmit, output), and the hUPF 526 may receive (e.g. acquire, obtain), an N4 Session Modification Request. At 537b the hUPF 526 may send (e.g. transmit, output), and the hSMF 528 may receive (e.g. acquire, obtain), an N4 Session Modification Response. These steps are executed if new QoS Flow(s) are to be created. The hSMF 528 updates the hUPF 526 with UL Packet Detection Rules of the new QoS Flow. In step 573b the hUPF 526 may include the SRv6 information (the Uplink SID list, the IPv6 Locator prefix, and the Uplink link SID format encoding template) in the N4 Session Modification Response. These steps are executed if the HPLMN S-NSSAI is replaced by an Alternative HPLMN S-NSSAI and the PDU Session is retained. The hSMF 528 updates the hUPF 526 with Alternative S-NSSAI.

[0118] Steps 574 to 578 are executed as described with reference to Figure 4.3.3.3-1 in 3GPP TS 23.502 V19.4.0.

[0119] At 579a the vSMF 518 may send (e.g. transmit, output), and the vUPF 516 may receive (e.g. acquire, obtain), an N4 Session Modification Request. The vSMF 518 includes the derived Uplink SID list, the IPv6 Locator prefix, and the Uplink SID format encoding template in the N4 Session Modification Request.

[0120] At 579b the vUPF 516 may send (e.g. transmit, output), and the vSMF 518 may receive (e.g. acquire, obtain), N4 Session Modification Response. The vUPF 516 may include the SRv6 information (Downlink SID list, the IPv6 Locator prefix, and the Downlink SID format encoding template) in the N4 Session Modification Response.

[0121] Steps 580 to 584 are executed as described with reference to Figure 4.3.3.3-1 in 3GPP TS 23.502 V19.4.0.

[0122] At 585 the vSMF 518 may send (e.g. transmit, output), and the hSMF 528 may receive (e.g. acquire, obtain), an Nsmf PDUSession Update Response. The Nsmf PDUSession Update response may carry information such as PCO provided by the UE 510 in the SM PDU Session Modification Command Ack message from the UE 510 to the vSMF 518, Secondary RAT usage data. The hSMF 528 shall modify the PDU SessionDocket No. SMM920250140-GR-NPcontext. The vSMF 518 includes the SRv6 information (the Downlink SID list, the IPv6 Locator prefix, and the Downlink SID format encoding template) received in step 589b in the Nsmf PDUSession Update response.

[0123] If the V-SMF has rejected QFI(s) (at step 573) or the (R)AN 512 has rejectedQFI(s) in step 6 of Figure 4.3.3.2-1 in 3GPP TS 23.502 vl9.4.0, the hSMF 528 is responsible of later updating the QoS rules and QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s) in the UE 510.

[0124] At 586a the hSMF 528 may send (e.g. transmit, output), and the hUPF 526 may receive (e.g. acquire, obtain), an N4 Session Modification Request. The hSMF 528, based on the SRv6 information received in step 585, may derive the Downlink SID list. The hSMF 528 may include the derived Downlink SID list, the IPv6 Locator prefix, and the Downlink SID format encoding template in the N4 Session Modification Request.

[0125] It is noted that section 5.2.8.2.2 of 3GPP TS 23.502 vl9.4.0 describes Nsmf PDUSession Create service operation. The Service operation name:Nsmf PDUSession Create may include as an optional input SRv6 information (Downlink SID list, IPv6 Locator prefix, Downlink SID format encoding template).

[0126] It is further noted that section 5.2.8.2.3 of 3GPP TS 23.502 vl9.4.0 describes Nsmf PDUSession Update service operation. The service operation name:Nsmf PDUSession Update may include as an optional input SRv6 information (Downlink SID list, IPv6 Locator prefix, Downlink SID format encoding template). The service operation name: Nsmf PDUSession Update may include as an optional output SRv6 information (Uplink SID list, IPv6 Locator prefix, Uplink SID format encoding template).

[0127] 3GPP TS 29.244 vl9.2.0 (June 2025) is titled “Interface between the Control Plane and the User Plane nodes” and defines at section 7.5.2.3 “Create FAR IE within PFCP Session Establishment Request”. Table 7.5.2.3-2 defines: Forwarding Parameters IE in FAR. This table may be modified to include at least one of the following additional information elements.Docket No. SMM920250140-GR-NPTable 1: IES that may be added to Table 7.5.2.3-2 of 3GPP TS 29.244 v!9.2.0

[0128] 3GPP TS 29.244 vl9.2.0 defines at section 7.5.3.2 “Created PDR IE within PFCP Session Establishment Response”. This may be modified to define “Created PDR IE within PFCP Session Establishment Response or PFCP Session Modification Response”. Further, table 7.5.3.2-1 defines: Created PDR IE within PFCP Session Establishment Response. This table may be modified to include at least one of the following additional information elements.Table 2: IEs that may be added to Table 7.5.3.2-1 of 3GPP TS 29.244 vl9.2.0

[0129] 3GPP TS 29.244 vl9.2.0 defines at section 7.5.4.3 “Update FAR IE within PFCP Session Modification Request”. Table 7.5.4.3-2 defines: Update Forwarding Parameters IE in the Update FAR IE. This table may be modified to include at least one of the following additional information elements.Docket No. SMM920250140-GR-NPTable 3: IES that may be added to Table 7.5.4.3-1 of 3GPP TS 29.244 v!9.2.0

[0130] Figure 6 gives an example of how the SRv6 locator prefix information element may be encoded. Figure 6 shows a number of bits 601 and a number of octets 608. Octets 1 to 2 carry Type = NN (decimal). Octets 3 to 4 carry Length = n. Octets 5 to 20 carry IPv6 Locator prefix. Octets b to (n+4) are present only if explicitly specified.

[0131] Figure 7 gives an example of how the SID format encoding template information element may be encoded. Figure 7 shows a number of bits 701 and a number of octets 708. Octets 1 to 2 carry Type = NM (decimal). Octets 3 to 4 carry Length = n. Octet 5 carries: Spare, FLAGS, PSI, QFI, PDU Session ID, FUNC, & LOC. Octet 6 carries Locator length value. Octet 7 carries Function length value. Octet m carries PDU Session ID length value. Octet o carries QFI length value. A further octet may carry the PSI length value. Octet p carries FLAGS length value. Octets q to (n+4) are present only if explicitly specified.

[0132] The following flags are coded within Octet 5.

[0133] Bit 1 - LOC: This bit is always set to “1” and indicates that the Locator field is present in the SID with its length specified in bits by the Locator length value.

[0134] Bit 2 - FUNC: If this bit is set to “1”, the Function field shall be present in the SID, with its length specified in bits by the Function length value. Otherwise, the Function length value shall not be present in this IE, and the Function field shall not be present in the SID.Docket No. SMM920250140-GR-NP

[0135] Bit 3 - PDU Session ID: If this bit is set to “1”, the PDU Session ID field shall be present in the SID, with its length specified in bits by the PDU Session ID length value. Otherwise, the PDU Session ID length value shall not be present in this IE, and the PDU Session ID field shall not be present in the SID.

[0136] Bit 4 - QFI: If this bit is set to “1”, the QFI field shall be present in the SID, with its length specified in bits by the QFI length value. Otherwise, the QFI length value shall not be present in this IE, and the QFI field shall not be present in the SID.

[0137] Bit 5 - PSI: If this bit is set to “1”, the PSI field shall be present in the SID, with its length specified in bits by the PSI length value. Otherwise, the PSI length value shall not be present in this IE, and the PSI field shall not be present in the SID.

[0138] Bit 6 - FLAGS: If this bit is set to “1”, the FLAGS field shall be present in the SID, with its length specified in bits by the FLAGS length value. Otherwise, the FLAGS length value shall not be present in this IE, and the FLAGs field shall not be present in the SID.

[0139] Bit 8 - Spare: For future use and set to “0”.

[0140] The following notes may apply. If the PDU Session ID length value is 0, the PDU Session ID field is not encoded in the SID and is instead encoded as a TLV within the SRH. If the QFI length value is 0, the QFI field is not encoded in the SID and is instead encoded as a TLV within the SRH. If the PSI length value is 0, the PSI field is not encoded in the SID and is instead encoded as a TLV within the SRH. If the Flags length value is 0, the Flags field is not encoded in the SID and is instead encoded as a TLV within the SRH.

[0141] Figure 8 gives an example of how the SRv6 SID list information element may be encoded. Figure 8 shows a number of bits 801 and a number of octets 808. Octets 1 to 2 carry Type = NO (decimal). Octets 3 to 4 carry Length = n. Octet 5 carry a number of SID elements. Octets 6 to 5+x*16 carry SIDs. Octets b to (n+4) are present only if explicitly specified.

[0142] Figure 9 illustrates an example of a UE 900 in accordance with aspects of the present disclosure. The UE 900 may include a processor 902, a memory 904, a controllerDocket No. SMM920250140-GR-NP906, and a transceiver 908. The processor 902, the memory 904, the controller 906, or the transceiver 908, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0143] The processor 902, the memory 904, the controller 906, or the transceiver 908, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0144] The processor 902 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 902 may be configured to operate the memory 904. In some other implementations, the memory 904 may be integrated into the processor 902. The processor 902 may be configured to execute computer-readable instructions stored in the memory 904 to cause the UE 900 to perform various functions of the present disclosure.

[0145] The memory 904 may include volatile or non-volatile memory. The memory 904 may store computer-readable, computer-executable code including instructions when executed by the processor 902 cause the UE 900 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 904 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general -purpose or special-purpose computer.

[0146] In some implementations, the processor 902 and the memory 904 coupled with the processor 902 may be configured to cause the UE 900 to perform one or more of the functions described herein (e.g., executing, by the processor 902, instructions stored in the memory 904). For example, the processor 902 may support wireless communication at theDocket No. SMM920250140-GR-NPUE 900 in accordance with examples as disclosed herein. The UE 900 may be configured to support the arrangements described herein.

[0147] The controller 906 may manage input and output signals for the UE 900. The controller 906 may also manage peripherals not integrated into the UE 900. In some implementations, the controller 906 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 906 may be implemented as part of the processor 902.

[0148] In some implementations, the UE 900 may include at least one transceiver 908. In some other implementations, the UE 900 may have more than one transceiver 908. The transceiver 908 may represent a wireless transceiver. The transceiver 908 may include one or more receiver chains 910, one or more transmitter chains 912, or a combination thereof.

[0149] A receiver chain 910 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 910 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 910 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 910 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 910 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0150] A transmitter chain 912 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 912 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 912 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 912 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.Docket No. SMM920250140-GR-NP

[0151] Figure 10 illustrates an example of a processor 1000 in accordance with aspects of the present disclosure. The processor 1000 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 1000 may include a controller 1002 configured to perform various operations in accordance with examples as described herein. The processor 1000 may optionally include at least one memory 1004, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 1000 may optionally include one or more arithmetic-logic units (ALUs) 1006. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0152] The processor 1000 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 1000) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).

[0153] The controller 1002 may be configured to manage and coordinate various operations (e.g., signalling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 1000 to cause the processor 1000 to support various operations in accordance with examples as described herein. For example, the controller 1002 may operate as a control unit of the processor 1000, generating control signals that manage the operation of various components of the processor 1000. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.Docket No. SMM920250140-GR-NP

[0154] The controller 1002 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1004 and determine subsequent instruction(s) to be executed to cause the processor 1000 to support various operations in accordance with examples as described herein. The controller 1002 may be configured to track memory address of instructions associated with the memory 1004. The controller 1002 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 1002 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1000 to cause the processor 1000 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 1002 may be configured to manage flow of data within the processor 1000. The controller 1002 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 1000.

[0155] The memory 1004 may include one or more caches (e.g., memory local to or included in the processor 1000 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 1004 may reside within or on a processor chipset (e.g., local to the processor 1000). In some other implementations, the memory 1004 may reside external to the processor chipset (e.g., remote to the processor 1000).

[0156] The memory 1004 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1000, cause the processor 1000 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 1002 and / or the processor 1000 may be configured to execute computer-readable instructions stored in the memory 1004 to cause the processor 1000 to perform various functions. For example, the processor 1000 and / or the controller 1002 may be coupled with or to the memory 1004, the processor 1000, the controller 1002, and the memory 1004 may be configured to perform various functions described herein. In some examples, the processor 1000 may include multiple processors and the memory 1004 may include multiple memories. One or more of the multiple processors may be coupled with one orDocket No. SMM920250140-GR-NPmore of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

[0157] The one or more ALUs 1006 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 1006 may reside within or on a processor chipset (e.g., the processor 1000). In some other implementations, the one or more ALUs 1006 may reside external to the processor chipset (e.g., the processor 1000). One or more ALUs 1006 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 1006 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 1006 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 1006 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), enabling the one or more ALUs 1006 to handle conditional operations, comparisons, and bitwise operations.

[0158] The processor 1000 may support wireless communication in accordance with examples as disclosed herein. The processor 1000 may be configured to support a means for a first network entity to: receive, from a second network entity, a PDU session create request including downlink segment routing information; and send, to the second network entity, a PDU session create response including uplink segment routing information. Alternatively, the processor 1000 may be configured to or operable to support a means for a second network entity to: send, to a first network entity, a PDU session create request including downlink segment routing information; receive, from the first network entity, a PDU session create response including uplink segment routing information.

[0159] The processor 1000 may be configured to or operable to support a means for a first network entity to: receive a request for downlink segment routing information from a second network entity; and send downlink segment routing information to the second network entity. Alternatively, the processor 1000 may be configured to or operable to support a means for a second network entity to: send a request for downlink segmentDocket No. SMM920250140-GR-NProuting information to a first network entity; and receive downlink segment routing information from the first network entity.

[0160] The processor 1000 may be configured to or operable to support a means for a first network entity to: receive a session modification request including uplink segment routing information from a second network entity; send a response message to the second network entity. Alternatively, the processor 1000 may be configured to or operable to support a means for a second network entity to: send a session modification request including uplink segment routing information to a first network entity; and receive a response message from the first network entity.

[0161] Figure 11 illustrates an example of a NE 1100 in accordance with aspects of the present disclosure. The NE 1100 may include a processor 1102, a memory 1104, a controller 1106, and a transceiver 1108. The processor 1102, the memory 1104, the controller 1106, or the transceiver 1108, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0162] The processor 1102, the memory 1104, the controller 1106, or the transceiver 1108, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0163] The processor 1102 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 1102 may be configured to operate the memory 1104. In some other implementations, the memory 1104 may be integrated into the processor 1102. The processor 1102 may be configured to execute computer-readable instructions stored in the memory 1104 to cause the NE 1100 to perform various functions of the present disclosure.Docket No. SMM920250140-GR-NP

[0164] The memory 1104 may include volatile or non-volatile memory. The memory 1104 may store computer-readable, computer-executable code including instructions when executed by the processor 1102 cause the NE 1100 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 1104 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general -purpose or special-purpose computer.

[0165] In some implementations, the processor 1102 and the memory 1104 coupled with the processor 1102 may be configured to cause the NE 1100 to perform one or more of the functions described herein (e.g., executing, by the processor 1102, instructions stored in the memory 1104). For example, the processor 1102 may support wireless communication at the NE 1100 in accordance with examples as disclosed herein.

[0166] The NE 1100 may be configured to support a means for a first network entity to: receive, from a second network entity, a PDU session create request including downlink segment routing information; and send, to the second network entity, a PDU session create response including uplink segment routing information. Alternatively, the NE 1100 may be configured to or operable to support a means for a second network entity to: send, to a first network entity, a PDU session create request including downlink segment routing information; receive, from the first network entity, a PDU session create response including uplink segment routing information.

[0167] The NE 1100 may be configured to or operable to support a means for a first network entity to: receive a request for downlink segment routing information from a second network entity; and send downlink segment routing information to the second network entity. Alternatively, the NE 1100 may be configured to or operable to support a means for a second network entity to: send a request for downlink segment routing information to a first network entity; and receive downlink segment routing information from the first network entity.Docket No. SMM920250140-GR-NP

[0168] The NE 1100 may be configured to or operable to support a means for a first network entity to: receive a session modification request including uplink segment routing information from a second network entity; send a response message to the second network entity. Alternatively, the NE 1100 may be configured to or operable to support a means for a second network entity to: send a session modification request including uplink segment routing information to a first network entity; and receive a response message from the first network entity.

[0169] The controller 1106 may manage input and output signals for the NE 1100. The controller 1106 may also manage peripherals not integrated into the NE 1100. In some implementations, the controller 1106 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 1106 may be implemented as part of the processor 1102.

[0170] In some implementations, the NE 1100 may include at least one transceiver 1108. In some other implementations, the NE 1100 may have more than one transceiver 1108. The transceiver 1108 may represent a wireless transceiver. The transceiver 1108 may include one or more receiver chains 1110, one or more transmitter chains 1112, or a combination thereof.

[0171] A receiver chain 1110 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 1110 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 1110 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 1110 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 1110 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0172] A transmitter chain 1112 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 1112 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured toDocket No. SMM920250140-GR-NPsupport one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 1112 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 1112 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0173] Figure 12 illustrates a flowchart of a method 1200 in accordance with aspects of the present disclosure. The operations of the method 1200 may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0174] At 1202, the method 1200 may include receiving, from a second network entity, a PDU session create request including downlink segment routing information. The operations of 1202 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1202 may be performed by a NE as described with reference to Figure 11.

[0175] At 1204, the method 1200 may include sending, to the second network entity, a PDU session create response including uplink segment routing information. The operations of 1204 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1204 may be performed by a NE as described with reference to Figure 11.

[0176] It should be noted that the method 1200 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0177] Figure 13 illustrates a flowchart of a method 1300 in accordance with aspects of the present disclosure. The operations of the method 1300 may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0178] At 1302, the method 1300 may include sending, to a first network entity, a PDU session create request including downlink segment routing information. The operations ofDocket No. SMM920250140-GR-NP1302 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1302 may be performed by a NE as described with reference to Figure 11.

[0179] At 1304, the method 1300 may include receiving, from the first network entity, a PDU session create response including uplink segment routing information. The operations of 1304 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1304 may be performed by a NE as described with reference to Figure 11.

[0180] It should be noted that the method 1300 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0181] Figure 14 illustrates a flowchart of a method 1400 in accordance with aspects of the present disclosure. The operations of the method 1400 may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0182] At 1402, the method 1400 may include receiving a request for downlink segment routing information from a second network entity. The operations of 1402 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1402 may be performed by a NE as described with reference to Figure 11.

[0183] At 1404, the method 1400 may include sending downlink segment routing information to the second network entity. The operations of 1404 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1404 may be performed by a NE as described with reference to Figure 11.

[0184] It should be noted that the method 1400 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.Docket No. SMM920250140-GR-NP

[0185] Figure 15 illustrates a flowchart of a method 1500 in accordance with aspects of the present disclosure. The operations of the method 1500 may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0186] At 1502, the method 1500 may include sending a request for downlink segment routing information to a first network entity. The operations of 1502 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1502 may be performed by a NE as described with reference to Figure 11.

[0187] At 1504, the method 1500 may include receiving downlink segment routing information from the first network entity. The operations of 1504 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1504 may be performed by a NE as described with reference to Figure 11.

[0188] It should be noted that the method 1500 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0189] Figure 16 illustrates a flowchart of a method 1600 in accordance with aspects of the present disclosure. The operations of the method 1600 may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0190] At 1602, the method 1600 may include: receiving a session modification request including uplink segment routing information from a second network entity. The operations of 1602 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1602 may be performed by a NE as described with reference to Figure 11.

[0191] At 1604, the method 1600 may include: sending a response message to the second network entity. The operations of 1604 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1604 may be performed by a NE as described with reference to Figure 11.Docket No. SMM920250140-GR-NP

[0192] It should be noted that the method 1600 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0193] Figure 17 illustrates a flowchart of a method 1700 in accordance with aspects of the present disclosure. The operations of the method 1700 may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0194] At 1702, the method 1700 may include sending a session modification request including uplink segment routing information to a first network entity. The operations of 1702 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1702 may be performed by a NE as described with reference to Figure 11.

[0195] At 1704, the method 1700 may include receiving a response message from the first network entity. The operations of 1704 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1704 may be performed by a NE as described with reference to Figure 11.

[0196] It should be noted that the method 1700 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0197] A first network entity for wireless communication is described. The first network entity may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the first network entity may include at least one memory, and at least one processor coupled with the at least one memory and configured to cause the first network entity to: receive, from a second network entity, a PDU session create request including downlink segment routing information; and send, to the second network entity, a PDU session create response including uplink segment routing information.

[0198] The first network entity may be a home Session Management Function (SMF). The second network entity may be a visited Session Management Function (SMF).Docket No. SMM920250140-GR-NP

[0199] The downlink segment routing information and / or the uplink segment routing information may comprise SRv6 capability information. The SRv6 capability information may contain information on SRv6 support for the downlink data. The SRv6 capability information may contain information on SRv6 support for the uplink data.

[0200] The downlink segment routing information may comprise at least one of: information on SRv6 support for the downlink data; a Downlink SID list; an IPv6 Locator prefix; and / or a Downlink SID format encoding template. The Downlink SID list may contain the segment identifiers of the downlink data path towards the V-UPF. The IPv6 Locator prefix may contain the IPv6 Locator prefix of the downlink data towards the V- UPF. The Uplink SID list may contain the segment identifiers of the uplink data path towards the H-UPF.

[0201] The at least one processor coupled with the at least one memory may be further configured to cause the first network entity to receive downlink data and send the downlink data towards a UE. The downlink data may be received from a home UPF.

[0202] The uplink segment routing information may comprise at least one of: information on SRv6 support for the uplink data; an Uplink SID list; an IPv6 Locator prefix; and / or an Uplink SID format encoding template. The Uplink SID list may contain the segment identifiers of the uplink data path towards the H-UPF. The IPv6 Locator prefix may contain the IPv6 Locator prefix of the uplink data towards the H-UPF. The Uplink SID format encoding template may contain a SID format encoding template of the uplink data towards the H-UPF.

[0203] The at least one processor coupled with the at least one memory may be further configured to cause the first network entity to receive uplink data and sending the uplink data towards a home UPF (H-UPF).

[0204] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with at least one memory and configured to cause the processor to: receive, from a second network entity, a PDU session create request including downlink segment routing information; send,Docket No. SMM920250140-GR-NPto the second network entity, a PDU session create response including uplink segment routing information.

[0205] A method performed or performable by the first network entity is described herein. The method may comprise: receiving, from a second network entity, a PDU session create request including downlink segment routing information; and sending, to the second network entity, a PDU session create response including uplink segment routing information.

[0206] The first network entity may be a home Session Management Function (SMF). The second network entity may be a visited Session Management Function (SMF).

[0207] The downlink segment routing information and / or the uplink segment routing information may comprise SRv6 capability information. The SRv6 capability information may contain information on SRv6 support for the downlink data. The SRv6 capability information may contain information on SRv6 support for the uplink data.

[0208] The downlink segment routing information may comprise at least one of: information on SRv6 support for the downlink data; a Downlink SID list; an IPv6 Locator prefix; and / or a Downlink SID format encoding template. The Downlink SID list may contain the segment identifiers of the downlink data path towards the V-UPF. The IPv6 Locator prefix may contain the IPv6 Locator prefix of the downlink data towards the V- UPF. The Downlink SID format encoding template may contain a SID format encoding template of the downlink data towards the V-UPF.

[0209] The method may further comprise receiving downlink data and sending the downlink data towards a UE. The downlink data may be received from a home UPF.

[0210] The uplink segment routing information may comprise at least one of: information on SRv6 support for the uplink data; an Uplink SID list; an IPv6 Locator prefix; and / or an Uplink SID format encoding template. The Uplink SID list may contain the segment identifiers of the uplink data path towards the H-UPF. The IPv6 Locator prefix may contain the IPv6 Locator prefix of the uplink data towards the H-UPF. The Uplink SID format encoding template may contain a SID format encoding template of the uplink data towards the H-UPF.Docket No. SMM920250140-GR-NP

[0211] The method may further comprise receiving uplink data and sending the uplink data towards a home UPF (H-UPF).

[0212] A second network entity for wireless communication is described. The second network entity may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the second network entity may include at least one memory, and at least one processor coupled with the at least one memory and configured to cause the second network entity to: send, to a first network entity, a PDU session create request including downlink segment routing information; receive, from the first network entity, a PDU session create response including uplink segment routing information.

[0213] The first network entity may be a home Session Management Function (SMF). The second network entity may be a visited Session Management Function (SMF).

[0214] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with at least one memory and configured to cause the processor to: send, to a first network entity, a PDU session create request including downlink segment routing information; and receive, from the first network entity, a PDU session create response including uplink segment routing information.

[0215] A method performed or performable by the second network entity is described herein. The method may comprise: sending, to a first network entity, a PDU session create request including downlink segment routing information; and receiving, from the first network entity, a PDU session create response including uplink segment routing information.

[0216] The first network entity may be a home Session Management Function (SMF). The second network entity may be a visited Session Management Function (SMF).

[0217] A first network entity for wireless communication is described. The first network entity may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the first network entity may include at leastDocket No. SMM920250140-GR-NPone memory, and at least one processor coupled with the at least one memory and configured to cause the first network entity to: receive a request for downlink segment routing information from a second network entity; and send downlink segment routing information to the second network entity.

[0218] The first network entity may be a visited User Plane Function (UPF). The second network entity may be a visited Session Management Function (SMF).

[0219] The first network entity may be an SMF. The second network entity may be a PCF / edge platform. The SMF may provide the downlink SID list to the PCF / edge platform via a network exposure interface between the SMF / PCF and the edge platform. The edge platform may receive the list and append it to the edge domain SID list, forming a complete end-to-end service chain. The edge platform may use this SID list to apply the SRH to downlink packets before forwarding them towards the core network.

[0220] The downlink segment routing information may comprise SRv6 capability information. The SRv6 capability information may contain information on SRv6 support for the downlink data. Downlink data may be sent towards a visited UPF (V-UPF).

[0221] The SRv6 capability information may contain a Downlink SID list. The Downlink SID list may contain the segment identifiers of the downlink data path towards the V-UPF.

[0222] The SRv6 capability information may contain an IPv6 Locator prefix. The IPv6 Locator prefix may contain the IPv6 Locator prefix of the downlink data towards the V- UPF.

[0223] The SRv6 capability information may contain a Downlink SID format encoding template. The Downlink SID format encoding template may contain a SID format encoding template of the downlink data towards the V-UPF.

[0224] The at least one processor coupled with the at least one memory may be further configured to cause the first network entity to receive downlink data and forwarding said downlink data towards a UE. The downlink data may be received from a home UPF.Docket No. SMM920250140-GR-NP

[0225] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with at least one memory and configured to cause the processor to: receive a request for downlink segment routing information from a second network entity; and send downlink segment routing information to the second network entity

[0226] A method performed or performable by the first network entity is described herein. The method may comprise: receiving a request for downlink segment routing information from a second network entity; and sending downlink segment routing information to the second network entity.

[0227] The first network entity may be a visited User Plane Function (UPF). The second network entity may be a visited Session Management Function (SMF).

[0228] The downlink segment routing information may comprise SRv6 capability information. The SRv6 capability information may contain information on SRv6 support for the downlink data. Downlink data may be sent towards a visited UPF (V-UPF).

[0229] The SRv6 capability information may contain a Downlink SID list. The Downlink SID list may contain the segment identifiers of the uplink data path towards the V-UPF.

[0230] The SRv6 capability information may contain an IPv6 Locator prefix. The IPv6 Locator prefix may contain the IPv6 Locator prefix of the downlink data towards the V- UPF.

[0231] The SRv6 capability information may contain a Downlink SID format encoding template. The Downlink SID format encoding template may contain a SID format encoding template of the uplink data towards the V-UPF.

[0232] The method may further comprise receiving downlink data and forwarding said downlink data towards a UE. The downlink data may be received from a home UPF.

[0233] A second network entity for wireless communication is described. The second network entity may be configured to, capable of, or operable to perform one or moreDocket No. SMM920250140-GR-NPoperations as described herein. For example, the second network entity may include at least one memory, and at least one processor coupled with the at least one memory and configured to cause the second network entity to: send a request for downlink segment routing information to a first network entity; and receive downlink segment routing information from the first network entity.

[0234] The first network entity may be a visited User Plane Function (UPF). The second network entity may be a visited Session Management Function (SMF).

[0235] The downlink segment routing information may comprise SRv6 capability information. The SRv6 capability information may contain information on SRv6 support for the downlink data. Downlink data may be sent towards a visited UPF (V-UPF).

[0236] The SRv6 capability information may contain a Downlink SID list. The Downlink SID list may contain the segment identifiers of the downlink data path towards the V-UPF.

[0237] The SRv6 capability information may contain an IPv6 Locator prefix. The IPv6 Locator prefix may contain the IPv6 Locator prefix of the downlink data towards the V- UPF.

[0238] The SRv6 capability information may contain a Downlink SID format encoding template. The Downlink SID format encoding template may contain a SID format encoding template of the uplink data towards the V-UPF.

[0239] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with at least one memory and configured to cause the processor to: send a request for downlink segment routing information to a first network entity; and receive downlink segment routing information from the first network entity

[0240] A method performed or performable by the second network entity is described herein. The method may comprise: sending a request for downlink segment routingDocket No. SMM920250140-GR-NPinformation to a first network entity; and receiving downlink segment routing information from the first network entity.

[0241] The first network entity may be a visited User Plane Function (UPF). The second network entity may be a visited Session Management Function (SMF).

[0242] The downlink segment routing information may comprise SRv6 capability information. The SRv6 capability information may contain information on SRv6 support for the downlink data. Downlink data may be sent towards a visited UPF (V-UPF).

[0243] The SRv6 capability information may contain a Downlink SID list. The Downlink SID list may contain the segment identifiers of the uplink data path towards the V-UPF.

[0244] The SRv6 capability information may contain an IPv6 Locator prefix. The IPv6 Locator prefix may contain the IPv6 Locator prefix of the downlink data towards the V- UPF.

[0245] The SRv6 capability information may contain a Downlink SID format encoding template. The Downlink SID format encoding template may contain a SID format encoding template of the uplink data towards the V-UPF.

[0246] A first network entity for wireless communication is described. The first network entity may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the first network entity may include at least one memory, and at least one processor coupled with the at least one memory and configured to cause the first network entity to: receive a session modification request including uplink segment routing information from a second network entity; send a response message to the second network entity.

[0247] The first network entity may be a visited User Plane Function (UPF). The second network entity may be a visited Session Management Function (SMF).

[0248] The first network entity may be an SMF. The second network entity may be a PCF / edge platform. Where the second network entity is an edge platform, the edge platform may not be aware of QFI, PSI, or PDU session IDs, and the SMF and / or the PCFDocket No. SMM920250140-GR-NPis responsible for mapping these parameters to the appropriate SID list granularity (per QFI, per PSI, or per PDU session ID). The SMF and / or the PCF may also be responsible for distributing the SID list to the UPF for SRH insertion.

[0249] The segment routing information may comprise SRv6 information. The SRv6 capability information may contain information on SRv6 support for the uplink data.Uplink data may be sent towards a home UPF (H-UPF). The SRv6 capability information may contain an Uplink SID list. The Uplink SID list may contain the segment identifiers of the uplink data path towards the H-UPF. The SRv6 capability information may contain an IPv6 Locator prefix. The IPv6 Locator prefix may contain the IPv6 Locator prefix of the uplink data towards the H-UPF. The SRv6 capability information may contain an Uplink SID format encoding template. The Uplink SID format encoding template may contain a SID format encoding template of the uplink data towards the H-UPF.

[0250] The method may further comprise receiving uplink data from a UE. The method may further comprise forwarding said uplink data towards a home UPF.

[0251] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with at least one memory and configured to cause the processor to: receive a session modification request including uplink segment routing information from a second network entity; and send a response message to the second network entity.

[0252] A method performed or performable by the first network entity is described herein. The method may comprise: receiving a session modification request including uplink segment routing information from a second network entity; and sending a response message to the second network entity.

[0253] A second network entity for wireless communication is described. The second network entity may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the second network entity may include at least one memory, and at least one processor coupled with the at least one memory and configured to cause the second network entity to: send a session modification requestDocket No. SMM920250140-GR-NPincluding uplink segment routing information to a first network entity; and receive a response message from the first network entity.

[0254] The segment routing information may comprise SRv6 information. The SRv6 capability information may contain information on SRv6 support for the uplink data.Uplink data may be sent towards a home UPF (H-UPF). The SRv6 capability information may contain an Uplink SID list. The Uplink SID list may contain the segment identifiers of the uplink data path towards the H-UPF. The SRv6 capability information may contain an IPv6 Locator prefix. The IPv6 Locator prefix may contain the IPv6 Locator prefix of the uplink data towards the H-UPF. The SRv6 capability information may contain an Uplink SID format encoding template. The Uplink SID format encoding template may contain a SID format encoding template of the uplink data towards the H-UPF.

[0255] The method may further comprise receiving downlink segment routing information from a third network entity. The third network entity may be a home PCF.

[0256] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with at least one memory and configured to cause the processor to: send a session modification request including uplink segment routing information to a first network entity; and receive a response message from the first network entity.

[0257] A method performed or performable by a second network entity is described herein. The method may comprise: sending a session modification request including uplink segment routing information to a first network entity; and receiving a response message from the first network entity.

[0258] The arrangements described herein tend to address the problem of service chaining across network domains by enabling Segment Routing over IPv6 (SRv6) to support domain-specific segment identifiers (SIDs) with embedded Session identifier and QoS parameters. It may allow networks to dynamically exchange and interpret SID lists and encoding formats, enabling flexible, per-flow traffic handling and QoS enforcement in multi-domain environments.Docket No. SMM920250140-GR-NP

[0259] The arrangements described herein tend to address the problem by enhancing SRv6-based service chaining across network domains through dynamic exchange of Segment Routing IPv6 (SRv6) SID lists and encoding templates. It enables SMFs and UPFs in different domains to interpret and apply domain-specific SID formats, including embedded QoS parameters like QFI, PSI and PDU Session ID, via extended N16, N16a, N4, N3 and network exposure interfaces. This allows flexible, per-flow service chaining and QoS enforcement in multi-domain environments.

[0260] The arrangements described herein tends to improve upon existing SRv6 solutions by enabling dynamic, domain-specific SID list exchange and QoS-aware service chaining across PLMNs. Unlike existing solutions that focus on a single domain with static SID allocation (e.g. via the management plane), this solution enables SID allocation across domains supporting per-session, per-flow, or per PSI SID customization with embedded QFI / PDU Session ID.

[0261] For example, in the case of Per-Flow SID List Exchange via N16, N16a, N4, N3 and network exposure Interfaces; there may be enabled the dynamic exchange of SRv6 SID lists per QoS flow between SMFs and UPFs across domains. This may allow embedding of QFI, PSI and PDU Session ID into SIDs, enabling differentiated service chaining (e.g., DPI for video, low latency for voice) and precise QoS enforcement.

[0262] By way of further example, in the case of Domain-Specific SID Encoding Templates; there may be introduced SID format templates (e.g., locator: :function:args) that may allow each domain to define how QoS parameters are encoded into SRv6 SIDs. These templates may be exchanged between domains to ensure consistent interpretation and processing of service chains.

[0263] By way of yet further example, in the case of Flexible SID List Construction Options; there may be supported multiple methods for constructing SID lists, either per QoS flow, per PSI or per PDU session, with encoding done at the SMF or UPF. This may allow flexible adaptation to different network architectures and operational preferences, tending to improving scalability and interoperabilityDocket No. SMM920250140-GR-NP

[0264] Accordingly, there may be provided a method for enabling inter-domain service chaining and quality of service (QoS) enforcement in a mobile network using Segment Routing over IPv6 (SRv6).

[0265] The segment identifier (SID) lists may be dynamically exchanged between a H- SMF and a V-SMF via an N16 interface or between a I-SMF and a SMF via an N16a interface. The SID lists may be exchanged between a SMF and a UPF via an N4 interface. PDU session identifiers, QoS parameters and Flags may be embedded into the SIDs using a domain-specific encoding format. Per-session service chains and per-flow service chains may be applied based on the encoded SIDs to enable differentiated traffic handling across network domains. The SID encoding format may comprise a template of the form locator: :function:args. The PDU session identifier and / or QoS parameters and or PSI values and / or Flags may be encoded either directly into the SID or provided as type-lengthvalue (TLV) structures. SID encoding format templates may be dynamically exchanged between an H-SMF and a V-SMF via an N16 interface or between a I-SMF and a SMF via an N16a interface. SID lists may be exchanged between a SMF and a UPF via an N4 interface. SID lists may be exchanged between a SMF and RAN via an N3 interface. SID lists may be exchanged between a SMF, a PCF and an edge pledge platform via network exposure interface.

[0266] There may be further provided a system for inter-domain SRv6 service chaining comprising one or more SMFs and one or more UPFs.

[0267] An SMF may be configured to generate and transmit SID lists and encoding templates. A UPF may be configured to generate and transmit SID lists and encoding templates. A RAN may be configured to generate and transmit SID lists and encoding templates. An edge platform may be configured to generate and transmit SID lists and encoding templates. An SMF may be configured to interpret and extend SID lists with domain-specific service functions. A UPF may be configured to interpret and extend SID lists with domain-specific service functions. A RAN may be configured to interpret and extend SID lists with domain-specific service functions. An edge platform may be configured to interpret and extend SID lists with domain-specific service functions. A UPF may be configured to apply SRv6 headers to data packets based on PDU session identifiers,Docket No. SMM920250140-GR-NPQoS flow identifiers, PSI values, Flags and service chaining requirements. A UPF may be configured to interpret SRv6 headers of data packets based on PDU session identifiers, QoS flow identifiers, PSI values, Flags and service chaining requirements. A RAN may be configured to apply SRv6 headers to data packets based on PDU session identifiers, QoS flow identifiers, PSI values, Flags and service chaining requirements. A RAN may be configured to interpret SRv6 headers of data packets based on PDU session identifiers, QoS flow identifiers, PSI values, Flags and service chaining requirements. An edge platform may be configured to apply SRv6 headers to data packets based on PDU session identifiers, QoS flow identifiers, PSI values, Flags and service chaining requirements. An edge platform may be configured to interpret SRv6 headers of data packets based on PDU session identifiers, QoS flow identifiers, PSI values, Flags and service chaining requirements.

[0268] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0269] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

[0270] The following abbreviations are relevant in the field addressed by this document: 5GC, 5G Core Network; 5GS, 5G System; GTP-U, GPRS Tunnel Protocol User plane; NAS , Non-Access Stratum.; NG, Next Generation; PDU Session ID , Identifier of the PDU Session. The GTP-U equivalent is TEID.; PLMN, Public Land Mobile Network; PDU Session ID, PDU Set Importance; QFI, QoS Flow Identifier; SID, Segment ID; SMF, Session Management Function; vSMF, Visited SMF; hSMF, Home SMF; SRH, Segment Routing Header ; SRv6, Segment Routing over IPv6; TEID, Tunnel Endpoint Identifier; and UPF, User Plane Function.Docket No. SMM920250140-GR-NP

Claims

CLAIMSWhat is claimed is:

1. A first network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first network entity to: receive, from a second network entity, a PDU session create request including downlink segment routing information; send, to the second network entity, a PDU session create response including uplink segment routing information.

2. The first network entity of claim 1, wherein the first network entity is a home Session Management Function (SMF).

3. The first network entity of claim 1 or 2, wherein the second network entity is a visited Session Management Function (SMF).

4. The first network entity of any of claims 1 to 3, wherein the downlink segment routing information and / or the uplink segment routing information comprises SRv6 capability information.

5. The first network entity of any of claims 1 to 4, wherein the downlink segment routing information comprises at least one of: information on SRv6 support for the downlink data; a Downlink SID list; an IPv6 Locator prefix; and / or a Downlink SID format encoding template.Docket No. SMM920250140-GR-NP6. The first network entity of any of claims 1 to 5, wherein the at least one processor coupled with the at least one memory is further configured to cause the first network entity to receive downlink data and send the downlink data towards a user equipment (UE).

7. The first network entity of any of claims 1 to 6, wherein the uplink segment routing information comprises at least one of information on SRv6 support for the uplink data; an Uplink SID list; an IPv6 Locator prefix; and / or an Uplink SID format encoding template.

8. The first network entity of any of claims 1 to 7, wherein the at least one processor coupled with the at least one memory is further configured to cause the first network entity to receive uplink data and sending the uplink data towards a home UPF (H-UPF).

9. A method performed or performable by a first network entity, the method comprising: receiving, from a second network entity, a PDU session create request including downlink segment routing information; sending, to the second network entity, a PDU session create response including uplink segment routing information.

10. The method of claim 9, wherein the first network entity is a home Session Management Function (SMF).

11. The method of claim 9 or 10, wherein the second network entity is a visited Session Management Function (SMF).

12. The method of any of claims 9 to 11, wherein the downlink segment routing information and / or the uplink segment routing information comprises SRv6 capability information.Docket No. SMM920250140-GR-NP13. The method of any of claims 9 to 12, wherein the downlink segment routing information comprises at least one of: information on SRv6 support for the downlink data; a Downlink SID list; an IPv6 Locator prefix; and / or a Downlink SID format encoding template.

14. The method of any of claims 9 to 13, further comprising receiving downlink data and sending the downlink data towards a UE.

15. A second network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the second network entity to: send, to a first network entity, a PDU session create request including downlink segment routing information; receive, from the first network entity, a PDU session create response including uplink segment routing information.

16. The second network entity of claim 15, wherein the first network entity is a home Session Management Function (SMF).

17. The second network entity of claim 15 or 16, wherein the second network entity is a visited Session Management Function (SMF).

18. A method performed or performable by a second network entity, the method comprising: sending, to a first network entity, a PDU session create request including downlink segment routing information;Docket No. SMM920250140-GR-NPreceiving, from the first network entity, a PDU session create response including uplink segment routing information.

19. The method of claim 18, wherein the first network entity is a home Session Management Function (SMF).

20. The method of claim 18 or 19, wherein the second network entity is a visited Session Management Function (SMF).Docket No. SMM920250140-GR-NP

Images