Patent Description:
The following abbreviations are herewith defined, at least some of which are referred to within the following description: Third Generation Partnership Project ("3GPP"), Five Generation System ("5GS"), Positive-Acknowledgment ("ACK"), Access and Mobility Management Function ("AMF"), Access Network ("AN"), Application Function ("AF"), Access Point ("AP"), Application Programming Interface ("API"), Access Point Name ("APN"), Aggregate MBR ("AMBR"), Automatic Repeat Request ("ARQ"), Application Server ("AS"), Base Station ("BS"), Bandwidth Part ("BWP"), Connection Management ("CM"), Core Network ("CN"), Communication Pattern ("CP"), Control Plane/User Plane ("CP/UP"), Cyclic Redundancy Check ("CRC"), Circuit Switched ("CS"), Downlink Control Information ("DCI"), Discontinuous Reception ("DRX"), Downlink ("DL"), Data Network Access Identifier ("DNAI"), Data Network ("DN"), Data Network Name ("DNN"), Domain Name System ("DNS"), Data Radio Bearer ("DRB"), Exchanged Data Rates for GSM Evolution ("EDGE"), Enhanced Discontinuous Reception ("eDRX"), Enhanced Mobile Broadband ("eMBB"), Evolved Node B ("eNB"), Evolved Packet System ("EPS"), Ethernet for Control Automation Technology ("EtherCAT"), Frame Check Sequence ("FCS"), <NUM> Node B ("gNB"), Home Public Land Mobile Network ("HPLMN"), Home Subscriber Server ("HSS"), Identity or Identifier or Identification ("ID"), IP Multimedia Subsystem ("IMS"), International Mobile Subscriber Identity ("IMSI"), Intemet-of-Things ("IoT"), Internet Protocol ("IP"), Listen Before Talk ("LBT"), Long Term Evolution ("LTE"), Multiple Access ("MA"), Medium Access Control ("MAC"), Maximum Bit Rate ("MBR"), Modulation Coding Scheme ("MCS"), Mobile Country Code ("MCC"), Mobility Management ("MM"), Mobility Management Entity ("MME"), Mobile Network Code ("MNC"), Mobile Network Operator ("MNO"), Machine Type Communication ("MTC"), Master Information Block ("MIB"), Mobile Initiated Connection Only ("MICO"), Mobility Management ("MM"), Mobile Switching Center ("MSC"), Mobile Station International Subscriber Directory Number ("MSISDN"), Multiplexer ("MUX"), Control Plane Interface Between an AN and a 5GS ("N2 Interface"), Non-3GPP Interworking Functions ("N3IWF"), Non-Access Stratum ("NAS"), Narrowband ("NB"), North Bound Interface ("NBI"), Network Parameter Configuration ("NC"), Negative-Acknowledgment ("NACK") or ("NAK"), Network Exposure Function ("NEF"), Next Generation ("NG"), New Radio ("NR"), Next Generation Node B ("gNB"), Operating System ("OS"), Policy Control Function ("PCF"), Physical Downlink Control Channel ("PDCCH"), Packet Data Convergence Protocol ("PDCP"), Protocol Data Unit ("PDU"), PDN Gateway ("PGW"), Physical Layer ("PHY"), Public Land Mobile Network ("PLMN"), Packet Switched ("PS"), Physical Random Access Channel ("PRACH"), Physical Resource Block ("PRB"), Physical Uplink Shared Channel ("PUSCH"), Quality of Service ("QoS"), QoS Flow Identifiers ("QFIs"), Radio Access Network ("RAN"), Radio Access Technology ("RAT"), Radio Link Control ("RLC"), Radio Network Temporary Identity ("RNTI"), Radio Resource Control ("RRC"), Receive ("RX"), Service Access Point ("SAP"), Single Carrier Frequency Division Multiple Access ("SC-FDMA"), Service Capability Exposure Function ("SCEF"), Sidelink Control Information ("SCI"), Subcarrier Spacing ("SCS"), Service Data Application Protocol ("SDAP"), Serving GPRS Support Node ("SGSN"), Sidelink ("SL"), Service Level Agreement ("SLA"), Subscriber Management ("SM"), Subscriber Management Function ("SMF"), Single Network Slice Selection Assistance Information ("S-NSSAI"), Subscriber Identity Module ("SIM"), System Information Block ("SIB"), Short Message Service ("SMS"), Signaling Radio Bearers ("SRBs"), Single Radio Voice Call Continuity ("SRVCC"), Session and Service Continuity ("SSC"), Subscription Concealed Identifier ("SUCI"), Subscription Permanent Identifier ("SUPI"), Transmit ("TX"), Unified Data Management ("UDM"), User Datagram Protocol ("UDP"), User Data Repository ("UDR"), User Entity/Equipment (Mobile Terminal) ("UE"), Universal Integrated Circuit Card ("UICC"), Uplink ("UL"), Universal Mobile Telecommunications System ("UMTS"), User Plane ("UP"), User Plane Function ("UPF"), Universal Terrestrial Radio Access ("UTRA"), Universal Terrestrial Radio Access Network ("UTRAN"), Universal Unique Identifier ("UUID"), Visited Public Land Mobile Network ("VPLMN"), WiFi Local Area Network ("WLAN").

