WO2023001015A1 - 一种传输数据的方法和装置 - Google Patents

一种传输数据的方法和装置 Download PDF

Info

Publication number
WO2023001015A1
WO2023001015A1 PCT/CN2022/105027 CN2022105027W WO2023001015A1 WO 2023001015 A1 WO2023001015 A1 WO 2023001015A1 CN 2022105027 W CN2022105027 W CN 2022105027W WO 2023001015 A1 WO2023001015 A1 WO 2023001015A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
terminal device
access network
message
network device
Prior art date
Application number
PCT/CN2022/105027
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 WO2023001015A1 publication Critical patent/WO2023001015A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H04W28/12—Flow control between communication endpoints using signalling between network elements

Definitions

  • the present application relates to the communication field, and more particularly, to a method and device for transmitting data.
  • the communication system can be simply divided into four parts, which are terminal equipment, access network (AN), core network (core network, CN) and data network (data network, DN).
  • the terminal equipment realizes data interaction with the data network through the access network and the core network.
  • the communication network needs to carry massive data transmission.
  • the core network is facing increasing data processing and transmission pressure.
  • the present application provides a data transmission method and device, which can reduce the data processing and transmission pressure of the core network.
  • the present application provides a method for transmitting data, which can be performed by access network equipment, or can also be performed by a chip or circuit in the access network equipment, which is not limited in this application, for the sake of convenience Description, the following takes the execution by the access network device as an example for description.
  • the method may include: the access network device acquires indication information, the indication information is used for the access network device to transmit the data of the terminal device through the user plane connection with the fixed network gateway device, and the access network device supports the first 3rd generation partnership project (3rd generation partnership project, 3GPP) access type; the access network device transmits the data of the terminal device through the user plane connection according to the indication information.
  • the indication information is used for the access network device to transmit the data of the terminal device through the user plane connection with the fixed network gateway device, and the access network device supports the first 3rd generation partnership project (3rd generation partnership project, 3GPP) access type
  • 3rd generation partnership project 3rd generation partnership project, 3GPP
  • the access network equipment supports the 3GPP access type, which may also be described as the access network equipment supporting the 3GPP access technology, the access network equipment supporting the cellular access type, or the access network equipment supporting the cellular access technology, etc.
  • the access network device supports the 3GPP access type, and may also be replaced by the access network device supporting the wired access technology or the access network device supporting the WIFI access technology.
  • the 3GPP access technology supported by the access network device may fully support the 3GPP protocol stack, or may support a part of the 3GPP protocol stack, such as only supporting the physical layer, media access control (media access control, MAC) layer, Radio link control (radio link control, RLC) layer, packet data convergence protocol (packet data convergence protocol, PDCP) layer, service data adaptation protocol (service data adaptation protocol, SDAP) layer, radio resource control (radio resource control, Part of the protocol stack in the RRC) layer.
  • media access control media access control
  • RLC radio link control
  • PDCP packet data convergence protocol
  • SDAP service data adaptation protocol
  • radio resource control radio resource control, Part of the protocol stack in the RRC
  • the user plane connection here may be an Internet protocol (internet protocol, IP) data channel, an Ethernet data channel, and a data transmission channel carrying a virtual local area network (virtual local area network, VLAN) identifier, etc., which are not limited in this application.
  • IP Internet protocol
  • Ethernet Ethernet
  • VLAN virtual local area network
  • the user plane connection is used to transmit user plane data for terminal devices of a set type.
  • the access network device may acquire indication information from the core network device.
  • the access network device after the access network device obtains the indication information, it can transmit the data of the terminal device through the user plane connection with the fixed network gateway device.
  • the uplink data of the terminal device can be sent through the access network device.
  • the downlink data sent to the terminal device can be sent to the terminal device by the fixed network gateway device through the access network device, that is, the user plane data of the terminal device is distributed to the fixed network gateway device, which helps to reduce the load on the core network. Data processing and transfer stress.
  • the access network device transmitting the data of the terminal device through the user plane connection according to the indication information includes: the access network device transmitting the data of the terminal device according to the indication information , establishing the user plane connection with the fixed network gateway device; the access network device transmits the data of the terminal device through the user plane connection.
  • the user plane connection between the access network device and the fixed network gateway device may be established according to the instruction information.
  • the indication information includes information used to indicate user plane data of a set type.
  • the indication information is used to instruct the access network device to transmit the set type of user plane data through the user plane connection with the fixed network gateway device.
  • the indication information includes information for indicating that the terminal device is a terminal device of a set type.
  • the instruction information is used to instruct the access network device to transmit the user plane data of the terminal device of the set type through the user plane connection with the fixed network gateway device.
  • the terminal device of the set type may be a fixed network terminal device. Examples include client devices, phones, routers, network switches, residential gateways (RGs), set-top boxes, fixed mobile convergence products, home network adapters, and Internet access gateways.
  • the terminal device of the set type may also be a mobile phone, an augmented reality (augmented reality, AR) terminal, a virtual reality (virtual reality, VR) terminal, a tablet computer (Pad) and other types of terminals.
  • the terminal device of the set type may also be a terminal device that transmits data through a fixed network gateway device, which is not limited in this application.
  • the indication information is included in one or more of the following information: registration acceptance information, authentication passing information, session acceptance information, and session type information.
  • At least one of the registration acceptance information, authentication passing information, session acceptance information and session type information may be used to instruct the access network device to transmit the data of the terminal device through the user plane connection with the fixed network gateway device. It can also be understood that part or all of the information included in at least one of the registration acceptance information, authentication passing information, session acceptance information and session type information can be used to instruct the access network device to connect the transmission terminal through the user plane connection with the fixed network gateway device device data.
  • session acceptance information may also be described as session establishment acceptance information and the like.
  • the indication information includes at least one of the following: information indicating the user plane data of the set type, information indicating the terminal The device is terminal device information of the set type, registration acceptance information, authentication passing information, session acceptance information, and session type information.
  • the access network device obtaining the indication information includes: the access network device obtaining the indication information; or, the access network device obtains the indication information in a session management process of the terminal device.
  • the session management process may be a session establishment process, a session modification process or a session release process.
  • the method further includes: the access network device receiving a first message from the terminal device, the first message being used for Requesting access management for the terminal device; the access network device acquires first information according to the indication information, and the first information is information that can pass the authentication of the access management; the access The network device sends the first information to the fixed network gateway device; the access network device receives a second message from the fixed network gateway device, and the second message instructs the terminal device to pass the access Management authentication; the access network device sends the second message to the terminal device.
  • the first information includes a line ID (line ID) that can pass the authentication of the access management.
  • the method further includes: the access network device receiving a first message from the terminal device, the first message being used for Requesting access management for the terminal device, the first message includes second information, and the second information is information used for authentication of the access management; the access network device according to the first message second information, acquiring third information, where the third information is used to identify the terminal device; the access network device sends the second information and the third information to the fixed network gateway device; the access network device sends the second information and the third information to the fixed network gateway device; The network access device receives a second message from the fixed network gateway device, the second message indicates that the terminal device has passed the authentication of the access management; the access network device sends the second message to the terminal device Two news.
  • the second information includes any one or more of the following: user name, password, and MAC address of the terminal device.
  • the third information includes a line identifier used to identify the terminal device.
  • the method further includes: the access network device receiving a first message from the terminal device, the first message being used for Requesting access management for the terminal device, the first message includes second information, and the second information is information used for authentication of the access management; the access network device sends the fixed The network gateway device sends the second information; the access network device receives a second message from the fixed network gateway device, and the second message indicates that the terminal device passes the authentication of the access management; the The access network device sends the second message to the terminal device.
  • the second information includes any one or more of the following: user name, password, and MAC address of the terminal device.
  • the third information corresponds to the identification information of the terminal device.
  • the identification information of the terminal device includes one or more of the following information: address information, device identification, permanent identification, temporary identification, External ID or Internal ID.
  • the third information is preconfigured in the access network device or comes from a core network device.
  • the first message may be one of the following messages: a dynamic host configuration protocol (dynamic host configuration protocol, DHCP) discovery message, a DHCP request message, an Ethernet bearer point-to-point protocol active discovery initial (point -to-point protocol over Ethernet active discovery initiation (PADI) message or Ethernet bearer point-to-point protocol active discovery request (point-to-point protocol over Ethernet active discovery request, PADR) message.
  • the second message may be a DHCP offer message (DHCP offer) or a DHCP confirmation message (DHCP ACK).
  • the method further includes: the access network device sending a third message to the fixed network gateway device, the third message using In order to request access management for the access network device, the third message includes fourth information, and the fourth information is information that can pass the authentication of the access management; the access network device receives the A fourth message sent by the gateway device, the fourth message indicates that the access network device has passed the authentication of the access management, and the fourth message includes the first IP address of the access network device.
  • the above steps may be performed before establishing a user plane connection with the fixed network gateway device, or may be performed during the process of establishing a user plane connection with the fixed network gateway device, or may be performed with the fixed network gateway device
  • the above steps are performed after the user plane connection is established, which is not limited in this application.
  • the fourth information includes a line identifier that can pass the authentication of the access management.
  • the method further includes: the access network device assigning a second IP address to the terminal device, and the second IP address corresponds to at the first IP address; the access network device receives first user plane data from the terminal device, where the first user plane data includes the second IP address; the access network device sends the replacing the second IP address in the first user plane data with the first IP address to obtain second user plane data; the access network device sending the second user plane data.
  • the third message may be one of the following messages: a DHCP discovery message, a DHCP request message, a PADI message, or a PADR message.
  • the fourth message may be a DHCP offer message or a DHCP confirmation message among the following messages.
  • the method further includes: the access network device receiving the first A session identifier; the access network device assigns a second session identifier to the terminal device, and the second session identifier corresponds to the first session identifier; the access network device assigns the first user plane data The second session ID of is replaced by the first session ID.
  • the method further includes: the access network device acquiring or preconfiguring at least one IP address and/or at least one session identifier, the The second IP address is one of the at least one IP address, and the second session identifier is one of the at least one session identifier.
  • At least one of the first information, the third information, and the fourth information may be preconfigured in the access network device or from The terminal device is either from a core network device.
  • the indication information further includes the IP address of the terminal device
  • the method further includes: forwarding, by the access network device, to the terminal device The IP address; the access network device establishes access network resources with the terminal device.
  • the IP address of the terminal device can be an IP address assigned to it by a fixed network server, for example, an IP address assigned to it by a DHCP server or a PPPoE server; the IP address of the terminal device can also be an IP address assigned by a fixed network gateway device. Assigned IP address.
  • the indication information may also include a session identifier assigned by the fixed network gateway device to the terminal device.
  • the method further includes: the access network device establishing access network resources with the terminal device.
  • the method further includes: when the second message indicates that the terminal device has not passed the access management authentication, the The access network device and the terminal device release access network resources.
  • the method further includes: when the second message indicates that the terminal device passes the access management authentication, the access The network access device establishes access network resources with the terminal device.
  • the present application provides a method for transmitting data.
  • the method may be executed by core network equipment, or may also be executed by a chip or circuit in the core network equipment. This application does not limit this.
  • the following takes execution by a core network device as an example for description.
  • the method may include: the core network equipment acquires indication information, the indication information is used for the access network equipment to transmit the data of the terminal equipment through the user plane connection with the fixed network gateway equipment; The device sends the indication information, and the access network device supports a 3GPP access type.
  • the access network equipment supports the 3GPP access type, which may also be described as the access network equipment supporting the 3GPP access technology, the access network equipment supporting the cellular access type, or the access network equipment supporting the cellular access technology, etc.
  • the terminal device of the set type may be a fixed network terminal device. Examples include client devices, phones, routers, network switches, residential gateways (RGs), set-top boxes, fixed mobile convergence products, home network adapters, and Internet access gateways.
  • the access network device supports the 3GPP access type, and may also be replaced by the access network device supporting the wired access technology or the access network device supporting the WIFI access technology. It should be noted that the 3GPP access technology supported by the access network equipment may fully support the 3GPP protocol stack, or support part of the 3GPP protocol stack, such as only supporting the physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and RRC layer. part of the protocol stack in the layer.
  • the user plane connection here may be an IP data channel, an Ethernet data channel, or a data transmission channel carrying a VLAN ID, which is not limited in this application.
  • the user plane connection is used to transmit user plane data for terminal devices of a set type.
  • the foregoing core network device may be an access and mobility management functional network element or a session management network element.
  • the core network device can obtain the instruction information and send it to the access network device, so that the access network device can transmit the data of the terminal device by connecting with the user plane of the fixed network gateway device after obtaining the instruction information,
  • the uplink data of the terminal device can be sent to the fixed network gateway device through the access network device
  • the downlink data sent to the terminal device can be sent to the terminal device by the fixed network gateway device through the access network device, that is, the user plane data of the terminal device Distributed to the fixed network gateway equipment, it helps to reduce the data processing and transmission pressure of the core network.
  • the indication information includes information used to indicate user plane data of a set type.
  • the indication information is used to instruct the access network device to transmit the set type of user plane data through the user plane connection with the fixed network gateway device.
  • the indication information includes information for indicating that the terminal device is a terminal device of a set type.
  • the instruction information is used to instruct the access network device to transmit the user plane data of the terminal device of the set type through the user plane connection with the fixed network gateway device.
  • the indication information is included in one or more of the following information: registration acceptance information, authentication passing information, session acceptance information, and session type information.
  • At least one of the registration acceptance information, authentication passing information, session acceptance information and session type information may be used to instruct the access network device to transmit the data of the terminal device through the user plane connection with the fixed network gateway device.
  • part or all of the information included in at least one of the registration acceptance information, authentication passing information, session acceptance information and session type information can be used to instruct the access network device to connect the transmission terminal through the user plane connection with the fixed network gateway device device data.
  • the indication information includes at least one of the following: information indicating user plane data of the set type, information indicating the terminal
  • the device is terminal device information of the set type, registration acceptance information, authentication passing information, session acceptance information, and session type information.
  • the core network device sends indication information to the access network device, including: the core network device is in the registration process of the terminal device Sending the indication information to the access network device; or, the core network device sending the indication information to the access network device in a session management process of the terminal device.
  • the session management process may be a session establishment process, a session modification process or a session release process.
  • the core network device obtaining the indication information includes: the core network device obtaining the subscription of the terminal device from a unified data management function network element data; the core network device acquires the indication information according to the subscription data.
  • the core network device obtaining the indication information includes: the core network device obtaining the policy information of the terminal device from a policy function network element; The core network device acquires the indication information according to the policy information.
  • the core network device obtaining indication information includes: the core network device obtaining type information of the terminal device, the type information indicating The terminal device is a terminal device of the set type; the core network device acquires the indication information according to the type information.
  • the type information is included in the subscription data of the terminal device; or, the type information comes from the terminal device.
  • the core network device is a session management network element
  • the method further includes: the session management network element skips selecting the user plane functional network element and/or a process of allocating an IP address for the terminal device.
  • the core network device is a session management network element
  • the method further includes: sending the session management network element to the fixed network gateway device sending a fifth message, where the fifth message is used to request access management for the terminal device, where the fifth message includes fifth information, where the fifth information is information that can pass the authentication of the access management ;
  • the session management network element receives a sixth message from the fixed network gateway device, where the sixth message indicates that the terminal device passes the access management authentication.
  • the sixth message and the indication information may further include an IP address assigned to the terminal device by the fixed network server.
  • the sixth message and the indication information may further include a session identifier assigned by the fixed network gateway device to the terminal device.
  • the fifth information is obtained by the session management network element from the unified data management function network element, or the fifth information It is pre-configured in the session management network element.
  • the fifth information includes a line identifier that can pass the authentication of the access management.
  • the present application provides a method for transmitting data, the method may be executed by an authentication, authorization, accounting (AAA) server, or may also be executed by a chip or circuit in the AAA server , the present application does not limit this, for the convenience of description, the following uses an AAA server as an example for description.
  • AAA authentication, authorization, accounting
  • the method may include: the AAA server receives the user name and password from the terminal device; the AAA server performs access management on the terminal device according to the user name and the password; if the user name corresponds to the The number of managed authenticated terminal devices is greater than a preset threshold, the AAA server rejects the access management of the first number of terminal devices, or enables the first number of terminal devices to go offline, the first number is greater than or equal to the The difference between the preset threshold and the number of authenticated terminal devices corresponding to the user name that pass the access management.
  • the AAA server can perform access management on the terminal equipment according to the user name and password of the terminal equipment, and reject a certain number of terminal equipment when the number of terminal equipment accessed through the user name and password is greater than the preset threshold access authentication or enable a certain number of terminal devices to go offline, so as to ensure that the number of terminal devices accessed through the user name and password does not exceed the preset threshold. In this way, effective access management can be performed on the terminal equipment.
  • the method further includes: the AAA server receives third information, the third information is used to identify the terminal device; the AAA server receives the third information according to the third information , determining the number of terminal devices corresponding to the user name that have passed the access management authentication.
  • the third information includes a line identifier used to identify the terminal device.
  • the third information corresponds to the identification information of the terminal device.
  • the identification information of the terminal device includes one or more of the following information: address information, device identification, permanent identification, temporary identification, External ID or Internal ID.
  • the present application provides a communication device, which is configured to execute the methods provided in the first aspect to the third aspect above.
  • the apparatus may include a unit and/or module for executing the methods provided in the first aspect to the third aspect, such as a processing unit and/or a communication unit.
  • the apparatus is an access network device.
  • the communication unit may be a transceiver, or an input/output interface;
  • the processing unit may be a processor.
  • the apparatus is a chip, a chip system or a circuit used in an access network device.
  • the communication unit may be an input/output interface, interface circuit, output circuit, input circuit, pipe feet or related circuits, etc.
  • the processing unit may be a processor, a processing circuit, or a logic circuit, etc.
  • the device is a core network device.
  • the communication unit may be a transceiver, or an input/output interface;
  • the processing unit may be a processor.
  • the apparatus is a chip, a chip system or a circuit used in core network equipment.
  • the communication unit may be an input/output interface, interface circuit, output circuit, input circuit, pin on the chip, chip system or circuit Or related circuits, etc.
  • the processing unit may be a processor, a processing circuit, or a logic circuit, etc.
  • the device is an AAA server.
  • the communication unit may be a transceiver, or an input/output interface;
  • the processing unit may be a processor.
  • the device is a chip, a chip system or a circuit used in an AAA server.
  • the communication unit may be an input/output interface, interface circuit, output circuit, input circuit, pin or Related circuits, etc.
  • the processing unit may be a processor, a processing circuit, or a logic circuit, etc.
  • the apparatus is a terminal device.
  • the communication unit may be a transceiver, or an input/output interface;
  • the processing unit may be a processor.
  • the apparatus is a chip, a chip system, or a circuit used in a terminal device.
  • the communication unit may be an input/output interface, interface circuit, output circuit, input circuit, pin or pin on the chip, chip system or circuit.
  • the processing unit may be a processor, a processing circuit, or a logic circuit, etc.
  • the foregoing transceiver may be a transceiver circuit.
  • the above input/output interface may be an input/output circuit.
  • the present application provides a communication device, which includes: a memory for storing a program; a processor for executing the program stored in the memory, and when the program stored in the memory is executed, the processor is used for executing the above-mentioned first The method provided by the first aspect to the third aspect.
  • the apparatus is an access network device, a core network device, an AAA server or a terminal device.
  • the apparatus is a chip, a chip system or a circuit used in an access network device, a core network device, an AAA server or a terminal device.
  • the present application provides a processor configured to execute the methods provided in the foregoing aspects.
  • the process of sending the above information and obtaining/receiving the above information in the above method can be understood as the process of outputting the above information by the processor and the process of receiving the input of the above information by the processor.
  • the processor When outputting the above information, the processor outputs the above information to the transceiver for transmission by the transceiver. After the above information is output by the processor, other processing may be required before reaching the transceiver.
  • the transceiver acquires/receives the above-mentioned information and inputs it into the processor. Furthermore, after the transceiver receives the above information, the above information may need to be processed before being input to the processor.
  • the receiving of the second message from the fixed network gateway device mentioned in the foregoing method may be understood as the processor receiving the input second message.
  • processor For the operations of transmitting, sending, and acquiring/receiving involved in the processor, if there is no special description, or if it does not conflict with its actual function or internal logic in the relevant description, it can be understood more generally as the processor Output and receive, input and other operations, rather than the transmission, transmission and reception operations performed directly by radio frequency circuits and antennas.
  • the above-mentioned processor may be a processor dedicated to performing these methods, or may be a processor that executes computer instructions in a memory to perform these methods, such as a general-purpose processor.
  • the above-mentioned memory can be a non-transitory (non-transitory) memory, such as a read-only memory (Read Only Memory, ROM), which can be integrated with the processor on the same chip, or can be respectively arranged on different chips.
  • ROM read-only memory
  • the embodiment does not limit the type of the memory and the arrangement of the memory and the processor.
  • the present application provides a computer-readable storage medium, where the computer-readable medium stores program code for execution by a device, where the program code is used to execute the methods provided in the first to third aspects above.
  • the present application provides a computer program product containing instructions, and when the computer program product is run on a computer, it causes the computer to execute the methods provided in the first aspect to the third aspect above.
  • the present application provides a chip, the chip includes a processor and a communication interface, the processor reads the instructions stored in the memory through the communication interface, and executes the above-mentioned first to third aspects. method.
  • the chip may further include a memory, the memory stores instructions, and the processor is configured to execute the instructions stored on the memory, when the instructions are executed , the processor is configured to execute the methods provided in the first aspect to the third aspect above.
  • the present application provides a communication system, including: an access network device, configured to execute the method described in the first aspect or any implementation thereof; and communicate with the access network device core network equipment.
  • FIG. 1 is a schematic diagram of a network architecture of a communication system 100 provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of a control plane protocol stack of the present application.
  • Fig. 3 is a schematic diagram of the user plane protocol stack of the present application.
  • Fig. 4 is another schematic diagram of the user plane protocol stack of the present application.
  • FIG. 5 is a schematic flow chart of a method 500 for transmitting data provided in this application.
  • Fig. 6 is a schematic diagram of a registration process of a terminal device provided by the present application.
  • Fig. 7 is an example of the method for transmitting data provided by this application.
  • Fig. 8 is another example of the method for transmitting data provided by this application.
  • Fig. 9 is another example of the method for transmitting data provided by this application.
  • Fig. 10 is another example of the method for transmitting data provided by this application.
  • Fig. 11 is another example of the method for transmitting data provided by this application.
  • Fig. 12 is an example of the data transmission process provided by this application.
  • Fig. 13 is another example of the data transmission process provided by this application.
  • Fig. 14 is a schematic structural diagram of a possible communication device provided by an embodiment of the present application.
  • Fig. 15 is a schematic structural diagram of a possible communication device provided by an embodiment of the present application.
  • the present application presents various aspects, embodiments or features in terms of a system comprising a number of devices, components, modules and the like. It is to be understood and appreciated that the various systems may include additional devices, components, modules, etc. and/or may not include all of the devices, components, modules etc. discussed in connection with the figures. In addition, combinations of these schemes can also be used.
  • At least one means one or more, and “multiple” means two or more.
  • At least in part means part or all.
  • “And/or” describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B, which may indicate: including the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the contextual objects are an "or” relationship.
  • At least one of the following” or similar expressions refer to any combination of these items, including any combination of single or plural items.
  • At least one item (piece) of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or multiple .
  • “obtain” may also include the meaning of "determine”.
  • the access network device acquiring the first information according to the indication information may also be understood as the access network device determining the first information according to the indication information.
  • the core network device acquiring the indication information may also be understood as the core network device determining the indication information.
  • “Establishing a connection” in this application may refer to "establishing a user plane connection", and no distinction will be made between the two below.
  • FIG. 1 is a schematic diagram of a network architecture of a communication system 100 provided by an embodiment of the present application.
  • the communication system 100 combines a mobile communication system and a fixed wired network, and can realize offloading user plane data of a terminal device to a fixed network gateway device.
  • a communication system 100 includes a terminal device, a core network, an access network, a fixed network gateway device, and a data network.
  • the access network may include at least one access network device.
  • the access network device supports 3GPP access type.
  • the terminal device can be connected to the access network device in a wireless manner, the access network device is connected to the core network in a wireless or wired manner, and the access network device is connected to the fixed network gateway device in a wired manner.
  • the core network equipment and the access network equipment can be independent and different physical equipment, or the functions of the core network equipment and the logical functions of the access network equipment can be integrated on the same physical equipment, or they can be integrated on one physical equipment Part of the functions of the core network device and part of the functions of the access network device are specified.
  • the terminal device and the terminal device and the access network device and the access network device may be connected to each other in a wired or wireless manner.
  • FIG. 1 is only a schematic diagram, and the communication system may also include other network devices.
  • the terminal device accesses the network through the 3GPP access mode, and completes the registration in the core network through the access network device.
  • the uplink data of the terminal device is sent to the fixed network gateway device through the access network device, and the downlink data is sent from the fixed network gateway device to the terminal device through the access network device.
  • the data network of the communication system 100 may include an Internet network (the Internet or the Internet), an IP multimedia subsystem (IP multimedia subsystem, IMS) network, an IPTV network, a telephone network, and other networks.
  • the data network can also be replaced by a network or a server, which is not limited in this application.
  • the mobile communication system part of the communication system 100 may belong to various mobile communication systems, for example: the fifth generation (5th generation, 5G) mobile communication system or new radio access technology (new radio access technology, NR), long term evolution (long term evolution (LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD) or other networks.
  • the mobile communication system part of the communication system 100 may also belong to a future mobile communication system, such as the sixth generation mobile communication system.
  • the mobile communication system may include non-standalone networking (non-standalone, NSA) and/or standalone networking (standalone, SA).
  • the access network device in the communication system 100 may be a base station (base station), an evolved base station (evolved NodeB, eNodeB), a transmission reception point (transmission reception point, TRP), or a next generation base station (next generation) in a 5G mobile communication system.
  • NodeB, gNB the next-generation base station in the sixth generation (6th generation, 6G) mobile communication system, or the base station in the future mobile communication system; it can also be a module or unit that completes some functions of the base station, for example, it can be a centralized Central unit (CU), distributed unit (DU), RRU or baseband unit (BBU).
  • CU Central unit
  • DU distributed unit
  • BBU baseband unit
  • the access network equipment may be a macro base station, a micro base station or an indoor station, or a relay node or a donor node.
  • the access network equipment supports 3GPP access types.
  • the embodiment of the present application does not limit the specific technology and specific equipment form adopted by the access network equipment.
  • a terminal device in the communication system 100 may also be called a terminal, a user equipment (user equipment, UE), a mobile station, a mobile terminal device, and the like.
  • Terminal devices can be widely used in various scenarios, such as virtual reality, augmented reality, industrial control, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc.
  • Terminal devices can be mobile phones, tablet computers, computers with wireless transceiver functions, robots, mechanical arms, smart home devices, etc.
  • Terminal devices can also be customer-premises equipment (CPE), telephones, routers, network switches, residential gateways (residential gateways, RG), set-top boxes, fixed-mobile convergence products, home network adapters, and Internet access gateways, etc.
  • CPE customer-premises equipment
  • the CPE or RG here can be a mobile signal access device that receives mobile signals and forwards them with wireless WiFi signals, and can also be a device that converts high-speed 4th generation (4th generation, 4G) or 5G signals into WiFi signals
  • the equipment that is, the CPE or RG can support both wired access and wireless access (for example, access to the mobile network through 3GPP).
  • the CPE or RG can also support receiving data through the cellular air interface and forwarding data through the cellular air interface.
  • the CPE or RG can support a large number of mobile terminal devices surfing the Internet at the same time.
  • CPE or RG can be widely used in wireless network access in rural areas, towns, hospitals, units, factories, communities, etc., which can save the cost of laying wired networks.
  • the CPE or RG can provide the interconnection service between the mobile operator's communication network and the client's Wi-Fi LAN.
  • the embodiment of the present application does not limit the specific technology and specific device form adopted by the terminal device.
  • Access network equipment and terminal equipment can be fixed or mobile. Access network equipment and terminal equipment can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; they can also be deployed on water.
  • the embodiments of the present application do not limit the application scenarios of the access network device and the terminal device.
  • the roles of the access network device and the terminal device may be relative.
  • Communication between access network devices and terminal devices, between access network devices and access network devices, between terminal devices and terminal devices can be carried out through licensed spectrum, or through license-free spectrum, or through authorized spectrum at the same time.
  • Spectrum and unlicensed spectrum for communication can communicate through spectrum below 6 gigahertz (GHz), can also communicate through spectrum above 6GHz, and can also use spectrum below 6GHz and spectrum above 6GHz at the same time.
  • the embodiments of the present application do not limit the frequency spectrum resources used for wireless communication.
  • the fixed network gateway device in the communication system 100 is an Internet protocol (internet protocol, IP) edge node, which may be a broadband network gateway (broadband network gateway, BNG), a broadband remote access server (broadband remote access server, BRAS), or a service Router (service router, SR) and so on.
  • BRAS and SR can be subdivided forms of BNG, which can be understood as BNG in a narrow sense.
  • BRAS serves as the entrance of traditional Internet services
  • SR serves as the entrance of new boutique services. Similar to the BRAS, the SR is used to terminate and manage the user's point-to-point protocol over Ethernet (PPPoE)/Internet protocol over Ethernet (IPoE) sessions of the user.
  • the fixed network gateway device may be called a non-mobile network gateway or a non-mobile gateway device.
  • the core network in the communication system 100 may include one or more core network devices, such as access and mobility management function (access and mobility management function, AMF), unified data management (unified data management, UDM) and authentication server function (authentication server function, AUSF) network element, the core network can also include more or less network elements, for example, the core network can also include session management function (session management function, SMF) network element (in Figure 1 not shown), etc.
  • AMF access and mobility management function
  • UDM unified data management
  • AUSF authentication server function
  • the core network can also include more or less network elements, for example, the core network can also include session management function (session management function, SMF) network element (in Figure 1 not shown), etc.
  • the AMF network element belongs to the control plane network element of the core network, and is mainly responsible for user mobility management, including mobility status management, allocation of temporary user IDs, authentication and authorization of users, and provision of control plane storage resources for sessions.
  • the UDM network element belongs to the core network control plane network element, belongs to the user server, and is mainly responsible for managing the subscription data.
  • the AUSF network element belongs to the core network control plane network element, and is mainly responsible for user authentication and authorization to ensure that the user is a legitimate user.
  • the SMF network element belongs to the control plane network element of the core network, and is mainly used for session management, UE IP address allocation and management, selection of manageable user plane functions, policy control, or termination points of charging function interfaces, and downlink data notification.
  • the foregoing core network elements may also be referred to as core network equipment.
  • FIG. 2 is a schematic diagram of a control plane protocol stack of the present application. It can be seen from FIG. 2 that for the control plane, the terminal device communicates with the access network device through RRC messages, and the terminal device communicates with the AMF through non-access stratum (non-access stratum, NAS) messages.
  • RRC radio resource control
  • NAS non-access stratum
  • Fig. 3 is a schematic diagram of the user plane protocol stack of the present application.
  • the terminal device can communicate with the fixed network gateway device through PPPoE or IPoE protocol.
  • the message between the terminal device and the fixed network gateway device is forwarded through the access network device supporting the 3GPP access type.
  • the message between the terminal device and the access network device is transmitted through the 3GPP cellular air interface, and the data transmission is performed between the access network device and the fixed network gateway device in a wired manner.
  • the terminal device can carry the message sent to the fixed network gateway device over the air interface and send it to the access network device, and then the access network device forwards it to the fixed network gateway device.
  • the access network device may determine whether to forward the data to the fixed network gateway device or to the mobile network gateway device according to the type of the terminal device.
  • Fig. 4 is another schematic diagram of the user plane protocol stack of the present application.
  • the access network device has an IPoE or PPPoE protocol stack.
  • the access network device can serve as a terminal device in the fixed network and directly establish a connection with the fixed network gateway device.
  • the connection between the access network device and the fixed network gateway device can be a connection shared by multiple terminal devices that transmit data through the access network device.
  • the access network device can perform network address translation so that The connections between multiple terminal devices and the access network device can be mapped to one or more connections established between the access network device and the fixed network gateway device.
  • the naming of the network element in this application is only a name, and the name does not limit the function of the network element itself.
  • the foregoing network elements may also have other names, which are not specifically limited in this embodiment of the present application.
  • some or all of the above-mentioned network elements may use the terms in 5G, or may be named by other names, etc., which will be described in a unified manner here, and will not be described in detail below.
  • the network element in this application may be hardware, or software divided by function, or a combination of the above two.
  • the network elements in this application may communicate through other devices or network elements.
  • FIG. 5 is a schematic flow chart of a method 500 for transmitting data provided in this application.
  • the method 500 may be executed by the terminal device, the access network device, the core network device, and the fixed network gateway device, or may be performed by modules or units in the terminal device, the access network device, the core network device, and the fixed network gateway device (for example, circuit, chip or system on chip (system on chip, SOC), etc.) to execute.
  • the following describes the technical solution of the present application by taking the terminal device, the access network device, the core network device and the fixed network gateway device as examples as execution subjects.
  • Method 500 may include at least some of the following.
  • step 501 the core network device acquires indication information.
  • the indication information is used for the access network device to transmit the data of the terminal device through the user plane connection with the fixed network gateway device.
  • the user plane connection may be an Internet protocol (internet protocol, IP) data channel, an Ethernet data channel, and a data transmission channel carrying a virtual local area network (virtual local area network, VLAN) identifier, etc. limit.
  • IP Internet protocol
  • Ethernet Ethernet
  • VLAN virtual local area network
  • the user plane connection is used to transmit user plane data for terminal equipment of a set type.
  • the indication information may include information indicating user plane data of a set type and/or information indicating that the terminal device is a terminal device of a set type.
  • the indication information may be included in one or more of the following information: registration acceptance information (for example, registration accept), authentication pass information (for example, indicated by authentication indication), session acceptance information (for example, PDU session accept), and session type information.
  • registration acceptance information for example, registration accept
  • authentication pass information for example, indicated by authentication indication
  • session acceptance information for example, PDU session accept
  • session type information for example, it can also be described as indicating that the information may include at least one of the following information: information indicating user plane data of a set type, information indicating that the terminal device is a terminal device of a set type, registration acceptance information, authentication pass information, session acceptance information, and session type information.
  • the information may be part or all of at least one of the following information: information used to indicate user plane data of a set type, information used to indicate that the terminal device is a terminal device of a set type information, registration acceptance information, authentication passing information, session acceptance information, and session type information.
  • the information used to indicate the user plane data of the set type may be one or more of the following information: address information, port information, protocol information, and first service information, which can be understood as the user plane data of the set type
  • the plane data is the user plane data using the address indicated by the address information, the user plane data transmitted through the port indicated by the port information, the user plane data transmitted using the protocol indicated by the protocol information, and the service information indicated by the first service information user plane data.
  • the address information may include one or more of the following information: source IP address, destination IP address, source MAC address, and destination MAC address.
  • the port information may include one or more of the following information: source port number and destination port number.
  • the protocol information may include one or more of the following information: protocol type, protocol name, and protocol version number.
  • the first service information may include one or more of the following information: service identifier, application identifier, and service type information.
  • the session type information is used to indicate that the session is a session of a set type of terminal equipment or a session used to transmit user plane data of a set type of terminal equipment, such as a session used to transmit home gateway data or a session used to transmit fixed network services session etc.
  • the terminal equipment of the set type may be a fixed network terminal equipment.
  • the terminal device of the set type may also be a mobile phone, an AR terminal, a VR terminal, a tablet computer and other types of terminals.
  • the terminal device of the set type may also be a terminal device that transmits data through a fixed network gateway device, which is not limited in this application.
  • the indication information includes information for indicating the set type of user plane data
  • the indication information is used to instruct the access network device to transmit the set type of user plane data through the user plane connection with the fixed network gateway device .
  • the indication information includes information indicating that the terminal device is a terminal device of a set type
  • the indication information is used to instruct the access network device to transmit a terminal of a set type through a user plane connection with a fixed network gateway device User plane data of the device.
  • the indication information includes at least one of registration acceptance information, authentication passing information, session acceptance information, and session type information
  • the core network device passes registration acceptance information, authentication passing information, session acceptance information, and session type information. At least one instructs the access network device to transmit the data of the terminal device through the user plane connection with the fixed network gateway device.
  • the core network device obtains the indication information when the terminal device successfully registers, authenticates successfully, or establishes a session successfully.
  • the core network device may implicitly instruct the access network device to transmit the data of the terminal device through the user plane connection with the fixed network gateway device through at least one of registration acceptance information, authentication passing information, and session acceptance information.
  • the access network device acquires in advance the information indicating the user plane data of the set type or the information indicating that the terminal device is a terminal device of the set type
  • the access network device receives From the registration acceptance information, authentication passing information, session acceptance information and session type information from the core network device, the access network device can determine that the user plane of the terminal device of the set type needs to be transmitted through the user plane connection with the fixed network gateway device.
  • the core network device implicitly instructs the access network device to transmit the terminal through the user plane connection with the fixed network gateway device through at least one of registration acceptance information, authentication passing information, and session acceptance information device data.
  • the access network device may obtain from the terminal device the information indicating the user plane data of the set type or the information indicating that the terminal device is a set type of terminal device.
  • the terminal device may pass a registration request message, a session The establishment request message, the session modification request message, etc. send the above information to the access network device.
  • the core network device may combine at least one of the registration acceptance information, the authentication pass information, and the session acceptance information, and the information used to indicate the user plane data of the setting type and the information used to indicate that the terminal device is set At least one of the information about the terminal device of a given type, instructing the access network device to transmit user plane data of a terminal device of a set type or user plane data of a set type through a user plane connection with the fixed network gateway device.
  • the core network device can obtain the indication information according to the subscription data of the terminal device.
  • a possible implementation manner is that the core network device acquires the indication information according to the type information of the terminal device and/or the second service information in the subscription data of the terminal device.
  • the type information is used to indicate the type of the terminal device
  • the second service information is used to indicate whether the terminal device has opened a fixed network service (or indicates whether the terminal device has the right to obtain the fixed network service, or indicates whether the service data flow of the terminal device requires distributed to the fixed network gateway device).
  • the fixed network services here may include home broadband services and the like.
  • the second service information includes specific service flow information.
  • the service flow information can be one or more of the following information: address information, port information, protocol information, and first service information, where the description of address information, port information, protocol information, and first service information can refer to The above will not be repeated here.
  • the core network device determines the information used to indicate the set type of user plane data in the indication information according to the specific service flow information in the second service information.
  • the core network device may obtain the subscription data of the terminal and obtain the indication information during the registration process of the terminal device.
  • the AMF can interact with the UDM to obtain the subscription data of the terminal device. Further, the AMF may determine the type of the terminal device and whether the terminal device has subscribed to the fixed network service (or whether the terminal device has the right to obtain the fixed network service, or Whether the business data of the terminal device needs to be offloaded to the fixed network gateway device).
  • AMF obtains Indication information, the indication information may include registration acceptance information or authentication passing information.
  • the AMF can interact with the UDM to obtain the subscription data of the terminal device. Further, the AMF may determine the type of the terminal device according to the type information of the terminal device included in the subscription data. If the terminal device is a set type of terminal device, the AMF acquires indication information, and the indication information may include registration acceptance information or authentication passing information.
  • the AMF can interact with the UDM to obtain the subscription data of the terminal device. Further, the AMF can determine whether the terminal device has subscribed to the fixed network service (or whether the terminal device has the right to obtain the fixed network service, or whether the service data of the terminal device needs to be distributed to the fixed network gateway according to the second service information included in the subscription data) equipment). If the terminal device has opened the fixed network service (or the terminal device has the right to obtain the fixed network service, or the service data flow of the terminal device needs to be diverted to the fixed network gateway device), AMF obtains the indication information, which can include registration acceptance information or authentication passing information.
  • the AMF can feed back registration rejection information (for example, registration reject) or authentication failure information to the access network device, or, the AMF can not obtain the indication information, and pass the access network device after the terminal device passes the security authentication process Send registration acceptance information or authentication success information to the terminal device.
  • registration rejection information for example, registration reject
  • authentication failure information for example, registration reject
  • the AMF can not obtain the indication information, and pass the access network device after the terminal device passes the security authentication process Send registration acceptance information or authentication success information to the terminal device.
  • the core network device may obtain the subscription data of the terminal device and obtain the indication information during the session management process of the terminal device.
  • the session management process may be a session establishment process, a session modification process or a session release process.
  • the SMF can interact with the UDM to obtain the subscription data of the terminal device. Further, the SMF can determine the type of the terminal device and whether the terminal device has subscribed to the fixed network service (or whether the terminal device has the right to obtain the fixed network service, or the terminal Whether the business data of the device needs to be offloaded to the fixed network gateway device). If it is determined that the terminal device is a set type of terminal device and/or the terminal device has opened a fixed network service (or the terminal device has the right to obtain fixed network services, or the service data flow of the terminal device needs to be diverted to the fixed network gateway device), the SMF obtains Indication information, where the indication information may include session acceptance information or authentication passing information.
  • the SMF interacts with the UDM to obtain the subscription data of the terminal device. Further, the SMF may determine the type of the terminal device according to the type information of the terminal device in the subscription data. If it is determined that the terminal device is a set type of terminal device, the SMF acquires indication information, and the indication information may include session acceptance information or authentication passing information.
  • the SMF interacts with the UDM to acquire the subscription data of the terminal device. Further, the SMF can determine whether the terminal device has opened the fixed network service (or whether the terminal device has the right to obtain the fixed network service, or whether the service data of the terminal device needs to be distributed to the fixed network gateway device according to the second service information in the subscription data) ). If the terminal device has opened the fixed network service (or the terminal device has the right to obtain the fixed network service, or the service data flow of the terminal device needs to be diverted to the fixed network gateway device), the SMF obtains the indication information, which can include session acceptance information or authentication passing information.
  • the indication information can include session acceptance information or authentication passing information.
  • the above-mentioned fixed network service may be a home broadband service or the like.
  • the SMF determines that the terminal device is a set type of terminal device and/or the terminal device has opened a fixed network service (or the terminal device has the right to obtain the fixed network service, or the service data flow of the terminal device needs to be diverted to the fixed network service).
  • the SMF can replace the terminal device and interact with the fixed network gateway device to complete the authentication of the terminal device, the acquisition of the IP address of the terminal device and/or the acquisition of the session identifier.
  • the SMF determines that the terminal device is a set type of terminal device and/or the terminal device has opened the fixed network service (or the terminal device has the right to obtain the fixed network service, or the service data flow of the terminal device needs to be diverted to the fixed network Gateway device), the user plane data of the terminal device will be offloaded to the fixed network gateway device, so the SMF does not need (or skip) to select the user plane function network element and/or assign an IP address to the terminal device.
  • SMF determines that the terminal device is not a set type of terminal device and/or the terminal device has not subscribed to fixed network services (or has no authority to obtain fixed network services, or the service data flow of the terminal device does not need to be diverted to the fixed network Gateway device).
  • SMF can feed back session rejection information (for example, PDU session reject) or authentication failure information to the access network device, or, after the terminal device completes the second authentication in the session establishment process, the SMF can pass through the access network The device sends session acceptance information or authentication passing information to the terminal device. At this time, the SMF does not need to obtain the indication information.
  • the core network device may determine the indication information according to the type information of the terminal device.
  • the type information of the terminal device here may come from the terminal device, for example, the terminal device may include the type information of the terminal device in an access stratum (access stratum, AS) or non-access stratum (non-access stratum, NAS) message.
  • the terminal device may include this type of information in a radio resource control (radio resource control, RRC) message, a registration request message, or a session establishment request message.
  • RRC radio resource control
  • the core network device may determine the indication information according to the policy information of the terminal device.
  • the policy information here may come from a policy function network element, such as a policy control function (policy control function, PCF).
  • policy control function policy control function
  • Step 502 the access network device acquires indication information.
  • the access network device in this application is a wireless access network device, or in other words, the access network device supports 3GPP access type.
  • the 3GPP access type supported by the access network device may also be described as, the access network device supports the 3GPP access technology, the access network device supports the cellular access type, or the access network device supports the cellular access technology.
  • the access network device supports the 3GPP access type, and it can also be replaced by the access network device supporting the wired access technology or the access network device supporting the WIFI access technology.
  • the 3GPP access technology supported by the access network equipment may fully support the 3GPP protocol stack, or support part of the 3GPP protocol stack, such as only supporting the physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and RRC layer. part of the protocol stack in the layer.
  • the access network device may acquire indication information from the core network device. Specifically, after acquiring the indication information, the core network device may send the indication information to the access network device, and accordingly, the access network device receives the indication information from the core network device.
  • the indication information For the description of the indication information, reference may be made to the above, and details are not repeated here.
  • the access network device may acquire indication information from the core network device during the registration process of the terminal device.
  • the access network device may receive the N2 message sent by the AMF, and the N2 message may include instruction information sent to the access network device.
  • the indication information may include at least one of the following: information indicating the user plane data of the set type, information indicating that the terminal device is a terminal device of the set type, registration acceptance information, and authentication passing information.
  • the N2 message further includes a NAS message sent to the terminal device, and the N2 message may include registration acceptance information or authentication passing information sent by the AMF to the terminal device.
  • the AMF may feed back registration rejection information (for example, registration reject) or authentication failure information to the access network device, and accordingly, the access network device receives registration rejection information or authentication failure information.
  • registration rejection information for example, registration reject
  • authentication failure information for example, authentication reject
  • the access network device may obtain indication information from the core network device during the session establishment process of the terminal device.
  • the access network device can receive the N1N2 message sent by the SMF through the AMF, wherein the N1N2 messaging message can carry a session identifier, N1 session information, and N2 session information.
  • the N1 session information is sent by the SMF to the terminal device through the AMF, and the N1 session information may include session acceptance information or authentication passing information.
  • the N2 session information is sent by the SMF to the access network device through the AMF, and the N2 session information may include indication information.
  • the indication information may include at least one of the following: information indicating user plane data of a set type, information indicating that the terminal device is a terminal device of a set type, authentication passing information, session acceptance information, and session type information , for a more detailed description of each piece of information, reference may be made to the above, and details will not be repeated here.
  • the N2 session information further includes a NAS message sent to the terminal device, and the NAS message may include registration acceptance information or authentication passing information sent by the AMF to the terminal device.
  • the N1 session information may also include the fixed network gateway The IP address and/or session identifier assigned by the device to the terminal device.
  • the SMF may feed back registration rejection information or authentication failure information to the access network device, and accordingly, the access network device receives registration rejection information or authentication failure information.
  • the method 500 further includes: the access network device forwards the N1 session information or the NAS message to the terminal device .
  • Step 503 the access network device transmits the data of the terminal device through the user plane connection with the fixed network gateway device according to the indication information.
  • the access network device may learn that at least part of the user plane data of the terminal device needs to be offloaded to the fixed network gateway device.
  • the access network device may transmit the set type of user plane data through the user plane connection with the fixed network gateway device according to the indication information.
  • the access network device may transmit user plane data of the terminal device of a set type through a user plane connection with the fixed network gateway device.
  • the access network device may need to communicate with the fixed network gateway device after receiving the registration acceptance information, authentication passing information, session acceptance information and session type information from the core network device.
  • the user plane connection transmits user plane data of a terminal device of a set type or user plane data of a set type.
  • the access network device may obtain from the terminal device the information indicating the user plane data of the set type or the information indicating that the terminal device is a set type of terminal device. For example, the terminal device may pass a registration request message, a session The establishment request message, the session modification request message, etc. send the above information to the access network device.
  • the access network device may transmit user plane data of a terminal device of a set type or user plane data of a set type by connecting with the user plane of the fixed network gateway device.
  • the access network device may determine that the terminal device is a terminal device of a set type according to the information indicating the user plane data of the set type and/or the information indicating that the terminal device is a terminal device of the set type and/or Or set the type of user plane data.
  • the access network device Since the registration acceptance information, authentication passing information, and session acceptance information belong to NAS layer information, the access network device does not actively acquire these information. In a possible implementation, after the access network device discovers that the NAS information is sent to itself, it may determine through default configuration that the data of the terminal device needs to be transmitted through the user plane connection with the fixed network gateway device.
  • the N2 message may also include registration acceptance information, authentication passing information, and session acceptance information, so that the access network device Registration acceptance information, authentication passing information, and session acceptance information can be acquired through the N2 message.
  • the access network device may establish a user plane connection with the fixed network gateway device according to the indication information.
  • the access management of the terminal device can be performed before the access network device establishes a user plane connection with the fixed network gateway device, or when the access device establishes a user plane connection with the fixed network gateway device, or can be performed when the access network device establishes a user plane connection with the fixed network gateway device.
  • the ingress device establishes a user plane connection with the fixed network gateway.
  • the terminal device sends a first message to the access network device, where the first message is used to request access management for the terminal device.
  • the access network device acquires the first information according to the instruction information, where the first information is information that can pass the authentication of the access management.
  • the access network device sends the first information to the fixed network gateway device.
  • the fixed network gateway device After receiving the first information, the fixed network gateway device sends the first information to the AAA server through the fixed network server.
  • the AAA server After receiving the first information, the AAA server performs access management authentication on the terminal device according to the first information. Since the first information is authentication information that can pass the access management, the AAA server will pass the access management authentication of the terminal device.
  • the AAA server feeds back to the fixed network gateway device that the terminal device has passed the authentication of the access management through the fixed network server.
  • the fixed network gateway device receives the second message from the fixed network server, and sends the second message to the access network device, the second message indicates that the terminal device has passed the authentication of the access management, and the second message may include that the fixed network server assigns the terminal device IP address.
  • the access network device may feed back the authentication of the terminal device passing the access management and the IP address to the terminal device.
  • the access network device acquiring the first information according to the indication information may also be understood as the access network device determining the first information according to the indication information.
  • the IP address of the terminal device may also be allocated by the fixed network gateway device.
  • the foregoing access management may include authenticating whether to subscribe to a fixed network service (or whether to have the right to obtain a fixed network service).
  • the first information may be pre-configured in the access network device, or from the terminal device, or from the core network device.
  • the first information may be an accessible line identifier (line ID).
  • the first message may be a DHCP discovery message or a DHCP request message, etc.
  • the second message may be a DHCP offer message (DHCP offer) or a DHCP confirmation message (DHCP ACK), etc.
  • the fixed network server may be a DHCP server.
  • the first message may be a message in the negotiation process of PADI, PADR or link configuration request (link configure request, LCP), and the second message may be PADO, PADS or LCP
  • the fixed network server can be a PPPoE server; at this time, the function of the PPPoE server can be integrated in the fixed network gateway device.
  • the fixed network gateway device integrates the function of the fixed network server, and assigns an IP address to the terminal device.
  • the terminal device obtains an IP address through an IP Control Protocol (IP Control Protocol, IPCP).
  • IP Control Protocol IP Control Protocol
  • the fixed network gateway device can also assign a PPPoE session identifier to the terminal device.
  • the access network device may also establish access network resources with the terminal device.
  • the present application does not limit the timing of establishing access network resources between the access network device and the terminal device. For example, after receiving the indication information, the access network device may establish access network resources with the terminal device. For another example, when the second message is received and the second message indicates that the terminal device has passed the access management authentication, the access network device may establish an access network resource with the terminal device. For example, after receiving the first message, the access network device may establish access network resources with the terminal device.
  • the access network device may release the access network resources with the terminal device.
  • the terminal device sends a first message to the access network device, where the first message is used to request access management for the terminal device, and the first message includes second information, where the second information is authentication information for performing access management.
  • the access network device acquires third information according to the second information in the first message, where the third information is used to identify the terminal device.
  • the access network device sends the second information and the third information to the fixed network gateway device.
  • the fixed network gateway device After receiving the second information and the third information, sends the second information and the third information to the AAA server through the fixed network server.
  • the AAA server performs access management authentication on the terminal device according to the second information and the third information.
  • the AAA server feeds back the terminal to the fixed network gateway device through the fixed network server.
  • the device has passed the authentication of access management.
  • the fixed network gateway device receives the second message from the fixed network server, and sends the second message to the access network device, the second message indicates that the terminal device has passed the authentication of the access management, and the second message may include that the fixed network server assigns the terminal device IP address.
  • the access network device may feed back the authentication of the terminal device passing the access management and the IP address to the terminal device.
  • the access network device acquires the third information according to the second information in the first message, and it can also be understood that the access network device determines the third information according to the second information in the first message.
  • the IP address of the terminal device may also be allocated by the fixed network gateway device.
  • the foregoing access management may include authenticating whether to subscribe to a fixed network service (or whether to have the right to obtain a fixed network service).
  • the second information includes at least one of a user name corresponding to the terminal device, a password, and an identifier of the terminal device.
  • the access network device may acquire the third information according to the identifier of the terminal device in the second information.
  • the third information corresponds to identification information of the terminal device, for example, the third information may be a line identification used to indicate the terminal device.
  • the identifier of the terminal device may include at least one of the following: address information (such as a MAC address), a device identifier, a permanent identifier (such as a subscription permanent identifier (SUPI)), a temporary identifier (such as a 5G global unique temporary identifier ( 5G-globally unique temporary identity, 5G-GUTI), 5G short temporary mobile subscription identifier (5G S-Temporary Mobile Subscription Identifier, 5G-S-TMSI)), external identification (such as mobile phone number, generic public subscription identifier , GPSI) or internal identification (such as SUPI, subscription concealed identifier (SUCI), 5G-GUTI, 5G-S-TMSI, internal GPSI, etc.).
  • the third information may be pre-configured in the access network device or from the core network device.
  • the AAA server may perform access management on the terminal device in the following manner. Specifically, if the number of terminal devices authenticated through access management corresponding to the user names carried in the second information is greater than the preset threshold, the AAA server rejects the access management of the first number of terminal devices, or enables the first number of terminal devices to The terminal devices go offline, where the first number is greater than or equal to the difference between the preset threshold and the number of terminal devices that pass the access management authentication corresponding to the user name.
  • the AAA server may determine, according to the received fourth information, the number of authenticated terminal devices that pass the access management and correspond to the user names carried in the second information.
  • the first message may be a DHCP discovery message or a DHCP request message, etc.
  • the second message may be a DHCP offer message or a DHCP confirmation message, etc.
  • the fixed network server may be a DHCP server.
  • the terminal device may adopt the PPPoE protocol
  • the first message may be a message during the negotiation of PADI, PADR or LCP
  • the second message may be a message during the negotiation of PADO, PADS or LCP
  • the fixed network server may It is a PPPoE server; at this time, the PPPoE server function can be integrated in the fixed network gateway device.
  • the fixed network gateway device integrates the function of the fixed network server, and assigns an IP address to the terminal device.
  • the terminal device obtains the IP address through IPCP.
  • the fixed network gateway device can also assign a PPPoE session identifier to the terminal device.
  • the access network device may also establish access network resources with the terminal device.
  • the present application does not limit the timing of establishing access network resources between the access network device and the terminal device. For example, after receiving the indication information, the access network device may establish access network resources with the terminal device. For another example, when the second message is received and the second message indicates that the terminal device has passed the access management authentication, the access network device may establish an access network resource with the terminal device. For example, after receiving the first message, the access network device may establish access network resources with the terminal device.
  • the access network device may release the access network resources with the terminal device.
  • the access network device may not acquire the third information.
  • the terminal device sends a first message to the access network device, the first message is used to request access management for the terminal device, and the first message includes second information, and the second information is authentication information for access management Information.
  • the access network device sends the second information to the fixed network gateway device.
  • the fixed network gateway device sends the second information to the AAA server through the fixed network server.
  • the AAA server performs access management authentication on the terminal device according to the second information. If the authentication is passed, the AAA server feeds back to the fixed network gateway device that the terminal device has passed the access management authentication through the fixed network server.
  • the fixed network gateway device receives the second message from the fixed network server, and sends the second message to the access network device, the second message indicates that the terminal device has passed the authentication of the access management, and the second message may include that the fixed network server assigns the terminal device IP address. Further, the access network device may feed back the authentication of the terminal device passing the access management and the IP address to the terminal device.
  • the IP address of the terminal device may also be allocated by the fixed network gateway device.
  • the second information includes at least one of a user name corresponding to the terminal device, a password, and an identifier of the terminal device.
  • the foregoing access management may include authenticating whether to subscribe to a fixed network service (or whether to have the right to obtain a fixed network service).
  • the first message may be a DHCP discovery message or a DHCP request message, etc.
  • the second message may be a DHCP offer message or a DHCP confirmation message, etc.
  • the fixed network server may be a DHCP server.
  • the terminal device may adopt the PPPoE protocol
  • the first message may be a message during the negotiation of PADI, PADR or LCP
  • the second message may be a message during the negotiation of PADO, PADS or LCP
  • the fixed network server may It is a PPPoE server; at this time, the PPPoE server function can be integrated in the fixed network gateway device.
  • the fixed network gateway device integrates the function of the fixed network server, and assigns an IP address to the terminal device.
  • the terminal device obtains the IP address through IPCP.
  • the fixed network gateway device can also assign a PPPoE session identifier to the terminal device.
  • the access network device may also establish access network resources with the terminal device.
  • the present application does not limit the timing of establishing access network resources between the access network device and the terminal device. For example, after receiving the indication information, the access network device may establish access network resources with the terminal device. For another example, when the second message is received and the second message indicates that the terminal device has passed the access management authentication, the access network device may establish an access network resource with the terminal device. For example, after receiving the first message, the access network device may establish access network resources with the terminal device.
  • the access network device may release the access network resources with the terminal device.
  • the access network device may send a third message to the fixed network gateway device, the third message is used to request access management for the access network device, and the third message may include fourth information, the fourth The information is information that can be authenticated by the access management.
  • the fixed network gateway device sends fourth information to the AAA server through the fixed network server.
  • the AAA server performs access management authentication on the access network device according to the fourth information. Since the fourth information is the authentication information that can pass the access management, the AAA server will pass the Access management authentication, the AAA server feeds back to the fixed network gateway device that the access network device has passed the access management authentication through the fixed network server.
  • the fixed network gateway device receives the fourth message from the fixed network server, and sends the fourth message to the access network device, the fourth message indicates that the access network device has passed the authentication of the access management, and the fourth message includes that the fixed network server is The first IP address assigned by the network access device. Further, the access network device may allocate a second IP address to the terminal device, and the second IP address corresponds to the first IP address. In this way, if subsequently receiving user plane data from the terminal device, the access network device may replace the second IP address in the user plane data with the first IP address, and send the data to the fixed network gateway device.
  • the foregoing access management may include authenticating whether to subscribe to a fixed network service (or whether to have the right to obtain a fixed network service).
  • the first IP address may also be allocated by the fixed network gateway device.
  • the fourth information may be preconfigured in the access network device, or from the terminal device, or from the core network device. In an implementation manner, the fourth information may be an identifier of an accessible line.
  • the third message may be a DHCP discovery message or a DHCP request message, etc.
  • the fourth message may be a DHCP offer message (DHCP offer) or a DHCP confirmation message (DHCP ACK).
  • the third message may be a message during PADI, PADR or LCP negotiation
  • the fourth message may be a message during PADO, PADS or LCP negotiation.
  • the fixed network gateway device can also assign the first session identifier to the access network device, and the access network device can also assign a second session identifier to the terminal device, and the second session identifier corresponds to the first session identifier. ID, if subsequently receiving user plane data from the terminal device, the access network device may also replace the second session ID in the user plane data with the first session ID.
  • the session identifier here may be a PPPoE session identifier.
  • the method 500 further includes: the access network device acquires or preconfigures at least one IP address and/or at least one session identifier, the second IP address is one of the at least one IP address, and the second session identifier is One of at least one session ID.
  • the access network device can obtain or pre-configure an IP address resource pool or a session ID resource pool in advance, and when it is necessary to assign an IP address or a session ID to a terminal device, it can select the corresponding IP address resource pool or session ID resource pool obtained from .
  • the authentication process for the access network device to perform access management of the access network device can also be performed before obtaining the instruction information. Further, when the terminal device completes the registration, the access network device can directly register the terminal device according to the instruction information. The device assigns an IP address and/or session ID.
  • the access network device may also establish access network resources with the terminal device.
  • the present application does not limit the timing of establishing access network resources between the access network device and the terminal device. For example, after receiving the indication information, the access network device may establish access network resources with the terminal device. For another example, after the terminal device completes registration, the access network device may establish access network resources with the terminal device. For example, after receiving the fourth message, the access network device may establish access network resources with the terminal device.
  • the access network device can release the access network resources with the terminal device.
  • Mode 5 is aimed at the situation where SMF replaces the terminal device and interacts with the fixed network gateway device to complete the authentication of the terminal device, the acquisition of the IP address of the terminal device and/or the acquisition of the session identifier.
  • the access network device obtains the After indicating the information, the access network resource can be established with the terminal device.
  • the SMF may interact with the fixed network gateway device in the following manner to complete the authentication of the terminal device, the acquisition of the IP address of the terminal device and/or the acquisition of the session identifier. Specifically, when the SMF determines that the terminal device is a set type of terminal device and/or has opened the fixed network service (or has the right to obtain the fixed network service, or the service data flow of the terminal device needs to be diverted to the fixed network gateway device) , to acquire fifth information, where the fifth information is information that can pass the authentication of the access management. The SMF sends fifth information to the fixed network gateway device. After receiving the fifth information, the fixed network gateway device sends the fifth information to the AAA server through the fixed network server.
  • the AAA server After receiving the fifth information, the AAA server performs access management authentication on the terminal device according to the fifth information. Since the fifth information is the authentication information that can pass the access management, the AAA server will pass the access management authentication of the terminal device. , the AAA server feeds back to the fixed network gateway device that the terminal device has passed the authentication of the access management through the fixed network server.
  • the fixed network gateway device receives a seventh message from the fixed network server, the seventh message is used to instruct the terminal device to pass the access management authentication, and the seventh message may include the IP address assigned by the fixed network server to the terminal device.
  • the SMF may send the N1N2 message to the access network device through the AMF. For the description of the NIN2 message, reference may be made to the above, and details will not be repeated here.
  • the IP address of the terminal device may also be allocated by the fixed network gateway device.
  • the foregoing access management may include authenticating whether to subscribe to a fixed network service (or whether to have the right to obtain a fixed network service).
  • the fifth information may be pre-configured in the core network device, or from the terminal device, or from other core network devices.
  • the fifth information may be an accessible line identifier (line ID).
  • the sixth message may be a DHCP discovery message or a DHCP request message, etc.
  • the seventh message may be a DHCP offer message (DHCP offer) or a DHCP confirmation message (DHCP ACK), etc.
  • the fixed network server may be a DHCP server.
  • the sixth message may be a message during the negotiation process of PADI, PADR or LCP
  • the seventh message may be a message during the negotiation process of PADO, PADS or LCP
  • the fixed network server may It is a PPPoE server; at this time, the PPPoE server function can be integrated in the fixed network gateway device.
  • the fixed network gateway device integrates the function of the fixed network server, and assigns an IP address to the terminal device.
  • the terminal device obtains the IP address through IPCP.
  • the fixed network gateway device can also assign a PPPoE session identifier to the terminal device.
  • the uplink data of the terminal device can be sent to the fixed network gateway device through the access network device, and the downlink data sent to the terminal device can be It can be sent from the fixed network gateway device to the terminal device through the access network device, that is, the user plane data of the terminal device is distributed to the fixed network gateway device, which helps to reduce the data processing and transmission pressure of the core network.
  • Fig. 6 is a schematic diagram of a registration process of a terminal device provided by the present application.
  • Step 601 the terminal device sends a registration request message to the access network device.
  • the registration request message may carry the registration type (registration type) and identification information of the terminal device.
  • Registration types can include the following:
  • Mobility registration update (mobility registration update): the registration process that needs to be initiated when the terminal device moves;
  • Periodic registration update (periodic registration update): When the terminal device is in the registration state, the registration process is initiated due to the timeout of the periodic registration update timer;
  • Emergency registration The registration process initiated when the terminal device is in a service-restricted state.
  • the identification information of the terminal device may include the user's subscription concealed identifier (SUCI), 5G globally unique temporary identity (5G-globally unique temporary identity, 5G-GUTI), and permanent equipment identifier (permanent equipment identifier, PEI). at least one.
  • SUCI subscription concealed identifier
  • 5G-globally unique temporary identity 5G-GUTI
  • PEI permanent equipment identifier
  • Step 602 the access network device selects a suitable AMF.
  • Step 603 the access network device sends the registration request message sent by the terminal device to the selected AMF.
  • step 604 the AMF selects an appropriate AUSF to perform security procedures such as authentication.
  • the terminal device AMF, AUSF, and UDM interact to complete security procedures such as authentication.
  • the process after the terminal device and the network side complete the security process such as authentication may include steps 605-607, and the specific implementation manners of steps 605-607 may have the following three ways.
  • Step 605 after the terminal device and the network side complete security processes such as authentication, the AMF interacts with the UDM to obtain the subscription data of the terminal device.
  • step 606 the AMF sends an N2 message to the access network device.
  • the N2 message includes the NAS message sent to the terminal device.
  • the NAS message may include first registration acceptance information (registration accept) or first registration rejection information (registration reject) sent by the AMF to the terminal device.
  • Step 607 after receiving the N2 message from the AMF, the access network device forwards the NAS message sent by the AMF to the terminal device.
  • the NAS message may include first registration acceptance information or first registration rejection information.
  • Step 605 after the terminal device and the network side complete security processes such as authentication, the AMF interacts with the UDM to obtain the subscription data of the terminal device.
  • the subscription data may include the type of the terminal device and/or the second service information.
  • the type of the terminal device is used to indicate whether the terminal device is a set type of terminal device; the second service information is used to indicate whether the terminal device has opened a fixed network service (or indicate whether the terminal device has the right to obtain fixed network services, or indicate Whether the service data flow of the terminal device needs to be offloaded to the fixed network gateway device).
  • step 606 the AMF sends an N2 message to the access network device.
  • the N2 message includes a NAS message sent to the terminal device, and the NAS message may include first registration acceptance information or first registration rejection information sent by the AMF to the terminal device.
  • the N2 message may also include second registration acceptance information or second registration rejection information sent to the access network device.
  • the AMF can Send the second registration acceptance information to the access network device through the N2 message (not in the NAS message); if the terminal device is not a set type of terminal device and/or the terminal device has not subscribed to the fixed network service (or has no authority to obtain the fixed network service , or the service data flow of the terminal device does not need to be distributed to the fixed network gateway device), then the AMF can send the second registration rejection information to the access network device through the N2 message, or the AMF does not need to include the second registration acceptance information or the second registration acceptance information in the N2 message 2. Registration rejection information.
  • the N2 message may also include the type of the terminal device sent to the access network device.
  • Step 607 After receiving the N2 message from the AMF, the access network device forwards the NAS message sent by the AMF to the terminal device, and according to the second registration acceptance information or the second registration rejection information in the N2 message, determines whether the terminal device registration success.
  • the NAS message may include first registration acceptance information or first registration rejection information.
  • the access network device may determine whether the terminal device is a set type of terminal device according to the terminal device type information in the N2 message.
  • the AMF may send the second registration rejection information (optional) or the second registration acceptance information, and the type of the terminal device (optional) to the access network device.
  • Step 605 after the terminal device and the network side complete security processes such as authentication, the AMF interacts with the UDM to obtain the subscription data of the terminal device.
  • the subscription data may include the type of the terminal device and the second service information.
  • the type of the terminal device is used to indicate whether the terminal device is a set type of terminal device; the second service information is used to indicate whether the terminal device has opened a fixed network service (or whether it has the right to obtain a fixed network service, or whether the terminal device's Whether the service data flow needs to be diverted to the fixed network gateway device).
  • step 606 the AMF sends an N2 message to the access network device.
  • the N2 message includes a NAS message that needs to be forwarded by the access network device to the terminal device, and the N2 message may include first registration acceptance information or first registration rejection information sent by the AMF to the terminal device.
  • the N2 message may also include authentication indication information sent to the access network device. If the terminal device is a terminal device of the set type and/or the terminal device has opened a fixed network service (or the terminal device has the right to obtain the fixed network service, or the service data flow of the terminal device needs to be diverted to the fixed network gateway device), then The authentication indication information indicates that the authentication is successful, for example, the authentication indication information is authentication passing information, etc.; The service data flow does not need to be distributed to the fixed network gateway device), the authentication indication information indicates that the authentication has failed, or the N2 message does not include the authentication indication information, for example, the authentication indication information is authentication failure information, etc.
  • the N2 message may also include the type of the terminal device sent to the access network device.
  • Step 607 After receiving the N2 message from the AMF, the access network device forwards the NAS message sent by the AMF to the terminal device, and determines whether the terminal device is authenticated successfully according to the authentication indication information in the N2 message.
  • the NAS message may include first registration acceptance information or first registration rejection information.
  • the access network device may determine whether the terminal device is a set type of terminal device according to the terminal device type information in the N2 message.
  • the AMF sends the authentication indication information (optional) and the type of the terminal device (optional) to the access network device.
  • the registration process using mode 1 is called the first registration process
  • the registration process using mode 2 is called the second registration process
  • the registration process using mode 3 is called the third registration process.
  • AMF does not send terminal device type information, registration acceptance information, registration rejection information, authentication instruction information, etc. to the access network device;
  • AMF sends terminal device type information (optional) and registration acceptance information or registration rejection information (optional) to the access network device;
  • the third registration process the AMF sends the terminal device type information (optional) and authentication indication information (optional) to the access network device.
  • Fig. 7 is an example of the method for transmitting data provided by this application.
  • the AAA server in Figure 7 is an authentication, authorization, and accounting (authentication, authorization, accounting) server, which is used to authenticate whether the terminal device is allowed to go online, and can also be understood as used to authenticate whether the terminal device has opened a fixed network service (or the terminal device whether it has the right to obtain fixed-line services).
  • the DHCP server is a dynamic host configuration protocol server (dynamic host configuration protocol server), which is used to assign IP addresses to terminal devices that have passed the authentication.
  • the method for transmitting data shown in FIG. 7 may be based on the terminal device having completed the first registration procedure in Example 1, and based on the user plane protocol stack shown in FIG. 3 .
  • the terminal device initiates a session establishment process, and the session establishment process involves interaction with core network devices.
  • Step 701 the terminal device sends a session establishment request message to the AMF.
  • the session establishment request message can carry relevant parameters for session establishment, such as session identification (PDU Session ID), data network name (data network name, DNN), network slice selection assistance information (network slice selection assistance information, NSSAI) Wait.
  • session identification PDU Session ID
  • data network name data network name, DNN
  • network slice selection assistance information network slice selection assistance information, NSSAI
  • a possible implementation is that the terminal device sends a PDU Session Establishment Request to the AMF.
  • Step 702 after receiving the session establishment request message from the terminal device, the AMF selects an appropriate SMF.
  • step 703 the AMF sends a session context creation request message to the SMF.
  • the create session context request message may carry an identifier of the terminal device (for example, SUPI, etc.), a session identifier, a data network name, auxiliary information for network slice selection, and the like.
  • AMF sends Nsmf_PDUSession_CreateSMContext Request to SMF.
  • step 704 the SMF interacts with the UDM to obtain the subscription data of the terminal device.
  • the subscription data may include the type of the terminal device and/or the second service information.
  • the second service information is used to indicate whether the terminal device has subscribed to the fixed network service (or whether the terminal device has the right to obtain the fixed network service, or whether the service data flow of the terminal device needs to be diverted to the fixed network gateway device).
  • Step 705 the SMF determines the type information of the terminal device and/or whether the terminal device has subscribed to the fixed network service (or whether it has the right to obtain the fixed network service, or whether the service data flow of the terminal device needs to be diverted to fixed network gateway device).
  • SMF can refuse Establish this session. In this case, steps 706-708 may be performed subsequently.
  • the SMF allows the establishment of The session, and the SMF does not need to select the UPF and assign an IP address to the end device.
  • the SMF can obtain the indication information, and then continue to perform steps 709-712.
  • the SMF acquires the indication information.
  • the SMF obtains the instruction information.
  • the SMF determines to obtain the indication information.
  • the above indication information may be offload indication information, which is used to instruct to offload the user plane data of the terminal device to the fixed network gateway device. It can be understood that when the indication information is the offloading indication information, the indication information is a displayed indication information that can explicitly instruct the access network device to offload the user plane data of the terminal device to the fixed network gateway device.
  • the indication information may be one or more of session acceptance information, authentication passing information, and session type information. The authentication passing information indicates that the terminal device has passed the second authentication process in the session establishment process.
  • the session type information indicates that the session is a session of a terminal device of a set type, a session for transmitting user data of a terminal device of a set type, or that the session is a session established for a terminal device of a set type, or indicates that the A session is used to transmit user plane data of a terminal device whose terminal type is a set type.
  • the indication information at this time is an implicit indication information, and by sending one or more of session acceptance, authentication passing information, and session type information to the access network device, it indicates that the terminal device that initiates the session establishment process is A terminal device of the specified type, and the terminal device successfully establishes the session. This implies that the access network device offloads the user plane data of the terminal device to the fixed network gateway device.
  • the indication information determined by the SMF may include information used to indicate the user plane data of the set type.
  • the service flow information can be one or more of the following information: address information, port information, protocol information, and first service information, where the description of address information, port information, protocol information, and first service information can refer to The above will not be repeated here.
  • step 706 the SMF sends a session context creation response message to the AMF.
  • the create session context response message may carry N1 session information (N1SM information) and N2 session information (N2SM information).
  • N1 session information can carry session rejection information, such as PDU session reject.
  • the N2 session information may include session rejection information or authentication failure information.
  • the session rejection information or authentication failure information is used to indicate to the access network device that the session establishment or authentication failure of the terminal device fails.
  • SMF sends Nsmf_PDUSession_CreateSMContext Response to AMF.
  • Step 707 If the N1 session information and N2 session information are received in step 706, the AMF sends the N2 session information to the access network device through the N2 message, and sends the N1 session information to the terminal device through the NAS message.
  • the NAS message is sent by the AMF to the access network device through the N2 message, and then forwarded by the access network device to the terminal device.
  • Step 708 after receiving the N2 message from the AMF, the access network device determines that the session establishment or authentication of the terminal device fails, and forwards the N1 session information to the terminal device, wherein the N1 session information includes session rejection information.
  • the N1 session information may be carried in a NAS message, for example, may be carried in a PDU Session Reject.
  • Step 709 the SMF sends the N1N2 messaging message to the AMF.
  • the N1N2 message transfer message may carry a session identifier, N1 session information, and N2 session information.
  • the N1 session information is sent by the SMF to the terminal device through the AMF, and the N1 session information may include session acceptance information (session establishment acceptance message), such as PDU session accept (PDU session establishment accept).
  • the N2 session information is sent by the SMF to the access network device through the AMF.
  • the N2 session information may include a session identifier and indication information.
  • the description of the indication information may refer to the above description, which will not be repeated here.
  • the indication information is the indication information determined or obtained in step 705 .
  • a possible implementation is that the SMF sends Namf_Communication_N1N2MessageTransfer to the AMF.
  • Step 710 after receiving the N1N2 message delivery message, the AMF sends an N2 session request message to the access network device.
  • the N2 session request message may carry N2 session information and N1 session information from the SMF.
  • the N2 session information is sent to the access network device through the N2 message, and the N1 session information is sent to the terminal device through the NAS message.
  • the NAS message is sent by the AMF to the access network device through the N2 message, and then forwarded by the access network device to the terminal device.
  • a possible implementation is that the AMF sends an N2PDU Session Request to the access network device.
  • Step 711 after receiving the N2 message from the AMF, the access network device determines through the indication information in the N2 session information that it needs to establish a user plane connection with the fixed network gateway device, or in other words, determines that it is necessary to offload the user plane data of the terminal device to the fixed network gateway device.
  • the access network device can establish an access network (access network, AN) resource with the terminal device, and forward N1 session information to the terminal device, where the N1 session information includes session acceptance information.
  • the N1 session information can be carried in a NAS message, for example, it can be carried in PDU Session Accept (or PDU Session Establishment Accept).
  • Step 712 the access network device sends an N2 session response message to the AMF.
  • a possible implementation manner is that the access network device sends the N2PDU Session Response to the AMF.
  • IPoE authentication and IP address distribution process can be performed.
  • Step 713 the terminal device sends a DHCP discovery message (DHCPDiscover) to the access network device.
  • DHCPDiscover a DHCP discovery message
  • the DHCP discovery message is carried on a cellular air interface or on a data radio bearer (data radio bearer, DRB).
  • DRB data radio bearer
  • the DHCP discovery message may indicate the type of the terminal device.
  • the option 60 (Option 60) field of the DHCP discovery message can carry information that can indicate the type of the terminal device.
  • Step 714 after receiving the DHCP discovery message from the terminal device, the access network device can insert an accessible line ID (line ID) into the DHCP discovery message according to whether the terminal device needs to establish a user plane connection with the fixed network gateway device. ) or an inaccessible line ID.
  • line ID accessible line ID
  • the access network device inserts an inaccessible line ID into the DHCP discovery message sent by the terminal device. In another possible implementation manner, the access network device may not forward the DHCP discovery message.
  • the access network device inserts an accessible line ID into the DHCP discovery message sent by the terminal device, so that the terminal device can pass IPoE authentication.
  • the access network device may also obtain the type information of the terminal device through the DHCP discovery message.
  • step 715 may also be performed before any step before step 714.
  • step 715 the access network device obtains the ID of an accessible line.
  • a possible implementation manner is that the access network device acquires an accessible line ID in an out-of-band manner.
  • an accessible line ID may be configured for the access network device in a preconfigured manner.
  • the access network device may also obtain the ID of an inaccessible line.
  • Step 716 the access network device sends a DHCP discovery message to the fixed network gateway device.
  • Step 717 after receiving the DHCP discovery message from the access network device, the fixed network gateway device sends the DHCP discovery message to the DHCP server.
  • Step 718 after receiving the DHCP discovery message from the fixed network gateway device, the DHCP server obtains information such as the line ID in the DHCP discovery message, constructs the first authentication information required for authentication, and sends an access request (Access Request) to the AAA server. Request) message.
  • the DHCP server obtains information such as the line ID in the DHCP discovery message, constructs the first authentication information required for authentication, and sends an access request (Access Request) to the AAA server. Request) message.
  • the access request message may include the first authentication information.
  • Step 719 the AAA server authenticates the terminal device according to the first authentication information.
  • the authentication results of the AAA server are different, and the subsequent steps are also different. If the line ID in the first authentication information is an inaccessible line ID, the AAA server does not pass the authentication of the terminal device, and steps 720-721 may be performed subsequently. If the line ID in the first authentication information is an accessible line ID, the AAA server passes the authentication of the terminal device, and steps 722-725 may be performed subsequently.
  • Step 720 the AAA server sends an access deny (access deny) message to the DHCP server.
  • Step 721 after receiving the access rejection message from the AAA server, the DHCP server sends a DHCP negative acknowledgment (NACK) message to the terminal device through the fixed network gateway device and the access network device.
  • NACK DHCP negative acknowledgment
  • Step 722 the AAA server sends an access accept (access accept) message to the DHCP server.
  • Step 723 after receiving the access acceptance message from the AAA server, the DHCP server assigns an IP address to the terminal device, and includes the IP address assigned to the terminal device in the DHCP offer (offer) message, and passes the fixed network gateway device, the access The network access device sends a DHCP offer message to the terminal device.
  • the DHCP offer message may further include second authentication information, so that the terminal device can perform authentication according to the second authentication information, and identify whether the DHCP offer message comes from a trusted DHCP server.
  • step 713 If the DHCP discovery message in step 713 is a broadcast message, then there may be multiple DHCP servers receiving the DHCP discovery message, so in step 723, there may also be multiple DHCP servers that assign IP addresses to terminal devices and send DHCP Provide news. If the terminal device receives DHCP offer messages sent from multiple DHCP servers, steps 724 and 725 may also be performed.
  • Step 724 after receiving the DHCP offer message, the terminal device sends a DHCP request (DHCP Request) message to the DHCP server through the access network device and the fixed network gateway device.
  • DHCP Request DHCP request
  • the terminal device sends a DCHP request message according to one of the multiple DHCP offer messages (for example, the first received DHCP offer message), where the DHCP request message may include the IP address assigned by the DHCP server. address.
  • Step 725 the DHCP server sends a DHCP acknowledgment (acknowledgment, ACK) message to the terminal device through the fixed network gateway device and the access network device.
  • the DHCP server is a DHCP server that allocates the IP address carried in the DHCP request message.
  • the user plane data transmission based on this example will be described in detail below with reference to FIG. 12 .
  • Example 2 after the terminal device completes the registration and initiates a session establishment request, the core network device learns through the subscription data during the session establishment process that the terminal device is a set type of terminal device and/or that the terminal device has activated Fixed network services (or have the right to obtain fixed network services, or the business data flow of the terminal equipment needs to be diverted to the fixed network gateway equipment), and will send corresponding information to the access network equipment, so that the access network equipment will subsequently receive data from Corresponding operations can be performed after the DHCP message of the terminal device.
  • Fixed network services or have the right to obtain fixed network services, or the business data flow of the terminal equipment needs to be diverted to the fixed network gateway equipment
  • the core network device indicates the terminal device to the access network device
  • the session establishment is rejected and/or the terminal device is not authenticated, or does not send indication information to the access network device; after receiving the DHCP discovery message from the terminal device, the access network device inserts an inaccessible line ID or The DHCP discovery message is not processed.
  • the core The network device obtains instruction information from the access network device and sends the instruction information to the access network device; the access network device can establish AN resources with the terminal device, and after receiving the DHCP discovery message from the terminal device, insert the The line ID, so that the terminal device can pass the authentication of the AAA server, establish a connection with the fixed network gateway device, and obtain the IP address assigned by the DHCP server, so that the terminal device can pass through the access network device and the fixed network gateway device.
  • Data interaction with the data network It helps to reduce the data processing and transmission pressure of the core network.
  • Example 2 only takes the terminal device adopting the IPoE protocol as an example, and the technical solution shown in Example 2 is also applicable to the scenario where the terminal device adopts other transmission protocols.
  • the difference is that each network element interacts with PPPoE-related messages, such as PADI, PADO, PADR, and PADS.
  • the access network device can insert an accessible line ID in the PADI message; the fixed network gateway device will assign a PPPoE session identifier to the terminal device; the terminal device will also exchange LCP messages with the fixed network gateway device through the access network device to Complete the configuration of data link parameters, and complete the authentication phase and network parameter negotiation phase, so that the terminal device obtains an IP address.
  • Fig. 8 is another example of the method for transmitting data provided by this application.
  • the connection establishment process shown in FIG. 8 may be based on the terminal device completing the first registration process in Example 1 and based on the user plane protocol stack shown in FIG. 3 .
  • the terminal device will initiate the session establishment process, and the core network will participate in the session establishment process.
  • the difference from Example 2 is that SMF replaces the terminal device and interacts with the fixed network gateway device to complete the authentication of the terminal device and obtain the IP address. , and send the acquired IP address to the terminal device through the session establishment process.
  • Step 801 the terminal device sends a session establishment request message to the AMF.
  • Step 802 after receiving the session establishment request message from the terminal device, the AMF selects an appropriate SMF.
  • step 803 the AMF sends a session context creation request message to the SMF.
  • Step 804 the SMF interacts with the UDM to obtain the subscription data of the terminal device.
  • the subscription data may include the type of the terminal device and the second service information.
  • the second service information is used to indicate whether the terminal device has subscribed to the fixed network service (or whether it has the right to obtain the fixed network service, or whether the service data flow of the terminal device needs to be diverted to the fixed network gateway device).
  • Step 805 the SMF determines the type information of the terminal device and/or whether the terminal device has subscribed to the fixed network service (or whether it has the right to obtain the fixed network service, or whether the service data flow of the terminal device needs to be diverted to fixed network gateway device).
  • the SMF may refuse to establish the session. In this case, steps 806-808 may be performed subsequently.
  • the SMF allows the establishment of The session, and the SMF does not need to select the UPF and assign an IP address to the end device. In this case, steps 809-823 may be performed subsequently.
  • step 806 the SMF sends a session context creation response message to the AMF.
  • the create session context response message may carry N1 session information.
  • N1 session information can carry session rejection information, such as PDU session reject.
  • SMF sends Nsmf_PDUSession_CreateSMContext Response to AMF.
  • step 807 if the N1 session information is received in step 806, the AMF sends the N1 session information to the terminal device through a NAS message. If the N2 session information is received in step 806, the AMF sends the N2 session information to the access network device.
  • Step 808 after receiving the N2 message from the AMF, the access network device determines that the session establishment or authentication of the terminal device fails, and forwards the N1 session information to the terminal device, wherein the N1 session information includes session rejection information.
  • steps 801-808 For a more detailed description of steps 801-808, reference may be made to steps 701-708, which will not be repeated here.
  • Step 809 the SMF sends a DHCP discovery message to the fixed network gateway device.
  • the DHCP discovery message includes an accessible line ID. That is to say, SMF will insert the accessible line ID in the DHCP message. Wherein, the accessible line ID may be used to identify the terminal device.
  • a possible implementation manner is that the SMF sends a DHCP discovery message to the fixed network gateway device through a network exposure function (network exposure function, NEF) network element.
  • NEF network exposure function
  • step 810 may also be performed at any step before step 809 .
  • step 810 the SMF obtains the ID of an accessible line.
  • a possible implementation manner is that the SMF obtains an accessible line ID in an out-of-band manner.
  • an accessible line ID can be configured for the SMF in a preconfigured manner.
  • the SMF may also obtain the ID of an inaccessible line.
  • Step 811 after receiving the DHCP discovery message from the SMF, the fixed network gateway device sends the DHCP discovery message to the DHCP server.
  • Step 812 after receiving the DHCP discovery message from the fixed network gateway device, the DHCP server obtains information such as the line ID in the DHCP discovery message, constructs first authentication information required for authentication, and sends an access request message to the AAA server.
  • the access request message may include the first authentication information.
  • Step 813 the AAA server authenticates the terminal device according to the first authentication information.
  • the line ID can be used to identify the terminal device, and the first authentication information is constructed according to the line ID, the first authentication information can identify the terminal device, so the AAA server can authenticate the terminal device according to the first authentication information.
  • the authentication results of the AAA server are different, and the subsequent steps are also different.
  • the AAA server does not pass the authentication of the terminal device, and steps 814-815 may be performed subsequently. If the line ID in the first authentication information is an accessible line ID, the AAA server passes the authentication of the terminal device, and subsequently, steps 816-823 may be performed. In this example, since the SMF inserts the accessible line ID in the DHCP discovery message, the AAA server will pass the authentication of the terminal device.
  • Step 814 the AAA server sends an access rejection message to the DHCP server.
  • Step 815 after receiving the access rejection message from the AAA server, the DHCP server sends a DHCP NACK message to the SMF through the fixed network gateway device.
  • Step 816 the AAA server sends an access acceptance message to the DHCP server.
  • Step 817 after receiving the access acceptance message from the AAA server, the DHCP server assigns an IP address to the terminal device, includes the IP address assigned to the terminal device in the DHCP offer message, and sends the DHCP offer message to the SMF through the fixed network gateway device. information.
  • the SMF may perform steps 818 and 819 .
  • Step 818 after receiving the DHCP offer message, the SMF sends a DHCP request message to the DHCP server through the fixed network gateway device.
  • the SMF sends a DCHP request message according to one of the multiple DHCP offer messages (for example, the first received DHCP offer message), where the DHCP request message may include the IP address assigned by the DHCP server .
  • Step 819 the DHCP server sends a DHCP ACK message to the SMF through the fixed network gateway device.
  • the DHCP server is a DHCP server that allocates the IP address carried in the DHCP request message.
  • Step 820 after receiving the DHCP ACK message, the SMF can acquire the indication information, and the SMF sends an N1N2 message delivery message to the AMF.
  • the N1N2 message transfer message may carry a session identifier, N1 session information, and N2 session information.
  • the N1 session information is sent by the SMF to the terminal device through the AMF, and the N1 session information can include session acceptance information (such as PDU session accept) and the IP address assigned by the DHCP server to the terminal device, such as PDU session accept.
  • the N2 session information is sent by the SMF to the access network device through the AMF.
  • the N2 session information may include a session identifier and indication information. The description of the indication information may refer to the above description, which will not be repeated here.
  • SMF sends Namf_Communication_N1N2Message Transfer to AMF.
  • Step 821 after receiving the N1N2 message delivery message, the AMF sends an N2 session request message to the access network device.
  • the N2 session request message may carry N2 session information and N1 session information from the SMF.
  • the N2 session information is sent to the access network device through the N2 message, and the N1 session information is sent to the terminal device through the NAS message.
  • the NAS message is sent by the AMF to the access network device through the N2 message, and then forwarded by the access network device to the terminal device.
  • a possible implementation is that the AMF sends an N2PDU Session Request to the access network device.
  • Step 822 after receiving the N2 message from the AMF, the access network device determines through the indication information in the N2 session information that it needs to establish a user plane connection with the fixed network gateway device, or in other words, determines that it is necessary to offload the user plane data of the terminal device to the fixed network gateway device.
  • the access network device may establish AN resources with the terminal device, and forward N1 session information to the terminal device, where the N1 session information includes session acceptance information.
  • the N1 session information may be carried in a NAS message, for example, may be carried in a PDU Session Accept.
  • Step 823 the access network device sends an N2 session response message to the AMF.
  • a possible implementation manner is that the access network device sends the N2PDU Session Response to the AMF.
  • the user plane data transmission based on this example will be described in detail below with reference to FIG. 12 .
  • Example 3 after the terminal device completes the registration and initiates the session establishment request, the core network device learns through the subscription data during the session establishment process that the terminal device is a set type of terminal device and/or that the terminal device has subscribed to For fixed network services (or have permission to obtain fixed network services, or the service data flow of the terminal equipment needs to be diverted to the fixed network gateway device), send a DHCP discovery message to the fixed network gateway device to complete IPoE authentication and obtain an IP address, and can In the session establishment process, the IP address is sent to the terminal device, and at the same time, the access network device can know that there is no need to establish an N3 tunnel with the UPF by sending instruction information to the access network device.
  • the access network device can send the user plane data to the fixed network gateway device instead of the UPF, so that the terminal device can communicate with the fixed network gateway device through the access network device and the fixed network gateway device.
  • Data network for data interaction. It helps to reduce the data processing and transmission pressure of the core network.
  • Example 3 also only takes the terminal device adopting the IPoE protocol as an example, and the technical solution shown in Example 3 is also applicable to the scenario where the terminal device adopts other transmission protocols.
  • the difference is that each network element interacts with PPPoE-related messages, such as PADI, PADO, PADR, and PADS.
  • the SMF can insert the accessible
  • the fixed network gateway device will assign a PPPoE session identifier to the terminal device; the SMF and the fixed network gateway device will also exchange LCP messages to complete the configuration of data link parameters, and complete the authentication phase and network parameter negotiation phase, so that the terminal device Get the IP address.
  • Fig. 9 is another example of the method for transmitting data provided by this application.
  • the connection establishment process shown in FIG. 9 may be based on the terminal device completing the second registration process or the third registration process in Example 1, and based on the user plane protocol stack shown in FIG. 3 .
  • the access network device since the access network device has directly or indirectly learned the type information of the terminal device and/or whether the terminal device has subscribed to the fixed network service (or whether it has the right to obtain the fixed network service, or the Whether the service data flow of the terminal device needs to be offloaded to the fixed network gateway device), therefore, the access network device does not need to obtain this information through the session establishment process.
  • the terminal device After the terminal device completes the registration process, it can perform IPoE authentication, obtain an IP address, and establish AN resources with the access network device.
  • Step 901 the terminal device sends a session establishment request message to the access network device.
  • Step 902 the access network device intercepts the session establishment request message sent by the terminal device, and determines according to the message that the terminal device is establishing a session. Because the access network device obtains the type information of the terminal device during the registration process and/or whether the terminal device has opened the fixed network service (or whether it has the right to obtain the fixed network service, or whether the service data flow of the terminal device needs to be diverted to the fixed network Gateway device), if the access network device confirms that the terminal device is a set type of terminal device and/or the terminal device has opened the fixed network service (or has the right to obtain the fixed network service, or the terminal device's service data flow needs to be offloaded to the fixed network gateway device), the access network device can know that it needs to intercept the NAS message sent by the terminal device after the registration process.
  • the access network device intercepts the NAS message sent by the terminal device, and learns that the message is a session establishment request message.
  • the access network device determines that the terminal device is a set type of terminal device and/or the terminal device has opened the fixed network service (or has the right to obtain the fixed network service, or the service data flow of the terminal device needs to be offloaded) to the fixed network gateway device), the access network device can establish AN resources with the terminal device.
  • the access network device may also send a session acceptance message to the terminal device.
  • Step 903 the terminal device sends a DHCP discovery message to the access network device.
  • the DHCP discovery message is carried on the cellular air interface or on the DRB. For example, if steps 901-902 are not performed before step 903, the DHCP discovery message may be carried in the RRC message. For another example, if steps 901-902 are performed before step 903, the DHCP discovery message may also be carried in the DRB.
  • the DHCP discovery message may indicate the type of the terminal device.
  • the option 60 (Option 60) field of the DHCP discovery message can carry information that can indicate the type of the terminal device.
  • Step 904 after receiving the DHCP discovery message from the terminal device, the access network device determines whether the terminal device has opened the fixed network service (or whether it has the authority to obtain the fixed network service, or whether the service data flow of the terminal device needs to be offloaded to the fixed network service). network gateway device), and insert an accessible line ID or an inaccessible line ID into the DHCP discovery message.
  • step 905 may also be performed.
  • Step 905 the access network device obtains the ID of an accessible line.
  • Step 906 the access network device sends a DHCP discovery message to the fixed network gateway device.
  • Step 907 after receiving the DHCP discovery message from the access network device, the fixed network gateway device sends the DHCP discovery message to the DHCP server.
  • Step 908 After receiving the DHCP discovery message from the fixed network gateway device, the DHCP server obtains information such as line ID in the DHCP discovery message, constructs first authentication information required for authentication, and sends an access request message to the AAA server.
  • Step 909 the AAA server authenticates the terminal device according to the first authentication information.
  • the authentication results of the AAA server are different, and the subsequent steps are also different. If the line ID in the first authentication information is an inaccessible line ID, the AAA server does not pass the authentication of the terminal device, and steps 910-911 may be performed subsequently. If the terminal device has subscribed to the fixed network service (or has the right to obtain the fixed network service), steps 912-916 may be performed.
  • Step 910 the AAA server sends an access deny (access deny) message to the DHCP server.
  • Step 911 after receiving the access rejection message from the AAA server, the DHCP server sends a DHCPNACK message to the terminal device through the fixed network gateway device and the access network device.
  • the access network device may also release the AN resources established with the terminal device.
  • Step 912 the AAA server sends an access acceptance message to the DHCP server.
  • Step 913 after receiving the access acceptance message from the AAA server, the DHCP server assigns an IP address to the terminal device, and the IP address assigned to the terminal device is included in the DHCP offer message, and is passed through the fixed network gateway device and the access network device Send a DHCP offer message to the end device.
  • Step 914 after receiving the DHCP offer message, the terminal device sends a DHCP request message to the DHCP server through the access network device and the fixed network gateway device.
  • Step 915 the DHCP server sends a DHCP ACK message to the terminal device through the fixed network gateway device and the access network device.
  • the DHCP server is a DHCP server that allocates the IP address carried in the DHCP request message.
  • Step 916 if the DHCP ACK message is received, the access network device can establish AN resources with the terminal device. This step is optional. For example, if steps 901-902 are not performed, then step 916 may be performed.
  • steps 903-915 For a more detailed description of the above steps 903-915, reference may be made to steps 713-725, which will not be repeated here.
  • the user plane data transmission based on this example will be described in detail below with reference to FIG. 12 .
  • the access network device can directly or indirectly know the type information of the terminal device and/or whether to subscribe to the fixed network service (or whether it has the right to obtain the fixed network service, or whether the terminal device Whether the business data flow needs to be offloaded to the fixed network gateway device), so as to determine whether to establish AN resources with the terminal device according to this information, and insert the corresponding line ID in the DHCP discovery message sent by the terminal device according to this information.
  • the terminal device does not need to initiate the session establishment process (or can send a session establishment request message, but the message is intercepted by the access network device, and the core network device does not actually participate in the session establishment process), which can further reduce the network-side signal order overhead.
  • Example 4 also only takes the terminal device adopting the IPoE protocol as an example, and the technical solution shown in Example 4 is also applicable to the scenario where the terminal device adopts other transmission protocols.
  • the difference is that each network element interacts with PPPoE-related messages, such as PADI, PADO, PADR, and PADS.
  • the access network device can insert in the PADI message Accessible line ID; the fixed network gateway device will assign a PPPoE session identifier to the terminal device; the terminal device will also exchange LCP messages with the fixed network gateway device through the access network device to complete the configuration of data link parameters and complete the authentication phase In the phase of negotiating with the network parameters, the terminal equipment obtains an IP address.
  • Fig. 10 is another example of the method for transmitting data provided by this application.
  • the connection establishment process shown in FIG. 10 may be based on the terminal device executing the second registration process or the third registration process in Example 1 and the user plane protocol stack shown in FIG. 4 .
  • the core network device does not participate in the user plane connection establishment process
  • the access network device as a fixed network terminal device, establishes a connection with the fixed network gateway device in advance, and the access network device can perform network address translation (NAT ) to realize data interaction between the terminal device and the data network through the access network device and the fixed network gateway device.
  • NAT network address translation
  • Step 1001 the access network device sends a DHCP discovery message to the fixed network gateway device.
  • the DHCP discovery message includes an accessible line ID. That is to say, the access network device will insert an accessible line ID into the DHCP message, so that the access network device can pass the IPoE authentication.
  • step 1002 may also be performed.
  • Step 1002 the access network device acquires an accessible line ID and IP address resource pool.
  • a possible implementation manner is that the access network device acquires an accessible line ID and IP address resource pool in an out-of-band manner.
  • an accessible line ID and IP address resource pool may be configured for the access network device in a preconfigured manner.
  • the IP address in the IP address resource pool can be used when the access network device determines that the terminal device is a set type of terminal device and/or the terminal device has opened a fixed network service (or has the right to obtain the fixed network service or the service data of the terminal device) When the stream needs to be distributed to the fixed network gateway device), it is allocated to the terminal device.
  • Step 1003 after receiving the DHCP discovery message from the access network device, the fixed network gateway device sends the DHCP discovery message to the DHCP server.
  • Step 1004 after receiving the DHCP discovery message from the fixed network gateway device, the DHCP server obtains information such as the line ID in the DHCP discovery message, constructs first authentication information required for authentication, and sends an access request message to the AAA server.
  • Step 1005 the AAA server authenticates the access network device according to the first authentication information.
  • Step 1006 the AAA server sends an access acceptance message to the DHCP server.
  • the access network device Since the line ID in the access request message is an accessible line ID, the access network device will pass the authentication of the AAA server.
  • Step 1007 after receiving the access acceptance message from the AAA server, the DHCP server assigns an IP address to the access network device, and includes the IP address assigned to the access network device in the DHCP offer message, and sends the IP address to the access network device through the fixed network gateway device.
  • the access network device sends a DHCP offer message.
  • the access network device may perform steps 1008 and 1009 .
  • Step 1008 after receiving the DHCP offer message, the access network device sends a DHCP request message to the DHCP server through the fixed network gateway device.
  • the access network device sends a DCHP request message according to one of the multiple DHCP offer messages (for example, the first received DHCP offer message), where the DHCP request message may include the DHCP server allocation IP address.
  • Step 1009 the DHCP server sends a DHCP ACK message to the access network device through the fixed network gateway device.
  • the DHCP server is a DHCP server that allocates the IP address carried in the DHCP request message.
  • the access network device as a fixed network terminal device, establishes a connection with the fixed network gateway device, and obtains the IP address assigned to the access network device.
  • step 1010 and step 1011 may continue to be performed.
  • Step 1010 the terminal device executes the second registration process or the third registration process as shown in Example 1.
  • the access network device can directly or indirectly know the type information of the terminal device and/or whether the terminal device has subscribed to the fixed network service (or whether it has the right to obtain the fixed network service or the terminal device's Whether the service data flow needs to be diverted to the fixed network gateway device).
  • Step 1011 if the terminal device is a terminal device of the set type and/or the terminal device has opened the fixed network service (or has the right to obtain the fixed network service, or the service data flow of the terminal device needs to be diverted to the fixed network gateway device), then The access network device establishes AN resources with the terminal device, and assigns an IP address to the terminal device.
  • the terminal device is not a set type of terminal device and/or the terminal device has not subscribed to the fixed network service (or has no authority to obtain the fixed network service, or the service data flow of the terminal device does not need to be diverted to the fixed network gateway device), then access The network device may not establish AN resources with the terminal device, nor assign an IP address to the terminal device.
  • the IP address allocated to the terminal device may be an IP address in the IP address resource pool obtained in step 1002 .
  • the access network device can maintain the mapping relationship between the IP address assigned by the access network device to the terminal device and the IP address assigned by the DHCP server to the access network device, so as to realize the NAT function of the access network device, thereby realizing
  • the terminal device performs data interaction with the data network through the access network device and the fixed network gateway device.
  • the user plane data transmission based on this example will be described in detail below with reference to FIG. 13 .
  • the access network device as a fixed network terminal device, establishes a connection with the fixed network gateway device in advance, and obtains the IP address assigned to the access network device; when the terminal device completes the second After the registration process or the third registration process, if the terminal device is a set type of terminal device and/or the terminal device has opened a fixed network service (or has the right to obtain the fixed network service or the service data flow of the terminal device needs to be diverted to the fixed network network gateway device), the access network device can establish AN resources with the terminal device, and assign an IP address to the terminal device. Furthermore, the access network device can implement data interaction between the terminal device and the data network through the access network device and the fixed network gateway device by performing network address translation. In Example 5, the session establishment process can also be omitted, which can further reduce the signaling overhead on the network side.
  • Example 5 also only takes the terminal device adopting the IPoE protocol as an example, and the technical solution shown in Example 5 is also applicable to the scenario where the terminal device adopts other transmission protocols.
  • each network element interacts with PPPoE-related messages, such as PADI, PADO, PADR, and PADS.
  • PADI PADI, PADO, PADR, and PADS.
  • the network device allocates a PPPoE session identifier, and then the access network device and the fixed network gateway device will also exchange LCP messages to complete the configuration of data link parameters, and complete the authentication phase and network parameter negotiation phase, so that the access network device obtains an IP address.
  • the terminal device interacts with the access network device, and the access network device assigns a PPPoE session identifier and an IP address to the terminal device.
  • Fig. 11 is another example of the method for transmitting data provided by this application.
  • connection establishment process shown in FIG. 11 may be based on the terminal device completing the second registration process in Example 1 and based on the user plane protocol stack shown in FIG. 3 .
  • the core network device also does not participate in the connection establishment process, and the registration process of the terminal device may not include the authentication process of the fixed network service. Network service authentication.
  • Step 1101 if the access network device confirms that the terminal device is successfully registered, then the access network device establishes AN resources with the terminal device.
  • the N2 session message from the AMF includes registration acceptance information and information indicating that the terminal device is a terminal device of a set type, that is, the access network device can determine that the terminal device is a set type of terminal device. If a certain type of terminal equipment is successfully registered, the access network equipment can establish AN resources with the terminal equipment.
  • step 1101 is an optional step, that is, before performing the user plane connection establishment process, the terminal device and the access network device may or may not establish AN resources.
  • Step 1102 the terminal device sends a DHCP discovery message to the access network device.
  • the DHCP discovery message may include information used to indicate the corresponding user name and password of the terminal device.
  • the above DHCP discovery message is carried on the cellular air interface or on the DRB.
  • the DHCP discovery message may be carried in an RRC message.
  • the DHCP discovery message may also be carried in the DRB.
  • the access network device may determine the type information of the terminal device according to a DHCP discovery message. For example, the access network device confirms that the terminal device is a terminal device of a set type by identifying the DHCP discovery message. For another example, the terminal device can carry type information that can indicate the terminal device in the Option 60 (Option 60) field of the DHCP discovery message, and the access network device can confirm that the terminal device is a terminal device of the set type through this field.
  • the access network device may carry type information that can indicate the terminal device in the Option 60 (Option 60) field of the DHCP discovery message, and the access network device can confirm that the terminal device is a terminal device of the set type through this field.
  • Step 1103 after receiving the DHCP discovery message from the terminal device, the access network device inserts the line ID into the DHCP discovery message.
  • the line IDs inserted by the access network equipment do not need to be divided into accessible line IDs and inaccessible line IDs as in example 2 to example 5.
  • the line ID can be mapped with the MAC address of the terminal device, that is, one MAC address corresponds to one line ID, so that the access network device, the fixed network gateway device, and the AAA server can distinguish different lines according to the line ID.
  • Terminal Equipment Terminal Equipment
  • step 1104 may also be performed.
  • Step 1104 the access network device obtains the line ID.
  • a possible implementation manner is that the access network device obtains the line ID in an out-of-band manner.
  • the line ID may be configured for the access network device in a preconfigured manner.
  • steps 1103 and 1104 are optional steps.
  • Step 1105 the access network device sends a DHCP discovery message to the fixed network gateway device.
  • Step 1106 after receiving the DHCP discovery message from the access network device, the fixed network gateway device sends the DHCP discovery message to the DHCP server.
  • Step 1107 after receiving the DHCP discovery message from the fixed network gateway device, the DHCP server obtains information such as the user name and password in the DHCP discovery message, constructs the first authentication information required for authentication, and sends an access request message to the AAA server .
  • the access request message may include the first authentication information.
  • Step 1108 the AAA server authenticates the terminal device according to the first authentication information.
  • AAA verifies whether the terminal device has opened the fixed network service according to the user name and password (or whether it has the right to obtain the fixed network service, or whether the service data flow of the terminal device needs to be diverted to the fixed network gateway device), and at the same time, the AAA server Also verify that another device is already authenticated with that username and password. If the terminal device has opened the fixed network service (or has the right to obtain the fixed network service, or the service data flow of the terminal device needs to be diverted to the fixed network gateway device), and no other device passes the authentication using the user name and password, the AAA server It is determined that the authentication of the terminal device is successful.
  • AAA determines that the authentication of the terminal device fails.
  • the authentication results of the AAA server are different, and the subsequent steps are also different.
  • steps 1109-1111 may be performed.
  • Step 1109 the AAA server sends an access rejection message to the DHCP server.
  • Step 1110 after receiving the access rejection message from the AAA server, the DHCP server sends a DHCP NACK message to the terminal device through the fixed network gateway device and the access network device.
  • step 1111 may also be executed.
  • Step 1111 the access network device releases the AN resource established with the terminal device according to the DHCP NACK message.
  • steps 1112-1116 may be performed.
  • Step 1112 the AAA server sends an access acceptance message to the DHCP server.
  • Step 1113 after receiving the access acceptance message from the AAA server, the DHCP server assigns an IP address to the terminal device, and the IP address assigned to the terminal device is included in the DHCP offer message, and passed through the fixed network gateway device and the access network device Send a DHCP offer message to the end device.
  • the DHCP offer message may further include second authentication information, so that the terminal device can perform authentication according to the second authentication information, and identify whether the DHCP offer message comes from a trusted DHCP server.
  • the DHCP discovery message in step 1102 is a broadcast message
  • there may be multiple DHCP servers receiving the DHCP discovery message so in step 1110, there may also be multiple DHCP servers that assign an IP address to the terminal device and send a DHCP Provide news.
  • the terminal device receives DHCP offer messages sent from multiple DHCP servers, the terminal device may perform steps 1114 and 1115 .
  • Step 1114 after receiving the DHCP offer message, the terminal device sends a DHCP request message to the DHCP server through the access network device and the fixed network gateway device.
  • the terminal device sends a DCHP request message according to one of the multiple DHCP offer messages (for example, the first received DHCP offer message), where the DHCP request message may include the IP address assigned by the DHCP server. address.
  • Step 1115 the DHCP server sends a DHCP ACK message to the terminal device through the fixed network gateway device and the access network device.
  • the DHCP server is a DHCP server that allocates the IP address carried in the DHCP request message.
  • step 1101 if step 1101 is not performed before step 1102, then step 1116 may be performed.
  • Step 1116 the access network device establishes AN resources with the terminal device according to the received DHCP ACK message.
  • the user plane data transmission based on this example will be described in detail below with reference to FIG. 12 .
  • Example 6 the fixed network authentication is decoupled from the registration process of the terminal device on the core network side. Providers are decoupled from network operators. This example also omits the session establishment process, and the registration process of the terminal device adopts the second registration process, so that the access network device can know whether the registration of the terminal device is successful. For a successfully registered terminal device, the access network device will establish an AN resource with it or forward a DHCP discovery message to it.
  • Example 6 also only takes the terminal device adopting the IPoE protocol as an example, and the technical solution shown in Example 6 is also applicable to the scenario where the terminal device adopts other transmission protocols.
  • PPPoE-related messages such as PADI, PADO, PADR, and PADS.
  • PADI can include user names and passwords, and access network devices can Insert the line ID into the PADI message; the fixed network gateway device will assign a PPPoE session identifier to the terminal device; the terminal device will also exchange LCP messages with the fixed network gateway device through the access network device to complete the configuration of data link parameters and complete the authentication Phase and network parameter negotiation phase, so that the terminal device obtains an IP address.
  • Fig. 12 is an example of the data transmission process provided by this application.
  • the data transmission process shown in FIG. 12 may be applicable to the user plane connection establishment process shown in Example 2, Example 3, Example 4, and Example 6 above.
  • the terminal device sends uplink data to the application server (application server, AS) through the access network device and the fixed network gateway device, and the application server sends downlink data to the terminal device through the fixed network gateway device and the access network device.
  • application server application server, AS
  • Fig. 13 is another example of the data transmission process provided by this application.
  • FIG. 13 takes two terminal devices as an example to describe how the access network device converts the IP address and the session identifier during the uplink and downlink data transmission. In an implementation manner, if the terminal device adopts the IPoE protocol, the access network device does not need to perform session identifier conversion.
  • the terminal device 1 sends uplink data to the access network device, wherein the source IP address of the uplink data is IP@1, the port number is 1, and the session identifier 1 is carried; the access network device sends the uplink data from the terminal device 1 Replace the source IP address of the source IP address with IP@3, the port number with 2, replace the session ID with session ID 3, and send it to the AS through the fixed network gateway device;
  • the terminal device 2 sends uplink data to the access network device, wherein the source IP address of the uplink data is IP@2, the port number is 1, and carries the session identifier 2; the access network device sends the uplink data from the terminal device 2 Replace the source IP address with IP@3, the port number with 3, replace the session ID with session ID 3, and send it to the AS through the fixed network gateway device.
  • the access network device receives downlink data, wherein the destination IP address of the downlink data is IP@3, the port number is 2, and carries the session identifier 3; the access network device determines the downlink data according to the destination IP address and port number It is to be sent to terminal device 1; the access network device converts the destination IP address of the downlink data to IP@1, converts the port number to 1, replaces the session ID with session ID 1, and sends the downlink data to terminal device 1 .
  • the access network device receives the downlink data, wherein the destination IP address of the downlink data is IP@3, the port number is 3, and carries the session identifier 3; the access network device determines that the downlink data is To be sent to terminal device 2; the access network device converts the destination IP address of the downlink data to IP@2, converts the port number to 1, replaces the session ID with session ID 2, and sends the downlink data to terminal device 2.
  • the apparatus in FIG. 14 or FIG. 15 includes corresponding hardware structures and/or software modules for performing various functions.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software with reference to the units and method steps of the examples described in the embodiments disclosed in the present application. Whether a certain function is executed by hardware or computer software drives the hardware depends on the specific application scenario and design constraints of the technical solution.
  • FIG. 14 and FIG. 15 are schematic structural diagrams of possible devices provided by the embodiments of the present application. These devices can be used to realize the functions of the access network device, the core network device and the AAA server in the above method embodiments, and thus can also realize the beneficial effects of the above method embodiments.
  • an apparatus 1400 includes a transceiver unit 1410 and a processing unit 1420 .
  • the transceiving unit 1410 is used to: acquire indication information, the indication information is used by the access network device through the user interface with the fixed network gateway device
  • the data of the terminal equipment is connected and transmitted, and the access network equipment supports 3GPP access type; the transceiver unit 1410 and the processing unit 1420 cooperate with each other to: transmit the data of the terminal equipment through the user plane connection according to the instruction information .
  • the indication information includes information used to indicate the set type of user plane data.
  • the indication information includes information for indicating that the terminal device is a terminal device of a set type.
  • the indication information is included in one or more of the following information: registration acceptance information, authentication passing information, session acceptance information, and session type information.
  • the transceiving unit 1410 is specifically configured to: acquire the indication information in a registration process of the terminal device; or acquire the indication information in a session establishment process of the terminal device.
  • the transceiving unit 1410 is specifically configured to: the access network device receives a first message from the terminal device, and the first message is used to request access management for the terminal device
  • the processing unit 1420 is specifically configured to: acquire first information according to the indication information, and the first information is information that can pass the authentication of the access management;
  • the transceiver unit 1410 is specifically configured to: The fixed network gateway device sends the first information; receives a second message from the fixed network gateway device, the second message indicates that the terminal device has passed the authentication of the access management; sends the terminal device Send the second message.
  • the first information includes a line identifier that can pass the authentication of the access management.
  • the transceiving unit 1410 is specifically configured to: receive a first message from the terminal device, the first message is used to request access management for the terminal device, and the first message Including second information, where the second information is information used for authentication of the access management; the processing unit 1420 is specifically configured to: acquire third information according to the second information, and use the third information to To identify the terminal device; the transceiver unit 1410 is specifically further configured to: send the second information and the third information to the fixed network gateway device; receive the second message from the fixed network gateway device, The second message indicates that the terminal device has passed the authentication of the access management; and sending the second message to the terminal device.
  • the transceiving unit 1410 is specifically configured to: receive a first message from the terminal device, the first message is used to request access management for the terminal device, and the first message including second information, where the second information is authentication information for the access management; sending the second information to the fixed network gateway device; receiving a second message from the fixed network gateway device, The second message indicates that the terminal device has passed the authentication of the access management; and sending the second message to the terminal device.
  • the third information includes a line identifier used to identify the terminal device.
  • the second information includes any one or more of the following: a user name, a password, and a MAC address of the terminal device.
  • the first message is a DHCP discovery message, a DHCP request message, a PADI message or a PADR message.
  • the transceiving unit 1410 is further configured to: send a third message to the fixed network gateway device, where the third message is used to request access management for the access network device, and the The third message includes fourth information, where the fourth information is information that can pass the authentication of the access management; receive the fourth message sent by the gateway device, and the fourth message indicates that the access network device passes the For the authentication of the access management, the fourth message includes the first Internet Protocol IP address of the access network device.
  • the fourth information includes a line identifier that can pass the authentication of the access management.
  • the processing unit 1420 is specifically configured to: assign a second IP address to the terminal device, where the second IP address corresponds to the first IP address; the transceiver unit 1410 is further configured to: : receiving first user plane data from the terminal device, where the first user plane data includes the second IP address; the processing unit 1420 is further configured to: use the second IP address in the first user plane data The IP address is replaced with the first IP address to obtain the second user plane data; the transceiving unit 1410 is further configured to: send the second user plane data.
  • the transceiving unit 1410 is further configured to: receive the first session identifier assigned by the fixed network gateway device to the access network device; the processing unit 1420 is further configured to: The device allocates a second session identifier, where the second session identifier corresponds to the first session identifier; and replaces the second session identifier in the first user plane data with the first session identifier.
  • the transceiving unit 1410 is further configured to: acquire or preconfigure at least one IP address and/or at least one session identifier, the second IP address is one of the at least one IP address, so The second session identifier is one of the at least one session identifier.
  • the terminal device of the set type is a fixed network terminal device.
  • the transceiver unit 1410 is used to: obtain indication information, the indication information is used for the access network equipment to connect with the fixed network gateway equipment through the user plane transmitting the data of the terminal device; sending the indication information to the access network device, where the access network device supports the 3GPP access type.
  • the indication information includes information used to indicate the set type of user plane data.
  • the indication information includes information for indicating that the terminal device is the terminal device of the set type.
  • the indication information is included in one or more of the following information: registration acceptance information, authentication passing information, session acceptance information, and session type information.
  • the transceiving unit 1410 is specifically configured to: send the indication information to the access network device during the registration process of the terminal device; or, during the session establishment process of the terminal device Send the indication information to the access network device.
  • the transceiving unit 1410 is specifically configured to: obtain the subscription data of the terminal device from a network element with a unified data management function; and obtain the indication information according to the subscription data.
  • the transceiving unit 1410 is specifically configured to: acquire type information of the terminal device, where the type information of the terminal device indicates that the terminal device is a terminal device of the set type; according to the Type information to obtain the indication information.
  • the type information is included in the subscription data of the terminal device; or, the type information comes from the terminal device.
  • the core network device is a session management network element
  • the processing unit 1420 is configured to: skip a process of selecting a user plane function network element and/or assigning an IP address to the terminal device.
  • the core network device is a session management network element
  • the transceiver unit 1410 is further configured to: send a fifth message to the fixed network gateway device, and the fifth message is used to request for the The terminal device performs access management, the fifth message includes fifth information, and the fifth information is information that can pass the authentication of the access management; receiving the sixth message from the fixed network gateway device, the The sixth message indicates that the terminal device has passed the authentication of the access management.
  • the fifth information includes a line identifier that can pass the authentication of the access management.
  • the terminal device of the set type is a fixed network terminal device.
  • the transceiver unit 1410 is used to: receive the user name and password from the terminal device; the processing unit 1420 is used to: The terminal device performs access management; if the number of terminal devices corresponding to the user name that has passed the access management authentication is greater than a preset threshold, reject the access management of the first number of terminal devices, or enable the first number of terminal devices The device goes offline, and the first number is greater than or equal to the difference between the preset threshold and the number of terminal devices corresponding to the user name that pass the access management authentication.
  • the transceiving unit 1410 is further configured to: receive third information, the third information is used to identify the terminal device; the processing unit 1420 is further configured to: determine the user Name corresponds to the number of terminal devices that have passed the authentication of access management.
  • the third information includes a line identifier used to identify the terminal device.
  • the third information corresponds to the identification information of the terminal device.
  • the identification information of the terminal device includes one or more of the following information: address information, device identification, permanent identification, temporary identification, external identification or internal identification.
  • the device 1500 includes a processor 1510 and an interface circuit 1520 .
  • the processor 1510 and the interface circuit 1520 are coupled to each other.
  • the interface circuit 1520 may be a transceiver or an input/output interface.
  • the apparatus 1500 may further include a memory 1530 for storing instructions executed by the processor 1510 or storing input data required by the processor 1510 to execute the instructions or storing data generated by the processor 1510 after executing the instructions.
  • the processor 1510 is used to implement the functions of the processing unit 1420 described above, and the interface circuit 1520 is configured to implement the functions of the transceiver unit 1410 described above.
  • the chip When the above communication device is a chip applied to access network equipment, the chip implements the functions of the access network equipment in the above method embodiments.
  • the chip receives information from other modules in the access network equipment (such as radio frequency modules or antennas), and the information is sent to the access network equipment by other equipment; or, the chip sends information to other modules in the access network equipment (such as radio frequency module or antenna) to send information, which is sent by the access network device to other devices.
  • the chip When the above communication device is a chip applied to core network equipment, the chip implements the functions of the core network equipment in the above method embodiments.
  • the chip receives information from other modules (such as radio frequency modules or antennas) in the core network equipment, and the information is sent to the core network equipment by other equipment; or, the chip sends information to other modules (such as radio frequency modules or antennas) in the core network equipment. ) to send information, which is sent by the core network equipment to other equipment.
  • the chip When the aforementioned communication device is a chip applied to an AAA server, the chip implements the function of the AAA server in the aforementioned method embodiment.
  • the chip receives information from other modules in the AAA server (such as radio frequency modules or antennas), and the information is sent to the AAA server by other devices; or, the chip sends information to other modules in the AAA server (such as radio frequency modules or antennas) , the information is sent by the AAA server to other devices.
  • the embodiment of the present application also provides a chip, which acquires an instruction and executes the instruction to implement the above method.
  • the chip includes a processor and a data interface, and the processor reads instructions stored in the memory through the data interface to execute the above method.
  • the chip may further include a memory, the memory stores instructions, the processor is configured to execute the instructions stored in the memory, and when the instructions are executed, the processor is configured to execute the above method .
  • An embodiment of the present application further provides a communication system, including any one of the above-mentioned communication devices, or including any one of the above-mentioned chips.
  • the embodiment of the present application also provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and the instructions are used in the methods in the foregoing method embodiments.
  • the embodiment of the present application also provides a computer program product including instructions, where the instructions are used to implement the methods in the above method embodiments.
  • processor in the embodiments of the present application may be a central processing unit (central processing unit, CPU), and may also be other general processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits (application specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.
  • CPU central processing unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor can be a microprocessor, or any conventional processor.
  • Memory in embodiments of the present application may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory.
  • the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory can be random access memory (RAM), which acts as external cache memory.
  • RAM random access memory
  • static random access memory static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory Access memory
  • SDRAM synchronous dynamic random access memory
  • double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • serial link DRAM SLDRAM
  • direct memory bus random access memory direct rambus RAM, DR RAM
  • the disclosed systems, devices and methods may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the functions described above are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disc and other media that can store program codes. .

Landscapes

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

Abstract

本申请提供了一种传输数据的方法和装置，在该方法中支持3GPP接入类型的接入网设备可以获取指示信息，并根据指示信息通过与固网网关设备的用户面连接传输终端设备的数据，其中，指示信息用于所述接入网设备通过与固网网关设备的用户面连接传输终端设备的数据。这样，终端设备的上行数据则可以通过接入网设备发送给固网网关设备，发送给终端设备的下行数据则可以由固网网关设备通过接入网设备发送至终端设备，即将终端设备的用户面数据分流至固网网关设备，有助于降低核心网的数据处理和传输压力。

Description

一种传输数据的方法和装置
本申请要求于2021年07月19日提交中国国家知识产权局、申请号为202110811077.7、申请名称为“一种传输数据的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及一种传输数据的方法和装置。
背景技术
通信系统可以简单地分为四个部分，分别是终端设备、接入网(access network，AN)、核心网(core network，CN)以及数据网络(data network，DN)。终端设备通过接入网、核心网实现与数据网络的数据交互。随着终端设备数量的迅速增长以及通信业务的快速发展，通信网络需要承载海量的数据传输，核心网作为数据处理和分发的中枢，面临着越来越大的数据处理和传输压力。
发明内容
本申请提供一种传输数据的方法和装置，能够降低核心网的数据处理和传输压力。
第一方面，本申请提供了一种传输数据的方法，该方法可以由接入网设备执行，或者，也可以由接入网设备中的芯片或电路执行，本申请对此不作限定，为了便于描述，下面以由接入网设备执行为例进行说明。
所述方法可以包括：接入网设备获取指示信息，所述指示信息用于所述接入网设备通过与固网网关设备的用户面连接传输终端设备的数据，所述接入网设备支持第三代合作伙伴计划(3rd generation partnership project，3GPP)接入类型；所述接入网设备根据所述指示信息通过所述用户面连接传输所述终端设备的数据。
其中，接入网设备支持3GPP接入类型，也可以描述为，接入网设备支持3GPP接入技术、接入网设备支持蜂窝接入类型、或接入网设备支持蜂窝接入技术等。接入网设备支持3GPP接入类型，也可以替换为，接入网设备支持有线接入技术或者接入网设备支持WIFI接入技术等。需要说明的是，接入网设备支持3GPP接入技术可以是完全支持3GPP协议栈，也可以是支持部分3GPP协议栈，例如只支持物理层、介质接入控制(media access control，MAC)层、无线链路控制(radio link control，RLC)层、分组数据汇聚协议(packet data convergence protocol，PDCP)层、服务数据适配协议(service data adaptation protocol，SDAP)层、无线资源控制(radio resource control，RRC)层中的部分协议栈。
这里的用户面连接可以是互联网协议(internet protocol，IP)数据通道、以太数据通道、以及携带虚拟局域网(virtual local area network，VLAN)标识的数据传输通道等，本申请不予限制。
在一种实现方式中，所述用户面连接用于为设定类型的终端设备传输用户面数据。
在一种实现方式中，接入网设备可以从核心网设备获取指示信息。
在上述技术方案中，接入网设备在获取到指示信息后，可以通过与固网网关设备的用户面连接传输终端设备的数据，换句话说，终端设备的上行数据可以通过接入网设备发送给固网网关设备，发送给终端设备的下行数据可以由固网网关设备通过接入网设备发送至终端设备，即将终端设备的用户面数据分流至固网网关设备，有助于降低核心网的数据处理和传输压力。
结合第一方面，在一种实现方式中，所述接入网设备根据所述指示信息通过所述用户面连接传输所述终端设备的数据，包括：所述接入网设备根据所述指示信息，与所述固网网关设备建立所述用户面连接；所述接入网设备通过所述用户面连接传输所述终端设备的数据。
也就是说，如果接入网设备与固网网关设备尚未建立用户面连接，在发送终端设备的数据之前，可以先根据指示信息建立接入网设备与固网网关设备之间的用户面连接。
结合第一方面或其任意一种实现方式，在另一种实现方式中，所述指示信息包括用于指示设定类型的用户面数据的信息。
可以理解为，指示信息用于指示接入网设备通过与固网网关设备的用户面连接来传输设定类型的用户面数据。
结合第一方面或其任意一种实现方式，在另一种实现方式中，所述指示信息包括用于指示所述终端设备为设定类型的终端设备的信息。
可以理解为，指示信息用于指示接入网设备通过与固网网关设备的用户面连接来传输设定类型的终端设备的用户面数据。
在一种实现方式中，设定类型的终端设备可以为固网终端设备。例如，客户端设备、电话、路由器、网络交换机、家庭网关(residential gateway，RG)、机顶盒、固定移动融合产品、家庭网络适配器、以及互联网接入网关等。设定类型的终端设备还可以是手机、增强现实(augmented reality，AR)终端、虚拟现实(virtual reality，VR)终端、平板电脑(Pad)以及其他类型终端。设定类型的终端设备还可以是通过固网网关设备传输数据的终端设备，本申请不予限制。
结合第一方面或其任意一种实现方式，在另一种实现方式中，所述指示信息包括在以下信息中的一个或多个中：注册接受信息、认证通过信息、会话接受信息、以及会话类型信息。
可以理解为，可以通过注册接受信息、认证通过信息、会话接受信息和会话类型信息中的至少一个指示接入网设备通过与固网网关设备的用户面连接传输终端设备的数据。也可以理解为，可以通过注册接受信息、认证通过信息、会话接受信息和会话类型信息中的至少一个所包括的部分或全部信息指示接入网设备通过与固网网关设备的用户面连接传输终端设备的数据。
其中，会话接受信息也可以描述为会话建立接受信息等。
结合第一方面或其任意一种实现方式，在另一种实现方式中，所述指示信息包括以下至少一个：用于指示所述设定类型的用户面数据的信息、用于指示所述终端设备为所述设定类型的终端设备的信息、注册接受信息、认证通过信息、会话接受信息、以及会话类型 信息。
结合第一方面或其任意一种实现方式，在另一种实现方式中，所述接入网设备获取指示信息，包括：所述接入网设备在所述终端设备的注册流程中获取所述指示信息；或者，所述接入网设备在所述终端设备的会话管理流程中获取所述指示信息。其中，会话管理流程可以是会话建立流程、会话修改流程或者会话释放流程。
结合第一方面或其任意一种实现方式，在另一种实现方式中，所述方法还包括：所述接入网设备接收来自所述终端设备的第一消息，所述第一消息用于请求对所述终端设备进行接入管理；所述接入网设备根据所述指示信息，获取第一信息，所述第一信息为可通过所述接入管理的认证的信息；所述接入网设备向所述固网网关设备发送所述第一信息；所述接入网设备接收来自所述固网网关设备的第二消息，所述第二消息指示所述终端设备通过所述接入管理的认证；所述接入网设备向所述终端设备发送所述第二消息。
在一种实现方式中，所述第一信息包括可通过所述接入管理的认证的线路标识(line ID)。
结合第一方面或其任意一种实现方式，在另一种实现方式中，所述方法还包括：所述接入网设备接收来自所述终端设备的第一消息，所述第一消息用于请求对所述终端设备进行接入管理，所述第一消息包括第二信息，所述第二信息为用于进行所述接入管理的认证的信息；所述接入网设备根据所述第二信息，获取第三信息，所述第三信息用于标识所述终端设备；所述接入网设备向所述固网网关设备发送所述第二信息和所述第三信息；所述接入网设备接收来自所述固网网关设备的第二消息，所述第二消息指示所述终端设备通过所述接入管理的认证；所述接入网设备向所述终端设备发送所述第二消息。
在一种实现方式中，所述第二信息包括以下任意一种或多种：用户名、密码、和所述终端设备的MAC地址。
在一种实现方式中，所述第三信息包括用于标识所述终端设备的线路标识。
结合第一方面或其任意一种实现方式，在另一种实现方式中，所述方法还包括：所述接入网设备接收来自所述终端设备的第一消息，所述第一消息用于请求对所述终端设备进行接入管理，所述第一消息包括第二信息，所述第二信息为用于进行所述接入管理的认证的信息；所述接入网设备向所述固网网关设备发送所述第二信息；所述接入网设备接收来自所述固网网关设备的第二消息，所述第二消息指示所述终端设备通过所述接入管理的认证；所述接入网设备向所述终端设备发送所述第二消息。
在一种实现方式中，所述第二信息包括以下任意一种或多种：用户名、密码、和所述终端设备的MAC地址。
结合第一方面或其任意一种实现方式，在另一种实现方式中，所述第三信息与所述终端设备的标识信息对应。
结合第一方面或其任意一种实现方式，在另一种实现方式中，所述终端设备的标识信息包括以下信息中的一项或多项：地址信息、设备标识、永久标识、临时标识、外部标识或内部标识。
结合第一方面或其任意一种实现方式，在另一种实现方式中，所述第三信息预配置于所述接入网设备中或者来自核心网设备。
在一种实现方式中，所述第一消息可以为以下消息中的一种：动态主机配置协议 (dynamic host configuration protocol，DHCP)发现消息、DHCP请求消息、以太网承载点对点协议主动发现初始(point-to-point protocol over Ethernet active discovery initiation，PADI)消息或以太网承载点对点协议主动发现请求(point-to-point protocol over Ethernet active discovery request，PADR)消息。所述第二消息可以为DHCP提供消息(DHCP offer)或DHCP确认消息(DHCP ACK)等。
结合第一方面或其任意一种实现方式，在另一种实现方式中，所述方法还包括：所述接入网设备向所述固网网关设备发送第三消息，所述第三消息用于请求对所述接入网设备进行接入管理，所述第三消息包括第四信息，所述第四信息为可通过所述接入管理的认证的信息；所述接入网设备接收所述网关设备发送的第四消息，所述第四消息指示所述接入网设备通过所述接入管理的认证，所述第四消息包括所述接入网设备的第一IP地址。
例如，可以在与所述固网网关设备建立用户面连接之前执行以上步骤，也可以在与所述固网网关设备建立用户面连接过程中执行以上步骤，也可以在与所述固网网关设备建立用户面连接之后执行以上步骤，本申请不做限制。
在一种实现方式中，所述第四信息包括可通过所述接入管理的认证的线路标识。
结合第一方面或其任意一种实现方式，在另一种实现方式中，所述方法还包括：所述接入网设备为所述终端设备分配第二IP地址，所述第二IP地址对应于所述第一IP地址；所述接入网设备接收来自所述终端设备的第一用户面数据，所述第一用户面数据包括所述第二IP地址；所述接入网设备将所述第一用户面数据中的第二IP地址替换为所述第一IP地址，得到第二用户面数据；所述接入网设备发送所述第二用户面数据。
在一种实现方式中，所述第三消息可以为以下消息中的一种：DHCP发现消息、DHCP请求消息、PADI消息或PADR消息。所述第四消息可以为以下消息中的一种DHCP提供消息或DHCP确认消息等。
结合第一方面或其任意一种实现方式，在另一种实现方式中，所述方法还包括：所述接入网设备接收所述固网网关设备为所述接入网设备分配的第一会话标识；所述接入网设备为所述终端设备分配第二会话标识，所述第二会话标识对应于所述第一会话标识；所述接入网设备将所述第一用户面数据中的第二会话标识替换为所述第一会话标识。
结合第一方面或其任意一种实现方式，在另一种实现方式中，所述方法还包括：所述接入网设备获取或预配置至少一个IP地址和/或至少一个会话标识，所述第二IP地址为所述至少一个IP地址中的一个，所述第二会话标识为所述至少一个会话标识中的一个。
结合第一方面或其任意一种实现方式，在另一种实现方式中，所述第一信息、第三信息、第四信息中的至少一个可以预配置于所述接入网设备中或者来自所述终端设备或者来自核心网设备。
结合第一方面或其任意一种实现方式，在另一种实现方式中，所述指示信息还包括终端设备的IP地址，所述方法还包括：所述接入网设备向所述终端设备转发所述IP地址；所述接入网设备与所述终端设备建立接入网资源。
其中，终端设备的IP地址可以为由固网服务器为其分配的IP地址，例如，DHCP服务器或PPPoE服务器等为其分配的IP地址；终端设备的IP地址也可以为由固网网关设备为其分配的IP地址。
在一种实现方式中，指示信息中还可以包括固网网关设备为终端设备分配的会话标识。
结合第一方面或其任意一种实现方式，在另一种实现方式中，所述方法还包括：所述接入网设备与所述终端设备建立接入网资源。
结合第一方面或其任意一种实现方式，在另一种实现方式中，所述方法还包括：当所述第二消息指示所述终端设备未通过所述接入管理的认证时，所述接入网设备与所述终端设备释放接入网资源。
结合第一方面或其任意一种实现方式，在另一种实现方式中，所述方法还包括：当所述第二消息指示所述终端设备通过所述接入管理的认证时，所述接入网设备与所述终端设备建立接入网资源。
第二方面，本申请提供了一种传输数据的方法，该方法可以由核心网设备执行，或者，也可以由核心网设备中的芯片或电路执行，本申请对此不作限定，为了便于描述，下面以由核心网设备执行为例进行说明。
所述方法可以包括：核心网设备获取指示信息，所述指示信息用于接入网设备通过与固网网关设备的用户面连接传输终端设备的数据；所述核心网设备向所述接入网设备发送所述指示信息，所述接入网设备支持3GPP接入类型。
其中，接入网设备支持3GPP接入类型，也可以描述为，接入网设备支持3GPP接入技术、接入网设备支持蜂窝接入类型、或接入网设备支持蜂窝接入技术等。
在一种实现方式中，设定类型的终端设备可以为固网终端设备。例如，客户端设备、电话、路由器、网络交换机、家庭网关(residential gateway，RG)、机顶盒、固定移动融合产品、家庭网络适配器、以及互联网接入网关等。接入网设备支持3GPP接入类型，也可以替换为，接入网设备支持有线接入技术或者接入网设备支持WIFI接入技术等。需要说明的是，接入网设备支持3GPP接入技术可以是完全支持3GPP协议栈，也可以是支持部分3GPP协议栈，例如只支持物理层、MAC层、RLC层、PDCP层、SDAP层、RRC层中的部分协议栈。
这里的用户面连接可以是IP数据通道、以太数据通道、以及携带VLAN标识的数据传输通道等，本申请不予限制。
在一种实现方式中，所述用户面连接用于为设定类型的终端设备传输用户面数据。
在一种实现方式中，上述核心网设备可以为接入和移动性管理功能网元或会话管理网元。
在上述技术方案中，核心网设备可以获取指示信息并发送给接入网设备，以便接入网设备在获取到指示信息后，可以通过与固网网关设备的用户面连接传输终端设备的数据，这样，终端设备的上行数据可以通过接入网设备发送给固网网关设备，发送给终端设备的下行数据可以由固网网关设备通过接入网设备发送至终端设备，即将终端设备的用户面数据分流至固网网关设备，有助于降低核心网的数据处理和传输压力。
结合第二方面，在一种实现方式中，所述指示信息包括用于指示设定类型的用户面数据的信息。
可以理解为，指示信息用于指示接入网设备通过与固网网关设备的用户面连接来传输设定类型的用户面数据。
结合第二方面或其任意一种实现方式，在另一种实现方式中，所述指示信息包括用于指示所述终端设备为设定类型的终端设备的信息。
可以理解为，指示信息用于指示接入网设备通过与固网网关设备的用户面连接来传输设定类型的终端设备的用户面数据。
结合第二方面或其任意一种实现方式，在另一种实现方式中，所述指示信息包括在以下信息中的一个或多个中：注册接受信息、认证通过信息、会话接受信息、以及会话类型信息。
可以理解为，可以通过注册接受信息、认证通过信息、会话接受信息和会话类型信息中的至少一个指示接入网设备通过与固网网关设备的用户面连接传输终端设备的数据。
也可以理解为，可以通过注册接受信息、认证通过信息、会话接受信息和会话类型信息中的至少一个所包括的部分或全部信息指示接入网设备通过与固网网关设备的用户面连接传输终端设备的数据。
结合第二方面或其任意一种实现方式，在另一种实现方式中，所述指示信息包括以下至少一个：用于指示所述设定类型的用户面数据的信息、用于指示所述终端设备为所述设定类型的终端设备的信息、注册接受信息、认证通过信息、会话接受信息、以及会话类型信息。
结合第二方面或其任意一种实现方式，在另一种实现方式中，所述核心网设备向接入网设备发送指示信息，包括：所述核心网设备在所述终端设备的注册流程中向所述接入网设备发送所述指示信息；或者，所述核心网设备在所述终端设备的会话管理流程中向所述接入网设备发送所述指示信息。其中，会话管理流程可以是会话建立流程、会话修改流程或者会话释放流程。
结合第二方面或其任意一种实现方式，在另一种实现方式中，所述核心网设备获取指示信息，包括：所述核心网设备从统一数据管理功能网元获取所述终端设备的签约数据；所述核心网设备根据所述签约数据，获取所述指示信息。
结合第二方面或其任意一种实现方式，在另一种实现方式中，所述核心网设备获取指示信息，包括：所述核心网设备从策略功能网元获取所述终端设备的策略信息；所述核心网设备根据所述策略信息，获取所述指示信息。
结合第二方面或其任意一种实现方式，在另一种实现方式中，所述核心网设备获取指示信息，包括：所述核心网设备获取所述终端设备的类型信息，所述类型信息指示所述终端设备为所述设定类型的终端设备；所述核心网设备根据所述类型信息，获取所述指示信息。
结合第二方面或其任意一种实现方式，在另一种实现方式中，所述类型信息包含于所述终端设备的签约数据；或者，所述类型信息来自所述终端设备。
结合第二方面或其任意一种实现方式，在另一种实现方式中，所述核心网设备为会话管理网元，所述方法还包括：所述会话管理网元跳过选择用户面功能网元和/或为所述终端设备分配IP地址的流程。
结合第二方面或其任意一种实现方式，在另一种实现方式中，所述核心网设备为会话管理网元，所述方法还包括：所述会话管理网元向所述固网网关设备发送第五消息，所述第五消息用于请求对所述终端设备进行接入管理，所述第五消息包括第五信息，所述第五信息为可通过所述接入管理的认证的信息；所述会话管理网元接收来自所述固网网关设备的第六消息，所述第六消息指示所述终端设备通过所述接入管理的认证。
在一种实现方式中，所述第六消息和所述指示信息还可以包括固网服务器为终端设备分配的IP地址。
在一种实现方式中，所述第六消息和所述指示信息中还可以包括固网网关设备为终端设备分配的会话标识。
结合第二方面或其任意一种实现方式，在另一种实现方式中，所述第五信息是所述会话管理网元从所述统一数据管理功能网元获取的，或者所述第五信息预配置于所述会话管理网元中。
结合第二方面或其任意一种实现方式，在另一种实现方式中，所述第五信息包括可通过所述接入管理的认证的线路标识。
第三方面，本申请提供了一种传输数据的方法，该方法可以由认证、授权和计费(authentication，authorization，accounting，AAA)服务器执行，或者，也可以由AAA服务器中的芯片或电路执行，本申请对此不作限定，为了便于描述，下面以由AAA服务器执行为例进行说明。
所述方法可以包括：AAA服务器接收来自终端设备的用户名和密码；所述AAA服务器根据所述用户名和所述密码，对所述终端设备进行接入管理；若所述用户名对应的通过接入管理的认证的终端设备的数量大于预设阈值，所述AAA服务器拒绝第一数量的终端设备的接入管理，或者使能第一数量的终端设备下线，所述第一数量大于或等于所述预设阈值与所述用户名对应的通过接入管理的认证的终端设备的数量的差值。
在上述技术方案中，AAA服务器可以根据终端设备的用户名和密码对终端设备进行接入管理，并在已经通过该用户名和密码接入的终端设备的数量大于预设阈值，拒绝一定数量的终端设备的接入认证或者使能一定数量的终端设备下线，从而保证通过该用户名和密码接入的终端设备的数量不超过预设阈值。这样可以对终端设备进行有效的接入管理。
结合第三方面，在一种实现方式中，所述方法还包括：所述AAA服务器接收第三信息，所述第三信息用于标识所述终端设备；所述AAA服务器根据所述第三信息，确定所述用户名对应的通过接入管理的认证的终端设备的数量。
在一种实现方式中，所述第三信息包括用于标识所述终端设备的线路标识。
结合第三方面或其任意一种实现方式，在另一种实现方式中，所述第三信息与所述终端设备的标识信息对应。
结合第三方面或其任意一种实现方式，在另一种实现方式中，所述终端设备的标识信息包括以下信息中的一项或多项：地址信息、设备标识、永久标识、临时标识、外部标识或内部标识。
第四方面，本申请提供了一种通信装置，该装置用于执行上述第一方面至第三方面提供的方法。具体地，该装置可以包括用于执行第一方面至第三方面提供的方法的单元和/或模块，如处理单元和/或通信单元。
在一种实现方式中，该装置为接入网设备。当该装置为接入网设备时，所述通信单元可以是收发器，或，输入/输出接口；所述处理单元可以是处理器。
在另一种实现方式中，该装置为用于接入网设备中的芯片、芯片系统或电路。当该装置为用于接入网设备中的芯片、芯片系统或电路时，所述通信单元可以是该芯片、芯片系统或电路上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等；所 述处理单元可以是处理器、处理电路或逻辑电路等。
在一种实现方式中，该装置为核心网设备。当该装置为核心网设备时，所述通信单元可以是收发器，或，输入/输出接口；所述处理单元可以是处理器。
在另一种实现方式中，该装置为用于核心网设备中的芯片、芯片系统或电路。当该装置为用于核心网设备中的芯片、芯片系统或电路时，所述通信单元可以是该芯片、芯片系统或电路上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等；所述处理单元可以是处理器、处理电路或逻辑电路等。
在一种实现方式中，该装置为AAA服务器。当该装置为AAA服务器时，所述通信单元可以是收发器，或，输入/输出接口；所述处理单元可以是处理器。
在另一种实现方式中，该装置为用于AAA服务器中的芯片、芯片系统或电路。当该装置为用于AAA服务器中的芯片、芯片系统或电路时，所述通信单元可以是该芯片、芯片系统或电路上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等；所述处理单元可以是处理器、处理电路或逻辑电路等。
在另一种实现方式中，该装置为终端设备。当该装置为终端设备时，所述通信单元可以是收发器，或，输入/输出接口；所述处理单元可以是处理器。
在另一种实现方式中，该装置为用于终端设备中的芯片、芯片系统或电路。当该装置为用于通信设备中的芯片、芯片系统或电路时，所述通信单元可以是该芯片、芯片系统或电路上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等；所述处理单元可以是处理器、处理电路或逻辑电路等。
一种可能的实现方式，上述收发器可以为收发电路。一种可能的实现方式，上述输入/输出接口可以为输入/输出电路。
第五方面，本申请提供了一种通信装置，该装置包括：存储器，用于存储程序；处理器，用于执行存储器存储的程序，当存储器存储的程序被执行时，处理器用于执行上述第一方面至第三方面提供的方法。
在一种实现方式中，该装置为接入网设备、核心网设备、AAA服务器或终端设备。
在另一种实现方式中，该装置为用于接入网设备、核心网设备、AAA服务器或终端设备中的芯片、芯片系统或电路。
第六方面，本申请提供了一种处理器，用于执行上述各方面提供的方法。在执行这些方法的过程中，上述方法中有关发送上述信息和获取/接收上述信息的过程，可以理解为由处理器输出上述信息的过程，以及处理器接收输入的上述信息的过程。在输出上述信息时，处理器将该上述信息输出给收发器，以便由收发器进行发射。该上述信息在由处理器输出之后，还可能需要进行其他的处理，然后才到达收发器。类似的，处理器接收输入的上述信息时，收发器获取/接收该上述信息，并将其输入处理器。更进一步的，在收发器收到该上述信息之后，该上述信息可能需要进行其他的处理，然后才输入处理器。
基于上述原理，举例来说，前述方法中提及的接收来自固网网关设备的第二消息，可以理解为处理器接收输入的第二消息。
对于处理器所涉及的发射、发送和获取/接收等操作，如果没有特殊说明，或者，如果未与其在相关描述中的实际作用或者内在逻辑相抵触，则均可以更加一般性的理解为处理器输出和接收、输入等操作，而不是直接由射频电路和天线所进行的发射、发送和接收 操作。
在实现过程中，上述处理器可以是专门用于执行这些方法的处理器，也可以是执行存储器中的计算机指令来执行这些方法的处理器，例如通用处理器。上述存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(Read Only Memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
第七方面，本申请提供了一种计算机可读存储介质，该计算机可读介质存储用于设备执行的程序代码，该程序代码包括用于执行上述第一方面至第三方面提供的方法。
第八方面，本申请提供了一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行上述第一方面至第三方面提供的方法。
第九方面，本申请提供了一种芯片，所述芯片包括处理器与通信接口，所述处理器通过所述通信接口读取存储器上存储的指令，执行上述第一方面至第三方面提供的方法。
一种可能的实现方式，作为一种实现方式，所述芯片还可以包括存储器，所述存储器中存储有指令，所述处理器用于执行所述存储器上存储的指令，当所述指令被执行时，所述处理器用于执行上述第一方面至第三方面提供的方法。
第十方面，本申请提供了一种通信系统，包括：接入网设备，用于执行如第一方面或其任意一种实现方式中所述的方法；以及与所述接入网设备进行通信的核心网设备。
附图说明
图1是本申请实施例提供的通信系统100的网络架构示意图。
图2是本申请的控制面协议栈的示意图。
图3是本申请的用户面协议栈的示意图。
图4是本申请的用户面协议栈的另一示意图。
图5是本申请提供的一种传输数据的方法500的示意性流程图。
图6是本申请提供的终端设备的注册流程的示意图。
图7是本申请提供的传输数据的方法的一个示例。
图8是本申请提供的传输数据的方法的另一个示例。
图9是本申请提供的传输数据的方法的另一个示例。
图10是本申请提供的传输数据的方法的另一个示例。
图11是本申请提供的传输数据的方法的另一个示例。
图12是本申请提供的数据传输流程的一个示例。
图13是本申请提供的数据传输流程的另一个示例。
图14是本申请的实施例提供的可能的通信装置的结构示意图。
图15是本申请的实施例提供的可能的通信装置的结构示意图。
具体实施方式
本申请将围绕包括多个设备、组件、模块等的系统来呈现各个方面、实施例或特征。应当理解和明白的是，各个系统可以包括另外的设备、组件、模块等，并且/或者可以并不包括结合附图讨论的所有设备、组件、模块等。此外，还可以使用这些方案的组合。
另外，在本申请实施例中，“示例的”、“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用示例的一词旨在以具体方式呈现概念。
本申请实施例中，“相应的(corresponding，relevant)”和“对应的(corresponding)”有时可以混用，应当指出的是，在不强调其区别时，其所要表达的含义是一致的。
除非另作定义，在本说明书和权利要求书中使用的技术术语或者科学术语应当为本发明所属技术领域内具有一般技能的人士所理解的通常意义。本说明书以及权利要求书中使用的“第一”或者“第二”以及类似的词语并不表示任何顺序、数量或者重要性，而只是用来区分不同的组成部分。在本说明书中描述的参考“一个实施例”或“一些实施例”等意味着在本申请的一个或多个实施例中包括结合该实施例描述的特定特征、结构或特点。由此，在本说明书中的不同之处出现的语句“在一个实施例中”、“在一些实施例中”、“在其他一些实施例中”、“在另外一些实施例中”等不是必然都参考相同的实施例，而是意味着“一个或多个但不是所有的实施例”，除非是以其他方式另外特别强调。术语“包括”、“包含”、“具有”及它们的变形都意味着“包括但不限于”，除非是以其他方式另外特别强调。
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“至少部分”是指部分或者全部。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：包括单独存在A，同时存在A和B，以及单独存在B的情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。
本申请中，“获取”也可以包含“确定”的含义。例如，接入网设备根据指示信息获取第一信息，也可以理解为，接入网设备根据指示信息确定第一信息。又例如，核心网设备获取指示信息，也可以理解为，核心网设备确定指示信息。本申请的“建立连接”可以指“建立用户面连接”，下文对二者不做区分。
为了便于理解，首先对可以应用本申请的技术方案的通信系统的架构进行描述。
图1是本申请实施例提供的通信系统100的网络架构示意图。通信系统100将移动通信系统和固定有线网络结合在一起，能够实现将终端设备的用户面数据分流至固网网关设备。如图1所示，通信系统100包括终端设备、核心网、接入网、固网网关设备、以及数据网络。接入网可以包括至少一个接入网设备。该接入网设备支持3GPP接入类型。终端设备可以通过无线的方式与接入网设备相连，接入网设备通过无线或有线方式与核心网连接，接入网设备通过有线方式与固网网关设备相连。核心网设备与接入网设备可以是独立的不同的物理设备，也可以是将核心网设备的功能与接入网设备的逻辑功能集成在同一个物理设备上，还可以是一个物理设备上集成了部分核心网设备的功能和部分的接入网设备的功能。终端设备和终端设备之间以及接入网设备和接入网设备之间可以通过有线或无线的方式相互连接。图1只是示意图，该通信系统中还可以包括其它网络设备。
具体地，与3GPP网络架构类似，终端设备通过3GPP的接入方式接入网络，并通过接入网设备完成在核心网的注册。与3GPP网络架构不同的是，终端设备的上行数据通过 接入网设备发送给固网网关设备，下行数据则由固网网关设备通过接入网设备发送至终端设备。
通信系统100的数据网络可以包括Internet网络(互联网或因特网)、IP多媒体子系统(IP multimedia subsystem，IMS)网络、IPTV网络、电话网络等网络。数据网络也可以被替换为网络或服务器等，本申请不予限制。
通信系统100的移动通信系统部分可以属于各种移动通信系统，例如：第五代(5th generation，5G)移动通信系统或新无线接入技术(new radio Access Technology，NR)、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)或者其他网络。通信系统100的移动通信系统部分还可以属于未来的移动通信系统，如第六代移动通信系统等。其中，移动通信系统可以包括非独立组网(non-standalone，NSA)和/或独立组网(standalone，SA)。
通信系统100中的接入网设备可以是基站(base station)、演进型基站(evolved NodeB，eNodeB)、发送接收点(transmission reception point，TRP)、5G移动通信系统中的下一代基站(next generation NodeB，gNB)、第六代(6th generation，6G)移动通信系统中的下一代基站、或未来移动通信系统中的基站等；也可以是完成基站部分功能的模块或单元，例如，可以是集中式单元(central unit，CU)、分布式单元(distributed unit，DU)、RRU或基带单元(baseband unit，BBU)等。接入网设备可以是宏基站，也可以是微基站或室内站，还可以是中继节点或施主节点等。在本申请中，接入网设备支持3GPP接入类型。本申请的实施例对接入网设备所采用的具体技术和具体设备形态不做限定。
通信系统100中的终端设备也可以称为终端、用户设备(user equipment，UE)、移动台、移动终端设备等。终端设备可以广泛应用于各种场景，例如，虚拟现实、增强现实、工业控制、远程医疗、智能电网、智能家具、智能办公、智能穿戴、智能交通、智慧城市等。终端设备可以是手机、平板电脑、带无线收发功能的电脑、机器人、机械臂、智能家居设备等。终端设备还可以是客户端设备(customer-premises equipment，CPE)、电话、路由器、网络交换机、家庭网关(residential gateway，RG)、机顶盒、固定移动融合产品、家庭网络适配器、以及互联网接入网关等。这里的CPE或RG可以是一种接收移动信号并以无线WiFi信号转发出来的移动信号接入设备，同时也可以是一种将高速第四代(4th generation，4G)或者5G信号转换成WiFi信号的设备，即CPE或RG可以既支持有线接入，也支持无线接入(例如，通过3GPP接入移动网络)。CPE或RG还可以支持通过蜂窝空口接收数据并通过蜂窝空口转发数据。CPE或RG可支持同时上网的移动终端设备数量也较多。CPE或RG可大量应用于农村、城镇、医院、单位、工厂、小区等无线网络接入，能节省铺设有线网络的费用。CPE或RG可以提供移动运营商通信网和用户端Wi-Fi局域网之间的对接服务。本申请的实施例对终端设备所采用的具体技术和具体设备形态不做限定。
接入网设备和终端设备可以是固定位置的，也可以是可移动的。接入网设备和终端设备可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上。本申请的实施例对接入网设备和终端设备的应用场景不做限定。接入网设备和终端设备的角色可以是相对的。接入网设备和终端设备之间、接入网设备和接入网设备之间、终端设备和终端设 备之间可以通过授权频谱进行通信，也可以通过免授权频谱进行通信，也可以同时通过授权频谱和免授权频谱进行通信；可以通过6千兆赫(gigahertz，GHz)以下的频谱进行通信，也可以通过6GHz以上的频谱进行通信，还可以同时使用6GHz以下的频谱和6GHz以上的频谱进行通信。本申请的实施例对无线通信所使用的频谱资源不做限定。
通信系统100中的固网网关设备是互联网协议(internet protocol，IP)边缘节点，可以为宽带网络网关(broadband network gateway，BNG)、宽带远程接入服务器(broadband remote access server，BRAS)、或业务路由器(service router，SR)等。BRAS和SR可以是BNG的细分形式，可以理解为狭义的BNG。BRAS作为传统的互联网业务的入口，而SR作为新的精品业务的入口。SR与BRAS类似，用来终结和管理用户的以太网承载点对点协议(point-to-point protocol over Ethernet，PPPoE)/以太网承载IP协议(Internet protocol over Ethernet，IPoE)会话。固网网关设备可以称为非移动网络网关或非移动网关设备等。
通信系统100中的核心网可以包括一个或多个核心网设备，如图1中的接入和移动性管理功能(access and mobility management function，AMF)、统一数据管理(unified data management，UDM)和认证服务器功能(authentication server function，AUSF)网元，核心网还可以包括更多或更少的网元，例如核心网还可以包括会话管理网元(session management function，SMF)网元(图1中未示出)等。AMF网元属于核心网控制面网元，主要负责用户的移动性管理，包括移动状态管理、分配用户临时身份标识、认证和授权用户、为会话提供控制面的存储资源等。UDM网元属于核心网控制面网元，归属用户服务器，主要负责管理签约数据。AUSF网元属于核心网控制面网元，主要负责对用户的鉴权、授权以保证用户是合法用户。SMF网元属于核心网控制面网元，主要用于会话管理、UE的IP地址分配和管理、选择可管理用户平面功能、策略控制、或收费功能接口的终结点以及下行数据通知等。上述核心网网元也可称为核心网设备。
应理解，上述通信系统仅是示例性说明，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。在图1所示的网络结构下，对本申请的控制面协议栈和用户面协议栈进行描述。
图2是本申请的控制面协议栈的示意图。从图2可以看出，对于控制面而言，终端设备通过RRC消息与接入网设备通信，终端设备通过非接入层(non-access stratum，NAS)消息与AMF通信。
图3是本申请的用户面协议栈的示意图。对于用户面而言，终端设备可以通过PPPoE或IPoE协议与固网网关设备通信。在本申请中，终端设备与固网网关设备之间的消息是通过支持3GPP接入类型的接入网设备转发的。终端设备与接入网设备之间的消息是通过3GPP蜂窝空口传输的，接入网设备与固网网关设备之间以有线的方式进行数据传输。对于终端设备而言，终端设备可以将发送给固网网关设备的消息承载于空口发送至接入网设备，再由接入网设备转发给固网网关设备。对于接入网设备而言，接入网设备可以根据终端设备的类型，确定将数据向固网网关设备转发还是向移动网络网关设备转发。
图4是本申请的用户面协议栈的另一示意图。与图3不同的是，接入网设备具有IPoE或PPPoE协议栈。当接入网设备具有IPoE或PPPoE协议栈时，接入网设备可以作为固定网络中的终端设备，直接与固网网关设备建立连接。接入网设备与固网网关设备之间的连接可以为多个通过该接入网设备传输数据的终端设备所共享的连接，在此情况下，接入网 设备可以通过做网络地址转换，使得多个终端设备与接入网设备的连接能够映射到接入网设备与固网网关设备之间建立的一个或多个的连接。
需要说明的是，本申请中的网元的命名仅是一个名字，名字对网元本身的功能不构成限定。在不同的网络中，上述各个网元也可以是其他的名字，本申请实施例对此不作具体限定。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能是其他命名，等等，在此进行统一说明，以下不再赘述。本申请中的网元可以是硬件，也可以是从功能上划分的软件或者以上二者的结合。本申请中的网元之间可以通过其他设备或网元通信。
下面结合附图对本申请提供的传输数据的方法进行描述。
图5是本申请提供的一种传输数据的方法500的示意性流程图。方法500可以由终端设备、接入网设备、核心网设备和固网网关设备来执行，也可以由终端设备、接入网设备、核心网设备和固网网关设备中的模块或单元(例如，电路、芯片或片上系统(system on chip，SOC)等)来执行。下面以执行主体为终端设备、接入网设备、核心网设备和固网网关设备为例对本申请的技术方案进行描述。方法500可以包括以下内容的至少部分内容。
步骤501，核心网设备获取指示信息。
其中，该指示信息用于接入网设备通过与固网网关设备的用户面连接传输终端设备的数据。
在一种实现方式中，用户面连接可以是互联网协议(internet protocol，IP)数据通道、以太数据通道、以及携带虚拟局域网(virtual local area network，VLAN)标识的数据传输通道等，本申请不予限制。在本申请中，该用户面连接用于为设定类型的终端设备传输用户面数据。
在一些实现方式中，指示信息可以包括用于指示设定类型的用户面数据的信息和/或用于指示终端设备为设定类型的终端设备的信息。在一些实现方式中，指示信息可以包括在以下信息中的一个或多个中：注册接受信息(例如，registration accept)、认证通过信息(例如，通过authentication indication指示)、会话接受信息(例如，PDU session accept)、以及会话类型信息。或者，也可以描述为指示信息可以包括以下信息中的至少一个：用于指示设定类型的用户面数据的信息、用于指示终端设备为设定类型的终端设备的信息、注册接受信息、认证通过信息、会话接受信息、以及会话类型信息。或者，也可以描述为指示信息可以为以下信息中的至少一个所包括的部分或全部信息：用于指示设定类型的用户面数据的信息、用于指示终端设备为设定类型的终端设备的信息、注册接受信息、认证通过信息、会话接受信息、以及会话类型信息。
其中，用于指示设定类型的用户面数据的信息可以是以下信息中的一项或多项：地址信息、端口信息、协议信息、以及第一业务信息，可以理解为，设定类型的用户面数据为使用该地址信息指示的地址的用户面数据、通过该端口信息指示的端口传输的用户面数据、使用该协议信息指示的协议传输的用户面数据、该第一业务信息指示的业务的用户面数据。其中，地址信息可以包括以下信息中的一项或多项：源IP地址、目的IP地址、源MAC地址、和目的MAC地址。端口信息可以包括以下信息中的一项或多项：源端口号和目的端口号。协议信息可以包括以下信息中的一项或多项：协议类型、协议名称、和协议版本号。第一业务信息可以包括以下信息中的一项或多项：业务标识、应用标识、和业务类型 信息。
会话类型信息用于指示会话为设定类型的终端设备的会话或用于传输设定类型的终端设备的用户面数据的会话，例如用于传输家庭网关数据的会话或用于传输固网业务的会话等。
设定类型的终端设备可以为固网终端设备。例如，电话、路由器、网络交换机、家庭网关、机顶盒、固定移动融合产品、家庭网络适配器、以及互联网接入网关等。设定类型的终端设备还可以是手机、AR终端、VR终端、平板电脑以及其他类型终端。设定类型的终端设备还可以是通过固网网关设备传输数据的终端设备，本申请不予限制。
当指示信息包括用于指示设定类型的用户面数据的信息时，可以理解为，指示信息用于指示接入网设备通过与固网网关设备的用户面连接来传输设定类型的用户面数据。
当指示信息包括用于指示终端设备为设定类型的终端设备的信息时，可以理解为，指示信息用于指示接入网设备通过与固网网关设备的用户面连接来传输设定类型的终端设备的用户面数据。
当指示信息包括注册接受信息、认证通过信息、会话接受信息以及会话类型信息中的至少一个时，可以理解为，核心网设备通过注册接受信息、认证通过信息、会话接受信息和会话类型信息中的至少一个指示接入网设备通过与固网网关设备的用户面连接传输终端设备的数据。或者，还可以理解为，核心网设备在终端设备注册成功、认证成功、或会话建立成功时，获取指示信息。
在一些实现方式中，核心网设备可以通过注册接受信息、认证通过信息、和会话接受信息中的至少一个隐式指示接入网设备通过与固网网关设备的用户面连接传输终端设备的数据。作为一个示例，在接入网设备提前获取了用于指示设定类型的用户面数据的信息或用于指示终端设备为设定类型的终端设备的信息的情况下，当接入网设备接收到来自核心网设备的注册接受信息、认证通过信息、会话接受信息和会话类型信息，接入网设备则可以确定需要通过与固网网关设备的用户面连接来传输设定类型的终端设备的用户面数据或设定类型的用户面数据，即核心网设备通过注册接受信息、认证通过信息、和会话接受信息中的至少一个隐式指示接入网设备通过与固网网关设备的用户面连接传输终端设备的数据。其中，接入网设备可以从终端设备获取用于指示设定类型的用户面数据的信息或用于指示终端设备为设定类型的终端设备的信息，例如，终端设备可以通过注册请求消息、会话建立请求消息、会话修改请求消息等向接入网设备发送上述信息。
在另一些实现方式中，核心网设备可以结合注册接受信息、认证通过信息、和会话接受信息中的至少一个、以及用于指示设定类型的用户面数据的信息和用于指示终端设备为设定类型的终端设备的信息中的至少一个，指示接入网设备通过与固网网关设备的用户面连接来传输设定类型的终端设备的用户面数据或设定类型的用户面数据。
在本申请中，核心网设备获取指示信息的方式有很多，本申请不作具体限定，下面对其中的几种方式进行描述。
方式1
核心网设备可以根据终端设备的签约数据，获取指示信息。一种可能的实现方式为核心网设备根据终端设备的签约数据中的终端设备的类型信息和/或第二业务信息，获取指示信息。其中，类型信息用于指示终端设备的类型，第二业务信息用于指示终端设备是否 开通了固网业务(或者指示终端设备是否有权限获取固网业务，或者指示终端设备的业务数据流是否需要分流至固网网关设备)。这里的固网业务可以包括家庭宽带业务等。
一种可能的实现方式中，第二业务信息包括了特定的业务流信息。该业务流信息可以是以下信息中的一项或多项：地址信息、端口信息、协议信息、以及第一业务信息，其中地址信息、端口信息、协议信息、和第一业务信息的描述可以参考上文，在此不再赘述。
一种可能的实现方式，核心网设备根据第二业务信息中的特定的业务流信息，确定指示信息中的用于指示设定类型的用户面数据的信息。
在一些实现方式中，核心网设备可以在终端设备的注册流程中获取终端的签约数据并获取指示信息。
例如，以核心网设备为AMF为例，当终端设备与网络侧完成鉴权等安全流程后，AMF可以与UDM交互以获取终端设备的签约数据。进一步地，AMF可以根据签约数据中包括的终端设备的类型信息以及第二业务信息，确定终端设备的类型、以及终端设备是否开通了固网业务(或者终端设备是否有权限获取固网业务，或者终端设备的业务数据是否需要分流至固网网关设备)。若确定终端设备为设定类型的终端设备和/或终端设备开通了固网业务(或者终端设备有权限获取固网业务，或者终端设备的业务数据流需分流至固网网关设备)，AMF获取指示信息，指示信息可以包括注册接受信息或认证通过信息。
又例如，以核心网设备为AMF为例，当终端设备与网络侧完成鉴权等安全流程后，AMF可以与UDM交互以获取终端设备的签约数据。进一步地，AMF可以根据签约数据中包括的终端设备的类型信息，确定终端设备的类型。若终端设备为设定类型的终端设备，AMF获取指示信息，指示信息可以包括注册接受信息或认证通过信息。
又例如，以核心网设备为AMF为例，当终端设备与网络侧完成鉴权等安全流程后，AMF可以与UDM交互以获取终端设备的签约数据。进一步地，AMF可以根据签约数据中包括的第二业务信息，确定终端设备是否开通了固网业务(或者终端设备是否有权限获取固网业务，或者终端设备的业务数据是否需要分流至固网网关设备)。若终端设备开通了固网业务(或者终端设备有权限获取固网业务，或者终端设备的业务数据流需分流至固网网关设备)，AMF获取指示信息，指示信息可以包括注册接受信息或认证通过信息。
需要说明的是，若AMF确定终端设备不是设定类型的终端设备和/或终端设备未开通固网业务(或者没有有权限获取固网业务，或者终端设备的业务数据流无需分流至固网网关设备)，AMF可以向接入网设备反馈注册拒绝信息(例如，registration reject)或认证失败信息，或者，AMF可以不获取指示信息，并在终端设备通过安全鉴权流程后，通过接入网设备向终端设备发送注册接受信息或认证成功信息。
在另一些实现方式中，核心网设备可以在终端设备的会话管理流程中获取终端设备的签约数据并获取指示信息。其中，会话管理流程可以是会话建立流程、会话修改流程或者会话释放流程。
例如，以核心网设备为SMF为例，SMF可以与UDM交互获取终端设备的签约数据。进一步地，SMF可以根据签约数据中的终端设备的类型信息以及第二业务信息，确定终端设备的类型、以及终端设备是否开通了固网业务(或者终端设备是否有权限获取固网业务，或者终端设备的业务数据是否需要分流至固网网关设备)。若确定终端设备为设定类型的终端设备和/或终端设备开通了固网业务(或者终端设备有权限获取固网业务，或者 终端设备的业务数据流需分流至固网网关设备)，SMF获取指示信息，指示信息可以包括会话接受信息或认证通过信息。
又例如，以核心网设备为SMF为例，SMF与UDM交互获取终端设备的签约数据。进一步地，SMF可以根据签约数据中的终端设备的类型信息，确定终端设备的类型。若确定终端设备为设定类型的终端设备，SMF获取指示信息，指示信息可以包括会话接受信息或认证通过信息。
又例如，例如，以核心网设备为SMF为例，SMF与UDM交互获取终端设备的签约数据。进一步地，SMF可以根据签约数据中的第二业务信息，确定终端设备是否开通了固网业务(或者终端设备是否有权限获取固网业务，或者终端设备的业务数据是否需要分流至固网网关设备)。若终端设备开通了固网业务(或者终端设备有权限获取固网业务，或者终端设备的业务数据流需分流至固网网关设备)，SMF获取指示信息，指示信息可以包括会话接受信息或认证通过信息。
上述固网业务可以是家庭宽带业务等。
在一些实现方式中，SMF在确定终端设备为设定类型的终端设备和/或终端设备开通了固网业务(或者终端设备有权限获取固网业务，或者终端设备的业务数据流需分流至固网网关设备)的情况下，SMF还可以代替终端设备与固网网关设备交互以完成终端设备的认证、终端设备的IP地址的获取和/或会话标识的获取。
需要说明的是，由于SMF确定终端设备为设定类型的终端设备和/或终端设备开通了固网业务(或者终端设备有权限获取固网业务，或者终端设备的业务数据流需分流至固网网关设备)，终端设备的用户面数据将会被分流至固网网关设备，因此SMF无需(或者说跳过)选择用户面功能网元和/或为终端设备分配IP地址。
还需要说明的是，若SMF确定终端设备不是设定类型的终端设备和/或终端设备未开通固网业务(或者没有权限获取固网业务，或者该终端设备的业务数据流无需分流至固网网关设备)，SMF可以向接入网设备反馈会话拒绝信息(例如，PDU session reject)或认证失败信息，或者，SMF可以在终端设备完成会话建立流程中的二次鉴权后，通过接入网设备向终端设备发送会话接受信息或认证通过信息。此时，SMF无需获取指示信息。
方式2
核心网设备可以根据终端设备的类型信息确定指示信息。这里的终端设备的类型信息可以来自终端设备，例如，终端设备可以在接入层(access stratum，AS)或非接入层(non-access stratum，NAS)消息中包括终端设备的类型信息。一种可能的实现方式，终端设备可以在无线资源控制(radio resource control，RRC)消息、注册请求消息或会话建立请求消息中包括该类型信息。
方式3
核心网设备可以根据终端设备的策略信息确定指示信息。这里的策略信息可以来自策略功能网元，例如策略控制功能(policy control function，PCF)。
步骤502，接入网设备获取指示信息。
本申请的接入网设备为无线接入网设备，或者说，接入网设备支持3GPP接入类型。接入网设备支持3GPP接入类型，也可以描述为，接入网设备支持3GPP接入技术、接入网设备支持蜂窝接入类型、或接入网设备支持蜂窝接入技术等。接入网设备支持3GPP接 入类型，也可以替换为，接入网设备支持有线接入技术或者接入网设备支持WIFI接入技术等。需要说明的是，接入网设备支持3GPP接入技术可以是完全支持3GPP协议栈，也可以是支持部分3GPP协议栈，例如只支持物理层、MAC层、RLC层、PDCP层、SDAP层、RRC层中的部分协议栈。
接入网设备获取指示信息的方式有很多，本申请不予限制。在一些实现方式中，如图5所示，接入网设备可以从核心网设备获取指示信息。具体地，核心网设备在获取指示信息后，可以向接入网设备发送指示信息，相应地，接入网设备接收来自核心网设备的指示信息。指示信息的描述可以参见上文，在此不再赘述。
接入网设备从核心网设备获取指示信息的方式有很多，本申请不予限制，下面对其中的几种方式进行描述。
方式1
接入网设备可以在终端设备的注册流程中从核心网设备获取指示信息。
以核心网设备为AMF为例，接入网设备可以接收AMF发送的N2消息，N2消息可以包括发送给接入网设备的指示信息。其中，指示信息可以包括以下至少一个：用于指示设定类型的用户面数据的信息、用于指示终端设备为设定类型的终端设备的信息、注册接受信息、以及认证通过信息，各信息更详细描述可以参考上文，在此不再赘述。
在一种实现方式中，N2消息还包括发送给终端设备的NAS消息，该NAS消息中可以包括AMF向终端设备发送的注册接受信息或认证通过信息。
需要说明的是，若AMF确定终端设备不是设定类型的终端设备和/或终端设备未开通固网业务(或者没有权限获取固网业务，或者该终端设备的业务数据流无需分流至固网网关设备)，AMF可以向接入网设备反馈注册拒绝信息(例如，registration reject)或认证失败信息，相应地，接入网设备接收到的为注册拒绝信息或认证失败信息。
方式2
接入网设备可以在终端设备的会话建立流程中从核心网设备获取指示信息。
以核心网设备为SMF为例，接入网设备可以接收SMF通过AMF发送的N1N2消息，其中，N1N2消息传递消息可以携带会话标识、N1会话信息、以及N2会话信息。N1会话信息是SMF通过AMF向终端设备发送的，N1会话信息中可以包括会话接受信息或认证通过信息。N2会话信息是SMF通过AMF向接入网设备发送的，N2会话信息中可以包括指示信息。其中，指示信息可以包括以下至少一个：用于指示设定类型的用户面数据的信息、用于指示终端设备为设定类型的终端设备的信息、认证通过信息、会话接受信息、以及会话类型信息，各信息更的详细描述可以参考上文，在此不再赘述。
在一种实现方式中，N2会话信息还包括发送给终端设备的NAS消息，该NAS消息中可以包括AMF向终端设备发送的注册接受信息或认证通过信息。
在一种实现方式中，在方式2的基础上，若SMF代替终端设备与固网网关设备交互以完成终端设备的认证和终端设备的IP地址的获取，N1会话信息中还可以包括固网网关设备为终端设备分配的IP地址和/或会话标识。
需要说明的是，若SMF确定终端设备不是设定类型的终端设备和/或终端设备未开通固网业务(或者没有权限获取固网业务，或者该终端设备的业务数据流无需分流至固网网关设备)，SMF可以向接入网设备反馈注册拒绝信息或认证失败信息，相应地，接入网 设备接收到的为注册拒绝信息或认证失败信息。
在一种实现方式中，若接入网设备接收到的N1会话信息或接收到包括NAS消息的N2消息，方法500中还包括：接入网设备向终端设备转发所述N1会话信息或NAS消息。
步骤503，接入网设备根据指示信息通过与固网网关设备的用户面连接传输终端设备的数据。
接入网设备在接收到指示信息后，可以获知需要将终端设备的至少部分用户面数据分流至固网网关设备。
当指示信息包括用于指示设定类型的用户面数据的信息时，接入网设备可以根据指示信息通过与固网网关设备的用户面连接传输设定类型的用户面数据。
当指示信息包括用于指示终端设备为设定类型的终端设备的信息时，接入网设备可以通过与固网网关设备的用户面连接传输设定类型的终端设备的用户面数据。
当指示信息包括注册接受信息、认证通过信息、会话接受信息以及会话类型信息中的至少一个时，若接入网设备提前获取了用于指示设定类型的用户面数据的信息或用于指示终端设备为设定类型的终端设备的信息，则接入网设备在接收到来自核心网设备的注册接受信息、认证通过信息、会话接受信息和会话类型信息后，可以需要通过与固网网关设备的用户面连接传输设定类型的终端设备的用户面数据或设定类型的用户面数据。其中，接入网设备可以从终端设备获取用于指示设定类型的用户面数据的信息或用于指示终端设备为设定类型的终端设备的信息，例如，终端设备可以通过注册请求消息、会话建立请求消息、会话修改请求消息等向接入网设备发送上述信息。
当指示信息包括注册接受信息、认证通过信息、和会话接受信息中的至少一个、以及用于指示设定类型的用户面数据的信息和用于指示终端设备为设定类型的终端设备的信息中的至少一个时，接入网设备可以通过与固网网关设备的用户面连接来传输设定类型的终端设备的用户面数据或设定类型的用户面数据。其中，接入网设备可以根据用于指示设定类型的用户面数据的信息和/或用于指示终端设备为设定类型的终端设备的信息，确定终端设备为设定类型的终端设备和/或设定类型的用户面数据。
由于注册接受信息、认证通过信息、和会话接受信息属于NAS层信息，接入网设备并不主动获取这些信息。在一种可能的实现方式中，当接入网设备发现这些NAS信息是发送给自己的后，可以通过默认配置的方式确定需要通过与固网网关设备的用户面连接传输终端设备的数据。
另一种可能的实现方式，除了NAS层信息包括注册接受信息、认证通过信息、和会话接受信息，N2消息中还可以包括注册接受信息、认证通过信息、和会话接受信息，从而接入网设备可以通过N2消息获取注册接受信息、认证通过信息、和会话接受信息。
在一些实现方式中，若接入网设备与固网网关设备尚未建立用户面连接，在接收到指示信息后，接入网设备可以根据指示信息建立与固网网关设备的用户面连接。
对终端设备进行接入管理的方式有很多，本申请不予限制，下面对其中的几种方式进行描述。可以理解的，对终端设备进行接入管理可以在接入网设备与固网网关设备建立用户面连接之前进行，也可以在接入设备与固网网关建立用户面连接时进行，也可以在接入设备与固网网关建立用户面连接之后进行。
方式1
终端设备向接入网设备发送第一消息，第一消息用于请求对终端设备进行接入管理。在接收到第一消息后，接入网设备根据指示信息，获取第一信息，第一信息为可通过接入管理的认证的信息。接入网设备向固网网关设备发送第一信息。在接收到第一信息后，固网网关设备通过固网服务器向AAA服务器发送第一信息。在接收到第一信息后，AAA服务器根据第一信息对终端设备进行接入管理的认证，由于第一信息为可通过接入管理的认证信息，因此AAA服务器会通过终端设备的接入管理认证，AAA服务器通过固网服务器向固网网关设备反馈终端设备通过接入管理的认证。固网网关设备接收来自固网服务器的第二消息，并向接入网设备发送第二消息，第二消息指示终端设备通过接入管理的认证，第二消息可以包括固网服务器为终端设备分配的IP地址。进一步地，接入网设备可以向终端设备反馈终端设备通过接入管理的认证以及IP地址。这里的接入网设备根据指示信息获取第一信息，也可以理解为，接入网设备根据指示信息确定第一信息。
在一种实现方式中，终端设备的IP地址也可以是固网网关设备分配的。
在一种实现方式中，上述接入管理可以包括对是否开通固网业务(或者是否有权获取固网业务)进行认证。
在一种实现方式中，第一信息可以为预配置于接入网设备中，或者来自终端设备，或者来自核心网设备。在一种实现方式中，第一信息可以为可接入的线路标识(line ID)。
在一种实现方式中，若终端设备采用IPoE协议，第一消息可以为DHCP发现消息或DHCP请求消息等，第二消息可以为DHCP提供消息(DHCP offer)或DHCP确认消息(DHCP ACK)等，固网服务器可以为DHCP服务器。
在一种实现方式中，若终端设备采用PPPoE协议，第一消息可以为PADI、PADR或链路配置请求(link configure request，LCP)协商过程中的消息，第二消息可以为PADO、PADS或LCP协商过程中的消息，固网服务器可以为PPPoE服务器；此时，PPPoE服务器功能可以集成于固网网关设备中。一种可能的实现方式，固网网关设备集成了固网服务器功能，为终端设备分配IP地址。可选的，终端设备通过IP控制协议(IP Control Protocol，IPCP)获取IP地址。并且，若终端设备采用PPPoE协议，固网网关设备还可以为终端设备分配PPPoE会话标识。
在一种实现方式中，接入网设备还可以与终端设备建立接入网资源。本申请不限定接入网设备与终端设备建立接入网资源的时机。例如，在接收到指示信息后，接入网设备可以与终端设备建立接入网资源。又例如，在接收到第二消息并且第二消息指示终端设备通过接入管理认证的情况下，接入网设备可以与终端设备建立接入网资源。例如，在接收到第一消息后，接入网设备可以与终端设备建立接入网资源。
需要说明的是，假设在接入网设备在接收到来自核心网设备的反馈之前已经与终端设备建立了接入网资源，若接入网设备接收到的是注册拒绝信息、认证失败信息、会话拒绝信息、或第二消息指示终端设备未通过接入管理的认证，则接入网设备可以释放与终端设备的接入网资源。
方式2
终端设备向接入网设备发送第一消息，第一消息用于请求对终端设备进行接入管理，且第一消息包括第二信息，第二信息为用于进行接入管理的认证的信息。在接收到第一消息后，接入网设备根据第一消息中的第二信息，获取第三信息，第三信息用于标识终端设 备。接入网设备向固网网关设备发送第二信息和第三信息。在接收到第二信息和第三信息后，固网网关设备通过固网服务器向AAA服务器发送第二信息和第三信息。在接收到第二信息和第三信息后，AAA服务器根据第二信息和第三信息对终端设备进行接入管理的认证，若通过认证，则AAA服务器通过固网服务器向固网网关设备反馈终端设备通过接入管理的认证。固网网关设备接收来自固网服务器的第二消息，并向接入网设备发送第二消息，第二消息指示终端设备通过接入管理的认证，第二消息可以包括固网服务器为终端设备分配的IP地址。进一步地，接入网设备可以向终端设备反馈终端设备通过接入管理的认证以及IP地址。这里的接入网设备根据第一消息中的第二信息获取第三信息，也可以理解为，接入网设备根据第一消息中的第二信息确定第三信息。
在一种实现方式中，终端设备的IP地址也可以是固网网关设备分配的。
在一种实现方式中，上述接入管理可以包括对是否开通固网业务(或者是否有权获取固网业务)进行认证。
在一种实现方式中，第二信息包括终端设备对应的用户名、密码、以及终端设备的标识中的至少一个。接入网设备可以根据第二信息中的终端设备的标识，获取第三信息。在一种实现方式中，第三信息与终端设备的标识信息对应，例如，第三信息可以为用于表示终端设备的线路标识。其中，终端设备的标识可以包括以下至少一项：地址信息(例如MAC地址)、设备标识、永久标识(例如订阅永久标识(subscription permanent identifier，SUPI))、临时标识(例如5G全球唯一临时标识(5G-globally unique temporary identity，5G-GUTI)、5G短临时移动订阅标识(5G S-Temporary Mobile Subscription Identifier，5G-S-TMSI))、外部标识(例如手机号码、一般公共订阅标识generic public subscription identifier，GPSI)或内部标识(例如SUPI、订阅隐藏标识(subscription concealed identifier，SUCI)、5G-GUTI、5G-S-TMSI、内部GPSI等)。第三信息可以预配置于接入网设备中或者来自核心网设备。
在一种实现方式中，以第二信息包括终端设备对应的用户名和密码为例，AAA服务器可以按照以下方式对对终端设备进行接入管理。具体地，若第二信息携带的用户名对应的通过接入管理的认证的终端设备的数量大于预设阈值，则AAA服务器拒绝第一数量的终端设备的接入管理，或者使能第一数量的终端设备下线，其中第一数量大于或等于预设阈值与该用户名对应的通过接入管理的认证的终端设备的数量的差值。其中，AAA服务器可以根据接收到的第四信息，确定第二信息携带的用户名对应的通过接入管理的认证的终端设备的数量。
在一种实现方式中，若终端设备采用IPoE协议，第一消息可以为DHCP发现消息或DHCP请求消息等，第二消息可以为DHCP提供消息或DHCP确认消息等，固网服务器可以为DHCP服务器。
在一种实现方式中，若终端设备采用PPPoE协议，第一消息可以为PADI、PADR或LCP协商过程中的消息，第二消息可以为PADO、PADS或LCP协商过程中的消息，固网服务器可以为PPPoE服务器；此时，PPPoE服务器功能可以集成于固网网关设备中。一种可能的实现方式，固网网关设备集成了固网服务器功能，为终端设备分配IP地址。可选的，终端设备通过IPCP获取IP地址。并且，若终端设备采用PPPoE协议，固网网关设备还可以为终端设备分配PPPoE会话标识。
在一种实现方式中，接入网设备还可以与终端设备建立接入网资源。本申请不限定接入网设备与终端设备建立接入网资源的时机。例如，在接收到指示信息后，接入网设备可以与终端设备建立接入网资源。又例如，在接收到第二消息并且第二消息指示终端设备通过接入管理认证的情况下，接入网设备可以与终端设备建立接入网资源。例如，在接收到第一消息后，接入网设备可以与终端设备建立接入网资源。
需要说明的是，假设在接入网设备在接收到来自核心网设备的反馈之前已经与终端设备建立了接入网资源，若接入网设备接收到的是注册拒绝信息、认证失败信息、会话拒绝信息、或第二消息指示终端设备未通过接入管理的认证，则接入网设备可以释放与终端设备的接入网资源。
方式3
与方式2不同的是，在方式3中，接入网设备可以不获取第三信息。
具体地，终端设备向接入网设备发送第一消息，第一消息用于请求对终端设备进行接入管理，且第一消息包括第二信息，第二信息为用于进行接入管理的认证的信息。在接收到第一消息后，接入网设备向固网网关设备发送第二信息。在接收到第二信息后，固网网关设备通过固网服务器向AAA服务器发送第二信息。在接收到第二信息后，AAA服务器根据第二信息对终端设备进行接入管理的认证，若通过认证，则AAA服务器通过固网服务器向固网网关设备反馈终端设备通过接入管理的认证。固网网关设备接收来自固网服务器的第二消息，并向接入网设备发送第二消息，第二消息指示终端设备通过接入管理的认证，第二消息可以包括固网服务器为终端设备分配的IP地址。进一步地，接入网设备可以向终端设备反馈终端设备通过接入管理的认证以及IP地址。
在一种实现方式中，终端设备的IP地址也可以是固网网关设备分配的。
在一种实现方式中，第二信息包括终端设备对应的用户名、密码、以及终端设备的标识中的至少一个。
在一种实现方式中，上述接入管理可以包括对是否开通固网业务(或者是否有权获取固网业务)进行认证。
在一种实现方式中，若终端设备采用IPoE协议，第一消息可以为DHCP发现消息或DHCP请求消息等，第二消息可以为DHCP提供消息或DHCP确认消息等，固网服务器可以为DHCP服务器。
在一种实现方式中，若终端设备采用PPPoE协议，第一消息可以为PADI、PADR或LCP协商过程中的消息，第二消息可以为PADO、PADS或LCP协商过程中的消息，固网服务器可以为PPPoE服务器；此时，PPPoE服务器功能可以集成于固网网关设备中。一种可能的实现方式，固网网关设备集成了固网服务器功能，为终端设备分配IP地址。可选的，终端设备通过IPCP获取IP地址。并且，若终端设备采用PPPoE协议，固网网关设备还可以为终端设备分配PPPoE会话标识。
在一种实现方式中，接入网设备还可以与终端设备建立接入网资源。本申请不限定接入网设备与终端设备建立接入网资源的时机。例如，在接收到指示信息后，接入网设备可以与终端设备建立接入网资源。又例如，在接收到第二消息并且第二消息指示终端设备通过接入管理认证的情况下，接入网设备可以与终端设备建立接入网资源。例如，在接收到第一消息后，接入网设备可以与终端设备建立接入网资源。
需要说明的是，假设在接入网设备在接收到来自核心网设备的反馈之前已经与终端设备建立了接入网资源，若接入网设备接收到的是注册拒绝信息、认证失败信息、会话拒绝信息、或第二消息指示终端设备未通过接入管理的认证，则接入网设备可以释放与终端设备的接入网资源。
方式4
在接收到指示信息后，接入网设备可以向固网网关设备发送第三消息，第三消息用于请求对接入网设备进行接入管理，且第三消息可以包括第四信息，第四信息为可通过接入管理的认证的信息。在接收到第三消息后，固网网关设备通过固网服务器向AAA服务器发送第四信息。在接收到第四信息后，AAA服务器根据第四信息对接入网设备进行接入管理的认证，由于第四信息为可通过接入管理的认证信息，因此AAA服务器会通过接入网设备的接入管理认证，AAA服务器通过固网服务器向固网网关设备反馈接入网设备通过接入管理的认证。固网网关设备接收来自固网服务器的第四消息，并向接入网设备发送第四消息，第四消息指示接入网设备通过接入管理的认证，且第四消息包括固网服务器为接入网设备分配的第一IP地址。进一步地，接入网设备可以为为终端设备分配第二IP地址，第二IP地址对应于第一IP地址。这样，若后续接收到来自终端设备的用户面数据，接入网设备可以将用户面数据中的第二IP地址替换为第一IP地址，并发送给固网网关设备。
在一种实现方式中，上述接入管理可以包括对是否开通固网业务(或者是否有权限获取固网业务)进行认证。
在一种实现方式中，第一IP地址也可以是固网网关设备分配的。
在一种实现方式中，第四信息可以为预配置于接入网设备中，或者来自终端设备，或者来自核心网设备。在一种实现方式中，第四信息可以为可接入的线路标识。
在一种实现方式中，若终端设备采用IPoE协议，第三消息可以为DHCP发现消息或DHCP请求消息等，第四消息可以为DHCP提供消息(DHCP offer)或DHCP确认消息(DHCP ACK)等。
在一种实现方式中，若终端设备采用PPPoE协议，第三消息可以为PADI、PADR或LCP协商过程中的消息，第四消息可以为PADO、PADS或LCP协商过程中的消息。并且，若终端设备采用PPPoE协议，固网网关设备还可以为接入网设备分配第一会话标识，接入网设备还可以为终端设备分配第二会话标识，第二会话标识对应于第一会话标识，若后续接收到来自终端设备的用户面数据，接入网设备还可以将用户面数据中的第二会话标识替换为第一会话标识。这里的会话标识可以为PPPoE会话标识。
在一种实现方式中，方法500还包括：接入网设备获取或预配置至少一个IP地址和/或至少一个会话标识，第二IP地址为至少一个IP地址中的一个，第二会话标识为至少一个会话标识中的一个。换句话说，接入网设备可以提前获取或预配置IP地址资源池或会话标识资源池，当需要为终端设备分配IP地址或会话标识时，可以从相应的IP地址资源池或会话标识资源池中获取。
需要说明的是，接入网设备进行接入网设备的接入管理的认证过程也可以在获取指示信息之前执行，进一步地，当终端设备完成注册，接入网设备可以直接根据指示信息为终端设备分配IP地址和/或会话标识。
在一种实现方式中，接入网设备还可以与终端设备建立接入网资源。本申请不限定接入网设备与终端设备建立接入网资源的时机。例如，在接收到指示信息后，接入网设备可以与终端设备建立接入网资源。又例如，在终端设备完成注册之后，接入网设备可以与终端设备建立接入网资源。例如，在接收到第四消息后，接入网设备可以与终端设备建立接入网资源。
需要说明的是，假设在接入网设备已经与终端设备建立了接入网资源，若接入网设备接收到的是注册拒绝信息、认证失败信息、会话拒绝信息、或第四消息指示终端设备未通过接入管理的认证，则接入网设备可以释放与终端设备的接入网资源。
方式5
方式5针对由SMF代替终端设备与固网网关设备交互以完成终端设备的认证、终端设备的IP地址的获取和/或会话标识的获取的情况，在该情况下，接入网设备在获取到指示信息后即可与终端设备建立接入网资源。
在一种实现方式中，SMF可以通过以下方式与固网网关设备交互以完成终端设备的认证、终端设备的IP地址的获取和/或会话标识的获取。具体地，SMF在确定终端设备为设定类型的终端设备和/或且开通了固网业务(或者有权限获取固网业务，或者该终端设备的业务数据流需分流至固网网关设备)时，获取第五信息，第五信息为可通过接入管理的认证的信息。SMF向固网网关设备发送第五信息。在接收到第五信息后，固网网关设备通过固网服务器向AAA服务器发送第五信息。在接收到第五信息后，AAA服务器根据第五信息对终端设备进行接入管理的认证，由于第五信息为可通过接入管理的认证信息，因此AAA服务器会通过终端设备的接入管理认证，AAA服务器通过固网服务器向固网网关设备反馈终端设备通过接入管理的认证。固网网关设备接收来自固网服务器的第七消息，第七消息用于指示终端设备通过接入管理的认证，第七消息可以包括固网服务器为终端设备分配的IP地址。进一步地，SMF可以通过AMF向接入网设备发送N1N2消息，对于NIN2消息的描述可以参考上文，在此不再赘述。
在一种实现方式中，终端设备的IP地址也可以是固网网关设备分配的。
在一种实现方式中，上述接入管理可以包括对是否开通固网业务(或者是否有权获取固网业务)进行认证。
在一种实现方式中，第五信息可以为预配置于核心网设备中，或者来自终端设备，或者来自其他核心网设备。在一种实现方式中，第五信息可以为可接入的线路标识(line ID)。
在一种实现方式中，若终端设备采用IPoE协议，第六消息可以为DHCP发现消息或DHCP请求消息等，第七消息可以为DHCP提供消息(DHCP offer)或DHCP确认消息(DHCP ACK)等，固网服务器可以为DHCP服务器。
在一种实现方式中，若终端设备采用PPPoE协议，第六消息可以为PADI、PADR或LCP协商过程中的消息，第七消息可以为PADO、PADS或LCP协商过程中的消息，固网服务器可以为PPPoE服务器；此时，PPPoE服务器功能可以集成于固网网关设备中。一种可能的实现方式，固网网关设备集成了固网服务器功能，为终端设备分配IP地址。可选的，终端设备通过IPCP获取IP地址。并且，若终端设备采用PPPoE协议，固网网关设备还可以为终端设备分配PPPoE会话标识。
这样，当网络侧需要对终端设备进行接入管理且终端设备通过该接入管理后，终端设 备的上行数据则可以通过接入网设备发送给固网网关设备，发送给终端设备的下行数据则可以由固网网关设备通过接入网设备发送至终端设备，即将终端设备的用户面数据分流至固网网关设备，有助于降低核心网的数据处理和传输压力。
下面结合具体的示例对本申请的技术方案进行详细描述。
示例1
图6是本申请提供的终端设备的注册流程的示意图。
步骤601，终端设备向接入网设备发送注册请求消息。
其中，注册请求消息(registration request)可以携带注册类型(registration type)以及终端设备的标识信息。
注册类型可以包括如下几种：
1)初始注册(initial registration)：当终端设备处于去注册状态时发起的注册流程；
2)移动性注册更新(mobility registration update)：当终端设备因移动而需要发起的注册流程；
3)周期性注册更新(periodic registration update)：当终端设备处于注册状态，因周期性注册更新计时器超时而发起的注册流程；
4)紧急注册(emergency registration)：当终端设备处于业务受限状态时发起的注册流程。
终端设备的标识信息可以包括用户的订阅隐藏标识(subscription concealed identifier，SUCI)、5G全球唯一临时标识(5G-globally unique temporary identity，5G-GUTI)、永久设备标识(permanent equipment identifier，PEI)中的至少一个。例如，当终端设备具有有效的5G-GUTI时，在注册请求消息中携带该5G-GUTI。又例如，若终端设备无有效的5G-GUTI，则在注册请求消息中携带SUCI。又例如，在紧急注册中，若终端设备无有效的5G-GUTI以及无用户永久标识(subscription permanent identifier，SUPI)(由于SUCI是加密的SUPI，此时可以理解为终端设备无SUCI)，则在注册请求消息中携带PEI。
步骤602，接入网设备选择合适的AMF。
步骤603，接入网设备将终端设备发送的注册请求消息发给选择的AMF。
步骤604，AMF选择合适的AUSF以进行鉴权等安全流程。
具体地，终端设备、AMF、AUSF、UDM交互，以完成鉴权等安全流程。
上述步骤601-604更详细的描述可以参考现有技术，在此不再详述。
在本申请中，终端设备与网络侧完成鉴权等安全流程后的流程可以包括步骤605-607，步骤605-607的具体实现方式可以有以下三种方式。
方式1
步骤605，当终端设备与网络侧完成鉴权等安全流程后，AMF与UDM交互以获取终端设备的签约数据。
步骤606，AMF向接入网设备发送N2消息。
其中，N2消息包括向给终端设备发送的NAS消息。该NAS消息中可以包括AMF向终端设备发送的第一注册接受信息(registration accept)或第一注册拒绝信息(registration reject)。
步骤607，在接收到来自AMF的N2消息后，接入网设备向终端设备转发AMF发送 的NAS消息。其中，NAS消息可以包括第一注册接受信息或第一注册拒绝信息。
方式2
步骤605，当终端设备与网络侧完成鉴权等安全流程后，AMF与UDM交互以获取终端设备的签约数据。
其中，签约数据可以包括终端设备的类型和/或第二业务信息。终端设备的类型用于指示该终端设备是否为设定类型的终端设备；第二业务信息用于指示该终端设备是否开通了固网业务(或者指示终端设备是否有权限获取固网业务，或者指示该终端设备的业务数据流是否需要分流至固网网关设备)。
步骤606，AMF向接入网设备发送N2消息。
其中，N2消息包括向终端设备发送的NAS消息，该NAS消息中可以包括AMF向终端设备发送的第一注册接受信息或第一注册拒绝信息。
N2消息除了包括该NAS消息外，还可以包括发送给接入网设备的第二注册接受信息或第二注册拒绝信息。若该终端设备为设定类型的终端设备和/或终端设备开通了固网业务(或者有权限获取固网业务，或者该终端设备的业务数据流需要分流至固网网关设备)，则AMF可以通过N2消息(非NAS消息中)向接入网设备发送第二注册接受信息；若该终端设备不是设定类型的终端设备和/或终端设备未开通固网业务(或没有权限获取固网业务、或者该终端设备的业务数据流无需分流至固网网关设备)，则AMF通过N2消息可以向接入网设备发送第二注册拒绝信息，或者AMF无需在N2消息包括第二注册接受信息或第二注册拒绝信息。
在一种实现方式中，N2消息还可以包括发送给接入网设备的终端设备的类型。
步骤607，在接收到来自AMF的N2消息后，接入网设备向终端设备转发AMF发送的NAS消息，并根据N2消息中的第二注册接受信息或第二注册拒绝信息，确定该终端设备是否注册成功。其中，NAS消息可以包括第一注册接受信息或第一注册拒绝信息。
在一种实现方式中，若N2消息还包括终端设备的类型信息，接入网设备可以根据N2消息中的终端设备类型信息，确定该终端设备是否为设定类型的终端设备。
由上述内容可知，AMF可以向接入网设备发送第二注册拒绝信息(可选的)或第二注册接受信息、以及终端设备的类型(可选的)。
方式3
步骤605，当终端设备与网络侧完成鉴权等安全流程后，AMF与UDM交互以获取终端设备的签约数据。
其中，签约数据可以包括终端设备的类型以及第二业务信息。终端设备的类型用于指示该终端设备是否为设定类型的终端设备；第二业务信息用于指示该终端设备是否开通了固网业务(或者是否有权限获取固网业务，或者该终端设备的业务数据流是否需要分流至固网网关设备)。
步骤606，AMF向接入网设备发送N2消息。
其中，N2消息包括需要让接入网设备转发给终端设备的NAS消息，该NAS消息中可以包括AMF向终端设备发送的第一注册接受信息或第一注册拒绝信息。
N2消息除了包括该NAS消息外，还可以包括发送给接入网设备的认证指示信息。若该终端设备为设定类型的终端设备和/或终端设备开通了固网业务(或者终端设备有权限 获取固网业务，或者该终端设备的业务数据流需要分流至固网网关设备)，则认证指示信息指示认证成功，例如，认证指示信息为认证通过信息等；若该终端设备不是设定类型的终端设备和/或未开通固网业务(或者没有权限获取固网业务，或者该终端设备的业务数据流无需分流至固网网关设备)，则认证指示信息指示认证失败，或者N2消息不包括认证指示信息，例如，认证指示信息为认证失败信息等。
在一种实现方式中，N2消息还可以包括发送给接入网设备的终端设备的类型。
步骤607，在接收到来自AMF的N2消息后，接入网设备向终端设备转发AMF发送的NAS消息，并根据N2消息中的认证指示信息，确定该终端设备是否认证成功。其中，NAS消息可以包括第一注册接受信息或第一注册拒绝信息。
在一种实现方式中，若N2消息还包括终端设备的类型信息，接入网设备可以根据N2消息中的终端设备类型信息，确定该终端设备是否为设定类型的终端设备。
由上述内容可知，AMF向接入网设备发送认证指示信息(可选的)、以及终端设备的类型(可选的)。
为了描述方便，在本申请中将采用方式1的注册流程称为第一注册流程，将采用方式2的注册流程称为第二注册流程，将采用方式3的注册流程称为第三注册流程。下面对三种注册流程主要区别进行总结：
1)第一注册流程：AMF不向接入网设备发送终端设备的类型信息、注册接受信息、注册拒绝信息、认证指示信息等；
2)第二注册流程：AMF向接入网设备发送终端设备的类型信息(可选的)、以及注册接受信息或注册拒绝信息(可选的)；
3)第三注册流程：AMF向接入网设备发送终端设备的类型信息(可选的)、以及认证指示信息(可选的)。
示例2
图7是本申请提供的传输数据的方法的一个示例。
图7中的AAA服务器为认证、授权和计费(authentication，authorization，accounting)服务器，用于认证终端设备是否允许上线，也可以理解为用于认证终端设备是否开通了固网业务(或者终端设备是否有权限获取固网业务)。DHCP服务器即为动态主机配置协议服务器(dynamic host configuration protocol server)，用于为认证通过的终端设备分配IP地址。
图7所示的传输数据的方法可以基于终端设备完成了示例1中的第一注册流程、以及基于图3所示的用户面协议栈。在本示例中，终端设备会发起会话建立流程，且会话建立流程涉及与核心网设备的交互。
步骤701，终端设备向AMF发送会话建立请求消息。
其中，会话建立请求消息可以携带用于会话建立的相关参数，例如会话标识(PDU Session ID)、数据网络名称(data network name，DNN)、网络切片选择辅助信息(network slice selection assistance information，NSSAI)等。
一种可能的实现方式为终端设备向AMF发送PDU Session Establishment Request。
步骤702，在接收到来自终端设备的会话建立请求消息后，AMF选择合适的SMF。
步骤703，AMF向SMF发送创建会话上下文请求消息。
其中，创建会话上下文请求消息可以携带终端设备的标识(例如，SUPI等)、会话标识、数据网络名称、网络切片选择辅助信息等。
一种可能的实现方式为AMF向SMF发送Nsmf_PDUSession_CreateSMContext Request。
步骤704，SMF与UDM交互获取终端设备的签约数据。
其中，签约数据可以包括终端设备的类型和/或第二业务信息。第二业务信息用于指示该终端设备是否开通了固网业务(或者终端设备是否有权限获取固网业务，或者该终端设备的业务数据流是否需要分流至固网网关设备)。
步骤705，SMF根据终端设备的签约数据，确定终端设备的类型信息和/或终端设备是否开通了固网业务(或者是否有权限获取固网业务，或者该终端设备的业务数据流是否需要分流至固网网关设备)。
若终端设备不是设定类型的终端设备和/或终端设备未开通固网业务(或没有权限获取固网业务，或该终端设备的业务数据流无需分流至固网网关设备)，则SMF可以拒绝建立该会话。在此情况下，后续可以继续执行步骤706-708。
若终端设备为设定类型的终端设备和/或终端设备开通了固网业务(或有权限获取固网业务，或该终端设备的业务数据流需要分流至固网网关设备)，则SMF允许建立该会话，并且SMF无需选择UPF和为终端设备分配IP地址。在此情况下，SMF可以获取指示信息，并且后续可以继续执行步骤709-712。
一种可能的实现方式，当签约数据包括终端设备的类型信息，且该类型信息指示终端设备为设定类型的终端设备(例如家庭网关、家庭终端或客户端设备)时，SMF获取指示信息。
另一种可能的实现方式，当签约数据包括第二业务信息，且第二业务信息指示终端设备开通了固网业务(或者指示终端设备有权限获取固网业务，或者指示该终端设备的业务数据流需要分流至固网网关设备)时，SMF获取指示信息。
另一种可能的实现方式，当签约数据包括终端设备的类型信息和第二业务信息时，且该类型信息指示终端设备为设定类型的终端设备，以及第二业务信息指示终端设备开通了固网业务(或者指示终端设备有权限获取固网业务，或者指示该终端设备的业务数据流需要分流至固网网关设备)时，SMF确定获取指示信息。
在一些的实现方式中，上述指示信息可以为分流指示信息，用于指示将该终端设备的用户面数据分流至固网网关设备。可以理解为，当指示信息为分流指示信息时，指示信息为一种显示的指示信息，可以明确地指示接入网设备将该终端设备的用户面数据分流至固网网关设备。另一种可能的实现方式，指示信息可以是会话接受信息、认证通过信息、会话类型信息中的一个或多个。该认证通过信息表示终端设备通过会话建立流程中的二次鉴权流程。该会话类型信息指示该会话为设定类型的终端设备的会话、用于传输设定类型的终端设备的用户数据的会话、或该会话为为设定类型的终端设备建立的会话，或者指示该会话用于传输终端类型为设定类型的终端设备的用户面数据。可以理解为，此时指示信息为一种隐式的指示信息，通过向接入网设备发送会话接受、认证通过信息、会话类型信息中的一个或多个，指示发起会话建立流程的终端设备为设定类型的终端设备，且该终端设备成功建立该会话。从而暗示接入网设备将该终端设备的用户面数据分流至固网网关设备。
一种可能的实现方式，当该第二业务信息包括特定的业务流信息时，SMF确定的指示信息可以包括用于指示所述设定类型的用户面数据的信息。该业务流信息可以是以下信息中的一项或多项：地址信息、端口信息、协议信息、以及第一业务信息，其中地址信息、端口信息、协议信息、和第一业务信息的描述可以参考上文，在此不再赘述。
步骤706，SMF向AMF发送创建会话上下文响应消息。
其中，创建会话上下文响应消息可以携带N1会话信息(N1SM information)和N2会话信息(N2SM information)。N1会话信息中可以携带会话拒绝信息，例如PDU session reject。N2会话信息中可以包括会话拒绝信息或认证失败信息。其中，会话拒绝信息或认证失败信息用于向接入网设备指示该终端设备的会话建立失败或认证失败。
一种可能的实现方式为SMF向AMF发送Nsmf_PDUSession_CreateSMContext Response。
步骤707，若在步骤706中接收到N1会话信息以及N2会话信息，则AMF将N2会话信息通过N2消息向接入网设备发送，将N1会话信息通过NAS消息向终端设备发送。
在一种实现方式中，NAS消息由AMF通过N2消息发给接入网设备，再由接入网设备转发给终端设备。
步骤708，在接收到来自AMF的N2消息后，接入网设备确定该终端设备的会话建立失败或认证失败，并向终端设备转发N1会话信息，其中该N1会话信息包括会话拒绝信息。在一种实现方式中，该N1会话信息可以承载于NAS消息中，例如可以承载于PDU Session Reject。
步骤709，SMF向AMF发送N1N2消息传递消息。
其中，N1N2消息传递消息可以携带会话标识、N1会话信息、以及N2会话信息。N1会话信息是SMF通过AMF向终端设备发送的，N1会话信息中可以包括会话接受信息(会话建立接受消息)，例如PDU session accept(PDU session establishment accept)。N2会话信息是SMF通过AMF向接入网设备发送的，N2会话信息中可以包括会话标识和指示信息，指示信息的描述可以参考上文，在此不再赘述。其中，指示信息为步骤705中确定或获取的指示信息。
一种可能的实现方式为SMF向AMF发送Namf_Communication_N1N2MessageTransfer。
步骤710，在接收到N1N2消息传递消息后，AMF向接入网设备发送N2会话请求消息。
其中，N2会话请求消息可以携带来自SMF的N2会话信息和N1会话信息。N2会话信息通过N2消息向接入网设备发送，N1会话信息通过NAS消息向终端设备发送。
在一种实现方式中，NAS消息由AMF通过N2消息发给接入网设备，再由接入网设备转发给终端设备。
一种可能的实现方式为AMF向接入网设备发送N2PDU Session Request。
步骤711，在接收到来自AMF的N2消息后，接入网设备通过N2会话信息中的指示信息确定需要与固网网关设备建立用户面连接，或者说，确定需要将终端设备的用户面数据分流至固网网关设备。在此情况下，接入网设备可以与该终端设备建立接入网(access network，AN)资源，并向终端设备转发N1会话信息，其中该N1会话信息包括会话接受 信息。在一种实现方式中，该N1会话信息可以承载于NAS消息中，例如可以承载于PDU Session Accept(或PDU Session Establishment Accept)。
步骤712，接入网设备向AMF发送N2会话响应消息。
一种可能的实现方式为接入网设备向AMF发送N2PDU Session Response。
接下来可以执行IPoE认证以及IP地址分发流程。
步骤713，终端设备向接入网设备发送DHCP发现消息(DHCPDiscover)。
其中，DHCP发现消息承载于蜂窝空口或承载于数据无线承载(data radio bearer，DRB)。
在一种实现方式中，DHCP发现消息可以指示终端设备的类型。例如，可以在DHCP发现消息的选择60(Option 60)字段携带可以指示终端设备的类型的信息。
步骤714，在接收到来自终端设备的DHCP发现消息后，接入网设备可以根据终端设备是否需要与固网网关设备建立用户面连接，向DHCP发现消息中插入可接入的线路ID(line ID)或不可接入的线路ID。
若在步骤713之前执行步骤706-708，则接入网设备在终端设备发送的DHCP发现消息中插入不可接入的线路ID。在另一种可能的实现方式中，接入网设备也可以不转发该DHCP发现消息。
若在步骤713之前执行步骤709-712，则接入网设备在终端设备发送的DHCP发现消息中插入可接入的线路ID，以使得终端设备可以通过IPoE认证。
在一种可能的实现方式中，若DHCP发现消息指示终端设备的类型信息，接入网设备也可以是通过DHCP发现消息获知终端设备的类型信息的。
在一种实现方式中，在步骤714之前的任何一个步骤之前，还可以执行步骤715。
步骤715，接入网设备获取可接入的线路ID。
一种可能的实现方式为接入网设备通过带外的方式获取可接入的线路ID。例如，可以通过预配置的方式为接入网设备配置可接入的线路ID。
在一种实现方式中，接入网设备还可以获取不可接入的线路ID。
步骤716，接入网设备向固网网关设备发送DHCP发现消息。
步骤717，在接收到来自接入网设备的DHCP发现消息后，固网网关设备向DHCP服务器发送DHCP发现消息。
步骤718，在接收到来自固网网关设备的DHCP发现消息后，DHCP服务器获取DHCP发现消息中的线路ID等信息，构造认证所需的第一认证信息，并向AAA服务器发送接入请求(Access Request)消息。
其中，接入请求消息可以包括该第一认证信息。
步骤719，AAA服务器根据第一认证信息，对该终端设备进行认证。
AAA服务器的认证结果不同，后续执行的步骤也不同。若第一认证信息中的线路ID为不可接入的线路ID，AAA服务器不通过终端设备的认证，后续可以执行步骤720-721。若第一认证信息中的线路ID为可接入的线路ID，AAA服务器通过终端设备的认证，后续可以执行步骤722-725。
步骤720，AAA服务器向DHCP服务器发送接入拒绝(access deny)消息。
步骤721，在接收到AAA服务器的接入拒绝消息后，DHCP服务器通过固网网关设备、接入网设备向终端设备发送DHCP否认(negative acknowledgement，NACK)消息。
步骤722，AAA服务器向DHCP服务器发送接入接受(access accept)消息。
步骤723，在接收到AAA服务器的接入接受消息后，DHCP服务器为终端设备分配IP地址，将为终端设备分配的IP地址包含于DHCP提供(offer)消息中，并通过固网网关设备、接入网设备向终端设备发送DHCP提供消息。
在一种实现方式中，DHCP提供消息中还可以包括第二认证信息，以便终端设备能够根据第二认证信息进行鉴权，识别该DHCP提供消息是否来自可信的DHCP服务器。
若步骤713中的DHCP发现消息为广播消息，则可能会有多个DHCP服务器接收到该DHCP发现消息，因此在步骤723中，也可能会有多个DHCP服务器为终端设备分配IP地址并发送DHCP提供消息。若终端设备接收来自多个DHCP服务器发送的DHCP提供消息，则还可以执行步骤724和725。
步骤724，在接收到DHCP提供消息后，终端设备通过接入网设备、固网网关设备向DHCP服务器发送DHCP请求(DHCP Request)消息。
在一种可能的实现方式中，终端设备根据多个DHCP提供消息中的一个(例如，最先收到的DHCP提供消息)发送DCHP请求消息，其中，DHCP请求消息可以包括该DHCP服务器分配的IP地址。
步骤725，DHCP服务器通过固网网关设备、接入网设备向终端设备发送DHCP确认(acknowledgement，ACK)消息。其中，DHCP服务器为分配DHCP请求消息中携带的IP地址的DHCP服务器。
基于本示例的用户面数据传输的将在下文结合图12进行详细描述。
由上述内容可知，在示例2中，终端设备完成注册以及发起会话建立请求后，核心网设备在会话建立流程中通过签约数据获知终端设备为设定类型的终端设备和/或该终端设备开通了固网业务(或有权限获取固网业务，或该终端设备的业务数据流需要分流至固网网关设备)，并将向接入网设备发送相应信息，使得接入网设备后续在收到来自终端设备的DHCP消息后可以进行相对应的操作。例如，若终端设备未开通固网业务(或没有权限获取固网业务，或该终端设备的业务数据流无需分流至固网网关设备)，则核心网设备向接入网设备指示该终端设备的会话建立被拒绝和/或该终端设备未通过认证，或者不向接入网设备发送指示信息；接入网设备收到来自该终端设备的DHCP发现消息后，插入不可接入的线路ID或对该DHCP发现消息不做处理。又例如，若该终端设备为设定类型的终端设备和/或开通了固网业务(或有权限获取固网业务，或该终端设备的业务数据流需分流至固网网关设备)，则核心网设备向接入网设备获取指示信息并向接入网设备发送该指示信息；接入网设备可以与终端设备建立AN资源，并在收到来自终端设备的DHCP发现消息后，插入可接入的线路ID，使得终端设备能通过AAA服务器的认证，与固网网关设备之间建立连接，并获得DHCP服务器为其分配的IP地址，从而使得终端设备能够通过接入网设备和固网网关设备与数据网络进行数据交互。有助于降低核心网的数据处理和传输压力。
需要说明的是，示例2仅以终端设备采用IPoE协议为例，示例2所示的技术方案同样适用终端设备采用其他传输协议的场景。例如，对于采用PPPoE协议的终端设备而言，区别在于各网元交互的是与PPPoE相关的消息，例如PADI、PADO、PADR、和PADS等，若接入网设备获取指示信息，在交互过程中，接入网设备可以在PADI消息中插入可 接入的线路ID；固网网关设备会为该终端设备分配PPPoE会话标识；终端设备还会通过接入网设备与固网网关设备交互LCP消息以完成配置数据链路参数，以及完成认证阶段与网络参数协商阶段，使终端设备获取IP地址。
示例3
图8是本申请提供的传输数据的方法的另一个示例。
图8所示的建立连接流程可以基于终端设备完成示例1中的第一注册流程、以及基于图3所示的用户面协议栈。在本示例中，终端设备会发起会话建立流程，且核心网会参与该会话建立流程，与示例2区别在于，SMF代替终端设备与固网网关设备交互以完成终端设备的认证和IP地址的获取，并将获取的IP地址通过会话建立流程中发给终端设备。
步骤801，终端设备向AMF发送会话建立请求消息。
步骤802，在接收到来自终端设备的会话建立请求消息后，AMF选择合适的SMF。
步骤803，AMF向SMF发送创建会话上下文请求消息。
步骤804，SMF与UDM交互获取终端设备的签约数据。
其中，签约数据可以包括终端设备的类型以及第二业务信息。第二业务信息用于指示该终端设备是否开通了固网业务(或者是否有权限获取固网业务，或者该终端设备的业务数据流是否需要分流至固网网关设备)。
步骤805，SMF根据终端设备的签约数据，确定终端设备的类型信息和/或终端设备是否开通了固网业务(或者是否有权限获取固网业务，或者该终端设备的业务数据流是否需要分流至固网网关设备)。
在一种实现方式中，若终端设备不是设定类型终端设备和/或终端设备未开通固网业务(或没有权限获取固网业务，或该终端设备的业务数据流无需分流至固网网关设备)，则SMF可以拒绝建立该会话。在此情况下，后续可以继续执行步骤806-808。
若终端设备为设定类型的终端设备和/或终端设备开通了固网业务(或有权限获取固网业务，或该终端设备的业务数据流需要分流至固网网关设备)，则SMF允许建立该会话，并且SMF无需选择UPF和为终端设备分配IP地址。在此情况下，后续可以继续执行步骤809-823。
步骤806，SMF向AMF发送创建会话上下文响应消息。
其中，创建会话上下文响应消息可以携带N1会话信息。N1会话信息中可以携带会话拒绝信息，例如PDU session reject。
一种可能的实现方式为SMF向AMF发送Nsmf_PDUSession_CreateSMContext Response。
步骤807，若在步骤806中接收到N1会话信息，则AMF将N1会话信息通过NAS消息向终端设备发送。若在步骤806中接收到N2会话信息，则AMF向接入网设备发送N2会话信息。
步骤808，在接收到来自AMF的N2消息后，接入网设备确定该终端设备的会话建立失败或认证失败，并向终端设备转发N1会话信息，其中该N1会话信息包括会话拒绝信息。
步骤801-808更详细的描述可以参考步骤701-708，在此不再赘述。
步骤809，SMF向固网网关设备发送DHCP发现消息。
其中，DHCP发现消息中包括可接入的线路ID。也就是说，SMF会在DHCP消息中插入可接入的线路ID。其中，该可接入的线路ID可以用于标识该终端设备。
一种可能的实现方式为SMF通过网络能力开放功能(network exposure function，NEF)网元向固网网关设备发送DHCP发现消息。
在一种实现方式中，在步骤809之前的任意一个步骤，还可以执行步骤810。
步骤810，SMF获取可接入的线路ID。
一种可能的实现方式为SMF通过带外的方式获取可接入的线路ID。例如，可以通过预配置的方式为SMF配置可接入的线路ID。
在一种实现方式中，SMF还可以获取不可接入的线路ID。
步骤811，在接收到来自SMF的DHCP发现消息后，固网网关设备向DHCP服务器发送DHCP发现消息。
步骤812，在接收到来自固网网关设备的DHCP发现消息后，DHCP服务器获取DHCP发现消息中的线路ID等信息，构造认证所需的第一认证信息，并向AAA服务器发送接入请求消息。
其中，接入请求消息可以包括该第一认证信息。
步骤813，AAA服务器根据第一认证信息，对该终端设备进行认证。
由于线路ID可以用于标识终端设备，且第一认证信息是根据线路ID构造的，因此第一认证信息可以标识该终端设备，因此AAA服务器可以根据第一认证信息，对该终端设备进行认证。
AAA服务器的认证结果不同，后续执行的步骤也不同。
若第一认证信息中的线路ID为不可接入的线路ID，AAA服务器不通过终端设备的认证，后续可以执行步骤814-815。若第一认证信息中的线路ID为可接入的线路ID，AAA服务器通过终端设备的认证，后续，则可以执行步骤816-823。在本示例中，由于SMF在DHCP发现消息中插入的是可接入的线路ID，因此AAA服务器会通过终端设备的认证。
步骤814，AAA服务器向DHCP服务器发送接入拒绝消息。
步骤815，在接收到AAA服务器的接入拒绝消息后，DHCP服务器向通过固网网关设备向SMF发送DHCP NACK消息。
步骤816，AAA服务器向DHCP服务器发送接入接受消息。
步骤817，在接收到AAA服务器的接入接受消息后，DHCP服务器为终端设备分配IP地址，将为终端设备分配的IP地址包含于DHCP提供消息中，并通过固网网关设备向SMF发送DHCP提供消息。
若步骤809中的DHCP发现消息为广播消息，则可能会有多个DHCP服务器接收到该DHCP发现消息，因此在步骤817中，也可能会有多个DHCP服务器为终端设备分配IP地址并发送DHCP提供消息。若SMF接收来自多个DHCP服务器发送的DHCP提供消息，则SMF可以执行步骤818和819。
步骤818，在接收到DHCP提供消息后，SMF通过固网网关设备向DHCP服务器发送DHCP请求消息。
在一种可能的实现方式中，SMF根据多个DHCP提供消息中的一个(例如，最先收到的DHCP提供消息)发送DCHP请求消息，其中，DHCP请求消息可以包括该DHCP 服务器分配的IP地址。
步骤819，DHCP服务器通过固网网关设备向SMF发送DHCP ACK消息。其中，DHCP服务器为分配DHCP请求消息中携带的IP地址的DHCP服务器。
步骤820，在接收到DHCP ACK消息后，SMF可以获取指示信息，并SMF向AMF发送N1N2消息传递消息。
其中，N1N2消息传递消息可以携带会话标识、N1会话信息、以及N2会话信息。N1会话信息是SMF通过AMF向终端设备发送的，N1会话信息中可以包括会话接受信息(例如PDU session accept)和DHCP服务器为终端设备分配的IP地址，例如PDU session accept。N2会话信息是SMF通过AMF向接入网设备发送的，N2会话信息中可以包括会话标识和指示信息，指示信息的描述可以参考上文，在此不再赘述。
一种可能的实现方式为SMF向AMF发送Namf_Communication_N1N2Message Transfer。
步骤821，在接收到N1N2消息传递消息后，AMF向接入网设备发送N2会话请求消息。
其中，N2会话请求消息可以携带来自SMF的N2会话信息和N1会话信息。N2会话信息通过N2消息向接入网设备发送，N1会话信息通过NAS消息向终端设备发送。
在一种实现方式中，NAS消息由AMF通过N2消息发给接入网设备，再由接入网设备转发给终端设备。
一种可能的实现方式为AMF向接入网设备发送N2PDU Session Request。
步骤822，在接收到来自AMF的N2消息后，接入网设备通过N2会话信息中的指示信息确定需要与固网网关设备建立用户面连接，或者说，确定需要将终端设备的用户面数据分流至固网网关设备。在此情况下，接入网设备可以与该终端设备建立AN资源，并向终端设备转发N1会话信息，其中该N1会话信息包括会话接受信息。在一种实现方式中，该N1会话信息可以承载于NAS消息中，例如可以承载于PDU Session Accept。
步骤823，接入网设备向AMF发送N2会话响应消息。
一种可能的实现方式为接入网设备向AMF发送N2PDU Session Response。
基于本示例的用户面数据传输的将在下文结合图12进行详细描述。
由上述内容可知，在示例3中，终端设备完成注册以及发起会话建立请求后，核心网设备在会话建立流程中通过签约数据获知终端设备为设定类型的终端设备和/或该终端设备开通了固网业务(或有权限获取固网业务，或该终端设备的业务数据流需要分流至固网网关设备)，向固网网关设备发送DHCP发现消息，以完成IPoE认证及获取IP地址，并可以在会话建立流程中将IP地址发给终端设备，同时还可以通过向接入网设备发送指示信息，使得接入网设备获知无需与UPF建立N3隧道。这样，在后续收到来自终端设备的用户面数据时，接入网设备可以将用户面数据发送给固网网关设备而不是UPF，从而使得终端设备能够通过接入网设备和固网网关设备与数据网络进行数据交互。有助于降低核心网的数据处理和传输压力。
需要说明的是，示例3同样仅以终端设备采用IPoE协议为例，示例3所示的技术方案同样适用终端设备采用其他传输协议的场景。例如，对于采用PPPoE协议的终端设备而言，区别在于各网元交互的是与PPPoE相关的消息，例如PADI、PADO、PADR、和 PADS等，若该终端设备为设定类型的终端设备和/或该终端设备开通了固网业务(或有权限获取固网业务，或该终端设备的业务数据流需要分流至固网网关设备)，在交互过程中，SMF可以在PADI消息中插入可接入的线路ID；固网网关设备会为该终端设备分配PPPoE会话标识；SMF与固网网关设备还会交互LCP消息以完成配置数据链路参数，以及完成认证阶段与网络参数协商阶段，使终端设备获取IP地址。
示例4
图9是本申请提供的传输数据的方法的另一个示例。
图9所示的建立连接流程可以基于终端设备完成示例1中的第二注册流程或第三注册流程、以及基于图3所示的用户面协议栈。在本示例中，由于接入网设备在终端设备的注册流程中已经直接或间接获知终端设备的类型信息和/或终端设备是否开通了固网业务(或者是否有权限获取固网业务，或者该终端设备的业务数据流是否需要分流至固网网关设备)，因此，接入网设备无需再通过会话建立流程获取这些信息。终端设备完成注册流程后，即可进行IPoE认证、获取IP地址、以及与接入网设备建立AN资源。
步骤901，终端设备向接入网设备发送会话建立请求消息。
步骤902，接入网设备截获终端设备发送的会话建立请求消息，并根据该消息确定终端设备在建立会话。由于接入网设备在注册流程中获取终端设备的类型信息和/或终端设备是否开通了固网业务(或者是否有权限获取固网业务，或者该终端设备的业务数据流是否需要分流至固网网关设备)，若接入网设备在终端设备的注册流程中确认终端设备为设定类型的终端设备和/或终端设备开通了固网业务(或有权限获取固网业务，或该终端设备的业务数据流需要分流至固网网关设备)，则接入网设备可以获知需要截获终端设备在注册流程之后发送的NAS消息。因此，在一种实现方式中，接入网设备在终端设备完成注册流程之后，截获终端设备发送的NAS消息，获知该消息为会话建立请求消息。接入网设备在终端设备的注册流程中确定终端设备为设定类型的终端设备和/或终端设备开通了固网业务(或有权限获取固网业务，或该终端设备的业务数据流需要分流至固网网关设备)，接入网设备可以与终端设备建立AN资源。
在一种实现方式中，接入网设备还可以向终端设备发送会话接受消息。
需要说明的是，步骤901和902为可选步骤，即在执行建立连接的流程之前，终端设备与接入网设备可以建立AN资源，也可以不建立AN资源。
步骤903，终端设备向接入网设备发送DHCP发现消息。
其中，DHCP发现消息承载于蜂窝空口或承载于DRB。例如，若在步骤903之前，未执行步骤901-902，DHCP发现消息可以承载于RRC消息中。又例如，若在步骤903之前，执行了步骤901-902，DHCP发现消息也可以承载于DRB中。
在一种实现方式中，DHCP发现消息可以指示终端设备的类型。例如，可以在DHCP发现消息的选择60(Option 60)字段携带可以指示终端设备的类型的信息。
步骤904，在接收到来自终端设备的DHCP发现消息后，接入网设备根据终端设备是否开通固网业务(或是否有权限获取固网业务，或该终端设备的业务数据流是否需要分流至固网网关设备)，向DHCP发现消息中插入可接入的线路ID或不可接入的线路ID。
在一种实现方式中，在步骤904之前的任意一个步骤，还可以执行步骤905。
步骤905，接入网设备获取可接入的线路ID。
步骤906，接入网设备向固网网关设备发送DHCP发现消息。
步骤907，在接收到来自接入网设备的DHCP发现消息后，固网网关设备向DHCP服务器发送DHCP发现消息。
步骤908，在接收到来自固网网关设备的DHCP发现消息后，DHCP服务器获取DHCP发现消息中的线路ID等信息，构造认证所需的第一认证信息，并向AAA服务器发送接入请求消息。
步骤909，AAA服务器根据第一认证信息，对该终端设备进行认证。
AAA服务器的认证结果不同，后续执行的步骤也不同。若第一认证信息中的线路ID为不可接入的线路ID，AAA服务器不通过终端设备的认证，后续可以执行步骤910-911。若该终端设备开通了固网业务开通(或有权限获取固网业务)，则可以执行步骤912-916。
步骤910，AAA服务器向DHCP服务器发送接入拒绝(access deny)消息。
步骤911，在接收到AAA服务器的接入拒绝消息后，DHCP服务器通过固网网关设备、接入网设备向终端设备发送DHCPNACK消息。
在一种实现方式中，若在步骤911之前终端设备与接入网设备建立了AN资源，接入网设备还可以释放与终端设备建立的AN资源。
步骤912，AAA服务器向DHCP服务器发送接入接受消息。
步骤913，在接收到AAA服务器的接入接受消息后，DHCP服务器为终端设备分配IP地址，将为终端设备分配的IP地址包含于DHCP提供消息中，并通过固网网关设备、接入网设备向终端设备发送DHCP提供消息。
步骤914，在接收到DHCP提供消息后，终端设备通过接入网设备、固网网关设备向DHCP服务器发送DHCP请求消息。
步骤915，DHCP服务器通过固网网关设备、接入网设备向终端设备发送DHCP ACK消息。其中，DHCP服务器为分配DHCP请求消息中携带的IP地址的DHCP服务器。
步骤916，若接收到DHCP ACK消息，则接入网设备可以与终端设备建立AN资源。该步骤为可选步骤。例如，若未执行步骤901-902，则可以执行步骤916。
上述步骤903-915更详细的描述可以参考步骤713-725，在此不再赘述。
基于本示例的用户面数据传输的将在下文结合图12进行详细描述。
由上述内容可知，在示例4中，接入网设备可以在注册流程中直接或间接获知终端设备的类型信息和/或是否开通固网业务(或者是否有权限获取固网业务，或者该终端设备的业务数据流是否需要分流至固网网关设备)，从而根据该信息来确定是否与终端设备建立AN资源，并根据该信息在终端设备发送的DHCP发现消息中插入相对应的线路ID。在示例4中，终端设备无需发起会话建立流程(或者可以发送会话建立请求消息，但该消息被接入网设备截获，核心网设备实际上没有参与会话建立流程)，可以进一步减少网络侧的信令开销。
示例4同样仅以终端设备采用IPoE协议为例，示例4所示的技术方案同样适用终端设备采用其他传输协议的场景。例如，对于采用PPPoE协议的终端设备而言，区别在于各网元交互的是与PPPoE相关的消息，例如PADI、PADO、PADR、和PADS等，若该终端设备为设定类型的终端设备和/或该终端设备开通了固网业务(或有权限获取固网业务，或该终端设备的业务数据流需要分流至固网网关设备)，在交互过程中，接入网设备 可以在PADI消息中插入可接入的线路ID；固网网关设备会为该终端设备分配PPPoE会话标识；终端设备还会通过接入网设备与固网网关设备交互LCP消息以完成配置数据链路参数，以及完成认证阶段与网络参数协商阶段，使终端设备获取IP地址。
示例5
图10是本申请提供的传输数据的方法的另一个示例。
图10所示的建立连接流程可以基于终端设备执行示例1中的第二注册流程或第三注册流程、以及图4所示的用户面协议栈。在本示例中，核心网设备不参与用户面连接建立流程，接入网设备作为固网终端设备预先与固网网关设备建立连接，接入网设备可以通过进行网络地址转换(network address translation，NAT)实现终端设备通过接入网设备和固网网关设备与数据网络进行数据交互。
步骤1001，接入网设备向固网网关设备发送DHCP发现消息。
其中，DHCP发现消息中包括可接入的线路ID。也就是说，接入网设备会在DHCP消息中插入可接入的线路ID，以使得接入网设备可以通过IPoE认证。
在一种实现方式中，在步骤1001之前还可以执行步骤1002。
步骤1002，接入网设备获取可接入的线路ID和IP地址资源池。
一种可能的实现方式为接入网设备通过带外的方式获取可接入的线路ID和IP地址资源池。例如，可以通过预配置的方式为接入网设备配置可接入的线路ID和IP地址资源池。
IP地址资源池中的IP地址可以在接入网设备确定终端设备为设定类型的终端设备和/或该终端设备开通了固网业务(或有权限获取固网业务或该终端设备的业务数据流需要分流至固网网关设备)时分配给该终端设备。
步骤1003，在接收到来自接入网设备的DHCP发现消息后，固网网关设备向DHCP服务器发送DHCP发现消息。
步骤1004，在接收到来自固网网关设备的DHCP发现消息后，DHCP服务器获取DHCP发现消息中的线路ID等信息，构造认证所需的第一认证信息，并向AAA服务器发送接入请求消息。
步骤1005，AAA服务器根据第一认证信息，对该接入网设备进行认证。
步骤1006，AAA服务器向DHCP服务器发送接入接受消息。
由于接入请求消息中的线路ID为可接入的线路ID，因此，接入网设备会通过AAA服务器的认证。
步骤1007，在接收到AAA服务器的接入接受消息后，DHCP服务器为接入网设备分配IP地址，将为接入网设备分配的IP地址包含于DHCP提供消息中，并通过固网网关设备向接入网设备发送DHCP提供消息。
若步骤1001中的DHCP发现消息为广播消息，则可能会有多个DHCP服务器接收到该DHCP发现消息，因此在步骤1007中，也可能会有多个DHCP服务器为接入网设备分配IP地址并发送DHCP提供消息。若接入网设备接收来自多个DHCP服务器发送的DHCP提供消息，则接入网设备可以执行步骤1008和1009。
步骤1008，在接收到DHCP提供消息后，接入网设备通过固网网关设备向DHCP服务器发送DHCP请求消息。
在一种可能的实现方式中，接入网设备根据多个DHCP提供消息中的一个(例如，最 先收到的DHCP提供消息)发送DCHP请求消息，其中，DHCP请求消息可以包括该DHCP服务器分配的IP地址。
步骤1009，DHCP服务器通过固网网关设备向接入网设备发送DHCP ACK消息。其中，DHCP服务器为分配DHCP请求消息中携带的IP地址的DHCP服务器。
通过上述步骤1001-1009，接入网设备作为固网终端设备，与固网网关设备建立了连接，获取为接入网设备分配的IP地址。
后续若终端设备需要通过接入网设备和固网网关设备与数据网络进行数据交互，可以继续执行步骤1010和步骤1011。
步骤1010，终端设备执行如示例1中的所示的第二注册流程或第三注册流程。
通过第二注册流程或第三注册流程，接入网设备可以直接或间接获知终端设备的类型信息和/或终端设备是否开通了固网业务(或者是否有权限获取固网业务或者该终端设备的业务数据流是否需要分流至固网网关设备)。
步骤1011，若终端设备为设定类型的终端设备和/或终端设备开通了固网业务(或有权限获取固网业务，或该终端设备的业务数据流需要分流至固网网关设备)，则接入网设备与终端设备建立AN资源，并向终端设备分配IP地址。
若终端设备不是设定类型的终端设备和/或终端设备未开通固网业务(或没有权限获取固网业务，或者该终端设备的业务数据流不需要分流至固网网关设备)，则接入网设备可以不与终端设备建立AN资源，也不为终端设备分配IP地址。
为终端设备分配的IP地址可以为步骤1002中获取的IP地址资源池中的IP地址。
在本示例中，接入网设备可以维护接入网设备为终端设备分配的IP地址与DHCP服务器为接入网设备分配的IP地址的映射关系，从而实现接入网设备的NAT功能，从而实现终端设备通过接入网设备和固网网关设备与数据网络进行数据交互。基于本示例的用户面数据传输的将在下文结合图13进行详细描述。
由上述内容可知，在示例5中，接入网设备作为固网终端设备预先与固网网关设备建立连接，获取为接入网设备分配的IP地址；当终端设备完成示例1所述的第二注册流程或第三注册流程后，若终端设备为设定类型的终端设备和/或该终端设备开通了固网业务(或有权限获取固网业务或该终端设备的业务数据流需要分流至固网网关设备)，接入网设备可以与终端设备建立AN资源，并为终端设备分配IP地址。进而接入网设备通过进行网络地址转换即可以实现终端设备通过接入网设备和固网网关设备与数据网络进行数据交互。在示例5中同样可以省略会话建立流程，可以进一步减少网络侧的信令开销。
示例5同样仅以终端设备采用IPoE协议为例，示例5所示的技术方案同样适用终端设备采用其他传输协议的场景。例如，对于采用PPPoE协议的终端设备而言，区别在于各网元交互的是与PPPoE相关的消息，例如PADI、PADO、PADR、和PADS等，在交互过程中，固网网关设备会为接入网设备分配PPPoE会话标识，随后，接入网设备与固网网关设备还会交互LCP消息以完成配置数据链路参数，以及完成认证阶段与网络参数协商阶段，使接入网设备获取IP地址。同理，终端设备与接入网设备交互，接入网设备为终端设备分配PPPoE会话标识以及IP地址。
示例6
图11是本申请提供的传输数据的方法的另一个示例。
图11所示的建立连接流程可以基于终端设备完成示例1中的第二注册流程、以及基于图3所示的用户面协议栈。在本示例中，核心网设备同样不参与建立连接流程，且在终端设备的注册流程中，可以不包括固网业务的认证流程，当终端设备完成注册流程后，再进一步在AAA服务器处完成固网业务的认证。
步骤1101，若接入网设备确认终端设备注册成功，则接入网设备与终端设备建立AN资源。
若终端设备完成第二注册流程，且在该流程中来自AMF的N2会话消息中包括注册接受信息和指示终端设备为设定类型的终端设备的信息，即接入网设备可以确定终端设备为设定类型的终端设备、以及终端设备注册成功，则接入网设备可以与终端设备建立AN资源。
需要说明的是，步骤1101为可选步骤，即在执行用户面连接建立流程之前，终端设备与接入网设备可以建立AN资源，也可以不建立AN资源。
步骤1102，终端设备向接入网设备发送DHCP发现消息。
其中，DHCP发现消息可以包括用于指示终端设备对应的用户名和密码的信息。
上述DHCP发现消息承载于蜂窝空口或承载于DRB。例如，若在步骤1102之前，未执行步骤1101，DHCP发现消息可以承载于RRC消息中。又例如，若在步骤1102之前，执行了步骤1101，DHCP发现消息也可以承载于DRB中。
在一种实现方式中，若在终端设备的注册流程中，接入网设备未获知终端设备的类型信息，接入网设备可以根据DHCP发现消息确定终端设备的类型信息。例如，接入网设备通过识别DHCP发现消息，确认终端设备为设定类型的终端设备。又例如，终端设备可以在DHCP发现消息的选择60(Option 60)字段携带可以指示终端设备的类型信息，接入网设备可以通过该字段确认终端设备为设定类型的终端设备。
步骤1103，在接收到来自终端设备的DHCP发现消息后，接入网设备向DHCP发现消息中插入线路ID。
由于固网业务的认证是独立的，因此接入网设备插入的线路ID无需像示例2至示例5中那样分为可接入的线路ID和不可接入的线路ID。
在一种实现方式中，线路ID可以与终端设备的MAC地址做映射，即一个MAC地址对应于一个线路ID，从而可以使接入网设备、固网网关设备、AAA服务器根据线路ID来区分不同终端设备。
在一种实现方式中，在步骤1103之前，还可以执行步骤1104。
步骤1104，接入网设备获取线路ID。
一种可能的实现方式为接入网设备通过带外的方式获取线路ID。例如，可以通过预配置的方式为接入网设备配置线路ID。
需要说明的是，步骤1103和1104为可选步骤。
步骤1105，接入网设备向固网网关设备发送DHCP发现消息。
步骤1106，在接收到来自接入网设备的DHCP发现消息后，固网网关设备向DHCP服务器发送DHCP发现消息。
步骤1107，在接收到来自固网网关设备的DHCP发现消息后，DHCP服务器获取DHCP发现消息中的用户名和密码等信息，构造认证所需的第一认证信息，并向AAA服务器发 送接入请求消息。
其中，接入请求消息可以包括该第一认证信息。
步骤1108，AAA服务器根据第一认证信息，对该终端设备进行认证。
具体地，AAA根据用户名和密码验证该终端设备是否开通了固网业务(或者是否有权限获取固网业务，或者该终端设备的业务数据流是否需要分流至固网网关设备)，同时，AAA服务器还验证是否已有其他设备使用该用户名和密码通过验证。若该终端设备开通了固网业务(或有权限获取固网业务，或该终端设备的业务数据流需要分流至固网网关设备)、且没有其他设备使用该用户名和密码通过验证，则AAA服务器确定该终端设备认证成功。若该终端设备未开通固网业务(或没有权限获取固网业务或该终端设备的业务数据流无需分流至固网网关设备)和/或已有其他设备使用该用户名和密码通过验证，则AAA服务器确定该终端设备认证失败。
AAA服务器的认证结果不同，后续执行的步骤也不同。
若该终端设备认证失败，则可以执行步骤1109-1111。
步骤1109，AAA服务器向DHCP服务器发送接入拒绝消息。
步骤1110，在接收到AAA服务器的接入拒绝消息后，DHCP服务器通过固网网关设备、接入网设备向终端设备发送DHCP NACK消息。
在一种实现方式中，若在步骤1110之前，终端设备与接入网设备已经建立了AN资源，还可以执行步骤1111。
步骤1111，接入网设备根据DHCP NACK消息，释放与终端设备建立的AN资源。
若该终端设备认证成功，则可以执行步骤1112-1116。
步骤1112，AAA服务器向DHCP服务器发送接入接受消息。
步骤1113，在接收到AAA服务器的接入接受消息后，DHCP服务器为终端设备分配IP地址，将为终端设备分配的IP地址包含于DHCP提供消息中，并通过固网网关设备、接入网设备向终端设备发送DHCP提供消息。
在一种实现方式中，DHCP提供消息中还可以包括第二认证信息，以便终端设备能够根据第二认证信息进行鉴权，识别该DHCP提供消息是否来自可信的DHCP服务器。
若步骤1102中的DHCP发现消息为广播消息，则可能会有多个DHCP服务器接收到该DHCP发现消息，因此在步骤1110中，也可能会有多个DHCP服务器为终端设备分配IP地址并发送DHCP提供消息。若终端设备接收来自多个DHCP服务器发送的DHCP提供消息，则终端设备可以执行步骤1114和1115。
步骤1114，在接收到DHCP提供消息后，终端设备通过接入网设备、固网网关设备向DHCP服务器发送DHCP请求消息。
在一种可能的实现方式中，终端设备根据多个DHCP提供消息中的一个(例如，最先收到的DHCP提供消息)发送DCHP请求消息，其中，DHCP请求消息可以包括该DHCP服务器分配的IP地址。
步骤1115，DHCP服务器通过固网网关设备、接入网设备向终端设备发送DHCP ACK消息。其中，DHCP服务器为分配DHCP请求消息中携带的IP地址的DHCP服务器。
在一种实现方式中，若在步骤1102之前，未执行步骤1101，则可以执行步骤1116。
步骤1116，接入网设备根据接收到的DHCP ACK消息，与终端设备建立AN资源。
基于本示例的用户面数据传输的将在下文结合图12进行详细描述。
由上述内容可知，在示例6中，将固网认证与终端设备在核心网侧的注册流程解耦，其好处在于可以使得固网业务与终端设备的签约数据相互独立，使得固网业务的服务提供商与网络运营商解耦。该示例同样省略了会话建立流程，且终端设备的注册流程采用第二注册流程，使得接入网设备能获知终端设备是否注册成功。对于注册成功的终端设备，接入网设备才会与其建立AN资源或为其转发DHCP发现消息。
示例6同样仅以终端设备采用IPoE协议为例，示例6所示的技术方案同样适用终端设备采用其他传输协议的场景。例如，对于采用PPPoE协议的终端设备而言，区别在于各网元交互的是与PPPoE相关的消息，例如PADI、PADO、PADR、和PADS等，PADI中可以包括用户名和密码，接入网设备可以在PADI消息中插入线路ID；固网网关设备会为该终端设备分配PPPoE会话标识；终端设备还会通过接入网设备与固网网关设备交互LCP消息以完成配置数据链路参数，以及完成认证阶段与网络参数协商阶段，使终端设备获取IP地址。
示例7
图12是本申请提供的数据传输流程的一个示例。
图12所示的数据传输流程可以适用于上述示例2、示例3、示例4、以及示例6所示的用户面连接建立流程。如图12所示，终端设备通过接入网设备、固网网关设备向应用服务器(application server，AS)发送上行数据，应用服务器通过固网网关设备、接入网设备向终端设备发送下行数据。
示例8
图13是本申请提供的数据传输流程的另一个示例。
图13所示的数据传输流程可以适用于上述示例5所示的用户面连接建立流程。图13以两个终端设备为例，对接入网设备如何在上下行数据传输过程中进行IP地址和会话标识转换进行描述。在一种实现方式中，若终端设备采用IPoE协议，则接入网设备可以无需执行会话标识转换。
对于上行数据：
1)终端设备1向接入网设备发送上行数据，其中，上行数据的源IP地址为IP@1、端口号为1，携带的会话标识1；接入网设备将来自终端设备1的上行数据的源IP地址替换为IP@3、端口号为2，将会话标识替换为会话标识3，并通过固网网关设备发送至AS；
2)终端设备2向接入网设备发送上行数据，其中，上行数据的源IP地址为IP@2、端口号为1，携带会话标识2；接入网设备将来自终端设备2的上行数据的源IP地址替换为IP@3、端口号为3将会话标识替换为会话标识3，并通过固网网关设备发送至AS。
对于下行数据：
1)接入网设备接收下行数据，其中，下行数据的目的IP地址为IP@3、端口号为2，携带会话标识3，；接入网设备根据目的IP地址和端口号，确定该下行数据是要发往终端设备1的；接入网设备将下行数据的目的IP地址转换为IP@1，端口号转换为1，将会话标识替换为会话标识1，并向终端设备1发送该下行数据。
2)接入网设备接收下行数据，其中，下行数据的目的IP地址为IP@3、端口号为3，携带会话标识3；接入网设备根据目的IP地址和端口号，确定该下行数据是要发往终端设 备2的；接入网设备将下行数据的目的IP地址转换为IP@2，端口号转换为1，将会话标识替换为会话标识2，并向终端设备2发送该下行数据。
上文结合图5至图13，详细描述了本申请提供的方法实施例，下面将结合图14和图15，详细描述本申请的装置实施例。可以理解的是，为了实现上述实施例中功能，图14或图15中的装置包括了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本申请中所公开的实施例描述的各示例的单元及方法步骤，本申请能够以硬件或硬件和计算机软件相结合的形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用场景和设计约束条件。
图14和图15为本申请的实施例提供的可能的装置的结构示意图。这些装置可以用于实现上述方法实施例中接入网设备、核心网设备和AAA服务器的功能，因此也能实现上述方法实施例所具备的有益效果。
如图14所示，装置1400包括收发单元1410和处理单元1420。
当装置1400用于实现方法实施例中的接入网设备的功能时，收发单元1410用于：获取指示信息，所述指示信息用于所述接入网设备通过与固网网关设备的用户面连接传输终端设备的数据，所述接入网设备支持3GPP接入类型；收发单元1410和处理单元1420相互配合，用于：根据所述指示信息通过所述用户面连接传输所述终端设备的数据。
在一种实现方式中，所述指示信息包括用于指示所述设定类型的用户面数据的信息。
在一种实现方式中，所述指示信息包括用于指示所述终端设备为设定类型的终端设备的信息。
在一种实现方式中，所述指示信息包括在以下信息中的一个或多个中：注册接受信息、认证通过信息、会话接受信息、以及会话类型信息。
在一种实现方式中，所述收发单元1410具体用于：在所述终端设备的注册流程中获取所述指示信息；或者，在所述终端设备的会话建立流程中获取所述指示信息。
在一种实现方式中，所述收发单元1410具体用于：所述接入网设备接收来自所述终端设备的第一消息，所述第一消息用于请求对所述终端设备进行接入管理；所述处理单元1420具体用于：根据所述指示信息，获取第一信息，所述第一信息为可通过所述接入管理的认证的信息；所述收发单元1410具体还用于：向所述固网网关设备发送所述第一信息；接收来自所述固网网关设备的第二消息，所述第二消息指示所述终端设备通过所述接入管理的认证；向所述终端设备发送所述第二消息。
在一种实现方式中，所述第一信息包括可通过所述接入管理的认证的线路标识。
在一种实现方式中，所述收发单元1410具体用于：接收来自所述终端设备的第一消息，所述第一消息用于请求对所述终端设备进行接入管理，所述第一消息包括第二信息，所述第二信息为用于所述接入管理的认证的信息；所述处理单元1420具体用于：根据所述第二信息，获取第三信息，所述第三信息用于标识所述终端设备；所述收发单元1410具体还用于：向所述固网网关设备发送所述第二信息和所述第三信息；接收来自所述固网网关设备的第二消息，所述第二消息指示所述终端设备通过所述接入管理的认证；向所述终端设备发送所述第二消息。
在一种实现方式中，所述收发单元1410具体用于：接收来自所述终端设备的第一消息，所述第一消息用于请求对所述终端设备进行接入管理，所述第一消息包括第二信息， 所述第二信息为用于所述接入管理的认证的信息；向所述固网网关设备发送所述第二信息；接收来自所述固网网关设备的第二消息，所述第二消息指示所述终端设备通过所述接入管理的认证；向所述终端设备发送所述第二消息。
在一种实现方式中，所述第三信息包括用于标识所述终端设备的线路标识。
在一种实现方式中，所述第二信息包括以下任意一种或多种：用户名、密码、以及所述终端设备的MAC地址。
在一种实现方式中，所述第一消息为DHCP发现消息、DHCP请求消息、PADI消息或PADR消息。
在一种实现方式中，所述收发单元1410还用于：向所述固网网关设备发送第三消息，所述第三消息用于请求对所述接入网设备进行接入管理，所述第三消息包括第四信息，所述第四信息为可通过所述接入管理的认证的信息；接收所述网关设备发送的第四消息，所述第四消息指示所述接入网设备通过所述接入管理的认证，所述第四消息包括所述接入网设备的第一互联网协议IP地址。
在一种实现方式中，所述第四信息包括可通过所述接入管理的认证的线路标识。
在一种实现方式中，所述处理单元1420具体用于：为所述终端设备分配第二IP地址，所述第二IP地址对应于所述第一IP地址；所述收发单元1410还用于：接收来自所述终端设备的第一用户面数据，所述第一用户面数据包括所述第二IP地址；所述处理单元1420还用于：将所述第一用户面数据中的第二IP地址替换为所述第一IP地址，得到第二用户面数据；所述收发单元1410还用于：发送所述第二用户面数据。
在一种实现方式中，所述收发单元1410还用于：接收所述固网网关设备为所述接入网设备分配的第一会话标识；所述处理单元1420还用于：为所述终端设备分配第二会话标识，所述第二会话标识对应于所述第一会话标识；将所述第一用户面数据中的第二会话标识替换为所述第一会话标识。
在一种实现方式中，所述收发单元1410还用于：获取或预配置至少一个IP地址和/或至少一个会话标识，所述第二IP地址为所述至少一个IP地址中的一个，所述第二会话标识为所述至少一个会话标识中的一个。
在一种实现方式中，所述设定类型的终端设备为固网终端设备。
当装置1400用于实现方法实施例中的核心网设备的功能时，收发单元1410用于：获取指示信息，所述指示信息用于所述接入网设备通过与固网网关设备的用户面连接传输终端设备的数据；向接入网设备发送所述指示信息，所述接入网设备支持3GPP接入类型。
在一种实现方式中，所述指示信息包括用于指示所述设定类型的用户面数据的信息。
在一种实现方式中，所述指示信息包括用于指示所述终端设备为所述设定类型的终端设备的信息。
在一种实现方式中，所述指示信息包括在以下信息中的一个或多个中：注册接受信息、认证通过信息、会话接受信息、以及会话类型信息。
在一种实现方式中，所述收发单元1410具体用于：在所述终端设备的注册流程中向所述接入网设备发送所述指示信息；或者，在所述终端设备的会话建立流程中向所述接入网设备发送所述指示信息。
在一种实现方式中，所述收发单元1410具体用于：从统一数据管理功能网元获取所 述终端设备的签约数据；根据所述签约数据，获取所述指示信息。
在一种实现方式中，所述收发单元1410具体用于：获取所述终端设备的类型信息，所述终端设备的类型信息指示所述终端设备为所述设定类型的终端设备；根据所述类型信息，获取所述指示信息。
在一种实现方式中，所述类型信息包含于所述终端设备的签约数据；或者，所述类型信息来自所述终端设备。
在一种实现方式中，所述核心网设备为会话管理网元，所述处理单元1420用于：跳过选择用户面功能网元和/或为所述终端设备分配IP地址的流程。
在一种实现方式中，所述核心网设备为会话管理网元，所述收发单元1410还用于：向所述固网网关设备发送第五消息，所述第五消息用于请求对所述终端设备进行接入管理，所述第五消息包括第五信息，所述第五信息为可通过所述接入管理的认证的信息；接收来自所述固网网关设备的第六消息，所述第六消息指示所述终端设备通过所述接入管理的认证。
在一种实现方式中，所述第五信息包括可通过所述接入管理的认证的线路标识。
在一种实现方式中，所述设定类型的终端设备为固网终端设备。
当装置1400用于实现方法实施例中的AAA服务器的功能时，收发单元1410用于：接收来自终端设备的用户名和密码；处理单元1420用于：根据所述用户名和所述密码，对所述终端设备进行接入管理；若所述用户名对应的通过接入管理的认证的终端设备的数量大于预设阈值，拒绝第一数量的终端设备的接入管理，或者使能第一数量的终端设备下线，所述第一数量大于或等于所述预设阈值与所述用户名对应的通过接入管理的认证的终端设备的数量的差值。
在一种实现方式中，收发单元1410还用于：接收第三信息，所述第三信息用于标识所述终端设备；处理单元1420还用于：根据所述第三信息，确定所述用户名对应的通过接入管理的认证的终端设备的数量。
在一种实现方式中，所述第三信息包括用于标识所述终端设备的线路标识。
在一种实现方式中，所述第三信息与所述终端设备的标识信息对应。
在一种实现方式中，所述终端设备的标识信息包括以下信息中的一项或多项：地址信息、设备标识、永久标识、临时标识、外部标识或内部标识。
有关上述获取单元1410和处理单元1420更详细的描述可以直接参考上述方法实施例中相关描述直接得到，这里不加赘述。
如图15所示，装置1500包括处理器1510和接口电路1520。处理器1510和接口电路1520之间相互耦合。可以理解的是，接口电路1520可以为收发器或输入输出接口。在一种实现方式中，装置1500还可以包括存储器1530，用于存储处理器1510执行的指令或存储处理器1510运行指令所需要的输入数据或存储处理器1510运行指令后产生的数据。
当装置1500用于实现上文所述的方法时，处理器1510用于实现上述处理单元1420的功能，接口电路1520用于实现上述收发单元1410的功能。
当上述通信装置为应用于接入网设备的芯片时，该芯片实现上述方法实施例中接入网设备的功能。该芯片从接入网设备中的其它模块(如射频模块或天线)接收信息，该信息是其他设备发送给接入网设备的；或者，该芯片向接入网设备中的其它模块(如射频模块 或天线)发送信息，该信息是接入网设备发送给其它设备的。
当上述通信装置为应用于核心网设备的芯片时，该芯片实现上述方法实施例中核心网设备的功能。该芯片从核心网设备中的其它模块(如射频模块或天线)接收信息，该信息是其他设备发送给核心网设备的；或者，该芯片向核心网设备中的其它模块(如射频模块或天线)发送信息，该信息是核心网设备发送给其它设备的。
当上述通信装置为应用于AAA服务器的芯片时，该芯片实现上述方法实施例中AAA服务器的功能。该芯片从AAA服务器中的其它模块(如射频模块或天线)接收信息，该信息是其他设备发送给AAA服务器的；或者，该芯片向AAA服务器中的其它模块(如射频模块或天线)发送信息，该信息是AAA服务器发送给其它设备的。
本申请实施例还提供一种芯片，该芯片获取指令并执行该指令来实现上述的方法。
可选地，作为一种实现方式，该芯片包括处理器与数据接口，该处理器通过该数据接口读取存储器上存储的指令，执行上述方法。
可选地，作为一种实现方式，该芯片还可以包括存储器，该存储器中存储有指令，该处理器用于执行该存储器上存储的指令，当该指令被执行时，该处理器用于执行上述方法。
本申请实施例还提供一种通信系统，包括上述任意一种通信装置，或者包括上述任意一种芯片。
本申请实施例还提供一种计算机可读存储介质，该计算机可读存储介质存储有指令，该指令用于上述方法实施例中的方法。
本申请实施例还提供一种包含指令的计算机程序产品，该指令用于实现上述方法实施例中的方法。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其它通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现场可编程门阵列(field programmable gate array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
本申请的实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的随机存取存储器(random access memory，RAM)可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
可以理解的是，在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。
除非另有说明，本申请实施例所使用的所有技术和科学术语与本申请的技术领域的技术人员通常理解的含义相同。本申请中所使用的术语只是为了描述具体的实施例的目的，不是旨在限制本申请的范围。应理解，上述为举例说明，上文的例子仅仅是为了帮助本领域技术人员理解本申请实施例，而非要将申请实施例限制于所示例的具体数值或具体场景。本领域技术人员根据上文所给出的例子，显然可以进行各种等价的修改或变化，这样的修改和变化也落入本申请实施例的范围内。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (36)

  1. 一种传输数据的方法，其特征在于，所述方法包括：
    接入网设备获取指示信息，所述指示信息用于所述接入网设备通过与固网网关设备的用户面连接传输终端设备的数据，所述接入网设备支持第三代合作伙伴计划3GPP接入类型；
    所述接入网设备根据所述指示信息通过所述用户面连接传输所述终端设备的数据。
  2. 根据权利要求1所述的方法，其特征在于，所述接入网设备根据所述指示信息通过所述用户面连接传输所述终端设备的数据，包括：
    所述接入网设备根据所述指示信息与所述固网网关设备建立所述用户面连接；
    所述接入网设备通过所述用户面连接传输所述终端设备的数据。
  3. 根据权利要求1或2所述的方法，其特征在于，所述指示信息包括用于指示设定类型的用户面数据的信息。
  4. 根据权利要求1或2所述的方法，其特征在于，所述指示信息包括用于指示所述终端设备为设定类型的终端设备的信息。
  5. 根据权利要求4所述的方法，其特征在于，所述设定类型的终端设备为固网终端设备。
  6. 根据权利要求1或2所述的方法，其特征在于，所述指示信息包括在以下信息中的一个或多个中：注册接受信息、认证通过信息、会话接受信息、以及会话类型信息。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，所述接入网设备获取指示信息，包括：
    所述接入网设备在所述终端设备的注册流程中获取所述指示信息；或者，
    所述接入网设备在所述终端设备的会话建立流程中获取所述指示信息。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述方法还包括：
    所述接入网设备接收来自所述终端设备的第一消息，所述第一消息用于请求对所述终端设备进行接入管理；
    所述接入网设备根据所述指示信息，获取第一信息，所述第一信息为可通过所述接入管理的认证的信息；
    所述接入网设备向所述固网网关设备发送所述第一信息；
    所述接入网设备接收来自所述固网网关设备的第二消息，所述第二消息指示所述终端设备通过所述接入管理的认证；
    所述接入网设备向所述终端设备发送所述第二消息。
  9. 根据权利要求8所述的方法，其特征在于，所述第一信息包括可通过所述接入管理的认证的线路标识。
  10. 根据权利要求1至7中任一项所述的方法，其特征在于，所述方法还包括：
    所述接入网设备接收来自所述终端设备的第一消息，所述第一消息用于请求对所述终端设备进行接入管理，所述第一消息包括第二信息，所述第二信息为用于所述接入管理的认证的信息；
    所述接入网设备根据所述第二信息，获取第三信息，所述第三信息用于标识所述终端设备；
    所述接入网设备向所述固网网关设备发送所述第二信息和所述第三信息；
    所述接入网设备接收来自所述固网网关设备的第二消息，所述第二消息指示所述终端设备通过所述接入管理的认证；
    所述接入网设备向所述终端设备发送所述第二消息。
  11. 根据权利要求1至7中任一项所述的方法，其特征在于，所述方法还包括：
    所述接入网设备接收来自所述终端设备的第一消息，所述第一消息用于请求对所述终端设备进行接入管理，所述第一消息包括第二信息，所述第二信息为用于所述接入管理的认证的信息；
    所述接入网设备向所述固网网关设备发送所述第二信息；
    所述接入网设备接收来自所述固网网关设备的第二消息，所述第二消息指示所述终端设备通过所述接入管理的认证；
    所述接入网设备向所述终端设备发送所述第二消息。
  12. 根据权利要求10所述的方法，其特征在于，所述第三信息包括用于标识所述终端设备的线路标识。
  13. 根据权利要求10至12中任一项所述的方法，其特征在于，所述第二信息包括以下任意一种或多种：用户名、密码、和所述终端设备的介质接入控制MAC地址。
  14. 根据权利要求8至13中任一项所述的方法，其特征在于，所述第一消息为以下消息中的一种：动态主机配置协议DHCP发现消息、DHCP请求消息、以太网承载点对点协议主动发现初始PADI消息、或以太网承载点对点协议主动发现请求PADR消息。
  15. 根据权利要求1至7中任一项所述的方法，其特征在于，所述方法还包括：
    所述接入网设备向所述固网网关设备发送第三消息，所述第三消息用于请求对所述接入网设备进行接入管理，所述第三消息包括第四信息，所述第四信息为可通过所述接入管理的认证的信息；
    所述接入网设备接收所述网关设备发送的第四消息，所述第四消息指示所述接入网设备通过所述接入管理的认证，所述第四消息包括所述接入网设备的第一互联网协议IP地址。
  16. 根据权利要求15所述的方法，其特征在于，所述第四信息包括可通过所述接入管理的认证的线路标识。
  17. 根据权利要求15或16所述的方法，其特征在于，所述方法还包括：
    所述接入网设备为所述终端设备分配第二IP地址，所述第二IP地址对应于所述第一IP地址；
    所述接入网设备接收来自所述终端设备的第一用户面数据，所述第一用户面数据包括所述第二IP地址；
    所述接入网设备将所述第一用户面数据中的第二IP地址替换为所述第一IP地址，得到第二用户面数据；
    所述接入网设备发送所述第二用户面数据。
  18. 根据权利要求17所述的方法，其特征在于，所述方法还包括：
    所述接入网设备接收所述固网网关设备为所述接入网设备分配的第一会话标识；
    所述接入网设备为所述终端设备分配第二会话标识，所述第二会话标识对应于所述第一会话标识；
    所述接入网设备将所述第一用户面数据中的第二会话标识替换为所述第一会话标识。
  19. 根据权利要求18所述的方法，其特征在于，所述方法还包括：
    所述接入网设备获取或预配置至少一个IP地址和/或至少一个会话标识，所述第二IP地址为所述至少一个IP地址中的一个，所述第二会话标识为所述至少一个会话标识中的一个。
  20. 一种传输数据的方法，其特征在于，所述方法包括：
    核心网设备获取指示信息，所述指示信息用于接入网设备通过与固网网关设备的用户面连接传输终端设备的数据；
    所述核心网设备向所述接入网设备发送所述指示信息，所述接入网设备支持第三代合作伙伴计划3GPP接入类型。
  21. 根据权利要求20所述的方法，其特征在于，所述指示信息包括用于指示设定类型的用户面数据的信息。
  22. 根据权利要求20所述的方法，其特征在于，所述指示信息包括用于指示所述终端设备为设定类型的终端设备的信息。
  23. 根据权利要求22所述的方法，其特征在于，所述设定类型的终端设备为固网终端设备。
  24. 根据权利要求20所述的方法，其特征在于，所述指示信息包括在以下信息中的一个或多个中：注册接受信息、认证通过信息、会话接受信息、以及会话类型信息。
  25. 根据权利要求20至24中任一项所述的方法，其特征在于，所述核心网设备向接入网设备发送指示信息，包括：
    所述核心网设备在所述终端设备的注册流程中向所述接入网设备发送所述指示信息；或者，
    所述核心网设备在所述终端设备的会话建立流程中向所述接入网设备发送所述指示信息。
  26. 根据权利要求20至25中任一项所述的方法，其特征在于，所述核心网设备获取指示信息，包括：
    所述核心网设备从统一数据管理功能网元获取所述终端设备的签约数据；
    所述核心网设备根据所述签约数据获取所述指示信息。
  27. 根据权利要求20至25中任一项所述的方法，其特征在于，所述核心网设备获取指示信息，包括：
    所述核心网设备获取所述终端设备的类型信息，所述终端设备的类型信息指示所述终端设备为所述设定类型的终端设备；
    所述核心网设备根据所述类型信息获取所述指示信息。
  28. 根据权利要求27所述的方法，其特征在于，
    所述类型信息包含于所述终端设备的签约数据；或者，
    所述类型信息来自所述终端设备。
  29. 根据权利要求20至28中任一项所述的方法，其特征在于，所述核心网设备为会话管理网元，所述方法还包括：
    所述会话管理网元跳过选择用户面功能网元和/或为所述终端设备分配互联网协议IP地址的流程。
  30. 根据权利要求20至29中任一项所述的方法，其特征在于，所述核心网设备为会话管理网元，所述方法还包括：
    所述会话管理网元向所述固网网关设备发送第五消息，所述第五消息用于请求对所述终端设备进行接入管理，所述第五消息包括第五信息，所述第五信息为可通过所述接入管理的认证的信息；
    所述会话管理网元接收来自所述固网网关设备的第六消息，所述第六消息指示所述终端设备通过所述接入管理的认证。
  31. 根据权利要求30所述的方法，其特征在于，所述第五信息包括可通过所述接入管理的认证的线路标识。
  32. 一种通信装置，其特征在于，包括：
    处理器，用于执行存储器中存储的计算机指令，以使得所述装置执行：如权利要求1至31中任一项所述的方法。
  33. 一种通信装置，其特征在于，包括：
    存储器，用于存储计算机指令；
    处理器，用于执行所述存储器中存储的计算机指令，以使得所述装置执行：如权利要求1至31中任一项所述的方法。
  34. 一种计算机可读存储介质，其特征在于，包括：所述计算机可读介质存储有计算机程序；所述计算机程序由一个或多个处理器执行时，使得包括所述处理器的装置执行如权利要求1至31中任一项所述的方法。
  35. 一种计算机程序产品，其特征在于，所述计算机程序产品包括计算机程序代码，当所述计算机程序代码在计算机上运行时，实现权利要求1至31中任一项所述的方法。
  36. 一种通信系统，其特征在于，包括：
    接入网设备，用于执行如权利要求1至19中任一项所述的方法；
    以及与所述接入网设备进行通信的核心网设备。
PCT/CN2022/105027 2021-07-19 2022-07-12 一种传输数据的方法和装置 WO2023001015A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110811077.7A CN115643611A (zh) 2021-07-19 2021-07-19 一种传输数据的方法和装置
CN202110811077.7 2021-07-19

Publications (1)

Publication Number Publication Date
WO2023001015A1 true WO2023001015A1 (zh) 2023-01-26

Family

ID=84939762

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/105027 WO2023001015A1 (zh) 2021-07-19 2022-07-12 一种传输数据的方法和装置

Country Status (2)

Country Link
CN (1) CN115643611A (zh)
WO (1) WO2023001015A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019047197A1 (en) * 2017-09-11 2019-03-14 Telefonaktiebolaget Lm Ericsson (Publ) METHOD AND SYSTEM FOR INTEGRATING FIXED ACCESS IN A CONVERGED 5G HEART
CN110417840A (zh) * 2018-04-28 2019-11-05 华为技术有限公司 一种信息处理方法及装置
CN110896553A (zh) * 2018-09-12 2020-03-20 中国电信股份有限公司 多接入边缘计算方法和平台、通信系统
WO2020199896A1 (zh) * 2019-04-02 2020-10-08 华为技术有限公司 一种业务流路由控制方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019047197A1 (en) * 2017-09-11 2019-03-14 Telefonaktiebolaget Lm Ericsson (Publ) METHOD AND SYSTEM FOR INTEGRATING FIXED ACCESS IN A CONVERGED 5G HEART
CN110417840A (zh) * 2018-04-28 2019-11-05 华为技术有限公司 一种信息处理方法及装置
CN110896553A (zh) * 2018-09-12 2020-03-20 中国电信股份有限公司 多接入边缘计算方法和平台、通信系统
WO2020199896A1 (zh) * 2019-04-02 2020-10-08 华为技术有限公司 一种业务流路由控制方法、装置及系统

Also Published As

Publication number Publication date
CN115643611A (zh) 2023-01-24

Similar Documents

Publication Publication Date Title
CN109391940B (zh) 一种接入网络的方法、设备及系统
EP4117340A1 (en) Business processing method, device and system for proximity service
WO2023284584A1 (zh) 通信方法和装置
RU2518186C2 (ru) Обработка трафика локального непосредственного соединенения в домашней базовой станции
KR102157185B1 (ko) 무선 통신 시스템에서 접속 계층을 통해 서비스 연결을 제공하는 장치 및 방법
KR20200115333A (ko) 무선 통신 시스템에서 에지 컴퓨팅 서비스를 제공하기 위한 위한 장치 및 방법
JP2020507255A (ja) 目標セルアクセス方法及び装置
US10291695B2 (en) Method and apparatus and computer readable record media for communication on wi-fi direct multi-group network
US20210075618A1 (en) Device-independent authentication based on a passphrase and a policy
US20170244705A1 (en) Method of using converged core network service, universal control entity, and converged core network system
CN114208386B (zh) 用户设备到用户设备中继的连接建立方法及其用户设备
EP3459318A1 (en) Using wlan connectivity of a wireless device
EP2572491B1 (en) Systems and methods for host authentication
US11611923B2 (en) Methods and apparatus for supporting quality of service in a system including a cable modem termination system and wireless communications link
WO2014153721A1 (zh) 数据包传输方法、系统及终端设备和网络设备
WO2014169240A1 (en) Internet protocol address registration
CN115462123A (zh) 扩展的5g局域网与家庭网络的互通以及对5g lan连接设备的接入网络的改变
WO2012130133A1 (zh) 一种接入点及终端接入方法
TW201401878A (zh) 在家庭ｍｏｃａ骨幹網上的分佈式無線擴展器
WO2022199451A1 (zh) 会话切换的方法和装置
WO2013174098A1 (zh) 基于capwap协议的网络接入方法、装置和系统
KR102055911B1 (ko) 세션 연결을 위한 시그널링 방법, 그리고 이를 구현한 장치
WO2020187261A1 (zh) 一种通信方法、装置及系统
WO2017206575A1 (zh) 通信协议接入的方法、装置及系统
WO2023001015A1 (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: 22845180

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE