WO2018214831A1 - 一种注册方法及装置 - Google Patents

一种注册方法及装置 Download PDF

Info

Publication number
WO2018214831A1
WO2018214831A1 PCT/CN2018/087590 CN2018087590W WO2018214831A1 WO 2018214831 A1 WO2018214831 A1 WO 2018214831A1 CN 2018087590 W CN2018087590 W CN 2018087590W WO 2018214831 A1 WO2018214831 A1 WO 2018214831A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
nas
fixed network
terminal device
access device
Prior art date
Application number
PCT/CN2018/087590
Other languages
English (en)
French (fr)
Inventor
李汉成
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2018214831A1 publication Critical patent/WO2018214831A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration

Definitions

  • the present application relates to the field of mobile communications technologies, and in particular, to a registration method and apparatus.
  • the terminal device accesses the access network (AN) through the fixed network, and then accesses the core network through the access device.
  • AN access network
  • the process of registering a terminal device to the access network and the core network is: the terminal device first creates and accesses a data channel between the devices, for example, completing the fixed network protocol as an Ethernet-based point-to-point protocol (English: Point To Point Protocol over Ethernet (PPPoE) registration, or complete the Dynamic Host Configuration Protocol (DHCP) registration in the Internet Protocol over Ethernet (IPoE) protocol.
  • the data channel delivers Network Attached Storage (NAS) messages to the access device to complete the registration process to the core network.
  • NAS Network Attached Storage
  • the main problems are: first, the registration process takes a long time; second It needs to occupy a proprietary data channel for delivering NAS messages, resulting in lower data channel usage.
  • the present application provides a registration method and apparatus for reducing the time when a terminal device registers with an access network and a core network, and improving resource utilization.
  • the application provides a registration method, including:
  • the access device receives the first fixed network message from the terminal device, where the first fixed network message includes a first non-access stratum NAS message, the first NAS message is used to request registration to the core network; and the access device is to the core
  • the network control plane CP device sends the first NAS message; the access device receives a NAS registration complete message from the CP device, and sends a second fixed network message to the terminal device, where the second fixed network message includes The second NAS message is used to indicate that the core network registration has been completed.
  • the terminal device in the process of registering to the access network, the terminal device also uses the NAS message for requesting registration to the core network to be carried in the fixed network message and sent to the access device, so as to simultaneously register the core network, and
  • the network message indicates that the registration of the core network is completed, and the registration of the fixed network and the core network is implemented in parallel, which reduces the time for the terminal device to register to the access network and the core network, and at the same time, because the NAS message is carried in the fixed network message, No additional dedicated data channels are required to deliver NAS messages, increasing resource usage.
  • the access device records a correspondence, where the correspondence is a user identifier of the terminal device, and/or a correspondence between an Ethernet-based point-to-point protocol PPPoE session identifier and a first interface
  • the PPPoE session identifier is allocated by the access device to the terminal device
  • the first interface is an interface between the access device and a functional unit for implementing access and mobility management.
  • the functional unit for implementing access and mobility management may be, for example, an Access and Mobility Management Function (AMF) network element.
  • AMF Access and Mobility Management Function
  • the first interface may have other naming methods. For example, it may also be referred to as an N2 interface, an NG2 interface, etc. As the communication evolves, the first interface may have other names in future communications, which is not limited in this application.
  • the access device may send the NAS message from the terminal device to the CP device of the core network through the corresponding first interface, and correspondingly, the access device receives the first interface.
  • the corresponding user identifier or PPPoE session identifier is determined, and the NAS message is sent to the corresponding terminal device.
  • the access device sends the first NAS message to the CP device, including: the access device determines the first interface according to the obtained user identifier, and/or the PPPoE session identifier, and the corresponding relationship; Sending a first NAS message to the CP device through the determined first interface. In this way, the access device can send the first NAS message to the CP device through the corresponding first interface.
  • the access device sends the second fixed network message to the terminal device, including: the access device according to the receiving NAS registration completion message.
  • An interface, and a corresponding relationship determine a PPPoE session identifier, and then the access device sends a second fixed network message to the terminal device corresponding to the PPPoE session identifier. In this way, the access device can send the second fixed network message to the corresponding terminal device.
  • the first interface, or the corresponding relationship is the correspondence between the user identifier and the first interface;
  • the first interface of the NAS registration completion message and the corresponding relationship determine the user identifier, and then the access device sends the second fixed network message to the terminal device corresponding to the user identifier. In this way, the access device can send the second fixed network message to the corresponding terminal device to ensure the accuracy of sending the fixed network message.
  • the first fixed network message is a PPPoE active discovery start PADI message
  • the second fixed network message provides a PADO message or a PPPoE active discovery session confirmation PADS message for PPPoE active discovery
  • the first fixed network message A PADR message is requested for PPPoE active discovery
  • the second fixed network message is a PADS message.
  • the access device sends a PADO message to the terminal device, the PADO message includes a NAS authentication request message, the access device receives the PADR message sent by the terminal device, and the PADR message includes the NAS authentication information, and the access device The CP device sends the NAS authentication information. In this way, the authentication process for the terminal device can be completed.
  • the access device receives the first request message from the terminal device, where the first request message is used to request the access device to support the capability of the NAS, and the access device sends the first response message to the terminal device,
  • the first response message is used to determine that the access device supports the NAS.
  • the access device can notify the terminal device of the capabilities of the NAS supported by the access device, for example, the access device supports the NAS or does not support the NAS.
  • the first request message is carried in the PADI message and sent to the access device, where the first response message is carried in the PADO message and sent to the terminal device.
  • the access device receives a second request message from the terminal device, the second request message is used to request the NAS user identity, and the access device sends a second response message to the terminal device, where the second response message is used.
  • the second request message Indicates the NAS user ID of the terminal device.
  • the second request message is carried in the PADI message and sent to the access device, where the second response message is carried in the PADO message or the PADS message and sent to the terminal device; or the second request message is carried in the PADR message.
  • the second response message sent to the access device is carried in the PADS message and sent to the terminal device.
  • the access device receives the third fixed network message from the terminal device, where the third fixed network message includes a PDU session creation request message, and the PDU session creation request message is used to request to create a PDU session;
  • the CP device sends a PDU session creation request message;
  • the access device receives a PDU session creation request response message from the CP device for the PDU session creation request message;
  • the access device sends a fourth fixed network message to the terminal device, and the fourth fixed network message
  • the PDU session creation request response message is included. In this way, the creation of a PDU session can be completed.
  • the fourth NAS message further includes an IP parameter, and the IP parameter is used by the terminal device as a PPPoE IP parameter.
  • the access device receives the fifth fixed network message from the terminal device, the fifth fixed network message includes an LCP configuration request message, and the access device sends an IPCP message to the terminal device, where the IPCP message includes the CP device as the terminal. IP parameters assigned by the device.
  • the first fixed network message further includes a PDU session creation request message
  • the PDU session creation request message is used to request to create a PDU session
  • the second fixed network message further includes a PDU session creation for the PDU session creation request message.
  • the response message is requested, and the access device sends the PDU session creation request message to the CP device, and the access device receives the PDU session creation request response message from the CP device. In this way, the PDU session can be created in the process of completing the registration of the fixed network and the core network in parallel.
  • the first fixed network message is a DHCP discovery message
  • the second fixed network message is a DHCP providing message or a DHCP acknowledgement message
  • the first fixed network message is a DHCP request message
  • the second fixed network message is Confirm the message for DHCP. That is, the present application is also applicable to parallel registration to the fixed network and the core network using the IPoE protocol.
  • the application provides a registration method, including:
  • the terminal device sends a first fixed network message to the access device, where the first fixed network message includes a first non-access stratum NAS message, the first NAS message is used to request registration to the core network, and the terminal device receives the second from the access device.
  • the fixed network message includes a second NAS message, and the second NAS message is used to indicate that the core network registration has been completed.
  • the terminal device in the process of registering to the access network, the terminal device also uses the NAS message for requesting registration to the core network to be carried in the fixed network message and sent to the access device, so as to simultaneously register the core network, and
  • the network message indicates that the registration of the core network is completed, and the registration of the fixed network and the core network is implemented in parallel, which reduces the time for the terminal device to register to the access network and the core network, and at the same time, because the NAS message is carried in the fixed network message, No additional dedicated data channels are required to deliver NAS messages, increasing resource usage.
  • the first fixed network message is a PADI message
  • the second fixed network message is a PADO message or a PADS message
  • the first fixed network message is a PADR message
  • the second fixed network message is a PADS message.
  • the terminal device receives the PADO message sent by the access device, and the PADO message includes the NAS authentication request message; the terminal device sends the PADR message to the access device, where the PADR message includes the NAS authentication information. In this way, the authentication process for the terminal device can be completed.
  • the terminal device sends a first request message to the access device, where the first request message is used to request the access device to support the NAS; the terminal device receives the first response message from the access device, the first The response message is used to indicate that the access device supports the NAS.
  • the access device can notify the terminal device of the capabilities of the NAS supported by the access device, for example, the access device supports the NAS or does not support the NAS.
  • the first request message is carried in the PADI message and sent to the access device, where the first response message is carried in the PADO message and sent to the terminal device.
  • the terminal device sends a second request message to the access device, the second request message is used to request the NAS user identifier, the terminal device receives the second response message from the access device, and the second response message is used. Indicates the NAS user ID of the terminal device.
  • the second request message is carried in the PADI message and sent to the access device, where the second response message is carried in the PADO message or the PADS message and sent to the terminal device; or the second request message is carried in the PADR message.
  • the second response message sent to the access device is carried in the PADS message and sent to the terminal device.
  • the terminal device sends a third fixed network message to the access device, where the third fixed network message includes a PDU session creation request message, the PDU session creation request message is used to request to create a PDU session, and the terminal device receives the connection.
  • the fourth fixed network message of the incoming device, the fourth fixed network message includes a PDU session creation request response message for the PDU session creation request message. In this way, the creation of a PDU session can be completed.
  • the terminal device sends a fifth fixed network message to the access device, where the fifth fixed network message includes an LCP configuration request message; the terminal device receives the IPCP message from the access device, and the IPCP message includes the CP device as the terminal. IP parameters assigned by the device. In this way, the IP parameters allocated by the CP device can be sent to the terminal device during the PPPoE session.
  • the fourth NAS message further includes an IP parameter, and the IP parameter is used by the terminal device as a PPPoE IP parameter.
  • the PPPoE session process can be cancelled, and the IP parameters to be allocated for the terminal device can also be sent to the terminal device.
  • the first fixed network message further includes a PDU session creation request message
  • the PDU session creation request message is used to request to create a PDU session
  • the second fixed network message further includes a PDU session creation for the PDU session creation request message. Request a reply message.
  • the first fixed network message is a DHCP discovery message
  • the second fixed network message is a DHCP providing message or a DHCP acknowledgement message
  • the first fixed network message is a DHCP request message
  • the second fixed network message is a DHCP request message. Confirm the message. That is, the present application is also applicable to parallel registration to the fixed network and the core network using the IPoE protocol.
  • the embodiment of the present application provides a registration device, which may be, for example, an access device, or a chip built in an access device or independent of an access device, where the access device refers to
  • the device that enters the core network may be, for example, a base station, a Broadband Network Gateway (BNG), an aggregation switch, a non-3GPP access device, etc., and the registration device has the function of implementing the access device in the foregoing method example.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • an embodiment of the present invention provides a registration apparatus, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor is connected to the memory through the bus, when the device In operation, the processor executes the computer-executable instructions stored by the memory to cause the registration device to perform the registration method of any of the first aspects above.
  • the embodiment of the present application provides a registration device, which may be, for example, a terminal device, or may be a chip built in or independent of a terminal device, and the registration device has a function of implementing the behavior of the terminal device in the foregoing method example.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • an embodiment of the present invention provides a registration apparatus, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor is connected to the memory through the bus, when the device In operation, the processor executes the computer-executed instructions stored by the memory to cause the registration device to perform the registration method of any of the second aspects above.
  • the embodiment of the present application provides a computer storage medium for storing computer software instructions used by the access device of the foregoing aspects, which includes a program designed to perform the foregoing aspects for an access device.
  • the embodiment of the present application provides a computer storage medium for storing computer software instructions used by the terminal device in the foregoing aspects, which includes a program designed to execute the foregoing aspects for the terminal device.
  • the present application also provides a computer program product.
  • the computer program product includes computer software instructions executable by a processor to implement the processes in the registration method of any of the above first aspects.
  • the application also provides a computer program product.
  • the computer program product includes computer software instructions executable by a processor to implement the processes in the registration method of any of the above second aspects.
  • FIG. 1 is a schematic diagram of an application scenario provided by the present application
  • FIG. 3 is a flowchart of another registration method provided by the present application.
  • FIG. 5 is a flowchart of another registration method provided by the present application.
  • FIG. 6 is a flowchart of another registration method provided by the present application.
  • FIG. 7 is a flowchart of another registration method provided by the present application.
  • FIG. 8 is a flowchart of another registration method provided by the present application.
  • FIG. 9 is a schematic diagram of a registration device provided by the present application.
  • FIG. 10 is a schematic diagram of a registration device provided by the present application.
  • FIG. 11 is a schematic diagram of a registration device provided by the present application.
  • the embodiment of the present application provides a registration method and a registration device based on the method, such as an access device, a terminal device, and the like, to reduce the time for the terminal device to register to the access network and the core network, and to improve the resource usage rate.
  • the method and the device are based on the same inventive concept. Since the principles of the method and the device for solving the problem are similar, the implementation of the device and the method can be referred to each other, and the repeated description is not repeated.
  • the NAS device that is used to request registration to the core network is carried in the fixed network message and sent to the access device, so as to simultaneously register the core network and
  • the network message indicates that the registration of the core network is completed, and the registration of the fixed network and the core network is implemented in parallel, which reduces the time for the terminal device to register to the access network and the core network, and at the same time, because the NAS message is carried in the fixed network message, No additional dedicated data channels are required to deliver NAS messages, increasing resource usage.
  • FIG. 1 it is a possible system architecture diagram of the present application, including an access device 10 and a Control Plane (CP) device 20, and the terminal device communicates with the access device 10 through a wired connection.
  • the access device 10 is connected to a core network (CN).
  • the devices in the core network can be divided into a Control Plane (CP) device 20 and a User Plane (UP) device.
  • the control plane device can also be called To control the surface network element, the user plane device may also be referred to as a user plane network element.
  • the communication interface between the access device 10 and the CP device 20 is referred to as a first interface.
  • the first interface may also have other naming manners, for example, an N2 interface, an NG2 interface, etc.
  • the evolution of communication, in the future communication, the first interface can also have other names, this application is not limited.
  • control plane device and the user plane device are only one name, and the name itself does not limit the device.
  • control plane device may also be replaced with a "control plane entity” or other name.
  • control plane device may also correspond to an entity including other functions in addition to the control plane function.
  • user plane device may also be replaced with a "user plane entity” or other name, and the user plane device may also correspond to an entity including other functions in addition to the user plane function.
  • control plane device mainly includes a functional unit for implementing access and mobility management, such as an AMF network element, and includes a functional unit for implementing session management, such as a Session Management Function (SMF) network.
  • the element includes a functional unit for implementing an authentication server, such as an Authentication Server Function (AUSF) network element, and includes a functional unit for implementing user data management, such as User Data Management (UDM). Network element, and so on.
  • AUSF Authentication Server Function
  • UDM User Data Management
  • Terminal equipment mainly refers to fixed terminals, including, for example, a Digital Subscriber Line (DSL) modem, a pon terminal, a cable modem, and the like.
  • DSL Digital Subscriber Line
  • the access device refers to a device that accesses the core network, and may be, for example, a base station, a BNG, an aggregation switch, a non-3GPP access device, etc., wherein when the access device is a base station, the base station specifically includes but is not limited to: an evolved type.
  • Node B evolved Node B, eNB
  • radio network controller RNC
  • Node B Node B, NB
  • Base Station Controller BSC
  • Base Transceiver Station Base Transceiver Station, BTS
  • home base station for example, Home evolved NodeB, or Home Node B, HNB
  • Baseband Unit BBU
  • new air interface base station g NodeB, gNB
  • transmission point Transmitting and receiving point
  • TRP Transmitting and receiving point
  • TP Transmitting point
  • mobile switching center etc.
  • the network architecture described in the embodiments of the present application is for the purpose of more clearly illustrating the technical solutions of the embodiments of the present application, and does not constitute a limitation of the technical solutions provided by the embodiments of the present application. As those skilled in the art may understand, with the evolution of the network architecture, The technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.
  • a flowchart of a registration method includes the following steps:
  • Step 201 The terminal device sends a first fixed network message to the access device, where the access device receives the first fixed network message.
  • the first NAS message includes a first NAS message, and the first NAS message may also be referred to as a NAS registration request message or a registration request message, etc., and the first NAS message is used to request registration to the core network.
  • Step 202 The access device sends a first NAS message to the CP device of the core network, and the CP device receives the first NAS message.
  • the access device After receiving the first fixed network message sent by the terminal device, the access device sends a first NAS message to the CP device, where the first NAS message is used to request registration to the core network from the CP device.
  • Step 203 The CP device sends a NAS registration completion message to the access device, and the access device receives the NAS registration completion message.
  • Step 204 The access device sends a second fixed network message to the terminal device, where the terminal device receives the second fixed network message.
  • the access device After receiving the NAS registration completion message sent by the CP device, the access device sends a second fixed network message to the terminal device, where the second fixed network message includes a second NAS message, where the second NAS message is used to indicate that the core network registration is completed.
  • step 203 is replaced by the step 203 (a)
  • the second NAS message included in the second fixed network message sent in the step 204 is replaced by another NAS message to indicate that the core network registration fails.
  • the terminal device in the process of registering to the access network, the terminal device also uses the NAS message for requesting registration to the core network to be carried in the fixed network message and sent to the access device, so as to simultaneously register the core network, and
  • the network message indicates that the registration of the core network is completed, and the registration of the fixed network and the core network is implemented in parallel, which reduces the time for the terminal device to register to the access network and the core network, and at the same time, because the NAS message is carried in the fixed network message, No additional dedicated data channels are required to deliver NAS messages, increasing resource usage.
  • the interaction between the terminal device and the access device is performed by the fixed network message, and the fixed network message includes the NAS message.
  • the NAS message may be transmitted through the vendor customized information of the fixed network message.
  • the fixed network registration is performed by using the PPPoE protocol
  • the fixed network message is a message during the PPPoE session, for example, the vendor-defined information in the Link Control Protocol (LCP) packet of the PPPoE session process can be used.
  • the NAS message is transmitted, that is, the LCP message is a fixed network message, where the vendor customized information carries the NAS message, such as the first NAS message and the second NAS message; similarly, the PPPoE of the PPPoE discovery process can also be used.
  • LCP Link Control Protocol
  • the vendor-defined information in the packet is used to deliver the NAS message.
  • the option of the custom type is added to the PPPoE packet to transmit the NAS message.
  • the PPPoE packet in the PPPoE discovery process is a fixed network message.
  • the vendor customization information carries a NAS message, such as the first NAS message and the second NAS message.
  • a PPPoE-like manner can be adopted for a terminal device that accesses the core network through the IPoE protocol.
  • a PPPoE-like manner can be adopted.
  • the core network registration is completed, and correspondingly, in the vendor-defined message of the DHCP message. Carry NAS messages.
  • the process of registering the parallel registration to the fixed network (ie, the access network) and the core network in the foregoing steps 201-204 may be completed in different stages based on the PPPoE protocol, for example, in the PPPoE discovery process, or The PPPoE session process is completed, either at different stages based on IPoE, or at different stages in future new protocols, such as defining a new registration to fixed network protocol.
  • This application can be based on new The protocol completes the process of parallel registration of terminal devices to the fixed network and the core network.
  • the access device communicates with the CP device of the core network through the first interface
  • the first interface may be, for example, an N2 interface, an NG2 interface, etc., and is accessed for different terminal devices or for different session identifiers.
  • the device will communicate with the CP device by using different first interfaces. Therefore, the registration process shown in FIG. 2(a) of the present application further includes establishing a correspondence between the user identifier and/or the session identifier and the first interface.
  • the corresponding relationship between the user identifier and the first interface is first established, where the user identifier can uniquely identify a terminal device, and the user identifier can be, for example, the terminal.
  • Link information may exist in the form of a table, or in the form of a formula, or The chart mode exists, etc., and the corresponding relationship will be described in the form of a table, for example, the established correspondence is as shown in Table 1.
  • the PPPoE session identifier may be added to the foregoing Table 1. In one possible manner, the added PPPoE session identifier is changed.
  • the first interface corresponding to the user identifier is shown in Table 2.
  • the first interface corresponding to the other session may be different from the first interface corresponding to session 1 of the terminal device, for example, as shown in Table 3.
  • the PPPoE session identifier is added on the basis of Table 1, and the result as shown in Table 4 is obtained.
  • the first interface corresponding to the other session is the same as the first interface corresponding to the session 1 of the terminal device, as shown in Table 5.
  • the access device allocates a PPPoE session identifier to the terminal device, and the access device further allocates the first interface based on the user identifier of the terminal device, and establishes a correspondence relationship.
  • the corresponding relationship is established according to the PPPoE session identifier. For example, when the PPPoE session identifiers of different terminal devices are different from each other, that is, the PPPoE session identifier in the network is unique, the correspondence between the PPPoE session identifier and the first interface can be directly established.
  • the correspondence between the two information of the user identifier and the PPPoE session identifier and the first interface may be established.
  • a plurality of first interfaces may be established in advance, and when the user needs to use, the corresponding first interface is directly allocated to the terminal device, or the first interface needs to be used in the terminal device.
  • the first interface is created by the access device and is used by the terminal device.
  • the method for obtaining the first interface is not limited, and the first interface may be allocated or the first interface may be created.
  • each PPPoE session identifier is unique in the network.
  • the same terminal device corresponds to only one first interface, that is, the first interface corresponding to all PPPoE session identifiers of the same terminal device is the same, the user identifier and the first interface corresponding to the first interface can be directly established as shown in Table 8. relationship.
  • the correspondence between the user identifier and the first interface may be established, and the PPPoE session identifier may be added to the corresponding relationship to establish a PPPoE session identifier, a user identifier, and the first Corresponding relationship of the interface, so that the access device can receive the received NAS message from the terminal device or the received NAS message corresponding to a certain PPPoE session identifier from the terminal device, according to the established correspondence, by using the corresponding first
  • the interface is sent to the CP device of the core network, and the access device can send the received message of a certain first interface of the CP device from the core network to the corresponding terminal device based on the established correspondence.
  • the process of the first NAS message sent by the access device to the CP device may be: the access device according to the acquired user identifier, and/or the PPPoE session identifier, and the corresponding The relationship determines the first interface, and then the access device sends the first NAS message to the CP device through the determined first interface.
  • the access device obtains the user identifier, and determines the corresponding first interface according to the corresponding relationship; if the correspondence is the correspondence between the PPPoE session identifier and the first interface The access device obtains the PPPoE session identifier, and determines the corresponding first interface according to the corresponding relationship; if the correspondence is the user identifier, the PPPoE session identifier, and the corresponding relationship with the first interface, the access device obtains the user identifier, The PPPoE session identifier is determined, and the corresponding first interface is determined according to the correspondence.
  • the process of the second fixed network message sent by the access device to the terminal device may be: if the correspondence is the correspondence between the PPPoE session identifier and the first interface; The access device determines the PPPoE session identifier according to the first interface that receives the NAS registration completion message, and the corresponding relationship, and sends the second fixed network message to the terminal device corresponding to the PPPoE session identifier; if the correspondence is the user identifier and the PPPoE session identifier Corresponding relationship with the first interface, or the corresponding relationship between the user identifier and the first interface, the access device determines the user identifier according to the first interface that receives the NAS registration completion message, and the corresponding relationship, and The terminal device corresponding to the user identifier sends the second fixed network message.
  • the PPPoE is used as an example, and the foregoing registration method may be implemented in the PPPoE discovery process, or may be implemented after the PPPoE discovery process.
  • the first fixed network message may be used. It is a PPPoE Active Discovery Initiation (PADI) message.
  • the second fixed network message is a PPPoE Active Discovery Offer (PADO) message or a PPPoE Active Discovery Session-Confirmation (PADS).
  • PADO PPPoE Active Discovery Offer
  • PADS PPPoE Active Discovery Session-Confirmation
  • the first fixed network message is a PPPoE Active Discovery Request (PADR) message
  • PADR PPPoE Active Discovery Request
  • IPoE is taken as an example.
  • the foregoing registration method may be implemented in the IPoE discovery process or after the IPoE discovery process.
  • the first fixed network is used.
  • the message is a Dynamic Host Configuration Protocol (DHCP) discovery (Discover) message
  • the second fixed network message is a DHCP offer (Offer) message or a DHCP acknowledgement (Ack) message
  • the first fixed network message is a DHCP request ( Request) message
  • the second fixed network message is a DHCP acknowledgement (Ack) message.
  • DHCP Dynamic Host Configuration Protocol
  • Discover Dynamic Host Configuration Protocol
  • the second fixed network message is a DHCP offer (Offer) message or a DHCP acknowledgement (Ack) message
  • the first fixed network message is a DHCP request ( Request) message
  • the second fixed network message is a DHCP acknowledgement (Ack) message.
  • DHCP Dynamic Host Configuration Protocol
  • the access device further sends a PADO message to the terminal device, where the PADO message includes a NAS authentication request message, the access device receives the PADR message sent by the terminal device, and the PADR message includes the NAS authentication information, and the access device The NAS authentication information is sent to the CP device. This process is used to complete the authentication and authentication of the terminal device.
  • the terminal device can also display the capability of the access device to support the NAS, for example, requesting to determine whether the access device supports the NAS, and if the terminal device determines that the access device supports the NAS, the terminal The device, the access device, and the CP device can complete the parallel registration of the terminal device to the fixed network (ie, the access network) and the core network by using the registration method provided by the present application. If the terminal device determines that the access device does not support the NAS, the terminal The registration of the fixed network and the core network will be completed between the device, the access device and the CP device using the traditional registration method mentioned in the background.
  • the fixed network ie, the access network
  • the terminal device carries a first request message in the PADI message, where the first request message is used to request the access device to support the capability of the NAS, and the access device receives the first request message from the terminal device, and according to The self-supporting NAS capability is to send a response message to the terminal device. If the first response message is sent, the first response message may be carried in the PADO message and sent to the terminal device, where the first response message is used to determine the connection.
  • the access device supports the NAS, and the terminal device determines that the access device supports the NAS, so the terminal device can be registered according to the registration method shown in FIG.
  • the access device sends other response messages to the terminal device, and the The response message is used to determine that the access device does not support the NAS, and the terminal device determines that the access device does not support the NAS, and therefore does not register according to the registration method shown in FIG. 2(a), but registers according to other methods, such as the terminal device.
  • the access device and the CP device are registered with the fixed network and the core network by using the traditional registration method mentioned in the background.
  • the first fixed network message in FIG. 2(a) is a PADI message and the second fixed network message is a PADO message
  • the first request message is carried in the first fixed network message and sent to the first fixed network message.
  • the first response message is carried in the second fixed network message and sent to the terminal device.
  • the terminal device may also implicitly request the access device to support the NAS, such as requesting to determine whether the access device supports the NAS. For example, referring to FIG. 2(a), The terminal device sends the first fixed network message to the access device, where the first fixed network message carries the first NAS message, and if the second fixed network message received by the terminal device is not the second NAS message, the access device is implicitly indicated. The NAS is not supported.
  • a possible implementation manner is that the second fixed network message does not include any NAS message, and the terminal device determines that the access device does not support the NAS, or carries the first NAS message in the second fixed network message. The terminal device also determines that the access device does not support the NAS.
  • there may be other implicit indication manners which are not limited in this application.
  • the terminal device may be concurrently registered to the fixed network and the core network according to the registration method of the present application, and if it is determined that the access device does not support the NAS,
  • the terminal device, the access device, and the CP device use the traditional registration method mentioned in the background technology to complete registration to the fixed network and the core network.
  • the terminal device may also request the access device to obtain the NAS user identifier, which is used as an identifier for sending the NAS message between the terminal device and the access device, and the NAS user identifier may be, for example, a MAC address and a user.
  • the reason why the terminal device needs to request a NAS user identifier from the access device has the following advantages:
  • the link information generates a user identifier for the terminal device, and the terminal device does not need to perceive its own link and location information, thereby improving access security and conforming to the characteristics of fixed network access; on the other hand, the terminal device can perform unified management, and the terminal device can perform unified management.
  • the device does not need to write special identification information.
  • the method further includes: the terminal device sends a second request message to the access device, where the access device receives the second request message from the terminal device. And sending a second response message to the terminal device, where the second response message is used to indicate the NAS user identifier of the terminal device.
  • the second response message indicates that the NAS user identifier is not limited.
  • the second response message may be used to display the NAS user identifier that is allocated to the terminal device, or the second response message does not carry the NAS user identifier.
  • the terminal device may use the user identifier as the NAS user identifier or the like according to a pre-agreed rule.
  • the second request message is carried in the PADI message and sent to the access device, where the second response message is carried in the PADO message or the PADS message and sent to the terminal device; or the second request message is carried in the PADR.
  • the second response message sent to the access device in the message is carried in the PADS message and sent to the terminal device.
  • the first request message, the first response message, the second request message, and the second response message may be sent by using a corresponding message in the new protocol, and Other fixed network messages for applying for the registration method can also be sent and received under the new protocol, which is not limited in this application.
  • the present application may also create a PDU session in combination with the foregoing registration method, and at least includes the following two methods.
  • the first method is a registration method provided by the present application, which includes steps 201-204 shown in FIG. 2(a), and after that, further includes the following steps:
  • Step 205 The terminal device sends a third fixed network message to the access device, where the access device receives the third fixed network message.
  • the third fixed network message includes a Packet Data Unit (PDU) session creation request message, and the PDU session creation request message is used to request to create a PDU session.
  • PDU Packet Data Unit
  • Step 206 The access device sends a PDU session creation request message to the CP device, and the CP device receives the PDU session creation request message.
  • Step 207 The CP device sends a PDU session creation request response message to the access device for the PDU session creation request message, and the access device receives the PDU session creation request response message.
  • Step 208 The access device sends a fourth fixed network message to the terminal device, where the terminal device receives the fourth fixed network message.
  • the fourth fixed network message includes a PDU session creation request response message.
  • PPPoE is used as an example, which may include a PPPoE session process, or may not include a PPPoE session process, for example, when a PPPoE session process is included.
  • the registration method shown in FIG. 2(b) further includes: the access device receives the fifth fixed network message from the terminal device, the fifth fixed network message includes an LCP configuration request message, and the access device sends an IPCP message to the terminal device, where the IPCP message includes The IP parameters assigned by the CP device to the terminal device.
  • the fifth fixed network message may be sent to the access device before, after, or simultaneously with step 205, and the IPCP message may be sent to the terminal device before, after, or simultaneously with step 208.
  • the IP parameter allocated by the CP device to the terminal device may be sent to the terminal device in the following manner, optionally, in the The PDU session creation request response message in step 207 includes an IP parameter, and in step 208, the access device sends the IP parameter to the terminal device through the fourth fixed network message, and the IP parameter is used by the terminal device as a PPPoE IP parameter.
  • the second method is a registration method provided by the present application, which is similar to steps 201-204 shown in FIG. 2(a), and completes the creation of a PDU session, and specifically includes the following steps:
  • Step 201 ′ the terminal device sends a first fixed network message to the access device, and the access device receives the first fixed network message.
  • the first fixed network message includes a first NAS message and a PDU session creation request message.
  • step 202 the access device sends a first NAS message and a PDU session creation request message to the CP device of the core network, and the CP device receives the first NAS message and the PDU session creation request message.
  • the access device After receiving the first fixed network message and the PDU session creation request message sent by the terminal device, the access device sends a first NAS message and a PDU session creation request message to the CP device.
  • Step 203 ′ the CP device sends a NAS registration completion message and a PDU session creation request response message to the access device, and the access device receives the NAS registration completion message and the PDU session creation request response message.
  • Step 204 ′ the access device sends a second fixed network message to the terminal device, and the terminal device receives the second fixed network message.
  • the access device After receiving the NAS registration completion message and the PDU session creation request response message sent by the CP device, the access device sends a second fixed network message to the terminal device, where the second fixed network message includes the second NAS message and the PDU session creation request response. Message.
  • the above steps 201'-step 204' are based on the steps 201-204, and the PDU session creation process is added.
  • the registration process of the fixed network and the core network in the step 201'-step 204' can refer to the foregoing description, no longer Narration.
  • the NAS device that is used to request registration to the core network is carried in the fixed network message and sent to the access device, so as to simultaneously register the core network and
  • the network message indicates that the registration of the core network is completed, and the registration of the fixed network and the core network is implemented in parallel, which reduces the time for the terminal device to register to the access network and the core network, and at the same time, because the NAS message is carried in the fixed network message, No additional dedicated data channels are required to deliver NAS messages, increasing resource usage. And, during the registration process, you can also create a PDU session to further improve registration efficiency.
  • FIG. 3 is a flowchart of another registration method provided by the present application.
  • the registration method uses the fixed network protocol as the PPPoE.
  • the registration process includes the following steps:
  • Step 1 The terminal device sends a PADI message to the access device, and the access device receives the PADI message.
  • Step 2 The access device sends a PADO message to the terminal device, and the terminal device receives the PADO message.
  • Step 3 The terminal device sends a PADR message to the access device, and the access device receives the PADR message.
  • Steps 1 to 3 are the PADI, PADO, and PADR interactions in the PPPoE discovery process between the terminal device and the access device in the prior art, and are not described again.
  • Step 4 The access device allocates a PPPoE session identifier to the terminal device, allocates a first interface according to the user identifier, and records the corresponding relationship.
  • the corresponding relationship may be a correspondence between the PPPoE session identifier and the first interface, or a correspondence between the user identifier, the PPPoE session identifier, and the first interface.
  • Step 5 The access device sends a PADS message to the terminal device, and the terminal device receives the PADS message.
  • the above step 5 and the above steps 1 - 3 constitute four interactions in the PPPoE discovery process.
  • the PPDS message identifier included in the PADS message is allocated to the terminal device.
  • Step 6 The terminal device sends a first fixed network message to the access device, where the first fixed network message includes the first NAS message, and the access device receives the first fixed network message.
  • the first NAS message may also be referred to as a NAS registration request message for requesting registration to the core network.
  • the first NAS message may be carried in a vendor-defined field of the first fixed network message.
  • Step 7 The access device determines the first interface according to the correspondence.
  • the access device determines the corresponding first interface according to the user identifier and/or the PPPoE session identifier in the first fixed network message.
  • the subsequent access device sends a message to the CP device through the first interface, and the corresponding first method is used to determine the corresponding first interface.
  • Step 8 The access device sends a first NAS message to the CP device by using the determined first interface, and the CP device receives the first NAS message.
  • Step 9 After the CP device registers the terminal device, the NAS registration completion message is sent to the access device, and the access device receives the NAS registration completion message.
  • the CP device sends the NAS registration completion message through the first interface.
  • Step 10 The CP device sends an N2 message to the access device, where the access device receives the N2 message, where the N2 message includes the user identifier.
  • the access device can determine the corresponding terminal device according to the user identifier.
  • Step 11 The access device sends a second fixed network message to the terminal device, where the terminal device receives the second fixed network message.
  • the second fixed network message includes a second NAS message, which is used to indicate that the core network registration has been completed.
  • the second NAS message may be encapsulated in a vendor-defined field of the second fixed network message.
  • the second fixed network message is an LCP message, and may be encapsulated in the LCP message.
  • Step 12 The terminal device sends the third fixed network message and the fifth fixed network message to the access device, where the access device receives the third fixed network message and the fifth fixed network message.
  • the third fixed network message includes a PDU creation request message for requesting to create a PDU session, and the fifth fixed network message includes an LCP configuration request message.
  • Step 13 The access device sends a PDU session creation request message to the CP device by using the first interface, and the CP device receives the PDU session creation request message.
  • Step 14 The CP device sends a PDU session creation request response message to the access device by using the first interface, and the access device receives the PDU session creation request response message.
  • the PDU session creation request response message contains the IP parameters allocated for the terminal device.
  • Step 15 The access device sends an IPCP message to the terminal device, where the terminal device receives the IPCP message.
  • the IPCP message contains the IP parameters assigned by the CP device to the terminal device.
  • the registration method shown in FIG. 3 carries the NAS message by using the vendor-defined field in the PPPoE fixed network message during the PPPoE session, and simultaneously performs the authentication process of the terminal device to the core network in the PPPoE signaling interaction process, and also Taking into account the existing PPPoE registration process and the registration process of the core network, on the one hand, the registration time is reduced, and on the other hand, the resource utilization is improved because there is no need to establish a dedicated data channel for the dedicated NAS message.
  • FIG. 4 is a flowchart of another registration method provided by the present application.
  • the registration method uses a fixed network protocol as a PPPoE.
  • the registration method includes the following steps:
  • Step 1 - Step 11 is the same as Step 1 - Step 11 of the registration method shown in FIG. 3, and can be referred to the foregoing description.
  • Step 12 The terminal device sends a third fixed network message to the access device, and the access device receives the third fixed network message.
  • the third fixed network message includes a PDU creation request message for requesting to create a PDU session.
  • Step 13 The access device sends a PDU session creation request message to the CP device by using the first interface, and the CP device receives the PDU session creation request message.
  • Step 14 The CP device sends a PDU session creation request response message to the access device by using the first interface, and the access device receives the PDU session creation request response message.
  • the PDU session creation request response message contains the IP parameters allocated for the terminal device.
  • Step 15 The access device sends a fourth fixed network message to the terminal device, where the terminal device receives the fourth fixed network message.
  • the fourth fixed network message includes an IP parameter allocated by the CP device for the terminal device.
  • the registration method shown in FIG. 4 is different from the registration method shown in FIG. 3 in that the PPPoE session process in the registration method shown in FIG. 3 is cancelled, and the IPCP message is no longer used to deliver IP parameters to the terminal device.
  • the use of NAS messaging IP parameters to the terminal device further simplifies the registration process and achieves the purpose of PPPoE registration.
  • FIG. 5 is a flowchart of another registration method provided by the present application.
  • the embodiment shown in FIG. 5 is based on the embodiment shown in FIG. 4, and the first NAS message is carried in a PADI message.
  • the second NAS message is carried in the PADS message and sent to the terminal device, that is, the first fixed network message is a PADI message, and the second fixed network message is a PADS message, and the registration method includes the following steps:
  • Step 1 The terminal device sends a PADI message to the access device, and the access device receives the PADI message.
  • the first NAS message is included in the PADI message.
  • the first NAS message may also be referred to as a NAS registration request message for requesting registration to the core network.
  • Step 2 The access device allocates the first interface according to the user identifier, and establishes a correspondence.
  • Step 3 The access device determines, according to the corresponding relationship, the first interface corresponding to the terminal device.
  • Step 4 The access device sends a first NAS message to the CP device by using the determined first interface, and the CP device receives the first NAS message.
  • the method determines that the corresponding first interface sends the NAS message.
  • Step 5 The CP device sends an authentication request to the access device, and the access device receives the authentication request.
  • step 5 is an optional step.
  • step 6 the authentication request is carried in step 6
  • step 8 the authentication information is carried in step 7, and step 8 is included.
  • Step 6 The access device sends a PADO message to the terminal device, and the terminal device receives the PADO message.
  • the PADO message includes an authentication request message.
  • Step 7 The terminal device sends a PADR message to the access device, and the access device receives the PADR message.
  • the PADR message includes authentication information.
  • Step 8 The access device sends the authentication information to the CP device, and the CP device receives the authentication information.
  • This step is an optional step.
  • Step 9 The CP device sends a NAS registration completion message to the terminal device through the first interface, and the terminal device receives the NAS registration completion message.
  • Step 10 The access device allocates a PPPoE session identifier to the terminal device, and adds the PPPoE session identifier to the foregoing correspondence.
  • Step 11 The access device sends a PADS message to the terminal device, and the terminal device receives the PADS message.
  • the PPDS message includes a PPPoE session identifier allocated for the terminal device, and further includes a second NAS message, where the second NAS message is used to indicate that the registration core network is completed.
  • Steps 12 to 15 are the same as steps 12 to 15 of the registration method shown in FIG. 4, and may be referred to the foregoing description, and are not described again.
  • the registration method shown in FIG. 5 advances part of the process of the core network registration process to the PPPoE discovery process, improving the efficiency of the registration process.
  • FIG. 6 is a flowchart of another registration method provided by the present application.
  • the registration method uses the fixed network protocol as the PPPoE as an example.
  • the PPPoE manufacturer is adopted in the PPPoE discovery process.
  • types of options define NAS negotiation messages, for example, you can define the following types of messages:
  • NAS support request Whether the server that requests access to the device supports NAS.
  • the NAS support request is also referred to as a first request message.
  • NAS support ack The identification server supports NAS and can respond to NAS related information.
  • NAS support ack is also referred to as a first response message.
  • NAS user identification request message The NAS user identifier that the user is requested to use to send the NAS message.
  • the NAS User Identity Request message is also referred to as a second request message.
  • the NAS user identifier is an identifier that is assigned to the user by the server, or information that the server specifies the user to use as the user identifier, such as a MAC address.
  • NAS user identity request response message used to indicate the NAS user identity of the terminal device.
  • the NAS User Identity Request Response message is also referred to as a second response message.
  • the registration method shown in FIG. 6 is based on the registration method shown in FIG. 4, and the steps 1 to 5 are modified.
  • Step 1 The terminal device sends a PADI message to the access device, and the access device receives the PADI message.
  • a first request message is included in the PADI message for requesting whether the access device supports the NAS message.
  • Step 2 The access device sends a PADO message to the terminal device, and the terminal device receives the PADO message.
  • the PADO message includes a first response message, which is used to notify the terminal device that the access device supports the NAS, that is, the NAS message can be used.
  • PADO may also carry NAS support Reject, or other unrecognized messages, or the first request message sent by the terminal device in step 1 of the replication, to indicate that the access device does not support the NAS.
  • the terminal device will not perform the subsequent steps 3 - 15 , but register the fixed network and the core network according to the traditional registration method.
  • Step 3 The terminal device sends a PADR message to the access device, and the access device receives the PADR message.
  • the second request message is included in the PADR message, and is used to request the NAS user identifier, and the second request message is optional, that is, the NAS user identifier may not be requested. In this case, the user of the terminal device itself is used. logo.
  • Step 4 The access device allocates a PPPo session identifier, and allocates a NAS user identifier, and establishes a correspondence.
  • Step 5 The access device sends a PADS message to the terminal device, and the terminal device receives the PADS message.
  • the access device adds a second response message to the PADS, which is used to indicate the NAS identifier information, or may be the type of information used by the terminal device to identify the NAS user identifier. For example, MAC address, etc.
  • the user NAS identifier information is optional. Even if the terminal device requests the user NAS identifier in step 3, the terminal device may not return the user NAS identifier information to the terminal device, that is, the PADS message does not carry the second response message. In this case, the terminal device may use the appointment information as the NAS user identifier according to a preset rule, for example, using the user identifier as the NAS user identifier.
  • Step 6 - Step 15 is the same as Step 6 - Step 15 in the registration method shown in FIG. 4, and the foregoing description is referred to, and details are not described herein again.
  • the scheme adds a NAS capability request procedure of the access device in the PPPoE process, so that the terminal device, the access device, and the CP device can select a corresponding registration method for registration, for example, using the present application. Apply for the method provided, or use the registration method provided by the prior art.
  • FIG. 7 is a flowchart of another registration method provided by the present application, where the PDU session creation process of step 12 to step 15 is added to step 1 - step 11 based on the registration method shown in FIG. 5 . During the registration process, it is initiated at the same time to further improve the registration efficiency, including the following steps:
  • Step 1 The terminal device sends a PADI message to the access device, and the access device receives the PADI message.
  • the PADI message includes a first NAS message and a PDU session creation request message.
  • the first NAS message may also be referred to as a NAS registration request message for requesting registration to the core network.
  • Step 2 The access device allocates the first interface according to the user identifier, and establishes a correspondence.
  • Step 3 The access device determines, according to the corresponding relationship, the first interface corresponding to the terminal device.
  • Step 4 The access device sends the first NAS message and the PDU session creation request message through the determined first interface.
  • the method determines that the corresponding first interface sends the NAS message.
  • Step 5 The CP device sends an authentication request to the access device, and the access device receives the authentication request.
  • step 5 is an optional step.
  • step 6 the authentication request is carried in step 6
  • step 8 the authentication information is carried in step 7, and step 8 is included.
  • Step 6 The access device sends a PADO message to the terminal device, and the terminal device receives the PADO message.
  • the PADO message includes an authentication request message.
  • Step 7 The terminal device sends a PADR message to the access device, and the access device receives the PADR message.
  • the PADR message includes authentication information.
  • Step 8 The access device sends the authentication information to the CP device, and the CP device receives the authentication information.
  • This step is an optional step.
  • Step 9 The CP device sends a NAS registration completion message and a PDU session creation completion message to the terminal device through the first interface, and the terminal device receives the NAS registration completion message and the PDU session creation completion message.
  • the PDU session creation completion message includes an IP parameter allocated by the CP device for the terminal device.
  • Step 10 The access device allocates a PPPoE session identifier to the terminal device, and adds the PPPoE session identifier to the foregoing correspondence.
  • Step 11 The access device sends a PADS message to the terminal device, and the terminal device receives the PADS message.
  • the PPDS message includes a PPPoE session identifier allocated to the terminal device, including a second NAS message, where the second NAS message is used to indicate that the registration core network has been completed, and further includes a PDU session creation completion message, including allocating the terminal device. IP parameters.
  • FIG. 8 is a flowchart of another registration method provided by the present application.
  • the registration method uses an IPOE as an example, which is similar to the registration process shown in FIG. 7, and includes the following steps:
  • Step 1 The terminal device sends a DCHP discovery message to the access device, and the access device receives the DCHP discovery message.
  • the DCHP discovery message includes a first NAS message and a PDU session creation request message.
  • the first NAS message may also be referred to as a NAS registration request message for requesting registration to the core network.
  • Step 2 The access device allocates the first interface according to the user identifier, and establishes a correspondence.
  • Step 3 The access device determines, according to the corresponding relationship, the first interface corresponding to the terminal device.
  • Step 4 The access device sends a first NAS message and a PDU session creation request message to the CP device by using the determined first interface, and the CP device receives the first NAS message and the PDU session creation request message.
  • the method determines that the corresponding first interface sends the NAS message.
  • Step 5 The CP device sends a NAS registration completion message and an N2 PDU session request message to the access device, and the access device receives the NAS registration completion message and the N2 PDU session request message.
  • the N2PDU session request message includes an IP parameter allocated by the CP device for the terminal device.
  • Step 6 The access device sends a DHCP providing message to the terminal device, and the terminal device receives the DHCP providing message.
  • the DHCP providing message includes an N2 PDU session request response message.
  • Step 7 The terminal device sends a DHCP request message to the access device, and the access device receives the DHCP request message.
  • the DHCP request message includes an N2PDU guard request response message.
  • Step 8 The access device sends an N2 PDU session request response message to the CP device, and the CP device receives the N2 PDU session request response message.
  • Step 9 The access device sends a DHCP acknowledgement message to the terminal device, and the terminal device receives the DHCP acknowledgement message.
  • the present invention carries the NAS message in a DHCP message (or DCHP message), and completes the DHCP process and the registration in the core network and the PDU session creation process in parallel, which can improve the registration efficiency.
  • FIG. 3 to FIG. 8 are only used as several possible implementation manners. In practical applications, other specific implementation manners may also be referred to, which may be referred to in the foregoing description of the present application. Again.
  • each network element such as a terminal device, an access device, and a CP device of a core network
  • each network element includes hardware structures and/or software modules for performing respective functions in order to implement the above functions.
  • the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the modules and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
  • FIG. 9 is a schematic diagram of a registration apparatus according to an embodiment of the present invention.
  • the registration device 900 includes at least one processor 91, a communication bus 92, a memory 93, and at least one communication interface 94.
  • the processor 91 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present invention.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • Communication bus 92 can include a path for communicating information between the components described above.
  • the communication interface 94 uses devices such as any transceiver for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), and the like.
  • RAN Radio Access Network
  • WLAN Wireless Local Area Networks
  • the memory 93 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device can also be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • the memory can exist independently and be connected to the processor via a bus.
  • the memory can also be integrated with the processor.
  • the memory 93 is used to store application code for executing the solution of the present invention, and is controlled by the processor 91 for execution.
  • the processor 91 is configured to execute application code stored in the memory 93.
  • processor 91 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • registration device 900 can include multiple processors, such as processor 91 and processor 98 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • the registration device 900 when the registration device 900 is an access device or a terminal device, the registration device 900 may further include an output device 95 and an input device 96.
  • Output device 95 is in communication with processor 91 and can display information in a variety of ways.
  • the output device 95 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait.
  • the input device 96 is in communication with the processor 91 and can acquire external information in a variety of ways, or accept input from the user.
  • input device 96 can be a camera, mouse, keyboard, touch screen device, or sensing device, and the like.
  • the access device in FIG. 1 may be the device shown in FIG. 9, and one or more software modules are stored in the memory of the control plane device.
  • the control plane device can implement the software module through the processor and the program code in the memory, and realize the registration of the terminal device to the fixed network and the core network.
  • the terminal device in FIG. 1 may be the device shown in FIG. 9, and one or more software modules are stored in the memory of the terminal device.
  • the terminal device can implement the software module through the processor and the program code in the memory, and realize the registration of the terminal device to the fixed network and the core network.
  • the embodiment of the present invention may perform the division of the function module on the terminal device or the access device according to the foregoing method example.
  • each function module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 10 is a schematic structural diagram of a possible implementation of the registration device involved in the foregoing embodiment.
  • the device 1000 includes: a receiving unit 1001, a processing unit 1002, Sending unit 1003, wherein:
  • the receiving unit 1001 is configured to receive a first fixed network message from the terminal device, where the first fixed network message includes a first non-access stratum NAS message, where the first NAS message is used to request registration to the core network;
  • the sending unit 1003 is configured to send the first NAS message to the core network control plane CP device.
  • the receiving unit 1001 is further configured to receive a NAS registration completion message from the CP device.
  • the sending unit 1003 is further configured to send a second fixed network message to the terminal device, where the second fixed network message includes a second NAS message, where the second NAS message is used to indicate that the core network registration is completed.
  • the processing unit 1002 is configured to record a correspondence, where the correspondence is a user identifier of the terminal device, and/or a correspondence between an Ethernet-based point-to-point protocol PPPoE session identifier and a first interface, where the PPPoE The session identifier is allocated by the access device to the terminal device, and the first interface is an interface between the access device and a functional unit for implementing access and mobility management.
  • the sending unit 1003 is configured to send the first NAS message to the core network control plane CP device, specifically, the sending unit 1003, according to the obtained user identifier, and/or the PPPoE session identifier, and Determining, by the corresponding relationship, the first interface; sending, by the determined first interface, the first NAS message to the CP device.
  • the corresponding relationship is a correspondence between the PPPoE session identifier and the first interface
  • the sending unit 1003 is further configured to send the second fixed network message to the terminal device, specifically: the sending unit 1003, according to the receiving And the first interface of the NAS registration completion message, and the corresponding relationship, determining a PPPoE session identifier; and sending the second fixed network message to the terminal device corresponding to the PPPoE session identifier.
  • the correspondence is a correspondence between the user identifier and the PPPoE session identifier, and the first interface, or the corresponding relationship is a correspondence between the user identifier and the first interface;
  • the sending unit 1003 is further used to The sending, by the terminal device, the second fixed network message, specifically: the sending unit 1003, determining, according to the first interface that receives the NAS registration completion message, and the corresponding relationship, determining a user identifier;
  • the terminal device sends the second fixed network message.
  • the first fixed network message is a PPPoE active discovery start PADI message
  • the second fixed network message provides a PADO message or a PPPoE active discovery session acknowledgement PADS message for PPPoE active discovery
  • the first fixed network message A PADR message is requested for PPPoE active discovery
  • the second fixed network message is a PADS message.
  • the sending unit 1003 is further configured to send a PADO message to the terminal device, where the PADO message includes a NAS authentication request message, and the receiving unit 1001 is further configured to receive a PADR message sent by the terminal device, where The PADR message includes NAS authentication information, and the sending unit 1003 is further configured to send the NAS authentication information to the CP device.
  • the receiving unit 1001 is further configured to receive a first request message from the terminal device, where the first request message is used to request the capability of the access device to support the NAS, and the sending unit 1003 is further configured to The terminal device sends a first response message, where the first response message is used to determine that the access device supports the NAS.
  • the first request message is carried in a PADI message and sent to the access device, where the first response message is carried in a PADO message and sent to the terminal device.
  • the receiving unit 1001 is further configured to receive a second request message from the terminal device, where the second request message is used to request a NAS user identifier
  • the sending unit 1003 is further configured to send, to the terminal device, a And a second response message, where the second response message is used to indicate the NAS user identifier of the terminal device.
  • the second request message is carried in a PADI message and sent to the access device, where the second response message is carried in a PADO message or a PADS message and sent to the terminal device; or
  • the second request message is carried in the PADR message and sent to the access device, and the second response message is carried in the PADS message and sent to the terminal device.
  • the receiving unit 1001 is further configured to receive a third fixed network message from the terminal device, where the third fixed network message includes a packet data unit PDU session creation request message, where the PDU session creation request message is used.
  • the sending unit 1003 is further configured to send a PDU session creation request message to the CP device
  • the receiving unit 1001 is further configured to receive a PDU session creation for the PDU session creation request message from the CP device.
  • the sending unit 1003 is further configured to send a fourth fixed network message to the terminal device, where the fourth fixed network message includes the PDU session creation request response message.
  • the fourth NAS message further includes an inter-network interconnection protocol IP parameter, where the IP parameter is used by the terminal device as a PPPoE IP parameter.
  • the receiving unit 1001 is further configured to receive a fifth fixed network message from the terminal device, where the fifth fixed network message includes a link control protocol LCP configuration request message, and the sending unit 1003 is further configured to The terminal device sends an inter-network interconnection protocol control protocol (IPCP) message, where the IPCP message includes an IP parameter allocated by the CP device to the terminal device.
  • IPCP inter-network interconnection protocol control protocol
  • the first fixed network message further includes a PDU session creation request message, where the PDU session creation request message is used to request to create a PDU session; and the second fixed network message further includes a request message for the PDU session creation request.
  • a PDU session creation request response message the sending unit 1003 is further configured to send the PDU session creation request message to the CP device, and the receiving unit 1001 is further configured to receive the PDU session creation request response from the CP device Message.
  • the first fixed network message is a dynamic host configuration protocol DHCP discovery message
  • the second fixed network message is a DHCP providing message or a DHCP acknowledgement message
  • the first fixed network message is a DHCP request message, where The second fixed network message is a DHCP acknowledgement message.
  • the device 1000 can be an access device, and all related content of the steps in the foregoing method embodiments can be referred to the function description of the corresponding function module, and details are not described herein again.
  • the implementation registration device is presented in the form of dividing each functional module corresponding to each function, or the implementation registration device is presented in a form that divides each functional module in an integrated manner.
  • a "module” herein may refer to an application-specific integrated circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above. Device.
  • ASIC application-specific integrated circuit
  • the implementation registration device 1000 can take the form shown in FIG.
  • the receiving unit 1001, the processing unit 1002, and the transmitting unit 1003 in FIG. 10 may be implemented by the processor 91 (and/or the processor 98) and the memory 93 of FIG. 9, specifically, the receiving unit 1001, the processing unit 1002, or
  • the sending unit 1003 can be executed by calling the application code stored in the memory 93 by the processor 91 (and/or the processor 98), which is not limited in this embodiment of the present invention.
  • FIG. 11 is a schematic diagram showing another possible implementation of the registration device involved in the above embodiment.
  • the device 1100 includes: a receiving unit 1101, and a processing unit 1102. , sending unit 1103, wherein:
  • the sending unit 1103 is configured to send, to the access device, the first fixed network message, where the first fixed network message includes a first non-access stratum NAS message, where the first NAS message is used to request registration to the core network; 1101.
  • the method is configured to receive a second fixed network message from the access device, where the second fixed network message includes a second NAS message, where the second NAS message is used to indicate that the core network registration is completed.
  • the first fixed network message is a PADI message
  • the second fixed network message is a PADO message or a PADS message
  • the first fixed network message is a PADR message
  • the second fixed network message is a PADS message.
  • the receiving unit 1101 further receives a PADO message sent by the access device, where the PADO message includes a NAS authentication request message, and the sending unit 1103 further sends a PADR message to the access device.
  • the PADR message includes NAS authentication information.
  • the sending unit 1103 is further configured to send a first request message to the access device, where the first request message is used to request the capability of the access device to support the NAS; the receiving unit 1101 further uses Receiving a first response message from the access device, the first response message is used to indicate that the access device supports a NAS.
  • the first request message is carried in a PADI message and sent to the access device, where the first response message is carried in a PADO message and sent to the terminal device.
  • the sending unit 1103 sends a second request message to the access device, where the second request message is used to request a NAS user identifier, and the receiving unit 1101 further receives a second from the access device. And a second response message, where the second response message is used to indicate the NAS user identifier of the terminal device.
  • the second request message is carried in a PADI message sent to the access device, where the second response message is carried in a PADO message or a PADS message is sent to the terminal device; or The second request message is carried in the PADR message and sent to the access device, and the second response message is carried in the PADS message and sent to the terminal device.
  • the sending unit 1103 sends a third fixed network message to the access device, where the third fixed network message includes a PDU session creation request message, where the PDU session creation request message is used to request to create a PDU session.
  • the receiving unit 1101 receives a fourth fixed network message from the access device, and the fourth fixed network message includes a PDU session creation request response message for the PDU session creation request message.
  • the sending unit 1103 sends a fifth fixed network message to the access device, where the fifth fixed network message includes an LCP configuration request message, and the receiving unit 1101 further receives the access device from the access device.
  • An IPCP message where the IPCP message includes an IP parameter allocated by the core network control plane CP device to the terminal device.
  • the fourth NAS message further includes an IP parameter, where the IP parameter is used by the terminal device as a PPPoE IP parameter.
  • the first fixed network message further includes a PDU session creation request message, where the PDU session creation request message is used to request to create a PDU session, and the second fixed network message further includes a request message for the PDU session creation request.
  • the PDU session creates a request reply message.
  • the first fixed network message is a DHCP discovery message
  • the second fixed network message is a DHCP providing message or a DHCP acknowledgement message
  • the first fixed network message is a DHCP request message
  • the second solid The network message is a DHCP acknowledgement message.
  • each functional unit in the embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the sending unit 1103 and the receiving unit 1101 may be the same unit and different units.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the device 1100 can be a terminal device, and all the related content of the steps in the foregoing method embodiments can be referred to the function description of the corresponding function module, and details are not described herein again.
  • the implementation registration device is presented in the form of dividing each functional module corresponding to each function, or the implementation registration device is presented in a form that divides each functional module in an integrated manner.
  • a "module” herein may refer to an application-specific integrated circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above. Device.
  • ASIC application-specific integrated circuit
  • the implementation registration device 1100 can take the form shown in FIG.
  • the receiving unit 1101, the processing unit 1102, and the transmitting unit 1103 in FIG. 11 may be implemented by the processor 91 (and/or the processor 98) of FIG.
  • the sending unit 1103 can be executed by calling the application code stored in the memory 93 by the processor 91 (and/or the processor 98), which is not limited in this embodiment of the present invention.
  • the embodiment of the present application further provides a computer readable storage medium for storing computer software instructions used by the access device in the foregoing method embodiment, which includes a program designed to execute the foregoing method embodiment.
  • the embodiment of the present application provides another computer readable storage medium for storing computer software instructions used by the terminal device in the foregoing method embodiment, which includes a program designed to execute the foregoing method embodiments.
  • the embodiment of the present application further provides a computer program product, which includes computer software instructions, which can be loaded by a processor to implement a flow in a registration method performed by a terminal device in the foregoing embodiment.
  • the embodiment of the present application provides another computer program product, which includes computer software instructions, which can be loaded by a processor to implement the flow in the registration method performed by the access device in the above embodiment.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server or data center by wire (eg, coaxial cable, fiber optic, Digital Subscriber Ling (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be stored by a computer or a data storage device such as a server, data center, or the like that includes a plurality of available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a Solid State Disk (SSD)) or the like.
  • a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
  • an optical medium eg, a DVD
  • a semiconductor medium eg, a Solid State Disk (SSD)
  • the steps of a method or algorithm described in this application can be directly embedded in hardware, a software unit executed by a processor, or a combination of the two.
  • the software unit can be stored in a random access memory (RAM), a flash memory, a read-only memory (ROM), and an Erasable Programmable Read Only Memory (EPROM). ), a register, a hard disk, a removable disk, a Compact Disc Read-Only Memory (CD-ROM), or any other form of storage medium in the art.
  • the storage medium can be coupled to the processor such that the processor can read information from the storage medium and can write information to the storage medium.
  • the storage medium can also be integrated into the processor.
  • the processor and the storage medium may be disposed in an ASIC, and the ASIC may be disposed in the terminal device or the access device.
  • the processor and the storage medium may also be disposed in different components in the terminal device or the access device.
  • Computer readable media includes computer storage media and communication media that facilitates the transfer of computer programs from one place to another.
  • the storage medium can be any available media that any general purpose or special computer can access.
  • such computer-readable media can include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage device, or any other device or data structure that can be used for carrying or storing Other media that can be read by a general purpose or special computer, or a general purpose or special processor.
  • any connection can be appropriately defined as a computer readable medium, for example, if the software is from a website site, server or other remote source through a coaxial cable, fiber optic computer, twisted pair, digital subscriber line (DSL) Or wirelessly transmitted in, for example, infrared, wireless, and microwave, is also included in the defined computer readable medium.
  • the disks and disks include compressed disks, laser disks, optical disks, digital Versatile Discs (DVDs), floppy disks, and Blu-ray disks. Disks usually copy data magnetically, and disks usually use The laser performs optical reproduction of the data. Combinations of the above may also be included in a computer readable medium.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供一种注册方法及装置，包括：接入设备接收来自终端设备的第一固网消息，其中包括第一NAS消息，用于请求注册至核心网，向核心网的CP设备发送该第一NAS消息，在CP设备完成对终端设备的核心网注册后，CP设备发送NAS注册完成消息至接入设备，接入设备向终端设备发送第二固网消息，其携带第二NAS消息，用于指示核心网注册已完成，由于注册至接入网的过程中，还将用于请求注册至核心网的NAS消息携带于固网消息中发送至接入设备，以便同时进行核心网的注册，减少了终端设备注册至接入网及核心网的时间，同时，由于将NAS消息携带于固网消息中，因此无需提供专门的数据通道传递NAS消息，提高了资源使用率。

