Carrying messages over wired access with transport protocol for fifth generation client devices

Abstract

Embodiments of the present disclosure relate to carrying messages over wired access using a transport protocol of a fifth generation client device. A device may register the device with a core network using a Point-to-Point Protocol over Ethernet (PPPoE) and a Point-to-Point Protocol (PPP), and may establish a first Packet Data Unit (PDU) session with the core network based on the PPPoE and the PPP. The device may configure the first PDU session to provide the first service based on the PPPoE and the PPP, and may generate a first keep-alive message to maintain the first PDU session. The device may establish a second PDU session with the core network based on the PPPoE and the PPP, and may configure the second PDU session based on the PPPoE and the PPP, where the second PDU session is configured to provide a second service different from the first service. The device may generate a second keep-alive message to maintain the second PDU session.

Description

[0001] Divisional Application Instructions

[0002] This application is a divisional application of the Chinese invention patent application with the application date of January 20, 2021, application number 202110076935.8, and name “Carrying messages on wired access using the transmission protocol of the fifth generation client device”. Technical Field

[0003] Embodiments of the present disclosure relate to client devices that transmit messages over wired access, and more particularly to carrying messages over wired access using a transport protocol of a fifth generation client device. Background Art

[0004] A client device (e.g., a residential gateway, a user equipment (UE), etc.) may be connected to a fifth generation (5G) core network using wired access (e.g., information transmission through physical elements such as fiber optic cables, coaxial cables, twisted pair cables, etc.). In this arrangement, when the client device is connected to the 5G core network using wired access, the client device may need to transmit non-access stratum (NAS) messages (e.g., packet data units (PDUs)) over the wired access. Summary of the invention

[0005] According to some implementations, a method may include: registering a device with a core network using Point-to-Point Protocol over Ethernet (PPPoE) and Point-to-Point Protocol (PPP), and establishing a first packet data unit (PDU) session with the core network based on PPPoE and PPP. The method may include: configuring the first PDU session with the core network based on PPPoE and PPP, wherein the first PDU session may be configured to provide a first service, and generating a first keep alive message to maintain the first PDU session with the core network. The method may include: establishing a second PDU session with the core network based on PPPoE and PPP, and configuring the second PDU session with the core network based on PPPoE and PPP, wherein the second PDU session may be configured to provide a second service different from the first service. The method may include: generating a second keep alive message to maintain the second PDU session with the core network.

[0006] According to some implementations, a device may include one or more memories and one or more processors, the one or more processors being used to register the device with a core network using PPPoE and PPP, and to establish a first PDU session with the core network based on PPPoE and PPP. The one or more processors may configure a first PDU session with the core network based on PPPoE and PPP, wherein the first PDU session may be configured to provide a first service, and may establish a second PDU session with the core network based on PPPoE and PPP. The one or more processors may configure a second PDU session with the core network based on PPPoE and PPP, wherein the second PDU session may be configured to provide a second service different from the first service.

[0007] According to some implementations, a non-transitory computer-readable medium may store one or more instructions that, when executed by one or more processors of a device, may cause the one or more processors to register the device with a core network using PPPoE and PPP, and to establish a first PDU session with the core network based on PPPoE and PPP. The one or more instructions may cause the one or more processors to configure the first PDU session with the core network based on PPPoE and PPP, wherein the first PDU session may be configured to provide a first service. The one or more instructions may cause the one or more processors to transmit a first keep-alive message to maintain the first PDU session with the core network. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figures 1A to 1S is a schematic diagram of one or more example implementations described herein.

[0009] Figure 2 is a schematic diagram of an example environment in which the systems and / or methods described herein may be implemented.

[0010] Figure 3 and Figure 4 yes Figure 2 A schematic diagram of example components of one or more devices.

[0011] Figures 5 to 7 is a flow chart of an example process for carrying messages over wired access utilizing a transport protocol for a 5G client device. DETAILED DESCRIPTION

[0012] The following detailed description of example implementations refers to the accompanying drawings.The same reference numbers in different drawings may identify the same or similar elements.

[0013] Currently, NAS messages can be transmitted via a single PDU session model or a multi-access PDU session model, and multiple (e.g., single access or multi-access) PDU sessions may be required to transmit NAS messages. The traffic of each PDU session may go to different core network devices and may require different services (e.g., aggregate maximum bit rate, guaranteed bit rate, quality of service (QoS) shaping requirements, etc.). However, identifying different PDU sessions from the same client device may not be achieved by using a media access control (MAC) address, an Internet Protocol (IP) address, a virtual local area network (VLAN), etc.

[0014] One current technique for handling different PDU sessions involves having the control plane utilize Extensible Authentication Protocol (EAP) over PPPoE to deliver NAS control plane packets. Unfortunately, since EAP carries NAS packets, the forwarding plane may be required to perform time-consuming and resource-intensive deep packet inspection to identify the packets to be provided to the control plane. EAP is always initiated from the core network side, and only client devices that support 5G can respond to EAP. Moreover, EAP requests that attempt to identify the 5G capabilities of a client device will affect existing client devices that support EAP but not 5G.

[0015] Another current technique for handling different PDU sessions includes having the data plane utilize stateless PPPoE to transmit data packets. In this technique, a session identifier is assigned by the client device, and the core network device blindly accepts packets based on the session identifier, which exposes the core network device to possible attacks. In addition, the combination of the MAC address from the client device and the session identifier will not be sufficient to uniquely identify the PDU session, and this technique requires expensive changes to the access network of the core network.

[0016] Therefore, current technologies for handling different PDU sessions may waste computing resources (e.g., processing resources, memory resources, communication resources, etc.), networking resources, etc. associated with performing deep packet inspection, determining the 5G capabilities of client devices, modifying access networks, handling network attacks, etc.

[0017] Some implementations described herein provide a client device that utilizes a transport protocol to carry messages via wired access to a 5G core network. For example, a client device may register the client device with a core network using PPPoE and PPP, and may establish a first PDU session with the core network based on PPPoE and PPP. The client device may configure a first PDU session with the core network based on PPPoE and PPP, wherein the first PDU session may be configured to provide a first service, and may generate a first keep-alive message to maintain the first PDU session with the core network. The client device may establish a second PDU session with the core network based on PPPoE and PPP, and may configure a second PDU session with the core network based on PPPoE and PPP, wherein the second PDU session may be configured to provide a second service different from the first service. The client device may generate a second keep-alive message to maintain the second PDU session with the core network.

[0018] In this way, the client device can utilize the transport protocol to carry messages via wired access to the 5G core network. The client device can use PPPoE and PPP with a new set of protocol identifiers for control services (e.g., packets) and data services. The client device can utilize PPPoE and PPP to handle multiple PDU sessions, thereby providing different services for multiple PDU sessions as needed. In turn, this saves computing resources (e.g., processing resources, memory resources, communication resources, etc.), networking resources, etc., which would otherwise be wasted when performing deep packet inspection, determining the 5G capabilities of the client device, modifying the access network, handling network attacks, etc.

[0019] Figures 1A to 1S is a schematic diagram of one or more example implementations 100 described herein. Figure 1A As shown, the client device may be associated with a wired access network (AN) and a core network. The client device may include network devices (e.g., residential gateways), mobile devices (e.g., user equipment), etc., which utilize a transport protocol to carry messages via wired access to the core network. The AN may include one or more radio transmitters. The core network may include an example architecture of a 5G next generation (NG) core network included in a 5G wireless telecommunications system, and may include physical elements, virtual elements, or a combination of physical elements and virtual elements.

[0020] As in Figure 1AAs further shown in the figure by reference numeral 105, the client device can utilize PPPoE and PPP to register the client device with the core network. In some implementations, as described herein, the client device can utilize PPPoE and PPP as a transport protocol to carry messages via wired access to the core network. In some implementations, the client device can utilize Figure 1B The call flow shown is used to register a client device with the core network using PPPoE and PPP.

[0021] like Figure 1B As shown, the client device can be associated with the AN and the access gateway function (AGF), access and mobility management function (AMF), session management function (SMF) and user plane function (UPF) of the core network. Figure 1B As further shown, the client device may provide a registration initiation request (e.g., a PPPoE Active Discovery Initiation (PADI) packet) to the AN, and the AN may provide a registration initiation request (e.g., along with an identifier of the client device) to the AGF. The AGF and the AMF may establish an N2 interface provided between the AGF and the AMF. The AGF may provide an offer response (e.g., a PPPoE Active Discovery Offer (PADO) packet) to the client device. The client device may provide a registration request (e.g., a PPPoE Active Discovery Request (PADR) packet) to the AN, and the AN may provide a registration request (e.g., along with an identifier of the client device) to the AGF. The client device and the AGF may establish a PPP Link Control Protocol (LCP) connection to exchange information (e.g., maximum receive unit (MRU), randomly generated numbers (e.g., called magic numbers), authorization information, etc.).