In certain wireless communications networks, EtherCAT may be used for communicating information.

<CIT> discusses data transmission in a communication network that is performed via a transmission path with which a master participant and at least one slave participant communicate.

Claim <NUM> defines a method. Claim <NUM> defines an apparatus.

Methods for extracting EtherCAT datagrams from an EtherCAT frame are disclosed. Apparatuses and systems also perform the functions of the apparatus. In one embodiment, the method includes receiving an Ethernet for control automation technology frame. In various embodiments, the method includes determining a first Ethernet for control automation technology datagram in the Ethernet for control automation technology frame for a first device and a second Ethernet for control automation technology datagram in the Ethernet for control automation technology frame for a second device. In certain embodiments, the method includes extracting the first Ethernet for control automation technology datagram from the Ethernet for control automation technology frame to result in an extracted first Ethernet for control automation technology datagram and the second Ethernet for control automation technology datagram from the Ethernet for control automation technology frame to result in an extracted second Ethernet for control automation technology datagram. In some embodiments, the method includes transmitting the extracted first Ethernet for control automation technology datagram directly to the first device. In various embodiments, the method includes transmitting the extracted second Ethernet for control automation technology datagram directly to the second device.

An apparatus for extracting EtherCAT datagrams from an EtherCAT frame, in one embodiment, includes a receiver that receives an Ethernet for control automation technology frame. In various embodiments, the apparatus includes a processor that: determines a first Ethernet for control automation technology datagram in the Ethernet for control automation technology frame for a first device and a second Ethernet for control automation technology datagram in the Ethernet for control automation technology frame for a second device; and extracts the first Ethernet for control automation technology datagram from the Ethernet for control automation technology frame to result in an extracted first Ethernet for control automation technology datagram and the second Ethernet for control automation technology datagram from the Ethernet for control automation technology frame to result in an extracted second Ethernet for control automation technology datagram. In certain embodiments, the apparatus includes a transmitter that: transmits the extracted first Ethernet for control automation technology datagram directly to the first device; and transmits the extracted second Ethernet for control automation technology datagram directly to the second device.

One method for forming an EtherCAT frame from an EtherCAT datagram includes receiving an Ethernet for control automation technology datagram. In some embodiments, the method includes receiving common header information corresponding to the Ethernet for control automation technology datagram. In certain embodiments, the method includes forming an Ethernet for control automation technology frame based on the Ethernet for control automation technology datagram.

An apparatus for forming an EtherCAT frame from an EtherCAT datagram, in one embodiment, includes a receiver that: receives an Ethernet for control automation technology datagram; and receives common header information corresponding to the Ethernet for control automation technology datagram. In various embodiments, the apparatus includes a processor that forms an Ethernet for control automation technology frame based on the Ethernet for control automation technology datagram.

<FIG> depicts an embodiment of a wireless communication system <NUM> for extracting EtherCAT datagrams from an EtherCAT frame. In one embodiment, the wireless communication system <NUM> includes remote units <NUM>, and network units <NUM>. Even though a specific number of remote units <NUM> and network units <NUM> are depicted in <FIG>, one of skill in the art will recognize that any number of remote units <NUM> and network units <NUM> may be included in the wireless communication system <NUM>.

In one embodiment, the remote units <NUM> may include computing devices, such as desktop computers, laptop computers, personal digital assistants ("PDAs"), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), IoT devices, or the like. The remote units <NUM> may communicate directly with one or more of the network units <NUM> via UL communication signals. Moreover, the remote units <NUM> may communicate directly with other remote units <NUM> via SL communication.

In certain embodiments, a network unit <NUM> may also be referred to as an access point, an access terminal, a base, a base station, a Node-B, an eNB, a gNB, a Home Node-B, a relay node, a device, a network device, or by any other terminology used in the art. In some embodiments, a network unit <NUM> may include one or more of the following network components a gNB, a NG-RAN node, a RAN node, a core network, an MME, an HSS, an SCEF, an AMF, an SMF, an NEF, a PCF, a UDR, a UPF, and/or a UDM.

In one implementation, the wireless communication system <NUM> is compliant with the LTE of the 3GPP protocol, wherein the network unit <NUM> transmits using an OFDM modulation scheme on the DL and the remote units <NUM> transmit on the UL using a SC-FDMA scheme or an OFDM scheme. More generally, however, the wireless communication system <NUM> may implement some other open or proprietary communication protocol, for example, WiMAX, among other protocols.

In certain embodiments, a remote unit <NUM> may receive an Ethernet for control automation technology datagram. In some embodiments, the remote unit <NUM> may receive common header information corresponding to the Ethernet for control automation technology datagram. In certain embodiments, the remote unit <NUM> may form an Ethernet for control automation technology frame based on the Ethernet for control automation technology datagram. Accordingly, a remote unit <NUM> may be used for forming an EtherCAT frame from an EtherCAT datagram.

