Methods, apparatuses and computer programs

Abstract

The present disclosure relates to a method, an apparatus and a computer program. The present disclosure provides a method performed by a first network entity, the method comprising: generating a first message comprising a first Ethernet header, a second header and data; and transmitting the first message to a second network entity, wherein the second header comprises: information indicating a version of a communication protocol used in the first message; information indicating a length of the second header; one or more optional fields comprising metadata; and information identifying the one or more optional fields.

Description

Technical Field

[0001] Various examples of this disclosure relate to methods, apparatus, systems, and computer programs, and specifically, but not exclusively, to metadata data transmission. Background Technology

[0002] A communication network can be viewed as a facility that enables communication between two or more communication devices, or provides communication devices with access to a data network. Mobile or wireless communication networks are an example of communication networks. Communication devices may be served by application servers.

[0003] Such communication networks operate according to standards provided by, for example, 3GPP (3rd Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). Examples of standards provided by 3GPP are the so-called 3GPP standards for generations of cellular technology, such as the 3GPP standards for 4G technology and the 3GPP standards for 5G technology. Summary of the Invention

[0004] Examples of this disclosure will be described with reference to certain aspects. These aspects are not intended to indicate key or essential features of the various examples of this disclosure, nor are they intended to limit its scope. Other features, aspects, and elements will be apparent to those skilled in the art in light of this disclosure. For example, it should be understood that other aspects may be provided by combination of any two or more aspects described below.

[0005] According to one aspect, a method is provided performed by a first network entity, the method comprising: generating a first message including a first Ethernet header, a second header, and data; and sending the first message to a second network entity, wherein the second header includes: information indicating a version of a communication protocol used in the first message; information indicating the length of the second header; one or more optional fields including metadata; and information identifying the one or more optional fields.

[0006] Metadata may include at least one of the following: business support information; protocol data unit (PDU) configuration information; and business information.

[0007] The tunnel endpoint identifier and / or sequence number may be omitted from the second header.

[0008] Metadata can be included in one or more containers within the first message, each container containing one or more information elements associated with different types of metadata.

[0009] Each container may include information indicating the type of metadata, which is included in the next container in the second header.

[0010] The process may further include: determining a checksum value associated with the first message; determining a frame check sequence based on the determined checksum value; and inserting the determined frame check sequence into the first message.

[0011] The first network entity can be a user equipment, and the second network entity can be an access node.

[0012] The first network entity can be an access node, and the second network entity can be a user equipment.

[0013] The method may further include: receiving a second message from a user equipment, including a second Ethernet header and data; wherein the generation of the first message is based on the received second message.

[0014] The first entity can be a user plane function, and the second network entity can be an access node.

[0015] User plane functions and access nodes can be included in a cluster, which includes user plane functions and multiple access nodes including access nodes, and wherein the cluster is configured to enable Layer 2 (L2) handover between multiple access nodes included in the cluster for the UE.

[0016] The method may further include: receiving a third message from a third network entity, including a third header and data; wherein the generation of the first message is based on the received third message.

[0017] Generating the first message may also include generating the first Ethernet header based on the third header.

[0018] The third network entity can be a protocol data unit session anchor user plane function.

[0019] The first entity can be a Protocol Data Unit Session Anchor User Plane Function, and the second network entity can be a User Plane Function.

[0020] The method may further include: receiving a fourth message including data from a fourth network entity; wherein the generation of the first message is based on the received fourth message.

[0021] According to one aspect, a first network entity is provided, the first network entity comprising: at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the first network entity to perform at least the methods of any of the foregoing aspects.

[0022] According to one aspect, a first network entity is provided, the first network entity comprising: components for generating a first message, the first message including a first Ethernet header, a second header, and data; and components for sending the first message to a second network entity, wherein the second header includes: information indicating a version of a communication protocol used in the first message; information indicating the length of the second header; one or more optional fields including metadata; and information identifying the one or more optional fields.

[0023] Metadata may include at least one of the following: business support information; protocol data unit (PDU) configuration information; and business information.

[0024] The tunnel endpoint identifier and / or sequence number may be omitted from the second header.

[0025] Metadata can be included in one or more containers within the first message, each container containing one or more information elements associated with different types of metadata.

[0026] Each container may include information indicating the type of metadata, which is included in the next container in the second header.

[0027] The processing components may further include: components for determining a checksum value associated with the first message; components for determining a frame check sequence based on the determined checksum value; and components for inserting the determined frame check sequence into the first message.

[0028] The first network entity can be a user equipment, and the second network entity can be an access node.

[0029] The first network entity can be an access node, and the second network entity can be a user plane function.

[0030] The first network entity may further include: a component for receiving a second message from a user equipment, including a second Ethernet header and data; wherein the generation of the first message is based on the received second message.

[0031] The first entity can be a user plane function, and the second network entity can be an access node.

[0032] User plane functions and access nodes can be included in a cluster, which includes user plane functions and multiple access nodes including access nodes, and wherein the cluster is configured to enable Layer 2 (L2) handover between multiple access nodes included in the cluster for the UE.