[0022] like Figure 1BAs further shown, the client device may provide a registration request (e.g., a PPP NAS registration request including network slice selection assistance information (NSSAI)) to the AGF, and the AGF may provide a Next Generation Application Protocol (NGAP) initial message (e.g., a registration request) to the AMF. Based on receiving the initial message, the AMF may provide an NGAP downlink NAS transmission identification request (e.g., finding the identification of the client device) to the AGF, and the AGF may provide the identification request to the client device via the PPP NAS downlink message. The client device may provide an identification response (e.g., identifying the client device) to the AGF via a PPP NAS uplink message, and the AGF may provide the identification response to the AMF (e.g., transmitting via the NGAP uplink NAS). Based on receiving the identification response, the AMF may provide an NGAP downlink NAS transmission authentication request (e.g., finding the authentication of the client device) to the AGF, and the AGF may provide the authentication request to the client device via the PPP NAS downlink message. The client device may provide an authentication response (e.g., authenticating the client device) to the AGF via the PPP NAS uplink message, and the AGF may provide the identification response to the AMF (e.g., transmitting via the NGAP uplink NAS).

[0023] Based on receiving the authentication response, the AMF may provide the AGF with an NGAP downlink NAS transmit security mode command (e.g., to be executed by the client device), and the AGF may provide the security mode command to the client device via a PPP NAS downlink message. The client device may execute the security mode command and provide a security mode complete response to the AGF via a PPP NAS uplink message (e.g., indicating that the client device executed the security mode command), and the AGF may provide the security mode complete response to the AMF (e.g., transmitted via the NGAP uplink NAS). Based on receiving the security mode complete response, the AMF may provide the AGF with an NGAP downlink NAS transmit registration acceptance (e.g., to be accepted by the client device), and the AGF may provide the client device with a registration acceptance via a PPP NAS message. The client device may accept the registration and provide a registration complete response to the AGF via a PPP NAS uplink message (e.g., indicating that the client device executed the security mode command). Based on receiving the registration complete response, the AGF may provide a registration complete response to the AMF (e.g., transmitted via the NGAP uplink NAS).

[0024] As in Figure 1C As shown by reference numeral 110 in FIG. 1 , the client device can utilize PPPoE and PPP to deregister the client device from the core network and release the PDU session (e.g., after the client device is registered and based on ending the PDU session). In some implementations, the client device can use Figure 1D The call flow shown is used to log out a client device from the core network using PPPoE and PPP.

[0025] like Figure 1D As shown, the client device may provide a deregistration request to the AGF via a PPP NAS message, and the AGF may provide the deregistration request to the AMF (e.g., transmitted via an NGAP uplink NAS). Based on receiving the deregistration request, the AMF may deregister the client device with the core network, and may provide an NGAP downlink NAS transmission deregistration acceptance message to the AGF. The AGF may provide a deregistration acceptance message to the client device via a PPP NAS message. The AMF may also provide another NGAP downlink NAS transmission deregistration request to the AGF, and the AGF may provide another deregistration request to the client device via a PPP NAS message. The client device may accept the deregistration request, and may provide another deregistration acceptance message to the AGF via a PPP NAS message. The AGF may provide another deregistration acceptance message to the AMF (e.g., transmitted via an NGAP uplink NAS), and the client device may deregister with the core network.

[0026] As in Figure 1E As shown by reference numeral 115 in FIG. 1 , the client device can utilize PPPoE and PPP to configure a PDU session with the core network. In some implementations, the client device can use Figure 1F The top portion of the call flow shown is used to configure a PDU session with the core network using PPPoE and PPP. Figure 1E As further shown in FIG. 1 by reference numeral 120, the client device can utilize PPPoE and PPP to modify the PDU session with the core network. In some implementations, the client device can use Figure 1F The bottom portion of the call flow shown utilizes PPPoE and PPP to modify the PDU session with the core network.

[0027] like Figure 1FAs shown in the top portion of , the client device (e.g., to establish and configure a PDU session) may provide a PDU session establishment request to the AGF via a PPP NAS message, and the AGF may provide the PDU session establishment request to the AMF via an NGAP uplink NAS transmission. Based on receiving the PDU session establishment request, the AMF may provide a network slice management function (NSMF) PDU session creation request to the SMF, and the SMF may provide an N4 packet forwarding control protocol (PFCP) session creation request to the UPF. The UPF may accept the N4 PFCP session creation request and may provide an N4 PFCP session creation response to the SMF. The SMF may provide an NSMF PDU session creation response to the AMF, and the AMF may provide a PDU session establishment acceptance to the AGF via an NGAP PDU session resource establishment request. The AGF may provide a PDU session establishment acceptance (e.g., and a data session identifier) ​​to the client device, and the client device may establish a PDU session with the core network. Based on establishing the PDU session, the client device may provide a PDU session establishment completion to the AGF via a PPP NAS message, and the AGF may provide an NGAP PDU session resource establishment response to the AMF. AMF may provide a NSMF PDU session modification request to SMF, and SMF may provide a N4 PFCP session modification request to UPF. UPF may provide a N4 PFCP session modification response to SMF, and SMF may provide a NSMF session modification response to AMF.

[0028] like Figure 1F As shown in the bottom portion of , the client device (for example, in order to modify a PDU session) may provide a PDU session modification request to the AGF via a PPP NAS message. The AGF may provide the PDU session modification request to the AMF via an NGAP uplink NAS transmission, and the AMF may provide an NSMF session modification request to the SMF. The SMF may provide an N4 PFCP session modification response to the UPF, and the UPF may provide an N4 PFCP session modification response to the SMF. The SMF may provide an NSMF session modification response to the AMF, and the AMF may provide a PDU session modification command to the AGF via an NGAP downlink NAS transmission. The AGF may provide a PDU session modification command to the client device via a PPP NAS downlink transmission message, and the client device may execute the PDU session modification command to modify the PDU session or may reject the modification. The client device may provide a PDU session modification complete / reject to the AGF via a PPP NAS message, and the AGF may provide a PDU session modification complete / reject to the AMF via an NGAP uplink NAS transmission.

[0029] As in Figure 1GAs shown by reference numeral 125 in FIG. 1 , the client device can utilize PPPoE and PPP to release the PDU session with the core network. In some implementations, the client device can utilize Figure 1H The call flow shown is to utilize PPPoE and PPP to release the PDU session with the core network.

[0030] like Figure 1H As shown, the client device (e.g., in order to release the PDU session) may provide a PDU session release request to the AGF via a PPP NAS message, and the AGF may provide the PDU session release request to the AMF via an NGAP uplink NAS transmission. Based on receiving the PDU session release request, the AMF may provide an NSMF PDU session delete request to the SMF, and the SMF may provide an N4 PFCP session delete request to the UPF. The UPF may provide an N4 PFCP session delete response to the SMF (e.g., indicating that the PDU session will be deleted), and the SMF may provide an NSMF PDU session delete response to the AMF. Based on receiving the NSMF PDU session delete response, the AMF may provide a PDU session release command to the AGF via an NGAP downlink NAS transmission, and the AGF may provide the PDU session release command to the client device via a PPP NAS message. The client device may execute the PDU session release command to release the PDU session, or may reject the command. The client device may then provide the PDU session release complete / reject to the AGF via a PPP NAS message, and the AGF may provide the PDU session release complete / reject to the AMF via a NGAP uplink NAS transmission.

[0031] As in Fig. 1I As shown by reference numeral 130, the client device can use PPPoE and PPP to establish multiple PDU sessions with the core network. In some implementations, the client device can use Figure 1J and Figure 1K The call flow shown is used to establish multiple PDU sessions with the core network using PPPoE and PPP.

[0032] like Figure 1JAs shown, the client device (e.g., to establish a first PDU session and a second PDU session) may provide a registration initiation request (e.g., a PADI packet) and a session identifier (e.g., 0) to the AGF, and the AGF may provide an offer response (e.g., a PADO) packet to the client device. The AGF and the AMF may establish an N2 interface provided between the AGF and the AMF. The client device may provide a registration request (e.g., a PADR packet) to the AGF, and the AGF may respond with a session confirmation (e.g., a PPPoE Active Discovery Session Confirmation (PADS) packet) and a session identifier (e.g., X). The client device and the AMF may complete the registration process of the client device. The client device and the AGF may generate and transmit a PPP keep-alive message to maintain the session (e.g., session X).