In various embodiments, a network unit <NUM> may receive an Ethernet for control automation technology frame. In various embodiments, the network unit <NUM> may determine a first Ethernet for control automation technology datagram in the Ethernet for control automation technology frame for a first device and a second Ethernet for control automation technology datagram in the Ethernet for control automation technology frame for a second device. In certain embodiments, the network unit <NUM> may extract the first Ethernet for control automation technology datagram from the Ethernet for control automation technology frame to result in an extracted first Ethernet for control automation technology datagram and the second Ethernet for control automation technology datagram from the Ethernet for control automation technology frame to result in an extracted second Ethernet for control automation technology datagram. In some embodiments, the network unit <NUM> may transmit the extracted first Ethernet for control automation technology datagram directly to the first device. In various embodiments, the network unit <NUM> may transmit the extracted second Ethernet for control automation technology datagram directly to the second device. Accordingly, a network unit <NUM> may be used for extracting EtherCAT datagrams from an EtherCAT frame.

<FIG> depicts one embodiment of an apparatus <NUM> that may be used for forming an EtherCAT frame from an EtherCAT datagram. The apparatus <NUM> includes one embodiment of the remote unit <NUM>. Furthermore, the remote unit <NUM> may include a processor <NUM>, a memory <NUM>, an input device <NUM>, a display <NUM>, a transmitter <NUM>, and a receiver <NUM>. In some embodiments, the input device <NUM> and the display <NUM> are combined into a single device, such as a touchscreen. In certain embodiments, the remote unit <NUM> may not include any input device <NUM> and/or display <NUM>. In various embodiments, the remote unit <NUM> may include one or more of the processor <NUM>, the memory <NUM>, the transmitter <NUM>, and the receiver <NUM>, and may not include the input device <NUM> and/or the display <NUM>.

In certain embodiments, the processor <NUM> may form an EtherCAT frame based on an EtherCAT datagram.

In some embodiments, the memory <NUM> stores data relating to network registration.

The transmitter <NUM> is used to provide UL communication signals to the network unit <NUM> and the receiver <NUM> is used to receive DL communication signals from the network unit <NUM>. In one embodiment, the receiver <NUM> may: receive an EtherCAT datagram; and receive common header information corresponding to the EtherCAT datagram.

<FIG> depicts one embodiment of an apparatus <NUM> that may be used for extracting EtherCAT datagrams from an EtherCAT frame. The apparatus <NUM> includes one embodiment of the network unit <NUM>. Furthermore, the network unit <NUM> may include a processor <NUM>, a memory <NUM>, an input device <NUM>, a display <NUM>, a transmitter <NUM>, and a receiver <NUM>. As may be appreciated, the processor <NUM>, the memory <NUM>, the input device <NUM>, the display <NUM>, the transmitter <NUM>, and the receiver <NUM> may be substantially similar to the processor <NUM>, the memory <NUM>, the input device <NUM>, the display <NUM>, the transmitter <NUM>, and the receiver <NUM> of the remote unit <NUM>, respectively.

In various embodiments, the receiver <NUM> receives an EtherCAT frame. In various embodiments, the processor <NUM>: determines a first EtherCAT datagram in the EtherCAT frame for a first device and a second EtherCAT datagram in the EtherCAT frame for a second device; and extracts the first EtherCAT datagram from the EtherCAT frame to result in an extracted first EtherCAT datagram and the second EtherCAT datagram from the EtherCAT frame to result in an extracted second EtherCAT datagram. In certain embodiments, the transmitter <NUM>: transmits the extracted first EtherCAT datagram directly to the first device; and transmits the extracted second EtherCAT datagram directly to the second device.

Although only one transmitter <NUM> and one receiver <NUM> are illustrated, the network unit <NUM> may have any suitable number of transmitters <NUM> and receivers <NUM>.

In some embodiments, an Ethernet fieldbus may use fieldbus masters to send Ethernet packets to individual fieldbus slaves, or the fieldbus masters may broadcast to a group of fieldbus slaves. In such embodiments, the Ethernet packets may take the form of a fieldbus packet encapsulated inside an IP packet such as UDP. The fieldbus master may wait for the fieldbus slaves to process the received data and respond to the fieldbus master via a response packet.

In various embodiments, in an EtherCAT fieldbus system, Ethernet packets may be delayed by only a few nanoseconds by each fieldbus slave in the chain because the fieldbus slave reads and writes to the encapsulated datagram each time it is received. Accordingly, Ethernet packets are "processed on-the-fly. " In such embodiments, if an EtherCAT master sends a frame, each fieldbus slave extracts its own data packet from an Ethernet datagram addressed specifically to it, while simultaneously forwarding the frame to the next device in the chain. Similarly, data to be returned to the EtherCAT master is inserted on-the-fly while the packet is processed by the fieldbus slave, as the Ethernet frame passes through the device.