Description

一种注册方法及装置
本申请要求于2017年5月25日提交中国专利局、申请号为201710381306.X、发明名称为“一种注册方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及移动通信技术领域，尤其涉及一种注册方法及装置。
背景技术
在非第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)接入场景中，终端设备通过固定网络接入到接入网(Access Network，AN)，之后通过接入设备接入到核心网。
现有技术中，终端设备注册至接入网及核心网的过程大致为：终端设备先创建和接入设备之间的数据通道，例如完成固网协议为基于以太网的点对点协议(英文：Point to Point Protocol over Ethernet，PPPoE)注册，或者完成基于以太网的网络之间互连的协议(Internet Protocol over Ethernet，IPoE)中的动态主机配置协议(Dynamic Host Configuration Protocol，DHCP)注册，之后使用创建的数据通道传递网络附属存储(Network Attached Storage，NAS)消息到接入设备，从而完成到核心网的注册过程。
这种首先创建终端设备到接入设备间的数据通道，然后在该数据通道上传递NAS消息完成到核心网的注册方式，存在的主要问题是：第一，注册过程耗时较长；第二，需要占用一个专有的数据通道用于传递NAS消息，使得数据通道使用率较低。
发明内容
本申请提供一种注册方法及装置，用以减少终端设备注册至接入网及核心网的时间，以及提高资源使用率。
第一方面，本申请提供一种注册方法，包括：
接入设备接收来自终端设备的第一固网消息，所述第一固网消息包括第一非接入层NAS消息，所述第一NAS消息用于请求注册至核心网；接入设备向核心网控制面CP设备发送所述第一NAS消息；接入设备接收来自所述CP设备的NAS注册完成消息，并向所述终端设备发送第二固网消息，所述第二固网消息包括第二NAS消息，所述第二NAS消息用于指示核心网注册已完成。
上述方案，终端设备在注册至接入网的过程中，还将用于请求注册至核心网的NAS消息携带于固网消息中发送至接入设备，以便同时进行核心网的注册，以及通过固网消息指示核心网注册完成，实现了并行进行固网和核心网的注册，减少了终端设备注册至接入网 及核心网的时间，同时，由于将NAS消息携带于固网消息中，因此也无需额外提供专门的数据通道用于传递NAS消息，提高了资源使用率。
在一种可能的设计中，接入设备记录对应关系，所述对应关系为所述终端设备的用户标识，和/或基于以太网的点对点协议PPPoE会话标识与第一接口的对应关系，所述PPPoE会话标识为所述接入设备为所述终端设备分配的,所述第一接口为接入设备与用于实现接入与移动性管理的功能单元之间的接口。其中，用于实现接入与移动性管理的功能单元例如可以是接入与移动性管理功能(Access and Mobility Management Function，AMF)网元，实际应用中，第一接口还可以有其它命名方式，例如，还可以称为N2接口，NG2接口等，随着通信的演变，在未来通信中，第一接口还可以有其它名称，本申请不做限定。
如此，接入设备在记录了对应关系之后，可基于对应关系，将来自终端设备的NAS消息通过相应的第一接口发送至核心网的CP设备，相应地，接入设备在接收到第一接口的NAS消息后，确定相应的用户标识或PPPoE会话标识，将NAS消息发送至相应的终端设备。
在一种可能的设计中，接入设备向CP设备发送第一NAS消息，包括：接入设备根据获取的用户标识，和/或PPPoE会话标识，及对应关系，确定第一接口；接入设备通过确定的第一接口，向CP设备发送第一NAS消息。如此，接入设备可通过相应的第一接口，向CP设备发送第一NAS消息。
在一种可能的设计中，若对应关系为PPPoE会话标识与第一接口的对应关系，则接入设备向终端设备发送第二固网消息，包括：接入设备根据接收NAS注册完成消息的第一接口，及对应关系，确定PPPoE会话标识，然后接入设备向该PPPoE会话标识对应的终端设备发送第二固网消息。如此，接入设备可向相应的终端设备发送第二固网消息。
在一种可能的设计中，若对应关系为用户标识和PPPoE会话标识，与第一接口的对应关系，或，所述对应关系为用户标识与第一接口的对应关系；则接入设备根据接收NAS注册完成消息的第一接口，及对应关系，确定用户标识，然后接入设备向用户标识对应的终端设备发送第二固网消息。如此，接入设备可向相应的终端设备发送第二固网消息，保证发送固网消息的准确性。
在一种可能的设计中，第一固网消息为PPPoE主动发现开始PADI消息，第二固网消息为PPPoE主动发现提供PADO消息或PPPoE主动发现会话确认PADS消息；或者所述第一固网消息为PPPoE主动发现请求PADR消息，所述第二固网消息为PADS消息。如此，终端设备可在PPPoE发现过程中，实现固网和核心网的并行注册。
在一种可能的设计中，接入设备向终端设备发送PADO消息，PADO消息包括NAS鉴权请求消息，接入设备接收终端设备发送的PADR消息，PADR消息包括NAS鉴权信息，接入设备向所述CP设备发送所述NAS鉴权信息。如此，可完成对终端设备的鉴权过程。
在一种可能的设计中，接入设备接收来自终端设备的第一请求消息，第一请求消息用于请求接入设备支持NAS的能力，接入设备向所述终端设备发送第一响应消息，第一响应消息用于确定接入设备支持NAS。如此，接入设备可将接入设备所支持的NAS的能力通知到终端设备，例如，接入设备支持NAS或不支持NAS。可选地，第一请求消息是携带在PADI消息中发送至接入设备的，第一响应消息是携带在PADO消息中发送至终端设备的。
在一种可能的设计中，接入设备接收来自终端设备的第二请求消息，第二请求消息用 于请求NAS用户标识，接入设备向终端设备发送第二响应消息，第二响应消息用于指示终端设备的NAS用户标识。可选地，第二请求消息是携带在PADI消息中发送至接入设备的，第二响应消息是携带在PADO消息或PADS消息中发送至终端设备的；或者第二请求消息是携带在PADR消息中发送至接入设备的，第二响应消息是携带在PADS消息中发送至终端设备的。
在一种可能的设计中，接入设备接收来自终端设备的第三固网消息，第三固网消息包括PDU会话创建请求消息，PDU会话创建请求消息用于请求创建PDU会话；接入设备向CP设备发送PDU会话创建请求消息；接入设备接收来自CP设备的针对该PDU会话创建请求消息的PDU会话创建请求应答消息；接入设备向终端设备发送第四固网消息，第四固网消息包括该PDU会话创建请求应答消息。如此，可完成PDU会话的创建。
在一种可能的设计中，第四NAS消息还包括IP参数，IP参数由终端设备作为PPPoE IP参数。
在一种可能的设计中，接入设备接收来自终端设备的第五固网消息，第五固网消息包括LCP配置请求消息，接入设备向终端设备发送IPCP消息，IPCP消息包括CP设备为终端设备分配的IP参数。
在一种可能的设计中，第一固网消息还包括PDU会话创建请求消息，PDU会话创建请求消息用于请求创建PDU会话，第二固网消息还包括针对PDU会话创建请求消息的PDU会话创建请求应答消息，以及，接入设备向CP设备发送该PDU会话创建请求消息，接入设备接收来自CP设备的PDU会话创建请求应答消息。如此，可在并行完成固网和核心网的注册过程中，完成PDU会话的创建。
在一种可能的设计中，第一固网消息为DHCP发现消息，第二固网消息为DHCP提供消息或DHCP确认消息；或者第一固网消息为DHCP请求消息，所述第二固网消息为DHCP确认消息。即，本申请也适用于采用IPoE协议并行注册至固网和核心网。
第二方面，本申请提供一种注册方法，包括：
终端设备向接入设备发送第一固网消息，第一固网消息包括第一非接入层NAS消息，第一NAS消息用于请求注册至核心网，终端设备接收来自接入设备的第二固网消息，第二固网消息包括第二NAS消息，第二NAS消息用于指示核心网注册已完成。
上述方案，终端设备在注册至接入网的过程中，还将用于请求注册至核心网的NAS消息携带于固网消息中发送至接入设备，以便同时进行核心网的注册，以及通过固网消息指示核心网注册完成，实现了并行进行固网和核心网的注册，减少了终端设备注册至接入网及核心网的时间，同时，由于将NAS消息携带于固网消息中，因此也无需额外提供专门的数据通道用于传递NAS消息，提高了资源使用率。
在一种可能的设计中，第一固网消息为PADI消息，第二固网消息为PADO消息或PADS消息；或者第一固网消息为PADR消息，第二固网消息为PADS消息。如此，终端设备可在PPPoE发现过程中，实现固网和核心网的并行注册。
在一种可能的设计中，终端设备接收接入设备发送的PADO消息，PADO消息包括NAS鉴权请求消息；终端设备向接入设备发送PADR消息，PADR消息包括NAS鉴权信息。如此，可完成对终端设备的鉴权过程。
在一种可能的设计中，终端设备向接入设备发送第一请求消息，第一请求消息用于请求接入设备支持NAS的能力；终端设备接收来自接入设备的第一响应消息，第一响应消息用于指示所述接入设备支持NAS。如此，接入设备可将接入设备所支持的NAS的能力通知到终端设备，例如，接入设备支持NAS或不支持NAS。可选地，第一请求消息是携带在PADI消息中发送至接入设备的，第一响应消息是携带在PADO消息中发送至终端设备的。
在一种可能的设计中，终端设备向接入设备发送第二请求消息，第二请求消息用于请求NAS用户标识；终端设备接收来自接入设备的第二响应消息，第二响应消息用于指示终端设备的NAS用户标识。可选地，第二请求消息是携带在PADI消息中发送至接入设备的，第二响应消息是携带在PADO消息或PADS消息中发送至终端设备的；或者第二请求消息是携带在PADR消息中发送至接入设备的，第二响应消息是携带在PADS消息中发送至终端设备的。
在一种可能的设计中，终端设备向接入设备发送第三固网消息，第三固网消息包括PDU会话创建请求消息，PDU会话创建请求消息用于请求创建PDU会话；终端设备接收来自接入设备的第四固网消息，第四固网消息包括针对PDU会话创建请求消息的PDU会话创建请求应答消息。如此，可完成PDU会话的创建。
在一种可能的设计中，终端设备向接入设备发送第五固网消息，第五固网消息包括LCP配置请求消息；终端设备接收来自接入设备的IPCP消息，IPCP消息包括CP设备为终端设备分配的IP参数。如此，可在PPPoE会话过程中将CP设备分配的IP参数发送至终端设备。
在一种可能的设计中，第四NAS消息还包括IP参数，IP参数由终端设备作为PPPoE IP参数。如此，可取消PPPoE会话过程，同时也可向将为终端设备分配的IP参数发送至终端设备。
在一种可能的设计中，第一固网消息还包括PDU会话创建请求消息，PDU会话创建请求消息用于请求创建PDU会话，第二固网消息还包括针对PDU会话创建请求消息的PDU会话创建请求应答消息。如此，可在并行完成固网和核心网的注册过程中，也完成PDU会话的创建。
在一种可能的设计中，第一固网消息为DHCP发现消息，第二固网消息为DHCP提供消息或DHCP确认消息；或者第一固网消息为DHCP请求消息，第二固网消息为DHCP确认消息。即，本申请也适用于采用IPoE协议并行注册至固网和核心网。
第三方面，本申请实施例提供一种注册装置，该装置例如可以是接入设备，也可以是内置于接入设备或独立于接入设备的芯片，其中，接入设备，指的是接入核心网的设备，例如可以是基站，宽带网络业务网关(Broadband Network Gateway，BNG)，汇聚交换机，非3GPP接入设备等，该注册装置具有实现上述方法示例中接入设备的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
第四方面，本发明的实施例提供一种注册装置，包括：处理器、存储器、总线和通信接口；该存储器用于存储计算机执行指令，该处理器与该存储器通过该总线连接，当该设备运行时，该处理器执行该存储器存储的该计算机执行指令，以使该注册装置执行如上述 第一方面任意一项的注册方法。
第五方面，本申请实施例提供一种注册装置，该注册装置例如可以是终端设备，还可以是内置或独立于终端设备的芯片，该注册装置具有实现上述方法示例中终端设备行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
第六方面，本发明的实施例提供一种注册装置，包括：处理器、存储器、总线和通信接口；该存储器用于存储计算机执行指令，该处理器与该存储器通过该总线连接，当该设备运行时，该处理器执行该存储器存储的该计算机执行指令，以使该注册装置执行如上述第二方面任意一项的注册方法。
第七方面，本申请实施例提供了一种计算机存储介质，用于储存为上述各方面接入设备所用的计算机软件指令，其包含用于执行上述各方面为接入设备所设计的程序。
第八方面，本申请实施例提供了一种计算机存储介质，用于储存为上述各方面终端设备所用的计算机软件指令，其包含用于执行上述各方面为终端设备所设计的程序。
第九方面，本申请还提供了一种计算机程序产品。该计算机程序产品包括计算机软件指令，该计算机软件指令可通过处理器进行加载来实现上述第一方面中任意一项的注册方法中的流程。
第十方面，本申请还提供了一种计算机程序产品。该计算机程序产品包括计算机软件指令，该计算机软件指令可通过处理器进行加载来实现上述第二方面中任意一项的注册方法中的流程。
另外，第三方面至第十方面中任一种设计方式所带来的技术效果可参见第一方面和第二方面中的设计方式所带来的技术效果，此处不再赘述。
本发明的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
下面将参照所示附图对本申请实施例进行更详细的描述。
图1为本申请提供的应用场景示意图；
图2(a)为本申请提供的一种注册方法流程图；
图2(b)为本申请提供的另一种注册方法流程图；
图2(c)为本申请提供的另一种注册方法流程图；
图3为本申请提供的另一种注册方法流程图；
图4为本申请提供的另一种注册方法流程图；
图5为本申请提供的另一种注册方法流程图；
图6为本申请提供的另一种注册方法流程图；
图7为本申请提供的另一种注册方法流程图；
图8为本申请提供的另一种注册方法流程图；
图9为本申请提供的一种注册装置示意图；
图10为本申请提供的注册装置示意图；
图11为本申请提供的注册装置示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述。
本申请实施例提供一种注册方法及基于这个方法的注册装置，例如接入设备、终端设备等，用以减少终端设备注册至接入网及核心网的时间，以及提高资源使用率。其中，方法和装置是基于同一发明构思的，由于方法及装置解决问题的原理相似，因此装置与方法的实施可以相互参见，重复之处不再赘述。
本申请，终端设备在注册至接入网的过程中，还将用于请求注册至核心网的NAS消息携带于固网消息中发送至接入设备，以便同时进行核心网的注册，以及通过固网消息指示核心网注册完成，实现了并行进行固网和核心网的注册，减少了终端设备注册至接入网及核心网的时间，同时，由于将NAS消息携带于固网消息中，因此也无需额外提供专门的数据通道用于传递NAS消息，提高了资源使用率。
为更加清晰的描述本发明实施例的技术方案，下面结合图1，对本发明实施例可能的系统架构进行说明。
如图1所示，是本申请的一种可能的系统架构示意图，包括接入设备10和控制面(Control Plane，CP)设备20，终端设备通过有线连接与接入设备10进行通信，为清楚起见，图中只示出一个接入设备和一个终端设备。接入设备10与核心网(core network，CN)相连，核心网中的设备可分为控制面(Control Plane，CP)设备20和用户面(User Plane，UP)设备，控制面设备也可以称为控制面网元，用户面设备也可以称为用户面网元。本申请，接入设备10与CP设备20之间的通信接口称为第一接口，实际应用中，第一接口还可以有其它命名方式，例如，还可以称为N2接口，NG2接口等，随着通信的演变，在未来通信中，第一接口还可以有其它名称，本申请不做限定。
需要说明的是，控制面设备以及用户面设备仅是一个名字，名字本身对设备不构成限定。例如，该控制面设备也有可能被替换为“控制面实体”或其他名字。而且，该控制面设备也可以对应一个包括除了控制面功能外，还有其他功能的实体。用户面设备也有可能被替换为“用户面实体”或其他名字，而且，该用户面设备也可以对应一个包括除了用户面功能外，还有其他功能的实体。在此进行统一说明，以下不再赘述。
本申请中，控制面设备，主要包含用于实现接入与移动性管理的功能单元，如AMF网元，包含用于实现会话管理的功能单元，如会话管理功能(Session Management Function，SMF)网元，包含用于实现鉴权服务器的功能单元，如鉴权服务器功能(Authentication Server Function，AUSF)网元，包含用于实现用户数据管理的功能单元，如用户数据管理(User Data Management，UDM)网元，等等。
终端设备(Terminal Equipment)，主要指的是固定终端，例如包括数字用户线路(Digital Subscriber Line，DSL)调整解调器(modem)，pon终端，电缆调制解调器 (cable modem)等。
接入设备，指的是接入核心网的设备，例如可以是基站，BNG，汇聚交换机，非3GPP接入设备等，其中，当接入设备为基站时，基站具体包括但不限于：演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(Base Station Controller，BSC)、基站收发台(Base Transceiver Station，BTS)、家庭基站(例如，Home evolved NodeB，或Home Node B，HNB)、基带单元(BaseBand Unit，BBU)、新空口基站(g NodeB，gNB)、传输点(Transmitting and receiving point，TRP)、发射点(Transmitting point，TP)、移动交换中心等。
本申请实施例描述的网络架构是为了更加清楚的说明本申请实施例的技术方案，并不构成对本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本申请中，名词“网络”和“系统”经常交替使用，但本领域的技术人员可以理解其含义。
本申请中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
下面将结合附图，对本申请实施例所提供的方案进行更为详细的描述。
参考图2(a)，为本申请提供的注册方法流程图，包括以下步骤：
步骤201、终端设备向接入设备发送第一固网消息，接入设备接收该第一固网消息。
第一固网消息中包含第一NAS消息，第一NAS消息也可以称为NAS注册请求消息或注册请求消息等，第一NAS消息用于请求注册至核心网。
步骤202、接入设备向核心网的CP设备发送第一NAS消息，CP设备接收该第一NAS消息。
接入设备接收到终端设备发送的第一固网消息后，向CP设备发送第一NAS消息，第一NAS消息用于向CP设备请求注册至核心网。
步骤203、CP设备向接入设备发送NAS注册完成消息，接入设备接收该NAS注册完成消息。
CP设备在接收到接入设备发送的第一NAS消息后，对终端设备进行核心网的注册过程，若注册成功，则CP设备向接入设备发送NAS注册完成消息，当然，若注册失败，则上述步骤203由步骤203(a)代替，步骤203(a)：CP设备向接入设备发送NAS注册失败消息。
步骤204、接入设备向终端设备发送第二固网消息，终端设备接收该第二固网消息。
接入设备在接收到CP设备发送的NAS注册完成消息后，向终端设备发送第二固网消息，第二固网消息包括第二NAS消息，第二NAS消息用于指示核心网注册已完成。
若步骤203由步骤203(a)替代，则相应地，步骤204中发送的第二固网消息中包含的第二NAS消息由另一NAS消息替代，用于指示核心网注册失败。
上述方案，终端设备在注册至接入网的过程中，还将用于请求注册至核心网的NAS消息携带于固网消息中发送至接入设备，以便同时进行核心网的注册，以及通过固网消息指示核心网注册完成，实现了并行进行固网和核心网的注册，减少了终端设备注册至接入网 及核心网的时间，同时，由于将NAS消息携带于固网消息中，因此也无需额外提供专门的数据通道用于传递NAS消息，提高了资源使用率。
上述步骤中，终端设备与接入设备的交互是通过固网消息交互的，固网消息中包含NAS消息，具体地，可通过固网消息的厂商自定义信息来传递NAS消息。以采用PPPoE协议进行固网注册为例，若固网消息为PPPoE会话过程中的消息，例如可以使用PPPoE会话过程的链路控制协议(Link Control Protocol，LCP)报文中的厂商自定义信息来传递NAS消息，即LCP报文即为一个固网消息，其中的厂商自定义信息中携带有NAS消息，如上述第一NAS消息，第二NAS消息；类似地，还可以使用PPPoE发现过程的PPPoE报文中的厂商自定义信息来传递NAS消息，例如，在PPPoE报文中添加自定义类型的选项(option)，用于传递NAS消息，即PPPoE发现过程的PPPoE报文为固网消息，其中的厂商自定义信息中携带有NAS消息，如上述第一NAS消息，第二NAS消息。再比如，对于通过IPoE协议接入核心网的终端设备，可以采用类似PPPoE的方式，例如在DHCP获取IP的过程中，完成核心网注册，相应地，可在DHCP报文的厂商自定义消息中携带NAS消息。
需要说明的是，上述步骤201-步骤204的并行注册至固网(即接入网)和核心网的过程，可以是在基于PPPoE协议的不同阶段完成，例如在PPPoE的发现过程完成，或者是在PPPoE的会话过程完成，也可以是在基于IPoE的不同阶段完成，还可以是基于未来新的协议中的不同阶段完成，例如定义新的注册至固网的协议，则本申请可以基于新的协议完成终端设备并行注册至固网和核心网的流程。
本申请，接入设备与核心网的CP设备之间是通过第一接口通信的，第一接口例如可以是N2接口、NG2接口等，并且针对不同的终端设备或针对不同的会话标识，接入设备将使用不同的第一接口与CP设备通信，因此本申请图2(a)所示的注册流程中还包括建立用户标识和/或会话标识，与第一接口的对应关系。
为方便说明，下面结合附图2(a)，并以PPPoE为例进行说明，根据不同的应用场景，建立对应的关系将不同。
例如，若在上述步骤202之前，还未为终端设备分配PPPoE会话标识，则首先建立用户标识与第一接口的对应关系，其中用户标识可唯一标识一个终端设备，用户标识例如可以是终端所在的链路信息，媒体接入控制(Medium Access Control，MAC)地址+虚拟局域网(Virtual Local Area Network，VLAN)，设备编号等，对应关系可以以表格的形式存在，也可以以公式的形式，或者以图表方式存在等，本申请后续将以表格的形式来说明对应关系，例如，建立的对应关系如表1所示。
表1
用户标识 第一接口
ID1 接口2
在建立如表1所示的对应关系之后，若接入设备为终端设备分配了PPPoE会话标识，则可将PPPoE会话标识加入上述表1中，一种可能的方式中，增加的PPPoE会话标识改变 了用户标识对应的第一接口，例如表2所示。
表2
用户标识 PPPoE会话标识 第一接口
ID1 会话1 接口3
例如，若表2中的ID1标识的终端设备还对应有其它会话，则其它会话对应的第一接口可以与该终端设备的会话1对应的第一接口不同，例如如表3所示。
表3
用户标识 PPPoE会话标识 第一接口
ID1 会话1 接口3
ID1 会话2 接口2
ID1 会话3 接口4
另一种可能的方式中，增加的PPPoE会话标识不改变用户标识对应的第一接口，则在表1基础上增加PPPoE会话标识，得到如表4所示的结果。
表4
用户标识 PPPoE会话标识 第一接口
ID1 会话1 接口2
同样地，若表4中的ID1标识的终端设备还对应有其它会话，则其它会话对应的第一接口均与该终端设备的会话1对应的第一接口相同，如表5所示。
表5
用户标识 PPPoE会话标识 第一接口
ID1 会话1 接口2
ID1 会话2 接口2
ID1 会话3 接口2
再比如，在上述步骤202之前，接入设备为终端设备分配PPPoE会话标识，则接入设备进一步地还基于终端设备的用户标识分配第一接口，并建立对应关系，在建立对应关系时，可根据PPPoE会话标识建立对应关系，例如，当不同的终端设备的PPPoE会话标识互 不相同时，即在网络中的PPPoE会话标识是唯一的，则可以直接建立PPPoE会话标识与第一接口的对应关系；当然，若不同的终端设备的PPPoE会话标识可能相同，则可以建立用户标识和PPPoE会话标识这两项信息与第一接口的对应关系。需要说明的是，对于使用的第一接口，既可以是预先建立多个第一接口，在需要使用时，直接为终端设备分配相应的第一接口，也可以是在终端设备需要使用第一接口时，由接入设备创建第一接口并由终端设备使用，本申请对于第一接口的获取方式不做限定，既可以是分配第一接口，也可以是创建第一接口，后续不再说明。
譬如，如表6所示，是直接建立PPPoE会话标识与第一接口的对应关系。在上述表6所示的对应关系中，每个PPPoE会话标识在网络中时唯一的。
表6
PPPoE会话标识 第一接口
会话4 接口5
会话5 接口6
会话6 接口8
譬如，如表7所示，当PPPoE会话标识在网络中不唯一时，则可以结合用户标识和PPPoE会话标识，建立与第一接口的对应关系。
表7
用户标识 PPPoE会话标识 第一接口
ID2 会话1 接口4
ID2 会话2 接口3
ID2 会话3 接口1
ID3 会话1 接口5
ID3 会话2 接口7
ID3 会话3 接口9
譬如，若同一个终端设备只对应一个第一接口，即同一个终端设备的所有PPPoE会话标识对应的第一接口相同，则也可以直接建立如表8所示的用户标识与第一接口的对应关系。
表8
用户标识 第一接口
ID2 接口4
ID3 接口3
ID4 接口1
总之，在图2(a)所示的流程中，可以建立用户标识与第一接口的对应关系，同时，还可以将PPPoE会话标识加入该对应关系，建立PPPoE会话标识、用户标识，与第一接口的对应关系，使得接入设备可基于建立的对应关系，将接收到的来自终端设备的NAS消息，或接收到的来自终端设备的某个PPPoE会话标识对应的NAS消息，通过相应的第一接口发送至核心网的CP设备，以及，使得接入设备可基于建立的对应关系，将接收到的来自核心网的CP设备的某个第一接口的消息，发送至相应的终端设备。
例如，基于上述建立对应关系的方式，则上述步骤202中，接入设备向CP设备发送第一NAS消息的过程可以是：接入设备根据获取的用户标识，和/或PPPoE会话标识，及对应关系，确定第一接口，然后接入设备通过确定的第一接口，向CP设备发送第一NAS消息。
具体地，若对应关系是用户标识与第一接口的对应关系，则接入设备获取用户标识，并根据对应关系，确定相应的第一接口；若对应关系是PPPoE会话标识与第一接口的对应关系，则接入设备获取PPPoE会话标识，并根据对应关系，确定相应的第一接口；若对应关系是用户标识、PPPoE会话标识，与第一接口的对应关系，则接入设备获取用户标识、PPPoE会话标识，并根据对应关系，确定相应的第一接口。
再比如，基于上述建立对应关系的方式，则上述步骤204中，接入设备向终端设备发送第二固网消息的过程可以是：若对应关系为PPPoE会话标识与第一接口的对应关系；则接入设备根据接收NAS注册完成消息的第一接口，及对应关系，确定PPPoE会话标识，并向PPPoE会话标识对应的终端设备发送该第二固网消息；若对应关系为用户标识和PPPoE会话标识，与第一接口的对应关系，或者是，对应关系为用户标识与第一接口的对应关系，则接入设备根据接收NAS注册完成消息的第一接口，及对应关系，确定用户标识，并向用户标识对应的终端设备发送该第二固网消息。
本申请，以PPPoE为例，则上述注册方法可以是在PPPoE发现过程实现，也可以是在PPPoE发现过程之后实现，例如，当在PPPoE发现过程实现上述注册方法时，则第一固网消息可以是PPPoE主动发现开始(PPPoE Active Discovery Initiation，PADI)消息，第二固网消息为PPPoE主动发现提供(PPPoE Active Discovery Offer，PADO)消息或PPPoE主动发现会话确认(PPPoE Active Discovery Session-confirmation，PADS)消息；或者，第一固网消息为PPPoE主动发现请求(PPPoE Active Discovery Request，PADR)消 息，所述第二固网消息为PADS消息。
本申请，以IPoE为例，则上述则上述注册方法可以是在IPoE发现过程实现，也可以是在IPoE发现过程之后实现，例如，当在IPoE发现过程实现上述注册方法时，则第一固网消息为动态主机配置协议(Dynamic Host Configuration Protocol，DHCP)发现(Discover)消息，第二固网消息为DHCP提供(Offer)消息或DHCP确认(Ack)消息；或者第一固网消息为DHCP请求(Request)消息，第二固网消息为DHCP确认(Ack)消息。
在一种可能的设计中，接入设备还向终端设备发送PADO消息，PADO消息包括NAS鉴权请求消息，接入设备接收终端设备发送的PADR消息，PADR消息包括NAS鉴权信息，接入设备向CP设备发送该NAS鉴权信息。该过程用于完成对终端设备的鉴权认证。
在一种可能的设计中，以PPPoE为例，终端设备还可以显示地请求接入设备支持NAS的能力，例如请求确定接入设备是否支持NAS，若终端设备确定接入设备支持NAS，则终端设备、接入设备及CP设备之间可通过本申请提供的注册方法完成终端设备向固网(即接入网)和核心网的并行注册，若终端设备确定接入设备不支持NAS，则终端设备、接入设备及CP设备之间将使用背景技术中提到的传统注册方法，完成到固网及核心网的注册。
可选地，终端设备在PADI消息中携带第一请求消息，第一请求消息用于请求所述接入设备支持NAS的能力，接入设备接收来自所述终端设备的第一请求消息，并根据自身支持NAS的能力，向终端设备发送响应消息，若发送的是第一响应消息，且第一响应消息可以是携带在PADO消息中发送至终端设备的，第一响应消息用于确定所述接入设备支持NAS，则终端设备确定接入设备支持NAS，因此可按照图2(a)所示的注册方法对终端设备进行注册；若接入设备向终端设备发送的是其它响应消息，且该响应消息用于确定接入设备不支持NAS，则终端设备确定接入设备不支持NAS，因此不按照图2(a)所示的注册方法进行注册，而是按照其它方法进行注册，例如终端设备、接入设备及CP设备之间使用背景技术中提到的传统注册方法，完成到固网及核心网的注册。
在一种可能的设计中，若图2(a)中第一固网消息为PADI消息，第二固网消息为PADO消息，则第一请求消息是携带于第一固网消息中发送至接入设备，第一响应消息是携带于第二固网消息中发送至终端设备。
在一种可能的设计中，以PPPoE为例，终端设备还可以隐式地请求接入设备支持NAS的能力，例如请求确定接入设备是否支持NAS，示例性地，参照图2(a)，终端设备向接入设备发送第一固网消息，第一固网消息中携带第一NAS消息，若终端设备接收到的第二固网消息中不是第二NAS消息，则隐式指示接入设备不支持NAS，一种可能的实现方式为，在第二固网消息中不包含任何NAS消息，则终端设备确定接入设备不支持NAS，或者，在第二固网消息中携带第一NAS消息，则终端设备也确定接入设备不支持NAS，当然，还可以有其它隐式指示的方式，本申请不做限定。
不论是隐式指示或显示指示，只要终端设备确定接入设备支持NAS，则可以按照本申请注册方法，对终端设备进行并行注册至固网和核心网，若确定接入设备不支持NAS，则终端设备、接入设备及CP设备之间使用背景技术中提到的传统注册方法，完成到固网及核心网的注册。
在一种可能的设计中，终端设备还可以向接入设备请求获取NAS用户标识，作为终端 设备与接入设备之间发送NAS消息时所使用的标识，NAS用户标识例如可以是MAC地址、用户标识、端口号、用户链路信息，或者根据规则生成的值，或者是为用户配置的值等，之所以需要终端设备向接入设备请求一个NAS用户标识，具有以下好处：一方面，可以根据链路信息为终端设备生成用户标识，而终端设备不需要感知自己的链路及位置信息，提高接入安全性，符合固网接入的特性；另一方面，终端设备可以做统一管理，终端设备不需要写入特殊的标识信息。
具体地，在图2(a)所示的注册方法中，还包括：终端设备向接入设备发送第二请求消息，用于请求NAS用户标识，接入设备接收来自终端设备的第二请求消息，并向终端设备发送第二响应消息，第二响应消息用于指示终端设备的NAS用户标识。其中，第二响应消息指示NAS用户标识的方法不限定，例如可以是在第二响应消息中显示携带为终端设备分配的NAS用户标识，也可以是在第二响应消息中不携带NAS用户标识，则终端设备在未从第二响应消息中获取到NAS用户标识时，可根据预先约定的规则，例如可以将自身的用户标识作为NAS用户标识等。可选地，第二请求消息是携带在PADI消息中发送至接入设备的，第二响应消息是携带在PADO消息或PADS消息中发送至终端设备的；或者，第二请求消息是携带在PADR消息中发送至接入设备的，第二响应消息是携带在PADS消息中发送至终端设备的。当然，如果后续增加了新的固网协议，则上述第一请求消息、第一响应消息、第二请求消息、第二响应消息，均可以通过新的协议中的相应消息来发送，并且，本申请注册方法的其它固网消息也均可以在新的协议下完成收发，本申请对此不做限定。
基于上述描述的注册方法，本申请还可以结合上述注册方法创建PDU会话，至少包含以下两种方法。
第一种方法，可参照图2(b)所示，为本申请提供的注册方法，其包含图2(a)所示的步骤201-204，并且在这之后，还包括以下步骤：
步骤205、终端设备向接入设备发送第三固网消息，接入设备接收该第三固网消息。
第三固网消息包括分组数据单元(Packet Data Unit，PDU)会话创建请求消息，PDU会话创建请求消息用于请求创建PDU会话。
步骤206、接入设备向CP设备发送PDU会话创建请求消息，CP设备接收该PDU会话创建请求消息。
步骤207、CP设备向接入设备发送针对PDU会话创建请求消息的PDU会话创建请求应答消息，接入设备接收该PDU会话创建请求应答消息。
步骤208、接入设备向终端设备发送第四固网消息，终端设备接收该第四固网消息。
第四固网消息包括PDU会话创建请求应答消息。
可选地，在图2(b)所示的步骤201-步骤208中，以PPPoE为例，其可以包含PPPoE会话过程，也可以不包含PPPoE会话过程，例如，当包含PPPoE会话过程时，图2(b)所示的注册方法还包括：接入设备接收来自终端设备的第五固网消息，第五固网消息包括LCP配置请求消息，接入设备向终端设备发送IPCP消息，IPCP消息包括CP设备为终端设备分配的IP参数。可选地，第五固网消息可以是在步骤205之前、之后，或同时发送至接入设备，IPCP消息可以是在步骤208之前、之后，或同时发送至终端设备。
再比如，当图2(b)所示的步骤201-步骤208中，不包含PPPoE会话过程时，则CP设 备为终端设备分配的IP参数可以通过以下方式发送至终端设备，可选地，在步骤207中的PDU会话创建请求应答消息中包含IP参数，以及步骤208中，接入设备将该IP参数通过第四固网消息发送至终端设备，且该IP参数由终端设备作为PPPoE IP参数。
第二种方法，可参照图2(c)所示，为本申请提供的注册方法，其类似图2(a)所示的步骤201-204，完成PDU会话的创建，具体包括以下步骤：
步骤201'、终端设备向接入设备发送第一固网消息，接入设备接收该第一固网消息。
第一固网消息中包括第一NAS消息和PDU会话创建请求消息。
步骤202'、接入设备向核心网的CP设备发送第一NAS消息和PDU会话创建请求消息，CP设备接收该第一NAS消息和PDU会话创建请求消息。
接入设备接收到终端设备发送的第一固网消息和PDU会话创建请求消息后，向CP设备发送第一NAS消息和PDU会话创建请求消息。
步骤203'、CP设备向接入设备发送NAS注册完成消息和PDU会话创建请求应答消息，接入设备接收该NAS注册完成消息和PDU会话创建请求应答消息。
步骤204'、接入设备向终端设备发送第二固网消息，终端设备接收该第二固网消息。
接入设备在接收到CP设备发送的NAS注册完成消息和PDU会话创建请求应答消息后，向终端设备发送第二固网消息，第二固网消息包括第二NAS消息和和PDU会话创建请求应答消息。
上述步骤201'-步骤204'是在步骤201-步骤204的基础上，增加了PDU会话创建过程，步骤201'-步骤204'中的固网和核心网的注册流程可参照前述描述，不再赘述。
本申请，终端设备在注册至接入网的过程中，还将用于请求注册至核心网的NAS消息携带于固网消息中发送至接入设备，以便同时进行核心网的注册，以及通过固网消息指示核心网注册完成，实现了并行进行固网和核心网的注册，减少了终端设备注册至接入网及核心网的时间，同时，由于将NAS消息携带于固网消息中，因此也无需额外提供专门的数据通道用于传递NAS消息，提高了资源使用率。以及，在注册过程中，还可以创建PDU会话，进一步提高了注册效率。
下面结合附图3-附图8，对本申请提供的注册方法做具体说明。
如图3所示，为本申请提供的另一种注册方法流程图，该注册方法以固网协议为PPPoE为例，注册过程包括以下步骤：
步骤1、终端设备向接入设备发送PADI消息，接入设备接收该PADI消息。
步骤2、接入设备向终端设备发送PADO消息，终端设备接收该PADO消息。
步骤3、终端设备向接入设备发送PADR消息，接入设备接收该PADR消息。
上述步骤1-步骤3为现有技术中的终端设备和接入设备之间进行PPPoE发现过程中的PADI，PADO，PADR交互，不再赘述。
步骤4、接入设备为终端设备分配PPPoE会话标识，根据用户标识分配第一接口，同时记录对应关系。
其中，对应关系可以是PPPoE会话标识与第一接口的对应关系，也可以是用户标识、PPPoE会话标识，与第一接口的对应关系。
步骤5、接入设备向终端设备发送PADS消息，终端设备接收该PADS消息。
上述步骤5与上述步骤1-步骤3，构成了PPPoE发现过程中的四个交互动作。
其中，在PADS消息中包括为终端设备分配的PPPoE会话标识。
步骤6、终端设备向接入设备发送第一固网消息，第一固网消息中包含第一NAS消息，接入设备接收该第一固网消息。
这里，第一NAS消息也可以称为NAS注册请求消息，用于请求注册至核心网。
在具体实现中，可以在第一固网消息的厂商自定义字段中携带第一NAS消息。
步骤7、接入设备根据对应关系，确定第一接口。
例如，接入设备根据用户标识，和/或第一固网消息中的PPPoE会话标识，确定对应的第一接口。本实施例中，后续接入设备通过第一接口发送消息到CP设备，都是采用同样的方法确定对应的第一接口。
步骤8、接入设备通过确定的第一接口向CP设备发送第一NAS消息，CP设备接收该第一NAS消息。
步骤9、CP设备对终端设备注册完成后，发送NAS注册完成消息至接入设备，接入设备接收该NAS注册完成消息。
其中，CP设备是通过第一接口发送NAS注册完成消息的。
步骤10、CP设备向接入设备发送N2消息，接入设备接收该N2消息，N2消息中包含用户标识。
接入设备可根据用户标识，确定相应的终端设备。
步骤11、接入设备向终端设备发送第二固网消息，终端设备接收该第二固网消息。
第二固网消息中包含第二NAS消息，用于指示核心网注册已完成。其中，第二NAS消息可封装在第二固网消息的厂商自定义字段中，例如第二固网消息为LCP报文，则可以封装在LCP报文中。
步骤12、终端设备发送第三固网消息和第五固网消息至接入设备，接入设备接收该第三固网消息和第五固网消息。
第三固网消息中包含PDU创建请求消息，用于请求创建PDU会话，第五固网消息中包含LCP配置请求消息。
步骤13、接入设备通过第一接口发送PDU会话创建请求消息至CP设备，CP设备接收该PDU会话创建请求消息。
步骤14、CP设备通过第一接口发送PDU会话创建请求应答消息到接入设备，接入设备接收该PDU会话创建请求应答消息。
PDU会话创建请求应答消息中包含为终端设备分配的IP参数。
步骤15、接入设备向终端设备发送IPCP消息，终端设备接收该IPCP消息。
IPCP消息中包含CP设备为终端设备分配的IP参数。
图3所示的注册方法，通过在PPPoE会话阶段，使用PPPoE固网消息中的厂商自定义字段承载NAS消息，在PPPoE信令交互过程中，同时进行终端设备到核心网的认证流程，并且还兼顾了现有的PPPoE注册过程，以及核心网的注册过程，一方面减少了注册时间，另一方面，由于无需建立专门的数据通道用于专递NAS消息，因而提高了资源利用率。
如图4所示，为本申请提供的另一种注册方法流程图，该注册方法以固网协议为PPPoE为例，该注册方法包括以下步骤：
步骤1-步骤11，与图3所示的注册方法的步骤1-步骤11相同，可参考前述描述。
步骤12、终端设备发送第三固网消息至接入设备，接入设备接收该第三固网消息。
第三固网消息中包含PDU创建请求消息，用于请求创建PDU会话。
步骤13、接入设备通过第一接口发送PDU会话创建请求消息至CP设备，CP设备接收该PDU会话创建请求消息。
步骤14、CP设备通过第一接口发送PDU会话创建请求应答消息到接入设备，接入设备接收该PDU会话创建请求应答消息。
PDU会话创建请求应答消息中包含为终端设备分配的IP参数。
步骤15、接入设备向终端设备发送第四固网消息，终端设备接收该第四固网消息。
其中，第四固网消息中包含CP设备为终端设备分配的IP参数。
图4所示的注册方法，与图3所示的注册方法，主要区别在于：取消了图3所示的注册方法中的PPPoE会话过程，不再使用IPCP消息传递IP参数给终端设备，而是使用NAS消息传递IP参数给终端设备，进一步简化了注册流程，且达到了PPPoE注册的目的。
如图5所示，为本申请提供的另一种注册方法流程图，图5所示的实施例是在图4所示的实施例的基础上，将第一NAS消息携带于PADI消息中发送至接入设备，将第二NAS消息携带于PADS消息发送至终端设备，即，第一固网消息为PADI消息，第二固网消息为PADS消息，该注册方法包括以下步骤：
步骤1、终端设备向接入设备发送PADI消息，接入设备接收该PADI消息。
PADI消息中包含第一NAS消息。这里，第一NAS消息也可以称为NAS注册请求消息，用于请求注册至核心网。
步骤2、接入设备根据用户标识，分配第一接口，并建立对应关系。
步骤3、接入设备根据对应关系，确定终端设备对应的第一接口。
步骤4、接入设备通过确定的第一接口向CP设备发送第一NAS消息，CP设备接收该第一NAS消息。
需要说明的是，后续接入设备向CP设备发送NAS消息时，均通过该方法确定相应的第一接口发送NAS消息。
步骤5、CP设备向接入设备发送鉴权请求，接入设备接收该鉴权请求。
该步骤为可选步骤，相应地，如果执行步骤5，则在步骤6中携带鉴权请求、步骤7中携带鉴权信息，以及包括步骤8。
步骤6、接入设备向终端设备发送PADO消息，终端设备接收该PADO消息。
可选地，PADO消息中包含鉴权请求消息。
步骤7、终端设备向接入设备发送PADR消息，接入设备接收该PADR消息。
可选地，PADR消息中包含鉴权信息。
步骤8、接入设备向CP设备发送鉴权信息，CP设备接收该鉴权信息。
该步骤为可选步骤。
步骤9、CP设备通过第一接口向终端设备发送NAS注册完成消息，终端设备接收该NAS注册完成消息。
步骤10、接入设备为终端设备分配PPPoE会话标识，并将PPPoE会话标识加入到前述对应关系。
步骤11、接入设备向终端设备发送PADS消息，终端设备接收该PADS消息。
其中，在PADS消息中包含为终端设备分配的PPPoE会话标识，以及还包括第二NAS消息，第二NAS消息用于指示注册核心网已完成。
步骤12-步骤15与图4所示的注册方法的步骤12-步骤15相同，可参照前述描述，不再赘述。
图5所示的注册方法，将核心网注册过程的部分流程提前到了PPPoE发现过程，提高了注册过程的效率。
如图6所示，为本申请提供的另一种注册方法流程图，该注册方法以固网协议为PPPoE为例，在图6所示的实施例中，在PPPoE发现过程中，通过PPPoE厂商定义类型的选项，定义NAS协商消息，例如可以定义以下几种类型的消息：
1、NAS support request：请求接入设备的服务器是否支持NAS。
本申请，NAS support request也称为第一请求消息。
2、NAS support ack：标识服务器支持NAS，并可以应答NAS相关信息。
本申请，NAS support ack也称为第一响应消息。
3、NAS用户标识请求消息：请求用户在发送NAS消息将使用的NAS用户标识。
本申请，NAS用户标识请求消息也称为第二请求消息。
其中，NAS用户标识为服务器返回分配给用户的标识，或者是服务器指定用户用作用户标识的信息，如MAC地址等。
4、NAS用户标识请求响应消息：用于指示终端设备的NAS用户标识。
本申请，NAS用户标识请求响应消息也称为第二响应消息。
图6所示的注册方法是在图4所示的注册方法基础上，修改了步骤1-步骤5，下面对图6所示的注册方法中的步骤1-步骤5进行说明，包括：
步骤1、终端设备发送PADI消息至接入设备，接入设备接收该PADI消息。
在PADI消息中包含第一请求消息，用于请求接入设备是否支持NAS消息。
步骤2、接入设备发送PADO消息至终端设备，终端设备接收该PADO消息。
PADO消息中包含第一响应消息，用于告知终端设备接入设备支持NAS，即可以使用NAS消息。
当然，PADO中也有可能携带NAS support Reject，或者其他不能识别的消息，或者是复制的步骤1中终端设备发送的第一请求消息，用以说明接入设备不支持NAS，在该情形下，则终端设备将不执行后续步骤3-步骤15，而是按照传统注册方法对终端设备进行固网和核心网的注册，具体流程可参考现有技术。
步骤3、终端设备向接入设备发送PADR消息，接入设备接收该PADR消息。
在PADR消息中，包含第二请求消息，用于请求NAS用户标识，并且，该第二请求消 息为可选项，即，也可以不请求NAS用户标识，该情况下，则使用终端设备自身的用户标识。
步骤4、接入设备分配PPPo会话标识，以及，分配NAS用户标识，并建立对应关系。
其中，建立对应关系的方法可参照图4所示的实施例中的描述，此处不赘述。
步骤5、接入设备向终端设备发送PADS消息，终端设备接收该PADS消息。
若步骤3中终端设备请求分配用户NAS标识，那么接入设备在PADS中添加第二响应消息，用于指示NAS标识信息，或者，还可以是指定终端设备用于作为NAS用户标识的信息类型，例如MAC地址等。
需要说明的是，用户NAS标识信息是可选内容，即使步骤3中终端设备请求了用户NAS标识，终端设备也可以不向终端设备返回用户NAS标识信息，即PADS消息中不携带第二响应消息，这种情况下，终端设备可根据预设的规则，使用约定信息作为NAS用户标识，例如使用自身用户标识作为NAS用户标识。
步骤6-步骤15与图4所示的注册方法中的步骤6-步骤15相同，则参照前述描述，这里不再赘述。
本方案相较于图4所示的注册方法，在PPPoE过程中增加了接入设备的NAS能力请求过程，使得终端设备、接入设备、CP设备可选择相应的注册方法进行注册，例如使用本申请提供的方法，或使用现有技术提供的注册方法。
如图7所示，为本申请提供的另一种注册方法流程图，其中，在图5所示的注册方法基础上，将步骤12-步骤15的PDU会话创建过程加入到步骤1-步骤11的注册过程中，同时发起，进一步提高注册效率，包括以下步骤：
步骤1、终端设备向接入设备发送PADI消息，接入设备接收该PADI消息。
PADI消息中包含第一NAS消息、PDU会话创建请求消息。这里，第一NAS消息也可以称为NAS注册请求消息，用于请求注册至核心网。
步骤2、接入设备根据用户标识，分配第一接口，并建立对应关系。
步骤3、接入设备根据对应关系，确定终端设备对应的第一接口。
步骤4、接入设备通过确定的第一接口发送第一NAS消息、PDU会话创建请求消息。
需要说明的是，后续接入设备向CP设备发送NAS消息时，均通过该方法确定相应的第一接口发送NAS消息。
步骤5、CP设备向接入设备发送鉴权请求，接入设备接收该鉴权请求。
该步骤为可选步骤，相应地，如果执行步骤5，则在步骤6中携带鉴权请求、步骤7中携带鉴权信息，以及包括步骤8。
步骤6、接入设备向终端设备发送PADO消息，终端设备接收该PADO消息。
可选地，PADO消息中包含鉴权请求消息。
步骤7、终端设备向接入设备发送PADR消息，接入设备接收该PADR消息。
可选地，PADR消息中包含鉴权信息。
步骤8、接入设备向CP设备发送鉴权信息，CP设备接收该鉴权信息。
该步骤为可选步骤。
步骤9、CP设备通过第一接口向终端设备发送NAS注册完成消息、PDU会话创建完成消息，终端设备接收该NAS注册完成消息、PDU会话创建完成消息。
其中，PDU会话创建完成消息包含CP设备为终端设备分配的IP参数。
步骤10、接入设备为终端设备分配PPPoE会话标识，并将PPPoE会话标识加入到前述对应关系。
步骤11、接入设备向终端设备发送PADS消息，终端设备接收该PADS消息。
其中，在PADS消息中包含为终端设备分配的PPPoE会话标识，包括第二NAS消息，第二NAS消息用于指示注册核心网已完成、以及还包括PDU会话创建完成消息，其中包括为终端设备分配的IP参数。
如图8所示，为本申请提供的另一种注册方法流程图，该注册方法以固网协议为IPoE为例，其与图7所示的注册过程类似，包括以下步骤：
步骤1、终端设备向接入设备发送DCHP发现消息，接入设备接收该DCHP发现消息。
DCHP发现消息中包含第一NAS消息、PDU会话创建请求消息。这里，第一NAS消息也可以称为NAS注册请求消息，用于请求注册至核心网。
步骤2、接入设备根据用户标识，分配第一接口，并建立对应关系。
步骤3、接入设备根据对应关系，确定终端设备对应的第一接口。
步骤4、接入设备通过确定的第一接口向CP设备发送第一NAS消息、PDU会话创建请求消息，CP设备接收该第一NAS消息、PDU会话创建请求消息。
需要说明的是，后续接入设备向CP设备发送NAS消息时，均通过该方法确定相应的第一接口发送NAS消息。
步骤5、CP设备向接入设备发送NAS注册完成消息、N2PDU会话请求消息，接入设备接收该NAS注册完成消息、N2PDU会话请求消息。
其中，N2PDU会话请求消息中包含CP设备为终端设备分配的IP参数。
步骤6、接入设备向终端设备发送DHCP提供消息，终端设备接收该DHCP提供消息。
其中，DHCP提供消息中包含N2PDU会话请求应答消息。
步骤7、终端设备向接入设备发送DHCP请求消息，接入设备接收该DHCP请求消息。
其中，DHCP请求消息中包含N2PDU护花请求应答消息。
步骤8、接入设备向CP设备发送N2PDU会话请求应答消息，CP设备接收该N2PDU会话请求应答消息。
步骤9、接入设备向终端设备发送DHCP确认消息，终端设备接收该DHCP确认消息。
本发明通过在DHCP获取IP的过程中，将NAS消息携带于DHCP消息(或称为DCHP报文)中，并行完成DHCP流程以及在核心网的注册及PDU会话创建过程，可提高注册效率。
需要说明的是，图3-图8所示的实施例，仅仅是作为几种可能的实现方式，在实际应用中，还有可能有其它具体实现方式，可参照本申请前文描述，此处不再例举。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，各个网元，例如终端设备、接入设备、核心网的CP设备，为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识 到，结合本文所公开的实施例描述的各示例的模块及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同的方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
如图9所示，图1中的终端设备、控制面设备，可以以图9中的注册装置的方式来实现。图9所示为本发明实施例提供的注册装置示意图。注册装置900包括至少一个处理器91，通信总线92，存储器93以及至少一个通信接口94。
处理器91可以是一个通用中央处理器(CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本发明方案程序执行的集成电路。
通信总线92可包括一通路，在上述组件之间传送信息。所述通信接口94，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(RAN)，无线局域网(Wireless Local Area Networks，WLAN)等。
存储器93可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、只读光盘(Compact Disc Read-Only Memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过总线与处理器相连接。存储器也可以和处理器集成在一起。
其中，所述存储器93用于存储执行本发明方案的应用程序代码，并由处理器91来控制执行。所述处理器91用于执行所述存储器93中存储的应用程序代码。
在具体实现中，作为一种实施例，处理器91可以包括一个或多个CPU，例如图9中的CPU0和CPU1。
在具体实现中，作为一种实施例，注册装置900可以包括多个处理器，例如图9中的处理器91和处理器98。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中，作为一种实施例，当注册装置900为接入设备或终端设备时，注册装置900还可以包括输出设备95和输入设备96。输出设备95和处理器91通信，可以以多种方式来显示信息。例如，输出设备95可以是液晶显示器(liquid crystal display，LCD),发光二级管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备96和处理器91通信，可以以多种方式获取外界信息、或接受用户的输入。例如，输入设备96可以是摄像头、鼠标、键盘、触摸屏设备或传感设备等。
示例性的，图1中的接入设备可以为图9所示的设备，控制面设备的存储器中存储了 一个或多个软件模块。控制面设备可以通过处理器以及存储器中的程序代码来实现软件模块，实现终端设备注册至固网和核心网。
又或者，图1中的终端设备可以为图9所示的设备，终端设备的存储器中存储了一个或多个软件模块。终端设备可以通过处理器以及存储器中的程序代码来实现软件模块，实现终端设备注册至固网和核心网。
本发明实施例可以根据上述方法示例对终端设备或接入设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本发明实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
比如，在采用对应各个功能划分各个功能模块的情况下，图10示出了上述实施例中所涉及的一种实现注册装置可能的结构示意图，该装置1000包括：接收单元1001，处理单元1002，发送单元1003，其中：
接收单元1001，用于接收来自终端设备的第一固网消息，所述第一固网消息包括第一非接入层NAS消息，所述第一NAS消息用于请求注册至核心网；
发送单元1003，用于向核心网控制面CP设备发送所述第一NAS消息；
所述接收单元1001，还用于接收来自所述CP设备的NAS注册完成消息；
所述发送单元1003，还用于向终端设备发送第二固网消息，所述第二固网消息包括第二NAS消息，所述第二NAS消息用于指示核心网注册已完成。
可选地，处理单元1002，用于记录对应关系，所述对应关系为所述终端设备的用户标识，和/或基于以太网的点对点协议PPPoE会话标识与第一接口的对应关系，所述PPPoE会话标识为所述接入设备为所述终端设备分配的,所述第一接口为接入设备与用于实现接入与移动性管理的功能单元之间的接口。
可选地，所述发送单元1003，用于向核心网控制面CP设备发送所述第一NAS消息，具体包括：所述发送单元1003，根据获取的用户标识，和/或PPPoE会话标识，及所述对应关系，确定第一接口；通过确定的所述第一接口，向所述CP设备发送所述第一NAS消息。
可选地，对应关系为PPPoE会话标识与第一接口的对应关系；所述发送单元1003，还用于向所述终端设备发送第二固网消息，具体包括：所述发送单元1003，根据接收所述NAS注册完成消息的第一接口，及所述对应关系，确定PPPoE会话标识；向所述PPPoE会话标识对应的所述终端设备发送所述第二固网消息。
可选地，对应关系为用户标识和PPPoE会话标识，与第一接口的对应关系，或，所述对应关系为用户标识与第一接口的对应关系；所述发送单元1003，还用于向所述终端设备发送第二固网消息，具体包括：所述发送单元1003，根据接收所述NAS注册完成消息的第一接口，及所述对应关系，确定用户标识；向所述用户标识对应的所述终端设备发送所述第二固网消息。
可选地，所述第一固网消息为PPPoE主动发现开始PADI消息，所述第二固网消息为 PPPoE主动发现提供PADO消息或PPPoE主动发现会话确认PADS消息；或者所述第一固网消息为PPPoE主动发现请求PADR消息，所述第二固网消息为PADS消息。
可选地，发送单元1003，还用于向所述终端设备发送PADO消息，所述PADO消息包括NAS鉴权请求消息；接收单元1001，还用于接收所述终端设备发送的PADR消息，所述PADR消息包括NAS鉴权信息；发送单元1003，还用于向所述CP设备发送所述NAS鉴权信息。
可选地，接收单元1001，还用于接收来自所述终端设备的第一请求消息，所述第一请求消息用于请求所述接入设备支持NAS的能力；发送单元1003，还用于向所述终端设备发送第一响应消息，所述第一响应消息用于确定所述接入设备支持NAS。
可选地，所述第一请求消息是携带在PADI消息中发送至所述接入设备的，所述第一响应消息是携带在PADO消息中发送至所述终端设备的。
可选地，接收单元1001，还用于接收来自所述终端设备的第二请求消息，所述第二请求消息用于请求NAS用户标识；发送单元1003，还用于向所述终端设备发送第二响应消息，所述第二响应消息用于指示所述终端设备的NAS用户标识。
可选地，所述第二请求消息是携带在PADI消息中发送至所述接入设备的，所述第二响应消息是携带在PADO消息或PADS消息中发送至所述终端设备的；或者所述第二请求消息是携带在PADR消息中发送至所述接入设备的，所述第二响应消息是携带在PADS消息中发送至所述终端设备的。
可选地，接收单元1001，还用于接收来自所述终端设备的第三固网消息，所述第三固网消息包括分组数据单元PDU会话创建请求消息，所述PDU会话创建请求消息用于请求创建PDU会话；发送单元1003，还用于向所述CP设备发送PDU会话创建请求消息；接收单元1001，还用于接收来自所述CP设备的针对所述PDU会话创建请求消息的PDU会话创建请求应答消息；发送单元1003，还用于向所述终端设备发送第四固网消息，所述第四固网消息包括所述PDU会话创建请求应答消息。
可选地，所述第四NAS消息还包括网络之间互连协议IP参数，所述IP参数由所述终端设备作为PPPoE IP参数。
可选地，接收单元1001，还用于接收来自所述终端设备的第五固网消息，所述第五固网消息包括链路控制协议LCP配置请求消息；发送单元1003，还用于向所述终端设备发送网络之间互连协议控制协议IPCP消息，所述IPCP消息包括所述CP设备为所述终端设备分配的IP参数。
可选地，所述第一固网消息还包括PDU会话创建请求消息，所述PDU会话创建请求消息用于请求创建PDU会话；所述第二固网消息还包括针对所述PDU会话创建请求消息的PDU会话创建请求应答消息；发送单元1003，还用于向所述CP设备发送所述PDU会话创建请求消息；接收单元1001，还用于接收来自所述CP设备的所述PDU会话创建请求应答消息。
可选地，所述第一固网消息为动态主机配置协议DHCP发现消息，所述第二固网消息为DHCP提供消息或DHCP确认消息；或者所述第一固网消息为DHCP请求消息，所述第二固网消息为DHCP确认消息。
其中，该装置1000可以为接入设备，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该实现注册装置以对应各个功能划分各个功能模块的形式来呈现，或者，该实现注册装置以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定应用集成电路(application-specific integrated circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到实现注册装置1000可以采用图9所示的形式。比如，图10中的接收单元1001、处理单元1002、发送单元1003可以通过图9的处理器91(和/或处理器98)和存储器93来实现，具体的，接收单元1001、处理单元1002或发送单元1003可以通过由处理器91(和/或处理器98)来调用存储器93中存储的应用程序代码来执行，本发明实施例对此不作任何限制。
比如，在采用对应各个功能划分各个功能模块的情况下，图11示出了上述实施例中所涉及的另一种实现注册装置可能的结构示意图，该装置1100包括：接收单元1101，处理单元1102，发送单元1103，其中：
发送单元1103，用于向接入设备发送第一固网消息，所述第一固网消息包括第一非接入层NAS消息，所述第一NAS消息用于请求注册至核心网；接收单元1101，用于接收来自所述接入设备的第二固网消息，所述第二固网消息包括第二NAS消息，所述第二NAS消息用于指示核心网注册已完成。可选地，所述第一固网消息为PADI消息，所述第二固网消息为PADO消息或PADS消息；或者所述第一固网消息为PADR消息，所述第二固网消息为PADS消息。
可选地，所述接收单元1101，还接收所述接入设备发送的PADO消息，所述PADO消息包括NAS鉴权请求消息；所述发送单元1103，还向所述接入设备发送PADR消息，所述PADR消息包括NAS鉴权信息。
可选地，所述发送单元1103还用于向所述接入设备发送第一请求消息，所述第一请求消息用于请求所述接入设备支持NAS的能力；所述接收单元1101还用于接收来自所述接入设备的第一响应消息，所述第一响应消息用于指示所述接入设备支持NAS。
可选地，所述第一请求消息是携带于PADI消息发送至所述接入设备的，所述第一响应消息是携带于PADO消息发送至所述终端设备的。
可选地，所述发送单元1103向所述接入设备发送第二请求消息，所述第二请求消息用于请求NAS用户标识；所述接收单元1101，还接收来自所述接入设备的第二响应消息，所述第二响应消息用于指示所述终端设备的NAS用户标识。可选地，所述第二请求消息是携带于PADI消息发送至所述接入设备的，所述第二响应消息是携带于PADO消息或PADS消息发送至所述终端设备的；或者所述第二请求消息是携带于PADR消息发送至所述接入设备的，所述第二响应消息是携带于PADS消息发送至所述终端设备的。
可选地，所述发送单元1103向所述接入设备发送第三固网消息，所述第三固网消息包括PDU会话创建请求消息，所述PDU会话创建请求消息用于请求创建PDU会话；所述接收单元1101接收来自所述接入设备的第四固网消息，所述第四固网消息包括针对所述PDU会话创建请求消息的PDU会话创建请求应答消息。
可选地，所述发送单元1103向所述接入设备发送第五固网消息，所述第五固网消息包括LCP配置请求消息；所述接收单元1101，还接收来自所述接入设备的IPCP消息，所 述IPCP消息包括核心网控制面CP设备为所述终端设备分配的IP参数。
可选地，所述第四NAS消息还包括IP参数，所述IP参数由所述终端设备作为PPPoE IP参数。
可选地，所述第一固网消息还包括PDU会话创建请求消息，所述PDU会话创建请求消息用于请求创建PDU会话，所述第二固网消息还包括针对所述PDU会话创建请求消息的PDU会话创建请求应答消息。
可选地，所述第一固网消息为DHCP发现消息，所述第二固网消息为DHCP提供消息或DHCP确认消息；或者所述第一固网消息为DHCP请求消息，所述第二固网消息为DHCP确认消息。
需要说明的是，本发明实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。本发明实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。例如，上述实施例中，发送单元1103和接收单元1101可以是同一个单元，也不同的单元。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
其中，该装置1100可以为终端设备，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该实现注册装置以对应各个功能划分各个功能模块的形式来呈现，或者，该实现注册装置以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定应用集成电路(application-specific integrated circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到实现注册装置1100可以采用图9所示的形式。比如，图11中的接收单元1101、处理单元1102、发送单元1103可以通过图9的处理器91(和/或处理器98)和存储器93来实现，具体的，接收单元1101、处理单元1102或发送单元1103可以通过由处理器91(和/或处理器98)来调用存储器93中存储的应用程序代码来执行，本发明实施例对此不作任何限制。
本申请实施例还提供一种计算机可读存储介质，用于储存为上述方法实施例中接入设备所用的计算机软件指令，其包含用于执行上述方法实施例所设计的程序。
本申请实施例提供另一种计算机可读存储介质，用于储存为上述方法实施例中终端设备所用的计算机软件指令，其包含用于执行上述方法实施例所设计的程序。
本申请实施例还提供一种计算机程序产品，该计算机程序产品包括计算机软件指令，该计算机软件指令可通过处理器进行加载来实现上述实施例中由终端设备执行的注册方法中的流程。
本申请实施例提供另一种计算机程序产品，该计算机程序产品包括计算机软件指令，该计算机软件指令可通过处理器进行加载来实现上述实施例中由接入设备执行的注册方法中的流程。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部 分地产生按照本申请所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如，同轴电缆、光纤、数字用户线(Digital Subscriber Ling，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存储的任何可用介质或者是包含一个多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)或者半导体介质(例如，固态硬盘(Solid State Disk，SSD))等。
本领域技术人员还可以了解到本申请列出的各种说明性逻辑块(illustrative logical block)和步骤(step)可以通过电子硬件、电脑软件，或两者的结合进行实现。这样的功能是通过硬件还是软件来实现取决于特定的应用和整个系统的设计要求。本领域技术人员可以对于每种特定的应用，可以使用各种方法实现所述的功能，但这种实现不应被理解为超出本申请保护的范围。
本申请中所描述的方法或算法的步骤可以直接嵌入硬件、处理器执行的软件单元、或者这两者的结合。软件单元可以存储于随机存取存储器(Random-Access Memory，RAM)、闪存、只读存储器(Read-Only Memory，ROM)、可擦除可编程只读寄存器(Erasable Programmable Read Only Memory，简称，EPROM)、寄存器、硬盘、可移动磁盘、只读光盘(Compact Disc Read-Only Memory，CD-ROM)或本领域中其它任意形式的存储媒介中。示例性地，存储媒介可以与处理器连接，以使得处理器可以从存储媒介中读取信息，并可以向存储媒介存写信息。可选地，存储媒介还可以集成到处理器中。处理器和存储媒介可以设置于ASIC中，ASIC可以设置于终端设备或接入设备中。可选地，处理器和存储媒介也可以是设置于终端设备或接入设备中的不同的部件中。
在一个或多个示例性的设计中，本申请所描述的上述功能可以在硬件、软件、固件或这三者的任意组合来实现。如果在软件中实现，这些功能可以存储与电脑可读的媒介上，或以一个或多个指令或代码形式传输于电脑可读的媒介上。电脑可读媒介包括电脑存储媒介和便于使得让电脑程序从一个地方转移到其它地方的通信媒介。存储媒介可以是任何通用或特殊电脑可以接入访问的可用媒体。例如，这样的电脑可读媒体可以包括但不限于RAM、ROM、EEPROM、CD-ROM或其它光盘存储、磁盘存储或其它磁性存储装置，或其它任何可以用于承载或存储以指令或数据结构和其它可被通用或特殊电脑、或通用或特殊处理器读取形式的程序代码的媒介。此外，任何连接都可以被适当地定义为电脑可读媒介，例如，如果软件是从一个网站站点、服务器或其它远程资源通过一个同轴电缆、光纤电脑、双绞线、数字用户线(DSL)或以例如红外、无线和微波等无线方式传输的也被包含在所定义的电脑可读媒介中。所述的碟片(disk)和磁盘(disc)包括压缩磁盘、镭射盘、光盘、数字通用光盘(Digital Versatile Disc，DVD)、软盘和蓝光光盘，磁盘通常以磁性复制数据，而碟片通常以激光进行光学复制数据。上述的组合也可以包含在电脑可读媒介中。
以上所述的具体实施方式，对本申请的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本申请的具体实施方式而已，并不用于限定本申请的保 护范围，凡在本申请的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本申请的保护范围之内。本申请说明书的上述描述可以使得本领域技术任何可以利用或实现本申请的内容，任何基于所公开内容的修改都应该被认为是本领域显而易见的，本申请所描述的基本原则可以应用到其它变形中而不偏离本申请的发明本质和范围。因此，本申请所公开的内容不仅仅局限于所描述的实施例和设计，还可以扩展到与本申请原则和所公开的新特征一致的最大范围。

Claims (33)

  1. 一种注册方法，其特征在于，所述方法包括：
    接入设备接收来自终端设备的第一固网消息，所述第一固网消息包括第一非接入层NAS消息，所述第一NAS消息用于请求注册至核心网；
    所述接入设备向核心网控制面CP设备发送所述第一NAS消息；
    所述接入设备接收来自所述CP设备的NAS注册完成消息，并向所述终端设备发送第二固网消息，所述第二固网消息包括第二NAS消息，所述第二NAS消息用于指示核心网注册已完成。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述接入设备记录对应关系，所述对应关系为所述终端设备的用户标识，和/或基于以太网的点对点协议PPPoE会话标识与第一接口的对应关系，所述PPPoE会话标识为所述接入设备为所述终端设备分配的,所述第一接口为接入设备与用于实现接入与移动性管理的功能单元之间的接口。
  3. 根据权利要求2所述的方法，其特征在于，
    所述接入设备向所述CP设备发送所述第一NAS消息，包括：
    所述接入设备根据获取的用户标识，和/或PPPoE会话标识，及所述对应关系，确定第一接口；
    所述接入设备通过确定的所述第一接口，向所述CP设备发送所述第一NAS消息。
  4. 根据权利要求2或3所述的方法，其特征在于，
    所述对应关系为PPPoE会话标识与第一接口的对应关系；则所述接入设备向所述终端设备发送第二固网消息，包括：
    所述接入设备根据接收所述NAS注册完成消息的第一接口，及所述对应关系，确定PPPoE会话标识；
    所述接入设备向所述PPPoE会话标识对应的所述终端设备发送所述第二固网消息；
    或
    所述对应关系为用户标识和PPPoE会话标识，与第一接口的对应关系，或，所述对应关系为用户标识与第一接口的对应关系；则所述接入设备向所述终端设备发送第二固网消息，包括：
    所述接入设备根据接收所述NAS注册完成消息的第一接口，及所述对应关系，确定用户标识；
    所述接入设备向所述用户标识对应的所述终端设备发送所述第二固网消息。
  5. 根据权利要求1至4任一所述的方法，其特征在于，所述方法还包括：
    所述第一固网消息为PPPoE主动发现开始PADI消息，所述第二固网消息为PPPoE主动发现提供PADO消息或PPPoE主动发现会话确认PADS消息；或者
    所述第一固网消息为PPPoE主动发现请求PADR消息，所述第二固网消息为PADS消息。
  6. 根据权利要求1至4任一所述的方法，其特征在于，所述方法还包括：
    所述接入设备接收来自所述终端设备的第一请求消息，所述第一请求消息用于请求所 述接入设备支持NAS的能力；
    所述接入设备向所述终端设备发送第一响应消息，所述第一响应消息用于确定所述接入设备支持NAS。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    所述第一请求消息是携带在PADI消息中发送至所述接入设备的，所述第一响应消息是携带在PADO消息中发送至所述终端设备的。
  8. 根据权利要求1至4、6、7任一所述的方法，其特征在于，所述方法还包括：
    所述接入设备接收来自所述终端设备的第二请求消息，所述第二请求消息用于请求NAS用户标识；
    所述接入设备向所述终端设备发送第二响应消息，所述第二响应消息用于指示所述终端设备的NAS用户标识。
  9. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    所述第二请求消息是携带在PADI消息中发送至所述接入设备的，所述第二响应消息是携带在PADO消息或PADS消息中发送至所述终端设备的；或者
    所述第二请求消息是携带在PADR消息中发送至所述接入设备的，所述第二响应消息是携带在PADS消息中发送至所述终端设备的。
  10. 根据权利要求1至9任一所述的方法，其特征在于，所述方法还包括：
    所述接入设备接收来自所述终端设备的第三固网消息，所述第三固网消息包括分组数据单元PDU会话创建请求消息，所述PDU会话创建请求消息用于请求创建PDU会话；
    所述接入设备向所述CP设备发送PDU会话创建请求消息；
    所述接入设备接收来自所述CP设备的针对所述PDU会话创建请求消息的PDU会话创建请求应答消息；
    所述接入设备向所述终端设备发送第四固网消息，所述第四固网消息包括所述PDU会话创建请求应答消息。
  11. 根据权利要求10所述的方法，其特征在于，
    所述第四NAS消息还包括网络之间互连协议IP参数，所述IP参数由所述终端设备作为PPPoE IP参数。
  12. 根据权利要求1至9任一所述的方法，其特征在于，
    所述第一固网消息还包括PDU会话创建请求消息，所述PDU会话创建请求消息用于请求创建PDU会话；所述第二固网消息还包括针对所述PDU会话创建请求消息的PDU会话创建请求应答消息；
    所述方法还包括：
    所述接入设备向所述CP设备发送所述PDU会话创建请求消息；
    所述接入设备接收来自所述CP设备的所述PDU会话创建请求应答消息。
  13. 根据权利要求1所述的方法，其特征在于，
    所述第一固网消息为动态主机配置协议DHCP发现消息，所述第二固网消息为DHCP提供消息或DHCP确认消息；或者
    所述第一固网消息为DHCP请求消息，所述第二固网消息为DHCP确认消息。
  14. 一种注册方法，其特征在于，所述方法包括：
    终端设备向接入设备发送第一固网消息，所述第一固网消息包括第一非接入层NAS消息，所述第一NAS消息用于请求注册至核心网；
    所述终端设备接收来自所述接入设备的第二固网消息，所述第二固网消息包括第二NAS消息，所述第二NAS消息用于指示核心网注册已完成。
  15. 根据权利要求14所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述接入设备发送第一请求消息，所述第一请求消息用于请求所述接入设备支持NAS的能力；
    所述终端设备接收来自所述接入设备的第一响应消息，所述第一响应消息用于指示所述接入设备支持NAS。
  16. 根据权利要求14或15所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述接入设备发送第二请求消息，所述第二请求消息用于请求NAS用户标识；
    所述终端设备接收来自所述接入设备的第二响应消息，所述第二响应消息用于指示所述终端设备的NAS用户标识。
  17. 根据权利要求14至16任一所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述接入设备发送第三固网消息，所述第三固网消息包括PDU会话创建请求消息，所述PDU会话创建请求消息用于请求创建PDU会话；
    所述终端设备接收来自所述接入设备的第四固网消息，所述第四固网消息包括针对所述PDU会话创建请求消息的PDU会话创建请求应答消息。
  18. 根据权利要求14至16任一所述的方法，其特征在于，所述方法还包括：
    所述第一固网消息还包括PDU会话创建请求消息，所述PDU会话创建请求消息用于请求创建PDU会话，所述第二固网消息还包括针对所述PDU会话创建请求消息的PDU会话创建请求应答消息。
  19. 一种注册装置，其特征在于，所述装置包括：
    接收单元，用于接收来自终端设备的第一固网消息，所述第一固网消息包括第一非接入层NAS消息，所述第一NAS消息用于请求注册至核心网；
    发送单元，用于向核心网控制面CP设备发送所述第一NAS消息；
    所述接收单元，还用于接收来自所述CP设备的NAS注册完成消息；
    所述发送单元，还用于向所述终端设备发送第二固网消息，所述第二固网消息包括第二NAS消息，所述第二NAS消息用于指示核心网注册已完成。
  20. 根据权利要求19所述的装置，其特征在于，所述装置还包括处理单元；
    所述处理单元用于，记录对应关系，所述对应关系为所述终端设备的用户标识，和/或基于以太网的点对点协议PPPoE会话标识与第一接口的对应关系，所述PPPoE会话标识为所述接入设备为所述终端设备分配的,所述第一接口为接入设备与用于实现接入与移动性管理的功能单元之间的接口。
  21. 根据权利要求20所述的装置，其特征在于，所述发送单元，用于向核心网控制面CP设备发送所述第一NAS消息，具体包括：
    所述发送单元，根据获取的用户标识，和/或PPPoE会话标识，及所述对应关系，确定第一接口；通过确定的所述第一接口，向所述CP设备发送所述第一NAS消息。
  22. 根据权利要求20或21所述的装置，其特征在于，
    所述对应关系为PPPoE会话标识与第一接口的对应关系；所述发送单元，还用于向所述终端设备发送第二固网消息，具体包括：
    所述发送单元，根据接收所述NAS注册完成消息的第一接口，及所述对应关系，确定PPPoE会话标识；向所述PPPoE会话标识对应的所述终端设备发送所述第二固网消息；
    或
    所述对应关系为用户标识和PPPoE会话标识，与第一接口的对应关系，或，所述对应关系为用户标识与第一接口的对应关系；所述发送单元，还用于向所述终端设备发送第二固网消息，具体包括：
    所述发送单元，根据接收所述NAS注册完成消息的第一接口，及所述对应关系，确定用户标识；向所述用户标识对应的所述终端设备发送所述第二固网消息。
  23. 根据权利要求19至22任一所述的装置，其特征在于，
    所述接收单元，还用于接收来自所述终端设备的第一请求消息，所述第一请求消息用于请求所述接入设备支持NAS的能力；
    所述发送单元，还用于向所述终端设备发送第一响应消息，所述第一响应消息用于确定所述接入设备支持NAS。
  24. 根据权利要求19至22任一所述的装置，其特征在于，
    所述接收单元，还用于接收来自所述终端设备的第二请求消息，所述第二请求消息用于请求NAS用户标识；
    所述发送单元，还用于向所述终端设备发送第二响应消息，所述第二响应消息用于指示所述终端设备的NAS用户标识。
  25. 根据权利要求19至24任一所述的装置，其特征在于，
    所述接收单元，还用于接收来自所述终端设备的第三固网消息，所述第三固网消息包括分组数据单元PDU会话创建请求消息，所述PDU会话创建请求消息用于请求创建PDU会话；
    所述发送单元，还用于向所述CP设备发送PDU会话创建请求消息；
    所述接收单元，还用于接收来自所述CP设备的针对所述PDU会话创建请求消息的PDU会话创建请求应答消息；
    所述发送单元，还用于向所述终端设备发送第四固网消息，所述第四固网消息包括所述PDU会话创建请求应答消息。
  26. 根据权利要求19至24任一所述的装置，其特征在于，
    所述第一固网消息还包括PDU会话创建请求消息，所述PDU会话创建请求消息用于请求创建PDU会话；所述第二固网消息还包括针对所述PDU会话创建请求消息的PDU会话创建请求应答消息；
    所述发送单元，还用于向所述CP设备发送所述PDU会话创建请求消息；
    所述接收单元，还用于接收来自所述CP设备的所述PDU会话创建请求应答消息。
  27. 一种注册装置，其特征在于，所述装置包括：
    发送单元，用于向接入设备发送第一固网消息，所述第一固网消息包括第一非接入层NAS消息，所述第一NAS消息用于请求注册至核心网；
    接收单元，用于接收来自所述接入设备的第二固网消息，所述第二固网消息包括第二NAS消息，所述第二NAS消息用于指示核心网注册已完成。
  28. 根据权利要求27所述的装置，其特征在于，
    所述发送单元，还用于向所述接入设备发送第一请求消息，所述第一请求消息用于请求所述接入设备支持NAS的能力；
    所述接收单元，还用于接收来自所述接入设备的第一响应消息，所述第一响应消息用于指示所述接入设备支持NAS。
  29. 根据权利要求27或28所述的装置，其特征在于，
    所述发送单元，还用于向所述接入设备发送第二请求消息，所述第二请求消息用于请求NAS用户标识；
    所述接收单元，还用于接收来自所述接入设备的第二响应消息，所述第二响应消息用于指示所述终端设备的NAS用户标识。
  30. 根据权利要求27至29任一所述的装置，其特征在于，
    所述发送单元，还用于向所述接入设备发送第三固网消息，所述第三固网消息包括PDU会话创建请求消息，所述PDU会话创建请求消息用于请求创建PDU会话；
    所述接收单元，还用于接收来自所述接入设备的第四固网消息，所述第四固网消息包括针对所述PDU会话创建请求消息的PDU会话创建请求应答消息。
  31. 一种注册装置，其特征在于，包括：处理器，所述所述处理器用于与存储器耦合，并读取存储器中的指令并根据所述指令执行如权利要求1至13任意一项所述的注册方法。
  32. 一种注册装置，其特征在于，包括：处理器，所述所述处理器用于与存储器耦合，并读取存储器中的指令并根据所述指令执行如权利要求14至18任意一项所述的注册方法。
  33. 一种计算机可读存储介质，其特征在于，该计算机可读存储介质中存储有指令，当其在计算机上运行时，可以执行如权利要求14至18任意一项所述的注册方法。
PCT/CN2018/087590 2017-05-25 2018-05-21 一种注册方法及装置 WO2018214831A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710381306.X 2017-05-25
CN201710381306.XA CN108934022B (zh) 2017-05-25 2017-05-25 一种注册方法及装置

Publications (1)

Publication Number Publication Date
WO2018214831A1 true WO2018214831A1 (zh) 2018-11-29

Family

ID=64396241

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/087590 WO2018214831A1 (zh) 2017-05-25 2018-05-21 一种注册方法及装置

Country Status (2)

Country Link
CN (1) CN108934022B (zh)
WO (1) WO2018214831A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115174172A (zh) * 2019-03-18 2022-10-11 华为技术有限公司 一种通信方法、装置及系统
CN111866858A (zh) * 2019-04-29 2020-10-30 华为技术有限公司 一种注册方法及通信装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006056540A1 (de) * 2004-11-25 2006-06-01 Siemens Aktiengesellschaft Übermittlung dienst-relevanter zugangsinformationen bei authentisierung eines endgeräts an einer zugangseinrichtung eines telekommunikationsnetzes
CN101188856A (zh) * 2006-11-16 2008-05-28 中国电信股份有限公司 通过宽带无线接入实现移动业务的系统和方法
CN101494638A (zh) * 2008-01-25 2009-07-29 华为技术有限公司 一种固定移动融合fmc的方法、系统及装置
CN101674580A (zh) * 2008-09-12 2010-03-17 上海顶竹通讯技术有限公司 一种藉由固网接入移动核心网的方法
CN102833846A (zh) * 2012-08-21 2012-12-19 大唐移动通信设备有限公司 实现ue注册、以及业务呼叫的方法及装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101009611A (zh) * 2006-01-25 2007-08-01 中兴通讯股份有限公司 一种终端接入不同服务网络的方法
US20090262683A1 (en) * 2008-04-18 2009-10-22 Amit Khetawat Method and Apparatus for Setup and Release of User Equipment Context Identifiers in a Home Node B System
US8984105B2 (en) * 2008-05-27 2015-03-17 Qualcomm Incorporated FMC architecture for CDMA network
CN104113930B (zh) * 2013-04-16 2019-02-15 中兴通讯股份有限公司 一种实现用户终结连接的方法及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006056540A1 (de) * 2004-11-25 2006-06-01 Siemens Aktiengesellschaft Übermittlung dienst-relevanter zugangsinformationen bei authentisierung eines endgeräts an einer zugangseinrichtung eines telekommunikationsnetzes
CN101188856A (zh) * 2006-11-16 2008-05-28 中国电信股份有限公司 通过宽带无线接入实现移动业务的系统和方法
CN101494638A (zh) * 2008-01-25 2009-07-29 华为技术有限公司 一种固定移动融合fmc的方法、系统及装置
CN101674580A (zh) * 2008-09-12 2010-03-17 上海顶竹通讯技术有限公司 一种藉由固网接入移动核心网的方法
CN102833846A (zh) * 2012-08-21 2012-12-19 大唐移动通信设备有限公司 实现ue注册、以及业务呼叫的方法及装置

Also Published As

Publication number Publication date
CN108934022B (zh) 2020-11-06
CN108934022A (zh) 2018-12-04

Similar Documents

Publication Publication Date Title
WO2019085803A1 (zh) 一种物联网通信的方法、装置和系统
EP4149084B1 (en) Address management method and system, and device
US11812496B2 (en) User group session management method and apparatus
EP3005822B1 (en) Mac layer transport for wi-fi direct services application service platform without internet protocol
JP7282146B2 (ja) Ｂｒａｓシステムベースのパケットカプセル化方法および装置
WO2019128671A1 (zh) 会话建立方法、设备及系统
US12063709B2 (en) Group management method, apparatus, and system
EP3641365B1 (en) Device access method, device and system
WO2018191854A1 (zh) 接入固定网络的方法和接入网关网元
KR20130140785A (ko) 하부 구조 및 직접 모드들을 갖는 무선 네트워크 인터페이스
EP3742785A1 (en) Session management method and device
JP2014535228A (ja) ポート設定方法、ルーティングデバイス、およびコンピュータプログラム製品
WO2019128672A1 (zh) 会话建立方法、设备及系统
JP2011508551A (ja) 複数の無線ネットワークに同時にアクセスするための装置及び方法
US11432357B2 (en) Multipath establishment method and apparatus
KR20160044565A (ko) 무선 환경에서의 이중 역할 처리를 위한 방법 및 시스템
WO2013067884A1 (zh) 授权信息传递方法、中继设备及服务器
WO2018214831A1 (zh) 一种注册方法及装置
WO2019144719A1 (zh) 一种远端设备的动态接入方法及装置
WO2013185696A2 (zh) 一种数据处理的方法与设备
WO2023221708A1 (zh) Pdn拨号及配置方法、系统、装置、设备及存储介质
EP3706373A1 (en) Establishing a vxlan between a wireless access point and a node
US20230107859A1 (en) Method and Apparatus for Obtaining Network Address of MUD File, and Storage Medium
WO2019149078A1 (zh) 会话管理方法、设备及系统
WO2018219221A1 (zh) 报文转发方法、设备及系统

Legal Events

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

Ref document number: 18805282

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18805282

Country of ref document: EP

Kind code of ref document: A1