[0033] like Figure 1J As further shown, the client device (e.g., to establish a first PDU session) may provide a PDU session establishment request and a PDU session identifier (e.g., P1) to the AGF via a PPP NAS message, and the AGF may provide the PDU session establishment request to the AMF via an NGAP uplink NAS transmission. Based on receiving the PDU session establishment request, the AMF may provide an NSMF PDU session creation request to the SMF, and the SMF may provide an N4 PFCP session creation request to the UPF. The UPF may accept the N4 PFCP session creation request and may provide an N4 PFCP session creation response to the SMF. The SMF may provide an NSMF PDU session creation response to the AMF, and the AMF may provide a PDU session establishment acceptance to the AGF via a PDU session resource establishment request. The AGF may provide a PDU session establishment acceptance (e.g., and a session identifier D1) to the client device, and the client device may establish a first PDU session with the core network. Based on establishing the first PDU session, the client device may provide a PDU session establishment completion to the AGF via a PPP NAS message, and the AGF may provide a PDU session resource establishment response to the AMF. The AMF may provide a NSMF PDU session modification request to the SMF, and the SMF may provide a N4 PFCP session modification request to the UPF. The UPF may provide a N4 PFCP session modification response to the SMF, and the SMF may provide a NSMF PDU session modification response to the AMF. The client device and the AGF may generate and transmit a PPP keep-alive message to maintain the first PDU session (e.g., session D1). The AGF and the UPF may establish a first general packet radio service (GPRS) tunneling protocol (GTP) tunnel (e.g., T1) for the first PDU session.

[0034] like Figure 1KAs shown, the client device (e.g., to establish a second PDU session) may provide a PDU session establishment request and a PDU session identifier (e.g., P2) to the AGF via a PPP NAS message, and the AGF may provide the PDU session establishment request to the AMF via an NGAP uplink NAS transmission. Based on receiving the PDU session establishment request, the AMF may provide an NSMF PDU session creation request to the SMF, and the SMF may provide an N4 PFCP session creation request to the UPF. The UPF may accept the N4 PFCP session creation request and may provide an N4 PFCP session creation response to the SMF. The SMF may provide an NSMF PDU session creation response to the AMF, and the AMF may provide a PDU session establishment acceptance to the AGF via a PDU session resource establishment request. The AGF may provide a PDU session establishment acceptance (e.g., and a session identifier D2) to the client device, and the client device may establish a second PDU session with the core network. Based on establishing the second PDU session, the client device may provide a PDU session establishment completion to the AGF via a PPP NAS message, and the AGF may provide a PDU session resource establishment response to the AMF. The AMF may provide a NSMF PDU session modification request to the SMF, and the SMF may provide a N4 PFCP session modification request to the UPF. The UPF may provide a N4 PFCP session modification response to the SMF, and the SMF may provide a NSMF PDU session modification response to the AMF. The client device and the AGF may generate and transmit a PPP keep-alive message to maintain the second PDU session (e.g., session D2). The AGF and the UPF may establish a GTP tunnel (e.g., T2) for the second PDU session.

[0035] Figure 1L The types of information utilized by PPPoE and PPP in the implementations described herein are shown. As shown, PPPoE may include bits associated with the PPP session phases, offer (PADO), initiation (PADI), session grant (PADG), session credit response (PADC), quality (PADQ), request (PADR), session confirmation (PADS), termination (PADT), message (PADM), and network (PADN).

[0036] like Figure 1LAs further shown, PPP may include bits associated with: Internet Protocol version 4 (IPv4), Bridged PDU, Multilink, Internet Protocol version 6 (IPv6), 5G data, Multi-Protocol Label Switching (MPLS) unicast, MPLS multicast, Provider Specific Protocol (VSP), Internet Protocol Control Protocol, IPv6 Control Protocol, Provider Specific Network Control Protocol (VSNCP), 5G Access Layer, Link Control Protocol, Cryptographic Authentication Protocol, Provider Specific Authentication Protocol (VSAP), Challenge Handshake Authentication Protocol, and Extensible Authentication Protocol. In some implementations, bits associated with 5G data and 5G access layer may be newly provided in PPP.

[0037] Figure 1M Information included in Ethernet packets, PPPoE packets of Ethernet packets, and PPP packets of PPPoE packets that can be used in the implementations described herein is shown. For example, the Ethernet packet encapsulation format may include a destination address field, a source address field, an Ethernet type field, a PPPoE packet field, and a checksum field. The PPPoE packet encapsulation format may include a version field, a type field, a code field, a session identifier field, a length field, and a PPP packet field. The PPP packet encapsulation format may include a flag field, an address field, a control field, a protocol field, an information field, a frame check sequence (FCS) field, and another flag field.

[0038] Figure 1N A packet associated with a 5G access layer over PPPoE that can be utilized in the implementations described herein is depicted. As shown, a first portion of the packet may include a destination media access control (MAC) address field, a source MAC address field, an Ethernet type field, and a PPPoE field pointing to a second portion of the packet. The second portion of the packet may include a version field, a type field, a code field, a session identifier field, a length field, and a PPP field pointing to a third portion of the packet. The third portion of the packet may include a protocol field (e.g., including the newly provided information "0x80XX") and a payload field pointing to a fourth portion of the packet. The fourth portion of the packet may include a 5G control field.

[0039] Fig.1O Figure 2 shows a type of 5G control NAS message format for registration and deregistration of client devices, as utilized by PPPoE and PPP in the implementations described herein. Fig.1OAs shown in the left table of , the 5G NAS message format for registration may include a version field, a flag field, a message type = registration request field, an S-NSSAI [octet 1] field, an S-NSSAI [octet 2] field, an S-NSSAI [octet 3] field, an S-NSSAI [octet 4] field, a length of the NAS PDU [octet 1] field, a length of the NAS PDU [octet 2] field, a type-length-value (ATLV) number field, an ATLV field, a NAS PDU [octet 1] field, a NAS PDU [octet 2] field, and a NAS PDU [octet N] field. Fig.1O As shown in the right table of , the 5G NAS message format for deregistration may include a version field, an attribute type length value (ATLV) flag field (for example, not set at "0" and set at "1"), a flag field, a message type = registration accept / complete / reject, a deregistration request / accept field, a NAS PDU [octet 1] length field, a NAS PDU [octet 2] length field, a NAS PDU [octet 1] field, a NAS PDU [octet 2] field, and a NAS PDU [octet N] field.

[0040] Figure 1P Figure 2 shows a type of 5G control NAS message format for PDU session management of client devices, as utilized by PPPoE and PPP in the implementations described herein. Figure 1P As shown in the left table of , the 5G NAS message format for PDU session management may include a version field, a flag field, a message type = PDU session establishment request / rejection / completion, PDU session modification request / command / rejection / completion, PDU session release request / command / rejection / completion field, a PDU session-ID field, a process transaction ID (PTI) field, a length of the NAS PDU [octet 1] field, a length of the NAS PDU [octet 2] field, a NAS PDU [octet 1] field, a NAS PDU [octet 2] field, and a NAS PDU [octet N] field. Figure 1P As shown in the table on the right, the 5G NAS message format for PDU session establishment acceptance may include a version field, a flag field, a message type = PDU session establishment acceptance field, a PDU session-ID field, a process transaction ID (PTI) field, a 5G data session-ID [octet 1] field, a 5G data session-ID [octet 2] field, a NAS PDU [octet 1] length field, a NAS PDU [octet 2] length field, a NAS PDU [octet 1] field, a NAS PDU [octet 2] field, and a NAS PDU [octet N] field.

[0041] Figure 1Q Figure 2 shows the types of 5G control NAS message formats used for uplink and downlink transmissions, as utilized by PPPoE and PPP in the implementations described herein. Figure 1Q As shown in the left table of , the 5G NAS message format for uplink transmission and downlink transmission may include a version field, a flag field, a message type = uplink (UL) transmission / downlink (DL) transmission field, a PDU session-ID field, a process transaction ID (PTI) field, a NAS PDU [octet 1] length field, a NAS PDU [octet 2] length field, a NAS PDU [octet 1] field, a NAS PDU [octet 2] field, and a NAS PDU [octet N] field. Figure 1Q As shown in the table on the right, uplink transmission can be utilized with service request, configuration update completion, authentication response / failure, identification response, security mode completion / rejection, security protected 5G NAS message, 5GMM status, 5GSM status and notification response. Downlink transmission can be utilized with service acceptance / rejection, configuration update command, authentication request / result / rejection, identification request, security mode command, security protected 5G NAS message, 5GMM status, 5GSM status and notification.

[0042] Figure 1R A packet associated with a 5G data protocol over PPPoE that can be utilized in the implementations described herein is depicted. As shown, the first portion of the packet may include a destination MAC address field, a source MAC address field, an Ethernet type field, and a PPPoE field pointing to the second portion of the packet. The second portion of the packet may include a version field, a type field, a code field, a session identifier field, a length field, and a PPP field pointing to the third portion of the packet. The third portion of the packet may include a protocol field (e.g., including the newly provided information "0x00XX") and a 5G data field pointing to the fourth portion of the packet. The fourth portion of the packet may include a version / flag field, a reflective quality of service (QoS) indicator (RQI) / QoS flow identifier (QFI) field, a protocol field, and a payload field.