[0033] The first network entity may further include: a component for receiving a third message, including a third header and data, from the third network entity; wherein the generation of the first message is based on the received third message.

[0034] The component used to generate the first message may also include: a component for generating the first Ethernet header based on the third header.

[0035] The third network entity can be a protocol data unit session anchor user plane function.

[0036] The first entity can be a Protocol Data Unit Session Anchor User Plane Function, and the second network entity can be a User Plane Function.

[0037] The first network entity may further include: a component for receiving a fourth message including data from the fourth network entity; wherein the generation of the first message is based on the received fourth message.

[0038] According to one aspect, a computer-readable medium is provided, the computer-readable medium including instructions that, when executed by a first network entity, cause the first network entity to perform at least the following: generating a first message, the first message including a first Ethernet header, a second header, and data; and sending the first message to a second network entity, wherein the second header includes: information indicating a version of a communication protocol used in the first message; information indicating the length of the second header; one or more optional fields including metadata; and information identifying the one or more optional fields.

[0039] According to one aspect, a non-transitory computer-readable medium is provided, the non-transitory computer-readable medium including program instructions that, when executed by a device, cause the device to perform at least the method according to any of the foregoing aspects.

[0040] Many different aspects have been described above. As previously stated, it should be understood that other aspects can be provided by combining any two or more of the above aspects. Other features, aspects, and elements will become apparent from the following. Attached Figure Description

[0041] Some examples will now be described with reference to the accompanying drawings (Figures), which are only non-limiting and illustrative examples, in which:

[0042] Figure 1 Examples of communication networks in which the examples disclosed herein can be applied are shown;

[0043] Figure 2 This illustrates a representation of a fifth-generation communication system;

[0044] Figure 3An example network deployment is shown, comprising multiple access nodes grouped into one or more clusters;

[0045] Figure 4 An example GTP-U header structure is shown;

[0046] Figure 5 The methods are shown based on some examples;

[0047] Figure 6 and Figure 7 Example protocol stacks for both uplink and downlink directions are shown; and

[0048] Figure 8 The apparatus is shown according to some examples. Detailed Implementation

[0049] Some examples of this disclosure can be implemented in communication networks, such as any of the following radio access technologies (RATs): Global Microwave Interconnection Access (WiMAX), Global System for Mobile Communications (GSM, 2G), GSM EDGE Radio Access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunications System based on Basic Wideband Code Division Multiple Access (W-CDMA) (UMTS, 3G), High-Speed ​​Packet Access (HSPA), Long Term Evolution (LTE), Advanced LTE and Enhanced LTE (eLTE), 5G (also known as NR), or any future RAT, such as 6G. Furthermore, communication within the communication network can utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), and / or Discrete Fourier Transform Spread Spectrum OFDM (DFT-s-OFDM).

[0050] As used herein, the term "network device" or "network node" can refer to a node in a communication network through which user equipment can access the network and / or through which the node can control wireless communication and manage wireless resources within a cell. A network node or network device can be referred to as a base station (BS), access point (AP), or access node. Depending on the technology applied, a network device can be, for example, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Header Terminal (RH), a Remote Radio Header Terminal (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low-power node, a non-terrestrial network (NTN) or non-terrestrial network equipment (such as satellite network equipment, low Earth orbit (LEO) satellites, and geostationary orbit (GEO) satellites), or an aircraft network equipment.

[0051] Furthermore, in the context of split radio access networks (RANs), network equipment can refer to a centralized unit (CU) and / or a distributed unit (DU) of a base station. The interface between the CU and the DU can be referred to as the F1 interface in NR. In a split RAN architecture, node operations can be performed, at least partially, in a central / centralized unit (CU) (e.g., a server, host, or node) operatively coupled to a DU (e.g., a radio head / node). A CU can control one or more DUs to at least act as a transmit / receive (Tx / Rx) node. In some examples, a DU may include, for example, a Radio Link Control (RLC), Media Access Control (MAC) layer, and a Physical (PHY) layer, while a CU may include layers above the RLC layer, such as a Packet Data Convergence Protocol (PDCP) layer, Radio Resource Control (RRC), and Internet Protocol (IP) layer. Other functional splits are also possible. In practice, any processing task can be performed in either a CU or a DU, and the boundary of responsibility transfer between the CU and the DU can depend on the applied implementation.

[0052] The term "terminal device" can refer to any terminal device capable of wireless communication. For example, a terminal device can be referred to as a communication device, user equipment (UE), subscriber station (SS), or mobile station (MS). Terminal devices can include mobile phones, cellular phones, smartphones, VoIP phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, USB dongles, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), automobiles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, and so on.

[0053] As used herein, the term "resource" can refer to radio resources in the time domain, frequency domain, spatial domain, and / or code domain. Some examples of resources include, for example, physical resource blocks (PRBs), radio frames, subframes, time slots, subbands, frequency regions, subcarriers, beams, etc. The terms "transmission" and / or "reception" can refer to wireless transmission and / or reception over radio resources via a radio propagation channel.