<FIG> is a schematic block diagram illustrating one embodiment of a system <NUM> that may use EtherCAT frames. The system <NUM> is a wireless system. The system <NUM> includes an EtherCAT master <NUM> (e.g., a network unit <NUM>), a first UE <NUM> (e.g., a first remote unit <NUM>), a second UE <NUM> (e.g., a second remote unit <NUM>), and a third UE <NUM> (e.g., a third remote unit <NUM>). The EtherCAT master <NUM> transmits <NUM> an EtherCAT frame to the first UE <NUM>. The first UE <NUM> processes the EtherCAT frame to extract an EtherCAT datagram corresponding to the first UE <NUM>, then inserts data to be returned to the EtherCAT master <NUM> into the EtherCAT datagram of the EtherCAT frame corresponding to the first UE <NUM>.

The first UE <NUM> then transmits <NUM> the revised EtherCAT frame to the second UE <NUM>. The second UE <NUM> processes the revised EtherCAT frame to extract an EtherCAT datagram corresponding to the second UE <NUM>, then inserts data to be returned to the EtherCAT master <NUM> into the EtherCAT datagram of the EtherCAT frame corresponding to the second UE <NUM>.

The second UE <NUM> then transmits <NUM> the revised EtherCAT frame to the third UE <NUM>. The third UE <NUM> processes the revised EtherCAT frame to extract an EtherCAT datagram corresponding to the third UE <NUM>, then inserts data to be returned to the EtherCAT master <NUM> into the EtherCAT datagram of the EtherCAT frame corresponding to the third UE <NUM>. The third UE <NUM> then transmits <NUM> the revised EtherCAT frame to the EtherCAT master <NUM>. As may be appreciated, latency may be added by the processing done by each of the first UE <NUM>, the second UE <NUM>, and the third UE <NUM>. This may result in high latency and inefficient use of resources (e.g., insufficient use of bandwidth with the entire EtherCAT transmitted to each of the first UE <NUM>, the second UE <NUM>, and the third UE <NUM>).

<FIG> is a schematic block diagram illustrating one embodiment of an EtherCAT frame <NUM>. The EtherCAT frame <NUM> includes an Ethernet header <NUM>, an EtherCAT header <NUM>, an EtherCAT telegram <NUM>, and an FCS <NUM>.

<FIG> is a schematic block diagram illustrating one embodiment of the EtherCAT telegram <NUM>. The EtherCAT telegram <NUM> includes a first datagram <NUM>, a second datagram <NUM>, a safety container <NUM>, a third datagram <NUM>, and an nth datagram <NUM>. As may be appreciated the EtherCAT telegram <NUM> may not include the safety container <NUM> and/or the EtherCAT telegram <NUM> may include fewer or more datagrams than illustrated. In one embodiment, the EtherCAT telegram <NUM> may include up to <NUM> datagrams. Each datagram may include a header, data to be read and/or written, and/or a working counter.

<FIG> is a schematic block diagram illustrating one embodiment of the safety container <NUM>. As illustrated, the safety container <NUM> may include a command <NUM> ("CMD"), a first safe data <NUM>, a first CRC <NUM> corresponding to the first safe data <NUM>, a second safe data <NUM>, a second CRC <NUM> corresponding to the second safe data <NUM>, and a connection ID <NUM> ("Conn ID"). As may be appreciated, the safety container <NUM> may include any suitable number of safe data and CRCs corresponding to the safe data.

<FIG> is a schematic block diagram illustrating one embodiment of communications <NUM> in a system that uses EtherCAT frames. Communications <NUM> are illustrated between a master <NUM> (e.g., EtherCAT master), a CN <NUM> (e.g., UPF), a RAN <NUM> (e.g., eNB, gNB, BS, AP, NR, etc.), and UEs <NUM> (e.g., multiple UEs, multiple remote units <NUM>, etc.). As may be appreciated, individual communications described herein may include one or more messages.

In one embodiment, in a first communication <NUM> transmitted from the master <NUM> to the CN <NUM>, the master <NUM> transmits an EtherCAT frame. In certain embodiments, the CN <NUM> (e.g., UPF) marks the incoming EtherCAT frame from the master <NUM> with an Ethertype identifier ("Ethertype ID") and adds the EtherCAT frame to a QoS flow. The Ethertype ID may be used to indicate that the EtherCAT frame received from the master <NUM> is an EtherCAT frame. In certain embodiments, a supported and/or configured topology of a slave connection, such as line, ring, star etc., may be indicated to the RAN <NUM> either with the QoS flow or as part of an N2 Interface (e.g., via a bit field).