[0043] Figure 1S The message format of a 5G data payload is shown, as utilized by PPPoE and PPP in the implementations described herein. As shown, the message format for a 5G data payload may include a version field, a reflective QoS field, a flag field, a QFI field, a PPP protocol [octet 1] field, a PPP protocol [octet 2] field, and a data field.

[0044] In this way, the client device uses a transport protocol to carry messages via wired access to the 5G core network, thereby improving the operation of the 5G core network, client devices, etc. For example, the client device can use PPPoE and PPP with a new set of protocol identifiers for control services and data services, and can use PPPoE and PPP to handle multiple PDU sessions, thereby providing different services to multiple PDU sessions as needed. In addition, there is currently no technology that uses a transport protocol to carry messages via wired access to the 5G core network in the manner described herein. Ultimately, the client device saves computing resources (such as processing resources, memory resources, communication resources, etc.), networking resources, etc., which would otherwise be wasted when performing deep packet inspection, determining the 5G capabilities of the client device, modifying the access network, handling network attacks, etc.

[0045] In addition, since no other protocols are provided to carry the overhead of packets for control, the implementation described herein can provide a lightweight protocol and can enable the control plane to assign session identifiers to the data plane, thereby enabling the control plane to maintain control of the data session and prevent conflicts and attacks. The implementation described herein can support the strict scale and latency requirements of 5G and can provide a simple packet format that can be processed by data plane hardware and software.

[0046] As indicated above, only Figures 1A to 1S As an example. Other examples may differ from the Figures 1A to 1S As described.

[0047] Figure 2 2 is a schematic diagram of an example environment 200 in which the systems and / or methods described herein may be implemented. Figure 2 As shown, example environment 200 may include client device 205, AN 210, core network 215, and data network 275. Devices and / or networks of example environment 200 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections.

[0048] The client device 205 includes one or more devices capable of receiving, generating, storing, processing, and / or providing information, such as the information described herein. For example, the client device 205 may include a residential gateway, a user device, a network device (e.g., a label switching router (LSR), a label edge router (LER), an ingress router, an egress router, a provider router, a virtual router, a gateway, a switch, a firewall, a hub, a bridge, a reverse proxy, a proxy server, a cloud server, a data center server, a load balancer, etc.), or a similar type of device. In some implementations, the client device 205 may receive network traffic from the core network 215 via the AN 210 and / or may provide network traffic to the core network 215.

[0049] AN 210 may include one or more nodes associated with a wired connection to a core network 215. AN 210 may include a central unit (CU) including a next generation (NG) interface connecting the CU to a core unit (NG) (e.g., a next generation core (NGC) unit), which may be a node of the core network 215. AN 210 may transfer traffic between client devices 205 and the core network 215. In some implementations, AN 210 may perform scheduling and / or resource management for client devices 205 covered by AN 210. In some implementations, AN 210 may be controlled or coordinated by a network controller, which may perform load balancing, network-level configuration, etc. The network controller may communicate with AN 210 via a wireless or wired backhaul. In some implementations, AN 210 may include a network controller, a self-organizing network (SON) module or component, or a similar module or component. In other words, the AN 210 may perform network control, scheduling and / or network management functions (eg, for uplink communications, downlink communications and / or sidelink communications for the client devices 205 covered by the AN 210 ).

[0050] In some implementations, the core network 215 may include an example functional architecture that may implement the systems and / or methods described herein. For example, the core network 215 may include an example architecture of a fifth generation (5G) next generation (NG) core network included in a 5G wireless telecommunications system. Figure 2 The example architecture of the core network 215 shown may be an example of a service-based architecture, but in some implementations, the core network 215 may be implemented as a reference point architecture.

[0051] like Figure 2 As shown, the core network 215 may include multiple functional elements. The functional elements may include, for example, a network slice selection function (NSSF) 220, a network exposure function (NEF) 225, an authentication server function (AUSF) 230, a unified data management (UDM) component 235, a policy control function (PCF) 240, an application function (AF) 245, an access and mobility management function (AMF) 250, an access gateway function (AGF) 255, a session management function (SMF) 260, a user plane function (UPF) 265, etc. These functional elements may be communicatively connected via a message bus 270. Figure 2 Each of the functional elements shown is implemented on one or more devices associated with a wireless telecommunications system. In some implementations, one or more functional elements may be implemented on physical devices such as access points, base stations, gateways, etc. In some implementations, one or more functional elements may be implemented on a computing device in a cloud computing environment.

[0052] NSSF 220 includes one or more devices that select a network slice instance for a client device 205. By providing network slicing, NSSF 220 allows operators to deploy multiple substantially independent end-to-end networks that potentially have the same infrastructure. In some implementations, each slice can be customized for different services.

[0053] NEF 225 includes one or more devices that support exposure of capabilities and / or events in the wireless telecommunication system to assist other entities in the wireless telecommunication system in discovering network services.

[0054] The AUSF 230 includes one or more devices that act as an authentication server and support the process of authenticating the client device 205 in the wireless telecommunications system.

[0055] The UDM 235 includes one or more devices that store user data and profiles in a wireless telecommunications system. The UDM 235 can be used for fixed access, mobile access, etc. in the core network 215.

[0056] PCF 240 includes one or more devices that provide a policy framework that includes network slicing, roaming, packet processing, mobility management, etc.

[0057] AF 245 includes one or more devices that support application influence on traffic routing, access to NEF 225, policy control, etc.

[0058] The AMF 250 includes one or more devices that serve as termination points for non-access stratum (NAS) signaling, mobility management, and the like.

[0059] The AGF 255 includes one or more devices between the wired access infrastructure (e.g., AN 210) and the wireless core network 215, which supports residential gateways (e.g., client devices 205) including 5G NAS signaling and pure wired residential gateways.

[0060] SMF 260 includes one or more devices that support the establishment, modification and release of communication sessions in a wireless telecommunications system. For example, SMF 260 can configure business steering policies at UPF 265, implement user equipment IP address allocation and policies, etc.

[0061] UPF 265 includes one or more devices that serve as an anchor point for intra-RAT and / or inter-RAT mobility. UPF 265 can apply rules to packets, such as rules related to packet routing, traffic reporting, handling user plane QoS, and the like.

[0062] The message bus 270 represents a communication structure for communication between functional elements. In other words, the message bus 270 can allow communication between two or more functional elements.

[0063] The data network 275 includes one or more wired and / or wireless data networks. For example, the data network 275 may include an IP multimedia subsystem (IMS), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a private network (such as a company intranet), an ad hoc network, the Internet, a fiber-based network, a cloud computing network, a third-party service network, an operator service network, etc. and / or a combination of these or other types of networks.

[0064] Figure 2 The number and arrangement of devices and networks shown are provided as examples. Figure 2 There may be additional devices and / or networks, fewer devices and / or networks, different devices and / or networks, or differently arranged devices and / or networks than those shown. Figure 2 Two or more of the devices shown may be implemented in a single device, or Figure 2 The single device shown may be implemented as multiple distributed devices. Additionally or alternatively, a collection of devices (eg, one or more devices) of the example environment 200 may perform one or more functions described as being performed by another collection of devices of the example environment 200.

[0065] Figure 3 2 is a diagram of example components of device 300. Device 300 may correspond to client device 205, NSSF 220, NEF 225, AUSF 230, UDM 235, PCF 240, AF 245, AMF 250, AGF 255, SMF 260, and / or UPF 265. In some implementations, client device 205, NSSF 220, NEF 225, AUSF 230, UDM 235, PCF 240, AF 245, AMF 250, AGF 255, SMF 260, and / or UPF 265 may include one or more devices 300 and / or one or more components of device 300. Figure 3 As shown, the device 300 may include one or more input components 305-1 to 305-A (A≥1) (hereinafter collectively referred to as input component 305, and individually referred to as input component 305), a switching component 310, one or more output components 315-1 to 315-B (B≥1) (hereinafter collectively referred to as output component 315, and individually referred to as output component 315) and a controller 320.

[0066] The input component 305 can be an attachment point for a physical link and can be an entry point for incoming traffic (such as packets). The input component 305 can process incoming traffic, such as by performing data link layer encapsulation or decapsulation. In some implementations, the input component 305 can send and / or receive packets. In some implementations, the input component 305 can include an input line card, which includes one or more packet processing components (e.g., in the form of an integrated circuit), such as one or more interface cards (IFCs), packet forwarding components, line card controller components, input ports, processors, memory, and / or input queues. In some implementations, the device 300 may include one or more input components 305.

[0067] The switching component 310 can interconnect the input component 305 with the output component 315. In some implementations, the switching component 310 can be implemented via one or more crossbar switches, via a bus, and / or using a shared memory. The shared memory can act as a temporary buffer to store packets from the input component 305 before the packets are finally scheduled for delivery to the output component 315. In some implementations, the switching component 310 can enable the input component 305, the output component 315, and / or the controller 320 to communicate.