[0054] Figure 1 The illustration shows an example of a communication network in which the examples disclosed herein can be applied. The communication network, or cellular communication network, may include a network node 110 providing one or more cells (such as cell 100) and a network node 112 providing one or more other cells (such as cell 102). For example, each cell may be a macrocell, microcell, femtocell, or picocell. A cell may define the coverage area or service area of ​​a corresponding access node.

[0055] Network node 110 can provide radio access to a communication network to user equipment (UE) 120 (one or more UEs). Radio access may include downlink (DL) communication from the network node to UE 120 and uplink (UL) communication from UE 120 to the network node. Examples of uplink channels include the Physical Uplink Control Channel (PUCCH) for transmitting control information and the Physical Uplink Shared Channel (PUSCH) for transmitting data to the network. Examples of downlink channels include the Physical Downlink Control Channel (PDCCH) for transmitting control information and the Physical Downlink Shared Channel (PDSCH) for transmitting data to the user equipment.

[0056] Multiple UEs 120 and 122 can exist in this system. Each UE can be served by the same or different network nodes 110 and 112. UEs can be configured with dual connectivity (DC), where a UE (e.g., UE 120) can connect to multiple network nodes 110 and 112. UEs 120 and 122 can communicate with each other when a device-to-device (D2D) communication interface is established between UEs 120 and 122 via a so-called side link (SL). For example, this D2D communication can be referred to as machine-to-machine, peer-to-peer (P2P) communication, or vehicle-to-vehicle (V2V) communication.

[0057] In a communication network with multiple network nodes, these nodes can connect to each other via interfaces. The LTE specification refers to this interface as the X2 interface. The interface between an LTE node and a 5G node, or between two 5G nodes, can be called the Xn interface. Network nodes 110 and 112 can also connect to the core network 116 of the communication network via another interface.

[0058] The following examples are explained with reference to communication devices capable of communicating with a communication system. Before explaining the various examples of this disclosure in detail, please refer to… Figure 2 Briefly explain the fifth-generation communication system (5GS), its access network and core network (5GC), and communication equipment.