In various embodiments, in a second communication <NUM> transmitted from the CN <NUM> to the RAN <NUM>, the CN <NUM> transmits the EtherCAT frame with the Ethertype ID to the RAN <NUM> as part of a QoS flow. In some embodiments, the RAN <NUM> (e.g., SDAP entity in the RAN <NUM> TX path) reads <NUM> the Ethertype ID in the QoS flow (e.g., and the topology information) and identifies the incoming Ethernet packet as an EtherCAT frame. In certain embodiments, the RAN <NUM> sets up <NUM> an Ethernet profile and context information corresponding to the EtherCAT frame to parse the EtherCAT telegram of the EtherCAT frame. This enables the RAN <NUM> to read, extract, and/or process the information in the EtherCAT telegram.

In various embodiments, the RAN <NUM> may read the EtherCAT telegram and segment the EtherCAT telegram into multiple datagrams (e.g., SDAP PDU's). The RAN <NUM> may map the datagrams to different radio bearers. The RAN <NUM> may schedule the datagrams (which include a node specific header and data) for unicast transmission for transmission to corresponding UEs <NUM>. Moreover, the RAN <NUM> may schedule common header information (e.g., EtherCAT header <NUM>) required for all UEs <NUM> (e.g., nodes) for multicast transmission.

In certain embodiments, the RAN <NUM> extracts the Ethertype ID (e.g., and the topology) from a QoS flow, reads the Ethertype ID (e.g., and the topology), determines whether the Ethertype ID matches an ID that corresponds to an EtherCAT frame structure (or any field bus protocol that does on the fly processing of an Ethernet frame), loads relevant profile information of the frame structure corresponding to the Ethertype ID, and parses the Ethernet packet according to the profile information. In such embodiments, parsing the packet Ethernet packet includes the reading, extracting, and/or processing information from the EtherCAT frame header. Moreover, in some embodiments, the RAN <NUM> extracts relevant details about nodes (e.g., UEs) such as an address of a node from each datagram header and a size of the data in the datagram. In various embodiments, an 'M' field in a datagram header may indicate the presence of more datagrams (e.g., a number of datagrams may be calculated) belonging to different slaves in an EtherCAT frame. As may be appreciated, a total size of an EtherCAT telegram may be determined from an EtherCAT header while a size of each datagram may be determined from a corresponding datagram header.

In certain embodiments, with information obtained by the RAN <NUM>, the RAN <NUM> (e.g., SDAP entity) may segment an EtherCAT telegram of an EtherCAT frame into multiple SDAP PDU's with each PDU mapped to a radio bearers (e.g., different radio bearers). In some embodiments, the RAN <NUM> maps datagrams belonging to different destination addresses and/or different priority to different radio bearer IDs and/or priorities.

In various embodiments, context information, such as a slave address (e.g., destination address), extracted from a datagram header may be mapped to a radio bearer ID and/or RNTI and the context information may be stored in memory (e.g., in a stored table) to be used for incoming EtherCAT frames. In certain embodiments, a stored table may include information about destination addresses belonging to slaves mapped to radio bearer IDs.

In some embodiments, information, such as read, write, and/or read/write, extracted from a datagram header and a corresponding size may be passed on to lower layers for scheduling decisions. In such embodiments, if the datagram header includes a write option and a corresponding datagram size for a slave to master transmission, then a scheduler may generate a corresponding uplink-scheduling grant, and the datagram header may be transmitted without an empty data field. In embodiments in which the datagram contains both read and write options, then downlink and uplink grant may be generated.

In certain embodiments, in a third communication <NUM> transmitted from the RAN <NUM> to the UEs <NUM>, the RAN <NUM> transmits the datagrams and the common header information to the UEs <NUM>.

In various embodiments, the UEs <NUM> reconstruct <NUM> and reassemble an EtherCAT frame using one or more corresponding EtherCAT datagrams based on an EtherCAT telegram structure and an EtherCAT frame structure. Accordingly, an EtherCAT header, one or more EtherCAT datagram headers and their corresponding data re placed in the EtherCAT frame. Moreover, filler or padding bits may be added to match a size of the EtherCAT telegram mentioned in a length field of the EtherCAT header due to missing datagrams corresponding to other nodes (e.g., other UEs <NUM>). The UEs <NUM> may transmit the reassembled EtherCAT frames to corresponding EtherCAT nodes. Moreover, the UEs <NUM> may receive EtherCAT frames from corresponding EtherCAT nodes. The UEs <NUM> may separate EtherCAT datagrams from the received EtherCAT frames from EtherCAT nodes and/or header information from the received EtherCAT frames from EtherCAT nodes.

In some embodiments, in a fourth communication <NUM> transmitted from the UEs <NUM> to the RAN <NUM>, the UEs <NUM> transmit EtherCAT datagrams and/or header information to the RAN <NUM>.

In various embodiments, the RAN <NUM> reconstructs <NUM> and reassembles datagrams received from the UEs <NUM> in a same order as that of the originally received EtherCAT telegram from the master <NUM>. The RAN <NUM> reconstruct the EtherCAT telegram to include a common header. Moreover, the RAN <NUM> may add filler bits and/or datagram headers may include information to inform the master <NUM> about any lost datagrams from the UEs <NUM>.

In some embodiments involving safety over EtherCAT, the RAN <NUM> may extract a safety message from a corresponding datagram (e.g., multiple safety messages from one or more corresponding datagrams). In certain embodiments, the RAN <NUM> may multicast one or more safety datagrams to different UEs <NUM>.

In certain embodiments, information, such as an order in which the slave nodes (e.g., nodes connected to UEs <NUM>) are connected in a topology, may be used for scheduling purposes. Accordingly, an order of connection of nodes may be stored and passed on to lower layers for scheduling purpose. In one example, a node connection order n1-n2-n3-n4 may be used to generate downlink and/or uplink grant order for slaves, resource mapping in via time and frequency resources, and/or slot scheduling. In another embodiment, a supported and/or configured topology of a slave connection, such as line, ring, star etc., may be indicated to the RAN <NUM> either with the QoS flow or as part of an N2 Interface.

In various embodiments, in a fifth communication <NUM> transmitted from the RAN <NUM> to the CN <NUM>, the RAN <NUM> transmits the reconstructed EtherCAT frame to the CN <NUM>. In some embodiments, in a sixth communication <NUM> transmitted from the CN <NUM> to the master <NUM>, the CN <NUM> transmits the reconstructed EtherCAT frame to the master <NUM>.

As may be appreciated, while the RAN <NUM> is described herein as segmenting and/or reconstructing an EtherCAT frame, in some embodiments, the master <NUM> may be directly connected to one or more of the UEs <NUM>. In such embodiments, the one or more UEs <NUM> may perform the functions described herein in relation to the RAN <NUM>. Thus, the one or more UEs <NUM> may segment PDUs to different radio bearers and transmit the segmented PDUs over Uu to the RAN <NUM> and/or over sidelink to other slaves directly.

<FIG> is a schematic block diagram illustrating one embodiment of a mapping <NUM> between an EtherCAT frame and a radio bearer. The mapping <NUM> includes an SDAP-SAP <NUM> that includes an SDAP entity <NUM>. Moreover, the SDAP entity <NUM> include an EtherCAT frame <NUM>. After the SDAP entity <NUM> parses the EtherCAT frame <NUM>, the SDAP entity <NUM> transmits the Ethernet header <NUM>, the EtherCAT header <NUM>, and a datagram of the EtherCAT telegram <NUM> that corresponds to a PDCP-SAP <NUM> (e.g., radio bearer). As may be appreciated, each PDCP-SAP (e.g., radio bearer) in a system may receive the Ethernet header <NUM>, the EtherCAT header <NUM>, and a datagram of the EtherCAT telegram <NUM> that corresponds to the respective PDCP-SAP.

In some embodiments, a PDCP entity (e.g., the PDCP-SAP <NUM>) may be notified about PDCP Ethernet header compression for a radio bearer carrying an EtherCAT header, an Ethernet header, a node specific header, and/or data. In one embodiment, RRC signaling may inform a PDCP entity about a compression profile ID, a context information indicating the static field in the header and its value, and so forth etc. In another embodiment, PDCP control PDU may be used to inform a PDCP entity about compression related information. In various embodiments, a compression ratio and/or field in the header chosen for compression may be dynamically adapted based on a channel condition, decompression feedback information, and/or available resources. In another embodiment, the compression profile ID and/or context information can be independently chosen for downlink, uplink, and/or sidelink.

<FIG> is a schematic flow chart diagram illustrating one embodiment of a method <NUM> for extracting EtherCAT datagrams from an EtherCAT frame. The method <NUM> in the illustrated embodiments uses an SDAP <NUM>, a PDCP <NUM>, an RLC <NUM>, a MAC <NUM>, and a PHY <NUM>. As illustrated, the SDAP <NUM> may identify an Ethertype from a QoS flow, and perform segmentation. Moreover, the PDCP <NUM> may perform header compression and perform datagram header compression. Furthermore, the RLC <NUM> may transmit ARQ in response to receiving the compressed headers. The MAC <NUM> may include a MUX that receives the compressed headers. In addition, the PHY <NUM> may perform coding, resource mapping, and/or transmission.

<FIG> is a schematic flow chart diagram illustrating another embodiment of a method <NUM> for extracting EtherCAT datagrams from an EtherCAT frame. In some embodiments, the method <NUM> is performed by an apparatus, such as the network unit <NUM>. In certain embodiments, the method <NUM> may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method <NUM> may include receiving <NUM> an Ethernet for control automation technology frame. In various embodiments, the method <NUM> includes determining <NUM> a first Ethernet for control automation technology datagram in the Ethernet for control automation technology frame for a first device (e.g., a first remote unit <NUM>) and a second Ethernet for control automation technology datagram in the Ethernet for control automation technology frame for a second device (e.g., a second remote unit <NUM>). In certain embodiments, the method <NUM> includes extracting <NUM> the first Ethernet for control automation technology datagram from the Ethernet for control automation technology frame to result in an extracted first Ethernet for control automation technology datagram and the second Ethernet for control automation technology datagram from the Ethernet for control automation technology frame to result in an extracted second Ethernet for control automation technology datagram. In some embodiments, the method <NUM> includes transmitting <NUM> the extracted first Ethernet for control automation technology datagram directly to the first device. In various embodiments, the method <NUM> includes transmitting <NUM> the extracted second Ethernet for control automation technology datagram directly to the second device.

In certain embodiments, the method <NUM> further comprises transmitting common header information corresponding to the Ethernet for control automation technology frame to the first device and the second device. In some embodiments, the common header information is scheduled for multicast transmission and hence mapped to a multicast logical data channel and/or a multicast radio bearer. In various embodiments, the extracted first Ethernet for control automation technology datagram and the extracted second Ethernet for control automation technology datagram are scheduled for unicast transmission and hence mapped to a unicast logical data channel and/or a unicast radio bearer.

In one embodiment, the method <NUM> further comprises receiving an identifier that indicates an incoming packet as the Ethernet for control automation technology frame. In certain embodiments, the method further comprises parsing the Ethernet for control automation technology frame based on an identified frame profile. In some embodiments, extracting the first Ethernet for control automation technology datagram and the second Ethernet for control automation technology datagram comprises: segmenting the Ethernet for control automation technology frame into a plurality of service data application protocol protocol data units; and mapping each service data application protocol protocol data unit of the plurality of service data application protocol protocol data units to a corresponding radio bearer.

In various embodiments, each service data application protocol protocol data unit comprises a priority, a destination address, or a combination thereof. In one embodiment, the method <NUM> further comprises: receiving a first response from the first device, wherein the first response corresponds to the first Ethernet for control automation technology datagram; receiving a second response from the second device, wherein the first response corresponds to the first Ethernet for control automation technology datagram; and forming an Ethernet for control automation technology reply frame based on the first response and the second response. In certain embodiments, the method <NUM> further comprises transmitting the Ethernet for control automation technology reply frame.

<FIG> is a schematic flow chart diagram illustrating one embodiment of a method <NUM> for forming an EtherCAT frame from an EtherCAT datagram. In some embodiments, the method <NUM> is performed by an apparatus, such as the remote unit <NUM>. In certain embodiments, the method <NUM> may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method <NUM> may include receiving <NUM> an Ethernet for control automation technology datagram. In some embodiments, the method <NUM> includes receiving <NUM> common header information corresponding to the Ethernet for control automation technology datagram. In certain embodiments, the method <NUM> includes forming <NUM> an Ethernet for control automation technology frame based on the Ethernet for control automation technology datagram.

In certain embodiments, the method <NUM> further comprises transmitting the Ethernet for control automation technology frame to a device. In some embodiments, the common header information is received from a multicast transmission. In various embodiments, the Ethernet for control automation technology datagram and is received from a unicast transmission.

In one embodiment, the method <NUM> further comprises receiving an identifier that indicates an incoming packet as the Ethernet for control automation technology datagram. In certain embodiments, the method <NUM> further comprises: receiving an Ethernet for control automation technology response frame from the device, wherein the Ethernet for control automation technology response frame corresponds to the Ethernet for control automation technology frame; and forming a response to the Ethernet for control automation technology datagram based on extracting information from the Ethernet for control automation technology response frame. In some embodiments, the method <NUM> further comprises transmitting the response to the Ethernet for control automation technology datagram.

In one embodiment, a method comprises: receiving an Ethernet for control automation technology frame; determining a first Ethernet for control automation technology datagram in the Ethernet for control automation technology frame for a first device and a second Ethernet for control automation technology datagram in the Ethernet for control automation technology frame for a second device; extracting the first Ethernet for control automation technology datagram from the Ethernet for control automation technology frame to result in an extracted first Ethernet for control automation technology datagram and the second Ethernet for control automation technology datagram from the Ethernet for control automation technology frame to result in an extracted second Ethernet for control automation technology datagram; transmitting the extracted first Ethernet for control automation technology datagram directly to the first device; and transmitting the extracted second Ethernet for control automation technology datagram directly to the second device.

In certain embodiments, the method further comprises transmitting common header information corresponding to the Ethernet for control automation technology frame to the first device and the second device.

In some embodiments, the common header information is scheduled for multicast transmission.

In various embodiments, the extracted first Ethernet for control automation technology datagram and the extracted second Ethernet for control automation technology datagram are scheduled for unicast transmission.

In one embodiment, the method further comprises receiving an identifier that indicates an incoming packet as the Ethernet for control automation technology frame.

In certain embodiments, the method further comprises parsing the Ethernet for control automation technology frame based on an identified frame profile.

In some embodiments, extracting the first Ethernet for control automation technology datagram and the second Ethernet for control automation technology datagram comprises: segmenting the Ethernet for control automation technology frame into a plurality of service data application protocol protocol data units; and mapping each service data application protocol protocol data unit of the plurality of service data application protocol protocol data units to a corresponding radio bearer.

In various embodiments, each service data application protocol protocol data unit comprises a priority, a destination address, or a combination thereof.

In one embodiment, the method further comprises: receiving a first response from the first device, wherein the first response corresponds to the first Ethernet for control automation technology datagram; receiving a second response from the second device, wherein the first response corresponds to the first Ethernet for control automation technology datagram; and forming an Ethernet for control automation technology reply frame based on the first response and the second response.

In certain embodiments, the method further comprises transmitting the Ethernet for control automation technology reply frame.

In one embodiment, an apparatus comprises: a receiver that receives an Ethernet for control automation technology frame; a processor that: determines a first Ethernet for control automation technology datagram in the Ethernet for control automation technology frame for a first device and a second Ethernet for control automation technology datagram in the Ethernet for control automation technology frame for a second device; and extracts the first Ethernet for control automation technology datagram from the Ethernet for control automation technology frame to result in an extracted first Ethernet for control automation technology datagram and the second Ethernet for control automation technology datagram from the Ethernet for control automation technology frame to result in an extracted second Ethernet for control automation technology datagram; and a transmitter that: transmits the extracted first Ethernet for control automation technology datagram directly to the first device; and transmits the extracted second Ethernet for control automation technology datagram directly to the second device.

In certain embodiments, the transmitter transmits common header information corresponding to the Ethernet for control automation technology frame to the first device and the second device.

In one embodiment, the receiver receives an identifier that indicates an incoming packet as the Ethernet for control automation technology frame.

In certain embodiments, the processor parses the Ethernet for control automation technology frame based on an identified frame profile.

In some embodiments, the processor extracting the first Ethernet for control automation technology datagram and the second Ethernet for control automation technology datagram comprises the processor: segmenting the Ethernet for control automation technology frame into a plurality of service data application protocol protocol data units; and mapping each service data application protocol protocol data unit of the plurality of service data application protocol protocol data units to a corresponding radio bearer.

In one embodiment, the receiver: receives a first response from the first device, wherein the first response corresponds to the first Ethernet for control automation technology datagram; and receives a second response from the second device, wherein the first response corresponds to the first Ethernet for control automation technology datagram; and the processor forms an Ethernet for control automation technology reply frame based on the first response and the second response.

In certain embodiments, the transmitter transmits the Ethernet for control automation technology reply frame.

In one embodiment, a method comprises: receiving an Ethernet for control automation technology datagram; receiving common header information corresponding to the Ethernet for control automation technology datagram; and forming an Ethernet for control automation technology frame based on the Ethernet for control automation technology datagram.

In certain embodiments, the method further comprises transmitting the Ethernet for control automation technology frame to a device.

In some embodiments, the common header information is received from a multicast transmission.

In various embodiments, the Ethemet for control automation technology datagram and is received from a unicast transmission.

In one embodiment, the method further comprises receiving an identifier that indicates an incoming packet as the Ethernet for control automation technology datagram.

In certain embodiments, the method further comprises: receiving an Ethernet for control automation technology response frame from the device, wherein the Ethernet for control automation technology response frame corresponds to the Ethernet for control automation technology frame; and forming a response to the Ethernet for control automation technology datagram based on extracting information from the Ethernet for control automation technology response frame.

In some embodiments, the method further comprises transmitting the response to the Ethernet for control automation technology datagram.

In one embodiment, an apparatus comprises: a receiver that: receives an Ethernet for control automation technology datagram; and receives common header information corresponding to the Ethernet for control automation technology datagram; and a processor that forms an Ethernet for control automation technology frame based on the Ethernet for control automation technology datagram.

In certain embodiments, the apparatus further comprises a transmitter that transmits the Ethernet for control automation technology frame to a device.

In various embodiments, the Ethernet for control automation technology datagram and is received from a unicast transmission.

In one embodiment, the receiver receives an identifier that indicates an incoming packet as the Ethernet for control automation technology datagram.

In certain embodiments: the receiver receives an Ethernet for control automation technology response frame from the device, wherein the Ethernet for control automation technology response frame corresponds to the Ethernet for control automation technology frame; and the processor forms a response to the Ethernet for control automation technology datagram based on extracting information from the Ethernet for control automation technology response frame.

In some embodiments, the apparatus further comprises a transmitter that transmits the response to the Ethernet for control automation technology datagram.

Claim 1:
A method (<NUM>) performed by a base station, the method comprising:
receiving (<NUM>) an Ethernet for control automation technology, EtherCAT, frame;
determining (<NUM>) a first EtherCAT datagram in the EtherCAT frame for a first device and a second EtherCAT datagram in the EtherCAT frame for a second device;
extracting (<NUM>) the first EtherCAT datagram from the EtherCAT frame to result in an extracted first EtherCAT datagram and the second EtherCAT datagram from the EtherCAT frame to result in an extracted second EtherCAT datagram;
transmitting (<NUM>) the extracted first EtherCAT datagram directly to the first device; and
transmitting (<NUM>) the extracted second EtherCAT datagram directly to the second device.