[0068] The output component 315 can store packets and can schedule packets for transmission on an output physical link. The output component 315 can support data link layer encapsulation or decapsulation and / or various high-level protocols. In some implementations, the output component 315 can send packets and / or receive packets. In some implementations, the output component 315 may include an output line card, which includes one or more packet processing components (e.g., in the form of an integrated circuit), such as one or more IFCs, packet forwarding components, line card controller components, output ports, processors, memories, and / or output queues. In some implementations, the device 300 may include one or more output components 315. In some implementations, the input component 305 and the output component 315 can be implemented by the same set of components (e.g., and the input / output component can be a combination of the input component 305 and the output component 315).

[0069] The controller 320 includes a processor in the form of a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and / or another type of processor or processing component. The processor is implemented in hardware, firmware, and / or a combination of software and hardware. In some implementations, the controller 320 may include one or more processors that can be programmed to perform a function.

[0070] In some implementations, the controller 320 may include random access memory (RAM), read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, optical memory, etc.) that stores information and / or instructions for use by the controller 320.

[0071] In some implementations, the controller 320 can communicate with other devices, networks, and / or systems connected to the device 300 to exchange information about the network topology. The controller 320 can create a routing table based on the network topology information, create a forwarding table based on the routing table, and forward the forwarding table to the input component 305 and / or the output component 315. The input component 305 and / or the output component 315 can use the forwarding table to perform a route lookup for incoming and / or outgoing packets. In some cases, the controller 320 can create a session table based on information determined when initializing a link failure detection session, and can forward the session table to the input component 305 and / or the output component 315.

[0072] The controller 320 may perform one or more processes described herein. The controller 320 may perform these processes in response to executing software instructions stored by a non-transient computer readable medium. A computer readable medium is defined herein as a non-transient memory device. A memory device includes memory space within a single physical memory device or memory space spread across multiple physical memory devices.

[0073] The software instructions may be read from another computer-readable medium or from another device into a memory and / or storage component associated with the controller 320 via a communication interface. When executed, the software instructions stored in the memory and / or storage component associated with the controller 320 may cause the controller 320 to perform one or more processes described herein. Additionally or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Thus, the implementations described herein are not limited to any specific combination of hardware circuitry and software.

[0074] Figure 3 The number and arrangement of components shown are provided as examples. Figure 3 The device 300 may include additional components, fewer components, different components, or components arranged differently than the components shown. Additionally or alternatively, a set of components (e.g., one or more components) of the device 300 may perform one or more functions described as being performed by another set of components of the device 300.

[0075] Figure 42 is a diagram of example components of device 400. Device 400 may correspond to client device 205, NSSF 220, NEF 225, AUSF 230, UDM 235, PCF 240, AF 245, AMF 250, AGF 255, SMF 260, and / or UPF 265. In some implementations, client device 205, NSSF 220, NEF 225, AUSF 230, UDM 235, PCF 240, AF 245, AMF 250, AGF 255, SMF 260, and / or UPF 265 may include one or more of device 400 and / or one or more components of device 400. Figure 4 As shown, device 400 may include a bus 410 , a processor 420 , a memory 430 , a storage component 440 , an input component 450 , an output component 460 , and a communication interface 470 .

[0076] The bus 410 includes components that allow communication between components of the device 400. The processor 420 is implemented in hardware, firmware, or a combination of hardware and software. The processor 420 is a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or another type of processing component. In some implementations, the processor 420 includes one or more processors that can be programmed to perform functions. The memory 430 includes a random access memory (RAM), a read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, and / or optical memory) that stores information and / or instructions for use by the processor 420.

[0077] Storage component 440 stores information and / or software related to the operation and use of device 400. For example, storage component 440 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optical disk, and / or a solid-state disk), a compact disk (CD), a digital versatile disk (DVD), a floppy disk, a cassette, a magnetic tape, and / or another type of non-transitory computer-readable medium and a corresponding drive.

[0078] Input components 450 include components that allow device 400 to receive information, such as via user input (e.g., a touch screen display, a keyboard, a keypad, a mouse, buttons, switches, and / or a microphone). Additionally or alternatively, input components 450 may include sensors for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, and / or an actuator). Output components 460 include components that provide output information from device 400 (e.g., a display, a speaker, and / or one or more light emitting diodes (LEDs)).

[0079] The communication interface 470 includes transceiver-like components (e.g., a transceiver and / or a separate receiver and transmitter) that enable the device 400 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of a wired and wireless connection. The communication interface 470 can allow the device 400 to receive information from another device and / or provide information to another device. For example, the communication interface 470 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, etc.

[0080] Device 400 may perform one or more processes described herein. Device 400 may perform these processes based on processor 420 executing software instructions stored by a non-transitory computer-readable medium, such as memory 430 and / or storage component 440.

[0081] The software instructions may be read into the memory 430 and / or storage component 440 from another computer-readable medium or from another device via the communication interface 470. When executed, the software instructions stored in the memory 430 and / or storage component 440 may cause the processor 420 to perform one or more processes described herein. Additionally or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Thus, the implementations described herein are not limited to any specific combination of hardware circuitry and software.

[0082] Figure 4 The number and arrangement of components shown are provided as examples. Figure 4 The device 400 may include additional components, fewer components, different components, or components arranged differently than the components shown. Additionally or alternatively, a set of components (e.g., one or more components) of the device 400 may perform one or more functions described as being performed by another set of components of the device 400.

[0083] Figure 5 is a flow chart of an example process 500 for carrying messages over wired access using a transport protocol of a 5G client device. In some implementations, Figure 5 One or more process blocks of can be performed by a device (e.g., client device 205). In some implementations, Figure 5 One or more process blocks of may be performed by another device or group of devices that is separate from or includes the device, such as one or more devices of a core network (eg, core network 215).

[0084] like Figure 5As shown, process 500 may include registering a device with a core network using Point-to-Point Protocol over Ethernet (PPPoE) and Point-to-Point Protocol (PPP) (block 510). For example, a device (e.g., using input component 305, switching component 310, output component 315, controller 320, processor 420, communication interface 470, etc.) may register a device with a core network using PPPoE and PPP, as described above.

[0085] like Figure 5 As further shown, process 500 may include establishing a first packet data unit (PDU) session with a core network based on PPPoE and PPP (block 520). For example, the device (e.g., using input component 305, switching component 310, output component 315, controller 320, processor 420, memory 430, communication interface 470, etc.) may establish a first PDU session with a core network based on PPPoE and PPP, as described above.

[0086] like Figure 5 As further shown, process 500 may include configuring a first PDU session with a core network based on PPPoE and PPP, wherein the first PDU session is configured to provide a first service (block 530). For example, a device (e.g., using input component 305, switching component 310, output component 315, controller 320, processor 420, storage component 440, communication interface 470, etc.) may configure a first PDU session with a core network based on PPPoE and PPP, as described above. In some implementations, the first PDU session may be configured to provide a first service.

[0087] like Figure 5 As further shown, process 500 may include generating a first keep-alive message to maintain a first PDU session with the core network (block 540). For example, the device (e.g., using switching component 310, output component 315, controller 320, processor 420, communication interface 470, etc.) may generate a first keep-alive message to maintain a first PDU session with the core network, as described above.

[0088] like Figure 5 As further shown, process 500 may include establishing a second PDU session with the core network based on PPPoE and PPP (block 550). For example, the device (e.g., using input component 305, switching component 310, output component 315, controller 320, processor 420, memory 430, communication interface 470, etc.) may establish a second PDU session with the core network based on PPPoE and PPP, as described above.

[0089] like Figure 5As further shown, process 500 may include configuring a second PDU session with the core network based on PPPoE and PPP, wherein the second PDU session is configured to provide a second service different from the first service (block 560). For example, the device (e.g., using input component 305, switching component 310, output component 315, controller 320, processor 420, storage component 440, communication interface 470, etc.) may configure a second PDU session with the core network based on PPPoE and PPP, as described above. In some implementations, the second PDU session is configured to provide a second service different from the first service.

[0090] like Figure 5 As further shown, process 500 may include generating a second keep-alive message to maintain a second PDU session with the core network (block 570). For example, the device (e.g., using switching component 310, output component 315, controller 320, processor 420, memory 430, communication interface 470, etc.) may generate a second keep-alive message to maintain a second PDU session with the core network, as described above.

[0091] Process 500 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in conjunction with one or more other processes described elsewhere herein.

[0092] In a first implementation, process 500 may include modifying one of the first PDU session or the second PDU session based on PPPoE and PPP.

[0093] In a second implementation, alone or in combination with the first implementation, modifying one of the first PDU session or the second PDU session may include: providing a PPP NAS PDU session modification request to the core network; receiving a PPP NAS PDU session modification command from the core network based on providing the PPP NAS PDU session modification request; modifying the first PDU session or the second PDU session based on executing the PPP NAS PDU session modification command; and providing a PPP NAS PDU session modification completion indication to the core network based on executing the PPP NAS PDU session modification command.