[0059] Figure 2 A schematic diagram of a 5G communication system (5GS) is shown. The 5GS may include a user equipment (UE) or terminal 120, a 5G core network 202 (which may be an example of the core network 116 described earlier), and one or more application functions 203. Application functions 203 may be deployed in the 5GS as trusted application functions, or they may be deployed or hosted on one or more application servers in a data network (DN) 204. Such application functions are untrusted application functions. The 5GS connects the UE to the data network, the access network, and the 5GC 202 (e.g., the 5GC's UPF).

[0060] 5GC may include the following network functions: Network Slice Selection Function (NSSF); Network Exposure Function (NEF) 205; Network Repository Function (NRF); Policy Control Function (PCF); Unified Data Management (UDM) 206; Application Function (AF) 203; Authentication Server Function (AUSF) 207; Access and Mobility Management Function (AMF) 208; Session Management Function (SMF) 209; and User Plane Function (UPF) 210. Figure 2 Various interfaces (N1, N2, etc.) that can be implemented between various components of the system are also shown. It should be understood that... Figure 2Not all of the above network functions are shown in the figure, and in some examples, 5GC may include other network functions in addition to those mentioned above.

[0061] The LTE specification designates the core network as the Evolved Packet Core (EPC), which may include, for example, a Mobility Management Entity (MME) and gateway nodes. The MME handles the mobility of terminal devices within a tracking area comprising multiple cells and manages signaling connections between the terminal devices and the core network. Gateway nodes handle data routing within the core network, as well as data routing to / from terminal devices. The 5G specification designates the core network as the 5G Core (5GC). AMF 208 can handle the termination of Non-Access Stratum (NAS) signaling, NAS encryption and integrity protection, registration management, connection management, mobility management, access authentication and authorization, and security context management. For example, a UPF 210 node can support packet routing and forwarding, packet inspection, and Quality of Service (QoS) processing.

[0062] Some examples in this disclosure relate to UE radio access technology (RAT) restrictions, where a UE may be restricted to using one or more RAT types. Examples of different RAT types include, but are not limited to, 4G, 5G, and 6G.

[0063] Some examples of this disclosure relate to network deployments providing multiple access nodes in a small geographical area. At least some of the multiple access nodes can provide cells with relatively small and partially overlapping coverage areas. Therefore, handovers of UEs moving within the geographical coverage area of ​​cells provided by multiple access nodes may be relatively frequent. Figure 3 An example of such a network deployment is shown in the figure.

[0064] like Figure 3 As shown, in some examples, multiple access nodes (gNBs) can be grouped into logical clusters 300a, 300b, and 300c. Each cluster may include multiple access nodes and user plane functions, which may be referred to as a cluster UPF. For example, cluster 300a may include access nodes 302a, 302b, and 302c and cluster UPF 304. Each cluster UPF can communicate with a Protocol Data Unit (PDU) Session Anchor (PSA) UPF 306, which provides access to the core network for the cluster UPF. The cluster UPF can be a standalone UPF or provided as part of the central unit of an access node (e.g., gNB-CU). In some examples, the cluster UPF may be a PSA UPF, or the PSA UPF may be a separate logical entity of the cluster UPF. The network may also include one or more additional access nodes 308 not included in the cluster. Although Figure 3The access node is shown as gNB, but it should be understood that different types of access nodes may be used in some examples.

[0065] Within each cluster, handover of UEs between access nodes included in the cluster can be enabled based on Layer 2 (L2) messaging (e.g., messaging indicating the UE's L2 address). In this case, explicit RRC or N2 signaling (between the access node and the core network) may not be required for UE mobility within the cluster. Instead, messaging is based on L2 (e.g., MAC) address information. This enables more efficient UE handover, which can be particularly beneficial because handover operations are performed relatively frequently due to the size and overlapping coverage of access nodes included in the cluster. When a UE moves from the coverage area of ​​an access node included in the cluster to the coverage area of ​​an access node not included in the cluster, UE handover can be performed based on L3 messaging (e.g., messaging indicating the UE's L3 address).

[0066] According to existing signaling mechanisms, General Packet Radio Service (GPRS) Tunneling Protocol (GTP) User Plane (GTP-U) tunnels are established between tunnel endpoints for transmitting user plane data between endpoints. Endpoints can be identified by a Tunnel Endpoint Identifier (TEID), which is included in the GTP-U header encapsulated in messages transmitted between network entities.

[0067] According to 3GPP TS 29.281, the GTP-U header may include fields that are always present in the GTP-U header, as well as fields that may be optionally included in the GTP-U header. Fields that are always present in the GTP-U header encapsulated in the message include: (a) Version field, which includes information indicating the version of the GTP protocol used in the header; (b) Protocol Type (PT) field, which includes information indicating the protocol type used in the header (e.g., GTP or GTP'); (c) Extended (E) header flags, which include information indicating whether the next header extension field is included in the header; (d) Sequence (S) number flag, which includes information indicating whether the sequence number field is included in the header; (e) PDU number (PN) flag, which includes information indicating whether the PDU number field is included in the header; (f) Message type field, which includes information indicating the message type; (g) A length field, which includes information indicating the length of the message; and (h) One or more TEIDs associated with the message (e.g., TEIDs associated with a tunnel endpoint in the receiving GTP-U entity).

[0068] In some examples, the optional fields included in the GTP-U header include at least one of the following: (a) One or more sequence numbers associated with the message (e.g., data included in the message may be associated with a sequence of PDUs, and the sequence number may indicate the sequence of PDUs to ensure that the transmission order of the data is preserved). (b) The Protocol Data Unit Number (N-PDU) of the data included in the message; or (c) The next extended header that indicates the type of the extended header following the next extended header in the GTP-U header.

[0069] Figure 4 The example GTP-U header that includes the fields mentioned above is shown in the image.

[0070] As mentioned above, in some example deployments, such as Figure 3 As shown, L2 messaging can be enabled for UEs within the cluster. L2 messages can be interchangeably referred to as Ethernet messages or Ethernet frames.

[0071] Ethernet messages can include an Ethernet message header, data, and a Frame Check Sequence (FCS). The Ethernet message header includes: (a) Destination address and source address, which can be an L2 address, such as a MAC address; (b) Information indicating the type of Ethernet message (e.g., the EtherType field), information indicating the content carried within the Ethernet message (e.g., IPv4 packets, IPv6 packets, or other content); or information indicating the length of the Ethernet message.

[0072] The FCS (Framework Counter) can be located at the end of an Ethernet message and allows for the detection of corrupted data within the Ethernet message at the receiver. The FCS value is calculated based on other fields included in the Ethernet message (i.e., the Ethernet header and data, and any optional padding fields) and compared to the FCS value included in the received Ethernet message. If the calculated FCS value matches the FCS value included in the Ethernet message, the Ethernet message is verified; if the values ​​differ, the Ethernet message can be considered corrupted.

[0073] When L2 handover is enabled for the UE (i.e., the UE is enabled to use Ethernet / L2 messages, as mentioned earlier), Figure 3When operating within the cluster described, GTP-U information may not be needed for routing messages because there is no need to establish a GTP-U tunnel for UE message passing and handover. This enables faster handover of user plane data.

[0074] However, the GTP-U header can include information (metadata, such as Quality of Service Flow Identifier, Protocol Data Unit Set Information, etc.) used by other network entities (such as access nodes and cluster UPF / PSA UPF), and therefore omitting the GTP-U header may result in information loss.

[0075] Therefore, carrying metadata on the user plane protocol stack is a challenge when L2 switching is enabled for packet forwarding. The example disclosed herein addresses this issue.

[0076] refer to Figure 5 It illustrates methods based on some examples. This will be described in more detail below. Figure 5 The method can be performed by a first network entity, which can be a UE, an access node (e.g., a gNB), or a UPF.

[0077] At 500, the method includes generating a first message, which includes a first Ethernet header, a second header, and data. The second header includes: information indicating the version of the communication protocol used in the first message; information indicating the length of the second header; one or more optional fields including metadata; and information identifying the one or more optional fields.

[0078] At 502, the method includes sending a first message to a second network entity.

[0079] The first message may include an Ethernet / L2 message. As previously mentioned, the first Ethernet header may include a destination address and a source address, as well as information indicating the type or length of the Ethernet message. The data may be user plane data to be transmitted between network entities.

[0080] In some examples, the second header may include a GTP-U header. The GTP-U header may be as described above. That is, the GTP-U header may include the previously described fields that are always present in the GTP-U header, and in some examples, may also include one or more optional fields from the previously described optional fields.

[0081] In some examples, the first Ethernet header may indicate that GTP-U is included in the first message. For example, the first Ethernet header may include information indicating that the GTP-U header is included in the first message. For example, the EtherType field in the first Ethernet header may be set to a value to indicate that the GTP-U header is included in the first message.

[0082] In some examples, the second header may include a simplified GTP-U header. A simplified GTP-U header can be understood as a GTP-U header with TEID omitted. Optionally, SQN may also be omitted from the simplified GTP-U header. Therefore, the simplified GTP-U header may include: (a) Version field, which includes information indicating the version of the GTP protocol used in the header; (b) Protocol type field, which includes information indicating the protocol type used in the header (e.g., GTP or GTP'); (c) Extended header flags, which include information indicating whether the next header extension field is included in the header; (d) PDU number flag, which includes information indicating whether the PDU number field is included in the header; (e) A message type field, which includes information indicating the message type; and (f) Length field, which includes information indicating the length of the message.

[0083] In some examples, the first Ethernet header may indicate that a simplified GTP-U header is included in the first message. For example, the first Ethernet header may include information indicating that simplified GTP-U is included in the first message. For example, the EtherType field in the first Ethernet header may be set to a value to indicate that a simplified GTP-U header is included in the first message.

[0084] In some examples, the GTP-U header and the simplified GTP-U header may also include metadata associated with the first network entity. When the first message is generated, the first network entity may include metadata associated with the first network entity in the second header. The metadata may include, for example, at least one of the following: (a) Business support information, which can be used to assist in the management of business flows and improve network performance; (b) PDU set information, for example, for providing application awareness for XRM services; (c) Business statistics.

[0085] In some examples, the second header may include an additional header—that is, a header that is not the GTP-U header or a simplified GTP-U header as described above. For example, the additional header could be a different header type, or a completely new header constructed to carry metadata in an Ethernet message. By leveraging the purpose of constructing the header, some examples enable further optimization of the size and structure of the second header.

[0086] Other headers may include: (a) Information indicating the version of the communication protocol used in the first message; (b) Information indicating the length of the second header; (c) One or more optional fields, which include metadata; (d) Information identifying one or more optional fields.

[0087] Metadata included in the additional header can be metadata associated with the first network entity previously described. Similar to the simplified GTP-U header, TEID and / or SQN can be omitted from the additional header.

[0088] In some examples, the additional header may consist of the following items previously described: information indicating the version of the communication protocol used in the first message; information indicating the length of the second header; one or more optional fields including metadata; and information identifying the one or more optional fields.

[0089] In some examples, the first Ethernet header may indicate that additional headers are included in the first message. For example, the first Ethernet header may include information indicating that additional headers are included in the first message. For example, the EtherType field in the first Ethernet header may be set to a value indicating that additional headers are included in the first message.

[0090] In some examples, the additional header may have a variable size. The size of the additional header may depend on the metadata included in the additional header. In some examples, the additional header may include information indicating the size of the additional header. This can enable message reception to determine where data begins within the first message, addressing the variable size of the additional header.

[0091] In some examples, additional headers may include one or more containers. Each container may include one or more information elements associated with different types of metadata. Different types of metadata may include, but are not limited to, PDU sets, flow control, QoS monitoring, sequence numbers, etc. For example, additional headers may include: a first container containing information associated with PDU sets, a second container containing information associated with flow control, a third container containing information associated with QoS monitoring, etc.

[0092] Each container may include a field (e.g., a next container field) that includes information indicating the type and / or length of the next field. Returning to the example above, the first container may include information indicating that the next field includes information associated with flow control, the second container may include information indicating that the next container includes information associated with QoS flows, and so on.

[0093] In some examples, the size of each container can be variable, depending on the amount of metadata to be sent. This can be beneficial because the header size can be flexibly adapted to the data size, but determining the container size and retrieving the data accordingly at the receiver can be more processing-intensive. In other examples, the size of each container can be fixed. This can be less processing-intensive at the receiver, but may lead to increased overhead due to the need to send redundant information fields when no metadata for redundant information fields is sent.

[0094] In some examples, the first network entity can determine a checksum value associated with the first message. The first network entity can then determine an FCS value based on the checksum value. The first network entity can then insert the determined FCS value into the first message within the FCS.

[0095] As previously mentioned, in some examples, the first network entity can be a UE, and the second network entity can be an access node, such as a gNB. For uplink data sent by the UE to the network, the UE can perform the method described above and send a first Ethernet message to the access node.

[0096] In other examples, the first network entity may be an access node, and the second network entity may be a UPF. The access node, as the first network entity, can receive a second message from the UE. The second message may include a second Ethernet header and data. The access node can generate a first message based on the received second message. For example, the access node can insert a second header into the received second message to generate the first message.

[0097] When the first message is generated, the access node may process or otherwise modify the second Ethernet header to generate the first Ethernet header. For example, the first message generated by the access node may include a GTP-U header. As previously described, the first Ethernet header may include information indicating that the first message includes a GTP-U header; however, the second Ethernet header received from the UE may not include such an indication. Therefore, the access node may process or otherwise modify the second Ethernet header to generate a first Ethernet header indicating that the GTP-U header is included in the first message.

[0098] For example, a second Ethernet message sent from the UE to the access node may include EtherType=2048, which indicates that the Ethernet type is IPv4. The access node can modify the EtherType field to set a value that indicates that GTP-U is included in the first message.

[0099] In another example, the access node may receive Ethernet frames from a UPF (e.g., a clustered UPF) that include an EtherType field indicating the Ethernet type. The access node can generate a first message by changing the EtherType header field to a value indicating the IP header and IP payload of the Ethernet frame.

[0100] Therefore, in some examples, the Ethernet header of the message received by the access node from the UE (i.e., the second Ethernet header) can be modified to create the Ethernet header of the message sent by the access node to the UPF. Consequently, the FCS value included in the message sent by the access node to the UPF may need to be updated to ensure that verification does not fail, as the original FCS included in the message received from the UE will no longer be correct. Therefore, the access node can determine the FCS value and insert the determined FCS value into the first message, as described above.

[0101] In some examples, if the UE supports a second header (e.g., the GTP-U / Simplified GTP-U / Additional headers described earlier), the UE may have already set an indication of the second header type in the first Ethernet header, for example, upon entering the trunk. In this case, the access node may not need to modify the second Ethernet header included in the second message received from the UE. Instead, the access node can generate the first message by inserting the second header into the second message.

[0102] Figure 6 and Figure 7 Example protocol stacks for uplink and downlink directions are shown. Figure 6 In the example, the access node and cluster UPF can execute the methods described previously, while Figure 7In the example, the UE, access node, and cluster UPF can execute the method described previously.

[0103] exist Figure 6 and Figure 7 In this context, "2nd Hdr" refers to the "second header," and "Eth" refers to the "Ethernet layer / header." Based on... Figure 6 and Figure 7 The second header may be included in a message (e.g., a first message) between the gNB and the cluster UPF, and / or between the UE and the gNB (e.g., encapsulated on an L2 / Ethernet header). Alternatively, the second header may carry data that is part of a message (e.g., a first message) between the gNB and the cluster UPF, and / or between the UE and the gNB.

[0104] For example, in Figure 6 In the uplink direction, the access node (gNB) can receive the second message from the UE and insert the second header into the message before sending the first message to the cluster UPF. Figure 7 In the example, in the uplink direction, the UE can... Figure 6 The example is used to send a second message to the access node, or the UE can generate a first message itself and send it to the access node.

[0105] In some examples, the first network entity can be a UPF. The UPF can be a PSA UPF, and the second entity can be a clustered UPF. Alternatively, the UPF can be a clustered UPF, and the second entity can be an access node. For downlink data sent to the UE, the UPF (clustered UPF or PSA UPF) can perform the above method and send a first Ethernet message to the access node or clustered UPF.

[0106] When the first network entity is a clustered UPF, the clustered UPF can receive a third message from the PSA UPF. The third message may include a third header and data. The third header may, for example, include an N9 GTP-U header (i.e., a GTP-U header suitable for messages sent between UPFs via the N9 interface, for example, having a TEID corresponding to the UPF's address). The clustered UPF can generate a first message based on the received third message. For example, the clustered UPF can replace the third header with a second header and generate an Ethernet / L2 header as described above. This is in... Figure 6 and Figure 7 The diagram shows an example protocol stack where, for the downlink direction, the cluster UPF can receive a third message from the PSA UPF (via the N9 interface) and inserts an Ethernet header and a second header into the message before sending the first message to the access node.

[0107] When the first network entity is a PSA UPF, the PSA UPF can receive a fourth message from other network entities. The fourth message may include data. The PSA UPF can generate a first message based on the fourth message and send the first message to the cluster UPF.

[0108] An example of generating an Ethernet message including an Ethernet header and a second header has been described. The second header can be a GTP-U header or a simplified GTP-U header, and can include various different types of metadata, as described above. The Ethernet header can be adapted to indicate the type of metadata included in the second header. Therefore, when L2 handover is enabled for the UE, the second header enables metadata to be sent.

[0109] In some examples, a first network entity is provided, comprising: components for generating a first message including a first Ethernet header, a second header, and data; and components for sending the first message to a second network entity, wherein the second header includes: a General Packet Radio Services Tunneling Protocol User Plane (GTP-U) header; or a simplified GTP-U header.

[0110] In some examples, a first network entity is provided, the first network entity including at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the first network entity to at least: generate a first message, the first message including a first Ethernet header, a second header and data; and send the first message to a second network entity, wherein the second header includes: a General Packet Radio Services Tunneling Protocol User Plane (GTP-U) header; or a simplified GTP-U header.

[0111] In some examples, the first network entity can be a UE, and the second network entity can be an access node. In some examples, the first network entity can be an access node, and the second network entity can be a UPF.

[0112] In some examples, the first network entity may be a UPF (or an apparatus for a UPF, such as an apparatus including components for providing a UPF configured to perform the methods described herein), and the second network entity may be an access node. For example, the first network entity may be a server or other apparatus including components for providing a UPF configured to perform the previously described methods. As another example, the first network entity may be a server or other apparatus including at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the first network entity to perform at least the methods described above.

[0113] While examples such as “an,” “one,” or “some” may be mentioned in this disclosure, this does not necessarily mean that the same example is mentioned each time, nor does it necessarily mean that a particular feature applies only to a single example. Individual features from different examples may also be combined to provide other examples. Furthermore, when a particular feature, structure, or property is described in conjunction with examples, those skilled in the art can apply those features, structures, or properties in conjunction with other examples, whether or not explicitly described. It should be understood that although the terms “first,” “second,” etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another.

[0114] It should be understood that the references to various network functions (e.g., AMF, SMF, etc.) in the foregoing can be implemented by means of at least some of the functions associated with these network functions. Furthermore, means configured to implement network functions can also be configured as virtual network function instances that implement the network function.

[0115] It should be understood that these devices may include or be coupled to other units or modules, such as radio components or radio heads for transmission and / or reception. Although these devices are described as a single entity, different modules and memories may be implemented in one or more physical or logical entities.

[0116] Note that while some examples have been described for 5G networks, similar examples can be applied to other networks and communication systems. Therefore, although some example architectures of wireless networks, technologies, and standards have been described above by way of example, other examples can be applied to any other suitable form of communication system besides those shown and described herein.

[0117] It is also noted in this document that various changes and modifications may be made to the various examples described herein without departing from the scope of this disclosure.

[0118] As used herein, the phrases “at least one of A or B,” “at least one of A and B,” and “A and / or B” refer to (A), (B), or (A and B). For the purposes of this disclosure, the phrase “A, B, and / or C” refers to (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).

[0119] As used herein, the term “or” means non-exclusive “or” unless otherwise stated (e.g., “otherwise” or “or in alternatives”).

[0120] As used herein, unless explicitly stated otherwise, “perform a step in response to A” does not indicate that the step is performed immediately after “A” occurs, but may include one or more intermediate steps. Similarly, “perform a step or function based on A” does not indicate that the step or function is performed solely based on “A”, as one or more additional conditions may be included.

[0121] Figure 8 A block diagram of apparatus 10 is shown by way of example. For example, apparatus 10 includes at least one processor 12 and at least one memory 14 storing instructions 15 that, when executed by the at least one processor, cause apparatus 10 to perform at least one or more methods disclosed herein. In one example, at least one memory and instructions (e.g., computer program code, software) are configured, together with at least one processor, to cause apparatus 10 to perform one or more methods disclosed herein.

[0122] Processor 12 may include, or be constructed as, one or more circuit systems configured to perform various stages of the methods described herein. As used herein, the term “circuit system” may refer to one or more or all of the following: (a) a hardware circuit implementation only (such as an implementation only in analog and / or digital circuit systems); and (b) a combination of hardware circuitry and software, such as (if applicable): (i) a combination of (multiple) analog and / or digital hardware circuitry having software / firmware; and (ii) any portion of (multiple) hardware processors having software (including (multiple) digital signal processors, software, and (multiple) memories that work together to enable a device (such as a user equipment) to perform various functions); and (c) (multiple) hardware circuitry and / or (multiple) processors, such as (multiple) microprocessors or portions thereof, which require software (e.g., firmware) to operate, but may be absent when operation is not required. This definition of circuit system applies to all uses of the term herein (including in any claim). As another example, as used herein, the term "circuit system" also encompasses only the implementation of hardware circuitry or a processor (or multiple processors) or portions thereof, and their accompanying software and / or firmware. For example, and if applicable to specific claim elements, the term "circuit system" also encompasses baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0123] The memory 14 can be implemented using any suitable data storage technology. The memory may include a database for storing data. The memory 14 may be at least partially located outside the device 10, but may be accessible by the device 10.

[0124] Instruction 15 may be included in a computer-readable medium or a non-transitory computer-readable medium. As used herein, the term “non-transitory” refers to a limitation on the medium itself (i.e., tangible, not tactile) rather than a limitation on the persistence of data storage (e.g., random access memory (RAM) versus read-only memory (ROM).

[0125] For example, device 10 can be a terminal device, such as the UE described above. As another example, the device can be included in such a terminal device, for example, as a chipset configured to control the terminal device. Device 10 can be made or configured to perform at least one or more of the methods described in the examples.

[0126] As another example, device 10 can be a network node, such as the access node or UPF described above. In another example, the device can be included in such a network node, for example, as a chipset configured to control the network node. Device 10 can be caused or configured to perform at least the methods of any one or more of the described examples.

[0127] The apparatus may include one or more entities from any protocol layer, such as a MAC entity, RRC entity, RLC entity, PDCP entity, or PHY entity. In some examples, the entity may be configured to perform at least one or more methods from the examples described.

[0128] Device 10 may include a wireless interface 16. Wireless interface 16 may provide communication capabilities to device 10. Wireless interface 16 may include a receiver configured to receive information according to at least one cellular or non-cellular standard. Wireless interface 16 may include a transmitter configured to transmit information according to at least one cellular or non-cellular standard. Receivers may include more than one receiver. Transmitters may include more than one transmitter. Wireless interface 16 may include a transceiver configured to receive and transmit information according to at least one cellular or non-cellular standard. Transceivers may include more than one transceiver.

[0129] Device 10 may include a user interface 18, which includes at least one of, for example, a keypad, microphone, touch display, monitor, speaker, etc. User interface 18 can be used to control the device by a user. User interface 18 may be external to device 10. For example, device 10 may be connected to another device, such as a computer, via a wireless or wired connection, and device 10 may be controlled by a user via the computer.

[0130] In some examples, at least some of the processes described herein may be performed by means including components for performing at least some of the processes. Components for performing the method steps disclosed herein may include software and / or hardware components of means 10. For example, at least one processor 12, memory 14, and computer program code form components for performing one or more methods disclosed herein, and any embodiments thereof. As used herein, the term “component” shall be interpreted in the singular, i.e., meaning a single element; or in the plural, i.e., meaning a combination of single elements. Thus, the term “component for [performing A, B, C]” shall be interpreted to encompass means in which only one component is used to perform A, B, and C, or in which there are components individually used to perform A, B, and C, or in which there are partially or completely overlapping components for performing A, B, and C. Furthermore, the terms “components for performing A, components for performing B, and components for performing C” should be interpreted as encompassing components in which only one means is used to perform A, B, and C, or components in which there are separate components for performing A, B, and C, or components in which there are partially or completely overlapping components for performing A, B, and C.

[0131] The independent claims define the scope of protection sought by the various examples of this disclosure. Examples and features described in this disclosure that are not within the scope of the independent claims, and if any, shall be interpreted as examples that help to understand the various examples of this disclosure.

[0132] Although examples of the invention have been described above with reference to the accompanying drawings, it will be apparent that these examples are not limited thereto, but can be modified in various ways within the scope of the appended claims. Therefore, all words and expressions should be interpreted broadly, and are intended to illustrate rather than limit the examples. It will be apparent to those skilled in the art that the inventive concept can be implemented in various ways as technology advances. Furthermore, it will be understood by those skilled in the art that the described examples can, but need not, be combined with other examples in various ways.

Claims

1. A method performed by a first network entity, the method comprising: Generate a first message, the first message including a first Ethernet header, a second header, and data; as well as The first message is sent to the second network entity, wherein the second header includes: Information indicating the version of the communication protocol used in the first message; Information indicating the length of the second header; One or more optional fields, including metadata; and Information that identifies one or more of the optional fields.

2. The method of claim 1, wherein the metadata comprises at least one of the following: Business support information; Protocol Data Unit (PDU) configuration information; and Business information.

3. The method of claim 1, wherein the tunnel endpoint identifier and / or sequence number are omitted from the second header.

4. The method of claim 1, wherein the metadata is included in one or more containers within the first message, each container including one or more information elements associated with different types of the metadata.

5. The method of claim 4, wherein each container comprises: Information indicating the type of metadata, wherein the type of metadata is included in the next container in the second header.

6. The method of claim 1, wherein the processing further comprises: Determine the checksum value associated with the first message; The frame check sequence is determined based on the determined checksum value. as well as The determined frame verification sequence is inserted into the first message.

7. The method according to claim 1, wherein the first network entity is a user equipment and the second network entity is an access node.

8. The method according to claim 1, wherein the first network entity is an access node and the second network entity is a user plane function.

9. The method according to claim 8, further comprising: Receive a second message from the user equipment, including a second Ethernet header and the data; The first message is generated based on the received second message.

10. The method of claim 1, wherein the first entity is a user plane function and the second network entity is an access node.

11. The method of claim 10, wherein the user plane function and the access node are included in a cluster, the cluster including the user plane function and a plurality of access nodes including the access node, and wherein the cluster is configured to enable the UE to perform Layer 2 (L2) handover among the plurality of access nodes included in the cluster.

12. The method of claim 10, further comprising: Receive a third message, including a third header and data, from a third network entity; The first message is generated based on the received third message.

13. The method of claim 12, wherein generating the first message further comprises generating the first Ethernet header based on the third header.

14. The method of claim 12, wherein the third network entity is a Protocol Data Unit Session Anchor User Plane Function.

15. The method of claim 10, wherein the first entity is a Protocol Data Unit Session Anchor User Plane Function, and the second network entity is a User Plane Function.

16. The method of claim 15, further comprising: Receive a fourth message including the data from the fourth network entity; The first message is generated based on the received fourth message.

17. A first network entity comprising at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the first network entity to perform at least the method according to any of the preceding claims.

Images