[0094] In a third implementation, alone or in combination with one or more of the first and second implementations, process 500 may include releasing one of the first PDU session or the second PDU session based on PPPoE and PPP.

[0095] In a fourth implementation, alone or in combination with one or more of the first to third implementations, process 500 may include releasing the first PDU session and the second PDU session after a period of time based on PPPoE and PPP; and deregistering the device from the core network based on releasing the first PDU session and the second PDU session.

[0096] In a fifth implementation, alone or in combination with one or more of the first to fourth implementations, releasing the first PDU session and the second PDU session may include: providing a PPP NAS first PDU session release request to the core network; receiving a PPP NAS first PDU session release command from the core network based on providing the PPP NAS first PDU session release request; releasing the first PDU session based on executing the PPP NAS first PDU session release command; providing a PPP NAS first PDU session release completion indication to the core network based on executing the PPP NAS first PDU session release command; providing a PPP NAS second PDU session release request to the core network; receiving a PPP NAS second PDU session release command from the core network based on providing the PPP NAS second PDU session release request; releasing the second PDU session based on executing the PPP NAS second PDU session release command; and providing a PPP NAS second PDU session release completion indication to the core network based on executing the PPP NAS second PDU session release command.

[0097] In a sixth implementation, alone or in combination with one or more of the first to fifth implementations, deregistering a device to a core network may include: providing a PPP NAS deregistration request to the core network; receiving a PPP NAS deregistration acceptance message from the core network based on providing the PPP NAS deregistration request; receiving another PPP NAS deregistration request from the core network; and providing another PPP NAS deregistration acceptance message to the core network based on receiving the other PPP NAS deregistration request.

[0098] although Figure 5 Example blocks of process 500 are shown, but in some implementations, Figure 5 Process 500 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently than those depicted. Additionally or alternatively, two or more blocks of process 500 may be performed in parallel.

[0099] Figure 6 is a flow chart of an example process 600 for carrying messages over wired access using a transport protocol of a 5G client device. In some implementations, Figure 6 One or more process blocks of can be performed by a device (e.g., client device 205). In some implementations, Figure 6One or more process blocks of may be performed by another device or group of devices that is separate from or includes the device, such as one or more devices of a core network (eg, core network 215).

[0100] like Figure 6 As shown, process 600 may include registering the device with the core network using PPPoE and PPP (block 610). For example, the device (e.g., using input component 305, switching component 310, output component 315, controller 320, processor 420, memory 430, communication interface 470, etc.) may register the device with the core network using PPPoE and PPP, as described above.

[0101] like Figure 6 As further shown, process 600 may include establishing a first PDU session with a core network based on PPPoE and PPP (block 620). For example, the device (e.g., using input component 305, switching component 310, output component 315, controller 320, processor 420, storage component 440, communication interface 470, etc.) may establish a first PDU session with a core network based on PPPoE and PPP, as described above.

[0102] like Figure 6 As further shown, process 600 may include configuring a first PDU session with a core network based on PPPoE and PPP, wherein the first PDU session is configured to provide a first service (block 630). For example, a device (e.g., using input component 305, switching component 310, output component 315, controller 320, processor 420, memory 430, communication interface 470, etc.) may establish a first PDU session with a core network based on PPPoE and PPP, as described above. In some implementations, the first PDU session is configured to provide a first service.

[0103] like Figure 6 As further shown, process 600 may include establishing a second PDU session with the core network based on PPPoE and PPP (block 640). For example, the device (e.g., using input component 305, switching component 310, output component 315, controller 320, processor 420, storage component 440, communication interface 470, etc.) may establish a second PDU session with the core network based on PPPoE and PPP, as described above.

[0104] like Figure 6As further shown, process 600 may include configuring a second PDU session with the core network based on PPPoE and PPP, wherein the second PDU session is configured to provide a second service different from the first service (block 650). For example, the device (e.g., using input component 305, switching component 310, output component 315, controller 320, processor 420, memory 430, storage component 440, communication interface 470, etc.) may configure a second PDU session with the core network based on PPPoE and PPP, as described above. In some implementations, the second PDU session is configured to provide a second service different from the first service.

[0105] Process 600 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in conjunction with one or more other processes described elsewhere herein.

[0106] In a first implementation, the device may include a residential gateway or user equipment.

[0107] In a second implementation, alone or in combination with the first implementation, registering a device with a core network using PPPoE and PPP may include: providing a PPP NAS registration request to the core network; receiving a PPP NAS downlink transmit identification request from the core network based on providing the PPP NAS registration request; providing a PPP NAS uplink transmit identification response to the core network based on the PPP NAS downlink transmit identification request, wherein the PPP NAS uplink transmit identification response includes an identification of the device; receiving a PPP NAS downlink transmit authentication request from the core network based on providing the PPP NAS uplink transmit identification response; providing a PPP NAS uplink transmit authentication response to the core network based on the PPP NAS downlink transmit authentication request, wherein the PPP NAS uplink transmit authentication response includes an authentication credential of the device; receiving a PPP NAS downlink transmit security mode command from the core network based on providing the PPP NAS uplink transmit authentication response; providing a PPP NAS uplink transmit indication of execution of the security mode command to the core network based on executing the PPP NAS downlink transmit security mode command; and providing a PPP NAS uplink transmit indication of execution of the security mode command based on providing the PPP NAS uplink transmit indication of execution of the security mode command. The NAS uplink transmits an indication to receive an indication from the core network that the device is registered with the core network.

[0108] In a third implementation, alone or in combination with one or more of the first implementation and the second implementation, establishing a first PDU session with the core network may include: providing a PPP NAS first PDU session establishment request to the core network; receiving a PPP NAS first PDU session accept message from the core network based on providing the PPP NAS first PDU session establishment request, wherein the PPPNAS first PDU session accept message includes a first session identifier for the first PDU session; establishing the first PDU session with the core network based on receiving the PPP NAS first PDU session accept message from the core network; and providing a PPP NAS first PDU session establishment completion indication to the core network based on establishing the first PDU session with the core network.

[0109] In a fourth implementation, alone or in combination with one or more of the first to third implementations, establishing a second PDU session with the core network may include: providing a PPP NAS second PDU session establishment request to the core network; receiving a PPP NAS second PDU session accept message from the core network based on providing the PPP NAS second PDU session establishment request, wherein the PPPNAS second PDU session accept message includes a second session identifier for the second PDU session; establishing a second PDU session with the core network based on receiving the PPP NAS second PDU session accept message from the core network; and providing a PPP NAS second PDU session establishment completion indication to the core network based on establishing the second PDU session with the core network.

[0110] In a fifth implementation, alone or in combination with one or more of the first to fourth implementations, process 600 may include: causing a first tunnel to be created in the core network based on establishing a first PDU session with the core network; and causing a second tunnel to be created in the core network based on establishing a second PDU session with the core network.

[0111] In a sixth implementation, alone or in combination with one or more of the first to fifth implementations, the core network may include a fifth generation core network.

[0112] although Figure 6 Example blocks of process 600 are shown, but in some implementations, Figure 6 Process 600 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently than those depicted. Additionally or alternatively, two or more blocks of process 600 may be performed in parallel.

[0113] Figure 7 is a flow chart of an example process 700 for carrying messages over wired access using a transport protocol of a 5G client device. In some implementations, Figure 7One or more process blocks of can be performed by a device (e.g., client device 205). In some implementations, Figure 7 One or more process blocks of may be performed by another device or group of devices that is separate from or includes the device, such as one or more devices of a core network (eg, core network 215).

[0114] like Figure 7 As shown, process 700 may include registering the device with the core network using PPPoE and PPP (block 710). For example, the device (e.g., using input component 305, switching component 310, output component 315, controller 320, processor 420, memory 430, communication interface 470, etc.) may register the device with the core network using PPPoE and PPP, as described above.

[0115] like Figure 7 As further shown, process 700 may include establishing a first PDU session with a core network based on PPPoE and PPP (block 720). For example, the device (e.g., using input component 305, switching component 310, output component 315, controller 320, processor 420, storage component 440, communication interface 470, etc.) may establish a first PDU session with a core network based on PPPoE and PPP, as described above.

[0116] like Figure 7 As further shown, process 700 may include configuring a first PDU session with a core network based on PPPoE and PPP, wherein the first PDU session is configured to provide a first service (block 730). For example, a device (e.g., using input component 305, switching component 310, output component 315, controller 320, processor 420, memory 430, storage component 440, communication interface 470, etc.) may configure a first PDU session with a core network based on PPPoE and PPP, as described above. In some implementations, the first PDU session is configured to provide a first service.

[0117] like Figure 7 As further shown, process 700 may include transmitting a first keep-alive message to maintain a first PDU session with the core network (block 740). For example, the device (e.g., using switching component 310, output component 315, controller 320, processor 420, memory 430, communication interface 470, etc.) may transmit a first keep-alive message to maintain a first PDU session with the core network, as described above.

[0118] Process 700 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in conjunction with one or more other processes described elsewhere herein.

[0119] In a first implementation, process 700 may include: establishing a second PDU session with the core network based on PPPoE and PPP; configuring the second PDU session with the core network based on PPPoE and PPP, wherein the second PDU session may be configured to provide a second service different from the first service; and transmitting a second keep-alive message to maintain the second PDU session with the core network.

[0120] In a second implementation, alone or in combination with the first implementation, process 700 may include modifying the first PDU session based on PPPoE and PPP.

[0121] In a third implementation, alone or in combination with one or more of the first and second implementations, process 700 may include: releasing the first PDU session after a period of time based on PPPoE and PPP; and deregistering the device from the core network based on releasing the first PDU session.

[0122] In a fourth implementation, alone or in combination with one or more of the first to third implementations, registering a device with a core network using PPPoE and PPP may include: providing a PPP NAS registration request to the core network; receiving a PPP NAS downlink transmission identification request from the core network based on providing the PPP NAS registration request; providing a PPP NAS uplink transmission identification response to the core network based on the PPP NAS downlink transmission identification request, wherein the PPP NAS uplink transmission identification response includes an identification of the device; receiving a PPP NAS downlink transmission authentication request from the core network based on providing the PPP NAS uplink transmission identification response; providing a PPP NAS uplink transmission authentication response to the core network based on the PPP NAS downlink transmission authentication request, wherein the PPP NAS uplink transmission authentication response includes an authentication credential of the device; receiving a PPP NAS downlink transmission security mode command from the core network based on providing the PPP NAS uplink transmission authentication response; providing a PPP NAS uplink transmission indication of execution of the security mode command to the core network based on executing the PPP NAS downlink transmission security mode command; and providing a PPP NAS uplink transmission indication of execution of the security mode command based on providing the PPP NAS uplink transmission indication of execution of the security mode command. The NAS uplink transmits an indication to receive an indication from the core network that the device is registered with the core network.

[0123] In a fifth implementation, alone or in combination with one or more of the first to fourth implementations, establishing a first PDU session with the core network may include: providing a PPP NAS first PDU session establishment request to the core network; receiving a PPP NAS first PDU session accept message from the core network based on providing the PPP NAS first PDU session establishment request, wherein the PPPNAS first PDU session accept message includes a first session identifier for the first PDU session; establishing the first PDU session with the core network based on receiving the PPP NAS first PDU session accept message from the core network; and providing a PPP NAS first PDU session establishment completion indication to the core network based on establishing the first PDU session with the core network.

[0124] although Figure 7 Example blocks of process 700 are shown, but in some implementations, Figure 7 Process 700 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently than those depicted. Additionally or alternatively, two or more blocks of process 700 may be performed in parallel.

[0125] According to some embodiments, the following examples are disclosed.

[0126] Example 1. A method, comprising: registering the device with a core network using Point-to-Point Protocol over Ethernet (PPPoE) and Point-to-Point Protocol (PPP); establishing a first packet data unit (PDU) session with the core network based on PPPoE and PPP by the device; configuring the first PDU session with the core network based on PPPoE and PPP by the device, wherein the first PDU session is configured to provide a first service; generating a first keep-alive message by the device to maintain the first PDU session with the core network; establishing a second PDU session with the core network based on PPPoE and PPP by the device; configuring a second PDU session with the core network based on PPPoE and PPP by the device, wherein the second PDU session is configured to provide a second service different from the first service; and generating a second keep-alive message by the device to maintain the second PDU session with the core network.

[0127] Example 2. The method according to Example 1, further comprising: modifying one of the first PDU session or the second PDU session based on PPPoE and PPP.

[0128] Example 3. A method according to Example 2, wherein modifying one of the first PDU session or the second PDU session includes: providing a PPP non-access stratum (NAS) PDU session modification request to a core network; receiving a PPP NAS PDU session modification command from the core network based on providing the PPP NAS PDU session modification request; modifying the first PDU session or the second PDU session based on executing the PPP NAS PDU session modification command; and providing a PPPNAS PDU session modification completion indication to the core network based on executing the PPP NAS PDU session modification command.

[0129] Example 4. The method according to Example 1, further comprising: releasing one of the first PDU session or the second PDU session based on PPPoE and PPP.

[0130] Example 5. The method according to Example 1 further includes: releasing the first PDU session and the second PDU session after a period of time based on PPPoE and PPP; and deregistering the device from the core network based on releasing the first PDU session and the second PDU session.

[0131] Example 6. A method according to Example 5, wherein releasing the first PDU session and the second PDU session includes: providing a PPP non-access stratum (NAS) first PDU session release request to a core network; receiving a PPP NAS first PDU session release command from the core network based on providing the PPP NAS first PDU session release request; releasing the first PDU session based on executing the PPP NAS first PDU session release command; providing a PPP NAS first PDU session release completion indication to the core network based on executing the PPP NAS first PDU session release command; providing a PPP NAS second PDU session release request to the core network; receiving a PPP NAS second PDU session release command from the core network based on providing the PPP NAS second PDU session release request; releasing the second PDU session based on executing the PPP NAS second PDU session release command; and providing a PPP NAS second PDU session release completion indication to the core network based on executing the PPP NAS second PDU session release command.

[0132] Example 7. A method according to Example 5, wherein deregistering a device to a core network includes: providing a PPP non-access stratum (NAS) deregistration request to the core network; receiving a PPP NAS deregistration acceptance message from the core network based on providing the PPP NAS deregistration request; receiving another PPP NAS deregistration request from the core network; and providing another PPP NAS deregistration acceptance message to the core network based on receiving the other PPP NAS deregistration request.

[0133] Example 8. A device comprising: one or more memories; and one or more processors, for: registering the device with a core network using Point-to-Point Protocol over Ethernet (PPPoE) and Point-to-Point Protocol (PPP); establishing a first packet data unit (PDU) session with the core network based on PPPoE and PPP; configuring a first PDU session with the core network based on PPPoE and PPP, wherein the first PDU session is configured to provide a first service; establishing a second PDU session with the core network based on PPPoE and PPP; and configuring a second PDU session with the core network based on PPPoE and PPP, wherein the second PDU session is configured to provide a second service different from the first service.

[0134] Example 9. The device according to Example 8, wherein the device comprises one of the following: a residential gateway, or a user equipment.

[0135] Example 10. A device according to Example 8, wherein when registering the device with a core network using PPPoE and PPP, one or more processors are used to: provide a PPP non-access stratum (NAS) registration request to the core network; receive a PPP NAS downlink transmission identification request from the core network based on providing the PPP NAS registration request; provide a PPP NAS uplink transmission identification response to the core network based on the PPP NAS downlink transmission identification request, wherein the PPP NAS uplink transmission identification response includes an identification of the device; receive a PPP NAS downlink transmission authentication request from the core network based on providing the PPP NAS uplink transmission identification response; provide a PPP NAS uplink transmission authentication response to the core network based on the PPP NAS downlink transmission authentication request, wherein the PPP NAS uplink transmission authentication response includes an authentication credential of the device; receive a PPP NAS downlink transmission security mode command from the core network based on providing the PPPNAS uplink transmission authentication response; provide a PPP NAS uplink transmission indication of execution of the security mode command to the core network based on executing the PPP NAS downlink transmission security mode command; and provide a PPP NAS uplink transmission indication of execution of the security mode command based on providing the PPP NAS uplink transmission indication of execution of the security mode command. The NAS uplink transmits an indication to receive an indication from the core network that the device is registered with the core network.

[0136] Example 11. A device according to Example 8, wherein when establishing a first PDU session with a core network, one or more processors are used to: provide a PPP non-access stratum (NAS) first PDU session establishment request to the core network; receive a PPP NAS first PDU session accept message from the core network based on providing the PPP NAS first PDU session establishment request, wherein the PPP NAS first PDU session accept message includes a first session identifier for the first PDU session; establish the first PDU session with the core network based on receiving the PPPNAS first PDU session accept message from the core network; and provide a PPP NAS first PDU session establishment completion indication to the core network based on establishing the first PDU session with the core network.

[0137] Example 12. A device according to Example 8, wherein when establishing a second PDU session with a core network, one or more processors are used to: provide a PPP non-access stratum (NAS) second PDU session establishment request to the core network; receive a PPP NAS second PDU session accept message from the core network based on providing the PPP NAS second PDU session establishment request, wherein the PPP NAS second PDU session accept message includes a second session identifier for the second PDU session; establish a second PDU session with the core network based on receiving the PPPNAS second PDU session accept message from the core network; and provide a PPP NAS second PDU session establishment completion indication to the core network based on establishing the second PDU session with the core network.

[0138] Example 13. A device according to Example 8, wherein the one or more processors are further configured to: cause a first tunnel to be created in the core network based on establishing a first PDU session with the core network; and cause a second tunnel to be created in the core network based on establishing a second PDU session with the core network.

[0139] Example 14. The apparatus of Example 8, wherein the core network comprises a fifth generation core network.

[0140] Example 15. A non-transitory computer-readable medium storing instructions, the instructions comprising: one or more instructions, which, when executed by one or more processors of a device, cause the one or more processors to: register the device with a core network using Point-to-Point Protocol over Ethernet (PPPoE) and Point-to-Point Protocol (PPP); establish a first packet data unit (PDU) session with the core network based on PPPoE and PPP; configure a first PDU session with the core network based on PPPoE and PPP, wherein the first PDU session is configured to provide a first service; and transmit a first keep-alive message to maintain the first PDU session with the core network.

[0141] Example 16. A non-transitory computer-readable medium according to Example 15, wherein the instructions further include: one or more instructions, which when executed by one or more processors cause the one or more processors to: establish a second PDU session with the core network based on PPPoE and PPP; configure a second PDU session with the core network based on PPPoE and PPP, wherein the second PDU session is configured to provide a second service different from the first service; and transmit a second keep-alive message to maintain the second PDU session with the core network.

[0142] Example 17. The non-transitory computer readable medium of Example 15, wherein the instructions further comprise: one or more instructions that, when executed by the one or more processors, cause the one or more processors to: modify the first PDU session based on PPPoE and PPP.

[0143] Example 18. A non-transitory computer-readable medium according to Example 15, wherein the instructions further include: one or more instructions, which when executed by one or more processors cause the one or more processors to: release a first PDU session after a period of time based on PPPoE and PPP; and deregister the device from the core network based on releasing the first PDU session.

[0144] Example 19. A non-transitory computer-readable medium according to Example 15, wherein one or more instructions that cause one or more processors to register a device with a core network using PPPoE and PPP cause the one or more processors to: provide a PPP non-access stratum (NAS) registration request to the core network; receive a PPP NAS downlink transmit identification request from the core network based on providing the PPP NAS registration request; provide a PPP NAS uplink transmit identification response to the core network based on the PPP NAS downlink transmit identification request, wherein the PPP NAS uplink transmit identification response includes an identification of the device; receive a PPP NAS downlink transmit authentication request from the core network based on providing the PPP NAS uplink transmit identification response; provide a PPP NAS uplink transmit authentication response to the core network based on the PPP NAS downlink transmit authentication request, wherein the PPP NAS uplink transmit authentication response includes an authentication credential of the device; receive a PPP NAS downlink transmit security mode command from the core network based on providing the PPP NAS uplink transmit authentication response; provide a PPP NAS uplink transmit indication of execution of the security mode command to the core network based on executing the PPP NAS downlink transmit security mode command; and provide a PPP NAS uplink transmit indication of execution of the security mode command to the core network based on providing the PPP NAS uplink transmit authentication response. The NAS uplink transmits an indication to receive an indication from the core network that the device is registered with the core network.

[0145] Example 20. A non-transitory computer-readable medium according to Example 15, wherein one or more instructions that cause one or more processors to establish a first PDU session with a core network cause the one or more processors to: provide a PPP non-access stratum (NAS) first PDU session establishment request to the core network; receive a PPP NAS first PDU session accept message from the core network based on providing the PPP NAS first PDU session establishment request, wherein the PPP NAS first PDU session accept message includes a first session identifier for the first PDU session; establish the first PDU session with the core network based on receiving the PPP NAS first PDU session accept message from the core network; and provide a PPP NAS first PDU session establishment completion indication to the core network based on establishing the first PDU session with the core network.

[0146] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the implementations.

[0147] As used herein, the term "component" is intended to be broadly interpreted as hardware, firmware, or a combination of hardware and software.

[0148] It will be apparent that the systems and / or methods described herein can be implemented in various forms of hardware, firmware, or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit the implementation. Therefore, the operation and behavior of the systems and / or methods are described herein without reference to specific software code—it is understood that software and hardware can be designed to implement the systems and / or methods based on the description herein.

[0149] Even though particular combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the various implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of the various implementations includes each dependent claim in combination with every other claim in the claim set.

[0150] Unless explicitly described in this way, the elements, actions or instructions used herein should not be interpreted as key or necessary. Moreover, as used herein, the articles "one" and "an" are intended to include one or more projects, and can be used interchangeably with "one or more". Further, as used herein, the article "the" is intended to include one or more projects quoted in conjunction with the article "the", and can be used interchangeably with "one or more". In addition, as used herein, the term "set" is intended to include one or more projects (such as related projects, unrelated projects, combinations of related projects and unrelated projects, etc.), and can be used interchangeably with "one or more". In the case of only one project, phrases "only one" or similar language are used. Moreover, as used herein, the terms "have (has)", "have (have)", "have (having)" etc. are intended to be open terms. Further, unless otherwise expressly provided, the phrase "based on" is intended to represent "based at least in part". Furthermore, as used herein, the term "or" when used in tandem is intended to be inclusive and may be used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in combination with "either" or "only one of...").

Claims

1. A method comprising: The device establishes a first packet data unit (PDU) session with the core network, wherein the first PDU session is configured to provide a first service; establishing, by the device, a second PDU session with the core network during the first PDU session, wherein the second PDU session is configured to provide a second service different from the first service; as well as A message is transmitted by the device to maintain the second PDU session with the core network.

2. The method according to claim 1, further comprising: A message is transmitted to maintain the first PDU session.

3. The method according to claim 1, further comprising: receiving a PDU session modification command from the core network; as well as The PDU session modification command is executed to: modify the first PDU session, or Modify the second PDU session.

4. The method according to claim 1, further comprising: A first General Packet Radio Service (GPRS) Tunneling Protocol (GTP) tunnel is established for the first PDU session.

5. The method according to claim 1, further comprising: releasing the first PDU session; as well as The device is deregistered from the core network based on releasing the first PDU session.

6. The method according to claim 1, further comprising: Provide a deregistration request; as well as A deregistration accept message is received based on providing the deregistration request.

7. The method of claim 1 , wherein establishing the first PDU session with the core network comprises: The first PDU session is established with the core network based on a transport protocol.

8. A device comprising: one or more memories; as well as One or more processors to: Establishing a first packet data unit (PDU) session with a core network; establishing a second PDU session with the core network during the first PDU session, wherein the second PDU session is configured to provide a second service different from the first service provided by the first PDU session; as well as A message is transmitted to maintain the second PDU session with the core network.

9. The apparatus of claim 8, wherein the one or more processors are further configured to: The device is registered with the core network using Point-to-Point Protocol (PPPoE).

10. The apparatus of claim 8, wherein the one or more processors are further configured to: The device is registered with the core network using the Point-to-Point Protocol (PPP).

11. The apparatus of claim 8, wherein the one or more processors, when establishing the first PDU session with the core network, are configured to: establishing the first PDU session based on receiving a first PDU session accept message from the core network; and A first PDU session establishment completion indication is provided based on establishing the first PDU session.

12. The apparatus of claim 8, wherein the one or more processors are further configured to: A message is generated to maintain the first PDU session.

13. The apparatus of claim 8, wherein the one or more processors are further configured to: releasing the first PDU session; and The device is deregistered based on releasing the first PDU session.

14. The apparatus of claim 8, wherein the one or more processors are further configured to: causing a first tunnel to be created in the core network based on establishing the first PDU session; and A second tunnel is caused to be created in the core network based on establishing the second PDU session.

15. A non-transitory computer-readable medium storing instructions, the instructions comprising: One or more instructions that, when executed by one or more processors of a device, cause the one or more processors to: Establishing a first packet data unit (PDU) session with a core network; transmitting a first message to maintain the first PDU session; establishing a second PDU session with the core network during the first PDU session; as well as A second message is transmitted to maintain the second PDU session.

16. The non-transitory computer readable medium of claim 15, wherein the instructions further comprise: one or more instructions that, when executed by the one or more processors, cause the one or more processors to: Releasing the first PDU session: and The device is deregistered from the core network based on releasing the first PDU session.

17. The non-transitory computer readable medium of claim 15, wherein the instructions further comprise: one or more instructions that, when executed by the one or more processors, cause the one or more processors to: The first PDU session is modified based on a transport protocol.

18. The non-transitory computer-readable medium of claim 15, wherein the device comprises a residential gateway or a user equipment.

19. The non-transitory computer-readable medium of claim 15, wherein the first PDU session and the second PDU session are each configured to provide a service.

20. The non-transitory computer readable medium of claim 15, wherein the instructions further comprise: one or more instructions that, when executed by the one or more processors, cause the one or more processors to: A transport protocol is utilized to carry messages via wired access to the core network.

Images